What's new
By:
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)

Hlaalu said:
Could someone please explain to me the difference between:

- UNI-Statistics.lua
- uniStat (containing main.lua and lang.lua)
- XxRStatv5e.lua
Click to expand...
UNI-Statistics.lua - Version to use on non-Ethos radios
- uniStat (containing main.lua and lang.lua) - Version for Ethos based radios
- XxRStatv5e.lua - Old version developed from the script for the D8 receivers when only the X8R and X4R were supported.

There is a limit to the number of attachments on a post on this forum, so "UniActi.zip" (and other files) are on the second post.

If you plug power in to a receiver with the connector reversed (upside down), the Rx appears to operate but doesn't work well, and may become damaged.

Mike
 
MikeB said:
UNI-Statistics.lua - Version to use on non-Ethos radios
- uniStat (containing main.lua and lang.lua) - Version for Ethos based radios
- XxRStatv5e.lua - Old version developed from the script for the D8 receivers when only the X8R and X4R were supported.
Click to expand...

My radio is a Taranis running last release of OpenTX, so UNI-Satistics.lua should work. But it doesn't. XxRStatv5e.lua works instead.

As for the Rx being fryied, I think it was a (stupid) mistake by my part. I downloaded the file from GitHub, but I right-cliked on the file and "save link as...". It downloaded me a seemingly normal .frk file, but it was 170+ KB large, as opposed to 40 KB.

Now I am still perplexed as to how on earth a wrong firmware, however "wrong", can physically damage a receiver beyond salvation. Pin wiring was absolutely correct.

In your experience, is the above possible? Or should I be looking elsewhere to understand what happened?

Also, could this have damaged the Taranis hardware somehow?

Thank you
 
Last edited:
Should be the same code so should work on both receivers.
Check you have the SPort set to be SPort and not FBUS.
Please confirm the actual version of UNI you have on the RX8R-PRO and the R-XSR.
Can you try the MRSC script with the RX8R-PRO?

Mike
 
FBUS is OFF for both RX and they have firmware V83. I just ordered some PicoBlade male connectors to build a harness to connect a spare RX8R PRO instead the R-XSR to my Heli with the MSRC sensor to do this test. The Heli with the tested RX8R PRO has different sensors connected. I will be able to do tests beginning next week.
 
I just tested my R-XSR with V83 and a FrSky vario sensor. Using the attached sensor_config.lua, (slightly changed from the one to which you linked) I am able to change the physical ID of the vario, so all seems to be working.

Mike
 

Attachments

Mike many thanks for testing. Your updated script is now also working for the Heli with MSRC. It can communicate with the FAS100S and FLVS sensors but not with MSRC. Looks to be there are still issues with MSRC itself.
 
Hi Guys,
I have been using uni since it came out and have loved it. recently, setting up a larger plane and found the RB25 on sale so bought one.
setup an rx8rpro and an RX6r as second reciever. setup the plane the way i wanted. all surfaces and devices worked as setup.
then tried to setup my failsafe. no matter what I set it to on the radio, all surfaces go full throw opposite when i shut the radio off. that was trying to set though the rb25. so i tried setting failsafe seperatly bound from rb25 and still same resullt when i shut radio off. is there a special process for setting failsafe with the rb25?
X12s running openTX 2.2.4
 
I think someone had recently posted that the RB uses a special script to set it up..?
 
