MET LOGR53 Commands - NTAS with CompactFLASH and Iridium Support

file: logr_newlgr53_cf_cmnd.html
20 May 2013

NTAS MET LOGR53 Commands - Firmware Ver 4.xx with CompactFLASH and Iridium Support

See LOGR53 with CFLASH OPERATIONS document for instructions on how to hook up the comms link to your PC.
Refer to Latest Version Information for reference info on latest firmware version numbers.

MET Logger always comes up running and logging in fixed configuration - see 'default' config below.

CFLASH NOTE 1 - Firmware Ver 4.xx has been tested using SanDisk CompactFLASH cards (256 MB and 64 MB) with SanDisk CompactFLASH PC Card (PCMCIA) Adapters on WHOI VMLOGR53 Rev D CPU boards.

CFLASH NOTE 2 - CompactFLASH cards MUST be formatted using the I command choice in the FOK command menu. CompactFLASH cards may be read on a PC and will contain 2 files: a .INF user-defined Info file, and a .DAT Data file. Processing of the new .DAT file is identical to processing the data files from older PCMCIA-based loggers, since the data file record format is unchanged.

NOTE for loggers with ATTACHED REMOTE COMMUNICATION CAPABILITY: ALWAYS verify that the Comms system is operating correctly before final deployment. For the first 60 minutes after powerup, the logger can be STOPped by an incorrectly programmed Comms system. After the first 60 minutes, and IF Comms system power is controlled by the logger, no STOP command will be accepted by the logger while Comms system power is ON. This offers some protection from accidently disabling the logger remotely. Of course, if Comms system power is independent of logger control, be very careful!

ASIMET Module port assignments

(Port 1 thru Port 11 correspond to LOGRIF PC Board P1 thru P11)

Port 1 - BPR
Port 2 - HRH
Port 3 - LWR
Port 4 - PRC
Port 5 - not used
Port 6 - SWR
Port 7 - not used
Port 8 - WND
Port 9 - GPS power control
Port 10 - SeaCat SBE37 w/RS485
Port 11 - Seimac PTT
Port 12 - Comms Controller (Iridium) Power Control

Command Descriptions

- ALL COMMANDS ARE TERMINATED IN CARRIAGE RETURN <cr> - don't forget! It's assumed for all commands below

- Remember: Modified address mode only - PRECEDE ALL COMMANDS WITH # (full address not used)
- NOTE: The FULL command set is ONLY available when the LOGR53 is NOT running (see STOP command).

A to echo "address\r\n" - artifact of IMET, simple confirmation of 'life'
- NOTE: address is NOT USED currently, but may be set/modified by UOK command below.
CCOxxx to overide the Comms Controller ON time value set by UOK. Values from 1 to 240 (minutes) may be set. A typical default value in EEPROM is 10 minutes. The CCOxxx command can make that longer (or shorter), allowing the Comms Controller to determine how long it can run to do its tasks. This command echoes the xxx value sent if valid. There is no response otherwise. NOTE: After a logging system coldstart (initial powerup), this command may not be issued for 60 minutes; since 30 minutes is the MAX duration (ON time) that may be set in EEPROM, this insures at least one power-on reset of the Comms Controller before normal operations proceed.
CCSTAT displays the following values related to Comms Controller operation:
- Interval from EEPROM - the time in hours (1-96) from one Comms Controller power ON to the next. Set under UOK with the CCI command.
- Duration from EEPROM - the time in minutes (1-30) that Comms Controller power is ON at each interval. Set under UOK with the CCD command.
- Current Interval Time Remaining - the time in minutes remaining until the end of the interval, when the next Comms Controller ON time will occur.
- Current Duration Time Remaining - the time in minutes remaining until Comms Controller power is turned OFF.
- Coldstart Status - set to 1 during the the coldstart period (60 minutes from logger powerup) as explained in the CCO command above. Changes to 0 (zero) after the 1st hour.
Example response, 4 hour interval, 10 minute duration, 30 minutes before ON time: "4,10,30,0,0\r\n"
CCSHDN kills power to the Comms Controller after a 2 second delay. May be issued by the Comms Controller to turn itself OFF.
Responds with "CommsCtrlr Power OFF\r\n"
CLOCK to see current date/time setting. Responds with "yyyy/mm/dd hh:mm:ss\r\n"
CLOCK=yyyy/mm/dd hh:mm:ss to set date/time; Sampling MUST be STOPPED to set the clock.
D responds with a single line of data (subset of full logged data) from most recent sample interval;
each line is terminated with \r\n
Firmware Ver 4.11cf displays:
- BP (mbar)
- RH (%), RH Temp (degC)
- LWR Flux (w/m^2)
- PRC Level (mm)
- Sea Temp (degC) & Conductivity (Seimens/meter)
- SWR (w/m^2)
- We, Wn (m/sec)
- Bat1, Bat2 (NOT USED in any version)
- ```
typical response:

1012.32   72.34  24.123  389.2  43.65  5.107 1.0127  994.23  6.38  -2.31  4.76  12.50
```

