I’m not a noob to computers, coms, serial, or usb. I’m a total noob to VESC, however, and this is the first time i’ve tried connecting one to BLDC tool.This is an Enertion VESC that went out with the most recent batch. I keep seeing how “easy” this is and figured most of the uissues would be ironed out by now, so maybe i’m doing something stupid.
I have the VESC powered by a DC power supply set to a max of 22 volts. It can only draw 5 amps from this unit. Should be plenty for bench testing and motor detection.
I installed the windows bldc tool and usb/serial drivers it came with. I made sure nothing was plugged into my serial port (i have a smart power strip that i use on my desk). I Connected the USB cable to the VESC and my PC. plugged in the motor phase wires. The default connection is set to COM3.
I click connect and it says DEVICE NOT FOUND.
I switched to COM2 and got the same thing.
I switched to COM1 and it says CONNECTED, then after a second or two it says NO FIRMWARE READ RESPONSE. and then says Not Connected again.
As soon as its powered on, the blue LED begins blinking rapidly and just keeps doing so sort of like a hard drive light does when its reading.
Before i tried it on windows, i got the same issue on Ubuntu. DEVICE NOT FOUND every time i hit connect no matter what COM i was using.
What am i doing wrong here? I tried both VESCs thinking maybe one was just bad. They both do this.