VESC Pronto

The regeneration (or braking) current can reach the same continuous and burst current ratings as the controller. However, the actual limit depends on your BMS and, more specifically, your battery cells, which determine how much current can safely flow back into the battery.

Additionally, the values for motor current, motor brake current, battery current, and battery regeneration current can all be individually configured using VESC Tool to suit your specific application, hardware or performance requirements.

The Maxim and Pronto controllers have the UART-pins shared with the hall sensor pins, so when using sensors the reverse and cruise control functions in the ADC app cannot be used at the same time as hall sensors or encoders. It is possible to use a simple lisp-script to simulate these functions with other pins depending on which pins you have available. The following example activates the reverse-button when the ACD2-input goes above 1V.

(app-adc-detach 2 1)
(loopwhile t {
(app-adc-override 2 (if (> (get-adc 1) 1.0) 1.0 0.0))
(sleep 0.01)
})

You can read more about those extensions here

https://github.com/vedderb/bldc/blob/master/lispBM/README.md#app-adc-detach
https://github.com/vedderb/bldc/blob/master/lispBM/README.md#app-adc-override

On the Maxim and Pronto controllers the motor sensors and UART share the same pins, so the UART app must be disabled when using sensors. This will affect the Hall 2 input as that is where UART TX is. In Firmware 7+ this should be done automatically, but on older firmware the UART-app must be disabled manually.

All Pronto-controllers shipped until 2026-xx have a hardware bug for the ABI encoder input, where the A and I signals are swapped. This can be resolved by swapping the A and I cables on the encoder.

The shutdown behavior can be configured using the shutdown-mode in the app settings. By default it is set to ALWAYS ON, which makes the controller stay on until power is removed. Changing the shutdown mode to ALWAYS OFF means that it will turn off after disconnecting the EN-pin.

Our dual motor controllers (Duet and Duet XS) only support hall sensors on the sensor ports. Some encoders might work on Motor 1, but Motor 2 only works with hall sensors or sensorless. HFI works on both motors for motors that are suited for HFI.

You can find CAN-bus documentation here

https://github.com/vedderb/bldc/blob/master/documentation/comm_can.md

The controller current rating is for the phase current and the input current will always be lower than the phase current. You can read about that in our article here

Choosing a Motor Controller

However, if you are driving a low inductance motor close to full duty cycle it is possible that the input current will exceed the rating of the fuse and blow it, especially if you are using liquid cooling. In that case you have to use an external fuse and bypass the fuse on the controller with a bus bar. Unfortunately we have not found fuses in this size rated for more than 350A.

Yes, we offer a discount when ordering 3+ and 10+ units which can be seen on the website. For order quantities over 50 units please send your business details and order requirements to info@vesclabs.com, and our team will provide a customized quote and lead time.

Yes, we do. Please contact us at info@vesclabs.com with your project requirements and specifications, and our team will assist you with tailored OEM or custom solutions.

Yes, we do. Please send the details of your project and institution to info@vesclabs.com, and our team will review your request.

Our partner Oliver, also known as Electricfox, offers paid consulting services for BMS and motor controller integration, setup, tuning and load testing. His website is

https://electricfox.de/

At the bottom of the page you can find different options to contact Oliver