FrSky's ACCST Update - should you? 

Too many times I've been stung by updating software to the 'latest and greatest' version, so I've taken the stance of only updating when it's necessary..

I just updated an R-XSR with fport firmware and i grabbed the newest one not thinking about it having completely spaced this, now I have to re-solder the RX to the flash lead...got me again FrSky, with the gift that keeps on giving.

Excellent advice. There has been problems with the updates, including your Taranis not starting up when switched to on, or your Taranis turning on all by itself when no one has turned it on. The company's response is that you need a new main board. But, when the cost of a mainboard is compared to the cost of a Taranis 2019, guess what most people choose?

As stated in the video this flaw is related to ACCST D16 only. Noticeable uncommanded servo movement and / or 0.9sec freeze of all servos affects EU-LBT only. FCC has the same flaw, but no noticeable effects occurs. Here are more details - 77hobby.pl/important-firmware-update-frsky-accst-d16-v2-n-51.html (switch to EN at the top of the page) - including a link to orginal report from German / Swiss / Austrian test team who identified and isolated the problem allowing FrSky to work on a fix. Re new FrSky protocol - ACCESS - I like it for many reasons: wireless firmware upgrades, receiver registration and thus easy model sharing (I fly with my son, so we use this one a lot), telemetry from more than one receiver in a model, less latency, much more linear RSSI, etc. So ACCESS upgrade was not about FrSky blocking dumb clones like Jumper. Which they have every right to do anyways, but ACCESS is simply awesome.

Time to peel off that screen film

Did FrSky ever said they had a failure that needs to be fixed by an upgrade? Is this the update that will roll out encryption? I got a Nano Talon Evo too and plan to use that motive receiver + jumper T 16. FrSky is no longer competitive. I've sold close to all FrSky components except 1 receiver and a sensor, but x-lite + x9d are all sold.

U la la... first AndrewN ewton grants me a Sir title, now Bruce promotes me to a Prince... What next? :)

Hiya Bruce is there a Flysky receiver that I can connect to my pc to use for the simulator for my Flysky i6 transmitter

I'm in EU and stopped flying 2.4ghz a long time ago. Even in the city's outskirts I got interference so bad that it failsafed 30m from me. I often check the bands as an enthusiast ham and beside the broadcast radio, a few railway channels, a drop of 2m and 70cm ham activity (still) some mobile phone channels in the high 800mhz...there is nothing! All the RC bands except 2.4ghz are silent. 27, 35, 40, 70mhz... just static. 2.4 is like a frigging zoo! You can't drop a needle in there without poking someone's eye out.

I’m sticking with what works, it will be years before compatible Rx are fazed out. Some one will break encryption!! If I need a new radio till then I will swap modules into my sweet tasty 9 ch Futaba.

Por desgracia actualicé el QX7, el módulo interno y el R-XSR y nada funciona, ni siquiera puedo bindearlo Unfortunately I updated the QX7, the internal module and the R-XSR and nothing works, I can't even bind it

Hugely bad move for FrSky, many in our club used the 9XD plus, new Access has killed it for most of us, next TX will be Jumper.... bye bye FrSky... a very bad move, guaranteed to lose millions of customers. They could find some resolve to a poor marketing choice, by offering both variants - with or without Access....... I loved FrSky so reliable and so adaptable, why change something that works. A real nail in the coffin.

I'm in UK on EU firmware and I've had no such servo movements and if I'm forced to upgrade I'll buy a crossfire system. And now all the frsky rx are discontinued

Heard it happens with the R9 system

I have never updated anything not my frsky xlite or my Betaflight still on 3,5 - if it’s working don’t fix it

Live in the UK...never used shitty LBT firmware, Cobblers by stuffed shirts in the EU...Also updated my friends gear to FCC for the same reason...We are leaving the EU club anyway, and it's long overdue..🤔

