docs(infrastructure): Add script and tests to generate FC doc sections/docs

This commit is contained in:
Hamish Willee
2026-04-02 09:10:59 +11:00
parent f444402e6c
commit 35a734d49a
177 changed files with 56826 additions and 1 deletions
File diff suppressed because it is too large Load Diff
@@ -0,0 +1,38 @@
### GPS & Compass {#gps_compass}
PX4 supports GPS modules connected to the GPS port(s) listed below.
The module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker pointing towards the front of the vehicle.
The GPS ports are:
- `GPS1` (FMU): TODO: connector type — GPS, compass (I2C)
![GNSS Connection](../../assets/flight_controller/test_fixture/gnss_connection.png)
<!-- checklist
- [ ] Confirm physical label(s) of GPS port(s) as printed on board
- [ ] Confirm connector type (e.g. 10-pin JST GH Pixhawk full or 6-pin basic)
- [ ] Confirm whether GPS1 includes safety switch, buzzer and LED pins
- [ ] Note whether an external compass is required or integrated in GPS module
- [ ] Add a connection diagram image showing GPS port location
-->
<!-- gps-source-data
{
"board": "test/fixture",
"source": {
"gps_ports": [
{
"label": "GPS1",
"device": "/dev/ttyS3",
"uart": "UART4"
}
],
"has_pps_capture": false,
"has_safety_switch": false,
"has_safety_led": false,
"has_buzzer": false
},
"gps_ports_wizard": null
}
-->
@@ -0,0 +1,48 @@
### GPS & Compass {#gps_compass}
PX4 supports GPS modules connected to the GPS port(s) listed below.
The module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker pointing towards the front of the vehicle.
The GPS ports are:
- `GPS1` (FMU): TODO: connector type — GPS, compass (I2C)
- `GPS2` (FMU): TODO: connector type — GPS, compass (I2C)
The GPS module's integrated safety switch is enabled _by default_ (when enabled, PX4 will not let you arm the vehicle).
To disable the safety switch press and hold it for 1 second.
You can press the safety switch again to enable safety and disarm the vehicle.
![GNSS Connection](../../assets/flight_controller/test_fixture/gnss_connection.png)
<!-- checklist
- [ ] Confirm physical label(s) of GPS port(s) as printed on board
- [ ] Confirm connector type (e.g. 10-pin JST GH Pixhawk full or 6-pin basic)
- [ ] Confirm whether GPS1 includes safety switch, buzzer and LED pins
- [ ] Note whether an external compass is required or integrated in GPS module
- [ ] Add a connection diagram image showing GPS port location
-->
<!-- gps-source-data
{
"board": "test/fixture",
"source": {
"gps_ports": [
{
"label": "GPS1",
"device": "/dev/ttyS0",
"uart": "USART1"
},
{
"label": "GPS2",
"device": "/dev/ttyS3",
"uart": "UART4"
}
],
"has_pps_capture": false,
"has_safety_switch": true,
"has_safety_led": false,
"has_buzzer": false
},
"gps_ports_wizard": null
}
-->
@@ -0,0 +1,42 @@
### GPS & Compass {#gps_compass}
PX4 supports GPS modules connected to the GPS port(s) listed below.
The module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker pointing towards the front of the vehicle.
The GPS ports are:
- `GPS1` (FMU): TODO: connector type — GPS, compass (I2C)
The GPS module's integrated safety switch is enabled _by default_ (when enabled, PX4 will not let you arm the vehicle).
To disable the safety switch press and hold it for 1 second.
You can press the safety switch again to enable safety and disarm the vehicle.
![GNSS Connection](../../assets/flight_controller/test_fixture/gnss_connection.png)
<!-- checklist
- [ ] Confirm physical label(s) of GPS port(s) as printed on board
- [ ] Confirm connector type (e.g. 10-pin JST GH Pixhawk full or 6-pin basic)
- [ ] Confirm whether GPS1 includes safety switch, buzzer and LED pins
- [ ] Note whether an external compass is required or integrated in GPS module
- [ ] Add a connection diagram image showing GPS port location
-->
<!-- gps-source-data
{
"board": "test/fixture",
"source": {
"gps_ports": [
{
"label": "GPS1",
"device": "/dev/ttyS3",
"uart": "UART4"
}
],
"has_pps_capture": false,
"has_safety_switch": true,
"has_safety_led": false,
"has_buzzer": false
},
"gps_ports_wizard": null
}
-->
@@ -0,0 +1,44 @@
### GPS & Compass {#gps_compass}
PX4 supports GPS modules connected to the GPS port(s) listed below.
The module should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible, with the direction marker pointing towards the front of the vehicle.
The GPS ports are:
- `GPS1` (FMU): TODO: connector type — GPS, compass (I2C)
![GNSS Connection](../../assets/flight_controller/test_fixture/gnss_connection.png)
<!-- checklist
- [ ] Confirm physical label(s) of GPS port(s) as printed on board
- [ ] Confirm connector type (e.g. 10-pin JST GH Pixhawk full or 6-pin basic)
- [ ] Confirm whether GPS1 includes safety switch, buzzer and LED pins
- [ ] Note whether an external compass is required or integrated in GPS module
- [ ] Add a connection diagram image showing GPS port location
-->
<!-- gps-source-data
{
"board": "test/fixture",
"source": {
"gps_ports": [
{
"label": "GPS1",
"device": "/dev/ttyS3",
"uart": "UART4"
}
],
"has_pps_capture": false,
"has_safety_switch": false,
"has_safety_led": false,
"has_buzzer": false
},
"gps_ports_wizard": [
{
"label": "GPS1",
"device": "/dev/ttyS0",
"uart": "USART1"
}
]
}
-->
@@ -0,0 +1,40 @@
## Power {#power}
The flight controller can be powered from a power module connected to the **TODO: POWER port label** port.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `TODO: POWER port label`: TODO: connector type
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 1,
"has_redundant_power": false,
"has_dual_battery_monitoring": false,
"has_dronecan_power_input": true,
"power_monitor_type": "ina238"
},
"power_ports_wizard": null
}
-->
@@ -0,0 +1,48 @@
## Power {#power}
The flight controller can be powered from a power module connected to the **POWER** port.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `POWER`: 6-pin JST GH — DroneCAN battery monitoring.
Connect a [DroneCAN power module](../power_module/index.md) to the CAN bus.
Set `UAVCAN_ENABLE = 2` (Sensors Automatic Config) and `UAVCAN_SUB_BAT = 1` (Raw data).
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 1,
"has_redundant_power": false,
"has_dual_battery_monitoring": false,
"has_dronecan_power_input": false,
"power_monitor_type": "analog"
},
"power_ports_wizard": [
{
"label": "POWER",
"connector_type": "6-pin JST GH",
"monitor_type": "dronecan"
}
]
}
-->
@@ -0,0 +1,42 @@
## Power {#power}
The flight controller can be powered from a power module connected to the **TODO: POWER 1 port label** or **TODO: POWER 2 port label** port, providing redundant power inputs.
If one power module fails the controller automatically switches to the other.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `TODO: POWER 1 port label`: TODO: connector type
- `TODO: POWER 2 port label`: TODO: connector type
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 2,
"has_redundant_power": true,
"has_dual_battery_monitoring": true,
"has_dronecan_power_input": true,
"power_monitor_type": "ltc44xx"
},
"power_ports_wizard": null
}
-->
@@ -0,0 +1,54 @@
## Power {#power}
The flight controller supports two power inputs: **POWER 1** for a standard power module and **POWER C1** for a DroneCAN power module.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `POWER 1`: 6-pin Molex CLIK-Mate
- `POWER C1`: 6-pin JST GH — DroneCAN battery monitoring.
Connect a [DroneCAN power module](../power_module/index.md) to the CAN bus.
Set `UAVCAN_ENABLE = 2` (Sensors Automatic Config) and `UAVCAN_SUB_BAT = 1` (Raw data).
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 2,
"has_redundant_power": true,
"has_dual_battery_monitoring": true,
"has_dronecan_power_input": true,
"power_monitor_type": "ltc44xx"
},
"power_ports_wizard": [
{
"label": "POWER 1",
"connector_type": "6-pin Molex CLIK-Mate",
"monitor_type": "analog"
},
{
"label": "POWER C1",
"connector_type": "6-pin JST GH",
"monitor_type": "dronecan"
}
]
}
-->
@@ -0,0 +1,40 @@
## Power {#power}
The flight controller can be powered from a power module connected to the **TODO: POWER port label** port.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `TODO: POWER port label`: TODO: connector type
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 1,
"has_redundant_power": false,
"has_dual_battery_monitoring": false,
"has_dronecan_power_input": false,
"power_monitor_type": "analog"
},
"power_ports_wizard": null
}
-->
@@ -0,0 +1,51 @@
## Power {#power}
The flight controller can be powered from a power module connected to the **POWER 1** or **POWER 2** port, providing redundant power inputs.
If one power module fails the controller automatically switches to the other.
The power module must supply a regulated **5V** at a minimum of **3A continuous**.
Power ports:
- `POWER 1`: 6-pin Molex CLIK-Mate
- `POWER 2`: 6-pin Molex CLIK-Mate
:::warning
The PWM output ports are not powered by the POWER port.
The output rail must be [separately powered](../assembly/servo_power.md) if it needs to power servos or other hardware.
This is generally true for VTOL and fixed-wing vehicles, but not necessarily true for MC vehicles.
:::
For battery and power module configuration see [Battery and Power Module Setup](../config/battery.md).
![Power Connection](../../assets/flight_controller/fixture/power_connection.png)
<!-- checklist
- [ ] Confirm power port label(s) as printed on board
- [ ] Confirm connector type(s)
- [ ] Confirm voltage/current ratings of power module used
- [ ] Add a connection diagram image showing power port location
-->
<!-- power-source-data
{
"board": "test/fixture",
"source": {
"num_power_inputs": 2,
"has_redundant_power": true,
"has_dual_battery_monitoring": true,
"has_dronecan_power_input": true,
"power_monitor_type": "ltc44xx"
},
"power_ports_wizard": [
{
"label": "POWER 1",
"connector_type": "6-pin Molex CLIK-Mate"
},
{
"label": "POWER 2",
"connector_type": "6-pin Molex CLIK-Mate"
}
]
}
-->
@@ -0,0 +1,12 @@
## PWM Outputs {#pwm_outputs}
This flight controller supports up to 8 FMU PWM outputs (MAIN).
All outputs support [DShot](../peripherals/dshot.md) and [Bidirectional DShot](../peripherals/dshot.md#bidirectional-dshot-telemetry).
The 8 outputs are in 2 groups:
- Outputs 1-4 in group1 (PWM2)
- Outputs 5-8 in group2 (PWM4)
All outputs within the same group must use the same output protocol and rate.
@@ -0,0 +1,3 @@
## PWM Outputs {#pwm_outputs}
PWM output information could not be determined from source.
@@ -0,0 +1,13 @@
## PWM Outputs {#pwm_outputs}
This flight controller supports up to 6 FMU PWM outputs (MAIN).
[DShot](../peripherals/dshot.md) is not supported.
The 6 outputs are in 3 groups:
- Outputs 1-2 in group1 (Timer1)
- Outputs 3-4 in group2 (Timer4)
- Outputs 5-6 in group3 (Timer5)
All outputs within the same group must use the same output protocol and rate.
@@ -0,0 +1,14 @@
## PWM Outputs {#pwm_outputs}
This flight controller supports up to 8 FMU PWM outputs (MAIN).
All outputs support [DShot](../peripherals/dshot.md) and [Bidirectional DShot](../peripherals/dshot.md#bidirectional-dshot-telemetry).
The 8 outputs are in 4 groups:
- Outputs 1-2 in group1 (Timer3)
- Outputs 3-4 in group2 (Timer2)
- Outputs 5-6 in group3 (Timer5)
- Outputs 7-8 in group4 (Timer8)
All outputs within the same group must use the same output protocol and rate.
@@ -0,0 +1,18 @@
## PWM Outputs {#pwm_outputs}
This flight controller supports up to 9 FMU PWM outputs (AUX) and 8 IO PWM outputs (MAIN).
FMU Outputs:
- Outputs 1-6, 9 support [DShot](../peripherals/dshot.md).
- Outputs 7-8 do not support DShot.
- Outputs 1-6, 9 support [Bidirectional DShot](../peripherals/dshot.md#bidirectional-dshot-telemetry).
The 9 outputs are in 4 groups:
- Outputs 1-4 in group1 (Timer5)
- Outputs 5-6 in group2 (Timer4)
- Outputs 7-8 in group3 (Timer12)
- Output 9 in group4 (Timer1)
All outputs within the same group must use the same output protocol and rate.
@@ -0,0 +1,46 @@
### Radio Control {#radio_control}
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
The ports and supported protocols are:
- `PX4IO/RC` (IO): SBUS, DSM/DSMX, CRSF, and GHST receivers
For PPM and S.Bus receivers, a single signal wire carries all channels. If your receiver outputs individual PWM signals (one wire per channel) it must be connected via a [PPM encoder](../getting_started/rc_transmitter_receiver.md#pwm-receivers).
![RC Connection Diagram](../../assets/flight_controller/test_fixture/rc_connection_diagram.png)
<!-- checklist
- [ ] List all RC port names exactly as labeled on the board
- [ ] State which protocols each port supports
- [ ] State the connector type used for each RC port
- [ ] Confirm which protocols have been tested with this board
- [ ] Add a connection diagram image showing where to plug in the RC receiver
-->
<!-- rc-source-data
{
"board": "test/fixture",
"modules": {
"rc_input": false,
"common_rc": true,
"px4io": true,
"has_ppm_pin": true,
"ppm_shared_with_serial": false
},
"rc_serial": {
"device": "/dev/ttyS5",
"uart": "USART6",
"label": "PX4IO/RC",
"side": "IO"
},
"io_serial": {
"device": "/dev/ttyS5",
"uart": "USART6",
"label": "PX4IO/RC"
},
"rc_ports_wizard": null
}
-->
@@ -0,0 +1,42 @@
### Radio Control {#radio_control}
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
The ports and supported protocols are:
- `RC` (FMU): SBUS, DSM/DSMX, ST24, SUMD, CRSF, and GHST receivers
For PPM and S.Bus receivers, a single signal wire carries all channels. If your receiver outputs individual PWM signals (one wire per channel) it must be connected via a [PPM encoder](../getting_started/rc_transmitter_receiver.md#pwm-receivers).
![RC Connection Diagram](../../assets/flight_controller/test_fixture/rc_connection_diagram.png)
<!-- checklist
- [ ] List all RC port names exactly as labeled on the board
- [ ] State which protocols each port supports
- [ ] State the connector type used for each RC port
- [ ] Confirm which protocols have been tested with this board
- [ ] Add a connection diagram image showing where to plug in the RC receiver
-->
<!-- rc-source-data
{
"board": "test/fixture",
"modules": {
"rc_input": true,
"common_rc": false,
"px4io": false,
"has_ppm_pin": false,
"ppm_shared_with_serial": false
},
"rc_serial": {
"device": "/dev/ttyS4",
"uart": "USART6",
"label": "RC",
"side": "FMU"
},
"io_serial": null,
"rc_ports_wizard": null
}
-->
@@ -0,0 +1,37 @@
### Radio Control {#radio_control}
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
The ports and supported protocols are:
- `TODO: RC port label` (FMU): TODO: list supported protocols
For PPM and S.Bus receivers, a single signal wire carries all channels. If your receiver outputs individual PWM signals (one wire per channel) it must be connected via a [PPM encoder](../getting_started/rc_transmitter_receiver.md#pwm-receivers).
![RC Connection Diagram](../../assets/flight_controller/test_fixture/rc_connection_diagram.png)
<!-- checklist
- [ ] List all RC port names exactly as labeled on the board
- [ ] State which protocols each port supports
- [ ] State the connector type used for each RC port
- [ ] Confirm which protocols have been tested with this board
- [ ] Add a connection diagram image showing where to plug in the RC receiver
-->
<!-- rc-source-data
{
"board": "test/fixture",
"modules": {
"rc_input": false,
"common_rc": false,
"px4io": false,
"has_ppm_pin": false,
"ppm_shared_with_serial": false
},
"rc_serial": null,
"io_serial": null,
"rc_ports_wizard": null
}
-->
@@ -0,0 +1,43 @@
### Radio Control {#radio_control}
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
The ports and supported protocols are:
- `RC` (FMU): SBUS, DSM/DSMX, ST24, SUMD, CRSF, and GHST receivers
- `TODO: PPM port label` (FMU): PPM
For PPM and S.Bus receivers, a single signal wire carries all channels. If your receiver outputs individual PWM signals (one wire per channel) it must be connected via a [PPM encoder](../getting_started/rc_transmitter_receiver.md#pwm-receivers).
![RC Connection Diagram](../../assets/flight_controller/test_fixture/rc_connection_diagram.png)
<!-- checklist
- [ ] List all RC port names exactly as labeled on the board
- [ ] State which protocols each port supports
- [ ] State the connector type used for each RC port
- [ ] Confirm which protocols have been tested with this board
- [ ] Add a connection diagram image showing where to plug in the RC receiver
-->
<!-- rc-source-data
{
"board": "test/fixture",
"modules": {
"rc_input": true,
"common_rc": false,
"px4io": false,
"has_ppm_pin": true,
"ppm_shared_with_serial": false
},
"rc_serial": {
"device": "/dev/ttyS4",
"uart": "USART6",
"label": "RC",
"side": "FMU"
},
"io_serial": null,
"rc_ports_wizard": null
}
-->
@@ -0,0 +1,42 @@
### Radio Control {#radio_control}
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
The ports and supported protocols are:
- `RC` (FMU): PPM, SBUS, DSM/DSMX, ST24, SUMD, CRSF, and GHST receivers
For PPM and S.Bus receivers, a single signal wire carries all channels. If your receiver outputs individual PWM signals (one wire per channel) it must be connected via a [PPM encoder](../getting_started/rc_transmitter_receiver.md#pwm-receivers).
![RC Connection Diagram](../../assets/flight_controller/test_fixture/rc_connection_diagram.png)
<!-- checklist
- [ ] List all RC port names exactly as labeled on the board
- [ ] State which protocols each port supports
- [ ] State the connector type used for each RC port
- [ ] Confirm which protocols have been tested with this board
- [ ] Add a connection diagram image showing where to plug in the RC receiver
-->
<!-- rc-source-data
{
"board": "test/fixture",
"modules": {
"rc_input": true,
"common_rc": false,
"px4io": false,
"has_ppm_pin": true,
"ppm_shared_with_serial": true
},
"rc_serial": {
"device": "/dev/ttyS4",
"uart": "USART6",
"label": "RC",
"side": "FMU"
},
"io_serial": null,
"rc_ports_wizard": null
}
-->
@@ -0,0 +1,12 @@
## SD Card
This board does not have an SD card slot.
<!-- sd-source-data
{
"board": "test/fixture",
"source": {
"has_sd_card": false
}
}
-->
@@ -0,0 +1,24 @@
## SD Card (Optional) {#sd_card}
SD cards are highly recommended as they are needed to [log and analyse flight details](../getting_started/flight_reporting.md), to run missions, and to use UAVCAN-bus hardware.
Insert the card into _TODO: fixture board name_ as shown below.
![SD Card Slot](../../assets/flight_controller/fixture/sd_card_slot.jpg)
:::tip
For more information see [Basic Concepts > SD Cards (Removable Memory)](../getting_started/px4_basic_concepts.md#sd-cards-removable-memory).
:::
<!-- checklist
- [ ] Confirm SD card slot location
- [ ] Add photo showing SD card insertion
-->
<!-- sd-source-data
{
"board": "test/fixture",
"source": {
"has_sd_card": true
}
}
-->
@@ -0,0 +1,3 @@
## Serial Port Mapping
Serial port mapping could not be determined from source.
@@ -0,0 +1,11 @@
## Serial Port Mapping
| UART | Device | Port | Flow Control |
|------|--------|------|:---:|
| LPUART2 | /dev/ttyS0 | Debug Console | - |
| LPUART3 | /dev/ttyS1 | GPS1 | - |
| LPUART4 | /dev/ttyS2 | TELEM1 | - |
| LPUART5 | /dev/ttyS3 | TELEM2 | - |
| LPUART6 | /dev/ttyS4 | TELEM3 | - |
| LPUART7 | /dev/ttyS5 | RC | - |
| LPUART8 | /dev/ttyS6 | | - |
@@ -0,0 +1,3 @@
## Serial Port Mapping
Serial port mapping could not be determined from source.
@@ -0,0 +1,12 @@
## Serial Port Mapping
| UART | Device | Port | Flow Control |
|------|--------|------|:---:|
| USART1 | /dev/ttyS0 | GPS1 | - |
| USART2 | /dev/ttyS1 | TELEM3 | Yes |
| USART3 | /dev/ttyS2 | Debug Console | - |
| UART4 | /dev/ttyS3 | GPS2 | Yes |
| UART5 | /dev/ttyS4 | TELEM2 | - |
| USART6 | /dev/ttyS5 | PX4IO/RC | - |
| UART7 | /dev/ttyS6 | TELEM1 | - |
| UART8 | /dev/ttyS7 | | - |
@@ -0,0 +1,57 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: TODO: list imu(s)
- **Barometer**: TODO: list barometer(s)
- **Magnetometer**: IST8310 (I2C, internal), IST8310 (I2C, bus 1, external)
### Interfaces
- **I2C ports**: 4
- IST8310 (magnetometer, internal)
- IST8310 (magnetometer, external, bus 1)
- **SPI buses**: TODO: number of SPI buses
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 4,
"num_spi_buses": 0,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [],
"baro": [],
"mag": [
"IST8310"
],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,56 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
- **IO Processor**: STM32F100 (32-bit Arm® Cortex®-M3, 24 MHz, 8KB SRAM)
### Sensors
- **IMU**: TODO: list imu(s)
- **Barometer**: TODO: list barometer(s)
- **Magnetometer**: TODO: list magnetometer(s)
### Interfaces
- **PWM outputs**: 8 (0 FMU + 8 IO)
- **I2C ports**: TODO: number of I2C ports
- **SPI buses**: TODO: number of SPI buses
- **USB**: TODO: confirm USB connector type
- **RC input**: SBUS, DSM/DSMX, ST24, SUMD, CRSF, GHST (via IO)
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": true,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 8,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 0,
"num_spi_buses": 0,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [],
"baro": [],
"mag": [],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,56 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
- **IO Processor**: STM32F100 (32-bit Arm® Cortex®-M3, 24 MHz, 8KB SRAM)
### Sensors
- **IMU**: TODO: list imu(s)
- **Barometer**: TODO: list barometer(s)
- **Magnetometer**: TODO: list magnetometer(s)
### Interfaces
- **PWM outputs**: 8 (0 FMU + 8 IO)
- **I2C ports**: TODO: number of I2C ports
- **SPI buses**: TODO: number of SPI buses
- **USB**: TODO: confirm USB connector type
- **RC input**: SBUS, DSM/DSMX, ST24, SUMD, CRSF, GHST, PPM (via IO)
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": true,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 8,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 0,
"num_spi_buses": 0,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [],
"baro": [],
"mag": [],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,59 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: ICM-42688P
- **Barometer**: MS5611
- **Magnetometer**: IST8310
### Interfaces
- **I2C ports**: TODO: number of I2C ports
- **SPI buses**: 3
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 0,
"num_spi_buses": 3,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [
"ICM-42688P"
],
"baro": [
"MS5611"
],
"mag": [
"IST8310"
],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,59 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: ICM-42688P (SPI)
- **Barometer**: MS5611 (SPI)
- **Magnetometer**: TODO: list magnetometer(s)
### Interfaces
- **I2C ports**: TODO: number of I2C ports
- **SPI buses**: 4
- ICM-42688P (IMU)
- MS5611 (barometer)
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 0,
"num_spi_buses": 4,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [
"ICM-42688P"
],
"baro": [
"MS5611"
],
"mag": [],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,70 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: ICM-42688P (SPI); BMI088 (SPI, hardware revision Rev 1.0), ICM-20602 (SPI, hardware revision Rev 1.1)
- **Barometer**: MS5611 (SPI)
- **Magnetometer**: IST8310 (I2C, internal), IST8310 (I2C, bus 1, external)
### Interfaces
- **I2C ports**: 4
- IST8310 (magnetometer, internal)
- IST8310 (magnetometer, external, bus 1)
- **SPI buses**: 5
- ICM-42688P (IMU)
- MS5611 (barometer)
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 4,
"num_spi_buses": 5,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [
"ICM-42688P",
"BMI088",
"ICM-20602"
],
"baro": [
"MS5611"
],
"mag": [
"IST8310"
],
"osd": []
},
"overview_wizard": {
"sensor_variant_labels": {
"HW000001": "Rev 1.0",
"__other__": "Rev 1.1"
}
}
}
-->
@@ -0,0 +1,65 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: ICM-42688P (SPI); BMI088 (SPI, variant HW000001), ICM-20602 (SPI, other variants)
- **Barometer**: MS5611 (SPI)
- **Magnetometer**: IST8310 (I2C, internal), IST8310 (I2C, bus 1, external)
### Interfaces
- **I2C ports**: 4
- IST8310 (magnetometer, internal)
- IST8310 (magnetometer, external, bus 1)
- **SPI buses**: 5
- ICM-42688P (IMU)
- MS5611 (barometer)
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 4,
"num_spi_buses": 5,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [
"ICM-42688P",
"BMI088",
"ICM-20602"
],
"baro": [
"MS5611"
],
"mag": [
"IST8310"
],
"osd": []
},
"overview_wizard": null
}
-->
@@ -0,0 +1,58 @@
## Specifications {#specifications}
### Processor
- **Main FMU Processor**: STM32H753 (32-bit Arm® Cortex®-M7, 480 MHz, 2MB flash, 1MB RAM)
### Sensors
- **IMU**: ICM-42688P
- **Barometer**: TODO: list barometer(s)
- **Magnetometer**: TODO: list magnetometer(s)
### Interfaces
- **I2C ports**: TODO: number of I2C ports
- **SPI buses**: 3
- ICM-42688P (IMU)
- **USB**: TODO: confirm USB connector type
- **Analog battery inputs**: 1
- **Additional analog inputs**: TODO: number of additional analog inputs
### Electrical Data
- **Input voltage**: TODO: supply voltage range
### Mechanical Data
- **Dimensions**: TODO: dimensions (mm)
- **Weight**: TODO: weight (g)
<!-- overview-source-data
{
"board": "test/fixture",
"chip_model": "STM32H753",
"has_io_board": false,
"total_outputs": null,
"fmu_servo_outputs": 0,
"io_outputs": 0,
"has_sd_card": false,
"has_ethernet": false,
"has_heater": false,
"num_i2c_buses": 0,
"num_spi_buses": 3,
"num_can_buses": 0,
"has_usb": false,
"sensor_drivers": {
"imu": [
"ICM-42688P"
],
"baro": [],
"mag": [],
"osd": []
},
"overview_wizard": {
"imu": "ICM-42688P"
}
}
-->
@@ -0,0 +1,26 @@
## Telemetry Radios (Optional) {#telemetry}
[Telemetry radios](../telemetry/index.md) may be used to communicate and control a vehicle in flight from a ground station (for example, you can direct the UAV to a particular position, or upload a new mission).
The vehicle-based radio should be connected to a TELEM port — **TELEM1**, **TELEM2**, **TELEM3** (if connected to **TELEM1**, no further configuration is required).
The other radio is connected to your ground station computer or mobile device (usually by USB).
![Telemetry Radio](../../assets/flight_controller/fixture/telemetry_radio.jpg)
<!-- checklist
- [ ] Confirm TELEM port label(s) as printed on board
- [ ] Add a wiring photo showing telemetry radio connected to TELEM1
-->
<!-- telemetry-source-data
{
"board": "test/fixture",
"source": {
"telem_ports": [
"TELEM1",
"TELEM2",
"TELEM3"
]
}
}
-->
@@ -0,0 +1,24 @@
## Telemetry Radios (Optional) {#telemetry}
[Telemetry radios](../telemetry/index.md) may be used to communicate and control a vehicle in flight from a ground station (for example, you can direct the UAV to a particular position, or upload a new mission).
The vehicle-based radio should be connected to the **TELEM1** port (if connected to this port, no further configuration is required).
The other radio is connected to your ground station computer or mobile device (usually by USB).
![Telemetry Radio](../../assets/flight_controller/fixture/telemetry_radio.jpg)
<!-- checklist
- [ ] Confirm TELEM port label(s) as printed on board
- [ ] Add a wiring photo showing telemetry radio connected to TELEM1
-->
<!-- telemetry-source-data
{
"board": "test/fixture",
"source": {
"telem_ports": [
"TELEM1"
]
}
}
-->