How to bind several Tx to one model

Is there a way to restore the factory ID later on?

You restore the factory ID by re-installing the devention firmware.

DeviationTx uses an id built from the MCU serial number if you don't provide one in the tx.ini file. You get that one back by deleting the entry from the tx.ini file.

Yeah! this is super cool kudos to the devs !!!

So what happens if you turn both tx's on, both set to the same model at the same time?

Hi,

Another question , could I get a TX ID to be able to copy it in another TX, so I do not have to bind all my models again, thanks.

stevecox wrote: Yeah! this is super cool kudos to the devs !!!

+1 !!!

Dug this back up cause I was finally willing to risk turning on 2 TX's at the same time today and...

[build suspense here]


Nothing happens... You turn the 2nd one on and there's no glitch, no nothing, then when you turn the first one off the 2nd one immediately has control. You can repeatedly switch back and forth and again, while they're both on whichever one was on first will have control and the other will do nothing.

This is with an X4R and Hexfet's frskyX_drop test build, Devo 10 and Devo U7E.

Sounds like you can use a second radio as a trainer without a trainer cord.

Cool.

Not really, the "student" would have to recognize they're about to F up and switch their tx off. All the training I've done I've had to take back control...

So cool. Thank you.
I just set the same tx id for my Devo 7e and Devo 10.
Tested with my V911 - works like charm. (Once I realized the FixedID being different and set to the same on both remotes.)
No more rebind switching between the remotes

Hi again,

Anyone got any ideas for how to find the TXID of my taranis so I can set my two devo's to match?

Issue with taranis is the RF module has its own locked FW and TxID isn't under OpenTx control so OTX can't access it (even just to see it) and it can't be sniffed from MCU -> RF module comms.

I was thinking maybe sniff traffic from receiver CC2500 to its STM32? Should that reveal the txid if I sniff the traces @ bind time?

i would be interested in this, too

I have a Taranis X9E with a multiprotocol modul (midelic) and a Devo 12S and a Devo6S
Would be fine to set them all to the same TXID.

I'm working with RCgroups member FishPepper on a device to read the TX id of Taranis over-the-air @ bind time, Devo's txid can then be set to match that.

Problem being open-tx doesn't have serial control over the internal HF module so there's no setting of the txid, in fact Open-TX doesn't so much as ever see the txid and the firmware on the internal Xjt is locked and not in communication with open-TX.


If you really really like to tinker there's always ER9x firmware that can run on your taranis, installing it gives you the option of rewiring the internal Xjt module to the spi bus means you can somewhat control it (note there's still no Open-tx setting for txid but you could do your own custom build of ER9x and maybe make some progress there).


BY FAR the easiest thing to do is just add bind buttons to all your models in accessible spots [sorry, this is what I do now and why I'm working with FP on his solution. Note he has it working on an A7105 w/ Fly sky, just gotta get it modded for CC2500/Frsky!

Didn't notice you were running an external multi-module... Great news; you have full FW control of that (not from the Gui, you'll have to make your own build) but in the code you can force set any txid you'd like, set that to match your devo's, compile, flash and you're g2g!

thanks for response

i didnt find the place in the multiprotocol code to force my own TXID.
I've seen the problem with the fixedID....at least, too.

Hi
Small question, before doing a bullshit
Thanks

here is where i put mine on all 3 of my transmitters and it works perfect...