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

[Request] DPL inverter set/get compensation #1314

Open
gitisgreat2023 opened this issue Oct 8, 2024 · 0 comments
Open

[Request] DPL inverter set/get compensation #1314

gitisgreat2023 opened this issue Oct 8, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@gitisgreat2023
Copy link

gitisgreat2023 commented Oct 8, 2024

Is your feature request related to a problem? Please describe.

See the issue in this discussion. In DPL, when the set limit value for the inverter doesn't match the actual value, the target value isn't reached.

Describe the solution you'd like

A set/get compensation for each inverter.

Describe alternatives you've considered

I implemented a set/get compensation in a Shelly script, added the difference between the set limit and actual produced inverter power. Every 5 seconds I update that value, thereby avoiding oscillations due to the response time of the inverter setting a new limit. This solution works perfectly fine now for four weeks, applying it on two inverters individually working parallel on a shared battery.

As I currently anyway already need the Shelly script to distribute the power on the two inverters, I'm happy with my current solution. But others could profit from having it available in OpenDTU-OnBattery itself, for example if there is for some reason an asymmetry in the inverter strains (not equal cable lengths etc) which typically causes a set/get mismatch.

Additional context

The DPL convergences to the target value if and only if the get (read) value from the inverter is indeed accurate. If for example cable losses between the output of the inverter and the meter are substantial, the target value won't be reached accurately.
I also didn't change the 5 secs over the 4 weeks period, it might be for these relative small changes (say max 100 W) the timescale the inverter reacts is shorter. I didn't study that.

@gitisgreat2023 gitisgreat2023 added the enhancement New feature or request label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant