-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model 704 WMaxLimPct and WSetPct #216
Comments
There are a lot prioritization questions that come up across the models for active and reactive power control. In general, we have left prioritization out of the communications specification with the view that it may vary across contexts. IEEE 1547-2018 makes statements about prioritization of functions. This approach makes it possible that some decisions are device specific but the alternative of specifying them in the communications specification may not be workable. In the example you site, it seems like WMaxLimPct would limit the values that could be applied with WSetPct but I am not sure that would always be the case. In general, It is probably best for the standards and jurisdictional requirements that specify functional behavior to address these considerations. That can leave a gap in this area, however. |
You mentioned in #154 that WSetPct may be negative. What is the basis if it is negative? Is it always 702-WMax? |
Yes, all active power percentage settings are based on WMax. |
WMaxLimPct is used to limit active power generation of DERs in general (PV and Battery inverters) - usually on request of the distribution network operator.
WSetPct is used to set active power level for DERs that are able to follow a setpoint (e.g. Battery systems) - usually on request of a local energy management system.
For Battery systems that support both (WMaxLimPct and WSetPct), this could lead to conflicting requirements, because, both refer to the AC output of the DER.
Did you consider a prioritization between the two?
The text was updated successfully, but these errors were encountered: