you can get fone apps that will relatively easily measure angles and inclination
1 Like
A too low setting on your Absolute Maximum Current is why you got an ABS_OVERCURRENT fault. Set that way high, and use your Battery Current Max to control the actual power that’s allowed through.
2 Likes
that’s set to 150
is at 80A on 12s
and 70A on 10s
2 Likes
Flash to NOLIMITS FW and set it higher, 200A would probably be sufficient.
1 Like
Even if it never happened before?
I just know that i when i reached the turn i went on the cobble stones, lost traction a bit and slowed down and at the end i accelerated again, then I heard a high pitched sound and it stalled. Shouldn’t the log show if i pulled more that the absolute maximum current? (noob at this)
1 Like
Do you want it to happen again?
Sometimes, but not always. The highest I saw before your ABS_OVERCURRENT fault was 114.4A.
Noob question, How do you flash NOLIMITS Firmware? Same as flashing fw5, and can be found on github?
2 Likes
Following @DEEIF. Interested as well.
Also looking for what you guys consider a “stable” firmware? Is everyone still ruining ack?
2 Likes
When flashing there’s a selection in one of the listboxes. Same FW, but a different BIN.
1 Like
I know I’ve seen it before, but I just flashed FW5.01 yesterday and didn’t see the No Limits bin for HW6
so there is that…
Edit:
I just looked again… nope… not there
1 Like
well I’ll be gawd damned… I just checked my mobile app and it’s there…
just rechecked the desktop and it’s not there…
fukkme
1 Like
No honey I did not!
I so dislike the VESC user interface
4 Likes
If k00k is happy, the day can only be good! 
the mobile version is the worst.
2 Likes
BTW… @xsynatic solved this… I just checked… follow 
his lead the no-hardware limits option is indeed in the non-default firmware tab on the desktop app…
3 Likes
I’ve been battling with ABS overcurrent faults myself. Setting to 160A is too low for me it seems… every time it happens that high pitched WEEEEEEEE sound happens, it’s scary, got thrown out of my bindings after thinking my cap bank might have solved it- it didn’t… and I think it’s the same reason as yours. It’s been happening exclusively on my MTB, the cap bank compensates for the long battery wires so it’s not that… It only happens on jarring terrain so I figured it must be something else and did some digging…
I can’t tell if it’s solved completely but I’ve read elsewhere that the FOC speed tracker PID loop could be causing the current to overshoot. First, I reduced my motor amps from 110 down to 100 which is kind of a bummer but I have a feeling it’s likely that alone has solved it.
next other few things I tried was to loosen my ramp up time from 0.25s to 0.45-0.5s so the controller has more time to compensate and hopefully not overshoot. Black box to me but I checked the high current sensing button, and increased the observer gain at minimum duty from 5% to 25%.
Finally, back to the speed tracker Ki and Kp. Enable realtime data, disable your remote, and test to see using the set RPM buttons watching the graph to see how high your current spikes. I found motor amps and duty cycle overshooting the target by 3-4x every time with the default values. Increasing Ki, doubling it to be specific, seems to have reduced that overshoot in duty cycle to never overshoots and lands right on target, while motor amps overshoot a tad still, but only by maybe 1.5x the target as opposed to 3-4x, and only a third of the time does it overshoot at all… usually the motor amps land exactly where they end up settling at now.
I have a strong feeling the rough terrain is jarring the speed tracker, and the default values for the speed tracker PID could be further tuned so that the vesc doesn’t overshoot the current beyond our set ABS max when we are jostling around under load. I’d love to figure out a test that might work better than setting RPM… it seems good enough though as it seems to set RPM instantly and clearly shows amps and duty cycle way overshooting the target. I plan on messing with these values further in the future as it’s clearly doing something to reduce/eliminate overshoot in current when making immediate changes to RPM similar to when on bounchy terrain.
I’ve also upped my ABS max to 169A.
I’d like to test everything how it was when I got thrown off, and just see if tuning the speed tracker did anything while on the board, but honestly at this point I don’t want to risk it just to be able to run 10 more motor amps per motor. After making all these changes I didn’t get any faults on an 8 mile ride with heavy loads, tons of rough terrain, jumps, etc… whereas without these changes I got tossed at the 1.5 mile mark due to the fault hitting while accelerating in some bumpy grass.
5 Likes
That high pitched noise comes when the DRV8301 Overcurrent protection kicks in. Its not the firmware taking the decision to shut down.
There is a demo from Vedder where he explains this and I have experienced it as well. You could allow higher current by increasing the default value in vesctool from 16 to 17…or disabeling it and only have the firmware to limit the current if needed. Always good with protection though 
From datasheet of DRV8301, 16 would allow for a voltage drop of 0,403V across a FET while conducting. With an RdsOn of 1,5mOhm… (IRF7749) this would allow a current of 268A. I guess your current spikes higher than this.
Anyone feel free to correct any assumptions I have made in the above statement. 
Slower filter for the ABS over current fault is also an option. Default is 0,1… maybe decrease this value?
Also running the FOC detection with a faster time constant would help the current controller in rough terrain where motor goes full current when the wheels are loosing traction.
Parts from above is what I have picked up from the vesc project forum.
2 Likes