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
FrSky XM + Taranis Q X7, Problem with connection and firmware
#1
Good afternoon!
I decided to buy the first quadrupter. I bought a set of Vantac Q100 and Taranis Q X7. I could not connect Taranis to the receiver (FrSky XM). I tried to reflash the receiver according to the instructions https://oscarliang.com/flash-frsky-rx-firmware/. Taranis wrote (FW update error, version request, failed). Now when the receiver is connected to the FC, only the red light is on it. Both in bind mode and in normal mode. I tried to use all the firmware from the FrSky website. The error is repeated. I tried to use the firmware from this topic - https://www.rcgroups.com/forums/showthre...working%21. Without changes. Help me please
Reply
Login to remove this ad | Register Here
#2
http://intofpv.com/t-xsr-wont-bind-to-qx7

It's taking about a different Rx but the process should be the same.
Reply
#3
On the QX7, you can't use the JR connection like the Taranis 9XD. You need to used the port next to the SD card slot. The pin order goes GRN, 5V, SPort. SPort being closest to the SD card slot.
Reply
#4
any fix to this issue?same thing happens to may xm+ only red and green light lit but not solid...
Reply
#5
(26-Nov-2017, 04:03 PM)DeeFPV89 Wrote: any fix to this issue?same thing happens to may xm+ only red and green light lit but not solid...

Is it bind to your TX?

If you are having trouble binding, make sure your RX is in the correct firmware (EU or international firmware).
Don't be a LOS'er, be an FPV'er :)  My Gear - Facebook - Instagram - Twitter
Reply
#6
(26-Nov-2017, 04:03 PM)DeeFPV89 Wrote: any fix to this issue?same thing happens to may xm+ only red and green light lit but not solid...
(26-Nov-2017, 05:26 PM)Oscar Wrote: Is it bind to your TX?

If you are having trouble binding, make sure your RX is in the correct firmware (EU or international firmware).

Same here. After flashing XSR-M with the most recent FW (XSR_LBT_180322.frk) the blue LED (which stands for 'SBUS mode = ON') doesn't light anymore (but the receiver is in SBUS mode and it works) and the green LED doesn't light solid when motors run (more RPM --> faster blinking).

I can change to CPPM mode and back to SBUS (the green LED flashes) but the blue LED is OFF all the time, even when the receiver is in SBUS mode. I tested the blue LED with the multimeter and it works well (it lights when testing it in the continuity mode).

Binding works too but since updating the firmware the blue LED doesn't light anymore and the green LED is blinking as I described.

During flashing the firmware the first two times there was an error (failed) but then the firmware was flashed successfully (verify was OK). The strange thing was - I didn't have to rebind the receiver after flashing (but I still did rebind it a few days later).
chupo_cro
Reply
#7
The blue light should be on regardless of what mode you have in the radio. If you haven't already tried, power up the receiver first, then hold the bind button for 3 sec and that should change CPPM to SBUS on the receiver.

You always want to rebind after flashing. The receiver do keep the pairing, but I realized that not every will always work.
Reply
#8
(17-Oct-2019, 09:55 PM)voodoo614 Wrote: The blue light should be on regardless of what mode you have in the radio.  If you haven't already tried, power up the receiver first, then hold the bind button for 3 sec and that should change CPPM to SBUS on the receiver.

You always want to rebind after flashing.  The receiver do keep the pairing, but I realized that not every will always work.

As I said, I can change from SBUS to CPPM and vice versa and SBUS is working (I can fly the quadcopter) but the blue light went off after I flashed the receiver with the new firmware. Before flashing the receiver with the new firmware the blue light was always on, I didn't try to change to CPPM mode to see if the blue LED will then be off but the manual says:


Quote:S-BUS/CPPM output (BLUE LED stay lit indicates XSR-M in S-BUS mode, otherwise in CPPM mode). How to switch S-BUS and CPPM signal: Long press the F/S button on the receiver for 3 seconds, the GREEN LED will flash thrice, indicating the switch is completed.

And if I remember correctly the green LED was not blinking with the old firmware - now with the new firmware it is blinking. When the throttle is low the green LED blinks slower and when the throttle is higher the green LED blinks faster.

As I said, I did rebind the receiver a few days after flashing the new firmware.
chupo_cro
Reply
#9
I am confuse. After flashing, are you getting stick controls and asking why the LEDs are different? Or after flashing things are not working? If the latter, then my advice is to reflash again.
Reply
#10
(18-Oct-2019, 12:19 AM)voodoo614 Wrote: I am confuse. After flashing, are you getting stick controls and asking why the LEDs are different? Or after flashing things are not working? If the latter, then my advice is to reflash again.

