mirror of
https://github.com/pascallanger/DIY-Multiprotocol-TX-Module.git
synced 2025-07-03 03:57:51 +00:00
Note that the Hubsan has a hardcoded id. Also note that DEVO and DSM* use the id of the radio module.
This commit is contained in:
parent
d90e698a15
commit
569aadf16d
@ -43,6 +43,7 @@ CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8|CH9
|
||||
---|---|---|---|---|---|---|---|---
|
||||
A|E|T|R|FLIP|LIGHT|PICTURE|VIDEO|HEADLESS
|
||||
|
||||
Only one model can be flown at the same time since the ID is hardcoded.
|
||||
***
|
||||
#CC2500 RF Module
|
||||
|
||||
|
@ -92,8 +92,7 @@ Once the TX is telemetry enabled, it just needs to be configured on the model (s
|
||||
##Protocols
|
||||
|
||||
###TX ID
|
||||
The multiprotocol TX module is using a 32bits ID generated randomly at first power up. This global ID is used by all protocols.
|
||||
There are little chances to get a duplicated ID.
|
||||
The multiprotocol TX module is using a 32bits ID generated randomly at first power up. This global ID is used by all protocolsexcept for the CYRF6963 (Devo, DSM2 and DSMX) protocols, which use the unique id of the CYRF6936 module. There are little chances to get a duplicated ID.
|
||||
|
||||
It's possible to generate a new ID using bind button on the Hubsan protocol during power up.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user