I idiot did update my tx few days ago😭. Did one flight since then and no problems, but I got strange reading of altitute from g-rx8 receiver. I bought 2 x8r receivers some time ago from banggood. I just bind them and no problems. After more than half of year I put them in plane and almost lost my plane. At 50m range I got low and critical rssi. Receivers bought from hobbyking or other just work..

If you buy new receivers are they going to be running the new version and force us to update?

Gid-A all Bruce they saying rip the protective stuff off(bollicks) my Taranis is 5 year old may be more have updated TX to 2.2.4 no worries My RX's never.I have in the last 3 months just removed clear protector off, was grotty. RX's have 4 X8R 2 in packets , 1 X4R in packet. Nothings broke. Cheer's

Yeah.. my one wing kept twitching the right servo.... which i decided to fly anyways and crashed

Fryky introducing PANIK so they can update the owners TX so the software locks in frsky RX. This may increase the sales of Jumpers !.

No way. I tried that and then spent lots of time (painfully) learning how to take it off... mostly because of the internal jxt module. Also had a crash trying it out with my xm+ that, come to find out, really has a poorly planned 2020 release.

Remember the good old days when people used to get a radio and not fart about with it?

When you complain to their reps that the ISRM 2.x update killed your SPI whoop binds, their first reaction is to act surprised, followed by "ACCESS radios can work with SPI receivers if you use a CLI command to bind them", which isn't the conversation being had at all. If you keep at them long enough though, they recover from amnesia and defensively acknowledge that it's not their responsibility to update SPI receivers being made by the likes of what they compare to "software pirates". How many of you held out on buying a Tango 2 and kept your FrSky radio because of integrated whoops? How many of you relish the idea of no longer being able to fly them if you want to try out one of their new Archer receivers? They didn't shoot themselves in the foot, they sawed off the branch they were standing on, and they're telling you that everything is fine and that a small handful of haters does not dictate reality. Let's see where they are a couple years from now.

Not going to fix something that is not broken... frisky skullduggery!

I don’t use internal module anymore only LR external modules so not concerned.

In the first half of the video, he SAID how he would respond to competition. In the second half he proved it, by telling people to subscribe to a "competing" channel.

Thanks I will now not be updating

MAY BE AFAKE SERVO CONPLAIN JUST TO MAKE SOME MONEY

Second! HAHA^^

Ditch freesky campain

This is a second attempt to round up the strays after the failed uptake of ACCESS. All of this shenanigans can probably be put down to the opening up of shares in the company to Investment (B)wankers.

Frsky just cutting there own throat. Let them. I’m moving on to T-16 and Xfire

No!

...and that's why my receivers are FCC and yes D8 too 😂😂 in the U.K.

I fly my big turbine jets with the X12S and Frsky receivers and have not had any "glitches". I fly in US with the FCC version.

Thanks Bruce, My personal opinion: If the problem was really the BUG, they could have fixed it without adding encryption, don't they?

Totally agree with you. I never care for these updates...because it WORKS !

Drove me nuts about a week ago. Flashed an R-xsr to the V2 firmware and the little sucker would no longer bind.. So much time wasted @#!%$×..😡 Saving up for that RadioMasterT16.. Heck Ya!...👍🏻🍻👊🏻

You’ve got amazing eyesight.... 2.5 km 😬😬

I am in the UK and i run the FCC firmware, have done so for many years without issue, be it D8 or D16. I fear this updated version is simply more shenanigans from Frsky. One thing i would advise all users that are sticking with the old version - go to the frsky website and download the old firmware, just in case you need it in the future, just in case it suddenly disappears from their website.

I loved FrSky at first, then they came out with the horrible S6R/S8R stabilized receivers and the craptacular R9 "long range" 900MHz system with 2.4GHz transmitter antennas and impossible to fit receiver antennas. Both systems were released with tons of bugs, and FrSky relied on the community to fix the issues for them. Firmware release after firmware release that either didn't fix the issue, or fixed one problem while adding others, etc. I learned a very valuable lesson in avoiding FrSky firmware updates whenever possible!

