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

Send GPS startup blob only if GPS_AUTO_CONFIG=1 #4636

Closed
wants to merge 3 commits into from

Conversation

mr337
Copy link
Contributor

@mr337 mr337 commented Aug 8, 2016

This PR is for issue #2622.

Problem

Currently all GPS regardless of type get sent the start blob. For some GNSS receivers this confuses them and halts sending GNSS data.

Solution

I could only find AUTO_CONFIG used in UBLOX receivers. To limit this the start blob is only sent if AUTO_CONFIG=1. This allows to have any type of GPS and still have control on to config or not. If using UBLOX AUTO_CONFIG=1 will have to be set, which is the default so hoping to have little impact.

Lee Hicks added 3 commits August 8, 2016 14:46
APM supports baud speeds of 19200, but GPS baud rates
don't support it. This commit adds it to follow APM supported
baud rates.
The counting of this will increment the counter before
selecting the baud speed, skipping the first baud rate.
All GPS types will recieve startup up blob config. For
some recievers this will cause them to hang. This commit
only allows sending of blobs if AUTO_CONFIG=1. Fixes ArduPilot#2622
@WickedShell
Copy link
Contributor

Seems appropriate to me. We really need to add support to stop auto-bauding as well, but that is probably a separate issue for the future.

I might rearrange the order of the baud table as well to keep the most common bauds first (9600 -> 38400 -> 115200 then the others) but that has been on the todo list for awhile now.

Will try to test on actual hardware before next dev call.

@mr337
Copy link
Contributor Author

mr337 commented Aug 13, 2016

@WickedShell I can update that tomorrow for common ordering,

9600
38400
115200
then the non common ones after that?

Also anything else I can do to test. I've been using the PR basically since I've submitted for my project.

@magicrub
Copy link
Contributor

Moving the baudrate increment is a good bug fix. Nice catch.

@tridge
Copy link
Contributor

tridge commented Aug 16, 2016

looks good, thanks!
applied

@tridge tridge closed this Aug 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants