Skip to content

Conversation

sthelen-enqs
Copy link
Contributor

According to the EEBus UC Implementation Guideline for LPC v1.0.0 section 2.2 1):
If Actor Controllable System receives an Active Power Consumption Limit with a duration set to "0", the limit SHALL immediately be deactivated by the Controllable System (see [LPC-007]). If the received write command contains a duration set to "0" AND also a request to set the Active Power Consumption Limit to "activated", the Actor Controllable System SHALL ignore the request

This has the added effect for us, that previously in the CS-LPC/CS-LPP API it was next to impossible to differentiate between a limit without a duration (active forever), and a limit with a 0 duration.

According to the EEBus UC Implementation Guideline for LPC v1.0.0
section 2.2 1):
If Actor Controllable System receives an Active Power Consumption Limit
with a duration set to "0", the limit SHALL immediately be deactivated
by the Controllable System (see [LPC-007]). If the received write
command contains a duration set to "0" AND also a request to set the
Active Power Consumption Limit to "activated", the Actor Controllable
System SHALL ignore the request

This has the added effect for us, that previously in the CS-LPC/CS-LPP
API it was next to impossible to differentiate between a limit without a
duration (active forever), and a limit with a 0 duration.
@sthelen-enqs sthelen-enqs self-assigned this Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants