Downlink
The Downlink socket found on every single DUELink module is used to connect to the next Uplink socket on the next module. The DUELink software magically handles the data going across the entire Daisylink chain of connected modules.
There will be no signal degradation along the wires as data is repeated on every Downlink socket. In cases power is dropping after several modules, a Power Inject module can be used.
This is not necessary in most modules as they are very low power. However, some modules, like large displays and motor drivers, do require a decent amount of power.
Modes
The Downlink socket has multiple modes of operations to give the user more control.
| Mode | Description |
|---|---|
| 0 | Null |
| 1 | Interface (Default) |
| 2 | Host |
| 3 | UART gateway |
The default Interface mode allows the DUELink engine to handle the Daisylink chain of modules automatically. The Host mode is used when a module is used as a host (bus controller), that sends commands Downlink using the Cmd() Standard Library function. It is also useful when there is a desire to stop the engine from sending anything Downlink.
In rare cases, like with Wireless Hook, the UART mode allows the system to bridge and pipe the data from the UART interface (Bluetooth in this case) to the Downlink port.
To initiate the Daisylink and enumerate the modules, a command must be sent. This very first command is only seen by the first device. An empty command (just a carriage return) can also be used.