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

Link fixes galore (#25151)

Browse Source
This commit is contained in:
Hamish Willee
2025-07-03 14:53:12 +10:00
committed by GitHub
parent dd0d00aedc
commit 375f421c61
107 changed files with 836 additions and 972 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/getting_started/flight_reporting.md
+1 -1
View File
@@ -9,7 +9,7 @@ Keeping flight logs is a legal requirement in some jurisdictions.
## Downloading Logs from the Flight Controller
Logs can be downloaded using [QGroundControl](http://qgroundcontrol.com/): **[Analyze View > Log Download](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/log_download.html)**.
Logs can be downloaded using [QGroundControl](https://qgroundcontrol.com/): **[Analyze View > Log Download](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/log_download.html)**.
![Flight Log Download](../../assets/qgc/analyze/log_download.jpg)
docs/en/getting_started/px4_basic_concepts.md
+2 -2
View File
@@ -74,9 +74,9 @@ A subset of the products that are known to work with PX4 are listed below.
### QGroundControl {#qgc}
The Dronecode GCS software is called [QGroundControl](http://qgroundcontrol.com/) ("QGC").
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](http://qgroundcontrol.com/downloads/).
You can download it (for free) from [here](https://qgroundcontrol.com/downloads/).
![QGC Main Screen](../../assets/concepts/qgc_fly_view.png)
docs/en/getting_started/rc_transmitter_receiver.md
+2 -4
View File
@@ -97,11 +97,11 @@ _PX4_ and _Pixhawk_ have been validated with:
- PPM sum receivers
- S.BUS and S.BUS2 receivers from:
- Futaba
- FrSky S.BUS and PPM models
- TBS Crossfire with SBUS as output protocol
- Herelink
- TBS Crossfire with ([CRSF protocol](../telemetry/crsf_telemetry.md))
- Express LRS with ([CRSF protocol](../telemetry/crsf_telemetry.md))
@@ -111,13 +111,11 @@ _PX4_ and _Pixhawk_ have been validated with:
Receivers from other vendors that use a supported protocol are likely to work but have not been tested.
::: info
Historically there were differences and incompatibilities between receiver models, largely due to a lack of detailed specification of protocols.
The receivers we have tested all now appear to be compatible, but it is possible that others may not be.
:::
## Connecting Receivers
As general guidance, receivers connect to the flight controller using the port appropriate to their supported protocol:
@@ -127,7 +125,7 @@ As general guidance, receivers connect to the flight controller using the port a
- Graupner HoTT receivers: SUMD output must connect to a **SPKT/DSM** input (as above).
- PPM-Sum and S.BUS receivers must connect directly to the **RC** ground, power and signal pins.
This is typically labeled: `RC IN`, `RCIN` or `RC`, but has in some FCs has been labeled `PPM RC` or `PPM`.
- PPM receivers that have an individual wire for each channel must connect to the RCIN channel _via_ a PPM encoder [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
- PPM receivers that have an individual wire for each channel must connect to the RCIN channel _via_ a PPM encoder [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
- TBS Crossfire/Express LRS Receivers using [CRSF Telemetry](../telemetry/crsf_telemetry.md) connect via a spare UART.
Flight controllers usually include appropriate cables for connecting common receiver types.