mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-22 21:53:33 +08:00
New Crowdin translations - zh-CN (#25202)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
co-authored by
Crowdin Bot
parent
ce4dfaf39a
commit
a01f39707e
@@ -8,6 +8,6 @@ Additional documentation on how to use Babel/other SLCAN adapters, the DroneCAN
|
||||
|
||||
## Debugging with Zubax Babel
|
||||
|
||||
A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://zubax.com/products/babel) in combination with the [GUI tool](https://dronecan.github.io/GUI_Tool/Overview/).
|
||||
A great tool to debug the transmission on the CAN bus is the [Zubax Babel](https://shop.zubax.com/products/zubax-babel) in combination with the [GUI tool](https://dronecan.github.io/GUI_Tool/Overview/).
|
||||
|
||||
They can also be used independently from Pixhawk hardware in order to test a node or manually control DroneCAN enabled ESCs.
|
||||
|
||||
+11
-11
@@ -38,7 +38,7 @@ Supported hardware includes (this is not an exhaustive list):
|
||||
|
||||
- Airspeed sensors
|
||||
- [Holybro High Precision DroneCAN Airspeed Sensor - DLVR](https://holybro.com/collections/sensors/products/high-precision-dronecan-airspeed-sensor-dlvr)
|
||||
- [RaccoonLab airspeed sensor](https://docs.raccoonlab.co/guide/airspeed)
|
||||
- [RaccoonLab airspeed sensor](https://docs.raccoonlab.co/guide/airspeed/)
|
||||
- [Thiemar airspeed sensor](https://github.com/thiemar/airspeed)
|
||||
|
||||
- GNSS receivers for GNSS (GPS, GLONASS, BeiDou, and so on)
|
||||
@@ -140,8 +140,8 @@ Sensor parameters may not exist (be visible in QGC) until you have enabled the a
|
||||
For example, [SENS_FLOW_MINHGT](../advanced_config/parameter_reference.md#SENS_FLOW_MINHGT) does not exist until [UAVCAN_SUB_FLOW](../advanced_config/parameter_reference.md#UAVCAN_SUB_FLOW) is enabled.
|
||||
:::
|
||||
|
||||
For example, to use a connected DroneCAN smart battery you would enable the [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT) parameter, which would subscribe PX4 to receive [BatteryInfo](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#batteryinfo) DroneCAN messages.
|
||||
If using a peripheral that needs to know if PX4 is armed, you would need to set the [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) parameter so that PX4 starts publishing [ArmingStatus](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#armingstatus) messages.
|
||||
For example, to use a connected DroneCAN smart battery you would enable the [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT) parameter, which would subscribe PX4 to receive [BatteryInfo](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#batteryinfo) DroneCAN messages.
|
||||
If using a peripheral that needs to know if PX4 is armed, you would need to set the [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) parameter so that PX4 starts publishing [ArmingStatus](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#armingstatus) messages.
|
||||
|
||||
The parameter names are prefixed with `UAVCAN_SUB_` and `UAVCAN_PUB_` to indicate whether they enable PX4 subscribing or publishing.
|
||||
The remainder of the name indicates the specific message/feature being set.
|
||||
@@ -165,7 +165,7 @@ The DroneCAN sensor parameters/subscriptions that you can enable are (in PX4 v1.
|
||||
- [UAVCAN_SUB_DPRES](../advanced_config/parameter_reference.md#UAVCAN_SUB_DPRES): Differential pressure
|
||||
- [UAVCAN_SUB_FLOW](../advanced_config/parameter_reference.md#UAVCAN_SUB_FLOW): Optical flow
|
||||
- [UAVCAN_SUB_GPS](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS): GPS
|
||||
- [UAVCAN_SUB_GPS_R](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS_R)<Badge type="tip" text="PX4 v1.15" />: Subscribes to GNSS relative message ([RelPosHeading](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#relposheading)).
|
||||
- [UAVCAN_SUB_GPS_R](../advanced_config/parameter_reference.md#UAVCAN_SUB_GPS_R)<Badge type="tip" text="PX4 v1.15" />: Subscribes to GNSS relative message ([RelPosHeading](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#relposheading)).
|
||||
Only used for logging in PX4 v1.15.
|
||||
- [UAVCAN_SUB_HYGRO](../advanced_config/parameter_reference.md#UAVCAN_SUB_HYGRO): Hygrometer
|
||||
- [UAVCAN_SUB_ICE](../advanced_config/parameter_reference.md#UAVCAN_SUB_ICE): Internal combustion engine (ICE).
|
||||
@@ -201,15 +201,15 @@ Position of rover is established using RTCM messages from the RTK base module (t
|
||||
PX4 DroneCAN parameters:
|
||||
|
||||
- [UAVCAN_PUB_RTCM](../advanced_config/parameter_reference.md#UAVCAN_PUB_RTCM):
|
||||
- Makes PX4 publish RTCM messages ([RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream)) to the bus (which it gets from the RTK base module via QGC).
|
||||
- Makes PX4 publish RTCM messages ([RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream)) to the bus (which it gets from the RTK base module via QGC).
|
||||
|
||||
Rover module parameters (also [set using QGC](#qgc-cannode-parameter-configuration)):
|
||||
|
||||
- [CANNODE_SUB_RTCM](../advanced_config/parameter_reference.md#CANNODE_SUB_RTCM) tells the rover that it should subscribe to [RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream) RTCM messages on the bus (from the moving base).
|
||||
- [CANNODE_SUB_RTCM](../advanced_config/parameter_reference.md#CANNODE_SUB_RTCM) tells the rover that it should subscribe to [RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream) RTCM messages on the bus (from the moving base).
|
||||
|
||||
:::info
|
||||
You could instead use [UAVCAN_PUB_MBD](../advanced_config/parameter_reference.md#UAVCAN_PUB_MBD) and [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD), which also publish RTCM messages (these are newer).
|
||||
Using the [RTCMStream](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#rtcmstream) message means that you can implement moving base (see below) at the same time.
|
||||
Using the [RTCMStream](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#rtcmstream) message means that you can implement moving base (see below) at the same time.
|
||||
:::
|
||||
|
||||
##### Rover and Moving Base
|
||||
@@ -219,8 +219,8 @@ In this setup the vehicle has a _moving base_ RTK GPS and a _rover_ RTK GPS.
|
||||
|
||||
These parameters can be [set on moving base and rover RTK CAN nodes](#qgc-cannode-parameter-configuration), respectively:
|
||||
|
||||
- [CANNODE_PUB_MBD](../advanced_config/parameter_reference.md#CANNODE_PUB_MBD) causes a moving base GPS unit to publish [MovingBaselineData](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#movingbaselinedata)RTCM messages onto the bus (for the rover)
|
||||
- [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD) tells the rover that it should subscribe to [MovingBaselineData](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#movingbaselinedata) RTCM messages on the bus (from the moving base).
|
||||
- [CANNODE_PUB_MBD](../advanced_config/parameter_reference.md#CANNODE_PUB_MBD) causes a moving base GPS unit to publish [MovingBaselineData](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#movingbaselinedata)RTCM messages onto the bus (for the rover)
|
||||
- [CANNODE_SUB_MBD](../advanced_config/parameter_reference.md#CANNODE_SUB_MBD) tells the rover that it should subscribe to [MovingBaselineData](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#movingbaselinedata) RTCM messages on the bus (from the moving base).
|
||||
|
||||
For PX4 you will also need to set [GPS_YAW_OFFSET](../advanced_config/parameter_reference.md#GPS_YAW_OFFSET) to indicate the relative position of the moving base and rover: 0 if your Rover is in front of your Moving Base, 90 if Rover is right of Moving Base, 180 if Rover is behind Moving Base, or 270 if Rover is left of Moving Base.
|
||||
|
||||
@@ -270,7 +270,7 @@ If the rangefinder is connected via DroneCAN (whether inbuilt or separate), you
|
||||
|
||||
PX4 DroneCAN parameters:
|
||||
|
||||
- [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) ([Arming Status](https://dronecan.github.io/Specification/7._List_of_standard_data_types/#armingstatus)): Publish when using DroneCAN components that require the PX4 arming status as a precondition for use.
|
||||
- [UAVCAN_PUB_ARM](../advanced_config/parameter_reference.md#UAVCAN_PUB_ARM) ([Arming Status](https://dronecan.github.io/Specification/1._Introduction//7._List_of_standard_data_types/#armingstatus)): Publish when using DroneCAN components that require the PX4 arming status as a precondition for use.
|
||||
|
||||
### ESC & Servos
|
||||
|
||||
@@ -324,6 +324,6 @@ If successful, the firmware binary will be removed from the root directory and t
|
||||
## Useful Links
|
||||
|
||||
- [Home Page](https://dronecan.github.io) (dronecan.github.io)
|
||||
- [Protocol Specification](https://dronecan.github.io/Specification) (dronecan.github.io)
|
||||
- [Protocol Specification](https://dronecan.github.io/Specification/1._Introduction/) (dronecan.github.io)
|
||||
- [Implementations](https://dronecan.github.io/Implementations/) (dronecan.github.io)
|
||||
- [Cyphal/CAN Device Interconnection](https://wiki.zubax.com/public/cyphal/CyphalCAN-device-interconnection?pageId=2195476) (kb.zubax.com)
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## CAN Power Connectors
|
||||
|
||||
CAN power connectors are designed for light unmanned aerial (UAV) and other vehicles for providing power over CAN using [CAN power cables](https://docs.raccoonlab.co/guide/pmu/wires/).
|
||||
CAN power connectors are designed for light unmanned aerial (UAV) and other vehicles for providing power over CAN using [CAN power cables](https://docs.raccoonlab.co/guide/pmu/wires.html).
|
||||
|
||||
There are two types of devices:
|
||||
|
||||
|
||||
@@ -8,33 +8,8 @@ While it can be controlled using traditional PWM input, it is designed to operat
|
||||
|
||||
Multiple vendors sell ESC hardware that runs sapog firmware:
|
||||
|
||||
- [Zubax Orel 20](https://zubax.com/products/orel_20)
|
||||
- [Holybro Kotleta20](https://holybro.com/products/kotleta20)
|
||||
|
||||
<style>
|
||||
#image_container {
|
||||
height: 100%;
|
||||
width: 100%;
|
||||
display: flex;
|
||||
}
|
||||
.image_column {
|
||||
width: 33%;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
</style>
|
||||
|
||||
<div id="image_container">
|
||||
<div class="image_column">
|
||||
<img src="../../assets/peripherals/esc_uavcan_zubax_orel20/orel20_top.jpg" alt="Orel20 - Top"/>
|
||||
<br><a href="https://zubax.com/products/orel_20">Zubax Orel 20</a>
|
||||
</div>
|
||||
<div class="image_column">
|
||||
<img src="../../assets/peripherals/esc_uavcan_holybro_kotleta20/kotleta20_top.jpg" alt="Holybro Kotleta20 top" />
|
||||
<br><a href="https://holybro.com/products/kotleta20">Holybro Kotleta20</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## 硬件安装
|
||||
|
||||
ESCs are connected to the CAN bus using a Pixhawk standard 4 pin JST GH cable.
|
||||
@@ -81,15 +56,15 @@ To enumerate the ESC:
|
||||
|
||||
3. Start the process of ESC auto-enumeration by pressing the **Start Assignment** button, as shown on the screenshot below.
|
||||
|
||||

|
||||

|
||||
|
||||
You will hear a sound indicating that the flight controller has entered the ESC enumeration mode.
|
||||
You will hear a sound indicating that the flight controller has entered the ESC enumeration mode.
|
||||
|
||||
4. Manually turn each motor in the correct direction of its rotation (as specified in the [Airframe Reference](../airframes/airframe_reference.md)), starting from the first motor and finishing with the last motor.
|
||||
Each time you turn a motor, you should hear a confirmation beep.
|
||||
Each time you turn a motor, you should hear a confirmation beep.
|
||||
|
||||
::: info
|
||||
Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration).
|
||||
::: info
|
||||
Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration).
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# Zubax Telega ESCs
|
||||
|
||||
Zubax Telega is a high end, proprietary sensorless FOC motor control technology.
|
||||
It is used in multiple products, including the [Zubax Myxa](https://zubax.com/products/myxa) ESC, [Zubax Mitochondrik](https://zubax.com/products/mitochondrik) motor controller module, and Zubax Sadulli integrated drive.
|
||||
It is used in multiple products, including the [Zubax Myxa](https://shop.zubax.com/products/zubax-myxa) ESC, [Zubax Mitochondrik](https://shop.zubax.com/products/mitochondrik) motor controller module, and Zubax Sadulli integrated drive.
|
||||
|
||||
While Telega can be controlled using traditional PWM input, it is designed to operate over CAN bus using [DroneCAN](index.md).
|
||||
|
||||
:::info
|
||||
ESCs based on Zubax Telega require non-trivial tuning of the propulsion system in order to deliver adequate performance and ensure robust operation.
|
||||
Users who lack the necessary tuning expertise are advised to either [purchase pre-tuned UAV propulsion kits](https://zubax.com/products/uav_propulsion_kits) or to use Zubax Robotic's professional tuning service.
|
||||
Users who lack the necessary tuning expertise are advised to either [purchase pre-tuned UAV propulsion kits](https://zubax.com/products#electric-drives) or to use Zubax Robotic's professional tuning service.
|
||||
Questions on this matter should be addressed to: [support@zubax.com](mailto:support@zubax.com).
|
||||
:::
|
||||
|
||||
@@ -15,10 +15,9 @@ Questions on this matter should be addressed to: [support@zubax.com](mailto:supp
|
||||
|
||||
## 购买渠道
|
||||
|
||||
- [Zubax Myxa](https://zubax.com/products/myxa): High-end PMSM/BLDC motor controller (FOC ESC) for light unmanned aircraft and watercraft.
|
||||
- [Zubax Mitochondrik](https://zubax.com/products/mitochondrik): Integrated sensorless PMSM/BLDC motor controller chip (used in ESCs and integrated drives)
|
||||
- [Zubax Komar](https://shop.zubax.com/products/komar-motor-controller-open-hardware-reference-design-for-mitochondrik?variant=32931555868771): Open hardware reference design for Mitochondrik
|
||||
- [Zubax Sadulli Integrated Drive](https://shop.zubax.com/collections/integrated-drives/products/sadulli-integrated-drive-open-hardware-reference-design-for-mitochondrik?variant=27740841181283)
|
||||
- [Zubax Myxa](https://shop.zubax.com/products/zubax-myxa): High-end PMSM/BLDC motor controller (FOC ESC) for light unmanned aircraft and watercraft.
|
||||
- [Zubax Mitochondrik](https://shop.zubax.com/products/mitochondrik): Integrated sensorless PMSM/BLDC motor controller chip (used in ESCs and integrated drives)
|
||||
- [Zubax Komar](https://shop.zubax.com/products/zubax-ad0510-komar-esc?variant=32931555868771): Open hardware reference design for Mitochondrik
|
||||
|
||||
## 硬件安装
|
||||
|
||||
@@ -27,10 +26,10 @@ For more information, refer to the [CAN Wiring](../can/index.md#wiring) instruct
|
||||
|
||||
## Firmware Setup
|
||||
|
||||
Motor enumeration for [Telega-based ESCs](https://zubax.com/products/telega) is usually performed using the [Kucher tool](https://files.zubax.com/products/com.zubax.kucher/) (or less "GUI-friendly" [DroneCAN GUI Tool](https://dronecan.github.io/GUI_Tool/Overview/)).
|
||||
Motor enumeration for [Telega-based ESCs](https://telega.zubax.com/) is usually performed using the [Kucher tool](https://files.zubax.com/products/com.zubax.kucher/) (or less "GUI-friendly" [DroneCAN GUI Tool](https://dronecan.github.io/GUI_Tool/Overview/)).
|
||||
Telega does NOT support automatic enumeration by spinning the motor.
|
||||
|
||||
There is some guidance here: [Quick start guide for Myxa v0.1](https://forum.zubax.com/t/quick-start-guide-for-myxa-v0-1/911) (Zubax blog).
|
||||
There is some guidance here: [Quick start guide for Myxa v0.1](https://forum.zubax.com/t/quick-start-guide-for-myxa/911) (Zubax blog).
|
||||
|
||||
Telega ESCs also require other motor setup and configuration for reliable performance. See the above guide and other Zubax documentation for more information.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user