My app configuration is UART and my motor configuration is BLDC with HAL sensor. When I use arrow keys to change duty cycle, after a while (usually less than 10 seconds) of moving back between left and right arrow key (-10% and 18% respectively), the vesc motor control will suddenly become unresponsive, causing the motor to not move but the current draw to stay around whatever value it stuck on (the value still fluctuates +- 0.1 A ). There is no fault code shown and the only way I can seem to fix it without having to reboot the vesc is by reloading the motor config to the vesc.
Any ideas as to what is causing the unresponsiveness to occur?
I also experience the same sort of issue with my own custom software application's programmatic commands. set_rpm and set_duty_cycle both occasionally cause the vesc control to lock up indefinitely.
Thanks.
Hi nolander
I'm not the real tech. person for that, but in my trials I had a few funny experiences with the VESC Comport emulation under Win10 with different USB3 chips.
My onboard (intel) with native Win10 drivers did block mouse movements (no mouse was usable since the RT tool was active) when the Vesctool was active and connected. With another Laptop and Intel original drivers the same tool worked flawlessly; with an noname USB3 chipset and native Win10 drivers the tool did not detect the VESC at all even when I'd talk to the VESC via hyperterminal.
Cause in my case is the limited USB3 compatibility to USB1/2 devices like the ST VCM. ST advised to use USB2 ports where possible... With modern devices that's mostly impossible.
Cheers and good luck
Sam
Pedelec usage in combination with a GoldenMotor MagicPie3 BLDC
When it stops responding does it disconnect from VESC Tool? Normally that happens if the VESC browned out and rebooted. Quite common on low inductance motors.
Had the same problem. Inductance of the motor is around 1,2uH.
In my case drilling the +5 Volt pin away (at the USB-Type A Plug that goes into the USB-Port of your Computer) fixed the problem.
Just put the drill through the corresponding hole on the metal shielding, drill at the foot of the pin and then remove it. The Pin is not connected on the VESC side and is therefore only a long antenna.
It stays connected. VESC tool is still displaying real time data, but I have to reload the motor configuration in order to get the motor control "unstuck".
I am experiencing a similar problem. Using VESC Tool, VESC 4.12(flipsky) loses UART connection after several seconds when motor is running. Using sensorless mode increases the time. Tested on 3 different computers and Windows and Linux. On linux it always shows that the firmware is too old and I can't update it. Even though firmware was uploaded by STLink. Any clue why it is like that and what could I do?
Increasing baud rate on VESC tool seem to solve the problem.