MET BLOGR24 Commands - NTAS/SOFS with internal SBD Iridium Support

file: blogr24_sd_cmnd.html
12 Jul 2018

NTAS/SOFS MET BLOGR24 Commands - Firmware Ver 5.xx with internal SBD Iridium Support

See BLOGR24 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.
Ver 5.xx is based on NTAS/SOFS MET LOGR53 Firmware Ver 4.2x with internal SBD support.

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

BLOGR24 UPGRADE NOTE - The BLOGR24 hardware consists of a single PC board in the same form factor as the earlier LOGRIF PC board (which was part of a two board set with the VMLOGR53 CPU PC board). It will fit the same chassis used previously, and all wiring connectors on the new BLOGR24 PC board are the same and in similar positions to the older LOGRIF PC board. I.E. the BLOGR24 is a drop in replacement for the older two board set.

SDHC NOTE 1 - Firmware Ver 5.xx has been tested using SanDisk SDHC cards of 2 GB, 4 GB, and 8 GB on WHOI BLOGR24 Rev A buoy logger boards.

SDHC NOTE 2 - SDHC cards MUST be initialized using the I command choice in the SDOK command menu. SDHC cards may be read on a PC and will contain 3 files: a BLOGR24.ID file, a BLOGR24.INF file, and a BLOGR24.DAT file. Refer to SDHC Storage Format for details.

NOTE for loggers with ATTACHED REMOTE COMMUNICATION CAPABILITY (e.g. external Iridium Comms (ICC) unit): 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 the 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!

NOTE for loggers with INTERNAL IRIDIUM SBD CAPABILITY: Firmware supports hourly messages of ASIMET MET data and WMO-compliant MET data via an NAL Research 9602N Iridium modem attached to P21 on the BLOGR24 board. See Iridium SBD message Format for internal Iridium SBD message format.

ASIMET Module port assignments

(Port 1 thru Port 11 correspond to BLOGR24 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 (option)
Port 12 - Comms Controller (Iridium) Power Control (option)
Port 13 - 9602N SBD modem (option)

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 BLOGR24 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 5.32 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)
- V3.3, vMain, vMet, vAux (volts), BoardTemp (degC)
- ```
typical response:

1012.32   72.34  24.123  389.2  43.65  5.107 1.0127  994.23  -12.31  4.76  3.32 12.51 12.46 12.65 23.2
```

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

Firmware Ver 5.32 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 & TEMP: 3.29v, 13.46vMain, 13.51vMet, 13.58vAux, 23.0 degC

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 the BLOGR24 is running (GO mode); i.e., only those commands available while running are displayed. To access the full command set, the BLOGR24 must be STOPPED.

   Example of output in STOPPED mode:

   Firmware BLOGR24 v5.32
   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
   GO - Re-start sampling
   H - Display Help message
   O - Send Onboard System Values (v3.3, vMain, vMet, VAux, degC)
   R - Display Recent records
   SDOK - SD Card access - password 'OK'
   STAT - System status info
   STATD - System status info & SD Card Dir
   STOP - Stop sampling
   T - Test mode commands:
       TI - Iridium SBD modem tests
       TM - MET Module tests
       TP - PTT tests
   UOK - Update EEPROM constants
   XMODE - XMODEM Dump SD Card via RS232 console

Note 1: Setting the RT Clock Date & Time sets both the PIC24 System RTCC and the battery-backed DS3232 RTC chip.
Note 2: 'SDOK' and 'XMODE' are not available unless an SD Card is installed.

R to HEX dump the most recent 64 records of data written to SD Card
- The BLOGR24 board uses 4K 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 hour to be dumped to the console as HEX-ASCII. At 9600 baud, this takes about 10 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 on the SD Card for later retrieval).
- See SDHC Storage Format to decode the HEX dump.
- See UOK command below to set R-interval for the RAM buffer.
SDOK Menu-driven SDHC card command operations
- Upon SDOK command entry, and between each command, you will see a prompt:
  Enter SD Card Cmnd, ? or H for Help:
- a request for Help returns this message followed by another prompt:
```
    SD Card Help (All commands end with Enter)

    D - Read the card Directory
    E - Erase a file
    F[W,R] - Write or Read the Info File
    H{?} - Help menu
    I - Initialize the SD Card for this module
    Q - Quit Flash operations
    S - Show ID file (HEX then ASCII)

    Enter SD Card Cmnd, ? or H for Help:
    
```
- description of SDOK Menu Commands:
  - D - displays a card directory
