VESC FAQ | Windows Version of BLDC tool

Yes, Vedder is working on some updates tho, if you do to the firmware tab it will tell what version firmware it uses

well i asked because i wasnt able to locate the files necessary to update my vesc to 2.13

OK. Really frustrated here. I have looked, but can’t find ANY info anywhere regarding the proper connection settings when using USB. I would think there would be some easily available information on how to get started (i.e. connected to your VESC), but it is eluding me. :frowning:

I have downloaded & installed the Widows version of the BLDC tool, connected the right-side VESC in my Raptor board (the that looks to be the “master” based on the remote receiver board being connected to it) using a min-USB cable, turned on the battery (I also tried it without the battery turned on), and ran the BLDC tool.

I get 2 pre-set connection options in the upper right (COM3 and 192.168.1.118) corner of the BLDC tool software, both which do not work. The VESC does not seem to be recognized as a USB device at all.

If someone could provide me with some help, I’d appreciate it.

make sure you have the stm32 drivers installed. http://www.st.com/web/en/catalog/tools/PF257938 or https://www.pjrc.com/teensy/td_download.html it’s the same driver as the teensy uses

It should appear in your device manager as a serial com port, enter the correct com port in the bldc tool.

(for the device manager, in the search file and program type devmgmt.msc)

1 Like

Thanks Blasto. It doesn’t appear to be working. I installed the STM32 driver, but nothing new shows up in Device Manager, and BLDC still does not work. One thing I noticed is that the STM32 drivers seem to be built for Windows 7 or 8, and I am running Windows 10. Do you know if that’s an issue? Most Windows 8 drivers work fine on Windows 10…

never used windows 10, but i don’t see any reason why the driver shouldn’t work. if you do not see another COM port, the driver is definitely your problem.

oh and you need to power up the vesc.

A post was merged into an existing topic: Enertion Raptor | First Batch Problems & Solutions

Thank you for your assistance on this. Unfortunately, I have not had any luck getting the COM port to show up in Device Manager. Given what you’ve told me, I assume this is the issue.

I don’t know if it’s Windows 10 or not. I don’t get any error messages at any point. I downloaded the installer in the link above, and the installation completed without error. I followed the instructions in the readme, navigated to the C:\Program Files (x86)\STMicroelectronics\Software\Virtual comport driver folder and double clicked dpinst_amd64.exe. That installation also completed without error. Then I powered on my battery (I see blue lights on both VESCs), plugged in my USB cable to the master VESC (or the one I assume is the master), and tried multiple USB ports on my computer. I got nothing. Not even the sound normally heard when a USB device is connected.

Since I’m not getting any errors, I’m really not sure where to go. I’m not a computer noob, but I haven’t had to deal with something so seemingly archaic since the early days of Android rooting. It’s probably my lack of knowledge about the VESC and it’s communication protocols. Any help would be appreciated.

Different computer maybe?

Already tried. Unfortunately, all my computers are Windows 10.

oh so i guess one with 7 or 8

Also, just FYI, sometimes Windows will try to install a newer driver for the OS than will work with specific hardware.

If your board is running, as on and working and your plugged into the VESC via USB I’d think it should show up in device manager somewhere. It may not be under com ports, could be unkown or something. If it doesn’t show at all, even without any driver installed, there may be another issue.

You have a dual right? I had to order an adapter to fit in the tight space between the glued in VESC and the side of the electronics compartment on my dual Raptor. None of my exsisting connections would work. Did you have an adapter or cable that worked without issue? Are you 100%sure that the cable and/or adapter your using supports data, and not just charging? There are plenty of Mini USB cables and adaptors that aren’t made for data transfer, at all. Is there any chance you’ve damaged the USB port connection on the VESC, or that it wasn’t intacted when you received it? Does a visual inspection of the USB port on the VESC seem OK, no bad solder joints etc?

You probably thought of all this yourself, but I thought I’d ask just in case something basic slipped your mind. Sometimes we can’t help thinking zebras …

OK. Got connected. Turned out to be a bad USB cable (or perhaps one that is only for charging). NOW I have a new problem: Firmware incompatibility. Anyone know where I can get the Proper version of the BLDC tool for VESC firmware 1.14?

http://vesc.net.au/BLDC-TOOL/Windows/OLD%20Versions/

Awesome! Thank you sir! :smile:

I was able to get it all connected and make the necessary changes. THANK you again!! :smile:

1 Like

i just got the VESC controller Ver 412 with f ctingirmware v2.18. my problem is its not connecting. error message “no firmware read response” Please help. thanks

Firm ware v2.18

Were you able to connect? I’m getting the same error

There is a copy of the tool linked in https://www.electric-skateboard.builders/t/bldc-tool-for-windows/42335