Almost made the Jump to Jeti !!! ( ACCST v2.1.0 Frustration)

[Konrad]

I'm at the family estate and decided to update all my FrSky equipment I have at my Denver family home. This consists of about 2 dozen receivers, two X9D+ and XJT RF modules.

This was again a very frustrating FrSky firmware experience! So much so that I was seriously thinking of dumping FrSky and making the move to Jeti.

Now I know about the RF and OS separation. I know to keep ACCST and ACCeSS separate. I know of the S-Bus and S-Port trap. I know about the cross over cable between the TX and RX. What I'm getting at is I know how to maintain my FrSky RF equipment, or so I thought.

The key problem I had is that the firmware/equipment doesn't report load failures.

With my luck the first X9D+ did not work while it appeared to have taken the ACCST v2.1.0 update. The receiver also didn't appear to work when updated to ACCST v2.1.x.
The trap I found myself in was seeing that the internal RF appeared to have been updated to V.2.1.0. But I could not get any bind with any RX combination running any v2.1.x.
I could go back to ACCST v1.17. and get a bind. But the TX "bitching betty" didn't appear to respond the same between TX start ups. Also the SD card version error would appear intermittently, (This was a clue!)

After spending a whole day chasing what should have been a straight forward firmware upgrade. I gave up and went to bed. In the morning I recall that in the past when I've had software problems they have been traced to SD cards or Windblows drivers. As I was on a Mac, I could eliminate the WIndblows issue. I got a new micro SD card and card reader.

I transferred the SD contents from the old card to new card and STILL had issues with OS stability and ACCST v.2.1.0 not binding. Let me tell you I was fit to be tied!!

Then I realized that the contents I just loaded on to the new SD card came off the old SD card. So If I thought that the SD card was corrupted it was only logical that the contents from the SD card would also be corrupted. So I did a clean SD card down load from the FrSky site. After learning a bit about FrSky's file structure. That the drive named Taranis and the drive named NO NAME are not both on the SD card. (It appears that the drive Taranis is the actual memory location of the Taranis microprocessor. (Do not touch these files!). And the NO NAME drive is the whole SD card. Once I realized that I didn't need to partition the SD card the up load of the SD contents went smoothly.

Again I updated ACCST to v2.1.0 with a newly down loaded file. Again the TX showed that the internal RF module was on ACCST 2.1.0. This looked the same as with the corrupted SD card. But now the OS (OpenTX 2.2.4) appeared to be stable as Bitching Betty's start up chime and warnings were consistent with each power up. Great!!!

Now on to updating the RX for ACCST v2.1.x. Now here was a big surprise. When I was trying to flash the RX from the TX with the corrupted SD card the write times where about 15 seconds to "up date" the RX. Now with the new SD card and clean down load files the write times are about 3 minutes. All RX updates to ACCST v2.1.x went smooth other than updating the stabilized RX's to V2.1.1 frsk.

These stabilized receiver files have a file extension "FRSK". All other receiver files I've down loaded for ACCST v2.1 have the file extension "FRK". It appears that my boot-loader (or radio) doesn't know how to handle the FRSK files. I'll need to dig into this a bit. But as I don't fly gyros or I try not to fly gyros this isn't a priority.

If anybody knows how to address this "frsk" file extension problem, I'd appreciate a heads up.


Now the second X9D+ upgraded just as it should. (SD card was NOT corrupted. With SD cards FrSky uses, this was a minor miracle)!

I'm not a software developer but there has to be a way to show if the software has failed to load. Now in the case of an SD card, I assume it is more of a hardware issue. But some kind of handshake or flashing LED code would help.

So the take away for me is, if the firmware update doesn't perform (bind) look for a corrupted SD card early in your troubleshoot efforts!

All the best,

Konrad

Edit: Add SD Card version error

 

[getsuyoubi]

This maybe a stupid suggestion (not a FrSky user (yet)), but can't you just rename those ".frsk" files on your MAC, changing their extension to ".frk"?

 

[MikeB]

No, a .frsk file has a 16 byte header, then the rest of the file is what would be in a .frk file.

Mike

 

[Konrad]

Mike is correct renaming did not work!

So why won't the X9D+ running OpenTX 2.2.4 not read or allow the .frsk extension file to migrate to the RX? Is this a limitation in the hardware (8 bit bite vs a 16 bit bite)?

If it is not a hardware limitation do I need to run a more modern boot loader?

I need to look into this. Why would FrSky have changed this. Is there a work around for why I can't up grade my old S6R and S8R rx with the ,frsk extention using the X9D+. Is this not the correct proceedure. Or do I need some other device(s) (Airlink S) or (STK)? It is not clear in the read me file if one or both are needed.

I have to admit I'm not in the mind frame to deal with FrSky's programing logic and customer interfaces. Love the power of OpenTX. But gawd why can't FrSky put forward some effort with the customer interface!!!

