Lemonergy · Studio block

Bus assignment

Replaces selected bus fields while preserving every other field.

Implementation ID
bus-assign
Reviewed
2026-10-27

Behavior

Replacement ports inherit the exact declared field types. The original bus value remains unchanged for other consumers.

Interface

Bus assignment interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Bus assignmentStudio blockbusstate.socbus
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
businput1pack; named bus with declared typed fields.
state.socinputfractionReplace state.soc; real signal.
busoutput1pack; named bus with declared typed fields.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Bus declaration
bus
1packExplicit bus used by this worked model.
Replacement field paths
fields
1["state.soc"]Explicit fields used by this worked model.

Equations and rules

  • updated[field] = replacement for selected fields; original[field] otherwise

Worked example

Update nested battery telemetry

Initial-SOC = 0.5; Updated-SOC = 0.6; Cell-voltage = 3.7. Before at 1 s = 0.5; After at 1 s = 0.6.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Before
Before
10.5fraction1e-09
After
After
10.6fraction1e-09

Use in a workflow

Update nested battery telemetry

Replaces selected bus fields while preserving every other field.

  1. Bus assignment: Replacement ports inherit the exact declared field types. The original bus value remains unchanged for other consumers.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • A field and one of its descendants cannot be replaced in the same assignment; replacement paths must be distinct.

Reference basis

This software operation is defined by its public contract and worked example; no external research result is claimed.

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)