VESC Firmware

Hi all,

I have a different kind of motor that I would like to drive with this controller. The current firmware is not suitable for this.

Is anyone interested in customizing the firmware according to my specifications? I guess it is not a too big deal - so you don't need to start from scratch. THe Windows/Linux software is not interesting for me; so there need to be modifications on the whole software.

Is there anyone here that can change the code and compile a new firmware file for me that uses ADC2 for the throttle instead of ADC1?

For some reason ADC1 has stopped working.  I read 2.8V on that pin and my hall effect throttle will no longer change it.  This happened after hitting a hard bump a few times.  I tested the throttle on ADC2 and it seems to work just fine there, the same way ADC1 worked before I hit those bumps.  

Looking for some thoughts on this data. On my dual vesc based dyno, i'm getting this data when changing switching frequency. Anything other than 20khz is distinctly and repeatably lower efficiency than 20khz. Why would this be? Is there something in hardware or firmware that's preset for that switching rate? Anyone have any ideas?

Interestingly, the test motor seems to be more stable and consistent above 20khz, but less efficient.

Could get more data easily with community setting recommendations in VESC-TOOL. 

Hi all,

Couple of questions on dealing with AS5047 encoder :

1. Why the SPI protocol is implemented in software ? It seems that this MCU has hardware SPI module, what am I missing ?

2. When encoding reading fails (I simulate it by disconnecting P1), the motor current shoots al the way to maximum and stays there until motor overheats. It would probably be safer to brake the motor in this condition. Did anyone tried making this change already ?

Thanks in advance,

Hi,

I bought my VESC over a year ago for a diy skateboard project I have not completed and put aside. Recently I have given it another attempt. However when trying to configure the VESC and motor, my firmware is outdated so upon attempting to download and update to a newer version it aborts and fails. The vesc is fully powered and there seems to be no problems as the motor spins and works so far with the use of the controller. So it is extremely frustrating because I dont know what is wrong and it wont let me update newer compatible firmware to the vesc.

Hi,

I am wondering why the CAN message IDs are defined as they are in https://github.com/vedderb/bldc/blob/master/datatypes.h :

Hi,

I wonder if I´m the only one how would like to let the motor "speak" in some situations. 
I thought there might be already some code written, but as I´m not that good with software it´s not that easy to find out.

Hello all

Not sure if this is the right place but here goes.

I have recently purchased a vesc from ebay in the uk. I have just tried to connect it and instantly got a message saying firmware is too old, please update with a programmer.

I thought this was the latest model. I am confused and dont know how to resolve this. I am using the new vesc tool and https://www.ebay.co.uk/itm/183433522210  link to vesc ive purchased. 

hi

i have some test mini vescs based on 4.12 hardware but they are with 2 and 3 miliohm shunts

can someone compile latest vesc 4.12 firmware for 2 and 3 miliohm shunts?

thanks

Hi guys,