New Safe Mode Controller #748
No reviewers
Labels
No Label
OPS TODO
api change
breaking api change
bug
documentation
duplicate
feature
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
#221 new safe mode
eive/eive-tmtc
Reference: eive/eive-obsw#748
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "acs-safe-flp-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
requires: eive/eive-tmtc#221
and appropriate changes for the MIB
New Safe Mode Controllerto WIP: New Safe Mode ControllerWIP: New Safe Mode Controllerto New Safe Mode Controller@ -33,0 +29,4 @@
SAFECTRL_MEKF = 10,
SAFECTRL_GYR = 11,
SAFECTRL_SUSMGM = 12,
SAFECTRL_ECLIPSE_DAMPING_GYR = 13,
I guess this enforces a minimum compatible OBSW version for the new MIB?
Yes this is a breaking change sadly
@ -0,0 +94,4 @@
{
PoolReadGuard pg(fusedRotRateData);
std::memcpy(fusedRotRateData->rotRateOrthogonal.value, ZERO_VEC, 3 * sizeof(double));
fusedRotRateData->rotRateOrthogonal.setValid(false);
im an AOCS noob, those 2 being invalid is on purpose?
they are. During eclipse we take the last valid rotational rate calculated and use the GYRs to continue from there. Therefore the split into orthogonal and parallel is never calculated here.