Lemonergy · Protocol step
Repeat
Repeat an ordered group of protocol steps.
- Implementation ID
repeat- Reviewed
- 2026-10-27
Behavior
The blocks array must be nonempty. Count is an integer from 1 to 10000. Nesting is limited to two levels and expansion remains within the protocol resource limits.
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 |
|---|---|---|---|
countcount | count | Supplied by the user | Integer repetitions from 1 to 10000. |
blocksblocks | ordered step array | Supplied by the user | Nonempty sequence of protocol steps. |
Equations and rules
This step is defined by its sequence and stopping conditions, described above.
Worked example
Inspect pulse characterization
0.2 V change after a 10 A step gives 20 mΩ by ΔV/ΔI on the same cell/pack basis.
Open Design → Protocol bench →Use in a workflow
Repeat charge/discharge
Cycle aging block repeats charge, discharge and rest.
- Repeat: Repeats blocks
- count
Inspect pulse characterization
HPPC alternates pulses, moves SOC and includes long rests.
- Repeat: Repeats SOC points
- count
Connected concepts
Limits and interpretation
- The estimate depends on timing, temperature and state; this is not AC impedance spectroscopy.
- 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)