I have been stuck on this for about a week and a half now and have been slowly driven insane so I’ll cut to the chase:
Technical Information:
FC: Rush Blade v2 F722 Analog | Product page and wiring diagram: https://rushfpv.net/products/rushfpv-rus...v2-version
Betaflight version: 10.9.0 | Where I got it: https://github.com/betaflight/betaflight
Receiver: FrSky R-XSR | ACCST firmware and wiring: https://www.frsky-rc.com/r-xsr/
Transmitter: FrSky Taranis X9D Plus (PRE 2019 with ACCST) | Firmware and such: https://www.frsky-rc.com/taranis-x9d-plus-2/


Problem:
I am attempting to get F.Port to work on UART 5 (in the dump it’s called serial 4), however despite being paired with the Taranis X9D (PRE 2019) and telemetry "working" (see below with only 2 sensors) Betaflight will not see any telemetry output and the graphs of the reciver tab don't change with input (in fact they have no data at all they are just blank). 
Attempted Solutions/Details etc.:
I have flashed the R-XSR with the latest firmware for F.Port firmware for ACCST from the firmware link: ACCST D16 v2.1.1(F.Port firmware update only). I have flashed the latest XJT firmware from FrSky for the Taranis from the link: ACCST D16 v2.1.0. I have updated to the latest version of OpenTX from the companion: 2.3.15. I have checked the wiring more times than I would care to admit:


R-XSR:    FC:
GND ===> GND
+5V ===> VCC (which is set at 5V, have confirmed with multimeter)
S.Port ===> TX-5
Others are for VTX which I have a Rush SOLO but it is unplugged at the moment



I have set what I believe to be the proper Betaflight settings:
Serial RX ON for UART 5 (no “Telemetry output” drop down for F.Port so is left blank)
In Receiver tab, Serial (via UART) receiver mode
Serial Receiver Provider: FrSky F.Port
Telemetry ON


Channel values remain empty, they do not change when I fiddle with the Taranis. I have tried the CLI serialrx_inverted/halfduplex ON/OFF , it is an F7 so they should be theoretically both ON I think. 




I can get the Taranis to pair with the R-XSR, solid green light, solid blue light (not in CPPM Mode). Gains and Loses telemetry on Taranis like normal EXCEPT, it can only ever find 2 sensors: RSSI and RxBt. I have the taranis in D16 mode but only using CH 1-8 for latency. 




I have even gone back and reflashed the R-XSR with the second latest software (since it has the same version number and I am at my wits end at this point):  ACCST D16 v2.1.0. No dice, same thing happens. I'm thinking it must be a reciver transmitter issue somewhere since the Taranis can't seem to find more than 2 telemetry sources but I am not sure. I have flashed and reflashed both the internal XJT D16 RF module and the R-XSR multiple times now. Reformatted SD card and redownloaded the .frk files etc. I live in US so I need the FCC versions. I have NO IDEA what is going on, does the latest firmware not work with opentx 2.3.15? Is it even a firmware issue at all?  Did I not pray hard enough to the Tech gods recently? 

Edit: since the original wiring photos are hard to see with the lights shining while it is plugged in, I have taken some new photos just in case. The wiring is still as described however. You can see the yellow F.Port wire does turn blue there because I am lazy and don't want to crimp those small JST connectors if I can avoid it.

… you have (accidentally) placed your faith in Frsky..I can describe it like being in a “abusive bad relationship” doing everything you can to make it work… non the less .. it doesn’t..
I myself was in that relationship, I reevaluated everything, sought out help.. and with the assistance of the fpv gods.. I was a free man.. out and about to seek out new and better things.. ELRS was the “new shinny”.. I was still “gun shy” and out of my league… with a little persuasion and some encouragement.. I discovered crossfire… and havnt regretted a day.. now I still have a soft spot for my Little(whoops)ones.. and visit them with d-8 .. but my “new squeeze” is tbs..
Just to be honest, I’m not “fully committed” to this relationship.. I feel good about it, it’s nice.. but not exactly sure if it’s gonna be a long term thing…

