Station model

1 Parameter scope

In dual-connector stations, configuration parameters are scoped explicitly.
The scope found in the Config UI under:

Config UI → Documentation → OCPP Keys

defines how a parameter applies to the connectors.

Scope	Meaning	What this means in practice
# Both	One shared value for both connectors	Changing the value affects connector 1 and 2 equally
# Individual	Separate values per connector	Connector 2 uses the _2 variant of the key
# Not relevant	Not tied to a connector	Applies to the whole station
# Master	Applies only to the backend-facing coordinator	Affects backend communication and coordination only

1.1 Master-scoped parameters

Some parameters are marked Master in the Config UI.

• These parameters are configured and evaluated on the station coordinator (connector 1).
• Their effect may be station-wide, depending on the feature.
• Connector-specific behavior is handled through Individual parameters (_2).

tip

For Master scope, configure the value on the station coordinator only (connector 1).

1.2 Connector-specific suffix

For Individual parameters:

• Connector 1 uses the OCPP key without a suffix.
• Connector 2 uses the _2 suffix.

This pattern applies to all connector-scoped OCPP parameters.

Example: Connector phase rotation

// Connector 1
{"key": "ConnectorPhaseRotation", "value": "RST"}

// Connector 2
{"key": "ConnectorPhaseRotation_2", "value": "RTS"}

The _2 suffix changes the behavior of connector 2 only.

2 Coordinator Behavior (Dual-Connector Stations)

• The backend connects to an OCPP backend through one of the connectors
• The active backend connection determines which connector acts as connector 1
• Regardless of backend connection state, connector 1 is typically also the Master Controller outside of OCPP communication
• The station internally coordinates between the two connectors
• The backend sees a single Charging Station with two connectors
• There is never a separate backend connection for connector 2