Tracer Summit-Missing something?

[michael26]

I have a building with 7 upcms which I have worked with, and a newer version of summit of which I don't have a clue. My problem is that I am sending out two binary setpoints to the boiler-room upcm to start the primary and secondary chilled water pumps based on outside air temperature. Which has an adjustable setpoint through summit, an analog setpoint. The binary setpoint I can change from summit if I right click and pull up the editor. These will turn the pumps on and off. But they don't work in unless changed manually. Does summit have a section that writes some sort of logic to these points, if so where do I find it? Or how do I change this to automatic? Under editor there are two over and under arrows to the left of this selection on or off and I can change this and save it. But how do I get this to auto? Also what turns on the rtaa340. How does the summit communicate through the bus to the chiller. I see a "chiller plant" under controllers but is there logic to this? I have worked with xbs before and it seems really easy compared to this. All the "user low" "priority" stuff I just don't get it. Where is the logic in the summit to control binary set-points. Also why store the logic in the front end. What if the computer is off. Am I missing something, please help. T-I-A

[Burnt-Out]

Yes your missing something, the logic is in the BCU not the computer for one thing.
As for the Binary outs, You will need to have a cpl routine driving them for any type of automatic operation.
The chiller is most likely connected to the lon network

[michael26]

O.k. the logic is in the BCU and I found the cpl screen but where do I find the screen that tells me what points the logic controls. There are two chillers and one is on the lon side but the one that I am having problems with is the com3/4. So a loss of communication value is for a loss with the bcu and not summit?

[henpecked]

I have a building with 7 upcms which I have worked with, and a newer version of summit of which I don't have a clue. My problem is that I am sending out two binary setpoints to the boiler-room upcm to start the primary and secondary chilled water pumps based on outside air temperature. Which has an adjustable setpoint through summit, an analog setpoint. The binary setpoint I can change from summit if I right click and pull up the editor. These will turn the pumps on and off. But they don't work in unless changed manually. Does summit have a section that writes some sort of logic to these points, if so where do I find it?

The pumps are probably controlled by logic within the UPCMs. You need to get UPCM edit and look at the PCL routines to see the logic controlling the pumps. It would be a pretty simple to write a PCL for the UPCM to do what you're talking about. All you're probably going to find in Summit is network variables/setpoints that the PCL routine inside the UPCM looks at to operate the pumps.

I don't really know why anyone would do this with a CPL in summit, it's possible to do it that way, but it would be much easier to do what you're wanting in the UPCM--if for no other reason, the pumps would still be controlled even if comms with the BCU were lost.




Or how do I change this to automatic? Under editor there are two over and under arrows to the left of this selection on or off and I can change this and save it. But how do I get this to auto? Also what turns on the rtaa340. How does the summit communicate through the bus to the chiller. I see a "chiller plant" under controllers but is there logic to this?

The BCU should communicate with the RTAA chiller on a com 3 link. Chiller Plant Control inside the BCU itself will control the chiller based on user settings.



I have worked with xbs before and it seems really easy compared to this. All the "user low" "priority" stuff I just don't get it. Where is the logic in the summit to control binary set-points. Also why store the logic in the front end. What if the computer is off. Am I missing something, please help. T-I-A

Logic isn't "stored" in the front end/workstation, everything (except graphics) is stored in the BCU and controllers, and even then, most all of the "logic" is going to be in the controllers, not in the BCU-- except for CPL routines (if you have any). The priority array is easy-- the lower the number, the higher the priority.

Hope this helps..