[FOSS-GPS] Using RTKLib with Novatel OEM device as base

jtwork taflan.work at gmail.com
Wed Sep 3 11:05:47 PDT 2014


The message is the 'binary log' output for the data message in the Novatel
OEM format.  The hex that it displays is supposedly a correct message, but I
just realized after somehow thinking there was no issue that rather than the
'AA4412' sync chars that are supposed to start off the message, every
message starts with '004412'.  I'm not sure why this is, especially since
even in the Novatel documentation there is no mention of a replacement of 00
for AA, and the Novatel parser in the source code definitely uses 'AA4412'
as the sync chars.  Perhaps there is some sort of strange header only for
the logs?  I'm going to attempt to replace the 00 with AA, and replace the
CRC with a correct one (I just tried simply replacing the 00 with AA to no
avail), and see if that makes any difference.

I have been attempting to use the OEMV-3 as a single-mode rover as well,
though at this point I'm just looking at the 'RTK monitor' output to see if
it can receive the data and actually parse it as the correct format.

View this message in context: http://open-source-gps-related-discussion-and-support.1099874.n2.nabble.com/Using-RTKLib-with-Novatel-OEM-device-as-base-tp7572967p7572988.html
Sent from the Open Source GPS-related discussion and support mailing list archive at Nabble.com.

More information about the FOSS-GPS mailing list