Table of Contents
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.................................................................................................. 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
Introduction.................................................................................................. 3-1
Key Concepts............................................................................................... 3-3
N30 Task Overview .................................................................................................... 3-3
Objects ....................................................................................................................... 3-4
Johnson Controls, Inc.
www.johnsoncontrols.com
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
Table of Contents
Introduction.................................................................................................. 5-1
Key Concepts............................................................................................... 5-2
VT100 Object ............................................................................................................. 5-2
Attributes .................................................................................................................... 5-2
Introduction.................................................................................................. 6-1
Key Concepts............................................................................................... 6-2
Group Object .............................................................................................................. 6-2
Site Group .................................................................................................................. 6-2
User Group................................................................................................................. 6-3
Attributes .................................................................................................................... 6-4
Introduction.................................................................................................. 7-1
Key Concepts............................................................................................... 7-2
Schedule Object......................................................................................................... 7-2
Attributes .................................................................................................................... 7-2
Dates .......................................................................................................................... 7-4
Wildcard Date Fields .................................................................................................. 7-4
Introduction.................................................................................................. 8-1
Key Concepts............................................................................................... 8-2
Calendar Object ......................................................................................................... 8-2
Attributes .................................................................................................................... 8-2
Wildcard Date Fields .................................................................................................. 8-3
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
Table of Contents
Introduction................................................................................................ 10-1
Key Concepts............................................................................................. 10-2
Temporary Occupancy Object Operation................................................................. 10-2
Attributes .................................................................................................................. 10-2
Introduction................................................................................................ 11-1
Key Concepts............................................................................................. 11-2
Printer Object ........................................................................................................... 11-2
Attributes .................................................................................................................. 11-2
Introduction................................................................................................ 12-1
Key Concepts............................................................................................. 12-2
Modem Configuration Object.................................................................................... 12-2
Attributes .................................................................................................................. 12-2
Introduction................................................................................................ 13-1
Introduction................................................................................................ 14-1
Key Concepts............................................................................................. 14-2
Interlock Object ........................................................................................................ 14-2
Attributes .................................................................................................................. 14-2
Example ................................................................................................................... 14-4
Introduction................................................................................................ 15-1
Key Concepts............................................................................................. 15-2
Signal Select ............................................................................................................ 15-2
Analog Signal Select ................................................................................................ 15-2
Binary Signal Select ................................................................................................. 15-2
Attributes .................................................................................................................. 15-3
Table of Contents
Introduction................................................................................................ 17-1
Key Concepts............................................................................................. 17-2
Multiple Command Object ........................................................................................ 17-2
Attributes .................................................................................................................. 17-2
Introduction................................................................................................ 18-1
Key Concepts............................................................................................. 18-2
Data Broadcast Object ............................................................................................. 18-2
Unconfirmed COV Notification ................................................................................. 18-2
Attributes .................................................................................................................. 18-2
Chapter 19
Introduction................................................................................................ 19-1
Key Concepts............................................................................................. 19-2
Demand Limiting/Load Rolling Controller Object ..................................................... 19-2
Shedding .................................................................................................................. 19-2
Introduction................................................................................................ 20-1
Key Concepts............................................................................................. 20-2
Load Object.............................................................................................................. 20-2
Shedding .................................................................................................................. 20-2
Releasing ................................................................................................................. 20-2
Attributes .................................................................................................................. 20-2
Introduction................................................................................................ 21-1
Key Concepts............................................................................................. 21-2
Pulse Meter Object................................................................................................... 21-2
Attributes .................................................................................................................. 21-2
Introduction................................................................................................ 22-1
Table of Contents
Introduction................................................................................................ 23-1
Key Concepts............................................................................................. 23-2
Analog Totalization Object ....................................................................................... 23-2
Analog Totalization Object Reset............................................................................. 23-3
Attributes .................................................................................................................. 23-3
Introduction................................................................................................ 24-1
Key Concepts............................................................................................. 24-2
Event Totalization Object ......................................................................................... 24-2
Event Totalization Object Reset ............................................................................... 24-3
Attributes .................................................................................................................. 24-3
10
Introduction................................................................................................ 25-1
Key Concepts............................................................................................. 25-2
Runtime Totalization Object ..................................................................................... 25-2
Runtime Totalization Object Reset........................................................................... 25-3
Attributes .................................................................................................................. 25-3
Introduction................................................................................................ 26-1
Key Concepts............................................................................................. 26-2
Analog Alarm Object ................................................................................................ 26-2
States ....................................................................................................................... 26-2
SNR.......................................................................................................................... 26-2
Attributes .................................................................................................................. 26-3
Introduction................................................................................................ 27-1
Key Concepts............................................................................................. 27-2
Multistate Alarm Object ............................................................................................ 27-2
States ....................................................................................................................... 27-2
SNR.......................................................................................................................... 27-2
Attributes .................................................................................................................. 27-2
Table of Contents
11
Introduction................................................................................................ 28-1
Key Concepts............................................................................................. 28-2
Trend Log Object ..................................................................................................... 28-2
Attributes .................................................................................................................. 28-2
Introduction................................................................................................ 29-1
Key Concepts............................................................................................. 29-3
Notification Class ..................................................................................................... 29-3
Destinations ............................................................................................................. 29-3
Attributes .................................................................................................................. 29-4
Introduction................................................................................................ 30-1
Key Concepts............................................................................................. 30-2
Remote Destination Object Operation...................................................................... 30-2
Attributes .................................................................................................................. 30-2
12
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
Introduction................................................................................................ 32-1
Key Concepts............................................................................................. 32-2
Pager Object Operation ........................................................................................... 32-2
Attributes .................................................................................................................. 32-3
Introduction................................................................................................ 33-1
Key Concepts............................................................................................. 33-2
BACnet Group Object vs Johnson Controls Proprietary Group Object .................... 33-2
Attributes .................................................................................................................. 33-2
Table of Contents
13
Introduction................................................................................................ 34-1
Key Concepts............................................................................................. 34-2
Event Enrollment Object........................................................................................... 34-2
Attributes .................................................................................................................. 34-2
Introduction..................................................................................................A-1
Key Concepts...............................................................................................A-2
Object Interaction .......................................................................................................A-2
Attribute Involvement..................................................................................................A-4
Advanced Object Functions .......................................................................................A-5
Troubleshooting ..........................................................................................A-8
Appendix B
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
Introduction..................................................................................................C-1
Key Concepts...............................................................................................C-2
14
Troubleshooting ..........................................................................................C-6
Appendix D
Introduction..................................................................................................D-1
Key Concepts...............................................................................................D-2
Object Interaction ...................................................................................................... D-2
Attribute Involvement................................................................................................. D-3
Example .................................................................................................................... D-4
Introduction.................................................................................................. E-1
Key Concepts............................................................................................... E-2
Object Interaction .......................................................................................................E-2
Attribute Involvement..................................................................................................E-4
1-1
Chapter 1
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:
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:
www.johnsoncontrols.com
Software Release 5.0
1-2
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.
1-3
Chapter Organization
Each chapter in the N30 Supervisory Controller Users Manual can be
divided into the main sections identified in Table 1-1.
Table 1-1: Chapter Organization
Section
Description
Introduction
Key Concepts
Procedure Overview
Detailed Procedures
1-4
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
LIT-6891100
LIT-6891300
LIT-6891400
LIT-6891200
Technical Information
How to Install an N30
M-Tool
Project Builder
Communications
How to Use Site Book and
Setup Ethernet
Communications with an
N30
LIT-6893350
LIT-6893400
LIT-6893450
Objects
Reference to All Objects
and their Attributes
Object Dictionary
2-1
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
www.johnsoncontrols.com
Software Release 5.0
2-2
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:
BAS Components
A typical BAS configuration consists of the components listed below
and illustrated in Figure 2-1 and Figure 2-2.
serial printer
2-3
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
LCP-xxx
All
MIG
3.0 or later
Metasys Integrator
UNT
B03 or later
Unitary Controller
VAV
A03 or later
AHU
C03 or later
PHX
All
VMA1400
All
All
ILC**
All
IFC-1010/2020
All
* 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).
2-4
M-Series Workstation
or PC with VT100 Emulator
VT100
or
VMA
VAV
N2
esc
Serial
Printer
DX
UNT
AHU
N30 BAS
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.
2-5
M-Tool
M-Tool contains the System Tools and the Configuration Tools. The
Project Builder component of System Tools includes the ability to:
M-Series Workstation
Ethernet
esc
N30
VT100
N2
N2
UNT
DX
VMA
VMA
DX
UNT
network n30
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.
2-6
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.
3-1
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
command objects
display a summary
print a summary
change an IP address
rebind a site
www.johnsoncontrols.com
Software Release 5.0
3-2
Note:
3-3
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:
Define Schedules.
See the chapters in this manual
on Schedule objects and
Calendar objects.
Print Controller
Configurations.
See the N30 Supervisory
Controller Point Mapping
Technical Bulletin
(LIT-6891400).
Define Groups.
See Working with Group
Objects chapter in this manual.
3-4
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 N30s Flash
memory stores configuration data, startup code, boot code, main code,
and the archive database within this memory.
3-5
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.
2.
3.
4.
5.
User must Rebind Site in order for the Interlock object in N30-A
to reestablish its reference to Outdoor Air.
3-6
Analog Alarm*
Multistate Alarm*
Analog Totalization*
Runtime Totalization*
Event Totalization*
Trend Log*
Container
Data Broadcast*
Internals
Site
Report Server
Also, all objects that can be added from the site name
Comm
Applications
Energy
Optimal Start*
Heavy Equip Contr
Pulse Meter*
Load*
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
Notifications
Notification*
Also, all objects that can be added from the site name
Operator Devices
Operators
Operator*
Also, all objects that can be added from the site name
Programming
Multiple Command
Interlock*
Global Data*
Signal Select*
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
3-7
* Detailed procedures for working with these objects are in this manual. For all other objects, refer to the
Object Dictionary for further information.
3-8
3-9
Alarm Information
Note:
Refer to Appendix B:
Building a Message
Router Application
(LIT-6892320) for
more information about
SNRs.
Site/User Information
User Workspace
User Assistance
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 Users 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.
3-10
3-11
Function
Context
Purpose
] or [
Page
Arrow Keys
Move cursor or
highlight fields
Delete
Delete
An object is open or an
empty container is open.
F1
Ack
F2
Command
An object is selected.
Del (Delete)
Item
Add
Edit
Save
Add Item
Back
Cancel
An object, container, or
attribute screen is open.
Quit
Return (Enter)
Execute
Open
An object, container, or
device is selected.
Select
Spacebar
Expand/
Collapse
Spacebar
(forward) and
Backspace key
(backward)
Cycle
Tab
Confirm Delete
Move to next
field
F3
F4
3-12
Procedure Overview
Table 3-4: Getting Started
To Do This
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.
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.
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.
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.
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.
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
Print a Summary
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.
3-13
To Do This (Cont.)
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.
3-14
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:
Logging On to an N30
To log on to an N30:
1.
2.
Press Enter when the N30 name appears at the top of the screen.
The Login screen appears (Figure 3-3).
3.
4.
Type your password and press Enter. The Main N30 screen
appears (Figure 3-4).
Notes:
3-15
Browse to and highlight the N30 you want to check (for example,
B7F3N01 in Figure 3-5).
3-16
Press Enter. The local attributes screen appears (Figure 3-6). The
firmware version level is on the right side under engineering
values.
3-17
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.
From the Main screen (Figure 3-4), use the arrow keys to
highlight an N30 (for example, N30P497).
2.
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.
3-18
From the Main screen (Figure 3-4), use the arrow keys to
highlight an N30.
2.
3.
Press the F3 (Edit) key. The first of two N30 Device object
attribute screens appears (Figure 3-8).
3-19
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.
3-20
From the Main screen (Figure 3-4), use the arrow keys to
highlight an N30.
2.
Note:
4.
5.
Use the arrow key to highlight the Controller object where the
N2 object is located. In this example, it is UNT {1}.
6.
3-21
8.
3-22
2.
3.
4.
Press the F3 (Add) key. A list of objects that can be added at that
point appears (Figure 3-12).
Note:
3-23
5.
6.
Press Enter. The attribute screen for the selected object appears.
7.
8.
2.
Note:
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.
Note:
6.
3-24
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.
2.
3-25
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.
5.
Press Enter.
Displaying a Summary
To display a summary:
1.
2.
3.
Highlight a Summary.
4.
5.
Use the Spacebar and Backspace keys to cycle through the list
until the Display command appears (Figure 3-15).
3-26
3-27
Printing a Summary
To print a summary:
1.
2.
3.
Highlight a Summary.
4.
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.
3-28
Changing an IP Address
Notes:
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.
5.
3-29
6.
7.
8.
9.
3-30
Rebinding a Site
To rebind a site:
1.
2.
3.
4.
Use the Spacebar and Backspace key to cycle through the list until
Rebind Site appears.
5.
Press Enter.
2.
3.
4.
Use the arrow keys or Tab key to highlight the Name field.
5.
6.
7.
2.
3.
Use the Spacebar and Backspace key to cycle through the list until
Archive appears.
4.
Press Enter.
4-1
Chapter 4
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:
www.johnsoncontrols.com
Software Release 5.0
4-2
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 Guards Operator object allows the viewing of Security
objects, whereas the Building Managers 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 administrators 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.
4-3
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.
2.
4-4
3.
Minimize the chance of users losing their ability to log into a site
due to a single N30 device breakdown.
4-5
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.
Only the user intended to have access to these objects should be granted
any level of access to these categories.
When the user logs into a VT100 equipped N30 device, the users Login ID and
Password entries are compared against those defined in each of the sites
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 sites 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)
4-6
Guideline (Cont.)
Description
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.
4-7
Site
Manager
N30
VT 100
Standalone N30 Configuration
Copy
Holder
Site
Manager
N30
N30
N30
VT 100
Multiple N30 Configuration with Single VT100 Monitor
Copy
Holder
Site
Manager
N30
VT 100
N30
N30
VT 100
Multiple N30 Configuration with Two VT100 Monitors
Site
Manager
N30
VT 100
N30
VT 100
Copy
Holder
N30
VT 100
4-8
Attributes
The values of an objects 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.
4-9
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 users relative degree of access, such as Configure,
Modify, etc., for each of the sites 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
Fire
Security
Services
Administrative
4-10
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
Modify
Supervise
Intervene
Operate
View
No Access
Can see the object listed on the browser but not the details.
The Login ID entry was kept short by using just the users first
name and the initial of the last name. To ensure clarity, the users
full name was entered in the Description field.
The User Group reference tailors the user interface to the users
specific needs. For more information, refer to Working with
Groups (LIT-6892060) in this manual.
4-11
4-12
Procedure Overview
Table 4-4: Working with Operator Objects
To Do This
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.
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.
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.
4-13
Detailed Procedures
Adding an Operator Object
Note:
The Administrator of the site is the only user who can add an
Operator object.
2.
3.
4-14
Attribute
Required
Default
Options/Range
Object
Object Name
No
Blank
Description
No
Blank
Maximum 40 characters
Object Type
Yes
Operator
Object Category
Yes
Administrative
All other
Operator objects
have the default
HVAC.
Enabled
Yes
True
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
Capability
User Group
No
Blank
Maximum 32 characters
Timeout
No
60
Minimum value = 1
Maximum value = 1440
Units = minutes
Acknowledge
No
True
Display Units
Yes
Imperial Units
Imperial Units
SI Can Units
SI Eur Units
HVAC
Yes
Operate
Fire
Yes
No Access
Security
Yes
No Access
Services
Yes
No Access
5.
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.
8.
4-15
The Administrator of the site is the only user who can edit an
Operator object.
2.
3.
4.
5.
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.
8.
2.
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.
Description
Enable
Allows the user to log on and access the site according to the
user access levels defined by the Operator object.
Disable
4.
Press Enter.
4-16
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.
3.
4.
5.
Use the Spacebar and the Backspace key to cycle through the list
until Change Password appears.
6.
Note:
Pressing the Tab or down arrow key also moves the cursor to
the next field.
7.
8.
9.
Log on to the N30 using the ADMIN login ID and password. This
is the only way the Change Password command is available.
2.
3.
Highlight the Operator object named site name. Operator {1}. For
example, BROWN DEER. Operator {1} (Figure 4-4).
4-17
5.
6.
Note:
Pressing the Tab or down arrow key also moves the cursor to
the next field.
7.
8.
9.
The Administrator of the site is the only user who can delete
an Operator object
2.
3.
4.
5-1
Chapter 5
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.
www.johnsoncontrols.com
Software Release 5.0
5-2
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.
Attributes
The values of an objects 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.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input,
or VT100.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
5-3
Active Filter
Selects the type of filtering in effect for this VT100 destination. The
filter types are as follows:
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.
5-4
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.
5-5
Procedure Overview
Table 5-1: Working with VT100 Objects
To Do This
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.
5-6
Detailed Procedures
Editing a VT100 Object
To edit a VT100 object:
1.
2.
Note:
3.
Press the F3 (Edit) key. The VT100 object attribute screen appears
(Figure 5-1).
5-7
Attribute
Required
Default
Options/Range
Object
Object Name
No
Blank
Description
No
Blank
Maximum 40 characters
Object Type
Yes
VT100
Object
Category
Yes
HVAC
Active Filter
Yes
Pass All
Priority
Filter A
Yes
[4] Items
Category
Filter A
Yes
[5] Items
Msg Type
Filter A
Yes
[3] Items
Priority
Filter B
Yes
[4] Items
Category
Filter B
Yes
[5] Items
Msg Type
Filter B
Yes
[3] Items
Alarm
Setup
Notification
Class
Port
Setup
Port Number
Yes
Port 1
5.
6.
7.
Use the Spacebar and Backspace key to view and select True or
False for the first available option.
8.
9.
Repeat Steps 7 and 8 until values are chosen for all of the options.
5-8
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.
14. Press any key to continue.
15. Press the F4 (Cancel) key to return to the container hierarchy.
6-1
Chapter 6
Introduction
The Group object provides the user with the ability to customize the
organization of objects within the site.
This chapter describes how to:
www.johnsoncontrols.com
Software Release 5.0
6-2
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.
6-3
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 users 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
Managers 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.
6-4
Attributes
The values of an objects 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.
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
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 objects
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.
6-5
Procedure Overview
Table 6-1: Working with Group Objects
To Do This
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.
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.
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.
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.
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.
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.
6-6
Detailed Procedures
Adding a Group Object
Note:
2.
3.
6-7
Attribute
Default
Options/Range
Object
Object Name
Required
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
Child List
Yes
0 Items
5.
6.
Press Enter. The Group object Child List appears (Figure 6-4).
8.
Note:
9.
6-8
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
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.
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.
1.
2.
3.
Press the F3 (Edit) key. The Group object attribute screen appears
(Figure 6-3).
4.
5.
6.
7.
Press Enter. The Group object Child List appears (Figure 6-4).
8.
9.
6-9
2.
3.
Press the F3 (Edit) key. The Group object attribute screen appears
(Figure 6-3).
4.
5.
Press Enter. The Group object Child List appears (Figure 6-4).
6.
7.
8.
Note:
9.
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
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.
14. Press any key to continue.
15. Press the F4 (Cancel) key to return to the container hierarchy.
2.
3.
4.
5.
Press Enter. The Group object Child List appears (Figure 6-4).
6.
7.
6-10
8.
9.
10. 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 11.
11. Press any key to continue.
12. Press the F4 (Cancel) key to return to the container hierarchy.
2.
3.
4.
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.
8.
9.
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 10.
6-11
In the Group container, add a Group object with the desired Child
List members.
Note:
2.
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.
5.
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.
8.
9.
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).
6-12
In the Group container, add a Group object with the desired Child
List members.
Note:
2.
3.
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
Log out and log in the VT100 with the appropriate Login ID and
Password for the edited Operator object.
5.
7-1
Chapter 7
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:
www.johnsoncontrols.com
Software Release 5.0
7-2
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 objects 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.
Description
Provides optional information to further describe the object.
Object Type
Indicates the type of object, such as Schedule, N2 Analog Input, or
Calendar.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
7-3
7-4
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.
Meaning
Day of Month
Month
Every month
Year
Every year
Day of Week
Table 7-2 shows some sample wildcard dates and their meanings.
Table 7-2: Sample Wildcard Dates
Wildcard Date
Meaning
01
12
Apr
Apr
1999
Every day
Monday
Every Monday
1999
Monday
Apr
1999
Monday
12
Apr
1999
7-5
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
1999
Wednesday
1999
Friday
Jun
1999
Wednesday
Aug
1999
Friday
Jun
1999
Any day of
the week
Aug
1999
30
Aug
1999
Any day of
the week
10
Any day of
the week
12
04
Jul
Monday
04
Jul
Friday
7-6
Day of Week
Meaning
Any
Any week of
month
Any
Days 1-7
Monday
Jan
Any week of
month
Tuesday
Feb
Days 8-14
Any
Any week of
month
Wednesday
Mar
Any week of
month
Any
Days 14-21
Apr
Days 22-28
Thursday
Any
Days 29-31
Jun
Saturday
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.
7-7
Procedure Overview
Table 7-5: Working with Schedule Objects
To Do This:
7-8
To Do This (Cont.)
Commanding a Schedule
Object
7-9
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.
2.
3.
7-10
Attribute
Required
Default
Options/ Range
Object
Object Name
No
Blank
Maximum 32 characters
Invalid characters: @ . ? * $ # : [ ]
If not completed, the system assigns a
name.
Scheduling
Values
Description
No
Blank
Maximum 40 characters
Object Type
Yes
Calendar
Object
Category
Yes
HVAC
Enabled
Yes
True
List of Prop
Refs
Yes
[0] Items
Weekly
Schedule
Yes
[7] Items
Exception
Schedule
Yes
[0] Items
Effective
Period
Yes
[2] Items
5.
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.
8.
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.
7-11
2.
3.
4.
5.
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.
7-12
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
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.
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.
7-13
2.
3.
4.
5.
Use the Spacebar and Backspace keys to cycle through and select
the day of the week for the schedule entry.
7.
8.
Add the time/value pair in the fields displayed. Press the Tab key
to move between the Time and Value fields.
9.
7-14
12. 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 13.
13. Press any key to continue.
14. Press the F4 (Back) key to return to the container hierarchy.
Adding an Exception Schedule
To add an Exception Schedule:
1.
2.
3.
4.
5.
Press the Add Item (F3) key. The Exception Schedule screen
appears.
7.
7-15
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.
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.
2.
3.
4.
5.
7-16
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.
8.
9.
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 10.
7-17
2.
3.
4.
5.
6.
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.
7-18
2.
3.
4.
5.
6.
7.
8.
9.
2.
3.
4.
5.
7-19
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.
9.
Press the F3 (Add) key to add Time and Value pairs to the weekly
schedule.
7-20
2.
3.
4.
5.
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.
9.
7-21
2.
3.
4.
5.
6.
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.
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
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 15.
15. Press any key to continue.
16. Press the F4 (Cancel) key to return to the container hierarchy.
7-22
2.
3.
4.
5.
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.
8.
9.
7-23
12. 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 13.
13. Press any key to continue.
14. Press the F4 (Cancel) key to return to the container hierarchy.
2.
3.
Description
Enable
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.
2.
3.
4.
5.
6.
Use the Spacebar or the Backspace key to select the day of the
week that contains the schedule you want to change.
7-24
7.
8.
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.
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
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 13.
13. Press any key to continue.
14. Press the F4 (Cancel) key to return to the container hierarchy.
Deleting an Exception Schedule
To delete an Exception Schedule:
1.
2.
3.
4.
5.
6.
Use the Spacebar and Tab keys to cycle to the Exception Schedule
you want to delete.
7.
8.
9.
2.
3.
4.
7-25
8-1
Chapter 8
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:
www.johnsoncontrols.com
Software Release 5.0
8-2
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Calendar.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
8-3
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.
Meaning
Day of Month
Month
Every month
Year
Every year
Day of Week
Table 8-2 shows some sample wildcard dates and their meanings.
8-4
Meaning
01
12
Apr
Apr
1999
Every day
Monday
Every Monday
1999
Monday
Apr
1999
Monday
12
Apr
1999
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
1999
Wednesday
1999
Friday
Jun
1999
Wednesday
Aug
1999
Friday
Jun
1999
Any day of
week
Aug
1999
Any
day of
week
30
Aug
1999
Any day of
week
Any
day of
week
10
Any day of
week
12
Any
day of
week
04
Jul
Monday
04
Jul
Friday
8-5
Day of Week
Meaning
Any
Any week of
month
Any
Days 1-7
Monday
Jan
Any week of
month
Tuesday
Feb
Days 8-14
Any
Any week of
month
Wednesday
Mar
Any week of
month
Any
Days 14-21
Apr
Days 22-28
Thursday
Any
Days 29-31
Jun
Saturday
8-6
Procedure Overview
Table 8-5: Working with Calendar Objects
To Do This
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.
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.
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.
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.
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.
8-7
Detailed Procedures
Adding a Calendar Object
To add a Calendar object:
1.
2.
3.
8-8
Attribute
Required
Default
Options/ Range
Object
Object Name
No
Blank
Maximum 32 characters
Invalid characters: @ . ? * $ # : [ ]
If not completed, the system assigns a
name.
Engineering
Values
Description
No
Blank
Maximum 40 characters
Object Type
Yes
Calendar
Object
Category
Yes
HVAC
Enabled
Yes
True
Date List
Yes
[0] Items
5.
6.
Press Enter.
7.
Press the F3 (Add Item) key. The Calendar object Date List
appears (Figure 8-2).
8-9
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.
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
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.
14. Press any key to continue.
15. Press the F4 (Cancel) key to return to the container hierarchy.
1.
2.
3.
4.
5.
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.
8.
2.
3.
8-10
4.
5.
Press Enter. The Calendar object Date List appears (Figure 8-2).
6.
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.
9.
2.
3.
4.
5.
Press Enter. The Calendar object Date List appears (Figure 8-2).
6.
7.
8.
Repeat Steps 6 and 7 for each entry to be removed from the list.
9.
8-11
2.
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.
Description
Enable
Compares the current day with the entries within the calendar
and reevaluates the Present Value based on the results.
Disable
4.
Press Enter.
2.
3.
4.
9-1
Chapter 9
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:
www.johnsoncontrols.com
Software Release 5.0
9-2
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:
Description
Heating or Cooling
Constant
Temperature
Differential
Deadtime
9-3
Deadtime = 5 minutes
Therefore:
= 0.1 * (15)2 + 5
= 0.1 * 225 + 5
= 22.5 + 5
= 27.5
= 28 minutes
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.
9-4
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
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.
9-5
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.
9-6
9-7
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:
Temperature Differential
9-8
Heating Deadtime
Lists the time required after startup to raise the temperature by one
degree. The Optimal Start objects 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 objects
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:
Occupied
9-9
Procedure Overview
Table 9-2: Working with Optimal Start Objects
To Do This
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.
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.
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.
9-10
Detailed Procedures
Adding an Optimal Start Object
To add an Optimal Start object:
1.
2.
3.
Highlight Optimal Start and press Enter. The first of two Optimal
Start object attribute screens appears (Figure 9-1).
Note:
9-11
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
Optimal Start
Object
Category
Yes
HVAC
OST Type
Yes
Heating/Cooling
Enabled
Yes
True
9-12
Screen
Area
(Cont.)
Attribute
Required
Default
Options/Range
Control
Adaptation
Enabled
Yes
True
Zone Schedule
Object
Yes
Blank
Zone Occ
Mode Object
Yes
Blank
Zone WC
Mode Object
Yes
Blank
Cooling
Setpoint
Yes (unless
Heating
Only)
Blank
Heating
Setpoint
Yes (unless
Cooling
Only)
Blank
Zone
Temperature
Yes
Blank
Outdoor Air
Temp
No
Blank
Cooling Design
Temp
Yes
95.0 deg F or
35.0 deg C
Heating
Design Temp
Yes
-5.0 deg F or
-20.0 deg C
Min Prestart
Time
Yes
20 minute
Minimum Value = 0
Maximum Value = 240
Units = Minutes
Max Prestart
Time
Yes
120 minute
Minimum Value = 5
Maximum Value = 480
Units = Minutes
Max Prestop
Time
Yes
0 minute
Minimum Value = 0
Maximum Value = 60
Units = Minutes
Display
Precision
Yes
10ths
Cooling
Constant
Yes
5.0
Minimum Value = 1
Maximum Value = 999
Cooling
Deadtime
Yes
10 minute
Minimum Value = 5
Maximum Value = 480
Units = Minutes
Heating
Constant
Yes
10.0
Minimum Value = 1
Maximum Value = 999
Heating
Deadtime
Yes
10 minute
Minimum Value = 5
Maximum Value = 480
Units = Minutes
Setup
9-13
5.
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.
8.
2.
Note:
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:
4.
5.
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.
8.
2.
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.
9-14
Description
Cancel Prestart
Cancel Prestop
Enable
Disable
4.
Press Enter.
2.
3.
4.
10-1
Chapter 10
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:
www.johnsoncontrols.com
Software Release 5.0
10-2
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 objects
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.
10-3
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.
10-4
Procedure Overview
Table 10-1: Working with Temporary Occupancy Objects
To Do This
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.
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
Delete a Temporary
Occupancy Object
10-5
Detailed Procedures
Adding a Temporary Occupancy Object
To add a Temporary Occupancy object:
1.
2.
3.
4.
Attribute
Name
Required
Default Value
Options/Range
Engineering
Values
Occupancy
Time
Yes
Output
Object
Yes
Null
Output
Value
Yes
10-6
6.
7.
8.
2.
3.
4.
5.
6.
7.
2.
3.
4.
2.
3.
4.
11-1
Chapter 11
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:
www.johnsoncontrols.com
Software Release 5.0
11-2
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:
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Analog Alarm.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
11-3
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:
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.
11-4
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 printers 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.
11-5
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 cant 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.
11-6
Procedure Overview
Table 11-1: Working with Printer Objects
To Do This
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.
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.
11-7
Detailed Procedures
Adding a Printer Object
To add a Printer object:
1.
2.
3.
Highlight Printer and press Enter. The first of two Printer object
attribute screens appears (Figure 11-1).
Note:
11-8
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
Printer
Object
Category
Yes
HVAC
Port Setup
Port Number
Yes
Port 2
Setup
Active Filter
Yes
Pass All
Priority
Filter A
Yes
[4] Items
Category
Filter A
Yes
[5] Items
Msg Type
Filter A
Yes
[3] Items
11-9
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Setup (Cont.)
Priority
Filter B
Yes
[4] Items
Category
Filter B
Yes
[5] Items
Msg Type
Filter B
Yes
[3] Items
Alt SNR
Destination
No
Blank
Page Size
No
Blank
SNR
Delimiter
Yes
False
Interleave
Yes
False
Max SNR
Queue
Yes
25
3-100
Xoff Delay
Time
Yes
20
0-65535 seconds
Process
Identifier
No
Use Dial
Yes
False
Phone
Number
No
Blank
Modem
Config
Object
No
Blank
SNR Dial
Out Level
Yes
80 %
35-100 percent
Retry
Interval
Yes
180
60-600 seconds
Retries
Yes
0-10
Hang Up
Wait Time
Yes
0-65535 seconds
Dial Setup
3-15
5.
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.
8.
11-10
2.
3.
Press the F3 (Edit) key. The Printer object attribute screen appears
(Figure 11-1 and Figure 11-2).
4.
5.
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.
8.
2.
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.
Description
Form Feed
Queue Clear
Cancel Print
Dial
Forces a dial out when the Error State is Dial Out Failed.
4.
Press Enter.
2.
3.
4.
12-1
Chapter 12
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:
www.johnsoncontrols.com
Software Release 5.0
12-2
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Modem Config.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
12-3
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.
12-4
Procedure Overview
Table 12-1: Working with Modem Configuration Objects
To Do This
Detailed Procedures
Adding a Modem Configuration Object
To add a Modem Configuration object:
1.
2.
3.
12-5
12-6
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
Modem
Config
Object
Category
Yes
HVAC
Enabled
Yes
True
Dial Mode
Yes
Tone
Connect
Timeout
Yes
45
Seconds
Number of
Redials
Yes
0-6
Modem Init
String
Yes
Blank
Setup
5.
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.
8.
12-7
2.
3.
4.
5.
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.
8.
2.
3.
4.
13-1
Chapter 13
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:
www.johnsoncontrols.com
Software Release 5.0
13-2
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Global Data.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
13-3
Procedure Overview
Table 13-1: Working with Global Data Sharing Objects
To Do This
13-4
Detailed Procedures
Adding a Global Data Sharing Object
To add a Global Data Sharing object:
1.
2.
3.
Highlight Global Data and press Enter. The Global Data Sharing
attribute screen appears (Figure 13-1).
13-5
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
Global Data
Object
Category
Yes
HVAC
Enabled
Yes
True
Master
Yes
Blank
Slaves List
Yes
0 items
Engineering
Values
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.
6.
Press Enter. The Global Data Sharing object Slaves List appears
(Figure 13-2).
13-6
8.
9.
Repeat Steps 7 through 8 for all slaves being added to the list.
13-7
1.
2.
Note:
3.
Press the F3 (Edit) key. The Global Data Sharing object attribute
screen appears (Figure 13-1).
4.
5.
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.
8.
2.
3.
Press the F3 (Edit) key. The Global Data Sharing object attribute
screen appears (Figure 13-1).
4.
5.
Press Enter. The Global Data Sharing object Slaves List appears
(Figure 13-2).
6.
7.
8.
9.
13-8
correct them and resave the entries. Once the save is successful,
continue with Step 12.
12. Press any key to continue.
13. Press the F4 (Cancel) key to return to the container hierarchy.
2.
3.
Press the F3 (Edit) key. The Global Data Sharing object attribute
screen appears (Figure 13-1).
4.
5.
Press Enter. The Global Data Sharing object Slaves List appears
(Figure 13-2).
6.
7.
8.
Repeat Steps 6 and 7 for each slave to be removed from the list.
9.
2.
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.
Description
Enable
Disable
4.
Press Enter.
2.
3.
4.
13-9
14-1
Chapter 14
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:
www.johnsoncontrols.com
Software Release 5.0
14-2
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Interlock.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
14-3
Enabled
Indicates if the object is active and executing an operational condition.
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
Attribute
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
Logic
Specifies the Boolean (AND/OR) logic used in combination with the
Source input to deliver a True or False statement. Options include:
14-4
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
Numbers
Spaces
Example
Figures 14-1 through 14-4 show screens from a sample completed
Interlock object. This sample object uses the Logic Equation attribute.
14-5
14-6
14-7
Procedure Overview
Table 14-3: Working with Interlock Objects
To Do This
14-8
To Do This (Cont.)
14-9
Detailed Procedures
Adding an Interlock Object
To add an Interlock object:
1.
2.
3.
14-10
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
Interlock
Object
Category
Yes
HVAC
Enabled
Yes
True
Engineering
Values
Commands
Priority
Yes
Default
Display
States Text
Yes
False True
Interlock
Definition
Source
Yes
0 items
Logic
Yes
Match All
Logic
Equation
No
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)
Action Table
5.
6.
8.
9.
Use the Spacebar and Backspace key to cycle through the list until
the desired option appears.
14-12
14-14
1.
2.
Note:
3.
4.
5.
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.
8.
2.
3.
4.
5.
6.
7.
8.
9.
Use the Spacebar and Backspace key to cycle through the list until
the desired option appears.
2.
3.
4.
5.
6.
7.
8.
9.
2.
3.
4.
14-16
5.
6.
7.
8.
9.
2.
3.
4.
5.
6.
7.
8.
9.
2.
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.
Description
Re-Command
Override
Override Release
Release
Release All
Enable
Disable
4.
5.
Press Enter.
2.
3.
4.
15-1
Chapter 15
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:
www.johnsoncontrols.com
Software Release 5.0
15-2
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:
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.
15-3
Description
Average Output
Computation
Logical OR
Computation
Logical AND
Computation
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Signal Select.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
15-4
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.
15-5
Procedure Overview
Table 15-2: Working with Signal Select Objects
To Do This
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.
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.
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.
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.
15-6
Detailed Procedures
Adding a Signal Select Object
To add a Signal Select object:
1.
2.
3.
Highlight Signal Select and press Enter. The Signal Select object
attribute screen appears (Figure 15-1).
15-7
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
Signal
Select
Object
Category
Yes
HVAC
Enabled
Yes
True
Input List
Yes
Average
Output
No
Blank
High OR
No
Blank
Low AND
No
Blank
Point Type
Yes
Analog
Engineering
Values
5.
6.
15-8
8.
9.
1.
2.
Note:
15-9
3.
Press the F3 (Edit) key. The Signal Select object attribute screen
appears (Figure 15-1).
4.
5.
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.
8.
2.
3.
Press the F3 (Edit) key. The Signal Select object attribute screen
appears (Figure 15-1).
4.
5.
6.
7.
8.
9.
15-10
2.
3.
Press the F3 (Edit) key. The Signal Select object attribute screen
appears (Figure 15-1).
4.
5.
6.
7.
8.
Repeat Steps 6 and 7 for each input to be removed from the list.
9.
2.
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.
Description
Enable
Disable
Locks out all outputs and prevents the Signal Select functionality.
4.
Press Enter.
2.
3.
4.
16-1
Chapter 16
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:
www.johnsoncontrols.com
Software Release 5.0
16-2
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 points 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:
16-3
Auto Shutdown
Object
Shutdown State
Are values
equal?
No
Startup Delay
Yes
Yes
Is there an
active timer?
Yes
Delete timer.
No
No
Disable Alarms of
Dependent
Objects.
Enable Alarms of
Dependent
Objects.
AS Seq.vsd
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.
16-4
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.
16-5
16-6
Procedure Overview
Table 16-1: Working with Auto Shutdown Objects
To Do This
16-7
Detailed Procedures
Adding an Auto Shutdown Object
To add an Auto Shutdown object:
1.
2.
3.
4.
6.
7.
8.
9.
16-8
Browse to and select the Auto Shutdown object that you want to
edit.
2.
3.
4.
5.
6.
7.
Browse to and select the Auto Shutdown object that you want to
command.
2.
3.
Use the spacebar and Tab keys to select either Enable or Disable.
4.
Browse to and select the Auto Shutdown object that you want to
delete.
2.
3.
4.
17-1
Chapter 17
Introduction
The Multiple Command (MC) object issues a series of commands to
multiple objects with a single command action.
This chapter describes how to:
www.johnsoncontrols.com
Software Release 5.0
17-2
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 60F, 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 72F.
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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Multiple Command.
17-3
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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 (State0StateN)
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:
17-4
Procedure Overview
Table 17-1: Working with Multiple Command Objects
To Do This
Command a Multiple
Command Object
Detailed Procedures
Adding a Multiple Command Object
To add an Multiple Command object:
1.
2.
3.
17-5
17-6
Attribute
Required
Default
Options/Range
Object
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
Object Category
Yes
HVAC
Enabled
Yes
True
True, False
Commands Priority
Yes
Default
Relinquish Default
No
Blank
Number Of States
Yes
States Text
Yes
States
Action Table
(State0State32)
Yes
Engineering
Values
Display
Action Table
5.
6.
17-7
8.
Press the Tab key or the down arrow key to move to the next field.
9.
17-8
1.
2.
Note:
3.
4.
5.
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.
8.
2.
3.
4.
5.
6.
7.
8.
Press the Tab key or the down arrow key to move to the next field.
9.
17-9
2.
3.
4.
5.
6.
7.
8.
9.
17-10
2.
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.
Description
State 0 . . .
State 31
Override
Override Release
Release
Release All
Enable
Disable
4.
5.
Press Enter.
2.
3.
4.
18-1
Chapter 18
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:
www.johnsoncontrols.com
Software Release 5.0
18-2
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.
Attributes
Input Reference
The object and attribute whose value is monitored for COVs. This
objects 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 input reference attribute data type does not support sign up.
18-3
Procedure Overview
Table 18-1: Working with Data Broadcast Objects
To Do This
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.
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.
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.
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.
18-4
Detailed Procedures
Adding a Data Broadcast Object
To add a Data Broadcast object:
1.
2.
3.
4.
6.
7.
8.
18-5
Browse to and select the Data Broadcast object that you want to
edit.
2.
3.
4.
5.
6.
7.
Browse to and select the Data Broadcast object that you want to
command.
2.
3.
Use the spacebar and Tab keys to select either Enable or Disable.
4.
Browse to and select the Data Broadcast object that you want to
delete.
2.
3.
4.
19-1
Chapter 19
Working with
Demand Limiting/Load Rolling
(DLLR) Objects
T
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:
www.johnsoncontrols.com
Software Release 5.0
19-2
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
days 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.
19-3
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.
19-4
Load Objects
The Loads sign up for Change-of-Value (COV) on the DLLRs
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.
19-5
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:
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 objects Present Value attribute,
which has to support signup for COV.
EOI Attribute
Note:
The object providing this attribute must support signup for trigger
on this attribute.
19-6
Attributes
The values of an objects 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.
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Analog Alarm.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
19-7
19-8
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.
19-9
Procedure Overview
Table 19-1: Working with DLLR Objects
To Do This
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.
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.
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.
19-10
Detailed Procedures
Adding a DLLR Object
To add a DLLR object:
1.
2.
3.
Highlight DLLR and press Enter. The first of two DLLR attribute
screens appears (Figure 19-1).
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
DLLR
Object
Category
Yes
HVAC
Enabled
Yes
True
LR Mode
Yes
LR Monitor
only
LR Target
Yes
0.0 kW
Load Rolling
19-12
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Demand
Limiting
DL Mode
Yes
DL Monitor
only
Meter Object
Yes
Blank
Algorithm
Yes
None
Interval
Length
Yes
15 minutes
Offline Shed
Rate
Yes
0.0
kW/minutes
Demand Limit
Yes
0.0 kW
Rate Units
Yes
kW
Consumption
Units
Yes
kWh
Offline Shed
Rate Units
Yes
kW/min
Sliding
Window Alg
Sensitivity
Yes
Medium
Display
Display
Precision
Yes
10ths
Fixed Window
Alg
Limit
Elevation
Yes
0%
EOI Attribute
Yes
Blank
Registering
Phase
Yes
15 seconds
Algorithm
Delay
Yes
5 seconds
Restart
Register
Yes
False
Advanced
Setup
5.
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.
8.
2.
Note:
3.
Press the F3 (Edit) key. The DLLR object attribute screen appears
(Figure 19-1 and Figure 19-2).
4.
5.
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.
8.
19-14
2.
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.
Description
Force Register
Enable
Disable
4.
5.
Press Enter.
2.
3.
4.
20-1
Chapter 20
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:
www.johnsoncontrols.com
Software Release 5.0
20-2
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 objects 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.
20-3
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Load.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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 attributes number of states.
Shed State
Specifies the output attribute states to be switched to when the load is
shed.
20-4
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 2
Indicates the absolute power difference when output changes from
State 2 to State 0.
Rate 3
Indicates the absolute power difference when output changes from
State 3 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.
20-5
Display Precision
Indicates the rounded position and decimal places to display for this
object.
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 objects
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.
20-6
Procedure Overview
Table 20-1: Working with Load Objects
To Do This
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.
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.
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.
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.
2.
3.
Highlight Load and press Enter. The first of two Load object
attribute screens appears (Figure 20-1 and Figure 20-2).
20-7
20-8
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
Load
Object
Category
Yes
HVAC
Enabled
Yes
True
Comfort Alarm
Attribute
Yes
Blank
Output Alarm
Attribute
Yes
Blank
Output
Attribute
Yes
Blank
DLLR Object
Yes
Blank
Load Priority
Yes
Setup
20-9
Screen
Area
(Cont.)
Attribute
Required
Default
Options/Range
Setup
(Cont.)
Load Use
Yes
For DL
and LR
Number of
States
Yes
Shed State
Yes
Load Locked
Yes
False
Restart
Release
Yes
False
Alarm Release
Yes
False
Offline
Release
Yes
False
Rate 1
Yes
0.0. kW
Rate 2
Yes
0.0. kW
Advanced
Setup
Rate 3
Yes
0.0. kW
Rate Units
Yes
kW
Yes
1 minute
Max Shed
Time
Yes
1 minute
Min Release
Time
Yes
1 minute
Display
Precision
Yes
10ths
Registering
Delay
Yes
0 second
Period
Yes
86400
seconds
Restart
Register
Yes
False
5.
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.
8.
20-10
2.
Note:
3.
Press the F3 (Edit) key. The Load object attribute screen appears
(Figure 20-1 and Figure 20-2).
4.
5.
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.
8.
2.
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.
Description
Unlock Load
Lock Load
Force Register
Release Load
For DL
For LR
For DL and LR
Enable
Disable
4.
5.
Press Enter.
2.
3.
4.
21-1
Chapter 21
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:
www.johnsoncontrols.com
Software Release 5.0
21-2
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:
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Pulse Meter.
21-3
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
Display Precision
Indicates the rounded position and decimal places to display for this
object.
21-4
Procedure Overview
Table 21-1: Working with Pulse Meter Objects
To Do This
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.
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.
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.
21-5
Detailed Procedures
Adding a Pulse Meter Object
To add a Pulse Meter object:
1.
2.
3.
Highlight Pulse Meter and press Enter. The Pulse Meter object
attribute screen appears (Figure 21-1).
21-6
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
Pulse
Meter
Object
Category
Yes
HVAC
Enabled
Yes
True
Counter Object
Yes
Blank
Rollover Limit
Yes
32767
Setup
Rate Units
Yes
kW
Rate Constant
Yes
3600
Rate Limit
Yes
3.402823
E38
Rate Default
Yes
0 kW
Sample Time
Yes
60
seconds
Consumption
Units
Yes
kWh
Pulse
Consumption
Yes
1.0 kWh
Display
Precision
Yes
10ths
5.
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.
8.
21-7
2.
Note:
3.
Press the F3 (Edit) key. The Pulse Meter object attribute screen
appears (Figure 21-1).
4.
5.
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.
8.
2.
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.
Description
Reset
Start Meter
Resumes metering.
Stop Meter
Stops metering.
Enable
Disable
4.
Press Enter.
21-8
2.
3.
4.
22-1
Chapter 22
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:
www.johnsoncontrols.com
Software Release 5.0
22-2
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 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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Utility Profile.
22-3
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
Display Precision
Indicates the rounded position and decimal places to display for this
object.
Consumption Units
Specifies units for all energy values (kWh).
Rate Units
Specifies units for all demand values (kW).
22-4
Procedure Overview
Table 22-1: Working with Utility Profile Objects
To Do This
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.
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.
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.
22-5
Detailed Procedures
Adding a Utility Profile Object
To add a Utility Profile object:
1.
2.
3.
Highlight Utility Profile and press Enter. The Utility Profile object
attribute screen appears (Figure 22-1).
22-6
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
Utility Profile
Object
Category
Yes
HVAC
Enabled
Yes
True
DLLR Object
Yes
Blank
Meter Object
Yes
Blank
Tracking
Periods
Yes
31
Display
Precision
Yes
10ths
Consumption
Units
Yes
kWh
Rate Units
Yes
kW
Setup
5.
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.
8.
22-7
2.
Note:
3.
Press the F3 (Edit) key. The Utility Profile object attribute screen
appears (Figure 22-1).
4.
5.
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.
8.
2.
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.
Description
Display
Reset
Start Meter
Allows metering.
Stop Meter
Prevents metering.
Enable
Disable
22-8
4.
5.
Press Enter.
2.
3.
4.
23-1
Chapter 23
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:
www.johnsoncontrols.com
Software Release 5.0
23-2
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:
Calculation
Formula
Example
23-3
Conditions
Occurs:
Restoration of the Present Value and Rollover Count values to their initial
states
Results In:
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Analog Totalization.
23-4
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
23-5
Display Precision
Indicates the rounded position and decimal places to display for 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.
23-6
Procedure Overview
Table 23-3: Working with Analog Totalization Objects
To Do This
Command an Analog
Totalization Object
23-7
Detailed Procedures
Adding an Analog Totalization Object
To add an Analog Totalization object:
1.
2.
3.
23-8
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
Analog
Totalization
Object
Category
Yes
HVAC
Enabled
Yes
True
Input
Reference
Yes
Timebase
Yes
Hours
Scalefactor
Yes
1.0
Totalize
Limit
No
Blank
Low Cutoff
Value
Yes
0.0
Rollover
Yes
False
Units
Yes
Blank
Display
Precision
Yes
10ths
Engineering
Values
Display
5.
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.
8.
23-9
2.
Note:
3.
4.
5.
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.
8.
2.
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).
Description
Reset
Enable
Disable
4.
Press Enter.
23-10
2.
3.
4.
24-1
Chapter 24
Introduction
The Event Totalization object tracks the number of events or pulses
over time, meaning it counts the number of transitions in an objects
value.
This chapter describes how to:
www.johnsoncontrols.com
Software Release 5.0
24-2
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:
Calculation
Formula
Example
24-3
Conditions
Occurs:
Restoration of the Present Value and Rollover Count values to their initial
states
Results In:
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Event Totalization.
24-4
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
24-5
Units
Indicates the measurement units of this object.
Display Precision
Indicates the rounded position and decimal places to display for this
object.
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.
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.
24-6
Procedure Overview
Table 24-3: Working with Event Totalization Objects
To Do This
Command an Event
Totalization Object
24-7
Detailed Procedures
Adding an Event Totalization Object
To add an Event Totalization object:
1.
2.
3.
24-8
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
Event
Totalization
Object
Category
Yes
HVAC
Enabled
Yes
True
Input
Reference
Yes
Reference
Yes
State 0
Value Per
Pulse
Yes
Transition
Yes
Entering
State
Scalefactor
Yes
1.0
Totalize
Limit
No
Blank
Rollover
Yes
False
Units
Yes
Blank
Display
Precision
Yes
1s
Engineering
Values
Display
5.
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.
8.
24-9
2.
Note:
3.
4.
5.
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.
8.
2.
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.
Description
Reset
Enable
Disable
4.
Press Enter.
24-10
2.
3.
4.
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
24-12
Configuration (Cont.)
Explanation
Solution
25-1
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:
www.johnsoncontrols.com
Software Release 5.0
25-2
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:
Calculation
Formula
Example
Note:
TA represents the time the Input Reference spends in the Reference state.
25-3
Conditions
Occurs:
Restoration of the Present Value and Rollover Count values to their initial
states
Results In:
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Runtime Totalization.
25-4
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
Units
Indicates the measurement units of this object.
25-5
Display Precision
Indicates the rounded position and decimal places to display for this
object.
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.
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.
25-6
Procedure Overview
Table 25-3: Working with Runtime Totalization Objects
To Do This
Command a Runtime
Totalization Object
Detailed Procedures
Adding a Runtime Totalization Object
To add a Runtime Totalization object:
1.
2.
3.
25-7
25-8
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
Runtime
Totalization
Object
Category
Yes
HVAC
Enabled
Yes
True
Input
Reference
Yes
Reference
Yes
State 1
Scalefactor
Yes
1.0
Totalize Limit
Yes
(hours)
Rollover
Yes
False
States Text
Yes
States
Units
Yes
hours
Display
Precision
Yes
10ths
Engineering
Values
Display
5.
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.
8.
25-9
2.
Note:
3.
4.
5.
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.
8.
2.
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.
Description
Reset
Enable
Disable
4.
Press Enter.
25-10
2.
3.
4.
26-1
Chapter 26
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:
www.johnsoncontrols.com
Software Release 5.0
26-2
Key Concepts
Analog Alarm Object
When the Analog Alarm objects Input attribute value exceeds the
defined limits, it causes a change in the Analog Alarm objects 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 60F and an alarm issued if the
temperature falls below 50F.
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.
26-3
Attributes
The values of an objects 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.
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Analog Alarm.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
26-4
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.
26-5
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.
26-6
Procedure Overview
Table 26-1: Working with Analog Alarm Objects
To Do This
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.
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.
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.
26-7
Detailed Procedures
Adding an Analog Alarm Object
To add an Analog Alarm object:
1.
2.
3.
Highlight Analog Alarm and press Enter. The first of two Analog
Alarm attribute screens appears (Figure 26-1).
Note:
26-8
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
Analog
Alarm
Object
Category
Yes
HVAC
Enabled
Yes
True
Input
Reference
Yes
Blank
Engineering
Values
26-9
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Engineering
Values (Cont.)
High Alarm
Limit
No
Blank
Low Alarm
Limit
No
Blank
Differential
Yes
0.00
High Warning
Offset
No
Blank
Warning
Reference
Alarm Setup
Alarm State
Low Warning
Offset
No
Blank
Yes
False
Fault Priority
Yes
Serious
Off Normal
Ack Req
Yes
False
Event Enable
Yes
True
Dialout
Required
Yes
False
Delay Time
Yes
0 seconds
Units = Seconds
Off Normal
Priority
Yes
Important
26-10
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Alarm State
(Cont.)
Normal Ack
Req
Yes
False
Normal
Priority
Yes
Status
Alarm Setup
Notification
Class
Report Delay
Alarm
Message Text
Yes
Blank
5.
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.
8.
2.
Note:
3.
Press the F3 (Edit) key. The Analog Alarm object attribute screen
appears.
4.
5.
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.
8.
2.
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.
Description
Cancel Delay
Time
Cancel Report
Delay Time
Enable
Disable
4.
Press Enter.
2.
3.
4.
27-1
Chapter 27
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:
www.johnsoncontrols.com
Software Release 5.0
27-2
Key Concepts
Multistate Alarm Object
When the Multistate Alarm objects 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 objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Multistate Alarm.
27-3
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Indicates if the object is active and executing an operational condition.
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.
27-4
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.
27-5
Procedure Overview
Table 27-1: Working with Multistate Alarm Objects
To Do This
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.
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.
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.
27-6
Detailed Procedures
Adding a Multistate Alarm Object
To add a Multistate Alarm object:
1.
2.
3.
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
Multistate
Alarm
Object
Category
Yes
HVAC
Enabled
Yes
True
27-7
27-8
Screen Area
(Cont.)
Attribute
Required
Engineering
Values
Input
Reference
Yes
Normal State
Yes
State 0
Yes
False
Fault Priority
Yes
Serious
Normal Ack
Req
Yes
False
Normal
Priority
Yes
Status
Alarm Setup
Default
Notification
Class
Alarm State
Event Enable
Yes
True
Dialout
Required
Yes
False
Report Delay
Alarm Setup
Options/Range
Delay Time
No
0 second
Units = seconds
Alarm
Message Text
No
Blank
5.
6.
Check the User Assistance area of the screen to verify if the save
was successful. If errors are detected, correct them and resave the
entries. Once the save is successful, continue with Step 7.
7.
8.
27-9
2.
Note:
3.
4.
5.
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.
8.
2.
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.
Description
Enable
Disable
4.
Press Enter.
27-10
2.
3.
4.
28-1
Chapter 28
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:
www.johnsoncontrols.com
Software Release 5.0
28-2
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
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Trend Log.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
28-3
Enabled
Indicates if the object is active and executing an operational condition.
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.
28-4
Procedure Overview
Table 28-1: Working with Trend Log Objects
To Do This
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.
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.
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.
28-5
Detailed Procedures
Adding a Trend Log Object
To add a Trend Log object:
1.
2.
3.
Highlight Trend Log and press Enter. The Trend Log object
attribute screen appears (Figure 28-2).
28-6
Attribute
Required
Default
Options/Range
Object
Object
Name
No
Blank
Maximum 32 characters
Invalid characters: @ . ? * $ # : [ ]
If not completed, the system assigns a name.
Setup
Description
No
Blank
Maximum 40 characters
Object Type
Yes
Trend Log
Object
Category
Yes
HVAC
Enabled
Yes
True
Stop When
Full
Yes
False
Buffer Size
144
1-5000
Log Interval
600
Minimum Value = 0
Maximum Value = 86400
Units = Seconds
Input
Reference
Yes
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.
8.
28-7
2.
Note:
3.
Press the F3 (Edit) key. The Trend Log object attribute screen
appears (Figure 28-2).
4.
5.
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.
8.
2.
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.
Description
Display
Displays the data that the Trend Log object collected from
the Input Reference object. See sample in Figure 28-1.
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
Enable
Disable
28-8
4.
5.
Press Enter.
2.
3.
4.
29-1
Chapter 29
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:
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:
www.johnsoncontrols.com
Software Release 5.0
29-2
29-3
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.
29-4
Type
Description
Time
Issue Confirmed
Notifications
Boolean
Process Identifier
Unsigned
Recipient
BACnet Recipient
Transitions
Valid Days
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.
29-5
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.
29-6
Procedure Overview
Table 29-2: Notification Class Object
To Do This
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.
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.
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.
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.
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.
29-7
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.
3.
In the object library on the left side of the screen, open the N30
folder.
4.
5.
6.
29-8
8.
10. Click the Structure Elements button. A new Recipient form opens
(Figure 29-3).
29-9
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
Object ID
The BACnet Object Identifier of the device object to which Event Notification
messages are sent.
Address IP
The Internet Protocol (IP) Address of the destination if routing via address.
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
Transitions
29-10
2.
3.
4.
5.
Click the Structure Elements button for the Recipient you want to
edit.
7.
8.
9.
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:
29-12
Browse to and select the Notification Class object that you want
to edit.
2.
4.
Note:
5.
6.
7.
2.
3.
4.
2.
3.
4.
30-1
Chapter 30
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:
Note:
www.johnsoncontrols.com
Software Release 5.0
30-2
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:
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 objects Connected To attribute does not change to Metasys
device. If the Error State attribute is set to this state, the Remote
Destination objects offline status is True.
Disconnected - The Remote Destination object currently does not need
to be connected.
30-3
30-4
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:
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.
30-5
30-6
Procedure Overview
Table 30-1: Remote Destination Object Procedure Overview
To Do This
Note:
30-7
Detailed Procedures
Adding a Remote Destination Object
To add a Remote Destination object:
1.
2.
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.
30-8
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
Remote
Destination
Object
Category
Yes
HVAC
30-9
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Engineering
Values
Port Number
Yes
Port 2
Dial Connect
Timeout
Yes
60
Retry
Interval
Yes
180
Retries
Yes
Password
Yes
Blank
SNR Dial
Out Level
Yes
80 %
35-100 percent
Login Id
Yes
Blank
Phone
Number
Yes
Blank
Active Filter
Yes
Pass All
Priority
Filter A
Yes
[4] Items
Category
Filter A
Yes
[5] Items
Msg Type
Filter A
Yes
[3] Items
Priority
Filter B
Yes
[4] Items
Category
Filter B
Yes
[5] Items
Msg Type
Filter B
Yes
[3] Items
Modem
Config
Object
No
Blank
Remote
Device
Name
No
Blank
Process
Identifier
Yes
Blank
Max SNR
Queue
Yes
25
3-100
Ack
Required
Yes
True
5.
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.
30-10
7.
8.
2.
3.
4.
5.
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.
8.
2.
3.
4.
31-1
Chapter 31
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:
www.johnsoncontrols.com
Software Release 5.0
31-2
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:
31-3
31-4
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.
31-5
Active Filter
Selects the type of filtering in effect for the E-mail object. The filter
types are as follows:
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.
31-6
None
Queue Full
Server Error
Example
Figure 31-4 and Figure 31-5 show screens from a sample completed
E-mail object.
31-7
31-8
Procedure Overview
Table 31-1: E-mail Object Procedure Overview
To Do This
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.
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.
31-9
Detailed Procedures
Adding an E-mail Object
To add an E-mail object:
1.
2.
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.
31-10
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
Object
Category
Yes
HVAC
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
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
Yes
180
60-600 seconds
Retries
Yes
0-10
Max SNR
Queue
Yes
25
3-100
Process
Identifier
Yes
Blank
Active Filter
Yes
Pass All
Priority
Filter A
Yes
[4] Items
Category
Filter A
Yes
[5] Items
Msg Type
Filter A
Yes
[3] Items
Priority
Filter B
Yes
[4] Items
Category
Filter B
Yes
[5] Items
Msg Type
Filter B
Yes
[3] Items
5.
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.
8.
31-12
2.
3.
4.
5.
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.
8.
2.
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.
Description
Disable
Enable
Queue Clear
4.
Press Enter.
2.
3.
4.
32-1
Chapter 32
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:
www.johnsoncontrols.com
Software Release 5.0
32-2
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:
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).
Note:
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.
Pager Message
SNR Message
SER
Fault
Alarm Message
04 Jun 2001 11:05:47
pagermsg
32-3
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:
32-4
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.
32-5
Procedure Overview
Table 32-1: Pager Object Procedure Overview
To Do This
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.
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.
32-6
Detailed Procedures
Adding a Pager Object
To add a Pager object:
1.
2.
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.
32-7
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
Pager
Object
Category
Yes
HVAC
32-8
Screen Area
(Cont.)
Attribute
Required
Default
Options/Range
Engineering
Values
Port Number
Yes
PORT2
Enumeration set:
1 = PORT1
2 = PORT2
3 = PORT3
Retries
No
0-10
Process
Identifier
Yes
Blank
Pager
Number
No
Blank
Pager
Service
No
Blank
Modem
Config
Object
No
Blank
Object reference
Active Filter
Yes
Pass All
Priority
Filter A
Yes
[4] Items
Category
Filter A
Yes
[5] Items
Msg Type
Filter A
Yes
[3] Items
Priority
Filter B
Yes
[4] Items
Category
Filter B
Yes
[5] Items
Msg Type
Filter B
Yes
[3] Items
5.
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.
8.
32-9
5.
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.
Description
Disable
Enable
7.
Press Enter.
2.
3.
4.
32-10
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.
2.
3.
Press 0 to view all attributes. Figure 32-4 and Figure 32-5 show
sample screens with all Pager attributes displayed.
Sample Value
Description
Dial Reply
Connect 9600
Req ID Send
CrCr
Req ID Reply*
CrLf ID =
Request ID message
Req ID Retry
2 Seconds
Snd ID Send
EcPG1Cr
Send ID message
Snd ID Reply*
CrAkCrEcBrpCr
Snd ID Retry
1 Seconds
Sx5426623Cr
"Snr Msg etc."
CrAkCr
1 Seconds
EtCr
CrEcEtCr
Terminate Retry
0 Seconds
09:29:58
02 Aug 2001
* 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.
33-1
Chapter 33
Introduction
Note:
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:
Note:
www.johnsoncontrols.com
Software Release 5.1
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:
For information on the Group object, refer to the Working with Group
Objects chapter (LIT-6892060) of the N30 Supervisory Controller
Users Manual or the Group chapter (LIT-694420) of the Object
Dictionary.
Attributes
The values of an objects 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 Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
33-3
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:
Format
Example
Full Reference
with Array Index
B7F3N01.Programming.AV{1}
.Priority Array[8]
Full Reference
without Array Index
B7F3N01.Programming.AV{1}
.Present Value
Functional Name
with Array Index
Functional Name
without Array Index
<Object ID>.<Attribute>
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
33-4
Detailed Procedures
Notes:
33-5
Do This
Object Name
Description
Object Type
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).
33-6
Figure 33-2: List Of Group Members Dialog Box Optimal Start (OST) Example
Notes:
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:
33-7
Controls Group
507 E. Michigan Street
P.O. Box 423
Milwaukee, WI 53201
www.johnsoncontrols.com
Printed in U.S.A.
34-1
Chapter 34
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 attributes 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:
www.johnsoncontrols.com
Software Release 5.1
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 objects 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 objects attributes determine how the object operates.
The Event Enrollment object attributes are described below.
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
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.
34-3
Format
Example
B7F3N01.Programming.AV{1}
.Priority Array[8]
B7F3N01.Programming.AV{1}
.Present Value
<Object ID>.<Attribute>
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
Full Reference
with Array Index
Full Reference
without Array Index1
P
Functional Name
with Array Index
Functional Name
2
without Array Index
P
1
2
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
Change of State
Change of Value
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.
34-4
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.
34-5
Detailed Procedures
Notes:
34-6
34-7
Do This
Object Name
Description
Object Type
Object Category
Select the desired category for this Event Enrollment object from the
drop-down menu. Default is HVAC.
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.
Type the desired text of the alarm message for event notification (optional).
3.
34-8
2.
4.
5.
Click Execute.
6.
Click Close.
34-9
2.
3.
Use the Spacebar and the Backspace key to select the desired
command. The Event Enrollment object supports the commands
in Table 34-4.
Description
Enable
Disable
4.
Press Enter.
2.
3.
4.
34-10
Figure 34-3: M-View Edit Attributes Dialog Box - Change of Bitstring Example
2.
3.
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.
Note:
7.
8.
Click the List Elements button. The Bitstring Values dialog box
appears (Figure 34-6).
34-12
Note:
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).
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.
34-14
Figure 34-8: M-View Edit Attributes Dialog Box - Change of State Example
2.
3.
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 List Elements button. The List of Values dialog box
appears (Figure 34-10).
Note:
7.
Note:
8.
34-16
9.
Figure 34-11: M-View Edit Attributes Dialog Box Change of Value Example 1
2.
3.
34-18
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.
Type the desired value in the COV Increment box that you want
the attribute to change before generating an alarm.
Note:
6.
7.
Figure 34-13: M-View Edit Attributes Dialog Box Change of Value Example 2
2.
3.
34-20
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.
Notes:
6.
7.
Figure 34-15: M-View Edit Attributes Dialog Box - Command Failure Example
2.
3.
34-22
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:
6.
7.
Figure 34-17: M-View Edit Attributes Dialog Box - Floating Limit Example
2.
3.
34-24
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.
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:
9.
Figure 34-19: M-View Edit Attributes Dialog Box - Out of Range Example
2.
3.
34-26
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.
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:
Controls Group
507 E. Michigan Street
P.O. Box 423
Milwaukee, WI 53201
8.
9.
www.johnsoncontrols.com
Printed in U.S.A.
A-1
Appendix A
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.
www.johnsoncontrols.com
Software Release 5.0
A-2
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.
7
N2 Binary Input
Object
(Output Alarm)
N2 Binary Input
Object
(Comfort Alarm)
Load Object
N2 Binary Output
Object
Load Object
N2 Binary Output
Object
Pulse Meter
Object
Utility Profile
Object
Schedule Object
N2 Pulse Counter
Object
Pulse Meter
Object
DLLR Object
DLLR Flow
A-3
Object
Role
DLLR
Receives energy consumption data from the Pulse Meter object to manage
demand limiting and load rolling through the shedding of loads.
Load
Registers with the DLLR object to let the DLLR object know that it exists and
can be shed.
Utility Profile
Collects utility data from a Pulse Meter object and a DLLR object.
Pulse Meter
N2 Pulse
Counter
Counts energy pulses via the N2 Bus from an actual hardware meter and
relates the data to the Pulse Meter object.
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 Loads
associated output can also be a Binary Value (BV), Multistate Output (MSO),
Multistate Value (MSV), or Multiple Command (MC) object.
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.
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.
Schedule
Object
A-4
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
DLLR
Meter Object
Load
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.
Meter Object
DLLR Object
Pulse Meter
Counter Object
N2 Pulse Counter
None
Output Object
None
Output Alarm
Object
None
Comfort Alarm
Object
None
Schedule Object
Enter the name of the Utility Profile object and schedule the
Utility Profiles 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 Schedules fast clock feature
should run.
Utility Profile
A-5
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
Utility
Profile
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
Schedule
Trend Log
Global Data
Sharing
Signal
Select
A-6
Procedure Overview
Table A-4: Building an Energy Management Application
To Do This
A-7
Detailed Procedures
Building an Energy Management Application
To build an energy management application:
1.
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.
4.
Add a Utility Profile object to the same device as the Pulse Meter
and DLLR objects.
5.
6.
7.
8.
A-8
Troubleshooting
This section provides some guidelines for making an energy
management application successful.
Table A-5: Energy Management Troubleshooting Guidelines
Guideline
Procedure
It is best to throttle (regulate the speed of) the load registration process by
modifying each Load objects Registering Delay attribute, if one or more of the
following conditions exist:
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 objects 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 objects 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
objects 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 objects
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 objects 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.
Continued on next page . . .
A-9
Guideline (Cont.)
Procedure
4.
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 objects 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 objects 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 objects Eligibility attribute. If Ineligible, continue with Step 3.
3. Check each Load objects Shed Refusal attribute for a reason why the Load
may be ineligible for shedding.
4. Remove all of the conditions listed in the Load objects Shed Refusal attribute
until the load becomes eligible, and Shed Refusal becomes No Refusal.
If the numbers still do not match, and re-sending the Load objects Force
Register command does not correct the situation, check each Load objects
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 objects
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 objects 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 objects 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 objects 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.
A-10
Guideline (Cont.)
Procedure
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 objects 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 Meters 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 objects N2 device is online.
4. Check if the value of the Pulse Meter objects Consumption attribute actually
represents the consumption of a single pulse. Refer to the meters type plate
or user manual.
5. Check if the value of the Pulse Meter objects 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 objects Rate
Limit attribute. To estimate the calculated rate:
a. Monitor the Pulse Meters 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 objects Sample Time is set to 60 seconds.
This ensures that the DLLR algorithm always uses current data calculated
from the last minutes 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 meters Present Value attribute
can be correctly read, and that it represents the average demand during the last
60 seconds.
A-11
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 objects 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.
The DLLR objects 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 objects LR Mode attribute to LR Shedding.
2. Verify that the DLLR objects LR Shed attribute quickly becomes equal to or
greater than the DLLR objects LR Target attribute.
3. If it does not reach the target, verify that the DLLR objects DLLR Status
attribute reads In Alarm.
4. Make sure that the DLLR objects 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.
When the DLLR objects 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 objects DL Mode attribute to Shedding.
2. Verify that the value of the DLLR objects Interval Demand attribute always
stays below the value of the DLLR objects 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 objects DLLR Status reads
In Alarm.
4. Make sure that the DLLR objects 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 systems behavior, the
Demand Limit may gradually be set closer to the actual limit provided by the utility
company.
A-12
Guideline (Cont.)
Procedure
The DLLR objects 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
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.
Not Eligible
Shed Accepted
Shed Refused
Shed Pending
Shed Lost
Interval Demand
Demand History
Amount Shed
LR Shed
LR to Shed
LR not Shed
DL Shed
DL to Shed
DL not Shed
Active Elevation
Profile Limit
Max Demand
A-13
Guideline (Cont.)
Procedure
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 objects 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 Profiles 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:
Consumption Unc
Consump Unreliable
Peak Unreliable
Demand Peak
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 objects user manual for more information on how to verify these
conditions.
B-1
Appendix B
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.
www.johnsoncontrols.com
Software Release 5.0
B-2
B-3
Key Concepts
Message Router Purpose
The Message Router object controls where important dynamic system
information is recorded or displayed. This information can include:
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.
B-4
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
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
Serious
Services
System Alert
Memory Overload
Serious
Services
System Alert
CPU Overload
Serious
Services
System Alert
Serious
Services
System Alert
Update References
Serious
Services
System Alert
Acknowledgement
Status
Services
Operator Transaction
(User Defined)
(User Defined)
Alarm
B-5
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.
3
Printer Objects
2
Alarm Objects
(Analog and Multisate)
Message Router
Object
4
VT100 Objects
MR Flow
Object
Role
Message
Router
Object
Receives alarm messages and SNRs from Alarm objects, works with the
Report Server object to distribute the messages throughout the system.
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.
Printer
Objects
VT100
Objects
C-1
Appendix C
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.
www.johnsoncontrols.com
Software Release 5.0
C-2
Key Concepts
Object Interaction
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.
5
Any Analog Attribute
(Zone Temperatue)
6
Any Analog Attribute
(Cooling Setpoint)
1
7
Any Analog Attribute
(Heating Setpoint)
8
Any Analog Attribute
(Optional)
(Outdoor Air
Temperature)
Schedule Object
OST Flow
Object
Role
Optimal Start
Schedule
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.
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.
C-3
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
Optimal Start
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 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.
Outside Air
Temperature
Enter the name of the Binary object that controls zone occupancy.
Schedule
C-4
Procedure Overview
Table C-3: Building an Optimal Start Application
To Do This
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.
C-5
Detailed Procedures
Building an Optimal Start Application
To build an Optimal Start application:
1.
2.
3.
Make sure valid start and stop times are entered into the Schedule
object.
4.
C-6
Troubleshooting
This section provides some solutions for problems in an Optimal Start
application.
Table C-4: Optimal Start Troubleshooting Problems and Solutions
Problem
Solution
The Optimal Start objects Present Value attribute may indicate Not Operational
because of errors in its connection status to other required objects.
To verify the Optimal Start objects 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.
D-1
Appendix D
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.
www.johnsoncontrols.com
Software Release 5.0
D-2
Key Concepts
Object Interaction
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.
2
Source Object
Source Object
Interlock Object
Source Object
Object
Role
Interlock
Object
2-4
Source
Objects
Provide attribute data that work with the Interlock objects 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
D-3
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
Interlock Object
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
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
Logic
Logic Equation
Delay
Command ID
Parameters
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
Command ID
D-4
Parameters
Example
Figures D-2 through D-5 show screens from a sample completed
Interlock object. This sample object uses the Logic Equation attribute.
D-5
D-6
D-7
Procedure Overview
Table D-3: Building an Interlock Application
To Do This
D-8
Detailed Procedures
Building an Interlock Application
To build an Interlock application:
1.
2.
3.
4.
E-1
Appendix E
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.
www.johnsoncontrols.com
Software Release 5.0
E-2
Key Concepts
Object Interaction
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.
2
N2 Analog
Input Object
(Zone)
N2 Analog
Output Object
(Setpoint)
N2 Analog
Input Object
(Zone)
6
N2 Analog
Output Object
(Setpoint)
N2 Analog
Input Object
(Zone)
N2 Analog
Output Object
(Setpoint)
SSA Flow
Object
Role
Signal Select
Object
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
E-3
receives.
2
N2 Binary
Input Object
(Zone)
N2 Binary
Output Object
(Setpoint)
N2 Binary
Input Object
(Zone)
6
N2 Binary
Output Object
(Setpoint)
N2 Binary
Input Object
(Zone)
N2 Binary
Output Object
(Setpoint)
SSB Flow
Object
Role
Signal Select
Object
2-3
Binary
Objects
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.
E-4
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
Signal Select
Object (Analog or
Binary)
Input List
Enter the exact object and analog or binary attribute names used
in the Signal Select computation.
Average Output
High OR
Low AND
Point Type
E-5
Procedure Overview
Table E-4: Building a Signal Select Application
To Do This
E-6
Detailed Procedures
Building a Signal Select Application
To build a Signal Select application:
1.
2.
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.
F-1
Appendix F
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).
www.johnsoncontrols.com
Software Release 5.0
F-2
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.
Associated SNR
Alarm Notification
Offline Notification
N30 Online/Offline
System Notification
Memory/CPU Overload
Operator Login/Logout
Battery Status
Update References
Acknowledgement
F-3
F-4
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.
3
Printer Objects
2
Alarm Objects
(Analog and Multisate)
Notification Class
Object
4
VT100 Objects
BNC Flow
Object
Role
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.
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.
Printer
Objects
VT100
Objects