8s w/ 1002 or 1202rx ???

I would only need to update one of my tx's for it to work correct?

Example: only update my 8s to work with the devo rx's that are already programed in my 12s.

Or would I need to update both 8s and 12s.

Would this effect the binding with a telemetry module?

Im thinking about how the telemetry modual will also need to bind with the tx. It shares the bind code of the rx set by the tx so there should not be a problem, i hope.

I'll download the latest nightly for both tx's tomorrow. Follow the steps you gave above, and rebind both tx's then report the results.

Just for my own clarity, ( yeah, we all know I'm slow..)
Is this for the capability of binding two different model Devos to a set of helis ( devo protocol rx's )?
Or does this also include ANY two Devo Tx's to a set of heli's running devo protocol rx's?
In my case, I fly my three 500's, and a 700 on the Devo 802Rx's, using a DEVO 8S, on Deviation in the Devo protocol.
I have two 8S devo's and an 8, that I want to use as my main flight Tx, and two backups. I do use fixedID on all the heli's. ( after a bad experience. )

Ok, i was able to download the latest nightly for both my devo12s and devo8s. I will be upgrading them tonight, but just want to be sure I'm clear on the steps to get them both to bind to my models without the need for rebinding when i switch tx.

I've noticed the hardware configure file that is included with the file system, do i need any special program to edit the text in this file when I input the txid#? Will text edit save the changes correctly with out modifying anything?

After inputing the same 8 digit txid# on both tx's, i will then need to rebind all my models to both tx's, or only one and have the same fixed id in both to bind with the other? Or will I need to do a full rebind (with plug) for both tx's before they are both recognized with fixed id?

And in future, if i get a new model/rx (dsm2/dsmx) I will only need to do the full bind process with one of the tx's, and just have the same fixed id set the same for it to bind with the other tx, correct?

Also, i do not have any protocol modules in my tx's, how do i (do i need to) disable the software from looking for the modules?

Is there anything else i might need to disable in the hardware configure file? I dont have the motor, and have not added any switches.

Im using a hp mini with windows 7.

It looks like i'll have to do it with "notepad".

Not:

;txid=

Ok, thankx


Look mom, i'm learning how to be a programer.....!

Ok, all smiles.

Updated both tx's to latest nightly (4.0.1-3e3acc2).

Transfered old models folders and added txid= (same 8digit code for both), Notepad saved it with no problems.

Re-binded rx and telemetry unit to the 8s first, set fixed ID.

Changed the fixed ID in the 12s to match the 8s and it binds.

Out of curiosity, i tried turning on the 8s while the 12s was bound, expecting to have two controlers fighting for control of the model, but the 8s did not bind. Tried it in reverse, 8s bind first then turn on 12s and 12s did not bind, leaving the tx that was bound first in full control. Overjoyed

Great Job phracturedblue!

You, and the team of guys here are truly amazing.

Now to go about rebinding all my models that have devo rx's.....

The 2801pro rx's are not effected by this change, correct?