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

Piksi upgrades + test #98

Closed
tanishqaggarwal opened this issue Dec 8, 2019 · 10 comments
Closed

Piksi upgrades + test #98

tanishqaggarwal opened this issue Dec 8, 2019 · 10 comments

Comments

@tanishqaggarwal
Copy link
Member

  • Take Quake SBDIX into account
  • Testing Piksi dead
  • Test Piksi float -> fixed RTK
@tanishqaggarwal
Copy link
Member Author

tanishqaggarwal commented Dec 8, 2019

Need to modify ClockManager as well to update "propagated" GPS time

@tanishqaggarwal
Copy link
Member Author

Need to unit-test that the output values are initialized to NaNs

@tanishqaggarwal
Copy link
Member Author

tanishqaggarwal commented Dec 30, 2019

The reported GPS position should be the GPS position of the center of mass (this is distinct from the GPS position of the GPS antenna face.) A position offset therefore needs to be added for all CDGPS measurements.

@tanishqaggarwal
Copy link
Member Author

We need to add a time offset since the hardware-stored GPS time offset is sometime in 2000

@tanishqaggarwal
Copy link
Member Author

The reported GPS position should be the GPS position of the center of mass (this is distinct from the GPS position of the GPS antenna face.) A position offset therefore needs to be added for all CDGPS measurements.

@nhz2 @kkrol27 In my notes from last semester I found that we want to offset the computed GPS position for the sake of the control algorithm. Is this still necessary under the new orbital control algorithm?

@kylekrol
Copy link
Member

The reported GPS position should be the GPS position of the center of mass (this is distinct from the GPS position of the GPS antenna face.) A position offset therefore needs to be added for all CDGPS measurements.

@nhz2 @kkrol27 In my notes from last semester I found that we want to offset the computed GPS position for the sake of the control algorithm. Is this still necessary under the new orbital control algorithm?

This will really only be an issue when we have RTK and are in very close approach.

@tanishqaggarwal tanishqaggarwal added this to 3/22 - 3/28 in Schedule Mar 10, 2020
@tanishqaggarwal tanishqaggarwal added this to the Sprint: 3/22 - 3/28 milestone Mar 10, 2020
@tanishqaggarwal tanishqaggarwal moved this from To Do to PR Review in Flight Software Development Mar 11, 2020
@tanishqaggarwal tanishqaggarwal removed this from the Sprint: 3/22 - 3/28 milestone Mar 11, 2020
@tanishqaggarwal tanishqaggarwal moved this from 3/22 - 3/28 to 3/8 - 3/14 in Schedule Mar 12, 2020
@tanishqaggarwal tanishqaggarwal moved this from 3/8 - 3/14 to 3/15 - 3/21 in Schedule Mar 15, 2020
@tanishqaggarwal tanishqaggarwal moved this from 3/15 - 3/21 to 3/22 - 3/28 in Schedule Mar 22, 2020
@tanishqaggarwal tanishqaggarwal moved this from 3/22 - 3/28 to 3/29 - 4/4 in Schedule Mar 28, 2020
@tanishqaggarwal tanishqaggarwal moved this from 3/29 - 4/4 to 4/5 - 4/11 in Schedule Mar 28, 2020
@tanishqaggarwal tanishqaggarwal moved this from 4/5 - 4/11 to 4/12 - 4/18 in Schedule Apr 9, 2020
@tanishqaggarwal tanishqaggarwal moved this from 4/12 - 4/18 to 4/5 - 4/11 in Schedule Apr 14, 2020
@tanishqaggarwal tanishqaggarwal moved this from 5/3 - 5/9 to 5/16 - 5/22 in Schedule May 1, 2020
@tanishqaggarwal tanishqaggarwal moved this from 5/16 - 5/22 to 5/10 - 5/15 in Schedule May 15, 2020
@tanishqaggarwal tanishqaggarwal moved this from 5/16 - 5/22 to 5/23 - 5/29 in Schedule May 18, 2020
@tanishqaggarwal tanishqaggarwal moved this from 5/23 - 5/29 to 5/30 - 6/5 in Schedule May 18, 2020
@tanishqaggarwal tanishqaggarwal moved this from 5/30 - 6/5 to Unscheduled/Unassigned in Schedule Aug 8, 2020
@tanishqaggarwal tanishqaggarwal moved this from Unscheduled/Unassigned to Pre-semester in Schedule Sep 2, 2020
@tanishqaggarwal tanishqaggarwal moved this from Pre-semester to Need discussion in Schedule Sep 2, 2020
@shihaocao
Copy link
Collaborator

PIksi should set values to NaN anytime an uncessusful read was performed that control cycle

@tanishqaggarwal
Copy link
Member Author

Piksi data gets reported into state fields in mm, not m

@kylekrol
Copy link
Member

We're only listening to fixed RTK mode, NaNs are a thing of the past and taken of somewhere else. The only potentially open issue is Piksi readings during SBDIX; however, we're deeming this very low priority.

@kylekrol kylekrol moved this from Last-Mile FSW Development to FSW Telemetry Configurations in Ticket organization by topic (Don't forget to check pprocs and psim for issues as well) Mar 16, 2021
@kylekrol kylekrol moved this from FSW Telemetry Configurations to We'll survive if we don't finish these... in Ticket organization by topic (Don't forget to check pprocs and psim for issues as well) Mar 16, 2021
@shihaocao
Copy link
Collaborator

Closing as we don't need any RTK interference code, and we have piksi dead as a fault

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Ticket organization by topic (Don't f...
We'll survive if we don't fin...
Schedule
  
Need discussion
Development

No branches or pull requests

3 participants