VESC Firmware

Dear Benjamin Vedder, dear VESC community

Currently I’m studying at the high school of engineering in Luzern.

Lately we tried to use the VESC to drive some of our homemade motors.

Now I have the problem that I can’t flash some parts of the software, and I was hoping you could help to find out what is going wrong.

I use a virtual machine with Ubuntu 17.10 running on a Windows7 and an ST-Link V2 Programmer.

The VESC’s hardware version is 4.12 and it uses an STM32F405RGT6 processor.

Hello Benjamin, Hello Everybody,

I try to implement an NRF Communication for the VESC just with one Arduino on the one side and an NRF Connection on P3 of VESC HW 4.12 on the other side. I connected all the wires for the SPI communication and set CE to VCC.

I tried with the Default settings of the VESC:

Hi! I want to modify actual firwmare on my vesc in order to implement a particular communication protocol with my pc. So I downloaded default firmware from vedder's site and change some lines.

Now how I can compile it? Once compiled, can I upload it with bldc tool?

Using the VESC tool, I updated my 4.12 Flier VESC from 2.54 Firmware to 3.34 Firmware. The update was successful (according to the VESC tool), but now the VESC will not respond to input from the controller. The VESC was communicating fine with the receiver until after the firmware update.  I have tried a few things to troubleshoot this, but no success.

Transmitter/receiver –

Hi there,

i'm new and i own now two vesc 4.12, soldered by myself and flashed today a bootloader and firmware through the stlink v2. After updating the firmware with vesc tool free it tells me that i got hardware version 410 but on the pcb stands 4.12. So it have to be HW version 412 or not ?  What did i wrong.

have a nice weekend

Hi not sure if I'm posting this in the right topic. My experience with can bus communication is from the automotive industry. While I never had to spend to much time diagnosing can bus issues I remember that the harness was always twisted pair. I never see it mentioned with the Vesc esc though. Is a twisted pair not needed with the short harness length? Is crosstalk not an issue? I'm getting ready to wire up dual Vesc 6s on a longboard and was wondering if I need to twist the wires or not?

I am trying to work out what dumb thing I have done.

I bought an assembled and working VESC. I wanted to create a custom firmware so followed the instructions with the example on vedder.se, and uploaded it with the STlink

I first used the default ubuntu 16.04 toolchain, but have since upgraded using the instructions here

http://vesc-project.com/node/310

I have since gone back to using the vanilla version from the github repository.

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,