mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-19 15:43:33 +08:00
docs(updates): Link fixes and orphan image removals (#26925)
* docs(updates): Link fixes and orphan image removals * docs(delete): Remove orphaned translations
This commit is contained in:
Hamish Willee
@@ -566,6 +566,8 @@
|
||||
- [DistanceSensorModeChangeRequest](msg_docs/DistanceSensorModeChangeRequest.md)
|
||||
- [DronecanNodeStatus](msg_docs/DronecanNodeStatus.md)
|
||||
- [Ekf2Timestamps](msg_docs/Ekf2Timestamps.md)
|
||||
- [EscEepromRead](msg_docs/EscEepromRead.md)
|
||||
- [EscEepromWrite](msg_docs/EscEepromWrite.md)
|
||||
- [EscReport](msg_docs/EscReport.md)
|
||||
- [EscStatus](msg_docs/EscStatus.md)
|
||||
- [EstimatorAidSource1d](msg_docs/EstimatorAidSource1d.md)
|
||||
@@ -756,6 +758,7 @@
|
||||
- [VehicleLocalPositionV0](msg_docs/VehicleLocalPositionV0.md)
|
||||
- [VehicleStatusV0](msg_docs/VehicleStatusV0.md)
|
||||
- [VehicleStatusV1](msg_docs/VehicleStatusV1.md)
|
||||
- [VehicleStatusV2](msg_docs/VehicleStatusV2.md)
|
||||
- [MAVLink Messaging](mavlink/index.md)
|
||||
- [Adding Messages](mavlink/adding_messages.md)
|
||||
- [Streaming Messages](mavlink/streaming_messages.md)
|
||||
|
||||
@@ -91,7 +91,7 @@ For FMUv6S, you need to route the PPS signal separately:
|
||||
|
||||
For ARK FMUv6X on the Jetson carrier board:
|
||||
|
||||
1. Connect your GNSS module using either the 10-pin or 6-pin GPS connector: [ARK PAB GPS1 Interface](../flight_controller/ark_pab#gps1)
|
||||
1. Connect your GNSS module using either the 10-pin or 6-pin GPS connector: [ARK PAB GPS1 Interface](../flight_controller/ark_pab.md#gps1)
|
||||
2. Connect the PPS signal to the **FMU_CAP** pin: [ARK PAB ADIO Interface](../flight_controller/ark_pab.md#adio)
|
||||
|
||||
## Verification
|
||||
|
||||
@@ -160,7 +160,7 @@ After the bootloader has updated you can [Load PX4 Firmware](../config/firmware.
|
||||
## FMUv2 Bootloader Update
|
||||
|
||||
If _QGroundControl_ installs the FMUv2 target (see console during installation), and you have a newer board, you may need to update the bootloader in order to access all the memory on your flight controller.
|
||||
This example explains how you can use [QGC Bootloader Update](qgc-bootloader-update-sys-bl-update) to update the bootloader.
|
||||
This example explains how you can use [QGC Bootloader Update](#qgc-bootloader-update-sys-bl-update) to update the bootloader.
|
||||
|
||||
::: info
|
||||
Early FMUv2 [Pixhawk-series](../flight_controller/pixhawk_series.md#fmu_versions) flight controllers had a [hardware issue](../flight_controller/silicon_errata.md#fmuv2-pixhawk-silicon-errata) that restricted them to using 1MB of flash memory.
|
||||
|
||||
@@ -37,7 +37,7 @@ The wiring for CAN networks is the same for both DroneCAN and Cyphal/CAN (in fac
|
||||
Devices within a network are connected in a _daisy-chain_ in any order (this differs from UARTs peripherals, where you attach just one component per port).
|
||||
|
||||
:::warning Don't connect each CAN peripheral to a separate CAN port!
|
||||
Unlike UARTs, CAN peripherals are designed to be daisy chained, with additional ports such as `CAN2` used for [redundancy](redundancy).
|
||||
Unlike UARTs, CAN peripherals are designed to be daisy chained, with additional ports such as `CAN2` used for [redundancy](#redundancy).
|
||||
:::
|
||||
|
||||
At either end of the chain, a 120Ω termination resistor should be connected between the two data lines.
|
||||
@@ -83,7 +83,7 @@ You only _need_ one CAN port to support an arbitrary number of CAN devices using
|
||||
Don't connect each CAN peripheral to a separate CAN port!
|
||||
:::
|
||||
|
||||
Generally you'll daisy all CAN peripherals off a single port, and if there is more than one CAN port, use the second one for [redundancy](redundancy).
|
||||
Generally you'll daisy all CAN peripherals off a single port, and if there is more than one CAN port, use the second one for [redundancy](#redundancy).
|
||||
If three are three ports, you might use the remaining network for devices that support another CAN protocol.
|
||||
|
||||
The documentation for your flight controller should indicate which ports are supported/enabled.
|
||||
|
||||
@@ -76,13 +76,13 @@ You might have to adjust the per-motor pole count (`DSHOT_MOT_POL1`–`DSHOT_MOT
|
||||
|
||||
The following parameters should be set to enable and configure dynamic notch filters:
|
||||
|
||||
| Parameter | Description |
|
||||
| ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
|
||||
| <a href="IMU_GYRO_DNF_EN"></a>[IMU_GYRO_DNF_EN](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_EN) | Enable IMU gyro dynamic notch filtering. `0`: ESC RPM, `1`: Onboard FFT. |
|
||||
| <a href="IMU_GYRO_FFT_EN"></a>[IMU_GYRO_FFT_EN](../advanced_config/parameter_reference.md#IMU_GYRO_FFT_EN) | Enable onboard FFT (required if `IMU_GYRO_DNF_EN` is set to `1`). |
|
||||
| <a href="IMU_GYRO_DNF_MIN"></a>[IMU_GYRO_DNF_MIN](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_MIN) | Minimum dynamic notch frequency in Hz. |
|
||||
| <a href="IMU_GYRO_DNF_BW"></a>[IMU_GYRO_DNF_BW](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_BW) | Bandwidth for each notch filter in Hz. |
|
||||
| <a href="IMU_GYRO_DNF_HMC"></a>[IMU_GYRO_DNF_HMC](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_BW) | Number of harmonics to filter. |
|
||||
| Parameter | Description |
|
||||
| ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
|
||||
| <a id="IMU_GYRO_DNF_EN"></a>[IMU_GYRO_DNF_EN](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_EN) | Enable IMU gyro dynamic notch filtering. `0`: ESC RPM, `1`: Onboard FFT. |
|
||||
| <a id="IMU_GYRO_FFT_EN"></a>[IMU_GYRO_FFT_EN](../advanced_config/parameter_reference.md#IMU_GYRO_FFT_EN) | Enable onboard FFT (required if `IMU_GYRO_DNF_EN` is set to `1`). |
|
||||
| <a id="IMU_GYRO_DNF_MIN"></a>[IMU_GYRO_DNF_MIN](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_MIN) | Minimum dynamic notch frequency in Hz. |
|
||||
| <a id="IMU_GYRO_DNF_BW"></a>[IMU_GYRO_DNF_BW](../advanced_config/parameter_reference.md#IMU_GYRO_DNF_BW) | Bandwidth for each notch filter in Hz. |
|
||||
| <a id="IMU_GYRO_DNF_HMC"></a>[IMU_GYRO_DNF_HMC](../advanced_config/parameter_reference.md#IMU_GYRO_NF0_BW) | Number of harmonics to filter. |
|
||||
|
||||
### Low-pass Filter
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ See the debug probe documentation for details on how to setup your debug connect
|
||||
|
||||
- [SEGGER J-Link](probe_jlink.md): commercial probe, no built-in serial console, requires adapter.
|
||||
- [Black Magic Probe](probe_bmp.md): integrated GDB server and serial console, requires adapter.
|
||||
- [STLink](probe_stlink): best value, integrated serial console, adapter must be soldered.
|
||||
- [STLink](probe_stlink.md): best value, integrated serial console, adapter must be soldered.
|
||||
|
||||
We recommend using the J-Link with the Pixhawk Debug Adapter or the STLinkv3-MINIE with a soldered custom cable.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ PX4 runs on ARM Cortex-M microcontrollers, which contain dedicated hardware for
|
||||
The SWD debug interface allows direct, low-level, hardware access to the microcontroller's processor and peripherals, so it does not depend on any software on the device.
|
||||
Therefore it can be used to debug bootloaders and operating systems such as NuttX.
|
||||
|
||||
## Debug Signals
|
||||
## Debug Signals {#debug-signals}
|
||||
|
||||
Four signals are required for debugging (in bold) while the rest is recommended.
|
||||
|
||||
@@ -29,7 +29,7 @@ They are usually not accessible and are typically only used to debug very specif
|
||||
|
||||
## Autopilot Debug Ports {#debug-ports}
|
||||
|
||||
Flight controllers commonly provide a single debug port that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console).
|
||||
Flight controllers commonly provide a single debug port that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console.md).
|
||||
|
||||
The [Pixhawk Connector Standards](#pixhawk-standard-debug-ports) formalize the port that must be used in each FMU version.
|
||||
However there are still many boards that use different pinouts or connectors, so we recommend you check the [documentation for your autopilot](../flight_controller/index.md) to confirm port location and pinout.
|
||||
@@ -91,7 +91,7 @@ There FMU and Pixhawk versions are (only) consistent after FMUv5X.
|
||||
|
||||
### Pixhawk Debug Mini
|
||||
|
||||
The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines the _Pixhawk Debug Mini_, a _6-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console).
|
||||
The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines the _Pixhawk Debug Mini_, a _6-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console.md).
|
||||
|
||||
This is used in FMUv4 and FMUv5.
|
||||
|
||||
@@ -122,7 +122,7 @@ You can connect to the debug port using a [cable like this one](https://www.digi
|
||||
|
||||
### Pixhawk Debug Full
|
||||
|
||||
The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines _Pixhawk Debug Full_, a _10-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console).
|
||||
The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines _Pixhawk Debug Full_, a _10-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console.md).
|
||||
This essentially moves the solder pads from beside the [Pixhawk Debug Mini](#pixhawk-debug-mini) into the connector, and also adds an SWO pin.
|
||||
|
||||
This port is specified for use in FMUv5x, FMUv6, FMUv6x.
|
||||
@@ -154,14 +154,14 @@ You can connect to the debug port using a [cable like this one](https://www.digi
|
||||
|
||||
## Debug Probes for PX4 Hardware {#debug-probes}
|
||||
|
||||
Flight controllers commonly provide a [single debug port](#autopilot-debug-ports) that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console).
|
||||
Flight controllers commonly provide a [single debug port](#autopilot-debug-ports) that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console.md).
|
||||
|
||||
There are several debug probes that are tested and supported for connecting to one or both of these interfaces:
|
||||
|
||||
- [SEGGER J-Link](../debug/probe_jlink.md): commercial probe, no built-in serial console, requires adapter.
|
||||
- [Black Magic Probe](../debug/probe_bmp.md): integrated GDB server and serial console, requires adapter.
|
||||
- [STLink](../debug/probe_stlink): best value, integrated serial console, adapter must be soldered.
|
||||
- [MCU-Link](../debug/probe_mculink): best value, integrated serial console, requires adapter.
|
||||
- [STLink](../debug/probe_stlink.md): best value, integrated serial console, adapter must be soldered.
|
||||
- [MCU-Link](../debug/probe_mculink.md): best value, integrated serial console, requires adapter.
|
||||
|
||||
An adapter to connect to the debug port may come with your flight controller or debug probe.
|
||||
Other options are given below.
|
||||
@@ -199,7 +199,7 @@ Probes that are known to come with connectors are listed below:
|
||||
|
||||
### Board-specific Adapters
|
||||
|
||||
Some manufacturers provide cables to make it easy to connect the SWD interface and [System Console](../debug/system_console).
|
||||
Some manufacturers provide cables to make it easy to connect the SWD interface and [System Console](../debug/system_console.md).
|
||||
|
||||
- [CUAV V5nano](../flight_controller/cuav_v5_nano.md#debug_port) and [CUAV V5+](../flight_controller/cuav_v5_plus.md#debug-port) include this debug cable:
|
||||
|
||||
@@ -213,7 +213,7 @@ You can also create custom cables for connecting to different boards or probes:
|
||||
- Connect the VREF pin, if supported by the debug probe.
|
||||
- Connect the remaining pins, if present.
|
||||
|
||||
See the [STLinkv3-MINIE](probe_stlink) for a guide on how to solder a custom cable.
|
||||
See the [STLinkv3-MINIE](probe_stlink.md) for a guide on how to solder a custom cable.
|
||||
|
||||
:::tip
|
||||
Where possible, we highly recommend that you create or obtain an adapter board rather than custom cables for connecting to SWD/JTAG debuggers and computers.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Arch Linux Development Environment
|
||||
|
||||
:::warning
|
||||
This development environment is [community supported and maintained](../advanced/community_supported_dev_env).
|
||||
This development environment is [community supported and maintained](../advanced/community_supported_dev_env.md).
|
||||
It may or may not work with current versions of PX4.
|
||||
|
||||
See [Toolchain Installation](../dev_setup/dev_env.md) for information about the environments and tools supported by the core development team.
|
||||
|
||||
@@ -84,7 +84,7 @@ You need to set necessary [DroneCAN](index.md) parameters and define offsets if
|
||||
|
||||
- Enable GPS yaw fusion by setting bit 3 of [EKF2_GPS_CTRL](../advanced_config/parameter_reference.md#EKF2_GPS_CTRL) to true.
|
||||
- Enable GPS blending to ensure the heading is always published by setting [SENS_GPS_MASK](../advanced_config/parameter_reference.md#SENS_GPS_MASK) to 7 (all three bits checked).
|
||||
- If using [Moving Baseline & GPS Heading](#setting-up-moving-baseline--gps-heading), set [SENS_GPS_PRIME](../advanced_config/parameter_reference.md#SENS_GPS_PRIME) to the CAN node ID of the _Moving Base_ module. The moving base is preferred because the rover receiver in a moving baseline configuration can experience degraded navigation rate and increased data latency when corrections are intermittent.
|
||||
- If using [Moving Baseline & GPS Heading](#setting-up-moving-baseline-gps-heading), set [SENS_GPS_PRIME](../advanced_config/parameter_reference.md#SENS_GPS_PRIME) to the CAN node ID of the _Moving Base_ module. The moving base is preferred because the rover receiver in a moving baseline configuration can experience degraded navigation rate and increased data latency when corrections are intermittent.
|
||||
- Enable [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS), [UAVCAN_SUB_MAG](../advanced_config/parameter_reference.md#UAVCAN_SUB_MAG), and [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO).
|
||||
- The parameters [SENS_GPS0_OFFX](../advanced_config/parameter_reference.md#SENS_GPS0_OFFX), [SENS_GPS0_OFFY](../advanced_config/parameter_reference.md#SENS_GPS0_OFFY) and [SENS_GPS0_OFFZ](../advanced_config/parameter_reference.md#SENS_GPS0_OFFZ) can be set to account for the offset of the ARK RTK GPS from the vehicles centre of gravity.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ PX4 supports DroneCAN compliant ESCs.
|
||||
## Supported ESC
|
||||
|
||||
:::info
|
||||
[Supported ESCs](../peripherals/esc_motors#supported-esc) in _ESCs & Motors_ may include additional devices that are not listed below.
|
||||
[Supported ESCs](../peripherals/esc_motors.md#supported-esc) in _ESCs & Motors_ may include additional devices that are not listed below.
|
||||
:::
|
||||
|
||||
The following articles have specific hardware/firmware information:
|
||||
|
||||
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
|
||||
Contact the [manufacturer](https://arkelectron.com/contact-us/) for hardware support or compliance issues.
|
||||
:::
|
||||
|
||||
The USA-built [ARKV6X](<(https://arkelectron.gitbook.io/ark-documentation/flight-controllers/arkv6x)>) flight controller is based on the [FMUV6X and Pixhawk Autopilot Bus open source standards](https://github.com/pixhawk/Pixhawk-Standards).
|
||||
The USA-built [ARKV6X](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/arkv6x) flight controller is based on the [FMUV6X and Pixhawk Autopilot Bus open source standards](https://github.com/pixhawk/Pixhawk-Standards).
|
||||
|
||||
With triple synced IMUs, data averaging, voting, and filtering is possible.
|
||||
The Pixhawk Autopilot Bus (PAB) form factor enables the ARKV6X to be used on any [PAB-compatible carrier board](../flight_controller/pixhawk_autopilot_bus.md), such as the [ARK Pixhawk Autopilot Bus Carrier](../flight_controller/ark_pab.md).
|
||||
|
||||
@@ -13,14 +13,14 @@ The mission is typically created and uploaded with a Ground Control Station (GCS
|
||||
|
||||
The following commands can be used in missions at time of writing (PX4 v1.16):
|
||||
|
||||
| QGC mission item | Command | Description |
|
||||
| ------------------- | ------------------------------------------------------------ | ------------------------------------------------- |
|
||||
| Mission start | [MAV_CMD_MISSION_START](MAV_CMD_MISSION_START) | Starts the mission. |
|
||||
| Waypoint | [MAV_CMD_NAV_WAYPOINT](MAV_CMD_NAV_WAYPOINT) | Navigate to waypoint. |
|
||||
| Return to launch | [MAV_CMD_NAV_RETURN_TO_LAUNCH][MAV_CMD_NAV_RETURN_TO_LAUNCH] | Return to the launch location. |
|
||||
| Change speed | [MAV_CMD_DO_CHANGE_SPEED][MAV_CMD_DO_CHANGE_SPEED] | Change the speed setpoint |
|
||||
| Set launch location | [MAV_CMD_DO_SET_HOME](MAV_CMD_DO_SET_HOME) | Changes launch location to specified coordinates. |
|
||||
| Jump to item (all) | [MAV_CMD_DO_JUMP][MAV_CMD_DO_JUMP] (and other jump commands) | Jump to specified mission item. |
|
||||
| QGC mission item | Command | Description |
|
||||
| ------------------- | ------------------------------------------- | ------------------------------------------------- |
|
||||
| Mission start | [MAV_CMD_MISSION_START] | Starts the mission. |
|
||||
| Waypoint | [MAV_CMD_NAV_WAYPOINT] | Navigate to waypoint. |
|
||||
| Return to launch | [MAV_CMD_NAV_RETURN_TO_LAUNCH] | Return to the launch location. |
|
||||
| Change speed | [MAV_CMD_DO_CHANGE_SPEED] | Change the speed setpoint |
|
||||
| Set launch location | [MAV_CMD_DO_SET_HOME] | Changes launch location to specified coordinates. |
|
||||
| Jump to item (all) | [MAV_CMD_DO_JUMP] (and other jump commands) | Jump to specified mission item. |
|
||||
|
||||
[MAV_CMD_MISSION_START]: https://mavlink.io/en/messages/common.html#MAV_CMD_MISSION_START
|
||||
[MAV_CMD_NAV_WAYPOINT]: https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_WAYPOINT
|
||||
|
||||
@@ -68,7 +68,7 @@ The following manual and assisted modes are currently supported on BlueROV2 Heav
|
||||
## Joystick Stick Mode
|
||||
|
||||
BlueROV2 supports two joystick mappings for manual control, selected using the
|
||||
[UUV_STICK_MODE](../advanced_config/parameter_reference.md#uuv_stick_mode) parameter.
|
||||
[UUV_STICK_MODE](../advanced_config/parameter_reference.md#UUV_STICK_MODE) parameter.
|
||||
|
||||
By default, `UUV_STICK_MODE` is set to `0`, which enables the UUV stick mapping intended for vectored underwater vehicles.
|
||||
|
||||
|
||||
@@ -14,50 +14,52 @@ This section describes the VTOL types and configurations supported by PX4, and p
|
||||
|
||||
## VTOL Types
|
||||
|
||||
PX4 supports the three most important/main VTOL types.
|
||||
PX4 supports the three most important/main VTOL types: [Standard VTOL](standardvtol.md), [Tiltrotor](tiltrotor.md), and [Tailsitter](tailsitter.md).
|
||||
|
||||
<div class="grid_wrapper three_column">
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><a href="tailsitter.html" title="Tailsitter"><big>Tailsitter</big></a></div>
|
||||
<div class="grid_text">
|
||||
Rotors permanently in fixed-wing position.
|
||||
Takes off and lands on tail. Whole vehicle tilts forward to enter forward flight.
|
||||
<img src="../../assets/airframes/vtol/wingtraone/hero.jpg" title="wingtraone" />
|
||||
<ul>
|
||||
<li>Simple and robust</li>
|
||||
<li>Minimal set of actuators</li>
|
||||
<li>Can be hard to control, particularly in wind</li>
|
||||
<li>Tradeoff between efficiency in hover and forward flight, as same actuators are used</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><a href="tiltrotor.html" title="Tiltrotor"><big>Tiltrotor</big></a></div>
|
||||
Rotors swivel 90 degrees to transition from multicopter to forward flight orientation.
|
||||
Takes off and lands on belly.
|
||||
<div class="grid_text">
|
||||
<img src="../../assets/airframes/vtol/eflite_convergence_pixfalcon/hero.jpg" title="Eflight Confvergence" />
|
||||
<ul>
|
||||
<li>Additional actuators for motor tilts</li>
|
||||
<li>Mechanically complex tilting mechanism</li>
|
||||
<li>Easier to control in hover than tailsitters due to more control authority</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><a href="standardvtol.html" title="Standard VTOL"><big>Standard VTOL</big></a></div>
|
||||
<div class="grid_text">
|
||||
Separate rotors/flight controls for multicopter and forward flight. Takes off and lands on belly.
|
||||
<img src="../../assets/airframes/vtol/vertical_technologies_deltaquad/hero_small.png" title="Vertical Technologies: Deltaquad" />
|
||||
<ul>
|
||||
<li>Additional weight from separate hover/forward flight propulsion systems</li>
|
||||
<li>Easiest to control due to dedicated hover/forward flight actuators</li>
|
||||
<li>Can hover</li>
|
||||
<li>Fuel engines for forward flight propulsion can be used</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
:::: tabs
|
||||
|
||||
::: tab Standard VTOL
|
||||
|
||||
Separate rotors/flight controls for multicopter and forward flight.
|
||||
Takes off and lands on belly.
|
||||
|
||||
|
||||
|
||||
- Additional weight from separate hover/forward flight propulsion systems
|
||||
- Easiest to control due to dedicated hover/forward flight actuators
|
||||
- Can hover
|
||||
- Fuel engines can be used for forward flight propulsion
|
||||
|
||||
:::
|
||||
|
||||
::: tab Tailsitter
|
||||
|
||||
Rotors permanently in fixed-wing position.
|
||||
Takes off and lands on tail. Whole vehicle tilts forward to enter forward flight.
|
||||
|
||||
|
||||
|
||||
- Simple and robust
|
||||
- Minimal set of actuators
|
||||
- Can be hard to control, particularly in wind
|
||||
- Tradeoff between efficiency in hover and forward flight, as same actuators are used
|
||||
|
||||
:::
|
||||
|
||||
::: tab Tiltrotor
|
||||
|
||||
Rotors swivel 90 degrees to transition from multicopter to forward flight orientation.
|
||||
Takes off and lands on belly.
|
||||
|
||||
|
||||
|
||||
- Additional actuators for motor tilts
|
||||
- Mechanically complex tilting mechanism
|
||||
- Easier to control in hover than tailsitters due to more control authority
|
||||
|
||||
:::
|
||||
|
||||
::::
|
||||
|
||||
In general, as mechanical complexity increases the vehicles are easier to fly, but the cost and weight increase.
|
||||
Each type has advantages and disadvantages, and there are successful commercial ventures based on all of them.
|
||||
@@ -125,7 +127,7 @@ VTOL Control & Airspeed Fault Detection (PX4 Developer Summit 2019)
|
||||
|
||||
<!-- 20190704 -->
|
||||
|
||||
### Tailsitter
|
||||
### Tailsitter {#tailsitter_video}
|
||||
|
||||
[UAV Works VALAQ Patrol Tailsitter](https://www.valaqpatrol.com/valaq_patrol_technical_data/)
|
||||
|
||||
@@ -135,7 +137,7 @@ VTOL Control & Airspeed Fault Detection (PX4 Developer Summit 2019)
|
||||
|
||||
<lite-youtube videoid="acG0aTuf3f8" title="PX4 VTOL - Call for Testpilots"/>
|
||||
|
||||
### Tiltrotor
|
||||
### Tiltrotor {#tiltrotor_video}
|
||||
|
||||
[Convergence Tiltrotor](../frames_vtol/vtol_tiltrotor_eflite_convergence_pixfalcon.md)
|
||||
|
||||
|
||||
@@ -88,35 +88,36 @@ This section contains videos that are specific to Tailsitter VTOL (videos that a
|
||||
|
||||
## Gallery
|
||||
|
||||
<div class="grid_wrapper three_column">
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><big><a href="https://wingtra.com/mapping-drone-fast-accurate-surveying/">WingtraOne</a></big></div>
|
||||
<div class="grid_text">
|
||||
<img src="../../assets/airframes/vtol/wingtraone/hero.jpg" title="Wingtra: WingtraOne VTOL Duo Tailsitter" alt="wingtraone" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><big><a href="https://www.skypull.technology/">Skypull</a></big></div>
|
||||
<div class="grid_text">
|
||||
<img title="Skypull SP-1 VTOL QuadTailsitter" src="../../assets/airframes/vtol/skypull/skypull_sp1.jpg" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><big><a href="../frames_vtol/vtol_tailsitter_caipiroshka_pixracer.html">TBS Caipiroshka</a></big></div>
|
||||
<div class="grid_text">
|
||||
<img title="TBS Caipiroshka" src="../../assets/airframes/vtol/caipiroshka/caipiroshka.jpg" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><big><a href="http://uav-cas.ac.cn/WOSHARK/">Woshark</a></big></div>
|
||||
<div class="grid_text">
|
||||
<img title="Woshark" src="../../assets/airframes/vtol/xdwgood_ax1800/hero.jpg" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_item">
|
||||
<div class="grid_item_heading"><big><a href="https://www.valaqpatrol.com/valaq_patrol_technical_data/">UAV Works VALAQ Patrol Tailsitter</a></big></div>
|
||||
<div class="grid_text">
|
||||
<img title="UAV Works VALAQ Patrol Tailsitter" src="../../assets/airframes/vtol/uav_works_valaq_patrol/hero.jpg" />
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
:::: tabs
|
||||
|
||||
::: tab WingtraOne
|
||||
[WingtraOne](https://wingtra.com/mapping-drone-fast-accurate-surveying/)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
::: tab Skypull
|
||||
[Skypull](https://www.skypull.technology/)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
::: tab TBS Caipiroshka
|
||||
[TBS Caipiroshka](../frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
::: tab Woshark
|
||||
[Woshark](http://uav-cas.ac.cn/WOSHARK/)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
::: tab VALAQ Patrol Tailsitter
|
||||
[UAV Works VALAQ Patrol Tailsitter](https://www.valaqpatrol.com/valaq_patrol_technical_data/)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
::::
|
||||
|
||||
@@ -13,7 +13,7 @@ This topic shows how to connect and configure DShot ESCs.
|
||||
|
||||
## Supported ESC
|
||||
|
||||
[ESCs & Motors > Supported ESCs](../peripherals/esc_motors#supported-esc) has a list of supported ESC (check "Protocols" column for DShot ESC).
|
||||
[ESCs & Motors > Supported ESCs](../peripherals/esc_motors.md#supported-esc) has a list of supported ESC (check "Protocols" column for DShot ESC).
|
||||
|
||||
## Wiring/Connections {#wiring}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user