IMTQ Updates #306
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.
Dependencies
No dependencies set.
Reference: eive/eive-obsw#306
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "mueller/imtq-updates"
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?
Update to allow conveniently setting new torque values in the controller. Is currently asynchronous which I really don't like. Can maybe be fixed with a PST.
Note for future me:
New ACS Task, High priority with the following general order
So basically the performOp step of the Subsystem, then the com sequences for all SPI MGMs, then three com sequences for IMTQ.
At this stage, all important sensor values for the ACS CTRL should be ready, so we execute the ACS CTRL to get the actuator output.
After the ACS CTRL has run, the MGT output should be ready and we can start IMTQ torqueing. We could also put the RWs inside this task so they actuate with the most recent values calculated by the ACS CTRL.