E responds with data from most recent sample interval on individual lines;
each line is terminated with \r\n

Firmware Ver 4.11cf displays:

    BPR: 1012.32
    HRH: 72.34  24.123
    LWR: 389.2
    PRC: 43.65
    SCT: 5.107 1.0127
    SWR: 994.23
    WND: -12.31  4.76
    BAT: 12.50 12.60 12.70 12.80   (BAT NOT USED in any version)

FOK for menu-driven CompactFLASH command operations
- Sampling MUST be STOPPED for CFLASH command ops.
- Upon FOK command entry, and between each command, you will see a prompt:
Enter Flash Cmnd, ? or H for Help:
- a request for Help returns this message followed by another prompt:
```
    Flash Help (All commands end with Enter)

    C - Read card Capacity
    D - Read the card Directory
    E[I,D] - Erase the contents of the Info or Data files
    F[W,R] - Write or Read the Info File
    H{?} - Display this menu
    I - Format & Initialize the card file structures
    P - Read the next write & read sector Pointers
    R{H,A}{SEC} - Read the next card sector (see P command above)
             optional {H,A} -> Hex ASCII or printable ASCII
	     optional {SEC} -> specific sector number
    S - Read the CF status (reg 7 and the ERRORs (reg 1), disp as HEX-ASCII
    W{nnn} - Write 512 byte Test Msg to the Data file
             optional {nnn} -> 1-3 digits of additional sectors to write
    Q - Quit Flash operations

    Enter Flash Cmnd, ? or H for Help:
        
```
- description of FOK Menu Commands:
- C - displays card capacity info
- D - displays a card directory (similar to a DOS "dir" command output):
```
Volume in drive is NEWLGR53
Directory of CF:
2008/04/24  19:10                   35 LOGR001.INF
2008/04/25  16:42               523904 LOGR001.DAT
               2 File(s)         523939 bytes
                              256179584 bytes free
       
```
- EI - erases the contents of the INFO file, and sets its size to 0
- ED - erases the contents of the DATA file, and sets its size to 0
- FR - reads the free-format ASCII contents of the INFO file
- FW - prompts for up to 600 characters of user info; CTRL-C terminates entry into the INFO file
- I - formats & initializes the CFLASH card for use in the logger. A series of prompts guides you through the process. This must be done before the logger will recognize the card and use it for data storage.
- P - reads the next write and read sector pointers. In particular, the next write sector pointer always indicates the last sector of data on the card. This is useful with the XMODE command.
```
  
Flash Write Pointer @ 1345
Flash Read Pointer @ 258
       
```
  The write sector pointer is always restored to the currently available sector for new data whenever the logger is powered up. The read pointer is reset to the INFO file sector on power up.
