Guralp Systems CMG-DCM build <10,000 User Manual
Page 184
Acquisition Modules and Platinum Firmware
Transmitting Data
12.2.2 The SEEDlink server
The SEEDlink server transmits data in miniSEED format (i.e. no
station/channel metadata) over the network to remote data consumers. The
data are generated by a GDI Mini-SEED compressor instance.
Note: The SEEDlink server requires data in 512 byte blocks - the
compressor must be reconfigured from its default setting (4 Kbytes)
if the SEEDlink server is to be used: see the previous section for
details.
The system will prevent you from configuring a SEEDlink server
unless the chosen compressor is set to prepare 512-byte blocks. The
system does not stop you from subsequently reconfiguring the
compressor but, if you change the block size, the SEEDlink server
will fail.
If you want to write miniSEED data with a block-size other than 512
bytes and run a SEEDlink server, you should instantiate different
compressors for each.
A single SEEDlink server instance takes data from a single compressor
instance and can serve multiple, simultaneous clients. If it is required to
serve different channels to different clients, multiple server instances should
be configured, each receiving data from a different compressor instance (the
channel selection is controlled by the compressor, not the server). A server
has a configured “Organization” name: if data are to appear to come from
multiple organizations, multiple server instances should be configured: they
can share a compressor instance if they will be serving the same channels or a
number of compressor instances can be used.
To configure a SEEDlink server from the web interface, select:
Data transfer/recording → Services
or
Configuration → All options → System services
To configure a SEEDlink server from the command line, start gconfig and
select “System services” from the top level menu.
Now select “seedlink-out -- SEEDlink network server” from the System
Services menu. The next screen shows a list of all SEEDlink server instances
that have been configured:
184
Issue E - February 2014