Once I update the pre v2.0 r-rxr firmware into the receiver what is the equivalent ACCST firmware for the TX? As I could not find the cable anywhere I ordered another
R-XSR just for the update cable, which is shipped from RDQ and should receive it in few days. Just trying to get mentally prepared for the next steps.

(23-Apr-2020, 07:37 AM)rockford007 Wrote: Once I update the pre v2.0 r-rxr firmware into the receiver what is the equivalent ACCST firmware for the TX?

You don't need to worry about the ACCST firmware on the internal XJT module of the QX7. The last pre-2.x.x update for that was way back in March 2017, so unless you have a really old QX7 then the internal XJT module will already be on the latest pre-2.x.x release of the ACCST firmware.

I would just make sure you're on the latest 2.3.7 release of OpenTX and that is all.

Ok, so I got the new RXSR receiver with the update cable (yay!) now I am on my way to update the v1.9 firmware,
In the zip folder following files are there, I believe based on my wiring done by iFlight I have to use the 3rd file (FPORT_FCC)?

RXSR_FCC_ACCST_191112.frk Firmware under NonLbt mode which is certificated for FCC rules.
RXSR_LBT_ACCST_191112.frk Firmware under LBT mode which is certificated for CE rules.
RXSR-FPORT_FCC_ACCST_191128.frk F.PORT version firmware under NonLbt mode which is certificated for FCC rules.
RXSR-FPORT_LBT_ACCST_191128.frk F.PORT version firmware under LBT mode which is certificated for CE rules.

Your R-XSR is wired to the iFlight Succex-E F405 board for SBUS communication, so you need to use the first firmware file -> RXSR_FCC_ACCST_191112.frk

And once you've flashed the R-XSR and have connected it up, don't forget to switch "Serial RX" ON for UART2 and OFF for all other UARTs. Then also run the following CLI commands to ensure that the receiver protocol is set up correctly for SBUS...

wow and all these days I was under impression it is connected as FPORT and was about to flash fport..

(25-Apr-2020, 01:54 AM)rockford007 Wrote: wow and all these days I was under impression it is connected as FPORT and was about to flash fport..

For it to be connected for FPORT, the S.Port pin on the R-XSR would need to be connected to the nT2 pad on the flight controller, but we already know there is some kind of design fault on these iFlight F4 boards whereby the nT2 pad doesn't allow bi-directional communications which is needed for FPORT to function correctly.

You can of course do the FPORT uninversion hack and connect a wire from the minuscule "P" pad on the R-XSR to the T2 pad instead which will work for FPORT, but that was probably too much hassle for iFlight to want to bother with, plus R-XSR's come flashed with SBUS firmware from the factory, so iFlight probably couldn't be bothered reflashing all the R-XSR's so just lashed them in with an SBUS only connection which is a poor show because that doesn't even give you telemetry back to the transmitter.

when I clicked the flash button after selecting the FW it is asking me to select
"Flash S.Port"
"Flash ext Module"
Flash int Moduile" etc....
should I select S.port or ext module?

You should connect the R-XSR to the bottom port of your QX7 using the wiring order shown below and the select "Flash S.Port".

Flashing complete.

Ok so after flashing firmware in RX, I still don,t see stick movement, and after selecting UART2 in receiver tab the quad image in bottom right rotating like crazy, and I can now see some effect in the AUX channels, so if I change the position of the AUX switches then AUX1 - AUX3 bars are moving. But nothing in AERT yet.

(I have yet not flashed TX firmware, was testing status.)

Hello,

I was finally able to establish the connection and now can see the receiver showing input of stick movement.

It is hard to say what exactly went wrong.
I flashed the firmware of R-XSR to v1.9* version then made the changes as snowleopard suggested, but after that I was only getting response of Aux switch movements but not for sticks, that made me believe that it is not like RX is not getting any input at all but something is wrong with the 4 channels of the sticks.
Then I looked into the home screen and found that the tiny circle that moves in a square box showing the stick movements was missing. I had no idea why is that happening so instead of updating TX firmware I just clicked the restore to factory setting and calibrated sticks and voila! receiver started showing the response. 

Initially I had a hick up assigning the channels as pitch was showing throttle, yaw was showing roll and so on, so made the adjustment in betaflight.

Now I can arm disarm and watching other videos to take the next steps, I may open another thread if I get lost again 

This thread can be marked solved if you all agree...

Thanks again to show path to this beginner, I was almost at the edge of giving up after trying to bind for two weeks.. 

Good news