During my last ride, going about 40kmh, VESCs cut out power and send me into wobbleland. After I come to a stop board wouldn’t respond, wand screen is frozen too.
After restarting, everything worked fine, but the master VESC (with the BLE module) has the red fault light on. Hooked it up to vesctool, printing faults in terminal gives no results.
Didn’t have metr logging on unfortunately.
What could it be?
I think you have to re create the situation in situ…becaue if you shut off your board, no faults will be shown…Going 40 km/hr and sudden wobble it is really dangerous. I think you should consult at @Trampa how to proceed for your safety before you go ridding again…
Talk about ironing out kinks… I’m going to try to remember to start metr religiously from here on out and I’ll encourage you to do the same. I am wondering if it was an overcurrent fault or a shorted phase lead.
With motors plugged in do you get any odd additional resistance when turning the motors, especially on the one plugged into the beach showing the fault light? Did you inspect the PCBs to see if any components look fried such as the DRV?
reflashed -> rebooted -> detection -> nrf pair = everything works but the red fault LED is still on on the master VESC…
Is there a way to retrieve what’s triggering it?
I will try to get some first hand information about that. Personally I would try to SWD PROG the unit and then see if the fault is still there. Either ist is software related or hardware realted. The best way to check the software side is a clean install via SWD.
Cleaned it thoroughly with qtips and denatured alcohol, then a couple layers of conformal coating.
Been doing 40km rides every day with no hiccups at all, fault LED is off.