Specifications

© 2010 Cypress Solutions Complete Manual: CTM-15X Firmware 1.3.0
Open CTM (Revision D)
169
Report Messages
Message format is:
$POBDC,v,px=xxxxxx,[px=xxxxxx],[px=xxxxxx],[px=xxxxxx]*hh<CR><LF>
Note: the number and type of px values are based on the configuration of pobda thru pobdd commands.
Where:
v is the data validity flag: A = valid current data, B = valid stored data, V = invalid current data, W = invalid
stored data
px=xxxxx is the parameter ID px followed by the value of the parameter xxxxx
hh is the message checksum
Example:
$POBDC,V*20
9.29 Message Type 122, $POBDD
Proprietary NMEA message containing OBD II information captured from a vehicle. There are 4 available
messages for reporting OBD II/J1939 data, each message can return information on up to 4 parameters
based on the OBDII/J1939 parameters table.
Message format is:
$POBDD,v,px=xxxxxx,[px=xxxxxx],[px=xxxxxx],[px=xxxxxx]*hh<CR><LF>
Note: the number and type of px values are based on the configuration of pobda thru pobdd commands.
Where:
v is the data validity flag: A = valid current data, B = valid stored data, V = invalid current data, W = invalid
stored data
px=xxxxx is the parameter ID px followed by the value of the parameter xxxxx
hh is the message checksum
Example:
$POBDD,V*27
9.30 Message Type 136, $PACCEL
Proprietary NMEA message containing hard acceleration/deceleration information obtained from GPS
velocity data. This NMEA message is designed to be sent whenever the GPS hard
acceleration/deceleration thresholds are exceeded (see cmd gpsaccel).
Message format is:
$PACCEL,hhmmss.ss, llll.llll,a,yyyyy.yyyy,b,vvv.v,uuu.u,ddmmyy,ggggggggggg*hh<CR><LF>