Message Type 112, ULCP binary format, Digital input and Output states, Modem ID and GPS data

Header: 0x70 0xSS 0x06 0x00 0x00 0xNN 0x0000

Where NN is the message length range 0x1d to 0x2B - dependant on the Modem ID string length.

Note: This message is message type 98? appended with modem ID

Message body:

HexDescription
4 bytesNormalized latitude (RMC latitude x 100,000)
4 bytesNormalized longitude (RMC longitude x 100,000)
2 bytesSpeed in knots
2 bytesHeading
1 byteGPS data validity: 0x”A” = valid; 0x”V” = invalid; 0x”B” = valid stored data; 0x"W" = invalid stored data
1 byteNumber of satellites used for position fix
1 bytePosition type (from GGA message)
1 byteDigital input state (0= off, 1=on): bit 0 = input #1, bit 1 = input #2…bit 5 = input #6, bit 6 = RF switch box output mode (1 = RF off, 0 = RF on), bit 7 = ignition status.
2 bytesAltitude in meters
2 bytesDifferential correction age (only valid if differential correction being used)
4 bytesTime (based on number of seconds since 00:00:00 January 1st 1970
1 byteDigital output state (0= off, 1=on): bit 0 = output #1, bit 1 = output #2, bit 2 = output #3, bit 3 = output #4,
bit 4 = output #5, bit 5 = output #6, bit 6 = input #7, bit 7 = input #8 (Outputs 5/6 and inputs 7/8 are CTM200r2 only)
0x00Not used
0x00Event source: None
0x00Event reason: None
1 to 15 bytesModem ID: ASCII string

Note: ULCP binary messages should not be used for local serial report mode 1 and 2 in applications where timed message delivery is critical.

Last modified 4 years ago Last modified on 16-05-27 02:24:33 PM