This v2.x.x issue with both ACCST and ACCeSS is why I have recommended to my last two students* to NOT enter the FrSky environment.

* These guys weren't from a computor back ground or tech savy. I still think Spektrum is the best for those types of hobbiest, limitations and all.

 

[HENNY]

Konrad maybe your primary issue is the Mac solution. I have been running all my gear X9D+, Horus X10S and many receivers for many years and have never seen any of the issues you are discussing. Get a windows machine, this will be at much lower cost to a Jeti solution.

 

[Konrad]

LOL ?

@HENNY Now that is a real bad joke. You need to put an emoticon at the end of such a statement so folks that might not know much about programing know you are kidding.

Having written code for on both the Windows platform and Mac and Unix, or more to the point troubleshot code I can tell you NOBODY in their right mind would start out on a Windows machine. Well, maybe for economic/market share reasons. But that's it. The Mac platform is so much more stable and elegant than any Windows OS.

Now I have to ask how would the Windows machine have helped isolate the corrupted SD card? No BS, I've had many problems with FrSky software that did not work or work well on the windows platform but worked just fine as downloaded on a Mac. True, this was more of an input output issue with faulty unstable Windows drivers but it was still a Windows issue that went away when doing the upgrade on a Mac.

Now I will agree that the Windows machines are a cheap, poor value solution to any computer issue. That is why it is so popular with institutional users where price trumps value every time.

I will say that if it wasn't for OpenTX, FrSky wouldn't be my brand of choice if looking for ease of use and mechanical durability (quality). Now Frsky does allow me to repair my own radio as they will sell me parts, as they deteriorate. This is a big plus over the Spektrum Radio!

So warts and all FrSky still is my brand or radio. But at times I want to dump this brand. Like why do they supply us with such low quality SD cards. 4 out of 6 of my FrSky radios have had failed SD cards. One might think it is the way I use the radio, fair enough. But when you see the service center stocking these SD cards by the bag full , with 100 count replacement cards each, this is telling.

*Now I haven't been deep into any code for 10 years, so things might have changed but I highly doubt it has changed significantly.

Konrad

 

[HENNY]

Konrad. You are all negative, negative, negative.

 

[Konrad]

WHAT??

It was you that cast aspersions on the Mac, Apple. I'm pro clean code with adherence to established protocols and standards. Now true I have a dim view of most corporation and institutions when it comes to IT.

To be clear I love OpenTX as opposed to the other OS systems we see on most radios. (I also loved the OS on the Multiplex Profi 4000mc). As the new FrSky Ethos is in the FrSky's customer beta test, I'll reserve comment on that until it is further along in its development.

True I was/am very frustrated with the whole ACCST v2 roll out. This time the root cause was the corrupted SD card, combined with the lack of proper feedback as to upgrade status.

True, I'm no fan boy of substandard products.

All the best,

Konrad

 

[Kilrah]

So why won't the X9D+ running OpenTX 2.2.4 not read or allow the .frsk extension file to migrate to the RX?

Simply because .frsk was created after 2.2.4 was released so it has no idea about what it is. Needs a current OpenTX version.

 

[Konrad]

So the ability to download RX firmware is dependent on the version of the TX OS? I don't recall reading that in the "Read Me" file. I'll have to re-read these. I did read that I'd need the hardware "Airlink S" or "STK"

So it looks like it might be best to down grade to v2.1.0 .frk rather than mess with the core core reason I have the radio, that is controlling my airplanes.
OK, again I'll have to read the revision history to see what I might want and what I'm willing to do without with 2.1.1 .Frsk.

Again I haven't actually seen a need to fly with FrSky's gyro (stabilized) RX.

 

[Wayne]

I don't kn ow what your love affair is with 2.2.4, but give it up and use the current version and your problems will be solved. In other words, you have created your own frustrations in this case.

 

[Konrad]

There was no issue with 2.2.4 It is a VERY stable version of OpenTX.

My issue was with the corrupted SD card (this appears to be my bane with FrSky radios). Once I changed to a new SD card and downloaded a clean copy of the software on to it, the upgrade to ACCST v2.1.0 went smooth, as it should have.

On my second X9D+ the upgrade to ACCST v2.1.0 went smooth as silk.

Is there a later version of OpenTX that reports RX failed down loads or detects corrupted files? With my X9D+ I got confirmation of a good load (update) of ACCST V2.1.0 of my TX & RX when in fact it was corrupted by the faulty SD card.

I fail to see how any of my issue with the update of the RF module to ACCST v2.1.0 would have gone any easier with a bloated version of OpenTX. I'm a strong believer in the concept of tight simple elegant code. I see no need* for many (any) of the added OpenTX features with a dated X9D+ transmitter.

