New Gecko Firmware [Updated]

Version 2.5 of the Gecko firmware adds improved reliability for the optional Telit 3G modem. This is in addition to the feature updates in v2.4 below. The upgrade process is as simple as ever – simply download the Rasbora.bin file, copy it onto an SD card, insert it into your Gecko and then apply power. The Gecko scans the SD card for the firmware file and if the build number is greater than its own it will reboot, reprogram its processor, then restart, all within about 10 seconds. The firmware remains on the SD card – you can delete it, or use the SD card to upgrade other Gecko recorders.

The latest firmware for the Gecko seismograph, version 2.4, brings many new features, support for future remote firmware upgrades, remote Gecko configuration via the Live Stream app and eqServer, performance improvements and bug fixes.

The new Histogram feature creates a daily CSV file on the SD card, with data logged every minute. The file can be easily imported into Excel or other graphing packages. The CSV file stores the maximum and minimum signal values for each channel from the previous minute, the supply voltage, internal temperature, latitude, longitude, altitude, horizontal and vertical GPS accuracy, and the clock crystal information.

By plotting the peak signal values you can quickly visualise a day of monitoring activity, which is particularly useful for blast monitoring applications.

When a Gecko is connected to a computer running Kelunji Hub (included in the free Windows/Linux Live Stream app and on eqServer) via Ethernet connection or cellular modem, in addition to continuous data streaming we now have a “Triggered Only” mode that just sends instantaneous trigger packets, suited to EEW (earthquake early warning) applications. Kelunji Hub can immediately generate an alarm, then request waveform data from the trigger time from all connected Gecko recorders for further analysis.

You can now also save your Gecko configuration file and then load that configuration file into another Gecko, which is particularly useful when pre-configuring large numbers of identical instruments for a deployment. Don’t forget to change each station code!

Download the updated user manual from our documentation resource library and get in touch if you have any questions or feedback.