MTQ Scaling Bugfix #653
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#653
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "mtq-cmd-bugfix"
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?
Currently the C
abs
is used, which is integer only and will truncate values. In case the required dipole is in below 1Am² but above 0.2Am², this will result in the dipole vector not being scaled down to the limit of 0.2Am². Instead the full dipole is passed on the the MTQ.According to https://egit.irs.uni-stuttgart.de/redmine/attachments/download/319/ISIS.iMTQ.User%20Manual.v1.6.pdf p.34 the MTQ will still accept the command and scale it down accordingly on its own. Therefore, this bug should not change the performance of the MTQ. Nevertheless this bug is relevant for all ACS Ctrl modes, including detumble and safe mode, and the performance of the MTQ should be checked asap during LEOP.
Actually math.h seems to save my ass here. No clue why, cause I cant find any documentation for that shit. Anyhow, this bug doesn't seem to be part of the flight software. This merge is still needed, cause newer versions of this function do not include math.h anymore