Vesc motor detection failing

So, I’m using a VESC 4.12 (Enertion), 2ea Zippy 5000mah batteries in series and a SK3 245Kv motor. I connected my vesc to the motor, vesc to the computer and finally i connected my vesc to the batteries.

I used the BLDC tool (v2.18 2.17) .

Whenever i do a motor detection my motor starts spinning, then stops and i hear a beep while the green led from the VESC blinks brighter (once, 1x short blink). The blue led stays on. After this i get an error “bad detection result received” and the motor detection says “Detection failed”.

@onloop may be able to help you. Have you tried to reflash the firmware?

I do hope so, no I haven’t… the BLDC toold does get the right motor parms though (read configuration)

So I flashed my firmware, now my vesc isn’t copatible with the bldc tol anymore :confused: Weired since i used the firmware folder from the bldc tool dir

I downloaded BLDC tool v2.15, it workes now, strange…

1 Like

Always also make sure that there is no load when doing a motor detection such as having no wheel or belt attached to the motor when you are doing a motor detection

The motor detection works?

Yea I think Vedder mentions this in his video.

Yes luckily it does

1 Like

It seems that anyone having issues with motor detection has fixed it by reflashing the firmware.

Hi, I’m getting the same problem as you. I installed version 2.15 and its corresponding firmware and I’m still getting “detection failed” and everything happens like you said "my motor starts spinning, then stops and i hear a beep while the green led from the VESC blinks brighter (once, 1x short blink). The blue led stays on. After this i get an error “bad detection result received” and the motor detection says “Detection failed”.

I also reflashed the fw when using bldc v 2.18 and still the same results.

I have the motor attached to the motor mount and to the truck but with no load on it.

I’m running the r-spec big motor (the one for mono-drive boards), the battery I connected the VESC to is a zippy flightmax 5000mah 25C 4s and these are my motor parameters before running detection.

any time you are having issues - also try a different and shorter USB cable. I recall Vedder mentioning this way back as a troubleshooting step.

worth a shot - GL!

You might need to change the battery cutoff. This happened to me when doing motor detection and changing the cutoff fixed the “bad detection result received” error.

8 Likes

That fixed it!!! Thank you! :DD

3 Likes

This also worked for me! I used a 12v lead acid battery and my cutoff was on 33v and end was on 30v. I changed this to 10v and 8v and then it worked like a charm. Entered the right values after motor detection and then changed it back to 33v and 30v. Thx a lot!

I signed up to the forum after months on ninja reading only to thank you for this post that saved me from a HUGE headache!

+1 Changing battery cutoff solved “bad detection result received” error. Thank you!

If none of these solutions work try upping the amps for the detection. Mine wasn’t detecting at 6A but I upped it to 8A and it worked like a charm.

1 Like

Great post, I just had same issue… motor detected before, then I changed some settings with volts and it would not detect… I reset to default, disocnnected, reconnected and it worked. Then I made my setting changes and saved… hope this does the trick!

Sorry guys,

but after extending these cables the engine stopped working. Is it because I have not sold them? Now i connect for fist time to bldc tool, update to 2.18 and try detection motor but dont move.

Im from spain. Sorry for my english

Thanks