rc data

-- [[PWM-dat]]

-## RC - protocols

-- [[RC-protocols-dat]]

-

-# CRSF-dat

-

-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.

-

-It’s used in RC applications (especially FPV drones) to transmit RC channel data, telemetry, and link status over a compact serial format.

-

-CRSF packets are binary data. Here's the basic structure of a CRSF packet:

-

-## CRSF Packet Structure (General)

-

-| Byte Index | Name | Description |

-|------------|----------------|---------------------------------------------|

-| 0 | Device Address | Who is sending (e.g., RX, TX) |

-| 1 | Frame Length | Length of payload + 1 (type byte + data) |

-| 2 | Frame Type | Type of data (e.g., RC channels, telemetry) |

-| 3 - N | Payload | Actual data, varies by Frame Type |

-| Last Byte | CRC | Checksum for packet validation |

-

-

-This is how a typical RC channel data packet might look (in hex):

-

-C8 18 16 A1 84 3F C1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9E

-

-## RC Channel Encoding (Packed 11-bit)

-

-Each RC channel is packed as 11-bit little-endian integers, with up to 16 channels per frame. Example values:

-

-- 1000 → channel center

-- 172 → min

-- 1811 → max

-

-## read data via serial

-

-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).

-

-### 📡 CRSF over Serial – Quick Guide

-

-- **Baud rate**: 420000 or 115200 (depends on TX/RX version or setting)

-- **Protocol**: UART (8N1)

-- **Signal direction**: Half-duplex (same wire for TX and RX)

-- **Voltage**: 3.3V (NOT 5V safe on most Crossfire receivers)

-- **Typical usage**: Read CRSF data from TBS Nano RX or TX

-

-#### 🧰 What You Need:

-- A microcontroller or board with UART support (e.g., Arduino, ESP32, STM32, Raspberry Pi)

-- Logic-level conversion (if needed for 3.3V safety)

-- CRSF-compatible device (e.g., TBS Crossfire Nano RX)

-

-Code Concept (Pseudocode)

-

-

- Serial.begin(420000); // Or 115200 for some TX modules

-

- void loop() {

- if (Serial.available()) {

- uint8_t byte = Serial.read();

- // Process CRSF packet bytes here

- }

- }

-

-

-

-## via ardupilot

-

-If you wish to use telemetry then a receiver can be connected to a UART utilizing the CRSF protocol.

-

-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.

-

-https://ardupilot.org/rover/docs/common-tbs-rc.html#common-tbs-rc

-

-## ref

-

-- [[FPV-dat]]

-

-# ELRS-915M-dat.md

-

-

-

-# ELRS-CHS-PWM-dat.md

-

-

-

-# ELRS-RX-dat

-

-

-## T-anntena version

-

-

-

-## SMD antenna version

-

-## info

-

-Nano2400-RX receiver with power amplifier (PA+LNA).

-

-Therefore, it has 100mW telemetry output and better sensitivity at longer distances.

-

-It uses an IPEX1 antenna connector.

-

-Paired with an external dipole T-antenna (customized by a professional factory, each antenna is tested with professional instruments to ensure quality, lightness, and durability).

-

-The CYCLONE series receivers are based on the open-source architecture and program of ExpressLRS.

-

-We have released 3 types of RX receiver modules. All use the [[ESP8285-dat]] [[MCU-dat]]. You can upgrade the firmware via [[WIFI-dat]], which is very user-friendly.

-

-Typically, after powering the receiver and with the remote controller turned off, the ExpressLRS hotspot can be found after a default of 60 seconds. Connect to this hotspot using a computer or mobile phone.

-

-The password is "expresslrs", and then you can access 10.0.0.1 to upload the receiver firmware.

-

-## Product Features

-

-- High refresh rate 100mW telemetry output;

-- Supports convenient and fast firmware flashing via WIFI connection;

-- Firmware Version: 3.3.0 [BETAFPVLite2400RX]

-- Equipped with a power amplifier (PA+LNA), providing 100mW telemetry output and better response speed;

-- Theoretically compatible with most ELRS 2.4G transmitter modules on the market (requires firmware version 2.0 or above).

-

-

-

-

-

-## ref

-

-- [[ELRS-dat]]

-

-# ELRS-dat

-

-Info - [[ELRS-frequency-dat]] - [[ELRS-faq-dat]]

-

-

-## ELRS-link

-

-ELRS-remote-console-tx

-

-- BETAFPV literadio 3

-- BETAFPV literadio 2

-

