Guralp Systems CMG-DCM - Manual (Page 121)

Operator's guide
will ask you if you want to quit without resetting the connection.
Choose yes to return the digitizer to data mode.
8.4 Monitoring
Data flow
You can check that the DCM is receiving data either by monitoring the
Summary page of the on-board Web interface (see Section 4.1, page
51), or from a command prompt using the command gnblocks:
Key 0x007000: Blocks 0 (Port 0, name Data out port,
device /dev/ttySA0, baud 115200)
Key 0x007001: Blocks 0 (Port 1, name Port B, device
/dev/ttySA1, baud 9600)
Key 0x007002: Blocks 149 (Port 2, name Port A, device
/dev/ttySA2, baud 38400)
This command shows, for each port:
•
the Key number (in hexadecimal) of the process on that port
which deals with incoming blocks,
•
the number of blocks received by that process,
•
the internal port number of the port,
•
the name you have assigned to it,
•
the port's Linux device name, and
•
the baud rate currently in operation on the port.
You can query a single port by using the port number or key as
arguments to the gnblocks command:
gnblocks 2
gnblocks 0x7002
gnblocks 28674
(In the last example, 28674 is the key ID 0x7002 expressed in decimal:
hex 7002 = 7 × 16
3
+ 2 = 28674.)
Another way to find out the index, key ID, name or device name of a
particular serial port is to issue the command serialmap. A line will
be output for each serial port, in the form
Port 0, Key 7000, name tts0, device /dev/ttyS0, baud 115200
December 2006 121