VESC Firmware

Hi all.

Apologies if this is a known issue or has been talked about before. 

Hi all,

I have two problems with a motor using FOC.

I'm controlling via PPM mapped into duty cycle. It's a small motor (max 300W) with KV=380.

The first problem is that giving 0.050 ms increments in the ppm (in a range 1-2ms ie steps of 5% of the total range) it happens that the motor stops completely as in the following figure.

https://ibb.co/fSY0n9

Hi,

I see the maximum Switching Frequency I can set is 150k, but can it really work at that frequency the driver?

My goal is to run at 68k, can I test it without problem? I'm using a relatively small motor (max 15A @24V) for multicopters.

Hi,

I'm in the process of writing a mode feature and need to hook a button up.

Since I want my firmware to be compatible with all app (PPM, ADC...), mapping change across the mode selected.

I also use ADC3 for external temperature monitoring (and cutoff if too high).

Based on FW3.40, I obtain this mapping table :

Hi All, recently I have replaced the original ESC in my Evolve Gen2 Carbon board with a VESC. The performance increase is enormous, much of which I attribute to a higher motor current setting than perhaps the original controller was using. I also guess that Evolve did not use current-control, but rather some kind of hybrid duty control.

Hi all,

i build a custom VESC Board and stripped down a few functions. Now i want to use the D2 Pin as FAULT Input (PB7 originally)

I found the #define in the hw_xx.h file to define the FAULT pin, but how can i disable the nrf part ? Just comment out the nrf part in the hw_xx.h file ?

Thanks in advance

Georg

Hi first time for me to write a post here. I´m really have to say thank all off you and especially vedder for this great work.
I´m stuck a bit and wonder if the answer to my question is so simple as I think it is and I´m the stupid one... please do not blame me.

Hi,

I've two VESC boards and I'm trying to update the firmware, they both report as running fw3.38 and hw4.10 (though have 4.12 on the board...)  in the VESC tool (0.95). 

I can connect, it says the firmware is too old and to update it.  I go to the firmware page, select VESC_default.bin then click upload, it completes, throws the COM error as expected and after 30 seconds I cycle the power.  It still says it's running 3.38 and can only connect in limited mode.

Has anyone tried such configuration?
Having a Nucleo F302 board to use as controller for prototype, would be nice is there is a F302 version exists somewhere.

Failed to found it here, that's the reason of this topic.

Thanks a lot.

i would like to see a vesc compatible board with a single microcontroller (maybe requiring a faster processor or package with more IO) but able to drive 2,4,6,8 motor drivers for use in multirotor drones etc