Minicom Advanced Systems CMG-DCM manual Introduction

Page 5

Operator's guide

1 Introduction

The CMG-DCM is a versatile Linux-based module for storing and transmitting data captured using Gü ralp Systems Limited's range of seismic measuring equipment. Data can be gathered from up to three digitizers compatible with the Gü ralp Compressed Format (such as the Gü ralp CMG-DM24), and stored in its on-board Flash memory, from where it is written from time to time to a USB hard disk or to another device on your network. Once data is on the hard disk, you can connect to the DCM by various means to retrieve it.

Depending on your site requirements, the DCM may be supplied in several formats. Although these look different, they all share the same internal features.

•A stand-aloneDCM, housed in a high-impact copolymer polypropylene case, may be connected to a digitizer through mil-spec connector cables and installed in a ground station or other location remote from the digitizer and seismometer. The stand-alone DCM can accept data from up to three devices connected to it through RS232 ports.

Stand-alone DCM units are normally supplied with high-capacity removable USB/FireWire disks for data storage. These disks allow the DCM to be used as part of completely autonomous installation in cases where communications links are poor or non-existent.

December 2005

5

Image 5

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 Overview Installing the CMG-DCMPower supply 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 DCM as a data store UsageGeneral notes 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 Gcfping the DCMs Scream! server Cannot see the DCMs Web site over Http or HttpsCannot connect to 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! ClientCD1.0 Http serverHttp client 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 flashRecent Log Entries Disk filesCamera Summary Network configurationData Out Port, Serial Port A, Serial Port B DNS configurationDisk Status Flash StatusTamper lines 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