I am very new to this exciting field but am being rather frustrated by being unable to connect to the third party VESC (412 firmware according to the markings on the PCB) and my laptop which is running Windows 7.
So far I have tried 3 different USB cables but I always get the same kind of response from the VESC Tool, ie ' No ports found' or, ' Could not auto connect. make sure USB cable plugged in and that the VESC is powered.' The laptop makes an unusual audible note which I guess reinforces the fact that it can't make a connection.
i have briefly scanned Esk8 forums and this appears to be a common situation. Is there a solution to this problem, do you need to download a special USB driver to your computer to support the VESC? I would be very grateful for assistance.
The same situation for me. I buy 2 ESC from diyelectricskateboard.com, and can't connect them to VESC tool. Trying 2 different cables, and nothing happens. Looking for info...
Try to install virtual com port drivers.
https://www.st.com/en/development-tools/stsw-stm32102.html
Thank you very much Frank. I installed the driver from STMicroelectronics and now have limited comms with the VESC on 1 USB port, the other USB port I tried on my laptop indicated that the virtual com port driver was not installed correctly, I don't know how that can happen.
When limited connection was made to the VESC a message appeared on the VESC tool stating that the Firmware was too old and needed to be updated from the Firmware page. I click on the Firmware page which shows 3.62; it is not clear if this is the existing Firmware residing in the VESC or, if this is the version to update to. Also a comment came up that if you update the firmware on the wrong hardware it WILL damage the VESC for sure.
Can someone please advise me if 3.62 Firmware is compatible with 412 hardware, and will that give full Comms and not damage the VESC? Or is there an even later Firmware version available for 412 hardware?
You choose 410, 411, 412 HW.
Upload the 3.62 FW. After Upload wait 10 seconds before doing anything. Then re-connect, job done.
On a side note, I've had plenty of times when I couldn't connect my windows laptop to the attached VESC due to some programs grabing a handle on that new serial port, which causes VESC-Tool to not being able to open the port properly.
The worst culprit in doing that is Cura. Also had troubles with VMWare workstation.
So try to close most other programs that may access a serial port and it'll make a difference!