FrSky won't bind! ACCST 2.0 is to blame. 

i once badgered a ferret with corned beef relish

Hi Bruce , I am an original Frsky customer from Australia , I have never had a single issue . After watching Joshua's Video I will never buy another genuine Frsky receiver . As far as im concerned they have lost me as a customer , Jumper and other 3rd party companies who produce excellent quality frsky compatible gear will get my cash .

Live by the sword, die by the sword. Cloning was always Chinese business method. So it’s even funny to see how they deal with a problem that western world has for many years. I think in few years China will introduce kind of IP law. If economy would be a reason one would buy multi-module for 30 bucks and preserves investment. But hobby is always about emotions so now people will switch to another cloned radio with multi-module inside for at least 150 bucks. :)

On the nail Bruce, I'm pretty well completely transitioned to crossfire now. Best radio decision I've made.

Sorry frsky no more products from u ever again .haha lol your company is very stupid customers are not dumb.

How to kill a successful business

i literally got 1 for my first build here and cant do anything cause i cant change the firmware without the cables i dont have...

LOL

dude I am so fucking infuriated

Still?

If Jumper can keep making decent ACCST RXs that keeps my QX7 working with them, I'm solid. Why does anyone ever need to upgrade the transmitter module firmware? No me!

I own a jumper T8SG v2+ now. It's a fine radio. but I'm pretty excited about the radiomaster TX16s due to be released this year. It appears to be a feature rich Jumper T16.

Ever since frsky is doing this scummy shit, I stopped buying their receiver. All I need is Jumper R1 which does exactly what R-XSR does, only to be a little bigger + it's half the price of R-XSR. Thanks frsky, never ever again will I buy 2.4 ghz receiver from them.

@@fen1x591 last couple of builds I have looked at that one, but it's been sold out every time I am ready to build.

@@FPVKermyt I've bought 3 at 11 euros, steal at that price when I compare it to R-XSR, it even has better antenna connetions.

djfurione lol but neither one can use whoops

@@aldenhauser9555 Yeah, that's sad. I'm going to keep my ACCST X9D, but every bigger quad will be crossfired, especially since I had nothing but problems with Frsky links in the past.

TBS is worse. It only supports the 900MHz spectrum. They hate everything else, not just whoops.

they pretty much nuked it from my perspective. i have a devention devo6e and spektrum dx6e and love em both to pieces haven't had any problems with them losing signal. i think i'll stay with what i have and what works

Maybe if jumper didn't make rx an undercut frsky an use frsky firmware on a jumper receive r frsky wouldn't have done this.

@@SuperJohnedge irony is frsky stole from futaba

@@SuperJohnedge it's a business of copycats, everyone does it

Frysky didn't send you to futaba for firmware updates.all I'm saying is gonna sale it support it.jumper sends you to frsky for support.

Just like this ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-pXhahv5gsr4.html

KenjiFPV by any chance a NBD BeeBrain BL? And if so, did you manage to get it to work?

Polywolf I did not understand your question.

Sorry, I was wondering which tiny whoop you were trying to get to bind :-) I’m having trouble with mine aswell

Polywolf oh...mine was a beta fpv 85x pro

which firmware do you have on your X9 Lite? Since 1 week im trying to bind my mobula 6 with the x9 lite but it wont work

Your supposed to update them ?

i would never mess with my computers cmos firmware. screw that up and you pretty much brick the entire machine.

pieter pretorius lol dude, just look up an overclocking guide. You’re software is gonna crash before you damage any hardware (unless you’re doing world record overclocking with LN2 or something). If you don’t know what you’re doing and just start changing stuff, sure, you’ll have a bad time, but setting a boost clock and a locked voltage is pretty safe and easy to do

If I just got a Taranis qx7 and a meteor 65, am I sorta screwed if I want to toss an sd card in my transmitter?

Same here. i blew up my taranis today while flashing my new receiver. Nothing works anymore. The old receiver worked fine and bought the same one. The new refused to bind. That was reason for flashing the software. Followed their manual but ended with broken shit worth over 300 euro. I go for an other brand. Have had it with Frsky.

Yeah R9 access is garbage

I did this from the DX9 to the then new QX7. Then Spektrum released the iX12. Now this FrSky forced obsolescence move has happened. So I remain happy with Spektrum