- R - read command allows a number of options, the most useful being the RH and RH{SEC} options. For example, to see what's in the last DATA sector, use the P command above to find the current write sector, then use that in the RH{SEC} command to see the values. So, for the value of the Flash Write Pointer above, send RH1345 to see the 512 bytes of that sector:
```
 
Reading Flash @ 1345

000  10 29 19 04 07 00 64 01 00 00 00 00 00 00 00 00 .)....d.........
010  00 00 0D F2 09 AC 00 00 08 F0 AD 2E 00 00 00 00 ................
020  00 00 00 00 00 00 00 00 00 00 00 00 30 D4 31 38 ............0.18
030  31 9C 32 00 07 5B CD 15 00 01 00 00 00 00 A5 A5 1.2..[..........
040  10 2A 19 04 07 00 65 01 00 00 00 00 00 00 00 00 .*....e.........
050  00 00 0D F2 09 AB 00 00 08 F5 AC F9 00 00 00 00 ................
060  00 00 00 00 00 00 00 00 00 00 00 00 30 D4 31 38 ............0.18
070  31 9C 32 00 07 5B CD 15 00 01 00 00 00 00 A5 A5 1.2..[..........
.
.
.
1B0  31 9C 32 00 07 5B CD 15 00 01 00 00 00 00 A5 A5 1.2..[..........
1C0  10 28 19 04 07 00 63 01 00 00 00 00 00 00 00 00 .(....c.........
1D0  00 00 0D F2 09 AA 00 00 08 D3 AD 6A 00 00 00 00 ...........j....
1E0  00 00 00 00 00 00 00 00 00 00 00 00 30 D4 31 38 ............0.18
1F0  31 9C 32 00 07 5B CD 15 00 01 00 00 00 00 A5 A5 1.2..[..........
      
```
  If you want to read subsequent contiguous sectors, just do an RH at the next prompt, and the next sector in sequence will display (1346 in this example). See Record Format to decode the HEX dump.
- S - CF status info - internal WHOI use only
- W{nnn} - writes test data to the current write sector in the DATA file. Used only for test. If you use this function, you should ED to erase the DATA file before deploying the logger, unless you wish to incur the wrath of your data processing guru!
- Q - quit Flash ops and return to logger command mode
- New CFLASH Card Prep - when installing a CFLASH card for the first time, it must be initialized for use in the logger. The "I" command, Format & Initialize card file structures is used to prepare the CFLASH card for use. You will be prompted for a Volume name, an INFO File name, and a DATA file name. The 3 character suffix of the INFO file is always .INF and the 3 character suffix of the DATA file is always .DAT Once formatting is complete, you can get a directory with a "D" command, or write user info into the INFO file with the "FW" command, then read the INFO file back with the "FR" command.

FS for CompactFLASH status and directory

- example - displays the following info:

Compact Flash Card present - Compact Flash OK!

Volume in drive is NEWLGR53
Directory of CF:
2008/04/24  19:10                   35 LOGR001.INF
2008/04/25  16:42               523904 LOGR001.DAT
               2 File(s)         523939 bytes
                              256179584 bytes free

GO to start sampling (power up default - only used to restart after STOP for testing, new configuration, etc.) Responds with "Sampling GO\r\n". Sampling MUST be STOPPED.

HELP displays a brief list of all the commands. Each line is terminated in "\r\n". A truncated HELP output is displayed when LOGR53 is running (GO mode); i.e., only those commands available while running are displayed. To access the full command set, the LOGR53 must be STOPPED.

   Example of output in STOPPED mode:

   Firmware LOGR53 v4.11cf
   A - Address acknowledge
   CC - Comms Controller commands:
       CCOxxx - Overide ON time [1-240]
       CCSTAT - Comms Controller Settings Status
       CCSHDN - Shutdown Comms Controller Power
   CLOCK(=YYYY/MM/DD HH:MM:SS) - Read/Set RT clock date/time
   D - Send latest standard data
   E - Send latest extended data
   F - Compact FLASH commands:
       FOK - Complete Sub-Menu
       FS - Status & Dir info only
   GO - Re-start sampling
   H - Display Help message
   R - Display Recent records
   STAT - System status info
   STATD - System status info & CFLASH Dir
   STOP - Stop sampling
   T - Test mode commands:
       TM - MET Module tests
       TP - PTT tests
   UOK - Update EEPROM constants
   XMODE - XMODEM Dump CFLASH card via RS232 console