Gone across to Jumper now and wont be purchasing any new FrySky products nor updating anything. Well done FrySky.............mind-blowingly dumb!

FCC firmware is affected by the bug just not as severely. Looking back I can see that I have personally experienced it on FCC firmware. Once with a 700 class helicopter and another time with a 550 size helicopter that both had brief unexplained channel inputs from the receiver in the air (I know because the FBL controller logs the channel inputs). Neither caused a crash but when that happens with a machine which can potentially kill someone it's scary. The encryption in ACCST 2.0 is completely open to being reverse engineered unlike ACCESS because it runs on unsecured hardware. This is why FrSky didn't release ACCESS for older generation receivers. It will protect the signal from hijacking or spying but it won't stop compatible hardware like the multi protocol module from implementing ACCST 2.0.

HELP! I live in holland (unfortunately...) and flashed my Taranis Q X7 in non-eu (D8 mode)... I have the V8FR-II as a receiver (D8 receiver). When I flew the Axon RC Aircraft, the plane had all sorts of glitches. The receiver has CONSTANT brown-outs (temporary loss of control), no response in the ailerons & elevator. The plane suddenly loses control in mid-air and spirals down. A second later, I have control again... Or when I have my flaperons, it glides with flaps but then it rolls to the left or right (one flaperon does have a glitch causing the Axon to roll). It seems like the transmitter (bought from holland for 135,-) has a problem in non-eu OR the receiver is just crap... The V8FR-II is also not far away from the ESC and it doesn't have external BEC power. (after all, I got it down (with a stone hard landing)... minor damage got easily fixed) What do I need to do? Upgrade my Tx? (Because I'm having loads of glitched with my D8 receiver and brown-outs)

Well to be fair, ACCESS adds a few other features. For example, telemetry now has a much higher data rate. And the new glider receivers with integrated air pressure sensor are amazing. But yeah. There's no reason why the X-Lite pro can't support ALL protocols. But no, you have to choose D16+ACCESS, or D8/D16 and the older stuff but no ACCESS.

UK flyer here with a gen 1 Taranis (non-plus), but never went to LBT as wanted to retain D8. Never had an issue, never left the International (FCC compatible) firmware, never will!

From what I understand, both FCC and EU firmware has the bug, but it's more likely to be triggered in EU firmware, because the EU protocol works different, as you mentioned. Btw, even ACCESS apparently has this bug, and needs to be updated, if you want to get this fixed. I'm running an old X9D+, also with fimware it came with, because I'm like you, if it works, don't update. I'm still flying quads with "ancient" BetaFlight 3.1.5 firmware, and these are still great: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-FAi5MwMDhkg.html

6:30 "Arsy" company! ROFL

My gear works great as it is. No updates in my future.

Don't you hate on companies that do not support thier old products.....Microsoft.

Oh bruce please tear the plastic protection of your screen ..

Great video yes I think the same way if is not broken why fix it lol.

The ACCST update needs to happen due to a dangerous bug that came to light (note that it was discovered by german users NOT by FrSky) but the update isn't ready for public release yet and FrSky should not have put it out yet. I had an uncommanded elevator input on a 700 size helicopter about two years ago that I am 100% sure was this bug. It only lasted a split second and didn't cause a crash but it scared the hell out of me. The FBL unit has channel logging and showed an aileron channel input from the receiver so I know it was from the radio system. I'm in the US and running FCC firmware so I personally know as a fact that the bug affects FCC as well as Frsky has said.

I used successfully XSR for 6.8km with 45rssi warning after 6.5km, all works fine, if used properly.

I think, the problem is that FrSky will soon sell all their transmiters with D16 v.2x.

I have been using a spektrum dx7s since 2012. Never done any firmware updates never had a signal loss or any issue at all.

Corona bug?

