Minicom Advanced Systems CMG-DCM manual Cmg-Dcm

Page 84

CMG-DCM

Once the operating system is loaded, the main Flash memory blocks (where present) are mounted on /nand0 and /nand1. Incoming data, which may be from several sources, is combined into a single stream and placed in one of

these blocks (whichever is less full). When in use, you can expect each to be between 50% and 75% full, with several da:ta files present. If the DCM is using GCF as its storage file format (recommended; see Section 4.2, “Disk”), then each file will be named after the timestamp on its first packet of data, in the following fashion:

file-yyyymmdd-jjj-s-cccccccc.gcf where yyyymmdd represents the date of the earliest data packet in the file, jjj the number of full days elapsed since midnight on January 1, s the time segment within the day (each day is divided into eight 3-hour segments), and cccccccc a unique hexadecimal code included to ensure filenames do not coincide.

When one of the Flash memory blocks approaches capacity, or after a fixed time period (if you have so configured it; see Section 4.2, “Disk”) the DCM will automatically move them onto the primary USB hard disk. This may be either an internal Lacie hard disk, or an external drive connected to the module through a USB client interface. This disk uses a specially-designed journalled filesystem, which is designed to maintain the integrity of your data at all times. Even if a write operation fails or is aborted suddenly, the disk will still contain a valid filesystem with all previously-saved data intact, which can be read using any driver that supports FAT32.

There is a set of specialised commands which allow you to perform basic tasks on this filesystem:

gfat32df : Displays the size of the filesystem, and how much free space remains, in a format similar to this:

FAT32 filesystem has 15 G bytes free

Partition is 37 G bytes (78140097 blocks of 512 bytes)

If no suitable storage medium can be found, you will see the message Failed to find a USB disk.

diskman : Ensures that the /nandx partitions do not become full by moving files when necessary. This program ordinarily runs constantly in the background. However, a user can use the command diskman -fto force the Flash memory to be entirely copied to the USB disk. Typing diskman -fis identical to clicking the Flush flash button on the Disk tools page (see “Flush

flash” in Section 5.3). It does not remove data from the Flash memory. If you issue diskman -fand then swap hard disks, the data remaining in memory will later be written out to the new hard disk, causing some overlap between it

and the old disk.

84

Issue A

Page 83 Page 85
Image 84
Page 83 Page 85
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 Installing the CMG-DCM Power supplyOverview 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 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 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 server Http clientCD1.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 Disk tools Partition, and format diskCheck disk filesystem Flush flashDisk files CameraRecent Log Entries Network configuration SummaryDNS configuration Data Out Port, Serial Port A, Serial Port BFlash Status Tamper linesDisk Status 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