VESC Tool

Hello

I am desesperatly wondering how to get max torque at start. My motor can get up to 80A and is sensored (5065 270KV). The battery (6S 45C) can deliver them. I don't know why the VESC limits it to 45A after the wizard process and when trying to run it limits to 35A. With another motor it delivers 50A but this motor is twice as heavy as the one I wan't to use and that can deliver the torque. I am using Flipsky VESC4.2 (so 50A max).

I'm trying to control my motor using position PID control but can't figure out how to get it to work. When I set a position in VESC tool the motor spins wildly and stops in a random spot. Only after setting the same position several times does it eventually rest on the correct position (and this seems to be if it just happens to get close by chance). 

Hey, I'm using an arduino connected to my VESC with UART to rev a BLDC motor, and that works fine. But I can't get the motor to accelerate smoothly with my potentiometer on the arduino.

The potentiometer can kind of control the speed of the motor, the first 20% it runs rather slowly, and anything above that is max speed. And if I ONLY connect the vesc to my computer and motor and use the build in rev function. It can only accelerate at max speed.

I use Vesc on many vehicles including bicycles, motorbikes, snowmobiles... the main problem is the display!
Currently the only solutions available are the Davega and the Flipsky but unfortunately not everyone likes them and they are not always compatible with the vehicle and its external circumstances.

I bought this Ottocast Carplay product for motorcycles, really well done:

For a project we have been given a used VESC4.7 and we want to check whether or not the board is still usable. 

Intuitively, we tried to connect the board over USB with the newest version of the VESC-tool, but the software keeps returning the error-message: "Could not autoconnect. Make sure that the USB cable is plugged in and that the VESC is powered." Note that at this stage the board is only connected over USB, so (besides the 5V over USB?), no additional power is being supplied over the battery connection. 

Hello
I have problems with the throttle movement.
If I have no restriction on the rpm (Motor settings/general/Max Erpm) then all my throttle movement works, i.e. if the throttle trigger is not pressed, the engine stands still as it should and if the throttle trigger is fully pressed, the engine revs at full rpm. The full throttle movement is used. 0-100%

Hi all,

I'm wondering if anyone has this issue? I've just downloaded the latest version of VESC tool (6.00), and I'm unable to save or load motor/app configurations. All other functionality seems to be fine. I've also tried to use older versions of VESC tool, but the same thing keeps happening. 

This issue happens regardless of whether I have a VESC connected to the software or not. 

I'm using Windows 10, which I assume is up to date with Windows Updates. The save/load functionality was working a month ago. 

Hoping someone can help. When I try to connect to the VESC Tool app on my Mac (Ventura 13.2.1) via bluetooth, the app crashes. However, my iPhone app connects just fine. Does anyone know how I can get connected to my Mac via bluetooth again or did I lock myself out somehow?

Any help is greatly appreciated. Thank you

Hi all,

I am doing a Capstone Project at school that is building an e-bike conversion kit. I am hoping to use a VESC controller, but I will require documentation for the control theory inside the software. I have looked through the documentation but I have not found anything like that. I was wondering if anyone knew where to look for this sort of thing?

Thanks!

Aeon

Hello !

I've a old VESC 4.12 buyed some years ago in second hand on internet.

The firmware in the VESC is 2.53

When I connect this esc to my PC, Vesc Tool give me a message "the firmware is too hold ..."

When I upload a new version of the firmware, all is good but the firmware version is the same after reboot. I've read a message on the tool about impossible update after upload a bootloader if another bootloader is present. May be this is the update problem.