RC receiver (tbs nano crossfire) is not powered up over telem 2 and possible cause shortage on Cube Orange

Cube Autopilot
1

Hello,

I have issues with my tbs nano crossfire - after installation into pixhawk with cube orange over telemetry port (UART), cube doesn’t emit succes signal, but emit clicking sounds over the buzzer. When it is disconnected, cube gets back to normal work.

Here is more details:

I have checked telem2 port by checking voltage on power and grounds wires of JST-GH cable from telem2 port (red probe on 1st pin, black probe on 6th pin) and it is near the zero.

I have found two or three similar issues over the web. Is it a flaw in the design/implementation of the circuit or just incorrect setup?

Hardware:
HEX Pixhawk 2.1 cube orange+
TBS Crossfire Nano SE V2 RX CRSF 915/868 МГц

2

Most likely a fault with your receiver or incorrect wiring.
The Cube power design has been around a long time running an untold number of peripherals.

The other thing to consider is:

  1. Telem1 has it’s own isolated 5v supply with current limit and protection
  2. All other ports: Telem2, CAN, GPS… all operate from one regulated current limited supply

You could try disconnecting devices to see if the issue goes away, indicating an over-current problem.
Or move the receiver to Telem1, or choose some peripheral(s) to run from a BEC.

In logs you can check Power.Flags the values add up for an overall status.

1   MAV_POWER_STATUS_BRICK_VALID      // main brick power supply valid
2   MAV_POWER_STATUS_SERVO_VALID      // main servo power supply valid for FMU
4   MAV_POWER_STATUS_USB_CONNECTED    // USB power is connected
8   MAV_POWER_STATUS_PERIPH_OVERCURRENT   // peripheral supply is in over-current state
16   MAV_POWER_STATUS_PERIPH_HIPOWER_OVERCURRENT   // hi-power peripheral supply is in over-current state
32   MAV_POWER_STATUS_CHANGED         // Power status has changed since boot

PERIPH_HIPOWER_OVERCURRENT refers to the Telem1 port, and PERIPH_OVERCURRENT refers to everything except Telem1.