So I have a sixth channel logging the compressor state successfully.
Makes it easy to determine my keezer compressor is currently running at a ~24% duty cycle. I can live with that![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Having this working opens up all kinds of "alert" possibilities. Eg: excessive on-time, on-time with no temperature response, temperature above setpoint + differential but compressor not running.
I was surprised to see was how small an effect that period immediately following compressor shut off where the evaporator is still sucking heat has on the keezer temperature. Granted the 5 minute polling resolution means there could be nearly 5 minutes of "jitter" between events, but still it looks like there's very little overshoot. This may be due to all six kegs being roughly 2/3rds full right now - there's around 180 pounds of beer in there and they're not going to move in a hurry![Big Grin :D :D](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Cheers!
Makes it easy to determine my keezer compressor is currently running at a ~24% duty cycle. I can live with that
Having this working opens up all kinds of "alert" possibilities. Eg: excessive on-time, on-time with no temperature response, temperature above setpoint + differential but compressor not running.
I was surprised to see was how small an effect that period immediately following compressor shut off where the evaporator is still sucking heat has on the keezer temperature. Granted the 5 minute polling resolution means there could be nearly 5 minutes of "jitter" between events, but still it looks like there's very little overshoot. This may be due to all six kegs being roughly 2/3rds full right now - there's around 180 pounds of beer in there and they're not going to move in a hurry
Cheers!
![brewpints_49.jpg brewpints_49.jpg](https://cdn.homebrewtalk.com/data/attach/198/198765-brewpints-49.jpg)