Mirrors_Framework/PX4-Autopilot
1
0
Fork 0
mirror of https://github.com/PX4/PX4-Autopilot.git synced 2026-06-02 11:59:17 +08:00
Code Issues Actions 21 Packages Projects Releases Wiki Activity

docs: Link fixes in docs - including 404 fixes (#26605)

Browse Source 
* Redirect 301/308 HTTP link fixes
* Easy 404 fixes - easy
* Add internal anchor fixes and generate msg docs fix
This commit is contained in:
Hamish Willee
2026-02-28 17:09:53 +11:00
committed by GitHub
parent a74724193e
commit 209c971c1b
83 changed files with 465 additions and 461 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Tools/msg/generate_msg_docs.py
+1 -1
View File
@@ -529,7 +529,7 @@ pageClass: is-wide-page
for enumValueName, enumValue in enum.enumValues.items():
description = f" {enumValue.comment} " if enumValue.comment else " "
markdown += f'<a href="#{enumValueName}"></a> {enumValueName} | `{enumValue.type}` | {enumValue.value} |{description}\n'
markdown += f'<a id="#{enumValueName}"></a> {enumValueName} | `{enumValue.type}` | {enumValue.value} |{description}\n'
# Generate table for constants docs
if len(self.constantFields) > 0:
docs/en/SUMMARY.md
+6
View File
@@ -529,6 +529,8 @@
- [LongitudinalControlConfiguration](msg_docs/LongitudinalControlConfiguration.md)
- [ManualControlSetpoint](msg_docs/ManualControlSetpoint.md)
- [ModeCompleted](msg_docs/ModeCompleted.md)
- [RaptorInput](msg_docs/RaptorInput.md)
- [RaptorStatus](msg_docs/RaptorStatus.md)
- [RegisterExtComponentReply](msg_docs/RegisterExtComponentReply.md)
- [RegisterExtComponentRequest](msg_docs/RegisterExtComponentRequest.md)
- [TrajectorySetpoint](msg_docs/TrajectorySetpoint.md)
@@ -750,6 +752,7 @@
- [VehicleThrustSetpoint](msg_docs/VehicleThrustSetpoint.md)
- [VehicleTorqueSetpoint](msg_docs/VehicleTorqueSetpoint.md)
- [VelocityLimits](msg_docs/VelocityLimits.md)
- [Vtx](msg_docs/Vtx.md)
- [WheelEncoders](msg_docs/WheelEncoders.md)
- [Wind](msg_docs/Wind.md)
- [YawEstimatorStatus](msg_docs/YawEstimatorStatus.md)
@@ -763,8 +766,11 @@
- [RegisterExtComponentReplyV0](msg_docs/RegisterExtComponentReplyV0.md)
- [RegisterExtComponentRequestV0](msg_docs/RegisterExtComponentRequestV0.md)
- [VehicleAttitudeSetpointV0](msg_docs/VehicleAttitudeSetpointV0.md)
- [VehicleCommandAckV0](msg_docs/VehicleCommandAckV0.md)
- [VehicleGlobalPositionV0](msg_docs/VehicleGlobalPositionV0.md)
- [VehicleLocalPositionV0](msg_docs/VehicleLocalPositionV0.md)
- [VehicleStatusV0](msg_docs/VehicleStatusV0.md)
- [VehicleStatusV1](msg_docs/VehicleStatusV1.md)
- [MAVLink Messaging](mavlink/index.md)
- [Adding Messages](mavlink/adding_messages.md)
- [Streaming Messages](mavlink/streaming_messages.md)
docs/en/advanced_config/tuning_the_ecl_ekf.md
+1 -1
View File
@@ -594,7 +594,7 @@ When this has been done, the performance metadata files can be processed to prov
- Attitude output data is found in the [VehicleAttitude](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleAttitude.msg) message.
- Local position output data is found in the [VehicleLocalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleLocalPosition.msg) message.
- Global \(WGS-84\) output data is found in the [VehicleGlobalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleGlobalPosition.msg) message.
- Wind velocity output data is found in the [Wind.msg](https://github.com/PX4/PX4-Autopilot/blob/main/msg/Wind.msg) message.
- Wind velocity output data is found in the [AirspeedWind.msg](https://github.com/PX4/PX4-Autopilot/blob/main/msg/AirspeedWind.msg) message.
### States
docs/en/airframes/airframe_reference.md
+2 -2
View File
@@ -402,7 +402,7 @@ div.frame_variant td, div.frame_variant th {
<td>Maintainer: Lorenz Meier &lt;lorenz@px4.io&gt;<p><code>SYS_AUTOSTART</code> = 4050</p></td>
</tr>
<tr id="copter_quadrotor_x_holybro_qav250">
<td><a href="https://docs.px4.io/main/en/frames_multicopter/holybro_qav250_pixhawk4_mini.html">HolyBro QAV250</a></td>
<td><a href="https://docs.px4.io/main/en/frames_multicopter/holybro_qav250_pixhawk4_mini">HolyBro QAV250</a></td>
<td>Maintainer: Beat Kueng &lt;beat-kueng@gmx.net&gt;<p><code>SYS_AUTOSTART</code> = 4052</p></td>
</tr>
<tr id="copter_quadrotor_x_holybro_kopis_2">
@@ -604,7 +604,7 @@ div.frame_variant td, div.frame_variant th {
<td>Maintainer: John Doe &lt;john@example.com&gt;<p><code>SYS_AUTOSTART</code> = 50000</p></td>
</tr>
<tr id="rover_rover_aion_robotics_r1_ugv">
<td><a href="https://docs.px4.io/main/en/complete_vehicles_rover/aion_r1.html">Aion Robotics R1 UGV</a></td>
<td><a href="https://docs.px4.io/main/en/complete_vehicles_rover/aion_r1">Aion Robotics R1 UGV</a></td>
<td>Maintainer: John Doe &lt;john@example.com&gt;<p><code>SYS_AUTOSTART</code> = 50001</p></td>
</tr>
<tr id="rover_rover_generic_rover_ackermann">
docs/en/assembly/quick_start_cuav_v5_nano.md
+2 -2
View File
@@ -33,7 +33,7 @@ We'll go through each of these in detail in the following sections.
| DSM/SBUS/RSSI | Includes DSM, SBUS, RSSI signal input interface, DSM interface can be connected to DSM satellite receiver, SBUS interface to SBUS remote control receiver, RSSI for signal strength return module. |
::: info
For more interface information, please read [V5 nano Manual](http://manual.cuav.net/V5-nano.pdf).
For more interface information, please read [V5 nano Manual](https://manual.cuav.net/V5-nano.pdf).
:::
![quickstart](../../assets/flight_controller/cuav_v5_nano/connection/v5_nano_quickstart_03.png)
@@ -128,6 +128,6 @@ Motors/servos are connected to the MAIN ports in the order specified for your ve
- [Airframe buildlog using CUAV v5 nano on a DJI FlameWheel450](../frames_multicopter/dji_f450_cuav_5nano.md)
- [CUAV V5 nano](../flight_controller/cuav_v5_nano.md)
- [V5 nano manual](http://manual.cuav.net/V5-nano.pdf) (CUAV)
- [V5 nano manual](https://manual.cuav.net/V5-nano.pdf) (CUAV)
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165) (CUAV)
- [CUAV Github](https://github.com/cuav) (CUAV)
docs/en/assembly/quick_start_cuav_v5_plus.md
+3 -3
View File
@@ -33,7 +33,7 @@ We'll go through each of these in detail in the following sections.
| DSM/SBUS/RSSI | Includes DSM, SBUS, RSSI signal input interface, DSM interface can be connected to DSM satellite receiver, SBUS interface to SBUS remote control receiver, RSSI for signal strength return module. |
::: info
For more interface information, please read [V5+ Manual](http://manual.cuav.net/V5-Plus.pdf).
For more interface information, please read [V5+ Manual](https://manual.cuav.net/V5-Plus.pdf).
:::
![V5+ AutoPilot](../../assets/flight_controller/cuav_v5_plus/connection/v5+_quickstart_02.png)
@@ -122,12 +122,12 @@ Motors/servos are connected to the MAIN and AUX ports in the order specified for
## Pinouts
Download **V5+** pinouts from [here](http://manual.cuav.net/V5-Plus.pdf).
See [CUAV V5+ Manual](https://manual.cuav.net/V5-Plus.pdf).
## Further Information
- [Airframe build-log using CUAV v5+ on a DJI FlameWheel450](../frames_multicopter/dji_f450_cuav_5plus.md)
- [CUAV V5+ Manual](http://manual.cuav.net/V5-Plus.pdf) (CUAV)
- [CUAV V5+ Manual](https://manual.cuav.net/V5-Plus.pdf) (CUAV)
- [CUAV V5+ docs](https://doc.cuav.net/controller/v5-autopilot/en/v5+.html) (CUAV)
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165) (CUAV)
- [CUAV Github](https://github.com/cuav) (CUAV)
docs/en/companion_computer/video_streaming.md
+1 -1
View File
@@ -20,7 +20,7 @@ For a Ubuntu companion, a minimal set might be:
sudo apt install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-gl -y
```
For the full set you can mirror the QGC dependencies installed by [/tools/setup/install-dependencies-debian.sh](https://github.com/mavlink/qgroundcontrol/blob/master/tools/setup/install-dependencies-debian.sh).
For the full set you can mirror the QGC dependencies installed by [/tools/setup/install_dependencies.py](https://github.com/mavlink/qgroundcontrol/blob/master/tools/setup/install_dependencies.py).
At time of writing this is:
```sh
docs/en/complete_vehicles_mc/px4_vision_kit.md
+1 -1
View File
@@ -381,7 +381,7 @@ The carrier board pinouts and other information are in the [downloads section](h
## Other Development Resources
- [_UP Core_ Wiki](https://github.com/up-board/up-community/wiki/Ubuntu) - _Up Core_ companion computer technical information
- [Occipital Developer Forum](https://structure.io/structure-sdk) - _Structure Core_ camera information
- [Occipital Developer Forum](https://structure.io/structure-sdk/) - _Structure Core_ camera information
- [Pixhawk 4 Overview](../flight_controller/pixhawk4.md)
- [Pixhawk 6C Overview](../flight_controller/pixhawk6c.md)
docs/en/contribute/git_examples.md
+1 -1
View File
@@ -45,7 +45,7 @@ Adding a feature to PX4 follows a defined workflow. In order to share your contr
git add <file name>
```
If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](https://nuclearsquid.com/writings/git-add/).
If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](https://nuclearsquid.com/writings/git-add/).
- Commit the added files with a meaningful message explaining your changes
docs/en/dev_setup/dev_env_windows_vm.md
+2 -2
View File
@@ -29,11 +29,11 @@ There is also an incomplete section for VirtualBox at the end (we'd welcome expa
VMWare performance is acceptable for basic usage (building Firmware) but not for running ROS or Gazebo Classic.
1. Download [VMWare Player Freeware](https://www.vmware.com/info/workstation-player/evaluation)
1. Download [VMWare Workstation Pro](https://www.vmware.com/products/desktop-hypervisor/workstation-and-fusion) (the free player has been discontinued)
1. Install it on your Windows system
1. Download the desired version of [Ubuntu Desktop ISO Image](https://ubuntu.com/download/desktop).
(see [Linux Instructions Page](../dev_setup/dev_env_linux.md) for recommended Ubuntu version).
1. Open _VMWare Player_.
1. Open _Workstation Pro_.
1. Enable 3D acceleration in the VM's settings: **VM > Settings > Hardware > Display > Accelerate 3D graphics**
::: info
docs/en/flight_controller/cuav_nora.md
+4 -4
View File
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
Contact the [manufacturer](https://www.cuav.net) for hardware support or compliance issues.
:::
The [Nora](https://doc.cuav.net/flight-controller/x7/en/nora.html)<sup>&reg;</sup> flight controller is a high-performance autopilot.
The [Nora](https://doc.cuav.net/controller/x7/en/nora-plus.html)<sup>&reg;</sup> flight controller is a high-performance autopilot.
It is an ideal choice for industrial drones and large-scale heavy-duty drones.
It is mainly supplied to commercial manufacturers.
@@ -31,7 +31,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
- High performance processor
::: tip
The manufacturer [CUAV Docs](https://doc.cuav.net/flight-controller/x7/en/nora.html) are the canonical reference for Nora.
The manufacturer [CUAV Docs](https://doc.cuav.net/controller/x7/en/nora-plus.html) are the canonical reference for Nora.
They should be used by preference as they contain the most complete and up to date information.
:::
@@ -79,7 +79,7 @@ The remaining 6 PWM ports are still being adapted (so it is not compatible with
## Connections (Wiring)
[CUAV nora Wiring Quickstart](https://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-nora.html)
[CUAV nora Wiring Quickstart](https://doc.cuav.net/controller/x7/en/quick-start/quick-start-nora.html)
## Size and Pinouts
@@ -167,6 +167,6 @@ The complete set of supported configurations can be seen in the [Airframes Refer
## Further info
- [Quick start](https://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-nora.html)
- [Quick start](https://doc.cuav.net/controller/x7/en/quick-start/quick-start-nora.html)
- [CUAV docs](https://doc.cuav.net/)
- [nora schematic](https://github.com/cuav/hardware/tree/master/X7_Autopilot)
docs/en/flight_controller/cuav_x7.md
+1 -1
View File
@@ -39,7 +39,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
- High performance processor
::: tip
The manufacturer [CUAV Docs](https://doc.cuav.net/flight-controller/x7/en/) are the canonical reference for the X7.
The manufacturer [CUAV Docs](https://doc.cuav.net/controller/x7/en/) are the canonical reference for the X7.
They should be used by preference as they contain the most complete and up to date information.
:::
docs/en/flight_controller/modalai_fc_v1.md
+1 -1
View File
@@ -116,7 +116,7 @@ Detailed information about the pinouts can be found [here](https://docs.modalai.
### User Guide
The full user guide is available [here](https://docs.modalai.com/flight-core-manual/).
The full user guide is available [here](https://docs.modalai.com/flight-core/).
### How to Build
docs/en/flight_controller/modalai_voxl_2.md
+3 -3
View File
@@ -62,7 +62,7 @@ ModalAI is actively maintaining a [branched PX4 version](https://github.com/moda
As VOXL 2 runs Ubuntu, the production releases of PX4 for VOXL 2 are distributed through [apt package management](https://docs.modalai.com/configure-pkg-manager/) and the [VOXL SDK](https://docs.modalai.com/voxl-sdk/).
More information about the firmware can be found [here](https://docs.modalai.com/voxl2-px4-developer-guide/).
More information about the firmware can be found [here](https://docs.modalai.com/voxl-px4-developer-guide/).
### main branch
@@ -84,7 +84,7 @@ This board is supported in QGroundControl 4.0 and later.
## Quick Start
Quickstarts from the vendor are located [here](https://docs.modalai.com/voxl2-quickstarts/).
Quickstarts from the vendor are located [here](https://docs.modalai.com/voxl-2-hardware-quickstart/).
### VOXL SDK
@@ -127,7 +127,7 @@ The PX4 developer guide for VOXL 2 is available [here](https://docs.modalai.com/
### How to Build
See the [VOXL PX4 Build Guide](https://docs.modalai.com/voxl2-px4-build-guide/) on how to build.
See the [VOXL PX4 Build Guide](https://docs.modalai.com/voxl-px4-dev-build-guide/) on how to build.
## Support
docs/en/flight_controller/modalai_voxl_flight.md
+22 -22
View File
@@ -30,25 +30,25 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
### Companion Computer
| Feature | Details |
| :-------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Base Operation System | Linux Yocto Jethro with 3.18 kernel. Additional Linux Operating Systems can be used by running Docker on VOXL, details [here](https://docs.modalai.com/docker-on-voxl/) |
| Compute | Qualcomm Snapdragon 821 w/ 4GB LPDDR4 1866MHz, Snapdragon 821 [Datasheet](https://developer.qualcomm.com/download/sd820e/qualcomm-snapdragon-820e-processor-apq8096sge-device-specification.pdf), [Docs](https://developer.qualcomm.com/hardware/apq-8096sg/tools) |
| CPU | Quad-core CPU up to 2.15GHz |
| GPU | Adreno 530 GPU at 624MHz |
| Compute DSP | Hexagon compute DSP (cDSP) 825MHz |
| Sensor DSP | Hexagon sensor DSP (sDSP) 700MHz |
| Video | 4k30 Video Capture h.264/5 w/ 720p FPV |
| Camera Interfaces | Support for MIPI-CSI2, USB UVC, HDMI |
| Wi-Fi | Pre-certified Wi-Fi module [QCNFA324 FCC ID:PPD-QCNFA324](https://fccid.io/PPD-QCNFA324), QCA6174A modem, 802.11ac 2x2 Dual-band, Bluetooth 4.2 (dual-mode) |
| 4G LTE | [Optional add-on module](https://www.modalai.com/collections/voxl-add-ons/products/voxl-lte) |
| Microhard pDDL | [Optional add-on module](https://www.modalai.com/collections/voxl-add-ons/products/voxl-microhard-modem-usb-hub) |
| GNSS | WGR7640 10Hz |
| I/O | 1x USB3.0 OTG (ADB port), 1x USB2.0 (expansion port), 2x UART, 3x I2C, additional GPIO and SPI can be configured |
| Storage | 32GB (UFS 2.0), Micro SD Card |
| Software | Docker, OpenCV 2.4.11, 3.4.6, 4.2, ROS Indigo, Qualcomm Machine Vision SDK, see [GitLab](https://gitlab.com/voxl-public) for lots of open source examples! |
| IMUs | ICM-42688 (SPI10), ICM-20948 (SPI1) |
| Barometer | BMP280 |
| Feature | Details |
| :-------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Base Operation System | Linux Yocto Jethro with 3.18 kernel. Additional Linux Operating Systems can be used by running Docker on VOXL, details [here](https://docs.modalai.com/docker-on-voxl/) |
| Compute | Qualcomm Snapdragon 821 w/ 4GB LPDDR4 1866MHz, Snapdragon 821 [Datasheet](https://manuals.plus/m/1409295179a6c50b5baa1ae6a7113ff67112341756058e9d0466bdb832800a60) |
| CPU | Quad-core CPU up to 2.15GHz |
| GPU | Adreno 530 GPU at 624MHz |
| Compute DSP | Hexagon compute DSP (cDSP) 825MHz |
| Sensor DSP | Hexagon sensor DSP (sDSP) 700MHz |
| Video | 4k30 Video Capture h.264/5 w/ 720p FPV |
| Camera Interfaces | Support for MIPI-CSI2, USB UVC, HDMI |
| Wi-Fi | Pre-certified Wi-Fi module [QCNFA324 FCC ID:PPD-QCNFA324](https://fccid.io/PPD-QCNFA324), QCA6174A modem, 802.11ac 2x2 Dual-band, Bluetooth 4.2 (dual-mode) |
| 4G LTE | [Optional add-on module](https://www.modalai.com/collections/voxl-add-ons/products/voxl-lte) |
| Microhard pDDL | [Optional add-on module](https://www.modalai.com/collections/voxl-add-ons/products/voxl-microhard-modem-usb-hub) |
| GNSS | WGR7640 10Hz |
| I/O | 1x USB3.0 OTG (ADB port), 1x USB2.0 (expansion port), 2x UART, 3x I2C, additional GPIO and SPI can be configured |
| Storage | 32GB (UFS 2.0), Micro SD Card |
| Software | Docker, OpenCV 2.4.11, 3.4.6, 4.2, ROS Indigo, Qualcomm Machine Vision SDK, see [GitLab](https://gitlab.com/voxl-public) for lots of open source examples! |
| IMUs | ICM-42688 (SPI10), ICM-20948 (SPI1) |
| Barometer | BMP280 |
### Flight Controller
@@ -118,8 +118,8 @@ A quickstart from the vendor is located [here](https://docs.modalai.com/voxl-fli
### voxl-vision-px4
The VOXL Flight runs [voxl-vision-px4](https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-vision-px4) on the companion computer portion of the hardware serving as a sort of MAVLink proxy.
For details, the source code is available [here](https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-vision-px4)
The VOXL Flight runs [voxl-vision-px4](https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub) on the companion computer portion of the hardware serving as a sort of MAVLink proxy.
For details, the source code is available [here](https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub)
### Connectors
@@ -170,7 +170,7 @@ _Note: 1000 Series connectors accessible from the STM32/PX4_
### User Guide
The full user guide is available [here](https://docs.modalai.com/voxl-flight-quickstart).
The full user guide is available [here](https://docs.modalai.com/voxl-flight-quickstart/).
### How to Build
docs/en/flight_controller/nxp_rddrone_fmuk66.md
+4 -4
View File
@@ -45,21 +45,21 @@ Telemetry radios ([HGD-TELEM433](https://www.nxp.com/part/HGD-TELEM433) and [HGD
![RDDRONE-FMUK66 FMU Kit](../../assets/flight_controller/nxp_rddrone_fmuk66/rddrone_fmu66_kit_img_contents.jpg)
A "Lite" version RDDRONE-FMUK66L is also available which does not include the power module, GPS, Jlink or USB-TTL-3V3 console cable or SDCard.[Scroll down to see FMUK66L in the buy section of the FMUK66 buy page](https://www.nxp.com/design/design-center/development-boards-and-designs/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66#buy)
A "Lite" version RDDRONE-FMUK66L is also available which does not include the power module, GPS, Jlink or USB-TTL-3V3 console cable or SDCard.[Scroll down to see FMUK66L in the buy section of the FMUK66 buy page](https://www.nxp.com/products/no-longer-manufactured/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66#buy)
Additional information can be found in the [Technical Data Sheet](https://www.nxp.com/design/design-center/development-boards-and-designs/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66). <!-- www.nxp.com/rddrone-fmuk66 -->
Additional information can be found in the [Technical Data Sheet](https://www.nxp.com/products/no-longer-manufactured/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66). <!-- www.nxp.com/rddrone-fmuk66 -->
## Where to Buy {#store}
**RDDRONE-FMUK66** reference design kit may be purchased direct from NXP or from any of NXP's authorised worldwide network of [electronics distributors](https://www.nxp.com/support/sample-and-buy/distributor-network:DISTRIBUTORS).
- [Purchase Link](https://www.nxp.com/design/design-center/development-boards-and-designs/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66#buy) (www.nxp.com)
- [Purchase Link](https://www.nxp.com/products/no-longer-manufactured/px4-robotic-drone-vehicle-flight-management-unit-vmu-fmu-rddrone-fmuk66:RDDRONE-FMUK66#buy) (www.nxp.com)
- Telemetry radios are purchased separately depending on frequency band:
- [HGD-TELEM433](https://www.nxp.com/part/HGD-TELEM433)
- [HGD-TELEM915](https://www.nxp.com/part/HGD-TELEM915)
::: info
_RDDRONE-FMUK66_ FMU is also included in the complete HoverGames drone kit: [KIT-HGDRONEK66](https://www.nxp.com/design/design-center/development-boards-and-designs/nxp-hovergames-drone-kit-including-flight-controller-and-peripherals:KIT-HGDRONEK66#buy)
_RDDRONE-FMUK66_ FMU is also included in the complete HoverGames drone kit: [KIT-HGDRONEK66](https://www.nxp.com/products/no-longer-manufactured/nxp-hovergames-drone-kit-including-flight-controller-and-peripherals:KIT-HGDRONEK66#buy)
:::
<!--
docs/en/flight_modes_fw/mission.md
+2 -2
View File
@@ -95,8 +95,8 @@ _QGroundControl_ provides additional GCS-level mission handling support (in addi
For more information see:
- [Remove mission after vehicle lands](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/stable_v3.2_long.html#remove-mission-after-vehicle-lands)
- [Resume mission after Return mode](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/stable_v3.2_long.html#resume-mission)
- [Remove mission after vehicle lands](https://docs.qgroundcontrol.com/Stable_V4.3/en/qgc-user-guide/releases/stable_v3.2_long.html#remove-mission-after-vehicle-lands)
- [Resume mission after Return mode](https://docs.qgroundcontrol.com/Stable_V4.3/en/qgc-user-guide/releases/stable_v3.2_long.html#resume-mission)
## Mission Parameters
docs/en/flight_modes_mc/mission.md
+2 -2
View File
@@ -95,8 +95,8 @@ _QGroundControl_ provides additional GCS-level mission handling support (in addi
For more information see:
- [Remove mission after vehicle lands](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/stable_v3.2_long.html#remove-mission-after-vehicle-lands)
- [Resume mission after Return mode](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/stable_v3.2_long.html#resume-mission)
- [Remove mission after vehicle lands](https://docs.qgroundcontrol.com/Stable_V4.3/en/qgc-user-guide/releases/stable_v3.2_long.html#remove-mission-after-vehicle-lands)
- [Resume mission after Return mode](https://docs.qgroundcontrol.com/Stable_V4.3/en/qgc-user-guide/releases/stable_v3.2_long.html#resume-mission)
## Mission Parameters
docs/en/flight_modes_mc/position.md
+1 -1
View File
@@ -78,7 +78,7 @@ All the parameters in the [Multicopter Position Control](../advanced_config/para
### Position Loss/Safety
Position mode is dependent on having an acceptable position estimate.
If the estimate falls below acceptable levels, for example due to GPS loss, this may trigger a [Position (GPS) Loss Failsafe](../config/safety.md#position-gnss-loss-failsafe).
If the estimate falls below acceptable levels, for example due to GPS loss, this may trigger a [Position (GPS) Loss Failsafe](../config/safety.md#position-loss-failsafe).
Depending on configuration, whether you have a remote control, and whether there is an adequate altitude estimate, PX4 may switch to altitude mode, manual mode, land mode or terminate.
## See Also
docs/en/frames_multicopter/omnicopter.md
+3 -3
View File
@@ -18,7 +18,7 @@ The components needed for this build are:
::: info
You can select your own flight controller of choice, it just needs to support 8 DShot outputs.
:::
- GPS: [ZED-F9P](https://gnss.store/zed-f9p-gnss-modules/105-elt0092.html)
- GPS: [ZED-F9P](https://gnss.store/en/zed-f9p-gnss-modules/105-elt0092.html)
- [GPS helix antenna](https://gnss.store/products/elt0014)
::: info
Any other GPS may work as well, however a helix antenna is expected to perform better for inverted flights.
@@ -32,8 +32,8 @@ The components needed for this build are:
- Battery: we used a 6S 3300mAh LiPo. Make sure to check the dimensions so it fits the frame.
- Battery strap
- Frame:
- Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/Vierkant-Rohre/CFK-Vierkantrohr-8x8-7x7mm.html)
- Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/pi.php/Halbfabrikate/Rohre/CFK-Rohre-pultrudiert-pullwinding/Carbon-Microtubes-100cm-x-20-3mm.html)
- Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/de/produkt/cfk-vierkantrohr-8x8-7x7mm)
- Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/de/produkt/carbon-microtubes-100cm-x-20-3mm)
- Required lengths:
- square tube: 8 pieces with length of 248mm
- rods: 12x328mm, 6x465mm
docs/en/frames_sub/bluerov2.md
+1 -1
View File
@@ -12,7 +12,7 @@ Configuration_.
## Where to Buy
[BlueROV2](https://bluerobotics.com/store/rov/bluerov2/) + [BlueROV2 Heavy Configuration Retrofit Kit](https://bluerobotics.com/store/rov/bluerov2-upgrade-kits/brov2-heavy-retrofit/)
[BlueROV2](https://bluerobotics.com/store/rov/bluerov2/) + [BlueROV2 Heavy Configuration Retrofit Kit](https://bluerobotics.com/store/rov/bluerov2-accessories/brov2-heavy-kit/)
### Motor Mapping/Wiring
docs/en/frames_vtol/vtol_quadplane_foxtech_loong_2160.md
+4 -4
View File
@@ -43,14 +43,14 @@ The following options have been tested:
- [Holybro PM08D Power Module (alternative to Auterion PM)](https://holybro.com/collections/power-modules-pdbs/products/pm08d-digital-power-module-14s-200a)
- [GPS F9P (included in Skynode eval. kit)](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md)
- [GPS M9N (cheaper alternative to F9P)](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md)
- [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/airspeed-sensor-sdp33) — recommended for improved safety and performance
- [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/p/airspeed-sensor-sdp33) — recommended for improved safety and performance
- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor-ms4525do)
- [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) (Optional)
- [Lidar Seeed Studio PSK-CM8JL65-CC5 (cheaper alternative)](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) (Optional)
- [Radio (RC) System](../getting_started/rc_transmitter_receiver.md) of your preference
- [Groundstation and Radio link](https://holybro.com/collections/rc-radio-transmitter-receiver/products/skydroid-h12?variant=42940989931709)
- [Groundstation and Radio link](https://holybro.com/products/skydroid-h12)
- [USB-C extension cable](https://www.digitec.ch/en/s1/product/powerguard-usb-c-usb-c-025-m-usb-cables-22529949?dbq=1&gclid=Cj0KCQjw2cWgBhDYARIsALggUhrh-z-7DSU0wKfLBVa8filkXLQaxUpi7pC0ffQyRzLng8Ph01h2R1gaAp0mEALw_wcB&gclsrc=aw.ds)
- [I2C Splitter](https://www.3dxr.co.uk/autopilots-c2/the-cube-aka-pixhawk-2-1-c9/cube-cables-accessories-sensors-c15/cubepilot-i2c-can-splitter-jst-gh-4pin-p2840)
- [I2C Splitter](https://www.3dxr.co.uk/autopilots-c2/the-cube-aka-pixhawk-2-1-c9/cube-cables-accessories-sensors-c15/cubepilot-i2c-can-splitter-jst-gh-4pin-hx4-06152-p2840)
- [3D-Printed mounts](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/vtol/foxtech_loong_2160/loong-3d-prints.zip)
- 1x Baseplate
- 1x Stack-fixture
@@ -301,7 +301,7 @@ To load the file:
- If the [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) is used, [SENS_EN_SF1XX](../advanced_config/parameter_reference.md#SENS_EN_SF1XX) needs to be set to 6 (SF/LW/20c).
- Make that the correct airspeed sensor is selected.
If you use the recommended [SDP33 airspeed sensor](https://www.dualrc.com/parts/airspeed-sensor-sdp33) no changes will be needed as [SENS_EN_SDP3X](../advanced_config/parameter_reference.md#SENS_EN_SDP3X) is enabled (set to `1`) in the parameter file.
If you use the recommended [SDP33 airspeed sensor](https://www.dualrc.com/parts/p/airspeed-sensor-sdp33) no changes will be needed as [SENS_EN_SDP3X](../advanced_config/parameter_reference.md#SENS_EN_SDP3X) is enabled (set to `1`) in the parameter file.
### Sensor Calibration
docs/en/frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md
+1 -1
View File
@@ -24,7 +24,7 @@ A number of other components have been updated in the parts list too.
- [GetFPV](https://www.getfpv.com/lumenier-30a-blheli-s-esc-opto-2-4s.html)
- BEC (3A, 5-5.3V) (only needed if you are using ESCs which cannot act as a 5V power supply for the output rail)
- 3S 2200 mA LiPo battery
- Team Orion 3S 11.1V 50 C ([Hobbyshop store](https://www.hobbyshop.ch/modellbau-elektronik/akku/team-orion-lipo-2200-3s-11-1v-50c-xt60-ori60163.html))
- Team Orion 3S 11.1V 50 C ([Hobbyshop store](https://www.hobbyshop.ch/team-orion-lipo-2200-3s-11-1v-50c-xt60-ori60163.html))
- [Pixracer autopilot board + power module](../flight_controller/pixracer.md)
- [Digital airspeed sensor](https://hobbyking.com/en_us/hkpilot-32-digital-air-speed-sensor-and-pitot-tube-set.html)
docs/en/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md
+2 -2
View File
@@ -43,7 +43,7 @@ The approximate maximum size of the FC is: 50x110x22mm
- [GPS F9P (included in Skynode eval. kit)](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md)
- [GPS M9N (cheaper alternative to F9P)](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md)
- [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/airspeed-sensor-sdp33) — recommended for improved safety and performance
- [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/p/airspeed-sensor-sdp33) — recommended for improved safety and performance
- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor-ms4525do)
- [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) (Optional)
- [Lidar Seeed Studio PSK-CM8JL65-CC5 (cheaper alternative)](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) (Optional)
@@ -288,7 +288,7 @@ To load the file:
The airspeed sensor can be enabled in the [Parameters](../advanced_config/parameters.md#finding-updating-parameters) tab.
- If the [recommended airspeed sensor (SDP33)](https://www.dualrc.com/parts/airspeed-sensor-sdp33) is used, `SENS_EN_SDP3X` needs to be enabled.
- If the [recommended airspeed sensor (SDP33)](https://www.dualrc.com/parts/p/airspeed-sensor-sdp33) is used, `SENS_EN_SDP3X` needs to be enabled.
- If the [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) is used, `SENS_EN_SF1XX` needs to be set to 6 (SF/LW/20c).
### Sensor Calibration
docs/en/getting_started/flight_reporting.md
+1 -1
View File
@@ -38,7 +38,7 @@ For more information see [Settings > MAVLink Settings > MAVLink 2 Logging (PX4 o
## Sharing the Log Files for Review by PX4 Developers
The [Flight Review](https://logs.px4.io/) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../index.md#reporting-bugs-issues).
The [Flight Review](https://logs.px4.io/) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../contribute/support.md#issue-bug-reporting).
## Log Configuration
docs/en/gps_compass/gps_cuav_neo_3.md
+1 -1
View File
@@ -47,7 +47,7 @@ It integrates Ublox M9N, IST8310, three-color LED lights and safety switches, an
## Where to Buy
- [CUAV](https://cuav.en.alibaba.com/product/1600217379204-820872629/CUAV_NEO_3_M9N_GPS_Module_for_Pixhawk_Compass_gps_tracker_navigation_gps.html?spm=a2700.shop_oth.74.1.636e28725EvVHb)
- [CUAV](https://www.alibaba.com/product-detail/CUAV_NEO_3_M9N_GPS_Module_for_Pixhawk_Compass_gps_tracker_navigation_gps_1600217379204.html)
## Wiring and Connections
docs/en/gps_compass/rtk_gps.md
+40 -40
View File
@@ -14,51 +14,51 @@ Some RTK GNSS setups can provide yaw/heading information, as an alternative to t
## Supported Devices
PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p), [u-blox F9P](https://www.u-blox.com/en/product/zed-f9p-module) and the [Trimble MB-Two](https://oemgnss.trimble.com/en/products/receiver-modules/mb-two) GPS, and products that incorporate them.
PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p-series), [u-blox F9P](https://www.u-blox.com/en/product/zed-f9p-module) and the [Trimble MB-Two](https://oemgnss.trimble.com/en/products/receiver-modules/mb-two) GPS, and products that incorporate them.
The RTK compatible devices below that are expected to work with PX4 (it omits discontined devices).
The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used.
It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic).
| Device | GPS | Compass | [DroneCAN] | [GPS Yaw] | PPK |
| :-------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :--------: | :---------------------------------: | :-: |
| [ARK G5 RTK GPS](../dronecan/ark_g5_rtk_gps.md) | [mosaic-G5 P3] | IIS2MDC | ✓ | | |
| [ARK G5 RTK HEADING GPS](../dronecan/ark_g5_rtk_heading_gps.md) | [mosaic-G5 P3H] | IIS2MDC | ✓ | [Heading Capability][mosaic-G5 P3H] | |
| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P] | |
| [ARK RTK GPS L1 L5](../dronecan/ark_rtk_gps_l1_l2.md) | F9P | BMM150 | ✓ | | |
| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna] | |
| [ARK X20 RTK GPS](../dronecan/ark_x20_rtk_gps.md) | X20P | IIS2MDC | ✓ | | |
| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | |
| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P] | |
| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P] | |
| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ |
| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | |
| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | |
| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P] | |
| [DATAGNSS NANO HRTK Receiver](../gps_compass/rtk_gps_datagnss_nano_hrtk.md) | [D10P] | IST8310 | | ✘ | |
| [DATAGNSS GEM1305 RTK Receiver](../gps_compass/rtk_gps_gem1305.md) | TAU951M | IST8310 | | ✘ | |
| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | |
| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | |
| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P] | |
| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P] | |
| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P] | |
| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P] | |
| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P] | |
| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | |
| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P] | |
| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | |
| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna] | |
| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | |
| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | |
| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P] | |
| [Navisys L1/L2 ZED-F9P RTK - Base only](https://www.navisys.com.tw/productdetail?name=GR901&class=RTK) | F9P | | | | |
| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | |
| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | |
| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna] | ✓ |
| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna] | ✓ |
| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P] | |
| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P] | |
| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | |
| Device | GPS | Compass | [DroneCAN] | [GPS Yaw] | PPK |
| :----------------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :--------: | :---------------------------------: | :-: |
| [ARK G5 RTK GPS](../dronecan/ark_g5_rtk_gps.md) | [mosaic-G5 P3] | IIS2MDC | ✓ | | |
| [ARK G5 RTK HEADING GPS](../dronecan/ark_g5_rtk_heading_gps.md) | [mosaic-G5 P3H] | IIS2MDC | ✓ | [Heading Capability][mosaic-G5 P3H] | |
| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P] | |
| [ARK RTK GPS L1 L5](../dronecan/ark_rtk_gps_l1_l2.md) | F9P | BMM150 | ✓ | | |
| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna] | |
| [ARK X20 RTK GPS](../dronecan/ark_x20_rtk_gps.md) | X20P | IIS2MDC | ✓ | | |
| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | |
| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P] | |
| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P] | |
| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ |
| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | |
| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | |
| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P] | |
| [DATAGNSS NANO HRTK Receiver](../gps_compass/rtk_gps_datagnss_nano_hrtk.md) | [D10P] | IST8310 | | ✘ | |
| [DATAGNSS GEM1305 RTK Receiver](../gps_compass/rtk_gps_gem1305.md) | TAU951M | IST8310 | | ✘ | |
| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | |
| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | |
| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P] | |
| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P] | |
| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P] | |
| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P] | |
| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P] | |
| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | |
| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P] | |
| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | |
| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna] | |
| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | |
| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | |
| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P] | |
| [Navisys L1/L2 ZED-F9P RTK - Base only](https://www.navisys.com.tw/productdetail?name=GR901&class=RTK) | F9P | | | | |
| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | |
| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | |
| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna] | ✓ |
| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna] | ✓ |
| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P] | |
| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/sparkfun-gps-rtk2-board-zed-f9p-qwiic-gps-15136.html) | F9P | ✓ | | [Dual F9P] | |
| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | |
<!-- links used in above table -->
docs/en/gps_compass/rtk_gps_cuav_c-rtk-9ps.md
+2 -2
View File
@@ -1,6 +1,6 @@
# CUAV C-RTK 9Ps
The CUAV [C-RTK 9Ps](https://www.cuav.net/en/c_rtk_9ps/) is a multi-satellite, multi-band, centimeter-level, RTK GNSS system.
The CUAV [C-RTK 9Ps](https://www.cuav.net/en/c-rtk-9ps-en/) is a multi-satellite, multi-band, centimeter-level, RTK GNSS system.
The module simultaneously receives GPS, GLONASS, Galileo and Beidou satellite signals, enabling faster positioning and higher accuracy.
It also supports [RTK GPS Heading](../gps_compass/u-blox_f9p_heading.md) using dual modules.
@@ -12,7 +12,7 @@ This is ideal for survey drones, agricultural drones and other application scena
## Where to Buy
[cuav Store](https://store.cuav.net/index.php?route=product/product&path=61&product_id=187)
[cuav Store](https://store.cuav.net/?route=product%2Fproduct&path=61&product_id=187)
## Specification
docs/en/gps_compass/rtk_gps_cuav_c-rtk.md
+2 -2
View File
@@ -1,6 +1,6 @@
# CUAV C-RTK
The [CUAV C-RTK GPS receiver](https://www.cuav.net/en/c_rtk_9ps/) is an [RTK GPS module](../gps_compass/rtk_gps.md) for the mass market.
The [CUAV C-RTK GPS receiver](https://www.cuav.net/en/c-rtk-9ps-en/) is an [RTK GPS module](../gps_compass/rtk_gps.md) for the mass market.
A complete RTK system consists of at least two C-RTK modules \(one for the base station and the others for the aircraft\). Using RTK, PX4 can get its position with centimetre-level accuracy, which is much more accurate than can be provided by a normal GPS.
<img src="../../assets/hardware/gps/rtk_c-rtk.jpg" width="500px" title="C-RTK" />
@@ -8,7 +8,7 @@ A complete RTK system consists of at least two C-RTK modules \(one for the base
## Where to Buy
- [cuav taobao](https://item.taobao.com/item.htm?id=565380634341&spm=2014.21600712.0.0)
- [cuav aliexpress](https://www.aliexpress.com/store/product/CUAV-NEW-Flight-Controller-GPS-C-RTK-differential-positioning-navigation-module-GPS-for-PIX4-Pixhawk-pixhack/3257035_32853894248.html?spm=2114.12010608.0.0.75592fadQKPPEn)
- [cuav aliexpress](https://www.aliexpress.com/item/32853894248.html?spm=2114.12010608.0.0.75592fadQKPPEn)
## Configuration
docs/en/gps_compass/rtk_gps_cuav_c-rtk2.md
+2 -2
View File
@@ -1,6 +1,6 @@
# CUAV C-RTK2 GNSS Module (RTK/PPK)
The [CUAV C-RTK2 receiver](https://www.cuav.net/en/c_rtk_9ps/) is a high-performance PPK/RTK positioning module created by CUAV for professional applications such as drone aerial surveying and mapping.
The [CUAV C-RTK2 receiver](https://www.cuav.net/en/c-rtk-9ps-en/) is a high-performance PPK/RTK positioning module created by CUAV for professional applications such as drone aerial surveying and mapping.
It has a high-precision IMU and positioning module, and can reduce the number of required [control points](https://www.youtube.com/watch?v=3k7v5aXyuKQ) by more than to 80%.
In addition to surveying/mapping, it is suitable for many other use-cases, including: agricultural plant protection and drone swarms.
@@ -18,7 +18,7 @@ In addition to surveying/mapping, it is suitable for many other use-cases, inclu
## Where to Buy
- [CUAV Store](https://store.cuav.net/index.php?route=product/product&product_id=159)
- [CUAV Store](https://store.cuav.net/?route=product%2Fproduct&product_id=159)
- [CUAV aliexpress](https://pt.aliexpress.com/item/1005003754165772.html?spm=a2g0o.store_pc_groupList.8148356.13.2f893550i0NE4o)
# Quick Summary
docs/en/gps_compass/rtk_gps_datagnss_nano_hrtk.md
+2 -3
View File
@@ -90,7 +90,7 @@ Note that for the base we recommend the [NANO RTK Receiver](https://www.datagnss
![DATAGNSS NANO RTK Receiver with case](../../assets/hardware/gps/datagnss_gem1305/nano_rtk_with_case.png)
See to [How to setup Base station](https://wiki.datagnss.com/index.php/GEM1305-autopilot#Base_station_setup) for information on how to configure the module for use as a base station (not including step 6 and later, for which you would QGroundControl instead of Mission Planner).
See to [How to setup Base station](https://docs.datagnss.com/#Base_station_setup) for information on how to configure the module for use as a base station (not including step 6 and later, for which you would QGroundControl instead of Mission Planner).
### Rover Setup (PX4)
@@ -111,13 +111,12 @@ GPS and RTK configuration on PX4 via _QGroundControl_ is plug and play (see [RTK
## Resources
- [NANO RTK Receiver 2D drawing file](https://wiki.datagnss.com/images/3/31/EVK-DG-1206_V.2.0.pdf)
- [NANO HRTK Receiver Wiki](https://docs.datagnss.com/gnss/rtk_receiver/NANO/nano-helix-rtk/) (DATAGNSS WiKi)
- [HED-10L Heading RTK Receiver](https://docs.datagnss.com/gnss/rtk_receiver/HED-10L/)
## More information
- [NANO RTK Receiver](https://docs.datagnss.com/gnss/rtk_receiver/NANO/nano-rtk-receiver)
- [NANO RTK Receiver](https://docs.datagnss.com/gnss/rtk_receiver/NANO/nano-rtk-receiver/)
- [HELIX Antenna for RTK](https://www.datagnss.com/collections/rtk-antenna/products/smart-helix-antenna)
- [RTK Antenna AGR6302G](https://www.datagnss.com/collections/rtk-antenna/products/antenna-agr6302g)
- [AT400 RTK Antenna](https://www.datagnss.com/collections/rtk-antenna/products/at400-multi-band-antenna-for-rtk)
docs/en/gps_compass/rtk_gps_gem1305.md
+2 -3
View File
@@ -93,7 +93,7 @@ Note that for the base we recommend the [NANO RTK Receiver](https://www.datagnss
<img src="../../assets/hardware/gps/datagnss_gem1305/nano_rtk_with_case.png" width="500px" alt="DATAGNSS NANO RTK Receiver">
See to [How to setup Base station](https://wiki.datagnss.com/index.php/GEM1305-autopilot#Base_station_setup) for information on how to configure the module for use as a base station (not including step 6 and later, for which you would QGroundControl instead of Mission Planner).
See to [How to setup Base station](https://docs.datagnss.com/#Base_station_setup) for information on how to configure the module for use as a base station (not including step 6 and later, for which you would QGroundControl instead of Mission Planner).
### Rover Setup (PX4)
@@ -115,14 +115,13 @@ GPS and RTK configuration on PX4 via _QGroundControl_ is plug and play (see [RTK
## Resources
- [NANO RTK Receiver 2D drawing file](https://wiki.datagnss.com/images/3/31/EVK-DG-1206_V.2.0.pdf)
- [GEM1305 Wiki](https://docs.datagnss.com/gnss/rtk_receiver/GEM1305/) (DATAGNSS WiKi)
- [HED-10L Heading RTK Receiver](https://docs.datagnss.com/gnss/rtk_receiver/HED-10L/)
- [NANO HRTK Receiver](https://docs.datagnss.com/gnss/rtk_receiver/NANO/nano-helix-rtk/)
## More information
- [NANO RTK Receiver](https://www.datagnss.com/collections/evk/products/tau951m-1312-tiny-evk)
- [NANO RTK Receiver](https://www.datagnss.com/products/tau951m-1312-tiny-evk)
- [HELIX Antenna for RTK](https://www.datagnss.com/collections/rtk-antenna/products/smart-helix-antenna)
- [RTK Antenna AGR6302G](https://www.datagnss.com/collections/rtk-antenna/products/antenna-agr6302g)
- [AT400 RTK Antenna](https://www.datagnss.com/collections/rtk-antenna/products/at400-multi-band-antenna-for-rtk)
docs/en/gps_compass/rtk_gps_holybro_unicore_um982.md
+3 -3
View File
@@ -1,10 +1,10 @@
# Holybro H-RTK Unicore UM982 GPS
The [Holybro H-RTK Unicore UM982 GPS](https://holybro.com/products/h-rtk-um982) is an multi-band high-precision [RTK GNSS System](../gps_compass/rtk_gps.md) launched by Holybro.
The [Holybro H-RTK Unicore UM982 GPS](https://holybro.com/products/h-rtk-unicore-um982) is an multi-band high-precision [RTK GNSS System](../gps_compass/rtk_gps.md) launched by Holybro.
![HB-pmw3901-1](../../assets/hardware/gps/holybro-unicore-um982/holybro-unicore-um982-1.jpg)
This module is based on the [Unicore UM982 Chip](https://en.unicorecomm.com/products/detail/24), which supports RTK positioning and dual-antenna heading calculation.
This module is based on the [Unicore UM982 Chip](https://en.unicore.com/products/dual-antenna-gnss-um982/), which supports RTK positioning and dual-antenna heading calculation.
This means that it can generate a moving baseline headline/yaw determinations for autopilots with just one GPS module and dual antennas - a magnetometer is not needed.
Unlike when using a module such as the U-blox F9P, where you would need [two U-blox F9P modules to compute a heading angle](../gps_compass/u-blox_f9p_heading.md), with the Unicore UM982 GPS, you only need one GPS module!
@@ -20,7 +20,7 @@ Additional technical information can be found at [Holybro Technical Documentatio
## Where to Buy
- [Holybro Website](https://holybro.com/products/h-rtk-um982)
- [Holybro Website](https://holybro.com/products/h-rtk-unicore-um982)
## Wiring
docs/en/gps_compass/u-blox_f9p_heading.md
+1 -1
View File
@@ -10,7 +10,7 @@ This feature works on F9P devices that support CAN or expose the GPS UART2 port.
The following devices are supported:
- [ARK RTK GPS](https://arkelectron.com/product/ark-rtk-gps/) (arkelectron.com)
- [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) (www.sparkfun.com)
- [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/sparkfun-gps-rtk2-board-zed-f9p-qwiic-gps-15136.html) (www.sparkfun.com)
- [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) (store-drotek.com)
- [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) (store.mrobotics.io)
- [Holybro H-RTK F9P Helical or Base](https://holybro.com/products/h-rtk-f9p-gnss-series) (Holybro Store)
docs/en/hardware/board_support_guide.md
+1 -1
View File
@@ -93,7 +93,7 @@ _New_ experimental boards are allocated [VER and REV IDs](#ver_rev_id) based on
This category includes all boards that aren't supported by the PX4 project or a manufacturer, and that fall outside the"experimental" support.
- Board is somewhat compatible on paper with something we already support, and it would take minimal effort to raise it to "experimental", but neither the dev-team or the manufacturer are currently pursuing this
- Manufacturer/Owner of hardware violates our [Code of Conduct](https://discuss.px4.io/t/code-of-conduct/13655)
- Manufacturer/Owner of hardware violates our [Code of Conduct](https://discuss.px4.io/t/px4-community-code-of-conduct/13655)
- Closed source, where any of the necessary tools/libs/drivers/etc needed to add support for a board is deemed incompatible due to licensing restrictions
- Board doesn't meet minimum requirements outlined in the General requirements
docs/en/log/flight_log_analysis.md
+1 -1
View File
@@ -156,7 +156,7 @@ Key features:
### PX4Tools
[PX4Tools](https://github.com/dronecrew/px4tools) is a log analysis toolbox for the PX4 autopilot written in Python.
The recommended installation procedure is to use [anaconda3](https://conda.io/docs/index.html). See [px4tools github page](https://github.com/dronecrew/px4tools) for details.
The recommended installation procedure is to use [anaconda3](https://docs.conda.io/docs/index.html). See [px4tools github page](https://github.com/dronecrew/px4tools) for details.
Key features:
docs/en/mavlink/index.md
+1 -1
View File
@@ -77,7 +77,7 @@ You will need to work with the [MAVLink team](https://mavlink.io/en/contributing
:::
PX4 includes the [mavlink/mavlink](https://github.com/mavlink/mavlink) repo as a submodule under [/src/modules/mavlink](https://github.com/PX4/PX4-Autopilot/tree/main/src/modules/mavlink).
This contains XML definition files in [/mavlink/messages/1.0/](https://github.com/mavlink/mavlink/blob/master/message_definitions/v1.0/).
This contains XML definition files in [/mavlink/messages/1.0/](https://github.com/mavlink/mavlink/tree/master/message_definitions/v1.0).
The build toolchain generates the MAVLink 2 C header files at build time.
The XML file for which headers files are generated may be defined in the [PX4 kconfig board configuration](../hardware/porting_guide_config.md#px4-board-configuration-kconfig) on a per-board basis, using the variable `CONFIG_MAVLINK_DIALECT`:
docs/en/middleware/uorb.md
+2 -2
View File
@@ -145,8 +145,8 @@ Versioned messages include an additional field `uint32 MESSAGE_VERSION = x`, whe
Versioned and non-versioned messages are separated in the file system:
- Non-versioned topic message files and [server service](../ros2/user_guide.md#px4-ros-2-service-servers) message files remain in the [`msg/`](https://github.com/PX4/PX4-Autopilot/tree/main/msg) and [`srv/`](https://github.com/PX4/PX4-Autopilot/tree/main/srv) directories, respectively.
- The current (highest) version of message files are located in the `versioned` subfolders ([`msg/versioned`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/versioned) and [`srv/versioned`](https://github.com/PX4/PX4-Autopilot/tree/main/srv/versioned)).
- Older versions of messages are stored in nested `msg/px4_msgs_old/` subfolders ([`msg/px4_msgs_old/msg/`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/px4_msgs_old/msg) and [`msg/px4_msgs_old/srv/`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/px4_msgs_old/srv)).
- The current (highest) version of message files are located in the `versioned` subfolders ([`msg/versioned`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/versioned) and [`srv/versioned`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/versioned)).
- Older versions of messages are stored in nested `msg/px4_msgs_old/` subfolders ([`msg/px4_msgs_old/msg/`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/px4_msgs_old/msg) and [`msg/px4_msgs_old/srv/`](https://github.com/PX4/PX4-Autopilot/tree/main/msg/px4_msgs_old)).
The files are also renamed with a suffix to indicate their version number.
::: tip
docs/en/modules/modules_driver_ins.md
+1 -1
View File
@@ -9,7 +9,7 @@ Source: [drivers/ins/microstrain](https://github.com/PX4/PX4-Autopilot/tree/main
MicroStrain by HBK Inertial Sensor Driver.
Currently supports the following sensors:
-[CV7-AR](https://www.hbkworld.com/en/products/transducers/inertial-sensors/vertical-reference-units--vru-/3dm-cv7-ar) -[CV7-AHRS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/attitude-and-heading-reference-systems--ahrs-/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/inertial-navigation-systems--ins-/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/inertial-navigation-systems--ins-/3dm-cv7-gnss-ins)
-[CV7-AR](https://www.hbkworld.com/en/products/transducers/inertial-sensors/vertical-reference/3dm-cv7-ar) -[CV7-AHRS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/attitude-and-heading-reference-systems--ahrs-/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/inertial-navigation-systems--ins-/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/inertial-navigation-systems--ins-/3dm-cv7-gnss-ins)
This driver is not included in the firmware by default.
Include the module in firmware by setting the
docs/en/msg_docs/ActionRequest.md
+17 -17
View File
@@ -25,26 +25,26 @@ Request are published by `manual_control` and subscribed by the `commander` and
### ACTION {#ACTION}
| Name | Type | Value | Description |
| ------------------------------------------------------------------------------------------- | ------- | ----- | --------------------------------------------------------------------- |
| <a href="#ACTION_DISARM"></a> ACTION_DISARM | `uint8` | 0 | Disarm vehicle |
| <a href="#ACTION_ARM"></a> ACTION_ARM | `uint8` | 1 | Arm vehicle |
| <a href="#ACTION_TOGGLE_ARMING"></a> ACTION_TOGGLE_ARMING | `uint8` | 2 | Toggle arming |
| <a href="#ACTION_UNKILL"></a> ACTION_UNKILL | `uint8` | 3 | Revert a kill action |
| <a href="#ACTION_KILL"></a> ACTION_KILL | `uint8` | 4 | Kill vehicle (instantly stop the motors) |
| <a href="#ACTION_SWITCH_MODE"></a> ACTION_SWITCH_MODE | `uint8` | 5 | Switch mode. The target mode is set in the `mode` field. |
| <a href="#ACTION_VTOL_TRANSITION_TO_MULTICOPTER"></a> ACTION_VTOL_TRANSITION_TO_MULTICOPTER | `uint8` | 6 | Transition to hover flight |
| <a href="#ACTION_VTOL_TRANSITION_TO_FIXEDWING"></a> ACTION_VTOL_TRANSITION_TO_FIXEDWING | `uint8` | 7 | Transition to fast forward flight |
| <a href="#ACTION_TERMINATION"></a> ACTION_TERMINATION | `uint8` | 8 | Irreversibly output failsafe values on all outputs, trigger parachute |
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------------------- | ------- | ----- | --------------------------------------------------------------------- |
| <a id="#ACTION_DISARM"></a> ACTION_DISARM | `uint8` | 0 | Disarm vehicle |
| <a id="#ACTION_ARM"></a> ACTION_ARM | `uint8` | 1 | Arm vehicle |
| <a id="#ACTION_TOGGLE_ARMING"></a> ACTION_TOGGLE_ARMING | `uint8` | 2 | Toggle arming |
| <a id="#ACTION_UNKILL"></a> ACTION_UNKILL | `uint8` | 3 | Revert a kill action |
| <a id="#ACTION_KILL"></a> ACTION_KILL | `uint8` | 4 | Kill vehicle (instantly stop the motors) |
| <a id="#ACTION_SWITCH_MODE"></a> ACTION_SWITCH_MODE | `uint8` | 5 | Switch mode. The target mode is set in the `mode` field. |
| <a id="#ACTION_VTOL_TRANSITION_TO_MULTICOPTER"></a> ACTION_VTOL_TRANSITION_TO_MULTICOPTER | `uint8` | 6 | Transition to hover flight |
| <a id="#ACTION_VTOL_TRANSITION_TO_FIXEDWING"></a> ACTION_VTOL_TRANSITION_TO_FIXEDWING | `uint8` | 7 | Transition to fast forward flight |
| <a id="#ACTION_TERMINATION"></a> ACTION_TERMINATION | `uint8` | 8 | Irreversibly output failsafe values on all outputs, trigger parachute |
### SOURCE {#SOURCE}
| Name | Type | Value | Description |
| --------------------------------------------------------- | ------- | ----- | --------------------------------------------------------------- |
| <a href="#SOURCE_STICK_GESTURE"></a> SOURCE_STICK_GESTURE | `uint8` | 0 | Triggered by holding the sticks in a certain position |
| <a href="#SOURCE_RC_SWITCH"></a> SOURCE_RC_SWITCH | `uint8` | 1 | Triggered by an RC switch moving into a certain position |
| <a href="#SOURCE_RC_BUTTON"></a> SOURCE_RC_BUTTON | `uint8` | 2 | Triggered by a momentary button on the RC being pressed or held |
| <a href="#SOURCE_RC_MODE_SLOT"></a> SOURCE_RC_MODE_SLOT | `uint8` | 3 | Mode change through the RC mode selection mechanism |
| Name | Type | Value | Description |
| ------------------------------------------------------- | ------- | ----- | --------------------------------------------------------------- |
| <a id="#SOURCE_STICK_GESTURE"></a> SOURCE_STICK_GESTURE | `uint8` | 0 | Triggered by holding the sticks in a certain position |
| <a id="#SOURCE_RC_SWITCH"></a> SOURCE_RC_SWITCH | `uint8` | 1 | Triggered by an RC switch moving into a certain position |
| <a id="#SOURCE_RC_BUTTON"></a> SOURCE_RC_BUTTON | `uint8` | 2 | Triggered by a momentary button on the RC being pressed or held |
| <a id="#SOURCE_RC_MODE_SLOT"></a> SOURCE_RC_MODE_SLOT | `uint8` | 3 | Mode change through the RC mode selection mechanism |
## Source Message
docs/en/msg_docs/AirspeedValidated.md
+8 -8
View File
@@ -30,14 +30,14 @@ Used by controllers, estimators and for airspeed reporting to operator.
### SOURCE {#SOURCE}
| Name | Type | Value | Description |
| ----------------------------------------------------------------- | ------ | ----- | ----------------------- |
| <a href="#SOURCE_DISABLED"></a> SOURCE_DISABLED | `int8` | -1 | Disabled |
| <a href="#SOURCE_GROUND_MINUS_WIND"></a> SOURCE_GROUND_MINUS_WIND | `int8` | 0 | Ground speed minus wind |
| <a href="#SOURCE_SENSOR_1"></a> SOURCE_SENSOR_1 | `int8` | 1 | Sensor 1 |
| <a href="#SOURCE_SENSOR_2"></a> SOURCE_SENSOR_2 | `int8` | 2 | Sensor 2 |
| <a href="#SOURCE_SENSOR_3"></a> SOURCE_SENSOR_3 | `int8` | 3 | Sensor 3 |
| <a href="#SOURCE_SYNTHETIC"></a> SOURCE_SYNTHETIC | `int8` | 4 | Synthetic airspeed |
| Name | Type | Value | Description |
| --------------------------------------------------------------- | ------ | ----- | ----------------------- |
| <a id="#SOURCE_DISABLED"></a> SOURCE_DISABLED | `int8` | -1 | Disabled |
| <a id="#SOURCE_GROUND_MINUS_WIND"></a> SOURCE_GROUND_MINUS_WIND | `int8` | 0 | Ground speed minus wind |
| <a id="#SOURCE_SENSOR_1"></a> SOURCE_SENSOR_1 | `int8` | 1 | Sensor 1 |
| <a id="#SOURCE_SENSOR_2"></a> SOURCE_SENSOR_2 | `int8` | 2 | Sensor 2 |
| <a id="#SOURCE_SENSOR_3"></a> SOURCE_SENSOR_3 | `int8` | 3 | Sensor 3 |
| <a id="#SOURCE_SYNTHETIC"></a> SOURCE_SYNTHETIC | `int8` | 4 | Synthetic airspeed |
## Constants
docs/en/msg_docs/ArmingCheckReply.md
+3 -3
View File
@@ -45,9 +45,9 @@ The message is not used by internal/FMU components, as their mode requirements a
### HEALTH_COMPONENT_INDEX {#HEALTH_COMPONENT_INDEX}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------- | ------- | ----- | --------------------------------------------------------- |
| <a href="#HEALTH_COMPONENT_INDEX_NONE"></a> HEALTH_COMPONENT_INDEX_NONE | `uint8` | 0 | Index of health component for which this response applies |
| Name | Type | Value | Description |
| --------------------------------------------------------------------- | ------- | ----- | --------------------------------------------------------- |
| <a id="#HEALTH_COMPONENT_INDEX_NONE"></a> HEALTH_COMPONENT_INDEX_NONE | `uint8` | 0 | Index of health component for which this response applies |
## Constants
docs/en/msg_docs/AutotuneAttitudeControlStatus.md
+19 -19
View File
@@ -37,25 +37,25 @@ The rate_sp field is consumed by the controllers, while the remaining fields (mo
### STATE {#STATE}
| Name | Type | Value | Description |
| ------------------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------- |
| <a href="#STATE_IDLE"></a> STATE_IDLE | `uint8` | 0 | Idle (not running) |
| <a href="#STATE_INIT"></a> STATE_INIT | `uint8` | 1 | Initialize filters and setup |
| <a href="#STATE_ROLL_AMPLITUDE_DETECTION"></a> STATE_ROLL_AMPLITUDE_DETECTION | `uint8` | 2 | FW only: determine required excitation amplitude (roll) |
| <a href="#STATE_ROLL"></a> STATE_ROLL | `uint8` | 3 | Roll-axis excitation and model identification |
| <a href="#STATE_ROLL_PAUSE"></a> STATE_ROLL_PAUSE | `uint8` | 4 | Pause to return to level flight |
| <a href="#STATE_PITCH_AMPLITUDE_DETECTION"></a> STATE_PITCH_AMPLITUDE_DETECTION | `uint8` | 5 | FW only: determine required excitation amplitude (pitch) |
| <a href="#STATE_PITCH"></a> STATE_PITCH | `uint8` | 6 | Pitch-axis excitation and model identification |
| <a href="#STATE_PITCH_PAUSE"></a> STATE_PITCH_PAUSE | `uint8` | 7 | Pause to return to level flight |
| <a href="#STATE_YAW_AMPLITUDE_DETECTION"></a> STATE_YAW_AMPLITUDE_DETECTION | `uint8` | 8 | FW only: determine required excitation amplitude (yaw) |
| <a href="#STATE_YAW"></a> STATE_YAW | `uint8` | 9 | Yaw-axis excitation and model identification |
| <a href="#STATE_YAW_PAUSE"></a> STATE_YAW_PAUSE | `uint8` | 10 | Pause to return to level flight |
| <a href="#STATE_VERIFICATION"></a> STATE_VERIFICATION | `uint8` | 11 | Verify model and candidate gains |
| <a href="#STATE_APPLY"></a> STATE_APPLY | `uint8` | 12 | Apply gains |
| <a href="#STATE_TEST"></a> STATE_TEST | `uint8` | 13 | Test gains in closed-loop |
| <a href="#STATE_COMPLETE"></a> STATE_COMPLETE | `uint8` | 14 | Tuning completed successfully |
| <a href="#STATE_FAIL"></a> STATE_FAIL | `uint8` | 15 | Tuning failed (model invalid or controller unstable) |
| <a href="#STATE_WAIT_FOR_DISARM"></a> STATE_WAIT_FOR_DISARM | `uint8` | 16 | Waiting for disarm before finalizing |
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------- |
| <a id="#STATE_IDLE"></a> STATE_IDLE | `uint8` | 0 | Idle (not running) |
| <a id="#STATE_INIT"></a> STATE_INIT | `uint8` | 1 | Initialize filters and setup |
| <a id="#STATE_ROLL_AMPLITUDE_DETECTION"></a> STATE_ROLL_AMPLITUDE_DETECTION | `uint8` | 2 | FW only: determine required excitation amplitude (roll) |
| <a id="#STATE_ROLL"></a> STATE_ROLL | `uint8` | 3 | Roll-axis excitation and model identification |
| <a id="#STATE_ROLL_PAUSE"></a> STATE_ROLL_PAUSE | `uint8` | 4 | Pause to return to level flight |
| <a id="#STATE_PITCH_AMPLITUDE_DETECTION"></a> STATE_PITCH_AMPLITUDE_DETECTION | `uint8` | 5 | FW only: determine required excitation amplitude (pitch) |
| <a id="#STATE_PITCH"></a> STATE_PITCH | `uint8` | 6 | Pitch-axis excitation and model identification |
| <a id="#STATE_PITCH_PAUSE"></a> STATE_PITCH_PAUSE | `uint8` | 7 | Pause to return to level flight |
| <a id="#STATE_YAW_AMPLITUDE_DETECTION"></a> STATE_YAW_AMPLITUDE_DETECTION | `uint8` | 8 | FW only: determine required excitation amplitude (yaw) |
| <a id="#STATE_YAW"></a> STATE_YAW | `uint8` | 9 | Yaw-axis excitation and model identification |
| <a id="#STATE_YAW_PAUSE"></a> STATE_YAW_PAUSE | `uint8` | 10 | Pause to return to level flight |
| <a id="#STATE_VERIFICATION"></a> STATE_VERIFICATION | `uint8` | 11 | Verify model and candidate gains |
| <a id="#STATE_APPLY"></a> STATE_APPLY | `uint8` | 12 | Apply gains |
| <a id="#STATE_TEST"></a> STATE_TEST | `uint8` | 13 | Test gains in closed-loop |
| <a id="#STATE_COMPLETE"></a> STATE_COMPLETE | `uint8` | 14 | Tuning completed successfully |
| <a id="#STATE_FAIL"></a> STATE_FAIL | `uint8` | 15 | Tuning failed (model invalid or controller unstable) |
| <a id="#STATE_WAIT_FOR_DISARM"></a> STATE_WAIT_FOR_DISARM | `uint8` | 16 | Waiting for disarm before finalizing |
## Source Message
docs/en/msg_docs/AuxGlobalPosition.md
+9 -9
View File
@@ -30,15 +30,15 @@ pseudolites, visual navigation, or other positioning system.
### SOURCE {#SOURCE}
| Name | Type | Value | Description |
| ----------------------------------------------------- | ------- | ----- | -------------- |
| <a href="#SOURCE_UNKNOWN"></a> SOURCE_UNKNOWN | `uint8` | 0 | Unknown source |
| <a href="#SOURCE_GNSS"></a> SOURCE_GNSS | `uint8` | 1 | GNSS |
| <a href="#SOURCE_VISION"></a> SOURCE_VISION | `uint8` | 2 | Vision |
| <a href="#SOURCE_PSEUDOLITES"></a> SOURCE_PSEUDOLITES | `uint8` | 3 | Pseudolites |
| <a href="#SOURCE_TERRAIN"></a> SOURCE_TERRAIN | `uint8` | 4 | Terrain |
| <a href="#SOURCE_MAGNETIC"></a> SOURCE_MAGNETIC | `uint8` | 5 | Magnetic |
| <a href="#SOURCE_ESTIMATOR"></a> SOURCE_ESTIMATOR | `uint8` | 6 | Estimator |
| Name | Type | Value | Description |
| --------------------------------------------------- | ------- | ----- | -------------- |
| <a id="#SOURCE_UNKNOWN"></a> SOURCE_UNKNOWN | `uint8` | 0 | Unknown source |
| <a id="#SOURCE_GNSS"></a> SOURCE_GNSS | `uint8` | 1 | GNSS |
| <a id="#SOURCE_VISION"></a> SOURCE_VISION | `uint8` | 2 | Vision |
| <a id="#SOURCE_PSEUDOLITES"></a> SOURCE_PSEUDOLITES | `uint8` | 3 | Pseudolites |
| <a id="#SOURCE_TERRAIN"></a> SOURCE_TERRAIN | `uint8` | 4 | Terrain |
| <a id="#SOURCE_MAGNETIC"></a> SOURCE_MAGNETIC | `uint8` | 5 | Magnetic |
| <a id="#SOURCE_ESTIMATOR"></a> SOURCE_ESTIMATOR | `uint8` | 6 | Estimator |
## Constants
docs/en/msg_docs/BatteryStatus.md
+30 -30
View File
@@ -59,45 +59,45 @@ Battery instance information is also logged and streamed in MAVLink telemetry.
### SOURCE {#SOURCE}
| Name | Type | Value | Description |
| ------------------------------------------------------- | ------- | ----- | ---------------------------------------------- |
| <a href="#SOURCE_POWER_MODULE"></a> SOURCE_POWER_MODULE | `uint8` | 0 | Power module (analog ADC or I2C power monitor) |
| <a href="#SOURCE_EXTERNAL"></a> SOURCE_EXTERNAL | `uint8` | 1 | External (MAVLink, CAN, or external driver) |
| <a href="#SOURCE_ESCS"></a> SOURCE_ESCS | `uint8` | 2 | ESCs (via ESC telemetry) |
| Name | Type | Value | Description |
| ----------------------------------------------------- | ------- | ----- | ---------------------------------------------- |
| <a id="#SOURCE_POWER_MODULE"></a> SOURCE_POWER_MODULE | `uint8` | 0 | Power module (analog ADC or I2C power monitor) |
| <a id="#SOURCE_EXTERNAL"></a> SOURCE_EXTERNAL | `uint8` | 1 | External (MAVLink, CAN, or external driver) |
| <a id="#SOURCE_ESCS"></a> SOURCE_ESCS | `uint8` | 2 | ESCs (via ESC telemetry) |
### WARNING {#WARNING}
| Name | Type | Value | Description |
| --------------------------------------------------- | ------- | ----- | -------------------------------------------- |
| <a href="#WARNING_NONE"></a> WARNING_NONE | `uint8` | 0 | No battery low voltage warning active |
| <a href="#WARNING_LOW"></a> WARNING_LOW | `uint8` | 1 | Low voltage warning |
| <a href="#WARNING_CRITICAL"></a> WARNING_CRITICAL | `uint8` | 2 | Critical voltage, return / abort immediately |
| <a href="#WARNING_EMERGENCY"></a> WARNING_EMERGENCY | `uint8` | 3 | Immediate landing required |
| <a href="#WARNING_FAILED"></a> WARNING_FAILED | `uint8` | 4 | Battery has failed completely |
| Name | Type | Value | Description |
| ------------------------------------------------- | ------- | ----- | -------------------------------------------- |
| <a id="#WARNING_NONE"></a> WARNING_NONE | `uint8` | 0 | No battery low voltage warning active |
| <a id="#WARNING_LOW"></a> WARNING_LOW | `uint8` | 1 | Low voltage warning |
| <a id="#WARNING_CRITICAL"></a> WARNING_CRITICAL | `uint8` | 2 | Critical voltage, return / abort immediately |
| <a id="#WARNING_EMERGENCY"></a> WARNING_EMERGENCY | `uint8` | 3 | Immediate landing required |
| <a id="#WARNING_FAILED"></a> WARNING_FAILED | `uint8` | 4 | Battery has failed completely |
### STATE {#STATE}
| Name | Type | Value | Description |
| ----------------------------------------------- | ------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a href="#STATE_UNHEALTHY"></a> STATE_UNHEALTHY | `uint8` | 6 | Battery is diagnosed to be defective or an error occurred, usage is discouraged / prohibited. Possible causes (faults) are listed in faults field |
| <a href="#STATE_CHARGING"></a> STATE_CHARGING | `uint8` | 7 | Battery is charging |
| Name | Type | Value | Description |
| --------------------------------------------- | ------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="#STATE_UNHEALTHY"></a> STATE_UNHEALTHY | `uint8` | 6 | Battery is diagnosed to be defective or an error occurred, usage is discouraged / prohibited. Possible causes (faults) are listed in faults field |
| <a id="#STATE_CHARGING"></a> STATE_CHARGING | `uint8` | 7 | Battery is charging |
### FAULT {#FAULT}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------------------------------------------------------------- |
| <a href="#FAULT_DEEP_DISCHARGE"></a> FAULT_DEEP_DISCHARGE | `uint8` | 0 | Battery has deep discharged |
| <a href="#FAULT_SPIKES"></a> FAULT_SPIKES | `uint8` | 1 | Voltage spikes |
| <a href="#FAULT_CELL_FAIL"></a> FAULT_CELL_FAIL | `uint8` | 2 | One or more cells have failed |
| <a href="#FAULT_OVER_CURRENT"></a> FAULT_OVER_CURRENT | `uint8` | 3 | Over-current |
| <a href="#FAULT_OVER_TEMPERATURE"></a> FAULT_OVER_TEMPERATURE | `uint8` | 4 | Over-temperature |
| <a href="#FAULT_UNDER_TEMPERATURE"></a> FAULT_UNDER_TEMPERATURE | `uint8` | 5 | Under-temperature fault |
| <a href="#FAULT_INCOMPATIBLE_VOLTAGE"></a> FAULT_INCOMPATIBLE_VOLTAGE | `uint8` | 6 | Vehicle voltage is not compatible with this battery (batteries on same power rail should have similar voltage) |
| <a href="#FAULT_INCOMPATIBLE_FIRMWARE"></a> FAULT_INCOMPATIBLE_FIRMWARE | `uint8` | 7 | Battery firmware is not compatible with current autopilot firmware |
| <a href="#FAULT_INCOMPATIBLE_MODEL"></a> FAULT_INCOMPATIBLE_MODEL | `uint8` | 8 | Battery model is not supported by the system |
| <a href="#FAULT_HARDWARE_FAILURE"></a> FAULT_HARDWARE_FAILURE | `uint8` | 9 | Hardware problem |
| <a href="#FAULT_FAILED_TO_ARM"></a> FAULT_FAILED_TO_ARM | `uint8` | 10 | Battery had a problem while arming |
| <a href="#FAULT_COUNT"></a> FAULT_COUNT | `uint8` | 11 | Counter. Keep this as last element |
| Name | Type | Value | Description |
| --------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------------------------------------------------------------- |
| <a id="#FAULT_DEEP_DISCHARGE"></a> FAULT_DEEP_DISCHARGE | `uint8` | 0 | Battery has deep discharged |
| <a id="#FAULT_SPIKES"></a> FAULT_SPIKES | `uint8` | 1 | Voltage spikes |
| <a id="#FAULT_CELL_FAIL"></a> FAULT_CELL_FAIL | `uint8` | 2 | One or more cells have failed |
| <a id="#FAULT_OVER_CURRENT"></a> FAULT_OVER_CURRENT | `uint8` | 3 | Over-current |
| <a id="#FAULT_OVER_TEMPERATURE"></a> FAULT_OVER_TEMPERATURE | `uint8` | 4 | Over-temperature |
| <a id="#FAULT_UNDER_TEMPERATURE"></a> FAULT_UNDER_TEMPERATURE | `uint8` | 5 | Under-temperature fault |
| <a id="#FAULT_INCOMPATIBLE_VOLTAGE"></a> FAULT_INCOMPATIBLE_VOLTAGE | `uint8` | 6 | Vehicle voltage is not compatible with this battery (batteries on same power rail should have similar voltage) |
| <a id="#FAULT_INCOMPATIBLE_FIRMWARE"></a> FAULT_INCOMPATIBLE_FIRMWARE | `uint8` | 7 | Battery firmware is not compatible with current autopilot firmware |
| <a id="#FAULT_INCOMPATIBLE_MODEL"></a> FAULT_INCOMPATIBLE_MODEL | `uint8` | 8 | Battery model is not supported by the system |
| <a id="#FAULT_HARDWARE_FAILURE"></a> FAULT_HARDWARE_FAILURE | `uint8` | 9 | Hardware problem |
| <a id="#FAULT_FAILED_TO_ARM"></a> FAULT_FAILED_TO_ARM | `uint8` | 10 | Battery had a problem while arming |
| <a id="#FAULT_COUNT"></a> FAULT_COUNT | `uint8` | 11 | Counter. Keep this as last element |
## Constants
docs/en/msg_docs/BatteryStatusV0.md
+30 -30
View File
@@ -60,45 +60,45 @@ Battery instance information is also logged and streamed in MAVLink telemetry.
### SOURCE {#SOURCE}
| Name | Type | Value | Description |
| ------------------------------------------------------- | ------- | ----- | ---------------------------------------------- |
| <a href="#SOURCE_POWER_MODULE"></a> SOURCE_POWER_MODULE | `uint8` | 0 | Power module (analog ADC or I2C power monitor) |
| <a href="#SOURCE_EXTERNAL"></a> SOURCE_EXTERNAL | `uint8` | 1 | External (MAVLink, CAN, or external driver) |
| <a href="#SOURCE_ESCS"></a> SOURCE_ESCS | `uint8` | 2 | ESCs (via ESC telemetry) |
| Name | Type | Value | Description |
| ----------------------------------------------------- | ------- | ----- | ---------------------------------------------- |
| <a id="#SOURCE_POWER_MODULE"></a> SOURCE_POWER_MODULE | `uint8` | 0 | Power module (analog ADC or I2C power monitor) |
| <a id="#SOURCE_EXTERNAL"></a> SOURCE_EXTERNAL | `uint8` | 1 | External (MAVLink, CAN, or external driver) |
| <a id="#SOURCE_ESCS"></a> SOURCE_ESCS | `uint8` | 2 | ESCs (via ESC telemetry) |
### WARNING {#WARNING}
| Name | Type | Value | Description |
| --------------------------------------------------- | ------- | ----- | -------------------------------------------- |
| <a href="#WARNING_NONE"></a> WARNING_NONE | `uint8` | 0 | No battery low voltage warning active |
| <a href="#WARNING_LOW"></a> WARNING_LOW | `uint8` | 1 | Low voltage warning |
| <a href="#WARNING_CRITICAL"></a> WARNING_CRITICAL | `uint8` | 2 | Critical voltage, return / abort immediately |
| <a href="#WARNING_EMERGENCY"></a> WARNING_EMERGENCY | `uint8` | 3 | Immediate landing required |
| <a href="#WARNING_FAILED"></a> WARNING_FAILED | `uint8` | 4 | Battery has failed completely |
| Name | Type | Value | Description |
| ------------------------------------------------- | ------- | ----- | -------------------------------------------- |
| <a id="#WARNING_NONE"></a> WARNING_NONE | `uint8` | 0 | No battery low voltage warning active |
| <a id="#WARNING_LOW"></a> WARNING_LOW | `uint8` | 1 | Low voltage warning |
| <a id="#WARNING_CRITICAL"></a> WARNING_CRITICAL | `uint8` | 2 | Critical voltage, return / abort immediately |
| <a id="#WARNING_EMERGENCY"></a> WARNING_EMERGENCY | `uint8` | 3 | Immediate landing required |
| <a id="#WARNING_FAILED"></a> WARNING_FAILED | `uint8` | 4 | Battery has failed completely |
### STATE {#STATE}
| Name | Type | Value | Description |
| ----------------------------------------------- | ------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a href="#STATE_UNHEALTHY"></a> STATE_UNHEALTHY | `uint8` | 6 | Battery is diagnosed to be defective or an error occurred, usage is discouraged / prohibited. Possible causes (faults) are listed in faults field |
| <a href="#STATE_CHARGING"></a> STATE_CHARGING | `uint8` | 7 | Battery is charging |
| Name | Type | Value | Description |
| --------------------------------------------- | ------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="#STATE_UNHEALTHY"></a> STATE_UNHEALTHY | `uint8` | 6 | Battery is diagnosed to be defective or an error occurred, usage is discouraged / prohibited. Possible causes (faults) are listed in faults field |
| <a id="#STATE_CHARGING"></a> STATE_CHARGING | `uint8` | 7 | Battery is charging |
### FAULT {#FAULT}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------------------------------------------------------------- |
| <a href="#FAULT_DEEP_DISCHARGE"></a> FAULT_DEEP_DISCHARGE | `uint8` | 0 | Battery has deep discharged |
| <a href="#FAULT_SPIKES"></a> FAULT_SPIKES | `uint8` | 1 | Voltage spikes |
| <a href="#FAULT_CELL_FAIL"></a> FAULT_CELL_FAIL | `uint8` | 2 | One or more cells have failed |
| <a href="#FAULT_OVER_CURRENT"></a> FAULT_OVER_CURRENT | `uint8` | 3 | Over-current |
| <a href="#FAULT_OVER_TEMPERATURE"></a> FAULT_OVER_TEMPERATURE | `uint8` | 4 | Over-temperature |
| <a href="#FAULT_UNDER_TEMPERATURE"></a> FAULT_UNDER_TEMPERATURE | `uint8` | 5 | Under-temperature fault |
| <a href="#FAULT_INCOMPATIBLE_VOLTAGE"></a> FAULT_INCOMPATIBLE_VOLTAGE | `uint8` | 6 | Vehicle voltage is not compatible with this battery (batteries on same power rail should have similar voltage) |
| <a href="#FAULT_INCOMPATIBLE_FIRMWARE"></a> FAULT_INCOMPATIBLE_FIRMWARE | `uint8` | 7 | Battery firmware is not compatible with current autopilot firmware |
| <a href="#FAULT_INCOMPATIBLE_MODEL"></a> FAULT_INCOMPATIBLE_MODEL | `uint8` | 8 | Battery model is not supported by the system |
| <a href="#FAULT_HARDWARE_FAILURE"></a> FAULT_HARDWARE_FAILURE | `uint8` | 9 | Hardware problem |
| <a href="#FAULT_FAILED_TO_ARM"></a> FAULT_FAILED_TO_ARM | `uint8` | 10 | Battery had a problem while arming |
| <a href="#FAULT_COUNT"></a> FAULT_COUNT | `uint8` | 11 | Counter. Keep this as last element |
| Name | Type | Value | Description |
| --------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------------------------------------------------------------- |
| <a id="#FAULT_DEEP_DISCHARGE"></a> FAULT_DEEP_DISCHARGE | `uint8` | 0 | Battery has deep discharged |
| <a id="#FAULT_SPIKES"></a> FAULT_SPIKES | `uint8` | 1 | Voltage spikes |
| <a id="#FAULT_CELL_FAIL"></a> FAULT_CELL_FAIL | `uint8` | 2 | One or more cells have failed |
| <a id="#FAULT_OVER_CURRENT"></a> FAULT_OVER_CURRENT | `uint8` | 3 | Over-current |
| <a id="#FAULT_OVER_TEMPERATURE"></a> FAULT_OVER_TEMPERATURE | `uint8` | 4 | Over-temperature |
| <a id="#FAULT_UNDER_TEMPERATURE"></a> FAULT_UNDER_TEMPERATURE | `uint8` | 5 | Under-temperature fault |
| <a id="#FAULT_INCOMPATIBLE_VOLTAGE"></a> FAULT_INCOMPATIBLE_VOLTAGE | `uint8` | 6 | Vehicle voltage is not compatible with this battery (batteries on same power rail should have similar voltage) |
| <a id="#FAULT_INCOMPATIBLE_FIRMWARE"></a> FAULT_INCOMPATIBLE_FIRMWARE | `uint8` | 7 | Battery firmware is not compatible with current autopilot firmware |
| <a id="#FAULT_INCOMPATIBLE_MODEL"></a> FAULT_INCOMPATIBLE_MODEL | `uint8` | 8 | Battery model is not supported by the system |
| <a id="#FAULT_HARDWARE_FAILURE"></a> FAULT_HARDWARE_FAILURE | `uint8` | 9 | Hardware problem |
| <a id="#FAULT_FAILED_TO_ARM"></a> FAULT_FAILED_TO_ARM | `uint8` | 10 | Battery had a problem while arming |
| <a id="#FAULT_COUNT"></a> FAULT_COUNT | `uint8` | 11 | Counter. Keep this as last element |
## Constants
docs/en/msg_docs/CellularStatus.md
+28 -28
View File
@@ -27,40 +27,40 @@ This is currently used only for logging cell status from MAVLink.
### STATUS_FLAG {#STATUS_FLAG}
| Name | Type | Value | Description |
| ------------------------------------------------------------------- | -------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a href="#STATUS_FLAG_UNKNOWN"></a> STATUS_FLAG_UNKNOWN | `uint16` | 1 | State unknown or not reportable |
| <a href="#STATUS_FLAG_FAILED"></a> STATUS_FLAG_FAILED | `uint16` | 2 | Modem is unusable |
| <a href="#STATUS_FLAG_INITIALIZING"></a> STATUS_FLAG_INITIALIZING | `uint16` | 4 | Modem is being initialized |
| <a href="#STATUS_FLAG_LOCKED"></a> STATUS_FLAG_LOCKED | `uint16` | 8 | Modem is locked |
| <a href="#STATUS_FLAG_DISABLED"></a> STATUS_FLAG_DISABLED | `uint16` | 16 | Modem is not enabled and is powered down |
| <a href="#STATUS_FLAG_DISABLING"></a> STATUS_FLAG_DISABLING | `uint16` | 32 | Modem is currently transitioning to the STATUS_FLAG_DISABLED state |
| <a href="#STATUS_FLAG_ENABLING"></a> STATUS_FLAG_ENABLING | `uint16` | 64 | Modem is currently transitioning to the STATUS_FLAG_ENABLED state |
| <a href="#STATUS_FLAG_ENABLED"></a> STATUS_FLAG_ENABLED | `uint16` | 128 | Modem is enabled and powered on but not registered with a network provider and not available for data connections |
| <a href="#STATUS_FLAG_SEARCHING"></a> STATUS_FLAG_SEARCHING | `uint16` | 256 | Modem is searching for a network provider to register |
| <a href="#STATUS_FLAG_REGISTERED"></a> STATUS_FLAG_REGISTERED | `uint16` | 512 | Modem is registered with a network provider, and data connections and messaging may be available for use |
| <a href="#STATUS_FLAG_DISCONNECTING"></a> STATUS_FLAG_DISCONNECTING | `uint16` | 1024 | Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated |
| <a href="#STATUS_FLAG_CONNECTING"></a> STATUS_FLAG_CONNECTING | `uint16` | 2048 | Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered |
| <a href="#STATUS_FLAG_CONNECTED"></a> STATUS_FLAG_CONNECTED | `uint16` | 4096 | One or more packet data bearers is active and connected |
| Name | Type | Value | Description |
| ----------------------------------------------------------------- | -------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="#STATUS_FLAG_UNKNOWN"></a> STATUS_FLAG_UNKNOWN | `uint16` | 1 | State unknown or not reportable |
| <a id="#STATUS_FLAG_FAILED"></a> STATUS_FLAG_FAILED | `uint16` | 2 | Modem is unusable |
| <a id="#STATUS_FLAG_INITIALIZING"></a> STATUS_FLAG_INITIALIZING | `uint16` | 4 | Modem is being initialized |
| <a id="#STATUS_FLAG_LOCKED"></a> STATUS_FLAG_LOCKED | `uint16` | 8 | Modem is locked |
| <a id="#STATUS_FLAG_DISABLED"></a> STATUS_FLAG_DISABLED | `uint16` | 16 | Modem is not enabled and is powered down |
| <a id="#STATUS_FLAG_DISABLING"></a> STATUS_FLAG_DISABLING | `uint16` | 32 | Modem is currently transitioning to the STATUS_FLAG_DISABLED state |
| <a id="#STATUS_FLAG_ENABLING"></a> STATUS_FLAG_ENABLING | `uint16` | 64 | Modem is currently transitioning to the STATUS_FLAG_ENABLED state |
| <a id="#STATUS_FLAG_ENABLED"></a> STATUS_FLAG_ENABLED | `uint16` | 128 | Modem is enabled and powered on but not registered with a network provider and not available for data connections |
| <a id="#STATUS_FLAG_SEARCHING"></a> STATUS_FLAG_SEARCHING | `uint16` | 256 | Modem is searching for a network provider to register |
| <a id="#STATUS_FLAG_REGISTERED"></a> STATUS_FLAG_REGISTERED | `uint16` | 512 | Modem is registered with a network provider, and data connections and messaging may be available for use |
| <a id="#STATUS_FLAG_DISCONNECTING"></a> STATUS_FLAG_DISCONNECTING | `uint16` | 1024 | Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated |
| <a id="#STATUS_FLAG_CONNECTING"></a> STATUS_FLAG_CONNECTING | `uint16` | 2048 | Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered |
| <a id="#STATUS_FLAG_CONNECTED"></a> STATUS_FLAG_CONNECTED | `uint16` | 4096 | One or more packet data bearers is active and connected |
### FAILURE_REASON {#FAILURE_REASON}
| Name | Type | Value | Description |
| --------------------------------------------------------------------- | ------- | ----- | ----------------------------------------------- |
| <a href="#FAILURE_REASON_NONE"></a> FAILURE_REASON_NONE | `uint8` | 0 | No error |
| <a href="#FAILURE_REASON_UNKNOWN"></a> FAILURE_REASON_UNKNOWN | `uint8` | 1 | Error state is unknown |
| <a href="#FAILURE_REASON_SIM_MISSING"></a> FAILURE_REASON_SIM_MISSING | `uint8` | 2 | SIM is required for the modem but missing |
| <a href="#FAILURE_REASON_SIM_ERROR"></a> FAILURE_REASON_SIM_ERROR | `uint8` | 3 | SIM is available, but not usable for connection |
| Name | Type | Value | Description |
| ------------------------------------------------------------------- | ------- | ----- | ----------------------------------------------- |
| <a id="#FAILURE_REASON_NONE"></a> FAILURE_REASON_NONE | `uint8` | 0 | No error |
| <a id="#FAILURE_REASON_UNKNOWN"></a> FAILURE_REASON_UNKNOWN | `uint8` | 1 | Error state is unknown |
| <a id="#FAILURE_REASON_SIM_MISSING"></a> FAILURE_REASON_SIM_MISSING | `uint8` | 2 | SIM is required for the modem but missing |
| <a id="#FAILURE_REASON_SIM_ERROR"></a> FAILURE_REASON_SIM_ERROR | `uint8` | 3 | SIM is available, but not usable for connection |
### CELLULAR_NETWORK_RADIO_TYPE {#CELLULAR_NETWORK_RADIO_TYPE}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------------- | ------- | ----- | ----------- |
| <a href="#CELLULAR_NETWORK_RADIO_TYPE_NONE"></a> CELLULAR_NETWORK_RADIO_TYPE_NONE | `uint8` | 0 | None |
| <a href="#CELLULAR_NETWORK_RADIO_TYPE_GSM"></a> CELLULAR_NETWORK_RADIO_TYPE_GSM | `uint8` | 1 | GSM |
| <a href="#CELLULAR_NETWORK_RADIO_TYPE_CDMA"></a> CELLULAR_NETWORK_RADIO_TYPE_CDMA | `uint8` | 2 | CDMA |
| <a href="#CELLULAR_NETWORK_RADIO_TYPE_WCDMA"></a> CELLULAR_NETWORK_RADIO_TYPE_WCDMA | `uint8` | 3 | WCDMA |
| <a href="#CELLULAR_NETWORK_RADIO_TYPE_LTE"></a> CELLULAR_NETWORK_RADIO_TYPE_LTE | `uint8` | 4 | LTE |
| Name | Type | Value | Description |
| --------------------------------------------------------------------------------- | ------- | ----- | ----------- |
| <a id="#CELLULAR_NETWORK_RADIO_TYPE_NONE"></a> CELLULAR_NETWORK_RADIO_TYPE_NONE | `uint8` | 0 | None |
| <a id="#CELLULAR_NETWORK_RADIO_TYPE_GSM"></a> CELLULAR_NETWORK_RADIO_TYPE_GSM | `uint8` | 1 | GSM |
| <a id="#CELLULAR_NETWORK_RADIO_TYPE_CDMA"></a> CELLULAR_NETWORK_RADIO_TYPE_CDMA | `uint8` | 2 | CDMA |
| <a id="#CELLULAR_NETWORK_RADIO_TYPE_WCDMA"></a> CELLULAR_NETWORK_RADIO_TYPE_WCDMA | `uint8` | 3 | WCDMA |
| <a id="#CELLULAR_NETWORK_RADIO_TYPE_LTE"></a> CELLULAR_NETWORK_RADIO_TYPE_LTE | `uint8` | 4 | LTE |
## Source Message
docs/en/msg_docs/DeviceInformation.md
+18 -18
View File
@@ -27,24 +27,24 @@ as well as tracking of the used firmware versions on the devices.
### DEVICE_TYPE {#DEVICE_TYPE}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------------- | ------- | ----- | ---------------------- |
| <a href="#DEVICE_TYPE_GENERIC"></a> DEVICE_TYPE_GENERIC | `uint8` | 0 | Generic/unknown sensor |
| <a href="#DEVICE_TYPE_AIRSPEED"></a> DEVICE_TYPE_AIRSPEED | `uint8` | 1 | Airspeed sensor |
| <a href="#DEVICE_TYPE_ESC"></a> DEVICE_TYPE_ESC | `uint8` | 2 | ESC |
| <a href="#DEVICE_TYPE_SERVO"></a> DEVICE_TYPE_SERVO | `uint8` | 3 | Servo |
| <a href="#DEVICE_TYPE_GPS"></a> DEVICE_TYPE_GPS | `uint8` | 4 | GPS |
| <a href="#DEVICE_TYPE_MAGNETOMETER"></a> DEVICE_TYPE_MAGNETOMETER | `uint8` | 5 | Magnetometer |
| <a href="#DEVICE_TYPE_PARACHUTE"></a> DEVICE_TYPE_PARACHUTE | `uint8` | 6 | Parachute |
| <a href="#DEVICE_TYPE_RANGEFINDER"></a> DEVICE_TYPE_RANGEFINDER | `uint8` | 7 | Rangefinder |
| <a href="#DEVICE_TYPE_WINCH"></a> DEVICE_TYPE_WINCH | `uint8` | 8 | Winch |
| <a href="#DEVICE_TYPE_BAROMETER"></a> DEVICE_TYPE_BAROMETER | `uint8` | 9 | Barometer |
| <a href="#DEVICE_TYPE_OPTICAL_FLOW"></a> DEVICE_TYPE_OPTICAL_FLOW | `uint8` | 10 | Optical flow |
| <a href="#DEVICE_TYPE_ACCELEROMETER"></a> DEVICE_TYPE_ACCELEROMETER | `uint8` | 11 | Accelerometer |
| <a href="#DEVICE_TYPE_GYROSCOPE"></a> DEVICE_TYPE_GYROSCOPE | `uint8` | 12 | Gyroscope |
| <a href="#DEVICE_TYPE_DIFFERENTIAL_PRESSURE"></a> DEVICE_TYPE_DIFFERENTIAL_PRESSURE | `uint8` | 13 | Differential pressure |
| <a href="#DEVICE_TYPE_BATTERY"></a> DEVICE_TYPE_BATTERY | `uint8` | 14 | Battery |
| <a href="#DEVICE_TYPE_HYGROMETER"></a> DEVICE_TYPE_HYGROMETER | `uint8` | 15 | Hygrometer |
| Name | Type | Value | Description |
| --------------------------------------------------------------------------------- | ------- | ----- | ---------------------- |
| <a id="#DEVICE_TYPE_GENERIC"></a> DEVICE_TYPE_GENERIC | `uint8` | 0 | Generic/unknown sensor |
| <a id="#DEVICE_TYPE_AIRSPEED"></a> DEVICE_TYPE_AIRSPEED | `uint8` | 1 | Airspeed sensor |
| <a id="#DEVICE_TYPE_ESC"></a> DEVICE_TYPE_ESC | `uint8` | 2 | ESC |
| <a id="#DEVICE_TYPE_SERVO"></a> DEVICE_TYPE_SERVO | `uint8` | 3 | Servo |
| <a id="#DEVICE_TYPE_GPS"></a> DEVICE_TYPE_GPS | `uint8` | 4 | GPS |
| <a id="#DEVICE_TYPE_MAGNETOMETER"></a> DEVICE_TYPE_MAGNETOMETER | `uint8` | 5 | Magnetometer |
| <a id="#DEVICE_TYPE_PARACHUTE"></a> DEVICE_TYPE_PARACHUTE | `uint8` | 6 | Parachute |
| <a id="#DEVICE_TYPE_RANGEFINDER"></a> DEVICE_TYPE_RANGEFINDER | `uint8` | 7 | Rangefinder |
| <a id="#DEVICE_TYPE_WINCH"></a> DEVICE_TYPE_WINCH | `uint8` | 8 | Winch |
| <a id="#DEVICE_TYPE_BAROMETER"></a> DEVICE_TYPE_BAROMETER | `uint8` | 9 | Barometer |
| <a id="#DEVICE_TYPE_OPTICAL_FLOW"></a> DEVICE_TYPE_OPTICAL_FLOW | `uint8` | 10 | Optical flow |
| <a id="#DEVICE_TYPE_ACCELEROMETER"></a> DEVICE_TYPE_ACCELEROMETER | `uint8` | 11 | Accelerometer |
| <a id="#DEVICE_TYPE_GYROSCOPE"></a> DEVICE_TYPE_GYROSCOPE | `uint8` | 12 | Gyroscope |
| <a id="#DEVICE_TYPE_DIFFERENTIAL_PRESSURE"></a> DEVICE_TYPE_DIFFERENTIAL_PRESSURE | `uint8` | 13 | Differential pressure |
| <a id="#DEVICE_TYPE_BATTERY"></a> DEVICE_TYPE_BATTERY | `uint8` | 14 | Battery |
| <a id="#DEVICE_TYPE_HYGROMETER"></a> DEVICE_TYPE_HYGROMETER | `uint8` | 15 | Hygrometer |
## Source Message
docs/en/msg_docs/VehicleCommand.md
+22 -22
View File
@@ -1490,34 +1490,34 @@ Change mode by specifying nav_state directly.
### ORBIT_YAW_BEHAVIOUR {#ORBIT_YAW_BEHAVIOUR}
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------------------------------------------- | ------- | ----- | ----------- |
| <a href="#ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TO_CIRCLE_CENTER"></a> ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TO_CIRCLE_CENTER | `uint8` | 0 |
| <a href="#ORBIT_YAW_BEHAVIOUR_HOLD_INITIAL_HEADING"></a> ORBIT_YAW_BEHAVIOUR_HOLD_INITIAL_HEADING | `uint8` | 1 |
| <a href="#ORBIT_YAW_BEHAVIOUR_UNCONTROLLED"></a> ORBIT_YAW_BEHAVIOUR_UNCONTROLLED | `uint8` | 2 |
| <a href="#ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TANGENT_TO_CIRCLE"></a> ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TANGENT_TO_CIRCLE | `uint8` | 3 |
| <a href="#ORBIT_YAW_BEHAVIOUR_RC_CONTROLLED"></a> ORBIT_YAW_BEHAVIOUR_RC_CONTROLLED | `uint8` | 4 |
| <a href="#ORBIT_YAW_BEHAVIOUR_UNCHANGED"></a> ORBIT_YAW_BEHAVIOUR_UNCHANGED | `uint8` | 5 |
| Name | Type | Value | Description |
| --------------------------------------------------------------------------------------------------------------- | ------- | ----- | ----------- |
| <a id="#ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TO_CIRCLE_CENTER"></a> ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TO_CIRCLE_CENTER | `uint8` | 0 |
| <a id="#ORBIT_YAW_BEHAVIOUR_HOLD_INITIAL_HEADING"></a> ORBIT_YAW_BEHAVIOUR_HOLD_INITIAL_HEADING | `uint8` | 1 |
| <a id="#ORBIT_YAW_BEHAVIOUR_UNCONTROLLED"></a> ORBIT_YAW_BEHAVIOUR_UNCONTROLLED | `uint8` | 2 |
| <a id="#ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TANGENT_TO_CIRCLE"></a> ORBIT_YAW_BEHAVIOUR_HOLD_FRONT_TANGENT_TO_CIRCLE | `uint8` | 3 |
| <a id="#ORBIT_YAW_BEHAVIOUR_RC_CONTROLLED"></a> ORBIT_YAW_BEHAVIOUR_RC_CONTROLLED | `uint8` | 4 |
| <a id="#ORBIT_YAW_BEHAVIOUR_UNCHANGED"></a> ORBIT_YAW_BEHAVIOUR_UNCHANGED | `uint8` | 5 |
### VEHICLE_ROI {#VEHICLE_ROI}
| Name | Type | Value | Description |
| --------------------------------------------------------- | ------- | ----- | ---------------------------- |
| <a href="#VEHICLE_ROI_NONE"></a> VEHICLE_ROI_NONE | `uint8` | 0 | No region of interest. |
| <a href="#VEHICLE_ROI_WPNEXT"></a> VEHICLE_ROI_WPNEXT | `uint8` | 1 | Point toward next MISSION. |
| <a href="#VEHICLE_ROI_WPINDEX"></a> VEHICLE_ROI_WPINDEX | `uint8` | 2 | Point toward given MISSION. |
| <a href="#VEHICLE_ROI_LOCATION"></a> VEHICLE_ROI_LOCATION | `uint8` | 3 | Point toward fixed location. |
| <a href="#VEHICLE_ROI_TARGET"></a> VEHICLE_ROI_TARGET | `uint8` | 4 | Point toward target. |
| <a href="#VEHICLE_ROI_ENUM_END"></a> VEHICLE_ROI_ENUM_END | `uint8` | 5 |
| Name | Type | Value | Description |
| ------------------------------------------------------- | ------- | ----- | ---------------------------- |
| <a id="#VEHICLE_ROI_NONE"></a> VEHICLE_ROI_NONE | `uint8` | 0 | No region of interest. |
| <a id="#VEHICLE_ROI_WPNEXT"></a> VEHICLE_ROI_WPNEXT | `uint8` | 1 | Point toward next MISSION. |
| <a id="#VEHICLE_ROI_WPINDEX"></a> VEHICLE_ROI_WPINDEX | `uint8` | 2 | Point toward given MISSION. |
| <a id="#VEHICLE_ROI_LOCATION"></a> VEHICLE_ROI_LOCATION | `uint8` | 3 | Point toward fixed location. |
| <a id="#VEHICLE_ROI_TARGET"></a> VEHICLE_ROI_TARGET | `uint8` | 4 | Point toward target. |
| <a id="#VEHICLE_ROI_ENUM_END"></a> VEHICLE_ROI_ENUM_END | `uint8` | 5 |
### SPEED_TYPE {#SPEED_TYPE}
| Name | Type | Value | Description |
| ----------------------------------------------------------------- | ------- | ----- | ----------- |
| <a href="#SPEED_TYPE_AIRSPEED"></a> SPEED_TYPE_AIRSPEED | `uint8` | 0 |
| <a href="#SPEED_TYPE_GROUNDSPEED"></a> SPEED_TYPE_GROUNDSPEED | `uint8` | 1 |
| <a href="#SPEED_TYPE_CLIMB_SPEED"></a> SPEED_TYPE_CLIMB_SPEED | `uint8` | 2 |
| <a href="#SPEED_TYPE_DESCEND_SPEED"></a> SPEED_TYPE_DESCEND_SPEED | `uint8` | 3 |
| Name | Type | Value | Description |
| --------------------------------------------------------------- | ------- | ----- | ----------- |
| <a id="#SPEED_TYPE_AIRSPEED"></a> SPEED_TYPE_AIRSPEED | `uint8` | 0 |
| <a id="#SPEED_TYPE_GROUNDSPEED"></a> SPEED_TYPE_GROUNDSPEED | `uint8` | 1 |
| <a id="#SPEED_TYPE_CLIMB_SPEED"></a> SPEED_TYPE_CLIMB_SPEED | `uint8` | 2 |
| <a id="#SPEED_TYPE_DESCEND_SPEED"></a> SPEED_TYPE_DESCEND_SPEED | `uint8` | 3 |
### MAV_MOUNT_MODE {#MAV_MOUNT_MODE}
docs/en/msg_docs/VehicleCommandAck.md
+12 -12
View File
@@ -28,18 +28,18 @@ Follows the MAVLink COMMAND_ACK message definition
### VEHICLE_CMD_RESULT {#VEHICLE_CMD_RESULT}
| Name | Type | Value | Description |
| ------------------------------------------------------------------------------------------------- | ------- | ----- | ---------------------------------------------------- |
| <a href="#VEHICLE_CMD_RESULT_ACCEPTED"></a> VEHICLE_CMD_RESULT_ACCEPTED | `uint8` | 0 | Command ACCEPTED and EXECUTED |
| <a href="#VEHICLE_CMD_RESULT_TEMPORARILY_REJECTED"></a> VEHICLE_CMD_RESULT_TEMPORARILY_REJECTED | `uint8` | 1 | Command TEMPORARY REJECTED/DENIED |
| <a href="#VEHICLE_CMD_RESULT_DENIED"></a> VEHICLE_CMD_RESULT_DENIED | `uint8` | 2 | Command PERMANENTLY DENIED |
| <a href="#VEHICLE_CMD_RESULT_UNSUPPORTED"></a> VEHICLE_CMD_RESULT_UNSUPPORTED | `uint8` | 3 | Command UNKNOWN/UNSUPPORTED |
| <a href="#VEHICLE_CMD_RESULT_FAILED"></a> VEHICLE_CMD_RESULT_FAILED | `uint8` | 4 | Command executed, but failed |
| <a href="#VEHICLE_CMD_RESULT_IN_PROGRESS"></a> VEHICLE_CMD_RESULT_IN_PROGRESS | `uint8` | 5 | Command being executed |
| <a href="#VEHICLE_CMD_RESULT_CANCELLED"></a> VEHICLE_CMD_RESULT_CANCELLED | `uint8` | 6 | Command Canceled |
| <a href="#VEHICLE_CMD_RESULT_COMMAND_LONG_ONLY"></a> VEHICLE_CMD_RESULT_COMMAND_LONG_ONLY | `uint8` | 7 | Command is only accepted when sent as a COMMAND_LONG |
| <a href="#VEHICLE_CMD_RESULT_COMMAND_INT_ONLY"></a> VEHICLE_CMD_RESULT_COMMAND_INT_ONLY | `uint8` | 8 | Command is only accepted when sent as a COMMAND_INT |
| <a href="#VEHICLE_CMD_RESULT_UNSUPPORTED_MAV_FRAME"></a> VEHICLE_CMD_RESULT_UNSUPPORTED_MAV_FRAME | `uint8` | 9 | Command does not support specified frame |
| Name | Type | Value | Description |
| ----------------------------------------------------------------------------------------------- | ------- | ----- | ---------------------------------------------------- |
| <a id="#VEHICLE_CMD_RESULT_ACCEPTED"></a> VEHICLE_CMD_RESULT_ACCEPTED | `uint8` | 0 | Command ACCEPTED and EXECUTED |
| <a id="#VEHICLE_CMD_RESULT_TEMPORARILY_REJECTED"></a> VEHICLE_CMD_RESULT_TEMPORARILY_REJECTED | `uint8` | 1 | Command TEMPORARY REJECTED/DENIED |
| <a id="#VEHICLE_CMD_RESULT_DENIED"></a> VEHICLE_CMD_RESULT_DENIED | `uint8` | 2 | Command PERMANENTLY DENIED |
| <a id="#VEHICLE_CMD_RESULT_UNSUPPORTED"></a> VEHICLE_CMD_RESULT_UNSUPPORTED | `uint8` | 3 | Command UNKNOWN/UNSUPPORTED |
| <a id="#VEHICLE_CMD_RESULT_FAILED"></a> VEHICLE_CMD_RESULT_FAILED | `uint8` | 4 | Command executed, but failed |
| <a id="#VEHICLE_CMD_RESULT_IN_PROGRESS"></a> VEHICLE_CMD_RESULT_IN_PROGRESS | `uint8` | 5 | Command being executed |
| <a id="#VEHICLE_CMD_RESULT_CANCELLED"></a> VEHICLE_CMD_RESULT_CANCELLED | `uint8` | 6 | Command Canceled |
| <a id="#VEHICLE_CMD_RESULT_COMMAND_LONG_ONLY"></a> VEHICLE_CMD_RESULT_COMMAND_LONG_ONLY | `uint8` | 7 | Command is only accepted when sent as a COMMAND_LONG |
| <a id="#VEHICLE_CMD_RESULT_COMMAND_INT_ONLY"></a> VEHICLE_CMD_RESULT_COMMAND_INT_ONLY | `uint8` | 8 | Command is only accepted when sent as a COMMAND_INT |
| <a id="#VEHICLE_CMD_RESULT_UNSUPPORTED_MAV_FRAME"></a> VEHICLE_CMD_RESULT_UNSUPPORTED_MAV_FRAME | `uint8` | 9 | Command does not support specified frame |
## Constants

Some files were not shown because too many files have changed in this diff Show More