-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fix: have CurrentLimits method in opev and oscev filter for LoadControlLimitDescription instead of MeasurementDescription #144
Conversation
…itDescriptionData instead of MeasurementDescriptionData
Thank you @AhmedMagdyCoretech , this looks great! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall, just some minor adjustments needed.
… for measurement ID in relevant LoadControlLimitDescriptions
… obtained from relevant load control limit descritpions. they need not exist in the measurement description list.
Thank you for the feedback. All the issues have been duly resolved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the changes, just a minor last request regarding a variable name. Sorry if this looks picky, but I understand something else with filters
.
Thank you for the feedback. Not so picky, I would say. Aptly addressed. |
Thank you very much @AhmedMagdyCoretech ! |
Since the "ScopeType" field in the LoadControlLimitDescription is more relevant (with a value of "overloadProtection" and "selfConsumption" for OPEV and OSCEV, respectively), it shall be used as the filter for obtaining the relevant ElectricalConnectionPermittedValueSetListData items in the CurrentLimits getters for OPEV and OSCEV. From the relevant LoadControlLimitDescriptionData items, one can get their corresponding measurement IDs and use them to filter for relevant parameter description items.