Open main menu
SUPPORT DOCUMENTATION

Minimus Demonstration

This document describes how to access an online demonstration system consisting of a Fortimus accelerometer, a Minimus digitiser and a Minimus+ digitiser. To complete the configuration, the user will need to know the Internet Address of the "station" and a registry group identifier, both of which will have been provided by your Customer Relationship Manager.

In order to mimic a real station, the three devices are connected to the Internet via a router which implements NATNAT stands for Network Address Translation, which is a mechanism for allowing access from the public Internet to a number of devices on a private network without exposing their individual addresses. . This means that some additional configuration work is required.

Install Discovery

At the time of writing, it is necessary to use a beta version of Discovery in order to fully access the demonstration digitisers. These installation instructions should be followed whether or not you already have discovery installed on your PC.

For this reason, the demonstration can currently only run on PCs and laptops running Microsoft Windows.

Download the discovery installer from the discovery download page, save it to a suitable location on your PC and then run it by double-clicking on it. Installation is straightforward but you can refer to the detailed instructions in §4.2 of the Minimus manual if you require guidance.

Configure Discovery

The Discovery installer will have offered to start the program for you. If you declined, start the program now by double-clicking its icon. The initial screen is displayed. Start by selecting _Settings from the _File menu:

The application configuration screen is displayed. Enter your Cloud registry group identifier into the text-field provided. The ID DEMO has been used in the illustration below: yours will be different.

Click the 'Apply' button to continue.

Check that the IP address of the Registry server is 52.34.40.123 as shown below and then click the 'Registry' button to put Discovery into registry mode.

The three systems shown below should appear within a few seconds.

The WAN addresses have been deliberately obscured in these illustrations.

The WAN addresses will be the same for all three systems: this is the address of the router. The router has been configured to pass incoming connections to the individual digitisers using port-forwarding rulesA port-forwarding rule configures the router so that an external, incoming connection to port aaaa will get forwarded to port bbbb on a specified internal system. Many such rules can be in place simultaneously. See this Wikipedia article for more information.. Discovery cannot currently communicate with the digitisers because it does not know which ports to use. Our next task is to configure Discovery with the correct ports for each of the digitisers.

Right-click on the system labelled Demo 1 and select Device port configuration from the context menu:

The following dialogue appears:

Fill in the fields as shown:

FieldValue
HTTP server10080
GDI transmission protocol11565
GCF transmission protocol11567
File exchange protocol14242
Remote console14244
Remote procedure calls11788

and then click the 'Apply' button. A confirmation screen appears:

Click the 'OK' button to close the confirmation and then the 'close' button to dismiss the dialogue.

Repeat this process for the other two systems, using the values from the table below:

FieldValue for Demo 2Value for Demo 3
HTTP server2008030080
GDI transmission protocol2156531565
GCF transmission protocol2156731567
File exchange protocol2424234242
Remote console2424434244
Remote procedure calls2178831788

This completes the configuration of Discovery. You can now, for example:

For more information, please see the Minimus manual, MAN-MIN-0001.

Scream configuration

You should have a copy of the standard Scream download instructions. If not, please send an email to scream.guralp.com giving your name, your institutional affiliation, the equipment with which you are working and an idea of the sort of work you will be doing. The rest of this section assumes that Scream is already installed.

Start Scream and open the Network Control dialogue by keying Ctrl + N. When the Network Control window opens, select the My Client tab and right-click in the Servers list. Select Add TCP Server... from the context menu:

Enter the Internet Address of the "station", followed by a colon (:) and the port number 11567, as shown:

Click the 'OK' button to proceed.

Repeat this process to add another two servers. All three use the same Internet address but the port numbers of the second and third are 21567 and 31567.

Once all three have been added, right-click on the first and select _Connect from the context menu:

Repeat this process to connect the second and third systems:

Data should start appearing within a few seconds and the source tree will be populated. Note that channels with slow sample rates will not appear for some time - this will be many minutes for those with the slowest rates.

You can now proceed to use Scream to monitor, analyse and save your data in many different formats. For more information, please see the Scream manual, MAN-SWA-0001.

MiniSEED data via SEEDlink

Many different packages can receive data in MiniSEEDMiniSEED is a subset of the industry-standard SEED format for seismic data, as defined by IRIS. See IRIS's miniSEED page for more details. format using the SEEDlinkSEEDlink is the standard transport protocol for MiniSEED data. For more information, see IRIS's SEEDlink page. protocol. Each has its own different method of configuration so discussion of such is beyond the scope of this document. As a demonstration, however, we will show how to use slinktool to read data from the demonstration systems. The source for slinktool program can be downloaded for free from the IRIS website.

To retrieve a list of available streams from the first demonstration systems, use slinktool with the -Q flag, followed by the Internet Address of the "station", a colon (:) and the port number 18000, as shown below. The examples use 192.0.2.1 where you should enter the address which you have been given.

$ slinktool -Q 192.0.2.1:18000 DG TEST2 00 HCA D 2020-10-09 03:18:51 - 2020-10-09 16:00:20 DG TEST2 00 HNZ D 2020-10-09 03:18:51 - 2020-10-09 16:00:21 DG TEST2 00 MNZ D 2020-10-09 03:18:24 - 2020-10-09 16:00:03 DG TEST2 00 HNN D 2020-10-09 03:18:49 - 2020-10-09 16:00:22 DG TEST2 00 MNN D 2020-10-09 03:18:26 - 2020-10-09 15:57:53 DG TEST2 00 HNE D 2020-10-09 03:18:48 - 2020-10-09 16:00:22 DG TEST2 00 MNE D 2020-10-09 03:18:29 - 2020-10-09 15:57:53 DG TEST2 99 BYV D 2020-10-09 03:18:19 - 2020-10-09 16:00:12 DG TEST2 99 BYP D 2020-10-09 03:18:23 - 2020-10-09 15:59:15 DG TEST2 99 BIO D 2020-10-09 03:18:47 - 2020-10-09 16:00:00 DG TEST2 99 BKO D 2020-10-09 03:18:13 - 2020-10-09 16:00:12 DG TEST2 00 SOH D 2020-10-09 03:15:49 - 2020-10-09 15:55:49

