30.06.2015 Views

REFERENCE MANUAL - FTP Directory Listing - Trimble

REFERENCE MANUAL - FTP Directory Listing - Trimble

REFERENCE MANUAL - FTP Directory Listing - Trimble

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

NMEA 0183<br />

C<br />

General NMEA Parser Requirements<br />

• When no position fix is available, some of the data fields in the NMEA<br />

messages will be blank (i.e., no characters between commas), but selected<br />

messages will output every second.<br />

• <strong>Trimble</strong> varies the number of digits of precision in variable length fields, so<br />

customer parsers should be able to handle variable lengths.<br />

• NMEA parsers should be built to be forward-compatible. Future versions of a<br />

standard message may have more fields or more choices per field.<br />

• Checksum matching is strongly recommended.<br />

• 9600 baud may be required if GSV messages are output.<br />

• When multiple NMEA settings are implemented, save them to Flash memory.<br />

• For GGA, GLL, RMC messages, time is GPS time (not UTC) until leap second<br />

parameter is known. There is no way to tell which time your are running in,<br />

until the time output suddenly decreases by 14 seconds (or by the current<br />

offset).<br />

• For GGA, GLL, RMC messages, if the datum is changed, there is no regular<br />

DTM warning of non-WGS-84 datum as required by NMEA 2.1. You must<br />

query the datum for this information.<br />

Copernicus GPS Receiver 217

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!