MPC and MGCP use cases as actors Monitored Unit and Grid Connection Point#169
MPC and MGCP use cases as actors Monitored Unit and Grid Connection Point#169jaroslawsky wants to merge 4 commits intoenbility:devfrom
Conversation
… a Monitored Unit actor
…se as a Grid Connection Point actor
… Unit and Grid Connection Point It's possible to test these cases with the controlbox simulator from https://github.com/vollautomat/eebus-go/tree/simulators
|
By the way, the MPC use case has already been successfully tested with real hardware - specifically with a Vaillant VR921. |
|
Hi Klaus, thanks for the PR and congrats on your efforts for creating the control box simulator. Well done! I will take a closer look as soon as I find some time. Some quick notes:
I mainly developed this all alone. Used my own experience and best practices for establishing a code and comment style. It is far from perfect. I did not write them down formally, getting the stack to this stage was way too much work already. So I put the efforts where I see them being of best use. This also means that going over a PR will be a bit more effort that otherwise, as contributors can only prepare by looking at the currently implemented code as an example. Hope this sounds fine for you. Best, |
|
Hello Andreas, I don’t expect more than what you’ve mentioned. Everything is fine. I’ll just wait until you’ve had time to look into it and then I’ll try to address any potential comments. If the MPC use case is excluded because it has already been implemented elsewhere, that’s absolutely no problem. I would then only need to focus on the tests for the MGCP use case, which makes things easier for me. However, I don’t have much experience with Go and its environment yet, so I’ll need to familiarize myself with the test framework first. It will also take me a little time on my end. Best regards, |
For both use cases, there has only been code available so far for the actor "Monitoring Appliance." This feature branch is now intended to also enable the implementation of the respective counterparts. Admittedly, the test cases are still missing here. If these are considered indispensable, please let me know. I will then endeavor to create them.
These implementations can be interactively tested using the controlbox simulator from this repository. Both the newly added "smartmeter" example and the modified "hems" example from the mentioned simulator repository can be used.
Both examples send a PowerLimitationFactor value one second after the connection is established and changing values for all other parameters every three seconds. These values are not necessarily very realistic. The aim was simply to send something that constantly changes. This makes it easiest to observe the functioning of the two use cases.
Using the simulator looks like this:
