I’ve been finalizing my build in this thread and today I attempted to spin up the motors and only one VESC appears to be working correctly.
Connection with Nunchuck was OK.
CANbus communication was OK.
VESC HW version: 4.10 from Enertion’s recent batch.
FW version : 2.5
BLDC version : 2.5
When I spin up the motors, only the slave VESC spins up as it should, the other one doesn’t budge.
I switched motor/VESC connection to verify motors are OK and I can conclude that the slave VESC and both motors are OK, there is a problem with the master VESC.
When I try to spin up the motor gently, it jitters: VIDEO
When I try to spin up the motor abruptly, it jolts, I get red LED and the VESC loses connection with the BLDC tool: VIDEO
I’ve reproduced this problem with two dfferent power supplies as well as my 12S pack.
I’ve briefly seen a variety of errors in the realtime data window: DRV_8302, UNDER_VOLTAGE and ABS_OVER_CURRENT, but generally there is no fault reported.
When I try to run motor detection get an error code saying “bad detection data received” or something along those lines. Detection obviously fails.
I’ve tried reflashing the firmware and reloading the R-SPEC 6355 default XML file, which doesn’t change anything.
I’ve inspected the VESC under a loupe and cannot find any obvious bridging.
Here are the high-res pictures if you want to pixel-peep:
I’m afraid I may have received a bad VESC from Enertion.
Can anyone come up with additional troubleshooting tips ?