Initial support for Algodue UEM meters on CP0 and CP1 #1960
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
caching prevents this to appear too often
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds support for Algodue UEM meters at internal chargepoints.
Tested with a modified openWB2 and a UEM80-4D R (Modbus RTU version).
Modbus Address is set to 155 for CP0 and 156 for CP1. Please adjust if does not fit the openWB adressing concepts (which I don't know).
Same registers should be valid for Ethernet/Modbus-TCP models (e.g. UEM80-4D E).
But since, according to my reverse-engineering of the code, ability to configure EVU Kit to use it requires UI changes and is generally more complex, I was not yet able to integrate that.
Additionally the problem is that EVU-Kit has hard-coded Modbus-TCP Port numberr of 8899 but Algodue meter's Modbus Port is the standard-port 502 and cannot be changed.
Maybe it can more easily be integrated with an openWB-Flex-Kit. Hints are welcome. But it could also be integrated in a second pull request.