Fix compatibility with automatically configuring newer ublox modules #646
Conversation
|
If the old CFG_MSG message is not valid anymore (4 instead of 6 IO port), it should be removed or at least fixed. |
|
I think we should remove the old CFG_MSG completely. It isn't used anywhere else in the project. I'll update the pull request with the changes. |
|
What about the old ublox 4? I guess quite a few people still have/use some that work just fine... |
|
Switching to this CFG-MSG will provide better support across module generations. The suggested change works for ublox 4 through ublox 7 modules and will very likely work for modules in the future since we don't need to know how many input/output ports the future modules will have. I had a bit of hard time finding the specification for ublox 4 modules. So here is a link if other people want it. |
|
Great, thx @achambers16 |
|
good for me as well |
|
Shame that we still need GPS_PORT_ID for UbxSend_CFG_PRT.... |
Fix compatibility with automatically configuring newer ublox modules
The current auto-configuration uses a "no longer supported" method to set the desired output messages from the ublox.
Currently, it sets the configuration for 4 outputs ports at once but starting with ublox 5, there are 6 I/O ports and this command no longer works.
See Section 4.5 "How to change between protocols" in GPS.G6-SW-10018-F
http://www.u-blox.com/images/downloads/Product_Docs/u-blox6_ReceiverDescriptionProtocolSpec_%28GPS.G6-SW-10018%29.pdf
This pull request sets the configuration of only 1 output port. That output port is determined by the port that receives the configuration message.
Fixes #645