fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-21 08:23:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix all end of file newlines

Browse Source 
Note: Some files are autogenerated and I did not yet
go through each source of generation to fix it there.
Instead I adjusted the filter to only exclude those
such that we can fix things in steps.
This commit is contained in:
Matthias Grob
2025-06-26 11:03:23 -07:00
committed by Ramon Roche
parent e9bac962ab
commit 2bc04f91f8
90 changed files with 173 additions and 193 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/actuators/index.md
+1 -1
View File
@@ -9,4 +9,4 @@ This section contains topics about the core actuators used for flight control (E
## See Also
- [Peripherals](../peripherals/index.md) - includes non-core actuators such as grippers, parachutes, etc.
- [Peripherals](../peripherals/index.md) - includes non-core actuators such as grippers, parachutes, etc.
docs/en/advanced_config/parameter_reference.md
-1
View File
@@ -40437,4 +40437,3 @@ Skip the controller.
Reboot | minValue | maxValue | increment | default | unit
--- | --- | --- | --- | --- | ---
  | | | | 0 |
docs/en/airframes/airframe_reference.md
-1
View File
@@ -797,4 +797,3 @@ div.frame_variant td, div.frame_variant th {
</tbody>
</table>
</div>
docs/en/assembly/assembly_vtol.md
+1 -1
View File
@@ -4,4 +4,4 @@ frame: VTOL
newEditLink: en/assembly/_assembly.md
---
<!--@include: _assembly.md-->
<!--@include: _assembly.md-->
docs/en/assembly/index.md
+1 -1
View File
@@ -3,4 +3,4 @@ frame: General
newEditLink: en/assembly/_assembly.md
---
<!--@include: _assembly.md-->
<!--@include: _assembly.md-->
docs/en/camera/index.md
+1 -1
View File
@@ -17,4 +17,4 @@ If a camera does not support this prototol, a [camera manager](../camera/mavlink
## See Also
- [Gimbal (Camera Mount)](../advanced/gimbal_control.md)
- [Camera Integration/Architecture](../camera/camera_architecture.md) (PX4 Developers)
- [Camera Integration/Architecture](../camera/camera_architecture.md) (PX4 Developers)
docs/en/complete_vehicles/betafpv_beta75x.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/betafpv_beta75x" />
<Redirect to="../complete_vehicles_mc/betafpv_beta75x" />
docs/en/complete_vehicles/crazyflie2.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/crazyflie2" />
<Redirect to="../complete_vehicles_mc/crazyflie2" />
docs/en/complete_vehicles/crazyflie21.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/crazyflie21" />
<Redirect to="../complete_vehicles_mc/crazyflie21" />
docs/en/complete_vehicles/holybro_kopis2.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/holybro_kops2" />
<Redirect to="../complete_vehicles_mc/holybro_kops2" />
docs/en/complete_vehicles/intel_aero.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/intel_aero" />
<Redirect to="../complete_vehicles_mc/intel_aero" />
docs/en/complete_vehicles/mindracer210.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/mindracer210" />
<Redirect to="../complete_vehicles_mc/mindracer210" />
docs/en/complete_vehicles/mindracer_BNF_RTF.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/mindracer_BNF_RTF" />
<Redirect to="../complete_vehicles_mc/mindracer_BNF_RTF" />
docs/en/complete_vehicles/modalai_starling.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/modalai_starling" />
<Redirect to="../complete_vehicles_mc/modalai_starling" />
docs/en/complete_vehicles/nanomind110.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/nanomind110" />
<Redirect to="../complete_vehicles_mc/nanomind110" />
docs/en/complete_vehicles/px4_vision_kit.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../complete_vehicles_mc/px4_vision_kit" />
<Redirect to="../complete_vehicles_mc/px4_vision_kit" />
docs/en/complete_vehicles_vtol/index.md
+1 -1
View File
@@ -33,4 +33,4 @@ These may or may not be updatable to run "vanilla" PX4.
## See Also
- [Complete Vehicles (Fixed-Wing)](../complete_vehicles_fw/index.md)
- [Complete Vehicles (MC)](../complete_vehicles_mc/index.md)
- [Complete Vehicles (MC)](../complete_vehicles_mc/index.md)
docs/en/config/safety_simulation.md
-1
View File
@@ -30,4 +30,3 @@ make run_failsafe_web_server
<script setup>
import { withBase } from 'vitepress';
</script>
docs/en/dev_log/logging.md
+1 -1
View File
@@ -188,4 +188,4 @@ There are different clients that support ulog streaming:
## See Also
- [Encrypted logging](../dev_log/log_encryption.md)
- [Encrypted logging](../dev_log/log_encryption.md)
docs/en/dev_setup/qgc_daily_build.md
+1 -1
View File
@@ -6,4 +6,4 @@ The QGroundControl _Daily Build_ includes development tools that are hidden in r
It should be used instead of the stable release when working with new code forked from the PX4 `main` branch.
- [Download daily builds](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/daily_builds.html)
- [Download daily builds](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/releases/daily_builds.html)
docs/en/flight_controller/ark_fpv.md
-2
View File
@@ -86,5 +86,3 @@ See the documentation [Ark Electronics GitBook](https://arkelectron.gitbook.io/a
## Pinout
See the [DS-10 Pixhawk Autopilot Bus Standard](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-fpv/pinout)
docs/en/flight_modes/index.md
+1 -1
View File
@@ -12,4 +12,4 @@ For information about flight modes available to specific frames see the followin
::: info
The mode sub-topics in this section contain information that is common to all vehicles, but may not be relevant to the normal/default setup.
Generally you should see the vehicle-specific topics first, and navigate to these generalized topics when it becomes relevant.
:::
:::
docs/en/flight_modes_fw/index.md
+1 -1
View File
@@ -55,4 +55,4 @@ Select the mode-specific sidebar topics for detailed technical information.
- [Basic Configuration > Flight Modes](../config/flight_mode.md) - How to map RC control switches to specific flight modes
- [Flight Modes (Multicopter)](../flight_modes_mc/index.md)
- [Flight Modes (VTOL)](../flight_modes_vtol/index.md)
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
docs/en/flight_modes_mc/index.md
-1
View File
@@ -54,4 +54,3 @@ Select the mode-specific sidebar topics for more detailed technical information.
- [Flight Modes (Fixed-Wing)](../flight_modes_fw/index.md)
- [Flight Modes (VTOL)](../flight_modes_vtol/index.md)
- [Drive Modes (Rover)](../flight_modes_rover/index.md)
docs/en/flight_modes_vtol/offboard.md
-1
View File
@@ -1,4 +1,3 @@
<Redirect to="../flight_modes/offboard" />
# Offboard Mode (VTOL)
docs/en/flying/basic_flying.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../flying/basic_flying_mc" />
<Redirect to="../flying/basic_flying_mc" />
docs/en/frames_multicopter/holybro_x500v2_pixhawk6c.md
+4 -4
View File
@@ -57,7 +57,7 @@ This topic provides full instructions for building the [Holybro X500 V2 ARF Kit]
1. To assemble the landing gear, loosen the pre-assembled screws of the Landing Gear-Cross Bar and insert the Landing Gear-Vertical Pole and fasten the same.
[![Assembly8](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/assembly8.png)](https://youtu.be/mU4vm4zyjcY)
[![Assembly9](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/assembly9.png)](https://youtu.be/7REaF3YAqLg)
1. Use the Socket Cap Screw M3*8 to screw the landing gears to the bottom plate
@@ -105,7 +105,7 @@ Note that the ESC connectors are color-coded and must be inserted in the PWM out
[![Assembly16](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/assembly16.png)](https://youtu.be/GOTqmjq9_3s)
1. While inserting the top plate on top of this the 3 piece assembly (bottom plate, top plate & arms) have to screwed using Socket Cap Screw M3*38 and Flange Locknut M3.
1. While inserting the top plate on top of this the 3 piece assembly (bottom plate, top plate & arms) have to screwed using Socket Cap Screw M3*38 and Flange Locknut M3.
1. Hold one side using the mini cross wrench provided in the developer kit.
[![Assembly17](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/assembly17.png)](https://youtu.be/2rcNVekJQd0)
@@ -133,7 +133,7 @@ The following parts can be placed as per usual.
1. Assemble the GPS by following the video.
[![Assembly20](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/assembly20.png)](https://youtu.be/aiFxVJFjlos)
This guide uses the GPS mount location suggested in Holybro’s guide.
1. Screw the GPS mount’s bottom end on the payload holder side using Locknut M3 & Screw M3*10
@@ -213,4 +213,4 @@ For instructions on how, start from [Auto-tune](../config/autotune_mc.md).
## Acknowledgements
This build log was contributed by Akshata and Hamish Willee with many thanks to Holybro and Dronecode for Hardware and technical support.
This build log was contributed by Akshata and Hamish Willee with many thanks to Holybro and Dronecode for Hardware and technical support.
docs/en/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md
+3 -4
View File
@@ -49,7 +49,7 @@ For example, you might wire it up like this example (orientation as if "sitting
Port | Connection
--- | ---
--- | ---
MAIN 1 | Front right motor (CCW)
MAIN 2 | Back left motor (CCW)
MAIN 3 | Front left motor (CW)
@@ -60,7 +60,7 @@ AUX 3 | Elevator
AUX 4 | Rudder
AUX 5 | Throttle
For further instructions on wiring and configurations please see:
For further instructions on wiring and configurations please see:
[Standard VTOL Wiring and Configuration](../config_vtol/vtol_quad_configuration.md). <!-- replace with Pixhawk Wiring Quickstart -->
## Airframe Configuration
@@ -72,7 +72,7 @@ For further instructions on wiring and configurations please see:
1. Configure the outputs and geometry following the instructions in [Actuators Configuration](../config/actuators.md)
1. The default parameters are often sufficient for stable flight. For more detailed tuning information see [Standard VTOL Wiring and Configuration](../config_vtol/vtol_quad_configuration.md).
After you finish calibration the VTOL is ready to fly.
After you finish calibration the VTOL is ready to fly.
## Video
@@ -82,4 +82,3 @@ After you finish calibration the VTOL is ready to fly.
## Support
If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
docs/en/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md
+5 -6
View File
@@ -43,7 +43,7 @@ The image below depicts the parts required for one wing.
![QuadRanger Parts](../../assets/airframes/vtol/quadranger_rangerex_pixhawk/quadranger_vtol_parts_for_one_wing.jpg)
The tools required for the conversion are;
- A Dremel or similar rotary tool
@@ -58,7 +58,7 @@ The tools required for the conversion are;
## Wing conversion
::: info
Please note that the conversion in this build log is performed on a wing that shows damage from a previous conversion.
Please note that the conversion in this build log is performed on a wing that shows damage from a previous conversion.
:::
Cut both 800mm square carbon tubes to a length of 570mm and 230mm.
@@ -87,7 +87,7 @@ When using the Afro ESC be sure to connect at least signal and ground wire.
![QuadRanger motor and esc](../../assets/airframes/vtol/quadranger_rangerex_pixhawk/quadranger_vtol_motor_and_esc.jpg)
## Wiring
## Wiring
The outputs of Pixhawk should be wired like this (orientation as seen
like "sitting in the plane").
@@ -99,7 +99,7 @@ MAIN 2 | Back left motor, CCW
MAIN 3 | Front left motor, CW
MAIN 4 | Back right motor, CW
AUX 1 | Left aileron
AUX 2 | Right aileron
AUX 2 | Right aileron
AUX 3 | Elevator
AUX 4 | Rudder
AUX 5 | Throttle
@@ -108,7 +108,7 @@ AUX 5 | Throttle
::: 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)
:::
For further instructions on wiring and configurations please see: [Standard VTOL Wiring and Configuration](../config_vtol/vtol_quad_configuration.md)
@@ -122,4 +122,3 @@ Configure the frame as shown in QGroundControl below (do not forget to click **A
## Support
If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
docs/en/getting_started/flight_controller_selection.md
-1
View File
@@ -39,4 +39,3 @@ Similarly, PX4 can also run natively Raspberry Pi (this approach is not generall
PX4 is available on many popular commercial drone products, including some that ship with PX4 and others that can be updated with PX4 (allowing you to add mission planning and other PX4 Flight modes to your vehicle).
For more information see [Complete Vehicles](../complete_vehicles/index.md).
docs/en/getting_started/flight_modes.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../getting_started/px4_basic_concepts" />
<Redirect to="../getting_started/px4_basic_concepts" />
docs/en/getting_started/vehicle_status.md
+1 -1
View File
@@ -9,4 +9,4 @@ The LED, tune, and GCS notifications are linked below:
* [LED Meanings](../getting_started/led_meanings.md)
* [Tune/Sound Meanings](../getting_started/tunes.md)
* [QGroundControl Flight-Readiness Status](../flying/pre_flight_checks.md)
* [QGroundControl Flight-Readiness Status](../flying/pre_flight_checks.md)
docs/en/mavlink/streaming_messages.md
-1
View File
@@ -254,4 +254,3 @@ In order to avoid clogging communications links with messages that aren't needed
If you needed, a GCS or other MAVLink API can request that particular messages are streamed at a particular rate using [MAV_CMD_SET_MESSAGE_INTERVAL](https://mavlink.io/en/messages/common.html#MAV_CMD_SET_MESSAGE_INTERVAL).
A particular message can be requested just once using [MAV_CMD_REQUEST_MESSAGE](https://mavlink.io/en/messages/common.html#MAV_CMD_REQUEST_MESSAGE).
docs/en/middleware/uorb_graph.md
-1
View File
@@ -29,4 +29,3 @@ The graph has the following properties:
You can also zoom the image.
- The *Preset* selection list allows you to refine the list of modules that are shown.
- The *Search* box can be used to find particular modules/topics (topics that are not selected by the search are greyed-out).
docs/en/modules/module_template.md
+2 -3
View File
@@ -13,7 +13,7 @@ All the things learned in the [First Application Tutorial](../modules/hello_sky.
## Work Queue Task
PX4-Autopilot contains a template for writing a new application (module) that runs as a *work queue task*:
PX4-Autopilot contains a template for writing a new application (module) that runs as a *work queue task*:
[src/examples/work_item](https://github.com/PX4/PX4-Autopilot/tree/main/src/examples/work_item).
A work queue task application is just the same as an ordinary (task) application, except that it needs to specify that it is a work queue task, and schedule itself to run during initialisation.
@@ -36,7 +36,7 @@ In summary:
{
}
```
::: info
The available work queues (`wq_configurations`) are listed in [WorkQueueManager.hpp](https://github.com/PX4/PX4-Autopilot/blob/main/platforms/common/include/px4_platform_common/px4_work_queue/WorkQueueManager.hpp#L49).
:::
@@ -64,4 +64,3 @@ The template demonstrates the following additional features/aspects that are req
documented [in the source code](https://github.com/PX4/PX4-Autopilot/blob/v1.8.0/src/platforms/px4_module.h#L381)):
- They are used to print the command-line usage when entering `module help` on the console.
- They are automatically extracted via script to generate the [Modules & Commands Reference](../modules/modules_main.md) page.
docs/en/msg_docs/index.md
-2
View File
@@ -300,5 +300,3 @@ NaN means the state was not controlled
- [AirspeedValidatedV0](AirspeedValidatedV0.md)
- [VehicleAttitudeSetpointV0](VehicleAttitudeSetpointV0.md)
- [VehicleStatusV0](VehicleStatusV0.md) — Encodes the system state of the vehicle published by commander
docs/en/payloads/generic_actuator_control.md
+1 -1
View File
@@ -163,4 +163,4 @@ Payloads that are triggered by servos and other actuators, such as grippers, can
This is safer than testing when the vehicle is armed.
Camera payloads can be triggered and tested at any time.
Camera payloads can be triggered and tested at any time.
docs/en/peripherals/camera.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../camera/configuration" />
<Redirect to="../camera/configuration" />
docs/en/peripherals/camera_t265_vio.md
+1 -1
View File
@@ -1 +1 @@
<Redirect to="../camera/camera_intel_realsense_t265_vio" />
<Redirect to="../camera/camera_intel_realsense_t265_vio" />
docs/en/peripherals/mavlink_peripherals.md
-1
View File
@@ -120,4 +120,3 @@ Links to setup instructions for specific MAVLink components:
- [Serial Port Configuration](../peripherals/serial_configuration.md)
- [PX4 Ethernet Setup > PX4 MAVLink Serial Port Configuration](../advanced_config/ethernet_setup.md#px4-mavlink-serial-port-configuration)
- [Serial Port Mapping](../hardware/serial_port_mapping.md)
docs/en/ros2/px4_ros2_interface_lib.md
+1 -1
View File
@@ -52,4 +52,4 @@ To get started using the library within an existing ROS 2 workspace:
When opening a pull request to PX4, CI runs the library integration tests.
These test that mode registration, failsafes, and mode replacement, work as expected.
For more information see [PX4 ROS2 Interface Library Integration Testing](../test_and_ci/integration_testing_px4_ros2_interface.md).
For more information see [PX4 ROS2 Interface Library Integration Testing](../test_and_ci/integration_testing_px4_ros2_interface.md).
docs/en/test_and_ci/integration_testing_px4_ros2_interface.md
+1 -1
View File
@@ -26,4 +26,4 @@ You can list the available test cases with:
```sh
./test/ros_test_runner.py --list-cases
```
```
docs/en/test_and_ci/integration_testing_ros1_mavros.md
+1 -1
View File
@@ -151,4 +151,4 @@ To write a new test:
@"$(SRC_DIR)"/test/rostest_px4_run.sh mavros_posix_tests_<new_test>.test
```
Run the tests as described above.
Run the tests as described above.