As mentioned in ArduPilot Copter Release Notes Copter 4.0.0-rc1 25-Oct-2019
says
“9) RC input/output changes:
a) Serial protocols supported on any serial port
b) IBUS R/C input support
c) DO_SET_SERVO and manual passthrough can operate on the same channel”
I have a Problem;
Good result with SBUS but however i can not use IBUS as RC protocol. No pulse in mission planner Radio Calibration window.
Thanks for the report. I don’t know anything about IBUS but I’ll ask around. We should probably have some discussion of how to set this up on this wiki page (but we don’t yet).
There shouldn’t be any special setup requirements beyond plugging it into the RC input of the flight controller just like SBUS.
@peterbarker did a test using his equipment and was able to use it successfully so we suspect that there’s perhaps some differences in the receiver (perhaps different receivers send different bytes).
We think that we will need to create a special debug version of the firmware that outputs all the bytes the receiver is sending to the flight controller and then ask you to run it so that we can look for differences… hopefully we can come up with that debug firmware in the next week or so.
I’m using a Fli14+ Flysky compatible receiver with a Chinese Pixhawk clone and a “hacked” Flysky i6 remote. Worked fine out of the box (connected to RC IN). I’m not getting any messages related to RC, so I guess it is using the IBUS protocol, since the receiver doesn’t support SBUS and I’m getting more than 8 working channels. I’ve configured the receiver to PPM/IBUS using the remote’s settings menu.
On Copter 4.0.7 with a FlySkyFTr10 receiver (TX is a Paladin 18) ibus doesn’t work, MP says “Bad channel 1 input, canceling”.
Switch the RX mode to sbus without modifying the connection (SERV0 to RCIN) and all is fine, calibration runs and MP show RC_IN_MODE as SBUS in the log.
So maybe ibus support is not so good/mature at the moment. ( tow october 2021 )