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

Fix GPS Week Number to consider mod 1024 #5

Open
Duncan-McD opened this issue Mar 8, 2022 · 0 comments
Open

Fix GPS Week Number to consider mod 1024 #5

Duncan-McD opened this issue Mar 8, 2022 · 0 comments

Comments

@Duncan-McD
Copy link
Member

The GPS Week number for PAN was the wrong value and stuck at 2000. This was determined to be due to the fact that the GPS week number is calculated to be the week number modulus 1024. This value ended up being below the lower serializer bound for the GPS week, causing the value to instead be set to 2000.

More Information from diagnosis by Kyle/Stewart: "We've root caused the GPS time issue where the week number is continually reporting as 2000. Turns out, GPS devices always report the current week number mod 1024. What that means is the Piksi is actually reporting the week number as 144 and this is underflowing the week number serializer. Futhermore, this means the concept of "PAN time" onboard the spacecraft is all out of wack because we calculate PAN time by subtracting another GPS time (the PAN epoch) from with a week number greater that 1024 -- see TimeEstimator.cpp."

More information from old PAN issue ticket: pathfinder-for-autonomous-navigation#864

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

No branches or pull requests

1 participant