fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-20 23:33:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Codespell check on English sources + swd fixes (#26657)

Browse Source
This commit is contained in:
Hamish Willee
2026-03-05 12:50:59 +11:00
committed by GitHub
parent 5528ebec64
commit b37733459d
96 changed files with 180 additions and 174 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/frames_plane/reptile_dragon_2.md
+3 -3
View File
@@ -81,7 +81,7 @@ The airplane needs some assembly out of the box.
Servos, wings, and the tail will need to be installed.
::: info
For this portion of assembly, the instructions included with the kit should be sufficent, but some helpful tips are listed below.
For this portion of assembly, the instructions included with the kit should be sufficient, but some helpful tips are listed below.
:::
### Gluing Foam
@@ -209,7 +209,7 @@ An alternative carrier board is the Holybro Pixhawk 5X carrier.
The carrier comes installed in a plastic case.
While the case does look nice, it is extra weight, so the carrier was removed from the case.
Once removed from the case, the ARK6X was installed, and a protective cover fitted ontop.
Once removed from the case, the ARK6X was installed, and a protective cover fitted on top.
![Flight computer carrier board](../../assets/airframes/fw/reptile_dragon_2/holybro_5x.jpg)
@@ -337,7 +337,7 @@ For more information see [TBS Crossfire (CRSF) Telemetry](../telemetry/crsf_tele
### `msp_osd` Module
The `msp_osd` module steams MSP telemetry to a selected serial port.
The `msp_osd` module streams MSP telemetry to a selected serial port.
The Caddx Vista Air Unit supports listening to MSP telemetry and will show the received telemetry values in its OSD (on screen display).
1. In the PX4 board config tool, navigate to the `drivers` submenu, then scroll down to highlight `OSD`.
docs/en/frames_plane/turbo_timber_evolution.md
+6 -6
View File
@@ -78,7 +78,7 @@ A long M3 nylon screw and a washer on the underside, followed by a washer and st
![Window and front fuselage (hatch) with FPV Pod mounted on top](../../assets/airframes/fw/turbo_timber_evolution/fpv_pod_hatch.jpg)
![Underside of hatch showing the FPV pod attachement screws and wires pulled through](../../assets/airframes/fw/turbo_timber_evolution/hatch_underside.jpg)
![Underside of hatch showing the FPV pod attachment screws and wires pulled through](../../assets/airframes/fw/turbo_timber_evolution/hatch_underside.jpg)
## Pitot Pod
@@ -138,7 +138,7 @@ Power for the servo and lighting will be provided by the "BEC" power supply in t
The TTE is very flexible when it comes to battery options.
I use both a 3.6Ah 4S Turnigy pack as well as a Upgrade Energy 4s2p liion pack.
While the 3.6Ah LiPo is inexpensive, nearly twice the flight time (24 minutes vs 12 minutes) can be acheived with the Upgrade Energy Liion pack.
While the 3.6Ah LiPo is inexpensive, nearly twice the flight time (24 minutes vs 12 minutes) can be achieved with the Upgrade Energy Liion pack.
![Image of batteries used for the build](../../assets/airframes/fw/turbo_timber_evolution/batteries.jpg)
@@ -165,10 +165,10 @@ Similarly, a JST PH to std spaced headers adapter was made, and it was also left
#### RC Receiver
A custom cable was made to connect the ExpressLRS RX ([RC Reciever](../getting_started/rc_transmitter_receiver.md)) to the Pixhawk 4 Mini.
A custom cable was made to connect the ExpressLRS RX ([RC Receiver](../getting_started/rc_transmitter_receiver.md)) to the Pixhawk 4 Mini.
Because the Pixhawk 4 Mini has limited uarts, the RX was connected to RC input which does not have a TX pin.
This means that the RX will only send control data to the FCU but telemtry cannot be sent to the RX from the FCU.
This means that the RX will only send control data to the FCU but telemetry cannot be sent to the RX from the FCU.
Heatshrink was used to secure the dupont connector of the cable such that it cannot back out off the headers of the ExpressLRS RX.
#### FPV Pod & Airspeed Cable
@@ -177,7 +177,7 @@ Another custom cable was made to connect the Caddx Vista FPV transmitter to the
A Molex microfit was added close to the Vista so that it could be easily disconnected without needing to gain access to the Pixhawk.
As the name implies, the `UART/I2C B` port provides both a UART and I2C interface.
This port is split with the custom cable and one side provides power and data to the I2C airspeed sensor, while the other side provides power and UART TX/RX to the Caddx Vista.
From the UART/I2C B port, 5V, GND, and I2C SCL/SDA, are connected to the I2C airspeed sensor, while just serial RX and TX are connected to the Caddx Vista (Ground is provided the seperate battery power/gnd leads for the Vista)
From the UART/I2C B port, 5V, GND, and I2C SCL/SDA, are connected to the I2C airspeed sensor, while just serial RX and TX are connected to the Caddx Vista (Ground is provided the separate battery power/gnd leads for the Vista)
The [msp_osd](../modules/modules_driver.md#msp-osd) module is used to stream telemetry to the Caddx Vista which can be seen on the DJI Goggles with the "custom OSD" feature enabled.
@@ -192,7 +192,7 @@ Heatshrink was used to electrically insulate the bare board and the radio was in
Overall, this build was a success.
Even with the added weight of the Pixhawk 4 Mini installation, the airplane balances well and has plenty of power to retain its original STOL characterisitics.
Even with the added weight of the Pixhawk 4 Mini installation, the airplane balances well and has plenty of power to retain its original STOL characteristics.
PX4 is easily capable of stabilizing the airplane and fine tuning of the rate loops were accomplished using [fixed-wing autotuning](../config/autotune_fw.md).
The results of tuning can be found in the [parameter file linked below](#parameter-file).