After holding out for a long time I finally broke down and bought a FrSky, coming from JR- great radios forever, absolutely no complaints, but it is far easier to find whoops with FrSky receivers. Now pissed that this game is going on with customers. Guess with quads it’s changing everything every two months, and then the FAA jumps in. WTF?

i went from flysky to spektrum but will not go the frsky route. spektrum works and that all that matters

I started with a Spektrum that was a gift but it's only 6 channels which served me for a while but I later needed at least 8 channels for turtle mode and RSSI. At the time I made the switch, I found a new 16 channel X9D SE that was cheaper than the Spektrum 8 channel radio. So the choice was simple. Who knew this mess would bubble up.

I’m going to Radiomaster’s new TX16S which cost 1/4-1/3 of a Frsky Horus, but have same ability AND a touchscreen!

If frsky chose to ship xm+ and rxsr with accst 2.0 or with the access firmware then yes you can flash it to the older version to get the compatibility back.

CHRISSO FPV because ACCST D16 V1 IS BROKEN. It has random servo movements and lockouts it shouldn’t have because Frsky wrote the error correction code wrong. translate.googleusercontent.com/translate_c?depth=1&hl=en&nv=1&rurl=translate.google.ca&sl=de&sp=nmt4&tl=en&u=frsky-forum.de/thread/3404-historie-und-zusammenfassung-der-wichtigsten-informationen-zum-thema-pl%25C3%25B6tzliche/&xid=17259,15700022,15700186,15700191,15700259,15700271&usg=ALkJrhhb8juhrPxCmsM1IBGDhLm6svXGKg

