VESC Firmware

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,

I downgraded using vesc tool 0.91 and bam it all works again. I repeated and switched between the two to verify. Happens on both my vescs, both my bluetooth adapters and both phones. For whatever reason data isnt being sent on the latest firmware. Im using HK vesc 4.10 and genuine keyes hm-10s. Anyone any ideas why?

I edited the FW and compiled a 100% throttle limit VESC6. Then I ran a motor at 100% throttle and it seems to run fine. However, the current measurements in VESC-Tool are all wrong. The average current at 100% throttle is very different from the average current at 99% throttle. And the sampled data makes no sense at all. Here on the left is the sampled data. On the right is oscilloscope traces of the phases showing the vesc is indeed running at 100%.

Since the generator usecase seems pretty common I wrote a custom app for that:

generator_app.zip

Uzip it to get generator_app.patch (unfortunately ordinary text files are not allowed here, so I had to zip it) and apply to a current firmware (current = 3.40, but older should work too) with