Velocity CAN ESCs¶
The Velocity range of ESCs provide motor control for the aerospace sector, with a high degree of reliability.
Designed for driving extremely large motors for heavy-lift applications, the Velocity range of ESCs is available in power levels above 20kW
- Up to 18S (75V) battery packs
- Sustained currents above 300A
- Compact design
- Fully isolated communication interface
- Designed and manufactured in Australia
The Velocity ESC provies a CAN communication interface for commands and telemetry. A traditional digital PWM interface is also supported.
Additionally, the Velocity ESC provides an optional hardware interlock for increased operator safety.
Connection and Configuration¶
The Velocity ESC uses the PiccoloCAN protocol. Originally developed for the Piccolo autopilot, the protocol is now natively supported by Ardupilot
To enable communication with the Velocity ESCs using PiccoloCAN, the following parameters must be set.
- Set CAN_D1_PROTOCOL = 4 (PiccoloCAN)
- Set CAN_P1_DRIVER = 1 (First driver) to specify that the ESCs are connected to the CAN1 port
- Set MOT_PWM_MIN = 1000 and MOT_PWM_MAX = 2000 so ArduPilot uses an output range that matches the ESCs input range
The following advanced configuration parameters allow adjustment of the Velocity ESC operation.
By default, all configured motor channels are used to send control commands to Velocity ESCs. These control messages are transmitted by the autopilot at 50Hz.
Logging and Reporting¶
Velocity ESCs provide comprehensive telemetry information back to the autopilot which is recorded in the autopilot’s onboard log, and can be viewed in any ArduPilot compatible log viewer. This information includes:
- ESC Temperature
- Motor current
- Motor Temperature (when used with an external sensor)
This information (except the motor temperature) can also be viewed in real-time using a ground station. If using the Mission Planner go to the Flight Data screen’s status tab and look for (e.g.) esc1_rpm.
Sending ESC data to the GCS requires using MAVLink2. Please check the appropriate SERIALx_PROTOCOL parameter is 2 (where “x” is the serial port number used for the telemetry connection).