This is my first time posting on this forum, but I’ve been reading posts for a while. I’m setting up the VESC for the first time and I keep getting the error “Bad detection result received” when I try to detect the motor. When I hit “start detection” the motor spins up to 24,000 ERPM stops accelerating and then jumps up to 45,000 ERPM momentarily before cutting off.
The motor spins fine using the arrow keys, however I cant get it to detect. I have tried varying the Current and Min ERPM to no avail (300-1200 ERPM & 1-6A current). The motor always spins fine but wont detect. I have also tried varying the Battery cutoff voltages and changing to a much shorter USB cable. There are currently no faults when I check the terminal
you’ve done most of what i’d do. I’d double check you have the belt/wheel disconnected if it might be part of the issue. I had one not detect when my belt was too tight, removed belt and detected fine.
@Hummmie the motor spins very smoothly. I’m pretty sure I’m not shorting the motor leads as I soldered them and used heat shrink. There is no exposed wire.
@Jinra Could I detect the motor using less cells (6s) and then use those setting with the full 8s setup?
are you saying that because it’s so high kv? wont the erpm limit keep him under the limit and all will be well? maybe if he just uses fewer cells for the test if it’s a test specific thing?
I can’t say for sure since i haven’t tried it personally, but i believe the vesc turns off if it hits the limit. Besides that, it’s a very inefficient setup with huge losses.
so hitting the limit would cause a shutdown as apposed to holding the motor to a max erpm that it could run at? oo. but why do you say his set-up is inefficient?
I believe I can use soft limits on the controller side though. I chose such a high rpm combination because I wanted very high torque for climbing hills. From my calculations I should be able to do a 25% grade hill at 20 mph