Minicom Advanced Systems CMG-DCM manual Inside the DCM

Page 82

CMG-DCM

6 Inside the DCM

The DCM is a fully-functional, Linux-based computer system especially designed for handling seismic data. It can collect and store data from several sources and, if required, output it in your preferred format to other locations on your network or on the Internet. This is done in the following manner.

Firstly, the DCM receives some data from an instrument connected to it. This can be any of

a digitizer connected through a serial link,

a computer running a Scream! server,

a CD1.0 or CD1.1 transmitter (optionally), or

another DCM or AM.

All the received data is stored in files in the on-board Flash memory. There are two banks of Flash memory available, which are accessible as /nand0 and /nand1 in the Linux file tree. Data is normally stored as GCF (Gü ralp Compressed Format) files.

As an option, you may be able to configure the DCM to use the miniSEED or sac formats instead (see Section 4.2, “Disk”)

In automatic mode, when the Flash memory becomes more than 75% full, the oldest data files are moved to the DCM's primary hard disk until it is less than 50% full. If you prefer, you can configure the DCM to write to the hard disk at set intervals (see Section 4.2, “Disk”.)

Writing to the hard disk is performed robustly, so that no data will be lost if a write is aborted (see Section 6.1, “File systems”.) This means that you can safely swap hardware in and out at any time. Stand-alone DCM modules use off-the-shelf Lacie hard disks, which can be easily removed and installed in most conditions. You can specify other models of IDE / USB or IEEE 1394 2.5” disk at manufacture. If an internal disk is not present, and the module has a USB host interface, it will look for hard disks connected to its external USB port.

82

Issue A

Image 82
Contents CMG-DCM Table of Contents December Inside the DCM Introduction CMG-DCM Inside the DCM Serial port services Network servicesSee .4, Connecting to a local network for full details Power supply Installing the CMG-DCMOverview Connecting to a single computer Connecting over a serial linkConnecting over Ethernet 192.168.0.xUsing an internal modem Connecting over USBConnecting to a local network Gcfgdbset option-namenew-value Wi-Fi Connecting to the InternetConnecting digitizers and external hardware Setting up the CMG-DCMWeb setup Setting up digitizers Using Scream General notes UsageDCM 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 connect to the DCMs Scream! server Cannot see the DCMs Web site over Http or HttpsCannot Gcfping the DCMs Scream! server Can Gcfping the DCMs Scream! server, but no data appears DCM is not receiving any data streamsUse the Serial port configuration → port name Web page, or DCM is receiving streams, but they do not contain any data143032 up 34 min, load average 1.24, 1.32 Configuration options GeneralDisk CMG-DCM Serial port configuration CMG-DCM Page Network configuration Ethernet portStatic routes DNS setup Incoming mail setup Outgoing mail setup Remote access Administrators PPP Mgetty Data transfer ScreamScream! Client AutoDRMHttp client Http serverCD1.0 CD1.1 CD1.1 subframe configuration DSS Server configuration Seed Page CMG-DCM Actions Data ViewerIcon bar Stream listDigitizer Setup General digitizer settings Digitizer output control CMG-DCM Trigger criteria CMG-DCM Tap # Rate Bandwidth Samples/s Auxiliary Mux channels Sensor mass control Check disk filesystem Disk toolsPartition, and format disk Flush flashCamera Disk filesRecent Log Entries Network configuration SummaryDNS configuration Data Out Port, Serial Port A, Serial Port BTamper lines Flash StatusDisk Status Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Monitoring Data flowDigitizer status Tamper lines From the hard disk Updating the DCMOver the Internet Removing support packagesFirmware Libgconfigdb Port a and B Appendix a Connector pinoutsAppendix A.1 Modular DCM units Data OUT portUSB connector Network connectorAppendix A.2 Integrated DCM units DM/AM module outputAppendix B Sensor and digitizer types Appendix B.1 Sensor response codesAppendix B.2 Digitizer type codes Digitizer