# UAVCAN ESCs (Motor Controllers)
- UAVCAN has been specifically designed to deliver robust and reliable connectivity over relatively large distances. It enables safe use of ESCs on bigger vehicles and communication redundancy.
- The bus is bi-directional, enabling health monitoring and diagnostics.
- Wiring is less complicated as you can have a single bus for connecting all your ESCs and other UAVCAN peripherals.
- Setup is easier as you configure ESC numbering by manually spinning each motor (for most types of UAVCAN ESCs).
# PX4 Supported ESC
PX4 is compatible with any/all UAVCAN v0 ESCs. At time of writing PX4 does not yet support UAVCAN v1.0.
UAVCAN is generally speaking a plug'n'play protocol. The main difference between UAVCAN ESCs from a setup perspective is that the physical connectors and the software tools used to configure the motor order and direction may be different.
Some popular UAVCAN ESC firmware/products include:
Sapog (opens new window) firmware; an advanced open source sensorless PMSM/BLDC motor controller firmware designed for use in propulsion systems of electric unmanned vehicles.
Zubax Myxa (opens new window) - High-end PMSM/BLDC motor controller (FOC ESC) for light unmanned aircraft and watercraft. :::note ESC based on the Zubax Telega sensorless FOC motor control technology (e.g., Zubax Myxa, Mitochondrik, Komar, etc.) 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 (opens new window) or to use Zubax Robotic's professional tuning service. Questions on this matter should be addressed to: email@example.com. :::
Zubax Mitochondrik (opens new window) - integrated sensorless PMSM/BLDC motor controller chip (used in ESCs and integrated drives)
A number of others are listed here (opens new window)
This list is not exhaustive/complete. If you know of another ESC, please add it to the list!
Mitochondrik based drives and ESC:
There are many other commercially available ESCs; please add new links as you find them!
Connect all of the on-board UAVCAN devices into a chain and make sure the bus is terminated at the end nodes. The order in which the ESCs are connected/chained does not matter.
For more information see UAVCAN > Wiring.
All UAVCAN ESCs share the same connection architecture/are wired the same way. Note however that the actual connectors differ (e.g. Zubax Orel 20 and Holybro Kotleta20 use Dronecode standard connectors (JST-GH 4 Pin) - while VESCs do not).
# PX4 Configuration
In order to use a UAVCAN ESC with PX4 you will need to enable the UAVCAN driver:
- Power the vehicle using the battery (you must power the whole vehicle, not just the flight controller) and connect QGroundControl.
- Navigate to the Vehicle Setup > Parameters screen. :::note Parameters explains how to find and set parameters. :::
- Set UAVCAN_ENABLE to the value Sensors and Motors (3) and then reboot the flight controller. This enables automatic enumeration of the motors (ESC) as described in the next section.
- (Optional) Set UAVCAN_ESC_IDLT to 1 in order to ensure that the motors are always running at least at the idle throttle while the system is armed. :::note Some systems will not benefit from this behavior, e.g. glider drones). :::
# ESC Setup
While UAVCAN devices are generally plug'n'play you will still need to enumerate (number) each of the ESC used in your system and set their direction so that they can be identified/controlled by PX4.
The ESC index and direction must match/map to the Airframe Reference for the vehicle type. ESC indexes from 0-7 map to MAIN 1-8, while ESC indexes 8-15 map to AUX 1-8.
The mechanism for enumerating each type of UAVCAN ESC is different (look up the instructions in your ESC's manual). Setup information for some UAVCAN ESCs is provided below.
# Sapog ESC Enumeration using QGroundControl
This section shows how to enumerate any Sapog-based (opens new window)-based ESCs "automatically" using QGroundControl.
You can skip this section if there is only one ESC in your setup, because the ESC index is already set to zero by default.
To enumerate the ESC:
Power the vehicle with a battery and connect to QGroundControl
Navigate to Vehicle Setup > Power in QGC.
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.
Manually turn each motor in the correct direction of its rotation (as specified in the Airframe Reference), starting from the first motor and finishing with the last motor. Each time you turn a motor, you should hear a confirmation beep.
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). :::
- After the last motor is enumerated, the confirmation sound should change to indicate that the enumeration procedure is complete.
- Reboot PX4 and the Sapog ESCs to apply the new enumeration IDs.
The following video demonstrates the process:
# Manual ESC Enumeration using Sapog
We recommend automated Sapog ESC Enumeration using QGroundControl shown above rather than manual enumeration (as it is easier and safer).
You can manually configure the ESC index and direction using the UAVCAN GUI Tool (opens new window). This assigns the following Sapog configuration parameters for each enumerated ESC:
See Sapog reference manual (opens new window) for more information about the parameters.
# Myxa ESC Setup
There is some guidance here: Quick start guide for Myxa v0.1 (opens new window) (Zubax blog).
# VESC ESC Setup
For VESC ESCs (opens new window) the preferred tool for motor enumeration is the VESC tool (opens new window). In addition to the normal motor configuration that you will have to setup in the VESC tool, you will also need to properly setup the app configuration. The recommended app setup is as follows:
|App to use|
|Can Status Message Mode|
|CAN Baud Rate|
|UAVCAN ESC Index|
VESC ID should have the same motor numbering as in PX4 convention, starting at
1 for top-right motor,
2 for bottom-left motor etc. However the
UAVCAN ESC Index starts from
0, and as such it is always one index lower than the
VESC ID. For example, in a quadcopter the bottom left motor will have
VESC ID = 2 and
UAVCAN ESC Index = 1.
CAN Baud Rate must match the value set in UAVCAN_BITRATE.
# Motors not spinning when armed
If the PX4 Firmware arms but the motors do not start to rotate, check that parameter
UAVCAN_ENABLE=3 to use UAVCAN ESCs. If the motors do not start spinning before thrust is increased, check
# UAVCAN devices dont get node ID/Firmware Update Fails
PX4 requires an SD card for UAVCAN node allocation and during firmware update (which happen during boot). Check that there is a (working) SD card present and reboot.