VESC Firmware

Hey guys,

I have some problems with connecting my Vesc to a ST Link v2.
I tried to upgrade my Vesc (hw 4.12) from fw 2.18 to the newest version with the Vesc-tool. Unfortunately, i did not take a look at the forum and misunderstood the warnings so i overwrote my bootloader.
Because of this (as i read afterwards at the forum) i destroyed my bootloader and can't upgrade my vesc. Bought an ST Link v2 clone on amazon and got it yesterday.

Hi.

I am working on a high voltage HW using IGBTs and I have issues measuring the resistance of the motor. My guess is that the forward voltage of the IGBTs causes problems during the measurement and that one should compensate for the forward voltage drop during the measurement. I tried to just subtract a fixed voltage in mcpwm_foc_measure_resistance. It helps to improve the measurement a bit, but I suspect it is the wrong approach.

Does somebody have an idea how I should compensate for the IGBT forward voltage drop during the measurement?

Hi, 

I'm trying to communicate my MCU with VESC4 via SPI (VESC is the master). The communication should be triggered by an external signal. Therefore I think the best way to achieve this is to connect the trigger signal to a VESC interrput pin. But I'm not sure which pins could be used as interrupt pins because I need SCK_ADC_EXT and MISO_ADC_EXT2 (PA5 and PA6) pins for communication.

Right now my code does not use the SERVO and TEMP_MOTOR pins. Can they be configured as the interrupt pins? 

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.