MAVSDK
MAVSDK copied to clipboard
Module range mismatch in "ActionImpl::set_actuator_async" function
Hi, I think I might have just found a minor bug in the "set_actuator_async" function. The range in the switch...case statement goes from 1 to 6 while the range of the module function (index % 6) goes from 0 to 5. So, param6 will never be set and if (index==6), then param7 will be equal to 1 and the whole command will be ignored by PX4 handle_message_command_both function.
If I understood correctly, at the moment PX4 only pays attention to 3 AUX outputs, namely param1, param2 and param3... so this bug should not have any effect on the whole system behavior.