mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-03 15:58:53 +08:00
Move PX4 Guide source into /docs (#24490)
* Add vitepress tree * Update existing workflows so they dont trigger on changes in the docs path * Add nojekyll, package.json, LICENCE etc * Add crowdin docs upload/download scripts * Add docs flaw checker workflows * Used docs prefix for docs workflows * Crowdin obvious fixes * ci: docs move to self hosted runner runs on a beefy server for faster builds Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: don't run build action for docs or ci changes Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: update runners Signed-off-by: Ramon Roche <mrpollo@gmail.com> * Add docs/en * Add docs assets and scripts * Fix up editlinks to point to PX4 sources * Download just the translations that are supported * Add translation sources for zh, uk, ko * Update latest tranlsation and uorb graphs * update vitepress to latest --------- Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Ramon Roche <mrpollo@gmail.com>
This commit is contained in:
Hamish Willee
co-authored by
Ramon Roche
Ramon Roche
parent
8e6d2ebe4a
commit
88d623bedb
@@ -0,0 +1,13 @@
|
||||
# DIY Builds (Fixed-Wing)
|
||||
|
||||
Do-it-yourself (DIY) builds describe how to assemble a vehicle from parts that are sourced separately.
|
||||
|
||||
At the easier end of the scale of DIY builds are those that take an existing RC vehicle and graft on a flight controller.
|
||||
At the harder end of the scale are "unique" vehicles where some parts may be fabricated using a 3D printer.
|
||||
Somewhere in the middle are builds that use separate but readily available components: frame, motors, ESC, propellers, flight controller, and so on.
|
||||
|
||||
DIY Builds:
|
||||
|
||||
- [Reptile Dragon 2 (ARK6X)](../frames_plane/reptile_dragon_2.md)
|
||||
- [Turbo Timber Evolution (../Pixhawk 4 Mini)](../frames_plane/turbo_timber_evolution.md)
|
||||
- [Wing Wing Z84 (Pixracer)](../frames_plane/wing_wing_z84.md)
|
||||
@@ -0,0 +1,38 @@
|
||||
# Planes (Fixed-Wing)
|
||||
|
||||
PX4 supports numerous plane geometries, including normal planes, flying wings, inverted V-tail planes, and so on.
|
||||
|
||||
::: tip
|
||||
The generic configurations can be seen in [Airframes Reference > Plane](../airframes/airframe_reference.md#plane).
|
||||
These can be customized during configuration.
|
||||
:::
|
||||
|
||||
## Overview
|
||||
|
||||
The linked sections instructions for assembling and configuring fixed-wing frames.
|
||||
|
||||
<!-- Features? -->
|
||||
|
||||
- [Assembly](../assembly/assembly_fw.md)
|
||||
- [Config/Tuning](../config_fw/index.md)
|
||||
- [Flying (Basics)](../flying/basic_flying_fw.md)
|
||||
- [Flight Modes](../flight_modes_fw/index.md)
|
||||
- [Complete Vehicles](../complete_vehicles_fw/index.md)
|
||||
- [DIY Builds](../frames_plane/diy_builds.md)
|
||||
|
||||
## Videos
|
||||
|
||||
|
||||
<lite-youtube videoid="VqNWwIPWJb0" params="ab_channel=ChrisSeto" title="Reptile Dragon 2 Demo Flight For Px4 Log Review"/>
|
||||
|
||||
---
|
||||
|
||||
<lite-youtube videoid="vMFCi3G5s6E" title="PX4 Turbo Timber Spot Landing"/>
|
||||
|
||||
---
|
||||
|
||||
<lite-youtube videoid="1DUV7QjcXrA" title="Px4 Turbo timber Evolution Short Flight"/>
|
||||
|
||||
---
|
||||
|
||||
<lite-youtube videoid="8m4_NpTQn0E" title="Solar-powered 81 hour endurance world record flight"/>
|
||||
@@ -0,0 +1,466 @@
|
||||
# Reptile Dragon 2 (RD2) Build
|
||||
|
||||
The Reptile Dragon 2 is a twin motor RC airplane specifically designed for efficient FPV [(first person view)](https://en.wikipedia.org/wiki/First-person_view_(radio_control)) flying.
|
||||
Being specific for FPV, the RD2 is optimized for easy mounting of cameras, sensors, logic electronics, large batteries, antennas, and other payload components which would be found on a typical FPV airplane.
|
||||
This emphasis on payload makes this airplane an ideal candidate for a PX4 installation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Overview
|
||||
|
||||
The goal of this build was to create an efficient, long endurance FPV platform to be used for general PX4 testing and development.
|
||||
|
||||
Key airframe features:
|
||||
|
||||
- Spacious interior
|
||||
- Easy access to the entire fuselage cavity with large top hatch
|
||||
- Rear hatch
|
||||
- Removable V tail or conventional tail options included
|
||||
- Threaded inserts in the wings and fuselage top for external mounting
|
||||
- Numerous mounting features
|
||||
- Top antenna hole
|
||||
- Top GPS cover
|
||||
- Side "T" antenna mounts
|
||||
- Rear electronics tray
|
||||
- Front facing "action cam" cutout
|
||||
- Front facing FPV camera cutout
|
||||
- Removable wings
|
||||
- Low stall speed
|
||||
- Gentle handling
|
||||
|
||||
Key build features
|
||||
|
||||
- Easy overall build
|
||||
- Easy access to Pixhawk and all peripherals
|
||||
- FPV with camera pan mount
|
||||
- Air data from pitot/static probe
|
||||
- ~40 minute long flight times
|
||||
|
||||
## Parts list
|
||||
|
||||
- [Reptile Dragon 2 kit](https://usa.banggood.com/REPTILE-DRAGON-2-1200mm-Wingspan-Twin-Motor-Double-Tail-EPP-FPV-RC-Airplane-KIT-or-PNP-p-1805237.html?cur_warehouse=CN&ID=531466)
|
||||
|
||||
- [ARK6X FMU](https://arkelectron.com/product/arkv6x/)
|
||||
- [ARK6X carrier](https://arkelectron.com/product/ark-pixhawk-autopilot-bus-carrier/)
|
||||
- [Alternative FMU carrier: Holybro Pixhawk 5x Carrier board](https://holybro.com/products/pixhawk-baseboards)
|
||||
- [Holybro power module](https://holybro.com/products/pm02d-power-module)
|
||||
- [Holybro M9N GPS module](https://holybro.com/products/m9n-gps)
|
||||
- Holybro PWM breakout board
|
||||
- MS4525DO differential pressure module and pitot tube
|
||||
- [Caddx Vista FPV air unit](https://caddxfpv.com/products/caddx-vista-kit)
|
||||
- [Emax ES08MA ii](https://emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo)
|
||||
- [DJI FPV Goggles](https://www.dji.com/fpv)
|
||||
- [ExpressLRS Matek Diversity RX](http://www.mateksys.com/?portfolio=elrs-r24)
|
||||
- [5V BEC](https://www.readymaderc.com/products/details/rmrc-3a-power-regulator-5-to-6-volt-ubec)
|
||||
- [6s2p 18650 LiIon flight battery](https://www.upgradeenergytech.com/product-page/6s-22-2v-5600mah-30c-dark-lithium-liion-drone-battery) (select XT60 connector)
|
||||
- [Custom designed 3D printed parts](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/reptile_dragon_2/rd2_3d_printed_parts.zip)
|
||||
- ARK6X carrier mount
|
||||
- Holybro Pixhawk 5x carrier mount
|
||||
- FPV pod and camera mount
|
||||
- Pitot static probe "plug" adapter
|
||||
- [Custom designed power distribution PCB](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/reptile_dragon_2/xt30_power_distro_pcb.zip)
|
||||
- Misc hardware: M3 hardware (standoffs, washers, O-rings, bolts), M2.5 nylon standoffs and screws, XT30 connectors, hot glue, heatshrink, Molex Microfit connectors
|
||||
- Silicone wiring (14awg for high current, 16awg for low current, 22awg for low power and signals)
|
||||
|
||||
## Tools
|
||||
|
||||
The following tools were used in this assembly.
|
||||
|
||||
- Servo tester (with centering button)
|
||||
- Screw driver set
|
||||
- 3D printer
|
||||
- Wrench set
|
||||
- Glue: Hot glue, CA (Cyanoacrylate) glue, "Foamtac" glue
|
||||
- Sandpaper
|
||||
|
||||
## Airframe Build
|
||||
|
||||
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.
|
||||
:::
|
||||
|
||||
### Gluing Foam
|
||||
|
||||
When gluing foam parts of the RD2 together, use sandpaper to rough the mating surface, then use CA glue.
|
||||
If the foam is not roughed with sandpaper, the glue will not have a surface to be able to "grab" the foam and the bond will be poor.
|
||||
|
||||
Foamtac doesn't seem to stick well to this foam, so I used CA glue for all foam-to-foam mates.
|
||||
|
||||
### Skid Plate
|
||||
|
||||
The skid plate that comes with the RD2 needs to be trimmed to fit.
|
||||
|
||||
|
||||
|
||||
Trim off the mold flashing from the flat side of the skid plate.
|
||||
Use coarse sandpaper to rough the inside surface of the skid plate as well as the mating surface on the underside of the airframe.
|
||||
After checking for fit, use CA glue to glue the skid plate to the bottom of the RD2.
|
||||
|
||||
### Servo Installation
|
||||
|
||||
::: info
|
||||
Prior to servo installation, it is recommended to use the sandpaper to rough the side of the servo facing the servo cover. During final installation, put a drop of Foamtac between the servo and the cover. This will prevent the servo from moving once installed.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
The servos on the RD2 are connected to control surfaces with adjustable servo linkages.
|
||||
The RD2 instructions will note that each control surface uses a specific length of linkage (included in the kit).
|
||||
Make sure to measure each linkage before installation to be sure that it is the right length linkage for that control surface.
|
||||
It's very important to align the servos such that the mechanical range of the servo is well aligned with the mechanical range of the control surface.
|
||||
When the servo is at it's center point, the servo arm should be at a 90 degree angle to the servo, and the control surface should be roughly centered.
|
||||
It might not be possible to get this alignment perfect, so any remaining offset will be adjusted out in software.
|
||||
|
||||
The following steps can be used to perform servo alignment:
|
||||
|
||||
1. Begin with the servo outside of the airplane
|
||||
2. Use the servo tester to move the servo to its center point
|
||||
3. Install the servo horn with the included retaining screw, taking care to align the horn to extend as close as possible to 90 degrees out on the correct side of the servo
|
||||
4. Install the servo in the servo pocket on the airplane
|
||||
5. Install the linkage, and twist to adjust it such that the control surface is as close to centered as possible
|
||||
|
||||
::: info
|
||||
The servo horn will likely not sit exactly at a 90 degree angle to the servo due to the teeth on the servo shaft.
|
||||
You can see this in the above example setup image.
|
||||
Just get it close enough to 90 degrees, and the remaining offset will be removed either with the linkage, or later in software.
|
||||
:::
|
||||
|
||||
## GPS/Compass Module Mounting
|
||||
|
||||
The GPS/Compass should be mounted in the rear electronics shelf included with the RD2.
|
||||
This location is far aft of power wiring (and anything else that might cause magnetic disturbances), which makes for an ideal location for the GPS/compass module
|
||||
|
||||
|
||||
|
||||
The GPS module can be removed from its plastic case to allow the use of the mounting holes.
|
||||
Then use the nylon M3 hardware to attach it to the rear electronics shelf.
|
||||
|
||||
Two of the three required holes are already coincidentally located in the electronics tray, so I used a marker and a drill to mark and drill the third hole.
|
||||
|
||||
|
||||
## FPV Pod
|
||||
|
||||
### FPV Pod Assembly
|
||||
|
||||
First, mount the ES08MA ii servo in the servo pocket of the FPV pod.
|
||||
The servo should simply slip in, with the cable exiting the FPV Pod through the hole in the servo pocket.
|
||||
Use a dot of Foamtac glue to secure the servo.
|
||||
|
||||
|
||||
|
||||
Use one of the servo horns included in the ES08ma ii package.
|
||||
Cut the horn such that it fits in the slot in the FPV pod camera carrier.
|
||||
It should sit flush to the bottom of the slot.
|
||||
Secure the horn with CA glue.
|
||||
|
||||
Use the servo tester to center the servo.
|
||||
Attach the camera carrier servo horn directly to the top of the servo and secure it with the included screw.
|
||||
Secure the DJI FPV camera into the carrier with the two side screws.
|
||||
|
||||
To finish the FPV pod assembly, install the Caddx Vista to the back of the pod using long M2 bolts, 1mm standoffs, and nylock nuts.
|
||||
|
||||
|
||||
|
||||
### FPV Pod Airframe Installation
|
||||
|
||||
The FPV pod was mounted on top of the battery hatch using nylon M3 bolts with two O-rings to space the FPV pod base plate from the battery hatch.
|
||||
|
||||
## Flight Computer Installation
|
||||
|
||||
::: info
|
||||
This build is compatible with both the ARK6X carrier and the Holybro 5X Carrier.
|
||||
Instructions are provided for both.
|
||||
:::
|
||||
|
||||
|
||||
The RD2 comes with a wooden electronics mount baseplate preglued in the airframe.
|
||||
In this image, two sets of marker ticks are used to indicate where the mounts for each carrier mount should back up to; the single tik for the Holybro 5X carrier mount, and the two ticks for the ARK5X carrier mount.
|
||||
|
||||
### ARK6X Carrier (Recommended)
|
||||
|
||||
A custom 3D printed mount was made for the ARK6X carrier.
|
||||
M2.5 nylon hardware was used to secure the ARK6X carrier to the mount.
|
||||
|
||||
|
||||
|
||||
|
||||
The ARK6X carrier doesn't have normal servo output connectors.
|
||||
Instead, it has a single JST GH connector which carries the 8 FMU servo outputs.
|
||||
A Holybro PWM breakout board was used to split the single JST GH PWM output connector into 8 individual servo channels.
|
||||
|
||||
|
||||
|
||||
The ARK6X carrier is shown here mounted to the base plate.
|
||||
Note the aft end of the carrier aligned against the two tick marks.
|
||||
|
||||
|
||||
|
||||
Finally, the ARK6X was installed on top of the mount.
|
||||
|
||||
|
||||
|
||||
|
||||
### Holybro 5X Carrier (Optional)
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
A custom mount for the Pixhawk 5X carrier board was designed and 3D printed.
|
||||
This mount adapts the RD2's internal mounting plate hole pattern to the mounting holes on the Pixhawk 5X carrier board.
|
||||
|
||||
|
||||
|
||||
It's important to install this mount in the correct location inside the RD2; as far aft as possible.
|
||||
With a large battery and the FPV pod up front, the airplane will tend to be noseheavy.
|
||||
Mounting the flight computer far aft will help to keep the airframe center of gravity (CG) in the correct location.
|
||||
|
||||
|
||||
|
||||
The images above show the fully completed and connected Holybro 5X carrier installation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Electrical
|
||||
|
||||
### Battery Power Distribution
|
||||
|
||||
Battery power is routed through the Holybro Power module, then to a custom designed power distribution PCB (printed circuit board).
|
||||
From the power distribution board, battery power is split to the BEC, both ESCs, and Caddx Vista through separate XT30 connectors.
|
||||
|
||||
|
||||
|
||||
Without the custom PCB, it's still easy to distribute power to all the components in the airplane.
|
||||
This image shows an alternative solution constructed from an XT60 connecter wired to several XT30 connectors.
|
||||
The servo power BEC is also shown in this image.
|
||||
|
||||
|
||||
|
||||
|
||||
### Servo Power
|
||||
|
||||
Because the Holybro carrier does not include an onboard servo power supply, an external ["BEC"](https://en.wikipedia.org/wiki/Battery_eliminator_circuit) is used to provide power to the servos.
|
||||
The input leads of the EC were soldered to a XT30 connector which was plugged into the power distribution board.
|
||||
The output of the BEC can be plugged into any unused servo output (I chose IO output 8).
|
||||
|
||||
### ESCs & Motors
|
||||
|
||||
|
||||
|
||||
Bullet connectors were soldered to 16awg leads, which were then soldered to each phase output on each ESC.
|
||||
Heatshrink was shrunk over the finished ESCs and the bullet connectors from the ESCs were connected to their respective motors.
|
||||
|
||||
Motor direction depends on the order of the motor leads connected to the ESC.
|
||||
For now, take a guess on each side. If either motor is spinning the wrong way, the direction can be swapped by swapping any two connections.
|
||||
Correct motor direction will be checked in the final preflight checks.
|
||||
|
||||
### Servos & ESC Signal Leads
|
||||
|
||||
Servos were wired to the FMU out port in the order left aileron, right aileron, left ESC, right ESC, elevator, rudder, FPV pan.
|
||||
|
||||
::: info
|
||||
[DSHOT ESC](../peripherals/dshot.md#wiring-connections) were used (not PWM as for the servos).
|
||||
To make efficient use of the [DSHOT output port restrictions](../peripherals/dshot.md#wiring-connections), the two ESCs must be wired to FMU output channels 3 and 4.
|
||||
:::
|
||||
|
||||
### Airspeed Sensor & Pitot Tube
|
||||
|
||||
The airspeed sensor was connected to the I2C port on the FMU carrier board with the supplied JST GH I2C cable.
|
||||
|
||||
|
||||
|
||||
The pitot tube was pushed through the pitot tube mount and then installed in the front fpv camera cut out.
|
||||
|
||||
The pitot/static hoses were cut to length and installed to connect the pitot static probe to the airspeed sensor.
|
||||
Finally, the pitot static sensor was taped to the sidewall of the airframe (using double sided tape).
|
||||
|
||||
### ELRS RX
|
||||
|
||||
A custom cable was made to connect the ELRS RX to the JST GH `TELEM2` port of the FMU carrier board.
|
||||
|
||||
|
||||
|
||||
The other end of the cable was terminated to a Dupont connector to connect to the standard spaced headers on the ELRS RX.
|
||||
The ELRS RX was connected to the cable, and then heatshrink was used to secure the two together.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
A thin radio antenna tube was pushed through the top of the airframe used to mount one of the two ELRS diversity antennas upright.
|
||||
The second diversity antenna was taped to the sidewall of the airframe, 90 degrees from the alignment of the first antenna.
|
||||
The ELRS RX was attached to the sidewall of the airframe next to the airspeed pressure sensor, using double-sided tape.
|
||||
|
||||
### USB
|
||||
|
||||
A right angle USB C extension cable was used to allow easy access to the USB C port on the FMU.
|
||||
|
||||
|
||||
|
||||
The cable was installed such that it escapes the pixhawk heading towards the aft of the airplane. The cable continues to run to the rear hatch, where the excess length can be securely wound into a knot.
|
||||
Access to this cable can be accomplished by simply removing the rear hatch and unknotting the cable.
|
||||
|
||||
## Firmware Build
|
||||
|
||||
You can't use prebuilt PX4 release (or main) firmware for this vehicle, as it depends on PX4 modules [crsf_rc](../modules/modules_driver.md#crsf-rc) and [msp_osd](../modules/modules_driver.md#msp-osd) that are not included by default.
|
||||
|
||||
These require some custom configuration to enable.
|
||||
|
||||
First, follow [this guide to setup a development environment](../dev_setup/dev_env.md ) and [this guide to get the PX4 source code](../dev_setup/building_px4.md).
|
||||
|
||||
Once a build environment has been setup, open a terminal and `cd` into the `PX4-Autopilot` directory.
|
||||
To launch the [PX4 board config tool (`menuconfig`)](../hardware/porting_guide_config.md#px4-menuconfig-setup) run:
|
||||
|
||||
```
|
||||
make ark_fmu-v6x_default boardconfig
|
||||
```
|
||||
|
||||
### `crsf_rc` Module
|
||||
|
||||
PX4 includes a standalone CRSF parser module which supports telemetry and CRSF LinkStatistics.
|
||||
To use this module, the default `rc_input` module must be disabled and the `crsf_rc` module must be enabled.
|
||||
|
||||
1. In the PX4 board config tool, navigate to the `drivers` submenu, then scroll down to highlight `rc_input`.
|
||||
2. Use the enter key to remove the `*` from `rc_input` checkbox.
|
||||
3. Scroll to highlight the `RC` submenu, then press enter to open it.
|
||||
4. Scroll to highlight `crsf_rc` and press enter to enable it.
|
||||
5. Save and exit the PX4 board config tool.
|
||||
|
||||
For more information see [TBS Crossfire (CRSF) Telemetry](../telemetry/crsf_telemetry.md).
|
||||
|
||||
### `msp_osd` Module
|
||||
|
||||
The `msp_osd` module steams 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`.
|
||||
2. Use the enter key to open the `OSD` submenu
|
||||
3. Scroll down to highlight `msp_osd` and press enter to enable it
|
||||
|
||||
### Building & Flashing
|
||||
|
||||
Once the `msp_osd` and `crsf_rc` modules are enabled and the `rc_input` module is disabled, the firmware source must be compiled and the resulting image flashed to the FMU.
|
||||
|
||||
To compile and flash the firmware, connect the FMU/Carrier to the build host PC via USB and run:
|
||||
|
||||
```
|
||||
make ark_fmu-v6x_default upload
|
||||
```
|
||||
|
||||
## PX4 Configuration
|
||||
|
||||
### Parameter Config
|
||||
|
||||
This param file contains the custom PX4 parameter configuration for this build, including radio setup, tuning and sensor config.
|
||||
Load the file via QGC using the instructions at [Parameters> Tools](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/parameters.html#tools) (QGC User Guide).
|
||||
|
||||
- [Snapshot of PX4 airframe params](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/reptile_dragon_2/reptile_dragon_2_params.params)
|
||||
|
||||
|
||||
You may need to modify some parameters for your build
|
||||
In particular you should check:
|
||||
|
||||
- [MSP_OSD_CONFIG](../advanced_config/parameter_reference.md#MSP_OSD_CONFIG) param must match serial port which is connected to the Caddx Vista (in this build, `/dev/ttyS7`).
|
||||
- [RC_CRSF_PRT_CFG](../advanced_config/parameter_reference.md#RC_CRSF_PRT_CFG) param must match the serial port which is connected to the ELRS RX (in this build, `Telem 1`).
|
||||
|
||||
### Radio Setup
|
||||
|
||||
You should enable Manual, Acro, and Position modes on your controller (at least for the first flight).
|
||||
For instructions see [Flight mode Configuration](../config/flight_mode.md)
|
||||
|
||||
We also recommend configuring an [autotuning switch](../config/autotune_fw.md#enable-disable-autotune-switch) for the first flight, as this makes it easier to enable/disable autotuning while flying.
|
||||
|
||||
The channel mappings for this build are included in the supplied [params file](#parameter-config).
|
||||
The channel order is throttle, roll, pitch, yaw, (blank), and flight mode
|
||||
|
||||
::: info
|
||||
ExpressLRS requires `AUX1` as an "arming channel".
|
||||
This arming channel is separate from PX4's arming mechanism and is used to tell the ELRS TX that is can switch into high transmit power.
|
||||
|
||||
In the PX4 channel mappings, I simply skip over this channel.
|
||||
On my transmitter, this channel is set to always be "high", so ELRS is always armed.
|
||||
:::
|
||||
|
||||
### Motor Setup & Prop Installation
|
||||
|
||||
Motors and flight control surface setup done in the [Actuator](../config/actuators.md) section.
|
||||
The supplied [params file](#parameter-config) maps the actuators as described in this build.
|
||||
|
||||
The RD2 kit comes with clockwise and counter clockwise propellers for counter rotating motors.
|
||||
With counter rotating props, the airplane can be set up such that it has no [critical motors](https://en.wikipedia.org/wiki/Critical_engine).
|
||||
|
||||
With no critical motors, controllability will be maximized if a motor fails.
|
||||
The motor direction should be set such that props should turn towards the fuselage on top of the plane.
|
||||
In other words, if you look at the left motor with the airplane facing away from you, it should spin clockwise while the right motor should spin counter clockwise.
|
||||
|
||||
With the propellers removed, power the airplane up and use the [Actuator](../config/actuators.md) test in QGC to spin up the motors.
|
||||
If the left or right motor does not spin in the correct direction, swap two of its ESC leads and check it again.
|
||||
Finally, when both motors are spinning the correct directions, use a wrench to attach the propellers.
|
||||
|
||||
## Final Checks
|
||||
|
||||
Prior to the first flight, a comprehensive preflight must be conducted.
|
||||
|
||||
I recommend checking the following items:
|
||||
|
||||
- Sensor calibration (QGC)
|
||||
- Mag calibration
|
||||
- Accelerometer calibration
|
||||
- Airspeed calibration
|
||||
- Level horizon calibration
|
||||
- Check control surface deflection
|
||||
- Right stick -> Right aileron goes up, left aileron goes down
|
||||
- Left stick -> Left aileron goes up, right aileron goes down
|
||||
- Stick back -> elevator goes up
|
||||
-Stick forward -> elevator goes down
|
||||
- Left rudder -> Rudder goes left
|
||||
- Right rudder -> Rudder goes right
|
||||
- Check Px4 inputs (in `stabilized mode`)
|
||||
- Roll right -> Right Aileron goes down
|
||||
- Roll left -> Left aileron goes down
|
||||
- Pitch up -> Elevator goes down
|
||||
- Pitch down -> Elevator goes up
|
||||
|
||||
|
||||
## First Flight
|
||||
|
||||
I recommend performing the first takeoff in manual mode.
|
||||
Because this airplane has no landing gear, you will either need to throw the airplane yourself, or ideally have a helper throw it.
|
||||
When throwing any airplane, throw at a slightly nose up attitude with full throttle.
|
||||
|
||||
It's critical to be ready to give aft stick input to prevent the airplane from impacting the ground if it happens to be trimmed nosedown.
|
||||
Once the airplane is successfully airborne, cruise up to an altitude of a few hundred feet and switch to [Acro mode](../flight_modes_fw/acro.md).
|
||||
This is a good time to use [Autotuning](../config/autotune_fw.md) to tune the airframe.
|
||||
|
||||
If the airplane is well behaved in _Acro mode_, switch to [Position mode](../flight_modes_fw/position.md).
|
||||
|
||||
## Build Results & Performance
|
||||
|
||||
Overall, this build was a success.
|
||||
The RD2 flies well in this configuration and has plenty of room onboard for sensors and additional hardware.
|
||||
|
||||
### Performance
|
||||
|
||||
- Stall speed: 15mph indicated
|
||||
- Cruise speed: 35-50mph
|
||||
- Endurance: ~40 minutes at 28mph
|
||||
|
||||
### Videos & Flight Logs
|
||||
|
||||
[Demo Flight log](https://review.px4.io/plot_app?log=6a1a279c-1df8-4736-9f55-70ec16656d1e)
|
||||
|
||||
FPV video of flight log:
|
||||
|
||||
<lite-youtube videoid="VqNWwIPWJb0" params="ab_channel=ChrisSeto" title="Reptile Dragon 2 Demo Flight For Px4 Log Review"/>
|
||||
@@ -0,0 +1,233 @@
|
||||
# Turbo Timber Evolution (TTE) Build
|
||||
|
||||
The Turbo Timber Evolution is a model sold by Horizon Hobby originally intended for classic line-of-sight RC model flying.
|
||||
This model is designed to excel at [STOL](https://en.wikipedia.org/wiki/STOL) flying and has a number of notable traits that also make it an ideal candidate to be converted into a FPV PX4 platform.
|
||||
|
||||
|
||||
|
||||
## Overview
|
||||
|
||||
The goal of this build was to create a platform which could be used for general PX4 testing/development.
|
||||
That design goal meant that naturally balanced controls representative of a "vanilla" airplane were desirable.
|
||||
Because classic RC planes are usually designed to be hand flown with no computer augmented flight controls, they tend to be specifically designed to be well trimmed and balanced out of the box.
|
||||
These airplanes also have more attention devoted to making sure they handle well in the air.
|
||||
While it's possible to fly even the most simple foamboard airplane, a lot of nuance in airborne handling can be finessed with a bit more engineering effort.
|
||||
This airplane is a premium example of that, with features like frise ailerons to minimize adverse yaw.
|
||||
|
||||
Key airframe features:
|
||||
|
||||
- Spacious interior
|
||||
- Top battery hatch
|
||||
- Optional leading edge slats
|
||||
- Fowler flaps
|
||||
- Rugged landing gear with steering tailwheel
|
||||
- Exterior lighting pre installed
|
||||
- Optional floats
|
||||
- Gentle flying characteristics
|
||||
- Low drag with internal linkages and minimal protrusions
|
||||
|
||||
Key Build Features:
|
||||
|
||||
* Easy overall build with minimal airframe setup
|
||||
* Easy access to Pixhawk USB and debug connector
|
||||
* [First Person View (FPV)](https://en.wikipedia.org/wiki/First-person_view_(radio_control)) with camera pan mount
|
||||
|
||||
* Air data provided by wing slung pitot static pod
|
||||
* Long flight times (with Liion battery option > 24 minutes)
|
||||
|
||||
## Parts List
|
||||
|
||||
- [Turbo Timber Evolution PNP (includes motor, servos, esc, etc, all fully installed)](https://www.horizonhobby.com/product/turbo-timber-evolution-1.5m-pnp-includes-floats/EFL105275.html#)
|
||||
- [80A Plush-32 ESC](https://hobbyking.com/en_us/turnigy-plush-32-80a-2-6s-brushless-speed-controller-w-bec-rev1-1-0.html)
|
||||
- [Pixhawk 4 Mini](../flight_controller/pixhawk4_mini.md) (with GPS and Power module)
|
||||
|
||||
- [SIK telemetry radio](../telemetry/sik_radio.md)
|
||||
|
||||
- MS4525DO differential pressure module and pitot tube
|
||||
- [Caddx Vista FPV air unit](https://caddxfpv.com/products/caddx-vista-kit)
|
||||
- [DJI FPV Goggles](https://www.dji.com/fpv)
|
||||
- [ExpressLRS Matek Diversity RX](http://www.mateksys.com/?portfolio=elrs-r24)
|
||||
- [Custom designed 3D printed parts](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/turbo_timber_evolution/3d_printed_parts.zip)
|
||||
- Pixhawk 4 Mini mount and top GPS mount
|
||||
- FPV pod and camera mount
|
||||
- Pitot static pod and wing hardpoint hanger
|
||||
- Misc hardware: M3 hardware (standoffs, washers, bolts), XT30 connector, hot glue, heatshrink, Molex Microfit connectors
|
||||
- Silicone wiring (14awg for high current, 16awg for low current, 22awg for low power and signals)
|
||||
- 3.6Ah 4S LiPo OR 4s2p 18650 LiIon
|
||||
|
||||
## Airframe Build
|
||||
|
||||
The vehicle comes out of the box near complete.
|
||||
Servos and linkages have already been installed, and the only real remaining work is installing the landing gear and horizontal stabilizer.
|
||||
For this portion of the assembly, simply follow the manual.
|
||||
|
||||
::: info
|
||||
[Some reports](https://www.rcgroups.com/forums/showthread.php?3904021-NEW-E-flite-Turbo-Timber-Evolution-1-5m-%C2%96-Smartest-Most-Capable-Durable-Timber-Yet/page50) have indicated that the stock ESC bundled with the airplane has an issue with overheating.
|
||||
|
||||
As this build will be especially heavy, and therefore likely demand higher average power from the ESC, the stock 60A ESC was replaced with an 80A Turnigy PLUSH-32 during testing.
|
||||
The stock motor was also replaced with a [higher power motor](https://hobbyking.com/en_us/turnigy-aerodrive-sk3-3548-840kv-brushless-outrunner-motor.html).
|
||||
The stock propeller was replaced with an [APC 13x4](https://www.apcprop.com/product/13x4/) for better efficiency than the stock tri-blade prop.
|
||||
This new ESC, motor, and propeller combination performs well in testing.
|
||||
:::
|
||||
|
||||
## FPV Pod
|
||||
|
||||
The FPV pod was mounted on top of the battery hatch using M3 nylon hardware.
|
||||
Mounting holes for the pod were located by placing the FPV pod on top (being careful to center it with a ruler) and then punching through the fpv pod mounting holes into the foam with a screwdriver.
|
||||
A long M3 nylon screw and a washer on the underside, followed by a washer and standoff on the top of the battery hatch, were then be used to mount the FPV pod.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Pitot Pod
|
||||
|
||||
An [airspeed sensor](../sensor/airspeed.md) is highly recommended for use on fixed-wing vehicles.
|
||||
This build uses a MS4525DO differential pressure module and pitot tube housed in a 3D printed pod that has a hardpoint hanger for connecting it to the wing.
|
||||
|
||||
|
||||
|
||||
Inside the pitot pod, the MS4525DO differential pressure sensor is connected to the pitot/static tube with a short length of tubing.
|
||||
Zipties are used as hoseclamps to prevent the tubing from backing off the sensor and pitot ports.
|
||||
The i2c and power leads were soldered directly to the MS4525 module, and then hotglue was used to mechanically reinforce the connections.
|
||||
|
||||
|
||||
|
||||
The pitot/static differential pressure sensor was mounted on the wing (outside the radius of the prop) using a 3D printed "hanger" glued to the leading edge of the wing.
|
||||
An M2 screw and nylock hold the pod to the hanger.
|
||||
|
||||
|
||||
|
||||
These four leads were then taped to the underside of the wing running back to the Pixhawk 4 Mini.
|
||||
|
||||
The lid of the pitot pod was initially taped in place to allow the setup to be tested and modified if needed after first flight.
|
||||
After the first flight, the lid was hot glued in place.
|
||||
|
||||
## Flight Computer Installation
|
||||
|
||||
A custom mount for the PX4 Mini was designed and 3d printed (see [3D printed parts](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/turbo_timber_evolution/3d_printed_parts.zip) for all parts).
|
||||
This mount was carefully designed to use internal foam mold features of the stock TTE airframe to be securely attached and well aligned.
|
||||
The mount consists of two parts in a double-decker configuration, bolted together with M3 threaded standoffs.
|
||||
The bottom mount carries the Pixhawk and attaches to the airframe while the top mount carries the GPS and ExpressLRS RX.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
First, the Pixhawk 4 Mini was placed in the lower mount.
|
||||
Hot glue was added to rigidly connect the fcu to the mount with two zipties providing additional security.
|
||||
The standoff mounts for the upper mount were installed, and the bolts securely tightened.
|
||||
Once the lower mount is installed, these screws are inaccessible, so attention was paid to making sure they were tightt enough so they cannot back out.
|
||||
|
||||
## Electrical
|
||||
|
||||
### Power
|
||||
|
||||
The Holybro power module was wired inline with the ESC.
|
||||
A spare 16awg power lead was also broken out, terminated to an XT30.
|
||||
This spare lead will be used to provide power to the Caddx Vista FPV unit, but could also be connected to a splitter to power more peripherals.
|
||||
Power for the servo and lighting will be provided by the "BEC" power supply in the ESC.
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
### Servos
|
||||
|
||||
Servos were wired to the flight computer in order of aileron, elevator, rudder, throttle, flaps, and FPV pan.
|
||||
An additional power plug for the lighting system needs to also be installed, but it does not carry a servo signal so it can be put on any spare channel.
|
||||
|
||||
The [Acutator Configuration](../config/actuators.md) screen is shown below.
|
||||
|
||||
|
||||
|
||||
Servo endpoints were obtained by using a servo tester to determine the servo PWM pulse width to reach the max travel of each surface in each direction.
|
||||
|
||||
### Config & Debug
|
||||
|
||||
Access to the Pixhawk 4 Mini requires removal of the upper mount.
|
||||
While this isn't too difficult, it was a consideration for wanting to streamline debugging in the field.
|
||||
A short right angle USB micro extension was used to allow easy access to the Pixhawk 4 Mini's USB interface.
|
||||
The USB-A end of this cable was left dangling in the battery bay.
|
||||
Similarly, a JST PH to std spaced headers adapter was made, and it was also left easily accessible in the battery bay.
|
||||
|
||||
### Peripherals
|
||||
|
||||
#### 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.
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
Another custom cable was made to connect the Caddx Vista FPV transmitter to the FCU UART (from the `UART/I2C B` port) and battery power from the Holybro power module.
|
||||
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)
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
#### SIK Telemetry Radio
|
||||
|
||||
The plastic case of the SIK telemetry radio was removed to reduce weight and decrease volume of the module.
|
||||
Heatshrink was used to electrically insulate the bare board and the radio was installed between the upper and lower flight computer mounts.
|
||||
|
||||
## Build Results & Performance
|
||||
|
||||
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.
|
||||
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).
|
||||
|
||||
In testing I found takeoffs can be as short as only 10ft (3m) using no flaps.
|
||||
I use full flaps on landing to slow the otherwise slippery airframe.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Performance
|
||||
|
||||
- Stall speed (no flaps): 14MPH indicated
|
||||
- Cruise speed: 35-65MPH
|
||||
- Takeoff roll (with full flaps): < 10ft
|
||||
- Endurance: ~24 minutes on 5.2Ah 4s2p LiIon, ~12 minutes on 3.6Ah 4S LiPo
|
||||
|
||||
### Videos
|
||||
|
||||
<lite-youtube videoid="vMFCi3G5s6E" title="PX4 Turbo Timber Spot Landing"/>
|
||||
|
||||
---
|
||||
|
||||
<lite-youtube videoid="1DUV7QjcXrA" title="PX4 Turbo timber Evolution Short Flight"/>
|
||||
|
||||
### Flight Logs
|
||||
|
||||
[Evening Flight (video of flight shown below)](https://review.px4.io/plot_app?log=d3f2c1f9-f802-48c1-ab5d-3983fc8b8719)
|
||||
|
||||
<lite-youtube videoid="6CqigySqyAQ" params="ab_channel=ChrisSeto" title="Turbo Timber Evolution Px4 Build Log Example Flight"/>
|
||||
|
||||
### Parameter File
|
||||
|
||||
[Snapshot of PX4 airframe params](https://github.com/PX4/PX4-user_guide/raw/main/assets/airframes/fw/turbo_timber_evolution/tteparams.params)
|
||||
|
||||
This param file contains the custom PX4 parameter config for this build, including radio setup, tuning and sensor config.
|
||||
The param file can be loaded via QGC using the instructions at [Parameters> Tools ](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/parameters.html#tools) (QGC User Guide).
|
||||
@@ -0,0 +1,92 @@
|
||||
# Wing Wing Z-84 Pixracer Build
|
||||
|
||||
The Wing Wing Z-84 is a flying wing frame.
|
||||
It is small, rugged and just large enough to host a [Pixracer](../flight_controller/pixracer.md).
|
||||
|
||||
Key information:
|
||||
|
||||
- **Frame:** Wing Wing Z-84
|
||||
- **Flight controller:** Pixracer
|
||||
|
||||
|
||||
|
||||
## Parts List
|
||||
|
||||
### Z-84 Plug n' Fly (PNF/PNP) or Kit
|
||||
|
||||
One of these:
|
||||
- [Banggood](https://www.banggood.com/Wing-Wing-Z-84-Z84-EPO-845mm-Wingspan-Flying-Wing-PNP-p-973125.html)
|
||||
- [Hobbyking US Warehouse](https://hobbyking.com/en_us/wing-wing-z-84-epo-845mm-kit.html)
|
||||
|
||||
:::tip
|
||||
PNF (or "PNP") versions include motor, propeller and electronic speed controller.
|
||||
The "kit" version does not include these components, which must be purchased separately.
|
||||
:::
|
||||
|
||||
|
||||
### Electronic Speed Controller (ESC)
|
||||
|
||||
One of these (any small (>=12A) ESC will do):
|
||||
|
||||
- [Turnigy 20A Brushed ESC ESC](https://hobbyking.com/en_us/turnigy-20a-brushed-esc.html) (Hobbyking)
|
||||
- [Lumenier Regler 30A BLHeli_S ESC OPTO](https://www.getfpv.com/lumenier-30a-blheli-s-esc-opto-2-4s.html) (GetFPV)
|
||||
|
||||
### Autopilot and Essential Components
|
||||
|
||||
- [Pixracer](../flight_controller/pixracer.md) kit (including GPS and power module)
|
||||
- FrSky D4R-II receiver or equivalent (jumpered to PPM sum output according to its manual)
|
||||
- [Mini telemetry set](../flight_controller/pixfalcon.md#availability) for Holybro pix32
|
||||
- [Digital airspeed sensor](../flight_controller/pixfalcon.md#availability) for Holybro pix32 / Pixfalcon
|
||||
- 1800 mAh 2S LiPo Battery - e.g. [Team Orion 1800mAh 7.4V 50C 2S1P](https://teamorion.com/en/batteries-en/lipo/soft-case/team-orion-lipo-1800-2s-7-4v-50c-xt60-en/)
|
||||
|
||||
|
||||
### Recommended spare parts
|
||||
|
||||
- 1 cm diameter O-ring for prop saver ([Hobbyking](https://hobbyking.com/en_us/wing-wing-z-84-o-ring-10pcs.html))
|
||||
- 125x110 mm propellers ([Hobbyking](https://hobbyking.com/en_us/gws-ep-propeller-dd-5043-125x110mm-green-6pcs-set.html))
|
||||
|
||||
## Wiring
|
||||
|
||||
Wire the servos and motors as shown.
|
||||
Use the `MAIN` outputs (not the ones labeled with AUX).
|
||||
The motor controller needs to have an in-built BEC, as the autopilot is not powering the servo rail.
|
||||
|
||||
Port | Connection
|
||||
--- | ---
|
||||
RC IN | PPM or S.BUS / S.BUS2 input
|
||||
MAIN 1 | Left Aileron
|
||||
MAIN 2 | Right Aileron
|
||||
MAIN 3 | Empty
|
||||
MAIN 4 | Motor 1
|
||||
|
||||
|
||||
## Build Log
|
||||
|
||||
The images below give a rough idea about the assembly process, which is simple and can be done with a hot glue gun.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## PX4 Configuration
|
||||
|
||||
### Airframe Configuration
|
||||
|
||||
Select **Flying Wing > Generic Flying Wing** in the QGroundControl [Airframe Configuration](../config/airframe.md):
|
||||
|
||||
|
||||
|
||||
### Actuator Mapping
|
||||
|
||||
Set up the [Actuator Configuration](../config/actuators.md) to match the wiring for the ailerons and throttle as [indicated above](#wiring).
|
||||
|
||||
|
||||
|
||||
### Other Configuration
|
||||
|
||||
Perform all the the other [Basic Configuration](../config/index.md), including [Autotuning](../config/autotune_fw.md).
|
||||
|
||||
Advanced tuning is optional - see [Fixed-wing Vehicle Configuration](../config_fw/index.md).
|
||||
Reference in New Issue
Block a user