Tech-dat/tech-dat.md
... ...
@@ -33,7 +33,9 @@
33 33
34 34
### MCU / CTRL / Processing
35 35
36
-- [[mcu-dat]] - [[SBC-dat]] - [[RPI-dat]] (raspberry pi)
36
+- [[mcu-dat]]
37
+
38
+- [[SBC-dat]] - [[RPI-dat]] (raspberry pi)
37 39
38 40
- [[CPLD-dat]] - [[FPGA-dat]]
39 41
... ...
@@ -42,7 +44,7 @@
42 44
43 45
- [[network-dat]] - [[M2M-dat]]
44 46
45
-- [[RF-DAT]]
47
+- [[RF-DAT]] - [[ELRS-dat]]
46 48
47 49
- [[LTE-dat]] - [[POE-dat]] - [[low-power-test-dat]] - [[M2M-interface]]
48 50
app-dat/RC-dat/RC-dat.md
... ...
@@ -1,2 +1,6 @@
1 1
2
-# RC-dat
... ...
\ No newline at end of file
0
+# RC-dat
1
+
2
+- [[RC-car-dat]] - [[RC-car-hack-dat]] - [[video-rc-car-dat]]
3
+
4
+- [[BMS-dat]]
... ...
\ No newline at end of file
app-dat/RC-dat/rover-dat/rover-dat.md
... ...
@@ -0,0 +1,13 @@
1
+
2
+# rover-dat
3
+
4
+- [[ardupilot-dat]]
5
+
6
+https://ardupilot.org/rover/index.html
7
+
8
+- [[RC-car-dat]] - [[rover-dat]] - [[RC-car-hack-dat]]
9
+
10
+- ARKV6X Flight Controller Overview
11
+- ARK FPV Flight Controller Overview == STM32H743IIK6 MCU
12
+- CUAV V5 Plus Overview == STM32F765
13
+
app-dat/app-dat.md
... ...
@@ -22,13 +22,19 @@
22 22
- [[home-plant-dat]] - [[Apocalypse-dat]] - [[surveillance-dat]]
23 23
24 24
25
-## Electrified in the air
25
+## RC Electrified in the air
26
+
27
+- [[ardupilot-dat]]
26 28
27 29
- [[quadcopter-dat]] - [[FPV-dat]] - [[UAV-dat]]
28 30
29
-- [[parachute-dat]] - [[rocket-dat]]
31
+- [[parachute-dat]] - [[rocket-dat]] - [[blimp-dat]]
32
+
33
+## RC lectrified on the ground
34
+
35
+- [[ardupilot-dat]]
30 36
31
-## Electrified on the ground
37
+- [[RC-car-dat]] - [[rover-dat]] - [[RC-car-hack-dat]] - [[submarine-dat]] - [[RC-boat-dat]]
32 38
33 39
- [[robot-dat]] - [[video-RC-car-dat]]
34 40
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/2025-05-04-16-11-57.png
... ...
Binary files /dev/null and b/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/2025-05-04-16-11-57.png differ
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/ArduPilot-dat.md
... ...
@@ -0,0 +1,50 @@
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
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
+## protocol converter
44
+
45
+![](2025-05-04-16-11-57.png)
46
+
47
+
48
+## ref
49
+
50
+- [[ardupilot-dat]] - [[FPV]]
... ...
\ No newline at end of file
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/CRSF-dat/CRSF-dat.md
... ...
@@ -0,0 +1,74 @@
1
+
2
+# CRSF-dat
3
+
4
+CRSF (Crossfire Serial Protocol) is a low-latency, high-speed serial protocol developed by **Team BlackSheep (TBS)** for communication between radio receivers (like TBS Crossfire Nano RX) and flight controllers.
5
+
6
+It’s used in RC applications (especially FPV drones) to transmit RC channel data, telemetry, and link status over a compact serial format.
7
+
8
+CRSF packets are binary data. Here's the basic structure of a CRSF packet:
9
+
10
+## CRSF Packet Structure (General)
11
+
12
+| Byte Index | Name | Description |
13
+|------------|----------------|---------------------------------------------|
14
+| 0 | Device Address | Who is sending (e.g., RX, TX) |
15
+| 1 | Frame Length | Length of payload + 1 (type byte + data) |
16
+| 2 | Frame Type | Type of data (e.g., RC channels, telemetry) |
17
+| 3 - N | Payload | Actual data, varies by Frame Type |
18
+| Last Byte | CRC | Checksum for packet validation |
19
+
20
+
21
+This is how a typical RC channel data packet might look (in hex):
22
+
23
+C8 18 16 A1 84 3F C1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9E
24
+
25
+## RC Channel Encoding (Packed 11-bit)
26
+
27
+Each RC channel is packed as 11-bit little-endian integers, with up to 16 channels per frame. Example values:
28
+
29
+- 1000 → channel center
30
+- 172 → min
31
+- 1811 → max
32
+
33
+## read data via serial
34
+
35
+Yes, you can use a serial port to read CRSF data, because CRSF is a serial protocol — specifically, a half-duplex, asynchronous UART protocol using 8N1 (8 data bits, no parity, 1 stop bit).
36
+
37
+### 📡 CRSF over Serial – Quick Guide
38
+
39
+- **Baud rate**: 420000 or 115200 (depends on TX/RX version or setting)
40
+- **Protocol**: UART (8N1)
41
+- **Signal direction**: Half-duplex (same wire for TX and RX)
42
+- **Voltage**: 3.3V (NOT 5V safe on most Crossfire receivers)
43
+- **Typical usage**: Read CRSF data from TBS Nano RX or TX
44
+
45
+#### 🧰 What You Need:
46
+- A microcontroller or board with UART support (e.g., Arduino, ESP32, STM32, Raspberry Pi)
47
+- Logic-level conversion (if needed for 3.3V safety)
48
+- CRSF-compatible device (e.g., TBS Crossfire Nano RX)
49
+
50
+Code Concept (Pseudocode)
51
+
52
+
53
+ Serial.begin(420000); // Or 115200 for some TX modules
54
+
55
+ void loop() {
56
+ if (Serial.available()) {
57
+ uint8_t byte = Serial.read();
58
+ // Process CRSF packet bytes here
59
+ }
60
+ }
61
+
62
+
63
+
64
+## via ardupilot
65
+
66
+If you wish to use telemetry then a receiver can be connected to a UART utilizing the CRSF protocol.
67
+
68
+CRSF is a full-duplex protocol that supports integrated telemetry and a number of other features. Connect the RX pin of the UART to the CRSF TX pin of the CRSF device and vice versa. Currently a full-duplex UART connection is required. For best performance a UART with DMA capability on its RX port is desirable, but not required. A message will be displayed once on the GCS console, if connected to a UART without this capability on an F4/F7 based autopilot.
69
+
70
+https://ardupilot.org/rover/docs/common-tbs-rc.html#common-tbs-rc
71
+
72
+## ref
73
+
74
+- [[FPV-dat]]
... ...
\ No newline at end of file
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-29-54.png
... ...
Binary files /dev/null and b/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-29-54.png differ
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-31-56.png
... ...
Binary files /dev/null and b/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-31-56.png differ
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/ELRS-RX-dat.md
... ...
@@ -34,4 +34,10 @@ The password is "expresslrs", and then you can access 10.0.0.1 to upload the rec
34 34
- Equipped with a power amplifier (PA+LNA), providing 100mW telemetry output and better response speed;
35 35
- Theoretically compatible with most ELRS 2.4G transmitter modules on the market (requires firmware version 2.0 or above).
36 36
37
-![](2025-04-25-16-55-05.png)
... ...
\ No newline at end of file
0
+![](2025-04-25-16-55-05.png)
1
+
2
+
3
+
4
+## ref
5
+
6
+- [[ELRS-dat]]
... ...
\ No newline at end of file
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-dat.md
... ...
@@ -11,9 +11,13 @@ ELRS-remote-console-tx
11 11
- BETAFPV literadio 3
12 12
- BETAFPV literadio 2
13 13
14
-- [[edge-tx-dat]] - [[radiomaster-dat]]
14
+- [[edge-tx-dat]] - [[radiomaster-dat]] - [[lightradio-dat]]
15 15
16
-- [[ELRS-RX-dat]] - [[CRSF-dat]] - [[SX1276-dat]] - [[ESP8285-dat]] - [[ESP32-dat]] - [[SX1281-dat]] - [[SX1208-dat]]
16
+- [[ELRS-RX-dat]] - [[SX1276-dat]] - [[ESP8285-dat]] - [[ESP32-dat]] - [[SX1281-dat]] - [[SX1208-dat]]
17
+
18
+protocol output - - [[CRSF-dat]]
19
+
20
+- [[CC2500-dat]]
17 21
18 22
- [[ELRS-915M-dat]] - [[ELRS-CHS-PWM-dat]] - [[ELRS-2.4Ghz-dat]]
19 23
... ...
@@ -25,6 +29,8 @@ https://github.com/ExpressLRS/ExpressLRS
25 29
26 30
https://www.expresslrs.org/quick-start/getting-started/
27 31
32
+[ExpressLRS-Configurator-releases](https://github.com/ExpressLRS/ExpressLRS-Configurator/releases)
33
+
28 34
29 35
30 36
## **ExpressLRS (ELRS) 2.4GHz Standard Explained**
... ...
@@ -115,6 +121,19 @@ https://www.expresslrs.org/quick-start/getting-started/
115 121
- [[5.8Ghz-dat]]
116 122
117 123
124
+## WebUI
125
+
126
+### Via "ExpressLRS RX" Access Point
127
+
128
+![](2025-05-04-15-29-54.png)
129
+
130
+Load the Web UI on your browser using these addresses:
131
+
132
+http://10.0.0.1/ - If you have connected to the ExpressLRS RX Access Point
133
+
134
+### Via button press
135
+
136
+![](2025-05-04-15-31-56.png)
118 137
119 138
120 139
## ref
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/FrSky-dat/FrSky-dat.md
... ...
@@ -0,0 +1,4 @@
1
+
2
+# FrSky-dat
3
+
4
+- [[CC2500-dat]]
... ...
\ No newline at end of file
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/flight-controller-dat/flight-controller-dat.md
... ...
@@ -0,0 +1,3 @@
1
+
2
+# flight-controller-dat
3
+
app-dat/quadcopter-dat/FPV-dat/FPV-dat.md
... ...
@@ -5,8 +5,9 @@
5 5
6 6
- [[FPV-controller-dat]] - [[Goggles-dat]]
7 7
8
-- [[ELRS-dat]]
9
-
8
+- [[ELRS-dat]] - [[FrSky-dat]] - [[ArduPilot-dat]] - [[CRSF-dat]]
9
+
10
+- [[BMS-dat]]
10 11
11 12
12 13
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-14-49-45.png
... ...
Binary files /dev/null and b/app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-14-49-45.png differ
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-15-34-48.png
... ...
Binary files /dev/null and b/app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-15-34-48.png differ
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/betaFPV-dat.md
... ...
@@ -0,0 +1,4 @@
1
+
2
+# betaFPV-dat
3
+
4
+- [[lightradio-dat]]
... ...
\ No newline at end of file
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/lightradio-dat.md
... ...
@@ -0,0 +1,94 @@
1
+
2
+# lightradio-dat
3
+
4
+## Lightradio 3 Pro
5
+
6
+- professional version
7
+- build-in OLED display
8
+
9
+![](2025-05-04-15-34-48.png)
10
+
11
+Choice of two protocols:
12
+
13
+* **Built-in ELRS 2.4G:** Maximum output power up to 250mW, built-in omnidirectional antenna, enables long-range flight.
14
+* **Built-in CC2500 version:** Supports Frsky D / Frsky X / SFHSS and other protocols, maximum 100mW transmission power.
15
+
16
+
17
+
18
+## lightradio 3
19
+
20
+- does NOT support original [[ELRS-dat]] system
21
+
22
+### info
23
+
24
+![](2025-05-04-14-49-45.png)
25
+
26
+
27
+### Flight Controller
28
+
29
+The application supports flight controller that can run LiteSilver firmeware.
30
+
31
+- Lite Brushed FC V3
32
+- Cetus FPV Kit
33
+- Cetus Pro FPV Kit
34
+- Cetus X FPV KIT
35
+- Cetus Lite FPV Kit
36
+- Aquila 16 FPV kit
37
+
38
+Configurator for FC board is active.Follow the steps to enter FC Setup page.
39
+
40
+1. Connect the FC board to the computer via USB data cable.
41
+2. Select the virtual COM port and click the *Connect" button on the top right.
42
+
43
+Note: If enter FC Setup page fail, please update the FC firmware first.
44
+
45
+Click the "Firmware Flasher" tab on the left for firmware update.
46
+
47
+### Radio Transmitter
48
+
49
+Support the radio controller come with BETAFPV LiteRadio Firmware 2.0 Version.
50
+
51
+- LiteRadio 1
52
+- LiteRadio 2 SEV2
53
+- LiteRadio 3
54
+- LiteRadio 4 SE
55
+
56
+The LiteRadio 2 SE Frsky or Bayang version is not supported. LiteRadio 2 and LiteRadio 3 Pro is powered by OpenTX system, please use the OpenTX Companion.
57
+
58
+Click the yellow button below to active configurator for radio controller.
59
+
60
+### Remote control parameters
61
+
62
+- Model == LiteRadio3 remote control
63
+- Remote control distance == 500-600 meters
64
+- Frequency range == 2.4G (2403MHz-2447MHz)
65
+- Support protocol == ELRS 2.4G/Frsky (CC2500)
66
+- Channel == 8
67
+- Support protocol == ELRS 2.4G
68
+- Power == 25mW/50mW/100mW
69
+- Adaptive drone type supports
70
+ - Multi-rotor/support USB firmware update
71
+ - BETAFPV Configurator connection
72
+ - Custom LiteRadio system joystick calibration
73
+- LED light == red light on/red warning/blue normal
74
+- Battery built-in == 2000mAh1S battery
75
+- Charging connector == Type-C
76
+
77
+## BetaFPV Configurator
78
+
79
+[github release ](https://github.com/BETAFPV/BETAFPV_Configurator/releases)
80
+
81
+[BETAFPV Configurator User Manual](https://support.betafpv.com/hc/en-us/articles/40712112687769-BETAFPV-Configurator-User-Manual)
82
+
83
+[github BETAFPV_Configurator](https://github.com/BETAFPV/BETAFPV_Configurator)
84
+
85
+
86
+### Connection
87
+
88
+- via serial port (USB)
89
+
90
+
91
+
92
+## ref
93
+
94
+- [[betaFPV]] - [[FPV]]
... ...
\ No newline at end of file
weekly-dat/2025-May-dat/2025-May-dat.md
... ...
@@ -0,0 +1,20 @@
1
+
2
+# 2025-May-dat
3
+
4
+This a weekly update newsletter, to briefly tell you whats new and whats fun we are working at, hope you like
5
+
6
+## New Boards
7
+
8
+
9
+
10
+## Development, Documents Updates
11
+
12
+- greate project [[ardupilot-dat]], going to build a [[rover-dat]]
13
+
14
+## Dissusion, Feedback, To-do
15
+
16
+
17
+
18
+## Interesting Readings, News
19
+
20
+