Skip to main content

Weidmueller reportování od 0

Subject: OCPP: Energy.Active.Import.Register Reports Reset on Each Session Instead of Cumulative Total

Dear Weidmüller Support,

I’m currently operating a Weidmüller Wallbox using the OCPP 1.6 protocol. I have encountered an issue related to the energy metering values being reported during charging sessions. The details about my wallbox from BootNotification are:

{"chargePointVendor":"Weidmueller","chargePointModel":"ACSMART","chargePointSerialNumber":"AX3722EM1100005","firmwareVersion":"01.06.01"}

I have configured the Wallbox to report Energy.Active.Import.Register in MeterValuesSampledData, and I receive periodic meter values (every 60 seconds). However, I’ve noticed the following behavior:

  • During an active charging session, the value reported for Energy.Active.Import.Register starts at 0 and increases relative to the session — as if it’s reporting per-session energy consumption.
  • At the end of the transaction (StopTransaction), the Wallbox reports the correct cumulative meter reading (as expected for Energy.Active.Import.Register).

According to the OCPP 1.6 specification, the measurand Energy.Active.Import.Register should reflect the total cumulative imported energy from the grid (in Wh), and should never reset during or between sessions.

This behavior causes confusion in the backend, as the sampled values during the session suggest a meter that resets to 0 at the start of every session — which is not the expected behavior for this measurand.

Questions

  1. Is there a setting or firmware update available to ensure that Energy.Active.Import.Register always reports the correct cumulative energy meter value — even during active sessions?
  2. Is it possible to switch the Wallbox from “session-based energy reporting” to “meter-based reporting” for this measurand?
  3. If the current behavior is by design, is there an alternative measurand or configuration that will provide true cumulative readings during sessions?

For reference, my current OCPP settings/configuration include:

{
    "WebSocketPingInterval": "60",
    "ConnectionTimeOut": "30",
    "ConnectorMaximumCurrent": "16",
    "HeartbeatInterval": "100",
    "MeterValueSampleInterval": "60",
    "NumberOfConnectors": "1",
    "TransactionMessageAttempts": "5",
    "TransactionMessageRetryInterval": "60",
    "ClockAlignedDataInterval": "0",
    "GetConfigurationMaxKeys": "29",
    "LocalAuthorizeOffline": "false",
    "LocalPreAuthorize": "true",
    "MeterValuesAlignedData": "",
    "MeterValuesSampledData": "Voltage.L1,Voltage.L2,Voltage.L3,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered,Energy.Active.Import.Register,Power.Active.Import,Temperature",
    "ResetRetries": "0",
    "ConnectorPhaseRotation": "NotApplicable",
    "StopTransactionOnEVSideDisconnect": "true",
    "StopTransactionOnInvalidId": "false",
    "StopTxnAlignedData": "",
    "StopTxnSampledData": "",
    "SupportedFeatureProfiles": "Core, Smart Charging",
    "UnlockConnectorOnEVSideDisconnect": "true",
    "AuthorizeRemoteTxRequests": "false",
    "ReserveConnectorZeroSupported": "false",
    "ChargeProfileMaxStackLevel": "9",
    "ChargingScheduleAllowedChargingRateUnit": "Current",
    "ChargingScheduleMaxPeriods": "10",
    "ConnectorSwitch3to1PhaseSupported": "0",
    "MaxChargingProfilesInstalled": "10"
}

Attaching my logs for further reference (upper left corner).

Best regards, Kamil Horák UnichargePay s.r.o.

Back to top