docs(i18n): PX4 guide translations (Crowdin) - ko (#28343)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
This commit is contained in:
authored and GitHub committed 2026-08-26 17:21:38 +10:00
1 parent 227d4ab1f8
commit cdecd908b1
48 files changed
+591 -301

No files matched your search

+11 -11
View File
@@ -107,7 +107,7 @@
- [Build: Foxtech Loong 2160 VTOL](frames_vtol/vtol_quadplane_foxtech_loong_2160.md)
- [FunCub QuadPlane (픽스호크)](frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md)
- [Ranger QuadPlane (픽스호크)](frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md)
- [팔콘 Vertigo QuadPlane (Dropix)](frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md)
- [✘ Falcon Vertigo QuadPlane (Dropix)](frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md)
- [테일시터 VTOL](frames_vtol/tailsitter.md)
- [빌드: TBS Caipiroshka Tailsitter Build (Pixracer)](frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md)
- [틸트로터 VTOL](frames_vtol/tiltrotor.md)
@@ -254,10 +254,11 @@
- [Lightware SF45 Rotary Lidar](sensor/sf45_rotating_lidar.md)
- [Lightware GRF250/GRF500 Gimbal Lidar](sensor/grf_lidar.md)
- [Sony AS-DT1 LiDAR](sensor/sony_asdt1.md)
- [TeraRanger ](sensor/teraranger.md)
- [✘ TeraRanger](sensor/teraranger.md)
- [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md)
- [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md)
- [GNSS (GPS)](gps_compass/index.md)
- [u-blox Diagnostics with u-center](gps_compass/u-center.md)
- [ARK GPS (CAN)](dronecan/ark_gps.md)
- [ARK DAN GPS](gps_compass/ark_dan_gps.md)
- [ARK SAM GPS](gps_compass/ark_sam_gps.md)
@@ -268,7 +269,7 @@
- [CUAV NEO 3X GPS (CAN)](gps_compass/gps_cuav_neo_3x.md)
- [Holybro DroneCAN M8N GPS (CAN)](dronecan/holybro_m8n_gps.md)
- [LOCOSYS Hawk A1 GNSS](gps_compass/gps_locosys_hawk_a1.md)
- [Hex Here2 (Discontinued)](gps_compass/gps_hex_here2.md)
- [✘ Hex Here2](gps_compass/gps_hex_here2.md)
- [Holybro M8N & M9N GPS](gps_compass/gps_holybro_m8n_m9n.md)
- [Sky-Drones SmartAP GPS](gps_compass/gps_smartap.md)
- [RTK GNSS](gps_compass/rtk_gps.md)
@@ -288,7 +289,7 @@
- [Freefly RTK GPS](gps_compass/rtk_gps_freefly.md)
- [Holybro H-RTK ZED-F9P (DroneCAN)](dronecan/holybro_h_rtk_zed_f9p_gps.md)
- [Holybro H-RTK-F9P](gps_compass/rtk_gps_holybro_h-rtk-f9p.md)
- [Holybro H-RTK-M8P](gps_compass/rtk_gps_holybro_h-rtk-m8p.md)
- [✘ Holybro H-RTK-M8P](gps_compass/rtk_gps_holybro_h-rtk-m8p.md)
- [Holybro H-RTK Unicore UM982 GPS](gps_compass/rtk_gps_holybro_unicore_um982.md)
- [Locosys Hawk R1](gps_compass/rtk_gps_locosys_r1.md)
- [Locosys Hawk R2](gps_compass/rtk_gps_locosys_r2.md)
@@ -296,7 +297,7 @@
- [Septentrio AsteRx-m3 Pro](gps_compass/septentrio_asterx-rib.md)
- [Septentrio mosaic-go](gps_compass/septentrio_mosaic-go.md)
- [Trimble MB-Two](gps_compass/rtk_gps_trimble_mb_two.md)
- [CubePilot Here+ (Discontined)](gps_compass/rtk_gps_hex_hereplus.md)
- [✘ CubePilot Here+](gps_compass/rtk_gps_hex_hereplus.md)
- [INS (Inertial Navigation/GNSS)](sensor/inertial_navigation_systems.md)
- [InertialLabs](sensor/inertiallabs.md)
- [MicroStrain](sensor/microstrain.md)
@@ -306,7 +307,7 @@
- [ARK Flow](dronecan/ark_flow.md)
- [ARK Flow MR](dronecan/ark_flow_mr.md)
- [PMW3901](sensor/pmw3901.md)
- [PX4FLOW (Deprecated)](sensor/px4flow.md)
- [✘ PX4FLOW](sensor/px4flow.md)
- [회전계(회전 계수기)](sensor/tachometers.md)
- [ThunderFly TFRPM01 타코미터 센서](sensor/thunderfly_tachometer.md)
- [IMU Factory Calibration](advanced_config/imu_factory_calibration.md)
@@ -348,13 +349,13 @@
- [Wifi 텔레메트리](telemetry/telemetry_wifi.md)
- [ESP8266 WiFi 모듈](telemetry/esp8266_wifi_module.md)
- [ESP32 WiFi Module](telemetry/esp32_wifi_module.md)
- [3DR Telemetry Wifi (Discontinued)](telemetry/3dr_telemetry_wifi.md)
- [✘ 3DR Telemetry Wifi](telemetry/3dr_telemetry_wifi.md)
- [Microhard Serial Telemetry Radio](telemetry/microhard_serial.md)
- [ARK Electron Microhard Serial Telemetry Radio](telemetry/ark_microhard_serial.md)
- [Holybro Microhard P900 Telemetry Radio](telemetry/holybro_microhard_p900_radio.md)
- [CUAV P8 Telemetry Radio](telemetry/cuav_p8_radio.md)
- [J.Fi Wireless Telemetry Module](telemetry/jfi_telemetry.md)
- [HolyBro XBP9X - Discontinued](telemetry/holybro_xbp9x_radio.md)
- [✘ HolyBro XBP9X](telemetry/holybro_xbp9x_radio.md)
- [FrSky 텔레메트리](peripherals/frsky_telemetry.md)
@@ -382,7 +383,7 @@
- [RaccoonLab Power Modules](dronecan/raccoonlab_power.md)
- [Sky-Drones SmartAP PDB](power_module/sky-drones_smartap-pdb.md)
- [Smart/MAVLink Batteries](smart_batteries/index.md)
- [Rotoye Batmon 배터리 스마트 키트](smart_batteries/rotoye_batmon.md)
- [✘ Rotoye Batmon Battery Smartification Kit](smart_batteries/rotoye_batmon.md)
- [탑재중량과 카메라](payloads/index.md)
- [Use Cases](payloads/use_cases.md)
@@ -692,7 +693,6 @@
- [GpioOut](msg_docs/GpioOut.md)
- [GpioRequest](msg_docs/GpioRequest.md)
- [GpsDump](msg_docs/GpsDump.md)
- [GpsInjectData](msg_docs/GpsInjectData.md)
- [Gripper](msg_docs/Gripper.md)
- [HealthReport](msg_docs/HealthReport.md)
- [HeaterStatus](msg_docs/HeaterStatus.md)
@@ -807,13 +807,13 @@
- [TrajectorySetpoint6dof](msg_docs/TrajectorySetpoint6dof.md)
- [TransponderReport](msg_docs/TransponderReport.md)
- [TuneControl](msg_docs/TuneControl.md)
- [UavcanFirmwareUpdate](msg_docs/UavcanFirmwareUpdate.md)
- [UavcanParameterRequest](msg_docs/UavcanParameterRequest.md)
- [UavcanParameterValue](msg_docs/UavcanParameterValue.md)
- [UlogStream](msg_docs/UlogStream.md)
- [UlogStreamAck](msg_docs/UlogStreamAck.md)
- [VehicleAcceleration](msg_docs/VehicleAcceleration.md)
- [VehicleAirData](msg_docs/VehicleAirData.md)
- [VehicleAngularAccelerationSetpoint](msg_docs/VehicleAngularAccelerationSetpoint.md)
- [VehicleConstraints](msg_docs/VehicleConstraints.md)
- [VehicleImu](msg_docs/VehicleImu.md)
- [VehicleImuStatus](msg_docs/VehicleImuStatus.md)
@@ -51,7 +51,7 @@ The details of the [connectors](https://docs.groundcontrol.com/iot/rockblock/spe
To [switch between the two antennas modes](https://docs.groundcontrol.com/iot/rockblock/user-manual/9603-atenna-mode) the position of a small RF link cable needs to changed.
외부 안테나를 사용하는 경우 모듈 손상을 방지하기 위해 안테나의 전원을 켜기 전에 항상 안테나가 모듈에 연결되어 있는 지 확인하십시오.
모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://www.groundcontrol.com/wp-content/uploads/2022/02/IRDM_ISU_ATCommandReferenceMAN0009_Rev2.0_ATCOMM_Oct2012.pdf).
모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://docs.groundcontrol.com/iot/rockblock/user-manual/at-commands).
1. Connect to the module with using a 19200/8-N-1 setting and check if the communication is working using the command: `AT`.
The response should be: `OK`.
+1 -1
View File
@@ -627,7 +627,7 @@ div.frame_variant td, div.frame_variant th {
<td>유지보수: John Doe &lt;john@example.com&gt;<p><code>SYS_AUTOSTART</code> = 51000</p></td>
</tr>
<tr id="rover_rover_axial_scx10_2_trail_honcho">
<td><a href="https://www.axialadventure.com/product/1-10-scx10-ii-trail-honcho-4wd-rock-crawler-brushed-rtr/AXID9059.html">Axial SCX10 2 Trail Honcho</a></td>
<td><a href="https://www.axialadventure.com/product/axial-1-10-scx10-ii-trail-honcho-4wd-rock-crawler-brushed-rtr/AXID9059.html">Axial SCX10 2 Trail Honcho</a></td>
<td>유지보수: John Doe &lt;john@example.com&gt;<p><code>SYS_AUTOSTART</code> = 51001</p></td>
</tr>
<tr id="rover_rover_nxp_b3rb_rover_ackermann">
+4 -4
View File
@@ -13,7 +13,7 @@ This quick start guide shows how to power the _Cube_<sup>&reg;</sup> flight cont
:::tip
The instructions apply to all Cube variants, including [Cube Black](../flight_controller/pixhawk-2.md), [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md) and [Cube Orange](../flight_controller/cubepilot_cube_orange.md).
Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube) (Cube Docs).
Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/autopilot/the-cube) (Cube Docs).
:::
## 소품
@@ -195,7 +195,7 @@ If connecting peripherals to the port labeled `GPS2`, assign the PX4 [serial por
## 설정
Configuration is performed using [QGroundContro](https://qgroundcontrol.com/).
Configuration is performed using [QGroundControl](https://qgroundcontrol.com/).
After downloading, installing and running _QGroundControl_, connect the board to your computer as shown.
@@ -220,5 +220,5 @@ PX4 펌웨어를 플래시한 후 [Program PX4IO(../getting_started/tunes.md#pro
- [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md)
- [Cube Orange](../flight_controller/cubepilot_cube_orange.md)
- Cube 문서 (제조사) :
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
- [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board)
+37 -13
View File
@@ -1,6 +1,6 @@
# Advanced TECS Tuning (Weight and Altitude)
This topic shows how you can compensate for changes to the [weight of the vehicle](#vehicle-weight-compensation) and the [air density](#air-density-compensation), along with information about the [algorithms](#weight-and-density-compensation-algorithms) that are used.
This topic shows how you can compensate for changes to the [mass of the vehicle](#vehicle-weight-compensation) and the [air density](#air-density-compensation), along with information about the [algorithms](#weight-and-density-compensation-algorithms) that are used.
:::warning
This topic requires that you have already performed [basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed).
@@ -9,25 +9,49 @@ This topic requires that you have already performed [basic TECS tuning](../confi
[Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) established the key performance limitations of the vehicle that are required for the altitude and airspeed controller to function properly.
While those limitations are specified using constant parameters, in reality vehicle performance is not constant and is affected by various factors.
If changes in weight and air density are not taken into account, altitude and airspeed tracking will likely deteriorate in the case where the configuration (air density and weight) deviate significantly from the configuration at which the vehicle was tuned.
If changes in vehicle mass and air density are not taken into account, altitude and airspeed tracking will likely deteriorate in the case where the configuration (air density and mass) deviate significantly from the configuration at which the vehicle was tuned.
## Vehicle Weight Compensation
Set (both) the following parameters to scale the maximum climb rate, minimum sink rate, and adjust airspeed limits for weight:
Set (both) the following parameters to scale the maximum climb rate, minimum sink rate, and adjust airspeed limits for the vehicle mass:
- [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the weight of the vehicle at which the [Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) was performed.
- [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the actual weight of the vehicle at any given time, for example when using a larger battery, or with a payload that was not present during tuning.
- [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the mass of the vehicle at which the [Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) was performed.
- [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_GROSS) — the actual mass of the vehicle at any given time, for example when using a larger battery, or with a payload that was not present during tuning.
You can determine the values by measuring the weight of the vehicle using a scale in the tuning configuration and when flying with a payload.
You can determine the values by measuring the mass of the vehicle using a scale in the tuning configuration and when flying with a payload.
:::info
The `WEIGHT_*` parameters are masses in kilograms; the parameter names and the derived _weight ratio_ (the ratio of the current vehicle mass to `WEIGHT_BASE`) use "weight" following common aviation usage.
:::
Scaling is performed when _both_ `WEIGHT_BASE` and `WEIGHT_GROSS` are greater than `0`, and will have no effect if the values are the same.
See the [algorithms](#weight-and-density-compensation-algorithms) section below for more information.
### Fuel Burn Compensation
On combustion-engine vehicles a significant proportion of the takeoff mass is fuel, so the vehicle mass decreases considerably over the course of a flight.
If a fuel tank sensor is present (publishing to the [FuelTankStatus](../msg_docs/FuelTankStatus.md) message, for example from a [DroneCAN](../dronecan/index.md) engine ECU), PX4 can continuously estimate the current vehicle mass from the amount of burned fuel.
To enable this, additionally set:
- [WEIGHT_FUEL](../advanced_config/parameter_reference.md#WEIGHT_FUEL) — the mass of a full fuel load (tank capacity multiplied by fuel density).
When `WEIGHT_FUEL` is greater than `0`, `WEIGHT_GROSS` must be set to the takeoff mass with a _full_ tank.
The current mass is then computed from the measured fraction of fuel remaining, so no parameter update is needed when taking off with a partially filled tank.
The measured fuel level is low-pass filtered to reject fuel slosh.
If no fuel data is available (no sensor, or the sensor fails before boot), any mass-based scaling makes the conservative assumption that the vehicle is at the full gross mass (including fuel).
If fuel data is lost mid-flight, the last known fuel state is kept.
Fuel-consumption compensation is only applied to the fuel tank with id `0` (the default id for single-tank systems).
Multi-tank vehicles should publish the aggregated total fuel state as tank `0`.
A warning is shown if fuel data is not received from id `0` but is received for other tank ids.
## Air Density Compensation
### Specify a Service Ceiling
In PX4 the service ceiling [FW_SERVICE_CEIL](../advanced_config/parameter_reference.md#FW_SERVICE_CEIL) specifies the altitude in standard atmospheric conditions at which the vehicle is still able to achieve a maximum climb rate of 0.5 m/s at maximum throttle and weight equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE).
In PX4 the service ceiling [FW_SERVICE_CEIL](../advanced_config/parameter_reference.md#FW_SERVICE_CEIL) specifies the altitude in standard atmospheric conditions at which the vehicle is still able to achieve a maximum climb rate of 0.5 m/s at maximum throttle and a vehicle mass equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE).
By default this parameter is disabled and no compensation will take place.
This parameter needs to be determined experimentally.
@@ -61,11 +85,11 @@ This is provided for interest only, and may be of interest to developers who wan
### 표기법
In the following sections we will use the notation $\hat X$ to specify that this value is a calibrated value of the variable $X$.
By calibrated we mean the value of that variable measured at sea level in standard atmospheric conditions, and when vehicle weight was equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE).
By calibrated we mean the value of that variable measured at sea level in standard atmospheric conditions, and when the vehicle mass was equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE).
예: by $\hat{\dot{h}}_{\text{max}}$ we specify the maximum climb rate the vehicle can achieve at [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) at sea level in standard atmospheric conditions.
### Effect of Weight on Maximum Climb Rate
### Effect of Mass on Maximum Climb Rate
The maximum climb rate ([FW_T_CLMB_MAX](../advanced_config/parameter_reference.md#FW_T_CLMB_MAX)) is scaled as a function of the weight ratio.
@@ -76,7 +100,7 @@ $$\dot{h}_{\text{max}} = \frac{V \cdot (\text{Thrust} - \text{Drag})}{m \cdot g}
where `V` is the true airspeed and `m` is the vehicle mass.
From this equation we see that the maximum climb rates scales with vehicle mass.
### Effect of Weight on Minimum Sink Rate
### Effect of Mass on Minimum Sink Rate
The minimum sink rate ([FW_T_SINK_MIN](../advanced_config/parameter_reference.md#FW_T_SINK_MIN)) is scaled as a function of weight ratio
@@ -88,7 +112,7 @@ where $\rho$ is the air density, S is the wing surface reference area and $f(C_L
From this equation we see that the minimum sink rate scales with the square root of the weight ratio.
### Effect of Weight on Airspeed Limits
### Effect of Mass on Airspeed Limits
The minimum airspeed ([FW_AIRSPD_MIN](../advanced_config/parameter_reference.md#FW_AIRSPD_MIN)), the stall airspeed ([FW_AIRSPD_STALL](../advanced_config/parameter_reference.md#FW_AIRSPD_STALL)) and trim airspeed ([FW_AIRSPD_TRIM](../advanced_config/parameter_reference.md#FW_AIRSPD_TRIM)) are adjusted based on the weight ratio specified by [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) and [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_GROSS).
@@ -100,12 +124,12 @@ rearranging this equation for airspeed gives:
$$V = \sqrt{\frac{2mg}{\rho S C_L}}$$
From this equation we see that if we assume a constant angle of attack (which we generally desire), the vehicle weight affects airspeed with a square root relation.
From this equation we see that if we assume a constant angle of attack (which we generally desire), the vehicle mass affects airspeed with a square root relation.
Therefore, the airspeed limits mentioned above are all scaled using the square root of the weight ratio.
### Effect of Bank Angle on Airspeed Limits
Flying a coordinated, level turn at bank angle $\phi$ increases the load factor by $\frac{1}{\cos{\phi}}$. This is similar to the added load factor due to weight (section above), and thus the stall and minimum airspeeds are increased by an additional factor of $\sqrt{\frac{1}{\cos{\phi}}}$.
Flying a coordinated, level turn at bank angle $\phi$ increases the load factor by $\frac{1}{\cos{\phi}}$. This is similar to the added load factor due to increased mass (section above), and thus the stall and minimum airspeeds are increased by an additional factor of $\sqrt{\frac{1}{\cos{\phi}}}$.
The maximum airspeed ([FW_AIRSPD_MAX](../advanced_config/parameter_reference.md#FW_AIRSPD_MAX)) is _not_ compensated in this way, as it can represent structural limits of the airframe.
+5
View File
@@ -142,6 +142,11 @@ Tuning is the final step, carried out only after most other setup and configurat
- [Multicopter Racer Setup](../config_mc/racer_setup.md)
- [Genius Tools](https://www.altitude-rd.com/genius-tools) — a commercial web app for interactive multicopter tuning from a flight log.
Bugs and questions should be addressed to the maintainer: [Altitude R&D](https://www.altitude-rd.com/home) (not the PX4 forums).
![Genius Tools](../../assets/config/mc/genius_tools.webp)
<!--
- Explain what you have to tune on PX4, what you can tune, and what each topic covers
- I expect we should start with an exhaustive list of the tuning you could want to do - such as position tuning, etc. Do we have one?
+2 -2
View File
@@ -11,7 +11,7 @@ PX4 프로젝트는 3가지 Git 분기 모델을 사용합니다.
We try to retain a [linear history through rebases](https://www.atlassian.com/git/tutorials/rewriting-history) and avoid the [Github flow](https://docs.github.com/en/get-started/using-github/github-flow).
그러나, 전세계의 역동적인 개발팀과 수시로 병합 작업을 진행합니다.
To contribute new functionality, [sign up for Github](https://docs.github.com/en/get-started/using-github/github-flow), then [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) the repository, [create a new branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository), add your [changes as commits](#commits-and-commit-messages), and finally [send a pull request](#pull-requests).
To contribute new functionality, [sign up for Github](https://docs.github.com/en/get-started/using-github/github-flow), then [fork](https://docs.github.com/en/pull-requests/how-tos/work-with-forks/fork-a-repo) the repository, [create a new branch](https://docs.github.com/en/pull-requests/how-tos/commit-changes/managing-branches-within-your-repository), add your [changes as commits](#commits-and-commit-messages), and finally [send a pull request](#pull-requests).
Changes will be merged when they pass our [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) tests.
All code contributions have to be under the permissive [BSD 3-clause license](https://opensource.org/license/BSD-3-Clause) and all code must not impose any further constraints on the use.
@@ -183,7 +183,7 @@ The body of the message can contain several paragraphs. Describe in detail what
## Pull Requests
Github [Pull Requests (PRs)](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) are the primary mechanism used to submit new functionality and bug fixes to PX4.
Github [Pull Requests (PRs)](https://docs.github.com/en/pull-requests/reference/pull-requests) are the primary mechanism used to submit new functionality and bug fixes to PX4.
They include the new set of [commits](#commits-and-commit-messages) in your branch (relative the main branch), and a description of the changes.
+1 -1
View File
@@ -60,7 +60,7 @@ If you already have a clone of the [PX4-Autopilot](https://github.com/PX4/PX4-Au
2. [Sign up](https://github.com/signup) for Github if you haven't already
3. Create a copy (Fork) of the [PX4-Autopilot repo](https://github.com/PX4/PX4-Autopilot) on Github ([instructions here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)).
3. Create a copy (Fork) of the [PX4-Autopilot repo](https://github.com/PX4/PX4-Autopilot) on Github ([instructions here](https://docs.github.com/en/pull-requests/how-tos/work-with-forks/fork-a-repo)).
4. 복사된 저장소를 로컬 컴퓨터에 복제합니다.
+2 -2
View File
@@ -8,7 +8,7 @@ PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4
- [Sign up](https://github.com/signup) for github if you haven't already
- Fork the PX4-Autopilot repo (see [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo))
- Fork the PX4-Autopilot repo (see [here](https://docs.github.com/en/pull-requests/how-tos/work-with-forks/fork-a-repo))
- 포크된 저장소를 로컬 컴퓨터에 복제합니다.
@@ -292,7 +292,7 @@ If a conflict occurs during a `git rebase`, please refer to [this guide](https:/
### 풀 병합 충돌
If a conflict occurs during a `git pull`, please refer to [this guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line#competing-line-change-merge-conflicts).
If a conflict occurs during a `git pull`, please refer to [this guide](https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/resolving-a-merge-conflict-using-the-command-line#competing-line-change-merge-conflicts).
### 오래된 git 태그로 인한 빌드 오류
+57 -8
View File
@@ -1,11 +1,53 @@
# 시스템 장애 주입
System failure injection allows you to induce different types of sensor and system failures, either programmatically using the [MAVSDK failure plugin](https://mavsdk.mavlink.io/main/en/cpp/api_reference/classmavsdk_1_1_failure.html), or "manually" via a PX4 console like the [MAVLink shell](../debug/mavlink_shell.md#mavlink-shell).
System failure injection allows you to induce different types of sensor and system failures, either via MAVLink (using [MAV_CMD_INJECT_FAILURE](https://mavlink.io/en/messages/common.html#MAV_CMD_INJECT_FAILURE) or via the [MAVSDK failure plugin](https://mavsdk.mavlink.io/main/en/cpp/api_reference/classmavsdk_1_1_failure.html)), or "manually" via a PX4 console like the [MAVLink shell](../debug/mavlink_shell.md#mavlink-shell).
This enables easier testing of [safety failsafe](../config/safety.md) behaviour, and more generally, of how PX4 behaves when systems and sensors stop working correctly.
Failure injection is disabled by default, and can be enabled using the [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN) parameter.
Failures can be injected both in simulation and on real hardware. In simulation the available failures depend on the simulator. On hardware the `off` (stop publishing) and `stuck` (freeze the last value) types are supported for the `gyro`, `accel`, `mag`, `baro`, `distance_sensor` and `gps` components; this requires firmware built with the failure-injection module. In addition, the `battery` component supports `off` (report a depleted pack, triggering the battery failsafe), and the `gps` component supports `wrong` (report the fix type selected by [SYS_FAIL_GPS_WRG](../advanced_config/parameter_reference.md#SYS_FAIL_GPS_WRG), leaving the reported position untouched).
Failures can be injected both in simulation and on real hardware; this requires firmware built with the failure-injection module.
The command always goes through the same firmware failure-injection module — whether it arrives over MAVLink or from the console, the accepted combinations are identical.
What differs is whether a _consumer_ applies the failure, and that depends on the environment.
## Supported Failure Types
The table lists the failure types that actually take effect per environment: `off`, `stuck`, `wrong` (`ok` is not listed, but clears an active injection on all environments).
A `—` means the module still accepts the command, but no consumer applies it in that environment.
| Component | [Gazebo] (gz) | [SIH] | `simulator_mavlink` (Gazebo Classic/JMAVSim) | 하드웨어 |
| ----------------- | ----------------------- | ----------------------- | --------------------------------------------------------------- | ----------------------- |
| `gyro` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` |
| `accel` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` |
| `mag` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` |
| `baro` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` |
| `distance_sensor` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` | `off`, `stuck` |
| `gps` | — | `off`, `stuck`, `wrong` | `off`, `stuck`, `wrong` | `off`, `stuck`, `wrong` |
| `airspeed` | `off`, `stuck`, `wrong` | — | `off`, `wrong` | — |
| `vio` | — | — | `off` | — |
| `battery` | `off`, `wrong` | `off`, `wrong` | `off`, `wrong` | `off`, `wrong` |
| `traffic` | `off` | `off` | `off` | `off` |
| `motor` | `off` | `off` | `off` | `off` |
| `esc` | `off`, `wrong` | `off`, `wrong` | `off`, `wrong` | `off`, `wrong` |
[SIH]: ../sim_sih/index.md
[Gazebo]: ../sim_gazebo_gz/index.md
::: info
- `gps off | stuck | wrong` on Gazebo (Gz): only available if [SIM_GZ_EN_GPS](../advanced_config/parameter_reference.md#SIM_GZ_EN_GPS) is set to `0` to use the injectable simulated-GPS module.
By default Gazebo publishes GPS from the simulator's own GNSS sensor (`SIM_GZ_EN_GPS` = 1), which is not injectable.
- `airspeed off | stuck | wrong` on Gazebo (Gz): only injectable when airspeed is provided by the simulated-airspeed module ([SENS_EN_ARSPDSIM](../advanced_config/parameter_reference.md#SENS_EN_ARSPDSIM)); worlds that model an airspeed sensor directly are not injected.
- `battery wrong` reports the remaining charge just below the [SYS_FAIL_BAT_LVL](../advanced_config/parameter_reference.md#SYS_FAIL_BAT_LVL) warning threshold to trigger the battery failsafe; `off` stops publishing the battery status entirely.
- `traffic off` suppresses incoming reports and marks the ADS-B/FLARM link unhealthy.
- `motor off` also requires [CA_FAILURE_MODE](../advanced_config/parameter_reference.md#CA_FAILURE_MODE).
- `esc off` reports the addressed ESC as offline and blanks its telemetry; `esc wrong` keeps it online but reports implausible telemetry (voltage and current at 10% of the real value, RPM 10x). ESCs are addressed by motor instance (the ESC's actuator function), so `-i 1` targets the ESC driving motor 1.
- On hardware, ESC injection is applied only by the UAVCAN (DroneCAN) ESC driver; the other ESC drivers (DShot, Cyphal, VOXL, TAP ESC) publish their telemetry unmodified.
:::
Sensors delivered through the shared driver layer (IMU, magnetometer, barometer, rangefinder via the `PX4*` sensor wrappers) support `off`/`stuck` in every environment that uses that layer — including the Gazebo and SIH sensor simulators, which feed synthesized measurements through the same wrappers.
The remaining gaps are backend-specific: GPS and airspeed are handled by dedicated simulator code (see the GPS and airspeed notes in the info box above), SIH does not simulate an injectable airspeed.
Components not listed (`optical_flow`, `servo`, `avoidance`, `rc_signal`, `mavlink_signal`) are rejected everywhere (`MAV_RESULT_UNSUPPORTED`); see the note below on NACK behaviour.
:::info
PX4 may accept a command to set a particular failure mode even it that mode is not supported by your simulator.
@@ -43,8 +85,10 @@ failure <component> <failure_type> [-i <instance_number>] [-m <instance_bitmask>
- 시스템:
- `battery`: Battery
- `motor`: Motor
- `esc`: ESC telemetry
- `servo`: Servo
- `avoidance`: Avoidance
- `avoidance`: Obstacle/collision avoidance system
- `traffic`: Traffic avoidance (ADS-B/transponder)
- `rc_signal`: RC Signal
- `mavlink_signal`: MAVLink data telemetry connection
- _failure_type_:
@@ -58,11 +102,12 @@ failure <component> <failure_type> [-i <instance_number>] [-m <instance_bitmask>
- `intermittent`: Publish intermittently
- _instance number_ (optional): Instance number of affected sensor.
0 (기본값) 지정된 유형의 모든 센서를 나타냅니다.
- _instance bitmask_ (optional): address several instances at once (bit 0 = first instance, bit 1 = second, …; decimal or `0x` hex). Used only when `-i` is omitted. Example: `-m 0x5` targets instances 1 and 3.
- _instance bitmask_ (optional): address several instances at once (bit 0 = first instance, bit 1 = second, …; decimal or `0x` hex). Used only when `-i` is omitted.
Example: `-m 0x5` targets instances 1 and 3.
:::info
GPS implements only the `off`, `stuck`, and `wrong` failure modes; the other failure types have no effect on it.
`gps wrong` makes the addressed receiver report the fix type selected by [SYS_FAIL_GPS_WRG](../advanced_config/parameter_reference.md#SYS_FAIL_GPS_WRG) and leaves the reported position untouched.
`gps wrong` makes the addressed receiver report the fix type selected by [SYS_FAIL_GPS_WRG](../advanced_config/parameter_reference.md#SYS_FAIL_GPS_WRG) and the jamming state selected by [SYS_FAIL_GPS_JAM](../advanced_config/parameter_reference.md#SYS_FAIL_GPS_JAM) (`Unchanged` keeps the receiver's own state), and leaves the reported position untouched.
:::
## RC Switch Trigger
@@ -72,7 +117,7 @@ A failure can also be injected from an RC switch, without a console or telemetry
- [SYS_FAIL_RC_SRC](../advanced_config/parameter_reference.md#SYS_FAIL_RC_SRC): the auxiliary RC input that triggers the failure — `0` disables it, `1`–`6` select AUX1–AUX6 (mapped via `RC_MAP_AUXn`).
- [SYS_FAIL_RC_UNIT](../advanced_config/parameter_reference.md#SYS_FAIL_RC_UNIT): the affected component (the `FAILURE_UNIT` value; e.g. `101` = motor).
- [SYS_FAIL_RC_MODE](../advanced_config/parameter_reference.md#SYS_FAIL_RC_MODE): the failure type (the `FAILURE_TYPE` value; e.g. `1` = off).
- [SYS_FAIL_RC_INST](../advanced_config/parameter_reference.md#SYS_FAIL_RC_INST): the affected instance (1-based; `0` = all instances).
- [SYS_FAIL_RC_INST](../advanced_config/parameter_reference.md#SYS_FAIL_RC_INST): the affected instances, as a bitmask (bit 0 = instance 1, e.g. `5` = instances 1 and 3; `0` = all instances).
While the selected aux switch is on the configured failure is injected; switching it back off clears the failure. The injection goes through the same path as the console/MAVLink commands, so for a motor it stops the motor exactly as `failure motor off` does (which also requires [CA_FAILURE_MODE](../advanced_config/parameter_reference.md#CA_FAILURE_MODE)).
@@ -119,10 +164,14 @@ To stop a motor mid-flight without the system anticipating it or excluding it fr
To trigger the battery failsafe by reporting a depleted pack:
1. Enable the [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN) parameter.
2. Enter the following commands on the MAVLink console or SITL _pxh shell_:
2. Optionally select the injected warning level with [SYS_FAIL_BAT_LVL](../advanced_config/parameter_reference.md#SYS_FAIL_BAT_LVL): Warn, Critical or Emergency. The reported remaining charge is set just below the matching threshold ([BAT_LOW_THR](../advanced_config/parameter_reference.md#BAT_LOW_THR), [BAT_CRIT_THR](../advanced_config/parameter_reference.md#BAT_CRIT_THR) or [BAT_EMERGEN_THR](../advanced_config/parameter_reference.md#BAT_EMERGEN_THR)).
3. Enter the following commands on the MAVLink console or SITL _pxh shell_:
```sh
# Report the battery as depleted (warning EMERGENCY) -> battery failsafe
# Report the battery as depleted at the SYS_FAIL_BAT_LVL warning level -> battery failsafe
failure battery wrong
# Stop publishing the battery status entirely
failure battery off
# Stop injecting the failure
+1 -1
View File
@@ -13,7 +13,7 @@ The video below demonstrates this for a simulated vehicle — the approach works
Follow the [ROS 2 Installation & Setup](../ros2/user_guide.md#installation-setup) instructions in the _ROS2 user guide_ to install:
- ROS 2
- [Micro XRCE-DDS Agent](../ros2/user_guide.md#setup-micro-xrce-dds-agent-client)
- [Micro XRCE-DDS Agent](../ros2/user_guide.md#setup-the-agent)
- [PX4/px4_msgs](https://github.com/PX4/px4_msgs): PX4/ROS2 shared message definitions.
- PX4 source code and build the simulator.
+3 -3
View File
@@ -220,6 +220,6 @@ This reduces the risk or poor wiring contributing to debugging problems, and has
<!-- Reference links used above -->
[swd]: https://developer.arm.com/documentation/ihi0031/a/The-Serial-Wire-Debug-Port--SW-DP-
[itm]: https://developer.arm.com/documentation/ddi0403/d/Appendices/Debug-ITM-and-DWT-Packet-Protocol?lang=en
[etm]: https://developer.arm.com/documentation/ihi0064/latest/
[swd]: https://support.arm.com/documentation/ihi0031/a/The-Serial-Wire-Debug-Port--SW-DP-
[itm]: https://support.arm.com/documentation/ddi0403/d/Appendices/Debug-ITM-and-DWT-Packet-Protocol?lang=en
[etm]: https://support.arm.com/documentation/ihi0064/latest/
+26 -6
View File
@@ -31,6 +31,12 @@ The latest OS images at time of updating this document is [AM3358 Debian 10.3 20
## 크로스 컴파일러 빌드 (권장)
:::warning
The Linaro toolchain previously recommended has been discontinued.
The instructions below have been updated to use its replacement (the Arm GNU Toolchain) but the changes **have not been tested**.
Please add a PR to either remove this comment or fix the instructions if you try them!
:::
The recommended way to build PX4 for _BeagleBone Blue_ is to compile on a development computer and upload the PX4 executable binary directly to the BeagleBone Blue.
:::tip
@@ -114,7 +120,7 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
cd /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf
```
The ARM Cross Compiler for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/#gnu_and_llvm).
The ARM Cross Compiler for _BeagleBone Blue_ can be found at the [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads) site (the official successor to the Linaro toolchain releases previously used here).
::: tip
GCC in the toolchain should be compatible with kernel in _BeagleBone Blue_.
@@ -122,13 +128,13 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
:::
Download and unpack [gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz](https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder.
Download and unpack [arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz](https://developer.arm.com/-/media/Files/downloads/gnu/15.2.rel1/binrel/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder.
Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/).
Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at the [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads) site.
```sh
wget https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz
tar -xf gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz
wget https://developer.arm.com/-/media/Files/downloads/gnu/15.2.rel1/binrel/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
tar -xf arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz
```
::: tip
@@ -138,10 +144,24 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
As a general rule of thumb is to choose a toolchain where the version of GCC is not higher than the version of GCC which comes with the OS image on _BeagleBone Blue_.
::: warning
PX4's build for this board looks specifically for compiler binaries named `arm-linux-gnueabihf-*` (the naming used by the old Linaro toolchain), but the Arm GNU Toolchain ships them as `arm-none-linux-gnueabihf-*`.
Create matching symlinks so the build can find them:
```sh
cd /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf/bin
for f in arm-none-linux-gnueabihf-*; do
ln -s "$f" "${f/arm-none-linux-gnueabihf/arm-linux-gnueabihf}"
done
```
:::
2. Add it to the PATH in ~/.profile as shown below
```sh
export PATH=$PATH:/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf/bin
export PATH=$PATH:/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf/bin
```
::: info
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
Contact the [manufacturer](https://cubepilot.org/#/home) for hardware support or compliance issues.
:::
The [Cube Orange](https://www.cubepilot.com/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems.
The [Cube Orange](https://cubepilot.org/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems.
![Cube Orange](../../assets/flight_controller/cube/orange/cube_orange_hero.jpg)
@@ -19,7 +19,7 @@ This is automatically configured and enabled in the default PX4 firmware.
Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다.
:::tip
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications).
:::
:::info
@@ -42,7 +42,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
## Where to Buy {#store}
- [Reseller list](https://www.cubepilot.com/#/reseller/list)
- [Reseller list](https://cubepilot.org/#/reseller/list)
## 조립
@@ -246,5 +246,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
- Cube 문서 (제조사) :
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
- [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board)
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
Contact the [manufacturer](https://cubepilot.org/#/home) for hardware support or compliance issues.
:::
The [Cube Orange+](https://www.cubepilot.com/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems.
The [Cube Orange+](https://cubepilot.org/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems.
Cube Orange+ is similar to Cube Orange, but has a more powerful dual-core processor (STM32H757), and some different sensor parts.
![Cube Orange](../../assets/flight_controller/cube/orangeplus/cubepilot_cube_orangeplus_standard_set.jpg)
@@ -20,7 +20,7 @@ This is automatically configured and enabled in the default PX4 firmware.
Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다.
:::tip
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications).
:::
:::info
@@ -43,7 +43,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
## Where to Buy {#store}
- [Reseller list](https://www.cubepilot.com/#/reseller/list)
- [Reseller list](https://cubepilot.org/#/reseller/list)
## 조립
@@ -251,5 +251,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
- Cube 문서 (제조사) :
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
- [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board)
@@ -15,7 +15,7 @@ For example, a carrier board for a commercial inspection vehicle might include c
Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다.
:::tip
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications).
:::
:::info
@@ -38,7 +38,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
## Where to Buy {#store}
- [Reseller list](https://www.cubepilot.com/#/reseller/list)
- [Reseller list](https://cubepilot.org/#/reseller/list)
## 조립
@@ -144,5 +144,5 @@ Cube의 CAN1과 CAN2의 실크 스크린이 뒤집힙니다. CAN1은 CAN2이고
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
- Cube 문서 (제조사) :
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
- [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board)
+5 -5
View File
@@ -11,7 +11,7 @@ We recommend however to consider products built on industry standards, such as t
이 비행 컨트롤러는 표준을 따르지 않으며, 특허받은 커넥터를 사용합니다.
:::
The [Hex Cube Black](https://docs.cubepilot.org/user-guides/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
The [Hex Cube Black](https://docs.cubepilot.org/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
It is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv3** open hardware design and runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.
![Cube Black](../../assets/flight_controller/cube/cube_black_hero.png)
@@ -23,7 +23,7 @@ while a carrier board for a racer could includes ESCs form the frame of the vehi
Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다.
:::info
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications).
:::
:::tip
@@ -49,7 +49,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
## Where to Buy {#store}
[Cube Black](https://www.cubepilot.com/#/reseller/list) (Reseller list)
[Cube Black](https://cubepilot.org/#/reseller/list) (Reseller list)
## 조립
@@ -165,5 +165,5 @@ Cube Black의 CAN1과 CAN2의 실크 스크린이 뒤집힙니다 (CAN1은 CAN2
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
- Cube 문서 (제조사) :
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
- [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube)
- [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board)
+8 -8
View File
@@ -52,13 +52,13 @@ At high level these are:
- [Mission path return](#rtl_type_2) (`RTL_TYPE=2`): Use mission path and fast-continue to mission landing (if defined).
If no mission _landing_ defined, fast-reverse mission to home.
If no _mission_ defined, return direct to home (rally points are ignored).
- [Closest safe destination return](#closest-safe-destination-return-type-rtl-type-3) (`RTL_TYPE=3`): Ascend to a safe altitude and return via direct path to closest destination: home, start of mission landing pattern, or rally point.
- [Closest safe destination return](#rtl_type_3) (`RTL_TYPE=3`): Ascend to a safe altitude and return via direct path to closest destination: home, start of mission landing pattern, or rally point.
목적지가 임무 착륙 패턴인 경우 패턴을 따라 착륙합니다.
- [Closest mission landing or reverse mission return](#closest-mission-landing-or-reverse-mission-return-type-rtl-type-4) (`RTL_TYPE=4`): Like `RTL_TYPE=2`, but chooses between mission landing and reverse mission path based on which requires fewer waypoints to traverse.
- [Closest mission landing or reverse mission return](#rtl_type_4) (`RTL_TYPE=4`): Like `RTL_TYPE=2`, but chooses between mission landing and reverse mission path based on which requires fewer waypoints to traverse.
Rally points are not considered.
- [Rally point return](#rally-point-return-type-rtl-type-5) (`RTL_TYPE=5`): Return directly to the closest rally point, ignoring home and mission landing.
- [Rally point return](#rtl_type_5) (`RTL_TYPE=5`): Return directly to the closest rally point, ignoring home and mission landing.
If no rally point is defined, land at the current position.
- [Battery-aware home priority return](#battery-aware-home-priority-return-type-rtl-type-6) (`RTL_TYPE=6`): Return to home if the estimated flight time is within the remaining battery time, otherwise return to the closest rally point.
- [Battery-aware home priority return](#rtl_type_6) (`RTL_TYPE=6`): Return to home if the estimated flight time is within the remaining battery time, otherwise return to the closest rally point.
Falls back to the closest safe point (home or rally) if the remaining battery time is unknown/unavailable.
각 유형에 대한 자세한 설명은 다음 섹션에서 제공됩니다.
@@ -164,7 +164,7 @@ In this return type, the vehicle:
By default an MC or VTOL in MC mode will land, and a fixed-wing vehicle circles at the descent altitude.
A VTOL in FW mode aligns its heading to the destination point, transitions to MC mode, and then lands.
### Closest of Mission Landing or Reverse Mission Return Type (RTL_TYPE=4)
### Closest of Mission Landing or Reverse Mission Return Type (RTL_TYPE=4) {#rtl_type_4}
This return type is similar to [Mission Path Return (RTL_TYPE=2)](#mission-path-return-type-rtl-type-2), but selects between the forward mission landing and the reverse mission path based on
which requires fewer waypoints to traverse from the current position (instead of always preferring the forward mission landing).
@@ -178,7 +178,7 @@ In this return type, the vehicle:
- Rally points are not considered.
- Landing behaviour at the destination follows the same rules as RTL_TYPE=2.
### Rally Point Return Type (RTL_TYPE=5)
### Rally Point Return Type (RTL_TYPE=5) {#rtl_type_5}
In this return type, the vehicle ignores home and mission landing patterns entirely and returns only to rally points:
@@ -191,7 +191,7 @@ If no rally points are defined the vehicle will land at its current position ins
This type is intended for use cases where only pre-approved rally points are acceptable landing destinations.
:::
### Battery-Aware Home Priority Return Type (RTL_TYPE=6)
### Battery-Aware Home Priority Return Type (RTL_TYPE=6) {#rtl_type_6}
In this return type, the vehicle uses the estimated flight time to home compared against the remaining battery time to decide the return destination.
@@ -207,7 +207,7 @@ The vehicle:
## Geofence Awareness {#geofence_awareness}
<Badge type="tip" text="main (PX4 v1.19)" />
<Badge type="tip" text="main (PX4 v1.20)" />
For most of the return types (including the default home/rally point return type) the return path is chosen to avoid breaching any geofence.
Planning is purely horizontal: the altitude profile is unaffected, and only the lateral path is adjusted to avoid the fence.
+1 -1
View File
@@ -58,7 +58,7 @@ Key build features
- [Caddx Vista FPV air unit](https://www.caddxfpv.com/collections/vista-kit)
- [Emax ES08MA ii](https://emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo)
- [Emax ES08MA ii](https://shop.emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo)
- [DJI FPV Goggles](https://www.dji.com/fpv)
+4 -4
View File
@@ -1,7 +1,7 @@
# HEX/ProfiCNC Here2 GPS (Discontinued)
:::warning
This has been superseded by the [Cube Here 3](https://www.cubepilot.com/#/here/here3)
This has been superseded by the [Cube Here 3](https://cubepilot.org/#/here/here3)
:::
The _Here2 GPS receiver_ is an update to the Here GPS module from HEX.
@@ -18,7 +18,7 @@ The _Here2 GPS receiver_ is an update to the Here GPS module from HEX.
## 구매처
- [Resellers](https://www.cubepilot.com/#/reseller/list)
- [Resellers](https://cubepilot.org/#/reseller/list)
## 설정
@@ -26,8 +26,8 @@ PX4의 설정과 사용법은 대부분 플러그앤플레이입니다.
::: info
- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/user-guides/here-2/updating-here-2-firmware).
- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/user-guides/here-2/here-2-can-mode-instruction).
- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/here-2/updating-here-2-firmware).
- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/here-2/here-2-can-mode-instruction).
:::
+1
View File
@@ -215,5 +215,6 @@ This behavior prevents large position errors that could occur when the yaw refer
- [GPS driver](../modules/modules_driver.md#gps)
- [PPS driver](../modules/modules_driver.md#pps-capture)
- [DroneCAN Example](../dronecan/index.md)
- [u-blox Diagnostics with u-center](../gps_compass/u-center.md)
- 나침반
- [Driver source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/magnetometer) (Compasses)
+1
View File
@@ -235,4 +235,5 @@ See the [Using PX4's Navigation Filter (EKF2) > GPS](../advanced_config/tuning_t
## 추가 정보
- [RTK-GPS (PX4-Integration)](../advanced/rtk_gps.md): Developer information about integrating RTK-GPS support into PX4.
- [u-blox Diagnostics with u-center](../gps_compass/u-center.md): bench-check RTCM reception and fix status on a u-blox rover/base.
- [Real Time Kinematic](https://en.wikipedia.org/wiki/Real_Time_Kinematic) (Wikipedia)
@@ -58,4 +58,5 @@ If using RTK with a fixed base station the secondary GPS will show the RTK state
## 추가 정보
- [ZED-F9P Moving base applications (Application note)](https://content.u-blox.com/sites/default/files/documents/ZED-F9P-MovingBase_AppNote_UBX-19009093.pdf) - General setup/instructions.
- [u-blox Diagnostics with u-center](../gps_compass/u-center.md) - UART2 diagnostic mode (not available with heading/moving-base modes, which already use UART2 for RTCM).
- [RTK GPS > GPS as Yaw/Heading Source](../gps_compass/rtk_gps.md#configuring-gps-as-yaw-heading-source)
+54
View File
@@ -0,0 +1,54 @@
# u-blox Diagnostics with u-center
<Badge type="tip" text="main (PX4 v2.0)" />
[u-center](https://www.u-blox.com/en/product/u-center) is u-blox's desktop tool for monitoring a receiver's live satellite, signal, and position data, and for reading and writing its configuration.
Setting [GPS_UBX_MODE](#GPS_UBX_MODE) to `7` configures a u-blox receiver's `UART2` as a UBX diagnostic port for [u-center](https://www.u-blox.com/en/product/u-center), while the receiver continues to serve the autopilot on `UART1` (as usual).
This is useful for diagnosing poor fixes, interference, or RTK issues without disconnecting the autopilot.
:::info
Heading and static-base-on-UART2 setups cannot use this feature.
For more information see [Constraints](#constraints) below.
:::
## 배선
Connect the adapter's RX to the receiver's `UART2` TX, its TX to `UART2` RX, and share ground.
u-blox UART pins are 3.3 V.
## PX4 설정
The parameters to set:
| Parameter | 설정 |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| <a id="GPS_UBX_MODE"></a>[GPS_UBX_MODE](../advanced_config/parameter_reference.md#GPS_UBX_MODE) | `u-center on UART2` (7) |
| [GPS_UBX_BAUD2](../advanced_config/parameter_reference.md#GPS_UBX_BAUD2) | UART2 baudrate, must match the USB-serial adapter (default 230400) |
Both parameters take effect after a reboot.
## Messages Enabled on UART2
The following messages are enabled when `GPS_UBX_MODE` is set to `7`:
| 메시지 | 주파수 |
| -------------------------------------------- | ----------------------- |
| `NAV-PVT`, `NAV-DOP`, `NAV-STATUS`, `MON-RF` | Every navigation epoch |
| `NAV-HPPOSLLH` | Every epoch, except M9 |
| `RXM-RTCM` | Every epoch, M9 and F9P |
| `NAV-SAT` | Every 10th epoch |
The set runs around 300 bytes per navigation epoch (GPS update cycle), roughly triple that on the epoch carrying `NAV-SAT`.
The default `UART2` baud rate (230400) covers the 25 Hz maximum; 115200 is the practical floor at the 10 Hz default rate.
Below that, the `NAV-SAT` epoch saturates the link, and a u-blox receiver drops messages on a congested port rather than throttling: the result is gaps in u-center.
## 제약 조건
- UBX input is enabled on `UART2`, so anything connected there can reconfigure the receiver.
Use this on the bench, not in flight.
- The driver writes to the receiver's RAM configuration layer on every boot.
Changes made from u-center to the RAM layer are lost at the next power cycle; changes written to BBR or flash persist and will fight the driver.
- `GPS_UBX_MODE` 1, 2 and 5 use `UART2` for RTCM, so heading and static-base-on-UART2 setups cannot use mode 7.
- The mode is skipped with a warning on M10 and F10 receivers, and on receivers older than u-blox protocol version 27.
+1 -1
View File
@@ -20,7 +20,7 @@ A kit qualifies when it meets all five requirements:
4. A guide, a focused tutorial, and a reference sheet included with the kit
5. Third-party build quality verification
The reference sheet must ship printed, in the box: pinouts, connectors, and specs at a glance, with no screen required ([example: ModalAI VOXL 2 reference sheet](https://docs.modalai.com/voxl2-d0014)).
The reference sheet must ship printed, in the box: pinouts, connectors, and specs at a glance, with no screen required ([example: ModalAI VOXL 2 reference sheet](https://docs.modalai.com/voxl2-d0014/)).
The guide and tutorial may ship as QR-code links.
## What Qualifying Looks Like in Practice
+5
View File
@@ -727,4 +727,9 @@ ver <command> [arguments...]
hwbasecmp Compare hardware base (returns 0 on match)
<hwbase> [<hwbase2>] Hardware type to compare against (eg. V2). An OR
comparison is used if multiple are specified
hwpopcmp Compare HW population option (returns 0 on match)
<value> [<value2>] Hex population option value(s) to compare against (eg.
06, cafe, ffff). An OR comparison is used if multiple are
specified
```
+1 -1
View File
@@ -572,7 +572,7 @@ ina228 <command> [arguments...]
[-a <val>] I2C address
default: 69
[-k] if initialization (probing) fails, keep retrying periodically
[-t <val>] battery index for calibration values (1 or 3)
[-t <val>] battery index for calibration values (1-3)
default: 1
stop
@@ -59,6 +59,37 @@ auav <command> [arguments...]
status print status info
```
## dlvr
Source: [drivers/differential_pressure/dlvr](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure/dlvr)
### 설명
I2C driver for _Amphenol All Sensors_ Digital Low Voltage R-Series (DLVR) pressure sensors
(continuous-sampling variants only).
The driver is enabled for specific sensor-variants using the parameter "SENS_EN_DLVR".
### Usage {#dlvr_usage}
```
dlvr <command> [arguments...]
Commands:
start
[-I] Internal I2C bus(es)
[-X] External I2C bus(es)
[-b <val>] board-specific bus (default=all) (external SPI: n-th bus
(default=1))
[-f <val>] bus frequency in kHz
[-q] quiet startup (no message if no device found)
[-a <val>] I2C address
default: 40
stop
status print status info
```
## ets_airspeed
Source: [drivers/differential_pressure/ets](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure/ets)
+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/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/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/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-gnss-ins)
This driver is not included in the firmware by default.
Include the module in firmware by setting the
@@ -202,7 +202,7 @@ iis2mdc <command> [arguments...]
[-f <val>] bus frequency in kHz
[-q] quiet startup (no message if no device found)
[-a <val>] I2C address
default: 48
default: 30
stop
+22 -18
View File
@@ -29,24 +29,25 @@ vehicle_command cannot propagate to the consumers applying the failures.
Used in field(s): [unit](#fld_unit)
| 명칭 | 형식 | Value | 설명 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | -- |
| <a id="#FAILURE_UNIT_SENSOR_GYRO"></a> FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | |
| <a id="#FAILURE_UNIT_SENSOR_ACCEL"></a> FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | |
| <a id="#FAILURE_UNIT_SENSOR_MAG"></a> FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_BARO"></a> FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | |
| <a id="#FAILURE_UNIT_SENSOR_GPS"></a> FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | |
| <a id="#FAILURE_UNIT_SENSOR_OPTICAL_FLOW"></a> FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | |
| <a id="#FAILURE_UNIT_SENSOR_VIO"></a> FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | |
| <a id="#FAILURE_UNIT_SENSOR_DISTANCE_SENSOR"></a> FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | |
| <a id="#FAILURE_UNIT_SENSOR_AIRSPEED"></a> FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | |
| <a id="#FAILURE_UNIT_SYSTEM_BATTERY"></a> FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | |
| <a id="#FAILURE_UNIT_SYSTEM_MOTOR"></a> FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | |
| <a id="#FAILURE_UNIT_SYSTEM_SERVO"></a> FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | |
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
| 명칭 | 형식 | Value | 설명 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | -- |
| <a id="#FAILURE_UNIT_SENSOR_GYRO"></a> FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | |
| <a id="#FAILURE_UNIT_SENSOR_ACCEL"></a> FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | |
| <a id="#FAILURE_UNIT_SENSOR_MAG"></a> FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_BARO"></a> FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | |
| <a id="#FAILURE_UNIT_SENSOR_GPS"></a> FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | |
| <a id="#FAILURE_UNIT_SENSOR_OPTICAL_FLOW"></a> FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | |
| <a id="#FAILURE_UNIT_SENSOR_VIO"></a> FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | |
| <a id="#FAILURE_UNIT_SENSOR_DISTANCE_SENSOR"></a> FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | |
| <a id="#FAILURE_UNIT_SENSOR_AIRSPEED"></a> FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | |
| <a id="#FAILURE_UNIT_SYSTEM_BATTERY"></a> FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | |
| <a id="#FAILURE_UNIT_SYSTEM_MOTOR"></a> FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | |
| <a id="#FAILURE_UNIT_SYSTEM_SERVO"></a> FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | |
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
| <a id="#FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE | `uint8` | 107 | |
### FAILURE_TYPE {#FAILURE_TYPE}
@@ -62,6 +63,7 @@ Used in field(s): [failure_type](#fld_failure_type)
| <a id="#FAILURE_TYPE_SLOW"></a> FAILURE_TYPE_SLOW | `uint8` | 5 | |
| <a id="#FAILURE_TYPE_DELAYED"></a> FAILURE_TYPE_DELAYED | `uint8` | 6 | |
| <a id="#FAILURE_TYPE_INTERMITTENT"></a> FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | |
| <a id="#FAILURE_TYPE_DRIFT"></a> FAILURE_TYPE_DRIFT | `uint8` | 8 | |
## Constants
@@ -109,6 +111,7 @@ uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103
uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104
uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105
uint8 FAILURE_UNIT_SYSTEM_ESC = 106
uint8 FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE = 107
uint16[4] instance_mask # Bit i targets instance (i+1); 0xFFFF = all instances
@@ -123,6 +126,7 @@ uint8 FAILURE_TYPE_WRONG = 4
uint8 FAILURE_TYPE_SLOW = 5
uint8 FAILURE_TYPE_DELAYED = 6
uint8 FAILURE_TYPE_INTERMITTENT = 7
uint8 FAILURE_TYPE_DRIFT = 8
```
:::
+3
View File
@@ -24,6 +24,7 @@ pageClass: is-wide-page
| 명칭 | 형식 | Value | 설명 |
| ------------------------------------------------------------------------------------------------------------------------ | ------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="#MAX_INSTANCES"></a> MAX_INSTANCES | `uint8` | 3 | |
| <a id="#MAV_FUEL_TYPE_UNKNOWN"></a> MAV_FUEL_TYPE_UNKNOWN | `uint8` | 0 | fuel type not specified. Fuel levels are normalized (i.e., maximum is 1, and other levels are relative to 1). |
| <a id="#MAV_FUEL_TYPE_LIQUID"></a> MAV_FUEL_TYPE_LIQUID | `uint8` | 1 | represents generic liquid fuels, such as gasoline or diesel. Fuel levels are measured in millilitres (ml), and flow rates in millilitres per second (ml/s). |
| <a id="#MAV_FUEL_TYPE_GAS"></a> MAV_FUEL_TYPE_GAS | `uint8` | 2 | represents a gas fuel, such as hydrogen, methane, or propane. Fuel levels are in kilo-Pascal (kPa), and flow rates are in milliliters per second (ml/s). |
@@ -36,6 +37,8 @@ pageClass: is-wide-page
Click here to see original file
```c
uint8 MAX_INSTANCES = 3
uint64 timestamp # time since system start (microseconds)
float32 maximum_fuel_capacity # maximum fuel capacity. Must always be provided, either from the driver or a parameter
+3
View File
@@ -35,6 +35,7 @@ pageClass: is-wide-page
| <a id="fld_throttle_trim"></a>throttle_trim | `float32` | | | estimated throttle value [0,1] required to fly level at equivalent_airspeed_sp in the current atmospheric conditions |
| <a id="fld_underspeed_ratio"></a>underspeed_ratio | `float32` | | | 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. |
| <a id="fld_fast_descend_ratio"></a>fast_descend_ratio | `float32` | | | value indicating if fast descend mode is enabled with ramp up and ramp down [0-1] |
| <a id="fld_weight_ratio"></a>weight_ratio | `float32` | | | Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled. |
## Source Message
@@ -75,6 +76,8 @@ float32 throttle_trim # estimated throttle value [0,1] required to fly level a
float32 underspeed_ratio # 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0.
float32 fast_descend_ratio # value indicating if fast descend mode is enabled with ramp up and ramp down [0-1]
float32 weight_ratio # [-] Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled.
```
:::
+67 -65
View File
@@ -1622,71 +1622,72 @@ Change heading/course. param1: heading type (0=course-over-ground, 1=heading). p
## Constants
| 명칭 | 형식 | Value | 설명 |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
| <a id="#PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION"></a> PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION | `uint16` | 3 | Param value for VEHICLE_CMD_PREFLIGHT_CALIBRATION to start temperature calibration. |
| <a id="#FUSION_SOURCE_GPS"></a> FUSION_SOURCE_GPS | `uint8` | 0 | GNSS (EKF2_GPS{i}\_CTRL, use instance param) |
| <a id="#FUSION_SOURCE_OF"></a> FUSION_SOURCE_OF | `uint8` | 1 | Optical Flow (EKF2_OF_CTRL) |
| <a id="#FUSION_SOURCE_EV"></a> FUSION_SOURCE_EV | `uint8` | 2 | External Vision (EKF2_EV_CTRL) |
| <a id="#FUSION_SOURCE_AGP"></a> FUSION_SOURCE_AGP | `uint8` | 3 | Auxiliary Global Position (EKF2_AGP{i}\_CTRL, use instance param) |
| <a id="#FUSION_SOURCE_BARO"></a> FUSION_SOURCE_BARO | `uint8` | 4 | Barometer (EKF2_BARO_CTRL) |
| <a id="#FUSION_SOURCE_RNG"></a> FUSION_SOURCE_RNG | `uint8` | 5 | Range Finder (EKF2_RNG_CTRL) |
| <a id="#FUSION_SOURCE_MAG"></a> FUSION_SOURCE_MAG | `uint8` | 6 | Magnetometer (EKF2_MAG_TYPE) |
| <a id="#FUSION_SOURCE_ASPD"></a> FUSION_SOURCE_ASPD | `uint8` | 7 | Airspeed (EKF2_ARSP_THR) |
| <a id="#FUSION_SOURCE_RNGBCN"></a> FUSION_SOURCE_RNGBCN | `uint8` | 8 | Ranging Beacon |
| <a id="#VEHICLE_MOUNT_MODE_RETRACT"></a> VEHICLE_MOUNT_MODE_RETRACT | `uint8` | 0 | Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_NEUTRAL"></a> VEHICLE_MOUNT_MODE_NEUTRAL | `uint8` | 1 | Load and keep neutral position (Roll,Pitch,Yaw) from permanent memory. |
| <a id="#VEHICLE_MOUNT_MODE_MAVLINK_TARGETING"></a> VEHICLE_MOUNT_MODE_MAVLINK_TARGETING | `uint8` | 2 | Load neutral position and start MAVLink Roll,Pitch,Yaw control with stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_RC_TARGETING"></a> VEHICLE_MOUNT_MODE_RC_TARGETING | `uint8` | 3 | Load neutral position and start RC Roll,Pitch,Yaw control with stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_GPS_POINT"></a> VEHICLE_MOUNT_MODE_GPS_POINT | `uint8` | 4 | Load neutral position and start to point to Lat,Lon,Alt. |
| <a id="#VEHICLE_MOUNT_MODE_ENUM_END"></a> VEHICLE_MOUNT_MODE_ENUM_END | `uint8` | 5 | |
| <a id="#ACTUATOR_CONFIGURATION_NONE"></a> ACTUATOR_CONFIGURATION_NONE | `uint8` | 0 | Do nothing. |
| <a id="#ACTUATOR_CONFIGURATION_BEEP"></a> ACTUATOR_CONFIGURATION_BEEP | `uint8` | 1 | Command the actuator to beep now. |
| <a id="#ACTUATOR_CONFIGURATION_3D_MODE_ON"></a> ACTUATOR_CONFIGURATION_3D_MODE_ON | `uint8` | 2 | Permanently set the actuator (ESC) to 3D mode (reversible thrust). |
| <a id="#ACTUATOR_CONFIGURATION_3D_MODE_OFF"></a> ACTUATOR_CONFIGURATION_3D_MODE_OFF | `uint8` | 3 | Permanently set the actuator (ESC) to non 3D mode (non-reversible thrust). |
| <a id="#ACTUATOR_CONFIGURATION_SPIN_DIRECTION1"></a> ACTUATOR_CONFIGURATION_SPIN_DIRECTION1 | `uint8` | 4 | Permanently set the actuator (ESC) to spin direction 1 (which can be clockwise or counter-clockwise). |
| <a id="#ACTUATOR_CONFIGURATION_SPIN_DIRECTION2"></a> ACTUATOR_CONFIGURATION_SPIN_DIRECTION2 | `uint8` | 5 | Permanently set the actuator (ESC) to spin direction 2 (opposite of direction 1). |
| <a id="#PARACHUTE_ACTION_DISABLE"></a> PARACHUTE_ACTION_DISABLE | `uint8` | 0 | |
| <a id="#PARACHUTE_ACTION_ENABLE"></a> PARACHUTE_ACTION_ENABLE | `uint8` | 1 | |
| <a id="#PARACHUTE_ACTION_RELEASE"></a> PARACHUTE_ACTION_RELEASE | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_GYRO"></a> FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | |
| <a id="#FAILURE_UNIT_SENSOR_ACCEL"></a> FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | |
| <a id="#FAILURE_UNIT_SENSOR_MAG"></a> FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_BARO"></a> FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | |
| <a id="#FAILURE_UNIT_SENSOR_GPS"></a> FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | |
| <a id="#FAILURE_UNIT_SENSOR_OPTICAL_FLOW"></a> FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | |
| <a id="#FAILURE_UNIT_SENSOR_VIO"></a> FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | |
| <a id="#FAILURE_UNIT_SENSOR_DISTANCE_SENSOR"></a> FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | |
| <a id="#FAILURE_UNIT_SENSOR_AIRSPEED"></a> FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | |
| <a id="#FAILURE_UNIT_SYSTEM_BATTERY"></a> FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | |
| <a id="#FAILURE_UNIT_SYSTEM_MOTOR"></a> FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | |
| <a id="#FAILURE_UNIT_SYSTEM_SERVO"></a> FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | |
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
| <a id="#FAILURE_TYPE_OK"></a> FAILURE_TYPE_OK | `uint8` | 0 | |
| <a id="#FAILURE_TYPE_OFF"></a> FAILURE_TYPE_OFF | `uint8` | 1 | |
| <a id="#FAILURE_TYPE_STUCK"></a> FAILURE_TYPE_STUCK | `uint8` | 2 | |
| <a id="#FAILURE_TYPE_GARBAGE"></a> FAILURE_TYPE_GARBAGE | `uint8` | 3 | |
| <a id="#FAILURE_TYPE_WRONG"></a> FAILURE_TYPE_WRONG | `uint8` | 4 | |
| <a id="#FAILURE_TYPE_SLOW"></a> FAILURE_TYPE_SLOW | `uint8` | 5 | |
| <a id="#FAILURE_TYPE_DELAYED"></a> FAILURE_TYPE_DELAYED | `uint8` | 6 | |
| <a id="#FAILURE_TYPE_INTERMITTENT"></a> FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | |
| <a id="#RC_TYPE_SPEKTRUM"></a> RC_TYPE_SPEKTRUM | `uint8` | 0 | |
| <a id="#RC_TYPE_CRSF"></a> RC_TYPE_CRSF | `uint8` | 1 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSM2"></a> RC_SUB_TYPE_SPEKTRUM_DSM2 | `uint8` | 0 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSMX"></a> RC_SUB_TYPE_SPEKTRUM_DSMX | `uint8` | 1 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSMX8"></a> RC_SUB_TYPE_SPEKTRUM_DSMX8 | `uint8` | 2 | |
| <a id="#ARMING_ACTION_DISARM"></a> ARMING_ACTION_DISARM | `int8` | 0 | |
| <a id="#ARMING_ACTION_ARM"></a> ARMING_ACTION_ARM | `int8` | 1 | |
| <a id="#GRIPPER_ACTION_RELEASE"></a> GRIPPER_ACTION_RELEASE | `uint8` | 0 | |
| <a id="#GRIPPER_ACTION_GRAB"></a> GRIPPER_ACTION_GRAB | `uint8` | 1 | |
| <a id="#SAFETY_OFF"></a> SAFETY_OFF | `uint8` | 0 | |
| <a id="#SAFETY_ON"></a> SAFETY_ON | `uint8` | 1 | |
| <a id="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH | `uint8` | 8 | |
| <a id="#COMPONENT_MODE_EXECUTOR_START"></a> COMPONENT_MODE_EXECUTOR_START | `uint16` | 1000 | |
| 명칭 | 형식 | Value | 설명 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
| <a id="#PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION"></a> PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION | `uint16` | 3 | Param value for VEHICLE_CMD_PREFLIGHT_CALIBRATION to start temperature calibration. |
| <a id="#FUSION_SOURCE_GPS"></a> FUSION_SOURCE_GPS | `uint8` | 0 | GNSS (EKF2_GPS{i}\_CTRL, use instance param) |
| <a id="#FUSION_SOURCE_OF"></a> FUSION_SOURCE_OF | `uint8` | 1 | Optical Flow (EKF2_OF_CTRL) |
| <a id="#FUSION_SOURCE_EV"></a> FUSION_SOURCE_EV | `uint8` | 2 | External Vision (EKF2_EV_CTRL) |
| <a id="#FUSION_SOURCE_AGP"></a> FUSION_SOURCE_AGP | `uint8` | 3 | Auxiliary Global Position (EKF2_AGP{i}\_CTRL, use instance param) |
| <a id="#FUSION_SOURCE_BARO"></a> FUSION_SOURCE_BARO | `uint8` | 4 | Barometer (EKF2_BARO_CTRL) |
| <a id="#FUSION_SOURCE_RNG"></a> FUSION_SOURCE_RNG | `uint8` | 5 | Range Finder (EKF2_RNG_CTRL) |
| <a id="#FUSION_SOURCE_MAG"></a> FUSION_SOURCE_MAG | `uint8` | 6 | Magnetometer (EKF2_MAG_TYPE) |
| <a id="#FUSION_SOURCE_ASPD"></a> FUSION_SOURCE_ASPD | `uint8` | 7 | Airspeed (EKF2_ARSP_THR) |
| <a id="#FUSION_SOURCE_RNGBCN"></a> FUSION_SOURCE_RNGBCN | `uint8` | 8 | Ranging Beacon |
| <a id="#VEHICLE_MOUNT_MODE_RETRACT"></a> VEHICLE_MOUNT_MODE_RETRACT | `uint8` | 0 | Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_NEUTRAL"></a> VEHICLE_MOUNT_MODE_NEUTRAL | `uint8` | 1 | Load and keep neutral position (Roll,Pitch,Yaw) from permanent memory. |
| <a id="#VEHICLE_MOUNT_MODE_MAVLINK_TARGETING"></a> VEHICLE_MOUNT_MODE_MAVLINK_TARGETING | `uint8` | 2 | Load neutral position and start MAVLink Roll,Pitch,Yaw control with stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_RC_TARGETING"></a> VEHICLE_MOUNT_MODE_RC_TARGETING | `uint8` | 3 | Load neutral position and start RC Roll,Pitch,Yaw control with stabilization. |
| <a id="#VEHICLE_MOUNT_MODE_GPS_POINT"></a> VEHICLE_MOUNT_MODE_GPS_POINT | `uint8` | 4 | Load neutral position and start to point to Lat,Lon,Alt. |
| <a id="#VEHICLE_MOUNT_MODE_ENUM_END"></a> VEHICLE_MOUNT_MODE_ENUM_END | `uint8` | 5 | |
| <a id="#ACTUATOR_CONFIGURATION_NONE"></a> ACTUATOR_CONFIGURATION_NONE | `uint8` | 0 | Do nothing. |
| <a id="#ACTUATOR_CONFIGURATION_BEEP"></a> ACTUATOR_CONFIGURATION_BEEP | `uint8` | 1 | Command the actuator to beep now. |
| <a id="#ACTUATOR_CONFIGURATION_3D_MODE_ON"></a> ACTUATOR_CONFIGURATION_3D_MODE_ON | `uint8` | 2 | Permanently set the actuator (ESC) to 3D mode (reversible thrust). |
| <a id="#ACTUATOR_CONFIGURATION_3D_MODE_OFF"></a> ACTUATOR_CONFIGURATION_3D_MODE_OFF | `uint8` | 3 | Permanently set the actuator (ESC) to non 3D mode (non-reversible thrust). |
| <a id="#ACTUATOR_CONFIGURATION_SPIN_DIRECTION1"></a> ACTUATOR_CONFIGURATION_SPIN_DIRECTION1 | `uint8` | 4 | Permanently set the actuator (ESC) to spin direction 1 (which can be clockwise or counter-clockwise). |
| <a id="#ACTUATOR_CONFIGURATION_SPIN_DIRECTION2"></a> ACTUATOR_CONFIGURATION_SPIN_DIRECTION2 | `uint8` | 5 | Permanently set the actuator (ESC) to spin direction 2 (opposite of direction 1). |
| <a id="#PARACHUTE_ACTION_DISABLE"></a> PARACHUTE_ACTION_DISABLE | `uint8` | 0 | |
| <a id="#PARACHUTE_ACTION_ENABLE"></a> PARACHUTE_ACTION_ENABLE | `uint8` | 1 | |
| <a id="#PARACHUTE_ACTION_RELEASE"></a> PARACHUTE_ACTION_RELEASE | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_GYRO"></a> FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | |
| <a id="#FAILURE_UNIT_SENSOR_ACCEL"></a> FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | |
| <a id="#FAILURE_UNIT_SENSOR_MAG"></a> FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | |
| <a id="#FAILURE_UNIT_SENSOR_BARO"></a> FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | |
| <a id="#FAILURE_UNIT_SENSOR_GPS"></a> FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | |
| <a id="#FAILURE_UNIT_SENSOR_OPTICAL_FLOW"></a> FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | |
| <a id="#FAILURE_UNIT_SENSOR_VIO"></a> FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | |
| <a id="#FAILURE_UNIT_SENSOR_DISTANCE_SENSOR"></a> FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | |
| <a id="#FAILURE_UNIT_SENSOR_AIRSPEED"></a> FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | |
| <a id="#FAILURE_UNIT_SYSTEM_BATTERY"></a> FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | |
| <a id="#FAILURE_UNIT_SYSTEM_MOTOR"></a> FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | |
| <a id="#FAILURE_UNIT_SYSTEM_SERVO"></a> FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | |
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
| <a id="#FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE | `uint8` | 107 | |
| <a id="#FAILURE_TYPE_OK"></a> FAILURE_TYPE_OK | `uint8` | 0 | |
| <a id="#FAILURE_TYPE_OFF"></a> FAILURE_TYPE_OFF | `uint8` | 1 | |
| <a id="#FAILURE_TYPE_STUCK"></a> FAILURE_TYPE_STUCK | `uint8` | 2 | |
| <a id="#FAILURE_TYPE_GARBAGE"></a> FAILURE_TYPE_GARBAGE | `uint8` | 3 | |
| <a id="#FAILURE_TYPE_WRONG"></a> FAILURE_TYPE_WRONG | `uint8` | 4 | |
| <a id="#FAILURE_TYPE_SLOW"></a> FAILURE_TYPE_SLOW | `uint8` | 5 | |
| <a id="#FAILURE_TYPE_DELAYED"></a> FAILURE_TYPE_DELAYED | `uint8` | 6 | |
| <a id="#FAILURE_TYPE_INTERMITTENT"></a> FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | |
| <a id="#RC_TYPE_SPEKTRUM"></a> RC_TYPE_SPEKTRUM | `uint8` | 0 | |
| <a id="#RC_TYPE_CRSF"></a> RC_TYPE_CRSF | `uint8` | 1 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSM2"></a> RC_SUB_TYPE_SPEKTRUM_DSM2 | `uint8` | 0 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSMX"></a> RC_SUB_TYPE_SPEKTRUM_DSMX | `uint8` | 1 | |
| <a id="#RC_SUB_TYPE_SPEKTRUM_DSMX8"></a> RC_SUB_TYPE_SPEKTRUM_DSMX8 | `uint8` | 2 | |
| <a id="#ARMING_ACTION_DISARM"></a> ARMING_ACTION_DISARM | `int8` | 0 | |
| <a id="#ARMING_ACTION_ARM"></a> ARMING_ACTION_ARM | `int8` | 1 | |
| <a id="#GRIPPER_ACTION_RELEASE"></a> GRIPPER_ACTION_RELEASE | `uint8` | 0 | |
| <a id="#GRIPPER_ACTION_GRAB"></a> GRIPPER_ACTION_GRAB | `uint8` | 1 | |
| <a id="#SAFETY_OFF"></a> SAFETY_OFF | `uint8` | 0 | |
| <a id="#SAFETY_ON"></a> SAFETY_ON | `uint8` | 1 | |
| <a id="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH | `uint8` | 8 | |
| <a id="#COMPONENT_MODE_EXECUTOR_START"></a> COMPONENT_MODE_EXECUTOR_START | `uint16` | 1000 | |
## Source Message
@@ -1871,6 +1872,7 @@ uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103
uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104
uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105
uint8 FAILURE_UNIT_SYSTEM_ESC = 106
uint8 FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE = 107
uint8 FAILURE_TYPE_OK = 0
uint8 FAILURE_TYPE_OFF = 1
+1 -1
View File
@@ -125,6 +125,6 @@ If FluxGrip does not respond:
## See Also
- [FluxGrip: Integration with PX4](https://forum.zubax.com/t/fluxgrip-integration-with-px4/2863) (Zubax Forum)
- [FluxGrip Quickstart Guide](https://forum.zubax.com/t/fluxgrip-quickstart-guide/2335) (Zubax Forum)
- [FluxGrip Quickstart Guide](https://forum.zubax.com/t/fluxgrip-quickstart-guide-v1-1/2864) (Zubax Forum)
- [DroneCAN](../dronecan/index.md)
- [Grippers](gripper.md)
+5 -3
View File
@@ -27,10 +27,11 @@ PX4 currently sends a subset of MSP messages.
Reliably-working display items include:
- Craft name and flight mode / arming state
- Battery voltage, current draw, mAh consumed, average cell voltage
- Average cell voltage, current draw, mAh consumed
- GPS latitude, longitude, satellite count, ground speed
- Home distance and direction
- Home distance
- Altitude (from GNSS / baro)
- Roll / pitch angle
- RSSI
- Crosshairs toggle
@@ -63,7 +64,8 @@ Then rebuild and flash.
3. Reboot.
4. Tune the display via the [`OSD_*` parameters](../advanced_config/parameter_reference.md#osd):
- [`OSD_SYMBOLS`](../advanced_config/parameter_reference.md#OSD_SYMBOLS) — bitmask selecting which items appear.
- [`OSD_CH_HEIGHT`](../advanced_config/parameter_reference.md#OSD_CH_HEIGHT) — vertical position of the crosshairs.
- [`OSD_CH_POS_VER`](../advanced_config/parameter_reference.md#OSD_CH_POS_VER) — vertical position of the crosshairs.
- [`OSD_CH_POS_HOR`](../advanced_config/parameter_reference.md#OSD_CH_POS_HOR) — horizontal position of the crosshairs.
- [`OSD_LOG_LEVEL`](../advanced_config/parameter_reference.md#OSD_LOG_LEVEL) — minimum severity for on-screen warnings.
- [`OSD_SCROLL_RATE`](../advanced_config/parameter_reference.md#OSD_SCROLL_RATE) / [`OSD_DWELL_TIME`](../advanced_config/parameter_reference.md#OSD_DWELL_TIME) — scrolling of long messages.
- [`OSD_RC_STICK`](../advanced_config/parameter_reference.md#OSD_RC_STICK) — forward RC sticks to the VTX when disarmed, so you can navigate the VTX menu.
+5 -5
View File
@@ -22,12 +22,12 @@ Remote ID hardware can only be connected via DroneCAN on `main` branch builds (b
PX4 integrates with Remote ID hardware that supports:
- [Open Drone ID](https://mavlink.io/en/services/opendroneid.html) MAVLink protocol<Badge type="tip" text="PX4 v1.14" />
- Remote ID over CAN<Badge type="tip" text="PX4 main (v1.16)" />
- [Open Drone ID](https://mavlink.io/en/services/opendroneid.html) MAVLink protocol <Badge type="tip" text="PX4 v1.14" />
- Remote ID over CAN <Badge type="tip" text="PX4 main (v1.16)" />
It has been tested with the following devices:
- [Cube ID](https://docs.cubepilot.org/user-guides/cube-id/cube-id) (CubePilot)
- [Cube ID](https://docs.cubepilot.org/cube-id/cube-id) (CubePilot)
- [Db201](https://dronescout.co/dronebeacon-mavlink-remote-id-transponder/) (BlueMark) - Tested via serial port. Not tested via CAN port.
- [Db202mav](https://dronescout.co/dronebeacon-mavlink-remote-id-transponder/) (BlueMark) - Less expensive variant without CAN port.
- [Holybro RemoteID Module](https://holybro.com/products/remote-id) (Holybro)
@@ -41,7 +41,7 @@ Most commonly they are connected directly to the `TELEM2` port (if it is not bei
### Cube ID
[Cube ID](https://docs.cubepilot.org/user-guides/cube-id/cube-id) can be connected using a serial or CAN port.
[Cube ID](https://docs.cubepilot.org/cube-id/cube-id) can be connected using a serial or CAN port.
It comes with 6-pin and 4-pin JST-GH 1.25mm cables that can be connected directly to the `TELEM` serial port and `CAN` ports, respectively, on most recent Pixhawk flight controllers.
@@ -75,7 +75,7 @@ The TX and RX on the flight controller must be connected to the RX and TX on the
The Cube ID uses proprietary firmware (not [ArduRemoteID](https://github.com/ArduPilot/ArduRemoteID) like some other remote id beacons).
For firmware update instructions see [Cube ID > Updating](https://docs.cubepilot.org/user-guides/cube-id/cube-id#updating).
For firmware update instructions see [Cube ID > Updating](https://docs.cubepilot.org/cube-id/cube-id#updating).
### BlueMark Db201/Db202mav
+1 -1
View File
@@ -14,7 +14,7 @@ const { site } = useData();
PX4 릴리스 노트는 각 릴리스의 변경 사항들을 설명합니다.
- [main](../releases/main.md) (changes planned for v1.19 or later)
- [main](../releases/main.md) (changes planned for v2.0 or later)
- [v1.18](../releases/1.18.md) (changes in v1.18, since v1.17)
- [v1.17](../releases/1.17.md)
- [v1.16](../releases/1.16.md)
+7 -2
View File
@@ -17,7 +17,7 @@ This contains changes to the PX4 `main` branch that are not included in the next
:::warning
PX4 v1.18 is in beta testing.
Update these notes with features that are going to be in `main` (PX4 v1.19 or later) but not the PX4 v1.18 release.
Update these notes with features that are going to be in `main` (PX4 v2.0 or later) but not the PX4 v1.18 release.
:::
## Read Before Upgrading
@@ -54,6 +54,11 @@ Please continue reading for [upgrade instructions](#upgrade-guide).
- [Geofence Aware Return mode](../flight_modes/return.md#geofence_awareness). ([PX4-Autopilot#27145: feat(navigator): Geofence Aware RTL](https://github.com/PX4/PX4-Autopilot/pull/27145), [PX4-Autopilot#28001: docs(navigator): [geofence] added some more warnings about limitations](https://github.com/PX4/PX4-Autopilot/pull/28001)).
- [Flight termination](../advanced_config/flight_termination.md) can now be used instead of a Descent mode as a fallback failsafe mode, allowing safer landing for unpiloted vehicles that carry a parachute.
See [Battery level failsafe](../config/safety.md#battery-level-failsafe) ([COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT)) and [Position Loss Failsafe Action](../config/safety.md#position-loss-failsafe-action) (new [COM_POS_FS_ACT](../advanced_config/parameter_reference.md#COM_POS_FS_ACT)). ([PX4-Autopilot#28064: feat(commander): add terminate options for critical battery and lost position failsafes](https://github.com/PX4/PX4-Autopilot/pull/28064)).
- [Failure injection](../debug/failure_injection.md) ( [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN)) has been significantly extended. (PX4-Autopilot#27572, PX4-Autopilot#27832, PX4-Autopilot#27950)
- Now applied on real hardware, not just simulators (injection hooks live in the shared sensor drivers).
- Command handling is centralized behind a dedicated failure-injection manager module.
- Multiple sensor instances can be failed simultaneously via a bitmask, and failures can be triggered from an RC switch.
- Changed default behaviour of injected WRONG failure for Batteries, to publish a wrong level, and not stop publishing
- [Motor failure recovery](../config/motor_failure_recovery.md) for hexarotors: on a single motor failure the control allocator removes the failed motor and additionally stops ([CA_FAILURE_MODE](../advanced_config/parameter_reference.md#CA_FAILURE_MODE) = `1`) or reverses (`2`) the motor opposite it to recover the lost yaw authority. Mode `2` requires a reverse-capable ESC and models the reverse thrust of a forward propeller with the new [CA_REV_THR_FRAC](../advanced_config/parameter_reference.md#CA_REV_THR_FRAC) (default `0.4`). Reversible motor outputs on DroneCAN are now sent as signed `RawCommand` values (negative is reverse). ([PX4-Autopilot#28078](https://github.com/PX4/PX4-Autopilot/pull/28078))
- Added `RTL_TYPE=6` for battery-aware home priority return ([PX4-Autopilot#26968](https://github.com/PX4/PX4-Autopilot/pull/26968)).
Returns to home if the estimated flight time to home is within the remaining battery time; otherwise returns to the closest rally point.
@@ -65,7 +70,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide).
### 센서
- TBD
- Enable [u-blox Diagnostics with u-center](../gps_compass/u-center.md) while the vehicle's GPS runs as usual. ([PX4-Autopilot#28280](https://github.com/PX4/PX4-Autopilot/pull/28280)).
### 시뮬레이션
+1 -1
View File
@@ -10,7 +10,7 @@ If you are operating on a real vehicle be sure to have a way of gaining back man
:::tip
This example uses C++.
A very similar example for Python can be found in [ROS/MAVROS Offboard Example (Python)](../ros/mavros_offboard_python.md) (also see the examples in [integrationtests/python_src/px4_it/mavros](https://github.com/PX4/PX4-Autopilot/tree/main/integrationtests/python_src/px4_it/mavros)).
A very similar example for Python can be found in [ROS/MAVROS Offboard Example (Python)](../ros/mavros_offboard_python.md).
:::
<video width="100%" autoplay="true" controls="true">
+2 -3
View File
@@ -12,7 +12,6 @@ If you are operating on a real vehicle be sure to have a way of gaining back man
:::tip
This example uses Python.
Other examples in Python can be found here: [integrationtests/python_src/px4_it/mavros](https://github.com/PX4/PX4-Autopilot/tree/main/integrationtests/python_src/px4_it/mavros).
:::
<a id="offb_video"></a>
@@ -306,10 +305,10 @@ For the `start_offb.launch` copy the following code:
```
As you can see, the `mavros_posix_sitl.launch` file is included.
This file is responsible for launching MAVROS, the PX4 SITL, the Gazebo Classic Environment and for spawning a vehicle in a given world (for further information see the file [here](https://github.com/PX4/PX4-Autopilot/blob/main/launch/mavros_posix_sitl.launch)).
This file is responsible for launching MAVROS, the PX4 SITL, the Gazebo Classic Environment and for spawning a vehicle in a given world (for further information see the file [here](https://github.com/PX4/PX4-Autopilot/blob/daa89a9116ebe3ef1c173c881eb100c4b15f6d60/launch/mavros_posix_sitl.launch)).
:::tip
The `mavros_posix_sitl.launch` file takes several arguments that can be set according to your preferences such as the vehicle to spawn or the Gazebo Classic world (refer to [here](https://github.com/PX4/PX4-Autopilot/blob/main/launch/mavros_posix_sitl.launch)) for a complete list).
The `mavros_posix_sitl.launch` file takes several arguments that can be set according to your preferences such as the vehicle to spawn or the Gazebo Classic world (refer to [here](https://github.com/PX4/PX4-Autopilot/blob/daa89a9116ebe3ef1c173c881eb100c4b15f6d60/launch/mavros_posix_sitl.launch)) for a complete list).
You can override the default value of these arguments defined in `mavros_posix_sitl.launch` by declaring them inside the _include_ tags.
As an example, if you wanted to spawn the vehicle in the `warehouse.world`, you would write the following:
+150 -88
View File
@@ -4,20 +4,25 @@ The ROS 2-PX4 architecture provides a deep integration between ROS 2 and PX4, al
This topic provides an overview of the architecture and application pipeline, and explains how to setup and use ROS 2 with PX4.
:::info
From PX4 v1.14, ROS 2 uses [uXRCE-DDS](../middleware/uxrce_dds.md) middleware, replacing the _FastRTPS_ middleware that was used in version 1.13 (v1.13 does not support uXRCE-DDS).
The [migration guide](../middleware/uxrce_dds.md#fast-rtps-to-uxrce-dds-migration-guidelines) explains what you need to do in order to migrate ROS 2 apps from PX4 v1.13 to PX4 v1.14.
If you're still working on PX4 v1.13, please follow the instructions in the [PX4 v1.13 Docs](https://docs.px4.io/v1.13/en/ros/ros2_comm).
<!-- remove this when there are PX4 v1.14 docs for some months -->
:::
## 개요
The application pipeline for ROS 2 is very straightforward, thanks to the use of the [uXRCE-DDS](../middleware/uxrce_dds.md) communications middleware.
PX4 supports two middleware options for bridging uORB topics to ROS 2: [uXRCE-DDS](#dds) (DDS) and [Zenoh](#zenoh).
You must select which middleware to use and build your firmware accordingly (see [Installation & Setup](#installation-setup)).
DDS is currently recommended for most users, as it is more established and has been more thoroughly tested with PX4.
If you want to command the vehicle and create custom flight behaviours using ROS 2 (rather than just reading telemetry), you can create external modes using the [PX4 ROS 2 Interface Library](./px4_ros2_interface_lib.md), a ROS 2 native C++ library that works on top of either middleware.
:::info
The instructions below target simulation using Gazebo.
The same concepts translate directly to real hardware: the middleware client, which bridges the uORB topics, runs on the flight controller, while the agent/router runs on your companion computer.
See [Using Flight Controller Hardware](#using-flight-controller-hardware) for the hardware-specific differences.
:::
### DDS
<Badge type="tip" text="PX4 v1.14" />
The [uXRCE-DDS](../middleware/uxrce_dds.md) communications middleware is a large part of what makes the application pipeline for ROS 2 very straightforward.
![Architecture uXRCE-DDS with ROS 2](../../assets/middleware/xrce_dds/architecture_xrce-dds_ros2.svg)
@@ -43,26 +48,35 @@ It can be built from [source](https://github.com/eProsima/Micro-XRCE-DDS-Agent)
You will normally need to start both the client and agent when using ROS 2.
Note that the uXRCE-DDS client is built into firmware by default but not started automatically except for simulator builds.
:::info
In PX4v1.13 and earlier, ROS 2 was dependent on definitions in [px4_ros_com](https://github.com/PX4/px4_ros_com).
This repo is no longer needed, but does contain useful examples.
:::
See [uXRCE-DDS > Version selection](../middleware/uxrce_dds.md#version-selection) to check which Micro XRCE-DDS version to use for your ROS 2 distribution.
### Zenoh
<Badge type="tip" text="PX4 v1.17" /> <Badge type="warning" text="Experimental" />
PX4 supports [Zenoh](../middleware/zenoh.md) as an alternative middleware for bridging uORB topics to ROS 2, via the ROS 2 [`rmw_zenoh`](https://github.com/ros2/rmw_zenoh) middleware.
It provides a fast and lightweight way to connect PX4 to ROS 2.
![Architecture PX4 Zenoh-Pico with ROS 2](../../assets/middleware/zenoh/architecture-px4-zenoh.svg)
The Zenoh-based middleware consists of a client running on PX4 (the [PX4 `zenoh` module](../modules/modules_driver.md#zenoh), based on Zenoh-Pico) and a Zenoh router (typically [zenohd](https://github.com/eclipse-zenoh/zenoh/tree/main/zenohd)) running on the companion computer, with bi-directional data exchange between them over a UART, TCP, UDP, or multicast-UDP link.
The router acts as a broker and discovery service, enabling PX4 to publish and subscribe to topics in the global Zenoh data space, and integrates seamlessly with ROS 2 nodes using `rmw_zenoh`.
See the [Zenoh](../middleware/zenoh.md) middleware page for full architecture and configuration details.
## Installation & Setup
The supported and recommended ROS 2 platform for working with PX4 is ROS 2 "Humble" LTS on Ubuntu 22.04.
The supported and recommended ROS 2 platform for working with PX4 is ROS 2 "Jazzy" LTS on Ubuntu 24.04.
:::tip
If you're working on Ubuntu 20.04 we recommend you update to Ubuntu 22.04.
In the meantime you can use ROS 2 "Foxy" with [Gazebo Classic](../sim_gazebo_classic/index.md) on Ubuntu 20.04.
Note that ROS 2 "Foxy" reached end-of-life in May 2023, but is (at time of writing) still stable and works with PX4.
If you're working on Ubuntu 22.04 you can use ROS 2 "Humble" LTS instead.
:::
To setup ROS 2 for use with PX4:
- [Install PX4](#install-px4) (to use the PX4 simulator)
- [Install ROS 2](#install-ros-2)
- [Setup Micro XRCE-DDS Agent & Client](#setup-micro-xrce-dds-agent-client)
- [Setup Middleware](#setup-middleware)
- [Build & Run ROS 2 Workspace](#build-ros-2-workspace)
Other dependencies of the architecture that are installed automatically, such as _Fast DDS_, are not covered.
@@ -99,6 +113,31 @@ To install ROS 2 and its dependencies:
:::: tabs
::: tab jazzy
To install ROS 2 "Jazzy" on Ubuntu 24.04:
```sh
sudo apt update && sudo apt install locales
sudo locale-gen en_US en_US.UTF-8
sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8
export LANG=en_US.UTF-8
sudo apt install software-properties-common
sudo add-apt-repository universe
sudo apt update && sudo apt install curl -y
export ROS_APT_SOURCE_VERSION=$(curl -s https://api.github.com/repos/ros-infrastructure/ros-apt-source/releases/latest | grep -F "tag_name" | awk -F'"' '{print $4}')
curl -L -o /tmp/ros2-apt-source.deb "https://github.com/ros-infrastructure/ros-apt-source/releases/download/${ROS_APT_SOURCE_VERSION}/ros2-apt-source_${ROS_APT_SOURCE_VERSION}.$(. /etc/os-release && echo ${UBUNTU_CODENAME:-${VERSION_CODENAME}})_all.deb"
sudo dpkg -i /tmp/ros2-apt-source.deb
sudo apt update && sudo apt upgrade -y
sudo apt install ros-jazzy-desktop
sudo apt install ros-dev-tools
source /opt/ros/jazzy/setup.bash && echo "source /opt/ros/jazzy/setup.bash" >> .bashrc
```
The instructions above are reproduced from the official installation guide: [Install ROS 2 Jazzy](https://docs.ros.org/en/jazzy/Installation/Ubuntu-Install-Debs.html).
You can install _either_ the desktop (`ros-jazzy-desktop`) _or_ bare-bones versions (`ros-jazzy-ros-base`), _and_ the development tools (`ros-dev-tools`).
:::
::: tab humble
To install ROS 2 "Humble" on Ubuntu 22.04:
@@ -121,15 +160,6 @@ To install ROS 2 and its dependencies:
The instructions above are reproduced from the official installation guide: [Install ROS 2 Humble](https://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debs.html).
You can install _either_ the desktop (`ros-humble-desktop`) _or_ bare-bones versions (`ros-humble-ros-base`), _and_ the development tools (`ros-dev-tools`).
:::
::: tab foxy
To install ROS 2 "Foxy" on Ubuntu 20.04:
- Follow the official installation guide: [Install ROS 2 Foxy](https://docs.ros.org/en/foxy/Installation/Ubuntu-Install-Debians.html).
You can install _either_ the desktop (`ros-foxy-desktop`) _or_ bare-bones versions (`ros-foxy-ros-base`), _and_ the development tools (`ros-dev-tools`).
:::
::::
@@ -140,11 +170,21 @@ To install ROS 2 and its dependencies:
pip install --user -U empy==3.3.4 pyros-genmsg setuptools
```
### Setup Micro XRCE-DDS Agent & Client
### Setup Middleware
This section explains how to set up either the [DDS](#dds_setup) or [Zenoh](#zenoh_setup) middleware.
:::tip
DDS is recommended for most users, as it is more established and has been more thoroughly tested with PX4.
:::
Make sure that your firmware has the corresponding module enabled: the [uxrce_dds_client](../modules/modules_system.md#uxrce-dds-client) module is included by default in most builds, while the [zenoh](../middleware/zenoh.md#px4-firmware) module must be explicitly enabled.
#### DDS {#dds_setup}
For ROS 2 to communicate with PX4, [uXRCE-DDS client](../modules/modules_system.md#uxrce-dds-client) must be running on PX4, connected to a micro XRCE-DDS agent running on the companion computer.
#### Setup the Agent
##### Setup the Agent
The agent can be installed onto the companion computer in a [number of ways](../middleware/uxrce_dds.md#micro-xrce-dds-agent-installation).
Below we show how to build the agent "standalone" from source and connect to a client running on the PX4 simulator.
@@ -179,7 +219,7 @@ You can leave the agent running in this terminal!
Note that only one agent is allowed per connection channel.
:::
#### Start the Client
##### Start the DDS Client
The PX4 simulator starts the uXRCE-DDS client automatically, connecting to UDP port 8888 on the local host.
@@ -187,31 +227,11 @@ To start the simulator (and client):
1. Open a new terminal in the root of the **PX4 Autopilot** repo that was installed above.
:::: tabs
Start a PX4 [Gazebo](../sim_gazebo_gz/index.md) simulation using:
::: tab humble
- Start a PX4 [Gazebo](../sim_gazebo_gz/index.md) simulation using:
```sh
make px4_sitl gz_x500
```
:::
::: tab foxy
- Start a PX4 [Gazebo Classic](../sim_gazebo_classic/index.md) simulation using:
```sh
make px4_sitl gazebo-classic
```
:::
::::
```sh
make px4_sitl gz_x500
```
The agent and client are now running they should connect.
@@ -237,6 +257,51 @@ The micro XRCE-DDS agent terminal should also start to show output, as equivalen
...
```
#### Zenoh {#zenoh_setup}
<Badge type="tip" text="PX4 v1.17" /> <Badge type="warning" text="Experimental" />
For ROS 2 to communicate with PX4 via Zenoh, the [PX4 Zenoh-Pico Node](../middleware/zenoh.md) must be running on PX4, connected to a Zenoh router (`zenohd`) running on the companion computer.
##### Setup the Router
Install and start the Zenoh router using ROS 2:
```sh
export RMW_IMPLEMENTATION=rmw_zenoh_cpp
ros2 run rmw_zenoh_cpp rmw_zenohd
```
For more information about the Zenoh Router see the [rmw_zenoh](https://github.com/ros2/rmw_zenoh?tab=readme-ov-file#start-the-zenoh-router) documentation.
:::info
You can leave the router running in this terminal!
:::
##### Start the Zenoh Client
To start the simulator (and client):
1. Open a new terminal in the root of the **PX4 Autopilot** repo that was installed above.
Start a Zenoh-enabled PX4 [Gazebo](../sim_gazebo_gz/index.md) simulation using:
```sh
make px4_sitl_zenoh gz_x500
```
2. In the PX4 shell, enable Zenoh and reboot to apply the change:
```sh
param set ZENOH_ENABLE 1
reboot
```
The default Zenoh daemon address for the `px4_sitl_zenoh` target is `localhost`, so no further network configuration is needed for simulation.
See [Zenoh > Configure Zenoh Network](../middleware/zenoh.md#configure-zenoh-network) if you need to connect to a router at a different address (such as on real hardware).
Once the client and router are connected, you can inspect the available topics using standard ROS 2 CLI tools, e.g. `ros2 topic list`.
### ROS 2 작업 공간 빌드
This section shows how to create a ROS 2 workspace hosted in your home directory (modify the commands as needed to put the source code elsewhere).
@@ -282,22 +347,22 @@ To create and build the workspace:
:::: tabs
::: tab humble
::: tab jazzy
```sh
cd ..
source /opt/ros/humble/setup.bash
source /opt/ros/jazzy/setup.bash
colcon build
```
:::
::: tab foxy
::: tab humble
```sh
cd ..
source /opt/ros/foxy/setup.bash
source /opt/ros/humble/setup.bash
colcon build
```
@@ -320,10 +385,20 @@ The [ROS2 beginner tutorials](https://docs.ros.org/en/humble/Tutorials/Beginner-
In a new terminal:
1. Navigate into the top level of your workspace directory and source the ROS 2 environment (in this case "Humble"):
1. Navigate into the top level of your workspace directory and source the ROS 2 environment (in this case "Jazzy"):
:::: tabs
::: tab jazzy
```sh
cd ~/ws_sensor_combined/
source /opt/ros/jazzy/setup.bash
```
:::
::: tab humble
```sh
@@ -332,16 +407,6 @@ In a new terminal:
```
:::
::: tab foxy
```sh
cd ~/ws_sensor_combined/
source /opt/ros/foxy/setup.bash
```
:::
::::
@@ -503,6 +568,15 @@ Use the following commands to install the correct ROS 2/gz interface packages (n
:::: tabs
:::tab jazzy
To install the bridge for use with ROS 2 "Jazzy" and Gazebo Harmonic (on Ubuntu 24.04):
```sh
sudo apt install ros-jazzy-ros-gzharmonic
```
:::
:::tab humble
To install the bridge for use with ROS 2 "Humble" and Gazebo Harmonic (on Ubuntu 22.04):
@@ -512,17 +586,6 @@ sudo apt install ros-humble-ros-gzharmonic
:::
:::tab foxy
First you will need to [install Gazebo Garden](../sim_gazebo_gz/index.md#installation-ubuntu-linux), as by default Foxy comes with Gazebo Classic 11. <!-- note, garden is EOL Nov 2024 -->
Then to install the interface packages for use with ROS 2 "Foxy" and Gazebo (Ubuntu 20.04):
```sh
sudo apt install ros-foxy-ros-gzgarden
```
:::
::::
:::info
@@ -984,20 +1047,19 @@ If any are missing, they can be added separately:
:::: tabs
::: tab humble
::: tab jazzy
```sh
sudo apt install ros-humble-eigen3-cmake-module
sudo apt install ros-jazzy-eigen3-cmake-module
```
:::
::: tab foxy
::: tab humble
```sh
$ cd ~/px4_ros_com_ros2/src/px4_ros_com/scripts
$ source build_ros2_workspace.bash
sudo apt install ros-humble-eigen3-cmake-module
```
+10 -5
View File
@@ -19,6 +19,10 @@ For fixed-wing flight it is the airspeed that guarantees lift — not ground spe
- I2C Sensirion series (e.g. SDP33)
- [ThunderFly TFPITOT01 Lightweight Pitot Tube](https://docs.thunderfly.cz/avionics/TFPITOT01/)
- [Drotek SDP3x Airspeed Sensor Kit](https://store-drotek.com/848-sdp3x-airspeed-sensor-kit-sdp33.html)
- I2C _Amphenol All Sensors_ Digital Low Voltage R-Series (DLVR) Pressure Sensors.
Continuous-sampling sensors only (see for [SENS_EN_DLVR](../advanced_config/parameter_reference.md#SENS_EN_DLVR) for supported sensors).
- [MATEKSYS Digital AirSpeed sensor ASPD-DLVR](https://www.mateksys.com/?portfolio=aspd-dlvr)
- [RCDrone Digital AirSpeed sensor ASPD-DLVR](https://rcdrone.top/products/matek-mateksys-digital-airspeed-sensor-aspd-dlvr)
- DroneCAN interface
- [Holybro High Precision DroneCAN Airspeed Sensor - DLVR](https://holybro.com/collections/sensors/products/high-precision-dronecan-airspeed-sensor-dlvr)
- [RaccoonLab Cyphal/CAN and DroneCAN Airspeed Sensor - MS4525DO](https://raccoonlab.co/tproduct/360882105-652259850171-cyphal-and-dronecan-airspeed-v2)
@@ -32,12 +36,13 @@ For fixed-wing flight it is the airspeed that guarantees lift — not ground spe
### Enable Airspeed Sensors
Airspeed sensor drivers are not started automatically.
Enable each type using its [corresponding parameter](../advanced_config/parameters.md):
Enable each driver and/or variant using its [corresponding parameter](../advanced_config/parameters.md):
- **Sensirion SDP3X:** [SENS_EN_SDP3X](../advanced_config/parameter_reference.md#SENS_EN_SDP3X)
- **TE MS4525:** [SENS_EN_MS4525DO](../advanced_config/parameter_reference.md#SENS_EN_MS4525DO)
- **TE MS5525:** [SENS_EN_MS5525DS](../advanced_config/parameter_reference.md#SENS_EN_MS5525DS)
- **Eagle Tree airspeed sensor:** [SENS_EN_ETSASPD](../advanced_config/parameter_reference.md#SENS_EN_ETSASPD)
- **[Sensirion SDP3X](../modules/modules_driver_airspeed_sensor.md#sdp3x)** — [SENS_EN_SDP3X](../advanced_config/parameter_reference.md#SENS_EN_SDP3X)
- **[TE MS4525](../modules/modules_driver_airspeed_sensor.md#ms4525do)** — [SENS_EN_MS4525DO](../advanced_config/parameter_reference.md#SENS_EN_MS4525DO)
- **[TE MS5525](../modules/modules_driver_airspeed_sensor.md#ms5525dso)** — [SENS_EN_MS5525DS](../advanced_config/parameter_reference.md#SENS_EN_MS5525DS)
- **Eagle Tree airspeed sensor:** — [SENS_EN_ETSASPD](../advanced_config/parameter_reference.md#SENS_EN_ETSASPD)
- **[Amphenol All Sensors DLVR](../modules/modules_driver_airspeed_sensor.md#dlvr) (continuous-sampling sensors only)** — [SENS_EN_DLVR](../advanced_config/parameter_reference.md#SENS_EN_DLVR)
You should also check [ASPD_PRIMARY](../advanced_config/parameter_reference.md#ASPD_PRIMARY) is `1` (see next section - this is the default).
+1 -1
View File
@@ -150,7 +150,7 @@ A screenshot showing the I2C pins (SLA, SLC, GND, and VCC) is provided below.
## Hex HereFlow PMW3901 광류 센서
The Hex [HereFlow PMW3901 Optical Flow Sensor](https://docs.cubepilot.org/user-guides/flow-senor/here-flow) is a tiny board containing the PMW3901 flow module, VL53L1X distance sensor, and an IMU (used to synchronize the flow data with the gyro data).
The Hex [HereFlow PMW3901 Optical Flow Sensor](https://docs.cubepilot.org/flow-senor/here-flow) is a tiny board containing the PMW3901 flow module, VL53L1X distance sensor, and an IMU (used to synchronize the flow data with the gyro data).
An onboard microcontroller samples the three sensors and publishes two DroneCAN messages containing all the information needed for the flow and distance sensor calculations.
+1 -1
View File
@@ -52,7 +52,7 @@ To support this feature, Gazebo Classic must be launched with the appropriate RO
ROS로 래핑된 시뮬레이션을 실행하는 데 사용할 수 있는 ROS 시작 스크립트가 있습니다.
- [posix_sitl.launch](https://github.com/PX4/PX4-Autopilot/blob/main/launch/posix_sitl.launch): plain SITL launch
- [mavros_posix_sitl.launch](https://github.com/PX4/PX4-Autopilot/blob/main/launch/mavros_posix_sitl.launch): SITL and MAVROS
- [mavros_posix_sitl.launch](https://github.com/PX4/PX4-Autopilot/blob/daa89a9116ebe3ef1c173c881eb100c4b15f6d60/launch/mavros_posix_sitl.launch): SITL and MAVROS
ROS에 래핑된 SITL을 실행하려면 ROS 환경을 업데이트한 다음, 평소와 같이 시작하여야 합니다.
+2 -2
View File
@@ -6,10 +6,10 @@ This allows for more reliable flight planning notification of failure conditions
PX4는 (최소한) 다음과 같은 스마트 배터리를 지원합니다.
- [Rotoye Batmon](../smart_batteries/rotoye_batmon.md)
- [Rotoye Batmon](../smart_batteries/rotoye_batmon.md) (Discontinued)
### 추가 정보
- [Mavlink Battery Protocol](https://mavlink.io/en/services/battery.html)
- [batt_smbus](../modules/modules_driver.md) - PX4 SMBus Battery Driver docs
- [batt_smbus](../modules/modules_driver.md#batt_smbus) - PX4 SMBus Battery Driver docs
- [Safety > Low Battery Failsafe](../config/safety.md#battery-level-failsafe).
+9 -3
View File
@@ -1,6 +1,12 @@
# Rotoye Batmon
# Rotoye Batmon (Discontinued)
[Rotoye Batmon](https://shop.rotoye.com/batmon/) is a kit for adding smart battery functionality to off-the-shelf Lithium-Ion and LiPo batteries.
<Badge type="info" text="Discontinued" />
:::warning
This product appears to have been discontinued and is no longer commercially available as of 2026-08 (formerly available at shop.rotoye.com/batmon/).
:::
_Rotoye Batmon_ is a kit for adding smart battery functionality to off-the-shelf Lithium-Ion and LiPo batteries.
독립형 장치로 또는 공장에서 조립된 스마트 배터리의 일부로 구입할 수 있습니다.
![Rotoye Batmon Board](../../assets/hardware/smart_batteries/rotoye_batmon/smart-battery-rotoye.jpg)
@@ -9,7 +15,7 @@
## 구매처
[Rotoye Store](https://shop.rotoye.com/product/BATMON-v5-devkit-p480893112): Batmon kits, custom smart-batteries, and accessories
Unavailable
## Wiring/Connections
+21 -13
View File
@@ -19,7 +19,8 @@ Connect the SmartAudio or Tramp pin of the VTX to the TX pin of a free serial po
Then set the following parameters:
- `VTX_SER_CFG`: Select the serial port used for VTX communication.
- `VTX_DEVICE`: Selects the VTX device (generic SmartAudio/Tramp or a specific device).
- `VTX_PROTOCOL`: Selects the wire protocol (SmartAudio or Tramp).
- `VTX_DEVICE`: Selects the specific VTX model.
Note that since the VTX communication is half-duplex, you can, for example, use the single-pin Radio Controller port for the VTX and use a full duplex TELEM port for CRSF communication.
@@ -264,25 +265,32 @@ Key configuration options:
- `2`: MSP controls frequency, AUX controls power
- `3`: MSP controls power, AUX controls band/channel
- `4`: Not used with MSP support
- `VTX_PROTOCOL`: Wire protocol used to talk to the VTX (see below)
- `VTX_DEVICE`: Device-specific configuration (see below)
## Device-Specific Configuration
## Protocol and Device Configuration
The `VTX_DEVICE` parameter allows device-specific workarounds.
It encodes both the protocol type and device variant:
The wire protocol and the device model are configured independently.
- Low byte (bits 0-7): Protocol selection
- `0`: SmartAudio (default)
- `1`: Tramp
- High byte (bits 8-15): Device-specific variant
- `0`: Generic device
- `20`: Peak THOR T67
- `40`: Rush Max Solo
`VTX_PROTOCOL` selects the wire protocol. Set it to the protocol listed in the manual of your VTX:
| Value | Protocol |
| ----- | --------------------------------------- |
| `0` | SmartAudio v1, v2, v2.1 |
| `100` | Tramp |
`VTX_DEVICE` selects the specific VTX model and only enables device-specific workarounds. Leave at Generic unless your VTX is listed
| Value | 장치 |
| ------- | ------------- |
| `0` | Generic |
| `5120` | Peak THOR T67 |
| `10240` | Rush MAX SOLO |
Peak THOR devices speak SmartAudio and the Rush MAX SOLO speaks Tramp, so set `VTX_PROTOCOL` to match the model you select.
### Known Device Workarounds
**Peak THOR T67** (`VTX_DEVICE` = 5120):
This device incorrectly reports pit mode status but otherwise functions normally.
The driver applies a workaround to override the reported status with the actual configured state.
For generic devices, use `VTX_DEVICE` = 0 (SmartAudio) or `VTX_DEVICE` = 1 (Tramp).