88d623bedb
* Add vitepress tree * Update existing workflows so they dont trigger on changes in the docs path * Add nojekyll, package.json, LICENCE etc * Add crowdin docs upload/download scripts * Add docs flaw checker workflows * Used docs prefix for docs workflows * Crowdin obvious fixes * ci: docs move to self hosted runner runs on a beefy server for faster builds Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: don't run build action for docs or ci changes Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: update runners Signed-off-by: Ramon Roche <mrpollo@gmail.com> * Add docs/en * Add docs assets and scripts * Fix up editlinks to point to PX4 sources * Download just the translations that are supported * Add translation sources for zh, uk, ko * Update latest tranlsation and uorb graphs * update vitepress to latest --------- Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Ramon Roche <mrpollo@gmail.com>
1.3 KiB
Telemetry Radio/Modem Integration
Telemetry Radios can (optionally) be used to provide a wireless MAVLink connection between a ground control station like QGroundControl and a vehicle running PX4. This section contains topics about advanced use of supported radios and integrating new telemetry systems into PX4.
:::tip Peripheral Hardware > Telemetry Radios contains information about telemetry radio systems already supported by PX4. This includes radios that use the SiK Radio firmware and 3DR WiFi Telemetry Radios. :::
Integrating Telemetry Systems
PX4 enables MAVLink-based telemetry via the telemetry port of a Pixhawk-based flight controller. Provided that a telemetry radio supports MAVLink and provides a UART interface with compatible voltage levels/connector, no further integration is required.
Telemetry systems that communicate using some other protocol will need more extensive integration, potentially covering both software (e.g. device drivers) and hardware (connectors etc.). While this has been done for specific cases (e.g. FrSky Telemetry enables sending vehicle status to an RC controller via an FrSky receiver) providing general advice is difficult. We recommend you start by discussing with the development team.