VESC Firmware

Hello. I have a strange issue with my VESC 4.12. I have been using this VESC with firmware 3.34 up to 3.38 now and I am noticing something wrong about the phase current limit. 

In my configuration I had set the phase current limit to 100A. After doing a data log with my VESC during a ride, I noticed that the phase current was being limited at ~68A. The battery current limits are working fine, but the phase current limit is off for some reason.

Hi there,

i'm using the awesome VESC in my electric scooter with the following setup:

throttle potentiometer on ADC1

Brake Button between PPM and GND

esp8266 on RX/TX as a wifi bridge to stream data to my smartphone

As App i'm using ADC no reverse brake button in current control mode.

Everything works great, but i also want a Pushbutton for cruise control. Is this already implemented and i do not find the info, or is a cruise control button not provided with the described config?

On the A200S, every time I try to set my motor type to DC it bricks my unit and I have to reflash the firmware. I am using a modified version of the 75_300 configuration. Also how are you supposed to debug the firmware? The guide is very old now.

delete

Hello,
Is 3rd harmonic injection for FOC already implemented in the Firmware?
It allows a 15% higher motor voltage and thus higher speed for a given battery voltage
without the disadvantages of field weakening.
See:
https://tomontheroll.wordpress.com/2014/12/25/a-quick-look-on-three-phase-overmodulation-waveforms/

Furthermore it can help to reduce the speed ripple for quad-copter applications.

Hello,

I have a vesc 6 to use it on an electric bike. I wanted to add an option to configure only the max current and the max ERPM by UART in order to control via a raspberry Pi.

I just started by adding the lines in commands_process_packet function, in command.c :

    // check if the code comes here
    send_buffer[ind++] = packet_id ;
    commands_send_packet(send_buffer, ind);

Hi!

I'm building some vesc:s but having the problem with that the vesc isn´t booting and are not detectable by usb.

Fairly certain that my soldering is correct since I can read the chip and program it with verification.

Programed with 3 different OS and have hade the same result every time. Have even tried the files from this with out results http://fishpepper.de/2017/10/31/tutorial-initial-flashing-a-new-born-vesc/

Any ideas?

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?