ESC support in UAVCAN v1

romain145 · February 18, 2021, 3:32pm

Hi,
I have some questions about supporting an ESC with UAVCAN v1.

This document is a good starting point:

UAVCAN/public_regulated_data_types/blob/master/reg/drone/service/actuator/esc/_.0.1.uavcan

# The electronic speed controller (ESC) service is designed for controlling and monitoring electric drives.
# From the standpoint of this standard, an electric drive is just a special case of a servo. For generality,
# COTS electric drives are recommended to also support the servo interface defined in the adjacent namespace.
#
# ESCs (drives) are segregated into groups. Each ESC in a group has an index that is unique within the group.
# Drives in a group are commanded synchronously by publishing a message containing an array of setpoints.
# There are several subjects defined:
#
#   - Setpoint array subject. Every participant subscribes to the same setpoint subject.
#     Every message is consumed by all participants according to their index in the group.
#     The setpoint subject defines the group. There may be an arbitrary number of such groups in the network.
#
#   - Readiness subject. Every participant subscribes to the same readiness control subject which is used to command
#     the state of the group: sleep, standby, or engaged. In many cases there will be one global subject controlling
#     the state of the entire system; in other cases there will be dedicated controls on a per-subsystem basis.
#
#   - Individual subjects, whose subject-ID is offset from the setpoint subject-ID `S` as a function of
#     group member index `i` as specified below.
#
#                                                   SUBJECT

This file has been truncated. show original

There are no regulated data types specific to ESCs.
How to send commands to the ESC?
Commands would be setpoints like: speed, torque, duty etc…
Configuration parameters are also required to set maximum speed, current, acceleration, etc…

Are there types defined somewhere else, or do they need to be defined for ESCs? In which case I’d be happy to help.
Thanks

pavel.kirienko · February 18, 2021, 8:59pm

The document you referenced is the ESC network service specification you are looking for. It is not yet stable (it’s v0.1 at the moment), but it is complete and there is a chance that it will make it to v1.0 with no substantial changes.

The document has a diagram that is intended to explain how to implement and use the service:

#                                                   SUBJECT
#                                                   NAME        SUBJECT TYPE                                SUBJECT-ID
#  +----------------+
#  |   Controller   |---------+------------+----... setpoint    reg.drone.service.actuator.common.sp.*      S
#  |                |-------+-)----------+-)----... readiness   reg.drone.service.common.Readiness          S+1
#  +----------------+       | |          | |
#   ^ ^ ^ ^  ^ ^ ^ ^        v v          v v
#   | | | |  | | | |   +---------+  +---------+
#   | | | |  | | | |   |Drive i=0|  |Drive i=1| ...
#   | | | |  | | | |   +---------+  +---------+
#   | | | |  | | | |     | | | |      | | | |
#   | | | |  | | | +-----+ | | |      | | | |       feedback    reg.drone.service.actuator.common.Feedback   S+(i+1)*5+1
#   | | | |  | | +---------+ | |      | | | |       status      reg.drone.service.actuator.common.Status     S+(i+1)*5+2
#   | | | |  | +-------------+ |      | | | |       power       reg.drone.physics.electricity.PowerTs        S+(i+1)*5+3
#   | | | |  +-----------------+      | | | |       dynamics    reg.drone.physics.dynamics.rotation.PlanarTs S+(i+1)*5+4
#   | | | |                           | | | |
#   | | | +---------------------------+ | | |
#   | | +-------------------------------+ | |
#   | +-----------------------------------+ |
#   +---------------------------------------+

For example, if you need to publish a setpoint for a group of six ESC, you publish a message of type reg.drone.service.actuator.common.sp.Vector6.0.1; if you want RPM and such, you subscribe to six subjects (one per ESC) of type reg.drone.physics.dynamics.rotation.PlanarTs.0.1; and so on.

It is also possible to apply constraints on acceleration, speed, and torque, but for that, you will need to also support the Servo service (it is very similar to ESC).

Configuration parameters are currently not regulated by DS-015 (neither they were in v0), but this may change at some point in the future if there is interest.