Lemonergy · Protocol step
Charge
Apply a charge segment in a Battery Test Protocol.
- Implementation ID
charge- Reviewed
- 2026-10-27
Behavior
CC mode commands positive a amperes; CP mode commands positive w watts. Duration s is positive and an exact multiple of dtS. Charge-only CCCV mode targets targetSoC and runs as the sole block in its protocol. Adaptive until conditions may stop CC or CP at a sampled boundary.
Interface
This reference describes a protocol step; its configuration fields are listed below. It has no connected Studio ports.
Parameters
Defaults are initial model values. Select values for your own model and operating conditions.
| Parameter | Unit | Default | Meaning and limits |
|---|---|---|---|
modemode | cc, cp or cccv | Supplied by the user | Choose the supported charge mode. |
aa | A | Supplied by the user | Positive CC magnitude; CC only. |
ww | W | Supplied by the user | Positive power magnitude; CP only. |
ss | s | Supplied by the user | Positive segment duration for CC/CP. |
targetSoCtargetSoC | fraction | Supplied by the user | CCCV target in (0,1]. |
sourceKWsourceKW | kW | Supplied by the user | Optional positive CCCV charger power. |
endCRateendCRate | 1/h | Supplied by the user | Optional positive CCCV current cutoff. |
Equations and rules
This step is defined by its sequence and stopping conditions, described above.
Worked example
Program current stages
10 A for 300 s then 5 A for 600 s supplies 1.67 Ah before efficiency adjustment.
Open Design → Protocol bench →Use in a workflow
Program constant power
Positive power magnitude and explicit direction define CP.
- Charge at constant power: Programs power
- mode: cp
- w / s
Repeat charge/discharge
Cycle aging block repeats charge, discharge and rest.
- Charge: Adds charge
- mode: cc
- a / s
Program current stages
Successive charge blocks produce stepped CC.
- Charge at constant current: First stage
- mode: cc
- a / s
- Charge at constant current: Next stage
- mode: cc
- a / s
Connected concepts
Limits and interpretation
- The bench refuses chaining plant blocks with standalone CC–CV; stepped CC is not multistage CC followed by final CV.
- This is CP only, not a combined CP–CV controller. CC and CP cannot share a protocol.
- Scheduling cycles does not supply calibrated degradation or physical lifetime evidence.
- Protocol dtS is 1e-6 to 60 s. CC and CP segments cannot share one protocol; CCCV charge must stand alone. Protocol samples use discharge-positive iPack.
Implementation sources
This reference follows Lemonergy implementation sources. Scientific articles support the linked concepts separately.
Repository: battery-design · Revision: ef9802329b75bc15bb96885f8ed5d49425106696
js/test-protocol.js
This implementation and its workflow uses (JSON) · Knowledge graph (JSON-LD)