Horus X12S out of date?

[mdbuilder]

I need some help here.

I have had a hours x12 for years, have not updated the software. I am on open TX 2.2. Recently I went to buy some new rx's and see the note about a new firmware version needing to be installed or choose the old version. I have not hooked the TX to the computer in a few years and have since changed computers a couple times. Also upgraded to windows 11!

So, for my X12, how critical is this firmware upgrade?

Considering getting a new TX and am confused about the whole X10 express / X20 / access / ethos / open TX issue? I like open TX.

Is zadig compatible with windows 11? Right now I can't get my TX to talk to the computer....

Thanks!

 

[Wayne]

You don't need Zadig unless you have major issues.

Yes, you can update the RF firmware, and it would also be a good idea to update the OpenTX version to the current release.

To summarize the issue with ACCST (the RF firmware) you have V1, and it was found to have a rather rare bug where the servos could randomly move for a second or two. This is not good. FrSky released ACCST V2 to fix this bug, but you need to update the radio and all receivers as V2 and V1 can't bind with one another.

Aloft Hobbies and others have built a new ACCST firmware called Universal ACCST and it fixes the V1 bug and the other issues we knew of in ACCST. This firmware is currently in beta testing and hope to release it for some of the ACCST receivers soon. This is really nice as a receiver with this firmware can talk with a V1 or V2 transmitter, it does not care. That is why we call it Universal.

Some other terms you asked about:
ACCESS is a replacement for ACCST. ACCESS requires a newer transmitter, and some older receivers can be updated to ACCESS. The Archer series of receivers are all use the ACCESS RF protocol.

Ethos is a brand new programming environment. Think of it as a modern version of OpenTX, but more friendly to use. FrSky hired the head programmer from the OpenTX team, so it has a lot of OpenTX functionality and a primary goal was to make the radio much easier to use. Development continues as they are constantly adding more power to the system. It has been very well received.

While we are on it, the new X20 that runs Ethos is also the first TANDEM transmitter from FrSky. This offers both 2.4 ACCST and ACCESS as well as 900mhz for very long range and getting around trees, etc. We will soon see the new Tandem receivers that talk both 2.4 and 900 at the sametime for a VERY reliable connection.

 

[mdbuilder]

So, if I want to preserve the ability to run open TX the choice would be the X10s rather than the X20...

Are these x10s's stable these days? Delivered with firmware that is current, no bugs, won't need to be reflashed next month in other words?

I am filling my cart -LOL.

Then we can talk about my current radio, I have installed companion 2.2,on my current pc tablet and when I plug the TX in no power I can not read the radio. If I pop out the card it reads through a USB hub/card reader.

Thanks, hope to hit buy today

Oh yes, I ordered about 275 worth of servo last night, if it hasn't shipped yet you could hold that

 

[gnichola]

@mdbuilder I had a buddy with an X10 and I suggested he install Ethos on it just to try it out as you can always just backup the device and restore it if you don't like it. He never went back, and in fact, about a month later he bought an X20S...which is an awesome radio

 

[mdbuilder]

Thanks, I've ordered. At least I can get a couple models up and running while I futz with the upgrade and an installed base of 25 + rx's. What a disaster.

 

[Wayne]

You might want to email the team at contact@alofthobbies.com and give them your order number and ask them to update the transmitter to all current levels. Typically we only do this if asked on the X10 radios. That and I think we are shipping the X10 with Ethos now.. We can do the OpenTX install for you if you like, but we do charge a couple of bucks for that one.

 

[mdbuilder]

Thanks, email sent. I'll try the Ethos version for a while and see how it goes.

 

[mdbuilder]

Ok, after much futzing about, you tube video watching etc. I have updated my x12s to open TX 2.3.14. The new power button behavior was the cause of some momentary 'did i brick it?' Panic but it works and my models are still there.

I have gone to the frysky website and grabbed the new firmware, I think what I need to do is put this file on the SD card in the TX in the firmware folder, then run it once choosing to update the internal module and run it again to flash the rx with the special cable connecting the sport on the X8R receiver to the lower three pins in the module bay? Order being signal, negative, positive for the TX side?

Thanks!

 

[mdbuilder]

