Board-dat/AMP/AMP1003-dat/AMP1003-dat.md
... ...
@@ -18,6 +18,7 @@ bottom
18 18
19 19
![](2023-09-28-16-26-44.png)
20 20
21
+- [[TPA3116-dat]]
21 22
22 23
## ref
23 24
Chip-dat/TI-dat/TI-audio-dat/TPA3116-dat/TPA3116-dat.md
... ...
@@ -9,4 +9,9 @@ https://www.electrodragon.com/product/210w-dual-channel-hifi-mini-audio-amplifie
9 9
10 10
## SCH
11 11
12
-![](2023-11-09-16-33-55.png)
... ...
\ No newline at end of file
0
+![](2023-11-09-16-33-55.png)
1
+
2
+
3
+## ref
4
+
5
+- [[ti-audio-dat]]
... ...
\ No newline at end of file
Tech-dat/Network-dat/network-dat.md
... ...
@@ -1,4 +1,18 @@
1 1
2 2
# network-dat.md
3 3
4
-- [[nfid-dat]] - [[NBIOT-dat]]
... ...
\ No newline at end of file
0
+- [[nfid-dat]] - [[NBIOT-dat]]
1
+
2
+
3
+## RC apps protocols
4
+
5
+- [[RF-DAT]] - [[ELRS-dat]] - [[CRSF-dat]] - [[GFSK-dat]] - [[ardupilot-dat]] - [[SBUS-dat]]
6
+
7
+- [[IBUS-dat]] - [[PPM-dat]] - [[FPort-dat]] - [[SPEKTRUM-dat]] - [[SUMD-dat]] - [[SRXL-dat]] - [[Ghost-dat]]
8
+
9
+- [[MAVLink-dat]] - [[DroneCAN-dat]]
10
+
11
+
12
+
13
+
14
+
Tech-dat/tech-dat.md
... ...
@@ -44,7 +44,7 @@
44 44
45 45
- [[network-dat]] - [[M2M-dat]]
46 46
47
-- [[RF-DAT]] - [[ELRS-dat]]
47
+- [[RF-DAT]] - [[ELRS-dat]] - [[CRSF-dat]] - [[GFSK-dat]] - [[ardupilot-dat]] - [[SBUS-dat]]
48 48
49 49
- [[LTE-dat]] - [[POE-dat]] - [[low-power-test-dat]] - [[M2M-interface]]
50 50
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/ArduPilot-dat.md
... ...
@@ -17,7 +17,7 @@ SBus receivers - [[SBUS-dat]]
17 17
18 18
Fast SBus (from DJI HDL video/RC systems)
19 19
20
-i-BUS receivers
20
+i-BUS receivers - [[IBUS-dat]]
21 21
22 22
FPort Receivers
23 23
... ...
@@ -40,6 +40,43 @@ MAVLink connected RC (not to be confused with MAVLink RC Overrides used for CS j
40 40
Parallel PWM outputs encoded to PPM-Sum using an external encoder (see below, not supported on many autopilots now)
41 41
42 42
43
+
44
+## specs
45
+
46
+| Original Manu | Range | Telemetry | Telem Speed | TX Display | RC Protocol | Notes |
47
+| --------------- | ------ | --------------- | ----------- | ----------- | -------------------- | ----- |
48
+| Flysky | Short | Yes | | yes | i-BUS/SBUS | 7 |
49
+| FrSky X series | Short | Bi-dir | Medium | yes | PPM-SUM/SBUS/ FPort | 2 |
50
+| Futaba | Short | No | | | SBus | |
51
+| Graupner | Short | Yes | Medium | yes | SUM-D | |
52
+| Multiplex | Short | No | | | SRXL | |
53
+| Spektrum | Short | Vendor Specific | | yes | DSM/DSM2 DSM-X/ SRXL | |
54
+| FrSky R9 series | Medium | Bi-dir | Medium | yes | PPM-SUM/SBUS/ FPort | 2 |
55
+| IRC Ghost | Medium | Vendor Specific | | yes | IRC Ghost | |
56
+| CRSF | Long | Bi-dir | Variable | yes | SBUS/CRSF | 3 |
57
+| DragonLink | Long | Bi-dir | 56K | via MTP/LUA | PPM_SUM/SBUS | 1 |
58
+| ELRS | Long | Bi-Dir | Variable | optional | SBUS/CRSF Mavlink | 4 |
59
+| HereLink | Long | Bi-dir | 56K | integrated | SBUS | 8 |
60
+| mLRS | Long | Bi-dir | 12K - 91K | via LUA | SBUS/CRSF | 5 |
61
+| SIYI | Long | Bi-dir | 56K | integrated | SBUS | 8 |
62
+
63
+Note 1: DragonLink provides a 56Kbaud transparent link for telemetry, allowing full MAVLink telemetry to/from the vehicle from the transmitter module. Dragonlink is an add-on module to the transmitter, such as an FRSky Taranis or RadioMaster T16. See DragonLink RC Systems. MTP (Mavlink to Passthru) converters are available to allow direct display of MAVLink Telemetry data on OpenTX transmitters using Yaapu Telemetry LUA Script.
64
+
65
+Note 2: See Yaapu FrSky Telemetry Script for OpenTX. The ability to change parameters over FRSky telemetry from an Open TX compatible transmitter in addition to displaying the telemetry data is possible. Most FRSky compatible transmitters use OpenTX. Note that R9 systems are not quite Long Range, but much further range than normal FRSky systems, themselves at the very high end of the Short Range category at 1.6-2km range.
66
+
67
+Note 3: ArduPilot provides a means to send its telemetry data via CRSF such that it can be displayed on OpenTX transmitters using the Yaapu Telemetry LUA Script. The ability to change parameters over CRSF telemetry from an Open TX compatible transmitter in addition to displaying the telemetry data is also possible. See TBS Crossfire Telemetry
68
+
69
+Note 4: ELRS (ExpressLRS) is a flexible open-source system that can output CRSF, SBUS, or MAVLink (with embedded RC) protocols. Telemetry requires the use of CRSF or Mavlink, and the receiver must be wired to a full UART. See ExpressLRS site <https://www.expresslrs.org/> and TBS CRSF/ ELRS for more information.
70
+
71
+Note 5: The mLRS project is firmware designed specifically to carry both RC and MAVLink. The usable telemetry speed varies by the chosen mode and is managed via RADIO_STATUS flow control. It uses the CRSF (TBS Crossfire) RC protocol on both the receiver and Tx module. It also integrates full MAVLink telemetry via serial connections on the Tx module and the receiver.
72
+
73
+Note 6: Vendor Specific Telem means that they accomodate sensor additions to the vehicle and can display the information on certain Vendor specific TXs but do not send ArduPilot telemetry from the vehicle to ArduPilot compatible GCS or OpenTX display scripts.
74
+
75
+Note 7: The receiver must support i-BUS telemetry (look for a SENS port on the receiver or check the product specifications).
76
+
77
+Note 8: These systems have integrated HD video transmission from Ethernet or HDMI camera systems in addition to RC control and vehicle telemetry.
78
+
79
+
43 80
## protocol converter
44 81
45 82
![](2025-05-04-16-11-57.png)
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/SBUS-dat/SBUS-dat.md
... ...
@@ -0,0 +1,75 @@
1
+
2
+# SBUS-dat
3
+
4
+- [[futaba-dat]]
5
+
6
+## 📡 What is SBUS? — Simple Explanation
7
+
8
+**SBUS (Serial Bus)** is a digital protocol used in RC systems to send multiple control signals (channels) over a single wire.
9
+
10
+---
11
+
12
+### 🧩 Key Features
13
+
14
+- 🔢 **Up to 16 channels** in one signal
15
+- 💬 **Digital serial protocol**
16
+- 📦 Sends data in **serial frames**
17
+- ⏱️ **100,000 baud**, **inverted UART**
18
+- ↪️ Invented by **Futaba**, widely used (FrSky, Radiolink, etc.)
19
+- 🧠 Needs **inversion** to be read by normal UART (hardware or software)
20
+
21
+---
22
+
23
+### 🧱 Simple Analogy
24
+
25
+> SBUS is like 16 people taking turns speaking very fast on one microphone.
26
+> Each frame contains all channel values packed tightly together.
27
+
28
+---
29
+
30
+### 🧪 Data Frame Structure
31
+
32
+Each SBUS frame is 25 bytes:
33
+
34
+| 1 byte | 22 bytes | 1 byte | 1 byte |
35
+| ------ | ----------- | ------ | ------ |
36
+| Header | 16 channels | Flags | End |
37
+
38
+
39
+
40
+- **Header**: 0x0F
41
+- **End**: 0x00
42
+- Sent **every ~9ms** (111Hz refresh rate)
43
+
44
+---
45
+
46
+### 🔌 Common Use Cases
47
+
48
+- RC Receiver → Flight Controller (e.g., FrSky RX to Betaflight FC)
49
+- RC Receiver → Microcontroller (Arduino, ESP32)
50
+- RC → Servo controller boards (if SBUS supported)
51
+
52
+---
53
+
54
+### ⚖️ SBUS vs PWM vs PPM
55
+
56
+| Feature | SBUS | PWM | PPM |
57
+|---------------|-------------|---------------|---------------|
58
+| Channels | 16 | 1 per wire | 8 (typically) |
59
+| Wires needed | 1 | 1 per channel | 1 |
60
+| Type | Digital | Analog pulse | Analog pulse |
61
+| Speed | Very fast | Slow | Medium |
62
+| Latency | Very low | High | Medium |
63
+
64
+---
65
+
66
+### 🧰 Tip for Developers
67
+
68
+To read SBUS using a microcontroller:
69
+- Use **UART** at **100000 baud**, **8E2**, **inverted signal**
70
+- Some MCUs (like ESP32) support inversion natively
71
+- Otherwise, use an **inverter circuit** or a software decoder
72
+
73
+## ref
74
+
75
+- [[network-dat]]