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.

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 research #3816

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

Gps research #3816

wants to merge 4 commits into from

Conversation

hdngr
Copy link
Contributor

@hdngr hdngr commented May 7, 2024

Begin researching M9 integration re: #3811.

A couple of things:

  1. Please provide feedback on if this overall structure looks alright. I don't think I'm breaking anything, but without any unit testing it is kind of a free for all
  2. @GPSFan it would be helpful if you could give some feedback on what the critical configs are to make the M9 functional... We'll translate them into 32.01

Feel free to write them as comments in the code here or in #3811.

cc @lolsborn

@GPSFan
Copy link
Contributor

GPSFan commented May 7, 2024

The hwVersion for the M9 is 90000 not 190000.

@GPSFan
Copy link
Contributor

GPSFan commented May 7, 2024

I have an M9 receiver and will be able to test it on my ESP32 based system, but until I get my I/O breakout for my RAK system (on order, shipped) I won't be able to do any testing on an NRF52.
I will review the attached code.

@hdngr
Copy link
Contributor Author

hdngr commented May 7, 2024

The hwVersion for the M9 is 90000 not 190000.

That would be logical, wouldn't it. But its not, lol.

image

@hdngr
Copy link
Contributor Author

hdngr commented May 7, 2024

I have an M9 receiver and will be able to test it on my ESP32 based system, but until I get my I/O breakout for my RAK system (on order, shipped) I won't be able to do any testing on an NRF52. I will review the attached code.

Totally. Just feeding ideas would be helpful. Have not dug into if they are defaults yet, but seems like setting RMC and GCA and then turning off all of the other chatty stuff might be the key thing to fix.

@lolsborn
Copy link
Contributor

lolsborn commented May 7, 2024 via email

@GPSFan
Copy link
Contributor

GPSFan commented May 7, 2024

Well, I'll be... shows you what a few years of not using the old M9 does..
That just reinforces the fact that the M9 is an odd duck.
And the rest of the example of the output of the MON-VER command (page 15 of UBX-21022436 - R02 shows an F9P, Protocol 34 and FWVER=HPG 1.12 as the firmware.
u-blox documentation isn't always the best.
My M9N is now at 4.04 protocol 32.01 and indeed does report the hwVersion as 190000.
Another corner case.....

LOG_INFO("Successfully set GPS update rate.!\n");
}
delay(1000);
}
Copy link
Contributor Author

@hdngr hdngr May 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What other messages should go here? Not super familiar with all of these protocols. A dump of the hex code for M9 would be helpful BUT, a pointer directly to config. Would be cool too.

For instance, what does _message_VALSET_DISABLE_NMEA_RAM correspond to? Would it be 3.10.13 UBX-CFG-NMEA (0x06 0x17)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GPSFan ^^... cc: @lolsborn

@GPSFan if you made comments in here with what configs our commands you think we absolutely need, we can grind them out. We'd appreciate it! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants