mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-05-21 21:55:34 +08:00
New Crowdin translations - ko
This commit is contained in:
Crowdin Bot
committed by
Hamish Willee
Hamish Willee
parent
389b76bd3a
commit
29a40f37e2
+24
-12
@@ -1,9 +1,7 @@
|
||||
- [Introduction](index.md)
|
||||
|
||||
- [기본 개념](getting_started/px4_basic_concepts.md)
|
||||
|
||||
- [멀티콥터](frames_multicopter/index.md)
|
||||
|
||||
- [Features](features_mc/index.md)
|
||||
- [비행 모드 ](flight_modes_mc/index.md)
|
||||
- [위치 모드 (멀티콥터)](flight_modes_mc/position.md)
|
||||
@@ -57,7 +55,6 @@
|
||||
- [DJI F450 (CUAV v5 nano)](frames_multicopter/dji_f450_cuav_5nano.md)
|
||||
|
||||
- [Planes (Fixed-Wing)](frames_plane/index.md)
|
||||
|
||||
- [Assembly](assembly/assembly_fw.md)
|
||||
- [Config/Tuning](config_fw/index.md)
|
||||
- [Auto-tune](config/autotune_fw.md)
|
||||
@@ -85,7 +82,6 @@
|
||||
- [Wing Wing Z84 (Pixracer)](frames_plane/wing_wing_z84.md)
|
||||
|
||||
- [수직이착륙기(VTOL)](frames_vtol/index.md)
|
||||
|
||||
- [Assembly](assembly/assembly_vtol.md)
|
||||
- [VTOL 설정 및 튜닝](config_vtol/index.md)
|
||||
- [Auto-tune](config/autotune_vtol.md)
|
||||
@@ -110,7 +106,6 @@
|
||||
- [Complete Vehicles](complete_vehicles_vtol/index.md)
|
||||
|
||||
- [Operations](config/operations.md)
|
||||
|
||||
- [안전 설정](config/safety_intro.md)
|
||||
- [Safety Configuration (Failsafes)](config/safety.md)
|
||||
- [Failsafe Simulation](config/safety_simulation.md)
|
||||
@@ -131,7 +126,6 @@
|
||||
- [QGroundControl Flight-Readiness Status](flying/pre_flight_checks.md)
|
||||
|
||||
- [Hardware Selection & Setup](hardware/drone_parts.md)
|
||||
|
||||
- [비행 컨트롤러 (오토파일럿)](flight_controller/index.md)
|
||||
- [Flight Controller Selection](getting_started/flight_controller_selection.md)
|
||||
- [Pixhawk Series](flight_controller/pixhawk_series.md)
|
||||
@@ -168,13 +162,11 @@
|
||||
- [ARK Electronics ARKV6X](flight_controller/ark_v6x.md)
|
||||
- [ARK FPV Flight Controller](flight_controller/ark_fpv.md)
|
||||
- [ARK Pi6X Flow Flight Controller](flight_controller/ark_pi6x.md)
|
||||
- [CUAV X7](flight_controller/cuav_x7.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 Pixhack v3 (FMUv3)](flight_controller/pixhack_v3.md)
|
||||
- [CubePilot Cube Orange+ (CubePilot)](flight_controller/cubepilot_cube_orangeplus.md)
|
||||
- [CubePilot Cube Orange (CubePilot)](flight_controller/cubepilot_cube_orange.md)
|
||||
- [CubePilot Cube Yellow (CubePilot)](flight_controller/cubepilot_cube_yellow.md)
|
||||
@@ -190,8 +182,7 @@
|
||||
- [ModalAI Flight Core v1](flight_controller/modalai_fc_v1.md)
|
||||
- [ModalAI VOXL Flight](flight_controller/modalai_voxl_flight.md)
|
||||
- [ModalAI VOXL 2](flight_controller/modalai_voxl_2.md)
|
||||
- [mRobotics-X2.1 (FMUv2)](flight_controller/mro_x2.1.md)
|
||||
- [mRo Control Zero F7)](flight_controller/mro_control_zero_f7.md)
|
||||
- [mRo Control Zero F7](flight_controller/mro_control_zero_f7.md)
|
||||
- [Sky-Drones AIRLink](flight_controller/airlink.md)
|
||||
- [SPRacing SPRacingH7EXTREME](flight_controller/spracingh7extreme.md)
|
||||
- [ThePeach FCC-K1](flight_controller/thepeach_k1.md)
|
||||
@@ -208,10 +199,13 @@
|
||||
- [BetaFPV Beta75X 2S Brushless Whoop](complete_vehicles_mc/betafpv_beta75x.md)
|
||||
- [Bitcraze Crazyflie 2.0 ](complete_vehicles_mc/crazyflie2.md)
|
||||
- [Aerotenna OcPoC-Zynq Mini](flight_controller/ocpoc_zynq.md)
|
||||
- [CUAV X7](flight_controller/cuav_x7.md)
|
||||
- [CUAV v5](flight_controller/cuav_v5.md)
|
||||
- [CUAV Pixhack v3 (FMUv3)](flight_controller/pixhack_v3.md)
|
||||
- [Holybro Kakute F7](flight_controller/kakutef7.md)
|
||||
- [Holybro Pixfalcon](flight_controller/pixfalcon.md)
|
||||
- [Holybro pix32 (FMUv2)](flight_controller/holybro_pix32.md)
|
||||
- [mRo X2.1 (FMUv2)](flight_controller/mro_x2.1.md)
|
||||
- [mRo AUAV-X2](flight_controller/auav_x2.md)
|
||||
- [NXP RDDRONE-FMUK66 FMU](flight_controller/nxp_rddrone_fmuk66.md)
|
||||
- [3DR Pixhawk 1](flight_controller/pixhawk.md)
|
||||
@@ -228,7 +222,9 @@
|
||||
- [Bootloader Update](advanced_config/bootloader_update.md)
|
||||
- [Bootloader Update FMUv6X-RT via USB](advanced_config/bootloader_update_v6xrt.md)
|
||||
- [Bootloader Flashing onto Betaflight Systems](advanced_config/bootloader_update_from_betaflight.md)
|
||||
|
||||
- [Airframe Selection](config/airframe.md)
|
||||
|
||||
- [센서](sensor/index.md)
|
||||
- [가속도계](sensor/accelerometer.md)
|
||||
- [Calibration](config/accelerometer.md)
|
||||
@@ -271,6 +267,7 @@
|
||||
- [CUAV C-RTK](gps_compass/rtk_gps_cuav_c-rtk.md)
|
||||
- [CUAV C-RTK2 PPK/RTK GNSS](gps_compass/rtk_gps_cuav_c-rtk2.md)
|
||||
- [CUAV C-RTK 9Ps](gps_compass/rtk_gps_cuav_c-rtk-9ps.md)
|
||||
- [DATAGNSS NANO HRTK GNSS](gps_compass/rtk_gps_datagnss_nano_hrtk.md)
|
||||
- [DATAGNSS GEM1305 RTK GNSS](gps_compass/rtk_gps_gem1305.md)
|
||||
- [Femtones MINI2 Receiver](gps_compass/rtk_gps_fem_mini2.md)
|
||||
- [Freefly RTK GPS](gps_compass/rtk_gps_freefly.md)
|
||||
@@ -296,6 +293,7 @@
|
||||
- [ThunderFly TFRPM01 타코미터 센서](sensor/thunderfly_tachometer.md)
|
||||
- [IMU Factory Calibration](advanced_config/imu_factory_calibration.md)
|
||||
- [센서 온도 보정](advanced_config/sensor_thermal_calibration.md)
|
||||
|
||||
- [액츄에이터](actuators/index.md)
|
||||
- [ADSB/FLARM (트래픽 회피)](config/actuators.md)
|
||||
- [ESC 보정](advanced_config/esc_calibration.md)
|
||||
@@ -310,10 +308,13 @@
|
||||
- [Zubax Orel](dronecan/zubax_orel.md)
|
||||
- [Vertiq](peripherals/vertiq.md)
|
||||
- [VESC](peripherals/vesc.md)
|
||||
|
||||
- [Radio Control (RC)](getting_started/rc_transmitter_receiver.md)
|
||||
- [무선 조종기 설정](config/radio.md)
|
||||
- [비행 모드](config/flight_mode.md)
|
||||
|
||||
- [Joysticks](config/joystick.md)
|
||||
|
||||
- [Data Links](data_links/index.md)
|
||||
- [MAVLink 텔레메트리(OSD/GCS) ](peripherals/mavlink_peripherals.md)
|
||||
|
||||
@@ -338,6 +339,7 @@
|
||||
- [TBS Crossfire (CRSF) Telemetry](telemetry/crsf_telemetry.md)
|
||||
|
||||
- [Satellite Comms (Iridium/RockBlock)](advanced_features/satcom_roadblock.md)
|
||||
|
||||
- [Power Systems](power_systems/index.md)
|
||||
- [Battery Estimation Tuning](config/battery.md)
|
||||
- [Battery Chemistry Overview](power_systems/battery_chemistry.md)
|
||||
@@ -356,6 +358,7 @@
|
||||
- [Sky-Drones SmartAP PDB](power_module/sky-drones_smartap-pdb.md)
|
||||
- [Smart/MAVLink Batteries](smart_batteries/index.md)
|
||||
- [Rotoye Batmon 배터리 스마트 키트](smart_batteries/rotoye_batmon.md)
|
||||
|
||||
- [탑재중량과 카메라](payloads/index.md)
|
||||
- [Use Cases](payloads/use_cases.md)
|
||||
- [Package Delivery Mission](flying/package_delivery_mission.md)
|
||||
@@ -367,19 +370,25 @@
|
||||
- [Gimbal \(Mount\) Configuration](advanced/gimbal_control.md)
|
||||
- [Grippers](peripherals/gripper.md)
|
||||
- [Servo Gripper](peripherals/gripper_servo.md)
|
||||
|
||||
- [Peripherals](peripherals/index.md)
|
||||
- [ADSB/FLARM/UTM (Traffic Avoidance)](peripherals/adsb_flarm.md)
|
||||
- [낙하산](peripherals/parachute.md)
|
||||
- [Remote ID](peripherals/remote_id.md)
|
||||
|
||||
- [I2C Peripherals](sensor_bus/i2c_general.md)
|
||||
- [I2C bus accelerators](sensor_bus/i2c_general.md#i2c-bus-accelerators)
|
||||
- [TFI2CADT01 I2C address translator](sensor_bus/translator_tfi2cadt.md)
|
||||
|
||||
- [CAN Peripherals](can/index.md)
|
||||
|
||||
- [DroneCAN Peripherals](dronecan/index.md)
|
||||
- [PX4 DroneCAN Firmware](dronecan/px4_cannode_fw.md)
|
||||
- [ARK CANnode](dronecan/ark_cannode.md)
|
||||
- [RaccoonLab CAN Nodes](dronecan/raccoonlab_nodes.md)
|
||||
|
||||
- [배선 개요](assembly/cable_wiring.md)
|
||||
|
||||
- [보조 컴퓨터](companion_computer/index.md)
|
||||
- [Pixhawk + Companion Setup](companion_computer/pixhawk_companion.md)
|
||||
- [RPi Pixhawk Companion](companion_computer/pixhawk_rpi.md)
|
||||
@@ -395,16 +404,19 @@
|
||||
- [리얼센스 T265 트래킹 카메라 (VIO)](camera/camera_intel_realsense_t265_vio.md)
|
||||
- [동영상 스트리밍](companion_computer/video_streaming.md)
|
||||
- [Video Streaming using WFB-ng Wifi (Long range)](companion_computer/video_streaming_wfb_ng_wifi.md)
|
||||
|
||||
- [직렬 포트 설정 ](peripherals/serial_configuration.md)
|
||||
|
||||
- [PX4 이더넷 설정](advanced_config/ethernet_setup.md)
|
||||
|
||||
- [Standard Configuration](config/index.md)
|
||||
|
||||
- [고급 설정](advanced_config/index.md)
|
||||
- [Using PX4's Navigation Filter (EKF2)](advanced_config/tuning_the_ecl_ekf.md)
|
||||
- [매개변수 검색 및 수정](advanced_config/parameters.md)
|
||||
- [전체 매개변수 정의서](advanced_config/parameter_reference.md)
|
||||
|
||||
- [Other Vehicles](airframes/index.md)
|
||||
|
||||
- [Airships (experimental)](frames_airship/index.md)
|
||||
- [Autogyros (experimental)](frames_autogyro/index.md)
|
||||
- [선더플라이 Auto-G2 (Holybro pix32)](frames_autogyro/thunderfly_auto_g2.md)
|
||||
@@ -765,7 +777,7 @@
|
||||
- [Debugging with GDB](debug/gdb_debugging.md)
|
||||
- [SWD Debug Port](debug/swd_debug.md)
|
||||
- [JLink Probe](debug/probe_jlink.md)
|
||||
- [Black Magic/DroneCode Probe](debug/probe_bmp.md)
|
||||
- [Black Magic/Zubax BugFace BF1 Probe](debug/probe_bmp.md)
|
||||
- [STLink Probe](debug/probe_stlink.md)
|
||||
- [MCU-Link Probe](debug/probe_mculink.md)
|
||||
- [Hardfault Debugging](debug/gdb_hardfault.md)
|
||||
|
||||
@@ -41,7 +41,7 @@ The specifications of the host computer where the Virtual Box is running, the Vi
|
||||
|
||||
## ROS 인디고 설치
|
||||
|
||||
- Follow instructions given at [ROS indigo installation guide](http://wiki.ros.org/indigo/Installation/Ubuntu):
|
||||
- Follow instructions given at [ROS indigo installation guide](https://wiki.ros.org/indigo/Installation/Ubuntu):
|
||||
- 데스크톱 전체 버전을 설치하십시오.
|
||||
- "Initialize rosdep"과 "Environment setup" 부분에 설명한 단계를 실행하십시오.
|
||||
|
||||
@@ -54,7 +54,6 @@ The specifications of the host computer where the Virtual Box is running, the Vi
|
||||
```
|
||||
|
||||
- Download and install the driver:
|
||||
|
||||
- Clone [RealSense_ROS repository](https://github.com/bestmodule/RealSense_ROS):
|
||||
|
||||
```sh
|
||||
@@ -62,7 +61,6 @@ The specifications of the host computer where the Virtual Box is running, the Vi
|
||||
```
|
||||
|
||||
- Follow instructions given in [here](https://github.com/bestmodule/RealSense_ROS/tree/master/r200_install).
|
||||
|
||||
- 패키지 설치할 지 여부를 물어보면 엔터키를 입력하십시오.
|
||||
|
||||
```sh
|
||||
@@ -86,11 +84,9 @@ The specifications of the host computer where the Virtual Box is running, the Vi
|
||||
- 설치 과정이 끝나면, 가상 머신을 다시 시작하십시오.
|
||||
|
||||
- 카메라 드라이버 시험:
|
||||
|
||||
- 인텔 리얼센스 카메라 헤드를 USB3 케이블로 USB3 방식을 따르는 컴퓨터의 포트에 연결하십시오.
|
||||
- Click on Devices->USB-> Intel Corp Intel RealSense 3D Camera R200 in the menu bar of the Virtual Box, in order to forward the camera USB connection to the Virtual Machine.
|
||||
- [패키지 해제 폴더]/Bin/DSReadCameraInfo 파일을 실행하십시오:
|
||||
|
||||
- 다음 오류 메시지가 나타나면 카메라 연결을 해제하십시오(컴퓨터에서 물리적으로 USB 케이블을 뽑아내십시오). Plug it in again + Click on Devices->USB-> Intel Corp Intel RealSense 3D Camera R200 in the menu bar of the Virtual Box again and execute again the file [unpacked folder]/Bin/DSReadCameraInfo.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -39,7 +39,7 @@ The u-blox U-Center RTK module configuration tool is not needed/used!
|
||||
:::
|
||||
|
||||
:::info
|
||||
Both _QGroundControl_ and the autopilot firmware share the same [PX4 GPS driver stack](https://github.com/PX4/GpsDrivers).
|
||||
Both _QGroundControl_ and the autopilot firmware share the same [PX4 GPS driver stack](https://github.com/PX4/PX4-GPSDrivers).
|
||||
실제로, 새 프로토콜 또는 메시지 지원시 한쪽에만 추가하면 됩니다.
|
||||
:::
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ On Windows, one option is to use _Melody Master_ within _Dosbox_.
|
||||
|
||||
소프트웨어 사용 절차는 다음과 같습니다.
|
||||
|
||||
1. Download [DosBox](http://www.dosbox.com/) and install the app
|
||||
1. Download [DosBox](https://www.dosbox.com/) and install the app
|
||||
|
||||
2. Download [Melody Master](ftp://archives.thebbs.org/ansi_utilities/melody21.zip) and unzip into a new directory
|
||||
|
||||
|
||||
@@ -78,7 +78,7 @@ arm-none-eabi-objcopy -O ihex build/px4_fmu-v6x_bootloader/px4_fmu-v6x_bootloade
|
||||
|
||||
### PX4 Bootloader FMUv5X and earlier
|
||||
|
||||
PX4 boards up to FMUv5X (before STM32H7) used the [PX4 bootloader](https://github.com/PX4/Bootloader) repository.
|
||||
PX4 boards up to FMUv5X (before STM32H7) used the [PX4 bootloader](https://github.com/PX4/PX4-Bootloader) repository.
|
||||
|
||||
The instructions in the repo README explain how to use it.
|
||||
|
||||
@@ -117,7 +117,7 @@ The following steps explain how you can "manually" update the bootloader using a
|
||||
|
||||
:::
|
||||
|
||||
4. The _gdb terminal_ appears and it should display the following output:
|
||||
4. The _gdb terminal_ appears and it should display (something like) the following output:
|
||||
|
||||
```sh
|
||||
GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
|
||||
@@ -129,9 +129,9 @@ The following steps explain how you can "manually" update the bootloader using a
|
||||
This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
|
||||
Type "show configuration" for configuration details.
|
||||
For bug reporting instructions, please see:
|
||||
<http://www.gnu.org/software/gdb/bugs/>.
|
||||
<https://www.sourceware.org/gdb/bugs/>.
|
||||
Find the GDB manual and other documentation resources online at:
|
||||
<http://www.gnu.org/software/gdb/documentation/>.
|
||||
<https://www.sourceware.org/gdb/documentation/>.
|
||||
For help, type "help".
|
||||
Type "apropos word" to search for commands related to "word"...
|
||||
Reading symbols from px4fmuv5_bl.elf...done.
|
||||
@@ -148,7 +148,7 @@ The following steps explain how you can "manually" update the bootloader using a
|
||||
7. Power on the Pixhawk with another USB cable and connect the probe to the `FMU-DEBUG` port.
|
||||
|
||||
::: info
|
||||
If using a Dronecode probe you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).
|
||||
If using a Zubax BugFace BF1 you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
This page documents how to flash the PX4 bootloader onto boards that are already flashed with Betaflight (e.g. [OmnibusF4 SD](../flight_controller/omnibus_f4_sd.md) or [Kakute F7](../flight_controller/kakutef7.md)).
|
||||
|
||||
There are three tools that can be used to flash the PX4 bootloader: _Betaflight Configurator_, [dfu-util](http://dfu-util.sourceforge.net/) command line tool, or the graphical [dfuse](https://www.st.com/en/development-tools/stsw-stm32080.html) (Windows only).
|
||||
There are three tools that can be used to flash the PX4 bootloader: _Betaflight Configurator_, [dfu-util](https://dfu-util.sourceforge.net/) command line tool, or the graphical [dfuse](https://www.st.com/en/development-tools/stsw-stm32080.html) (Windows only).
|
||||
|
||||
:::info
|
||||
The _Betaflight Configurator_ is easiest, but newer versions may not support non-betaflight bootloader update.
|
||||
@@ -23,7 +23,7 @@ To install the PX4 bootloader using the _Betaflight Configurator_:
|
||||
2. Download the [Betaflight Configurator](https://github.com/betaflight/betaflight-configurator/releases) for your platform.
|
||||
|
||||
:::tip
|
||||
If using the _Chrome_ web browser, a simple cross-platform alternative is to install the configurator as an [extension from here](https://chrome.google.com/webstore/detail/betaflight-configurator/kdaghagfopacdngbohiknlhcocjccjao).
|
||||
If using the _Chrome_ web browser, a simple cross-platform alternative is to install the configurator as an [extension from here](https://chromewebstore.google.com/detail/betaflight-configurator/kdaghagfopacdngbohiknlhcocjccjao?pli=1).
|
||||
|
||||
:::
|
||||
|
||||
@@ -38,7 +38,7 @@ To install the PX4 bootloader using the _Betaflight Configurator_:
|
||||
|
||||
## DFU Bootloader Update
|
||||
|
||||
This section explains how to flash the PX4 bootloader using the [dfu-util](http://dfu-util.sourceforge.net/) or the graphical [dfuse](https://www.st.com/en/development-tools/stsw-stm32080.html) tool (Windows only).
|
||||
This section explains how to flash the PX4 bootloader using the [dfu-util](https://dfu-util.sourceforge.net/) or the graphical [dfuse](https://www.st.com/en/development-tools/stsw-stm32080.html) tool (Windows only).
|
||||
|
||||
You will first need to download or build [bootloader firmware](#bootloader-firmware) for the board you want to flash (below, this is referred to as `<target.bin>`).
|
||||
|
||||
@@ -118,10 +118,10 @@ cd PX4-Autopilot
|
||||
make <target> # For example: holybro_kakuteh7mini_bootloader
|
||||
```
|
||||
|
||||
For other flight controllers download the [PX4/Bootloader](https://github.com/PX4/Bootloader) repository and build the source code using the appropriate targets:
|
||||
For other flight controllers download the [PX4/Bootloader](https://github.com/PX4/PX4-Bootloader) repository and build the source code using the appropriate targets:
|
||||
|
||||
```
|
||||
git clone --recursive https://github.com/PX4/Bootloader.git
|
||||
git clone --recursive https://github.com/PX4/PX4-Bootloader.git
|
||||
cd Bootloader
|
||||
make <target> # For example: omnibusf4sd_bl or kakutef7_bl
|
||||
```
|
||||
|
||||
@@ -108,7 +108,7 @@ You also need to [configure the Ethernet port](#px4-mavlink-serial-port-configur
|
||||
If you're using Ubuntu for your ground station (or companion computer) then you can use [netplan](https://netplan.io/) to configure the network.
|
||||
|
||||
Below we show how you write a setup to the netplan configuration file "`/etc/netplan/01-network-manager-all.yaml`", which would run on the same network as used by the PX4 setup above.
|
||||
Note that there are many more [examples](https://netplan.io/examples/) and instructions in the [netplan](https://netplan.io/) documentation.
|
||||
Note that there are many more [examples](https://github.com/canonical/netplan/tree/main/examples) and instructions in the [netplan](https://netplan.io/) documentation.
|
||||
|
||||
To setup the Ubuntu Computer:
|
||||
|
||||
|
||||
@@ -109,7 +109,7 @@ Arming is prevented if:
|
||||
- The current mode requires an adequate global position estimate but the vehicle does not have GPS lock.
|
||||
- Many more (see [arming/disarming safety settings](../config/safety.md#arming-disarming-settings) for more information).
|
||||
|
||||
The current failed checks can be viewed in QGroundControl (v4.2.0 and later) [Arming Check Report](../flying/pre_flight_checks.md#qgc-arming-check-report) (see also [Fly View > Arming and Preflight Checks](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/fly_view/fly_view.md#arm)).
|
||||
The current failed checks can be viewed in QGroundControl (v4.2.0 and later) [Arming Check Report](../flying/pre_flight_checks.md#qgc-arming-check-report) (see also [Fly View > Toolbar > Flight Status](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/fly_view/fly_view_toolbar.html#flight-status)).
|
||||
|
||||
Note that internally PX4 runs arming checks at 10Hz.
|
||||
A list of the failed checks is kept, and if the list changes PX4 emits the current list using the [Events interface](../concept/events_interface.md).
|
||||
@@ -159,7 +159,6 @@ It corresponds to: [COM_PREARM_MODE=1](#COM_PREARM_MODE) (safety switch) and [CB
|
||||
- 시스템이 시동전 상태로 전환: 추진 모터를 제외한 모든 액츄에이터 동작 가능(예: 보조익)
|
||||
- 시스템 안전 장치 꺼짐: 시동 가능
|
||||
3. 시동 명령 인가
|
||||
|
||||
- 시스템에 시동이 걸림
|
||||
- 모든 모터와 액츄에이터를 움직일 수 있음
|
||||
|
||||
@@ -177,7 +176,6 @@ This corresponds to [COM_PREARM_MODE=0](#COM_PREARM_MODE) (Disabled) and [CBRK_I
|
||||
- _All actuators stay locked into disarmed position (same as disarmed)._
|
||||
- 시스템 안전 장치 꺼짐: 시동 가능
|
||||
3. 시동 명령 인가
|
||||
|
||||
- 시스템에 시동이 걸림
|
||||
- 모든 모터와 액츄에이터를 움직일 수 있음
|
||||
|
||||
|
||||
@@ -277,7 +277,7 @@ For more details about the configuration of height sources, [click here](#height
|
||||
|
||||
#### 방향(Yaw) 측정
|
||||
|
||||
Some GPS receivers such as the [Trimble MB-Two RTK GPS receiver](https://www.trimble.com/Precision-GNSS/MB-Two-Board.aspx) can be used to provide a heading measurement that replaces the use of magnetometer data.
|
||||
Some GPS receivers such as the [Trimble MB-Two RTK GPS receiver](https://oemgnss.trimble.com/en/products/receiver-modules/mb-two) can be used to provide a heading measurement that replaces the use of magnetometer data.
|
||||
This can be a significant advantage when operating in an environment where large magnetic anomalies are present, or at latitudes here the earth's magnetic field has a high inclination.
|
||||
Use of GPS yaw measurements is enabled by setting bit position 3 to 1 (adding 8) in the [EKF2_GPS_CTRL](../advanced_config/parameter_reference.md#EKF2_GPS_CTRL) parameter.
|
||||
|
||||
@@ -542,9 +542,9 @@ When this has been done, the performance metadata files can be processed to prov
|
||||
|
||||
### 출력 데이터
|
||||
|
||||
- Attitude output data is found in the [VehicleAttitude](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleAttitude.msg) message.
|
||||
- Local position output data is found in the [VehicleLocalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleLocalPosition.msg) message.
|
||||
- Global \(WGS-84\) output data is found in the [VehicleGlobalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/VehicleGlobalPosition.msg) message.
|
||||
- Attitude output data is found in the [VehicleAttitude](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleAttitude.msg) message.
|
||||
- Local position output data is found in the [VehicleLocalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleLocalPosition.msg) message.
|
||||
- Global \(WGS-84\) output data is found in the [VehicleGlobalPosition](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/VehicleGlobalPosition.msg) message.
|
||||
- Wind velocity output data is found in the [Wind.msg](https://github.com/PX4/PX4-Autopilot/blob/main/msg/Wind.msg) message.
|
||||
|
||||
### 상태
|
||||
|
||||
@@ -103,10 +103,10 @@ At time of writing is no _convenient_ way to directly invoke precision landing (
|
||||
|
||||
### IR 센서/비콘 설정
|
||||
|
||||
The IR sensor/landing beacon solution requires an [IR-LOCK Sensor](https://irlock.com/products/ir-lock-sensor-precision-landing-kit) and downward facing [distance sensor](../sensor/rangefinders.md) connected to the flight controller, and an IR beacon as a target (e.g. [IR-LOCK MarkOne](https://irlock.com/collections/markone)).
|
||||
The IR sensor/landing beacon solution requires an [IR-LOCK Sensor](https://irlock.com/products/ir-lock-sensor-precision-landing-kit) and downward facing [distance sensor](../sensor/rangefinders.md) connected to the flight controller, and an IR beacon as a target (e.g. [IR-LOCK MarkOne](https://irlock.com/collections/ir-markers)).
|
||||
정밀 착륙은 약 10 cm 이내의 오차로 착륙할 수 있게 합니다. GPS 착륙은 수 미터의 오차가 발생할 수 있습니다.
|
||||
|
||||
Install the IR-LOCK sensor by following the [official guide](https://irlock.readme.io/v2.0/docs).
|
||||
Install the IR-LOCK sensor by following the [official guide](https://irlock.readme.io/docs/getting-started).
|
||||
센서의 x축이 기체의 y축과 정렬되어 있는지, 센서의 y축이 기체의 -x 방향과 정렬되어 있는지 확인하십시오 (카메라에서 전방으로 90도 기울인 경우).
|
||||
|
||||
Install a [range/distance sensor](../sensor/rangefinders.md) (the _LidarLite v3_ has been found to work well).
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
|
||||
위성 통신에는 다음의 요소들이 필요합니다.
|
||||
|
||||
- A [RockBlock 9603 Iridium Satellite Modem](https://www.iridium.com/products/rock-seven-rockblock-9603/) module connected to a Pixhawk flashed with the PX4 Autopilot.
|
||||
- A [RockBlock 9603 Iridium Satellite Modem](https://www.iridium.com/products/ground-control-rockblock-9603/) module connected to a Pixhawk flashed with the PX4 Autopilot.
|
||||
- Ubuntu Linux를 실행하는 메시지 릴레이 서버
|
||||
- A ground station computer running _QGroundControl_ on Ubuntu Linux
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
The setup was tested with the current release of _QGroundControl_ running on Ubuntu 14.04 and 16.04.
|
||||
|
||||
- 다른 지상국 및 운영체제를 사용할 수 있지만, 아직 테스트되지 않았습니다.
|
||||
- The [RockBlock MK2](https://www.groundcontrol.com/us/product/rockblock-9602-satellite-modem/) module can also be used.
|
||||
- The [RockBlock MK2](https://www.groundcontrol.com/product/rockblock-9602-satellite-modem/) module can also be used.
|
||||
RockBlock 9603 모듈은 크기가 작고 가볍우면서도 동일한 기능을 제공하기 때문에 권장됩니다.
|
||||
|
||||
:::
|
||||
@@ -34,7 +34,7 @@ The setup was tested with the current release of _QGroundControl_ running on Ubu
|
||||
- Each message transmitted over the system costs one _credit_ per 50 bytes.
|
||||
번들 크기에 따라 RockBlock에서 신용당 0.04파운드 0.11파운드에 신용대출을 구입할 수 있습니다.
|
||||
|
||||
Refer to the [RockBlock Documentation](https://docs.rockblock.rock7.com/docs) for a detailed explanation of the modules, running costs and _RockBlock_ in general.
|
||||
Refer to the [RockBlock Documentation](https://docs.groundcontrol.com/iot/rockblock) for a detailed explanation of the modules, running costs and _RockBlock_ in general.
|
||||
|
||||
## 기체 설정
|
||||
|
||||
@@ -43,15 +43,15 @@ Refer to the [RockBlock Documentation](https://docs.rockblock.rock7.com/docs) fo
|
||||
RockBlock 모듈을 Pixhawk의 직렬 포트에 연결합니다.
|
||||
모듈의 전원 요구 사항으로 인하여 5V에서 최대 0.5A가 필요하므로 고출력 직렬 포트를 통해서만 전원을 공급할 수 있습니다.
|
||||
사용 가능한 별도의 전원을 사용시에는 Pixhawk와 동일한 접지이어야 합니다.
|
||||
The details of the [connectors](https://docs.rockblock.rock7.com/docs/connectors) and the [power requirements](https://docs.rockblock.rock7.com/docs/power-supply) can be found in the RockBlock documentation.
|
||||
The details of the [connectors](https://docs.groundcontrol.com/iot/rockblock/specification/connectors-wiring) and the [power requirements](https://docs.groundcontrol.com/iot/rockblock/electrical) can be found in the RockBlock documentation.
|
||||
|
||||
### 모듈
|
||||
|
||||
모듈은 내부 안테나 또는 SMA 커넥터에 연결된 외부 안테나를 사용할 수 있습니다.
|
||||
To [switch between the two antennas modes](https://docs.rockblock.rock7.com/docs/switching-rockblock-9603-antenna-mode) the position of a small RF link cable needs to changed.
|
||||
To [switch between the two antennas modes](https://docs.groundcontrol.com/iot/rockblock/user-manual/9603-atenna-mode) the position of a small RF link cable needs to changed.
|
||||
외부 안테나를 사용하는 경우 모듈 손상을 방지하기 위해 안테나의 전원을 켜기 전에 항상 안테나가 모듈에 연결되어 있는 지 확인하십시오.
|
||||
|
||||
모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://www.groundcontrol.com/en/wp-content/uploads/2022/02/IRDM_ISU_ATCommandReferenceMAN0009_Rev2.0_ATCOMM_Oct2012.pdf).
|
||||
모듈의 기본 보드 속도는 19200입니다. However, the PX4 _iridiumsbd_ driver requires a baud rate of 115200 so it needs to be changed using the [AT commands](https://www.groundcontrol.com/wp-content/uploads/2022/02/IRDM_ISU_ATCommandReferenceMAN0009_Rev2.0_ATCOMM_Oct2012.pdf).
|
||||
|
||||
1. Connect to the module with using a 19200/8-N-1 setting and check if the communication is working using the command: `AT`.
|
||||
The response should be: `OK`.
|
||||
@@ -101,7 +101,6 @@ Log in to the [account](https://rockblock.rock7.com/Operations) and register the
|
||||
릴레이 서버는 Ubuntu 16.04 또는 14.04 버전에서 실행하여야 합니다.
|
||||
|
||||
1. 메시지 릴레이로 작동하는 서버에는 고정 IP 주소와 열린 TCP 포트 2개가 있어야 합니다.
|
||||
|
||||
- `5672` for the _RabbitMQ_ message broker (can be changed in the _rabbitmq_ settings)
|
||||
- `45679` for the HTTP POST interface (can be changed in the **relay.cfg** file)
|
||||
|
||||
@@ -124,7 +123,7 @@ Log in to the [account](https://rockblock.rock7.com/Operations) and register the
|
||||
sudo rabbitmqctl set_permissions iridiumsbd ".*" ".*" ".*"
|
||||
```
|
||||
|
||||
5. Clone the [SatComInfrastructure](https://github.com/acfloria/SatComInfrastructure.git) repository:
|
||||
5. Clone the [SatComInfrastructure](https://github.com/acfloria/SatComInfrastructure) repository:
|
||||
|
||||
```sh
|
||||
git clone https://github.com/acfloria/SatComInfrastructure.git
|
||||
@@ -240,7 +239,6 @@ If in the terminal where the `udp2rabbit.py` script is running within a couple o
|
||||
링크 표시기는 항상 우선 순위 링크의 이름을 표시합니다.
|
||||
|
||||
5. 이제 위성 통신 시스템을 사용할 준비가 되었습니다.우선 순위 링크(명령 전송 링크)는 다음 방법으로 결정됩니다.
|
||||
|
||||
- 사용자가 링크를 명령하지 않으면, 지연 시간이 큰 링크보다 일반적인 텔레메트리 링크가 선호됩니다.
|
||||
- 기체가 시동을 켜고 텔레메트리 링크가 끊어지면(특정 시간 동안 MAVLink 메시지가 수신되지 않을 경우), 오토파일럿과 QGC는 일반 텔레메트리에서 긴 대기 시간 링크로 되돌아갑니다.
|
||||
텔레메트리 링크가 복구되는 즉시 QGC와 자동 조종기가 다시 이 링크로 전환됩니다.
|
||||
@@ -255,7 +253,6 @@ If in the terminal where the `udp2rabbit.py` script is running within a couple o
|
||||
- 릴레이 서버의 설정을 확인하고 해당 설정이 올바른지 확인합니다(특히 IMEI).
|
||||
|
||||
- 비행기의 위성 통신 메시지는 지상국에 도착하지 않습니다.
|
||||
|
||||
- Check using the system console if the _iridiumsbd_ driver started and if it did that a signal from any satellite is received by the module:
|
||||
|
||||
```sh
|
||||
@@ -267,7 +264,6 @@ If in the terminal where the `udp2rabbit.py` script is running within a couple o
|
||||
- 링크가 연결되어 있고 설정이 정확한 지 확인하십시오.
|
||||
|
||||
- IridiumSBD 드라이버가 시작되지 않음:
|
||||
|
||||
- 기체를 재부팅합니다.
|
||||
If that helps increase the sleep time in the `extras.txt` before the driver is started.
|
||||
그래도 Pixhawk와 모듈이 동일한 접지 레벨을 유지하는지 확인할 수 있습니다. 모듈의 보레이트가 115200으로 설정되어 있는 지 확인하십시오.
|
||||
|
||||
@@ -54,7 +54,7 @@ The GPS/Compass module should be [mounted on the frame](../assembly/mount_gps_co
|
||||
케이블을 사용하여 비행 제어 GPS에 연결합니다.
|
||||
|
||||
:::info
|
||||
If you use the [NEO V2 PRO GNSS (CAN GPS)](http://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html), please use the cable to connect to the flight control CAN interface.
|
||||
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.
|
||||
:::
|
||||
|
||||
|
||||
@@ -134,7 +134,7 @@ Download **V5+** pinouts from [here](http://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](http://manual.cuav.net/V5-Plus.pdf) (CUAV)
|
||||
- [CUAV V5+ docs](http://doc.cuav.net/flight-controller/v5-autopilot/en/v5+.html) (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)
|
||||
|
||||
@@ -13,7 +13,7 @@ This quick start guide shows how to power the _Cube_<sup>®</sup> flight cont
|
||||
|
||||
:::tip
|
||||
The instructions apply to all Cube variants, including [Cube Black](../flight_controller/pixhawk-2.md), [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md) and [Cube Orange](../flight_controller/cubepilot_cube_orange.md).
|
||||
Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual) (Cube Docs).
|
||||
Further/updated information may be available in the [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube) (Cube Docs).
|
||||
:::
|
||||
|
||||
## 소품
|
||||
@@ -195,7 +195,7 @@ If connecting peripherals to the port labeled `GPS2`, assign the PX4 [serial por
|
||||
|
||||
## 설정
|
||||
|
||||
Configuration is performed using [QGroundContro](http://qgroundcontrol.com/).
|
||||
Configuration is performed using [QGroundContro](https://qgroundcontrol.com/).
|
||||
|
||||
After downloading, installing and running _QGroundControl_, connect the board to your computer as shown.
|
||||
|
||||
@@ -220,6 +220,5 @@ PX4 펌웨어를 플래시한 후 [Program PX4IO(../getting_started/tunes.md#pro
|
||||
- [Cube Yellow](../flight_controller/cubepilot_cube_yellow.md)
|
||||
- [Cube Orange](../flight_controller/cubepilot_cube_orange.md)
|
||||
- Cube 문서 (제조사) :
|
||||
- [Cube Module Overview](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview)
|
||||
- [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual)
|
||||
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
|
||||
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
|
||||
|
||||
@@ -148,7 +148,7 @@ The instructions below show how to connect the different types of receivers to _
|
||||
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
@@ -214,6 +214,6 @@ QuadPlane specific configuration is covered here: [QuadPlane VTOL Configuration]
|
||||
|
||||
- [Durandal Overview](../flight_controller/durandal.md)
|
||||
- [Durandal Technical Data Sheet](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Durandal_technical_data_sheet_90f8875d-8035-4632-a936-a0d178062077.pdf) (Holybro)
|
||||
- [Durandal Pinouts](https://holybro.com/collections/autopilot-flight-controllers/products/Durandal-Pinouts) (Holybro)
|
||||
- [Durandal_MB_H743sch.pdf](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/durandal/Durandal_MB_H743sch.pdf) (Durandal Schematics)
|
||||
- [STM32H743IIK_pinout.pdf](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/durandal/STM32H743IIK_pinout.pdf) (Durandal Pinmap)
|
||||
- [Durandal Pinouts](https://cdn.shopifycdn.net/s/files/1/0604/5905/7341/files/Durandal_Pinouts_v1.0.pdf?v=1693983344) (Holybro)
|
||||
- [Durandal_MB_H743sch.pdf](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/durandal/Durandal_MB_H743sch.pdf) (Durandal Schematics)
|
||||
- [STM32H743IIK_pinout.pdf](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/durandal/STM32H743IIK_pinout.pdf) (Durandal Pinmap)
|
||||
|
||||
@@ -124,7 +124,7 @@ The instructions below show how to connect the different types of receivers to _
|
||||
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
@@ -182,5 +182,5 @@ QuadPlane specific configuration is covered here: [QuadPlane VTOL Configuration]
|
||||
- [Pix32 v5 Technical Data Sheet](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5_technical_data_sheet_v1.1.pdf)
|
||||
- [Pix32 v5 Pinouts](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_Pix32-V5-Base-Mini-Pinouts.pdf)
|
||||
- [Pix32 v5 Base Schematic Diagram](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5-BASE-Schematic_diagram.pdf)
|
||||
- [Pix32 v5 Base Components Layout](https://holybro.com/manual/Holybro_PIX32-V5-BASE-ComponentsLayout.pdf)
|
||||
- [Pix32 v5 Base Components Layout](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5-BASE-RC02-ComponentsLayout.pdf)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165).
|
||||
|
||||
@@ -83,7 +83,7 @@ You will need to [select a compatible transmitter/receiver](../getting_started/r
|
||||
- PPM-SUM and S.BUS receivers connect to the **RC** ground, power and signal pins as shown.
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -136,7 +136,7 @@ The instructions below show how to connect the different types of receivers to _
|
||||
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
@@ -179,7 +179,7 @@ The wiring and configuration of optional/less common components is covered withi
|
||||
|
||||
## 핀배열
|
||||
|
||||
[Pixhawk 4 Pinouts](https://holybro.com/manual/Pixhawk4-Pinouts.pdf) (Holybro)
|
||||
[Pixhawk 4 Pinouts](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Pixhawk4-Pinouts.pdf) (Holybro)
|
||||
|
||||
## 설정
|
||||
|
||||
@@ -192,6 +192,6 @@ QuadPlane specific configuration is covered here: [QuadPlane VTOL Configuration]
|
||||
## 추가 정보
|
||||
|
||||
- [Pixhawk 4](../flight_controller/pixhawk4.md) (Overview page)
|
||||
- [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf)
|
||||
- [Pixhawk 4 Pinouts](https://holybro.com/manual/Pixhawk4-Pinouts.pdf) (Holybro)
|
||||
- [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-Autopilot/blob/main/docs/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf)
|
||||
- [Pixhawk 4 Pinouts](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Pixhawk4-Pinouts.pdf) (Holybro)
|
||||
- [Pixhawk 4 Quick Start Guide (Holybro)](https://holybro.com/manual/Pixhawk4-quickstartguide.pdf)
|
||||
|
||||
@@ -108,7 +108,7 @@ The instructions below show how to connect the different types of receivers to _
|
||||
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **PPM RC** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -93,7 +93,7 @@ You will need to [select a compatible transmitter/receiver](../getting_started/r
|
||||
- Spektrum/DSM receivers connect to the **DSM/SBUS RC** input.
|
||||
- PPM or SBUS receivers connect to the **RC IN** input port.
|
||||
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC IN** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC IN** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ You will need to [select a compatible transmitter/receiver](../getting_started/r
|
||||
- Spektrum/DSM receivers connect to the **DSM** input.
|
||||
- PPM or SBUS receivers connect to the **PPM/SBUS** input port.
|
||||
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the \*PPM/SBUS\*\* port \*via a PPM encoder\* [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the \*PPM/SBUS\*\* port \*via a PPM encoder\* [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -106,7 +106,7 @@ You will need to [select a compatible transmitter/receiver](../getting_started/r
|
||||
- Spektrum/DSM receivers connect to the **DSM/SBUS RC** input.
|
||||
- PPM or SBUS receivers connect to the **RC IN** input port.
|
||||
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC IN** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RC IN** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ You will need to [select a compatible transmitter/receiver](../getting_started/r
|
||||
|
||||
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RCIN** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RCIN** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
### 전원 모듈 (ACSP4)
|
||||
|
||||
|
||||
@@ -31,5 +31,5 @@
|
||||
|
||||
유용한 참고사항들입니다.
|
||||
|
||||
- [An Introduction to Shock & Vibration Response Spectra, Tom Irvine](http://www.vibrationdata.com/tutorials2/srs_intr.pdf) (free paper)
|
||||
- [An Introduction to Shock & Vibration Response Spectra, Tom Irvine](https://www.vibrationdata.com/tutorials2/srs_intr.pdf) (free paper)
|
||||
- [Structural Dynamics and Vibration in Practice - An Engineering Handbook, Douglas Thorby](https://books.google.ch/books?id=PwzDuWDc8AgC&printsec=frontcover) (preview).
|
||||
|
||||
@@ -1,16 +1,18 @@
|
||||
# Intel® RealSense™ Tracking Camera T265 (VIO)
|
||||
|
||||
The [Intel® RealSense™ Tracking Camera T265](https://www.intelrealsense.com/tracking-camera-t265/) provides odometry information that can be used for [VIO](../computer_vision/visual_inertial_odometry.md), augmenting or replacing other positioning systems on PX4.
|
||||
|
||||
:::tip
|
||||
This camera is recommended, and is used in the [Visual Inertial Odometry (VIO) > Suggested Setup](../computer_vision/visual_inertial_odometry.md#suggested-setup).
|
||||
This camera is discontinued.
|
||||
:::
|
||||
|
||||
The _Intel® RealSense™ Tracking Camera T265_ provides odometry information that can be used for [VIO](../computer_vision/visual_inertial_odometry.md), augmenting or replacing other positioning systems on PX4.
|
||||
|
||||
It is used in the [Visual Inertial Odometry (VIO) > Suggested Setup](../computer_vision/visual_inertial_odometry.md#suggested-setup).
|
||||
|
||||
|
||||
|
||||
## 구매처
|
||||
|
||||
[Intel® RealSense™ Tracking Camera T265](https://www.intelrealsense.com/tracking-camera-t265/) (store.intelrealsense.com)
|
||||
No longer available.
|
||||
|
||||
## Setup Instructions
|
||||
|
||||
|
||||
@@ -113,12 +113,12 @@ If it is your first time enabling the camera trigger app, remember to reboot aft
|
||||
|
||||
The camera trigger driver supports several backends - each for a specific application, controlled by the [TRIG_INTERFACE](../advanced_config/parameter_reference.md#TRIG_INTERFACE) parameter:
|
||||
|
||||
| Number | 설명 |
|
||||
| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 1 | Enables the GPIO interface. The AUX outputs are pulsed high or low (depending on the `TRIG_POLARITY` parameter) every [TRIG_INTERVAL](../advanced_config/parameter_reference.md#TRIG_INTERVAL) duration. This can be used to trigger most standard machine vision cameras directly. Note that on PX4FMU series hardware (Pixhawk, Pixracer, etc.), the signal level on the AUX pins is 3.3v. |
|
||||
| 2 | Enables the Seagull MAP2 interface. This allows the use of the [Seagull MAP2](http://www.seagulluav.com/product/seagull-map2/) to interface to a multitude of supported cameras. Pin/Channel 1 (camera trigger) and Pin/Channel 2 (mode selector) of the MAP2 should be connected to the lower and higher mapped [camera trigger pins](#trigger-output-pin-configuration). Using Seagull MAP2, PX4 also supports automatic power control and keep-alive functionalities of Sony Multiport cameras like the QX-1. |
|
||||
| 3 | This mode enables MAVLink cameras that used the legacy [MAVLink interface listed above](#mavlink-command-interface). The messages are automatically emitted on the MAVLink `onboard` channel when found in missions. PX4 emits the `CAMERA_TRIGGER` MAVLink message when a camera is triggered, by default to the `onboard` channel (if this is not used, custom stream will need to be enabled). [Simple MAVLink cameras](../camera/mavlink_v1_camera.md) explains this use case in more detail. |
|
||||
| 4 | Enables the generic PWM interface. This allows the use of [infrared triggers](https://hobbyking.com/en_us/universal-remote-control-infrared-shutter-ir-rc-1g.html) or servos to trigger your camera. |
|
||||
| Number | 설명 |
|
||||
| ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 1 | Enables the GPIO interface. The AUX outputs are pulsed high or low (depending on the `TRIG_POLARITY` parameter) every [TRIG_INTERVAL](../advanced_config/parameter_reference.md#TRIG_INTERVAL) duration. This can be used to trigger most standard machine vision cameras directly. Note that on PX4FMU series hardware (Pixhawk, Pixracer, etc.), the signal level on the AUX pins is 3.3v. |
|
||||
| 2 | Enables the Seagull MAP2 interface. This allows the use of the [Seagull MAP2](https://www.seagulluav.com/product/seagull-map2/) to interface to a multitude of supported cameras. Pin/Channel 1 (camera trigger) and Pin/Channel 2 (mode selector) of the MAP2 should be connected to the lower and higher mapped [camera trigger pins](#trigger-output-pin-configuration). Using Seagull MAP2, PX4 also supports automatic power control and keep-alive functionalities of Sony Multiport cameras like the QX-1. |
|
||||
| 3 | This mode enables MAVLink cameras that used the legacy [MAVLink interface listed above](#mavlink-command-interface). The messages are automatically emitted on the MAVLink `onboard` channel when found in missions. PX4 emits the `CAMERA_TRIGGER` MAVLink message when a camera is triggered, by default to the `onboard` channel (if this is not used, custom stream will need to be enabled). [Simple MAVLink cameras](../camera/mavlink_v1_camera.md) explains this use case in more detail. |
|
||||
| 4 | Enables the generic PWM interface. This allows the use of [infrared triggers](https://hobbyking.com/en_us/universal-remote-control-infrared-shutter-ir-rc-1g.html) or servos to trigger your camera. |
|
||||
|
||||
### Trigger Output Pin Configuration
|
||||
|
||||
|
||||
@@ -137,9 +137,9 @@ Generic/extensible camera managers:
|
||||
- [MAVLink Camera Manager](https://github.com/mavlink/mavlink-camera-manager) - Extensible cross-platform MAVLink Camera Server built on top of GStreamer and Rust-MAVLink.
|
||||
- [Dronecode Camera Manager](https://camera-manager.dronecode.org/en/) - Adds Camera Protocol interface for cameras connected to Linux computer.
|
||||
|
||||
Camera-specfic camera managers:
|
||||
Camera-specific camera managers:
|
||||
|
||||
- [SIYI A8 mini camera manager](https://github.com/julianoes/siyi-a8-mini-camera-manager) - MAVSDK-plugin based camera manager for the [SIYI A8 mini](https://shop.siyi.biz/products/siyi-a8-mini) (includes tutorial).
|
||||
- [SIYI A8 mini camera manager](https://github.com/julianoes/siyi-a8-mini-camera-manager) - MAVSDK-plugin based camera manager for the [SIYI A8 mini](https://shop.siyi.biz/products/siyi-a8-mini-gimbal-camera) (includes tutorial).
|
||||
|
||||
::: tip
|
||||
This is a good example of how MAVSDK can be used to create a MAVLink camera protocol interface for a particular camera.
|
||||
@@ -150,6 +150,6 @@ When using a camera manager you connect the companion computer to the flight con
|
||||
|
||||
More information about camera manager and companion computer setups can be found in:
|
||||
|
||||
- [SIYI A8 mini camera manager](https://github.com/julianoes/siyi-a8-mini-camera-manager) - Tutorial for integrating with the [SIYI A8 mini](https://shop.siyi.biz/products/siyi-a8-mini) using a MAVSDK-based camera manager running on a Raspberry Pi companion computer.
|
||||
- [SIYI A8 mini camera manager](https://github.com/julianoes/siyi-a8-mini-camera-manager) - Tutorial for integrating with the [SIYI A8 mini](https://shop.siyi.biz/products/siyi-a8-mini-gimbal-camera) using a MAVSDK-based camera manager running on a Raspberry Pi companion computer.
|
||||
- [Using a Companion Computer with Pixhawk Controllers](../companion_computer/pixhawk_companion.md)
|
||||
- [Companion Computers > Companion Computer Software](../companion_computer/index.md#companion-computer-software): In particular note [MAVLink-Router](https://github.com/mavlink-router/mavlink-router), which you can setup to route MAVLink traffic between a serial port and an IP link (or other camera manager interface).
|
||||
|
||||
@@ -38,7 +38,7 @@ The following diagram shows an example of a CAN bus connecting a flight controll
|
||||
The diagram does not show any power wiring.
|
||||
Refer to your manufacturer instructions to confirm whether components require separate power or can be powered from the CAN bus itself.
|
||||
|
||||
For more information, see [Cyphal/CAN device interconnection](https://kb.zubax.com/pages/viewpage.action?pageId=2195476) (kb.zubax.com).
|
||||
For more information, see [Cyphal/CAN device interconnection](https://wiki.zubax.com/public/cyphal/CyphalCAN-device-interconnection?pageId=2195476) (kb.zubax.com).
|
||||
While the article is written with the Cyphal protocol in mind, it applies equally to DroneCAN hardware and any other CAN setup.
|
||||
For more advanced scenarios, consult with [On CAN bus topology and termination](https://forum.opencyphal.org/t/on-can-bus-topology-and-termination/1685).
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Auterion Skynode
|
||||
# Auterion Skynode X
|
||||
|
||||
[Skynode](https://auterion.com/product/skynode/) is a powerful flight computer that combines a mission computer, flight controller, video streaming, networking, and cellular connection, in a single tightly integrated device.
|
||||
[Skynode](https://auterion.com/product/skynode-x/) is a powerful flight computer that combines a mission computer, flight controller, video streaming, networking, and cellular connection, in a single tightly integrated device.
|
||||
|
||||
|
||||
|
||||
@@ -12,10 +12,11 @@ Auterion OS and Skynode allow seamless integration with Auterion's other softwar
|
||||
For information about Auterion and Skynode:
|
||||
|
||||
- [auterion.com](https://auterion.com/)
|
||||
- [Skynode](https://auterion.com/product/skynode/) (auterion.com)
|
||||
- [Skynode X](https://auterion.com/product/skynode-x/) (auterion.com)
|
||||
- Skynode Guides:
|
||||
- [Manufacturer's Guide](https://docs.auterion.com/manufacturers/getting-started/readme)
|
||||
- [App Developer's Guide](https://docs.auterion.com/developers/getting-started/readme)
|
||||
- [Vehicle Operation](https://docs.auterion.com/vehicle-operation/auterion-sign-up)
|
||||
- [App Development](https://docs.auterion.com/app-development/app-development)
|
||||
- [Hardware Integration](https://docs.auterion.com/app-development/app-development)
|
||||
|
||||
## Skynode with Vanilla PX4
|
||||
|
||||
@@ -34,7 +35,7 @@ Upstream PX4 will generally work, with the following caveats:
|
||||
|
||||
PX4 `px4_fmu-v5x` binaries for Skynode are built from source using the normal [developer environment](../dev_setup/dev_env.md) and [build commands](../dev_setup/building_px4.md), and are uploaded using either `upload_skynode_usb` or `upload_skynode_wifi` upload targets.
|
||||
|
||||
`upload_skynode_usb` and `upload_skynode_wifi` connect to Skynode via SSH over a network interface using the default (fixed) IP addresses for [USB](https://docs.auterion.com/manufacturers/avionics/skynode/advanced-configuration/connecting-to-skynode) and [WiFi](https://docs.auterion.com/manufacturers/avionics/skynode/advanced-configuration/configuration), and upload a TAR compressed binary to the mission computer.
|
||||
`upload_skynode_usb` and `upload_skynode_wifi` connect to Skynode via SSH over a network interface using the default (fixed) IP addresses for USB and WiFi, respectively (see [AuterionOS System Guide > Building and Flashing PX4 Firmware](https://docs.auterion.com/hardware-integration/auterionos-system-guide/flashing-px4-upstream-firmware)), and upload a TAR compressed binary to the mission computer.
|
||||
The mission computer then decompresses the binary and installs it to the flight controller.
|
||||
|
||||
:::info
|
||||
|
||||
@@ -30,7 +30,7 @@ A few "turnkey" options are listed below:
|
||||
[mro_usb_ftdi_serial_to_jst_gh]: https://store.mrobotics.io/USB-FTDI-Serial-to-JST-GH-p/mro-ftdi-jstgh01-mr.htm
|
||||
[sparkfun_ftdi basic_breakout]: https://www.sparkfun.com/products/9873
|
||||
|
||||
You can also use an off-the-shelf FTDI cable [like this one](https://www.sparkfun.com/products/9717) and connect it to flight controller using the appropriate header adaptor
|
||||
You can also use an off-the-shelf FTDI cable [like this one](https://www.sparkfun.com/ftdi-cable-5v-vcc-3-3v-i-o.html) and connect it to flight controller using the appropriate header adaptor
|
||||
(JST-GH connectors are specified in the Pixhawk standard, but you should confirm the connectors for your flight controller).
|
||||
|
||||
### Logic Level Shifters
|
||||
@@ -40,7 +40,7 @@ In order to resolve this, a level shifter can be implemented to safely convert t
|
||||
|
||||
Options include:
|
||||
|
||||
- [SparkFun Logic Level Converter - Bi-Directional](https://www.sparkfun.com/products/12009)
|
||||
- [SparkFun Logic Level Converter - Bi-Directional](https://www.sparkfun.com/sparkfun-logic-level-converter-bi-directional.html)
|
||||
- [4-channel I2C-safe Bi-directional Logic Level Converter - BSS138](https://www.adafruit.com/product/757)
|
||||
|
||||
## Cameras
|
||||
@@ -78,7 +78,7 @@ However NAT has no way to know where to direct the traffic from an arbitrary ext
|
||||
:::
|
||||
|
||||
A common approach is to set up a virtual private network between the companion and GCS computer (i.e. install a VPN system like [zerotier](https://www.zerotier.com/) on both computers).
|
||||
The companion then uses [mavlink-router](https://github.com/intel/mavlink-router) to route traffic between the serial interface (flight controller) and GCS computer on the VPN network.
|
||||
The companion then uses [mavlink-router](https://github.com/mavlink-router/mavlink-router) to route traffic between the serial interface (flight controller) and GCS computer on the VPN network.
|
||||
|
||||
This method has the benefit that the GCS computer address can be static within the VPN, so the configuration of the _mavlink router_ does not need to change over time.
|
||||
In addition, the communication link is secure because all VPN traffic is encrypted (MAVLink 2 itself does not support encryption).
|
||||
@@ -90,5 +90,6 @@ This approach means that you do not need to know the IP address of the GCS compu
|
||||
|
||||
Some USB modules that are known to work include:
|
||||
|
||||
- [Huawei E8372](https://consumer.huawei.com/en/mobile-broadband/e8372/) and [Huawei E3372](https://consumer.huawei.com/en/mobile-broadband/e3372/)
|
||||
- The _E8372_ includes WiFi which you can use to configure the SIM while it is plugged into the companion (making the development workflow a little easier). The _E3372_ lacks WiFi, so you have to configure it by plugging the stick into a laptop.
|
||||
- [Huawei E8372](https://consumer.huawei.com/au/support/routers/e8372/) and [Huawei E3372](https://consumer.huawei.com/au/support/routers/e3372/)
|
||||
- The _E8372_ includes WiFi which you can use to configure the SIM while it is plugged into the companion (making the development workflow a little easier).
|
||||
The _E3372_ lacks WiFi, so you have to configure it by plugging the stick into a laptop.
|
||||
|
||||
@@ -4,7 +4,7 @@ The [Holybro Pixhawk Jetson Baseboard](https://holybro.com/products/pixhawk-jets
|
||||
|
||||
|
||||
|
||||
The board comes with either the [Jetson Orin NX (16GB RAM)](https://holybro.com/products/nvidia-jetson-orin-nx-16g) or [Jetson Orin Nano (4GB RAM)](https://holybro.com/products/nvidia-jetson-orin-nx-16g?variant=44391410598077).
|
||||
The board comes with either the _Jetson Orin NX_ (16GB RAM) or _Jetson Orin Nano_ (4GB RAM) (see [NVIDIA Jetson Orin™](https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-orin/)).
|
||||
It can be used with any Pixhawk Autopilot Bus (PAB) specification-compliant Pixhawk flight controller, such as the Pixhawk 6 or Pixhawk 6X.
|
||||
|
||||
This guide walks through the process of setting up the board and connecting to PX4, including:
|
||||
@@ -44,7 +44,6 @@ This information comes from the [Holybro Pixhawk-Jetson Baseboard Documentation]
|
||||
[Dimensions and weight](https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard/dimension-and-weight) (Holybro)
|
||||
|
||||
- 크기
|
||||
|
||||
- 126 x 80 x 45mm (with Jetson Orin NX + Heatsink/Fan & FC Module)
|
||||
- 126 x 80 x 22.9mm (without Jetson and FC Module)
|
||||
|
||||
@@ -56,37 +55,30 @@ This information comes from the [Holybro Pixhawk-Jetson Baseboard Documentation]
|
||||
:::tab Jetson connectors
|
||||
|
||||
- 2x Gigabit Ethernet Port
|
||||
|
||||
- Connected to both Jetson & Autopilot via Ethernet switch (RTL8367S)
|
||||
- Ethernet Switch powered by the same circuit as the Pixhawk
|
||||
- 8-pin JST-GH
|
||||
- RJ45
|
||||
|
||||
- 2x MIPI CSI Camera Inputs
|
||||
|
||||
- 4 Lanes each
|
||||
- 22-Pin Raspberry Pi Cam FFC
|
||||
|
||||
- 2x USB 3.0 Host Port
|
||||
|
||||
- USB A
|
||||
- 5A Current Limit
|
||||
|
||||
- 2x USB 2.0 Host Port
|
||||
|
||||
- 5-Pin JST-GH
|
||||
- 0A Current Limit
|
||||
|
||||
- USB 2.0 for Programming/Debugging
|
||||
|
||||
- USB-C
|
||||
|
||||
- 2 Key M 2242/2280 for NVMe SSD
|
||||
|
||||
- PCIEx4
|
||||
|
||||
- 2 Key E 2230 for WiFi/BT
|
||||
|
||||
- PCIEx2
|
||||
- USB
|
||||
- UART
|
||||
@@ -95,27 +87,21 @@ This information comes from the [Holybro Pixhawk-Jetson Baseboard Documentation]
|
||||
- Mini HDMI Out
|
||||
|
||||
- 4x GPIO
|
||||
|
||||
- 6-pin JST-GH
|
||||
|
||||
- CAN Port
|
||||
|
||||
- Connected to Autopilot's CAN2 (4 Pin JST-GH)
|
||||
|
||||
- SPI Port
|
||||
|
||||
- 7-Pin JST-GH
|
||||
|
||||
- I2C Port
|
||||
|
||||
- 4-Pin JST-GH
|
||||
|
||||
- I2S Port
|
||||
|
||||
- 7-Pin JST-GH
|
||||
|
||||
- 2x UART Port
|
||||
|
||||
- 1 for debug
|
||||
- 1 connected to Autopilot's telem2
|
||||
|
||||
@@ -128,12 +114,10 @@ This information comes from the [Holybro Pixhawk-Jetson Baseboard Documentation]
|
||||
:::tab Autopilot connectors
|
||||
|
||||
- Pixhawk Autopilot Bus Interface
|
||||
|
||||
- 100 Pin Hirose DF40
|
||||
- 50 Pin Hirose DF40
|
||||
|
||||
- Redundant Digital Power Module Inputs
|
||||
|
||||
- I2C Power Monitor Support
|
||||
- 2x 6-Pin Molex CLIK-Mate
|
||||
|
||||
@@ -142,66 +126,52 @@ This information comes from the [Holybro Pixhawk-Jetson Baseboard Documentation]
|
||||
- Overvoltage Protection
|
||||
|
||||
- 정격 전압
|
||||
|
||||
- 최대 입력 전압: 6V
|
||||
- USB 전원 입력: 4.75~5.25V
|
||||
|
||||
- Full GPS Plus Safety Switch Port
|
||||
|
||||
- 10-Pin JST-GH
|
||||
|
||||
- Secondary (GPS2) Port
|
||||
|
||||
- 6-Pin JST-GH
|
||||
|
||||
- 2x CAN Ports
|
||||
|
||||
- 4-Pin JST-GH
|
||||
|
||||
- 3x Telemetry Ports with Flow Control
|
||||
|
||||
- 2x 6-Pin JST-GH
|
||||
- 1 is connected to Jetson's `UART1` Port
|
||||
|
||||
- 16 PWM Outputs
|
||||
|
||||
- 2x 10-Pin JST-GH
|
||||
|
||||
- UART4 & I2C Port
|
||||
|
||||
- 6-Pin JST-GH
|
||||
|
||||
- 2x Gigabit Ethernet Port
|
||||
|
||||
- Connected to both Jetson & Autopilot via Ethernet switch (RTL8367S)
|
||||
- 8-Pin JST-GH
|
||||
- RJ45
|
||||
|
||||
- AD & IO
|
||||
|
||||
- 8-Pin JST-GH
|
||||
|
||||
- USB 2.0
|
||||
|
||||
- USB-C
|
||||
- 4-Pin JST-GH
|
||||
|
||||
- DSM Input
|
||||
|
||||
- 3-Pin JST-ZH 1.5mm Pitch
|
||||
|
||||
- RC In
|
||||
|
||||
- PPM/SBUS
|
||||
- 5-Pin JST-GH
|
||||
|
||||
- SPI Port
|
||||
|
||||
- External Sensor Bus (SPI5)
|
||||
- 11-Pin JST-GH
|
||||
|
||||
- 2x Debug Port
|
||||
|
||||
- 1 for FMU
|
||||
- 1 for IO
|
||||
- 10-Pin JST-SH
|
||||
@@ -1333,7 +1303,7 @@ You can now start your ROS2 nodes and continue the development.
|
||||
You can test the Client and agent by using the `sensor_combined` example in [Build ROS 2 Workspace](../ros2/user_guide.md#build-ros-2-workspace) (ROS2 User Guide).
|
||||
|
||||
:::tip
|
||||
[VSCode over SSH](https://code.visualstudio.com/learn/develop-cloud/ssh-lab-machines) enables faster development and application of changes to your ROS 2 code!
|
||||
[VSCode over SSH](https://code.visualstudio.com/docs/remote/ssh) enables faster development and application of changes to your ROS 2 code!
|
||||
:::
|
||||
|
||||
After getting to the point of running the example:
|
||||
|
||||
@@ -42,7 +42,7 @@ Larger high power examples:
|
||||
- [NXP NavQPlus](https://nxp.gitbook.io/navqplus/user-contributed-content/ros2/microdds)
|
||||
- [Nvidia Jetson TX2](https://developer.nvidia.com/embedded/jetson-tx2)
|
||||
|
||||
* [Intel NUC](https://www.intel.com/content/www/us/en/products/details/nuc.html)
|
||||
* [Intel NUC](https://www.asus.com/au/content/nuc-overview/)
|
||||
* [Gigabyte Brix](https://www.gigabyte.com/Mini-PcBarebone/BRIX)
|
||||
|
||||
Small/lower power examples:
|
||||
@@ -78,7 +78,7 @@ You can also write your own custom MAVLink libraries from scratch:
|
||||
|
||||
You will need a router if you need to bridge MAVLink from the vehicle to a ground station or IP network, or if you need multiple connections:
|
||||
|
||||
- [MAVLink Router](https://github.com/intel/mavlink-router) (recommended)
|
||||
- [MAVLink Router](https://github.com/mavlink-router/mavlink-router) (recommended)
|
||||
- [MAVProxy](https://ardupilot.org/mavproxy/)
|
||||
|
||||
## Ethernet Setup
|
||||
|
||||
@@ -20,7 +20,7 @@ The high level benefits of _WFB-ng_ include:
|
||||
- Bidirectional telemetry link (MAVLink).
|
||||
- TCP/IP tunnel.
|
||||
- Automatic TX diversity - use multiple cards on the ground to avoid antenna tracker.
|
||||
- Full link encryption and authentication (using [libsodium](https://download.libsodium.org/doc/)).
|
||||
- Full link encryption and authentication (using [libsodium](https://doc.libsodium.org/)).
|
||||
- Aggregation of MAVLink packets (pack small packets into batches before transmitting).
|
||||
- Enhanced [OSD](https://github.com/svpcom/wfb-ng-osd) for Raspberry PI or generic linux desktop with gstreamer.
|
||||
|
||||
@@ -36,21 +36,19 @@ The vehicle setup consists of:
|
||||
|
||||
- A camera.
|
||||
These have been tested:
|
||||
|
||||
- [Raspberry Pi camera](https://www.raspberrypi.org/products/camera-module-v2/) connected via CSI.
|
||||
- [Logitech camera C920](https://www.logitech.com/en-us/product/hd-pro-webcam-c920?crid=34) connected via USB
|
||||
- [Logitech camera C920](https://support.logi.com/hc/en-us/articles/360024326953-Getting-started-HD-Pro-Webcam-C920) connected via USB
|
||||
|
||||
- WiFi module [ALPHA AWUS036ACH](https://www.alfa.com.tw/products_detail/1.htm) or any other **RTL8812au** card.
|
||||
- WiFi module [ALPHA AWUS036ACH](https://www.alfa.com.tw/products/awus036ach_1?variant=40319795789896) or any other **RTL8812au** card.
|
||||
|
||||
### Ground Station
|
||||
|
||||
- Ground Station Computer.
|
||||
These options have been tested:
|
||||
|
||||
- Any Linux computer with a USB port (tested on Ubuntu 18.04 x86-64)
|
||||
- A computer with any OS running QGround control and Raspberry PI connected via Ethernet (RPi provides the wifi connection).
|
||||
|
||||
- WiFi module [ALPHA AWUS036ACH](https://www.alfa.com.tw/products_detail/1.htm) or any other **RTL8812au** card.
|
||||
- WiFi module [ALPHA AWUS036ACH](https://www.alfa.com.tw/products/awus036ach_1?variant=40319795789896) or any other **RTL8812au** card.
|
||||
See [WFB-ng wiki > WiFi hardware](https://github.com/svpcom/wfb-ng/wiki/WiFi-hardware) for more information on supported modules.
|
||||
|
||||
## Hardware Modification
|
||||
@@ -125,7 +123,7 @@ If you need a higher bandwidth you can use other MCS index (for example 2 or gre
|
||||
|
||||
## Antennas and Diversity
|
||||
|
||||
For simple cases you can use omnidirectional antennas with linear (that bundled with wifi cards) or circular leaf ([circularly polarized Coverleaf Antenna](http://www.antenna-theory.com/antennas/cloverleaf.php)) polarization.
|
||||
For simple cases you can use omnidirectional antennas with linear (that bundled with wifi cards) or circular leaf ([circularly polarized Coverleaf Antenna](https://www.antenna-theory.com/antennas/cloverleaf.php)) polarization.
|
||||
If you want to setup long distance link you can use multiple wifi adapters with directional and omnidirectional antennas. TX/RX diversity for multiple adapters supported out of box (just add multiple NICs to `/etc/default/wifibroadcast`).
|
||||
If your WiFi adapter has two antennas (like Alfa AWU036ACH) TX diversity is implemented via [STBC](https://en.wikipedia.org/wiki/Space%E2%80%93time_block_code).
|
||||
Cards with 4 ports (like Alfa AWUS1900) are currently not supported.
|
||||
|
||||
@@ -12,7 +12,7 @@ You can find others on [px4.io](https://px4.io/ecosystem/commercial-systems/) an
|
||||
This section contains consumer vehicles that run a _custom_ version of PX4 (supported by their vendors).
|
||||
These may or may not be updatable to run "vanilla" PX4.
|
||||
|
||||
- [Sentera PXH](https://sentera.com/products/fieldcapture/ag-drones/phx/)
|
||||
- [Sentera PXH](https://senterasensors.com/phx/)
|
||||
|
||||
<!--
|
||||
## Drone Development Kits/Reference Platforms
|
||||
|
||||
@@ -104,7 +104,7 @@ It is pre-installed with PX4 v1.15.4 at time of writing (a more recent version m
|
||||
|
||||
## Tutorials
|
||||
|
||||
- Tutorials [English](https://docs.amovlab.com/f450-v6c-wiki/#/en/)/[Chinese](https://docs.amovlab.com/F450-V6C-wiki/#/src/%E8%A7%84%E6%A0%BC%E5%8F%82%E6%95%B0/%E8%A7%84%E6%A0%BC%E5%8F%82%E6%95%B0) (docs.amovlab.com/)
|
||||
- Tutorials [English](https://docs.amovlab.com/f450-v6c-wiki/#/en/)/[Chinese](https://docs.amovlab.com/f450-v6c-wiki/#/) (docs.amovlab.com/)
|
||||
|
||||
## Upgrading
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ After setting up the PX4 development environment, follow these steps to install
|
||||
1. Download the source code of the PX4 Bootloader:
|
||||
|
||||
```sh
|
||||
git clone https://github.com/PX4/Bootloader.git
|
||||
git clone https://github.com/PX4/PX4-Bootloader.git
|
||||
```
|
||||
|
||||
2. Navigate into the top directory of the source code and compile it using:
|
||||
@@ -257,7 +257,7 @@ Crazyflie is able to fly in _Altitude_ mode if you use a [Z-ranger deck](https:/
|
||||
According to the datasheet, the maximum height (above ground) the range finder can sense is 2 m. However, when tested on dark surfaces this value decreases to 0.5 m. On a light floor, it goes up to max 1.3 m. This means you cannot hold altitudes above this value in _Altitude_ or _Position_ flight modes.
|
||||
|
||||
:::tip
|
||||
If the Crazyflie 2.0 height drifts at mid-throttle command in _Altitude mode_ or _Position mode_, first try rebooting the vehicle. If this does not fix the problem, recalibrate the accel and mag (compass).\
|
||||
If the Crazyflie 2.0 height drifts at mid-throttle command in _Altitude mode_ or _Position mode_, first try rebooting the vehicle. If this does not fix the problem, recalibrate the accel and mag (compass).
|
||||
:::
|
||||
|
||||
:::info
|
||||
|
||||
@@ -65,7 +65,7 @@ After setting up the PX4 development environment, follow these steps to install
|
||||
1. Download the source code of the PX4 Bootloader:
|
||||
|
||||
```sh
|
||||
git clone https://github.com/PX4/Bootloader.git --recurse-submodules
|
||||
git clone https://github.com/PX4/PX4-Bootloader.git --recurse-submodules
|
||||
```
|
||||
|
||||
2. Navigate into the top directory of the source code and compile it using:
|
||||
|
||||
@@ -19,12 +19,12 @@ They may come either fully assembled or in parts.
|
||||
|
||||
This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed.
|
||||
|
||||
- [Teal One](https://tealdrones.com/teal-one/)
|
||||
- [ModalAI Starling](../complete_vehicles_mc/modalai_starling.md)
|
||||
- [ModalAI Sentinel](https://www.modalai.com/sentinel)
|
||||
- [MindRacer 210](../complete_vehicles_mc/mindracer210.md)
|
||||
- [NanoMind 110](../complete_vehicles_mc/nanomind110.md)
|
||||
- [Amovlab F410](../complete_vehicles_mc/amov_F410_drone.md)
|
||||
- [Teal One](https://px4.io/project/teal-one/) ([superseded](https://tealdrones.com/solutions/teal-2/))
|
||||
|
||||
## PX4 Compatible
|
||||
|
||||
@@ -42,7 +42,7 @@ These may or may not be updatable to run "vanilla" PX4.
|
||||
- [Yuneec Typhoon H Plus](https://us.yuneec.com/typhoon-h-plus/)
|
||||
- [Yuneec Mantis Q](https://px4.io/portfolio/yuneec-mantis-q/)
|
||||
- [Yuneec H520](https://px4.io/portfolio/yuneec-h520-hexacopter/)
|
||||
- [AeroSense Aerobo (AS-MC02-P)](https://px4.io/portfolio/aerosense-aerobo/)
|
||||
- [AeroSense Aerobo (AS-MC02-P)](https://px4.io/project/aerosense-aerobo/)
|
||||
|
||||
## See Also
|
||||
|
||||
|
||||
@@ -75,7 +75,6 @@ What's inside the PX4 Vision V1 can be found here in the [PX4 v1.13 Docs here](h
|
||||
The PX4 Vision DevKit contains following components:
|
||||
|
||||
- Core Components:
|
||||
|
||||
- 1x Pixhawk 4 or Pixhawk 6C (for v1.5) flight controller
|
||||
- 1x PMW3901 optical flow sensor
|
||||
- 1x TOF Infrared distance sensor (PSK‐CM8JL65‐CC5)
|
||||
@@ -96,7 +95,6 @@ The PX4 Vision DevKit contains following components:
|
||||
- WiFi 802.11 b/g/n @ 2.4 GHz (attached to external antenna #1). Allows computer to access home WiFi network for Internet access/updates.
|
||||
|
||||
- Mechanical Specification:
|
||||
|
||||
- Frame: Full 5mm 3k carbon fiber twill
|
||||
- Motors: T-MOTOR KV1750
|
||||
- ESC: BEHEli-S 20A ESC
|
||||
@@ -107,7 +105,6 @@ The PX4 Vision DevKit contains following components:
|
||||
- Telemetry: ESP8266 connected to flight controller (attached to external antenna #2). Enables wireless connection to the ground station.
|
||||
|
||||
- A USB2.0 stick with pre-flashed software that bundles:
|
||||
|
||||
- Ubuntu 18.04 LTS
|
||||
- ROS Melodic
|
||||
- Occipital Structure Core ROS driver
|
||||
@@ -135,7 +132,6 @@ In addition, users will need ground station hardware/software:
|
||||
## First-time Setup
|
||||
|
||||
1. Attach a [compatible RC receiver](../getting_started/rc_transmitter_receiver.md#connecting-receivers) to the vehicle (not supplied with kit):
|
||||
|
||||
- Remove/unscrew the top plate (where the battery goes) using an H2.0 hex key tool.
|
||||
- [Connect the receiver to the flight controller](../assembly/quick_start_pixhawk4.md#radio-control).
|
||||
- Re-attach the top plate.
|
||||
@@ -222,7 +218,6 @@ When the vehicle setup described above is complete:
|
||||
:::
|
||||
|
||||
3. Check that the avoidance system has started properly:
|
||||
|
||||
- The _QGroundControl_ notification log displays the message: **Avoidance system connected**.
|
||||
|
||||
|
||||
@@ -339,7 +334,6 @@ To login to the companion computer:
|
||||
The Ubuntu login screen should then appear on the monitor.
|
||||
|
||||
3. Login to the _UP Core_ using the credentials:
|
||||
|
||||
- **Username:** px4vision
|
||||
- **Password:** px4vision
|
||||
|
||||
@@ -391,7 +385,7 @@ To integrate a different planner, this needs to be disabled.
|
||||
```
|
||||
|
||||
The ROS workspace is placed in `~/catkin_ws`.
|
||||
For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](http://wiki.ros.org/catkin/Tutorials).
|
||||
For reference on developing in ROS and using the catkin workspace, see the [ROS catkin tutorials](https://wiki.ros.org/catkin/Tutorials).
|
||||
|
||||
### Developing PX4 Firmware
|
||||
|
||||
|
||||
@@ -46,9 +46,7 @@ To setup ROS and PX4:
|
||||
|
||||
- [Verify that VIO is set up correctly](#verify_estimate) before your first flight!
|
||||
|
||||
<a id="vio_ros_node"></a>
|
||||
|
||||
### ROS VIO node
|
||||
### ROS VIO node {#vio_ros_node}
|
||||
|
||||
In this suggested setup, a ROS node is required to
|
||||
|
||||
@@ -58,17 +56,16 @@ In this suggested setup, a ROS node is required to
|
||||
|
||||
The implementation of the ROS node will be specific to the camera used and will need to be developed to use the interface and drivers appropriate for the camera.
|
||||
|
||||
The odometry messages should be of the type [`nav_msgs/Odometry`](http://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html) and published to the topic `/mavros/odometry/out`.
|
||||
The odometry messages should be of the type [`nav_msgs/Odometry`](https://docs.ros.org/en/noetic/api/nav_msgs/html/msg/Odometry.html) and published to the topic `/mavros/odometry/out`.
|
||||
|
||||
System status messages of the type [`mavros_msgs/CompanionProcessStatus`](https://github.com/mavlink/mavros/blob/master/mavros_msgs/msg/CompanionProcessStatus.msg) should be published to the topic `/mavros/companion_process/status`. These should identify the component as `MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY` (197) and indicate the `state` of the system. Recommended status values are:
|
||||
System status messages of the type [`mavros_msgs/CompanionProcessStatus`](https://github.com/mavlink/mavros/blob/master/mavros_msgs/msg/CompanionProcessStatus.msg) should be published to the topic `/mavros/companion_process/status`.
|
||||
These should identify the component as `MAV_COMP_ID_VISUAL_INERTIAL_ODOMETRY` (197) and indicate the `state` of the system. Recommended status values are:
|
||||
|
||||
- `MAV_STATE_ACTIVE` when the VIO system is functioning as expected,
|
||||
- `MAV_STATE_CRITICAL` when the VIO system is functioning, but with low confidence, and
|
||||
- `MAV_STATE_FLIGHT_TERMINATION` when the system has failed or the estimate confidence is unacceptably low.
|
||||
|
||||
<a id="ekf2_tuning"></a>
|
||||
|
||||
### PX4 튜닝
|
||||
### PX4 Tuning {#ekf2_tuning}
|
||||
|
||||
EKF2에서 외부 위치 정보를 사용하려면 다음 매개 변수를 설정하여야 합니다.
|
||||
|
||||
@@ -83,9 +80,7 @@ These can be set in _QGroundControl_ > **Vehicle Setup > Parameters > EKF2** (re
|
||||
|
||||
For more detailed/additional information, see: [Using PX4's Navigation Filter (EKF2) > External Vision System](../advanced_config/tuning_the_ecl_ekf.md#external-vision-system).
|
||||
|
||||
<a id="tuning-EKF2_EV_DELAY"></a>
|
||||
|
||||
#### EKF2_EV_DELAY 튜닝
|
||||
#### Tuning EKF2_EV_DELAY {#tuning-EKF2_EV_DELAY}
|
||||
|
||||
[EKF2_EV_DELAY](../advanced_config/parameter_reference.md#EKF2_EV_DELAY) is the _Vision Position Estimator delay relative to IMU measurements_.
|
||||
즉, 비전 시스템 타임스탬프와 IMU 클록 (EKF2의 "기본 클록")에 의해 기록된 "실제" 캡처 시간 간의 차이입니다.
|
||||
@@ -104,9 +99,7 @@ A plot of external data vs. onboard estimate (as above) can be generated using [
|
||||
|
||||
이 값은 동적 기동 중에 가장 낮은 EKF 혁신을 산출하는 값을 찾기 위하여, 매개변수를 변경하여 추가 튜닝할 수 있습니다.
|
||||
|
||||
<a id="verify_estimate"></a>
|
||||
|
||||
## VIO 예상치 확인
|
||||
## Check/Verify VIO Estimate {#verify_estimate}
|
||||
|
||||
:::info
|
||||
The [MAV_ODOM_LP](../advanced_config/parameter_reference.md#MAV_ODOM_LP) parameter mentioned below was removed in PX4 v1.14.
|
||||
@@ -153,11 +146,9 @@ First, make sure MAVROS is able to connect successfully to the flight controller
|
||||
제대로 연결되는 경우 일반적인 문제 해결 방법은 다음과 같습니다.
|
||||
|
||||
- **Problem:** I get drift / flyaways when the drone flies, but not when I carry it around with the props off.
|
||||
|
||||
- If using the [T265](../peripherals/camera_t265_vio.md) try soft-mounting it (this camera is very sensitive to high-frequency vibrations).
|
||||
|
||||
- **Problem:** I get toilet-bowling when VIO is enabled.
|
||||
|
||||
- 카메라의 방향이 시작 파일의 변환과 일치하는 지 확인합니다.
|
||||
Use the _QGroundControl_ [MAVLink Inspector](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_inspector.html) to verify that the velocities in the `ODOMETRY` message coming from MAVROS are aligned to the FRD coordinate system.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
PX4 consists of two main layers: the [flight stack](#flight-stack) is an estimation and flight control system,
|
||||
and the [middleware](#middleware) is a general robotics layer that can support any type of autonomous robot, providing internal/external communications and hardware integration.
|
||||
|
||||
All PX4 [airframes](../airframes/index.md) share a single codebase (this includes other robotic systems like boats, rovers, submarines etc.). The complete system design is [reactive](http://www.reactivemanifesto.org), which means that:
|
||||
All PX4 [airframes](../airframes/index.md) share a single codebase (this includes other robotic systems like boats, rovers, submarines etc.). The complete system design is [reactive](https://www.reactivemanifesto.org), which means that:
|
||||
|
||||
- 모든 기능은 대체 가능한 구성 요소와 재사용 가능한 구성 요소로 나누어 집니다.
|
||||
- 통신은 비동기 메시지 전달에 의해 수행됩니다.
|
||||
|
||||
@@ -42,7 +42,7 @@ Overview of the mixing pipeline in terms of modules and uORB topics (press to sh
|
||||
- publishes the servo trims separately so they can be added as an offset when [testing actuators](../config/actuators.md#actuator-testing) (using the test sliders).
|
||||
- the output drivers:
|
||||
- handle the hardware initialization and update
|
||||
- use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module/).
|
||||
- use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module).
|
||||
The driver defines a parameter prefix, e.g. `PWM_MAIN` that the library then uses for configuration.
|
||||
Its main task is to select from the input topics and assign the right data to the outputs based on the user set `<param_prefix>_FUNCx` parameter values.
|
||||
For example if `PWM_MAIN_FUNC3` is set to **Motor 2**, the 3rd output is set to the 2nd motor from `actuator_motors`.
|
||||
|
||||
@@ -78,7 +78,6 @@ Explanations and requirements:
|
||||
This means as long as the event name stays the same, so will the ID.
|
||||
|
||||
- **Log Level**:
|
||||
|
||||
- valid log levels are the same as used in the MAVLink [MAV_SEVERITY](https://mavlink.io/en/messages/common.html#MAV_SEVERITY) enum.
|
||||
In order of descending importance these are:
|
||||
|
||||
@@ -117,7 +116,7 @@ Valid types: `uint8_t`, `int8_t`, `uint16_t`, `int16_t`, `uint32_t`, `int32_t`,
|
||||
You can also use enumerations as arguments:
|
||||
|
||||
- PX4-specific/custom enumerations for events should be defined in [src/lib/events/enums.json](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/events/enums.json), and can then be used as event argument in the form of `events::send<events::px4::enums::my_enum_t>(...)`.
|
||||
- MAVLink "common" events are defined in [mavlink/libevents/events/common.json](https://github.com/mavlink/libevents/blob/master/events/common.json) and can be used as event argument in the form of `events::send<events::common::enums::my_enum_t>(...)`.
|
||||
- MAVLink "common" events are defined in [mavlink/libevents/events/common.json](https://github.com/mavlink/libevents/blob/main/events/common.json) and can be used as event argument in the form of `events::send<events::common::enums::my_enum_t>(...)`.
|
||||
|
||||
#### Text format
|
||||
|
||||
@@ -128,7 +127,6 @@ Text format for event message description:
|
||||
These have to be escaped: '\\\\', '\\<', '\\{'.
|
||||
|
||||
- supported tags:
|
||||
|
||||
- Profiles: `<profile name="[!]NAME">CONTENT</profile>`
|
||||
|
||||
`CONTENT` will only be shown if the name matches the configured profile.
|
||||
@@ -142,7 +140,6 @@ Text format for event message description:
|
||||
- no nested tags of the same type are allowed
|
||||
|
||||
- arguments: template placeholders that follow python syntax, with 1-based indexing (instead of 0)
|
||||
|
||||
- general form: `{ARG_IDX[:.NUM_DECIMAL_DIGITS][UNIT]}`
|
||||
|
||||
UNIT:
|
||||
|
||||
@@ -5,7 +5,7 @@ On NuttX they reside in the [ROMFS/px4fmu_common/init.d](https://github.com/PX4/
|
||||
The scripts that are only used on Posix are located in [ROMFS/px4fmu_common/init.d-posix](https://github.com/PX4/PX4-Autopilot/tree/main/ROMFS/px4fmu_common/init.d-posix).
|
||||
|
||||
All files starting with a number and underscore (e.g. `10000_airplane`) are predefined airframe configurations.
|
||||
They are exported at build-time into an `airframes.xml` file which is parsed by [QGroundControl](http://qgroundcontrol.com) for the airframe selection UI.
|
||||
They are exported at build-time into an `airframes.xml` file which is parsed by [QGroundControl](https://qgroundcontrol.com) for the airframe selection UI.
|
||||
Adding a new configuration is covered [here](../dev_airframes/adding_a_new_frame.md).
|
||||
|
||||
나머지 파일은 공통 시작 로직의 일부입니다.
|
||||
@@ -33,7 +33,7 @@ Posix에서 시스템 셸은 스크립트 인터프리터로 사용됩니다(예
|
||||
|
||||
- 쉘은 각 모듈을 새로운(클라이언트) 프로세스로 시작합니다.
|
||||
각 클라이언트 프로세스는 실제 모듈이 스레드로 실행되는 px4(서버)의 기본 인스턴스와 통신합니다.
|
||||
This is done through a [UNIX socket](http://man7.org/linux/man-pages/man7/unix.7.html).
|
||||
This is done through a [UNIX socket](https://man7.org/linux/man-pages/man7/unix.7.html).
|
||||
서버는 클라이언트가 연결하고 명령을 보낼 수 있는 소켓으로 수신 대기합니다.
|
||||
그런 다음 서버는 출력과 반환 코드를 다시 클라이언트로 전송합니다.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ Most other steps can be done out of order, except for [tuning](#tuning), which m
|
||||
|
||||
## 전제 조건
|
||||
|
||||
Before starting you should [Download QGroundControl](http://qgroundcontrol.com/downloads/) and install it on your **desktop** computer.
|
||||
Before starting you should [Download QGroundControl](https://qgroundcontrol.com/downloads/) and install it on your **desktop** computer.
|
||||
Then open the QGC application menu ("Q" icon in the top-left corner) and choose **Vehicle Setup** in the _Select Tool_ popup:
|
||||
|
||||
|
||||
@@ -77,7 +77,6 @@ If you need help with the configuration you can ask for help on the [QGroundCont
|
||||
- [Flight Controller Peripherals](../peripherals/index.md) - Setup specific sensors, optional sensors, actuators, and so on.
|
||||
- [Advanced Configuration](../advanced_config/index.md) - Factory/OEM calibration, configuring advanced features, less-common configuration.
|
||||
- Vehicle-Centric Config/Tuning:
|
||||
|
||||
- [Multicopter Config/Tuning](../config_mc/index.md)
|
||||
- [Helicopter Config/Tuning](../config_heli/index.md)
|
||||
- [Fixed-wing Config/Tuning](../config_fw/index.md)
|
||||
|
||||
@@ -12,7 +12,7 @@ This approach may be used by manual control units that have an integrated ground
|
||||
:::
|
||||
|
||||
:::info
|
||||
_QGroundControl_ uses the cross-platform [SDL2](http://www.libsdl.org/index.php) library to convert joystick movements to MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages, which are then sent to PX4 over the telemetry channel.
|
||||
_QGroundControl_ uses the cross-platform [SDL2](https://www.libsdl.org/index.php) library to convert joystick movements to MAVLink [MANUAL_CONTROL](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL) messages, which are then sent to PX4 over the telemetry channel.
|
||||
결과적으로 조이스틱 기반 제어 시스템은 차량이 조이스틱 움직임에 반응하기 위해 안정적인 고대역폭 원격 채널이 필요합니다.
|
||||
:::
|
||||
|
||||
|
||||
@@ -58,7 +58,7 @@ Users can select the form that is used by setting the proportional gain for the
|
||||
두 가지 형식이 아래에 기술되어 있습니다.
|
||||
|
||||
:::info
|
||||
The derivative term (**D**) is on the feedback path in order to avoid an effect known as the [derivative kick](http://brettbeauregard.com/blog/2011/04/improving-the-beginner%E2%80%99s-pid-derivative-kick/).
|
||||
The derivative term (**D**) is on the feedback path in order to avoid an effect known as the [derivative kick](http://brettbeauregard.com/blog/2011/04/improving-the-beginners-pid-derivative-kick/).
|
||||
:::
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -14,7 +14,7 @@ We try to retain a [linear history through rebases](https://www.atlassian.com/gi
|
||||
To contribute new functionality, [sign up for Github](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account), then [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the repository, [create a new branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository), add your [changes as commits](#commits-and-commit-messages), and finally [send a pull request](#pull-requests).
|
||||
Changes will be merged when they pass our [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) tests.
|
||||
|
||||
All code contributions have to be under the permissive [BSD 3-clause license](https://opensource.org/licenses/BSD-3-Clause) and all code must not impose any further constraints on the use.
|
||||
All code contributions have to be under the permissive [BSD 3-clause license](https://opensource.org/license/BSD-3-Clause) and all code must not impose any further constraints on the use.
|
||||
|
||||
## Code Style
|
||||
|
||||
@@ -114,7 +114,7 @@ Source-code documentation standards are not enforced, and the code is currently
|
||||
- Do not add documentation that can trivially be inferred from C++ entity names.
|
||||
- ALWAYS specify units of variables, constants, and input/return parameters where they are defined.
|
||||
- 일반적으로 특이 사항이나 오류 처리에 대한 정보를 추가할 수 있습니다.
|
||||
- [Doxgyen](http://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
|
||||
- [Doxgyen](https://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
|
||||
A good example of usage is [src/modules/events/send_event.h](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/events/send_event.h).
|
||||
|
||||
Please avoid "magic numbers", for example, where does this number in the conditional come from? What about the multiplier on yaw stick input?
|
||||
|
||||
@@ -29,11 +29,11 @@ The Community Q&A call is open to all interested community members.
|
||||
|
||||
## 회의 목적
|
||||
|
||||
We publish a forum post per meeting a week before the call on [PX4 Discuss - weekly-dev-call](https://discuss.px4.io/c/weekly-dev-call) and track the agenda write down the discussion for the day. We welcome any topics that you, as a community member may have questions about / want to discuss!
|
||||
We publish a forum post per meeting a week before the call on [PX4 Discuss - weekly-dev-call](https://discuss.px4.io/c/weekly-dev-call/14) and track the agenda write down the discussion for the day. We welcome any topics that you, as a community member may have questions about / want to discuss!
|
||||
|
||||
Please add your topics for discussion to the agenda before the meeting begins, by replying to the meeting note. This will help you formulate your questions more clearly, and allow us to think about them in advance.
|
||||
|
||||
## 일정
|
||||
|
||||
- TIME: Wednesday 17h00 CET ([subscribe to calendar](https://www.dronecode.org/calendar/))
|
||||
- TIME: Wednesday 17h00 CET ([subscribe to calendar](https://dronecode.org/calendar/))
|
||||
- **Join the call**: [https://discord.gg/BDYmr6FA6Q](https://discord.gg/BDYmr6FA6Q)
|
||||
|
||||
@@ -38,7 +38,7 @@ For these kinds of changes we suggest using the same approach as for _code_:
|
||||
1. Use the _git_ toolchain to get the PX4 source code onto your local computer.
|
||||
2. 필요한 문서를 수정합니다(추가, 변경, 삭제).
|
||||
3. _Test_ that it builds properly using Vitepress.
|
||||
4. Create a branch for your changes and create a pull request (PR) to pull it back into the [PX4-Autopilot](https://github.com/PX4/PX4-Autopilot.git) repo.
|
||||
4. Create a branch for your changes and create a pull request (PR) to pull it back into the [PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) repo.
|
||||
|
||||
다음에는 소스 코드를 가져오고, 로컬에서 빌드(테스트용)하고, 코드를 수정하는 방법을 설명합니다.
|
||||
|
||||
@@ -58,7 +58,7 @@ If you already have a clone of the [PX4-Autopilot](https://github.com/PX4/PX4-Au
|
||||
|
||||
1. Download git for your computer from [https://git-scm.com/downloads](https://git-scm.com/downloads)
|
||||
|
||||
2. [Sign up](https://github.com/join) for Github if you haven't already
|
||||
2. [Sign up](https://github.com/signup) for Github if you haven't already
|
||||
|
||||
3. Create a copy (Fork) of the [PX4-Autopilot repo](https://github.com/PX4/PX4-Autopilot) on Github ([instructions here](https://docs.github.com/en/get-started/quickstart/fork-a-repo)).
|
||||
|
||||
@@ -135,7 +135,6 @@ Within the repository you created above:
|
||||
새 분기가 분기된 저장소로 푸시되었다는 메시지가 표시되어야 합니다.
|
||||
|
||||
7. 풀 요청(PR) 생성:
|
||||
|
||||
- On the right hand side of the "new branch message" (see one step before), you should see a green button saying "Compare & Create Pull Request".
|
||||
클릭합니다.
|
||||
- 풀 요청 템플릿이 생성됩니다.
|
||||
@@ -153,7 +152,6 @@ Within the repository you created above:
|
||||
로컬에서 라이브러리를 빌드하여, 변경 사항이 제대로 반영되었는 지를 테스트합니다.
|
||||
|
||||
1. Install the [Vitepress prerequisites](https://vitepress.dev/guide/getting-started#prerequisites):
|
||||
|
||||
- [Nodejs 18+](https://nodejs.org/en)
|
||||
- [Yarn classic](https://classic.yarnpkg.com/en/docs/install)
|
||||
|
||||
@@ -234,7 +232,6 @@ The guide uses the [Vitepress](https://vitepress.dev/) toolchain.
|
||||
- 이렇게 하면 다른 페이지와 이미지가 항상 동일한 상대 수준이므로 연결이 더 용이해집니다.
|
||||
|
||||
- The _structure_ of the book is defined in `SUMMARY.md`.
|
||||
|
||||
- If you add a new page to the guide you must also add an entry to this file!
|
||||
|
||||
:::tip
|
||||
@@ -260,7 +257,6 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
|
||||
## 스타일 가이드
|
||||
|
||||
1. 파일/파일명
|
||||
|
||||
- Put new markdown files in an appropriate sub-folder of `/en/`, such as `/en/contribute/`.
|
||||
폴더를 중첩하지 마십시오.
|
||||
- Put new image files in an appropriate nested sub-folder of `/assets/`.
|
||||
@@ -270,14 +266,12 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
|
||||
- Use lower case filenames and separate words using underscores (`_`).
|
||||
|
||||
2. 이미지
|
||||
|
||||
- 이미지는 최대한 가장 작은 크기와 가장 낮은 해상도를 사용합니다(이렇게 하면 대역폭이 좋지 않은 사용자의 다운로드 비용이 줄어듭니다).
|
||||
- New images should be created in a sub-folder of `/assets/` (so they can be shared between translations).
|
||||
- SVG files are preferred for diagrams.
|
||||
PNG files are preferred over JPG for screenshots.
|
||||
|
||||
3. 내용
|
||||
|
||||
- Use "style" (**bold**, _emphasis_, etc.) consistently and sparingly (as little as possible).
|
||||
- **Bold** for button presses and menu definitions.
|
||||
- _Emphasis_ for tool names such as _QGroundControl_ or _prettier_.
|
||||
@@ -292,7 +286,6 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
|
||||
- Format using _prettier_ (_VSCode_ is a has extensions can be used for this).
|
||||
|
||||
4. Videos:
|
||||
|
||||
- Youtube videos can be added using the format `<lite-youtube videoid="<youtube-video-id>" title="your title"/>` (supported via the [https://www.npmjs.com/package/lite-youtube-embed](https://www.npmjs.com/package/lite-youtube-embed) custom element, which has other parameters you can pass).
|
||||
- Use instructional videos sparingly as they date badly, and are hard to maintain.
|
||||
- Cool videos of airframes in flight are always welcome.
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
|
||||
PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4에 기여 결과를 공유할 수 있습니다.
|
||||
|
||||
- [Sign up](https://github.com/join) for github if you haven't already
|
||||
- [Sign up](https://github.com/signup) for github if you haven't already
|
||||
|
||||
- Fork the PX4-Autopilot repo (see [here](https://docs.github.com/en/get-started/quickstart/fork-a-repo))
|
||||
|
||||
@@ -49,7 +49,7 @@ PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4
|
||||
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`](http://nuclearsquid.com/writings/git-add/).
|
||||
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/).
|
||||
|
||||
- 변경 사항을 설명하는 메시지와 함께 추가된 파일을 커밋합니다.
|
||||
|
||||
@@ -292,7 +292,7 @@ If a conflict occurs during a `git rebase`, please refer to [this guide](https:/
|
||||
|
||||
### 풀 병합 충돌
|
||||
|
||||
If a conflict occurs during a `git pull`, please refer to [this guide](https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/#competing-line-change-merge-conflicts).
|
||||
If a conflict occurs during a `git pull`, please refer to [this guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line#competing-line-change-merge-conflicts).
|
||||
|
||||
### 오래된 git 태그로 인한 빌드 오류
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user