I've run in to this issue a number of times now with my Sanav devices. The message string that the DCS parses is missing a comma, so the Lat/Lon are incorrect. (always a Lon of 0.0000 showing the device in France!)
The message is missing a comma around the N.
Has anyone seen this before? Either with a Sanav device or any other device?
I've seen this issue while sending over both HTTP and UDP.
Is it a bug with the device, or is it a bug with the DCS parsing the initial message string?
This would be a bug in the data from the device. The NMEA-0183 standard for $GPRMC records specifies that there should be commas around the ",N,".
In any case, you can modify the parser in your DCS to take to account this bug.
I've made changes to the parser to ignore any messages that have messed up co-ordinates. However, I'd really like to find out why it's happening..
Would it be possible to add support for custom field ", START" (last part of the string)
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.