@@Euryheli ...ok..gotcha!FrSky are idiots then. I must admit I mainly use my X9Dse with Crossfire.Bought it in 2018,..(haven't noticed any glitches though,..when I fly my 3" non Crossfire🤔)

Been looking into this after getting bit by this type of nonsense on their R9 system where they obsoleted ACCST on newer hardware. This looks like a great starting point atleast for LoRa based transcievers: github.com/RavenLRS/raven . You could potentially communicate between R9, Crossfire, and custom hardware.

I'm crossing my fingers and toes it would be amazing.

Yeah, I found the other flysky dude, high five! This is exactly why I went with fs-i6 (forward and backward compatible with AFHDS 2A and non-2A protocols so I have a big selection of receivers to suit my needs), since my Turnigy 9x was showing it’s age since most micros use the newer one. Not sure I’d really need anything different any time soon, it just works and does it well especially after minor modifications. It used to use anything from an old cell phone battery to a 6s pack for powering the transmitter but now I’m just using old 3s packs since I have a 2w booster on the back (FCC technician license KG5YRN), so I was going to go for crossfire or R9 but really there’s no need now and no firmware or setting changes at all for any of my models like my tiny whoops to my planes, everything just works every time, it’s nice!

@@jakegarrett8109 FlySky did the exact same move as frsky last year. They released the AFHDS3 protocol together with all new radios which are no longer backwards compatible. Just to get control back over the protocol that they put all their work and R&D money in. Which is totally fine and well within their right.. just like most of what frsky tries to do is well within their right and justified. This entire drama around frsky is pretty dumb. Sometimes, the people in this community feel so entitled. Why do they think that frsky should continue to support bootleg unlicensed receivers.. Or that they should be okay with multi-protocol modules being able to run their intellectual property? Imagine the tantrum that TBS would throw if they were in this situation..

@@yekt3805 The bad thing is its turning your stuff into bricks. Its like if Windows stopped supporting 32 bit applications**. Also, controllers from FlySky have been that way, I don't know if you knew, but AFHDS2A is not backwards compatible with AFHDS, however some/most controllers could run both protocols: which is why I bought the older Flysky i6 and not the newer i6s, because the i6 out of the box you can switch between the two and it saves that with your model, so no changing my receivers out of my old planes or quads because it can run the new protocol like my Whoop runs 2A (with voltage telemetry) while my old stuff mostly has AFHDS non-2a receivers. So the protocol has never been backwards compatible to my knowledge, but that didn't mean the controller couldn't just natively run it (which I would think is ideal). So that's not really news worthy that 3A wouldn't back support it. **which has been debated in Linux and Mac ecosystems, but of course with Linux you simply install the small package back in and youre fine, not a huge deal, but if Mac does it, then its forced fed down the throats of all Mac users much the same way WIndows force updates and removes useful features or ads stupid ones like Grove music/3D Viewer/Maps/Weather/Candy Crush/Xbox app and how they took away the most useful thing ever "sticky notes", and hey, just checked today and that's back even though they removed that a long time ago maybe in windows 8...

@@jakegarrett8109 Sry for the confusion but I said that the new *radios* are not backwards compatible and won't support the 2 older protocols. I never said that any protocol itself is backwards compatible with an older protocol.. And windows might not be the best example since there are so many companies that are (or were) stuck on older OS versions like XP because their in-house programs and workflows would no longer work in Win7/8/10. Ofc it's bad for the customer, but in my eyes it's kinda what you get if you buy a product that runs non-legitimate hard/software..

I'm seriously rethinking going back to DSMX on most of my setups now

Dsmx is the Apple of transmitters. They charge you by the channel.

Opentx for life!!

at least spektrum is finally starting to give better telemetry but still not worth it..

Yes indeed...

No customers. :-O They had better hope that they get LOTS of new customers to replace their many years established customer base that they are driving off. I am NOT buying a FrSky transmitter that will not bind to my many D8 receivers and I am NOT plugging a module into my transmitter to do so. If I am plugging a module into my transmitter it is a Crossfire module. With their greed FrSky is screwing their customers over and screwing themselves over.

I'm annoyed with FrSky not just for this one thing, but for a series of anti-competitive decisions they have made. The first one was changing a component on the QX7 (inverter) so that Crossfire stopped working. I don't remember any announcement that this had been done. Just.... on the first shipment of QX7, Crossfire worked, then suddenly it didn't, and TBS had to dig through the PCB to find out why. After that, they left D16 mode out of ACCESS radios, which I believe was an attempt to create this exact same kind of schism, where users of 3rd party receivers would be forced to upgrade away from them. There was no technical reason to do this, and the proof is that, after a huge uproar from users, they added D16 in via firmware update. So now you argue this compatibility break might have been necessary, but FrSky hasn't earned any benefit-of-the-doubt here. They have demonstrated that they will break compatibility in order to force their customers away from 3rd party hardware, sometimes without ever announcing that they have done it (inverter). P.S. let's also not forget that some vendors claimed FrSky had threatened to cut them off if they sold the Jumper T16, and most vendors don't carry the Jumper as a result. This is despite the fact that the Jumper infringes on no intellectual property of Frsky. In fact, it is based on the same open-source software as FrSky's radios, and has equal right to use it.

@@JoshuaBardwell You raise some fair points about them having lost the benefit of the doubt. At the same time, I can only put myself in the shoes of their engineers. You're expecting them to support 3rd party products they have no control over, the module bay thing with the QX7 is kind of the same issue. Do they advertise that this module bay is for using with a standard, or with their own modules? As for the lack of D16 in new radios, why would they put in the effort to support an old protocol when every receiver they've sold in the last 5 years will get an access upgrade? Again, the only reason is to support non-official hardware. I think the issue is pretty clear, they don't advertise support for 3rd party receivers and they won't make any effort to take them into account when releasing upgrades, new products and so on. And why should they? Are these 3rd parties paying any licensing fees to them? Ultimately what they're doing is no different than what most technology vendors do without us questioning it, but we had all collectively fooled ourselves into thinking Frsky was akin to the Apache Foundation when they're actually Oracle. Us as consumers are free to buy from a company like Jumper, but then you might as well buy Frsky and just not upgrade if you want equivalent functionality? PD: I do agree the move to intimidate sellers was shitty. That's a different matter though. And thanks for putting in the time to make this videos and reply to random people in the Internet like me with well thought out responses. I just don't agree with your take on this particular issue :)

i bought original Frsky receivers only then they kicked my back multiple times with incompatibilities. Soldering out all rx to get into their dependency-trap is far beyond welcome. Such policies will go down. Amen

You will get into it. Just like with all hobby, hard to start-

Whoah -- can you link source please? Or better yet email me so I am sure to see it.

There is nothing wrong with FrSky protecting their IP. But they are doing wrong by their customers by breaking backwards-compatibility in order to get the bug fix.

@Mark Evans Yes true. But am I still able to Bind to my Tinyhawk for example?

Wow that's a tough one. The funny thing is they both make and sell a whoop of their own: www.team-blacksheep.com/products/prod:tinywhoop_nano_bnf / www.frsky-rc.com/product/frsky-apus-mq60/