Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
No RSSI on F.Port R-XSR with ACCESS 2.1.0
#1
For those of you who are using R-XSR receiver with F.Port connection flashed with the latest ACCESS 2.1.0 and missing RSSI (0 value in OSD/Betaflight) you can try attached FW beta version.


Attached Files
.zip   RXSR_ACCESS_2.1.0_20200506.zip (Size: 138.21 KB / Downloads: 91)
[-] The following 1 user Likes pike's post:
  • SnowLeopardFPV
Reply
Login to remove this ad | Register Here
#2
EDIT 14/05/20: So today FrSky "released new FW version" on their webpages. They silently changed the file under the last released 2.1.0 (now it is the same file as attached here) and didn't change version, even release date. The only change in release notes is point 7: "Press button for 5 seconds will have RSSI output in channel 16 of SBUS." This version still has another bug - it sends RSSI level info via F.Port in dB, so Betaflight displays max RSSI as 109 % in setup info tab and OSD will crop it to 99.
[-] The following 1 user Likes pike's post:
  • SnowLeopardFPV
Reply
#3
Thanks for posting the updates. Hopefully it will help others who find themselves in the same situation. It's a bit sneaky of FrSky to release the fix under the same version number and date. It should at least be version 2.1.1 with a revised date so people who installed the older revision of the same version know they need to update to get rid of the bug. I guess FrSky don't want to admit their cock-up. I expect they will do the same for the RSSI issue once they fix that one too. Nice to see that FrSky are being open and transparent, as per usual...NOT Rolleyes

We see so many ACCESS related issues that it makes me glad that I didn't buy into the FrSky ACCESS ecosystem, but other people have so any information and support like this is really helpful.

EDIT: Just to note that the firmware they released is exactly the same as the one in the ZIP file you attached to the first post of this thread. So it looks like FrSky didn't make any further changes after that version they sent out for testing with.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Help FrSky r xsr receiver not entering bind mode August 1 129 05-Mar-2024, 08:49 PM
Last Post: August
  Charging a Radiomaster X16S via case bottom USB C port BadRaven 0 173 13-Feb-2024, 12:04 PM
Last Post: BadRaven
  Help Binding Jumper T-Lite with R-XSR miudi12732 36 12,382 08-Feb-2024, 02:55 AM
Last Post: mstc
  Help FrSky Archer RS to Speedybee F405V4 through F.Port trecords 0 141 28-Jan-2024, 09:10 PM
Last Post: trecords
  Help RSSI does not display correctly on OSD l_eon 8 1,953 04-Jan-2024, 10:28 PM
Last Post: SnowLeopardFPV


Login to remove this ad | Register Here