Lemonergy · Studio block

Physical availability / signal schedule

A typed physical signal selected by explicit time windows.

Implementation ID: signal-schedule
Reviewed: 2026-10-27

Behavior

Each window is active on its half-open interval [startS, endS). Outside all windows the block emits defaultValue. Windows are ordered and cannot overlap; adjacent windows are allowed.

Interface

Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.

Ports and observed outputs
Name	Direction	Unit	Meaning
`out`	output	declared signal quantity	Observed result from the solved component or sampled controller.

Parameters

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

Configuration fields
Parameter	Unit	Default	Meaning and limits
Default Value `defaultValue`	declared signal	0	Configured model parameter; the default is an initial editor value, not an operating recommendation. Minimum -1000000000000; Maximum 1000000000000
Schedule windows `schedule`	startS/endS in s; value in declared signal quantity	Supplied by the user	Required array of 1 to 32 ordered, nonoverlapping {startS, endS, value} windows; endS must exceed startS. This is a document field, not a scalar parameter.

Equations and rules

out(t) = window.value when startS <= t < endS; defaultValue otherwise

Worked example

Charge during available stops

A 15-minute stop at a 100 kW grid cap has a 25 kWh upper grid-energy bound before losses and battery limits.

Open the Studio example →

Use in a workflow

Charge during available stops

Availability is an independent signal.

Physical availability / signal schedule: Defines stop windows
- defaultValue
- startS / endS / value

Open the Studio example

Connected concepts

Limits and interpretation

All battery and converter limits still apply. A schedule is not an electrochemical law.

Implementation sources

This reference follows Lemonergy implementation sources. Scientific articles support the linked concepts separately.

Repository: battery-design · Revision: ef9802329b75bc15bb96885f8ed5d49425106696

js/charging-control.js
js/charging-scenarios.js
docs/CHARGING_BLOCKS_SPEC.md
js/physical-network.js

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