Problem with Energy.Active.Import.Register since 03.02.2020 (V0.4.15 - V0.4.16)

[McFranky]

ABB Terra Firmware 1.5.2

Problem:
Energy.Active.Import.Register
I got dropouts over the time

The problem can be identifed in the log:
Normal MeterValues; Energy.Active.Import.Register = 895Wh = 0,89kWh; thats correct
2022-02-04 06:29:19 INFO (MainThread) [ocpp] ILET01: receive message [2, "5430689", "MeterValues", {"connectorId": 1, "transactionId": 1643951526, "meterValue": [{"timestamp": "2022-02-04T05:29:17.000Z", "sampledValue": [{"value": "222.30", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L1-N", "unit": "V"}, {"value": "14.30", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L1", "unit": "A"}, {"value": "3144", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L1", "unit": "W"}, {"value": "228.70", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L2-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L2", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L2", "unit": "W"}, {"value": "226.40", "context": "Sample.Periodic", "format": "Raw", "measurand": "Voltage", "phase": "L3-N", "unit": "V"}, {"value": "0.0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Import", "phase": "L3", "unit": "A"}, {"value": "0", "context": "Sample.Periodic", "format": "Raw", "measurand": "Power.Active.Import", "phase": "L3", "unit": "W"}, {"value": "895", "context": "Sample.Periodic", "format": "Raw", "measurand": "Energy.Active.Import.Register", "unit": "Wh"}, {"value": "16", "context": "Sample.Periodic", "format": "Raw", "measurand": "Current.Offered", "unit": "A"}]}]}]

A litle bit later than this:
2022-02-04 06:30:01 INFO (MainThread) [ocpp] ILET01: receive message [2, "6287334", "MeterValues", {"connectorId": 1, "meterValue": [{"timestamp": "2022-02-04T05:30:00.000Z", "sampledValue": [{"value": "10531", "context": "Sample.Clock", "format": "Raw", "measurand": "Energy.Active.Import.Register", "location": "Inlet"}]}]}]

UnNormal MeterValues; Energy.Active.Import.Register = 10531Wh = 10,53kWh; thats not correct (Is this the total energy (not session)?)

The second is without transactionID!

I have a new Firmware on the ABB Terra. I think thats a new problem. Can you filter only Energy.Active.Import.Register values with transactionID?

Greetings from Berlin
Frank

[drc38]

If you reinstall the integration and set "Charger idle sampling interval" to 0 that will turn off the clock sampling as a temporary fix.

[drc38]

I think the simplest approach is to assume Energy.Active.Import.Register should be monotonically increasing (ie majority of chargers output). An if statement can be used to check if new value > old value and if not, updated value = new delta + old

[lbbrhzn]

Not sure how we would, seems it is manufacturer dependent! That is they have interpreted the ocpp 1.6 spec differently. My charger always reports an absolute meter value. What does the wallbox do?

MeterValues for connect_id=0 should be for all connectors combined, MeterValues with connector_id>0 should be for a specific connector. Not sure how many chargers there are for domestic use with multiple connectors though.

[drc38]

I don't think it will output MeterValues for connector_id=0 when charging, @McFranky can you check?

[lbbrhzn]

From OCPP spec:

MeterValues_req,connecor_id:
The id of the Connector from which samples were taken. If the connectorId is 0, it is associated with the entire Charge Point. If the connectorId is 0 and the Measurand is energy related, the sample SHOULD be taken from the main energy meter.

[lbbrhzn]

@drc38: We should distinguish between meter values with transaction_id and without.

The Charge Point SHALL send a MeterValues.req PDU for offloading meter values. The request PDU SHALL contain for each sample:
The transaction Id of the transaction to which these values are related, if applicable. If there is no transaction in progress or if the values are taken from the main meter, then transaction id may be omitted.

For each energy sensor that we create we should decide whether it displays main or transaction related data. If they are transaction related they should be reset by the charger at the start of a transaction, and otherwise not. In our current implementation we ignore the transaction_id, and assume that all meter values are not transaction related. To compute the session energy, we subtract the value at start.

For non-energy related values (power, current, etc) there should only be differences between main and transaction if it supports multiple connectors, so it supports concurrent transactions. Let's not worry about that now.

[McFranky]

connector_id is 1 (look to my first message) There is only one connector on my wallboxes (7x ABB Terra) Am 04.02.2022, 19:38:34, drc38 ***@***.***> schrieb: > > > I don't think it will out MeterValues for connector_id=0, @McFranky (https://github.com/McFranky) can you check? > > > > — > Reply to this email directly, view it on GitHub (#366 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AOHLA2SXFWFIBQTUQFRDYFLUZQMKVANCNFSM5NRH2WJA). > Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub). > You are receiving this because you were mentioned.Message ID: ***@***.***> > >

[lbbrhzn]

I've created issue #374 for this

[gytisgreitai]

Hey, should this be fixed? I somehow have a strange graph?

And the value ... 37690 kwh? is there some decimal issue?

[drc38]

Did you set "Charger idle sampling interval" to 0 as suggested above?

[gytisgreitai]

sorry, missed that - thought that it was needed before the fix. Removed and re-added, set to zero, let's see how it goes. Also I somehow failed to remove OCPP via UI, had to do that through various .store/core.* files

[gytisgreitai]

The energy import register accumulates from charger installation every charge session's energy

ok, so with sampling interval set to 0 for ABB Terra this does not seem to be the case? Looks like it's equal to sessions energy. Is this yet another quirk of the ABB Terra?

[drc38]

Probably! If you want it to show the accumulated register instead you could try not selecting the energy.active.import.register when setting up the integration and turn back on the sampling interval.

[drc38]

This should now be fixed in release v0.4.42 thanks to @nlindn