VESC Firmware

Hello everyone, I've been working off a fairly recent branch (b3ad0bc, which is Benjamin's checkin on Jan 12, 2020), and cannot seem to get the RPM PID control to work.  Using the default PID gains and the discovered FOC parameters, the motor does not turn at all--it tries to apply a small current, and gives up very quickly.  In vesc_tool "faults" terminal command, the FAULT_CODE_UNDER_VOLTAGE is displayed consistently, with the voltage value far lower than my input voltage (9.3 V) of my power supply--which can supply up to 5 A.

Hello,

I am having trouble with the VESC firmware in BLDC mode. When I change the input duty cycle from 0 to let's say 50 instantaneously the ESC is failing to commutate. The VESC firmware should have a ramping function that ramps up the motor in steps. I tried decreasing the duty cycle used for ramping step from default 0.02 to 0.001. But it seems that the ramping is too slow now. Has anyone experianced a similar problem?

Thanks.

Hi, 

we are developing our own hardware and we are going to add ethernet for high speed logging purposes.

Our PHY is not supported in current ChibiOS version (3.0.2). I was wondering if there is a reson why didn't switched already to a newer version. There is any downside to do so?

Cheers

Stefano

Hi everyone

I am quite new in all this field, I have some general questions, hope you guys can help me

1. When I enter the "Firmware Changelog" tab in the software I can see that the latest updated​ firmware is 4.02, right?

Is it work with any version of hardware?, in my case my hardware version is 4.12

Hi everyone

for a personal project I need more features via UAVCAN protocol:

Hi all,

I am currently developing my own hardware based on the VESC 6.

The device will be rather small and so the physical size of the LQFP-64 Package is a problem. There are STM32F4s in a QFP48 Package, which would be a good fit and is still hand-solderable with hot air.

Can you "port" the VESC Firmware to the other package? Will there be enough pins with the necessary functionalities (timers, etc.)?

Memory and other hardware features should be the same, so not a problem?

Bests and thanks,

Jakob

Hallo, ich habe zwei Teile, vesc hw6.41, in meinem Trampa-Board installiert, die über einen Dosenbus miteinander verbunden sind. Leider hat einer der beiden einen defekten Micro-USB-Anschluss. Jetzt sagt das vesc-Tool, dass ich ein Update machen soll.

Hello,

I have the Flipsky High Current FSESC 200A and a Flying Rodeo motor along with the Maytech waterproof remote control. I am having trouble programming the VESC. First off, I've been using the VESC tool for Mac v2.03 available from here.

Says the fireware is 4.2, Hw: 60

Hi everyone,

I just started using Vesc tool few days ago, and I would like to drive the motor in both senses with same duty cycle CAN frame, so for a 0 payload frame I would like a "-1" duty cycle.

I tried to re-load a custom firmware after modifing the code line in "comm_can":

buffer_append_int32(buffer, (int32_t)(duty * 100000.0), &send_index);

by:   buffer_append_int32(buffer, (int32_t)((duty+1) * 50000.0), &send_index); 

Hello everyone,

I'm enabling the ws2811 inside the firmware, I'm able to compile and upload to my vesc, 

Added some print statements just to make sure that the code was executing and I see my print statements on vesc terinal.

But I don't see anything on GPIOB 6, or 7. I tried using channel 1 and channel 2, no luck, they keep stuck around 2.7V. 

Im checking the output with mu osciloscope, nothing...

Any ideas?