Commissioning & Standard Programming Using CCT

Commissioning & Standard Programming using CCT
Day 1
Agenda
Day 1 2
missioning & Standard Programming using Lesson – Adding and Modifying Activity
Lesson – Overview
CCT Modules
Lesson – Introduction to Controllers Activity - Modifying a Configuration
Lesson – Troubleshooting Software

Lesson – Sideloops
Connections
Activity - Data Flow and Viewing Activity - Create a Feedback Control

Connections Sideloop
Lesson – Modifying Inputs and Outputs
Activity - Input/Output Commissioning
Lesson Lab Resources

Agenda
Day 1 2
Lesson – State Tables Activity – Custom Logic
Lesson – Data Flow and Saturation Timers
Lesson - Logic Blocks
Lesson - Timers
Lesson - MUX
Lesson - PRAC and PID
Lesson Lab Resources

Overview
Day 1 Overview
Overview
Tier 1
Server /
Software
Tier 2
Supervisor de
Red
Tier 3
Controladores
de Campo
Tier 4 Valves and

Campo Actuator
Sensors
Transducers
Excellence in Training Online Product Literature

Day 1 Overview
Que es un BAS (Sistema de Automatización de Edificios)?
Colección de componentes individuales de control y software que trabajan

juntos, como un Sistema, para Automatizar el funcionamiento de un edificio
HVAC, iluminación y otros subsistemas mecánicos y eléctricos.
Optimiza
Costos de
Operación
Asegura
Confort de ¿Por que los ▪ Minimiza el uso de
ocupación, clientes energía
seguridad y ▪ Elimina o minimiza el
salud. adquieren BAS? uso de un operador.
▪ Alarga el tiempo de
vida
▪ Extiende la vida del
activo.

Day 1 Overview
Arquitectura del Sistema Facility Explorer
Distribuido Escalable Seguro Abierto
Integra
Los componentes Se pueden agregar
dispositivos de
se pueden situar lo componentes
terceros y
más cerca posible según sea Protege contra el
generaciones
del equipo que necesario para acceso no
anteriores de
están controlando, controlar edificios y autorizado a
componentes
para proporcionar sistemas de datos y sistemas
Metasys para
un rendimiento y complejidad, de control
unificar y
una fiabilidad tamaño y alcance
modernizar su
óptimos diferentes.
funcionamiento

Introduction to Controllers
Day 1 Introduction to Controllers
Objectives
At the end of this session, you will be able to:

Identify controllers belonging to the FX family of controllers
Describe available family components

Key Topics
Overview
Field Equipment Controllers
FX Family Components:
Field Controllers and Sensors
Wireless Field Bus System
FX Family Overview
Click each topic to learn about it.

Visão geral – Quais são os controladores de equipamentos de campo?
A family of FX Equipment Controllers that operate with FX Supervisor:

Programmable Controllers - General (PCGs)
Programmable Controllers – Advanced (PCAs)
Programmable Controllers – Expansion (PCXs) (BACnet® or SA Bus Only)
Programmable Controllers – VAV (PCVs)
Network Control Engine (SNC – Generation 4), hybrid NAE/PCG
Programmable Controllers – General (CGM) Generation 4
Programmable Controllers – VAV (CVM) Generation 4
Networked Thermostats (TEC) and Networked Sensors (NSs)
Local Display Module (DIS)
They communicate either IP or Field Controller Bus, which can be configured for
BACnet® Master-Slave/Token-Passing (MS/TP) or N2 protocols
They use a wide range of standard applications to control HVAC equipment

FX Family Components—Field Controllers and Sensors
Programmable Programmable Controllers Programmable

Network Control Engine
Controllers General Advanced Controllers – VAV
Programmable Controllers Field Equipment

Network Sensors IP Controllers Controllers Generation 4
Expansion

PCV Controllers
PCV16 (32-bit) PCV19 (32-bit)

FX-PCV models CCT-1615, and PCV-1630, Similar to PCV16, except:
include three universal inputs
Star or Daisy Chain (TCP IP Network
Provides an economical offering for applications Configuration)
requiring CO2 + DA-T sensing
Ring configuration
FX-PCVs include state-of-the-art digital
pressure sensor Local History
Provides improved accuracy, especially in low- Local Alarm

flow applications
Local Schedule
Supports bi-directional flow operation with
automatic pressure polarity correction, with Real-time Clock
eliminates high/low pressure tube connection
mistakes BACnet® IP
Point capacity can be expanded by adding

PCX’s
32-bit microprocessor
N2 or BACnet® MS/TP

PCG/PCA Controllers
PCG PCX
32-bit processor Expands I/O Capacity for FX-PCGs, PCA’s
and PCV’s
Optional local display
Has no internal control logic capability
Supports wireless communications
Several models with various I/O counts and
N2 or BACnet® MS/TP mixes
I/O Modules are BACnet® or SA Bus (on N2

or BACnet® configured Field Controllers)
only

PCG/PCA Controllers
PCA PCA49
Similar to PCG, except: Similar to PCG, except:

Real-time clock Star or Daisy Chain (TCP IP Network
Configuration)
Local scheduling option
Ring configuraration
Local trend option
BACnet® IP
Local alarm option
N2 or BACnet® MS/TP

PCG/PCA Controllers
F4-CGM F4-CVM
Similar to PCA, except: Similar to PCV, except:
RX64M 32-bit Renesas microcontroller RX64M 32-bit Renesas microcontroller
16 MB flash memory and 8 MB SDRAM 16 MB flash memory and 8 MB SDRAM
Set of 3 Rotary switches used to set device Set of 3 Rotary switches used to set device
address between 4 and 127 address between 4 and 127
Super capacitor maintains power to the onboard Super capacitor maintains power to the onboard
real-time clock for a minimum of 72 hours real-time clock for a minimum of 72 hours
N2 or BACnet® MS/TP N2 or BACnet® MS/TP

Network Sensors
BACnet® Master-Slave/Token-Passing (MS/TP) protocol communication

between controller and sensors on the SA Bus
Backlit LCD available on some models
Simple temperature setpoint adjustment available on some models
Onboard PIR Occupancy Sensor available on some models
Temporary Occupancy available on some models
Field-selectable default display setting available
on some models
Fahrenheit/Celsius (F/C) button available
on some models

Local Displays
At-a-glance system status

Complete access to operating parameters and setpoints
Easy-to-use interface
Tactile-feel keypad
Backlit LCD
Customized user preferences
Password protection (optional)
Easy panel installation
Compatible with all PCG, PCV, and PCA
models without integral displays

Mobile Access Portal Gateway (MAP)
Provides a wireless mobile user interface to all field devices

Complete access to operating parameters and setpoints - viewing and
commanding
Easy-to-use interface
Ethernet and Wi-Fi Connectivity
Browser-based remote building management
Password protection
Portable or stationary versions available
User interface is customizable using CCT for
PCG, PCV, and PCA controllers

Bluetooth® Converter
Allows commissioning and servicing of the controllers over a wireless

connection
Any controller on FC Bus can be commissioned by connecting to any other
controller, sensor, or PCX connected on the same bus
Controllers using the N2 protocol may only be commissioned locally

Handheld VAV Balancing Tool
Convenient, Portable VAV Balancing Tool

Allows user to easily view, adjust, and set the required parameters for VAV
applications running in a PCV
DP offset
Actual flow and flow setpoints
Auto-calibrate
Box gain (K factor)
Balancing parameters are displayed on the tool’s
LCD

