Universal ACCST Firmware (UNI)

[jmorrow]

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



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

Attached is a version of the Activate script where I updated it to use the new bitwise operators, but it still didn't work correctly on EdgeTX 2.11.3.

 

[MikeB]

I've dug out my prototype X9Dplus and put Edge 2.11.3 on it. I can confirm the LUAs are not working, but do not show any errors.
I've tested the activate script using erskyTx and it works correctly. ErskyTx is now also using LUA version 5.3.
It seems something has changed in Edge.

Mike

Edit: The script is OK if using an external MultiProtocol module.
Edit2: It appears there is an issue on Edge (2.11) regarding sending data to the Rx when using a XJT module.

 

[jmorrow]

I've dug out my prototype X9Dplus and put Edge 2.11.3 on it. I can confirm the LUAs are not working, but do not show any errors.
I've tested the activate script using erskyTx and it works correctly. ErskyTx is now also using LUA version 5.3.
It seems something has changed in Edge.

Mike

Edit: The script is OK if using an external MultiProtocol module.

This commit may have something to do with it. https://github.com/EdgeTX/edgetx/commit/30b89220964faedb157a39470587d118d71f9cf6

I reverted back to EdgeTX 2.10.6 and the script worked correctly.

 

[alm_nl]

The order of reading the channels is also out of order when using EdgeTX 2.11.x with the UNI-Statistics.lua script (using the XJT module inside the X9D Plus).

 

[davemcddd]

Have you tried Edge 2.10.6 to see if it works OK?

 

[alm_nl]

Yes, EdgeTX 2.10.6 (and below) did not have the issue I mentioned.

 

[ScottyDsntKnow]

Recently picked up a cheap Horus 10S Express off of RCG to run Edge with ACCESS and had not really messed with UNI too much before but set up a S6R with UNI and I gotta say I like it better than the new Archer+ as far as how stab is setup and the interface and the ease of it. And then looking at the whole picture, is there any real benefit to move several ACCST planes I have over to access when UNI exists? I'm not seeing a reason if I'm not using TD or TW or needing more than 16ch. Latency, resolution, signal etc... all seem similar for what I'm doing. And all the FrSky sensors work fine with UNI. Maybe I'm missing something?

 

[MikeB]

About the only advantage ACCESS has is it sends packets every 7mS instead of 9mS for ACCST, so just a small reduction in latency.
When running UNI on ACCESS capable receivers (e.g. G-RX8) you do get the improved sensitivity so may set the RSSI warning values to 35 and 32.

Mike

 

[JeromePilot]

hi,
first : congratulations for this great job
Any chance to see a UNI firmware for the ACCST 900mhz receivers ? dual transmitter would be great...

 

[MikeB]

Probably not. The 900MHz uses a different RF chip. I would need to see how this works and see what the protocol is as well. Some of this I could likely find from the multiprotocol code, but would be quite a bit of work to sort all the timing out and test it.

Mike

 

[JeromePilot]

thk for your reply Mike.
I'll find an other solution (on my x9e I can't just swap the module, I need to open it)