eive/eive-obsw
eive/eive-obsw
13
4
Fork 0
Code Issues 4 Pull Requests 1 Releases 120 Wiki Activity

removed TODO
All checks were successful
EIVE/eive-obsw/pipeline/head This commit looks good
Details

Browse Source
This commit is contained in:
Robin Müller 2022-10-20 10:52:13 +02:00
parent 07fe2cb122
commit ada1111252
No known key found for this signature in database
GPG Key ID: 71B58F8A3CDFA9AC
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
mission/devices/ImtqHandler.cpp
View File

@ -62,11 +62,7 @@ void ImtqHandler::doStartUp() {
void ImtqHandler::doShutDown() { setMode(_MODE_POWER_DOWN); } void ImtqHandler::doShutDown() { setMode(_MODE_POWER_DOWN); }
ReturnValue_t ImtqHandler::buildNormalDeviceCommand(DeviceCommandId_t* id) { ReturnValue_t ImtqHandler::buildNormalDeviceCommand(DeviceCommandId_t* id) {
// TODO: Add IMTQ torque handling here, will be set in the software and thus must be part // Depending on the normal polling mode configuration, 3-4 communication steps are recommended
// of normal handling. Keep in mind that torqueing should happen after all HK data was read
// because the MGM values might be useless if the IMTQ is torqueing. Also, remove
// calibrated MGM polling, we have our own calibration. Thus, there are 3 communication
// steps per IMTQ cycle.
switch (communicationStep) { switch (communicationStep) {
case CommunicationStep::GET_ENG_HK_DATA: case CommunicationStep::GET_ENG_HK_DATA:
*id = IMTQ::GET_ENG_HK_DATA; *id = IMTQ::GET_ENG_HK_DATA;