mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-03 15:38:52 +08:00
docs: Codespell check on English sources + swd fixes (#26657)
This commit is contained in:
@@ -28,7 +28,7 @@ Order this module from:
|
||||
- Pixhawk Standard SPI Connector
|
||||
- 7 Pin JST GH
|
||||
- PWM Connector
|
||||
- 10 Pin JST JST
|
||||
- 10 Pin JST
|
||||
- 8 PWM Outputs
|
||||
- Matches Pixhawk 4 PWM Connector Pinout
|
||||
- Pixhawk Standard Debug Connector
|
||||
@@ -77,7 +77,7 @@ DroneCAN configuration in PX4 is explained in more detail in [DroneCAN > Enablin
|
||||
|
||||
You will need to enable the subscriber appropriate for each of the sensors that are connected to the ARK CANnode.
|
||||
|
||||
This is done using the the parameters named like `UAVCAN_SUB_*` in the parameter reference (such as [UAVCAN_SUB_ASPD](../advanced_config/parameter_reference.md#UAVCAN_SUB_ASPD), [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO) etc.).
|
||||
This is done using the parameters named like `UAVCAN_SUB_*` in the parameter reference (such as [UAVCAN_SUB_ASPD](../advanced_config/parameter_reference.md#UAVCAN_SUB_ASPD), [UAVCAN_SUB_BARO](../advanced_config/parameter_reference.md#UAVCAN_SUB_BARO) etc.).
|
||||
|
||||
## Ark CANNode Configuration
|
||||
|
||||
|
||||
@@ -103,7 +103,7 @@ You need to set necessary [DroneCAN](index.md) parameters and define offsets if
|
||||
|
||||
### Parameter references
|
||||
|
||||
This GPS is using ARK's private driver, the prameters below only exist on the firmware we ship the GPS with. You can set these params either in QGC or using the DroneCAN GUI Tool.
|
||||
This GPS is using ARK's private driver, the parameters below only exist on the firmware we ship the GPS with. You can set these params either in QGC or using the DroneCAN GUI Tool.
|
||||
|
||||
#### SEP_OFFS_YAW (float)
|
||||
|
||||
|
||||
@@ -86,7 +86,7 @@ DroneCAN configuration in PX4 is explained in more detail in [DroneCAN > Enablin
|
||||
|
||||
### Sensor Position Configuration
|
||||
|
||||
- For the the single Rover the module should be mounted with the included mast.
|
||||
- For the single Rover the module should be mounted with the included mast.
|
||||
- For the Dual ZED-F9P setup (moving baseline), the DroneCAN modules should be placed at least 30cm apart on the airframe and elevated on a mast also.
|
||||
See the following [mast](https://holybro.com/products/30-antenna-mount?_pos=20&_sid=67b49d76b&_ss=r).
|
||||
- F9P module arrow(s) should be pointing forward with respect to the autopilot orientation.
|
||||
|
||||
@@ -152,7 +152,7 @@ DroneCAN peripherals connected to PX4 can also be [configured using parameters v
|
||||
By convention, parameters named with the prefix [CANNODE\_](../advanced_config/parameter_reference.md#CANNODE_BITRATE) have prefined meaning, and may be documented in the parameter reference.
|
||||
`CANNODE_` parameters prefixed with `CANNODE_PUB_` and `CANNODE_SUB_` enable the peripheral to publish or subscribe the associated DroneCAN message.
|
||||
These allow DroneCAN peripherals to be configured to only subscribe and publish messages that they actually need (in the same way that PX4 uses the corresponding `UAVCAN_PUB_`/`UAVCAN_SUB_` parameters).
|
||||
Note that a peripheral might might not use `CANNODE_` parameters, in which case it may have to publish/subscribe to particular messages whether or not they are needed.
|
||||
Note that a peripheral might not use `CANNODE_` parameters, in which case it may have to publish/subscribe to particular messages whether or not they are needed.
|
||||
|
||||
The following sections provide additional detail on the PX4 and DroneCAN peripheral parameters used to enable particular features.
|
||||
|
||||
@@ -285,7 +285,7 @@ Note that DroneCAN ESCs should be on their own dedicated CAN interface(s) becaus
|
||||
|
||||
PX4 can control external LEDs on a connected DroneCAN peripheral using the standard DroneCAN [LightsCommand](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#lightscommand) message.
|
||||
Up to 2 lights acan be controlled.
|
||||
Each light can independently show [system status colours](../getting_started/led_meanings.md#ui-led), a fixed colour (commonly used for indciating aircraft orientation), or switch between both depending on arm state.
|
||||
Each light can independently show [system status colours](../getting_started/led_meanings.md#ui-led), a fixed colour (commonly used for indicating aircraft orientation), or switch between both depending on arm state.
|
||||
|
||||
See [DroneCAN Lights](lights.md) for full configuration details.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user