-- [[edge-tx-dat]] - [[radiomaster-dat]] - [[lightradio-dat]]

-

-- [[ELRS-RX-dat]] - [[SX1276-dat]] - [[ESP8285-dat]] - [[ESP32-dat]] - [[SX1281-dat]] - [[SX1208-dat]]

-

-protocol output - - [[CRSF-dat]]

-

-- [[CC2500-dat]]

-

-- [[ELRS-915M-dat]] - [[ELRS-CHS-PWM-dat]] - [[ELRS-2.4Ghz-dat]]

-

-- [[ELRS]]

-

-## resources

-

-https://github.com/ExpressLRS/ExpressLRS

-

-https://www.expresslrs.org/quick-start/getting-started/

-

-[ExpressLRS-Configurator-releases](https://github.com/ExpressLRS/ExpressLRS-Configurator/releases)

-

-

-

-## **ExpressLRS (ELRS) 2.4GHz Standard Explained**

-

-**ExpressLRS (ELRS) 2.4GHz** is an open-source **long-range, low-latency radio control link** developed for FPV drones and RC applications. It offers **high performance, ultra-fast response times, and robust signal reliability** compared to traditional RC protocols like FrSky, Crossfire, and Ghost.

-

----

-

-### **🔹 Key Features of ELRS 2.4GHz**

-- **Ultra-Low Latency** (~5ms in high-speed mode).

-- **Long-Range Performance** (Up to **30km+** with proper setup).

-- **High Packet Rate (Up to 1000Hz)** for **smooth & responsive controls**.

-- **Open-Source & Customizable** (Community-driven development).

-- **Affordable Hardware** (Compared to Crossfire or Ghost).

-- **Wide Compatibility** (Supported on many **radio transmitters & receivers**).

-

----

-

-### **🔹 ELRS 2.4GHz vs. Other RC Links**

-| Feature | ELRS 2.4GHz | TBS Crossfire | Ghost 2.4GHz | FrSky R9M |

-| --------------- | ------------ | ------------- | ------------ | ----------- |

-| **Frequency** | 2.4GHz | 900MHz | 2.4GHz | 900MHz |

-| **Max Range** | ~30km+ | ~50km+ | ~15km | ~10-20km |

-| **Latency** | 5-7ms | 15-50ms | ~4ms | ~20ms |

-| **Packet Rate** | Up to 1000Hz | 50-150Hz | 500Hz | ~100Hz |

-| **Open Source** | ✅ Yes | ❌ No | ❌ No | ❌ No |

-| **Cost** | 💰 Affordable | 💰💰 Expensive | 💰💰 Expensive | 💰 Mid-Range |

-

----

-

-### **🔹 ELRS 2.4GHz Modes & Performance**

-| Mode | Packet Rate | Latency | Range |

-| --------- | ----------- | ------- | --------------------- |

-| **500Hz** | 500Hz | ~5ms | Short (~3km) |

-| **250Hz** | 250Hz | ~7ms | Mid (~10km) |

-| **150Hz** | 150Hz | ~10ms | Long (~20km) |

-| **50Hz** | 50Hz | ~20ms | Extreme Long (~30km+) |

-

-🔹 **Higher packet rate = Lower latency, but reduced range**

-🔹 **Lower packet rate = Higher range, but increased latency**

-

----

-

-### **🔹 Recommended ExpressLRS 2.4GHz Hardware**

-#### **🛠️ Transmitters (TX)**

-- **RadioMaster Zorro ELRS 2.4GHz**

-- **Jumper T20S (Built-in ELRS)**

-- **Happymodel ES24TX Pro (External ELRS Module)**

-- **BetaFPV ELRS Micro TX Module**

-

-#### **📡 Receivers (RX)**

-- **Happymodel EP2 (Tiny, best for micro quads)**

-- **BetaFPV ELRS 2.4GHz Nano RX**

-- **Radiomaster RP1 / RP2 RX (Great range & reliability)**

-

----

-

-### **🔹 Why Choose ELRS 2.4GHz?**

-✅ **Best for FPV Racing & Freestyle** → **Low latency & fast response**

-✅ **Perfect for Long-Range FPV** → **Good range at lower packet rates**

-✅ **Affordable & Open-Source** → **Cheaper than Crossfire & Ghost**

-

-🚀 **If you need ultra-low latency for FPV racing or long-range performance at an affordable price, ExpressLRS 2.4GHz is the best choice!** 🔥

-

-

-## 2.4hz compare to LORA 915mhz

-

-| Feature | DJI NC3 (OcuSync 2.0) | ELRS 2.4GHz (100mW) | ELRS 915MHz (100mW, SX1276) |

-|----------------------------|---------------------------|------------------------------|-------------------------------|

-| Protocol Type | Proprietary digital (DJI) | Open-source LoRa/FLRC | Open-source LoRa |

-| Frequency Band | 2.4GHz + 5.8GHz | 2.4GHz | 915MHz |

-| Max Packet Rate | N/A (digital control/video)| Up to 500Hz | Up to 50Hz |

-| Latency (best-case) | ~120 ms (control + video) | ~2.5 ms (500Hz) | ~20 ms (50Hz) |

-| Typical Latency | ~120–150 ms | ~6–13 ms | ~22–30 ms |

-| Max Range (LOS, FCC) | ~10 km | ~2 km | ~10 km |

-| Penetration (Obstacles) | Moderate | Moderate | Strong |

-| Interference Resistance | High (hopping + digital) | Moderate | Strong |

-| Video Support | Yes (integrated) | No | No |

-| Use Case | DJI drones (Mini, Air) | FPV racing, freestyle | Long-range FPV, endurance |

-| Antenna Size | Small | Small | Larger |

-| Custom Flight Controllers | Not supported | Fully supported | Fully supported |

-

-

-❌ No — ELRS does not support 5.8GHz (as of now).

-

-- [[LORA-dat]] - [[RF-2.4ghz-dat]]

-

-- [[5.8Ghz-dat]]

-

-

-## WebUI

-

-### Via "ExpressLRS RX" Access Point

-

-

-

-Load the Web UI on your browser using these addresses:

-

-http://10.0.0.1/ - If you have connected to the ExpressLRS RX Access Point

-

-### Via button press

-

-

-

-

-## ref

-

-- [[FPV-dat]]

-

-- [[ELRS]]

-

-# ELRS-faq-dat

-

-## Frequently Asked Questions (FAQ)

-

-**Q1: Can this receiver bind with a transmitter module (TX module) from brand XXX?**

-**A:** The ELRS project is open-source. Therefore, as long as the TX module uses the ELRS protocol, regardless of the brand, they can bind with each other, provided three conditions are met:

- 1. **Same Frequency:** Both must operate on the same frequency band (e.g., both 2.4GHz or both 915MHz).

- 2. **Matching Firmware Version:** The firmware versions must be identical. For example, if the TX module is flashed with firmware version 2.5.0, the receiver must also be flashed with version 2.5.0.

- 3. **Binding Phrase:** Either both devices have no binding phrase set, or they both have the exact same binding phrase configured.

-

-**Q2: How do I enter binding mode?**

-**A:** After soldering the receiver, quickly power cycle the aircraft three times: power on then immediately power off, power on then immediately power off, power on and leave it on. Each power cycle interval should be less than 1.5 seconds. If performed correctly, the receiver's LED will flash quickly twice in a repeating pattern, indicating it is in binding mode. Then, use the bind function/button on your remote controller (often found in the ELRS Lua script). Once binding is successful, the receiver's LED will turn solid.

-

-**Q3: The first time I used my receiver, it wouldn't enter binding mode, and the LED stayed solid. Why?**

-**A:** We've encountered this issue in support cases. It's often caused by an abnormality on the flight controller's TX/RX UART port, which forces the receiver into bootloader/firmware flashing mode upon power-up. Switching the receiver connection to a different, functional TX/RX UART port on the flight controller usually resolves this.

-

-**Q4: Why is my receiver's LED flashing quickly and continuously?**

-**A:** If the receiver is powered on but doesn't enter binding mode (or if it's already bound but the remote controller is off), it will automatically enter Wi-Fi firmware update mode after approximately 60 seconds of not receiving a signal. The fast flashing indicates Wi-Fi mode is active.