(21-Feb-2023, 11:21 PM)Rob Axel Wrote: … you have (accidentally) placed your faith in Frsky..I can describe it like being in a “abusive bad relationship” doing everything you can to make it work… non the less .. it doesn’t..
 I myself was in that relationship, I reevaluated everything, sought out help.. and with the assistance  of the fpv gods.. I was a free man.. out and about to seek out new and better things.. ELRS was the “new shinny”.. I was still “gun shy” and out of my league… with a little persuasion and some encouragement.. I discovered crossfire… and havnt regretted a day.. now I still have a soft spot for my Little(whoops)ones.. and visit them with d-8 .. but my “new squeeze” is tbs..
 Just to be honest, I’m not “fully committed” to this relationship.. I feel good about it, it’s nice.. but not exactly sure if it’s gonna be a long term thing…

Ah... I figured that since I already had a Taranis from long ago when my father was into drone stuff I would go with the same company specifically to avoid hiccups like this one regarding cross compatibility. It also seemed to be smart since allegedly the F.Port programing was a joint effort between Betaflight devs and FrSky so I was fairly confident it would be more straight forward. Are you saying that I have made a grave "oopsie"? Though I would still like to solve the problem since I have everything set up and planed for the receiver using one UART, next time I will look into crossfire  and ELRS which I suppose is already better since it is more open source.

I should also note that the UART 2 is set up for GPS and works flawlessly when I connect it up and everything. The receiver however does not work when I change the receiver to UART2 and open UART2 serial rx instead and fiddle with the inversion settings. It seems that my UART ports all work fine but I haven't tested ALL of them. Regardless I know UART2 works fine but not with the receiver so it makes me think that the problem lies elsewhere.

