VESC Firmware

I am working on custom board based on VESC6 for 200A+, but it is not managing to track the motor position properly. 

The board has 10k pull down resistors on the mosfet gates which I think are causing a voltage offset on the phases.

This means the absolute voltage on each phase does not go below 0 when the motor is free running. So I tried turning the motor with a drill and the BEMF plot looks nice but the tracking oscillates between 45 and 65 degrees.

Hi!

I'm new to VESC and have some troubles to get the right data when using PYVESC over UART. When I loop thru the GET_VALUE response package I get ok variable names but the data seems wrong. Could some one please make sense out of this?!

Hello everyone,

Connect your VESC (FOC mode & Hall), enable RT and watch the tachometer. It will change of course when the motor is moving, mut its value will also change when you do a Full Brake or Stop and turn the motor by hand.

Except when you turn on handbrake and turn the motor by hand. Now the tachometer does not change. 

Would be good if it does, because then you know that the handbrake level is not high enough.

I tried to locate the bug in the source code but failed to find the appropriate line.

I have two new VESC V6.41 that I am using to replace an older VESC V4.10. The setup includes a 63mm Alien Power Systems Motor connected to the VESC powered by a 6 cell 5000mAh Lipo.

Hello, I'm happy to have found this excellent resource - thanks!

in the FOC code (mcpwm_foc.c), there is a variable called last_inj_adc_isr_duration.

My understanding, looking at the mcpwm_foc_init method is that injected ADC are not used (they are used in BLDC mode). Only regular conversion is used.

Also, that variable is updated in mcpwm_foc_adc_int_handler whereas the corresponding bldc variable is updated in mcpwm_adc_inj_int_handler, so it's all a bit misleading.

To make things more complicated, there is an interface method that blends the two concepts (mc_interface_get_last_inj_adc_isr_duration).

Hi,

I'm new to the VESC and want to make a position control with the vesc via NRF. Now I am facing the problem that my Motorcurrent is measured wrong all the time. So my question so far is,

how is the 4095.0 calculated or where does it come from? All V_REG are divided by this number.

Tanks for your help in advance,

Christian

Hi,

I'm developing a fairly large experimental racing drone and have bought a set of 4 VESC's to use on this monster.

Yes it may seem excessive, however I've come to this after testing quite a few large multirotor ESC's - none up them are up to the toque loads and voltage spikes created by a system of this size. I'm not an electronics or firmware expert, more of a frame designer so not really sure how to get the flight controller to communicate to the VESC.

Hi guys,

I was running my old VESC on 2.18 and I upgraded to 3.33 and now I can't get my telemetry to work again, I was using RollingGecko's VescUartControl library and I suspect the library has not been updated to reflect the latest changes to 3.33...

Any ideas how I can fix this?

Thanks!
Ervine