VESC Original Hardware

Hi all,

I build my VESC with HW 4.12 about 2 months ago and after some failures, like a burned DRV, I have it running my Turnigy SK3 149kV motor.

The problem: when I connect one 5S battery it works flawlessly, like you'd expect. Yet once I add a second battery in series to a total of 10S I get a DRV8302 error... When I switch back to the 5S config no errors at all.

My voltage limits are set from 8V to 57V and I don't get a overvoltage error but a DRV error.

Why does the VESC not use the current shunt amplifiers built into the DRV chip instead of adding amplifiers to the system? I see that this used to be the way it was done in 4.12hw. Why did it change for vesc6 other than to use a third current shunt? Could DRV8323R be used with the same results in a footprint?

Thanks

Are there any less expensive alternatives to STM32F40X? How about F3 or F2 series? Yes these are not as fast as F4,have less memory, but...they are less expensive.

Any opinions/experience?

Thanks!

Hi Benjamin,

Do you have any idea how much spare current the 5V converter allows to draw for powering Arduino + WS2812 LEDS ?

Power comsuption on bench is not so high but with nRF module and so on, maybe ther's not enough room for this.

Hi

i have the newest vesc from flier a chines factory

how can i find out which hardware they use to make a firmware update.

thanks for help

Where can the schematics and kicad files be found? Are they open source? I mean HW version 6 and above...

Hi,

I've just login to this forum after a quiet long quest of the best solution to my hardware issue (vesc 4.12 from Torqueboards for those who know with firmware/bldc tool 2.18 provided also by this vendor).

I hope my post is in the good discussion folder of this forum and apologize if not (maybe you can suggest the proper site/forum).

 Hi guys, Could you please help?

The board has been working well with dual vesc6 for a few days, I've probably done 20kms using these new vesc6s. (upgraded from Maytech vesc 4s which were useless in FOC.)

When the problem occurred I had only been running for about 30 seconds when I lost connection with my remote, (under very small load and turning fairly sharply). I assumed a flat remote battery initially. 

This is a copy from here (With a few amendments):

http://vedder.se/forums/viewtopic.php?f=7&t=873

I don't seem to get much feedback, so trying it here.

Hey guys,

Hello,

I noticed that the dead-time of the MOSFETs seems to be composed of 3 parts.

1. HW part DRV8302 (or 01), 10K sets 80nS dead-time, 50µS the min possible + 3nS/1K of resistance.
2. In mc_interface.h #define mcpwm_dead_time_cycles 60, but I ignore the lenght of one cycle, help, please
3. In BLDC Tool or VESC Tool, you can find dead-time compensation, preset to 0.08µS.