What's new
By:
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Urgent firmware update to all X receivers and RF modules (ACCST D16) just released

ODD, I've been flying and programing My X9D+ for 4 years and don't recall any issues. I wonder what are the conditions that allow these issue to come to the surface. I haven't seen it. I'm not sure I want to spend a weekend of my time bringing all my FrSky RF stuff current. FrSky what are the conditions that cause these problems?
 
ululi1970 said:
It looks like FrSky is pushing an urgent update that applies both to internal modules as well as most X receivers
https://www.frsky-rc.com/important-firmware-update-accst-d16/

Over the last 12 months, I lost two airframes to what looked like servos suddenly moving to extreme positions. I chalked that to CDI interference and/or other hardware problems, but I wonder if in reality this was the cause.
Click to expand...
"Servos suddenly moving to extreme positions".....I wonder if this 'glitch' had anything to do with one of my quads doing a "moonshot" last month.....Hmmm.
 
This is concerning -- It encompasses almost their entire lineup of transmitters from the first Taranis X9D -- however some are curiously not included in the list.
Including X7 / X7S / X9D / X9DP / X9DP SE / X9E / X-Lite / X10 / X10S / X12S / XJT --- but missing include: X9DP 2019, X9 lite, QX7 ACCESS, X-Lite Pro, X-Lite S, Horus X10 Express

It's notable that those not included are primarily those currently for sale. Is this because they don't have the same problem or perhaps they don't want to cut into sales with this announcement.

What I REALLY want to know is if my new(ish) X9DP SE 2019 need the upgrade. Ya... not listed... but I'm nervous about this.
 
If you check on the Opentx site they also have and emergency upgrade for the Horus family of radios to 2.3.5. This issue was related to using 2.4g and 900meg as a redundant receiver system. I have upgraded my X10s and X9D+ from files available on the FRsky web site to D16 V2.0.1. All upgrades work fine, upgrade the TX XJT module and receivers at the same time, the receivers required re-binding. I am now also on Opentx 2.3.5. It's becoming very messy I hope it will stabilize soon. There appears no upgrades yet for the newer Express radios.
 
Yikes, follow the money!

So is the practice of dual banding the issue? I'd like to learn what are the conditions that result in the channel change and un-commanded servo movement.
 
Hi Konrad, I guess the issue is that some flyers having increasingly complex radio systems on board their models. So this was an extremely rare case when having 2.4g and 900MHz on board where the fail safe did not operate as expected. For 99.9% of flyers this situation would never arise.
 
The OpenTx 2.3.5 upgrade has nothing to do with the subject of this thread. Head over to RCGROUPS and check the Horus X10/X10S thread for more info. Several people are coming out
with similar stories (aileron servo jamming to full deflected).
 
Understood OpenTX has nothing to do with the RF protocols.

In what configuration does the radio exhibit un-commanded servo movement (aileron?)? I've been fly for years without any said issue. So something new has happened. I suspect like Henny said it is the unusual condition of using the dual band option that is causing the problem. (I don't do dual band as I don't see the benefit. It isn't really a redundant system. To my way of thinking it just runs down the TX battery twice as fast (two transmitting RF decks).

Please if sending someone (me) to RCGoofs please provide a link. I hate spending time there flailing like a fish out of water. Besides there is no point in adding to RCG's google hits just trying to find some obscure thread.
 
Hi Konrad. I believe it was an Opentx version 2.3.3 to 2.3.4 issue only with the Horus radios. X9D+ and other models not effected.
 
Now I’m confused. Why do all the legacy TX have the new firmware in their folders if the issue is with the Horus branded TX? If the issue is with OpenTX then the proper fix is to fix OpenTX not the XJT module (internal and external).
Something isn’t adding up.

While I like much of FrSky’s products, as a corporation I’m a bit leery. They often dump products on the market that is not ready for the market. (We in effect often pay to be beta testers, This is wrong!) They came out with the Horus brand to try to get around their distribution contract with the then current FrSky importers. They have implemented ACCESS mainly to hamper the clones (I get from a post by Scott Page). And now this emergency update to the legacy TX and RX products without a clear explanation as to why. I again think Scott Page is on to something. I think it is a sales thing and may be rooted in FrSky’s desire to squelch their clones.

If I’m going to be spending hours and hours of my precious hobby time digging out my RF sections* and updating them I want to know why!

*Some of this hardware will need some hardware work installing the update ports.

From my perspective this all seems like much to do about nothing. Please FrSky show us why. Most of us haven’t had an issue. So what is the combination that causes said issues?
 
