Overshoot compensation #140
Open
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
kev300
force-pushed
the
overshoot_compensation
branch
from
06bc805
to
c36c9ee
Compare
kev300
force-pushed
the
overshoot_compensation
branch
3 times, most recently
from
e2e63b9
to
cb10f0e
Compare
kev300
force-pushed
the
overshoot_compensation
branch
from
2b26c5f
to
402a2d3
Compare
|
This happens, if the latency value is too high. So I made it adjustable. (cargingAmps = charging Amps ;-) ) Currently, when the battery is cold, it cannot be charged. So I need to set the Inverter to output the incoming solar power as fast as possible. BTW: This is another case for a very fast update intervall without overshooting. 👅 |
|
There is a typo in |
added 10 commits
February 20, 2024 10:09
kev300
force-pushed
the
overshoot_compensation
branch
from
0c9071c
to
65d86ea
Compare
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.
Like #122 but less complicated and works better with ramping consumption changes. :)
Fixes: #73 (for me)
Also there is no pid setting anymore, only max_power_sensor_latency_ms.
It is necessary because the inverter does not exactly hit it's power target (demand +500W actually ends up producing something like +480W) and when multiple loads are changing within the compensation period.
Works for me with an update intervall of 250ms at the moment. Without this PR the demand only jumps between min demand and max demand constantly. 😬