After flashing the stick controls (SBUS) and the telemetry (SmartPort) work well, the only difference is blue LED is now always off despite the receiver is in SBUS mode. And the green LED now works as I described which is not same as it worked before flashing. In other words, if I didn't look at the LEDs I wouldn't notice any difference compared to the old firmware.
chupo_cro
Reply
#11
(18-Oct-2019, 01:24 PM)chupo_cro Wrote: After flashing the stick controls (SBUS) and the telemetry (SmartPort) work well, the only difference is blue LED is now always off despite the receiver is in SBUS mode. And the green LED now works as I described which is not same as it worked before flashing. In other words, if I didn't look at the LEDs I wouldn't notice any difference compared to the old firmware.

Most likely just a bug (or "feature" as developers like to call it) in the newest firmware. If you were to flash back to a previous version of the firmware and it works then you could prove that, but probably not worth the hassle if everything is set up and working as you expect (other than the blue LED obviously). You could report the bug to FrSky but I doubt they will ever fix it. That is probably the last version of firmware you will ever see for the XSR-M now that FrSky have moved away from ACCST and onto their new ACCESS protocol.
Reply
#12
(18-Oct-2019, 01:35 PM)SnowLeopardFPV Wrote: Most likely just a bug (or "feature" as developers like to call it) in the newest firmware. If you were to flash back to a previous version of the firmware and it works then you could prove that, but probably not worth the hassle if everything is set up and working as you expect (other than the blue LED obviously). You could report the bug to FrSky but I doubt they will ever fix it. That is probably the last version of firmware you will ever see for the XSR-M now that FrSky have moved away from ACCST and onto their new ACCESS protocol.

Frsky probably put the bug in on purpose to rub salt in the wound to get people so annoyed and jump to ACCESS. "Here is the last firmware suckers. Enjoy!"
Reply
#13
(18-Oct-2019, 01:35 PM)SnowLeopardFPV Wrote: Most likely just a bug (or "feature" as developers like to call it) in the newest firmware. If you were to flash back to a previous version of the firmware and it works then you could prove that, but probably not worth the hassle if everything is set up and working as you expect (other than the blue LED obviously). You could report the bug to FrSky but I doubt they will ever fix it. That is probably the last version of firmware you will ever see for the XSR-M now that FrSky have moved away from ACCST and onto their new ACCESS protocol.

Yes, they probably won't update ACCST firmwares anymore Undecided

I'll try to flash some older firmware these days (it is not possible to know which one exactly was in the receiver when it was new) to see if the blue LED will then work as before. It is in fact just a few minutes of work because I flashed the new firmware without desoldering the receiver from the FC by using serialpassthrough + FrSky Update Sport. I was already thinking about testing the F.Port firmware anyways so before that I could test some older firmwares too.
chupo_cro
Reply
#14
(18-Oct-2019, 01:35 PM)SnowLeopardFPV Wrote: Most likely just a bug (or "feature" as developers like to call it) in the newest firmware. If you were to flash back to a previous version of the firmware and it works then you could prove that, but probably not worth the hassle if everything is set up and working as you expect (other than the blue LED obviously). You could report the bug to FrSky but I doubt they will ever fix it. That is probably the last version of firmware you will ever see for the XSR-M now that FrSky have moved away from ACCST and onto their new ACCESS protocol.

It really was because of the firmware. I've bought another XSR-M which arrived with international firmware and working blue LED and after flashing it with XSR_LBT_180322.frk the blue LED didn't work anymore and holding the button for 3 seconds (toggle between SBUS and CPPM mode) did nothing.

Then I tried to flash the receiver with XSR-MLBT170619.frk which is older and then the blue LED and holding the button for 3 seconds were working again. After holding the button for more than 3 seconds the receiver indicates SBUS --> CPPM mode change (or vice versa) by three short flashes of the green LED and by toggling the blue LED which indicates the mode that is currently active.

In other words, with the most recent firmware the receiver can work in SBUS mode only and the blue LED is then always off, while with the older firmwares the receiver works according to user manual.
chupo_cro
Reply
#15
Thanks for reporting back and letting us know Thumbs Up
[-] The following 1 user Likes SnowLeopardFPV's post:
  • chupo_cro
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Announcement TBS Crossfire / Tracer 6.33 Firmware Released SnowLeopardFPV 84 41,199 15-Apr-2024, 11:27 AM
Last Post: SnowLeopardFPV
  Help Frsky XM+ Firmware versions Steak-9 3 131 26-Mar-2024, 01:28 PM
Last Post: Steak-9
  Help FrSky r xsr receiver not entering bind mode August 1 99 05-Mar-2024, 08:49 PM
Last Post: August
  BetaFPV Elrs module not loading in a taranis X7 Stumpy 2 202 31-Jan-2024, 12:19 PM
Last Post: Stumpy
  Help FrSky Archer RS to Speedybee F405V4 through F.Port trecords 0 124 28-Jan-2024, 09:10 PM
Last Post: trecords


Login to remove this ad | Register Here