Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support Neo 8M GPSes #124

Closed
geeksville opened this issue May 4, 2020 · 2 comments
Closed

Support Neo 8M GPSes #124

geeksville opened this issue May 4, 2020 · 2 comments

Comments

@geeksville
Copy link
Member

either by using the new PVT API or by falling back to NEMA.
@geeksville
Copy link
Member Author

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/device-code-release-announcements/32/29

geeksville added a commit to meshtastic/protobufs that referenced this issue May 4, 2020
@geeksville
Use int32s for lat/long - higher precision and 4 bytes less per packet
cabbdf5 
related to meshtastic/firmware#124
geeksville added a commit to geeksville/Meshtastic-Android that referenced this issue May 4, 2020
@geeksville
support int based lat/long
12f7e9a 
for meshtastic/firmware#124
geeksville added a commit to geeksville/Meshtastic-esp32 that referenced this issue May 4, 2020
@geeksville
Use int based lat/long from now on in the device code
9b309fe 
for meshtastic#124
geeksville added a commit to geeksville/Meshtastic-esp32 that referenced this issue May 5, 2020
@geeksville
WIP on meshtastic#124
c2be6c4
@geeksville
Copy link
Member Author

I've been told this now works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@geeksville