v1.15.0 #311
@ -62,11 +62,7 @@ void ImtqHandler::doStartUp() {
|
||||
void ImtqHandler::doShutDown() { setMode(_MODE_POWER_DOWN); }
|
||||
|
||||
ReturnValue_t ImtqHandler::buildNormalDeviceCommand(DeviceCommandId_t* id) {
|
||||
// TODO: Add IMTQ torque handling here, will be set in the software and thus must be part
|
||||
// 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.
|
||||
// Depending on the normal polling mode configuration, 3-4 communication steps are recommended
|
||||
switch (communicationStep) {
|
||||
case CommunicationStep::GET_ENG_HK_DATA:
|
||||
*id = IMTQ::GET_ENG_HK_DATA;
|
||||
|
Loading…
Reference in New Issue
Block a user