Skip to content
This repository was archived by the owner on Jan 28, 2021. It is now read-only.

Corrected the default maxWait values (for getPVT etc.) #62

Merged
merged 1 commit into from
Dec 27, 2019
Merged

Corrected the default maxWait values (for getPVT etc.) #62

merged 1 commit into from
Dec 27, 2019

Conversation

PaulZC
Copy link
Collaborator

@PaulZC PaulZC commented Dec 26, 2019

Hi Nathan (@nseidle),

It was a great idea to make sure that maxWait was flowed down correctly from function to function.
The trouble is, the default maxWait for getLatitude, which calls getPVT, was then too short and resulted in timeouts. The default for getPVT was 1000msec, but that was getting overwritten by the 250msec default for getLatitude.
So, I've added a #define getPVTmaxWait of 1100msec (slightly longer than one navigation cycle) and have referenced that in getPVT, getLatitude, etc., etc..

I've done the same thing for the getHPPOSLLH functions too.

getLatitude was missing moduleQueried.all = false; so I've added that. (All the other associated functions include that line.)

I've also added some extra debug prints to help monitor the time it takes for an ACK to be received.
Enjoy!
Paul

@nseidle
Copy link
Member

nseidle commented Dec 27, 2019

Thanks for this!

@PaulZC PaulZC deleted the PaulZC_corrected_maxWait_values branch December 28, 2019 10:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants