03-Celeris_Users_Guide.pdf

Celeris® User's Guide

© Copyright 2008 Phoenix Controls

Phoenix Controls, Theris, Traccel, Celeris, Zone Presence Sensor, and ZPS are registered trademarks of Honeywell International, Inc. MicroServer and MacroServer are trade-marks of Honeywell International, Inc. LonMaker is a registered trademark of Echelon Corporation.

Phoenix Controls products are covered by one or more of the following U.S. patents:

5,385,505 5,545,086 6,457,437 and other patents pending.

The material in this document is for information purposes only and is subject to change without notice. Phoenix Controls assumes no responsibility for any errors or for conse-quential damages that may result from the use or misrepresentation of any of the mate-rial in this publication.

Celeris® 1 User’s Guide Table of Contents

Section 1 Introduction

Using Phoenix Controls Configuration Plug-in . . . . . . . . . . . . . . . . . . . .1-1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Database Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Room-level Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Phoenix Controls Configuration Plug-in Menus . . . . . . . . . . . . . . . 1-8 Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14 Subsystem-level Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 Room-level Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Using the Phoenix Controls Configuration Plug-in . . . . . . . . . . . . . . . .1-19 Building-Level Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23 Room-Level Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24 Configuration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

Section 2 Device Configuration

Device Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Device I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Alarm Enable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Section 3 Valve Configuration

Valve Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Clamp Selector Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Emergency Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Valve I/O Configuration Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Section 4 Occupancy Configuration

Occupancy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Occupancy I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . 4-4

Section 5 Emergency Configuration

Emergency Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 i MKT-0125 MPC-1912 Rev. 02/13

Section 6 Humidity Configuration

Humidity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Humidification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Dehumidification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Humidity I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Section 7 Temperature Configuration

Temperature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Primary Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Auxiliary Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Temperature Offset Lever . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22 Multiple Device Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29

Advanced Temperature Control (ATC) . . . . . . . . . . . . . . . . . . . . . . . . . 7-37

Section 8 I/O Configuration

I/O Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 I/O Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Section 9 Custom PID Configuration

Custom PID Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Input/Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Section 10 MAV/MAV_ATC Configuration

MAV/MAV_ATC Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Booster(s) Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Section 11 GEX Configuration

GEX Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Booster Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4 I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Section 12 Hood Main Configuration

Hood Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 ii Rev. 02/13 MKT-0125 MPC-1912

Hood Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8 Subsystem Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 Two-State Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15

Section 13 SccLabCmpt Configuration

SccLabCmpt Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5 Flow Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5 Subsystem Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8 Additional Control Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18 SccLabCmpt Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . 13-22 Indoor Air Quality (IAQ) control . . . . . . . . . . . . . . . . . . . . . . . . . 13-23

Section 14 SccLabFull Configuration

SccLabFull Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-1 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4 Flow Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5 Subsystem Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7 Additional Control Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-13 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18

Thermal Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-23 Temp Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-24 Flow Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27

SccLabFull Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-29 Indoor Air Quality (IAQ) control . . . . . . . . . . . . . . . . . . . . . . . . . 14-29

Section 15 SccZoneVav Configuration

SccZoneVav Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-1 Zone Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Tracking Pair Supply Zone Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-3 System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4 Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5 Flow Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5 Boosters Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

Standalone (or Return) Zone Type . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-8 iii

Office Supply Zone Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9 Additional Control Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-20 SccZoneVav Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . 15-24 Indoor Air Quality (IAQ) control. . . . . . . . . . . . . . . . . . . . . . . . . . 15-25

Section 16 Booster Configuration

Section 17 Bypass Configuration

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2 Booster(s) Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Section 18 Progressive Offset Control (POC)

Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 Progressive Offset Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3 Temperature Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4 Additional Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4 Diversity Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5 Local Flow Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28 POC Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29 POC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31

Section 19 Lab Compact Configuration

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3 Temperature Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4 Flow Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4 Subsystem Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16

Section 20 Lab Full Configuration

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3 Other Set Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3 Constant Volume Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4 Subsystem Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6 Additional Control Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-11 Output Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16 iv

Thermal Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-21 Temp Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-22 Flow Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25

Section 21 Standalone Configuration

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 Booster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4 I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Section 22 Tracking Pair Configuration

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3 Subsystem Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6 I/O Configuration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7

Section 23 TpVav (Legacy Traccel) Configuration

Alarm Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

Valve Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2 Valve Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3 Emergency Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4

Space Comfort Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-5 Primary Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-7 Auxiliary Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11

I/O Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-14 I/O Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14

