• State Not Answered
  • Replies 3 replies
  • Subscribers 69 subscribers
  • Views 869 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 274967
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy91 GPGGA value invalid, missing parts

daz

Hi there,

When parsing the GPS data from the Thingy91's GPGGA format, I've received invalid from such parsers.

Invalid:

$GPGGA,120558.916,5058.7457,N,00647.0514,E,2,06,1.7,109.0,M,47.6,,*71

I'm still able to successfully parse the value on my backend with a hack by adding an extra comma:

$GPGGA,120558.916,5058.7457,N,00647.0514,E,2,06,1.7,109.0,M,47.6,,,*7


Although I'm catering for a valid scenario (based on string split into an array of length 15), and an invalid scenario of length 14 (with the hack) this solution isn't ideal, and also may not be safe.

Is there a configuration option to correct the GPS format or a clean way to correct missing value(s) on the Thingy91 itself?

I also read a previous community post that you mentioned this is due to not supporting geoid model, and currently only support the ellipsoid model. Is this still the case?

I'm using the nRF SDK 1.6 version.

Thanks,

Daz

Parents Reply
  • 0 in reply to daz

    Hi,

     

    daz said:

    Thingy91 GPS value: $GPGGA,120558.916,5058.7457,N,00647.0514,E,2,06,1.7,109.0,M,47.6,,*71

    Bad GPGGA field count 14 via https://rl.se/gprmc

    I'm using modem firmware mfw_nrf9160_1.2.1.

    Could you try updating the modem fw? Which ncs version are you currently on?

    As mentioned, I did not get any errors when parsing with mfw v1.3.0 and ncs v1.6.x.

    daz said:

    Are there any clean solutions or even a conversion from ellipsoid to geoid with defaults (empty values for example) that you're aware of?

    I'm not aware, unfortunately.

    Kind regards,

    Håkon 

      

Children
No Data
Related