Hey out there; I'm having some issues getting my FC to receive input data from my receiver. I've got the receiver wired according to the FC manual, I've checked all of the connections, and I've tried two different receivers (one off of a fixed wing that I had just been flying so it should be good) and both bind and send back telemetry to the radio.
I've pretty much boiled it down to it being an IO setup issue, but I don't know how to read the dump to figure that out.

Here's the rundown on parts:
FC: HGLRC Zeus5 - Manual
Receiver: Crossfire nano rx (not the pro)
Radio: Tango 2 pro v3

This should be wired according to the manual and I continuity tested that the two pads R2 and RC to ensure that they are jumped.
(Sorry, best image I could get with my phone)


The wiring should match the output map configuration as I set it up in the radio.


I attached the dump as a text file; let me know if there is anything else I need to post up for information.

It’s hard to tell from your photo, but it looks to me like you have Channel 1 (crsf tx) going to pad t2.
That means you probably have channel 2 (crsf rx) going to pad rc/r2.

If this is the case, try swapping those wires around.

When wiring to a flight controller, tx goes to rx, and rx goes to tx.
Basically, tx means transmit, and rx means receive- and if one thing is transmitting (tx), you want the other thing to receive (rx).

I’m not near a flight controller to try loading your dump to see your settings at the moment, but here’s the important things to set in betaflight after you’ve sorted out your potential wiring issue:

In the ports tab in betaflight, enable serial rx on uart2 (only enable it on uart 2). Don’t select anything in the drop down menus for this uart. Hit the save button.

In the receiver tab in betaflight:
In the drop down menu for “Receiver Mode”, select “Serial (via UART).
In the drop down menu for “Serial Receiver Provider”, select “CRSF”.
Hit the save button.

BTW, thanks for including a link to the manual for your FC, it makes it much easier to help when I don’t have to hunt down a pin out for the board.

(22-Feb-2023, 06:27 AM)Lemonyleprosy Wrote: It’s hard to tell from your photo, but it looks to me like you have Channel 1 (crsf tx) going to pad t2.
That means you probably have channel 2 (crsf rx) going to pad rc/r2.

If this is the case, try swapping those wires around.

When wiring to a flight controller, tx goes to rx, and rx goes to tx.
Basically, tx means transmit, and rx means receive- and if one thing is transmitting (tx), you want the other thing to receive (rx).

Right you are! I guess I needed another pair of eyes. I appreciate the catch; thanks!

(23-Feb-2023, 04:03 AM)Foxpope Wrote: Right you are! I guess I needed another pair of eyes. I appreciate the catch; thanks!

Does that mean you're now getting movement in the receiver tab in betaflight or you are now in the air?

(23-Feb-2023, 04:07 AM)Lemonyleprosy Wrote: Does that mean you're now getting movement in the receiver tab in betaflight or you are now in the air?

Had a few other issues (forgot to hit the reversed motor direction switch etc.), but I am now in the air!

Awesome! Happy flying!