EV fast charge time with taper

Why DC fast charging tapers and how this model approximates it

Above the taper start, power falls linearly from peak at the taper start to peak times end_power_ratio at one hundred percent. In the taper band the instantaneous power is a linear function of state of charge, so session time is the closed-form integral of dE over P(s), which reduces to a logarithmic expression in the powers at the endpoints. That is enough structure to show why the last twenty percent is expensive in minutes without requiring a manufacturer-specific curve file, temperature, or pre-conditioning state.

Inputs, defaults, outputs, and validation contract

Example: seventy-five kilowatt-hours at one hundred fifty kilowatts from ten to eighty percent stays entirely below the default taper start, so tapered and constant times match. POST a JSON body with two required finite positive numbers: battery_kwh (usable pack capacity) and peak_kw (peak DC charge power the vehicle can accept on this stop). Optional from_pct and to_pct default to ten and eighty, covering the classic highway top-up band; both must lie between zero and one hundred with to_pct strictly greater than from_pct. Optional end_power_ratio defaults to zero point one five, meaning power at full charge is fifteen percent of peak under the linear taper; it must sit in the open-closed interval from just above zero through one. Optional taper_start_pct defaults to eighty and must be between one and ninety-nine. Optional precision is an integer from zero to eight that rounds every numeric field in the success payload. Aliases such as capacity_kwh, charger_kw, from_percent, and taper_ratio are accepted so route-planning clients can reuse familiar keys. On success the body echoes the resolved inputs, energy_kwh added to the pack, hours_below_taper and hours_above_taper, hours_tapered and minutes_tapered for the realistic total, hours_constant and minutes_constant for the naive flat-peak comparison, taper_penalty_minutes as the difference, power_at_to_kw at the target state of charge, method, and a formula string. Missing, non-finite, zero, or inverted ranges fail with invalid_input naming the field; those failures are not billed. Extending the same pack from ten to one hundred percent makes hours_above_taper positive and minutes_tapered larger than the flat-peak baseline by the reported penalty.

Where taper-aware charge times earn their keep

Highway trip planners that only divide remaining energy by station peak power systematically promise drivers shorter stops than the battery will allow once state of charge climbs past eighty percent. Fleet dispatch tools that schedule depot or en-route DC sessions can batch many vehicle packs and peak rates, compare ten-to-eighty versus ten-to-full policies, and quantify how much extra dwell the taper costs at each site. Embedding this EV fast charge time with taper calculator—or calling the same pure module over the API—gives a second number that already includes the slow top-up band so arrival-time estimates and coffee-break scheduling stay honest. Pair the minutes_tapered field with your own map routing, station availability, and cost-per-kWh layers; this endpoint only answers how long the energy transfer is expected to take under the stated linear taper model.