Last edited:
Konrad, I think you are ready more into the upgrades then is necessary. If you have no problems don't upgrade. I have not had any issues with ACCST either. However one non critical issue did annoy me, this was when the transmitter was close to the receiver you would experience Telemetry lost, telemetry recovered warnings. There were several others issues as well. So the version 2.0.1 for XJT and connected receivers fixes this and several other issues. Yes its a pain but the old saying no pain gain. ????
 
Dennis said:
Just received my RX6R receiver would anyone know what firmware it comes with ACCST or ACCESS ?

Dennis
Click to expand...
I believe the only receivers shipping with Access loaded is the Archer. If you are not sure just reflash the new RX6R it only takes a minute and you can do it with a servo lead using your Horus.
 
Dennis,

I don’t believe there is a production version of ACCESS for the X series of RX. Production RX’s that are ACCESS are called Archer.
Most “modern” RX can be user upgraded to Access. (See FrSky web site for the latest on this).

Henny,
That's the issue I don't know what the real issues the firmware really addresses. Upgrading stuff when one doesn't understand the basic issue causes all sorts of other unintended consequences. (FrSky is natorious for not fully vetting their products before release. I assume there is a real issue, I'd like to know what it is and them determine if it is applicable to my situation. History is indicating that I don't have any real issue. The swamping the TX with the RX telemetry is a none event for me.
 
Henny
My Horus X10 Did this from day one.

However one non critical issue did annoy me, this was when the transmitter was close to the receiver you would experience Telemetry lost, telemetry recovered warnings.
[/QUOTE]
 
Konrad
FRsky have detailed the reasons on the download section for the reason for the upgrades. You can find them on the FRsky download page.
Here is the reason for X9D+ upgrade. This is for the X9D+ XJT module upgrade.
2020-01-16ACCST

D16 v2.0.1		1.Fixed the channel output error (uncontrolled servo movements) under certain conditions.
2.Strengthened correction and verification capability.
Note: Please update the firmware of all your radios, RF modules and receivers accordingly.
The previous upgrade was back in 2017. In the end any upgrades are up to the user.



Maybe Aloft could host a upgrade day for their client?
 
Dennis said:
Henny
My Horus X10 Did this from day one.

However one non critical issue did annoy me, this was when the transmitter was close to the receiver you would experience Telemetry lost, telemetry recovered warnings.
Click to expand...
[/QUOTE]
Yes all FRsky radios had this issue. (Not serious) but you can now fix it with version D16 v2.0.1 if you feel so inclined.
 
Yep. classic double talk. What are the condition that the current firmware fails. I as a customer want to know the failure mode. Can I repeat the problem (this is the foundation to science and engineering)? Like the old saying goes, trust but verify. OK I'll trust FrSky, but need to verify the problem.

This is the classic part; "2.Strengthened correction and verification capability." What does this mean? Sounds like a lock out for Jumper!

Again I've been using Frsky for 5 or more years with three X9D+ one X9E and 1/2 a dozen XJT conversions of Jr bay radios (and one Futaba Super Seven) Never an issue!

I've never thought the swamping of the TX was an issue. To me it indicated that the sensitivity of the telemetry was very high, something I like to see in my RF links even for telemetry. I hope the "FIX" hasn't detuned the sensitivity of the front end of the telemetry receiving RF board.

This is a technical hobby please give us the technical data to make informed decisions.

Really FrSky what is going on!
 
Last edited:
Konrad said:
Yep. classic double talk. What are the condition that the current firmware fails. I as a customer want to know the failure mode. Can I repeat the problem (this is the foundation to science and engineering)? Like the old saying goes, trust but verify. OK I'll trust FrSky, but need to verify the problem.

This is the classic part; "2.Strengthened correction and verification capability." What does this mean? Sounds like a lock out for Jumper!

Again I've been using Frsky for 5 or more years with three X9D+ one X9E and 1/2 a dozen XJT conversions of Jr bay radios (and one Futaba Super Seven) Never an issue!

I've never thought the swamping of the TX was an issue. To me it indicated that the sensitivity of the telemetry was very high, something I like to see in my RF links even for telemetry. I hope the "FIX" hasn't detuned the sensitivity of the front end of the telemetry receiving RF board.

This is a technical hobby please give us the technical data to make informed decisions.

Really FrSky what is going on!
Click to expand...
This maybe a topic for Wayne to follow up? I have tried contacting FRsky service but almost never receive a reply.
 

Similar threads

B
Need Internal RF module firmware file for X12S
Replies
3
Views
2K
Bill Sanford
B
MikeB
  • Sticky
UNI receiver Firmware Release FIles (Universal ACCST D16)
2
Replies
23
Views
21K
Amarok
A
Back
Top