Hi all, I and now at a complete loose end. Receiver inputs are not coming through in Betaflight (i.e the bars aren't moving when I wiggle sticks)

I have updated my FC MABAF722 to BF 4.2.9, receiver to latest Firmware (FrSky R-XSR FW_ACCESS_v2.1.7) and radio is all up to date too.

Receiver binds ok with green light (receiver is in SBUS mode not CCM, i.e. blue light is on), receiver get telemetry, and the bind menu is set to Receiver1 RXSR is set to FPORT under the RX options.

I even swapped out another R-XSR from another quad and it does the same, but works fine in another quad.

What am I doing wrong......

Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Please also post some good clear photos of the actual wiring and connections between your receiver and flight controller.

(29-Sep-2021, 04:57 PM)SnowLeopardFPV Wrote: Can you please run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Please also post some good clear photos of the actual wiring and connections between your receiver and flight controller.

Sure, receiver wiring added and txt of dump.

If it works in a different quad properly, but not on that quads.. I’m betting it’s a config issue..

(29-Sep-2021, 07:14 PM)Rob Axel Wrote: If it works in a different quad properly, but not only the quads.. I’m betting it’s a config issue..

yeah the R-XSR board is ok, I just don't know what else in the config is not right. Telemetry is working, just not the radio inputs. Never seen this issue before.

(29-Sep-2021, 07:25 PM)Synadex Wrote: yeah the R-XSR board is ok, I just don't know what else in the config is not right. Telemetry is working, just not the radio inputs. Never seen this issue before.

You have the R-XSR wired up for SBUS / S.Port (two wires) but you've selected FPORT as the protocol. Which protocol are you wanting to use?

Fport. Just added SBUS to the RC pad it in case down the line I change mind rather than lift it out of the connector. Have done this in the past with no issue. So if I remove the SBUS it cable it will work?

I'm not sure if having the SBUS wire still connected when using FPORT causes any issues. I've never tried it, but it might be wise to remove the yellow wire pin from the plug of the R-XSR.

You do have the F.Port option ticked on your transmitter don't you? See the following post for where to find that option...

https://intofpv.com/t-r-xsr-fport-connec...#pid106590

(29-Sep-2021, 08:44 PM)SnowLeopardFPV Wrote: I'm not sure if having the SBUS wire still connected when using FPORT causes any issues. I've never tried it, but it might be wise to remove the yellow wire pin from the plug of the R-XSR.

You do have the F.Port option ticked on your transmitter don't you? See the following post for where to find that option...

https://intofpv.com/t-r-xsr-fport-connec...#pid106590

Yeah I thought I added those photos

Will try and lift out the SBUS wire and see what happens

(29-Sep-2021, 08:44 PM)SnowLeopardFPV Wrote: I'm not sure if having the SBUS wire still connected when using FPORT causes any issues. I've never tried it, but it might be wise to remove the yellow wire pin from the plug of the R-XSR.

You do have the F.Port option ticked on your transmitter don't you? See the following post for where to find that option...

https://intofpv.com/t-r-xsr-fport-connec...#pid106590

nah no luck, pulled the SBUS wire and the TX via FPort is still not taking stick inputs. Telemetry still works though.

I’ve never gone into the f-port config on these RXs .. I got my first rig used, the controller was already set up.. the quad had a toasted (F3) fc,,, the RX was simply wired +/- & sbus…so I just continued from there…

(30-Sep-2021, 10:04 AM)Synadex Wrote: nah no luck, pulled the SBUS wire and the TX via FPort is still not taking stick inputs. Telemetry still works though.

One thing that isn't clear with some of these F7 FC's that have a pad specifically marked for S.Port/F.Port is whether or not that pad has an inline hardware inverter between it and the MCU pin. All F7 MCUs natively support signal inversion without the need for an inline inverter so if manufacturers are putting dedicated S.Port/F.Port pads on their F7 FC's which has an inline hardware inverter like they needed to for F4 MCUs then they are just confusing things, and if the inverter isn't bi-directional then it will only allow data to flow one way meaning the MCU will only get either RC command data from the transmitter or telemetry data back, but not both. So maybe this is the issue on some of these F7 FC's. I wonder if these manufacturers ever actually tested the use of F.Port on their F7 FC's which have a dedicated S.Port/F.Port pad.

The easy option is to just try using the TX pad of a different UART instead, but it would be nice to find out if Diatone are using an inline inverter on their F7 FC's or not. You can test the theory by using a multimeter in continuity mode to see if the S.Port/F.Port pad has a direct connection to the PB6 pin on the MCU (pin #58 in the pinout diagram below). If it doesn't then it means that there is a hardware inverter somewhere between the pad and the MCU pin.

Thanks!

So I tied the uninverted on a R-XSR for another F4 quad and no luck on the TX1 pad. (With abs without half duplex and inversion) .

Rally wanted to resist opening the whole quad up again after doing a neat and tidy build (chips on the underside between ESC).

Gonna try a different tx pad and then failing that I guess it’s full drone surgery, as am gonna have to located VBAT on chip to find pin #58.

Sigh.

Incidentally I can’t seem to get SBUS in isolation working either

Just found SnowLeopardFPV that you have advised on this issue before, I didn’t find those posts originally I don’t know why.

From the sound of it the move to a different tx pad will sort it, but will do the chip check to see if it has an inline inverter.

Yes, we have seen this problem more than once. I really have no idea what Diatone have done to butcher the TX1 connection on their F7 FC's. Unfortunately I don't own one that I can do any diagnosis on.