FrSky is wanting to force users to aftermarket modules and rx!

flying the ACCST LBT version, I had problems and crashed my DLG ... updated everything to V2 ...

1:43... Exactly....

Hello!! I love your videos!!! But now i need your help, pleasee!! Because the antenna from my radio (FrSky Taranis X9D 2019 ACCESS) came from factory too stuck I damaged it twice. The first time, i made a new one from old coaxial cable from old laptops and worked fine! At the second time, while removing the hot glue, without noticing, I removed a very small blue component that is very close to the soldering points of the antenna. I still don't know what component is! The radio still works but, with the Fr-Sky ARCHER R8 PRO after 200 meters i get low signal warnings... :/ Do you think that I can easily fix this or should i buy a new module?! Or, if i buy the external module R9M, should it work fine with the old module? Thanks in advance! cheers

Plus #SayNoToFAADroneProposels #DoNotTreadOnMe #NeverStopTheRC Thanks

The new firmware is pre loaded on new receivers. Which doesn’t let me bind to my qx7 without the upgraded firmware. Now I really don’t want to upgrade to use it because I will have to upgrade all my old receivers firm ware which is a pain when you have 10 quads... guess it’s time to get cross fire. F frsky!

If it works don't update

I just updated most of my receivers and my iXJT in my X10S to 2.0. I've done the X8R, R-XSR, and R-X8R Pro. No issues with telemetry or anything so far, though I did have to rediscover a couple sensors. However, I did NOT update my X4R-SBs because they are running F.Port firmware and currently there is no ACCST V2 firmware with F.Port enabled. Luckily, since I have a iRangeX 4in1 module, I can still fly those receivers. It's updated to the newest MPM firmware (1.3.something) and everything is working great. The reason I updated was because yesterday I had something very peculiar happen. I hadn't planned on updating to V2, but yesterday I was flying my GAUI NX4 (500mm size nitro helicopter) and while hovering it suddenly darted straight toward the ground at full negative pitch. Smacked into the ground, but luckily bounced up and I was able to save it, albeit with some broken skid struts. I reviewed all my logs... telemetry logs, and the gyro unit MSH Brain2's several logs. All telemetry logs looked good, no issues there, no low RSSI or signal loss, then I moved onto the Brain2 logs. One of the parameters I have logging is receiver pitch, which is channel 6, and it's logging the signal that it gets from Ch6. For some reason, there was a 0.40s long burst of -117 on Ch6 right when it started to plunge. Obviously I know for a fact that I didn't go from a hover to giving full negative pitch for half a second while only about 3m above the ground. I went through all my different flight modes, switch positions, etc and there was no possible way I was able to replicate that -117 signal on Ch6. So I was like "wtf? what are the chances this happened for the first time today". I'm not entirely sure that bug is what happened, but I can't afford to risk it, I have 5 helicopters, ranging from 380mm to 700mm nitro, and I don't want to put myself or others at risk. Even if it's a once every thousand flights kind of deal, it's not worth it to me. I'm not keen on FrSky's attitude and anti-consumerism as of late, but I can't afford nor do I want to switch to a whole new radio system... I really like the radio, both the OS (OTX) and the feel of the radio in the hands and its hardware. So I'm just going with it for now. I've considered switching to Jeti, but that's not gonna happen anytime soon. I love OpenTX and I don't want to get rid of it. I'm just not entirely sure I trust the $150 JumperTX and the MPM to $3000 worth of flying nitro powered chainsaws in the air.

FrSky was solid with the D8 when they moved up to the D16 that's when their issues started. The one problem I saw was receiver lockout after interference from gas engine ignitions. All radios can have a problem with noisy ignitions, but the X series receiver would lockout and even if the RSSI got better it would not recover cause a crash. Testing on the ground many videos on that shows the receiver has to be power cycled before it will work again even if you shut off the ignition.

