Yes I am new to it. I have not been able to get the motor to reliably spin up. It works just fine in the wizard, but fails as soon as I try controlling it. As such analysis tools are kind of useless. I think the main issue is that most of the motors with hall sensors that are used with a VESC have around 14 motor pole pairs. This motor has two pole pairs. So when run in sensored mode the VESC is expecting the hall sensors to trigger more frequently. Pretty sure the fact that they were not made it think that there was a load on the shaft so it kept dumping more and more current into the motor because I had it on RPM PID control and it was stuck on 0 RPM.
As for braking, you do not want to feed voltage back into the power supply. Batteries can handle that just fine. MOSFETs not so much. The VESC is designed to work with batteries. Going through the interface of VESC tool there is no direct options for setting it up with a powersupply. Things like it does not ask you the voltage. It asks you the number of lipo cells.
One issue I have with the VESC is that while they have a UART interface, it is completely binary. That would be okay if they maintained libraries to interface with it, but they do not. Instead it is up to the community to maintain the libraries. The ‘stable’ Arduino library for it is able to interface with the 3.X firmware. The ‘dev’ Arduino library for it is able to interface with the 4.X. The current release version of the firmware is version 5.X
ODrive on the other hand has been designed to work with power supplies and batteries. They include a breaking resistor with the board so you do not need to worry about feeding power back into the power supply. They also have a human readable UART interface and they directly maintain the Arduino and Python libraries for interfacing with it. This means that my original goal of being able to provide detailed feedback on motor current and torque is very doable with the ODrive.