diff --git a/docs/ko/SUMMARY.md b/docs/ko/SUMMARY.md index c16d59682fc..7245e4611dc 100644 --- a/docs/ko/SUMMARY.md +++ b/docs/ko/SUMMARY.md @@ -107,7 +107,7 @@ - [Build: Foxtech Loong 2160 VTOL](frames_vtol/vtol_quadplane_foxtech_loong_2160.md) - [FunCub QuadPlane (픽스호크)](frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md) - [Ranger QuadPlane (픽스호크)](frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md) - - [팔콘 Vertigo QuadPlane (Dropix)](frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md) + - [✘ Falcon Vertigo QuadPlane (Dropix)](frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md) - [테일시터 VTOL](frames_vtol/tailsitter.md) - [빌드: TBS Caipiroshka Tailsitter Build (Pixracer)](frames_vtol/vtol_tailsitter_caipiroshka_pixracer.md) - [틸트로터 VTOL](frames_vtol/tiltrotor.md) @@ -254,10 +254,11 @@ - [Lightware SF45 Rotary Lidar](sensor/sf45_rotating_lidar.md) - [Lightware GRF250/GRF500 Gimbal Lidar](sensor/grf_lidar.md) - [Sony AS-DT1 LiDAR](sensor/sony_asdt1.md) - - [TeraRanger ](sensor/teraranger.md) + - [✘ TeraRanger](sensor/teraranger.md) - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md) - [Avionics Anonymous Laser Altimeter UAVCAN Interface (CAN)](dronecan/avanon_laser_interface.md) - [GNSS (GPS)](gps_compass/index.md) + - [u-blox Diagnostics with u-center](gps_compass/u-center.md) - [ARK GPS (CAN)](dronecan/ark_gps.md) - [ARK DAN GPS](gps_compass/ark_dan_gps.md) - [ARK SAM GPS](gps_compass/ark_sam_gps.md) @@ -268,7 +269,7 @@ - [CUAV NEO 3X GPS (CAN)](gps_compass/gps_cuav_neo_3x.md) - [Holybro DroneCAN M8N GPS (CAN)](dronecan/holybro_m8n_gps.md) - [LOCOSYS Hawk A1 GNSS](gps_compass/gps_locosys_hawk_a1.md) - - [Hex Here2 (Discontinued)](gps_compass/gps_hex_here2.md) + - [✘ Hex Here2](gps_compass/gps_hex_here2.md) - [Holybro M8N & M9N GPS](gps_compass/gps_holybro_m8n_m9n.md) - [Sky-Drones SmartAP GPS](gps_compass/gps_smartap.md) - [RTK GNSS](gps_compass/rtk_gps.md) @@ -288,7 +289,7 @@ - [Freefly RTK GPS](gps_compass/rtk_gps_freefly.md) - [Holybro H-RTK ZED-F9P (DroneCAN)](dronecan/holybro_h_rtk_zed_f9p_gps.md) - [Holybro H-RTK-F9P](gps_compass/rtk_gps_holybro_h-rtk-f9p.md) - - [Holybro H-RTK-M8P](gps_compass/rtk_gps_holybro_h-rtk-m8p.md) + - [✘ Holybro H-RTK-M8P](gps_compass/rtk_gps_holybro_h-rtk-m8p.md) - [Holybro H-RTK Unicore UM982 GPS](gps_compass/rtk_gps_holybro_unicore_um982.md) - [Locosys Hawk R1](gps_compass/rtk_gps_locosys_r1.md) - [Locosys Hawk R2](gps_compass/rtk_gps_locosys_r2.md) @@ -296,7 +297,7 @@ - [Septentrio AsteRx-m3 Pro](gps_compass/septentrio_asterx-rib.md) - [Septentrio mosaic-go](gps_compass/septentrio_mosaic-go.md) - [Trimble MB-Two](gps_compass/rtk_gps_trimble_mb_two.md) - - [CubePilot Here+ (Discontined)](gps_compass/rtk_gps_hex_hereplus.md) + - [✘ CubePilot Here+](gps_compass/rtk_gps_hex_hereplus.md) - [INS (Inertial Navigation/GNSS)](sensor/inertial_navigation_systems.md) - [InertialLabs](sensor/inertiallabs.md) - [MicroStrain](sensor/microstrain.md) @@ -306,7 +307,7 @@ - [ARK Flow](dronecan/ark_flow.md) - [ARK Flow MR](dronecan/ark_flow_mr.md) - [PMW3901](sensor/pmw3901.md) - - [PX4FLOW (Deprecated)](sensor/px4flow.md) + - [✘ PX4FLOW](sensor/px4flow.md) - [회전계(회전 계수기)](sensor/tachometers.md) - [ThunderFly TFRPM01 타코미터 센서](sensor/thunderfly_tachometer.md) - [IMU Factory Calibration](advanced_config/imu_factory_calibration.md) @@ -348,13 +349,13 @@ - [Wifi 텔레메트리](telemetry/telemetry_wifi.md) - [ESP8266 WiFi 모듈](telemetry/esp8266_wifi_module.md) - [ESP32 WiFi Module](telemetry/esp32_wifi_module.md) - - [3DR Telemetry Wifi (Discontinued)](telemetry/3dr_telemetry_wifi.md) + - [✘ 3DR Telemetry Wifi](telemetry/3dr_telemetry_wifi.md) - [Microhard Serial Telemetry Radio](telemetry/microhard_serial.md) - [ARK Electron Microhard Serial Telemetry Radio](telemetry/ark_microhard_serial.md) - [Holybro Microhard P900 Telemetry Radio](telemetry/holybro_microhard_p900_radio.md) - [CUAV P8 Telemetry Radio](telemetry/cuav_p8_radio.md) - [J.Fi Wireless Telemetry Module](telemetry/jfi_telemetry.md) - - [HolyBro XBP9X - Discontinued](telemetry/holybro_xbp9x_radio.md) + - [✘ HolyBro XBP9X](telemetry/holybro_xbp9x_radio.md) - [FrSky 텔레메트리](peripherals/frsky_telemetry.md) @@ -382,7 +383,7 @@ - [RaccoonLab Power Modules](dronecan/raccoonlab_power.md) - [Sky-Drones SmartAP PDB](power_module/sky-drones_smartap-pdb.md) - [Smart/MAVLink Batteries](smart_batteries/index.md) - - [Rotoye Batmon 배터리 스마트 키트](smart_batteries/rotoye_batmon.md) + - [✘ Rotoye Batmon Battery Smartification Kit](smart_batteries/rotoye_batmon.md) - [탑재중량과 카메라](payloads/index.md) - [Use Cases](payloads/use_cases.md) @@ -692,7 +693,6 @@ - [GpioOut](msg_docs/GpioOut.md) - [GpioRequest](msg_docs/GpioRequest.md) - [GpsDump](msg_docs/GpsDump.md) - - [GpsInjectData](msg_docs/GpsInjectData.md) - [Gripper](msg_docs/Gripper.md) - [HealthReport](msg_docs/HealthReport.md) - [HeaterStatus](msg_docs/HeaterStatus.md) @@ -807,13 +807,13 @@ - [TrajectorySetpoint6dof](msg_docs/TrajectorySetpoint6dof.md) - [TransponderReport](msg_docs/TransponderReport.md) - [TuneControl](msg_docs/TuneControl.md) + - [UavcanFirmwareUpdate](msg_docs/UavcanFirmwareUpdate.md) - [UavcanParameterRequest](msg_docs/UavcanParameterRequest.md) - [UavcanParameterValue](msg_docs/UavcanParameterValue.md) - [UlogStream](msg_docs/UlogStream.md) - [UlogStreamAck](msg_docs/UlogStreamAck.md) - [VehicleAcceleration](msg_docs/VehicleAcceleration.md) - [VehicleAirData](msg_docs/VehicleAirData.md) - - [VehicleAngularAccelerationSetpoint](msg_docs/VehicleAngularAccelerationSetpoint.md) - [VehicleConstraints](msg_docs/VehicleConstraints.md) - [VehicleImu](msg_docs/VehicleImu.md) - [VehicleImuStatus](msg_docs/VehicleImuStatus.md) diff --git a/docs/ko/advanced_features/satcom_roadblock.md b/docs/ko/advanced_features/satcom_roadblock.md index 3008ed6c02b..bf212f0aaf6 100644 --- a/docs/ko/advanced_features/satcom_roadblock.md +++ b/docs/ko/advanced_features/satcom_roadblock.md @@ -51,7 +51,7 @@ The details of the [connectors](https://docs.groundcontrol.com/iot/rockblock/spe To [switch between the two antennas modes](https://docs.groundcontrol.com/iot/rockblock/user-manual/9603-atenna-mode) the position of a small RF link cable needs to changed. 외부 안테나를 사용하는 경우 모듈 손상을 방지하기 위해 안테나의 전원을 켜기 전에 항상 안테나가 모듈에 연결되어 있는 지 확인하십시오. -모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://www.groundcontrol.com/wp-content/uploads/2022/02/IRDM_ISU_ATCommandReferenceMAN0009_Rev2.0_ATCOMM_Oct2012.pdf). +모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://docs.groundcontrol.com/iot/rockblock/user-manual/at-commands). 1. Connect to the module with using a 19200/8-N-1 setting and check if the communication is working using the command: `AT`. The response should be: `OK`. diff --git a/docs/ko/airframes/airframe_reference.md b/docs/ko/airframes/airframe_reference.md index bdb007e75ab..7d5cb4d0f75 100644 --- a/docs/ko/airframes/airframe_reference.md +++ b/docs/ko/airframes/airframe_reference.md @@ -627,7 +627,7 @@ div.frame_variant td, div.frame_variant th { 유지보수: John Doe <john@example.com>

SYS_AUTOSTART = 51000

- Axial SCX10 2 Trail Honcho + Axial SCX10 2 Trail Honcho 유지보수: John Doe <john@example.com>

SYS_AUTOSTART = 51001

diff --git a/docs/ko/assembly/quick_start_cube.md b/docs/ko/assembly/quick_start_cube.md index 1037a50683c..11ce0f3735c 100644 --- a/docs/ko/assembly/quick_start_cube.md +++ b/docs/ko/assembly/quick_start_cube.md @@ -13,7 +13,7 @@ This quick start guide shows how to power the _Cube_® flight cont :::tip The instructions apply to all Cube variants, including [Cube Black](../flight_controller/pixhawk-2.md), [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md) and [Cube Orange](../flight_controller/cubepilot_cube_orange.md). -Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube) (Cube Docs). +Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/autopilot/the-cube) (Cube Docs). ::: ## 소품 @@ -195,7 +195,7 @@ If connecting peripherals to the port labeled `GPS2`, assign the PX4 [serial por ## 설정 -Configuration is performed using [QGroundContro](https://qgroundcontrol.com/). +Configuration is performed using [QGroundControl](https://qgroundcontrol.com/). After downloading, installing and running _QGroundControl_, connect the board to your computer as shown. @@ -220,5 +220,5 @@ PX4 펌웨어를 플래시한 후 [Program PX4IO(../getting_started/tunes.md#pro - [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md) - [Cube Orange](../flight_controller/cubepilot_cube_orange.md) - Cube 문서 (제조사) : - - [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) - - [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board) + - [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) + - [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board) diff --git a/docs/ko/config_fw/weight_and_altitude_tuning.md b/docs/ko/config_fw/weight_and_altitude_tuning.md index 75eb7a7d327..0d55f6c7159 100644 --- a/docs/ko/config_fw/weight_and_altitude_tuning.md +++ b/docs/ko/config_fw/weight_and_altitude_tuning.md @@ -1,6 +1,6 @@ # Advanced TECS Tuning (Weight and Altitude) -This topic shows how you can compensate for changes to the [weight of the vehicle](#vehicle-weight-compensation) and the [air density](#air-density-compensation), along with information about the [algorithms](#weight-and-density-compensation-algorithms) that are used. +This topic shows how you can compensate for changes to the [mass of the vehicle](#vehicle-weight-compensation) and the [air density](#air-density-compensation), along with information about the [algorithms](#weight-and-density-compensation-algorithms) that are used. :::warning This topic requires that you have already performed [basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed). @@ -9,25 +9,49 @@ This topic requires that you have already performed [basic TECS tuning](../confi [Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) established the key performance limitations of the vehicle that are required for the altitude and airspeed controller to function properly. While those limitations are specified using constant parameters, in reality vehicle performance is not constant and is affected by various factors. -If changes in weight and air density are not taken into account, altitude and airspeed tracking will likely deteriorate in the case where the configuration (air density and weight) deviate significantly from the configuration at which the vehicle was tuned. +If changes in vehicle mass and air density are not taken into account, altitude and airspeed tracking will likely deteriorate in the case where the configuration (air density and mass) deviate significantly from the configuration at which the vehicle was tuned. ## Vehicle Weight Compensation -Set (both) the following parameters to scale the maximum climb rate, minimum sink rate, and adjust airspeed limits for weight: +Set (both) the following parameters to scale the maximum climb rate, minimum sink rate, and adjust airspeed limits for the vehicle mass: -- [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the weight of the vehicle at which the [Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) was performed. -- [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the actual weight of the vehicle at any given time, for example when using a larger battery, or with a payload that was not present during tuning. +- [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) — the mass of the vehicle at which the [Basic TECS tuning](../config_fw/position_tuning_guide_fixedwing.md#tecs-tuning-altitude-and-airspeed) was performed. +- [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_GROSS) — the actual mass of the vehicle at any given time, for example when using a larger battery, or with a payload that was not present during tuning. -You can determine the values by measuring the weight of the vehicle using a scale in the tuning configuration and when flying with a payload. +You can determine the values by measuring the mass of the vehicle using a scale in the tuning configuration and when flying with a payload. + +:::info +The `WEIGHT_*` parameters are masses in kilograms; the parameter names and the derived _weight ratio_ (the ratio of the current vehicle mass to `WEIGHT_BASE`) use "weight" following common aviation usage. +::: Scaling is performed when _both_ `WEIGHT_BASE` and `WEIGHT_GROSS` are greater than `0`, and will have no effect if the values are the same. See the [algorithms](#weight-and-density-compensation-algorithms) section below for more information. +### Fuel Burn Compensation + +On combustion-engine vehicles a significant proportion of the takeoff mass is fuel, so the vehicle mass decreases considerably over the course of a flight. +If a fuel tank sensor is present (publishing to the [FuelTankStatus](../msg_docs/FuelTankStatus.md) message, for example from a [DroneCAN](../dronecan/index.md) engine ECU), PX4 can continuously estimate the current vehicle mass from the amount of burned fuel. + +To enable this, additionally set: + +- [WEIGHT_FUEL](../advanced_config/parameter_reference.md#WEIGHT_FUEL) — the mass of a full fuel load (tank capacity multiplied by fuel density). + +When `WEIGHT_FUEL` is greater than `0`, `WEIGHT_GROSS` must be set to the takeoff mass with a _full_ tank. +The current mass is then computed from the measured fraction of fuel remaining, so no parameter update is needed when taking off with a partially filled tank. +The measured fuel level is low-pass filtered to reject fuel slosh. + +If no fuel data is available (no sensor, or the sensor fails before boot), any mass-based scaling makes the conservative assumption that the vehicle is at the full gross mass (including fuel). +If fuel data is lost mid-flight, the last known fuel state is kept. + +Fuel-consumption compensation is only applied to the fuel tank with id `0` (the default id for single-tank systems). +Multi-tank vehicles should publish the aggregated total fuel state as tank `0`. +A warning is shown if fuel data is not received from id `0` but is received for other tank ids. + ## Air Density Compensation ### Specify a Service Ceiling -In PX4 the service ceiling [FW_SERVICE_CEIL](../advanced_config/parameter_reference.md#FW_SERVICE_CEIL) specifies the altitude in standard atmospheric conditions at which the vehicle is still able to achieve a maximum climb rate of 0.5 m/s at maximum throttle and weight equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE). +In PX4 the service ceiling [FW_SERVICE_CEIL](../advanced_config/parameter_reference.md#FW_SERVICE_CEIL) specifies the altitude in standard atmospheric conditions at which the vehicle is still able to achieve a maximum climb rate of 0.5 m/s at maximum throttle and a vehicle mass equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE). By default this parameter is disabled and no compensation will take place. This parameter needs to be determined experimentally. @@ -61,11 +85,11 @@ This is provided for interest only, and may be of interest to developers who wan ### 표기법 In the following sections we will use the notation $\hat X$ to specify that this value is a calibrated value of the variable $X$. -By calibrated we mean the value of that variable measured at sea level in standard atmospheric conditions, and when vehicle weight was equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE). +By calibrated we mean the value of that variable measured at sea level in standard atmospheric conditions, and when the vehicle mass was equal to [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE). 예: by $\hat{\dot{h}}_{\text{max}}$ we specify the maximum climb rate the vehicle can achieve at [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) at sea level in standard atmospheric conditions. -### Effect of Weight on Maximum Climb Rate +### Effect of Mass on Maximum Climb Rate The maximum climb rate ([FW_T_CLMB_MAX](../advanced_config/parameter_reference.md#FW_T_CLMB_MAX)) is scaled as a function of the weight ratio. @@ -76,7 +100,7 @@ $$\dot{h}_{\text{max}} = \frac{V \cdot (\text{Thrust} - \text{Drag})}{m \cdot g} where `V` is the true airspeed and `m` is the vehicle mass. From this equation we see that the maximum climb rates scales with vehicle mass. -### Effect of Weight on Minimum Sink Rate +### Effect of Mass on Minimum Sink Rate The minimum sink rate ([FW_T_SINK_MIN](../advanced_config/parameter_reference.md#FW_T_SINK_MIN)) is scaled as a function of weight ratio @@ -88,7 +112,7 @@ where $\rho$ is the air density, S is the wing surface reference area and $f(C_L From this equation we see that the minimum sink rate scales with the square root of the weight ratio. -### Effect of Weight on Airspeed Limits +### Effect of Mass on Airspeed Limits The minimum airspeed ([FW_AIRSPD_MIN](../advanced_config/parameter_reference.md#FW_AIRSPD_MIN)), the stall airspeed ([FW_AIRSPD_STALL](../advanced_config/parameter_reference.md#FW_AIRSPD_STALL)) and trim airspeed ([FW_AIRSPD_TRIM](../advanced_config/parameter_reference.md#FW_AIRSPD_TRIM)) are adjusted based on the weight ratio specified by [WEIGHT_BASE](../advanced_config/parameter_reference.md#WEIGHT_BASE) and [WEIGHT_GROSS](../advanced_config/parameter_reference.md#WEIGHT_GROSS). @@ -100,12 +124,12 @@ rearranging this equation for airspeed gives: $$V = \sqrt{\frac{2mg}{\rho S C_L}}$$ -From this equation we see that if we assume a constant angle of attack (which we generally desire), the vehicle weight affects airspeed with a square root relation. +From this equation we see that if we assume a constant angle of attack (which we generally desire), the vehicle mass affects airspeed with a square root relation. Therefore, the airspeed limits mentioned above are all scaled using the square root of the weight ratio. ### Effect of Bank Angle on Airspeed Limits -Flying a coordinated, level turn at bank angle $\phi$ increases the load factor by $\frac{1}{\cos{\phi}}$. This is similar to the added load factor due to weight (section above), and thus the stall and minimum airspeeds are increased by an additional factor of $\sqrt{\frac{1}{\cos{\phi}}}$. +Flying a coordinated, level turn at bank angle $\phi$ increases the load factor by $\frac{1}{\cos{\phi}}$. This is similar to the added load factor due to increased mass (section above), and thus the stall and minimum airspeeds are increased by an additional factor of $\sqrt{\frac{1}{\cos{\phi}}}$. The maximum airspeed ([FW_AIRSPD_MAX](../advanced_config/parameter_reference.md#FW_AIRSPD_MAX)) is _not_ compensated in this way, as it can represent structural limits of the airframe. diff --git a/docs/ko/config_mc/index.md b/docs/ko/config_mc/index.md index 786532994cd..a8935bc9f28 100644 --- a/docs/ko/config_mc/index.md +++ b/docs/ko/config_mc/index.md @@ -142,6 +142,11 @@ Tuning is the final step, carried out only after most other setup and configurat - [Multicopter Racer Setup](../config_mc/racer_setup.md) +- [Genius Tools](https://www.altitude-rd.com/genius-tools) — a commercial web app for interactive multicopter tuning from a flight log. + Bugs and questions should be addressed to the maintainer: [Altitude R&D](https://www.altitude-rd.com/home) (not the PX4 forums). + +![Genius Tools](../../assets/config/mc/genius_tools.webp) + -[swd]: https://developer.arm.com/documentation/ihi0031/a/The-Serial-Wire-Debug-Port--SW-DP- -[itm]: https://developer.arm.com/documentation/ddi0403/d/Appendices/Debug-ITM-and-DWT-Packet-Protocol?lang=en -[etm]: https://developer.arm.com/documentation/ihi0064/latest/ +[swd]: https://support.arm.com/documentation/ihi0031/a/The-Serial-Wire-Debug-Port--SW-DP- +[itm]: https://support.arm.com/documentation/ddi0403/d/Appendices/Debug-ITM-and-DWT-Packet-Protocol?lang=en +[etm]: https://support.arm.com/documentation/ihi0064/latest/ diff --git a/docs/ko/flight_controller/beaglebone_blue.md b/docs/ko/flight_controller/beaglebone_blue.md index 5e1b591db0c..8d6612660c3 100644 --- a/docs/ko/flight_controller/beaglebone_blue.md +++ b/docs/ko/flight_controller/beaglebone_blue.md @@ -31,6 +31,12 @@ The latest OS images at time of updating this document is [AM3358 Debian 10.3 20 ## 크로스 컴파일러 빌드 (권장) +:::warning +The Linaro toolchain previously recommended has been discontinued. +The instructions below have been updated to use its replacement (the Arm GNU Toolchain) but the changes **have not been tested**. +Please add a PR to either remove this comment or fix the instructions if you try them! +::: + The recommended way to build PX4 for _BeagleBone Blue_ is to compile on a development computer and upload the PX4 executable binary directly to the BeagleBone Blue. :::tip @@ -114,7 +120,7 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd cd /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf ``` - The ARM Cross Compiler for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/#gnu_and_llvm). + The ARM Cross Compiler for _BeagleBone Blue_ can be found at the [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads) site (the official successor to the Linaro toolchain releases previously used here). ::: tip GCC in the toolchain should be compatible with kernel in _BeagleBone Blue_. @@ -122,13 +128,13 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd ::: - Download and unpack [gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz](https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder. + Download and unpack [arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz](https://developer.arm.com/-/media/Files/downloads/gnu/15.2.rel1/binrel/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz) to the bbblue_toolchain folder. - Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at [Linaro Toolchain Binaries site](https://www.linaro.org/downloads/). + Different ARM Cross Compiler versions for _BeagleBone Blue_ can be found at the [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads) site. ```sh - wget https://snapshots.linaro.org/gnu-toolchain/13.0-2022.06-1/arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz - tar -xf gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf.tar.xz + wget https://developer.arm.com/-/media/Files/downloads/gnu/15.2.rel1/binrel/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz + tar -xf arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf.tar.xz ``` ::: tip @@ -138,10 +144,24 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd As a general rule of thumb is to choose a toolchain where the version of GCC is not higher than the version of GCC which comes with the OS image on _BeagleBone Blue_. + ::: warning + PX4's build for this board looks specifically for compiler binaries named `arm-linux-gnueabihf-*` (the naming used by the old Linaro toolchain), but the Arm GNU Toolchain ships them as `arm-none-linux-gnueabihf-*`. + Create matching symlinks so the build can find them: + + ```sh + cd /opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf/bin + for f in arm-none-linux-gnueabihf-*; do + ln -s "$f" "${f/arm-none-linux-gnueabihf/arm-linux-gnueabihf}" + done + ``` + + +::: + 2. Add it to the PATH in ~/.profile as shown below ```sh - export PATH=$PATH:/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/gcc-linaro-13.0.0-2022.06-x86_64_arm-linux-gnueabihf/bin + export PATH=$PATH:/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf/arm-gnu-toolchain-15.2.rel1-x86_64-arm-none-linux-gnueabihf/bin ``` ::: info diff --git a/docs/ko/flight_controller/cubepilot_cube_orange.md b/docs/ko/flight_controller/cubepilot_cube_orange.md index f52e3220cd1..71629a6448d 100644 --- a/docs/ko/flight_controller/cubepilot_cube_orange.md +++ b/docs/ko/flight_controller/cubepilot_cube_orange.md @@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://cubepilot.org/#/home) for hardware support or compliance issues. ::: -The [Cube Orange](https://www.cubepilot.com/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems. +The [Cube Orange](https://cubepilot.org/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems. ![Cube Orange](../../assets/flight_controller/cube/orange/cube_orange_hero.jpg) @@ -19,7 +19,7 @@ This is automatically configured and enabled in the default PX4 firmware. Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다. :::tip -The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications). +The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications). ::: :::info @@ -42,7 +42,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo ## Where to Buy {#store} -- [Reseller list](https://www.cubepilot.com/#/reseller/list) +- [Reseller list](https://cubepilot.org/#/reseller/list) ## 조립 @@ -246,5 +246,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h - [Cube Wiring Quickstart](../assembly/quick_start_cube.md) - Cube 문서 (제조사) : - - [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) - - [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board) + - [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) + - [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board) diff --git a/docs/ko/flight_controller/cubepilot_cube_orangeplus.md b/docs/ko/flight_controller/cubepilot_cube_orangeplus.md index 171c9f4aeb0..e5aa2bc1e25 100644 --- a/docs/ko/flight_controller/cubepilot_cube_orangeplus.md +++ b/docs/ko/flight_controller/cubepilot_cube_orangeplus.md @@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://cubepilot.org/#/home) for hardware support or compliance issues. ::: -The [Cube Orange+](https://www.cubepilot.com/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems. +The [Cube Orange+](https://cubepilot.org/#/cube/features) flight controller is a flexible autopilot intended primarily for manufacturers of commercial systems. Cube Orange+ is similar to Cube Orange, but has a more powerful dual-core processor (STM32H757), and some different sensor parts. ![Cube Orange](../../assets/flight_controller/cube/orangeplus/cubepilot_cube_orangeplus_standard_set.jpg) @@ -20,7 +20,7 @@ This is automatically configured and enabled in the default PX4 firmware. Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다. :::tip -The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications). +The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications). ::: :::info @@ -43,7 +43,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo ## Where to Buy {#store} -- [Reseller list](https://www.cubepilot.com/#/reseller/list) +- [Reseller list](https://cubepilot.org/#/reseller/list) ## 조립 @@ -251,5 +251,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h - [Cube Wiring Quickstart](../assembly/quick_start_cube.md) - Cube 문서 (제조사) : - - [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) - - [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board) + - [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) + - [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board) diff --git a/docs/ko/flight_controller/cubepilot_cube_yellow.md b/docs/ko/flight_controller/cubepilot_cube_yellow.md index ba02f82b427..a5ef2adafd4 100644 --- a/docs/ko/flight_controller/cubepilot_cube_yellow.md +++ b/docs/ko/flight_controller/cubepilot_cube_yellow.md @@ -15,7 +15,7 @@ For example, a carrier board for a commercial inspection vehicle might include c Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다. :::tip -The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications). +The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications). ::: :::info @@ -38,7 +38,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo ## Where to Buy {#store} -- [Reseller list](https://www.cubepilot.com/#/reseller/list) +- [Reseller list](https://cubepilot.org/#/reseller/list) ## 조립 @@ -144,5 +144,5 @@ Cube의 CAN1과 CAN2의 실크 스크린이 뒤집힙니다. CAN1은 CAN2이고 - [Cube Wiring Quickstart](../assembly/quick_start_cube.md) - Cube 문서 (제조사) : - - [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) - - [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board) + - [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) + - [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board) diff --git a/docs/ko/flight_controller/pixhawk-2.md b/docs/ko/flight_controller/pixhawk-2.md index a2daa87681f..33f44fa3eaf 100644 --- a/docs/ko/flight_controller/pixhawk-2.md +++ b/docs/ko/flight_controller/pixhawk-2.md @@ -11,7 +11,7 @@ We recommend however to consider products built on industry standards, such as t 이 비행 컨트롤러는 표준을 따르지 않으며, 특허받은 커넥터를 사용합니다. ::: -The [Hex Cube Black](https://docs.cubepilot.org/user-guides/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems. +The [Hex Cube Black](https://docs.cubepilot.org/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems. It is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv3** open hardware design and runs PX4 on the [NuttX](https://nuttx.apache.org/) OS. ![Cube Black](../../assets/flight_controller/cube/cube_black_hero.png) @@ -23,7 +23,7 @@ while a carrier board for a racer could includes ESCs form the frame of the vehi Cube에는 2 개의 IMU에 진동 차단이 포함되어 있으며, 세 번째 고정 IMU는 참조 백업용으로 사용됩니다. :::info -The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications). +The manufacturer [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/autopilot/the-cube/introduction/specifications). ::: :::tip @@ -49,7 +49,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md ## Where to Buy {#store} -[Cube Black](https://www.cubepilot.com/#/reseller/list) (Reseller list) +[Cube Black](https://cubepilot.org/#/reseller/list) (Reseller list) ## 조립 @@ -165,5 +165,5 @@ Cube Black의 CAN1과 CAN2의 실크 스크린이 뒤집힙니다 (CAN1은 CAN2 - [Cube Wiring Quickstart](../assembly/quick_start_cube.md) - Cube 문서 (제조사) : - - [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) - - [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board) + - [Cube User Guide](https://docs.cubepilot.org/autopilot/the-cube) + - [Mini Carrier Board](https://docs.cubepilot.org/carrier-boards/mini-carrier-board) diff --git a/docs/ko/flight_modes/return.md b/docs/ko/flight_modes/return.md index 6959e6cd0f8..fc45e585911 100644 --- a/docs/ko/flight_modes/return.md +++ b/docs/ko/flight_modes/return.md @@ -52,13 +52,13 @@ At high level these are: - [Mission path return](#rtl_type_2) (`RTL_TYPE=2`): Use mission path and fast-continue to mission landing (if defined). If no mission _landing_ defined, fast-reverse mission to home. If no _mission_ defined, return direct to home (rally points are ignored). -- [Closest safe destination return](#closest-safe-destination-return-type-rtl-type-3) (`RTL_TYPE=3`): Ascend to a safe altitude and return via direct path to closest destination: home, start of mission landing pattern, or rally point. +- [Closest safe destination return](#rtl_type_3) (`RTL_TYPE=3`): Ascend to a safe altitude and return via direct path to closest destination: home, start of mission landing pattern, or rally point. 목적지가 임무 착륙 패턴인 경우 패턴을 따라 착륙합니다. -- [Closest mission landing or reverse mission return](#closest-mission-landing-or-reverse-mission-return-type-rtl-type-4) (`RTL_TYPE=4`): Like `RTL_TYPE=2`, but chooses between mission landing and reverse mission path based on which requires fewer waypoints to traverse. +- [Closest mission landing or reverse mission return](#rtl_type_4) (`RTL_TYPE=4`): Like `RTL_TYPE=2`, but chooses between mission landing and reverse mission path based on which requires fewer waypoints to traverse. Rally points are not considered. -- [Rally point return](#rally-point-return-type-rtl-type-5) (`RTL_TYPE=5`): Return directly to the closest rally point, ignoring home and mission landing. +- [Rally point return](#rtl_type_5) (`RTL_TYPE=5`): Return directly to the closest rally point, ignoring home and mission landing. If no rally point is defined, land at the current position. -- [Battery-aware home priority return](#battery-aware-home-priority-return-type-rtl-type-6) (`RTL_TYPE=6`): Return to home if the estimated flight time is within the remaining battery time, otherwise return to the closest rally point. +- [Battery-aware home priority return](#rtl_type_6) (`RTL_TYPE=6`): Return to home if the estimated flight time is within the remaining battery time, otherwise return to the closest rally point. Falls back to the closest safe point (home or rally) if the remaining battery time is unknown/unavailable. 각 유형에 대한 자세한 설명은 다음 섹션에서 제공됩니다. @@ -164,7 +164,7 @@ In this return type, the vehicle: By default an MC or VTOL in MC mode will land, and a fixed-wing vehicle circles at the descent altitude. A VTOL in FW mode aligns its heading to the destination point, transitions to MC mode, and then lands. -### Closest of Mission Landing or Reverse Mission Return Type (RTL_TYPE=4) +### Closest of Mission Landing or Reverse Mission Return Type (RTL_TYPE=4) {#rtl_type_4} This return type is similar to [Mission Path Return (RTL_TYPE=2)](#mission-path-return-type-rtl-type-2), but selects between the forward mission landing and the reverse mission path based on which requires fewer waypoints to traverse from the current position (instead of always preferring the forward mission landing). @@ -178,7 +178,7 @@ In this return type, the vehicle: - Rally points are not considered. - Landing behaviour at the destination follows the same rules as RTL_TYPE=2. -### Rally Point Return Type (RTL_TYPE=5) +### Rally Point Return Type (RTL_TYPE=5) {#rtl_type_5} In this return type, the vehicle ignores home and mission landing patterns entirely and returns only to rally points: @@ -191,7 +191,7 @@ If no rally points are defined the vehicle will land at its current position ins This type is intended for use cases where only pre-approved rally points are acceptable landing destinations. ::: -### Battery-Aware Home Priority Return Type (RTL_TYPE=6) +### Battery-Aware Home Priority Return Type (RTL_TYPE=6) {#rtl_type_6} In this return type, the vehicle uses the estimated flight time to home compared against the remaining battery time to decide the return destination. @@ -207,7 +207,7 @@ The vehicle: ## Geofence Awareness {#geofence_awareness} - + For most of the return types (including the default home/rally point return type) the return path is chosen to avoid breaching any geofence. Planning is purely horizontal: the altitude profile is unaffected, and only the lateral path is adjusted to avoid the fence. diff --git a/docs/ko/frames_plane/reptile_dragon_2.md b/docs/ko/frames_plane/reptile_dragon_2.md index 7bbb7393723..f6416072177 100644 --- a/docs/ko/frames_plane/reptile_dragon_2.md +++ b/docs/ko/frames_plane/reptile_dragon_2.md @@ -58,7 +58,7 @@ Key build features - [Caddx Vista FPV air unit](https://www.caddxfpv.com/collections/vista-kit) -- [Emax ES08MA ii](https://emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo) +- [Emax ES08MA ii](https://shop.emaxmodel.com/products/emax-es08ma-ii-12g-mini-metal-gear-analog-servo-for-rc-model-robot-pwm-servo) - [DJI FPV Goggles](https://www.dji.com/fpv) diff --git a/docs/ko/gps_compass/gps_hex_here2.md b/docs/ko/gps_compass/gps_hex_here2.md index d461e7b0c42..ba01d9a97a9 100644 --- a/docs/ko/gps_compass/gps_hex_here2.md +++ b/docs/ko/gps_compass/gps_hex_here2.md @@ -1,7 +1,7 @@ # HEX/ProfiCNC Here2 GPS (Discontinued) :::warning -This has been superseded by the [Cube Here 3](https://www.cubepilot.com/#/here/here3) +This has been superseded by the [Cube Here 3](https://cubepilot.org/#/here/here3) ::: The _Here2 GPS receiver_ is an update to the Here GPS module from HEX. @@ -18,7 +18,7 @@ The _Here2 GPS receiver_ is an update to the Here GPS module from HEX. ## 구매처 -- [Resellers](https://www.cubepilot.com/#/reseller/list) +- [Resellers](https://cubepilot.org/#/reseller/list) ## 설정 @@ -26,8 +26,8 @@ PX4의 설정과 사용법은 대부분 플러그앤플레이입니다. ::: info -- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/user-guides/here-2/updating-here-2-firmware). -- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/user-guides/here-2/here-2-can-mode-instruction). +- If the GPS is _not detected_ then [update the Here2 firmware](https://docs.cubepilot.org/here-2/updating-here-2-firmware). +- If the GPS is detected but does not work, attempt the process outlined in [allocating node uavcan ID](https://docs.cubepilot.org/here-2/here-2-can-mode-instruction). ::: diff --git a/docs/ko/gps_compass/index.md b/docs/ko/gps_compass/index.md index 93814a2be62..2c3fae95d55 100644 --- a/docs/ko/gps_compass/index.md +++ b/docs/ko/gps_compass/index.md @@ -215,5 +215,6 @@ This behavior prevents large position errors that could occur when the yaw refer - [GPS driver](../modules/modules_driver.md#gps) - [PPS driver](../modules/modules_driver.md#pps-capture) - [DroneCAN Example](../dronecan/index.md) + - [u-blox Diagnostics with u-center](../gps_compass/u-center.md) - 나침반 - [Driver source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/magnetometer) (Compasses) diff --git a/docs/ko/gps_compass/rtk_gps.md b/docs/ko/gps_compass/rtk_gps.md index d4cee1fe9b7..744bce27ca7 100644 --- a/docs/ko/gps_compass/rtk_gps.md +++ b/docs/ko/gps_compass/rtk_gps.md @@ -235,4 +235,5 @@ See the [Using PX4's Navigation Filter (EKF2) > GPS](../advanced_config/tuning_t ## 추가 정보 - [RTK-GPS (PX4-Integration)](../advanced/rtk_gps.md): Developer information about integrating RTK-GPS support into PX4. +- [u-blox Diagnostics with u-center](../gps_compass/u-center.md): bench-check RTCM reception and fix status on a u-blox rover/base. - [Real Time Kinematic](https://en.wikipedia.org/wiki/Real_Time_Kinematic) (Wikipedia) diff --git a/docs/ko/gps_compass/u-blox_f9p_heading.md b/docs/ko/gps_compass/u-blox_f9p_heading.md index 980f0c05224..94ed4ef8096 100644 --- a/docs/ko/gps_compass/u-blox_f9p_heading.md +++ b/docs/ko/gps_compass/u-blox_f9p_heading.md @@ -58,4 +58,5 @@ If using RTK with a fixed base station the secondary GPS will show the RTK state ## 추가 정보 - [ZED-F9P Moving base applications (Application note)](https://content.u-blox.com/sites/default/files/documents/ZED-F9P-MovingBase_AppNote_UBX-19009093.pdf) - General setup/instructions. +- [u-blox Diagnostics with u-center](../gps_compass/u-center.md) - UART2 diagnostic mode (not available with heading/moving-base modes, which already use UART2 for RTCM). - [RTK GPS > GPS as Yaw/Heading Source](../gps_compass/rtk_gps.md#configuring-gps-as-yaw-heading-source) diff --git a/docs/ko/gps_compass/u-center.md b/docs/ko/gps_compass/u-center.md new file mode 100644 index 00000000000..edfd9e7660f --- /dev/null +++ b/docs/ko/gps_compass/u-center.md @@ -0,0 +1,54 @@ +# u-blox Diagnostics with u-center + + + +[u-center](https://www.u-blox.com/en/product/u-center) is u-blox's desktop tool for monitoring a receiver's live satellite, signal, and position data, and for reading and writing its configuration. + +Setting [GPS_UBX_MODE](#GPS_UBX_MODE) to `7` configures a u-blox receiver's `UART2` as a UBX diagnostic port for [u-center](https://www.u-blox.com/en/product/u-center), while the receiver continues to serve the autopilot on `UART1` (as usual). +This is useful for diagnosing poor fixes, interference, or RTK issues without disconnecting the autopilot. + +:::info +Heading and static-base-on-UART2 setups cannot use this feature. +For more information see [Constraints](#constraints) below. +::: + +## 배선 + +Connect the adapter's RX to the receiver's `UART2` TX, its TX to `UART2` RX, and share ground. +u-blox UART pins are 3.3 V. + +## PX4 설정 + +The parameters to set: + +| Parameter | 설정 | +| ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | +| [GPS_UBX_MODE](../advanced_config/parameter_reference.md#GPS_UBX_MODE) | `u-center on UART2` (7) | +| [GPS_UBX_BAUD2](../advanced_config/parameter_reference.md#GPS_UBX_BAUD2) | UART2 baudrate, must match the USB-serial adapter (default 230400) | + +Both parameters take effect after a reboot. + +## Messages Enabled on UART2 + +The following messages are enabled when `GPS_UBX_MODE` is set to `7`: + +| 메시지 | 주파수 | +| -------------------------------------------- | ----------------------- | +| `NAV-PVT`, `NAV-DOP`, `NAV-STATUS`, `MON-RF` | Every navigation epoch | +| `NAV-HPPOSLLH` | Every epoch, except M9 | +| `RXM-RTCM` | Every epoch, M9 and F9P | +| `NAV-SAT` | Every 10th epoch | + +The set runs around 300 bytes per navigation epoch (GPS update cycle), roughly triple that on the epoch carrying `NAV-SAT`. + +The default `UART2` baud rate (230400) covers the 25 Hz maximum; 115200 is the practical floor at the 10 Hz default rate. +Below that, the `NAV-SAT` epoch saturates the link, and a u-blox receiver drops messages on a congested port rather than throttling: the result is gaps in u-center. + +## 제약 조건 + +- UBX input is enabled on `UART2`, so anything connected there can reconfigure the receiver. + Use this on the bench, not in flight. +- The driver writes to the receiver's RAM configuration layer on every boot. + Changes made from u-center to the RAM layer are lost at the next power cycle; changes written to BBR or flash persist and will fight the driver. +- `GPS_UBX_MODE` 1, 2 and 5 use `UART2` for RTCM, so heading and static-base-on-UART2 setups cannot use mode 7. +- The mode is skipped with a warning on M10 and F10 receivers, and on receivers older than u-blox protocol version 27. diff --git a/docs/ko/hardware/dev_kit_program.md b/docs/ko/hardware/dev_kit_program.md index 9fd9d136351..bbe76b50497 100644 --- a/docs/ko/hardware/dev_kit_program.md +++ b/docs/ko/hardware/dev_kit_program.md @@ -20,7 +20,7 @@ A kit qualifies when it meets all five requirements: 4. A guide, a focused tutorial, and a reference sheet included with the kit 5. Third-party build quality verification -The reference sheet must ship printed, in the box: pinouts, connectors, and specs at a glance, with no screen required ([example: ModalAI VOXL 2 reference sheet](https://docs.modalai.com/voxl2-d0014)). +The reference sheet must ship printed, in the box: pinouts, connectors, and specs at a glance, with no screen required ([example: ModalAI VOXL 2 reference sheet](https://docs.modalai.com/voxl2-d0014/)). The guide and tutorial may ship as QR-code links. ## What Qualifying Looks Like in Practice diff --git a/docs/ko/modules/modules_command.md b/docs/ko/modules/modules_command.md index 2c4109499eb..f307426e196 100644 --- a/docs/ko/modules/modules_command.md +++ b/docs/ko/modules/modules_command.md @@ -727,4 +727,9 @@ ver [arguments...] hwbasecmp Compare hardware base (returns 0 on match) [] Hardware type to compare against (eg. V2). An OR comparison is used if multiple are specified + + hwpopcmp Compare HW population option (returns 0 on match) + [] Hex population option value(s) to compare against (eg. + 06, cafe, ffff). An OR comparison is used if multiple are + specified ``` diff --git a/docs/ko/modules/modules_driver.md b/docs/ko/modules/modules_driver.md index 63d8eef021c..167990793ca 100644 --- a/docs/ko/modules/modules_driver.md +++ b/docs/ko/modules/modules_driver.md @@ -572,7 +572,7 @@ ina228 [arguments...] [-a ] I2C address default: 69 [-k] if initialization (probing) fails, keep retrying periodically - [-t ] battery index for calibration values (1 or 3) + [-t ] battery index for calibration values (1-3) default: 1 stop diff --git a/docs/ko/modules/modules_driver_airspeed_sensor.md b/docs/ko/modules/modules_driver_airspeed_sensor.md index 68738a4053e..8aaf44cc637 100644 --- a/docs/ko/modules/modules_driver_airspeed_sensor.md +++ b/docs/ko/modules/modules_driver_airspeed_sensor.md @@ -59,6 +59,37 @@ auav [arguments...] status print status info ``` +## dlvr + +Source: [drivers/differential_pressure/dlvr](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure/dlvr) + +### 설명 + +I2C driver for _Amphenol All Sensors_ Digital Low Voltage R-Series (DLVR) pressure sensors +(continuous-sampling variants only). + +The driver is enabled for specific sensor-variants using the parameter "SENS_EN_DLVR". + +### Usage {#dlvr_usage} + +``` +dlvr [arguments...] + Commands: + start + [-I] Internal I2C bus(es) + [-X] External I2C bus(es) + [-b ] board-specific bus (default=all) (external SPI: n-th bus + (default=1)) + [-f ] bus frequency in kHz + [-q] quiet startup (no message if no device found) + [-a ] I2C address + default: 40 + + stop + + status print status info +``` + ## ets_airspeed Source: [drivers/differential_pressure/ets](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure/ets) diff --git a/docs/ko/modules/modules_driver_ins.md b/docs/ko/modules/modules_driver_ins.md index beb6dbfaa4c..d65de7afcde 100644 --- a/docs/ko/modules/modules_driver_ins.md +++ b/docs/ko/modules/modules_driver_ins.md @@ -9,7 +9,7 @@ Source: [drivers/ins/microstrain](https://github.com/PX4/PX4-Autopilot/tree/main MicroStrain by HBK Inertial Sensor Driver. Currently supports the following sensors: --[CV7-AR](https://www.hbkworld.com/en/products/transducers/inertial-sensors/vertical-reference-units--vru-/3dm-cv7-ar) -[CV7-AHRS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/attitude-and-heading/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-gnss-ins) +-[CV7-AR](https://www.hbkworld.com/en/products/transducers/inertial-sensors/vertical-reference/3dm-cv7-ar) -[CV7-AHRS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/attitude-and-heading/3dm-cv7-ahrs) -[CV7-INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-ins) -[CV7-GNSS/INS](https://www.hbkworld.com/en/products/transducers/inertial-sensors/navigation/3dm-cv7-gnss-ins) This driver is not included in the firmware by default. Include the module in firmware by setting the diff --git a/docs/ko/modules/modules_driver_magnetometer.md b/docs/ko/modules/modules_driver_magnetometer.md index 888b94eb83a..a160f29392d 100644 --- a/docs/ko/modules/modules_driver_magnetometer.md +++ b/docs/ko/modules/modules_driver_magnetometer.md @@ -202,7 +202,7 @@ iis2mdc [arguments...] [-f ] bus frequency in kHz [-q] quiet startup (no message if no device found) [-a ] I2C address - default: 48 + default: 30 stop diff --git a/docs/ko/msg_docs/FailureInjection.md b/docs/ko/msg_docs/FailureInjection.md index 83ed53430d6..d7f33d21f40 100644 --- a/docs/ko/msg_docs/FailureInjection.md +++ b/docs/ko/msg_docs/FailureInjection.md @@ -29,24 +29,25 @@ vehicle_command cannot propagate to the consumers applying the failures. Used in field(s): [unit](#fld_unit) -| 명칭 | 형식 | Value | 설명 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | -- | -| FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | | -| FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | | -| FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | | -| FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | | -| FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | | -| FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | | -| FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | | -| FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | | -| FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | | -| FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | | -| FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | | -| FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | | -| FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | | -| FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | | -| FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | | -| FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | | +| 명칭 | 형식 | Value | 설명 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | -- | +| FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | | +| FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | | +| FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | | +| FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | | +| FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | | +| FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | | +| FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | | +| FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | | +| FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | | +| FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | | +| FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | | +| FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | | +| FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | | +| FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | | +| FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | | +| FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | | +| FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE | `uint8` | 107 | | ### FAILURE_TYPE {#FAILURE_TYPE} @@ -62,6 +63,7 @@ Used in field(s): [failure_type](#fld_failure_type) | FAILURE_TYPE_SLOW | `uint8` | 5 | | | FAILURE_TYPE_DELAYED | `uint8` | 6 | | | FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | | +| FAILURE_TYPE_DRIFT | `uint8` | 8 | | ## Constants @@ -109,6 +111,7 @@ uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103 uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104 uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105 uint8 FAILURE_UNIT_SYSTEM_ESC = 106 +uint8 FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE = 107 uint16[4] instance_mask # Bit i targets instance (i+1); 0xFFFF = all instances @@ -123,6 +126,7 @@ uint8 FAILURE_TYPE_WRONG = 4 uint8 FAILURE_TYPE_SLOW = 5 uint8 FAILURE_TYPE_DELAYED = 6 uint8 FAILURE_TYPE_INTERMITTENT = 7 +uint8 FAILURE_TYPE_DRIFT = 8 ``` ::: diff --git a/docs/ko/msg_docs/FuelTankStatus.md b/docs/ko/msg_docs/FuelTankStatus.md index 3f17e7f3913..5f1399968f9 100644 --- a/docs/ko/msg_docs/FuelTankStatus.md +++ b/docs/ko/msg_docs/FuelTankStatus.md @@ -24,6 +24,7 @@ pageClass: is-wide-page | 명칭 | 형식 | Value | 설명 | | ------------------------------------------------------------------------------------------------------------------------ | ------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| MAX_INSTANCES | `uint8` | 3 | | | MAV_FUEL_TYPE_UNKNOWN | `uint8` | 0 | fuel type not specified. Fuel levels are normalized (i.e., maximum is 1, and other levels are relative to 1). | | MAV_FUEL_TYPE_LIQUID | `uint8` | 1 | represents generic liquid fuels, such as gasoline or diesel. Fuel levels are measured in millilitres (ml), and flow rates in millilitres per second (ml/s). | | MAV_FUEL_TYPE_GAS | `uint8` | 2 | represents a gas fuel, such as hydrogen, methane, or propane. Fuel levels are in kilo-Pascal (kPa), and flow rates are in milliliters per second (ml/s). | @@ -36,6 +37,8 @@ pageClass: is-wide-page Click here to see original file ```c +uint8 MAX_INSTANCES = 3 + uint64 timestamp # time since system start (microseconds) float32 maximum_fuel_capacity # maximum fuel capacity. Must always be provided, either from the driver or a parameter diff --git a/docs/ko/msg_docs/TecsStatus.md b/docs/ko/msg_docs/TecsStatus.md index 04908283fb1..b13b4bf3522 100644 --- a/docs/ko/msg_docs/TecsStatus.md +++ b/docs/ko/msg_docs/TecsStatus.md @@ -35,6 +35,7 @@ pageClass: is-wide-page | throttle_trim | `float32` | | | estimated throttle value [0,1] required to fly level at equivalent_airspeed_sp in the current atmospheric conditions | | underspeed_ratio | `float32` | | | 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. | | fast_descend_ratio | `float32` | | | value indicating if fast descend mode is enabled with ramp up and ramp down [0-1] | +| weight_ratio | `float32` | | | Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled. | ## Source Message @@ -75,6 +76,8 @@ float32 throttle_trim # estimated throttle value [0,1] required to fly level a float32 underspeed_ratio # 0: no underspeed, 1: maximal underspeed. Controller takes measures to avoid stall proportional to ratio if >0. float32 fast_descend_ratio # value indicating if fast descend mode is enabled with ramp up and ramp down [0-1] + +float32 weight_ratio # [-] Ratio of estimated vehicle weight to WEIGHT_BASE. Accounts for burned fuel if fuel-based weight compensation is enabled. ``` ::: diff --git a/docs/ko/msg_docs/VehicleCommand.md b/docs/ko/msg_docs/VehicleCommand.md index 894a3695061..d67cc697763 100644 --- a/docs/ko/msg_docs/VehicleCommand.md +++ b/docs/ko/msg_docs/VehicleCommand.md @@ -1622,71 +1622,72 @@ Change heading/course. param1: heading type (0=course-over-ground, 1=heading). p ## Constants -| 명칭 | 형식 | Value | 설명 | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| MESSAGE_VERSION | `uint32` | 0 | | -| PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION | `uint16` | 3 | Param value for VEHICLE_CMD_PREFLIGHT_CALIBRATION to start temperature calibration. | -| FUSION_SOURCE_GPS | `uint8` | 0 | GNSS (EKF2_GPS{i}\_CTRL, use instance param) | -| FUSION_SOURCE_OF | `uint8` | 1 | Optical Flow (EKF2_OF_CTRL) | -| FUSION_SOURCE_EV | `uint8` | 2 | External Vision (EKF2_EV_CTRL) | -| FUSION_SOURCE_AGP | `uint8` | 3 | Auxiliary Global Position (EKF2_AGP{i}\_CTRL, use instance param) | -| FUSION_SOURCE_BARO | `uint8` | 4 | Barometer (EKF2_BARO_CTRL) | -| FUSION_SOURCE_RNG | `uint8` | 5 | Range Finder (EKF2_RNG_CTRL) | -| FUSION_SOURCE_MAG | `uint8` | 6 | Magnetometer (EKF2_MAG_TYPE) | -| FUSION_SOURCE_ASPD | `uint8` | 7 | Airspeed (EKF2_ARSP_THR) | -| FUSION_SOURCE_RNGBCN | `uint8` | 8 | Ranging Beacon | -| VEHICLE_MOUNT_MODE_RETRACT | `uint8` | 0 | Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization. | -| VEHICLE_MOUNT_MODE_NEUTRAL | `uint8` | 1 | Load and keep neutral position (Roll,Pitch,Yaw) from permanent memory. | -| VEHICLE_MOUNT_MODE_MAVLINK_TARGETING | `uint8` | 2 | Load neutral position and start MAVLink Roll,Pitch,Yaw control with stabilization. | -| VEHICLE_MOUNT_MODE_RC_TARGETING | `uint8` | 3 | Load neutral position and start RC Roll,Pitch,Yaw control with stabilization. | -| VEHICLE_MOUNT_MODE_GPS_POINT | `uint8` | 4 | Load neutral position and start to point to Lat,Lon,Alt. | -| VEHICLE_MOUNT_MODE_ENUM_END | `uint8` | 5 | | -| ACTUATOR_CONFIGURATION_NONE | `uint8` | 0 | Do nothing. | -| ACTUATOR_CONFIGURATION_BEEP | `uint8` | 1 | Command the actuator to beep now. | -| ACTUATOR_CONFIGURATION_3D_MODE_ON | `uint8` | 2 | Permanently set the actuator (ESC) to 3D mode (reversible thrust). | -| ACTUATOR_CONFIGURATION_3D_MODE_OFF | `uint8` | 3 | Permanently set the actuator (ESC) to non 3D mode (non-reversible thrust). | -| ACTUATOR_CONFIGURATION_SPIN_DIRECTION1 | `uint8` | 4 | Permanently set the actuator (ESC) to spin direction 1 (which can be clockwise or counter-clockwise). | -| ACTUATOR_CONFIGURATION_SPIN_DIRECTION2 | `uint8` | 5 | Permanently set the actuator (ESC) to spin direction 2 (opposite of direction 1). | -| PARACHUTE_ACTION_DISABLE | `uint8` | 0 | | -| PARACHUTE_ACTION_ENABLE | `uint8` | 1 | | -| PARACHUTE_ACTION_RELEASE | `uint8` | 2 | | -| FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | | -| FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | | -| FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | | -| FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | | -| FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | | -| FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | | -| FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | | -| FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | | -| FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | | -| FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | | -| FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | | -| FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | | -| FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | | -| FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | | -| FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | | -| FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | | -| FAILURE_TYPE_OK | `uint8` | 0 | | -| FAILURE_TYPE_OFF | `uint8` | 1 | | -| FAILURE_TYPE_STUCK | `uint8` | 2 | | -| FAILURE_TYPE_GARBAGE | `uint8` | 3 | | -| FAILURE_TYPE_WRONG | `uint8` | 4 | | -| FAILURE_TYPE_SLOW | `uint8` | 5 | | -| FAILURE_TYPE_DELAYED | `uint8` | 6 | | -| FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | | -| RC_TYPE_SPEKTRUM | `uint8` | 0 | | -| RC_TYPE_CRSF | `uint8` | 1 | | -| RC_SUB_TYPE_SPEKTRUM_DSM2 | `uint8` | 0 | | -| RC_SUB_TYPE_SPEKTRUM_DSMX | `uint8` | 1 | | -| RC_SUB_TYPE_SPEKTRUM_DSMX8 | `uint8` | 2 | | -| ARMING_ACTION_DISARM | `int8` | 0 | | -| ARMING_ACTION_ARM | `int8` | 1 | | -| GRIPPER_ACTION_RELEASE | `uint8` | 0 | | -| GRIPPER_ACTION_GRAB | `uint8` | 1 | | -| SAFETY_OFF | `uint8` | 0 | | -| SAFETY_ON | `uint8` | 1 | | -| ORB_QUEUE_LENGTH | `uint8` | 8 | | -| COMPONENT_MODE_EXECUTOR_START | `uint16` | 1000 | | +| 명칭 | 형식 | Value | 설명 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| MESSAGE_VERSION | `uint32` | 0 | | +| PREFLIGHT_CALIBRATION_TEMPERATURE_CALIBRATION | `uint16` | 3 | Param value for VEHICLE_CMD_PREFLIGHT_CALIBRATION to start temperature calibration. | +| FUSION_SOURCE_GPS | `uint8` | 0 | GNSS (EKF2_GPS{i}\_CTRL, use instance param) | +| FUSION_SOURCE_OF | `uint8` | 1 | Optical Flow (EKF2_OF_CTRL) | +| FUSION_SOURCE_EV | `uint8` | 2 | External Vision (EKF2_EV_CTRL) | +| FUSION_SOURCE_AGP | `uint8` | 3 | Auxiliary Global Position (EKF2_AGP{i}\_CTRL, use instance param) | +| FUSION_SOURCE_BARO | `uint8` | 4 | Barometer (EKF2_BARO_CTRL) | +| FUSION_SOURCE_RNG | `uint8` | 5 | Range Finder (EKF2_RNG_CTRL) | +| FUSION_SOURCE_MAG | `uint8` | 6 | Magnetometer (EKF2_MAG_TYPE) | +| FUSION_SOURCE_ASPD | `uint8` | 7 | Airspeed (EKF2_ARSP_THR) | +| FUSION_SOURCE_RNGBCN | `uint8` | 8 | Ranging Beacon | +| VEHICLE_MOUNT_MODE_RETRACT | `uint8` | 0 | Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization. | +| VEHICLE_MOUNT_MODE_NEUTRAL | `uint8` | 1 | Load and keep neutral position (Roll,Pitch,Yaw) from permanent memory. | +| VEHICLE_MOUNT_MODE_MAVLINK_TARGETING | `uint8` | 2 | Load neutral position and start MAVLink Roll,Pitch,Yaw control with stabilization. | +| VEHICLE_MOUNT_MODE_RC_TARGETING | `uint8` | 3 | Load neutral position and start RC Roll,Pitch,Yaw control with stabilization. | +| VEHICLE_MOUNT_MODE_GPS_POINT | `uint8` | 4 | Load neutral position and start to point to Lat,Lon,Alt. | +| VEHICLE_MOUNT_MODE_ENUM_END | `uint8` | 5 | | +| ACTUATOR_CONFIGURATION_NONE | `uint8` | 0 | Do nothing. | +| ACTUATOR_CONFIGURATION_BEEP | `uint8` | 1 | Command the actuator to beep now. | +| ACTUATOR_CONFIGURATION_3D_MODE_ON | `uint8` | 2 | Permanently set the actuator (ESC) to 3D mode (reversible thrust). | +| ACTUATOR_CONFIGURATION_3D_MODE_OFF | `uint8` | 3 | Permanently set the actuator (ESC) to non 3D mode (non-reversible thrust). | +| ACTUATOR_CONFIGURATION_SPIN_DIRECTION1 | `uint8` | 4 | Permanently set the actuator (ESC) to spin direction 1 (which can be clockwise or counter-clockwise). | +| ACTUATOR_CONFIGURATION_SPIN_DIRECTION2 | `uint8` | 5 | Permanently set the actuator (ESC) to spin direction 2 (opposite of direction 1). | +| PARACHUTE_ACTION_DISABLE | `uint8` | 0 | | +| PARACHUTE_ACTION_ENABLE | `uint8` | 1 | | +| PARACHUTE_ACTION_RELEASE | `uint8` | 2 | | +| FAILURE_UNIT_SENSOR_GYRO | `uint8` | 0 | | +| FAILURE_UNIT_SENSOR_ACCEL | `uint8` | 1 | | +| FAILURE_UNIT_SENSOR_MAG | `uint8` | 2 | | +| FAILURE_UNIT_SENSOR_BARO | `uint8` | 3 | | +| FAILURE_UNIT_SENSOR_GPS | `uint8` | 4 | | +| FAILURE_UNIT_SENSOR_OPTICAL_FLOW | `uint8` | 5 | | +| FAILURE_UNIT_SENSOR_VIO | `uint8` | 6 | | +| FAILURE_UNIT_SENSOR_DISTANCE_SENSOR | `uint8` | 7 | | +| FAILURE_UNIT_SENSOR_AIRSPEED | `uint8` | 8 | | +| FAILURE_UNIT_SYSTEM_BATTERY | `uint8` | 100 | | +| FAILURE_UNIT_SYSTEM_MOTOR | `uint8` | 101 | | +| FAILURE_UNIT_SYSTEM_SERVO | `uint8` | 102 | | +| FAILURE_UNIT_SYSTEM_AVOIDANCE | `uint8` | 103 | | +| FAILURE_UNIT_SYSTEM_RC_SIGNAL | `uint8` | 104 | | +| FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL | `uint8` | 105 | | +| FAILURE_UNIT_SYSTEM_ESC | `uint8` | 106 | | +| FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE | `uint8` | 107 | | +| FAILURE_TYPE_OK | `uint8` | 0 | | +| FAILURE_TYPE_OFF | `uint8` | 1 | | +| FAILURE_TYPE_STUCK | `uint8` | 2 | | +| FAILURE_TYPE_GARBAGE | `uint8` | 3 | | +| FAILURE_TYPE_WRONG | `uint8` | 4 | | +| FAILURE_TYPE_SLOW | `uint8` | 5 | | +| FAILURE_TYPE_DELAYED | `uint8` | 6 | | +| FAILURE_TYPE_INTERMITTENT | `uint8` | 7 | | +| RC_TYPE_SPEKTRUM | `uint8` | 0 | | +| RC_TYPE_CRSF | `uint8` | 1 | | +| RC_SUB_TYPE_SPEKTRUM_DSM2 | `uint8` | 0 | | +| RC_SUB_TYPE_SPEKTRUM_DSMX | `uint8` | 1 | | +| RC_SUB_TYPE_SPEKTRUM_DSMX8 | `uint8` | 2 | | +| ARMING_ACTION_DISARM | `int8` | 0 | | +| ARMING_ACTION_ARM | `int8` | 1 | | +| GRIPPER_ACTION_RELEASE | `uint8` | 0 | | +| GRIPPER_ACTION_GRAB | `uint8` | 1 | | +| SAFETY_OFF | `uint8` | 0 | | +| SAFETY_ON | `uint8` | 1 | | +| ORB_QUEUE_LENGTH | `uint8` | 8 | | +| COMPONENT_MODE_EXECUTOR_START | `uint16` | 1000 | | ## Source Message @@ -1871,6 +1872,7 @@ uint8 FAILURE_UNIT_SYSTEM_AVOIDANCE = 103 uint8 FAILURE_UNIT_SYSTEM_RC_SIGNAL = 104 uint8 FAILURE_UNIT_SYSTEM_MAVLINK_SIGNAL = 105 uint8 FAILURE_UNIT_SYSTEM_ESC = 106 +uint8 FAILURE_UNIT_SYSTEM_TRAFFIC_AVOIDANCE = 107 uint8 FAILURE_TYPE_OK = 0 uint8 FAILURE_TYPE_OFF = 1 diff --git a/docs/ko/peripherals/gripper_epm.md b/docs/ko/peripherals/gripper_epm.md index 2c2fe626bbf..e2e0a69514e 100644 --- a/docs/ko/peripherals/gripper_epm.md +++ b/docs/ko/peripherals/gripper_epm.md @@ -125,6 +125,6 @@ If FluxGrip does not respond: ## See Also - [FluxGrip: Integration with PX4](https://forum.zubax.com/t/fluxgrip-integration-with-px4/2863) (Zubax Forum) -- [FluxGrip Quickstart Guide](https://forum.zubax.com/t/fluxgrip-quickstart-guide/2335) (Zubax Forum) +- [FluxGrip Quickstart Guide](https://forum.zubax.com/t/fluxgrip-quickstart-guide-v1-1/2864) (Zubax Forum) - [DroneCAN](../dronecan/index.md) - [Grippers](gripper.md) diff --git a/docs/ko/peripherals/osd.md b/docs/ko/peripherals/osd.md index d0dd696085a..57cba16398d 100644 --- a/docs/ko/peripherals/osd.md +++ b/docs/ko/peripherals/osd.md @@ -27,10 +27,11 @@ PX4 currently sends a subset of MSP messages. Reliably-working display items include: - Craft name and flight mode / arming state -- Battery voltage, current draw, mAh consumed, average cell voltage +- Average cell voltage, current draw, mAh consumed - GPS latitude, longitude, satellite count, ground speed -- Home distance and direction +- Home distance - Altitude (from GNSS / baro) +- Roll / pitch angle - RSSI - Crosshairs toggle @@ -63,7 +64,8 @@ Then rebuild and flash. 3. Reboot. 4. Tune the display via the [`OSD_*` parameters](../advanced_config/parameter_reference.md#osd): - [`OSD_SYMBOLS`](../advanced_config/parameter_reference.md#OSD_SYMBOLS) — bitmask selecting which items appear. - - [`OSD_CH_HEIGHT`](../advanced_config/parameter_reference.md#OSD_CH_HEIGHT) — vertical position of the crosshairs. + - [`OSD_CH_POS_VER`](../advanced_config/parameter_reference.md#OSD_CH_POS_VER) — vertical position of the crosshairs. + - [`OSD_CH_POS_HOR`](../advanced_config/parameter_reference.md#OSD_CH_POS_HOR) — horizontal position of the crosshairs. - [`OSD_LOG_LEVEL`](../advanced_config/parameter_reference.md#OSD_LOG_LEVEL) — minimum severity for on-screen warnings. - [`OSD_SCROLL_RATE`](../advanced_config/parameter_reference.md#OSD_SCROLL_RATE) / [`OSD_DWELL_TIME`](../advanced_config/parameter_reference.md#OSD_DWELL_TIME) — scrolling of long messages. - [`OSD_RC_STICK`](../advanced_config/parameter_reference.md#OSD_RC_STICK) — forward RC sticks to the VTX when disarmed, so you can navigate the VTX menu. diff --git a/docs/ko/peripherals/remote_id.md b/docs/ko/peripherals/remote_id.md index c2eda8b4458..7111fc02f67 100644 --- a/docs/ko/peripherals/remote_id.md +++ b/docs/ko/peripherals/remote_id.md @@ -22,12 +22,12 @@ Remote ID hardware can only be connected via DroneCAN on `main` branch builds (b PX4 integrates with Remote ID hardware that supports: -- [Open Drone ID](https://mavlink.io/en/services/opendroneid.html) MAVLink protocol -- Remote ID over CAN +- [Open Drone ID](https://mavlink.io/en/services/opendroneid.html) MAVLink protocol +- Remote ID over CAN It has been tested with the following devices: -- [Cube ID](https://docs.cubepilot.org/user-guides/cube-id/cube-id) (CubePilot) +- [Cube ID](https://docs.cubepilot.org/cube-id/cube-id) (CubePilot) - [Db201](https://dronescout.co/dronebeacon-mavlink-remote-id-transponder/) (BlueMark) - Tested via serial port. Not tested via CAN port. - [Db202mav](https://dronescout.co/dronebeacon-mavlink-remote-id-transponder/) (BlueMark) - Less expensive variant without CAN port. - [Holybro RemoteID Module](https://holybro.com/products/remote-id) (Holybro) @@ -41,7 +41,7 @@ Most commonly they are connected directly to the `TELEM2` port (if it is not bei ### Cube ID -[Cube ID](https://docs.cubepilot.org/user-guides/cube-id/cube-id) can be connected using a serial or CAN port. +[Cube ID](https://docs.cubepilot.org/cube-id/cube-id) can be connected using a serial or CAN port. It comes with 6-pin and 4-pin JST-GH 1.25mm cables that can be connected directly to the `TELEM` serial port and `CAN` ports, respectively, on most recent Pixhawk flight controllers. @@ -75,7 +75,7 @@ The TX and RX on the flight controller must be connected to the RX and TX on the The Cube ID uses proprietary firmware (not [ArduRemoteID](https://github.com/ArduPilot/ArduRemoteID) like some other remote id beacons). -For firmware update instructions see [Cube ID > Updating](https://docs.cubepilot.org/user-guides/cube-id/cube-id#updating). +For firmware update instructions see [Cube ID > Updating](https://docs.cubepilot.org/cube-id/cube-id#updating). ### BlueMark Db201/Db202mav diff --git a/docs/ko/releases/index.md b/docs/ko/releases/index.md index 01a520eb62a..d80dad64f32 100644 --- a/docs/ko/releases/index.md +++ b/docs/ko/releases/index.md @@ -14,7 +14,7 @@ const { site } = useData(); PX4 릴리스 노트는 각 릴리스의 변경 사항들을 설명합니다. -- [main](../releases/main.md) (changes planned for v1.19 or later) +- [main](../releases/main.md) (changes planned for v2.0 or later) - [v1.18](../releases/1.18.md) (changes in v1.18, since v1.17) - [v1.17](../releases/1.17.md) - [v1.16](../releases/1.16.md) diff --git a/docs/ko/releases/main.md b/docs/ko/releases/main.md index c4bf9b1ea3e..974d00196b2 100644 --- a/docs/ko/releases/main.md +++ b/docs/ko/releases/main.md @@ -17,7 +17,7 @@ This contains changes to the PX4 `main` branch that are not included in the next :::warning PX4 v1.18 is in beta testing. -Update these notes with features that are going to be in `main` (PX4 v1.19 or later) but not the PX4 v1.18 release. +Update these notes with features that are going to be in `main` (PX4 v2.0 or later) but not the PX4 v1.18 release. ::: ## Read Before Upgrading @@ -54,6 +54,11 @@ Please continue reading for [upgrade instructions](#upgrade-guide). - [Geofence Aware Return mode](../flight_modes/return.md#geofence_awareness). ([PX4-Autopilot#27145: feat(navigator): Geofence Aware RTL](https://github.com/PX4/PX4-Autopilot/pull/27145), [PX4-Autopilot#28001: docs(navigator): [geofence] added some more warnings about limitations](https://github.com/PX4/PX4-Autopilot/pull/28001)). - [Flight termination](../advanced_config/flight_termination.md) can now be used instead of a Descent mode as a fallback failsafe mode, allowing safer landing for unpiloted vehicles that carry a parachute. See [Battery level failsafe](../config/safety.md#battery-level-failsafe) ([COM_LOW_BAT_ACT](../advanced_config/parameter_reference.md#COM_LOW_BAT_ACT)) and [Position Loss Failsafe Action](../config/safety.md#position-loss-failsafe-action) (new [COM_POS_FS_ACT](../advanced_config/parameter_reference.md#COM_POS_FS_ACT)). ([PX4-Autopilot#28064: feat(commander): add terminate options for critical battery and lost position failsafes](https://github.com/PX4/PX4-Autopilot/pull/28064)). +- [Failure injection](../debug/failure_injection.md) ( [SYS_FAILURE_EN](../advanced_config/parameter_reference.md#SYS_FAILURE_EN)) has been significantly extended. (PX4-Autopilot#27572, PX4-Autopilot#27832, PX4-Autopilot#27950) + - Now applied on real hardware, not just simulators (injection hooks live in the shared sensor drivers). + - Command handling is centralized behind a dedicated failure-injection manager module. + - Multiple sensor instances can be failed simultaneously via a bitmask, and failures can be triggered from an RC switch. + - Changed default behaviour of injected WRONG failure for Batteries, to publish a wrong level, and not stop publishing - [Motor failure recovery](../config/motor_failure_recovery.md) for hexarotors: on a single motor failure the control allocator removes the failed motor and additionally stops ([CA_FAILURE_MODE](../advanced_config/parameter_reference.md#CA_FAILURE_MODE) = `1`) or reverses (`2`) the motor opposite it to recover the lost yaw authority. Mode `2` requires a reverse-capable ESC and models the reverse thrust of a forward propeller with the new [CA_REV_THR_FRAC](../advanced_config/parameter_reference.md#CA_REV_THR_FRAC) (default `0.4`). Reversible motor outputs on DroneCAN are now sent as signed `RawCommand` values (negative is reverse). ([PX4-Autopilot#28078](https://github.com/PX4/PX4-Autopilot/pull/28078)) - Added `RTL_TYPE=6` for battery-aware home priority return ([PX4-Autopilot#26968](https://github.com/PX4/PX4-Autopilot/pull/26968)). Returns to home if the estimated flight time to home is within the remaining battery time; otherwise returns to the closest rally point. @@ -65,7 +70,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide). ### 센서 -- TBD +- Enable [u-blox Diagnostics with u-center](../gps_compass/u-center.md) while the vehicle's GPS runs as usual. ([PX4-Autopilot#28280](https://github.com/PX4/PX4-Autopilot/pull/28280)). ### 시뮬레이션 diff --git a/docs/ko/ros/mavros_offboard_cpp.md b/docs/ko/ros/mavros_offboard_cpp.md index f4c056630e4..1c60a4e4aff 100644 --- a/docs/ko/ros/mavros_offboard_cpp.md +++ b/docs/ko/ros/mavros_offboard_cpp.md @@ -10,7 +10,7 @@ If you are operating on a real vehicle be sure to have a way of gaining back man :::tip This example uses C++. -A very similar example for Python can be found in [ROS/MAVROS Offboard Example (Python)](../ros/mavros_offboard_python.md) (also see the examples in [integrationtests/python_src/px4_it/mavros](https://github.com/PX4/PX4-Autopilot/tree/main/integrationtests/python_src/px4_it/mavros)). +A very similar example for Python can be found in [ROS/MAVROS Offboard Example (Python)](../ros/mavros_offboard_python.md). :::