-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
BL_HELI: Reverse throttle by RC Switch spins the motor in the wrong directions #28476
Comments
No, I don't swap any cables in the process. If ESC is configured "normal" direction, motor spins in the correct "forward" direction. I can fix the whole configuration thing if I set the ESC to "3D (forward/reverse) REVERSED". I currently don't have a PWM controlled ESC to test if it works correctly in PWM control and just wrong in DSHOT. |
What parameters have you set? |
My latest config for the Drift Motor is on Channel1. Additional Changes have been according to guide. ESC set to bidirectional non-inverted via ESC-Configurator tool. |
The ARWingPro (Matek F405 Wing V2 + Holybro Tekko32 F4 45A ESC) still has this test setup. It works in correct directions with the attached parameter file and ESC set to bi-directional + reversed. The motor direction is also correct if none of the check-boxes is selected, (i.e. not bi-directional and not reversed). |
Pretty sure this is a bug I fixed in 4.6, please can you try the latest? |
Sorry, it is the same behavior in 4.6. |
I think you are getting bitten by SERVO_DSHOT_ESC - you have configured this and so AP will send the dshot commands to reverse, so given that you have already reversed in the configurator the setup will be inverted. Remove the static setting from the configurator |
For the test with AP 4.6, I did not reverse the ESC via Configurator. I'm seeing the same issue as before. If ESC is configured normal, then direction is forward. If ESC is configured bi-directional and not reversed, then direction is backwards without reverse-thrust and vice-versa. The dshot esc is for propeller efficiency measurements and with AM32 I can't go back to PWM controlled modes anyways. Can I debug this DSHOT stuff somehow via logs? |
So wait, it works on this setup but not the other? |
I don't think this supports bdshot, I am not sure what the implication for 3D is. Should work but who knows. Other possibility is that dshot commands are not working properly. |
Yes the ARWingPro with the ESC set to bi-directional and reversed has a correct working Reverse Thrust.
Observation tells, no implications, it just does not evaluate the ESC telemetry. |
Bug report
Reporting a minor issue with motor direction with 3D enabled BL_HELI compatible ESCs. Observed with Bluejay and AM32 firmware, both DSHOT600 protocol. Can be fixed by changing ESC to "3D (forward/reverse) Reversed".
Issue details
While following the guide for Reverse Throttle via RC_Switch
https://notes.stavros.io/ardupilot/reverse-thrust/
I observed that the resulting directions are wrong.
After setting the ESC to 3D (forward/reverse) via ESC-Configurator Online tool and changing the parameters according to guide,
the default motor direction produces reverse thrust. After switching to Reverse Thrust followed by the GCS message that Reverse Thrust is enabled, the motor direction produces positive thrust.
Version
Ardupilot 4.5.7
Platform
[x] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
Airframe type
Hardware type
STM32F405 based FC with
Logs
The issue does not show in logs but is observed visually on the bench.
The text was updated successfully, but these errors were encountered: