VESC can't control motor anymore

After only about 15km on this VESC (egreenmotion) it stopped working and when I pull the trigger on the remote a red LED flashes 3 times, stops and flashes another 3 times. BLDC tool can connect fine but also cannot controll the motor. Detection fails, LED response is the same.

are you getting any faults?

type “faults” in terminal and post results. If it’s a DRV failure, you’re gonna need a new one.

returns: FAULT_CODE_DRV8302

The following faults were registered since start:

Fault            : FAULT_CODE_DRV8302
Current          : 0.1
Current filtered : -0.2
Voltage          : 40.49
Duty             : 0.02
RPM              : 10.1
Tacho            : 4
Cycles running   : 4
TIM duty         : 889
TIM val samp     : 456
TIM current samp : 22970
TIM top          : 45028
Comm step        : 4
Temperature      : 30.70

Fault            : FAULT_CODE_DRV8302
Current          : 0.2
Current filtered : -0.2
Voltage          : 40.49
Duty             : 0.03
RPM              : 2.0
Tacho            : 5
Cycles running   : 4
TIM duty         : 1160
TIM val samp     : 609
TIM current samp : 21453
TIM top          : 41687
Comm step        : 5
Temperature      : 30.70

Fault            : FAULT_CODE_DRV8302
Current          : -1.7
Current filtered : -0.3
Voltage          : 40.49
Duty             : 0.03
RPM              : 1.9
Tacho            : 6
Cycles running   : 4
TIM duty         : 1160
TIM val samp     : 609
TIM current samp : 21453
TIM top          : 41687
Comm step        : 6
Temperature      : 30.73

You will have to get it repaired or replaced . If you dont have warranty talk to @JohnnyMeduse .

What is the KV of your motor and what voltage are you running?

sk3 192kv @10s6p

for some reason when I connected to the vesc after it stopped worrking “Sensorless - Communication Mode” under Motor Configuration > BLDC was set to “delay” instead of “intergrated”. I don’t recall doing that.

and here is a video of the issue

You have buggy firmware, as shown by the 50.00 max current ramp step. In addition to replacing the DRV8302 chip you need to update your f/w to get rid of the bug.

Bug details:

1 Like