Installed and busted the slave 3 times.
All three vesc were freshly repaired, thinking that they were not actually repaired made me simply swap them out then i would bust the next one… A little stupid of me but i had my dough’s
I’m not asking for any help here, just logging the info.
All three had the same behavior, they work fine when working alone configured as master. When i set them up as a slave, both motors work fine for about 1minute then the slave drv will blow out of nowhere.
So here my actions i will take in hopes of isolating the problem:
-replace the old crusty 3300uf caps that i got in a sketchy electronic shop with new ones
-disable the traction control
-run the motors in sensorless mode (currently sensored)
-replace the new 3300uf caps ( if it doesnt work) with 6 680uf caps(like the capacitor boards)
I’m open to other actions to take, but like i said, i’m just logging what i’m doing.
For my short failed stint with a dual motor board I ran them in chained serial. Not sure it makes any difference, but it might be give you some debugging data points.
Tie the TX line to both VESC’s, but of course the RX line only comes back from one.
I do think that bigger caps might help - that jolt on first start is likely what caused my failure. Both motors started at exactly the same time. Next time I’m going to run separate serial channels and add a slight delay to one of the motor starts.