The only thang about it is if you buy a new receiver you have to flash it to the old version I just got a new xm plus from racedayquads and it would not bind to my jumper radio until I flashed it with older firmware thanks for the headache frsky

What made FrSky so popular was exactly the use of OPEN software and now they are trying to close it when they are successful?! Time to move away from them.

Hello, congratulations for your videos. I need help if you can explain me, can i use FrSky G-RX6 ACCESS 6, oon the Taranis Plus X9D. Thanks

You have line of sight out to 2.5km - do you have bionic eyes?

First! Hello Bruce 🖐🖐🤩

Err . I've got my Jumper T16 Pro working with 'EU LBT' on an FrSky X8R with Telem so what's the prob?

I finally found a difference between the v1.* and the v2.* firmware, and it only applies to the XM receiver, not the XM+: Normally I configure the transmitter to send only 8 channels in D16 mode for a faster (9ms) frame rate. Using v1.*.* firmware (transmitter and receiver), this works fine with the XM+, but with the XM it binds but won't output a valid SBUS signal (it does output something on my oscilloscope, but no flight controller accepts it). However, when sending all 16 channels, then it starts to output valid SBUS data again. When I flash v2.*.* firmware to transmitter and receiver, then the XM does work again in D16 mode with only 8 channels.

The information is wrong. Both LBT (EU) and FCC versions have the bug but in the FCC version the probability of the bug occurring is much lower since the transmitter doesn't listen (wait) before talking, it just sends data, regularly, which helps the receiver detecting/decrypting valid frames. Depending on how much noise the receiver picks up combined with the poor "encryption" that FrSky implemented in ACCST, the receiver can interpret one or multiple frames as valid data even though it's noise or interference. In the best case this garbled data is just moving servos randomly for a very short time (for a few milliseconds). In the worst case the FrSky receivers will interpret the data in multiple consecutive frames as control bits leading to a desync. This persists up to about 1 second. During that time the data again causes random servo movement which over a second can cause full deflection of a control surface. Even worse you have no control over your craft for up to 1 second. After that, the receiver should automatically synchronize to the sender and you should have back control.

Is there a way to downgrade back to v1.1.3 if its already been updated?