To retrieve the corresponding lists from the other two systems, use the port numbers 28000 and 38000:

$ slinktool -Q 192.0.2.1:28000 DG TEST1 00 HDF D 2020-10-09 09:53:07 - 2020-10-09 16:04:09 DG TEST1 00 HHZ D 2020-10-09 09:53:07 - 2020-10-09 16:04:09 DG TEST1 00 MHZ D 2020-10-09 09:51:38 - 2020-10-09 16:01:44 DG TEST1 00 HHN D 2020-10-09 09:53:05 - 2020-10-09 16:04:09 DG TEST1 00 MHN D 2020-10-09 09:51:18 - 2020-10-09 16:01:36 DG TEST1 00 HHE D 2020-10-09 09:53:07 - 2020-10-09 16:04:09 DG TEST1 00 MHE D 2020-10-09 09:51:37 - 2020-10-09 16:01:44 DG TEST1 00 LMZ D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 00 LMN D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 00 LME D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 01 HDF D 2020-10-09 09:53:06 - 2020-10-09 16:04:10 DG TEST1 01 HHZ D 2020-10-09 09:53:05 - 2020-10-09 16:04:10 DG TEST1 01 MHZ D 2020-10-09 09:50:31 - 2020-10-09 16:01:43 DG TEST1 01 HHN D 2020-10-09 09:53:05 - 2020-10-09 16:04:11 DG TEST1 01 MHN D 2020-10-09 09:51:11 - 2020-10-09 16:03:23 DG TEST1 01 HHE D 2020-10-09 09:53:04 - 2020-10-09 16:04:09 DG TEST1 01 MHE D 2020-10-09 09:51:30 - 2020-10-09 16:02:09 DG TEST1 01 LMZ D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 01 LMN D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 01 LME D 2020-10-09 09:49:16 - 2020-10-09 16:01:47 DG TEST1 99 BYV D 2020-10-09 09:52:13 - 2020-10-09 16:03:37 DG TEST1 99 BIO D 2020-10-09 09:52:47 - 2020-10-09 16:03:30 DG TEST1 99 BKO D 2020-10-09 09:52:37 - 2020-10-09 16:03:23 DG TEST1 00 SOH D 2020-10-09 09:50:12 - 2020-10-09 16:00:12

and for the third system...

$ slinktool -Q 192.0.2.1:38000 DG TEST 00 HDF D 2020-10-09 05:27:36 - 2020-10-09 16:04:20 DG TEST 00 HHZ D 2020-10-09 05:27:37 - 2020-10-09 16:04:18 DG TEST 00 MHZ D 2020-10-09 05:25:31 - 2020-10-09 16:01:28 DG TEST 00 HHN D 2020-10-09 05:27:39 - 2020-10-09 16:04:19 DG TEST 00 MHN D 2020-10-09 05:25:41 - 2020-10-09 16:02:31 DG TEST 00 HHE D 2020-10-09 05:27:36 - 2020-10-09 16:04:18 DG TEST 00 MHE D 2020-10-09 05:26:00 - 2020-10-09 16:02:19 DG TEST 00 LMZ D 2020-10-09 05:25:22 - 2020-10-09 16:02:15 DG TEST 00 LMN D 2020-10-09 05:25:22 - 2020-10-09 16:02:15 DG TEST 00 LME D 2020-10-09 05:25:22 - 2020-10-09 16:02:15 DG TEST 99 MYY D 2017-01-01 03:00:00 - 2017-01-01 03:00:00 DG TEST 99 MYP D 2017-01-01 03:00:00 - 2017-01-01 03:00:00 DG TEST 99 MYR D 2017-01-01 03:00:00 - 2017-01-01 03:00:00 DG TEST 99 BYV D 2020-10-09 05:26:27 - 2020-10-09 16:03:14 DG TEST 99 BIO D 2020-10-09 05:27:15 - 2020-10-09 16:03:57 DG TEST 99 BKO D 2020-10-09 05:26:32 - 2020-10-09 16:04:04 DG TEST 00 SOH D 2020-10-09 05:25:38 - 2020-10-09 16:00:38

In a similar manner, the same port numbers can be used to access other slinktool functions. The final example shows the headers of incoming packets from one channel from the third demonstration system being listed in real time:

$ slinktool -p -S DG_TEST:HHZ 192.0.2.1:38000 DG_TEST_00_HHZ, 315 samples, 200 Hz, 2020,283,16:14:05.470000 (latency ~3.1 sec) DG_TEST_00_HHZ, 311 samples, 200 Hz, 2020,283,16:14:07.045000 (latency ~3.1 sec) DG_TEST_00_HHZ, 323 samples, 200 Hz, 2020,283,16:14:08.600000 (latency ~3.0 sec) DG_TEST_00_HHZ, 316 samples, 200 Hz, 2020,283,16:14:10.215000 (latency ~2.9 sec) DG_TEST_00_HHZ, 323 samples, 200 Hz, 2020,283,16:14:11.795000 (latency ~2.8 sec) DG_TEST_00_HHZ, 313 samples, 200 Hz, 2020,283,16:14:13.410000 (latency ~2.8 sec) DG_TEST_00_HHZ, 326 samples, 200 Hz, 2020,283,16:14:14.975000 (latency ~2.7 sec) . . .