Güralp digitizers manufactured after 2005 are of this type. Firmware for these modules has a version number above v.100.
The digitizer has three firmware components, which can be updated separately: the main system program, the DSP code and the boot loader. The .zip file on this page contains all three of these files.
To find out what version of the main system program you are currently using, right-click on the digitizer’s icon (not the Local or the Comxx icons) in Scream!'s main window and select Configure from the pop-up menu. This will open the Configuration setup window. The version number is given in the Software revision box.
IMPORTANT: if you are upgrading from firmware versions before v.103 build 27, you will need to update the bootloader code first. See the release notes and instructions below for further information.
Ethernet: if your digitizer has an Ethernet port, you will need a different firmware version to use it. Please contact support@guralp.com for more information and to get the latest Ethernet-enabled firmware.
Download the latest DM24 mk3 firmware, a 179K .zip file including:
IMPORTANT: If you have a CMG-5TD sensor/digitizer with an integrated LCD status panel, please use bootloader v.10 build 27 to avoid loss of LCD functionality.
Earlier versions of the DM24mk3 firmware, for testing or reference, may be downloaded from: the DM24mk3 download directory.
You can update the digitizer firmware using any terminal program which supports the Xmodem protocol, such as hypertrm or newer versions of Scream!.
To install this firmware using Scream!:
Right-click on the digitizer’s icon in the main window and select Terminal from the pop-up menu:
Check that there is two-way communication with the digitizer by pressing Enter. The digitizer should reply with ok on a new line.
Type re-boot to reinitialize the digitizer, and confirm with y. As it is restarting, the digitizer will report its status over the terminal connection, followed by a maintenance menu:
MPE ARM ANS ROM PowerForth v6.20 ARM Serial BootStrap v1.100, 11 August 2003 Copyright (c) 2002-3 GSL, EDSL & MicroProcessor Engineering Ltd. Port 0 38400 baud Port 1 38400 baud Port 2 38400 baud Guralp Systems Ltd - ARM-BOOT v01.0 mgs 29/07/04 [b 015] System Code versions loaded :- 0103:0000 Guralp Systems Ltd DMARM v01.0 mgs 09/07/04 [Build 017] 0107:0000 Guralp Systems Ltd - DM+FW v01.1 mgs 11/08/04 [Build 007] Default 010B:0000 Blank DSP Code : 0101:0000 ARMT16D16-050304.BIN 0102:0000 dm48ch1048.bin 04/08/04 Default Command keys: C - set real time Clock (2004 8 13 09:29:48 ) I - view/upload InfoBlock F - run the Forth monitor R - Run an application E - Erase an application S - update System program B - update Boot program D - update DSP code N - set the default application Number (3) Q - Quit maintenance system 3 seconds to auto-start Enter command:
If you do not press a key in the next 5 seconds, the digitizer will start up normally.
To update the system program, press S at the maintenance menu. The digitizer will display
Update System program
There are three slots available for system application code. The digitizer will automatically use either the first free slot, or the slot which currently contains the oldest firmware version. In the example above, there are three System code versions loaded, of which the one in slot 2 (0107:0000 in memory) is currently the Default.
The digitizer will then request a transfer using the Xmodem protocol. If you are using Scream!, a file browser window will appear automatically.
Navigate through the directories on your computer and select the file to be uploaded, or type in its full path and file name. Click Open.
Whilst the file is loading, a progress window will be
displayed. Depending on the speed of the link, it may take up to 20
minutes to transfer the firmware.
Once the file is fully transferred, the digitizer will set the new firmware as the Default and return to the maintenance menu.
If there was a problem during transfer, the previous Default will stay active.
Go back to step 2 and try again.Look in the boot-up messages to find the version of the boot loader you are currently using.
Guralp Systems Ltd - ARM-BOOT v01.0 mgs 29/07/04 [b 015]
In this example, the current boot loader is version 1.0, build 15.
If the boot loader in the firmware package is newer than the version you have installed, you will need to update it. Press B at the maintenance menu to do this.
The digitizer will then request a transfer using the Xmodem protocol, as described above.
Look in the boot-up messages to find the version of the DSP code you are currently using.
DSP Code : 0101:0000 ARMT16D16-050304.BIN 0102:0000 dm48ch1048.bin 04/08/04 Default
There are two slots available for DSP code. In this example, the version in use is dm48ch1048.bin, i.e. version 1.048 .
If the DSP code in the firmware package is newer than the version you have installed, you will need to update it. Press D at the maintenance menu to do this. The digitizer will reply with
Enter 0/1 to select DSP code to update
Select which of the two DSP code slots you want to overwrite, and press ENTER. The default is slot 0. The digitizer will then prompt:
Enter Filename/date – upto 31 characters
You can enter a descriptive string for the DSP code here. The digitizer will print this string at every boot-up, to remind you which version of the DSP code you are using. If you leave this blank, the original filename will be used.
The digitizer will then request a transfer using the Xmodem protocol, as described above.
Set default Application Number Enter Application number 1..3:
Type the number of the slot you have used for the new system code, followed by ENTER, and wait whilst the system reboots. This sets the Default application which will be used every time the digitizer starts up.
Alternatively, you can test the new system code by pressing R at the maintenance menu, followed by the slot number of the new code. This will run the digitizer with the new firmware for one session only. When it is rebooted, tha digitizer will revert to the Default application.
2008 6 12 10:38:45 Data Ready to Transfer 2008 6 12 10:41:25 Data Transfer Complete #Entries: 83 of 510 Capacity 1.2GB Used 1.0GB Available 200.9MB Not enough space for next transfer 4.1GB FireWire Buffer 2008 6 12 10:50:32 Transferring 30.0MB to Disk 2008 6 12 10:50:53 Data Transfer Complete #Entries: 84 of 510 Capacity 19.5GB Used 1.0GB Available 18.4GB FireWire buffer too small for optimum disk useage *****
SetPGAalarm to set the level in gal.
| Measurement | Current loop output | Relay output | Sensor |
|---|---|---|---|
| SI | 0 | 0 | Sensor A |
| PGA | 1 | 1 | Sensor A |
| SI | 2 | 2 | Sensor B |
| PGA | 3 | 3 | Sensor B |
LLstreams disable to suppress output of data streams, so that only strong motion computed
values are output. Use LLstreams enable to return to previous operation.baud command. Use the new Forth command
[baud] for other rates.uspmonitor to re-enable
unified status packets.SetTriggerLevels (protected) for real-units setup of level
triggering.&H0 part).
Remove spurious characters during setmodem$ command
interaction.setmodem$). +modem supports option for
'dial-in only' mode.setdssrate). Supports 'enhanced' BRP mode developed for IP
wireless networking. System also automatically 'files' data that would have been lost due to
transmit buffer — can be recovered by selecting adaptive mode.Note: Units running firmware before v.103 build 10 may incorrectly mark blocks of Flash memory as "bad" and not use them. To return incorrectly-marked blocks to use, download all data from Flash memory, then issue the commands
ok-1 \ select extended dictionary vocabulary direct \ switch off flash filing mode .badblks \ show current table 0 blkerase . \ erase table (note the "." after blkerase) checkflash \ rescan for marked bad blocks .badblks \ show updated table erasefile \ to completely clear the data in flash [seal] \ revert to 'system' commandsNow reconfigure the digitizer to record to flash using the previous filing mode.