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
3.1.7 motor issue on CC3D with PWM receiver #3079
Comments
I think it's on PWM reciever code: it works on 3.0.1 (as it had PWM timer clash protection), and works "bad" at 3.1.x (as it had no PWM timer clash protection). Other input methods (PPM, SBUS, etc) are have timer clash protection. I've bought PPM reciever for my quad and all works fine. |
I tested the latest build ( betaflight_3.2.0-1271-968d2c2.zip ) with same result. Not working with PWM receiver. Unfortunately i can't use PPM or other then PWM with my HobbyKink HK-T6 remote controller. I rolling back to 3.0.1 |
szepnorbee I can confirm your initial issue - although my board was unfortunately a clone CC3D ( which I did not know when I bought my RTF quad ). |
@szepnorbee I think you can add PWM -> PPM(sbus) decoder (physycal module) between your receiver and FC controller input. It's not good problem solve, but it cheaper then new remote controller and reciever pack. |
I can confirm this issue too. I configured my CC3D to PWM receiver and 3 motors did not work. |
See my note on #2780. Make sure channels 1-4 are not going to failsafe mode. Possibly because of a minimum pwm signal being hit. I was seeing nothing on channels 1-4 in receiver tab for 3.1.7 and going back to 3.0.1 it would work fine. |
Hi! I have an issue with CC3D. I uploaded the 3.1.7 firmware succesfully, but not all correct. On QuadX configuration if i select PWM receiver (one wire per channel) 3 of the 4 motor stopped working. If i select PPM input then all fine (all 4 motor activated) but i can't have PPM receiver. Help me please! This is a bug?
My config:
Copter: QuadX
ESC mode: PWM (not OneShot etc.)
Receiver mode: PWM (one wire per channel)
Chanel map: 2T1AER34
Thank you!
The text was updated successfully, but these errors were encountered: