Mirrors_Framework/PX4-Autopilot
1
0
Fork 0
mirror of https://github.com/PX4/PX4-Autopilot.git synced 2026-10-06 09:02:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2026-07-22 15:27:20 +10:00
committed by GitHub
co-authored by Crowdin Bot
parent 2997ab7b81
commit dfe32bf6c0
31 changed files with 1503 additions and 180 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ko/SUMMARY.md
+1
View File
@@ -884,6 +884,7 @@
- [Log Encryption](dev_log/log_encryption.md)
- [고급 주제](advanced/index.md)
- [PX4 Metadata](advanced/px4_metadata.md)
- [Detect and Avoid](advanced_features/detect_and_avoid.md)
- [Package Delivery Architecture](advanced/package_delivery.md)
- [Camera Integration/Architecture](camera/camera_architecture.md)
- [컴퓨터 비전](advanced/computer_vision.md)
docs/ko/advanced/rtk_gps.md
+5 -1
View File
@@ -34,6 +34,10 @@ The PX4 GPS stack automatically sets up the GPS modules to send and receive the
As soon as the autopilot receives `GPS_RTCM_DATA` MAVLink messages, it reassembles fragmented packets when needed and then forwards the RTCM data to the attached GPS module over existing data channels (a dedicated channel for correction data is not required).
:::info
Firmware built with `CONFIG_GPS_SPARTN` (default off; enabled on selected targets such as ARK GNSS nodes and SITL) also frames [SPARTN](https://www.spartnformat.org/) corrections on that same inject path — for example u-blox PointPerfect streams carried in `GPS_RTCM_DATA` / `rtcm_corrections`. PX4 does not provision SPARTN decryption keys; those must already be configured on the receiver.
:::
:::info
The u-blox U-Center RTK module configuration tool is not needed/used!
:::
@@ -51,7 +55,7 @@ If you are sending RTCM corrections to PX4 yourself, follow the MAVLink [`GPS_RT
- If the RTCM payload exceeds 180 bytes, split it across up to 4 packets using the Fragment ID and Sequence ID (encoded in `GPS_RTCM_DATA.flags`).
Every packet except the last one must be filled to its maximum 180-byte capacity; only the final packet may be partially filled.
- PX4 reassembles fragmented packets according to the MAVLink rules and supports out-of-order delivery for one in-progress fragmented message at a time.
- A fragmented message is considered complete when either 4 fragments with the same Sequence ID have been received, or when you receive a partial fragment and you have already recieved all the fully-packed fragments that precede it (by Fragment ID) in the current sequence.
- A fragmented message is considered complete when either 4 fragments with the same Sequence ID have been received, or when you receive a partial fragment and you have already received all the fully-packed fragments that precede it (by Fragment ID) in the current sequence.
- If the RTCM payload length is an exact multiple of 180 bytes and uses fewer than 4 fragments, the sender must still send a final zero-length fragment to mark completion. A 720-byte payload (all 4 fragments full) is complete after the last fragment is received.
- As a compatibility fallback for older QGroundControl builds that omit that final zero-length fragment, PX4 also flushes a buffered RTCM message to the GNSS when a `GPS_RTCM_DATA` message with a different Sequence ID arrives, but only if the buffered fragments are a gap-free run of full 180-byte fragments starting at fragment 0.
docs/ko/advanced_features/detect_and_avoid.md
+1032
View File
File diff suppressed because it is too large Load Diff
docs/ko/advanced_features/index.md
+1
View File
@@ -3,6 +3,7 @@
PX4 자동비행 프로그램의 고급 기능에 대하여 설명합니다.
- [Air Traffic Avoidance: ADS-B/FLARM/UTM](../peripherals/adsb_flarm.md)
- [Detect And Avoid](../advanced_features/detect_and_avoid.md)
- [Computer Vision](../computer_vision/index.md)
- [Collision Prevention](../computer_vision/collision_prevention.md)
- [Motion Capture (MoCap)](../computer_vision/motion_capture.md)
docs/ko/config/safety.md
+13 -4
View File
@@ -276,13 +276,22 @@ The _Offboard Loss Failsafe_ is triggered if the offboard link is lost while und
## 교통 회피 안전 장치
The Traffic Avoidance Failsafe allows PX4 to respond to transponder data (e.g. from [ADSB transponders](../advanced_features/traffic_avoidance_adsb.md)) during missions.
The Traffic Avoidance Failsafe allows PX4 to respond to [cooperative traffic reports](../peripherals/adsb_flarm.md).
The action parameters depend on the conflict model selected when the firmware is built.
관련된 매개 변수는 다음과 같습니다.
| Parameter | 설명 |
| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [NAV_TRAFF_AVOID](../advanced_config/parameter_reference.md#NAV_TRAFF_AVOID) | 비상 안전 장치를 설정합니다 : 비활성화, 경고, 귀환 모드, 착륙 모드. |
| Parameter | 설명 |
| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| [DAA_EN](../advanced_config/parameter_reference.md#DAA_EN) | Enables or disables Detect and Avoid. |
| [NAV_TRAFF_AVOID](../advanced_config/parameter_reference.md#NAV_TRAFF_AVOID) | Action for the Crosstrack model. |
| [DAA_LVL_LOW_ACT](../advanced_config/parameter_reference.md#DAA_LVL_LOW_ACT) | F3442-mode action for a `LOW` conflict. |
| [DAA_LVL_MED_ACT](../advanced_config/parameter_reference.md#DAA_LVL_MED_ACT) | F3442-mode action for a `MEDIUM` conflict. |
| [DAA_LVL_HIGH_ACT](../advanced_config/parameter_reference.md#DAA_LVL_HIGH_ACT) | F3442-mode action for a `HIGH` conflict. |
| [DAA_LVL_CRIT_ACT](../advanced_config/parameter_reference.md#DAA_LVL_CRIT_ACT) | F3442-mode action for a `CRITICAL` conflict. |
All action parameters use `Disabled`, `Warn only`, `Return mode`, `Land mode`, `Position Hold mode`, and `Terminate`.
See [Detect and Avoid](../advanced_features/detect_and_avoid.md) for conflict-model and action-transition details.
## Remote ID Failsafe
docs/ko/debug/failure_injection.md
+29 -2
View File
@@ -5,7 +5,7 @@ This enables easier testing of [safety failsafe](../config/safety.md) behaviour,
Failure injection is disabled by default, and can be enabled using the [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN) parameter.
Failure injection must also be be supported by the current simulator, and the set of supported failures is simulator-dependent.
Failures can be injected both in simulation and on real hardware. In simulation the available failures depend on the simulator. On hardware the `off` (stop publishing) and `stuck` (freeze the last value) types are supported for the `gyro`, `accel`, `mag`, `baro`, `distance_sensor` and `gps` components; this requires firmware built with the failure-injection module. In addition, the `battery` component supports `off` (report a depleted pack, triggering the battery failsafe).
:::info
PX4 may accept a command to set a particular failure mode even it that mode is not supported by your simulator.
@@ -24,7 +24,7 @@ Failures can be injected using the [failure system command](../modules/modules_c
The full syntax of the [failure](../modules/modules_command.md#failure) command is:
```sh
failure <component> <failure_type> [-i <instance_number>]
failure <component> <failure_type> [-i <instance_number>] [-m <instance_bitmask>]
```
여기서:
@@ -58,11 +58,23 @@ failure <component> <failure_type> [-i <instance_number>]
- `intermittent`: Publish intermittently
- _instance number_ (optional): Instance number of affected sensor.
0 (기본값) 지정된 유형의 모든 센서를 나타냅니다.
- _instance bitmask_ (optional): address several instances at once (bit 0 = first instance, bit 1 = second, …; decimal or `0x` hex). Used only when `-i` is omitted. Example: `-m 0x5` targets instances 1 and 3.
:::info
The simulated GPS (SITL) implements only the `off`, `stuck`, and `wrong` failure modes; the other failure types have no effect on it.
:::
## RC Switch Trigger
A failure can also be injected from an RC switch, without a console or telemetry link. This is useful for in-flight hardware testing. It is configured with the following parameters:
- [SYS_FAIL_RC_SRC](../advanced_config/parameter_reference.md#SYS_FAIL_RC_SRC): the auxiliary RC input that triggers the failure — `0` disables it, `1`–`6` select AUX1–AUX6 (mapped via `RC_MAP_AUXn`).
- [SYS_FAIL_RC_UNIT](../advanced_config/parameter_reference.md#SYS_FAIL_RC_UNIT): the affected component (the `FAILURE_UNIT` value; e.g. `101` = motor).
- [SYS_FAIL_RC_MODE](../advanced_config/parameter_reference.md#SYS_FAIL_RC_MODE): the failure type (the `FAILURE_TYPE` value; e.g. `1` = off).
- [SYS_FAIL_RC_INST](../advanced_config/parameter_reference.md#SYS_FAIL_RC_INST): the affected instance (1-based; `0` = all instances).
While the selected aux switch is on the configured failure is injected; switching it back off clears the failure. The injection goes through the same path as the console/MAVLink commands, so for a motor it stops the motor exactly as `failure motor off` does (which also requires [CA_FAILURE_MODE](../advanced_config/parameter_reference.md#CA_FAILURE_MODE)).
## MAVSDK 실패 플러그인
The [MAVSDK failure plugin](https://mavsdk.mavlink.io/main/en/cpp/api_reference/classmavsdk_1_1_failure.html) can be used to programmatically inject failures.
@@ -100,3 +112,18 @@ To stop a motor mid-flight without the system anticipating it or excluding it fr
# Turn it back on
failure motor ok -i 1
```
## Example: Battery
To trigger the battery failsafe by reporting a depleted pack:
1. Enable the [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN) parameter.
2. Enter the following commands on the MAVLink console or SITL _pxh shell_:
```sh
# Report the battery as depleted (warning EMERGENCY) -> battery failsafe
failure battery off
# Stop injecting the failure
failure battery ok
```
docs/ko/dronecan/ark_cannode.md
+1 -1
View File
@@ -85,7 +85,7 @@ On the ARK CANnode, you may need to configure the following parameters:
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. |
## LED 신호의 의미
docs/ko/dronecan/ark_flow.md
+1 -1
View File
@@ -112,7 +112,7 @@ On the ARK Flow, you may need to configure the following parameters:
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. |
## LED 신호의 의미
docs/ko/dronecan/ark_flow_mr.md
+1 -1
View File
@@ -107,7 +107,7 @@ You may need to [configure the following parameters](../dronecan/index.md#qgc-ca
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. |
## LED 신호의 의미
docs/ko/dronecan/ark_gps.md
+1 -1
View File
@@ -99,7 +99,7 @@ You may need to [configure the following parameters](../dronecan/index.md#qgc-ca
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. Set to `1` if this is the last node on the CAN bus. |
## LED 신호의 의미
docs/ko/dronecan/ark_rtk_gps.md
+1 -1
View File
@@ -94,7 +94,7 @@ You may need to [configure the following parameters](../dronecan/index.md#qgc-ca
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. Set to `1` if this is the last node on the CAN bus. |
### Setting Up Rover and Fixed Base
docs/ko/dronecan/ark_rtk_gps_l1_l2.md
+1 -1
View File
@@ -93,7 +93,7 @@ You may need to [configure the following parameters](../dronecan/index.md#qgc-ca
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. Set to `1` if this is the last node on the CAN bus. |
### Setting Up Rover and Fixed Base
docs/ko/dronecan/ark_x20_rtk_gps.md
+1 -1
View File
@@ -96,7 +96,7 @@ You may need to [configure the following parameters](../dronecan/index.md#qgc-ca
| Parameter | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-127 to use a static node ID. |
| <a id="CANNODE_NODE_ID"></a>[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) | CAN node ID (0 for dynamic allocation). If set to 0 (default), dynamic node allocation is used. Set to 1-125 to use a static node ID. |
| <a id="CANNODE_TERM"></a>[CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM) | CAN built-in bus termination. Set to `1` if this is the last node on the CAN bus. |
### Setting Up Rover and Fixed Base
docs/ko/dronecan/index.md
+3 -22
View File
@@ -109,7 +109,7 @@ The parameter is set to 1 by default.
Devices running the [PX4 DroneCAN firmware](px4_cannode_fw.md) (such as [ARK CANnode](ark_cannode.md)) can use the
[CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) parameter to set a static node ID.
Set it to 0 (default) for dynamic allocation, or to a value between 1-127 to use a specific static node ID.
Set it to 0 (default) for dynamic allocation, or to a value between 1-125 to use a specific static node ID.
:::
:::warning
@@ -306,7 +306,7 @@ For example, the screenshot below shows the parameters for a CAN GPS with node i
Common CANNODE parameters that you can configure include:
- [CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID): Set a static node ID (1-127) or use 0 for dynamic allocation. See [PX4 DroneCAN Firmware > Static Node ID](px4_cannode_fw.md#static-node-id) for more information.
- [CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID): Set a static node ID (1-125) or use 0 for dynamic allocation. See [PX4 DroneCAN Firmware > Static Node ID](px4_cannode_fw.md#static-node-id) for more information.
- [CANNODE_TERM](../advanced_config/parameter_reference.md#CANNODE_TERM): Enable CAN bus termination on the last node in the bus.
## Device Specific Setup
@@ -334,31 +334,12 @@ On boot, PX4 scans both locations, reads the board ID from the _APDescriptor_ of
The source file is then deleted.
Any connected node whose running version does not match is then flashed over the CAN bus.
### Firmware Database
A flat-file database at `/fs/microsd/ufw/FW.db` maps each board ID to the original firmware filename that was installed.
This may be queried by external tools to determine current firmware versions.
Example entry:
```txt
122.bin=122-1.17.63eeff1a.uavcan.bin
```
Entries are removed on boot if their corresponding firmware is not present.
### Remote Update
Remote updates can be made by uploading the corresponding bin files to `/fs/microsd/ufw_staging/`.
PX4 will then update firmware on next boot.
This approach enables efficient mass-update of binaries from archives (`.zip` or `.tar` that contains `.bin` files for the target CAN nodes).
Tools can:
1. Read the PX4 firmware database to determine what firmware is present
2. Extract the more-recent versions of matching firmware to the staging directory
PX4 does not provide such tools.
:::info
Auterion uses a form of this workflow to update CAN firmware to SkyNode based devices.
@@ -372,7 +353,7 @@ The `upload_skynode.sh` script with multiple `--ext-fw` flags is used to bundle
--ext-fw=build/auterion_canio_default/some_other_default.uavcan.bin
```
Another tool then checks the firmware database and extracts just the relevant files to the PX4 firmware staging area.
Another tool then checks which files were already uploaded using a local database and extracts just the relevant files to the PX4 firmware staging area.
:::
## 문제 해결
docs/ko/dronecan/px4_cannode_fw.md
+1 -1
View File
@@ -29,7 +29,7 @@ However, you can configure a static node ID using the [CANNODE_NODE_ID](../advan
To configure a static node ID:
1. Set [CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) to a value between 1-127 using [QGroundControl](index.md#qgc-cannode-parameter-configuration)
1. Set [CANNODE_NODE_ID](../advanced_config/parameter_reference.md#CANNODE_NODE_ID) to a value between 1-125 using [QGroundControl](index.md#qgc-cannode-parameter-configuration)
2. Reboot the device
To return to dynamic allocation, set `CANNODE_NODE_ID` back to 0.
docs/ko/middleware/dds_topics.md
+3 -1
View File
@@ -131,6 +131,8 @@ See messages
- [DebugKeyValue](../msg_docs/DebugKeyValue.md)
- [DebugValue](../msg_docs/DebugValue.md)
- [DebugVect](../msg_docs/DebugVect.md)
- [DetectAndAvoid](../msg_docs/DetectAndAvoid.md)
- [DetectAndAvoidMostUrgent](../msg_docs/DetectAndAvoidMostUrgent.md)
- [DeviceInformation](../msg_docs/DeviceInformation.md)
- [DifferentialPressure](../msg_docs/DifferentialPressure.md)
- [DistanceSensorModeChangeRequest](../msg_docs/DistanceSensorModeChangeRequest.md)
@@ -184,7 +186,6 @@ See messages
- [GpioOut](../msg_docs/GpioOut.md)
- [GpioRequest](../msg_docs/GpioRequest.md)
- [GpsDump](../msg_docs/GpsDump.md)
- [GpsInjectData](../msg_docs/GpsInjectData.md)
- [Gripper](../msg_docs/Gripper.md)
- [HealthReport](../msg_docs/HealthReport.md)
- [HeaterStatus](../msg_docs/HeaterStatus.md)
@@ -254,6 +255,7 @@ See messages
- [RoverRateStatus](../msg_docs/RoverRateStatus.md)
- [RoverSpeedStatus](../msg_docs/RoverSpeedStatus.md)
- [Rpm](../msg_docs/Rpm.md)
- [RtcmData](../msg_docs/RtcmData.md)
- [RtlStatus](../msg_docs/RtlStatus.md)
- [RtlTimeEstimate](../msg_docs/RtlTimeEstimate.md)
- [SatelliteInfo](../msg_docs/SatelliteInfo.md)
docs/ko/middleware/zenoh.md
+3 -4
View File
@@ -151,7 +151,7 @@ These are applied to all Zenoh publishers.
If `CONFIG_ZENOH_PUB_OPTION_OVERRIDE=y`, individual publishers can override one or more global publisher options.
Default configuration [dds_topics.yaml](../middleware/dds_topics.md) already provides overrides for several publishers.
Individual publisher options can be overriden through the mapping configuration shown in the next section
Individual publisher options can be overridden through the mapping configuration shown in the next section
### 4. Modifying Topic Mappings
@@ -262,6 +262,5 @@ The PX4 ROS 2 Interface Library is not compatible with ROS 2 Humble and earlier,
ERROR [zenoh] Could not create a subscriber for type ***
```
When it happens, check if `src/modules/zenoh/Kconfig.topics` has unstaged changes.
If there are any it means that new uorb topics have been added and the previous build updated the `Kconfig.topics` file accordingly.
Please perform a clean build so that the new `Kconfig.topics` can be used.
This usually means the firmware was built with a different set of uORB topics than the peer expects.
The Zenoh topic catalog (`Kconfig.topics`) is generated automatically at configure time into the build directory, so performing a clean build picks up any newly added or changed topics.
docs/ko/modules/modules_command.md
+1
View File
@@ -121,6 +121,7 @@ failure [arguments...]
ok|off|... Specify failure type
[-i <val>] sensor instance (0=all)
default: 0
[-m <val>] instance bitmask (bit i = instance i+1); overridden by -i
```
## gpio
docs/ko/modules/modules_controller.md
+1 -1
View File
@@ -287,7 +287,7 @@ navigator <command> [arguments...]
fencefile load a geofence file from SD card, stored at etc/geofence.txt
fake_traffic publishes 24 fake transponder_report_s uORB messages
fake_traffic run synthetic DAA traffic; use 'navigator fake_traffic help'
stop
docs/ko/modules/modules_driver.md
+3 -2
View File
@@ -358,7 +358,7 @@ Source: [drivers/gps](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers
### 설명
GPS driver module that handles the communication with the device and publishes the position via uORB.
It supports multiple protocols (device vendors) and by default automatically selects the correct one.
The available device protocols are selected at build time.
The module supports a secondary GPS device, specified via `-e` parameter. The position will be published
on the second uORB topic instance, but it's currently not used by the rest of the system (however the
@@ -401,7 +401,8 @@ gps <command> [arguments...]
values: spi|uart, default: uart
[-j <val>] secondary GPS interface
values: spi|uart, default: uart
[-p <val>] GPS Protocol (default=auto select)
[-p <val>] GPS protocol (availability depends on build; default from
GPS_x_PROTOCOL)
values: ubx|mtk|ash|eml|fem|nmea
stop
docs/ko/modules/modules_driver_camera.md
+1 -1
View File
@@ -11,7 +11,7 @@ Camera trigger driver.
This module triggers cameras that are connected to the flight-controller outputs,
or simple MAVLink cameras that implement the MAVLink trigger protocol.
The driver responds to the following MAVLink trigger commands being found in missions or recieved over MAVLink:
The driver responds to the following MAVLink trigger commands being found in missions or received over MAVLink:
- `MAV_CMD_DO_TRIGGER_CONTROL`
- `MAV_CMD_DO_DIGICAM_CONTROL`
docs/ko/modules/modules_system.md
+14 -7
View File
@@ -262,14 +262,21 @@ Source: [modules/failure_injection_manager](https://github.com/PX4/PX4-Autopilot
### 설명
The failure injection manager is the single subscriber to `vehicle_command` for
`MAV_CMD_INJECT_FAILURE`. It maintains the set of currently active failures and
publishes the `failure_injection` topic, republishing only when the configuration
changes so that command spam cannot propagate to the consumers that apply the
failures. It also produces the central `vehicle_command_ack`.
Central module for handling failure injection. It collects failure requests, tracks
the set of active failures, and publishes them on the `failure_injection` topic for
the apply-sites to act on.
Failure injection is gated by the `SYS_FAILURE_EN` parameter, which the startup
script checks before starting this module.
Failures can be triggered through:
- `MAV_CMD_INJECT_FAILURE` over MAVLink (e.g. from MAVSDK)
- the `failure` console command
- an RC switch: `SYS_FAIL_RC_SRC` selects the aux input, and `SYS_FAIL_RC_UNIT` /
`SYS_FAIL_RC_MODE` / `SYS_FAIL_RC_INST` define the failure applied while it is on
Requires `SYS_FAILURE_EN` to be set; the startup script only starts this module when it is.
Failures can be applied both in simulation and on real hardware, where the apply-sites are
compiled in alongside this module.
### Usage {#failure_injection_manager_usage}
docs/ko/msg_docs/DetectAndAvoid.md
+93
View File
@@ -0,0 +1,93 @@
---
pageClass: is-wide-page
---
# DetectAndAvoid (UORB message)
Detect-and-avoid conflict assessment for one traffic aircraft.
Detailed per-traffic output from navigator's `DetectAndAvoid` component.
A sample is published when an evaluated report indicates a conflict or updates
an aircraft already tracked as a conflict. New reports assessed at NONE are omitted.
Unlike `detect_and_avoid_most_urgent`, this topic does not summarize the single
active conflict driving DAA actions or prearm checks. It reports the conflict level
and geometry for the specific traffic aircraft that was just evaluated.
Published by: `navigator` (`DetectAndAvoid`)
Used by: logging and tests
**TOPICS:** detect_and_avoid
## Fields
| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 |
| ---------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
| <a id="fld_unique_id"></a>unique_id | `uint64` | | | Encoded traffic identifier selected in priority order: ICAO address, ADS-B callsign, then reduced UAS ID tail bytes |
| <a id="fld_unique_id_encoding"></a>unique_id_encoding | `uint8` | | | Namespace used to decode `unique_id` |
| <a id="fld_conflict_level"></a>conflict_level | `uint8` | | | Conflict level calculated for this traffic aircraft |
| <a id="fld_aircraft_dist"></a>aircraft_dist | `float32` | m | | Current 3D point-to-point range between ownship and the traffic aircraft |
| <a id="fld_aircraft_dist_hor"></a>aircraft_dist_hor | `float32` | m [NED] | | Horizontal separation metric. In Crosstrack mode this is the signed crosstrack distance when available, otherwise direct horizontal range |
| <a id="fld_aircraft_dist_vert"></a>aircraft_dist_vert | `float32` | m [NED] | | Vertical separation between ownship (the current vehicle) and the traffic aircraft |
| <a id="fld_expected_min_dist_time"></a>expected_min_dist_time | `float32` | s | | Conservative collision-time estimate from current 3D separation and the sum of ownship and traffic speed magnitudes |
## Constants
| 명칭 | 형식 | Value | 설명 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | ------------------------------------------------------------- |
| <a id="#DAA_CONFLICT_LVL_NONE"></a> DAA_CONFLICT_LVL_NONE | `uint8` | 0 | |
| <a id="#DAA_CONFLICT_LVL_LOW"></a> DAA_CONFLICT_LVL_LOW | `uint8` | 1 | |
| <a id="#DAA_CONFLICT_LVL_MEDIUM"></a> DAA_CONFLICT_LVL_MEDIUM | `uint8` | 2 | |
| <a id="#DAA_CONFLICT_LVL_HIGH"></a> DAA_CONFLICT_LVL_HIGH | `uint8` | 3 | |
| <a id="#DAA_CONFLICT_LVL_CRITICAL"></a> DAA_CONFLICT_LVL_CRITICAL | `uint8` | 4 | |
| <a id="#UNIQUE_ID_ENCODING_ICAO"></a> UNIQUE_ID_ENCODING_ICAO | `uint8` | 0 | `unique_id` contains an ICAO address |
| <a id="#UNIQUE_ID_ENCODING_ADSB_CALLSIGN"></a> UNIQUE_ID_ENCODING_ADSB_CALLSIGN | `uint8` | 1 | `unique_id` contains an ADS-B callsign packed into a `uint64` |
| <a id="#UNIQUE_ID_ENCODING_UAS_ID"></a> UNIQUE_ID_ENCODING_UAS_ID | `uint8` | 2 | `unique_id` contains the reduced tail bytes of a UAS ID |
| <a id="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH | `uint8` | 16 | |
## Source Message
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/DetectAndAvoid.msg)
:::details
Click here to see original file
```c
# Detect-and-avoid conflict assessment for one traffic aircraft.
#
# Detailed per-traffic output from navigator's `DetectAndAvoid` component.
# A sample is published when an evaluated report indicates a conflict or updates
# an aircraft already tracked as a conflict. New reports assessed at NONE are omitted.
#
# Unlike `detect_and_avoid_most_urgent`, this topic does not summarize the single
# active conflict driving DAA actions or prearm checks. It reports the conflict level
# and geometry for the specific traffic aircraft that was just evaluated.
#
# Published by: `navigator` (`DetectAndAvoid`)
# Used by: logging and tests
uint8 DAA_CONFLICT_LVL_NONE = 0
uint8 DAA_CONFLICT_LVL_LOW = 1
uint8 DAA_CONFLICT_LVL_MEDIUM = 2
uint8 DAA_CONFLICT_LVL_HIGH = 3
uint8 DAA_CONFLICT_LVL_CRITICAL = 4
uint8 UNIQUE_ID_ENCODING_ICAO = 0 # `unique_id` contains an ICAO address
uint8 UNIQUE_ID_ENCODING_ADSB_CALLSIGN = 1 # `unique_id` contains an ADS-B callsign packed into a `uint64`
uint8 UNIQUE_ID_ENCODING_UAS_ID = 2 # `unique_id` contains the reduced tail bytes of a UAS ID
uint8 ORB_QUEUE_LENGTH = 16
uint64 timestamp # [us] Time since system start
uint64 unique_id # [-] Encoded traffic identifier selected in priority order: ICAO address, ADS-B callsign, then reduced UAS ID tail bytes
uint8 unique_id_encoding # [-] Namespace used to decode `unique_id`
uint8 conflict_level # [-] Conflict level calculated for this traffic aircraft
float32 aircraft_dist # [m] Current 3D point-to-point range between ownship and the traffic aircraft
float32 aircraft_dist_hor # [m] [@frame NED] Horizontal separation metric. In Crosstrack mode this is the signed crosstrack distance when available, otherwise direct horizontal range
float32 aircraft_dist_vert # [m] [@frame NED] Vertical separation between ownship (the current vehicle) and the traffic aircraft
float32 expected_min_dist_time # [s] Conservative collision-time estimate from current 3D separation and the sum of ownship and traffic speed magnitudes
```
:::
docs/ko/msg_docs/DetectAndAvoidMostUrgent.md
+77
View File
@@ -0,0 +1,77 @@
---
pageClass: is-wide-page
---
# DetectAndAvoidMostUrgent (UORB message)
Detect-and-avoid summary for the most urgent active conflict.
Aggregated DAA status from navigator's `DetectAndAvoid` component.
It publishes the single active conflict that currently has the highest urgency
after the per-traffic conflict buffer has been updated.
Unlike `detect_and_avoid`, this topic is not published for every processed
traffic report and does not include the detailed horizontal and vertical geometry.
It is the topic used for overall DAA status, automatic-action decisions, and
prearm checks.
Published by: `navigator` (`DetectAndAvoid`)
Used by: `commander` DAA arming checks, logging, and tests
**TOPICS:** detect_and_avoid_most_urgent
## Fields
| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 |
| ----------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
| <a id="fld_unique_id"></a>unique_id | `uint64` | | | Encoded identifier of the current most urgent traffic aircraft, selected in priority order: ICAO address, ADS-B callsign, then reduced UAS ID tail bytes |
| <a id="fld_unique_id_encoding"></a>unique_id_encoding | `uint8` | | | Namespace used to decode `unique_id` |
| <a id="fld_has_action"></a>has_action | `bool` | | | True if the configured DAA response for this most urgent conflict is stronger than Warn only |
| <a id="fld_conflict_level"></a>conflict_level | `uint8` | | | Conflict level of the current most urgent active conflict |
| <a id="fld_aircraft_dist"></a>aircraft_dist | `float32` | m | | Approximate 3D range to the most urgent traffic aircraft (9999 when empty) |
## Constants
| 명칭 | 형식 | Value | 설명 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | ------------------------------------------------------------- |
| <a id="#UNIQUE_ID_ENCODING_ICAO"></a> UNIQUE_ID_ENCODING_ICAO | `uint8` | 0 | `unique_id` contains an ICAO address |
| <a id="#UNIQUE_ID_ENCODING_ADSB_CALLSIGN"></a> UNIQUE_ID_ENCODING_ADSB_CALLSIGN | `uint8` | 1 | `unique_id` contains an ADS-B callsign packed into a `uint64` |
| <a id="#UNIQUE_ID_ENCODING_UAS_ID"></a> UNIQUE_ID_ENCODING_UAS_ID | `uint8` | 2 | `unique_id` contains the reduced tail bytes of a UAS ID |
## Source Message
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/DetectAndAvoidMostUrgent.msg)
:::details
Click here to see original file
```c
# Detect-and-avoid summary for the most urgent active conflict.
#
# Aggregated DAA status from navigator's `DetectAndAvoid` component.
# It publishes the single active conflict that currently has the highest urgency
# after the per-traffic conflict buffer has been updated.
#
# Unlike `detect_and_avoid`, this topic is not published for every processed
# traffic report and does not include the detailed horizontal and vertical geometry.
# It is the topic used for overall DAA status, automatic-action decisions, and
# prearm checks.
#
# Published by: `navigator` (`DetectAndAvoid`)
# Used by: `commander` DAA arming checks, logging, and tests
uint8 UNIQUE_ID_ENCODING_ICAO = 0 # `unique_id` contains an ICAO address
uint8 UNIQUE_ID_ENCODING_ADSB_CALLSIGN = 1 # `unique_id` contains an ADS-B callsign packed into a `uint64`
uint8 UNIQUE_ID_ENCODING_UAS_ID = 2 # `unique_id` contains the reduced tail bytes of a UAS ID
uint64 timestamp # [us] Time since system start
uint64 unique_id # [-] Encoded identifier of the current most urgent traffic aircraft, selected in priority order: ICAO address, ADS-B callsign, then reduced UAS ID tail bytes
uint8 unique_id_encoding # [-] Namespace used to decode `unique_id`
bool has_action # [-] True if the configured DAA response for this most urgent conflict is stronger than Warn only
uint8 conflict_level # [-] Conflict level of the current most urgent active conflict
float32 aircraft_dist # [m] Approximate 3D range to the most urgent traffic aircraft (9999 when empty)
```
:::
docs/ko/msg_docs/FailureInjection.md
+2
View File
@@ -46,6 +46,7 @@ Used in field(s): [unit](#fld_unit)
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
### FAILURE_TYPE {#FAILURE_TYPE}
@@ -107,6 +108,7 @@ uint8 FAILURE_UNIT_SYSTEM_SERVO = 102
uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103
uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104
uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105
uint8 FAILURE_UNIT_SYSTEM_ESC = 106
uint16[4] instance_mask # Bit i targets instance (i+1); 0xFFFF = all instances
docs/ko/msg_docs/HeaterStatus.md
+20 -18
View File
@@ -8,24 +8,25 @@ pageClass: is-wide-page
## Fields
| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 |
| ------------------------------------------------------------------------------------------------------------------------------ | --------- | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
| <a id="fld_device_id"></a>device_id | `uint32` | | | |
| <a id="fld_heater_on"></a>heater_on | `bool` | | | |
| <a id="fld_temperature_target_met"></a>temperature_target_met | `bool` | | | |
| <a id="fld_temperature_sensor"></a>temperature_sensor | `float32` | | | |
| <a id="fld_temperature_target"></a>temperature_target | `float32` | | | |
| <a id="fld_controller_period_usec"></a>controller_period_usec | `uint32` | | | |
| <a id="fld_controller_time_on_usec"></a>controller_time_on_usec | `uint32` | | | |
| <a id="fld_proportional_value"></a>proportional_value | `float32` | | | |
| <a id="fld_integrator_value"></a>integrator_value | `float32` | | | |
| <a id="fld_feed_forward_value"></a>feed_forward_value | `float32` | | | |
| <a id="fld_supply_voltage"></a>supply_voltage | `float32` | | | Supply voltage (V) |
| <a id="fld_heater_current"></a>heater_current | `float32` | | | Heater current (A) |
| <a id="fld_nominal_multiplier"></a>nominal_multiplier | `float32` | | | |
| <a id="fld_mode"></a>mode | `uint8` | | | |
| <a id="fld_temperature_source"></a>temperature_source | `uint8` | | | |
| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
| <a id="fld_device_id"></a>device_id | `uint32` | | | |
| <a id="fld_heater_on"></a>heater_on | `bool` | | | |
| <a id="fld_temperature_target_met"></a>temperature_target_met | `bool` | | | |
| <a id="fld_temperature_activation_threshold_met"></a>temperature_activation_threshold_met | `bool` | | | |
| <a id="fld_temperature_sensor"></a>temperature_sensor | `float32` | | | |
| <a id="fld_temperature_target"></a>temperature_target | `float32` | | | |
| <a id="fld_controller_period_usec"></a>controller_period_usec | `uint32` | | | |
| <a id="fld_controller_time_on_usec"></a>controller_time_on_usec | `uint32` | | | |
| <a id="fld_proportional_value"></a>proportional_value | `float32` | | | |
| <a id="fld_integrator_value"></a>integrator_value | `float32` | | | |
| <a id="fld_feed_forward_value"></a>feed_forward_value | `float32` | | | |
| <a id="fld_supply_voltage"></a>supply_voltage | `float32` | | | Supply voltage (V) |
| <a id="fld_heater_current"></a>heater_current | `float32` | | | Heater current (A) |
| <a id="fld_nominal_multiplier"></a>nominal_multiplier | `float32` | | | |
| <a id="fld_mode"></a>mode | `uint8` | | | |
| <a id="fld_temperature_source"></a>temperature_source | `uint8` | | | |
## Constants
@@ -50,6 +51,7 @@ uint32 device_id
bool heater_on
bool temperature_target_met
bool temperature_activation_threshold_met
float32 temperature_sensor
float32 temperature_target
docs/ko/msg_docs/RtcmData.md
+77
View File
@@ -0,0 +1,77 @@
---
pageClass: is-wide-page
---
# RtcmData (UORB message)
RTCM3 data exchanged with GNSS receivers.
Published under two topic names that share this definition (see TOPICS below):
rtcm_corrections - external fixed-base corrections fed into the vehicle (MAVLink
GPS_RTCM_DATA, UAVCAN RTCMStream, GPS drivers in dump mode). Multiple
sources are allowed, one uORB instance each; consumers select an instance
via their stale-link logic.
rtcm_moving_baseline - moving-base GPS output (RTCM 4072 or equivalent) intended for a rover.
Single publisher per vehicle (on-board moving base, or a CANnode
forwarding MovingBaselineData); consumers only read instance 0.
**TOPICS:** rtcm_corrections rtcm_moving_baseline
## Fields
| 명칭 | 형식 | Unit [Frame] | Range/Enum | 설명 |
| -------------------------------------------------------- | ------------ | ---------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
| <a id="fld_device_id"></a>device_id | `uint32` | | | Unique device ID of the publisher that produced this RTCM |
| <a id="fld_len"></a>len | `uint16` | | | Length of data |
| <a id="fld_flags"></a>flags | `uint8` | | | LSB: 1=fragmented |
| <a id="fld_data"></a>data | `uint8[300]` | | | Correction payload (fixed-base RTCM3 and/or SPARTN frames, or moving-baseline RTCM3) |
## Constants
| 명칭 | 형식 | Value | 설명 |
| ----------------------------------------------------------------------------------------- | ------- | ----- | -- |
| <a id="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH | `uint8` | 16 | |
| <a id="#MAX_INSTANCES"></a> MAX_INSTANCES | `uint8` | 4 | |
## Source Message
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/RtcmData.msg)
:::details
Click here to see original file
```c
# RTCM3 data exchanged with GNSS receivers.
#
# Published under two topic names that share this definition (see TOPICS below):
#
# rtcm_corrections - external fixed-base corrections fed into the vehicle (MAVLink
# GPS_RTCM_DATA, UAVCAN RTCMStream, GPS drivers in dump mode). Multiple
# sources are allowed, one uORB instance each; consumers select an instance
# via their stale-link logic.
#
# rtcm_moving_baseline - moving-base GPS output (RTCM 4072 or equivalent) intended for a rover.
# Single publisher per vehicle (on-board moving base, or a CANnode
# forwarding MovingBaselineData); consumers only read instance 0.
uint64 timestamp # [us] Time since system start
uint32 device_id # [-] Unique device ID of the publisher that produced this RTCM
uint16 len # [-] Length of data
uint8 flags # [-] LSB: 1=fragmented
uint8[300] data # Correction payload (fixed-base RTCM3 and/or SPARTN frames, or moving-baseline RTCM3)
uint8 ORB_QUEUE_LENGTH = 16
# Sized for the fixed-base corrections case (up to four independent sources). The moving-baseline
# topic only uses instance 0 (single publisher per vehicle).
uint8 MAX_INSTANCES = 4
# TOPICS rtcm_corrections rtcm_moving_baseline
```
:::
docs/ko/msg_docs/VehicleCommand.md
+2
View File
@@ -1651,6 +1651,7 @@ Change heading/course. param1: heading type (0=course-over-ground, 1=heading). p
| <a id="#FAILURE_UNIT_SYSTEM_AVOIDANCE"></a> FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | |
| <a id="#FAILURE_UNIT_SYSTEM_RC_SIGNAL"></a> FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | |
| <a id="#FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL"></a> FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | |
| <a id="#FAILURE_UNIT_SYSTEM_ESC"></a> FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | |
| <a id="#FAILURE_TYPE_OK"></a> FAILURE_TYPE_OK | `uint8` | 0 | |
| <a id="#FAILURE_TYPE_OFF"></a> FAILURE_TYPE_OFF | `uint8` | 1 | |
| <a id="#FAILURE_TYPE_STUCK"></a> FAILURE_TYPE_STUCK | `uint8` | 2 | |
@@ -1854,6 +1855,7 @@ uint8 FAILURE_UNIT_SYSTEM_SERVO = 102
uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103
uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104
uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105
uint8 FAILURE_UNIT_SYSTEM_ESC = 106
uint8 FAILURE_TYPE_OK = 0
uint8 FAILURE_TYPE_OFF = 1
docs/ko/msg_docs/index.md
+3 -1
View File
@@ -104,6 +104,8 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
- [DebugKeyValue](DebugKeyValue.md)
- [DebugValue](DebugValue.md)
- [DebugVect](DebugVect.md)
- [DetectAndAvoid](DetectAndAvoid.md) — Detect-and-avoid conflict assessment for one traffic aircraft.
- [DetectAndAvoidMostUrgent](DetectAndAvoidMostUrgent.md) — Detect-and-avoid summary for the most urgent active conflict.
- [DeviceInformation](DeviceInformation.md) — Device information.
- [DifferentialPressure](DifferentialPressure.md) — Differential-pressure (airspeed) sensor.
- [DistanceSensor](DistanceSensor.md) — DISTANCE_SENSOR message data.
@@ -159,7 +161,6 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
- [GpioOut](GpioOut.md) — GPIO mask and state.
- [GpioRequest](GpioRequest.md) — Request GPIO mask to be read.
- [GpsDump](GpsDump.md) — This message is used to dump the raw gps communication to the log.
- [GpsInjectData](GpsInjectData.md)
- [Gripper](Gripper.md) — # Used to command an actuation in the gripper, which is mapped to a specific output in the control allocation module.
- [HealthReport](HealthReport.md)
- [HeaterStatus](HeaterStatus.md)
@@ -237,6 +238,7 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
- [RoverSteeringSetpoint](RoverSteeringSetpoint.md) — Rover Steering setpoint.
- [RoverThrottleSetpoint](RoverThrottleSetpoint.md) — Rover Throttle setpoint.
- [Rpm](Rpm.md)
- [RtcmData](RtcmData.md) — RTCM3 data exchanged with GNSS receivers.
- [RtlStatus](RtlStatus.md)
- [RtlTimeEstimate](RtlTimeEstimate.md)
- [SatelliteInfo](SatelliteInfo.md)
docs/ko/peripherals/adsb_flarm.md
+107 -104
View File
File diff suppressed because it is too large Load Diff
docs/ko/test_and_ci/integration_testing_mavsdk.md
+4 -4
View File
@@ -45,10 +45,10 @@ The tests need the MAVSDK C++ library installed system-wide (e.g. in `/usr/lib`
## 모든 PX4 테스트 실행
To run all SITL tests as defined in [sitl.json](https://github.com/PX4/PX4-Autopilot/blob/main/test/mavsdk_tests/configs/sitl.json), do:
To run all SITL tests using the SIH simulator as defined in [sih-sitl.json](https://github.com/PX4/PX4-Autopilot/blob/main/test/mavsdk_tests/configs/sih-sitl.json), do:
```sh
test/mavsdk_tests/mavsdk_test_runner.py test/mavsdk_tests/configs/sitl.json --speed-factor 10
test/mavsdk_tests/mavsdk_test_runner.py test/mavsdk_tests/configs/sih-sitl.json --speed-factor 10
```
This will list all the tests and then run them sequentially.
@@ -87,10 +87,10 @@ options:
## 단일 테스트 실행
Run a single test by specifying the `model` and test `case` as command line options.
예를 들어, 임무에서 테일시터 비행을 테스트하려면, 다음을 실행합니다.
For example, to test a multicopter mission using the SIH simulator:
```sh
test/mavsdk_tests/mavsdk_test_runner.py test/mavsdk_tests/configs/sitl.json --speed-factor 10 --model tailsitter --case 'Fly square Multicopter Missions including RTL'
test/mavsdk_tests/mavsdk_test_runner.py test/mavsdk_tests/configs/sih-sitl.json --speed-factor 10 --model quadx --case 'Fly square Multicopter Missions including RTL'
```
The easiest way to find out the current set of models and their associated test cases is to run all PX4 tests [as shown above](#run-all-px4-tests) (note, you can then cancel the build if you wish to test just one).