-
Member Post posted an update
I’m doing the PMs on a York YK chiller. Its running at the same time with another chiller. That other chiller is at setpoint and running at 44% loaded. The York is also at setpoint and its not unloading. It’s staying running at 100% loaded. What would keep it from unloading?
Member Post12 Comments-
Different chilled water set point on the other machine? You are still a degree above the set point on the one you are showing. If the other one is at 44 or 45 it might act this way.
2 -
I would bet it is how the sequencing of the chillers is set up in the automation system. sorry in advance for the essay, but below is how this typically works.
Its very common for them to cycle chillers between lead and lag over some programmable period of time to spread out the operational hours. This is how it will typically work
When BAS Calls for Cooling
> The Lead Chiller is Enabled and runs off internal controller logic to maintain the leaving water temp
> if the lead chiller is at 100%, and there is more load, the loop temp will continue to rise.
> if its still rising, and there is no alarms, the BAS, or the chillers internal logic will notice that we need more load, and it will start the Lag chiller
> once it starts the lag chiller, the lag chiller will also run off of its internal logic to maintain leaving water temp.The way they do the transition to the lag chiller varies, sometimes they will override the chillers controller, and unload the Lead chiller by 15-20%, start the second machine, and bring the Lead chiller back up to 100% before loading the Lag. Sometimes both chillers can be set up to talk to each other, and do most of this through the internal logic, so the Lead chiller starts the lag chiller, and not the BAS system.
There are tons of ways to do it, but its very common to see a lead / lag setup in a similar way to this on most commercial applications.
1-
@the-chiller-guys I have seen issues with loading just based on the capacity of the chillers. Not sure the tonnage on this one but before the lag is enabled and started, the lead must drop down that 15-20% to not overshoot and give that capacity to the lag.
-
@goldie is that something configured in the machine, or the automation?
To me it seems like it’s got plenty of load, is it overshooting? -
@the-chiller-guys Ive only ever seen it in the automation in BACnet. I set it up on Daikin chillers. Signal drops to 50% capacity before enable gets sent to the lag. Then the lag gets a 50% signal when started up. Obviously has to run on its pull down limits but with the loop already cool enough, shouldn’t have an issue pulling down at 40% capacity.
-
@goldie are you having issues with it pulling down?
Or were you just curious why they didn’t bring the lead chiller down, and load and unload the two in unison? -
@the-chiller-guys I used to do startups on Daikin chillers do I was setting it up from initial.
They did have issues meeting the SP with 1 chiller running at 100%, so by design they wanted to load 2 at 50% and stage up from there as needed after certain time sequences lapse.
-
-
-
If that is the case, the chillers will show what the active chilled water set point is and that would confirm it.
-
This is a 134A chiller Discharge superheat is 19 I think it should be closer to 15 on the YK. also the delta on the condenser water is a little high not by much. PRV position only 16 % @100% FLA. This explains higher then normal Oil temp in sump due to vanes being closed down some and the heat of compression adding to oil traveling thru compressor. I would check flow rate and see if it could stand a lil more charge. maybe other issues just a quick glance
2-
You know you may be able to lower liquid level setpoint in condenser and see if you can get it to settle down there as well
2-
@brian-medley yeah, I had to take one from 50% to 25% to get it to act right. It would help if we had pics of the other machine too.
1
-
-
-
It has not reached setpoint so the chillers are either different capacity or the York is receiving more load
-