That’s the draw per motor from the battery. Total of thirty amps. 80 motor amps, fifteen battery amps.
Battery amps =/= motor amps.
1 Like
Your pack min voltage is 30v…you are going to low…the chart will help you to translate that to your reading…if you battery push 60amp max thats equals to 30A to each motor…It does not matter ir you motors are rated at 80A (also do not trust the vendor on that info)…Best is to run the latest VescTool firmware…it is a great help when it comes to setting and true values…
@MysticalDork is correct, my motor curr limit can be anything, but vesc won’t accept more than 15A from vattery
Yes thats right, sorry for that mystique…
I don’t understand what this calculator is for? My question is how do I know what values to put on the VESC Tool? I have a Samsung 25r 10s4p battery with constant BMS 100A for charging and discharging.
Your motor kv seems to be quite high, with possibility that the motor its self doesnt sustain high amp output. I had this type of motor that constantly cutting out due to over current. If you plug the vesc and do real time data and logging, youll see vesc continuously report over current. One way to go around this is to throttle gently and not punching it from 0 to 100 in a blip.
1 Like
If you experience cut off maybe it is created by the BMS, when you are low it start the balancing creating and emergency cut of…Many of us bypass the discharge… To add the values at the vesc tool just check the vesc-tool project web page and go to documents…Also everything it is on the forum…
Nope, you’re doing it again. His battery max will be 80A/2=40A. The motor max can be higher, up to the rating of the motors themselves. Usually I set mine to 60 or 80 each.
2 Likes
I am out…too late and tired…sorry if I confuse any of you guys…Thank you MysticalDork…sorry again…
No worries, it’s easy to get twisted around with all the different numbers flying around.
1 Like
Can you show us a picture of how your bms is bypassed?
I made a foolish mistake once and thought I had bypassed it but it wasn’t really. This made my bms cut off power when hitting upper and lower limits of the bms cut offs.
It doesn’t seem to be the case for you though since you mention it only happens to one side.
Perhaps check the cut off values in the VESC tool to see if they have the same cut off values.
I second this: Weird things can happen when setting up two vescs and you can end up with funny settings.
I’d also suggest plugging in the offending vesc and checking for any fault or error codes. Don’t power off the vesc between when the cutout happens and when you plug into the computer - the error codes are in volatile memory and will disappear if power is lost even for a second.
I would
It looks like a min voltage cut off or overloaded over temp
Check battery cut off on both vesc Check each each p group voltage and pack voltage Check vesc temp Check nothing could be shorting eg phase wires Plug vesc in to pc befor turning off and look at the fault code
1 Like
The following faults were registered since start:
Fault : FAULT_CODE_DRV Current : 20.5 Current filtered : -3.7 Voltage : 16.96 Duty : 0.688 RPM : 18496.2 Tacho : 17940 Cycles running : 73186 TIM duty : 4061 TIM val samp : 2030 TIM current samp : 4983 TIM top : 5905 Comm step : 4 Temperature : 32.77
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -71.2 Current filtered : -130.4 Voltage : 29.19 Duty : 0.862 RPM : 224.6 Tacho : 192620 Cycles running : 154478 TIM duty : 4189 TIM val samp : 2072 TIM current samp : 4502 TIM top : 4859 Comm step : 6 Temperature : 44.06
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -70.5 Current filtered : -144.9 Voltage : 23.17 Duty : 0.671 RPM : 11402.5 Tacho : 240644 Cycles running : 79167 TIM duty : 4050 TIM val samp : 2025 TIM current samp : 5043 TIM top : 6037 Comm step : 4 Temperature : 40.23
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -75.0 Current filtered : -146.0 Voltage : 23.32 Duty : 0.681 RPM : 11655.3 Tacho : 245804 Cycles running : 5949 TIM duty : 4057 TIM val samp : 2028 TIM current samp : 5008 TIM top : 5960 Comm step : 4 Temperature : 40.38
Fault : FAULT_CODE_DRV Current : -4.3 Current filtered : -54.3 Voltage : 17.96 Duty : 0.612 RPM : 12791.5 Tacho : 265455 Cycles running : 70762 TIM duty : 4009 TIM val samp : 2004 TIM current samp : 5282 TIM top : 6556 Comm step : 5 Temperature : 40.90
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -80.7 Current filtered : -146.8 Voltage : 23.15 Duty : 0.690 RPM : 11602.1 Tacho : 269852 Cycles running : 115 TIM duty : 4062 TIM val samp : 2031 TIM current samp : 4973 TIM top : 5884 Comm step : 4 Temperature : 40.77
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -74.1 Current filtered : -143.0 Voltage : 23.77 Duty : 0.684 RPM : 10370.9 Tacho : 273392 Cycles running : 6000 TIM duty : 4058 TIM val samp : 2029 TIM current samp : 4995 TIM top : 5933 Comm step : 4 Temperature : 40.56
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -75.8 Current filtered : -145.3 Voltage : 21.82 Duty : 0.666 RPM : 9176.8 Tacho : 276446 Cycles running : 1480 TIM duty : 4047 TIM val samp : 2023 TIM current samp : 5063 TIM top : 6079 Comm step : 4 Temperature : 40.56
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -73.4 Current filtered : -145.6 Voltage : 23.06 Duty : 0.677 RPM : 9692.7 Tacho : 279752 Cycles running : 20406 TIM duty : 4054 TIM val samp : 2027 TIM current samp : 5020 TIM top : 5986 Comm step : 4 Temperature : 40.44
Fault : FAULT_CODE_ABS_OVER_CURRENT Current : -89.9 Current filtered : -138.5 Voltage : 18.97 Duty : 0.656 RPM : 4502.8 Tacho : 287990 Cycles running : 63064 TIM duty : 4041 TIM val samp : 2020 TIM current samp : 5099 TIM top : 6157 Comm step : 4 Temperature : 40.80
Just had a NASTY fall bit a rough patch of road and I’m almost sure that one of the motors completely locked up, throwing me off the board at around 15 mph. I came home, cleaned up my wounds and plugged in my VESC to my computer to find the faults above.
This time, I was running CANBUS, Arkmaniac firmware, Motor 50,-40 and Batt 12,-6 (just to make sure it wasn’t cutting out)
You’ve got DRV errors, which means you’ve blown your DRV chip, which means it’s time to either replace/have someone else replace the DRV chip, or get a new vesc.
Most likely the fried DRV is the cause of the overcurrent faults and the lockups. The next question is, what’s the cause of the fried DRV? The most common causes are disconnected or shorting phase wires while riding. Just once is enough to fry the chip. @esk8snith