Lemonergy · Protocol step

Rest

Program a zero-current interval between active test segments.

Implementation ID
rest
Reviewed
2026-10-27

Behavior

Rest lasts s seconds, a positive exact multiple of protocol dtS. It evolves the selected plant from its preceding state; it does not reset SOC or temperature.

Interface

Rest interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.RestProtocol step
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.

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.

Configuration fields
ParameterUnitDefaultMeaning and limits
s
s
sSupplied by the userPositive rest duration.

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.

  1. Rest: Sets zero current
    • s
Open Design → Protocol bench

Replay a changing load

Replay applies an existing governed profile.

  1. Rest: Observes recovery
    • s
Open Design → Protocol bench

Inspect pulse characterization

HPPC alternates pulses, moves SOC and includes long rests.

  1. Rest: Allows relaxation
    • s
Open Design → Protocol bench

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.
  • The selected profile determines regeneration. This is not an independent road-load or motor-efficiency model.
  • 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)