Temperature I/O Configuration Settings . . . . . . . . . . . . . . . . . . . . . . 23-20 Temperature Sensor Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21 Temperature Set Point Lever. . . . . . . . . . . . . . . . . . . . . . . . . . . 23-22 Output Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-23 Additional Flow Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-26 Additional Control Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-28 Output Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-30

Occupancy I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-32 Occupancy I/O Configuration Settings. . . . . . . . . . . . . . . . . . . . 23-32

Emergency Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-35 Local Alarm Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-37 Local Alarm Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-39

Flow Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-40 Offset Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-41 Ventilation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-41 Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-42 Flow Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-42 v

Index vi

Celeris User’s Guide Section 1 Introduction

Using Phoenix Controls Configuration Plug-in

This section will help you become familiar with a custom tool used to configure Phoenix Controls LonWorks-based controllers: the Phoenix Controls Configuration Plug-in. In addition, you will commission devices directly from your laptop computer.

We will be using the Phoenix Controls Configuration Plug-in to define the actual CFMs, the voltage ranges on valves and actuators, temperature and humidity settings, etc. We will also use another plug-in, known as Point Viewer, to view the points for each valve.

General Description The Phoenix Controls Configuration Plug-in is an applet developed by Phoenix Controls that runs on top of LonMaker, or as a standalone application, and is used to configure Celeris2 Valve Controllers. It allows users to navigate to devices on the network and select a specific function on a specific valve in order to set up the necessary configuration properties. The Phoenix Controls Configuration Plug--in also enforces application “rules” which are specific to Celeris room control, such as total room minimum and maximum supply clamps. The new settings can then be downloaded to, or uploaded from, a particular Lon Valve Controller (LVC) in the network.

The Phoenix Controls Configuration Plug-in is written in Visual Basic (VB)

6.0. The main Multiple Document Interface (MDI) Form contains all other forms. As such, the MDI is divided into a Toolbar and a menu section at the top, a Form (or data) view on the right hand side, two tree views on the left, and Tabs for switching between Form View and Data View.

1-1

Introduction Using Phoenix Controls Configuration Plug-in Figure 1-1. Phoenix Controls Configuration Plug-in Multiple Document Interface

1. Menu and toolbar

2. Upper or building-level tree

3. Lower or room-level tree

4. Form View or Data View window

5. Form and Data View tabs

6. Status bar

The upper tree (item 2, Figure 1-1) contains the building-level hierarchy as read from the LON Database, while the lower tree (item 3, Figure 1-1) contains the room-level hierarchy. All room-level subsystems in the upper tree are represented by leaves (branches containing no children), so that there is no duplicate navigation available (lower tree paths are not directly accessible from the upper tree, and vice-versa).

When an upper leaf is clicked, the Phoenix Controls Configuration Plug-in builds the lower tree room level, showing any controllers and their enabled functional objects. By clicking on any functional object, the Form View then builds the Form (item 4, Figure 1-1) based on the class of the functional object selected. Figure 1-2 and Figure 1-3 show all the functional objects, and all the Forms that can be built, as well as which valve type supports those forms.

5 6 1-2

Celeris User’s Guide Figure 1-2. Form Names, Icons, and Valve Types

Figure 1-3. New Valve Types

The “Data View” Tab along the bottom edge of the screen (item 5, Figure 1-1) toggles the display to show a table of all the configuration parameters of the selected functional object, along with their current values.

Form

C lass N am es

Valve Types

Icon

Booster/Track

Bypass

GexRet Hood

LabCmpct

LabFull

MAV

MAV_ATC

POC

StandAlone

Tp ExhMain

Tp Exh Bstr

Tp Sup Main

Tp Sup Bstr

Traccel TpVav

Form

C lass N am es

AddFlowCfg AdvTemperature BstrCfg BypassCfg CusPID DeviceCmpct Device Emergency GexRetCfg HoodCfg Humidity

IO

LabCmpctCfg LabFullCfg MavMainCfg Occupancy POCZoneCfg Temperature TpZoneCfg TpVav Alarms TpVav Flow Control TpVav IO TpVav Space Comfort TpVav Valve Valve

Form

C lass N am es

New C2.5 Valve Types

Icon

SccLabFull

SccLabCmpct

SccZoneVav

Form

C lass N am es

SccDevice SccI/O SccValve ** SccZoneVav's includes Cascade Control SccEmergency SccOccupancy SccTemperature SccHumidity SccLabFullCfg ** Includes IAQ and Local Zone Emergency SccLabCmpctCfg ** Includes IAQ and Local Zone Emergency SccZoneVavCfg ** Includes IAQ and Local Zone Emergency SBRC (Traccel) ** Includes Device, Valve, Occupancy, Temperature Emergency, Humidity, I/O SBHC (Theris) ** Includes Device, Valve, Occupancy, Temperature Emergency, Humidity, I/O

Form

C lass N am es 1-3

Figure 1-4. Example Data View

The “Status Bar” along the bottom of the screen (Item 6, Figure 4-1) provides a quick reference of run-time information such as; number of devices that have changed, Auto-Save and, ONNET status

Database Rules Automated rules help with some of the necessary room-level and subsystem-level calculations. The subsystem rules run automatically when you click on a functional object that needs those rules. The room-level rules run whenever you click on a room in the upper tree.

Room-level rules also take effect if you choose to force the rules to run manually by clicking the Run Rules NOW button on the Toolbar at the top of the screen.

1-4

Celeris User’s Guide The table below shows a list of database subsystem architecture rules which must be observed in LonMaker in order for the Phoenix Controls Configuration Plug-in trees and rules to work properly:

Database Subsystem Architecture Rules

Rule # Description Details

1 Only one main (non-BstrTrk) valve allowed per subsystem

EXCEPTION: TpSupM, TPExhM, TpSupB, TpExhB Must share a subsystem

Only the following valves can have boosters: here are their max per subsystem:

Bypass Max Bstrs = 8

GexRet Max Bstrs = 8

Hood Max Bstrs = 2

Hood Max Trks = 3

MAV Max Bstrs = 2

SccZoneVav Max Bstrs = 3

A subsystem that contains a Valve (LVC device) CANNOT also contain other subsystems, because Valve (LVC device) level is always the lowest level for any tree branch.

Illegal Example:

Only ONE(1) of the following Zone- Control types allowed per room (the subsystem above device level)

LabFull

LabCmpct

POC

SccLabFull (direct replacement for LabFull)

SccLabCmpct (direct replacement for LabCmpc)

(TPExhM is not included- can have multiple TPs as long as each is in its own subsystem)

# of MAV Subsystems allowed in a room is limited by the room’s zone control valve:

LabFull: 4

SccLabFull: 4

LabCmpct: 1

SccLabCmpct: 1

POC: 1

6 The following valve types can have up to 1 Bypass subsystem in its room:

LabFull

LabCmpct

POC

SccLabFull

SccLabCmpct

The following valve types can have up to 1 of either GEX or return type subsystem in its room:

LabFull

LabCmpct

POC

1-5

Room-level Examples

The following figures illustrate room-level configurations for the Phoenix Controls Configuration Plug-in trees and rules.

The following valve types can have one of each GEX and return type subsystem in its room:

SccLabFull

SccLabCmpct

# of hood Subsystems allowed in a room is limited by the room’s zone control valve:

LabFull: 10

SccLabFull: 10

LabCmpct: 7

SccLabCmpct: 7

10 SccLabFull is a direct replacement for LabFull in any application.

*In addition, SccLabFull Itself can be configured as a MAV, GEX, Bypass, or Return (not just a supply or exhaust like LabFull)

11 SccLabCmpct is a Direct Replacement for LabCmpct In ANY application

**In addition, SccLabCmpct Itself can be configured as a MAV, GEX, Bypass, or Return (not just a supply or exhaust like LabCmpct)

12 SccZoneVav is limited to the following applications:

As a Supply main in a 2-4 node TP system (all other nodes are BstrTracks)

As A Supply main in a 4 node TP System, where one of the BstrTrks is a tracking return

As a Return Valve in the Return subsystem of a SccLabCmpct-controlled or SccLabFull-controlled room.

As an Office Supply or Exhaust which received no flow command only gives flow feedback. (In addition, Multiple SccZoneVavs can be found as Office Supplies or Exhausts in a room)

When a SccLabFull or SccLabCmpct room has a return subsystem, the return valve MUST be a SccZoneVav Valve (NOT a GexRet valve).

The reverse is also true. In a Celeris LabFull or LabCmpct room with a return subsystem, the return valve MUST be a GexRet (NOT a SccZoneVav valve).

Database Subsystem Architecture Rules

Rule # Description Details 1-6

Celeris User’s Guide Figure 1-5. Database where SccZoneVav is Office Supply and BioSafety Cabinet

Figure 1-6. Legacy Tracking Pair Room with Boosters 1-7

Figure 1-7. Illegal Room with Valve and Subsystems

Phoenix Controls Configuration Plug-in Menus

