Minicom Advanced Systems CMG-DCM manual 143032 up 34 min, load average 1.24, 1.32

Page 39

Operator's guide

The DCM receives streams, but gaps appear in the data some minutes after boot-up.

Check that the baud rate between the digitizer and the DCM is sufficient for all the data streams you want to transmit. If it is not, the digitizer's output buffer will gradually fill up until no more data can be stored. Increase the baud rate of the digitizer through the DCM (or using Scream!), then set the baud rate of the DCM's input port to the same value.

If you are using triggered output streams, be especially careful to allow a high enough baud rate to transmit data from all possible output streams simultaneously, or you will observe gaps when an event triggers the digitizer.

The DCM receives streams, but 2-minute gaps appear in the data at 4-hour intervals.

After a reboot, the DCM takes around 2 minutes to begin transmitting. The DCM runs a guardian process which monitors the health of the system. In some circumstances guardian will need to reboot the DCM to attempt to resolve a problem. If the reboot does not help, the DCM will soon find itself in the same position, and guardian will reboot it again.

You can check the time since the last reboot with the command uptime, which will respond with a line like

14:30:32 up 34 min, load average: 1.24, 1.32, 1.10

In this example, the DCM last rebooted 34 minutes ago.

The most common circumstance where guardian will reboot a DCM is when the operator has instructed it to record data, but it cannot do so, either because

•

•

•

the Flash memory is full, and all connected USB disks are also full,

the Flash memory is full, and no USB disk is present; or

the Flash memory is full, and a USB disk is inaccessible for some other reason (e.g. it is unformatted, incorrectly partitioned, or faulty).

December 2005

39

Image 39

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 Flush flash Disk toolsPartition, and format disk Check disk filesystemDisk 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 Removing support packages Updating the DCMOver the Internet From the hard diskFirmware Libgconfigdb Data OUT port Appendix a Connector pinoutsAppendix A.1 Modular DCM units Port a and BNetwork 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