Universal ACCST Firmware (UNI)

[alm_nl]

Are their any options to making this work with my X10S/FROS?

Upgrade to OpenTX or EdgeTX not an option?

 

[MikeB]

You just need to update the Rx to V83 (or V84). Before V83 the servo pulse rates were specific to the Tx, so binding a Tx used the settings for that Tx. From V83 on, the servo rates are specific to the Rx.
1. Update to V83/V84.
2. Bind to QX7 and set servo rates.
3. Bind to X10.

Mike

 

[TerryH]

Mike,
Many thanks! this is simple.
The firmware version I have been using is V80. Which I have in about 15 receivers, do you recommend updating them all to V84, this is all for fixed wing aircraft.

I greatly appreciate all the effort of firmware development, testing, scripts, documentation you have created and support, as I know this is a huge job, with I am sure has been close to a full time job!

Terry

 

[MikeB]

Changes since V80:
Add stabilised receivers, fix a bug when using SBUS in, make servo rate settings common to both bindable transmitters, allow binding to a XJT Lite, allow inversion of CH7 (internal pad) on S6R, Re-initialise RF chip if 30 consecutive packets are missed (could help with interference when using spark ignition engines).

If you are not using the dual bind feature, SBUS in, a XJT Lite or a stabilised Rx then no update is needed.

Mike

 

[TerryH]

Mike,
I have tried both V83 and V84 RX8R-PRO firmware updates from V80. The setting for the PWM to 9ms (111Hz) rate works fine with using the Q7, however, on my X10S, it reverts back to the 18 ms (55 Hz). It is radio dependent. This for a RX8R Pro receiver.

I am using the script UNI-Statistics.lua on the Q7 for setting the servo rates, and not setting anything else.

Thanks for any suggestions.

Terry

 

[MikeB]

OK, I have a small bug! The master enable for 9mS rates is not quite handled correctly.
BInd one Tx, then enable 9mS rates and set each channel to the required rate.
If you then just bind another Tx, then the enable for 9mS rates will be off but the channel settings are as previously set, so you need to enable the 9mS rates.

If you now bind the original Tx by using the dual bind procedure (Tx in bind mode then just power the Rx on without pressing the bind button) all works correctly.

The 9mS rates master enable setting is only lost if you bind using the bind button.

I'll fix this in the next version!

Mike

 

[TerryH]

Mike,
I am not sure if I completely follow your steps.
I am doing the firmware updates with my X10S (FROS), and using the Q7 to enter the codes to activate the firmware and to run the script to configure the PWM rate to 9 ms. After this process, then I bind the receiver to the X10S.
In following your latest steps, I then put the X10S in bind mode, then turn on the receiver, but I do not press the bind button at power up on the receiver. I also binded the receiver to the X10S, which worked, then binded the receiver to the Q7 and set the PWM rates to 9 ms, then went back to the X10S with the X10s in bind mode, but not with the button pressed . Sadly, none of this worked

Any other suggestions with the current firmware.

Thanks,
Terry

 

[MikeB]

No, you do need to be able, with the current firmware, to run the setup script to enable the servo rates.
I'll try to get the fix released.

Mike

 

[MikeB]

I've put V85 on the release files thread. This should fix the problem.
I've still to update the text in the post describing the reason for the release.

Mike

 

[TerryH]

Mike,

Thanks for providing the V85 firmware update. After completing the upgrade and configuration process, everything works as expected—the PWM pulse is correctly set to 9ms and remains stable regardless of which radio it's bound to.
Beyond the standard range check and basic channel functionality, are there any additional tests you'd recommend to further validate performance/operations.

Appreciate the continued support!
Terry

 

[MikeB]

I recommend logging both RSSI and VFR when doing a range check (if VFR is not displayed while range checking), then inspecting the VFR value. VFR usually stays above 80 even when RSSI goes critical.

Mike

 

[mapes12]

Newbie here. I think I've figured out how to get the V85 FW onto my X8R using a male to male servo cable from my X18 smart port socket on the Tx (located on the top of the Tx?.) But the next bit about installing activation scripts and the like is a mystery to me. I've found this page: https://github.com/strgaltdel/Ethos-Uni-Receiver but it gives no idiot proof instructions about what to do to get the scripts onto my Tx.

My understanding is that once I've got the script working I can then contact a vendor (T9Hobbysport here in the UK) to buy an activation code. BUT how do I get these scripts onto my X18 and working??

 

[MikeB]

On the link you mention, in the src directory, is a directory "uniActi". Copy this directory onto the SD card in your Tx as a sub-directory of the "scripts" directory. So you should end with the scripts directory containing "uniActi", that itself contains the files.
Then in the Settings menu you should find an icon for uni-activate. Touch this and it will run.
Have a look at the second post in https://forum.alofthobbies.com/inde...mware-release-files-universal-accst-d16.3270/
There you will find some information in the "Universal ACCST guide.pdf" file.

Mike

 

[jmorrow]

I'm currently trying to flash my Frsky receivers with the universal firmware and I'm having a problem. I've tried both an X8R and a G-RX6 receiver with the same results and I'm hoping someone here can help.

I've flashed the version 85 firmware and I've bound the receivers successfully, but when I run the RX Activation lua script v5 it does not provide a Rx Code.

The radio is a Taranis X9D Plus running EdgeTX 2.11.3 and the internal RF module firmware is XJT_ACCST_2.1.0_FCC.frk.

 

[davemcddd]

Did you bind the receivers with telemetry turned on? Are you receiving telemetry from the locked receivers?

 

[MikeB]

Have you tried the script from here: https://github.com/offer-shmuely/frsky-accst-uni-rx-scripts/tree/main/edgeTx/SCRIPTS/TOOLS ?

Mike

 

[jmorrow]

Did you bind the receivers with telemetry turned on? Are you receiving telemetry from the locked receivers?

Yes and I'm receiving information after discovering sensors.

 

[jmorrow]

Have you tried the script from here: https://github.com/offer-shmuely/frsky-accst-uni-rx-scripts/tree/main/edgeTx/SCRIPTS/TOOLS ?

Mike

Yes, I've tried both the version in the zip archive from the forum and GitHub.

 

[MikeB]

What does display when you run the script?
Could you backup your Tx settings and firmware then try either erskyTx or openTx to see if the script operates correctly with them.

Mike

 

[jmorrow]

What does display when you run the script?
Could you backup your Tx settings and firmware then try either erskyTx or openTx to see if the script operates correctly with them.

Mike

I took a look at EdgeTX release notes and it appears that they updated to Lua 5.3 in 2.11.x. There are incompatibilities with Lua 5.2 used in earlier versions of EdgeTX. I suspect that since the bit32 library has been deprecated, the UNI RX scripts will need to be updated to use the bitwise operators in Lua 5.3.

Here is the list of Lua 5.2 to 5.3 incompatibilities: https://www.lua.org/manual/5.3/manual.html#8

Lua supports the following bitwise operators:

• &: bitwise AND
• |: bitwise OR
• ~: bitwise exclusive OR
• >>: right shift
• <<: left shift
• ~: unary bitwise NOT

All bitwise operations convert its operands to integers (see §3.4.3), operate on all bits of those integers, and result in an integer.

Both right and left shifts fill the vacant bits with zeros. Negative displacements shift to the other direction; displacements with absolute values equal to or higher than the number of bits in an integer result in zero (as all bits are shifted out).

When I get some time this weekend I'll try reverting to EdgeTX 2.8 and see if it works.