Handheld VAV Balancing Tool (Cont'd.)
Navigation is menu-based using the dial and push buttons

Menus are customized based on the application residing in the PCV
Can plug into the service port on the NS for convenient access
(no ladder required)

ZigBee® Wireless USB Dongle
Allows a laptop to connect to a ZigBee® Field Router (ZFR) Wireless Field Bus
for the purpose of commissioning and downloading applications
Analyzing a ZFR wireless mesh using the ZFR Checkout Tool (ZCT)
Wireless Field Bus system is not available with N2 networks

FX Family Components—Wireless Field Bus System
Supervisory engines
Network Automation Engine (NAE)
Network Control Engines (NCE)
BACnet® field controllers
Field Equipment Controllers
VAV Modular Assemblies
I/O Modules
Room sensors
Network Sensors
Wireless Mesh temperature sensors
Wireless Field Bus system is not available with N2 networks.

PCG Family Overview

Troubleshooting Software Connections
Day 1 Troubleshooting Software Connections
Objectives
After completing this module you should be able to:

Perform an analysis of an application by viewing Connections and using
Show Involvement
Perform an analysis of state-based control

Key Topics
Troubleshooting Software Commissioning Data Flow

Connections
View Connections
State-Based Control

Commissioning Data Flow
Data flows from left to right in CCT. Inputs can be

connected to and evaluated by modules in the
Setpoint/Miscellaneous column Input
Setpoint/Miscellaneous outputs flow into State Values
Generation modules, where the mode or state of Setpoint/Miscellaneous

different subsystems is determined Values
State Generation outputs flow into the State Generation

State Tables State
State Tables pass values to Output Control State Tables

modules
Mode
Output Control modules pass signals to the Output Control
Outputs
Values
Outputs

Commissioning Data Flow (Cont’d.)
The Last Value (LV) module holds the value that its input had at the end of the
previous execution of the control system for use by the current execution as a way
to bring an output back into the program.
For example: State Generation

State Generation modules often need State
a value from an Output Control module
State Tables..
Mode
Output Control
Values
LV Block
At CCT version 6.0 or higher, LV modules can be hidden.

Commissioning Data Flow (Cont’d.)
Output Control modules pass signals to the LV module, which are then
passed back to the State Generator modules.
LV Blocks are always used when the result of a process is fed back into a
another process
State Generation
State
State Tables..
Mode
Output Control
Values
LV Block
At CCT version 6.0 or higher, LV modules can be hidden.

View Connections
In this example, by selecting the Connections tab in the Features panel and then
selecting the ZNT-SP Network Input, we note that the output of ZNT-SP is
connected to the Network Setpoint port of the ZN-T Setpoint Determination
module.
Destination blocks are

actually modules in CCT.

View Connections (Cont’d.)
Then by selecting ZN-T Setpoint Determination, all the input and output
connections for this module can be identified including the connection from
ZNT-SP. In this way, connections from one module to the next can be followed.

Connections view hints:

Use Ctrl to select and view connections for more than one module within a
category. Ctrl+A will select all modules in a category.
The connections tab has additional buttons to Show All connections, Show
State Selector connections, to Expose additional Ports on modules, and to
Freeze the connections view.

The Connections tab allows you to identify connections between modules

CCT uses a consistent Connections color scheme: inputs are yellow, outputs
are cyan
This is true in the Logic view as well
To aid in analyzing data flow, there is a Show Involvement feature (shown)
Input and outputs display their
Present Value in the Connections
view when simulating or
commissioning

Let’s take a closer look at data flow and connections.
DEMO

State-Based Control
Control is based on states.

Methods include the following:
Finite State Machine (FSM): A CCT logic block that contains code to produce a
specific state
State Selection that actually determines which FSM or State Generator sets
the specific state (or mode) for control
The use of FSMs and State Generators eliminates the possibility of conflict in the
logic.

State-Based Control (Cont’d.)
Example - Simple State Devices for a VAV Box with Reheat Application
Heating PID at 0.0% Zone temperature greater

for the Saturation Time than cooling Setpoint
Heating Satisfied Cooling

Minimum
Modulate Modulate
flow
heating valve damper
no heating
Zone temperature less Cooling PID at 0.0%

than heating Setpoint for the Saturation Time
Transition event conditions consider both time and value comparisons.

Basic Data Flow
State
Setpoint/Misc Generation State Output
(Process (Decides which Selection Control
Variable Input) state should run (State Tables) (PID)
- FSM)
Room Temp Heating Heating = Control Heating = 0-100%

Cooling = Off Cooling = 0%
NetStat Inputs Heating and Cooling

Outputs

To use the Show Involvement feature:

Right-click an Output and select Show Involvement
Modules involved with controlling the Output are highlighted magenta
Right-click the output again and select Hide Involvement to return to normal

Show Involvement can also be displayed in a separate window by selecting

the checkbox for Settings → Use Involvement Dialog
The Show Involvement window can be resized
Within the Show Involvement window, module columns can be resized
The Show Involvement window has focus and must be closed before other
actions can be taken

Key Points
Data flows from left to right in applications. Inputs are typically connected to
and evaluated by modules in the Setpoint/Miscellaneous column. LV Blocks
are used to return an output value back into the program.
Select the Connections tab in the Features panel to view connections. You
can view various combinations of module connections using the Ctrl key and
the Connections tab buttons.
Methods for establishing state-based control include Finite State Machines
(FSM) and State Selection to determine which FSM or State Generator sets
the control mode

Discussion

Activity - Data Flow and Viewing Connections
Day 1 Activity - Data Flow and Viewing Connections
Objectives
After completion of this lab, you will be able to:
Follow connections throughout an application

Analyze State Table connections
Requirement
Computer with CCT and the Rooftop.caf file.
Estimated Time
This exercise will take about 15 minutes to complete.

→ Check Zone Temperature Connections

How do I do it? Helpful Hints and Notes:
1. Launch CCT and open Rooftop.caf
2. Select ZN-T and select the Connections

tab
Using Help, answer the following questions:

Q1 How many Destination modules does the ZN-T Output go to?
Q2 What is the default value for the ZN-T sensor Output?

→ Check Unocc Status Determination Module Connections

1. View the connections for the

Unocc Status Determination module
Q3 How many unique Source modules send data to the Unocc Status Determination module?
Q4 What is its Destination module(s)?

→ Check the State Table Connections

1. On the Connections tab,

Click Show All
2. View the first module displayed. The

header name should be State Selection.
State Table Inputs on the left (yellow) and
Outputs (cyan) on the right will be visible,
along with their connections.
Q5 How many Input Source Modules does this State Table use?

Q6 Is there an Output connection from the State Table to the Proportional Cooling Control
module?
Q7 If so, what is the connection Port name?

→ Examine the Proportional Cooling Control Module Connections

1. View connections for the Proportional

Cooling Control module
Q8 How many Input Source modules are there?
Q9 Is one of them from the State Table?

Q10 What are its Destination modules?

→ Examine the Zone Temperature Setpoint Determination Module Connections

1. View connections for the ZN-T Setpoint

Determination module
Q11 Since CLGOCC-SP is not connected to anything, what is its Present Value?
Q12 How many modules receive a value from the EFFCLG-SP Output connection?
You have completed this lab.

Answers
Q1 How many Destination modules does the ZN-T Output go to?
Ans. There should be four modules.
Q2 What is the default value for the ZN-T sensor?
Ans. 72° F (22.0° C)
Q3 How many unique Source modules send data to the Unocc Status Determination module?
Ans. There should be three modules.
Q4 What is its Destination module(s)?
Ans. State Selection
Q5 How many Input Source modules does this State Table use?
Ans. 11
Q6 Is there an Output connection from the State Table to the Proportional Cooling Control module?
Ans. Yes

Q7 If so, what is the connection Port name?
Ans. Mode
Q8 How many Input Source modules are there?
Ans. 7
Q9 Is one of them from the State Table?
Ans. Yes
Q10 What are its Destination modules?
Ans. Cooling Control Status LV, CLG-O, and Cooling Percent Cmd LV.
Q11 Since CLGOCC-SP is not connected to anything, what is its Present Value?
Ans. 74° F (23.0° C)
Q12 How many modules receive a value from the EFFCLG-SP Output connection?
Ans. Three

Modifying Inputs and Outputs
Day 1 Modifying Inputs and Outputs
Objectives
After completing this module you will be able to:

Identify types of inputs and outputs on a controller
Discuss the process for adding or modifying an input or output to an application
in CCT
Change the name or type of signal assigned to a point

Key Topics

Click the topic to learn about it.

Icons
CCT uses icons to identify what is connected to the controller.

Input or Output directly connected to the controller
Input or Output connected to an PCX on the SA Bus
Input or Output from a NetSensor on the SA Bus
Input or Output from a VSD on the SA Bus
This is an object connected via peer-to-peer
This is an object with a trend defined on an Advanced Application controller
This is an object with an alarm defined on an Advanced Application controller
This is an object with a schedule defined on an Advanced Application controller

Input Types
CCT has three Input types:

Network Inputs
Defined during the system selection process
Values are from the system or user commanded
Used for Peer-to-Peer data sharing
Inputs
Exist as hardware, physically connected to
the controller
Input examples are:
Analog or Binary inputs
NetSensor inputs
VSD inputs
Miscellaneous
Used for the override monitoring feature

Network Inputs
Network Inputs are software objects which hold a value received through the
system (operator or otherwise) and can also be updated by Peer-to-Peer
communications.
There are three data types used in CCT
Boolean
Float
Enum
All are available as Network Inputs:
Boolean: False/True only
Float: Floating point analog values
Enum: 2 or more states
Enumeration Sets are 2 or more states (i.e., Off/On - 2 states, or
Occupied/Unoccupied/Standby - 3 states. Enum set Box Mode has 8 states.) There are many
Enum sets available, and custom sets can be created.

Inputs
Type of functional input: Analog Input

Controller point type: Universal Input
Type of functional input: Binary Input
Controller point type: Binary Input or Universal Input
Type of functional input: NetSensor
Device connects on the SA Bus
Analog Input
Binary Input
NetSensor

Inputs (Cont’d.)
Analog Inputs are defined by tree selection or added with CCT

For NetSensor Inputs, configuration is already done in the NetSensor device
and cannot be changed
Configure the effective range for analog Inputs in the Details view of the object

Inputs (Cont’d.)
Right-click New on the Inputs heading and you will get a selection menu of
predefined inputs
The filter is for words that appear in any column
Try typing phrases like “temperature N” to find all temperatures with nickel
elements or “zone temp” to find all zone temperature types

Inputs (Cont’d.)
Binary Inputs are defined by tree selection or added with CCT; they are
primarily used as status Inputs and as accumulator Inputs
Universal Inputs are configured to receive either an analog or binary signal.
Binary Inputs will only accept a binary signal.
Binary Inputs are expected to be dry contact only, no voltage
Polarity, Normal or Reverse, can be set in the object’s detail view

Output Types
CCT has three Output types:

Network Outputs
Defined during the system selection process
Values are sent to the system
Used for Peer-to-Peer data sharing
Outputs
Exist as hardware, physically connected to
the controller
Output examples are:
Analog or Binary outputs
NetSensor outputs
VSD outputs
Miscellaneous
Used for advanced features

Network Outputs
Network Outputs are software objects which hold a value from the program,
potentially to send to the system and can also be used in Peer-to-Peer
communications
There are three data types used in CCT

Boolean
Float
Enum
All are available as Network Outputs:
Boolean: False/True only
Float: Floating point analog values
Enum: 2 or more states
Enumeration Sets are 2 or more states (i.e., Off/On - 2 states, or

Occupied/Unoccupied/Standby - 3 states. Enum set Box Mode has 8 states.) There are many
Enum sets available, and custom sets can be created.

Outputs
Type of functional output: Analog Output

Controller point type: Analog Output
Controller point type: Universal Output
Controller point type: Configurable Output

Outputs (Cont’d.)
Type of functional output: Binary Output

Controller point type: Relay Output
Controller point type: Binary Output
Controller point type: Universal Output
Controller point type: Configurable Output

Outputs (Cont’d.)
Right-click New on the Outputs heading and you will get a selection menu of
predefined outputs
The Filter is for words that appear in any column

Key Points
Configurable outputs:
Are externally sourced triacs
Triacs require a load and minimum current flow to operate
Can only be voltage type when configured as analog
There are wiring considerations
Universal outputs:
Are externally sourced N-Channel MOSFETs
Will accept 30 VAC or 30 VDC @ 500 mA
Have no minimum current or load requirement
Can be voltage or current when configured as analog
There are wiring considerations

Key Points
Analog outputs:
Analog outputs are defined by tree selection or added with CCT
Analog outputs are normally configured as a 0-100% command
For each output, the span and direction can be configured in the object’s
detail view

Changing Signals
To change an input or output signal:

Right-click the Input or Output module and select Modify Signal to make the
related dialog box appear
Highlight the signal desired and Click Update

Get ready to Actively Participate

Discussion

Activity - Input/Output Commissioning
Day 1 Activity - Input/Output Commissioning
Session Overview
This session consists of a PowerPoint presentation of input and output commissioning, an instructor
demonstration, and a lab, which will reinforce concepts from the demonstration.
Objective
After completion of this lab, you will be able to commission the I/O objects of a controller application.
Requirements
1. Computer with CCT software
2. Mobile Access Portal (MAP) or Wireless Commissioning Converter (BTCVT)
3. An FC bus with MS/TP controllers connected to it
Estimated Time
This exercise takes about 45 minutes to complete.

Contents
Activity 1 Hardware Point Commissioning
Activity 2 Commissioning Input Points
Activity 3 Calibrate Analog Input Points
Activity 4 Commissioning Peer-to-Peer Communication
Activity 5 Receiving Device (PCV )
Activity 6 Testing the Application

Before Starting the Commissioning Labs:

Use the procedures you have learned in the transferring files labs and download the PCG at
address 5 with the file called MASP VAV with OA-T.caf. You will need to open the CAF file, use the
Define Hardware Wizard and make sure all points are assigned, and finally set the Device Address to
5. Use the transfer function and download the file into the controller. The SA/FC Bus switch on the test
panel will need to be set to SA. Close the file after the transfer is complete.

Activity 1: Hardware Point Commissioning

1. Launch CCT You should now be looking at the main screen

with no program opened.

Q1 What is the only mode available to you when no application file is open?
2. Click the Commission mode button A Connection window appears.

3. Select the appropriate:

Transfer Type
Connection Type
Connection Parameters
Discovery
4. Click Next

5. Locate the PCG at address 5, select it, and You can use the Discovery button to force
click Next another auto-discover.
Your display may differ slightly, depending

upon the controllers on your network.

6. In the Commission Device window, If Unbound References is True, then you

the Commission Summary with have a broken connection link for one
Device Information appears (or more) objects in this application.
Note the Boot and Main Code Version The Device Information window contains
the same information as appears in the
Controller Information feature.

7. Confirm that this is the controller you wish to

commission and click Finish
8. Monitor the progress on the Status bar and

text messages at the bottom of the screen
during the transfer process
Results: The application file first transfers

from the controller to the computer,
immediately followed by live data displayed in
CCT.
You may be prompted to upgrade the file.

Q2 Which mode buttons are available at the top of the screen now?
Device still online to the engine:

Unlike previous JCI field controllers, the PCG product family does not go offline when in the
Commission mode. This is helpful for testing field points that communicate over the network
to an engine.
When does the device go offline to the engine?

There are going to be times when inputs and outputs will need to be commanded from the engine to
verify operation. In those situations, we must first enter Test Mode. This will take the controller offline to
the engine. Peer-to-Peer links still function on the bus.
When in Test Mode and the controller is offline (red Xs), point statuses will display:
??? <present value> Offline
in the UI.

9. Select the check box next to Start Test There is no indication that Test Mode is active
Mode. You may have to maximize the except for the check box.
Commissioning Control Bar at the bottom
of the display.
Local commands are now allowed since the
field device is offline to the engine.

Testing Network Input points is only available in Test Mode.

Test Mode avoids FX features reacting to commands issued in Commission mode.
Intrinsic Trends on objects continue to function.
When viewing live data in the Commission mode, changing values are highlighted in color. Colored
highlighting is determined by the frequency the value changes. As poll cycles return consistent values,
the highlight fades away.
The intention of this feature is to bring to attention changes across the applications data system, to
expose potential relationships between values and modules, and assist in troubleshooting.
Temporary color highlighting appears in three color stages (blue, yellow, and red). After the third
stage (red), all subsequent consecutive changes continue to display red. For more information on
status color, see Control Tab Status Colors and Icons in Help.
The parameter change color highlighting feature can be turned on or off from the
Commissioning Control Bar.
When Start Test Mode is deselected, all local commands are sent a Restore command.

10. Right-click SF-C Note that the Commands selection is

available.
11. Clear the check box next to

Start Test Mode
Note that the Commands selection is now
12. Right-click SF-C again unavailable.

Commissioning Output Points

Inputs and outputs assigned to an SA Bus Input Output Module (IOM) will be listed alphabetically,
with the inputs and outputs assigned to connections on the controller.
The table below lists some of the Output points. It was filled in by displaying View Details.
Object Name Description Object Type Attribute Device Type and Connection
MAD-O Mixed Air Damper Output AO CO OUT5
SF-C Supply Fan Command BO BO OUT1
SF-O Supply Fan Output AO CO OUT6
Hovering the cursor over a point will display point information and signal type.
Outputs that are commanded by the application will be tested as you exercise the control strategy. You
should also manually test any of the outputs that are not commanded by the application.
To adjust the output range of an Analog Output in CCT, double-click the point and edit the
Min Out Value and Max Out Value.

Activity 2: Commissioning Input Points

1. Fill in the table below for the Input points Tip: There are various ways to obtain point
(ZN-H is filled in as an example) information:
Hover over the point
Open the Details window
Use the Define Hardware Wizard/Point
Assignment tab
Object Name Description Object Type Attribute Point Type and Signal
Connection
ZN-H Zone Humidity AI NetSensor SAB
DA-T
DA1-P
SF-S
OA-T

Q3 List the input points that have an orange background color.
Q4 What does the orange color indicate? (Use Help - search for orange.)
You can also check monitor only points for reliability and accuracy. A monitor only point is the one that
is not used by CCT application logic.

2. Find any monitor only points in your CAF file Tip: An easy way to highlight a group of
by selecting all your Inputs modules within a category is to select one
module and type Ctrl + A. This keyboard
shortcut works in many other Windows
programs as well.
3. Select the Connections tab in the Features Points that are not connected to modules in
panel the application are known as monitor only
points.

Q5 Determine which Inputs are monitor only and record your findings below.
Q6 How would you determine if a monitor only point is working properly?

Activity 3: Calibrate Analog Input Points

Calibration can only be performed in the Commission mode. Sensors such as temperature or humidity are
compared against a reliable reference. If you need to calibrate an input, right-click the point and select
View Details. The Details window opens. Select Edit and enter the appropriate correction value in the
Offset field. Select Close to save.
1. Locate DA-T on the inputs of the controller Re-enter Commission mode if you have
you are commissioning left it.
2. Hover over the point and record its The icon will identify whether the point is
location and point number: connected directly to a controller or to an PCX
Record the device on the SA Bus.
For assistance with the icons, select Help →

and point number Topics from the menu bar. Select Search,
type icons in the Enter search term box, and
click Search. Select Control Tab Status
of DA-T. Colors and Icons from the Search results
list.

3. Plug the lab panel gray I/O cable into the

connector under the device (PCX or PCG)
where DA-T is defined. Adjust the
appropriate potentiometer for a reasonable
value.
Record the current value of DA-T.
4. Assume you have used a temperature tester

and read an actual DA-T value that is 1° F
(0.5° C) higher than you just recorded
5. Right-click DA-T and select View Details You will have to wait up to three minutes for
the value to update. Filtering is built into all
controllers.

6. Click Edit and enter 1 in the Offset field
7. Click Apply and Close If you edit Offset to calibrate points, make
sure you upload the .caf file afterwards to
Did your value change to 1° F higher than save the changes.
what you recorded above?

Calibrating Binary Input Points

For Binary Input points, the Polarity parameter controls the reporting of the object’s value. Normal Polarity
reports an open contact as the first state of the States Text (Enum Set). If a Binary Input is giving you an
opposite incorrect value, change the Polarity to Reverse.

Using TUNING-RESET
(Read only, there are no exercises to perform.)
The following scenario is an example where TUNING-RESET can regain tuning control very quickly.
Scenario:
A. Construction is still active at the job site.
B. The crew needs airflow so the PCG controlling the AHU is downloaded to get the fan system up and
running.
C. Since the central plant chiller system is not yet operational, there is no water flowing through the AHU’s
cooling coils.
D. The chiller system is not planned to be functional for a few days. During this time, the fan system
toggles between Occupied/Unoccupied to provide air flow for the crew.
E. During this time, the PCG’s automatic tuning features attempt to tune the AHU cooling valve output but
fails because there is no chilled water flowing in the system.
F. The central plant comes online and chilled water becomes available for the cooling coil.

G. The PCG tuning values need to be reset as chilled water is available now. There are two methods
to reset the tuning parameters:
Re-download the original CAF file to the PCG
This is the only fix for CAF files created prior to CCT Rel 5.0
Command the PCG’s TUNING-RESET Network Input point to True
This point is available for CAF files created at CCT Release 5.0+
Within 20 seconds of sending a True command, the PID tuning parameters are back to
original starting values
Re-tuning can take close to half an hour to fully complete

Other TUNING-RESET scenarios may be:

The chilled water system is turned off for the season and there is warm weather
The plant is shut down for extended maintenance
If there are many devices (like a series of VAV boxes), you could use Trunk Utilities to reset many
controllers at once. Add the TUNING-RESET Network Input as an attribute and write the True/False value.
Below is how an Attribute Template might look:

Activity 4: Commissioning Peer-to-Peer Communication

General rules regarding Peer-to-Peer communication:
1. Peer-to-Peer communication works between points in different devices on the same bus
(not across the site or through engines)
2. Network Inputs will read values from source controllers; therefore, Network Inputs must be defined to
locate a source object. Network Outputs are needed to send data to third party BACnet® devices.
Some applications are:

1. Sharing outside air temperature without using a Global Data Sharing object in an engine
2. Sharing the result of a calculation (Enthalpy, Tonnage, etc.)
3. Sharing fan status with VAV boxes (this lab will use this application).
This would save engine processing time since you would not have to use a Global Data Sharing object.
Sequence of Operation:
The PCV will have its UNITEN-MODE (Network Input) read the value of the PCG’s SF-S. When SF-S is
On, the PCV ’s UNITEN-MODE will become Enable, while when the SF-S is Off, UNITEN-MODE will
become Shutdown.

Activity 5: Receiving Device (PCV )
1. Open the file called VAV Box.CAF
2. Right-click UNITEN-MODE in Network

Inputs and select View Details
3. In the Peer Reference section, the

Instance Number is 6029, which is the
BACnet® ID of the source PCG
4. Notice that the Object Identifier is 1095, You are directing UNITEN-MODE to read the
which is the PCG’s SF-S Input PCG’s SF-S object Present Value.
Object Identifier
5. Click Close

6. Open the file named MASP VAV with The BACnet® ID of the PCG is found in the
OA-T.CAF and click Define Hardware. Define Hardware Wizard.
Select the Network Settings tab.

7. Verify that the source PCG’s BACnet® ID is If necessary, make the changes shown above
the same as the UNITEN-MODE Peer and re-download the controller(s).
Reference in the PCV
Destination Object
Source Object
(Attribute: Peer Reference)
Engine1 Object’s
Device Device Object Device
Point Type and Network Input’s Object Name
Trunk 1 Name BACnet® ID Name Name
BACnet® ID
NAE5 MASP VAV

6029 SF-S BI 1095 VAV Box UNITEN-MODE
Trunk #1 AHU
VAV Box
(to PCV 11)
SF-S
(from PCG5) UNITEN-MODE Unit Enable
Mode controlled by SF-S

8. Download the MASP VAV with OA-T.caf file

into the PCG, if you haven’t done so already
9. Open the file called VAV Box.CAF. Verify

that the PCV address is 11 and matches the
switch settings on the PCV . Download the
PCV if necessary.
10. Set up the training PCG panel as follows: Use the right-side of the training PCG panel to
toggle the SF-S point.
a. Plug the thick gray I/O cable into the large
connector located below the PCG
controller
Start Commission mode of the PCG and
b. Flip the BI3 toggle switch to the right. This confirm that BI3 is changing SF-S.
simulates SF-S in the Off mode.
This will only work if you have the PCG test
kit. If you are using a different setup, you can
wire your own toggle switch into BI3 on the
PCG

Activity 6: Testing the Application
1. Open the PCV program and start You may have to move the MAP or
Commission mode BTCVT to a port on the PCV .
Note the current value of UNITEN-MODE.
2. Turn SF-S (BI3) On, left position if you are This is simulates the SF-S Binary Input going
using the PCG test panel. Command the On in the PCG.
point On if you are not using the test
panel. According to the VAV box specification, when
UNITEN-MODE is enabled, the supply
damper (DPR-O) starts to modulate open.
Note the value of UNITEN-MODE.

3. Wait for 5–10 seconds

4. Turn SF-S Off and note that

UNITEN-MODE changed
5. Exit the Commission mode

If there is time, go back and explore anything you did not fully understand.

Adding and Modifying Activity Modules
Day 2 Adding and Modifying Activity Modules
Objectives

Define an Activity Module
Create a new Activity Module
Insert new logic into an Activity Module
Insert a Standard Module and modify it to meet a sequence

Key Topics
Adding and Modifying Activity Modules Defined

Activity Modules
Creating New Activities
Viewing and Modifying the Inserted
Logic
Modifying a Standard Module

Activity Modules Defined
An Activity:
Acts as a container for Logic Blocks
Contains logic integral to the module

Stuart Price
Stuart Price is a relatively new technician. In the rest of this module, we follow
Stuart as he uses CCT to add and modify activities. His steps are marked
throughout with red numbers.
Stuart Price

Creating New Activities
Our example - Stuart needs to average 3 sensors
1 Right-click Category
2 Select New

Creating New Activities (Cont’d.)
Enter Ac to Filter to
3
Activity Module.
5 Name the Module.
4 Change Count to 3.
6 Click Finish.

7 Right-click the Module.
8 Click Insert Logic.

Enter Ac to Filter
9 for Activity Inputs
and Outputs.
12 Name the Modules.

Change Input
10
Count to 3.
11 Change Output
Count to 1.
13 Click Finish.

15 Click Insert Logic.

16 Enter Av to Filter to AVG.
18 Click Finish.

20 Click View Logic.

Viewing and Modifying the Inserted Logic
Arrange the Blocks

1 by Dragging them
around the screen. Connect ZONE TEMP-1,
2 ZONE TEMP-2 and AVG
ZONE TEMP.
ZONE TEMP-3 cannot be

connected yet since no I3
3 exists. Right-click the
AVG Block then
View → Details.

Viewing and Modifying the Inserted Logic (Cont’d.)
4 Select IO Modifications.
5 Click + to Add I3.
7 Click OK.
8 Click Close.

Viewing and Modifying the Inserted Logic (Cont’d.)
9 Connect ZONE TEMP-3 to I3.

Modifying a Standard Module
Stuart created the average zone temperature logic using a new Module and
logic Blocks.
He could have opted to modify a Standard Module. He knows that a
Standard Module exists that averages two Inputs. Let’s follow his steps this
time as he modifies an existing Standard Module.
He will add a Sideloop Average Inputs Module
and modify it to add the third zone temperature.
Stuart Price

Modifying a Standard Module (Cont’d.)
1 Right-click Category
2 Select New

Enter Ave to Filter to Sideloop

3
Average Inputs Module.
5 Name the Module.
6 Click Finish.

Rename the Activity Inputs and

7 Outputs by double-clicking them.
ZONE TEMP-3 cannot be

connected yet since no I3
8
exists. Right-click the
AVG Block and
View → Details.

9 Select IO Modifications.
10 Click + to Add I3.
12 Click OK.
13 Click Close.

14 Connect ZONE TEMP-3 to I3.

Key Points
An Activity acts as a container for logic integral to a Module

There is a step-by-step process for creating new Activities
Alternatively, users may opt to modify Standard Modules using a similar step-
by-step process

Discussion
1. What processes might you need to add or modify

Activities for?
2. Can you give an example of a Standard System
you have had to modify so that it met the
specifications of a Sequence of Operations?

Activity - Modifying a Configuration
Day 2 Activity - Modifying a Configuration
Session Overview
This session consists of a lab designed to allow you to use concepts associated with modifying a
configuration to address the issues outlined in the following scenario. You will change programming to
use the average temperature for a specific classroom in a large school.
Scenario
You are being sent out to the Washington Elementary School where construction has changed the
configuration of one of the classrooms. The room is so large that the specifying engineer has asked for
three sensors in the room at strategic locations, and has specified the average of the three temperatures
be the control process variable when the system is occupied, and the lowest temperature of the three
when it is unoccupied.
When you arrive at the school, the Principal sees you and asks if you are the one making the changes for
the new large classroom and asks if the new average temperature for the room can be displayed on their
FX® UI. You tell him that it is possible and you will make the changes.
Estimated Time

Contents
Activity 1 Modify a Configuration

Activity 1: Modifying a Configuration

Getting Started
→ Add Two More Zone Sensors
1. Open VAV Box.caf
2. Add two more SA Bus sensors To add SA Bus zone sensors use the
Define Hardware Wizard
(add Zone NetSensors for Zone 2 and Zone 3).
3. Rename the ZN-T NetSensors as

ZN1-T, ZN2-T, and ZN3-T

→ Find the Average of the Three Sensors

1. Add the averaging module. In the Change the User Name to AVG 3 Zone
Setpoint/Miscellaneous column, add Inputs for this module.
a new Sideloop Average Inputs module.
2. Open the logic view of the The black Output connector is the Default
AVG 3 Zone Inputs module Element. This is the value displayed in the
module during Simulation and while in
Commissioning mode.
3. Rename the Input 1 connector as Renaming is a vital part of program

Zone 1 Input documentation.
4. Rename the Input 2 connector as

Zone 2 Input
5. Add a third Activity Input by expanding You will find the Activity Inputs folder in the
the Activity Inputs folder and dragging an Palette to the left of the logic screen. You
Input (Float) block into the logic. Place it could also Copy and Paste or Duplicate an
below the Zone 2 Input connector. existing Input.

6. Rename this new connection as

Zone 3 Input
7. Right-click the AVG block and

View → Details. Check the box at the
top - IO Modifications. Click the green Plus
sign in the Inputs section to add a new
Input port.
8. Drag a connection line from the

Zone 3 Input connector to the new Input
port on the AVG block
9. Rename the Present Value Output Again, you are helping to document your
Activity Output to Zone Avg Output Value program properly.

10. Select the Select Default Element icon, This value may be already selected. You can
and in the Default Element Selection also right-click anywhere in the logic white
window, select Zone Avg Output Value space and Select Default Element.
11. View → Details for each Activity Input This makes the Inputs and Outputs available
and Output connection and set its BACnet® to read and displayed in the Parameters tab
Exposed attribute to True if the connections are also exposed.
12. Return to Control view after you modify this Click the Control view tab.
logic

→ Connect the New Average Module

1. Select the AVG 3 Zone Inputs module You may need to expand the bottom of the
and select the Connections tab screen.
2. Right-click the Input column header and New Activity Inputs and Outputs are
select Expose Ports. In our example, automatically exposed for connection.
leave all IO ports exposed for connection.

3. Connect the three zone Inputs to their

respective zone sensors by right-clicking
the yellow Input connection and selecting
the appropriate sensor
The average value from the three sensors

needs to go to the same modules as the
original ZN-T.
Do not connect the Zone Avg Output Value

connection right now, as you do not know
where to connect it.

Using Help, answer the following question:
Q1 Can the Activity Inputs and Outputs now be viewed in the Parameters window?

→ Complete the Modification

1. Find out where the original NetSensor Since you will be changing these connections,
(ZN1-T) is currently connected. Select it you need to know what they are now. The
and then select the Connections tab easiest way to remember them is by printing
them.
Use CCT’s Print feature and print

Connections. This creates a PDF file. Keep
this PDF file since you will be referring to it
later.
Notice that this sensor sends its value to many

destinations.
2. Click Save As for this *.caf file before you It is recommended that you rename the file
continue while saving it.
3. View the connections of the first module to In this example, the ZN1-T Output
which the original sensor is currently connections need to be moved to the Output
connected of the AVG 3 Zone Inputs module.

4. Locate the Input connection coming from

Zone Temperature ZN1-T and right-click it.
5. Select Change Connection and connect to

the Output of the AVG 3 Zone Inputs
module. Click OK.
6. Change connections for the remaining It is a good idea to keep going back and
module connections that come from the viewing the original ZN-T connections.
original zone sensor
This is where the original connections PDF file
will be used as a reference to make sure that
you move all the original ZN-T connections to
the Output of the averaging module.

7. Verify that all three zone temperature Use the PDF file to verify that you connected
sensors go into the AVG 3 Zone Inputs everything correctly in the previous steps.
module and that the output of the Average 3
Zone Inputs module goes to the original
module and port connections of ZNT-1

→ Simulate and Verify the Modifications

1. Simulate and test your changed If the application is working properly, you can
connections. Verify that the average delete the PDF file you created earlier for
module is working as expected. reference information.
2. Command the inputs and watch the

average module. When it goes above or
below the current setpoint, confirm that the
controller goes into heating or cooling
mode as expected.
3. Click Save As and save the file with a new

file name

→ Change Order Request for This Program

A change has been requested from your customer with the following specification:
“When the OCC-SCHEDULE Network Input point is set to Occupied or Standby,

the output of the AVG 3 Zone Inputs module will be the average of the three zone temperature inputs.
When it is set to Unoccupied or Not Set, the output will be the lowest value of the three zone sensors. The
customer also wishes to have the averaged value available to be mapped into their graphics.”
You will need to know the Enum set of the OCC-SCHEDULE Network Input point as it passes data to the
Mode Input of the MUX block.

Use the following instructions to help you create logic that matches the specification
1. View the details of the OCC-SCHEDULE

Network Input and record the States Text
(Enumeration Set)
2. View the logic of AVG 3 Zone Inputs
3. In the Palette find the MIN block,

and drag one into the logic view
4. Connect the three zone temps to it This might be a good time to hide the lines by
right-clicking the line and choosing Hide.
Optionally double-click the numbered circles
and label the lines for clarity.
5. Add an Activity Input (Enum) and Rename

it OCCSCHED
6. Change the States Text to match the It should be Occ Schedule.

OCC-Schedule Network Input

7. Add a MUX block from the Palette that is

Float IO, Enum Mode
8. Double-click the MUX, Click Edit, and

change the Mode Input Units to OCC
Schedule
9. Change I1- Modes to Occupied and

Standby and I2 – Modes to Default
10. Click Close and Apply changes
11. Connect OCCSCHED to the Mode of the

MUX, the average to Input 1, and the MIN
block to Input 2.

12. Disconnect the existing connection to the

Output block
13. Connect the Output of the MUX in its place

14. Expose and connect OCCSCHED to the

OCC-SCHEDULE Network Input
15. Save your program
16. Simulate by changing the OCC-SCHEDULE When Occupied or Standby, you should
Network Input value to ensure that the have the average temperature. In any other
correct values are passed out of this module Mode, you should have the lowest sensor
value.
17. Use the Export Module feature to save this
module for future use in other CCT
programs or to send to others for their use

Answers
Q1 Can these Activity Inputs and Outputs now be viewed on the Parameters tab?
Ans. Yes. Make sure you exposed them to BACnet® within the logic.

Sideloops
Day 2 Sideloops
Objectives
After completing this module you should be able to:

Identify the key features associated with sideloops
Describe how the Sideloop Wizard works

Day 2 Sideloops
Key Topics
Key Features
Sideloops
Click the topic to learn about it.

Day 2 Sideloops
Key Features
Sideloops are used to expand the

operational productivity of a controller
beyond what is done in the main
application.
Following are sideloop features:
The Sideloop Wizard uses a
System Selection Wizard interface
Inputs can be either existing or new
points
Outputs must be new points
Click each sideloop in the image to learn about it.

Day 2 Sideloops
Key Features (Cont’d.)
Three types of Sideloop control are available

in the Sideloop Selection Wizard.
Feedback Control:
A Feedback Control Sideloop can do a
simple reset schedule, a PID loop, or a
combination of both
Inputs can be either existing or new points
An example would be
a hot water mixing
valve application
(PID) with an outdoor
air reset schedule of
the hot water setpoint

Day 2 Sideloops
Analog to Binary Control:

A measured variable is compared to a
setpoint to see if it is greater than or
equal to (direct acting) or less than or
equal to (reverse acting)
Inputs can be existing or new points
An example would be to start a coil
circulation pump if the outdoor air
temperature is less than 36º F (2º C)

Day 2 Sideloops
Binary Interlock Control:

A Binary Input is used to send
commands to a Binary Output
with an option for On/Off delays
Inputs could be either existing
or new points
An example would be a Supply
Fan Status (SF-S) Input starts
and stops an Exhaust Fan
(EF-C) Output

Day 2 Sideloops
Create State Selection Interlock:

An Input table and an Output
column are created in the State
Tables so that the action of the
Sideloop can be linked to the
main application
Logic actions will need to be
added in the new row and column
in the State Tables
An example would be that a
Sideloop is only active in the
Occupied mode of the main
program

Day 2 Sideloops
Sideloop Options:
Position Feedback can be added to
controlled devices such as valves and
dampers, but this is not common

Day 2 Sideloops
Let’s see how an Expert uses Sideloops and Sideloop key features.
DEMO

Day 2 Sideloops
Check Your Knowledge
1. A Feedback Control Sideloop:

a. Compares one BI variable to a setpoint
b. Sends commands to a Binary Output
c. Can do simple reset or PI control
d. Can compare more than one BI
and control a BO or AO point

Day 2 Sideloops
Key Points
Sideloops are used to expand a controller’s operational productivity beyond

what is available from the main application System Selection Wizard
The Sideloop Wizard uses a System Selection Wizard interface
Inputs can be either existing or new points
There are three types of Sideloop controls available in the
Sideloop Selection Wizard
The action of Sideloops can be linked to the main application
Although Position Feedback can be added to
controlled devices, it is not common

Activity - Create a Feedback Control Sideloop
Day 2 Activity - Create a Feedback Control Sideloop
Objectives
The Sideloop Wizard in CCT will create a complete control loop, including separate Inputs and Outputs
that are independent of the rest of the application.
In this lab, you will add a Sideloop to control a Variable Speed Drive (VSD) in a simple AHU configuration
and incorporate that VSD control loop into the main application.
Requirement
1. Laptop computer with CCT software
Estimated Time

Review the System Requirements

Job Scenario:
The installed supply fan has a VSD. The speed of the fan is modulated to compensate for
Read loss of airflow as HEPA filters get dirty. Since CCT does not have a System Selection
carefully Wizard option that matches this scenario, select Single Speed as the fan operation so that
the controller will assign a Binary Output to start the VSD. A Sideloop will be created to
control the VSD. Refer to the control drawing and Sequence of Operation below to get
familiar with the system.

In the System Selection Wizard,

select Single Speed Supply Fan.
Air Flow Station and FIL-

VP created by Sideloop
SF-O created by
Sideloop

→ Create a MASD Constant Volume Application, Accepting all the Defaults

1. Launch CCT and create a new application The System Selection Wizard does not have
that controls the system using a an option for an airflow station to control the
Single Speed Supply Fan VSD. Therefore, create the program so that
the fan is a constant volume unit. You will use
a Feedback Control Sideloop (AI controlling
an AO) later to control the VSD.
2. After selecting the Supply Fan type accept

all other defaults. Complete the application
by selecting Next and Finish.
3. Save the file as VAV Air Unit Save your CAF file frequently.

→ Create a Sideloop to Control the Speed of the Fan Based on Velocity Pressure
1. Click Sideloop
2. Select Feedback Control as the Feedback Control is used when the device
Sideloop type being controlled is analog in nature.
3. For the Input Type select Other This loop will be using velocity pressure as its
Input. The other selections are not applicable.
4. Select Number of Inputs as One This loop looks at one process variable to
control the Output.
5. Select Feedback Control (PI) for the
Control Type
6. Select Reverse Acting for the This loop is Reverse Acting. As the velocity
Control Action pressure (process variable) decreases, the
volume of air delivered (Output of the PID)
must increase.
7. Select Proportional Actuator for the The speed drive will be receiving a
Output Type 0 – 10 VDC signal from the controller.

8. Select Create State Selection to The State Table can be used to force the
Interlock this Side Loop signal to the VSD to various values based on
the state the controller is operating in.
This is what your selections should look like:

9. After all selections are done, Click Finish
10. When prompted for a Name, specify SL-SF
SL-SF is an abbreviation for Sideloop Supply

Fan.
The Name of the Sideloop will precede the

object names that are created by the
Sideloop Wizard.
11. After giving the Sideloop a Name, This completes the Sideloop creation.
Click OK
Four new Input and Output points were created that now begin with SL-SF.


Q1 What are the full names of the four new points?
You should also have a new Output Control module.
Q2 What is its Name?

→ Change the Point Names to Match Those in the Control Drawing

1. Right-click SL-SF SL-P and select

Rename
2. Enter the User Name as FIL-VP
3. After changing the name, Click OK
4. Using the procedure above, Rename the These names now match the field
following points: designations on the control drawing above.
SL-SF SL-O as SF-O

SL-SF SLP-SP as SF-Flow-SP

→ Add a Module to Calculate Airflow

1. In the Setpoint/Miscellaneous category,

Right-click the category heading and
select New
2. Type Flow Calculation into the Filter The Flow Calculation module will convert
velocity pressure to airflow.
3. Find the module on the list, and change
Count to 1 Imperial units: CFM (cubic feet/minute)
Metric units: L/s (Liters/second)
4. Click Finish
Since the Analog Input is velocity pressure,
we will convert it to airflow before connecting it
to the Sideloop.
5. View the details of the Flow Calculation
module
6. Change the following values:
Pickup Gain 1
Area 7 sq. ft. (0.7 sq. meters)

7. Set the Elevation attribute to the altitude Make sure that you edit this attribute at your
of the city you are currently in job site locations.
8. Click Apply Elevation examples:
9. Close the Details window Milwaukee is 600 feet

Beijing is 64 meters
Mt. Everest is 29,029 feet

→ Modify the Output Control Loop

The control drawing specifies that the fan output volume (CFM) will be maintained as the HEPA filters get
dirty. We will set the Proportional Output module to CFM before connecting the Sideloop process
variable.
Change the Process ID of SL-SF-PI to represent Airflow with the appropriate Process Range.
1. View the details of the SL-SF PI

Proportional Output module. Edit the
following three values:
Process ID to Airflow
Process Range to 20,000

(9,440 in Metric)
Process Units to cfm (L/s)

When changing the Process ID remember to

change the Units as well, if necessary.
These parameters are the new Process ID

variables that the PID block will use.
2. Apply your changes and Close the

Details window

→ Change the Units for SF-Flow-SP to Represent Airflow with an Appropriate

Setpoint
1. View Details of SF-Flow-SP
2. Click Edit
3. Change the following:
Units to cfm (L/s)

Default Value to 5,000 (2,360 in Metric)
4. Apply your changes and Close the

Details window

→ Change the Connection for FIL-VP to Flow Calculation’s Differential Port

When the Sideloop was created, it automatically connected its Analog Input to the Process Variable
connection of the SL-SF PI Proportional Output module. This needs to be changed so that the Output of
the flow calculation becomes the process variable connection.
1. Select the Connections tab in the

Features panel
2. Select the FIL-VP Input and view its

connections
3. Right-click O1-0.00 in wc and select

Change Connection
We will move the FIL-VP connection from the

SL-SF PI Proportional Output module to the
Flow Calculation module.

4. Select the Flow Calculation module
5. Select Differential Pressure
6. Click OK

→ Connect the Output of the Flow Calculation to the Process Variable of the
SL-SF PI Proportional Output
1. Select the Flow Calculation module and

make sure the Connections tab is
selected
2. Right-click Output FLOW – 0 cfm and

select Make Connection
3. Select SL-SF PI Proportional Output
4. Select Process Variable
5. Click OK
6. Select the State Tables tab The name of the Sideloop Output Control
(Features panel) module is SL-SF PI Proportional Output.

7. Scroll to the right until you see the SL-SF

PI Proportional Output column
8. Scroll down to locate the Loss of Airflow

Sequencing Table

A Normal state for the Loss of Airflow

Sequencing module indicates that the supply
fan is running and the Sideloop needs to be
in operation.
Any other State indicates a Loss of Airflow

and the Sideloop control should be shut
down.
9. Edit each state based on the following:
Normal Control
Low Flow Off
Self Reset Fault Off It should look like this:
Manual Reset Fault Off

By selecting Control for the Normal state,

you ensure that the Sideloop is activated.
With all other states set to Off, the VFD will

ramp down.
10. Move the SL-SF Override Check and With the Loss of Airflow Sequencing
SL-SF PID Tuning Reset tables above table fully specified, neither SL-SF
the Loss of Airflow Sequencing table so Override Check or SL-SF PID Tuning
they can function properly when needed. Reset tables could gain control of the
Sideloop Proportional Output module if
the Output is Overridden or if loop
tuning needs to be reset unless we move
them up in priority.

11. Change the False state of SL-SF Changing the command for the False state of
Override Check to an asterisk (*) the SL-SF Override Check to an asterisk (*)
allows the Loss of Airflow Sequencing
module to gain control of the Sideloop
12. Click Apply to save your changes module when the Output is not Overridden.

→ Define the Appropriate Hardware

1. Use the Define Hardware Wizard and Take all the defaults.
assign all points to a controller
2. Save the program

→ Verify the Program Operation

1. Launch the Simulator Take all the defaults.
2. Right-click SF-S and Command it On
Q3 What is the value of the Flow Calculation module?
Q4 What is the value of the SF-O Output?

3. Command FIL-VP to 0.1” w.c. (25 Pa)
→ Calculate the Flow in the Given Situation

The Imperial equation for airflow is:
4005 √FIL-VP (in ‘wc) × 7 sq ft (area) = CFM
The Metric equation is:

1.3 √FIL-VP (in Pascals) x Area (in sq m) x 1000 = L/s
Q5 What is the calculated flow?

Q6 What is the actual flow (as represented in the object in the program)?
Q7 What is the value of the SF-O output?

→ Simulate a Flow Setpoint of 10,000 cfm (4,720 L/s)

1. Command SF-Flow-SP to 10,000 cfm

(4,720 L/s)
Q8 What is the command to SF-O?

→ Simulate a Supply Fan Status of Off

1. Command SF-S Off
Q9 What is the SL-SF PI Proportional Output module state?
Q10 What is the value of SF-O?

Answers
Q1 What are the full names of the four new points?
Ans. SL-SF SLP-SP, SL-SF Tuning Reset, SL-SF SL-P, and SL-SF SL-O.
Q2 What is its name?
Ans. SL-SF PI Proportional Output.
Q3 What is the value of the Flow Calculation module?
Ans. 0 cfm.
Ans. 100%.
Q5 What is the calculated flow?
Ans. 8865 cfm.
Q6 What is the actual flow?
Ans. 8884 cfm.(this answer will depend on the elevation setting used)

Ans. 0%
Q8 What is the command to SF-O?
Ans. 100%
Q9 What is the SL-SF PI Proportional Output module state?
Ans. Off.
Q10 What is the value of SF-O?
Ans. 0%.

State Tables
Day 2 State Tables
Objectives

View State Tables in a standard program configured by
the System Selection Wizard
Create State Tables for a new program

Day 2 State Tables
Key Topics
View State Tables

State Tables
State Table Details
Edit State Tables
Using State Tables in Commissioning
or Simulation

Day 2 State Tables
Key Features
Incoming states are prioritized

For each state, the appropriate Output Control action is defined
State Generators and modules from other categories become individual
tables (Inputs)
Output Control modules are columns (Outputs)
State Tables are automatically created for standard systems.

Day 2 State Tables
Steps
1. Select the State Tables tab.

2. Double-click the heading of the Features pane to maximize the panel.
3. On the State Tables tab, click View Details.
4. Edit State Tables

Day 2 State Tables
View State Tables
1. Select the State Tables tab

2. Double-click the heading of the Features pane to maximize the panel

Day 2 State Tables
View State Tables (Cont’d.)
State Table State Table

Input from State Output to
Generation Output Control
module module

Day 2 State Tables
State Table Details
On the State Tables tab, click View Details.

Day 2 State Tables
Edit State Tables
Output not
Input not connected
connected
Right-click any column heading
Move Table up / down
Use pulldown
menus for
modes

Day 2 State Tables
Using State Tables in Commissioning or Simulation
State Tables are used to command modules (typically Output Control

modules) on the basis of the state of one or more Inputs
When in the Simulate or Commission mode, the State Table Inputs display
the current state in green

Day 2 State Tables
Key Points
Incoming states are prioritized

For each state, the appropriate Output Control module mode is defined
State Generators and modules from other categories are individual
tables/rows (Inputs)
Output Control modules are columns (Outputs)
State Tables are used to command modules (typically Output Control
modules) on the basis of the state of one or more Inputs
When in Simulate or Commission mode, State Table Inputs
display the current state in green

Data Flow and Saturation Timers
Day 2 Data Flow and Saturation Timers
Objectives

Perform an analysis of CCT modules using Help and features such as viewing
Connections, View Logic, and the Simulator
Explain how PID loops and Saturation Timers work in different modes

Key Topics
Data Flow in CCT

Data Flow and Saturation Timers
Saturation Timers
Click each topic to learn about it

Data Flow in CCT
Generally, data flows from left to right in CCT applications.

Inputs can be connected to and evaluated by modules
in the Setpoint/Miscellaneous category Input
Values
Setpoint/Miscellaneous Outputs flow into
State Generation modules, where modes or states of Setpoint/Miscellaneous
the different subsystems are determined Values
State Generation Outputs flow into the State Tables State Generation
State Tables pass values to Output Control modules State
State Tables
Output Control modules pass signals to the Outputs
Mode
Output Control
Values
Outputs

Data Flow in CCT (Cont’d.)
LV modules allow data to flow from right to left in applications as a way to pass
Output signals back into a program without causing a Circular Redundancy.
For example:
State Generation
State Generation modules often need a lockout
State
value from an Output Control module
State Tables..
Mode
Output Control
Values
LV Block
LV modules can be hidden in CCT.

Output Control modules pass signals to

LV modules, which are then passed back into
State Generation modules
LV modules are always used when the result of
a process is fed back into a process State Generation
State
State Tables..
Mode
Output Control
Values
LV Block

Workflow Process
Identify connections between modules and logic blocks
Connectors: Yellow (Input) / Cyan (Output)
Analyze data flow (use Show Involvement)
Present Value is displayed on the logic view connection lines while in the
Simulator or Commissioning mode

Let’s briefly review an expert demonstration of data flow and connections.
DEMO

Saturation Timers
This example looks at the control of a cooling valve. Every loop has these
Saturation Timer components.
100% 100%
Overridden Normal Timing High High Normal Timing Low Low Overridden
>0%, (Duration (Saturation > 0%, (Duration of (Saturation

Valve = 0% <100% of Saturation Timer <100% Saturation Timer Expired) Valve = 0%
Timer) Expired) Timer)
0%
Click each type of control status to learn more about it.

Saturation Timers
100% 100%

0%
LV Module
Overridden Ctrl Status Ctrl Status
Hybrid Activity Module Mode = NOT Control

Zone Sequencing Module
State Table Mode
0.00%
OFF mode
Constant Valve
Constant Overridden
Ctrl Status
Overridden Click each type of control status
to learn more about it.
Mode = NOT Control - Control Status is Overridden.

This tells the Zone Sequencing module that cooling is disabled and can be switched to control at
any time.

Saturation Timers
100% 100%

0%
LV Module
Normal Ctrl Status Ctrl Status
Hybrid Activity Module Mode = Control

0.01 – 99.9%
State Table Mode Control mode
PV Valve
Ctrl Status Normal

Ctrl Status
Normal Click each type of control status
Mode = Control - Control Status changes to Normal for at least one execution cycle of the PID and
remains as Normal as long as the Output is > 0 and < 100. This tells the Zone Sequencing module
that the system is now in cooling and prevents a immediate state change to any other mode.

Saturation Timers
100% 100%

0%
LV Module
Timing High Ctrl Status Ctrl Status

State Table Mode
100%
Control mode
PV Valve
Ctrl Status Timing High

Ctrl Status
Timing High Click each type of control status
Mode = Control – Control Status changes to Timing High when the PID Output hits 100%. The
Timing High Control Status is not used in most sequences, but it indicates that the valve is fully open
and we are waiting for the Saturation Timer to expire.

Saturation Timers
100% 100%

0%
LV Module
High Ctrl Status Ctrl Status

State Table Mode
100%
Control mode
PV Valve
Ctrl Status High

Ctrl Status
High Click each type of control status
Mode = Control - Control Status changes to High when the PID Output stays at 100% beyond the
duration of the Saturation Timer. This status is not used in standard sequences, but it could be used in
logic to initiate some other action.

Saturation Timers
100% 100%

0%
LV Module
Normal Ctrl Status Ctrl Status

0.01 – 99.9%
State Table Mode Control mode
PV Valve
Ctrl Status Normal

Ctrl Status
Normal Click each type of control status
Mode = Control – Control Status changes back to Normal when the PID Output drops below 100%.

Saturation Timers
100% 100%

0%
LV Module
Timing Low Ctrl Status Ctrl Status

State Table Mode
0.00%
Control mode
PV Valve
Ctrl Status Timing Low

Ctrl Status
Timing Low Click each type of control status
Mode = Control - Control Status changes to Timing Low when the PID Output reaches 0%. This
holds the state as is for the duration of the Saturation Timer.

Saturation Timers
100% 100%

0%
LV Module
Low Ctrl Status Ctrl Status

State Table Mode
0.00%
Control mode
PV Valve
Ctrl Status Low

Ctrl Status
Low Click each type of control status
Mode = Control - Control Status changes to Low when the PID Output is at 0% and the Saturation
Timer has expired. Normally this mode will change after only one execution cycle - Control Status will
almost instantly switch from Low to Overridden.

Saturation Timers
100% 100%

0%
LV Module
Overridden Ctrl Status Ctrl Status
Hybrid Activity Module Mode = NOT Control

State Table Mode
0.00%
Control mode
PV Valve
Ctrl Status Overridden

Ctrl Status
Overridden Click each type of control status
Mode = NOT Control - Control Status is Overridden.

This tells the Zone Sequencing module that cooling is disabled and can be switched to control at any
time.

1. What module is used to return an Output value back into a program as an

Input?
a. Logic View module
b. A status override module
c. Modules operating in Commissioning or
Simulator mode
d. Last Value (LV) modules

Check Your Knowledge (Cont’d.)
2. When does Control Status change to High?

a. When the Output is: > 0 and < 100
b. When the PID Output reaches 0%
c. When the PID Output drops below
100% to close the valve
d. When the PID Output stays at
100% beyond the duration
of the Saturation Timer

Key Points
Usually data flows from left to right in CCT applications

Last Value (LV) modules are used when the result of a process is fed back
into a process
You can analyze data flow using Show Involvement
Present Values are displayed on logic connection lines when the Simulator is
running or you are in Commissioning mode
Saturation Timers are used in every process

Get ready to Actively Participate

Discussion

Logic Blocks
Day 2 Logic Blocks
Objectives

Explain the utility of common logic blocks
Use the block Palette to locate and use specific logic blocks
Implement Activity Input and Activity Output connectors
Given five example blocks, explain how logic was employed

Day 2 Logic Blocks
Key Topics
Logic Diagrams
Logic Blocks
Logic Blocks Palette Categories
Selected Logic Blocks

Day 2 Logic Blocks
Logic Diagrams
Sample Logic Diagram
Logic Block Palette

Day 2 Logic Blocks
Logic Blocks Palette Categories
Click the palette items to know more about them.

Day 2 Logic Blocks
Logic Blocks Palette Categories (Cont’d.)
Objects to Bring Data into a Module

Day 2 Logic Blocks
Result from Module Logic

Day 2 Logic Blocks
Contains AND, OR, NOT, XOR,

and Reliability Modules

Day 2 Logic Blocks
Reset Schedules, Totalization

Blocks, and Expressions

Day 2 Logic Blocks
Greater Than, Less Than, Equal

Not Equal, Etc.

Day 2 Logic Blocks
Used when a Fixed Value is needed

Day 2 Logic Blocks
Embedding an Activity or Hybrid

Activity

Day 2 Logic Blocks
Blocks Used in PID Loop Control

Day 2 Logic Blocks
Various Mathematical Functions


Day 2 Logic Blocks
Staged Control Based on Load

or Demand

Day 2 Logic Blocks
Blocks used for Calculating

Humidity, Dew Point, and Enthalpy

Day 2 Logic Blocks
Multiplexer, Command Hierarchy,

Click the palette items to know more about them. and Converters

Day 2 Logic Blocks
Staged Control Based on Fixed

Limits

Day 2 Logic Blocks
High, Low, Average, and Statistics

Day 2 Logic Blocks
Timers, Last Values, Rate Limiter,

Click the palette items to know more about them. and Latch

Day 2 Logic Blocks
Selected Logic Blocks
Adding Ports to blocks

Ports on most blocks can be cloned to add Activity Inputs and Outputs.
Expose Ports, View Details and Rename as appropriate
Right-click and select Clone Ports
Use the Clone Ports window to select which Ports are to be cloned
Connections are made automatically

Day 2 Logic Blocks
Selected Logic Blocks (Cont’d.)
Selected Blocks
Boolean—Supervisor
Status
Calculation—Span
Selection—MUX
Calculation—EWMA
Timing—Timer
Click the Blocks to know more about them.

Day 2 Logic Blocks
Boolean— Calculation—
Calculation—Span Selection—MUX Timing—Timer
Supervisor Status EWMA
Boolean—Supervisor Status
If the controller is mapped to a supervisory device and communication is valid,
this block’s Output = True
If communication is lost, the block Output = False
Can be used for switching to local control in a network failure

Day 2 Logic Blocks
Calculation—Span
The Span block creates a linear Output based on a specific value on the Input
In this example, the hot water setpoint will ramp from 190º F to 130º F as the outdoor
air temperature changes from 0º F through 60º F.

Day 2 Logic Blocks
Selection—MUX
The MUX (Multiplexer) blocks are selected based on the data type of the
MODE and Inputs and Outputs
For example, when switching the setpoint of discharge air temperature from a fixed value
to a resetting value with a schedule, you would use a MUX with an Enum Mode
(schedules are enumerated data) and Float I/O (setpoints are floating data).

Day 2 Logic Blocks
Selection—MUX
Right-click a MUX block and select View → Details to determine which Input
is sent through for a given value on the Mode connection
In this example, Input 2 passes through when the schedule is Occupied, and
Input 1 is passed for all other Mode states.

Day 2 Logic Blocks
Calculation—EWMA
Exponential Weighted Moving Average (EWMA) calculates a difference
between two Inputs over a time period, with the most recent changes weighted
as the most important.
Here is an example with changes over a five minute period. Notice how the EWMA
Output changes when no Input changes occur. Eventually, the EWMA will equal the
difference between the Inputs if no change occurs.
1 Minute
3 Minutes
Click the Blocks to know 5 Minutes

more about them.

Day 2 Logic Blocks
Timing—Timer
1. Timer blocks are configured for the function they perform. There are nine
different Timer types
2. The Duration of a Timer can be exposed and brought out to the network
3. Rename Timers to
indicate their Duration 3
1 2
Click the Blocks to know

more about them.

Day 2 Logic Blocks
Key Points
A logic block is a component used to construct the control logic of a module,

based on the functionality needed for the application
The control block Palette contains folders which contain function-specific
groups of logic blocks
The Launch Wizard simplifies your search for a block or group of blocks to
add to your logic
Help is available for any block by Selecting it and pressing F1

Day 2 Logic Blocks
1. The Activity Inputs Folder contains how many different types of Input
Blocks?
a. 1
b. 2
c. 3
d. 4

Day 2 Logic Blocks
2. Which of the following blocks would you expect to find in the Boolean
folder?
a. MUX blocks
b. And and Or blocks
c. Add, Subtract and Multiply blocks
d. Activity Input blocks

Day 2 Logic Blocks
3. Which one of the following blocks creates a linear Output based on

specific Input values?
a. EWMA (Exponential Weighted Moving Average)
b. MUX (Multiplexer)
c. Timer
d. Span

Day 2 Logic Blocks
Discussion

Timers
Day 2 Timers
Objectives

Explain the function of Timers
Configure Timers
Understand a Timer’s function in an application

Day 2 Timers
Key Topics
Timers Overview
Timers
Timer Functions
Breakout Session

Day 2 Timers
Timers Overview
Examine this logic. Notice the Enum-to-Boolean and Boolean-to-Enum

translator blocks.
Boolean Logic
Boolean-to-Enum translator
Enum-to-Boolean Converts False/True (Boolean)
translator to Off/On (Enum)
Converts Off/On
(Enum) to False/True
(Boolean)
Activity Output
Enum Type
Activity Input
Enum Type

Day 2 Timers
Timers Overview (Cont'd.)
In many applications, you will have Timers that function as Minimum On,
Off Delay, Pulse, etc.
Multiple timing functions are available from the Timer block
For example:
When a fan is switched On, wait before a pump starts
Be sure that a pump is Off for a certain period of time before starting it again,
preventing short cycling
To see how a Timer is
configured, select it and
right-click View → Details

Day 2 Timers
Timer Functions
To understand the details of a Timer block, use Help.

Timer types are:
On Delay
On Delay With Memory
Off Delay
Minimum On
Minimum Off
Pulse
Cancelable Pulse
Retriggerable
Pulse
Free Running

Day 2 Timers
Timer Functions (Cont'd.)
The type of Timer is displayed by default as the name of the Timer block and
can be edited
Add the duration of the timer to the name.
Reset is an optional Input. To use it:
1. Right-click the Timer
2. Select Expose Ports For Connection
Anytime Reset is True, the Timer Output
is False.
(Reset has no effect when the setup is
Minimum On or Minimum Off.)

Day 2 Timers
Timer Functions (Cont'd.)
Time Remaining indicates the time until expiration. The Time Remaining
Update Interval must be greater than 0 seconds for this to function.
Timer blocks only allow Boolean Input and Output connections. CCT will
automatically add Enum-Boolean and Boolean-Enum translators if the
connections to and from a Timer are 2 state Enum.

Day 2 Timers
Breakout Session
What Timer block types would you expect to be used in this sequence? Draw an
overview of the logic on paper.
Spend a few minutes in a breakout session and consider how to implement this
logic
Chiller Control Sequence:

The operator will select the chiller via the CH1-START command. Once selected, the
DDC controller will start the associated chilled water pump (CHP1-C) and two minutes
later start the condenser water pump (CWP1-C). Once there is proof of flow from both
pumps (CHP1-S & CWP1-S), the controller will enable the Chiller (CH1-C) to start.
When the CH1-START command is off, the respective chiller will stop. Two minutes
later the condenser water pump will stop and two minutes after that the chilled water
pump will stop.

Day 2 Timers
Breakout Session (Cont'd.)
The logic below shows one possible solution

Day 2 Timers
Key Points
In many programs you will have Timers that function as Minimum On,
Off Delay, Pulse, etc. and multiple timing functions are available in the
Timer block
The functions within a Timer include:
On Delay Retriggerable Pulse
On Delay With Memory Free Running
Off Delay, Minimum On Pulse
Minimum Off Cancelable Pulse
To understand the details of the Timer block use Help.

Day 2 Timers
Chat
1. Describe two different scenarios you

might expect to use a Timer?

MUX
Day 2 MUX
Objectives

Describe the purpose of the MUX block
Analyze the configuration of a MUX block

Day 2 MUX
Key Topics
MUX Block Description

MUX
MUX Block Configuration

Day 2 MUX
MUX Block Description
The MUX block is used often and serves as a switch when there are multiple
Inputs and only one Output.
Here we see the MUX block has:

Float data type for the Input and Output connections
Enum data type for the Mode connection

Day 2 MUX
MUX Block Configuration
Double-click the MUX block to view details
When in Simulation or Commissioning modes, double-clicking the MUX only

allows a change in Default Values.

Day 2 MUX
MUX Block Configuration (Cont’d.)
Customize the
attributes by
selecting the Edit
button
Check the IO
Modifications box
to add or delete
Inputs
When adding Inputs choose how many you want to add then rename them using the
Edit feature.

Day 2 MUX
MUX Block Configuration (Cont’d.)
Click Edit, then Click each Input button to select a Mode or Modes that will
cause the MUX to pass that Input’s data
The Enum Set used by this MUX block is OCC Override

When the Mode connection is Occupied or Bypass, Input 1 is selected and its value
is switched out
Otherwise, Input 2 is selected and passed along. Default is selected instead of
checking the remaining options

Day 2 MUX
Key Points
The MUX block is used often and serves as a switch where there are multiple
Inputs and only one Output
To configure a MUX, double-click the block. When in Simulation or
Commissioning mode, double-clicking the MUX only allows a change to
Default Values.
When adding Inputs, choose how many you want to add then rename them
using the Edit feature.

Day 2 MUX
Discussion

PRAC and PID
Day 2 PRAC and PID
Objectives

Describe feedback loops
Explain event and state-based logic

Day 2 PRAC and PID
Key Topics
Feedback Loops
PRAC and PID
State-Based Control

Day 2 PRAC and PID
Key Topics (Cont’d.)
Feedback Loops Feedback Loops in State-based

Control Basics
Feedback Control Algorithms
PID
PID Inputs
Presetting Values of the PID Block
MSC Pre-Processor
PID Block
Loop Tuning Terminology
Control of VAV Actuators

Day 2 PRAC and PID
Feedback Loops
Feedback Loops in State-Based Control Basics

The MS/TP family of controllers has two primary control elements:
Feedback Loops
State-Based Logic

Day 2 PRAC and PID
Feedback Loops (Cont’d.)
All standard systems using feedback loops in a controller invoke PRAC+,

a predictive and adaptive control system. Under normal conditions, loops
self-tune to gain precise control.
Nearly all loops can self-tune with a couple of exceptions:
Severe Lag or Variable Efficiency
Chiller Optimization Programs

Day 2 PRAC and PID
Thomas has been working with CCT for a while. He is developing a baseline
understanding of the feedback control algorithms.
He knows that feedback control is based on a patented Proportional Integral
Derivative (PID) algorithm — Pattern Recognition Adaptive Control (PRAC+),
and that Proportional Band and Integral Time values
are automatically calculated by PRAC+.
Thomas Bruce

Day 2 PRAC and PID
He decides to learn more by asking an expert.
DEMO

Day 2 PRAC and PID
Thomas discovers that:

PID logic with PRAC+ always contains:
PID block
PID Pre-Processor block
Sometimes contains a Lead Compensator block

Day 2 PRAC and PID
He needs to understand the relationship between these PID components.

He will need to discover the following
PID:
Self-tuning processes adjust PB and IT parameters to find the most effective
values to control the system
Pre-Processor:
Starts the PID tuning with specific values. This only occurs at the time of
download and reset
References the Process ID
Lead Compensator:
Connected where oversized or nonlinear devices might be applied
Can be manually connected in any system where nonlinear devices
might affect control

Day 2 PRAC and PID
Process Variables (Inputs) have a Process ID

Process ID Unit Type Time Constant Dead Time Process Range
Airflow Flow 30 3 n/a
CHWS-T Mixing Temperature 500 50 20
CWS-T Temperature 600 60 15
DA-T Temperature 200 20 30
Duct Static Pressure 30 3 375
Pump Diff P Pressure 30 3 140000
RA-H RH 1200 120 50
ZN-T Temperature 900 30 15
The Process ID identifies the type of loop and subsequent starting values for
the Pre-Processor connected to the PID
There is not a Process ID for every possible type of HVAC application, but CCT picks
something as close as possible. You can select a Custom Process ID, but be very
careful with this option as you will have to populate starting values. To find the latest
Process ID table, use Help and search for “Appendix.”

Day 2 PRAC and PID
Thomas further discovers that:

The PID Pre-Processor values vary with the Process ID
The PID Pre-Processor pre-conditions inputs on the PID block

Day 2 PRAC and PID
The Multistage Controller (MSC) Pre-Processor pre-conditions the inputs to

a PID controlling Staged Outputs

Day 2 PRAC and PID
The Proportional Variable Deadzone Controller (PVDC) is used with a VAV

box damper command:
It dynamically estimates a dead band (deadzone) based on turbulence (noise)
measured by the pressure sensor
Calculates an actual pulse width and desired
position for the actuator stepper motor PVDC
Outputs 0-100% to a Position Adjust Output Startup Value
(PAO) or Analog Output object Min Pulse Width
Flow Present Value
Maximum Flow
Effective Stroke Time Saturation Status
Smooth Factor
Flow Setpoint

Day 2 PRAC and PID
Pattern Recognition Adaptive Control Plus (PRAC+)

A self-tuning method to calculate:
Effective Proportional Band
Effective Integral Time
Minimum Tune Band

Minimum Tune Band is the amount of error (difference between Setpoint and
Process Variable) below which no PRAC+ tuning takes place.

Day 2 PRAC and PID
Interval is the time between PID calculations

Process Range is the Process Variable change expected as the PID Output
throttles between 0% and 100%
Time Constant is the time required for the Process Variable to reach 63% of
its Process Range with a 100% change in the PID Output
Dead Time is the time required for the Process Variable to begin a change
based on a step change in the PID Output

Day 2 PRAC and PID
This example DA-T 63 %

shows the DA-T DA-T feedback Process Range
value changing of DA-T
change
after the heating
valve PID Output
changed from 0%
to 100%
Dead Time
DAT-SP Time Constant DAT-SP achieved
changed @time=t1
@time=t0

Day 2 PRAC and PID
600 PRAC turned on

Static Pressure (Pa)
500 Process Output
400
300
200 Setpoint
0 2 4 6 8 10 12
Time (minutes)
300 Pascals = 1.2” wc

Day 2 PRAC and PID
1. What is PRAC+?
a. A self-tuning method to calculate
Effective Proportional Band
and Effective Integral Time
b. A process used to speed up
control responses
c. The time required for a Process
Variable to begin to change
based on a step change in the
Output
d. The time required for a Process
Variable to reach 63% of its
Process Range for a 100%
change in the Output

Day 2 PRAC and PID
Key Topics
Control Implementation
State-Based Control
State-Based Control
Basic Data Flow
Example
Putting It All Together

Overrides
Tuning Reset

Day 2 PRAC and PID
Now let’s watch as Thomas works with State-Based Control

Control is based on States, e.g., Heating – Satisfied – Cooling
State-based control includes:
Finite State Machine (FSM): Logic block that
contains code to produce a specific state
State Generator: Logic module that determines
a specific state
Using FSMs eliminates state conflicts
(e.g., cooling called for when heating is enabled)
Thomas Bruce

Day 2 PRAC and PID
State
Setpoint/Misc Generation
Output
{Process (decides which State
Control
Variable Input} state is active) Selection
{PID}
{Finite State
Machine}
Room Temp Heating Heating = Control Heating = 0-100%

Cooling = Off Cooling = 0%
Heating and Cooling

NetStat Inputs
Outputs

Day 2 PRAC and PID
Heating PID at 0.0% Zone temperature greater

for Saturation Time than cooling setpoint
Satisfied
Heating Cooling
Minimum
Modulate Modulate
flow;
heating cooling
no heating
Zone temperature less Cooling PID at 0.0%

than heating setpoint for Saturation Time
Transition events consider both time and value comparisons.

Day 2 PRAC and PID
State selection is input on the Mode connection: Off (no humidity control) or
H Control (humidity control)
The Command Hierarchy block outputs the desired state
If commanded to H Control, humidifier PID logic will control the humidification
loop to add moisture. Otherwise, the Off layer of logic disables humidification

Day 2 PRAC and PID
Overriding an output can cause PRAC+ to self-tune inaccurately. To avoid this

scenario, Miscellaneous inputs are created for all Outputs that are under PID
control and modules are created to determine override status.

Day 2 PRAC and PID
The Override Check modules monitor if an Output is in Override, and if so,

places the associated Output Control in Hold mode
Hold mode in an Output Control passes the value of the Output (4)
unchanged when not Overridden, and the Override value (7) if it is
Overridden.

Day 2 PRAC and PID
Lastly, Thomas works with Tuning-Reset and learns that:

If a controller is placed into a situation where it is mechanically unable to
control, the values from PRAC+ can be miscalculated. This will cause a very
long cycle before re-tuning correctly once the problem is fixed.
This sometimes happens in new construction. For example, VAV controllers
attempting to heat when there is no hot water available.
After the mechanical issue is resolved, toggling the Tuning-Reset Network
Input places all PRAC+ loops at their Process ID Default Values so that they
can tune properly in normal conditions

Day 2 PRAC and PID
The Tuning-Reset Network Input is a Boolean value. When it is commanded

from False to True, all PIDs are restarted with initial tuning parameters.
It is connected to the PID Tuning Reset module that:
Watches for the Tuning-Reset transition
Commands the State Table to place the Mode
of all Output Control modules with PIDs into Hold mode
Sets up a 20-second period for the reset to occur

Day 2 PRAC and PID
Key Points
All systems using feedback loops in the controller invoke PRAC+, a predictive
and adaptive control system
Feedback control is based on patented algorithms — Pattern Recognition
Adaptive Control (PRAC+), and Proportional Band and Integral Time
values are automatically calculated by PRAC+
PID logic with PRAC+ always contains a PID block, PID Pre-Processor block
and sometimes a Lead Compensator block
State-based control includes Finite State Machines (FSM) and
State Generators
Overriding an Output can cause a PRAC+ PID to mistune
The Tuning-Reset Network Input is used to place
all PRAC+ loops back at their Process ID Default Values

Activity – Custom Logic
Day 2 Custom Logic
Descripción general Objetivos

Esta sesión consiste en un laboratorio que demostrará la creación de una lógica
personalizada básica para controlar el equipo auxiliar.
Metas
Al final del laboratorio, puedes:
Comprender las conexiones entre los bloques lógicos CCT.
Requisito
Computadora con software CCT.
Tiempo estimado: este ejercicio tarda unos 40 minutos en completarse.

Day 2 Custom Logic
→ Crea una nueva lógica personalizada.

Como hacer Consejos y notas útiles:
1. Launch CCT
2. Seleccione File → New
3. En System Name pon el nombre

LABCUSTOM1
4. En System Type seleccione Custom

Aplications

Day 2 Custom Logic

5. En System Selection Wizard seleccione

los puntos de General Point Monitoring:
Zone Items:
➢ Zone Temperature Sensor (AI)
6. Quantity = 2 Sensors (2 AI’s)
7. Clickea en Next
8. Clickea en Finish

Day 2 Custom Logic

10. Seleccione Sideloop para crear una

nueva lógica

Day 2 Custom Logic

11. Crearemos una lógica personalizada para

controlar la válvula de agua enfriada.
12. Clickea en Finish

Day 2 Custom Logic
→ Crea una nueva lógica personalizada

14. En Sideloop pon el nombre FANCOIL

Day 2 Custom Logic

Como fazer Consejos y notas útiles:
14. Haga clic derecho en

Setpoint/Miscellaneous y seleccione
New…
15. Crear un Modulo Activity llamado Average
16. Haga Clic en View Logic en el modulo

Average

Day 2 Custom Logic

Usa el filtro para encontrar los bloques más

17. Usando Pallete, cree una lógica para rápidamente
calcular la temperatura promedio.
18. Cambiar el nombre de los bloques a:
➢ Input (Float) – Temp1

➢ Input (Float) – Temp2
➢ Output (Float) - TempAverage

Day 2 Custom Logic

14. Conecte las Inputs a las Temperaturas
15. Conecte Output en FANCOIL PI

Proportional Output v51 al puerto Process
Variable

Day 2 Custom Logic

17. Crear un Output para el control del

Ventilador (SF-C) con la señal mantenida
de 24VAC Maintained.
18. Cree un State Table basada en Network

Input SLINT-S, cuando se active para
encender el, ventilador SF-C.
19. Conecte el Mode a State Table

Day 2 Custom Logic

20. Haga clic en Simulate, y pruebe la lógica.

Commissioning & Standard Programming Using CCT

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Commissioning & Standard Programming Using CCT

Cargado por

Copyright:

Formatos disponibles

Commissioning & Standard Programming using CCT

Lesson – Introduction to Controllers Activity - Modifying a Configuration

Lesson – Troubleshooting Software

Activity - Data Flow and Viewing Activity - Create a Feedback Control

Lesson – Modifying Inputs and Outputs

Activity - Input/Output Commissioning

Lesson Lab Resources

Lesson – State Tables Activity – Custom Logic

Lesson – Data Flow and Saturation Timers

Lesson - Logic Blocks

Lesson - PRAC and PID

Lesson Lab Resources

Tier 4 Valves and

Excellence in Training Online Product Literature

Que es un BAS (Sistema de Automatización de Edificios)?

Colección de componentes individuales de control y software que trabajan

Excellence in Training Online Product Literature

Arquitectura del Sistema Facility Explorer

Distribuido Escalable Seguro Abierto

Excellence in Training Online Product Literature

At the end of this session, you will be able to:

Excellence in Training Online Product Literature

Click each topic to learn about it.

Excellence in Training Online Product Literature

Visão geral – Quais são os controladores de equipamentos de campo?

A family of FX Equipment Controllers that operate with FX Supervisor:

Excellence in Training Online Product Literature

FX Family Components—Field Controllers and Sensors

Programmable Programmable Controllers Programmable

Programmable Controllers Field Equipment

Excellence in Training Online Product Literature

PCV16 (32-bit) PCV19 (32-bit)

Provides improved accuracy, especially in low- Local Alarm

Point capacity can be expanded by adding

Excellence in Training Online Product Literature

I/O Modules are BACnet® or SA Bus (on N2

Excellence in Training Online Product Literature

Similar to PCG, except: Similar to PCG, except:

Excellence in Training Online Product Literature

16 MB flash memory and 8 MB SDRAM 16 MB flash memory and 8 MB SDRAM

N2 or BACnet® MS/TP N2 or BACnet® MS/TP

Excellence in Training Online Product Literature

BACnet® Master-Slave/Token-Passing (MS/TP) protocol communication

Excellence in Training Online Product Literature

At-a-glance system status

Excellence in Training Online Product Literature

Mobile Access Portal Gateway (MAP)

Provides a wireless mobile user interface to all field devices

Excellence in Training Online Product Literature

Allows commissioning and servicing of the controllers over a wireless

Excellence in Training Online Product Literature

Handheld VAV Balancing Tool

Convenient, Portable VAV Balancing Tool

Excellence in Training Online Product Literature

Handheld VAV Balancing Tool (Cont'd.)

Navigation is menu-based using the dial and push buttons

Excellence in Training Online Product Literature

ZigBee® Wireless USB Dongle

Excellence in Training Online Product Literature

FX Family Components—Wireless Field Bus System

Wireless Field Bus system is not available with N2 networks.

Excellence in Training Online Product Literature

PCG Family Overview