Binding two X8R receivers

[Wayne]

Yep, since you have X9E radios, this is very possibly the case you are running into. Good job Mike!

This is why you could not do with with FrSky firmware on the receivers either.

You will need to burn new ACCST firmware and may not be a bad idea to update OpenTX too.

 

[48thFleet]

By my math you are still short a PWM output (8x2=16). Are you using S-bus to pull out the extra channel? Set up a dummy model with more than 8 channel. Verify that you are out putting more than 8 channels per the monitor screen and bind per the pamphlet.

Can you tell us what Radio experiance you have? Are you coming from Spektrum? make sure you are binding ber Frky's procedure.

Yes I agree being short the output. No, I am not using S-bus,, but rather binding two receivers, 2x8. I tried to bind two receivers to my model which has 17 CH, I plan on using an external module as well. I have attempted binding by the FrSky pamphlet, with and without using a jumper, via the Aloft UNI directions as well.
I have three other X(E's, all of which are bund to two receivers/model. I also am using the X12E, both with OTX and FrSky Horus OS. Both of those radios are also bound to models carrying tow receivers. Before that it was Robbe analog.......

 

[48thFleet]

According to the manual for the PXX protocol (the one used between the radio and the Tx module), support for setting "no telemetry" and "CH9-16" was added in May 2016. If your Tx modules (Tx as a whole) was bought before then, the Tx module will NOT support this functionality.
It is likely you will need to update the firmware on the Tx module (not openTx itself).

Mike

Thank you Mike. Now you are scaring me....

Yep, since you have X9E radios, this is very possibly the case you are running into. Good job Mike!

This is why you could not do with with FrSky firmware on the receivers either.

You will need to burn new ACCST firmware and may not be a bad idea to update OpenTX too.

Wayne,
This sounds like a job for someone who knows what they are doing. Know anyone? Me thinks my remedy is to box her up and sent her to Aloft. Would you want receivers seent as well, and because I plan on using an external module, should I sent it also?
Thank you all for you input. Even Neophytes can learn....
Jonathan

 

[48thFleet]

Thank you Mike. Now you are scaring me....

Wayne,
This sounds like a job for someone who knows what they are doing. Know anyone? Me thinks my remedy is to box her up and sent her to Aloft. Would you want receivers seent as well, and because I plan on using an external module, should I sent it also?
Thank you all for you input. Even Neophytes can learn....
Jonathan

Gentlemen,
I am having second thoughts about the solution to my issue binding receievrs. Here is why. I have attempted to bind the same receivers, UNI programmed by Aloft, to two other X9E radios. Each X-mitter is running update software compared to the "original" radio that exhibited the inability to bind. Each of the subsequent radios have been and is bound to multiple receivers PER model, ie 2 each, which function correctly. Neither of these two xmitter will bind in D16 mode to the UNI receivers. They will bind to both receivers, and operate them simultaniously, BUT only on CH 1-8 or 9-16 while sharing the same CH range. It makes no difference if Tele is enabled or not.
I have approached this issue every way I can think of. I have xmitters that are operating in D16 mode, but they will not bind to these receivers in this mode. How can it still be the xmitter?

 

[Konrad]

What is the TX updated software? This is not an OpenTX issue. Rather the XJT RF module FW.

There are multiple micro processors in your radio. Each has its own FW packages associated with it.

If saying you updated the FW please tell us what version you updated. This will clue us into what micro processor you were trying to update.

I know Aloft has a few X9E as test beds. Maybe they can verify that the Uni FW will channel expand over 2 RX’s. (I’m 90% sure I’ve done this, and with X8R’s)

 

[MikeB]

I got my X9E out and flashed the internal module with old firmware. I tried several, all dated 2015 or earlier. They all bound OK, but none of them would switch to CH9-16. One of them didn't operate the Rx either.
When I flashed later firmware (V1 or V2), the bind selecting CH 9-16 worked correctly.

I would recommend updating the firmware of the internal module. Assuming you are running openTx, this should be straightforward as you may flash the module from openTx.

Mike

 

[48thFleet]

I got my X9E out and flashed the internal module with old firmware. I tried several, all dated 2015 or earlier. They all bound OK, but none of them would switch to CH9-16. One of them didn't operate the Rx either.
When I flashed later firmware (V1 or V2), the bind selecting CH 9-16 worked correctly.

I would recommend updating the firmware of the internal module. Assuming you are running openTx, this should be straightforward as you may flash the module from openTx.

Mike

As someone who is still using an abacus, I am assuming that when you refer to the internal module, you are referring to the XJT RF module, correct? Or should I be looking at the OTX v2.3.9? Thanks for the help.
Jonathan

 

[Konrad]

I got my X9E out and flashed the internal module with old firmware. I tried several, all dated 2015 or earlier. They all bound OK, but none of them would switch to CH9-16. One of them didn't operate the Rx either.
When I flashed later firmware (V1 or V2), the bind selecting CH 9-16 worked correctly.

I would recommend updating the firmware of the internal module. Assuming you are running openTx, this should be straightforward as you may flash the module from openTx.

Mike

Thank you Mike!

Jonathan,
This was the FW on the XJT, it has nothing to do with OpenTX. What is your abacus? if it has USB drivers you should be able to down load the XJT firmware off the FrSky site and upload the FW to your RF modules (both the internal and external modules).

I not buying your feigned incompetence at programing if you are writing OpenTX models with 17 channels. Wayne will tell you there are few that are worse than I, at manipulating bits and bites! If you have a computer that is less than 25 years old and has a USB port you should be able to do the FW updates. I don't think one can do this off a phone or mobile device.

BTW, what version of OpenTX are you running? I'm running OpenTX 2.2.4 on my 2018 X9E with the modern ACCST v2.1.X update on both internal and external XJT RF decks.

 

[48thFleet]

Thank you Mike!

Jonathan,
This was the FW on the XJT, it has nothing to do with OpenTX. What is your abacus? if it has USB drivers you should be able to down load the XJT firmware off the FrSky site and upload the FW to your RF modules (both the internal and external modules).

I not buying your feigned incompetence at programing if you are writing OpenTX models with 17channels. Wayne will tell you there are few that are worse than I at manipulating bits and bites! If you have a computer that is less than 25 years old and has a USB port you should be able to do the FW updates. I don't think one can do this off a phone or mobile device.

BTW what version of OpenTX are you running? I'm running OpenTX 2.2.4 on my 2018 X9E with the modern ACCST v2.1.X update on both internal and external XJT RF decks.

LOL. Well Konrad you may well be seeing thru my veil. I am running otx 2.2.4 BUT i HAVE NO IDEA WHICH ACCST version. I can not find any info regarding that on my X9E. I have read of problems with FrSky's latest ACCST release, but my models are ships, not aircraft and I do not expect to mix receiver brands, s I will go that route. Thank you for your help.

 

[Konrad]

I don't think your radio will not report what ACCST version you have. You just have to keep track of your updates. That is upload the ACCST XJT firmware and record the number (I have a piece of tape that I write the FW number).

I recommend ACCST v2.1.x if you have fast boats. But if you are doing slow scale models that can tolerate the possible loss of control for 900 ms you should be fine (safe enough) on ACCST v1.1.x. As you have a lot of D-8 RX I think one could make a strong point for staying with ACCST v.1.1.x.

Not sure what mixing receiver brands is all about. Also what issues are you hearing about ACCST 2.1.x?

 

[Wayne]

Yes, we can do the updates for you. But first let me have @Chris do a quick test here with our X9E (think we still have one) and confirm all is good.

 

[48thFleet]

Thank you Wayne,
Chris has reached out to me and I just wrote back.
Jonathan

 

[Jammo]

Mike,
Yes I do. Here is my routine: Select D16 mode, Set xmitter to CH1-16, Prepare the xmitter to bind on CH 1-8 +Tele, Power up X8R with Bind button depressed, engage Xmitter into bind mode with selected channels. The receiver will bind correctly. Disengage the receiver from power. Set the Xmitter to prepare to bind the second receiver, same receiver ID #as the first , but with CH 9-16 selected WITHOUT Tele. Power up second receiver with bind button depressed, Engage the Xmitter in bind mode with the selected CH's. The receiver binds, BUT the second receiver binds to CH 1-8, NOT CH 9-16. With both receivers powered up, the xmitter controls BOTH receivers on CH 1-8.
Any thoughts?

Hi Mike how do you power both receivers. Do you have seperate power supply or does the one receiver power the other?

 

[Jammo]

I have bound several models with multiple receivers, specifically X9E's to X8R's without issues and the new UNI receivers bind beautifully. That said I can not get my current radio to bind to two receivers on channels 1-16. For all intensive purposes it appears to stay in D8 mode, even when D16 mode is selected. I can bind the two receivers to the radio, but they both bind on chaaneels 1-8. Has anyone else ever run into this and if so, what was the solution? Thank you, Jonathan

Hi Mike, how do you power the second receiver? Do you have a seperate power supply or does one receiver power the other?