-
Notifications
You must be signed in to change notification settings - Fork 54
Connectivity
Andrey Voroshkov edited this page Oct 4, 2018
·
3 revisions
Chorus device uses UART interface to input/output data from/to external devices. Therefore you may use different UART converters to adapt Chorus signals to other interfaces.
- Bluetooth: HM-10 module -> built-in BT
- WiFi: DT-06 module -> built-in WiFi
- Bluetooth: HC-06 or HC-05 module -> built-in BT (or BT dongle?)
- WiFi: DT-06 module -> built-in WiFi
(for devices with OTG support):
- 3DR Telemetry (433/915 MHz): UART-Telemetry converter -> Telemetry-USB converter
- Wired (limited distance, got reports of reliable connectivity with 20 meters cable length): Ethernet UTP cat5 cable -> UART-USB converter (CP2101 or FT232RL)
- Wired reliable: UART-RS422 converter -> Ethernet UTP cat5 cable -> RS422-UART converter -> UART-USB converter (CP2101 or FT232RL)
- Bluetooth: HC-06 or HC-05 module -> built-in BT (or BT dongle?). Connect to virtual Bluetooth COM port.
- WiFi: DT-06 module -> built-in WiFi. Connect to IP:port set up in DT-06 settings.
- USB wireless: 3DR Telemetry (433/915 MHz): UART-Telemetry converter -> Telemetry-USB converter. Connect to virtual CP2101 COM port.
- USB Wired limited distance: (got reports of reliable connectivity with 20 meters cable length): UART -> Ethernet UTP cat5 cable -> UART-USB converter (CP2101 or FT232RL). Connect to virtual CP2101 COM port.
- USB Wired reliable: UART-RS422 converter -> Ethernet UTP cat5 cable -> RS422-UART converter -> UART-USB converter (CP2101 or FT232RL). Connect to virtual CP2101 COM port.
Note: the only publicly available and fully compatible PC software for interacting with Chorus at the moment is "LiveTime Scoring Engine". So far it only supports connection via virtual COM port. Of course you may use any other terminal software using COM port (e.g. "CoolTerm") or TCP/UDP (e.g."IO Ninja") connection to interact with Chorus, but it's more for testing purposes.