VESC Tool

Hey all, 

I have searched for this issue and have not found a solution yet.  I am using the VESC with a throttle in Duty cycle mode ( I know of the differences between current and such, we just need duty). I was wondering if anyone has found a way to limit the current spikes when changing the throttle.  Right now i'm seeing lots of current pushed to the motor when changes in throttle happen.  This is a bit Jarring.  

Electric skateboard was working fine, it was a bit sluggish so I wanted to tweak some settings. I Load up the VescTool Configure my motor, Run the controller set up, the program reads my input from the controller fine. Disconnect the Vesc and my board will no longer read input from my Vanpro Controller. Any way to fix this?

Hi Everyone,

This post is about motor tuning for a drone on VESC tool. The hardware is a VESC 6, and this is related to a post I made more than a year ago about the KDE 2814XF-515. I had trouble tuning that one and still don’t have a firm grasp on these parameters, the tuning process and how to optimize this better. Here is what I’ve been using for the KDE 2814XF-515 for the last year to reasonable effect.

R = 62.0 mOhm (for a quoted 130 mOhm motor this seems about half and correct)

L = 6.41 uH

lambda = 1.459 mWb

Kp = 0.0107

Hey,

Does anyone know that the difference is between "current in" and "current in setup" in the log file?

In the RT data logging help/Info area, there is just limited information.

  Thanks a lot !

Ole 

SOLVED

Hi,

I am trying to compile the vesc tool mobile apk version. I enjoy using the app and it is awesome. But I would like to have the RT data screen as the home window and auto scan/connect.

So far I have compiled an apk but it is the full software version which you would use on a tablet or a computer. I have done this in QT creator in a linux VM on windows 10

So my question is how do I compile the mobile version?

And a tip on if it is possible to open the app layout in qt design and if so how would be nice.

Trying to use VESC to drive the blower motor in a car. Yes I know it's not wise to use hobbyist quality parts for automotive applications... 

The PWM speed signal from the 2009 Camry is open collector, so that means lower duty cycle maps to higher speed.

Is there any way to change the mapping to do this? I was thinking of making the throttle curve have a negative slope, but can't do it. In the PPM app, I also tried changing

"Pulselength start"  = 2 

"Pulselength end" = 0

but that didn't work either.

Hi,

I´ve got a probably easy to solve problem:

I can control the VESC with my remote without problems, but when I try to use the keyboard control from the tool the motor only clicks and rattels briefly.

The same happens when I try to control it from the app or the terminal.

I didn´t find anything on google. Has anyone got an idea what I am doing wrong?

Hello,

I quickly wanted to report a bug I was able to solve. Just incase anyone encounters the same: The input field for "Sensorless ERPM" under FOC=>Hall Sensors will randomly autocorrect and will only allow values below 999 or above 100000. This was caused by having dot ... and comma ,,, swapped in my german Windows PCs system-wide settings. I am sure it will be the same for other input fields as well, but not for all.

I think this is pretty rare, and now here it is. I don't know if this can be fixed, as it's probably related to QT.

Hello,

i have a problem with connecing the flipsky FSESC6.6 to the VESC tool. When I try connecting it, it just says: Invalid serial port: \ \ . \ COM5. Im new to this and would really appreciate it if somebody wold help me.

Thanks :)

Hi there,

I'm a newbie in search of help.

I have just downloaded VESC Tool - Platinum and I am attempting to run it under Windows 7.

It completely fails to load.

Can anyone please point me in the right direction.

I have tried "Compatibility Mode" and "Run as Administrator".

I've also loaded it into a variety of locations (Desktop, C:/, C:/Windows, C:/Windows/Programs etc... No Luck with any of these locations either



Regards,

Martin Moore