bitcraze/crazyflie-firmware#903 changed the semantics of notifySetpointsStop and removed the need for the remainValidMillisecs argument. We should update the docstring. We could also remove that parameter from the ROS service definition.
From the current search results, it seems that notifySetpointStop is not documented at all on the Bitcraze website. Even though it is not implemented in crazyflie-lib-python yet, it should still appear somewhere in the CRTP protocol docs. After updating our docstring, we could submit the same description there as a PR.
bitcraze/crazyflie-firmware#903 changed the semantics of
notifySetpointsStopand removed the need for theremainValidMillisecsargument. We should update the docstring. We could also remove that parameter from the ROS service definition.From the current search results, it seems that
notifySetpointStopis not documented at all on the Bitcraze website. Even though it is not implemented in crazyflie-lib-python yet, it should still appear somewhere in the CRTP protocol docs. After updating our docstring, we could submit the same description there as a PR.