-
Notifications
You must be signed in to change notification settings - Fork 28
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
fix demand control range and remapping #271
Conversation
Real ranges are 5-100% but by testing 5-20% don't give any reasonable value.. so it's decided to start from 20%. Also steps are not relevant at all.. for reality there is 3-5 steps.. |
Hmm interesting, |
Could you provide graphics with compressor frequency and demand control? I am curious how it's looks in new model's |
You are asking for a lot of time investment while it's -7°C outside 😂 But anyway, I feel like my changes make sense regardless. |
Yes i know, i done it by myself, and pump react pretty fast, best is to do while preparing dhw, or in cold moment's when pump will work in higher frequency (100hz is ideal) i am not asking to do that, just you said that your pump is reacting in precisely.. so i thought you already have some test's and graphic for it.. |
Just did some DHW and tested. You are right, it does seem to apply fairly quickly. 5%-> 22hz Not sure why it didn't go up to ~60Hz. The firmware seems to be a bit unpredictable sometimes.. |
Yes, because pump have it's own priority.. so it not always true for demand control. Also it will not go higher because there is no demand.. as I told it's best to test when natural pump demand will go to 100Hz. With demand control your not setting demand, but you're limiting pump to it's percentage.. as i see there is no such big difference in 5-20% also.. 22-24hz also could be just fluctuate by limiting it.. same are to other steps.. |
There was demand. It was during a DHW cycle. Target outlet temp = 75°, actual outlet temp = ~40C. Maybe their "demand control" does actually try to modulate up to 9kW, but then later caps the frequency to 60Hz, that's why 75% and 100% is more or less the same. Would be interesting to see what 75% and 100% actually result in on a 9kW unit. I'm just not sure why it only went to 54 and not to 60Hz despite there being demand. But I guess the ways of the aquarea are inscrutable. But yes. Around 5 to 20% is more or less the same. At 25% the changes seem to start. Edit: never mind, it's because the cap is not 60hz, but 5kw. And 5kw was reached with 54hz in this case. |
I do. While the actual improvement is only minor (but existent), it at least makes it match the Heishamon/Panasonic documentation. |
Hi,
the functions to remap the demand control values were wrong, and the range was 20-100% instead of the actual 5-100%.
Old behavior:
New behavior:
This matches the documented range: https://github.com/IgorYbema/HeishaMon/blob/main/OptionalPCB.md#set-command-byte-decrypt
Same for the read function (probably only really relevant when something external manages the demand control as well?.. hopefully never).