Issue with Sanav messages

Help
Chris
2012-12-31
2013-06-12
  • Chris

    Chris - 2012-12-31

    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!)
    imei=353681046621009&rmc=$GPRMC,022434.000,A,4327.5920N08026.8806,W,0.00,317.84,141212,,,A*75,START

    The message is missing a comma around the N.
    imei=353681046621009&rmc=$GPRMC,022434.000,A,4327.5920,N,08026.8806,W,0.00,317.84,141212,,,A*75,START

    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?

     
  • Martin Flynn

    Martin Flynn - 2012-12-31

    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,".

     
  • Eduardo Robles

    Eduardo Robles - 2013-01-02

    In any case, you can modify the parser in your DCS to take to account this bug.
    Cheers,
    Eduardo.

     
  • Chris

    Chris - 2013-01-04

    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..

    cheers!

     
  • Andrew Chamot

    Andrew Chamot - 2013-01-11

    ,START

     
  • Andrew Chamot

    Andrew Chamot - 2013-01-11

    Would it be possible to add support for custom field  ", START" (last part of the string)

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks