n30 supervisory controller user's manualcgproducts.johnsoncontrols.com/met_pdf/6892010.pdfn30...

N30 Supervisory Controller User’s Manual

© Johnson Controls, Inc. www.johnsoncontrols.com

1

Table of Contents


Chapter 1 Using this Manual ............................................................. 1-1

Introduction.................................................................................................. 1-1

Key Concepts............................................................................................... 1-2 Manual Organization .................................................................................................. 1-2 Manual Conventions .................................................................................................. 1-2 Chapter Organization ................................................................................................. 1-3 Related Publications .................................................................................................. 1-4 Questions or Comments about this Manual ............................................................... 1-4

Chapter 2 Introduction to the N30 Supervisory Controller ............. 2-1

Introduction.................................................................................................. 2-1

Key Concepts............................................................................................... 2-2 N30 Supervisory Controller ........................................................................................ 2-2 N30 Capabilities ......................................................................................................... 2-2 BAS Components....................................................................................................... 2-2 Supported Application Specific Controllers (ASCs) ................................................... 2-3 Interfaces to the N30.................................................................................................. 2-4 M-Series Workstation................................................................................................. 2-4 M-Tool ........................................................................................................................ 2-5 VT100 Terminal.......................................................................................................... 2-5 VT100 Terminal Emulator .......................................................................................... 2-6 Local Display Terminal (LDT)..................................................................................... 2-6 Printer......................................................................................................................... 2-6 N2 Bus ....................................................................................................................... 2-6 Ethernet Bus .............................................................................................................. 2-6 BACnet....................................................................................................................... 2-6 10BaseT, Twisted Pair Cable..................................................................................... 2-6

Chapter 3 Getting Started .................................................................. 3-1

Introduction.................................................................................................. 3-1

Key Concepts............................................................................................... 3-3 N30 Task Overview.................................................................................................... 3-3 Objects ....................................................................................................................... 3-4


2

Object Names ............................................................................................................ 3-4 Containers.................................................................................................................. 3-4 Groups ....................................................................................................................... 3-4 Flash Memory............................................................................................................. 3-4 Warm Start ................................................................................................................. 3-5 Site Manager.............................................................................................................. 3-5 Rebind Site................................................................................................................. 3-5 Containers and Objects.............................................................................................. 3-6 N30 Screen Layout on VT100 Terminal or VT100 Terminal Emulator....................... 3-8 Browsing .................................................................................................................... 3-9 Functions Available in the VT100............................................................................. 3-10

Procedure Overview .................................................................................. 3-12

Detailed Procedures .................................................................................. 3-14 Logging On to an N30 .............................................................................................. 3-14 Checking the Firmware Version Level of an N30..................................................... 3-15 Setting the Date and Time ....................................................................................... 3-17 Editing the Attributes of an N30 ............................................................................... 3-18 Browsing an N30 Database with a VT100................................................................ 3-20 Adding Objects with a VT100................................................................................... 3-22 Editing Objects with a VT100 ................................................................................... 3-23 Commanding Objects............................................................................................... 3-24 Displaying a Summary ............................................................................................. 3-25 Printing a Summary.................................................................................................. 3-27 Changing an IP Address .......................................................................................... 3-28 Rebinding a Site....................................................................................................... 3-30 Changing Device Names.......................................................................................... 3-30 Archiving the Current Database ............................................................................... 3-30

Chapter 4 Working with Operator Objects ....................................... 4-1

Introduction.................................................................................................. 4-1

Key Concepts............................................................................................... 4-2 Operator Object.......................................................................................................... 4-2 Administrator .............................................................................................................. 4-2 Site Manager Device.................................................................................................. 4-2 Copy Holder Device ................................................................................................... 4-2 Global Objects............................................................................................................ 4-3 Redundant Objects .................................................................................................... 4-3 User Access Feature.................................................................................................. 4-3 Guidelines for Defining User Access.......................................................................... 4-5 Attributes .................................................................................................................... 4-8 Operator Object Example......................................................................................... 4-10


Detailed Procedures .................................................................................. 4-13 Adding an Operator Object ...................................................................................... 4-13

Table of Contents

3

Editing an Operator Object....................................................................................... 4-15 Commanding an Operator Object ............................................................................ 4-15 Changing Any Operator Password........................................................................... 4-16 Changing the ADMIN Password............................................................................... 4-16 Deleting an Operator Object .................................................................................... 4-17

Chapter 5 Working with VT100 Objects............................................ 5-1

Introduction.................................................................................................. 5-1

Key Concepts............................................................................................... 5-2 VT100 Object ............................................................................................................. 5-2 Attributes .................................................................................................................... 5-2

Procedure Overview .................................................................................... 5-5

Detailed Procedures .................................................................................... 5-6 Editing a VT100 Object .............................................................................................. 5-6

Chapter 6 Working with Group Objects............................................ 6-1

Introduction.................................................................................................. 6-1

Key Concepts............................................................................................... 6-2 Group Object .............................................................................................................. 6-2 Site Group .................................................................................................................. 6-2 User Group................................................................................................................. 6-3 Attributes .................................................................................................................... 6-4


Detailed Procedures .................................................................................... 6-6 Adding a Group Object............................................................................................... 6-6 Editing a Group Object ............................................................................................... 6-8 Adding Object References to a Group Object ............................................................ 6-9 Deleting Object References from a Group Object...................................................... 6-9 Deleting a Group Object........................................................................................... 6-10 Creating a Site Group .............................................................................................. 6-11 Creating a User Group ............................................................................................. 6-12

Chapter 7 Working with Schedule Objects ...................................... 7-1

Introduction.................................................................................................. 7-1

Key Concepts............................................................................................... 7-2 Schedule Object......................................................................................................... 7-2 Attributes .................................................................................................................... 7-2 Dates..........................................................................................................................7-4 Wildcard Date Fields .................................................................................................. 7-4


4

Time Changes............................................................................................................ 7-6


Detailed Procedures .................................................................................... 7-9 Creating a New Schedule .......................................................................................... 7-9 Editing Schedule Objects ......................................................................................... 7-16 Commanding Schedule Objects............................................................................... 7-23 Deleting Schedule Objects....................................................................................... 7-23

Chapter 8 Working with Calendar Objects ....................................... 8-1

Introduction.................................................................................................. 8-1

Key Concepts............................................................................................... 8-2 Calendar Object ......................................................................................................... 8-2 Attributes .................................................................................................................... 8-2 Wildcard Date Fields .................................................................................................. 8-3


Detailed Procedures .................................................................................... 8-7 Adding a Calendar Object .......................................................................................... 8-7 Editing a Calendar Object .......................................................................................... 8-9 Adding Date List Entries to a Calendar Object........................................................... 8-9 Deleting Date List Entries from a Calendar Object................................................... 8-10 Commanding a Calendar Object .............................................................................. 8-11 Deleting a Calendar Object ...................................................................................... 8-11

Chapter 9 Working with Optimal Start Objects................................ 9-1

Introduction.................................................................................................. 9-1

Key Concepts............................................................................................... 9-2 Optimal Start Object ................................................................................................... 9-2 Optimal Start Equation ............................................................................................... 9-2 Optimal Start Example ............................................................................................... 9-3 Optimal Stop .............................................................................................................. 9-3 Adaptation .................................................................................................................. 9-4 Attributes .................................................................................................................... 9-4


Detailed Procedures .................................................................................. 9-10 Adding an Optimal Start Object................................................................................ 9-10 Editing an Optimal Start Object ................................................................................ 9-13 Commanding an Optimal Start Object...................................................................... 9-13 Deleting an Optimal Start Object.............................................................................. 9-14

Chapter 10 Working with Temporary Occupancy Objects.............. 10-1

Table of Contents

5

Introduction................................................................................................ 10-1

Key Concepts............................................................................................. 10-2 Temporary Occupancy Object Operation................................................................. 10-2 Attributes .................................................................................................................. 10-2


Detailed Procedures .................................................................................. 10-5 Adding a Temporary Occupancy Object .................................................................. 10-5 Editing a Temporary Occupancy Object................................................................... 10-6 Commanding a Temporary Occupancy Object ........................................................ 10-6 Deleting a Temporary Occupancy Object ................................................................ 10-6

Chapter 11 Working with Printer Objects......................................... 11-1

Introduction................................................................................................ 11-1

Key Concepts............................................................................................. 11-2 Printer Object ........................................................................................................... 11-2 Attributes .................................................................................................................. 11-2


Detailed Procedures .................................................................................. 11-7 Adding a Printer Object ............................................................................................ 11-7 Editing a Printer Object .......................................................................................... 11-10 Commanding a Printer Object ................................................................................ 11-10 Deleting a Printer Object ........................................................................................ 11-11

Chapter 12 Working with Modem Configuration Objects ............... 12-1

Introduction................................................................................................ 12-1

Key Concepts............................................................................................. 12-2 Modem Configuration Object.................................................................................... 12-2 Attributes .................................................................................................................. 12-2


Detailed Procedures .................................................................................. 12-5 Adding a Modem Configuration Object .................................................................... 12-5 Editing a Modem Configuration Object..................................................................... 12-7 Deleting a Modem Configuration Object .................................................................. 12-7

Chapter 13 Working with Global Data Sharing Objects .................. 13-1

Introduction................................................................................................ 13-1


6

Key Concepts............................................................................................. 13-2 Global Data Sharing Object ..................................................................................... 13-2 Attributes .................................................................................................................. 13-2


Detailed Procedures .................................................................................. 13-4 Adding a Global Data Sharing Object ...................................................................... 13-4 Editing a Global Data Sharing Object ...................................................................... 13-7 Adding Slaves to the Slaves List .............................................................................. 13-7 Deleting Slaves from the Slaves List........................................................................ 13-8 Commanding a Global Data Sharing Object ............................................................ 13-8 Deleting a Global Data Sharing Object .................................................................... 13-9

Chapter 14 Working with Interlock Objects ..................................... 14-1

Introduction................................................................................................ 14-1

Key Concepts............................................................................................. 14-2 Interlock Object ........................................................................................................ 14-2 Attributes .................................................................................................................. 14-2 Example ................................................................................................................... 14-4


Detailed Procedures .................................................................................. 14-9 Adding an Interlock Object ....................................................................................... 14-9 Editing an Interlock Object ..................................................................................... 14-14 Adding Sources to an Interlock Object................................................................... 14-14 Deleting Sources from an Interlock Object............................................................. 14-15 Adding Action Table Entries to an Interlock Object................................................ 14-15 Deleting Action Table Entries from an Interlock Object.......................................... 14-16 Commanding an Interlock Object ........................................................................... 14-17 Deleting an Interlock Object ................................................................................... 14-17

Chapter 15 Working with Signal Select Objects .............................. 15-1

Introduction................................................................................................ 15-1

Key Concepts............................................................................................. 15-2 Signal Select ............................................................................................................ 15-2 Analog Signal Select ................................................................................................ 15-2 Binary Signal Select ................................................................................................. 15-2 Attributes .................................................................................................................. 15-3


Detailed Procedures .................................................................................. 15-6 Adding a Signal Select Object.................................................................................. 15-6

Table of Contents

7

Editing a Signal Select Object .................................................................................. 15-8 Adding Input Entries to a Signal Select Object ........................................................ 15-9 Deleting Input Entries from a Signal Select Object ................................................ 15-10 Commanding a Signal Select Object...................................................................... 15-10 Deleting a Signal Select Object.............................................................................. 15-11

Chapter 17 Working with Multiple Command Objects .................... 17-1

Introduction................................................................................................ 17-1

Key Concepts............................................................................................. 17-2 Multiple Command Object ........................................................................................ 17-2 Attributes .................................................................................................................. 17-2


Detailed Procedures .................................................................................. 17-5 Adding a Multiple Command Object......................................................................... 17-5 Editing a Multiple Command Object ......................................................................... 17-8 Adding Action Table Entries to a Multiple Command Object.................................... 17-8 Deleting Action Table Entries from a Multiple Command Object ............................. 17-9 Commanding a Multiple Command Object............................................................. 17-10 Deleting a Multiple Command Object..................................................................... 17-11

Chapter 18 Working with Data Broadcast Objects .......................... 18-1

Introduction................................................................................................ 18-1

Key Concepts............................................................................................. 18-2 Data Broadcast Object ............................................................................................. 18-2 Unconfirmed COV Notification ................................................................................. 18-2 Attributes .................................................................................................................. 18-2


Detailed Procedures .................................................................................. 18-4 Adding a Data Broadcast Object .............................................................................. 18-4 Editing a Data Broadcast Object .............................................................................. 18-5 Commanding a Data Broadcast Object.................................................................... 18-5 Deleting a Data Broadcast Object ............................................................................ 18-5

Chapter 19 Working with Demand Limiting/Load Rolling (DLLR) Objects 19-1

Introduction................................................................................................ 19-1

Key Concepts............................................................................................. 19-2 Demand Limiting/Load Rolling Controller Object ..................................................... 19-2 Shedding .................................................................................................................. 19-2


8

Releasing ................................................................................................................. 19-2 Demand Limiting ...................................................................................................... 19-3 Interaction with Other Objects.................................................................................. 19-4 Attributes .................................................................................................................. 19-6


Detailed Procedures ................................................................................ 19-10 Adding a DLLR Object ........................................................................................... 19-10 Editing a DLLR Object............................................................................................ 19-13 Commanding a DLLR Object ................................................................................. 19-14 Deleting a DLLR Object ......................................................................................... 19-14

Chapter 20 Working with Load Objects............................................ 20-1

Introduction................................................................................................ 20-1

Key Concepts............................................................................................. 20-2 Load Object.............................................................................................................. 20-2 Shedding .................................................................................................................. 20-2 Releasing ................................................................................................................. 20-2 Attributes .................................................................................................................. 20-2


Detailed Procedures .................................................................................. 20-7 Adding a Load Object............................................................................................... 20-7 Editing a Load Object............................................................................................. 20-10 Commanding a Load Object................................................................................... 20-11 Deleting a Load Object........................................................................................... 20-11

Chapter 21 Working with Pulse Meter Objects ................................ 21-1

Introduction................................................................................................ 21-1

Key Concepts............................................................................................. 21-2 Pulse Meter Object................................................................................................... 21-2 Attributes .................................................................................................................. 21-2


Detailed Procedures .................................................................................. 21-5 Adding a Pulse Meter Object ................................................................................... 21-5 Editing a Pulse Meter Object.................................................................................... 21-7 Commanding a Pulse Meter Object ......................................................................... 21-7 Deleting a Pulse Meter Object ................................................................................. 21-8

Chapter 22 Working with Utility Profile Objects .............................. 22-1

Introduction................................................................................................ 22-1

Table of Contents

9

Key Concepts............................................................................................. 22-2 Utility Profile Object .................................................................................................. 22-2 Attributes .................................................................................................................. 22-2


Detailed Procedures .................................................................................. 22-5 Adding a Utility Profile Object................................................................................... 22-5 Editing a Utility Profile Object ................................................................................... 22-7 Commanding a Utility Profile Object......................................................................... 22-7 Deleting a Utility Profile Object................................................................................. 22-8

Chapter 23 Working with Analog Totalization Objects ................... 23-1

Introduction................................................................................................ 23-1

Key Concepts............................................................................................. 23-2 Analog Totalization Object ....................................................................................... 23-2 Analog Totalization Object Reset............................................................................. 23-3 Attributes .................................................................................................................. 23-3


Detailed Procedures .................................................................................. 23-7 Adding an Analog Totalization Object ...................................................................... 23-7 Editing an Analog Totalization Object ...................................................................... 23-9 Commanding an Analog Totalization Object ............................................................ 23-9 Deleting an Analog Totalization Object .................................................................. 23-10

Chapter 24 Working with Event Totalization Objects...................... 24-1

Introduction................................................................................................ 24-1

Key Concepts............................................................................................. 24-2 Event Totalization Object ......................................................................................... 24-2 Event Totalization Object Reset ............................................................................... 24-3 Attributes .................................................................................................................. 24-3


Detailed Procedures .................................................................................. 24-7 Adding an Event Totalization Object ........................................................................ 24-7 Editing an Event Totalization Object ........................................................................ 24-9 Commanding an Event Totalization Object .............................................................. 24-9 Deleting an Event Totalization Object .................................................................... 24-10

Troubleshooting ...................................................................................... 24-11

Chapter 25 Working with Runtime Totalization Objects ................. 25-1


10

Introduction................................................................................................ 25-1

Key Concepts............................................................................................. 25-2 Runtime Totalization Object ..................................................................................... 25-2 Runtime Totalization Object Reset........................................................................... 25-3 Attributes .................................................................................................................. 25-3


Detailed Procedures .................................................................................. 25-7 Adding a Runtime Totalization Object ...................................................................... 25-7 Editing a Runtime Totalization Object ...................................................................... 25-9 Commanding a Runtime Totalization Object............................................................ 25-9 Deleting a Runtime Totalization Object .................................................................. 25-10

Chapter 26 Working with Analog Alarm Objects ............................. 26-1

Introduction................................................................................................ 26-1

Key Concepts............................................................................................. 26-2 Analog Alarm Object ................................................................................................ 26-2 States ....................................................................................................................... 26-2 SNR.......................................................................................................................... 26-2 Attributes .................................................................................................................. 26-3


Detailed Procedures .................................................................................. 26-7 Adding an Analog Alarm Object ............................................................................... 26-7 Editing an Analog Alarm Object ............................................................................. 26-10 Commanding an Analog Alarm Object ................................................................... 26-11 Deleting an Analog Alarm Object ........................................................................... 26-11

Chapter 27 Working with Multistate Alarm Objects ........................ 27-1

Introduction................................................................................................ 27-1

Key Concepts............................................................................................. 27-2 Multistate Alarm Object ............................................................................................ 27-2 States ....................................................................................................................... 27-2 SNR.......................................................................................................................... 27-2 Attributes .................................................................................................................. 27-2


Detailed Procedures .................................................................................. 27-6 Adding a Multistate Alarm Object ............................................................................. 27-6 Editing a Multistate Alarm Object ............................................................................. 27-9 Commanding a Multistate Alarm Object................................................................... 27-9

Table of Contents

11

Deleting a Multistate Alarm Object ......................................................................... 27-10

Chapter 28 Working with Trend Log Objects................................... 28-1

Introduction................................................................................................ 28-1

Key Concepts............................................................................................. 28-2 Trend Log Object ..................................................................................................... 28-2 Attributes .................................................................................................................. 28-2


Detailed Procedures .................................................................................. 28-5 Adding a Trend Log Object ...................................................................................... 28-5 Editing a Trend Log Object ...................................................................................... 28-7 Commanding a Trend Log Object ............................................................................ 28-7 Deleting a Trend Log Object .................................................................................... 28-8

Chapter 29 Working with Notification Class Objects ...................... 29-1

Introduction................................................................................................ 29-1

Key Concepts............................................................................................. 29-3 Notification Class ..................................................................................................... 29-3 Destinations ............................................................................................................. 29-3 Attributes .................................................................................................................. 29-4


Detailed Procedures .................................................................................. 29-7 Adding a Notification Class Object in Project Builder............................................... 29-7 Editing a Notification Class Object in Project Builder............................................. 29-10 Editing a Notification Class Object Using a VT100 ................................................ 29-12 Commanding a Notification Class Object Using a VT100...................................... 29-13 Deleting a Notification Class Object Using a VT100 .............................................. 29-13

Chapter 30 Working with Remote Destination Objects................... 30-1

Introduction................................................................................................ 30-1

Key Concepts............................................................................................. 30-2 Remote Destination Object Operation...................................................................... 30-2 Attributes .................................................................................................................. 30-2


Detailed Procedures .................................................................................. 30-7 Adding a Remote Destination Object ....................................................................... 30-7 Editing a Remote Destination Object ..................................................................... 30-10


12

Deleting a Remote Destination Object ................................................................... 30-10

Chapter 31 Working with E-mail Objects.......................................... 31-1

Introduction................................................................................................ 31-1

Key Concepts............................................................................................. 31-2 E-mail Object Operation........................................................................................... 31-2 E-mail Delivery Failure ............................................................................................. 31-3 SMTP Server Location ............................................................................................. 31-3 Attributes .................................................................................................................. 31-4 Example ................................................................................................................... 31-6


Detailed Procedures .................................................................................. 31-9 Adding an E-mail Object .......................................................................................... 31-9 Editing an E-mail Object......................................................................................... 31-12 Commanding an E-mail Object .............................................................................. 31-12 Deleting an E-mail Object ...................................................................................... 31-12

Chapter 32 Working with Pager Objects .......................................... 32-1

Introduction................................................................................................ 32-1

Key Concepts............................................................................................. 32-2 Pager Object Operation ........................................................................................... 32-2 Attributes .................................................................................................................. 32-3


Detailed Procedures .................................................................................. 32-6 Adding a Pager Object ............................................................................................. 32-6 Editing a Pager Object ............................................................................................. 32-9 Commanding a Pager Object ................................................................................... 32-9 Deleting a Pager Object ........................................................................................... 32-9

Troubleshooting ...................................................................................... 32-10 Troubleshooting Using Internal Attributes .............................................................. 32-10

Chapter 33 Working with BACnet™ Group Objects........................ 33-1

Introduction................................................................................................ 33-1

Key Concepts............................................................................................. 33-2 BACnet Group Object vs Johnson Controls Proprietary Group Object .................... 33-2 Attributes .................................................................................................................. 33-2

Detailed Procedures .................................................................................. 33-4

Table of Contents

13

Adding a BACnet Group Object ............................................................................... 33-4 Editing a BACnet Group Object................................................................................ 33-4 Deleting a BACnet Group Object ............................................................................. 33-7

Chapter 34 Working with Event Enrollment Objects....................... 34-1

Introduction................................................................................................ 34-1

Key Concepts............................................................................................. 34-2 Event Enrollment Object........................................................................................... 34-2 Attributes .................................................................................................................. 34-2

Detailed Procedures .................................................................................. 34-5 Adding an Event Enrollment Object ......................................................................... 34-5 Editing an Event Enrollment Object.......................................................................... 34-5 Commanding an Event Enrollment Object ............................................................... 34-8 Deleting an Event Enrollment Object ....................................................................... 34-9 Editing Event Parameters - Examples.................................................................... 34-10

Appendix A Building an Energy Management Application ................A-1

Introduction..................................................................................................A-1

Key Concepts...............................................................................................A-2 Object Interaction .......................................................................................................A-2 Attribute Involvement..................................................................................................A-4 Advanced Object Functions .......................................................................................A-5

Procedure Overview ....................................................................................A-6

Detailed Procedures ....................................................................................A-7 Building an Energy Management Application.............................................................A-7

Troubleshooting ..........................................................................................A-8

Appendix B Building a Message Router Application .........................B-1

Introduction..................................................................................................B-1

Key Concepts...............................................................................................B-3 Message Router Purpose ..........................................................................................B-3 Routing SNRs ............................................................................................................B-3 Filtering ......................................................................................................................B-4 Object Interaction .......................................................................................................B-5

Appendix C Building an Optimal Start Application ............................C-1

Introduction..................................................................................................C-1

Key Concepts...............................................................................................C-2


14

Object Interaction ...................................................................................................... C-2 Attribute Involvement................................................................................................. C-3

Procedure Overview ....................................................................................C-4

Detailed Procedures ....................................................................................C-5 Building an Optimal Start Application........................................................................ C-5

Troubleshooting ..........................................................................................C-6

Appendix D Building an Interlock Application ....................................D-1

Introduction..................................................................................................D-1

Key Concepts...............................................................................................D-2 Object Interaction ...................................................................................................... D-2 Attribute Involvement................................................................................................. D-3 Example .................................................................................................................... D-4

Procedure Overview ....................................................................................D-7

Detailed Procedures ....................................................................................D-8 Building an Interlock Application ............................................................................... D-8

Appendix E Building a Signal Select Application...............................E-1

Introduction.................................................................................................. E-1

Key Concepts............................................................................................... E-2 Object Interaction .......................................................................................................E-2 Attribute Involvement..................................................................................................E-4

Procedure Overview .................................................................................... E-5

Detailed Procedures .................................................................................... E-6 Building a Signal Select Application...........................................................................E-6

N30 Supervisory Controller User’s Manual 1-1

© November 01, 2001 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-6892010 Software Release 5.0

Chapter 1 Using this Manual

Introduction This manual is a learning and reference guide for the N30 Supervisory Controller (N30). This manual contains an overview of the N30, basic operation, and specific procedures for a number of objects and features available to control your Building Automation System (BAS) using the N30. This chapter describes:

• organization of information in this manual

• where to find related information about the N30

• manual conventions This manual is written with the assumption that the user is familiar with the general concepts and terminology of Building Automation Systems (BAS) and Heating, Ventilating, and Air Conditioning (HVAC). Note: Unless otherwise indicated, the information in this manual

refers to both the N30 Supervisory Controller and the N31 Supervisory Controller.

1-2 N30 Supervisory Controller User’s Manual

Key Concepts Manual Organization

The first three chapters of this manual contain introductory material about the manual and the N30. This includes information on how to perform generic tasks. Generic tasks are those that are performed the same, though in practice they may differ in the details. For example, the task of adding an object is generic to all objects; however, adding an Optimal Start (OST) object requires that the object be added to a specific container with specific attributes. The remaining chapters each address a specific object. This manual also contains several appendixes that provide details about how to create some of the more complex objects and applications.

Manual Conventions Throughout this manual the term N30 is used to stand for an N30 Supervisory Controller and, unless otherwise noted, the N31 Supervisory Controller. The term VT100 is used to stand for either a VT100 Terminal or a VT100 Terminal Emulator running on a Personal Computer (PC). Unless otherwise indicated, all screen captures and procedures were performed with a VT100 Terminal Emulator running on a PC and connected to one of the serial ports on the N30. Where possible we have shown some of the screens that would be seen if performing the indicated tasks offline using Project Builder software to edit the N30 database. In these cases, Project Builder was installed as part of M-Tool on the same PC where we were running the VT100 Terminal Emulator.


Chapter Organization Each chapter in the N30 Supervisory Controller User’s Manual can be divided into the main sections identified in Table 1-1.

Table 1-1: Chapter Organization Section Description Introduction Briefly outlines the contents of the chapter and lists

any task instructions that are written in the chapter. Key Concepts Describes concepts necessary to perform specific

tasks. The Key Concepts section of the object chapters include descriptions of attributes necessary to properly create the object.

Procedure Overview Describes the general steps for completing the tasks described in the Detailed Procedures section. It combines the steps of the Detailed Procedures sections into a short paragraph without drawings or explanatory notes. This section is for those familiar with the tasks they are planning to perform. Procedure Overview pages can be used to create a quick reference guide to N30 tasks.

Detailed Procedures Describes in detail the steps needed to complete the tasks described within the chapter.


Related Publications Table 1-2 describes where to find various types of information about the N30 Supervisory Controller.

Table 1-2: N30-Related Publications Topic Publication Publication Number Technical Information

How to Install an N30 N30 Supervisory Controller Installation Technical Bulletin

LIT-6891100

How to Network N30s N30 Supervisory Controller Networking Technical Bulletin

LIT-6891300

How to Add Controllers and Map Points

N30 Supervisory Controller Point Mapping Technical Bulletin

LIT-6891400

How to Setup an N30 Site Using Project Builder

N30 Supervisory Controller Quick Start Technical Bulletin

LIT-6891200

M-Tool Project Builder Project Builder User’s Guide

Communications How to Use Site Book and Setup Ethernet Communications with an N30

Site Book User’s Guide

How to Setup Direct Connect and Dial-up Connections with N30s on Windows® 98

Direct Connect and Dial-up on Windows 98 Application Note

LIT-6893350

How to Setup Direct Connect and Dial-up Connections with N30s on Windows NT®

Direct Connect and Dial-up on Windows NT Application Note

LIT-6893400

How to Setup Direct Connect and Dial-up Connections with N30s on Windows 2000

Direct Connect and Dial-up on Windows 2000 Application Note

LIT-6893450

Objects Reference to All Objects and their Attributes

Object Dictionary

Questions or Comments about this Manual Please direct your questions about the technical content of this manual to your authorized Johnson Controls representative.


Chapter 2 Introduction to the N30 Supervisory Controller

Introduction This chapter describes the basic functions and operation of an N30 Supervisory Controller (N30). It also provides the foundation you need to monitor and control your facility using the N30. This chapter includes:

• N30 concepts

• descriptions and illustrations of the Building Automation System (BAS) components

© June 28, 2006 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-6892020 Software Release 5.0


Key Concepts N30 Supervisory Controller

The N30 monitors and controls HVAC equipment in your facility. It provides powerful data gathering and energy management tools, such as Totalization and Demand Limiting, which can improve the cost efficiency of your facility. The N30 is optionally available with an integral Local Display Terminal (LDT).

N30 Capabilities You can complete the following BAS functions with the N30:

• schedule BAS actions

• set up calendars, including exception and holiday calendars

• monitor facility conditions

• detect and respond to alarms

• control equipment and automate routine functions

• collect trend and totalization data

• reduce energy consumption and costs

BAS Components A typical BAS configuration consists of the components listed below and illustrated in Figure 2-1 and Figure 2-2.

• Multiple N30 Supervisory Controllers (with or without optional Local Display Terminal [LDT])

• VT100 Terminal/Terminal Emulator

• Ethernet Local Area Network (LAN)

• N2 Bus (field bus or controller bus)

• serial printer

• N2 controllers (Table 2-1)

N30 Supervisory Controller User's Manual 2-3

Supported Application Specific Controllers (ASCs) The N30 supports all current N2 devices except the N2 Dialer. This includes Metasys® (AS) and Facilitator™ (FA) models and support for the Variable Air Volume Modular Assembly (VMA) 1400 Series controller. Table 2-1 shows the firmware version of all currently supported ASCs.

Note: Metasys Integrator® (MIG), Variable Air Volume (VAV), Unitary (UNT), and Air Handling Unit (AHU) controllers with older code revisions are not allowed on an N30 system. They are forced offline when detected.

Table 2-1: Firmware Revision of Current ASCs* Device/Controller Type

Revision Comments

DR-9100 1.x Room Controller DR-9100 2.x Room Controller DC-9100 1.x Plant Controller DC-9100 2.x Plant Controller DO-9100 1.x Digital Optimizer DX-9100 1.x Digital Controller DX-9100 2.x Digital Controller TC-9100 1.x-3.x Temperature Controller TEC1100 1.x N2 LCD Thermostat TEC2100 1.x N2 LCD Thermostat XT-9100 1.x Extension Module XTM-101 1.x Extension Module XTM-105 1.x Extension Module XTM-905 1.x Extension Module LDT A08 or later Local Display Terminal LCP-xxx All Lab and Central Plant Controller MIG 3.0 or later Metasys Integrator UNT B03 or later Unitary Controller VAV A03 or later Variable Air Volume Controller AHU C03 or later Air Handling Unit Controller PHX All Phoenix Interface Module VMA1400 All VAV Modular Assembly VND (Vendor Devices) All Metasys Compatible (by others)

including TEC1100 ILC** All Intelligent Lighting Controller IFC-1010/2020 All Intelligent Fire Controller

* Some controllers are unique to a local market and may not be available on a global basis.

** Information for ILCs is not valid for Microlite lighting controllers. For Microlite panels, use the information for Vendor Devices instead (VND).


M-Series Workstationor PC with VT100 Emulator

N30 with LDT

VAV

UNTDX

VMA

N2

N30 BAS

AHU

VT100

oror

Serial Printer

esc

Figure 2-1: BAS Components - N30 Example

Interfaces to the N30 There are several user interfaces to the N30 available. M-Series Workstations are used for online browsing and editing of facility conditions with full graphical displays, VT100 Terminals or Terminal Emulators on PCs can be used to add, edit, and browse objects in text mode. Project Builder software is used for offline creation, management, and editing of N30 databases. The Local Display Terminal (LDT) installed in the N30 is used for display of a selected set of data from the facility, including alarms, and allows local onsite adjustments to operating conditions.

M-Series Workstation Johnson Controls M-Series Workstation product portfolio represents a special packaging of software components. The M3 Workstation software application suite includes monitoring, commissioning, and analysis features. It works in combination with N30 Series and existing Companion™/Facilitator Supervisory Controllers to provide a complete facility management solution.

N30 Supervisory Controller User's Manual 2-5

The M5 Workstation provides extensions and enhancements to the Metasys Operator Workstation (OWS) to enable existing Metasys N1 systems to be expanded with N30 controllers.

M-Tool M-Tool contains the System Tools and the Configuration Tools. The Project Builder component of System Tools includes the ability to:

• upgrade existing N30s to the latest firmware

• import Advanced Installation Management (AIM) Tools point lists and room schedule information

• configure the complete N30 database

• upload and download Application Specific Controllers (ASCs) and DXs from a file created by Configuration Tools

M-Tool includes the N30 Upgrade Utility, which allows you to upgrade databases from the data format used at one release to the data format used at the next release.

UNTDXVMA

N30

Ethernet

UNT DX VMA

N2N2

network n30

M-Series Workstation

VT100

N30 with LDT

esc

Figure 2-2: Networked N30s Example

VT100 Terminal A video terminal developed by DEC and still a standard interface. A VT100 Terminal can be connected to a serial port on an N30 either directly or via modem.


VT100 Terminal Emulator A program that allows a computer to function like a VT100 Terminal. The computer appears as a terminal to the N30 and accepts the same escape sequences for functions such as cursor positioning and clearing the screen.

Local Display Terminal (LDT) A display device optionally installed in the N30 controller. The LDT provides alarm notification and navigation and access to data in the controller. It allows the display and modification of operating conditions, such as temperature, heating and cooling setpoints, and fan override. For more information on the LDT, refer to the N30 Supervisory Controller Installation Technical Bulletin (LIT-6891100).

Printer Connects to an N30 via a serial port or modem. The N30 sends data, such as alarm messages, summaries, or scheduled reports to a printer file in one of three ways: automatically, by operator command, or by scheduled command.

N2 Bus The communication network that allows the application specific controllers to communicate with the N30.

Ethernet Bus The Local Area Network (LAN) protocol used to allow multiple N30 Supervisory Controllers to communicate peer-to-peer using BACnet® messaging. It is a widely used LAN standard.

BACnet The Building Automation Control Network (BACnet), Standard 35-1995, designed by the American Society of Heating, Refrigerating, and Air Conditioning Engineers (ASHRAE) as a data communications protocol to promote connectivity between multiple vendors of control equipment.

10BaseT, Twisted Pair Cable The Cable used to connect N30s in an Ethernet network. Specified by the IEEE 10BaseT standard, Unshielded Twisted Pair (UTP) and Shielded Twisted Pair (STP) are common and economical media to install in the network.



Chapter 3 Getting Started

Introduction A VT100 can be used to add and edit objects and to browse an N30 database. Project Builder software provides an easier way to create, define, and edit N30 databases offline. This chapter explains the VT100 interface to the N30 and describes tasks performed in using an N30. Notes on using Project Builder to perform these tasks are included where appropriate. This chapter describes how to:

• log on to an N30

• check the firmware version level of an N30

• set the date and time

• edit the attributes of an N30

• browse an N30 database with a VT100

• add objects with a VT100

• edit objects with a VT100

• command objects

• display a summary

• print a summary

• change an IP address

• rebind a site

• change device names

• archive the current database


Note: Tasks such as adding or commanding objects are described generically. For details on specific objects, see the relevant chapter in this manual or in the Object Dictionary. For information about using Project Builder software, see the Project Builder User’s Guide.


Key Concepts N30 Task Overview

Figure 3-1 is a flowchart of tasks to get started with your N30 system using the VT100 and, in the case of setting up the N30 site, Project Builder software. Other documents are referenced where required. For information about generating N30 databases using Project Builder, refer to the N30 Supervisory Controller Quick Start Technical Bulletin (LIT-6891200). Note: We recommend generating databases using Project Builder

software. Project Builder supports copy, paste, and mass copy and can save you a substantial amount of time.

Install the N30.See the N30 Supervisory

Controller Installation TechnicalBulletin

(LIT-6891100).

Set Up the N30 Site.See the N30 Supervisory

Controller Quick StartTechnical Bulletin

(LIT-6891200).Define Schedules.

See the chapters in this manualon Schedule objects and

Calendar objects.

Define Trend Logs.See the Working with Trend

Log Objects chapterin this manual.

Build Energy ManagementApplications.

See Appendix A: Building anEnergy Management

Application in this manual.

Build Optimal StartApplications.

See Appendix C: Building anOptimal Start Application

in this manual.

Define Global DataSharing Objects.

See Working with Global DataSharing Objects chapter

in this manual.

Build Signal SelectApplications.

See Appendix E: Building aSignal Select Application

in this manual.

Edit and add additionalobjects as required.

See the appropriate chapter inthis manual or in theObject Dictionary.Add Controllers to your

Database and Map the Pointsto N30 Point Objects.

See the N30 SupervisoryController Point Mapping

Technical Bulletin(LIT-6891400) and the

Object Dictionary.

Print ControllerConfigurations.

See the N30 SupervisoryController Point Mapping

Technical Bulletin(LIT-6891400).

Define Alarms andAlarm Messages.

See the chapters in this manualon Analog Alarm objects,Multistate Alarm objects,

Notification Class objects,Remote Destination objects,

E-mail objects, andPager objects.

Define Groups.See Working with Group

Objects chapter in this manual.

N30 Overview.vsd

Figure 3-1: Getting Started with an N30


Objects Configurable and reusable features of the N30 that contain both data and a means to act on that data to achieve desired results. They add flexibility to the programming of the N30 by allowing you to add only the objects you need to your database. They are the building blocks of the N30 database. Individual objects are described throughout the N30 literature. The Object Dictionary provides a reference to all the current N30 objects.

Object Names Providing an Object Name is optional, but if it is defined, it must be unique throughout the site. If it is not defined, the full reference becomes the identifier. For example, Building1Floor2. The following characters are not allowed: @ . ? * $ # : ‘ [ or ].

Containers The basic organization of the N30 database is arranged through containers. All objects are added to containers. The type of container selected determines the type of objects that can be added to that part of the database. See Table 3-1 for a list of which objects can be added to each container. A container object can hold a maximum of 75 objects. However, since there are hidden objects in N30s, N30s are limited to 50 child objects. To put more than 50 objects in an N30, use Container objects to organize your objects. Use a maximum of 50 Container objects in one N30.

Groups A way to personalize the organization of a N30 database. Groups contain references to objects. This allows you access to the object from both the designated group and from the container where it was added. They are a powerful organizational tool when working with large databases. For more information, see the Working with Group Objects (LIT-6892060) chapter in this document.

Flash Memory A type of nonvolatile memory within the N30 device. The N30’s Flash memory stores configuration data, startup code, boot code, main code, and the archive database within this memory.


Warm Start Cycling the N30 power off and then on again. In the N30, it is considered a warm start when power is cycled with the battery still installed. Warm starts are used as a reset for certain functions. For example, after changing the IP address in an N30, it is necessary to warm start the device to allow the updates to take effect.

Site Manager The N30 within a site that contains the master Site object. The master Site object is responsible for the synchronization of global objects, time synchronization, and device status monitoring within the site. There can only be one Site Manager per site.

Rebind Site Rebind Site (formerly Rebind References) is a fail-safe command used to correct situations where references to offbox objects become unreliable. The Rebind Site command typically is used when you have made major changes to a database and are re-downloading objects to N30s. If all N30s in the database are connected during the download, some N30s can bind to objects that have been moved to other N30s. The Rebind Site command is not required when the IP address of an N30 changes because other N30s in the site automatically relocate it within a few minutes. See Rebinding a Site in the Detailed Procedures section. The following describes a sample sequence of events requiring the Rebind Site command: 1. Outdoor Air (an N2 Analog Input object on N30-B) is used in an

Interlock object in N30-A. 2. N30-A temporarily loses its network connection to N30-B. 3. User moves Outdoor Air from N30-B to N30-C. 4. User reestablishes the network connection to N30-A. 5. User must Rebind Site in order for the Interlock object in N30-A

to reestablish its reference to Outdoor Air.


Containers and Objects You can add objects as they are needed for your facility. The objects available to add depend on the container selected. Table 3-1 lists the objects that can be added to each container.

Table 3-1: Containers/Objects When This Container is Selected These Objects Can Be Added: Site Name - Top level name on the

VT100 screen Note: All the N30s on this site are

listed in this container; it is usually given a localized name during set up of the N30 site.

Analog Alarm* Multistate Alarm* Analog Totalization* Runtime Totalization* Event Totalization* Trend Log* Container Data Broadcast*

N30 - Name determined by user All objects that can be added from the site name Internals Site

Report Server Also, all objects that can be added from the site name

Comm All objects that can be added from the site name Applications All objects that can be added from the site name Energy Optimal Start*

Heavy Equip Contr Pulse Meter* Load*

Demand Limit and Load Rolling (DLLR*) Utility Profile* Also, all objects that can be added from the site name

Group Group* Also, all objects that can be added from the site name

N2 Controller Also, all objects that can be added from the site name

A Controller object within an N2 container

N2 Analog Input (N2 AI) N2 Binary Input (N2BI) N2 Analog Output (N2 AO) N2 Binary Output (N2 BO) N2 Multistate Input (N2 MSI)

N2 Multistate Output (N2 MSO) N2 Pulse Counter (N2 PC) Also, all objects that can be added from the site name

Notifications Notification* Also, all objects that can be added from the site name

Continued on next page . . . * Detailed procedures for working with these objects are in this manual. For all other objects, refer to the

Object Dictionary for further information.


When This Container is Selected (Cont.)

These Objects Can Be Added:

Operator Devices Display* (Project Builder is required to add this object.) E-mail* Modem Config* LAN Remote Dest Pager* Printer* Remote Destination* VT100* (Project Builder is required to add this object.) Also, all objects that can be added from the site name

Operators Operator* Also, all objects that can be added from the site name

Programming Multiple Command Interlock* Global Data* Signal Select*

Multistate Value (MV) Analog Value (AV) Binary Value (BV) Also, all objects that can be added from the site name

Schedule Schedule* Calendar* Temporary Occupancy* Also, all objects that can be added from the site name

Summaries Summary Also, all objects that can be added from the site name

* Detailed procedures for working with these objects are in this manual. For all other objects, refer to the Object Dictionary for further information.


N30 Screen Layout on VT100 Terminal or VT100 Terminal Emulator Figure 3-2 shows a typical N30 screen on a VT100 Terminal. The screen shown is the main screen for the site called Brown Deer after someone has logged on to the N30 device named Dean with a user name of ADMIN. Table 3-2 describes areas 1 through 4 in Figure 3-2. See Browsing an N30 Database with a VT100 in this chapter for basic screens available in the N30. See the specific object chapter in this document also.

Figure 3-2: N30 Screen Layout


Table 3-2: N30 Screen Layout Description Number Display Area Name Purpose and Description 1 Alarm Information

Note: Refer to Appendix B: Building a Message Router Application (LIT-6892320) for more information about SNRs.

Used to view Status Notification Reports (SNRs). Occupies Lines 1 and 2 at the top of the screen. Alarm information displayed in this example includes (from left to right): • alarm priority (IMP). Possible values are SER (Serious), CRIT

(Critical), IMP (Important), STAT (Status). • event state being reported (LW). Possible values are HA (High

Alarm), LA (Low Alarm), HW (High Warning), LW (Low Warning), and Nor (Normal).

• object name in alarm (Principal Office) • value of attribute (65.0 deg F). Assumed attribute is Present

Value. • units of attribute (optional) • local date (28 Jan 2000) • local time (09:16:39) • message text (line 2)

2 Site/User Information Used to view site/user information. Occupies Line 3 at the top of the screen. Site/user information displayed in this example includes (from left to right): • device object name (Dean) • name of logged-in user (ADMIN) • date and time (Fri 28 Jan 2000 9:18 CST)

3 User Workspace Used to view site information and to complete most operations. Occupies Lines 4 through 22 in the middle of the screen. In this space, the operator displays and interacts with objects, calls up summaries, and uses the available features to program the site. In this example, Brown Deer is the name of the site, Overview Grp is the name of the Site Group, and South Building and Dean are names the operator gave to the two N30s on this site.

4 User Assistance Used to view function key options, help messages, and error messages. Occupies Lines 23 and 24 at the bottom of the screen.

Browsing Browsing with a VT100 is moving within and through the N30 database to view, edit, and command objects. Browsing with Project Builder software is performed offline and therefore commands are not available. For information on browsing an N30 database using an M-Series Workstation, see M-Explorer User’s Guide. The User Assistance Line at the bottom of each screen (Number 4 in Figure 3-2) displays the active keys and functions. The active keys and the functions associated with each key change according to where you are in the database. It also provides instructions for filling in attribute fields. Some basic navigational keys are available but not described, such as the arrow keys for moving the cursor.


Functions Available in the VT100 The same keys are used in an N30 with a VT100 Terminal or a VT100 Terminal Emulator. The functions of some of the keys are context-sensitive. For example, the F3 key can add, edit, or save changes to an object, depending on when it is used. The available keys and their functions at that time appear on the User Assistance Line at the bottom of the screen. See Table 3-3 for descriptions of the keys.


Table 3-3: Functions Available in N30 from VT100 Function Key Function Context Purpose ] or [ Page There is more data than can

fit on one screen. Displays all available screens.

Arrow Keys Move cursor or highlight fields

Available on any screen where the cursor can move.

Moves the cursor or highlight box to an object, attribute, or field.

Delete Delete An object is open or an empty container is open.

Deletes the selected object.

F1 Ack An alarm is displayed at the top of the screen.

Acknowledges alarms that appear at the top of the screen.

F2 Command An object is selected. Allows you to select an action on the selected object.

Del (Delete) Item

An attribute that can have items deleted from it is open.

Deletes an item from an attribute, such as an item from an Input List.

Add A container or an object that can have items added to it is selected.

Opens the Add Object screen. However, the function varies with the object or container that is highlighted when this key is pressed.

Edit An editable object is open. Displays the objects attribute screen.

F3

Save An editable object is open and changes have been made to it.

Saves changes to the memory database (RAM). The memory database is archived in Flash memory once a day after midnight.

Add Item An attribute that can have items added to it is open.

Adds a blank entry for an item to be added to an attribute, such as an item for an Input List.

Back An attribute that can have items added to or deleted from it is open.

Displays the previous screen. F4

Cancel An object, container, or attribute screen is open.

Cancels the current action and/or displays the previous screen.

Q Quit N30 main screen displays. Logs the user off the N30. Execute An object has its command

line open and a command selected.

Carries out (executes) the displayed command.

Open An object, container, or device is selected.

Opens the selected (highlighted) object.

Return (Enter)

Select An add object screen is open with an object highlighted.

Opens the attribute screen to create a new object of the highlighted type.

Spacebar Expand/ Collapse

An object with a plus (+) or minus (–) next to it is highlighted.

Expands a container, device, group, or object that has a plus (+) sign beside it; collapses a container that has a minus (-) sign beside it.

Spacebar (forward) and Backspace key (backward)

Cycle A field with multiple predefined options is selected, for example, commanding an object.

When available, allows you to cycle through the available options for the selected attribute.

Tab Confirm Delete An object has been deleted. Confirms the Delete operation. Move to next

field An object is being edited. Moves the highlight box to highlight an

attribute.


Procedure Overview Table 3-4: Getting Started To Do This Follow These Steps: Log On to an N30 Start your VT100 Emulator or turn on your VT100. Press Enter when the

N30 name appears at the top of the screen. Type your Login ID and press Enter. Type your password and press Enter.

Check the Firmware Version Level of an N30

Using a VT100 Terminal or VT100 Terminal Emulator on a PC, browse to and highlight the N30 you want to check. Press Enter. The firmware version level is on the right side under engineering values.

Set the Date and Time Use the arrow keys to highlight an N30. Press the F2 (Command) key. Cycle through the list of commands until the Set Time or Set Date command appears. Use the arrow keys or Tab key to highlight the Value field. Edit the value as necessary. Press Enter.

Edit the Attributes of the N30 Use the arrow keys to highlight an N30. Press Enter. Press the F3 (Edit) key. Move to the field that you want to edit. Edit the values. Press the F3 (Save) key to save the changes or the F4 (Cancel) key to cancel the changes.

Browse an N30 Database with a VT100

Use the arrow keys to highlight an N30. Use the Spacebar to expand the list of containers. Select a container. Press the Spacebar to expand the list of objects. Select an object. Press the Spacebar to expand the list of additional objects and select an object. Press Enter to open the object.

Add Objects with a VT100 Browse to and highlight an N30. Press the Spacebar to expand the list of object containers. Browse to and highlight a container or object. Press the F3 (Add) key. Select the type of object to add and press Enter. Fill in the fields. Press the F3 (Save) key.

Edit Objects with a VT100 Browse to and highlight an object. Press Enter to open the object. Press the F3 (Edit) key. Edit as desired. Press the F3 (Save) key.

Command Objects Browse to and highlight an object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list of commands until the desired command appears. Press Enter to carry out the command.

Display a Summary Browse to and highlight the Summary container. Press the Spacebar to expand the list of Summaries. Highlight a Summary. Press the F2 (Command) key. Use the Spacebar and Backspace keys to cycle through the list until Display appears. Press Enter.

Print a Summary Browse to and highlight the Summary container. Press the Spacebar to expand the list of Summaries. Highlight a Summary. Press the F2 (Command) key. Use the Spacebar and Backspace keys to cycle through the list until Print appears. Use the arrow keys or Tab key to highlight the Destination field. Use the Spacebar and the Backspace key to cycle through to the desired printer. Press Enter.

Change an IP Address Browse to and select an N30. Press Enter. Press the F3 (Edit) key. Move the cursor to IP Address. Press Enter. Type in the address for your network. Press the F4 (Back) key. Enter the IP Mask and IP Router addresses. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key to return to the main screen. Press Q to quit the N30. Warm start the N30 to reset.

Rebind a Site Browse to and highlight an N30. Press Enter to open the N30 Device object. Press the F2 (Command) key. Use the Spacebar and Backspace key to cycle through the list until Rebind Site appears. Press Enter.

Continued on next page . . .


To Do This (Cont.) Follow These Steps: Change Device Names Browse to and highlight an N30. Press the Enter key to open the N30

Device Object. Press the F3 (Edit) key. Use the arrow keys or Tab key to highlight the Name field. Type in the new device name. Press the F3 (Save) key. Press any key to continue.

Archive the Current Database Note: The N30 automatically archives the memory database to Flash memory at 12:02 a.m. (just after midnight) and after a download. The Archive command is provided for special circumstances and should not be used regularly.

After logging into an N30, browse to and highlight an N30. Press the F2 (Command) key. Use the Spacebar and Backspace key to cycle through the list until Archive appears. Press Enter.


Detailed Procedures The following procedures assume the N30 is already set up properly. If using a direct serial port connection from the PC to the N30, see the appropriate application note:

• Direct Connect and Dial-Up on Windows 98 Application Note (LIT-6893350)

• Direct Connect and Dial-Up on Windows NT Application Note (LIT-6893400)

• Direct Connect and Dial-Up on Windows 2000 Application Note (LIT-6893450)

If connecting to the N30 through an Ethernet Local Area Network (LAN), also see the N30 Supervisory Controller Networking Technical Bulletin (LIT-6891300).

Logging On to an N30 To log on to an N30: 1. Start your VT100 Emulator or turn on your VT100. 2. Press Enter when the N30 name appears at the top of the screen.

The Login screen appears (Figure 3-3).

Figure 3-3: N30 Login Screen in a VT100


3. Type your Login ID and press Enter. 4. Type your password and press Enter. The Main N30 screen

appears (Figure 3-4). Notes: The default Login ID is ADMIN.

The default password is 2468. The password is case sensitive.

We strongly recommend that the site administrator change the default password immediately and create Operator objects for editing the site.

Figure 3-4: N30 Main Screen After Logging In

Checking the Firmware Version Level of an N30 To check the firmware version number of an N30: Note: These steps are performed using a VT100 Terminal or

VT100 Terminal Emulator on a PC.

1. Browse to and highlight the N30 you want to check (for example, B7F3N01 in Figure 3-5).


Figure 3-5: N30 Screen after Logging in Through VT100 Terminal 2. Press Enter. The local attributes screen appears (Figure 3-6). The

firmware version level is on the right side under engineering values.

Figure 3-6: N30 Local Attributes Screen


Setting the Date and Time Note: The date and time defined for a site can be changed from any

of the configured N30 devices. When date or time is changed at one N30 device, the change is automatically sent to all other N30 devices on the site.

To set the date and time: 1. From the Main screen (Figure 3-4), use the arrow keys to

highlight an N30 (for example, N30P497). 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar or the Backspace key to cycle through the list

until the Set Time or Set Date command appears. 4. Use the arrow keys or Tab key to highlight the Value field. 5. Edit the value as necessary, using the number keys to set the

numbers and the Spacebar to scroll through the months. 6. Press Enter.


Editing the Attributes of an N30 To edit the attributes of the N30: 1. From the Main screen (Figure 3-4), use the arrow keys to

highlight an N30. 2. Press Enter to open the object (Figure 3-7).

Figure 3-7: Open N30 Device Object Note: When an object is opened, an object information line appears

beneath the alarm/site information display area. The information that appears, from left to right, includes: object name (B7F3N01), present value, and object status (Operational). Figure 3-7 only shows object name and object status as an N30 Device object does not have a present value.

3. Press the F3 (Edit) key. The first of two N30 Device object attribute screens appears (Figure 3-8).


Figure 3-8: N30 Device Object Attribute Screen 4. Use the arrow keys to move the cursor to the field that you want

to edit. The ] and [ keys are used to see additional pages of attributes.

5. Edit the values. The acceptable values for each field are described in the User Assistance line at the bottom of the screen. For more information about the attributes of the N30 Device object, refer to the N30 Device (LIT-694610) object chapter of the Object Dictionary.

6. Press the F3 (Save) key to save changes or the F4 (Cancel) key to cancel the changes.


Browsing an N30 Database with a VT100 This example illustrates how to browse an N30 database in a VT100 by describing how to view the attributes of an N2 Analog Output (AO) object. To browse an N30 database: 1. From the Main screen (Figure 3-4), use the arrow keys to

highlight an N30. 2. Press the Spacebar to expand the list of containers (Figure 3-9). Note: The content of the list depends on the database. The

examples in this chapter use the containers of the default N30 database.

Figure 3-9: Expanded N30 Container List 3. Select the N2 container. 4. Press the Spacebar to expand the list of objects. 5. Use the arrow key to highlight the Controller object where the

N2 object is located. In this example, it is UNT {1}. 6. Press the Spacebar to expand the list of N2 objects in the UNT

Controller object (Figure 3-10).


Figure 3-10: Expanded List of Objects in the UNT 7. Use the arrow keys to highlight the N2 AO object. In this example,

we want to see the attributes of the Heating Setpoint (SP). 8. Press the Enter key to open the object (Figure 3-11).

Figure 3-11: Open N2 AO Object


Adding Objects with a VT100 This section describes how to add objects using a VT100. Adding objects using Project Builder software is simply a matter of dragging the desired objects from the N30 library to the appropriate container in your database, defining their attributes, and downloading to the N30. See the Project Builder User’s Guide for more details. Note: Most objects require that certain attributes be defined for

them to be valid. Refer to the Object Dictionary for details.

To add objects with a VT100: 1. Browse to and highlight an N30. 2. Press the Spacebar to expand the list of object containers

(Figure 3-9). 3. Browse to and highlight the container or object where you want to

add an object (for example, the UNT in Figure 3-10). See Table 3-1 for a list of the objects that can be added to each container type.

4. Press the F3 (Add) key. A list of objects that can be added at that point appears (Figure 3-12).

Note: The Add Objects list changes according to what is selected when the F3 (Add) key is pressed (see Table 3-1).

Figure 3-12: Add Object Screen


5. Select the type of object to add. 6. Press Enter. The attribute screen for the selected object appears. 7. Fill in the fields using the information in the Object Dictionary or

the appropriate chapter in this manual. Point mapping information is in the N30 Supervisory Controller Point Mapping Technical Bulletin (LIT-6891400).

8. Press the F3 (Save) key.

Editing Objects with a VT100 Editing objects using the VT100 requires browsing to the object, opening the object, and modifying the attributes as desired. Editing objects using Project Builder software is similar in that the object must be browsed to and opened to modify it. However, in Project Builder, objects are edited in the M-View interface, allowing standard windows features such as drop-down lists. For more information, see the Working with Objects and the M-View Screen (LIT-693230) chapter in the Project Builder User’s Guide. To edit objects: 1. Browse to and highlight an object. 2. Press Enter to open the object. Note: Additional attributes appear after an object is created. For

complete lists of attributes for each object, refer to the Object Dictionary.

3. Press the F3 (Edit) key. The attribute screen for that object appears (Figure 3-13).

4. Use the arrow keys to move the cursor to a field and edit as desired. The User Assistance lines at the bottom of the screen provide help on the range of values or types of information that can be entered in the selected field. For example, in Figure 3-13, with the Change-of-Value (COV) Increment field selected, the User Assistance line shows that the number entered must be greater than or equal to 0 to be valid for that field.

5. If an attribute shows a number of items rather than a value (for example, [7] Items) move the cursor to the field, then press the Enter key to open the list. The number in brackets indicates the number of items that may be edited when that field is opened.

Note: After editing the items, press the F4 (Back) key to return to the previous screen.

6. Press the F3 (Save) key.


Figure 3-13: N2 AO Object Attribute Screen

Commanding Objects To command objects, the N30 device with the objects you are commanding must be online. Therefore, you can command objects using a VT100 or an M-Series Workstation but not while using an offline tool such as Project Builder. To command objects: 1. Browse to and highlight an object. 2. Press the F2 (Command) key. The Command field appears

(Figure 3-14).


Figure 3-14: Command Field 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. In this example, the Override command is available for the Rooftop Unit N2 Binary Output object.

4. If the desired command appears with additional parameters below it, press the Tab key to highlight the field, and either type in the necessary information or use the Spacebar and Backspace key to cycle through the list of options.

5. Press Enter.

Displaying a Summary To display a summary: 1. Browse to and highlight the Summary container. 2. Press the Spacebar to expand the list of Summaries. 3. Highlight a Summary. 4. Press the F2 (Command) key. 5. Use the Spacebar and Backspace keys to cycle through the list

until the Display command appears (Figure 3-15).


Figure 3-15: Summary Command Screen 6. Press Enter. The Summary Display screen appears (Figure 3-16).

Figure 3-16: Summary Display Screen


Printing a Summary To print a summary: 1. Browse to and highlight the Summary container. 2. Press the Spacebar to expand the list of Summaries. 3. Highlight a Summary. 4. Press the F2 (Command) key. 5. Use the Spacebar and Backspace keys to cycle through the list

until Print appears (Figure 3-17). 6. Use the arrow keys or Tab key to highlight the Destination field. 7. Use the Spacebar and Backspace keys to cycle through the list

until the desired printer appears. 8. Press Enter.

Figure 3-17: Print Summary Command


Changing an IP Address Notes: Before performing the following steps, have the necessary

Internet Protocol (IP) Addresses available. If the network uses Bootstrap Protocol (BOOTP), you can allow the N30 to obtain its own IP address by setting its BOOTP Enabled attribute to true and by configuring the BOOTP server to assign an IP address. See the N30 Device (LIT-694610) chapter in the Object Dictionary and the N30 Supervisory Controller Networking Technical Bulletin (LIT-6891300) for more information.

To change an IP address using a VT100: 1. Browse to and highlight an N30. 2. Press Enter to open the N30 Device object. Figure 3-7 shows the

N30 Device object named South Building after it has been opened.

3. Press the F3 (Edit) key. The first of two N30 Device object attribute screens appears (Figure 3-8).

4. Use the arrow keys to move the cursor to IP Address. 5. Press Enter. The IP Address list appears (Figure 3-18).

Figure 3-18: N30 IP Address List


6. Type in the address for your network in the four fields. 7. Press the F4 (Back) key. 8. Repeat steps 5 through 7 for the IP Mask and IP Router addresses. 9. Press the F3 (Save) key. 10. Press any key to continue. 11. Press the F4 (Cancel) key to return to the container hierarchy. Note: The status field for the device should now show

Reset Needed (Figure 3-19). The South Building N30 Device object has just had its IP address changed.

Figure 3-19: N30 Requiring Reset 12. Press Q to quit the N30. 13. Warm start the N30 to reset.


Rebinding a Site To rebind a site: 1. Browse to and highlight an N30. 2. Press Enter to open the N30 Device object. 3. Press the F2 (Command) key. 4. Use the Spacebar and Backspace key to cycle through the list until

Rebind Site appears. 5. Press Enter.

Changing Device Names To change device names for the N30s: 1. Browse to and highlight an N30. 2. Press the Enter key to open the N30 Device Object. 3. Press the F3 (Edit) key. 4. Use the arrow keys or Tab key to highlight the Name field. 5. Type in the new device name. 6. Press the F3 (Save) key. 7. Press any key to continue.

Archiving the Current Database Note: The N30 automatically archives the memory database to

Flash memory at 12:02 a.m. (just after midnight) and after a download. The Archive command is provided for special circumstances and should not be used regularly.

To archive the current database in an N30 to Flash memory: 1. After logging in, browse to and highlight an N30. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and Backspace key to cycle through the list until

Archive appears. 4. Press Enter.



Chapter 4 Working with Operator ObjectsT

Introduction Before new users can log into and access an N30 site, an Operator object must first be defined for each user. The Operator object dictates password and login ID entry guidelines and specifies complete access privileges for each user. Only site administrators can create, modify, and delete this object. This chapter describes how to:

• add an Operator object

• edit an Operator object

• command an Operator object

• change any Operator password

• change the ADMIN password

• delete an Operator object


Key Concepts Operator Object

Added for each user in a site and configured according to the access the user needs or requires for certain object categories. For instance, a Security Guard’s Operator object allows the viewing of Security objects, whereas the Building Manager’s Operator object allows the adding and deleting of HVAC objects.

Administrator The only user of a site with the ability to create, modify, or delete operator objects. With the exception that the administrator cannot change an Operator password after its initial creation, the administrator has unrestricted access to and control over all other objects defined for the site. The administrator’s Login ID is ADMIN and the default password is 2468. The user assigned it is responsible for changing the administrator password for their site and keeping it recorded in a secure place. Because an administrator is the only user with access to Operator objects, he or she is the only user who can issue commands, such as Enable and Disable, to these objects.

Site Manager Device The device in a site that contains the master Site object. The master Site object synchronizes all global objects.

Copy Holder Device Thie device that maintains copies of Redundant objects within each site. The Copy Holder device name is an attribute of the Site Data object.


Global Objects Objects duplicated at each site-configured device. The master, stored on the Site Manager device, is recorded complete with object name. The copies of each global object are disseminated to all other N30 devices, but without an object name. The Site Data and two administrative Operator objects are global objects. Users can neither create additional global objects nor remove any entries from any pre-defined set of global objects. The Site Manager device is responsible for ensuring that attribute values associated with all global objects are synchronized across all devices. Changes can be made only to the named global objects maintained on the Site Manager device.

Redundant Objects Objects for which a copy is maintained for each object instance. The master or named instance is loaded into a specified host device. The copy is automatically copied to the Copy Holder device where it is retained as a backup in case a host device goes offline or becomes inoperable. All non-administrative Operator objects fall into this classification.

User Access Feature A feature that establishes and maintains a core access capability, which can be expanded to meet increasing levels of sophistication. A site can range from a single VT100 configured N30 device to one consisting of fifty networked N30 devices (or ten N31s). As such, the User Access feature focuses on these primary objectives: 1. Identify legitimate users and grant each an access level based on

his or her role and site responsibilities (via the configuration of the Operator object).

2. Ensure that all devices can be accessed by at least a few operators at all times (even if network communications between N30 devices is not functioning).

• A copy of the administrator Operator object is added or downloaded to the Site Manager device and then distributed to each of the site’s N30 devices.

• By maintaining copies in each N30, the administrator is essentially guaranteed access to all objects on the site, even during a network breakdown. During such a disruption, the administrator must be physically logged into the N30 device containing the object to be accessed using a VT100 Terminal.


3. Minimize the chance of users losing their ability to log into a site due to a single N30 device breakdown.

• Designating one of the N30 devices on the site as the Copy Holder device ensures the maintenance of a copy of each non-administrative Operator object defined in the site.

• A user attempting to log in whose Operator object resides in a non-operational N30, automatically has his or her login ID and password entry verified against the copy of his Operator object maintained in the site’s Copy Holder device.


Guidelines for Defining User Access Table 4-1 provides guidelines for defining user access.

Table 4-1: Guidelines for Defining User Access Guideline Description Assigning Objects to Object Categories

• When created, all objects are defaulted to the HVAC object category. Access to objects intended for special applications (such as fire or security) can be easily restricted.

• Objects that require greater restrictions should be segregated into one of the other categories (Fire, Security, Services, or Administrative).

• Only the user intended to have access to these objects should be granted any level of access to these categories.

Understanding the User Login Validation Process

When the user logs into a VT100 equipped N30 device, the user’s Login ID and Password entries are compared against those defined in each of the site’s Operator objects. This search and comparison process consists of the following steps. 1. The entries are compared against the administrator Operator object, which

is locally maintained within each site’s configured N30 devices. 2. If no match is found, the entries are compared against each

non-administrator Operator object maintained within the N30 device that the user is using to log into the site.

3. If no match is found, the entries are compared against each copy of all the Operator objects defined for the site. This activity is performed by the Copy Holder device.

4. If the Copy Holder device is offline or is undefined, all N30 devices are queried to determine which (if any) of the devices has an Operator object through which the user entries can be validated.

5. If no match is found by the end of this validation sequence, the user is denied access.

Assigning Operator Objects to N30 Devices (see Figure 4-1)

In a fully operational site, an Operator object can reside anywhere. However, in practice, you can take steps to help minimize the chances that an offline N30 or a faulty communications network could prevent a legitimate operator from successfully logging into a site. In sites with one VT100 Terminal, locate all Operator objects within the N30 device that the VT100 is interfaced to, if enough memory is available. Following this guideline, the possibility of a required Operator object being located in an offline N30 is negated. In sites consisting of two VT100-equipped N30 devices, locate all Operator objects within either of these N30 devices. Note in the next section that one N30 should be the Site Manager and the other N30 should be designated the Copy Holder device. In sites equipped with more than two VT100 interfaces, locate each Operator object within the VT100-equipped N30 that the operator is most apt to use routinely.



Guideline (Cont.) Description Designating Site Manager and Copy Holder Devices (see Figure 4-1)

Site Manager Configuration: Unless there is a reason for not doing so (available memory, etc.), designate a VT100-equipped N30 device to be the Site Manager. Copy Holder Configuration: Unless there is a reason for not doing so (available memory, etc.), designate a Copy Holder as follows: • For a standalone configuration, Copy Holder designation is not required. • For a single VT100 and multiple N30 devices, any device can be

designated Copy Holder as long as all Operator objects have been loaded into the single VT100 equipped N30 device.

• For multiple VT100s, direct the Copy Holder designation to one of the other VT100-equipped N30 devices. Since the Copy Holder retains a copy of each Operator object defined for the site, login access attempted through this device is virtually guaranteed to any legitimate operator.


VT 100

Site Manager

N30

Standalone N30 Configuration

Multiple N30 Configuration with Single VT100 Monitor

VT 100

Site Manager

N30

Copy Holder

N30 N30

N30

VT 100

Site Manager

N30

Copy Holder

VT 100

N30

Multiple N30 Configuration with Two VT100 Monitors

VT 100

Site Manager

N30

VT 100

Copy Holder

N30N30

VT 100

Multiple N30 Configuration, Each with a VT100 Monitor

SiteCopy

Figure 4-1: Site Manager/Copy Holder Designations


Attributes The values of an object’s attributes determine how the object operates. The Operator object attributes described below are listed in the order that they appear on the screen. For additional information about the Operator object and its attributes, refer to the Object Dictionary.

Object Name Identifies the object on the user interface. For the Operator object, the Login ID is the object name.

Description Provides optional information to further describe the object.

Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Operator.

Object Category Determines the general classification of an object to help define user access capability and message routing.

Enabled Determines whether the user associated with a specific Operator object can log on to the site. True indicates that the user can log on to the site; False indicates that a user cannot log on to the site.

Password Determines the password that a specific user must enter to log on to the site. The Password must be a number of characters equal to or greater than the Minimum Password Length defined for the site by the Site Data object. The Password is case sensitive.

User ID Appears as a string output on a printed status report and identifies the user that has acknowledged an alarm.

Login ID Determines the Login ID that a specific user must enter to log on to the site. The Login ID may be up to 32 characters long.

IMPORTANT: As of Release 2.0, the Login ID is case sensitive.


User Group Determines which Group object (if any) appears directly under the main container on the main N30 screen. Once the Group is added to the Group container, the exact name of a Group object must be entered in the User Group field of an Operator object, in order for that Group object to appear directly under the main container whenever that user logs in. For more information regarding User Group, refer to the Working with Group Objects (LIT-6892060) chapter of this document.

Timeout Indicates the amount of time that must elapse before a VT100 session expires due to no keyboard activity.

Acknowledge Specifies if the user has the ability to recognize alarm reports. Alarm reports may be routed to terminals being used.

Display Units Defines which units are used for display when the operator is logged in.

User Capability Dictates the user’s relative degree of access, such as Configure, Modify, etc., for each of the site’s five object categories. The five object categories for which the user must have an access level defined are identified in Table 4-2. Since non-administrative users have no access to objects in the Administrative category, the entry for this category defaults to No Access, and the Administrative field is not accessible from the VT100. The administrator receives a default access level of Configure to all five object categories.

Table 4-2: Object Categories Category Description HVAC Categorizes an object as relating to Heating, Ventilating and

Air Conditioning functions. Fire Categorizes an object as relating to Fire functions. Security Categorizes an object as relating to Security functions. Services Categorizes an object as relating to Services functions. Administrative Categorizes an object as relating to Administrative functions.

Only Operator objects can be categorized as Administrative and only the site administrator can access these objects.


For each of the five object categories identified above, a user must be assigned (through the User Capability attribute of the Operator object) one of the seven access levels defined in Table 4-3. These access levels represent the degree of functional capability a user has when accessing objects assigned to the object category. A user receives all capabilities defined at the assigned level and below.

Table 4-3: Access Levels Access Level Description Configure Can create, add, delete, upload, and download. Modify Can release, release all, change attributes, enable, and

disable objects. Supervise Can override at Command Priority 8 (Operator Override). Intervene Can set time and date, declare points Out of Service,

Lock/Unlock loads, and Cancel Timer. Operate Can start, stop, adjust, etc., at Command Priority 16 (Default). View Can only view attribute details. No Access Can see the object listed on the browser but not the details.

As an example, one user may be granted a Configure access level to objects categorized as HVAC but only given a View access level to objects categorized as Security, and No Access to objects assigned to the Fire, Security, or Administrative object categories. Another more experienced user may be granted the ability to Configure objects in all four of the categories – HVAC, Fire, Security, and Services.

Operator Object Example Figure 4-2 is an example of the flexibility of Operator objects. This example illustrates the following:

• The Login ID entry was kept short by using just the user’s first name and the initial of the last name. To ensure clarity, the user’s full name was entered in the Description field.

• The User Group reference tailors the user interface to the user’s specific needs. For more information, refer to Working with Groups (LIT-6892060) in this manual.

• Careful consideration to User Capability ensures that the user is granted the appropriate access level to the four object categories accessible to non-administrator operators.

• The login ID becomes the name of the defined Operator object.


Figure 4-2: Operator Object Example


Procedure Overview Table 4-4: Working with Operator Objects To Do This Follow These Steps: Add an Operator Object Browse to and highlight the Operators container. Press the F3 (Add) key.

Highlight Operator and press Enter. Fill in the fields using Table 4-5. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Operator Object Browse to and highlight an Operator object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 4-5. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Operator Object Browse to and highlight an Operator object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Changing Any Operator Password

Log on to the N30 using the login ID and password of the user whose password is to be changed. Browse to and expand the Operators container. Highlight the Operator object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until Change Password appears. Press Enter to move to the next field. Pressing the Tab or down arrow key also moves the cursor to the next field. In the New Password field, type a new password. Press Enter to move to the next field. Type the password again in the Confirm New Password field. Press Enter.

Change the ADMIN Password Log on to the N30 using the ADMIN login ID and password. In the N30 device object designated as the Site Manager, expand the Internals container. Highlight the Operator object named site name.Operator {1}. Press Enter to open the object. Press the F2 (Command) key. Press Enter to move to the next field. Pressing the Tab or down arrow key also moves the cursor to the next field. In the New Password field, type a new password. Press Enter to move to the next field. Type the password again in the Confirm New Password field. Press Enter.

Delete an Operator Object Browse to and highlight an Operator object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Operator Object

Note: The Administrator of the site is the only user who can add an Operator object.

To add an Operator object: 1. Browse to and highlight the Operators container. 2. Press the F3 (Add) key. The Add Objects list appears. 3. Highlight Operator and press Enter. The Operator object attribute

screen appears (Figure 4-3).

Figure 4-3: Operator Object Attribute Screen 4. Fill in the fields using Table 4-5.


Table 4-5: Attribute Entry Requirements Screen Area

Attribute Required Default Options/Range

Object Object Name No Blank Determined by the Login ID. Description No Blank Maximum 40 characters Object Type Yes Operator Default is preset and cannot be changed. Object Category Yes Administrative

All other Operator objects have the default HVAC.

Use the Spacebar and Backspace key to view and select options: HVAC, Fire, Security, Services, Administrative.

Enabled Yes True Use the Spacebar and Backspace key to view and select options: True, False.

Login ID Yes Blank Maximum 32 characters This entry identifies the object in the container hierarchy. It is recommended to keep this entry as short as possible because the user must type this in for each login.

Password Yes Blank Maximum 8 characters The Password is case sensitive.

User ID Yes Blank 1 to 8 characters User Group No Blank Maximum 32 characters Timeout No 60 Minimum value = 1

Maximum value = 1440 Units = minutes

Acknowledge No True Use the Spacebar and Backspace key to view and select options: True, False.

Display Units Yes Imperial Units Imperial Units SI Can Units SI Eur Units

HVAC Yes Operate Fire Yes No Access Security Yes No Access

User Capability

Services Yes No Access

Use the Spacebar and Backspace key to view and select options: No Access, View, Operate, Intervene, Supervise, Modify, or Configure.

5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save

was successful or if there were errors. If errors were detected, correct them and resave the entries. Once the save is successful, continue with Step 7.

7. Press any key to continue. 8. Press the F4 (Cancel) key to return to the container hierarchy.


Editing an Operator Object Note: The Administrator of the site is the only user who can edit an

Operator object.

To edit an Operator object: 1. Browse to and highlight an Operator object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Operator object attribute screen

appears (Figure 4-3). 4. Edit the fields using Table 4-5. 5. Press the F3 (Save) key to save the changes. 6. Check the User Assistance area of the screen to verify if the save


7. Press any key to continue. 8. Press F4 (Cancel) to return to the container hierarchy.

Commanding an Operator Object To command an Operator object: 1. Browse to and highlight an Operator object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Operator object supports the commands described in Table 4-6.

Table 4-6: Operator Object Commands Command Description Enable Allows the user to log on and access the site according to the

user access levels defined by the Operator object. Disable Prevents the user from logging on to the site.

4. Press Enter.


Changing Any Operator Password Note: Administrative and non-administrative Operator objects are

maintained in different locations.

To change any Operator password: 1. Log on to the N30 using the login ID and password of the user

whose password is to be changed. This is the only way the Change Password command is available.

2. Browse to and expand the Operators container. 3. Highlight the Operator object. 4. Press the F2 (Command) key. The Command field appears. 5. Use the Spacebar and the Backspace key to cycle through the list

until Change Password appears. 6. Press Enter to move to the next field. Note: Pressing the Tab or down arrow key also moves the cursor to

the next field.

7. In the New Password field, type a new password. 8. Press Enter to move to the next field. 9. Type the password again in the Confirm New Password field. 10. Press Enter.

Changing the ADMIN Password Note: Administrative and non-administrative Operator objects are

maintained in different locations.

To change the ADMIN password: 1. Log on to the N30 using the ADMIN login ID and password. This

is the only way the Change Password command is available. 2. In the N30 device object designated as the Site Manager, expand

the Internals container. 3. Highlight the Operator object named site name. Operator {1}. For

example, BROWN DEER. Operator {1} (Figure 4-4).


Figure 4-4: SITE NAME.Operator {1} 4. Press Enter to open the object. 5. Press the F2 (Command) key. The Command field appears with

only the Change Password available. 6. Press Enter to move to the next field. Note: Pressing the Tab or down arrow key also moves the cursor to

the next field.

7. In the New Password field, type a new password. 8. Press Enter to move to the next field. 9. Type the password again in the Confirm New Password field. 10. Press Enter.

Deleting an Operator Object Note: The Administrator of the site is the only user who can delete

an Operator object

To delete an Operator object: 1. Browse to and highlight an Operator object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 5 Working with VT100 ObjectsT

Introduction The VT100 object is a representation of the VT100 user interface. One VT100 object exists in each new N30 by default. This makes it possible for every N30 to have a VT100 directly attached to it. A user cannot add additional or delete existing VT100 objects via a VT100; however, the VT100 object can be edited for the filtering of messages as desired. Additional VT100 objects can be added to a database using Project Builder software. This chapter describes how to edit a VT100 object.


Key Concepts VT100 Object

The VT100 object performs three primary functions:

• provides the means for users to observe VT100 data and status, and identify it as a target device for alarms and summaries.

• handles unsolicited messages directed from objects, such as alarm messages and Summaries.

• supports the relationship to the Serial Datalink object that manages dial connections and line status conditions.

The VT100 object provides support for VT100 Terminals as well as VT100 Terminal Emulators running on a standard computer. The VT100 object’s attributes allow a user to configure a variety of filters that establish the type of messages, or Status Notification Reports (SNR), which the VT100 object receives. For more information about determining filter configurations, refer to Appendix B: Building a Message Router Application (LIT-6892320) in this document.

Attributes The values of an object’s attributes determine how the object operates. The VT100 object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 5-2. For additional information about the VT100 object and its attributes, refer to the Object Dictionary.

Object Name Identifies the object on the user interface.


Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or VT100.



Active Filter Selects the type of filtering in effect for this VT100 destination. The filter types are as follows:

• Pass None - When selected, this destination receives no alarm messages.

• Pass All - When selected, this destination receives all alarm messages.

• Filter A - This destination receives alarm messages based on settings of Filter A.

• Filter B - This destination receives alarm messages based on settings of Filter B.

• Filter A and B - This destination receives alarm messages based on settings of Filter A and B.

Priority Filter A Defines which priorities the destination receives when Filter A is in effect. A value of True for a particular selection means that messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, and Status.

Category Filter A Defines which categories of messages the destination receives when Filter A is in effect. This filter has no effect for alarm messages without a defined object category. A value of True for a particular selection means that messages of that defined object category reach this destination.

Msg Type Filter A Defines which types of messages the destination receives when Filter A is in effect. A value of True for a particular selection means that messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, and Alarm.

Priority Filter B Defines which priorities the destination receives when Filter B is in effect. A value of True for a particular selection means messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, and Status.


Category Filter B Defines which categories of messages the destination receives when Filter B is in effect. This filter has no effect for alarm messages without a defined object category. A value of True for a particular selection means that messages of that defined category reach this destination.

Msg Type Filter B Defines which types of messages the destination receives when Filter B is in effect. A value of True for a particular selection means that messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, or Alarm.

Port Number Identifies the port where the VT100 Terminal is connected.


Procedure Overview Table 5-1: Working with VT100 Objects To Do This Follow These Steps: Edit a VT100 Object Browse to and highlight the VT100 object. Press Enter to open the object.

Press the F3 (Edit) key. Edit the fields using Table 5-2. Move the cursor to the next field (Priority Filter A). Press Enter. Use the Spacebar and Backspace key to view and select True or False for the first available option. Press the down arrow key to move to the next option. Enter values for all of the options. Press F4 (Back) to return to the attribute screen. Edit all fields. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.


Detailed Procedures Editing a VT100 Object

To edit a VT100 object: 1. Browse to and highlight a VT100 object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary

for more information.

3. Press the F3 (Edit) key. The VT100 object attribute screen appears (Figure 5-1).

Figure 5-1: VT100 Object Attribute Screen 4. Edit the fields using Table 5-2.




Object Object Name No Blank The default is preset and cannot be changed. Description No Blank Maximum 40 characters Object Type Yes VT100 The default is preset and cannot be changed. Object

Category Yes HVAC Use the Spacebar and Backspace key to view and

select options: HVAC, Fire, Security, Services, Administrative.

Alarm Setup

Active Filter Yes Pass All Use the Spacebar and Backspace key to view and select options: Pass None, Pass All, Filter A, Filter B, Filter A and B.

Priority Filter A

Yes [4] Items Use the Spacebar and Backspace key to view and select True or False for the following values: Critical, Serious, Important, Status.

Category Filter A

Yes [5] Items Use the Spacebar and Backspace key to view and select True or False for the following values: HVAC, Fire, Security, Services, Administrative.

Msg Type Filter A

Yes [3] Items Use the Spacebar and Backspace key to view and select True or False for the following values: System Alert, Operator Transaction, Alarm.

Priority Filter B


Category Filter B


Msg Type Filter B


Notification Class

Enter an integer between 1 and 4194303.

Port Setup

Port Number Yes Port 1 The default is preset and cannot be changed.

5. Move the cursor to the next field (Priority Filter A). 6. Press Enter. The filter options appear. 7. Use the Spacebar and Backspace key to view and select True or

False for the first available option. 8. Press the down arrow key to move to the next option. 9. Repeat Steps 7 and 8 until values are chosen for all of the options. 10. Press F4 (Back) to return to the attribute screen. 11. Repeat Steps 5 through 10 while referring to Table 5-2 or the User

Assistance line, until all of the fields are edited as desired. 12. Press the F3 (Save) key.


13. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. If errors were detected, correct them and resave the entries. Once the save is successful, continue with Step 14.




Chapter 6 Working with Group ObjectsT

Introduction The Group object provides the user with the ability to customize the organization of objects within the site. This chapter describes how to:

• add a Group object

• edit a Group object

• add object references to a Group object

• delete object references from a Group object

• delete a Group object

• create a Site Group

• create a User Group


Key Concepts Group Object

An organizational tool that organizes and displays site information according to specific needs. For example, a Group object can display information by floors, sections, all zone temps, etc. These representations are independent of the devices themselves. This allows users to define site hierarchies differently than the default organization by N30 device. Groups can reference any object, collection of objects, or other groups. By referencing groups from inside of other groups a full or partial site hierarchy can be built. The flexibility of the Group object allows for multiple custom hierarchies defined for use by different users or different job functions. More than one Group object can reference a single object in the site. Multiple points in the hierarchy can access the same object information. Each object in the site, however, is not required to be referenced within a group. View, edit, and command objects in the groups using the same operations available for the other containers in the site hierarchy. If changes are made to an object from within the Group object, these changes are reflected in the object wherever it is accessed from. A total of 75 objects or groups can be added per group and up to seven consecutive levels of Group objects can be added within any other container or object or group.

Site Group The site can have a particular Site Group appear at the top level of the site hierarchy when any user logs in. First, add a Group object under the Group container. Then the name of this group is inserted into the Site Group Object field of the Site Data object. A Site Group contains any information important to a site and that needs to be easily accessed. Figure 6-1 shows an example of a Site Group named OVERVIEW GRP. This procedure is described in the Detailed Procedures section of this chapter.


Figure 6-1: Site Group Example in the Container Hierarchy

User Group Each user (operator) in the site can also have a personal group appear at the top level of the site hierarchy when he or she logs in. First, create a Group object in the Group container. Then reference the name of this group via the User Group attribute of the user’s Operator object. Creating a User Group allows users to customize their container hiearchy. For instance, a particular Facility Manager may need to check temperatures and setpoints on a daily basis. By creating a Group object containing this information (named Maintenance) under the Group container and then making sure to enter the name of this Group (Maintenance) in the User Group attribute field of the Facility Manager’s own Operator object, a group of vital information is created at the top of the container hierarchy that eliminates the need to browse any further after logging in. Figure 6-2 is an example of a User Group. This procedure is described in the Detailed Procedures section of this chapter. If both a User Group and Site Group are defined and that particular operator is logged in, the User Group appears first, and then the Site Group followed by the remainder of the site hierarchy. For more information about the Operator object, refer to the Working with Operator Objects (LIT-6892030) chapter of this document.


Figure 6-2: User Group Example in the Container Hierarchy

Attributes The values of an object’s attributes determine how the object operates. The Group object attributes described below are listed in the order that they appear on the user interface. For additional information about the Group object and its attributes, refer to the Object Dictionary.



Child List Consists of an object reference and a label string for display. The object reference may refer to any object including another group. The optional label allows a shorter name to be used when displaying the members in the group. It is also intended to reflect the object’s meaning relative to the group that it is in. The label names within a given group must be unique from all other labels in that group.


Procedure Overview Table 6-1: Working with Group Objects To Do This Follow These Steps: Add a Group Object Browse to and highlight the Group container. Press the F3 (Add) key.

Highlight Group and press Enter. Fill in the fields using Table 6-2. Move the cursor to Child List. Press Enter. Type in the exact name of an object to be added to the new Group object. Press F3 (Add Item) to add a blank entry for another object. Press F4 (Back) key. Press F3 (Save) key to save the object. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Group Object Browse to and highlight a Group object. Press Enter to open the object. Press F3 (Edit) key. Move the cursor to Child List. Press Enter. Make any necessary changes (correct an object or label name). Press the F4 (Back) key. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Object References to a Group Object

Browse to and highlight a Group object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Child List. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in the exact name of an object to be added to the Group object. Press F3 (Add Item) to add a blank entry for another object. Press the F4 (Back) key. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Object References from a Group Object

Browse to highlight a Group object. Press Enter to open object. Press F3 (Edit) key. Move the cursor to Child List. Press Enter. Highlight either the Reference Name or Label of an object and press the F2 (Del Item) key. Press the F4 (Back) key. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete a Group Object Browse to and highlight a Group object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Child List. Press Enter. Press F2 (Del Item) key until all of the objects in the Child List are deleted. Press the F4 (Back) key. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the Delete key. Press the Tab key to confirm the deletion.

Create a Site Group In the Group container, add a Group object with the desired Child List members. Write down the name of this new group. Browse to and expand the Site Data object. Press the F3 (Edit) key. Move the cursor to the Site Group Object field. Type in the name of this new group. Press the F3 (Save) key. Press any key to continue. Log out and log in for the changes to take effect. Check the container hierarchy to verify that the Site Group appears.

Create a User Group In the Group container, add a Group object with the desired Child List members. Write down the name of this new group. Edit the appropriate Operator object by entering the exact name of this new group in the User Group field. Log out and log in the VT100 with the appropriate Login ID and Password for the edited Operator object. Check the container hierarchy to verify that the User Group appears.


Detailed Procedures Adding a Group Object

Note: When adding objects to a Group object it is helpful to have a list of the exact names of the objects to be added.

To add a Group object: 1. Browse to and highlight the Group container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Group and press Enter. The Group object attribute

screen appears (Figure 6-3):

Figure 6-3: Group Object Attribute Screen 4. Fill in the fields using Table 6-2.


Table 6-2: Attribute Entry Requirements Screen Area Attribute Required Default Options/Range

Object Name No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ’ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Group Object Category

HVAC

Object

Child List Yes 0 Items Object reference and optional label of 20 maximum characters

5. Move the cursor to Child List. 6. Press Enter. The Group object Child List appears (Figure 6-4).

Figure 6-4: Group Object Child List 7. Type in the exact name of an object to be added to the new Group

object. 8. If desired, type in a Label for that object. Note: If a Label is entered it appears in the container hierarchy

under the name of the Group object. Otherwise, the Reference name appears.

9. Press F3 (Add Item) to add a blank entry for another object.


10. Repeat Steps 7 through 9 for all objects to be added to the Group object.

11. Press the F4 (Back) key. 12. Press the F3 (Save) key to save the object. 13. Check the User Assistance area of the screen to verify if the save


14. Press any key to continue. 15. Press the F4 (Cancel) key to return to the container hierarchy. Note: Once a Group object is added, users can view and edit its

objects the same way they would view and edit objects in their original containers.

Editing a Group Object To edit a Group object: Note: To add object references to or delete object references from a

Group object, refer to the appropriate sections of this chapter.

1. Browse to and highlight a Group object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Group object attribute screen appears

(Figure 6-3). 4. If necessary, edit the Description field. 5. If only the Description field is edited, press F3 (Save) and

continue with Step 11. If the Child List is to be edited, continue with Step 6.

6. Move the cursor to Child List. 7. Press Enter. The Group object Child List appears (Figure 6-4). 8. Make any necessary changes (correct an object or label name). 9. Press the F4 (Back) key. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save




Adding Object References to a Group Object To add object references to a Group object: 1. Browse to and highlight a Group object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Group object attribute screen appears

(Figure 6-3). 4. Move the cursor to Child List. 5. Press Enter. The Group object Child List appears (Figure 6-4). 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in the exact name of an object. 8. If desired, type in a Label for that object. Note: If a Label is entered it appears in the container hierarchy

under the name of the Group object. Otherwise, the Reference name appears.

9. Press F3 (Add Item) to add a blank entry for another object. 10. Repeat Steps 7 through 9 for all objects to be added to the Group

object. 11. Press the F4 (Back) key. 12. Press the F3 (Save) key to save the changes. 13. Check the User Assistance area of the screen to verify if the save



Deleting Object References from a Group Object To delete object references from a Group object: 1. Browse to and highlight a Group object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Child List. 5. Press Enter. The Group object Child List appears (Figure 6-4). 6. Highlight either the Reference Name or Label of an object and

press the F2 (Del Item) key. 7. Repeat Step 6 for all objects to be deleted.


8. Press the F4 (Back) key. 9. Press the F3 (Save) key to save the changes. 10. Check the User Assistance area of the screen to verify if the save



Deleting a Group Object To delete a Group object: 1. Browse to and highlight a Group object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Child List. 5. Press Enter. The Group object Child List appears (Figure 6-4). 6. Press the F2 (Del Item) key until all of the objects in the Child

List are deleted. Note: All objects must be deleted from the Child List before the

Group object can be deleted.

7. Press the F4 (Back) key. 8. Press the F3 (Save) key to save the changes. 9. Check the User Assistance area of the screen to verify if the save


10. Press any key to continue. 11. Press the Delete key. 12. Press the Tab key to confirm the deletion.


Creating a Site Group To create a Site Group: 1. In the Group container, add a Group object with the desired Child

List members. Note: See Adding a Group Object in this chapter.

2. Write down the name of this new group. 3. Browse to and highlight the Site Data object. The Site Data object

appears at the top of the hierarchy. In Figure 6-1, the Site Data object is Brown Deer.

4. Press Enter to open the object. 5. Press the F3 (Edit) key. 6. Move the cursor to the Site Group Object field (Figure 6-5).

Figure 6-5: Site Group Object field – Site Data Object Attribute Screen 7. Type in the name of this new group. 8. Press the F3 (Save) key. 9. Press any key to continue. 10. Log out and log in for the changes to take effect. 11. Check the container hierarchy to verify that the Site Group

appears (Figure 6-1).


Creating a User Group To create a User Group: 1. In the Group container, add a Group object with the desired Child

List members. Note: See Adding a Group Object in this chapter.

2. Write down the exact name of this new group. 3. Edit the appropriate Operator object by entering the exact name of

this new group in the User Group field (Figure 6-6). Note: The Administrator of the site is the only user who can edit an

Operator object. See Working with Operator Objects (LIT-6892040) in this document for editing an Operator object

Figure 6-6: User Group Field - Operator Object Attribute Screen 4. Log out and log in the VT100 with the appropriate Login ID and

Password for the edited Operator object. 5. Check the container hierarchy to verify that the User Group




Chapter 7 Working with Schedule Objects

Introduction A Schedule object allows you to automate routine functions. For example, you can schedule a fan to start every weekday (Monday through Friday) at 7:00 a.m. and stop at 5:00 p.m. This chapter describes how to:

• create a new Schedule object

• edit a Schedule object

• delete a Schedule object

• command a Schedule object For information on creating and editing Schedule objects in Project Builder, see the Project Builder User’s Guide. For information on viewing and editing Schedules using M-Schedule, see the M-Schedule/M-Calendar User’s Guide.


Key Concepts Schedule Object

The Schedule object updates the attribute values of objects according to the time of day. The Schedule object allows for flexible selection of dates on which to run the Schedule. These times can be specified for days of the week and exception days. The exception days can be defined as specific dates, ranges of dates, or days for which a given Calendar object is defined. See Table 7-7 for a list of exception types. The Schedule object is compatible with the BACnet Schedule object. All required and optional attributes of the BACnet Schedule object are supported. Some proprietary attributes have been added to the N30 to extend the functionality of the Schedule object. The Schedule object is added to the Schedule container in an N30 database.

Attributes The values of an object’s attributes determine how the object operates. The Schedule object attributes described below are listed in the order that they appear on the screen. For additional information about Schedule object and its attributes refer to the Object Dictionary.

Object Name Identifies the object on the user interface. This is the name the user sees when viewing the database.


Object Type Indicates the type of object, such as Schedule, N2 Analog Input, or Calendar.


Enabled Indicates if the object is active and executing an operational condition.

N30 Supervisory Controller User’s Guide 7-3

List of Property References (List of Prop Refs) Lists attributes of objects, which are to be written at the scheduled times. The List of Prop Refs is a list of the objects and attributes that are scheduled using the Schedule object.

Weekly Schedule Contains one element for each day of the week, where element 1=Monday, 2=Tuesday, . . . 7=Sunday. Each element contains a list of the times and corresponding values for the Schedule object to write to the scheduled objects. The exception schedules override the times in this weekly schedule.

Exception Schedule Contains a list of exceptions to the times listed in the weekly schedule. The exceptions can be based on a specific date, a date range, a calendar reference, or a week/day selection. The Schedule object automatically deletes date or range type of exceptions that expired 31 days ago. All four types of exceptions also contain the times and corresponding values for the Schedule object to write to the scheduled objects on those exceptions. The exceptions are also prioritized 1 . . . 16, with 1 being the highest priority. If multiple exceptions apply for a given day, then the exception with highest priority is in effect. If multiple exceptions apply for the current day and have the same priority, then the first of these in the list is in effect. The week/day selection can be used to identify particular days of the week, months of the year, etc.

Effective Period Gives the range of dates that the Schedule object is active. By default, these dates are unspecified (blank), causing the Schedule object to be active for all days. Refer to Wildcard Date Fields in this chapter for further details.

Present Value Indicates the current value of the Schedule object. This is the value most recently written to a referenced object attribute, listed in the List of Prop Refs attribute. A blank Present Value field in a Schedule object indicates that the schedule has not reached a scheduled time since the object was created (or since the last device restart).


Dates Each date contains four fields: Day of Month, Month, Year, and Day of Week. These fields appear in the following format:

<Day of Month> <Month> <Year> <Day of Week> The values of the Day of Month and Day of Week fields cannot contradict each other or the date is not valid. For example, a date of 10 Apr 1999 Tuesday is invalid because April 10, 1999 is not a Tuesday. Also, the values of a date range (start date, end date) must be in chronological order or the date range is not valid. For example, a date range with a start date of 30 Aug 1999 Monday and an end date of 30 Jun 1999 Wednesday is not valid because August 1999 comes after June 1999.

Wildcard Date Fields Any unspecified date field is considered to be a wildcard date field.

Single Date For a single date, a wildcard opens a particular field to the full range of possible values for that field. Table 7-1 describes the meaning of a wildcard in each of the four date fields.

Table 7-1: Wildcard Date Field Meanings Unspecified Field Meaning Day of Month Every day of the month, unless a particular day of the

week is specified by the Day of Week field Month Every month Year Every year Day of Week Every day of the week, unless a particular day of the

month is specified by the Day of Month field

Table 7-2 shows some sample wildcard dates and their meanings.

Table 7-2: Sample Wildcard Dates Wildcard Date Meaning 01 * * Any day of the week The first day of every month, every year 12 Apr * Any day of the week April 12 of every year * Apr 1999 Any day of the week Every day in April 1999 * * * Any day of the week Every day * * * Monday Every Monday * * 1999 Monday Every Monday in 1999 * Apr 1999 Monday Every Monday in April of 1999 12 Apr 1999 Any day of the week Only on Monday, April 12, 1999 (same meaning as 4/12/99Mon)

* Indicates a blank field.


Date Range If the same field is a wildcard in both the start date and end date, the range from start to end is infinite, except as limited by the other date fields. The Day of Week field is only considered when it is specified for both the start date and the end date. Table 7-3 shows sample wildcard date ranges and meanings.

Table 7-3: Sample Wildcard Date Ranges Start Date End Date Meaning * * * Wednesday * * * Friday Every Wednesday, Thursday, and

Friday of every month, every year * * 1999 Wednesday * * 1999 Friday Every Wednesday, Thursday, and

Friday of every month in 1999 * Jun 1999 Wednesday * Aug 1999 Friday Every Wednesday, Thursday, and

Friday in June, July, and August in 1999

* Jun 1999 Any day of the week

* Aug 1999 * Every day in June, July, and August in 1999

30 Aug 1999 Any day of the week

* * * * Every day after August 30, 1999

10 * * Any day of the week

12 * * * The tenth, eleventh, and twelfth days of every month, every year

04 Jul * Monday 04 Jul * Friday Every July 4 that is a Monday, Tuesday, Wednesday, Thursday, or Friday, every year


Week and Day The Week and Day selection identifies a month, a week of the month, and a day of the week. The week of the month can be chosen as Any (every) week of month, Days 1-7, Days 8-14, Days 15-21, Days 22-28, Days 29-31, and the Last seven days. Table 7-4 shows some sample wildcard week and day exceptions.


Table 7-4: Sample Wildcard Week and Days Wildcard Date Meaning Month Week of Month Day of Week Any Any week of

month Any day of week Every day of the year

Any Days 1-7 Monday Monday of the first week of every month Jan Any week of

month Tuesday Every Tuesday in January

Feb Days 8-14 Any day of week Every day of the week in the second week of February Any Any week of

month Wednesday Wednesday of every week of every month

Mar Any week of month

Any day of week Every day of every week in March

Any Days 14-21 Any day of week Every day of the third week of every month Apr Days 22-28 Thursday Thursday in the fourth week of April Any Days 29-31 Any day of week Last three days of every month with 31 days Jun Last seven days Saturday Saturday in the last seven days of June

Time Changes When a time change occurs or the supervisory controller restarts, the Schedule object attempts to reissue the last value that should have been scheduled. It searches backwards through the time and value pairs for the current day to find the last scheduled time. If no times are found from midnight to the current time, then the latest scheduled value will be used. Changes in time due to Daylight Saving Time are also handled in this manner.


Procedure Overview Table 7-5: Working with Schedule Objects To Do This: Follow These Steps:

Add a Schedule object - Browse to and highlight the Schedule container. Press the F3 (Add) key. Highlight Schedule and press Enter. Fill in the fields using Table 7-6. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy. Add to a List of Prop Refs - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to the List of Prop Refs. Press Enter. In the Object Name field that is highlighted, type the exact name of the object to be scheduled. Press Enter. Move the cursor to the Attribute field for that object. Use the Spacebar and Backspace keys to cycle through the list of attributes until the desired attribute appears. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy. Add a Weekly Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Weekly Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle through the days of the week until the day you are scheduling appears. Press the F3 (Add Item) key. Enter the time/value pair in the fields displayed. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy. Add an Exception Schedule - In the Schedule container, highlight a schedule. Press Enter. Press the F3 (Edit) key. Move the cursor to the Exception Schedule field. Press Enter. Press the Add Item (F3) key. Move the cursor to Exception Type. Select an exception type . Enter values for Date and Priority. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Create a New Schedule Object

Set an Effective Period for an Object - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Effective Period and press Enter. Enter the starting and ending dates the Weekly schedule should be active. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Schedule Object Edit a List of Prop Refs - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to the List of Prop Refs. Press Enter. Highlight the Object Name that you want to edit. Type the exact name of the new object you want to schedule. Move the cursor to the Attribute field for that object. Use the Spacebar and Backspace keys to cycle through the list of attributes until the desired attribute appears. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.



To Do This (Cont.) Follow These Steps: Delete from a List of Prop Refs - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to the List of Prop Refs. Press Enter. Highlight the Object Name to delete. Press the F2 (Del Item) key. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy. Edit a Weekly Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Weekly Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle through and select the day of the week. Move the cursor to the time and value pairs. Edit the fields as desired. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy. Edit an Exception Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Exception Schedule and press Enter. Use the Spacebar or Backspace key to select an exception schedule. Highlight Exception Type. Cycle through the available exception types. Use the cursor to move to the other fields and edit as desired. Press the F4 (Back) key. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key. Add Time and Value Pairs to an Exception Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Exception Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle through and select the Exception Schedule where you want to add time and value pairs. Place the cursor on any of the fields that appear except the number of Exception Schedules. Press the F3 (Add Item) key. In the Time field, type the desired time. In the Value field, press the Spacebar or Backspace key to select On or Off. Press the F4 (Back) key. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key.

Edit a Schedule Object (Cont.)

Delete Time and Value Pairs from an Exception Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Exception Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle through and select the Exception Schedule where you want to delete time and value pairs. Place the cursor on a time and value pair. Press the F2 (Delete Item) key. Press the F4 (Back) key. Press the F3 (Save) key.

Commanding a Schedule Object

Browse to and highlight a Schedule object. Press the F2 (Command) key. Use the Spacebar and Backspace keys to cycle through the available commands. Press Enter. Delete a Weekly Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Weekly Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle through the days of the week. Move the cursor to each time and value pair. Press the F2 (Item Del) key for each time and value pair. Press the F4 (Back) key. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key. Delete an Exception Schedule - Browse to and highlight a Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to Exception Schedule and press Enter. Use the Spacebar and Backspace keys to cycle to the Exception Schedule that you want to delete. Press the Del Item (F2) key. Press the F4 (Back) key. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key.

Delete a Schedule Object

Delete a Schedule Object - Browse to and highlight a Schedule. Press Enter. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Creating a New Schedule

Creating a new schedule consists of adding a Schedule object, adding the objects and the attributes of those objects (List of Prop Refs) that you are scheduling, and then creating a weekly Schedule for those items. Additional tasks that can be part of creating a new schedule are adding exceptions to the schedule, and setting an effective period for the Schedule or the exceptions. All of these tasks are covered in this section, Creating a New Schedule.

To add a Schedule object: 1. Browse to and highlight the Schedule container. 2. Press the F3 (Add) key. The Add Objects list appears. 3. Highlight Schedule and press Enter. The Schedule object attribute


Figure 7-1: New Schedule Object Screen 4. Fill in the fields using Table 7-1.


Table 7-6: Attribute Entry Requirements Screen Area Attribute Required Default Options/ Range Object Object Name No Blank Maximum 32 characters

Invalid characters: @ . ? * $ # : ’ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Calendar The default is preset and cannot be

changed. Object

Category Yes HVAC Use the Spacebar and Backspace key to

view and select options: HVAC, Fire, Security, Services, Administrative.


List of Prop Refs

Yes [0] Items See the appropriate sections of this chapter.

Weekly Schedule


Exception Schedule


Scheduling Values

Effective Period




7. Press any key to continue. 8. Press the F4 (Back) key to return to the container hierarchy. Note: Now that you have a Schedule object you need to add the

objects to be scheduled. See Adding to a List of Prop Refs in this chapter.


Adding to a List of Prop Refs

IMPORTANT: All objects scheduled by a Schedule object must reside on the same N30. The first object in the List of Prop Refs determines which N30. The Schedule object itself may or may not be located on this N30.

Notes: Prior to adding to a List of Prop Refs you should have a list of the exact names of the objects that you are scheduling. A Schedule object can indirectly schedule objects on multiple N30s by scheduling a Multiple Command object, which commands objects on multiple devices. For more information, see the Working with Multiple Command Objects (LIT-6892170) chapter in this manual.

To add objects and attributes to a List of Prop Refs: 1. Browse to and highlight the Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to the List of Prop Refs. 5. Press Enter. The List of Prop Refs appears (Figure 7-2). 6. In the Object Name field that is highlighted, type the exact name

of the object to be scheduled. 7. If the object is valid, use the arrow or Tab key to move the cursor

to the attribute field. If the object name is invalid, you receive an Object not found message. If you receive this message you must retype a valid object name.

8. Use the Spacebar and Backspace keys to cycle through the list of attributes until the desired attribute appears. The default value is Present Value.


Figure 7-2: List of Prop Refs 9. Press the F3 (Add Item) key to add a blank entry for an additional

object and attribute. 10. Repeat Steps 6 through 10 for each object being added to the List

of Prop Refs. 11. Press the F4 (Back) key. 12. Press the F3 (Save) key. 13. Check the User Assistance area of the screen to verify if the save


14. Press any key to continue. 15. Press the F4 (Back) key to return to the container hierarchy.

IMPORTANT: Once you save entries in the List of Prop Refs, you can no longer edit the first entry in the list (the object device). You cannot change an existing Schedule object to schedule points on a different N30; you must delete the entire schedule and add a new one.


Adding a Weekly Schedule To add a Weekly Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to the Weekly Schedule. 5. Press Enter. A new Weekly Schedule screen appears (Figure 7-3). Note: You cannot add a weekly schedule unless there is something to

be scheduled in the List of Prop Refs.

Figure 7-3: Weekly Schedule Screen 6. Use the Spacebar and Backspace keys to cycle through and select

the day of the week for the schedule entry. 7. Press the F3 (Add Item) key. 8. Add the time/value pair in the fields displayed. Press the Tab key

to move between the Time and Value fields. 9. To add another entry, repeat Steps 6 through 8. 10. Press the F4 (Back) key to return to the previous screen. 11. Press the F3 (Save) key.




Adding an Exception Schedule To add an Exception Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to the Exception Schedule field. 5. Press Enter. The Exception Schedule appears (Figure 7-1).

Figure 7-4: Schedule Object Exception Schedule 6. Press the Add Item (F3) key. The Exception Schedule screen

appears. 7. Use the Spacebar and Backspace keys to cycle through the

Exception Type options (Table 7-7).


Table 7-7: Exception Schedule Types Exception Type Setting Single Date Enter the date to run the Exception schedule instead of the current schedule. Date Range Enter the range of dates to run the Exception schedule instead of the current schedule. Week and Day Enter a recurring week and day of the month to run the Exception schedule instead of

the current schedule. Calendar Ref Enter a reference to an existing Calendar object that determines the dates to run the

Exception schedule instead of the current schedule. This exception must be a valid Calendar object name.

8. Use the Tab or arrow keys to move to the remaining fields. Either

type in all values, or use the number keys to enter dates and the Spacebar and the Backspace key to change days and months.

Note: Pressing the F3 (Add) key at this point adds Time and Value pairs to the Exception Schedule. Information on adding and deleting Time and Value pairs is under the Editing Schedule Objects section of this chapter.

9. Repeat Steps 6 through 8 for each new Exception Schedule. 10. Press the F4 (Back) key to return to the previous screen. 11. Press the F3 (Save) key. 12. Check the User Assistance area of the screen to verify if the save



Setting an Effective Period for a Schedule Object To set an Effective Period for a Schedule object: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Effective Period. 5. Press Enter. The Effective Period screen appears (Figure 7-5).


Figure 7-5: Effective Period Screen 6. Enter the starting and ending dates the Weekly schedule should be

active. Use the number keys to enter dates and the Spacebar and the Backspace key to change days and months.

7. Press the F4 (Back) key to return to the previous screen. 8. Press the F3 (Save) key. 9. Check the User Assistance area of the screen to verify if the save


10. Press any key to to continue. 11. Press the F4 (Cancel) key to return to the container hierarchy.

Editing Schedule Objects Note: Editing a Schedule can include editing the objects and the

attributes of those objects (List of Prop Refs) that you have already scheduled, editing a weekly Schedule for those items, editing exceptions to the schedule, and editing the effective periods of the various schedules.


Editing a List of Prop Refs

IMPORTANT: When entries are put in the List of Prop Refs and saved, you can no longer edit the first entry in the list (the object device). You cannot change an existing Schedule object to schedule points on a different N30; you must delete the entire schedule and add a new one.

To edit a List of Prop Refs: 1. Browse to and highlight the Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to List of Prop Refs. 5. Press Enter. The List of Prop Refs appears (Figure 7-2). 6. Highlight an Object Name that you want to edit. 7. In the Object Name field that is highlighted, type the exact name

of the object to be scheduled. 8. If the object is valid, use the arrow or Tab key to move the cursor

to the attribute field. If the object name is invalid, you receive an Object not found message. If you receive this message, you must retype a valid object name.

9. Use the Spacebar and Backspace keys to cycle through the list of attributes until the desired attribute appears. The default value is Present Value.





Deleting from a List of Prop Refs To delete from a List of Prop Refs: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to the List of Prop Refs. 5. Press Enter. The List of Prop Refs appears (Figure 7-2). 6. Highlight the Object Name to delete. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each object you want to delete. 9. Press the F4 (Back) key. 10. Press the F3 (Save) key. 11. Check the User Assistance area of the screen to verify if the save



Editing a Weekly Schedule To edit a Weekly Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Weekly Schedule. 5. Press Enter. The Weekly Schedule screen appears (Figure 7-6).


Figure 7-6: Weekly Schedule with Time and Value Pair 6. Use the Spacebar or the Backspace key to select the day of the

week that contains the schedule you want to change. 7. Use the arrow or Tab keys to move the cursor to a time and value

pair that you want to edit. 8. Edit the fields as desired. 9. Press the F3 (Add) key to add Time and Value pairs to the weekly

schedule. 10. To change another schedule, repeat Steps 6 through 9. 11. Press the F4 (Back) key to return to the previous screen. 12. Press the F3 (Save) key. 13. Check the User Assistance area of the screen to verify if the save




Editing an Exception Schedule To edit an Exception Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Exception Schedule. 5. Press Enter. The Exception Schedule screen appears (Figure 7-7).

Figure 7-7: Exception Schedule Edit Screen 6. Use the Spacebar or Backspace key to cycle through the available

exception schedules until the one you want to edit appears. Note: The number of Exception schedules you are cycling through is

listed. The example in Figure 7-7 shows the second of three available Exception schedules.

7. To change the Exception type, use the arrow or Tab keys to select the Exception Type field. Use the Spacebar and Backspace keys to cycle through the Exception Type options. See Table 7-7.

8. To edit other fields, use the Tab or arrow keys to move to the fields. Either type in all values, or use the number keys to enter dates and the Spacebar and the Backspace key to change days and months.





Adding Time and Value Pairs to an Exception Schedule To add time and value pairs to an Exception Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Exception Schedule. 5. Press Enter. The Exception Schedule screen appears (Figure 7-7). 6. Use the Spacebar and Backspace keys to cycle to the Exception

Schedule where you want to add Time and Value pairs. 7. Place the cursor on any of the fields that appear except the number

of Exception Schedules. 8. Press the F3 (Add Item) key. The Time and Value fields appear

(Figure 7-8). 9. In the Time field, type the desired time. 10. In the Value field, press the Spacebar or Backspace key to select

On or Off. Note: Enter as many Time and Value pairs as you need.

11. Repeat Steps 7 through 10 for each pair. 12. Press the F4 (Back) key to return to the previous screen. 13. Press the F3 (Save) key. 14. Check the User Assistance area of the screen to verify if the save




Figure 7-8: Adding a Time and Value to an Attribute Screen

Deleting Time and Value Pairs from an Exception Schedule To delete time and value pairs from an Exception Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Exception Schedule. 5. Press Enter. The Exception Schedule appears (Figure 7-8). 6. Use the Spacebar and Backspace keys to cycle through and select

the Exception Schedule that you want to delete time and value pairs from.

7. Place the cursor on a time and value pair. 8. Press the F2 (Delete Item) key. 9. Repeat Steps 6 through 8 for each pair you wish to delete. 10. Press the F4 (Back) key to return to the previous screen. 11. Press the F3 (Save) key.




Commanding Schedule Objects To command a Schedule object: 1. Browse to and highlight a Schedule object. 2. Press the F2 (Command) key. 3. Use the Spacebar and Backspace keys to cycle through the

available commands. The Schedule object supports the commands described in Table 7-8.

Table 7-8: Supported Commands Command Description Enable Allows the Schedule object to resume normal scheduling

operation. Disable Halts all future scheduled times. Neither the weekly nor the

exception schedules will run again, until the Schedule object is re-enabled.

4. Press Enter.

Deleting Schedule Objects Note: Deleting Schedule objects can include deleting Weekly

Schedules, deleting Exception Schedules from Schedule objects or deleting the Schedule object itself. Deleting items from a List of Prop Refs or an Exception Schedule is covered in the Editing Schedule Objects section of this chapter.

Deleting a Weekly Schedule To delete a Weekly Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Weekly Schedule. 5. Press Enter. The Weekly Schedule appears (Figure 7-3). 6. Use the Spacebar or the Backspace key to select the day of the

week that contains the schedule you want to change.


7. Move the cursor to the first time and value pair. 8. Press the F2 (Item Del) key. 9. Repeat Steps 7 and 8 for each time and value pair in the weekly

schedule you are deleting. Note: The seven days of the week are always available in the weekly

schedule. Deleting a weekly schedule means you have removed all schedule time and value pairs from that schedule.




Deleting an Exception Schedule To delete an Exception Schedule: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. 4. Move the cursor to Exception Schedule. 5. Press Enter. The Exception Schedule screen appears (Figure 7-7). 6. Use the Spacebar and Tab keys to cycle to the Exception Schedule

you want to delete. 7. Press the F2 (Delete) key. 8. Repeat Steps 5 through 7 for each Exception Schedule you want

to delete. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key. 11. Check the User Assistance area of the screen to verify if the save




Deleting a Schedule Object To delete a Schedule object: 1. Browse to and highlight a Schedule object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 8 Working with Calendar Objects T

Introduction Calendar objects allow a user to accommodate for a special day or days, such as a holiday, in which the building controls should run in a different way than usual. For instance, users can configure a Calendar object for days when there is a change in the number of people or in the amount of activity in the building. This chapter describes how to:

• add a Calendar object

• edit a Calendar object

• add Date List entries to a Calendar object

• delete Date List entries from a Calendar object

• command a Calendar object

• delete a Calendar object For information on creating and editing Calendar objects in Project Builder, see the Project Builder User’s Guide. For information on viewing and editing Calendars using M-Calendar, see the M-Schedule/M-Calendar User’s Guide.


Key Concepts Calendar Object

The Calendar object maintains a list of dates designated as exceptions to the normal schedule. A Schedule object working from a chosen Calendar reads the Present Value of the Calendar object to determine if the current day is within the Date List of the Calendar. Single or multiple Schedule objects can work from the same Calendar object, allowing a user to reference a defined Calendar object, such as a holiday calendar, from any Schedule object. When a new day is added to the Calendar object, all the schedules working from the Calendar object are updated at the same time.

Attributes The values of an object’s attributes determine how the object operates. The Calendar object attributes described below are listed in the order that they appear on the screen. For additional information about the Calendar object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Calendar.




Date List List dates defined as entries to the Calendar object. Each entry may either be an individual date, range of dates, or month/week-of-month/day-of-week specification. If the current date matches any calendar entry, the Present Value is set to True. Also, individual fields of an entry can be left unspecified, thus acting as a wildcard if necessary. Each date contains four fields: Day of Month, Month, Year, and Day of Week. These fields appear in the following format:

<Day of Month> <Month> <Year> <Day of Week> The values of the Day of Month and Day of Week fields cannot contradict each other or the date is not valid. For example, a date of 10 Apr 1999 Tuesday does not schedule because April 10, 1999 is not a Tuesday. Also, the values of a date range (start date, end date) must be in chronological order or the date range is not valid. For example, a date range with a start date of 30 Aug 1999 Monday and an end date of 30 Jun 1999 Wednesday is not valid because August 30, 1999 comes after June 30, 1999.

Wildcard Date Fields Any unspecified date field is considered to be a wildcard date field.

Single Date For a single date, a wildcard opens a particular field to the full range of possible values for that field. Table 8-1 describes the meaning of a wildcard in each of the four date fields.

Table 8-1: Wildcard Date Field Meanings Wildcard Field Meaning Day of Month Every day of the month, unless a particular day of the

week is specified by the Day of Week field Month Every month Year Every year Day of Week Every day of the week, unless a particular day of the

month is specified by the Day of Month field

Table 8-2 shows some sample wildcard dates and their meanings.


Table 8-2: Sample Wildcard Dates Wildcard Date Meaning 01 * * Any day of week The first day of every month, every year 12 Apr * Any day of week April 12 of every year * Apr 1999 Any day of week Every day in April 1999 * * * Any day of week Every day * * * Monday Every Monday * * 1999 Monday Every Monday in 1999 * Apr 1999 Monday Every Monday in April of 1999 12 Apr 1999 Any day of week Only on Monday, April 12, 1999 (same meaning as 4/12/99Mon)


Date Range If the same field is a wildcard in both the start date and end date, the range from start to end is infinite, except as limited by the other date fields. The Day of Week field is only considered when it is specified for both the start date and the end date. Table 8-3 shows sample wildcard date ranges and meanings.

Table 8-3: Sample Wildcard Date Ranges Start Date End Date Meaning * * * Wednesday * * * Friday Every Wednesday, Thursday, and Friday

of every month, every year * * 1999 Wednesday * * 1999 Friday Every Wednesday, Thursday, and Friday

of every month in 1999 * Jun 1999 Wednesday * Aug 1999 Friday Every Wednesday, Thursday, and Friday

in June, July, and August in 1999 * Jun 1999 Any day of

week * Aug 1999 Any

day of week

Every day in June, July, and August in 1999

30 Aug 1999 Any day of week

* * * Any day of week

Every day after August 30, 1999

10 * * Any day of week

12 * * Any day of week

The tenth, eleventh, and twelfth days of every month, every year

04 Jul * Monday 04 Jul * Friday Every July 4 that is a Monday, Tuesday, Wednesday, Thursday, or Friday, every year



Week and Day The Week and Day selection identifies a month, a week of the month, and a day of the week. The week of the month can be chosen as Any (every) week of month, Days 1-7, Days 8-14, Days 15-21, Days 22-28, Days 29-31, and the Last seven days. Table 8-4 shows some sample wildcard week and day exceptions.

Table 8-4: Sample Wildcard Week and Days Wildcard Date Meaning Month Week of Month Day of Week Any Any week of

month Any day of week Every day of the year

Any Days 1-7 Monday Monday of the first week of every month Jan Any week of

month Tuesday Every Tuesday in January

Feb Days 8-14 Any day of week Every day of the week in the second week of February Any Any week of

month Wednesday Wednesday of every week of every month

Mar Any week of month

Any day of week Every day of every week in March

Any Days 14-21 Any day of week Every day of the third week of every month Apr Days 22-28 Thursday Thursday in the fourth week of April Any Days 29-31 Any day of week Last three days of every month with 31 days Jun Last seven days Saturday Saturday in the last seven days of June


Procedure Overview Table 8-5: Working with Calendar Objects To Do This Follow These Steps: Add a Calendar Object Browse to and highlight the Schedule container. Press the F3 (Add) key.

Highlight Calendar and press Enter. Fill in the fields using Table 8-6. Move the cursor to Date List. Press Enter. Press the F3 (Add Item) key. Use the Spacebar and Backspace key to view and select options and set date parameters. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the attribute screen. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Calendar Object Browse to and highlight a Calendar object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 8-6. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Date List Entries to a Calendar Object

Browse to and highlight a Calendar object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Date List. Press Enter. Press the F3 (Add Item) key to add a blank entry. Use the Spacebar and Backspace key to view and select options and set date parameters. Press the F4 (Back) key to return to the attribute screen. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Date List Entries from a Calendar Object

Browse to and highlight a Calendar object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Date List. Press Enter. Highlight the calendar entry to be deleted. Press the F2 (Del Item) key. Press the F4 (Back) key to return to the attribute screen. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Calendar Object Browse to and highlight a Calendar object. Press the F2 (Command) key. Use the Spacebar and Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Calendar Object Browse to and highlight a Calendar object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Calendar Object

To add a Calendar object: 1. Browse to and highlight the Schedule container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Calendar and press Enter. The Calendar object attribute


Figure 8-1: Calendar Object Attribute Screen 4. Fill in the fields using Table 8-6.


Table 8-6: Attribute Entry Requirements Screen Area Attribute Required Default Options/ Range Object Object Name No Blank Maximum 32 characters


Description No Blank Maximum 40 characters Object Type Yes Calendar The default is preset and cannot be

changed. Object


view and select options: HVAC, Fire, Security, Services, Administrative


Engineering Values

Date List Yes [0] Items Use the Spacebar and Backspace key to view and select options: Single Date, Date Range, Week and Day. Refer to Table 8-1, Table 8-2, Table 8-3, and Table 8-4.

5. Move the cursor to Date List. 6. Press Enter. 7. Press the F3 (Add Item) key. The Calendar object Date List


Figure 8-2: Calendar Object Date List


8. Use the Spacebar and Backspace key to view and select options and set date parameters. Refer to Table 8-1, Table 8-2, Table 8-3, and Table 8-4.

9. Press the F3 (Add Item) key to add a blank entry. 10. Repeat Steps 8 and 9 until all Date List entries have been added. 11. Press the F4 (Back) key to return to the attribute screen. 12. Press the F3 (Save) key. 13. Check the User Assistance area of the screen to verify if the save



Editing a Calendar Object To edit a Calendar object: Note: To delete or add Date List entries, refer to the appropriate

sections of this chapter.

1. Browse to and highlight a Calendar object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Calendar object attribute screen

appears (Figure 8-1). 4. Edit the fields using Table 8-6. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Adding Date List Entries to a Calendar Object To add Date List entries to a Calendar object: 1. Browse to and highlight a Calendar object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Calendar object attribute screen



4. Move the cursor to Date List. 5. Press Enter. The Calendar object Date List appears (Figure 8-2). 6. Press the F3 (Add Item) key to add a blank entry. 7. Use the Spacebar and Backspace key to view and select options

and set date parameters. Refer to Table 8-1, Table 8-2, Table 8-3, and Table 8-4.

8. Repeat Steps 6 and 7 for each entry to be added. 9. Press the F4 (Back) key to return to the attribute screen. 10. Press the F3 (Save) key. 11. Check the User Assistance area of the screen to verify if the save



Deleting Date List Entries from a Calendar Object To delete Date List entries from a Calendar object: 1. Browse to and highlight a Calendar object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Calendar object attribute screen

appears (Figure 8-1). 4. Move the cursor to Date List. 5. Press Enter. The Calendar object Date List appears (Figure 8-2). 6. Highlight the calendar entry to be deleted. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each entry to be removed from the list. 9. Press the F4 (Back) key to return to the attribute screen. 10. Press the F3 (Save) key. 11. Check the User Assistance area of the screen to verify if the save




Commanding a Calendar Object To command a Calendar object: 1. Browse to and highlight the Calendar object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and Backspace key to cycle through the list until

the desired command appears. The Calendar object supports the commands described in Table 8-7.

Table 8-7: Supported Commands Command Description Enable Compares the current day with the entries within the calendar

and reevaluates the Present Value based on the results. Disable Forces the Present Value of the object to the False state.

4. Press Enter.

Deleting a Calendar Object To delete a Calendar object: 1. Browse to and highlight a Calendar object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 9 Working with Optimal Start Objects T

Introduction The Optimal Start (OST) feature reduces energy consumption by keeping a facility in its unoccupied mode for as long as possible (for example, in the morning) and putting it in unoccupied mode as soon as possible (for example, at night), without sacrificing comfort. This chapter describes how to:

• add an Optimal Start object

• edit an Optimal Start object

• command an Optimal Start object

• delete an Optimal Start object


Key Concepts Optimal Start Object

The goal of Optimal Start is to reach either the Heating setpoint or Cooling setpoint at occupancy. (The Optimal Start object selects the appropriate setpoint depending on current temperature.) To meet this goal, the Optimal Start object calculates:

• building Heating and Cooling constants that represent the rate at which the temperature inside the building changes

• temperature differences between the Zone Temperature and the Heating setpoint or Cooling setpoint

• how many minutes of precooling or preheating are required based on the above difference

• optimal start time when the Zone WC (Warmup/Cooldown) Mode object is controlled by the optimal start process

The Optimal Start object interacts with Schedule objects, N2 Binary objects, and N2 Analog objects in an Optimal Start application. For more information, refer to Appendix C: Building an Optimal Start Application (LIT-6892330) in this document.

Optimal Start Equation The following equation illustrates how the optimal start time is derived:

Heating or Cooling Constant * (Temperature Differential)2 + Deadtime = Optimal Start Time

Table 9-1: Optimal Start Equation Variables Variable Description Heating or Cooling Constant

This variable is the building Heating or Cooling Constant parameter divided by 100.

Temperature Differential

This variable is the difference between the Zone Temperature and the Heating Setpoint or Cooling Setpoint. Units = delta deg F or delta deg K

Deadtime This variable is the amount of time required to raise or lower the Zone Temperature 1.0 degree. Units = minutes


Optimal Start Example For an example of the optimal start process, assume:

• The Zone Occ (Occupied) Mode object is scheduled weekly to start at 7:00 a.m. and stop at 5:00 p.m.

• Zone Temperature = 55°F

• Heating Setpoint = 70°F

• Deadtime = 5 minutes

• Building Heating Constant (since in Heating mode) = 10 (The optimal start process has run for several days, and the building Heating Constant has been adjusted to 10 based on past performance.)

• Temperature Differential = 70°F - 55°F = 15°F

• Heating Constant = 10/100 = 0.1 Therefore:

• Optimal Start Time = 0.1 * (15)2 + 5 = 0.1 * 225 + 5 = 22.5 + 5 = 27.5 = 28 minutes The optimal start process turns on the Zone WC (Warmup/Cooldown) Mode object at 6:32 a.m. (28 minutes prior to the scheduled 7:00 a.m. start time.)

Optimal Stop The goal of optimal stop is to set the heating/cooling zone to vacant zone temperature settings prior to actual zone vacancy. It must do this while the zone is still occupied without causing comfort level alarms. The Optimal Start object calculates the number of minutes before the zone changes from occupied to vacant. It then uses the same equation for deriving the optimal start time to determine the earliest stop time. To ensure occupancy comfort, it sets the temperature differential to the edited Temp (Temperature) Differential attribute.


Adaptation Each day, at occupancy, the optimal start process adapts the building Heating and Cooling Constant. It checks if the Zone Temperature converged to within the edited temperature differential of the Heating setpoint or Cooling setpoint. If the Zone Temperature did not converge, the building Heating and/or Cooling Constants are increased. This increase moves the optimal start time closer to the earliest start time defined for the system. If the Zone Temperature converges to within the edited Temperature Differential of the Heating setpoint or Cooling setpoint prior to occupancy, the buildings Heating and/or Cooling constants are decreased. This decrease moves the optimal start time closer to the occupancy start time defined for the system.

Attributes The values of an object’s attributes determine how the object will operate. The Optimal Start object attributes described below are listed in the order that they appear on the screen. For additional information about the Optimal Start object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Optimal Start.

Object Category Classifies the object to aid in the determination of user access capability and message routing.

OST Type Defines the supported configuration. When the zone is in a mode not available as an OST Type and not supported by the Optimal Start object, the Present Value is Idle.

Enabled Indicates if an object is active and executing an operational condition.


Adaptation Enabled Indicates whether the Optimal Start object should use adaptive learning to change the building heating and cooling constants and cooling and heating deadtimes.

Zone Schedule Obj (Zone Schedule Object) Identifies the object that schedules the Zone Occupied Mode object. This object must be defined in the schedule and have valid start and stop times for the current day for the Optimal Start object to run.

Zone Occ Mode Obj (Zone Occupied Mode Object) Identifies the object used to command a zone to occupied or unoccupied. This object must be specified in the zone schedule. It is commanded by scheduling to Occupied and by the Optimal Start object if the Maximum Prestop attribute is enabled.

Zone WC Mode Obj (Zone Warmup/Cooldown Mode Object) Identifies the object used to command a zone to Warmup or Cooldown mode. This object may be the same as the Zone Occupied Mode object. This object is commanded by the Optimal Start object at the optimal start time, and may be released at the occupied time.

Cooling Setpoint Identifies the attribute of an object used to define the zone occupied target cooling temperature. This object may be the same as the Heating Setpoint object.

Heating Setpoint Identifies the attribute of an object used to define the zone occupied target heating temperature. This object may be the same as the Cooling Setpoint object.

Zone Temperature Identifies the attribute of an object used to determine the actual zone temperature.


Outdoor Air Temp Identifies the attribute of an object used to determine the actual outside air temperature. If this attribute is not specified, or is offline, the outdoor air temperature is not used in the Optimal Start object’s calculations and it is assumed to be within the design temperatures.

Cooling Design Temp Indicates the highest outside temperature at which the cooling system maintains zone comfort in the Cooling mode. The default units (Imperial or SI) of this attribute are based on the Default Base Units attribute in the Device object.

Heating Design Temp Indicates the lowest outside temperature at which the heating system maintains zone comfort in the Heating mode. The default units (Imperial or SI) of this attribute are based on the Default Base Units attribute in the Device object.

Min (Minimum) Prestart Time Lists the minimum period of time before occupancy to start the heating/cooling system. This time allows for the required amount of air changes in the zone prior to occupancy (latest optimal start time).

Max (Maximum) Prestart Time Lists the maximum period of time required to bring the zone up to occupancy setpoint temperature under the worst conditions (earliest optimal start time).

Max (Maximum) Prestop Time Lists the maximum period of time that the heating/cooling system can be shut down and still maintain the occupied zone temperature until entering the unoccupied mode (earliest optimal stop time). By setting this time to zero (the default value), optimal stop is disabled.


Temperature Units Lists the units associated with the attributes for temperatures. The default units of this attribute are determined by the default base units attribute in the Device object. These attributes are:

• Cooling Design Temperature

• Heating Design Temperature

• Zone Temperature at Start

• Temperature Differential

Relative Temp Units Units associated with the Temp Differential attribute.

Display Precision Indicates the rounded position and decimal places to display for this object.

Cooling Constant Defines the rate at which the zone cools down after equipment startup. If adaptation is enabled, this constant is adapted without user intervention. If adapting and cooling and heating setpoints are the same attribute, the cooling constant is adapted even if the mode is not cooling, meaning both constants change.

Cooling Deadtime Lists the time required after startup to lower the temperature by one degree. The Optimal Start object’s algorithm adapts this value, if adaptation is enabled. If adapting and cooling and heating setpoints are the same attribute, the cooling deadtime is adapted even if the mode is not cooling, meaning both deadtimes change.

Heating Constant Defines the rate at which the zone heats up after equipment startup. If adaptation is enabled, this constant is adapted without user intervention. This attribute does not have a unit. If adapting and cooling and heating setpoints are the same attribute, the heating constant is adapted even if the mode is not heating, meaning both constants will change.


Heating Deadtime Lists the time required after startup to raise the temperature by one degree. The Optimal Start object’s algorithm adapts this value, if adaptation is enabled. If adapting and cooling and heating setpoints are the same attribute, the heating deadtime is adapted even if the mode is not heating, meaning both deadtimes change.

Temp (Temperature) Differential Lists the temperature value added to and subtracted from the zone setpoint to define a deadband used in the Optimal Start object’s calculations.

Present Value Represents the current value of the object. Present Value appears to the right of the object name in the container hierarchy after the object is created. Possible values are:

• Idle - Waiting for next occupied time for a supported mode (heating or cooling).

• Prestart Heating – Heating Optimal Start time is pending.

• Prestart Cooling – Cooling Optimal Start time is pending.

• Calculating Deadtime – Valid only if Adaption Enabled.

• Calculating Constant – Valid only if Adaption Enabled.

• Occupied

• Prestop – Waiting to reach optimal stop time.

• Not Operational – Optimal Start object is not operational due to errors in its connection status to other required objects. You can determine the specific problem by viewing the other status attributes. The Optimal Start object is Not Operational if the Zone Occ Mode Obj attribute is in the schedule, but there are no valid start and stop times for that day.


Procedure Overview Table 9-2: Working with Optimal Start Objects To Do This Follow These Steps: Add an Optimal Start Object Browse to and highlight the Energy container. Press the F3 (Add) key.

Highlight Optimal Start and press Enter. Fill in the fields using Table 9-3. Press the F3 (Save) key to save the object. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Optimal Start Object Browse to and highlight an Optimal Start object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 9-3. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Optimal Start Object

Browse to and highlight an Optimal Start object. Press the F2 (Command) key. Use the Spacebar or the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete an Optimal Start Object Browse to and highlight an Optimal Start object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Optimal Start Object

To add an Optimal Start object: 1. Browse to and highlight the Energy container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Optimal Start and press Enter. The first of two Optimal

Start object attribute screens appears (Figure 9-1). Note: Use the [ and ] keys to page to other screens.

Figure 9-1: Optimal Start Object Attribute Screen (1 of 2)


Figure 9-2: Optimal Start Object Attribute Screen (2 of 2) 4. Fill in the fields using Table 9-3.



Object Name No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ‘ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Optimal Start Default is preset and cannot be changed. Object Category

Yes HVAC Use the Spacebar and Backspace key to view and select options: HVAC, Fire, Security, Services, Administrative.

OST Type Yes Heating/Cooling Use the Spacebar and Backspace key to view and select options: Cooling Only, Heating/Cooling, Heating Only.

Object




Screen Area (Cont.)


Adaptation Enabled

Yes True Use the Spacebar and Backspace key to view and select options: True = Enabled; False = Not enabled.

Zone Schedule Object

Yes Blank Name of the Schedule object scheduling the Zone Occ Mode Obj

Zone Occ Mode Object

Yes Blank Name of the object used to command a zone to occupied or unoccupied

Zone WC Mode Object

Yes Blank Name of the object used to command a zone to Warmup or Cooldown mode. It may be the same as the Zone Occ Mode Obj.

Cooling Setpoint

Yes (unless Heating Only)

Blank Name of the object and analog attribute used to define the zone occupied target cooling temperature

Heating Setpoint

Yes (unless Cooling Only)

Blank Name of the object and analog attribute used to define the zone occupied target heating temperature

Zone Temperature

Yes Blank Name of the object and analog attribute used to determine the zone temperature

Control

Outdoor Air Temp

No Blank Name of the object and analog attribute used to determine the outside air temperature

Cooling Design Temp

Yes 95.0 deg F or 35.0 deg C

Minimum Value = -20 Maximum Value = 120 Units = Temperature Units

Heating Design Temp

Yes -5.0 deg F or -20.0 deg C

Minimum Value = -35 Maximum Value = 90 Units = Temperature Units

Min Prestart Time

Yes 20 minute Minimum Value = 0 Maximum Value = 240 Units = Minutes

Max Prestart Time


Max Prestop Time


Display Precision

Yes 10ths Use the Spacebar and Backspace key to view and select options. Refer to Display Precision Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Cooling Constant

Yes 5.0 Minimum Value = 1 Maximum Value = 999

Cooling Deadtime


Heating Constant

Yes 10.0 Minimum Value = 1 Maximum Value = 999

Setup

Heating Deadtime






Editing an Optimal Start Object To edit an Optimal Start object: 1. Browse to and highlight an Optimal Start object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The first of the two Optimal Start object attribute screen appears (Figure 9-1 and Figure 9-2).

Note: Use the [ and ] keys to page to other screens.

4. Edit the fields using Table 9-3. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Commanding an Optimal Start Object To command an Optimal Start object: 1. Browse to and highlight an Optimal Start object. 2. Press the F2 (Command) key. The Optimal Start Command field

appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Optimal Start object supports the commands described in Table 9-4.


Table 9-4: Supported Commands Command Description Cancel Prestart Delays pending start until latest prestart time. Only valid

during Prestart and before the Optimal Start time. Cancel Prestop Cancels the pending stop. Only valid during Prestop and

before the Optimal Stop time. Enable Allows the object to perform its calculations once a minute. Disable Prevents the object’s functionality, no calculations take

place.

4. Press Enter.

Deleting an Optimal Start Object To delete an Optimal Start object: 1. Browse to and highlight an Optimal Start object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 10 Working with Temporary Occupancy ObjectsT

Introduction The Temporary Occupancy (Temp Occ) object gives users the capability to temporarily override the current state of a multistate object for a specified period of time. This chapter describes how to:

• add a Temporary Occupancy object

• edit a Temporary Occupancy object

• command a Temporary Occupancy object

• delete a Temporary Occupancy object


Key Concepts Temporary Occupancy Object Operation

Upon receipt of the temporary occupancy request, the Temporary Occupancy object sends a write attribute message, at a higher priority than the scheduling feature, to the specified object. The overridden point then stays occupied until the timer expires, or the user cancels the occupancy request.

Attributes

Present Value This is the current state of the Temporary Occupancy object’s occupancy timer. A value of Active means the timer is active, and a value of Inactive means the timer is inactive.

Occupancy Time This defines the requested time for the Output object to remain occupied. The valid range is 1-65,535 minutes.

Time Remaining This is the value in minutes of the remaining occupancy time for the Output object.

Output Object This contains the reference to a prioritized attribute of a given object type in order to temporarily override that attribute.

Output Value This is the value to be written to the Output Object, when the Present Value attribute is set to Active.

States Text This is a reference to the multistate set, which characterizes the Output Value. The states text is obtained from the object/attribute specified in the Output Object once a new Temporary Occupancy object is created.


Reliability This is the reliability of the Temporary Occupancy object. If the Temporary Occupancy object is unable to communicate with the Output object during creation, the reliability is set to Unreliable. Once the Output object comes online, the reliability of the Temporary Occupancy object returns to Reliable. If at any other time, the Output object either goes Offline or is Unreliable, the Temporary Occupancy object does not report this change. Also, if the Temporary Occupancy object is Unreliable, the Present Value attribute may not be changed.


Procedure Overview Table 10-1: Working with Temporary Occupancy Objects

To Do This Follow These Steps: Add a Temporary Occupancy Object

Browse to and select the Schedule container. Press the F3 (Add) key. Select Temp Occ. Press the Enter key. Fill in the fields using Table 10-2. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key to return to the main screen.

Edit a Temporary Occupancy Object

Browse to and select the object you want to edit. Press the Return key. Press the F3 (Edit) key. Edit the attributes according to Table 10-2. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key to return to the main screen.

Command a Temporary Occupancy Object

Browse to and select the Temporary Occupancy object you want to command. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle to the desired command. Press the enter key.

Delete a Temporary Occupancy Object

Browse to and select the Temporary Occupancy object you want to delete. Press the Return key to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Temporary Occupancy Object

To add a Temporary Occupancy object: 1. Browse to and select the Schedule Container. 2. Press the F3 (Add) key. 3. Select Temp Occ from the list that appears. 4. Press the Enter key. The Temporary Occupancy object

configuration screen appears (Figure 10-1).

Figure 10-1: Temporary Occupancy Object Configuration Screen 5. Fill in the fields using Table 10-2.

Table 10-2: Temporary Occupancy Attribute Entry Requirements Screen Area

Attribute Name

Required Default Value Options/Range

Occupancy Time

Yes 1 Valid Range: 1-65,535; Units: Minutes

Output Object

Yes Null

Engineering Values

Output Value

Yes Multistate Set: Redirected to States Text. Refer to States Text in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).


6. Press the F3 (Save) key. 7. Press any key to continue. 8. Press the F4 (Cancel) key to return to the main screen.

Editing a Temporary Occupancy Object To edit a Temporary Occupancy object: 1. Browse to and select the object you want to edit. 2. Press the Return key to open it. 3. Press the F3 (Edit) key. 4. Edit the attributes according to Table 10-2. 5. Press the F3 (Save) key. 6. Press any key to continue. 7. Press the F4 (Cancel) key to return to the main screen.

Commanding a Temporary Occupancy Object To command a Temporary Occupancy object: 1. Browse to and select the Temporary Occupancy object you want

to command. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and Backspace keys to select a command. Select

State 1 to send the Temporary Occupancy object into the occupied mode. Select State 0 to send the Temporary Occupancy object into the unoccupied mode.

4. Press the Enter key. The command is executed.

Deleting a Temporary Occupancy Object To delete a Temporary Occupancy object: 1. Browse to and select the Temporary Occupancy object you want

to delete. 2. Press the Return key to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 11 Working with Printer ObjectsT

Introduction The Printer object allows printed alarms, summaries, and reports from within the N30 system to be generated. A Printer object needs to be added for each piece of printer hardware that exists on the system. Each N30 allows for a maximum of two printers to be attached to it.

IMPORTANT: Do not do a serial download of an N30 from Project Builder through a port for which a direct connect printer is defined. Doing so can cause communications to stop working, causing download errors. For example, if you are downloading a database with a direct connect Printer object assigned to Port 1 of the N30, you should establish your communications with the N30 on either Port 2 or Port 3 to avoid communications errors.

This chapter describes how to:

• add a Printer object

• edit a Printer object

• command a Printer object

• delete a Printer object


Key Concepts Printer Object

The Printer object provides hard copy output of the alarms, summaries, and other reports generated by objects, features, and the system. The Printer object is responsible for the buffering of output to the printer device. Printers are either connected directly or connected through dial-up access via modems. The Printer object provides the interface to manipulate the printer device and performs the following:

• Prints alarm messages from the Message Router object.

• Prints trend log data, summaries, and utility profile reports. The Printer object’s attributes allow a user to configure a variety of filters that establish the type of messages, or Status Notification Reports (SNR), which the Printer object receives. For more information about determining filter configurations, refer to Appendix B: Building a Message Router Application (LIT-6892320) in this document.

Attributes The values of an object’s attributes determine how the object operates. The Printer object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 11-2. For additional information about the Printer object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Analog Alarm.



Port Number Specifies which serial port the printer is connected to.

Active Filter Selects the type of filtering in effect for this printer destination. The filter types are as follows:

• Pass None - When selected this destination receives no alarm messages.

• Pass All - When selected this destination receives all alarm messages.




Priority Filter A Defines which priorities this destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, Status.

Category Filter A Defines which categories of messages the destination receives when Filter A is in effect. This filter has no effect for alarm messages without a defined category. A value of True for a particular selection means messages of that defined category reach this destination.

Msg Type Filter A Defines which types of messages the destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, Alarm.

Priority Filter B Defines which priorities the destination receives when Filter B is in effect. A value of True for a particular selection means that messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, Status.


Category Filter B Defines which categories of messages the destination receives when Filter B is in effect. This filter has no effect for alarm messages without a defined category. A value of True for a particular selection means that messages of that defined category reach this destination.

Msg Type Filter B Defines which types of messages the destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, Alarm.

Alt SNR Destination Indicates the alternate destination to receive this printer’s output if this printer is unavailable.

Page Size Indicates the number of lines per page.

SNR Delimiter Identifies if printed alarm messages and other data should be separated by a dashed line.

Interleave Specifies whether to mix alarm messages in other types of reports. If this attribute is True, alarm messages will be held or buffered until the end of the currently printing page. At this point, all of the buffered alarm messages will be printed. When the alarm messages are done printing, the remaining report pages are printed. If False, the complete report will be printed before alarm messages are printed.

Max SNR Queue Specifies the maximum number of alarm messages that can be buffered for this printer. If the queue is full, alarm messages sent to this printer to be printed may be lost.

XOFF Delay Time Defines the amount of time that passes before filtering XON/XOFF signal changes. Once the Serial Datalink object receives the XOFF signal, the Printer object waits the specified amount of time before changing the Error State attribute to OUT OF PAPER.


Use Dial Indicates remote connect printer or the direct connected printer. If this attribute is set to True, the object is set for the remote connect printer. If this attribute is set to False, the object is set for the direct connect printer and the Phone Number can’t be changed from None.

Phone Number Indicates the dial out phone number to printer device if a modem is connected to the port. If a printer device is connected to the port directly, this attribute should be blank.

Modem Config Object Lists the name of the object that holds the modem initialization strings and other dialout-related data.

SNR Dial Out Level Indicates the percentage of the queue that needs to be full before dial out occurs.

Retry Interval Indicates the interval in which the Printer object retries sending the Dial command periodically, if dial out fails. This attribute has no effect if the object is designated for the direct connect printer.

Hang Up Wait Time Specifies how many times the Printer object resends the Dial command. If the dial up connection is unsuccessful, the Printer object sends the Dial command again in the time defined as the Retry Interval. This attribute has no effect if the object is designated for the direct connect printer.

Process Identifier Used to identify the Printer object as a destination for SNRs. This identifier must be unique for each device. If it is not specified, the next available identifier is automatically used.


Procedure Overview Table 11-1: Working with Printer Objects To Do This Follow These Steps: Add a Printer Object Browse to and highlight the Operator Devices container. Press the

F3 (Add) key. Highlight Printer and press Enter. Fill in the fields using Table 11-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Printer Object Browse to and highlight a Printer object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields according to Table 11-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Printer Object Browse to and highlight a Printer object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Printer Object Browse to and highlight a Printer object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Printer Object

To add a Printer object: 1. Browse to and highlight the Operator Devices container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Printer and press Enter. The first of two Printer object

attribute screens appears (Figure 11-1). Note: Use the [ and ] keys to page to other screens.

Figure 11-1: Printer Object Attribute Screen (1 of 2)


Figure 11-2: Printer Object Attribute Screen (2 of 2) 4. Fill in the fields using Table 11-2.

Table 11-2: Attribute Entry Requirements Screen Area Attribute Required Default Options/Range Object Object

Name No Blank Maximum 32 characters


Description No Blank Maximum 40 characters Object Type Yes Printer The default is preset and cannot be changed. Object

Category Yes HVAC Use the Spacebar and Backspace key to view

and select options: HVAC, Fire, Security, Services, Administrative.

Port Setup Port Number Yes Port 2 Use the Spacebar and Backspace key to view and select options: Port 0, Port 1, Port 2, Port 3. Port 2 and Port 3 are the only valid options.

Setup Active Filter Yes Pass All Use the Spacebar and Backspace key to view and select options: Pass None, Pass All, Filter A, Filter B, Filter A and B.

Priority Filter A


Category Filter A


Msg Type Filter A




Screen Area (Cont.)


Setup (Cont.) Priority Filter B


Category Filter B


Msg Type Filter B


Alt SNR Destination

No Blank Enter the exact name of the Printer or VT100 object to act as an alternate destination for messages should this printer be inoperable.

Page Size No Blank 3-255 (Blank = printed lines not counted) SNR

Delimiter Yes False Use the Spacebar and Backspace key to view

and select options: True, False. Interleave Yes False Use the Spacebar and Backspace key to view

and select options: True, False. Max SNR

Queue Yes 25 3-100

Xoff Delay Time

Yes 20 0-65535 seconds

Process Identifier

No 3-15

Dial Setup Use Dial Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Phone Number

No Blank Blank = printer connected directly

Modem Config Object

No Blank Enter the exact name of the Modem Configuration object containing the required dial-out information.

SNR Dial Out Level

Yes 80 % 35-100 percent

Retry Interval


Retries Yes 3 0-10 Hang Up

Wait Time Yes 1 0-65535 seconds





Editing a Printer Object To edit a Printer object: 1. Browse to and highlight a Printer object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Printer object attribute screen appears

(Figure 11-1 and Figure 11-2). 4. Edit the fields according to Table 11-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Commanding a Printer Object To command a Printer object: 1. Browse to and highlight a Printer object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Printer object supports the commands listed in Table 11-3. For more information about supported commands, refer to the Object Dictionary.

Table 11-3: Supported Commands Command Description Form Feed Form feeds the paper. Queue Clear Clears the queue entries. Cancel Print Stops printing Trend Log, Summary, or Utility Profile data in

progress. Dial Forces a dial out when the Error State is Dial Out Failed.

4. Press Enter.


Deleting a Printer Object To delete a Printer object: 1. Browse to and highlight a Printer object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 12 Working with Modem Configuration ObjectsT

Introduction The Modem Configuration object allows a user to have different modem configuration data (for different purposes) located in a separate location. For example, one phone number may require a much longer connection timeout or number of redials. This chapter describes how to:

• add a Modem Configuration object

• edit a Modem Configuration object

• delete a Modem Configuration object


Key Concepts Modem Configuration Object

The Modem Configuration object serves as a named storage place for modem configuration data. The user provides the specific dial-out configuration data for this object and then other objects capable of initializing a dial out connection refer to this data. A dial-out Printer object typically uses the Modem Configuration object as a source of data. If the standard modem configuration string of the Serial Datalink object (as defined by the N30 Device object) refers to incorrect modem configuration data for a particular printer, the Printer object can reference the Modem Configuration object for different modem configuration data. When the default values of the Serial Datalink object are sufficient, no Modem Configuration object is required.

Attributes The values of an object’s attributes determine how the object operates. The Modem Configuration object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 12-2. For additional information about the Modem Configuration object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Modem Config.




Dial Mode Indicates if pulse or tone dialing is used.

Connect Timeout Specifies the length of time to wait for connection after dialing before the attempt is aborted.

Modem Init String Identifies the set up commands sent to the modem.

Number of Redials Specifies the number of times the dialing connection is attempted.


Procedure Overview Table 12-1: Working with Modem Configuration Objects To Do This Follow These Steps: Add a Modem Configuration Object

Browse to and highlight the Operator Devices container. Press the F3 (Add) key. Highlight Modem Config and Press Enter. Fill in the fields using Table 12-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Modem Configuration Object

Browse to and highlight a Modem Configuration object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 12-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete a Modem Configuration Object

Browse to and highlight a Modem Configuration object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Modem Configuration Object

To add a Modem Configuration object: 1. Browse to and highlight the Operator Devices container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Modem Config and Press Enter. The Modem

Configuration Object attribute screen appears (Figure 12-1).

Figure 12-1: Modem Configuration Object Attribute Screen 4. Fill in the fields using Table 12-2.


Table 12-2: Attribute Entry Requirements Screen Area Attribute Required Default Options/Range Object Object Name No Blank Maximum 32 characters


Description No Blank Maximum 40 characters Object Type Yes Modem

Config The default is preset and cannot be changed.

Object Category



Setup Dial Mode Yes Tone Use the Spacebar and Backspace key to view and select options: Tone, Pulse.

Connect Timeout

Yes 45 Seconds

Number of Redials

Yes 3 0-6

Modem Init String

Yes Blank Enter the modem setup data.





Editing a Modem Configuration Object To edit a Modem Configuration object: 1. Browse to and highlight a Modem Configuration object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Modem Configuration object

attribute screen appears (Figure 12-1). 4. Edit the fields using Table 12-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Deleting a Modem Configuration Object To delete a Modem Configuration object: 1. Browse to and highlight a Modem Configuration object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 13 Working with Global Data Sharing Objects

Introduction The Global Data Sharing object permits the sharing of data from a single master input with up to 16 slave output references. This chapter describes how to:

• add a Global Data Sharing object

• edit a Global Data Sharing object

• add slaves to the Slaves List

• delete slaves from the Slaves List

• command a Global Data Sharing object

• delete a Global Data Sharing object



Key Concepts Global Data Sharing Object

The Global Data Sharing feature distributes changes in value associated with a single master input to a range of between one and sixteen targeted slave outputs. For example, Outdoor Air data can be distributed and shared between multiple Air Handling Unit controllers.

Attributes The values of an object’s attributes determine how the object operates. The Global Data Sharing object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are listed in Table 13-2. For additional information about Global Data Sharing object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Global Data.



Master Identifies the attribute reference (object and attribute name) and its value, state, or status that is to be sent to the list of slaves.

Slaves List Identifies the names (attribute references) of from 1 to 16 slaves that receive the value, status, or state of the master.


Procedure Overview Table 13-1: Working with Global Data Sharing Objects To Do This Follow These Steps: Add a Global Data Sharing Object

Browse to and highlight the Programming container. Press the F3 (Add) key. Highlight Global Data and press Enter. Fill in the fields using Table 13-2. Move the cursor to Slave List. Press Enter. Type in an object name and attribute name. Press the F3 (Add Item) key and type in another slave. Press the F4 (Back) key. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Global Data Sharing Object

Browse to and highlight a Global Data Sharing object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 13-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Slaves to the Slaves List Browse to and highlight a Global Data Sharing Object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Slaves List. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an object name and attribute name. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Slaves from the Slaves List

Browse to and highlight a Global Data Sharing Object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Slaves List. Press Enter. Highlight the slave to be deleted. Press the F2 (Del Item) key. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Global Data Sharing Object

Browse to and highlight a Global Data Sharing object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Global Data Sharing Object

Browse to and highlight a Global Data Sharing object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm deletion.


Detailed Procedures Adding a Global Data Sharing Object

To add a Global Data Sharing object: 1. Browse to and highlight the Programming container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Global Data and press Enter. The Global Data Sharing

attribute screen appears (Figure 13-1).

Figure 13-1: Global Data Sharing Object Attribute Screen 4. Fill in the fields using Table 13-2.




Description No Blank Maximum 40 characters Object Type Yes Global Data Default is preset and cannot be changed. Object Category


Object


Engineering Values

Master Yes Blank Enter the exact object and attribute name containing the data to be distributed. For example, the name of the N2 Analog Input point object representing outdoor air temperature.

Slaves List Yes 0 items Enter the exact object name and attribute names of the object and attribute to receive the data. For example, the names of all Controller objects representing Air Handling Units in the site. Present Value appears by default (AHU1.Present Value).

IMPORTANT: The system does not check to ensure that the master (input) and the slaves (outputs) are mapped to the same data type. Each slave attempts to convert the value being received (if necessary) to the data type defined for itself.

5. Move the cursor to Slaves List. 6. Press Enter. The Global Data Sharing object Slaves List appears

(Figure 13-2).


Figure 13-2: Global Data Sharing Object Slaves List 7. Type in an object name and attribute name.

Example: AHU1.Present Value. 8. Press the F3 (Add Item) key and type in another slave. 9. Repeat Steps 7 through 8 for all slaves being added to the list. 10. Press the F4 (Back) key to return to the previous screen. 11. Press the F3 (Save) key. 12. Check the User Assistance area of the screen to verify if the save




Editing a Global Data Sharing Object To edit a Global Data Sharing object: Note: To delete or add slaves, refer to the appropriate sections of

this chapter.

1. Browse to and highlight a Global Data Sharing object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Global Data Sharing object attribute screen appears (Figure 13-1).




Adding Slaves to the Slaves List To add slaves to the Slaves List: 1. Browse to and highlight a Global Data Sharing object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Global Data Sharing object attribute

screen appears (Figure 13-1). 4. Move the cursor to Slaves List. 5. Press Enter. The Global Data Sharing object Slaves List appears

(Figure 13-2). 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in an object name and attribute name. 8. Repeat Steps 6 and 7 for each new slave. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save

was successful or if there were errors. If errors were detected,


correct them and resave the entries. Once the save is successful, continue with Step 12.


Deleting Slaves from the Slaves List To delete slaves from the Slaves List: 1. Browse to and highlight a Global Data Sharing object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Global Data Sharing object attribute

screen appears (Figure 13-1). 4. Move the cursor to Slaves List. 5. Press Enter. The Global Data Sharing object Slaves List appears

(Figure 13-2). 6. Highlight the slave to be deleted. 7. Press the F2 (Delete Item) key. 8. Repeat Steps 6 and 7 for each slave to be removed from the list. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save



Commanding a Global Data Sharing Object To command a Global Data Sharing object: 1. Browse to and highlight a Global Data Sharing object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Global Data Sharing object support the command listed in Table 13-3.

Table 13-3: Supported Commands Command Description Enable Updates changes to the slaves list. Disable Prevents distribution of Changes-of-Value.


4. Press Enter.

Deleting a Global Data Sharing Object To delete a Global Data Sharing object: 1. Browse to and highlight a Global Data Sharing object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 14 Working with Interlock Objects

Introduction The Interlock object establishes conditional control over one or more other objects. Based on the results of some conditional checks, a series of commands can control other objects. This chapter describes how to:

• add an Interlock object

• edit an Interlock object

• add sources to an Interlock object

• delete sources from an Interlock object

• add action table entries to an Interlock object

• delete action table entries from an Interlock object

• command an Interlock object

• delete an Interlock object



Key Concepts Interlock Object

The Interlock object establishes conditional control over one or more other objects. It consists of IF conditional statements, True command statements, and False command statements. Through these statements, the user specifies a set of conditional checks. Based on the results of those checks, a series of commands can control a collection of one or more objects. For example, the Interlock object is used to place a Variable Air Volume (VAV) controller in the occupied mode whenever the main fan is on and in the occupied mode. The attributes of the Interlock object have to work together as well as with other objects in order for the object to function properly. The Source and Logic attributes determine the condition and the Action Table defines the course of action (commands) to take based on those conditions. For information about building an Interlock application, refer to Appendix D: Building an Interlock Application (LIT-6892340) in this manual.

Attributes The values of an object’s attributes determine how the object operates. The Interlock object attributes described below are listed in the order they appear on the screen. Entry requirements for these attributes are in Table 14-4. For additional information about the Interlock object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Interlock.


N30 Supervisory Controller User’s 14-3


Commands Priority Determines the order by importance for all commands set.

States Text Indicates the text that appears for the Present Value.

Source Contains data pertaining to an object being referenced which is used as input into the logic expression. It helps determine if the condition is true or false. Table 14-1 identifies the information needed for the source.

Table 14-1: Source Information Options Description Object Name Name of the source object Attribute Varies with the object. The default is Present Value. Relation Equal, Not Equal, Greater Than, Less Than, Greater or Equal, Less or Equal Value The value used in the relation varies according to the object. True or False. Differential Accounts for variations in the value. Required if the value is analog.

Logic Specifies the Boolean (AND/OR) logic used in combination with the Source input to deliver a True or False statement. Options include:

• Match All - Every condition must be true.

• Match Any - One or more of the conditions must be true.

• Complex - Use Logic Equation attribute for complex logic.


Logic Equation When the Logic attribute is set to Complex, this attribute contains a logic equation. Use the logic equation to define the relationship between the master conditions using logic operators and parentheses for determining precedence. Valid characters in the Logic Equation string are shown in Table 14-2.

Table 14-2: Logic Equation Characters Character Description * AND operator + OR operator ( Open parenthesis (for grouping) ) Close parenthesis (for grouping) Numbers Master condition numbers Spaces Spaces are allowed for readability

The following is a sample Logic Equation string: ((1+2)*(3+4))+(6*7) This sample equation says that master condition ((1 or 2) and (3 or 4)) or (6 and 7) results in a True execution.

Action Table - True List commands issued when the Interlock object’s Present Value goes to a True state. This attribute identifies the object to receive the commands, the amount of time each command waits to be sent after a change in condition, and the command to be issued from those made available upon entering the Command ID field.

Action Table - False Lists commands issued when the Interlock object’s Present Value goes to a False state. This attribute identifies the same parameters as the Action Table - True attribute.

Example Figures 14-1 through 14-4 show screens from a sample completed Interlock object. This sample object uses the Logic Equation attribute.


Figure 14-1: Completed Interlock Object - Focus Screen

Figure 14-2: Completed Interlock Object - Edit Screen


Figure 14-3: Completed Interlock Object - Source

Figure 14-4: Completed Interlock Object - Action Table - True


Procedure Overview Table 14-3: Working with Interlock Objects To Do This Follow These Steps: Add an Interlock Object Browse to and highlight the Programming container. Press the

F3 (Add) key. Select Interlock and press Enter. Fill in the fields using Table 14-4. Move the cursor to Source. Press Enter. Type in the object name. Press Tab to move to the next field. Use the Spacebar and Backspace key to cycle through the list until the desired option appears. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Move the cursor to Logic. Fill in the field using Table 14-4. If necessary, move the cursor to Logic Equation and fill in the field. Move the cursor to True under Action Table. Press Enter. Type in an object name. Press Tab to move to the next field. Fill in the remaining fields. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Move the cursor to the next field (False). Press Enter. Type in an object name. Press Tab to move to the next field. Fill in the remaining fields. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Interlock Object Browse to and highlight an Interlock object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 14-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Sources to an Interlock Object

Browse to and highlight an Interlock object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Source. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an object name. Press Tab to move to the next field. Use the Spacebar and Backspace key to cycle through the list until the desired option appears. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Sources from an Interlock Object

Browse to and highlight an Interlock object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Source. Press Enter. Highlight the source to be deleted. Press the F2 (Del Item) key. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Action Table Entries to an Interlock Object

Browse to and highlight an Interlock object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to True or False under Action Table. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an object name. Press Tab to move to the next field. Fill in the remaining fields. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.



To Do This (Cont.) Follow These Steps: Delete Action Table Entries from an Interlock Object

Browse to and highlight an Interlock object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to True or False under Action Table. Press Enter. Highlight the Action Table value to be deleted. Press the F2 (Del Item) key. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Interlock Object Browse to and highlight an Interlock object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete an Interlock Object Browse to and highlight an Interlock object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Interlock Object

To add an Interlock object: 1. Browse to and highlight the Programming container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Select Interlock and press Enter. The Interlock object attribute


Figure 14-5: Interlock Object Attribute Screen 4. Fill in the fields using Table 14-4.



Object Name

No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ’ [ ]. If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type

Yes Interlock The default is preset and cannot be changed.

Object Category

Yes HVAC Use the Spacebar and the Backspace key to view and select options: HVAC, Fire, Security, Services, Administrative.

Object

Enabled Yes True Use the Spacebar and the Backspace key to view and select options: True, False.

Engineering Values

Commands Priority

Yes Default Use the Spacebar and the Backspace key to view and select option. Refer to Write Priority Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Display States Text Yes False True Use the Spacebar and the Backspace key to view and select options. Refer to States Text in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Interlock Definition

Source Yes 0 items List of source objects used for input into the logic expression.

Logic Yes Match All Use the Spacebar and the Backspace key to view and select options. Match All: All of the source conditions must be true. Match Any: One or more of the source conditions must be true. Complex: Use the Logic Equation attribute for complex logic.

Logic Equation

No Define the relationship between the master conditions using logic operators and parentheses for determining precedence.

Action Table True Yes 0 items Object Name Delay Command ID Parameters (varies according to the command)

False Yes 0 items Object Name Delay Command ID Parameters (varies according to the command)

5. Move the cursor to Source. 6. Press Enter. The Interlock object Source list appears

(Figure 14-6).


Figure 14-6: Interlock Object Source List 7. Type in an object name. 8. Press Tab to move to the next field. 9. Use the Spacebar and Backspace key to cycle through the list until

the desired option appears. 10. Repeat Steps 8 and 9 for the other fields. 11. Press the F3 (Add Item) key to add a blank entry. 12. Repeat Steps 7 through 11 for each new source to be added. 13. Press the F4 (Back) key to return to the previous screen. 14. Move the cursor to Logic. 15. Fill in the field according to Table 14-4. 16. If the Logic field is set to Complex, move the cursor to Logic

Equation and fill in the field. 17. Move the cursor to True under Action Table. 18. Press Enter. The True list appears (Figure 14-7).


Figure 14-7: Interlock Object True List 19. Type in an object name. 20. Press Tab to move to the next field. 21. Fill in the remaining fields. 22. Press the F3 (Add Item) key to add a blank entry. 23. Repeat Steps 19 through 22 for each Action Table (True) value to

be added. 24. Press the F4 (Back) key to return to the previous screen. 25. Move the cursor to the next field (False). 26. Press Enter. The False list appears (Figure 14-8).


Figure 14-8: Interlock Object False List 27. Type in an object name. 28. Press Tab to move to the next field. 29. Fill in the remaining fields. 30. Press the F3 (Add Item) key to add a blank entry. 31. Repeat Steps 27 through 30 for each Action Table (False) value to

be added. 32. Press the F4 (Back) key to return to the previous screen. 33. Press the F3 (Save) key. 34. Check the User Assistance area of the screen to verify if the save




Editing an Interlock Object To edit an Interlock object: Note: To delete or add Sources or Action Table values, refer to the

appropriate sections of this chapter.

1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Interlock object attribute screen appears (Figure 14-5).




Adding Sources to an Interlock Object To add sources to an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. The Interlock object attribute

screen appears (Figure 14-5). 3. Press the F3 (Edit) key. 4. Move the cursor to Source. 5. Press Enter. The Interlock object Source list appears

(Figure 14-6). 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in an object name. 8. Press Tab to move to the next field. 9. Use the Spacebar and Backspace key to cycle through the list until

the desired option appears. 10. Repeat Steps 8 and 9 for the other fields. 11. Press the F3 (Add Item) key to add a blank entry. 12. Repeat Steps 7 through 11 for each source to be added.


13. Press the F4 (Back) key to return to the previous screen. 14. Press the F3 (Save) key to save the changes. 15. Check the User Assistance area of the screen to verify if the save



Deleting Sources from an Interlock Object To delete sources from an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. The Interlock object attribute

screen appears (Figure 14-5). 3. Press the F3 (Edit) key. 4. Move the cursor to Source. 5. Press Enter. The Interlock object Source list appears

(Figure 14-6). 6. Highlight the source to be deleted. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each source to be deleted. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save



Adding Action Table Entries to an Interlock Object To add Action Table entries from an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. The Interlock object attribute

screen appears (Figure 14-5). 3. Press the F3 (Edit) key. 4. Move the cursor to True or False under Action Table.


5. Press Enter. The Interlock object True or False list appears. 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in an object name. 8. Press Tab to move to the next field. 9. Fill in the remaining fields. 10. Press the F3 (Add Item) key to add a blank entry. 11. Repeat Steps 7 through 10 for each Action Table value to be

added. 12. Press the F4 (Back) key to return to the previous screen. 13. Press the F3 (Save) key to save the changes. 14. Check the User Assistance area of the screen to verify if the save



Deleting Action Table Entries from an Interlock Object To delete Action Table entries from an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. The Interlock object attribute

screen appears (Figure 14-5). 3. Press the F3 (Edit) key. 4. Move the cursor to True or False under Action Table. 5. Press Enter. The True or False list appears. 6. Highlight the Action Table value to be deleted. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each Action Table value to be deleted. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save


12. Press the any key to continue. 13. Press the F4 (Cancel) key to return to the container hierarchy.


Commanding an Interlock Object To command an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Interlock object supports the commands described Table 14-5.

Table 14-5: Supported Commands Command Description Re-Command Reissues the commands for the current state. Override Updates the Present Value at Command Priority Operator

Override. Choose True to send the commands in the True Action Table or False to send the commands in the False Action Table.

Override Release Releases Command Priority Operator Override from Present Value.

Release Releases the identified command priority from the specified, writeable attribute, and allows it to be controlled by the next highest priority.

Release All Releases Command Priorities 3 through 15 from the specified, writeable attribute. Command Priorities 1 and 2 remain.

Enable Ensures that the object reacts to any changes it missed while it was disabled.

Disable Locks out all outputs and prevents the Interlock functionality.

4. If the desired command appears with additional parameters below

it, press the Tab key to highlight the field and either type in the necessary information or use the Spacebar and Backspace key to cycle through the list of options.

5. Press Enter.

Deleting an Interlock Object To delete an Interlock object: 1. Browse to and highlight an Interlock object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 15 Working with Signal Select Objects

Introduction The Signal Select feature allows you to create objects that either calculate the average, high, and low values from a set of analog points, or process values from multiple zones to adjust various setpoints. This chapter describes how to:

• add a Signal Select object

• edit a Signal Select object

• add input entries to a Signal Select object

• delete input entries from a Signal Select object

• command a Signal Select object

• delete a Signal Select object



Key Concepts Signal Select

The Signal Select feature works with either analog or binary points, and in Multi-Zone applications where values from multiple zones are processed and used by the Air Handling Unit (AHU) to adjust various setpoints. With Signal Select, you can:

• determine the highest, lowest, and average values of a set of analog input points.

• command analog points to the average, highest, or lowest values calculated from a set of analog input points.

• calculate the state of a set of binary input points (using AND and OR logical operations) and use the calculated value to command a binary output point.

Analog Signal Select For Analog point types, the Signal Select object computes (one or more of) average input, highest input, and lowest input values for use in updating an attribute value of another object. This computation occurs each time the input points change value. Immediately after the computation, the Signal Select object commands each (of up to three) referenced output objects to their respective values (average output, highest output, and lowest output). If a binary type attribute is defined as an input, the input value is converted to analog before each computation. Any other input type forces the Signal Select object to classify the input as unreliable.

Binary Signal Select For Binary point types, the Signal Select object computes average state, logical OR state, and logical AND state values for use in updating an attribute value of another object. This computation occurs each time one or more of the input points changes state. Immediately after the computation, it commands each (of up to three) referenced output objects to their respective states (Average Output, Logical OR Output, and Logical AND Output). If an analog type attribute is defined as an input, the input value is converted to binary before each computation. Any other input type forces the Signal Select object to classify the input as unreliable. Table 15-1 describes the various types of computations.


Table 15-1: Computation Types for Binary Signal Select Computation Type Description Average Output Computation

If the majority of inputs are at State 1 or the inputs are evenly split between State 1 and State 0, the Average Output is commanded to State 1. If the majority of inputs are at State 0, the Average output is commanded to State 0.

Logical OR Computation

If any input is at State 1, the Logical OR output is commanded to State 1. If all inputs are at State 0, the Logical OR output is commanded to State 0.

Logical AND Computation

If all inputs are at State 1, the AND output is commanded to State 1. If any input is not at State 1, the AND output is commanded to State 0.

Attributes The values of an object’s attributes determine how the object operates. The Signal Select object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 15-3. For additional information about the Signal Select object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Signal Select.




Input List Lists attributes of objects used in the Signal Select calculations. If an analog type is added to this list but the Point Type attribute indicates binary, this analog type is converted to a binary value before each computation and vice versa. If one or more of the objects in the input list is disabled, the output objects’ values are calculated using only the remaining inputs’ values.

Average Output Indicates the object attribute updated using the calculated average of all of the inputs of the Signal Select object.

High OR Indicates the object attribute updated using the highest input of all of the inputs in the Signal Select object for analog point types. For point types specified as binary, the value is updated using a logical OR condition of all inputs of the Signal Select object.

Low AND Indicates the object attribute updated using the lowest input of all of the inputs in the Signal Select object for point types specified as analog. For point types specified as binary, the value is updated using logical AND condition of all inputs of the Signal Select object.

Point Type Indicates the type of input values (analog or binary) the Signal Select monitors.


Procedure Overview Table 15-2: Working with Signal Select Objects To Do This Follow These Steps: Add a Signal Select Object Browse to and highlight the Programming container. Press the

F3 (Add) key. Highlight Signal Select and press Enter. Fill in the fields using Table 15-3. Move the cursor to Input List. Press Enter. Type in an object and attribute name. Press the F3 (Add Item) key to add a blank entry. Press F4 (Back) key to return to the previous screen. Fill in the remaining fields using to Table 15-3. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Signal Select Object Browse to and highlight a Signal Select object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 15-3. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Input Entries to a Signal Select Object

Browse to and highlight a Signal Select object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Input List. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an object and attribute name. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Input Entries from a Signal Select Object

Browse to and highlight a Signal Select object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to Input List. Press Enter. Highlight the input to be deleted and press F2 (Del Item) key. Press the F4 (Back) key to return to the previous screen. Press the F3 (Save) key to save the changes. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Signal Select Object

Browse to and highlight a Signal Select object. Press the F2 (Command) key. Use the spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Signal Select Object Browse to and highlight a Signal Select object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Signal Select Object

To add a Signal Select object: 1. Browse to and highlight the Programming container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Signal Select and press Enter. The Signal Select object


Figure 15-1: Signal Select Object Attribute Screen 4. Fill in the fields using Table 15-3.





Description No Blank Maximum 40 characters Object Type Yes Signal

Select The default is preset and cannot be changed.

Object Category

Yes HVAC Use the spacebar and the Backspace key to view and select options: HVAC, Fire, Security, Services, Administrative.

Enabled Yes True Use the spacebar and the Backspace key to view and select options: True, False.

Engineering Values

Input List Yes 0 Enter the exact object and attribute reference. Present Value appears as the default attribute. Minimum number of Inputs in list = 2 Maximum number of Inputs in list = 12

Average Output

No Blank Enter the exact object and attribute reference. Present Value appears as the default attribute.

High OR No Blank Enter the exact object and attribute reference. Present Value appears as the default attribute.

Low AND No Blank Enter the exact object and attribute reference. Present Value appears as the default attribute.

Point Type Yes Analog Use the spacebar and the Backspace key to view and select options: Analog, Binary.

5. Move the cursor to Input List. 6. Press Enter. The Signal Select object Input List appears

(Figure 15-2).


Figure 15-2: Signal Select Object Input List 7. Type in an object and attribute name. 8. Press the F3 (Add Item) key to add a blank entry. 9. Repeat Steps 7 and 8 for each input being added. 10. Press the F4 (Back) key to return to the previous screen. 11. Fill in the remaining fields using Table 15-3. 12. Press the F3 (Save) key. 13. Check the User Assistance area of the screen to verify if the save



Editing a Signal Select Object To edit a Signal Select object: Note: To delete or add Input entries, refer to the appropriate


1. Browse to and highlight a Signal Select object. 2. Press Enter to open the object.


Note: Additional attributes appear. Refer to the Object Dictionary for more information.

3. Press the F3 (Edit) key. The Signal Select object attribute screen appears (Figure 15-1).




Adding Input Entries to a Signal Select Object To add Input entries to a Signal Select object: 1. Browse to and highlight a desired Signal Select object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Signal Select object attribute screen

appears (Figure 15-1). 4. Move the cursor to Input List. 5. Press Enter. The Signal Select object Input List appears

(Figure 15-2). 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in an object and attribute name. 8. Repeat Steps 6 and 7 for each input being added. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save




Deleting Input Entries from a Signal Select Object To delete Input entries from a Signal Select Object: 1. Browse to and highlight a Signal Select object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Signal Select object attribute screen

appears (Figure 15-1). 4. Move the cursor to Input List. 5. Press Enter. The Signal Select object Input List appears

(Figure 15-2). 6. Highlight the input to be deleted. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each input to be removed from the list. 9. Press the F4 (Back) key to return to the previous screen. 10. Press the F3 (Save) key to save the changes. 11. Check the User Assistance area of the screen to verify if the save



Commanding a Signal Select Object To command a Signal Select object: 1. Browse to and highlight a Signal Select object. 2. Press the F2 (Command) key. The Signal Select Command field

appears. 3. Use the spacebar and the Backspace key to cycle through the list

until the desired command appears. The Signal Select object supports the commands described in Table 15-4.

Table 15-4: Supported Commands Command Description Enable Ensures that the object reacts to any changes it may have

missed while it was disabled and returns it to normal operation. Disable Locks out all outputs and prevents the Signal Select functionality.

4. Press Enter.


Deleting a Signal Select Object To delete a Signal Select object: 1. Browse to and highlight a Signal Select object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 16 Working with Auto Shutdown Objects

Introduction The Auto Shutdown (AS) object provides a means of preventing nuisance alarms by suppressing alarm reporting for specified points. This chapter describes the Auto Shutdown object and how to:

• add an Auto Shutdown object

• edit an Auto Shutdown object

• command an Auto Shutdown object

• delete an Auto Shutdown object An example of a use for the Auto Shutdown object is to prevent alarms set to monitor the discharge air temperature of a fan when that fan is turned off.



Key Concepts Auto Shutdown Object

When a selected multistate control point is in a specified shutdown state, the Auto Shutdown object suppresses alarm reporting from a list of dependent objects to prevent nuisance alarms. This is accomplished by sending an enable/disable command to each of the dependent objects’ Alarm objects, based on the control point’s attribute reference value and the shutdown state. A startup delay is provided so that points are not released immediately from shutdown. An example of a use for the Auto Shutdown object is to prevent alarms set to monitor the discharge air temperature of a fan when that fan is turned off. When the fan is turned off, the fan state value is sent to the Auto Shutdown object. The Auto Shutdown object then evaluates the Present Value (control point state) against the Shutdown State defined in the Auto Shutdown object. If the Present Value matches the Shutdown State, the Auto Shutdown object sends a Disable Command to the Alarm Object of every referenced dependent object in the Dependents list. Consequently, when the fan is turned back on, the Auto Shutdown object again evaluates the current state and, if the Present Value does not match the Shutdown State, starts the Startup Delay timer. Once the timer expires, the Auto Shutdown object sends an Enable command to the Alarm Object of every referenced dependent object in the Dependents list. Note: Changing the Dependents attribute causes an immediate

reevaluation of the current state. However, changes to the Startup Delay time do not take effect until the next change in the Control Point state.


Auto Shutdown Logic The flowchart in Figure 16-1 shows the logic sequence of the Auto Shutdown object.

Auto ShutdownObject

Disable Alarms ofDependent

Objects.

Are valuesequal? Startup Delay

Wait for Delay toExpire.

Enable Alarms ofDependent

Objects.

No

Control Point State

Shutdown State

COS (Control Point Attribute)

Yes

NoIs there anactive timer? Delete timer.

Yes

Yes

No

AS Seq.vsd

Figure 16-1: Auto Shutdown Object Logic

Attributes

Control Point The value associated with this attribute, along with the shutdown state, is used to determine if an alarm shutdown should occur.

Dependents Each dependent object identified in this list of object references is used to locate the Alarm object that is to have its alarm reporting controlled by the Control Point.


Shutdown State The value of this attribute determines the definition of the shutdown state.

Startup Delay The Startup delay represents the time in minutes that must elapse before alarm reporting is re-enabled once the Control Point changes from the shutdown state.

Reliability The value of this attribute reflects the reliability of the Control Point. Input Unreliable is the state used when the configured input goes unreliable.

Commands

Disable Prevents the AS object from responding to any change occurring at the control attribute reference, including the reliability associated with the control point.

Enable This ensures activation of all processing associated with this object. Immediately following receipt of this command, the AS object re-evaluates the control attribute reference value and takes the appropriate action to the dependent list.

Example Figure 16-2 and Figure 16-3 show screens for a sample completed Auto Shutdown object on air handler AHU-1. The control point is the fan (N2 BO point) and the dependents are temperature sensors DA-T (Discharge Air), RM-T (Room Temperature), STATIC (Static Pressure), and RA-T (Return Temperature). The dependents are all N2 AI points.


Figure 16-2: Completed Auto Shutdown Object - Focus Screen

Figure 16-3: Completed Auto Shutdown Object - Dependents


Procedure Overview Table 16-1: Working with Auto Shutdown Objects To Do This Follow These Steps: Add an Auto Shutdown Object Browse to and highlight the multistate point for

which you want to suppress alarm reporting. Press the F3 (Add) key. Select Auto Shutdown from the list of objects that appears. Press Enter. Enter an object name and description. Under Engineering Values, add the Control Point attribute reference and at least one dependent object reference. Press the F3 (Save) key. Press any key to continue. Press F4 (Cancel) to return to the main screen.

Edit an Auto Shutdown Object Browse to and select the Auto Shutdown object that you want to edit. Press the Enter key to open the object. Press the F3 (Edit) key. Edit the fields as desired. Press the F3 (Save) key. Press any key to continue. Press the F4 key to return to the main screen.

Command an Auto Shutdown Object

Browse to and select the Auto Shutdown object that you want to command. Press the F2 (Command) key. Use the spacebar and Tab keys to select either Enable or Disable. Press the Enter key to execute the selected command.

Delete an Auto Shutdown Object

Browse to and select the Auto Shutdown object that you want to delete. Press the Enter key to open the object. Press the Delete key to delete the object. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Auto Shutdown Object

To add an Auto Shutdown object: 1. Browse to and highlight the object containing the multistate point

for which you want to suppress alarm reporting. 2. Press the F3 (Add) key. 3. Select Auto Shutdown from the list of objects that appears. 4. Press Enter. The Auto Shutdown object configuration screen


Figure 16-4: Auto Shutdown Object Screen 5. Enter an object name and description. 6. Under Engineering Values, add the Control Point attribute

reference and at least one dependent object reference. 7. Press the F3 (Save) key. 8. Press any key to continue. 9. Press F4 (Cancel) to return to the main screen.


Editing an Auto Shutdown Object To edit an Auto Shutdown object: 1. Browse to and select the Auto Shutdown object that you want to

edit. 2. Press the Enter key to open the object. 3. Press the F3 (Edit) key. 4. Edit the fields as desired. 5. Press the F3 (Save) key. 6. Press any key to continue. 7. Press the F4 (Cancel) key to return to the main screen.

Commanding an Auto Shutdown Object To command an Auto Shutdown Object: 1. Browse to and select the Auto Shutdown object that you want to

command. 2. Press the F2 (Command) key. The Command field appears. 3. Use the spacebar and Tab keys to select either Enable or Disable. 4. Press the Enter key to execute the selected command.

Deleting an Auto Shutdown Object To delete an Auto Shutdown object: 1. Browse to and select the Auto Shutdown object that you want to

delete. 2. Press the Enter key to open the object. 3. Press the Delete key to delete the object. 4. Press the Tab key to confirm the deletion.


Chapter 17 Working with Multiple Command Objects

Introduction The Multiple Command (MC) object issues a series of commands to multiple objects with a single command action. This chapter describes how to:

• add a Multiple Command object

• edit a Multiple Command object

• add Action Table entries to a Multiple Command object

• delete Action Table entries from a Multiple Command object

• command a Multiple Command object

• delete a Multiple Command object



Key Concepts Multiple Command Object

The Multiple Command object issues a series of commands to multiple objects with a single command action. Commanding the Multiple Command object results in the execution of the commands for a given state. It supports States 1-32. A possible use of the Multiple Command object involves using one command to start building controls for the day. For instance, a Multiple Command object can be added with three states using Occupancy mode states text (Unoccupied, Occupied, and Startup). When the building is in Unoccupied mode, the Multiple Command object can turn off fans, lower the setpoint to 60°F, and secure the doors of the building. During the Startup mode, the Multiple Command object can unlock doors, and start boiler circulating pumps. When in Occupied mode, the Multiple Command object can turn on fans and raise setpoints to 72°F. Another possible use for the Multiple Command object involves using one command to run fan sequencing-type operations. For instance, a number of fans listed in the Action Table attribute start sequentially at one minute intervals by setting the Delay accordingly. The Delay time is cumulative, so if a one minute delay between each fan start is desired, then the Delay times would be 0, 60 120, 180 minutes, etc.

Attributes The values of an object’s attributes determine how the object operates. The Multiple Command object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 17-2. For additional information about the Multiple Command object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Multiple Command.




Commands Priority Determines the order of all commands sent by importance. If it is set to No Priority, commands are sent at each individual priority specified in the Action Table attribute.

Relinquish Default Indicates the default value used for the Present Value attribute when commands are not controlling this object. If this attribute is configured with a value, the object sends commands for the value immediately.

Number Of States Specifies the number of possible Multiple Command object states, 1-32.

States Text Indicates the displayed text for the Present Value.

Action Table (State0…StateN) Contains the list of actions to take for each supported state. Each action contains a slave object reference, a delay, a command and parameters associated with the command, and a priority. The priority in this table is used only when Command Priority is set to No Priority. The delay is the number of seconds before the given command is issued. Command delays can be lengthened or shortened to result in commands being sent out after, before, or at the same time as any other command. Note: The total number of commands identified in the Action

Table command set should not exceed 40.


Procedure Overview Table 17-1: Working with Multiple Command Objects To Do This Follow These Steps: Add a Multiple Command Object

Browse to and highlight the Programming container. Press the F3 (Add) key. Highlight Multiple Command and press Enter. Fill in the fields using Table 17-2. Move the cursor to State 0 under Action Table. Press Enter. Type in an object name. Press the Tab key or the down arrow key to move to the next field. Type in or choose the required information. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Move the cursor to the next State. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Multiple Command Object

Browse to and highlight a Multiple Command object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 17-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Add Action Table Entries to a Multiple Command Object

Browse to and highlight a Multiple Command object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to the appropriate State under Action Table. Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an object name. Press the Tab key or the down arrow key to move to the next field. Type in or choose the required information. Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return to the previous screen. Move the cursor to the next State, if necessary. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete Action Table Entries from a Multiple Command Object

Browse to and highlight a Multiple Command object. Press Enter to open the object. Press the F3 (Edit) key. Move the cursor to the appropriate State under Action Table. Press Enter. Highlight any field for the object reference to be deleted. Press the F2 (Del Item) key. Press the F4 (Back) key to return to the previous screen. Move the cursor to the next state, if necessary. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Multiple Command Object

Browse to and highlight a Multiple Command object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Multiple Command Object

Browse to highlight a Multiple Command object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Multiple Command Object

To add an Multiple Command object: 1. Browse to and highlight the Programming container. 2. Press the F3 (Add) key. The Add Objects list appears. 3. Highlight Multiple Command and press Enter. The Multiple

Command object attribute screen appears (Figure 17-1).

Figure 17-1: Multiple Command Object Attribute Screen 4. Fill in the fields using Table 17-2.



Object Name No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ‘ [ ] If not complete the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Multiple

Command Default is preset and cannot be changed.

Object Category Yes HVAC Use the Spacebar and the Backspace key to view and select options: HVAC, Fire, Security, Services, Administrative.

Object

Enabled Yes True True, False Commands Priority Yes Default Use the Spacebar and the Backspace

key to view and select options. Refer to Write Priority Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Engineering Values

Relinquish Default No Blank Use the Spacebar and the Backspace key to view and select options: Blank, State 0, State 1, State 2, State 3.

Number Of States Yes 4 Use the Spacebar and the Backspace key to view and select options: 1-32 This attribute determines the number of states to appear in the Action Table.

Display

States Text Yes States Use the Spacebar and the Backspace key to view and select options. Refer to States Text in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Action Table Action Table (State0…State32)

Yes Actions to take for each supported state. Each action contains an object reference, a delay, a command, and parameters associated with the command, and possibly a priority. Note: The total number of commands

identified in the Action Table 1 command set should not exceed 40.

5. Move the cursor to State 0 under Action Table. 6. Press Enter. The Multiple Command object State list appears

(Figure 17-2).


Figure 17-2: Multiple Command object State List 7. Type in an object name. 8. Press the Tab key or the down arrow key to move to the next field. 9. Type in or choose the required information. 10. Repeat Steps 8 and 9 for all of the required fields. 11. Press the F3 (Add Item) key to add a blank entry. 12. Repeat Steps 7 through 11 for each object reference to be added. 13. Press the F4 (Back) key to return to the previous screen. 14. Move the cursor to the next State. 15. Repeat Steps 6 through 14 for each State being configured as

determined by the Number of States attribute. 16. Press the F3 (Save) key. 17. Check the User Assistance area of the screen to verify if the save




Editing a Multiple Command Object To edit a Multiple Command object: Note: To delete or add Action Table values, refer to the appropriate


1. Browse to and highlight a Multiple Command object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Multiple Command object attribute screen appears (Figure 17-1).




Adding Action Table Entries to a Multiple Command Object To add Action Table entries to a Multiple Command object: 1. Browse to and highlight a Multiple Command object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Multiple Command object attribute

screen appears (Figure 17-1). 4. Move the cursor to appropriate State under Action Table. 5. Press Enter. The Multiple Command object State list appears. 6. Press the F3 (Add Item) key to add a blank entry. 7. Type in an object name. 8. Press the Tab key or the down arrow key to move to the next field. 9. Type in or choose the required information. 10. Repeat Steps 8 and 9 for all of the required fields. 11. Press the F3 (Add Item) key to add a blank entry. 12. Repeat Steps 7 through 11 for each object reference to be added to

the State list.


13. Press the F4 (Back) key to return to the previous screen. 14. Move the cursor to the next State, if necessary. 15. Repeat Steps 5 through 14 for each State having an object

reference added to it. 16. Press the F3 (Save) key. 17. Check the User Assistance area of the screen to verify if the save



Deleting Action Table Entries from a Multiple Command Object To delete Action Table entries from a Multiple Command object: 1. Browse to and highlight a Multiple Command object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Multiple Command object attribute

screen appears (Figure 17-1). 4. Move the cursor to the appropriate State under Action Table. 5. Press Enter. The Multiple Command object State list appears. 6. Highlight any field for the object reference to be deleted. 7. Press the F2 (Del Item) key. 8. Repeat Steps 6 and 7 for each object reference to be deleted from

the State list. 9. Press the F4 (Back) key to return to the previous screen. 10. Move the cursor to the next State, if necessary. 11. Repeat Steps 5 through 10 for each State having an object

reference deleted from it. 12. Press the F3 (Save) key. 13. Check the User Assistance area of the screen to verify if the save




Commanding a Multiple Command Object To command a Multiple Command object: 1. Browse to and highlight a Multiple Command object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Multiple Command object supports the commands described in Table 17-3.

Table 17-3: Supported Commands Command Description State 0 . . . State 31

Releases Command Priorities 9-15 (scheduling) and then writes to the Present Value at the Default (16) command priority. The state command names and number of commands depend on the States Text and Number of States attributes.

Override Updates the Present Value at Command Priority Operator Override. Choose State 1-31.

Override Release Releases Command Priority Operator Override from Present Value.

Release Releases the identified Command Priority from the specified attribute. Choose an attribute name and command priority.

Release All Releases Command Priorities 3-15 (scheduling), and then writes the highest of the released values at the Default (16) command priority. Command Priorities 1 and 2 remain. Choose an attribute name.

Enable Allows the object’s functionality. Disable Locks all outputs and prevents the object’s functionality.



5. Press Enter.


Deleting a Multiple Command Object To delete a Multiple Command object: 1. Browse to highlight a Multiple Command object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 18 Working with Data Broadcast Objects

Introduction The Data Broadcast object provides a means of sharing globally important data with third-party BACnet devices.

IMPORTANT: Do not create Data Broadcast objects on sites containing only Metasys devices (for example, N30s or M-Series Workstations). Since Metasys devices share data using the Johnson Controls COV mechanism, the Data Broadcast object is not useful.

As the number of Data Broadcast objects on a site increases, the network performance may suffer due to excessive broadcasts. Only use Data Broadcast objects when necessary. This chapter describes how to:

• add a Data Broadcast object

• edit a Data Broadcast object

• command a Data Broadcast object

• delete a Data Broadcast object



Key Concepts Data Broadcast Object

This object can be added as an extension to any object that contains critical data. Typically, this data may be the outdoor air temperature or a value indicating whether a building is occupied. The Data Broadcast then broadcasts an Unconfirmed COV (Change-of-Value) Notification message to non-Metasys BACnet devices containing the referenced data value when it changes.

Unconfirmed COV Notification Unconfirmed COV Notification is a BACnet service that can be used to distribute object attributes of wide interest to many devices simultaneously without a subscription.

Attributes

Input Reference The object and attribute whose value is monitored for COVs. This object’s attribute value, if reliable, is then broadcast in an Unconfirmed COV Notification message.

Reliability The reliability of the Data Broadcast object. The reliability changes to Input Unreliable when errors occur with the Input Reference.

Message Transmits This attribute provides a count of the number of Unconfirmed COV Notification messages that have been sent by the Data Broadcast object. The value rolls over to 0, and continues counting, after reaching 4,294,967,295.

Status The Data Broadcast object sets the Status attribute to OS_UNRELIABLE under any of the following conditions:

• The Reliability attribute is set to a value other than RELIABLE.

• There is a communications problem with the input reference.

• The input reference attribute data type does not support sign up.


Procedure Overview Table 18-1: Working with Data Broadcast Objects

To Do This Follow These Steps: Add a Data Broadcast Object Browse to and highlight the container where you want to add the Data

Broadcast Object. Press the F3 (Add) key. Select Data Broadcast from the list of objects that appears. Press Enter.

Edit a Data Broadcast Object Browse to and select the Data Broadcast object that you want to edit. Press the Enter key to open the object. Press the F3 (Edit) key. Edit the fields as desired. Press the F3 (Save) key. Press any key to continue. Press the F4 key to return to the main screen.

Command a Data Broadcast Object

Browse to and select the Data Broadcast object that you want to command. Press the F2 (Command) key to open the Command field. Use the Spacebar and Tab keys to select either Enable or Disable. Press Enter.

Delete a Data Broadcast Object

Browse to and select the Data Broadcast object that you want to delete. Press the Enter key to open the object. Press the Delete key to delete the object. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Data Broadcast Object

To add a Data Broadcast object: 1. Browse to and highlight the object for which you want to

broadcast a value from one of its attributes. 2. Press the F3 (Add) key. 3. Select Data Broadcast from the list of objects that appears. 4. Press Enter. The Data Broadcast object configuration screen


Figure 18-1: Data Broadcast Object Configuration Screen 5. Enter an object name and description. If you added the Data

Broadcast object to another object the input reference is filled in, otherwise, enter the name of the object attribute for which you want to broadcast a value.

6. Press the F3 (Save) key. 7. Press any key to continue. 8. Press F4 (Cancel) to return to the main screen.


Editing a Data Broadcast Object To edit a Data Broadcast object: 1. Browse to and select the Data Broadcast object that you want to

edit. 2. Press the Enter key to open the object. 3. Press the F3 (Edit) key. 4. Edit the fields as desired. 5. Press the F3 (Save) key. 6. Press any key to continue. 7. Press the F4 key to return to the main screen.

Commanding a Data Broadcast Object To command a Data Broadcast Object: 1. Browse to and select the Data Broadcast object that you want to

command. 2. Press the F2 (Command) key. The Command field appears. 3. Use the spacebar and Tab keys to select either Enable or Disable. 4. Press the Enter key.

Deleting a Data Broadcast Object To delete a Data Broadcast object: 1. Browse to and select the Data Broadcast object that you want to

delete. 2. Press the Enter key to open the object. 3. Press the Delete key to delete the object. 4. Press the Tab key to confirm the deletion.



Chapter 19 Working with Demand Limiting/Load Rolling (DLLR) ObjectsT

Introduction The Demand Limiting/Load Rolling (DLLR) object selectively sheds loads to assure that the total energy consumed during one interval never exceeds a certain limit. This chapter describes how to:

• add a DLLR object

• edit a DLLR object

• command a DLLR object

• delete a DLLR object


Key Concepts Demand Limiting/Load Rolling Controller Object

The Demand Limiting/Load Rolling (DLLR) Controller object reduces utility expenses by selectively shedding loads. Demand limiting reduces energy costs by turning off designated equipment when the amount of energy consumed by the facility approaches a specified target. The purpose of demand limiting is to keep the demand for energy at one time below this target. This reduces energy costs because utility companies often determine charges by the day’s peak demand for energy. Load rolling reduces energy consumption by repeatedly turning off designated equipment at specified intervals. For example, instead of running a fan continuously, load rolling can save energy by turning the fan off for 15 minutes every hour. The DLLR object is the heart of the DLLR feature. The DLLR algorithm inside the DLLR object determines the necessary power reduction to meet the specified target. Power reduction is accomplished by shedding loads. Shedding loads is done by advising the associated loads to switch off their associated outputs, which then leads to the actual physical shedding of loads causing the desired power reduction.

Shedding The process of turning off equipment for Demand Limiting/Load Rolling.

Releasing The process of turning on equipment shed by Demand Limiting/Load Rolling.


Demand Limiting The job of demand limiting is to assure that the total energy consumed during one interval never exceeds a certain limit. The Demand Limit (DL) attribute is the maximum allowed average power during this interval. Hence, the target of DL is to keep the demand below the demand limit. The DLLR executes once each minute to calculate a new amount to shed for DL. The DLLR first sheds loads to satisfy the Load Rolling (LR) target. The DLLR then sheds loads of Priority 4 first to meet the DL target. If this is not possible with loads of Priority 4, then loads of Priority 3 are also used. The same mechanism applies then for loads of Priorities 2 and 1. Loads shed for LR count towards meeting the DL target. If the DL target is not met after shedding all eligible loads, the amount of power not shed is in the DL not Shed attribute. The DLLR can use two different algorithms to determine the amount of power to shed: Fixed Window Algorithm and Sliding Window Algorithm.

Fixed Window Algorithm (FWA) The fixed window is a period of time during which maximum energy consumption must not be exceeded. This period is started and ended by the End-of-Interval (EOI) pulse, which is provided by the power company. Typical values for the interval length are 15 or 30 minutes. As an example, a demand limit of 100 kW with a 15-minute fixed interval means only that the total energy consumption between two EOI pulses must not exceed 25 kWh, but it does not limit the maximum power that can be used. If, for example, only 10 kWh were consumed during the first 10 minutes of a fixed 15-minute interval, there are still 15 kWh allowed to be consumed during the last 5 minutes of the interval. This results in an allowed average power of 180 kW during the last 5 minutes of the interval, which is 80% above the demand limit, and still no loads would have to be shed.


Sliding Window Algorithm (SWA) The sliding window is a period of time during which maximum energy consumption must not be exceeded. This period has a fixed length, here called interval length, and it always ends at the current time. A typical value for the interval length is 15 minutes. As an example, a demand limit of 100 kW with a 15 minute sliding interval means only that the maximum energy consumption within any 15 consecutive minutes must not exceed 25 kWh, but it does not limit the maximum power that can be used. However, since every minute is also the beginning of a new sliding interval, the Sliding Window Algorithm reacts every minute and tries to prevent the demand from getting above the demand limit. The Fixed Window Algorithm reacts only when there is danger of surpassing the maximum energy during the interval.

Interaction with Other Objects Note: For more information about the DLLR object’s interaction

with other objects, refer to Appendix A: Building an Energy Management Application (LIT-6892310) in this document.

Load Objects The Loads sign up for Change-of-Value (COV) on the DLLR’s DLLR Status attribute. This attribute informs the loads about the current state of their DLLR. The DLLR can enter the Register mode by setting DLLR Status temporarily to Register, which causes the signed up loads to register. The DLLR signs up for trigger on some internal attributes of the Loads, which allows the DLLR to be constantly informed about the eligibility of Loads to be used as sheddable Loads. Which and how many attributes are used for this purpose must be determined after the overall system communication performance is evaluated.


Meter Objects The DLLR generally can use any object as its meter object, as long as that object fulfills the requirements listed below. Currently, the Pulse Meter object is the best suited object for this purpose, but Analog Input and Analog Value objects are possible when they meet requirements. The following requirements must be met:

• A permanent communication path must exist between the meter object and the DLLR.

• The meter object must calculate a new rate exactly once every 60 seconds.

• This rate must be the average power over the just elapsed minute and must be provided in the meter object’s Present Value attribute, which has to support signup for COV.

• The meter object’s Rate Units must be identical to the DLLR’s Rate Units.

EOI Attribute Note: The use of an End-of-Interval (EOI) input is required for the

Fixed Window Algorithm only. It must not be used for the Sliding Window Algorithm.

The attribute supplying the End-of-Interval pulse is defined by the attribute reference entered in the DLLR’s EOI attribute. This EOI attribute can be any attribute of any object, as long as the following requirements are met:

• A permanent communication path must exist between this attribute and the DLLR.

• This attribute must be a numerical attribute, where a raise from 0 to 1 indicates the end of the interval, and thus, the beginning of the next interval.

• The object providing this attribute must support signup for trigger on this attribute.


Attributes The values of an object’s attributes determine how the object operates. The DLLR object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 19-2. For additional information about the DLLR object and its attributes, refer to the Object Dictionary.






DL Mode Shows the operation mode of Demand Limiting. The mode Monitor Only means that no Load is to be shed.

Demand Limit Indicates the maximum allowed average demand during the interval.

Algorithm Indicates the type of mathematical procedure used to determine the amount to shed for demand limiting.

Meter Object References the object supplying the instantaneous demand.

Interval Length Indicates the input used in the algorithm to indicate the number of minutes in the sliding and fixed windows.


Offline Shed Rate Indicates the absolute amount of power that Demand Limiting can increase or decrease the current amount of power shed per minute when the meter is offline. This value is specified in power/minute. Positive numbers increase, negative numbers decrease the amount shed.

Display Precision Indicates the rounded position and decimal places to display for this object. Indicates the operation mode of Load Rolling. The mode Monitor Only means that no Loads are to be shed.

LR Target Indicates the desired power reduction through Load Rolling.

Consumption Units Defines the unit for energy values; for example, kWh.

Offline Shed Rate Units Defines the unit used for offline shed rate value; for example, kW/minute.

Rate Units Defines units for demand values; for example, kW.

Limit Elevation Indicates the amount in percent by which the demand limit is increased at the beginning of the next interval. The increased demand limit is the starting value of the the demand limit profile, in the Fixed Window Algorithm.

EOI Attribute Indicates the Attribute reference to the EOI pulse, in the Fixed Window Algorithm.

Sensitivity Indicates the level of aggression for shedding Loads, in the Sliding Window Algorithm.

Registering Phase Defines the time in seconds that the DLLR remains in the Register mode to get all signed up Loads to register.


Algorithm Delay Defines the time in seconds that the DLLR puts between the execution of the meter object and the execution of the DL algorithm. This allows the newest values to be reported by the meter before the DL algorithm executes.

Restart Register Indicates (if set) if the DLLR enters the Register mode after a restart.


Procedure Overview Table 19-1: Working with DLLR Objects To Do This Follow These Steps: Add a DLLR Object Browse to and highlight the Energy container. Press the F3 (Add) key.

Highlight DLLR and press Enter. Fill in the fields using Table 19-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a DLLR Object Browse to and highlight a DLLR object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 19-2. Press the (F3) Save key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a DLLR Object Browse to and highlight a DLLR object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a DLLR Object Browse to and highlight a DLLR object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a DLLR Object

To add a DLLR object: 1. Browse to and highlight the Energy container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight DLLR and press Enter. The first of two DLLR attribute

screens appears (Figure 19-1).

Figure 19-1: DLLR Object Attribute Screen (1 of 2)


Figure 19-2: DLLR Object Attribute Screen (2 of 2) 4. Fill in the fields using Table 19-2.

Table 19-2: Attribute Entry Requirements Section Attribute Required Default Options/Range


Description No Blank Maximum 40 characters Object Type Yes DLLR The default is preset and cannot be changed. Object Category


Object


LR Mode Yes LR Monitor only

Use the Spacebar and Backspace key to view and select options: LR Monitor only, LR Shedding.

Load Rolling

LR Target Yes 0.0 kW Enter a float value that is greater than or equal to zero.



Screen Area (Cont.)


DL Mode Yes DL Monitor only

Use the Spacebar and Backspace key to view and select options: DL shedding, DL monitor only.

Meter Object Yes Blank Enter the exact name of the Pulse Meter object dedicated to this DLLR object.

Algorithm Yes None Use the Spacebar and Backspace key to view and select options: None, Fixed Window, Sliding Window.

Interval Length

Yes 15 minutes Enter an integer value between 3 and 60 minutes.

Offline Shed Rate

Yes 0.0 kW/minutes

Enter a float value.

Demand Limit Yes 0.0 kW Enter a float value that is greater than or equal to zero.

Rate Units Yes kW Use the Spacebar and Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Consumption Units

Yes kWh Use the Spacebar and Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Demand Limiting

Offline Shed Rate Units

Yes kW/min Use the Spacebar and Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Sliding Window Alg

Sensitivity Yes Medium Use the Spacebar and Backspace key to view and select options: Low, Medium, High.

Display Display Precision


Limit Elevation

Yes 0% Enter an integer value between 0% and 99%. Fixed Window Alg

EOI Attribute Yes Blank Enter an object and attribute name. Registering Phase

Yes 15 seconds Enter an integer value that is greater than or equal to zero.

Advanced Setup

Algorithm Delay

Yes 5 seconds Enter an integer value that is greater than or equal to zero.

Restart Register

Yes False Use the Spacebar and Backspace key to view and select options: True = The DLLR enters the Register mode after a restart. False = The DLLR does not enter Register mode after a restart.





Editing a DLLR Object To edit a DLLR object: 1. Browse to and highlight a DLLR object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The DLLR object attribute screen appears (Figure 19-1 and Figure 19-2).

4. Edit the fields using Table 19-2. 5. Press the (F3) Save key. 6. Check the User Assistance area of the screen to verify if the save




Commanding a DLLR Object To command a DLLR object: 1. Browse to and highlight a DLLR object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The DLLR object supports the commands listed in Table 19-3.

Table 19-3: Supported Commands Command Description Force Register Use this command only when necessary; for example, when

loads have been lost or when there are many changes to the loads. This command reinitializes connections between Load and DLLR objects. Load shedding is suspended during this time. Selecting False only updates the database while selecting True clears out and then updates the database.

Enable Allows the DLLR object’s functionality. Disable Prohibits the DLLR from sending shed load commands.



5. Press Enter.

Deleting a DLLR Object To delete a DLLR object: 1. Browse to and highlight a DLLR object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 20 Working with Load Objects T

Introduction Load objects identify pieces of equipment, corresponding to an N2 Binary Output, Binary Value (BV), Multistate Output (MSO), Multistate Value (MSV), or Multiple Command (MC) object, that consumes a certain noticeable amount of energy. Load objects register with the DLLR (Demand Limiting/Load Rolling) object, meaning they let the DLLR know they exist and can be shed to save energy when appropriate. This chapter describes how to:

• add a Load object

• edit a Load object

• command a Load object

• delete a Load object


Key Concepts Load Object

This object allows a user to shut off equipment based on the evaluation of information from the DLLR object (how much energy is used on average and how much energy does not need to be used). One Load object exists for every Load that participates in the DLLR feature. The Load object receives a Shed Load command from the DLLR object and takes immediate actions to switch off its associated output, which then leads to the actual physical Load shedding, causing the desired power reduction. The Load object is responsible for monitoring the conditions that require the Load to be released. The request to release a Load can also come from outside of the Load object. To achieve optimal operation, the Load object should be placed into the device as close as possible to the device containing the output attribute. If comfort override and output alarm checking are defined, these attributes should be also very close to the Load object. The comfort override attribute and the DLLR may be shared by several Load objects, but the output attribute must not be referenced by more than one Load object. The Load object interacts with other objects. For more information, refer to Appendix A: Building an Energy Management Application (LIT-6892310) in this document.

Shedding The entire process of turning off equipment for DLLR.

Releasing The entire process of turning on equipment shed by DLLR.

Attributes The values of an object’s attributes determine how the object operates. The Load object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 20-2. For additional information about the Load object and its attributes, refer to the Object Dictionary.




Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Load.



Comfort Alarm Attr (Attribute) References the attribute supplying the comfort override alarm condition.

Output Alarm Attr (Attribute) References the attribute supplying the output alarm condition.

Output Attribute References the attribute controlling the physical output.

DLLR Object Identifies the DLLR object that determines the load to be shed.

Load Priority Specifies the load priority.

Load Use Specifies the use of the Load object for either DL only, LR only, or both DL and LR.

Number of States Indicates the output attribute’s number of states.

Shed State Specifies the output attribute state’s to be switched to when the load is shed.


Load Locked Indicates that the Load object is locked and will not shed its load. It does not prevent the load from being released.

Restart Release Specifies if the load should be released when the Load feature is started.

Alarm Release Specifies if the load should be released upon release time when the DLLR object is in the alarm state.

Offline Release Specifies if the load should be released upon release time when it has lost communication with its DLLR object.

Rate 1 Indicates the absolute power difference when output changes from State 1 to State 0.



Rate Units Defines unit for demand values, for example, kW.

Min (Minimum) Shed Time Specifies the minimum time in which the Load must be shed.

Max (Maximum) Shed Time Specifies the maximum amount of time the load can be shed in minutes. This time must be equal to or greater than the Minimum Shed Time.

Min (Minimum) Release Time Specifies the minimum amount of time in which the load must be released in minutes.



Registered Delay Defines the delay in seconds for registering at the DLLR object after the Load object is informed by the DLLR object that it is time to register, or after the Load feature is started. This attribute can be varied to avoid too many Load objects registering at the DLLR object at the same time and to help in getting a certain order in the DLLR object’s database.

Period Defines the time period of the registering attempts in seconds.

Restart Register Specifies if the load should register when the Load object is started or restarted.


Procedure Overview Table 20-1: Working with Load Objects To Do This Follow These Steps: Add a Load Object Browse to and highlight the Energy container. Press the F3 (Add) key.

Highlight Load and press Enter. Fill in the fields using Table 20-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Load Object Browse and highlight a Load object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields according to Table 20-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Load Object Browse to and highlight a Load object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Load Object Browse to and highlight a Load object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Load Object

To add a Load object: 1. Browse to and highlight the Energy container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Load and press Enter. The first of two Load object

attribute screens appears (Figure 20-1 and Figure 20-2).

Figure 20-1: Load Object Attribute Screen (1 of 2)


Figure 20-2: Load Object Attribute Screen (2 of 2) 4. Fill in the fields using Table 20-2.



Object Object Name No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ’ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Load The default is preset and cannot be changed. Object

Category Yes HVAC Use the Spacebar and Backspace key to view

and select options: HVAC, Fire, Security, Services, Administrative.


Setup Comfort Alarm Attribute

Yes Blank Enter the exact object and attribute name of the object controlling Comfort Alarm.

Output Alarm Attribute

Yes Blank Enter the exact object and attribute name of the object controlling Output Alarm.

Output Attribute

Yes Blank Enter the exact object and attribute name of the object controlling the Output.

DLLR Object Yes Blank Enter the exact name of the DLLR object. Load Priority Yes 4 Enter a whole number from 1 to 4. Continued on next page . . .


Screen Area (Cont.)


Setup (Cont.)

Load Use Yes For DL and LR

Use the Spacebar and Backspace key to view and select options: For DL only, For LR only, For DL and LR.

Number of States

Yes 2 Enter a whole number from 2 to 4.

Shed State Yes 0 Enter a whole number from 0 and 2 (must be at least 2 less than the Number of States).

Load Locked Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Restart Release

Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Alarm Release Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Offline Release


Rate 1 Yes 0.0. kW Enter a float value greater than or equal to 0. Rate 2 Yes 0.0. kW Enter a float value greater than or equal to 0. Rate 3 Yes 0.0. kW Enter a float value greater than or equal to 0. Rate Units Yes kW Use the Spacebar and Backspace key to view

and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Min Shed Time Yes 1 minute Enter a whole number/Integer value greater than 0.

Max Shed Time

Yes 1 minute Enter a value greater than 0 or equal to Minimum Shed Time.

Min Release Time

Yes 1 minute Enter a value greater than 0 or equal to Minimum Shed Time.

Display Precision


Advanced Setup

Registering Delay

Yes 0 second Enter an integer value greater than or equal to 0.

Period Yes 86400 seconds

Enter an integer value greater than or equal to 0.

Restart Register

Yes False Use the Spacebar and Backspace key to view and select options: False, True





Editing a Load Object To edit a Load object: 1. Browse and highlight a Load object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Load object attribute screen appears (Figure 20-1 and Figure 20-2).

4. Edit the fields according to Table 20-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save




Commanding a Load Object To command a Load object: 1. Browse to and highlight a Load object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Load object supports the commands described in Table 20-3.

Table 20-3: Supported Commands Command Description Unlock Load Unlocks load making it available to shed. Lock Load Locks load making it unavailable to shed. Force Register Re-notifies the DLLR object that the Load object exists.

Used if the user suspects the Load object is not registered correctly.

Release Load Releases and sheds the Load while obeying all constraints concerning the releasing of loads, such as when the Minimum Shed Time has not yet elapsed, the Load is not yet released, but will wait until it becomes eligible to be released. Options include:

• For DL • For LR • For DL and LR

Force Release Load Releases and sheds the load while ignoring all constraints concerning the release of loads.

Enable Allows the functionality of the Load object and makes the Load available to shed.

Disable Prevents the functionality of the Load object and makes the Load unavailable to shed.



5. Press Enter.

Deleting a Load Object To delete a Load object: 1. Browse to and highlight a Load object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 21 Working with Pulse Meter Objects T

Introduction The Pulse Meter object calculates a rate of change in the Pulse Counter. It also totalizes the counted pulses and converts them into units of consumption. This chapter describes how to:

• add a Pulse Meter object

• edit a Pulse Meter object

• command a Pulse Meter object

• delete a Pulse Meter object


Key Concepts Pulse Meter Object

Working with the Pulse Meter object allows a user to determine the rate of energy used and accumulated energy used. The Pulse Meter object accumulates the differences between consecutive reads of the integer value provided by a pulse counter and calculates the rate of change between each reading of the value. Note: The Pulse Meter object handles only counters that count

forward.

The Pulse Meter object must be tied to an N2 Pulse Counter object to access the counter value that resides in the pulse counter hardware device (which is hardwired to the pulse input). The N2 Pulse Counter object may be hardware specific, while the Pulse Meter object is hardware independent. Multiple Pulse Meter objects may share the same N2 Pulse Counter object. The Pulse Meter object must reside on the same device as the N2 Pulse Counter device. The Pulse Meter object interacts with other objects. For more information, refer to Appendix A: Building an Energy Management Application (LIT-6892310) in this document.

Attributes The values of an object’s attributes determine how the object operates. The Pulse Meter object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 21-2. For additional information about the Pulse Meter object attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Pulse Meter.




Meter Active Specifies whether the associated Meter object should be collecting data.

Counter Object Specifies the associated Pulse Counter object.

Rollover Limit Specifies the highest counter value before the pulse counter on the pulse counting device rolls over to zero.

Rate Units Specifies the engineering units for all rate attributes.

Rate Constant Specifies a constant used in the algorithm.

Rate Limit Specifies the highest allowed Present Value before using Rate Default.

Rate Default Specifies the value of Present Value when the calculated rate exceeds the Rate Limit.

Sample Time Specifies the period of time for automatic executions of the algorithm.

Consumption Units Specifies the engineering units for all consumption attributes.

Pulse Consumption Specifies a constant used in the algorithm.



Procedure Overview Table 21-1: Working with Pulse Meter Objects To Do This Follow These Steps: Add a Pulse Meter Object Browse to and highlight the Energy container. Press the F3 (Add) key.

Highlight Pulse Meter and press Enter. Fill in the fields using Table 21-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Pulse Meter Object Browse to and highlight a Pulse Meter object. Press Enter to open the object. Press the F3 (Edit) key. Fill in the fields using Table 21-2. Press the (F3) Save key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Pulse Meter Object

Browse to and highlight a Pulse Meter object. Press the F2 (Command) key. Use the Spacebar and Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Pulse Meter Object Browse to and highlight a Pulse Meter object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Pulse Meter Object

To add a Pulse Meter object: 1. Browse to and highlight the Energy container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Pulse Meter and press Enter. The Pulse Meter object


Figure 21-1: Pulse Meter Object Attribute Screen 4. Fill in the fields using Table 21-2.





Description No Blank Maximum 40 characters Object Type Yes Pulse

Meter The default is preset and cannot be changed.

Object Category



Setup Counter Object Yes Blank Enter the exact name of the object that will provide the pulse counter value.

Rollover Limit Yes 32767 Enter a whole number. The value depends on the hardware used for the Pulse Counter: • N2 open = 32767 (default) • SYS 91 = depends on the configuration

Rate Units Yes kW Use the Spacebar and the Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Rate Constant Yes 3600 Enter a float value greater than zero. Rate Limit Yes 3.402823

E38 Enter a float value greater than or equal to zero.

Rate Default Yes 0 kW Enter a float value greater than or equal to zero. Sample Time Yes 60

seconds Enter a whole number greater than or equal to zero.

Consumption Units

Yes kWh Use the Spacebar and the Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Pulse Consumption

Yes 1.0 kWh Enter a float value greater than zero. Must be set to the physical quantity that each single pulse represents.

Display Precision

Yes 10ths Use the Spacebar and the Backspace key to view and select options. Refer to Display Precision Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).





Editing a Pulse Meter Object To edit a Pulse Meter object: 1. Browse to and highlight a Pulse Meter object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Pulse Meter object attribute screen appears (Figure 21-1).

4. Fill in the fields using Table 21-2. 5. Press the (F3) Save key. 6. Check the User Assistance area of the screen to verify if the save



Commanding a Pulse Meter Object To command a Pulse Meter object: 1. Browse to and highlight a Pulse Meter object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and Backspace key to cycle through the list until

the desired command appears. The Pulse Meter object supports the commands described in Table 21-3.

Table 21-3: Supported Commands Command Description Reset Resets the Pulse Meter, including the Consumption

attribute. Start Meter Resumes metering. Stop Meter Stops metering. Enable Starts metering dependent on the Meter Active

attribute (True). Disable Disables metering independent of the Meter Active

attribute (True or False).

4. Press Enter.


Deleting a Pulse Meter Object To delete a Pulse Meter object: 1. Browse to and highlight a Pulse Meter object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 22 Working with Utility Profile Objects

Introduction The Utility Profile object is a standalone object that takes over some functions provided by the DLLR (Demand Limiting/Load Rolling) application. Working with this object allows a user to report energy usage. This chapter describes how to:

• add a Utility Profile object

• edit a Utility Profile object

• command a Utility Profile object

• delete a Utility Profile object



Key Concepts Utility Profile Object

The Utility Profile object collects utility data from a Pulse Meter object and a DLLR object. The associated Pulse Meter object should be dedicated to the Utility Profile object, since it will be activated, de-activated, and reset by the Utility Profile object. The DLLR object may be shared by multiple Utility Profile objects. This is the case when separate utility profiles should be generated for different tracking periods, such as daily, weekly, and monthly. For each tracking period it logs the following:

• the energy consumption

• the time and date of the interval with the highest energy consumption

• the time and date of the interval with the highest sum of energy consumption and energy not consumed due to shedding

For more information about how the Utility Profile object interacts with other objects, refer to Appendix A: Building an Energy Management Application (LIT-6892310) in this document.

Attributes The values of an object’s attributes determine how the object operates. The Utility Profile object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 22-2. For additional information about the Utility Profile object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Utility Profile.




Meter Active Specifies whether the associated Meter object should be collecting data.

DLLR Object Specifies the associated DLLR object.

Meter Object Specifies the associated Pulse Meter object.

Tracking Periods Indicates the period during which consumption is totaled before being reset, typically a billing period.


Consumption Units Specifies units for all energy values (kWh).

Rate Units Specifies units for all demand values (kW).


Procedure Overview Table 22-1: Working with Utility Profile Objects To Do This Follow These Steps: Add a Utility Profile Object Browse to and highlight the Energy container. Press the F3 (Add) key.

Highlight Utility Profile and press Enter. Fill in the fields using Table 22-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Utility Profile Object Browse to and highlight a Utility Profile object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 22-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Utility Profile Object

Browse to and highlight a Utility Profile object. Press the F2 (Command) key. Use the Spacebar and Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Utility Profile Object Browse to and highlight a Utility Profile object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Utility Profile Object

To add a Utility Profile object: 1. Browse to and highlight the Energy container. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Utility Profile and press Enter. The Utility Profile object


Figure 22-1: Utility Profile Object Attribute Screen 4. Fill in the fields using Table 22-2.




Description No Blank Maximum 40 characters Object Type Yes Utility Profile The default is preset and cannot be

changed. Object


view and select options: HVAC, Fire, Security, Services, Administrative.


Setup DLLR Object Yes Blank Enter the exact name of the associated DLLR object.

Meter Object Yes Blank Enter the exact name of the associated Meter object.

Tracking Periods

Yes 31 Enter a whole number from 1 to 31.

Display Precision

Yes 10ths Use the Spacebar and the Backspace key to view and select options. Refer to Display Precision Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Consumption Units

Yes kWh Use the Spacebar and the Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Rate Units Yes kW Use the Spacebar and the Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).





Editing a Utility Profile Object To edit a Utility Profile object: 1. Browse to and highlight a Utility Profile object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Utility Profile object attribute screen appears (Figure 22-1).




Commanding a Utility Profile Object To command a Utility Profile object: 1. Browse to and highlight a Utility Profile object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and Backspace key to cycle through the list until

the desired command appears. The Utility Profile object supports the commands described in Table 22-2.

Table 22-3: Supported Commands Command Description Display Displays the customized profile summary on the active user

interface. Print Sends the customized utility profile summary to be printed at

an identified printer. Enter the exact name of the Printer object.

Reset Resets and starts a new tracking period. Start Meter Allows metering. Stop Meter Prevents metering. Enable Starts metering dependent on the Meter Active attribute

(True). Disable Disables metering independent of the Meter Active attribute

(True or False).


4. If the desired command appears with additional parameters below it, press the Tab key to highlight the field and either type in the necessary information or use the Spacebar and Backspace key to cycle through the list of options.

5. Press Enter.

Deleting a Utility Profile Object To delete a Utility Profile object: 1. Browse to and highlight a Utility Profile object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 23 Working with Analog Totalization Objects

Introduction An Analog Totalization object maintains a total for the data recorded at an analog sensor. It answers the question “How much?” and is typically used to measure the consumption of a supply, such as steam, electricity, or chilled water. The input sensor provides a value corresponding to the amount of consumption or flow. This chapter describes how to:

• add an Analog Totalization object

• edit an Analog Totalization object

• command an Analog Totalization object

• delete an Analog Totalization object

© November, 2001 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-6892230 Software Release 5.0


Key Concepts Analog Totalization Object

The Analog Totalization object can be added to any container or object in the hierarchy. The Analog Totalization object references any analog attribute value for input data calculations. Note: The Input Reference of an Analog Totalization object should

refer to a signed or unsigned integer, a signed or unsigned long, or a floating point based attribute in order to perform as intended. Analog Totalization objects referencing other attribute data types (e.g., Boolean) yield unusual results, though not necessarily unusable results. Neither the VT100 nor Project Builder give an error message when this object is attached to any attribute other than signed or unsigned integer, signed or unsigned long, or floating point based attributes.

Typical uses of Analog Totalization include:

• to determine how many kilowatt/hours were used in a week

• to determine how much steam is used in a week

• to totalize a calculated value (for instance, degree days) The Analog Totalization formula and an example are illustrated in Table 23-1.

Table 23-1: Analog Totalization Formula and Example Calculations Analog Totalization

Calculation

Formula Present Value + (Input x Period)/(Time Factor x Scalefactor) = Present Value (New) Example 200 gallons + (20 gallons x 1 minute)/(60 seconds x 1) = 220 gallons


Analog Totalization Object Reset Table 23-2 describes under what conditions the reset of the Analog Totalization object occurs and what conditions result due to the reset.

Table 23-2: Analog Totalization Reset Reset Conditions Occurs: • When a Reset Command is received.

• When the following attributes are rewritten: Low Cutoff Value Timebase Scalefactor Reset Totalize Limit, when the Present Value has reached the currently defined Totalize Limit value Rollover, when the Present Value has reached the currently defined Totalize Limit value

• Following a return from a Totalization object’s disabled state to an enabled state

Results In: • Termination of ongoing calculations • Restoration of the Present Value and Rollover Count values to their initial

states • Retriggering of all Change-of-Value state changes

Attributes The values of an object’s attributes determine how the object operates. The Analog Totalization object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 23-4. For additional information about the Analog Totalization object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Analog Totalization.




Input Reference Specifies the object and attribute totalized by this object. If this attribute is unreliable or falls below the Low Cutoff Value, totalization is temporarily suspended.

Timebase Establishes the time frame on which the calculated totalization value is based. Processing a write of this attribute sets the Reset condition.

Scalefactor Indicates the value used to scale the totalized value to either a larger or smaller value than would otherwise result. Processing a write of this attribute sets the Reset condition. This value must be greater than zero.

Totalize Limit Defines a threshold value the Present Value must meet or exceed in order for the totalization object to take special action. The special action taken depends on the setting defined for the Rollover attribute.

Low CutOff Value Defines a minimum input value; values beneath this minimum input value are not totalized. With this attribute, sensor errors associated with the low readings of flow sensors can be eliminated. Writing this attribute forces a Reset condition.

Rollover Defines the special action that the Analog Totalization object must take when the Present Value reaches the Totalize Limit value. If the Rollover attribute is set to False, the Runtime Totalization object ceases further operation when the Present Value equals or exceeds the Totalize Limit value. If it is True, it resets the Present Value to 0.0 and resumes a new totalization cycle.

Units Indicates the measurement units of this object.



Present Value Represents the current totalized value of the object. Writing this attribute (changing it) forces the Reset condition. Present Value appears to the right of the object name in the container hierarchy after the object is created.

Reset Forces a Reset condition and then returns to False, after a write of this attribute to True. The reading of this attribute (viewing it on the user interface) always returns a False condition. This attribute is not displayed on the attributes screen but it is useful for advanced diagnostics.

Rollover Count Indicates how many rollovers have occurred since the object started totalization, when the Rollover attribute is True. This is an internal attribute value. It is not displayed on the attributes screen but it is useful for advanced diagnostics.


Procedure Overview Table 23-3: Working with Analog Totalization Objects To Do This Follow These Steps: Add an Analog Totalization Object

Browse to and highlight the container or object where the Analog Totalization object is to be added. Press the F3 (Add) key. Select Analog Totalization and press Enter. Fill in the fields using Table 23-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Analog Totalization Object

Browse to and highlight an Analog Totalization object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 23-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Analog Totalization Object

Browse to and highlight an Analog Totalization object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete an Analog Totalization Object

Browse to and highlight an Analog Totalization object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Analog Totalization Object

To add an Analog Totalization object: 1. Browse to and highlight the container or object where the Analog

Totalization object is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Select Analog Totalization and press Enter. The Analog

Totalization object attribute screen appears (Figure 23-1).

Figure 23-1: Analog Totalization Object Attribute Screen 4. Fill in the fields using Table 23-4.



Object Name

No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ’ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Analog

Totalization The default is preset and cannot be changed.

Object Category



Object

Input Reference

Yes If this Analog Totalization object is being added to a container, the exact name of the object and attribute to be totalized must be entered. If this Analog Totalization object is being added to an object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.

Engineering Values

Timebase Yes Hours Use the Spacebar and Backspace key to view and select options: Hours, Seconds, Minutes.

Scalefactor Yes 1.0 A float value greater than 0 Totalize

Limit No Blank A float value greater than 0

Low Cutoff Value

Yes 0.0 A float value greater than 0

Rollover Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Display Units Yes Blank Use the Spacebar and the Backspace key to cycle through the list of options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Display Precision

Yes 10ths Use the Spacebar and Backspace key to cycle through the list of options. Refer to Display Precision Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).





Editing an Analog Totalization Object To edit an Analog Totalization object: 1. Browse to and highlight an Analog Totalization object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Analog Totalization object attribute screen appears (Figure 23-1).




Commanding an Analog Totalization Object To command an Analog Totalization object: 1. Browse to and highlight an Analog Totalization object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Analog Totalization object supports the commands listed in (Table 23-5).

Table 23-5: Supported Commands Command Description Reset Resets the Present Value to zero. Enable Instructs the Analog Totalization object to start analog totalizing

the Input Reference object. Disable Instructs the Analog Totalization object to stop analog totalizing

the Input Reference object.

4. Press Enter.


Deleting an Analog Totalization Object To delete an Analog Totalization object: 1. Browse to and highlight an Analog Totalization object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 24 Working with Event Totalization Objects

Introduction The Event Totalization object tracks the number of events or pulses over time, meaning it counts the number of transitions in an object’s value. This chapter describes how to:

• add an Event Totalization object

• edit an Event Totalization object

• command an Event Totalization object

• delete an Event Totalization object



Key Concepts Event Totalization Object

An Event Totalization object records a total for the number of times any binary event has occurred. Unlike the other types of totalization, Event Totalization updates its Present Value output each time an event occurs, instead of calculating the value every minute. The Event Totalization object can be added to any container or object in the hierarchy. The Event Totalization object references any object and one of its attributes for input data calculations. Note: The Input Reference of an Event Totalization object should

refer to enumeration or Boolean based attributes in order to perform as intended. Event Totalization objects referencing other attribute data types (e.g., floating point) yield unusual results, though not necessarily unusable results. Neither the VT100 nor Project Builder give an error message when this object is attached to any attribute other than enumeration or Boolean based attributes.

Typical uses for Event Totalization are determining:

• how many times a motor started

• how often a sensor was in alarm

• how many cars entered a parking lot The Event Totalization formula and an example are illustrated in Table 24-1. Refer to the Attributes section of this chapter for information about attributes used in the calculation.

Table 24-1: Event Totalization Formula and Example Calculations Event Totalization

Calculation

Formula Present Value + (Value per Pulse/Scalefactor) = Present Value (New) Example 1 person + (1/1) = 2 persons (Occupancy)


Event Totalization Object Reset Describes under what conditions the reset of the Event Totalization object occurs and what conditions result due to the reset.

Table 24-2: Event Totalization Reset Reset Conditions Occurs: • When a Reset Command is received.





Attributes The values of an object’s attributes determine how the object operates. The Event Totalization object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 24-4. For additional information about the Event Totalization object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Event Totalization.




Input Reference Specifies the object and attribute totalized by this object. If this attribute is unreliable, totalization is temporarily suspended.

Reference Defines the state (0-31) in which the Input Reference attribute must be for totalization to be active. Writing this attribute forces the Reset condition.

Value Per Pulse Indicates the unit value of the Input Reference for pulse totalization. For the event totalization, the value is 1. Writing this attribute sets the Reset condition.

Transition Defines which transitions should be counted. If the value is Entering State, it counts the number of transitions into a given state as indicated by the Reference attribute. If the value is Count All, it counts all state transitions. Writing this attribute sets the Reset condition.

Scalefactor Indicates the value used to scale the totalized value to either a larger or smaller value than would otherwise result. Writing this attribute sets the Reset condition.

Totalize Limit Defines a threshold value the Present Value must meet or exceed in order for the totalization object to take special action. The special action taken depends on the setting defined for the Rollover attribute.

Rollover Defines the special action the totalization object must take when the Present Value reaches the Totalize Limit value. If the Rollover attribute is set to False, the Runtime Totalization object ceases further operation when the Present Value equals or exceeds the Totalize Limit value. If it is True, it will reset the Present Value to 0.0 and resume a new cycle of totalization.




Present Value Represents the current totalized value of the object. Writing this attribute forces the Reset condition. Present Value appears to the right of the object name in the container hierarchy after the object is created.

Reset Forces a Reset condition, after a write of this attribute to True. The reading of this attribute always returns a False condition. It is not displayed on the attributes screen but it is useful for advanced diagnostics.



Procedure Overview Table 24-3: Working with Event Totalization Objects To Do This Follow These Steps: Add an Event Totalization Object

Browse to and highlight the container or object where the Event Totalization object is to be added. Press the F3 (Add) key. Select Event Totalization and press Enter. Fill in the fields using Table 24-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Event Totalization Object

Browse to and highlight an Event Totalization object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 24-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Event Totalization Object

Browse to and highlight an Event Totalization object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list of commands until the desired command appears. Press Enter.

Delete an Event Totalization Object

Browse to and highlight an Event Totalization object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Event Totalization Object

To add an Event Totalization object: 1. Browse to and highlight the container or object where the Event

Totalization object is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Select Event Totalization and press Enter. The Event Totalization

object attribute screen appears (Figure 24-1).

Figure 24-1: Event Totalization Object Attribute Screen 4. Fill in the fields using Table 24-4.





Description No Blank Maximum 40 characters Object

Type Yes Event


Object Category



Input Reference

Yes If this Event Totalization object is being added to a container, the exact name of the object and attribute to be totalized must be entered. If this Event Totalization object is being added to another object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.

Engineering Values

Reference Yes State 0 Use the Spacebar and Backspace key to cycle through the list of options: 0 to 31.

Value Per Pulse

Yes 1 A float value equal to or greater than 0

Transition Yes Entering State

Use the Spacebar and Backspace key to cycle through the list of options: Entering State, Count All.

Scalefactor Yes 1.0 A float value greater than 0 Totalize

Limit No Blank A float value greater than 0

Rollover Yes False Use the Spacebar and Backspace key to view and select options: True, False.

Display Units Yes Blank Use the Spacebar and Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Display Precision

Yes 1s Use the Spacebar and Backspace key to view and select options. Refer to Display Precision Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).



7. Press any key to continue.


8. Press the F4 (Cancel) key to return to the container hierarchy.

Editing an Event Totalization Object To edit an Event Totalization object: 1. Browse to and highlight an Event Totalization object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Event Totalization object attribute screen appears (Figure 24-1).




Commanding an Event Totalization Object To command an Event Totalization object: 1. Browse to and highlight an Event Totalization object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

of commands until the desired command appears. The Event Totalization object supports the commands identified in Table 24-5.

Table 24-5: Supported Commands Command Description Reset Resets the Present Value to zero. Enable Instructs the Event Totalization object to start event totalizing the

Input Reference object. Disable Instructs the Event Totalization object to stop event totalizing the

Input Reference object.

4. Press Enter.


Deleting an Event Totalization Object To delete an Event Totalization object: 1. Browse to and highlight an Event Totalization object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Troubleshooting When configuring an Event Totalization object with a Multistate Value object, the user can inadvertently specify a value for the Reference attribute that is unobtainable within the Multistate Value object. The Reference attribute dictates the state in which the targeted object has its specified events recorded. This situation occurs because the user is prompted with a generic list of state selections ranging from State 0, State 1, State 2, all the way up to State 31, when queried for the Reference value. Because this initial selection list is not directly derived from the targeted Multistate Value, it is possible for the user to select a value that actually falls outside the range of values defined for the Multistate Value object. Table 24-6 lists examples of potential problems and suggested solutions.

Table 24-6: Event Totalization Multistate Configurations Configuration Explanation Solution The Multistate Value object is configured as follows: • Number of States attribute = 4 • States Text attribute = States

(value ranges from State 0 to State 31)

The Event Totalization object is configured as follows: Reference attribute = State 4

State 0, State 1, State 2, and State 3 are the only legitimate values that the Multistate Value object can attain. Since the Multistate Value object cannot enter State 4, the Event Totalization object can record any events and its Present Value remains at 0. No error message displays and the Event Totalization object’s Executing attribute displays Active, despite an unobtainable value being entered.

The state specified for the Reference attribute of the Event Totalization object must be a state that can be legitimately achieved by the Multistate Value object.

The Multistate Value object is configured as follows: • Number of States attribute = 4 • States Text attribute = HVAC

Mode (Startup, Shutdown, Occupied, Unoccupied)

The Event Totalization object is configured as follows: Reference attribute = Any available options: State 0 through State 31

Legitimate selections for the Event Totalization object include: State 0 (Occupied) State 1 (Unoccupied) State 2 (Startup) State 3 (Shutdown) Since State 4 falls outside the range of legitimate Multistate Values, the Event Totalization object is inoperable. State 4 also falls outside the range of legitimate States Text values. Examination of the Event Totalization object via the VT100 results in the terminal beeping and the Reference attribute value displaying a “?”.

Edit the Event Totalization object using the steps described in the Editing an Event Totalization Object, highlight the Reference attribute field and press the Spacebar or Backspace key. This action forces a presentation of the attainable values, given the value of the Multistate Value object’s States Text attribute. The compatible value can then be chosen from the values presented.


Configuration (Cont.) Explanation Solution The Multistate Value object is configured as follows: • Number of States attribute = 3 • States Text attribute = HVAC

Mode (Startup, Occupied, Unoccupied are possible. Shutdown is not achievable by the Multistate Value object.)

The Event Totalization object is configured as follows: Reference attribute = State 3 (This correlates to Shutdown.)

Legitimate selections for the Event Totalization object include: State 0 (Occupied) State 1 (Unoccupied) State 2 (Startup) Since State 3 falls outside the range of legitimate Multistate Values, the Event Totalization object is inoperable. However, State 3 falls within the legitimate range of HVAC mode values, so the examination of the Event Totalization object via the VT100 does not result in the terminal beeping nor the Reference attribute value displaying a “?”.

The state specified for the Reference attribute of the Event Totalization object must be a state that can be legitimately achieved by the Multistate Value object.

IMPORTANT: It is recommended to set the Reference attribute of a new Event Totalization object being configured with a Multistate Value object to an initial selection of State 0. This guarantees that no matter which States Text set is employed by the Multistate Value object, the value falls within the legitimate range. After creating the Event Totalization object, go back and edit the Reference attribute to the required State. This allows the presentation of legitimate values given the Multistate Value object’s States Text attribute.


Chapter 25 Working with Runtime Totalization Objects

Introduction The Runtime Totalization object tracks the number of one minute time intervals that elapse while a designated input, such as a binary or multistate value, has matched a specified state. This chapter describes how to:

• add a Runtime Totalization object

• edit a Runtime Totalization object

• command a Runtime Totalization object

• delete a Runtime Totalization object



Key Concepts Runtime Totalization Object

A Runtime Totalization object accumulates total time only while a particular condition is satisfied (for instance, Supply Fan 1 is on). It answers the question “How long?” and is typically used to even out the use and wear of equipment, or to schedule maintenance after a certain amount of use. Data is recorded in minutes and converted to hours for the display. The Runtime Totalization object can be added to any container or object. The Runtime Totalization object references any binary or multistate attribute value for input data for its own calculations. Note: The Input Reference of a Runtime Totalization object should

refer to enumeration or Boolean based attributes in order to perform as intended. Runtime Totalization objects referencing other attribute data types (e.g., floating point) yield unusual results, though not necessarily unusable results. Neither the VT100 nor Project Builder give an error message when this object is attached to any attribute other than enumeration or Boolean based attributes.

Typical uses for a Runtime Totalization object are determining:

• fan or pump runtime

• the amount of time a point is in alarm

• runtime of fixed loads (such as lighting) for energy totalization and tenant billback

The Runtime Totalization formula and an example are illustrated in Table 25-1. Refer to the Attributes section of this chapter for information about attributes used in the calculation.

Table 25-1: Runtime Totalization Formula and Example Calculations Runtime Totalization

Calculation

Formula Present Value (current) + TA / (3600 x Scalefactor) = Present Value (new) Example 1.5 hours + 60 seconds/(3600 seconds/hour x 1) = 1.52 hours Note: TA represents the time the Input Reference spends in the Reference state.


Runtime Totalization Object Reset Describes under what conditions the reset of the Runtime Totalization object occurs and what conditions result due to the reset.

Table 25-2: Runtime Totalization Reset Reset Conditions Occurs: • When a Reset Command is received.





Attributes The values of an object’s attributes determine how the object operates. The Runtime Totalization object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 25-4. For additional information about the Runtime Totalization object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Runtime Totalization.




Input Reference Specifies the object and attribute totalized by this object. If this attribute is unreliable or changes from the Reference (state) to another state, totalization is temporarily suspended.

Reference Defines the state (0-31) totalized as defined in the Input Reference attribute. Writing this attribute forces the Reset condition.

Scalefactor Indicates the value used to scale the totalized value to either a larger or smaller value than would otherwise result. Writing this attribute forces the Reset condition.

Totalize Limit Defines a threshold value that the Present Value must meet or exceed in order for the Runtime Totalization object to take special action. The special action taken depends on the setting defined for the Rollover attribute.

Rollover Defines the special action the Runtime Totalization object must take when the Present Value reaches the Totalize Limit value. If the Rollover attribute is set to False, the Runtime Totalization object ceases further operation when the Present Value equals or exceeds the Totalize Limit value. If it is True, it will reset the present Value to 0.0 and resume a new cycle of totalization.

States Text Indicates the text that appears for the Present Value.




Present Value Represents the current totalized value of the object. Writing this attribute forces the Reset condition. Present Value appears to the right of the object name in the container hierarchy after the object is created.

Reset Forces a Reset condition, after a write of this attribute to True. The reading of this attribute always returns a False condition. It is not displayed on the attributes screen but it is useful for advanced diagnostics.



Procedure Overview Table 25-3: Working with Runtime Totalization Objects To Do This Follow These Steps: Add a Runtime Totalization Object

Browse to and highlight the container or object where the Runtime Totalization object is to be added. Press the F3 (Add) key. Select Runtime Totalization and press Enter. Fill in the fields using Table 25-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Runtime Totalization Object

Browse to and highlight a Runtime Totalization object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 25-4. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Runtime Totalization Object

Browse to and highlight a Runtime Totalization object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list of commands until the desired command appears. Press Enter.

Delete a Runtime Totalization Object

Browse to and highlight a Runtime Totalization object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Runtime Totalization Object

To add a Runtime Totalization object: 1. Browse to and highlight the container or object where the

Runtime Totalization object is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Select Runtime Totalization and press Enter. The Runtime

Totalization object attribute screen appears (Figure 25-1).

Figure 25-1: Runtime Totalization Object Attribute Screen 4. Fill in the fields using Table 25-4.





Description No Blank Maximum 40 characters Object Type Yes Runtime


Object Category



Input Reference

Yes If this Runtime Totalization object is being added to a container, the exact name of the object and attribute to be totalized must be entered. If this Runtime Totalization object is being added to another object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.

Engineering Values

Reference Yes State 1 Use the Spacebar and the Backspace key to cycle through the list of options: 0 to 31.

Scalefactor Yes 1.0 A float value greater than 0 Totalize Limit Yes (hours) A float value greater than 0 Rollover Yes False Use the Spacebar and Backspace key to view

and select options: True, False. Display States Text Yes States Use the Spacebar and Backspace key to view

and select options. Refer to States Text in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Units Yes hours Use the Spacebar and Backspace key to view and select options. Refer to Units Enumeration Set in Appendix A: Object Enumeration Sets of the Object Dictionary (LIT-694980).

Display Precision






Editing a Runtime Totalization Object To edit a Runtime Totalization object: 1. Browse to and highlight a Runtime Totalization object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Runtime Totalization object attribute screen appears (Figure 25-1).




Commanding a Runtime Totalization Object To command a Runtime Totalization object: 1. Browse to and highlight a Runtime Totalization object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

of commands until the desired command appears. The Runtime Totalization object supports the commands identified in Table 25-5.

Table 25-5: Supported Commands Command Description Reset Terminates ongoing calculations, restores the present value to

its initial state, creates a reset date and time stamp, and reinitializes all Changes of Value.

Enable Forces a Reset on the Runtime Totalization object and returns it to normal operation.

Disable Locks out all outputs and prevents functionality of the Runtime Totalization object. Temporarily suspends totalization.

4. Press Enter.


Deleting a Runtime Totalization Object To delete a Runtime Totalization object: 1. Browse to and highlight a Runtime Totalization. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 26 Working with Analog Alarm Objects

Introduction The Analog Alarm object adds the alarming capability for a floating-point attribute of any object, such as the Present Value of an Analog Input object. Note: The Input Reference of an Analog Alarm object should refer

to an analog attribute type in order to perform as intended. Analog Alarm objects referencing other attribute data types (e.g., Boolean) yield unusual results, though not necessarily unusable results. Neither the VT100 nor Project Builder give an error message when this object is attached to any attribute other than floating point based attributes.

This object detects an alarm based on up to four limits and can be configured to report that alarm. This object sets the Alarm State attribute of the object it is added to. This chapter describes how to:

• add an Analog Alarm object

• edit an Analog Alarm object

• command an Analog Alarm object

• delete an Analog Alarm object



Key Concepts Analog Alarm Object

When the Analog Alarm object’s Input attribute value exceeds the defined limits, it causes a change in the Analog Alarm object’s present value and the generation of a Status Notification Report (SNR). For example, with this object you can have a warning issued if the temperature in a room falls below 60°F and an alarm issued if the temperature falls below 50°F.

States The Analog Alarm object can be in any of the following states:

Normal State This occurs when the Analog Alarm object is in an acceptable, expected condition, as indicated by the Input attribute value.

Off Normal State This occurs when the Analog Alarm object transitions into the high and low warning conditions, as indicated by Input attribute value.

Fault State This occurs when the Analog Alarm object transitions into the high alarm, low alarm, and unreliable conditions, as indicated by the Input attribute value.

SNR Status Notification Report. A report that is generated by alarm objects and routed via the Message Routing feature to printers and VT100 Terminals.


Attributes The values of an object’s attributes determine how the object operates. The Analog Alarm object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 26-2. For additional information about the Analog Alarm object and its attributes, refer to the Object Dictionary.






Input Reference Indicates the object and attribute monitored for Changes-of-Value (COVs) and reported in alarm messages. The reliability of the Input Reference is monitored and saved in the Reliability attribute of this alarm object. The last value received from the Input Reference is written to the Input attribute.

High Alarm Limit Specifies the actual High Alarm Limit. If blank, the limit is not used.

Low Alarm Limit Specifies the actual Low Alarm Limit. If blank, the limit is not used.


Differential Indicates the amount the Input decreases or increases. If the Input is in High Alarm (or High Warning), it must decrease by the Differential before the object will return to High Warning (or Normal). If the Input is in Low Alarm (or Low Warning), it must increase by the Differential before the object will return to Low Warning (or Normal). This Differential is provided to prevent nuisance alarms due to a value that is cycling near an alarm (or warning) limit.

High Warning Offset Indicates the value that is added to the Analog Alarm Reference attribute to determine the actual High Warning Limit. If blank, the offset is not used. Either the High Warning Offset and Low Warning Offset must be defined or both must be blank.

Warning Reference The value that is added to the High and Low Warning Offsets to create the actual warning limits that the Input is compared against. The Reference is typically a setpoint. In order to disable warning analysis, this attribute must be blank.

Low Warning Offset Indicates the value that is subtracted from the Analog Alarm Reference variable to determine the actual Low Warning limit. If blank, the offset is not used. Either the High Warning Offset and Low Warning Offset must be defined or both must be blank.

Fault Ack Req (Acknowledgment Required) Indicates whether a transition into the Fault state creates a Message Requiring Acknowledgment (MRA).

Fault Priority Provides the priority assigned to the Fault state that gets transmitted to the SNR.

Fault Ack Pend (Acknowledgement Pending) Indicates whether a Message Requiring Acknowledgment (MRA) concerning a transition into the Fault state is waiting to be acknowledged.

Off Normal Ack Req (Acknowledgement Required) Indicates whether a Message Requiring Acknowledgment (MRA) concerning a transition into the Off Normal state must be acknowledged.


Event Enable Determines if the object sends reports (SNRs), if this value is True.

Dialout Required Forces a dial out to a destination device (if True), when this object goes into an alarm or warning state.

Delay Time Indicates the amount of time, following a change to the Analog Alarm reference value, that an Input must get within the warning or alarm limits before the object reports the warning. After this time, the input value is reevaluated. If it is still outside of the limit, a report is generated. If the Delay Time is changed, any current timer is canceled and reset to the new Delay Time.

Off Normal Priority Indicates the priority assigned to the Off Normal state that gets transmitted to the SNR.

Normal Ack Req (Acknowledgement Required) Indicates whether an MRA concerning a transition into the Normal state must be acknowledged.

Normal Priority Indicates the priority assigned to the Normal state that gets transmitted to the SNR.

Alarm Message Text Provides text associated with the SNR that a user can add for further information when an alarm or warning occurs.


Procedure Overview Table 26-1: Working with Analog Alarm Objects

To Do This Follow These Steps: Add an Analog Alarm Object Browse to and highlight the container or object where the Analog Alarm

object is to be added. Press the F3 (Add) key. Highlight Analog Alarm and press Enter. Fill in the fields using Table 26-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an Analog Alarm Object Browse to and highlight an Analog Alarm object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields using Table 26-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an Analog Alarm Object

Browse to and highlight an Analog Alarm object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete an Analog Alarm Object Browse to and highlight an Analog Alarm object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an Analog Alarm Object

To add an Analog Alarm object: 1. Browse to and highlight the container or object where the Analog

Alarm object is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Analog Alarm and press Enter. The first of two Analog

Alarm attribute screens appears (Figure 26-1). Note: Use the [ and ] keys to page to other screens.

Figure 26-1: Analog Alarm Attribute Screen (1 of 2)


Figure 26-2: Analog Alarm Attribute Screen (2 of 2) 4. Fill in the fields using Table 26-2.



Description No Blank Maximum 40 characters Object Type Yes Analog

Alarm The default is preset and cannot be changed.

Object Category



Engineering Values

Input Reference

Yes Blank If this Analog Alarm object is being added to a container, the exact name of the object and attribute to have an alarm must be entered. If this Analog Alarm object is being added to another object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.



Screen Area (Cont.)


Engineering Values (Cont.)

High Alarm Limit

No Blank A float value. Must be greater than the value of (Analog Alarm Reference + High Warning Offset).

Low Alarm Limit

No Blank A float value. Must be less than the value of (Analog Alarm Reference - Low Warning Offset).

Differential Yes 0.00 A float value greater than or equal to zero. High Warning

Offset No Blank A float value greater than or equal to zero.

If warnings are defined, define both High Warning Offset and Low Warning Offset or neither.

Warning Reference

A float value that is added to the High and Low Warning Offsets to create the actual warning limits that the Input is compared against. To disable warning analysis, this attribute must be blank.

Low Warning Offset

No Blank A float value greater than or equal to zero. If warnings are defined, define both High Warning Offset and Low Warning Offset or neither.

Alarm Setup Fault Ack Req Yes False Use the Spacebar and Backspace key to view and select options: False = Acknowledgement not required. True = Acknowledgement required.

Fault Priority Yes Serious Use the Spacebar and Backspace key to view and select options: Critical, Serious, Important, Status.

Off Normal Ack Req

Yes False Use the Spacebar and Backspace key to view and select options: False = Acknowledgement not required. True = Acknowledgement required.

Alarm State Event Enable Yes True Use the Spacebar and Backspace key to view and select options: True = Enables the object to report SNRs. False = Disables SNR reporting feature.

Dialout Required

Yes False Use the Spacebar and Backspace key to view and select options: False = Dialout not required. True = Dialout required.

Delay Time Yes 0 seconds Units = Seconds Off Normal

Priority Yes Important Use the Spacebar and Backspace key to

view and select options: Critical, Serious, Important, Status.



Screen Area (Cont.)


Alarm State (Cont.)

Normal Ack Req


Normal Priority

Yes Status Use the Spacebar and Backspace key to view and select options: Critical, Serious, Important, Status.

Notification Class

Identifies the instance number (Object Identifier [OID]) of the local Notification Class object to which notifications are sent.

Report Delay The number of seconds after the input value goes outside of an alarm or warning limit that the object waits before generating a warning or alarm. This applies only to changes from the normal state. After this time, the input value is reevaluated. If it is still outside the limit, a report is generated.

Alarm Setup Alarm Message Text

Yes Blank Up to 56 alphanumeric characters (1 line)




Editing an Analog Alarm Object To edit an Analog Alarm object: 1. Browse to and highlight an Analog Alarm object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Analog Alarm object attribute screen appears.





Commanding an Analog Alarm Object To command an Analog Alarm object: 1. Browse to and highlight an Analog Alarm object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Analog Alarm object supports the commands described in Table 26-3.

Table 26-3: Supported Commands Command Description Cancel Delay Time

Cancels delay timer if active. Canceling the delay time on an Analog Alarm object causes a warning if the value is in this state.

Cancel Report Delay Time

Cancels the report delay timer if active. Canceling the report delay time on an Analog Alarm object causes a warning or alarm if the value is in this state.

Enable Allows regular alarm analysis. Disable Prevents alarm analysis. Forces object to normal condition.

4. Press Enter.

Deleting an Analog Alarm Object To delete an Analog Alarm object: 1. Browse to and highlight an Analog Alarm object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 27 Working with Multistate Alarm Objects

Introduction The Multistate Alarm object provides the alarming capability for a Boolean or multistate attribute for any object, such as the Present Value of a Binary Input object. Note: The Input Reference of a Multistate Alarm object should

refer to enumeration or Boolean based attributes in order to perform as intended. Multistate Alarm objects referencing other attribute data types (e.g., floating point) yield unusual results, though not necessarily unusable results. Neither the VT100 nor Project Builder give an error message when this object is attached to any attribute other than enumeration or Boolean based attributes.

This object detects the alarm with respect to a difference from a defined normal state, and it can be configured to report the alarm. This chapter describes how to:

• add a Multistate Alarm object

• edit a Multistate Alarm object

• command a Multistate Alarm object

• delete a Multistate Alarm object



Key Concepts Multistate Alarm Object

When the Multistate Alarm object’s Input attribute value goes Off, it causes the generation of a Status Notification Report (SNR). For example, an alarm can be issued when a switch is in the Off position.

States The Multistate Alarm object can be in any of the following states:

Normal State This occurs when the Multistate Alarm object is in an acceptable, expected condition, as indicated by the Input attribute value.

Fault State This occurs when the Multistate Alarm object enters the alarm condition, as indicated by the Input attribute value.

SNR Status Notification Report. A report that is generated and routed via the Message Routing feature to printers and VT100 Terminals.

Attributes The values of an object’s attributes determine how the object operates. The Multistate Alarm object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 27-2. For additional information about the Multistate Alarm object and its attributes, refer to the Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Multistate Alarm.




Input Reference Indicates the object and attribute monitored for Changes-of-Value (COVs) and reported in alarm messages. The last value received from the Input Reference is written to the Input attribute. Also, the reliability of the Input Reference is monitored and saved in the Reliability attribute of this object.

Normal State Indicates the attribute value that is compared to the Input. If the Input value is different from the Normal State, an Alarm state occurs.

Fault Ack Req (Acknowledgement Required) Indicates whether a Message Requiring Acknowledgment (MRA) concerning a transition into the Fault state must be acknowledged.

Fault Priority Indicates the priority assigned to the Fault state that gets transmitted to the SNR.

Normal Ack Required (Acknowledgement Required) Indicates whether an MRA concerning a transition into the Normal state must be acknowledged.

Normal Priority Indicates the priority assigned to the Normal state that gets transmitted to the SNR.

Event Enable Determines if the object sends reports (SNRs), if this value is True.

Dialout Required Forces a dial out to a destination device (if True), when this object goes into an alarm or warning state.


Delay Time Indicates the amount of time Input has to get within the alarm limits before the object reports the alarm, following a Normal state change. The Present Value does not change what is reported until the Delay Time has expired. If the Delay Time is changed, any current timer is canceled and reset to the new Delay Time.

Alarm Message Text Provides text associated with the SNR that a user can add for further information when an alarm or warning occurs.


Procedure Overview Table 27-1: Working with Multistate Alarm Objects To Do This Follow These Steps: Add a Multistate Alarm Object Browse to and highlight the container or object where the Multistate Alarm

is to be added. Press the F3 (Add) key. Highlight Multistate Alarm and press Enter. Fill in the fields using Table 27-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Multistate Alarm Object Browse to and highlight a Multistate Alarm object. Press Enter to open the object. Press the F3 (Edit) key. Fill in the fields using Table 27-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Multistate Alarm Object

Browse to and highlight a Multistate Alarm object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Multistate Alarm Object

Browse to and highlight a Multistate Alarm object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Multistate Alarm Object

To add a Multistate Alarm object: 1. Browse to and highlight the container or object where the

Multistate Alarm is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Multistate Alarm and press Enter. The first of

two Multistate Alarm object attribute screens appears (Figure 27-1).

Figure 27-1: Multistate Alarm Object Attribute Screen (1 of 2)


Figure 27-2: Multistate Alarm Object Attribute Screen (2 of 2) 4. Fill in the fields using Table 27-2.



Description No Blank Maximum 40 characters Object Type Yes Multistate

Alarm The default is preset and cannot be changed.

Object Category





Screen Area (Cont.)


Engineering Values

Input Reference

Yes If this Multistate Alarm object is being added to a container, the exact name of the object and attribute to have an alarm must be entered. If this object is being added to another object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.

Normal State Yes State 0 Use the Spacebar and Backspace key to view and select options: State 0-State 31.

Alarm Setup Fault Ack Req Yes False Use the Spacebar and Backspace key to view and select options: False = Acknowledgement not required. True = Acknowledgement required.

Fault Priority Yes Serious Use the Spacebar and Backspace key to view and select options: Critical, Serious, Important, Status.

Normal Ack Req


Normal Priority

Yes Status Use the Spacebar and Backspace key to view and select options: Critical, Serious, Important, Status.

Notification Class

Identifies the instance number (Object Identifier [OID]) of the local Notification Class object to which notifications are sent.

Alarm State Event Enable Yes True Use the Spacebar and Backspace key to view and select options: True, False.

Dialout Required


Report Delay The number of seconds after the input value goes outside of an alarm or warning limit that the object waits before generating a warning or alarm. This applies only to changes from the normal state. After this time, the input value is reevaluated. If it is still outside the limit, a report is generated.

Delay Time No 0 second Units = seconds Alarm Setup Alarm

Message Text No Blank Type a message up to one line that appears

when an alarm occurs.


was successful. If errors are detected, correct them and resave the entries. Once the save is successful, continue with Step 7.



Editing a Multistate Alarm Object To edit a Multistate Alarm object: 1. Browse to and highlight a Multistate Alarm object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Multistate Alarm object attribute screen appears (Figure 27-1 and Figure 27-2).

4. Fill in the fields using Table 27-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Commanding a Multistate Alarm Object To command a Multistate Alarm object: 1. Browse to and highlight a Multistate Alarm object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Multistate Alarm object supports the commands described in Table 27-3.

Table 27-3: Supported Commands Command Description Cancel Delay Time Cancels the current Delay Timer. Enable Allows regular alarm analysis. Disable Prevents alarm analysis. Forces object to normal

condition.

4. Press Enter.


Deleting a Multistate Alarm Object To delete a Multistate Alarm object: 1. Browse to and highlight a Multistate Alarm object. 2. Press Enter to open the object. 3. Press the Delete. 4. Press the Tab key to confirm the deletion.


Chapter 28 Working with Trend Log Objects

Introduction The Trend Log object monitors and records changes in the behavior of an individual attribute over time, in order to help operators diagnose various site-wide behavioral characteristics. This chapter describes how to:

• add a Trend Log object

• edit a Trend Log object

• command a Trend Log object

• delete a Trend Log object



Key Concepts Trend Log Object

The Trend Log object can be added to any object to sample the value of any of the attributes of the following data types: Boolean, float, double float, enumeration, byte, unsigned integer, unsigned long, signed integer, signed long, or bit string. Typically, a Trend Log object collects data from an N2 Analog Input point object in a controller, which reports information such as outdoor air temperature or room air temperature. This data can be displayed or printed. Figure 28-1 shows a sample of Trend Log object data collected.

Trend Log Data From: ADMIN-Office, Present Value, Fault, OutOfService 27 Aug 1999 12:00:00 78.0 deg F 27 Aug 1999 14:32:00 79.1 deg F 28 Aug 1999 00:00:00 79.1 deg F 28 Aug 1999 12:00:00 79.1 deg F 29 Aug 1999 00:00:00 78.7 deg F 29 Aug 1999 12:00:00 79.3 deg F 30 Aug 1999 00:00:00 81.3 deg F

Figure 28-1: Sample Trend Log

Attributes The values of an object’s attributes determine how the object operates. The Trend Log object attributes described below are listed in the order that they appear on the screen. Entry requirements for these attributes are in Table 28-2. For additional information about the Trend Log object and its attributes, refer to Object Dictionary.



Object Type Indicates the kind of object, such as Schedule, N2 Analog Input, or Trend Log.




Stop When Full Determines whether the Trend Log object stops collecting data when it fills the buffer. True causes the Trend Log object to stop collecting data when the buffer is full. False causes it to continue collecting data every interval and to overwrite the oldest data sample with each new data sample.

Buffer Size Determines how many data samples can be collected before the Trend Log object must stop collecting data, or begin overwriting the oldest data samples.

Log Interval Determines how often the Trend Log object collects data from the Input Reference object. For example, a Log Interval of 600 seconds causes the Trend Log object to collect a data sample every 600 seconds (10 minutes). When Log Interval is set to zero, the Trend Log object operates as a Change-Of-Value (COV) mechanism, only recording data when the value of the Input Reference object changes by a difference equal to or greater than the COV Increment defined in the Input Reference object.

Input Reference Determines which object or attribute the Trend Log object collects data from. The Input Reference and the name of the object and attribute to be trended must match exactly.


Procedure Overview Table 28-1: Working with Trend Log Objects To Do This Follow These Steps: Add a Trend Log Object Browse to and highlight the container or object where the Trend Log

object is to be added. Press the F3 (Add) key. Highlight Trend Log and press Enter. Fill in the fields using Table 28-2 Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Trend Log Object Browse to and highlight a Trend Log object. Press Enter to open the object. Press the F3 (Edit) key. Fill in the fields using Table 28-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Trend Log Object Browse to and highlight a Trend Log object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list until the desired command appears. Press Enter.

Delete a Trend Log Object Browse to and highlight a Trend Log object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Trend Log Object

To add a Trend Log object: 1. Browse to and highlight the container or object where the Trend

Log object is to be added. 2. Press the F3 (Add) key. The Add Object list appears. 3. Highlight Trend Log and press Enter. The Trend Log object


Figure 28-2: Trend Log Object Attribute Screen 4. Fill in the fields using Table 28-2.




Object Object Name

No Blank Maximum 32 characters Invalid characters: @ . ? * $ # : ’ [ ] If not completed, the system assigns a name.

Description No Blank Maximum 40 characters Object Type Yes Trend Log The default is preset and cannot be changed. Object

Category Yes HVAC Use the Spacebar and Backspace key to view and

select options: HVAC, Fire, Security, Services, Administrative.


Setup Stop When Full


Buffer Size 144 1-5000 Log Interval 600 Minimum Value = 0

Maximum Value = 86400 Units = Seconds

Input Reference

Yes If this Trend Log object is being added to a container, the exact name of the object and attribute to be trended must be entered. If this Trend Log object is being added to another object, the name of that object appears automatically with its Present Value attribute. Example: HEATING SP.Present Value. Present Value is the default attribute that appears.

IMPORTANT: The desired Buffer Size, Log Interval, and Input Reference values must be entered now. They can be entered only when adding a new Trend Log object.





Editing a Trend Log Object To edit a Trend Log object: 1. Browse to and highlight a Trend Log object. 2. Press Enter to open the object. Note: Additional attributes appear. Refer to the Object Dictionary


3. Press the F3 (Edit) key. The Trend Log object attribute screen appears (Figure 28-2).

4. Fill in the fields using Table 28-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Commanding a Trend Log Object To command a Trend Log object: 1. Browse to and highlight a Trend Log object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

until the desired command appears. The Trend Log object supports the command described in Table 28-3.

Table 28-3: Supported Commands Command Description Display Displays the data that the Trend Log object collected from

the Input Reference object. See sample in Figure 28-1. Print Prints the data that the Trend Log object collected from the

Input Reference object. See sample in Figure 28-1. Enter the exact name of the Printer object.

Execute Instructs the Trend Log object to take a sample. Enable Instructs the Trend Log object to start collecting data from

the Input Reference object. Disable Instructs the Trend Log object to stop collecting data from

the Input Reference object.


4. If the desired command appears with additional parameters below it, press the Tab key to highlight the field and type in the necessary information.

5. Press Enter.

Deleting a Trend Log Object To delete a Trend Log object: 1. Browse to and highlight a Trend Log object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 29 Working with Notification Class Objects

Introduction The Notification Class object defines a standardized BACnet object with attributes that contain information required for the distribution of event notifications within BACnet systems. Notification Classes are useful for event-initiating objects that have identical needs in terms of how their notifications should be handled, what the destinations for their notifications should be, and how they should be acknowledged.

IMPORTANT: A Notification Class object needs to have a recipient list to define the destinations to which Notifications are sent. This cannot be done in a VT100, therefore, use Project Builder to add Notification Class objects.

The instructions in this chapter assume the database in which you are adding the Notification Class object has been properly uploaded to, or created in, Project Builder software. This chapter describes how to:

• add Notification Class object in Project Builder

• edit a Notification Class object in Project Builder

• edit a Notification Class object with a VT100

• command a Notification Class object with a VT100

• delete a Notification Class object with a VT100



For information on setting up a database using Project Builder, see the N30 Supervisory Controller Quick Start Technical Bulletin. For information on using Project Builder software, including working with objects and the M-View screen, see the Project Builder User’s Guide. Note: The Notification Class object is a BACnet object and is

sometimes referred to as BACnet Notification Class object. For reference information on this object in the Object Dictionary, see the BACnet Notification Class (LIT-694250) chapter.


Key Concepts Notification Class

A notification class defines how event notifications are prioritized according to To-Offnormal, To-Fault, and To-Normal events; whether these categories of events require acknowledgement (nearly always, by a human operator); and what destination devices or processes receive notifications.

Destinations It is often necessary to send event notifications to multiple destinations or to different destinations based on the time of day or day of week. Notification Classes may specify a list of destinations, each of which is qualified by time, day of week, and type of handling. See Table 29-1 for a list of destination parameters. If an event that uses a Notification Class object occurs and the day is one of the days of the week that is valid for a given destination, and the time is within the window specified in the destination, then a notification is sent to the destination. Further qualify destinations, as applicable, by any combination of the three event transitions (To-Offnormal, To-Fault, and To-Normal). The destination also defines the recipient device to receive the notification and a process within the device. Numeric handles identify processes that are only meaningful to the destination device. The administration of these handles is a local matter. The recipient device may be specified by either its unique Device Object Identifier or its BACnet Address. In the latter case, a specific node address, a multicast address, or a broadcast address may be used. The destination further specifies whether the notification is sent using a confirmed or unconfirmed event notification. The Recipient List attribute describes how the parameters listed in Table 29-1 relate to the Notification Class object.


Table 29-1: BACnet Destination Parameters Parameter Type Description From Time, To Time Time The window of time (inclusive) during which the

destination is viable on the valid days of the week. Issue Confirmed Notifications

Boolean True if confirmed notifications are sent and False if unconfirmed notifications are sent.

Process Identifier Unsigned The handle of a process within the recipient device that receives the event notification.

Recipient BACnet Recipient The destination devices to receive notifications. Transitions BACnet Event Transition

Bits A set of three flags that indicate those transitions (To-Offnormal, To-Fault, To-Normal) for which this recipient is suitable.

Valid Days BACnet Days of Week The set of days of the week on which this destination may be used during the value of From Time, To Time.

Attributes

Ack Required Conveys three separate flags that represent whether acknowledgement is required in notifications generated for To-Offnormal, To-Fault, and To-Normal event transitions, respectively.

Description This is a string of printable characters.

Notification Class Indicates the numeric value of this notification class and equals the instance number of the Notification Class object. Event-initiating objects use this number to refer to this Notification Class object indirectly.

Object Identifier A unique numeric code used to identify the object.

Object Name A character string that represents the name of the object.

Object Type A value that indicates membership in a particular object type class.

Priority Convey the priority to be used for event notifications for To-Offnormal, To-Fault, and To-Normal events, respectively. A lower number indicates a higher priority.


Recipient List Conveys a list of one or more recipient destinations to which notifications are sent when event-initiating objects using this class detect the occurrence of an event. The destinations themselves define a structure of parameters that is summarized in Table 29-1.


Procedure Overview Table 29-2: Notification Class Object To Do This Follow These Steps: Add a Notification Class Object in Project Builder

In Project Builder, open the database to which you want to add the Notification Class object. Expand the database so that the container or object you want to add the Notification Class object to is visible. In the object library on the left side of the screen, open the N30 folder. Select the Notification object and drag it to the container or object to which you want to add the Notification Class object. Browse to the object you just created. Double-click the row header of the Notification Class object to open the M-View screen. Enter an object name and description. Click the List Elements button. Click the Add button. Click the Structure Elements button. Fill in the fields according to Table 29-3. Click Done to return to the Complex View – Recipient list. Continue adding until all recipients are entered. Click Done to return to the M-View screen for the Notification Class object. Click the Array Elements button to edit the priority list. Click the Ack Required button to edit whether destinations must globally acknowledge transitions. Click OK when finished. The object cannot be used until the new, modified database is downloaded to your N30.

Edit a Notification Class Object in Project Builder

In Project Builder, open the database with the Notification Class object you want to edit. Browse to and select the object you want to edit. Double-click the row header of the object to open the M-View screen. Edit the object name and description if necessary. Click the List Elements button. Click the Structure Elements button. Fill in the fields according to Table 29-3. Click Done to return to the Complex View – Recipient list. Edit each recipient in the list as necessary. Click Done to return to the M-View screen. Click the Array Elements button to edit the priority list. Click the Ack Required button to edit whether destinations must globally acknowledge transitions. Click OK when finished. The edited object cannot be used until the new, modified database is downloaded to your N30.

Edit a Notification Class Object with a VT100

Browse to and select the Notification Class object that you want to edit. Press the Return key to open. Press the F3 (Edit) key. Edit the fields as required. Note: The recipient list cannot be edited using a VT100. Press the F3 (Save) key. Press any key to continue. Press the F4 (Cancel) key to return to the main screen.

Command a Notification Class Object with a VT100

Browse to and select the Notification Class object you want to command. Press the F2 (Command) key. Use the Spacebar and Backspace keys to select Enable or Disable. Press the Return key to execute the selected command.

Delete a Notification Class Object with a VT100

Browse to and select the Notification Class object you want to delete. Press the Return key to open. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Notification Class Object in Project Builder

To add a Notification Class object: 1. In Project Builder, open the database to which you want to add the

Notification Class object. 2. Expand the database so that the container or object you want to

add the Notification Class object to is visible. 3. In the object library on the left side of the screen, open the N30

folder. 4. Select the Notification object and drag it over to the container or

object to which you want to add the Notification Class object. 5. Browse to the object you just created. 6. Double-click the row header of the Notification Class object to

open the M-View screen for the Notification Class object (Figure 29-1).

Figure 29-1: Notification Class Object in M-View 7. Enter an object name and description.


8. Click the List Elements button. The Complex View – Recipient List screen appears (Figure 29-2).

Figure 29-2: Complex View - Recipient List 9. Click the Add button. 10. Click the Structure Elements button. A new Recipient form opens

(Figure 29-3).


Figure 29-3: New Recipient Form 11. Fill in the fields according to Table 29-3.

Table 29-3: Recipient List Fields Field Used for Valid Days The set of days of the week on which this destination may be used. From Time The window of time (inclusive) during which the destination may be used.

To specify all times, use 00:00:00 for From Time and 23:59:59 for To Time. To Time The window of time (inclusive) during which the destination may be used.

To specify all times, use 00:00:00 for From Time and 23:59:59 for To Time. Recipient Choice The choice of whether to use an Object Identifier (value of 0) or the Network

Address (value of 1) of the destination to route the notifications. Object ID The BACnet Object Identifier of the device object to which Event Notification

messages are sent. Address Net Number The network number for the destination if routing via address. Address IP The Internet Protocol (IP) Address of the destination if routing via address. Address UDP Port Number The User Datagram Protocol (UDP) port number for the destination if routing

via address. Process Identifier The process ID within the recipient device that is to receive the Event

Notification messages. Confirmed Notif If TRUE, Confirmed Event Notifications are sent, if FALSE Unconfirmed

Event Notifications are sent. Transitions Three flags that indicate which types of transitions (To-Offnormal, To-Fault,

or To-Normal) should be sent to the destination.


12. Click Done to return to the Complex View – Recipient list. 13. Repeat Steps 9 through 12 until all recipients are entered. 14. Click Done to return to the M-View screen for the Notification

Class object. 15. Click the Array Elements button to edit the priority list. 16. Click the Ack Required button to edit whether destinations must

globally acknowledge transitions. 17. Click OK when finished. You are returned to the main Project

Builder screen.

IMPORTANT: The object cannot be used until the new, modified database is downloaded to your N30.

Editing a Notification Class Object in Project Builder To edit a Notification Class object in Project Builder: 1. In Project Builder, open the database with the Notification Class

object you want to edit. 2. Browse to and select the object you want to edit. 3. Double-click the row header of the Notification Class object to

open the M-View screen for the Notification Class object (Figure 29-1).

4. Edit the object name and description if necessary. 5. Click the List Elements button. The Complex View – Recipient

List screen appears containing previously entered recipients (Figure 29-4).


Figure 29-4: Complex View - Recipient List with Recipients 6. Click the Structure Elements button for the Recipient you want to

edit. 7. Fill in the fields according to Table 29-3. 8. Click Done to return to the Complex View – Recipient list. 9. Repeat Steps 6 through 8 until all recipients that need to be edited

are complete. 10. Click Done to return to the M-View screen for the Notification

Class object. 11. Click the Array Elements button to edit the priority list. 12. Click the Ack Required button to edit whether destinations must

globally acknowledge transitions. 13. Click OK when finished. You are returned to the main Project

Builder screen.

IMPORTANT: The changes to the object cannot be used until the new, modified database is downloaded to your N30.


Editing a Notification Class Object Using a VT100 To edit a Notification Class object using a VT100: 1. Browse to and select the Notification Class object that you want

to edit. 2. Press the Return key to open. The Notification Class object

attributes screen appears (Figure 29-5).

Figure 29-5: Notification Class Object Attributes 3. Press the F3 (Edit) key. 4. Edit the fields as required. Note: The recipient list cannot be edited using a VT100.

5. Press the F3 (Save) key. 6. Press any key to continue. 7. Press the F4 (Cancel) key to return to the main screen.


Commanding a Notification Class Object Using a VT100 To command a Notification Class object using a VT100: 1. Browse to and select the Notification Class object you want to

command. 2. Press the F2 (Command) key. The command field appears. 3. Use the Spacebar and Backspace keys to select Enable or Disable. 4. Press the Return key to execute the selected command.

Deleting a Notification Class Object Using a VT100 To delete a Notification Class object using a VT100: 1. Browse to and select the Notification Class object you want to

delete. 2. Press the Return key to open. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 30 Working with Remote Destination Objects

Introduction The Remote Destination object ensures delivery of Status Notification Reports (SNRs) to a workstation via a modem. It also makes and maintains a connection with the workstation, allowing the workstation to make a connection permanent or to deny a connection. This chapter describes how to:

• add a Remote Destination object

• edit a Remote Destination object

• delete a Remote Destination object Note: Remote Destination objects are not commandable.



Key Concepts Remote Destination Object Operation

SNRs (received from Alarm objects) initiate a connection if either the Dialout Required flag is set, or the Max SNR Queue reaches the percentage set in the SNR Dial Out Level attribute. The Remote Destination object is connected to the Serial Datalink object by setting the Port Number attribute. The Remote Destination object performs the following tasks:

• receives status notification report messages from the Message Router object.

• sends Dial commands to the Serial Datalink object when status notification report messages need to be sent.

• notifies the Serial Datalink object to disconnect when the Dial Connect Timeout expires.

Attributes

Dial Connect Timeout Indicates the amount of time the Remote Destination object waits to receive messages before disconnecting, following the N30-initiated Dial command.

Timeout Indicates the amount of time remaining prior to disconnection, following the N30-initiated Dial command.

Error State Indicates the reason for error: None - No error. Dial Out Failed - The Serial Datalink object failed to connect in the time set by the Retries and Retry Interval attributes. The Serial Datalink object’s Connected To attribute does not change to Metasys device. If the Error State attribute is set to this state, the Remote Destination object’s offline status is True. Disconnected - The Remote Destination object currently does not need to be connected.


Max SNR Queue Specifies the number of alarm messages that are buffered for this Remote Destination. If the queue is full, alarm messages sent to this Remote Destination to be printed may be lost.

Modem Config Object Specifies the Modem Configuration object, which holds the modem information used by the Serial Datalink object. This attribute must be set to a Modem Configuration Class object.

Phone Number Indicates the Dial-out phone number if a modem is connected to the port.

Port Number Indicates the port number specifying the port to which data is sent.

Queue Used Current Indicates the number of active entries in the report list.

Retries Specifies how many times the Remote Destination object resends the Dial command. If the dial-up connection could not be made in the time defined as the Retry Interval, the Remote Destination object sends the Dial command again.

Retry Interval Indicates the amount of time in which Retries occur. If the Error State attribute is set to Disconnected, the Remote Destination object retries sending the Dial command periodically in this interval.

SNR Dial Out Level The percentage of the queue that needs to be full before dial-out occurs.

Login ID Identifies which user is connected during a dial-up session with an M-Series Workstation.

Password Identifies which password is connected during a dial-up session with an M-Series Workstation.


Process Identifier Used to route notifications (alarms) to this destination. Must be a unique number for each device. If not specified, a value is automatically assigned on download.

Ack Required Setting this value to True allows the BACnet Acknowledgement Notification messages to be passed to the M3 workstation.

Status The Metasys Common Object (LIT-694020) chapter of the Object Dictionary details this attribute. A list of relevant states follows (listed in hierarchical order from highest to lowest): Normal: Expected operating condition.

Active Filter Selects the type of filtering in effect for this remote destination. The filter types are as follows:

• Pass None - When selected this destination receives no alarm messages.

• Pass All - When selected this destination receives all alarm messages.




Priority Filter A Defines which priorities this destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, Status.

Category Filter A Defines which categories of messages the destination receives when Filter A is in effect. This filter has no effect for alarm messages without a defined category. A value of True for a particular selection means messages of that defined category reach this destination.


Msg Type Filter A Defines which types of messages the destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, Alarm.

Priority Filter B Defines which priorities the destination receives when Filter B is in effect. A value of True for a particular selection means that messages of that defined priority reach this destination. Choices from highest to lowest priority are Critical, Serious, Important, Status.

Category Filter B Defines which categories of messages the destination receives when Filter B is in effect. This filter has no effect for alarm messages without a defined category. A value of True for a particular selection means that messages of that defined category reach this destination.

Msg Type Filter B Defines which types of messages the destination receives when Filter A is in effect. A value of True for a particular selection means messages of that defined type reach this destination. Choices from highest to lowest priority are System Alert, Operator Transaction, Alarm.


Procedure Overview Table 30-1: Remote Destination Object Procedure Overview To Do This Follow These Steps: Add a Remote Destination Object

Browse to and highlight the Operator Devices container. Press the F3 (Add) key. Highlight Remote Destination and press Enter. Fill in the fields using Table 30-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Remote Destination Object

Browse to and highlight a Remote Destination object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields according to Table 30-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Delete a Remote Destination Object

Browse to and highlight a Remote Destination object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.

Note: The Remote Destination object has no commands.


Detailed Procedures Adding a Remote Destination Object

To add a Remote Destination object: 1. Browse to and highlight the Operator Devices container. 2. Press the F3 (Add) key. 3. Highlight the Remote Destination object from the list that appears

and press Enter. The first of two Remote Destination object configuration screens appears (Figure 30-1). The second screen is shown in Figure 30-2.

Figure 30-1: Remote Destination Object Configuration Screen 1


Figure 30-2: Remote Destination Object Configuration Screen 2 4. Fill in the fields using Table 30-2.

Table 30-2: Remote Destination Object Attributes Screen Area Attribute Required Default Options/Range Object Object



Description No Blank Maximum 40 characters Object Type Yes Remote

Destination The default is preset and cannot be changed.

Object Category

Yes HVAC HVAC, Fire, Security, Services, Administrative.



Screen Area (Cont.)


Engineering Values

Port Number Yes Port 2 Port 0, Port 1, Port 2, Port 3. Port 0 is not a valid option for this object.

Dial Connect Timeout

Yes 60 Value greater than 0, duration of connection in seconds when call is initiated by the N30

Retry Interval

Yes 180 60-600 seconds, time between dial attempts when previous dial attempts fail

Retries Yes 3 0-10, number of attempts before failure Password Yes Blank M-Series Workstation connection password,

13 character maximum SNR Dial

Out Level Yes 80 % 35-100 percent

Login Id Yes Blank M-Series Workstation Login ID, 20 character maximum

Phone Number

Yes Blank M-Series Workstation modem number to dial

Active Filter Yes Pass All Pass None, Pass All, Filter A, Filter B, Filter A and B.

Priority Filter A

Yes [4] Items Critical, Serious, Important, Status.

Category Filter A

Yes [5] Items HVAC, Fire, Security, Services, Administrative.

Msg Type Filter A

Yes [3] Items System Alert, Operator Transaction, Alarm.

Priority Filter B

Yes [4] Items Critical, Serious, Important, Status.

Category Filter B

Yes [5] Items HVAC, Fire, Security, Services, Administrative.

Msg Type Filter B

Yes [3] Items System Alert, Operator Transaction, Alarm.

Modem Config Object

No Blank Enter the exact name of the Modem Configuration object containing the required dial-out information.

Remote Device Name

No Blank M-Series Workstation Device name

Process Identifier

Yes Blank This value is automatically assigned during download, but must be assigned a value between 3 and 15 for the given device when it is being added from the VT100.

Max SNR Queue

Yes 25 3-100

Ack Required

Yes True True/False, Passes BACnet Event Notify messages to M3 Workstation

5. Press F3 to save the new object. 6. Check the User Assistance area of the screen to verify if the save

was sucessful or if there were errors. If errors were detected, correct them and resave the entries. Once the save is successful, continue with Step 7.



Editing a Remote Destination Object To edit a Remote Destination object: 1. Browse to and highlight a Remote Destination object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Remote Destination object attribute

screen appears. See Figure 30-1 and Figure 30-2. 4. Edit the fields according to Table 30-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Deleting a Remote Destination Object To delete a Remote Destination object: 1. Browse to and highlight a Remote Destination object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.



Chapter 31 Working with E-mail ObjectsT

Introduction The E-mail object provides alarm notification through electronic mail (e-mail) to personnel at a remote location. The E-mail object translates alarm messages into the correct e-mail format and sends the message via the local mail gateway (Simple Mail Transfer Protocol [SMTP] server). Note: In order to function, the E-mail object must have access via

Ethernet to an SMTP server on the Local Area Network (LAN). In addition, the N30 Device object must identify the location of the SMTP server.

For standard alarming, the E-mail object routes alarms based on filtering criteria defined in the E-mail object attributes. However, for BACnet alarming, set the E-mail object as a destination of the BACnet Notification Class in order to route alarms. This chapter describes how to:

• add an E-mail object

• edit an E-mail object

• command an E-mail object

• delete an E-mail object


Key Concepts E-mail Object Operation

The Message Router object sends a Status Notification Report (SNR) containing status change information to the E-mail object. The E-mail object converts the text of the SNR into the proper format for the body of an e-mail message. The E-mail object sends the e-mail message to an SMTP server, which routes the message to the intended recipient (see Figure 31-1). Note: The E-mail object can only guarantee delivery of the

message to the SMTP server. The SMTP server is responsible for delivering the message to the intended recipient. If the SMTP server cannot deliver a message, the SMTP server sends a delivery failure notice to the e-mail address identified in the Reverse Path attribute.

If the E-mail object cannot send a message due to errors/failures in communicating with the server, the E-mail object buffers the message and tries again at a later time according to the values of the Number of Retries and the Retry Interval attributes.

TO:FROM:SUBJECT:0001_SITE: SER HA 0001-AV-1 150.0 Deg F 14 Jan 2000 13:19:02

[email protected]@jci.com

emailmsg

Site Name: 0001_SITE

Alarm Priority: SEREvent State: HAPrevious Event State: NORObject Name: 0001-AV-1Object Value: 150.0 Deg FObject Category: HVACReliability: ReliableAlarm Text: Chiller at northwest corner of building

Date: 14 Jan 2000Time: 13:19:02Message Type: Alarm

Acknowledge Required: TRUE

Figure 31-1: Sample E-mail Message


E-mail Delivery Failure The E-mail object can only guarantee delivery of the message to the SMTP server. The SMTP server is responsible for delivering the message to the intended recipient. If the SMTP server cannot deliver a message, the SMTP server sends a delivery failure notice to the e-mail address identified in the Reverse Path attribute. The following are sample situations in which an SMTP server cannot deliver a message and, as a result, sends a delivery failure notice to the Reverse Path e-mail address. Attribute Values: Recipient 1 = [email protected] Recipient 2 = [email protected] Reverse Path = [email protected] Situation 1 The mail system for Acme Inc. is currently full or not receiving messages. The E-mail object sends a delivery failure message to [email protected] indicating that the SNR message was not delivered because the Acme Inc. mail system failed to receive it. Situation 2 A recipient e-mail address does not exist because John Smith is no longer an employee of Acme Inc. The E-mail object sends a delivery failure message to [email protected] indicating that the SNR message was not delivered because the recipient e-mail address does not exist.

SMTP Server Location In order to use the E-mail object, the N30 Device object must identify the location of the SMTP server. If the site uses a Domain Name System (DNS) server, use the SMTP Server Name attribute in the N30 Device object to identify the SMTP server location. If the site does not use a DNS server, use the SMTP Server IP Address attribute in the N30 device object instead. See the N30 Device (LIT-694610) chapter in the Object Dictionary for details on using these attributes.


Attributes

Recipient 1/2/3 Name Specifies the e-mail addresses of the intended recipients. Specifies up to three recipients.

Reverse Path Name Specifies the e-mail address of the person who receives delivery failure messages for failures that occur after the e-mail has been sent to the SMTP server. If the SMTP server cannot deliver a message, the SMTP server sends a delivery failure notice to the e-mail address identified in this attribute. (The E-mail object cannot receive email messages and thus cannot receive delivery failure messages.)

Retry Interval If delivery fails while the E-mail object is sending the e-mail to the SMTP server, the E-mail object retries sending the e-mail message periodically in this interval.

Retries If delivery fails while the E-mail object is sending the e-mail to the SMTP server, the E-mail object attempts to send the message in the time defined in the Retry Interval attribute. The Number of Retries attribute specifies how many times the E-mail object resends the message.

Max SNR Queue Specifies the number of SNR messages that the SNR queue can hold.

Process Identifier Used to route messages to the E-mail object. Must be a unique number for each device. If not specified, a value is automatically assigned on download.


Active Filter Selects the type of filtering in effect for the E-mail object. The filter types are as follows:

• Pass None - No SNR messages sent.

• Pass All - Send all SNR messages.

• Filter A - Send SNR messages based on the settings of Filter A.

• Filter B - Send SNR messages based on the settings of Filter B.

• Filter A and B - Send SNR messages based on the settings of Filter A and Filter B.

Priority Filter A This element of Filter A defines which priorities the E-mail object sends when Filter A is in effect. A value of True for a particular position (Critical, Serious, Important, or Status) means that the E-mail object sends messages of that defined priority.

Category Filter A This element of Filter A defines which categories of messages the E-mail object sends when Filter A is in effect. This filter has no effect for SNRs that do not define a category. A value of True for a particular position (HVAC, Fire, Security, Services, or Administrative) means that the E-mail object sends messages of that defined category.

Msg Type Filter A This element of Filter A defines which message types the E-mail object sends when Filter A is in effect. A value of True for a particular position (System Alert, Operator Transaction, or Alarm) means that the E-mail object sends a message of that defined type.

Priority Filter B This element of Filter B defines which priorities the E-mail object sends when Filter B is in effect. A value of True for a particular position (Critical, Serious, Important, or Status) means that the E-mail object sends messages of that defined priority.

Category Filter B This element of Filter B defines which categories of messages the E-mail object sends when Filter B is in effect. This filter has no effect for SNRs that do not define a category. A value of True for a particular position (HVAC, Fire, Security, Services, or Administrative) means that the E-mail object sends messages of that defined category.


Msg Type Filter B This element of Filter B defines which message types the E-mail object sends when Filter B is in effect. A value of True for a particular position (System Alert, Operator Transaction, or Alarm) means that the E-mail object sends a message of that defined type.

Error State Indicates the reason for the error. Possible values are:

• None

• Queue Full

• Server Error

Example Figure 31-4 and Figure 31-5 show screens from a sample completed E-mail object.

Figure 31-2: Completed E-mail Object - Screen 1


Figure 31-3: Completed E-mail Object - Screen 2


Procedure Overview Table 31-1: E-mail Object Procedure Overview To Do This Follow These Steps: Add an E-mail Object Browse to and highlight the Operator Devices container. Press the

F3 (Add) key. Highlight E-mail and press Enter. Fill in the fields using Table 31-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit an E-mail Object Browse to and highlight an E-mail object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields according to Table 31-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command an E-mail Object Browse to and highlight an E-mail object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list of commands until the desired command appears. Press Enter.

Delete an E-mail Object Browse to and highlight an E-mail object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding an E-mail Object

To add an E-mail object: 1. Browse to and highlight the Operator Devices container. 2. Press the F3 (Add) key. 3. Highlight the E-mail object from the list that appears and press

Enter. The first of two E-mail object configuration screens appears (Figure 31-4). The second screen is shown in Figure 31-5.

Figure 31-4: E-mail Object Configuration Screen 1


Figure 31-5: E-mail Object Configuration Screen 2 4. Fill in the fields using Table 31-2.

Table 31-2: E-mail Object Attributes Screen Area Attribute Required Default Options/Range Object Object



Description No Blank Maximum 40 characters Object Type Yes Email The default is preset and cannot be changed. Object

Category Yes HVAC HVAC, Fire, Security, Services, Administrative.



Screen Area (Cont.)


Setup Recipient 1 Name

Yes Blank Maximum of 50 characters

Recipient 2 Name

No Blank Maximum of 50 characters

Recipient 3 Name

No Blank Maximum of 50 characters

Reverse Path Name

Yes Blank Maximum of 50 characters

Retry Interval


Retries Yes 3 0-10 Max SNR

Queue Yes 25 3-100

Process Identifier

Yes Blank This value is automatically assigned during download but must be assigned a value between 3 and 15 for the given device when it is being added from the VT100.

Active Filter Yes Pass All Pass None, Pass All, Filter A, Filter B, Filter A and B

Priority Filter A

Yes [4] Items Critical, Serious, Important, Status

Category Filter A

Yes [5] Items HVAC, Fire, Security, Services, Administrative

Msg Type Filter A

Yes [3] Items System Alert, Operator Transaction, Alarm

Priority Filter B


Category Filter B


Msg Type Filter B


5. Press F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save

was successful or if there were errors. If errors were detected, correct them, and resave the entries. Once the save is successful, continue with Step 7.



Editing an E-mail Object To edit an E-mail object: 1. Browse to and highlight an E-mail object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The E-mail object attribute screen

appears. See Figure 31-4 and Figure 31-5. 4. Edit the fields according to Table 31-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save

was successful or if there were errors. If errors were detected, correct them, and resave the entries. Once the save is successful, continue with Step 7.


Commanding an E-mail Object To command an E-mail object: 1. Browse to and highlight an E-mail object. 2. Press the F2 (Command) key. The Command field appears. 3. Use the Spacebar and the Backspace key to cycle through the list

of commands until the desired command appears. The E-mail object supports the commands identified in Table 31-3.

Table 31-3: Supported Commands Command Description Disable Causes E-mail object to ignore incoming SNR messages. Enable Causes E-mail object to process incoming SNR messages. Queue Clear Clears all SNR messages in the SNR queue.

4. Press Enter.

Deleting an E-mail Object To delete an E-mail object: 1. Browse to and highlight an E-mail object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Chapter 32 Working with Pager Objects

Introduction The Pager object provides alarm notifications via pager to personnel at a remote location who would otherwise not be aware of the alarm coming into a workstation or terminal. The Pager object integrates the alarm message into the correct protocol message format and sends the dialup message via outgoing modem. This object is designed for a supervisory controller such as the N30. Notes: The Pager object supports only a basic notification function

that communicates to alphanumeric pager services that support the Telocator Alphanumeric Protocol (TAP). The pager service port must be set to accept N30 pager notifications: Data bits = 8, Parity = None, and Stop bits = 1 The Pager object does not support Acknowledgement, Systems Management Server (SMS) and Wireless Application Protocol (WAP) solutions, or other similar advanced functions.

For standard alarming, the Pager object routes alarms based on filtering criteria defined in the Pager object attributes. However, for BACnet alarming, set the Pager object as a destination of the BACnet Notification Class object in order to route alarms. This chapter describes how to:

• add a Pager object

• edit a Pager object

• command a Pager object

• delete a Pager object

© March 15, 2006 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-1201113 Software Release 5.0


Key Concepts Pager Object Operation

The Message Router object sends a Status Notification Report (SNR) containing status change information to the Pager object. The Pager Object decodes the message and formats it into Pager message format. The Pager object dials the pager service using the proper protocol. Notes:

Note:

Pager devices are connected via modem through a Dialout N30 port. More than one Pager object can be related to a Dialout port by setting the Port Number attribute. However, only one Pager object at a time can use the port.

The Pager object can share a Dialout port only with other Pager objects (not with other devices). If another Pager object is already using the Dialout N30 port, the Pager object stores the message in a queue and attempts to dial again at one minute intervals. Once the pager service receives the message, the pager service routes the SNR message to the pager (see Figure 32-1).

If a port is busy when the Pager object tries to dial the pager service, the Pager object buffers the message and attempts to dial out again at a later time.

SER B7F3 SUPPLY FAN Fault 04 Jun 2001 11:05:47 CALL MAINTENANCE SERVICE @ 555-4703

SNR Message Alarm Message

Pager Message

pagermsg

Figure 32-1: Sample Pager Message


Attributes

Port Number Specifies the port to which the Pager object sends data.

Retries Number of times that the Pager object resends any transmissions to the pager service if an error occurs.

Process Identifier Used to route messages to the Pager object. Must be a unique number for each device. If not specified, a value is automatically assigned on download.

Pager Number Dial-out phone number of the pager to receive the Alphanumeric message. Both the Pager Number and Pager Service are required for the Pager object to function.

Pager Service Dial-out phone number of the pager service providing Alphanumeric messaging service. Both the Pager Number and Pager Service are required for the Pager object to function.

Modem Config Object Holds the modem information used by the Serial Datalink Object. Set this attribute to a Modem Configuration object. When the Modem Configuration Object attribute is set to None, the Pager object uses the default modem initialization string and parameters from the Serial Datalink object. See the Modem Configuration (LIT-694490) and Serial Datalink (LIT-694810) chapters in the Object Dictionary.

Active Filter Selects the type of filtering in effect for the Pager object. The filter types are as follows:

• Pass None - No SNR messages sent.

• Pass All - Send all SNR messages.

• Filter A - Send SNR messages based on the settings of Filter A.

• Filter B - Send SNR messages based on the settings of Filter B.

• Filter A and B - Send SNR messages based on the settings of Filter A and Filter B.


Priority Filter A This element of Filter A defines which priorities the Pager object sends when Filter A is in effect. A value of True for a particular position (Critical, Serious, Important, or Status) means that the Pager object sends messages of that defined priority.

Category Filter A This element of Filter A defines which categories of messages the Pager object sends when Filter A is in effect. This filter has no effect for SNRs that do not define a category. A value of True for a particular position (HVAC, Fire, Security, Services, or Administrative) means that the Pager object sends messages of that defined category.

Msg Type Filter A This element of Filter A defines which message types the Pager object sends when Filter A is in effect. A value of True for a particular position (System Alert, Operator Transaction, or Alarm) means that the Pager object sends a message of that defined type.

Priority Filter B This element of Filter B defines which priorities the Pager object sends when Filter B is in effect. A value of True for a particular position (Critical, Serious, Important, or Status) means that the Pager object sends messages of that defined priority.

Category Filter B This element of Filter B defines which categories of messages the Pager object sends when Filter B is in effect. This filter has no effect for SNRs that do not define a category. A value of True for a particular position (HVAC, Fire, Security, Services, or Administrative) means that the Pager object sends messages of that defined category.

Msg Type Filter B This element of Filter B defines which message types the Pager object sends when Filter B is in effect. A value of True for a particular position (System Alert, Operator Transaction, or Alarm) means that the Pager object sends a message of that defined type.


Procedure Overview Table 32-1: Pager Object Procedure Overview To Do This Follow These Steps: Add a Pager Object Browse to and highlight the Operator Devices container. Press the

F3 (Add) key. Highlight Pager, and press Enter. Fill in the fields using Table 32-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Edit a Pager Object Browse to and highlight a Pager object. Press Enter to open the object. Press the F3 (Edit) key. Edit the fields according to Table 32-2. Press the F3 (Save) key. Check the User Assistance area of the screen to verify if the save was successful or if there were errors. Press any key to continue. Press the F4 (Cancel) key to return to the container hierarchy.

Command a Pager Object Browse to and highlight a Pager object. Press the F2 (Command) key. Use the Spacebar and the Backspace key to cycle through the list of commands until the desired command appears. Press Enter.

Delete a Pager Object Browse to and highlight a Pager object. Press Enter to open the object. Press the Delete key. Press the Tab key to confirm the deletion.


Detailed Procedures Adding a Pager Object

To add a Pager object: 1. Browse to and highlight the Operator Devices container. 2. Press the F3 (Add) key. 3. Highlight the Pager object from the list that appears and press

Enter. The first of two Pager object configuration screens appears (Figure 32-2). The second screen is shown in Figure 32-3.

Figure 32-2: Pager Object Configuration Screen 1


Figure 32-3: Pager Object Configuration Screen 2 4. Fill in the fields using Table 32-2.

Table 32-2: Pager Object Attributes Screen Area Attribute Required Default Options/Range Object Object



Description No Blank Maximum 40 characters Object Type Yes Pager The default is preset and cannot be changed. Object

Category Yes HVAC HVAC, Fire, Security, Services, Administrative



Screen Area (Cont.)


Engineering Values

Port Number Yes PORT2 Enumeration set: 1 = PORT1 2 = PORT2 3 = PORT3

Retries No 3 0-10 Process

Identifier Yes Blank This value is automatically assigned during

download, but must be assigned a value between 3 and 15 for the given device when it is being added from the VT100.

Pager Number

No Blank

Pager Service

No Blank

Modem Config Object

No Blank Object reference

Active Filter Yes Pass All Pass None, Pass All, Filter A, Filter B, Filter A and B

Priority Filter A


Category Filter A


Msg Type Filter A


Priority Filter B


Category Filter B


Msg Type Filter B






Editing a Pager Object To edit a Pager object: 1. Browse to and highlight a Pager object. 2. Press Enter to open the object. 3. Press the F3 (Edit) key. The Pager object attribute screen appears.

See Figure 32-2 and Figure 32-3. 4. Edit the fields according to Table 32-2. 5. Press the F3 (Save) key. 6. Check the User Assistance area of the screen to verify if the save



Commanding a Pager Object To command a Pager object: 4. Browse to and highlight a Pager object. 5. Press the F2 (Command) key. The Command field appears. 6. Use the Spacebar and the Backspace key to cycle through the list

of commands until the desired command appears. The Pager object supports the commands identified in Table 32-3.

Table 32-3: Supported Commands Command Description Disable Writes Enable attribute to False. Causes Pager object to ignore

incoming SNR messages. Enable Writes Enable attribute to True. Causes Pager object to process

incoming SNR messages.

7. Press Enter.

Deleting a Pager Object To delete a Pager object: 1. Browse to and highlight a Pager object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Troubleshooting If the Pager object experiences problems, verify the values of the Pager Number and Pager Service attributes. Include area codes where appropriate. If problems persist, see Troubleshooting Using Internal Attributes below.

Troubleshooting Using Internal Attributes Table 32-4 shows internal attributes of the Pager object. These attributes may be helpful in troubleshooting Pager object problems. To view internal attributes: 1. Browse to and highlight a Pager object. 2. Press Enter to open the object. 3. Press 0 to view all attributes. Figure 32-4 and Figure 32-5 show

sample screens with all Pager attributes displayed.

Table 32-4: Pager Object Internal Attributes Attribute Sample Value Description Dial Reply Connect 9600 Connected status of the Dial command Req ID Send CrCr Message sent to request the ID Req ID Reply* CrLf ID = Request ID message Req ID Read Cnt** 0 Number of retries for this message Req ID Retry 2 Seconds Delay before reading the reply Snd ID Send EcPG1Cr Send ID message Snd ID Reply* CrAkCrEcBrpCr Acknowledgement of a good reply for the Send ID message Snd ID Read Cnt** 0 Number of retries for this message Snd ID Retry 1 Seconds Delay before reading the reply Snd Msg Send Sx5426623Cr

"Snr Msg etc." Message containing the Pager Number, SNR message, Alarm message, and control characters

Snd Msg Reply* CrAkCr Acknowledgement of a good reply for the Send message Snd Msg Read Cnt** 0 Number of retries for this message Snd Msg Retry 1 Seconds Delay before reading the reply Snd Trm Send EtCr Message sent to terminate the connection Snd Trm Reply* CrEcEtCr Acknowledgement of a good transmission for the Terminate

message Snd Trm Read Cnt** 0 Number of retries for this message Terminate Retry 0 Seconds Delay before reading the reply Last Executed Time 09:29:58 Time stamp of last message processed Last Executed Date 02 Aug 2001 Date stamp of last message processed * An Nk appearing in the value of this attribute (for example, CrNkCrEcBrpCr) indicates an error such as a

checksum error, transmission error, or missing area code. An Rs appearing in the value of this attribute (for example, CrRsCr) indicates the transmission violated a system rule (for example, invalid pager ID).

** If any of the Read Cnt values is the same as the Retries value, try increasing the Retries value to allow more connection attempts.


Figure 32-4: Sample Pager Object - All Attributes Displayed (Screen 1)

Figure 32-5: Sample Pager Object - All Attributes Displayed (Screen 2)


© May 1, 2002 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-1201217 Software Release 5.1

Chapter 33 Working with BACnet™ Group Objects T

Introduction Note: Do not confuse the BACnet™ Group object with the

Johnson Controls Group object. For information on the Group object, refer to the Working with Group Objects chapter (LIT-6892060) of the N30 Supervisory Controller User’s Manual or the Group chapter (LIT-694420) of the Object Dictionary.

The BACnet Group object provides the user with the ability to customize the organization of objects within the site. The BACnet Group object simplifies the exchange of information between objects by calling all members of the group at once. A group consists of any combination of object types. For example, you can use the BACnet Group object to monitor the temperature in different rooms throughout a floor of a building. This chapter describes the difference between BACnet Group objects and Group objects and how to:

• add a BACnet Group object

• edit a BACnet Group object

• delete a BACnet Group object Note: The BACnet Group object is not VT100 configurable. You

must use Project Builder to configure the BACnet Group object.

See the American Society of Heating, Refrigerating, and Air-conditioning Engineers (ASHRAE) Standard 135-1995 for information on this object and the BACnet communication standard.

Working with BACnet Group Objects 33-2

Key Concepts BACnet Group Object vs Johnson Controls Proprietary Group Object

Differences between BACnet Group objects and Johnson Control Proprietary Group objects are:

• BACnet Group objects are compliant with the BACnet protocol, while Group objects are not.

• BACnet Group objects reference any object except another BACnet Group object as long as all members of the group reside in the same device that maintains the BACnet Group object. Group objects can reference other Group objects and objects that do not reside in the same device.

• BACnet Group objects have no limit to the number of members in a group, and each object member within the group includes one or more of its attributes. The Group object can hold up to 75 group members.

• BACnet Group objects list multiple attributes of the group members while the Group objects only list the Present Value of the group members.

For information on the Group object, refer to the Working with Group Objects chapter (LIT-6892060) of the N30 Supervisory Controller User’s Manual or the Group chapter (LIT-694420) of the Object Dictionary.

Attributes The values of an object’s attributes determine how the object operates. The BACnet Group object attributes are described below. For additional information about the BACnet Group object and its attributes, refer to the BACnet Group chapter (LIT-694180) of the Object Dictionary.




Object Type Indicates membership in a particular object type class. In this case, the object type is BACnet Group.

Object Identifier Identifies the object with a unique code.

List of Group Members Contains the references (Input References) that define the members of the group. These group members are referenced during a transaction. The List of Group Members consists of two parts:

• Object Identifier (Object ID)

• List of Property References (Attribute or Attribute with Array) In M-View, the Object Identifier and the List of Property References form the Input Reference. The Input Reference uses the syntax shown in Table 33-1. Nesting is not allowed and the List of Group Members cannot refer to the Present Value property of the BACnet Group object. Refer to Editing a BACnet Group Object in the Detailed Procedures to add and delete the Input Reference elements of this attribute.

Table 33-1: Input Reference Syntax Input Reference Type Format Example Full Reference with Array Index

<Device ID>.<Object ID>.<Attribute(Array)> B7F3N01.Programming.AV{1} .Priority Array[8]

Full Reference without Array Index

<Device ID>.<Object ID>.<Attribute> B7F3N01.Programming.AV{1} .Present Value

Functional Name with Array Index

<Object ID>.<Attribute (Array)> Test AV.Priority Array[8]

Functional Name without Array Index

<Object ID>.<Attribute> Test AV.Present Value

BACnet Syntax with Array Index

#<Device ID>:(#<class>:<instance>).#<Attribute (Array)>

#32:(#2:65001).#87[8]

BACnet Syntax without Array Index

#<Device ID>:(#<class>:<instance>).#<Attribute> #32:(#2:65001).#85


Detailed Procedures Notes: The BACnet Group object is not VT100 configurable. You

must use Project Builder to configure the BACnet Group object. Before performing the following procedures, start Project Builder and open or create the project in which you want to add a BACnet Group object. Refer to the Getting Started chapter (LIT-693215) of Project Builder User’s Guide.

Adding a BACnet Group Object Note: You must use Project Builder to add the BACnet Group

object.

For instructions on adding a BACnet Group object, refer to the Working with Objects and the M-View Screen chapter (LIT-693230) of Project Builder User’s Guide.

Editing a BACnet Group Object Note: Figure 33-1 and Figure 33-2 show a Group object configured

to monitor the objects used by the Optimal Start (OST) object that controls the heating and cooling of a zone in a building for the month of December.

To edit a BACnet Group object: 1. Double-click the row head of the BACnet Group object or, with

the BACnet Group object selected, select Edit Object on the Edit menu. The M-View Configuration dialog box appears (Figure 33-1).


Figure 33-1: M-View Configuration Dialog Box 2. Edit the parameters using Table 33-2. Refer to the BACnet Group

chapter (LIT-694180) of the Object Dictionary. Note: Clicking Cancel returns you to Project Builder without

saving your changes.

Table 33-2: Editing BACnet Group Object Attributes To Edit This Attribute Do This Object Name Type a name for this BACnet Group object (optional). Description Type a description for this BACnet Group object (optional). Object Type This attribute cannot be edited. Object Type is BACnet Group. Object Category Select the desired category for this BACnet Group object. Default is HVAC.

3. Click the List Elements button. The List Of Group Members dialog

box appears (Figure 33-2).


Figure 33-2: List Of Group Members Dialog Box - Optimal Start (OST) Example

Notes: If there are no Input References defined, the left side of the screen is blank. Clicking Cancel or Back returns you to the M-View Configuration dialog box without saving your changes. In Figure 33-2, Input Reference 3 is a reference to the Present Value of an Analog Value object’s Outdoor Air Temperature used by the OST object in its calculations.

4. To add an Input Reference, click Add and type the Input Reference in the box according to the syntax in Table 33-1. Repeat this step if you want to add more Input References.

Note: You must define at least one input reference to download the database to an N30 and save your changes.

5. To delete an Input Reference, select the Input Reference box you want to delete and click Delete. Repeat this step if you want to delete more Input References.

6. Click Done to save your changes and return to the M-View Configuration dialog box.

7. Click OK to save your changes and return to Project Builder. Note: To view the Present Value of the BACnet Group object,

enter online mode and use the M-Inspector feature.


Deleting a BACnet Group Object You can delete a BACnet Group object using Project Builder or the VT100.

Using Project Builder For instructions on deleting a BACnet Group object using Project Builder, refer to the Working with Objects and the M-View Screen chapter (LIT-693230) of Project Builder User’s Guide.

Using the VT100 To delete a BACnet Group object using the VT100: 1. Browse to and highlight the BACnet Group object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.

Controls Group 507 E. Michigan Street P.O. Box 423 www.johnsoncontrols.comMilwaukee, WI 53201 Printed in U.S.A.


© May 1, 2002 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-1201218 Software Release 5.1

Chapter 34 Working with Event Enrollment Objects T

Introduction The Event Enrollment object monitors the value of a single attribute in another object in the same or another device, and reports events based on changes in the attribute’s value. For example, the Event Enrollment object can monitor the temperature value from a room thermostat and report an event if the temperature falls below a low limit parameter value. Note: The Event Enrollment object is not VT100 configurable.

You must use Project Builder to configure the Event Enrollment object.

This chapter describes how to:

• add an Event Enrollment object

• edit an Event Enrollment object

• command an Event Enrollment object

• delete an Event Enrollment object

• edit Event Parameters - examples

Working with Event Enrollment Objects 34-2

Key Concepts Event Enrollment Object

Unlike the Analog Alarm objects and Multistate Alarm objects in the N30 Supervisory Controller, Event Enrollment objects are compliant with BACnet™ protocol. The Event Enrollment object’s attributes contain information for generating events. The object is configured to trigger an event when the value of the user-defined referenced attribute changes and meets the specified criteria. When an event occurs, a notification message is sent to the user-defined recipients. Notification message recipients are devices defined in the Notification Class object referenced by the Event Enrollment object. See the Event Enrollment/BACnet Event Enrollment chapter (LIT-694160) of the Object Dictionary or the American Society of Heating, Refrigerating and Air-conditioning Engineers (ASHRAE) Standard 135-1995 for information on this object and the BACnet communication standard.

Attributes The values of an object’s attributes determine how the object operates. The Event Enrollment object attributes are described below.



Object Type Indicates membership in a particular object type class. In this case, the object type is Event Enrollment.

Object Property Reference Designates the particular object and attribute referenced by the Event Enrollment object. The condition specified by the Event Type is applied to the referenced attribute to determine the Event State. The Object Property Reference (also referred to as Input Reference) uses one of the syntax options shown in Table 34-1.


Table 34-1: Object Property Reference Syntax Object Property Reference Type Format Example Full Reference with Array Index

<Device ID>.<Object ID>.<Attribute (Array)> B7F3N01.Programming.AV{1} .Priority Array[8]

Full Reference without Array IndexP

1P

<Device ID>.<Object ID>.<Attribute> B7F3N01.Programming.AV{1} .Present Value

Functional Name with Array Index

<Object ID>.<Attribute (Array)> Test AV.Priority Array[8]

Functional Name without Array IndexP

2P

<Object ID>.<Attribute> Test AV.Present Value

BACnet Syntax with Array Index

#<Device ID>:(#<class>:<instance>).#<Attribute (Array)>

#32:(#2:65001).#87[8]

BACnet Syntax without Array Index

#<Device ID>:(#<class>:<instance>).#<Attribute> #32:(#2:65001).#85

1 Used for object references in another N30 device. 2 Used for object references in the same N30 device.

Event Type Indicates the type of event analysis used to detect events that change the Event State and report to recipient devices. Table 34-2 describes each event type. See the Editing Event Parameters - Examples section of this chapter.

Table 34-2: Event Types Event Type Description Change of Bitstring Generates an off-normal transition when the value of the referenced property is

equal to one of the user-defined Bitstring Values (List Elements after applying the Bitmask) and the values are equal for the amount of seconds defined by the Time Delay attribute. The Bitmask defines the bits important for monitoring.

Change of State Generates an off-normal transition when the value of the referenced property is equal to one of the values in the List of Values (List Elements) and the values are equal for the number of seconds defined by the Time Delay attribute.

Change of Value Generates a normal transition when the value of a referenced property changes by an amount equal to or greater than the referenced property increment (Change of Value [COV] Increment) for the amount of seconds defined by the Time Delay attribute.

Command Failure Generates an off-normal transition if the values of the referenced property and the Feedback Reference are not equal for a time greater than the number of seconds defined by the Time Delay attribute.

Floating Limit Generates a transition to high or low limit alarm if the value of the referenced property is higher or lower than the range of values determined by the current value of the Setpoint Reference, High Limit, Low Limit, and Deadband for a time greater than the number of seconds defined by the Time Delay attribute.

Out of Range Generates a transition to high or low limit alarm if the value of the referenced property is higher or lower than the range of values defined by the High Limit and Low Limit for a time greater than the number of seconds defined by the Time Delay attribute.


Event Parameter Provides the parameter values required to detect the specified Event Type in the referenced object.

Event Enable Defines three flags that determine if notifications are enabled for To Off Normal, To Fault, and To Normal transitions.

Notify Type Defines the notifications generated by the event analysis specified by Event Type as Event or Alarm types. Both types generate event notifications.

Notification Class References a Notification Class object in the device containing the Event Enrollment object. The Notification Class object specifies the handling, reporting, and acknowledgement characteristics for one or more Event Enrollment objects.

Alarm Message Text Designates the optional user-defined text that is included in event notification. For additional information about the Event Enrollment object and its attributes, refer to the Event Enrollment/BACnet Event Enrollment chapter (LIT-694160) of the Object Dictionary.


Detailed Procedures Notes: The Event Enrollment object is not VT100 configurable.

You must use Project Builder to configure the Event Enrollment object. Before performing the following procedures, start Project Builder and open or create the project in which you want to add an Event Enrollment object. Refer to the Getting Started chapter (LIT-693215) of Project Builder User’s Guide.

Adding an Event Enrollment Object Note: You must use Project Builder to add the Event Enrollment

object. You can only add the Event Enrollment object to other objects.

For instructions on adding an Event Enrollment object, refer to the Working with Objects and the M-View Screen chapter (LIT-693230) of Project Builder User’s Guide.

Editing an Event Enrollment Object To edit an Event Enrollment object: 1. Double-click the row head of the Event Enrollment object, or with

the Event Enrollment object selected, select Edit Object on the Edit menu. The M-View Edit Attributes dialog box appears (Figure 34-1).


Figure 34-1: M-View Edit Attributes Dialog Box 2. Edit the parameters using Table 34-3. Refer to the Event

Enrollment/BACnet Event Enrollment chapter (LIT-694160) of the Object Dictionary.


Table 34-3: Editing Event Enrollment Object Attributes To Edit This Attribute Do This Object Name Type a name for this Event Enrollment object (optional). Description Type a description for this Event Enrollment object (optional). Object Type This attribute cannot be edited. Object Type is Event Enrollment. Object Category Select the desired category for this Event Enrollment object from the

drop-down menu. Default is HVAC. Object Property Ref Type the Object Property Reference in the box according to the syntax in

Table 34-1. Event Type Select the desired Event Type for this Event Enrollment object from the

drop-down menu. The options are Change of Bitstring, Change of State, Change of Value, Command Failure, Floating Limit, and Out of Range.

Event Parameters Click the Event Parameters button. Depending on the Event Type selected, a corresponding dialog box appears. Edit the parameters in the dialog box and click Done to save your changes and return to the M-View Edit Attributes dialog box. Refer to the Editing Event Parameters - Examples section in this chapter for examples on how to edit the parameters for each Event Type. Note: Clicking Cancel or Back returns you to the previous dialog box

without saving your changes. Event Enable Click the Event Enable button. The Event Enable Dialog Box appears.

Select True or False for the To Off Normal, To Fault, and To Normal attributes. Click Done.

Notify Type Select Event or Alarm as the Notify Type for this Event Enrollment object. Notification Class Type the Object Identifier (Object ID) of the Notification Class object from

which you are routing alarms. Alarm Message Text Type the desired text of the alarm message for event notification (optional).

3. Click OK to save your changes and return to Project Builder.


Commanding an Event Enrollment Object You can command an Event Enrollment object using the M-Series Workstation or the VT100. The Event Enrollment object must be online.

Using the M-Series Workstation To command an Event Enrollment object using the M-Series Workstation: 1. In M-Explorer, select the Event Enrollment object. 2. On the Actions menu, click Inspect. The M-Inspector dialog box


Figure 34-2: M-Inspector Dialog Box - M-Command Tab 3. Click the M-Command tab. 4. Select Enable or Disable in the Command drop-down menu. 5. Click Execute. 6. Click Close.


Using the VT100 To command an Event Enrollment object using the VT100: 1. Browse to and highlight the Event Enrollment object. 2. Press the F2 (Command) key. The command field appears. 3. Use the Spacebar and the Backspace key to select the desired

command. The Event Enrollment object supports the commands in Table 34-4.

Table 34-4: Supported Commands Command Description Enable The Event Enrollment object processes new values from the

referenced attribute (Object Property Reference). Disable The Event Enrollment object ignores new values from the

referenced attribute (Object Property Reference).

4. Press Enter.

Deleting an Event Enrollment Object You can delete an Event Enrollment object using Project Builder or the VT100.

Using Project Builder For instructions on deleting an Event Enrollment object using Project Builder, refer to the Working with Objects and the M-View Screen chapter (LIT-693230) of Project Builder User’s Guide.

Using the VT100 To delete an Event Enrollment object using the VT100: 1. Browse to and highlight the Event Enrollment object. 2. Press Enter to open the object. 3. Press the Delete key. 4. Press the Tab key to confirm the deletion.


Editing Event Parameters - Examples This section provides examples for editing the Event Parameters of each Event Type. For all other attributes, follow the instructions in the Editing an Event Enrollment Object section in this chapter.

Change of Bitstring - Example 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-3 shows an example of an Event Enrollment object that references an Analog Value object named SetpointAV that generates an off-normal transition when the value of its Status Flags attribute changes. The Status Flags attribute uses a bitstring data type with 4 elements (bits). Refer to Table 1 in About the Object Dictionary (LIT-694010) for data type descriptions.

Figure 34-3: M-View Edit Attributes Dialog Box - Change of Bitstring Example 2. Select Change of bitstring in the Event Type drop-down menu. 3. Click the Event Parameters button. The Change of Bitstring Event

Parameters dialog box appears (Figure 34-4).


Figure 34-4: Change of Bitstring Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay

box that you want to wait before generating an event after a value change.

5. Click the 4 Elements button. The Bitmask dialog box appears (Figure 34-5).

Figure 34-5: Bitmask Dialog Box 6. Select True or False for each element in the Bitmask. Note: Only elements with a value of True in the Bitmask are

included in the event analysis and generate alarms.

7. Click Done to save changes and return to the Change of Bitstring Event Parameters dialog box (Figure 34-4).

8. Click the List Elements button. The Bitstring Values dialog box appears (Figure 34-6).


Figure 34-6: Bitstring Values Dialog Box 9. Click the Add or Delete button to add or delete Bitstring Values. Note: One value is required for each set of elements’ values that is

required to generate an event. Use the Bitmask to exclude elements that are not involved in any event.

10. Click the 4 Elements button to display the values. The Bitstring Values - 4 Elements dialog box appears showing the 4 elements (Figure 34-7).

Figure 34-7: Bitstring Values - 4 Elements Dialog Box 11. Select True or False for each bitstring value. Note: An event generates when the actual value of the attribute is

equal to this set of bit values.

12. Click Done to save changes and return to the Bitstring Values dialog box (Figure 34-6).


13. Click Done to save changes and return to the Change of Bitstring Event Parameters dialog box (Figure 34-4).

14. Click Done to save changes and return to the M-View Edit Attributes dialog box (Figure 34-3).

15. Click OK to save changes and return to Project Builder.


Change of State - Example 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-8 shows an example of a Multistate Value object named FeedbackMV that generates an off-normal transition when the value of its Reliability attribute changes. The Reliability attribute uses the enumerated data type.

Figure 34-8: M-View Edit Attributes Dialog Box - Change of State Example 2. Select Change of state in the Event Type drop-down menu. 3. Click the Event Parameters button. The Change of State Event



Figure 34-9: Change of State Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay


5. Click the List Elements button. The List of Values dialog box appears (Figure 34-10).

Figure 34-10: List of Values Dialog Box 6. Click Add or Delete to add or delete values. Note: One value is required for each attribute status that is required

to generate an event.

7. Select the desired status for each value. Note: An event generates when the actual status of the attribute is

equal to this status.

8. Click Done to save changes and return to the Change of State Event Parameters dialog box (Figure 34-9).


Change of Value - Example 1 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-11 shows an example of an Analog Input object named RoomTemp that generates a normal transition when the value of its Present Value attribute changes by a specified amount. The Present Value attribute uses the analog (Float) data type.

Figure 34-11: M-View Edit Attributes Dialog Box - Change of Value Example 1

2. Select Change of value in the Event Type drop-down menu. 3. Click the Event Parameters button. The Change of Value Event



Figure 34-12: Change of Value Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay


5. Type the desired value in the COV Increment box that you want the attribute to change before generating an alarm.

Note: In this example, an event is generated 120 seconds after the room temperature changes 3.0 degrees.

6. Click Done to save change and return to the M-View Edit Attributes dialog box (Figure 34-11).



Change of Value - Example 2 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-13 shows an example of an Analog Value object named FeedbackAV that generates a normal transition when the value of its Status Flags attribute changes. The Status Flags attribute uses a bitstring data type with 4 elements (bits). See Figure 34-14.

Figure 34-13: M-View Edit Attributes Dialog Box - Change of Value Example 2

2. Select Change of value in the Event Type drop-down menu. 3. Click the Event Parameters button. The Change of Value Event



Figure 34-14: Change of Value Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay


5. Select True or False for each value. Notes: When the value is True, any change of value generates an

event. In this example, an event is generated 30 seconds after the InAlarm, Fault, or OutOfService changes state. Any changes to the Overridden value is ignored.




Command Failure - Example 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-15 shows an example of a Binary Value object named N30.Programming.BV that generates an offnormal transition when a command to its Present Value attribute fails. Failure is determined by the value of the feedback reference Fan4.PresentValue.

Figure 34-15: M-View Edit Attributes Dialog Box - Command Failure Example 2. Select Command Failure in the Event Type drop-down menu. 3. Click the Event Parameters button. The Command Failure Event



Figure 34-16: Command Failure Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay

box that you want to wait before generating an event. An event generates after a command has been issued and the feedback value does not change.

5. Type the reference for the attribute used to confirm the command execution in the Feedback Reference box.

Note: The referenced command attribute and the referenced feedback attribute must be of the same data type.




Floating Limit - Example 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-17 shows an example of an Analog Input object named RoomTemp that transitions to high or low limit alarm when the value of its Present Value attribute exceeds the configured floating limit values.

Figure 34-17: M-View Edit Attributes Dialog Box - Floating Limit Example 2. Select Floating limit in the Event Type drop-down menu. 3. Click the Event Parameters button. The Floating Limit Event



Figure 34-18: Floating Limit Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay


5. Type the reference for the attribute that provides the value used as a setpoint reference value in the Setpoint Reference box.

6. Type the lowest amount (in degrees) that the temperature can fall below the referenced setpoint value before generating a low limit alarm in the Low Limit box.

7. Type the highest amount (in degrees) that the temperature can rise above the referenced setpoint value before generating a high limit alarm in the High Limit box.

8. Type the amount of change (in degrees) from the limit value required for the attribute to return to normal in the Deadband box.

Notes: In this example, the Present Value attribute is in alarm when it is 4 degrees above or 3 degrees below the reference setpoint. The Present Value attribute returns to normal when it is 2.5 degrees above or 1.5 degrees below the reference setpoint. The Deadband value is considered when the temperature returns from a high or low limit state to a normal state. Use this feature to reduce toggling between the high or low limit state and a normal state when the temperature remains near the high or low limit.




Out of Range - Example 1. Edit the parameters of the M-View Edit Attributes dialog box

using Table 34-3. Figure 34-19 shows an example of an Analog Input object named RoomTemp that transitions to high or low limit alarm when the value of its Present Value attribute goes out of the user-defined range.

Figure 34-19: M-View Edit Attributes Dialog Box - Out of Range Example 2. Select Out of range in the Event Type drop-down menu. 3. Click the Event Parameters button. The Out of Range Event



Figure 34-20: Out of Range Event Parameters Dialog Box 4. Type the desired amount of time (in seconds) in the Time Delay


5. Type the value (in degrees) for the low end of the range in the Low Limit box.

6. Type the value (in degrees) for the high end of the range in the High Limit box.

7. Type the amount of change (in degrees) from the limit value required for the attribute to return to normal in the Deadband box.

Note: In this example, the Present Value attribute is in alarm outside of the range of 66.0 to 74.0 and returns to normal when it is inside the range of 68.0 to 72.0.



Controls Group 507 E. Michigan Street P.O. Box 423 www.johnsoncontrols.comMilwaukee, WI 53201 Printed in U.S.A.

N30 Supervisory Controller User’s Manual A-1

Appendix A Building an Energy Management Application

Introduction Numerous energy management applications are possible for small to mid-size site configurations. This document provides information to consider when building a core energy management application, including what objects are involved and how attributes interact. This document describes how to build a core energy management application.



Key Concepts Object Interaction

Different objects interact in a core energy management application. Figure A-1 illustrates an example of an energy management application. Table A-1 describes the objects and their role in energy management.

N2 Pulse CounterObject

Pulse MeterObject DLLR Object

Load Object

Load Object

N2 Binary OutputObject

N2 Binary OutputObject

Utility ProfileObject

Pulse MeterObject

N2 Binary InputObject

(Comfort Alarm)

Schedule Object

1

2

3

2

4

45

6

6

9

8

DLLR Flow

N2 Binary InputObject

(Output Alarm)

7

Figure A-1: Energy Management Example


Table A-1: Energy Management Objects Number Object Role 1 DLLR Receives energy consumption data from the Pulse Meter object to manage

demand limiting and load rolling through the shedding of loads. 2 Load Registers with the DLLR object to let the DLLR object know that it exists and

can be shed. 3 Utility Profile Collects utility data from a Pulse Meter object and a DLLR object. 4 Pulse Meter Collects energy consumption data to be available to either the Utility Profile

object or the DLLR object. 5 N2 Pulse

Counter Counts energy pulses via the N2 Bus from an actual hardware meter and relates the data to the Pulse Meter object.

6 Output Object

Acts as the associated output for the Load object, which switches it off for the actual physical load shedding. Besides an N2 Binary Output object, a Load’s associated output can also be a Binary Value (BV), Multistate Output (MSO), Multistate Value (MSV), or Multiple Command (MC) object.

7 Output Alarm Object

Provides the attribute supplying the output alarm condition. This attribute can be any numerical attribute of any object type in which a change from zero to a non-zero value indicates an alarm condition.

8 Comfort Alarm Object

Provides the attribute supplying the comfort override alarm condition. This attribute can be any numerical attribute of any object type in which a change from zero to a non-zero value indicates an alarm condition.

9 Schedule Object

Starts new billing periods by resetting the Utility Profile object.


Attribute Involvement Building a core energy management application means that each object must have its attributes configured to reference the appropriate objects in order to achieve the desired results. Table A-2 lists the objects and attributes involved and guidelines for data entry.

Table A-2: Key Components for a Core Energy Management Application Object Type/Function

Attributes Involved

Data Entry Guidelines

DLLR Meter Object Enter the exact name of that Pulse Meter object, which is dedicated to serve only as an input to this particular DLLR object.

DLLR Object Enter the exact name of the DLLR object. Output Attribute Enter the attribute of the output object that will be shut off to shed

the load. Make sure that the attribute supports a prioritized write. Output Alarm Attr Enter the attribute supplying the Output Alarm condition.

Load

Comfort Alarm Attr Enter the attribute supplying the Comfort Alarm condition. Meter Object Enter the exact name of that Pulse Meter object, which is

dedicated to serve only as an input to this particular Utility Profile object.

Utility Profile

DLLR Object Enter the exact name of the DLLR object. Pulse Meter Counter Object Enter the exact name of the N2 Pulse Counter object. The

N2 Pulse Counter object must reside on the same device as the Pulse Meter object.

N2 Pulse Counter None None. The Pulse Meter object references this object. Output Object None None. The Load object references this object’s Output Attribute. Output Alarm Object

None None. The Load object references this object ‘s Output Alarm attribute.

Comfort Alarm Object

None None. The Load object references this object’s Comfort Alarm attribute.

Schedule Object List of Prop Refs Enter the name of the Utility Profile object and schedule the Utility Profile’s Reset attribute to go to 1 at the time you want a new billing period to start, and to go back to 0 one minute later. Setting back the reset attribute is necessary to avoid a premature start of the billing period in case the Schedule’s fast clock feature should run.


Advanced Object Functions Beyond a core application, the energy management objects can combine with other objects to perform a variety of functions for sophisticated applications. The possibilities are too numerous to be covered in this document. Table A-3 offers an overview of the objects and advanced functions possible in energy management applications.

Table A-3: Advanced Object Functions Object Function DLLR Operates at different demand limits and load rolling targets over time.

Allows an external source instead of the internal algorithm to dictate the amounts to shed. Accounts for Pulse Meter failure through the configuration of its algorithm.

Load Adapts shedding priority to the current situation. Performs local load rolling, such as cyclically running one out of many air handlers. This requires the load to drive a Multiple Command object, which coordinates the local load rolling. Handles analog loads, such as adjusting setpoints when shed. Again, this functionality is best achieved through a Multiple Command object as the load’s output object. Remains shed through load configuration in case of an abnormal situation.

Utility Profile

Provides a breakdown of energy consumption data over variable time periods. Provides a breakdown of energy consumption data into different energy tariffs. In this case one Utility Profile per tariff must be used. The coordination of the Utility Profiles is best achieved through scheduling, interlock, and/or multiple command objects.

Pulse Meter Allows electronic filtering of the pulse rate input signal by varying its Sample Time attribute. Analog Alarm

Provides detailed alarm notification for any abnormal situations in the energy management application. Alarm objects can be attached to any numerical attribute of any object.

Multistate Alarm

Provides detailed alarm notification for any abnormal situations in the energy management application. Alarm objects can be attached to any numerical attribute of any object.

Interlock Monitors any numerical attribute of any object involved in the DLLR application. Invokes any command of any object involved in the DLLR application. Can send commands with or without delays to itself. This opens up many opportunities for periodic execution of certain processes, such as local load rolling. Tunes the energy management application at runtime by modifying parameters in the DLLR and Load objects depending on certain conditions. Serves as Comfort Alarm points used by Load objects.

Multiple Command

Invokes any command of any object involved in the DLLR application. Coordinates which of several Utility Profiles currently is active. Replaces an N2 Binary Output as a load’s output. Sends commands with or without delays to itself. This opens up many opportunities for periodic execution of certain processes, such as local load rolling. Serves as Comfort Alarm points used by Load objects.

Schedule Resets Utility Profiles or to select the currently active Utility Profile. Tunes the energy management application at runtime by modifying parameters in the DLLR and Load objects, depending on certain conditions.

Trend Log Provides additional detailed energy data. Global Data Sharing

Propagates data within the energy management application.

Signal Select

Changes attributes of the objects. Monitors numerical attributes and subsequently propagates data within the energy management application, based on the result of the logic evaluation of the input conditions.


Procedure Overview Table A-4: Building an Energy Management Application To Do This Follow These Steps: Build an Energy Management Application

Add N2 point objects to the database, including N2 Pulse Counter objects. Add the DLLR object. Add a Pulse Meter object referencing the N2 Pulse Counter object and the DLLR object. Add a Utility Profile object to the same device as the Pulse Meter and DLLR objects. Add another Pulse Meter object referencing the N2 Pulse Counter object and the Utility Profile object. Add Load objects referencing output loads to potentially be shed and referencing objects representing an Output Alarm and a Comfort Alarm. Add a Schedule object referencing the Utility Profile object. Verify that the energy management application is operating correctly.


Detailed Procedures Building an Energy Management Application

To build an energy management application: 1. Add N2 point objects to the database, including N2 Pulse Counter

objects. See the N30 Supervisory Controller Point Mapping Technical Bulletin (LIT-6891400).

2. Add the DLLR object. One DLLR object exists per meter hardware piece. For example, a building with three electric meters should have three DLLR objects to regulate the system. Multiple DLLR objects can exist in one N30.

3. Add a Pulse Meter object referencing the N2 Pulse Counter object and the DLLR object. The Pulse Meter should be on the same device as the DLLR object.

4. Add a Utility Profile object to the same device as the Pulse Meter and DLLR objects.

5. Add another Pulse Meter object referencing the N2 Pulse Counter object and the Utility Profile object. One Pulse Meter object should be dedicated to one Utility Profile object.

6. Add Load objects referencing output loads to potentially be shed and referencing objects representing an Output Alarm and a Comfort Alarm. A maximum of 80 Load objects can register to one DLLR. A maximum of 80 output objects can be referenced by the 80 Load objects.

7. Add a Schedule object referencing the Utility Profile object. This Schedule is required to reset the Utility Profile object at the end of each billing period. Enter the name of the Utility Profile object and schedule the Utility Profile’s Reset attribute to go to 1 at the time you want a new billing period to start, and to go back to 0 one minute later. Setting back the reset attribute is necessary to avoid a premature start of the billing period if the Schedule’s fast clock feature should run.

8. Verify that the energy management application is operating correctly. Refer to the Troubleshooting section of this document.


Troubleshooting This section provides some guidelines for making an energy management application successful.

Table A-5: Energy Management Troubleshooting Guidelines Guideline Procedure Ensure All Loads are Capable of Registering Correctly

It is best to throttle (regulate the speed of) the load registration process by modifying each Load object’s Registering Delay attribute, if one or more of the following conditions exist: • twenty or more Load objects are used per DLLR object • Load objects are mainly not on the same device as the DLLR object • the device housing the DLLR object is likely to be low on acquired memory To throttle the load registration process, assign a Register Delay of 5 seconds to the first load to register, a delay of 6 seconds to the next, and so on. This results in approximately one incoming registration message per second during the Registering Phase. This also results and in a predictable order for the list of loads kept inside the DLLR object. Leaving the Register Delay attributes of all Load objects to zero seconds result in the fastest possible load registration. However, if this overloads the device, such as an N30, housing the DLLR object, use the Register Delay attributes to throttle the registration process.

Ensure All Loads are Registered Correctly

After creating the entire database, check if the Load objects are correctly registered at their respective DLLR objects. Depending on the configuration settings in the Load or DLLR objects, some loads may not have registered. Also, creating the database while certain devices are offline may result in unregistered loads. 1. Check if the DLLR object’s Number of Loads attribute matches the number of

loads expected to be registered (the number of loads created to register to the DLLR object). If the numbers match, the loads are registered correctly. If not, go the Step 2.

2. If the numbers do not match, or to ensure the correctness of the load registration process, run the DLLR object’s Force Register command: • To get all loads to register while the DLLR algorithm is not yet in a stage

in which it would be harmful to suspend its operation, run the DLLR object’s Force Register command with the command parameter set to True. This command erases the entire load registration information inside the DLLR object, and starts a new registration process.

• To get all loads to register while the DLLR algorithm is already in a stage in which it is critical not to suspend its operation, run the DLLR object’s Force Register command with the command parameter set to False. This command preserves the entire load registration information inside the DLLR object while starting a new registration process.

3. Wait the amount of time equal to the Register Delay attribute, and then recheck if the DLLR object’s Number of Loads attribute now matches the number of loads expected to be registered.

Note: Since the Number of Loads attribute does not refresh automatically, refresh the display by closing the current view and reopening it.



Guideline (Cont.) Procedure Ensure All Loads are Registered Correctly (Cont.)

4. If the numbers still do not match, and re-sending the Load object’s Force Register command does not correct the situation, check each Load object’s Load Number attribute. A load number of zero indicates unsuccessful registering that can be the result of several factors. Each Load object with a Load Number attribute value of zero should be checked with these steps: a. Check if all Load objects are online to their DLLR object. If all are online,

the loads are registered correctly. If not, continue with Step 4b. b. Check if all Load objects have the correct name of the DLLR object

entered in their DLLR object attribute. If all have the correct name, all loads are registered correctly. If not, continue with Step 4c.

c. Run the Force Register command for each questionable load. d. Wait until the Registering Delay time has elapsed, then recheck the Load

Number attribute to see if it contains a non-zero number. This would indicate that the load is now registered. In addition, if the DLLR object’s Number of Loads attribute increases by one, this also indicates the load is now registered.

e. Repeat Steps 4c and 4d. If it still appears that loads are not registered, continue with Step 4f.

f. Check the DLLR object’s Registering Phase attribute. This attribute defines the length of the registration process. In large systems it may be necessary to extend this value to a time similar to the highest Register Delay attribute.

g. Run the DLLR object’s Force Register command with the command parameter set to True. This assures that loads are registered correctly, as long as they are configured correctly and online.

If running the DLLR object’s Force Register command never results in correct load registration, a memory or communication overload may exist, and registration messages may be lost. In this case, throttle the registration process as described earlier. If this does not improve the registration process, there may be a communication or memory problem in the system, requiring a re-evaluation of the entire system.

Ensure All Loads are Potentially Eligible for Shedding

An incorrectly configured load may never be eligible for shedding and therefore be of no use to the system. To check if all loads have the potential to be eligible, each load must be individually checked. 1. Check if the DLLR object’s Eligible for DL Only, Eligible for LR Only, and

Eligible for DLLR attributes add up to the Number of Loads attribute. If the numbers add up, and the DLLR object’s Not Eligible attribute is zero, the loads are eligible for shedding. If both conditions are not met, continue with Step 2.

Note: The above attributes do not refresh automatically each time they are updated. To refresh the display, close the current view and reopen it.

2. Check each Load object’s Eligibility attribute. If Ineligible, continue with Step 3. 3. Check each Load object’s Shed Refusal attribute for a reason why the Load

may be ineligible for shedding. 4. Remove all of the conditions listed in the Load object’s Shed Refusal attribute

until the load becomes eligible, and Shed Refusal becomes No Refusal. Continued on next page . . .


Guideline (Cont.) Procedure Ensure the Pulse Meter is Working Correctly

If you want to use the Demand Limiting feature of the DLLR object, a rate of consumption must be fed into the algorithm. While this rate could be provided by any analog Present Value attribute of type float, the DLLR object is optimized to use a Pulse Meter object as its input. To ensure proper Pulse Meter operation: 1. Check the Pulse Meter object’s Reliability attribute. If it is Reliable, the Pulse

Meter object is operating correctly. If the value is Unreliable for more than a few minutes, the Pulse Meter object is not working correctly. Go to Step 2.

2. Check if the Pulse Counter object specified in the Pulse Meter’s Counter Object attribute resides on the same device as the Pulse Meter. If both objects reside on the same device, but the Pulse Meter object is still Unreliable, go to Step 3.

3. Verify that the Pulse Counter object’s N2 device is online. 4. Check if the value of the Pulse Meter object’s Consumption attribute actually

represents the consumption of a single pulse. Refer to the meter’s type plate or user manual.

5. Check if the value of the Pulse Meter object’s Rate Constant attribute equals the Rate Units attribute multiplied by seconds divided by the value of the Consumption Units attribute. For example, if the Rate Unit is KW, and the Consumption Unit is KWh, the correct value of the Rate Constant attribute must be KWs / KWh = 3600 s/h.

6. Check that the calculated rate does not exceed the Pulse Meter object’s Rate Limit attribute. To estimate the calculated rate: a. Monitor the Pulse Meter’s Pulse Count attribute for a minute. It should

increase by a few points within that minute. However, in some cases the rate of consumption is so low that no pulse is generated in a minute. If this is true, wait until a pulse is generated and counted by the Pulse Counter object and keep track of the time until the next pulse.

b. Multiply the number of Pulse Counts from Step 6a with the value of the Pulse Consumption attribute, then divide it by the pulse counting period length in seconds, and multiply that result by the value of the Rate Constant attribute. The result should be reasonable. In most cases, you can refer to figures from utility bills to check if the values are reasonable.

c. Make sure the Pulse Meter object’s Sample Time is set to 60 seconds. This ensures that the DLLR algorithm always uses current data calculated from the last minute’s consumption. If a Sample Time of 60 seconds provides too few pulses to reasonably operate the Demand Limiting algorithm, use a different pulse generator with a higher resolution. The pulse count is too low if 60-second intervals without any pulses occur, even during normal building operation. However, sampling no pulses during some minutes at night may be a reasonable rate. The DLLR algorithm works best when the rate is higher than ten pulses per minute. This way the rate used in the algorithm is at least within 10% of its real value.

When a meter different from a Pulse Meter is used, most considerations described above do not apply. In this case, make sure the meter’s Present Value attribute can be correctly read, and that it represents the average demand during the last 60 seconds.



Guideline (Cont.) Procedure Ensure the End-of-Interval (EOI) Pulse is Working Correctly

When the Fixed Window Algorithm is used, the End-of-Interval information has to be made available to the DLLR object. After one entire interval has elapsed, the DLLR object’s EOI Alarm attribute should remain set to False. If it is set to True, the DLLR object did not receive the End-of-Interval information. In this case, check the following: 1. If the utility company provides the End-of-Interval pulse, verity that the EOI

pulse creating device is correctly wired to the system. 2. Verify that the object, typically a BI, actually changes to True for a short time

when the pulse is detected. The pulse should be long enough to allow the N2 Bus to poll the high value from the N2 controller and generate a Change-of-Value message to the DLLR object. In case the pulse cannot be reliably transferred into a BI or similar object and on to the DLLR object, a latching mechanism has to be added that ensures a pulse long enough to be definitely detected.

3. Verify that the End-of-Interval regularly occurs once after each interval is finished.

4. Verify that the object providing the End-of-Interval information is online to the DLLR object.

Ensure the Load Rolling Algorithm is Working Correctly

The DLLR object’s Load Rolling algorithm, when the LR Mode attribute is set to LR Shedding, tries to keep the LR Shed attribute equal to or greater than the LR Target attribute. This algorithm can easily be verified using the following procedure: 1. Set the DLLR object’s LR Mode attribute to LR Shedding. 2. Verify that the DLLR object’s LR Shed attribute quickly becomes equal to or

greater than the DLLR object’s LR Target attribute. 3. If it does not reach the target, verify that the DLLR object’s DLLR Status

attribute reads In Alarm. 4. Make sure that the DLLR object’s LR Target is not unreasonably high, and

ensure that enough eligible loads are available to meet the target. Occasionally not meeting the LR Target is acceptable, but it should be an exception.

Ensure the Demand Limiting Algorithm is Working Correctly

When the DLLR object’s DL Mode attribute is set to Shedding, the Demand Limiting algorithm tries to keep the Interval Demand below the Demand Limit. The correct operation of the algorithm is much harder to verify than the Load Rolling algorithm. Use this general guideline to see if the Demand Limiting algorithm produces reasonable results: 1. Set the DLLR object’s DL Mode attribute to Shedding. 2. Verify that the value of the DLLR object’s Interval Demand attribute always

stays below the value of the DLLR object’s Demand Limit attribute. 3. If Interval Demand exceeds the Demand Limit value, or when it is close to

exceeding the Demand Limit, verify that the DLLR object’s DLLR Status reads In Alarm.

4. Make sure that the DLLR object’s Demand Limit is not unreasonably low, and ensure that enough eligible loads are available to avoid exceeding the Demand Limit. Do not exceed the Demand Limit, since it may cause penalties to be paid to the utility company.

If there are severe consequences for exceeding the Demand Limit, start with a much lower Demand Limit during the first weeks or months of operation to ensure not to exceed the limit. With growing knowledge of the system’s behavior, the Demand Limit may gradually be set closer to the actual limit provided by the utility company.



Guideline (Cont.) Procedure Ensure the Demand Limiting Load Rolling Object is Working Correctly

The DLLR object’s DLLR Status attribute summarizes the overall state of the DLLR object. The value should be Normal except when it is in its registering phase. Please verify the following additional DLLR attributes for more detailed information about how the DLLR application is behaving: • Reliability • DLLR Alarm Reason • Meter Alarm • EOI Alarm • Meter Value The following attributes also provide more detailed information about how the DLLR application is doing. In some cases it takes expertise to interpret the results, but severe errors or malfunctions should be easily identifiable. • Number of Loads Eligible For DLLR • Eligible For DL Only • Eligible For LR Only • Not Eligible • Highest Load Shed Sent • Shed Accepted • Shed Refused • Shed Pending • Shed Lost • Shed Not Sent • Interval Demand • Unc Interval Demand • Demand History • Unc Demand History • Amount Shed • LR Shed • LR to Shed • LR not Shed • DL Shed • DL to Shed • DL not Shed

Fixed Window Algorithm Only • Calculation Active Limit • Active Elevation • Time Until EOI • Time Since EOI • Energy Since EOI • Demand Since EOI • Profile Limit • Max Demand



Guideline (Cont.) Procedure Ensure the Utility Profile Application is Working Correctly

The modular design of the Utility Profile makes it possible to track consumption data and peak data broken down into a variety of specific tracking periods, such as tracking periods for specific utility tariffs, days, weeks, months, or for any other reason you may want to create separate tracking records. The Utility Profile object should ideally reside either close to the Pulse Meter object or the DLLR object. Ideally Pulse Meter and DLLR objects should reside in the same device. To verify the correct operation of the Utility Profile application: 1. Check the Utility Profile object’s Meter Active attribute. It should be either

Normal if the object is currently tracking data, or it should be Suspended if it is currently not tracking data.

2. Make sure each Utility Profile object has a dedicated Pulse Meter object. The Meter Active attribute of the Pulse Meter object must always be identical to the Meter Active attribute of the Utility Profile object.

3. Check if the Pulse Meter object specified in the Utility Profile’s Meter object attribute is an online Pulse Meter object.

4. Check if any Peak Unreliable or Consump Unreliable flags are set for each Utility Profile object. Also check the Historical Data attribute for these flags. If both the Pulse Meter and the DLLR object continuously provided reliable data, there should be no indication of unreliable data in the Utility Profile object. However, some previous conditions may have left their unreliability mark in the utility profile data.

After each Utility Profile object has begun collecting, check for reasonable data for the following attributes: • Period Start Date • Period Start Time • Consumption Unc • Consump Unreliable • Peak Unreliable • Demand Peak • Demand Peak Date • Demand Peak Time • Unc Demand Peak Date • Unc Demand Peak Time • Historical Data Figures from previous utility bills as well as some common sense should be enough to determine if the results are reasonable.

Ensure the DLLR Energy Management Application is Working Correctly

Run the following test to verify the system is configured correctly. Certain tests may require modification of values to simulate conditions that would not occur under normal operations. 1. Verify all alarm messages generated by DLLR related objects are correctly

delivered to all their destinations. Invoking alarm messages may require temporary manipulation of DLLR related data.

2. Verify all schedules involved in the DLLR application schedule the correct objects at the correct times.

3. Verify all calendars are correctly tied into the DLLR application. 4. Verify there are no unbound references in the entire DLLR application. The

unbound references can be found in the Unbound References attribute of each device object involved in the DLLR application.

5. Verify each device has sufficient memory and processor bandwidth. Refer to the device object’s user manual for more information on how to verify these conditions.

N30 Supervisory Controller User’s Manual B-1

Appendix B Building a Message Router Application

Introduction The Message Router object receives all alarm messages (including alarm messages requiring a user to acknowledge them) that are generated and routes them to destinations, such as printers and workstations. It also handles rerouting messages to alternate destinations and sends all messages requiring acknowledgment to the Report Server object. Using Message Router objects to route alarms is one of two alarm routing options. The BACnet Notification Class object can also be used to route alarms. See Appendix F: Building a Notification Class Alarm Routing Application (LIT-6892360) in this manual for information on routing alarms using the BACnet Notification Class object. A Message Router object is a global object configured for each site. A primary Message Router object resides on the site manager device, and copies reside on all other controllers. The Message Router object is an internal object that is vital to the communication between objects. It works with the Report Server to ensure the delivery of messages within the system. This appendix describes aspects of the Message Router feature, including the purpose of the Message Router object, how Status Notification Reports are routed, how message filtering is configured, and how the Message Router object interacts with other objects. The Message Router and Report Server objects are internal objects of the N30 Supervisory Controller. They may be accessed using a VT100 Terminal Emulator.



For information about generating N30 databases using Project Builder, refer to the N30 Supervisory Controller Quick Start Technical Bulletin (LIT-6891200).


Key Concepts Message Router Purpose

The Message Router object controls where important dynamic system information is recorded or displayed. This information can include:

• object changes into and out of alarm

• changes offline and online by controllers or other devices

• reports from the system, such as those generated when elements of the site exceed user defined limits

This information is contained within Status Notification Reports (SNRs) that are generated by alarm objects and routed to various destinations for acknowledgment or storage.

Routing SNRs The SNRs can be routed to defined destinations such as printers and VT100s. The Message Router and Report Server internal objects (one per site) are responsible for transmitting and managing acknowledgement for the defined set of destination devices. The routing mechanism uses the priority, BACnet event state and timestamp of non-acknowledged events to provide the oldest, highest priority SNR to the acknowledging devices. The initiating alarm object provides this data. Unacknowledged messages that appear on a VT100 may be replaced without user acknowledgement if the same event for the same object occurs before the acknowledgement of the original event. For example, an analog alarm has a value of High Alarm and is displayed on a VT100. If the alarm returns to a Normal state and then again goes into a Normal state, the VT100 displays the data for the newest High Alarm event. An acknowledgement message, Acknowledged by: System, is sent to non-acknowledging devices. Non-acknowledging devices, such as printers, receive SNRs in the order of their occurrence. The Message Router feature distributes SNRs from the various sources. The Message Router examines each SNR and routes it to the appropriate destinations based on the types of SNRs each destination is configured to receive. For information about how SNRs appear on a VT100, refer to the Getting Started (LIT-6892030) chapter in this manual.


Filtering Filtering is done by each destination using the priority, category, and message type of each SNR received. Two separate filters exist for each destination: Filter A and Filter B. The filtering operation allows output of SNRs based on a match on priority, category, and message type.

Active Filter Attribute The Active Filter attribute can be set to any of the following:

• Filter A and B

• Filter A

• Filter B

• Pass All (no filtering, all SNRs output)

• Pass None (no SNRs output) The user can change the filter values to control which SNRs a destination receives based on time of day or an event (scheduling or interlocking). For example, based on the time of day, SNRs can be routed to certain destinations during normal hours and other destinations during off-hours. Another example would be to change what is routed to a destination based on some event happening in the system.

Configuring Filter Destinations Table B-1 shows priority, category, and message type for SNRs created by the N30. This information can be helpful when configuring the filter destinations in the VT100 and Printer objects.

Table B-1: Configuring Filter Destinations SNR Type Priority Category Message Type Device Online and Offline (N30 and N2 Devices)

Serious Services System Alert

Memory Overload Serious Services System Alert CPU Overload Serious Services System Alert Battery Status (Good or Bad) Serious Services System Alert Update References Serious Services System Alert Acknowledgement Status Services Operator Transaction Analog and Multistate Alarms (User Defined)

(User Defined) (User Defined) Alarm


Object Interaction Figure B-1 illustrates an example of the Message Router feature. Table B-2 describes the objects and their role in the Message Router feature.

Alarm Objects(Analog and Multisate)

Message RouterObject

Printer Objects

VT100 Objects

1

4

2

3

MR Flow

Figure B-1: Message Router Example

Table B-2: Message Router Feature Objects Number Object Role 1 Message

Router Object

Receives alarm messages and SNRs from Alarm objects, works with the Report Server object to distribute the messages throughout the system.

2 Alarm Objects

Generate alarm messages and SNRs that are routed by the Message Router object. For more information, refer to Working with Analog Alarm Objects (LIT-6892260) and Working with Multistate Alarm Objects (LIT-6892270) chapters in this document.

3 Printer Objects

Contain the filtering information to determine what alarm messages and SNRs they receive from the Message Router for printing. For more information, refer to Working with Printer Objects (LIT-6892110) chapter in this document.

4 VT100 Objects

Contain the filtering information to determine what alarm messages and SNRs they receive from the Message Router for viewing. For more information, refer to Working with VT100 Objects (LIT-6892050) chapter in this document.

N30 Supervisory Controller User’s Manual C-1

Appendix C Building an Optimal Start Application

Introduction An Optimal Start application makes it possible for users to reduce energy consumption by controlling the occupied/unoccupied mode of the building. This document provides information to consider when building a core Optimal Start application, including what objects are involved and how attributes interact.




Different objects interact in a core Optimal Start application. Figure C-1 illustrates a sample Optimal Start application. Table C-1 describes the objects and their role in an Optimal Start application.

Any Analog Attribute(Zone Temperatue)

Any Analog Attribute(Cooling Setpoint)

Optimal Start Object Any Binary Object(Warmup and Cooldown)

Any Analog Attribute(Heating Setpoint)

Any Analog Attribute(Optional)

(Outdoor AirTemperature)

Any Binary Object(Zone Occupancy)Schedule Object

1

3

4

2

5

6

7

8

OST Flow

Figure C-1: Optimal Start Application Example

Table C-1: Optimal Start Application Objects Number Object Role 1 Optimal Start Receives data from temperature points, setpoints, and a schedule object to

determine optimal start and optimal stop times. 2 Schedule Provides start and stop times for the building zone. 3 Any Binary

Object Refers to the any binary object (N2 Binary Output, Binary Value, etc.) that commands a zone to occupied or unoccupied. It is commanded by the Schedule object to occupied and by the Optimal Start to unoccupied if the Maximum Prestop attribute is enabled.

4 Any Binary Object

Refers to the object (N2 Binary Output, Binary Value, etc.) that commands a zone to warm up or cool down. It is commanded by the Optimal Start object at the optimal start time and released at the occupied time. It will not be released if the Zone WC Mode Obj and the Zone Occ Mode Obj are the same.

5-8 Any Analog Attribute

Provides any analog attributes (via N2 Analog Output objects, Analog Value objects, etc.) representing zone temperatures, cooling setpoints, and heating setpoints that are referenced by the Optimal Start object for use in calculations. If an Analog attribute reference is defined for the outside air temperature, it aids in determining if the Optimal Start object should adapt constants and deadtimes.


Attribute Involvement Building an Optimal Start application means that each object must have its attributes configured to reference the appropriate objects in order to achieve the desired results. Table C-2 lists the objects and attributes involved and guidelines for data entry.

Table C-2: Key Components for an Optimal Start Application Object Type/Function

Attributes Involved


Zone Schedule Object

Enter the exact name of the Schedule object scheduling the valid start and stop times for the Binary object controlling zone occupancy.

Zone Occ Mode Object

Enter the exact name of the Binary object controlling zone occupancy.

Zone WC Mode Object

Enter the exact name of the Binary object controlling zone warmup and cooldown. This may be the same object as the Zone Occ Mode object.

Cooling Setpoint Enter the exact object and analog attribute name representing the cooling setpoint.

Heating Setpoint Enter the exact object and analog attribute name representing the heating setpoint.

Zone Temperature Enter the exact object and attribute name representing the zone temperature.

Optimal Start

Outside Air Temperature

Enter the exact name of the attribute of the Analog object representing the outside air temperature.

Schedule List of Prop Refs Enter the name of the Binary object that controls zone occupancy.


Procedure Overview Table C-3: Building an Optimal Start Application To Do This Follow These Steps: Build an Optimal Start Application

Add N2 Controller and point objects to the database. Add the Schedule object scheduling the Binary objects controlling zone occupancy. Make sure valid start and stop times are entered into the Schedule object. Add the Optimal Start object referencing the above Schedule object, the Binary objects designated as zone occupancy and warmup/cooldown, and the analog attributes of objects designated as modes, temperatures, and setpoints.


Detailed Procedures Building an Optimal Start Application

To build an Optimal Start application: 1. Add N2 Controller and point objects to the database. See the

N30 Supervisory Controller Point Mapping Technical Bulletin (LIT-6891400) and the Project Builder User’s Guide.

2. Add the Schedule object scheduling the Binary object controlling zone occupancy. See the Working with Schedule Objects (LIT-6892070) chapter in this manual or the Adding and Editing Schedules (LIT-693235)chapter of the Project Builder User’s Guide.

3. Make sure valid start and stop times are entered into the Schedule object.

4. Add the Optimal Start object referencing the above Schedule object, the Binary objects designated as zone occupancy and warmup/cooldown, and the analog attributes of objects designated as modes, temperatures, and setpoints. See the Working with Optimal Start Objects (LIT-6892090) chapter in this manual. Or, in Project Builder software, drag the Optimal Start collection from the Devices and Collections folders in the Object Library into the Energy Container of your N30 database. With the object selected in the database, select Edit Object on the Edit menu to enter M-View. In M-View, enter your references and attributes. You can then download the new database to any N30 that should have the same Optimal Start settings.


Troubleshooting This section provides some solutions for problems in an Optimal Start application.

Table C-4: Optimal Start Troubleshooting Problems and Solutions Problem Solution Present Value of the Optimal Start Object Indicates Not Operational

The Optimal Start object’s Present Value attribute may indicate Not Operational because of errors in its connection status to other required objects. To verify the Optimal Start object’s connection status to other required objects: 1. Verify that the required Schedule object, Binary objects, and Analog objects

are all defined and online. 2. Verify that the Binary object controlling zone occupancy is in the List of Prop

Refs for the Schedule object. 3. Verify that valid start and stop times for the current day are defined in the

Schedule object. Optimal Start Object is Not Adapting Constants and Deadtimes

To ensure the Optimal Start object is adapting constants and deadtimes: 1. Verify that the Adaptation Enabled attribute indicates True. 2. Verify that the value of the Zone Temperature attribute is not within the value

of the Temperature Differential attribute (plus or minus one degree). 3. Verify that the value of the Outdoor Air Temperature attribute is within the

values of the Cooling Design Temperature and Heating Design Temperature attributes.

N30 Supervisory Controller User’s Manual D-1

Appendix D Building an Interlock Application

Introduction An Interlock application makes it possible for users to have multiple objects react to certain established, relational conditions based on data from other objects. This document provides information to consider when building a core Interlock application, including what objects are involved and how attributes interact.




Different objects interact in a core Interlock application. Figure D-1 illustrates an example of an Interlock application. Table D-1 describes the objects and their role in an Interlock application.

Source Object

Source Object Interlock Object Action Table Object

Source Object

Action Table Object

Action Table Object

1

7

6

2

3

4

5

INTL Flow

Figure D-1: Interlock Application Example

Table D-1: Interlock Application Objects Number Object Role 1 Interlock

Object References Source objects to obtain attribute data. Uses attribute data in conjunction with the Logic attribute to determine conditions. Identifies Action Table objects that will receive commands based on the conditions.

2-4 Source Objects

Provide attribute data that work with the Interlock object’s Logic attribute to determine conditions. A Source object can be any object. The number of Source objects do not need to equal the number of Action Table objects.

5-7 Action Table Objects

Receive commands based on the conditions determined by the Interlock object. An Action Table object can be any object capable of accepting commands.


Attribute Involvement Building an Interlock application means that each object must have its attributes configured to reference the appropriate objects and attributes in order to achieve the desired results. Table D-2 lists the objects and attributes involved and guidelines for data entry.

Table D-2: Key Components for an Interlock Application Object Type/Function

Attributes Involved


Source Object Name Enter the exact name of the object with the desired attribute data. Attribute Enter the exact name of the attribute containing the desired data. Relation Choose how the Attribute data must relate to the Value. Value Choose the condition if the values of the Attribute and Value meet

the established Relation. For example, if the value of the Attribute is greater than the Value, this is considered True.

Differential If the value of the Source object’s attribute is analog, enter a number that establishes a range over which the Attribute value may vary without constituting a change in value. This number determines at what point in the fluctuations of an analog value (Attribute) does the Relation become no longer True or no longer False. This prevents commands being sent based on changes in the analog value that may be too small to warrant them.

Logic Choose how the conditions must be met. If multiple Source objects are being referenced by the Interlock object, must all conditions established for all of the Source objects be met or can just one of the conditions be met in order for the command in the Action Table to be sent to the Action Table objects.

Logic Equation If the Logic attribute is set to Complex, use the Logic Equation attribute to define the relationship between the master conditions using logic operators and parentheses for determining precedence.

Action Table - True Object Name Enter the exact name of the object to receive the command based

on the condition being True. Objects do not need to be specified for both the True and False Action Table.

Delay Enter the time each command waits to be sent after the source values meet the True condition.

Command ID Choose the command to be sent to the object referenced in this Action Table. The commands available to choose from are based on the type of object being referenced in this Action Table and the access capability of the user adding the Interlock object.

Parameters Based on the command chosen various parameters may appear just as in any instance of commanding an object. Fill in the appropriate information.

Action Table - False

Object Name Enter the exact name of the object to receive the command based on the condition being False. Objects do not need to be specified for both the True and False Action Table.

Delay Enter the same information as explained in Action Table - True.

Interlock Object

Command ID Enter the same information as explained in Action Table - True.


Parameters Enter the same information as explained in Action Table - True.

Example Figures D-2 through D-5 show screens from a sample completed Interlock object. This sample object uses the Logic Equation attribute.

Figure D-2: Completed Interlock Object - Focus Screen


Figure D-3: Completed Interlock Object - Edit Screen

Figure D-4: Completed Interlock Object - Source


Figure D-5: Completed Interlock Object - Action Table - True


Procedure Overview Table D-3: Building an Interlock Application To Do This Follow These Steps: Build an Interlock Application Consider what the Interlock object needs to do and determine which

objects need to be involved. Make sure all of the objects involved in the Interlock application are added to the database. Verify/record the exact object and attribute names involved. Add the Interlock object referencing all of the required objects.


Detailed Procedures Building an Interlock Application

To build an Interlock application: 1. Consider what the Interlock object needs to do and determine

which objects need to be involved. 2. Make sure all of the objects involved in the Interlock application

are added to the database. See the appropriate chapters in this manual.

3. Verify/record the exact object and attribute names to be involved in the Interlock application.

4. Add the Interlock object referencing all of the required objects. See the Working with Interlock Objects (LIT-6892140) chapter in this manual.

N30 Supervisory Controller User’s Manual E-1

Appendix E Building a Signal Select Application

Introduction A Signal Select application makes it possible for users to process values from multiple zones to adjust various setpoints. This document provides information to consider when building a core Signal Select application, including what objects are involved and how attributes interact.




Different objects interact in a core Signal Select application. A Signal Select application involves any analog or binary attributes. Separate Signal Select objects should be created for analog versus binary data to ensure accurate and uniform data is involved in the computations. If analog and binary data combine in a Signal Select object, the Signal Select data tries to convert the data. Figure E-1 illustrates an example of an analog Signal Select application. Figure E-2 illustrates an example of a binary Signal Select application.

N2 AnalogInput Object

(Zone)


(Zone)

Signal Select Object N2 AnalogOutput Object

(Setpoint)


(Zone)

N2 AnalogOutput Object

(Setpoint)

N2 AnalogOutput Object

(Setpoint)

1

7

6

2

3

4

5

SSA Flow

Figure E-1: Analog Signal Select Example

Table E-1 describes the objects shown in Figure E-1 and their role in an analog Signal Select application.

Table E-1: Analog Signal Select Application Objects Number Object Role 1 Signal Select

Object References any object to obtain analog attribute data. Computes average, logical OR, and logical AND input values based on this data. Identifies analog attributes of any object to be updated based on the data and computation.

2-3 Analog Objects

Provide attribute data to the Signal Select object. For example, the zone temperatures of various rooms.

4-6 Analog Objects

Represent the analog objects and attributes that are updated by the Signal Select object based on computations derived from the attribute data it


receives.

N2 BinaryInput Object

(Zone)


(Zone)

Signal Select Object N2 BinaryOutput Object

(Setpoint)


(Zone)

N2 BinaryOutput Object

(Setpoint)

N2 BinaryOutput Object

(Setpoint)

1

7

6

2

3

4

5

SSB Flow

Figure E-2: Binary Signal Select Example Table E-2 describes the objects shown in Figure E-2 and their role in a binary Signal Select application.

Table E-2: Binary Signal Select Application Objects Number Object Role 1 Signal Select

Object References any object to obtain binary attribute data. Computes average, logical OR, and logical AND input values based on this data. Identifies binary attributes of any object to be updated based on the data and computation.

2-3 Binary Objects

Provide attribute data to the Signal Select object.

4-6 Binary Objects

Represent the binary objects and attributes that are updated by the Signal Select object based on computations derived from the attribute data it receives.


Attribute Involvement Building a Signal Select application means that each object must have its attributes configured to reference the appropriate objects in order to achieve the desired results. Table E-3 lists the objects and attributes involved and guidelines for data entry.

Table E-3: Key Components for a Signal Select Application Object Type/Function

Attributes Involved


Input List Enter the exact object and analog or binary attribute names used in the Signal Select computation.

Average Output Enter the exact object and analog or binary attribute names being updated to reflect the Average Output computed.

High OR Enter the exact object and analog or binary attribute names being updated to reflect the High or Logical OR Output computed. The Point Type attribute determines which computation occurs.

Low AND Enter the exact object and analog or binary attribute names being updated to reflect the Low or Logical AND Output computed. The Point Type attribute determines which computation occurs.

Signal Select Object (Analog or Binary)

Point Type Enter the point type involved in the Signal Select application: Analog or Binary.


Procedure Overview Table E-4: Building a Signal Select Application

To Do This Follow These Steps: Build a Signal Select Application

Add N2 Controller and point objects to the database. Verify/record the exact object and attribute names to be involved in the Signal Select application. Add the Signal Select objects referencing the objects with the desired analog or binary attributes.


Detailed Procedures Building a Signal Select Application

To build a Signal Select application: 1. Add N2 Controller and point objects to the database. See the

N30 Supervisory Controller Point Mapping Technical Bulletin (LIT-6891400).

2. Verify/record the exact object and attribute names to be involved in the Signal Select application.

3. Add the Signal Select objects referencing the objects with the desired analog or binary attributes. See the Working with Signal Select Objects (LIT-6892150) chapter in this manual.

N30 Supervisory Controller User’s Manual F-1

Appendix F Building a Notification Class Alarm Routing Application

Introduction Notification Class objects receive alarm messages and route them to destinations such as printers and VT100s. They also handle routing messages requiring acknowledgement to the Report Server object. Using Notification Class objects to route alarms is one of two alarm routing options. The Message Router feature can also be used to route alarms. See Appendix B: Building a Message Router Application (LIT-6892320) in this manual for information on routing alarms using the Message Router object. Only one of these two methods can be used on a site. If routing to third-party (non-Metasys) BACnet devices is required, then Notification Class objects need to be used for alarm routing. This appendix describes aspects of the Notification Class feature, including how Status Notification Reports are routed, how message filtering is configured, and how the Notification Class object interacts with other objects. For further information about the objects described in this appendix, see the Working with Notification Class Objects (LIT-6892290) chapter in this document and the relevant object chapters in the Object Dictionary. For information about generating N30 databases using Project Builder, refer to the N30 Supervisory Controller Quick Start Technical Bulletin (LIT-6891200).



Key Concepts Routing SNRs

The SNRs are routed to the destinations defined in the Recipient List of the Notification Class object. These destinations need to be configured in every Notification Class object. When adding a new destination, such as a printer, add it to the Recipient List of all Notification Class objects from which SNRs are desired. The Notification Class object determines if acknowledgement is required. (Unlike the Message Router Feature, where the Alarm object determines if acknowledgement is required). If acknowledgement is required, the SNRs are also automatically routed to the Report Server for delivery to VT100s. The Report Server and VT100 function as described in Appendix B: Building a Message Router Application (LIT-6892320) in this manual. One Notification Class object can distributes SNRs from various sources. The Notification Class object examines each SNR and routes it to the appropriate destinations based on the types of SNRs each destination is configured to receive. For information about how SNRs appear on a VT100, refer to the Getting Started (LIT-6892290) chapter in this manual.

Filtering For filtering, configure the Recipient List in the Notification Class object. Filter options include valid days, times and types of SNRs. See the Working with Notification Class Objects (LIT-6892290) chapter in this manual for details.


Default Notification Class Objects Each N30 contains three Notification Class objects by default (Table F-1). The objects, which generate SNRs, default to these Notification Class objects. However, additional Notification Class objects can be created and used to perform advanced filtering and routing.

Table F-1: Default Notification Class Objects Default Notification Class object Associated SNR

Analog and Multistate Alarms (User Defined) Alarm Notification N2 Online/Offline

Offline Notification N30 Online/Offline Memory/CPU Overload Operator Login/Logout Battery Status Update References

System Notification

Acknowledgement


Object Interaction Figure F-1 is an example of the Notification Class Alarm Routing feature. Table F-2 describes the objects and their role in the Notification Class Alarm Routing feature.

Alarm Objects(Analog and Multisate)

Notification ClassObject

Printer Objects

VT100 Objects

1

4

2

3

BNC Flow

Figure F-1: Notification Class Alarm Routing Example

Table F-2: Notification Class Alarm Routing Objects Number Object Role 1 Notification

Class Object Receives alarm messages and SNRs from Alarm objects, works with the Report Server object to distribute the messages throughout the system. Specifies priority and if acknowledgement is required.

2 Alarm Objects

Generate alarm messages and SNRs that are routed by the configured Notification Class object. For more information, refer to Working with Analog Alarm Objects (LIT-6892260) and Working with Multistate Alarm Objects (LIT-6892270) chapters in this document.

3 Printer Objects

Defined as recipients of SNRs in Notification Class objects. For more information, refer to Working with Printer Objects (LIT-6892110) chapter in this document.

4 VT100 Objects

Contain the filtering information to determine what alarm messages and SNRs they receive from the report Server for viewing. For more information, refer to Working with VT100 Objects (LIT-6892050) chapter in this document.

n30 supervisory controller user's manualcgproducts.johnsoncontrols.com/met_pdf/6892010.pdfn30...

Documents