The menu bar along the top of the screen lets you set up the user interface for personal preferences and carry out a number of administrative, database and device functions

The Phoenix Controls Configuration Plug-in main menu bar contains selections for File, Database, Transfer, Utilities, Reports, and Help.

Figure 1-8. Phoenix Controls Configuration Plug-in main menu bar

Each menu contains a variety of commands, which are shown in the table below.

1-8

Celeris User’s Guide Menu Selections

Menu Item Commands Functions

File

Exit

Closes the Phoenix Controls Configuration Plug-in and exits to the Microsoft Visio application (If running on top of LonMaker).

• If any configuration properties have been changed you will be prompted to save to the database and/or download changes to the affected devices

• NOTE: If you are OFFNET, you will not be prompted to download to any configured devices

• If you have the Auto-Save feature turned on you may not be prompted to save to the database

Database

Save to database

Enabled when a change has been made. Stores the Phoenix Controls Configuration Plug-in’s entire database settings to the LON database as configuration parameters, always in SI units.

Those value can be seen using Lon Browser.

• If there are changes to configuration properties, clicking on Database >Save to database, or pressing and holding the Ctrl key while pressing the S key will save any changes to the database.

• NOTE: If there are no changes to be saved or the user is logged in as Read-Only, the menu item will be grayed out.

Transfer

• Download to controller

• Upload from controller

“Download to controller” pops up the download window, which lets you select which controllers should receive new configuration parameters.

• You can also opt to get feedback, which means the transaction will be verified for each valve. The software looks for error messages when finished. The results for each valve are shown separately.

“Upload from controller” pops up the upload window, which lets you select which controllers will send their configuration parameters. The results for each valve are shown separately.

Utilities

• “Select Units

• “Plug-in Settings

• “User Manager Choosing “Select Units” gives you the choice of “US Units” or “SI Units”.

• Use “US Units” to globally change all units in the GUI to US measurements with their proper conversions. When a unit has more than one US option, it can be configured by selecting the “Plugin Settings” menu choice.

• Use “SI Units” to globally change all units in the GUI to SI measurements with their proper conversions. When a unit has more than one SI option, it can be configured by selecting the “Plugin Settings” menu choice.

1-9

Utilities (cont.)

“Plug-in Settings

Choosing “Plug-in Settings” opens a popup window that lets you further refine units of measure for:

• Flow in liters/second (l/s) or meters cubed per hour (m3/h)

• Pressure in inches of water column (In of H2O) or pounds per square inch (psi)

• “Plug-in Settings” also lets you turn on the log file, which always defaults to “Off” when starting the application. Logging provides a more detailed trail of what the application has been requested to do, and is usually not recommend due to its effect on resources.

For this reason, a warning will always flash whenever this option is selected, or if the option is turn on and the window is opened.

• AutoSave—Turns the AutoSave function ON or OFF.

• Selecting ON tells the Phoenix Controls

Configuration Plug-in to save changes to the database any time you navigate away from device where configuration properties have been edited. This will occur as a background task and you will not be prompted if you want to save changes.

• Selecting OFF tells the Phoenix Controls Configuration Plug-in to prompt the user before saving any changes. AutoSave ON is highly recommended.

Menu Selections (Continued)

Menu Item Commands Functions 1-10

Celeris User’s Guide Utilities (cont.)

“User Manager”

Provides a popup window that lets you:

Add User—Clicking on this button changes the lower part of the window so you can:

• Enter a new User Name

• User name may be any alphanumeric character A-Z, a-z, 0-

• User name must be at least 1 character and may be up to 16 characters in length

• Enter a Description of that user

• Enter a Password for the user

• Confirm Password by retyping it

• Password should be at least 1 character in length and may be up to 255 characters in length/

• Password may be any keyboard character

NOTE: User name and password are case sensitive.

“User Manager” also lets you set up accounts in four different levels--Super User, Field Service, Read Only User, and Account Disabled. Only accounts at or below the current log-in level can be created or edited.

• Read Only—this user level may view configuration settings but may not edit them, save to the database, or upload or download configuration properties to a device.

• Field Service—this user has access to all the common and practical configuration properties, may save to the database and may upload and download to devices. A Field Service user may add, remove, or disable any Field Service or Read-Only user.

• Super User—this user has all the permissions of a Field Service user plus has the ability to add, disable and/or remove any user.

• Account Disabled—this user account is still valid, but will not allow the user to log in. User name and password remain unchanged until it is activated again. This is a way to create a user account for an occasional user, but prohibit access for security purposes when access is not required or desired.