-

-**Q5: How do I enter Wi-Fi mode to update the receiver's firmware?**

-**A:** As mentioned above, simply power on the receiver and wait. If it doesn't connect to a transmitter within about 60 seconds, it will automatically enter Wi-Fi update mode, indicated by the rapidly flashing LED.

-

-

-## ref

-

-

-# ELRS-frequency-dat.md

-

-| Feature | ELRS 915MHz (LoRa) | ELRS 2.4GHz (LoRa/FLRC) |

-|---------------------|-----------------------------|------------------------------|

-| Frequency Band | 915 MHz | 2.4 GHz |

-| Range (LOS, 100mW) | ✅ 5–10+ km | ⚠️ 1–2 km |

-| Penetration | ✅ Strong (trees, buildings) | ⚠️ Moderate |

-| Latency | ❌ ~20–30 ms | ✅ ~2.5–13 ms |

-| Max Packet Rate | ❌ ~50Hz | ✅ Up to 500Hz |

-| Antenna Size | ❌ Large | ✅ Small |

-| Interference Avoidance | ✅ Less crowded band | ⚠️ More Wi-Fi/Bluetooth noise |

-| Use Case | Long-range, endurance | Freestyle, racing |

-| Power Efficiency | ✅ High (lower data rate) | ✅ High (LoRa + FLRC modes) |

