3db1f982d6fab105faeff7dc4b0df9a33d149277
app-dat/RC-dat/ArduPilot-dat/2025-05-04-16-11-57.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/ArduPilot-dat/2025-05-04-16-11-57.png differ |
app-dat/RC-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 | + |
|
| 89 | + |
|
| 90 | + |
|
| 91 | +## ref |
|
| 92 | + |
|
| 93 | +- [[ardupilot-dat]] - [[FPV]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-car-dat/2025-03-25-15-00-18.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/2025-03-25-15-00-18.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/2025-03-25-15-00-49.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/2025-03-25-15-00-49.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/2025-03-25-15-01-11.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/2025-03-25-15-01-11.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/2025-03-25-15-02-19.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/2025-03-25-15-02-19.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/2025-03-28-18-44-53.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/2025-03-28-18-44-53.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/RC-car-dat.md
| ... | ... | @@ -1,49 +0,0 @@ |
| 1 | - |
|
| 2 | -# RC-car-dat |
|
| 3 | - |
|
| 4 | -- [[video-RC-car-dat]] |
|
| 5 | - |
|
| 6 | -basic [[tech-dat]] - [[robot-dat]] |
|
| 7 | - |
|
| 8 | - |
|
| 9 | - |
|
| 10 | -## Tracked robot platform |
|
| 11 | - |
|
| 12 | - |
|
| 13 | - |
|
| 14 | - |
|
| 15 | - |
|
| 16 | - |
|
| 17 | - |
|
| 18 | - |
|
| 19 | - |
|
| 20 | - |
|
| 21 | -## tricycle / four-wheels platform |
|
| 22 | - |
|
| 23 | - |
|
| 24 | - |
|
| 25 | -tricycle |
|
| 26 | - |
|
| 27 | -Four-wheel two-drive car |
|
| 28 | - |
|
| 29 | -Four-wheel drive car |
|
| 30 | - |
|
| 31 | -Omnidirectional four-wheel two-wheel drive car |
|
| 32 | - |
|
| 33 | - |
|
| 34 | -## other |
|
| 35 | - |
|
| 36 | -### robot tank with camera |
|
| 37 | - |
|
| 38 | -- https://github.com/YahboomTechnology/Raspberry-pi-G1-Tank |
|
| 39 | - |
|
| 40 | - |
|
| 41 | -## read |
|
| 42 | - |
|
| 43 | -- [Tear down and Learn a good-build $20 RC Toy Car](https://www.electrodragon.com/disassemble-and-learn-a-good-build-20-rc-toy-car/) |
|
| 44 | - |
|
| 45 | -## ref |
|
| 46 | - |
|
| 47 | -- [[motor-dat]] |
|
| 48 | - |
|
| 49 | -- [[RC-car]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-car-dat/RC-car-hack-dat/RC-car-hack-dat.md
| ... | ... | @@ -1,26 +0,0 @@ |
| 1 | - |
|
| 2 | -# rc-car-hack-dat |
|
| 3 | - |
|
| 4 | - |
|
| 5 | -## 1. battery Enlargement |
|
| 6 | - |
|
| 7 | -- [[lithium-battery-dat]] |
|
| 8 | - |
|
| 9 | -## 2. RC Signal Extension |
|
| 10 | - |
|
| 11 | -- improve up to 10KM by [[FPV-dat]] system [[ELRS-dat]] |
|
| 12 | - |
|
| 13 | -- [[antenna-dat]] |
|
| 14 | - |
|
| 15 | -- control system - try to hack by [[arduino-dat]] |
|
| 16 | - |
|
| 17 | -## 3. Imaging System |
|
| 18 | - |
|
| 19 | -- [[video-transmission-dat]] == pickup option == [[LTE-dat]] |
|
| 20 | - |
|
| 21 | - |
|
| 22 | - |
|
| 23 | - |
|
| 24 | -## 4. GNSS location system |
|
| 25 | - |
|
| 26 | -- [[location-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-43-46.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-43-46.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-48-15.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-48-15.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-48-28.png
| ... | ... | Binary files a/app-dat/RC-dat/RC-car-dat/video-RC-car-dat/2025-03-25-14-48-28.png and /dev/null differ |
app-dat/RC-dat/RC-car-dat/video-RC-car-dat/video-RC-car-dat.md
| ... | ... | @@ -1,36 +0,0 @@ |
| 1 | - |
|
| 2 | -# video-RC-car-dat |
|
| 3 | - |
|
| 4 | - |
|
| 5 | -[[tech-dat]] - [[Camera-dat]] - [[rc-car-dat]] - [[video-transmission-dat]] - [[robot-dat]] |
|
| 6 | - |
|
| 7 | -- [[rc-car-hack-dat]] |
|
| 8 | - |
|
| 9 | -## Demos |
|
| 10 | - |
|
| 11 | -### based on cable [[fiber-optic-dat]] |
|
| 12 | - |
|
| 13 | -#### demos 1 |
|
| 14 | - |
|
| 15 | -up to 100 meters |
|
| 16 | - |
|
| 17 | - |
|
| 18 | - |
|
| 19 | - |
|
| 20 | - |
|
| 21 | - |
|
| 22 | - |
|
| 23 | - |
|
| 24 | -#### demo video 2 |
|
| 25 | - |
|
| 26 | -- https://t.me/electrodragon3/334 |
|
| 27 | - |
|
| 28 | -### Wireless |
|
| 29 | - |
|
| 30 | -- [[video-transmission-dat]] |
|
| 31 | - |
|
| 32 | -## ref |
|
| 33 | - |
|
| 34 | -- [[video-RC-car]] - [[RC-car]] - [[video-transmission]] |
|
| 35 | - |
|
| 36 | -- [[camera]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-dat.md
| ... | ... | @@ -1,6 +1,31 @@ |
| 1 | 1 | |
| 2 | 2 | # RC-dat |
| 3 | 3 | |
| 4 | -- [[RC-car-dat]] - [[RC-car-hack-dat]] - [[video-rc-car-dat]] |
|
| 5 | 4 | |
| 6 | -- [[BMS-dat]] |
|
| ... | ... | \ No newline at end of file |
| 0 | +## RC - apps |
|
| 1 | + |
|
| 2 | +- [[rover-dat]] - [[RC-car-dat]] - [[RC-car-hack-dat]] - [[video-rc-car-dat]] |
|
| 3 | + |
|
| 4 | +- [[quadcopter-dat]] - [[FPV-dat]] |
|
| 5 | + |
|
| 6 | +- [[airplane-dat]] |
|
| 7 | + |
|
| 8 | +- [[UAV-dat]] |
|
| 9 | + |
|
| 10 | +## RC - protocols |
|
| 11 | + |
|
| 12 | +- [[RC-protocols-dat]] |
|
| 13 | + |
|
| 14 | +## RC - systems |
|
| 15 | + |
|
| 16 | +- [[ardupilot-dat]] |
|
| 17 | + |
|
| 18 | +## RC - Hardware |
|
| 19 | + |
|
| 20 | +- [[flight-controller-dat]] |
|
| 21 | + |
|
| 22 | +- [[BMS-dat]] |
|
| 23 | + |
|
| 24 | +## RC - manufacturers |
|
| 25 | + |
|
| 26 | +- [[Wfly-dat]] - [[betaFPV-dat]] - [[speedybee-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/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/RC-dat/RC-protocols/ELRS-dat/2025-04-25-17-30-48.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/2025-04-25-17-30-48.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/2025-04-25-17-34-11.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/2025-04-25-17-34-11.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/2025-05-04-15-29-54.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/2025-05-04-15-29-54.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/2025-05-04-15-31-56.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/2025-05-04-15-31-56.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-915M-dat.md
| ... | ... | @@ -0,0 +1,4 @@ |
| 1 | + |
|
| 2 | +# ELRS-915M-dat.md |
|
| 3 | + |
|
| 4 | + |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-CHS-PWM-dat.md
| ... | ... | @@ -0,0 +1,4 @@ |
| 1 | + |
|
| 2 | +# ELRS-CHS-PWM-dat.md |
|
| 3 | + |
|
| 4 | + |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-RX-dat/2025-04-25-16-52-56.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-RX-dat/2025-04-25-16-52-56.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-RX-dat/2025-04-25-16-55-05.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-RX-dat/2025-04-25-16-55-05.png differ |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-RX-dat/ELRS-RX-dat.md
| ... | ... | @@ -0,0 +1,43 @@ |
| 1 | + |
|
| 2 | +# ELRS-RX-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## T-anntena version |
|
| 6 | + |
|
| 7 | + |
|
| 8 | + |
|
| 9 | +## SMD antenna version |
|
| 10 | + |
|
| 11 | +## info |
|
| 12 | + |
|
| 13 | +Nano2400-RX receiver with power amplifier (PA+LNA). |
|
| 14 | + |
|
| 15 | +Therefore, it has 100mW telemetry output and better sensitivity at longer distances. |
|
| 16 | + |
|
| 17 | +It uses an IPEX1 antenna connector. |
|
| 18 | + |
|
| 19 | +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). |
|
| 20 | + |
|
| 21 | +The CYCLONE series receivers are based on the open-source architecture and program of ExpressLRS. |
|
| 22 | + |
|
| 23 | +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. |
|
| 24 | + |
|
| 25 | +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. |
|
| 26 | + |
|
| 27 | +The password is "expresslrs", and then you can access 10.0.0.1 to upload the receiver firmware. |
|
| 28 | + |
|
| 29 | +## Product Features |
|
| 30 | + |
|
| 31 | +- High refresh rate 100mW telemetry output; |
|
| 32 | +- Supports convenient and fast firmware flashing via WIFI connection; |
|
| 33 | +- Firmware Version: 3.3.0 [BETAFPVLite2400RX] |
|
| 34 | +- Equipped with a power amplifier (PA+LNA), providing 100mW telemetry output and better response speed; |
|
| 35 | +- Theoretically compatible with most ELRS 2.4G transmitter modules on the market (requires firmware version 2.0 or above). |
|
| 36 | + |
|
| 37 | + |
|
| 38 | + |
|
| 39 | + |
|
| 40 | + |
|
| 41 | +## ref |
|
| 42 | + |
|
| 43 | +- [[ELRS-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-dat.md
| ... | ... | @@ -0,0 +1,143 @@ |
| 1 | + |
|
| 2 | +# ELRS-dat |
|
| 3 | + |
|
| 4 | +Info - [[ELRS-frequency-dat]] - [[ELRS-faq-dat]] |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +## ELRS-link |
|
| 8 | + |
|
| 9 | +ELRS-remote-console-tx |
|
| 10 | + |
|
| 11 | +- BETAFPV literadio 3 |
|
| 12 | +- BETAFPV literadio 2 |
|
| 13 | + |
|
| 14 | +- [[edge-tx-dat]] - [[radiomaster-dat]] - [[lightradio-dat]] |
|
| 15 | + |
|
| 16 | +- [[ELRS-RX-dat]] - [[SX1276-dat]] - [[ESP8285-dat]] - [[ESP32-dat]] - [[SX1281-dat]] - [[SX1208-dat]] |
|
| 17 | + |
|
| 18 | +protocol output - - [[CRSF-dat]] |
|
| 19 | + |
|
| 20 | +- [[CC2500-dat]] |
|
| 21 | + |
|
| 22 | +- [[ELRS-915M-dat]] - [[ELRS-CHS-PWM-dat]] - [[ELRS-2.4Ghz-dat]] |
|
| 23 | + |
|
| 24 | +- [[ELRS]] |
|
| 25 | + |
|
| 26 | +## resources |
|
| 27 | + |
|
| 28 | +https://github.com/ExpressLRS/ExpressLRS |
|
| 29 | + |
|
| 30 | +https://www.expresslrs.org/quick-start/getting-started/ |
|
| 31 | + |
|
| 32 | +[ExpressLRS-Configurator-releases](https://github.com/ExpressLRS/ExpressLRS-Configurator/releases) |
|
| 33 | + |
|
| 34 | + |
|
| 35 | + |
|
| 36 | +## **ExpressLRS (ELRS) 2.4GHz Standard Explained** |
|
| 37 | + |
|
| 38 | +**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. |
|
| 39 | + |
|
| 40 | +--- |
|
| 41 | + |
|
| 42 | +### **🔹 Key Features of ELRS 2.4GHz** |
|
| 43 | +- **Ultra-Low Latency** (~5ms in high-speed mode). |
|
| 44 | +- **Long-Range Performance** (Up to **30km+** with proper setup). |
|
| 45 | +- **High Packet Rate (Up to 1000Hz)** for **smooth & responsive controls**. |
|
| 46 | +- **Open-Source & Customizable** (Community-driven development). |
|
| 47 | +- **Affordable Hardware** (Compared to Crossfire or Ghost). |
|
| 48 | +- **Wide Compatibility** (Supported on many **radio transmitters & receivers**). |
|
| 49 | + |
|
| 50 | +--- |
|
| 51 | + |
|
| 52 | +### **🔹 ELRS 2.4GHz vs. Other RC Links** |
|
| 53 | +| Feature | ELRS 2.4GHz | TBS Crossfire | Ghost 2.4GHz | FrSky R9M | |
|
| 54 | +| --------------- | ------------ | ------------- | ------------ | ----------- | |
|
| 55 | +| **Frequency** | 2.4GHz | 900MHz | 2.4GHz | 900MHz | |
|
| 56 | +| **Max Range** | ~30km+ | ~50km+ | ~15km | ~10-20km | |
|
| 57 | +| **Latency** | 5-7ms | 15-50ms | ~4ms | ~20ms | |
|
| 58 | +| **Packet Rate** | Up to 1000Hz | 50-150Hz | 500Hz | ~100Hz | |
|
| 59 | +| **Open Source** | ✅ Yes | ❌ No | ❌ No | ❌ No | |
|
| 60 | +| **Cost** | 💰 Affordable | 💰💰 Expensive | 💰💰 Expensive | 💰 Mid-Range | |
|
| 61 | + |
|
| 62 | +--- |
|
| 63 | + |
|
| 64 | +### **🔹 ELRS 2.4GHz Modes & Performance** |
|
| 65 | +| Mode | Packet Rate | Latency | Range | |
|
| 66 | +| --------- | ----------- | ------- | --------------------- | |
|
| 67 | +| **500Hz** | 500Hz | ~5ms | Short (~3km) | |
|
| 68 | +| **250Hz** | 250Hz | ~7ms | Mid (~10km) | |
|
| 69 | +| **150Hz** | 150Hz | ~10ms | Long (~20km) | |
|
| 70 | +| **50Hz** | 50Hz | ~20ms | Extreme Long (~30km+) | |
|
| 71 | + |
|
| 72 | +🔹 **Higher packet rate = Lower latency, but reduced range** |
|
| 73 | +🔹 **Lower packet rate = Higher range, but increased latency** |
|
| 74 | + |
|
| 75 | +--- |
|
| 76 | + |
|
| 77 | +### **🔹 Recommended ExpressLRS 2.4GHz Hardware** |
|
| 78 | +#### **🛠️ Transmitters (TX)** |
|
| 79 | +- **RadioMaster Zorro ELRS 2.4GHz** |
|
| 80 | +- **Jumper T20S (Built-in ELRS)** |
|
| 81 | +- **Happymodel ES24TX Pro (External ELRS Module)** |
|
| 82 | +- **BetaFPV ELRS Micro TX Module** |
|
| 83 | + |
|
| 84 | +#### **📡 Receivers (RX)** |
|
| 85 | +- **Happymodel EP2 (Tiny, best for micro quads)** |
|
| 86 | +- **BetaFPV ELRS 2.4GHz Nano RX** |
|
| 87 | +- **Radiomaster RP1 / RP2 RX (Great range & reliability)** |
|
| 88 | + |
|
| 89 | +--- |
|
| 90 | + |
|
| 91 | +### **🔹 Why Choose ELRS 2.4GHz?** |
|
| 92 | +✅ **Best for FPV Racing & Freestyle** → **Low latency & fast response** |
|
| 93 | +✅ **Perfect for Long-Range FPV** → **Good range at lower packet rates** |
|
| 94 | +✅ **Affordable & Open-Source** → **Cheaper than Crossfire & Ghost** |
|
| 95 | + |
|
| 96 | +🚀 **If you need ultra-low latency for FPV racing or long-range performance at an affordable price, ExpressLRS 2.4GHz is the best choice!** 🔥 |
|
| 97 | + |
|
| 98 | + |
|
| 99 | +## 2.4hz compare to LORA 915mhz |
|
| 100 | + |
|
| 101 | +| Feature | DJI NC3 (OcuSync 2.0) | ELRS 2.4GHz (100mW) | ELRS 915MHz (100mW, SX1276) | |
|
| 102 | +|----------------------------|---------------------------|------------------------------|-------------------------------| |
|
| 103 | +| Protocol Type | Proprietary digital (DJI) | Open-source LoRa/FLRC | Open-source LoRa | |
|
| 104 | +| Frequency Band | 2.4GHz + 5.8GHz | 2.4GHz | 915MHz | |
|
| 105 | +| Max Packet Rate | N/A (digital control/video)| Up to 500Hz | Up to 50Hz | |
|
| 106 | +| Latency (best-case) | ~120 ms (control + video) | ~2.5 ms (500Hz) | ~20 ms (50Hz) | |
|
| 107 | +| Typical Latency | ~120–150 ms | ~6–13 ms | ~22–30 ms | |
|
| 108 | +| Max Range (LOS, FCC) | ~10 km | ~2 km | ~10 km | |
|
| 109 | +| Penetration (Obstacles) | Moderate | Moderate | Strong | |
|
| 110 | +| Interference Resistance | High (hopping + digital) | Moderate | Strong | |
|
| 111 | +| Video Support | Yes (integrated) | No | No | |
|
| 112 | +| Use Case | DJI drones (Mini, Air) | FPV racing, freestyle | Long-range FPV, endurance | |
|
| 113 | +| Antenna Size | Small | Small | Larger | |
|
| 114 | +| Custom Flight Controllers | Not supported | Fully supported | Fully supported | |
|
| 115 | + |
|
| 116 | + |
|
| 117 | +❌ No — ELRS does not support 5.8GHz (as of now). |
|
| 118 | + |
|
| 119 | +- [[LORA-dat]] - [[RF-2.4ghz-dat]] |
|
| 120 | + |
|
| 121 | +- [[5.8Ghz-dat]] |
|
| 122 | + |
|
| 123 | + |
|
| 124 | +## WebUI |
|
| 125 | + |
|
| 126 | +### Via "ExpressLRS RX" Access Point |
|
| 127 | + |
|
| 128 | + |
|
| 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 | + |
|
| 137 | + |
|
| 138 | + |
|
| 139 | +## ref |
|
| 140 | + |
|
| 141 | +- [[FPV-dat]] |
|
| 142 | + |
|
| 143 | +- [[ELRS]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-faq-dat.md
| ... | ... | @@ -0,0 +1,26 @@ |
| 1 | + |
|
| 2 | +# ELRS-faq-dat |
|
| 3 | + |
|
| 4 | +## Frequently Asked Questions (FAQ) |
|
| 5 | + |
|
| 6 | +**Q1: Can this receiver bind with a transmitter module (TX module) from brand XXX?** |
|
| 7 | +**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: |
|
| 8 | + 1. **Same Frequency:** Both must operate on the same frequency band (e.g., both 2.4GHz or both 915MHz). |
|
| 9 | + 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. |
|
| 10 | + 3. **Binding Phrase:** Either both devices have no binding phrase set, or they both have the exact same binding phrase configured. |
|
| 11 | + |
|
| 12 | +**Q2: How do I enter binding mode?** |
|
| 13 | +**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. |
|
| 14 | + |
|
| 15 | +**Q3: The first time I used my receiver, it wouldn't enter binding mode, and the LED stayed solid. Why?** |
|
| 16 | +**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. |
|
| 17 | + |
|
| 18 | +**Q4: Why is my receiver's LED flashing quickly and continuously?** |
|
| 19 | +**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. |
|
| 20 | + |
|
| 21 | +**Q5: How do I enter Wi-Fi mode to update the receiver's firmware?** |
|
| 22 | +**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. |
|
| 23 | + |
|
| 24 | + |
|
| 25 | +## ref |
|
| 26 | + |
app-dat/RC-dat/RC-protocols/ELRS-dat/ELRS-frequency-dat.md
| ... | ... | @@ -0,0 +1,20 @@ |
| 1 | + |
|
| 2 | +# ELRS-frequency-dat.md |
|
| 3 | + |
|
| 4 | +| Feature | ELRS 915MHz (LoRa) | ELRS 2.4GHz (LoRa/FLRC) | |
|
| 5 | +|---------------------|-----------------------------|------------------------------| |
|
| 6 | +| Frequency Band | 915 MHz | 2.4 GHz | |
|
| 7 | +| Range (LOS, 100mW) | ✅ 5–10+ km | ⚠️ 1–2 km | |
|
| 8 | +| Penetration | ✅ Strong (trees, buildings) | ⚠️ Moderate | |
|
| 9 | +| Latency | ❌ ~20–30 ms | ✅ ~2.5–13 ms | |
|
| 10 | +| Max Packet Rate | ❌ ~50Hz | ✅ Up to 500Hz | |
|
| 11 | +| Antenna Size | ❌ Large | ✅ Small | |
|
| 12 | +| Interference Avoidance | ✅ Less crowded band | ⚠️ More Wi-Fi/Bluetooth noise | |
|
| 13 | +| Use Case | Long-range, endurance | Freestyle, racing | |
|
| 14 | +| Power Efficiency | ✅ High (lower data rate) | ✅ High (LoRa + FLRC modes) | |
|
| 15 | +| Hardware Support | Older SX1276 modules | Newer SX1280 + ESP modules | |
|
| 16 | + |
|
| 17 | + |
|
| 18 | +## ref |
|
| 19 | + |
|
| 20 | +- [[ELRS-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/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/RC-dat/RC-protocols/RC-protocols-dat.md
| ... | ... | @@ -0,0 +1,16 @@ |
| 1 | + |
|
| 2 | +# RC-protocols-dat.md |
|
| 3 | + |
|
| 4 | +- [[edge-tx-dat]] |
|
| 5 | + |
|
| 6 | +- [[CRSF-dat]] |
|
| 7 | + |
|
| 8 | +- [[FrSky-dat]] == [[CC2500-dat]] |
|
| 9 | + |
|
| 10 | +- [[ELRS-dat]] |
|
| 11 | + |
|
| 12 | +- [[SBUS-dat]] - [[PPM-dat]] |
|
| 13 | + |
|
| 14 | +## ref |
|
| 15 | + |
|
| 16 | +- [[RC-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/RC-protocols/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]] |
app-dat/RC-dat/RC-protocols/edge-tx-dat/edge-tx-dat.md
| ... | ... | @@ -0,0 +1,4 @@ |
| 1 | + |
|
| 2 | +# edge-tx-dat |
|
| 3 | + |
|
| 4 | +https://github.com/EdgeTX/edgetx |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/UAV-dat/UAV-dat.md
| ... | ... | @@ -0,0 +1,46 @@ |
| 1 | + |
|
| 2 | +# UAV-dat |
|
| 3 | + |
|
| 4 | +A UAV stands for Unmanned Aerial Vehicle. It's an aircraft without a human pilot on board, controlled remotely or autonomously. They are also commonly known as drones. |
|
| 5 | + |
|
| 6 | +- [[betaflight-dat]] - [[ArduPilot-dat]] |
|
| 7 | + |
|
| 8 | +- [[FPV-dat]] |
|
| 9 | + |
|
| 10 | + |
|
| 11 | + |
|
| 12 | +## fixed-wing UAV |
|
| 13 | + |
|
| 14 | +### Talon 1400 Overview |
|
| 15 | + |
|
| 16 | +#### What is the Talon 1400? |
|
| 17 | +The **Talon 1400** is a high-performance, **3D-printed unmanned aerial vehicle (UAV)** developed by Flightory. It is optimized for long-range and efficient flight. |
|
| 18 | + |
|
| 19 | +##### Specifications: |
|
| 20 | +- **Wingspan:** 1,305 mm |
|
| 21 | +- **Length:** 830 mm |
|
| 22 | +- **Flight Time:** Up to 4 hours (with large Li-Ion 4S6P battery) |
|
| 23 | +- **Materials:** LW-PLA and PETG |
|
| 24 | +- **Airfoil:** Eppler E205 |
|
| 25 | +- **Optimal Cruise Speed:** 55-65 km/h |
|
| 26 | + |
|
| 27 | +#### Is It Betaflight-Based? |
|
| 28 | + |
|
| 29 | +**No**, the Talon 1400 is **not** based on Betaflight. Since it is a **fixed-wing UAV**, it is more suited for **autonomous flight controllers** rather than Betaflight, which is designed for FPV racing drones. |
|
| 30 | + |
|
| 31 | +##### Recommended Flight Controllers: |
|
| 32 | + |
|
| 33 | +- **Mateksys F405-Wing / F765-Wing** |
|
| 34 | +- **Pixhawk (PX4 or ArduPilot firmware)** |
|
| 35 | +- **Holybro Kakute F7 / H743-Wing** |
|
| 36 | + |
|
| 37 | +These controllers support **GPS navigation, waypoint missions, and return-to-home (RTH)**, making them better suited for long-range operations. |
|
| 38 | + |
|
| 39 | +#### Resources: |
|
| 40 | + |
|
| 41 | +- [Flying a 3D Printed Fixed Wing Drone | Talon 1400 V2](https://www.youtube.com/watch?v=2ngGgtw1sUw) |
|
| 42 | + |
|
| 43 | +- [Flightory Talon 1400 Official Page](https://flightory.com/product/talon-1400/) |
|
| 44 | +- [Talon 1400 Assembly Tutorial (YouTube)](https://www.youtube.com/watch?v=LGt_8F4e5r8) |
|
| 45 | + |
|
| 46 | + |
app-dat/RC-dat/UAV-dat/betaflight-dat.md
| ... | ... | @@ -0,0 +1,31 @@ |
| 1 | + |
|
| 2 | + |
|
| 3 | +# betaflight-dat.md |
|
| 4 | + |
|
| 5 | +Betaflight is an open-source firmware for drones and other unmanned aerial vehicles (UAVs). It is designed to provide advanced flight control capabilities, making it popular among hobbyists and enthusiasts in the drone community. Betaflight is known for its flexibility, configurability, and support for a wide range of hardware platforms. |
|
| 6 | + |
|
| 7 | +- [[FPV-dat]] |
|
| 8 | + |
|
| 9 | + |
|
| 10 | + |
|
| 11 | + |
|
| 12 | + |
|
| 13 | +## commerlized projects |
|
| 14 | + |
|
| 15 | +- **speedybee** == https://www.speedybee.com/ == SpeedyBee is a company that specializes in providing high-quality drone components and accessories, including flight controllers, ESCs, and other related products. They are known for their innovative designs and user-friendly interfaces, making them a popular choice among drone enthusiasts. |
|
| 16 | +- **betafpv** == https://www.betafpv.com/ == BETAFPV is a company that focuses on producing small and lightweight drones, particularly for FPV (First Person View) racing and freestyle flying. They offer a range of products, including flight controllers, cameras, and other accessories tailored for FPV enthusiasts. |
|
| 17 | +- happymodel |
|
| 18 | +- iFlight |
|
| 19 | +- Holybro |
|
| 20 | +- TBS |
|
| 21 | +- Flywoo |
|
| 22 | +- HGLRC |
|
| 23 | +- Diatone |
|
| 24 | +- GepRC |
|
| 25 | +- Racerstar |
|
| 26 | +- Emax |
|
| 27 | +- Eachine |
|
| 28 | +- HGLRC |
|
| 29 | +- Racerstar |
|
| 30 | + |
|
| 31 | + |
app-dat/RC-dat/WFLY-dat/2025-05-05-14-45-14.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/2025-05-05-14-45-14.png differ |
app-dat/RC-dat/WFLY-dat/2025-05-05-14-51-22.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/2025-05-05-14-51-22.png differ |
app-dat/RC-dat/WFLY-dat/2025-05-05-14-53-48.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/2025-05-05-14-53-48.png differ |
app-dat/RC-dat/WFLY-dat/2025-05-05-14-58-58.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/2025-05-05-14-58-58.png differ |
app-dat/RC-dat/WFLY-dat/2025-05-05-15-03-29.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/2025-05-05-15-03-29.png differ |
app-dat/RC-dat/WFLY-dat/WFLY-WFT06X_Mannual.pdf
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/WFLY-dat/WFLY-WFT06X_Mannual.pdf differ |
app-dat/RC-dat/WFLY-dat/WFLY-dat.md
| ... | ... | @@ -0,0 +1,7 @@ |
| 1 | + |
|
| 2 | +# WFLY-dat.md |
|
| 3 | + |
|
| 4 | +- [[WFT06x-dat]] - [[WFR06S-dat]] |
|
| 5 | + |
|
| 6 | + |
|
| 7 | + |
app-dat/RC-dat/WFLY-dat/WFR06S-dat.md
| ... | ... | @@ -0,0 +1,4 @@ |
| 1 | + |
|
| 2 | +# WFR06S-dat.md |
|
| 3 | + |
|
| 4 | + |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/WFLY-dat/WFT06X-dat.md
| ... | ... | @@ -0,0 +1,113 @@ |
| 1 | +# WFLY-dat |
|
| 2 | + |
|
| 3 | + |
|
| 4 | + |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +- the manual == [[WFLY-WFT06X_Mannual.pdf]] |
|
| 8 | +- [fccd.io manual link](https://fccid.io/TZVWFT06XWFT08S/User-Manual/User-Manual-1-1119279.pdf) |
|
| 9 | + |
|
| 10 | +## Info |
|
| 11 | + |
|
| 12 | +- WFT06X-A: 6 channels airplane,mixfunction,D/R,HDE helicopter. |
|
| 13 | +- WFT06X-B: 4 channesl airplane, mix function,D/R, HDE helicopter. |
|
| 14 | +- WFT06X-C: 6 channels CCPMhelicopter,airplane. |
|
| 15 | + |
|
| 16 | + |
|
| 17 | +## Models |
|
| 18 | + |
|
| 19 | + |
|
| 20 | + |
|
| 21 | +- [[airplane-dat]] |
|
| 22 | + |
|
| 23 | + |
|
| 24 | +## toggle switches |
|
| 25 | + |
|
| 26 | + |
|
| 27 | + |
|
| 28 | + |
|
| 29 | +| Switch | State | | Up | Down | |
|
| 30 | +| :---------- | :--------- | --------------------------- | :--------------------------------- | :--------------------------------- | |
|
| 31 | +| A | Helicopter | Ch3 to Ch4 mixture. (note1) | Enables | Disables | |
|
| 32 | +| B | N/A | | Selects Helicopter state. | Selects Airplane state. | |
|
| 33 | +| C (1,2,4,6) | Airplane | | Dual Rate set to ±125%. | Dual Rate set to ±100%. | |
|
| 34 | +| D | Airplane | | Enables mixture functions (E, F). | Disables mixture functions (E, F). | |
|
| 35 | +| E | Airplane | | Enables Ch2 & Ch4 mixture (note3) | Enables Ch1 & Ch6 mixture (note3) | |
|
| 36 | +| F | Airplane | | Enables Ch1 & Ch2 mixture (note2). | N/A | |
|
| 37 | +| G (Ch1) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 38 | +| H (Ch2) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 39 | +| I (Ch3) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 40 | +| J (Ch4) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 41 | +| K (Ch6) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 42 | + |
|
| 43 | +note1 == Ch3 to Ch6 mix always active |
|
| 44 | + |
|
| 45 | +note2 == (Elevon/Delta Wing) (Requires D Up, overrides D) |
|
| 46 | + |
|
| 47 | +note3 == (V-Tail) (Requires D Up). |
|
| 48 | + |
|
| 49 | +Switch Function Instruction |
|
| 50 | + |
|
| 51 | +- (A)At helicopterstate,pulling A down to put offmixturefunction of channel3to channel4,when pulling it up it willcomebackthefunction.Butthemixturefunctiontochannel 6isstable,whichisirrelevant with this switch. |
|
| 52 | +- (B) Pulling B down is airplane state and pulling it up is helicopter state. |
|
| 53 | +- (C) At airplane state, pulling 1, 2, 4, 6 down the dual rate is ±100%; when pulling them up, the dual rate will be ±125%. |
|
| 54 | +- (D) At airplane state, pulling D down make switches have no mixture function, but pulling it up will cause them have thefunction. |
|
| 55 | +- (E) At airplane state, when D is pulled up, pulling E down cause channel 1 & 6 mixture function (Flaperon); pulling E up will cause channel 2 & 4 mixture function(V-TAIL). |
|
| 56 | +- (F) At airplane state,when D is pulled up,pulling F up it works as the mixture function of channel 1&2(TrianglewingELEVON),and Dfunctiondoesn'tworkat that moment. |
|
| 57 | +- (G) Channel 1 is reverse switch for aileron.Pulling G down is to make it in normal mode,and pulling it up is to make it act in reverse. |
|
| 58 | +- (H) Channel 2 is reverse switch for elevator. Pulling H down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 59 | +- (I) Channel 3 is reverse switch for power. Pulling I down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 60 | +- (J) Channel 4 is reverse switch for rudder. Pulling J down is to make it in normal mode, and pulling it up is to makeitactinreverse. |
|
| 61 | +- (K) Channel 6 is reverse switch for screw-pitch/ flaperon.Pulling K down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 62 | + |
|
| 63 | + |
|
| 64 | + |
|
| 65 | +## Binding Instructions: |
|
| 66 | + |
|
| 67 | +1. **Receiver:** Press and hold the "SET" button until the orange "STATUS" light flashes slowly. The receiver is now waiting for the transmitter's binding command. |
|
| 68 | +2. **Transmitter:** Press and hold the "SET" button while powering on the transmitter. Press the SET button once more to enter the binding function (the orange "STATUS" light will be solid). Then, press and hold the SET button until the orange light flashes slowly, entering the binding state. |
|
| 69 | +3. **Binding Successful:** The transmitter's green light will turn solid, and the receiver's indicator light will turn off. |
|
| 70 | + |
|
| 71 | +## Failsafe Setup: |
|
| 72 | + |
|
| 73 | +1. Power on the receiver. |
|
| 74 | +2. Press and hold the "SET" button while powering on the transmitter. Then, press and hold the SET button for about 2 seconds to enter the failsafe setup state (the green light will flash). |
|
| 75 | +3. The receiver's green light will flash quickly. The data currently being output by the transmitter will be set as the failsafe output data for the receiver. |
|
| 76 | +4. **Failsafe Active State:** The receiver's red light will be solid. |
|
| 77 | + |
|
| 78 | +## Technical Parameters: |
|
| 79 | + |
|
| 80 | +* **Application:** Fixed-wing aircraft, HDE helicopters, fixed-pitch helicopters, cars, boats |
|
| 81 | +* **Frequency Band:** 2.400 - 2.483 GHz |
|
| 82 | +* **Transmit Power:** ≤ 100mW |
|
| 83 | +* **Operating Current:** ≤ 160mA |
|
| 84 | +* **Encoding:** PPM |
|
| 85 | +* **RF Module:** Built-in |
|
| 86 | +* **Power Supply:** 9.6 - 12V |
|
| 87 | +* **Dual Rate/Expo Range:** 100% ~ 125% |
|
| 88 | +* **Mixing:** |
|
| 89 | + * Flaperon (Channel 6 and Channel 1 mix) |
|
| 90 | + * V-Tail (Channel 4 and Channel 2 mix) |
|
| 91 | + * Delta Wing (Elevon) (Channel 1 and Channel 2 mix) |
|
| 92 | + * HDE Helicopter (Channel 3 to Channel 4 & 6 mix) |
|
| 93 | + * HDE Helicopter (Channel 3 to Channel 6 mix) |
|
| 94 | +* **Reverse Switches:** |
|
| 95 | + * Channel 1: Aileron |
|
| 96 | + * Channel 2: Elevator |
|
| 97 | + * Channel 3: Throttle |
|
| 98 | + * Channel 4: Rudder |
|
| 99 | + * Channel 6: Flap/Pitch |
|
| 100 | +* **Low Voltage Alarm (Visual & Audible):** |
|
| 101 | + * Battery Voltage < 8.8V: Power indicator flashes once per second with beeping. |
|
| 102 | + * Battery Voltage < 8.3V: Power indicator flashes twice per second (0.5s interval) with beeping. |
|
| 103 | +* **Charging Jack:** Yes |
|
| 104 | +* **Simulator Jack:** Yes |
|
| 105 | + |
|
| 106 | + |
|
| 107 | +## demo video |
|
| 108 | + |
|
| 109 | +- [how to binding WFLY in chinese ](https://www.bilibili.com/video/BV1Mh4y1c7FS/?vd_source=74a6b8b9bfcd41c5946a742815bf71ae) |
|
| 110 | + |
|
| 111 | +## ref |
|
| 112 | + |
|
| 113 | +- [[WFLY]] - [[lightradio]] - [[radiomaster]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/airplane-dat/airplane-dat.md
| ... | ... | @@ -0,0 +1,38 @@ |
| 1 | + |
|
| 2 | +# airplane-dat |
|
| 3 | + |
|
| 4 | +## Channel 1: Aileron Action |
|
| 5 | + |
|
| 6 | +Control theright-and-left lean of the aircraft.To level the slantwise aircraft,youmust make |
|
| 7 | +thecontrol rod act inreverse direction.Otherwise,it will makethe aircraftoverturn. |
|
| 8 | + |
|
| 9 | +## Channel 2: Elevator Action |
|
| 10 | + |
|
| 11 | +Control the aerocraft to descend orascend.Pulling the control rod down will driveup the head, |
|
| 12 | +and the aeroplane will ascend.Boosting it upwill make thehead downhill,and the aeroplane |
|
| 13 | +willdescend. |
|
| 14 | + |
|
| 15 | +## Channel 3: Throttle Operation |
|
| 16 | + |
|
| 17 | +Control the power. Pulling the control rod down will minish down the power group, and boosting |
|
| 18 | +the control rod up will increase thepower group. |
|
| 19 | + |
|
| 20 | +## Channel 4: Rudder Action |
|
| 21 | + |
|
| 22 | +Control the swerve of the aerocraft. Turning the control rod to left will make the head of the |
|
| 23 | +aircraft turn left, and turning it to right will make the head turn right. |
|
| 24 | + |
|
| 25 | +## Channel 5: LandingGear/GyroAction |
|
| 26 | + |
|
| 27 | +This channel is for switch variable. It is a switch to control landing gear when used for airplane |
|
| 28 | +state, but it will be a switch for gyroscope when used for helicopter. |
|
| 29 | + |
|
| 30 | +## Channel 6: Screw-pitch/Flaperon Action |
|
| 31 | + |
|
| 32 | +The angle adjustingof the flaperon isfor the airplane state,and the adjustingof themain |
|
| 33 | +screw-pitch is forhelicopter state. |
|
| 34 | + |
|
| 35 | + |
|
| 36 | +## ref |
|
| 37 | + |
|
| 38 | +- [[RC-dat]] - [[airplane]] - [[RC]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/betaFPV-dat/2025-05-04-14-49-45.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/betaFPV-dat/2025-05-04-14-49-45.png differ |
app-dat/RC-dat/betaFPV-dat/2025-05-04-15-34-48.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/betaFPV-dat/2025-05-04-15-34-48.png differ |
app-dat/RC-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/RC-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 | + |
|
| 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 | + |
|
| 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 |
app-dat/RC-dat/flight-controller-dat/flight-controller-dat.md
| ... | ... | @@ -0,0 +1,3 @@ |
| 1 | + |
|
| 2 | +# flight-controller-dat |
|
| 3 | + |
app-dat/RC-dat/quadcopter-dat/2025-01-29-17-12-32.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/quadcopter-dat/2025-01-29-17-12-32.png differ |
app-dat/RC-dat/quadcopter-dat/FPV-dat/2025-04-02-12-45-53.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/quadcopter-dat/FPV-dat/2025-04-02-12-45-53.png differ |
app-dat/RC-dat/quadcopter-dat/FPV-dat/2025-04-02-13-14-05.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/quadcopter-dat/FPV-dat/2025-04-02-13-14-05.png differ |
app-dat/RC-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/FPV-controller-dat.md
| ... | ... | @@ -0,0 +1,13 @@ |
| 1 | + |
|
| 2 | +# FPV-receiver-dat |
|
| 3 | + |
|
| 4 | +- [[ELRS-dat]] - [[TBS-dat]] |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +## DJI |
|
| 8 | + |
|
| 9 | +- [DJI FPV Remote Controller 3](https://www.amazon.com/DJI-FPV-Remote-Controller-Compatibility/dp/B0CS6JCX2W/ref=sr_1_3?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-3) |
|
| 10 | + |
|
| 11 | +- [DJI RC Motion 3, FPV Smart Controller with Immersive Motion Control, Compact and Portable, One-Click Emergency Brake, AR Cursor, Intuitive Drone Controller, Multi-Model Compatibility](https://www.amazon.com/DJI-Controller-Immersive-Multi-Model-Compatibility/dp/B0CS6LDCKC/ref=sr_1_11?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-11) |
|
| 12 | + |
|
| 13 | + |
app-dat/RC-dat/quadcopter-dat/FPV-dat/FPV-dat.md
| ... | ... | @@ -0,0 +1,208 @@ |
| 1 | + |
|
| 2 | +# FPV-dat |
|
| 3 | + |
|
| 4 | +- [[quadcopter-dat]] |
|
| 5 | + |
|
| 6 | +- [[FPV-controller-dat]] - [[Goggles-dat]] |
|
| 7 | + |
|
| 8 | +- [[ELRS-dat]] - [[FrSky-dat]] - [[ArduPilot-dat]] - [[CRSF-dat]] |
|
| 9 | + |
|
| 10 | +- [[BMS-dat]] |
|
| 11 | + |
|
| 12 | + |
|
| 13 | + |
|
| 14 | +## parts of the FPV drones |
|
| 15 | + |
|
| 16 | +- **Flight Controller**: The brain of the drone, responsible for stabilizing and controlling the flight. It processes data from sensors and executes commands from the pilot or autopilot system. |
|
| 17 | + |
|
| 18 | +- **Electronic Speed Controller (ESC)**: Controls the speed of the motors by adjusting the power supplied to them. ESCs are essential for smooth and responsive flight. |
|
| 19 | + |
|
| 20 | +- **Motors**: Provide the thrust needed for flight. Brushless motors are commonly used in FPV drones due to their efficiency and power. |
|
| 21 | + |
|
| 22 | +- **Propellers**: Generate lift by spinning rapidly. The size and pitch of the propellers can significantly affect the drone's performance and flight characteristics. |
|
| 23 | + |
|
| 24 | + - [[SCU1059-dat]] |
|
| 25 | + |
|
| 26 | +- **Camera**: Captures real-time video for FPV flying. FPV cameras are designed to provide low-latency video transmission to the pilot's goggles or screen. |
|
| 27 | + |
|
| 28 | +- [[VTX-dat]]: Video Transmitters are commonly referred to as VTX units. They are responsible for transmitting the video signal from the camera to the pilot's goggles or screen. VTX units come in various power levels and frequencies, allowing pilots to choose the best option for their flying environment. |
|
| 29 | +- **Antenna**: Enhances the signal strength and range of the VTX. Different antenna types (e.g., dipole, patch, circular polarized) can be used to optimize performance. |
|
| 30 | + |
|
| 31 | +- **ExpressLRS**: A long-range radio control link for FPV drones, known for its low latency and high refresh rates. It is an open-source project that competes with other systems like Crossfire and ELRS. |
|
| 32 | + |
|
| 33 | + - [[ELRS-dat]] |
|
| 34 | + |
|
| 35 | +- **Goggles**: Wearable displays that allow pilots to see the live video feed from the drone's camera. They often include features like head tracking and DVR (Digital Video Recorder) capabilities. |
|
| 36 | + |
|
| 37 | + |
|
| 38 | + |
|
| 39 | + |
|
| 40 | + |
|
| 41 | +## Bee35 |
|
| 42 | + |
|
| 43 | + |
|
| 44 | + |
|
| 45 | + |
|
| 46 | + |
|
| 47 | + |
|
| 48 | +| version | price | description | |
|
| 49 | +| -------------------------- | ----- | ------------------------------------- | |
|
| 50 | +| Bee35 Pro O3 Air Unit TBS | 480 | O3 Air Unit, TBS radio | |
|
| 51 | +| Bee35 Pro O3 Air Unit ELRS | 470 | O3 Air Unit, ELRS radio | |
|
| 52 | +| Bee35 Pro O3 Air Unit PNP | 460 | O3 Air Unit, no receiver | |
|
| 53 | +| Bee35 Pro | 270 | Standard analog version | |
|
| 54 | +| Bee35 Pro LINK WASP TBS | 430 | LINK WASP digital system, TBS radio | |
|
| 55 | +| Bee35 Pro LINK WASP ELRS | 420 | LINK WASP digital system, ELRS radio | |
|
| 56 | +| Bee35 Pro LINK WASP PNP | 400 | LINK WASP digital system, no receiver | |
|
| 57 | +| Bee35 Analog TBS | 306 | Analog FPV system, TBS radio | |
|
| 58 | +| Bee35 Analog ELRS | 296 | Analog FPV system, ELRS radio | |
|
| 59 | + |
|
| 60 | + |
|
| 61 | + |
|
| 62 | +## commerialized FPV |
|
| 63 | + |
|
| 64 | +- [[speedybee-dat]] |
|
| 65 | + |
|
| 66 | +### 1. [SpeedyBee Flight Controllers & Stacks](https://speedybee.com/) |
|
| 67 | +- **Brand:** SpeedyBee |
|
| 68 | +- **Description:** Budget-friendly, Betaflight-supported flight controllers with easy app-based tuning. |
|
| 69 | +- **Example Products:** |
|
| 70 | + - **SpeedyBee F405 V4 Stack** (F4-based, affordable) |
|
| 71 | + - **SpeedyBee F7 V3 Stack** (F7-based, powerful & feature-rich) |
|
| 72 | +- **Commercial Features:** |
|
| 73 | + - Wireless **Bluetooth & Wi-Fi tuning** via SpeedyBee app. |
|
| 74 | + - Fully compatible with Betaflight Configurator. |
|
| 75 | +- **Website:** [speedybee.com](https://speedybee.com/) |
|
| 76 | + |
|
| 77 | +--- |
|
| 78 | + |
|
| 79 | +### 2. [TBS Tango 2 (Crossfire-Integrated Radio Controller)](https://www.team-blacksheep.com/) |
|
| 80 | +- **Brand:** Team BlackSheep (TBS) |
|
| 81 | +- **Description:** A high-performance FPV radio transmitter designed for **Betaflight-based drones** with **built-in Crossfire**. |
|
| 82 | +- **Commercial Features:** |
|
| 83 | + - Fully optimized for **Betaflight & Crossfire**. |
|
| 84 | + - Compact, ergonomic design for FPV pilots. |
|
| 85 | +- **Website:** [team-blacksheep.com](https://www.team-blacksheep.com/) |
|
| 86 | + |
|
| 87 | + |
|
| 88 | +## opensource control projects |
|
| 89 | + |
|
| 90 | +# Most Famous Open-Source FPV GitHub Projects |
|
| 91 | + |
|
| 92 | +If you're looking for **open-source FPV (First-Person View) projects** on GitHub, here are some of the **most famous** ones: |
|
| 93 | + |
|
| 94 | +## 1. [Betaflight](https://github.com/betaflight/betaflight) |
|
| 95 | +- **Description:** One of the most widely used open-source flight control firmware for FPV drones. |
|
| 96 | +- **Features:** |
|
| 97 | + - Highly optimized for **acrobatic** and **racing drones**. |
|
| 98 | + - Supports a wide range of flight controllers. |
|
| 99 | + - Advanced **tuning options** for PID, filters, and motor control. |
|
| 100 | +- **GitHub:** [github.com/betaflight/betaflight](https://github.com/betaflight/betaflight) |
|
| 101 | + |
|
| 102 | +--- |
|
| 103 | + |
|
| 104 | +## 2. [iNavFlight](https://github.com/iNavFlight/inav) |
|
| 105 | +- **Description:** A fork of Betaflight, but optimized for **GPS and long-range FPV**. |
|
| 106 | +- **Features:** |
|
| 107 | + - Supports **GPS waypoint navigation, return-to-home (RTH), and mission planning**. |
|
| 108 | + - Designed for **freestyle and long-range cruising** rather than racing. |
|
| 109 | +- **GitHub:** [github.com/iNavFlight/inav](https://github.com/iNavFlight/inav) |
|
| 110 | + |
|
| 111 | +--- |
|
| 112 | + |
|
| 113 | +## 3. [ArduPilot](https://github.com/ArduPilot/ardupilot) |
|
| 114 | +- **Description:** A professional-grade open-source autopilot for drones, including **FPV quadcopters, planes, and rovers**. |
|
| 115 | +- **Features:** |
|
| 116 | + - **Highly autonomous** with advanced mission planning. |
|
| 117 | + - Works with multiple types of vehicles (planes, multirotors, helicopters). |
|
| 118 | + - Compatible with **Mission Planner** and **QGroundControl**. |
|
| 119 | +- **GitHub:** [github.com/ArduPilot/ardupilot](https://github.com/ArduPilot/ardupilot) |
|
| 120 | + |
|
| 121 | +--- |
|
| 122 | + |
|
| 123 | +## 4. [PX4](https://github.com/PX4/PX4-Autopilot) |
|
| 124 | +- **Description:** A powerful open-source **flight control software** used in drones and FPV systems. |
|
| 125 | +- **Features:** |
|
| 126 | + - Supports both **FPV racing drones** and **autonomous UAVs**. |
|
| 127 | + - Works with Pixhawk flight controllers and supports **ROS (Robot Operating System)**. |
|
| 128 | +- **GitHub:** [github.com/PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) |
|
| 129 | + |
|
| 130 | +--- |
|
| 131 | + |
|
| 132 | +## 5. [FalcoX](https://github.com/FlightOne/FalcoX) |
|
| 133 | +- **Description:** An alternative FPV flight control firmware focusing on **ease of use and smooth flight performance**. |
|
| 134 | +- **Features:** |
|
| 135 | + - Intuitive configuration interface. |
|
| 136 | + - Aimed at both **freestyle pilots** and **racers**. |
|
| 137 | +- **GitHub:** [github.com/FlightOne/FalcoX](https://github.com/FlightOne/FalcoX) |
|
| 138 | + |
|
| 139 | +--- |
|
| 140 | + |
|
| 141 | +## 6. [ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) |
|
| 142 | +- **Description:** Open-source long-range **radio control link** for FPV drones, competing with Crossfire and ELRS. |
|
| 143 | +- **Features:** |
|
| 144 | + - **Low latency and high refresh rates** (great for FPV racing). |
|
| 145 | + - Compatible with many radio transmitters (TBS, Jumper, Radiomaster). |
|
| 146 | +- **GitHub:** [github.com/ExpressLRS/ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) |
|
| 147 | + |
|
| 148 | +--- |
|
| 149 | + |
|
| 150 | +## 7. [OpenHD](https://github.com/OpenHD/OpenHD) |
|
| 151 | +- **Description:** Open-source **HD video transmission** for FPV drones (alternative to DJI HD systems). |
|
| 152 | +- **Features:** |
|
| 153 | + - Uses **Raspberry Pi + WiFi** for HD FPV video streaming. |
|
| 154 | + - Supports OSD (On-Screen Display) and telemetry data. |
|
| 155 | +- **GitHub:** [github.com/OpenHD/OpenHD](https://github.com/OpenHD/OpenHD) |
|
| 156 | + |
|
| 157 | +--- |
|
| 158 | + |
|
| 159 | +## 🔥 Which One Should You Choose? |
|
| 160 | +| Purpose | Best Open-Source Project | |
|
| 161 | +| ------------------------------------------- | ------------------------------------------------------ | |
|
| 162 | +| **Racing/Freestyle FPV** | [Betaflight](https://github.com/betaflight/betaflight) | |
|
| 163 | +| **GPS & Long-Range FPV** | [iNav](https://github.com/iNavFlight/inav) | |
|
| 164 | +| **Full Autopilot (Drones, Planes, Rovers)** | [ArduPilot](https://github.com/ArduPilot/ardupilot) | |
|
| 165 | +| **Professional UAVs & Research** | [PX4](https://github.com/PX4/PX4-Autopilot) | |
|
| 166 | +| **HD FPV Video Streaming** | [OpenHD](https://github.com/OpenHD/OpenHD) | |
|
| 167 | +| **Long-Range Radio Links** | [ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) | |
|
| 168 | + |
|
| 169 | + |
|
| 170 | + |
|
| 171 | +## standards |
|
| 172 | + |
|
| 173 | +### PNP stands for "Plug and Play." |
|
| 174 | + |
|
| 175 | +In the context of FPV drones, a PNP version means that the drone comes mostly assembled but does not include a radio receiver. |
|
| 176 | + |
|
| 177 | +Here's why it doesn't include a receiver: |
|
| 178 | + |
|
| 179 | +Flexibility: PNP versions cater to experienced FPV pilots who already have their preferred radio transmitter and receiver. This allows them to use their existing equipment and avoid paying for redundant components. |
|
| 180 | +Customization: Pilots might have specific receiver requirements based on their radio system (e.g., TBS Crossfire, ELRS, FrSky). Offering a PNP version lets them choose the exact receiver that's compatible with their setup. |
|
| 181 | +Cost Savings: By excluding the receiver, the manufacturer can offer the PNP version at a lower price point, making it attractive to those who don't need the included receiver. |
|
| 182 | +In short, PNP versions are designed for users who want to use their own radio gear and prefer to avoid unnecessary costs or compatibility issues. |
|
| 183 | + |
|
| 184 | + |
|
| 185 | + |
|
| 186 | +## popular products |
|
| 187 | + |
|
| 188 | +DJI |
|
| 189 | + |
|
| 190 | +- [DJI Avata 2 (Drone Only), FPV Drone with Camera 4K, Immersive Flight Experience, Built-in Propeller Guard, Easy Flip/Roll, Super-Wide 155° FOV, Compatible with RC Motion 3, FAA Remote ID Compliant](https://www.amazon.com/DJI-Immersive-Experience-Super-Wide-Compatible/dp/B0CS6KY96F/ref=sr_1_45?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-45) |
|
| 191 | + |
|
| 192 | +BetaFPV |
|
| 193 | + |
|
| 194 | +- [BETAFPV Betaflight ELRS V3 Cetus X FPV Kit with LiteRadio 3 Transmitter C04 Camera VR03 Goggles with DVR Recording Function, Supported 2S Power Advanced RTF Kit for FPV Beginners to Fly Faster Further](https://www.amazon.com/BETAFPV-LiteRadio-Transmitter-Recording-Betaflight/dp/B0BJVP3XW7/ref=sr_1_48?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-48) == rating == 3.5 |
|
| 195 | + |
|
| 196 | +- [BETAFPV Pavo20 Brushless Whoop Quadcopter with HD Digital Bracket for O3 Air Unit, F4 2-3S 20A FC, 1103 8500KV Motor, COB LED Strip, Compatible for FPV Racing Indoor and Outdoor](https://www.amazon.com/BETAFPV-Brushless-Quadcopter-Material-Compatible/dp/B0CKT5G6C1/ref=sr_1_11?crid=1KCLBGZLCPWMM&dib=eyJ2IjoiMSJ9.u8zpDMqhQLF9cnPbc5r76LO9SVPJiVyPzTq0xdtVa2u4UYSXdyYl9H-Z3gMzqguhRBkKgkoRZWaxBHDFD6BRFsCQJKVb4iWibNm9DVSzo8jjnyx10jKEMfQICYMtZJab4CpDzmZXALE0VqfYmsl2b2z6zA536zmhj3MbQfvXxqOrlO8RzQiYLdFv-lIZbHe3VqkD5N2AuBL25TgOETuGrMPmYt7Yhvu1G4lry067nFXe06m0NOi7YGC9HehoblQsTDd1-4IPkuJfZGdR6OljCFD_F9mIqaJ-dIPMlULs8kg.m1NOD5DB1dn9oAtRj6kjXh5UkWTCRb94gNjUZ8Owz8Y&dib_tag=se&keywords=betafpv&qid=1744202445&sprefix=beta%2Caps%2C676&sr=8-11) == rating == 4.1 |
|
| 197 | + |
|
| 198 | + |
|
| 199 | +SpeedyBee Frame |
|
| 200 | + |
|
| 201 | +- [Speedy Bee Bee35 3.5inch Cinewhoop FPV Drone Frame- Pro Version 4S 6S Frame Kit Compatible with DJI O3 Air Unit FPV VTX,Different Flight Controller Stack](https://www.amazon.com/3-5inch-Cinewhoop-Compatible-Different-Controller/dp/B086X5M24H/ref=sr_1_1?dib=eyJ2IjoiMSJ9.flOlB5a6W8Z4mxOLR-K_BDlWDFVnqHJ69LrRLHzsG3Vt1_EuF1CQCJw-erVA1bWn.aK6G-MxmMYmSkACuczQuR4yI0PIn2BzHbY4-bbiXRLo&dib_tag=se&keywords=bee35&qid=1744202041&sr=8-1) |
|
| 202 | + |
|
| 203 | + |
|
| 204 | + |
|
| 205 | + |
|
| 206 | +## ref |
|
| 207 | + |
|
| 208 | +- [[FPV]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/quadcopter-dat/FPV-dat/FPV-simulation-dat/FPV-simulation-dat.md
| ... | ... | @@ -0,0 +1,88 @@ |
| 1 | + |
|
| 2 | +# FPV-simulation-dat |
|
| 3 | + |
|
| 4 | +## Popular FPV Simulators for PC |
|
| 5 | + |
|
| 6 | +| Simulator | Highlights | Price | |
|
| 7 | +| ------------- | ---------------------------------------------------------- | ----- | |
|
| 8 | +| Liftoff | Realistic physics, good for racing & freestyle | ~$20 | |
|
| 9 | +| VelociDrone | Excellent feel, popular for competition practice | ~$20 | |
|
| 10 | +| DRL Simulator | Based on the Drone Racing League, includes tracks & events | ~$10 | |
|
| 11 | +| Uncrashed | Stunning graphics, smooth flying | ~$15 | |
|
| 12 | +| FPV Freerider | Lightweight, good for low-end PCs | ~$5 | |
|
| 13 | + |
|
| 14 | + |
|
| 15 | + |
|
| 16 | +## Compatible Controllers |
|
| 17 | + |
|
| 18 | +- RadioMaster TX16S |
|
| 19 | +- FrSky Taranis QX7 / X9D |
|
| 20 | +- BetaFPV LiteRadio |
|
| 21 | +- DJI FPV controller (works with some sims) |
|
| 22 | +- Most transmitters that support USB or simulator mode |
|
| 23 | + |
|
| 24 | + |
|
| 25 | + |
|
| 26 | +## 🆓 Free or Open Source FPV Simulators for PC |
|
| 27 | + |
|
| 28 | +### 🛠 FPV.Skydive (from ORQA) |
|
| 29 | +- ✅ Free on Steam |
|
| 30 | +- 🧠 Beginner-friendly with training modules |
|
| 31 | +- 🎮 Supports many controllers (via USB) |
|
| 32 | +- 📦 Good for freestyle and basic racing |
|
| 33 | +- ❗ Not open-source, but completely free |
|
| 34 | +- 🔗 [Steam Link](https://store.steampowered.com/app/1645840/FPV_Skydive/) |
|
| 35 | + |
|
| 36 | +https://store.steampowered.com/app/1278060/FPV_SkyDive__FPV_Drone_Simulator/ |
|
| 37 | + |
|
| 38 | +--- |
|
| 39 | + |
|
| 40 | +### 🛠 RotorHazard Simulator |
|
| 41 | +- ⚙️ Community-developed simulator inspired by RotorHazard timing system |
|
| 42 | +- 🖥 Lightweight, browser-based or local |
|
| 43 | +- 💻 Not super polished, but interesting for DIY folks |
|
| 44 | +- 🌐 Open-source (GitHub available) |
|
| 45 | +- 🔗 [GitHub Repository](https://github.com/RotorHazard) |
|
| 46 | + |
|
| 47 | +--- |
|
| 48 | + |
|
| 49 | +### 🛠 OpenFPV Simulator (dead?) |
|
| 50 | +- 🌍 Browser-based prototype sim |
|
| 51 | +- 👶 Very basic physics and controls |
|
| 52 | +- 🧑💻 Open-source, you can fork or contribute |
|
| 53 | +- 🔧 Good for devs/hackers/experimenters |
|
| 54 | +- 🔗 [GitHub Link](https://github.com/OpenFPV/openfpv-simulator) |
|
| 55 | + |
|
| 56 | +--- |
|
| 57 | + |
|
| 58 | +### 🛠 Multirotor Sim (Unity-based) (dead?) |
|
| 59 | +- 🧪 Community project with editable Unity source |
|
| 60 | +- 🎮 Supports USB controllers |
|
| 61 | +- 🔧 Needs a bit of setup, but can be modified freely |
|
| 62 | +- 🔗 [GitHub Link](https://github.com/ArduPilot/multirotor_sim) |
|
| 63 | + |
|
| 64 | +--- |
|
| 65 | + |
|
| 66 | +### 📌 Honorable Mentions (Free Trials or Demos) |
|
| 67 | + |
|
| 68 | +#### **FPV Freerider (Demo version)** |
|
| 69 | +- Limited map, but physics work well |
|
| 70 | +- 🔗 [freeriderfpv.com](https://fpv-freerider.itch.io/fpv-freerider-recharged-demo) |
|
| 71 | + |
|
| 72 | +--- |
|
| 73 | + |
|
| 74 | +### 🧭 Recommendation |
|
| 75 | + |
|
| 76 | +- **If you're new and want a polished free experience:** |
|
| 77 | + ➡️ Try **[FPV.Skydive](https://store.steampowered.com/app/1645840/FPV_Skydive/)** |
|
| 78 | + |
|
| 79 | +- **If you're into tinkering or want to code your own sim:** |
|
| 80 | + ➡️ Check out **OpenFPV** or **Multirotor Sim** on GitHub |
|
| 81 | + |
|
| 82 | + |
|
| 83 | + |
|
| 84 | + |
|
| 85 | +## ref |
|
| 86 | + |
|
| 87 | + |
|
| 88 | +- [[FPV-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/quadcopter-dat/FPV-dat/Goggles-dat/Goggles-dat.md
| ... | ... | @@ -0,0 +1,7 @@ |
| 1 | + |
|
| 2 | +# Goggles-dat |
|
| 3 | + |
|
| 4 | +[DJI Goggles 3, FPV Goggles with Stunning Micro-OLED Screens, Immersive Flight Experience, O4 HD Video Transmission, Adjustable Diopters, Wireless Streaming, Drone Goggles with Real View PiP](https://www.amazon.com/DJI-Micro-OLED-Experience-Transmission-Adjustable/dp/B0CS6L6D6J/ref=sr_1_17?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-17) |
|
| 5 | + |
|
| 6 | + |
|
| 7 | +[Fat Shark Recon Echo FPV Goggles](https://www.amazon.com/Fat-Shark-Recon-Echo-Goggles/dp/B0CTB8VLYQ/ref=sr_1_41?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-41) |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/quadcopter-dat/quadcopter-dat.md
| ... | ... | @@ -0,0 +1,65 @@ |
| 1 | + |
|
| 2 | +# quadcopter-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## opensource |
|
| 6 | + |
|
| 7 | +### cleanfight |
|
| 8 | + |
|
| 9 | +https://github.com/cleanflight/cleanflight |
|
| 10 | + |
|
| 11 | +https://github.com/cleanflight/cleanflight/tree/master/docs |
|
| 12 | + |
|
| 13 | +https://cleanflight.com/ |
|
| 14 | + |
|
| 15 | + |
|
| 16 | +### Openpilot |
|
| 17 | + |
|
| 18 | +## Commerial |
|
| 19 | + |
|
| 20 | +### CJMCU |
|
| 21 | + |
|
| 22 | + |
|
| 23 | + |
|
| 24 | +- https://www.rcgroups.com/forums/showthread.php?2456739-Openpilot-port-to-CJMCU-stm32-quadcopter |
|
| 25 | + |
|
| 26 | +- https://oscarliang.com/build-fpv-micro-quadcopter-smallest-quad/ |
|
| 27 | + |
|
| 28 | +#### new version from https://aeracoop.net/cjmcu2-open-source-brushed-quadcopter/ |
|
| 29 | + |
|
| 30 | +https://github.com/Edragon/cjmcu2 |
|
| 31 | + |
|
| 32 | + |
|
| 33 | + |
|
| 34 | +## BOM |
|
| 35 | + |
|
| 36 | +### receiver |
|
| 37 | + |
|
| 38 | +- [DT 2.4GHz Receivers](https://www.deltang.co.uk/) |
|
| 39 | + |
|
| 40 | + |
|
| 41 | + |
|
| 42 | +### props |
|
| 43 | + |
|
| 44 | + |
|
| 45 | +### motors |
|
| 46 | + |
|
| 47 | + |
|
| 48 | +### motor drive |
|
| 49 | + |
|
| 50 | +- [[mosfet-dat]] |
|
| 51 | + |
|
| 52 | +## forum |
|
| 53 | + |
|
| 54 | +- http://www.multiwii.com/forum |
|
| 55 | +- https://www.rcgroups.com/forums |
|
| 56 | + |
|
| 57 | + |
|
| 58 | + |
|
| 59 | +## hexquadcopter |
|
| 60 | + |
|
| 61 | +- http://www.multiwii.com/forum/viewtopic.php?f=12&t=4893&p=53317#p53317 |
|
| 62 | + |
|
| 63 | +## ref |
|
| 64 | + |
|
| 65 | +- [[quadcopter]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-00-18.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-00-18.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-00-49.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-00-49.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-01-11.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-01-11.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-02-19.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-25-15-02-19.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-28-18-44-53.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/2025-03-28-18-44-53.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/RC-car-dat.md
| ... | ... | @@ -0,0 +1,49 @@ |
| 1 | + |
|
| 2 | +# RC-car-dat |
|
| 3 | + |
|
| 4 | +- [[video-RC-car-dat]] |
|
| 5 | + |
|
| 6 | +basic [[tech-dat]] - [[robot-dat]] |
|
| 7 | + |
|
| 8 | + |
|
| 9 | + |
|
| 10 | +## Tracked robot platform |
|
| 11 | + |
|
| 12 | + |
|
| 13 | + |
|
| 14 | + |
|
| 15 | + |
|
| 16 | + |
|
| 17 | + |
|
| 18 | + |
|
| 19 | + |
|
| 20 | + |
|
| 21 | +## tricycle / four-wheels platform |
|
| 22 | + |
|
| 23 | + |
|
| 24 | + |
|
| 25 | +tricycle |
|
| 26 | + |
|
| 27 | +Four-wheel two-drive car |
|
| 28 | + |
|
| 29 | +Four-wheel drive car |
|
| 30 | + |
|
| 31 | +Omnidirectional four-wheel two-wheel drive car |
|
| 32 | + |
|
| 33 | + |
|
| 34 | +## other |
|
| 35 | + |
|
| 36 | +### robot tank with camera |
|
| 37 | + |
|
| 38 | +- https://github.com/YahboomTechnology/Raspberry-pi-G1-Tank |
|
| 39 | + |
|
| 40 | + |
|
| 41 | +## read |
|
| 42 | + |
|
| 43 | +- [Tear down and Learn a good-build $20 RC Toy Car](https://www.electrodragon.com/disassemble-and-learn-a-good-build-20-rc-toy-car/) |
|
| 44 | + |
|
| 45 | +## ref |
|
| 46 | + |
|
| 47 | +- [[motor-dat]] |
|
| 48 | + |
|
| 49 | +- [[RC-car]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/rover-dat/rc-car-dat/rc-car-hack-dat/rc-car-hack-dat.md
| ... | ... | @@ -0,0 +1,26 @@ |
| 1 | + |
|
| 2 | +# rc-car-hack-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +## 1. battery Enlargement |
|
| 6 | + |
|
| 7 | +- [[lithium-battery-dat]] |
|
| 8 | + |
|
| 9 | +## 2. RC Signal Extension |
|
| 10 | + |
|
| 11 | +- improve up to 10KM by [[FPV-dat]] system [[ELRS-dat]] |
|
| 12 | + |
|
| 13 | +- [[antenna-dat]] |
|
| 14 | + |
|
| 15 | +- control system - try to hack by [[arduino-dat]] |
|
| 16 | + |
|
| 17 | +## 3. Imaging System |
|
| 18 | + |
|
| 19 | +- [[video-transmission-dat]] == pickup option == [[LTE-dat]] |
|
| 20 | + |
|
| 21 | + |
|
| 22 | + |
|
| 23 | + |
|
| 24 | +## 4. GNSS location system |
|
| 25 | + |
|
| 26 | +- [[location-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-43-46.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-43-46.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-48-15.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-48-15.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-48-28.png
| ... | ... | Binary files /dev/null and b/app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/2025-03-25-14-48-28.png differ |
app-dat/RC-dat/rover-dat/rc-car-dat/video-rc-car-dat/video-RC-car-dat.md
| ... | ... | @@ -0,0 +1,36 @@ |
| 1 | + |
|
| 2 | +# video-RC-car-dat |
|
| 3 | + |
|
| 4 | + |
|
| 5 | +[[tech-dat]] - [[Camera-dat]] - [[rc-car-dat]] - [[video-transmission-dat]] - [[robot-dat]] |
|
| 6 | + |
|
| 7 | +- [[rc-car-hack-dat]] |
|
| 8 | + |
|
| 9 | +## Demos |
|
| 10 | + |
|
| 11 | +### based on cable [[fiber-optic-dat]] |
|
| 12 | + |
|
| 13 | +#### demos 1 |
|
| 14 | + |
|
| 15 | +up to 100 meters |
|
| 16 | + |
|
| 17 | + |
|
| 18 | + |
|
| 19 | + |
|
| 20 | + |
|
| 21 | + |
|
| 22 | + |
|
| 23 | + |
|
| 24 | +#### demo video 2 |
|
| 25 | + |
|
| 26 | +- https://t.me/electrodragon3/334 |
|
| 27 | + |
|
| 28 | +### Wireless |
|
| 29 | + |
|
| 30 | +- [[video-transmission-dat]] |
|
| 31 | + |
|
| 32 | +## ref |
|
| 33 | + |
|
| 34 | +- [[video-RC-car]] - [[RC-car]] - [[video-transmission]] |
|
| 35 | + |
|
| 36 | +- [[camera]] |
|
| ... | ... | \ No newline at end of file |
app-dat/RC-dat/speedybee-dat/speedybee-dat.md
| ... | ... | @@ -0,0 +1,7 @@ |
| 1 | + |
|
| 2 | +# speedybee-dat |
|
| 3 | + |
|
| 4 | +[SpeedyBee 4pcs FPV Soldering Practice Board for FPV Drone Beginners, Tools for Flight controller ESC Soldering Practice](https://www.amazon.com/SpeedyBee-Soldering-Practice-Beginners-controller/dp/B0C5X26JWQ/ref=sr_1_32?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-32) |
|
| 5 | + |
|
| 6 | + |
|
| 7 | + |
app-dat/UAV-dat/UAV-dat.md
| ... | ... | @@ -1,46 +0,0 @@ |
| 1 | - |
|
| 2 | -# UAV-dat |
|
| 3 | - |
|
| 4 | -A UAV stands for Unmanned Aerial Vehicle. It's an aircraft without a human pilot on board, controlled remotely or autonomously. They are also commonly known as drones. |
|
| 5 | - |
|
| 6 | -- [[betaflight-dat]] - [[ArduPilot-dat]] |
|
| 7 | - |
|
| 8 | -- [[FPV-dat]] |
|
| 9 | - |
|
| 10 | - |
|
| 11 | - |
|
| 12 | -## fixed-wing UAV |
|
| 13 | - |
|
| 14 | -### Talon 1400 Overview |
|
| 15 | - |
|
| 16 | -#### What is the Talon 1400? |
|
| 17 | -The **Talon 1400** is a high-performance, **3D-printed unmanned aerial vehicle (UAV)** developed by Flightory. It is optimized for long-range and efficient flight. |
|
| 18 | - |
|
| 19 | -##### Specifications: |
|
| 20 | -- **Wingspan:** 1,305 mm |
|
| 21 | -- **Length:** 830 mm |
|
| 22 | -- **Flight Time:** Up to 4 hours (with large Li-Ion 4S6P battery) |
|
| 23 | -- **Materials:** LW-PLA and PETG |
|
| 24 | -- **Airfoil:** Eppler E205 |
|
| 25 | -- **Optimal Cruise Speed:** 55-65 km/h |
|
| 26 | - |
|
| 27 | -#### Is It Betaflight-Based? |
|
| 28 | - |
|
| 29 | -**No**, the Talon 1400 is **not** based on Betaflight. Since it is a **fixed-wing UAV**, it is more suited for **autonomous flight controllers** rather than Betaflight, which is designed for FPV racing drones. |
|
| 30 | - |
|
| 31 | -##### Recommended Flight Controllers: |
|
| 32 | - |
|
| 33 | -- **Mateksys F405-Wing / F765-Wing** |
|
| 34 | -- **Pixhawk (PX4 or ArduPilot firmware)** |
|
| 35 | -- **Holybro Kakute F7 / H743-Wing** |
|
| 36 | - |
|
| 37 | -These controllers support **GPS navigation, waypoint missions, and return-to-home (RTH)**, making them better suited for long-range operations. |
|
| 38 | - |
|
| 39 | -#### Resources: |
|
| 40 | - |
|
| 41 | -- [Flying a 3D Printed Fixed Wing Drone | Talon 1400 V2](https://www.youtube.com/watch?v=2ngGgtw1sUw) |
|
| 42 | - |
|
| 43 | -- [Flightory Talon 1400 Official Page](https://flightory.com/product/talon-1400/) |
|
| 44 | -- [Talon 1400 Assembly Tutorial (YouTube)](https://www.youtube.com/watch?v=LGt_8F4e5r8) |
|
| 45 | - |
|
| 46 | - |
app-dat/UAV-dat/betaflight-dat.md
| ... | ... | @@ -1,31 +0,0 @@ |
| 1 | - |
|
| 2 | - |
|
| 3 | -# betaflight-dat.md |
|
| 4 | - |
|
| 5 | -Betaflight is an open-source firmware for drones and other unmanned aerial vehicles (UAVs). It is designed to provide advanced flight control capabilities, making it popular among hobbyists and enthusiasts in the drone community. Betaflight is known for its flexibility, configurability, and support for a wide range of hardware platforms. |
|
| 6 | - |
|
| 7 | -- [[FPV-dat]] |
|
| 8 | - |
|
| 9 | - |
|
| 10 | - |
|
| 11 | - |
|
| 12 | - |
|
| 13 | -## commerlized projects |
|
| 14 | - |
|
| 15 | -- **speedybee** == https://www.speedybee.com/ == SpeedyBee is a company that specializes in providing high-quality drone components and accessories, including flight controllers, ESCs, and other related products. They are known for their innovative designs and user-friendly interfaces, making them a popular choice among drone enthusiasts. |
|
| 16 | -- **betafpv** == https://www.betafpv.com/ == BETAFPV is a company that focuses on producing small and lightweight drones, particularly for FPV (First Person View) racing and freestyle flying. They offer a range of products, including flight controllers, cameras, and other accessories tailored for FPV enthusiasts. |
|
| 17 | -- happymodel |
|
| 18 | -- iFlight |
|
| 19 | -- Holybro |
|
| 20 | -- TBS |
|
| 21 | -- Flywoo |
|
| 22 | -- HGLRC |
|
| 23 | -- Diatone |
|
| 24 | -- GepRC |
|
| 25 | -- Racerstar |
|
| 26 | -- Emax |
|
| 27 | -- Eachine |
|
| 28 | -- HGLRC |
|
| 29 | -- Racerstar |
|
| 30 | - |
|
| 31 | - |
app-dat/airplane-dat/airplane-dat.md
| ... | ... | @@ -1,38 +0,0 @@ |
| 1 | - |
|
| 2 | -# airplane-dat |
|
| 3 | - |
|
| 4 | -## Channel 1: Aileron Action |
|
| 5 | - |
|
| 6 | -Control theright-and-left lean of the aircraft.To level the slantwise aircraft,youmust make |
|
| 7 | -thecontrol rod act inreverse direction.Otherwise,it will makethe aircraftoverturn. |
|
| 8 | - |
|
| 9 | -## Channel 2: Elevator Action |
|
| 10 | - |
|
| 11 | -Control the aerocraft to descend orascend.Pulling the control rod down will driveup the head, |
|
| 12 | -and the aeroplane will ascend.Boosting it upwill make thehead downhill,and the aeroplane |
|
| 13 | -willdescend. |
|
| 14 | - |
|
| 15 | -## Channel 3: Throttle Operation |
|
| 16 | - |
|
| 17 | -Control the power. Pulling the control rod down will minish down the power group, and boosting |
|
| 18 | -the control rod up will increase thepower group. |
|
| 19 | - |
|
| 20 | -## Channel 4: Rudder Action |
|
| 21 | - |
|
| 22 | -Control the swerve of the aerocraft. Turning the control rod to left will make the head of the |
|
| 23 | -aircraft turn left, and turning it to right will make the head turn right. |
|
| 24 | - |
|
| 25 | -## Channel 5: LandingGear/GyroAction |
|
| 26 | - |
|
| 27 | -This channel is for switch variable. It is a switch to control landing gear when used for airplane |
|
| 28 | -state, but it will be a switch for gyroscope when used for helicopter. |
|
| 29 | - |
|
| 30 | -## Channel 6: Screw-pitch/Flaperon Action |
|
| 31 | - |
|
| 32 | -The angle adjustingof the flaperon isfor the airplane state,and the adjustingof themain |
|
| 33 | -screw-pitch is forhelicopter state. |
|
| 34 | - |
|
| 35 | - |
|
| 36 | -## ref |
|
| 37 | - |
|
| 38 | -- [[RC-dat]] - [[airplane]] - [[RC]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/2025-01-29-17-12-32.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/2025-01-29-17-12-32.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/2025-04-02-12-45-53.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/2025-04-02-12-45-53.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/2025-04-02-13-14-05.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/2025-04-02-13-14-05.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/2025-05-04-16-11-57.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ArduPilot-dat/2025-05-04-16-11-57.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-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 | - |
|
| 89 | - |
|
| 90 | - |
|
| 91 | -## ref |
|
| 92 | - |
|
| 93 | -- [[ardupilot-dat]] - [[FPV]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/CRSF-dat/CRSF-dat.md
| ... | ... | @@ -1,74 +0,0 @@ |
| 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-04-25-17-30-48.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-04-25-17-30-48.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-04-25-17-34-11.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-04-25-17-34-11.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-29-54.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-29-54.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-31-56.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/2025-05-04-15-31-56.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-915M-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-915M-dat.md |
|
| 3 | - |
|
| 4 | - |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-CHS-PWM-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-CHS-PWM-dat.md |
|
| 3 | - |
|
| 4 | - |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/2025-04-25-16-52-56.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/2025-04-25-16-52-56.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/2025-04-25-16-55-05.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/2025-04-25-16-55-05.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-RX-dat/ELRS-RX-dat.md
| ... | ... | @@ -1,43 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-RX-dat |
|
| 3 | - |
|
| 4 | - |
|
| 5 | -## T-anntena version |
|
| 6 | - |
|
| 7 | - |
|
| 8 | - |
|
| 9 | -## SMD antenna version |
|
| 10 | - |
|
| 11 | -## info |
|
| 12 | - |
|
| 13 | -Nano2400-RX receiver with power amplifier (PA+LNA). |
|
| 14 | - |
|
| 15 | -Therefore, it has 100mW telemetry output and better sensitivity at longer distances. |
|
| 16 | - |
|
| 17 | -It uses an IPEX1 antenna connector. |
|
| 18 | - |
|
| 19 | -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). |
|
| 20 | - |
|
| 21 | -The CYCLONE series receivers are based on the open-source architecture and program of ExpressLRS. |
|
| 22 | - |
|
| 23 | -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. |
|
| 24 | - |
|
| 25 | -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. |
|
| 26 | - |
|
| 27 | -The password is "expresslrs", and then you can access 10.0.0.1 to upload the receiver firmware. |
|
| 28 | - |
|
| 29 | -## Product Features |
|
| 30 | - |
|
| 31 | -- High refresh rate 100mW telemetry output; |
|
| 32 | -- Supports convenient and fast firmware flashing via WIFI connection; |
|
| 33 | -- Firmware Version: 3.3.0 [BETAFPVLite2400RX] |
|
| 34 | -- Equipped with a power amplifier (PA+LNA), providing 100mW telemetry output and better response speed; |
|
| 35 | -- Theoretically compatible with most ELRS 2.4G transmitter modules on the market (requires firmware version 2.0 or above). |
|
| 36 | - |
|
| 37 | - |
|
| 38 | - |
|
| 39 | - |
|
| 40 | - |
|
| 41 | -## ref |
|
| 42 | - |
|
| 43 | -- [[ELRS-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-dat.md
| ... | ... | @@ -1,143 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-dat |
|
| 3 | - |
|
| 4 | -Info - [[ELRS-frequency-dat]] - [[ELRS-faq-dat]] |
|
| 5 | - |
|
| 6 | - |
|
| 7 | -## ELRS-link |
|
| 8 | - |
|
| 9 | -ELRS-remote-console-tx |
|
| 10 | - |
|
| 11 | -- BETAFPV literadio 3 |
|
| 12 | -- BETAFPV literadio 2 |
|
| 13 | - |
|
| 14 | -- [[edge-tx-dat]] - [[radiomaster-dat]] - [[lightradio-dat]] |
|
| 15 | - |
|
| 16 | -- [[ELRS-RX-dat]] - [[SX1276-dat]] - [[ESP8285-dat]] - [[ESP32-dat]] - [[SX1281-dat]] - [[SX1208-dat]] |
|
| 17 | - |
|
| 18 | -protocol output - - [[CRSF-dat]] |
|
| 19 | - |
|
| 20 | -- [[CC2500-dat]] |
|
| 21 | - |
|
| 22 | -- [[ELRS-915M-dat]] - [[ELRS-CHS-PWM-dat]] - [[ELRS-2.4Ghz-dat]] |
|
| 23 | - |
|
| 24 | -- [[ELRS]] |
|
| 25 | - |
|
| 26 | -## resources |
|
| 27 | - |
|
| 28 | -https://github.com/ExpressLRS/ExpressLRS |
|
| 29 | - |
|
| 30 | -https://www.expresslrs.org/quick-start/getting-started/ |
|
| 31 | - |
|
| 32 | -[ExpressLRS-Configurator-releases](https://github.com/ExpressLRS/ExpressLRS-Configurator/releases) |
|
| 33 | - |
|
| 34 | - |
|
| 35 | - |
|
| 36 | -## **ExpressLRS (ELRS) 2.4GHz Standard Explained** |
|
| 37 | - |
|
| 38 | -**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. |
|
| 39 | - |
|
| 40 | ---- |
|
| 41 | - |
|
| 42 | -### **🔹 Key Features of ELRS 2.4GHz** |
|
| 43 | -- **Ultra-Low Latency** (~5ms in high-speed mode). |
|
| 44 | -- **Long-Range Performance** (Up to **30km+** with proper setup). |
|
| 45 | -- **High Packet Rate (Up to 1000Hz)** for **smooth & responsive controls**. |
|
| 46 | -- **Open-Source & Customizable** (Community-driven development). |
|
| 47 | -- **Affordable Hardware** (Compared to Crossfire or Ghost). |
|
| 48 | -- **Wide Compatibility** (Supported on many **radio transmitters & receivers**). |
|
| 49 | - |
|
| 50 | ---- |
|
| 51 | - |
|
| 52 | -### **🔹 ELRS 2.4GHz vs. Other RC Links** |
|
| 53 | -| Feature | ELRS 2.4GHz | TBS Crossfire | Ghost 2.4GHz | FrSky R9M | |
|
| 54 | -| --------------- | ------------ | ------------- | ------------ | ----------- | |
|
| 55 | -| **Frequency** | 2.4GHz | 900MHz | 2.4GHz | 900MHz | |
|
| 56 | -| **Max Range** | ~30km+ | ~50km+ | ~15km | ~10-20km | |
|
| 57 | -| **Latency** | 5-7ms | 15-50ms | ~4ms | ~20ms | |
|
| 58 | -| **Packet Rate** | Up to 1000Hz | 50-150Hz | 500Hz | ~100Hz | |
|
| 59 | -| **Open Source** | ✅ Yes | ❌ No | ❌ No | ❌ No | |
|
| 60 | -| **Cost** | 💰 Affordable | 💰💰 Expensive | 💰💰 Expensive | 💰 Mid-Range | |
|
| 61 | - |
|
| 62 | ---- |
|
| 63 | - |
|
| 64 | -### **🔹 ELRS 2.4GHz Modes & Performance** |
|
| 65 | -| Mode | Packet Rate | Latency | Range | |
|
| 66 | -| --------- | ----------- | ------- | --------------------- | |
|
| 67 | -| **500Hz** | 500Hz | ~5ms | Short (~3km) | |
|
| 68 | -| **250Hz** | 250Hz | ~7ms | Mid (~10km) | |
|
| 69 | -| **150Hz** | 150Hz | ~10ms | Long (~20km) | |
|
| 70 | -| **50Hz** | 50Hz | ~20ms | Extreme Long (~30km+) | |
|
| 71 | - |
|
| 72 | -🔹 **Higher packet rate = Lower latency, but reduced range** |
|
| 73 | -🔹 **Lower packet rate = Higher range, but increased latency** |
|
| 74 | - |
|
| 75 | ---- |
|
| 76 | - |
|
| 77 | -### **🔹 Recommended ExpressLRS 2.4GHz Hardware** |
|
| 78 | -#### **🛠️ Transmitters (TX)** |
|
| 79 | -- **RadioMaster Zorro ELRS 2.4GHz** |
|
| 80 | -- **Jumper T20S (Built-in ELRS)** |
|
| 81 | -- **Happymodel ES24TX Pro (External ELRS Module)** |
|
| 82 | -- **BetaFPV ELRS Micro TX Module** |
|
| 83 | - |
|
| 84 | -#### **📡 Receivers (RX)** |
|
| 85 | -- **Happymodel EP2 (Tiny, best for micro quads)** |
|
| 86 | -- **BetaFPV ELRS 2.4GHz Nano RX** |
|
| 87 | -- **Radiomaster RP1 / RP2 RX (Great range & reliability)** |
|
| 88 | - |
|
| 89 | ---- |
|
| 90 | - |
|
| 91 | -### **🔹 Why Choose ELRS 2.4GHz?** |
|
| 92 | -✅ **Best for FPV Racing & Freestyle** → **Low latency & fast response** |
|
| 93 | -✅ **Perfect for Long-Range FPV** → **Good range at lower packet rates** |
|
| 94 | -✅ **Affordable & Open-Source** → **Cheaper than Crossfire & Ghost** |
|
| 95 | - |
|
| 96 | -🚀 **If you need ultra-low latency for FPV racing or long-range performance at an affordable price, ExpressLRS 2.4GHz is the best choice!** 🔥 |
|
| 97 | - |
|
| 98 | - |
|
| 99 | -## 2.4hz compare to LORA 915mhz |
|
| 100 | - |
|
| 101 | -| Feature | DJI NC3 (OcuSync 2.0) | ELRS 2.4GHz (100mW) | ELRS 915MHz (100mW, SX1276) | |
|
| 102 | -|----------------------------|---------------------------|------------------------------|-------------------------------| |
|
| 103 | -| Protocol Type | Proprietary digital (DJI) | Open-source LoRa/FLRC | Open-source LoRa | |
|
| 104 | -| Frequency Band | 2.4GHz + 5.8GHz | 2.4GHz | 915MHz | |
|
| 105 | -| Max Packet Rate | N/A (digital control/video)| Up to 500Hz | Up to 50Hz | |
|
| 106 | -| Latency (best-case) | ~120 ms (control + video) | ~2.5 ms (500Hz) | ~20 ms (50Hz) | |
|
| 107 | -| Typical Latency | ~120–150 ms | ~6–13 ms | ~22–30 ms | |
|
| 108 | -| Max Range (LOS, FCC) | ~10 km | ~2 km | ~10 km | |
|
| 109 | -| Penetration (Obstacles) | Moderate | Moderate | Strong | |
|
| 110 | -| Interference Resistance | High (hopping + digital) | Moderate | Strong | |
|
| 111 | -| Video Support | Yes (integrated) | No | No | |
|
| 112 | -| Use Case | DJI drones (Mini, Air) | FPV racing, freestyle | Long-range FPV, endurance | |
|
| 113 | -| Antenna Size | Small | Small | Larger | |
|
| 114 | -| Custom Flight Controllers | Not supported | Fully supported | Fully supported | |
|
| 115 | - |
|
| 116 | - |
|
| 117 | -❌ No — ELRS does not support 5.8GHz (as of now). |
|
| 118 | - |
|
| 119 | -- [[LORA-dat]] - [[RF-2.4ghz-dat]] |
|
| 120 | - |
|
| 121 | -- [[5.8Ghz-dat]] |
|
| 122 | - |
|
| 123 | - |
|
| 124 | -## WebUI |
|
| 125 | - |
|
| 126 | -### Via "ExpressLRS RX" Access Point |
|
| 127 | - |
|
| 128 | - |
|
| 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 | - |
|
| 137 | - |
|
| 138 | - |
|
| 139 | -## ref |
|
| 140 | - |
|
| 141 | -- [[FPV-dat]] |
|
| 142 | - |
|
| 143 | -- [[ELRS]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-faq-dat.md
| ... | ... | @@ -1,26 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-faq-dat |
|
| 3 | - |
|
| 4 | -## Frequently Asked Questions (FAQ) |
|
| 5 | - |
|
| 6 | -**Q1: Can this receiver bind with a transmitter module (TX module) from brand XXX?** |
|
| 7 | -**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: |
|
| 8 | - 1. **Same Frequency:** Both must operate on the same frequency band (e.g., both 2.4GHz or both 915MHz). |
|
| 9 | - 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. |
|
| 10 | - 3. **Binding Phrase:** Either both devices have no binding phrase set, or they both have the exact same binding phrase configured. |
|
| 11 | - |
|
| 12 | -**Q2: How do I enter binding mode?** |
|
| 13 | -**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. |
|
| 14 | - |
|
| 15 | -**Q3: The first time I used my receiver, it wouldn't enter binding mode, and the LED stayed solid. Why?** |
|
| 16 | -**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. |
|
| 17 | - |
|
| 18 | -**Q4: Why is my receiver's LED flashing quickly and continuously?** |
|
| 19 | -**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. |
|
| 20 | - |
|
| 21 | -**Q5: How do I enter Wi-Fi mode to update the receiver's firmware?** |
|
| 22 | -**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. |
|
| 23 | - |
|
| 24 | - |
|
| 25 | -## ref |
|
| 26 | - |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/ELRS-frequency-dat.md
| ... | ... | @@ -1,20 +0,0 @@ |
| 1 | - |
|
| 2 | -# ELRS-frequency-dat.md |
|
| 3 | - |
|
| 4 | -| Feature | ELRS 915MHz (LoRa) | ELRS 2.4GHz (LoRa/FLRC) | |
|
| 5 | -|---------------------|-----------------------------|------------------------------| |
|
| 6 | -| Frequency Band | 915 MHz | 2.4 GHz | |
|
| 7 | -| Range (LOS, 100mW) | ✅ 5–10+ km | ⚠️ 1–2 km | |
|
| 8 | -| Penetration | ✅ Strong (trees, buildings) | ⚠️ Moderate | |
|
| 9 | -| Latency | ❌ ~20–30 ms | ✅ ~2.5–13 ms | |
|
| 10 | -| Max Packet Rate | ❌ ~50Hz | ✅ Up to 500Hz | |
|
| 11 | -| Antenna Size | ❌ Large | ✅ Small | |
|
| 12 | -| Interference Avoidance | ✅ Less crowded band | ⚠️ More Wi-Fi/Bluetooth noise | |
|
| 13 | -| Use Case | Long-range, endurance | Freestyle, racing | |
|
| 14 | -| Power Efficiency | ✅ High (lower data rate) | ✅ High (LoRa + FLRC modes) | |
|
| 15 | -| Hardware Support | Older SX1276 modules | Newer SX1280 + ESP modules | |
|
| 16 | - |
|
| 17 | - |
|
| 18 | -## ref |
|
| 19 | - |
|
| 20 | -- [[ELRS-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/ELRS-dat/edge-tx-dat/edge-tx-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 1 | - |
|
| 2 | -# edge-tx-dat |
|
| 3 | - |
|
| 4 | -https://github.com/EdgeTX/edgetx |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/FPV-controller-dat.md
| ... | ... | @@ -1,13 +0,0 @@ |
| 1 | - |
|
| 2 | -# FPV-receiver-dat |
|
| 3 | - |
|
| 4 | -- [[ELRS-dat]] - [[TBS-dat]] |
|
| 5 | - |
|
| 6 | - |
|
| 7 | -## DJI |
|
| 8 | - |
|
| 9 | -- [DJI FPV Remote Controller 3](https://www.amazon.com/DJI-FPV-Remote-Controller-Compatibility/dp/B0CS6JCX2W/ref=sr_1_3?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-3) |
|
| 10 | - |
|
| 11 | -- [DJI RC Motion 3, FPV Smart Controller with Immersive Motion Control, Compact and Portable, One-Click Emergency Brake, AR Cursor, Intuitive Drone Controller, Multi-Model Compatibility](https://www.amazon.com/DJI-Controller-Immersive-Multi-Model-Compatibility/dp/B0CS6LDCKC/ref=sr_1_11?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-11) |
|
| 12 | - |
|
| 13 | - |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/FrSky-dat/FrSky-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 1 | - |
|
| 2 | -# FrSky-dat |
|
| 3 | - |
|
| 4 | -- [[CC2500-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/SBUS-dat/SBUS-dat.md
| ... | ... | @@ -1,75 +0,0 @@ |
| 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]] |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-45-14.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-45-14.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-51-22.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-51-22.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-53-48.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-53-48.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-58-58.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-14-58-58.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-15-03-29.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/2025-05-05-15-03-29.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/WFLY-WFT06X_Mannual.pdf
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/WFLY-WFT06X_Mannual.pdf and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/WFLY-dat.md
| ... | ... | @@ -1,7 +0,0 @@ |
| 1 | - |
|
| 2 | -# WFLY-dat.md |
|
| 3 | - |
|
| 4 | -- [[WFT06x-dat]] - [[WFR06S-dat]] |
|
| 5 | - |
|
| 6 | - |
|
| 7 | - |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/WFR06S-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 1 | - |
|
| 2 | -# WFR06S-dat.md |
|
| 3 | - |
|
| 4 | - |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/WFLY-dat/WFT06X-dat.md
| ... | ... | @@ -1,113 +0,0 @@ |
| 1 | -# WFLY-dat |
|
| 2 | - |
|
| 3 | - |
|
| 4 | - |
|
| 5 | - |
|
| 6 | - |
|
| 7 | -- the manual == [[WFLY-WFT06X_Mannual.pdf]] |
|
| 8 | -- [fccd.io manual link](https://fccid.io/TZVWFT06XWFT08S/User-Manual/User-Manual-1-1119279.pdf) |
|
| 9 | - |
|
| 10 | -## Info |
|
| 11 | - |
|
| 12 | -- WFT06X-A: 6 channels airplane,mixfunction,D/R,HDE helicopter. |
|
| 13 | -- WFT06X-B: 4 channesl airplane, mix function,D/R, HDE helicopter. |
|
| 14 | -- WFT06X-C: 6 channels CCPMhelicopter,airplane. |
|
| 15 | - |
|
| 16 | - |
|
| 17 | -## Models |
|
| 18 | - |
|
| 19 | - |
|
| 20 | - |
|
| 21 | -- [[airplane-dat]] |
|
| 22 | - |
|
| 23 | - |
|
| 24 | -## toggle switches |
|
| 25 | - |
|
| 26 | - |
|
| 27 | - |
|
| 28 | - |
|
| 29 | -| Switch | State | | Up | Down | |
|
| 30 | -| :---------- | :--------- | --------------------------- | :--------------------------------- | :--------------------------------- | |
|
| 31 | -| A | Helicopter | Ch3 to Ch4 mixture. (note1) | Enables | Disables | |
|
| 32 | -| B | N/A | | Selects Helicopter state. | Selects Airplane state. | |
|
| 33 | -| C (1,2,4,6) | Airplane | | Dual Rate set to ±125%. | Dual Rate set to ±100%. | |
|
| 34 | -| D | Airplane | | Enables mixture functions (E, F). | Disables mixture functions (E, F). | |
|
| 35 | -| E | Airplane | | Enables Ch2 & Ch4 mixture (note3) | Enables Ch1 & Ch6 mixture (note3) | |
|
| 36 | -| F | Airplane | | Enables Ch1 & Ch2 mixture (note2). | N/A | |
|
| 37 | -| G (Ch1) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 38 | -| H (Ch2) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 39 | -| I (Ch3) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 40 | -| J (Ch4) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 41 | -| K (Ch6) | N/A | | Reverse Mode. | Normal Mode. | |
|
| 42 | - |
|
| 43 | -note1 == Ch3 to Ch6 mix always active |
|
| 44 | - |
|
| 45 | -note2 == (Elevon/Delta Wing) (Requires D Up, overrides D) |
|
| 46 | - |
|
| 47 | -note3 == (V-Tail) (Requires D Up). |
|
| 48 | - |
|
| 49 | -Switch Function Instruction |
|
| 50 | - |
|
| 51 | -- (A)At helicopterstate,pulling A down to put offmixturefunction of channel3to channel4,when pulling it up it willcomebackthefunction.Butthemixturefunctiontochannel 6isstable,whichisirrelevant with this switch. |
|
| 52 | -- (B) Pulling B down is airplane state and pulling it up is helicopter state. |
|
| 53 | -- (C) At airplane state, pulling 1, 2, 4, 6 down the dual rate is ±100%; when pulling them up, the dual rate will be ±125%. |
|
| 54 | -- (D) At airplane state, pulling D down make switches have no mixture function, but pulling it up will cause them have thefunction. |
|
| 55 | -- (E) At airplane state, when D is pulled up, pulling E down cause channel 1 & 6 mixture function (Flaperon); pulling E up will cause channel 2 & 4 mixture function(V-TAIL). |
|
| 56 | -- (F) At airplane state,when D is pulled up,pulling F up it works as the mixture function of channel 1&2(TrianglewingELEVON),and Dfunctiondoesn'tworkat that moment. |
|
| 57 | -- (G) Channel 1 is reverse switch for aileron.Pulling G down is to make it in normal mode,and pulling it up is to make it act in reverse. |
|
| 58 | -- (H) Channel 2 is reverse switch for elevator. Pulling H down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 59 | -- (I) Channel 3 is reverse switch for power. Pulling I down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 60 | -- (J) Channel 4 is reverse switch for rudder. Pulling J down is to make it in normal mode, and pulling it up is to makeitactinreverse. |
|
| 61 | -- (K) Channel 6 is reverse switch for screw-pitch/ flaperon.Pulling K down is to make it in normal mode, and pulling it up is to make it act in reverse. |
|
| 62 | - |
|
| 63 | - |
|
| 64 | - |
|
| 65 | -## Binding Instructions: |
|
| 66 | - |
|
| 67 | -1. **Receiver:** Press and hold the "SET" button until the orange "STATUS" light flashes slowly. The receiver is now waiting for the transmitter's binding command. |
|
| 68 | -2. **Transmitter:** Press and hold the "SET" button while powering on the transmitter. Press the SET button once more to enter the binding function (the orange "STATUS" light will be solid). Then, press and hold the SET button until the orange light flashes slowly, entering the binding state. |
|
| 69 | -3. **Binding Successful:** The transmitter's green light will turn solid, and the receiver's indicator light will turn off. |
|
| 70 | - |
|
| 71 | -## Failsafe Setup: |
|
| 72 | - |
|
| 73 | -1. Power on the receiver. |
|
| 74 | -2. Press and hold the "SET" button while powering on the transmitter. Then, press and hold the SET button for about 2 seconds to enter the failsafe setup state (the green light will flash). |
|
| 75 | -3. The receiver's green light will flash quickly. The data currently being output by the transmitter will be set as the failsafe output data for the receiver. |
|
| 76 | -4. **Failsafe Active State:** The receiver's red light will be solid. |
|
| 77 | - |
|
| 78 | -## Technical Parameters: |
|
| 79 | - |
|
| 80 | -* **Application:** Fixed-wing aircraft, HDE helicopters, fixed-pitch helicopters, cars, boats |
|
| 81 | -* **Frequency Band:** 2.400 - 2.483 GHz |
|
| 82 | -* **Transmit Power:** ≤ 100mW |
|
| 83 | -* **Operating Current:** ≤ 160mA |
|
| 84 | -* **Encoding:** PPM |
|
| 85 | -* **RF Module:** Built-in |
|
| 86 | -* **Power Supply:** 9.6 - 12V |
|
| 87 | -* **Dual Rate/Expo Range:** 100% ~ 125% |
|
| 88 | -* **Mixing:** |
|
| 89 | - * Flaperon (Channel 6 and Channel 1 mix) |
|
| 90 | - * V-Tail (Channel 4 and Channel 2 mix) |
|
| 91 | - * Delta Wing (Elevon) (Channel 1 and Channel 2 mix) |
|
| 92 | - * HDE Helicopter (Channel 3 to Channel 4 & 6 mix) |
|
| 93 | - * HDE Helicopter (Channel 3 to Channel 6 mix) |
|
| 94 | -* **Reverse Switches:** |
|
| 95 | - * Channel 1: Aileron |
|
| 96 | - * Channel 2: Elevator |
|
| 97 | - * Channel 3: Throttle |
|
| 98 | - * Channel 4: Rudder |
|
| 99 | - * Channel 6: Flap/Pitch |
|
| 100 | -* **Low Voltage Alarm (Visual & Audible):** |
|
| 101 | - * Battery Voltage < 8.8V: Power indicator flashes once per second with beeping. |
|
| 102 | - * Battery Voltage < 8.3V: Power indicator flashes twice per second (0.5s interval) with beeping. |
|
| 103 | -* **Charging Jack:** Yes |
|
| 104 | -* **Simulator Jack:** Yes |
|
| 105 | - |
|
| 106 | - |
|
| 107 | -## demo video |
|
| 108 | - |
|
| 109 | -- [how to binding WFLY in chinese ](https://www.bilibili.com/video/BV1Mh4y1c7FS/?vd_source=74a6b8b9bfcd41c5946a742815bf71ae) |
|
| 110 | - |
|
| 111 | -## ref |
|
| 112 | - |
|
| 113 | -- [[WFLY]] - [[lightradio]] - [[radiomaster]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-controller-dat/flight-controller-dat/flight-controller-dat.md
| ... | ... | @@ -1,3 +0,0 @@ |
| 1 | - |
|
| 2 | -# flight-controller-dat |
|
| 3 | - |
app-dat/quadcopter-dat/FPV-dat/FPV-dat.md
| ... | ... | @@ -1,208 +0,0 @@ |
| 1 | - |
|
| 2 | -# FPV-dat |
|
| 3 | - |
|
| 4 | -- [[quadcopter-dat]] |
|
| 5 | - |
|
| 6 | -- [[FPV-controller-dat]] - [[Goggles-dat]] |
|
| 7 | - |
|
| 8 | -- [[ELRS-dat]] - [[FrSky-dat]] - [[ArduPilot-dat]] - [[CRSF-dat]] |
|
| 9 | - |
|
| 10 | -- [[BMS-dat]] |
|
| 11 | - |
|
| 12 | - |
|
| 13 | - |
|
| 14 | -## parts of the FPV drones |
|
| 15 | - |
|
| 16 | -- **Flight Controller**: The brain of the drone, responsible for stabilizing and controlling the flight. It processes data from sensors and executes commands from the pilot or autopilot system. |
|
| 17 | - |
|
| 18 | -- **Electronic Speed Controller (ESC)**: Controls the speed of the motors by adjusting the power supplied to them. ESCs are essential for smooth and responsive flight. |
|
| 19 | - |
|
| 20 | -- **Motors**: Provide the thrust needed for flight. Brushless motors are commonly used in FPV drones due to their efficiency and power. |
|
| 21 | - |
|
| 22 | -- **Propellers**: Generate lift by spinning rapidly. The size and pitch of the propellers can significantly affect the drone's performance and flight characteristics. |
|
| 23 | - |
|
| 24 | - - [[SCU1059-dat]] |
|
| 25 | - |
|
| 26 | -- **Camera**: Captures real-time video for FPV flying. FPV cameras are designed to provide low-latency video transmission to the pilot's goggles or screen. |
|
| 27 | - |
|
| 28 | -- [[VTX-dat]]: Video Transmitters are commonly referred to as VTX units. They are responsible for transmitting the video signal from the camera to the pilot's goggles or screen. VTX units come in various power levels and frequencies, allowing pilots to choose the best option for their flying environment. |
|
| 29 | -- **Antenna**: Enhances the signal strength and range of the VTX. Different antenna types (e.g., dipole, patch, circular polarized) can be used to optimize performance. |
|
| 30 | - |
|
| 31 | -- **ExpressLRS**: A long-range radio control link for FPV drones, known for its low latency and high refresh rates. It is an open-source project that competes with other systems like Crossfire and ELRS. |
|
| 32 | - |
|
| 33 | - - [[ELRS-dat]] |
|
| 34 | - |
|
| 35 | -- **Goggles**: Wearable displays that allow pilots to see the live video feed from the drone's camera. They often include features like head tracking and DVR (Digital Video Recorder) capabilities. |
|
| 36 | - |
|
| 37 | - |
|
| 38 | - |
|
| 39 | - |
|
| 40 | - |
|
| 41 | -## Bee35 |
|
| 42 | - |
|
| 43 | - |
|
| 44 | - |
|
| 45 | - |
|
| 46 | - |
|
| 47 | - |
|
| 48 | -| version | price | description | |
|
| 49 | -| -------------------------- | ----- | ------------------------------------- | |
|
| 50 | -| Bee35 Pro O3 Air Unit TBS | 480 | O3 Air Unit, TBS radio | |
|
| 51 | -| Bee35 Pro O3 Air Unit ELRS | 470 | O3 Air Unit, ELRS radio | |
|
| 52 | -| Bee35 Pro O3 Air Unit PNP | 460 | O3 Air Unit, no receiver | |
|
| 53 | -| Bee35 Pro | 270 | Standard analog version | |
|
| 54 | -| Bee35 Pro LINK WASP TBS | 430 | LINK WASP digital system, TBS radio | |
|
| 55 | -| Bee35 Pro LINK WASP ELRS | 420 | LINK WASP digital system, ELRS radio | |
|
| 56 | -| Bee35 Pro LINK WASP PNP | 400 | LINK WASP digital system, no receiver | |
|
| 57 | -| Bee35 Analog TBS | 306 | Analog FPV system, TBS radio | |
|
| 58 | -| Bee35 Analog ELRS | 296 | Analog FPV system, ELRS radio | |
|
| 59 | - |
|
| 60 | - |
|
| 61 | - |
|
| 62 | -## commerialized FPV |
|
| 63 | - |
|
| 64 | -- [[speedybee-dat]] |
|
| 65 | - |
|
| 66 | -### 1. [SpeedyBee Flight Controllers & Stacks](https://speedybee.com/) |
|
| 67 | -- **Brand:** SpeedyBee |
|
| 68 | -- **Description:** Budget-friendly, Betaflight-supported flight controllers with easy app-based tuning. |
|
| 69 | -- **Example Products:** |
|
| 70 | - - **SpeedyBee F405 V4 Stack** (F4-based, affordable) |
|
| 71 | - - **SpeedyBee F7 V3 Stack** (F7-based, powerful & feature-rich) |
|
| 72 | -- **Commercial Features:** |
|
| 73 | - - Wireless **Bluetooth & Wi-Fi tuning** via SpeedyBee app. |
|
| 74 | - - Fully compatible with Betaflight Configurator. |
|
| 75 | -- **Website:** [speedybee.com](https://speedybee.com/) |
|
| 76 | - |
|
| 77 | ---- |
|
| 78 | - |
|
| 79 | -### 2. [TBS Tango 2 (Crossfire-Integrated Radio Controller)](https://www.team-blacksheep.com/) |
|
| 80 | -- **Brand:** Team BlackSheep (TBS) |
|
| 81 | -- **Description:** A high-performance FPV radio transmitter designed for **Betaflight-based drones** with **built-in Crossfire**. |
|
| 82 | -- **Commercial Features:** |
|
| 83 | - - Fully optimized for **Betaflight & Crossfire**. |
|
| 84 | - - Compact, ergonomic design for FPV pilots. |
|
| 85 | -- **Website:** [team-blacksheep.com](https://www.team-blacksheep.com/) |
|
| 86 | - |
|
| 87 | - |
|
| 88 | -## opensource control projects |
|
| 89 | - |
|
| 90 | -# Most Famous Open-Source FPV GitHub Projects |
|
| 91 | - |
|
| 92 | -If you're looking for **open-source FPV (First-Person View) projects** on GitHub, here are some of the **most famous** ones: |
|
| 93 | - |
|
| 94 | -## 1. [Betaflight](https://github.com/betaflight/betaflight) |
|
| 95 | -- **Description:** One of the most widely used open-source flight control firmware for FPV drones. |
|
| 96 | -- **Features:** |
|
| 97 | - - Highly optimized for **acrobatic** and **racing drones**. |
|
| 98 | - - Supports a wide range of flight controllers. |
|
| 99 | - - Advanced **tuning options** for PID, filters, and motor control. |
|
| 100 | -- **GitHub:** [github.com/betaflight/betaflight](https://github.com/betaflight/betaflight) |
|
| 101 | - |
|
| 102 | ---- |
|
| 103 | - |
|
| 104 | -## 2. [iNavFlight](https://github.com/iNavFlight/inav) |
|
| 105 | -- **Description:** A fork of Betaflight, but optimized for **GPS and long-range FPV**. |
|
| 106 | -- **Features:** |
|
| 107 | - - Supports **GPS waypoint navigation, return-to-home (RTH), and mission planning**. |
|
| 108 | - - Designed for **freestyle and long-range cruising** rather than racing. |
|
| 109 | -- **GitHub:** [github.com/iNavFlight/inav](https://github.com/iNavFlight/inav) |
|
| 110 | - |
|
| 111 | ---- |
|
| 112 | - |
|
| 113 | -## 3. [ArduPilot](https://github.com/ArduPilot/ardupilot) |
|
| 114 | -- **Description:** A professional-grade open-source autopilot for drones, including **FPV quadcopters, planes, and rovers**. |
|
| 115 | -- **Features:** |
|
| 116 | - - **Highly autonomous** with advanced mission planning. |
|
| 117 | - - Works with multiple types of vehicles (planes, multirotors, helicopters). |
|
| 118 | - - Compatible with **Mission Planner** and **QGroundControl**. |
|
| 119 | -- **GitHub:** [github.com/ArduPilot/ardupilot](https://github.com/ArduPilot/ardupilot) |
|
| 120 | - |
|
| 121 | ---- |
|
| 122 | - |
|
| 123 | -## 4. [PX4](https://github.com/PX4/PX4-Autopilot) |
|
| 124 | -- **Description:** A powerful open-source **flight control software** used in drones and FPV systems. |
|
| 125 | -- **Features:** |
|
| 126 | - - Supports both **FPV racing drones** and **autonomous UAVs**. |
|
| 127 | - - Works with Pixhawk flight controllers and supports **ROS (Robot Operating System)**. |
|
| 128 | -- **GitHub:** [github.com/PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) |
|
| 129 | - |
|
| 130 | ---- |
|
| 131 | - |
|
| 132 | -## 5. [FalcoX](https://github.com/FlightOne/FalcoX) |
|
| 133 | -- **Description:** An alternative FPV flight control firmware focusing on **ease of use and smooth flight performance**. |
|
| 134 | -- **Features:** |
|
| 135 | - - Intuitive configuration interface. |
|
| 136 | - - Aimed at both **freestyle pilots** and **racers**. |
|
| 137 | -- **GitHub:** [github.com/FlightOne/FalcoX](https://github.com/FlightOne/FalcoX) |
|
| 138 | - |
|
| 139 | ---- |
|
| 140 | - |
|
| 141 | -## 6. [ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) |
|
| 142 | -- **Description:** Open-source long-range **radio control link** for FPV drones, competing with Crossfire and ELRS. |
|
| 143 | -- **Features:** |
|
| 144 | - - **Low latency and high refresh rates** (great for FPV racing). |
|
| 145 | - - Compatible with many radio transmitters (TBS, Jumper, Radiomaster). |
|
| 146 | -- **GitHub:** [github.com/ExpressLRS/ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) |
|
| 147 | - |
|
| 148 | ---- |
|
| 149 | - |
|
| 150 | -## 7. [OpenHD](https://github.com/OpenHD/OpenHD) |
|
| 151 | -- **Description:** Open-source **HD video transmission** for FPV drones (alternative to DJI HD systems). |
|
| 152 | -- **Features:** |
|
| 153 | - - Uses **Raspberry Pi + WiFi** for HD FPV video streaming. |
|
| 154 | - - Supports OSD (On-Screen Display) and telemetry data. |
|
| 155 | -- **GitHub:** [github.com/OpenHD/OpenHD](https://github.com/OpenHD/OpenHD) |
|
| 156 | - |
|
| 157 | ---- |
|
| 158 | - |
|
| 159 | -## 🔥 Which One Should You Choose? |
|
| 160 | -| Purpose | Best Open-Source Project | |
|
| 161 | -| ------------------------------------------- | ------------------------------------------------------ | |
|
| 162 | -| **Racing/Freestyle FPV** | [Betaflight](https://github.com/betaflight/betaflight) | |
|
| 163 | -| **GPS & Long-Range FPV** | [iNav](https://github.com/iNavFlight/inav) | |
|
| 164 | -| **Full Autopilot (Drones, Planes, Rovers)** | [ArduPilot](https://github.com/ArduPilot/ardupilot) | |
|
| 165 | -| **Professional UAVs & Research** | [PX4](https://github.com/PX4/PX4-Autopilot) | |
|
| 166 | -| **HD FPV Video Streaming** | [OpenHD](https://github.com/OpenHD/OpenHD) | |
|
| 167 | -| **Long-Range Radio Links** | [ExpressLRS](https://github.com/ExpressLRS/ExpressLRS) | |
|
| 168 | - |
|
| 169 | - |
|
| 170 | - |
|
| 171 | -## standards |
|
| 172 | - |
|
| 173 | -### PNP stands for "Plug and Play." |
|
| 174 | - |
|
| 175 | -In the context of FPV drones, a PNP version means that the drone comes mostly assembled but does not include a radio receiver. |
|
| 176 | - |
|
| 177 | -Here's why it doesn't include a receiver: |
|
| 178 | - |
|
| 179 | -Flexibility: PNP versions cater to experienced FPV pilots who already have their preferred radio transmitter and receiver. This allows them to use their existing equipment and avoid paying for redundant components. |
|
| 180 | -Customization: Pilots might have specific receiver requirements based on their radio system (e.g., TBS Crossfire, ELRS, FrSky). Offering a PNP version lets them choose the exact receiver that's compatible with their setup. |
|
| 181 | -Cost Savings: By excluding the receiver, the manufacturer can offer the PNP version at a lower price point, making it attractive to those who don't need the included receiver. |
|
| 182 | -In short, PNP versions are designed for users who want to use their own radio gear and prefer to avoid unnecessary costs or compatibility issues. |
|
| 183 | - |
|
| 184 | - |
|
| 185 | - |
|
| 186 | -## popular products |
|
| 187 | - |
|
| 188 | -DJI |
|
| 189 | - |
|
| 190 | -- [DJI Avata 2 (Drone Only), FPV Drone with Camera 4K, Immersive Flight Experience, Built-in Propeller Guard, Easy Flip/Roll, Super-Wide 155° FOV, Compatible with RC Motion 3, FAA Remote ID Compliant](https://www.amazon.com/DJI-Immersive-Experience-Super-Wide-Compatible/dp/B0CS6KY96F/ref=sr_1_45?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-45) |
|
| 191 | - |
|
| 192 | -BetaFPV |
|
| 193 | - |
|
| 194 | -- [BETAFPV Betaflight ELRS V3 Cetus X FPV Kit with LiteRadio 3 Transmitter C04 Camera VR03 Goggles with DVR Recording Function, Supported 2S Power Advanced RTF Kit for FPV Beginners to Fly Faster Further](https://www.amazon.com/BETAFPV-LiteRadio-Transmitter-Recording-Betaflight/dp/B0BJVP3XW7/ref=sr_1_48?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-48) == rating == 3.5 |
|
| 195 | - |
|
| 196 | -- [BETAFPV Pavo20 Brushless Whoop Quadcopter with HD Digital Bracket for O3 Air Unit, F4 2-3S 20A FC, 1103 8500KV Motor, COB LED Strip, Compatible for FPV Racing Indoor and Outdoor](https://www.amazon.com/BETAFPV-Brushless-Quadcopter-Material-Compatible/dp/B0CKT5G6C1/ref=sr_1_11?crid=1KCLBGZLCPWMM&dib=eyJ2IjoiMSJ9.u8zpDMqhQLF9cnPbc5r76LO9SVPJiVyPzTq0xdtVa2u4UYSXdyYl9H-Z3gMzqguhRBkKgkoRZWaxBHDFD6BRFsCQJKVb4iWibNm9DVSzo8jjnyx10jKEMfQICYMtZJab4CpDzmZXALE0VqfYmsl2b2z6zA536zmhj3MbQfvXxqOrlO8RzQiYLdFv-lIZbHe3VqkD5N2AuBL25TgOETuGrMPmYt7Yhvu1G4lry067nFXe06m0NOi7YGC9HehoblQsTDd1-4IPkuJfZGdR6OljCFD_F9mIqaJ-dIPMlULs8kg.m1NOD5DB1dn9oAtRj6kjXh5UkWTCRb94gNjUZ8Owz8Y&dib_tag=se&keywords=betafpv&qid=1744202445&sprefix=beta%2Caps%2C676&sr=8-11) == rating == 4.1 |
|
| 197 | - |
|
| 198 | - |
|
| 199 | -SpeedyBee Frame |
|
| 200 | - |
|
| 201 | -- [Speedy Bee Bee35 3.5inch Cinewhoop FPV Drone Frame- Pro Version 4S 6S Frame Kit Compatible with DJI O3 Air Unit FPV VTX,Different Flight Controller Stack](https://www.amazon.com/3-5inch-Cinewhoop-Compatible-Different-Controller/dp/B086X5M24H/ref=sr_1_1?dib=eyJ2IjoiMSJ9.flOlB5a6W8Z4mxOLR-K_BDlWDFVnqHJ69LrRLHzsG3Vt1_EuF1CQCJw-erVA1bWn.aK6G-MxmMYmSkACuczQuR4yI0PIn2BzHbY4-bbiXRLo&dib_tag=se&keywords=bee35&qid=1744202041&sr=8-1) |
|
| 202 | - |
|
| 203 | - |
|
| 204 | - |
|
| 205 | - |
|
| 206 | -## ref |
|
| 207 | - |
|
| 208 | -- [[FPV]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/FPV-simulation-dat/FPV-simulation-dat.md
| ... | ... | @@ -1,88 +0,0 @@ |
| 1 | - |
|
| 2 | -# FPV-simulation-dat |
|
| 3 | - |
|
| 4 | -## Popular FPV Simulators for PC |
|
| 5 | - |
|
| 6 | -| Simulator | Highlights | Price | |
|
| 7 | -| ------------- | ---------------------------------------------------------- | ----- | |
|
| 8 | -| Liftoff | Realistic physics, good for racing & freestyle | ~$20 | |
|
| 9 | -| VelociDrone | Excellent feel, popular for competition practice | ~$20 | |
|
| 10 | -| DRL Simulator | Based on the Drone Racing League, includes tracks & events | ~$10 | |
|
| 11 | -| Uncrashed | Stunning graphics, smooth flying | ~$15 | |
|
| 12 | -| FPV Freerider | Lightweight, good for low-end PCs | ~$5 | |
|
| 13 | - |
|
| 14 | - |
|
| 15 | - |
|
| 16 | -## Compatible Controllers |
|
| 17 | - |
|
| 18 | -- RadioMaster TX16S |
|
| 19 | -- FrSky Taranis QX7 / X9D |
|
| 20 | -- BetaFPV LiteRadio |
|
| 21 | -- DJI FPV controller (works with some sims) |
|
| 22 | -- Most transmitters that support USB or simulator mode |
|
| 23 | - |
|
| 24 | - |
|
| 25 | - |
|
| 26 | -## 🆓 Free or Open Source FPV Simulators for PC |
|
| 27 | - |
|
| 28 | -### 🛠 FPV.Skydive (from ORQA) |
|
| 29 | -- ✅ Free on Steam |
|
| 30 | -- 🧠 Beginner-friendly with training modules |
|
| 31 | -- 🎮 Supports many controllers (via USB) |
|
| 32 | -- 📦 Good for freestyle and basic racing |
|
| 33 | -- ❗ Not open-source, but completely free |
|
| 34 | -- 🔗 [Steam Link](https://store.steampowered.com/app/1645840/FPV_Skydive/) |
|
| 35 | - |
|
| 36 | -https://store.steampowered.com/app/1278060/FPV_SkyDive__FPV_Drone_Simulator/ |
|
| 37 | - |
|
| 38 | ---- |
|
| 39 | - |
|
| 40 | -### 🛠 RotorHazard Simulator |
|
| 41 | -- ⚙️ Community-developed simulator inspired by RotorHazard timing system |
|
| 42 | -- 🖥 Lightweight, browser-based or local |
|
| 43 | -- 💻 Not super polished, but interesting for DIY folks |
|
| 44 | -- 🌐 Open-source (GitHub available) |
|
| 45 | -- 🔗 [GitHub Repository](https://github.com/RotorHazard) |
|
| 46 | - |
|
| 47 | ---- |
|
| 48 | - |
|
| 49 | -### 🛠 OpenFPV Simulator (dead?) |
|
| 50 | -- 🌍 Browser-based prototype sim |
|
| 51 | -- 👶 Very basic physics and controls |
|
| 52 | -- 🧑💻 Open-source, you can fork or contribute |
|
| 53 | -- 🔧 Good for devs/hackers/experimenters |
|
| 54 | -- 🔗 [GitHub Link](https://github.com/OpenFPV/openfpv-simulator) |
|
| 55 | - |
|
| 56 | ---- |
|
| 57 | - |
|
| 58 | -### 🛠 Multirotor Sim (Unity-based) (dead?) |
|
| 59 | -- 🧪 Community project with editable Unity source |
|
| 60 | -- 🎮 Supports USB controllers |
|
| 61 | -- 🔧 Needs a bit of setup, but can be modified freely |
|
| 62 | -- 🔗 [GitHub Link](https://github.com/ArduPilot/multirotor_sim) |
|
| 63 | - |
|
| 64 | ---- |
|
| 65 | - |
|
| 66 | -### 📌 Honorable Mentions (Free Trials or Demos) |
|
| 67 | - |
|
| 68 | -#### **FPV Freerider (Demo version)** |
|
| 69 | -- Limited map, but physics work well |
|
| 70 | -- 🔗 [freeriderfpv.com](https://fpv-freerider.itch.io/fpv-freerider-recharged-demo) |
|
| 71 | - |
|
| 72 | ---- |
|
| 73 | - |
|
| 74 | -### 🧭 Recommendation |
|
| 75 | - |
|
| 76 | -- **If you're new and want a polished free experience:** |
|
| 77 | - ➡️ Try **[FPV.Skydive](https://store.steampowered.com/app/1645840/FPV_Skydive/)** |
|
| 78 | - |
|
| 79 | -- **If you're into tinkering or want to code your own sim:** |
|
| 80 | - ➡️ Check out **OpenFPV** or **Multirotor Sim** on GitHub |
|
| 81 | - |
|
| 82 | - |
|
| 83 | - |
|
| 84 | - |
|
| 85 | -## ref |
|
| 86 | - |
|
| 87 | - |
|
| 88 | -- [[FPV-dat]] |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/Goggles-dat/Goggles-dat.md
| ... | ... | @@ -1,7 +0,0 @@ |
| 1 | - |
|
| 2 | -# Goggles-dat |
|
| 3 | - |
|
| 4 | -[DJI Goggles 3, FPV Goggles with Stunning Micro-OLED Screens, Immersive Flight Experience, O4 HD Video Transmission, Adjustable Diopters, Wireless Streaming, Drone Goggles with Real View PiP](https://www.amazon.com/DJI-Micro-OLED-Experience-Transmission-Adjustable/dp/B0CS6L6D6J/ref=sr_1_17?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-17) |
|
| 5 | - |
|
| 6 | - |
|
| 7 | -[Fat Shark Recon Echo FPV Goggles](https://www.amazon.com/Fat-Shark-Recon-Echo-Goggles/dp/B0CTB8VLYQ/ref=sr_1_41?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-41) |
|
| ... | ... | \ No newline at end of file |
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-14-49-45.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-14-49-45.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-15-34-48.png
| ... | ... | Binary files a/app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/2025-05-04-15-34-48.png and /dev/null differ |
app-dat/quadcopter-dat/FPV-dat/betaFPV-dat/betaFPV-dat.md
| ... | ... | @@ -1,4 +0,0 @@ |
| 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
| ... | ... | @@ -1,94 +0,0 @@ |
| 1 | - |
|
| 2 | -# lightradio-dat |
|
| 3 | - |
|
| 4 | -## Lightradio 3 Pro |
|
| 5 | - |
|
| 6 | -- professional version |
|
| 7 | -- build-in OLED display |
|
| 8 | - |
|
| 9 | - |
|
| 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 | - |
|
| 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 |
app-dat/quadcopter-dat/FPV-dat/speedybee-dat/speedybee-dat.md
| ... | ... | @@ -1,7 +0,0 @@ |
| 1 | - |
|
| 2 | -# speedybee-dat |
|
| 3 | - |
|
| 4 | -[SpeedyBee 4pcs FPV Soldering Practice Board for FPV Drone Beginners, Tools for Flight controller ESC Soldering Practice](https://www.amazon.com/SpeedyBee-Soldering-Practice-Beginners-controller/dp/B0C5X26JWQ/ref=sr_1_32?dib=eyJ2IjoiMSJ9.85xi15ftM4OWw33_siXrDRGNOKuf3CgQct4cVlBOFqI1ZAAZD4Gz_S4U_wqEKgjxWcsGOZPlWkdGdEASaTJntO1H_pFgsXO61wuEgveKAmLTLHR-cjsa5SOhaKUXU0vVHE7oijzqLoIPsx-H55gYNPr_F8aMX98OqPfwk64Ma12qrNSidLDVokmdegWL621v3U-5PDEaMNTjdACgOTHEBxAGhtxksaYVouWcSkxMCTI-jr0FkvxyQeZmO6S-UjXJcEcChxa4sPMjVyiK7070XhJlH2EnXqgnv0KScl80Jqc.AzbbGJAa2ls6bQWRCrudB-jGcm6vKV7pRItsIyBMpdA&dib_tag=se&keywords=FPV&qid=1744201259&sr=8-32) |
|
| 5 | - |
|
| 6 | - |
|
| 7 | - |
app-dat/quadcopter-dat/quadcopter-dat.md
| ... | ... | @@ -1,65 +0,0 @@ |
| 1 | - |
|
| 2 | -# quadcopter-dat |
|
| 3 | - |
|
| 4 | - |
|
| 5 | -## opensource |
|
| 6 | - |
|
| 7 | -### cleanfight |
|
| 8 | - |
|
| 9 | -https://github.com/cleanflight/cleanflight |
|
| 10 | - |
|
| 11 | -https://github.com/cleanflight/cleanflight/tree/master/docs |
|
| 12 | - |
|
| 13 | -https://cleanflight.com/ |
|
| 14 | - |
|
| 15 | - |
|
| 16 | -### Openpilot |
|
| 17 | - |
|
| 18 | -## Commerial |
|
| 19 | - |
|
| 20 | -### CJMCU |
|
| 21 | - |
|
| 22 | - |
|
| 23 | - |
|
| 24 | -- https://www.rcgroups.com/forums/showthread.php?2456739-Openpilot-port-to-CJMCU-stm32-quadcopter |
|
| 25 | - |
|
| 26 | -- https://oscarliang.com/build-fpv-micro-quadcopter-smallest-quad/ |
|
| 27 | - |
|
| 28 | -#### new version from https://aeracoop.net/cjmcu2-open-source-brushed-quadcopter/ |
|
| 29 | - |
|
| 30 | -https://github.com/Edragon/cjmcu2 |
|
| 31 | - |
|
| 32 | - |
|
| 33 | - |
|
| 34 | -## BOM |
|
| 35 | - |
|
| 36 | -### receiver |
|
| 37 | - |
|
| 38 | -- [DT 2.4GHz Receivers](https://www.deltang.co.uk/) |
|
| 39 | - |
|
| 40 | - |
|
| 41 | - |
|
| 42 | -### props |
|
| 43 | - |
|
| 44 | - |
|
| 45 | -### motors |
|
| 46 | - |
|
| 47 | - |
|
| 48 | -### motor drive |
|
| 49 | - |
|
| 50 | -- [[mosfet-dat]] |
|
| 51 | - |
|
| 52 | -## forum |
|
| 53 | - |
|
| 54 | -- http://www.multiwii.com/forum |
|
| 55 | -- https://www.rcgroups.com/forums |
|
| 56 | - |
|
| 57 | - |
|
| 58 | - |
|
| 59 | -## hexquadcopter |
|
| 60 | - |
|
| 61 | -- http://www.multiwii.com/forum/viewtopic.php?f=12&t=4893&p=53317#p53317 |
|
| 62 | - |
|
| 63 | -## ref |
|
| 64 | - |
|
| 65 | -- [[quadcopter]] |
|
| ... | ... | \ No newline at end of file |
weekly-dat/2025-May-dat/2025-May-dat.md
| ... | ... | @@ -9,7 +9,8 @@ This a weekly update newsletter, to briefly tell you whats new and whats fun we |
| 9 | 9 | |
| 10 | 10 | ## Development, Documents Updates |
| 11 | 11 | |
| 12 | -- greate project [[ardupilot-dat]], going to build a [[rover-dat]] |
|
| 12 | +- greate project [[ardupilot-dat]], going to build a [[rover-dat]], further complete [[RC-dat]] info |
|
| 13 | + |
|
| 13 | 14 | |
| 14 | 15 | ## Dissusion, Feedback, To-do |
| 15 | 16 |
weekly-dat/weekly-dat.md
| ... | ... | @@ -24,7 +24,7 @@ |
| 24 | 24 | | 15 | Apr 7 | Apr 13 | [[2024-April-dat]] | |
| 25 | 25 | | 16 | Apr 14 | Apr 20 | [[2024-April-dat]] | |
| 26 | 26 | | 17 | Apr 21 | Apr 27 | [[2024-April-dat]] | |
| 27 | -| 18 | Apr 28 | May 4 | | |
|
| 27 | +| 18 | Apr 28 | May 4 | [[2025-May-dat]] | |
|
| 28 | 28 | | 19 | May 5 | May 11 | | |
| 29 | 29 | | 20 | May 12 | May 18 | | |
| 30 | 30 | | 21 | May 19 | May 25 | | |