NOTE: It is recommended that you set up a Field Service level and Read Only level account for the local facilities or maintenance personnel that is different than your log in. This way unless someone with Field Service level or above deletes or disables your password, you have a means to log into the Phoenix Controls Configuration Plug-in.

Menu Selections (Continued)

Menu Item Commands Functions 1-11

User Manager (contnued)

Delete User—Clicking on this button lets you delete the selected user. A new window will ask you to confirm you wish to delete the user account.

The User Manager tool lets you edit the description, change the user’s password, or change the users security level.

• Edit any field and buttons appear that allow you to:

• Cancel Changes

• Apply Changes

WARNING: Once a user has been deleted, the user cannot be recovered.

Reports

Offers “Configuration Report” on the sub-menu, which provides a popup window.

This menu lets you generate a Configuration Report for all, or selected controllers on the network.

Generates a CSV (Comma Separated Value) or an XML report based on a checklist of valves, of all configuration parameters and their current settings. You can specify where the report is saved, and whether or not to overwrite older reports. This report can be thought of as a “snapshot” of all controller settings.

• You may browse folders on the computer or removable hard drive to select the location where the configuration reports will be saved.

• Check the selection box in front of each controller to generate a report.

• Un-check the selection box in front of the controller to skip that controller when reports are generated

• You can click on the” Check/Uncheck All” boxes to select or deselect all devices

• Checking the “Overwrite old reports without prompt” box simply means any duplicate reports in the selected folder will be overwritten

• Select either the “XML” button or the “CSV” button to generate the type of report output you want.

• Click on the “Create Report Files” button

• An individual file will be generated for each device selected and placed in the folder selected.

• XML Report format is recommended and is viewable as a well-organized report using Microsoft Internet Explorer.

Menu Selections (Continued)

Menu Item Commands Functions 1-12

Celeris User’s Guide Toolbar Buttons Some of the buttons on the Toolbar offer the same functions as their menu counterparts. Other buttons offer unique functions. All Toolbar button capabilities are described below.

Figure 1-9. Phoenix Controls Configuration Plug-in Toolbar Buttons

From left to right, the buttons are:

• Save Changes,

• Refresh (Re-load) the Entire Database,

• Download to the controller(s),

• Upload from the controller(s),

• Show Current Rule Activity,

• Run Rules NOW, and

• Create a Configuration Report.

Clicking on the Save Changes button stores the Phoenix Controls Configuration Plug-in’s entire database settings to the LON database as configuration parameters, always in SI units. Those values can be seen using Lon Browser.

• This button is normally grayed out. It is only active if you have made changes to one or more configuration properties in the configuration

Help

Offers “Configuration Help” and “About Plug-in” on the sub-menu.

“Configuration Help” opens a Help Index window, with links to the various Help screens.

“About Plug-in” gives the current Phoenix Controls Configuration Plug-in version number.

Menu Selections (Continued)

Menu Item Commands Functions

Save Changes Refresh Database

Download Upload

Show Rule Details Which Have Run

Run Rules NOW

Create Configuration Report 1-13 window or if rules have run that have changed properties of devices in the background.

• If Auto-Save is turned ON, the Phoenix Controls Configuration Plug-in will save changes to the database every time you navigate from one subsystem to another or if you close or exit from the Phoenix Controls Configuration Plug--in. Turning Auto-Save ON is highly recommended.

• If Auto-Save is turned OFF, and configuration properties have changed the button will turn blue and you must manually save the changes to the database

Clicking on the Refresh (Re-load) the Entire Database button re-loads the entire Lon Database. This button is useful when you make changes to the structure of the database (i.e. Valves, subsystems, rooms, floors added or removed). Using this button means that you do not have to shutdown and restart the Phoenix Controls Configuration Plug--in.

CAUTION: During Refresh, any information in the Phoenix Controls Con-figuration Plug-in will be replaced by that of the database.

Clicking on the Download to the controller(s) button pops up the download window. The download window lets you select which controllers will receive download configuration parameters. You can also opt to get feedback, which means have the transaction verified for each valve, looking for error messages when finished. The results for each valve are shown separately.

Clicking on the Upload from the controller(s) button pops up the upload window. The upload window lets you select which controllers’ configuration parameters will be retrieved. The results for each valve are shown separately.

Clicking on the Show Current Rule Activity button pops up a window which displays current rule activity. Here you can choose to clear the list, close the window, or even leave it open (it refreshes by itself as rules are run). Rules are listed by a brief description, the valve the data comes from, the valve that requested the rule be run, and the location of the subsystem in the database hierarchy.

