(27-Jun-2021, 07:50 AM)ProfDrYoMan Wrote: Thanks. I am still in contact with the iFlight support. Lets see if this works out.

iFlight support is usually quite useless and I predict that they won't be able to solve the issue but will instead offer you a discount on another one of their (poorly designed) FC's. If they do that you are better off just cutting your losses and the hours wasted by purchasing a different FC from a different manufacturer.

Please let us know what the outcome is.

On a side note, if this is a newly purchased BNF quad then your best option would be to contact the vendor and return the whole quad for a full refund with a reason of "not fit for purpose".

I for sure will inform you. Last email (after many useless) was from a hopefully good support guy. I linked to this thread beginning with my posts, so I guess they/he will anyhow read this.

I will spend some time on their suggested solutions (to come), lets see.

Have you try other UART?
If you are using the "uninverted" output, any UART should work.
Also stick with FPort so the wiring/configuration is more simple.

Honestly I would recommend moving to Crossfire now (or if you are tech savvy, go for ELRS). I haven't use Frsky for 2 years now except on tiny whoops.

Hi Oscar, nice to see you chime in.

Fport might be more simple but needs working bidirectional inverted UART.
The wiring diagram shows a version with Fport, but ...
Latest release of R-XSR LBT Fport FW has a known bug which leads to a stopping Fport after some seconds.

I a fine in "donating" a UART for Sport, if it will just work.

I tried all UARTs TX (but the one used for OSD) in UART and softserial mode. None of them is working with the hacked (positive) Sport. The signal captures I did clearly show that the RX is querying, but no answer from the FC.

The RX type does not change anything her, I would say. There is something broken/wrong with the FC.

Ok, I am done.

Used the stock dump after reset and tried:

- T6
- T4
- T1 (nothing else connected to UART1)
- LED STRIP softserial (nothing else connected to LED STRIP)

With SPORT telemetry on hacked (uninverted SPORT) output. Nothing. Nothing in the captured traces as above.
I did try all 4 combinations for set tlm_inverted and set tlm_halfduplex.
I even tried older BF (4.2.0) variant for all above tests.

What puzzles me is, that the UART4 is working in fullduplex with the GPS when configured.

I am giving up and blaming iFLight.

End of the topic:

I got a very well reduce price for a E7 type board and it works (easy drop in). So at least iFlight did act nice for me. Just wanted to inform you on that.

Ok for those that are still struggling with this issue, I've managed to get full Telemetry working on myNazgul 5 V2 and Xlite-S using the R-XSR and BF2.3.9 that was pre-installed.

---------------------------------------------------------
UPDATE:
ACCESS apparantly Sucks!!
I had failsafes within 50 meters behind me and random sensor losts.
I went back to ACCST16 firmare 2.1.0, left settings as descibed below.. only other change I had to make in betaflight was:
set rssi_scale=200
this to correct the OSD RSSI value to match the sensor output on my radio.
---------------------------------------------------------

Here is what I evenually ended up doing:

Wiring

• Remove the yellow cable from the plug on the side of the receiver and place it the position for the S-Port (next to the red wire)
  
• Remove the same yellow cable at the other end and place it outer position of the plug T2 on the FC (2 positions next to black)
  Since OP doesnt have this T2 pad, you could try to use a different T pad or plug...?
  

Radio Setup

• Update the radio to ISRM firmware 2.1.0 version 2.1.6 might work, I dunno, IDC, I'm done trying. 
  
• Installed the latest ACCESS (2.1.7) firmware onto the R-XSR receiver using the S-Port on the radio.
  (Check wire orientation of the provided cable! I received one with black and red wires reversed.. From left right it should be Yellow/Red/Black)
  
• Bind the R-XSR using the ACCESS mode. (Not ACCST)
  After registering and binding stay in that menu go down to receiver 1 [RXSR] (or the number that you assigned) and press for options.
  
• In this submenu tick the F-Port option to enable it on the transmitter and go back to save these settings to the R-XSR.
  

BetaFlight Settings

• In Ports Tab I made no changes. But If you selected a different UART instead of T2 U might need to change the Serial RX column
  
• In the Receiver Tab set Serial Receiver Provider to: FrSKy FPort and enable the Telemetry option below that
  
• Save and go to the CLI tab and type or copy/paste the following commands:
  
  set serialrx_Provider=FPORT
  set serialrx_inverted=ON
  set serialrx_halfduplex=ON
  save
  

 
Now after reboot you might need to scan for new sensors on the radio. If this didnt help you, I dont know what to tell you.. I'm just sharing how I got telemetry working for me on this rig. 



Another tip: dont forget to long press the hold button on the R-XSR to enable SBUS/Fport output (blue light on)..

Good luck to all.
Sir Brokalot