DPL: Solar inverter max increase calculcation is less strict, respects overscaling configuration and more #1487
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.
As we are having issues with solar inverters reporting that they can't increase their power i tried to analyse the methods and developed ideas what could be the cause and how to fix those. + the configured overscaling input power threshold should be used for this calculation as well.
Ideas
Low limits
Inverters with low limit (below 15%) are usually not able to provide the expected power and we would rate mppts as shaded.
This will result in us thinking that we can't get more power from that inverter and the limit is 'stuck'.
Strict checks
The max increase calculation is based on the overscaling method but it actually does not need to be as strict.
I lowered the input power threshold from 98% to 97% to be less strict and to hopefully let more inverters recover from low limits.
This won't hurt because if the inverter is actually not able to provide what we calculated we will fix this in the next DPL run.
Threshold config
As said earlier the max increase calculation is based on the overscaling method, and it needs to be, we need to make sure they stay aligned. Thats why i will now use the configured input threshold to calculate max increase.
Missing visibility
We can't really debug whats going on because the key factor to determine the max increase and also for scaling the limit is the power power MPPT. I added this information when debug logging is enabled.
Related discussion