lemonergy· battery engineering courses

Lemonergy · Studio block

Enabled and triggered kernel

Tracks every trigger edge, including while disabled, and executes only enabled edges; disabled edges are never replayed.

Implementation ID
native-enabled-triggered-submodel
Reviewed
2026-10-27

Behavior

Tracks every trigger edge, including while disabled, and executes only enabled edges; disabled edges are never replayed. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.

Interface

Enabled and triggered kernel interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Enabled and triggered kernelStudio blockin0in1in2out0out1
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input—Value; real scalar.
in1input—Enabled; bool scalar.
in2input—Trigger; bool scalar.
out0output—Integral; real scalar.
out1output—Invocations this sample; u32 scalar.

Parameters

Defaults are initial model values. Select values for your own model and operating conditions.

Configuration fields
ParameterUnitDefaultMeaning and limits
Sample period
sampleTimeS		s1Positive interval between accepted control samples. Outputs hold between these instants.
Minimum 0
Trigger edge
params[0]		—00 rising; 1 falling; 2 either edge.
Reset on enable
params[1]		—00 retain child memory; 1 reset on enable transition.
Child operation
nested		—Discrete integratorOne configurable native computation operation. Its declared input/output types must match the wrapper.
Initial held outputs
tables[0]		—[0]Initial values for all child output lanes, in output order. For independent elements, supply one value per element.

Equations and rules

  • fire = enabled && selectedTriggerEdge
  • Track previousTrigger on every sample, including disabled samples

Worked example

Enabled and triggered kernel worked example

Default editable example at the first accepted sample (t = 0 s). Child operation: discrete integrator. The output checks below are execution oracles for this example.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Integral
out0		02—1e-08
Invocations this sample
out1		01—1e-08

Explore the recorded outputs

Enabled and triggered kernel recorded example

Enabled and triggered kernel / Integral
Enabled and triggered kernel / Integral against timeRecorded synthetic simulation values. Time in seconds; output in —.1.501.750.5212.251.52.52—Time (s)
Enabled and triggered kernel / Integral: 2 — at 0 s

3 actual recorded samples. Lines are visual guides between samples. Synthetic example, not measured cell data.

Download the recorded samples (JSON) · Open this Studio example after release

Use in a workflow

Enabled and triggered kernel worked example

Tracks every trigger edge, including while disabled, and executes only enabled edges; disabled edges are never replayed.

  1. Enabled and triggered kernel: Tracks every trigger edge, including while disabled, and executes only enabled edges; disabled edges are never replayed. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Control executes on an explicit sampled clock. Continuous states, history/delay kernels, residual equations, and event-source children are not supported.
  • The wrapper contains one original computation operation; arbitrary multi-block submodels are not supported.
  • A sampled child advances once per invocation using its own declared period. Repeated calls share the same outer timestamp and do not advance physical time.
  • A trigger edge seen while disabled is consumed and is not replayed when enable becomes true.

Scientific and mathematical references

These sources explain the scientific and mathematical background. The behavior, interface and limits above define the Lemonergy implementation; a citation does not imply every model option in the source is implemented.

  1. Statecharts: A visual formalism for complex systems

    David Harel · Science of Computer Programming, 8(3), 231–274 · 1987

    Technical reference · Background on explicit states and events. Lemonergy bounded control blocks are not a complete Statecharts implementation.

Implementation sources

This reference follows the public interface and locally verified numerical checks for an upcoming release.

Contract: Lemonergy Studio public contract · Verification record: verification-2026-10-27

  • docs/glossary/native-block-verification.json

This implementation and its workflow uses (JSON) · Knowledge graph (JSON-LD)