Third Party Hardware

Hey guys  I changed the drv on 4.12 hw. I get every data in vesc tool. Even when I spin the motor by hand I can see it in rt data exactly. But motor detection ends in bad result and no spin at all. Cant also spin the motor with arrow keys. I get no faults also. Mosfets and gate resistors seem fine. I was thinking about the gnd pad of the drv got not reflown correct but would the vesc even turn on if thats true? I dont want to take it off and on again and check for other issues before. Also updated fw. I really cant find out where the issue is.  Any suggestions?

Hi,

I have problem with my custom board,inductance measurement are 2x times higher than official board vesc 4.12.

and inductance detection is lot noisier.

My board uses 3 low side current amplifiers AD8418.

Everything works fine except sometimes i got ABS_overcurrent.

When i adjust inductance manually , error is gone.

What can be cause wrong measurement ?

Thanks

Hey all. Thanks for reading!

I have a Flipsky dual FSESC6.6 to which I'm connecting an Alien Power Systems APS8072 sensored BLDC.

I'm powering this with an Echo 58v battery that is intended for electric mowers, weed eaters, blowers, etc.

Hey,

I have a problem with my Flipsky Dual FSESC4.20 100A VESC, when I open vesc tool 1.09 and connect my VESC, it says that my vesc firmware is too old and that I need to udapte it, vesc tool 1.09 only support 3.55 firmwares, my vesc is 3.4, so I udapte the firmware in the software, everything seems to work, but after I reboot the VESC it still says 4.3 version and please udapte the firmware, over and over again.

Also I tried to udapte the bootloader, it doesn't fix my problem.

Hello
Actually, everything worked very well and without problems.
but suddenly I could not gas.
The ADC input remains HIGH (3 volts).
The ADC 2 input is working properly.
ADC1 Throttle
ADC2 brake
I use "Current no reverse brake ADC2"
The throttle levers both work on the ADC2.

I need your help?

Lukas

We have a Flipsky Dual FSESC6.6 Plus which we have configured to run in FOC mode and controlling over CANBUS. The configuration is successful and we can drive the two motors. After some period of time one of the channels becomes unresponsive and upon connecting to it via the VESC APP/USB we find that some of the settings have reverted back, in this particular case the CAN ID has changed. We have previously had a similar occurrence but the CAN baud rate changed from 250k to 500k. Has anyone ever experienced behavior like this?

We are releasing some neat piece of hardware, if you like it please leave a like and follow the project!

https://hackaday.io/project/164932-axiom-100kw-motor-controller

We are going to compete hard to win this year hackaday prize.

Hi,

I am using BLDC sensored mode with my hoverboard motor. I am using the stock defaults, because I have not been able to get BLDC detect to work at all. no matter what I set, the motor just cogs, or spins up for a fraction of a second then cogs.

Using the stock settings and current control mode, the motor does spin smoothly. The problem is that I am seeing a massive overshoot in current starting the motor only sometimes. I attached a graph.

Got my newborn VESC running. Everything seems to be working. The only thing is a bit scratchy noise when I slowly open the throttle at about 2-4% and leave it there.

It sounds almost like an engine misfiring on a car. If I twist it quickly, the motor bypasses that region and works normally.  Below is the video showing what's happening.

Has anyone dealt with this issue before? 

Hello, i bought the maytech vesc, and after configuring everything, i tried to operate it, but it only makes sounds and not spinning, but if i help it just a little bit with my hand (spinning forst and then using the controller), it works, does anyone know why its happening?

Thanks!!