Skip to content
This repository was archived by the owner on Jun 29, 2024. It is now read-only.

uclpcserver: align electricalConnectionCharacteristicListData data #30

Closed
wants to merge 1 commit into from

Conversation

DAMEK86
Copy link
Contributor

@DAMEK86 DAMEK86 commented Apr 9, 2024

in Limitation of Power Consumption v1.0.0 section3.2.2.2.5.1 the following data is required

  • powerConsumptionNominalMax
  • contractualConsumptionNominalMax

in Limitation of Power Consumption v1.0.0 section3.2.2.2.5.1 the following data is required
- powerConsumptionNominalMax
- contractualConsumptionNominalMax

Signed-off-by: Andreas Rehn <[email protected]>
@DerAndereAndi
Copy link
Member

DerAndereAndi commented Apr 9, 2024

No, please check the spec again. One is required for consumable devices, the other for the CEM. See chapter 2.2 page 14

@DerAndereAndi DerAndereAndi marked this pull request as draft April 9, 2024 21:54
@DAMEK86
Copy link
Contributor Author

DAMEK86 commented Apr 10, 2024

as far as i can see in the docs on page 57 this section is just for server data resources
image
image

@DerAndereAndi
Copy link
Member

DerAndereAndi commented Apr 10, 2024

Yes, that is what should generally be available when implementing the server feature. BUT a CEM does NOT have a nominal max power consumption and a consumable system does NOT have a contractual max power consumption.

See page 14 chapter 2.2 lines 400-403:

The CS SHOULD inform the Energy Guard about its nominal maximum values (either the Power
Consumption Nominal Max ([LPC-041]) in case the CS is not an energy manager, or the Contractual
Consumption Nominal Max ([LPC-042]) if the CS is an energy manager). The CS SHALL NOT consume
more than the according nominal maximum value.

I fell in the same trap first when blindly implementing the data structures, but when implementing the API I asked myself that question: How can a HEMS have a nominal max. It can't. Then re-read the spec and found the mentioned reference.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants