Network-dat/RC-dat/RC-dat.md
... ...
@@ -1,8 +1,15 @@
1 1
2 2
# RC-dat
3 3
4
-- [[RC-system-dat]]
4
+- [[RC-system-dat]] - [[ardupilot-dat]] - [[betaflight-dat]] - [[heli-configurator-dat]]
5
+
6
+- [[RC-protocols-dat]] - [[CRSF-dat]]
7
+
8
+- [[RC-TX-dat]] - [[ELRS-dat]]
9
+
10
+- [[flight-controller-dat]]
11
+
12
+- [[RC-code-dat]]
13
+
5 14
6
-- [[RC-protocols-dat]]
7 15
8
-- [[RC-TX-dat]] - [[ELRS-dat]]
... ...
\ No newline at end of file
Network-dat/RC-dat/RC-system-dat/ArduPilot-dat/2025-05-04-16-11-57.png
... ...
Binary files /dev/null and b/Network-dat/RC-dat/RC-system-dat/ArduPilot-dat/2025-05-04-16-11-57.png differ
Network-dat/RC-dat/RC-system-dat/ArduPilot-dat/ArduPilot-dat.md
... ...
@@ -0,0 +1,93 @@
1
+
2
+# ArduPilot-dat
3
+
4
+
5
+## Radio Control Systems
6
+
7
+
8
+- [Radio Control Systems](https://ardupilot.org/rover/docs/common-rc-systems.html)
9
+
10
+Compatible RC Protocols
11
+
12
+ArduPilot autopilots are compatible with the following receiver output protocols:
13
+
14
+PPM-Sum receivers - [[PPM-dat]]
15
+
16
+SBus receivers - [[SBUS-dat]]
17
+
18
+Fast SBus (from DJI HDL video/RC systems)
19
+
20
+i-BUS receivers - [[IBUS-dat]]
21
+
22
+FPort Receivers
23
+
24
+Spektrum SRXL2,DSM, DSM2, and DSM-X Satellite receivers
25
+
26
+Multiplex SRXL version 1 and version 2 receivers
27
+
28
+CRSF receivers (including ExpressLRS systems) - [[ELRS-dat]] - [[CRSF-dat]]
29
+
30
+mLRS (with telemetry) (MAVLink)
31
+
32
+Graupner SUM-D
33
+
34
+IRC Ghost
35
+
36
+DroneCAN peripherals can decode these RC protocols on a peripheral and pass to the autopilot
37
+
38
+MAVLink connected RC (not to be confused with MAVLink RC Overrides used for CS joystick control of RC functions)
39
+
40
+Parallel PWM outputs encoded to PPM-Sum using an external encoder (see below, not supported on many autopilots now)
41
+
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-dat]] | Long | Bi-dir | Variable | yes | SBUS/CRSF | 3 |
57
+| DragonLink | Long | Bi-dir | 56K | via MTP/LUA | PPM_SUM/SBUS | 1 |
58
+| [[ELRS-dat]] | 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
+- [[network-dat]]
64
+
65
+RC protocols - [[SBUS-dat]] - [[CRSF-dat]] - [[PPM-SUM-dat]] - [[Fport-dat]] - [[SUM-D-dat]] - [[IBUS-dat]] - [[DSM-dat]]
66
+
67
+
68
+
69
+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.
70
+
71
+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.
72
+
73
+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
74
+
75
+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.
76
+
77
+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.
78
+
79
+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.
80
+
81
+Note 7: The receiver must support i-BUS telemetry (look for a SENS port on the receiver or check the product specifications).
82
+
83
+Note 8: These systems have integrated HD video transmission from Ethernet or HDMI camera systems in addition to RC control and vehicle telemetry.
84
+
85
+
86
+## protocol converter
87
+
88
+![](2025-05-04-16-11-57.png)
89
+
90
+
91
+## ref
92
+
93
+- [[ardupilot-dat]] - [[FPV]]
... ...
\ No newline at end of file
app-dat/RC-apps-dat/ArduPilot-dat/2025-05-04-16-11-57.png
... ...
Binary files a/app-dat/RC-apps-dat/ArduPilot-dat/2025-05-04-16-11-57.png and /dev/null differ
app-dat/RC-apps-dat/ArduPilot-dat/ArduPilot-dat.md
... ...
@@ -1,93 +0,0 @@
1
-
2
-# ArduPilot-dat
3
-
4
-
5
-## Radio Control Systems
6
-
7
-
8
-- [Radio Control Systems](https://ardupilot.org/rover/docs/common-rc-systems.html)
9
-
10
-Compatible RC Protocols
11
-
12
-ArduPilot autopilots are compatible with the following receiver output protocols:
13
-
14
-PPM-Sum receivers - [[PPM-dat]]
15
-
16
-SBus receivers - [[SBUS-dat]]
17
-
18
-Fast SBus (from DJI HDL video/RC systems)
19
-
20
-i-BUS receivers - [[IBUS-dat]]
21
-
22
-FPort Receivers
23
-
24
-Spektrum SRXL2,DSM, DSM2, and DSM-X Satellite receivers
25
-
26
-Multiplex SRXL version 1 and version 2 receivers
27
-
28
-CRSF receivers (including ExpressLRS systems) - [[ELRS-dat]] - [[CRSF-dat]]
29
-
30
-mLRS (with telemetry) (MAVLink)
31
-
32
-Graupner SUM-D
33
-
34
-IRC Ghost
35
-
36
-DroneCAN peripherals can decode these RC protocols on a peripheral and pass to the autopilot
37
-
38
-MAVLink connected RC (not to be confused with MAVLink RC Overrides used for CS joystick control of RC functions)
39
-
40
-Parallel PWM outputs encoded to PPM-Sum using an external encoder (see below, not supported on many autopilots now)
41
-
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-dat]] | Long | Bi-dir | Variable | yes | SBUS/CRSF | 3 |
57
-| DragonLink | Long | Bi-dir | 56K | via MTP/LUA | PPM_SUM/SBUS | 1 |
58
-| [[ELRS-dat]] | 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
-- [[network-dat]]
64
-
65
-RC protocols - [[SBUS-dat]] - [[CRSF-dat]] - [[PPM-SUM-dat]] - [[Fport-dat]] - [[SUM-D-dat]] - [[IBUS-dat]] - [[DSM-dat]]
66
-
67
-
68
-
69
-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.
70
-
71
-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.
72
-
73
-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
74
-
75
-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.
76
-
77
-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.
78
-
79
-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.
80
-
81
-Note 7: The receiver must support i-BUS telemetry (look for a SENS port on the receiver or check the product specifications).
82
-
83
-Note 8: These systems have integrated HD video transmission from Ethernet or HDMI camera systems in addition to RC control and vehicle telemetry.
84
-
85
-
86
-## protocol converter
87
-
88
-![](2025-05-04-16-11-57.png)
89
-
90
-
91
-## ref
92
-
93
-- [[ardupilot-dat]] - [[FPV]]
... ...
\ No newline at end of file
app-dat/RC-apps-dat/RC-Controller-dat/2025-05-23-16-14-35.png
... ...
Binary files /dev/null and b/app-dat/RC-apps-dat/RC-Controller-dat/2025-05-23-16-14-35.png differ
app-dat/RC-apps-dat/RC-Controller-dat/RC-controller-dat.md
... ...
@@ -107,4 +107,61 @@ Go to **Rates Tab**:
107 107
- Lower **P/D** = softer movements.
108 108
- Raise **I** = stable hover.
109 109
- Reduce **Rates** + add **Expo** = slower stick response.
110
-- Throttle Expo = smoother lift / descend.
... ...
\ No newline at end of file
0
+- Throttle Expo = smoother lift / descend.
1
+
2
+
3
+
4
+
5
+
6
+# RC-console-dat
7
+
8
+- [[Wfly-dat]] - [[WFT06x-dat]] - [[WFR06S-dat]]
9
+
10
+
11
+- [[radiomaster-dat]]
12
+
13
+
14
+
15
+## RC Tx
16
+
17
+- [[PX4-dat]]
18
+
19
+![](2025-05-23-16-14-35.png)
20
+
21
+
22
+
23
+## RC Receiver
24
+
25
+When you push the **RC console (joystick or stick) up and down**, you're typically controlling the throttle or elevator channel, depending on the mode of your transmitter. The PWM (Pulse Width Modulation) signal output sent to the receiver or flight controller varies accordingly:
26
+
27
+PWM signal range: ~1000 µs (microseconds) to ~2000 µs
28
+
29
+ Center/stick neutral: ~1500 µs
30
+
31
+ Stick fully down: ~1000 µs
32
+
33
+ Stick fully up: ~2000 µs
34
+
35
+Example:
36
+
37
+If you're using Mode 2 (common mode):
38
+
39
+Left stick up/down = Throttle
40
+
41
+ Stick down = 1000 µs (zero throttle)
42
+
43
+ Stick up = 2000 µs (full throttle)
44
+
45
+If it's controlling elevator (pitch):
46
+
47
+ Stick down (nose down) = 1000 µs
48
+
49
+ Stick up (nose up) = 2000 µs
50
+
51
+
52
+
53
+## ref
54
+
55
+- https://docs.px4.io/v1.11/en/getting_started/rc_transmitter_receiver.html
56
+
57
+- [[RC-dat]]
... ...
\ No newline at end of file
app-dat/RC-apps-dat/RC-console-dat/2025-05-23-16-14-35.png
... ...
Binary files a/app-dat/RC-apps-dat/RC-console-dat/2025-05-23-16-14-35.png and /dev/null differ
app-dat/RC-apps-dat/RC-console-dat/RC-console-dat.md
... ...
@@ -1,53 +0,0 @@
1
-
2
-# RC-console-dat
3
-
4
-- [[Wfly-dat]] - [[WFT06x-dat]] - [[WFR06S-dat]]
5
-
6
-
7
-- [[radiomaster-dat]]
8
-
9
-
10
-
11
-## RC Tx
12
-
13
-- [[PX4-dat]]
14
-
15
-![](2025-05-23-16-14-35.png)
16
-
17
-
18
-
19
-## RC Receiver
20
-
21
-When you push the **RC console (joystick or stick) up and down**, you're typically controlling the throttle or elevator channel, depending on the mode of your transmitter. The PWM (Pulse Width Modulation) signal output sent to the receiver or flight controller varies accordingly:
22
-
23
-PWM signal range: ~1000 µs (microseconds) to ~2000 µs
24
-
25
- Center/stick neutral: ~1500 µs
26
-
27
- Stick fully down: ~1000 µs
28
-
29
- Stick fully up: ~2000 µs
30
-
31
-Example:
32
-
33
-If you're using Mode 2 (common mode):
34
-
35
-Left stick up/down = Throttle
36
-
37
- Stick down = 1000 µs (zero throttle)
38
-
39
- Stick up = 2000 µs (full throttle)
40
-
41
-If it's controlling elevator (pitch):
42
-
43
- Stick down (nose down) = 1000 µs
44
-
45
- Stick up (nose up) = 2000 µs
46
-
47
-
48
-
49
-## ref
50
-
51
-- https://docs.px4.io/v1.11/en/getting_started/rc_transmitter_receiver.html
52
-
53
-- [[RC-dat]]
... ...
\ No newline at end of file
app-dat/RC-apps-dat/RC-supplier-dat/caddxFPV-dat/2025-09-21-13-34-00.png
... ...
Binary files /dev/null and b/app-dat/RC-apps-dat/RC-supplier-dat/caddxFPV-dat/2025-09-21-13-34-00.png differ
app-dat/RC-apps-dat/RC-supplier-dat/caddxFPV-dat/caddxFPV-dat.md
... ...
@@ -110,6 +110,8 @@ Caddx蜗牛平头哥二代穿越机摄像头fpv摄像机夜视镜头无人机rat
110 110
111 111
### ratel pro
112 112
113
+- [[X12-dat]]
114
+
113 115
![](2025-09-16-18-55-15.png)
114 116
115 117
![](2025-09-16-18-55-45.png)
... ...
@@ -122,7 +124,9 @@ body dimesnion ~20mm
122 124
123 125
![](2025-09-18-21-02-28.png)
124 126
127
+wiring
125 128
129
+![](2025-09-21-13-34-00.png)
126 130
127 131
## goggles
128 132