Skip to content
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

GenericPowermeter: improve logging and fix Modbus range #730

Merged
merged 3 commits into from
Jun 21, 2024

Conversation

mhei
Copy link
Contributor

@mhei mhei commented Jun 18, 2024

Describe your changes

This PR fixes a small issue with the allowed range of Modbus addresses, and it introduces log messages in case the power meter communication is interrupted or restored.

Issue ticket number and link

The logging part is related to #523, but it not the complete fix for this issue.

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements
  • chargebyte internal review approved this PR

The Modbus RTU address range only permits addresses from 1 to 247
(at least what makes sense in our context here).

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
This introduces a high-level/device specific logging in case
communication with power meter is failing or communication is
restored again.

Signed-off-by: Michael Heimpold <michael.heimpold@chargebyte.com>
@mhei mhei force-pushed the cb-genericpowermeter-logging branch from c186c80 to c1246a6 Compare June 18, 2024 20:03
@barsnick barsnick merged commit 951e592 into EVerest:main Jun 21, 2024
5 of 6 checks passed
@barsnick barsnick deleted the cb-genericpowermeter-logging branch June 21, 2024 11:43
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.

3 participants