Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream update MAV_CMD_DO_MOTOR_TEST #264

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

amilcarlucas
Copy link

No description provided.

<param index="1" label="Instance" minValue="1" increment="1">Motor instance number (from 1 to max number of motors on the vehicle).</param>
<param index="2" label="Throttle Type" enum="MOTOR_TEST_THROTTLE_TYPE">Throttle type (whether the Throttle Value in param3 is a percentage, PWM value, etc.)</param>
<param index="3" label="Throttle">Throttle value.</param>
<param index="4" label="Timeout" units="s" minValue="0">Timeout between tests that are run in sequence.</param>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is actually incorrect for ArduPilot. It specifies the duration of the test, as well as the interval between.

I think the original concept was the user would manually cancel the test by sending another message, but that a timeout would be specified in the message. As soon as we added the "Motor Count" parameter this became weird.

ArduPilot is in two minds about how this should work. Comments indicate that there's a fixed pause between each motor. Other comments say it spends half this time with motors on and half off. In actuality it's... weird.

In any case, the change here isn't right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants