Minicom Advanced Systems CMG-DCM manual Scream! Client, AutoDRM

Page 56

CMG-DCM

datatransfer.scream.server.port : The network port number which Scream! should use to connect to the DCM. You can use any port which neither the PC nor the DCM is using for other purposes. See your Scream! configuration for the current port setting; the default is 1567.

datatransfer.scream.sampleratelimit : The fastest sample rate allowed for transmission over this connection. Using this option, you can prevent high-rate streams from being transmitted to Scream!, whilst allowing them to be transmitted by other means (e.g. CD1.1, etc.) Setting this option to zero will filter out all data streams but preserve status channels, allowing you to use Scream! to monitor the status of your instrumentation whilst minimizing the bandwidth used.

Scream! Client

datatransfer.scream.client : The DCM also has the ability to act as a Scream! client, i.e. to retrieve data from another Scream!-compatible instrument or server on your network. This data is treated as if it came directly from an attached digitizer, and will be collected on the hard disk or sent out across the network according to the module's configuration. If you wish to be able to do this, select on.

datatransfer.scream.client.port : The network port number which the DCM should use to connect to the remote Scream! server. You can use any port which neither device is using for other purposes. The default is 1567.

datatransfer.scream.client.server : The IP address or hostname of the Scream! server from which you wish the DCM to gather data.

AutoDRM

AutoDRM is an automated system for handling requests for seismic data over e- mail, and for fulfilling those requests either by returning e-mails or by establishing an FTP connnection. In order for the AutoDRM system to work, the module must be able to send and receive e-mail messages: this can be configured using the Incoming and Outgoing mail setup configuration pages. See “Incoming mail setup” in Section 4.4 for more details.

The DCM's AutoDRM capabilities are compatible with the GSE2.0 and 2.1 message standards developed for GSE-EISMS and GSETT-3.

datatransfer.autodrm : Select on to enable the DCM to handle AutoDRM requests.

datatransfer.autodrm.maxpoolsize : The maximum pool size to use whilst processing AutoDRM requests, in megabytes.

56

Issue A

Page 55 Page 57
Image 56
Page 55 Page 57
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 Overview Installing the CMG-DCMPower supply 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 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 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 AutoDRMCD1.0 Http serverHttp client 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 Disk tools Partition, and format diskCheck disk filesystem Flush flashRecent Log Entries Disk filesCamera Network configuration SummaryDNS configuration Data Out Port, Serial Port A, Serial Port BDisk Status Flash StatusTamper lines Software Versions Inside the DCM File systems CMG-DCM Command line tools Configuration Digitizer console access Monitoring Data flowDigitizer status Tamper lines Updating the DCM Over the InternetFrom the hard disk Removing support packagesFirmware Libgconfigdb Appendix a Connector pinouts Appendix A.1 Modular DCM unitsPort a and B 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
Top Page Image Contents