Reecew89 said:
I assumed that a controller that could demand say 250Amps would need a bms that was 300amps
Yes if you wanted to use a BMS as usually implemented, that is the way to go.
> a BMS would not be required as the battery pack would only send the current the controller asked for (so to speak)
Whether you want a BMS at all is a personal judgment call, but that issue about current has nothing to do with that question.
If you know when to stop using the motor as voltage goes down, then the LVC function of the BMS - the only one used while riding - is not required.
If you trust your charger not to overcharge, then the BMS' HVC function becomes redundant.
If you know your balancing routines are sufficient, then that function is not required from the BMS.
And thus in that case a BMS may not be desired at all.
> So this had me thinking of a project i am underway with, 20s12p Molicell p42a Max current 540amps controller can handle 460, Now i thought if i commected battery to controller it would potentially brick the controller as there is not control over the current being fed from the battery.
It is not the job of a BMS to protect the controller.
Nothing "pushes" current, it is the load that **pulls** the amps it requires.
Therefore it is the battery that needs protection from the motor, and that is exactly the controller's job. The controller determines what current level it will **make available** (not push) to the motor, within its limitations.
And of course within the battery's limits.
The user can program a good controller so it does not draw more than X battery amps, or ramps the power level down when the motor starts to overheat, etc. That is where the intelligence of the system resides, other than the rider's brain watching the readouts.
>> The whole point of a BMS is last-ditch protection **of the battery pack** from failures in the other devices