I have had uncommanded servo movement two or three times last year, each lasted only one second until control came back. For example suddenly it gave 100% throttle and 50% roll right while I (FPV) was only 10m above the ground and only 30m away from me, it lasted for exactly one second during which I had no control, I almost got a heart attack but still managed to not crash. This was not a failsafe, I have had normal failsafes (and quite a few more stage 1) before and this was entirely different, it threw the sticks to a random position and held them for one second until I got back control! The other two times were similar and I crashed. I have had the EU-LBT version of D16, all modules had been updated to the (then) latest version of 2018 or 2019 (can't remember exactly anymore but it was the latest I could find at that time).

I had problems about servo movement without being commanded to move, but only with the FrSky stabilizing receivers S6R and S8R( the problem happened multiple times but just using flaperons. One of the ailerons moved and stayed at full deflection. The other channels were working fine. With the receiver programmed to disable the stabilization , to work as a normal rx, the problem did not happen even using flaperons. Using the stabilization but without using flaperons, the problem also did not happen as well.

Bruce , you recommended FrSKY when it came on the market many yrs back and I bought a TX module for my MX22 TX which worked perfectly. I bought an X9D when they were available--all perfect ! Now I am using an x10s on 2.2.2 with G-RX6 and G-RX8 RXs everything is perfect and I have no intention of changing OpenTX non EU to newer versions --- Thanks soo much for great advice, Ali SUTHERLAND, UK.

Hmmm. I had a 700 size heli crash itself straight into the ground back in 2015, straight from a hover about 20ft up. I had the flight controller checked over by the manufacturer and it was fine. The cause was always a mystery. An unwanted servo command would certainly have accounted for that. It just went full negative pitch into the ground, as if I'd chopped the stick. Maybe it was this bug? If so, FrSky owe me a few hundred quid! However, I use (and always did use) the worldwide firmware on my Taranis. Mine is a 2014 model, so grandfathered into the 2015 LBT rules, so it's legal for me to use. I won't be upgrading. I only fly fixed wing and quads on FrSky now. My helicopters are on Vbar control since 2016 as it's more convenient.

Bit of a dilemma here. I have been learning to fly using an X9D+ and X9E with a buddy lead. Plane is a Tundra. My instructor used the "D". I found the "E" to be a bit uncomfortable so invested in another D, an SE this time. All was going reasonably well during 2 or 3 flights but, at one point, the plane suddenly rolled onto its back. The instructor corrected it at berated me for "going inverted". I was sure I hadn't initiated the roll but accepted it. Then, in a later flight, it did it again and crashed before the instructor could save it as the plane was too low. He knew I hadn't initiated the roll as he was watching my hands. So, is this the kind of thing the update is aimed at? I haven't flown since but having the, repaired, plane and Tx switched on have shown no problems. I am in the UK so using the EU version. Should I update?

Dont, dont , dont since I changed my firmware to eu, I have all kind of problems. Now I have a bunch of recievers which will not Bind to my radio, I had a Beautiful radio with all my models working perfectly now I have all kind of bugs.....and I am angry and very sad....:(

My taranis is fine, I run all D16, XM mini RX's EU firmware, not noticed any erratic or uncommanded servo movement, not going to update anytime soon, also don't want to screw up my Lua scripts

Listen before talk is the contention algorithm used by WiFi IEEE 802.11. This device operates - unless I am mistaken - on WiFi frequencies 2.4GHz and 5GHz, so it is not strange that the EU require radio transmission devices that use these frequencies, to adhere to the friggin standard. en.wikipedia.org/wiki/Contention-based_protocol

Anyone has 35 mhz channel 76 crystals left? especially multiplex (they are off frequency) and futaba ds; that way i can keep expanding my WORKING 35mhz fleet.

Hello, i don’t understand this, i have a DIY Frsky module installed in my futaba FM radio, i have had problems with range and lost of signal lately. Is it the firmware??

So glad the motive rc receiver is really good, just bought 2 of them. Trying to get away from the orange rx telemetry one which is shit. Had to set the rssi to the lowest point or the t16 wont shut up saying telemetry lost or low rssi. But no brown outs or loss of control. Figured the orange rx uses TSSR values which dont match rssi values. Over orange rx so motive rc is the new go to

I Bought the new Taranis x9d se plus 2019 and R9m new 2019 receiver and module for a glider, one month ago. AlI have is telemetry lost every second flight, I have to land and switch all off and then on again to get telemetry back. One would expect both to be problem free as they are the 2019 edition and top of the range...

A 'problem' which is so bad it's taken nearly *8 years* to be fixed? Then either FrSky stuff is crap or...

I just bought an x lite and a tinyhawk. Will it come with 2.0 on it? I dont want to open it of I cant use it.

Bet you still fly bf3.5 :) Edit: just realised you fly cleanflight😂

I turn my taranis on and it takes 5 seconds for the little man inside to turn the screen on, should I sack him?

I was thinking the same thing... No way I'm updating

Engineers holy words......If it works ...

I upgraded my FrSky to the first version of the EU software, I did a test flight with my three week old V-Tail and after about 3 minutes flying the machine climbed, the telemetry said the v-tails 3 cell battery was at 6V and the damn thing flew away. Turning off the transmitter (last resort) didn't kick in the failsafe (which had been bench tested after updating the TX & RX) I never got the V-Tail back and TBH I have clocked up less than an hours flying since (about last three and a half years)

Is this an OPENTX problem or a FrSky problem ?

Rant rant rant

Don't do it......

Easy answer is no

This could also be a trick to push a new version with bugs, in order to force the upgrade to the new system. Unlikely, but I've seen stranger.