```
2011-09-20 11:34:38             216 BLOGR24.ID
2011-10-04 12:59:00            7168 BLOGR24.DAT
2011-10-04 09:25:52             512 BLOGR24.INF
       
```
  - E - erases a file. Prompts with:
    Erase a file (8.3 format max) ->
    Enter aborts; type a valid filename and enter to erase the file.
  - FR - reads the free-format ASCII contents of the info file, BLOGR24.INF
  - FW - prompts for up to 500 characters of user info; CTRL-C terminates entry into the info file, BLOGR24.INF
  - I - initializes the SD Card for use in the module. You must answer Y at the prompt or this command will abort. This initialization must be performed before the module will recognize the card and use it for data storage.
  - Q - quit SD Card ops and return to logger command mode
  - S - display the contents of the ID file in HEX then ASCII. This file contains the current firmware version from program FLASH on the PIC24 micro, plus miscellaneous info from the EEPROM (as set via UOK command and displayed via I command). The current firmware version from program FLASH is compared with the version in the ID file to determine if the SD Card is initialized for use in the module.
- New SD Card Prep - when installing an SD Card for the first time, it must be initialized for use in the module. The "I" command, Initialize the SD Card for this module is used to prepare the SD Card for use. Three files will be created: BLOGR24.ID, BLOGR24.INF, and BLOGR24.DAT. Once initialization is complete, you can get a directory with a "D" command, or write user info into the BLOGR24.INF file with the "FW" command, then read the info file back with the "FR" command.
STAT reports all current settings in multiline format. On an EEPROM failure, the first line will be "\r\nDEFAULT OPERATION\r\n".
- Note that 2 clocks are displayed. The RTCC is the PIC24 internal clock which times all BLOGR24 functions. The DS3232 is the battery-backed clock chip which is reloads the RTCC on BLOGR24 startup.
- 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)
  RTCC date and time\r\n (CLOCK command format)
  DS3232 date and time\r\n (CLOCK command format)
  Logging Interval and Current Tick\r\n
  Recent Record Interval (R-interval)\r\n
  System values: v3.3, vMain, vMet, vAux, degC\r\n
  (optional failure messages for any bad/missing modules)
  PTT load success/failure message
  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
  Iridium: MET data enabled/disabled & WMO data enabled/disabled messages\r\n
  Iridium MET Status messages\r\n
  Iridium WMO Status messages\r\n
  Sampling GO\r\n
```
    Example of STAT with PTT enabled and Iridium SBD disabled (note 4 missing modules):

    LOG01
    Model: BLOGR24
    SerNum: 001
    CalDat: 24APR12
    Firmware: BLOGR24 v5.32
    RTCC: 2012/04/24  15:24:00
    DS3232: 2012/04/24  15:24:01
    Logging Interval: 60; Current Tick: 3
    R-interval: 1
    System: 3.30v, 13.44vMain, 13.51vMet, 13.58vAux, 21.6 degC
    PRC failed
    SST failed
    TMP failed
    WND failed
    Last PTT module update OK
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    5439F07D0321FF7FC00000000001F45439F07D0321FF7FC00000000001F43E0E
    Iridium: disabled
    Sampling GO

    
```
STATD reports as above, with the addition of directory info for the SD 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)
  RTCC date and time\r\n (CLOCK command format)
  DS3232 date and time\r\n (CLOCK command format)
  Logging Interval and Current Tick\r\n
  Recent Record Interval (R-interval)\r\n
  System values: v3.3, vMain, vMet, vAux, degC\r\n
  SD Card Ready/NOT Ready message\r\n
  Several lines of Directory info, each terminated \r\n
  (optional failure messages for any bad/missing modules)
  PTT load success/failure message
  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
  Iridium: MET data enabled/disabled & WMO data enabled/disabled messages\r\n
  Iridium MET Status messages\r\n
  Iridium WMO Status messages\r\n
  Sampling GO\r\n
