mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-10-06 09:02:52 +08:00
docs(i18n): PX4 guide translations (Crowdin) - uk (#27811)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
co-authored by
Crowdin Bot
Crowdin Bot
parent
50161b1f09
commit
bf0d1013b2
+15
-13
@@ -3,6 +3,11 @@
|
||||
|
||||
- [Try PX4 (Simulation)](simulation/px4_simulation_quickstart.md)
|
||||
|
||||
- [Developer Kits](dev_kits/index.md)
|
||||
- [ModalAI Starling 2](complete_vehicles_mc/modalai_starling.md)
|
||||
- [DroneBlocks DEXI 5](complete_vehicles_mc/droneblocks_dexi.md)
|
||||
- [Holybro X500 v2](frames_multicopter/holybro_x500v2_pixhawk6c.md)
|
||||
|
||||
- [Мультикоптери](frames_multicopter/index.md)
|
||||
- [Функції](features_mc/index.md)
|
||||
- [Режим польоту](flight_modes_mc/index.md)
|
||||
@@ -39,7 +44,6 @@
|
||||
- [Static Pressure Buildup](advanced_config/static_pressure_buildup.md)
|
||||
- [Flying (Basics)](flying/basic_flying_mc.md)
|
||||
- [Complete Vehicles](complete_vehicles_mc/index.md)
|
||||
- [ModalAI Starling](complete_vehicles_mc/modalai_starling.md)
|
||||
- [PX4 Vision Kit](complete_vehicles_mc/px4_vision_kit.md)
|
||||
- [MindRacer BNF & RTF](complete_vehicles_mc/mindracer_BNF_RTF.md)
|
||||
- [MindRacer 210](complete_vehicles_mc/mindracer210.md)
|
||||
@@ -48,12 +52,6 @@
|
||||
- [Holybro Kopis 2](complete_vehicles_mc/holybro_kopis2.md)
|
||||
- [Amov F410 Drone](complete_vehicles_mc/amov_F410_drone.md)
|
||||
- [Набори](frames_multicopter/kits.md)
|
||||
- [X500 v2 (Pixhawk 6C)](frames_multicopter/holybro_x500v2_pixhawk6c.md)
|
||||
- [X500 v2 (Pixhawk 5X)](frames_multicopter/holybro_x500V2_pixhawk5x.md)
|
||||
- [X500 (Pixhawk 4)](frames_multicopter/holybro_x500_pixhawk4.md)
|
||||
- [S500 V2 (Pixhawk 4)](frames_multicopter/holybro_s500_v2_pixhawk4.md)
|
||||
- [Lumenier QAV-R 5" Racer (Pixracer)](frames_multicopter/qav_r_5_kiss_esc_racer.md)
|
||||
- [QAV250 (Pixhawk4 Mini) - Припинено](frames_multicopter/holybro_qav250_pixhawk4_mini.md)
|
||||
- [DIY Builds](frames_multicopter/diy_builds.md)
|
||||
- [Omnicopter](frames_multicopter/omnicopter.md)
|
||||
- [DJI F450 (CUAV v5+)](frames_multicopter/dji_f450_cuav_5plus.md)
|
||||
@@ -178,10 +176,6 @@
|
||||
- [CORVON 743v2](flight_controller/corvon_743v2.md)
|
||||
- [CORVON V5](flight_controller/corvon_v5.md)
|
||||
- [CUAV Nora](flight_controller/cuav_nora.md)
|
||||
- [CUAV V5+ (FMUv5)](flight_controller/cuav_v5_plus.md)
|
||||
- [Wiring Quickstart](assembly/quick_start_cuav_v5_plus.md)
|
||||
- [CUAV V5 nano (FMUv5)](flight_controller/cuav_v5_nano.md)
|
||||
- [Швидке підключення CUAV V5 nano](assembly/quick_start_cuav_v5_nano.md)
|
||||
- [CUAV X25 EVO](flight_controller/cuav_x25-evo.md)
|
||||
- [CUAV X25 EVO Wiring Quick Start](assembly/quick_start_cuav_x25_evo.md)
|
||||
- [CUAV X25 SUPER](flight_controller/cuav_x25-super.md)
|
||||
@@ -521,7 +515,9 @@
|
||||
- [Pre-built Packages](simulation/px4_sitl_prebuilt_packages.md)
|
||||
- [Апаратне забезпечення](hardware/index.md)
|
||||
- [Дизайн контролера польоту](hardware/reference_design.md)
|
||||
- [Manufacturer’s Board Support Guide](hardware/board_support_guide.md)
|
||||
- [Manufacturers](hardware/manufacturers.md)
|
||||
- [Manufacturer’s Board Support Guide](hardware/board_support_guide.md)
|
||||
- [Official PX4 Developer Kit Program](hardware/dev_kit_program.md)
|
||||
- [Flight Controller Porting Guide](hardware/porting_guide.md)
|
||||
- [PX4 Конфігурація плати (kconfig)](hardware/porting_guide_config.md)
|
||||
- [Посібник з портування NuttX](hardware/porting_guide_nuttx.md)
|
||||
@@ -584,6 +580,7 @@
|
||||
- [VtolVehicleStatus](msg_docs/VtolVehicleStatus.md)
|
||||
- [Wind](msg_docs/Wind.md)
|
||||
- [Historic (old) Versions](msg_docs/versioned_old_messages.md)
|
||||
- [ActuatorServosV0](msg_docs/ActuatorServosV0.md)
|
||||
- [AirspeedValidatedV0](msg_docs/AirspeedValidatedV0.md)
|
||||
- [ArmingCheckReplyV0](msg_docs/ArmingCheckReplyV0.md)
|
||||
- [ArmingCheckRequestV0](msg_docs/ArmingCheckRequestV0.md)
|
||||
@@ -655,6 +652,7 @@
|
||||
- [EstimatorStatusFlags](msg_docs/EstimatorStatusFlags.md)
|
||||
- [FailsafeFlags](msg_docs/FailsafeFlags.md)
|
||||
- [FailureDetectorStatus](msg_docs/FailureDetectorStatus.md)
|
||||
- [FailureInjection](msg_docs/FailureInjection.md)
|
||||
- [FiducialMarkerPosReport](msg_docs/FiducialMarkerPosReport.md)
|
||||
- [FiducialMarkerYawReport](msg_docs/FiducialMarkerYawReport.md)
|
||||
- [FigureEightStatus](msg_docs/FigureEightStatus.md)
|
||||
@@ -719,6 +717,7 @@
|
||||
- [OffboardControlMode](msg_docs/OffboardControlMode.md)
|
||||
- [OnboardComputerStatus](msg_docs/OnboardComputerStatus.md)
|
||||
- [OpenDroneIdArmStatus](msg_docs/OpenDroneIdArmStatus.md)
|
||||
- [OpenDroneIdBasicId](msg_docs/OpenDroneIdBasicId.md)
|
||||
- [OpenDroneIdOperatorId](msg_docs/OpenDroneIdOperatorId.md)
|
||||
- [OpenDroneIdSelfId](msg_docs/OpenDroneIdSelfId.md)
|
||||
- [OpenDroneIdSystem](msg_docs/OpenDroneIdSystem.md)
|
||||
@@ -935,11 +934,14 @@
|
||||
- [Test MC_08 - DSHOT ESC](test_cards/mc_08_dshot.md)
|
||||
- [Test MC_09 - VIO (Visual-Inertial Odometry)](test_cards/mc_09_vio.md)
|
||||
- [Test MC_10 - Optical Flow / GPS Mixed](test_cards/mc_10_optical_flow_gps_mixed.md)
|
||||
- [Test MC_11 - Companion Computer (ROS 2 External Mode)](test_cards/mc_11_companion_ros2_external_mode.md)
|
||||
- [Fixed Wing](test_and_ci/test_flights.md#fixed-wing)
|
||||
- [Test FW_01 - Manual Modes](test_cards/fw_01_manual_modes.md)
|
||||
- [Test FW_02 - Full Autonomous](test_cards/fw_02_full_autonomous.md)
|
||||
- [Hardware Bench Testing (px4bench)](test_and_ci/bench_testing.md)
|
||||
- [Модульні Тести](test_and_ci/unit_tests.md)
|
||||
- [Fuzz Tests](test_and_ci/fuzz_tests.md)
|
||||
- [Sanitizers](test_and_ci/sanitizers.md)
|
||||
- [Безперервна інтеграція](test_and_ci/continous_integration.md)
|
||||
- [Integration Testing](test_and_ci/integration_testing.md)
|
||||
- [MAVSDK Тестування інтеграції ](test_and_ci/integration_testing_mavsdk.md)
|
||||
@@ -984,7 +986,7 @@
|
||||
- [Релізи](releases/index.md)
|
||||
- [Release Process](releases/release_process.md)
|
||||
- [main (alpha)](releases/main.md)
|
||||
- [v1.18 (alpha)](releases/1.18.md)
|
||||
- [v1.18 (beta)](releases/1.18.md)
|
||||
- [1.17 (stable)](releases/1.17.md)
|
||||
- [1.16](releases/1.16.md)
|
||||
- [1.15](releases/1.15.md)
|
||||
|
||||
@@ -39,7 +39,7 @@
|
||||
|
||||
## GPS + компас + зумер + захисний вимикач + світлодіод
|
||||
|
||||
Pixhawk<sup>®</sup> V6X можна придбати з GPS [NEO3](https://store.cuav.net/shop/neo-3/) (10-контактний роз'єм) та слід підключити до порту **GPS1**.
|
||||
The Pixhawk<sup>®</sup> V6X can be purchased with a [NEO3 GPS](https://store.cuav.net/shop/neo-3-pro/) (10-pin connector) and should be connected to the **GPS1** port.
|
||||
Ці модулі GNSS мають вбудований компас, безпечний перемикач, дзвіночок та світлодіод.
|
||||
|
||||
Якщо вам потрібно використовувати допоміжний GPS, підключіться до порту **GPS2**.
|
||||
@@ -49,7 +49,7 @@ GPS/компас слід [монтувати на раму](../assembly/mount_g
|
||||
|
||||
|
||||
:::info
|
||||
Pixhawk V6X<sup>®</sup> is not compatible with NEO V2 GPS built-in buzzer: you should use [NEO3/NEO 3Pro](https://store.cuav.net/shop/neo-3/) instead.
|
||||
Pixhawk V6X<sup>®</sup> is not compatible with NEO V2 GPS built-in buzzer: you should use [NEO3/NEO 3Pro](https://store.cuav.net/shop/neo-3-pro/) instead.
|
||||
Вбудований безпечний вимикач в GPS-модулі увімкнений _за замовчуванням_ (коли включений, PX4 не дозволить вам готувати до польоту).
|
||||
Щоб вимкнути безпеку, натисніть і утримуйте безпечний вимикач протягом 1 секунди.
|
||||
Ви можете натиснути безпечний вимикач знову, щоб увімкнути безпеку та відключити транспортний засіб (це може бути корисно, якщо, з якихось причин, ви не можете вимкнути транспортний засіб за допомогою вашого пульта дистанційного керування або наземної станції).
|
||||
@@ -85,7 +85,7 @@ Connect the 6pin connector of the module to the flight control **Power C1** or *
|
||||
Бортову радіостанцію слід підключити до порту **TELEM1**/**TELEM2**/**TELEM3**, як показано нижче (у разі підключення до **TELEM1**, подальша конфігурація не потрібна).
|
||||
Інша радіостанція підключається до вашого комп'ютера або мобільного пристрою наземної станції (зазвичай за допомогою USB).
|
||||
|
||||
Ви також можете придбати телеметричні радіо з [магазину CUAV](https://store.cuav.net/uav-telemetry-module/).
|
||||
You can also purchase telemetry radios from the [CUAV store](https://store.cuav.net/category/telemetry/).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,133 +1,7 @@
|
||||
# Швидке підключення CUAV V5 nano
|
||||
<Redirect to="../flight_controller/autopilot_discontinued" />
|
||||
|
||||
:::warning
|
||||
PX4 не розробляє цей (або будь-який інший) автопілот.
|
||||
Contact the [manufacturer](https://store.cuav.net/) for hardware support or compliance issues.
|
||||
:::
|
||||
<!--
|
||||
# CUAV V5 nano Wiring Quick Start
|
||||
|
||||
This quick start guide shows how to power the [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) flight controller and connect its most important peripherals.
|
||||
|
||||
|
||||
|
||||
## Огляд схеми підключення
|
||||
|
||||
На зображенні нижче показано, як під'єднати найважливіші датчики та периферійні пристрої (за винятком виходів мотора та сервоприводів).
|
||||
Ми розглянемо кожну з них докладно в наступних розділах.
|
||||
|
||||
|
||||
|
||||
| Основний інтерфейс | Функція |
|
||||
| :--------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Power | Під'єднати модуль живлення; Надає живлення та виміри напруги та струму ANALOG. |
|
||||
| PM2 | [Do not use with PX4](../flight_controller/cuav_v5_nano.md#compatibility_pm2) |
|
||||
| TF CARD | Карта SD для зберігання logs (постачається з картою) |
|
||||
| M1~M8 | PWM виходи. Може бути використаний для управління двигунами або сервоприводами. |
|
||||
| A1~A3 | Capture pins (not _currently_ supported on PX4). |
|
||||
| nARMED | Вказує на стан зброєння FMU. Це активне низьке (низьке під час увімкнення). |
|
||||
| DSU7 | Використовується для дебагінгу FMU, читання інформації щодо дебагінгу. |
|
||||
| I2C2/I2C3/I2C4 | Підключає пристрій I2C, такий як зовнішній компас. |
|
||||
| CAN1/CAN2 | Підключає пристрої UAVCAN, такі як CAN GPS. |
|
||||
| TYPE-C\(USB\) | Під'єднатися до комп'ютера для зв'язку між контролером польоту та комп'ютером, наприклад, як завантаження прошивки |
|
||||
| GPS&SAFETY | Приєднайтесь до Neo GPS, який містить GPS, перемикач безпеки, інтерфейс зумовлювача. |
|
||||
| TELEM1/TELEM2 | Під'єднатися до системи телеметрії. |
|
||||
| DSM/SBUS/RSSI | Включає інтерфейси введення сигналів DSM, SBUS, RSSI, інтерфейс DSM може бути підключений до приймача DSM-супутника, інтерфейс SBUS - до приймача дистанційного керування SBUS, RSSI - для модуля зворотного повернення сили сигналу. |
|
||||
|
||||
:::info
|
||||
For more interface information, please read [V5 nano Manual](https://manual.cuav.net/V5-nano.pdf).
|
||||
:::
|
||||
|
||||
|
||||
|
||||
:::info
|
||||
If the controller cannot be mounted in the recommended/default orientation (e.g. due to space constraints) you will need to configure the autopilot software with the orientation that you actually used: [Flight Controller Orientation](../gps_compass/rtk_gps.md).
|
||||
:::
|
||||
|
||||
## GPS + Компас + Безпечний вимикач + Світлодіоди
|
||||
|
||||
The recommended GPS module is the _Neo v2 GPS_, which contains GPS, compass, safety switch, buzzer, LED status light.
|
||||
|
||||
:::info
|
||||
Other GPS modules may not work (see [this compatibility issue](../flight_controller/cuav_v5_nano.md#compatibility_gps)).
|
||||
:::
|
||||
|
||||
The GPS/Compass module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker towards the front of the vehicle (Neo GPS arrow is in the same direction as the flight control arrow).
|
||||
Під'єднайтеся до інтерфейсу GPS контролера польоту за допомогою кабелю.
|
||||
|
||||
:::info
|
||||
If you use CAN GPS, please use the cable to connect to the flight control CAN interface.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
## Запобіжний перемикач
|
||||
|
||||
The dedicated safety switch that comes with the V5+ is only required if you are not using the recommended _Neo v2 GPS_ (which has an inbuilt safety switch).
|
||||
|
||||
If you are flying without the GPS you must attach the switch directly to the `GPS1` port in order to be able to arm the vehicle and fly (If you use the old 6-pin GPS, please read the definition of the bottom interface to change the line).
|
||||
|
||||
## Зумер
|
||||
|
||||
If you do not use the recommended _Neo v2 GPS_ the buzzer may not work.
|
||||
|
||||
## Радіоуправління
|
||||
|
||||
Для ручного керування вашим апаратом потрібна система дистанційного керування радіо (RC) (PX4 не вимагає наявності системи радіо для автономних режимів польоту).
|
||||
Вам буде потрібно вибрати сумісний передавач/приймач та потім зв'язати їх, щоб вони взаємодіяли (прочитайте інструкції, що додаються до вашого конкретного передавача/приймача).
|
||||
|
||||
На малюнку нижче показано, як ви можете отримати доступ до вашого віддаленого приймача (знайдіть кабель S.Bus у комплекті)
|
||||
|
||||
|
||||
|
||||
## Супутникові приймачі Spektrum
|
||||
|
||||
V5 nano має присвячений кабель DSM.
|
||||
If using a Spektrum satellite receiver, this should be connected to the flight controller `DSM/SBUS/RSSI` interface.
|
||||
|
||||
## Power
|
||||
|
||||
The _v5 nano_ kit includes the _HV_PM_ module, which supports 2~14S LiPo batteries.
|
||||
Connect the 6pin connector of the _HW_PM_ module to the flight control `Power` interface.
|
||||
|
||||
:::warning
|
||||
The supplied power module is unfused.
|
||||
Power **must** be turned off while connecting peripherals.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
:::info
|
||||
The power module is not a power source for peripherals connected to the PWM outputs.
|
||||
Якщо ви підключаєте сервоприводи / приводи, вам потрібно окремо живити їх за допомогою BEC.
|
||||
:::
|
||||
|
||||
## Система телеметрії (Опціонально)
|
||||
|
||||
Система телеметрії дозволяє вам спілкуватися, контролювати та управляти транспортним засобом у польоті з наземної станції (наприклад, ви можете направляти БПЛА до певної позиції або завантажувати нове завдання).
|
||||
|
||||
Канал зв'язку здійснюється через телеметричні радіостанції.
|
||||
The vehicle-based radio should be connected to the **TELEM1** or **TELEM2** port (if connected to these ports, no further configuration is required).
|
||||
Інша радіостанція підключається до вашого комп'ютера або мобільного пристрою наземної станції (зазвичай через USB).
|
||||
|
||||
|
||||
|
||||
## SD Card (Optional) {#sd_card}
|
||||
|
||||
An [SD card](../getting_started/px4_basic_concepts.md#sd-cards-removable-memory) is inserted in the factory (you do not need to do anything).
|
||||
|
||||
## Двигуни
|
||||
|
||||
Motors/servos are connected to the MAIN ports in the order specified for your vehicle in the [Airframes Reference](../airframes/airframe_reference.md).
|
||||
|
||||
|
||||
|
||||
## Схема розташування виводів
|
||||
|
||||
|
||||
|
||||
## Подальша інформація
|
||||
|
||||
- [Airframe buildlog using CUAV v5 nano on a DJI FlameWheel450](../frames_multicopter/dji_f450_cuav_5nano.md)
|
||||
- [CUAV V5 nano](../flight_controller/cuav_v5_nano.md)
|
||||
- [V5 nano manual](https://manual.cuav.net/V5-nano.pdf) (CUAV)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165) (CUAV)
|
||||
- [CUAV Github](https://github.com/cuav) (CUAV)
|
||||
DOC REMOVED: 202607
|
||||
-->
|
||||
|
||||
@@ -1,134 +1,7 @@
|
||||
# Короткий посібник з підключення CUAV V5+
|
||||
<Redirect to="../flight_controller/autopilot_discontinued" />
|
||||
|
||||
:::warning
|
||||
PX4 не розробляє цей (або будь-який інший) автопілот.
|
||||
Contact the [manufacturer](https://store.cuav.net/) for hardware support or compliance issues.
|
||||
:::
|
||||
<!--
|
||||
# CUAV V5+ Wiring Quick Start
|
||||
|
||||
This quick start guide shows how to power the [CUAV V5+](../flight_controller/cuav_v5_plus.md) flight controller and connect its most important peripherals.
|
||||
|
||||
|
||||
|
||||
## Огляд схеми підключення
|
||||
|
||||
На зображенні нижче показано, як під'єднати найважливіші датчики та периферійні пристрої (за винятком виходів мотора та сервоприводів).
|
||||
Ми розглянемо кожну з них докладно в наступних розділах.
|
||||
|
||||
|
||||
|
||||
| Основний інтерфейс | Функція |
|
||||
| :--------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Power1 | Підключає модуль живлення. Power input with _analog_ voltage and current detection. Не використовуйте Digital PM на цьому роз'ємі! |
|
||||
| Power2 | Підключає i2c розумну батарею. |
|
||||
| TF CARD | Карта SD для зберігання журналів (карта попередньо вставлена на заводі). |
|
||||
| M1~M8 | PWM виходи. Може бути використаний для управління двигунами або сервоприводами. |
|
||||
| A1~A6 | PWM виходи. Може бути використаний для управління двигунами або сервоприводами. |
|
||||
| DSU7 | Використовується для дебагінгу FMU, читання інформації щодо дебагінгу. |
|
||||
| І2C1/I2C2 | Підключає пристрій I2C, такий як зовнішній компас. |
|
||||
| CAN1/CAN2 | Підключає пристрої UAVCAN, такі як CAN GPS. |
|
||||
| TYPE-C\(USB\) | Під'єднати до комп'ютера для зв'язку між контролером польоту та комп'ютером, наприклад, як завантаження прошивки. |
|
||||
| SBUS OUT | Підключає пристрої SBUS (наприклад, камери з карданним підвісом). |
|
||||
| GPS&SAFETY | Приєднайтесь до Neo GPS, який містить GPS, перемикач безпеки, інтерфейс зумовлювача. |
|
||||
| TELEM1/TELEM2 | Під'єднатися до системи телеметрії. |
|
||||
| DSM/SBUS/RSSI | Включає інтерфейси введення сигналів DSM, SBUS, RSSI, інтерфейс DSM може бути підключений до приймача DSM-супутника, інтерфейс SBUS - до приймача дистанційного керування SBUS, RSSI - для модуля зворотного повернення сили сигналу. |
|
||||
|
||||
:::info
|
||||
For more interface information, please read [V5+ Manual](https://manual.cuav.net/V5-Plus.pdf).
|
||||
:::
|
||||
|
||||
|
||||
|
||||
:::info
|
||||
If the controller cannot be mounted in the recommended/default orientation (e.g. due to space constraints) you will need to configure the autopilot software with the orientation that you actually used: [Flight Controller Orientation](../gps_compass/rtk_gps.md).
|
||||
:::
|
||||
|
||||
## GPS + Компас + Безпечний вимикач + Світлодіоди
|
||||
|
||||
The recommended GPS module is the _Neo v2 GPS_, which contains GPS, compass, safety switch, buzzer, LED status light.
|
||||
|
||||
:::info
|
||||
Other GPS modules may not work (see [this compatibility issue](../flight_controller/cuav_v5_nano.md#compatibility_gps)\)).
|
||||
:::
|
||||
|
||||
The GPS/Compass module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker towards the front of the vehicle (_Neo v2 GPS_ arrow is in the same direction as the flight control arrow).
|
||||
Під'єднайтеся до інтерфейсу GPS контролера польоту за допомогою кабелю.
|
||||
|
||||
:::info
|
||||
If you use the [NEO V2 PRO GNSS (CAN GPS)](https://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html), please use the cable to connect to the flight control CAN interface.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
## Запобіжний перемикач
|
||||
|
||||
The dedicated safety switch that comes with the V5+ is only required if you are not using the recommended _Neo V2 GPS_ (which has an inbuilt safety switch).
|
||||
|
||||
If you are flying without the GPS you must attach the switch directly to the `GPS1` port in order to be able to arm the vehicle and fly (if you use the old 6-pin GPS, please read the definition of the bottom interface to change the line).
|
||||
|
||||
## Зумер
|
||||
|
||||
Якщо ви не використовуєте рекомендований GPS, зумер може не працювати.
|
||||
|
||||
## Радіоуправління
|
||||
|
||||
Для ручного керування вашим апаратом потрібна система дистанційного керування радіо (RC) (PX4 не вимагає наявності системи радіо для автономних режимів польоту).
|
||||
Вам буде потрібно вибрати сумісний передавач/приймач та потім зв'язати їх, щоб вони взаємодіяли (прочитайте інструкції, що додаються до вашого конкретного передавача/приймача).
|
||||
|
||||
На малюнку нижче показано, як ви можете отримати доступ до вашого віддаленого приймача (знайдіть кабель SBUS у комплекті).
|
||||
|
||||
|
||||
|
||||
## Супутникові приймачі Spektrum
|
||||
|
||||
V5+ має присвячений кабель DSM.
|
||||
Якщо використовується супутниковий приймач Spektrum, його слід підключити до інтерфейсу DSM/SBUS/RSSI контролера польоту.
|
||||
|
||||
## Power
|
||||
|
||||
The V5+ kit includes the _HV_PM_ module, which supports 2~14S LiPo batteries.
|
||||
Connect the 6pin connector of the _HW_PM_ module to the flight control `Power1` interface.
|
||||
|
||||
:::warning
|
||||
The supplied power module is unfused.
|
||||
Power **must** be turned off while connecting peripherals.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
:::info
|
||||
The power module is not a power source for peripherals connected to the PWM outputs.
|
||||
Якщо ви підключаєте сервоприводи / приводи, вам потрібно окремо живити їх за допомогою BEC.
|
||||
:::
|
||||
|
||||
## Система телеметрії (Опціонально)
|
||||
|
||||
Система телеметрії дозволяє вам спілкуватися, контролювати та управляти транспортним засобом у польоті з наземної станції (наприклад, ви можете направляти БПЛА до певної позиції або завантажувати нове завдання).
|
||||
|
||||
Канал зв'язку здійснюється через телеметричні радіостанції.
|
||||
The vehicle-based radio should be connected to either the `TELEM1` or `TELEM2` port (if connected to these ports, no further configuration is required).
|
||||
Інша радіостанція підключається до вашого комп'ютера або мобільного пристрою наземної станції (зазвичай через USB).
|
||||
|
||||
|
||||
|
||||
## SD Card (Optional) {#sd_card}
|
||||
|
||||
An [SD card](../getting_started/px4_basic_concepts.md#sd-cards-removable-memory) is inserted in the factory (you do not need to do anything).
|
||||
|
||||
## Двигуни
|
||||
|
||||
Motors/servos are connected to the MAIN and AUX ports in the order specified for your vehicle in the [Airframes Reference](../airframes/airframe_reference.md).
|
||||
|
||||
|
||||
|
||||
## Схема розташування виводів
|
||||
|
||||
See [CUAV V5+ Manual](https://manual.cuav.net/V5-Plus.pdf).
|
||||
|
||||
## Подальша інформація
|
||||
|
||||
- [Airframe build-log using CUAV v5+ on a DJI FlameWheel450](../frames_multicopter/dji_f450_cuav_5plus.md)
|
||||
- [CUAV V5+ Manual](https://manual.cuav.net/V5-Plus.pdf) (CUAV)
|
||||
- [CUAV V5+ docs](https://doc.cuav.net/controller/v5-autopilot/en/v5+.html) (CUAV)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165) (CUAV)
|
||||
- [CUAV Github](https://github.com/cuav) (CUAV)
|
||||
- [Base board design reference](https://github.com/cuav/hardware/tree/master/V5_Autopilot/V5%2B/V5%2BBASE) (CUAV)
|
||||
DOC REMOVED: 202607
|
||||
-->
|
||||
|
||||
@@ -51,7 +51,7 @@ The following flight controller models are applicable to this quick start guide.
|
||||
|
||||
We recommend using a CAN GPS/RTK (such as [Neo 4SE](https://store.cuav.net/shop/cuav-neo-4-se-gps-module/)); simply connect it to the **CAN 1** or **CAN 2** port.
|
||||
|
||||
You can also use a standard GPS/RTK module(such as [NEO3 GPS](https://store.cuav.net/shop/neo-3/) (10-pin connector)) by connecting it to the **GPS&SAFETY** port.
|
||||
You can also use a standard GPS/RTK module(such as [NEO3 GPS](https://store.cuav.net/shop/neo-3-pro/) (10-pin connector)) by connecting it to the **GPS&SAFETY** port.
|
||||
Most commonly used GPS modules today integrate GPS, compass, safety switch, buzzer, and LED status light.
|
||||
|
||||
Якщо вам потрібно використовувати допоміжний GPS, підключіться до порту **GPS2**.
|
||||
@@ -105,7 +105,7 @@ It can be directly connected to the **Power C1/C2** port of the X25 EVO and is p
|
||||
|
||||
[Telemetry system](../telemetry/index.md) allows you to communicate with the unmanned system via ground station software, enabling you to monitor and control the UAV’s status during flight. Connect the on-board unit of the telemetry system to the **TELEM1** or **TELEM2** port.
|
||||
|
||||
Ви також можете придбати телеметричні радіо з [магазину CUAV](https://store.cuav.net/uav-telemetry-module/).
|
||||
You can also purchase telemetry radios from the [CUAV store](https://store.cuav.net/category/telemetry/).
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ For a Ubuntu companion, a minimal set might be:
|
||||
sudo apt install gstreamer1.0-plugins-bad gstreamer1.0-libav gstreamer1.0-gl -y
|
||||
```
|
||||
|
||||
For the full set you can mirror the QGC dependencies installed by [/tools/setup/install_dependencies.py](https://github.com/mavlink/qgroundcontrol/blob/master/tools/setup/install_dependencies.py).
|
||||
For the full set you can mirror the QGC dependencies installed by [/tools/setup/install_dependencies](https://github.com/mavlink/qgroundcontrol/tree/master/tools/setup/install_dependencies).
|
||||
At time of writing this is:
|
||||
|
||||
```sh
|
||||
|
||||
@@ -122,7 +122,6 @@ An overview of the Crazyflie 2.1 can be [found here](https://www.bitcraze.io/pro
|
||||
## Встановлення оригінальної прошивки Bitcraze
|
||||
|
||||
1. Завантажте останній [завантажувач Crazyflie 2.1](https://github.com/bitcraze/crazyflie2-stm-bootloader/releases)
|
||||
|
||||
2. Поставте Crazyflie 2.1 у режим DFU, виконавши ці кроки:
|
||||
- Спочатку переконайтеся, що він знеструмлений.
|
||||
- Переконайтеся, що акумулятор від'єднаний.
|
||||
@@ -130,7 +129,6 @@ An overview of the Crazyflie 2.1 can be [found here](https://www.bitcraze.io/pro
|
||||
- Підключіть до USB-порту комп'ютера.
|
||||
- Через секунду синій світлодіод повинен почати блимати, а через 5 секунд повинен почати блимати швидше.
|
||||
- Відпустіть кнопку.
|
||||
|
||||
3. Виконайте прошивку завантажувальника за допомогою _dfu-util_ та від'єднайте Crazyflie 2.1, коли це зроблено:
|
||||
|
||||
```sh
|
||||
@@ -139,7 +137,7 @@ An overview of the Crazyflie 2.1 can be [found here](https://www.bitcraze.io/pro
|
||||
|
||||
Коли увімкнено Crazyflie 2.1, жовтий світлодіод повинен мигати.
|
||||
|
||||
4. Встановіть останнє програмне забезпечення для польоту Bitcraze Crazyflie 2.1, використовуючи [цей](https://www.bitcraze.io/documentation/tutorials/getting-started-with-crazyflie-2-x/#update-fw) посібник.
|
||||
. Встановіть останнє програмне забезпечення для польоту Bitcraze Crazyflie 2.1, використовуючи [цей](https://www.bitcraze.io/documentation/tutorials/getting-started-with-crazyflie-2-x/#update-fw) посібник.
|
||||
|
||||
## Інструкції з налаштування бездротового з'єднання
|
||||
|
||||
@@ -151,15 +149,26 @@ An overview of the Crazyflie 2.1 can be [found here](https://www.bitcraze.io/pro
|
||||
Підключення через **MAVLink**:
|
||||
|
||||
- Використовуйте Crazyradio PA разом із сумісним GCS.
|
||||
- Завантажте вихідний код _crazyflie-lib-python_:
|
||||
|
||||
- Download the _crazyflie-lib-python_ source code, and check out the last commit that included `cfbridge.py` (see warning below):
|
||||
|
||||
```sh
|
||||
git clone https://github.com/bitcraze/crazyflie-lib-python.git
|
||||
git -C crazyflie-lib-python checkout 829ae10715b5bf2373a7a643434e474ab406fc62
|
||||
```
|
||||
|
||||
:::info
|
||||
Ми будемо використовувати [cfbridge.py](https://github.com/bitcraze/crazyflie-lib-python/blob/master/examples/cfbridge.py) для налаштування бездротового зв'язку MAVlink між Crazyflie 2.1 (прошитий PX4) та QGroundControl. _Cfbridge_ дозволяє QGroundControl комунікувати з crazyradio PA.
|
||||
Цей [базований на C cfbridge](https://github.com/dennisss/cfbridge) наразі має проблеми з втратою даних, тому ми вирішили використовувати **cfbridge.py**.
|
||||
::: info
|
||||
We will use [cfbridge.py](https://github.com/bitcraze/crazyflie-lib-python/blob/829ae10715b5bf2373a7a643434e474ab406fc62/examples/cfbridge.py) to setup a wireless MAVlink communication link between Crazyflie 2.1 (flashed with PX4) and QGroundControl.
|
||||
_Cfbridge_ дозволяє QGroundControl комунікувати з crazyradio PA.
|
||||
Цей [базований на C cfbridge](https://github.com/dennisss/cfbridge) наразі має проблеми з втратою даних, тому ми вирішили використовувати **cfbridge.py**.
|
||||
|
||||
:::
|
||||
|
||||
::: warning
|
||||
`cfbridge.py` was removed from the `crazyflie-lib-python` repository upstream (April 2026) and was not migrated to Bitcraze's `crazyflie-demos` repository.
|
||||
The commands above check out the last commit that included the file.
|
||||
This part of the workflow is no longer maintained by Bitcraze!
|
||||
|
||||
:::
|
||||
|
||||
- Переконайтеся, що ви налаштували дозволи udev для використання USB радіо. Для цього виконайте наступні кроки [тут](https://www.bitcraze.io/documentation/repository/crazyflie-lib-python/master/installation/usb_permissions/) та **перезапустіть** ваш комп'ютер.
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
# DroneBlocks DEXI 5
|
||||
|
||||
The [DEXI 5](https://droneblocks.io/program/dexi-5-px4-stem-drone-kit/) is an NDAA-compliant PX4 STEM and development drone kit from [DroneBlocks](https://droneblocks.io/), designed to take students, hobbyists, and PX4 developers from unboxing to writing autonomous code with no technical barrier.
|
||||
|
||||
DEXI 5 is an [Official PX4 Developer Kit](../dev_kits/index.md).
|
||||
|
||||
|
||||
|
||||
## Загальний огляд
|
||||
|
||||
DEXI 5 is built around an all-in-one flight controller running PX4, developed in collaboration with [ARK Electronics](https://arkelectron.com/), with integrated optical flow sensing for GPS-denied indoor flight.
|
||||
A Raspberry Pi compute module acts as the companion computer, with a Pi camera and accessible GPIO pins for sensors, servos, and other payloads (up to about 225 g).
|
||||
|
||||
Assembly is modular, solder-free, and plug-and-play, and is itself part of the learning experience: building the vehicle teaches the aerodynamics, mechanics, and electronics behind it.
|
||||
|
||||
All critical electronic components are manufactured in the United States, meeting NDAA Section 848 requirements.
|
||||
|
||||
## Software and Curriculum
|
||||
|
||||
The kit ships with a full project-based curriculum on [learn.droneblocks.io](https://learn.droneblocks.io/) covering:
|
||||
|
||||
- DroneBlocks visual (block-based) programming
|
||||
- Python scripting with [MAVSDK](https://mavsdk.mavlink.io/)
|
||||
- [ROS 2](../ros2/index.md) development, including projects such as AprilTag detection
|
||||
- Computer vision with OpenCV using the onboard Pi camera
|
||||
|
||||
Community support is available on the [DroneBlocks forum](https://community.droneblocks.io/).
|
||||
|
||||
## Де купити
|
||||
|
||||
- [DroneBlocks DEXI 5](https://droneblocks.io/program/dexi-5-px4-stem-drone-kit/) (single kits and classroom packs)
|
||||
@@ -12,8 +12,13 @@
|
||||
Цей розділ містить перелік наборів дронів, які призначені як платформи для подальшого розвитку.
|
||||
Вони можуть бути як повністю зібраними, так і у частинах.
|
||||
|
||||
:::tip
|
||||
Kits certified by the PX4 team are listed in [PX4 Developer Kits](../dev_kits/index.md).
|
||||
:::
|
||||
|
||||
- [ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md) - SLAM development drone supercharged by VOXL 2 and PX4 ([Official PX4 Developer Kit](../dev_kits/index.md))
|
||||
- [DroneBlocks DEXI 5](../complete_vehicles_mc/droneblocks_dexi.md) - STEM/development kit with optical flow and Raspberry Pi companion computer ([Official PX4 Developer Kit](../dev_kits/index.md))
|
||||
- [PX4 Vision DevKit](../complete_vehicles_mc/px4_vision_kit.md) - Мультикоптер, що використовується для розробки комп'ютерного зору PX4
|
||||
- [ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md) - SLAM development drone supercharged by VOXL 2 and PX4.
|
||||
|
||||
## Попередньо встановлене PX4
|
||||
|
||||
|
||||
@@ -137,34 +137,38 @@ _Польотні завдання_ використовуються у [Реж
|
||||
|
||||
Наприклад, щоб активувати наше нове завдання `MyTask` в позиційному режимі мультикоптера:
|
||||
|
||||
- Оновіть `MPC_POS_MODE` ([multicopter_position_mode_params.](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mc_pos_control/multicopter_position_mode_params.c)), щоб додати варіант для вибору "MyTask", якщо параметр має раніше невикористане значення, наприклад 5:
|
||||
- Update `MPC_POS_MODE` ([multicopter_position_mode_params.yaml](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mc_pos_control/multicopter_position_mode_params.yaml)) to add an option for selecting "MyTask" using a previously unused parameter value (in this case 5):
|
||||
|
||||
```c
|
||||
...
|
||||
* @value 0 Direct velocity
|
||||
* @value 4 Acceleration based
|
||||
* @value 5 My task
|
||||
* @group Multicopter Position Control
|
||||
*/
|
||||
PARAM_DEFINE_INT32(MPC_POS_MODE, 5);
|
||||
```yaml
|
||||
MPC_POS_MODE:
|
||||
...
|
||||
type: enum
|
||||
values:
|
||||
0: Direct velocity
|
||||
4: Acceleration based
|
||||
5: My task
|
||||
default: 4
|
||||
```
|
||||
|
||||
- Додайте мітку case для нового варіанту в операторі switch для параметра в [FlightModeManager.cpp](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/flight_mode_manager/FlightModeManager.cpp#L266-L285), щоб увімкнути завдання коли `_param_mpc_pos_mode` має відповідне значення.
|
||||
- Add a case for your new option in the switch for the parameter [FlightModeManager.cpp](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/flight_mode_manager/FlightModeManager.cpp#L214-L229) to enable the task when `_param_mpc_pos_mode` has the right value.
|
||||
|
||||
```cpp
|
||||
...
|
||||
// manual position control
|
||||
...
|
||||
switch (_param_mpc_pos_mode.get()) {
|
||||
...
|
||||
case 3:
|
||||
error = switchTask(FlightTaskIndex::ManualPositionSmoothVel);
|
||||
break;
|
||||
case 5: // Add case for new task: MyTask
|
||||
error = switchTask(FlightTaskIndex::MyTask);
|
||||
break;
|
||||
case 0:
|
||||
error = switchTask(FlightTaskIndex::ManualPosition);
|
||||
break;
|
||||
|
||||
case 5:
|
||||
error = switchTask(FlightTaskIndex::MyTask);
|
||||
break;
|
||||
|
||||
case 4:
|
||||
....
|
||||
default:
|
||||
...
|
||||
error = switchTask(FlightTaskIndex::ManualAcceleration);
|
||||
break;
|
||||
}
|
||||
...
|
||||
```
|
||||
|
||||
|
||||
@@ -126,9 +126,18 @@ PX4 and the receiver may also need to be configured in order to _detect RC loss_
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="COM_RC_LOSS_T"></a>[COM_RC_LOSS_T](../advanced_config/parameter_reference.md#COM_RC_LOSS_T) | Аварійний режим втрати ручного керування Timeout | Час після отримання останньої встановленої точки від вибраного джерела керування вручну, після якого керування вважається втраченим. This must be kept short because the vehicle will continue to fly using the last known stick position until the timeout triggers. |
|
||||
| <a id="COM_FAIL_ACT_T"></a>[COM_FAIL_ACT_T](../advanced_config/parameter_reference.md#COM_FAIL_ACT_T) | Затримка відмови від дії | Delay in seconds between failsafe condition being triggered (`COM_RC_LOSS_T`) and failsafe action (RTL, Land, Hold). У цьому стані транспортний засіб очікує в режимі утримання на повторне підключення джерела керування вручну. Це може бути встановлено довше для довгих польотів, щоб втрата інтермітентного з'єднання не викликала негайного виклику аварійного режиму. Це може бути рівним нулю, щоб аварійний запобіжник спрацював негайно. |
|
||||
| <a id="NAV_RCL_ACT"></a>[NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) | Моделювання відмовостійкості | Вимкнути, Блукати, Повернутися, Приземлитися, Роззброїти, Завершити. |
|
||||
| <a id="NAV_RCL_ACT"></a>[NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) | Моделювання відмовостійкості | Disabled, Loiter, Return, Land, Disarm, Terminate, Hold mode (no failsafe). |
|
||||
| <a id="COM_RCL_EXCEPT"></a>[COM_RCL_EXCEPT](../advanced_config/parameter_reference.md#COM_RCL_EXCEPT) | Виключення втрат RC | Set modes in which manual control loss is ignored. |
|
||||
|
||||
### Hold Mode (No Failsafe)
|
||||
|
||||
The `Hold mode (no failsafe)` action (`NAV_RCL_ACT = 7`) is a special case that does _not_ enter the failsafe.
|
||||
Instead, if manual control is lost while actively flying a manual mode (such as Position, Altitude, or Stabilized), the vehicle switches to [Hold mode](../flight_modes_mc/hold.md) as if the user had commanded it: there is no failsafe state and no alarming failsafe notification.
|
||||
This is intended for operations where a switch to Hold on manual control loss is expected and should not be surfaced as a failsafe (for example when operating multiple drones with one GCS).
|
||||
|
||||
If Hold cannot be entered (for example without a valid position estimate), the normal failsafe takes over and escalates from there (Return, Land, Descend, or Terminate as applicable).
|
||||
Manual control loss in any non-manual (auto/offboard) mode is ignored with this setting.
|
||||
|
||||
## Втрата каналу зв'язку Failsafe
|
||||
|
||||
The Data Link Loss failsafe is triggered if the connection to the last MAVLink ground station like QGroundControl is lost.
|
||||
|
||||
@@ -49,7 +49,7 @@
|
||||
git add <file name>
|
||||
```
|
||||
|
||||
If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](https://nuclearsquid.com/writings/git-add/).
|
||||
If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](https://nuclearsquid.com/writings/git-add/).
|
||||
|
||||
-
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Software Bill of Materials (SBOM)
|
||||
|
||||
PX4 generates a [Software Bill of Materials](https://ntia.gov/SBOM) for every firmware build in [SPDX 2.3](https://spdx.github.io/spdx-spec/v2.3/) JSON format.
|
||||
PX4 generates a [Software Bill of Materials](https://www.ntia.gov/SBOM) for every firmware build in [SPDX 2.3](https://spdx.github.io/spdx-spec/v2.3/) JSON format.
|
||||
|
||||
## Why SBOM?
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Follow the [ROS 2 Installation & Setup](../ros2/user_guide.md#installation-setup
|
||||
|
||||
You will also need to install:
|
||||
|
||||
- [PlotJuggler for ROS2](https://github.com/facontidavide/PlotJuggler)
|
||||
- [PlotJuggler for ROS2](https://github.com/PlotJuggler/PlotJuggler)
|
||||
|
||||
::: tip
|
||||
Use the Debian packages (the snap files are not supported).
|
||||
|
||||
@@ -21,7 +21,7 @@ The _6-pos DF13_ connector that comes with the probe cannot be used for SWD debu
|
||||
|
||||
:::info
|
||||
To debug STM32F7 or later (FMUv5 and newer) the Zubax BugFace BF1 / Blackmagic probe likely requires a firmware update.
|
||||
You can find how to update the [blackmagic probe here](https://black-magic.org/upgrade.html).
|
||||
You can find how to update the [blackmagic probe here](https://black-magic.org/docs/intro/upgrade/).
|
||||
:::
|
||||
|
||||
To use a Zubax BugFace BF1 with GDB, start GDB with the exact ELF file that is currently flashed on the autopilot:
|
||||
|
||||
@@ -19,9 +19,9 @@ The [MCU-Link Debug Probe](https://www.nxp.com/design/design-center/software/dev
|
||||
|
||||
## Налагодження конфігурації за допомогою NXP LinkServer
|
||||
|
||||
MCU-Link забезпечує для чіпів NXP (FMUv6X-RT) сервер GDB [LinkServer](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER):
|
||||
The MCU-Link provides for NXP (FMUv6X-RT) chips the [LinkServer](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKSERVER) GDB server:
|
||||
|
||||
[Завантажте](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER#downloads) Linkserver для вашої операційної системи та дотримуйтесь інструкцій з установки.
|
||||
[Download](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKSERVER#downloads) the Linkserver for your operating system and follow the installation instructions.
|
||||
|
||||
На Windows LinkServer встановлюється в `C:\NXP\LinkServer_x.x.x`
|
||||
На Linux LinkServer встановлюється `/usr/local/LinkServer/LinkServer`
|
||||
|
||||
@@ -34,7 +34,7 @@ Flight controllers commonly provide a single debug port that exposes both the [S
|
||||
The [Pixhawk Connector Standards](#pixhawk-standard-debug-ports) formalize the port that must be used in each FMU version.
|
||||
However there are still many boards that use different pinouts or connectors, so we recommend you check the [documentation for your autopilot](../flight_controller/index.md) to confirm port location and pinout.
|
||||
|
||||
Місцезнаходження порту налагодження та роз'єми для підмножини автопілотів зв'язані нижче:
|
||||
The debug port location and pinouts for a subset of current autopilots are linked below:
|
||||
|
||||
<a id="port-information"></a>
|
||||
|
||||
@@ -53,8 +53,6 @@ However there are still many boards that use different pinouts or connectors, so
|
||||
| [Holybro Kakute H7](../flight_controller/kakuteh7.md#debug-port) | SWD pads and system console |
|
||||
| [Holybro Kakute H7 mini](../flight_controller/kakuteh7mini.md#debug-port) | SWD pads and system console |
|
||||
| [Holybro Kakute H7 V2](../flight_controller/kakuteh7v2.md#debug-port) | SWD pads and system console |
|
||||
| [CUAV V5+](../flight_controller/cuav_v5_plus.md#debug-port) | Custom port but comes with adaptor cable |
|
||||
| [CUAV V5nano](../flight_controller/cuav_v5_nano.md#debug_port) | Custom port but comes with adaptor cable |
|
||||
| [CUAV Pixhawk V6X](../flight_controller/cuav_pixhawk_v6x.md#debug_port) | [Pixhawk Debug Full](#pixhawk-debug-full) |
|
||||
| [CUAV X25-SUPER](../flight_controller/cuav_x25-super.md#debug_port) | [Pixhawk Debug Mini] |
|
||||
| [CUAV X25-EVO](../flight_controller/cuav_x25-evo.md#debug_port) | [Pixhawk Debug Mini] |
|
||||
@@ -201,7 +199,7 @@ Some SWD [debug probes](#debug-probes) come with adapters/cables for connecting
|
||||
|
||||
Some manufacturers provide cables to make it easy to connect the SWD interface and [System Console](../debug/system_console.md).
|
||||
|
||||
- [CUAV V5nano](../flight_controller/cuav_v5_nano.md#debug_port) and [CUAV V5+](../flight_controller/cuav_v5_plus.md#debug-port) include this debug cable:
|
||||
For example, some CUAV board include this debug cable:
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -246,16 +246,19 @@ If the airframe is for a **new group** you additionally need to:
|
||||
|
||||
3. Update _QGroundControl_:
|
||||
- Add the svg image for the group into: [src/AutopilotPlugins/Common/images](https://github.com/mavlink/qgroundcontrol/tree/master/src/AutoPilotPlugins/Common/Images)
|
||||
- Add reference to the svg image into [qgcimages.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcimages.qrc), following the pattern below:
|
||||
- Add a reference to the svg image into [CMakeLists.txt](https://github.com/mavlink/qgroundcontrol/blob/master/src/AutoPilotPlugins/Common/CMakeLists.txt), following the pattern below:
|
||||
|
||||
```xml
|
||||
<qresource prefix="/qmlimages">
|
||||
...
|
||||
<file alias="Airframe/AirframeSimulation">src/AutoPilotPlugins/Common/Images/AirframeSimulation.svg</file>
|
||||
<file alias="Airframe/AirframeUnknown">src/AutoPilotPlugins/Common/Images/AirframeUnknown.svg</file>
|
||||
<file alias="Airframe/Boat">src/AutoPilotPlugins/Common/Images/Boat.svg</file>
|
||||
<file alias="Airframe/FlyingWing">src/AutoPilotPlugins/Common/Images/FlyingWing.svg</file>
|
||||
...
|
||||
```cmake
|
||||
qt_add_resources(${CMAKE_PROJECT_NAME} autopilot_plugin_common_airframes
|
||||
PREFIX "/qmlimages/Airframe"
|
||||
BASE "${CMAKE_SOURCE_DIR}/src/AutoPilotPlugins/Common/Images"
|
||||
FILES
|
||||
"${CMAKE_SOURCE_DIR}/src/AutoPilotPlugins/Common/Images/AirframeSimulation.svg"
|
||||
"${CMAKE_SOURCE_DIR}/src/AutoPilotPlugins/Common/Images/AirframeUnknown.svg"
|
||||
"${CMAKE_SOURCE_DIR}/src/AutoPilotPlugins/Common/Images/Boat.svg"
|
||||
"${CMAKE_SOURCE_DIR}/src/AutoPilotPlugins/Common/Images/FlyingWing.svg"
|
||||
...
|
||||
)
|
||||
```
|
||||
|
||||
::: info
|
||||
|
||||
@@ -0,0 +1,59 @@
|
||||
# PX4 Developer Kits
|
||||
|
||||
Official PX4 Developer Kits are the recommended way to get flying hardware for PX4 application development.
|
||||
|
||||
Kits that carry the _Official PX4 Developer Kit_ designation are certified by the PX4 maintainer team to meet the requirements of the [Developer Kit Program](../hardware/dev_kit_program.md):
|
||||
|
||||
- A flight controller that meets the latest Pixhawk standard, or matches its capabilities
|
||||
- The latest stable PX4 release, pre-installed
|
||||
- Pre-assembled, or assembly that requires no technical skill (no soldering)
|
||||
- A guide, a focused tutorial, and a printed reference sheet included in the box
|
||||
- Third-party build quality verification
|
||||
|
||||
This means you can take any of the kits below out of the box and be developing against a current, supported PX4 stack in hours, not weeks.
|
||||
|
||||
:::info
|
||||
Manufacturers who want their kit certified should read the [Developer Kit Program](../hardware/dev_kit_program.md) documentation.
|
||||
:::
|
||||
|
||||
## ModalAI Starling 2 Max
|
||||
|
||||
|
||||
|
||||
The [Starling 2 Max](https://www.modalai.com/products/starling-2-max) is an NDAA-compliant, ready-to-fly development drone built around the [VOXL 2](../flight_controller/modalai_voxl_2.md), which combines the flight controller and a powerful companion computer in a single package.
|
||||
|
||||
It is designed for computer-vision development (SLAM, GPS-denied navigation, long-range dead reckoning), carries a 500 g payload, and flies for up to 55 minutes.
|
||||
The open source [VOXL SDK](https://gitlab.com/voxl-public/voxl-sdk) ships with pre-configured autonomy models, and the platform supports ROS 2 and MAVSDK workflows on the onboard computer.
|
||||
|
||||
- [PX4 documentation](../complete_vehicles_mc/modalai_starling.md)
|
||||
- [Manufacturer documentation](https://docs.modalai.com/starling-2-max/)
|
||||
|
||||
## DroneBlocks DEXI 5
|
||||
|
||||
|
||||
|
||||
The [DEXI 5](https://droneblocks.io/program/dexi-5-px4-stem-drone-kit/) is an NDAA-compliant STEM and development drone kit built around an all-in-one PX4 flight controller with integrated optical flow (for GPS-denied indoor flight) and a Raspberry Pi companion computer with camera.
|
||||
|
||||
Assembly is modular, solder-free, and plug-and-play.
|
||||
The kit ships with a full project-based curriculum covering Python (MAVSDK), ROS 2, OpenCV, and DroneBlocks visual programming, taking you from unboxing to autonomous code with no technical barrier.
|
||||
|
||||
- [PX4 documentation](../complete_vehicles_mc/droneblocks_dexi.md)
|
||||
- [Manufacturer curriculum](https://learn.droneblocks.io/)
|
||||
|
||||
## Holybro X500 v2
|
||||
|
||||
|
||||
|
||||
The [PX4 Development Kit X500 v2](https://holybro.com/products/px4-development-kit-x500-v2) is a classic 500 mm carbon-fiber quadcopter kit with a Pixhawk 6C or 6X flight controller, M10 GPS, telemetry radio, and power module.
|
||||
|
||||
Motors and ESCs come pre-installed on the arms, so assembly is solder-free and takes about 30 minutes.
|
||||
It lifts a 1.5 kg payload, which makes it a good base for adding your own companion computer and sensors.
|
||||
|
||||
- [PX4 build guide](../frames_multicopter/holybro_x500v2_pixhawk6c.md)
|
||||
- [Manufacturer documentation](https://docs.holybro.com/drone-development-kit/px4-development-kit-x500v2)
|
||||
|
||||
## Дивіться також
|
||||
|
||||
- [Повні Транспортні Засоби (MC)](../complete_vehicles_mc/README.md)
|
||||
- [Kit Builds (MC)](../frames_multicopter/kits.md)
|
||||
- [Developer Kit Program](../hardware/dev_kit_program.md) (for manufacturers)
|
||||
@@ -498,7 +498,7 @@ struct message_dropout_s {
|
||||
- [QGroundControl](https://github.com/mavlink/qgroundcontrol): C++, ULog streaming via MAVLink and minimal parsing for GeoTagging.
|
||||
- [mavlink-router](https://github.com/mavlink-router/mavlink-router): C++, ULog streaming via MAVLink.
|
||||
- [MAVGAnalysis](https://github.com/ecmnet/MAVGCL): Java, ULog streaming via MAVLink and parser for plotting and analysis.
|
||||
- [PlotJuggler](https://github.com/facontidavide/PlotJuggler): C++/Qt application to plot logs and time series. Підтримує ULog з версії 2.1.3.
|
||||
- [PlotJuggler](https://github.com/PlotJuggler/PlotJuggler): C++/Qt application to plot logs and time series. Підтримує ULog з версії 2.1.3.
|
||||
- [ulogreader](https://github.com/maxsun/ulogreader): Javascript, ULog reader and parser outputs log in JSON object format.
|
||||
- [Foxglove](https://foxglove.dev): an integrated visualization and diagnosis tool for robotics data that supports ULog files.
|
||||
- [TypeScript ULog parser](https://github.com/foxglove/ulog): TypeScript, ULog reader that outputs JS objects.
|
||||
|
||||
@@ -122,9 +122,9 @@ The following list shows the build commands for the [Pixhawk standard](../flight
|
||||
|
||||
- [Pixhawk 4 Mini (FMUv5)](../flight_controller/pixhawk4_mini.md): `make px4_fmu-v5_default`
|
||||
|
||||
- [CUAV V5+ (FMUv5)](../flight_controller/cuav_v5_plus.md): `make px4_fmu-v5_default`
|
||||
- [CUAV V5+ (FMUv5)](../flight_controller/cuav_v5_plus.md): `make px4_fmu-v5_default` - Discontinued
|
||||
|
||||
- [CUAV V5 nano (FMUv5)](../flight_controller/cuav_v5_nano.md): `make px4_fmu-v5_default`
|
||||
- [CUAV V5 nano (FMUv5)](../flight_controller/cuav_v5_nano.md): `make px4_fmu-v5_default` - Discontinued
|
||||
|
||||
- [Pixracer (FMUv4)](../flight_controller/pixracer.md): `make px4_fmu-v4_default`
|
||||
|
||||
|
||||
@@ -29,8 +29,8 @@ The module incorporates the [Septentrio mosaic-G5 P3 Ultra-compact high-precisio
|
||||
- Advanced GNSS+ algorithms
|
||||
- 20Hz update rate
|
||||
- [ST IIS2MDC Magnetometer](https://www.st.com/en/mems-and-sensors/iis2mdc.html)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://www.invensense.tdk.com/en-us/products/6-axis/icm-42688-p)
|
||||
- STM32F412VGH6 MCU
|
||||
- Кнопка безпеки
|
||||
- Зумер
|
||||
|
||||
@@ -29,8 +29,8 @@ The module incorporates the [Septentrio mosaic-G5 P3H Ultra-compact high-precisi
|
||||
- Advanced GNSS+ algorithms
|
||||
- 20Hz update rate
|
||||
- [ST IIS2MDC Magnetometer](https://www.st.com/en/mems-and-sensors/iis2mdc.html)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://www.invensense.tdk.com/en-us/products/6-axis/icm-42688-p)
|
||||
- STM32F412VGH6 MCU
|
||||
- Кнопка безпеки
|
||||
- Зумер
|
||||
|
||||
@@ -19,8 +19,8 @@
|
||||
- [AIM+ jamming protection](https://www.septentrio.com/en/learn-more/advanced-positioning-technology/aim-anti-jamming-protection)
|
||||
- Update rate of 100 Hz
|
||||
- ST IIS2MDC Magnetometer
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp390.html)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp390.html)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://www.invensense.tdk.com/en-us/products/6-axis/icm-42688-p)
|
||||
- STM32F412VGH6 MCU
|
||||
- З'єднання
|
||||
- Two Pixhawk Standard CAN Connectors (4 Pin JST-GH, 5V Input)
|
||||
|
||||
@@ -21,8 +21,8 @@
|
||||
- -162 dBm tracking sensitivity
|
||||
- Submeter positioning accuracy
|
||||
- [ST IIS2MDC Magnetometer](https://www.st.com/en/mems-and-sensors/iis2mdc.html)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp390.html)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/pressure-sensors-bmp390.html)
|
||||
- [Invensense ICM-42688-P 6-Axis IMU](https://www.invensense.tdk.com/en-us/products/6-axis/icm-42688-p)
|
||||
- STM32F412VGH6 MCU
|
||||
- Dual Band (L1/L5) Helical GPS Antenna
|
||||
- Два роз'єми стандарту CAN для Pixhawk (4 контакти JST GH)
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
:::warning
|
||||
PX4 не розробляє цей (або будь-який інший) автопілот.
|
||||
Contact [3DR](https://3dr.com/) for hardware support or compliance issues.
|
||||
Contact [3DR](https://www.3dr.com/) for hardware support or compliance issues.
|
||||
:::
|
||||
|
||||
The _3DR Control N1_ is a compact, high-performance, low-profile and lightweight flight controller designed and assembled in USA.
|
||||
@@ -116,14 +116,14 @@ Select and assign your preferred protocol in QGroundControl during initial setup
|
||||
The Control N1 is designed to be used with a carrier board.
|
||||
The following carrier boards are available from 3DR:
|
||||
|
||||
| Материнська плата | Опис |
|
||||
| --------------------------------------------------------------------------------------------------- | --------------------------------------------- |
|
||||
| [CB1 Cuby](https://docs.3dr.com/autopilots/carrier-boards/r0026-cb1-cuby) | Compact square form factor |
|
||||
| [CB2 Longy](https://docs.3dr.com/autopilots/carrier-boards/r0027-cb2-longy) | Thin form factor for space-constrained builds |
|
||||
| [CB3 FPV](https://docs.3dr.com/autopilots/carrier-boards/r0033-cb3-fpv) | Optimized for FPV platforms |
|
||||
| [CB4 Wing](https://docs.3dr.com/autopilots/carrier-boards/r0036-cb4-wing) | Fixed-wing and VTOL applications |
|
||||
| [CN1 Prototyping Board](https://docs.3dr.com/autopilots/carrier-boards/r0037-cn1-prototyping-board) | Full signal access for development |
|
||||
| [CN1 to CZ OEM Adapter](https://docs.3dr.com/autopilots/carrier-boards/r0034-cn1-to-czoem-adapter) | Adapter for Control Zero OEM carrier boards |
|
||||
| Материнська плата | Опис |
|
||||
| ---------------------------------------------------------------------------------------------------- | --------------------------------------------- |
|
||||
| [CB1 Cuby](https://docs.3dr.com/autopilots/carrier-boards/r0026-cb1-cuby/) | Compact square form factor |
|
||||
| [CB2 Longy](https://docs.3dr.com/autopilots/carrier-boards/r0027-cb2-longy/) | Thin form factor for space-constrained builds |
|
||||
| [CB3 FPV](https://docs.3dr.com/autopilots/carrier-boards/r0033-cb3-fpv/) | Optimized for FPV platforms |
|
||||
| [CB4 Wing](https://docs.3dr.com/autopilots/carrier-boards/r0036-cb4-wing/) | Fixed-wing and VTOL applications |
|
||||
| [CN1 Prototyping Board](https://docs.3dr.com/autopilots/carrier-boards/r0037-cn1-prototyping-board/) | Full signal access for development |
|
||||
| [CN1 to CZ OEM Adapter](https://docs.3dr.com/autopilots/carrier-boards/r0034-cn1-to-czoem-adapter/) | Adapter for Control Zero OEM carrier boards |
|
||||
|
||||
The image below shows the pinout of the CB2 Longy as a reference for connector layout and signal assignment.
|
||||
|
||||
@@ -134,10 +134,10 @@ The image below shows the pinout of the CB2 Longy as a reference for connector l
|
||||
The [SWD debug port](../debug/swd_debug.md) signals (SWCLK, SWDIO) and BOOT0 are routed through connector **J200** on the Control N1 module.
|
||||
The physical debug interface (connector type, pinout, and location) depends on the carrier board.
|
||||
|
||||
Depending on the carrier board, the debug connector may be a TC2030-compatible pad-of-nails (requires a [Tag-Connect TC2030](https://www.tag-connect.com/product/tc2030-ctx-nl-6-pin-no-legs-cable-for-use-with-cortex-processors) cable) or a 14-pin ARM Cortex JTAG/SWD header (Samtec FTSH-107, 2×7, 1.27 mm pitch).
|
||||
Depending on the carrier board, the debug connector may be a TC2030-compatible pad-of-nails (requires a [Tag-Connect TC2030](https://www.tag-connect.com/product/tc2030-ctx-nl-6-pin-no-legs-cable-with-10-pin-micro-connector-for-cortex-processors) cable) or a 14-pin ARM Cortex JTAG/SWD header (Samtec FTSH-107, 2×7, 1.27 mm pitch).
|
||||
Note that some carrier boards may not expose a debug interface.
|
||||
Refer to your carrier board's documentation for the exact connector location and pinout.
|
||||
|
||||
## Подальша інформація
|
||||
|
||||
- [3DR Control N1 documentation](https://docs.3dr.com/autopilots/control-n1)
|
||||
- [3DR Control N1 documentation](https://docs.3dr.com/autopilots/control-n1/)
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
:::warning
|
||||
PX4 не розробляє цей (або будь-який інший) автопілот.
|
||||
Contact the [manufacturer](https://aedrox.com/) for hardware support.
|
||||
Contact the [manufacturer](https://www.aedrox.com/) for hardware support.
|
||||
:::
|
||||
|
||||
The AEDROXH7 is an STM32H743-based FPV / racing flight controller from AEDROX.
|
||||
|
||||
@@ -23,8 +23,8 @@ See the documentation [Ark Electronics GitBook](https://arkelectron.gitbook.io/a
|
||||
|
||||
## Датчики
|
||||
|
||||
- [Invensense IIM-42653 Industrial IMU](https://invensense.tdk.com/products/smartindustrial/iim-42653/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense IIM-42653 Industrial IMU](https://www.invensense.tdk.com/en-us/products/6-axis/iim-42653)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [ST IIS2MDC Magnetometer](https://www.st.com/en/mems-and-sensors/iis2mdc.html)
|
||||
|
||||
## Мікропроцесор
|
||||
|
||||
@@ -17,12 +17,12 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
|
||||
## Where To Buy {#store}
|
||||
|
||||
Order From [Ark Electronics](https://arkelectron.com/product/arkv6s/) (US)
|
||||
Order From [Ark Electronics](https://arkelectron.com/product/arkv6s-flight-controller/) (US)
|
||||
|
||||
## Датчики
|
||||
|
||||
- [Invensense IIM-42653 Industrial IMU](https://invensense.tdk.com/products/smartindustrial/iim-42653/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Invensense IIM-42653 Industrial IMU](https://www.invensense.tdk.com/en-us/products/6-axis/iim-42653)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [ST IIS2MDC Magnetometer](https://www.st.com/en/mems-and-sensors/iis2mdc.html)
|
||||
|
||||
## Мікропроцесор
|
||||
|
||||
@@ -22,9 +22,9 @@ Order From [Ark Electronics](https://arkelectron.com/product/arkv6x/) (US)
|
||||
|
||||
## Датчики
|
||||
|
||||
- [Dual Invensense ICM-42688-P IMUs](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-42688-p/)
|
||||
- [Invensense IIM-42652 Industrial IMU](https://invensense.tdk.com/products/smartindustrial/iim-42652/)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Dual Invensense ICM-42688-P IMUs](https://www.invensense.tdk.com/en-us/products/6-axis/icm-42688-p)
|
||||
- [Invensense IIM-42652 Industrial IMU](https://www.invensense.tdk.com/en-us/products/6-axis/iim-42652)
|
||||
- [Bosch BMP390 Barometer](https://www.bosch-sensortec.com/en/products/environmental-sensors/pressure-sensors/bmp390/)
|
||||
- [Bosch BMM150 Magnetometer](https://www.bosch-sensortec.com/media/boschsensortec/downloads/datasheets/bst-bmm150-ds001.pdf)
|
||||
|
||||
## Мікропроцесор
|
||||
|
||||
@@ -9,6 +9,8 @@ They are listed because you may be using them in an existing drone, and because
|
||||
- _Drotek DroPix_ (FMUv2) — last published in [PX4 v1.13](https://docs.px4.io/v1.13/en/flight_controller/dropix) <!-- 202603 removed doc -->
|
||||
- _Drotek Pixhawk 3 Pro_ (FMUv4pro) — last published in [PX4 v1.15](https://docs.px4.io/v1.15/en/flight_controller/pixhawk3_pro) <!-- 202603 removed doc -->
|
||||
- _Omnibus F4 SD_ — last published in [PX4 v1.15](https://docs.px4.io/v1.15/en/flight_controller/omnibus_f4_sd) <!-- 202603 removed doc -->
|
||||
- _CUAV V5 nano_ (Manufacturer supported) — last published in [PX4 v1.17](https://docs.px4.io/v1.17/en/flight_controller/cuav_v5_nano) <!-- 202607 removed doc -->
|
||||
- _CUAV V5+_ (Manufacturer supported) — last published in [PX4 v1.17](https://docs.px4.io/v1.17/en/flight_controller/cuav_v5_plus) <!-- 202607 removed doc -->
|
||||
- _CUAV X7_ — last published in [PX4 v1.16](https://docs.px4.io/v1.16/en/flight_controller/cuav_x7) <!-- 202507 removed doc -->
|
||||
- _CUAV v5_ (Pixhawk FMUv5) — last published in [PX4 v1.16](https://docs.px4.io/v1.16/en/flight_controller/cuav_v5) <!-- 202507 removed doc -->
|
||||
- _CUAV Pixhack v3_ (FMUv3) — last published in [PX4 v1.15](https://docs.px4.io/v1.15/en/flight_controller/pixhack_v3) <!-- 202603 removed doc -->
|
||||
|
||||
@@ -30,8 +30,6 @@ This category includes boards that are not fully compliant with the pixhawk stan
|
||||
- [CORVON 743v2](../flight_controller/corvon_743v2.md)
|
||||
- [CORVON v5](../flight_controller/corvon_v5.md)
|
||||
- [CUAV Nora](../flight_controller/cuav_nora.md) (CUAV X7 variant)
|
||||
- [CUAV V5+](../flight_controller/cuav_v5_plus.md) (FMUv5)
|
||||
- [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) (FMUv5)
|
||||
- [CUAV X25 EVO](../flight_controller/cuav_x25-evo.md)
|
||||
- [CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
|
||||
- [CUAV X25 MEGA](../flight_controller/cuav_x25-mega.md)
|
||||
|
||||
@@ -37,7 +37,7 @@ CAN transceivers require a 5 V supply. USB-only power (≈4.5 V after the input
|
||||
|
||||
## Де купити
|
||||
|
||||
Check [CBUnmanned](https://cbunmanned.com) for availability.
|
||||
Check [CBUnmanned](https://www.cbunmanned.com/) for availability.
|
||||
|
||||
## Збірка прошивки
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -27,9 +27,9 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
- F-RAM Cypress MF25V02-G 256-Кбіт неволатильна пам'ять (Flash-пам'ять, яка працює так же швидко, як RAM)
|
||||
|
||||
- Датчики:
|
||||
- [Bosch BMI088](https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi088/) 3-axis accelerometer/gyroscope (internally vibration dampened)
|
||||
- [Invensense ICM-20602](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-20602/) 3-axis accelerometer/gyroscope
|
||||
- [Invensense ICM-20948](https://invensense.tdk.com/products/motion-tracking/9-axis/icm-20948/) 3-axis accelerometer/gyroscope/magnetometer
|
||||
- [Bosch BMI088](https://www.bosch-sensortec.com/en/products/motion-sensors/imus/bmi088/) 3-axis accelerometer/gyroscope (internally vibration dampened)
|
||||
- [Invensense ICM-20602](https://www.invensense.tdk.com/en-us/products/motion-tracking/6-axis/icm-20602) 3-axis accelerometer/gyroscope
|
||||
- [Invensense ICM-20948](https://www.invensense.tdk.com/en-us/products/9-axis/icm-20948) 3-axis accelerometer/gyroscope/magnetometer
|
||||
- Infineon DPS310 barometer - [Discontinued](https://www.infineon.com/products/sensor/pressure-sensors/pressure-sensors-for-iot) (So smooth and NO more light sensitivity)
|
||||
|
||||
- Інтерфейси:
|
||||
|
||||
@@ -80,7 +80,7 @@ PX4 _developers_ need to know the FMU version of their board, as this is require
|
||||
Більше RAM.
|
||||
Більше CAN шин.
|
||||
Набагато більш налаштовуваний.
|
||||
([Pixhawk 4](../flight_controller/pixhawk4.md),[CUAV v5](../flight_controller/cuav_v5.md),[CUAV V5+](../flight_controller/cuav_v5_plus.md),[CUAV V5 nano](../flight_controller/cuav_v5_nano.md))
|
||||
([Pixhawk 4 (Discontinued)](../flight_controller/pixhawk4.md),[CUAV v5 (Discontinued)](../flight_controller/cuav_v5.md), [CUAV V5+ (Discontinued)](../flight_controller/cuav_v5_plus.md),[CUAV V5 nano (Discontinued)](../flight_controller/cuav_v5_nano.md))
|
||||
- **FMUv5X:** New processor (F7).
|
||||
Набагато швидший, модульний дизайн.
|
||||
Більш надійний.
|
||||
|
||||
@@ -13,20 +13,20 @@ Ubuntu Server on RPi 4B consumes a lot of current and generates a lot of heat.
|
||||
|
||||
#### armhf
|
||||
|
||||
- [Ubuntu Server 18.04.5 for RPi2](https://cdimage.ubuntu.com/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi2.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi3](https://cdimage.ubuntu.com/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi3.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi4](https://cdimage.ubuntu.com/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi4.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi2](https://cdimage.ubuntu.com/ubuntu/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi2.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi3](https://cdimage.ubuntu.com/ubuntu/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi3.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi4](https://cdimage.ubuntu.com/ubuntu/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-armhf+raspi4.img.xz)
|
||||
- [Ubuntu Server 20.04.1 for RPi 2/3/4](https://old-releases.ubuntu.com/releases/focal/ubuntu-20.04.2-preinstalled-server-arm64+raspi.img.xz)
|
||||
|
||||
#### arm64
|
||||
|
||||
- [Ubuntu Server 18.04.5 for RPi3](https://cdimage.ubuntu.com/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-arm64+raspi3.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi4](https://cdimage.ubuntu.com/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi3](https://cdimage.ubuntu.com/ubuntu/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-arm64+raspi3.img.xz)
|
||||
- [Ubuntu Server 18.04.5 for RPi4](https://cdimage.ubuntu.com/ubuntu/releases/18.04.5/release/ubuntu-18.04.5-preinstalled-server-arm64+raspi4.img.xz)
|
||||
- [Ubuntu Server 20.04.1 for RPi 3/4](https://old-releases.ubuntu.com/releases/focal/ubuntu-20.04.2-preinstalled-server-arm64+raspi.img.xz)
|
||||
|
||||
#### Найновіша ОС
|
||||
|
||||
Please refer to official [cdimage](https://cdimage.ubuntu.com/releases/) page for any new updates.
|
||||
Please refer to official [cdimage](https://cdimage.ubuntu.com/ubuntu/releases/) page for any new updates.
|
||||
|
||||
### Перший запуск
|
||||
|
||||
|
||||
@@ -363,13 +363,12 @@ Rover MAVLink setpoints are gated by the MAVLink parameter [MAV_FWDEXTSP](../adv
|
||||
|
||||
_Offboard mode_ is affected by the following parameters:
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="COM_OF_LOSS_T"></a>[COM_OF_LOSS_T](../advanced_config/parameter_reference.md#COM_OF_LOSS_T) | Time-out (in seconds) to wait when offboard connection is lost before triggering offboard lost failsafe (`COM_OBL_RC_ACT`) |
|
||||
| <a id="COM_OBL_RC_ACT"></a>[COM_OBL_RC_ACT](../advanced_config/parameter_reference.md#COM_OBL_RC_ACT) | Flight mode to switch to if offboard control is lost. |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). This is not enabled for offboard mode by default. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| <a id="COM_RCL_EXCEPT"></a>[COM_RCL_EXCEPT](../advanced_config/parameter_reference.md#COM_RCL_EXCEPT) | Specify modes in which RC loss is ignored and the failsafe action not triggered. Set bit `2` to ignore RC loss in Offboard mode. |
|
||||
| Parameter | Опис |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="COM_OF_LOSS_T"></a>[COM_OF_LOSS_T](../advanced_config/parameter_reference.md#COM_OF_LOSS_T) | Time-out (in seconds) to wait when offboard connection is lost before triggering offboard lost failsafe (`COM_OBL_RC_ACT`) |
|
||||
| <a id="COM_OBL_RC_ACT"></a>[COM_OBL_RC_ACT](../advanced_config/parameter_reference.md#COM_OBL_RC_ACT) | Flight mode to switch to if offboard control is lost. |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
| <a id="COM_RCL_EXCEPT"></a>[COM_RCL_EXCEPT](../advanced_config/parameter_reference.md#COM_RCL_EXCEPT) | Specify modes in which RC loss is ignored and the failsafe action not triggered. Set bit `2` to ignore RC loss in Offboard mode. |
|
||||
|
||||
## Developer Resources
|
||||
|
||||
|
||||
@@ -18,8 +18,8 @@ The _Return_ flight mode is used to _fly a vehicle to safety_ on an unobstructed
|
||||
- Літаючі транспортні засоби перейдуть в режим аварійної безпеки, якщо втратять оцінку положення.
|
||||
- Режим вимагає встановленої домашньої позиції.
|
||||
- Mode prevents arming (vehicle cannot be armed while this mode is selected).
|
||||
- Перемикачі керування RC можуть використовуватися для зміни режимів польоту на будь-якому транспортному засобі.
|
||||
- RC stick movement in a multicopter (or VTOL in multicopter mode) will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- RC switches can be used to change flight modes on any vehicle.
|
||||
- Stick movement in a multicopter (or VTOL in hover) will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- VTOL повернеться як MC або FW на основі свого режиму в точці, коли режим повернення було запущено.
|
||||
У режимі багтороторного літання він буде дотримуватися параметрів багтороторного літання, таких як "конус" посадки.
|
||||
У режимі ФПВ він буде дотримуватися параметрів фіксованого крила (ігнорувати конус), але, якщо не використовується місійна посадка, перейде в режим багтороторного літання та посадиться у пункт призначення після нависання на висоті спуску.
|
||||
@@ -46,10 +46,10 @@ PX4 provides four alternative approaches for finding an unobstructed path to a s
|
||||
|
||||
На високому рівні є:
|
||||
|
||||
- [Home/rally point return](#home_return) (`RTL_TYPE=0`): Ascend to safe altitude and return via a direct path to the closest rally point or home location.
|
||||
- [Mission landing/rally point return](#mission-landing-rally-point-return-type-rtl-type-1) (`RTL_TYPE=1`): Ascend to a safe altitude, fly direct to the closest destination _other than home_: rally point or start of mission landing.
|
||||
- [Home/rally point return](#rtl_type_0) (`RTL_TYPE=0`): Ascend to safe altitude and return via a direct path to the closest rally point or home location.
|
||||
- [Mission landing/rally point return](#rtl_type_1) (`RTL_TYPE=1`): Ascend to a safe altitude, fly direct to the closest destination _other than home_: rally point or start of mission landing.
|
||||
Якщо не визначено пунктів посадки або збору місії, поверніться додому прямим шляхом.
|
||||
- [Mission path return](#mission-path-return-type-rtl-type-2) (`RTL_TYPE=2`): Use mission path and fast-continue to mission landing (if defined).
|
||||
- [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.
|
||||
@@ -57,16 +57,14 @@ PX4 provides four alternative approaches for finding an unobstructed path to a s
|
||||
|
||||
Більш детальні пояснення щодо кожного з типів наведено в наступних розділах.
|
||||
|
||||
<a id="home_return"></a>
|
||||
|
||||
### Тип повернення додому/точка збору (RTL_TYPE=0)
|
||||
### Home/Rally Point Return Type (RTL_TYPE=0) {#rtl_type_0}
|
||||
|
||||
This is the default return type for a [multicopter](../flight_modes_mc/return.md) (see topic for more information).
|
||||
|
||||
У цьому типі повернення транспортний засіб:
|
||||
|
||||
- Ascends to a safe [minimum return altitude](#minimum-return-altitude) (above any expected obstacles).
|
||||
- Летить прямою траєкторією до вихідної позиції або точки збору (залежно від того, що ближче)
|
||||
- Flies to the home position or a rally point (whichever is closest), preferring a [geofence-aware](#geofence_awareness) horizontal path over a direct path where possible.
|
||||
- On [arrival](#loiter-landing-at-destination) descends to "descent altitude" and waits for a configurable time.
|
||||
Цей час можна використати для розгортання шасі для посадки.
|
||||
- Lands or waits (this depends on landing parameters),
|
||||
@@ -77,7 +75,7 @@ This is the default return type for a [multicopter](../flight_modes_mc/return.md
|
||||
If no rally points are defined, this is the same as a _Return to Launch_ (RTL)/_Return to Home_ (RTH).
|
||||
:::
|
||||
|
||||
### Тип посадки/повернення точки збору (RTL_TYPE=1)
|
||||
### Mission Landing/Rally Point Return Type (RTL_TYPE=1) {#rtl_type_1}
|
||||
|
||||
This is the default return type for a [fixed-wing](../flight_modes_fw/return.md) or [VTOL](../flight_modes_vtol/return.md) vehicle (see topics for more information).
|
||||
|
||||
@@ -85,7 +83,7 @@ This is the default return type for a [fixed-wing](../flight_modes_fw/return.md)
|
||||
|
||||
- Ascends to a safe [minimum return altitude](#minimum-return-altitude) (above any expected obstacles) if needed.
|
||||
Транспортний засіб підтримує свою початкову висоту, якщо вона вище, ніж мінімальна висота повернення.
|
||||
- Flies via direct constant-altitude path to a rally point or the start of a [mission landing pattern](#mission-landing-pattern) (whichever is closest).
|
||||
- Flies at constant-altitude to a rally point or the start of a [mission landing pattern](#mission-landing-pattern) (whichever is closest), preferring a [geofence-aware](#geofence_awareness) horizontal path over a direct path where possible.
|
||||
Якщо місця посадки або збору не визначені, транспортний засіб повертається додому прямим шляхом.
|
||||
- Якщо призначенням є місійний маршрут посадки, апарат буде дотримуватися маршруту для посадки.
|
||||
- If the destination is a rally point or home it will [land or wait](#loiter-landing-at-destination) at descent altitude (depending on landing parameters).
|
||||
@@ -100,7 +98,7 @@ This is the default return type for a [fixed-wing](../flight_modes_fw/return.md)
|
||||
Fixed wing vehicles commonly also set [MIS_TKO_LAND_REQ](#MIS_TKO_LAND_REQ) to _require_ a mission landing pattern.
|
||||
:::
|
||||
|
||||
### Тип повернення маршруту завдання (RTL_TYPE=2)
|
||||
### Mission Path Return Type (RTL_TYPE=2) {#rtl_type_2}
|
||||
|
||||
This return type uses the mission (if defined) to provide a safe return _path_, and the [mission landing pattern](#mission-landing-pattern) (if defined) to provide landing behaviour.
|
||||
If there is a mission but no mission landing pattern, the mission is flown _in reverse_.
|
||||
@@ -110,6 +108,10 @@ If there is a mission but no mission landing pattern, the mission is flown _in r
|
||||
The behaviour is fairly complex because it depends on the flight mode, and whether a mission and mission landing are defined.
|
||||
:::
|
||||
|
||||
:::warning
|
||||
This return type does have [geofence awareness](#geofence_awareness) (at any stage).
|
||||
:::
|
||||
|
||||
Mission _with_ landing pattern:
|
||||
|
||||
- **Mission mode:**
|
||||
@@ -145,7 +147,7 @@ For `RTL_TYPE=4`, PX4 currently chooses between continuing to a mission landing
|
||||
This is only an approximation of the flown path length, because the number if mission items is not indicative of the distance remaining and non-position items are also counted.
|
||||
:::
|
||||
|
||||
### Тип повернення додому/точка збору (RTL_TYPE=3)
|
||||
### Closest Safe Destination Return Type (RTL_TYPE=3) {#rtl_type_3}
|
||||
|
||||
У цьому типі повернення транспортний засіб:
|
||||
|
||||
@@ -156,12 +158,62 @@ This is only an approximation of the flown path length, because the number if mi
|
||||
За замовчуванням багатороторні квадрокоптери або вертикально-взлітно-посадкові літаки в режимі багатороторника приземлюються, а фіксованокрилі літаки обертаються на висоті спуску.
|
||||
ВТОЛ у режимі FW вирівнює свою орієнтацію на точку призначення, переходить у режим МБ і потім приземлюється.
|
||||
|
||||
## 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.
|
||||
If no geofence is set, the vehicle flies a direct path to the destination.
|
||||
|
||||
While the return mode is inactive, the autopilot constantly recalculates a [shortest horizontal return path](#shortest-path-calculation) that does not enter any exclusion zones and does not exit any inclusion zones.
|
||||
|
||||
If the return mode is triggered while the vehicle is violating any geofence, then the vehicle will first fly directly to the most recent recorded location at which it was not violating the geofence.
|
||||
If no such point exists, or if the autopilot fails to plan a feasible path (e.g. the destination is located in an exclusion zone), then the vehicle falls back to flying directly to the destination.
|
||||
|
||||
:::info
|
||||
The estimated time for return is based on the current shortest horizontal path to the destination and may change if the geofence is updated.
|
||||
:::
|
||||
|
||||
:::warning
|
||||
Geofence awareness currently supports a maximum of 99 polygon vertices in total (circles count as 8 vertices each).
|
||||
If this limit is exceeded, the autopilot falls back to a direct path as described above.
|
||||
:::
|
||||
|
||||
:::warning
|
||||
There is no absolute guarantee that the vehicle will not breach a geofence on the return path.
|
||||
Things like path tracking error, wind and other disturbances may cause temporary violation of the geofence.
|
||||
It is therefore very important to consider this possibility and especially to review the geofence breach action (e.g. [GF_ACTION](../advanced_config/parameter_reference.md#GF_ACTION)).
|
||||
:::
|
||||
|
||||
### RTL-types with Geofence-Awareness
|
||||
|
||||
The following table shows which return types currently support geofence awareness:
|
||||
|
||||
| Return Type (RTL_TYPE) | Geofence Awareness |
|
||||
| -------------------------------------------------------------- | ------------------ |
|
||||
| 0 (home/rally point) | Так |
|
||||
| 1 (mission landing) | Так |
|
||||
| 2 (mission path) | Ні |
|
||||
| 3 (closest safe dest.) | Так |
|
||||
| 4 (mission path) | Ні |
|
||||
| 5 (rally point only) | Так |
|
||||
|
||||
### Shortest-Path Calculation
|
||||
|
||||
For the construction of the shortest path between the starting location and the destination, the autopilot uses the vertices of the geofence polygons as intermediate waypoints.
|
||||
In order to avoid the path being too close to the polygon boundaries, the autopilot constructs a corresponding set of polygons, which are either enlarged (for exclusion zones) or shrunk (for inclusion zones).
|
||||
The margin in both images below is 10m.
|
||||
The figures below show an exclusion zone and an inclusion zone.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Мінімальна висота повернення
|
||||
|
||||
For most [return types](#return_types) a vehicle will ascend to a _minimum safe altitude_ before returning (unless already above that altitude), in order to avoid any obstacles between it and the destination.
|
||||
|
||||
:::info
|
||||
The exception is when executing a [mission path return](#mission-path-return-type-rtl-type-2) from _within a mission_.
|
||||
The exception is when executing a [mission path return](#rtl_type_2) from _within a mission_.
|
||||
У цьому випадку транспортний засіб слідує точкам маршруту місії, які ми припускаємо, що сплановані таким чином, щоб уникнути будь-яких перешкод.
|
||||
:::
|
||||
|
||||
@@ -206,7 +258,7 @@ If `RTL_LAND_DELAY=-1` it will loiter indefinitely.
|
||||
This consists of a [MAV_CMD_DO_LAND_START](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_LAND_START), one or more position waypoints, and a [MAV_CMD_NAV_LAND](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_LAND) (or [MAV_CMD_NAV_VTOL_LAND](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_VTOL_LAND) for a VTOL Vehicle).
|
||||
|
||||
Landing patterns defined in missions are the safest way to automatically land a _fixed-wing_ vehicle on PX4.
|
||||
For this reason fixed-wing vehicles are configured to use [Mission landing/really point return](#mission-landing-rally-point-return-type-rtl-type-1) by default.
|
||||
For this reason fixed-wing vehicles are configured to use [Mission landing/really point return](#rtl_type_1) by default.
|
||||
|
||||
## Параметри
|
||||
|
||||
@@ -221,7 +273,6 @@ The RTL parameters are listed in [Parameter Reference > Return Mode](../advanced
|
||||
| <a id="RTL_MIN_DIST"></a>[RTL_MIN_DIST](../advanced_config/parameter_reference.md#RTL_MIN_DIST) | Within this distance from the return destination, the return altitude is calculated from the "cone" rather than directly from `RTL_RETURN_ALT`. |
|
||||
| <a id="RTL_CONE_ANG"></a>[RTL_CONE_ANG](../advanced_config/parameter_reference.md#RTL_CONE_ANG) | Половина кута конуса, який визначає висоту повернення транспортного засобу RTL. Values (in degrees): `0`, `25`, `45`, `65`, `80`, `90`. Note that `0` is "no cone" (always return at `RTL_RETURN_ALT` or higher), while `90` indicates an almost vertical cone, so the vehicle generally returns at its current altitude when close to the destination. The return altitude may still be constrained to avoid flying too low while approaching the destination. |
|
||||
| <a id="RTL_APPR_FORCE"></a>[RTL_APPR_FORCE](../advanced_config/parameter_reference.md#RTL_APPR_FORCE) | [VTOL FW only] If set, home or rally-point RTL destinations are only considered when a valid VTOL approach loiter is defined for that landing location. Mission landing patterns are unaffected. |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md) (unless prevented by the active failsafe state). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
| <a id="RTL_LOITER_RAD"></a>[RTL_LOITER_RAD](../advanced_config/parameter_reference.md#RTL_LOITER_RAD) | [Тільки фіксоване крило] Радіус круга обертання (у значенні [RTL_LAND_DELAY](#RTL_LAND_DELAY)). |
|
||||
| <a id="MIS_TKO_LAND_REQ"></a>[MIS_TKO_LAND_REQ](../advanced_config/parameter_reference.md#MIS_TKO_LAND_REQ) | Вказує, чи _необхідний_ місійний маршрут посадки або зльоту. Зазвичай літаки з фіксованим крилом встановлюють це для вимоги до посадкового маршруту, але VTOL - ні. |
|
||||
|
||||
@@ -4,10 +4,10 @@
|
||||
|
||||
Режим польоту _Return_ використовується для _повернення транспортного засобу до безпеки_ по вільному шляху до безпечного пункту призначення, де він може приземлитися.
|
||||
|
||||
Літаки з фіксованим крилом за замовчуванням використовують тип повернення до призначення [місії посадки/точка збору](../flight_modes/return.md#mission-landing-rally-point-return-type-rtl-type-1), і завжди передбачається, що у них буде завдання з шаблоном посадки.
|
||||
Fixed-wing vehicles use the [Mission Landing/Rally Point](../flight_modes/return.md#rtl_type_1) return type by default, and are expected to always have a mission with a landing pattern.
|
||||
З цією конфігурацією режим повернення зумовлює підняття транспортного засобу на мінімальну безпечну висоту над перешкодами (якщо потрібно), польот до початку схеми посадки, визначеної у плані місії, і далі слідує за нею для посадки.
|
||||
|
||||
Фіксоване крило підтримує [інші типи повернення PX4](../flight_modes/return.md#return-types-rtl-type), включаючи повернення додому/радільної точки, маршрут місії та найближче безпечне місце призначення.
|
||||
Fixed-wing supports the [other PX4 return types](../flight_modes/return.md#return_types), including home/rally point return, mission path and closest safe destination.
|
||||
За замовчуванням рекомендується використовувати цей тип.
|
||||
|
||||
::: info
|
||||
@@ -33,7 +33,8 @@
|
||||
- Піднімається на безпечну мінімальну висоту повернення, визначену за допомогою [RTL_RETURN_ALT](#RTL_RETURN_ALT) (безпечно вище будь-яких очікуваних перешкод).
|
||||
Транспортний засіб підтримує свою початкову висоту, якщо вона вище, ніж мінімальна висота повернення.
|
||||
Зверніть увагу, що висоту повернення не можна налаштувати, використовуючи параметр "cone" в літаках з фіксованим крилом.
|
||||
- Летить прямим шляхом на постійній висоті до призначення, яким буде найближча з точки старту місійного маршруту посадки та будь-яка точка збору, або домашня локація, якщо місійний маршрут посадки або точки збору не визначені.
|
||||
- Flies via a constant-altitude path to the destination, which will be the closest of the start of a _mission landing pattern_ and any rally point, or the home location if no mission landing pattern or rally points are defined.
|
||||
The path is chosen to be the shortest horizontal [geofence-aware path](../flight_modes/return.md#geofence_awareness).
|
||||
- Якщо призначення - це шаблон посадки місії, воно буде слідувати за шаблоном для посадки.
|
||||
- Якщо місце призначення - це точка ралі або дім, воно спуститься на висоту спуску, а потім обережно почекає або приземлиться (в залежності від параметрів посадки).
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ _Hold mode_ can be used to pause a mission or to help you regain control of a ve
|
||||
- Роззброєні транспортні засоби можуть переключатися в режим без дійсної оцінки позиції, але не можуть озброюватися.
|
||||
- Режим вимагає, щоб швидкість вітру та час польоту були в межах допустимих значень (вказано через параметри).
|
||||
- Перемикачі керування RC можуть використовуватися для зміни режимів польоту на будь-якому транспортному засобі.
|
||||
- RC stick movement will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- Stick movement will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
|
||||
<!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/commander/ModeUtil/mode_requirements.cpp -->
|
||||
|
||||
@@ -29,17 +29,17 @@ _Hold mode_ can be used to pause a mission or to help you regain control of a ve
|
||||
The vehicle stops and hovers, maintaining its position and altitude.
|
||||
The vehicle will first ascend to [NAV_MIN_LTR_ALT](#NAV_MIN_LTR_ALT) if the mode is engaged below this altitude.
|
||||
|
||||
RC stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#COM_RC_OVERRIDE)).
|
||||
Stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#MAN_OVERRIDE_SPD)).
|
||||
|
||||
### Параметри
|
||||
|
||||
Поведінку режиму утримання можна налаштувати за допомогою наведених нижче параметрів.
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="NAV_MIN_LTR_ALT"></a>[NAV_MIN_LTR_ALT](../advanced_config/parameter_reference.md#NAV_MIN_LTR_ALT) | Це мінімальна висота над домашньою позицією, яку система завжди буде дотримуватися в режимі утримання, якщо перемикається в цей режим без вказівки висоти (наприклад, за допомогою перемикача на дистанційному керуванні). |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="NAV_MIN_LTR_ALT"></a>[NAV_MIN_LTR_ALT](../advanced_config/parameter_reference.md#NAV_MIN_LTR_ALT) | Це мінімальна висота над домашньою позицією, яку система завжди буде дотримуватися в режимі утримання, якщо перемикається в цей режим без вказівки висоти (наприклад, за допомогою перемикача на дистанційному керуванні). |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
| <a id="MPC_AUTO_NUDGING"></a>[MPC_AUTO_NUDGING](../advanced_config/parameter_reference.md#MPC_AUTO_NUDGING) | Bitmask enabling stick nudging in Auto modes (multicopter). Bit 0 (yaw nudging) lets the yaw stick nudge heading in Hold, held when the stick is released; switching flight mode clears the held heading. Requires stick override to be disabled ([MAN_OVERRIDE_SPD](#MAN_OVERRIDE_SPD) = -1). |
|
||||
|
||||
<!-- Code for this here: https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/navigator/loiter.cpp#L61 -->
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@
|
||||
- Літаючі транспортні засоби перейдуть в режим аварійної безпеки, якщо втратять оцінку положення.
|
||||
- Mode prevents arming (vehicle cannot be armed while this mode is selected).
|
||||
- Перемикачі керування RC можуть використовуватися для зміни режимів польоту на будь-якому транспортному засобі.
|
||||
- RC stick movement in a multicopter (or VTOL in multicopter mode) will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- Stick movement in a multicopter (or VTOL in hover) will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- The mode can be triggered using the [MAV_CMD_NAV_LAND](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_LAND) MAVLink command, or by explicitly switching to Land mode.
|
||||
|
||||
<!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/commander/ModeUtil/mode_requirements.cpp -->
|
||||
@@ -25,18 +25,18 @@
|
||||
Транспортний засіб приземлиться в місці, в якому був активований режим.
|
||||
The vehicle descends at the rate specified in [MPC_LAND_SPEED](#MPC_LAND_SPEED) and will disarm after landing (by [default](#COM_DISARM_LAND)).
|
||||
|
||||
RC stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#COM_RC_OVERRIDE)).
|
||||
Stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#MAN_OVERRIDE_SPD)).
|
||||
|
||||
### Параметри
|
||||
|
||||
Поведінку режиму приземлення можна налаштувати за допомогою наведених нижче параметрів.
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="MPC_LAND_SPEED"></a>[MPC_LAND_SPEED](../advanced_config/parameter_reference.md#MPC_LAND_SPEED) | Швидкість спуску під час посадки. Це повинно бути тримано досить низько, оскільки ґрунтові умови не відомі. |
|
||||
| <a id="COM_DISARM_LAND"></a>[COM_DISARM_LAND](../advanced_config/parameter_reference.md#COM_DISARM_LAND) | Тайм-аут для автоматичного роззброєння після посадки, у секундах. Якщо встановлено на -1, транспортний засіб не роззброюється при посадці. |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="MPC_LAND_SPEED"></a>[MPC_LAND_SPEED](../advanced_config/parameter_reference.md#MPC_LAND_SPEED) | Швидкість спуску під час посадки. Це повинно бути тримано досить низько, оскільки ґрунтові умови не відомі. |
|
||||
| <a id="COM_DISARM_LAND"></a>[COM_DISARM_LAND](../advanced_config/parameter_reference.md#COM_DISARM_LAND) | Тайм-аут для автоматичного роззброєння після посадки, у секундах. Якщо встановлено на -1, транспортний засіб не роззброюється при посадці. |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
| <a id="MPC_AUTO_NUDGING"></a>[MPC_AUTO_NUDGING](../advanced_config/parameter_reference.md#MPC_AUTO_NUDGING) | Bitmask enabling stick nudging in Auto modes (multicopter). Bit 0 (yaw nudging) lets the yaw stick nudge heading during landing. Bit 1 (land nudging) additionally lets the pitch/roll sticks move the vehicle horizontally (within [MPC_LAND_RADIUS](#MPC_LAND_RADIUS)), the throttle stick amend the descent speed, and the yaw stick rotate the heading. Requires stick override to be disabled ([MAN_OVERRIDE_SPD](#MAN_OVERRIDE_SPD) = -1). |
|
||||
|
||||
## Дивіться також
|
||||
|
||||
|
||||
@@ -11,8 +11,9 @@ _Режим місії_ змушує транспортний засіб вик
|
||||
- Транспортний засіб повинен бути озброєний перед тим, як цей режим може бути активований.
|
||||
- Цей режим є автоматичним - для керування автомобілем не потрібно втручання користувача.
|
||||
- Перемикачі керування RC можуть використовуватися для зміни режимів польоту на будь-якому транспортному засобі.
|
||||
- RC stick movement will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
Це справжнє для багтороторів і ВПС у режимі КУ.
|
||||
- Stick movement will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
This is true for multicopters and VTOL in hover.
|
||||
- The yaw stick can optionally nudge vehicle heading during the mission without changing mode (see [MPC_AUTO_NUDGING](#MPC_AUTO_NUDGING)).
|
||||
|
||||
:::
|
||||
|
||||
@@ -110,11 +111,11 @@ _QGroundControl_ надає додаткову підтримку обробки
|
||||
|
||||
Загальні параметри:
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="NAV_RCL_ACT"></a>[NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) | Режим аварійного відновлення зв'язку RC (що робить транспортний засіб, якщо втрачає зв'язок RC) - наприклад, увійти в режим утримання, режим повернення, завершити тощо. |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Контролює переміщення джойстика на мультикоптері (або конвертоплані у режимі MC) повертає керування пілоту в [Режим положення](../flight_modes_mc/position.md). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="NAV_RCL_ACT"></a>[NAV_RCL_ACT](../advanced_config/parameter_reference.md#NAV_RCL_ACT) | Режим аварійного відновлення зв'язку RC (що робить транспортний засіб, якщо втрачає зв'язок RC) - наприклад, увійти в режим утримання, режим повернення, завершити тощо. |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
| <a id="MPC_AUTO_NUDGING"></a>[MPC_AUTO_NUDGING](../advanced_config/parameter_reference.md#MPC_AUTO_NUDGING) | Bitmask enabling stick nudging in Auto modes (multicopter). Bit 0 (yaw nudging) lets the yaw stick nudge heading without switching modes; the heading is held when the stick is released. Switching flight mode (e.g. to Hold and back) clears the held heading and returns yaw to the mode default. Requires stick override to be disabled ([MAN_OVERRIDE_SPD](#MAN_OVERRIDE_SPD) = -1). |
|
||||
|
||||
Параметри, пов'язані з [перевірками можливостей місії](#mission-feasibility-checks):
|
||||
|
||||
|
||||
@@ -4,11 +4,11 @@
|
||||
|
||||
Режим польоту _Return_ використовується для _повернення транспортного засобу до безпеки_ по вільному шляху до безпечного пункту призначення, де він може приземлитися.
|
||||
|
||||
Мультикоптери за замовчуванням використовують тип повертання до [домашньої/ралійної точки](../flight_modes/return.md#home-rally-point-return-type-rtl-type-0).
|
||||
У цьому типі повернення транспортні засоби підіймаються на безпечну висоту над перешкодами, якщо потрібно, прямують безпосередньо до найближчої безпечної точки посадки (точки збору або домашньої позиції), опускаються на "висоту опускання", надвіюються коротко, а потім сідають.
|
||||
Multicopters use a [home/rally point return type](../flight_modes/return.md#home_return) by default.
|
||||
In this return type vehicles ascend to a safe altitude above obstructions if needed, fly to the closest safe landing point (a rally point or the home position) via the shortest horizontal [geofence-aware path](../flight_modes/return.md#geofence_awareness), descend to the "descent altitude", wait briefly, and then land.
|
||||
Висота повернення, висота зниження та затримка при посадці зазвичай встановлені на консервативні "безпечні" значення, але їх можна змінити за потреби.
|
||||
|
||||
Multicopter підтримує [інші типи повернення PX4](../flight_modes/return.md#return-types-rtl-type), включаючи посадку місії, маршрут місії і найближче безпечне місце призначення.
|
||||
Multicopter supports the [other PX4 return types](../flight_modes/return.md#return_types), including mission landing, mission path and closest safe destination.
|
||||
За замовчуванням рекомендується використовувати цей тип.
|
||||
|
||||
::: info
|
||||
@@ -20,7 +20,7 @@ Multicopter підтримує [інші типи повернення PX4](../f
|
||||
- Режим вимагає встановленої домашньої позиції.
|
||||
- Mode prevents arming (vehicle cannot be armed while this mode is selected).
|
||||
- Перемикачі керування RC можуть використовуватися для зміни режимів польоту на будь-якому транспортному засобі.
|
||||
- RC stick movement will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- Stick movement will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
|
||||
<!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/commander/ModeUtil/mode_requirements.cpp -->
|
||||
|
||||
@@ -28,12 +28,13 @@ Multicopter підтримує [інші типи повернення PX4](../f
|
||||
|
||||
## Технічний підсумок
|
||||
|
||||
Multicopters use the [home/rally point return type](../flight_modes/return.md#home-rally-point-return-type-rtl-type-0) by default ([RTL_TYPE=0](../advanced_config/parameter_reference.md#RTL_TYPE)).
|
||||
Multicopters use the [home/rally point return type](../flight_modes/return.md#home_return) by default. ([RTL_TYPE=0](../advanced_config/parameter_reference.md#RTL_TYPE)).
|
||||
У цьому типі повернення вертольот:
|
||||
|
||||
- Піднімається на [мінімальну висоту повернення](#minimum-return-altitude) (безпечно вище будь-яких очікуваних перешкод).
|
||||
Транспортний засіб підтримує свою початкову висоту, якщо вона вище, ніж мінімальна висота повернення.
|
||||
- Летить за допомогою прямого постійного шляху на безпечну точку посадки, яка буде найближчою із всіх ралі-точок та домашньої позиції.
|
||||
- Flies via a constant-altitude path to the safe landing point, which will be the nearest of any rally points and the home position.
|
||||
The path is chosen to be the shortest horizontal [geofence-aware path](../flight_modes/return.md#geofence_awareness).
|
||||
- Прибуваючи до пункту призначення, він швидко спускається на «висоту спуску» ([RTL_DESCEND_ALT](#RTL_DESCEND_ALT)).
|
||||
- Він чекає протягом налаштованого часу ([RTL_LAND_DELAY](#RTL_LAND_DELAY)), який може бути використаний для розгортання шасі посадки.
|
||||
- Потім сідає на землю.
|
||||
@@ -52,7 +53,7 @@ The cone affects the minimum return altitude if return mode is triggered within
|
||||
Inside the cone, the vehicle returns at an altitude calculated from the cone geometry, up to `RTL_RETURN_ALT`.
|
||||
After reaching the destination, it descends to `RTL_DESCEND_ALT` (if above that altitude) before landing or loitering.
|
||||
|
||||
Для отримання додаткової інформації про цей тип повернення див. [Тип повернення додому/району збору (RTL_TYPE=0)](../flight_modes/return.md#home-rally-point-return-type-rtl-type-0)
|
||||
For more information on this return type see [Home/Rally Point Return Type (RTL_TYPE=0)](../flight_modes/return.md#home_return)
|
||||
|
||||
## Параметри
|
||||
|
||||
@@ -60,15 +61,14 @@ After reaching the destination, it descends to `RTL_DESCEND_ALT` (if above that
|
||||
|
||||
Параметри, які є важливими для мультикоптерів (припускаючи, що [RTL_TYPE](../advanced_config/parameter_reference.md#RTL_TYPE) встановлено на 0), перераховані нижче.
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="RTL_RETURN_ALT"></a>[RTL_RETURN_ALT](../advanced_config/parameter_reference.md#RTL_RETURN_ALT) | Повернути висоту в метрах (за замовчуванням: 60м), коли [RTL_CONE_ANG](../advanced_config/parameter_reference.md#RTL_CONE_ANG) дорівнює 0. Якщо вже вище цієї величини, транспортний засіб повернеться на поточну висоту. |
|
||||
| <a id="RTL_DESCEND_ALT"></a>[RTL_DESCEND_ALT](../advanced_config/parameter_reference.md#RTL_DESCEND_ALT) | Altitude above the destination used for the final descent before landing or loitering (default: 30m). |
|
||||
| <a id="RTL_LAND_DELAY"></a>[RTL_LAND_DELAY](../advanced_config/parameter_reference.md#RTL_LAND_DELAY) | Time to hover at `RTL_DESCEND_ALT` before landing (default: 0.5s) - by default this period is short so that the vehicle will simply slow and then land immediately. Якщо встановлено значення -1, система буде кружляти на висоті `RTL_DESCEND_ALT` замість посадки. Затримка надається для того, щоб ви могли налаштувати час для розгортання шасі для посадки (автоматично спрацьовує). |
|
||||
| <a id="RTL_MIN_DIST"></a>[RTL_MIN_DIST](../advanced_config/parameter_reference.md#RTL_MIN_DIST) | Within this distance from the home position, the return altitude is calculated from the "cone" rather than directly from `RTL_RETURN_ALT`. |
|
||||
| <a id="RTL_CONE_ANG"></a>[RTL_CONE_ANG](../advanced_config/parameter_reference.md#RTL_CONE_ANG) | Половина кута конуса, який визначає висоту повернення транспортного засобу RTL. Values (in degrees): `0`, `25`, `45`, `65`, `80`, `90`. Note that `0` is "no cone" (always return at `RTL_RETURN_ALT` or higher), while `90` indicates an almost vertical cone, so the vehicle generally returns at its current altitude when close to the destination. The return altitude may still be constrained to avoid flying too low while approaching the destination. |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md) (unless prevented by the active failsafe state). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="RTL_RETURN_ALT"></a>[RTL_RETURN_ALT](../advanced_config/parameter_reference.md#RTL_RETURN_ALT) | Повернути висоту в метрах (за замовчуванням: 60м), коли [RTL_CONE_ANG](../advanced_config/parameter_reference.md#RTL_CONE_ANG) дорівнює 0. Якщо вже вище цієї величини, транспортний засіб повернеться на поточну висоту. |
|
||||
| <a id="RTL_DESCEND_ALT"></a>[RTL_DESCEND_ALT](../advanced_config/parameter_reference.md#RTL_DESCEND_ALT) | Altitude above the destination used for the final descent before landing or loitering (default: 30m). |
|
||||
| <a id="RTL_LAND_DELAY"></a>[RTL_LAND_DELAY](../advanced_config/parameter_reference.md#RTL_LAND_DELAY) | Time to hover at `RTL_DESCEND_ALT` before landing (default: 0.5s) - by default this period is short so that the vehicle will simply slow and then land immediately. Якщо встановлено значення -1, система буде кружляти на висоті `RTL_DESCEND_ALT` замість посадки. Затримка надається для того, щоб ви могли налаштувати час для розгортання шасі для посадки (автоматично спрацьовує). |
|
||||
| <a id="RTL_MIN_DIST"></a>[RTL_MIN_DIST](../advanced_config/parameter_reference.md#RTL_MIN_DIST) | Within this distance from the home position, the return altitude is calculated from the "cone" rather than directly from `RTL_RETURN_ALT`. |
|
||||
| <a id="RTL_CONE_ANG"></a>[RTL_CONE_ANG](../advanced_config/parameter_reference.md#RTL_CONE_ANG) | Половина кута конуса, який визначає висоту повернення транспортного засобу RTL. Values (in degrees): `0`, `25`, `45`, `65`, `80`, `90`. Note that `0` is "no cone" (always return at `RTL_RETURN_ALT` or higher), while `90` indicates an almost vertical cone, so the vehicle generally returns at its current altitude when close to the destination. The return altitude may still be constrained to avoid flying too low while approaching the destination. |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
|
||||
## Дивіться також
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ The _Takeoff_ flight mode causes the vehicle to take off to a specified height a
|
||||
- Літаючі транспортні засоби перейдуть в режим аварійної безпеки, якщо втратять оцінку положення.
|
||||
- Роззброєні транспортні засоби можуть переключатися в режим без дійсної оцінки позиції, але не можуть озброюватися.
|
||||
- Перемикачі радіокерування можна використовувати для зміни режимів польоту.
|
||||
- RC stick movement will [by default](#COM_RC_OVERRIDE) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- Stick movement will [by default](#MAN_OVERRIDE_SPD) change the vehicle to [Position mode](../flight_modes_mc/position.md) unless prevented by the active failsafe state.
|
||||
- The [Failure Detector](../config/safety.md#failure-detector) will automatically stop the engines if there is a problem on takeoff.
|
||||
|
||||
<!-- https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/commander/ModeUtil/mode_requirements.cpp -->
|
||||
@@ -23,18 +23,33 @@ The _Takeoff_ flight mode causes the vehicle to take off to a specified height a
|
||||
|
||||
A multi rotor ascends vertically to the altitude defined in [MIS_TAKEOFF_ALT](../advanced_config/parameter_reference.md#MIS_TAKEOFF_ALT) and holds position.
|
||||
|
||||
RC stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#COM_RC_OVERRIDE)).
|
||||
Stick movement will change the vehicle to [Position mode](../flight_modes_mc/position.md) (by [default](#MAN_OVERRIDE_SPD)).
|
||||
|
||||
### Параметри
|
||||
|
||||
Взліт впливається наступними параметрами:
|
||||
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="MIS_TAKEOFF_ALT"></a>[MIS_TAKEOFF_ALT](../advanced_config/parameter_reference.md#MIS_TAKEOFF_ALT) | Цільова висота під час злітання (типово: 2.5м) |
|
||||
| <a id="MPC_TKO_SPEED"></a>[MPC_TKO_SPEED](../advanced_config/parameter_reference.md#MPC_TKO_SPEED) | Швидкість підйому (за замовчуванням: 1.5м/с) |
|
||||
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). Це можна окремо увімкнути для автоматичних режимів та для режиму поза бортом, і в автоматичних режимах воно включено за замовчуванням. |
|
||||
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled) |
|
||||
| Parameter | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="MIS_TAKEOFF_ALT"></a>[MIS_TAKEOFF_ALT](../advanced_config/parameter_reference.md#MIS_TAKEOFF_ALT) | Цільова висота під час злітання (типово: 2.5м) |
|
||||
| <a id="MPC_TKO_SPEED"></a>[MPC_TKO_SPEED](../advanced_config/parameter_reference.md#MPC_TKO_SPEED) | Швидкість підйому (за замовчуванням: 1.5м/с) |
|
||||
| <a id="MAN_OVERRIDE_SPD"></a>[MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) | Speed (normalized stick travel per second) above which moving the sticks controlling a multicopter (or VTOL in hover) gives control back to the pilot by switching to [Position mode](../flight_modes_mc/position.md) (or Altitude mode if position is unavailable). At the default value of 1 a half-stick movement in ~0.5 s triggers it; lower is more sensitive. A stick held statically has zero speed and will not trigger. Set to -1 to disable. <Badge type="tip" text="PX4 v1.18" /> |
|
||||
|
||||
## Takeoff From a Moving Platform (Boat Deck) <Badge type="tip" text="PX4 v1.18" />
|
||||
|
||||
Automatic takeoff from a moving platform, such as a boat deck, is supported. The multicopter climbs and holds the point where it left the deck, rather than following the boat.
|
||||
|
||||
:::warning
|
||||
Given that the vehicle holds the point where it left the deck and does not travel along with the boat, always take off from the **back (stern) of the boat**, with clear open space behind it.
|
||||
Taking off from the bow or the middle of the boat can leave it behind across the deck and into masts, antennas, superstructure, or crew.
|
||||
:::
|
||||
|
||||
:::info
|
||||
Takeoff from a moving platform is only supported in [Takeoff mode](#technical-summary) (or the equivalent coordinate-less takeoff commanded from a ground station), not as part of a [Mission](../flight_modes_mc/mission.md).
|
||||
To run a mission from a boat, take off first in Takeoff mode and then start the mission once the vehicle is airborne.
|
||||
:::
|
||||
|
||||
The moving-platform case can be exercised in simulation with the Gazebo [Moving Platform world](../sim_gazebo_gz/worlds.md#moving-platform).
|
||||
|
||||
## Дивіться також
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
Режим _повернення_ використовується для _політів засобом перевезення до безпечного місця_ при наявності вільного шляху до безпечного пункту призначення, де він може зачекати (зависнути або обійти колом) або сісти.
|
||||
|
||||
Літальні апарати типу VTOL за замовчуванням використовують тип повернення до призначення [місії посадки/точка збору](../flight_modes/return.md#mission-landing-rally-point-return-type-rtl-type-1).
|
||||
VTOL vehicles use the [Mission Landing/Rally Point](../flight_modes/return.md#rtl_type_1) return type by default.
|
||||
У цьому типі повернення апарат піднімається на мінімальну безпечну висоту над перешкодами (за необхідності), а потім напряму летить до точки збору або початкової точки призначення місії (яка є найближчою), або додому, якщо жодна з точок збору або місійний маршрут посадки не визначені.
|
||||
Якщо призначенням є місійний маршрут посадки, апарат потім дотримуватиметься маршруту для посадки.
|
||||
If the destination is a rally point or the home location, the vehicle will fly to that destination and land.
|
||||
@@ -12,7 +12,7 @@ If the destination is a rally point or the home location, the vehicle will fly t
|
||||
Літальний апарат повернеться за допомогою режиму польоту (MC або FW), який він використовував у той момент, коли був активований режим повернення.
|
||||
Загалом, він буде дотримуватися того ж поведінкового зразка режиму повернення, що й відповідний тип транспортного засобу, але завжди перейде до режиму MC (якщо потрібно) перед посадкою.
|
||||
|
||||
VTOL підтримує [інші типи повернення PX4](../flight_modes/return.md#return-types-rtl-type), включаючи повернення до дому / точки збору, маршрут місії і найближче безпечне місце призначення. Рекомендується використовувати тип за замовчуванням.
|
||||
VTOL supports the [other PX4 return types](../flight_modes/return.md#return_types), including home/rally point return, mission path and closest safe destination.
|
||||
За замовчуванням рекомендується використовувати цей тип.
|
||||
|
||||
::: info
|
||||
@@ -32,7 +32,7 @@ VTOL підтримує [інші типи повернення PX4](../flight_m
|
||||
|
||||
## Технічний підсумок
|
||||
|
||||
Літальні апарати типу VTOL за замовчуванням використовують тип повернення до призначення [місії посадки/ точки збору](../flight_modes/return.md#mission-landing-rally-point-return-type-rtl-type-1), і повертаються, використовуючи режим польоту (MC або FW), який вони використовували в момент активації режиму повернення.
|
||||
VTOL vehicles use the [Mission Landing/Rally Point](../flight_modes/return.md#rtl_type_1) return type by default, and return using the flying mode (MC or FW) it was using at the point when return mode was triggered.
|
||||
|
||||
### Повернення режиму фіксованого крила (FW)
|
||||
|
||||
@@ -42,7 +42,8 @@ VTOL підтримує [інші типи повернення PX4](../flight_m
|
||||
Транспортний засіб підтримує свою початкову висоту, якщо вона вище, ніж мінімальна висота повернення.
|
||||
<!-- Note that return altitude cannot be configured using the "cone" parameter in fixed-wing vehicles. -->
|
||||
|
||||
- Летить прямим шляхом на постійній висоті до призначення, яким буде найближча з точки старту місійного маршруту посадки та будь-яка точка збору, або домашня локація, якщо місійний маршрут посадки або точки збору не визначені.
|
||||
- Flies via a constant-altitude path to the destination, which will be the closest of the start of a _mission landing pattern_ and any rally point, or the home location if no mission landing pattern or rally points are defined.
|
||||
The path is chosen to be the shortest horizontal [geofence-aware path](../flight_modes/return.md#geofence_awareness).
|
||||
|
||||
- Якщо призначенням є місійний маршрут посадки, апарат буде дотримуватися маршруту для посадки.
|
||||
|
||||
|
||||
@@ -34,5 +34,5 @@ The set of supported configurations can be seen in [Airframes Reference > Autogy
|
||||
|
||||
У цьому розділі перелічені транспортні засоби, які продаються повністю зібраними та готові до польоту (RTF), з встановленим PX4.
|
||||
|
||||
- [ThunderFly TF-G2](https://docs.thunderfly.cz/instruments/TF-G2) - Unmanned Autogyro Development Kit
|
||||
- [ThunderFly TF-G250](https://docs.thunderfly.cz/instruments/TF-G250) - Atmospheric Sounding Aerological Autogyro
|
||||
- [ThunderFly TF-G2](https://docs.thunderfly.cz/instruments/TF-G2/) - Unmanned Autogyro Development Kit
|
||||
- [ThunderFly TF-G250](https://docs.thunderfly.cz/instruments/TF-G250/) - Atmospheric Sounding Aerological Autogyro
|
||||
|
||||
@@ -6,7 +6,7 @@ Durafly™ Auto-G2 Gyrocopter RC model, with several parts of the original model
|
||||
|
||||
|
||||
:::info
|
||||
Auto-G2 autogyro’s airframe was originally developed by [ThunderFly](https://www.thunderfly.cz/) and has since evolved into the updated [TF-G2 platform](https://docs.thunderfly.cz/instruments/TF-G2).
|
||||
Auto-G2 autogyro’s airframe was originally developed by [ThunderFly](https://www.thunderfly.cz/) and has since evolved into the updated [TF-G2 platform](https://docs.thunderfly.cz/instruments/TF-G2/).
|
||||
Check out our site for more information on the current [TF-G2 commercial airframe](https://www.thunderfly.cz/tf-g2.html).
|
||||
:::
|
||||
|
||||
@@ -30,7 +30,7 @@ Durafly Auto-G2 коробка автожира містить полістир
|
||||
### Автопілот
|
||||
|
||||
Літак з усіма модифікаціями вже досить важкий.
|
||||
Therefore a low-weight flight controller is recommended (e.g. [Holybro pix32](../flight_controller/holybro_pix32.md) or [CUAV nano](../flight_controller/cuav_v5_nano.md)).
|
||||
Therefore a low-weight flight controller is recommended.
|
||||
|
||||
The autopilot should be mounted on the bottom side of the autogyro on a 3D-printed damping pad.
|
||||
We have used the damping platform found on [thingiverse](https://www.thingiverse.com/thing:160655)
|
||||
@@ -104,7 +104,7 @@ It is a small box equipped with a servo that pulls out the pin and releases the
|
||||
|
||||
### Електроніка
|
||||
|
||||
- Autopilot ([Holybro pix32](../flight_controller/holybro_pix32.md), [CUAV nano](../flight_controller/cuav_v5_nano.md))
|
||||
- Autopilot ([Holybro pix32](../flight_controller/holybro_pix32.md), _CUAV nano_ (discontinued)
|
||||
- GPS (Модуль GPS NEO-6M, з патч-антеною)
|
||||
- Airspeed sensor ([SDP3x series](https://sensirion.com/products/catalog?categories=differential-pressure&series=SDP3x&page=1&page_size=12))
|
||||
- Stronger servos as a substitution for the original ones (optional), ([BlueBird BMS-125WV](https://www.blue-bird-model.com/products_detail/411.htm))
|
||||
|
||||
@@ -14,7 +14,7 @@ This topic provides full instructions for building the kit and configuring PX4 u
|
||||
|
||||
Компоненти, необхідні для цієї збірки, є:
|
||||
|
||||
- Flight controller: [CUAV V5 nano](https://store.cuav.net/shop/v5-nano/):
|
||||
- Flight controller: [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) (Discontinued):
|
||||
- GPS: [CUAV NEO V2 GPS](https://store.cuav.net/?id_product=97&id_product_attribute=0&rewrite=cuav-new-ublox-neo-m8n-gps-module-with-shell-stand-holder-for-flight-controller-gps-compass-for-pixhack-v5-plus-rc-parts-px4&controller=product&id_lang=1)
|
||||
- Модуль живлення
|
||||
- Frame: [DJI F450](https://www.amazon.com/Flame-Wheel-Basic-Quadcopter-Drone/dp/B00HNMVQHY)
|
||||
|
||||
@@ -5,7 +5,7 @@ This topic provides full instructions for building the kit and configuring PX4 u
|
||||
Основна Інформація
|
||||
|
||||
- **Frame:** DJI F450
|
||||
- **Flight controller:** [CUAV V5+](../flight_controller/cuav_v5_plus.md)
|
||||
- **Flight controller:** [CUAV V5+](../flight_controller/cuav_v5_plus.md) (Discontinued)
|
||||
- **Assembly time (approx.):** 90 minutes (45 minutes for frame, 45 minutes autopilot installation/configuration)
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ This topic provides full instructions for building the kit and configuring PX4 u
|
||||
|
||||
Компоненти, необхідні для цієї збірки, є:
|
||||
|
||||
- Flight controller: [CUAV V5+](https://store.cuav.net/uav-flight-controller/):
|
||||
- Flight controller: _CUAV V5+_ (Discontinued):
|
||||
- GPS: CUAV NEO V2 GPS (Discontined)
|
||||
- Модуль живлення
|
||||
- Frame: [DJI F450](https://www.amazon.com/Flame-Wheel-Basic-Quadcopter-Drone/dp/B00HNMVQHY)
|
||||
|
||||
@@ -14,12 +14,16 @@ Kits generally do not include:
|
||||
|
||||
:::
|
||||
|
||||
:::tip
|
||||
Kits certified by the PX4 team are listed in [PX4 Developer Kits](../dev_kits/index.md).
|
||||
:::
|
||||
|
||||
## Набори
|
||||
|
||||
Наступні комплекти в даний час доступні:
|
||||
|
||||
- [Holybro X500 v2 PX4 Development Kit](https://holybro.com/collections/x500-kits) (Pixhawk 6c) ([Build instructions](../frames_multicopter/holybro_x500v2_pixhawk6c.md)) - [Official PX4 Developer Kit](../dev_kits/index.md)
|
||||
- [Holybro X650 PX4 Development Kit](https://holybro.com/collections/x650-kits) (Pixhawk 6C/6X) ([Frame assembly guide](https://docs.holybro.com/drone-development-kit/x650-development-kit/download))
|
||||
- [Holybro X500 v2 PX4 Development Kit](https://holybro.com/collections/x500-kits) (Pixhawk 6c) ([Build instructions](../frames_multicopter/holybro_x500v2_pixhawk6c.md))
|
||||
- [Holybro S500 Kit v2](https://holybro.com/collections/s500/products/s500-v2-development-kit) (Pixhawk 6c)
|
||||
- [Holybro QAV250 Kit](https://holybro.com/products/qav250-kit) (Pixhawk 6c)
|
||||
- [NXP HoverGames KIT-HGDRONEK66](https://www.nxp.com/KIT-HGDRONEK66) ([hovergames.com](https://www.hovergames.com/))
|
||||
|
||||
@@ -34,8 +34,8 @@ This build follows the original design from [Brescianini, Dario, and Raffaello D
|
||||
- Акумулятор: ми використовували LiPo на 6S 3300mAh. Обов'язково перевірте розміри, щоб він підійшов до рами.
|
||||
- Ремінь для акумулятора
|
||||
- Рама:
|
||||
- Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/de/produkt/cfk-vierkantrohr-8x8-7x7mm)
|
||||
- Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://www.shop.swiss-composite.ch/de/produkt/carbon-microtubes-100cm-x-20-3mm)
|
||||
- Carbon square tube R 8mm X 7mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://shop.swiss-composite.ch/de/produkt/cfk-vierkantrohr-8x8-7x7mm)
|
||||
- Carbon Rods R 3mm X 2mm X 1000mm, e.g. [here on shop.swiss-composite.ch](https://shop.swiss-composite.ch/de/produkt/carbon-microtubes-100cm-x-20-3mm)
|
||||
- Необхідні довжини:
|
||||
- квадратна трубка: 8 штук довжиною 248 мм
|
||||
- стрижні: 12x328мм, 6x465мм
|
||||
|
||||
@@ -14,7 +14,7 @@ It is small, rugged and just large enough to host a [Pixracer](../flight_control
|
||||
|
||||
### Z-84 Plug n' Fly (PNF/PNP) або Комплект
|
||||
|
||||
- [Banggood](https://www.banggood.com/Wing-Wing-Z-84-Z84-EPO-845mm-Wingspan-Flying-Wing-PNP-p-973125.html)
|
||||
- [Banggood](https://www.banggood.com/Zeta-Wing-Wing-Z-84-Z84-EPO-845mm-Wingspan-Flying-Wing-PNP-p-973125.html?akmClientCountry=America&)
|
||||
|
||||
:::tip
|
||||
PNF (or "PNP") versions include motor, propeller and electronic speed controller.
|
||||
|
||||
@@ -92,7 +92,7 @@ This section contains videos that are specific to Tailsitter VTOL (videos that a
|
||||
:::: tabs
|
||||
|
||||
:::tab WingtraOne
|
||||
[WingtraOne](https://wingtra.com/mapping-drone-fast-accurate-surveying/)
|
||||
[WingtraOne](https://wingtra.com/wingtraone-gen-ii-drone/)
|
||||
|
||||
|
||||
:::
|
||||
|
||||
@@ -50,7 +50,7 @@ Foxtech Loong 2160 VTOL - це легкий у монтажі майже гот
|
||||
- [Радіо (RC) система](../getting_started/rc_transmitter_receiver.md) на ваш вибір
|
||||
- [Groundstation and Radio link](https://holybro.com/products/skydroid-h12)
|
||||
- [Розширення кабеля USB-C](https://www.digitec.ch/en/s1/product/powerguard-usb-c-usb-c-025-m-usb-cables-22529949?dbq=1&gclid=Cj0KCQjw2cWgBhDYARIsALggUhrh-z-7DSU0wKfLBVa8filkXLQaxUpi7pC0ffQyRzLng8Ph01h2R1gaAp0mEALw_wcB&gclsrc=aw.ds)
|
||||
- [I2C Splitter](https://www.3dxr.co.uk/autopilots-c2/the-cube-aka-pixhawk-2-1-c9/cube-cables-accessories-sensors-c15/cubepilot-i2c-can-splitter-jst-gh-4pin-hx4-06152-p2840)
|
||||
- [I2C Splitter](https://www.3dxr.co.uk/products/cubepilot-i2c-can-splitter-jst-gh-4pin-hx4-06152)
|
||||
- [3D-Printed mounts](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/vtol/foxtech_loong_2160/loong-3d-prints.zip)
|
||||
- 1x Базова плита
|
||||
- 1x Stack-fixture
|
||||
|
||||
@@ -14,8 +14,8 @@ These instructions _should_ work with the updated vehicle: [TBS Caipirinha 2](ht
|
||||
|
||||
- TBS Caipirinha Wing (no longer available - try [TBS Caipirinha 2](https://www.team-blacksheep.com/products/prod:tbs_caipi2_pnp))
|
||||
- Left and right 3D-printed motor mount (<a href="https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/airframes/vtol/caipiroshka/motor_mounts.zip" target="_blank">design files</a>)
|
||||
- CW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-CWCCW-Propeller-For-Quadcopters-1-Pair-p-950874.html))
|
||||
- CCW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-CWCCW-Propeller-For-Quadcopters-1-Pair-p-950874.html))
|
||||
- CW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-8x4_5-8-Inch-Propeller-for-Quacopters-p-950874.html?akmClientCountry=America&))
|
||||
- CCW 8045 propeller ([Eflight store](https://www.banggood.com/GEMFAN-Carbon-Nylon-8045-8x4_5-8-Inch-Propeller-for-Quacopters-p-950874.html?akmClientCountry=America&))
|
||||
- 2x 1800 kV 120-180W двигуни
|
||||
- [ePower 2208](https://www.galaxus.ch/en/s5/product/epower-22081400-fuer-2-3-lipo-imax-rc-motors-8355913)
|
||||
- [Armattan 2208 1800kV Multirotor Motor](https://www.amazon.com/Armattan-2208-1800kV-Multirotor-Motor/dp/B00UWLW0C8)
|
||||
|
||||
@@ -33,7 +33,7 @@ For more information see: [Flight Analysis](../dev_log/flight_log_analysis.md).
|
||||
|
||||
:::tip
|
||||
If you have a constant high-rate MAVLink connection to the vehicle (not just a telemetry link) then you can use _QGroundControl_ to automatically upload logs directly to _Flight Review_.
|
||||
For more information see [Settings > MAVLink Settings > MAVLink 2 Logging (PX4 only)](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/settings_view/mavlink.html#logging).
|
||||
For more information see [Settings > MAVLink Settings > MAVLink 2 Logging (PX4 only)](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/settings_view/px4_log_transfer.html).
|
||||
:::
|
||||
|
||||
## Надання доступу до файлів журналів розробникам PX4
|
||||
|
||||
@@ -4,7 +4,7 @@ The [Holybro H-RTK Unicore UM982 GPS](https://holybro.com/products/h-rtk-unicore
|
||||
|
||||
|
||||
|
||||
This module is based on the [Unicore UM982 Chip](https://en.unicore.com/products/dual-antenna-gnss-um982/), which supports RTK positioning and dual-antenna heading calculation.
|
||||
This module is based on the [Unicore UM982 Chip](https://en.unicore.com/products/um982/), which supports RTK positioning and dual-antenna heading calculation.
|
||||
|
||||
Це означає, що він може генерувати рухому базову лінію визначення курсу/рискання для автопілотів з одним GPS-модулем і двома антенами - магнітометр не потрібен.
|
||||
Unlike when using a module such as the U-blox F9P, where you would need [two U-blox F9P modules to compute a heading angle](../gps_compass/u-blox_f9p_heading.md), with the Unicore UM982 GPS, you only need one GPS module!
|
||||
|
||||
@@ -197,7 +197,7 @@ For that reason:
|
||||
|
||||
The board support process improves over time, and contributions to the process itself are welcome.
|
||||
|
||||
- Ask the community on the PX4 [Discord](https://chat.dronecode.org) under the `Hardware` channels, or on the [discuss forum](https://discuss.px4.io/).
|
||||
- Ask the community on the PX4 [Discord](https://discord.com/invite/dronecode) under the `Hardware` channels, or on the [discuss forum](https://discuss.px4.io/).
|
||||
- Join the regular hardware call.
|
||||
- Consultancy options are listed at [px4.io/community/consultants](https://px4.io/community/consultants/).
|
||||
|
||||
|
||||
@@ -0,0 +1,65 @@
|
||||
# Official PX4 Developer Kit Program
|
||||
|
||||
This topic explains how manufacturers can get a drone kit certified as an _Official PX4 Developer Kit_.
|
||||
|
||||
The PX4 community is growing quickly, and developers are frequently blocked on getting the right hardware into their hands.
|
||||
Too many options and configuration permutations also make it hard for maintainers to support the community well.
|
||||
Official PX4 Developer Kits solve this by establishing a foundational hardware reference for the ecosystem: kits that meet a defined standard for the bare-minimum components a PX4 developer needs to create modern applications, backed by the trust of the PX4 name.
|
||||
|
||||
In return, Dronecode puts its official weight behind qualifying products (see [What you get](#what-you-get) below).
|
||||
|
||||
Currently certified kits are listed in [PX4 Developer Kits](../dev_kits/index.md).
|
||||
|
||||
## Вимоги
|
||||
|
||||
A kit qualifies when it meets all five requirements:
|
||||
|
||||
1. A flight controller meeting the latest [Pixhawk standard](https://pixhawk.org/standards/), or matching its capabilities
|
||||
2. The latest stable PX4 release, pre-installed
|
||||
3. Pre-assembled, or assembly that requires no technical skill (no soldering)
|
||||
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 guide and tutorial may ship as QR-code links.
|
||||
|
||||
## What Qualifying Looks Like in Practice
|
||||
|
||||
The experience your kit must deliver:
|
||||
|
||||
- **Rapid start:** No technical skill needed to get flying. Minimal or zero assembly, software pre-installed, documentation included.
|
||||
- **Room to extend:** Ample headroom for performant code. The latest components, or space to expand.
|
||||
- **Current hardware:** Latest-generation drone hardware, matching the newest Pixhawk standard or its capabilities.
|
||||
- **A modern companion computer:** Able to offload compute from the flight controller MCU.
|
||||
- **Everything included:** Bundled with the open source software and tools developers expect.
|
||||
- **Quality assurance:** An available support channel or forum.
|
||||
|
||||
### Where to Focus: the Companion Computer
|
||||
|
||||
The biggest differentiator for a kit is the companion computer and the tools developers can leverage on it:
|
||||
|
||||
- **MAVLink:** A solid interface that can feed multiple targets, using [MAVSDK](https://mavsdk.mavlink.io/), mission planning tools, or MAVROS.
|
||||
- **DDS & ROS 2:** Leverage the [uXRCE-DDS](../middleware/uxrce_dds.md) integration and expose the interface directly to the companion computer over a high-bandwidth link.
|
||||
- **Easy app deployment:** Tools that help developers continuously test applications across the whole development lifecycle.
|
||||
- **LTE / WiFi:** A competent network stack that reaches the cloud securely and efficiently.
|
||||
- **Great documentation:** Publicly accessible docs, with ways to contribute back for continuous improvement.
|
||||
|
||||
## What You Get {#what-you-get}
|
||||
|
||||
Kits accepted into the program receive:
|
||||
|
||||
- **Official endorsement:** The _Official PX4 Developer Kit_ designation, on your product and your marketing.
|
||||
- **PX4 website listing:** A listing on the PX4 website and in this documentation, for standing presence in front of the entire community.
|
||||
- **Official promotion:** A promotional announcement from official Dronecode accounts on social media.
|
||||
|
||||
## Eligibility
|
||||
|
||||
The program is open exclusively to [Dronecode Foundation](https://dronecode.org/) members.
|
||||
Active membership is required for the endorsement, the website listing, and the promotion.
|
||||
|
||||
To apply, or to discuss membership as a first step, [contact Dronecode](https://dronecode.org/contact/).
|
||||
|
||||
## Дивіться також
|
||||
|
||||
- [PX4 Developer Kits](../dev_kits/index.md)
|
||||
- [Manufacturer's Board Support Guide](../hardware/board_support_guide.md)
|
||||
@@ -3,7 +3,7 @@
|
||||
This section contains topics about integrating PX4 with _new_ autopilot and peripheral hardware, including:
|
||||
|
||||
- [Flight Controller Reference Design](../hardware/reference_design.md)
|
||||
- [Manufacturer’s Board Support Guide](../hardware/board_support_guide.md)
|
||||
- [Manufacturers](../hardware/manufacturers.md) - board support guide and developer kit program
|
||||
- [Flight Controller Porting Guide](../hardware/porting_guide.md)
|
||||
- [Serial Port Mapping](../hardware/serial_port_mapping.md)
|
||||
- [Airframes](../dev_airframes/index.md)
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
# Manufacturers
|
||||
|
||||
This section contains information for manufacturers building hardware products for the PX4 ecosystem:
|
||||
|
||||
- [Manufacturer's Board Support Guide](../hardware/board_support_guide.md) - How to create and maintain PX4-compatible flight controllers, including branding, licensing, and support expectations.
|
||||
- [Official PX4 Developer Kit Program](../hardware/dev_kit_program.md) - How to get a drone kit certified as an _Official PX4 Developer Kit_.
|
||||
|
||||
Related topics:
|
||||
|
||||
- [Flight Controller Reference Design](../hardware/reference_design.md)
|
||||
- [Flight Controller Porting Guide](../hardware/porting_guide.md)
|
||||
- [Pixhawk Standards](https://pixhawk.org/standards/)
|
||||
- [Dronecode Foundation](https://dronecode.org/) (membership, trademarks, working groups)
|
||||
+5
-1
@@ -33,6 +33,10 @@ Want to modify PX4 or build from source? Start with the [Development Guide](deve
|
||||
|
||||
Start with [Basic Concepts](getting_started/px4_basic_concepts.md) for an overview of the flight stack, flight modes, safety features, and supported hardware.
|
||||
|
||||
## Developer Kits
|
||||
|
||||
The fastest way to get flying hardware for PX4 development. [Official PX4 Developer Kits](dev_kits/index.md) ship with the latest stable PX4 pre-installed on current Pixhawk-standard hardware, need no build skills, and are certified by the PX4 team.
|
||||
|
||||
## Build a Vehicle
|
||||
|
||||
Pick your frame type: [Multicopter](frames_multicopter/index.md), [Fixed-Wing](frames_plane/index.md), [VTOL](frames_vtol/index.md), [Helicopter](frames_helicopter/index.md), or [Rover](frames_rover/index.md). Each section covers complete vehicles, kits, and DIY builds. For assembly instructions see [Assembling a Multicopter](assembly/assembly_mc.md) or the equivalent for your frame.
|
||||
@@ -91,7 +95,7 @@ The calendar default timezone is Central European Time (CET).
|
||||
|
||||
<img src="../assets/site/position_fixed.svg" title="Position fix required (e.g. GPS)" width="30px" /> _placeholder_ icon made by <a href="https://www.flaticon.com/authors/smashicons" title="Smashicons">Smashicons</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="https://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.
|
||||
|
||||
<img src="../assets/site/automatic_mode.svg" title="Automatic mode" width="30px" /> _camera-automatic-mode_ icon made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="https://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.
|
||||
<img src="../assets/site/automatic_mode.svg" title="Automatic mode" width="30px" /> _camera-automatic-mode_ icon made by <a href="https://www.magnific.com/" title="Magnific">Magnific (formerly Freepik)</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> is licensed by <a href="https://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>.
|
||||
|
||||
## Управління
|
||||
|
||||
|
||||
+256
-253
File diff suppressed because it is too large
Load Diff
@@ -310,7 +310,7 @@ The benefits of the PX4 hardware abstraction comes into play here!
|
||||
Немає потреби взаємодіяти з драйверами сенсорів та оновлювати додаток, якщо плата або сенсори оновлені.
|
||||
:::
|
||||
|
||||
Individual message channels between applications are called [topics](../middleware/uorb.md). For this tutorial, we are interested in the [VehicleAcceleration](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleAcceleration.msg) topic, which holds the filtered vehicle acceleration data.
|
||||
Individual message channels between applications are called [topics](../middleware/uorb.md). For this tutorial, we are interested in the [VehicleAcceleration](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleAcceleration.msg) topic, which holds the filtered vehicle acceleration data.
|
||||
|
||||
Підписка на тему проста:
|
||||
|
||||
|
||||
@@ -69,6 +69,6 @@ PX4/PX4-Autopilot contains a template for writing a new application (module) tha
|
||||
[startup script](../concept/system_startup.md).
|
||||
- Парсинг аргументів командного рядка.
|
||||
- Documentation: the `PRINT_MODULE_*` methods serve two purposes (the API is
|
||||
documented [in the source code](https://github.com/PX4/PX4-Autopilot/blob/v1.17/platforms/common/include/px4_platform_common/module.h)):
|
||||
documented [in the source code](https://github.com/PX4/PX4-Autopilot/blob/v1.17.0/platforms/common/include/px4_platform_common/module.h)):
|
||||
- They are used to print the command-line usage when entering `module help` on the console.
|
||||
- They are automatically extracted via script to generate the [Modules & Commands Reference](../modules/modules_main.md) page.
|
||||
|
||||
@@ -1085,7 +1085,7 @@ px4io <command> [arguments...]
|
||||
|
||||
## rgbled
|
||||
|
||||
Source: [drivers/lights/rgbled_ncp5623c](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/lights/rgbled_ncp5623c)
|
||||
Source: [drivers/lights/rgbled](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/lights/rgbled)
|
||||
|
||||
### Usage {#rgbled_usage}
|
||||
|
||||
@@ -1100,9 +1100,7 @@ rgbled <command> [arguments...]
|
||||
[-f <val>] bus frequency in kHz
|
||||
[-q] quiet startup (no message if no device found)
|
||||
[-a <val>] I2C address
|
||||
default: 57
|
||||
[-o <val>] RGB PWM Assignment
|
||||
default: 123
|
||||
default: 85
|
||||
|
||||
stop
|
||||
|
||||
|
||||
@@ -122,6 +122,7 @@ dps310 <command> [arguments...]
|
||||
[-m <val>] SPI mode
|
||||
[-f <val>] bus frequency in kHz
|
||||
[-q] quiet startup (no message if no device found)
|
||||
[-8] Drive DPS368
|
||||
|
||||
stop
|
||||
|
||||
|
||||
@@ -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-reference-systems--ahrs-/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-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)
|
||||
|
||||
This driver is not included in the firmware by default.
|
||||
Include the module in firmware by setting the
|
||||
|
||||
@@ -6,22 +6,33 @@ pageClass: is-wide-page
|
||||
|
||||
Cellular status.
|
||||
|
||||
This is currently used only for logging cell status from MAVLink.
|
||||
This is currently used only for logging cell status from MAVLink 1:1.
|
||||
|
||||
**TOPICS:** cellular_status
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ------------------------------------------------------------------ | -------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_status"></a>status | `uint16` | | [STATUS_FLAG](#STATUS_FLAG) | Status bitmap |
|
||||
| <a id="fld_failure_reason"></a>failure_reason | `uint8` | | [FAILURE_REASON](#FAILURE_REASON) | Failure reason |
|
||||
| <a id="fld_type"></a>type | `uint8` | | [CELLULAR_NETWORK_RADIO_TYPE](#CELLULAR_NETWORK_RADIO_TYPE) | Cellular network radio type |
|
||||
| <a id="fld_quality"></a>quality | `uint8` | dBm | | Cellular network RSSI/RSRP, absolute value |
|
||||
| <a id="fld_mcc"></a>mcc | `uint16` | | | Mobile country code (Invalid: UINT16_MAX) |
|
||||
| <a id="fld_mnc"></a>mnc | `uint16` | | | Mobile network code (Invalid: UINT16_MAX) |
|
||||
| <a id="fld_lac"></a>lac | `uint16` | | | Location area code (Invalid: 0) |
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_status"></a>status | `uint8` | | [STATUS_FLAG](#STATUS_FLAG) | Status |
|
||||
| <a id="fld_failure_reason"></a>failure_reason | `uint8` | | [FAILURE_REASON](#FAILURE_REASON) | Failure reason |
|
||||
| <a id="fld_type"></a>type | `uint8` | | [CELLULAR_NETWORK_RADIO_TYPE](#CELLULAR_NETWORK_RADIO_TYPE) | Cellular network radio type |
|
||||
| <a id="fld_quality"></a>quality | `uint8` | % | | Cellular network signal quality in percent. May be used for RSSI (Invalid: UINT8_MAX) |
|
||||
| <a id="fld_mcc"></a>mcc | `uint16` | | | Mobile country code (Invalid: UINT16_MAX) |
|
||||
| <a id="fld_mnc"></a>mnc | `uint16` | | | Mobile network code (Invalid: UINT16_MAX) |
|
||||
| <a id="fld_lac"></a>lac | `uint16` | | | Location area code (Invalid: 0) |
|
||||
| <a id="fld_id"></a>id | `uint8` | | | Cellular instance number. Indexed from 1. A value of 0 indicates the sender does not support reporting of multiple modems |
|
||||
| <a id="fld_link_tx_rate"></a>link_tx_rate | `uint32` | KiB/s | | Download rate (Invalid: 0) |
|
||||
| <a id="fld_link_rx_rate"></a>link_rx_rate | `uint32` | KiB/s | | Upload rate (Invalid: 0) |
|
||||
| <a id="fld_cell_tower_id"></a>cell_tower_id | `char[9]` | | | ID of the currently connected cell tower. Must be NULL terminated if the length is less than 9 human-readable characters, and without NULL termination character if the length is exactly 9 characters (Invalid: 0) |
|
||||
| <a id="fld_band_number"></a>band_number | `uint8` | | | LTE frequency band number (Invalid: 0) |
|
||||
| <a id="fld_band_frequency"></a>band_frequency | `float32` | MHz | | LTE radio frequency (Invalid: 0) |
|
||||
| <a id="fld_channel_number"></a>channel_number | `uint32` | | | Channel Number (CN), Absolute radio-frequency (ARFCN) / E-UTRA (EARFCN) / UTRA (UARFCN) / New radio (NR_CH) (Invalid: 0) |
|
||||
| <a id="fld_rx_level"></a>rx_level | `float32` | dBm | | Receiver signal level. On 3G is Received Signal Code Power (RSCP). On LTE Reference Signal Received Power (RSRP). On 5G is New Radio Reference Signal Received Power (NR_RSRP) (Invalid: 0) |
|
||||
| <a id="fld_tx_level"></a>tx_level | `float32` | dBm | | Transmitter signal absolute level (Invalid: 0) |
|
||||
| <a id="fld_rx_quality"></a>rx_quality | `float32` | dBm | | Received signal quality. On 3G is Receiver Quality (RxQual). On LTE is Reference Signal Received Quality (RSRQ). On 5G is New Radio Reference Signal Received Quality (NR_RSRQ) (Invalid: 0) |
|
||||
| <a id="fld_sinr"></a>sinr | `float32` | dB | | Signal to Interference plus Noise Ratio (Invalid: 0) |
|
||||
|
||||
## Enums
|
||||
|
||||
@@ -29,21 +40,21 @@ This is currently used only for logging cell status from MAVLink.
|
||||
|
||||
Used in field(s): [status](#fld_status)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------- | -------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="#STATUS_FLAG_UNKNOWN"></a> STATUS_FLAG_UNKNOWN | `uint16` | 1 | State unknown or not reportable |
|
||||
| <a id="#STATUS_FLAG_FAILED"></a> STATUS_FLAG_FAILED | `uint16` | 2 | Modem is unusable |
|
||||
| <a id="#STATUS_FLAG_INITIALIZING"></a> STATUS_FLAG_INITIALIZING | `uint16` | 4 | Modem is being initialized |
|
||||
| <a id="#STATUS_FLAG_LOCKED"></a> STATUS_FLAG_LOCKED | `uint16` | 8 | Modem is locked |
|
||||
| <a id="#STATUS_FLAG_DISABLED"></a> STATUS_FLAG_DISABLED | `uint16` | 16 | Modem is not enabled and is powered down |
|
||||
| <a id="#STATUS_FLAG_DISABLING"></a> STATUS_FLAG_DISABLING | `uint16` | 32 | Modem is currently transitioning to the STATUS_FLAG_DISABLED state |
|
||||
| <a id="#STATUS_FLAG_ENABLING"></a> STATUS_FLAG_ENABLING | `uint16` | 64 | Modem is currently transitioning to the STATUS_FLAG_ENABLED state |
|
||||
| <a id="#STATUS_FLAG_ENABLED"></a> STATUS_FLAG_ENABLED | `uint16` | 128 | Modem is enabled and powered on but not registered with a network provider and not available for data connections |
|
||||
| <a id="#STATUS_FLAG_SEARCHING"></a> STATUS_FLAG_SEARCHING | `uint16` | 256 | Modem is searching for a network provider to register |
|
||||
| <a id="#STATUS_FLAG_REGISTERED"></a> STATUS_FLAG_REGISTERED | `uint16` | 512 | Modem is registered with a network provider, and data connections and messaging may be available for use |
|
||||
| <a id="#STATUS_FLAG_DISCONNECTING"></a> STATUS_FLAG_DISCONNECTING | `uint16` | 1024 | Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated |
|
||||
| <a id="#STATUS_FLAG_CONNECTING"></a> STATUS_FLAG_CONNECTING | `uint16` | 2048 | Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered |
|
||||
| <a id="#STATUS_FLAG_CONNECTED"></a> STATUS_FLAG_CONNECTED | `uint16` | 4096 | One or more packet data bearers is active and connected |
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ----------------------------------------------------------------------------------------------------------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="#STATUS_FLAG_UNKNOWN"></a> STATUS_FLAG_UNKNOWN | `uint8` | 0 | State unknown or not reportable |
|
||||
| <a id="#STATUS_FLAG_FAILED"></a> STATUS_FLAG_FAILED | `uint8` | 1 | Modem is unusable |
|
||||
| <a id="#STATUS_FLAG_INITIALIZING"></a> STATUS_FLAG_INITIALIZING | `uint8` | 2 | Modem is being initialized |
|
||||
| <a id="#STATUS_FLAG_LOCKED"></a> STATUS_FLAG_LOCKED | `uint8` | 3 | Modem is locked |
|
||||
| <a id="#STATUS_FLAG_DISABLED"></a> STATUS_FLAG_DISABLED | `uint8` | 4 | Modem is not enabled and is powered down |
|
||||
| <a id="#STATUS_FLAG_DISABLING"></a> STATUS_FLAG_DISABLING | `uint8` | 5 | Modem is currently transitioning to the STATUS_FLAG_DISABLED state |
|
||||
| <a id="#STATUS_FLAG_ENABLING"></a> STATUS_FLAG_ENABLING | `uint8` | 6 | Modem is currently transitioning to the STATUS_FLAG_ENABLED state |
|
||||
| <a id="#STATUS_FLAG_ENABLED"></a> STATUS_FLAG_ENABLED | `uint8` | 7 | Modem is enabled and powered on but not registered with a network provider and not available for data connections |
|
||||
| <a id="#STATUS_FLAG_SEARCHING"></a> STATUS_FLAG_SEARCHING | `uint8` | 8 | Modem is searching for a network provider to register |
|
||||
| <a id="#STATUS_FLAG_REGISTERED"></a> STATUS_FLAG_REGISTERED | `uint8` | 9 | Modem is registered with a network provider, and data connections and messaging may be available for use |
|
||||
| <a id="#STATUS_FLAG_DISCONNECTING"></a> STATUS_FLAG_DISCONNECTING | `uint8` | 10 | Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated |
|
||||
| <a id="#STATUS_FLAG_CONNECTING"></a> STATUS_FLAG_CONNECTING | `uint8` | 11 | Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered |
|
||||
| <a id="#STATUS_FLAG_CONNECTED"></a> STATUS_FLAG_CONNECTED | `uint8` | 12 | One or more packet data bearers is active and connected |
|
||||
|
||||
### FAILURE_REASON {#FAILURE_REASON}
|
||||
|
||||
@@ -78,42 +89,54 @@ Click here to see original file
|
||||
```c
|
||||
# Cellular status
|
||||
#
|
||||
# This is currently used only for logging cell status from MAVLink.
|
||||
# This is currently used only for logging cell status from MAVLink 1:1.
|
||||
|
||||
uint64 timestamp # [us] Time since system start
|
||||
uint64 timestamp # [us] Time since system start
|
||||
|
||||
uint16 status # [@enum STATUS_FLAG] Status bitmap
|
||||
uint16 STATUS_FLAG_UNKNOWN = 1 # State unknown or not reportable
|
||||
uint16 STATUS_FLAG_FAILED = 2 # Modem is unusable
|
||||
uint16 STATUS_FLAG_INITIALIZING = 4 # Modem is being initialized
|
||||
uint16 STATUS_FLAG_LOCKED = 8 # Modem is locked
|
||||
uint16 STATUS_FLAG_DISABLED = 16 # Modem is not enabled and is powered down
|
||||
uint16 STATUS_FLAG_DISABLING = 32 # Modem is currently transitioning to the STATUS_FLAG_DISABLED state
|
||||
uint16 STATUS_FLAG_ENABLING = 64 # Modem is currently transitioning to the STATUS_FLAG_ENABLED state
|
||||
uint16 STATUS_FLAG_ENABLED = 128 # Modem is enabled and powered on but not registered with a network provider and not available for data connections
|
||||
uint16 STATUS_FLAG_SEARCHING = 256 # Modem is searching for a network provider to register
|
||||
uint16 STATUS_FLAG_REGISTERED = 512 # Modem is registered with a network provider, and data connections and messaging may be available for use
|
||||
uint16 STATUS_FLAG_DISCONNECTING = 1024 # Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated
|
||||
uint16 STATUS_FLAG_CONNECTING = 2048 # Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered
|
||||
uint16 STATUS_FLAG_CONNECTED = 4096 # One or more packet data bearers is active and connected
|
||||
uint8 status # [@enum STATUS_FLAG] Status
|
||||
uint8 STATUS_FLAG_UNKNOWN = 0 # State unknown or not reportable
|
||||
uint8 STATUS_FLAG_FAILED = 1 # Modem is unusable
|
||||
uint8 STATUS_FLAG_INITIALIZING = 2 # Modem is being initialized
|
||||
uint8 STATUS_FLAG_LOCKED = 3 # Modem is locked
|
||||
uint8 STATUS_FLAG_DISABLED = 4 # Modem is not enabled and is powered down
|
||||
uint8 STATUS_FLAG_DISABLING = 5 # Modem is currently transitioning to the STATUS_FLAG_DISABLED state
|
||||
uint8 STATUS_FLAG_ENABLING = 6 # Modem is currently transitioning to the STATUS_FLAG_ENABLED state
|
||||
uint8 STATUS_FLAG_ENABLED = 7 # Modem is enabled and powered on but not registered with a network provider and not available for data connections
|
||||
uint8 STATUS_FLAG_SEARCHING = 8 # Modem is searching for a network provider to register
|
||||
uint8 STATUS_FLAG_REGISTERED = 9 # Modem is registered with a network provider, and data connections and messaging may be available for use
|
||||
uint8 STATUS_FLAG_DISCONNECTING = 10 # Modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated
|
||||
uint8 STATUS_FLAG_CONNECTING = 11 # Modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered
|
||||
uint8 STATUS_FLAG_CONNECTED = 12 # One or more packet data bearers is active and connected
|
||||
|
||||
uint8 failure_reason # [@enum FAILURE_REASON] Failure reason
|
||||
uint8 FAILURE_REASON_NONE = 0 # No error
|
||||
uint8 FAILURE_REASON_UNKNOWN = 1 # Error state is unknown
|
||||
uint8 FAILURE_REASON_SIM_MISSING = 2 # SIM is required for the modem but missing
|
||||
uint8 FAILURE_REASON_SIM_ERROR = 3 # SIM is available, but not usable for connection
|
||||
uint8 failure_reason # [@enum FAILURE_REASON] Failure reason
|
||||
uint8 FAILURE_REASON_NONE = 0 # No error
|
||||
uint8 FAILURE_REASON_UNKNOWN = 1 # Error state is unknown
|
||||
uint8 FAILURE_REASON_SIM_MISSING = 2 # SIM is required for the modem but missing
|
||||
uint8 FAILURE_REASON_SIM_ERROR = 3 # SIM is available, but not usable for connection
|
||||
|
||||
uint8 type # [@enum CELLULAR_NETWORK_RADIO_TYPE] Cellular network radio type
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_NONE = 0 # None
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_GSM = 1 # GSM
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_CDMA = 2 # CDMA
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_WCDMA = 3 # WCDMA
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_LTE = 4 # LTE
|
||||
uint8 type # [@enum CELLULAR_NETWORK_RADIO_TYPE] Cellular network radio type
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_NONE = 0 # None
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_GSM = 1 # GSM
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_CDMA = 2 # CDMA
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_WCDMA = 3 # WCDMA
|
||||
uint8 CELLULAR_NETWORK_RADIO_TYPE_LTE = 4 # LTE
|
||||
|
||||
uint8 quality # [dBm] Cellular network RSSI/RSRP, absolute value
|
||||
uint16 mcc # [@invalid UINT16_MAX] Mobile country code
|
||||
uint16 mnc # [@invalid UINT16_MAX] Mobile network code
|
||||
uint16 lac # [@invalid 0] Location area code
|
||||
uint8 quality # [%] [@invalid UINT8_MAX] Cellular network signal quality in percent. May be used for RSSI
|
||||
uint16 mcc # [@invalid UINT16_MAX] Mobile country code
|
||||
uint16 mnc # [@invalid UINT16_MAX] Mobile network code
|
||||
uint16 lac # [@invalid 0] Location area code
|
||||
|
||||
uint8 id # [-] Cellular instance number. Indexed from 1. A value of 0 indicates the sender does not support reporting of multiple modems
|
||||
uint32 link_tx_rate # [KiB/s] [@invalid 0] Download rate
|
||||
uint32 link_rx_rate # [KiB/s] [@invalid 0] Upload rate
|
||||
char[9] cell_tower_id # [@invalid 0] ID of the currently connected cell tower. Must be NULL terminated if the length is less than 9 human-readable characters, and without NULL termination character if the length is exactly 9 characters
|
||||
uint8 band_number # [-] [@invalid 0] LTE frequency band number
|
||||
float32 band_frequency # [MHz] [@invalid 0] LTE radio frequency
|
||||
uint32 channel_number # [@invalid 0] Channel Number (CN), Absolute radio-frequency (ARFCN) / E-UTRA (EARFCN) / UTRA (UARFCN) / New radio (NR_CH)
|
||||
float32 rx_level # [dBm] [@invalid 0] Receiver signal level. On 3G is Received Signal Code Power (RSCP). On LTE Reference Signal Received Power (RSRP). On 5G is New Radio Reference Signal Received Power (NR_RSRP)
|
||||
float32 tx_level # [dBm] [@invalid 0] Transmitter signal absolute level
|
||||
float32 rx_quality # [dBm] [@invalid 0] Received signal quality. On 3G is Receiver Quality (RxQual). On LTE is Reference Signal Received Quality (RSRQ). On 5G is New Radio Reference Signal Received Quality (NR_RSRQ)
|
||||
float32 sinr # [dB] [@invalid 0] Signal to Interference plus Noise Ratio
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
@@ -6,7 +6,7 @@ pageClass: is-wide-page
|
||||
|
||||
Configurable overrides by (external) modes or mode executors.
|
||||
|
||||
**TOPICS:** config_overrides config_overrides_request
|
||||
**TOPICS:** config_overrides config_overrides_request config_overrides_confirm
|
||||
|
||||
## Fields
|
||||
|
||||
@@ -57,7 +57,7 @@ uint8 source_id # ID depending on source_type
|
||||
|
||||
uint8 ORB_QUEUE_LENGTH = 4
|
||||
|
||||
# TOPICS config_overrides config_overrides_request
|
||||
# TOPICS config_overrides config_overrides_request config_overrides_confirm
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
@@ -10,17 +10,18 @@ Fixed Wing Lateral Guidance Status message. Published by fw_pos_control module t
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| -------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_course_setpoint"></a>course_setpoint | `float32` | rad | [-pi : pi] | Desired direction of travel over ground w.r.t (true) North. Set by guidance law |
|
||||
| <a id="fld_lateral_acceleration_ff"></a>lateral_acceleration_ff | `float32` | FRD | | lateral acceleration demand only for maintaining curvature |
|
||||
| <a id="fld_bearing_feas"></a>bearing_feas | `float32` | | [0 : 1] | bearing feasibility |
|
||||
| <a id="fld_bearing_feas_on_track"></a>bearing_feas_on_track | `float32` | | [0 : 1] | on-track bearing feasibility |
|
||||
| <a id="fld_signed_track_error"></a>signed_track_error | `float32` | m | | signed track error |
|
||||
| <a id="fld_track_error_bound"></a>track_error_bound | `float32` | m | | track error bound |
|
||||
| <a id="fld_adapted_period"></a>adapted_period | `float32` | s | | adapted period (if auto-tuning enabled) |
|
||||
| <a id="fld_wind_est_valid"></a>wind_est_valid | `uint8` | boolean | | true = wind estimate is valid and/or being used by controller (also indicates if wind estimate usage is disabled despite being valid) |
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| -------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_course_setpoint"></a>course_setpoint | `float32` | rad | [-pi : pi] | Desired direction of travel over ground w.r.t (true) North. Set by guidance law |
|
||||
| <a id="fld_lateral_acceleration_ff"></a>lateral_acceleration_ff | `float32` | FRD | | lateral acceleration demand only for maintaining curvature |
|
||||
| <a id="fld_bearing_feas"></a>bearing_feas | `float32` | | [0 : 1] | bearing feasibility |
|
||||
| <a id="fld_bearing_feas_on_track"></a>bearing_feas_on_track | `float32` | | [0 : 1] | on-track bearing feasibility |
|
||||
| <a id="fld_signed_track_error"></a>signed_track_error | `float32` | m | | signed track error |
|
||||
| <a id="fld_track_error_bound"></a>track_error_bound | `float32` | m | | track error bound |
|
||||
| <a id="fld_switch_distance"></a>switch_distance | `float32` | m | [0 : INF] | distance from the current waypoint at which the navigator should advance to the next one (turn anticipation). If below NAV_ACC_RAD, the parameter value is used instead. (Invalid: NaN) |
|
||||
| <a id="fld_adapted_period"></a>adapted_period | `float32` | s | | adapted period (if auto-tuning enabled) |
|
||||
| <a id="fld_wind_est_valid"></a>wind_est_valid | `uint8` | boolean | | true = wind estimate is valid and/or being used by controller (also indicates if wind estimate usage is disabled despite being valid) |
|
||||
|
||||
## Source Message
|
||||
|
||||
@@ -41,6 +42,7 @@ float32 bearing_feas # [@range 0,1] bearing feasibility
|
||||
float32 bearing_feas_on_track # [@range 0,1] on-track bearing feasibility
|
||||
float32 signed_track_error # [m] signed track error
|
||||
float32 track_error_bound # [m] track error bound
|
||||
float32 switch_distance # [m] [@range 0, INF] [@invalid NaN] distance from the current waypoint at which the navigator should advance to the next one (turn anticipation). If below NAV_ACC_RAD, the parameter value is used instead.
|
||||
float32 adapted_period # [s] adapted period (if auto-tuning enabled)
|
||||
uint8 wind_est_valid # [boolean] true = wind estimate is valid and/or being used by controller (also indicates if wind estimate usage is disabled despite being valid)
|
||||
```
|
||||
|
||||
@@ -8,40 +8,63 @@ pageClass: is-wide-page
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_state"></a>state | `uint8` | | | |
|
||||
| <a id="fld_flags"></a>flags | `uint32` | | | |
|
||||
| <a id="fld_engine_load_percent"></a>engine_load_percent | `uint8` | | | Engine load estimate, percent, [0, 127] |
|
||||
| <a id="fld_engine_speed_rpm"></a>engine_speed_rpm | `uint32` | | | Engine speed, revolutions per minute |
|
||||
| <a id="fld_spark_dwell_time_ms"></a>spark_dwell_time_ms | `float32` | | | Spark dwell time, millisecond |
|
||||
| <a id="fld_atmospheric_pressure_kpa"></a>atmospheric_pressure_kpa | `float32` | | | Atmospheric (barometric) pressure, kilopascal |
|
||||
| <a id="fld_intake_manifold_pressure_kpa"></a>intake_manifold_pressure_kpa | `float32` | | | Engine intake manifold pressure, kilopascal |
|
||||
| <a id="fld_intake_manifold_temperature"></a>intake_manifold_temperature | `float32` | | | Engine intake manifold temperature, kelvin |
|
||||
| <a id="fld_coolant_temperature"></a>coolant_temperature | `float32` | | | Engine coolant temperature, kelvin |
|
||||
| <a id="fld_oil_pressure"></a>oil_pressure | `float32` | | | Oil pressure, kilopascal |
|
||||
| <a id="fld_oil_temperature"></a>oil_temperature | `float32` | | | Oil temperature, kelvin |
|
||||
| <a id="fld_fuel_pressure"></a>fuel_pressure | `float32` | | | Fuel pressure, kilopascal |
|
||||
| <a id="fld_fuel_consumption_rate_cm3pm"></a>fuel_consumption_rate_cm3pm | `float32` | | | Instant fuel consumption estimate, (centimeter^3)/minute |
|
||||
| <a id="fld_estimated_consumed_fuel_volume_cm3"></a>estimated_consumed_fuel_volume_cm3 | `float32` | | | Estimate of the consumed fuel since the start of the engine, centimeter^3 |
|
||||
| <a id="fld_throttle_position_percent"></a>throttle_position_percent | `uint8` | | | Throttle position, percent |
|
||||
| <a id="fld_ecu_index"></a>ecu_index | `uint8` | | | The index of the publishing ECU |
|
||||
| <a id="fld_spark_plug_usage"></a>spark_plug_usage | `uint8` | | | Spark plug activity report. |
|
||||
| <a id="fld_ignition_timing_deg"></a>ignition_timing_deg | `float32` | | | Cylinder ignition timing, angular degrees of the crankshaft |
|
||||
| <a id="fld_injection_time_ms"></a>injection_time_ms | `float32` | | | Fuel injection time, millisecond |
|
||||
| <a id="fld_cylinder_head_temperature"></a>cylinder_head_temperature | `float32` | | | Cylinder head temperature (CHT), kelvin |
|
||||
| <a id="fld_exhaust_gas_temperature"></a>exhaust_gas_temperature | `float32` | | | Exhaust gas temperature (EGT), kelvin |
|
||||
| <a id="fld_lambda_coefficient"></a>lambda_coefficient | `float32` | | | Estimated lambda coefficient, dimensionless ratio |
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_state"></a>state | `uint8` | | [STATE](#STATE) | Engine state |
|
||||
| <a id="fld_substate"></a>substate | `uint8` | | [SUBSTATE](#SUBSTATE) | Engine substate |
|
||||
| <a id="fld_flags"></a>flags | `uint32` | | [FLAG](#FLAG) | Engine status flags bitmap |
|
||||
| <a id="fld_engine_load_percent"></a>engine_load_percent | `uint8` | % | [0 : 127] | Engine load estimate |
|
||||
| <a id="fld_engine_speed_rpm"></a>engine_speed_rpm | `uint32` | rpm | [0 : inf] | Engine speed |
|
||||
| <a id="fld_spark_dwell_time_ms"></a>spark_dwell_time_ms | `float32` | ms | [0 : inf] | Spark dwell time |
|
||||
| <a id="fld_atmospheric_pressure_kpa"></a>atmospheric_pressure_kpa | `float32` | kPa | [0 : inf] | Atmospheric (barometric) pressure |
|
||||
| <a id="fld_intake_manifold_pressure_kpa"></a>intake_manifold_pressure_kpa | `float32` | kPa | [0 : inf] | Engine intake manifold pressure |
|
||||
| <a id="fld_intake_manifold_temperature"></a>intake_manifold_temperature | `float32` | K | [0 : inf] | Engine intake manifold temperature |
|
||||
| <a id="fld_coolant_temperature"></a>coolant_temperature | `float32` | K | [0 : inf] | Engine coolant temperature |
|
||||
| <a id="fld_oil_pressure"></a>oil_pressure | `float32` | kPa | [0 : inf] | Oil pressure |
|
||||
| <a id="fld_oil_temperature"></a>oil_temperature | `float32` | K | [0 : inf] | Oil temperature |
|
||||
| <a id="fld_fuel_pressure"></a>fuel_pressure | `float32` | kPa | [0 : inf] | Fuel pressure |
|
||||
| <a id="fld_fuel_consumption_rate_cm3pm"></a>fuel_consumption_rate_cm3pm | `float32` | cm^3/min | [0 : inf] | Instant fuel consumption estimate |
|
||||
| <a id="fld_estimated_consumed_fuel_volume_cm3"></a>estimated_consumed_fuel_volume_cm3 | `float32` | cm^3 | [0 : inf] | Estimate of the consumed fuel since the start of the engine |
|
||||
| <a id="fld_throttle_position_percent"></a>throttle_position_percent | `uint8` | % | [0 : 100] | Throttle position |
|
||||
| <a id="fld_ecu_index"></a>ecu_index | `uint8` | | [0 : 255] | The index of the publishing ECU |
|
||||
| <a id="fld_spark_plug_usage"></a>spark_plug_usage | `uint8` | | [SPARK_PLUG](#SPARK_PLUG) | Spark plug activity report |
|
||||
| <a id="fld_ignition_timing_deg"></a>ignition_timing_deg | `float32` | deg | [-inf : inf] | Cylinder ignition timing, angular degrees of the crankshaft |
|
||||
| <a id="fld_injection_time_ms"></a>injection_time_ms | `float32` | ms | [0 : inf] | Fuel injection time |
|
||||
| <a id="fld_cylinder_head_temperature"></a>cylinder_head_temperature | `float32` | K | [0 : inf] | Cylinder head temperature (CHT) |
|
||||
| <a id="fld_exhaust_gas_temperature"></a>exhaust_gas_temperature | `float32` | K | [0 : inf] | Exhaust gas temperature (EGT) |
|
||||
| <a id="fld_lambda_coefficient"></a>lambda_coefficient | `float32` | | [0 : inf] | Estimated lambda coefficient, dimensionless ratio |
|
||||
| <a id="fld_pid_idle_rpm_integral"></a>pid_idle_rpm_integral | `float32` | | [-1 : 1] | Integral of the PID for the closed loop idle RPM controller |
|
||||
|
||||
## Constants
|
||||
## Enums
|
||||
|
||||
### STATE {#STATE}
|
||||
|
||||
Used in field(s): [state](#fld_state)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ---------------------------------------------------------------- | ------- | -------- | ------------------------------------------------------------------------------------- |
|
||||
| <a id="#STATE_STOPPED"></a> STATE_STOPPED | `uint8` | 0 | The engine is not running. This is the default state. |
|
||||
| <a id="#STATE_STARTING"></a> STATE_STARTING | `uint8` | 1 | The engine is starting. This is a transient state. |
|
||||
| <a id="#STATE_RUNNING"></a> STATE_RUNNING | `uint8` | 2 | The engine is running normally. |
|
||||
| <a id="#STATE_FAULT"></a> STATE_FAULT | `uint8` | 3 | The engine can no longer function. |
|
||||
|
||||
### SUBSTATE {#SUBSTATE}
|
||||
|
||||
Used in field(s): [substate](#fld_substate)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| -------------------------------------------------------------- | ------- | -------- | --------------------------------------------------------------------------------- |
|
||||
| <a id="#SUBSTATE_RUN"></a> SUBSTATE_RUN | `uint8` | 0 | The engine is running. This is the default state. |
|
||||
| <a id="#SUBSTATE_IDLE"></a> SUBSTATE_IDLE | `uint8` | 1 | The engine idle rpm controller is running. |
|
||||
| <a id="#SUBSTATE_REST"></a> SUBSTATE_REST | `uint8` | 2 | The engine is at rest. |
|
||||
|
||||
### FLAG {#FLAG}
|
||||
|
||||
Used in field(s): [flags](#fld_flags)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | -------------------------------------------------------------------------------------- |
|
||||
| <a id="#STATE_STOPPED"></a> STATE_STOPPED | `uint8` | 0 | The engine is not running. This is the default state. |
|
||||
| <a id="#STATE_STARTING"></a> STATE_STARTING | `uint8` | 1 | The engine is starting. This is a transient state. |
|
||||
| <a id="#STATE_RUNNING"></a> STATE_RUNNING | `uint8` | 2 | The engine is running normally. |
|
||||
| <a id="#STATE_FAULT"></a> STATE_FAULT | `uint8` | 3 | The engine can no longer function. |
|
||||
| <a id="#FLAG_GENERAL_ERROR"></a> FLAG_GENERAL_ERROR | `uint32` | 1 | General error. |
|
||||
| <a id="#FLAG_CRANKSHAFT_SENSOR_ERROR_SUPPORTED"></a> FLAG_CRANKSHAFT_SENSOR_ERROR_SUPPORTED | `uint32` | 2 | Error of the crankshaft sensor. This flag is optional. |
|
||||
| <a id="#FLAG_CRANKSHAFT_SENSOR_ERROR"></a> FLAG_CRANKSHAFT_SENSOR_ERROR | `uint32` | 4 | |
|
||||
@@ -62,10 +85,17 @@ pageClass: is-wide-page
|
||||
| <a id="#FLAG_OIL_PRESSURE_ABOVE_NOMINAL"></a> FLAG_OIL_PRESSURE_ABOVE_NOMINAL | `uint32` | 131072 | Over-pressure warning |
|
||||
| <a id="#FLAG_DEBRIS_SUPPORTED"></a> FLAG_DEBRIS_SUPPORTED | `uint32` | 262144 | Debris warning. This flag is optional |
|
||||
| <a id="#FLAG_DEBRIS_DETECTED"></a> FLAG_DEBRIS_DETECTED | `uint32` | 524288 | Detection of debris warning |
|
||||
| <a id="#SPARK_PLUG_SINGLE"></a> SPARK_PLUG_SINGLE | `uint8` | 0 | |
|
||||
| <a id="#SPARK_PLUG_FIRST_ACTIVE"></a> SPARK_PLUG_FIRST_ACTIVE | `uint8` | 1 | |
|
||||
| <a id="#SPARK_PLUG_SECOND_ACTIVE"></a> SPARK_PLUG_SECOND_ACTIVE | `uint8` | 2 | |
|
||||
| <a id="#SPARK_PLUG_BOTH_ACTIVE"></a> SPARK_PLUG_BOTH_ACTIVE | `uint8` | 3 | |
|
||||
|
||||
### SPARK_PLUG {#SPARK_PLUG}
|
||||
|
||||
Used in field(s): [spark_plug_usage](#fld_spark_plug_usage)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ------------------------------------------------------------------------------------------------------------------------------ | ------- | -------- | ---- |
|
||||
| <a id="#SPARK_PLUG_SINGLE"></a> SPARK_PLUG_SINGLE | `uint8` | 0 | |
|
||||
| <a id="#SPARK_PLUG_FIRST_ACTIVE"></a> SPARK_PLUG_FIRST_ACTIVE | `uint8` | 1 | |
|
||||
| <a id="#SPARK_PLUG_SECOND_ACTIVE"></a> SPARK_PLUG_SECOND_ACTIVE | `uint8` | 2 | |
|
||||
| <a id="#SPARK_PLUG_BOTH_ACTIVE"></a> SPARK_PLUG_BOTH_ACTIVE | `uint8` | 3 | |
|
||||
|
||||
## Source Message
|
||||
|
||||
@@ -75,13 +105,18 @@ pageClass: is-wide-page
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
uint64 timestamp # time since system start (microseconds)
|
||||
uint64 timestamp # [us] Time since system start
|
||||
|
||||
uint8 STATE_STOPPED = 0 # The engine is not running. This is the default state.
|
||||
uint8 STATE_STARTING = 1 # The engine is starting. This is a transient state.
|
||||
uint8 STATE_RUNNING = 2 # The engine is running normally.
|
||||
uint8 STATE_FAULT = 3 # The engine can no longer function.
|
||||
uint8 state
|
||||
uint8 state # [@enum STATE] Engine state
|
||||
|
||||
uint8 SUBSTATE_RUN = 0 # The engine is running. This is the default state.
|
||||
uint8 SUBSTATE_IDLE = 1 # The engine idle rpm controller is running.
|
||||
uint8 SUBSTATE_REST = 2 # The engine is at rest.
|
||||
uint8 substate # [@enum SUBSTATE] Engine substate
|
||||
|
||||
uint32 FLAG_GENERAL_ERROR = 1 # General error.
|
||||
|
||||
@@ -110,35 +145,37 @@ uint32 FLAG_OIL_PRESSURE_ABOVE_NOMINAL = 131072 # Over-pressure warning
|
||||
|
||||
uint32 FLAG_DEBRIS_SUPPORTED = 262144 # Debris warning. This flag is optional
|
||||
uint32 FLAG_DEBRIS_DETECTED = 524288 # Detection of debris warning
|
||||
uint32 flags
|
||||
uint32 flags # [@enum FLAG] Engine status flags bitmap
|
||||
|
||||
uint8 engine_load_percent # Engine load estimate, percent, [0, 127]
|
||||
uint32 engine_speed_rpm # Engine speed, revolutions per minute
|
||||
float32 spark_dwell_time_ms # Spark dwell time, millisecond
|
||||
float32 atmospheric_pressure_kpa # Atmospheric (barometric) pressure, kilopascal
|
||||
float32 intake_manifold_pressure_kpa # Engine intake manifold pressure, kilopascal
|
||||
float32 intake_manifold_temperature # Engine intake manifold temperature, kelvin
|
||||
float32 coolant_temperature # Engine coolant temperature, kelvin
|
||||
float32 oil_pressure # Oil pressure, kilopascal
|
||||
float32 oil_temperature # Oil temperature, kelvin
|
||||
float32 fuel_pressure # Fuel pressure, kilopascal
|
||||
float32 fuel_consumption_rate_cm3pm # Instant fuel consumption estimate, (centimeter^3)/minute
|
||||
float32 estimated_consumed_fuel_volume_cm3 # Estimate of the consumed fuel since the start of the engine, centimeter^3
|
||||
uint8 throttle_position_percent # Throttle position, percent
|
||||
uint8 ecu_index # The index of the publishing ECU
|
||||
uint8 engine_load_percent # [%] [@range 0, 127] Engine load estimate
|
||||
uint32 engine_speed_rpm # [rpm] [@range 0, inf] Engine speed
|
||||
float32 spark_dwell_time_ms # [ms] [@range 0, inf] Spark dwell time
|
||||
float32 atmospheric_pressure_kpa # [kPa] [@range 0, inf] Atmospheric (barometric) pressure
|
||||
float32 intake_manifold_pressure_kpa # [kPa] [@range 0, inf] Engine intake manifold pressure
|
||||
float32 intake_manifold_temperature # [K] [@range 0, inf] Engine intake manifold temperature
|
||||
float32 coolant_temperature # [K] [@range 0, inf] Engine coolant temperature
|
||||
float32 oil_pressure # [kPa] [@range 0, inf] Oil pressure
|
||||
float32 oil_temperature # [K] [@range 0, inf] Oil temperature
|
||||
float32 fuel_pressure # [kPa] [@range 0, inf] Fuel pressure
|
||||
float32 fuel_consumption_rate_cm3pm # [cm^3/min] [@range 0, inf] Instant fuel consumption estimate
|
||||
float32 estimated_consumed_fuel_volume_cm3 # [cm^3] [@range 0, inf] Estimate of the consumed fuel since the start of the engine
|
||||
uint8 throttle_position_percent # [%] [@range 0, 100] Throttle position
|
||||
uint8 ecu_index # [-] [@range 0, 255] The index of the publishing ECU
|
||||
|
||||
|
||||
uint8 SPARK_PLUG_SINGLE = 0
|
||||
uint8 SPARK_PLUG_FIRST_ACTIVE = 1
|
||||
uint8 SPARK_PLUG_SECOND_ACTIVE = 2
|
||||
uint8 SPARK_PLUG_BOTH_ACTIVE = 3
|
||||
uint8 spark_plug_usage # Spark plug activity report.
|
||||
uint8 spark_plug_usage # [@enum SPARK_PLUG] Spark plug activity report
|
||||
|
||||
float32 ignition_timing_deg # Cylinder ignition timing, angular degrees of the crankshaft
|
||||
float32 injection_time_ms # Fuel injection time, millisecond
|
||||
float32 cylinder_head_temperature # Cylinder head temperature (CHT), kelvin
|
||||
float32 exhaust_gas_temperature # Exhaust gas temperature (EGT), kelvin
|
||||
float32 lambda_coefficient # Estimated lambda coefficient, dimensionless ratio
|
||||
float32 ignition_timing_deg # [deg] [@range -inf, inf] Cylinder ignition timing, angular degrees of the crankshaft
|
||||
float32 injection_time_ms # [ms] [@range 0, inf] Fuel injection time
|
||||
float32 cylinder_head_temperature # [K] [@range 0, inf] Cylinder head temperature (CHT)
|
||||
float32 exhaust_gas_temperature # [K] [@range 0, inf] Exhaust gas temperature (EGT)
|
||||
float32 lambda_coefficient # [-] [@range 0, inf] Estimated lambda coefficient, dimensionless ratio
|
||||
|
||||
float32 pid_idle_rpm_integral # [-] [@range -1, 1] Integral of the PID for the closed loop idle RPM controller
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
@@ -8,25 +8,25 @@ pageClass: is-wide-page
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ---------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | | | the timestamp of the raw data (microseconds) |
|
||||
| <a id="fld_valid"></a>valid | `bool` | | | |
|
||||
| <a id="fld_data_source"></a>data_source | `uint8` | | | |
|
||||
| <a id="fld_roll"></a>roll | `float32` | | | move right, positive roll rotation, right side down |
|
||||
| <a id="fld_pitch"></a>pitch | `float32` | | | move forward, negative pitch rotation, nose down |
|
||||
| <a id="fld_yaw"></a>yaw | `float32` | | | positive yaw rotation, clockwise when seen top down |
|
||||
| <a id="fld_throttle"></a>throttle | `float32` | | | move up, positive thrust, -1 is minimum available 0% or -100% +1 is 100% thrust |
|
||||
| <a id="fld_flaps"></a>flaps | `float32` | | | position of flaps switch/knob/lever [-1, 1] |
|
||||
| <a id="fld_aux1"></a>aux1 | `float32` | | | |
|
||||
| <a id="fld_aux2"></a>aux2 | `float32` | | | |
|
||||
| <a id="fld_aux3"></a>aux3 | `float32` | | | |
|
||||
| <a id="fld_aux4"></a>aux4 | `float32` | | | |
|
||||
| <a id="fld_aux5"></a>aux5 | `float32` | | | |
|
||||
| <a id="fld_aux6"></a>aux6 | `float32` | | | |
|
||||
| <a id="fld_sticks_moving"></a>sticks_moving | `bool` | | | |
|
||||
| <a id="fld_buttons"></a>buttons | `uint16` | | | From uint16 buttons field of Mavlink manual_control message |
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ---------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | | | the timestamp of the raw data (microseconds) |
|
||||
| <a id="fld_valid"></a>valid | `bool` | | | |
|
||||
| <a id="fld_data_source"></a>data_source | `uint8` | | | |
|
||||
| <a id="fld_roll"></a>roll | `float32` | | | move right, positive roll rotation, right side down |
|
||||
| <a id="fld_pitch"></a>pitch | `float32` | | | move forward, negative pitch rotation, nose down |
|
||||
| <a id="fld_yaw"></a>yaw | `float32` | | | positive yaw rotation, clockwise when seen top down |
|
||||
| <a id="fld_throttle"></a>throttle | `float32` | | | move up, positive thrust, -1 is minimum available 0% or -100% +1 is 100% thrust |
|
||||
| <a id="fld_flaps"></a>flaps | `float32` | | | position of flaps switch/knob/lever [-1, 1] |
|
||||
| <a id="fld_aux1"></a>aux1 | `float32` | | | |
|
||||
| <a id="fld_aux2"></a>aux2 | `float32` | | | |
|
||||
| <a id="fld_aux3"></a>aux3 | `float32` | | | |
|
||||
| <a id="fld_aux4"></a>aux4 | `float32` | | | |
|
||||
| <a id="fld_aux5"></a>aux5 | `float32` | | | |
|
||||
| <a id="fld_aux6"></a>aux6 | `float32` | | | |
|
||||
| <a id="fld_sticks_moving"></a>sticks_moving | `bool` | | | manual control override request in an auto or offboard mode, only gets true if feature is enabled |
|
||||
| <a id="fld_buttons"></a>buttons | `uint16` | | | From uint16 buttons field of Mavlink manual_control message |
|
||||
|
||||
## Constants
|
||||
|
||||
@@ -89,7 +89,7 @@ float32 aux4
|
||||
float32 aux5
|
||||
float32 aux6
|
||||
|
||||
bool sticks_moving
|
||||
bool sticks_moving # manual control override request in an auto or offboard mode, only gets true if feature is enabled
|
||||
|
||||
uint16 buttons # From uint16 buttons field of Mavlink manual_control message
|
||||
|
||||
|
||||
@@ -0,0 +1,34 @@
|
||||
---
|
||||
pageClass: is-wide-page
|
||||
---
|
||||
|
||||
# OpenDroneIdBasicId (UORB message)
|
||||
|
||||
**TOPICS:** open_drone_id_basic_id
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ----------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | |
|
||||
| <a id="fld_id_or_mac"></a>id_or_mac | `uint8[20]` | | | Only used for drone ID data received from other UAs, no null termination, null filled if shorter |
|
||||
| <a id="fld_id_type"></a>id_type | `uint8` | | | MAV_ODID_ID_TYPE: indicates the format for the uas_id field |
|
||||
| <a id="fld_ua_type"></a>ua_type | `uint8` | | | MAV_ODID_UA_TYPE: indicates the type of UA (Unmanned Aircraft) |
|
||||
| <a id="fld_uas_id"></a>uas_id | `uint8[20]` | | | UAS (Unmanned Aircraft System) ID following the format specified by id_type, no null termination, null filled if shorter |
|
||||
|
||||
## Source Message
|
||||
|
||||
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/OpenDroneIdBasicId.msg)
|
||||
|
||||
:::details
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
uint64 timestamp
|
||||
uint8[20] id_or_mac # Only used for drone ID data received from other UAs, no null termination, null filled if shorter
|
||||
uint8 id_type # MAV_ODID_ID_TYPE: indicates the format for the uas_id field
|
||||
uint8 ua_type # MAV_ODID_UA_TYPE: indicates the type of UA (Unmanned Aircraft)
|
||||
uint8[20] uas_id # UAS (Unmanned Aircraft System) ID following the format specified by id_type, no null termination, null filled if shorter
|
||||
```
|
||||
|
||||
:::
|
||||
@@ -30,7 +30,7 @@ Request to register an external component.
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| --------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 2 | |
|
||||
| <a id="#LATEST_PX4_ROS2_API_VERSION"></a> LATEST_PX4_ROS2_API_VERSION | `uint16` | 1 | API version compatibility. Increase this on a breaking semantic change. Changes to any message field are detected separately and do not require an API version change. |
|
||||
| <a id="#LATEST_PX4_ROS2_API_VERSION"></a> LATEST_PX4_ROS2_API_VERSION | `uint16` | 2 | API version compatibility. Increase this on a breaking semantic change. Changes to any message field are detected separately and do not require an API version change. |
|
||||
| <a id="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH | `uint8` | 2 | |
|
||||
|
||||
## Source Message
|
||||
@@ -50,7 +50,7 @@ uint64 timestamp # time since system start (microseconds)
|
||||
uint64 request_id # ID, set this to a random value
|
||||
char[25] name # either the requested mode name, or component name
|
||||
|
||||
uint16 LATEST_PX4_ROS2_API_VERSION = 1 # API version compatibility. Increase this on a breaking semantic change. Changes to any message field are detected separately and do not require an API version change.
|
||||
uint16 LATEST_PX4_ROS2_API_VERSION = 2 # API version compatibility. Increase this on a breaking semantic change. Changes to any message field are detected separately and do not require an API version change.
|
||||
|
||||
uint16 px4_ros2_api_version # Set to LATEST_PX4_ROS2_API_VERSION
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ The information is published in the `SCALED_PRESSURE_n` MAVLink messages (along
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | us | | Time of raw data capture |
|
||||
| <a id="fld_device_id"></a>device_id | `uint32` | | | Unique device ID for the sensor that does not change between power cycles |
|
||||
| <a id="fld_pressure"></a>pressure | `float32` | Pa | | Static pressure measurement |
|
||||
| <a id="fld_temperature"></a>temperature | `float32` | degC | | Temperature. |
|
||||
| <a id="fld_temperature"></a>temperature | `float32` | °C | | Temperature. |
|
||||
| <a id="fld_error_count"></a>error_count | `uint32` | | | Number of errors detected by driver. |
|
||||
|
||||
## Constants
|
||||
@@ -46,7 +46,7 @@ uint64 timestamp_sample # [us] Time of raw data capture
|
||||
|
||||
uint32 device_id # [-] Unique device ID for the sensor that does not change between power cycles
|
||||
float32 pressure # [Pa] Static pressure measurement
|
||||
float32 temperature # [degC] Temperature.
|
||||
float32 temperature # [°C] Temperature.
|
||||
uint32 error_count # [-] Number of errors detected by driver.
|
||||
|
||||
uint8 ORB_QUEUE_LENGTH = 4
|
||||
|
||||
@@ -13,10 +13,10 @@ pageClass: is-wide-page
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | | | |
|
||||
| <a id="fld_device_id"></a>device_id | `uint32` | | | unique device ID for the sensor that does not change between power cycles |
|
||||
| <a id="fld_x"></a>x | `float32` | | | magnetic field in the FRD board frame X-axis in Gauss |
|
||||
| <a id="fld_y"></a>y | `float32` | | | magnetic field in the FRD board frame Y-axis in Gauss |
|
||||
| <a id="fld_z"></a>z | `float32` | | | magnetic field in the FRD board frame Z-axis in Gauss |
|
||||
| <a id="fld_temperature"></a>temperature | `float32` | | | temperature in degrees Celsius |
|
||||
| <a id="fld_x"></a>x | `float32` | Gauss | | magnetic field in the FRD board frame X-axis |
|
||||
| <a id="fld_y"></a>y | `float32` | Gauss | | magnetic field in the FRD board frame Y-axis |
|
||||
| <a id="fld_z"></a>z | `float32` | Gauss | | magnetic field in the FRD board frame Z-axis |
|
||||
| <a id="fld_temperature"></a>temperature | `float32` | °C | | Temperature. |
|
||||
| <a id="fld_error_count"></a>error_count | `uint32` | | | |
|
||||
|
||||
## Constants
|
||||
@@ -38,11 +38,11 @@ uint64 timestamp_sample
|
||||
|
||||
uint32 device_id # unique device ID for the sensor that does not change between power cycles
|
||||
|
||||
float32 x # magnetic field in the FRD board frame X-axis in Gauss
|
||||
float32 y # magnetic field in the FRD board frame Y-axis in Gauss
|
||||
float32 z # magnetic field in the FRD board frame Z-axis in Gauss
|
||||
float32 x # [Gauss] magnetic field in the FRD board frame X-axis
|
||||
float32 y # [Gauss] magnetic field in the FRD board frame Y-axis
|
||||
float32 z # [Gauss] magnetic field in the FRD board frame Z-axis
|
||||
|
||||
float32 temperature # temperature in degrees Celsius
|
||||
float32 temperature # [°C] Temperature.
|
||||
|
||||
uint32 error_count
|
||||
|
||||
|
||||
@@ -0,0 +1,98 @@
|
||||
---
|
||||
pageClass: is-wide-page
|
||||
---
|
||||
|
||||
# SetpointConfig (UORB message)
|
||||
|
||||
Setpoint configuration message.
|
||||
|
||||
Published by external modes and PX4 will respond with SetpointConfigReply.
|
||||
|
||||
**TOPICS:** setpoint_config
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| -------------------------------------------------------------- | -------- | ---------------------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_type"></a>type | `uint16` | | [TYPE](#TYPE) | setpoint type (corresponding to one or more setpoint messages) |
|
||||
| <a id="fld_source_id"></a>source_id | `uint8` | | | nav_state of the mode |
|
||||
| <a id="fld_should_apply"></a>should_apply | `bool` | | | if true: apply as current setpoint configuration (mode should be active). If false: setpoint configuration is not changed (can be used to check if a setpoint can be used with the current vehicle configuration). |
|
||||
| <a id="fld_timeout_ms"></a>timeout_ms | `uint16` | | | Configure setpoint timeout. If no setpoint received for this time, PX4 triggers a failsafe. 0 disables the timeout (unresponsive modes still trigger a timeout through arming checks). |
|
||||
|
||||
## Enums
|
||||
|
||||
### TYPE {#TYPE}
|
||||
|
||||
Used in field(s): [type](#fld_type)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | ---------------------------------------------------------- |
|
||||
| <a id="#TYPE_INVALID"></a> TYPE_INVALID | `uint16` | 0 | |
|
||||
| <a id="#TYPE_DIRECT_ACTUATORS"></a> TYPE_DIRECT_ACTUATORS | `uint16` | 1 | ActuatorMotors and ActuatorServos |
|
||||
| <a id="#TYPE_MULTICOPTER_GOTO"></a> TYPE_MULTICOPTER_GOTO | `uint16` | 2 | GotoSetpoint |
|
||||
| <a id="#TYPE_FIXEDWING_LATERAL_LONGITUDINAL"></a> TYPE_FIXEDWING_LATERAL_LONGITUDINAL | `uint16` | 3 | FixedWingLateralSetpoint and FixedWingLongitudinalSetpoint |
|
||||
| <a id="#TYPE_TRAJECTORY"></a> TYPE_TRAJECTORY | `uint16` | 4 | TrajectorySetpoint |
|
||||
| <a id="#TYPE_RATES"></a> TYPE_RATES | `uint16` | 5 | VehicleRatesSetpoint |
|
||||
| <a id="#TYPE_ATTITUDE"></a> TYPE_ATTITUDE | `uint16` | 6 | VehicleAttitudeSetpoint |
|
||||
| <a id="#TYPE_ROVER_POSITION"></a> TYPE_ROVER_POSITION | `uint16` | 7 | RoverPositionSetpoint |
|
||||
| <a id="#TYPE_ROVER_SPEED_ATTITUDE"></a> TYPE_ROVER_SPEED_ATTITUDE | `uint16` | 8 | RoverSpeedSetpoint and RoverAttitudeSetpoint |
|
||||
| <a id="#TYPE_ROVER_SPEED_RATE"></a> TYPE_ROVER_SPEED_RATE | `uint16` | 9 | RoverSpeedSetpoint and RoverRateSetpoint |
|
||||
| <a id="#TYPE_ROVER_SPEED_STEERING"></a> TYPE_ROVER_SPEED_STEERING | `uint16` | 10 | RoverSpeedSetpoint and RoverSteeringSetpoint |
|
||||
| <a id="#TYPE_ROVER_THROTTLE_ATTITUDE"></a> TYPE_ROVER_THROTTLE_ATTITUDE | `uint16` | 11 | RoverThrottleSetpoint and RoverAttitudeSetpoint |
|
||||
| <a id="#TYPE_ROVER_THROTTLE_RATE"></a> TYPE_ROVER_THROTTLE_RATE | `uint16` | 12 | RoverThrottleSetpoint and RoverRateSetpoint |
|
||||
| <a id="#TYPE_ROVER_THROTTLE_STEERING"></a> TYPE_ROVER_THROTTLE_STEERING | `uint16` | 13 | RoverThrottleSetpoint and RoverSteeringSetpoint |
|
||||
| <a id="#TYPE_TRAJECTORY_6DOF"></a> TYPE_TRAJECTORY_6DOF | `uint16` | 14 | TrajectorySetpoint6dof |
|
||||
| <a id="#TYPE_THRUST_AND_TORQUE"></a> TYPE_THRUST_AND_TORQUE | `uint16` | 15 | VehicleThrustSetpoint and VehicleTorqueSetpoint |
|
||||
| <a id="#TYPE_POSITION_TRIPLET"></a> TYPE_POSITION_TRIPLET | `uint16` | 16 | PositionSetpointTriplet |
|
||||
|
||||
## Constants
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ------------------------------------------------------------------ | -------- | -------- | ---- |
|
||||
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
|
||||
|
||||
## Source Message
|
||||
|
||||
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/SetpointConfig.msg)
|
||||
|
||||
:::details
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
# Setpoint configuration message
|
||||
#
|
||||
# Published by external modes and PX4 will respond with SetpointConfigReply.
|
||||
|
||||
uint32 MESSAGE_VERSION = 0
|
||||
|
||||
uint64 timestamp # [us] Time since system start
|
||||
|
||||
uint16 TYPE_INVALID = 0
|
||||
uint16 TYPE_DIRECT_ACTUATORS = 1 # ActuatorMotors and ActuatorServos
|
||||
uint16 TYPE_MULTICOPTER_GOTO = 2 # GotoSetpoint
|
||||
uint16 TYPE_FIXEDWING_LATERAL_LONGITUDINAL = 3 # FixedWingLateralSetpoint and FixedWingLongitudinalSetpoint
|
||||
uint16 TYPE_TRAJECTORY = 4 # TrajectorySetpoint
|
||||
uint16 TYPE_RATES = 5 # VehicleRatesSetpoint
|
||||
uint16 TYPE_ATTITUDE = 6 # VehicleAttitudeSetpoint
|
||||
uint16 TYPE_ROVER_POSITION = 7 # RoverPositionSetpoint
|
||||
uint16 TYPE_ROVER_SPEED_ATTITUDE = 8 # RoverSpeedSetpoint and RoverAttitudeSetpoint
|
||||
uint16 TYPE_ROVER_SPEED_RATE = 9 # RoverSpeedSetpoint and RoverRateSetpoint
|
||||
uint16 TYPE_ROVER_SPEED_STEERING = 10 # RoverSpeedSetpoint and RoverSteeringSetpoint
|
||||
uint16 TYPE_ROVER_THROTTLE_ATTITUDE = 11 # RoverThrottleSetpoint and RoverAttitudeSetpoint
|
||||
uint16 TYPE_ROVER_THROTTLE_RATE = 12 # RoverThrottleSetpoint and RoverRateSetpoint
|
||||
uint16 TYPE_ROVER_THROTTLE_STEERING = 13 # RoverThrottleSetpoint and RoverSteeringSetpoint
|
||||
uint16 TYPE_TRAJECTORY_6DOF = 14 # TrajectorySetpoint6dof
|
||||
uint16 TYPE_THRUST_AND_TORQUE = 15 # VehicleThrustSetpoint and VehicleTorqueSetpoint
|
||||
uint16 TYPE_POSITION_TRIPLET = 16 # PositionSetpointTriplet
|
||||
|
||||
uint16 type # [@enum TYPE] setpoint type (corresponding to one or more setpoint messages)
|
||||
|
||||
uint8 source_id # nav_state of the mode
|
||||
|
||||
bool should_apply # if true: apply as current setpoint configuration (mode should be active). If false: setpoint configuration is not changed (can be used to check if a setpoint can be used with the current vehicle configuration).
|
||||
|
||||
uint16 timeout_ms # Configure setpoint timeout. If no setpoint received for this time, PX4 triggers a failsafe. 0 disables the timeout (unresponsive modes still trigger a timeout through arming checks).
|
||||
```
|
||||
|
||||
:::
|
||||
@@ -0,0 +1,75 @@
|
||||
---
|
||||
pageClass: is-wide-page
|
||||
---
|
||||
|
||||
# SetpointConfigReply (UORB message)
|
||||
|
||||
Reply to SetpointConfig.
|
||||
|
||||
**TOPICS:** setpoint_config_reply
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ---------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_type"></a>type | `uint16` | | | See SetpointConfig::TYPE\_\* |
|
||||
| <a id="fld_source_id"></a>source_id | `uint8` | | | nav_state of the mode that sent the SetpointConfig |
|
||||
| <a id="fld_result"></a>result | `uint8` | | [RESULT](#RESULT) | |
|
||||
| <a id="fld_mode_req_angular_velocity"></a>mode_req_angular_velocity | `bool` | | | |
|
||||
| <a id="fld_mode_req_attitude"></a>mode_req_attitude | `bool` | | | |
|
||||
| <a id="fld_mode_req_local_alt"></a>mode_req_local_alt | `bool` | | | |
|
||||
| <a id="fld_mode_req_local_position"></a>mode_req_local_position | `bool` | | | |
|
||||
|
||||
## Enums
|
||||
|
||||
### RESULT {#RESULT}
|
||||
|
||||
Used in field(s): [result](#fld_result)
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- | ---------------------------------------------------- |
|
||||
| <a id="#RESULT_SUCCESS"></a> RESULT_SUCCESS | `uint8` | 0 | |
|
||||
| <a id="#RESULT_FAILURE_OTHER"></a> RESULT_FAILURE_OTHER | `uint8` | 1 | |
|
||||
| <a id="#RESULT_UNSUPPORTED"></a> RESULT_UNSUPPORTED | `uint8` | 2 | Setpoint type is unsupported for the current vehicle |
|
||||
| <a id="#RESULT_UNKNOWN_SETPOINT_TYPE"></a> RESULT_UNKNOWN_SETPOINT_TYPE | `uint8` | 3 | The setpoint type is not known |
|
||||
|
||||
## Constants
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ------------------------------------------------------------------ | -------- | -------- | ---- |
|
||||
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
|
||||
|
||||
## Source Message
|
||||
|
||||
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/SetpointConfigReply.msg)
|
||||
|
||||
:::details
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
# Reply to SetpointConfig
|
||||
|
||||
uint32 MESSAGE_VERSION = 0
|
||||
|
||||
uint64 timestamp # [us] Time since system start
|
||||
|
||||
uint16 type # See SetpointConfig::TYPE_*
|
||||
|
||||
uint8 source_id # nav_state of the mode that sent the SetpointConfig
|
||||
|
||||
uint8 RESULT_SUCCESS = 0
|
||||
uint8 RESULT_FAILURE_OTHER = 1
|
||||
uint8 RESULT_UNSUPPORTED = 2 # Setpoint type is unsupported for the current vehicle
|
||||
uint8 RESULT_UNKNOWN_SETPOINT_TYPE = 3 # The setpoint type is not known
|
||||
uint8 result # [@enum RESULT]
|
||||
|
||||
# Mode requirements for using the given setpoint type. A mode will use these and apply them to the arming check reply (PX4 does not do that itself).
|
||||
# Certain setpoint types can be used in a reduced way, for example a TrajectorySetpoint without position control. In that case PX4 still sets all requirement flags, and the mode will then ignore mode_req_local_position.
|
||||
bool mode_req_angular_velocity
|
||||
bool mode_req_attitude
|
||||
bool mode_req_local_alt
|
||||
bool mode_req_local_position
|
||||
```
|
||||
|
||||
:::
|
||||
@@ -1528,6 +1528,20 @@ Change mode by specifying nav_state directly.
|
||||
| 6 | | | Unused |
|
||||
| 7 | | | Unused |
|
||||
|
||||
### VEHICLE_CMD_DO_SET_GLOBAL_ORIGIN (611)
|
||||
|
||||
Sets GNSS coordinates of the vehicle local origin (0,0,0) position. Send as COMMAND_INT with MAV_FRAME_GLOBAL_INT.
|
||||
|
||||
| Param | Units | Range/Enum | Опис |
|
||||
| ----- | ----- | ---------- | ------------------------------------- |
|
||||
| 1 | | | Unused |
|
||||
| 2 | | | Unused |
|
||||
| 3 | | | Unused |
|
||||
| 4 | | | Unused |
|
||||
| 5 | | | Latitude (WGS-84) |
|
||||
| 6 | | | Longitude (WGS-84) |
|
||||
| 7 | m | | Altitude (AMSL) |
|
||||
|
||||
### VEHICLE_CMD_GUIDED_CHANGE_HEADING (43002)
|
||||
|
||||
Change heading/course. param1: heading type (0=course-over-ground, 1=heading). param2: target [deg]. param3: max rate [deg/s].
|
||||
@@ -1797,6 +1811,7 @@ uint32 VEHICLE_CMD_PX4_INTERNAL_START = 65537 # Start of PX4 internal only vehic
|
||||
uint32 VEHICLE_CMD_SET_GPS_GLOBAL_ORIGIN = 100000 # Sets the GPS coordinates of the vehicle local origin (0,0,0) position. |Unused|Unused|Unused|Unused|Latitude (WGS-84)|Longitude (WGS-84)|[m] Altitude (AMSL from GNSS, positive above ground)|
|
||||
uint32 VEHICLE_CMD_SET_NAV_STATE = 100001 # Change mode by specifying nav_state directly. |nav_state|Unused|Unused|Unused|Unused|Unused|Unused|
|
||||
|
||||
uint16 VEHICLE_CMD_DO_SET_GLOBAL_ORIGIN = 611 # Sets GNSS coordinates of the vehicle local origin (0,0,0) position. Send as COMMAND_INT with MAV_FRAME_GLOBAL_INT. |Unused|Unused|Unused|Unused|Latitude (WGS-84)|Longitude (WGS-84)|[m] Altitude (AMSL)|
|
||||
uint16 VEHICLE_CMD_GUIDED_CHANGE_HEADING = 43002 # Change heading/course. param1: heading type (0=course-over-ground, 1=heading). param2: target [deg]. param3: max rate [deg/s]. |Heading type (HEADING_TYPE enum)|[deg] Target bearing [0..360]|[deg/s] Max rate of change|Unused|Unused|Unused|Unused|
|
||||
|
||||
uint8 VEHICLE_MOUNT_MODE_RETRACT = 0 # Load and keep safe position (Roll,Pitch,Yaw) from permanent memory and stop stabilization.
|
||||
|
||||
@@ -4,7 +4,9 @@ pageClass: is-wide-page
|
||||
|
||||
# VehicleControlMode (повідомлення UORB)
|
||||
|
||||
**TOPICS:** vehicle_control_mode config_control_setpoints
|
||||
Defines which controllers should run.
|
||||
|
||||
**TOPICS:** vehicle_control_mode
|
||||
|
||||
## Fields
|
||||
|
||||
@@ -20,28 +22,19 @@ pageClass: is-wide-page
|
||||
| <a id="fld_flag_control_velocity_enabled"></a>flag_control_velocity_enabled | `bool` | | | true if horizontal velocity (implies direction) is controlled |
|
||||
| <a id="fld_flag_control_altitude_enabled"></a>flag_control_altitude_enabled | `bool` | | | true if altitude is controlled |
|
||||
| <a id="fld_flag_control_climb_rate_enabled"></a>flag_control_climb_rate_enabled | `bool` | | | true if climb rate is controlled |
|
||||
| <a id="fld_flag_control_acceleration_enabled"></a>flag_control_acceleration_enabled | `bool` | | | true if acceleration is controlled |
|
||||
| <a id="fld_flag_control_attitude_enabled"></a>flag_control_attitude_enabled | `bool` | | | true if attitude stabilization is mixed in |
|
||||
| <a id="fld_flag_control_rates_enabled"></a>flag_control_rates_enabled | `bool` | | | true if rates are stabilized |
|
||||
| <a id="fld_flag_control_allocation_enabled"></a>flag_control_allocation_enabled | `bool` | | | true if control allocation is enabled |
|
||||
| <a id="fld_flag_control_termination_enabled"></a>flag_control_termination_enabled | `bool` | | | true if flighttermination is enabled |
|
||||
| <a id="fld_source_id"></a>source_id | `uint8` | | | Mode ID (nav_state) |
|
||||
|
||||
## Constants
|
||||
|
||||
| Назва | Тип | Значення | Опис |
|
||||
| ------------------------------------------------------------------ | -------- | -------- | ---- |
|
||||
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
|
||||
|
||||
## Source Message
|
||||
|
||||
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleControlMode.msg)
|
||||
[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleControlMode.msg)
|
||||
|
||||
:::details
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
uint32 MESSAGE_VERSION = 0
|
||||
# Defines which controllers should run
|
||||
|
||||
uint64 timestamp # time since system start (microseconds)
|
||||
bool flag_armed # synonym for actuator_armed.armed
|
||||
@@ -55,16 +48,9 @@ bool flag_control_position_enabled # true if position is controlled
|
||||
bool flag_control_velocity_enabled # true if horizontal velocity (implies direction) is controlled
|
||||
bool flag_control_altitude_enabled # true if altitude is controlled
|
||||
bool flag_control_climb_rate_enabled # true if climb rate is controlled
|
||||
bool flag_control_acceleration_enabled # true if acceleration is controlled
|
||||
bool flag_control_attitude_enabled # true if attitude stabilization is mixed in
|
||||
bool flag_control_rates_enabled # true if rates are stabilized
|
||||
bool flag_control_allocation_enabled # true if control allocation is enabled
|
||||
bool flag_control_termination_enabled # true if flighttermination is enabled
|
||||
|
||||
# TODO: use dedicated topic for external requests
|
||||
uint8 source_id # Mode ID (nav_state)
|
||||
|
||||
# TOPICS vehicle_control_mode config_control_setpoints
|
||||
```
|
||||
|
||||
:::
|
||||
|
||||
@@ -4,15 +4,19 @@ pageClass: is-wide-page
|
||||
|
||||
# VehicleThrustSetpoint (повідомлення UORB)
|
||||
|
||||
Vehicle thrust setpoint.
|
||||
|
||||
This is the thrust setpoint provided by the controller and fed into the control allocator.
|
||||
|
||||
**TOPICS:** vehicle_thrust_setpoint vehicle_thrust_setpoint_virtual_fw vehicle_thrust_setpoint_virtual_mc
|
||||
|
||||
## Fields
|
||||
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ---------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | | | timestamp of the data sample on which this message is based (microseconds) |
|
||||
| <a id="fld_xyz"></a>xyz | `float32[3]` | | | thrust setpoint along X, Y, Z body axis [-1, 1] |
|
||||
| Назва | Тип | Unit [Frame] | Range/Enum | Опис |
|
||||
| ---------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <a id="fld_timestamp"></a>timestamp | `uint64` | us | | Time since system start |
|
||||
| <a id="fld_timestamp_sample"></a>timestamp_sample | `uint64` | us | | Timestamp of the data sample on which this message is based |
|
||||
| <a id="fld_xyz"></a>xyz | `float32[3]` | | [-1 : 1] | Thrust setpoint along X, Y, Z body axis. If set to NAN the motors affecting this axis are stopped. |
|
||||
|
||||
## Source Message
|
||||
|
||||
@@ -22,10 +26,14 @@ pageClass: is-wide-page
|
||||
Click here to see original file
|
||||
|
||||
```c
|
||||
uint64 timestamp # time since system start (microseconds)
|
||||
uint64 timestamp_sample # timestamp of the data sample on which this message is based (microseconds)
|
||||
# Vehicle thrust setpoint
|
||||
#
|
||||
# This is the thrust setpoint provided by the controller and fed into the control allocator.
|
||||
|
||||
float32[3] xyz # thrust setpoint along X, Y, Z body axis [-1, 1]
|
||||
uint64 timestamp # [us] Time since system start
|
||||
uint64 timestamp_sample # [us] Timestamp of the data sample on which this message is based
|
||||
|
||||
float32[3] xyz # [-] [@range -1, 1] Thrust setpoint along X, Y, Z body axis. If set to NAN the motors affecting this axis are stopped.
|
||||
|
||||
# TOPICS vehicle_thrust_setpoint
|
||||
# TOPICS vehicle_thrust_setpoint_virtual_fw vehicle_thrust_setpoint_virtual_mc
|
||||
|
||||
@@ -36,6 +36,8 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [RaptorStatus](RaptorStatus.md) — Raptor Status.
|
||||
- [RegisterExtComponentReply](RegisterExtComponentReply.md)
|
||||
- [RegisterExtComponentRequest](RegisterExtComponentRequest.md) — Request to register an external component.
|
||||
- [SetpointConfig](SetpointConfig.md) — Setpoint configuration message.
|
||||
- [SetpointConfigReply](SetpointConfigReply.md) — Reply to SetpointConfig.
|
||||
- [TrajectorySetpoint](TrajectorySetpoint.md) — Trajectory setpoint in NED frame. Input to PID position controller. Потрібно мати кінематичну консистентність і бути можливим для плавного польоту. setting a value to NaN means the state should not be controlled.
|
||||
- [UnregisterExtComponent](UnregisterExtComponent.md)
|
||||
- [VehicleAngularVelocity](VehicleAngularVelocity.md)
|
||||
@@ -43,7 +45,6 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [VehicleAttitudeSetpoint](VehicleAttitudeSetpoint.md)
|
||||
- [VehicleCommand](VehicleCommand.md) — Vehicle Command uORB message. Використовується для управління місією / дією / тощо. Follows the MAVLink COMMAND_INT / COMMAND_LONG definition.
|
||||
- [VehicleCommandAck](VehicleCommandAck.md) — Vehicle Command Acknowledgement uORB message.
|
||||
- [VehicleControlMode](VehicleControlMode.md)
|
||||
- [VehicleGlobalPosition](VehicleGlobalPosition.md) — Fused global position in WGS84. This struct contains global position estimation. It is not the raw GPS. measurement (@see vehicle_gps_position). This topic is usually published by the position. estimator, which will take more sources of information into account than just GPS,. e.g. control inputs of the vehicle in a Kalman-filter implementation.
|
||||
- [VehicleLandDetected](VehicleLandDetected.md)
|
||||
- [VehicleLocalPosition](VehicleLocalPosition.md) — Fused local position in NED. The coordinate system origin is the vehicle position at the time when the EKF2-module was started.
|
||||
@@ -129,6 +130,7 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [EstimatorStatusFlags](EstimatorStatusFlags.md)
|
||||
- [FailsafeFlags](FailsafeFlags.md) — Input flags for the failsafe state machine set by the arming & health checks.
|
||||
- [FailureDetectorStatus](FailureDetectorStatus.md)
|
||||
- [FailureInjection](FailureInjection.md) — Failure injection configuration.
|
||||
- [FiducialMarkerPosReport](FiducialMarkerPosReport.md) — Relative position of a precision-landing target detected by a vision pipeline (e.g. an ArUco marker).
|
||||
- [FiducialMarkerYawReport](FiducialMarkerYawReport.md) — Yaw of a precision-landing target relative to the NED (North, East, Down) frame, reported by a vision pipeline.
|
||||
- [FigureEightStatus](FigureEightStatus.md)
|
||||
@@ -193,6 +195,7 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [OffboardControlMode](OffboardControlMode.md) — Off-board control mode.
|
||||
- [OnboardComputerStatus](OnboardComputerStatus.md) — ONBOARD_COMPUTER_STATUS message data.
|
||||
- [OpenDroneIdArmStatus](OpenDroneIdArmStatus.md)
|
||||
- [OpenDroneIdBasicId](OpenDroneIdBasicId.md)
|
||||
- [OpenDroneIdOperatorId](OpenDroneIdOperatorId.md)
|
||||
- [OpenDroneIdSelfId](OpenDroneIdSelfId.md)
|
||||
- [OpenDroneIdSystem](OpenDroneIdSystem.md)
|
||||
@@ -275,8 +278,8 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [UlogStreamAck](UlogStreamAck.md) — Ack a previously sent ulog_stream message that had. the NEED_ACK flag set.
|
||||
- [VehicleAcceleration](VehicleAcceleration.md)
|
||||
- [VehicleAirData](VehicleAirData.md) — Vehicle air data.
|
||||
- [VehicleAngularAccelerationSetpoint](VehicleAngularAccelerationSetpoint.md)
|
||||
- [VehicleConstraints](VehicleConstraints.md) — Local setpoint constraints in NED frame. setting something to NaN means that no limit is provided.
|
||||
- [VehicleControlMode](VehicleControlMode.md) — Defines which controllers should run.
|
||||
- [VehicleImu](VehicleImu.md) — IMU readings in SI-unit form.
|
||||
- [VehicleImuStatus](VehicleImuStatus.md)
|
||||
- [VehicleLocalPositionSetpoint](VehicleLocalPositionSetpoint.md) — Local position setpoint in NED frame. Telemetry of PID position controller to monitor tracking. NaN means the state was not controlled.
|
||||
@@ -284,7 +287,7 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
|
||||
- [VehicleOpticalFlow](VehicleOpticalFlow.md) — Optical flow in XYZ body frame in SI units.
|
||||
- [VehicleOpticalFlowVel](VehicleOpticalFlowVel.md)
|
||||
- [VehicleRoi](VehicleRoi.md) — Vehicle Region Of Interest (ROI).
|
||||
- [VehicleThrustSetpoint](VehicleThrustSetpoint.md)
|
||||
- [VehicleThrustSetpoint](VehicleThrustSetpoint.md) — Vehicle thrust setpoint.
|
||||
- [VehicleTorqueSetpoint](VehicleTorqueSetpoint.md)
|
||||
- [VelocityLimits](VelocityLimits.md) — Velocity and yaw rate limits for a multicopter position slow mode only.
|
||||
- [VteAidSource1d](VteAidSource1d.md) — Vision Target Estimator 1D fusion aid-source diagnostics (e.g. yaw).
|
||||
|
||||
@@ -17,7 +17,7 @@ Note that after training the network you will need to update and rebuild PX4.
|
||||
|
||||
TLFM is a mature inference library intended for use on embedded devices.
|
||||
It has support for several architectures, so there is a high likelihood that you can build it for the board you want to use.
|
||||
If not, there are other possible NN frameworks, such as [Eigen](https://eigen.tuxfamily.org/index.php?title=Main_Page) and [Executorch](https://docs.pytorch.org/executorch/stable/intro-overview.html).
|
||||
If not, there are other possible NN frameworks, such as [Eigen](https://libeigen.gitlab.io/) and [Executorch](https://docs.pytorch.org/executorch/stable/intro-overview.html).
|
||||
|
||||
This document explains how you can include the module in your PX4 build, and provides a broad overview of how it works.
|
||||
The other documents in the section provide more information about the integration, allowing you to replace the NN with a version trained on different data, or even to replace the TLFM library altogether.
|
||||
|
||||
@@ -18,7 +18,7 @@ A line to autostart the [mc_nn_control](../modules/modules_controller.md#mc-nn-c
|
||||
|
||||
It checks whether the module is included by looking for the parameter [MC_NN_EN](../advanced_config/parameter_reference.md#MC_NN_EN).
|
||||
If this is set to `1` (the default value), the module will be started when booting PX4.
|
||||
Similarly you could create other parameters in the [`mc_nn_control_params.c`](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mc_nn_control/mc_nn_control_params.c) file for other startup script checks.
|
||||
Similarly you could create other parameters in the [`mc_nn_control_params.yaml`](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mc_nn_control/mc_nn_control_params.yaml) file for other startup script checks.
|
||||
|
||||
## Custom Flight Mode
|
||||
|
||||
|
||||
+280
-75
File diff suppressed because it is too large
Load Diff
@@ -13,17 +13,15 @@ const { site } = useData();
|
||||
</div>
|
||||
</div>
|
||||
|
||||
This contains changes to PX4 `main` branch after the next major release ([PX v1.18](../releases/1.16.md)).
|
||||
This contains changes to the PX4 `main` branch that are not included in the next release ([PX4 v1.18](../releases/1.18.md)).
|
||||
|
||||
:::warning
|
||||
PX4 v1.18 is in alpha/beta testing.
|
||||
Update these notes with features that are going to be in `main` (PX4 v1.18 or later) but not the PX4 v1.18 release.
|
||||
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.
|
||||
:::
|
||||
|
||||
## Прочитайте перед оновленням
|
||||
|
||||
- Уточнюється
|
||||
|
||||
Please continue reading for [upgrade instructions](#upgrade-guide).
|
||||
|
||||
## Основні зміни
|
||||
|
||||
@@ -12,9 +12,9 @@ This is done through the MAVLink protocol, specifically the [SET_POSITION_TARGET
|
||||
|
||||
Є дві речі, які ви маєте налаштувати на стороні прошивки перед початком розробки.
|
||||
|
||||
### Enable RC Override
|
||||
### Enable Stick Override
|
||||
|
||||
In _QGroundControl_ you can set the [COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) parameter to automatically switch from offboard mode (or any mode) to Position mode if the RC sticks are moved.
|
||||
In _QGroundControl_ the [MAN_OVERRIDE_SPD](../advanced_config/parameter_reference.md#MAN_OVERRIDE_SPD) parameter controls automatically switching from offboard (or autonomous) mode to Position mode when the remote sticks are moved. This is enabled by default; set it to -1 to disable.
|
||||
This is the best way to ensure that an operator can easily take control of the vehicle and switch to the safest flight mode.
|
||||
|
||||
### Зв'язування RC перемикача з активацією режиму offboard.
|
||||
@@ -23,7 +23,7 @@ In _QGroundControl_ you can set the [RC_MAP_OFFB_SW](../advanced_config/paramete
|
||||
This can be used to switch between offboard mode and the mode set by the mode switch ([RC_MAP_MODE_SW](../advanced_config/parameter_reference.md#RC_MAP_MODE_SW)).
|
||||
You can also switch into offboard mode using a GCS/MAVLink so this is not "mandatory".
|
||||
|
||||
Note also that this mechanism is not as "safe" as using [RC Override](#enable-rc-override) to switch out of offboard mode, because the mode you switch to is unpredictable.
|
||||
Note also that this mechanism is not as "safe" as using [stick Override](#enable-stick-override) to switch out of offboard mode, because the mode you switch to is unpredictable.
|
||||
|
||||
### Увімкніть інтерфейс комп'ютера-компаньйона
|
||||
|
||||
|
||||
+1
-1
@@ -7,7 +7,7 @@ ROS 1 is now "discommended" as the last LTS version is approaching end of life.
|
||||
ROS 2 has much deeper integration with PX4, enabling lower-latency communication with access to PX4 internal messaging.
|
||||
:::
|
||||
|
||||
[ROS (1)](http://www.ros.org/) is a general purpose robotics library that can be used with PX4 for drone application development.
|
||||
[ROS (1)](https://www.ros.org/) is a general purpose robotics library that can be used with PX4 for drone application development.
|
||||
|
||||
This version of ROS uses the [MAVROS](../ros/mavros_installation.md) package to communicate with PX4 over [MAVLink](../middleware/mavlink.md) (MAVROS bridges ROS topics to MAVLink and PX4 conventions).
|
||||
|
||||
|
||||
@@ -14,8 +14,8 @@ Airspeed sensors are _highly recommended_ for fixed-wing and VTOL frames.
|
||||
- I2C MEAS Spec series (e.g. [MS4525DO](https://www.te.com/en/product-20003581-00.html), [MS5525](https://www.te.com/usa-en/product-CAT-BLPS0003.html))
|
||||
- [mRo I2C Airspeed Sensor JST-GH MS4525DO](https://store.3dr.com/airspeed-sensor-jst-gh-ms4525do/) (3DR store)
|
||||
- [Digital Differential Airspeed Sensor Kit - MS4525DO](https://store-drotek.com/793-digital-differential-airspeed-sensor-kit-.html) (Drotek).
|
||||
- [Holybro Digital Air Speed Sensor - MS4525DO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms4525do)
|
||||
- [Holybro Digital Air Speed Sensor - MS5525DSO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-ms5525dso)
|
||||
- [Holybro Digital Air Speed Sensor - MS4525DO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-standard)
|
||||
- [Holybro Digital Air Speed Sensor - MS5525DSO](https://holybro.com/collections/sensors/products/digital-air-speed-sensor-standard)
|
||||
- I2C Sensirion series (e.g. SDP33)
|
||||
- [ThunderFly TFPITOT01 Lightweight Pitot Tube](https://docs.thunderfly.cz/avionics/TFPITOT01/)
|
||||
- [Drotek SDP3x Airspeed Sensor Kit](https://store-drotek.com/848-sdp3x-airspeed-sensor-kit-sdp33.html)
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
|
||||
[TFSLOT](https://github.com/ThunderFly-aerospace/TFSLOT01) is an airspeed sensor based on venturi effects.
|
||||
In the basic configuration, the TFSLOT is equipped with the [TFASPDIMU02](https://github.com/ThunderFly-aerospace/TFASPDIMU02) sensor board, which contains a differential pressure sensor ([Sensirion SDP3x series](https://sensirion.com/products/catalog?filter_series=d1816d53-f5c8-47e3-ab47-818c3fd54259)) and a 9-axis motion tracking sensor ([ICM-20948](https://invensense.tdk.com/products/motion-tracking/9-axis/icm-20948/)).
|
||||
In the basic configuration, the TFSLOT is equipped with the [TFASPDIMU02](https://github.com/ThunderFly-aerospace/TFASPDIMU02) sensor board, which contains a differential pressure sensor ([Sensirion SDP3x series](https://sensirion.com/products/catalog?filter_series=d1816d53-f5c8-47e3-ab47-818c3fd54259)) and a 9-axis motion tracking sensor ([ICM-20948](https://www.invensense.tdk.com/en-us/products/9-axis/icm-20948)).
|
||||
Одиницю IMU можна використовувати як зовнішній компас.
|
||||
|
||||
- Цей дизайн має кілька переваг при використанні на невеликих і повільних безпілотних літальних апаратах.
|
||||
@@ -42,7 +42,7 @@ TFSLOT is possible to buy at [Tindie store](https://www.tindie.com/products/thun
|
||||
|
||||
## Налаштування
|
||||
|
||||
Because there is an [IMU IC](https://invensense.tdk.com/products/motion-tracking/9-axis/icm-20948/) connected in front of the sensor, the IMU IC needs to be set into a bridge mode.
|
||||
Because there is an [IMU IC](https://www.invensense.tdk.com/en-us/products/9-axis/icm-20948) connected in front of the sensor, the IMU IC needs to be set into a bridge mode.
|
||||
Після цього можна запустити драйвер датчика швидкості повітря. Це може бути зроблено за допомогою наступних послідовностей команд. Команди передбачають підключення до порту I2C2.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -36,4 +36,4 @@ CONFIG_DRIVERS_DISTANCE_SENSOR_LEDDAR_ONE=y
|
||||
|
||||
## Подальша інформація
|
||||
|
||||
- [LeddarOne Spec sheet](https://leddartech.com/app/uploads/dlm_uploads/2021/04/Spec-Sheet_LeddarOne_V10.0_EN-1.pdf)
|
||||
- [LeddarOne Spec sheet](https://leddartech.com/download/specsheet-leddarone-single-element-sensor-module/pdf_file.pdf)
|
||||
|
||||
@@ -18,7 +18,7 @@ This is used by default.
|
||||
|
||||
## Aruco
|
||||
|
||||
Aruco world is the default world with the addition of an [ArUco marker](https://docs.opencv.org/4.x/d5/dae/tutorial_aruco_detection.html).
|
||||
Aruco world is the default world with the addition of an [ArUco marker](https://docs.opencv.org/4.13.0/d5/dae/tutorial_aruco_detection.html).
|
||||
|
||||
This is used in conjunction with the [x500_mono_cam_down](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-monocular-camera-down-facing) airframe to test [precision landing](../advanced_features/precland.md).
|
||||
|
||||
@@ -126,4 +126,4 @@ The PX4 toolchain will automatically spawn a world that has the same name as the
|
||||
|
||||
Світи певних моделей:
|
||||
|
||||
- [Aruco world](#aruco): Default world with an [ArUco marker](https://docs.opencv.org/4.x/d5/dae/tutorial_aruco_detection.html) that can be used with [x500_mono_cam_down](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-monocular-camera-down-facing) for testing [precision landing](../advanced_features/precland.md).
|
||||
- [Aruco world](#aruco): Default world with an [ArUco marker](https://docs.opencv.org/4.13.0/d5/dae/tutorial_aruco_detection.html) that can be used with [x500_mono_cam_down](../sim_gazebo_gz/vehicles.md#x500-quadrotor-with-monocular-camera-down-facing) for testing [precision landing](../advanced_features/precland.md).
|
||||
|
||||
@@ -89,7 +89,7 @@ To add another X-Plane aircraft:
|
||||
4. Tune the PX4 parameters from ULog data and X-Plane truth logs.
|
||||
|
||||
See the [px4xplane custom airframe guide](https://github.com/alireza787b/px4xplane/blob/master/docs/custom-airframe-config.md) for bridge configuration details.
|
||||
For X-Plane-side aircraft design and dataref mapping, see the official [Plane Maker manual](https://developer.x-plane.com/manuals/planemaker/index.html) and [X-Plane datarefs reference](https://developer.x-plane.com/datarefs/).
|
||||
For X-Plane-side aircraft design and dataref mapping, see the official [Plane Maker manual](https://developer.x-plane.com/manuals/planemaker/) and [X-Plane datarefs reference](https://developer.x-plane.com/datarefs/).
|
||||
|
||||
## Усунення проблем
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# PX4 Simulation QuickStart
|
||||
|
||||
First install [Docker](https://docs.docker.com/get-docker/) (a free tool that runs containers).
|
||||
First install [Docker](https://docs.docker.com/get-started/get-docker/) (a free tool that runs containers).
|
||||
|
||||
The following command will then run a PX4 quadrotor simulation that you can connect to [QGroundControl](https://qgroundcontrol.com), [MAVSDK](https://mavsdk.mavlink.io/) or [ROS 2](../ros2/user_guide.md) (on Linux, macOS, and Windows):
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ sudo apt remove px4-gazebo # Gazebo package
|
||||
|
||||
Container images are built using the same `.deb` packages described above, packaged into minimal Docker images.
|
||||
They are published to [Docker Hub](https://hub.docker.com/u/px4io) on every tagged release.
|
||||
You will need to [install Docker](https://docs.docker.com/get-docker/).
|
||||
You will need to [install Docker](https://docs.docker.com/get-started/get-docker/).
|
||||
|
||||
| Зображення | Симулятор |
|
||||
| ----------------------------- | --------------------------------- |
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
|
||||
## Де купити
|
||||
|
||||
[Rotoye Store](https://shop.rotoye.com/batmon/): Batmon kits, custom smart-batteries, and accessories
|
||||
[Rotoye Store](https://shop.rotoye.com/product/BATMON-v5-devkit-p480893112): Batmon kits, custom smart-batteries, and accessories
|
||||
|
||||
## Проведення/Підключення
|
||||
|
||||
@@ -24,15 +24,19 @@ More details can be found [here](https://github.com/rotoye/batmon_reader)
|
||||
### Створення прошивки PX4
|
||||
|
||||
1. Clone or download [Rotoye's fork of PX4:](https://github.com/rotoye/PX4-Autopilot/tree/batmon_4.03)
|
||||
|
||||
```sh
|
||||
git clone https://github.com/rotoye/PX4-Autopilot.git
|
||||
cd PX4-Autopilot
|
||||
```
|
||||
|
||||
2. Checkout the _batmon_4.03_ branch
|
||||
|
||||
```sh
|
||||
git fetch origin batmon_4.03
|
||||
git checkout batmon_4.03
|
||||
```
|
||||
|
||||
3. [Build and upload the firmware](../dev_setup/building_px4.md) for your target board
|
||||
|
||||
### Налаштування параметрів
|
||||
@@ -46,6 +50,7 @@ In _QGroundControl_:
|
||||
2. Open the [MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html)
|
||||
3. Start the [batt_smbus driver](../modules/modules_driver.md) in the console.
|
||||
Наприклад, для запуску двох BatMons у одному підключенні:
|
||||
|
||||
```sh
|
||||
batt_smbus start -X -b 1 -a 11 # External bus 1, address 0x0b
|
||||
batt_smbus start -X -b 1 -a 12 # External bus 1, address 0x0c
|
||||
|
||||
@@ -1,23 +1,17 @@
|
||||
# Дальній телеметр RFD900
|
||||
|
||||
[jDrones](http://store.jDrones.com) and [RFDesign](https://rfdesign.com.au/) offer _long-range_ [SiK](../telemetry/sik_radio.md)-compatible telemetry radios.
|
||||
[RFDesign](https://rfdesign.com.au/) offers _long-range_ [SiK](../telemetry/sik_radio.md)-compatible telemetry radios.
|
||||
Радіостанції забезпечують надійне підключення на відстанях більше 5 км звичайними антенами (і було повідомлено про досягнення набагато більших відстаней).
|
||||
|
||||
|
||||
|
||||
|
||||
:::tip
|
||||
_jDrones_ have productized _RFDesign_ modems (added a casing with power management, filtering and other electronics inside, along with cables to connect to popular flight controllers, and individually validated antennas).
|
||||
The first such modem was the _RFD900_, but both _RFDesign_ and _jDrones_ have since iterated to new versions.
|
||||
:::
|
||||
The raw modems expose bare pin headers, multiple vendors—along with _RFDesign_ themselves—offer productized versions.
|
||||
Depending on your region and target deployment, several turn-key solutions and regional bundles are available:
|
||||
|
||||
The _jDrones_ radios have a JST-GH connector, and come with cables for: _JST-GH to JST-GH_ and _JST-GH to DF-13_.
|
||||
They can therefore be used in a "plug-n-play" way with most [Pixhawk Series](../flight_controller/pixhawk_series.md) controllers (you might have to change/use an appropriate connector for some "non-standard" boards).
|
||||
- **Official RFDesign Store:**
|
||||
- [RFD900x Modem (915MHz - Americas/APAC)](https://store.rfdesign.com.au/rfd-900x-modem/)
|
||||
- [RFD868x Modem (868MHz - Europe)](https://store.rfdesign.com.au/rfd868x-eu-hs-8517-62-00-90/)
|
||||
|
||||
Є кілька доступних версій:
|
||||
|
||||
- [jD-RF900Plus Longrange (900Mhz)](http://store.jdrones.com/jD_RD900Plus_Telemetry_Bundle_p/rf900set02.htm) (USA)
|
||||
- [jD-RF868Plus Longrange (868Mhz)](http://store.jdrones.com/jD_RD868Plus_Telemetry_Bundle_p/rf868set02.htm) (Europe)
|
||||
- [store.rfdesign.com.au](https://store.rfdesign.com.au/radio-modems/):
|
||||
- [RFD 900+ Modem](https://store.rfdesign.com.au/rfd-900p-modem/)
|
||||
- [RFD 868x Modem (EU)](https://store.rfdesign.com.au/rfd868x-eu-hs-8517-62-00-90/)
|
||||
- [RFD900x](https://store.rfdesign.com.au/rfd-900x-modem/)
|
||||
- **Productized Enclosures & Bundles:**
|
||||
- [Bask Aerospace AeroLink System](https://baskaerospace.com.au/products/aerolink/) (Rugged, weather-resistant base station and drone adapters)
|
||||
- [IR-Lock RFD900x TXMOD V2 Bundle](https://irlock.com/products/rfd900-txmod-bundle) (Complete ground-to-air transmitter kit)
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user