@HighHopes or at @marcos
How do you guys deal with the VESC's non-ideal behavior with slower-switching hardware? I've been able to observe in my own testing that the VESC firmware depends on hardware that switches really fast in order for the motor detection and control to perform as expected...