General discussion

Hi everyone,

one of my Maytech superfoc6.8 VESC just blew up :(

Setup:

First off, I need to mention that I do not have a genuine Axiom HW. Out of pure curiosity, I flashed the FW to a general purpose STM32F405 board which I've made.

I worked my way around the few fault codes that the VESC was spitting out and hooked up the SIN/COS signals from the ME1304. As the encoder of the motor uses a 5V supply, the voltage levels are not compatible and need some level shifting. For this, I used a differential amplifier build around an OPAMP. With the circuit, the SIN and COS signals have a DC offset of 1,65V and an amplitude of about 2Vpp.

Hi guys.

Do you think if the 80100 KV220 (7kWt) generates 31v at 6000 RPM as alternator being directly connected to an ICE, a VESC is still capable of regenerating and charging a 10S (40V) LiPo battery?

In theory, I guess YES. What about practice?

Cheers, Andrew

Hello all members,

I suspect problems on start up on my VTT motorisation with the internal current limitations..Has the VESC 4.20 50A ESC internal current limitations? and can we increase the 50A current if yes?

thanks

I blew up a few VESC 4.12 and finally decided to repair them.  The chip originally is a DRV8301 but there are none in stock anywhere, so I replaced it with DRV8302.

A couple had burnt traces so I only managed to revive 3 of them.  When I run them they all behave similarily throwing a FAULT_CODE_ABS_OVER_CURRENT

I get this issue even if I just turn the motor by hand.  Generic 6374 motors.

Tried reflashing them, several times, but still same issue.

I am using a remote control receiver which is hooked up to the ADC of the VESC MKV6. The remote has a power on/off, up(to increase the speed) and down button (to reduce the speed). Basically I am using the remote to control the speed. I am also using a momentary switch to auto power off and I have set the timer to 1 min. With the power on/off i am able to turn on/off the motor. But when I am using the switch to auto power on the system, the VESC cuts off the speed to the whole system disabling the motor to startup when I press the power button on the remote.

I don't quite understand under what circumstances the PID controller is used (specifically talking about FOC control in my case).

I've got encoder feedback, but thus far I've actually had better results from running Sensorless (by keeping the 'Sensorless ERPM' setting lower than my min ERPM). I guess this means the encoder info is taken into account for start-up only, but then it quickly switches to Sensorless mode?

I'm running a motor that has a Kt value of 105 according to the manufacturer. I've got an input voltage of 49.4V (as read by VESC Tool software). Therefore with no losses and a max duty cycle of of 95%, I'd expect to hit RPM values of around 49.4 x 105 x 0.95 = 4928RPM. (I have the max ERPM software limit set well above the max I should ever see in practice, so that shouldn't be doing any limiting).

Hi

I am wanting to edit and compile the VESC tool but I have no idea how to compile it, and can't seem to find anything out there to help. 

I use a Windows 10 machine.

Any help is much appreciated.

Can i slow down the speed of the motor(gradually decrease the speed) when the battery is about to die rather than an abrupt stop?