R to HEX dump the most recent 256 records of data written to FLASH
- The LOGR53 board uses 16K of spare RAM as a circular buffer to keep the most recent 1 minute records written to FLASH. If set for an R-interval of 1, that allows the most recent 4.25 hours to be dumped to the console as HEX-ASCII. At 9600 baud, this takes about 40 seconds.
- One 64 byte record is dumped per line; this means 128 HEX characters per line.
- This data may be dumped without STOPping the logger.
- Data is in volatile RAM; if power is lost, all existing recent data in the RAM buffer is lost. (Of course, it still remains stored in FLASH for later retrieval).
- See Record Format to decode the HEX dump.
- See UOK command below to set R-interval for the RAM buffer.
STAT reports all current settings in multiline format. On an EEPROM failure, the first line will be "\r\nDEFAULT OPERATION\r\n".
- Normal Operation, STAT command:
  Instrument Address\r\n (not used)
  Model\r\n
  Serial Number\r\n\
  Latest Checkout/Calibration Date\r\n
  Firmware Name and Version\r\n (from EPROM)
  RTC date and time\r\n (CLOCK command format)
  Logging Interval and Current Tick\r\n
  Recent Record Interval (R-interval)\r\n
  CFLASH Card Present?\r\n
  Main Battery Voltage: (place holder - NOT USED in any version)\r\n
  (optional failure messages for any bad/missing modules)
  PTT ID#1 packed data message in Hex-Ascii\r\n
  PTT ID#2 packed data message in Hex-Ascii\r\n
  PTT ID#3 packed data message in Hex-Ascii\r\n
  Sampling GO\r\n
```
    Example of STAT (note 4 missing modules):

    LOG01
    Model: LOGR-530
    SerNum: L12
    CalDat: 24APR08
    Firmware: LOGR53 v4.11cf
    RTClock: 2008/04/24  15:24:00
    Logging Interval: 60; Current Tick: 3
    R-interval: 1
    Compact Flash Card present - Compact Flash OK!
    Main Battery Voltage:  12.50
    PRC failed
    SST failed
    TMP failed
    WND failed
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    Sampling GO

    
```
STATD reports as above, with the addition of directory info for the CFLASH card.
- Normal Operation, STATD command:
  Instrument Address\r\n (not used)
  Model\r\n
  Serial Number\r\n\
  Latest Checkout/Calibration Date\r\n
  Firmware Name and Version\r\n (from EPROM)
  RTC date and time\r\n (CLOCK command format)
  Logging Interval and Current Tick\r\n
  Recent Record Interval (R-interval)\r\n
  CFLASH Card Present?\r\n
  Several lines of Directory info, each terminated \r\n
  Main Battery Voltage: (place holder - NOT USED in any version)\r\n
  (optional failure messages for any bad/missing modules)
  PTT ID#1 packed data message in Hex-Ascii\r\n
  PTT ID#2 packed data message in Hex-Ascii\r\n
  PTT ID#3 packed data message in Hex-Ascii\r\n
  Sampling GO\r\n
