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

Motor Test: allow negative throttle % input #1911

Closed
rmackay9 opened this issue Aug 3, 2018 · 5 comments
Closed

Motor Test: allow negative throttle % input #1911

rmackay9 opened this issue Aug 3, 2018 · 5 comments

Comments

@rmackay9
Copy link
Contributor

rmackay9 commented Aug 3, 2018

It would be great if the Initial Setup >> Motor Test page allowed the user to provide a negative throttle percentage to indicate that they want to spin the motors in reverse. This might only be valid on Rovers and Boats although allowing it for all vehicles would probably be fine (it should be and if copters do something bad we could patch their motor test handling code).

The background for this request is recently while helping a developer with a skid-steering rover setup, we discovered that the relays used to control motor direction were reversed (i.e. left motor's relay was attached to flight controller's right-motor-relay control). This incorrect setup could have been discovered more quickly if the Motor Test page supported providing a negative throttle percentage because then the user would have found that they couldn't make the motors spin in reverse.

@Kelly-Foster
Copy link

Useful for us ArduPlane pilots starting to experiment with reverse thrust.

Kelly

@rmackay9
Copy link
Contributor Author

I just wanted to mention that this would still be useful to have. For example this user is having problems getting the ESC setup correct on a rover and it would be helpful if he could test both forward and backwards.

meee1 added a commit that referenced this issue Jun 11, 2019
@rmackay9
Copy link
Contributor Author

@meee1, great thanks! Here's another user support issue from yesterday that will benefit from this change... so thanks again

@meee1
Copy link
Contributor

meee1 commented Jun 12, 2019

@rmackay9 i did the change, but 100% untested in real life

@rmackay9
Copy link
Contributor Author

I've tested this and it works, thanks!

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

No branches or pull requests

3 participants