- Posts: 402
About Fixed ID
- blackmoon
- Topic Author
- Offline
But does Fixed ID work with all the protocols ?.
Thank you
Please Log in or Create an account to join the conversation.
- cmpang
- Offline
- Posts: 296
To test if FixedID works,bind your receiver, then turn off your TX and on again, the receiver should be locked again..
cmPang
Please Log in or Create an account to join the conversation.
- linux-user
- Offline
- Posts: 271
The Hubsan4 protocol supports 4 channels, and only supports auto-binding. The fixed ID can be used, but does not prevent auto-binding during power-on.
But if fixed-ID is working as intended it has some advantage which apply for micros as well:
- you can't bind accidently the wrong model.
- usually it will bind even if you power the model before the TX
(what you should never do)
- the model could rebind after a power outage
- binding is faster
Disadvantage:
You can't use different TX with the same model with fixed-ID unless you use the latest deviation firmware with "txid override feature"
This works in over 9 of 10.cmpang wrote: To test if FixedID works,bind your receiver, then turn off your TX and on again, the receiver should be locked again..
cmPang
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Walkera chooses 3 channels at boot time by scanning the airwaves and looking for the least used channels. It does this every time you turn on your Tx (or at least it did last time I snooped on their transmissions). So every time you turn on the Tx, you potentially get different channels if the noise around you has changed.
Maybe Walkera has better algorithms than I that are more likely to result in the same answer, or maybe they changed their algorithm to be based on the TxId, but my analysis from 2 years ago did not indicate either of these things.
So Deviation's code works as intended and fixed-id DOES work by my definition. Using a channel selection based on txid would be trivial, but as long as Deviation doesn't reboot, I'm not sure why I'd weaken the channel selection. Unlike some other protocols, the Devo protocol does not use many channels in its hopping sequence, and so it will be more sensitive to noise. I'm not sure why I'd want to further weaken it.
Please Log in or Create an account to join the conversation.
- rbe2012
- Offline
- So much to do, so little time...
- Posts: 1433
I use a fixed ID for nearly all of my models (Devo, DSM2 and DSMX protocol) and it works in any case - don't actually know if other protocols support that.cmpang wrote: Since you raise it, Deviation's FixedID (Devo) doesn't work properly.. the only one works is Gale's version
You have to distinguish nicely between the tx fixed ID (TXID) which shall be different for all tx on the world (since a unique value in the CYRF chip is used to calculate it) -unless you use one of the last builds where you can override this with a manual given ID- and the model fixed ID which is used in combination with the TXID to enable recognizing transmitter and receiver.
Please Log in or Create an account to join the conversation.
- cmpang
- Offline
- Posts: 296
Or do it vice verse, turn off the receiver and on again, it should bind back to the Tx..
Try it... and Gale's version works all the time...
Please Log in or Create an account to join the conversation.
- cmpang
- Offline
- Posts: 296
1. add two 3 position switches to the 7e.. and that is done perfectly in version 4
2. low power on the cc2500 (Skyartec protocol) module.. Both Gale and SUV has fixed it..
3. Devo FixedID.. Gale has fixed it
Anyway, don't get me wrong, I really appreciate and big thanks to PB and those of you who have contributed all their hard work here, not a single doubt about it. And it is for this reason I really like to see Deviation goes even better..
cmPang
Please Log in or Create an account to join the conversation.
- blackmoon
- Topic Author
- Offline
- Posts: 402
Please Log in or Create an account to join the conversation.
- Hondawasaki
- Offline
- Posts: 49
.
I have done the same to my Blade nano DSMX( with different ID of course) and both models connect every time with out rebinding ...
.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Where is Galee's repo? As I've said, I don't consider this a bug. It is a design choice to give the best noise rejection. But if he found a solution that maintains the protocol robustness, I'll be happy to take it.cmpang wrote: 3. Devo FixedID.. Gale has fixed it
Please Log in or Create an account to join the conversation.
- Home
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- About Fixed ID