Hey everyone,
I have a TB Vesc that is acting up. Currently running FOC and I can run low speed for a little while just fine but then it just drops the power completely…seems to reboot the vesc then start again. Any reason why I would hit an over current? I’m running Bat and Motor max at 70.
Board Specs:
10s3p battery from the last US group buy (with BMS)
Vesc from TB (With Ack’s firmware)
Enertion 6372 motor/mount
Benchwheel Remote
97mm wheels
I can post my vesc settings if that would help. Any advice?
If you´re running a 10s3p with 25r cells you should trim that battery max down! 70A is too much for them.
25r are able to deliver 20A max, so 3x 20A are 60A max. But you should leave room, so get that down to 40A to be safe or 50A if you really need that punch.
Totally makes sense…I don’t know what I was thinking with 70. Dropping that down to 40 for sure…I’ll just create a profile at 50 using the @Ackmaniac App to see the difference.
Set your battery cutoff start to 30V and the cutoff end to 28V for your 10S li-ion Battery.
But it doesn’t make sense that you get a Overcurrent Error with 130 A as absolute max. Because the current when the error happened was below 130. So did you change it in the settings back to 130 A or was it at 130 A when the error happened?
there was a case like this before if i remember correctly that you have errors sometimes if you run high, identical bat/motor settings. So 70A Bat and 70A motor could have caused that problem.
@Emerson try it pls with the new settings and report back here.
ABS Max is key for letting the VESC handle hard brakes of accelerations. It will adjust it’s power and control where the current flows to make sure that the battery nor the motor exceeds set limits, but that doesn’t happen instantly, and current spikes can occur at random- ABS max needs to be high enough so the VESC’s current ramping has a good ceiling to work under.
I already had this error pushing high the current limit too.
It was on bench when I triggered it, so really no load but I hit a peak of 132A.
Since I came back to 50A, I never had this problem again.
Right, it’s just there to protect the VESC from spikes or when something goes wrong. So this definitely should be higher than Motor max.
130 is a good value.
When you enable “Slow absolute max” then it throws a error when Current filtered is above absolut max.
When you disable “Slow absolute max” then it throws a error when Current is above absolut max.
And when the error is logged it detects again the actual current. So it could be a bit off (<1ms) to the moment when the error happened.
Fun fact: When I had most of the settings in BLDC instead of FOC the error required power reset in order to control the board. While in FOC the error will occur but then only drop the receiver for a few seconds.
Just lower the currents that you use and see if it get’s better. And also enable “Define Max Watt” and set max watts to 36V * batter max.
So if battery max is set to 40A then it would be 36V * 40 A = 1440W
But to me it seems that your VESC has issues to detect the actual current correctly. So just by lowering the values it will get better. And i recommend to not use FOC as long as you have these issues.
