I just purchased a VESC6 and downloaded the most recent firmware to it (3.29/HW60). I am running it off of 12S with my voltage max set to 57V. If I mess with it long enough I can eventually get the serial/USB connection established with the computer. I then calibrate the first FOC settings (resistance, et al) and then press the button to calibrate lambda. Nothing happens. The USB/serial connection locks up and the VESC-tool looses all communication with device. Re-establishing comm after that is quite a process. It is a little better when running off of 9S, but not a lot. In short the USB/serial connection is REALLY finicky. Is there something I am doing wrong. Are there some settings that need to change?
Hi protontim, some USB cables are simply crap. They are made for charging a phone, nothing else.
Try a quality cable. If you still struggle, post here.
Frank
Hi Frank, thanks for responding!
Turns out it is not the USB connection, at least not directly. I tried different cables, ferrite beads, notebook computer running on batteries. All to no avail.
I can run the RL calibration multiple times back to back with no USB failure, so the RL calibration is not taking down the USB. However, as soon as I try doing a lambda calibration the communication craps out. It appears the the VESC6 stops responding when I send the lambda command. The motor does not pulse or anything. Communication just jams up when I press the lambda button. It should be noted that when I power up the VESC6 the red LED is blinking in sets of three. When I go to the display real time data the fault simply says DRV. Not sure if this is why the lambda measurement is locking up and not sure what this means in general. I have messed with the voltage level settings trying to clear this but to no avail. In an attempt to change some of the voltage settings the VESC6 locked up again. Very frustrating. Not sure if I got a busted one or not. Any ideas on how to proceed? Thanks!!
I’ve been having the same sort of problems, can’t work out if it’s the vescs, the cable, the computer or the vesc tool. It’s very frustrating, I can’t wait to hear how you sort your problem.
@phill I have tried different cables and different computers, with the same results. So it looks like it is the VESC6 or the VESC - tool. I think if I can get rid of the red flashing lights I stand a chance of the protocol working, but it seems this mystery condition prevents some functions from running and as a result locks up the comm link. Not sure how much more time I can spend on this. Does anyone know how to read the error codes on the VESC6? When I go to real time display it just says fault:DRV. Not real specific.
I have a twin motor vesc set up,lve had one vesc stop connecting then a few sessions later it decides to start connect again motor detection worked once now it won't,it's a pain in the arse
Problem Solved: I flashed the VESC6 using the ST link V2 tool. (BTW I had do connect ALL the SWD connections, including reset and VCC, to get it to work). Once the part was flashed with the boot loader and code, I attached it to VESC tool and loaded the most recent code. All USB problems are now history and, after some twiddling of parameters I was able to get it to do its self discovery and run in FOC mode.