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

Use ObjectAcConnection to fetch /Ac/PvOn* phase totals #1908

Open
blammit opened this issue Feb 17, 2025 · 0 comments · May be fixed by #1909
Open

Use ObjectAcConnection to fetch /Ac/PvOn* phase totals #1908

blammit opened this issue Feb 17, 2025 · 0 comments · May be fixed by #1909
Assignees
Milestone

Comments

@blammit
Copy link
Contributor

blammit commented Feb 17, 2025

The /Ac/PvOnGrid, /Ac/PvOnGenset and /Ac/PvOnOutput values may change frequently, so the PvMonitor implementation is sub-optimal as it re-calculates the phase totals for these values whenever a single phase value has changed.

Use ObjectAcConnection to monitor these values instead, as that is only done once per second.

@blammit blammit added this to the Version 1.1.0 milestone Feb 17, 2025
@blammit blammit self-assigned this Feb 17, 2025
blammit added a commit that referenced this issue Feb 17, 2025
The /Ac/PvOnGrid, /Ac/PvOnGenset and /Ac/PvOnOutput values may change
frequently, so the PvMonitor implementation was sub-optimal as it
re-calculated the phase totals for these values whenever a single
phase value was changed.

Use ObjectAcConnection to monitor these values instead, as that only
calculates the totals once per second.

Fixes #1908
@blammit blammit linked a pull request Feb 17, 2025 that will close this issue
blammit added a commit that referenced this issue Feb 17, 2025
The /Ac/PvOnGrid, /Ac/PvOnGenset and /Ac/PvOnOutput values may change
frequently, so the PvMonitor implementation was sub-optimal as it
re-calculated the phase totals for these values whenever a single
phase value was changed.

Use ObjectAcConnection to monitor these values instead, as that only
calculates the totals once per second.

Fixes #1908
blammit added a commit that referenced this issue Feb 17, 2025
The /Ac/PvOnGrid, /Ac/PvOnGenset and /Ac/PvOnOutput values may change
frequently, so the PvMonitor implementation was sub-optimal as it
re-calculated the phase totals for these values whenever a single
phase value was changed.

Use ObjectAcConnection to monitor these values instead, as that only
calculates the totals once per second.

Fixes #1908
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant