Minicom Advanced Systems CMG-DCM manual File systems

Page 83

Operator's guide

Once the data is stored on the DCM, whether in Flash memory or on the hard disk, it can be retrieved

•by a remote computer running Gü ralp Systems' Scream!, or other GCF- compatible software;

•by another DCM or AM, also using GCF;

•by setting up a CD1.0 or CD1.1 transmitter on the DCM;

•by direct file transfer (using SSH, HTTP, HTTPS, etc.,)

•optionally, by requesting the data using SeedLink or AutoDRM.

A PC running Gü ralp Systems' Scream! software can not only collect data from the DCM, but also configure the module and any instruments attached to it.

You may need to enable and configure some of these methods before you can use them: see Chapter 4, “Configuration options” for more details.

Most installations of the DCM will not require any more complex setting up than the Web configuration system can offer. However, in some cases you may need to take advantage of the flexibility offered by the underlying Linux operating system.

6.1 File systems

The DCM uses the standard Unix/Linux file naming conventions. The operating system resides in two blocks of Flash memory, mounted on / and /boot; when the module is powered up, a separate boot loader loads the rest of the operating system.

December 2005

83

Image 83

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 Flush flash Disk toolsPartition, and format disk Check disk filesystemRecent 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 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