-| Hardware Support | Older SX1276 modules | Newer SX1280 + ESP modules |

-

-

-## ref

-

-- [[ELRS-dat]]

-

-# FrSky-dat

-

-- [[CC2500-dat]]

-

-# PPM-dat

-

-- [[Wfly-dat]]

-

-- [[PWM-dat]]

-

-PPM (Pulse Position Modulation) is a type of analog signal used in radio control (RC) systems to transmit multiple channels of control information (like throttle, steering, elevator, etc.) over a single wire.

-

-In simple terms:

-

-- It sends a series of pulses.

-- The position (or timing) of each pulse within a repeating frame represents the value for a specific channel.

-- A longer "sync" pulse marks the end of one frame and the beginning of the next.

-

-So, instead of needing a separate wire for each control channel, PPM combines them into one sequential signal.

-

-## demo video

-

-[RC #PPM PWM send and receive at Arduino, note the four channels color](https://youtube.com/shorts/BDdSFPlh9KE?si=n1oF2KUIMqEeH1QW)

-

-

-

-

-## ref

-

-- [[RC-protocols-dat]]

-

-# RC-protocols-dat.md

-

-- [[edge-tx-dat]]

-

-- [[CRSF-dat]]

-

-- [[FrSky-dat]] == [[CC2500-dat]]

-

-- [[ELRS-dat]]

-

-- [[SBUS-dat]] - [[PPM-dat]]

-

-## ref

-

-- [[RC-dat]]

-

-# SBUS-dat

-

-- [[futaba-dat]]

-

-## 📡 What is SBUS? — Simple Explanation

-

-**SBUS (Serial Bus)** is a digital protocol used in RC systems to send multiple control signals (channels) over a single wire.

-

----

-

-### 🧩 Key Features

-

-- 🔢 **Up to 16 channels** in one signal

-- 💬 **Digital serial protocol**

-- 📦 Sends data in **serial frames**

-- ⏱️ **100,000 baud**, **inverted UART**

-- ↪️ Invented by **Futaba**, widely used (FrSky, Radiolink, etc.)

-- 🧠 Needs **inversion** to be read by normal UART (hardware or software)

-

----

-

-### 🧱 Simple Analogy

-

-> SBUS is like 16 people taking turns speaking very fast on one microphone.

-> Each frame contains all channel values packed tightly together.

-

----

-

-### 🧪 Data Frame Structure

-

-Each SBUS frame is 25 bytes:

-

-| 1 byte | 22 bytes | 1 byte | 1 byte |

-| ------ | ----------- | ------ | ------ |

-| Header | 16 channels | Flags | End |

-

-

-

-- **Header**: 0x0F

-- **End**: 0x00

-- Sent **every ~9ms** (111Hz refresh rate)

-

----

-

-### 🔌 Common Use Cases

-

-- RC Receiver → Flight Controller (e.g., FrSky RX to Betaflight FC)

-- RC Receiver → Microcontroller (Arduino, ESP32)

-- RC → Servo controller boards (if SBUS supported)

-

----

-

-### ⚖️ SBUS vs PWM vs PPM

-

-| Feature | SBUS | PWM | PPM |

-|---------------|-------------|---------------|---------------|

-| Channels | 16 | 1 per wire | 8 (typically) |

-| Wires needed | 1 | 1 per channel | 1 |

-| Type | Digital | Analog pulse | Analog pulse |

-| Speed | Very fast | Slow | Medium |

-| Latency | Very low | High | Medium |

-

----

-

-### 🧰 Tip for Developers

-

-To read SBUS using a microcontroller:

-- Use **UART** at **100000 baud**, **8E2**, **inverted signal**

-- Some MCUs (like ESP32) support inversion natively

-- Otherwise, use an **inverter circuit** or a software decoder

-

-## ref

-

-- [[network-dat]]

-

-# edge-tx-dat

-

-https://github.com/EdgeTX/edgetx