carrier uc16 program

[fac 213]

I have a uc16 controlling a rooftop unit by a time schedule. Hwout _1 powers a rib relay to start and stop the unit. Also on the CCN are 15 comfort ID VAV boxes. I also have a SPT (T-55), which in in the system, but is not configured to turn the rooftop unit on in the unoccp mode. Can the Linkage/opss schedule be used ? (VAV 15 is the linkage master) Or should I stick with the T-55?

[Balibe]

Sounds like linkage would be the best way to go with your setup, but need to know a bit more on the setup/operation.

What other points do you have on the UC? Which algorithim are you using now to control the S/S of the RTU? Is the RTU also used for heat or just cooling? Do you have a PAT on the master? What controls the heat/cool for the RTU?

If it is not starting in unoccupied now, it wont with linkage either. All the linkage algorithm is going to do is replace the existing sensor you have in the current algorithim. Sounds like you may have another issue. Give as much details as you can.

[fac 213]

OK lets start with the Rooftop unit. The unit is a VAV cooling only, and has a morning warm up control in the unit. I have it set at 65 degrees (retun air). The unit also has the ability to drive all the VAV boxes open for morning warm up. Terminal 1 and 2 on the roof top unit start the sequence. Thats where my rib relay (n.o) contacts are. The rib is powered from HWOUT point 1 on the uc16. I have five inputs on the uc16, Imput -1 is PAT, 2 is OAT, 3 is mixed air, 4 is fan status, which only is fan status, 5 is a T-55 which is not programed to stat or stop the unit. The uc16 is is broadcasting the time and the mixed air, and outdoor air to 6400 wich controls the boilers, and a hot water coil pump in the main supply duct before the VAV boxes. Also VAV 213 which is the linkage master has a PAT.The stats I am using on the VAV boxes are T-59 with a 2 degree offset. The algorithim on HWOUT point 1 is in sevice config from top to bottom is---- yes, 2, 2, HWOUT 1, RTU-1 , 4, 0 .On config for HWOUT 1 (do time clock wopt ck) I have OCCPCO1, and set up a time sch. I do not fully understand the programing for the Linage /OPSS espically the sensor group. I do have the Overview and configuration manual for the uc16. The flow charts blow my mind too. Did I cover everything ?

[ccnster]

Normally it shouldn't be that tough. I generally create a linkage/aoss algo first, and then as you are configuring the other algorithms (fan s/s, hot or chilled water valves, dx cooling, whatever), use the quick look up feature to select the linkage algo as the input for space temp, setpoint schedules, occ schedules and so on. That way you are tying the vav's to the UC through linkage.

[ccnster]

I guess the other question is, what are you using to program the UC? system pilot, cview, or service tool 2?

[fac 213]

I am not familiar with the quick look up feature. Where can I access it?
Also, I have Comfortview 3.1 on the main computer for the building. I have Service Tool 1 which I purchased 4/07. I knew there was a 1.5 version, but I have now found out there is a version 2. Where can I get the update? I searched Carrier's website,with no luck.

[ccnster]

Well, comfortview 3.1 doesn't support programming the universal controller. Neither does service tool 1. CCN web box 2.0 can be used to configure the UC, but there is a few bugs in it. The system pilot is also designed to program the UC, but it is a pain to use. I would get in touch with whomever you purchased service tool 1 from and ask them to get you the upgrade to the newest version. It probably is free. I had put service tool 1 on my computer and in order to upgrade to the newest service tool you also have to install fieldloader on the computer to install the usb drivers (if I remember right). That said, the new service tool works pretty well (and easily) to program the universal. With Cview, if you highlight an input or output when configuring an algorithm and push either F3 or F7 (can't remember which offhand), it brings up a dropdown of acceptable points to choose from. This makes it easy to link algo's together, such as the NTFC or AOSS/linkage into the heating, cooling and fan algo's.

[Balibe]

Well, comfortview 3.1 doesn't support programming the universal controller.

CView will program a UC, I have done it. The procedure is different than other CCN devices. Once you have programmed the algo with the output or type of sensor with the input, you need to delete the UC from your database and then upload it again. Once this is done, you can modify the parameters of it as you would with any other CCN device. If you modify the Service-Configuration in any way, you must delete it and upload again.

Below is from Form 808-346

The following CCN operator interface devices can be used to view and modify data in the Universal Controller:
• System Pilot
• CCNWeb
• ComfortVIEW
• Network Service Tool

Starting on page #11 of Form 808-346, it outlines the following "Configuring a Newly Installed Universal Controller Using ComfortVIEW".

[Balibe]

Not 100% what you have setup in the RTU S/S algo, but with no sensor or setpoint table in the DO:TC it will not turn on in unoccupied. I would setup/modify the UC/VAV’s for linkage operation [listed below]. This way the VAV’s will control the start/stop of the RTU and they will all be on the same occupancy schedule.

Setup below is based on the information you posted above, not sure how the morning warm-up is programmed, the boiler/pump control, how you are driving VAV’s to max, etc. Before you setup linkage or modify any algo’s, make sure your changes won’t affect any other programming. You can also export the controllers before any changes, this way if you have issues you can restore them back to original.

If you want to export the UC, 6400 & master vav and email them to me [email in profile], I can take a look at the programming.

Create the following in the UC
OCCPC65 [schedule for the VAV’s & RTU’s, which will be broadcasted]
SETPT** use next number [this will be backup for loss of linkage]
LINK_01 [the new linkage algo]

In the existing TC w/Chk
-Sensor: Link_01
-Time: Link_01
-Setpoint: Link_01
-Loadshed:
-NTFC:
-TempCheck: Enabled

In the new LINK_01
-Setpoint: SETPT** created above [backup for loss of linkage]
-Optimal:
--Cooling Factor:
--Heating Factor:
Sensor: T-55 Space Sensor [backup for loss of linkage]
Time: OCCPC65 created above
NTFC:
Supply Air: Supply Air Sensor for the RTU
Equip Status: Fan Status input for the RTU
Optimal Stop:
-- Stop Time:
-- Setpoint Delta:
-- Evacuation:
-- Presurization:

In the ComfortID Linkage Master
Config ----> Linkage Table
- Linkage Master: Yes
- Number of Zones: [# of VAV’s including Master]
- Air Source Bus: Bus # of UC
- Air Source Element: Element # of UC

Service ----> Options Table
- Occupancy Schedule: 65

In the ComfortID Slaves
Service ----> Options Table
- Occupancy Schedule: 65

[fac 213]

O K Balibe I followed you instructions, but I need to get to the job , delete the UC16 in service tool and upload, then make a new algo on a on a different point. (dry run) But in the UC -SEPT** , use next number and LINK_01,will I get to change them .

Thanks

[Balibe]

Didnt get to it last night, just dropped you an email. DAT file didnt work.

- Bal

[fac 213]

you couldnot open the program

Frank