Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 OK. The version of OpenTX on the QX7 is one that requires the use of the S.Port connector on the front to be used for flashing receivers. It is version 2.2.2 and prior that meant you could only use the rear JR module bay connector. So you are on a compatible version for the S.Port connector. You always get a slightly lower capacity tested with H2testw than the actual capacity of the card, so that is normal. So your SD Card is all good and your QX7 has a compatible version of OpenTX on it. I'm fairly sure that your R-XSR's are somehow bricked, but I don't know why that has happened. Maybe the firmware file you tried to flash it with is corrupt for some reason, or maybe the ACCST 2.1.0 firmware file has a bug in it that is causing the R-XSR to be bricked. Go to the following web page and upload the firmware file you flashed your R-XSR with to that web page, and then compare the "MD5 file checksum" value displayed with those below. Does your one match the corresponding entry in the list below? http://onlinemd5.com Code: RXSR_ACCST_2.1.0_FCC.frk ----------> 5DC18D3CE40BC5D9C031CEA45EBCBAFE
RXSR_ACCST_2.1.0_Fport_FCC.frk ----> F573CB7869CC3EEE3485E8A1F87F5180
RXSR_ACCST_2.1.0_Fport_LBT.frk ----> 1298C909BF5E92D87A3FA895D3F7065C
RXSR_ACCST_2.1.0_LBT.frk ----------> F629B731A7F2796A25309EFE068EEB03
![[-]](https://intofpv.com/images/collapse.png) • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 Checkum is 100% correct from the file from the SDCARD • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 OK, so that confirms that the file on the SD Card hasn't got corrupted either.
When you power up the R-XSR, are any LEDs on it coming on or does it appear to be dead? • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 Both RXSR reacts normaly. When I turn on Taranis, the red LED will turn off. Video here https://photos.app.goo.gl/zfV7Fx1gEG191FEg9 • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 That is totally bizarre. When you turn on the Taranis, does the green LED come on when the red LED goes out?
So it's all "seems" to be working fine and is bound, but you get no stick movements ans are now seemingly stuck on v2.1.0 of the ACCST firmware with no way to downgrade and supposedly no way to upgrade either if a newer 2.x.x version gets released.
When you try to flash new firmware, you ARE using the socket on the R-XSR aren't you with the other servo cable that was supplied with the R-XSR, and you are also disconnecting the other wire from the FC that is wired from the "P" pad aren't you? • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 I get solid green and blue light when TX is connected. I am using the socket on the RX with the included cable. I have one RXSR out of the quad without any wire connected. Video here... https://photos.app.goo.gl/SxurDt7r2aYgjsBH8 • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 It's a bit difficult to see in your video, but on that connector going into the S.Port socket in the bottom of your X-Lite, it looks like you've got the black wire in the middle pin and the red wire on the right side pin. If that is true then it's incorrect wiring. Can you please confirm what wiring order you are using. The correct wiring order for the S.Port socket from left to right is S.Port (yellow), VCC (red), and GND (black). ![[Image: frsky_taranisX-lite_remote_controle_smar...24x683.jpg]](https://blog.seidel-philipp.de/wp-content/uploads/2018/06/frsky_taranisX-lite_remote_controle_smartport_pins-1024x683.jpg) • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 21-Apr-2020, 06:23 PM (This post was last modified: 21-Apr-2020, 06:25 PM by ericz.) It´s correct, tried 2 cables to be sure. https://photos.app.goo.gl/fRyQ75oKEALgBpFk6 Today when new RXSR came I flashed it without problems. It look like the new firmware changed something. Should I order a new RXSR and DO NOT FLASHING the last firmware? I am serial RX killer :-) • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 OK. I thought I'd call it out anyway just in case because from the the video wasn't that clear. The worrying thing is that you can't even re-flash the version 2.1.0 firmware to the receiver which is supposed the version already on there, So it's like you're now completely locked out of the receiver. I would be tempted to contact the supplier and try to get both the R-XSR's replaced under warranty with a reason of not fit for purpose. If you have the appetite, you could try flashing using FC pass-through, or using the FrSky STK tool (available from somewhere like HERE), but I don't hold out a lot of hope TBH. FC Pass-though Method: https://oscarliang.com/flash-frsky-rx-fc-passthrough STK Tool / Method: https://www.frsky-rc.com/how-to-use-frsky-stk-tool-to-update-firmware • Posts: 41 Threads: 8 Likes Received: 0 in 0 posts Likes Given: 6 Joined: Apr 2020 Reputation: 0 (21-Apr-2020, 06:23 PM)ericz Wrote: It´s correct, tried 2 cables to be sure. https://photos.app.goo.gl/fRyQ75oKEALgBpFk6
Today when new RXSR came I flashed it without problems. It look like the new firmware changed something. Should I order a new RXSR and DO NOT FLASHING the last firmware? I am serial RX killer :-) I wish I had that update cable  • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 Already tried it in the afternoon... I like Oscar´s guides... It can´t find any device... I also swap COM ports... I am finished today, completely
I can contact the seller in Czech republic for replacing... The first one RX is from China :-)
I also contacted the official servis partner of FRSKY in my country about information of repair - he told me the repair of RXSR coast like a half of a new one, he should change the CPU and he doesn´t have any one. Bye :-)
Last question today - I am not sure my FC is working correctly after crash. Is it possible, the RXSR was ok until I connected to my FC? Maybe the flash didn´t brick my RXSR and it caused by FC? The local seller has my FC on stock... • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 21-Apr-2020, 08:14 PM (This post was last modified: 21-Apr-2020, 08:19 PM by SnowLeopardFPV.) (21-Apr-2020, 07:52 PM)ericz Wrote: Last question today - I am not sure my FC is working correctly after crash. Is it possible, the RXSR was ok until I connected to my FC? Maybe the flash didn´t brick my RXSR and it caused by FC? The local seller has my FC on stock... The only way I can see that the FC might have destroyed the R-XSR is if there was some kind of a short circuit across to the UART TX connection for the receiver which then provided more then 3.3V on the S.Port connection. Not impossible I guess but that would be really unlucky and I would have thought that would also do some damage to the MCU on the FC as well if that was the case. If you have any doubts then just get a new FC to be on the safe side. When you get your new R-XSR, I suggest you don't go anywhere near the ACCST 2.x.x firmware. Just stay on the v191128 firmware. Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 (21-Apr-2020, 08:14 PM)SnowLeopardFPV Wrote: The only way I can see that the FC might have destroyed the R-XSR is if there was some kind of a short circuit across to the UART TX connection for the receiver which then provided more then 3.3V on the S.Port connection. Not impossible I guess but that would be really unlucky and I would have thought that would also do some damage to the MCU on the FC as well if that was the case.
If you have any doubts then just get a new FC to be on the safe side.
When you get your new R-XSR, I suggest you don't go anywhere near the ACCST 2.x.x firmware. Just stay on the v191128 firmware. FFF - f*cking Frsky Freaks! I can confirm the last version version 2.x.x ACCST firmware killed my RXSR! 2 times! RX looks paired but no reactions in BF. After the flash I am not able to flash any other version of firmware. 3rd RXSR came today, I flashed ACCST firmware (v191128), with v20180416 for Taranis and................. it´s working! - good advice Leo! Just to be sure - I´ve tried to flash the RXSR v191128 firmware 3 times - without any problem! Thank you for help me to stay in the air!!! • Posts: 21,193 Threads: 583 Likes Received: 8,933 in 6,609 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (23-Apr-2020, 02:19 PM)ericz Wrote: I can confirm the last version version 2.x.x ACCST firmware killed my RXSR! 2 times! RX looks paired but no reactions in BF. After the flash I am not able to flash any other version of firmware.
3rd RXSR came today, I flashed ACCST firmware (v191128), with v20180416 for Taranis and................. it´s working! - good advice Leo!
Just to be sure - I´ve tried to flash the RXSR v191128 firmware 3 times - without any problem!
Thank you for help me to stay in the air!!! That's good news at last. Thanks for the confirmation that everything is fine on the pre-2.x.x ACCST firmware. The next thing to try is to flash the R-XSR to v2.1.0 and see if it then ends up bricked  Only kidding  If I was you, I would raise an official complaint with FrSky that their new v2.1.0 firmware seems to be bricking R-XSR receivers. I'll stick a note in the other thread warning other members of this potential pitfall. • Posts: 122 Threads: 9 Likes Received: 6 in 6 posts Likes Given: 22 Joined: Apr 2020 Reputation: 1 • |
