Laser Technology TruPulse 200X, User Manual

Page: 49 / 62

Section 6 – Serial Interface
Page 45
Download Message Format
The CR400 data format follows the guidelines of the NMEA Standard for interfacing
Marine Electronic Navigational Devices, Revision 2.0. NMEA 0183 provides for both
standard and proprietary data formats. Since none of the standard formats are useful for
the data transferred from the TruPulse 200X, special proprietary formats are used. Rules
described in the NMEA standard governing general message structure, leading and
trailing characters, numeric values, delimiting character, checksums, maximum line
length, data rate, and bit format are followed exactly. As required by NMEA 0183, the
CR400-format does not respond to unrecognized header formats, malformed messages, or
messages with invalid checksums.
Requests
The TruPulse 200X accepts Criterion 400 format requests for the firmware version ID.
The instrument will not respond to an invalid query. The format is as follows:
Firmware Version ID Request (1)
$PLTIT,RQ,ID<CR><LF>
$PLTIT The Criterion 400 message identifier.
RQ Indicates a request message.
ID Indicates the request type.
<CR> Carriage return.
<LF> Optional linefeed.
Instrument response:
$PLTIT,ID, model , versionid *csum <CR><LF>
$PLTIT The Criterion 400 message identifier
ID Identifies the message type.
model Indicates the model.
versionid The main firmware revision number.
*csum An asterisk followed by a hexadecimal checksum.
The checksum is calculated by XORing all the
characters between the dollar sign and the asterisk.
<CR> Carriage return.
<LF> Linefeed.
Examples:
Request: $PLTIT,RQ,ID
Response: $ID,TP-100,TruPulse200X-3.14-53,FEB 21 2013,AD9829CF*4FCF