Minicom Advanced Systems CMG-DCM manual Real-time data transmission

Page 33

Operator's guide

Click Save changes to save the configuration and start writing SEED volumes. One volume will be written for each stream every three hours. The DCM will always start a new volume if it is power cycled; the aborted file will still be a valid SEED volume.

Real-time data transmission

You can use the DATA OUT port (or any of the DCM's serial ports) in several ways, depending on the service you have chosen to run on the port.

By default, the DATA OUT port runs the getty service, which allows you to connect to the DCM's console.

The mgetty and mgetty_raw services are similar, but can deal with connections made through modems.

The gcf_out service causes the DCM to combine the incoming GCF streams and send them on transparently, as for a Gü ralp SAM or CRM.

The gcf_in service turns the port into an extra digital data input port. The DCM's PORT A and PORT B run the gcf_in service.

Scream! server

In a straightforward vault installation, we recommend that you leave the DATA OUT port running the getty service for emergency console access, and instruct the DCM to act as a server for incoming data on your network. This can be done from the Data transfer Scream! Server page on the Web site:

1. Enable the Scream! server on the DCM by setting

datatransfer.scream.servertoonand datatransfer.scream.server.allowserialaccess to yes. Make a note of the port number datatransfer.scream.server.port, or change it to another. Click Save settings.

2.Start up Scream!, and select Windows Network Control... from the main menu. Click the My Client tab.

3.If it is not already selected, check Receive Data to start Scream! listening.

4.Right-click anywhere in the Servers list box, and select Add UDP Server.... Enter the IP address and port number of the DCM, separated by a colon : (e.g. 192.168.0.2:12345)

5.Test communications by right-clicking on the newly-added server, and selecting GCFPING. A message appears in the Control pane logging the ping being sent. If communication is good, and the server is enabled

December 2005

33

Image 33
Contents CMG-DCM Table of Contents December Inside the DCM Introduction CMG-DCM Inside the DCM Network services Serial port servicesSee .4, Connecting to a local network for full details Installing the CMG-DCM Power supplyOverview Connecting over a serial link Connecting to a single computer192.168.0.x Connecting over EthernetConnecting over USB Using an internal modemConnecting to a local network Gcfgdbset option-namenew-value Connecting to the Internet Wi-FiSetting up the CMG-DCM Connecting digitizers and external hardwareWeb setup Setting up digitizers Using Scream Usage General notesDCM as a data store Gnblocks port-number Page CMG-DCM DCM as a GCF data source Accessing the DCM command line through gcfout Sensor arrays DCM as a network data hub Communicating with digitizers Configuring digitizers Data storage and retrieval Using miniSEED format Real-time data transmission CD1.0 and CD1.1 Troubleshooting DCM installations Cannot see the DCMs Web site over Http or Https Cannot connect to the DCMs Scream! serverCannot Gcfping the DCMs Scream! server DCM is not receiving any data streams Can Gcfping the DCMs Scream! server, but no data appearsDCM is receiving streams, but they do not contain any data Use the Serial port configuration → port name Web page, or143032 up 34 min, load average 1.24, 1.32 General Configuration optionsDisk CMG-DCM Serial port configuration CMG-DCM Page Ethernet port Network configurationStatic routes DNS setup Incoming mail setup Outgoing mail setup Remote access Administrators PPP Mgetty Scream Data transferAutoDRM Scream! ClientHttp server Http clientCD1.0 CD1.1 CD1.1 subframe configuration DSS Server configuration Seed Page CMG-DCM Data Viewer ActionsStream list Icon barDigitizer Setup General digitizer settings Digitizer output control CMG-DCM Trigger criteria CMG-DCM Tap # Rate Bandwidth Samples/s Auxiliary Mux channels Sensor mass control Partition, and format disk Disk toolsCheck disk filesystem Flush flashDisk files CameraRecent Log Entries Summary Network configurationData Out Port, Serial Port A, Serial Port B DNS configurationFlash Status Tamper linesDisk Status Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Data flow MonitoringDigitizer status Tamper lines Over the Internet Updating the DCMFrom the hard disk Removing support packagesFirmware Libgconfigdb Appendix A.1 Modular DCM units Appendix a Connector pinoutsPort a and B Data OUT portNetwork connector USB connectorDM/AM module output Appendix A.2 Integrated DCM unitsAppendix B.1 Sensor response codes Appendix B Sensor and digitizer typesDigitizer Appendix B.2 Digitizer type codes