Wayne I'm staying with the stable OpenTX 2.2.4 because you told me that often models built with older versions of OpenTX might not play nice with newer versions of OpenTX. Is this no longer true? That is that the model programs I wrote on OpenTX 2.2.4 will run on 2.3.11 with no need for detailed follow up to make sure the mixers are working as they did in the lower OpenTX version. ( My hobby is flying toy airplanes, not keeping up with software that offers me no added flexibility or useful features). Why would I want to add this level of frustration just to see a version number on my TX that says OpenTX 2.3.11.

Wayne, can you give some details as to how OpenTX 2.2.4 contributed to my issues loading ACCST v.2.1.0? I just don't see it in practical terms, or in any of the read me files for the later OpenTX versions. OpenTX 2.2.4 and ACCST v2.1.0 work great together. I now have 65 hour (across 2 pilots) of flight time on these upgraded radios and no RF issue using ACCST v2.1.0. (I can't say that with ACCST v1,17)

*I don't fly gyros, rather my thumbs and eyes are my primary interface with the flight controls. I have no need for the stabilized FrSky rx's. So the .frsk and .frk never was a concern to me it was just something I noticed as I was trying to bring my total fleet of FrSky RX's up to the much safer modern standard that is ACCST v2.1.0. While I own 1/2 a dozen stabilized FrSky RX's I don't think I could ever justify using them, with the frustration of getting them to work properly. You all might notice that the stabilized thread is the longest here on ALoft's Forum' and for good reason!

All the best,

Konrad

P.S.

I'm still flying FrSky even though the attempt to upgrade from ACCST v1.17 to ACCST v2.1.0 cost me a day of flying and some restless nights. This is a cost we as FrSky customer shouldn't have to deal** with.

**I know it is a bit unfair to blame FrSky for corrupted SD cards. But I attribute this to FrSky purchasing the lowest grade SD card possible. If this isn't the case, can anyone explain why all the SD cards I've purchased have worked straight out of the package and 3/4 of all the SD Cards I've purchased with FrSky products have failed?

Like I said. Look to the SD early on as a possible source of one's issues when trouble shooting any software issue with FRSky products.

 

[Flying Dutchman]

While I own 1/2 a dozen stabilized FrSky RX's I don't think I could ever justify using them, with the frustration of getting them to work properly.

You bought a stack of these stabilized Rx's but decided not to use them, and now they're laying around collecting dust? Really?
Next time you're doing a major cleanup, feel free to send them my way!

 

[Konrad]

I only have about 6.

Way back when, I was planning to use them in the replacement of Spektrum AS3X RX (DX7 and DX9 TX). After flying many of the AS3X planes I decided that Gyro's were not appropriate for me and my style of flying. I still use gyros in my helicopters. But again I haven't seen the need to bother with all the horrors of getting the FrSky gyro RX to work. I'm sure that being a FrSky product they offer a lot of promised features. But reading the sticky thread on this forum they aren't for me.

You haven't pissed me off enough to send you my units. I'm sorry I don't sell what I think are flawed products. Mine are very early units. If you want stabilized RXs I think what Wayne is selling today are probably much more stable products than what I have. Just reading the sticky I wouldn't wish a stabilized RX on my enemies.

I was just updating these stabilized RXs to keep commonality across my ACCST 2.1.0 fleet.

 

[HENNY]

Konrad the problem is when something doesn't work to your satisfaction its always someone else's fault. Id say purchase the Jeti, it looks like a nice radio.

 

[Flying Dutchman]

You haven't pissed me off enough to send you my units. I'm sorry I don't sell what I think are flawed products.

Wait a minute, give me a chance - I'd be happy to piss you off! And I wasn't suggesting you sell them to me. I wanted you to give them to me. OK, I'll pay for shipping, but that's it. Am I getting warm yet?

 

[Konrad]

Konrad the problem is when something doesn't work to your satisfaction its always someone else's fault. Id say purchase the Jeti, it looks like a nice radio.

You haven't been reading many of my build threads. I post the issues "I" have and try to offer work arounds so that others can avoid the issue "I" have had.

Now I'm annoyed at fan boys. Like how does a corrupted SD card point back to me. In this case (FrSky) uses low quality cards. True in the last 6 years or so "I" have learned that the SD cards should always be suspect. So much of this thread's issue (long time troubleshooting) is my fault in that I expected the product I purchased for FrSky to actually work. (I knew better when it came the the SD cards as supplied by FrSky).

Now I have an issue with the software reporting that it had a successful upload when it didn't. I don't have an answer to that. It is just an observation.

To show that the above statement makes you look like an ASS. I'll go back through this forum and list many of the Issue I've had with product where I've published that the error was mine.