I also still use my Taranis… and as I stated use d-8 for my whoops.. (guilty-I still have a few RXSRs , but NOT updated… the new “Boxer” w/ ELRS has caught my eye, and I can use my crossfire module with it …
I bought my stuff used, the Frsky protocol was my first encounter.. I had no idea there were others. I actually thought Frsky and Flysky were the same.. thought it may have been “autocorrect”…
Honestly I may have stayed with Frsky has they not pulled this BS “update” with no D-8 support.. even with the 50ft failsafes.. if the new RXs fixed it.. I may have never gone crossfire ..

(22-Feb-2023, 07:24 PM)Rob Axel Wrote: I also still use my Taranis… and as I stated use d-8 for my whoops.. (guilty-I still have a few RXSRs , but NOT updated… the new “Boxer” w/ ELRS has caught my eye, and I can use my crossfire module with it …
 I bought my stuff used, the Frsky protocol was my first encounter.. I had no idea there were others. I actually thought Frsky and Flysky were the same.. thought it may have been “autocorrect”…
  Honestly I may have stayed with Frsky has they not pulled this BS “update” with no D-8 support.. even with the 50ft failsafes.. if the new RXs fixed it.. I may have never gone crossfire ..

What exactly do you mean by no D-8 support? As in no support for 8 channels? As far as I know in the Taranis model setup you can choose D-16 and then simply limit the number of channels used manually my lowering the second number of the channel range.  Also my Taranis after I have gone through all the updates an such listed still has an option to change to D-8. The FrSky website link however does not have a firmware link for D-8 only D-16. Is there a functional difference between using D-16 on 8 channels and D-8? Other than possible incompatibility with older D-8 receivers?

All of your wiring and Betaflight settings look correct to me.

There have been a number of issues with Betaflight 4.4.0 due to the fact that it now builds firmware on-the-fly using a cloud build system whereby it only compiles in features that are needed / selected. It's possible that there's an issue with FPORT in Betaflight 4.4.0 whereby the code for it isn't being correctly compiled into the firmware for the Blade_F7 Betafight target. I don't know.

To eliminate (or confirm) Betaflight 4.4.0 as being a possible cause of the issue I suggest going back to Betaflight 4.3.2 and/or Betaflight 4.2.11 to see if it works under either of those older versions.

(23-Feb-2023, 12:28 AM)SnowLeopardFPV Wrote: All of your wiring and Betaflight settings look correct to me.

There have been a number of issues with Betaflight 4.4.0 due to the fact that it now builds firmware on-the-fly using a cloud build system whereby it only compiles in features that are needed / selected. It's possible that there's an issue with FPORT in Betaflight 4.4.0 whereby the code for it isn't being correctly compiled into the firmware for the Blade_F7 Betafight target. I don't know.

To eliminate (or confirm) Betaflight 4.4.0 as being a possible cause of the issue I suggest going back to Betaflight 4.3.2 and/or Betaflight 4.2.11 to see if it works under either of those older versions.

I have not thought of that possibility. After redownloading the Betaflight configurator (now 10.8.0) and reflashing the F7 with BLADE_F7 4.3.2 firmware, not much has changed as of now except the graphs on the receiver tab DO show SOMETHING now which is a step up. 
Still no response to inputs though.

I'm assuming that you still have the S.Port pin of the R-XSR connected to the TX5 connection on the FC. Is that correct?

Can you please post a fresh "dump" and "diff all" from your Betaflight 4.3.2 setup.

(23-Feb-2023, 01:26 AM)SnowLeopardFPV Wrote: I'm assuming that you still have the S.Port pin of the R-XSR connected to the TX5 connection on the FC. Is that correct?

Can you please post a fresh "dump" and "diff all" from your Betaflight 4.3.2 setup.

I am a moron, I forgot to toggle the serial rx duplex/inverted after reflashing. It now picks up my inputs in betaflight. The Taranis now is SLOWLY finding new sensors and has about 15 now but some of them are of questionable accuracy. Like how Tmp 1 reads 30002 degrees C while Tmp 2 simultaneously reads 0 C. Plus there is a second Tmp 1 at 48 C which is much more realistic but still a little on the warm side. Likely the cpu. It would also appear to be discovering a new sensor every time I reboot the thing?

OK, so it looks like FPORT is working under Betaflight 4.3.2. That either means there is a bug in Betaflight 4.4.0 or there is a requirement to include some custom defines as part of the build parameters to get it to work properly.

For Betaflight the FrSky "Tmp1" sensor is documented as being the barometer or gyro temperature. I'm not sure that the barometers or gyros used on our FC's even have temperature reporting capabilities which means that number might just be gobbledegook. INAV actually states the "Tmp1" sensor as being used to report the flight mode. So there is conflicting information as to what that particular sensor is for. It's probably up to the flight control firmware developers what they use that sensor for. The "Tmp2" sensor is documented as being for GPS data in both Betaflight and INAV.

TBH, only some of the sensors are useful for real-world stuff, so just use the ones that you think are going to add value. The voltage sensor values (VFAS and Cels) and current sensor value (Curr) are probably the most widely used ones followed by the GPS sensors (if you have a GPS module installed).

Regarding new sensors appearing on each reboot, just do a delete and rediscovery of the sensors until they all appear. Then stop the discovery. You shouldn't get new sensors appearing unless you physically start the sensor discovery option again. The list of sensors should remain static until you do that. Make sure you have at least a metre or two of distance between the transmitter and the R-XSR, so don't put them too close together.

I have R-XSR. But haven't used it. I remember a lot of pain with firmware versions. Some have Telemetry not working. Some have other problems.
Does anybody know the "good" firmware for old ACCST Radio for FCC NA?

(01-Mar-2023, 05:33 AM)romangpro Wrote: I have R-XSR. But haven't used it. I remember a lot of pain with firmware versions. Some have Telemetry not working. Some have other problems.
Does anybody know the "good" firmware for old ACCST Radio for FCC NA?

Here are the old firmware

https://davesdronedesigns.com/frsky-firmwares/

(23-Feb-2023, 02:12 AM)SnowLeopardFPV Wrote: OK, so it looks like FPORT is working under Betaflight 4.3.2.

I try go back from BF 4.4 to 4.3. RXSR Fport telemetry does not work with 2.1.1 firmware..
And it does not work in INAV! I had two issues in one time in two different flight controllers with different firmware BF and INAV..

But it is very strange:
2.1.1 fport telemetry link work successfull when i try to use BF lua script setup from Taranis! I can make all change in BF from this tools! In this case telemetry channel is working! But common telemetries data do not updated in one time.. Why? I do not understand..