NOTE: The Toolbar button will flash Blue whenever new rules have been run.

Clicking the button will reset (clear) the flash. If you only want to clear the flashing without having to open the rules summary window, right click on the flashing blue button.

Clicking on the Run Rules NOW button runs both the subsystem and room-level rules on whichever room is selected in the upper (building-level) tree. If the selection is not a room (i.e. not a tree leaf), a warning will result, as only one room can be run at a time.

NOTE: Clicking this button causes exactly the same action as clicking on a room in the upper tree.

1-14

Rules

Celeris User’s Guide Clicking on the Create a Configuration Report button generates an XML report based on a checklist of valves, of all configuration parameters and their current settings. You can specify where the report is saved, and whether or not to overwrite older reports. This report can be thought of as a “snapshot” of all LVC settings. It can then be viewed with Microsoft Internet Explorer.

Rules

There are two types of rules: subsystem-level and room-level. In addition to these rules, there are many checks that the software performs when opening a Form to make sure that it is displaying valid data. These additional checks are in place if the database was last saved with bad data (either corrupted, or if you made manual changes using Lon Browser and made configuration mistakes…).

If the software DOES discover contradicting or bad data, it will make changes to correct the data. This can be thought of as the “third set” of rules.

Subsystem-level Rules

Subsystem-level rules run at the lowest subsystems on the lower tree, represented by the pink boxes farthest from the root. There are between 1 and 9 valves under any of these subsystems (1 valve + up to 8 boosters).

Subsystem-level rules can be triggered three ways:

1. Opening a Form (clicking on the lower tree branch) that contains subsystem rules

• Only Forms represented by the icon may have subsystem rules. The table below shows which forms contain subsystem rules.

2. Opening a new room (clicking on any end node, or leaf, of the top tree)

• When the lower tree is built for any room, each subsystem has its rules executed, followed by the room-level rules.

3. Clicking on the Run Rules NOW button.

• Clicking on this button will run all subsystem-level and then room-level rules on whichever room is currently selected in the upper tree. If a non-room node is selected (i.e. one with children), this button will give a failure message.

Subsystem Form Rules

Only forms represented by the icon have subsystem rules.

Forms and Their Subsystem-Level Rules

Form Name Displayed As Rule Name Description

AddFlowCfg _StandAlone STNDLN-1 Getting Number Of Subsystem Boosters

STNDLN-2 Getting Booster Names

STNDLN-3 Getting Booster Min / Max Clamps 1-15

STNDLN-4 Calculating Total Min/Max Clamps

BypassCfg _Bypass BYPASS-1 Getting Number Of Subsystem Boosters

BYPASS-2 Getting Booster Names

BYPASS-3 Getting Booster Min / Max Clamps

BYPASS-4 Calculating Total Min/Max Clamps

BYPASS-5 Setting Lab Controller Type

GexRetCfg _GeneralExh/Ret GEXRET-1 Getting Number Of Subsystem Boosters

GEXRET-2 Getting Booster Names

GEXRET-3 Getting Booster Min / Max Clamps

GEXRET-4 Calculating Total Min/Max Clamps

GEXRET-5 Setting Lab Controller Type

HoodCfg _Hood HOOD-1 Getting Number Of Subsystem Boosters

HOOD-2 Getting Number Of Subsystem Tracks

HOOD-3 Getting Booster Names

HOOD-4 Getting Track Names

HOOD-5 Getting Bstr Min/Max Clamps

HOOD-6 Getting Track Min/Max Clamps

MavMainCfg _MAV MAV-1 Getting Subsystem Number

MAV-2 Getting Number Of Subsystem Boosters

MAV-3 Getting Booster Names

MAV-4 Getting Bstr Min/Max Clamps

MAV-5 Calculating Total Min/Max Clamps

MAV-6 Setting Lab Controller Type

TpZoneCfg _TrackingPair TP-1 Getting TpSupplyMain Min/Max Clamps

TP-2 Getting TpExhaustBstr Min/Max Clamps

TP-3 Getting TpSupplyBstr Min/Max Clamps

Forms and Their Subsystem-Level Rules

Form Name Displayed As Rule Name Description 1-16

Celeris User’s Guide Room-level Rules Room-level rules run for whichever room is currently selected (highlighted on the upper tree, and represented by the entire lower tree). On the upper tree, a room is defined as a node with no children (a leaf). There may be as many as 20 valves under any one room, as defined by the Phoenix Controls Celeris 2 performance guidelines for building databases.

