RX6R wont show up while registering

[firozdang]

I have a Taranis 2019 SE working very well with both ACCESS and ACCST protocols with XM+, X8, S6R, X8R, and R6 receivers.

I just soldered the FrSky RX6R but when I try to register the device my TX cant find it, it just waits for 'Waiting'

I even tried to update the firmware on it using the STK as well the sport on my transmitter but it doesn't take any firmware as well, I tried both ACCESS and ACCST. Error is device is not responding while trying to update the firmware.

I have tried both ACCESS and ACCST binding as well, but after setting the FS button and power on, it shows red and green ON that's it.

I think my receiver is bad

 

[HENNY]

What did you solder on the RX6R. What version firmware did you flash to the RX6R. So if you flash the RX6R with ACCESS version V2.1.7 this is for ACCESS only. So select ACCESS on you TX then press and hold the receiver bind button, apply power and you should have solid red and green LED's. Then click register on your TX. Ensure the receiver number is not already used on an other model. This process works perfectly.

 

[Flying Dutchman]

Since you are using both ACCST and ACCESS, you can run into problems with the RX6R when updating the firmware.
Did you load the latest ACCESS or ACCST? If ACCESS, did you use the Archer v2.1.7 or the 2.1.7 specifically for the RX6R? If you tried to load the one for Archer Rx's, it is bricked.

 

[firozdang]

What did you solder on the RX6R. What version firmware did you flash to the RX6R. So if you flash the RX6R with ACCESS version V2.1.7 this is for ACCESS only. So select ACCESS on you TX then press and hold the receiver bind button, apply power and you should have solid red and green LED's. Then click register on your TX. Ensure the receiver number is not already used on an other model. This process works perfectly.

Yes, I just soldered the pins on the RX6R. I do see solid red and green LEDs but I don't see anything on the TX while registering, it just keeps on waiting. I did not program any firmware on it, I TRIED to program but on the STK it was stuck at 'Finding device' while programming from the Taranis SPort it said 'Device not responding'.

I TRIED to program both ACCST and ACCESS FW but it failed. All I maintain an excel sheet with the models and its receiver number so I picked the number which was never used before

 

[firozdang]

Since you are using both ACCST and ACCESS, you can run into problems with the RX6R when updating the firmware.
Did you load the latest ACCESS or ACCST? If ACCESS, did you use the Archer v2.1.7 or the 2.1.7 specifically for the RX6R? If you tried to load the one for Archer Rx's, it is bricked.

I TRIED to load RX6R_ACCESS_2.1.7.frsk it was ACCESS so Archer ..but before that, I also tried to load ACCST and it didn't respond.. this sucks .....I somehow started to again invest in Frsky products but they don't keep any stone unturned to screw things up...soon moving to RadioMaster...

 

[firozdang]

BTW which is the correct ACCST firmware to load just in case you guys can point out?

 

[Wayne]

Silly question, but did you get the polarity right?

 

[firozdang]

Silly question, but did you get the polarity right?

Yes, the signal is the TOP most pin and the VCC and GNC are closer to the bottom edge, I looked at the datasheet as well

 

[Flying Dutchman]

BTW which is the correct ACCST firmware to load just in case you guys can point out?

The correct one for ACCST is "RX6R_ACCST_2.1.1_FCC.frk" (or the older "RX6R_ACCST_2.1.0_FCC.frk")
For ACCESS it is "RX6R_ACCESS_2.1.7.frsk"

Your initial troubles with binding it under ACCST may have been due to a v1 vs v2 mismatch between Tx and Rx.

Good luck with the move to RadioMaster, but I don't think that will solve the problem for you. It would be similar to staying with ACCST (using either FrSky or RM). But I understand that RM had to limit their product offering recently, after being sued by FrSky over IP rights relating to the latest D16 versions.

I have also noticed that there are many knowledgeable people (on this forum and elsewhere) who have decided to stick with ACCST v2 (and FrSky), and not go to ACCESS. As long as FrSky keeps selling ACCST Rx's, you'd be fine.

 

[firozdang]

What us V1 and V2? I have posted screen shots of opentx and ISRM versions, what I need to update?

I dont want to mess with my TX since there are 10 receivers connected to it, but I cant even update this receiver with ACCST, thats the another problem

 

[Konrad]

FrSky site

D16 FW see downlad history.

I STRONGLY recommend updating all your ACCST D16 RX to ACCST v2.1.X. This is a critical (Urgent) safety issue!

It only takes about 3 miniutes per RX.

 

[Flying Dutchman]

What us V1 and V2? I have posted screen shots of opentx and ISRM versions, what I need to update?

I dont want to mess with my TX since there are 10 receivers connected to it, but I cant even update this receiver with ACCST, thats the another problem

V1 and V2 refer to 1.x.x and 2.x.x versions. The 1.x.x version had the safety issue that Konrad refers to, and it was addressed in 2.1.0 and later versions.

Screen shot #3 shows that the internal module (ISRM) of your Tx is at 2.1.0, so no need to mess with it. A newer version (2.1.6) is available, but doesn't appear to be essential for your use.
Perhaps the Rx was at a rev prior to 2.1.0, which would have caused the binding problem. If you tried to upload the Archer firmware, it is bricked (happened to me). Remove and keep the antenna's, and throw it in the trash. A $30 lesson...

 

[firozdang]

Do I have any warranty or something like that? I first did try to load ACCST but it didnt respond, then I tried ACCESS, still it shows both red and green light correctly..... can I contact FrSky? will they help me.... I am not at any fault, they should have cleaned up this mess ....

 

[Flying Dutchman]

