How the car sets its limits
The battery management system decides how much voltage, current and power the car can take at each moment. How it derates, where its limits appear in each protocol, and why the operating point always settles at the lower of the two sides.
What the BMS knows
The battery management system measures every cell voltage, the pack current and the temperatures, and estimates the state of charge and the state of health. From these it works out, continuously, the current the pack may take now and the highest voltage it may see. Its limit is the most restrictive of several:
- Cell voltage headroom: the highest cell has to stay below the maximum of its chemistry, so the permitted current falls as the cells fill. This is the constant voltage part of the curve.
- Temperature: cold cells risk lithium plating at high current and hot cells age faster, so both reduce the limit.
- State of charge: most packs have a table of current by state of charge and temperature and step down it as the pack fills.
- Balance and ageing: an unbalanced or aged pack reaches its limits earlier, because its weakest cell decides.
- Parts other than cells: the inlet contacts, the cable from the inlet to the pack, the contactors and the fuses have ratings too, and the inlet often has temperature sensors of its own. A warm inlet can derate a session as much as the cells can.
How these combine is the design of the car maker and is not standardised. The protocols carry only the result. Why a charging curve looks the way it does shows what it looks like over a whole session.
Where the limits travel
| Protocol | Declared at the start | Updated during charging |
|---|---|---|
| DIN SPEC 70121, ISO 15118-2 DC | ChargeParameterDiscoveryReq: EVMaximumVoltageLimit, EVMaximumCurrentLimit, optional EVMaximumPowerLimit, EVEnergyCapacity, EVEnergyRequest, FullSOC, BulkSOC | CurrentDemandReq: EVTargetCurrent and EVTargetVoltage in every cycle, optional new maximum limits, ChargingComplete, BulkChargingComplete and the remaining times |
| ISO 15118-2 AC | ChargeParameterDiscoveryReq: EVMaxVoltage, EVMaxCurrent, EVMinCurrent, EAmount, optional DepartureTime | Nothing in the messages: the onboard charger draws what the BMS allows |
| ISO 15118-20 DC | DC_ChargeParameterDiscoveryReq: EVMaximumChargePower, EVMaximumChargeCurrent, EVMaximumVoltage and the minimum values, optional TargetSOC | DC_ChargeLoopReq: EVTargetCurrent and EVTargetVoltage in scheduled mode; maximum and minimum power, current and voltage in dynamic mode |
| CHAdeMO | 0x100: the maximum battery voltage and related limits | 0x102: current request, target voltage, fault and status flags |
| GB/T 27930 | BCP: maximum charging voltage per cell and in total, maximum current, nominal energy | BCL: voltage and current demand and the charging mode; BCS: measured values |
EVMaximumCurrentLimit is a ceiling, not a request. The request is EVTargetCurrent, which on DC moves with every cycle of the loop. On AC with ISO 15118-2 the car sends no request at all: its onboard charger simply draws less when the BMS asks for less, and only a current log shows it.
Meeting at the lower one
Each side states its limits, and energy flows at the lowest one in force. On DC the charger regulates, so it delivers the smallest of the car's target, its own current limit and its own power limit at the present voltage. The flags EVSECurrentLimitAchieved and EVSEPowerLimitAchieved in the response say when the charger, not the car, is the limit.
| Limit (illustrative numbers) | Value | As a current at 380 V |
|---|---|---|
| Car: EVMaximumCurrentLimit | 350 A | 350 A |
| Car: EVMaximumPowerLimit | 150 kW | about 395 A |
| Car: EVTargetCurrent now, cold battery | 180 A | 180 A |
| Charger: EVSEMaximumCurrentLimit | 200 A | 200 A |
| Charger: EVSEMaximumPowerLimit | 100 kW | about 263 A |
| Operating point | 180 A, about 68 kW: the car is the limit |
Once the battery warms and the car asks for 300 A, the operating point moves to 200 A, about 76 kW, with EVSECurrentLimitAchieved set: now the charger is the limit. On a charger good for 400 A and 200 kW the same car would get its own maximum of 350 A, about 133 kW.
- The voltages have to fit as well: the battery voltage must lie within the charger's range (EVSEMinimumVoltageLimit to EVSEMaximumVoltageLimit). Ranges that do not overlap end the session in ChargeParameterDiscovery, often with FAILED_WrongChargeParameter.
- A minimum above the other side's maximum is a conflict too, for example an EVMinCurrent above EVSEMaxCurrent on AC.
- The Negotiation tool puts both sets of limits side by side, shows the value both can live with and marks every pair that cannot hold.
What the checks compare
| Check | Compares | Party when it fails |
|---|---|---|
| IS20-03 | ISO 15118-20: the charge current against the charger maximum, and a discharge against the smaller discharge current and power maxima both sides announced | Charger |
| IS20-04 | ISO 15118-20 scheduled mode: the delivered current against the target the car asked for, with the margin and settling time of the profile | Charger |
| CH-02, CH-03 | CHAdeMO: output current against the request in 0x102, output voltage against the battery maximum in 0x100 | Charger |
| GB-05, GB-06 | GB/T 27930: output current against the BCL demand, measured voltage against the BMS maximum | Charger |
| PW-01 | A measured current against the smallest limit in force, from any source | Car on AC, charger on DC |
None of these checks fails because a car asks for little. A low EVTargetCurrent is the BMS at work: read it together with the state of charge in the same message, and with the temperature where the protocol carries it, before you suspect the charger. See Charging is slower than expected.
The CHAdeMO and GB/T margins (chademo.currentMarginA, chademo.voltageMarginV, gbt.currentMarginA, gbt.voltageMarginV) and the overcurrent margin of the other checks (pw.currentMarginPct, pw.currentMarginA) are flagged for verification in the limit profile.
Sources
- ISO 15118-2:2014, DC_EVChargeParameter, AC_EVChargeParameter, CurrentDemandReq and CurrentDemandRes
- DIN SPEC 70121:2014-12, DC_EVChargeParameter and CurrentDemandReq
- ISO 15118-20:2022, DC_ChargeParameterDiscovery, scheduled and dynamic control modes
- CHAdeMO specification and GB/T 27930-2015, 0x100 and 0x102; BCP, BCL and BCS