I’m not sure I follow what you’re looking for with “cycle time”. When you narrow the target range, the dehumidifier cycles on and off more times in a period of time than it will with a broader target range, right? Have you messed with setting a constant target, instead of a range, and using a buffer?
Controlling drying with the wine cooler by using the dehumidifier to generate heat and cycle the cooler on sounds like a difficult target.
I’ll try to catch up tonight and see if I’m misunderstanding methods you’re trying to dial in to achieve your goals.
So, Firstly I cannot take credit for any of this. I have viewed 100s of videos/threads all over the internet, that have blazed this trail long before me, so thank you to all of them.
So, the cycle time, and forgive me if I misunderstood your question. The Dehumidifier is just that, a fully programmable stand alone device. No other person I know of used this device, so there is that deviation to the design, that my executive decision determined was appropriate, from my research. Additionally, the modules available online where not up to snuff, and required additional resources that in the end drove up costs and added more unnecessary complexity to the build.
Typically, other users tear down and strip a Dehumidifier to only the module, and control it with a third party programmable controller. I can achieve this by simply connecting my Dehumidifier to an AC Infinity controller and cycle it with the AC Infinity controller.
But, it is just as simple to use the onboard programming functionality of the Dehumidifier and until someone tells me different, I'm not confident there is an advantage to cycling power with the third party controller. Albeit, since I'm already using it to monitor environment, why not use it to control the Dehumidifier, so the thought of it is not lost on me.
Okay, according to the internet...the purpose of the Dehumidifier, is to raise the internal temperature of the wine cooler, resulting in the cycling of power to the wine cooler, based off of the temperature target of the wine cooler. The Dehumidifier cycle time is determined by the controller.
Here is the rub...if controlling the Dehumidifier is managed by a third party controller, then the cycle time of the Dehumidifier is short, very short. This is a result of the third party controller being satisfied when target temp is reached, by the cooling efforts of the wine cooler that has been triggered by the third party controller.
Conversely, using the Dehumidifier's onboard programming controls, allow for a different scenario. This is where I dropped the ball, only to later, have an epiphany regarding the cycle time.
Originally, I had set the cycle time too long. My data set proves that the Dehumidifier was heating the interior so much, that the wine cooler fought to cool the interior and defeated the purpose of a slow and cold drying environment. Instead, I had big swings in the environment and unachievable environmental goals.
My remedy to this, was to drastically reduce the cycle time of the Dehumidifier, by changing the parameters or triggers. In doing so, the goals have been met, with regard to the environment.
I now have the correct environment for my goal of a slow and cold dry. Please know this. I am a rookie. I am learning. I am sharing, even my failures. All, in an effort to further our communities effort to have the very best experience.
So, please continue to deep dive this subject and thank you.
