From a406f7b642b006e2ee7c85831cf01d5a675f46ef Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:06 +1100 Subject: [PATCH 01/62] New translations offboard.md (Japanese) --- ja/flight_modes/offboard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ja/flight_modes/offboard.md b/ja/flight_modes/offboard.md index a2bbc87d4490..837170748c30 100644 --- a/ja/flight_modes/offboard.md +++ b/ja/flight_modes/offboard.md @@ -76,7 +76,7 @@ For example, if the `acceleration` field is the first non-zero value, then PX4 r | thrust and torque (FRD) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | - | none | [VehicleThrustSetpoint](../msg_docs/VehicleThrustSetpoint.md) and [VehicleTorqueSetpoint](../msg_docs/VehicleTorqueSetpoint.md) | | direct motors and servos | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | none | [ActuatorMotors](../msg_docs/ActuatorMotors.md) and [ActuatorServos](../msg_docs/ActuatorServos.md) | -where ✓ means that the bit is set, ✗ means that the bit is not set and `-` means that the bit is value is irrelevant. +where ✓ means that the bit is set, ✘ means that the bit is not set and `-` means that the bit is value is irrelevant. :::info Before using offboard mode with ROS 2, please spend a few minutes understanding the different [frame conventions](../ros2/user_guide.md#ros-2-px4-frame-conventions) that PX4 and ROS 2 use. @@ -87,6 +87,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg) - The following input combinations are supported: + - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers. - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers. - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`) From efd990b5c85bba5ddf7f2a22098380845c0dc1c1 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:08 +1100 Subject: [PATCH 02/62] New translations offboard.md (Korean) --- ko/flight_modes/offboard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ko/flight_modes/offboard.md b/ko/flight_modes/offboard.md index 9a31cb643bae..eee2936229b5 100644 --- a/ko/flight_modes/offboard.md +++ b/ko/flight_modes/offboard.md @@ -76,7 +76,7 @@ For example, if the `acceleration` field is the first non-zero value, then PX4 r | thrust and torque (FRD) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | - | none | [VehicleThrustSetpoint](../msg_docs/VehicleThrustSetpoint.md) and [VehicleTorqueSetpoint](../msg_docs/VehicleTorqueSetpoint.md) | | direct motors and servos | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | none | [ActuatorMotors](../msg_docs/ActuatorMotors.md) and [ActuatorServos](../msg_docs/ActuatorServos.md) | -where ✓ means that the bit is set, ✗ means that the bit is not set and `-` means that the bit is value is irrelevant. +where ✓ means that the bit is set, ✘ means that the bit is not set and `-` means that the bit is value is irrelevant. :::info Before using offboard mode with ROS 2, please spend a few minutes understanding the different [frame conventions](../ros2/user_guide.md#ros-2-px4-frame-conventions) that PX4 and ROS 2 use. @@ -87,6 +87,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg) - 다음 입력 조합이 지원됩니다. + - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers. - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers. - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`) From 105626dd9f2ec990a0a6b4f92446b2286c90b5ed Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:10 +1100 Subject: [PATCH 03/62] New translations offboard.md (Turkish) --- tr/flight_modes/offboard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tr/flight_modes/offboard.md b/tr/flight_modes/offboard.md index a2bbc87d4490..837170748c30 100644 --- a/tr/flight_modes/offboard.md +++ b/tr/flight_modes/offboard.md @@ -76,7 +76,7 @@ For example, if the `acceleration` field is the first non-zero value, then PX4 r | thrust and torque (FRD) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | - | none | [VehicleThrustSetpoint](../msg_docs/VehicleThrustSetpoint.md) and [VehicleTorqueSetpoint](../msg_docs/VehicleTorqueSetpoint.md) | | direct motors and servos | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | none | [ActuatorMotors](../msg_docs/ActuatorMotors.md) and [ActuatorServos](../msg_docs/ActuatorServos.md) | -where ✓ means that the bit is set, ✗ means that the bit is not set and `-` means that the bit is value is irrelevant. +where ✓ means that the bit is set, ✘ means that the bit is not set and `-` means that the bit is value is irrelevant. :::info Before using offboard mode with ROS 2, please spend a few minutes understanding the different [frame conventions](../ros2/user_guide.md#ros-2-px4-frame-conventions) that PX4 and ROS 2 use. @@ -87,6 +87,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg) - The following input combinations are supported: + - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers. - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers. - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`) From a8380008f39de002ae547a95750a7a7971083cd1 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:13 +1100 Subject: [PATCH 04/62] New translations offboard.md (Ukrainian) --- uk/flight_modes/offboard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/uk/flight_modes/offboard.md b/uk/flight_modes/offboard.md index 2c7a824d8e86..ab7b85156d66 100644 --- a/uk/flight_modes/offboard.md +++ b/uk/flight_modes/offboard.md @@ -76,7 +76,7 @@ For example, if the `acceleration` field is the first non-zero value, then PX4 r | тяга та крутний момент (FRD) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | - | нічого | [VehicleThrustSetpoint](../msg_docs/VehicleThrustSetpoint.md) and [VehicleTorqueSetpoint](../msg_docs/VehicleTorqueSetpoint.md) | | двигуни та серво | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | нічого | [ActuatorMotors](../msg_docs/ActuatorMotors.md) and [ActuatorServos](../msg_docs/ActuatorServos.md) | -where ✓ means that the bit is set, ✗ means that the bit is not set and `-` means that the bit is value is irrelevant. +where ✓ means that the bit is set, ✘ means that the bit is not set and `-` means that the bit is value is irrelevant. :::info Before using offboard mode with ROS 2, please spend a few minutes understanding the different [frame conventions](../ros2/user_guide.md#ros-2-px4-frame-conventions) that PX4 and ROS 2 use. @@ -87,6 +87,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg) - Підтримуються наступні вхідні комбінації: + - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers. - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers. - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`) From 1f63e543981152b202aae040f3f9f00df707f6a7 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:14 +1100 Subject: [PATCH 05/62] New translations offboard.md (Chinese Simplified) --- zh/flight_modes/offboard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/zh/flight_modes/offboard.md b/zh/flight_modes/offboard.md index 06084edf7bf1..0d556ca45706 100644 --- a/zh/flight_modes/offboard.md +++ b/zh/flight_modes/offboard.md @@ -76,7 +76,7 @@ For example, if the `acceleration` field is the first non-zero value, then PX4 r | 推力和力矩(FRD) | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | - | 无 | [VehicleThrustSetpoint](../msg_docs/VehicleThrustSetpoint.md) and [VehicleTorqueSetpoint](../msg_docs/VehicleTorqueSetpoint.md) | | 直接给电机和舵机 | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | 无 | [ActuatorMotors](../msg_docs/ActuatorMotors.md) and [ActuatorServos](../msg_docs/ActuatorServos.md) | -where ✓ means that the bit is set, ✗ means that the bit is not set and `-` means that the bit is value is irrelevant. +where ✓ means that the bit is set, ✘ means that the bit is not set and `-` means that the bit is value is irrelevant. :::info Before using offboard mode with ROS 2, please spend a few minutes understanding the different [frame conventions](../ros2/user_guide.md#ros-2-px4-frame-conventions) that PX4 and ROS 2 use. @@ -87,6 +87,7 @@ Before using offboard mode with ROS 2, please spend a few minutes understanding - [px4_msgs::msg::TrajectorySetpoint](https://github.com/PX4/PX4-Autopilot/blob/main/msg/TrajectorySetpoint.msg) - 支持以下输入组合： + - Position setpoint (`position` different from `NaN`). Non-`NaN` values of velocity and acceleration are used as feedforward terms for the inner loop controllers. - Velocity setpoint (`velocity` different from `NaN` and `position` set to `NaN`). Non-`NaN` values acceleration are used as feedforward terms for the inner loop controllers. - Acceleration setpoint (`acceleration` different from `NaN` and `position` and `velocity` set to `NaN`) From 4e60f022fc3a651384f73a90c587974efd97913b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:16 +1100 Subject: [PATCH 06/62] New translations index.md (Japanese) --- ja/gps_compass/index.md | 54 ++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/ja/gps_compass/index.md b/ja/gps_compass/index.md index ecb06c23a091..5d24f01603b7 100644 --- a/ja/gps_compass/index.md +++ b/ja/gps_compass/index.md @@ -22,31 +22,31 @@ PX4 should work with any unit that communicates via the u-blox, MTK Ashtech or E This table contains non-RTK GNSS units (most of which also have a compass). These have been tested by the PX4 dev team, or which are popular within the PX4 community. -| Device | GPS | Compass | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Notes | -| :----------------------------------------------------------- | :-----------------------------: | :-----------------------------: | :-----------------------------: | :-------------------------------------------------------------------------------------------: | :---------------------------------------------------------- | -| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | &check; | &check; | + Baro, IMU | -| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | &check; | &check; | + Baro, IMU | -| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | &check; | &cross; | | -| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | &check; | | -| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | &check; | &check; | + Baro | -| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | &check; | &cross;&check;&check; | + Baro. | -| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | &check; | Superseded by HERE3 | -| [Emlid Reach M+](https://emlid.com/reach/) | &check; | &cross; | | &cross; | Supports PPK. RTK expected. | -| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | &check; | &cross; | + Baro | -| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | &cross; | | -| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | &cross; | | -| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | &check; | | -| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | &check; | | -| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | &check; | &check; | | -| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | &check; | | -| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | &check; | | &cross; | | -| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | &cross;&cross;&check; | | -| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | &cross; | | -| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | &check; | &cross;&cross;&check; | + Baro | -| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | &check; | + Baro | -| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | &cross; | + Baro | +| Device | GPS | Compass | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Notes | +| :----------------------------------------------------------- | :---------: | :-----------------------: | :-------------------------: | :-------------------: | :---------------------------------------------------------- | +| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | ✓ | ✓ | + Baro, IMU | +| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | ✓ | ✓ | + Baro, IMU | +| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | ✓ | ✘ | | +| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | ✓ | | +| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | ✓ | ✓ | + Baro | +| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | ✓ | ✘✓✓ | + Baro. | +| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | ✓ | Superseded by HERE3 | +| [Emlid Reach M+](https://emlid.com/reach/) | ✓ | ✘ | | ✘ | Supports PPK. RTK expected. | +| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | ✓ | ✘ | + Baro | +| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | ✘ | | +| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | ✘ | | +| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | ✓ | | +| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | ✓ | | +| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | ✓ | ✓ | | +| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | ✓ | | +| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | ✓ | | ✘ | | +| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | ✘✘✓ | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | ✘✘✓ | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | ✘✘✓ | | +| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | ✘ | | +| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | ✓ | ✘✘✓ | + Baro | +| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | ✓ | + Baro | +| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | ✘ | + Baro | @@ -63,9 +63,9 @@ These have been tested by the PX4 dev team, or which are popular within the PX4 Notes: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - The list may omit some discontinued hardware that is still supported (check earlier versions for info about discontinued modules). Removed items include: - _Here_ GPS From 136ff1ffeb46aa27d4f3d7bebacacdfab3eb9ce4 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:18 +1100 Subject: [PATCH 07/62] New translations index.md (Korean) --- ko/gps_compass/index.md | 54 ++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/ko/gps_compass/index.md b/ko/gps_compass/index.md index 4fa3a04a4c64..5b0d91566ba7 100644 --- a/ko/gps_compass/index.md +++ b/ko/gps_compass/index.md @@ -22,31 +22,31 @@ PX4는 u-blox, MTK Ashtech 또는 Emlid 프로토콜 또는 UAVCAN 통신 장치 This table contains non-RTK GNSS units (most of which also have a compass). These have been tested by the PX4 dev team, or which are popular within the PX4 community. -| 장치 | GPS | 나침반 | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | 참고 | -| :----------------------------------------------------------- | :-----------------------------: | :-----------------------------: | :-----------------------------: | :-------------------------------------------------------------------------------------------: | :---------------------------------------------------------- | -| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | &check; | &check; | + Baro, IMU | -| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | &check; | &check; | + Baro, IMU | -| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | &check; | &cross; | | -| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | &check; | | -| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | &check; | &check; | + Baro | -| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | &check; | &cross;&check;&check; | + Baro. | -| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | &check; | Superseded by HERE3 | -| [Emlid Reach M+](https://emlid.com/reach/) | &check; | &cross; | | &cross; | Supports PPK. RTK expected. | -| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | &check; | &cross; | + Baro | -| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | &cross; | | -| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | &cross; | | -| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | &check; | | -| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | &check; | | -| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | &check; | &check; | | -| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | &check; | | -| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | &check; | | &cross; | | -| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | &cross;&cross;&check; | | -| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | &cross; | | -| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | &check; | &cross;&cross;&check; | + Baro | -| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | &check; | + Baro | -| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | &cross; | + Baro | +| 장치 | GPS | 나침반 | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | 참고 | +| :----------------------------------------------------------- | :---------: | :-----------------------: | :-------------------------: | :-------------------: | :---------------------------------------------------------- | +| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | ✓ | ✓ | + Baro, IMU | +| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | ✓ | ✓ | + Baro, IMU | +| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | ✓ | ✘ | | +| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | ✓ | | +| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | ✓ | ✓ | + Baro | +| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | ✓ | ✘✓✓ | + Baro. | +| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | ✓ | Superseded by HERE3 | +| [Emlid Reach M+](https://emlid.com/reach/) | ✓ | ✘ | | ✘ | Supports PPK. RTK expected. | +| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | ✓ | ✘ | + Baro | +| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | ✘ | | +| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | ✘ | | +| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | ✓ | | +| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | ✓ | | +| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | ✓ | ✓ | | +| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | ✓ | | +| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | ✓ | | ✘ | | +| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | ✘✘✓ | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | ✘✘✓ | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | ✘✘✓ | | +| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | ✘ | | +| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | ✓ | ✘✘✓ | + Baro | +| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | ✓ | + Baro | +| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | ✘ | + Baro | @@ -63,9 +63,9 @@ These have been tested by the PX4 dev team, or which are popular within the PX4 참고: -- ✓ 또는 특정 부품 번호는 기능이 지원되는 것을 나타내며, ✗ 또는 비어 있으면 해당 기능이 지원되지 않는 것을 나타냅니다. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?"는 "알 수 없음"을 나타냅니다. -- 가능하고 관련성이있는 경우 부품 이름이 사용됩니다 (예 : GPS 열의 ✓ GPS 모듈이 있지만 부품을 알 수 없음을 나타냄). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - The list may omit some discontinued hardware that is still supported (check earlier versions for info about discontinued modules). Removed items include: - _Here_ GPS From b3ec405c0a18d87a86a33e32a7da5206d212029e Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:20 +1100 Subject: [PATCH 08/62] New translations index.md (Turkish) --- tr/gps_compass/index.md | 54 ++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/tr/gps_compass/index.md b/tr/gps_compass/index.md index ecb06c23a091..5d24f01603b7 100644 --- a/tr/gps_compass/index.md +++ b/tr/gps_compass/index.md @@ -22,31 +22,31 @@ PX4 should work with any unit that communicates via the u-blox, MTK Ashtech or E This table contains non-RTK GNSS units (most of which also have a compass). These have been tested by the PX4 dev team, or which are popular within the PX4 community. -| Device | GPS | Compass | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Notes | -| :----------------------------------------------------------- | :-----------------------------: | :-----------------------------: | :-----------------------------: | :-------------------------------------------------------------------------------------------: | :---------------------------------------------------------- | -| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | &check; | &check; | + Baro, IMU | -| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | &check; | &check; | + Baro, IMU | -| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | &check; | &cross; | | -| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | &check; | | -| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | &check; | &check; | + Baro | -| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | &check; | &cross;&check;&check; | + Baro. | -| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | &check; | Superseded by HERE3 | -| [Emlid Reach M+](https://emlid.com/reach/) | &check; | &cross; | | &cross; | Supports PPK. RTK expected. | -| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | &check; | &cross; | + Baro | -| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | &cross; | | -| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | &cross; | | -| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | &check; | | -| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | &check; | | -| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | &check; | &check; | | -| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | &check; | | -| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | &check; | | &cross; | | -| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | &cross;&cross;&check; | | -| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | &cross; | | -| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | &check; | &cross;&cross;&check; | + Baro | -| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | &check; | + Baro | -| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | &cross; | + Baro | +| Device | GPS | Compass | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Notes | +| :----------------------------------------------------------- | :---------: | :-----------------------: | :-------------------------: | :-------------------: | :---------------------------------------------------------- | +| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | ✓ | ✓ | + Baro, IMU | +| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | ✓ | ✓ | + Baro, IMU | +| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | ✓ | ✘ | | +| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | ✓ | | +| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | ✓ | ✓ | + Baro | +| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | ✓ | ✘✓✓ | + Baro. | +| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | ✓ | Superseded by HERE3 | +| [Emlid Reach M+](https://emlid.com/reach/) | ✓ | ✘ | | ✘ | Supports PPK. RTK expected. | +| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | ✓ | ✘ | + Baro | +| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | ✘ | | +| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | ✘ | | +| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | ✓ | | +| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | ✓ | | +| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | ✓ | ✓ | | +| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | ✓ | | +| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | ✓ | | ✘ | | +| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | ✘✘✓ | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | ✘✘✓ | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | ✘✘✓ | | +| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | ✘ | | +| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | ✓ | ✘✘✓ | + Baro | +| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | ✓ | + Baro | +| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | ✘ | + Baro | @@ -63,9 +63,9 @@ These have been tested by the PX4 dev team, or which are popular within the PX4 Notes: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - The list may omit some discontinued hardware that is still supported (check earlier versions for info about discontinued modules). Removed items include: - _Here_ GPS From 273fef27b7d485e14ab79c8226877cf1d2ec80ed Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:21 +1100 Subject: [PATCH 09/62] New translations index.md (Ukrainian) --- uk/gps_compass/index.md | 54 ++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/uk/gps_compass/index.md b/uk/gps_compass/index.md index c36f1a99bef1..bc53da66e492 100644 --- a/uk/gps_compass/index.md +++ b/uk/gps_compass/index.md @@ -22,31 +22,31 @@ PX4 повинен працювати з будь-яким пристроєм, Ця таблиця містить не-RTK GNSS-пристрої (більшість з яких також мають компас). Вони були протестовані командою розробників PX4 або користуються популярністю у спільноті PX4. -| Пристрій | GPS | Компас | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Примітки | -| :----------------------------------------------------------- | :-----------------------------: | :-----------------------------: | :-----------------------------: | :-------------------------------------------------------------------------------------------: | :------------------------------------------------------------- | -| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | &check; | &check; | + Baro, IMU | -| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | &check; | &check; | + Baro, IMU | -| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | &check; | &cross; | | -| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | &check; | | -| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | &check; | &check; | + Baro | -| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | &check; | &cross;&check;&check; | + Baro. | -| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | &check; | Superseded by HERE3 | -| [Emlid Reach M+](https://emlid.com/reach/) | &check; | &cross; | | &cross; | Підтримує PPK. Очікується RTK. | -| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | &check; | &cross; | + Baro | -| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | &cross; | | -| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | &cross; | | -| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | &check; | | -| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | &check; | | -| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | &check; | &check; | | -| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | &check; | | -| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | &check; | | &cross; | | -| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | опціональний | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | &cross;&cross;&check; | | -| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | &cross; | | -| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | &check; | &cross;&cross;&check; | + Baro | -| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | &check; | + Baro | -| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | &cross; | + Baro | +| Пристрій | GPS | Компас | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | Примітки | +| :----------------------------------------------------------- | :---------: | :-----------------------: | :-------------------------: | :-------------------: | :------------------------------------------------------------- | +| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | ✓ | ✓ | + Baro, IMU | +| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | ✓ | ✓ | + Baro, IMU | +| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | ✓ | ✘ | | +| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | ✓ | | +| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | ✓ | ✓ | + Baro | +| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | ✓ | ✘✓✓ | + Baro. | +| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | ✓ | Superseded by HERE3 | +| [Emlid Reach M+](https://emlid.com/reach/) | ✓ | ✘ | | ✘ | Підтримує PPK. Очікується RTK. | +| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | ✓ | ✘ | + Baro | +| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | ✘ | | +| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | ✘ | | +| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | ✓ | | +| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | ✓ | | +| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | ✓ | ✓ | | +| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | ✓ | | +| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | ✓ | | ✘ | | +| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | опціональний | | ✘✘✓ | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | ✘✘✓ | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | ✘✘✓ | | +| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | ✘ | | +| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | ✓ | ✘✘✓ | + Baro | +| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | ✓ | + Baro | +| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | ✘ | + Baro | @@ -63,9 +63,9 @@ PX4 повинен працювати з будь-яким пристроєм, Примітки: -- ✓ або конкретний номер артикулу вказує на те, що функція підтримується, тоді як ✗ або пусте поле вказує на те, що функція не підтримується. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" означає "невідомо". -- Там, де це можливо і доречно, використовується назва деталі (наприклад, ✓ у колонці GPS вказує на наявність GPS-модуля, але деталь невідома). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - The list may omit some discontinued hardware that is still supported (check earlier versions for info about discontinued modules). Removed items include: - _Here_ GPS From cff096ff71b960f1684d11449681d8b52951e479 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:23 +1100 Subject: [PATCH 10/62] New translations index.md (Chinese Simplified) --- zh/gps_compass/index.md | 54 ++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/zh/gps_compass/index.md b/zh/gps_compass/index.md index dc7fc542a1df..8f55c6a0ccf1 100644 --- a/zh/gps_compass/index.md +++ b/zh/gps_compass/index.md @@ -22,31 +22,31 @@ PX4 also supports [Real Time Kinematic (RTK)](../gps_compass/rtk_gps.md) and **P 下表包括了一些无RTK的GPS模块（其中大部分也有指南针）。 下面的设备PX4开发团队测试过了，或者是在PX4社区中受欢迎的。 -| 设备 | GPS | 罗盘 | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | 备注 | -| :----------------------------------------------------------- | :-----------------------------: | :-----------------------------: | :-----------------------------: | :-------------------------------------------------------------------------------------------: | :---------------------------------------------------------- | -| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | &check; | &check; | + Baro, IMU | -| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | &check; | &check; | + Baro, IMU | -| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | &check; | &cross; | | -| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | &check; | | -| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | &check; | &check; | + Baro | -| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | &check; | &cross;&check;&check; | + Baro. | -| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | &check; | Superseded by HERE3 | -| [Emlid Reach M+](https://emlid.com/reach/) | &check; | &cross; | | &cross; | Supports PPK. RTK expected. | -| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | &check; | &cross; | + Baro | -| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | &cross; | | -| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | &cross; | | -| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | &check; | | -| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | &check; | | -| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | &check; | &check; | | -| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | &check; | | -| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | &check; | | &cross; | | -| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | &cross;&cross;&check; | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | &cross;&cross;&check; | | -| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | &cross; | | -| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | &check; | &cross;&cross;&check; | + Baro | -| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | &check; | + Baro | -| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | &cross; | + Baro | +| 设备 | GPS | 罗盘 | [CAN](../dronecan/index.md) | Buzzer / SafeSw / LED | 备注 | +| :----------------------------------------------------------- | :-------------------------: | :-------------------------: | :-------------------------: | :-------------------------: | :---------------------------------------------------------- | +| [ARK GPS](../dronecan/ark_gps.md) | M9N | BMM150 | ✓ | ✓ | + Baro, IMU | +| [ARK TESEO GPS](../dronecan/ark_teseo_gps.md) | Teseo-LIV4F | BMM150 | ✓ | ✓ | + Baro, IMU | +| [Avionics Anonymous UAVCAN GNSS/Mag][avionics_anon_can_gnss] | SAM-M8Q | MMC5983MA | ✓ | ✘ | | +| [CUAV NEO 3 GPS](../gps_compass/gps_cuav_neo_3.md) | M9N | IST8310 | | ✓ | | +| [CUAV NEO 3 Pro GPS](../gps_compass/gps_cuav_neo_3pro.md) | M9N | RM3100 | ✓ | ✓ | + Baro | +| [CUAV NEO 3X GPS](../gps_compass/gps_cuav_neo_3x.md) | M9N | RM3100 | ✓ | ✘✓✓ | + Baro. | +| [CubePilot Here2 GNSS GPS (M8N)][CubePilot Here2] | M8N | ICM20948 | | ✓ | Superseded by HERE3 | +| [Emlid Reach M+](https://emlid.com/reach/) | ✓ | ✘ | | ✘ | Supports PPK. RTK expected. | +| [Holybro DroneCAN M8N GPS](../dronecan/holybro_m8n_gps.md) | M8N | BMM150 | ✓ | ✘ | + Baro | +| [Holybro Micro M8N GPS][Hb Micro M8N] | M8N | IST8310 | | ✘ | | +| [Holybro Nano Ublox M8 5883 GPS][hb_nano_m8_5883] | UBX-M8030 | QMC5883 | | ✘ | | +| [Holybro M8N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M8N | IST8310 | | ✓ | | +| [Holybro M9N GPS](../gps_compass/gps_holybro_m8n_m9n.md) | M9N | IST8310 | | ✓ | | +| [Holybro DroneCAN M9N GPS][hb_can_m9n] | M9N | BMM150 | ✓ | ✓ | | +| [Holybro M10 GPS][hb_m10] | M10 | IST8310 | | ✓ | | +| [Hobbyking u-blox Neo-M8N GPS & Compass][hk_ublox_neo_8mn] | M8N | ✓ | | ✘ | | +| [LOCOSYS Hawk A1 GNSS receiver][LOCOSYS Hawk A1] | MC-1612-V2b | optional | | ✘✘✓ | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | ✘✘✓ | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | ✘✘✓ | | +| [mRo GPS u-blox Neo-M8N Dual Compass][mro_neo8mn_dual_mag] | M8N | LIS3MDL, IST8308 | | ✘ | | +| [RaccoonLab L1 GNSS NEO-M8N][RccnLabGNSS250] | NEO-M8N | RM3100 | ✓ | ✘✘✓ | + Baro | +| [Sky-Drones SmartAP GPS](../gps_compass/gps_smartap.md) | M8N | HMC5983, IST8310, LIS3MDL | | ✓ | + Baro | +| [Zubax GNSS 2](https://zubax.com/products/gnss_2) | MAX-M8Q | LIS3MDL | | ✘ | + Baro | @@ -63,9 +63,9 @@ PX4 also supports [Real Time Kinematic (RTK)](../gps_compass/rtk_gps.md) and **P 备注： -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - The list may omit some discontinued hardware that is still supported (check earlier versions for info about discontinued modules). Removed items include: - _Here_ GPS From 9c3b761690261509d9b8346ddaa8108259f3dd76 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:24 +1100 Subject: [PATCH 11/62] New translations rtk_gps.md (Japanese) --- ja/gps_compass/rtk_gps.md | 70 +++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/ja/gps_compass/rtk_gps.md b/ja/gps_compass/rtk_gps.md index ae3893b6bc08..43a1909da4f7 100644 --- a/ja/gps_compass/rtk_gps.md +++ b/ja/gps_compass/rtk_gps.md @@ -20,39 +20,39 @@ The RTK compatible devices below that are expected to work with PX4 (it omits di The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used. It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic). -| Device | GPS | Compass | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | -| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-----------------------------: | :------------------------------: | :-----------------------------------------------: | :-----------------------------: | -| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | &check; | [Septentrio Dual Antenna][SeptDualAnt] | | -| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | &check; | | | | -| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | &check; | -| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | -| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | &check; | | | -| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | &cross; | | &cross; | | -| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | &check; | | | | -| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | -| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | -| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | -| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | -| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | &check; | | | -| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | &check; | | | -| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | &check; | | &check; | | +| Device | GPS | Compass | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | +| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :------------------------------: | :-----------------------------------------------: | :-: | +| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna][SeptDualAnt] | | +| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | | +| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ | +| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | +| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | | +| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | ✘ | | ✘ | | +| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | | +| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | +| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | +| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | +| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | +| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | | +| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | | +| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | | @@ -65,9 +65,9 @@ It also highlights devices that connect via the CAN bus, and those which support Notes: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably. - The list may omit some discontinued hardware that is still supported. For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release. From ebf3272755dacdb648ec771bdb6590ebd68a2b0b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:26 +1100 Subject: [PATCH 12/62] New translations rtk_gps.md (Korean) --- ko/gps_compass/rtk_gps.md | 70 +++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/ko/gps_compass/rtk_gps.md b/ko/gps_compass/rtk_gps.md index 34dcb0e61d52..b16f53e665d3 100644 --- a/ko/gps_compass/rtk_gps.md +++ b/ko/gps_compass/rtk_gps.md @@ -21,39 +21,39 @@ PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p), [u-blo The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used. It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic). -| 장치 | GPS | 나침반 | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | -| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-----------------------------: | :------------------------------: | :-----------------------------------------------: | :-----------------------------: | -| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | &check; | [Septentrio Dual Antenna][SeptDualAnt] | | -| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | &check; | | | | -| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | &check; | -| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | -| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | &check; | | | -| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | &cross; | | &cross; | | -| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | &check; | | | | -| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | -| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | -| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | -| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | -| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | &check; | | | -| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | &check; | | | -| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | &check; | | &check; | | +| 장치 | GPS | 나침반 | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | +| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :------------------------------: | :-----------------------------------------------: | :-: | +| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna][SeptDualAnt] | | +| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | | +| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ | +| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | +| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | | +| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | ✘ | | ✘ | | +| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | | +| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | +| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | +| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | +| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | +| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | | +| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | | +| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | | @@ -66,9 +66,9 @@ It also highlights devices that connect via the CAN bus, and those which support 참고: -- ✓ 또는 특정 부품 번호는 기능이 지원되는 것을 나타내며, ✗ 또는 비어 있으면 해당 기능이 지원되지 않는 것을 나타냅니다. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?"는 "알 수 없음"을 나타냅니다. -- 가능하고 관련성이있는 경우 부품 이름이 사용됩니다 (예 : GPS 열의 ✓ GPS 모듈이 있지만 부품을 알 수 없음을 나타냄). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably. - The list may omit some discontinued hardware that is still supported. For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release. From 4ffb915747d7fc8a88ae69c1f14a5766b87f8309 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:28 +1100 Subject: [PATCH 13/62] New translations rtk_gps.md (Turkish) --- tr/gps_compass/rtk_gps.md | 70 +++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/tr/gps_compass/rtk_gps.md b/tr/gps_compass/rtk_gps.md index ae3893b6bc08..43a1909da4f7 100644 --- a/tr/gps_compass/rtk_gps.md +++ b/tr/gps_compass/rtk_gps.md @@ -20,39 +20,39 @@ The RTK compatible devices below that are expected to work with PX4 (it omits di The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used. It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic). -| Device | GPS | Compass | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | -| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-----------------------------: | :------------------------------: | :-----------------------------------------------: | :-----------------------------: | -| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | &check; | [Septentrio Dual Antenna][SeptDualAnt] | | -| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | &check; | | | | -| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | &check; | -| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | -| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | &check; | | | -| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | &cross; | | &cross; | | -| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | &check; | | | | -| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | -| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | -| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | -| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | -| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | &check; | | | -| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | &check; | | | -| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | &check; | | &check; | | +| Device | GPS | Compass | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | +| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :------------------------------: | :-----------------------------------------------: | :-: | +| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna][SeptDualAnt] | | +| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | | +| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ | +| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | +| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | | +| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | ✘ | | ✘ | | +| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | | +| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | +| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | +| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | +| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | +| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | | +| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | | +| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | | @@ -65,9 +65,9 @@ It also highlights devices that connect via the CAN bus, and those which support Notes: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably. - The list may omit some discontinued hardware that is still supported. For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release. From a6519eca16e6e77a6b6bff40929566973a92e427 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:29 +1100 Subject: [PATCH 14/62] New translations rtk_gps.md (Ukrainian) --- uk/gps_compass/rtk_gps.md | 70 +++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/uk/gps_compass/rtk_gps.md b/uk/gps_compass/rtk_gps.md index d54447678198..00535d259a87 100644 --- a/uk/gps_compass/rtk_gps.md +++ b/uk/gps_compass/rtk_gps.md @@ -20,39 +20,39 @@ PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p), [u-blo Таблиця вказує пристрої, які також виводять курсову відмітку, а також можуть надавати курсову відмітку, коли використовуються дві одиниці на транспортному засобі. Він також відзначає пристрої, які підключаються через CAN шину, та ті, які підтримують PPK (пост-процесуальну кінематику). -| Пристрій | GPS | Компас | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | -| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-----------------------------: | :------------------------------: | :-----------------------------------------------: | :-----------------------------: | -| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | &check; | [Septentrio Dual Antenna][SeptDualAnt] | | -| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | &check; | | | | -| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | &check; | -| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | -| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | &check; | | | -| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | &cross; | | &cross; | | -| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | &check; | | | | -| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | -| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | -| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | -| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | -| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | &check; | | | -| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | &check; | | | -| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | &check; | | &check; | | +| Пристрій | GPS | Компас | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | +| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :------: | :------------------------------: | :-----------------------------------------------: | :-: | +| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna][SeptDualAnt] | | +| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | | +| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ | +| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | +| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | | +| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | ✘ | | ✘ | | +| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | | +| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | +| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | +| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | +| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | +| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | | +| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | | +| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | | @@ -65,9 +65,9 @@ PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p), [u-blo Примітки: -- ✓ або конкретний номер артикулу вказує на те, що функція підтримується, тоді як ✗ або пусте поле вказує на те, що функція не підтримується. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" означає "невідомо". -- Там, де це можливо і доречно, використовується назва деталі (наприклад, ✓ у колонці GPS вказує на наявність GPS-модуля, але деталь невідома). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - Деякі RTK-модулі можна використовувати лише в певній ролі (база або ровер), тоді як інші можна використовувати як взаємозамінні. - У списку може бути відсутнє деяке зняте з виробництва обладнання, яке все ще підтримується. For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release. From f70e3982e3a66b9b50f91116f3ae3df5b083def2 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:31 +1100 Subject: [PATCH 15/62] New translations rtk_gps.md (Chinese Simplified) --- zh/gps_compass/rtk_gps.md | 70 +++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 35 deletions(-) diff --git a/zh/gps_compass/rtk_gps.md b/zh/gps_compass/rtk_gps.md index 75c7f1e96bd2..d7da04e50a5a 100644 --- a/zh/gps_compass/rtk_gps.md +++ b/zh/gps_compass/rtk_gps.md @@ -20,39 +20,39 @@ The RTK compatible devices below that are expected to work with PX4 (it omits di The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used. It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic). -| 设备 | GPS | 罗盘 | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | -| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-----------------------------: | :------------------------------: | :-----------------------------------------------: | :-----------------------------: | -| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | &check; | [Septentrio Dual Antenna][SeptDualAnt] | | -| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | &check; | | | | -| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | &check; | -| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | -| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | &check; | | | -| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | &cross; | | &cross; | | -| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | &check; | | | | -| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | -| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | -| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | &check; | [Dual F9P][DualF9P] | | -| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | -| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | -| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | -| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | -| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | -| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | -| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | &check; | | | -| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | &check; | | | -| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | &check; | | [Septentrio Dual Antenna][SeptDualAnt] | &check; | -| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | &check; | | [Dual F9P][DualF9P] | | -| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | &check; | | &check; | | +| 设备 | GPS | 罗盘 | [DroneCAN](../dronecan/index.md) | [GPS Yaw](#configuring-gps-as-yaw-heading-source) | PPK | +| :------------------------------------------------------------------------------------------------------------------- | :------------------: | :-------------------------: | :------------------------------: | :-----------------------------------------------: | :-------------------------: | +| [ARK RTK GPS](../dronecan/ark_rtk_gps.md) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [ARK MOSAIC-X5 RTK GPS](../dronecan/ark_mosaic__rtk_gps.md) | Mosaic-X5 | IIS2MDC | ✓ | [Septentrio Dual Antenna][SeptDualAnt] | | +| [CUAV C-RTK GPS](../gps_compass/rtk_gps_cuav_c-rtk.md) | M8P/M8N | ✓ | | | | +| [CUAV C-RTK2](../gps_compass/rtk_gps_cuav_c-rtk2.md) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK 9Ps GPS](../gps_compass/rtk_gps_cuav_c-rtk-9ps.md) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [CUAV C-RTK2 PPK/RTK GNSS](../gps_compass/rtk_gps_cuav_c-rtk.md) | F9P | RM3100 | | | ✓ | +| [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) | M8P | HMC5983 | | | | +| [CubePilot Here3 CAN GNSS GPS (M8N)](https://www.cubepilot.org/#/here/here3) | M8P | ICM20948 | ✓ | | | +| [Drotek SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [DATAGNSS GEM1305 RTK Receiver][DATAGNSS GEM1305 RTK] | TAU951M | ✘ | | ✘ | | +| [Femtones MINI2 Receiver](../gps_compass/rtk_gps_fem_mini2.md) | FB672, FB6A0 | ✓ | | | | +| [Freefly RTK GPS](../gps_compass/rtk_gps_freefly.md) | F9P | IST8310 | | | | +| [Holybro H-RTK ZED-F9P RTK Rover (DroneCAN variant)](../dronecan/holybro_h_rtk_zed_f9p_gps.md) | F9P | RM3100 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK ZED-F9P RTK Rover](https://holybro.com/collections/h-rtk-gps/products/h-rtk-zed-f9p-rover) | F9P | RM3100 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Ultralight](https://holybro.com/products/h-rtk-f9p-ultralight) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Helical or Base](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | [Dual F9P][DualF9P] | | +| [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | F9P | BMM150 | ✓ | [Dual F9P][DualF9P] | | +| [Holybro H-RTK F9P Rover Lite](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) | F9P | IST8310 | | | | +| [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | F9P | BMM150 | | [Dual F9P][DualF9P] | | +| [Holybro H-RTK M8P GNSS](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) | M8P | IST8310 | | | | +| [Holybro H-RTK Unicore UM982 GPS](../gps_compass/rtk_gps_holybro_unicore_um982.md) | UM982 | IST8310 | | [Unicore Dual Antenna][UnicoreDualAnt] | | +| [LOCOSYS Hawk R1](../gps_compass/rtk_gps_locosys_r1.md) | MC-1612-V2b | | | | | +| [LOCOSYS Hawk R2](../gps_compass/rtk_gps_locosys_r2.md) | MC-1612-V2b | IST8310 | | | | +| [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [RaccoonLab L1/L2 ZED-F9P][RaccoonLab L1/L2 ZED-F9P] | F9P | RM3100 | ✓ | | | +| [RaccoonLab L1/L2 ZED-F9P with external antenna][RaccnLabL1L2ZED-F9P ext_ant] | F9P | RM3100 | ✓ | | | +| [Septentrio AsteRx-m3 Pro](../gps_compass/septentrio_asterx-rib.md) | AsteRx | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [Septentrio mosaic-go](../gps_compass/septentrio_mosaic-go.md) | mosaic X5 / mosaic H | ✓ | | [Septentrio Dual Antenna][SeptDualAnt] | ✓ | +| [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | F9P | ✓ | | [Dual F9P][DualF9P] | | +| [Trimble MB-Two](../gps_compass/rtk_gps_trimble_mb_two.md) | F9P | ✓ | | ✓ | | @@ -65,9 +65,9 @@ It also highlights devices that connect via the CAN bus, and those which support 备注： -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". -- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). +- Where possible and relevant the part name is used (i.e. ✓ in the GPS column indicates that a GPS module is present but the part is not known). - Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably. - The list may omit some discontinued hardware that is still supported. For example [CubePilot Here+ RTK GPS](../gps_compass/rtk_gps_hex_hereplus.md) is discontinued and may be removed from the list in a future release. From 8436d0f40d94eaf51a6f133cec07654cb9740d0b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:33 +1100 Subject: [PATCH 16/62] New translations septentrio_mosaic-go.md (Japanese) --- ja/gps_compass/septentrio_mosaic-go.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/ja/gps_compass/septentrio_mosaic-go.md b/ja/gps_compass/septentrio_mosaic-go.md index d2000350b07d..c040b60039d6 100644 --- a/ja/gps_compass/septentrio_mosaic-go.md +++ b/ja/gps_compass/septentrio_mosaic-go.md @@ -125,14 +125,14 @@ The web interface also uses easy-to-read quality indicators ideal to monitor the ## LED Status -| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | -| ------------- | :------------------------------: | :------------------------------: | :------------------------------: | :------------------------------: | -| Red | &check;️ | | | | -| Green | &check;️ | &check;️ | | | -| Blue | &check;️ | &check;️ | &check;️ | | -| Purple | &check;️ | | &check;️ | | -| Purple + Blue | &check;️ | &check;️ | &check;️ | &check;️ | -| Red + Green | &check;️ | &check;️ | | &check;️ | +| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | +| ------------- | :-----: | :-------------: | :----------: | :-------------: | +| Red | ✓ | | | | +| Green | ✓ | ✓ | | | +| Blue | ✓ | ✓ | ✓ | | +| Purple | ✓ | | ✓ | | +| Purple + Blue | ✓ | ✓ | ✓ | ✓ | +| Red + Green | ✓ | ✓ | | ✓ | :::tip For more detailed information about the mosaic-go and its module, please refer to the [hardware manual](https://web.septentrio.com/l/858493/2022-04-19/xgrrd) or the [Septentrio Support](https://support.septentrio.com/l/858493/2022-04-19/xgrrl) page. From ee9eda8d786761fed5ac7c976bc9a91cac39dd6e Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:34 +1100 Subject: [PATCH 17/62] New translations septentrio_mosaic-go.md (Korean) --- ko/gps_compass/septentrio_mosaic-go.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/ko/gps_compass/septentrio_mosaic-go.md b/ko/gps_compass/septentrio_mosaic-go.md index bd6ea9efdbf0..87dcc69e749b 100644 --- a/ko/gps_compass/septentrio_mosaic-go.md +++ b/ko/gps_compass/septentrio_mosaic-go.md @@ -125,14 +125,14 @@ The web interface also uses easy-to-read quality indicators ideal to monitor the ## LED Status -| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | -| ------------- | :------------------------------: | :------------------------------: | :------------------------------: | :------------------------------: | -| 빨강 | &check;️ | | | | -| 녹색 | &check;️ | &check;️ | | | -| 청색 | &check;️ | &check;️ | &check;️ | | -| Purple | &check;️ | | &check;️ | | -| Purple + Blue | &check;️ | &check;️ | &check;️ | &check;️ | -| Red + Green | &check;️ | &check;️ | | &check;️ | +| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | +| ------------- | :-----: | :-------------: | :----------: | :-------------: | +| 빨강 | ✓ | | | | +| 녹색 | ✓ | ✓ | | | +| 청색 | ✓ | ✓ | ✓ | | +| Purple | ✓ | | ✓ | | +| Purple + Blue | ✓ | ✓ | ✓ | ✓ | +| Red + Green | ✓ | ✓ | | ✓ | :::tip For more detailed information about the mosaic-go and its module, please refer to the [hardware manual](https://web.septentrio.com/l/858493/2022-04-19/xgrrd) or the [Septentrio Support](https://support.septentrio.com/l/858493/2022-04-19/xgrrl) page. From 2da227983e36b73c2c468bf7437a5a6a302a01de Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:36 +1100 Subject: [PATCH 18/62] New translations septentrio_mosaic-go.md (Turkish) --- tr/gps_compass/septentrio_mosaic-go.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/tr/gps_compass/septentrio_mosaic-go.md b/tr/gps_compass/septentrio_mosaic-go.md index d2000350b07d..c040b60039d6 100644 --- a/tr/gps_compass/septentrio_mosaic-go.md +++ b/tr/gps_compass/septentrio_mosaic-go.md @@ -125,14 +125,14 @@ The web interface also uses easy-to-read quality indicators ideal to monitor the ## LED Status -| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | -| ------------- | :------------------------------: | :------------------------------: | :------------------------------: | :------------------------------: | -| Red | &check;️ | | | | -| Green | &check;️ | &check;️ | | | -| Blue | &check;️ | &check;️ | &check;️ | | -| Purple | &check;️ | | &check;️ | | -| Purple + Blue | &check;️ | &check;️ | &check;️ | &check;️ | -| Red + Green | &check;️ | &check;️ | | &check;️ | +| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | +| ------------- | :-----: | :-------------: | :----------: | :-------------: | +| Red | ✓ | | | | +| Green | ✓ | ✓ | | | +| Blue | ✓ | ✓ | ✓ | | +| Purple | ✓ | | ✓ | | +| Purple + Blue | ✓ | ✓ | ✓ | ✓ | +| Red + Green | ✓ | ✓ | | ✓ | :::tip For more detailed information about the mosaic-go and its module, please refer to the [hardware manual](https://web.septentrio.com/l/858493/2022-04-19/xgrrd) or the [Septentrio Support](https://support.septentrio.com/l/858493/2022-04-19/xgrrl) page. From a3bb4a102f3549d499abede7be5e3345dbcfed15 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:37 +1100 Subject: [PATCH 19/62] New translations septentrio_mosaic-go.md (Ukrainian) --- uk/gps_compass/septentrio_mosaic-go.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/uk/gps_compass/septentrio_mosaic-go.md b/uk/gps_compass/septentrio_mosaic-go.md index c62946496cc5..431cefff9787 100644 --- a/uk/gps_compass/septentrio_mosaic-go.md +++ b/uk/gps_compass/septentrio_mosaic-go.md @@ -125,14 +125,14 @@ The included GNSS receiver control and analysis software [RxTools](https://web.s ## Статус LED -| Колір світлодіоду | Живлення | SD карта змонтована | PVT Solution | Logging enabled | -| ----------------- | :------------------------------: | :------------------------------: | :------------------------------: | :------------------------------: | -| Red | &check;️ | | | | -| Зелений | &check;️ | &check;️ | | | -| Синій | &check;️ | &check;️ | &check;️ | | -| Purple | &check;️ | | &check;️ | | -| Purple + Blue | &check;️ | &check;️ | &check;️ | &check;️ | -| Red + Green | &check;️ | &check;️ | | &check;️ | +| Колір світлодіоду | Живлення | SD карта змонтована | PVT Solution | Logging enabled | +| ----------------- | :------: | :-----------------: | :----------: | :-------------: | +| Red | ✓ | | | | +| Зелений | ✓ | ✓ | | | +| Синій | ✓ | ✓ | ✓ | | +| Purple | ✓ | | ✓ | | +| Purple + Blue | ✓ | ✓ | ✓ | ✓ | +| Red + Green | ✓ | ✓ | | ✓ | :::tip For more detailed information about the mosaic-go and its module, please refer to the [hardware manual](https://web.septentrio.com/l/858493/2022-04-19/xgrrd) or the [Septentrio Support](https://support.septentrio.com/l/858493/2022-04-19/xgrrl) page. From 2c6c8ff6a77dbc5d2a2c115bb6b6433e5c150d5b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:38 +1100 Subject: [PATCH 20/62] New translations septentrio_mosaic-go.md (Chinese Simplified) --- zh/gps_compass/septentrio_mosaic-go.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/zh/gps_compass/septentrio_mosaic-go.md b/zh/gps_compass/septentrio_mosaic-go.md index aeeaa2f828d5..123b9a33c31c 100644 --- a/zh/gps_compass/septentrio_mosaic-go.md +++ b/zh/gps_compass/septentrio_mosaic-go.md @@ -125,14 +125,14 @@ The web interface also uses easy-to-read quality indicators ideal to monitor the ## LED Status -| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | -| ------------- | :------------------------------: | :------------------------------: | :------------------------------: | :------------------------------: | -| Red | &check;️ | | | | -| 绿色 | &check;️ | &check;️ | | | -| 蓝色 | &check;️ | &check;️ | &check;️ | | -| Purple | &check;️ | | &check;️ | | -| Purple + Blue | &check;️ | &check;️ | &check;️ | &check;️ | -| Red + Green | &check;️ | &check;️ | | &check;️ | +| LED Color | Powered | SD card mounted | PVT Solution | Logging enabled | +| ------------- | :-------------------------: | :-------------------------: | :-------------------------: | :-------------------------: | +| Red | ✓ | | | | +| 绿色 | ✓ | ✓ | | | +| 蓝色 | ✓ | ✓ | ✓ | | +| Purple | ✓ | | ✓ | | +| Purple + Blue | ✓ | ✓ | ✓ | ✓ | +| Red + Green | ✓ | ✓ | | ✓ | :::tip For more detailed information about the mosaic-go and its module, please refer to the [hardware manual](https://web.septentrio.com/l/858493/2022-04-19/xgrrd) or the [Septentrio Support](https://support.septentrio.com/l/858493/2022-04-19/xgrrl) page. From 69c8298bada362470f159c59c06c09b9b4d87e52 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:40 +1100 Subject: [PATCH 21/62] New translations magnetometer.md (Japanese) --- ja/gps_compass/magnetometer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ja/gps_compass/magnetometer.md b/ja/gps_compass/magnetometer.md index 0fac602ef797..627ac48db673 100644 --- a/ja/gps_compass/magnetometer.md +++ b/ja/gps_compass/magnetometer.md @@ -38,15 +38,15 @@ If GNSS is required, then a combined GNSS/Compass module will be preferred over This list contains stand-alone magnetometer modules (without GNSS). -| Device | Compass | DroneCan | -| :--------------------------------------------------------------------------------------------------------------- | :-----: | :-----------------------------: | -| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | -| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | -| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | +| Device | Compass | DroneCan | +| :--------------------------------------------------------------------------------------------------------------- | :-----: | :------: | +| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | +| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | +| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | Note: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". - A compass that is not "DroneCAN" can be assumed to be SPI or I2C. From 5a968a3ff4a2e3d7d0cf9fe51326f53e7dff8fee Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:41 +1100 Subject: [PATCH 22/62] New translations magnetometer.md (Korean) --- ko/gps_compass/magnetometer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ko/gps_compass/magnetometer.md b/ko/gps_compass/magnetometer.md index 370bf08449fc..7e8e984cabc3 100644 --- a/ko/gps_compass/magnetometer.md +++ b/ko/gps_compass/magnetometer.md @@ -38,15 +38,15 @@ If GNSS is required, then a combined GNSS/Compass module will be preferred over This list contains stand-alone magnetometer modules (without GNSS). -| 장치 | 나침반 | DroneCan | -| :--------------------------------------------------------------------------------------------------------------- | :----: | :-----------------------------: | -| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | -| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | -| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | +| 장치 | 나침반 | DroneCan | +| :--------------------------------------------------------------------------------------------------------------- | :----: | :------: | +| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | +| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | +| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | 참고: -- ✓ 또는 특정 부품 번호는 기능이 지원되는 것을 나타내며, ✗ 또는 비어 있으면 해당 기능이 지원되지 않는 것을 나타냅니다. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?"는 "알 수 없음"을 나타냅니다. - A compass that is not "DroneCAN" can be assumed to be SPI or I2C. From 1a29fa461c5aac05e57c6094cb2a8e0ea73ba1df Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:42 +1100 Subject: [PATCH 23/62] New translations magnetometer.md (Turkish) --- tr/gps_compass/magnetometer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tr/gps_compass/magnetometer.md b/tr/gps_compass/magnetometer.md index 0fac602ef797..627ac48db673 100644 --- a/tr/gps_compass/magnetometer.md +++ b/tr/gps_compass/magnetometer.md @@ -38,15 +38,15 @@ If GNSS is required, then a combined GNSS/Compass module will be preferred over This list contains stand-alone magnetometer modules (without GNSS). -| Device | Compass | DroneCan | -| :--------------------------------------------------------------------------------------------------------------- | :-----: | :-----------------------------: | -| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | -| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | -| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | +| Device | Compass | DroneCan | +| :--------------------------------------------------------------------------------------------------------------- | :-----: | :------: | +| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | +| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | +| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | Note: -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". - A compass that is not "DroneCAN" can be assumed to be SPI or I2C. From 4a18e52695ea909f61eaa19714a166e560664147 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:44 +1100 Subject: [PATCH 24/62] New translations magnetometer.md (Ukrainian) --- uk/gps_compass/magnetometer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/uk/gps_compass/magnetometer.md b/uk/gps_compass/magnetometer.md index 5957ae92ad53..136b1628c55a 100644 --- a/uk/gps_compass/magnetometer.md +++ b/uk/gps_compass/magnetometer.md @@ -38,15 +38,15 @@ PX4 можна використовувати з багатьма деталям Цей список містить самостійні модулі магнітометрів (без ГНСС). -| Пристрій | Компас | DroneCan | -| :-------------------------------------------------------------------------------------------------------------- | :----: | :-----------------------------: | -| [Магнітометр UAVCAN Avionics Anonymous](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | -| [Компас/Магнітометр Holybro DroneCAN RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | -| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | +| Пристрій | Компас | DroneCan | +| :-------------------------------------------------------------------------------------------------------------- | :----: | :------: | +| [Магнітометр UAVCAN Avionics Anonymous](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | +| [Компас/Магнітометр Holybro DroneCAN RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | +| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | Примітка: -- ✓ або конкретний номер артикулу вказує на те, що функція підтримується, тоді як ✗ або пусте поле вказує на те, що функція не підтримується. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" означає "невідомо". - Компас, який не є "DroneCAN", можна вважати SPI або I2C. From cbec6a4f5c9f85a0d84ab5699944f4e1bd2a61a4 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:45 +1100 Subject: [PATCH 25/62] New translations magnetometer.md (Chinese Simplified) --- zh/gps_compass/magnetometer.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/zh/gps_compass/magnetometer.md b/zh/gps_compass/magnetometer.md index 510d3cef3dc9..2655481edf74 100644 --- a/zh/gps_compass/magnetometer.md +++ b/zh/gps_compass/magnetometer.md @@ -38,15 +38,15 @@ If GNSS is required, then a combined GNSS/Compass module will be preferred over This list contains stand-alone magnetometer modules (without GNSS). -| 设备 | 罗盘 | DroneCan | -| :--------------------------------------------------------------------------------------------------------------- | :----: | :-----------------------------: | -| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | -| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | -| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | &check; | +| 设备 | 罗盘 | DroneCan | +| :--------------------------------------------------------------------------------------------------------------- | :----: | :-------------------------: | +| [Avionics Anonymous UAVCAN Magnetometer](https://www.tindie.com/products/avionicsanonymous/uavcan-magnetometer/) | ? | | +| [Holybro DroneCAN RM3100 Compass/Magnetometer](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | +| [RaccoonLab DroneCAN/Cyphal Magnetometer RM3100](https://holybro.com/products/dronecan-rm3100-compass) | RM3100 | ✓ | 注意： -- ✓ or a specific part number indicate that a features is supported, while ✗ or empty show that the feature is not supported. +- ✓ or a specific part number indicate that a features is supported, while ✘ or empty show that the feature is not supported. "?" indicates "unknown". - A compass that is not "DroneCAN" can be assumed to be SPI or I2C. From 91f05f6528a3ad561c97ac0c68170cca44996a06 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:46 +1100 Subject: [PATCH 26/62] New translations dev_env.md (Japanese) --- ja/dev_setup/dev_env.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/ja/dev_setup/dev_env.md b/ja/dev_setup/dev_env.md index cee702eb31f6..887702688488 100644 --- a/ja/dev_setup/dev_env.md +++ b/ja/dev_setup/dev_env.md @@ -10,14 +10,14 @@ The _supported platforms_ for PX4 development are: The table below shows what PX4 targets you can build on each OS. -| Target | Linux (Ubuntu) | Mac | Windows | -| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-----------------------------: | :-----------------------------: | -| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | &check; | &check; | &check; | -| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | &check; | | | -| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | &check; | &check; | &check; | -| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | &check; | &check; | &check; | -| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | &check; | | &check; | -| **Simulation:** ROS 2 with Gazebo | &check; | | &check; | +| Target | Linux (Ubuntu) | Mac | Windows | +| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-: | :-----: | +| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ | +| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | | +| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | ✓ | | ✓ | +| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ | Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md) From 8a7b447dbbbd01b0b27a17ea6189a5a87a676ed2 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:48 +1100 Subject: [PATCH 27/62] New translations dev_env.md (Korean) --- ko/dev_setup/dev_env.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/ko/dev_setup/dev_env.md b/ko/dev_setup/dev_env.md index ccd8e3acf1af..427f28d30208 100644 --- a/ko/dev_setup/dev_env.md +++ b/ko/dev_setup/dev_env.md @@ -10,14 +10,14 @@ The _supported platforms_ for PX4 development are: 아래 표는 각 OS에서 구축 가능한 PX 대상을 보여줍니다. -| 대상 | Linux (Ubuntu) | Mac | 윈도우 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-----------------------------: | :-----------------------------: | -| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | &check; | &check; | &check; | -| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | &check; | | | -| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | &check; | &check; | &check; | -| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | &check; | &check; | &check; | -| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | &check; | | &check; | -| **Simulation:** ROS 2 with Gazebo | &check; | | &check; | +| 대상 | Linux (Ubuntu) | Mac | 윈도우 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-: | :-: | +| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ | +| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | | +| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | ✓ | | ✓ | +| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ | Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md) From 437f425100970c9e0fcf19da8f6aeec3b5ef74f8 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:49 +1100 Subject: [PATCH 28/62] New translations dev_env.md (Turkish) --- tr/dev_setup/dev_env.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/tr/dev_setup/dev_env.md b/tr/dev_setup/dev_env.md index cee702eb31f6..887702688488 100644 --- a/tr/dev_setup/dev_env.md +++ b/tr/dev_setup/dev_env.md @@ -10,14 +10,14 @@ The _supported platforms_ for PX4 development are: The table below shows what PX4 targets you can build on each OS. -| Target | Linux (Ubuntu) | Mac | Windows | -| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-----------------------------: | :-----------------------------: | -| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | &check; | &check; | &check; | -| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | &check; | | | -| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | &check; | &check; | &check; | -| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | &check; | &check; | &check; | -| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | &check; | | &check; | -| **Simulation:** ROS 2 with Gazebo | &check; | | &check; | +| Target | Linux (Ubuntu) | Mac | Windows | +| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-: | :-----: | +| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ | +| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | | +| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | ✓ | | ✓ | +| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ | Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md) From 6e8fff511f201eda9e10ba66ff9b411dc1721c7f Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:50 +1100 Subject: [PATCH 29/62] New translations dev_env.md (Ukrainian) --- uk/dev_setup/dev_env.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/uk/dev_setup/dev_env.md b/uk/dev_setup/dev_env.md index 08f557aa1baa..46bcc54138ff 100644 --- a/uk/dev_setup/dev_env.md +++ b/uk/dev_setup/dev_env.md @@ -10,14 +10,14 @@ The _supported platforms_ for PX4 development are: Таблиця нижче показує, які цільові платформи PX4 можна побудувати на кожній ОС. -| Цільова платформа | Linux (Ubuntu) | Mac | Windows | -| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-----------------------------: | :-----------------------------: | -| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | &check; | &check; | &check; | -| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | &check; | | | -| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | &check; | &check; | &check; | -| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | &check; | &check; | &check; | -| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | &check; | | &check; | -| **Simulation:** ROS 2 with Gazebo | &check; | | &check; | +| Цільова платформа | Linux (Ubuntu) | Mac | Windows | +| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-: | :-----: | +| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ | +| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | | +| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | ✓ | | ✓ | +| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ | Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md) From 5552374077a8485bb684b743179d5446bafc675a Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 13:20:51 +1100 Subject: [PATCH 30/62] New translations dev_env.md (Chinese Simplified) --- zh/dev_setup/dev_env.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/zh/dev_setup/dev_env.md b/zh/dev_setup/dev_env.md index 95aa22a9f787..fadf7c8dcaf7 100644 --- a/zh/dev_setup/dev_env.md +++ b/zh/dev_setup/dev_env.md @@ -10,14 +10,14 @@ The _supported platforms_ for PX4 development are: 下表显示了您可以在每个操作系统上构建何种 PX平台的固件编译。 -| 平台 | Linux (Ubuntu) | Mac | Windows | -| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-----------------------------: | :-----------------------------: | -| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | &check; | &check; | &check; | -| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | &check; | | | -| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | &check; | &check; | &check; | -| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | &check; | &check; | &check; | -| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | &check; | | &check; | -| **Simulation:** ROS 2 with Gazebo | &check; | | &check; | +| 平台 | Linux (Ubuntu) | Mac | Windows | +| ------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------------: | :-------------------------: | :-------------------------: | +| **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) | ✓ | ✓ | ✓ | +| **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md) | ✓ | | | +| **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md) | ✓ | ✓ | ✓ | +| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md) | ✓ | | ✓ | +| **Simulation:** ROS 2 with Gazebo | ✓ | | ✓ | Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md) From ad58583acfd4e57126dea2c40d10c6aeb864b988 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:26 +1100 Subject: [PATCH 31/62] New translations summary.md (Japanese) --- ja/SUMMARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/SUMMARY.md b/ja/SUMMARY.md index 1b2c6ebe66b2..c21489f7cccd 100644 --- a/ja/SUMMARY.md +++ b/ja/SUMMARY.md @@ -247,7 +247,7 @@ - [Benewake TFmini Lidar](sensor/tfmini.md) - [Lidar-Lite](sensor/lidar_lite.md) - [TeraRanger](sensor/teraranger.md) - - [Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) + - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) From c635da0cd9d3f821291147dcd1af7d6d6630d545 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:31 +1100 Subject: [PATCH 32/62] New translations summary.md (Korean) --- ko/SUMMARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/SUMMARY.md b/ko/SUMMARY.md index e7e892e447ce..bd92660a49f7 100644 --- a/ko/SUMMARY.md +++ b/ko/SUMMARY.md @@ -247,7 +247,7 @@ - [Benewake TFmini 라이다](sensor/tfmini.md) - [Lidar-Lite](sensor/lidar_lite.md) - [TeraRanger ](sensor/teraranger.md) - - [Lanbao PSK-CM8JL65-CC5 ](sensor/cm8jl65_ir_distance_sensor.md) + - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) From 6ab9fef470209d458941274eaf9924d9f6f6d78f Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:36 +1100 Subject: [PATCH 33/62] New translations summary.md (Turkish) --- tr/SUMMARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/SUMMARY.md b/tr/SUMMARY.md index bb6da6734208..0a1316e27e6a 100644 --- a/tr/SUMMARY.md +++ b/tr/SUMMARY.md @@ -247,7 +247,7 @@ - [Benewake TFmini Lidar](sensor/tfmini.md) - [Lidar-Lite](sensor/lidar_lite.md) - [TeraRanger](sensor/teraranger.md) - - [Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) + - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) From 21fcd8e88cb6f0b3621c156ec13c7993d5921f4c Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:42 +1100 Subject: [PATCH 34/62] New translations summary.md (Ukrainian) --- uk/SUMMARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/SUMMARY.md b/uk/SUMMARY.md index d1e5238653c0..e56920754654 100644 --- a/uk/SUMMARY.md +++ b/uk/SUMMARY.md @@ -247,7 +247,7 @@ - [Benewake TFmini Lidar](sensor/tfmini.md) - [Lidar-Lite](sensor/lidar_lite.md) - [TeraRanger](sensor/teraranger.md) - - [Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) + - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) From ff49c048c843d3a59d5c31253b3480f686c5242c Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:47 +1100 Subject: [PATCH 35/62] New translations summary.md (Chinese Simplified) --- zh/SUMMARY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/SUMMARY.md b/zh/SUMMARY.md index 913a7606f1e1..e3e9cac52f52 100644 --- a/zh/SUMMARY.md +++ b/zh/SUMMARY.md @@ -247,7 +247,7 @@ - [北醒 TFmini 激光雷达](sensor/tfmini.md) - [Lidar-Lite](sensor/lidar_lite.md) - [TeraRanger](sensor/teraranger.md) - - [兰宝 PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) + - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) From fc837b66cc7d064254c7cb925fcdba458a3f2bc0 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:54 +1100 Subject: [PATCH 36/62] New translations cm8jl65_ir_distance_sensor.md (Japanese) --- ja/sensor/cm8jl65_ir_distance_sensor.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/ja/sensor/cm8jl65_ir_distance_sensor.md b/ja/sensor/cm8jl65_ir_distance_sensor.md index 73952501ebbb..2c830b0be852 100644 --- a/ja/sensor/cm8jl65_ir_distance_sensor.md +++ b/ja/sensor/cm8jl65_ir_distance_sensor.md @@ -1,4 +1,10 @@ -# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor +# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor (Discontinued) + + + +:::warning +This product has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) is a very small IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. @@ -10,7 +16,7 @@ It must be connected to a UART/serial bus. ## Hardware Setup -PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELEM3, GPS2 etc. +PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: `TELEM2`, `TELEM3`, `GPS2` etc. The pinouts are labeled on the bottom of the sensor: @@ -20,8 +26,7 @@ The pinouts are labeled on the bottom of the sensor: [Configure the serial port](../peripherals/serial_configuration.md) on which the lidar will run using [SENS_CM8JL65_CFG](../advanced_config/parameter_reference.md#SENS_CM8JL65_CFG). -::: info - +:::info If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware): ```plain From e922ab6dd3da5dcca0983120eded1c7ccd7acf95 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:56 +1100 Subject: [PATCH 37/62] New translations cm8jl65_ir_distance_sensor.md (Korean) --- ko/sensor/cm8jl65_ir_distance_sensor.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/ko/sensor/cm8jl65_ir_distance_sensor.md b/ko/sensor/cm8jl65_ir_distance_sensor.md index 68fdb58d0b42..eee5b5ce6824 100644 --- a/ko/sensor/cm8jl65_ir_distance_sensor.md +++ b/ko/sensor/cm8jl65_ir_distance_sensor.md @@ -1,4 +1,10 @@ -# Lanbao PSK-CM8JL65-CC5 ToF 적외선 거리 측정 센서 +# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor (Discontinued) + + + +:::warning +This product has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) is a very small IR distance sensor with a 0.17m-8m range and millimeter resolution. UART/직렬 버스에 연결됩니다. @@ -10,7 +16,7 @@ UART/직렬 버스에 연결됩니다. ## 하드웨어 설정 -PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELEM3, GPS2 etc. +PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: `TELEM2`, `TELEM3`, `GPS2` etc. 핀배열은 센서 하단에 레이블이 있습니다. @@ -20,8 +26,7 @@ PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELE [Configure the serial port](../peripherals/serial_configuration.md) on which the lidar will run using [SENS_CM8JL65_CFG](../advanced_config/parameter_reference.md#SENS_CM8JL65_CFG). -::: info - +:::info If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware): ```plain From 1f0006991d861300ad043d673921ca821b0acc56 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:57 +1100 Subject: [PATCH 38/62] New translations cm8jl65_ir_distance_sensor.md (Turkish) --- tr/sensor/cm8jl65_ir_distance_sensor.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/tr/sensor/cm8jl65_ir_distance_sensor.md b/tr/sensor/cm8jl65_ir_distance_sensor.md index 73952501ebbb..2c830b0be852 100644 --- a/tr/sensor/cm8jl65_ir_distance_sensor.md +++ b/tr/sensor/cm8jl65_ir_distance_sensor.md @@ -1,4 +1,10 @@ -# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor +# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor (Discontinued) + + + +:::warning +This product has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) is a very small IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. @@ -10,7 +16,7 @@ It must be connected to a UART/serial bus. ## Hardware Setup -PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELEM3, GPS2 etc. +PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: `TELEM2`, `TELEM3`, `GPS2` etc. The pinouts are labeled on the bottom of the sensor: @@ -20,8 +26,7 @@ The pinouts are labeled on the bottom of the sensor: [Configure the serial port](../peripherals/serial_configuration.md) on which the lidar will run using [SENS_CM8JL65_CFG](../advanced_config/parameter_reference.md#SENS_CM8JL65_CFG). -::: info - +:::info If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware): ```plain From beae7c4a9afe8605b332cc03f32e33d6e3aae9d9 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:58 +1100 Subject: [PATCH 39/62] New translations cm8jl65_ir_distance_sensor.md (Ukrainian) --- uk/sensor/cm8jl65_ir_distance_sensor.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/uk/sensor/cm8jl65_ir_distance_sensor.md b/uk/sensor/cm8jl65_ir_distance_sensor.md index 4cbdc9d5db8f..c4e9eaef1603 100644 --- a/uk/sensor/cm8jl65_ir_distance_sensor.md +++ b/uk/sensor/cm8jl65_ir_distance_sensor.md @@ -1,4 +1,10 @@ -# Lanbao PSK-CM8JL65-CC5 ІЧ-датчик вимірювання відстані ToF +# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor (Discontinued) + + + +:::warning +This product has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) is a very small IR distance sensor with a 0.17m-8m range and millimeter resolution. Це повинно бути підключено до шини UART/серійного порту. @@ -10,7 +16,7 @@ The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrare ## Налаштування програмного забезпечення -PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELEM3, GPS2 etc. +PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: `TELEM2`, `TELEM3`, `GPS2` etc. Виводи позначені знизу сенсора: @@ -20,8 +26,7 @@ PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELE [Configure the serial port](../peripherals/serial_configuration.md) on which the lidar will run using [SENS_CM8JL65_CFG](../advanced_config/parameter_reference.md#SENS_CM8JL65_CFG). -::: info - +:::info If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware): ```plain From 574266b45f6e99eb484acaca852978799f1bc149 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:17:59 +1100 Subject: [PATCH 40/62] New translations cm8jl65_ir_distance_sensor.md (Chinese Simplified) --- zh/sensor/cm8jl65_ir_distance_sensor.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/zh/sensor/cm8jl65_ir_distance_sensor.md b/zh/sensor/cm8jl65_ir_distance_sensor.md index 37ea3e8bf5d4..e80caf71b150 100644 --- a/zh/sensor/cm8jl65_ir_distance_sensor.md +++ b/zh/sensor/cm8jl65_ir_distance_sensor.md @@ -1,4 +1,10 @@ -# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor +# Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor (Discontinued) + + + +:::warning +This product has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: The [Lanbao PSK-CM8JL65-CC5](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) is a very small IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. @@ -10,7 +16,7 @@ It must be connected to a UART/serial bus. ## 硬件安装 -PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: TELEM2, TELEM3, GPS2 etc. +PSK-CM8JL65-CC5 can be connected to any unused _serial port_, e.g.: `TELEM2`, `TELEM3`, `GPS2` etc. The pinouts are labeled on the bottom of the sensor: @@ -20,8 +26,7 @@ The pinouts are labeled on the bottom of the sensor: [Configure the serial port](../peripherals/serial_configuration.md) on which the lidar will run using [SENS_CM8JL65_CFG](../advanced_config/parameter_reference.md#SENS_CM8JL65_CFG). -::: info - +:::info If the configuration parameter is not available in _QGroundControl_ then you may need to [add the driver to the firmware](../peripherals/serial_configuration.md#parameter_not_in_firmware): ```plain From 62bc39094f824625e1e966064ea2bfbc5ff8a875 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:01 +1100 Subject: [PATCH 41/62] New translations pmw3901.md (Japanese) --- ja/sensor/pmw3901.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/sensor/pmw3901.md b/ja/sensor/pmw3901.md index c2a3ff0ee010..85ceb76eda12 100644 --- a/ja/sensor/pmw3901.md +++ b/ja/sensor/pmw3901.md @@ -35,7 +35,7 @@ Any [rangefinder/distance sensor](../sensor/rangefinders.md) supported by PX4 ma The sensor can be mounted anywhere but must point down, and should be connected/configured as usual. :::tip -The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) on smaller vehicles. +The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) (Discontinued) on smaller vehicles. ::: ## Mounting/Orientation From 82067f6e6cbe12b11854c2f85ac591b4f6129776 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:03 +1100 Subject: [PATCH 42/62] New translations pmw3901.md (Korean) --- ko/sensor/pmw3901.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/sensor/pmw3901.md b/ko/sensor/pmw3901.md index eedc18a26ae2..149f9b811a29 100644 --- a/ko/sensor/pmw3901.md +++ b/ko/sensor/pmw3901.md @@ -35,7 +35,7 @@ Any [rangefinder/distance sensor](../sensor/rangefinders.md) supported by PX4 ma 센서는 어디나 장착할 수 있지만, 아래를 향해야하며 평소와 같이 연결/설정하여야 합니다. :::tip -The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) on smaller vehicles. +The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) (Discontinued) on smaller vehicles. ::: ## 장착 및 방향 From 5805526ab8d113b3195e199291978f9cbd8e7b9c Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:04 +1100 Subject: [PATCH 43/62] New translations pmw3901.md (Turkish) --- tr/sensor/pmw3901.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/sensor/pmw3901.md b/tr/sensor/pmw3901.md index c2a3ff0ee010..85ceb76eda12 100644 --- a/tr/sensor/pmw3901.md +++ b/tr/sensor/pmw3901.md @@ -35,7 +35,7 @@ Any [rangefinder/distance sensor](../sensor/rangefinders.md) supported by PX4 ma The sensor can be mounted anywhere but must point down, and should be connected/configured as usual. :::tip -The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) on smaller vehicles. +The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) (Discontinued) on smaller vehicles. ::: ## Mounting/Orientation From e7ae9903c90021eb380f497beb27a758343cce1e Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:06 +1100 Subject: [PATCH 44/62] New translations pmw3901.md (Ukrainian) --- uk/sensor/pmw3901.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/sensor/pmw3901.md b/uk/sensor/pmw3901.md index cecd4db44ffa..6db09f9fe5dc 100644 --- a/uk/sensor/pmw3901.md +++ b/uk/sensor/pmw3901.md @@ -35,7 +35,7 @@ Any [rangefinder/distance sensor](../sensor/rangefinders.md) supported by PX4 ma Датчик може бути встановлений будь-де, але повинен бути спрямований вниз і повинен бути підключений/налаштований як зазвичай. :::tip -The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) on smaller vehicles. +The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) (Discontinued) on smaller vehicles. ::: ## Монтаж/Орієнтація From 852a0bf259de84abfeb8528c5a55ca10d0aa3853 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:07 +1100 Subject: [PATCH 45/62] New translations pmw3901.md (Chinese Simplified) --- zh/sensor/pmw3901.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/sensor/pmw3901.md b/zh/sensor/pmw3901.md index aa2af2cc41e8..28a3f03bfe47 100644 --- a/zh/sensor/pmw3901.md +++ b/zh/sensor/pmw3901.md @@ -35,7 +35,7 @@ Any [rangefinder/distance sensor](../sensor/rangefinders.md) supported by PX4 ma The sensor can be mounted anywhere but must point down, and should be connected/configured as usual. :::tip -The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) on smaller vehicles. +The PX4 team mainly tested using the [Lidar Lite V3](../sensor/lidar_lite.md) on larger vehicles and the [Lanbao CM8JL65](../sensor/cm8jl65_ir_distance_sensor.md) (Discontinued) on smaller vehicles. ::: ## Mounting/Orientation From 41aac93f8e794a76c03b3a38e58b1388e83265a9 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:09 +1100 Subject: [PATCH 46/62] New translations rangefinders.md (Japanese) --- ja/sensor/rangefinders.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ja/sensor/rangefinders.md b/ja/sensor/rangefinders.md index 200d8174c403..19569f12e469 100644 --- a/ja/sensor/rangefinders.md +++ b/ja/sensor/rangefinders.md @@ -69,6 +69,8 @@ The [Benewake TFmini Lidar](../sensor/tfmini.md) is a tiny, low cost, and low po ### PSK-CM8JL65-CC5 + + The [Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor](../sensor/cm8jl65_ir_distance_sensor.md) is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. From 0ea18e8bab2bd541172b64d49b3fc5b8f7f3edf5 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:10 +1100 Subject: [PATCH 47/62] New translations rangefinders.md (Korean) --- ko/sensor/rangefinders.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/ko/sensor/rangefinders.md b/ko/sensor/rangefinders.md index ac1ca1d95d2a..ad8f7e3a319e 100644 --- a/ko/sensor/rangefinders.md +++ b/ko/sensor/rangefinders.md @@ -69,6 +69,8 @@ The [Benewake TFmini Lidar](../sensor/tfmini.md) is a tiny, low cost, and low po ### PSK-CM8JL65-CC5 + + The [Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor](../sensor/cm8jl65_ir_distance_sensor.md) is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. UART/직렬 버스에 연결됩니다. @@ -107,14 +109,14 @@ The hardware and software setup that is _specific to each distance sensor_ is co The generic configuration that is _common to all distance sensors_, covering both the physical setup and usage, is given below. -### 일반 설정 +### Generic Configuration The common rangefinder configuration is specified using [EKF2_RNG\_\*](../advanced_config/parameter_reference.md#EKF2_RNG_CTRL) parameters. These include (non exhaustively): - [EKF2_RNG_POS_X](../advanced_config/parameter_reference.md#EKF2_RNG_POS_X), [EKF2_RNG_POS_Y](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Y), [EKF2_RNG_POS_Z](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Z) - offset of the rangefinder from the vehicle centre of gravity in X, Y, Z directions. - [EKF2_RNG_PITCH](../advanced_config/parameter_reference.md#EKF2_RNG_PITCH) - A value of 0 degrees (default) corresponds to the range finder being exactly aligned with the vehicle vertical axis (i.e. straight down), while 90 degrees indicates that the range finder is pointing forward. - 0이 아닌 피치가 사용되는 경우 간단한 삼각법을 사용하여 지면까지의 거리를 계산합니다. + Simple trigonometry is used to calculate the distance to ground if a non-zero pitch is used. - [EKF2_RNG_DELAY](../advanced_config/parameter_reference.md#EKF2_RNG_DELAY) - approximate delay of data reaching the estimator from the sensor. - [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 @@ -144,7 +146,7 @@ To view the rangefinder output: The tool will then plot the result: ![QGC Analyze DISTANCE\_SENSOR value](../../assets/qgc/analyze/qgc_analyze_tool_distance_sensor.png) -### QGroundControl MAVLink 콘솔 +### QGroundControl MAVLink Console You can also use the _QGroundControl MAVLink Console_ to observe the `distance_sensor` uORB topic: @@ -161,7 +163,7 @@ For more information see: [Development > Debugging/Logging > Sensor/Topic Debugg ## 시뮬레이션 -### Gazebo 시뮬레이션 +### Gazebo Simulation Lidar and sonar rangefinders can be used in the [Gazebo](../sim_gazebo_gz/index.md) simulator. To do this you must start the simulator using a vehicle model that includes the rangefinder. From 00144a1dc841c1da8aa8fc8361cd68e9cd0c9357 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:11 +1100 Subject: [PATCH 48/62] New translations rangefinders.md (Turkish) --- tr/sensor/rangefinders.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tr/sensor/rangefinders.md b/tr/sensor/rangefinders.md index 200d8174c403..19569f12e469 100644 --- a/tr/sensor/rangefinders.md +++ b/tr/sensor/rangefinders.md @@ -69,6 +69,8 @@ The [Benewake TFmini Lidar](../sensor/tfmini.md) is a tiny, low cost, and low po ### PSK-CM8JL65-CC5 + + The [Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor](../sensor/cm8jl65_ir_distance_sensor.md) is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. From ac3096b6cd381152e5d5052970756adedcb06ed8 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:13 +1100 Subject: [PATCH 49/62] New translations rangefinders.md (Ukrainian) --- uk/sensor/rangefinders.md | 42 ++++++++++++++++++++------------------- 1 file changed, 22 insertions(+), 20 deletions(-) diff --git a/uk/sensor/rangefinders.md b/uk/sensor/rangefinders.md index afb66c7e0754..d613fe0e41a8 100644 --- a/uk/sensor/rangefinders.md +++ b/uk/sensor/rangefinders.md @@ -69,10 +69,12 @@ The [Benewake TFmini Lidar](../sensor/tfmini.md) is a tiny, low cost, and low po ### PSK-CM8JL65-CC5 + + The [Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor](../sensor/cm8jl65_ir_distance_sensor.md) is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. Це повинно бути підключено до шини UART/серійного порту. -### Авіоніка Анонімний UAVCAN Лазерний Альтиметр Інтерфейс +### Avionics Anonymous UAVCAN Laser Altimeter Interface The [Avionics Anonymous UAVCAN Laser Altimeter Interface](../dronecan/avanon_laser_interface.md) allows several common rangefinders (e.g. [Lightware SF11/c, SF30/D](../sensor/sfxx_lidar.md), etc) to be connected to the [CAN](../can/index.md) bus via [DroneCAN](../dronecan/index.md), a more robust interface than I2C. @@ -93,7 +95,7 @@ Supported rangefinders include: [RaccoonLab µRANGEFINDER](https://docs.raccoonlab.co/guide/rangefinder/uRANGEFINDER.html) is designed to measure distance and publish it via Cyphal/DroneCAN protocols. It can be used to estimate precision landing or object avoidance. -Функції: +Features: - [VL53L1CBV0FY-1](https://www.st.com/resource/en/datasheet/vl53l1.pdf) sensor - Input voltage sensor @@ -101,30 +103,30 @@ It can be used to estimate precision landing or object avoidance. ## Configuration/Setup {#configuration} -Дальні вимірювачі зазвичай підключаються до порту або послідовного (PWM), або I2C (залежно від драйвера пристрою), і активуються на порту шляхом встановлення певного параметра. +Rangefinders are usually connected to either a serial (PWM) or I2C port (depending on the device driver), and are enabled on the port by setting a particular parameter. The hardware and software setup that is _specific to each distance sensor_ is covered in their individual topics. The generic configuration that is _common to all distance sensors_, covering both the physical setup and usage, is given below. -### Загальна конфігурація +### Generic Configuration The common rangefinder configuration is specified using [EKF2_RNG\_\*](../advanced_config/parameter_reference.md#EKF2_RNG_CTRL) parameters. -Ці включають (не вичерпно): +These include (non exhaustively): - [EKF2_RNG_POS_X](../advanced_config/parameter_reference.md#EKF2_RNG_POS_X), [EKF2_RNG_POS_Y](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Y), [EKF2_RNG_POS_Z](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Z) - offset of the rangefinder from the vehicle centre of gravity in X, Y, Z directions. - [EKF2_RNG_PITCH](../advanced_config/parameter_reference.md#EKF2_RNG_PITCH) - A value of 0 degrees (default) corresponds to the range finder being exactly aligned with the vehicle vertical axis (i.e. straight down), while 90 degrees indicates that the range finder is pointing forward. - Проста тригонометрія використовується для обчислення відстані до землі, якщо використовується ненульовий кут нахилу. + Simple trigonometry is used to calculate the distance to ground if a non-zero pitch is used. - [EKF2_RNG_DELAY](../advanced_config/parameter_reference.md#EKF2_RNG_DELAY) - approximate delay of data reaching the estimator from the sensor. - [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 ## Тестування -Найлегший спосіб перевірити дальномер - змінювати діапазон і порівнювати зі значеннями, виявленими PX4. -Нижче наведено деякі підходи до отримання виміряного діапазону. +The easiest way to test the rangefinder is to vary the range and compare to the values detected by PX4. +The sections below show some approaches to getting the measured range. -### Інспектор MAVLink QGroundControl +### QGroundControl MAVLink Inspector The _QGroundControl MAVLink Inspector_ lets you view messages sent from the vehicle, including `DISTANCE_SENSOR` information from the rangefinder. The main difference between the tools is that the _Analyze_ tool can plot values in a graph. @@ -134,7 +136,7 @@ The messages that are sent depend on the vehicle configuration. You will only get `DISTANCE_SENSOR` messages if the connected vehicle has a rangefinder installed and is publishing sensor values. ::: -Для перегляду виводу дальномера: +To view the rangefinder output: 1. Open the menu **Q > Select Tool > Analyze Tools**: @@ -144,7 +146,7 @@ You will only get `DISTANCE_SENSOR` messages if the connected vehicle has a rang The tool will then plot the result: ![QGC Analyze DISTANCE\_SENSOR value](../../assets/qgc/analyze/qgc_analyze_tool_distance_sensor.png) -### Консоль QGroundControl MAVLink +### QGroundControl MAVLink Console You can also use the _QGroundControl MAVLink Console_ to observe the `distance_sensor` uORB topic: @@ -154,17 +156,17 @@ listener distance_sensor 5 :::info The _QGroundControl MAVLink Console_ works when connected to Pixhawk or other NuttX targets, but not the Simulator. -На симуляторі ви можете виконувати команди безпосередньо в терміналі. +On the Simulator you can run the commands directly in the terminal. ::: For more information see: [Development > Debugging/Logging > Sensor/Topic Debugging using the Listener Command](../debug/sensor_uorb_topic_debugging.md). ## Симуляція -### Симуляція Gazebo +### Gazebo Simulation Lidar and sonar rangefinders can be used in the [Gazebo](../sim_gazebo_gz/index.md) simulator. -Для цього вам потрібно запустити симулятор, використовуючи модель автомобіля, яка включає дальномір. +To do this you must start the simulator using a vehicle model that includes the rangefinder. Downward facing sensors that write to the [DistanceSensor](../msg_docs/DistanceSensor.md) UORB topic can be used to test use cases such as [landing](../flight_modes_mc/land.md) and [terrain following](../flying/terrain_following_holding.md): @@ -188,25 +190,25 @@ Front-facing sensors that write to [ObstacleDistance](../msg_docs/ObstacleDistan make px4_sitl gz_x500_lidar_front ``` -### Класичний симулятор Gazebo +### Gazebo-Classic Simulation Lidar and sonar rangefinders can be used in the [Gazebo Classic](../sim_gazebo_classic/index.md) simulator. -Для цього вам потрібно запустити симулятор, використовуючи модель автомобіля, яка включає дальномір. +To do this you must start the simulator using a vehicle model that includes the rangefinder. -Модель оптичного потоку ірису включає лідарний дальномер: +The iris optical flow model includes a Lidar rangefinder: ```sh make px4_sitl gazebo-classic_iris_opt_flow ``` -Тайфун_h480 включає в себе зондовий дальномер: +The typhoon_h480 includes a sonar rangefinder: ```sh make px4_sitl gazebo-classic_typhoon_h480 ``` -Якщо вам потрібно використовувати інше транспортний засіб, ви можете включити модель у файл конфігурації. -Ви можете побачити, як у відповідних файлах конфігурації Iris та Typhoon: +If you need to use a different vehicle you can include the model in its configuration file. +You can see how in the respective Iris and Typhoon configuration files: - [iris_opt_flow.sdf](https://github.com/PX4/PX4-SITL_gazebo-classic/blob/main/models/iris_opt_flow/iris_opt_flow.sdf) From e30fe88754f1e3940f38fef2420a77d3f8f147c4 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:14 +1100 Subject: [PATCH 50/62] New translations rangefinders.md (Chinese Simplified) --- zh/sensor/rangefinders.md | 38 ++++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 18 deletions(-) diff --git a/zh/sensor/rangefinders.md b/zh/sensor/rangefinders.md index 925b7ada5d4d..f7eca8aaaf2b 100644 --- a/zh/sensor/rangefinders.md +++ b/zh/sensor/rangefinders.md @@ -69,10 +69,12 @@ The [Benewake TFmini Lidar](../sensor/tfmini.md) is a tiny, low cost, and low po ### PSK-CM8JL65-CC5 + + The [Lanbao PSK-CM8JL65-CC5 ToF Infrared Distance Measuring Sensor](../sensor/cm8jl65_ir_distance_sensor.md) is a very small (38 mm x 18mm x 7mm, <10g) IR distance sensor with a 0.17m-8m range and millimeter resolution. It must be connected to a UART/serial bus. -### Avionics Anonymous UAVCAN 激光高度计接口 +### Avionics Anonymous UAVCAN Laser Altimeter Interface The [Avionics Anonymous UAVCAN Laser Altimeter Interface](../dronecan/avanon_laser_interface.md) allows several common rangefinders (e.g. [Lightware SF11/c, SF30/D](../sensor/sfxx_lidar.md), etc) to be connected to the [CAN](../can/index.md) bus via [DroneCAN](../dronecan/index.md), a more robust interface than I2C. @@ -101,30 +103,30 @@ Features: ## Configuration/Setup {#configuration} -测距仪通常连接到串口(PWM)或者 I2C 接口(取决于设备驱动），并通过设置特定的参数在端口上启用。 +Rangefinders are usually connected to either a serial (PWM) or I2C port (depending on the device driver), and are enabled on the port by setting a particular parameter. The hardware and software setup that is _specific to each distance sensor_ is covered in their individual topics. The generic configuration that is _common to all distance sensors_, covering both the physical setup and usage, is given below. -### 常规配置 +### Generic Configuration The common rangefinder configuration is specified using [EKF2_RNG\_\*](../advanced_config/parameter_reference.md#EKF2_RNG_CTRL) parameters. -这些包括（非详尽）： +These include (non exhaustively): - [EKF2_RNG_POS_X](../advanced_config/parameter_reference.md#EKF2_RNG_POS_X), [EKF2_RNG_POS_Y](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Y), [EKF2_RNG_POS_Z](../advanced_config/parameter_reference.md#EKF2_RNG_POS_Z) - offset of the rangefinder from the vehicle centre of gravity in X, Y, Z directions. - [EKF2_RNG_PITCH](../advanced_config/parameter_reference.md#EKF2_RNG_PITCH) - A value of 0 degrees (default) corresponds to the range finder being exactly aligned with the vehicle vertical axis (i.e. straight down), while 90 degrees indicates that the range finder is pointing forward. - 如果使用非零间距，则使用简单的三角法计算到地面的距离。 + Simple trigonometry is used to calculate the distance to ground if a non-zero pitch is used. - [EKF2_RNG_DELAY](../advanced_config/parameter_reference.md#EKF2_RNG_DELAY) - approximate delay of data reaching the estimator from the sensor. - [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 ## 测试 -测试测距仪最简单的方法是改变距离并与 PX4 检测到的值进行比较 -以下部分显示了一些获取测量范围的方法。 +The easiest way to test the rangefinder is to vary the range and compare to the values detected by PX4. +The sections below show some approaches to getting the measured range. -### QGroundControl MAVLink 检查器 +### QGroundControl MAVLink Inspector The _QGroundControl MAVLink Inspector_ lets you view messages sent from the vehicle, including `DISTANCE_SENSOR` information from the rangefinder. The main difference between the tools is that the _Analyze_ tool can plot values in a graph. @@ -134,7 +136,7 @@ The messages that are sent depend on the vehicle configuration. You will only get `DISTANCE_SENSOR` messages if the connected vehicle has a rangefinder installed and is publishing sensor values. ::: -查看测距仪输出： +To view the rangefinder output: 1. Open the menu **Q > Select Tool > Analyze Tools**: @@ -144,7 +146,7 @@ You will only get `DISTANCE_SENSOR` messages if the connected vehicle has a rang The tool will then plot the result: ![QGC Analyze DISTANCE\_SENSOR value](../../assets/qgc/analyze/qgc_analyze_tool_distance_sensor.png) -### QGroundControl MAVLink 控制台 +### QGroundControl MAVLink Console You can also use the _QGroundControl MAVLink Console_ to observe the `distance_sensor` uORB topic: @@ -154,17 +156,17 @@ listener distance_sensor 5 :::info The _QGroundControl MAVLink Console_ works when connected to Pixhawk or other NuttX targets, but not the Simulator. -在模拟器上可以直接在终端中运行命令。 +On the Simulator you can run the commands directly in the terminal. ::: For more information see: [Development > Debugging/Logging > Sensor/Topic Debugging using the Listener Command](../debug/sensor_uorb_topic_debugging.md). ## 仿真 -### Gazebo 仿真 +### Gazebo Simulation Lidar and sonar rangefinders can be used in the [Gazebo](../sim_gazebo_gz/index.md) simulator. -要做到这一点，你必须在启动模拟器时使用一个拥有测距仪的机体模型。 +To do this you must start the simulator using a vehicle model that includes the rangefinder. Downward facing sensors that write to the [DistanceSensor](../msg_docs/DistanceSensor.md) UORB topic can be used to test use cases such as [landing](../flight_modes_mc/land.md) and [terrain following](../flying/terrain_following_holding.md): @@ -191,22 +193,22 @@ Front-facing sensors that write to [ObstacleDistance](../msg_docs/ObstacleDistan ### Gazebo-Classic Simulation Lidar and sonar rangefinders can be used in the [Gazebo Classic](../sim_gazebo_classic/index.md) simulator. -要做到这一点，你必须在启动模拟器时使用一个拥有测距仪的机体模型。 +To do this you must start the simulator using a vehicle model that includes the rangefinder. -iris 光流模型包括激光雷达测距仪： +The iris optical flow model includes a Lidar rangefinder: ```sh make px4_sitl gazebo-classic_iris_opt_flow ``` -typhoon_h480 包括一个声纳测距仪： +The typhoon_h480 includes a sonar rangefinder: ```sh make px4_sitl gazebo-classic_typhoon_h480 ``` -如果你需要使用一个不同的车辆，你可以在它的配置文件中包含此模型。 -你可以看到如何在相应的 Iris 和 Typhoon 配置文件： +If you need to use a different vehicle you can include the model in its configuration file. +You can see how in the respective Iris and Typhoon configuration files: - [iris_opt_flow.sdf](https://github.com/PX4/PX4-SITL_gazebo-classic/blob/main/models/iris_opt_flow/iris_opt_flow.sdf) From 5c83053210825311dd09c6b373a6339406fdbfe1 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:18 +1100 Subject: [PATCH 51/62] New translations thunderfly_tachometer.md (Ukrainian) --- uk/sensor/thunderfly_tachometer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/sensor/thunderfly_tachometer.md b/uk/sensor/thunderfly_tachometer.md index 573f6a63c774..80a8621eb92a 100644 --- a/uk/sensor/thunderfly_tachometer.md +++ b/uk/sensor/thunderfly_tachometer.md @@ -100,7 +100,7 @@ listener rpm For periodic display, you can add `-n 50` parameter after the command, which prints the next 50 messages. -#### Інспектор MAVLink QGroundControl +#### QGroundControl MAVLink Inspector The QGroundControl [Mavlink Inspector](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_inspector.html) can be used to observe MAVLink messages from PX4, including [RAW_RPM](https://mavlink.io/en/messages/common.html#RAW_RPM) emitted by the driver: From 2e7c659147fedb0128033ad248313041450548db Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:19 +1100 Subject: [PATCH 52/62] New translations thunderfly_tachometer.md (Chinese Simplified) --- zh/sensor/thunderfly_tachometer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/sensor/thunderfly_tachometer.md b/zh/sensor/thunderfly_tachometer.md index 6efb43d00967..ae32e7048194 100644 --- a/zh/sensor/thunderfly_tachometer.md +++ b/zh/sensor/thunderfly_tachometer.md @@ -100,7 +100,7 @@ listener rpm For periodic display, you can add `-n 50` parameter after the command, which prints the next 50 messages. -#### QGroundControl MAVLink 检查器 +#### QGroundControl MAVLink Inspector The QGroundControl [Mavlink Inspector](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_inspector.html) can be used to observe MAVLink messages from PX4, including [RAW_RPM](https://mavlink.io/en/messages/common.html#RAW_RPM) emitted by the driver: From 710f7b6e099e4a3f435ab14fab839aad8414654c Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:28 +1100 Subject: [PATCH 53/62] New translations index.md (Korean) --- ko/sim_gazebo_gz/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/sim_gazebo_gz/index.md b/ko/sim_gazebo_gz/index.md index 3a315aeff854..3ce8233038b8 100644 --- a/ko/sim_gazebo_gz/index.md +++ b/ko/sim_gazebo_gz/index.md @@ -1,4 +1,4 @@ -# Gazebo 시뮬레이션 +# Gazebo Simulation :::warning Gazebo was previously known as "Gazebo Ignition" (while _Gazebo Classic_ was previously known as Gazebo). From 797e6f002b2c2f68194089ac8c4d0d5adae9b142 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:30 +1100 Subject: [PATCH 54/62] New translations index.md (Ukrainian) --- uk/sim_gazebo_gz/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/sim_gazebo_gz/index.md b/uk/sim_gazebo_gz/index.md index 6fbc61938d77..ffc4a5e99066 100644 --- a/uk/sim_gazebo_gz/index.md +++ b/uk/sim_gazebo_gz/index.md @@ -1,4 +1,4 @@ -# Симуляція Gazebo +# Gazebo Simulation :::warning Gazebo was previously known as "Gazebo Ignition" (while _Gazebo Classic_ was previously known as Gazebo). From a3178b1be77ae41735271d1697727d9f02a6dde2 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:32 +1100 Subject: [PATCH 55/62] New translations index.md (Chinese Simplified) --- zh/sim_gazebo_gz/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/sim_gazebo_gz/index.md b/zh/sim_gazebo_gz/index.md index 6f9d9676e00f..065cada1a2c9 100644 --- a/zh/sim_gazebo_gz/index.md +++ b/zh/sim_gazebo_gz/index.md @@ -1,4 +1,4 @@ -# Gazebo 仿真 +# Gazebo Simulation :::warning Gazebo was previously known as "Gazebo Ignition" (while _Gazebo Classic_ was previously known as Gazebo). From ad87a8982cb234778c38b0bf9e52bb018b89ac8e Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:43 +1100 Subject: [PATCH 56/62] New translations collision_prevention.md (Korean) --- ko/computer_vision/collision_prevention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/computer_vision/collision_prevention.md b/ko/computer_vision/collision_prevention.md index 7e1b6d2b3251..cb27436fa930 100644 --- a/ko/computer_vision/collision_prevention.md +++ b/ko/computer_vision/collision_prevention.md @@ -198,7 +198,7 @@ The minimum rate at which messages _must_ be sent depends on vehicle speed - at Initial testing of the system used a vehicle moving at 4 m/s with `OBSTACLE_DISTANCE` messages being emitted at 10Hz (the maximum rate supported by the vision system). 시스템은 상당히 빠른 속도와 낮은 주파수 거리 업데이트에서 잘 작동 할 수 있습니다. -## Gazebo 시뮬레이션 +## Gazebo Simulation _Collision Prevention_ can be tested using [Gazebo](../sim_gazebo_gz/index.md) with the [x500_lidar_2d](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-2d-lidar) model. To do this, start a simulation with the x500 lidar model by running the following command: From 9bae3fcb3013c570f538e65307cb0fa248bf0f81 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:45 +1100 Subject: [PATCH 57/62] New translations collision_prevention.md (Ukrainian) --- uk/computer_vision/collision_prevention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/computer_vision/collision_prevention.md b/uk/computer_vision/collision_prevention.md index 56fdf651ab5a..2bb97de6e814 100644 --- a/uk/computer_vision/collision_prevention.md +++ b/uk/computer_vision/collision_prevention.md @@ -198,7 +198,7 @@ The minimum rate at which messages _must_ be sent depends on vehicle speed - at Initial testing of the system used a vehicle moving at 4 m/s with `OBSTACLE_DISTANCE` messages being emitted at 10Hz (the maximum rate supported by the vision system). Система може добре працювати при значно вищих швидкостях і менших частотах оновлення відстані. -## Симуляція Gazebo +## Gazebo Simulation _Collision Prevention_ can be tested using [Gazebo](../sim_gazebo_gz/index.md) with the [x500_lidar_2d](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-2d-lidar) model. To do this, start a simulation with the x500 lidar model by running the following command: From 21cf5649b0329fd0a540108d9b0c0a5aa202f984 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:47 +1100 Subject: [PATCH 58/62] New translations collision_prevention.md (Chinese Simplified) --- zh/computer_vision/collision_prevention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/computer_vision/collision_prevention.md b/zh/computer_vision/collision_prevention.md index 32ed523a3994..9d05d42b5b08 100644 --- a/zh/computer_vision/collision_prevention.md +++ b/zh/computer_vision/collision_prevention.md @@ -198,7 +198,7 @@ The minimum rate at which messages _must_ be sent depends on vehicle speed - at Initial testing of the system used a vehicle moving at 4 m/s with `OBSTACLE_DISTANCE` messages being emitted at 10Hz (the maximum rate supported by the vision system). 在更高的速度或更低的距离信息更新频率下，该系统应该也能达到不错的效果。 -## Gazebo 仿真 +## Gazebo Simulation _Collision Prevention_ can be tested using [Gazebo](../sim_gazebo_gz/index.md) with the [x500_lidar_2d](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-2d-lidar) model. To do this, start a simulation with the x500 lidar model by running the following command: From b09151e7c0e0ace59d8fa5706826527b0ec4f32d Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:49 +1100 Subject: [PATCH 59/62] New translations mavlink_shell.md (Korean) --- ko/debug/mavlink_shell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/debug/mavlink_shell.md b/ko/debug/mavlink_shell.md index 61d1bfe92056..d11d451f5db8 100644 --- a/ko/debug/mavlink_shell.md +++ b/ko/debug/mavlink_shell.md @@ -14,7 +14,7 @@ If the system does not start properly you should instead use the [System Console -### QGroundControl MAVLink 콘솔 +### QGroundControl MAVLink Console The easiest way to access shell is to use the [QGroundControl MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html) (see **Analyze View > Mavlink Console**). From b9f03d8fd9ae8a6ac92823506596d664ad210cf3 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:51 +1100 Subject: [PATCH 60/62] New translations mavlink_shell.md (Ukrainian) --- uk/debug/mavlink_shell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/debug/mavlink_shell.md b/uk/debug/mavlink_shell.md index 1d025a1775e8..ebfac42ef045 100644 --- a/uk/debug/mavlink_shell.md +++ b/uk/debug/mavlink_shell.md @@ -14,7 +14,7 @@ If the system does not start properly you should instead use the [System Console -### Консоль QGroundControl MAVLink +### QGroundControl MAVLink Console The easiest way to access shell is to use the [QGroundControl MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html) (see **Analyze View > Mavlink Console**). From d5e02bb46fb33cdf99e4b8a9495d98fb7b94340d Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:18:53 +1100 Subject: [PATCH 61/62] New translations mavlink_shell.md (Chinese Simplified) --- zh/debug/mavlink_shell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/debug/mavlink_shell.md b/zh/debug/mavlink_shell.md index d3502e584ccd..f13056ecc03d 100644 --- a/zh/debug/mavlink_shell.md +++ b/zh/debug/mavlink_shell.md @@ -14,7 +14,7 @@ If the system does not start properly you should instead use the [System Console -### QGroundControl MAVLink 控制台 +### QGroundControl MAVLink Console The easiest way to access shell is to use the [QGroundControl MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html) (see **Analyze View > Mavlink Console**). From bcd854846c0fd6c704bcaabc86fb52b8fc7a754b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 11 Dec 2024 14:19:00 +1100 Subject: [PATCH 62/62] New translations ark_pi6x.md (Ukrainian) --- uk/flight_controller/ark_pi6x.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/flight_controller/ark_pi6x.md b/uk/flight_controller/ark_pi6x.md index 8f2ac05a4f0d..f544e2240026 100644 --- a/uk/flight_controller/ark_pi6x.md +++ b/uk/flight_controller/ark_pi6x.md @@ -15,7 +15,7 @@ The [ARK Pi6X Flow](\(https://arkelectron.gitbook.io/ark-documentation/flight-co ### Raspberry Pi Compute Module 4 Carrier - Autopilot Firmware: PX4 -- Функції: +- Features: - MicroSD slot (for CM4 Lite) - Micro HDMI - Ethernet