Universal ACCST Firmware (UNI)

[MikeB]

I reproduced the problem with V2.1.0 firmware on a XJT-Lite. It seems the XJT-Lite only sends one type of packet when binding while everything else is sending two types.
I have a fix that seems to be working, I can now bind the updated XJT-Lite to a X8R. I now need to build and release firmware for all receivers!

Mike

 

[Teamdavey]

Sorry to give you work Mike and thank you for working a fix! If you would like me to check out a beta code, juet let me know. I have X4R and S6R available to test.

 

[MikeB]

I've posted what should be V84 for those two receivers in the BETA test thread.
My testing all seems OK.

Mike

 

[alm_nl]

Is it recommended to do a rebind when going from UNI v0.57 to v0.83 on an X8R? It's still bound after the upgrade, though.

 

[MikeB]

No rebind should be needed.

Mike

 

[sam51401]

Not sure if this has been asked, i just joined the forums today.
I am updating my ACCST receivers, S6R, S8R and X8R to UNI and ask if another way to get the rcvr ID is known
that doesnt have me binding and setting a plane to view the unistats on the radio for each receiver with the LUA script?
I have a X20S with 1.5.18 FCC, using a STK tool to load the rcvr fw with v83. Im getting each Rx ID and will be submitting Aloft
shortly.
Another thing im not seeing is a step by step that can guide a new user in processing and loading the FW. Using the STK tool has a few quirks
i found out and i hope there is a better way to obtain the rcvr ID. So far putting the fw on the receiver has been ok once i worked out the sequence
using the STK tool on a PC.
Thanks

 

[MikeB]

I believe most people flash the receivers using a wired connection from the Tx, rather than use the STK tool.
At present the only way to get the ID is to use the script on the Tx.
If you have several receivers, after flashing, I would suggest putting the Tx into bind mode, then power each receiver in bind mode to bind them (more than one Rx may be powered on to bind at the same time).
The activate script for transmitters not running Ethos, notices if you power the Rx off, and then reads to ID again, so would pick up the ID from a different Rx. At present, it seems, the Ethos script only ever reads the ID once (I didn't write that script!).

Mike

 

[MikeB]

When using a XJT Lite, it seems Ethos doesn't recognise the scripts need to communicate with the external module. Ethos may be able to check for received data from either, but appears to only send the requests to one of the internal or external modules.

Mike

 

[WimH]

Two questions:
1) Where to make the "short" on a D8R ( same as D8RIIplus?) for overwriting the Frsky bootloader?
2) How long does it take these days to get an activation code (for my X4R) from Aloft. Does it make sense to ask again ? ( I did get an automatic reply...)

 

[Chris]

If you ask for a code on the weekend you will usually not get a response until Monday.

 

[MikeB]

Check this post: https://www.rcgroups.com/forums/showpost.php?p=42901485&postcount=133.
Another post following that indicates the pads are labelled R22 and are in a corner of the main PCB.

Mike

 

[WimH]

If you ask for a code on the weekend you will usually not get a response until Monday.

Thanks, got the code from you about 2 hours ago, and it worked!

 

[WimH]

Check this post: https://www.rcgroups.com/forums/showpost.php?p=42901485&postcount=133.
Another post following that indicates the pads are labelled R22 and are in a corner of the main PCB.

Mike

Thanks, cannot find them on the pic, but finding R22 on the actual receivers should be easy enough. I had a small problem with my X4R, flashed it from my Zorro/OTX with 4in1 module and I think I chose D16 8CH or so. Getting the receiver code worked but the activation code apparently did not do anything (receiver was recognized but no servo output). I gave up trying after a while and tried on my Pocket/Edge with the newest ETX/Lua activation script. First try it would not bind (FrSky X2 ,LBT-EU, telemetry) but it did on the second try. After that the activation went smoothly. It seems to work ok now... Maybe I'll have a go at making some kind of manual, trying to avoid looking all over the place for the correct files/procedures...

 

[alm_nl]

Just tried to activate an S6R, but the v4 script at https://github.com/offer-shmuely/fr...ob/main/edgeTx/SCRIPTS/TOOLS/UNI-Activate.lua didn't activate it (kept saying LOCKED). Have tried a few times, also power-off/on again. When I used version 1 of the Activate script it worked right away. TX used is X9D+.

I've created an issue in the github repo.

 

[MikeB]

What firmware on the Tx? erskyTx, openTx or edgeTx?

Mike

 

[alm_nl]

What firmware on the Tx? erskyTx, openTx or edgeTx?

Mike

OpenTX 2.3.15 (compiled from sourcecode of March 8, 2025).

 

[MikeB]

I just tested this on a X9Lite running openTx 2.3.15b (the one I've published built from the "latest" sources, dated 02-Jan-2025) and it worked without any problems.
I used a S8R, sent the wrong code 3 times to make it locked, then rebound the Rx and sent the correct code and it activated immediately.

Mike

 

[alm_nl]

I just tested this on a X9Lite running openTx 2.3.15b (the one I've published built from the "latest" sources, dated 02-Jan-2025) and it worked without any problems.
I used a S8R, sent the wrong code 3 times to make it locked, then rebound the Rx and sent the correct code and it activated immediately.

Mike

With version 4 of the UNI Activate Script? If yes, then it's strange as the sourcecode of 2025-03-08 (of OpenTX) is just the same as 2025-01-02 except for CREDITS.txt, but that should not matter. Unless there's a difference between the radio's that explains it.

 

[MikeB]

I've done some further testing, and found the activate script doesn't always work depending on what Tx and what version of different OS I use.
In the function "refreshSetup", "result" is declared as a local. This change doesn't work and that line should be removed. That seems to fix the problem.

Mike

 

[alm_nl]

I can try, but that won't be today anymore. Will get back.