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!
Thanks Mike but I checked my Taranis (which I used for the update) and the file in FIRMWARE is UNI_x4R_84sm.frk
I should check that I did not inadvertently use the x8r file which is below the x4r one.
EDIT I have re-flashed the UNI_x4R_84sm.frk and I'm now getting the correct voltage. Thanks for advice.
As an aside, on another model with an RX8R-PRO installed, using my X18 (on Ethos) if I check the Telemetry signals for RxBat, it is giving me the correct voltage but if I stir the sticks vigorously with the radio say <5ft away, the battery voltage signal ceases and the radio reports "internal module telemetry lost", the volts number stops changing and turns red. I have to switch off the Rx to recover. This did not seem to happen with the Tx 30ft away.
I have picked up on a problem with RxBat on the RX8R-PRO, I have a fix tested for that, it may be the same as your problem.
Do you lose RSSI as well as RxBat? Every telemetry packet has one of RSSI and RxBat in it, alternating which is sent.
I haven't released the fix for the RX8R-PRO as I'm adding the ACCESS protocol to UNI.
Typically FrSky will do a very large production run for a given radio type. This run is probably enough to meet global demand for anywhere from 6 months to several years depending on demand for tha version and that color. They do install the current stable release at that time. It is boxed and stored until purchased by individual or distributor. If a distributor, then it will continue to be stored until sold. You can tell how long ago your radio was built more or less based on the version of firmware installed. (FrSky may skip minor updates at the time of construction.)
Now onthe software side of things, frSky does not have a hard set firmware update release schedule. They release when things have progressed and there is enough reason to release. This could be every few weeks, or every few months, but it is pretty often compared to other companies. They are very software based and like to add features and fix bugs. It can be a little trying to see a bunch of updates, but it sure is nice to see the firmwares mature and add features.
Other radio companies are very poor about fixing well done bugs in their radios. Futaba for example had known bugs, not only did they never fix the bugs in the production life of the first model of radio, but they used the same basic software in later versions several years later and they still had the same bugs.
Other radio companies are very poor about fixing well done bugs in their radios. Futaba for example had known bugs, not only did they never fix the bugs in the production life of the first model of radio, but they used the same basic software in later versions several years later and they still had the same bugs.
Futaba is overrated, in my club most people fly with Futaba but most do not even know how to program things that are basic things in OpenTX/EdgeTX/Ethos. New rooky members are told to buy Futaba and they mostly keep flying with it, not knowing there are easier (and cheaper) systems out there.
However, UNI is what FrSky should have created themselves. Just one firmware that deals with ACCST v1/v2 and FCC/LBT.
There's also people with Spektrum, Jeti, Graupner, Multiplex, Powerbox and FrSky (which I use myself). And some 3D heli-pilots fly with Mikado VBar. So, it's not only Futaba.
The first post of the release files thread now includes a test version of UNI that supports the ACCESS protocol as well as ACCST.
On older receivers (e.g. X8R) check if you still need low and critical RSSI levels set to 45 and 42.
To use ACCESS, simply power the Rx on with the button pressed and register the Rx.
With the button pressed at power on, the Rx will detect an attempt to register in ACCESS mode as well as binding in one of the ACCST modes.
The ACCESS implementation does not support the SHARE feature, but does support Dual Bind, just register the Rx to two transmitters.
Please TEST carefully BEFORE USING TO CONTROL A MODEL.