Guralp Systems Limited
MAN-MIN-0001 - Güralp Minimus - Technical Manual

PreviousNext

1. Preliminary Notes 2. System Overview 3. System description 4. Getting started 5. Advanced system configuration 6. GüVü app 7. Advanced troubleshooting 8. Appendix 1 – Instrument/channel names 9. Appendix 2 – Minimus ports 10. Appendix 3 – Güralp Discovery installation 11. Appendix 4 – Connector pin-outs 12. Revision History

Section Index: 5.1. System status 5.2. Station meta-data 5.3. GDI auto-connection 5.4. I.P. address options 5.5. Power monitoring 5.6. Data storage 5.7. Data transmission 5.8. Timing 5.9. Configuration and control of connected digital instruments 5.10. Configuration and control of connected analogue instruments 5.11. Setting a sensors orientation 5.12. Earthquake Early Warning 5.13. Using a registry 5.14. Updating Minimus firmware 5.15. Import / Export an existing configuration

Chapter 5. Advanced system configuration

Advanced system configuration control and configuration tools are available by selecting an instrument in Discovery, right-clicking its entry and selecting “View Web Page”. Alternatively, the web interface can be viewed by navigating to the LAN address of the instrument from any common web-browser.

5.1 System status

The “System Status” tab of the web browser interface provides a number of state-of-health information about the Minimus and connected instruments. These parameters are described as follows:

5.2 Station meta-data

Discovery provides a number of flexible station meta-data inputs.

These are accessible from the “Setup” tab of the instrument’s web browser window.

Label” is used in Discovery only and appears in the list of instruments in the main window. The Label can also be edited by right-clicking on the instrument in the main window of Discovery and selecting “Edit Label”.

Station Name, Network Code and “Site Name are all standard meta-data header values used by the miniSEED file format, which will be included in locally-stored miniSEED files (see section 5.6).

5.3 GDI auto-connection

Minimus normally acts as a server and a connection can be made by a client to pull data, as when the GDI viewer in Discovery is launched.

The GDI auto-connection feature enables the Minimus to establish outgoing network connections in order to push data to one or more remote clients, such as Platinum systems or an Earthworm system running the gdi2ew plug-in.

To configure an auto-connection, type either the I.P. address or the host-name of the client, together with the port number, in one of the connection fields in the “Network” tab of the web page.

When the auto-connection from Minimus to a host is configured, and that host listens to incoming connections, Minimus will negotiate the link with the client and start streaming data.

The Minimus will check to see whether there is an open connection to the configured client every 60 seconds.

5.4 I.P. address options

By default, the Minimus uses DHCP (Dynamic Host Configuration Protocol) to acquire its network configuration but static I.P. addressing can be used where required.

To configure static addressing, visit the “Network” tab of the instrument’s Web page and, under “DHCP”, change the mode from “DHCP” to “Static On” in the drop-down menu.

In this mode, it is possible to specify the I.P. address,the NetMask and the address of the Gateway (default router), as shown:

Before any changes made here will take effect, the Minimus must be re-booted. To do this, click the button on the “Data Record” tab

Network settings are also available in Discovery by right-clicking on the Minimus and selecting “Edit Network Address”.

5.5 Power monitoring

The “Power” tab of the Minimus’s web page provides information about the supply voltage, as measured by the Minimus. The Minimus can also be powered using Power-over-Ethernet (PoE). The voltage measured at the PoE input is also displayed here.

5.6 Data storage

MicroSD cards need to be specifically formatted to operate with the Minimus. Cards supplied with Radian systems will have the correcting formatting applied prior to shipping.

Data are stored on the microSD cards in the commonly-used miniSEED format, in which each channel during a period of recording is saved as a single file. Instrument and station meta-data (e.g. instrument responses, coordinates, compression type etc.) are also stored in the Dataless SEED format.

Monitoring and configuration of data storage can be found in the “Data Record” tab of instrument web page. This page is organised into three main panels: microSD status, card formatting controls and channel recording configuration.

Note: When changing a setting in the Minimus web page, ensure that you wait for a few seconds before changing another setting. This allows the previous changes to take effect.

Main panels of the Data Record tab within the instrument web browser window

5.6.1 Recording status

Card and data recording status can be monitored in the upper-most panel of the “Data Record” tab.

