Board Info: Dual Motor x2 170 KV
x2 VESC 4.12
Li ion 12s3p Battery
VESC Firmware 2.52 (With Ackmaniacs BLDC Throttle Control Mod)
My board was working great until yesterday when one of my motors cut out and I couldnt get it running again. I got home started testing, after running motor detection I think that my Intergrator Limit and BEMF coupling values were wrong on both VESCs/Motors (This baffled me because im almost certain I set them correctly on initial setup).
I didnt think the board would even run with wrong values but anyway im still a novice really. My MASTER VESC seems to be fine with both motors detected and are responding normally via Remote Control but when I press Right on the keyboard either connected motor will stutter and barely spin (due to the incorrect values maybe?).
With my SLAVE VESC neither motor is detected and I get the “Bad Motor Detection Result” message, after typing “Fault” into the TERMINAL page I get “FAULT CODE NONE” and typing “Faults” it tells me “No Faults Registered Since Startup”. So, the LED lights all function as normal on SLAVE VESC the only thing is when I move it I hear the sound of spark but I cannot see where its coming from. This spark has also interfered with my battery indicator (blinks stating 0%). After rebooting the SLAVE VESC battery indicator returned to normal (84%). All my other BLDC settings look correct for my setup…
If you hear a sparking sound when moving the vesc it might be the cables from the battery coming into contact with something.
Check the soldering on the capacitor PCB and where the wires go onto the vesc.
Will propably have to remove the heat shrink.
First of all your settings are way to high. You have a 12S3P Li-Ion Battery so they can only give 60A (20A a cell) continuous.
But each of your VESCs is setup to 60A. You should set them to 30A max battery each. And also adjust the max watts setting according to that. So it should only be half the value. Because when both VESCs draw max power from the battery the amps get summarized.
Next thing is that you didn’t do the motor detection on the slave VESC. Could be that it got killed by that.
But it also could be that the motor detection get’s disturbed by the remote signal.
So you always have to disable the remote in the application settings by set the crontrol mode to disabled (as in the picture) when you want to do a motor detection. An the slave VESC gets the signal by the master. So you have to disable the control mode at the master. Then switch to the slave and do the motor detection there.
First read the configuration.
1.Select Disabled in your control mode. If you use the Nunchuk do it in the Nunchuk tab, if you use PPM do it in the PPM tab. If you have a dual setup and the 2 VESCs are connected by CAN then set it to disabled at the Master.
Write the application settings.
Change to the motor configuration
Read the configuration
Do the Motor Detection.
If the motor detection was successful click the apply button
write the configuration
do step 3 - 7 for the slave
go to the masters application tab
read the configuration
select your wanted control mode
write the configuration
So the best is disable the remotes control mode. Do the motor detection’s on both VESCs and then do the rest.
I had the sparking issue on my VESC, and it turned out that one of the contacts for the battery were coming off the board, so it would effectively “spark” making a popping sound.
I managed to pinpoint the problem as a bad contact on the cable from the capacitors going into the VESC. It had come loose and under vibration would disconnecct causing a spark then would reconnect once repositioned, I re-soldered this contact and the disconnection problem stopped.
My problem still is doing a motor detection, I keep receiving “Bad Detection Result Recieved” message. When I type “Fault” or “Faults” in the terminal page it tells me “No faults registered since startup” or “FAULT_CODE_NONE”. On top of this the LED lights are functioning as normal and when I use the directional keys within BLDC Tool the lights change accordingly but with no movement from the motor.
I have tested this motor on my MASTER VESC and it works fine so it rules out motor troubles. I then re-flashed the firmware on the SLAVE VESC but im still unable to run a motor detection. When I “Activate Sampling” in the Realtime Data tab I get seemingly normal responses in the graphs but nothing from the motor.
After re-flashing the firmware all my settings are Default Settings for VESC 4.12/Firmware 2.52.
Is there something more I can do to figure out the problem? Anyone got suggestions as to what this is?
I believe it upgraded after downloading the Throttle Mod (see above) I could try reflashing back to 2.18 but I dont think thats the problem, the Throttle Mod was working great (really improved the ride) for over a month. Is there any other way to check for faults other than the terminal page? Could something fry without showing a fault?
p.s I will do the pictures as soon as I get home. Gonna have to say goodbye to the heatshrink haha othwerwise the pics are useless
I am using a 12s3P battery and 5563 dual motors. Results that I disconnected one my vescs since I was having issues with my BMS. After solving the issue with my BMS the VESC didn’t turn on at all. I connected it to my computer and was not detected. There are no damages on the motor driver itself neither on the MCU. It only gets hot by the usb port. Sadly, I only rode my electric skateboard for a weekend.
Anybody has had this issued? did you have to replace something? I’ve checked the BOMs and I can get the parts if you ever had this type of issue.
haha othwerwise the pics are useless