Minicom Advanced Systems CMG-DCM manual

Page 45

Operator's guide

command pppd to establish these links. pppd is a versatile program, which uses command-line options to specify the type of PPP link required. These options are fully described in the Linux documentation for pppd.

The serial.x.ppp box allows you to specify pppd options to use on this serial port. Options which you wish to apply to all serial ports running the ppp service should be placed in the /etc/ppp/options file (see “options” in Section 4.4.)

serial.x.service : How the DCM will use each serial port. There are five options:

•getty : The module will use this port to listen for logins from a connected computer. Once logged in, the user will have direct command-line access to the DCM's Linux operating system.

•mgetty : The module will use this port to listen for logins over a connected serial modem. Again, a logged-in user will be presented with the DCM's Linux command line.

•mgetty-r : The module will use this port to listen for logins over a connected serial modem which is operating in raw mode (i.e. which does

not support the standard AT modem commands.) This option in runs the Linux command mgetty -r. A port running the mgetty-rservice will also listen for incoming PPP frames, and if it detects one will configure

the PPP link according to the /etc/mgetty+sendfax/login.config file (see “login.config” in Section 4.4.)

•

•

•

ppp: The module will use this port to provide a PPP link to a connected computer. Once set up on the computer, the DCM will appear as if on a local TCP/IP network. You can then log in to it using ssh or use its Web-based administration system, as well as receiving data.

Before a PPP link will function, you will need to specify the PPP options and (if using CHAP) provide a chap-secretsfile. This can be done through the DCM configuration interface: see “options” in Section 4.4

and “chap-secrets” in Section 4.4. Also see the Linux manual page for pppd(8) for an explanation of how PPP is implemented.

gcf_in : The module will use this port to communicate with a GCF- compatible digitizer.

gcf_out : The module will use this port to send GCF data directly to the connected device as it is received. A number of programs are available for PCs which handle incoming GCF data streams, such as Scream!, Antelope, and Earthworm. The DCM transparently merges all incoming data streams, so if you are using Scream!, you can also configure and

December 2005

45

Page 44 Page 46
Image 45
Page 44 Page 46
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 Partition, and format disk Disk toolsCheck disk filesystem Flush flashDisk 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 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
Top Page Image Contents