The left-hand column provides details of the external (primary, removable) microSD card; the right-hand column shows the status of the internal (backup) card.

microSD card and file storage status panel

In this panel, check-boxes are used to indicate the status of the following:

Note: After re-inserting an external microSD card, reload the Data Record page so that the card/recording status information can successfully update.

5.6.2 MicroSD card re-formatting

During the card re-formatting process, empty files are created that can be written to at a later date.

There are two methods for card reformatting: “Quick format” and “Full format”. The quick format mode should be used for pre-deployment tests (e.g. stomp/huddle tests) to ensure that the instruments are operating properly. This mode simply marks existing files as empty without deleting their contents. Full formatting should be used prior to a long-term deployment to ensure that headers are included and files are fully clean before writing.

5.6.2.1 Quick format

Ensure the external microSD card is correctly inserted. Click the button and a dialogue box will appear to confirm the formatting operation – click the “OK” button to continue. The instrument web page will refresh and return to the “Status” tab. The reformatting operation is now complete.

5.6.2.2 Full format

Ensure the external microSD card is correctly inserted. Click the button and a dialogue box will appear to confirm the formatting operation – click the “OK” button to continue. The instrument web page will refresh and return to the “Status” tab. The reformatting operation is now complete.

5.6.3 Channel recording set-up

Using the “Output Rate SPS” column, drop-down boxes are available for each channel to either prevent the channel from recording by selecting the “Disabled” option, or to stop all channels from saving, select the button.

Upon changing the sample rate, the Minimus will need to be restarted for the changes to come into effect; this can be done by pressing the button.

During the reboot, the LEDs will flash using the starting-up sequence (see section 3.1.2) and the Instrument Web Page will display the following screen.

Once the Minimus has successfully restarted, the full web browser display/controls will be available to view.

5.6.4 Viewing recorded data

The “Storage” tab of the web browser interface displays the miniSEED files stored on the microSD card:

If the web page is accessed from a web browser, clicking on the file from the list automatically starts a download, as in the picture below.

Where the web page is launched from Discovery, it is necessary to copy the URL of the file and paste it into a web browser.

The microSD cards are formatted with empty files which are filled with data as they become available. The file-names are also changed when the files are written to. Until they are written to, they are marked as “hidden” files, so that it is easier to see how many files contain data when looking at the contents of the card.

Note: When viewing files in Windows Explorer, Güralp highly recommends that Hidden files are not shown. In Windows 10, this can be done by clearing the “Hidden items” check-box within the ribbon of Windows Explorer.

Ensuring that Hidden files are not shown in Windows Explorer

To view files saved on the external microSD card, insert the card into a microSD card reader (external or in-built) on your PC/laptop. Within a few seconds, the card should appear as a removable disk/drive.

