payneib Posted April 24 Share Posted April 24 Evening All, I've just spent another fruitless evening trying to get £150 worth of Rxs to work with my X9D 2019. I had two RX8R Pros working fine, until I had to update my internal module firmware to ISRM v2.1.10 in order to register/bind a new ACCESS SR10 Pro. This caused the two ACCST RX8s to unbind, one of which was flashed with ACCST D16 v2.1.1, and rebound - it's since been flying and still works now, along with the SR10. I now have one RX8R Pro mounted but not flying, and two new RX8R Pros, which regardless of what firmware they're flashed with, will not bind with the Tx. I'm completely out of ideas. The only thing I can think of, is if there's a possibility of copying the working Rx to flash the other three. Or maybe I'm not binding correctly and the working one was a fluke. Or maybe there's a problem with the three Rxs (although one was working before this all started). I think my next best option after this to change everything back to nice cheap FlySky radio kit that just works, and just give up on the fancy talking radio because it's massively over complicated. If anyone has a simple answer that'll get all of my Rxs working with my TX, that'd be great. Quote Link to comment Share on other sites More sharing options...
RottenRow Posted April 24 Share Posted April 24 Have you tried flashing the receivers with the UNI firmware? This eliminates the issue of different ACCST versions and LBT etc. Note that with the UNI firmware, you can bind the newly-flashed receiver (so you get a solid green LED) but you won't get any servo operation until you activate it using a code that you get from T9 or Aloft Hobbies. Also, sometimes a receiver won't bind if it is too close to the transmitter during the attempted binding process. Try them a few feet apart. Brian. Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 24 Share Posted April 24 I assume you are certain they are RX8R PROs and not RX8R (the "PRO" text is difficult to see!). UNI firmware on the Rx will eliminate the need to make sure you have compatible firmware on the Rx. Mike Quote Link to comment Share on other sites More sharing options...
Kim Taylor Posted April 25 Share Posted April 25 In my experience, it's important to have a metre or more distance between the tx and rx when binding the RX8R. They're also prone to swamping if you're too close to the model when testing/setting up, giving nuisance 'telemetry lost ' announcements. I've heard that the uni firmware doesn't do this - Mike?? Kim Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 25 Share Posted April 25 UNI does avoid the swamping problems, as the RSSI value becomes very high it turns off the front end amplifier and reduces the telemetry transmit power. Mike 1 Quote Link to comment Share on other sites More sharing options...
GrumpyGnome Posted April 25 Share Posted April 25 Ian, look here.... https://www.t9hobbysport.com/frsky-xr-uni-accst-firmware-receivers Read down to the bottom 1 Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 25 Share Posted April 25 In addition the the receivers listed there, UNI is also available for the XSR and R-XSR. Mike Quote Link to comment Share on other sites More sharing options...
payneib Posted April 25 Author Share Posted April 25 So there's good news and weird news: I flashed the Uni firmware on to all three Rxs and all three bound fine. The good news is, that the (old) mounted Rx started working immediately, which I assume means it's one I bought from T9 and was already unlocked for Uni firmware. The two new Rxs, both bound and I ran the setup script. The weird bit is, I got the same unlock code for both. Is that normal? Or should it be separate codes? Quote Link to comment Share on other sites More sharing options...
Mike Blandford Posted April 25 Share Posted April 25 It is quite possible. The 12-character code is from the processor unique ID, but to use it in full would result in a 20-character code, so the 12-character value may be the same on two receivers, particularly if the processors are from the same batch. This is quite possible if they were purchased at the same time. Mike 1 Quote Link to comment Share on other sites More sharing options...
payneib Posted April 25 Author Share Posted April 25 Tip top, I'll get them emailed off to T9 and hopefully get this resolved shortly. Quote Link to comment Share on other sites More sharing options...
payneib Posted April 26 Author Share Posted April 26 (edited) Good news: both Rxs used the same code from T9, and are now bound and unlocked. I can carry on with winter maintenance now. Although I still think that at £50 a pop, Rxs should just "work" when you open the packet. PXL_20240426_183932256_TS.mp4 Edited April 26 by payneib 1 Quote Link to comment Share on other sites More sharing options...
RottenRow Posted April 26 Share Posted April 26 That’s good news. I’m glad that you got it sorted. They do work straight out of the packet, but you have to have the correct, matching tx firmware. Mike’s UNI firmware overcomes that issue. Brian. Quote Link to comment Share on other sites More sharing options...
GrumpyGnome Posted April 26 Share Posted April 26 (edited) .... Edited April 26 by GrumpyGnome Changed my mind 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.