FRSKY RXs - How the heck do I choose?

[Hank]

Both versions are 2.3.11-otx. I assumed that was the ACCST version 2, but now I'm realizing that is the OpenTX version. I thought I had updated the RF module to version 2, but now I realize I must have not done that.
Looks like I have some homework to do.

I updated/flashed the v2 ACCST firmware on my old QX7 internal RF module and now I can bind it to the Archer Plus R8 receiver.
Apparently I had wrongly assumed that I had updated the TX internal RF module when I did the X9 Lite some time ago. But until now I was only using a HITEC external module and Hitec (and FRSKY MINIMA) receivers on the QX7. So I never had the need to bind D16 receivers.

 

[turfdoggie]

That receiver comparison chart from a couple of years ago is pretty helpful. I have to admit that I'm still puzzled by some of the FrSKY naming conventions. For example, the stabilized 8 channel receiver product names. I think the first version was the S8R, which used the ACCST protocol. Then came the Archer SR8, which used the ACCESS protocol. So far, so good (other than the LUA script complexity).

After that, if I understand correctly, came the Archer SR8 PRO, which added something called configurable telemetry power and some port switching. The Archer SR8 PRO appears to have replaced the Archer SR8. Okay, that makes some sense.

Next up, if I am reading the FrSKY web site correctly, is the Archer Plus SR8, but I'll be darned if I can determine what new features it has (though I see it supports ACCESS and ACCST).

Now I see that some of the SR models have names like Archer Plus SR10+, where the receiver has its own plus sign after the channel number.

Any hints on what features and/or advantages each of these product lines adds to the receivers? If there's a comparison chart, that would be fantastic!

Mitchell

 

[Wayne]

Darn good question.. Sometimes we just want to strangle whoever is responsible for the names at FrSky. Trust me is a battle I have fought in the past and I have simply given up on getting some common sense on the names.

For the most part, FrSky takes the existing and adds refinement. If the physical size did not change, then chances are good it was mostly a firmware change. This might support some added features like the Archer Plus line was basically a firmware update to the older Archer units that added ACCST support for older radios. This is a welcome change. While you might think, OK, this is just a firmware change, no need for new names.. I'm pretty sure this firmware forced FCC recertification and at that point you might as well change the name. It also really helps support staff know what version someone has. I think they also add a few other tid bits.. We sell the stuff and it is hard to store it all in our brains.

For the vast majority of users, the many changes really didn't make much difference. They just buy the current version and enjoy.

Since it sounds like you like stabilized receivers, FrSky makes this pretty easy. Each RF protocol has a series of stabilized receivers. These typically range from 6 upto 18 channels units. They will all start with the letter "S". So you will have the Archer Plus, Tandem and Twin versions of stabilized receivers with a different number of channels and added features.

FrSky does not leave a customer hurting for choices when it comes to receivers!

I tend to fly smaller stuff, so I typically buy the smaller receivers as space is often a concern. FrSky is GREAT about offering a lot of smaller options. When I have a big model, I go for the luxury of a 12 or more channel as I like the power switch options. (NFC or audio jack styles.) Otherwise, I just go for the unit that has the correct number of channels. Occasionally I go after a specific unit as I am looking for stability or a glider vario, etc.

 

[j ferguson]

HI Wayne, flying smaller stuff, I bought an S6R mini. It looks like it's setup to be managed with Ethos which doesn't run on either of my tranceivers. X9D and QX7. It does look like it can be setup using the windows software , and STK and the appropriate cabling.

Is this correct?

john

 

[Wayne]

If you are asking about the stabilization side of things, I'm not sure.. Probably just need current LUA scripts in your transmitters.

 

[j ferguson]

The manual refers to the "special" cable which I assumed was a cable which could work with the STK and the S6R configuration app. But alas, no joy. It could be that it will work with a cable between the X9D and the s6r mini. FWIW, I had no trouble configuring on eof the older S6R's (black case) using the confiuration software, the STK and some cabling.

This isn't a big deal, but eventually I'd like to get this sorted out.

If I asked FRSKY if the s6R mini can be configured in this way, do you thiknk I will get a useful answer?

john

 

[Wayne]

Yeah, probably will.

 

[Alois]

The manual refers to the "special" cable which I assumed was a cable which could work with the STK and the S6R configuration app. But alas, no joy. It could be that it will work with a cable between the X9D and the s6r mini. FWIW, I had no trouble configuring on eof the older S6R's (black case) using the confiuration software, the STK and some cabling.

This isn't a big deal, but eventually I'd like to get this sorted out.

If I asked FRSKY if the s6R mini can be configured in this way, do you thiknk I will get a useful answer?

john

Hello John

I assume that you have one of the normal OTX versions on your radios (2.3.15 or older).
This versions do bind and work with newer receivers like Archer plus or SR6 mini but there is a"sanity check" in the software so newer receivers are not fully supported.
This means you can not address the receiver in the option menu and the existing LUA script for stabilisation does not work. ( issue #9015)
This is already solved in the OTx 2.3.16 but there is no due date for 2.3.16.

At the moment there are 3 options to get the stabilization working.
1. do the setup with an ethos radio and bind to an OpenTx Radio afterwards.
2. switch to EdgeTX (this receivers are already fully supported in the newer versions)
3. use a special OTX version compiled by MikeB
https://openrcforums.com/forum/viewtopic.php?t=14126&sid=ae9d841e333aea50a781b5b10ca46a24

I use the third option and it works great for me.
There is only one restriction: the compilation is done without the option for "Lua mixer scripts" but there is hardly anyone who uses these type of scripts.
Another restriction is that in EdgeTx and OpenTx you can not use the "second page" in the Lua script.
But the important first page is sufficient for normal stabilization function.

Alois

 

[j ferguson]

Thank you so much Alois. I never would have found this without your note. I understand the problem of the wonderful people who make the devices we use and that they cannot conitnue to support all of the legacy hardware. Gosh, these wheels don't fit my 1941 Terraplane.