What's new
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!

Updating RX4R and RX6R receivers to bind with Taranis X9D+

BillO

New User
I have a Taranis X9D+ 2019 transmitter and a bunch of planes with RX4R and RX6R receivers all working just fine using the ACCST protocol. Then a few years ago I bought 4 more RX4R receivers and 2 RX6R receivers. I have tried binding a few of them lately and they won't bind. What would be the easiest way for me to get these receivers to bind? I'm hoping I can just burn the UNI RX firmware on to them. This then brings up the issue that I don't know how to do that. I have done some searching but haven't come up with instructions for this particular combo. Thanks for any suggestions!
 
They may have ACCESS firmware on them. Have you tried using ACCESS protocol and registering them?

Mike
 
I found the printed instructions that came with the TX and the receiver. The receiver instructions say nothing about the ACCESS protocol or registration. The TX instructions do describe how to register and bind a receiver using the ACCESS protocol. Following the instructions, I created a new model. On the Model Setup page I set the Mode to Internal RF / ACCESS. I left the channel range at 1-16, then set the receiver number to 15 (an unused number). Next I selected the [Register] option of the Module prompt. A small dialog popped up like in the instructions with the message "Waiting for Rx" and the TX started beeping. I went to the receiver, pressed the F/S button and applied power and nothing happened. The receiver name did not pop up in the TX dialog, beeping continued, and the only option available was to exit. It seemed like registration did not happen. I tried it again, this time setting the channel range to 1-8 but it didn't make a difference.
 
A small dialog popped up like in the instructions with the message "Waiting for Rx" and the TX started beeping. I went to the receiver, pressed the F/S button and applied power and nothing happened.

did you power up the receiver and at the same time you were pushing the receiver's F/S button ?
 
I found the printed instructions that came with the TX and the receiver. The receiver instructions say nothing about the ACCESS protocol or registration. The TX instructions do describe how to register and bind a receiver using the ACCESS protocol. Following the instructions, I created a new model. On the Model Setup page I set the Mode to Internal RF / ACCESS. I left the channel range at 1-16, then set the receiver number to 15 (an unused number). Next I selected the [Register] option of the Module prompt. A small dialog popped up like in the instructions with the message "Waiting for Rx" and the TX started beeping. I went to the receiver, pressed the F/S button and applied power and nothing happened. The receiver name did not pop up in the TX dialog, beeping continued, and the only option available was to exit. It seemed like registration did not happen. I tried it again, this time setting the channel range to 1-8 but it didn't make a difference.
The current FRsky radio use 2 types of transmission protocol which you need to select on the transmitter before binding. The receivers mostly can do both protocols but the receiver needs to be flashed with either ACCST or ACCESS firmware. Sounds like you know how to bind when using ACCST protocol.

When binding ACCESS protocols the procedure is a bit different. So select ACCESS on the Transmitter, but don't click register yet. On the receiver press and hold the bind button then apply power, continue to hold the bind button until you see a constant red and green LED. Now press Register on the TX, if successful the TX will instantly reply with the receiver type. Follow the dialog to complete the register process. The receiver LED should also flash. Power the RX down, on the TX select one of the 3 receiver bind boxes then power up the receiver. If successful the TX will respond, follow the dialog to complete the process. Good bind luck, Henny
 
The Receivers may be flashed to use one of three possible protocols: ACCESS, ACCST-FCC, and ACCST-EULBT.
From where did you purchase these receivers? If Europe, they will likely have ACCST-EULBT firmware on them.

For ACCESS, the Tx uses an "OwnerID". Are you using openTx? If so, the OwnerID is in the Radio SETUP menus.

Mike
 
@BillO You mentioned that you bought those RX4R and RX6R receivers "a few years ago". While these Rx's are ACCESS-capable, they were generally always shipped with ACCST firmware installed, not ACCESS. Unless you bought them from a private party, it is more than likely that yours are ACCST.

However, depending on how long ago you got them, they may have a different version of ACCST loaded than is on the Tx. In case you're not aware, there was a major ACCST update (V1 to V2) a few years ago that fixed a significant software bug. If your Tx has the updated V2 version, but the Rx's still have V1, you have an ACCST version mismatch issue. And vice versa, if your Tx is a few years older (and un-updated), it can be on V1 and the Rx's on V2.

The RX4/6R's run great on ACCESS, but you'll need to install that firmware on them first. However, be SURE to select the correct f/w or it will be irreversibly bricked; you'll want to to download it from the product page on the FrSky website.
 
Thanks for all the replies guys! I purchased all the gear new in the US, some from Aloft and some from Amain Hobbies. I tried again today with some success. I forgot to mention that I just got a new Taranis X9D+ 2019 SE recently to have a backup TX. I think maybe I was using that one to bind with, and it wasn't working because it must be on the V2 firmware.

I was able to successfully bind 2 of the RX4R's with my old Taranis, so I'm thinking both the old TX and receivers use the V1 firmware. I'm happy about that. The RX6R's won't bind with either TX, but I don't want to deal with that just yet. First I would like to see if I can downgrade the new TX to V1 firmware using Companion. Then I can use the new TX as a backup for my older TX.

If that works, then I will take up the RX6R binding problem.
 
Last edited:
Thanks for all the replies guys! I purchased all the gear new in the US, some from Aloft and some from Amain Hobbies. I tried again today with some success. I forgot to mention that I just got a new Taranis X9D+ 2019 SE recently to have a backup TX. I think maybe I was using that one to bind with, and it wasn't working because it must be on the V2 firmware.

I was able to successfully bind 2 of the RX4R's with my old Taranis, so I'm thinking both the old TX and receivers use the V1 firmware. I'm happy about that. The RX6R's won't bind with either TX, but I don't want to deal with that just yet. First I would like to see if I can downgrade the new TX to V1 firmware using Companion. Then I can use the new TX as a backup for my older TX.

If that works, then I will take up the RX6R binding problem.
To flash the internal module all you need is the firmware copied to the SD card and you flash the TX within the radio. No need for companion. Aloft could possibly email you the V1 firmware file.??
 
Sounds like a perfect time to install UNI firmware onto those receivers. Worse comes to worse we can do this install for you. You can drop them by the shop, or put them in the mail for us. But it is not all that hard to do yourself. Then your receivers will talk with either transmitter.

Or you can bring them to Sunset and we should be able to instal uni for you there. :)
 
Sounds like a perfect time to install UNI firmware onto those receivers. Worse comes to worse we can do this install for you. You can drop them by the shop, or put them in the mail for us. But it is not all that hard to do yourself. Then your receivers will talk with either transmitter.

Or you can bring them to Sunset and we should be able to instal uni for you there. :)
Now that's amazing service.
 
Back
Top