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!

RX6R Binding Issue

I finally got around to using my new RX6r receiver in a small indoor plane I'm building. I had a little trouble, apparently, getting channels AETR to output to the servos.
I initially tried the D16 protocol on my 9xd+. I current have OpenTX 2.3.1. I bound getting the green LED but then no servo movement. I researched on the web for anything I could find about the Rx, but nothing specific. One blog hinted at holding the bind button too long causing an unexpected mode change. I suspected, for some reason that Channels 1-8 might be muted somehow and tried a mixing on channel 9. The servo moved. I started suspecting that this is normally a quad receiver and not typical for planes.

So while experimenting, I rebound using the D8 Telemetry On option and then all worked well as expected. AETR inputs matched the expected mixed channel order on channels 1-4. The features said is was ACCST D16 compatible. but obviously different than expected. (at least to me)

My question is that I couldn't find anything in the instructions or perhaps I just don't understand what was happening here. Whenever you get new technology you read as much as possible, but maybe I need a little expert explanation as to what was happening here. Why did my expected channels end up on 9-12 when I first selected the D16 protocol? I've used other FrSky Rx's, S8R, RX8R Pro, x8R, XM+ and this is the only one that did this to me out of the box.

Is this an OpenTx 2.3.1 issue unique to this version of software or is it something in the features of the Rx6R that I don't understand. Can somebody explain this to me?
 
Last edited:
It is a normal RX. Are you getting PWM outputs (normal servo)? Just that the channel mapping isn't what you expected (AETR) maybe you are seeing TEAR instead.

Look at the manual to see if you are in fact following the instructions.

Also have you a copy of these great manuals to help with the TX configuration?

I have the OpenTx manual. I've used OpenTx for years (about 8 years?) on above "normal" Rx's. I've used AETR and /or TAER channel order as needed without problem. To be clear, I had no output or servo movement when inputs were mixed on Channels 1-5. Not till I mixed a stick input on channel 9 on Tx did I get a servo movement. Again, I did get output on channel 9 but not on 1-5 when I was bound to D16 Telemetry On. Only when bound to D8 Telemetry On, did I have output i.e. servo movements, on Channels 1-5 as expected. So I am deducing their is something different about how the Rx6R receiver works. I just don't know why. I'm going to try the same binding with a second RX6R I purchased to see if it acts the same.
 
Well you are way ahead of me, I've only programed about 1/2 a dozen models configuration on Open TX. Please let us know what you find.

All the best,
Konrad
 
I created a new model on my Transmitter. I then bound the second RX6R I bought and it bound the same way. Selecting D16 Telemetry On, I had no servo movement on Channels 1-8 mixed with a stick input. I had 5 servos connected and used the 6th position to power up the receiver. Again, when I mixed on Channel 9-14, I was able to get servo movement.

I rebound the receiver bringing down the number of channels to 8 and chose the Telemetry On option. The receiver worked as expected Channels 1-5 had the correct servo movement.

The framerate is different between D8 and D16. The receiver is supposed to be compatible with the ACCST and the new ACCESS protocol. There's obviously some reason binding while using the D 16 option the receiver mutes the output on Channels 1-8, but not 9-16.

Regardless, I can get the receiver to work, but there must be some technical reason why it works this way and it is not explained in the instructions and I am clueless. Perhaps somebody out there can comment on this. I would ask if Wayne, if he has time, to chime in here and explain this.
 
I created a new model on my Transmitter. I then bound the second RX6R I bought and it bound the same way. Selecting D16 Telemetry On, I had no servo movement on Channels 1-8 mixed with a stick input. I had 5 servos connected and used the 6th position to power up the receiver. Again, when I mixed on Channel 9-14, I was able to get servo movement.

I rebound the receiver bringing down the number of channels to 8 and chose the Telemetry On option. The receiver worked as expected Channels 1-5 had the correct servo movement.

The framerate is different between D8 and D16. The receiver is supposed to be compatible with the ACCST and the new ACCESS protocol. There's obviously some reason binding while using the D 16 option the receiver mutes the output on Channels 1-8, but not 9-16.

Regardless, I can get the receiver to work, but there must be some technical reason why it works this way and it is not explained in the instructions and I am clueless. Perhaps somebody out there can comment on this. I would ask if Wayne, if he has time, to chime in here and explain this.

D8 only supported 8 channels so that why it works when you bind. With regards to the D16 binding have a look on the bind page where you select Internal Radio module, near the bind menu box. You will see a menu box labelled start and a second box labelled channels. Normally the start channel could be CH1 and channel could be any number from 1 thru 16. So if the start channel is 9 and the channel number is 16 you are directing the outputs to these channels 9 thru 16. So if you do not need more than 8 channel select the start channel to be 1 channels to be 8 and when you bind Telemetry ON channels 1-8. In 8 channel mode the frame rate will be 9ms. The RX6R can operate on either D16 or ACCESS but this requires the receiver to be flash with either ACCST or ACCESS firmware. Also check on your mix page and confirm your channels are being directed to channel-1 thru 8.
 
Thanks for a logical answer. Yes, I do/did understand that the "start" channel could be different. I sometimes wish I had a video on when choosing initial parameters. Likely I didn't notice that Channel 9 start was being default selected. To take advantage of the lower framerate it makes sense to use Channels 1-8 anyway on this receiver. Again, having bound many receiver types over the years, this never came up. Perhaps a perfect combination of OpenTx software development and new receivers. The development of the latest software forces more exacting selections, the bane of adding more features and finite control. All is well.
 
Back
Top