In the root directory of the disk, there is a file name network.DATALESS where network is the two-character network code defined in Discovery (e.g. GU.DATALESS). This file is a dataless SEED volume that contains meta-data (http://ds.iris.edu/ds/nodes/dmc/data/formats/dataless-seed/); (including instrument responses, coordinates, compression type etc.) that is used in combination with the miniSEED data-files. The dataless SEED volume is generated from the .RESP files for each channel.

In the root directory, there is also a directory named all_miniSEED_files_are_in_here. Within this directory, there will be a miniSEED file for each recording channel. The file-name prefix is the same as the channel name description given in the “Data Record” tab. Each file is 128 MB in size.

Files and directories in the root directory of the microSD card

miniSEED files stored on the microSD card

5.7 Data transmission

Monitoring and configuration of transmitted data is handled by the “Data Flow” tab of the instrument’s web page.

In the “Output Rate SPS” column, drop-down boxes are available for each channel to either select a sample rate or exclude the channel from streaming, which is done by selecting the “Disabled” option.

Upon changing the sample rate, the Minimus will need to be restarted for the changes to come into effect; this can be done by pressing the button.

During the reboot, the LEDs will flash, displaying the starting-up sequence (see section 3.1.2) and the Instrument Web Page will display the following screen.

Once the Minimus has successfully restarted, the full web browser display/controls will be available to view again.

5.7.1 Scream! (GCF format + Scream protocol)

The Minimus can act as a Scream! Server and stream data by sending GCF (Güralp Compressed Format) packets over a network connection using the scream data transmission protocol.

This is primarily intended to support Güralp’s Scream! Software (see section 4.3.2) or any software that can communicate using the Scream! Protocol, including SeisComP3.

Note: Güralp devices running the Platinum software can receive GCF data over the scream protocol, but gdi-link is recommended for use in these cases.

These include:

Data can also be received by software that can communicate using the Scream! Protocol, including SeisComp3 and Earthworm.

5.7.2 GDI-link protocol

The Minimus can also transmit data using the GDI-link protocol. GDI-link can currently be used with:

GDI-link provides a highly efficient, low latency method of exchanging data via TCP between seismic stations and data centres. The protocol allows state-of-health information to be attached to samples during transmission. A receiver can accept data from multiple transmitters, and a single transmitter can send data to multiple receivers, allowing maximum flexibility for configuring seismic networks. GDI-link streams data sample-by-sample (instead of assembling them into packets) to minimise transmission latency.

A significant advantage of GDI-link is that it has the ability to stream data pre-converted into real physical units instead of just as raw digitiser counts.

For more information on GDI-link, please refer to Güralp manual SWA‑RFC‑GDIL (SWA‑RFC‑GDIL">http://www.guralp.com/documents/SWA-RFC-GDIL).

5.7.3 SEEDlink protocol

The Minimus can act as a SEEDlink server to send miniSEED data packets over a network connection.

There is currently no option to turn the SEEDlink server on or off; the SEEDlink server is always switched on by default.

To test the SEEDlink server, Güralp recommends using the slinktool software for Linux, which is distributed by IRIS. For more information and to download, see http://ds.iris.edu/ds/nodes/dmc/software/downloads/slinktool/.

To show a list of available miniSEED streams, issue the command:

$ slinktool -Q IP-Address

Which produces output like the following:

DG TEST  00 CHZ D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  01 HHZ D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 CHN D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  01 HHN D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 CHE D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  01 HHE D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 MHZ D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 MHN D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 MHE D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

DG TEST  00 HMZ D 2016-09-13 10:42:18  -  2016-09-13 10:46:56

…etc

To print miniSEED data records of a single channel, you will need the following command:

$ slinktool -p -S DG_TEST:00HNZ.D IP-Address

Which produces the following output:

DG_TEST_00_HNZ, 412 samples, 100 Hz, 2016,257,10:43:42.000000 (latency ~2.9 sec)

DG_TEST_00_HNZ, 415 samples, 100 Hz, 2016,257,10:43:46.120000 (latency ~2.6 sec)

DG_TEST_00_HNZ, 416 samples, 100 Hz, 2016,257,10:43:50.270000 (latency ~3.0 sec)

DG_TEST_00_HNZ, 413 samples, 100 Hz, 2016,257,10:43:54.430000 (latency ~2.6 sec)

DG_TEST_00_HNZ, 419 samples, 100 Hz, 2016,257,10:43:58.560000 (latency ~3.0 sec)

DG_TEST_00_HNZ, 418 samples, 100 Hz, 2016,257,10:44:02.750000 (latency ~2.6 sec)

DG_TEST_00_HNZ, 415 samples, 100 Hz, 2016,257,10:44:06.930000 (latency ~3.0 sec)

DG_TEST_00_HNZ, 417 samples, 100 Hz, 2016,257,10:44:11.080000 (latency ~2.6 sec)

DG_TEST_00_HNZ, 416 samples, 100 Hz, 2016,257,10:44:15.250000 (latency ~3.0 sec)

DG_TEST_00_HNZ, 416 samples, 100 Hz, 2016,257,10:44:19.410000 (latency ~3.4 sec)

…etc

The SEEDlink server on the Minimus also supports the use of wild-cards (the “?” character) within network, station and channel codes. This allows you to request multiple streams using a single command.

5.8 Timing

The Minimus system supports timing provided through an attached GNSS receiver or, if that is not available, using Network Timing Protocol (NTP). The currently supported GNSS systems are Navstar (GPS), GLONAS and BeiDou.

5.8.1 GNSS lock status

This is available in the “Status” tab of the instrument’s Web page. A number of GNSS reporting parameters are given, including:

GNSS timing status in the instrument web page

5.8.2 Network Timing Protocol (NTP)

By default, the NTP server option under the “Setup” tab of the instrument’s web page is set to “Pool” which uses the virtual server pool pool.ntp.org.

Alternatively, it is possible to set the I.P. of your preferred NTP server. To do this, select the “Static” option from the “NTP server” drop-down menu, which activates the “NTP IP Addr” setting; add your NTP server’s I.P. address here.

5.9 Configuration and control of connected digital instruments

Please refer to Section 7 of MAN-RAD-0001 for full details on configuring and controlling digital instruments that are connected to the Minimus (e.g. a Güralp Radian).

5.10 Configuration and control of connected analogue instruments

5.10.1 Setting instrument (sensor) gain

The Güralp Fortis strong-motion accelerometer features a remotely-switchable gain option that can be controlled from inside Discovery. First, ensure that physical gain switch on the underside of the Fortis is set to position “3” (as indicated by the engraving). See MAN‑FOR‑0001 for more details.

To change the gain electronically, first, set the “Instrument Type” to “Fortis”. Setting this option will then enable the “Instrument Gain” control. Under the “Instrument Gain”, select a gain setting (options: 0.5g; 1g; 2g; 4g).

Setting the instrument type to “Fortis” will also change the miniSEED channel names to indicate that data are recorded from an accelerometer, e.g. “HNZ”.

Changing the gain for a Güralp Fortis strong motion accelerometer. Key switches are highlighted in red.

5.10.2 Setting digitiser gain

The input gain can be controlled from the "Setup" tab of the web page using the “Input Gain” drop-down box. Digitiser gain options available are: Unity, ×2, ×4, ×8 and ×12.

5.10.3 Mass control

The Minimus allows control of mass centring and locking for connected instruments.

5.10.3.1 Mass centring

Many broadband seismometers (e.g. Güralp 3T and 3ESPC) support remote/electronic mass centring. Mass centring can be controlled from the "Setup" tab of the web page using the “Recentre” button.

Note: “Instrument Type” must be set to “Generic” for the mass lock control buttons to be visible.

Mass centring status and control can also be found in the Centring tab of the instrument Control Centre window.

5.10.3.2 Mass locking

Some seismometers require their masses to be locked for transportation. Mass locking can be controlled from the "Setup" tab of the web page using the “Lock” and “Unlock” buttons.

Note: The mass lock control buttons are not displayed unless the “Sensor Type” is set to “Generic”.

5.10.4 Instrument response parameters

Calibration is a procedure used to verify or measure the frequency response and sensitivity of a sensor. It establishes the relationship between actual ground motion and the corresponding output voltage.

Although the Minimus automatically receives calibration parameters from connected digital instruments (e.g. Güralp Radian), calibration values need to be supplied for connected analogue sensors (e.g. Güralp Fortis).

A form to enter such calibration values can be displayed by right-clicking the connected Minimus in Discovery’s main window and selecting “Calibration” → “Calibration Page Editor”. The instrument response values (poles, zeros and gain/sensitivity) can be entered here, using one tab per component:

In the Calibration editor window, as shown above:

The calibration parameters of one component can be copied to other components of the same instrument, or other instruments. This is especially useful for poles and zeros, because they are typically identical for all three components of all instruments in a class. The drop-down menu at the left of the button allows selection of what to copy: poles and zeros, gains or everything. The destination sensor and component(s) can be selected in the subsequent drop-down menus.

The overall system calibration parameters can be exported and saved in a file for future use by clicking on the button. The resulting file-name will have the extension .conf. Values from an existing calibration file can be imported using the button. The associated drop-down menu allows specification of what to import: poles and zeros, gains or everything.

When transmitting MiniSEED data, the responses of the instruments and digitisers are encoded in a message called a “data-less SEED” volume. The contents of these volumes can be displayed in human-readable form, known as RESP, by clicking on the “RESP file” link of each channel in the “Data flow” and “Data record” tab of the Minimus web page. The resulting pages look like this:

5.11 Setting a sensors orientation

A Matlab extension for Scream! allows easy determination of the exact orientation of a sensor relative to a surface reference sensor (which can be installed accurately aligned with the Earth’s magnetic field North).

The complete description of the procedure is explained at the following link http://www.guralp.com/howtos/determining-sensor-orientation.shtml.

The Relative Orientation extension of Scream! provides a correction angle that can be entered into the Sensor Orientation section of the Minimus web page.

This feature can be applied to analogue seismometers and accelerometers and also when either Borehole or Posthole Radian are installed in a vertical orientation.

5.12 Earthquake Early Warning

When the option is enabled, the “Trigger” tab is dedicated to Earthquake Early Warning settings. It is disabled by default because of the amount of processing time that is consumed in these calculations.

It is based on STA/LTA (Short-Time-Average divided by Long-Time-Average) triggering.

The algorithm continuously calculates the average values of the absolute amplitude of a seismic signal in two consecutive moving-time windows. The short time average (STA) is sensitive to seismic events while the long time average (LTA) provides information about the current amplitude of seismic background noise at the site. When the ratio of STA to LTA exceeds a pre-set value (the parameters can be set as highlighted in the picture below), an event is “declared”.

List of parameters:

When a trigger is declared, the system will issue messages to a CAP (Common Alerting Protocol) receiver. For the full specification of this protocol, please refer to http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html.

Various parameters control how the CAP message is created:

The Trigger section enables the user to configure the triggering system. The trigger source should be configured first because different configuration options are displayed for for different source types. Once the source-specific settings are configured, the destination should be specified. Destinations can be shared between sources, allowing the creation of networks (directed graphs) of systems for distributed event detection.

5.12.1 Trigger sources

The available sources are:

5.12.2 Trigger destinations

The options available form the various Destination fields are:

5.12.3 Derived Streams

The various calculated averages used in the triggering algorithm can be displayed as streams in Discovery’s live streaming window. This can be used to help decide appropriate triggering parameters. The available streams are:

Note: Each time an event is detected and the trigger is enabled, the LED on the top of the Minimus flashes blue.

5.12.4 CAP receiver

Güralp Discovery includes a CAP (Common Alerting Protocol) receiver. It listens on a specified UDP port for incoming CAP messages. When one arrives, it is displayed and plotted on a map. In addition, the receiver can open a TCP connection to the cloud-based registry server and display CAP messages that have been sent to the registry server. See section 5.13 for information about configuring a registry server.

All CAP messages are stored in a log-file. The full message is recorded so that it can be re-loaded later, if required.

The CAP receiver functionality is accessed using the context (right-click) menu in Discovery:

The CAP receiver window allows specification of the listening port. Each Minimus from which messages should be received must have this value specified as the “CAP Port” in its triggering settings (see section 5.12.2). The value should be between 1025 and 65535. You should avoid numbers in the list at https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers.

The reception of CAP messages can be enabled or disabled clicking on the button at the top, right-hand side of the window.

If you wish to forward the CAP messages to a server, type its IP address into the field and tick the check-box named “Use forwarding server”. An error message is displayed if the entered IP address is not valid.

To log CAP messages to a file, tick the “Log events” check-box and use the button to select an appropriate location for the database file.

To import an existing database of events, enable logging, browse to the file using the button, then click the button to load the file. If no file is specified, the logging is automatically switched off and a pop-up message is produced.

When an event is detected and a CAP message is received, the location of the Minimus that generated the trigger is displayed on the map with a pointer. The events and the information contained in the CAP message are displayed at the right-hand side of the window. This includes the SEED identifiers, network, station, channel and location, long with the time, the recipients and the threshold value which was exceeded.

Click on the button to clear markers from the map and descriptions from the right-hand-side list. This action does not affect the contents of the log-file.

5.13 Using a registry

Discovery can maintain a list of Minimus digitisers in a local or cloud-based registry, simplifying management of medium to large networks. Registered digitisers appear in the selection list in the main screen, regardless of whether they are on the local network or not.

5.13.1 Setting the registry server

The address of the registry server must be set for all participating digitisers and also for all instances of Discovery.

To set the registry server address for an instance of discovery, type it into the field at the bottom left of the main screen:

Note: The list of digitisers displayed will not change until the button is pressed again.

To set the address of the registry server for a digitiser, right-click () on the digitiser’s entry in the main Discovery list and select “View Web Page” from the context menu:

In the resulting web page, select the “Network” tab. The group ID can be set in the text field in the bottom right of the resulting screen:

The frequency at which the registry is updated with details of this digitiser can also be set on this screen, in the drop-down menu to the left.

Once you have set the correct values, the digitiser must be rebooted for them to take effect. To do this, click the button.

Note: The digitiser will disappear from the list of registered servers until the registry address of the instance of Discovery is changed to match, using the text field on the bottom left of the main screen.

5.13.2 Groups IDs: partitioning networks

Discovery provides the ability to assign group identifiers to registered digitisers. An instance of Discovery can then be configured to only display registered digitisers in a particular group. This allows partitioning of large networks into smaller administrative domains.

Groups do not need to be created before use. To assign a group identifier to a digitiser, right-click () on the digitiser’s entry in the main Discovery list and select “View Web Page” from the context menu:

In the resulting web page, select the “Network” tab. The group ID can be set in the text field in the bottom right of the resulting screen:

5.13.3 Enable the registry

This feature must be enabled before use. To enable the registry:

5.14 Updating Minimus firmware

The firmware of the Minimus is upgradeable. New releases appear regularly – mostly to add new features but, occasionally, to fix problems. Güralp recommends that the Minimus’ is regularly checked for availability of firmware updates and, when convenient, these updates should be installed.

Right-click on the digitiser in Discovery’s main window and select “System Update”. In the “System Update” tab, and in the “System Software” window select “Guralp Server – stable version (online)” to obtain the new firmware from the Internet via Ethernet. Then select “Get from server and update”.

Discovery, may ask to overwrite a temporary file on your PC – click to allow it to do so.

Next, Discovery will confirm through another dialogue box that the file download is complete. Click to begin the firmware upload to the Minimus.

If new firmware is required, the “Uploading System Image” message may appear for several minutes.

At the end of the uploading process, the dialogue box will ask whether to restart the Minimus. Click to finalise the process.

At this point the Minimus will re-boot and, during this process, the yellow light will flicker rapidly between red and green. Once rebooted, the “Uptime” status clock in Discovery will begin to tick.

5.14.1 FPGA Firmware update

The Minimus uses a field-programmable gate array (FPGA) to implement some of its functionality. This has its own firmware, separate from the main firmware.

An image of the FPGA firmware is included in the Minimus firmware, allowing the FPGA to be updated to the version included in the loaded Minimus firmware. To upgrade it to the latest version, first upgrade the Minimus’ main firmware and then follow the instructions below.

Caution: Any interruption during the update can cause a serious malfunction of the Minimus, requiring it to be returned to the factory for reprogramming. We recommend that updates are only performed when requested by Güralp’s support staff.

In Minimus web page, select the “Setup” tab. Ensure that the “FPGA update sensor” drop-down menu at the bottom of the page is set to “Digitiser”. Click on the button to start the updating process.

The first phase is called “Parking”, during which the firmware is written to the module from the most recent version available. A percentage value in brackets shows the status of the process. It takes around 15 minutes to reach the 100%.

The second phase is called “Programming”, it lasts only a few minutes and at this stage the FPGA is actually programmed with the new firmware.

When the procedure is completed the status is marked as “Programming finished”. At this point the Minimus must be manually power-cycled by removing and then, after a minute, reconnecting the power.

Normally the status is “Idle” but, when the Minimus is turned on, it checks if the upgrade went well and if the FPGA is responding to commands. During this operation the status appears as “Busy”.

5.15 Import / Export an existing configuration

Updating the Minimus’ firmware can, occasionally, cause loss of configuration.

To insure against loss of parameter values, including selected channels and sample rates, we recommend that you export and save the current configuration before proceeding with an upgrade.

This operation can be done through Discovery by right-clicking on the digitiser’s entry in the list and select “System Configuration” from the context menu:

Select "Use configuration from one of the devices". If more than one device is available, select the one from which the configuration should be downloaded. Click the button and browse to a suitable location into which to save the configuration file.

After the firmware update is successfully completed, the previous configuration can be imported, if required, by following the instructions below.

Right-click on the digitiser’s entry in the Discovery list and select "System Configuration" from the context menu. Select the "Use configuration from file" option.

Select the configuration file from where it was saved in the File Explorer and confirm. Use the check-boxes to select the devices to which the configuration should be uploaded and click on the button.

Wait until the process finishes. To apply the new configuration, the unit has to be rebooted: the button can be used to perform the required system restarts.

PreviousNext

1. Preliminary Notes 2. System Overview 3. System description 4. Getting started 5. Advanced system configuration 6. GüVü app 7. Advanced troubleshooting 8. Appendix 1 – Instrument/channel names 9. Appendix 2 – Minimus ports 10. Appendix 3 – Güralp Discovery installation 11. Appendix 4 – Connector pin-outs 12. Revision History