You might try the retailer from whom you bought it, but I wouldn't expect much from contacting FrSky directly. If you bought it from Aloft, they may be able to check it out for you.
My personal opinion: while irritating, a $30 loss like this is not worth my time and hassle, so I move on and try be more careful in the future. FrSky stuff simply is not plug & play - you need to learn about RF protocols, updates & upgrades, OpenTX, etc, etc, and every once in a while it blows up in your face. Oh well. You could also buy Spektrum, Futaba, Jeti, etc, and pay 3~5x more - and still have issues.

 

[Konrad]

To be clear ACCST 2.x.xx be it any of the earlier poorly vetted version like 2.0.1 will bind to the TX on 2.1.x. So the bind issue is per ACCST 2.x.x and ACCST 1.xx.x. The read me file and download make it clear that both the TX and RX need to be running The same major revision numbers.

Spectrum never did allow you to upgrade your RX to DSMX from DSM2. They did offer to upgrade your TX from DSM2 to DSMX for about $70 plus shipping both ways. FrSky is a much much better radio, both in what it offers in power features and reliable RF link. But this FrSky power and flexibility comes at a huge price. That is the frustration of trying to follow the configuration control of the fast (way too fast) revision number updates.

So the $30 to $70 cost of a FrSky education really is cheap. The kicker is that if FrSky had a software validation process prior to the public release of the software and clear documentation it need not be near as frustrating as it is.

As I recall the pre ACCST 2.1.x versions of ACCST v2.x.x had a lot of issues with telemetry. I think all the ACCST v2 had a solid data packet fix. It was just that other issues were introduced that took about 6 month to correct. ACCST v2.1.0 is proving to be stable. Please update all your D-16 ACCST RF sections to ACCST v2.1.x . This is a safety issue!

Aloft has this nice graphic trying to show the two basic firmware (RF and OS).

 

[Konrad]

Do I have any warranty or something like that? I first did try to load ACCST but it didnt respond, then I tried ACCESS, still it shows both red and green light correctly..... can I contact FrSky? will they help me.... I am not at any fault, they should have cleaned up this mess ....

Let me play devils advocate. How does you uploading the wrong FW to the RX be a warrantable issue with FrSky. The "Read Me" files clearly states the requirements. One needs to be very careful with any FW update.

What mess is that? They found a data packet pass through problem in D-16 ACCST v1 and offer us an end user fix with a simple FW update with ACCST v2.1.x. On the face of it, it sound like the correct thing for FrSky to have done.

I know, I know the road to hell is paved with good intensions. And the devil is in the details!

 

[HENNY]

I agree Konrad, too often there is a urgency to upgrade firmware without first reading the documentation.

 

[firozdang]

You might try the retailer from whom you bought it, but I wouldn't expect much from contacting FrSky directly. If you bought it from Aloft, they may be able to check it out for you.
My personal opinion: while irritating, a $30 loss like this is not worth my time and hassle, so I move on and try be more careful in the future. FrSky stuff simply is not plug & play - you need to learn about RF protocols, updates & upgrades, OpenTX, etc, etc, and every once in a while it blows up in your face. Oh well. You could also buy Spektrum, Futaba, Jeti, etc, and pay 3~5x more - and still have issues.

I got it from RDQ, I showed them photos and they send me a new one, that's why I really like RDQ their customer service is best and fast. I also order from Aloft as well but feel bad to pay for shipping but the RXs are much cheaper at Aloft.

 

[firozdang]

Let me play devils advocate. How does you uploading the wrong FW to the RX be a warrantable issue with FrSky. The "Read Me" files clearly states the requirements. One needs to be very careful with any FW update.

What mess is that? They found a data packet pass through problem in D-16 ACCST v1 and offer us an end user fix with a simple FW update with ACCST v2.1.x. On the face of it, it sound like the correct thing for FrSky to have done.

I know, I know the road to hell is paved with good intensions. And the devil is in the details!

Well, when I said mess because for a beginner the learning curve for me was not just learning "binding, opentx, rates, mixers and functions" but I was stuck for like 6 months with my TX and RX FM incompatibilities and I didn't get much help...going from V1 and V2 on both sides with faulty RXs it was just too painful to work with.

I have wasted more time in understanding FM compatibility rather than flying.

Not only that in the README and in the website description they clearly mentioned that "It can work with both ACCESS AND ACCST" how will in my dreams I know that the currect LATEST working FM under ACCESS is WRONG... it takes an experienced person to figure things out ....you know the background and history but every dumb user like me want to enjoy lfying rather than waste my time working with incorrect descriptions and uploads

 

[Konrad]

You'd be surprises at how little I know of FrSky. The only leg up I have over you and most beginners to FrSky, is that 20 plus years ago I flew the Multiplex Profi 4000mc. This gave me a leg up on how to properly use mixes (none of this menu driven slave/master stuff). The rest of the FrSky mind set is as incomprehensible to me as it is to you. Now I will say that I read the Read Me files and try to understand what is said in those files and notes.

Even with all that I still get burned. You might want to read some of my trials and tribulation, here.

I agree that the documentation is not very clear as to what is what with FrSky. I use to attribute that to maybe a language barrier and that things are moving far too fast with FW updates. But I now think that FrSky really doesn't understand the market place. Most of us fly models for a hobby. Many are not well versed to file manipulation with our own computers. I think if FrSky would step back and listen to their dealer network as to what issues the customer is having things would be a lot smoother for those of us that are flier rather than software nerds.

Firms like Aloft Hobbies have some real nice graphics and video that make it pretty clear what is what. FrSky needs to learn to bring the lessons learned with their dealer network to their own site. These guys have been dealing first hand with the customer issues for a lot longer than FrSky has. It really isn't fair to have us looking all over the internet for the "fix" to the poor FrSky customer experience.