diff --git a/docs/ko/SUMMARY.md b/docs/ko/SUMMARY.md index e0d537903d..8046208ff9 100644 --- a/docs/ko/SUMMARY.md +++ b/docs/ko/SUMMARY.md @@ -179,8 +179,6 @@ - [Wiring Quickstart](assembly/quick_start_durandal.md) - [Holybro Pix32 v5](flight_controller/holybro_pix32_v5.md) - [Wiring Quickstart](assembly/quick_start_holybro_pix32_v5.md) - - [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) - [mRo Control Zero F7](flight_controller/mro_control_zero_f7.md) - [Sky-Drones AIRLink](flight_controller/airlink.md) @@ -205,6 +203,8 @@ - [Holybro Kakute F7](flight_controller/kakutef7.md) - [Holybro Pixfalcon](flight_controller/pixfalcon.md) - [Holybro pix32 (FMUv2)](flight_controller/holybro_pix32.md) + - [ModalAI Flight Core v1](flight_controller/modalai_fc_v1.md) + - [ModalAI VOXL Flight](flight_controller/modalai_voxl_flight.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) @@ -833,6 +833,7 @@ - [시험 MC_04 - 안전 장치 시험](test_cards/mc_04_failsafe_testing.md) - [시험 MC_05 - 실내 비행 (수동 모드)](test_cards/mc_05_indoor_flight_manual_modes.md) - [단위 테스트](test_and_ci/unit_tests.md) + - [Fuzz Tests](test_and_ci/fuzz_tests.md) - [지속 통합](test_and_ci/continous_integration.md) - [Integration Testing](test_and_ci/integration_testing.md) - [MAVSDK 통합 테스트](test_and_ci/integration_testing_mavsdk.md) diff --git a/docs/ko/advanced_config/tuning_the_ecl_ekf.md b/docs/ko/advanced_config/tuning_the_ecl_ekf.md index 1568a23e05..15977dbc40 100644 --- a/docs/ko/advanced_config/tuning_the_ecl_ekf.md +++ b/docs/ko/advanced_config/tuning_the_ecl_ekf.md @@ -389,7 +389,6 @@ It is further configured using the `EKF2_RNG_A_` parameters: - [EKF2_RNG_A_VMAX](../advanced_config/parameter_reference.md#EKF2_RNG_A_VMAX): Maximum horizontal speed, above which range aid is disabled. - [EKF2_RNG_A_HMAX](../advanced_config/parameter_reference.md#EKF2_RNG_A_HMAX): Maximum height, above which range aid is disabled. -- [EKF2_RNG_A_IGATE](../advanced_config/parameter_reference.md#EKF2_RNG_A_IGATE): Range aid consistency checks "gate" (a measure of the error before range aid is disabled). #### Range height fusion diff --git a/docs/ko/camera/fc_connected_camera.md b/docs/ko/camera/fc_connected_camera.md index 11b8dafc88..ca8fe2e5e8 100644 --- a/docs/ko/camera/fc_connected_camera.md +++ b/docs/ko/camera/fc_connected_camera.md @@ -246,7 +246,7 @@ Note that Pic2Map is limited to only 40 images. ### Reconstruction -We use [Pix4D](https://pix4d.com/) for 3D reconstruction. +We use [Pix4D](https://www.pix4d.com/) for 3D reconstruction. ![GeoTag](../../assets/camera/geotag.jpg) diff --git a/docs/ko/companion_computer/holybro_pixhawk_jetson_baseboard.md b/docs/ko/companion_computer/holybro_pixhawk_jetson_baseboard.md index 235e6930b5..a0d29a92bc 100644 --- a/docs/ko/companion_computer/holybro_pixhawk_jetson_baseboard.md +++ b/docs/ko/companion_computer/holybro_pixhawk_jetson_baseboard.md @@ -20,7 +20,7 @@ This guide walks through the process of setting up the board and connecting to P You will temporarily need the following hardware in order to log into your Jetson and get its IP address, after which you will be able to log in via SSH: - External display. - If your display doesn't have a mini HDMI connector you will also need a [Mini HDMI to HDMI converter](https://a.co/d/6N815N9) if your external display has HDMI input + If your display doesn't have a mini HDMI connector you will also need a [Mini HDMI to HDMI converter](https://www.amazon.com/dp/B014I8UEGY/) if your external display has HDMI input - Ethernet cable - Mouse and keyboard (the baseboard has 4 USB ports exposed from Jetson, two of which are USB 3.0) diff --git a/docs/ko/complete_vehicles_mc/crazyflie2.md b/docs/ko/complete_vehicles_mc/crazyflie2.md index def33dec25..316599c78d 100644 --- a/docs/ko/complete_vehicles_mc/crazyflie2.md +++ b/docs/ko/complete_vehicles_mc/crazyflie2.md @@ -36,7 +36,7 @@ The main hardware documentation is here: https://wiki.bitcraze.io/projects:crazy ## 구매처 - [Crazyflie 2.0](https://store.bitcraze.io/collections/kits/products/crazyflie-2-0). -- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/collections/kits/products/crazyradio-pa): used for wireless communication between _QGroundControl_ and Crazyflie 2.0. +- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/products/crazyradio-pa): used for wireless communication between _QGroundControl_ and Crazyflie 2.0. - [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): breakout expansion board for connecting new peripherals. - [Flow deck](https://store.bitcraze.io/collections/decks/products/flow-deck): contains an optical flow sensor to measure movements of the ground and a distance sensor to measure the distance to the ground. This will be useful for precise altitude and position control. @@ -203,7 +203,7 @@ python cfbridge.py :::info _Cfbridge_ by default tries to initiate the radio link communication on channel 80 and with crazyflie address 0xE7E7E7E7E7. -If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/index.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl. +If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/README.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl. Next, launch the cfbridge by giving the same channel and address as the first and second arguments respectively, e.g: `python cfbridge.py 90 0x0202020202` ::: diff --git a/docs/ko/complete_vehicles_mc/crazyflie21.md b/docs/ko/complete_vehicles_mc/crazyflie21.md index 63e9fcfd08..a33794df2a 100644 --- a/docs/ko/complete_vehicles_mc/crazyflie21.md +++ b/docs/ko/complete_vehicles_mc/crazyflie21.md @@ -40,7 +40,7 @@ The vehicle can be purchased here: [Crazyflie 2.1](https://store.bitcraze.io/pro Useful peripheral hardware includes: -- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/collections/kits/products/crazyradio-pa): Wireless communication between _QGroundControl_ and Crazyflie 2.0 +- [Crazyradio PA 2.4 GHz USB dongle](https://store.bitcraze.io/products/crazyradio-pa): Wireless communication between _QGroundControl_ and Crazyflie 2.0 - [Breakout deck](https://store.bitcraze.io/collections/decks/products/breakout-deck): Breakout expansion board for connecting new peripherals. - [Flow deck v2](https://store.bitcraze.io/collections/decks/products/flow-deck-v2): Optical flow sensor and a distance sensor for altitude and position control. - [Z-ranger deck v2](https://store.bitcraze.io/collections/decks/products/z-ranger-deck-v2): Distance sensor for altitude control (same sensor as the Flow deck). @@ -220,7 +220,7 @@ To connect Crazyflie 2.1 with crazyradio, **launch cfbridge** by following these ::: info _Cfbridge_ by default tries to initiate the radio link communication on channel 80 and with crazyflie address 0xE7E7E7E7E7. - If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/index.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl. + If you are using [multiple crazyflies and/or crazyradios](https://github.com/dennisss/cfbridge/blob/master/README.md#advanced-swarming) in the same room and want to use a different channel and/or address for each, first connect the crazyflie with QGroundControl via a USB cable and change the syslink parameters (channel, address) in QGroundControl. Next, launch the cfbridge by giving the same channel and address as the first and second arguments respectively, e.g: `python cfbridge.py 90 0x0202020202` ::: diff --git a/docs/ko/complete_vehicles_mc/index.md b/docs/ko/complete_vehicles_mc/index.md index ae94b4d1fc..bbc749fad2 100644 --- a/docs/ko/complete_vehicles_mc/index.md +++ b/docs/ko/complete_vehicles_mc/index.md @@ -12,19 +12,16 @@ You can find others on [px4.io](https://px4.io/ecosystem/commercial-systems/) an This section lists drone kits that are intended as platforms for further development. They may come either fully assembled or in parts. -- [ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md) - SLAM development drone supercharged by VOXL 2 and PX4. - [PX4 Vision DevKit](../complete_vehicles_mc/px4_vision_kit.md) - Multicopter used for PX4 computer vision development +- ~[ModalAI VOXL 2 Starling PX4 Development Drone](../complete_vehicles_mc/modalai_starling.md)~ (Discontinued/superseded) - SLAM development drone supercharged by VOXL 2 and PX4. ## PX4 Preinstalled This section lists vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed. -- [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 @@ -32,7 +29,6 @@ This section lists vehicles where you can update the software to run PX4. - [Holybro Kopis 2](../complete_vehicles_mc/holybro_kopis2.md) - [Bitcraze Crazyflie 2.1](../complete_vehicles_mc/crazyflie21.md) -- [BetaFPV Beta75X 2S Brushless Whoop](../complete_vehicles_mc/betafpv_beta75x.md) (discontinued) ## Custom PX4 @@ -40,8 +36,8 @@ This section contains consumer vehicles that run a _custom_ version of PX4 (supp 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/) +- [Yuneec Mantis Q](https://px4.io/project/yuneec-mantis-q/) +- [Yuneec H520](https://px4.io/project/yuneec-h520-hexacopter/) - [AeroSense Aerobo (AS-MC02-P)](https://px4.io/project/aerosense-aerobo/) ## See Also diff --git a/docs/ko/complete_vehicles_mc/px4_vision_kit.md b/docs/ko/complete_vehicles_mc/px4_vision_kit.md index f78cc3aeda..3322995f53 100644 --- a/docs/ko/complete_vehicles_mc/px4_vision_kit.md +++ b/docs/ko/complete_vehicles_mc/px4_vision_kit.md @@ -403,7 +403,7 @@ The carrier board pinouts and other information are in the [downloads section](h ## Other Development Resources - [_UP Core_ Wiki](https://github.com/up-board/up-community/wiki/Ubuntu) - _Up Core_ companion computer technical information -- [Occipital Developer Forum](https://structure.io/developers) - _Structure Core_ camera information +- [Occipital Developer Forum](https://structure.io/developers/) - _Structure Core_ camera information - [Pixhawk 4 Overview](../flight_controller/pixhawk4.md) - [Pixhawk 6C Overview](../flight_controller/pixhawk6c.md) diff --git a/docs/ko/complete_vehicles_rover/aion_r1.md b/docs/ko/complete_vehicles_rover/aion_r1.md index b4ec7f763f..c13130734a 100644 --- a/docs/ko/complete_vehicles_rover/aion_r1.md +++ b/docs/ko/complete_vehicles_rover/aion_r1.md @@ -4,7 +4,7 @@ The [Aion R1](https://www.aionrobotics.com/) vehicle was chosen to test and improve the differential drive support for PX4, and to improve driver support for Roboclaw Motor Controllers, such as the [RoboClaw 2x15A](https://www.basicmicro.com/RoboClaw-2x15A-Motor-Controller_p_10.html). -The documentation and driver information here should also make it easier to work with Roboclaw controllers on other vehicles, and to work with vehicles like the [Aion R6](https://www.aionrobotics.com/r6). +The documentation and driver information here should also make it easier to work with Roboclaw controllers on other vehicle. Currently, PX4 supports MANUAL mode for this setup. @@ -12,8 +12,7 @@ Currently, PX4 supports MANUAL mode for this setup. ## 부품 목록 -- [Aion R1 (Discontinued)](https://www.aionrobotics.com/) - - [Documentation](https://github-docs.readthedocs.io/en/latest/r1-ugv.html) +- Aion R1 (Discontinued) - [RoboClaw 2x15A](https://www.basicmicro.com/RoboClaw-2x15A-Motor-Controller_p_10.html) - [R1 Roboclaw specifications](https://resources.basicmicro.com/aion-robotics-r1-autonomous-robot/) - [Auterion Skynode](../companion_computer/auterion_skynode.md) @@ -50,7 +49,6 @@ Use _QGroundControl_ for rover configuration: First configure the serial connection: 1. Navigate to the [Parameters](../advanced_config/parameters.md) section in QGroundControl. - - Set the [RBCLW_SER_CFG](../advanced_config/parameter_reference.md#RBCLW_SER_CFG) parameter to the serial port to which the RoboClaw is connected (such as `GPS2`). - [RBCLW_COUNTS_REV](../advanced_config/parameter_reference.md#RBCLW_COUNTS_REV) specifies the number of encoder counts required for one wheel revolution. This value should be left at `1200` for the tested `RoboClaw 2x15A Motor Controller`. diff --git a/docs/ko/complete_vehicles_vtol/index.md b/docs/ko/complete_vehicles_vtol/index.md index 1dae34c9b5..78dbbcc513 100644 --- a/docs/ko/complete_vehicles_vtol/index.md +++ b/docs/ko/complete_vehicles_vtol/index.md @@ -18,7 +18,7 @@ They may come either fully assembled or in parts. This section lists VTOL vehicles that are sold fully assembled and ready to fly (RTF), with PX4 installed. -- [Vertical Technologies DeltaQuad](https://px4.io/portfolio/deltaquad-vtol/) +- [Vertical Technologies DeltaQuad](https://px4.io/project/deltaquad-vtol/) @@ -27,8 +27,8 @@ This section lists VTOL vehicles that are sold fully assembled and ready to fly 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. -- [WingtraOne Tailsitter VTOL](https://px4.io/portfolio/wingtraone-tailsitter-vtol/) -- [Flightwave Edge](https://px4.io/portfolio/flywave-edge/) +- [WingtraOne Tailsitter VTOL](https://px4.io/project/wingtraone-tailsitter-vtol/) +- [Flightwave Edge](https://px4.io/project/flywave-edge/) ## See Also diff --git a/docs/ko/concept/control_allocation.md b/docs/ko/concept/control_allocation.md index c8333ec530..d6374c3143 100644 --- a/docs/ko/concept/control_allocation.md +++ b/docs/ko/concept/control_allocation.md @@ -42,11 +42,11 @@ 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/tree/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 `_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`. - - output functions are defined under [src/lib/mixer_module/output_functions.yaml](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module/output_functions.yaml). + - output functions are defined under [src/lib/mixer_module/output_functions.yaml](https://github.com/PX4/PX4-Autopilot/tree/main/src/lib/mixer_module/output_functions.yaml). - if you want to control an output from MAVLink, set the relevant output function to **Offboard Actuator Set x**, and then send the [MAV_CMD_DO_SET_ACTUATOR](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_ACTUATOR) MAVLink command. ## Adding a new Geometry or Output Function diff --git a/docs/ko/concept/px4_systems_architecture.md b/docs/ko/concept/px4_systems_architecture.md index 7897a99c36..9f3a9b0a4d 100644 --- a/docs/ko/concept/px4_systems_architecture.md +++ b/docs/ko/concept/px4_systems_architecture.md @@ -3,28 +3,28 @@ 아래 섹션에서는 "일반적인" PX4 시스템의 하드웨어와 소프트웨어 개요를 제공합니다. 하나는 비행 콘트롤러만 있는 것이고 다른 하나는 비행 컨트롤러와 보조 컴퓨터("미션 컴퓨터"라고도 함)가 있습니다. :::info -The [PX4 Architectural Overview](../concept/architecture.md) provides information about the flight stack and middleware. -Offboard APIs are covered in [ROS](../ros/index.md) and [MAVSDK](https://mavsdk.mavlink.io/main/en/). +PX4 아키텍처 개요(../concept/architecture.md)는 비행 스택과 미들웨어에 대한 정보를 제공합니다. +오프보드 API는 ROS(../ros/index.md)와 MAVSDK(https://mavsdk.mavlink.io/main/en/)에서 다루어집니다. ::: ## 비행 콘트롤러 아래 다이어그램은 비행 콘트롤러 기반 PX4 시스템 개요입니다. -![PX4 architecture - FC only system](../../assets/diagrams/px4_arch_fc.svg) +![PX4 구조: 비행 컨트롤러 단독 운용 시스템](../../assets/diagrams/px4_arch_fc.svg) 하드웨어 구성 -- [Flight controller](../flight_controller/index.md) (running the PX4 flight stack). 콘트롤러에는 대부분 내부 IMU, 나침반 및 기압계가 포함되어 있습니다. +- (PX4 비행 제어 소프트웨어를 실행하는) [비행 컨트롤러](../flight_controller/index.md). 콘트롤러에는 대부분 내부 IMU, 나침반 및 기압계가 포함되어 있습니다. - [Motor ESCs](../peripherals/esc_motors.md) connected to [PWM outputs](../peripherals/pwm_escs_and_servo.md), [DroneCAN](../dronecan/escs.md) (DroneCAN allows two-way communication, not single direction as shown) or some other bus. - Sensors ([GPS](../gps_compass/index.md), [compass](../gps_compass/index.md), distance sensors, barometers, optical flow, barometers, ADSB transponders, etc.) connected via I2C, SPI, CAN, UART etc. - [Camera](../camera/index.md) or other payload. 카메라는 PWM 출력에 연결하거나 MAVLink로 연결할 수 있습니다. - [Telemetry radios](../telemetry/index.md) for connecting to a ground station computer/software. - [RC Control System](../getting_started/rc_transmitter_receiver.md) for manual control -The left hand side of the diagram shows the software stack, which is horizontally aligned (approximately) with the hardware parts of the diagram. +도표의 왼쪽은 소프트웨어 스택을 보여주며, 이는 도표의 하드웨어 구성 요소들과 (대략적으로) 수평으로 정렬되어 있습니다. - The ground station computer typically runs [QGroundControl](../getting_started/px4_basic_concepts.md#qgc) (or some other ground station software). It may also run robotics software like [MAVSDK](https://mavsdk.mavlink.io/) or [ROS](../ros/index.md). @@ -42,11 +42,11 @@ The flight controller runs the normal PX4 flight stack, while a companion comput The two systems are connected using a fast serial or IP link, and typically communicate using the [MAVLink protocol](https://mavlink.io/en/). Communications with the ground stations and the cloud are usually routed via the companion computer (e.g. using the [MAVLink Router](https://github.com/mavlink-router/mavlink-router) (from Intel)). -PX4 systems typically run a Linux OS on the companion computer. +PX4 기반 시스템에서는 보조 컴퓨터에 리눅스 운영체제를 쓰는 경우가 많습니다. Linux는 NuttX보다 "일반" 소프트웨어 개발을 위한 플랫폼입니다. 많은 Linux 개발자와 유용한 소프트웨어가 이미 개발되어 있습니다(예: 컴퓨터 비전, 통신, 클라우드 통합, 하드웨어 드라이버용). 보조 컴퓨터는 때때로 같은 이유로 Android를 사용합니다. :::info -The diagram shows a cloud or ground station connection via LTE, an approach that has been used a number of PX4-based systems. +이 다이어그램은 LTE를 통해 클라우드 또는 지상국과 연결하는 방식을 보여주며, 이 방식은 여러 PX4 기반 시스템에서 사용되어 왔습니다. PX4는 특별히 LTE와 클라우드 통합을 위한 소프트웨어를 제공하지 않습니다(사용자 맞춤형 개발이 필요함). ::: diff --git a/docs/ko/config/actuators.md b/docs/ko/config/actuators.md index 635fe44738..ef3550d0ae 100644 --- a/docs/ko/config/actuators.md +++ b/docs/ko/config/actuators.md @@ -379,7 +379,7 @@ The following functions can only be applied to FMU outputs: Enabled when [`PPS_CAP_ENABLE==0`](../advanced_config/parameter_reference.md#PPS_CAP_ENABLE) :::info -The functions are defined in source at [/src/lib/mixer_module/output_functions.yaml](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module/output_functions.yaml). +The functions are defined in source at [/src/lib/mixer_module/output_functions.yaml](https://github.com/PX4/PX4-Autopilot/tree/main/src/lib/mixer_module/output_functions.yaml). This list is correct at PX4 v1.15. ::: @@ -507,7 +507,6 @@ For each motor: 2. Slowly move the slider up until it snaps to the _minimum_ position. In this position the motor is set to the outputs `minimum` value. - - 이 위치에서 모터가 매우 느리게 회전하는 지 확인합니다. - If the motor is not spinning, or spinning too fast you will need to adjust the corresponding PWM `minimum` value in the [Actuator Outputs](#actuator-outputs) such that the motors barely spin. @@ -518,7 +517,6 @@ For each motor: ::: 3. Increase the slider value to a level where you can verify that the motor is spinning in the correct direction and that it would give a positive thrust in the expected direction. - - The expected thrust direction can vary by vehicle type. For example in multicopters the thrust should always point upwards, while in a fixed-wing vehicle the thrust will push the vehicle forwards. - For VTOL, thrust should point upwards when the Tilt Servo is at 0 degrees as defined the [Tilt Servo Convention](#tilt-servo-coordinate-system). @@ -568,7 +566,6 @@ To set these up: If the control surface moves in the opposite direction, click on the `Rev Range` checkbox to reverse the range. 3. Move the slider again to the middle and check if the Control Surfaces are aligned in the neutral position of the wing. - - If it is not aligned, you can set the **Trim** value for the control surface. ::: info diff --git a/docs/ko/config/index.md b/docs/ko/config/index.md index d3a05360c2..85c913994f 100644 --- a/docs/ko/config/index.md +++ b/docs/ko/config/index.md @@ -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](https://qgroundcontrol.com/downloads/) and install it on your **desktop** computer. +Before starting you should [Download QGroundControl](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) 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: ![QGC Main Menu Popup: highlighting Vehicle Setup](../../assets/qgc/setup/menu_setup.png) diff --git a/docs/ko/config/joystick.md b/docs/ko/config/joystick.md index 37df0dd6d8..3ac6d2699f 100644 --- a/docs/ko/config/joystick.md +++ b/docs/ko/config/joystick.md @@ -2,7 +2,7 @@ A [computer joystick](https://en.wikipedia.org/wiki/Joystick) or gamepad connected through _QGroundControl_ can be used to manually control the vehicle (_instead_ of using an [RC Transmitter](../config/radio.md)). -This approach may be used by manual control units that have an integrated ground control station (like the _UAVComponents_ [MicroNav](https://uxvtechnologies.com/ground-control-stations/micronav/) shown below). +This approach may be used by manual control units that have an integrated ground control station (like the _UAVComponents_ [MicroNav](https://www.uxvtechnologies.com/ground-control-stations/micronav) shown below). 조이스틱은 일반적으로 비행 시뮬레이션용으로 많이 사용합니다. ![Joystick MicroNav](../../assets/peripherals/joystick/micronav.jpg) diff --git a/docs/ko/config/safety.md b/docs/ko/config/safety.md index facf431d8d..3323b03aaa 100644 --- a/docs/ko/config/safety.md +++ b/docs/ko/config/safety.md @@ -319,8 +319,8 @@ The [failure detector](#failure-detector), if [enabled](#CBRK_FLIGHTTERM), can a 외부 작동 시스템은 비행 컨트롤러 포트 AUX5 (또는 AUX 포트가없는 보드의 MAIN5)에 연결되어야 하며 아래의 매개 변수들을 사용하여 설정합니다. :::info -External ATS is required by [ASTM F3322-18](https://webstore.ansi.org/Standards/ASTM/ASTMF332218). -One example of an ATS device is the [FruityChutes Sentinel Automatic Trigger System](https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/sentinel-automatic-trigger-system.htm). +External ATS is required by [ASTM F3322-18](https://webstore.ansi.org/standards/astm/ASTMF332218). +One example of an ATS device is the [FruityChutes Sentinel Automatic Trigger System (SATS-MINI)](https://fruitychutes.com/uav_rpv_drone_recovery_parachutes/sentinel-automatic-trigger-system). ::: | 매개변수 | 설명 | diff --git a/docs/ko/config_vtol/vtol_quad_configuration.md b/docs/ko/config_vtol/vtol_quad_configuration.md index d7de0dec16..7c234d9653 100644 --- a/docs/ko/config_vtol/vtol_quad_configuration.md +++ b/docs/ko/config_vtol/vtol_quad_configuration.md @@ -155,7 +155,3 @@ When transitioning from **multirotor to fixed-wing** (transition switch is on/fi When transitioning from **fixed-wing to multirotor** for this type of VTOL the switch is immediate so there isn’t really a backing out option here, unlike for tilt rotor VTOLs. If you want it to go back into fixed-wing you will need to go through the full transition. If it’s still travelling fast this should happen quickly. - -### 지원 - -If you have any questions regarding your VTOL conversion or configuration please see [discuss.px4.io/c/px4/vtol](https://discuss.px4.io/c/px4/vtol). diff --git a/docs/ko/contribute/code.md b/docs/ko/contribute/code.md index b63b4479ae..8673e2516f 100644 --- a/docs/ko/contribute/code.md +++ b/docs/ko/contribute/code.md @@ -8,10 +8,10 @@ PX4 프로젝트는 3가지 Git 분기 모델을 사용합니다. - [beta](https://github.com/PX4/PX4-Autopilot/tree/beta) has been thoroughly tested. 비행 테스터를 위한 것입니다. - [stable](https://github.com/PX4/PX4-Autopilot/tree/stable) points to the last release. -We try to retain a [linear history through rebases](https://www.atlassian.com/git/tutorials/rewriting-history) and avoid the [Github flow](https://docs.github.com/en/get-started/quickstart/github-flow). +We try to retain a [linear history through rebases](https://www.atlassian.com/git/tutorials/rewriting-history) and avoid the [Github flow](https://docs.github.com/en/get-started/using-github/github-flow). 그러나, 전세계의 역동적인 개발팀과 수시로 병합 작업을 진행합니다. -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). +To contribute new functionality, [sign up for Github](https://docs.github.com/en/get-started/using-github/github-flow), then [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/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/license/BSD-3-Clause) and all code must not impose any further constraints on the use. diff --git a/docs/ko/contribute/docs.md b/docs/ko/contribute/docs.md index bae9c4beed..b8d7bc1dbe 100644 --- a/docs/ko/contribute/docs.md +++ b/docs/ko/contribute/docs.md @@ -60,7 +60,7 @@ If you already have a clone of the [PX4-Autopilot](https://github.com/PX4/PX4-Au 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)). +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/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)). 4. 복사된 저장소를 로컬 컴퓨터에 복제합니다. diff --git a/docs/ko/contribute/git_examples.md b/docs/ko/contribute/git_examples.md index 34ece0585b..d4e71a7deb 100644 --- a/docs/ko/contribute/git_examples.md +++ b/docs/ko/contribute/git_examples.md @@ -8,7 +8,7 @@ PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4 - [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)) +- Fork the PX4-Autopilot repo (see [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)) - 포크된 저장소를 로컬 컴퓨터에 복제합니다. diff --git a/docs/ko/contribute/maintainers.md b/docs/ko/contribute/maintainers.md index 5a134bd143..774b655aed 100644 --- a/docs/ko/contribute/maintainers.md +++ b/docs/ko/contribute/maintainers.md @@ -1,7 +1,7 @@ # Maintainer Role Dronecode maintainers have technical leadership and responsibility for specific areas of PX4, and for other ecosystem components such as MAVLink, MAVSDK, QGroundControl, and others. -The maintainer role is defined by the community with help and supervision from the [Dronecode Foundation](https://www.dronecode.org/). +The maintainer role is defined by the community with help and supervision from the [Dronecode Foundation](https://dronecode.org/). To find the most up-to-date maintainers list, visit [PX4-Autopilot README](https://github.com/PX4/PX4-Autopilot#maintenance-team). @@ -22,7 +22,7 @@ Once accepted every maintainers will go through the following process: 1. **Discord** server admin will grant you the `dev team` role, which gives you: 1. Basic admin privileges on discord. 2. Access to the `#maintainers` channel. -2. You will be given access to the GitHub team: "[`Dev Team`](https://github.com/orgs/PX4/teams/dev-team)" which grants you: +2. You will be given access to the GitHub team: "[`Dev Team`](https://github.com/orgs/PX4/teams/dev-team)" which grants you: 1. Permission to merge the PR of any of PX4 workspace repositories after it's approved 2. Permission to trigger GitHub actions when a new contributor opens a PR. 3. Permission to edit Issue/PR contents. diff --git a/docs/ko/contribute/support.md b/docs/ko/contribute/support.md index 8ff5265ef5..ae7d5b0203 100644 --- a/docs/ko/contribute/support.md +++ b/docs/ko/contribute/support.md @@ -29,7 +29,7 @@ The Discuss Forum is much preferred because it is indexed by search engines and 문제의 원인이 무엇인지 확실하지 않고 문제 분석의 도움을 원하시면, - Upload logs to [Flight Log Review](https://logs.px4.io/) -- Open a discussion on [PX4 Discuss](https://discuss.px4.io/c/flight-testing/) with a flight report and links to logs. +- Open a discussion on [PX4 Discuss](https://discuss.px4.io/c/flight-testing/10) with a flight report and links to logs. - The dev team may prompt you to [raise an issue](#issue-bug-reporting) if the problem is caused by a bug. ## Issue & Bug Reporting diff --git a/docs/ko/debug/binary_size_profiling.md b/docs/ko/debug/binary_size_profiling.md index 0731376222..297a53ca7e 100644 --- a/docs/ko/debug/binary_size_profiling.md +++ b/docs/ko/debug/binary_size_profiling.md @@ -8,7 +8,7 @@ This can help analyse changes that (may) cause `px4_fmu-v2_default` to hit the 1 ::: _Bloaty_ must be in your path and found at _cmake_ configure time. -The PX4 [docker files](https://github.com/PX4/containers/blob/master/docker/Dockerfile_nuttx-bionic) install _bloaty_ as shown: +The PX4 [docker files](https://github.com/PX4/PX4-containers/blob/master/docker/Dockerfile_nuttx-bionic) install _bloaty_ as shown: ```sh git clone --recursive https://github.com/google/bloaty.git /tmp/bloaty \ diff --git a/docs/ko/debug/eclipse_jlink.md b/docs/ko/debug/eclipse_jlink.md index 71fde0d8a2..34ea6212f4 100644 --- a/docs/ko/debug/eclipse_jlink.md +++ b/docs/ko/debug/eclipse_jlink.md @@ -21,7 +21,7 @@ This topic explains how to setup and use [MCU Eclipse](https://gnu-mcu-eclipse.g To install _Eclipse_: -1. Download [Eclipse CDT for C/C++ Developers](https://github.com/gnu-mcu-eclipse/org.eclipse.epp.packages/releases/) (MCU GitHub). +1. Download [Eclipse CDT for C/C++ Developers](https://github.com/eclipse-embed-cdt/org.eclipse.epp.packages/releases) (MCU GitHub). 2. Eclipse 폴더의 압축을 풀고 적당한 폴더에 복사합니다(설치 스크립트를 실행할 필요가 없음). 3. Run _Eclipse_ and choose a location for your initial workbench. diff --git a/docs/ko/debug/probe_bmp.md b/docs/ko/debug/probe_bmp.md index 88273c89ac..4afc881f9f 100644 --- a/docs/ko/debug/probe_bmp.md +++ b/docs/ko/debug/probe_bmp.md @@ -21,7 +21,7 @@ The _6-pos DF13_ connector that comes with the probe cannot be used for SWD debu :::info To debug STM32F7 or later (FMUv5 and newer) the Zubax BugFace BF1 / Blackmagic probe likely requires a firmware update. -You can find how to update the [blackmagic probe here](https://github.com/blacksphere/blackmagic/wiki/Upgrading-Firmware). +You can find how to update the [blackmagic probe here](https://black-magic.org/upgrade.html). ::: To use a Zubax BugFace BF1 with GDB, start GDB with the exact ELF file that is currently flashed on the autopilot: diff --git a/docs/ko/debug/probe_jlink.md b/docs/ko/debug/probe_jlink.md index 741c16a16b..cc39721bba 100644 --- a/docs/ko/debug/probe_jlink.md +++ b/docs/ko/debug/probe_jlink.md @@ -47,7 +47,7 @@ See the [Embedded Debug Tools][emdbg] for more advanced debug options. ### Segger JLink EDU Mini Debug Probe The [Segger JLink EDU Mini](https://www.segger.com/products/debug-probes/j-link/models/j-link-edu-mini/) is an inexpensive and popular SWD debug probe. -The probe's connector pinout looks like the image below (connect to this using an ARM 10-pin mini connector like [FTSH-105-01-F-DV-K](https://www.digikey.com/products/en?keywords=SAM8796-ND)). +The probe's connector pinout looks like the image below (connect to this using an ARM 10-pin mini connector like [FTSH-105-01-F-DV-K](https://www.digikey.com/en/products/detail/samtec-inc/FTSH-105-01-F-DV-K/2649974)). ![connector_jlink_mini.png](../../assets/debug/connector_jlink_mini.png) diff --git a/docs/ko/debug/swd_debug.md b/docs/ko/debug/swd_debug.md index 8904553159..b8813cf961 100644 --- a/docs/ko/debug/swd_debug.md +++ b/docs/ko/debug/swd_debug.md @@ -217,5 +217,5 @@ This reduces the risk or poor wiring contributing to debugging problems, and has [swd]: https://developer.arm.com/documentation/ihi0031/a/The-Serial-Wire-Debug-Port--SW-DP- [itm]: https://developer.arm.com/documentation/ddi0403/d/Appendices/Debug-ITM-and-DWT-Packet-Protocol?lang=en [etm]: https://developer.arm.com/documentation/ihi0064/latest/ -[bm06b-ghs-tbt(lf)(sn)(n)]: https://www.digikey.com/products/en?keywords=455-1582-1-ND -[sm06b-ghs-tbt(lf)(sn)(n)]: https://www.digikey.com/products/en?keywords=455-1568-1-ND +[bm06b-ghs-tbt(lf)(sn)(n)]: https://www.digikey.com/en/products/detail/jst-sales-america-inc/BM06B-GHS-TBT/807804 +[sm06b-ghs-tbt(lf)(sn)(n)]: https://www.digikey.com/en/products/detail/jst-sales-america-inc/SM06B-GHS-TB/807790 diff --git a/docs/ko/dev_log/log_encryption.md b/docs/ko/dev_log/log_encryption.md index 5fdb48e126..4af14b648e 100644 --- a/docs/ko/dev_log/log_encryption.md +++ b/docs/ko/dev_log/log_encryption.md @@ -191,7 +191,7 @@ You can now build and test. ## Download & Decrypt Log Files Before you can analyse your logs they must first be downloaded and decrypted. -PX4 includes Python scripts in [Tools/log_encryption](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/) that make this process easier: +PX4 includes Python scripts in [Tools/log_encryption](https://github.com/PX4/PX4-Autopilot/tree/main/Tools) that make this process easier: - [download_logs.py](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/log_encryption/download_logs.py): Downloads the logs to `/logs/encrypted`. - [decrypt_logs.py](https://github.com/PX4/PX4-Autopilot/blob/main/Tools/log_encryption/decrypt_logs.py): Decrypts encrypted logs in `/logs/encrypted` to `/logs/decrypted` using a specified (or default) key. diff --git a/docs/ko/dev_log/ulog_file_format.md b/docs/ko/dev_log/ulog_file_format.md index f104685724..2af8fc1e78 100644 --- a/docs/ko/dev_log/ulog_file_format.md +++ b/docs/ko/dev_log/ulog_file_format.md @@ -495,7 +495,7 @@ Since the Definitions and Data Sections use the same message header format, they - [FlightPlot](https://github.com/PX4/FlightPlot): Java, log plotter. - [MAVLink](https://github.com/mavlink/mavlink): Messages for ULog streaming via MAVLink (note that appending data is not supported, at least not for cut off messages). - [QGroundControl](https://github.com/mavlink/qgroundcontrol): C++, ULog streaming via MAVLink and minimal parsing for GeoTagging. -- [mavlink-router](https://github.com/01org/mavlink-router): C++, ULog streaming via MAVLink. +- [mavlink-router](https://github.com/mavlink-router/mavlink-router): C++, ULog streaming via MAVLink. - [MAVGAnalysis](https://github.com/ecmnet/MAVGCL): Java, ULog streaming via MAVLink and parser for plotting and analysis. - [PlotJuggler](https://github.com/facontidavide/PlotJuggler): C++/Qt application to plot logs and time series. 버전 2.1.3부터 ULog를 지원합니다. - [ulogreader](https://github.com/maxsun/ulogreader): Javascript, ULog reader and parser outputs log in JSON object format. diff --git a/docs/ko/dev_setup/dev_env_windows_cygwin.md b/docs/ko/dev_setup/dev_env_windows_cygwin.md index 6d6c4b80de..f8cf00f8df 100644 --- a/docs/ko/dev_setup/dev_env_windows_cygwin.md +++ b/docs/ko/dev_setup/dev_env_windows_cygwin.md @@ -20,7 +20,7 @@ PX4 빌드에 사용되어 집니다. ## 설치 방법 -1. Download the latest version of the ready-to-use MSI installer from: [Github releases](https://github.com/PX4/windows-toolchain/releases) or [Amazon S3](https://s3-us-west-2.amazonaws.com/px4-tools/PX4+Windows+Cygwin+Toolchain/PX4+Windows+Cygwin+Toolchain+0.9.msi) (fast download). +1. Download the latest version of the ready-to-use MSI installer from: [Github releases](https://github.com/PX4/PX4-windows-toolchain/releases) or [Amazon S3](https://s3-us-west-2.amazonaws.com/px4-tools/PX4+Windows+Cygwin+Toolchain/PX4+Windows+Cygwin+Toolchain+0.9.msi) (fast download). 2. Run it, choose your desired installation location, let it install: diff --git a/docs/ko/dev_setup/dev_env_windows_cygwin_packager_setup.md b/docs/ko/dev_setup/dev_env_windows_cygwin_packager_setup.md index a9dcb3fbaf..a0c4704546 100644 --- a/docs/ko/dev_setup/dev_env_windows_cygwin_packager_setup.md +++ b/docs/ko/dev_setup/dev_env_windows_cygwin_packager_setup.md @@ -91,16 +91,16 @@ The toolchain gets maintained and hence these instructions might not cover every ::: ::: info - That's what [cygwin64/install-cygwin-px4.bat](https://github.com/MaEtUgR/PX4Toolchain/blob/master/toolchain/cygwin64/install-cygwin-px4.bat) does. + That's what [cygwin64/install-cygwin-px4.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/cygwin64/install-cygwin-px4.bat) does. ::: -6. Write up or copy the **batch scripts** [`run-console.bat`](https://github.com/MaEtUgR/PX4Toolchain/blob/master/run-console.bat) and [`setup-environment.bat`](https://github.com/PX4/windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat). +6. Write up or copy the **batch scripts** [`run-console.bat`](https://github.com/MaEtUgR/PX4Toolchain/blob/master/run-console.bat) and [`setup-environment.bat`](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat). The reason to start all the development tools through the prepared batch script is they preconfigure the starting program to use the local, portable Cygwin environment inside the toolchain's folder. - This is done by always first calling the script [**setup-environment.bat**](https://github.com/PX4/windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat) and the desired application like the console after that. + This is done by always first calling the script [**setup-environment.bat**](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat) and the desired application like the console after that. - The script [setup-environment.bat](https://github.com/PX4/windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat) locally sets environmental variables for the workspace root directory `PX4_DIR`, all binary locations `PATH`, and the home directory of the unix environment `HOME`. + The script [setup-environment.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat) locally sets environmental variables for the workspace root directory `PX4_DIR`, all binary locations `PATH`, and the home directory of the unix environment `HOME`. 7. Add necessary **python packages** to your setup by opening the Cygwin toolchain console (double clicking **run-console.bat**) and executing @@ -118,19 +118,19 @@ The toolchain gets maintained and hence these instructions might not cover every 8. Download the [**ARM GCC compiler**](https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads) as zip archive of the binaries for Windows and unpack the content to the folder `C:\PX4\toolchain\gcc-arm`. ::: info - This is what the toolchain does in: [gcc-arm/install-gcc-arm.bat](https://github.com/MaEtUgR/PX4Toolchain/blob/master/toolchain/gcc-arm/install-gcc-arm.bat). + This is what the toolchain does in: [gcc-arm/install-gcc-arm.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/gcc-arm/install-gcc-arm.bat). ::: 9. Install the JDK: - - Download Java 14 from [Oracle](https://www.oracle.com/java/technologies/javase-jdk14-downloads.html) or [AdoptOpenJDK](https://adoptopenjdk.net/). + - Download Java 14 from [Oracle](https://www.oracle.com/java/technologies/downloads/) or [AdoptOpenJDK](https://adoptopenjdk.net/). - Because sadly there is no portable archive containing the binaries directly you have to install it. - Find the binaries and move/copy them to **C:\PX4\toolchain\jdk**. - You can uninstall the Kit from your Windows system again, we only needed the binaries for the toolchain. ::: info - This is what the toolchain does in: [jdk/install-jdk.bat](https://github.com/MaEtUgR/PX4Toolchain/blob/master/toolchain/jdk/install-jdk.bat). + This is what the toolchain does in: [jdk/install-jdk.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/jdk/install-jdk.bat). ::: @@ -142,12 +142,11 @@ The toolchain gets maintained and hence these instructions might not cover every ::: ::: info - This is what the toolchain does in: [apache-ant/install-apache-ant.bat](https://github.com/MaEtUgR/PX4Toolchain/blob/master/toolchain/apache-ant/install-apache-ant.bat). + This is what the toolchain does in: [apache-ant/install-apache-ant.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/apache-ant/install-apache-ant.bat). ::: 11. Download, build and add _genromfs_ to the path: - - Clone the source code to the folder **C:\PX4\toolchain\genromfs\genromfs-src** with ```sh @@ -164,4 +163,4 @@ The toolchain gets maintained and hence these instructions might not cover every - Copy the resulting binary **genromfs.exe** one folder level out to: **C:\PX4\toolchain\genromfs** -12. Make sure all the binary folders of all the installed components are correctly listed in the `PATH` variable configured by [**setup-environment.bat**](https://github.com/PX4/windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat). +12. Make sure all the binary folders of all the installed components are correctly listed in the `PATH` variable configured by [**setup-environment.bat**](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat). diff --git a/docs/ko/dev_setup/dev_env_windows_vm.md b/docs/ko/dev_setup/dev_env_windows_vm.md index 4f419d5bf9..53106360c7 100644 --- a/docs/ko/dev_setup/dev_env_windows_vm.md +++ b/docs/ko/dev_setup/dev_env_windows_vm.md @@ -33,7 +33,7 @@ VMWare performance is acceptable for basic usage (building Firmware) but not for 2. 윈도우 시스템에 설치합니다. -3. Download the desired version of [Ubuntu Desktop ISO Image](https://www.ubuntu.com/download/desktop). +3. Download the desired version of [Ubuntu Desktop ISO Image](https://ubuntu.com/download/desktop). (see [Linux Instructions Page](../dev_setup/dev_env_linux.md) for recommended Ubuntu version). 4. Open _VMWare Player_. @@ -58,7 +58,6 @@ VMWare performance is acceptable for basic usage (building Firmware) but not for 10. Once the new VM is booted up make sure you install _VMWare tools drivers and tools extension_ inside your guest system. 이렇게 하면 다음과 같은 VM 사용의 성능과 유용성들이 향상됩니다. - - 크게 향상된 그래픽 성능 - Proper support for hardware device usage like USB port allocation (important for target upload), proper mouse wheel scrolling, sound support - 창 크기에 따른 게스트 디스플레이 해상도 조정 @@ -96,7 +95,6 @@ To allow this, you need to configure USB passthrough settings: 3. Enable USB controller in VM: **VirtualBox > Settings > USB** 4. Add USB filters for the bootloader in VM: **VirtualBox > Settings > USB > Add new USB filter**. - - Open the menu and plug in the USB cable connected to your autopilot. Select the `...Bootloader` device when it appears in the UI. diff --git a/docs/ko/dev_setup/dev_env_windows_wsl.md b/docs/ko/dev_setup/dev_env_windows_wsl.md index 0dc93f2a83..4a4afc0efd 100644 --- a/docs/ko/dev_setup/dev_env_windows_wsl.md +++ b/docs/ko/dev_setup/dev_env_windows_wsl.md @@ -1,6 +1,6 @@ # Windows Development Environment (WSL2-Based) -The following instructions explain how to set up a PX4 development environment on Windows 10 or 11, running on Ubuntu Linux within [WSL2](https://docs.microsoft.com/en-us/windows/wsl/about). +The following instructions explain how to set up a PX4 development environment on Windows 10 or 11, running on Ubuntu Linux within [WSL2](https://learn.microsoft.com/en-us/windows/wsl/about). PX4 빌드에 사용되어 집니다. @@ -16,7 +16,7 @@ The list above are those targets that are regularly tested. ## 개요 -The [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/about) ([WSL2](https://docs.microsoft.com/en-us/windows/wsl/compare-versions)) allows users to install and run the [Ubuntu Development Environment](../dev_setup/dev_env_linux_ubuntu.md) on Windows, _almost_ as though we were running it on a Linux computer. +The [Windows Subsystem for Linux](https://learn.microsoft.com/en-us/windows/wsl/about) ([WSL2](https://learn.microsoft.com/en-us/windows/wsl/compare-versions)) allows users to install and run the [Ubuntu Development Environment](../dev_setup/dev_env_linux_ubuntu.md) on Windows, _almost_ as though we were running it on a Linux computer. With this environment developers can: @@ -94,7 +94,6 @@ If you're using [Windows Terminal](https://learn.microsoft.com/en-us/windows/ter To open a WSL shell using a command prompt: 1. Open a command prompt: - - Press the Windows **Start** key. - Type `cmd` and press **Enter** to open the prompt. diff --git a/docs/ko/dronecan/development.md b/docs/ko/dronecan/development.md index 922d7c91da..93129d7a55 100644 --- a/docs/ko/dronecan/development.md +++ b/docs/ko/dronecan/development.md @@ -8,6 +8,6 @@ Additional documentation on how to use Babel/other SLCAN adapters, the DroneCAN ## Debugging with Zubax Babel -A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://zubax.com/products/babel) in combination with the [GUI tool](https://dronecan.github.io/GUI_Tool/Overview/). +A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://shop.zubax.com/products/zubax-babel) in combination with the [GUI tool](https://dronecan.github.io/GUI_Tool/Overview/). They can also be used independently from Pixhawk hardware in order to test a node or manually control DroneCAN enabled ESCs. diff --git a/docs/ko/dronecan/index.md b/docs/ko/dronecan/index.md index dce4d8e850..5b284bf78d 100644 --- a/docs/ko/dronecan/index.md +++ b/docs/ko/dronecan/index.md @@ -38,7 +38,7 @@ Supported hardware includes (this is not an exhaustive list): - Airspeed sensors - [Holybro High Precision DroneCAN Airspeed Sensor - DLVR](https://holybro.com/collections/sensors/products/high-precision-dronecan-airspeed-sensor-dlvr) - - [RaccoonLab airspeed sensor](https://docs.raccoonlab.co/guide/airspeed) + - [RaccoonLab airspeed sensor](https://docs.raccoonlab.co/guide/airspeed/) - [Thiemar airspeed sensor](https://github.com/thiemar/airspeed) - GNSS receivers for GNSS (GPS, GLONASS, BeiDou, and so on) @@ -140,8 +140,8 @@ Sensor parameters may not exist (be visible in QGC) until you have enabled the a For example, [SENS_FLOW_MINHGT](../advanced_config/parameter_reference.md#SENS_FLOW_MINHGT) does not exist until [UAVCAN_SUB_FLOW](../advanced_config/parameter_reference.md#UAVCAN_SUB_FLOW) is enabled. ::: -For example, to use a connected DroneCAN smart battery you would enable the [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT) parameter, which would subscribe PX4 to receive [BatteryInfo](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#batteryinfo) DroneCAN messages. -If using a peripheral that needs to know if PX4 is armed, you would need to set the [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) parameter so that PX4 starts publishing [ArmingStatus](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#armingstatus) messages. +For example, to use a connected DroneCAN smart battery you would enable the [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT) parameter, which would subscribe PX4 to receive [BatteryInfo](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#batteryinfo) DroneCAN messages. +If using a peripheral that needs to know if PX4 is armed, you would need to set the [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) parameter so that PX4 starts publishing [ArmingStatus](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#armingstatus) messages. The parameter names are prefixed with `UAVCAN_SUB_` and `UAVCAN_PUB_` to indicate whether they enable PX4 subscribing or publishing. The remainder of the name indicates the specific message/feature being set. @@ -165,7 +165,7 @@ The DroneCAN sensor parameters/subscriptions that you can enable are (in PX4 v1. - [UAVCAN_SUB_DPRES](../advanced_config/parameter_reference.md#UAVCAN_SUB_DPRES): Differential pressure - [UAVCAN_SUB_FLOW](../advanced_config/parameter_reference.md#UAVCAN_SUB_FLOW): Optical flow - [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS): GPS -- [UAVCAN_SUB_GPS_R](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS_R): Subscribes to GNSS relative message ([RelPosHeading](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#relposheading)). +- [UAVCAN_SUB_GPS_R](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS_R): Subscribes to GNSS relative message ([RelPosHeading](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#relposheading)). Only used for logging in PX4 v1.15. - [UAVCAN_SUB_HYGRO](../advanced_config/parameter_reference.md#UAVCAN_SUB_HYGRO): Hygrometer - [UAVCAN_SUB_ICE](../advanced_config/parameter_reference.md#UAVCAN_SUB_ICE): Internal combustion engine (ICE). @@ -201,15 +201,15 @@ Position of rover is established using RTCM messages from the RTK base module (t PX4 DroneCAN parameters: - [UAVCAN_PUB_RTCM](../advanced_config/parameter_reference.md#UAVCAN_PUB_RTCM): - - Makes PX4 publish RTCM messages ([RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream)) to the bus (which it gets from the RTK base module via QGC). + - Makes PX4 publish RTCM messages ([RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream)) to the bus (which it gets from the RTK base module via QGC). Rover module parameters (also [set using QGC](#qgc-cannode-parameter-configuration)): -- [CANNODE_SUB_RTCM](../advanced_config/parameter_reference.md#CANNODE_SUB_RTCM) tells the rover that it should subscribe to [RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream) RTCM messages on the bus (from the moving base). +- [CANNODE_SUB_RTCM](../advanced_config/parameter_reference.md#CANNODE_SUB_RTCM) tells the rover that it should subscribe to [RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream) RTCM messages on the bus (from the moving base). :::info You could instead use [UAVCAN_PUB_MBD](../advanced_config/parameter_reference.md#UAVCAN_PUB_MBD) and [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD), which also publish RTCM messages (these are newer). -Using the [RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream) message means that you can implement moving base (see below) at the same time. +Using the [RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream) message means that you can implement moving base (see below) at the same time. ::: ##### Rover and Moving Base @@ -219,8 +219,8 @@ In this setup the vehicle has a _moving base_ RTK GPS and a _rover_ RTK GPS. These parameters can be [set on moving base and rover RTK CAN nodes](#qgc-cannode-parameter-configuration), respectively: -- [CANNODE_PUB_MBD](../advanced_config/parameter_reference.md#CANNODE_PUB_MBD) causes a moving base GPS unit to publish [MovingBaselineData](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#movingbaselinedata)RTCM messages onto the bus (for the rover) -- [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD) tells the rover that it should subscribe to [MovingBaselineData](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#movingbaselinedata) RTCM messages on the bus (from the moving base). +- [CANNODE_PUB_MBD](../advanced_config/parameter_reference.md#CANNODE_PUB_MBD) causes a moving base GPS unit to publish [MovingBaselineData](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#movingbaselinedata)RTCM messages onto the bus (for the rover) +- [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD) tells the rover that it should subscribe to [MovingBaselineData](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#movingbaselinedata) RTCM messages on the bus (from the moving base). For PX4 you will also need to set [GPS_YAW_OFFSET](../advanced_config/parameter_reference.md#GPS_YAW_OFFSET) to indicate the relative position of the moving base and rover: 0 if your Rover is in front of your Moving Base, 90 if Rover is right of Moving Base, 180 if Rover is behind Moving Base, or 270 if Rover is left of Moving Base. @@ -270,7 +270,7 @@ If the rangefinder is connected via DroneCAN (whether inbuilt or separate), you PX4 DroneCAN parameters: -- [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) ([Arming Status](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#armingstatus)): Publish when using DroneCAN components that require the PX4 arming status as a precondition for use. +- [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) ([Arming Status](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#armingstatus)): Publish when using DroneCAN components that require the PX4 arming status as a precondition for use. ### ESC & Servos @@ -324,6 +324,6 @@ If successful, the firmware binary will be removed from the root directory and t ## Useful Links - [Home Page](https://dronecan.github.io) (dronecan.github.io) -- [Protocol Specification](https://dronecan.github.io/Specification) (dronecan.github.io) +- [Protocol Specification](https://dronecan.github.io/Specification/1._Introduction/) (dronecan.github.io) - [Implementations](https://dronecan.github.io/Implementations/) (dronecan.github.io) - [Cyphal/CAN Device Interconnection](https://wiki.zubax.com/public/cyphal/CyphalCAN-device-interconnection?pageId=2195476) (kb.zubax.com) diff --git a/docs/ko/dronecan/raccoonlab_power.md b/docs/ko/dronecan/raccoonlab_power.md index de76e85751..89bbc203cb 100644 --- a/docs/ko/dronecan/raccoonlab_power.md +++ b/docs/ko/dronecan/raccoonlab_power.md @@ -2,7 +2,7 @@ ## CAN Power Connectors -CAN power connectors are designed for light unmanned aerial (UAV) and other vehicles for providing power over CAN using [CAN power cables](https://docs.raccoonlab.co/guide/pmu/wires/). +CAN power connectors are designed for light unmanned aerial (UAV) and other vehicles for providing power over CAN using [CAN power cables](https://docs.raccoonlab.co/guide/pmu/wires.html). There are two types of devices: diff --git a/docs/ko/dronecan/sapog.md b/docs/ko/dronecan/sapog.md index 1eb7d30402..c10d8ea15c 100644 --- a/docs/ko/dronecan/sapog.md +++ b/docs/ko/dronecan/sapog.md @@ -8,33 +8,8 @@ While it can be controlled using traditional PWM input, it is designed to operat Multiple vendors sell ESC hardware that runs sapog firmware: -- [Zubax Orel 20](https://zubax.com/products/orel_20) - [Holybro Kotleta20](https://holybro.com/products/kotleta20) - - -
-
- Orel20 - Top -
Zubax Orel 20 -
-
- Holybro Kotleta20 top -
Holybro Kotleta20 -
-
- ## 하드웨어 설정 ESCs are connected to the CAN bus using a Pixhawk standard 4 pin JST GH cable. @@ -81,15 +56,15 @@ To enumerate the ESC: 3. Start the process of ESC auto-enumeration by pressing the **Start Assignment** button, as shown on the screenshot below. - ![QGC - DroneCAN ESC auto-enumeration](../../assets/peripherals/esc_qgc/qgc_uavcan_settings.jpg) + ![QGC - DroneCAN ESC auto-enumeration](../../assets/peripherals/esc_qgc/qgc_uavcan_settings.jpg) - You will hear a sound indicating that the flight controller has entered the ESC enumeration mode. + You will hear a sound indicating that the flight controller has entered the ESC enumeration mode. 4. Manually turn each motor in the correct direction of its rotation (as specified in the [Airframe Reference](../airframes/airframe_reference.md)), starting from the first motor and finishing with the last motor. - Each time you turn a motor, you should hear a confirmation beep. + Each time you turn a motor, you should hear a confirmation beep. - ::: info - Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration). + ::: info + Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration). ::: diff --git a/docs/ko/dronecan/zubax_telega.md b/docs/ko/dronecan/zubax_telega.md index f9a7a68da9..19cec8f95e 100644 --- a/docs/ko/dronecan/zubax_telega.md +++ b/docs/ko/dronecan/zubax_telega.md @@ -1,13 +1,13 @@ # Zubax Telega ESCs Zubax Telega is a high end, proprietary sensorless FOC motor control technology. -It is used in multiple products, including the [Zubax Myxa](https://zubax.com/products/myxa) ESC, [Zubax Mitochondrik](https://zubax.com/products/mitochondrik) motor controller module, and Zubax Sadulli integrated drive. +It is used in multiple products, including the [Zubax Myxa](https://shop.zubax.com/products/zubax-myxa) ESC, [Zubax Mitochondrik](https://shop.zubax.com/products/mitochondrik) motor controller module, and Zubax Sadulli integrated drive. While Telega can be controlled using traditional PWM input, it is designed to operate over CAN bus using [DroneCAN](index.md). :::info ESCs based on Zubax Telega require non-trivial tuning of the propulsion system in order to deliver adequate performance and ensure robust operation. -Users who lack the necessary tuning expertise are advised to either [purchase pre-tuned UAV propulsion kits](https://zubax.com/products/uav_propulsion_kits) or to use Zubax Robotic's professional tuning service. +Users who lack the necessary tuning expertise are advised to either [purchase pre-tuned UAV propulsion kits](https://zubax.com/products#electric-drives) or to use Zubax Robotic's professional tuning service. Questions on this matter should be addressed to: [support@zubax.com](mailto:support@zubax.com). ::: @@ -15,10 +15,9 @@ Questions on this matter should be addressed to: [support@zubax.com](mailto:supp ## 구매처 -- [Zubax Myxa](https://zubax.com/products/myxa): High-end PMSM/BLDC motor controller (FOC ESC) for light unmanned aircraft and watercraft. -- [Zubax Mitochondrik](https://zubax.com/products/mitochondrik): Integrated sensorless PMSM/BLDC motor controller chip (used in ESCs and integrated drives) -- [Zubax Komar](https://shop.zubax.com/products/komar-motor-controller-open-hardware-reference-design-for-mitochondrik?variant=32931555868771): Open hardware reference design for Mitochondrik -- [Zubax Sadulli Integrated Drive](https://shop.zubax.com/collections/integrated-drives/products/sadulli-integrated-drive-open-hardware-reference-design-for-mitochondrik?variant=27740841181283) +- [Zubax Myxa](https://shop.zubax.com/products/zubax-myxa): High-end PMSM/BLDC motor controller (FOC ESC) for light unmanned aircraft and watercraft. +- [Zubax Mitochondrik](https://shop.zubax.com/products/mitochondrik): Integrated sensorless PMSM/BLDC motor controller chip (used in ESCs and integrated drives) +- [Zubax Komar](https://shop.zubax.com/products/zubax-ad0510-komar-esc?variant=32931555868771): Open hardware reference design for Mitochondrik ## 하드웨어 설정 @@ -27,10 +26,10 @@ For more information, refer to the [CAN Wiring](../can/index.md#wiring) instruct ## Firmware Setup -Motor enumeration for [Telega-based ESCs](https://zubax.com/products/telega) is usually performed using the [Kucher tool](https://files.zubax.com/products/com.zubax.kucher/) (or less "GUI-friendly" [DroneCAN GUI Tool](https://dronecan.github.io/GUI_Tool/Overview/)). +Motor enumeration for [Telega-based ESCs](https://telega.zubax.com/) is usually performed using the [Kucher tool](https://files.zubax.com/products/com.zubax.kucher/) (or less "GUI-friendly" [DroneCAN GUI Tool](https://dronecan.github.io/GUI_Tool/Overview/)). Telega does NOT support automatic enumeration by spinning the motor. -There is some guidance here: [Quick start guide for Myxa v0.1](https://forum.zubax.com/t/quick-start-guide-for-myxa-v0-1/911) (Zubax blog). +There is some guidance here: [Quick start guide for Myxa v0.1](https://forum.zubax.com/t/quick-start-guide-for-myxa/911) (Zubax blog). Telega ESCs also require other motor setup and configuration for reliable performance. See the above guide and other Zubax documentation for more information. diff --git a/docs/ko/flight_controller/autopilot_discontinued.md b/docs/ko/flight_controller/autopilot_discontinued.md index 7f623cdd63..107a1a0c25 100644 --- a/docs/ko/flight_controller/autopilot_discontinued.md +++ b/docs/ko/flight_controller/autopilot_discontinued.md @@ -17,6 +17,8 @@ They are listed because you may be using them in an existing drone, and because - [Holybro Pixhawk Mini](../flight_controller/pixhawk_mini.md) (FMUv3) - [Holybro Pixfalcon](../flight_controller/pixfalcon.md) (Pixhawk FMUv2) - [Holybro Pix32](../flight_controller/holybro_pix32.md) (FMUv2) +- [ModalAI VOXL Flight](../flight_controller/modalai_voxl_flight.md) +- [ModalAI Flight Core v1](../flight_controller/modalai_fc_v1.md) - [mRobotics-X2.1](../flight_controller/mro_x2.1.md) (FMUv2) - [mRo AUAV-X2](../flight_controller/auav_x2.md) (Pixhawk FMUv2) - [NXP FMUK66](../flight_controller/nxp_rddrone_fmuk66.md) (Discontinued) diff --git a/docs/ko/flight_controller/autopilot_manufacturer_supported.md b/docs/ko/flight_controller/autopilot_manufacturer_supported.md index ebea4e589c..f0e843b75c 100644 --- a/docs/ko/flight_controller/autopilot_manufacturer_supported.md +++ b/docs/ko/flight_controller/autopilot_manufacturer_supported.md @@ -25,12 +25,9 @@ This category includes boards that are not fully compliant with the pixhawk stan - [CubePilot Cube Yellow](../flight_controller/cubepilot_cube_yellow.md) - [Holybro Kakute H7v2](../flight_controller/kakuteh7v2.md) - [Holybro Kakute H7mini](../flight_controller/kakuteh7mini.md) -- [Holybro Kakute F7](../flight_controller/kakutef7.md) - Discontinued - [Holybro Kakute H7](../flight_controller/kakuteh7.md) - [Holybro Durandal](../flight_controller/durandal.md) - [Holybro Pix32 v5](../flight_controller/holybro_pix32_v5.md) -- [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) - [mRo Control Zero](../flight_controller/mro_control_zero_f7.md) - [Sky-Drones AIRLink](../flight_controller/airlink.md) diff --git a/docs/ko/flight_controller/beaglebone_blue.md b/docs/ko/flight_controller/beaglebone_blue.md index a12a9435d3..95602eb614 100644 --- a/docs/ko/flight_controller/beaglebone_blue.md +++ b/docs/ko/flight_controller/beaglebone_blue.md @@ -27,7 +27,7 @@ Other useful information can be found in the [FAQ](https://github.com/beagleboar Optionally you can update to a realtime kernel, and if you do, re-check if _librobotcontrol_ works properly with the realtime kernel. ::: -The latest OS images at time of updating this document is [bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz](https://debian.beagle.cc/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz). +The latest OS images at time of updating this document is [AM3358 Debian 10.3 2020-04-06 4GB SD IoT](https://www.beagleboard.org/distros/am3358-debian-10-3-2020-04-06-4gb-sd-iot). ## 크로스 컴파일러 빌드 (권장) diff --git a/docs/ko/flight_controller/cuav_nora.md b/docs/ko/flight_controller/cuav_nora.md index 4415b4eeb0..1729b7e98e 100644 --- a/docs/ko/flight_controller/cuav_nora.md +++ b/docs/ko/flight_controller/cuav_nora.md @@ -140,7 +140,7 @@ FTDI 케이블을 DSU7 커넥터에 연결하기만 하면됩니다. 제품 목 The [PX4 System Console](../debug/system_console.md) and [SWD interface](../debug/swd_debug.md) operate on the **FMU Debug** port (`DSU7`). -The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/product-detail/en/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/455-1582-1-ND/807850) connector and has the following pinout: +The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/en/products/detail/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/807850) connector and has the following pinout: | 핀 | 신호 | 전압 | | ------------------------- | ------------------------------- | --------------------- | diff --git a/docs/ko/flight_controller/cuav_pixhawk_v6x.md b/docs/ko/flight_controller/cuav_pixhawk_v6x.md index 49de406664..b253c1a36d 100644 --- a/docs/ko/flight_controller/cuav_pixhawk_v6x.md +++ b/docs/ko/flight_controller/cuav_pixhawk_v6x.md @@ -96,7 +96,6 @@ The Pixhawk® V6X is ideal for corporate research labs, academic research and co - Baseboard: 56g - Operating & storage temperature: -20 ~ 85°c - Size - - Flight controller ![Pixhawk V6X](../../assets/flight_controller/cuav_pixhawk_v6x/v6x_size.jpg) @@ -206,7 +205,7 @@ The pinouts and connector comply with the [Pixhawk Debug Full](../debug/swd_debu ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/cuav_v5_nano.md b/docs/ko/flight_controller/cuav_v5_nano.md index 9a3d4cdeeb..87f674128f 100644 --- a/docs/ko/flight_controller/cuav_v5_nano.md +++ b/docs/ko/flight_controller/cuav_v5_nano.md @@ -104,7 +104,7 @@ The [PX4 System Console](../debug/system_console.md) and [SWD interface](../debu ![Debug port (DSU7)](../../assets/flight_controller/cuav_v5_nano/debug_port_dsu7.jpg) -The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/product-detail/en/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/455-1582-1-ND/807850) connector and has the following pinout: +The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/en/products/detail/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/807850) connector and has the following pinout: | 핀 | 신호 | 전압 | | ------------------------- | ------------------------------- | --------------------- | diff --git a/docs/ko/flight_controller/cuav_v5_plus.md b/docs/ko/flight_controller/cuav_v5_plus.md index fb3a598cd3..2a29246848 100644 --- a/docs/ko/flight_controller/cuav_v5_plus.md +++ b/docs/ko/flight_controller/cuav_v5_plus.md @@ -132,7 +132,7 @@ The [PX4 System Console](../debug/system_console.md) and [SWD interface](../debu ![Debug port (DSU7)](../../assets/flight_controller/cuav_v5_plus/debug_port_dsu7.jpg) -The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/product-detail/en/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/455-1582-1-ND/807850) connector and has the following pinout: +The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/en/products/detail/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/807850) connector and has the following pinout: | 핀 | 신호 | 전압 | | ------------------------- | ------------------------------- | --------------------- | diff --git a/docs/ko/flight_controller/cuav_x7.md b/docs/ko/flight_controller/cuav_x7.md index 48db23d9c2..89f345c533 100644 --- a/docs/ko/flight_controller/cuav_x7.md +++ b/docs/ko/flight_controller/cuav_x7.md @@ -12,7 +12,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://www.cuav.net) for hardware support or compliance issues. ::: -The [X7](http://doc.cuav.net/flight-controller/x7/en/x7.html)® flight controller is a high-performance autopilot. +The [X7](https://doc.cuav.net/controller/x7/en/)® flight controller is a high-performance autopilot. 산업용 드론과 대형 대형 드론에 적합합니다. 주로 상용 제조업체에 공급됩니다. @@ -151,7 +151,7 @@ FTDI 케이블을 DSU7 커넥터에 연결하기만 하면됩니다. 제품 목 The [PX4 System Console](../debug/system_console.md) and [SWD interface](../debug/swd_debug.md) operate on the **FMU Debug** port (`DSU7`). -The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/product-detail/en/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/455-1582-1-ND/807850) connector and has the following pinout: +The debug port (`DSU7`) uses a [JST BM06B](https://www.digikey.com.au/en/products/detail/jst-sales-america-inc/BM06B-GHS-TBT-LF-SN-N/807850) connector and has the following pinout: | 핀 | 신호 | 전압 | | ------------------------- | ------------------------------- | --------------------- | @@ -177,11 +177,10 @@ For direct connection to _Segger Jlink_ we recommended you use the 3.3 Volts fro ## 지원 플랫폼 및 기체 -일반 RC 서보 또는 Futaba S-Bus 서보로 제어 가능한 모든 멀티콥터/비행기/로버 또는 보트. +Any multicopter / plane / rover or boat that can be controlled with normal RC servos or Futaba S-Bus servos. The complete set of supported configurations can be seen in the [Airframes Reference](../airframes/airframe_reference.md). ## 추가 정보 -- [Quick start](http://doc.cuav.net/flight-controller/x7/en/quick-start/quick-start-x7.html) - [CUAV docs](https://doc.cuav.net/) - [x7 schematic](https://github.com/cuav/hardware/tree/master/X7_Autopilot) diff --git a/docs/ko/flight_controller/durandal.md b/docs/ko/flight_controller/durandal.md index df406d3053..6f2fc66681 100644 --- a/docs/ko/flight_controller/durandal.md +++ b/docs/ko/flight_controller/durandal.md @@ -90,9 +90,7 @@ For more information see: [Durandal Technical Data Sheet](https://cdn.shopify.co ## 구매처 -Order from [Holybro](https://holybro.com/collections/autopilot-flight-controllers/products/durandal). - - +Order from [Holybro](https://holybro.com/products/durandal). ## 연결 @@ -182,9 +180,7 @@ make holybro_durandal-v1_default - - -## 디버그 포트 +## Debug Port {#debug_port} The [PX4 System Console](../debug/system_console.md) and [SWD interface](../debug/swd_debug.md) run on the _Debug Port_. diff --git a/docs/ko/flight_controller/holybro_pix32.md b/docs/ko/flight_controller/holybro_pix32.md index 6760018783..ab57a27967 100644 --- a/docs/ko/flight_controller/holybro_pix32.md +++ b/docs/ko/flight_controller/holybro_pix32.md @@ -7,7 +7,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues. ::: -The Holybro® [pix32 autopilot](https://holybro.com/collections/autopilot-flight-controllers/products/pix32pixhawk-flight-controller) (also known as "Pixhawk 2", and formerly as HKPilot32) is based on the [Pixhawk®-project](https://pixhawk.org/) **FMUv2** open hardware design. +The Holybro® [pix32 autopilot](https://holybro.com/products/pix32pixhawk-flight-controller) (also known as "Pixhawk 2", and formerly as HKPilot32) is based on the [Pixhawk®-project](https://pixhawk.org/) **FMUv2** open hardware design. This board is based on hardware version Pixhawk 2.4.6. It runs the PX4 flight stack on the [NuttX](https://nuttx.apache.org/) OS. @@ -58,12 +58,11 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo ## 구매처 -[shop.holybro.com](https://holybro.com/collections/autopilot-flight-controllers/products/pix32pixhawk-flight-controller) +[shop.holybro.com](https://holybro.com/products/pix32pixhawk-flight-controller) ### 소품 -- [Digital airspeed sensor](https://holybro.com/products/digital-air-speed-sensor) -- [Hobbyking® Wifi Telemetry](https://hobbyking.com/en_us/apm-pixhawk-wireless-wifi-radio-module.html) +- [Digital airspeed sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [HolyBro SiK Telemetry Radio (EU 433 MHz, US 915 MHz)](../telemetry/holybro_sik_radio.md) ## 펌웨어 빌드 diff --git a/docs/ko/flight_controller/holybro_pix32_v6.md b/docs/ko/flight_controller/holybro_pix32_v6.md index b4093ea31b..f91f924f4a 100644 --- a/docs/ko/flight_controller/holybro_pix32_v6.md +++ b/docs/ko/flight_controller/holybro_pix32_v6.md @@ -95,7 +95,7 @@ This flight controller is perfect for people that is looking for a affordable an ## 구매처 -Order from [Holybro](https://holybro.com/collections/autopilot-flight-controllers/products/pix32-v6). +Order from [Holybro](https://holybro.com/products/pix32-v6). ## 핀배열 @@ -188,7 +188,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/kakutef7.md b/docs/ko/flight_controller/kakutef7.md index 3aea837e6e..09871f8b6b 100644 --- a/docs/ko/flight_controller/kakutef7.md +++ b/docs/ko/flight_controller/kakutef7.md @@ -2,6 +2,10 @@ +:::warning +This frame has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: + :::warning PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues. diff --git a/docs/ko/flight_controller/kakuteh7mini.md b/docs/ko/flight_controller/kakuteh7mini.md index 60f812c008..6c6ee145e3 100644 --- a/docs/ko/flight_controller/kakuteh7mini.md +++ b/docs/ko/flight_controller/kakuteh7mini.md @@ -7,7 +7,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues. ::: -The [Holybro Kakute H7 mini](https://holybro.com/collections/autopilot-flight-controllers/products/kakute-h7-mini) flight controller is intended for lightweight frame builds (such as racers, etc.). +The [Holybro Kakute H7 mini](https://holybro.com/products/kakute-h7-mini) flight controller is intended for lightweight frame builds (such as racers, etc.). This flight controller is full of features including HD camera plug, dual plug-and-play 4in1 ESC ports, VTX ON/OFF Pit Switch (Battery Voltage), barometer, OSD, 6x UARTs, 128MB Flash for logging (not supported with PX4 yet), 5V BEC, and bigger soldering pad with easy layout and much more. diff --git a/docs/ko/flight_controller/kakuteh7v2.md b/docs/ko/flight_controller/kakuteh7v2.md index d6fda590b4..bb49e7a9be 100644 --- a/docs/ko/flight_controller/kakuteh7v2.md +++ b/docs/ko/flight_controller/kakuteh7v2.md @@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues. ::: -The [Holybro Kakute H7 V2](https://holybro.com/collections/autopilot-flight-controllers/products/kakute-h7-v2) flight controller is full of features including integrated Bluetooth, HD camera plug, dual plug-and-play 4in1 ESC ports, 9V VTX ON/OFF Pit Switch, barometer, OSD, 6x UARTs, 128MB Flash for Logging (not supported with PX4 yet), 5V and 9V BEC, and bigger soldering pad with easy layout and much more. +The [Holybro Kakute H7 V2](https://holybro.com/products/kakute-h7-v2) flight controller is full of features including integrated Bluetooth, HD camera plug, dual plug-and-play 4in1 ESC ports, 9V VTX ON/OFF Pit Switch, barometer, OSD, 6x UARTs, 128MB Flash for Logging (not supported with PX4 yet), 5V and 9V BEC, and bigger soldering pad with easy layout and much more. The Kakute H7v2 builds upon the best features of its predecessor, the [Kakute F7](../flight_controller/kakutef7.md), and the [Kakute H7](../flight_controller/kakuteh7.md). diff --git a/docs/ko/flight_controller/mindpx.md b/docs/ko/flight_controller/mindpx.md index 62a34ab1dc..e3bf186c00 100644 --- a/docs/ko/flight_controller/mindpx.md +++ b/docs/ko/flight_controller/mindpx.md @@ -28,7 +28,6 @@ MindPX는보다 복잡한 VTOL 구성과보다 정밀한 제어를 지원할 수 ![](../../assets/hardware/hardware-mindpx-specs.png) - 메인시스템 온칩 : STM32F427 - - CPU : 32 비트, 168 MHz ARM 코어 텍스® FPU 포함 M4 - RAM : 256KB SRAM - 2MB 플래시 @@ -107,7 +106,7 @@ MindPX에는 보드에는 USB-TO-UART 브리지 IC가 있습니다. ## 구매처 -MindRacer는 인터넷 [AirMind Store](http://drupal.xitronet.com/?q=catalog)에 구매할 수 있습니다. +MindRacer is available at [AirMind Store](https://airmind.mindpx.net/catalog). Amazon® 또는 eBay®에서도 MindRacer를 구매할 수 있습니다. ## 시리얼 포트 매핑 diff --git a/docs/ko/flight_controller/mindracer.md b/docs/ko/flight_controller/mindracer.md index 8d233867a2..a1b4b9d547 100644 --- a/docs/ko/flight_controller/mindracer.md +++ b/docs/ko/flight_controller/mindracer.md @@ -89,7 +89,7 @@ The user guide is [here](http://mindpx.net/assets/accessories/mindracer_user_gui ## 구매처 -MindRacer is available at [AirMind Store](http://drupal.xitronet.com/?q=catalog). +MindRacer is available at [AirMind Store](https://airmind.mindpx.net/catalog). Amazon® 또는 eBay®에서도 MindRacer를 구매할 수 있습니다. ## 지원 diff --git a/docs/ko/flight_controller/modalai_fc_v1.md b/docs/ko/flight_controller/modalai_fc_v1.md index 30a8de5b15..c34ccd0469 100644 --- a/docs/ko/flight_controller/modalai_fc_v1.md +++ b/docs/ko/flight_controller/modalai_fc_v1.md @@ -1,14 +1,18 @@ # ModalAI Flight Core v1 - + + +:::warning +This frame has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: :::warning PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://forum.modalai.com/) for hardware support or compliance issues. ::: -The ModalAI [Flight Core v1](https://modalai.com/flight-core) ([Datasheet](https://docs.modalai.com/flight-core-datasheet)) is a flight controller for PX4, made in the USA. -The Flight Core can be paired with ModalAI [VOXL](https://modalai.com/voxl) ([Datasheet](https://docs.modalai.com/voxl-datasheet/)) for obstacle avoidance and GPS-denied navigation, or used independently as a standalone flight controller. +The ModalAI _Flight Core v1_ ([Datasheet](https://docs.modalai.com/flight-core-datasheet)) is a flight controller for PX4, made in the USA. +The Flight Core can be paired with ModalAI VOXL for obstacle avoidance and GPS-denied navigation, or used independently as a standalone flight controller. ![FlightCoreV1](../../assets/flight_controller/modalai/fc_v1/main.jpg) @@ -52,9 +56,9 @@ More detailed hardware documentation can be found [here](https://docs.modalai.co [stm32f765ii]: https://www.st.com/en/microcontrollers-microprocessors/stm32f765ii.html -[bmp388]: https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp388/ -[icm-20602]: https://www.invensense.com/products/motion-tracking/6-axis/icm-20602/ -[bmi088]: https://www.bosch-sensortec.com/bst/products/all_products/bmi088_1 +[bmp388]: https://www.adafruit.com/product/3966 +[icm-20602]: https://invensense.tdk.com/products/motion-tracking/6-axis/icm-20602/ +[bmi088]: https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi088/ [px4]: https://github.com/PX4/PX4-Autopilot/tree/main/boards/modalai/fc-v1 [a71ch]: https://www.nxp.com/products/security-and-authentication/authentication/plug-and-trust-the-fast-easy-way-to-deploy-secure-iot-connections:A71CH @@ -77,10 +81,7 @@ More information about the firmware can be found [here](https://docs.modalai.com ## 구매처 -- [Flight Core Complete Kit](https://modalai.com/flight-core) -- [Flight Core integrated with VOXL Companion Computer on a single PCB](https://modalai.com/flight-core) -- [Flight Core integrated with VOXL Companion Computer and Obstacle Avoidance Cameras (VOXL Flight Deck)](https://modalai.com/flight-deck) ([Datasheet](https://docs.modalai.com/voxl-flight-deck-platform-datasheet/)) -- [Flight Core assembled with VOXL and cameras](https://shop.modalai.com/products/voxl-flight-deck-r1) +- No longer available ## 빠른 시작 diff --git a/docs/ko/flight_controller/modalai_voxl_flight.md b/docs/ko/flight_controller/modalai_voxl_flight.md index f8a558e0a2..848dd9fd19 100644 --- a/docs/ko/flight_controller/modalai_voxl_flight.md +++ b/docs/ko/flight_controller/modalai_voxl_flight.md @@ -1,13 +1,17 @@ # ModalAI VOXL Flight - + + +:::warning +This frame has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available. +::: :::warning PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://forum.modalai.com/) for hardware support or compliance issues. ::: -The ModalAI [VOXL Flight](https://modalai.com/voxl-flight) ([Datasheet](https://docs.modalai.com/voxl-flight-datasheet)) is one of the first computing platforms to combine the power and sophistication of Snapdragon with the flexibility and ease of use of PX4 on an STM32F7. +The ModalAI VOXL Flight is one of the first computing platforms to combine the power and sophistication of Snapdragon with the flexibility and ease of use of PX4 on an STM32F7. Made in the USA, VOXL Flight supports obstacle avoidance and GPS-denied (indoor) navigation fused with a PX4 flight controller on a single PCB. ![VOXL-Flight](../../assets/flight_controller/modalai/voxl_flight/voxl-flight-dk.jpg) @@ -76,9 +80,9 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo [stm32f765ii]: https://www.st.com/en/microcontrollers-microprocessors/stm32f765ii.html [px4]: https://github.com/PX4/PX4-Autopilot/tree/main/boards/modalai/fc-v1 -[icm-20602]: https://www.invensense.com/products/motion-tracking/6-axis/icm-20602/ -[bmi088]: https://www.bosch-sensortec.com/bst/products/all_products/bmi088_1 -[bmp388]: https://www.bosch-sensortec.com/products/environmental-sensors/pressure-sensors/bmp388/ +[icm-20602]: https://invensense.tdk.com/products/motion-tracking/6-axis/icm-20602/ +[bmi088]: https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi088/ +[bmp388]: https://www.adafruit.com/product/3966 [a71ch]: https://www.nxp.com/products/security-and-authentication/authentication/plug-and-trust-the-fast-easy-way-to-deploy-secure-iot-connections:A71CH :::info @@ -106,10 +110,7 @@ More information about the firmware can be found [here](https://docs.modalai.com ## 구매처 -- [VOXL Flight Complete Kit](https://modalai.com/voxl-flight) -- [VOXL Flight Board](https://www.modalai.com/products/voxl-flight?variant=31707275362355) (only) -- [VOXL Flight integrated with Obstacle Avoidance Cameras (VOXL Flight Deck)](https://modalai.com/flight-deck) ([Datasheet](https://docs.modalai.com/voxl-flight-deck-platform-datasheet/)) -- [VOXL Flight in a ready to fly VOXL m500 Development Drone](https://www.modalai.com/collections/development-drones/products/voxl-m500) ([Datasheet](https://docs.modalai.com/voxl-m500-reference-drone-datasheet/)) +No longer available. ## 빠른 시작 @@ -132,12 +133,12 @@ _Note: 1000 Series connectors accessible from the STM32/PX4_ | 커넥터 | 요약 | 사용처 | | ----- | ------------------------------------------------------------------- | ---------------------------------------------------- | -| J2 | 4k 이미지 센서 (CSI0) 고용 | Snapdragon - 리눅스 | -| J3 | 스테레오 이미지 센서 (CSI1) | Snapdragon - 리눅스 | -| J6 | 냉각 팬 커넥터 | Snapdragon - 리눅스 | -| J7 | BLSP6 (GPIO) and BLSP9 (UART) | Snapdragon - 리눅스 | -| J13 | 확장 B2B | Snapdragon - 리눅스 | -| J14 | 통합 GNSS 안테나 연결 | Snapdragon - 리눅스 | +| J2 | 4k 이미지 센서 (CSI0) 고용 | Snapdragon - Linux | +| J3 | 스테레오 이미지 센서 (CSI1) | Snapdragon - Linux | +| J6 | 냉각 팬 커넥터 | Snapdragon - Linux | +| J7 | BLSP6 (GPIO) and BLSP9 (UART) | Snapdragon - Linux | +| J13 | 확장 B2B | Snapdragon - Linux | +| J14 | 통합 GNSS 안테나 연결 | Snapdragon - Linux | | J1001 | 프로그래밍 및 디버그/UART3 | STM32 - PX4 | | J1002 | UART ESC, UART2/TELEM3 | STM32 - PX4 | | J1003 | PPM RC 입력 | STM32 - PX4 | @@ -159,13 +160,13 @@ _Note: 1000 Series connectors accessible from the STM32/PX4_ | 커넥터 | 요약 | 사용처 | | ------------ | -------------------------------------- | --------------------------- | -| J4 | 추적/광류 이미지 센서 (CSI2) | Snapdragon - 리눅스 | +| J4 | 추적/광류 이미지 센서 (CSI2) | Snapdragon - Linux | | J8 | USB 3.0 OTG | Snapdragon - Linux, **adb** | -| J10 | BLSP7 UART 및 I2C 오프보드 | Snapdragon - 리눅스 | -| J11 | BLSP12 UART 및 I2C 오프보드 | Snapdragon - 리눅스 | -| VOXL microSD | | Snapdragon - 리눅스 | +| J10 | BLSP7 UART 및 I2C 오프보드 | Snapdragon - Linux | +| J11 | BLSP12 UART 및 I2C 오프보드 | Snapdragon - Linux | +| VOXL microSD | | Snapdragon - Linux | | PX4 microSD | 32Gb Max | STM32 - PX4 | -| Wi-Fi 안테나 | 포함됨. | Snapdragon - 리눅스 | +| Wi-Fi 안테나 | 포함됨. | Snapdragon - Linux | ### 사용자 가이드 diff --git a/docs/ko/flight_controller/mro_control_zero_f7.md b/docs/ko/flight_controller/mro_control_zero_f7.md index 55b4e34502..c4b5bf85c8 100644 --- a/docs/ko/flight_controller/mro_control_zero_f7.md +++ b/docs/ko/flight_controller/mro_control_zero_f7.md @@ -22,20 +22,17 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo ## 주요 특징 - 마이크로 프로세서: - - FPU가있는 32 비트 STM32F777 코어 텍스® M4 코어. 3 - 216 MHz/512 KB RAM/2 MB 플래시 - F-RAM Cypress MF25V02-G 256Kbit 비휘발성 메모리(RAM만큼 빠른 플래시 메모리) - 센서: - - - [Bosch BMI088](https://www.bosch-sensortec.com/bst/products/all_products/bmi088_1) 3-axis accelerometer/gyroscope (internally vibration dampened) - - [Invensense ICM-20602](https://www.invensense.com/products/motion-tracking/6-axis/icm-20602/) 3-axis accelerometer/gyroscope + - [Bosch BMI088](https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi088/) 3-axis accelerometer/gyroscope (internally vibration dampened) + - [Invensense ICM-20602](https://invensense.tdk.com/products/motion-tracking/6-axis/icm-20602/) 3-axis accelerometer/gyroscope - [Invensense ICM-20948](https://www.invensense.com/products/motion-tracking/9-axis/icm-20948/) 3-axis accelerometer/gyroscope/magnetometer - [Infineon DPS310 barometer](https://www.infineon.com/cms/en/product/sensor/pressure-sensors/pressure-sensors-for-iot/dps310/) (So smooth and NO more light sensitivity) - 인터페이스: - - 6x UART(총 직렬 포트), 3x(HW 흐름 제어 포함), 1x FRSky Telemetry(D 또는 X 유형), 1x 콘솔 및 1x GPS + I2C - PWM 출력(모든 DShot 가능) 8개 - CAN 1개 @@ -52,7 +49,6 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo - 삼색 LED - 중량 및 크기(케이스 없음): - - 중량: 5.3g (0.19oz) - 넓이: 20mm (0.79") - 길이: 32mm (1.26") @@ -84,11 +80,11 @@ make mro_ctrl-zero-f7 The [PX4 System Console](../debug/system_console.md) runs on `USART7` using the pins listed below. This is a standard serial pinout, designed to connect to a [3.3V FTDI](https://www.digikey.com/en/products/detail/TTL-232R-3V3/768-1015-ND/1836393) cable (5V tolerant). -| mRo control zero f7 | | FTDI | | -| ------------------- | ----------- | ---- | ------------------------------- | -| 17 | USART7 Tx | 5 | FTDI RX (황) | -| 19 | USART7 Rx | 4 | FTDI TX (적황) | -| 6 | USART21 GND | 1 | FTDI GND (흑) | +\| mRo control zero f7 | | FTDI | +\| ------------------- | ----------- | ---- | ---------------- | +\| 17 | USART7 Tx | 5 | FTDI RX (yellow) | +\| 19 | USART7 Rx | 4 | FTDI TX (orange) | +\| 6 | USART21 GND | 1 | FTDI GND (black) | ### SWD 포트 diff --git a/docs/ko/flight_controller/nxp_mr_vmu_rt1176.md b/docs/ko/flight_controller/nxp_mr_vmu_rt1176.md index 1eb6ee3c2e..e68d711b94 100644 --- a/docs/ko/flight_controller/nxp_mr_vmu_rt1176.md +++ b/docs/ko/flight_controller/nxp_mr_vmu_rt1176.md @@ -265,7 +265,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/omnibus_f4_sd.md b/docs/ko/flight_controller/omnibus_f4_sd.md index 3878055d78..8753f21e49 100644 --- a/docs/ko/flight_controller/omnibus_f4_sd.md +++ b/docs/ko/flight_controller/omnibus_f4_sd.md @@ -211,7 +211,7 @@ The referenced links above contains the documentation for the TX/RX modules. | RX | Ch1 | 다음으로 TX/RX 모듈을 업데이트하여 CRSF 프로토콜을 사용하고 텔레메트리를 설정합니다. -Instructions for this are provided in the [TBS Crossfire Manual](https://www.team-blacksheep.com/tbs-crossfire-manual.pdf) (search for 'Setting up radio for CRSF'). +Instructions for this are provided in the [TBS Crossfire Manual](https://www.team-blacksheep.com/media/files/tbs-crossfire-manual.pdf) (search for 'Setting up radio for CRSF'). #### PX4 CRSF Configuration diff --git a/docs/ko/flight_controller/pixfalcon.md b/docs/ko/flight_controller/pixfalcon.md index 6e347df258..0f789c4add 100644 --- a/docs/ko/flight_controller/pixfalcon.md +++ b/docs/ko/flight_controller/pixfalcon.md @@ -39,11 +39,10 @@ From distributor [Hobbyking®](https://hobbyking.com/en_us/pixfalc Optional hardware: - Optical flow: PX4 Flow unit from manufacturer [Holybro](https://holybro.com/products/px4flow) -- Digital Airspeed sensor from manufacturer [Holybro](https://holybro.com/products/digital-air-speed-sensor) or distributor [Hobbyking](https://hobbyking.com/en_us/hkpilot-32-digital-air-speed-sensor-and-pitot-tube-set.html) +- Digital Airspeed sensor from manufacturer [Holybro](https://holybro.com/products/digital-air-speed-sensor-ms4525do) or distributor [Hobbyking](https://hobbyking.com/en_us/hkpilot-32-digital-air-speed-sensor-and-pitot-tube-set.html) - 텔레메트리가 통합 화면 디스플레이 - [Hobbyking OSD + EU Telemetry (433 MHz)](https://hobbyking.com/en_us/micro-hkpilot-telemetry-radio-module-with-on-screen-display-osd-unit-433mhz.html) - 순수 텔레메트리 옵션: - - [Hobbyking Wifi Telemetry](https://hobbyking.com/en_us/apm-pixhawk-wireless-wifi-radio-module.html) - [SIK Radios](../telemetry/sik_radio.md) ## 펌웨어 빌드 diff --git a/docs/ko/flight_controller/pixhawk4_mini.md b/docs/ko/flight_controller/pixhawk4_mini.md index f2f1bf48a4..bbd22ea165 100644 --- a/docs/ko/flight_controller/pixhawk4_mini.md +++ b/docs/ko/flight_controller/pixhawk4_mini.md @@ -137,7 +137,7 @@ The pinout uses the standard [Pixhawk debug connector](https://github.com/pixhaw ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](../telemetry/index.md) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/pixhawk5x.md b/docs/ko/flight_controller/pixhawk5x.md index 7011995819..dcbdcf5576 100644 --- a/docs/ko/flight_controller/pixhawk5x.md +++ b/docs/ko/flight_controller/pixhawk5x.md @@ -62,7 +62,6 @@ The Pixhawk® 5X is perfect for developers at corporate research labs, startups, - 32 비트 Arm® Cortex®-M3, 24MHz, 8KB SRAM - On-board Sensors: - - Accel/Gyro: ICM-20649 - Accel/Gyro: ICM-42688P - 가속도/자이로: ICM-20602 @@ -70,7 +69,6 @@ The Pixhawk® 5X is perfect for developers at corporate research labs, startups, - Barometer: 2x BMP388 - 인터페이스 - - 16- PWM servo outputs - R/C input for Spektrum / DSM - Dedicated R/C input for PPM and S.Bus input @@ -100,18 +98,15 @@ The Pixhawk® 5X is perfect for developers at corporate research labs, startups, - 2 Dedicated debug and GPIO lines - 정격 전압 - - 최대 입력 전압: 6V - USB 전원 입력: 4.75~5.25V - 서보 레일 입력: 0~36V - 크기 - - Flight Controller Module: 38.8 x 31.8 x 14.6mm - Standard Baseboard: 52.4 x 103.4 x 16.7mm - 중량 - - Flight Controller Module: 23g - Standard Baseboard: 51g @@ -227,7 +222,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/pixhawk6c.md b/docs/ko/flight_controller/pixhawk6c.md index b6a130c336..015476573a 100644 --- a/docs/ko/flight_controller/pixhawk6c.md +++ b/docs/ko/flight_controller/pixhawk6c.md @@ -194,7 +194,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/flight_controller/pixhawk6c_mini.md b/docs/ko/flight_controller/pixhawk6c_mini.md index fc76068bc5..8d884325c9 100644 --- a/docs/ko/flight_controller/pixhawk6c_mini.md +++ b/docs/ko/flight_controller/pixhawk6c_mini.md @@ -193,7 +193,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](../telemetry/index.md): - [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md) - [Holybro Microhard P900 Radio](../telemetry/holybro_microhard_p900_radio.md) diff --git a/docs/ko/flight_controller/pixhawk6x-rt.md b/docs/ko/flight_controller/pixhawk6x-rt.md index 9ec2a19e51..cae46b21bb 100644 --- a/docs/ko/flight_controller/pixhawk6x-rt.md +++ b/docs/ko/flight_controller/pixhawk6x-rt.md @@ -122,7 +122,6 @@ The Pixhawk®​ 6X-RT is perfect for developers at corporate research labs, sta - CAN Bus has individual silent controls or ESC RX-MUX control - 2 Power input ports with SMBus - - 1 AD & IO port - 2개의 추가 아날로그 입력 - 1 PWM/Capture input @@ -240,7 +239,7 @@ For information about using this port see: ## 주변 장치 -- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor) +- [Digital Airspeed Sensor](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Telemetry Radio Modules](https://holybro.com/collections/telemetry-radios?orderby=date) - [Rangefinders/Distance sensors](../sensor/rangefinders.md) diff --git a/docs/ko/frames_multicopter/dji_f450_cuav_5nano.md b/docs/ko/frames_multicopter/dji_f450_cuav_5nano.md index e147ecb4a8..82c0b52ee5 100644 --- a/docs/ko/frames_multicopter/dji_f450_cuav_5nano.md +++ b/docs/ko/frames_multicopter/dji_f450_cuav_5nano.md @@ -163,7 +163,7 @@ FrSky Taranis 조종기를 사용할 수 있습니다. ## PX4 설정 _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. :::tip Full instructions for installing and configuring PX4 can be found in [Basic Configuration](../config/index.md). diff --git a/docs/ko/frames_multicopter/dji_f450_cuav_5plus.md b/docs/ko/frames_multicopter/dji_f450_cuav_5plus.md index 64ed53be20..9621e854b7 100644 --- a/docs/ko/frames_multicopter/dji_f450_cuav_5plus.md +++ b/docs/ko/frames_multicopter/dji_f450_cuav_5plus.md @@ -166,7 +166,7 @@ FrSky Taranis 조종기를 사용할 수 있습니다. ## PX4 설정 _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the frame. -[Download and install](https://qgroundcontrol.com/downloads/) +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. :::tip diff --git a/docs/ko/frames_multicopter/holybro_qav250_pixhawk4_mini.md b/docs/ko/frames_multicopter/holybro_qav250_pixhawk4_mini.md index 09c35d2fdf..5677c2aac7 100644 --- a/docs/ko/frames_multicopter/holybro_qav250_pixhawk4_mini.md +++ b/docs/ko/frames_multicopter/holybro_qav250_pixhawk4_mini.md @@ -211,7 +211,7 @@ If you have to wire the system yourself, the diagram below shows all the connect ## PX4 설정 _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the QAV250 frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. :::tip Full instructions for installing and configuring PX4 can be found in [Basic Configuration](../config/index.md). diff --git a/docs/ko/frames_multicopter/holybro_s500_v2_pixhawk4.md b/docs/ko/frames_multicopter/holybro_s500_v2_pixhawk4.md index 680e9f02d5..1a2c8bc8f6 100644 --- a/docs/ko/frames_multicopter/holybro_s500_v2_pixhawk4.md +++ b/docs/ko/frames_multicopter/holybro_s500_v2_pixhawk4.md @@ -268,7 +268,7 @@ M3X8 나사 (총 8개, 각 측면에 4개)로 연결합니다. ## PX4 설정 _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the QAV250 frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. :::tip Full instructions for installing and configuring PX4 can be found in [Basic Configuration](../config/index.md). diff --git a/docs/ko/frames_multicopter/holybro_x500V2_pixhawk5x.md b/docs/ko/frames_multicopter/holybro_x500V2_pixhawk5x.md index 93bc0114f2..71b00944d1 100644 --- a/docs/ko/frames_multicopter/holybro_x500V2_pixhawk5x.md +++ b/docs/ko/frames_multicopter/holybro_x500V2_pixhawk5x.md @@ -196,7 +196,7 @@ Full instructions for installing and configuring PX4 can be found in [Basic Conf ::: _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the X500 frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. First update the firmware, airframe, and actuator mappings: diff --git a/docs/ko/frames_multicopter/holybro_x500_pixhawk4.md b/docs/ko/frames_multicopter/holybro_x500_pixhawk4.md index 31247eafa5..12b2c679bb 100644 --- a/docs/ko/frames_multicopter/holybro_x500_pixhawk4.md +++ b/docs/ko/frames_multicopter/holybro_x500_pixhawk4.md @@ -215,7 +215,7 @@ Full instructions for installing and configuring PX4 can be found in [Basic Conf ::: _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the X500 frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. First update the firmware, airframe, and actuator mappings: diff --git a/docs/ko/frames_multicopter/holybro_x500v2_pixhawk6c.md b/docs/ko/frames_multicopter/holybro_x500v2_pixhawk6c.md index 3331f53b37..86543b5e5f 100644 --- a/docs/ko/frames_multicopter/holybro_x500v2_pixhawk6c.md +++ b/docs/ko/frames_multicopter/holybro_x500v2_pixhawk6c.md @@ -171,7 +171,7 @@ Full instructions for installing and configuring PX4 can be found in [Basic Conf ::: _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the X500 frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. First update the firmware, airframe, and actuator mappings: diff --git a/docs/ko/frames_multicopter/qav_r_5_kiss_esc_racer.md b/docs/ko/frames_multicopter/qav_r_5_kiss_esc_racer.md index 4d6015c546..28ffd7b5e3 100644 --- a/docs/ko/frames_multicopter/qav_r_5_kiss_esc_racer.md +++ b/docs/ko/frames_multicopter/qav_r_5_kiss_esc_racer.md @@ -225,7 +225,7 @@ To configure the transmitter to an other channel and adjust the transmission pow ## PX4 설정 _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for the frame. -[Download and install](https://qgroundcontrol.com/downloads/) _QGroundControl_ for your platform. +[Download and install](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html) _QGroundControl_ for your platform. :::tip Full instructions for installing and configuring PX4 can be found in [Basic Configuration](../config/index.md). diff --git a/docs/ko/frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md b/docs/ko/frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md index 8405164f3a..a55b0116ab 100644 --- a/docs/ko/frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md +++ b/docs/ko/frames_vtol/vtol_quadplane_falcon_vertigo_hybrid_rtf_dropix.md @@ -284,7 +284,3 @@ Perform the normal [Basic Configuration](../config/index.md). ## 비디오 - -## 지원 - -If you have any questions regarding your VTOL conversion or configuration please visit . diff --git a/docs/ko/frames_vtol/vtol_quadplane_foxtech_loong_2160.md b/docs/ko/frames_vtol/vtol_quadplane_foxtech_loong_2160.md index 93dc9fa2e8..9decf9821c 100644 --- a/docs/ko/frames_vtol/vtol_quadplane_foxtech_loong_2160.md +++ b/docs/ko/frames_vtol/vtol_quadplane_foxtech_loong_2160.md @@ -44,7 +44,7 @@ The following options have been tested: - [GPS F9P (included in Skynode eval. kit)](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) - [GPS M9N (cheaper alternative to F9P)](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) - [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/airspeed-sensor-sdp33) — recommended for improved safety and performance -- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor?pr_prod_strat=use_description&pr_rec_id=236dfda00&pr_rec_pid=7150470561981&pr_ref_pid=7150472462525&pr_seq=uniform) +- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) (Optional) - [Lidar Seeed Studio PSK-CM8JL65-CC5 (cheaper alternative)](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) (Optional) - [Radio (RC) System](../getting_started/rc_transmitter_receiver.md) of your preference diff --git a/docs/ko/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md b/docs/ko/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md index abe6c16c36..cb090bee2e 100644 --- a/docs/ko/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md +++ b/docs/ko/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md @@ -74,7 +74,3 @@ For further instructions on wiring and configurations please see: ## 비디오 - -## 지원 - -If you have any questions regarding your VTOL conversion or configuration please visit . diff --git a/docs/ko/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md b/docs/ko/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md index 146831f6eb..5b3cccaeaf 100644 --- a/docs/ko/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md +++ b/docs/ko/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md @@ -102,7 +102,7 @@ Pixhawk의 출력은 다음과 같이 연결되어야합니다 ( "평면에 앉 | AUX 5 | 스로틀 | :::info -The servo direction can be reversed using the PWM\_REV parameters in the PWM\_OUTPUT group of QGroundControl (cogwheel tab, last item in the left menu) +The servo direction can be reversed using the PWM_REV parameters in the PWM_OUTPUT group of QGroundControl (cogwheel tab, last item in the left menu) ::: For further instructions on wiring and configurations please see: [Standard VTOL Wiring and Configuration](../config_vtol/vtol_quad_configuration.md) @@ -112,7 +112,3 @@ For further instructions on wiring and configurations please see: [Standard VTOL Configure the frame as shown in QGroundControl below (do not forget to click **Apply and Restart** in the top). ![QGC - select firmware for standard VTOL](../../assets/airframes/vtol/funcub_pixhawk/qgc_firmware_standard_vtol_fun_cub_quad.png) - -## 지원 - -If you have any questions regarding your VTOL conversion or configuration please visit . diff --git a/docs/ko/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md b/docs/ko/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md index 5cab5bacce..9bb916d719 100644 --- a/docs/ko/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md +++ b/docs/ko/frames_vtol/vtol_tiltrotor_omp_hobby_zmo_fpv.md @@ -44,7 +44,7 @@ The approximate maximum size of the FC is: 50x110x22mm - [GPS F9P (included in Skynode eval. kit)](../gps_compass/rtk_gps_holybro_h-rtk-f9p.md) - [GPS M9N (cheaper alternative to F9P)](../gps_compass/rtk_gps_holybro_h-rtk-m8p.md) - [Airspeed sensor (included in Skynode eval. kit)](https://www.dualrc.com/parts/airspeed-sensor-sdp33) — recommended for improved safety and performance -- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor?pr_prod_strat=use_description&pr_rec_id=236dfda00&pr_rec_pid=7150470561981&pr_ref_pid=7150472462525&pr_seq=uniform) +- [Airspeed sensor (cheaper alternative)](https://holybro.com/products/digital-air-speed-sensor-ms4525do) - [Lidar Lightware lw20-c (included in Skynode eval. kit)](../sensor/sfxx_lidar.md) (Optional) - [Lidar Seeed Studio PSK-CM8JL65-CC5 (cheaper alternative)](https://www.seeedstudio.com/PSK-CM8JL65-CC5-Infrared-Distance-Measuring-Sensor-p-4028.html) (Optional) - [5V BEC](https://www.mateksys.com/?portfolio=bec12s-pro) diff --git a/docs/ko/getting_started/px4_basic_concepts.md b/docs/ko/getting_started/px4_basic_concepts.md index 663de0e58e..da456a2a21 100644 --- a/docs/ko/getting_started/px4_basic_concepts.md +++ b/docs/ko/getting_started/px4_basic_concepts.md @@ -1,71 +1,72 @@ # 기본 개념 -This topic provides a basic introduction to drones and using PX4 (it is meant mostly for novice users but is also a good introduction for more experienced users). +이 주제는 드론과 PX4 사용에 대한 기본적인 소개를 제공합니다 (주로 초보자를 위한 내용이지만, 경험이 있는 사용자에게도 좋은 입문 자료가 될 수 있습니다). -If you are already familiar with the basic concepts, you can move on to [Basic Assembly](../assembly/index.md) to learn how to wire your specific autopilot hardware. -To load firmware and set up the vehicle with _QGroundControl_, see [Basic Configuration](../config/index.md). +기본 개념에 이미 익숙하다면, [기본 조립](../assembly/index.md) 섹션으로 넘어가서 사용 중인 오토파일럿 하드웨어의 배선 방법을 배우실 수 있습니다. +펌웨어를 설치하고 _QGroundControl_을 사용해 비행체를 설정하려면\ +[기본 설정](../config/index.md) 섹션을 참조하세요. ## 드론의 정의 -A drone, or Unmanned Vehicles (UV), is an unmanned "robotic" vehicle that can be manually or autonomously controlled. -They can travel in air, on the ground, on/under the water, and are used for many [consumer, industrial, government and military applications](https://px4.io/ecosystem/commercial-systems/), including aerial photography/video, carrying cargo, racing, search and surveying, and so on. +드론(Drones), 또는 무인 차량(Unmanned Vehicles, UV)은 사람이 탑승하지 않은 "로봇형" 차량으로, 수동 또는 자율적으로 제어될 수 있습니다. +드론은 공중, 지상, 수상 또는 수중을 이동할 수 있으며, 항공 사진/영상 촬영, 화물 운송, 레이싱, 수색, 측량 등 다양한 [소비자, 산업, 정부 및 군사 분야](https://px4.io/ecosystem/commercial-systems/)에서 활용됩니다. -Drones are more formally referred to as Unmanned Aerial Vehicles (UAV), Unmanned Ground Vehicles (UGV), Unmanned Surface Vehicles (USV), Unmanned Underwater Vehicles (UUV). +드론은 보다 공식적으로는 무인 항공기(UAV), 무인 지상 차량(UGV), 무인 수상 차량(USV), 무인 수중 차량(UUV)으로 구분됩니다. :::info -The term Unmanned Aerial System (UAS) typically refers to a UAV and all of the other components of a complete system, including a ground control station and/or radio controller, and any other systems used to control the drone, capture, and process data. +"무인 항공 시스템(UAS)"이라는 용어는 일반적으로 UAV(무인 항공기)와 함께 이를 구성하는 전체 시스템을 의미하며, 여기에는 지상 관제소, 무선 조종기, 드론을 제어하거나 데이터를 수집 및 처리하는 데 사용되는 모든 시스템이 포함됩니다. ::: -## Drone Types +## 드론의 종류 -There are many different vehicle frames (types), and within the types there are many variations. -Some of the types, along with the use cases for which they are most suited are listed below. +드론에는 다양한 프레임(기체 형태)이 있으며, 각 형태 내에도 여러 가지 변형이 존재합니다. +아래는 드론의 대표적인 형태들과 각 형태에 가장 적합한 활용 사례들입니다. -- [Multicopters](../frames_multicopter/index.md) — Multi-rotors offer precision hovering and vertical takeoff, at the cost of shorter and generally slower flight. - They are the most popular type of flying vehicle, in part because they are easy to assemble, and PX4 has modes that make them easy to fly and very suitable as a camera platform. -- [Helicopters](../frames_helicopter/index.md) — Helicopters similar benefits to Multicopters but are mechanically more complex and more efficient. - They are also much harder to fly. -- [Planes (Fixed-wing)](../frames_plane/index.md) — Fixed-wing vehicles offer longer and faster flight than multicopters, and hence better coverage for ground surveys etc. - However they are harder to fly and land than multicopters, and aren't suitable if you need to hover or fly very slowly (e.g. when surveying vertical structures). -- [VTOL](../frames_vtol/index.md) (Vertical Takeoff and Landing) - Hybrid Fixed-wing/Multicopter vehicles offer the best of both worlds: take off in vertical mode and hover like a multicopter but transition to forward flight like an airplane to cover more ground. - VTOL are often more expensive than either multicopters and fixed-wing aircraft, and harder to build and tune. - They come in a number of types: tiltrotors, tailsitters, quadplanes etc. -- [Airships](../frames_airship/index.md)/[Balloons](../frames_balloon/index.md) — Lighter-than-air vehicles that typically offer high altitude long duration flight, often at the cost of having limited (or no) control over speed and direction of flight. -- [Rovers](../frames_rover/index.md) — Car-like ground vehicles. - They are simple to control and often fun to use. - They can't travel as fast as most aircraft, but can carry heavier payloads, and don't use much power when still. -- **Boats** — Water-surface vehicles. -- [Submersibles](../frames_sub/index.md) — Underwater vehicles. +- [멀티콥터(Multicopters)](../frames_multicopter/index.md) — 멀티로터는 정밀한 호버링과 수직 이착륙이 가능하지만, 비행 시간이 짧고 속도도 일반적으로 느린 편입니다. + 이들은 가장 인기 있는 비행체 유형 중 하나로, 조립이 쉽고 PX4가 제공하는 다양한 비행 모드를 통해 조종이 간편하며, 카메라 플랫폼으로도 매우 적합하기 때문입니다. +- [헬리콥터](../frames_helicopter/index.md) — 헬리콥터는 멀티콥터와 유사한 이점을 제공하지만, 기계적으로 더 복잡하고 더 효율적입니다. + 이들은 또한 조종이 훨씬 더 어렵습니다. +- [비행기 (고정익)](../frames_plane/index.md) — 고정익 기체는 멀티콥터보다 더 오래, 더 빠르게 비행할 수 있어 지상 조사 등에서 더 넓은 범위를 커버할 수 있습니다.\ + 하지만 멀티콥터보다 조종과 착륙이 더 어렵고, 공중에 머무르거나 아주 느리게 비행해야 하는 경우(예: 수직 구조물 조사)에는 적합하지 않습니다. +- [VTOL](../frames_vtol/index.md) (수직 이착륙) — 고정익/멀티콥터 하이브리드 기체는 두 가지 방식의 장점을 모두 제공합니다. 멀티콥터처럼 수직으로 이륙하고 호버링할 수 있으며, 비행 중에는 비행기처럼 전진 비행으로 전환해 더 넓은 지역을 커버할 수 있습니다. + VTOL은 일반적으로 멀티콥터나 고정익 항공기보다 더 비싸며, 제작과 튜닝도 더 어렵습니다. + VTOL은 여러 형태로 나뉘며, 대표적으로 틸트로터(tiltrotor), 테일시터(tailsitter), 쿼드플레인(quadplane) 등이 있습니다. +- [에어십](../frames_airship/index.md)/[기구](../frames_balloon/index.md) — 공기보다 가벼운 비행체로, 일반적으로 고고도에서 오랜 시간 비행이 가능하지만, 속도나 비행 방향에 대한 제어가 제한되거나 불가능한 경우가 많습니다. +- [로버](../frames_rover/index.md) — 자동차와 유사한 지상 주행형 비행체입니다. + 조작이 간단하고 사용하기에 재미있는 경우가 많습니다. + 대부분의 항공기만큼 빠르게 이동할 수는 없지만, 더 무거운 화물을 운반할 수 있으며 정지 상태에서는 전력을 거의 소모하지 않습니다. +- **보트** — 수면 위를 이동하는 수상 차량입니다. +- [잠수정(Submersibles)](../frames_sub/index.md) — 수중에서 운용되는 차량입니다. 더 자세한 정보는 다음을 참고하십시오. -- [Vehicle Types & Setup](../airframes/index.md) -- [Airframe setup](../config/airframe.md) -- [Airframe Reference](../airframes/airframe_reference.md). +- [비행체 유형 및 설정](../airframes/index.md) +- [기체 프레임 설정](../config/airframe.md) +- [기체 프레임 참조](../airframes/airframe_reference.md) ## 자동조종장치 자율비행장치(오토파일럿)는 드론의 두뇌에 해당하는 장치입니다. -It minimally consists of _flight stack_ software running on a real time OS ("RTOS") on _flight controller_ (FC) hardware. -The flight stack provides essential stabilisation and safety features, and usually also some level of pilot assistance for manual flight and automating common tasks, such as taking off, landing, and executing predefined missions. +기본적으로 드론 시스템은 실시간 운영체제("RTOS")가 탑재된 비행 컨트롤러(FC)에서 비행 제어용 소프트웨어(비행 스택)를 실행하는 구조로 이루어져 있습니다. +비행 스택은 기본적인 안정화와 안전 기능을 제공하며, 일반적으로 수동 비행 시 조종을 도와주는 보조 기능과 함께 이륙, 착륙, 미리 정해진 임무 수행 같은 작업을 자동으로 실행할 수 있도록 지원합니다. -Some autopilots also include a general-purpose computing system that can provide "higher level" command and control, and that can support more advanced networking, computer vision, and other features. -This might be implemented as a separate [companion computer](#offboard-companion-computer), but in future it is increasingly likely to be a fully integrated component. +일부 자율 비행 장치는 고차원 명령과 제어를 수행할 수 있는 범용 컴퓨팅 시스템을 함께 탑재하고 있어, 보다 정교한 네트워킹, 컴퓨터 비전, 기타 고급 기능들을 지원할 수 있습니다. +이 기능은 별도의 [보조 컴퓨터](#offboard-companion-computer)로 구현될 수도 있지만, 앞으로는 이러한 시스템이 하나로 통합된 구성 요소로 점점 더 많이 탑재될 가능성이 큽니다. ## PX4 자동비행장치 -[PX4](https://px4.io/) is powerful open source autopilot _flight stack_ running on the NuttX RTOS. +[PX4](https://px4.io/)는 NuttX 실시간 운영체제(RTOS) 위에서 구동되는 강력한 오픈소스 자율비행 소프트웨어(flight stack)입니다. PX4의 주요 특징들은 아래와 같습니다. -- Supports many different vehicle frames/types, including: [multicopters](../frames_multicopter/index.md), [fixed-wing aircraft](../frames_plane/index.md) (planes), [VTOLs](../frames_vtol/index.md) (hybrid multicopter/fixed-wing), [ground vehicles](../frames_rover/index.md), and [underwater vehicles](../frames_sub/index.md). +- 다양한 기체 프레임/유형을 지원하며, 다음을 포함합니다: [멀티콥터](../frames_multicopter/index.md), [고정익 항공기](../frames_plane/index.md) (비행기), [수직 이착륙기(VTOL)](../frames_vtol/index.md) (멀티콥터와 고정익의 하이브리드), [지상 차량](../frames_rover/index.md), [수중 차량](../frames_sub/index.md) 등. - Great choice of drone components for [flight controller](#flight-controller), [sensors](#sensors), [payloads](#payloads), and other peripherals. - Flexible and powerful [flight modes](#flight-modes) and [safety features](#safety-settings-failsafe). - Robust and deep integration with [companion computers](#offboard-companion-computer) and [robotics APIs](../robotics/index.md) such as [ROS 2](../ros2/user_guide.md) and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html). PX4 is a core part of a broader drone platform that includes the [QGroundControl](#qgc) ground station, [Pixhawk hardware](https://pixhawk.org/), and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html) for integration with companion computers, cameras and other hardware using the MAVLink protocol. -PX4 is supported by the [Dronecode Project](https://www.dronecode.org/). +PX4 is supported by the [Dronecode Project](https://dronecode.org/). ## Ground Control Stations @@ -76,7 +77,7 @@ A subset of the products that are known to work with PX4 are listed below. The Dronecode GCS software is called [QGroundControl](https://qgroundcontrol.com/) ("QGC"). It runs on Windows, Android, MacOS or Linux hardware, and supports a wide range of screen form factors. -You can download it (for free) from [here](https://qgroundcontrol.com/downloads/). +You can download it (for free) from [here](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/getting_started/download_and_install.html). ![QGC Main Screen](../../assets/concepts/qgc_fly_view.png) diff --git a/docs/ko/index.md b/docs/ko/index.md index c688fb6081..0e579b2428 100644 --- a/docs/ko/index.md +++ b/docs/ko/index.md @@ -133,9 +133,9 @@ The calendar default timezone is Central European Time (CET). ## 운영 방법 -The PX4 flight stack is hosted under the governance of the [Dronecode Project](https://www.dronecode.org/). +The PX4 flight stack is hosted under the governance of the [Dronecode Project](https://dronecode.org/). -Dronecode Logo Linux Foundation Logo +Dronecode Logo Linux Foundation Logo
 
diff --git a/docs/ko/releases/main.md b/docs/ko/releases/main.md index cff6ee6e56..99c333229e 100644 --- a/docs/ko/releases/main.md +++ b/docs/ko/releases/main.md @@ -84,7 +84,7 @@ Please continue reading for [upgrade instructions](#upgrade-guide). ### 탐사선 -- TBD +- Removed deprecated rover module ([PX4-Autopilot#25054](https://github.com/PX4/PX4-Autopilot/pull/25054)). ### ROS 2 diff --git a/docs/ko/sim_flightgear/index.md b/docs/ko/sim_flightgear/index.md index 80de0eb9a7..18cf1ec945 100644 --- a/docs/ko/sim_flightgear/index.md +++ b/docs/ko/sim_flightgear/index.md @@ -68,7 +68,7 @@ These instructions were tested on Ubuntu 18.04 Setting the permissions is required because the PX4-FlightGear-Bridge puts the communication definition file here. -Additional installation instructions can be found on [FlightGear wiki](http://wiki.flightgear.org/Howto:Install_Flightgear_from_a_PPA). +Additional installation instructions can be found on [FlightGear wiki](https://wiki.flightgear.org/Howto:Install_Flightgear_from_a_PPA). ## Running the Simulation diff --git a/docs/ko/sim_flightgear/multi_vehicle.md b/docs/ko/sim_flightgear/multi_vehicle.md index a86be0d750..4e4d8701c6 100644 --- a/docs/ko/sim_flightgear/multi_vehicle.md +++ b/docs/ko/sim_flightgear/multi_vehicle.md @@ -21,7 +21,7 @@ It is suitable for testing multi-vehicle support in _QGroundControl_, [MAVSDK](h To start multiple instances (on separate ports and IDs): -1. Checkout the [PX4 branch that supports multiple vehicles](https://github.com/ThunderFly-aerospace/PX4Firmware/tree/flightgear-multi) (at ThunderFly-aerospace): +1. Checkout the [PX4 branch that supports multiple vehicles](https://github.com/ThunderFly-aerospace/PX4-Autopilot/tree/flightgear-multi) (at ThunderFly-aerospace): ```sh git clone https://github.com/ThunderFly-aerospace/PX4Firmware.git diff --git a/docs/ko/sim_gazebo_classic/index.md b/docs/ko/sim_gazebo_classic/index.md index 6bd6d2193b..4d0a1784e4 100644 --- a/docs/ko/sim_gazebo_classic/index.md +++ b/docs/ko/sim_gazebo_classic/index.md @@ -533,7 +533,7 @@ To disable lockstep in: ## Extending and Customizing To extend or customize the simulation interface, edit the files in the `Tools/simulation/gazebo/sitl_gazebo` folder. -The code is available on the [sitl_gazebo repository](https://github.com/PX4/PX4-SITL_gazebo) on Github. +The code is available on the [sitl_gazebo repository](https://github.com/PX4/PX4-SITL_gazebo-classic) on GitHub. :::info The build system enforces the correct GIT submodules, including the simulator. diff --git a/docs/ko/sim_jmavsim/index.md b/docs/ko/sim_jmavsim/index.md index 01ad1cca18..e64a540c29 100644 --- a/docs/ko/sim_jmavsim/index.md +++ b/docs/ko/sim_jmavsim/index.md @@ -30,7 +30,7 @@ Follow the instructions below to install jMAVSim on macOS. To setup the environment for [jMAVSim](../sim_jmavsim/index.md) simulation: 1. Install a recent version of Java (e.g. Java 15). - You can download [Java 15 (or later) from Oracle](https://www.oracle.com/java/technologies/javase-downloads.html) or use [Eclipse Temurin](https://adoptium.net): + You can download [Java 15 (or later) from Oracle](https://www.oracle.com/java/technologies/downloads/?er=221886) or use [Eclipse Temurin](https://adoptium.net): ```sh brew install --cask temurin @@ -314,7 +314,7 @@ and comment out the line indicated below: ``` For more info, check [this GitHub issue](https://github.com/PX4/PX4-Autopilot/issues/9557). -A contributor found the fix in [askubuntu.com](https://askubuntu.com/questions/695560). +A contributor found the fix in [askubuntu.com](https://askubuntu.com/questions/695560/assistive-technology-not-found-awterror). ### Exception in thread "main" java.lang.UnsupportedClassVersionError diff --git a/docs/ko/telemetry/crsf_telemetry.md b/docs/ko/telemetry/crsf_telemetry.md index ae50c40943..b34c670497 100644 --- a/docs/ko/telemetry/crsf_telemetry.md +++ b/docs/ko/telemetry/crsf_telemetry.md @@ -37,7 +37,7 @@ Then you can _bind_ the transmitter and receiver together. Instructions for the steps above are covered in -- [TBS Crossfire Manual](https://www.team-blacksheep.com/tbs-crossfire-manual.pdf) +- [TBS Crossfire Manual](https://www.team-blacksheep.com/media/files/tbs-crossfire-manual.pdf) - [Express LRS: QuickStart](https://www.expresslrs.org/quick-start/getting-started/) ### 배선 @@ -148,7 +148,7 @@ RC Controllers that support TBS Crossfire and ExpressLRS TX modules: - [FrSky Taranis X9D Plus](https://www.frsky-rc.com/product/taranis-x9d-plus-2/) has an external module bay that can be used with TBS or ExpressLRS transmitter modules that are "JR module bay" compatible. You will need to install OpenTX software, which supports CRSF, and enable the external module and CRSF. -- [Radiomaster TX16S](https://www.radiomasterrc.com/collections/tx16s-mkii) has an internal ExpressLRS transmitter module. +- [Radiomaster TX16S Mk II](https://radiomasterrc.com/products/tx16s-mark-ii-radio-controller) has an internal ExpressLRS transmitter module. It also has an external module bay that can be used with TBS or ExpressLRS transmitter modules that are "JR module bay" compatible. It runs both OpenTX and EdgeTx software, either of which can support CRSF. @@ -186,7 +186,7 @@ Receivers: ## 텔레메트리 메시지 -The supported telemetry messages and their source are listed below (this table is reproduced from the [TBS Crossfire Manual: "Available sensors with OpenTX"](https://www.team-blacksheep.com/tbs-crossfire-manual.pdf)). +The supported telemetry messages and their source are listed below (this table is reproduced from the [TBS Crossfire Manual: "Available sensors with OpenTX"](https://www.team-blacksheep.com/media/files/tbs-crossfire-manual.pdf)). | Datapoint | 설명 | Data source | | --------- | --------------------------------------------------------------------- | -------------------------------- | @@ -215,7 +215,7 @@ The supported telemetry messages and their source are listed below (this table i ## See Also -- [TBS Crossfire Manual](https://www.team-blacksheep.com/tbs-crossfire-manual.pdf) +- [TBS Crossfire Manual](https://www.team-blacksheep.com/media/files/tbs-crossfire-manual.pdf) - [ExpressLRS Documentation](https://www.expresslrs.org/quick-start/getting-started/) - [FrSky Telemetry](../peripherals/frsky_telemetry.md) - [Radio Control Setup](../config/radio.md) diff --git a/docs/ko/telemetry/esp8266_wifi_module.md b/docs/ko/telemetry/esp8266_wifi_module.md index 0b005c3455..cb4c789871 100644 --- a/docs/ko/telemetry/esp8266_wifi_module.md +++ b/docs/ko/telemetry/esp8266_wifi_module.md @@ -16,8 +16,7 @@ ESP8266 모듈은 여러 곳에서 쉽게 구매할 수 있습니다. 3.3V 사용 모듈: -- [WRL-17146](https://www.sparkfun.com/products/13678) (Sparkfun) -- [AI Cloud](https://us.gearbest.com/boards-shields/pp_009604906563.html) - discontinued (GearBeast) +- [WRL-17146](https://www.sparkfun.com/wifi-module-esp8266-4mb-flash.html) (Sparkfun) 5.0V 사용 모듈: diff --git a/docs/ko/telemetry/rfd900_telemetry.md b/docs/ko/telemetry/rfd900_telemetry.md index 6012b29e5d..bbb11ce4b6 100644 --- a/docs/ko/telemetry/rfd900_telemetry.md +++ b/docs/ko/telemetry/rfd900_telemetry.md @@ -20,4 +20,4 @@ They can therefore be used in a "plug-n-play" way with most [Pixhawk Series](../ - [store.rfdesign.com.au](https://store.rfdesign.com.au/radio-modems/): - [RFD 900+ Modem](https://store.rfdesign.com.au/rfd-900p-modem/) - [RFD 868x Modem (EU)](https://store.rfdesign.com.au/rfd868x-eu-hs-8517-62-00-90/) - - [RFD900x](https://store.rfdesign.com.au/rfd-900x-modem-hs-8517-62-00-90/) + - [RFD900x](https://store.rfdesign.com.au/rfd-900x-modem/) diff --git a/docs/ko/telemetry/tfsik_telemetry.md b/docs/ko/telemetry/tfsik_telemetry.md index e9af14122a..01f6ec60d5 100644 --- a/docs/ko/telemetry/tfsik_telemetry.md +++ b/docs/ko/telemetry/tfsik_telemetry.md @@ -10,7 +10,7 @@ The modem is plug-and-play with flight controllers using a JST-GH UART interface ## 구매처 -- [TFSIK01A on Tindie](https://www.tindie.com/products/34682/) +- [TFSIK01A on Tindie](https://www.tindie.com/products/thunderfly/tfsik01-high-performance-uav-telemetry-modem/) - Directly from [ThunderFly](https://www.thunderfly.cz/contact-us.html) ([sale@thunderfly.cz](mailto:sale@thunderfly.cz)) ## 특징 diff --git a/docs/ko/test_and_ci/docker.md b/docs/ko/test_and_ci/docker.md index 3e4bc144b0..8d650a97a0 100644 --- a/docs/ko/test_and_ci/docker.md +++ b/docs/ko/test_and_ci/docker.md @@ -16,16 +16,16 @@ PX4 containers are currently only supported on Linux (if you don't have Linux yo Do not use `boot2docker` with the default Linux image because it contains no X-Server. ::: -[Install Docker](https://docs.docker.com/installation/) for your Linux computer, preferably using one of the Docker-maintained package repositories to get the latest stable version. You can use either the _Enterprise Edition_ or (free) _Community Edition_. +[Install Docker](https://docs.docker.com/get-started/get-docker/) for your Linux computer, preferably using one of the Docker-maintained package repositories to get the latest stable version. You can use either the _Enterprise Edition_ or (free) _Community Edition_. -For local installation of non-production setups on _Ubuntu_, the quickest and easiest way to install Docker is to use the [convenience script](https://docs.docker.com/install/linux/docker-ce/ubuntu/#install-using-the-convenience-script) as shown below (alternative installation methods are found on the same page): +For local installation of non-production setups on _Ubuntu_, the quickest and easiest way to install Docker is to use the [convenience script](https://docs.docker.com/engine/install/ubuntu/#install-using-the-convenience-script) as shown below (alternative installation methods are found on the same page): ```sh curl -fsSL get.docker.com -o get-docker.sh sudo sh get-docker.sh ``` -The default installation requires that you invoke _Docker_ as the root user (i.e. using `sudo`). However, for building the PX4 firmware we suggest to [use docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user). 그렇게하면, docker를 사용한 후 빌드 폴더를 관리자가 소유하지 않습니다. +The default installation requires that you invoke _Docker_ as the root user (i.e. using `sudo`). However, for building the PX4 firmware we suggest to [use docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user). 그렇게하면, docker를 사용한 후 빌드 폴더를 관리자가 소유하지 않습니다. ```sh # Create docker group (may not be required) diff --git a/docs/ko/test_and_ci/fuzz_tests.md b/docs/ko/test_and_ci/fuzz_tests.md new file mode 100644 index 0000000000..5afba73dd8 --- /dev/null +++ b/docs/ko/test_and_ci/fuzz_tests.md @@ -0,0 +1,70 @@ +# Fuzz Tests + +Fuzz tests are a generalised form of [unit test](../test_and_ci/unit_tests.md) that run code against a large number of random inputs. +This helps to ensure that the code is robust against any input, not just those expected by the developer. + +They can be written like unit tests with possible assertions (`EXPECT_EQ`, etc), and have a set of input parameters. +The fuzzer then tries to find inputs that cause the code to crash (with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html) enabled automatically) or trigger an assertion. + +The tests are run as part of normal unit tests, and in a more comprehensive fuzzing mode test. +For more information see [Running Fuzz Tests](#running-fuzz-tests) below. + +## Writing a Fuzz Test + +To write a fuzz test: + +1. Start by writing a "normal" [functional test](../test_and_ci/unit_tests.md#functional-test). +2. Make sure the file name contains `fuzz` (lower case). + For example `my_driver_fuzz_tests.cpp`. +3. Add one or more fuzz tests to the file. + 예: + + ```cpp + #include + #include + + void myDriverNeverCrashes(const std::string& s) { + MyDriver driver; + driver.handleInput(s); + } + FUZZ_TEST(MyDriverFuzzTests, myDriverNeverCrashes); + ``` + +The file can also contain normal tests. +For more information, see https://github.com/google/fuzztest. + +A complete example in the PX4 repository can be found in the [septentrio driver](https://github.com/PX4/PX4-Autopilot/blob/main/src/drivers/gnss/septentrio/septentrio_fuzz_tests.cpp). + +## Running Fuzz Tests + +Fuzz tests can be run in two modes: + +- As part of normal unit tests with `make tests`. + This will only create a small number of inputs and not use coverage information. +- In fuzzing mode: this runs a single fuzz test with coverage information over a longer period of time (either fixed or indefinitely). + The fuzzer will try to find inputs that cover all reachable code paths. + It requires compilation with Clang and can be run with the following commands: + + ```sh + rm -rf build/px4_sitl_tests + export CC=clang + export CXX=clang++ + make tests TESTFILTER=__no_tests__ + cd build/px4_sitl_tests + ./functional- --fuzz= + ``` + +## Seeds + +Depending on the code complexity, it might be hard for the fuzzer to find inputs that pass certain conditions. +For this it is possible to provide one or more seeds, which the fuzzer will use as first inputs. +[The google documentation](https://github.com/google/fuzztest/blob/main/doc/fuzz-test-macro.md#initial-seeds-initial-seeds) contains more details. + +You can also use the `FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION` macro for conditional code compilation, for example to exclude CRC checks. + +More information about efficient fuzzing can be found on [this page](https://chromium.googlesource.com/chromium/src/+/main/testing/libfuzzer/efficient_fuzzing.md). + +## CI + +Fuzz tests are run as part of the normal unit tests in CI for each pull request. +In addition, the fuzz tests are run daily for 15 minutes on the main branch. diff --git a/docs/ko/test_and_ci/unit_tests.md b/docs/ko/test_and_ci/unit_tests.md index 2d20e85903..a4eb12d9fd 100644 --- a/docs/ko/test_and_ci/unit_tests.md +++ b/docs/ko/test_and_ci/unit_tests.md @@ -23,7 +23,7 @@ PX4에서는 단위 테스트 작성에 필요한 몇가지 수단을 제공합 Tests can be run via `make tests`, after which you will find the binary in `build/px4_sitl_test/unit-MyNewUnit`. 디버거에서 바로 실행할 수 있습니다. -## GTest 기능 테스트 작성 +## Writing a GTest Functional Test {#functional-test} GTest 기능 시험은 매개변수, uORB 메세지, 고급 GTest 기능에 따라 테스트할 테스트 단위 또는 구성 요소가 있을 때 활용해야합니다. 게다가, 기능 테스트 과정에서 자체 STL 데이터 구조를 사용할 수 있습니다(플랫폼간 차이에 유의해야 함. 예: maxOS, Linux). @@ -178,3 +178,10 @@ make tests TESTFILTER= - `make tests TESTFILTER=unit` only run GTest unit tests - `make tests TESTFILTER=sitl` only run simulation tests - `make tests TESTFILTER=Attitude` only run the `AttitudeControl` test + +## Fuzz Testing + +Fuzz tests are a generalised form of unit test that ensures code is robust against any input. +They are run as part of the unit tests, and also more extensively in their own testing mode. + +For more information see [Fuzz Tests](../test_and_ci/fuzz_tests.md).