```
    Example of STATD with PTT disabled and both Iridium SBD messages enabled:

    LOG01
    Model: BLOGR24
    SerNum: 001
    CalDat: 24APR12
    Firmware: BLOGR24 V5.32
    RTCC: 2012/04/24  15:24:00
    DS3232: 2012/04/24  15:24:01
    Logging Interval: 60; Current Tick: 3
    R-interval: 1
    System: 3.30v, 13.44vMain, 13.51vMet, 13.58vAux, 21.6 degC
    SD Card Ready
    2012-05-11 15:13:02               0 BLOGR24.INF
    2012-05-11 15:12:58              94 BLOGR24.ID
    2012-05-14 14:59:10            3200 BLOGR24.DAT
    ARGOS: disabled
    Iridium: MET data enabled & WMO data enabled
    Iridium MET Status: SBD Message OK
    Iridium WMO Status: SBD Message OK
    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
TI Iridium SBD Modem Tests
- on entry, displays 'Starting Iridium mode test'
- on success of messages, displays 'successful' message
- on failure, displays message indicating point of failure
- tests MET only if WMO not enabled
```
Example:
Starting Iridium mode test
SBD MET Message successful!
SBD command failed - no ACK
Exiting Iridium modem test
```
- error messages:
   SBDWB Checksum bad
   SBDWB data not accepted - timeout
   SBDWB command not accepted - timeout
   SBDI command not accepted - timeout
   SBDI command failed - no ACK

- the only message you may commonly see is SBDI command failed - this indicates that the modem did not get an acknowledgement from the satellite - do you have a good antenna with a good view of the sky? The other messages point to a problem with the modem configuration. Check your setup!
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 at this time
  - * 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.
  - * ARGOS=x 1 to enable ARGOS MET data transmission, 0 to disable
  - * IRD=x 1 to enable Iridium MET data transmission, 0 to disable
  - * WMO=x 1 to enable Iridium WMO data transmission, 0 to disable
    NOTE: WMO data will only be transmitted if IRD=1 enabling MET data transmission
  - * RE=xxx - R-interval for RAM buffer (1 - 60 minutes) R-interval determines how often a data record (64 bytes per 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 one hour maximum of data to be buffered. An R-interval of 4 puts every 4th data record into the buffer, so about 4 hours of data will be buffered, at 4 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.
  - WRTOK to write all EEPROM parameters. Update mode exits upon completion of write.
XMODE XMODEM Dump SD Card via console
- XMODE command only works in RS232 mode and only if an SD Card is installed
- SD Cards will take a LONG TIME to read this way - the preferred method of reading a large .DAT data file is to remove the SD Card from the module and read it on a PC. Three files will be recognized by the PC, the BLOGR24.ID containing ID info, the BLOGR24.INF INFO file which can contain up to 500 characters of user information, and the BLOGR24.DAT DATA file which contains the module data records. See the SDOK command above.
- This command is somewhat rudimentary; if you must dump data this way, use the STATD command to display the current directory and file sizes on the SD Card. You can then estimate where to start dumping data, based on one 64 byte record per minute.
- On command entry, requests: Start record # (1 is first, 0 aborts) -> followed by: Number of records (default is 512) ->
  - i.e. to get first day of data (1440 records per day), enter 1 as the start record, and 1440 for the number of records.
  - add 1440 to your start record number to find the start of subsequent day-long portions of data; i.e. if you entered 1 to start at the first record on the SD Card, subsequent days of data start at record 1441, 2881, etc...
- Typical example - any terminal program capable of XMODEM transfer should work.
  - On entry, module will first prompt for start record:
    Start record # (1 is first, 0 aborts) ->
    Enter a valid record # (see discussion above)
  - followed by a prompt for number of records:
    Number of records (default is 512) ->
    Enter a valid sector count (see discussion above)
  - Next, you'll be prompted:
    Set terminal speed for 115200 then hit any key
  - After setting speed and hitting a key, you will see:
    XMODEM Send Function
    Waiting for start...
  - Start a transfer - on completion, you will see something like:
    Sent 25 records (100 xmodem 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, module will send a "\r\n"
  - Ignore occasional gibberish when changing baud rates!
- If you request more records than the data file contains, you will see a "Reached EOF" message before the final record and block tally.
- Note: Only the BLOGR24.DAT data file from the SD Card is dumped via XMODEM; Refer to SDHC Storage Format.