It all started this morning. I rode my board and it worked just fine. Then I came home after work for a short ride, but one motor was twitching and the other wouldn’t spin. This happened before and it was a bad motor, so i figured it would be the same thing. I have a 12s4p, 2 vesc-x, and 2 enertion rspec ghost motors. When I connect one of the vescs to either motor the both motors work just fine. Then I connect the other vesc to the computer, but it will not detect either motor and they will not spin even using the bldc tool using start detection. I am bypassing the remote and using my keyboard as my remote. When I check real time data and check the current, the graph is dancing like crazy on both vescs, but only the one vesc will output power. One vesc goes over 100 watts of power and the duty cycle goes past 70%. The malfunctioning one goes up about a half a percent and negative a half a percent. I have reset the vesc settings to default, but the problem still persists. The vescs are connected via can bus. It is a LHB build, so I have only done slight modifications to his work. I’ve checked all the connections and they are tight. Any advice would be greatly appreciated.
Have you tried to contact @longhairedboy and see what he thinks? I mean now that you have modified it, it’s yours but he might have some insight into your issue.
He would probably know the answer as he is an expert in his field, but I’m pretty confident it is the vesc.
Plug in the vesc that’s not working and go to the terminal section on the top of the bldc tool and type in faults and if there is some sort of fault or problem it will show you.
check the CAN bus connections. Replace the wires and solder in new ones, then run detection and save it on each motor and see what happens afterward.
also its worth noting that my boards are 100% hackable and although it voids my warranty to do whatever you want with them, i still stick around and help out and usually provide replacement parts at my cost when needed.