Also, BTW - the fedex box with my Horus 10S in it has been parked / stuck in Willow Springs Illinois since Wed. I called fedex who took my phone # and was supposed to call me back but no call so far. Maybe you can put a race on it or something as the shipper.

 

[mdbuilder]

Well, I flashed the TX which went to completion, flashed the rx with the modified cable which also took a bit and went to completion. I can not get the rx to bind, any suggestions?

found a similar complaint in GitHub:

I tried, with my X12S with the newest Open TX 2.3.5, also with IXJT internal module with firmware v2.01 (FCC) to update all my X8R receivers (total of 21 receivers) also to the newest firmware v2.01. Of course with the cable and the correct procedure I have been always using to do so (from the lower connectors in the external module bay, as the X12S doesn't have an auxiliary connector as the X10S).
Two different problems:

If you try updating the firmware on the receiver directly in your airplane without disconnecting the servos, the process starts correctly but after a third of the way, the servos make a little jitter and the Horus tells you that is unable to reconnect with the receiver. The receiver does not block at all, as you can try it again and again with same results.
If you don't have anything connected to the receiver, the process starts and run smoothly all the way to the end, but you are unable to bind it.
I ended up updating without problems all the receivers to v2.01 (FCC) with my reliable X9D+, also updated with Open TX 2.3.5 and the internal XJT module with firmware v2.01. Of course, I used the same cable and the same method. This time, I was perfectly able to update and bind with everything connected (servos, battery and sensors) to the receiver.

General information

OpenTX and Companion version 2.3.5
Hardware Frsky X12S and X9D+ (both with Open TX 2.3.5, and IXJT/XJT v2.01 firmware)
OpenTX Companion (2.3.5 on Windows 10 64bits)

 

[mdbuilder]

Never mind, when the ijt file is flashed on the TX rather than theX8R file, it now binds...

 

[mdbuilder]

Also, FedEx found the box. Delivery will be tomorrow...

 

[mdbuilder]

I spent at least a couple of hours if not more yesterday playing around with Ethos setting up a new big EDF I an working on. Pretty impressed, I had a few times when it took me a while to figure out how to do something but not too bad. I need to hookup a test fan that will burn a few milliamps tonight and see if I have my telemetry and consumption call outs setup right.

 

[Wayne]

Good deal. Sounds like you are on the right path.

Sorry I didn't see the thread when you had the questions..

 

[mdbuilder]

No problem.

I got the consumption telemetry and call outs every 500 mah working tonight

 

[mdbuilder]

Posting this for others future use more than anything.

So, I have have been my way through 8 or so receivers by now. 4 or 5 X8R's all worked great. After grabbing the file off the frsky download page for the S8R however that came to a screaming halt. First, the latest file had an extension of '.frsk' which meant it doesn't show up on the TX, renamed to .frk and was able to flash.

However, no bind!

Looked at the file name more closely and it is dated 7-8-2021 and version 2.1.2, older and larger file dated 6-24 is version 2.1.0

Downloaded the older file and flashed that which now worked Grrrrrr!

 

[mdbuilder]

Continuing to work my way through re-flashing my fleet of receivers. Last night I decided to do an S8R in an e-flight Havoc without disconnecting all the servos, despite the grave warnings I have seen against such a practice . It worked fine, in fact the Rx is still bound to the Tx and the stabilization setup seems fine as well. What is the deal here? Is it OK to leave the servo's and what about stabilization setup as the firmware readme says you will need to redo it?

I also setup the same model with a new Archer SR8 Pro which went well with one little twist that took a you tube video to figure out. The channel setups for quick mode are easy, the calibration and getting the stabilization directions correct OK. The problem was that second step in the self test. I wound up with no servo movements until I re-ran the self test twice. I am finding ETHOS pretty nice, so far I am doing models all from scratch to develop the right 'muscle memories', later I will copy already setup models then modify.

 

[Wayne]

Powering the receiver and all of the servos via the smartport is a recipe for a damage. The circuit is not designed to carry an amp load. And if you are doing this with the smart port on the transmitter, same thing.

 

[mdbuilder]

I see, makes this whole process most painful.

Thanks

 

[Wayne]

Yeah, sorry about that. I use a little tape and identify each servo plug number before unplugging. It helps speed the process up. But if you have a really tidy install, ughh.