As with subsystem-level rules, room-level rules can be triggered three ways:

1. Opening a Form (clicking on the lower tree branch) that requires room-level rules.

• Only Forms represented by the icon may have room-level rules.

The table below shows which Forms contain room-level rules.

2. Opening a new room (clicking on any end node, or leaf, of the top tree)

• When the lower tree is built for any room, each subsystem has its rules executed, followed by the room-level rules.

3. Clicking on the Run Rules NOW button.

• Clicking on this button will run all subsystem-level and then room-level rules on whichever room is currently selected in the upper tree.

This button will instead give a failure message if a non-room node is selected (i.e. one with children)

TP-4 Setting Exhaust Allocations based on number of Boosters

TP-5 Setting Supply Allocations based on number of Boosters

SccLabFullCfg _SccLabFull SccLabFull-1 Setting own Valve Min/Max Clamps

SccLabCmptCfg _SccLabCmpt SccLabCmpt-1 Setting own Valve Min/Max Clamps

SccZoneVavCfg _SccZoneVav SccZoneVav-1 Number of Subsystem Boosters

SccZoneVav-2 Setting Booster Names

SccZoneVav-3 Setting Booster Clamps

SccZoneVav-4 Setting Own Clamps

SccZoneVav-5 Checking if SccZoneVav is functioning as a Return

SccZoneVav-5 Setting Total Clamps

Forms and Their Subsystem-Level Rules

Form Name Displayed As Rule Name Description 1-17

Using the Phoenix Controls Configuration Plug-in Using the Phoenix Controls Configuration Plug-in

1. Launch the Phoenix Controls Configuration Plug-in and log into the tool.

Method A: As A Standalone Application

• Double-click the “Launch Configuration Plug-in” File. You can then select the database to open. Then, log in as below.

Method B: As A LonMaker Plug-in

• Using the right mouse button, click on any blank spot on the screen

Forms and Their Room-level Rules

Form Name Displayed As Rule Name Description

LabCmpctCfg _LabCompact LABCMPCT-1 Setting MAV Subsystem Total Clamps

LABCMPCT-2 Setting GEX Subsystem Total Clamps

LABCMPCT-3 Setting BYPASS Subsystem Total Clamps

LabFullCfg _LabFull LABFULL-1 Setting MAV Subsystem Total Clamps

LABFULL-2 Setting GEX Subsystem Total Clamps

LABFULL-3 Setting BYPASS Subsystem Total Clamps

LABFULL-4 Checking MAV Subsystem Numbers

POCZoneCfg _POC POC-1 Setting MAV Subsystem Total Clamps

POC-2 Setting GEX Subsystem Total Clamps

POC-3 Setting BYPASS Subsystem Total Clamps

SccLabCmptCfg _SccLabCompact SccLabCmpt-1 Setting MAV Subsystem Total Clamps

SccLabCmpt-2 Setting GEX Subsystem Total Clamps

SccLabCmpt-3 Setting BYPASS Subsystem Total Clamps

SccLabCmpt-4 Setting Return Subsystem Total Clamps

SccLabFullCfg _SccLabFull SccLabFull-1 Setting MAV Subsystem Total Clamps

SccLabFull-2 Setting GEX Subsystem Total Clamps

SccLabFull-3 Setting BYPASS Subsystem Total Clamps

SccLabFull-4 Checking MAV Subsystem Numbers

SccLabFull-5 Setting Return Subsystem Total Clamps 1-18

Celeris User’s Guide and select Plug-ins from the pop-up menu.

• The LonMaker Plug-ins dialog box will appear on your screen. In the Select Plug-In list,

• Select Phoenix Controls Configuration Plug-in and click OK

OR

• Double-click on Phoenix Controls Configuration Plug-in.

NOTE: If the Phoenix Controls Configuration Plug-in is not listed see Registering Plug-ins

• A message will appear on your screen briefly as LonMaker opens the Phoenix Controls Configuration Plug-in. When it is finished, you'll see a Sign On box that asks for a User Name and Password.

Plug-ins menu command

Configure (Phoenix Controls Configuration Plug-in tool)

Select Plug-in list 1-19

For security purposes the Phoenix Controls Configuration Plug-in requires an authenticated User Name and Password

2. If this is your first time launching the Phoenix Controls Configuration Plug-in, you must set up a user account. Enter the User Name and Password as follows:

• In the User Name box, type First_Time_Only. Skip the Password box.

