-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
Setting inverter limit needs about 25 - 90 seconds to be fully active #571
Comments
You are very welcome to buy a DTU pro, disassemble it and trace the packages sent to the inverter when the zero export function is active. |
one question: does Ahoy DTU already have that feature , so it may be possible to take it over from there ? is that zero export function a secret ? |
The question is if this zero export function is really faster working than setting the inverter limit. Perhaps it is just advertised as zero export but in fact inverterter takes also with official DTU Pro some time to adjust. I'm reluctant to buy a DTU Pro and check myself, because you also need a special energy meter to communicate with DTU Pro, see https://www.hoymiles.com/wp-content/uploads/2023/01/Technical-Note-Export-Management-Guide-of-Hoymiles-Microinverter-System_AU.pdf page 3. As far as I remember this is Modbus protocol. Of course you could also generate these packages to use Shelly 3EM to feed the current power values into DTU Pro, but also that requires a lot of time and I'm over 50 % sure that also with official DTU Pro inverter won't adapt its output power faster with Zero Export enabled in DTU Pro. So there is a high risk of investing a lot of time for nothing, because also official devices won't work better than OpenDTU. |
today isnt sunny here , got issues to test it.
-> it could be that the hoymiles firmware is ramping up/down slowly, but i have seen different reports in the internet about almost instant reactions ...... |
Hi, i can confirm that the HM300 is ramping with about 5W roughly in 3s , starting from the previous limit :-( thats slow regards, |
In AhoyDtu project various ramp rates are described: It would be great if we could set these parameters in openDtu to get a faster reaction. |
Apparently the ramp speed to set a new limit can be configured to 15s (soft limit) or 2s (hard limit) as per appendix 2 |
I understand this appendix different. Hardlimit disconnects the inverter and in the example the softlimit is 500 Watt, whereas the hardlimit is 1 kW
|
@JsBergbau @Simon566 thanks for describing and measuring the ramp up / down rates with your installations and the Shelly 3EM. The Ramp Up / Down Rates are defined per inverter in a so called Grid Profile. This can be set via the S-Miles Cloud and a DTU connected to your inverter. We have an option in newer OpenDTU versions to extract the current Grid Profile in binary / Hex-Format from the UI. There are already about a dozen distinct Grid Profiles documented on the Wiki: https://github.com/tbnobody/OpenDTU/wiki/Grid-Profile-Parser Thanks to @noone2k we already have a python script which can be used to parse these Grid Profiles #1527 and make sense of the encoded settings within the binary code. So it would be good to identify the values in your inverters for the Normal RUR_NM and Soft Start Ramp up Rates RUR_SS. In fact there is a separate Guide from Hoymiles on the Grid Profiles which also goes into some depth of how the Ramp Up / Down Rates work and are applied. https://www.hoymiles.com/wp-content/uploads/2022/11/Technical-Note-How-to-set-Hoymiles-3Gen-Grid-Profile-V1.1.pdf So in general this issue / feature request is more of a long shot as we need to understand and implement setting the Grid Profile first #365, but the these parameters may be adjusted #256 within the given regulations, laws and policies of your country. |
Due to the fact that this is related to grid profiles and not to OpenDTU i would close this issue. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
What happened?
Setting the inverter limit either via MQTT (/cmd/limit_persistent_relative) or Webpage (HM-1500) it takes about 18 seconds until inverter reacts and begins adjusting the power. After about 25 seconds the inverter is using the new power limit fully, so it gradually adjusts the power over a few seconds.
According to https://www.hoymiles.com/wp-content/uploads/2023/01/Technical-Note-Export-Management-Guide-of-Hoymiles-Microinverter-System_AU.pdf there is a Zero Export control with original DTU-Pro. So to support Zero Export the inverter must react much faster. I think that this faster mode can be enabled in the inverter otherwise "Zero Export" as Hoymiles advertises is no real zero export because load can change a lot in 25 seconds.
With a Shelly 3-PM it can be verified that this delay is real and current output power display in OpenDTU is in sync with power Shelly 3-PM reports.
To Reproduce Bug
Set the power limit and measure the time until new output power can be mesured.
Expected Behavior
Output power is adjusted within 1-3 seconds.
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
b5d099f
Relevant log/trace output
No response
Anything else?
Maybe this mode can't be enabled and it is a limit of the inverter, but than "Zero Export" as Hoymiles advertises is a marketing trick because it reacts much too slowly and there will be power exported and of course also imported, because increasing the inverter power also needs some time.
MQTT messages was sent at 12:50:15 to reduce power to 10 % (before 100 %)
Inverter began adjusting power at 12:51:40, so about 90 seconds later.
Until it was completly adjusted it was 12:53:21, so it took about 100 seconds to adjust power, together with the time until it began adjusting power about 3 minutes have passed. This is much too slow.
Update: Going back from 10 % too 100 % it began after 2 seconds with adjusting the power, but until power was fully adjusted 90 seconds passed
The text was updated successfully, but these errors were encountered: