Orange Cube Plus – SBus Port Not Reading Input

Cube Autopilot
1

Hello,

We recently purchased an Orange Cube Plus for use in one of our production drones. Unfortunately, the SBus port does not detect any input

Here’s what we’ve tried so far:

  • Verified SBus receiver is functional on other flight controllers.
  • Checked wiring and connector continuity.
  • Tested with different SBus receivers and cables.
  • Confirmed firmware is up to date.

Despite these steps, the Cube Plus still does not read SBus. I have searched through forum posts and documentation but haven’t found a working solution.

I’m posting here to:

  1. Report the possible hardware fault.
  2. Confirm if this is a known issue with the Cube Plus SBus port.
  3. Check if there are any troubleshooting steps we may have missed before sending the unit back.

Any advice or confirmation would be greatly appreciated.

Thank you,

2

The SBUS pins are output (like to a gimbal) - the RCin pins accept SBUS input and whole range of receiver protocols.

BRD_SBUS_OUT controls the SBUS output rate

RC_OPTIONS set some RC input options, no need to change this usually

RC_PROTOCOLS can be set for specific protocols if you require, but Auto is OK

They are bitmask values, so best to use MissionPlanner to set them

3

Hi, I am referring to the RCin Sbus

4

What receiver ?
Got a photo of the Cube/carrier and receiver connected ?

It’s odd because I’ve never seen a failed RC input - but then I’ve not seen everything…

1 Like
6

I flashed PX4 then Ardupilot and restored my parameter now everything is working fine.

Thank you for replying to my topic.

Really appreciated.

1 Like
7

Strange, but good that it worked.

8

Yes it was a strange experience, but I am glad it is working now.
I wish I could tell why.

but Shawn I have a different problem and maybe you can assist me resolve.

I have another Orange Cube+ flight controller and I’ve connected an ESP32 dev board to the GPS1 serial port.

What I’m seeing:

TX from GPS1 works fine — I can receive MAVLink heartbeat messages from the Cube+ on my ESP32.
RX from GPS1 does not seem to work — the Cube+ does not respond to any MAVLink messages I send from the ESP32.

Setup details:

Flight Controller: Orange Cube+
Serial Port: GPS1 (Serial 3)
ESP32 dev board running custom code (successfully tested with another FC)
Wiring: TX–RX crossed, GND shared
Baud rate: 57600 (also tested at 115200)
Protocol: MAVLink1/2
Power: FC powered via USB/battery
Firmware: ArduCopter (latest stable)

What I have tried so far:

Verified wiring (TX to RX, RX to TX).
Tested ESP32 code and wiring on a different flight controller — works perfectly (can send/receive MAVLink messages, read RC channels, etc.).

Changed SERIAL3_PROTOCOL to 1 (MAVLink), tested other ports as well.
Changed baud rate via SERIAL3_BAUD — same result.

Question:

Is there anything specific to the Cube+ GPS1 port that could block incoming MAVLink messages?

Could there be a parameter or hardware setting preventing RX on this port?
How can I troubleshoot whether this is a hardware fault or a config issue?

Thanks in advance for any help!

9

No, “GPS1” is merely the silkscreened label and the default purpose.

Probably provide a .param file so we can see all the parameters.

10

Not so strange he probably somehow had his SBUS removed from the RC_PROTOCOLS and the PX4 and back set it back to default.

11

Interesting, and how does that happen?
is there a parameter to remove and add the something into RC_PROTOCOLS ?

12

3 1970-01-01 02-00-00.bin (460 KB)

here is .bin file

Thank you

13

Copy the SR1_ values to SR3_ so the flight controller knows to send updates out that port, and at what rate.

EDIT: your ESP32 should be able to request mavlink data if comms is working properly.
Are you having trouble sending from the Cube or receiving mavlink commands from the ESP32 ?

14

I copied the parameter and nothing happened still no message received in mission planner,
I want to receive messages from the ESP32

15

You may want something like this then:

You might need to reorganise what devices are on which serial ports though.