NOTE: Be sure to use an underscore character (_) between words. Also, User Names and Passwords are case-sensitive.

• Click the OK button, and the following message will appear on your screen.

• Click the OK button to change your user name and password

• The Sign On box will reappear on your screen.

• Enter a User Name.

• User Name may be any alphanumeric character A-Z, a-z, 0-9.

• User Name must be at least 1 character and may be up to 16 characters in length.

• Enter a Password.

• Password should be at least 1 character in length and may be up to 255 characters in length.

• Password may be any keyboard character.

Sign On box 1-20

Celeris User’s Guide

• User Name and Password are case sensitive.

NOTE: For security reasons, the letters, numbers, and other characters you use in your password are displayed as asterisks in the Sign Onbox.

NOTE: As a general rule it is best to create a User Name and Password for yourself that is consistent across all sites you or your organization service and is easy for you to remember. There will be opportunities later for you to set up user accounts for owner personnel.

• Click the OK button. A welcome message will briefly appear to confirm that your User Name and Password were changed successfully.

3. If you had previously created a user account simply enter your User Name and Password when prompted and click OK.

1-21

• The Phoenix Controls Configuration Plug-in navigation screen will open.

• The screen is divided into 6 main sections

• The Menu Bar at the top—Drop-down lists allow you to perform various database and device operations and set user preferences for the Phoenix Controls Configuration Plug-in.

• The Icon Toolbar just below it—provides quick access to frequently used features such as Save, Upload, Download, Run Rules, etc

• The upper, Building-level Navigation Tree—lets you navigate through the building or floor-level network to locate the desired room.

• The lower, Room-level Navigation Tree—provides a list of devices found in the room-level network and lets you select any function of any device to view or edit the associated configuration properties.

• The Configuration Window—provides the user interface for viewing or editing control function configuration properties. This view will change based on the device type and function selected in the Room-level Navigation Tree.

• The Status Bar along the bottom of the screen—provides a quick reference of run-time information such as the number of devices changes, Auto-Save and ONNET status.

Device configuration area

Building- Level Navigation Tree

Room- Level Navigation Tree 1-22

Celeris User’s Guide As you click on each device in the Room-level Navigation Tree, a different configuration screen will display in the Configuration Window.

Building-Level Navigation Tree

From this screen you can scroll through the Building Level Navigation tree until you find the desired room.

Spaces are grouped based on the subsystem structure established in the LON Database. Therefore, if you created a subsystem for each floor, or a subsystem for each type of space, that grouping will be reflected in the Building Level Navigation window 1-23

Click on any + sign or double-click on the subsystem name to expand the spaces or groups of spaces under that subsystem.

NOTE: If a vertical scroll bar appears, you may need to click on the up/down scroll arrows to display the room of interest.

Room-Level Navigation Tree

When you click on a specific room, the Phoenix Controls Configuration Plug-in will read the LON Database and:

• Determine what devices make up that particular pressurization space.

• Gather all the configuration properties of devices in the selected space.

• Run application and business rules to insure devices are properly grouped and configuration properties are appropriate based on the number and type of devices.

Vertical Scroll Bar 1-24

Celeris User’s Guide Once the rules have run, the devices in the selected space will be displayed in the lower room-level navigation list.

Selected Space

Devices in Selected Space

Control Function Objects

Room-level Subsystem

Room-level Device 1-25

Clicking on each room-level subsystem exposes the room-Level devices and control function objects associated with each device.

Clicking on a Control Function Object populates the Configuration Window.

Configuration Window

The Configuration Window presents context-specific configuration data for each of the 21 device types (GEX, MAV, Hood, LabCmpt, etc…).

When you select a particular device by double-clicking on it (or clicking on the plus sign (+) in front of the name, the Configuration Window displays the functions enabled for that device. The functions displayed are determined by the functions supported by that device type and what functions are enabled in the Device Function Object.

Selected Control Function Object

Configuration Data

Device Function Objects and Their Icons

Icon Function Object Icon Function Object

Device Temperature

Valve Advanced Temperature

I/O Humidity

Flow/Zone Occupancy

Traccel Alarms Emergency

Traccel Flow Control Custom PID 1-26

Celeris User’s Guide The Device Function is always first, followed by the Valve Function.

The General Control Functions follow, based on the order in which they were enabled.

The I/O and Flow/Zone Functions will always be last in the list.

Clicking on the function object branch populates the Configuration Window with the associated configuration properties.

Most of the screens are relatively…