John Wagg Posted April 29 Share Posted April 29 2 penny worth - do both TXs have to be on the same protocol ? and are they ? Distance from the Rx may be an issue - to close ? Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 29 Share Posted April 29 Just about a meter away. Similar distance to the original bind process. Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 29 Author Share Posted April 29 No they don't have to be on the same protocol. Does the problem happen with both transmitters? Call them A and B. If you bind A first, then B, A is the "other" Tx so should bind when in bind mode and you power on the Rx. If you bind B first, then A, B is the "other" Tx so should bind when in bind mode and you power on the Rx. Mike Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 29 Share Posted April 29 Doesn’t matter which tx is a or b. Bind to a. Then bind to b. Then try and bind back to a and it won’t. Doesn’t matter which tx is which a or b. It will not bind back to the other as expected in uni. Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 29 Share Posted April 29 Reflashed from sd card. Reactivated. Same problem. It won’t remind to other tx. Binding and rebinding done at about 3 meters distance. Only thing left is to down load a new cut of the firmware maybe? Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 29 Author Share Posted April 29 When binding normally, how are you doing it? In particular, are you holding the bind button pressed until binding completes? If so, then the Rx will see the bind button activated after binding, and this invokes a feature that erases the bind of the "other" Tx. Normally you do this, if required, by pressing the bind button after binding completes. To bind, I start the Rx in bind mode (power on with bind button pressed), and see the Rx has the red LED on, but blipping off every half a second (it is changing protocol when it blips). Then start the Tx binding. Mike 1 Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 29 Share Posted April 29 2 hours ago, Mike Blandford said: When binding normally, how are you doing it? In particular, are you holding the bind button pressed until binding completes? If so, then the Rx will see the bind button activated after binding, and this invokes a feature that erases the bind of the "other" Tx. Normally you do this, if required, by pressing the bind button after binding completes. To bind, I start the Rx in bind mode (power on with bind button pressed), and see the Rx has the red LED on, but blipping off every half a second (it is changing protocol when it blips). Then start the Tx binding. Mike Sorted! Thanks Mike. 1 Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 30 Share Posted April 30 The speed and depth of the support for the UNI firmware is impressive and much appreciated. Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 30 Author Share Posted April 30 I'm adding a note, about the bind button being pressed at the end of binding, to the guide. Was that the reason for your problems, or is there something else I should add? Mike Quote Link to comment Share on other sites More sharing options...
Wookman Posted April 30 Share Posted April 30 That was exactly the problem. Holding the bind button down until the receiver had bound was what I was doing. Normally not a problem, until UNI comes along. Set the receiver to bind and release the button prior to setting the tx to bind. Bind to each tx like this and the rx swapped between txs very quickly with no problem. Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 30 Author Share Posted April 30 OK, even with the FrSky firmware you only need to hold the button pressed while powering on, then you may release it (typically after 0.5 to 1 second). Mike 1 1 Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted June 18 Author Share Posted June 18 UNI firmware for the R-XSR is now in beta test. It all appears to work fine, I just need to add the CPPM support. Mike 1 Quote Link to comment Share on other sites More sharing options...
Torsten Spitzner Posted October 10 Share Posted October 10 Need some help please. I have Installed my first Uni-Rx firmware on an RX8R and activated with the activation code and that seems to be successful. The green LED is on solid, the VFR is found under the sensors and when switching power to the Rx on and off, the familiar 'telemetry lost, telemetry recovered' is uttered. However, none of the servo outputs are working. I did make and error when trying to enter the activation code in that I flashed the Rx with the firmware again, then I re-read the instructions again and and went to the 'Activate' setting and entered the code. Would that have caused issues? Quote Link to comment Share on other sites More sharing options...
Wookman Posted October 10 Share Posted October 10 It sounds like you have an issue with the activation code/process. Have you miss read the code? Have you miss typed the code? I am sure Mike will lend a hand after he has had his coffee. Quote Link to comment Share on other sites More sharing options...
Torsten Spitzner Posted October 15 Share Posted October 15 Just to follow up. All sorted and working, thanks to Mike B over on the Aloft forum. Easy when you know how... Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted November 14 Author Share Posted November 14 UNI firmware for the R-XSR is now available. Mike 1 Quote Link to comment Share on other sites More sharing options...
John Wagg Posted November 15 Share Posted November 15 Hi Mike' Will there be any chance of 'UNI' for the XM+ ? I have one but it is very prone to swamping which is a big problem when hand launching. I also have an R-XSR which I would like to change to the 'UNI' firmware but I don't really understand how the 'code' system works. I understand somehow that an individual reference is produced, after flashing, which is sent to Aloft or T9 who gives out a code to enable the Rx. I've gone through all the Aloft, RCGoups etc' posts but nothing explains the actual process. (that I can find.) Aloft said they would do a short video but, unfortunately, that doesn't seem to have materialised. No problem in the initial flashing process, just the follow-up. Any chance of a 'blow by blow' beginners guide please ? Best regards and thanks. John. Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted November 15 Author Share Posted November 15 Sorry the XM+ uses a different processor that doesn't have enough flash/RAM for UNI, and also needs a specific compiler. Please look at this thread: https://forum.alofthobbies.com/index.php?threads/uni-receiver-firmware-release-files-universal-accst-d16.3270/, go to the second post and read "Universal ACCST Guide.pdf". Let me know if you then need more information. Mike 1 Quote Link to comment Share on other sites More sharing options...
John Wagg Posted November 16 Share Posted November 16 Mike, thank you very much for the reply. Also thankyou for the pointer to the instruction PDF. Downloaded and will ingest today. Shame about the XM+ but I get swamping easily within 4 feet so virtually useless for hand launching (slope soarer's and park fly's.) Regards John Quote Link to comment Share on other sites More sharing options...
John Wagg Posted November 17 Share Posted November 17 Flashed my R-XSR with the 'UNI' firmware and bound it. Ran the Lua script (UNI_Activate.lua) and got the code. Just waiting for a reply from T9 now. Strange thing was when flashing the R-XSR it showed a green LED which it was interspersed with the odd red flash every now and again. Previously when I have flashed other receivers I haven't noticed any red LED just a constant green. I presume it must have worked as I got the 12 digit receiver code. Quote Link to comment Share on other sites More sharing options...
John Wagg Posted November 21 Share Posted November 21 On 17/11/2023 at 11:24, John Wagg said: Flashed my R-XSR with the 'UNI' firmware and bound it. Ran the Lua script (UNI_Activate.lua) and got the code. Just waiting for a reply from T9 now. Strange thing was when flashing the R-XSR it showed a green LED which it was interspersed with the odd red flash every now and again. Previously when I have flashed other receivers I haven't noticed any red LED just a constant green. I presume it must have worked as I got the 12 digit receiver code. Received the activation code from T9, ran the Lua script, and now up and running. Just need to do a range check now - when the weather plays ball. 🙄 Thank you very much Mike for the help. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.