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!
Universal ACCST Firmware (UNI)
- Thread starter Wayne
- Start date
Nestor Vald
New User
Yes, I mean matched, but channel matched on the radio, not into programmable servos.
Like we do in RB25S or RB35S boxes. Exactly like elevators.
In this case, we do the fine triming in the TX.
We match center, then highest and lowest levels. That's all.
Since 2 or 3 months, we can easily trim with curves on Ethos radio but I'm not sure stab function respect those curves.
Before that, only 3 points were ok so, no complex curves have to be added in RX.
Then, you only have to add 2 more aileron channels controlled by the stab without hard mods. You already did it for elevators.
( For the rudder case, I don't think people fly so big models without box, so a 2nd rudder chan should be useless )
Happy new year and sorry for my bad English language, it's not my native one.
Last edited:
Jeronimo770
New User
Hi Guys, I have not been here for a while as my 15 year old X9'd+ (V1 ACCST) is running my 15 some various receivers on V83 UNI firmware, nicely.
But, Santa brought me a FrSky X18 Tx for Christmas and I want to use this as a second Tx. Could you just confirm that by going through the Dual Bind process all will work swimmingly with my X18, I've no need to do anything else - except set the Tx protocol to ACCST D16.
Thanks muchly.
But, Santa brought me a FrSky X18 Tx for Christmas and I want to use this as a second Tx. Could you just confirm that by going through the Dual Bind process all will work swimmingly with my X18, I've no need to do anything else - except set the Tx protocol to ACCST D16.
Thanks muchly.
Jeronimo770
New User
Thank you Mike. Yes, that worked once I found I had to turn on the 2.4G internal module 
Except that, in order to revert to TxA and then back to TxB, I had to hold in the FS button when powering on the Rx. It did not bind by just having the Tx in bind mode and power on the Rx.
My exact problem was previously queried in post #216 on page 11. I have tried releasing the FS button as soon as the red LED comes on whilst binding, as mentioned in your response - post 218, to no avail. I do not press the FS button again after binding, before power off. I'm using an X9D+ with ACCST V1, and X18 with Ethos 1.6.0 and an X8R with UNI v83 firmware. I do not know if I should have updated any other X18 firmware than the bootloader necessary to install Ethos 1.6.0. Ethos Suite reports averything is up top date.
Except that, in order to revert to TxA and then back to TxB, I had to hold in the FS button when powering on the Rx. It did not bind by just having the Tx in bind mode and power on the Rx.
My exact problem was previously queried in post #216 on page 11. I have tried releasing the FS button as soon as the red LED comes on whilst binding, as mentioned in your response - post 218, to no avail. I do not press the FS button again after binding, before power off. I'm using an X9D+ with ACCST V1, and X18 with Ethos 1.6.0 and an X8R with UNI v83 firmware. I do not know if I should have updated any other X18 firmware than the bootloader necessary to install Ethos 1.6.0. Ethos Suite reports averything is up top date.
Last edited:
Jeronimo770
New User
I'm wondering if my problem is to do with the receiver ID with the 2 transmitters apparently having different ID approaches.
The X9D+ identifies my Rx as 06 whilst the X18 can only show me 6. The X18 also has the Owner registration ID which the Taranis does not.
Maybe again, I need to have the channel ranges the same, that is Ch1- Ch8 or Ch1 - Ch16 in both setups ???
When I try to connect the other Tx (not the already bound one) by setting it into "bind" mode and powering on the Rx, the Rx red LED flashes slowly, every ½ or 1 second, which is indicative of UNI firmware in the Rx I believe.
Any advice appreciated, thanks. Jerry
The X9D+ identifies my Rx as 06 whilst the X18 can only show me 6. The X18 also has the Owner registration ID which the Taranis does not.
Maybe again, I need to have the channel ranges the same, that is Ch1- Ch8 or Ch1 - Ch16 in both setups ???
When I try to connect the other Tx (not the already bound one) by setting it into "bind" mode and powering on the Rx, the Rx red LED flashes slowly, every ½ or 1 second, which is indicative of UNI firmware in the Rx I believe.
Any advice appreciated, thanks. Jerry
Jeronimo770
New User
Ah ha. Thank you again Mike, that has done it. 3 feet actually was not enough. I moved the Tx 8 feet away and BINGO. I thought I had read somewhere someone saying you needed to hold it close. That did not work, but clearly, I was not giving it enough clearance.
That's great. 1 more of my IT(?) problems solved. Next one, how to charge my new electric car
I'm not looking for an answer here
That's great. 1 more of my IT(?) problems solved. Next one, how to charge my new electric car
I'm not looking for an answer here
Quick question in regard to firmware version 80 versus 83. I have about 10 planes with receivers installed all with version 80, how critical is tit to upgrade to version 83.
The receiver are RX6R, RX8R-PRO, and G-RX8. I am not using the SBUS on any of them.
In looking at the UNI receiver Firmware Release Files thread, I do see the updates listed for version 83, however, the version 80 seems to be working good for my needs.
Input welcomed!
The receiver are RX6R, RX8R-PRO, and G-RX8. I am not using the SBUS on any of them.
In looking at the UNI receiver Firmware Release Files thread, I do see the updates listed for version 83, however, the version 80 seems to be working good for my needs.
Input welcomed!
MikeB
Very Strong User
V80 is perfectly OK.
V83 added support for the S6R and S8R receivers. It also fixes a possible problem. With UNI you may configure each servo output to be sent every 18mS or every 9mS. On V80, these settings are specific to each of the two possible transmitters. Should you use the "dual bind" feature to change to the second transmitter, the configured servo rates will change. In V83, these settings are specific to the receiver, so are the same for each transmitter.
If you don't use dual bind then V80 is fine.
Mike
V83 added support for the S6R and S8R receivers. It also fixes a possible problem. With UNI you may configure each servo output to be sent every 18mS or every 9mS. On V80, these settings are specific to each of the two possible transmitters. Should you use the "dual bind" feature to change to the second transmitter, the configured servo rates will change. In V83, these settings are specific to the receiver, so are the same for each transmitter.
If you don't use dual bind then V80 is fine.
Mike
Go to this post in a different thread for what to do to get UNI installed, unlocked, and working.
forum.alofthobbies.com
UNI receiver Firmware Release FIles (Universal ACCST D16)
Please do NOT post questions in this thread, see below. Should you find UNI useful you might consider donating, a donate button may be found here: https://github.com/MikeBland/mbtx LATEST NEWS: V84 now available. The R-XSR is now supported by UNI (V79). A guide document is in the second post...
forum.alofthobbies.com
Need clarification of which direcrtory on the SD card to install the UNI-Activate.lua file.
I think it should be the "Tools" sub directory ??
My SD card does not have a "Tools" entry - so do I just create a new directory (using companion ??) to install the lua script to??
Thanks for your assistance
I think it should be the "Tools" sub directory ??
My SD card does not have a "Tools" entry - so do I just create a new directory (using companion ??) to install the lua script to??
Thanks for your assistance
Teamdavey
New User
I'm not sure what to make of this :
I recently bought an XJT lite module essentially to play with. I updated it to the latest published FRSKY firmware and attempted to bind a receiver that had UNI installed - it would not complete the bind process. After a bunch of experiments I established the following:
UNI receiver (tried both a stabilised and an X4R) will not bind I appears to "see" the transmission but never successfully binds.
Same receivers rolled back to the latest Frsky firmware will bind and operate.
An Archer plus receiver will bind in ACCST mode and operate.
All these receivers bind happily to my TD X20 and X18 running 1.6.2/3.0.2 firmware (the latest) on the internal RF module. Also I am currently flying a number of UNI coded receivers on the X20 internal ACCST capability with no issues.
It appears that there is something about the XJT lite that the UNI does not like.
Update: On a hunch I tried again with the Tx in the next room! It did bind this time so.........You need to be a long way away for the bind to work! At least for the X4R but the two stabilized receivers remain stubborn and will not bind
I recently bought an XJT lite module essentially to play with. I updated it to the latest published FRSKY firmware and attempted to bind a receiver that had UNI installed - it would not complete the bind process. After a bunch of experiments I established the following:
UNI receiver (tried both a stabilised and an X4R) will not bind I appears to "see" the transmission but never successfully binds.
Same receivers rolled back to the latest Frsky firmware will bind and operate.
An Archer plus receiver will bind in ACCST mode and operate.
All these receivers bind happily to my TD X20 and X18 running 1.6.2/3.0.2 firmware (the latest) on the internal RF module. Also I am currently flying a number of UNI coded receivers on the X20 internal ACCST capability with no issues.
It appears that there is something about the XJT lite that the UNI does not like.
Update: On a hunch I tried again with the Tx in the next room! It did bind this time so.........You need to be a long way away for the bind to work! At least for the X4R but the two stabilized receivers remain stubborn and will not bind
Last edited:
Teamdavey
New User
To avoid repeatedly editing my post here is where the binding issue is now.
It appears the X4R bind with the Tx in the next room was a fluke as it cannot get it to bind again. I have also tried rolling the XJT lite back to the older V1 firmware and the three UNI receivers will bind immediately with that.
Mike, I have tried with both X20 and X18 as hosts for the module. Both are on Ethos 1.6.2 and RF firmware 3.0.2. Assuming that in your test you had the Lite module on the 2.0.1 firmware this suggests that the issue is associated with the Ethos firmware.
I am now going to pull myself out of this rabbit hole and get on with masking and painting a model!
It appears the X4R bind with the Tx in the next room was a fluke as it cannot get it to bind again. I have also tried rolling the XJT lite back to the older V1 firmware and the three UNI receivers will bind immediately with that.
Mike, I have tried with both X20 and X18 as hosts for the module. Both are on Ethos 1.6.2 and RF firmware 3.0.2. Assuming that in your test you had the Lite module on the 2.0.1 firmware this suggests that the issue is associated with the Ethos firmware.
I am now going to pull myself out of this rabbit hole and get on with masking and painting a model!
MikeB
Very Strong User
On the FrSky site, the ACCST firmware for the XJT Lite is 2.1.0, there isn't a later version. Has ETHOS updated your XJT Lite?
I just checked both my XJT Lites, they are on 1.1.0. I've never used them for flying, only testing firmware so it appears I've never updated them!
I'll update to 2.1.0 when I get some time.
Mike
I just checked both my XJT Lites, they are on 1.1.0. I've never used them for flying, only testing firmware so it appears I've never updated them!
I'll update to 2.1.0 when I get some time.
Mike
Teamdavey
New User
Mike - this is not a big deal on my end - it is more of an experiment and isn't stopping me flying anything. Bye the way, all my stabilizer UNI models are clocking up airtime - very happy with that firmware.
If your XJT is on 1.1.0 then that mirrors my experience. I downloaded the 2.1.0 from the Frsky site and uploaded it to the module via the Tx. The Ethos suite offer the same module firmware that is on the site.
If your XJT is on 1.1.0 then that mirrors my experience. I downloaded the 2.1.0 from the Frsky site and uploaded it to the module via the Tx. The Ethos suite offer the same module firmware that is on the site.
Similar threads
- richardsearcy
- FrSky