```
    Example of STATD:

    LOG01
    Model: LOGR-530
    SerNum: L12
    CalDat: 24APR08
    Firmware: LOGR53 v4.11cf
    RTClock: 2008/04/24  15:24:00
    Logging Interval: 60; Current Tick: 3
    R-interval: 1
    Compact Flash Card present - Compact Flash OK!
    Volume in drive is NEWLGR53
    Directory of CF:
    2008/04/24  19:10                 35 LOGR001.INF
    2008/04/25  14:20             519168 LOGR001.DAT
		2 File(s)         519203 bytes
			       256184320 bytes free
    Main Battery Voltage:  12.50
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    Sampling GO

    
```
NOTE: Power to failed modules is cycled OFF for 45 seconds, then restored; At the next 1 minute interval, new data will NOT be ready - new data will appear at 2 minutes after the power was originally cycled off.
STOP to stop sampling and allow configuration changes or testing. Responds with "Sampling STOP\r\n".
NOTE: this command may NOT be issued while the Comms Controller power is ON, except during the initial 60 minutes after powerup. This is a safety measure to prevent a Comms Controller from STOPping the logger operation.
TM Test all modules (Ports 1 thru 8 only, fixed format)
- On entry, displays "MET Module test command", then continuously tries to poll the standard 8 modules by sending a 'C' command to the default module address (e.g. #BPR01C)
- displays one module per line, full 'C' command return string
```
Example:
MET Module test command
BPR:  976.32
HRH:   0.000   0.000
LWR:   0.000   0.000   0.000   0.000
PRC: not responding (not installed?)
SCT: not responding (not installed?)
SWR:   -4.3
WND: not responding (not installed?)
                
```
- Updates about every 5 seconds (longer if missing modules)
- To quit, hit ESC.
- NOTE: there is about a 2 second timeout delay on each bad/missing module
TP Test PTT serial comms
- On entry, displays "PTT test command",
- NOT IMPLEMENTED
- Sampling MUST be STOPPED to use any test command.
UOK enter configuration update mode (held in EEPROM)
- Commands tagged with * will respond individually with their current settings if terminated immediately with <cr>; i.e. to see the current address, send ADR<cr>
- Remain in update mode until ABORT or WRTOK command.
- Sampling MUST be STOPPED to enter update mode.
  - ABORT to quit this mode without update; responds with "quitting...\r\n" after restoring original settings.
  - * ADR=xxxxx to set 1 to 5 character address (default is LOG01). These must be alpha-numeric. NOT USED in Ver 1.2x
  - * CCD=xx to read/set the Comms Controller ON time at each interval.
    May bet set from 1 to 30 minutes of ON time.
  - * CCI=xx to read/set the Comms Controller ON time interval.
    May bet set from 1 to 96 hours from one ON time to the next.
  - * CD=xxxxxxx to set a free format, 7 characters max, configuration date. For reference only, not used internally by instrument. Displayed in STAT[D] commands.
  - * RE=xxx - R-interval for RAM buffer (1 - 60 minutes) R-interval determines how often a data record is put into the RAM buffer for the R command. For example, an R-interval of 1 puts every data record into the RAM buffer, allowing about 4 1/4 hours maximum of data to be buffered. An R-interval of 6 puts every 6th data record into the buffer, so about a whole day of data will be buffered, at 6 minute intervals.
  - * RI=xxxx to set the logging interval (typically 60 seconds) The interval may be from 60 to 3600 seconds, in multiples of 60 seconds only! Displayed in STAT[D] commands. CAUTION: Long term testing has been performed only at the 60 second logging interval (RI=60)
  - WRTOK to write all EEPROM parameters. Update mode exits upon completion of write.
XMODE XMODEM Dump CFLASH card via RS232 console
- Sampling MUST be STOPPED and logger comms MUST be set for RS232 to dump data via XMODEM
CompactFLASH cards will take FOREVER to read this way - the preferred method of reading data is to remove the CFLASH card from the LOGR53 and read it on a PC. Two files will be recognized by the PC, an INFO file which can contain up to 600 characters of user information, and a DATA file which contains the logger data records. See the FOK command above.
- This command is rudimentary; if you must dump data this way, use the FS command to display the current directory and file sizes on the CFLASH card. You can then estimate where to start dumping data, based on one 64 byte record per minute, and a CFLASH sector size of 512 bytes. Or use the FOK command to look at the HEX values of particular sectors to decide where to start the dump.
- Command dumps data from the requested starting sector for up to 2048 512-byte sectors (i.e. a maximum of 1 MB of data). Sector 322 is the first sector of the data file on the CFLASH card.
- On command entry, requests: Start sector # (322 is first, 0 aborts) -> followed by: Number of sectors (1 to 2048, default is 512) ->
- i.e. to get first MB of data (16384 logger records -> about 11 days), enter 322 as the start sector, and 2048 for the number of sectors.
- add 2048 to your start sector number to find the start of subsequent 1 MB portions of data; i.e. if you entered 322 to start at the first sector on the FLASH card, subsequent 1 MB portions of data start at sector 2370, 4418, etc...
- Typical example - the following description assumes PCPLUS for terminal software, but any terminal program capable of XMODEM transfer should work.
- On entry, LOGR53 will first prompt for start sector:
  Start sector # (322 is first, 0 aborts) ->
  Enter a valid sector # (see discussion above)
- followed by a prompt for number of sectors:
  Number of sectors (1 to 2048, default is 512) ->
  Enter a valid sector count (see discussion above)
- Next, you'll be prompted:
  Set terminal speed for 38400 then hit any key
- After setting speed and hitting a key, you will see:
  XMODEM Send Function
  Waiting for start...
- Start a transfer (PgDn in PCPLUS) - on completion, you will see something like:
  Sent 160 blocks - done
  Restore terminal speed to 9600 then hit any key
  NOTE:"blocks" here are XMODEM blocks of 128 bytes each
- After resetting speed to 9600 baud and hitting a key, LOGR53 will send a "\r\n"
- Ignore occasional gibberish when changing baud rates!
- See also Record Format.