-
Notifications
You must be signed in to change notification settings - Fork 964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPS updates #3142
GPS updates #3142
Conversation
We've found some really weird details around the PM2 config message. Comparing the u-center output with https://content.u-blox.com/sites/default/files/products/documents/u-blox6_ReceiverDescrProtSpec_(GPS.G6-SW-10018)_Public.pdf reveals some weird things. The most notable thing is that the PDF says the internal flag must be 000, while u-center sets it to 111. So the bytes we set as 0x0E814301 should actually be 0x00814301. According to the U-blox spec. There are many other fields that are marked reserved in the PDF, that u-center sets values to. |
This is the beginning of the GPS updates as a result of my audit of the initialization message flow for the u-blox series of receivers.
The first step was correction several of the init messsages sent by Meshtastic to configure the GPS receiver(s), There are many models and some require different commands to do the same thing. That will be the focus of the next update. This PR only addresses the Neo-6, and adds some groundwork for the future changes.
Testing has been done on my Chatter 2 platform with a Neo-6 module and on a t-beam 1.2 with a Neo-6 as well.