diff --git a/docs/ko/SUMMARY.md b/docs/ko/SUMMARY.md index 2781c3feefa..ee4b4a7a176 100644 --- a/docs/ko/SUMMARY.md +++ b/docs/ko/SUMMARY.md @@ -666,7 +666,6 @@ - [EstimatorBias3d](msg_docs/EstimatorBias3d.md) - [EstimatorEventFlags](msg_docs/EstimatorEventFlags.md) - [EstimatorFusionControl](msg_docs/EstimatorFusionControl.md) - - [EstimatorGpsStatus](msg_docs/EstimatorGpsStatus.md) - [EstimatorInnovations](msg_docs/EstimatorInnovations.md) - [EstimatorSelectorStatus](msg_docs/EstimatorSelectorStatus.md) - [EstimatorSensorBias](msg_docs/EstimatorSensorBias.md) @@ -812,6 +811,7 @@ - [SensorTemp](msg_docs/SensorTemp.md) - [SensorUwb](msg_docs/SensorUwb.md) - [SensorsStatus](msg_docs/SensorsStatus.md) + - [SensorsStatusGnss](msg_docs/SensorsStatusGnss.md) - [SensorsStatusImu](msg_docs/SensorsStatusImu.md) - [SystemPower](msg_docs/SystemPower.md) - [TakeoffStatus](msg_docs/TakeoffStatus.md) @@ -834,6 +834,7 @@ - [VehicleConstraints](msg_docs/VehicleConstraints.md) - [VehicleControlMode](msg_docs/VehicleControlMode.md) - [VehicleGnss](msg_docs/VehicleGnss.md) + - [VehicleGnssHeading](msg_docs/VehicleGnssHeading.md) - [VehicleImu](msg_docs/VehicleImu.md) - [VehicleImuStatus](msg_docs/VehicleImuStatus.md) - [VehicleLocalPositionSetpoint](msg_docs/VehicleLocalPositionSetpoint.md) diff --git a/docs/ko/actuators/internal_combustion_engine.md b/docs/ko/actuators/internal_combustion_engine.md index d1e827d78a8..bcc2dd3b63d 100644 --- a/docs/ko/actuators/internal_combustion_engine.md +++ b/docs/ko/actuators/internal_combustion_engine.md @@ -75,8 +75,6 @@ In other words, a setpoint of `0` produces the configured **Minimum** output and :::info When the engine is commanded off, the throttle setpoint is `NAN`, which by definition drives the output to its configured **Disarmed** value rather than to **Minimum**. This lets you park the throttle servo at an idle-stop position that is different from the closed-throttle position used to switch off the engine. - -The throttle output also goes to _Disarmed_ while the engine is running if the [idle governor](#idle-rpm-governor) is disabled and the throttle demand drops to near zero (the fixed-wing controller stops the motor below 2% thrust). ::: Points to note when setting the values: diff --git a/docs/ko/advanced_config/tuning_the_ecl_ekf.md b/docs/ko/advanced_config/tuning_the_ecl_ekf.md index 297704f88c0..38d3653e63d 100644 --- a/docs/ko/advanced_config/tuning_the_ecl_ekf.md +++ b/docs/ko/advanced_config/tuning_the_ecl_ekf.md @@ -302,27 +302,24 @@ Once the vehicle has performed sufficient horizontal movement to make the yaw ob #### 이중 수신기 -Data from GPS receivers can be blended using an algorithm that weights data based on reported accuracy (this works best if both receivers output data at the same rate and use the same accuracy). -The mechanism also provides automatic failover if data from a receiver is lost (it allows, for example, a standard GPS to be used as a backup to a more accurate RTK receiver). -This is controlled by the [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) parameter. +When two GPS receivers are connected, PX4 uses the data from one of them at a time, and automatically fails over to the other if the selected receiver is lost or its fix degrades (this allows, for example, a standard GPS to be used as a backup to a more accurate RTK receiver). -The [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) parameter is set by default to disable blending and always use the first receiver, so it will have to be set to select which receiver accuracy metrics are used to decide how much each receiver output contributes to the blended solution. -Where different receiver models are used, it is important that the [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) parameter is set to a value that uses accuracy metrics that are supported by both receivers. -For example do not set bit position 0 to `true` unless the drivers for both receivers publish values in the `speed_accuracy` field of the `sensor_gnss` message that are comparable. -This can be difficult with receivers from different manufacturers due to the different way that accuracy is defined, e.g. CEP vs 1-sigma, etc. +The receiver is selected as follows: + +- The preferred receiver, set by [SENS_GNSS_PRIME](../advanced_config/parameter_reference.md#SENS_GNSS_PRIME), is used while it is publishing data and has at least a 3D fix. + By default this is the main serial GPS. +- Otherwise the receiver with the best fix type is used, and if both have the same fix type, the one using the most satellites. +- Set [SENS_GNSS_PRIME](../advanced_config/parameter_reference.md#SENS_GNSS_PRIME) to `-1` to give both receivers equal priority, so that the best one is always used. +- A receiver that has not published data for 2 seconds is not used. + +The EKF resets its horizontal position to the new receiver when the selected receiver changes. The following items should be checked during setup: - 두 번째 수신기의 데이터가 있는 지 확인합니다. This will be logged as `sensor_gnss_1` and can also be checked when connected via the _nsh console_ using the command `listener sensor_gnss -i 1`. The [GPS_2_CONFIG](../advanced_config/parameter_reference.md#GPS_2_CONFIG) parameter will need to be set correctly. -- Check the `speed_accuracy`, `eph` and `epv` data from each receiver and decide which accuracy metrics can be used. - If both receivers output sensible `speed_accuracy` and `eph` data, and GPS vertical position is not being used directly for navigation, then setting [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) to 3 is recommended. - Where only `eph` data is available and both receivers do not output `speed_accuracy` data, set [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) to 2. - Bit position 2 would only be set if the GPS had been selected as the reference height source with the [EKF2_HGT_REF](../advanced_config/parameter_reference.md#EKF2_HGT_REF) parameter and both receivers output sensible `epv` data. -- The output from the blended receiver data is logged as `vehicle_gnss`, and can be checked whilst connect via the nsh terminal using the command `listener vehicle_gnss`. -- 수신기가 다른 속도로 출력하는 경우에는 혼합 출력은 더 느린 수신기의 속도로 결정됩니다. - 가능한 경우 수신기는 동일한 속도로 출력하도록 설정하는 것이 바람직합니다. +- The data from the selected receiver is logged as `vehicle_gnss`, and can be checked whilst connected via the nsh terminal using the command `listener vehicle_gnss`. #### GNSS 성능 요구 사항 diff --git a/docs/ko/airframes/airframe_reference.md b/docs/ko/airframes/airframe_reference.md index 7d5cb4d0f75..9200ad84167 100644 --- a/docs/ko/airframes/airframe_reference.md +++ b/docs/ko/airframes/airframe_reference.md @@ -677,6 +677,10 @@ div.frame_variant td, div.frame_variant th { KTH-ATMOS Maintainer: DISCOWER

SYS_AUTOSTART = 70000

+ + KTH-ATMOS-DUAL + Maintainer: DISCOWER

SYS_AUTOSTART = 70001


Specific Outputs: + diff --git a/docs/ko/complete_vehicles_mc/crazyflie21.md b/docs/ko/complete_vehicles_mc/crazyflie21.md index 6a3c3200b12..d390a66a052 100644 --- a/docs/ko/complete_vehicles_mc/crazyflie21.md +++ b/docs/ko/complete_vehicles_mc/crazyflie21.md @@ -40,10 +40,11 @@ The vehicle can be purchased here: [Crazyflie 2.1](https://store.bitcraze.io/pro Useful peripheral hardware includes: -- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/products/crazyradio-pa): Wireless communication between _QGroundControl_ and Crazyflie 2.0 +- [Crazyradio 2.0](https://www.bitcraze.io/products/crazyradio-2-0/) 2.4 GHz USB dongle: Wireless communication between _QGroundControl_ and Crazyflie 2.0. + This behaves like the [old hardware](https://www.bitcraze.io/products/old-products/crazyradio-pa/) (anecdotally) when running its default "Crazyradio PA emulation" firmware. - [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): Breakout expansion board for connecting new peripherals. - [Flow deck v2](https://store.bitcraze.io/products/flow-deck-v2): Optical flow sensor and a distance sensor for altitude and position control. -- [Z-ranger deck v2](https://store.bitcraze.io/collections/decks/products/z-ranger-deck-v2): Distance sensor for altitude control (same sensor as the Flow deck). +- [Z-ranger deck v2](https://www.bitcraze.io/products/old-products/z-ranger-deck-v2/) (Discontinued): Distance sensor for altitude control (same sensor as the Flow deck). - [Multi-ranger deck](https://store.bitcraze.io/collections/decks/products/multi-ranger-deck) Multi-direction object detection - [Buzzer deck](https://store.bitcraze.io/collections/decks/products/buzzer-deck) Audio feedback on system events, like low battery or charging completed. - [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): Expansion board that gives you the ability to test new hardware easily without soldering. diff --git a/docs/ko/config/airspeed.md b/docs/ko/config/airspeed.md index 087bf0a1885..ac199550134 100644 --- a/docs/ko/config/airspeed.md +++ b/docs/ko/config/airspeed.md @@ -17,7 +17,10 @@ Before calibration they must be [enabled via the corresponding parameter](../adv ## 보정 절차 -항속 센서 보정 절차 +All connected airspeed sensors are calibrated in one run. +The zero reading is taken from every sensor at the same time, but you are prompted to blow into each pitot in turn. + +To calibrate the airspeed sensor(s): 1. Start _QGroundControl_ and connect the vehicle. @@ -34,7 +37,7 @@ Before calibration they must be [enabled via the corresponding parameter](../adv 6. Click **OK** to start the calibration. -7. 피톳 튜브의 끝에 입으로 바람을 불어 보정 완료 신호를 보냅니다. +7. Once asked for, blow into the tip of each pitot tube to signal the end of its calibration. :::tip Blowing into the tube is also a basic check that the dynamic and static ports are installed correctly. diff --git a/docs/ko/config/safety.md b/docs/ko/config/safety.md index 5bb7de374c5..1777040e9a3 100644 --- a/docs/ko/config/safety.md +++ b/docs/ko/config/safety.md @@ -154,6 +154,7 @@ This is intended for operations where a switch to Hold on manual control loss is If Hold cannot be entered (for example without a valid position estimate), the normal failsafe takes over and escalates from there (Return, Land, Descend, or Terminate as applicable). Manual control loss in any non-manual (auto/offboard) mode is ignored with this setting. +If another failsafe would fall back to a manual mode while manual control is lost, for example an Offboard loss with [COM_OBL_RC_ACT](../advanced_config/parameter_reference.md#COM_OBL_RC_ACT) set to Position mode, the vehicle switches to Hold instead. ## 데이터 연결불량 안전장치 @@ -278,14 +279,19 @@ Triggers on either of: - **Count drop**: receivers with a 3D fix drop below [SYS_HAS_NUM_GNSS](#SYS_HAS_NUM_GNSS). No failsafe action when `SYS_HAS_NUM_GNSS=0` (default). - **Position divergence**: two receivers disagree beyond their expected separation (configured via [SENS_GNSS0_OFFX/Y](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFX), [SENS_GNSS1_OFFX/Y](../advanced_config/parameter_reference.md#SENS_GNSS1_OFFX)) plus reported accuracy. Only triggers a failsafe action if `SYS_HAS_NUM_GNSS=2`. + Receivers might report an optimistic accuracy, so the reported accuracy of each receiver is floored with [EKF2_GPS_P_NOISE](../advanced_config/parameter_reference.md#EKF2_GPS_P_NOISE). At least a warning is emitted, additional failsafe actions can be configured using [COM_GNSSLOSS_ACT](#COM_GNSSLOSS_ACT). Loss of a single GPS when none are required is handled by other GPS health checks. -| Parameter | 설명 | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| [SYS_HAS_NUM_GNSS](../advanced_config/parameter_reference.md#SYS_HAS_NUM_GNSS) | Number of usable GNSS receivers required for arming. If two are required then they also need to be consistent. | -| [COM_GNSSLOSS_ACT](../advanced_config/parameter_reference.md#COM_GNSSLOSS_ACT) | Failsafe action when a GNSS failure is detected in flight. | +When `COM_GNSSLOSS_ACT` is set to `Warning`, both triggers produce a warning only and never block arming. +When set to `Warning, block arming`, both triggers block arming and only produce a warning in flight. +When set to `Return`, `Land`, or `Terminate`, both triggers block arming and fire the configured in-flight failsafe action (subject to the `SYS_HAS_NUM_GNSS` condition above). + +| Parameter | 설명 | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [SYS_HAS_NUM_GNSS](../advanced_config/parameter_reference.md#SYS_HAS_NUM_GNSS) | Number of usable GNSS receivers required. If two are required then they also need to be consistent. | +| [COM_GNSSLOSS_ACT](../advanced_config/parameter_reference.md#COM_GNSSLOSS_ACT) | Failsafe action when a GNSS failure is detected. `0`: Warning only (default), `1`: Return, `2`: Land, `3`: Terminate, `4`: Warning, block arming. Values above Warning also block arming. | ## 오프 보드 안전 장치 diff --git a/docs/ko/config_fw/airspeed_scale_handling.md b/docs/ko/config_fw/airspeed_scale_handling.md index 02f745fc72b..f2296b0a602 100644 --- a/docs/ko/config_fw/airspeed_scale_handling.md +++ b/docs/ko/config_fw/airspeed_scale_handling.md @@ -5,7 +5,11 @@ This section complements the existing [Airspeed Validation](../advanced_config/a ::: The airspeed scale is used by PX4 to convert the measured airspeed (indicated airspeed) to the calibrated airspeed. -This scale can be set by [ASPD_SCALE_n](../advanced_config/parameter_reference.md#ASPD_SCALE_1) (where `n` is the sensor number), and logged in [AirspeedWind.msg](../msg_docs/AirspeedWind.md). +This scale can be set by [ASPD_SCALE_n](../advanced_config/parameter_reference.md#ASPD_SCALE_1), and logged in [AirspeedWind.msg](../msg_docs/AirspeedWind.md). + +`n` identifies the sensor by its calibration entry: `ASPD_SCALE_1` belongs to the sensor recorded in `CAL_DPRES0_ID`, `ASPD_SCALE_2` to `CAL_DPRES1_ID`, and so on. +With a single airspeed sensor this is always `ASPD_SCALE_1`. +See [Multiple Airspeed Sensors](../sensor/airspeed.md#multiple-airspeed-sensors) if you have more than one. Note that the airspeed scale is different from the airspeed sensor offset calibration done on the ground at 0 m/s. The airspeed scale accounts for errors in the airspeed measurement during flight, such as those caused by sensor placement or installation effects. diff --git a/docs/ko/config_fw/position_tuning_guide_fixedwing.md b/docs/ko/config_fw/position_tuning_guide_fixedwing.md index 86c3dc21bb1..8b412ccca6f 100644 --- a/docs/ko/config_fw/position_tuning_guide_fixedwing.md +++ b/docs/ko/config_fw/position_tuning_guide_fixedwing.md @@ -51,6 +51,9 @@ the maximum allowed airspeed. - [FW_THR_MIN](../advanced_config/parameter_reference.md#FW_THR_MIN) - set to the minimum throttle the plane should fly at. - [FW_AIRSPD_MAX](../advanced_config/parameter_reference.md#FW_AIRSPD_MAX) - set to the maximum airspeed you achieved during level flight at `FW_THR_MAX`. +TECS accelerates above trim airspeed with throttle only, rather than by descending (see [Speed and Altitude Weighting](../flight_stack/controller_diagrams.md#speed-and-altitude-weighting)). +If `FW_AIRSPD_MAX` is set higher than the vehicle can reach in level flight at `FW_THR_MAX`, it will hold altitude and fly slower than commanded. + #### 3rd: Pitch & Climb Rate Limits :::warning diff --git a/docs/ko/config_fw/trimming_guide_fixedwing.md b/docs/ko/config_fw/trimming_guide_fixedwing.md index 14db6622826..de9d3859d32 100644 --- a/docs/ko/config_fw/trimming_guide_fixedwing.md +++ b/docs/ko/config_fw/trimming_guide_fixedwing.md @@ -17,8 +17,8 @@ The [Advanced Trimming](#advanced-trimming) section introduces parameters that c These parameters are set automatically during [RC calibration](../config/radio.md). - [CA_SV_CSx_TRIM](../advanced_config/parameter_reference.md#CA_SV_CS0_TRIM) applies trim to a control surfaces channel. 이들은 비행 전에 제어 표면을 기본 각도로 미세하게 정렬하는 데 사용됩니다. -- [FW_PSP_OFF](../advanced_config/parameter_reference.md#FW_PSP_OFF) applies an offset to the pitch setpoint. - 항공기가 순항 속도로 비행해야하는 공격 각도를 설정하는 데 사용됩니다. +- [FW_PSP_OFF](../advanced_config/parameter_reference.md#FW_PSP_OFF) is the pitch angle at which your aircraft flies level at trim airspeed. + See [Level-Flight Pitch](#level-flight-pitch) for how PX4 defines and uses it. - [FW_AIRSPD_TRIM](../advanced_config/parameter_reference.md#FW_AIRSPD_TRIM) is used by the rate controllers to scale their output depending on the measured airspeed. See [Airspeed Scaling](../flight_stack/controller_diagrams.md#airspeed-scaling) for more details. - [TRIM_ROLL](../advanced_config/parameter_reference.md#TRIM_ROLL), [TRIM_PITCH](../advanced_config/parameter_reference.md#TRIM_PITCH) and [TRIM_YAW](../advanced_config/parameter_reference.md#TRIM_YAW) apply trim to the control signals _before_ mixing. @@ -28,8 +28,7 @@ The [Advanced Trimming](#advanced-trimming) section introduces parameters that c 위의 매개 변수를 설정하는 올바른 순서는 다음과 같습니다. 1. Trim the servos by physically adjusting the linkages lengths if possible and fine tune by trimming the PWM channels (use `PWM_MAIN/AUX_TRIMx`) on the bench to properly set the control surfaces to their theoretical position. -2. Fly in stabilized mode at cruise speed and set the pitch setpoint offset (`FW_PSP_OFF`) to desired angle of attack. - 순항 속도에서 필요한 공격 각도는 날개 높이 비행 중에 일정한 고도를 유지하기 위해 비행기가 비행해야 하는 피치 각도에 해당합니다. +2. Fly in stabilized mode at cruise speed and set `FW_PSP_OFF` to the pitch angle that the airplane needs to fly at in order to keep constant altitude during wing-leveled flight. If you are using an airspeed sensor, also set the correct cruise airspeed (`FW_AIRSPD_TRIM`). 3. Look at the actuator controls in the log file (upload it to [Flight Review](https://logs.px4.io) and check the _Actuator Controls_ plot for example) and set the pitch trim (`TRIM_PITCH`). 이 값을 수평 비행 중의 피치 신호의 평균 오프셋으로 설정합니다. @@ -37,6 +36,30 @@ The [Advanced Trimming](#advanced-trimming) section introduces parameters that c 로그 조회가 필요가 없거나 수동 모드에서 편안하게 비행 할 수있는 경우 2 단계 전에 3 단계를 수행할 수 있습니다. You can then trim your remote (with the trim switches) and report the values to `TRIM_PITCH` (and remove the trims from your transmitter) or update `TRIM_PITCH` directly during flight via telemetry and QGC. +## Level-Flight Pitch + +PX4 measures the fixed-wing pitch angle θ between the body x-axis and the horizon. +The body frame is fixed to the vehicle: x points forward through the nose, y along the right wing and z down. +Its orientation follows the mounting of the flight controller (see [Flight Controller Orientation](../config/flight_controller_orientation.md)), not the wing chord. +For tailsitters, the fixed-wing body frame is the multicopter body frame rotated by 90° in pitch. + +![Side view of a fixed-wing aircraft pitched up: the body x-axis points forward, z down and y along the right wing out of the page; the pitch angle θ is the angle between the body x-axis and the horizon, and in level flight at trim airspeed it equals FW_PSP_OFF](../../assets/config/fw/fw_pitch_angle_definition.svg) + +[FW_PSP_OFF](../advanced_config/parameter_reference.md#FW_PSP_OFF) is θ in level flight at trim airspeed ([FW_AIRSPD_TRIM](../advanced_config/parameter_reference.md#FW_AIRSPD_TRIM)). +In level flight the velocity is horizontal, so this is also the angle of attack measured from the body x-axis. +It differs from the angle of attack of the wing by the angle between the wing chord and the body x-axis. + +Pitch setpoints and pitch limits in PX4 are absolute pitch angles θ, and `FW_PSP_OFF` is not added to them. +This applies for example to [FW_P_LIM_MIN](../advanced_config/parameter_reference.md#FW_P_LIM_MIN), [FW_P_LIM_MAX](../advanced_config/parameter_reference.md#FW_P_LIM_MAX), [FW_TKO_PITCH_MIN](../advanced_config/parameter_reference.md#FW_TKO_PITCH_MIN), [FW_LND_FL_PMIN](../advanced_config/parameter_reference.md#FW_LND_FL_PMIN), [FW_LND_FL_PMAX](../advanced_config/parameter_reference.md#FW_LND_FL_PMAX) and [RWTO_PSP](../advanced_config/parameter_reference.md#RWTO_PSP). + +`FW_PSP_OFF` itself is used in these places: + +- The altitude and airspeed controller (TECS) uses `FW_PSP_OFF` as the pitch at zero climb angle: its pitch setpoint is `FW_PSP_OFF` plus the commanded climb angle plus an integrator correction. + The logged TECS pitch setpoint (`tecs_status.pitch_sp_rad`) is absolute, while the logged pitch integrator (`tecs_status.pitch_integ`) is a correction added to it rather than a pitch angle. +- In [Stabilized mode](../flight_modes_fw/stabilized.md), the centred pitch stick commands `FW_PSP_OFF`. +- During the front transition, standard VTOLs ramp their pitch setpoint to `FW_PSP_OFF`, and tailsitters end their pitch-down rotation at it. +- The first principle check of the [airspeed validation](../advanced_config/airspeed_validation.md) considers the vehicle to be pitching down when θ is below `FW_PSP_OFF`. + ## 고급 트리밍 비대칭 익형에 의해 유도된 하향 피치 모멘트는 대기 속도에 따라 증가하고 플랩이 전개 될 때 현재 측정된 대기 속도와 플랩 위치에 따라 항공기를 다시 트리밍하여야 합니다. diff --git a/docs/ko/dev_setup/dev_env_mac.md b/docs/ko/dev_setup/dev_env_mac.md index a88e736bf25..87c474746ee 100644 --- a/docs/ko/dev_setup/dev_env_mac.md +++ b/docs/ko/dev_setup/dev_env_mac.md @@ -89,7 +89,7 @@ To build for [other targets](../dev_setup/dev_env.md#supported-targets) you will The `--sim-tools` flag installs Gazebo and the libraries PX4's simulation modules build against. Gazebo does not come from Homebrew. -The script installs it from a locked [conda-forge](https://conda-forge.org/) environment, using [pixi](https://pixi.sh), into `Tools/setup/macos/.pixi`. +The script installs it from a locked [conda-forge](https://conda-forge.org/) environment, using [pixi](https://pixi.prefix.dev/latest/), into `Tools/setup/macos/.pixi`. The lock file pins every package, so the install does not change when Homebrew updates its own Gazebo dependencies. The build and the `make px4_sitl gz_*` targets find it on their own, like the `.venv`. Activating `.venv` also puts it on your `PATH`, which you only need to run `gz` commands directly. diff --git a/docs/ko/dronecan/ark_rtk_gps.md b/docs/ko/dronecan/ark_rtk_gps.md index cc704c78559..63ac0ac147d 100644 --- a/docs/ko/dronecan/ark_rtk_gps.md +++ b/docs/ko/dronecan/ark_rtk_gps.md @@ -83,7 +83,6 @@ GPS data should arrive at 10Hz. You need to set necessary [DroneCAN](index.md) parameters and define offsets if the sensor is not centred within the vehicle: - Enable GPS yaw fusion by setting bit 3 of [EKF2_GPS_CTRL](../advanced_config/parameter_reference.md#EKF2_GPS_CTRL) to true. -- Enable GPS blending to ensure the heading is always published by setting [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) to 7 (all three bits checked). - If using [Moving Baseline & GPS Heading](#setting-up-moving-baseline-gps-heading), set [SENS_GNSS_PRIME](../advanced_config/parameter_reference.md#SENS_GNSS_PRIME) to the CAN node ID of the _Moving Base_ module. The moving base is preferred because the rover receiver in a moving baseline configuration can experience degraded navigation rate and increased data latency when corrections are intermittent. - Enable [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS), [UAVCAN_SUB_MAG](../advanced_config/parameter_reference.md#UAVCAN_SUB_MAG), and [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO). - The parameters [SENS_GNSS0_OFFX](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFX), [SENS_GNSS0_OFFY](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFY) and [SENS_GNSS0_OFFZ](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFZ) can be set to account for the offset of the ARK RTK GPS from the vehicles centre of gravity. diff --git a/docs/ko/dronecan/ark_rtk_gps_l1_l2.md b/docs/ko/dronecan/ark_rtk_gps_l1_l2.md index 79f0625c2eb..177a47cd094 100644 --- a/docs/ko/dronecan/ark_rtk_gps_l1_l2.md +++ b/docs/ko/dronecan/ark_rtk_gps_l1_l2.md @@ -83,7 +83,6 @@ GPS data should arrive at 10Hz. You need to set necessary [DroneCAN](index.md) parameters and define offsets if the sensor is not centred within the vehicle: - Enable GPS yaw fusion by setting bit 3 of [EKF2_GPS_CTRL](../advanced_config/parameter_reference.md#EKF2_GPS_CTRL) to true. -- Enable GPS blending to ensure the heading is always published by setting [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) to 7 (all three bits checked). - Enable [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS), [UAVCAN_SUB_MAG](../advanced_config/parameter_reference.md#UAVCAN_SUB_MAG), and [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO). - The parameters [SENS_GNSS0_OFFX](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFX), [SENS_GNSS0_OFFY](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFY) and [SENS_GNSS0_OFFZ](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFZ) can be set to account for the offset of the ARK RTK GPS L1 L5 from the vehicles centre of gravity. diff --git a/docs/ko/dronecan/ark_x20_rtk_gps.md b/docs/ko/dronecan/ark_x20_rtk_gps.md index 42798152f8c..4ad305eadc5 100644 --- a/docs/ko/dronecan/ark_x20_rtk_gps.md +++ b/docs/ko/dronecan/ark_x20_rtk_gps.md @@ -86,7 +86,6 @@ GPS data should arrive at 10Hz. You need to set necessary [DroneCAN](index.md) parameters and define offsets if the sensor is not centred within the vehicle: - Enable GPS yaw fusion by setting bit 3 of [EKF2_GPS_CTRL](../advanced_config/parameter_reference.md#EKF2_GPS_CTRL) to true. -- Enable GPS blending to ensure the heading is always published by setting [SENS_GNSS_MASK](../advanced_config/parameter_reference.md#SENS_GNSS_MASK) to 7 (all three bits checked). - Enable [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS), [UAVCAN_SUB_MAG](../advanced_config/parameter_reference.md#UAVCAN_SUB_MAG), and [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO). - The parameters [SENS_GNSS0_OFFX](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFX), [SENS_GNSS0_OFFY](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFY) and [SENS_GNSS0_OFFZ](../advanced_config/parameter_reference.md#SENS_GNSS0_OFFZ) can be set to account for the offset of the ARK X20 RTK GPS from the vehicles centre of gravity. diff --git a/docs/ko/flight_modes/return.md b/docs/ko/flight_modes/return.md index fc816f530c1..6899deb25bf 100644 --- a/docs/ko/flight_modes/return.md +++ b/docs/ko/flight_modes/return.md @@ -115,7 +115,7 @@ The behaviour is fairly complex because it depends on the flight mode, and wheth ::: :::warning -This return type does have [geofence awareness](#geofence_awareness) (at any stage). +This return type does not have [geofence awareness](#geofence_awareness) (at any stage). ::: Mission _with_ landing pattern: @@ -255,8 +255,10 @@ The figures below show an exclusion zone and an inclusion zone. ### Geofence Limitations -- Geofence awareness currently supports a maximum of 99 polygon vertices in total (circles count as 8 vertices each). - If this limit is exceeded, the autopilot falls back to a direct path as described above. +- The size of geofence that can be handled is limited by [GF_AVOID_NODES](../advanced_config/parameter_reference.md#GF_AVOID_NODES) (default 100, maximum 200, reboot required). + Each circle counts as 8 nodes, and each polygon counts as its number of vertices plus extra nodes for sharp corners. + If the geofence needs more nodes than configured, the autopilot falls back to a direct path as described above. + Setting the parameter to 0 disables geofence awareness in Return entirely. - The autopilot does not check at upload time whether every part of the allowed area is still reachable once the [safety margin](#shortest-path-calculation) has been applied. A region can be "cut off" by the margin — for example where several exclusion zones overlap — without any error being reported when the geofence is uploaded. The error is only reported when a return is triggered and no feasible path can be found, at which point the vehicle falls back to flying directly to the destination. @@ -267,6 +269,14 @@ The figures below show an exclusion zone and an inclusion zone. It is derived from [NAV_LOITER_RAD](../advanced_config/parameter_reference.md#NAV_LOITER_RAD) for fixed-wing and VTOL vehicles, and from twice [NAV_ACC_RAD](../advanced_config/parameter_reference.md#NAV_ACC_RAD) for multicopters. It is not directly configurable. +### Geofence Awareness Messages + +The following messages are reported to the ground station and stored in the flight log, and can help you understand how a return was flown: + +- `Return: avoiding geofence` (info): The return started on a geofence-aware path. +- `Return: no geofence avoidance path; flying directly` (critical): The return started, but no feasible geofence-aware path was found, so the vehicle flies directly to the destination. +- `Geofence too large for Return avoidance (needs N of M nodes), Return will fly directly` (warning): Reported when the geofence is uploaded or the safety margin changes, if the geofence needs more nodes than [GF_AVOID_NODES](../advanced_config/parameter_reference.md#GF_AVOID_NODES) allows. + ## 목적지에 호버링/착륙 For most [return types](#return_types) a vehicle will ascend to a _minimum safe altitude_ before returning (unless already above that altitude), in order to avoid any obstacles between it and the destination. diff --git a/docs/ko/flight_modes_fw/mission.md b/docs/ko/flight_modes_fw/mission.md index 68d8264ee61..6f33662c43a 100644 --- a/docs/ko/flight_modes_fw/mission.md +++ b/docs/ko/flight_modes_fw/mission.md @@ -156,6 +156,8 @@ Mission Items: - [MAV_CMD_DO_JUMP](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_JUMP) - _Param1_ (sequence number) must refer to an earlier mission item. A mission is rejected if a jump targets itself or a later item, even if its repeat count is 0. + - _Param2_ (repeat count) must be from 0 to 65535. + A mission with a negative or larger repeat count is rejected. - [MAV_CMD_NAV_ROI](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_ROI) - [MAV_CMD_DO_SET_ROI](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_ROI) - [MAV_CMD_DO_SET_ROI_LOCATION](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_ROI_LOCATION) @@ -328,6 +330,10 @@ Flaring consists of a switch from altitude tracking to a shallow sink rate setpo The flaring altitude is calculated during the final approach via "time-to-impact" ([FW_LND_FL_TIME](#FW_LND_FL_TIME)) and the approach descent rate. An additional safety parameter [FW_LND_FLALT](#FW_LND_FLALT) sets the minimum altitude at which the vehicle will flare (if the time based altitude is too low to allow a safe flare maneuver). +The flare can be disabled by setting either [FW_LND_FL_TIME](#FW_LND_FL_TIME) or [FW_LND_FLALT](#FW_LND_FLALT) to -1. +The vehicle then keeps tracking the landing slope at the landing airspeed ([FW_LND_AIRSPD](../advanced_config/parameter_reference.md#FW_LND_AIRSPD), or [FW_AIRSPD_MIN](../advanced_config/parameter_reference.md#FW_AIRSPD_MIN) if not set) until touchdown. +In this case also set [FW_LND_USETER](#FW_LND_USETER) to `0`, otherwise the landing may abort just before touchdown when the distance sensor stops giving valid readings close to the ground. + If belly landing, the vehicle will continue in the flaring state until touchdown, land detection, and subsequent disarm. For runway landings, [FW_LND_TD_TIME](#FW_LND_TD_TIME) enables setting the time post flare start to pitch down the nose (e.g. consider tricycle gear) onto the runway ([RWTO_PSP](#RWTO_PSP)) and avoid bouncing. This time roughly corresponds to the touchdown post flare, and should be tuned for a given airframe during test flights only after the flare has been tuned. The parameters that affect flaring are listed below. diff --git a/docs/ko/flight_modes_mc/mission.md b/docs/ko/flight_modes_mc/mission.md index df5646748a1..76c22200192 100644 --- a/docs/ko/flight_modes_mc/mission.md +++ b/docs/ko/flight_modes_mc/mission.md @@ -158,6 +158,8 @@ Mission Items: - [MAV_CMD_DO_JUMP](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_JUMP) - _Param1_ (sequence number) must refer to an earlier mission item. A mission is rejected if a jump targets itself or a later item, even if its repeat count is 0. + - _Param2_ (repeat count) must be from 0 to 65535. + A mission with a negative or larger repeat count is rejected. - [MAV_CMD_NAV_ROI](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_ROI) - [MAV_CMD_DO_SET_ROI](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_ROI) - [MAV_CMD_DO_SET_ROI_LOCATION](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_ROI_LOCATION) diff --git a/docs/ko/flight_modes_rover/index.md b/docs/ko/flight_modes_rover/index.md index 58c3df51cd1..12a176b4c3c 100644 --- a/docs/ko/flight_modes_rover/index.md +++ b/docs/ko/flight_modes_rover/index.md @@ -26,3 +26,14 @@ Selecting any other mode than those listed below will either stop the rover or c | ------------------------------- | --------------------------------------------------------------------------------------- | | [Mission](auto.md#mission-mode) | Automatic mode that causes the vehicle to execute a predefined mission. | | [Return](auto.md#return-mode) | Automatic mode that returns the vehicle to the launch position. | + +## Failsafe Fallback Sequence + +If a rover loses navigation while in an autonomous or semi-autonomous mode that relies on it, such as losing GNSS while in **Position** mode, PX4 will fall back to the mode that maintains the most control given the (remaining) available sensor information. + +The failure cascade sequence with a manual controller available is: **Position -> Stabilized -> Acro -> Manual** + +If manual control input is not available, the fallback cascade continues to: **Hold -> RTL -> Disarm** + +Note that rovers will not use unsupported multicopter modes, such as Altitude or Descend. +If the failsafe system attempts to force the rover into an unsupported `Descend` state, the rover will safely bypass termination and automatically fall back to the action defined by the `COM_POS_FS_ACT` parameter. diff --git a/docs/ko/flight_stack/controller_diagrams.md b/docs/ko/flight_stack/controller_diagrams.md index 1b4c10d330f..80b1666245b 100644 --- a/docs/ko/flight_stack/controller_diagrams.md +++ b/docs/ko/flight_stack/controller_diagrams.md @@ -140,11 +140,15 @@ $$E_T = \frac{1}{2} m V_T^2 + m g h$$ $$\dot{E_T} = m V_T \dot{V_T} + m g \dot{h}$$ -이로부터 특정 에너지율은 다음과 같습니다. +Dividing by the mass gives the specific (per unit mass) total energy rate, in m²/s³: -$$\dot{E} = \frac{\dot{E_T}}{mgV_T} = \frac{\dot{V_T}}{g} + \frac{\dot{h}}{V_T} = \frac{\dot{V_T}}{g} + sin(\gamma)$$ +$$\dot{E_s} = \frac{\dot{E_T}}{m} = V_T \dot{V_T} + g \dot{h}$$ -여기서 $\gamma{}$는 비행 계획 각도입니다. +Dividing it further by $g V_T{}$ gives the normalised energy rate, which is dimensionless: + +$$\dot{E} = \frac{\dot{E_s}}{g V_T} = \frac{\dot{V_T}}{g} + \frac{\dot{h}}{V_T} = \frac{\dot{V_T}}{g} + sin(\gamma)$$ + +where $\gamma{}$ is the flight path angle. 작은 $\gamma{}$의 경우 다음과 같이 근사할 수 있습니다. $$\dot{E} \approx \frac{\dot{V_T}}{g} + \gamma$$ @@ -160,9 +164,41 @@ $$\Delta T = mg(\frac{\dot{V_T}}{g} + \gamma)$$ 보시다시피 $\Delta T{}$는 $\dot{E}{}$에 비례하므로, 추력 설정값을 전체 에너지 제어에 사용합니다. -반면에 엘리베이터 제어는 에너지를 보존하므로, 위치 에너지를 운동 에너지로 또는 그 반대로 전환합니다. 이를 위하여, 특정 에너지 균형 비율은 다음과 같이 정의합니다. +Elevator control on the other hand is energy conservative, and is thus used for exchanging potential energy for kinetic energy and vice versa. +To this end, the specific energy balance rate is defined as: -$$\dot{B} = \gamma - \frac{\dot{V_T}}{g}$$ +$$\dot{B_s} = g \dot{h} - V_T \dot{V_T}$$ + +and its normalised form as: + +$$\dot{B} = \frac{\dot{B_s}}{g V_T} \approx \gamma - \frac{\dot{V_T}}{g}$$ + +TECS computes the energy rates in their specific form (m²/s³). +It only converts the energy balance rate to its normalised form, an equivalent flight path angle, when forming the pitch setpoint. + +#### Speed and Altitude Weighting + +[FW_T_SPDWEIGHT](../advanced_config/parameter_reference.md#FW_T_SPDWEIGHT) sets how the pitch loop weights speed errors against height errors in the energy balance. +A value of 0 controls height only, which is also used when flying without an airspeed sensor. +A value of 2 controls speed only, which is intended for gliders. +The default of 1 weights both equally. + +Pitch only trades altitude for speed up to the trim airspeed ([FW_AIRSPD_TRIM](../advanced_config/parameter_reference.md#FW_AIRSPD_TRIM)): accelerating beyond trim is the throttle's job. +With an airspeed setpoint above trim, what the pitch loop does therefore depends on the measured airspeed: + +![Pitch and throttle roles along the measured airspeed: below trim, pitch trades height for speed aiming for trim; between trim and the airspeed setpoint, pitch holds height only and the throttle accelerates; above the setpoint, pitch trades speed for height and the throttle is reduced](../../assets/diagrams/tecs_speed_regions.svg) + +- Below trim, pitch trades height for speed, but only aims for trim airspeed. +- Between trim and the setpoint, pitch ignores airspeed and holds height only. + It neither descends to gain speed nor pitches up to turn the throttle's acceleration into height. + If the throttle saturates at [FW_THR_MAX](../advanced_config/parameter_reference.md#FW_THR_MAX), the vehicle holds its altitude and settles at a lower airspeed than commanded. +- Above the setpoint, pitch trades speed for height to correct the overspeed. + +With an airspeed setpoint at or below trim there is no middle region, and pitch and throttle share speed control as weighted by `FW_T_SPDWEIGHT`. + +These regions apply up to a speed weight of 1 and are faded out as the speed weight goes from 1 to 2, so with a weight of 2 pitch alone tracks the full airspeed setpoint. +Gliders, which have no throttle to accelerate with, should therefore use `FW_T_SPDWEIGHT` = 2. +The speed weight is also raised towards 2 automatically during underspeed recovery and fast descend, which therefore still use pitch to reach their airspeed setpoint. ## 고정익 자세 콘트롤러 diff --git a/docs/ko/gps_compass/index.md b/docs/ko/gps_compass/index.md index 1a35318018b..3c5b95a7292 100644 --- a/docs/ko/gps_compass/index.md +++ b/docs/ko/gps_compass/index.md @@ -160,8 +160,8 @@ The following steps show how to configure a secondary GPS on the `GPS 2` port in 보조 GPS 포트를 설정 후 : -1. 두 GPS 시스템의 데이터를 혼합하도록 ECL/EKF2 추정기를 설정합니다. - For detailed instructions see: [Using the ECL EKF > Dual Receivers](../advanced_config/tuning_the_ecl_ekf.md#dual-receivers). +1. Optionally set which receiver is preferred using [SENS_GNSS_PRIME](../advanced_config/parameter_reference.md#SENS_GNSS_PRIME). + For more information see: [Using the ECL EKF > Dual Receivers](../advanced_config/tuning_the_ecl_ekf.md#dual-receivers). ### DroneCAN GNSS Configuration diff --git a/docs/ko/mavlink/standard_modes.md b/docs/ko/mavlink/standard_modes.md index e493dcbbd5d..5b47d3091c8 100644 --- a/docs/ko/mavlink/standard_modes.md +++ b/docs/ko/mavlink/standard_modes.md @@ -118,12 +118,9 @@ PX4 supports these commands for changing modes on some vehicle types: - [MAV_CMD_NAV_TAKEOFF](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_TAKEOFF) — Takeoff mode - [MAV_CMD_NAV_RETURN_TO_LAUNCH](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_RETURN_TO_LAUNCH) — Return mode - [MAV_CMD_NAV_LAND](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_LAND) — Land mode -- [MAV_CMD_DO_FOLLOW](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_FOLLOW) — MC Follow mode -- [MAV_CMD_DO_FOLLOW_REPOSITION](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_FOLLOW_REPOSITION) — Follow mode (from new position) - [MAV_CMD_DO_ORBIT](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_ORBIT) — MC Orbit mode - [MAV_CMD_NAV_VTOL_TAKEOFF](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_VTOL_TAKEOFF) — VTOL specific takeoff mode - [MAV_CMD_DO_REPOSITION](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_REPOSITION) -- [MAV_CMD_DO_PAUSE_CONTINUE](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_PAUSE_CONTINUE) — Pauses a mission by putting the vehicle into Hold/Loiter - [MAV_CMD_MISSION_START](https://mavlink.io/en/messages/common.html#MAV_CMD_MISSION_START) — Starts a mission. Note that these commands predate "standard modes" and are mapped to vehicle-specific custom modes. diff --git a/docs/ko/middleware/uorb.md b/docs/ko/middleware/uorb.md index 762d5cb2c06..c26e9dfe21b 100644 --- a/docs/ko/middleware/uorb.md +++ b/docs/ko/middleware/uorb.md @@ -187,6 +187,9 @@ A subscriber will then have to choose to which instance to subscribe to using `o Make sure not to mix `orb_advertise_multi` and `orb_advertise` for the same topic! +Destroying a `uORB::PublicationMulti` frees its instance for the next publisher. +Destroying a `uORB::Publication` leaves the topic advertised with its last sample, because other publishers may share it. + The full API is documented in [platforms/common/uORB/uORBManager.hpp](https://github.com/PX4/PX4-Autopilot/blob/main/platforms/common/uORB/uORBManager.hpp). ## 토픽 나열 및 듣기 diff --git a/docs/ko/msg_docs/AirspeedValidated.md b/docs/ko/msg_docs/AirspeedValidated.md index 47c3a4cd530..60df20acd4e 100644 --- a/docs/ko/msg_docs/AirspeedValidated.md +++ b/docs/ko/msg_docs/AirspeedValidated.md @@ -24,7 +24,7 @@ Used by controllers, estimators and for airspeed reporting to operator. | calibraded_airspeed_synth_m_s | `float32` | m/s | | Synthetic airspeed (Invalid: NaN) | | airspeed_derivative_filtered | `float32` | m/s^2 | | Filtered indicated airspeed derivative | | throttle_filtered | `float32` | | | Filtered fixed-wing throttle | -| pitch_filtered | `float32` | rad | | Filtered pitch | +| pitch_filtered | `float32` | rad | | Filtered absolute pitch angle of the fixed-wing body x-axis above the horizon | ## Enums @@ -80,7 +80,7 @@ float32 calibrated_ground_minus_wind_m_s # [m/s] [@invalid NaN] CAS calculated f float32 calibraded_airspeed_synth_m_s # [m/s] [@invalid NaN] Synthetic airspeed float32 airspeed_derivative_filtered # [m/s^2] Filtered indicated airspeed derivative float32 throttle_filtered # [-] Filtered fixed-wing throttle -float32 pitch_filtered # [rad] Filtered pitch +float32 pitch_filtered # [rad] Filtered absolute pitch angle of the fixed-wing body x-axis above the horizon ``` ::: diff --git a/docs/ko/msg_docs/FailsafeFlags.md b/docs/ko/msg_docs/FailsafeFlags.md index c1a1273a08a..c92e15d1983 100644 --- a/docs/ko/msg_docs/FailsafeFlags.md +++ b/docs/ko/msg_docs/FailsafeFlags.md @@ -30,6 +30,7 @@ The flag comments are used as label for the failsafe state machine simulation | mode_req_prevent_arming | `uint32` | | | if set, cannot arm while in this mode | | mode_req_manual_control | `uint32` | | | | | mode_req_other | `uint32` | | | other requirements, not covered above (for external modes) | +| mode_not_supported | `uint32` | | | if set, mode is not supported by the current vehicle architecture | | angular_velocity_invalid | `bool` | | | Angular velocity invalid | | attitude_invalid | `bool` | | | Attitude invalid | | local_altitude_invalid | `bool` | | | Local altitude invalid | @@ -93,7 +94,7 @@ uint32 mode_req_wind_and_flight_time_compliance # if set, mode cannot be entered uint32 mode_req_prevent_arming # if set, cannot arm while in this mode uint32 mode_req_manual_control uint32 mode_req_other # other requirements, not covered above (for external modes) - +uint32 mode_not_supported # if set, mode is not supported by the current vehicle architecture # Mode requirements bool angular_velocity_invalid # Angular velocity invalid diff --git a/docs/ko/msg_docs/FixedWingLongitudinalSetpoint.md b/docs/ko/msg_docs/FixedWingLongitudinalSetpoint.md index 9f6d55c5624..84677a1e245 100644 --- a/docs/ko/msg_docs/FixedWingLongitudinalSetpoint.md +++ b/docs/ko/msg_docs/FixedWingLongitudinalSetpoint.md @@ -9,19 +9,20 @@ Fixed Wing Longitudinal Setpoint message. Used by the fw_lateral_longitudinal_control module If pitch_direct and throttle_direct are not both finite, then the controller relies on altitude/height_rate and equivalent_airspeed to control vertical motion. If both altitude and height_rate are NAN, the controller maintains the current altitude. +Pitch angles are absolute: the angle of the fixed-wing body x-axis above the horizon, without FW_PSP_OFF applied. **TOPICS:** fixed_wing_longitudinal_setpoint ## Fields -| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | -| ---------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- | -| timestamp | `uint64` | us | | Time since system start | -| altitude | `float32` | m | | Altitude setpoint AMSL, not controlled directly if NAN or if height_rate is finite | -| height_rate | `float32` | m/s [ENU] | | Scalar height rate setpoint. NAN if not controlled directly | -| equivalent_airspeed | `float32` | m/s | [0 : inf] | Scalar equivalent airspeed setpoint. NAN if system default should be used | -| pitch_direct | `float32` | rad [FRD] | [-pi : pi] | NAN if not controlled, overrides total energy controller | -| throttle_direct | `float32` | norm | [0 : 1] | NAN if not controlled, overrides total energy controller | +| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | +| ---------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | +| timestamp | `uint64` | us | | Time since system start | +| altitude | `float32` | m | | Altitude setpoint AMSL, not controlled directly if NAN or if height_rate is finite | +| height_rate | `float32` | m/s [ENU] | | Scalar height rate setpoint. NAN if not controlled directly | +| equivalent_airspeed | `float32` | m/s | [0 : inf] | Scalar equivalent airspeed setpoint. NAN if system default should be used | +| pitch_direct | `float32` | rad | [-pi/2 : pi/2] | Absolute pitch angle setpoint. NAN if not controlled, overrides total energy controller | +| throttle_direct | `float32` | norm | [0 : 1] | NAN if not controlled, overrides total energy controller | ## Constants @@ -42,6 +43,7 @@ Click here to see original file # Used by the fw_lateral_longitudinal_control module # If pitch_direct and throttle_direct are not both finite, then the controller relies on altitude/height_rate and equivalent_airspeed to control vertical motion. # If both altitude and height_rate are NAN, the controller maintains the current altitude. +# Pitch angles are absolute: the angle of the fixed-wing body x-axis above the horizon, without FW_PSP_OFF applied. uint32 MESSAGE_VERSION = 0 @@ -50,7 +52,7 @@ uint64 timestamp # [us] Time since system start float32 altitude # [m] Altitude setpoint AMSL, not controlled directly if NAN or if height_rate is finite float32 height_rate # [m/s] [@frame ENU] Scalar height rate setpoint. NAN if not controlled directly float32 equivalent_airspeed # [m/s] [@range 0, inf] Scalar equivalent airspeed setpoint. NAN if system default should be used -float32 pitch_direct # [rad] [@range -pi, pi] [@frame FRD] NAN if not controlled, overrides total energy controller +float32 pitch_direct # [rad] [@range -pi/2, pi/2] Absolute pitch angle setpoint. NAN if not controlled, overrides total energy controller float32 throttle_direct # [norm] [@range 0,1] NAN if not controlled, overrides total energy controller ``` diff --git a/docs/ko/msg_docs/LongitudinalControlConfiguration.md b/docs/ko/msg_docs/LongitudinalControlConfiguration.md index 89ff0610475..abc96fb3858 100644 --- a/docs/ko/msg_docs/LongitudinalControlConfiguration.md +++ b/docs/ko/msg_docs/LongitudinalControlConfiguration.md @@ -8,23 +8,24 @@ Fixed Wing Longitudinal Control Configuration message. Used by the fw_lateral_longitudinal_control module and TECS to constrain FixedWingLongitudinalSetpoint messages and configure the resultant setpoints. +Pitch angles are absolute: the angle of the fixed-wing body x-axis above the horizon, without FW_PSP_OFF applied. **TOPICS:** longitudinal_control_configuration ## Fields -| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | -| ---------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| timestamp | `uint64` | us | | Time since system start | -| pitch_min | `float32` | rad | [-pi : pi] | Defaults to FW_P_LIM_MIN if NAN. | -| pitch_max | `float32` | rad | [-pi : pi] | Defaults to FW_P_LIM_MAX if NAN. | -| throttle_min | `float32` | norm | [0 : 1] | Defaults to FW_THR_MIN if NAN. | -| throttle_max | `float32` | norm | [0 : 1] | Defaults to FW_THR_MAX if NAN. | -| climb_rate_target | `float32` | m/s | | Target climbrate to change altitude. Defaults to FW_T_CLMB_R_SP if NAN. Not used if height_rate is directly set in FixedWingLongitudinalSetpoint. | -| sink_rate_target | `float32` | m/s | | Target sinkrate to change altitude. Defaults to FW_T_SINK_R_SP if NAN. Not used if height_rate is directly set in FixedWingLongitudinalSetpoint. | -| speed_weight | `float32` | | [0 : 2] | 0=pitch controls altitude only, 2=pitch controls airspeed only | -| enforce_low_height_condition | `bool` | | | If true, the altitude controller is configured with an alternative timeconstant for tighter altitude tracking | -| disable_underspeed_protection | `bool` | | | If true, underspeed handling is disabled in the altitude controller | +| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | +| ---------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| timestamp | `uint64` | us | | Time since system start | +| pitch_min | `float32` | rad | [-pi/2 : pi/2] | Minimum absolute pitch angle setpoint. Defaults to FW_P_LIM_MIN if NAN. | +| pitch_max | `float32` | rad | [-pi/2 : pi/2] | Maximum absolute pitch angle setpoint. Defaults to FW_P_LIM_MAX if NAN. | +| throttle_min | `float32` | norm | [0 : 1] | Defaults to FW_THR_MIN if NAN. | +| throttle_max | `float32` | norm | [0 : 1] | Defaults to FW_THR_MAX if NAN. | +| climb_rate_target | `float32` | m/s | | Target climbrate to change altitude. Defaults to FW_T_CLMB_R_SP if NAN. Not used if height_rate is directly set in FixedWingLongitudinalSetpoint. | +| sink_rate_target | `float32` | m/s | | Target sinkrate to change altitude. Defaults to FW_T_SINK_R_SP if NAN. Not used if height_rate is directly set in FixedWingLongitudinalSetpoint. | +| speed_weight | `float32` | | [0 : 2] | 0=pitch controls altitude only, 2=pitch controls airspeed only | +| enforce_low_height_condition | `bool` | | | If true, the altitude controller is configured with an alternative timeconstant for tighter altitude tracking | +| disable_underspeed_protection | `bool` | | | If true, underspeed handling is disabled in the altitude controller | ## Constants @@ -44,13 +45,14 @@ Click here to see original file # # Used by the fw_lateral_longitudinal_control module and TECS to constrain FixedWingLongitudinalSetpoint messages # and configure the resultant setpoints. +# Pitch angles are absolute: the angle of the fixed-wing body x-axis above the horizon, without FW_PSP_OFF applied. uint32 MESSAGE_VERSION = 0 uint64 timestamp # [us] Time since system start -float32 pitch_min # [rad] [@range -pi, pi] Defaults to FW_P_LIM_MIN if NAN. -float32 pitch_max # [rad] [@range -pi, pi] Defaults to FW_P_LIM_MAX if NAN. +float32 pitch_min # [rad] [@range -pi/2, pi/2] Minimum absolute pitch angle setpoint. Defaults to FW_P_LIM_MIN if NAN. +float32 pitch_max # [rad] [@range -pi/2, pi/2] Maximum absolute pitch angle setpoint. Defaults to FW_P_LIM_MAX if NAN. float32 throttle_min # [norm] [@range 0,1] Defaults to FW_THR_MIN if NAN. float32 throttle_max # [norm] [@range 0,1] Defaults to FW_THR_MAX if NAN. float32 climb_rate_target # [m/s] Target climbrate to change altitude. Defaults to FW_T_CLMB_R_SP if NAN. Not used if height_rate is directly set in FixedWingLongitudinalSetpoint. diff --git a/docs/ko/msg_docs/RcChannels.md b/docs/ko/msg_docs/RcChannels.md index 9b7e9daba0b..9d320c3d88d 100644 --- a/docs/ko/msg_docs/RcChannels.md +++ b/docs/ko/msg_docs/RcChannels.md @@ -14,47 +14,10 @@ pageClass: is-wide-page | timestamp_last_valid | `uint64` | | | Timestamp of last valid RC signal | | channels | `float32[18]` | | | Scaled to -1..1 (throttle: 0..1) | | channel_count | `uint8` | | | Number of valid channels | -| function | `int8[30]` | | | Functions mapping | | rssi | `uint8` | | | Receive signal strength index | | signal_lost | `bool` | | | Control signal lost, should be checked together with topic timeout | | frame_drop_count | `uint32` | | | Number of dropped frames | -## Constants - -| 명칭 | 형식 | Value | 설명 | -| ---------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | -- | -| FUNCTION_THROTTLE | `uint8` | 0 | | -| FUNCTION_ROLL | `uint8` | 1 | | -| FUNCTION_PITCH | `uint8` | 2 | | -| FUNCTION_YAW | `uint8` | 3 | | -| FUNCTION_RETURN | `uint8` | 4 | | -| FUNCTION_LOITER | `uint8` | 5 | | -| FUNCTION_OFFBOARD | `uint8` | 6 | | -| FUNCTION_FLAPS | `uint8` | 7 | | -| FUNCTION_AUX_1 | `uint8` | 8 | | -| FUNCTION_AUX_2 | `uint8` | 9 | | -| FUNCTION_AUX_3 | `uint8` | 10 | | -| FUNCTION_AUX_4 | `uint8` | 11 | | -| FUNCTION_AUX_5 | `uint8` | 12 | | -| FUNCTION_AUX_6 | `uint8` | 13 | | -| FUNCTION_PARAM_1 | `uint8` | 14 | | -| FUNCTION_PARAM_2 | `uint8` | 15 | | -| FUNCTION_PARAM_3_5 | `uint8` | 16 | | -| FUNCTION_KILLSWITCH | `uint8` | 17 | | -| FUNCTION_TRANSITION | `uint8` | 18 | | -| FUNCTION_GEAR | `uint8` | 19 | | -| FUNCTION_ARMSWITCH | `uint8` | 20 | | -| FUNCTION_FLTBTN_SLOT_1 | `uint8` | 21 | | -| FUNCTION_FLTBTN_SLOT_2 | `uint8` | 22 | | -| FUNCTION_FLTBTN_SLOT_3 | `uint8` | 23 | | -| FUNCTION_FLTBTN_SLOT_4 | `uint8` | 24 | | -| FUNCTION_FLTBTN_SLOT_5 | `uint8` | 25 | | -| FUNCTION_FLTBTN_SLOT_6 | `uint8` | 26 | | -| FUNCTION_ENGAGE_MAIN_MOTOR | `uint8` | 27 | | -| FUNCTION_PAYLOAD_POWER | `uint8` | 28 | | -| FUNCTION_TERMINATION | `uint8` | 29 | | -| FUNCTION_FLTBTN_SLOT_COUNT | `uint8` | 6 | | - ## Source Message [Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/RcChannels.msg) @@ -65,43 +28,9 @@ Click here to see original file ```c uint64 timestamp # time since system start (microseconds) -uint8 FUNCTION_THROTTLE = 0 -uint8 FUNCTION_ROLL = 1 -uint8 FUNCTION_PITCH = 2 -uint8 FUNCTION_YAW = 3 -uint8 FUNCTION_RETURN = 4 -uint8 FUNCTION_LOITER = 5 -uint8 FUNCTION_OFFBOARD = 6 -uint8 FUNCTION_FLAPS = 7 -uint8 FUNCTION_AUX_1 = 8 -uint8 FUNCTION_AUX_2 = 9 -uint8 FUNCTION_AUX_3 = 10 -uint8 FUNCTION_AUX_4 = 11 -uint8 FUNCTION_AUX_5 = 12 -uint8 FUNCTION_AUX_6 = 13 -uint8 FUNCTION_PARAM_1 = 14 -uint8 FUNCTION_PARAM_2 = 15 -uint8 FUNCTION_PARAM_3_5 = 16 -uint8 FUNCTION_KILLSWITCH = 17 -uint8 FUNCTION_TRANSITION = 18 -uint8 FUNCTION_GEAR = 19 -uint8 FUNCTION_ARMSWITCH = 20 -uint8 FUNCTION_FLTBTN_SLOT_1 = 21 -uint8 FUNCTION_FLTBTN_SLOT_2 = 22 -uint8 FUNCTION_FLTBTN_SLOT_3 = 23 -uint8 FUNCTION_FLTBTN_SLOT_4 = 24 -uint8 FUNCTION_FLTBTN_SLOT_5 = 25 -uint8 FUNCTION_FLTBTN_SLOT_6 = 26 -uint8 FUNCTION_ENGAGE_MAIN_MOTOR = 27 -uint8 FUNCTION_PAYLOAD_POWER = 28 -uint8 FUNCTION_TERMINATION = 29 - -uint8 FUNCTION_FLTBTN_SLOT_COUNT = 6 - uint64 timestamp_last_valid # Timestamp of last valid RC signal float32[18] channels # Scaled to -1..1 (throttle: 0..1) uint8 channel_count # Number of valid channels -int8[30] function # Functions mapping uint8 rssi # Receive signal strength index bool signal_lost # Control signal lost, should be checked together with topic timeout uint32 frame_drop_count # Number of dropped frames diff --git a/docs/ko/msg_docs/RcParameterMap.md b/docs/ko/msg_docs/RcParameterMap.md index f0eef39f0a7..cb8ca5a216d 100644 --- a/docs/ko/msg_docs/RcParameterMap.md +++ b/docs/ko/msg_docs/RcParameterMap.md @@ -23,7 +23,7 @@ pageClass: is-wide-page | 명칭 | 형식 | Value | 설명 | | ------------------------------------------------------------------------------------------------------------------ | ------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| RC_PARAM_MAP_NCHAN | `uint8` | 3 | This limit is also hardcoded in the enum RC_CHANNELS_FUNCTION in rc_channels.h | +| RC_PARAM_MAP_NCHAN | `uint8` | 3 | This limit is also hardcoded in the enum RCUpdate::Function in rc_update.h | | PARAM_ID_LEN | `uint8` | 16 | corresponds to MAVLINK_MSG_PARAM_VALUE_FIELD_PARAM_ID_LEN | ## Source Message @@ -35,7 +35,7 @@ Click here to see original file ```c uint64 timestamp # time since system start (microseconds) -uint8 RC_PARAM_MAP_NCHAN = 3 # This limit is also hardcoded in the enum RC_CHANNELS_FUNCTION in rc_channels.h +uint8 RC_PARAM_MAP_NCHAN = 3 # This limit is also hardcoded in the enum RCUpdate::Function in rc_update.h uint8 PARAM_ID_LEN = 16 # corresponds to MAVLINK_MSG_PARAM_VALUE_FIELD_PARAM_ID_LEN bool[3] valid #true for RC-Param channels which are mapped to a param diff --git a/docs/ko/msg_docs/TecsStatus.md b/docs/ko/msg_docs/TecsStatus.md index b13b4bf3522..01a72c4bcc7 100644 --- a/docs/ko/msg_docs/TecsStatus.md +++ b/docs/ko/msg_docs/TecsStatus.md @@ -8,34 +8,34 @@ pageClass: is-wide-page ## Fields -| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| timestamp | `uint64` | | | time since system start (microseconds) | -| altitude_sp | `float32` | | | Altitude setpoint AMSL [m] | -| altitude_reference | `float32` | | | Altitude setpoint reference AMSL [m] | -| altitude_time_constant | `float32` | | | Time constant of the altitude tracker [s] | -| height_rate_reference | `float32` | | | Height rate setpoint reference [m/s] | -| height_rate_direct | `float32` | | | Direct height rate setpoint from velocity reference generator [m/s] | -| height_rate_setpoint | `float32` | | | Height rate setpoint [m/s] | -| height_rate | `float32` | | | Height rate [m/s] | -| equivalent_airspeed_sp | `float32` | | | Equivalent airspeed setpoint [m/s] | -| true_airspeed_sp | `float32` | | | True airspeed setpoint [m/s] | -| true_airspeed_filtered | `float32` | | | True airspeed filtered [m/s] | -| true_airspeed_derivative_sp | `float32` | | | True airspeed derivative setpoint [m/s^2] | -| true_airspeed_derivative | `float32` | | | True airspeed derivative [m/s^2] | -| true_airspeed_derivative_raw | `float32` | | | True airspeed derivative raw [m/s^2] | -| total_energy_rate_sp | `float32` | | | Total energy rate setpoint [m^2/s^3] | -| total_energy_rate | `float32` | | | Total energy rate estimate [m^2/s^3] | -| total_energy_balance_rate_sp | `float32` | | | Energy balance rate setpoint [m^2/s^3] | -| total_energy_balance_rate | `float32` | | | Energy balance rate estimate [m^2/s^3] | -| throttle_integ | `float32` | | | Throttle integrator value [-] | -| pitch_integ | `float32` | | | Pitch integrator value [rad] | -| throttle_sp | `float32` | | | Current throttle setpoint [-] | -| pitch_sp_rad | `float32` | | | Current pitch setpoint [rad] | -| throttle_trim | `float32` | | | estimated throttle value [0,1] required to fly level at equivalent_airspeed_sp in the current atmospheric conditions | -| underspeed_ratio | `float32` | | | 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. | -| fast_descend_ratio | `float32` | | | value indicating if fast descend mode is enabled with ramp up and ramp down [0-1] | -| weight_ratio | `float32` | | | Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled. | +| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| timestamp | `uint64` | | | time since system start (microseconds) | +| altitude_sp | `float32` | | | Altitude setpoint AMSL [m] | +| altitude_reference | `float32` | | | Altitude setpoint reference AMSL [m] | +| altitude_time_constant | `float32` | | | Time constant of the altitude tracker [s] | +| height_rate_reference | `float32` | | | Height rate setpoint reference [m/s] | +| height_rate_direct | `float32` | | | Direct height rate setpoint from velocity reference generator [m/s] | +| height_rate_setpoint | `float32` | | | Height rate setpoint [m/s] | +| height_rate | `float32` | | | Height rate [m/s] | +| equivalent_airspeed_sp | `float32` | | | Equivalent airspeed setpoint [m/s] | +| true_airspeed_sp | `float32` | | | True airspeed setpoint [m/s] | +| true_airspeed_filtered | `float32` | | | True airspeed filtered [m/s] | +| true_airspeed_derivative_sp | `float32` | | | True airspeed derivative setpoint [m/s^2] | +| true_airspeed_derivative | `float32` | | | True airspeed derivative [m/s^2] | +| true_airspeed_derivative_raw | `float32` | | | True airspeed derivative raw [m/s^2] | +| total_energy_rate_sp | `float32` | | | Total energy rate setpoint [m^2/s^3] | +| total_energy_rate | `float32` | | | Total energy rate estimate [m^2/s^3] | +| total_energy_balance_rate_sp | `float32` | | | Energy balance rate setpoint [m^2/s^3] | +| total_energy_balance_rate | `float32` | | | Energy balance rate estimate [m^2/s^3] | +| throttle_integ | `float32` | | | Throttle integrator value [-] | +| pitch_integ | `float32` | | | Pitch integrator value [rad], a correction added to the pitch setpoint rather than a pitch angle | +| throttle_sp | `float32` | | | Current throttle setpoint [-] | +| pitch_sp_rad | `float32` | | | Current pitch setpoint [rad], absolute: angle of the fixed-wing body x-axis above the horizon, FW_PSP_OFF included | +| throttle_trim | `float32` | | | estimated throttle value [0,1] required to fly level at equivalent_airspeed_sp in the current atmospheric conditions | +| underspeed_ratio | `float32` | | | 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. | +| fast_descend_ratio | `float32` | | | value indicating if fast descend mode is enabled with ramp up and ramp down [0-1] | +| weight_ratio | `float32` | | | Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled. | ## Source Message @@ -68,10 +68,10 @@ float32 total_energy_balance_rate_sp # Energy balance rate setpoint [m^2/s^3] float32 total_energy_balance_rate # Energy balance rate estimate [m^2/s^3] float32 throttle_integ # Throttle integrator value [-] -float32 pitch_integ # Pitch integrator value [rad] +float32 pitch_integ # Pitch integrator value [rad], a correction added to the pitch setpoint rather than a pitch angle float32 throttle_sp # Current throttle setpoint [-] -float32 pitch_sp_rad # Current pitch setpoint [rad] +float32 pitch_sp_rad # Current pitch setpoint [rad], absolute: angle of the fixed-wing body x-axis above the horizon, FW_PSP_OFF included float32 throttle_trim # estimated throttle value [0,1] required to fly level at equivalent_airspeed_sp in the current atmospheric conditions float32 underspeed_ratio # 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. diff --git a/docs/ko/releases/main.md b/docs/ko/releases/main.md index c37895ecd73..3b8c9e8f49d 100644 --- a/docs/ko/releases/main.md +++ b/docs/ko/releases/main.md @@ -47,8 +47,8 @@ Please continue reading for [upgrade instructions](#upgrade-guide). Saved parameters are migrated automatically, but loading a QGC parameter file with the old names does not restore them. The log analysis scripts in the tree read both the old and the new names. The uORB-over-Cyphal registers are renamed from `uorb.sensor_gps` to `uorb.sensor_gnss` (`uavcan.sub.uorb.sensor_gnss.0.id`, `uavcan.pub.uorb.sensor_gnss.0.id`); `UCAN1_UORB_GPS` and `UCAN1_UORB_GPS_P` are unchanged. ([PX4-Autopilot#24399](https://github.com/PX4/PX4-Autopilot/pull/24399)) -- **`DO_JUMP` can only loop back.** - A mission is now rejected if a `DO_JUMP` targets itself or a later mission item, even if its repeat count is 0. +- **`DO_JUMP` can only loop back and its repeat count must fit.** + A mission is now rejected if a `DO_JUMP` targets itself or a later mission item, even if its repeat count is 0, and if its repeat count is negative, above 65535 or not a number (it is no longer narrowed to a different count). Missions stored on the vehicle with such jumps must be edited and uploaded again. ## Other changes @@ -133,7 +133,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide). ### Fixed-wing -- TBD +- TECS underspeed protection now starts at the minimum airspeed ([FW_AIRSPD_MIN](../advanced_config/parameter_reference.md#FW_AIRSPD_MIN)) and is fully active at 90% of it, or halfway to [FW_AIRSPD_STALL](../advanced_config/parameter_reference.md#FW_AIRSPD_STALL) if that is higher. Previously it only started 15% of trim airspeed below the minimum airspeed. The roll angle is limited towards 20° (or [FW_R_LIM](../advanced_config/parameter_reference.md#FW_R_LIM) if lower) while undersped, and the altitude reference is reset to avoid a pitch-up on recovery. ([PX4-Autopilot#26859](https://github.com/PX4/PX4-Autopilot/pull/26859)) ### Rover diff --git a/docs/ko/releases/release_process.md b/docs/ko/releases/release_process.md index b7abf5bfe78..18f3c403687 100644 --- a/docs/ko/releases/release_process.md +++ b/docs/ko/releases/release_process.md @@ -209,7 +209,7 @@ If a critical issue is discovered during RC testing that must be fixed before re 3. Maintainers vote on whether to merge the fix 4. If approved, merge the fix and create a new RC tag (e.g., `v1.18.0-rc2`) -### 7) Release Vote +### 7. Release Vote The release vote takes place during the [Weekly Community Q&A Call](../contribute/dev_call.md): @@ -254,7 +254,7 @@ When a version tag is pushed, the [build_all_targets.yml](https://github.com/PX4 2. Uploads firmware artifacts to AWS S3 (`Firmware/vX.Y.Z/` and updates `Firmware/stable/`) 3. Creates a **draft release** on GitHub with all `.px4` firmware files attached -### 11) Publish GitHub Release +### 11. Publish GitHub Release Edit the draft release on GitHub: diff --git a/docs/ko/sensor/airspeed.md b/docs/ko/sensor/airspeed.md index c16b4a58a2b..6d7a04531e3 100644 --- a/docs/ko/sensor/airspeed.md +++ b/docs/ko/sensor/airspeed.md @@ -48,22 +48,51 @@ You should also check [ASPD_PRIMARY](../advanced_config/parameter_reference.md#A ### Multiple Airspeed Sensors + + :::warning 실험 Using multiple airspeed sensors is experimental. ::: -If you have multiple airspeed sensors then you can select which sensor is _preferred_ as the primary source using [ASPD_PRIMARY](../advanced_config/parameter_reference.md#ASPD_PRIMARY), where `1`, `2` and `3` reflect the order in which the airspeed sensors were started: +PX4 supports up to three airspeed sensors. +Each sensor is converted to airspeed independently, keeps its own zero-offset calibration, and is validated separately, so the selector can fall back to a healthy sensor if one fails in flight. -- `0`: Synthetic airspeed estimation (groundspeed minus windspeed) -- `1`: First airspeed sensor started (default) -- `2`: Second airspeed sensor started -- `3`: Third airspeed sensor started +#### Selecting the Primary Sensor -The airspeed selector validates the indicated sensor _first_ and only falls back to other sensors if the indicated sensor fails airspeed checks ([ASPD_DO_CHECKS](../advanced_config/parameter_reference.md#ASPD_DO_CHECKS) is used to configure the checks). +[ASPD_PRIMARY](../advanced_config/parameter_reference.md#ASPD_PRIMARY) selects the source that is _preferred_: + +- `0`: Groundspeed minus windspeed +- `1`: Airspeed sensor 1 (default) +- `2`: Airspeed sensor 2 +- `3`: Airspeed sensor 3 +- `4`: Thrust-based (synthetic) airspeed + +The sensor numbers `1`, `2` and `3` refer to the **calibration entry** the sensor owns (recorded in `CAL_DPRES{n-1}_ID`). + +:::tip +Calibrate every sensor before relying on `ASPD_PRIMARY`. +::: + +#### Failover + +The preferred sensor is used while it passes the airspeed checks ([ASPD_DO_CHECKS](../advanced_config/parameter_reference.md#ASPD_DO_CHECKS) configures which checks run). +If it fails, the selector switches to another valid sensor, preferring the configured primary. + +[ASPD_FALLBACK](../advanced_config/parameter_reference.md#ASPD_FALLBACK) controls what happens when _no_ sensor is usable: stay without airspeed, fall back to groundspeed minus windspeed, or fall back to thrust-based airspeed. + +:::warning +By default a sensor that fails its checks stays failed until the next reboot ([ASPD_FS_T_START](../advanced_config/parameter_reference.md#ASPD_FS_T_START) is `-1`). +Set it to a positive number of seconds to allow a recovered sensor to be used again in the same flight. +::: The selected sensor is then used to [supply data to the estimator (EKF2)](../advanced_config/tuning_the_ecl_ekf.md#airspeed) and the controllers. +#### Per-Sensor Calibration + +Each sensor stores its own zero offset in `CAL_DPRES{n}_OFF`, linked to the sensor's device ID in `CAL_DPRES{n}_ID`. +A single [airspeed calibration](../config/airspeed.md) calibrates every connected sensor. + ### Sensor-specific Configuration Other than enabling the sensor, sensor-specific configuration is often not required. @@ -77,10 +106,13 @@ The specific configuration for sensors that do not have a separate page is liste Airspeed sensors should be calibrated by following the instructions: [Basic Configuration > Airspeed](../config/airspeed.md). +## Validation + For more advanced validation, configuration and debugging see [Airspeed Validation](../advanced_config/airspeed_validation.md). ## See Also +- [Airspeed Scale Handling](../config_fw/airspeed_scale_handling) - [Using PX4's Navigation Filter (EKF2) > Airspeed](../advanced_config/tuning_the_ecl_ekf.md#airspeed) - [Airspeed drivers](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure) (source code) - [VTOL Without an Airspeed Sensor](../config_vtol/vtol_without_airspeed_sensor.md) diff --git a/docs/ko/sensor/inertiallabs.md b/docs/ko/sensor/inertiallabs.md index 522c4a95fff..b755e8faa94 100644 --- a/docs/ko/sensor/inertiallabs.md +++ b/docs/ko/sensor/inertiallabs.md @@ -21,8 +21,8 @@ The mode is configurable using a parameter. [Get technical support or send requests to sales team](https://inertiallabs.com/inertial-labs-inc/contact-inertial-labs-team/). Recommended sensors: -- [INS-U GNSS/INS](https://inertiallabs.com/wp-content/uploads/2026/01/INS-U_INS-U-OEM_Datasheet_REV2.18_JAN2026.pdf): Recommended for fixed-wing systems without hovering, where static heading is not necessary. -- [INS-DU DUAL GNSS/INS](https://inertiallabs.com/wp-content/uploads/2025/12/INS-DU_INS-DU-OEM_Datasheet_REV1.00_DEC2025.pdf): Recommended for multicopter systems where hovering and low dynamics requires the use of static heading. +- [INS-U GNSS/INS](https://inertiallabs.com/library/ins_u_datasheet.pdf): Recommended for fixed-wing systems without hovering, where static heading is not necessary. +- [INS-DU DUAL GNSS/INS](https://inertiallabs.com/library/ins_du_datasheet.pdf): Recommended for multicopter systems where hovering and low dynamics requires the use of static heading. ## 하드웨어 설정 diff --git a/docs/ko/sensor/lidar_lite.md b/docs/ko/sensor/lidar_lite.md index 98a85488422..84719b1f67a 100644 --- a/docs/ko/sensor/lidar_lite.md +++ b/docs/ko/sensor/lidar_lite.md @@ -1,86 +1,201 @@ -# Lidar-Lite +# Garmin LIDAR-Lite -LIDAR-Lite는 드론, 로봇 또는 무인 차량용 소형 고성능 광학 원거리 측정 센서입니다. I2C 또는 PWM에 연결됩니다. + -![LidarLite v3](../../assets/hardware/sensors/lidar_lite/lidar_lite_v3.jpg) +The [Garmin LIDAR-Lite v3](https://www.garmin.com/en-US/p/557294/) is a compact laser time-of-flight [rangefinder](../sensor/rangefinders.md) with a range of up to 40 m (PX4 caps this to 35 m or less). +It connects to the flight controller using either I2C or PWM. -## 구매처 - -- [LIDAR-Lite v3](https://www.garmin.com/en-AU/p/557294/) (5cm - 40m) - -## 핀배열 - -Lidar-Lite (v2, v3) 핀배열은 아래와 같습니다. - -| 핀 | 명칭 | 설명 | -| - | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 1 | POWER_IN | 전원 공급. 4.75-5.5V DC 공칭, 최대 6V DC. | -| 2 | POWER_EN | 액티브 하이는 3.3V 마이크로 컨트롤러 레귤레이터의 작동을 가능하게 합니다. Low puts board to sleep, draws <40 μA. (Internal 100K pull-up) | -| 3 | 모드 선택 제어 | 트리거 (하이-로우 에지) PWM 출력 (하이) 제공 | -| 4 | SCL | I2C Clock | -| 5 | SDA | I2C 데이터 | -| 6 | GND | 신호/전원 접지. | - -## 배선 - -The _Lidar-Lite v3_ can be used with either PWM or I2C. -구형 모델에서는 PWM을 권장합니다. -거리계는 일부 ESC/BEC(PWM 또는 I2C를 통해 연결됨)로 별도 전원이 공급되어야합니다. +![LIDAR-Lite v3](../../assets/hardware/sensors/lidar_lite/lidar_lite_v3.jpg) :::info -The I2C interface of non-blue-label Lidar-Lite (v1) devices has stability limitations and all silver-label generations of Lidar-Lite sensors are therefore excluded from the I2C interface. -이러한 센서에는 PWM 인터페이스(아래에 자세히 설명)를 사용하는 것이 좋습니다. -파란색 레이블(v2) 장치는 일부 조건에서 5V 미만 전원을 사용하며, 일정한 오프셋을 나타낼 수 있습니다. -이는 현재 (2015 년 4 분기) 제조업체에서 조사 중이며, 특정 운영 조건을 준수하여 잠재적으로 해결 가능합니다. -권장되는 강력한 설정은 PWM 인터페이스를 가진 v1 장치입니다. +The driver for the PWM connection is not included in PX4 firmware by default. +See [Firmware Support](#firmware_support) for how to check your board and add it. ::: -The standard wiring instructions for Lidar-Lite 3 (from the [Operation Manual](https://static.garmin.com/pumac/LIDAR_Lite_v3_Operation_Manual_and_Technical_Specifications.pdf)) are shown below. -Lidar-Lite v2와 v3은 커넥터의 핀 순서가 역전된다는 점을 제외하면 동일합니다 (즉, 커넥터가 뒤집힌 것처럼). +## Supported Models {#supported_models} -![LidarLite v3 - Standard Wiring from Garmin Specification](../../assets/hardware/sensors/lidar_lite/lidar_lite2_standard_wiring_spec.jpg) +| 모델 | 범위 | 연결 | 참고 | +| ------------------------------------------------------- | ---------- | -------- | ------------------------------------------- | +| [LIDAR-Lite v3](https://www.garmin.com/en-US/p/557294/) | Up to 40 m | I2C, PWM | | +| LIDAR-Lite v3HP | | I2C | | +| LIDAR-Lite v4 LED | | I2C | PX4 caps the range to 10 m. | +| LIDAR-Lite v2 | | I2C, PWM | | +| LIDAR-Lite v1 | | I2C, PWM | | -### PWM 인터페이스 배선 +The rest of this page describes the LIDAR-Lite v3, unless otherwise stated. -The pin connections for wiring LidarLite to the _Pixhawk 1_ AUX ports (PWM interface) are shown below. +## Specifications {#specifications} -| 핀 | Lidar-Lite (v2, v3) | Pixhawk AUX Servo | 설명 | -| - | -------------------------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | VCC | AUX 6 (중앙) | 전원 공급. 4.75-5.5V DC 공칭, 최대 6V DC. | -| 2 | RESET | AUX 6 (하단) | 센서의 재설정 라인 | -| 3 | PWM | AUX 5 (하단) | Lidar Lite의 PWM 출력. **Needs a 470 Ohm pull-down (to GND), Do not use a 1 K0hm resistor.** | -| 4 | SCL | - | 연결되지 않음 | -| 5 | SDA | - | 연결되지 않음 | -| 6 | GND | AUX 6 (상단) | 접지 | +The following specifications are for the LIDAR-Lite v3. + +- **Technology:** Laser time-of-flight (905 nm) +- **Range:** Up to 40 m (70% reflective target) +- **Update rate:** 270 Hz typical, 650 Hz in fast mode (PX4 samples at up to 100 Hz on I2C, and at 20 Hz on PWM) +- **Beam divergence:** 8 mrad +- **Accuracy:** ±2.5 cm typical below 5 m, ±10 cm typical at 5 m and above +- **Resolution:** ±1 cm +- **Interface:** I2C (address `0x62`), PWM +- **Input voltage:** 5 V DC nominal (4.5–5.5 V) +- **Current draw:** 105 mA idle, 135 mA in continuous operation +- **Dimensions:** 20 x 48 x 40 mm +- **Weight:** 22 g +- **Operating temperature:** -20 to 60 °C +- **Laser class:** Class 1 + +## Where to Buy {#store} + +- [LIDAR-Lite v3](https://www.garmin.com/en-US/p/557294/) (Garmin) + +## Hardware Setup {#hardware_setup} + +### Mounting {#mounting} + +PX4 assumes that the rangefinder is facing down (the orientation cannot be configured). + +### Pinouts {#pinouts} + +The LIDAR-Lite v3 has a 6-pin connector that mates with a JST GH housing (`GHR-06V-S`, 1.25 mm pitch). + +| 핀 | Wire colour | 신호 | 설명 | +| - | ----------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | +| 1 | 빨강 | 5 V DC (+) | Power supply. 5 V DC nominal (4.5–5.5 V). | +| 2 | Orange | Power enable | Internal pull-up. Can be driven low to shut off power to the sensor. | +| 3 | 노랑 | Mode control | PWM interface: pull low to trigger a measurement; returns a pulse (10 μs/cm). | +| 4 | 녹색 | I2C SCL | I2C clock | +| 5 | 청색 | I2C SDA | I2C data | +| 6 | 검정 | Ground (-) | Signal and power ground | + +### Wiring {#wiring} + +The LIDAR-Lite v3 can be connected using either I2C or PWM. +Older LIDAR-Lite generations (v1 and v2) were reported to have I2C problems, and PWM was recommended for them. + +The sensor requires a 5 V DC supply, and draws up to 135 mA in continuous operation. +Check that the flight controller port can supply this, or power the sensor from a separate supply that shares a ground with the flight controller. + +#### I2C {#wiring_i2c} + +Connect the sensor to an external `I2C` port on the flight controller. + +![LIDAR-Lite v3 I2C wiring](../../assets/hardware/sensors/lidar_lite/lidar_lite_v3_i2c_wiring.svg) + +| LIDAR-Lite v3 pin | Wire colour | Connect to | +| ------------------------------ | ----------- | ------------------------- | +| 1 (5 V DC) | 빨강 | 5 V DC supply | +| 4 (I2C SCL) | 녹색 | Flight controller I2C SCL | +| 5 (I2C SDA) | 청색 | Flight controller I2C SDA | +| 6 (Ground) | 검정 | Flight controller GND | + +Pins 2 (power enable) and 3 (mode control) are not connected. + +Garmin's standard I2C wiring also requires a 680 μF electrolytic capacitor between the 5 V DC and ground wires (observe the polarity). + +The sensor uses the I2C address `0x62`. + +#### PWM {#wiring_pwm} :::info -On a flight controller that has no AUX port the equivalent MAIN pins are used (e.g. the PWM output on the lidar instead maps to MAIN 5). -핀 번호는 하드 코딩되어 있습니다. +The PWM connection is not as well tested as I2C. ::: -LidarLite v2의 배선은 아래와 같습니다. -Lidar-Lite v3는 커넥터의 핀 번호가 반대라는 점을 제외에는 유사하게 연결됩니다. +PX4 reads the sensor's PWM output on the flight controller's PWM input pin. +On Pixhawk flight controllers this is FMU output 5 (`AUX 5`, or `MAIN 5` on flight controllers that have no AUX port). +The pin is fixed. -![Lidar Lite 2 Interface wiring](../../assets/hardware/sensors/lidar_lite/lidar_lite_2_interface_wiring.jpg) +![LIDAR-Lite v3 PWM wiring](../../assets/hardware/sensors/lidar_lite/lidar_lite_v3_pwm_wiring.svg) -![Lidar Lite 2 Interface wiring](../../assets/hardware/sensors/lidar_lite/lidarlite_wiring_scheme_pixhawk.jpg) +| LIDAR-Lite v3 pin | Wire colour | Connect to | +| ----------------------------------- | ----------- | ------------------------------------------------------------------------------- | +| 1 (5 V DC) | 빨강 | 5 V DC supply | +| 3 (Mode control) | 노랑 | `AUX 5` signal pin, and to ground through a resistor (below) | +| 6 (Ground) | 검정 | Flight controller GND | -![Lidar Lite 2 pins/cabling](../../assets/hardware/sensors/lidar_lite/lidarlite_wiring_pins_cables.jpg) +Pins 2 (power enable), 4 (I2C SCL) and 5 (I2C SDA) are not connected. -### I2C 인터페이스 배선 +The mode control pin must be connected to ground through a resistor, which makes the sensor measure continuously. +The Garmin specification is for a 1 kΩ resistor, but a 470 Ω resistor was found to be needed when tested with PX4 on a Pixhawk. -I2C 배선은 다른 거리 센서에 대해서도 동일합니다. -SLA, SLC, GND 및 VCC를 비행 콘트롤러와 센서의 해당 (동일한) 핀에 연결하면 됩니다. +The driver also uses FMU output 6 (`AUX 6`), so this output cannot be used for anything else. -## 소프트웨어 설정 +## Firmware Support {#firmware_support} -The rangefinder/port is enabled using [SENS_EN_LL40LS](../advanced_config/parameter_reference.md#SENS_EN_LL40LS) - set to `1` for PWM, or `2` for I2C. +The rangefinder is supported by a different driver for each connection, as described below. -:::info -The driver for this rangefinder is usually present in firmware. -If missing, you would also need to add the driver (`drivers/ll40ls`) to the board configuration. -::: +To check your board, look for the keys in its [board configuration](../hardware/porting_guide_config.md) file, `boards///default.px4board`. -## 추가 정보 +If a driver is missing, add its key to the board's `default.px4board` file, or enable it in [boardconfig](../hardware/porting_guide_config.md#px4-menuconfig-setup) under **Drivers > Distance sensors**, and then [build and upload the firmware](../dev_setup/building_px4.md). -- [LIDAR_Lite_v3_Operation_Manual_and_Technical_Specifications.pdf](https://static.garmin.com/pumac/LIDAR_Lite_v3_Operation_Manual_and_Technical_Specifications.pdf) (Garmin) +The drivers do not start until they are enabled using the parameter in [PX4 Configuration](#px4_configuration). + +### I2C {#firmware_support_i2c} + +The driver is [ll40ls](../modules/modules_driver_distance_sensor.md#ll40ls), which is built into firmware by either of the following keys: + +- `CONFIG_COMMON_DISTANCE_SENSOR=y`: the common set of rangefinder drivers, which includes this one. +- `CONFIG_DRIVERS_DISTANCE_SENSOR_LL40LS=y`: this driver on its own. + +Most boards set `CONFIG_COMMON_DISTANCE_SENSOR`, so the I2C driver is present in most firmware. + +### PWM {#firmware_support_pwm} + +The driver is [ll40ls_pwm](../modules/modules_driver_distance_sensor.md#ll40ls-pwm), which is built into firmware by the key `CONFIG_DRIVERS_DISTANCE_SENSOR_LL40LS_PWM=y`. +It is not part of the common set of rangefinder drivers, so it is only present in the firmware for boards that set that key. + +The PWM driver also requires the `pwm_input` driver (`CONFIG_DRIVERS_PWM_INPUT=y`). + +## PX4 Configuration {#px4_configuration} + +The rangefinder is enabled using the parameter [SENS_EN_LL40LS](../advanced_config/parameter_reference.md#SENS_EN_LL40LS). +The value to set depends on the connection, as described below. +Reboot the flight controller after changing the parameter. + +If the parameter is not available in _QGroundControl_ then the I2C driver is not in the firmware: see [Firmware Support](#firmware_support). + +The configuration that is common to all rangefinders, such as the sensor position offsets used by the estimator, is covered in [Rangefinders > Configuration/Setup](../sensor/rangefinders.md#configuration). + +### I2C {#px4_configuration_i2c} + +Set [SENS_EN_LL40LS](../advanced_config/parameter_reference.md#SENS_EN_LL40LS) to `2`. + +The driver detects the hardware version of the connected sensor, and uses this to set the maximum range that PX4 will use: + +- LIDAR-Lite v4 LED: 10 m +- Other versions: 25 m or 35 m, depending on the detected hardware version + +The minimum range is 5 cm. + +### PWM {#px4_configuration_pwm} + +Set [SENS_EN_LL40LS](../advanced_config/parameter_reference.md#SENS_EN_LL40LS) to `1`. + +PX4 uses a range of 5 cm to 25 m for all versions of the sensor. + +## Testing {#testing} + +You can check that the driver is running using the _QGroundControl MAVLink Console_. +For I2C: + +```sh +ll40ls status +``` + +For PWM: + +```sh +ll40ls_pwm status +``` + +You can observe the published measurements with: + +```sh +listener distance_sensor +``` + +The measurements can also be viewed in the `DISTANCE_SENSOR` message in the _QGroundControl MAVLink Inspector_. +For more information see [Rangefinders > Testing](../sensor/rangefinders.md#testing). + +## Further Information {#further_information} + +- [Modules Reference: Distance Sensor (Driver): ll40ls](../modules/modules_driver_distance_sensor.md#ll40ls) +- [Modules Reference: Distance Sensor (Driver): ll40ls_pwm](../modules/modules_driver_distance_sensor.md#ll40ls-pwm) +- [LIDAR-Lite v3 Operation Manual and Technical Specifications](https://static.garmin.com/pumac/LIDAR_Lite_v3_Operation_Manual_and_Technical_Specifications.pdf) (Garmin) diff --git a/docs/ko/sensor/rangefinders.md b/docs/ko/sensor/rangefinders.md index 8a1b4e0953b..9d2ab8e5754 100644 --- a/docs/ko/sensor/rangefinders.md +++ b/docs/ko/sensor/rangefinders.md @@ -5,7 +5,7 @@ Distance sensors provide distance measurement that can be used for [terrain foll This section lists the distance sensors supported by PX4 (linked to more detailed documentation), and provides information about the [generic configuration](#configuration) required for all rangefinders, [testing](#testing), and simulation with [Gazebo](#gazebo-simulation) or [Gazebo-Classic](#gazebo-classic-simulation). 보다 자세한 설정과 정보는 아래 링크(및 사이드 바)를 참고하십시오. -Lidar Lite V3LightWare SF11/C LidarARK Flow +LIDAR-Lite v3LightWare SF11/C LidarARK Flow ## 지원되는 거리 측정기 @@ -15,39 +15,40 @@ This is a subset of the rangefinders that can be used with PX4. There may also be other DroneCAN rangefinders than those listed here. ::: -| Rangefinder | Technology | Range (min – max) | 연결 | NDAA | 참고 | -| ------------------------------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------- | ----------------- | ------------------------------------------------------ | -| [Ainstein US-D1 Standard Radar Altimeter] | Microwave radar | ~50 m | UART | ✔️ | | -| [ARK DIST SR] | ToF (850 nm IR) | 8 cm to ~30 m | DroneCAN, UART | ✔️ | | -| [ARK DIST MR] | ToF (IR) | 8 cm to ~50 m | DroneCAN, UART | ✔️ | | -| [Benewake TFmini] | ToF (IR laser) | ~12 m | UART | ~ | | -| [Holybro ST VL53L1X Lidar] | ToF (IR) | up to ~4 m | I2C | ~ | | -| [LeddarOne] | ToF (IR) | 1 cm – 40 m | UART | ~ | | -| [Lidar-Lite] | ToF (IR laser) | 5 cm – 40 m | I2C, PWM | ~ | | -| [LightWare SF11/C] | ToF (IR laser) | up to ~120 m | UART, I2C | ~ | | -| [LightWare LW20/C] | ToF (IR laser) | up to ~100 m | I2C | ~ | Waterproof (IP67) + servo | -| [LightWare SF45/B] | ToF (IR laser) | ~50 m | UART | ~ | Rotary lidar (collision prevention) | -| [MaxBotix I2CXL-MaxSonar-EZ] | Ultrasonic | | I2C | ~ | | -| [RaccoonLab Cyphal & DroneCAN µRANGEFINDER] | ToF (IR) | ~0.1 m – ~8 m | DroneCAN, Cyphal | ~ | | -| [Sony AS-DT1] | ToF | up to 40 m | UART | ~ | Multipoint distance sensor | -| [TeraRanger Evo 60 m] | ToF (IR) | 0.5 m – 60 m | I2C | ~ | | -| [TeraRanger Evo 600Hz] | ToF (IR) | 0.75 m – 8 m | I2C | ~ | High update rate (600 Hz) | -| [LightWare SF02] _(disc.)_ | ToF (IR laser) | ~50 m | UART | ~ | Discontinued | -| [LightWare SF10/A] _(disc.)_ | ToF (IR laser) | ~25 m | UART, I2C | ~ | Discontinued | -| [LightWare SF10/B] _(disc.)_ | ToF (IR laser) | ~50 m | UART, I2C | ~ | Discontinued | -| [LightWare SF10/C] _(disc.)_ | ToF (IR laser) | ~100 m | UART, I2C | ~ | Discontinued | -| [Lanbao PSK-CM8JL65-CC5] _(disc.)_ | ToF (IR) | 0.17 m – 8 m | UART | ✖️ | Discontinued | -| [Smartmicro Drone Altimeter] | Microwave radar | 1 m to 175 m | DroneCAN | ~ | | -| [TeraRanger One] _(disc.)_ | ToF (IR) | ~0.2 m – ~14 m (typical) | I2C (adapter required) | ~ | Discontinued | +| Rangefinder | Technology | Range (min – max) | 연결 | NDAA | 참고 | +| ------------------------------------------- | ---------------------------------- | ------------------------------------------------------------- | ---------------- | ----------------- | ------------------------------------------------------ | +| [Ainstein US-D1 Standard Radar Altimeter] | Microwave radar | ~50 m | UART | ✔️ | | +| [ARK DIST SR] | ToF (850 nm IR) | 8 cm to ~30 m | DroneCAN, UART | ✔️ | | +| [ARK DIST MR] | ToF (IR) | 8 cm to ~50 m | DroneCAN, UART | ✔️ | | +| [Benewake TFmini] | ToF (IR laser) | ~12 m | UART | ~ | | +| [Garmin LIDAR-Lite v3] | ToF (IR laser) | up to 40 m | I2C, PWM | ~ | PX4 caps range to 35 m or less | +| [Holybro ST VL53L1X Lidar] | ToF (IR) | up to ~4 m | I2C | ~ | | +| [LeddarOne] | ToF (IR) | 1 cm – 40 m | UART | ~ | | +| [LightWare SF11/C] | ToF (IR laser) | up to ~120 m | UART, I2C | ~ | | +| [LightWare LW20/C] | ToF (IR laser) | up to ~100 m | I2C | ~ | Waterproof (IP67) + servo | +| [LightWare SF45/B] | ToF (IR laser) | ~50 m | UART | ~ | Rotary lidar (collision prevention) | +| [MaxBotix I2CXL-MaxSonar-EZ] | Ultrasonic | | I2C | ~ | | +| [RaccoonLab Cyphal & DroneCAN µRANGEFINDER] | ToF (IR) | ~0.1 m – ~8 m | DroneCAN, Cyphal | ~ | | +| [Sony AS-DT1] | ToF | up to 40 m | UART | ~ | Multipoint distance sensor | +| [LightWare SF02] _(disc.)_ | ToF (IR laser) | ~50 m | UART | ~ | Discontinued | +| [LightWare SF10/A] _(disc.)_ | ToF (IR laser) | ~25 m | UART, I2C | ~ | Discontinued | +| [LightWare SF10/B] _(disc.)_ | ToF (IR laser) | ~50 m | UART, I2C | ~ | Discontinued | +| [LightWare SF10/C] _(disc.)_ | ToF (IR laser) | ~100 m | UART, I2C | ~ | Discontinued | +| [Lanbao PSK-CM8JL65-CC5] _(disc.)_ | ToF (IR) | 0.17 m – 8 m | UART | ✖️ | Discontinued | +| [Smartmicro Drone Altimeter] | Microwave radar | 1 m to 175 m | DroneCAN | ~ | | +| [TeraRanger Evo 60m] _(disc.)_ | ToF (IR) | 0.5 m – 60 m | I2C | ~ | Discontinued | +| [TeraRanger Evo 600Hz] _(disc.)_ | ToF (IR) | 0.75 m – 8 m | I2C | ~ | Discontinued | +| [TeraRanger Evo 3m] _(disc.)_ | ToF (IR) | 0.1 m – 3 m | I2C | ~ | Discontinued | +| [TeraRanger One] _(disc.)_ | ToF (IR) | 0.2 m – 14 m | I2C | ~ | Discontinued | [Ainstein US-D1 Standard Radar Altimeter]: ../sensor/ulanding_radar.md [ARK DIST SR]: ../dronecan/ark_dist.md [ARK DIST MR]: ../dronecan/ark_dist_mr.md [Benewake TFmini]: ../sensor/tfmini.md +[Garmin LIDAR-Lite v3]: ../sensor/lidar_lite.md [Holybro ST VL53L1X Lidar]: #holybro-st-vl53l1x-lidar [Lanbao PSK-CM8JL65-CC5]: ../sensor/cm8jl65_ir_distance_sensor.md [LeddarOne]: ../sensor/leddar_one.md -[Lidar-Lite]: ../sensor/lidar_lite.md [LightWare Lidar]: ../sensor/sfxx_lidar.md [LightWare SF11/C]: ../sensor/sfxx_lidar.md [LightWare LW20/C]: ../sensor/sfxx_lidar.md @@ -59,8 +60,9 @@ There may also be other DroneCAN rangefinders than those listed here. [MaxBotix I2CXL-MaxSonar-EZ]: #maxbotix-i2cxl-maxsonar-ez [Smartmicro Drone Altimeter]: ../dronecan/smartmicro_t132.md [Sony AS-DT1]: ../sensor/sony_asdt1.md -[TeraRanger Evo 60 m]: ../sensor/teraranger.md +[TeraRanger Evo 60m]: ../sensor/teraranger.md [TeraRanger Evo 600Hz]: ../sensor/teraranger.md +[TeraRanger Evo 3m]: ../sensor/teraranger.md [TeraRanger One]: ../sensor/teraranger.md These adaptors allows you to connect a non-CAN rangefinder via the CAN interface. @@ -90,10 +92,10 @@ The [VL53L1X](https://holybro.com/products/st-vl53l1x-lidar) is a state-of-the-a It comes with a JST GHR 4 pin connector that is compatible with the I2C port on [Pixhawk 4](../flight_controller/pixhawk4.md), [Pixhawk 5X](../flight_controller/pixhawk5x.md), and other flight controllers that follow the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf). -### Lidar-Lite +### Garmin LIDAR-Lite -[Lidar-Lite](../sensor/lidar_lite.md) is a compact, high-performance optical distant measurement rangefinder. -It has a sensor range from (5cm - 40m) and can be connected to either PWM or I2C ports. +The [Garmin LIDAR-Lite v3](../sensor/lidar_lite.md) is a compact laser time-of-flight rangefinder with a range of up to 40 m (PX4 caps this to 35 m or less). +It can be connected to either I2C or PWM ports. ### MaxBotix I2CXL-MaxSonar-EZ @@ -120,10 +122,11 @@ PX4 configures the sensor baud rate and measurement output from the driver. ### TeraRanger 거리계 -[TeraRanger](../sensor/teraranger.md) provide a number of lightweight distance measurement sensors based on infrared Time-of-Flight (ToF) technology. -They are typically faster and have greater range than sonar, and smaller and lighter than laser-based systems. + -PX4 supports the following models connected via the I2C bus: TeraRanger One, TeraRanger Evo 60m and TeraRanger Evo 600Hz. +[Terabee TeraRanger](../sensor/teraranger.md) sensors are small, lightweight rangefinders based on infrared Time-of-Flight (ToF) technology, with maximum ranges from 3 m to 60 m (depending on the model). + +PX4 supports the following models connected via the I2C bus: TeraRanger Evo 60m, TeraRanger Evo 600Hz, TeraRanger Evo 3m and TeraRanger One. ### Ainstein US-D1 Standard Radar Altimeter @@ -199,6 +202,23 @@ These include (non exhaustively): - [EKF2_RNG_SFE](../advanced_config/parameter_reference.md#EKF2_RNG_SFE) - Range finder range dependent noise scaler. - [EKF2_RNG_NOISE](../advanced_config/parameter_reference.md#EKF2_RNG_NOISE) - Measurement noise for range finder fusion +### Health Reporting + +PX4 reports the rangefinder status to ground stations in the [SYS_STATUS](https://mavlink.io/en/messages/common.html#SYS_STATUS) message, using the `MAV_SYS_STATUS_SENSOR_LASER_POSITION` bit (this bit is used for all distance sensor types, not just lasers): + +- `onboard_control_sensors_present`: set once any distance sensor has published data. +- `onboard_control_sensors_health`: cleared if a required distance sensor is missing or stops providing valid data (no update for more than 1 second). + +The required distance sensors are the first [SYS_HAS_NUM_DIST](../advanced_config/parameter_reference.md#SYS_HAS_NUM_DIST) sensors. +For example, with `SYS_HAS_NUM_DIST` set to 2 and three sensors connected, only the first two affect the health bit. +A required sensor that fails also blocks arming. + +WARNING : `SYS_HAS_NUM_DIST` is `0` by default, which means no distance sensor is required. +The health bit is then always reported as healthy, even if a rangefinder stops working. +Set `SYS_HAS_NUM_DIST` if you want rangefinder failures to be reported. + +You can check these bits in the `SYS_STATUS` message using the [QGroundControl MAVLink Inspector](#qgroundcontrol-mavlink-inspector). + ## 시험 The easiest way to test the rangefinder is to vary the range and compare to the values detected by PX4. diff --git a/docs/ko/sensor/teraranger.md b/docs/ko/sensor/teraranger.md index 6681cdc7a35..c21b9fe4710 100644 --- a/docs/ko/sensor/teraranger.md +++ b/docs/ko/sensor/teraranger.md @@ -1,46 +1,149 @@ -# TeraRanger Rangefinders (Discontinued) +# Terabee TeraRanger Rangefinders (Discontinued) + + :::warning TeraRanger Evo sensors were discontinued by Terabee in May 2024. -Limited stock may still be available from third-party resellers such as [Tribotix](https://tribotix.com/product/teraranger-evo-60m/). +Limited stock may still be available from third-party resellers (see [Where to Buy](#store)). ::: -TeraRanger는 적외선 ToF(Time-of-Flight) 기반의 다양한 경량 거리측정 센서입니다. -They are typically faster and have greater range than sonar, and smaller and lighter than laser-based systems. - -PX4는 아래 장치들을 지원합니다. - -- [TeraRanger Evo 60m](https://tribotix.com/product/teraranger-evo-60m/) (0.5 – 60 m) -- [TeraRanger Evo 600Hz](https://tribotix.com/product/teraranger-evo-600hz/) (0.75 - 8 m) +Terabee TeraRanger sensors are small, lightweight [rangefinders](../sensor/rangefinders.md) based on infrared Time-of-Flight (ToF) technology, with maximum ranges from 3 m to 60 m (depending on the model). +They connect to the flight controller using I2C. :::info -PX4 also supports _TeraRanger One_ (I2C adapter required). -This has been discontinued. +The driver for these rangefinders is not included in PX4 firmware by default. +See [Firmware Support](#firmware_support) for how to add it. ::: -## 구매처 +## Supported Models {#supported_models} -- TBD +PX4 supports the following models. -## 핀배열 +| 모델 | 범위 | Current draw | [SENS\_EN\_TRANGER][SENS_EN_TRANGER] | 참고 | +| -------------------- | ------------------------ | ------------ | ------------------------------------ | ---------------------------------------------------- | +| TeraRanger Evo 60m | 0.5–60 m | 90–330 mA | `3` | Requires the Evo I2C/UART backboard. | +| TeraRanger Evo 600Hz | 0.75–8 m | 95–190 mA | `4` | Requires the Evo I2C/UART backboard. | +| TeraRanger Evo 3m | 0.1–3 m | 70–250 mA | `5` | Requires the Evo I2C/UART backboard. | +| TeraRanger One | 0.2–14 m | | `2` | | -## 배선 +[SENS_EN_TRANGER]: ../advanced_config/parameter_reference.md#SENS_EN_TRANGER -모든 TeraRanger 센서는 I2C 버스로 연결됩니다. +## Specifications {#specifications} -## 소프트웨어 설정 +The following specifications apply to TeraRanger Evo sensors fitted with the Evo I2C/UART backboard. -The sensors are enabled using the parameter [SENS_EN_TRANGER](../advanced_config/parameter_reference.md#SENS_EN_TRANGER) (you can set the type of sensor or that PX4 should auto-detect the type). +- **Technology:** Infrared Time-of-Flight (LED) +- **Field of view:** Approx. 2° (Evo 60m) +- **Interface:** I2C (3.3 V logic, address `0x31`) +- **Input voltage:** 5 V DC ±5% +- **Dimensions:** Approx. 29 x 29 x 22 mm (sensor and backboard) +- **Weight:** 9 g (sensor) + 3 g (backboard) + +## Where to Buy {#store} + +TeraRanger sensors are no longer sold by Terabee. +At the time of writing the following are still listed by the reseller Tribotix: + +- [TeraRanger Evo 60m](https://tribotix.com/product/teraranger-evo-60m/) +- [TeraRanger Evo 600Hz](https://tribotix.com/product/teraranger-evo-600hz/) +- [TeraRanger Evo 3m](https://tribotix.com/product/teraranger-evo-3m/) + +Select the **I2C/UART** interface option when ordering (PX4 cannot use the USB backboard). + +## Hardware Setup {#hardware_setup} + +### Mounting {#mounting} + +PX4 assumes that the sensor is facing down (the orientation cannot be configured). + +For TeraRanger Evo sensors: + +- Do not mount anything directly in front of the sensor, or within a cone of approximately ±15° around its optical axis. +- Within the first metre, avoid highly reflective objects within a cone of approximately ±45° around the optical axis. +- Do not add a cover in front of the sensor. +- Rotor blades in the field of view can affect the readings. + +### Pinouts {#pinouts} + +TeraRanger Evo sensors must be fitted with the Evo I2C/UART backboard, which has a single 9-pin Hirose DF13 connector. + +| 핀 | 신호 | 설명 | +| - | --- | -------------------------------------------------------------- | +| 1 | Tx | UART transmit (3.3 V logic) | +| 2 | Rx | UART receive (3.3 V logic) | +| 3 | GND | 접지 | +| 4 | SDA | I2C data (3.3 V logic) | +| 5 | SCL | I2C clock (3.3 V logic) | +| 6 | - | Reserved | +| 7 | 5V | +5 V supply input | +| 8 | GND | 접지 | +| 9 | - | Reserved | + +### Wiring {#wiring} + +All TeraRanger sensors must be connected via the I2C bus, using an external `I2C` port on the flight controller. + +| Backboard pin | Connect to | +| ------------------------------- | ------------------------- | +| 4 (SDA) | Flight controller I2C SDA | +| 5 (SCL) | Flight controller I2C SCL | +| 7 (5V) | 5 V DC supply | +| 3 or 8 (GND) | Flight controller GND | + +The UART pins are not used by PX4. + +The sensor requires a 5 V DC (±5%) supply, and can draw up to 330 mA depending on the [supported model](#supported_models). +Check that the flight controller port can supply this, or power the sensor from a separate supply that shares a ground with the flight controller. + +The backboard has built-in 10 kΩ pull-up resistors on SDA and SCL, so do not add further pull-ups on the same bus. +The sensor must be left at its default I2C address (`0x31`). + +## Firmware Support {#firmware_support} + +The rangefinder is supported by the [teraranger](../modules/modules_driver_distance_sensor.md#teraranger) driver, which is built into firmware by the [board configuration](../hardware/porting_guide_config.md) key `CONFIG_DRIVERS_DISTANCE_SENSOR_TERARANGER=y`. + +The driver is not part of the common set of rangefinder drivers (`CONFIG_COMMON_DISTANCE_SENSOR`), so it is only present in the firmware for boards that set that key. + +To check your board, look for the key in its configuration file, `boards///default.px4board`, or check whether [SENS\_EN\_TRANGER][SENS_EN_TRANGER] is listed in _QGroundControl_ (parameters are only shown for drivers that are in the firmware). + +To add the driver, add the key to the board's `default.px4board` file, or enable it in [boardconfig](../hardware/porting_guide_config.md#px4-menuconfig-setup) under **Drivers > Distance sensors**, and then [build and upload the firmware](../dev_setup/building_px4.md). + +The driver does not start until it is enabled using the parameter in [PX4 Configuration](#px4_configuration). + +## PX4 Configuration {#px4_configuration} + +Set [SENS\_EN\_TRANGER][SENS_EN_TRANGER] to the value for your sensor in the [Supported Models](#supported_models) table, and then reboot. + +You can instead set the parameter to `1` to have PX4 detect the sensor. :::info -If using auto-detect for Evo sensors the minimum and maximum values for the range are set to the lowest and highest possible readings across the Evo family (currently 0.5 - 60 m). +If using auto-detect for Evo sensors the minimum and maximum values for the range are set to the lowest and highest possible readings across the Evo family (currently 0.1–60 m). 올바른 최대/최소 값을 사용하려면 Evo 센서의 적절한 모델을 매개변수에 설정합니다 (자동 감지를 사용하는 대신). ::: -:::tip -The driver for this rangefinder is usually present in firmware. If missing, you would also need to add the driver (`distance_sensor/teraranger`) to the board configuration. -::: +If the parameter is not available in _QGroundControl_ then the driver is not in the firmware: see [Firmware Support](#firmware_support). -## 추가 정보 +The configuration that is common to all rangefinders, such as the sensor position offsets used by the estimator, is covered in [Rangefinders > Configuration/Setup](../sensor/rangefinders.md#configuration). -- [Modules Reference: Distance Sensor (Driver) : teraranger](../modules/modules_driver_distance_sensor.md#teraranger) +## Testing {#testing} + +You can check that the driver is running, and see its error counters, using the _QGroundControl MAVLink Console_: + +```sh +teraranger status +``` + +You can observe the published measurements with: + +```sh +listener distance_sensor +``` + +The measurements can also be viewed in the `DISTANCE_SENSOR` message in the _QGroundControl MAVLink Inspector_. +For more information see [Rangefinders > Testing](../sensor/rangefinders.md#testing). + +## Further Information {#further_information} + +- [Modules Reference: Distance Sensor (Driver): teraranger](../modules/modules_driver_distance_sensor.md#teraranger) +- [User Manual for TeraRanger Evo single point distance sensors and backboards](https://web.archive.org/web/20240611084754/http://www.terabee.com/wp-content/uploads/2021/02/User-Manual-for-TeraRanger-Evo-single-point-distance-sensors-and-backboards.pdf) (Terabee, archived copy) +- [TeraRanger Evo Specification Sheet](https://acroname.com/sites/default/files/assets/teraranger-evo-specification-sheet.pdf) (Terabee, hosted by Acroname)