There has been a report of loss of signal for 5 seconds when using UNI on a X8R with a spark ignition engine (Log file here: https://www.rcgroups.com/forums/showpost.php?p=54111909&postcount=82).
My conclusion is it is likely the internal registers of the CC2500 RF chip got corrupted due to interference from the ignition resulting in no packets received for the 5 seconds UNI keeps following the hopping sequence before reinitialising the RF chip (FrSky firmware only follows the hopping sequence for around 1 second, then re-initialises the chip).

With UNI, if no packet is received, then no telemetry packet is sent back. Doing this fixes the occasional telemetry corruption. In the time taken to send a telemetry packet, there is more than enough time to reinitialise the RF chip.

So, I'm considering a change to UNI where if no packet has been received for a certain time, the RF chip will be reinitialised while continuing to follow the hopping sequence. Any possible RF chip corruption will therefore be corrected quite quickly. I cannot see any downside to doing this.

I just need to define how long to wait before doing the initialise. My current thought is 0.18 seconds (20 packet times) would be a reasonable time. Assuming it is only RF chip corruption causing the packet loss (not ignition noise blocking the signal), then the next packet should be received OK, so control should be regained in less then 0.2 seconds.

Anyone any thoughts on this?

Mike
 
Hi Mike,

I'm trying to think my way through any possible implications for link quality. If the threshold for reinitialization is 20 sequential lost frames, reinitialization could occur with LQ as high as 80%. Did I get that right? I suppose reintialization could also be triggered at a lower LQ if there had been prior non-sequential lost frames. Regardless, is there ever any reason for concern?

The topic brings reminds me of ELRS' handling of Dynamic Power. Dynamic Power, too, ramps up very early during what may or may not turn out to be a critical threat to the RF link. I don't recall the exact threshold (if in fact I ever know it), but I do remember an ELRS dev saying something like, better safe than sorry.

If you go ahead with the change, the fellow in the RCG (funaro13) thread might be an ideal tester.

Andrew
 
I subscribed to the RCG thread just to keep track of what happens.
I've never tried running an X8R in a gasoline powered plane before simply because the RX8R Pro was created specifically for ignition engines. So my gas powered planes have RX8R Pro receivers, and so does my turbine jet. No problems to date with these.

Does the UNI firmware in the X8R and the RX8R Pro operate the same as far as what happens when packet loss is detected?
 
Hi Guy's
My TX is a x20s running Ethos 1.6.3 and the receivers are S6R and S8R running UNI
I am confused regarding which LUA files I should be using and also the correct procedure for setting the receivers up. I have set these receivers up before using Frsky software and had them working correctly so I know what to expect.
Any help or suggestions would be most appreciated, many thanks
Dave
 
I'm not running Ethos, but maybe this post from another thread might help?
The file he is referring to are in the first two posts of that thread.
His Update is probably what you need to read.

S

Post in thread 'UNI receiver Firmware Release FIles (Universal ACCST D16)'

Trying to setup a S8R with uni 83 on ETHOS 1.5.18 and the latest ETHOS files given in this thread. The rcvr binds and i have control but in the UNIset 2.0, i have no calibration and i tried the uniset2 zip with the .LUA files and the UNIset script doesnt show. I reloaded the ETHOSuniscriptsV2 from the zip file above and it shows again. Does the receiver need to be plugged into the radio by chance? I find no info
in the .pdf that gives that suggestion. I get nothing like what is shown in that pdf instructions. What am i missing here to use the uni calibrating function as i have no...
*****Update, Ok i got it going but suggest an amendment to the second post that addresses ETHOS radios and what is required for those. After reading the pdf again, it refers to a file that is listed in the FIRST post, "UNI-SxR.zip" for the calibration part so i added it to my scripts on my X20S and got the S8R setup. Besides the files in the second post, the one given needs to be added from the first listing post and your off and running.
 
WombatDave, I posted that and can help further if need be. Once I loaded that other script and then calibrated the receiver, it works in all three modes. The one thing I haven't tried yet is the self check function still.
 
Hello! I´m looking for a sulotion for my S6R (a few of them) to get CH7.

I already asked at the other thread at RCgroups. hope it´s ok when I post that link here. Would be interested in any helping information. Thank you!

RC Groups (see #979)

Best regards,
Alex
 
I’m using an RX8R Pro receiver that’s been updated to the uni_RX8R-PRO_v80.frk firmware. I’d like to configure the output PWM rate to a faster setting suitable for digital servos. Could someone point me to the correct procedure or settings menu to make this change?

Many thanks,
 
On the second post of the release files thread is the UNI setup guide. Details for this are in there.
Note that in V80 firmware the servo rate settings are specific to the bound Tx. If you use the dual bind feature to change to the "other" Tx, the servo rate settings will need checking.
V83 firmware (and later) change this and the servo rate settings are common to both transmitters.

Mike
 
Mike,
Thanks for the info. I was successful setting channel pulse period with the script. I have been doing the updates with Frsky Q7 radio with Open TX. However, my main radio I use is a Frsky Horus x10S with the FROS. When binding the receiver to the X10S, the original pulse settings revert to the slower update rate for analog servos.

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

Many thanks!
Terry
 
You must log in or register to reply here.

Similar threads

R
FrSky Access and Accst Issues
Replies
2
Views
279
alm_nl
A
E
X10S ACCESS Upgrade module installation process question
Replies
5
Views
805
alm_nl
A
V
Best firmware and method to repurpose FRSKY TH9X with ACCST module and D4R-II rcvr for BOT???
Replies
2
Views
353
MikeB
MikeB
John in Boston
Firmware Upgrade(s) for (now-early) FrSky X-Lite transmitters?
Replies
4
Views
1K
alm_nl
A
B
Need Internal RF module firmware file for X12S
Replies
3
Views
2K
Bill Sanford
B
Back
Top