lemonergy· battery engineering courses

Lemonergy · Studio block

Conserving vehicle-to-vehicle converter

One conserving converter linking donor and recipient electrical islands.

Implementation ID
v2v-converter
Reviewed
2026-10-27

Behavior

The donor supplies the recipient power and converter losses. Donor reserve, recipient target, voltage envelopes, current limits, permissions and temperature signals limit transfer together. Both islands require an electrical reference.

Interface

Conserving vehicle-to-vehicle converter interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Conserving vehicle-to-vehicle converterStudio blockcommanddonorSocrecipientSocenabledonorBmsPermitrecipientBmsPermitdonorTemperaturerecipientTemperaturedonorPowerrecipientPowerlossdonorCurrentrecipientCurrentdonorVoltagerecipientVoltagealloweddonorPdonorNrecipientPrecipientN
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
donorPconservingV, AElectrical terminal: potential and charge-conserving current.
donorNconservingV, AElectrical terminal: potential and charge-conserving current.
recipientPconservingV, AElectrical terminal: potential and charge-conserving current.
recipientNconservingV, AElectrical terminal: potential and charge-conserving current.
commandinputWRequested power; this does not bypass voltage, current, SOC or permission limits.
donorSocinputfractionTyped signal input; its quantity must match the connected output.
recipientSocinputfractionTyped signal input; its quantity must match the connected output.
enableinputdimensionlessTyped signal input; its quantity must match the connected output.
donorBmsPermitinputdimensionlessTyped signal input; its quantity must match the connected output.
recipientBmsPermitinputdimensionlessTyped signal input; its quantity must match the connected output.
donorTemperatureinputKTyped signal input; its quantity must match the connected output.
recipientTemperatureinputKTyped signal input; its quantity must match the connected output.
donorPoweroutputWObserved result from the solved component or sampled controller.
recipientPoweroutputWObserved result from the solved component or sampled controller.
lossoutputWObserved result from the solved component or sampled controller.
donorCurrentoutputAObserved result from the solved component or sampled controller.
recipientCurrentoutputAObserved result from the solved component or sampled controller.
donorVoltageoutputVObserved result from the solved component or sampled controller.
recipientVoltageoutputVObserved result from the solved component or sampled controller.
allowedoutput0 or 1Observed 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
ParameterUnitDefaultMeaning and limits
Power W
powerW		W recipient DC3000Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1000000000
Donor Capacity Ah
donorCapacityAh		Ah100Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 1e-06; Maximum 1000000000
Recipient Capacity Ah
recipientCapacityAh		Ah100Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 1e-06; Maximum 1000000000
Donor Reserve Soc
donorReserveSoc		fraction0.2Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1
Recipient Target Soc
recipientTargetSoc		fraction0.8Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1
Donor Minimum Voltage V
donorMinimumVoltageV		V250Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0.01; Maximum 1000000
Donor Voltage Droop Ohm
donorVoltageDroopOhm		ohm near minimum-voltage envelope0.01Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 1e-06; Maximum 1000000
Recipient Voltage Limit V
recipientVoltageLimitV		V420Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0.01; Maximum 1000000
Donor Current A
donorCurrentA		A32Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1000000
Recipient Current A
recipientCurrentA		A32Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0; Maximum 1000000
Efficiency
efficiency		fraction0.9Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0.01; Maximum 1
Boundary Time S
boundaryTimeS		s1Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 0.001; Maximum 3600
Min Temperature K
minTemperatureK		K273.15Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 1; Maximum 1000
Max Temperature K
maxTemperatureK		K318.15Configured model parameter; the default is an initial editor value, not an operating recommendation.
Minimum 1; Maximum 1000

Equations and rules

  • P_donor = P_recipient / eta
  • P_loss = P_donor - P_recipient

Worked example

Transfer between two batteries

5 kW delivered at 90% efficiency needs about 5.56 kW from the donor and produces about 0.56 kW loss.

Open the Studio example →

Use in a workflow

Transfer between two batteries

Conserving conversion couples donor and recipient.

  1. Conserving vehicle-to-vehicle converter: Enforces both batteries’ limits
    • donorP / donorN
    • recipientP / recipientN
    • donorReserveSoc / recipientTargetSoc
    • efficiency
Open the Studio example

Connected concepts

Limits and interpretation

  • The example assumes hardware compatibility; it does not establish connector or communication compatibility.

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
  • rust-core/src/charging_control.rs

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