It is late, but let me start off where I admitted that the initial lack of directional control with my Samsara was traced to ME not setting the flap to aileron mix to allow proper differential. This was totally my fault and a programing error to boot.

But yes I want folks, be them the OEM or hapless customer, to learn from my mistakes with substandard products!

Chrome porcupines or gaudy TX faces are not going to pull me away from OpenTX. Now if Jeti would allow the use of OpenTX, I in all likelihood would have jumped! But as it is now I'm not about to throw out the baby with the bath water. OpenTX is that GOOD of an OS as to keep me working through the many short comings that have been FrSky's quality issues. (To be clear Wayne at Aloft Hobbies has supported the FrSky product line with phenomenal technical and customer support. Wether the issue is with the OEM's build quality, premature release, or customer induce failures).

 

[Konrad]

Wait a minute, give me a chance - I'd be happy to piss you off! And I wasn't suggesting you sell them to me. I wanted you to give them to me. OK, I'll pay for shipping, but that's it. Am I getting warm yet?

Dutch you have a long way to go before you piss me off enough to give you these poorly thought out stabilized RX (dated).

Now Henny is getting close. I try to bring to the forefront issues I see with products. And I offer work arounds as I find them. In this case (ACCST v2) I've been reading of a lot of folks having problems with their attempts at upgrading to ACCST v.2.1.0. The high rate of failure with the customer not being able to upgrade their radios is a clear indication that there is something fundamentally wrong with the way FrSky has presented the information. I tried to show that I covered the classic issue early on. Such as the ACCST vs ACCeSS firmware (the names are far too close). Then the S-Bus vs S-Port (Again the nomenclature is too close to even be cute). The cross over leads (again a fundamental trap that a dedicated port would have addressed). FRSKY SUCKS WHEN IT COMES TO THE CUSTOMER INTERFACE! I avoided all of the short comings, or so I thought.

Yet I got trapped by a faulty SD card. I tried to show the thought process in arriving at the conclusion that the SD card was corrupted. I also called out what I saw was an indication that one might have a set of corrupted files. (The 15 second vs 3 minute upload times with the RX). I admit that I should have seen this SD card corruption issue a lot sooner in my trouble shooting efforts (My bad).

Now I will admit that at first I thought that this ACCST v2.x.x issue was an attempt by FrSky to break the clone hold on the bottom end of the market. As this ACCST issue unfortunately was identified by the amateur german team at about the same time as FrSKy's genuine attempt to lock out the clones with the encrypted ACCeSS protocol. I've said it before and I'll say it again. ACCST v2.1.0 is addressing real safety concerns with faulty data packet pass through. ACCST v2.1 HAS NOTHING TO DO WITH LOCKING OUT CLONES. IT IS A CRITICAL SAFETY UPDATE.

Dutch, If you really want the head aches associated with the stabilized RX please give Wayne your business. These really are very inexpensive RXs. I just saw the price tag on the last Futaba RX I purchased (R148DP PCM) for $149 and that was in 1992 dollars! FrSky today is a great value if it works!

 

[Kilrah]

Is there a later version of OpenTX that reports RX failed down loads or detects corrupted files?

OpenTX can't do anything about it since FrSky devices don't report failure.

 

[Konrad]

Thanks, that's what I thought. I suspect the issue is in the hardware as I doubt there is enough memory to perform functional tests on the down loaded software.

I'm at a bit of a loss as to why Wayne is pushing the later OpenTX versions. OpenTX 2.2.4 is a very stable OS and works great with these old monochromic radios. It has proven to work well with ACCST v2.1.0 when the SD card isn't corrupted.

Why would one want to introduce more variables by changing the OS to an already weak customer experience? I'm really loath to have to rewrite my model programs just so I can see OpenTX version 2.3.11 on my radio set up page.

Reading OpenTX revision log and the "Read me " files I see no reason for somebody running a classic X9D+ moving up to the latest and greatest OpenTX. What am I missing?

I had a seamless upgrade to ACCST/ACCeSS 2.1.1 with OpenTX 2.3.10 but this was with a modern X Lite-S. Well, seamless after I learned that the NIB purchase of the RX ant TX had different ACCST/ACCeSS version from production runs that had close to the same date. Gawd, configuration control is nonexistent with FrSky. (Love the detailed log with OpenTX).

Again my issue was with a corrupted low quality SD card supplied by FrSky. Combined with the "upgraded" TX claiming to have been updated to ACCST 2.1.0 when it hadn't.

The take away is that the update works and works well. As long as the many gotchas (see first post) and a corrupted SD card are not involved. See that the second X9D+ upgraded as smooth as silk.

If anybody is following along, please look for a faulty SD card early on in one's trouble shooting, if you can't get the RX & TX to bind after your attempt to upgrade to ACCST v2.1.0.
This is NOT an OpenTX issue but rather a hardware issue with the SD card.