-
Notifications
You must be signed in to change notification settings - Fork 17.2k
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
Copter: SUMD not working 3.6.5 #10346
Comments
@lvale, is this a regression from 3.6.4 or something new that was expected to work in 3.6.5 but doesn't? |
didn't work before. according to fixes on 3.6.5rc1 this is new |
Great, thanks. That's quite a relief. This is probably something that we should discuss with @tridge |
Adding a Logic trace with SUMD out with SBUS out |
based on data from Luis from issue ArduPilot#10346
@lvale I added the data from your test to the RC protocol test code and it passes fine. It get these channel values: |
based on data from Luis from issue #10346
based on data from Luis from issue ArduPilot#10346
based on data from Luis from issue ArduPilot#10346
Would it be easier, if you let SBUS at the LEDSTRIP pin and set SUMD to the RX1 pin? |
Please reopen this issue if it is still a problem on our stable or master releases. tridge was unable to reproduce with the supplied information. |
Same receiver plugged on RC IN on the following boards, all running Release version 3.6.5 Chibios:
PixHawk 1
MindRacer v2
CUAV v5
PixRacer
RC Receiver GR-12L has the capability of outputting either SBUS or SUMD
When set to SBUS all channels work as expected
When set to SUMD RC receiver is not detected by ArduPilot Copter 3.6.5 (tested both Copter and TradHeli) and no channel gets detected.
Checked with Logic analyser the output of the RC receiver and it is outputting data correctly on both modes.
According to this https://github.com/ArduPilot/ardupilot/blob/Copter-3.6/ArduCopter/ReleaseNotes.txt
this issue wasn't supposed to happen.
Same receiver with other flight stacks works both on SBUS and SUMD
The text was updated successfully, but these errors were encountered: