Professional Documents
Culture Documents
Table of Contents
Introduction................................................................................................ 10-1
Introduction................................................................................................ 25-1
Key Concepts...............................................................................................A-2
Object Interaction .......................................................................................................A-2
Attribute Involvement..................................................................................................A-4
Advanced Object Functions .......................................................................................A-5
Procedure Overview ....................................................................................A-6
Key Concepts...............................................................................................B-3
Message Router Purpose ..........................................................................................B-3
Routing SNRs ............................................................................................................B-3
Filtering ......................................................................................................................B-4
Object Interaction .......................................................................................................B-5
Appendix C Building an Optimal Start Application ............................C-1
Introduction..................................................................................................C-1
Key Concepts...............................................................................................C-2
14 N30 Supervisory Controller User’s Manual
Key Concepts...............................................................................................D-2
Object Interaction ...................................................................................................... D-2
Attribute Involvement................................................................................................. D-3
Example .................................................................................................................... D-4
Procedure Overview ....................................................................................D-7
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:
• organization of information in this manual
• where to find related information about the N30
• manual conventions
This manual is written with the assumption that the user is familiar
with the general concepts and terminology of Building Automation
Systems (BAS) and Heating, Ventilating, and Air Conditioning
(HVAC).
Note: Unless otherwise indicated, the information in this manual
refers to both the N30 Supervisory Controller and the
N31 Supervisory Controller.
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.
N30 Supervisory Controller User’s Manual 1-3
Chapter Organization
Each chapter in the N30 Supervisory Controller User’s Manual can be
divided into the main sections identified in Table 1-1.
Related Publications
Table 1-2 describes where to find various types of information about
the N30 Supervisory Controller.
Chapter 2
Introduction to the
N30 Supervisory Controller
Introduction
This chapter describes the basic functions and operation of an
N30 Supervisory Controller (N30). It also provides the foundation you
need to monitor and control your facility using the N30.
This chapter includes:
• N30 concepts
• descriptions and illustrations of the Building Automation System
(BAS) components
Key Concepts
N30 Supervisory Controller
The N30 monitors and controls HVAC equipment in your facility. It
provides powerful data gathering and energy management tools, such
as Totalization and Demand Limiting, which can improve the cost
efficiency of your facility. The N30 is optionally available with an
integral Local Display Terminal (LDT).
N30 Capabilities
You can complete the following BAS functions with the N30:
• schedule BAS actions
• set up calendars, including exception and holiday calendars
• monitor facility conditions
• detect and respond to alarms
• control equipment and automate routine functions
• collect trend and totalization data
• reduce energy consumption and costs
BAS Components
A typical BAS configuration consists of the components listed below
and illustrated in Figure 2-1 and Figure 2-2.
• Multiple N30 Supervisory Controllers (with or without optional
Local Display Terminal [LDT])
• VT100 Terminal/Terminal Emulator
• Ethernet Local Area Network (LAN)
• N2 Bus (field bus or controller bus)
• serial printer
• N2 controllers (Table 2-1)
N30 Supervisory Controller User's Manual 2-3
M-Series Workstation
or PC with VT100 Emulator
VT100
or
VAV VMA
N2
esc
Serial
Printer N30 with LDT
AHU
DX UNT
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.
N30 Supervisory Controller User's Manual 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:
• upgrade existing N30s to the latest firmware
• import Advanced Installation Management (AIM) Tools point lists
and room schedule information
• configure the complete N30 database
• upload and download Application Specific Controllers (ASCs) and
DXs from a file created by Configuration Tools
M-Tool includes the N30 Upgrade Utility, which allows you to
upgrade databases from the data format used at one release to the data
format used at the next release.
esc
VT100
N2 N2
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 N30 Supervisory Controller User’s Manual
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.
Chapter 3
Getting Started
Introduction
A VT100 can be used to add and edit objects and to browse an N30
database. Project Builder software provides an easier way to create,
define, and edit N30 databases offline. This chapter explains the
VT100 interface to the N30 and describes tasks performed in using an
N30. Notes on using Project Builder to perform these tasks are
included where appropriate. This chapter describes how to:
• log on to an N30
• check the firmware version level of an N30
• set the date and time
• edit the attributes of an N30
• browse an N30 database with a VT100
• add objects with a VT100
• edit objects with a VT100
• command objects
• display a summary
• print a summary
• change an IP address
• rebind a site
• change device names
• archive the current database
Key Concepts
N30 Task Overview
Figure 3-1 is a flowchart of tasks to get started with your N30 system
using the VT100 and, in the case of setting up the N30 site, Project
Builder software. Other documents are referenced where required.
For information about generating N30 databases using Project Builder,
refer to the N30 Supervisory Controller Quick Start Technical Bulletin
(LIT-6891200).
Note: We recommend generating databases using Project Builder
software. Project Builder supports copy, paste, and mass
copy and can save you a substantial amount of time.
Define Groups.
Print Controller See Working with Group
Configurations. Define Trend Logs. Objects chapter in this manual.
See the N30 Supervisory See the Working with Trend
Controller Point Mapping Log Objects chapter
Technical Bulletin in this manual.
(LIT-6891400).
Edit and add additional
Build Energy Management objects as required.
Applications. See the appropriate chapter in
See Appendix A: Building an this manual or in the
Add Controllers to your Energy Management Object Dictionary.
Database and Map the Points Application in this manual.
to N30 Point Objects.
See the N30 Supervisory
Controller Point Mapping Build Optimal Start
Technical Bulletin Applications.
(LIT-6891400) and the See Appendix C: Building an
Object Dictionary. Optimal Start Application
in this manual.
N30 Overview.vsd
Objects
Configurable and reusable features of the N30 that contain both data
and a means to act on that data to achieve desired results. They add
flexibility to the programming of the N30 by allowing you to add only
the objects you need to your database. They are the building blocks of
the N30 database. Individual objects are described throughout the N30
literature. The Object Dictionary provides a reference to all the current
N30 objects.
Object Names
Providing an Object Name is optional, but if it is defined, it must be
unique throughout the site. If it is not defined, the full reference
becomes the identifier. For example, Building1Floor2. The following
characters are not allowed: @ . ? * $ # : ‘ [ or ].
Containers
The basic organization of the N30 database is arranged through
containers. All objects are added to containers. The type of container
selected determines the type of objects that can be added to that part of
the database. See Table 3-1 for a list of which objects can be added to
each container.
A container object can hold a maximum of 75 objects. However, since
there are hidden objects in N30s, N30s are limited to 50 child objects.
To put more than 50 objects in an N30, use Container objects to
organize your objects. Use a maximum of 50 Container objects in
one N30.
Groups
A way to personalize the organization of a N30 database. Groups
contain references to objects. This allows you access to the object from
both the designated group and from the container where it was added.
They are a powerful organizational tool when working with large
databases. For more information, see the Working with Group Objects
(LIT-6892060) chapter in this document.
Flash Memory
A type of nonvolatile memory within the N30 device. The N30’s Flash
memory stores configuration data, startup code, boot code, main code,
and the archive database within this memory.
N30 Supervisory Controller User’s Manual 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. Outdoor Air (an N2 Analog Input object on N30-B) is used in an
Interlock object in N30-A.
2. N30-A temporarily loses its network connection to N30-B.
3. User moves Outdoor Air from N30-B to N30-C.
4. User reestablishes the network connection to N30-A.
5. User must Rebind Site in order for the Interlock object in N30-A
to reestablish its reference to Outdoor Air.
3-6 N30 Supervisory Controller User’s Manual
2 Site/User Information Used to view site/user information. Occupies Line 3 at the top of the
screen. Site/user information displayed in this example includes (from
left to right):
• device object name (Dean)
• name of logged-in user (ADMIN)
• date and time (Fri 28 Jan 2000 9:18 CST)
3 User Workspace Used to view site information and to complete most operations.
Occupies Lines 4 through 22 in the middle of the screen. In this space,
the operator displays and interacts with objects, calls up summaries,
and uses the available features to program the site.
In this example, Brown Deer is the name of the site, Overview Grp is
the name of the Site Group, and South Building and Dean are names
the operator gave to the two N30s on this site.
4 User Assistance Used to view function key options, help messages, and error
messages. Occupies Lines 23 and 24 at the bottom of the screen.
Browsing
Browsing with a VT100 is moving within and through the N30
database to view, edit, and command objects. Browsing with Project
Builder software is performed offline and therefore commands are not
available. For information on browsing an N30 database using an
M-Series Workstation, see M-Explorer User’s Guide.
The User Assistance Line at the bottom of each screen (Number 4 in
Figure 3-2) displays the active keys and functions. The active keys and
the functions associated with each key change according to where you
are in the database. It also provides instructions for filling in attribute
fields. Some basic navigational keys are available but not described,
such as the arrow keys for moving the cursor.
3-10 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 3-4: Getting Started
To Do This Follow These Steps:
Log On to an N30 Start your VT100 Emulator or turn on your VT100. Press Enter when the
N30 name appears at the top of the screen. Type your Login ID and press
Enter. Type your password and press Enter.
Check the Firmware Version Using a VT100 Terminal or VT100 Terminal Emulator on a PC, browse to
Level of an N30 and highlight the N30 you want to check. Press Enter. The firmware
version level is on the right side under engineering values.
Set the Date and Time Use the arrow keys to highlight an N30. Press the F2 (Command) key.
Cycle through the list of commands until the Set Time or Set Date
command appears. Use the arrow keys or Tab key to highlight the Value
field. Edit the value as necessary. Press Enter.
Edit the Attributes of the N30 Use the arrow keys to highlight an N30. Press Enter. Press the F3 (Edit)
key. Move to the field that you want to edit. Edit the values. Press the
F3 (Save) key to save the changes or the F4 (Cancel) key to cancel the
changes.
Browse an N30 Database with Use the arrow keys to highlight an N30. Use the Spacebar to expand the
a VT100 list of containers. Select a container. Press the Spacebar to expand the
list of objects. Select an object. Press the Spacebar to expand the list of
additional objects and select an object. Press Enter to open the object.
Add Objects with a VT100 Browse to and highlight an N30. Press the Spacebar to expand the list of
object containers. Browse to and highlight a container or object. Press the
F3 (Add) key. Select the type of object to add and press Enter. Fill in the
fields. Press the F3 (Save) key.
Edit Objects with a VT100 Browse to and highlight an object. Press Enter to open the object. Press
the F3 (Edit) key. Edit as desired. Press the F3 (Save) key.
Command Objects Browse to and highlight an object. Press the F2 (Command) key. Use the
Spacebar and the Backspace key to cycle through the list of commands
until the desired command appears. Press Enter to carry out the
command.
Display a Summary Browse to and highlight the Summary container. Press the Spacebar to
expand the list of Summaries. Highlight a Summary. Press the
F2 (Command) key. Use the Spacebar and Backspace keys to cycle
through the list until Display appears. Press Enter.
Print a Summary Browse to and highlight the Summary container. Press the Spacebar to
expand the list of Summaries. Highlight a Summary. Press the
F2 (Command) key. Use the Spacebar and Backspace keys to cycle
through the list until Print appears. Use the arrow keys or Tab key to
highlight the Destination field. Use the Spacebar and the Backspace key
to cycle through to the desired printer. Press Enter.
Change an IP Address Browse to and select an N30. Press Enter. Press the F3 (Edit) key. Move
the cursor to IP Address. Press Enter. Type in the address for your
network. Press the F4 (Back) key. Enter the IP Mask and IP Router
addresses. Press the F3 (Save) key. Press any key to continue. Press the
F4 (Cancel) key to return to the main screen. Press Q to quit the N30.
Warm start the N30 to reset.
Rebind a Site Browse to and highlight an N30. Press Enter to open the N30 Device
object. Press the F2 (Command) key. Use the Spacebar and Backspace
key to cycle through the list until Rebind Site appears. Press Enter.
Continued on next page . . .
N30 Supervisory Controller User’s Manual 3-13
Detailed Procedures
The following procedures assume the N30 is already set up properly.
If using a direct serial port connection from the PC to the N30, see the
appropriate application note:
• Direct Connect and Dial-Up on Windows 98 Application Note
(LIT-6893350)
• Direct Connect and Dial-Up on Windows NT Application Note
(LIT-6893400)
• Direct Connect and Dial-Up on Windows 2000 Application Note
(LIT-6893450)
If connecting to the N30 through an Ethernet Local Area Network
(LAN), also see the N30 Supervisory Controller Networking Technical
Bulletin (LIT-6891300).
Logging On to an N30
To log on to an N30:
1. Start your VT100 Emulator or turn on your VT100.
2. Press Enter when the N30 name appears at the top of the screen.
The Login screen appears (Figure 3-3).
Commanding Objects
To command objects, the N30 device with the objects you are
commanding must be online. Therefore, you can command objects
using a VT100 or an M-Series Workstation but not while using an
offline tool such as Project Builder.
To command objects:
1. Browse to and highlight an object.
2. Press the F2 (Command) key. The Command field appears
(Figure 3-14).
N30 Supervisory Controller User’s Manual 3-25
Displaying a Summary
To display a summary:
1. Browse to and highlight the Summary container.
2. Press the Spacebar to expand the list of Summaries.
3. Highlight a Summary.
4. Press the F2 (Command) key.
5. Use the Spacebar and Backspace keys to cycle through the list
until the Display command appears (Figure 3-15).
3-26 N30 Supervisory Controller User’s Manual
Printing a Summary
To print a summary:
1. Browse to and highlight the Summary container.
2. Press the Spacebar to expand the list of Summaries.
3. Highlight a Summary.
4. Press the F2 (Command) key.
5. Use the Spacebar and Backspace keys to cycle through the list
until Print appears (Figure 3-17).
6. Use the arrow keys or Tab key to highlight the Destination field.
7. Use the Spacebar and Backspace keys to cycle through the list
until the desired printer appears.
8. Press Enter.
Changing an IP Address
Notes: Before performing the following steps, have the necessary
Internet Protocol (IP) Addresses available.
If the network uses Bootstrap Protocol (BOOTP), you can
allow the N30 to obtain its own IP address by setting its
BOOTP Enabled attribute to true and by configuring the
BOOTP server to assign an IP address. See the N30 Device
(LIT-694610) chapter in the Object Dictionary and the
N30 Supervisory Controller Networking Technical Bulletin
(LIT-6891300) for more information.
To change an IP address using a VT100:
1. Browse to and highlight an N30.
2. Press Enter to open the N30 Device object. Figure 3-7 shows the
N30 Device object named South Building after it has been
opened.
3. Press the F3 (Edit) key. The first of two N30 Device object
attribute screens appears (Figure 3-8).
4. Use the arrow keys to move the cursor to IP Address.
5. Press Enter. The IP Address list appears (Figure 3-18).
Rebinding a Site
To rebind a site:
1. Browse to and highlight an N30.
2. Press Enter to open the N30 Device object.
3. Press the F2 (Command) key.
4. Use the Spacebar and Backspace key to cycle through the list until
Rebind Site appears.
5. Press Enter.
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:
• add an Operator object
• edit an Operator object
• command an Operator object
• change any Operator password
• change the ADMIN password
• delete an Operator object
Key Concepts
Operator Object
Added for each user in a site and configured according to the access
the user needs or requires for certain object categories. For instance, a
Security Guard’s Operator object allows the viewing of Security
objects, whereas the Building Manager’s Operator object allows the
adding and deleting of HVAC objects.
Administrator
The only user of a site with the ability to create, modify, or delete
operator objects. With the exception that the administrator cannot
change an Operator password after its initial creation, the administrator
has unrestricted access to and control over all other objects defined for
the site.
The administrator’s Login ID is ADMIN and the default password
is 2468. The user assigned it is responsible for changing the
administrator password for their site and keeping it recorded in a
secure place.
Because an administrator is the only user with access to Operator
objects, he or she is the only user who can issue commands, such as
Enable and Disable, to these objects.
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.
3. Minimize the chance of users losing their ability to log into a site
due to a single N30 device breakdown.
• Designating one of the N30 devices on the site as the Copy
Holder device ensures the maintenance of a copy of each
non-administrative Operator object defined in the site.
• A user attempting to log in whose Operator object resides in a
non-operational N30, automatically has his or her login ID and
password entry verified against the copy of his Operator object
maintained in the site’s Copy Holder device.
N30 Supervisory Controller User’s Manual 4-5
Site
Manager
N30
VT 100
Standalone N30 Configuration
Site Copy
Manager Holder
Site Copy
Manager Holder
VT 100 VT 100
Site Copy
Manager Holder
N30 N30 N30
VT 100
VT 100 VT 100
Attributes
The values of an object’s attributes determine how the object operates.
The Operator object attributes described below are listed in the order
that they appear on the screen.
For additional information about the Operator object and its attributes,
refer to the Object Dictionary.
Object Name
Identifies the object on the user interface. For the Operator object, the
Login ID is the object name.
Description
Provides optional information to further describe the object.
Object Type
Indicates the kind of object, such as Schedule, N2 Analog Input, or
Operator.
Object Category
Determines the general classification of an object to help define user
access capability and message routing.
Enabled
Determines whether the user associated with a specific Operator object
can log on to the site. True indicates that the user can log on to the site;
False indicates that a user cannot log on to the site.
Password
Determines the password that a specific user must enter to log on to
the site. The Password must be a number of characters equal to or
greater than the Minimum Password Length defined for the site by the
Site Data object. The Password is case sensitive.
User ID
Appears as a string output on a printed status report and identifies the
user that has acknowledged an alarm.
Login ID
Determines the Login ID that a specific user must enter to log on to the
site. The Login ID may be up to 32 characters long.
User Group
Determines which Group object (if any) appears directly under the
main container on the main N30 screen. Once the Group is added to
the Group container, the exact name of a Group object must be entered
in the User Group field of an Operator object, in order for that Group
object to appear directly under the main container whenever that user
logs in.
For more information regarding User Group, refer to the Working with
Group Objects (LIT-6892060) chapter of this document.
Timeout
Indicates the amount of time that must elapse before a VT100 session
expires due to no keyboard activity.
Acknowledge
Specifies if the user has the ability to recognize alarm reports. Alarm
reports may be routed to terminals being used.
Display Units
Defines which units are used for display when the operator is logged
in.
User Capability
Dictates the user’s relative degree of access, such as Configure,
Modify, etc., for each of the site’s five object categories.
The five object categories for which the user must have an access level
defined are identified in Table 4-2. Since non-administrative users
have no access to objects in the Administrative category, the entry for
this category defaults to No Access, and the Administrative field is not
accessible from the VT100. The administrator receives a default access
level of Configure to all five object categories.
Table 4-2: Object Categories
Category Description
HVAC Categorizes an object as relating to Heating, Ventilating and
Air Conditioning functions.
Fire Categorizes an object as relating to Fire functions.
Security Categorizes an object as relating to Security functions.
Services Categorizes an object as relating to Services functions.
Administrative Categorizes an object as relating to Administrative functions.
Only Operator objects can be categorized as Administrative and
only the site administrator can access these objects.
4-10 N30 Supervisory Controller User’s Manual
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.
Procedure Overview
Table 4-4: Working with Operator Objects
To Do This Follow These Steps:
Add an Operator Object Browse to and highlight the Operators container. Press the F3 (Add) key.
Highlight Operator and press Enter. Fill in the fields using Table 4-5.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit an Operator Object Browse to and highlight an Operator object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 4-5. Press the
F3 (Save) key to save the changes. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Command an Operator Object Browse to and highlight an Operator object. Press the F2 (Command)
key. Use the Spacebar and the Backspace key to cycle through the list
until the desired command appears. Press Enter.
Changing Any Operator Log on to the N30 using the login ID and password of the user whose
Password password is to be changed. Browse to and expand the Operators
container. Highlight the Operator object. Press the F2 (Command) key.
Use the Spacebar and the Backspace key to cycle through the list until
Change Password appears. Press Enter to move to the next field.
Pressing the Tab or down arrow key also moves the cursor to the next
field. In the New Password field, type a new password. Press Enter to
move to the next field. Type the password again in the Confirm New
Password field. Press Enter.
Change the ADMIN Password Log on to the N30 using the ADMIN login ID and password. In the
N30 device object designated as the Site Manager, expand the Internals
container. Highlight the Operator object named site name.Operator {1}.
Press Enter to open the object. Press the F2 (Command) key. Press
Enter to move to the next field. Pressing the Tab or down arrow key also
moves the cursor to the next field. In the New Password field, type a new
password. Press Enter to move to the next field. Type the password again
in the Confirm New Password field. Press Enter.
Delete an Operator Object Browse to and highlight an Operator object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 4-13
Detailed Procedures
Adding an Operator Object
Note: The Administrator of the site is the only user who can add an
Operator object.
To add an Operator object:
1. Browse to and highlight the Operators container.
2. Press the F3 (Add) key. The Add Objects list appears.
3. Highlight Operator and press Enter. The Operator object attribute
screen appears (Figure 4-3).
4. Press Enter.
4-16 N30 Supervisory Controller User’s Manual
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.
Key Concepts
VT100 Object
The VT100 object performs three primary functions:
• provides the means for users to observe VT100 data and status, and
identify it as a target device for alarms and summaries.
• handles unsolicited messages directed from objects, such as alarm
messages and Summaries.
• supports the relationship to the Serial Datalink object that manages
dial connections and line status conditions.
The VT100 object provides support for VT100 Terminals as well as
VT100 Terminal Emulators running on a standard computer.
The VT100 object’s attributes allow a user to configure a variety of
filters that establish the type of messages, or Status Notification
Reports (SNR), which the VT100 object receives. For more
information about determining filter configurations, refer to
Appendix B: Building a Message Router Application (LIT-6892320) in
this document.
Attributes
The values of an object’s attributes determine how the object operates.
The VT100 object attributes described below are listed in the order
that they appear on the screen. Entry requirements for these attributes
are in Table 5-2.
For additional information about the VT100 object and its attributes,
refer to the Object Dictionary.
Object Name
Identifies the object on the user interface.
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.
N30 Supervisory Controller User’s Manual 5-3
Active Filter
Selects the type of filtering in effect for this VT100 destination. The
filter types are as follows:
• Pass None - When selected, this destination receives no alarm
messages.
• Pass All - When selected, this destination receives all alarm
messages.
• Filter A - This destination receives alarm messages based on
settings of Filter A.
• Filter B - This destination receives alarm messages based on
settings of Filter B.
• Filter A and B - This destination receives alarm messages based
on settings of Filter A and B.
Priority Filter A
Defines which priorities the destination receives when Filter A is in
effect. A value of True for a particular selection means that messages
of that defined priority reach this destination. Choices from highest to
lowest priority are Critical, Serious, Important, and Status.
Category Filter A
Defines which categories of messages the destination receives when
Filter A is in effect. This filter has no effect for alarm messages
without a defined object category. A value of True for a particular
selection means that messages of that defined object category reach
this destination.
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 N30 Supervisory Controller User’s Manual
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.
Port Number
Identifies the port where the VT100 Terminal is connected.
N30 Supervisory Controller User’s Manual 5-5
Procedure Overview
Table 5-1: Working with VT100 Objects
To Do This Follow These Steps:
Edit a VT100 Object Browse to and highlight the VT100 object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields using Table 5-2. Move the cursor to
the next field (Priority Filter A). Press Enter. Use the Spacebar and
Backspace key to view and select True or False for the first available
option. Press the down arrow key to move to the next option. Enter values
for all of the options. Press F4 (Back) to return to the attribute screen.
Edit all fields. Press the F3 (Save) key. Check the User Assistance area
of the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
5-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Editing a VT100 Object
To edit a VT100 object:
1. Browse to and highlight a VT100 object.
2. Press Enter to open the object.
Note: Additional attributes appear. Refer to the Object Dictionary
for more information.
3. Press the F3 (Edit) key. The VT100 object attribute screen appears
(Figure 5-1).
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.
N30 Supervisory Controller User’s Manual 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:
• add a Group object
• edit a Group object
• add object references to a Group object
• delete object references from a Group object
• delete a Group object
• create a Site Group
• create a User Group
Key Concepts
Group Object
An organizational tool that organizes and displays site information
according to specific needs. For example, a Group object can display
information by floors, sections, all zone temps, etc. These
representations are independent of the devices themselves. This allows
users to define site hierarchies differently than the default organization
by N30 device.
Groups can reference any object, collection of objects, or other groups.
By referencing groups from inside of other groups a full or partial site
hierarchy can be built. The flexibility of the Group object allows for
multiple custom hierarchies defined for use by different users or
different job functions.
More than one Group object can reference a single object in the site.
Multiple points in the hierarchy can access the same object
information. Each object in the site, however, is not required to be
referenced within a group. View, edit, and command objects in the
groups using the same operations available for the other containers in
the site hierarchy. If changes are made to an object from within the
Group object, these changes are reflected in the object wherever it is
accessed from.
A total of 75 objects or groups can be added per group and up to
seven consecutive levels of Group objects can be added within any
other container or object or group.
Site Group
The site can have a particular Site Group appear at the top level of the
site hierarchy when any user logs in.
First, add a Group object under the Group container. Then the name of
this group is inserted into the Site Group Object field of the Site Data
object. A Site Group contains any information important to a site and
that needs to be easily accessed. Figure 6-1 shows an example of a Site
Group named OVERVIEW GRP. This procedure is described in the
Detailed Procedures section of this chapter.
N30 Supervisory Controller User’s Manual 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 user’s Operator
object.
Creating a User Group allows users to customize their container
hiearchy. For instance, a particular Facility Manager may need to
check temperatures and setpoints on a daily basis. By creating a Group
object containing this information (named Maintenance) under the
Group container and then making sure to enter the name of this Group
(Maintenance) in the User Group attribute field of the Facility
Manager’s own Operator object, a group of vital information is created
at the top of the container hierarchy that eliminates the need to browse
any further after logging in. Figure 6-2 is an example of a User Group.
This procedure is described in the Detailed Procedures section of this
chapter.
If both a User Group and Site Group are defined and that particular
operator is logged in, the User Group appears first, and then the Site
Group followed by the remainder of the site hierarchy.
For more information about the Operator object, refer to the Working
with Operator Objects (LIT-6892030) chapter of this document.
6-4 N30 Supervisory Controller User’s Manual
Attributes
The values of an object’s attributes determine how the object operates.
The Group object attributes described below are listed in the order that
they appear on the user interface.
For additional information about the Group object and its attributes,
refer to the Object Dictionary.
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 object’s
meaning relative to the group that it is in. The label names within a
given group must be unique from all other labels in that group.
N30 Supervisory Controller User’s Manual 6-5
Procedure Overview
Table 6-1: Working with Group Objects
To Do This Follow These Steps:
Add a Group Object Browse to and highlight the Group container. Press the F3 (Add) key.
Highlight Group and press Enter. Fill in the fields using Table 6-2. Move
the cursor to Child List. Press Enter. Type in the exact name of an object
to be added to the new Group object. Press F3 (Add Item) to add a blank
entry for another object. Press F4 (Back) key. Press F3 (Save) key to
save the object. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Group Object Browse to and highlight a Group object. Press Enter to open the object.
Press F3 (Edit) key. Move the cursor to Child List. Press Enter. Make any
necessary changes (correct an object or label name). Press the F4 (Back)
key. Press the F3 (Save) key to save the changes. Check the User
Assistance area of the screen to verify if the save was successful or if
there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Add Object References to a Browse to and highlight a Group object. Press Enter to open the object.
Group Object Press the F3 (Edit) key. Move the cursor to Child List. Press Enter. Press
the F3 (Add Item) key to add a blank entry. Type in the exact name of an
object to be added to the Group object. Press F3 (Add Item) to add a
blank entry for another object. Press the F4 (Back) key. Press the
F3 (Save) key to save the changes. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Delete Object References from Browse to highlight a Group object. Press Enter to open object. Press
a Group Object F3 (Edit) key. Move the cursor to Child List. Press Enter. Highlight either
the Reference Name or Label of an object and press the F2 (Del Item)
key. Press the F4 (Back) key. Press the F3 (Save) key to save the
changes. Check the User Assistance area of the screen to verify if the
save was successful or if there were errors. Press any key to continue.
Press the F4 (Cancel) key to return to the container hierarchy.
Delete a Group Object Browse to and highlight a Group object. Press Enter to open the object.
Press the F3 (Edit) key. Move the cursor to Child List. Press Enter. Press
F2 (Del Item) key until all of the objects in the Child List are deleted. Press
the F4 (Back) key. Press the F3 (Save) key to save the changes. Check
the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
Delete key. Press the Tab key to confirm the deletion.
Create a Site Group In the Group container, add a Group object with the desired Child List
members. Write down the name of this new group. Browse to and expand
the Site Data object. Press the F3 (Edit) key. Move the cursor to the Site
Group Object field. Type in the name of this new group. Press the
F3 (Save) key. Press any key to continue. Log out and log in for the
changes to take effect. Check the container hierarchy to verify that the
Site Group appears.
Create a User Group In the Group container, add a Group object with the desired Child List
members. Write down the name of this new group. Edit the appropriate
Operator object by entering the exact name of this new group in the User
Group field. Log out and log in the VT100 with the appropriate Login ID
and Password for the edited Operator object. Check the container
hierarchy to verify that the User Group appears.
6-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Group Object
Note: When adding objects to a Group object it is helpful to have a
list of the exact names of the objects to be added.
To add a Group object:
1. Browse to and highlight the Group container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Group and press Enter. The Group object attribute
screen appears (Figure 6-3):
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.
Figure 6-5: Site Group Object field – Site Data Object Attribute Screen
7. Type in the name of this new group.
8. Press the F3 (Save) key.
9. Press any key to continue.
10. Log out and log in for the changes to take effect.
11. Check the container hierarchy to verify that the Site Group
appears (Figure 6-1).
6-12 N30 Supervisory Controller User’s Manual
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:
• create a new Schedule object
• edit a Schedule object
• delete a Schedule object
• command a Schedule object
For information on creating and editing Schedule objects in Project
Builder, see the Project Builder User’s Guide. For information on
viewing and editing Schedules using M-Schedule, see the
M-Schedule/M-Calendar User’s Guide.
Key Concepts
Schedule Object
The Schedule object updates the attribute values of objects according
to the time of day. The Schedule object allows for flexible selection of
dates on which to run the Schedule. These times can be specified for
days of the week and exception days. The exception days can be
defined as specific dates, ranges of dates, or days for which a given
Calendar object is defined. See Table 7-7 for a list of exception types.
The Schedule object is compatible with the BACnet Schedule object.
All required and optional attributes of the BACnet Schedule object are
supported. Some proprietary attributes have been added to the N30 to
extend the functionality of the Schedule object. The Schedule object is
added to the Schedule container in an N30 database.
Attributes
The values of an object’s attributes determine how the object operates.
The Schedule object attributes described below are listed in the order
that they appear on the screen.
For additional information about Schedule object and its attributes
refer to the Object Dictionary.
Object Name
Identifies the object on the user interface. This is the name the user
sees when viewing the database.
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.
N30 Supervisory Controller User’s Guide 7-3
Weekly Schedule
Contains one element for each day of the week, where element
1=Monday, 2=Tuesday, . . . 7=Sunday. Each element contains a list of
the times and corresponding values for the Schedule object to write to
the scheduled objects. The exception schedules override the times in
this weekly schedule.
Exception Schedule
Contains a list of exceptions to the times listed in the weekly schedule.
The exceptions can be based on a specific date, a date range, a
calendar reference, or a week/day selection. The Schedule object
automatically deletes date or range type of exceptions that expired
31 days ago. All four types of exceptions also contain the times and
corresponding values for the Schedule object to write to the scheduled
objects on those exceptions. The exceptions are also prioritized
1 . . . 16, with 1 being the highest priority. If multiple exceptions apply
for a given day, then the exception with highest priority is in effect.
If multiple exceptions apply for the current day and have the same
priority, then the first of these in the list is in effect. The week/day
selection can be used to identify particular days of the week, months of
the year, etc.
Effective Period
Gives the range of dates that the Schedule object is active. By default,
these dates are unspecified (blank), causing the Schedule object to be
active for all days. Refer to Wildcard Date Fields in this chapter for
further details.
Present Value
Indicates the current value of the Schedule object. This is the value
most recently written to a referenced object attribute, listed in the List
of Prop Refs attribute. A blank Present Value field in a Schedule
object indicates that the schedule has not reached a scheduled time
since the object was created (or since the last device restart).
7-4 N30 Supervisory Controller User’s Manual
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.
Single Date
For a single date, a wildcard opens a particular field to the full range of
possible values for that field. Table 7-1 describes the meaning of a
wildcard in each of the four date fields.
Table 7-2 shows some sample wildcard dates and their meanings.
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.
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.
N30 Supervisory Controller User’s Guide 7-7
Procedure Overview
Table 7-5: Working with Schedule Objects
To Do This: Follow These Steps:
Create a New Schedule Object Add a Schedule object - Browse to and highlight the Schedule container.
Press the F3 (Add) key. Highlight Schedule and press Enter. Fill in the
fields using Table 7-6. Press the F3 (Save) key. Check the User
Assistance area of the screen to verify if the save was successful or if
there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Add to a List of Prop Refs - Browse to and highlight a Schedule object.
Press Enter. Press the F3 (Edit) key. Move the cursor to the List of Prop
Refs. Press Enter. In the Object Name field that is highlighted, type the
exact name of the object to be scheduled. Press Enter. Move the cursor
to the Attribute field for that object. Use the Spacebar and Backspace
keys to cycle through the list of attributes until the desired attribute
appears. Press the F4 (Back) key. Press the F3 (Save) key. Check the
User Assistance area of the screen to verify if the save was successful or
if there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Add a Weekly Schedule - Browse to and highlight a Schedule object.
Press Enter. Press the F3 (Edit) key. Move the cursor to Weekly
Schedule. Press Enter. Use the Spacebar and Backspace keys to cycle
through the days of the week until the day you are scheduling appears.
Press the F3 (Add Item) key. Enter the time/value pair in the fields
displayed. Press the F4 (Back) key. Press the F3 (Save) key. Check the
User Assistance area of the screen to verify if the save was successful or
if there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Add an Exception Schedule - In the Schedule container, highlight a
schedule. Press Enter. Press the F3 (Edit) key. Move the cursor to the
Exception Schedule field. Press Enter. Press the Add Item (F3) key. Move
the cursor to Exception Type. Select an exception type . Enter values for
Date and Priority. Press the F4 (Back) key. Press the F3 (Save) key.
Check the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
F4 (Cancel) key to return to the container hierarchy.
Set an Effective Period for an Object - Browse to and highlight a
Schedule object. Press Enter. Press the F3 (Edit) key. Move the cursor to
Effective Period and press Enter. Enter the starting and ending dates the
Weekly schedule should be active. Press the F4 (Back) key. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Schedule Object Edit a List of Prop Refs - Browse to and highlight a Schedule object.
Press Enter. Press the F3 (Edit) key. Move the cursor to the List of Prop
Refs. Press Enter. Highlight the Object Name that you want to edit. Type
the exact name of the new object you want to schedule. Move the cursor
to the Attribute field for that object. Use the Spacebar and Backspace
keys to cycle through the list of attributes until the desired attribute
appears. Press the F4 (Back) key. Press the F3 (Save) key. Check the
User Assistance area of the screen to verify if the save was successful or
if there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Continued on next page . . .
7-8 N30 Supervisory Controller User’s Manual
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.
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.
N30 Supervisory Controller User’s Guide 7-13
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.
8. Use the Tab or arrow keys to move to the remaining fields. Either
type in all values, or use the number keys to enter dates and the
Spacebar and the Backspace key to change days and months.
Note: Pressing the F3 (Add) key at this point adds Time and Value
pairs to the Exception Schedule. Information on adding and
deleting Time and Value pairs is under the Editing Schedule
Objects section of this chapter.
9. Repeat Steps 6 through 8 for each new Exception Schedule.
10. Press the F4 (Back) key to return to the previous screen.
11. Press the F3 (Save) key.
12. Check the User Assistance area of the screen to verify if the save
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.
IMPORTANT: When entries are put in the List of Prop Refs and
saved, you can no longer edit the first entry in the list
(the object device). You cannot change an existing
Schedule object to schedule points on a different N30;
you must delete the entire schedule and add a new one.
To edit a List of Prop Refs:
1. Browse to and highlight the Schedule object.
2. Press Enter to open the object.
3. Press the F3 (Edit) key.
4. Move the cursor to List of Prop Refs.
5. Press Enter. The List of Prop Refs appears (Figure 7-2).
6. Highlight an Object Name that you want to edit.
7. In the Object Name field that is highlighted, type the exact name
of the object to be scheduled.
8. If the object is valid, use the arrow or Tab key to move the cursor
to the attribute field. If the object name is invalid, you receive an
Object not found message. If you receive this message, you
must retype a valid object name.
9. Use the Spacebar and Backspace keys to cycle through the list of
attributes until the desired attribute appears. The default value is
Present Value.
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.
7-18 N30 Supervisory Controller User’s Manual
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.
4. Press Enter.
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:
• add a Calendar object
• edit a Calendar object
• add Date List entries to a Calendar object
• delete Date List entries from a Calendar object
• command a Calendar object
• delete a Calendar object
For information on creating and editing Calendar objects in Project
Builder, see the Project Builder User’s Guide. For information on
viewing and editing Calendars using M-Calendar, see the
M-Schedule/M-Calendar User’s Guide.
Key Concepts
Calendar Object
The Calendar object maintains a list of dates designated as exceptions
to the normal schedule. A Schedule object working from a chosen
Calendar reads the Present Value of the Calendar object to determine
if the current day is within the Date List of the Calendar.
Single or multiple Schedule objects can work from the same Calendar
object, allowing a user to reference a defined Calendar object, such as
a holiday calendar, from any Schedule object. When a new day is
added to the Calendar object, all the schedules working from the
Calendar object are updated at the same time.
Attributes
The values of an object’s attributes determine how the object operates.
The Calendar object attributes described below are listed in the order
that they appear on the screen.
For additional information about the Calendar object and its attributes,
refer to Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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.
Single Date
For a single date, a wildcard opens a particular field to the full range of
possible values for that field. Table 8-1 describes the meaning of a
wildcard in each of the four date fields.
Table 8-2 shows some sample wildcard dates and their meanings.
8-4 N30 Supervisory Controller User’s Manual
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.
Procedure Overview
Table 8-5: Working with Calendar Objects
To Do This Follow These Steps:
Add a Calendar Object Browse to and highlight the Schedule container. Press the F3 (Add) key.
Highlight Calendar and press Enter. Fill in the fields using Table 8-6.
Move the cursor to Date List. Press Enter. Press the F3 (Add Item) key.
Use the Spacebar and Backspace key to view and select options and set
date parameters. Press the F3 (Add Item) key to add a blank entry. Press
the F4 (Back) key to return to the attribute screen. Press the F3 (Save)
key. Check the User Assistance area of the screen to verify if the save
was successful or if there were errors. Press any key to continue. Press
the F4 (Cancel) key to return to the container hierarchy.
Edit a Calendar Object Browse to and highlight a Calendar object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields using Table 8-6. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Date List Entries to a Browse to and highlight a Calendar object. Press Enter to open the object.
Calendar Object Press the F3 (Edit) key. Move the cursor to Date List. Press Enter. Press
the F3 (Add Item) key to add a blank entry. Use the Spacebar and
Backspace key to view and select options and set date parameters. Press
the F4 (Back) key to return to the attribute screen. Press the F3 (Save)
key. Check the User Assistance area of the screen to verify if the save
was successful or if there were errors. Press any key to continue. Press
the F4 (Cancel) key to return to the container hierarchy.
Delete Date List Entries from a Browse to and highlight a Calendar object. Press Enter to open the object.
Calendar Object Press the F3 (Edit) key. Move the cursor to Date List. Press Enter.
Highlight the calendar entry to be deleted. Press the F2 (Del Item) key.
Press the F4 (Back) key to return to the attribute screen. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Calendar Object Browse to and highlight a Calendar object. Press the F2 (Command) key.
Use the Spacebar and Backspace key to cycle through the list until the
desired command appears. Press Enter.
Delete a Calendar Object Browse to and highlight a Calendar object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 8-7
Detailed Procedures
Adding a Calendar Object
To add a Calendar object:
1. Browse to and highlight the Schedule container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Calendar and press Enter. The Calendar object attribute
screen appears (Figure 8-1).
8. Use the Spacebar and Backspace key to view and select options
and set date parameters. Refer to Table 8-1, Table 8-2, Table 8-3,
and Table 8-4.
9. Press the F3 (Add Item) key to add a blank entry.
10. Repeat Steps 8 and 9 until all Date List entries have been added.
11. Press the F4 (Back) key to return to the attribute screen.
12. Press the F3 (Save) key.
13. Check the User Assistance area of the screen to verify if the save
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.
4. Press Enter.
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:
• add an Optimal Start object
• edit an Optimal Start object
• command an Optimal Start object
• delete an Optimal Start object
Key Concepts
Optimal Start Object
The goal of Optimal Start is to reach either the Heating setpoint or
Cooling setpoint at occupancy. (The Optimal Start object selects the
appropriate setpoint depending on current temperature.) To meet this
goal, the Optimal Start object calculates:
• building Heating and Cooling constants that represent the rate at
which the temperature inside the building changes
• temperature differences between the Zone Temperature and the
Heating setpoint or Cooling setpoint
• how many minutes of precooling or preheating are required based
on the above difference
• optimal start time when the Zone WC (Warmup/Cooldown) Mode
object is controlled by the optimal start process
The Optimal Start object interacts with Schedule objects, N2 Binary
objects, and N2 Analog objects in an Optimal Start application. For
more information, refer to Appendix C: Building an Optimal Start
Application (LIT-6892330) in this document.
Optimal 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 N30 Supervisory Controller User’s Manual
Adaptation
Each day, at occupancy, the optimal start process adapts the building
Heating and Cooling Constant. It checks if the Zone Temperature
converged to within the edited temperature differential of the Heating
setpoint or Cooling setpoint. If the Zone Temperature did not
converge, the building Heating and/or Cooling Constants are
increased. This increase moves the optimal start time closer to the
earliest start time defined for the system. If the Zone Temperature
converges to within the edited Temperature Differential of the Heating
setpoint or Cooling setpoint prior to occupancy, the buildings Heating
and/or Cooling constants are decreased. This decrease moves the
optimal start time closer to the occupancy start time defined for the
system.
Attributes
The values of an object’s attributes determine how the object will
operate. The Optimal Start object attributes described below are listed
in the order that they appear on the screen.
For additional information about the Optimal Start object and its
attributes, refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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.
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 N30 Supervisory Controller User’s Manual
Temperature Units
Lists the units associated with the attributes for temperatures.
The default units of this attribute are determined by the default base
units attribute in the Device object. These attributes are:
• Cooling Design Temperature
• Heating Design Temperature
• Zone Temperature at Start
• Temperature Differential
Display Precision
Indicates the rounded position and decimal places to display for this
object.
Cooling Constant
Defines the rate at which the zone cools down after equipment startup.
If adaptation is enabled, this constant is adapted without user
intervention. If adapting and cooling and heating setpoints are the
same attribute, the cooling constant is adapted even if the mode
is not cooling, meaning both constants change.
Cooling Deadtime
Lists the time required after startup to lower the temperature by one
degree. The Optimal Start object’s algorithm adapts this value, if
adaptation is enabled. If adapting and cooling and heating setpoints are
the same attribute, the cooling deadtime is adapted even if the mode is
not cooling, meaning both deadtimes change.
Heating Constant
Defines the rate at which the zone heats up after equipment startup.
If adaptation is enabled, this constant is adapted without user
intervention. This attribute does not have a unit. If adapting and
cooling and heating setpoints are the same attribute, the heating
constant is adapted even if the mode is not heating, meaning both
constants will change.
9-8 N30 Supervisory Controller User’s Manual
Heating Deadtime
Lists the time required after startup to raise the temperature by one
degree. The Optimal Start object’s algorithm adapts this value, if
adaptation is enabled. If adapting and cooling and heating setpoints are
the same attribute, the heating deadtime is adapted even if the mode is
not heating, meaning both deadtimes change.
Present Value
Represents the current value of the object. Present Value appears to the
right of the object name in the container hierarchy after the object is
created.
Possible values are:
• Idle - Waiting for next occupied time for a supported mode
(heating or cooling).
• Prestart Heating – Heating Optimal Start time is pending.
• Prestart Cooling – Cooling Optimal Start time is pending.
• Calculating Deadtime – Valid only if Adaption Enabled.
• Calculating Constant – Valid only if Adaption Enabled.
• Occupied
• Prestop – Waiting to reach optimal stop time.
• Not Operational – Optimal Start object is not operational due to
errors in its connection status to other required objects. You can
determine the specific problem by viewing the other status
attributes. The Optimal Start object is Not Operational if the Zone
Occ Mode Obj attribute is in the schedule, but there are no valid
start and stop times for that day.
N30 Supervisory Controller User’s Manual 9-9
Procedure Overview
Table 9-2: Working with Optimal Start Objects
To Do This Follow These Steps:
Add an Optimal Start Object Browse to and highlight the Energy container. Press the F3 (Add) key.
Highlight Optimal Start and press Enter. Fill in the fields using Table 9-3.
Press the F3 (Save) key to save the object. Check the User Assistance
area of the screen to verify if the save was successful or if there were
errors. Press any key to continue. Press the F4 (Cancel) key to return to
the container hierarchy.
Edit an Optimal Start Object Browse to and highlight an Optimal Start object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 9-3. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command an Optimal Start Browse to and highlight an Optimal Start object. Press the F2 (Command)
Object key. Use the Spacebar or the Backspace key to cycle through the list until
the desired command appears. Press Enter.
Delete an Optimal Start Object Browse to and highlight an Optimal Start object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
9-10 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding an Optimal Start Object
To add an Optimal Start object:
1. Browse to and highlight the Energy container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Optimal Start and press Enter. The first of two Optimal
Start object attribute screens appears (Figure 9-1).
Note: Use the [ and ] keys to page to other screens.
4. Press Enter.
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:
• add a Temporary Occupancy object
• edit a Temporary Occupancy object
• command a Temporary Occupancy object
• delete a Temporary Occupancy object
Key Concepts
Temporary Occupancy Object Operation
Upon receipt of the temporary occupancy request, the Temporary
Occupancy object sends a write attribute message, at a higher priority
than the scheduling feature, to the specified object. The overridden
point then stays occupied until the timer expires, or the user cancels
the occupancy request.
Attributes
Present Value
This is the current state of the Temporary Occupancy object’s
occupancy timer. A value of Active means the timer is active, and a
value of Inactive means the timer is inactive.
Occupancy Time
This defines the requested time for the Output object to remain
occupied. The valid range is 1-65,535 minutes.
Time Remaining
This is the value in minutes of the remaining occupancy time for the
Output object.
Output Object
This contains the reference to a prioritized attribute of a given object
type in order to temporarily override that attribute.
Output Value
This is the value to be written to the Output Object, when the Present
Value attribute is set to Active.
States Text
This is a reference to the multistate set, which characterizes the Output
Value. The states text is obtained from the object/attribute specified in
the Output Object once a new Temporary Occupancy object is created.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 10-1: Working with Temporary Occupancy Objects
To Do This Follow These Steps:
Add a Temporary Occupancy Browse to and select the Schedule container. Press the F3 (Add) key.
Object Select Temp Occ. Press the Enter key. Fill in the fields using Table 10-2.
Press the F3 (Save) key. Press any key to continue. Press the
F4 (Cancel) key to return to the main screen.
Edit a Temporary Occupancy Browse to and select the object you want to edit. Press the Return key.
Object 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 Browse to and select the Temporary Occupancy object you want to
Occupancy Object command. Press the F2 (Command) key. Use the Spacebar and the
Backspace key to cycle to the desired command. Press the enter key.
Delete a Temporary Browse to and select the Temporary Occupancy object you want to
Occupancy Object delete. Press the Return key to open the object. Press the Delete key.
Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 10-5
Detailed Procedures
Adding a Temporary Occupancy Object
To add a Temporary Occupancy object:
1. Browse to and select the Schedule Container.
2. Press the F3 (Add) key.
3. Select Temp Occ from the list that appears.
4. Press the Enter key. The Temporary Occupancy object
configuration screen appears (Figure 10-1).
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.
Key Concepts
Printer Object
The Printer object provides hard copy output of the alarms, summaries,
and other reports generated by objects, features, and the system. The
Printer object is responsible for the buffering of output to the printer
device. Printers are either connected directly or connected through
dial-up access via modems.
The Printer object provides the interface to manipulate the printer
device and performs the following:
• Prints alarm messages from the Message Router object.
• Prints trend log data, summaries, and utility profile reports.
The Printer object’s attributes allow a user to configure a variety of
filters that establish the type of messages, or Status Notification
Reports (SNR), which the Printer object receives. For more
information about determining filter configurations, refer to
Appendix B: Building a Message Router Application (LIT-6892320) in
this document.
Attributes
The values of an object’s attributes determine how the object operates.
The Printer object attributes described below are listed in the order that
they appear on the screen. Entry requirements for these attributes are
in Table 11-2.
For additional information about the Printer object and its attributes,
refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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:
• Pass None - When selected this destination receives no alarm
messages.
• Pass All - When selected this destination receives all alarm
messages.
• Filter A - This destination receives alarm messages based on
settings of Filter A.
• Filter B - This destination receives alarm messages based on
settings of Filter B.
• Filter A and B - This destination receives alarm messages based
on settings of Filter A and B.
Priority Filter A
Defines which priorities 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.
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 N30 Supervisory Controller User’s Manual
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.
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.
Use Dial
Indicates remote connect printer or the direct connected printer. If this
attribute is set to True, the object is set for the remote connect printer.
If this attribute is set to False, the object is set for the direct connect
printer and the Phone Number can’t be changed from None.
Phone Number
Indicates the dial out phone number to printer device if a modem is
connected to the port. If a printer device is connected to the port
directly, this attribute should be blank.
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.
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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 11-1: Working with Printer Objects
To Do This Follow These Steps:
Add a Printer Object Browse to and highlight the Operator Devices container. Press the
F3 (Add) key. Highlight Printer and press Enter. Fill in the fields using
Table 11-2. Press the F3 (Save) key. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Edit a Printer Object Browse to and highlight a Printer object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields according to Table 11-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Printer Object Browse to and highlight a Printer object. Press the F2 (Command) key.
Use the Spacebar and the Backspace key to cycle through the list until
the desired command appears. Press Enter.
Delete a Printer Object Browse to and highlight a Printer object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 11-7
Detailed Procedures
Adding a Printer Object
To add a Printer object:
1. Browse to and highlight the Operator Devices container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Printer and press Enter. The first of two Printer object
attribute screens appears (Figure 11-1).
Note: Use the [ and ] keys to page to other screens.
4. Press Enter.
N30 Supervisory Controller User’s Manual 11-11
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:
• add a Modem Configuration object
• edit a Modem Configuration object
• delete a Modem Configuration object
Key Concepts
Modem Configuration Object
The Modem Configuration object serves as a named storage place for
modem configuration data. The user provides the specific dial-out
configuration data for this object and then other objects capable of
initializing a dial out connection refer to this data. A dial-out Printer
object typically uses the Modem Configuration object as a source of
data.
If the standard modem configuration string of the Serial Datalink
object (as defined by the N30 Device object) refers to incorrect
modem configuration data for a particular printer, the Printer object
can reference the Modem Configuration object for different modem
configuration data. When the default values of the Serial Datalink
object are sufficient, no Modem Configuration object is required.
Attributes
The values of an object’s attributes determine how the object operates.
The Modem Configuration object attributes described below are listed
in the order that they appear on the screen. Entry requirements for
these attributes are in Table 12-2.
For additional information about the Modem Configuration object and
its attributes, refer to Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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.
Number of Redials
Specifies the number of times the dialing connection is attempted.
12-4 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 12-1: Working with Modem Configuration Objects
To Do This Follow These Steps:
Add a Modem Configuration Browse to and highlight the Operator Devices container. Press the
Object F3 (Add) key. Highlight Modem Config and Press Enter. Fill in the fields
using Table 12-2. Press the F3 (Save) key. Check the User Assistance
area of the screen to verify if the save was successful or if there were
errors. Press any key to continue. Press the F4 (Cancel) key to return to
the container hierarchy.
Edit a Modem Configuration Browse to and highlight a Modem Configuration object. Press Enter to
Object open the object. Press the F3 (Edit) key. Edit the fields using Table 12-2.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Delete a Modem Configuration Browse to and highlight a Modem Configuration object. Press Enter to
Object open the object. Press the Delete key. Press the Tab key to confirm the
deletion.
N30 Supervisory Controller User’s Manual 12-5
Detailed Procedures
Adding a Modem Configuration Object
To add a Modem Configuration object:
1. Browse to and highlight the Operator Devices container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Modem Config and Press Enter. The Modem
Configuration Object attribute screen appears (Figure 12-1).
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:
• add a Global Data Sharing object
• edit a Global Data Sharing object
• add slaves to the Slaves List
• delete slaves from the Slaves List
• command a Global Data Sharing object
• delete a Global Data Sharing object
Key Concepts
Global Data Sharing Object
The Global Data Sharing feature distributes changes in value
associated with a single master input to a range of between one and
sixteen targeted slave outputs. For example, Outdoor Air data can be
distributed and shared between multiple Air Handling Unit controllers.
Attributes
The values of an object’s attributes determine how the object operates.
The Global Data Sharing object attributes described below are listed in
the order that they appear on the screen. Entry requirements for these
attributes are listed in Table 13-2.
For additional information about Global Data Sharing object and its
attributes, refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 13-3
Procedure Overview
Table 13-1: Working with Global Data Sharing Objects
To Do This Follow These Steps:
Add a Global Data Sharing Browse to and highlight the Programming container. Press the
Object F3 (Add) key. Highlight Global Data and press Enter. Fill in the fields
using Table 13-2. Move the cursor to Slave List. Press Enter. Type in an
object name and attribute name. Press the F3 (Add Item) key and type in
another slave. Press the F4 (Back) key. Press the F3 (Save) key.
Check the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
F4 (Cancel) key to return to the container hierarchy.
Edit a Global Data Sharing Browse to and highlight a Global Data Sharing object. Press Enter to
Object open the object. Press the F3 (Edit) key. Edit the fields using Table 13-2.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Slaves to the Slaves List Browse to and highlight a Global Data Sharing Object. Press Enter to
open the object. Press the F3 (Edit) key. Move the cursor to Slaves List.
Press Enter. Press the F3 (Add Item) key to add a blank entry. Type in an
object name and attribute name. Press the F4 (Back) key to return to the
previous screen. Press the F3 (Save) key to save the changes. Check the
User Assistance area of the screen to verify if the save was successful or
if there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Delete Slaves from the Slaves Browse to and highlight a Global Data Sharing Object. Press Enter to
List open the object. Press the F3 (Edit) key. Move the cursor to Slaves List.
Press Enter. Highlight the slave to be deleted. Press the F2 (Del Item)
key. Press the F4 (Back) key to return to the previous screen. Press the
F3 (Save) key to save the changes. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Command a Global Data Browse to and highlight a Global Data Sharing object. Press the
Sharing Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list until the desired command appears. Press Enter.
Delete a Global Data Sharing Browse to and highlight a Global Data Sharing object. Press Enter to
Object open the object. Press the Delete key. Press the Tab key to confirm
deletion.
13-4 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Global Data Sharing Object
To add a Global Data Sharing object:
1. Browse to and highlight the Programming container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Global Data and press Enter. The Global Data Sharing
attribute screen appears (Figure 13-1).
IMPORTANT: The system does not check to ensure that the master
(input) and the slaves (outputs) are mapped to the
same data type. Each slave attempts to convert the
value being received (if necessary) to the data type
defined for itself.
5. Move the cursor to Slaves List.
6. Press Enter. The Global Data Sharing object Slaves List appears
(Figure 13-2).
13-6 N30 Supervisory Controller User’s Manual
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.
4. Press Enter.
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:
• add an Interlock object
• edit an Interlock object
• add sources to an Interlock object
• delete sources from an Interlock object
• add action table entries to an Interlock object
• delete action table entries from an Interlock object
• command an Interlock object
• delete an Interlock object
Key Concepts
Interlock Object
The Interlock object establishes conditional control over one or more
other objects. It consists of IF conditional statements, True command
statements, and False command statements. Through these statements,
the user specifies a set of conditional checks. Based on the results of
those checks, a series of commands can control a collection of one or
more objects.
For example, the Interlock object is used to place a Variable Air
Volume (VAV) controller in the occupied mode whenever the main
fan is on and in the occupied mode.
The attributes of the Interlock object have to work together as well as
with other objects in order for the object to function properly.
The Source and Logic attributes determine the condition and the
Action Table defines the course of action (commands) to take based on
those conditions. For information about building an Interlock
application, refer to Appendix D: Building an Interlock Application
(LIT-6892340) in this manual.
Attributes
The values of an object’s attributes determine how the object operates.
The Interlock object attributes described below are listed in the order
they appear on the screen. Entry requirements for these attributes are
in Table 14-4.
For additional information about the Interlock object and its attributes,
refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s 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.
Logic
Specifies the Boolean (AND/OR) logic used in combination with the
Source input to deliver a True or False statement. Options include:
• Match All - Every condition must be true.
• Match Any - One or more of the conditions must be true.
• Complex - Use Logic Equation attribute for complex logic.
14-4 N30 Supervisory Controller User’s Manual
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.
Example
Figures 14-1 through 14-4 show screens from a sample completed
Interlock object. This sample object uses the Logic Equation attribute.
N30 Supervisory Controller User’s 14-5
Procedure Overview
Table 14-3: Working with Interlock Objects
To Do This Follow These Steps:
Add an Interlock Object Browse to and highlight the Programming container. Press the
F3 (Add) key. Select Interlock and press Enter. Fill in the fields using
Table 14-4. Move the cursor to Source. Press Enter. Type in the object
name. Press Tab to move to the next field. Use the Spacebar and
Backspace key to cycle through the list until the desired option appears.
Press the F3 (Add Item) key to add a blank entry. Press the F4 (Back) key
to return to the previous screen. Move the cursor to Logic. Fill in the field
using Table 14-4. If necessary, move the cursor to Logic Equation and fill
in the field. Move the cursor to True under Action Table. Press Enter.
Type in an object name. Press Tab to move to the next field. Fill in the
remaining fields. Press the F3 (Add Item) key to add a blank entry. Press
the F4 (Back) key to return to the previous screen. Move the cursor to the
next field (False). Press Enter. Type in an object name. Press Tab to
move to the next field. Fill in the remaining fields. Press the F3 (Add Item)
key to add a blank entry. Press the F4 (Back) key to return to the previous
screen. Press the F3 (Save) key. Check the User Assistance area of the
screen to verify if the save was successful or if there were errors. Press
any key to continue. Press the F4 (Cancel) key to return to the container
hierarchy.
Edit an Interlock Object Browse to and highlight an Interlock object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 14-4. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Sources to an Interlock Browse to and highlight an Interlock object. Press Enter to open the
Object object. Press the F3 (Edit) key. Move the cursor to Source. Press Enter.
Press the F3 (Add Item) key to add a blank entry. Type in an object name.
Press Tab to move to the next field. Use the Spacebar and Backspace
key to cycle through the list until the desired option appears. Press the
F3 (Add Item) key to add a blank entry. Press the F4 (Back) key to return
to the previous screen. Press the F3 (Save) key to save the changes.
Check the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
F4 (Cancel) key to return to the container hierarchy.
Delete Sources from an Browse to and highlight an Interlock object. Press Enter to open the
Interlock Object object. Press the F3 (Edit) key. Move the cursor to Source. Press Enter.
Highlight the source to be deleted. Press the F2 (Del Item) key. Press the
F4 (Back) key to return to the previous screen. Press the F3 (Save) key to
save the changes. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Action Table Entries to an Browse to and highlight an Interlock object. Press Enter to open the
Interlock Object object. Press the F3 (Edit) key. Move the cursor to True or False under
Action Table. Press Enter. Press the F3 (Add Item) key to add a blank
entry. Type in an object name. Press Tab to move to the next field. Fill in
the remaining fields. Press the F3 (Add Item) key to add a blank entry.
Press the F4 (Back) key to return to the previous screen. Press the
F3 (Save) key to save the changes. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Continued on next page . . .
14-8 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding an Interlock Object
To add an Interlock object:
1. Browse to and highlight the Programming container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Select Interlock and press Enter. The Interlock object attribute
screen appears (Figure 14-5).
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:
• add a Signal Select object
• edit a Signal Select object
• add input entries to a Signal Select object
• delete input entries from a Signal Select object
• command a Signal Select object
• delete a Signal Select object
Key Concepts
Signal Select
The Signal Select feature works with either analog or binary points,
and in Multi-Zone applications where values from multiple zones are
processed and used by the Air Handling Unit (AHU) to adjust various
setpoints.
With Signal Select, you can:
• determine the highest, lowest, and average values of a set of analog
input points.
• command analog points to the average, highest, or lowest values
calculated from a set of analog input points.
• calculate the state of a set of binary input points (using AND and
OR logical operations) and use the calculated value to command a
binary output point.
Attributes
The values of an object’s attributes determine how the object operates.
The Signal Select object attributes described below are listed in the
order that they appear on the screen. Entry requirements for these
attributes are in Table 15-3.
For additional information about the Signal Select object and its
attributes, refer to the Object Dictionary.
Object 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 N30 Supervisory Controller User’s Manual
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.
N30 Supervisory Controller User’s Manual 15-5
Procedure Overview
Table 15-2: Working with Signal Select Objects
To Do This Follow These Steps:
Add a Signal Select Object Browse to and highlight the Programming container. Press the
F3 (Add) key. Highlight Signal Select and press Enter. Fill in the fields
using Table 15-3. Move the cursor to Input List. Press Enter. Type in an
object and attribute name. Press the F3 (Add Item) key to add a blank
entry. Press F4 (Back) key to return to the previous screen. Fill in the
remaining fields using to Table 15-3. Press the F3 (Save) key. Check the
User Assistance area of the screen to verify if the save was successful or
if there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Edit a Signal Select Object Browse to and highlight a Signal Select object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 15-3. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Input Entries to a Signal Browse to and highlight a Signal Select object. Press Enter to open the
Select Object object. Press the F3 (Edit) key. Move the cursor to Input List. Press Enter.
Press the F3 (Add Item) key to add a blank entry. Type in an object and
attribute name. Press the F4 (Back) key to return to the previous screen.
Press the F3 (Save) key to save the changes. Check the User Assistance
area of the screen to verify if the save was successful or if there were
errors. Press any key to continue. Press the F4 (Cancel) key to return to
the container hierarchy.
Delete Input Entries from a Browse to and highlight a Signal Select object. Press Enter to open the
Signal Select Object object. Press the F3 (Edit) key. Move the cursor to Input List. Press Enter.
Highlight the input to be deleted and press F2 (Del Item) key. Press the
F4 (Back) key to return to the previous screen. Press the F3 (Save) key to
save the changes. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Signal Select Browse to and highlight a Signal Select object. Press the F2 (Command)
Object key. Use the spacebar and the Backspace key to cycle through the list
until the desired command appears. Press Enter.
Delete a Signal Select Object Browse to and highlight a Signal Select object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
15-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Signal Select Object
To add a Signal Select object:
1. Browse to and highlight the Programming container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Signal Select and press Enter. The Signal Select object
attribute screen appears (Figure 15-1).
4. Press Enter.
N30 Supervisory Controller User’s Manual 15-11
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:
• add an Auto Shutdown object
• edit an Auto Shutdown object
• command an Auto Shutdown object
• delete an Auto Shutdown object
An example of a use for the Auto Shutdown object is to prevent alarms
set to monitor the discharge air temperature of a fan when that fan is
turned off.
Key Concepts
Auto Shutdown Object
When a selected multistate control point is in a specified shutdown
state, the Auto Shutdown object suppresses alarm reporting from a list
of dependent objects to prevent nuisance alarms. This is accomplished
by sending an enable/disable command to each of the dependent
objects’ Alarm objects, based on the control point’s attribute reference
value and the shutdown state. A startup delay is provided so that points
are not released immediately from shutdown.
An example of a use for the Auto Shutdown object is to prevent alarms
set to monitor the discharge air temperature of a fan when that fan is
turned off. When the fan is turned off, the fan state value is sent to the
Auto Shutdown object. The Auto Shutdown object then evaluates the
Present Value (control point state) against the Shutdown State defined
in the Auto Shutdown object. If the Present Value matches the
Shutdown State, the Auto Shutdown object sends a Disable Command
to the Alarm Object of every referenced dependent object in the
Dependents list.
Consequently, when the fan is turned back on, the Auto Shutdown
object again evaluates the current state and, if the Present Value does
not match the Shutdown State, starts the Startup Delay timer. Once the
timer expires, the Auto Shutdown object sends an Enable command to
the Alarm Object of every referenced dependent object in the
Dependents list.
Note: Changing the Dependents attribute causes an immediate
reevaluation of the current state. However, changes to the
Startup Delay time do not take effect until the next change in
the Control Point state.
N30 Supervisory Controller User’s Manual 16-3
Auto Shutdown
Object
Are values
Shutdown State No Startup Delay
equal?
Yes
Yes
No
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 N30 Supervisory Controller User’s Manual
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.
N30 Supervisory Controller User’s Manual 16-5
Procedure Overview
Table 16-1: Working with Auto Shutdown Objects
To Do This Follow These Steps:
Add an Auto Shutdown Object Browse to and highlight the multistate point for
which you want to suppress alarm reporting.
Press the F3 (Add) key. Select Auto Shutdown
from the list of objects that appears. Press
Enter. Enter an object name and description.
Under Engineering Values, add the Control
Point attribute reference and at least
one dependent object reference. Press the F3
(Save) key. Press any key to continue. Press
F4 (Cancel) to return to the main screen.
Edit an Auto Shutdown Object Browse to and select the Auto Shutdown
object that you want to edit. Press the Enter
key to open the object. Press the F3 (Edit) key.
Edit the fields as desired. Press the F3 (Save)
key. Press any key to continue. Press the F4
key to return to the main screen.
Command an Auto Shutdown Browse to and select the Auto Shutdown
Object object that you want to command. Press the
F2 (Command) key. Use the spacebar and
Tab keys to select either Enable or Disable.
Press the Enter key to execute the selected
command.
Delete an Auto Shutdown Browse to and select the Auto Shutdown
Object 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.
N30 Supervisory Controller User’s Manual 16-7
Detailed Procedures
Adding an Auto Shutdown Object
To add an Auto Shutdown object:
1. Browse to and highlight the object containing the multistate point
for which you want to suppress alarm reporting.
2. Press the F3 (Add) key.
3. Select Auto Shutdown from the list of objects that appears.
4. Press Enter. The Auto Shutdown object configuration screen
appears (Figure 16-4).
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:
• add a Multiple Command object
• edit a Multiple Command object
• add Action Table entries to a Multiple Command object
• delete Action Table entries from a Multiple Command object
• command a Multiple Command object
• delete a Multiple Command object
Key Concepts
Multiple Command Object
The Multiple Command object issues a series of commands to multiple
objects with a single command action. Commanding the Multiple
Command object results in the execution of the commands for a given
state. It supports States 1-32.
A possible use of the Multiple Command object involves using one
command to start building controls for the day. For instance, a
Multiple Command object can be added with three states using
Occupancy mode states text (Unoccupied, Occupied, and Startup).
When the building is in Unoccupied mode, the Multiple Command
object can turn off fans, lower the setpoint to 60°F, and secure the
doors of the building. During the Startup mode, the Multiple
Command object can unlock doors, and start boiler circulating pumps.
When in Occupied mode, the Multiple Command object can turn on
fans and raise setpoints to 72°F.
Another possible use for the Multiple Command object involves using
one command to run fan sequencing-type operations. For instance, a
number of fans listed in the Action Table attribute start sequentially at
one minute intervals by setting the Delay accordingly. The Delay time
is cumulative, so if a one minute delay between each fan start is
desired, then the Delay times would be 0, 60 120, 180 minutes, etc.
Attributes
The values of an object’s attributes determine how the object operates.
The Multiple Command object attributes described below are listed in
the order that they appear on the screen. Entry requirements for these
attributes are in Table 17-2.
For additional information about the Multiple Command object and its
attributes, refer to Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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.
Procedure Overview
Table 17-1: Working with Multiple Command Objects
To Do This Follow These Steps:
Add a Multiple Command Browse to and highlight the Programming container. Press the
Object F3 (Add) key. Highlight Multiple Command and press Enter. Fill in the
fields using Table 17-2. Move the cursor to State 0 under Action Table.
Press Enter. Type in an object name. Press the Tab key or the down
arrow key to move to the next field. Type in or choose the required
information. Press the F3 (Add Item) key to add a blank entry. Press the
F4 (Back) key to return to the previous screen. Move the cursor to the
next State. Press the F3 (Save) key. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Edit a Multiple Command Browse to and highlight a Multiple Command object. Press Enter to open
Object the object. Press the F3 (Edit) key. Edit the fields using Table 17-2. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Add Action Table Entries to a Browse to and highlight a Multiple Command object. Press Enter to open
Multiple Command Object the object. Press the F3 (Edit) key. Move the cursor to the appropriate
State under Action Table. Press Enter. Press the F3 (Add Item) key to
add a blank entry. Type in an object name. Press the Tab key or the down
arrow key to move to the next field. Type in or choose the required
information. Press the F3 (Add Item) key to add a blank entry. Press the
F4 (Back) key to return to the previous screen. Move the cursor to the
next State, if necessary. Press the F3 (Save) key. Check the User
Assistance area of the screen to verify if the save was successful or if
there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Delete Action Table Entries Browse to and highlight a Multiple Command object. Press Enter to open
from a Multiple Command the object. Press the F3 (Edit) key. Move the cursor to the appropriate
Object State under Action Table. Press Enter. Highlight any field for the object
reference to be deleted. Press the F2 (Del Item) key. Press the
F4 (Back) key to return to the previous screen. Move the cursor to the
next state, if necessary. Press the F3 (Save) key. Check the User
Assistance area of the screen to verify if the save was successful or if
there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Command a Multiple Browse to and highlight a Multiple Command object. Press the
Command Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list until the desired command appears. Press Enter.
Delete a Multiple Command Browse to highlight a Multiple Command object. Press Enter to open the
Object object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 17-5
Detailed Procedures
Adding a Multiple Command Object
To add an Multiple Command object:
1. Browse to and highlight the Programming container.
2. Press the F3 (Add) key. The Add Objects list appears.
3. Highlight Multiple Command and press Enter. The Multiple
Command object attribute screen appears (Figure 17-1).
Chapter 18
Introduction
The Data Broadcast object provides a means of sharing globally
important data with third-party BACnet devices.
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
object’s attribute value, if reliable, is then broadcast in an
Unconfirmed COV Notification message.
Reliability
The reliability of the Data Broadcast object. The reliability changes to
Input Unreliable when errors occur with the Input Reference.
Message Transmits
This attribute provides a count of the number of Unconfirmed COV
Notification messages that have been sent by the Data Broadcast
object. The value rolls over to 0, and continues counting, after
reaching 4,294,967,295.
Status
The Data Broadcast object sets the Status attribute to
OS_UNRELIABLE under any of the following conditions:
• The Reliability attribute is set to a value other than RELIABLE.
• There is a communications problem with the input reference.
• The input reference attribute data type does not support sign up.
N30 Supervisory Controller User’s Manual 18-3
Procedure Overview
Table 18-1: Working with Data Broadcast Objects
To Do This Follow These Steps:
Add a Data Broadcast Object Browse to and highlight the container where you want to add the Data
Broadcast Object. Press the F3 (Add) key. Select Data Broadcast from
the list of objects that appears. Press Enter.
Edit a Data Broadcast Object Browse to and select the Data Broadcast object that you want to edit.
Press the Enter key to open the object. Press the F3 (Edit) key. Edit the
fields as desired. Press the F3 (Save) key. Press any key to continue.
Press the F4 key to return to the main screen.
Command a Data Broadcast Browse to and select the Data Broadcast object that you want to
Object command. Press the F2 (Command) key to open the Command field. Use
the Spacebar and Tab keys to select either Enable or Disable. Press
Enter.
Delete a Data Broadcast Browse to and select the Data Broadcast object that you want to delete.
Object 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 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Data Broadcast Object
To add a Data Broadcast object:
1. Browse to and highlight the object for which you want to
broadcast a value from one of its attributes.
2. Press the F3 (Add) key.
3. Select Data Broadcast from the list of objects that appears.
4. Press Enter. The Data Broadcast object configuration screen
appears (Figure 18-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:
• add a DLLR object
• edit a DLLR object
• command a DLLR object
• delete a DLLR object
Key Concepts
Demand Limiting/Load Rolling Controller Object
The Demand Limiting/Load Rolling (DLLR) Controller object reduces
utility expenses by selectively shedding loads.
Demand limiting reduces energy costs by turning off designated
equipment when the amount of energy consumed by the facility
approaches a specified target. The purpose of demand limiting is to
keep the demand for energy at one time below this target. This reduces
energy costs because utility companies often determine charges by the
day’s peak demand for energy.
Load rolling reduces energy consumption by repeatedly turning off
designated equipment at specified intervals. For example, instead of
running a fan continuously, load rolling can save energy by turning the
fan off for 15 minutes every hour.
The DLLR object is the heart of the DLLR feature. The DLLR
algorithm inside the DLLR object determines the necessary power
reduction to meet the specified target. Power reduction is
accomplished by shedding loads. Shedding loads is done by advising
the associated loads to switch off their associated outputs, which then
leads to the actual physical shedding of loads causing the desired
power reduction.
Shedding
The process of turning off equipment for Demand Limiting/Load
Rolling.
Releasing
The process of turning on equipment shed by Demand Limiting/Load
Rolling.
N30 Supervisory Controller User’s Manual 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.
Load Objects
The Loads sign up for Change-of-Value (COV) on the DLLR’s
DLLR Status attribute. This attribute informs the loads about the
current state of their DLLR. The DLLR can enter the Register mode
by setting DLLR Status temporarily to Register, which causes the
signed up loads to register.
The DLLR signs up for trigger on some internal attributes of the
Loads, which allows the DLLR to be constantly informed about the
eligibility of Loads to be used as sheddable Loads. Which and how
many attributes are used for this purpose must be determined after the
overall system communication performance is evaluated.
N30 Supervisory Controller User’s Manual 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:
• A permanent communication path must exist between the meter
object and the DLLR.
• The meter object must calculate a new rate exactly once every
60 seconds.
• This rate must be the average power over the just elapsed minute
and must be provided in the meter object’s Present Value attribute,
which has to support signup for COV.
• The meter object’s Rate Units must be identical to the DLLR’s
Rate Units.
EOI Attribute
Note: The use of an End-of-Interval (EOI) input is required for the
Fixed Window Algorithm only. It must not be used for the
Sliding Window Algorithm.
The attribute supplying the End-of-Interval pulse is defined by the
attribute reference entered in the DLLR’s EOI attribute. This EOI
attribute can be any attribute of any object, as long as the following
requirements are met:
• A permanent communication path must exist between this attribute
and the DLLR.
• This attribute must be a numerical attribute, where a raise from
0 to 1 indicates the end of the interval, and thus, the beginning of
the next interval.
• The object providing this attribute must support signup for trigger
on this attribute.
19-6 N30 Supervisory Controller User’s Manual
Attributes
The values of an object’s attributes determine how the object operates.
The DLLR object attributes described below are listed in the order that
they appear on the screen. Entry requirements for these attributes are
in Table 19-2.
For additional information about the DLLR object and its attributes,
refer to the Object Dictionary.
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.
N30 Supervisory Controller User’s Manual 19-7
Display Precision
Indicates the rounded position and decimal places to display for this
object.
Indicates the operation mode of Load Rolling. The mode Monitor
Only means that no Loads are to be shed.
LR Target
Indicates the desired power reduction through Load Rolling.
Consumption Units
Defines the unit for energy values; for example, kWh.
Rate Units
Defines units for demand values; for example, kW.
Limit Elevation
Indicates the amount in percent by which the demand limit is increased
at the beginning of the next interval. The increased demand limit is the
starting value of the the demand limit profile, in the Fixed Window
Algorithm.
EOI Attribute
Indicates the Attribute reference to the EOI pulse, in the Fixed
Window Algorithm.
Sensitivity
Indicates the level of aggression for shedding Loads, in the Sliding
Window Algorithm.
Registering Phase
Defines the time in seconds that the DLLR remains in the Register
mode to get all signed up Loads to register.
19-8 N30 Supervisory Controller User’s Manual
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.
N30 Supervisory Controller User’s Manual 19-9
Procedure Overview
Table 19-1: Working with DLLR Objects
To Do This Follow These Steps:
Add a DLLR Object Browse to and highlight the Energy container. Press the F3 (Add) key.
Highlight DLLR and press Enter. Fill in the fields using Table 19-2. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a DLLR Object Browse to and highlight a DLLR object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields using Table 19-2. Press the
(F3) Save key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a DLLR Object Browse to and highlight a DLLR object. Press the F2 (Command) key.
Use the Spacebar and the Backspace key to cycle through the list until
the desired command appears. Press Enter.
Delete a DLLR Object Browse to and highlight a DLLR object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
19-10 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a DLLR Object
To add a DLLR object:
1. Browse to and highlight the Energy container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight DLLR and press Enter. The first of two DLLR attribute
screens appears (Figure 19-1).
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:
• add a Load object
• edit a Load object
• command a Load object
• delete a Load object
Key Concepts
Load Object
This object allows a user to shut off equipment based on the evaluation
of information from the DLLR object (how much energy is used on
average and how much energy does not need to be used).
One Load object exists for every Load that participates in the DLLR
feature. The Load object receives a Shed Load command from the
DLLR object and takes immediate actions to switch off its associated
output, which then leads to the actual physical Load shedding, causing
the desired power reduction. The Load object is responsible for
monitoring the conditions that require the Load to be released. The
request to release a Load can also come from outside of the Load
object.
To achieve optimal operation, the Load object should be placed into
the device as close as possible to the device containing the output
attribute. If comfort override and output alarm checking are defined,
these attributes should be also very close to the Load object.
The comfort override attribute and the DLLR may be shared by
several Load objects, but the output attribute must not be referenced by
more than one Load object.
The Load object interacts with other objects. For more information,
refer to Appendix A: Building an Energy Management Application
(LIT-6892310) in this document.
Shedding
The entire process of turning off equipment for DLLR.
Releasing
The entire process of turning on equipment shed by DLLR.
Attributes
The values of an object’s attributes determine how the object operates.
The Load object attributes described below are listed in the order that
they appear on the screen. Entry requirements for these attributes are
in Table 20-2.
For additional information about the Load object and its attributes,
refer to the Object Dictionary.
N30 Supervisory Controller User’s Manual 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.
Output Attribute
References the attribute controlling the physical output.
DLLR Object
Identifies the DLLR object that determines the load to be shed.
Load Priority
Specifies the load priority.
Load Use
Specifies the use of the Load object for either DL only, LR only, or
both DL and LR.
Number of States
Indicates the output attribute’s number of states.
Shed State
Specifies the output attribute state’s to be switched to when the load is
shed.
20-4 N30 Supervisory Controller User’s Manual
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.
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 object’s
database.
Period
Defines the time period of the registering attempts in seconds.
Restart Register
Specifies if the load should register when the Load object is started or
restarted.
20-6 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 20-1: Working with Load Objects
To Do This Follow These Steps:
Add a Load Object Browse to and highlight the Energy container. Press the F3 (Add) key.
Highlight Load and press Enter. Fill in the fields using Table 20-2. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Load Object Browse and highlight a Load object. Press Enter to open the object. Press
the F3 (Edit) key. Edit the fields according to Table 20-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Load Object Browse to and highlight a Load object. Press the F2 (Command) key. Use
the Spacebar and the Backspace key to cycle through the list until the
desired command appears. Press Enter.
Delete a Load Object Browse to and highlight a Load object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 20-7
Detailed Procedures
Adding a Load Object
To add a Load object:
1. Browse to and highlight the Energy container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Load and press Enter. The first of two Load object
attribute screens appears (Figure 20-1 and Figure 20-2).
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:
• add a Pulse Meter object
• edit a Pulse Meter object
• command a Pulse Meter object
• delete a Pulse Meter object
Key Concepts
Pulse Meter Object
Working with the Pulse Meter object allows a user to determine the
rate of energy used and accumulated energy used.
The Pulse Meter object accumulates the differences between
consecutive reads of the integer value provided by a pulse counter and
calculates the rate of change between each reading of the value.
Note: The Pulse Meter object handles only counters that count
forward.
The Pulse Meter object must be tied to an N2 Pulse Counter object to
access the counter value that resides in the pulse counter hardware
device (which is hardwired to the pulse input). The N2 Pulse Counter
object may be hardware specific, while the Pulse Meter object is
hardware independent.
Multiple Pulse Meter objects may share the same N2 Pulse Counter
object. The Pulse Meter object must reside on the same device as the
N2 Pulse Counter device.
The Pulse Meter object interacts with other objects. For more
information, refer to Appendix A: Building an Energy Management
Application (LIT-6892310) in this document.
Attributes
The values of an object’s attributes determine how the object operates.
The Pulse Meter object attributes described below are listed in the
order that they appear on the screen. Entry requirements for these
attributes are in Table 21-2.
For additional information about the Pulse Meter object attributes,
refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 21-1: Working with Pulse Meter Objects
To Do This Follow These Steps:
Add a Pulse Meter Object Browse to and highlight the Energy container. Press the F3 (Add) key.
Highlight Pulse Meter and press Enter. Fill in the fields using Table 21-2.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Pulse Meter Object Browse to and highlight a Pulse Meter object. Press Enter to open the
object. Press the F3 (Edit) key. Fill in the fields using Table 21-2. Press
the (F3) Save key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Pulse Meter Browse to and highlight a Pulse Meter object. Press the F2 (Command)
Object key. Use the Spacebar and Backspace key to cycle through the list until
the desired command appears. Press Enter.
Delete a Pulse Meter Object Browse to and highlight a Pulse Meter object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 21-5
Detailed Procedures
Adding a Pulse Meter Object
To add a Pulse Meter object:
1. Browse to and highlight the Energy container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Pulse Meter and press Enter. The Pulse Meter object
attribute screen appears (Figure 21-1).
4. Press Enter.
21-8 N30 Supervisory Controller User’s Manual
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:
• add a Utility Profile object
• edit a Utility Profile object
• command a Utility Profile object
• delete a Utility Profile object
Key Concepts
Utility Profile Object
The Utility Profile object collects utility data from a Pulse Meter
object and a DLLR object. The associated Pulse Meter object should
be dedicated to the Utility Profile object, since it will be activated,
de-activated, and reset by the Utility Profile object. The DLLR object
may be shared by multiple Utility Profile objects. This is the case
when separate utility profiles should be generated for different
tracking periods, such as daily, weekly, and monthly.
For each tracking period it logs the following:
• the energy consumption
• the time and date of the interval with the highest energy
consumption
• the time and date of the interval with the highest sum of energy
consumption and energy not consumed due to shedding
For more information about how the Utility Profile object interacts
with other objects, refer to Appendix A: Building an Energy
Management Application (LIT-6892310) in this document.
Attributes
The values of an object’s attributes determine how the object operates.
The Utility Profile object attributes described below are listed in the
order that they appear on the screen. Entry requirements for these
attributes are in Table 22-2.
For additional information about the Utility Profile object and its
attributes, refer to Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 22-1: Working with Utility Profile Objects
To Do This Follow These Steps:
Add a Utility Profile Object Browse to and highlight the Energy container. Press the F3 (Add) key.
Highlight Utility Profile and press Enter. Fill in the fields using Table 22-2.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Utility Profile Object Browse to and highlight a Utility Profile object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 22-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Utility Profile Browse to and highlight a Utility Profile object. Press the F2 (Command)
Object key. Use the Spacebar and Backspace key to cycle through the list until
the desired command appears. Press Enter.
Delete a Utility Profile Object Browse to and highlight a Utility Profile object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 22-5
Detailed Procedures
Adding a Utility Profile Object
To add a Utility Profile object:
1. Browse to and highlight the Energy container.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Utility Profile and press Enter. The Utility Profile object
attribute screen appears (Figure 22-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:
• add an Analog Totalization object
• edit an Analog Totalization object
• command an Analog Totalization object
• delete an Analog Totalization object
Key Concepts
Analog Totalization Object
The Analog Totalization object can be added to any container or object
in the hierarchy. The Analog Totalization object references any analog
attribute value for input data calculations.
Note: The Input Reference of an Analog Totalization object should
refer to a signed or unsigned integer, a signed or unsigned
long, or a floating point based attribute in order to perform as
intended. Analog Totalization objects referencing other
attribute data types (e.g., Boolean) yield unusual results,
though not necessarily unusable results. Neither the VT100
nor Project Builder give an error message when this object is
attached to any attribute other than signed or unsigned
integer, signed or unsigned long, or floating point based
attributes.
Typical uses of Analog Totalization include:
• to determine how many kilowatt/hours were used in a week
• to determine how much steam is used in a week
• to totalize a calculated value (for instance, degree days)
The Analog Totalization formula and an example are illustrated in
Table 23-1.
Attributes
The values of an object’s attributes determine how the object operates.
The Analog Totalization object attributes described below are listed in
the order that they appear on the screen. Entry requirements for these
attributes are in Table 23-4.
For additional information about the Analog Totalization object and its
attributes, refer to the Object Dictionary.
Object 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 N30 Supervisory Controller User’s Manual
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.
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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 23-3: Working with Analog Totalization Objects
To Do This Follow These Steps:
Add an Analog Totalization Browse to and highlight the container or object where the Analog
Object Totalization object is to be added. Press the F3 (Add) key. Select Analog
Totalization and press Enter. Fill in the fields using Table 23-4. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit an Analog Totalization Browse to and highlight an Analog Totalization object. Press Enter to
Object open the object. Press the F3 (Edit) key. Edit the fields using Table 23-4.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command an Analog Browse to and highlight an Analog Totalization object. Press the
Totalization Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list until the desired command appears. Press Enter.
Delete an Analog Totalization Browse to and highlight an Analog Totalization object. Press Enter to
Object open the object. Press the Delete key. Press the Tab key to confirm the
deletion.
N30 Supervisory Controller User’s Manual 23-7
Detailed Procedures
Adding an Analog Totalization Object
To add an Analog Totalization object:
1. Browse to and highlight the container or object where the Analog
Totalization object is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Select Analog Totalization and press Enter. The Analog
Totalization object attribute screen appears (Figure 23-1).
4. Press Enter.
23-10 N30 Supervisory Controller User’s Manual
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 object’s
value.
This chapter describes how to:
• add an Event Totalization object
• edit an Event Totalization object
• command an Event Totalization object
• delete an Event Totalization object
Key Concepts
Event Totalization Object
An Event Totalization object records a total for the number of times
any binary event has occurred. Unlike the other types of totalization,
Event Totalization updates its Present Value output each time an event
occurs, instead of calculating the value every minute.
The Event Totalization object can be added to any container or object
in the hierarchy. The Event Totalization object references any object
and one of its attributes for input data calculations.
Note: The Input Reference of an Event Totalization object should
refer to enumeration or Boolean based attributes in order to
perform as intended. Event Totalization objects referencing
other attribute data types (e.g., floating point) yield unusual
results, though not necessarily unusable results. Neither the
VT100 nor Project Builder give an error message when this
object is attached to any attribute other than enumeration or
Boolean based attributes.
Typical uses for Event Totalization are determining:
• how many times a motor started
• how often a sensor was in alarm
• how many cars entered a parking lot
The Event Totalization formula and an example are illustrated in
Table 24-1. Refer to the Attributes section of this chapter for
information about attributes used in the calculation.
Attributes
The values of an object’s attributes determine how the object operates.
The Event Totalization object attributes described below are listed in
the order that they appear on the screen. Entry requirements for these
attributes are in Table 24-4.
For additional information about the Event Totalization object and its
attributes, refer to Object Dictionary.
Object 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 N30 Supervisory Controller User’s Manual
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.
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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 24-3: Working with Event Totalization Objects
To Do This Follow These Steps:
Add an Event Totalization Browse to and highlight the container or object where the Event
Object Totalization object is to be added. Press the F3 (Add) key. Select Event
Totalization and press Enter. Fill in the fields using Table 24-4. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit an Event Totalization Browse to and highlight an Event Totalization object. Press Enter to open
Object the object. Press the F3 (Edit) key. Edit the fields using Table 24-4. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command an Event Browse to and highlight an Event Totalization object. Press the
Totalization Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list of commands until the desired command appears.
Press Enter.
Delete an Event Totalization Browse to and highlight an Event Totalization object. Press Enter to open
Object the object. Press the Delete key. Press the Tab key to confirm the
deletion.
N30 Supervisory Controller User’s Manual 24-7
Detailed Procedures
Adding an Event Totalization Object
To add an Event Totalization object:
1. Browse to and highlight the container or object where the Event
Totalization object is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Select Event Totalization and press Enter. The Event Totalization
object attribute screen appears (Figure 24-1).
4. Press Enter.
24-10 N30 Supervisory Controller User’s Manual
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.
Chapter 25
Working with
Runtime Totalization Objects
Introduction
The Runtime Totalization object tracks the number of one minute time
intervals that elapse while a designated input, such as a binary or
multistate value, has matched a specified state.
This chapter describes how to:
• add a Runtime Totalization object
• edit a Runtime Totalization object
• command a Runtime Totalization object
• delete a Runtime Totalization object
Key Concepts
Runtime Totalization Object
A Runtime Totalization object accumulates total time only while a
particular condition is satisfied (for instance, Supply Fan 1 is on).
It answers the question “How long?” and is typically used to even out
the use and wear of equipment, or to schedule maintenance after a
certain amount of use. Data is recorded in minutes and converted to
hours for the display.
The Runtime Totalization object can be added to any container or
object. The Runtime Totalization object references any binary or
multistate attribute value for input data for its own calculations.
Note: The Input Reference of a Runtime Totalization object should
refer to enumeration or Boolean based attributes in order to
perform as intended. Runtime Totalization objects
referencing other attribute data types (e.g., floating point)
yield unusual results, though not necessarily unusable
results. Neither the VT100 nor Project Builder give an error
message when this object is attached to any attribute other
than enumeration or Boolean based attributes.
Typical uses for a Runtime Totalization object are determining:
• fan or pump runtime
• the amount of time a point is in alarm
• runtime of fixed loads (such as lighting) for energy totalization and
tenant billback
The Runtime Totalization formula and an example are illustrated in
Table 25-1. Refer to the Attributes section of this chapter for
information about attributes used in the calculation.
Attributes
The values of an object’s attributes determine how the object operates.
The Runtime Totalization object attributes described below are listed
in the order that they appear on the screen. Entry requirements for
these attributes are in Table 25-4.
For additional information about the Runtime Totalization object and
its attributes, refer to Object Dictionary.
Object 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 N30 Supervisory Controller User’s Manual
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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 25-3: Working with Runtime Totalization Objects
To Do This Follow These Steps:
Add a Runtime Totalization Browse to and highlight the container or object where the Runtime
Object Totalization object is to be added. Press the F3 (Add) key. Select Runtime
Totalization and press Enter. Fill in the fields using Table 25-4. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Edit a Runtime Totalization Browse to and highlight a Runtime Totalization object. Press Enter to
Object open the object. Press the F3 (Edit) key. Edit the fields using Table 25-4.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Runtime Browse to and highlight a Runtime Totalization object. Press the
Totalization Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list of commands until the desired command appears.
Press Enter.
Delete a Runtime Totalization Browse to and highlight a Runtime Totalization object. Press Enter to
Object open the object. Press the Delete key. Press the Tab key to confirm the
deletion.
N30 Supervisory Controller User’s Manual 25-7
Detailed Procedures
Adding a Runtime Totalization Object
To add a Runtime Totalization object:
1. Browse to and highlight the container or object where the
Runtime Totalization object is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Select Runtime Totalization and press Enter. The Runtime
Totalization object attribute screen appears (Figure 25-1).
4. Press Enter.
25-10 N30 Supervisory Controller User’s Manual
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: The Input Reference of an Analog Alarm object should refer
to an analog attribute type in order to perform as intended.
Analog Alarm objects referencing other attribute data types
(e.g., Boolean) yield unusual results, though not necessarily
unusable results. Neither the VT100 nor Project Builder give
an error message when this object is attached to any attribute
other than floating point based attributes.
This object detects an alarm based on up to four limits and can be
configured to report that alarm. This object sets the Alarm State
attribute of the object it is added to.
This chapter describes how to:
• add an Analog Alarm object
• edit an Analog Alarm object
• command an Analog Alarm object
• delete an Analog Alarm object
Key Concepts
Analog Alarm Object
When the Analog Alarm object’s Input attribute value exceeds the
defined limits, it causes a change in the Analog Alarm object’s present
value and the generation of a Status Notification Report (SNR).
For example, with this object you can have a warning issued if the
temperature in a room falls below 60°F and an alarm issued if the
temperature falls below 50°F.
States
The Analog Alarm object can be in any of the following states:
Normal State
This occurs when the Analog Alarm object is in an acceptable,
expected condition, as indicated by the Input attribute value.
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.
N30 Supervisory Controller User’s Manual 26-3
Attributes
The values of an object’s attributes determine how the object operates.
The Analog Alarm object attributes described below are listed in the
order that they appear on the screen. Entry requirements for these
attributes are in Table 26-2.
For additional information about the Analog Alarm object and its
attributes, refer to the Object Dictionary.
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.
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.
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.
Fault Priority
Provides the priority assigned to the Fault state that gets transmitted to
the SNR.
Event Enable
Determines if the object sends reports (SNRs), if this value is True.
Dialout Required
Forces a dial out to a destination device (if True), when this object
goes into an alarm or warning state.
Delay Time
Indicates the amount of time, 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.
Normal Priority
Indicates the priority assigned to the Normal state that gets transmitted
to the SNR.
Procedure Overview
Table 26-1: Working with Analog Alarm Objects
To Do This Follow These Steps:
Add an Analog Alarm Object Browse to and highlight the container or object where the Analog Alarm
object is to be added. Press the F3 (Add) key. Highlight Analog Alarm
and press Enter. Fill in the fields using Table 26-2. Press the F3 (Save)
key. Check the User Assistance area of the screen to verify if the save
was successful or if there were errors. Press any key to continue. Press
the F4 (Cancel) key to return to the container hierarchy.
Edit an Analog Alarm Object Browse to and highlight an Analog Alarm object. Press Enter to open the
object. Press the F3 (Edit) key. Edit the fields using Table 26-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command an Analog Alarm Browse to and highlight an Analog Alarm object. Press the
Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list until the desired command appears. Press Enter.
Delete an Analog Alarm Object Browse to and highlight an Analog Alarm object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 26-7
Detailed Procedures
Adding an Analog Alarm Object
To add an Analog Alarm object:
1. Browse to and highlight the container or object where the Analog
Alarm object is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Analog Alarm and press Enter. The first of two Analog
Alarm attribute screens appears (Figure 26-1).
Note: Use the [ and ] keys to page to other screens.
4. Press Enter.
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: The Input Reference of a Multistate Alarm object should
refer to enumeration or Boolean based attributes in order to
perform as intended. Multistate Alarm objects referencing
other attribute data types (e.g., floating point) yield unusual
results, though not necessarily unusable results. Neither the
VT100 nor Project Builder give an error message when this
object is attached to any attribute other than enumeration or
Boolean based attributes.
This object detects the alarm with respect to a difference from a
defined normal state, and it can be configured to report the alarm.
This chapter describes how to:
• add a Multistate Alarm object
• edit a Multistate Alarm object
• command a Multistate Alarm object
• delete a Multistate Alarm object
Key Concepts
Multistate Alarm Object
When the Multistate Alarm object’s Input attribute value goes Off, it
causes the generation of a Status Notification Report (SNR). For
example, an alarm can be issued when a switch is in the Off position.
States
The Multistate Alarm object can be in any of the following states:
Normal State
This occurs when the Multistate Alarm object is in an acceptable,
expected condition, as indicated by the Input attribute value.
Fault State
This occurs when the Multistate Alarm object enters the alarm
condition, as indicated by the Input attribute value.
SNR
Status Notification Report. A report that is generated and routed via
the Message Routing feature to printers and VT100 Terminals.
Attributes
The values of an object’s attributes determine how the object operates.
The Multistate Alarm object attributes described below are listed in the
order that they appear on the screen. Entry requirements for these
attributes are in Table 27-2.
For additional information about the Multistate Alarm object and its
attributes, refer to the Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 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 Priority
Indicates the priority assigned to the Fault state that gets transmitted to
the SNR.
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 N30 Supervisory Controller User’s Manual
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.
Procedure Overview
Table 27-1: Working with Multistate Alarm Objects
To Do This Follow These Steps:
Add a Multistate Alarm Object Browse to and highlight the container or object where the Multistate Alarm
is to be added. Press the F3 (Add) key. Highlight Multistate Alarm and
press Enter. Fill in the fields using Table 27-2. Press the F3 (Save) key.
Check the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
F4 (Cancel) key to return to the container hierarchy.
Edit a Multistate Alarm Object Browse to and highlight a Multistate Alarm object. Press Enter to open the
object. Press the F3 (Edit) key. Fill in the fields using Table 27-2. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Multistate Alarm Browse to and highlight a Multistate Alarm object. Press the
Object F2 (Command) key. Use the Spacebar and the Backspace key to cycle
through the list until the desired command appears. Press Enter.
Delete a Multistate Alarm Browse to and highlight a Multistate Alarm object. Press Enter to open the
Object object. Press the Delete key. Press the Tab key to confirm the deletion.
27-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Multistate Alarm Object
To add a Multistate Alarm object:
1. Browse to and highlight the container or object where the
Multistate Alarm is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Multistate Alarm and press Enter. The first of
two Multistate Alarm object attribute screens appears
(Figure 27-1).
4. Press Enter.
27-10 N30 Supervisory Controller User’s Manual
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:
• add a Trend Log object
• edit a Trend Log object
• command a Trend Log object
• delete a Trend Log object
Key Concepts
Trend Log Object
The Trend Log object can be added to any object to sample the value
of any of the attributes of the following data types: Boolean, float,
double float, enumeration, byte, unsigned integer, unsigned long,
signed integer, signed long, or bit string. Typically, a Trend Log object
collects data from an N2 Analog Input point object in a controller,
which reports information such as outdoor air temperature or room air
temperature. This data can be displayed or printed. Figure 28-1 shows
a sample of Trend Log object data collected.
Trend Log Data From: ADMIN-Office, Present Value, Fault, OutOfService
27 Aug 1999 12:00:00 78.0 deg F
27 Aug 1999 14:32:00 79.1 deg F
28 Aug 1999 00:00:00 79.1 deg F
28 Aug 1999 12:00:00 79.1 deg F
29 Aug 1999 00:00:00 78.7 deg F
29 Aug 1999 12:00:00 79.3 deg F
30 Aug 1999 00:00:00 81.3 deg F
Attributes
The values of an object’s attributes determine how the object operates.
The Trend Log object attributes described below are listed in the order
that they appear on the screen. Entry requirements for these attributes
are in Table 28-2.
For additional information about the Trend Log object and its
attributes, refer to Object Dictionary.
Object 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.
N30 Supervisory Controller User’s Manual 28-3
Enabled
Indicates if the object is active and executing an operational condition.
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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 28-1: Working with Trend Log Objects
To Do This Follow These Steps:
Add a Trend Log Object Browse to and highlight the container or object where the Trend Log
object is to be added. Press the F3 (Add) key. Highlight Trend Log and
press Enter. Fill in the fields using Table 28-2 Press the F3 (Save) key.
Check the User Assistance area of the screen to verify if the save was
successful or if there were errors. Press any key to continue. Press the
F4 (Cancel) key to return to the container hierarchy.
Edit a Trend Log Object Browse to and highlight a Trend Log object. Press Enter to open the
object. Press the F3 (Edit) key. Fill in the fields using Table 28-2. Press
the F3 (Save) key. Check the User Assistance area of the screen to verify
if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Trend Log Object Browse to and highlight a Trend Log object. Press the F2 (Command)
key. Use the Spacebar and the Backspace key to cycle through the list
until the desired command appears. Press Enter.
Delete a Trend Log Object Browse to and highlight a Trend Log object. Press Enter to open the
object. Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 28-5
Detailed Procedures
Adding a Trend Log Object
To add a Trend Log object:
1. Browse to and highlight the container or object where the Trend
Log object is to be added.
2. Press the F3 (Add) key. The Add Object list appears.
3. Highlight Trend Log and press Enter. The Trend Log object
attribute screen appears (Figure 28-2).
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.
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 N30 Supervisory Controller User’s Manual
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.
N30 Supervisory Controller User’s Manual 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 N30 Supervisory Controller User’s Manual
Procedure Overview
Table 29-2: Notification Class Object
To Do This Follow These Steps:
Add a Notification Class In Project Builder, open the database to which you want to add the
Object in Project Builder Notification Class object. Expand the database so that the container or
object you want to add the Notification Class object to is visible. In the
object library on the left side of the screen, open the N30 folder. Select
the Notification object and drag it to the container or object to which you
want to add the Notification Class object. Browse to the object you just
created. Double-click the row header of the Notification Class object to
open the M-View screen. Enter an object name and description. Click the
List Elements button. Click the Add button. Click the Structure Elements
button. Fill in the fields according to Table 29-3. Click Done to return to
the Complex View – Recipient list. Continue adding until all recipients are
entered. Click Done to return to the M-View screen for the Notification
Class object. Click the Array Elements button to edit the priority list. Click
the Ack Required button to edit whether destinations must globally
acknowledge transitions. Click OK when finished.
The object cannot be used until the new, modified database is
downloaded to your N30.
Edit a Notification Class In Project Builder, open the database with the Notification Class object
Object in Project Builder you want to edit. Browse to and select the object you want to edit.
Double-click the row header of the object to open the M-View screen. Edit
the object name and description if necessary. Click the List Elements
button. Click the Structure Elements button. Fill in the fields according to
Table 29-3. Click Done to return to the Complex View – Recipient list. Edit
each recipient in the list as necessary. Click Done to return to the M-View
screen. Click the Array Elements button to edit the priority list. Click the
Ack Required button to edit whether destinations must globally
acknowledge transitions. Click OK when finished.
The edited object cannot be used until the new, modified database is
downloaded to your N30.
Edit a Notification Class Browse to and select the Notification Class object that you want to edit.
Object with a VT100 Press the Return key to open. Press the F3 (Edit) key. Edit the fields as
required.
Note: The recipient list cannot be edited using a VT100.
Press the F3 (Save) key. Press any key to continue. Press the
F4 (Cancel) key to return to the main screen.
Command a Notification Class Browse to and select the Notification Class object you want to command.
Object with a VT100 Press the F2 (Command) key. Use the Spacebar and Backspace keys to
select Enable or Disable. Press the Return key to execute the selected
command.
Delete a Notification Class Browse to and select the Notification Class object you want to delete.
Object with a VT100 Press the Return key to open. Press the Delete key. Press the Tab key to
confirm the deletion.
N30 Supervisory Controller User’s Manual 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. Expand the database so that the container or object you want to
add the Notification Class object to is visible.
3. In the object library on the left side of the screen, open the N30
folder.
4. Select the Notification object and drag it over to the container or
object to which you want to add the Notification Class object.
5. Browse to the object you just created.
6. Double-click the row header of the Notification Class object to
open the M-View screen for the Notification Class object
(Figure 29-1).
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:
• add a Remote Destination object
• edit a Remote Destination object
• delete a Remote Destination object
Note: Remote Destination objects are not commandable.
Key Concepts
Remote Destination Object Operation
SNRs (received from Alarm objects) initiate a connection if either the
Dialout Required flag is set, or the Max SNR Queue reaches the
percentage set in the SNR Dial Out Level attribute.
The Remote Destination object is connected to the Serial Datalink
object by setting the Port Number attribute.
The Remote Destination object performs the following tasks:
• receives status notification report messages from the Message
Router object.
• sends Dial commands to the Serial Datalink object when status
notification report messages need to be sent.
• notifies the Serial Datalink object to disconnect when the Dial
Connect Timeout expires.
Attributes
Dial Connect Timeout
Indicates the amount of time the Remote Destination object waits to
receive messages before disconnecting, following the N30-initiated
Dial command.
Timeout
Indicates the amount of time remaining prior to disconnection,
following the N30-initiated Dial command.
Error State
Indicates the reason for error:
None - No error.
Dial Out Failed - The Serial Datalink object failed to connect in the
time set by the Retries and Retry Interval attributes. The Serial
Datalink object’s Connected To attribute does not change to Metasys
device. If the Error State attribute is set to this state, the Remote
Destination object’s offline status is True.
Disconnected - The Remote Destination object currently does not need
to be connected.
N30 Supervisory Controller User’s Manual 30-3
Phone Number
Indicates the Dial-out phone number if a modem is connected to the
port.
Port Number
Indicates the port number specifying the port to which data is sent.
Retries
Specifies how many times the Remote Destination object resends the
Dial command. If the dial-up connection could not be made in the time
defined as the Retry Interval, the Remote Destination object sends the
Dial command again.
Retry Interval
Indicates the amount of time in which Retries occur. If the Error State
attribute is set to Disconnected, the Remote Destination object retries
sending the Dial command periodically in this interval.
Login ID
Identifies which user is connected during a dial-up session with an
M-Series Workstation.
Password
Identifies which password is connected during a dial-up session with
an M-Series Workstation.
30-4 N30 Supervisory Controller User’s Manual
Process Identifier
Used to route notifications (alarms) to this destination. Must be a
unique number for each device. If not specified, a value is
automatically assigned on download.
Ack Required
Setting this value to True allows the BACnet Acknowledgement
Notification messages to be passed to the M3 workstation.
Status
The Metasys Common Object (LIT-694020) chapter of the Object
Dictionary details this attribute. A list of relevant states follows (listed
in hierarchical order from highest to lowest):
Normal: Expected operating condition.
Active Filter
Selects the type of filtering in effect for this remote destination. The
filter types are as follows:
• Pass None - When selected this destination receives no alarm
messages.
• Pass All - When selected this destination receives all alarm
messages.
• Filter A - This destination receives alarm messages based on
settings of Filter A.
• Filter B - This destination receives alarm messages based on
settings of Filter B.
• Filter A and B - This destination receives alarm messages based
on settings of Filter A and B.
Priority Filter A
Defines which priorities 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.
N30 Supervisory Controller User’s Manual 30-5
Priority Filter B
Defines which priorities the destination receives when Filter B is in
effect. A value of True for a particular selection means that messages
of that defined priority reach this destination. Choices from highest to
lowest priority are Critical, Serious, Important, Status.
Category Filter B
Defines which categories of messages the destination receives when
Filter B is in effect. This filter has no effect for alarm messages
without a defined category. A value of True for a particular selection
means that messages of that defined category reach this destination.
Procedure Overview
Table 30-1: Remote Destination Object Procedure Overview
To Do This Follow These Steps:
Add a Remote Destination Browse to and highlight the Operator Devices container. Press the
Object F3 (Add) key. Highlight Remote Destination and press Enter. Fill in the
fields using Table 30-2. Press the F3 (Save) key. Check the User
Assistance area of the screen to verify if the save was successful or if
there were errors. Press any key to continue. Press the F4 (Cancel) key
to return to the container hierarchy.
Edit a Remote Destination Browse to and highlight a Remote Destination object. Press Enter to open
Object the object. Press the F3 (Edit) key. Edit the fields according to Table 30-2.
Press the F3 (Save) key. Check the User Assistance area of the screen to
verify if the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Delete a Remote Destination Browse to and highlight a Remote Destination object. Press Enter to open
Object the object. Press the Delete key. Press the Tab key to confirm the
deletion.
Note: The Remote Destination object has no commands.
N30 Supervisory Controller User’s Manual 30-7
Detailed Procedures
Adding a Remote Destination Object
To add a Remote Destination object:
1. Browse to and highlight the Operator Devices container.
2. Press the F3 (Add) key.
3. Highlight the Remote Destination object from the list that appears
and press Enter. The first of two Remote Destination object
configuration screens appears (Figure 30-1). The second screen is
shown in Figure 30-2.
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: In order to function, the E-mail object must have access via
Ethernet to an SMTP server on the Local Area Network
(LAN). In addition, the N30 Device object must identify the
location of the SMTP server.
For standard alarming, the E-mail object routes alarms based on
filtering criteria defined in the E-mail object attributes. However, for
BACnet alarming, set the E-mail object as a destination of the
BACnet Notification Class in order to route alarms.
This chapter describes how to:
• add an E-mail object
• edit an E-mail object
• command an E-mail object
• delete an E-mail object
Key Concepts
E-mail Object Operation
The Message Router object sends a Status Notification Report (SNR)
containing status change information to the E-mail object. The E-mail
object converts the text of the SNR into the proper format for the body
of an e-mail message.
The E-mail object sends the e-mail message to an SMTP server, which
routes the message to the intended recipient (see Figure 31-1).
Note: The E-mail object can only guarantee delivery of the
message to the SMTP server. The SMTP server is
responsible for delivering the message to the intended
recipient. If the SMTP server cannot deliver a message, the
SMTP server sends a delivery failure notice to the e-mail
address identified in the Reverse Path attribute.
If the E-mail object cannot send a message due to errors/failures in
communicating with the server, the E-mail object buffers the message
and tries again at a later time according to the values of the Number of
Retries and the Retry Interval attributes.
TO:jane.smith@jci.com
FROM:john.smith@jci.com
SUBJECT:0001_SITE: SER HA 0001-AV-1 150.0 Deg F 14 Jan 2000 13:19:02
Site Name: 0001_SITE
Alarm Priority: SER
Event State: HA
Previous Event State: NOR
Object Name: 0001-AV-1
Object Value: 150.0 Deg F
Object Category: HVAC
Reliability: Reliable
Alarm Text: Chiller at northwest corner of building
Date: 14 Jan 2000
Time: 13:19:02
Message Type: Alarm
Acknowledge Required: TRUE
emailmsg
Attributes
Recipient 1/2/3 Name
Specifies the e-mail addresses of the intended recipients. Specifies up
to three recipients.
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.
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.
N30 Supervisory Controller User’s Manual 31-5
Active Filter
Selects the type of filtering in effect for the E-mail object. The filter
types are as follows:
• Pass None - No SNR messages sent.
• Pass All - Send all SNR messages.
• Filter A - Send SNR messages based on the settings of Filter A.
• Filter B - Send SNR messages based on the settings of Filter B.
• Filter A and B - Send SNR messages based on the settings of
Filter A and Filter B.
Priority Filter A
This element of Filter A defines which priorities the E-mail object
sends when Filter A is in effect. A value of True for a particular
position (Critical, Serious, Important, or Status) means that the E-mail
object sends messages of that defined priority.
Category Filter A
This element of Filter A defines which categories of messages the
E-mail object sends when Filter A is in effect. This filter has no effect
for SNRs that do not define a category. A value of True for a particular
position (HVAC, Fire, Security, Services, or Administrative) means
that the E-mail object sends messages of that defined category.
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 N30 Supervisory Controller User’s Manual
Error State
Indicates the reason for the error. Possible values are:
• None
• Queue Full
• Server Error
Example
Figure 31-4 and Figure 31-5 show screens from a sample completed
E-mail object.
Procedure Overview
Table 31-1: E-mail Object Procedure Overview
To Do This Follow These Steps:
Add an E-mail Object Browse to and highlight the Operator Devices container. Press the
F3 (Add) key. Highlight E-mail and press Enter. Fill in the fields using
Table 31-2. Press the F3 (Save) key. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Edit an E-mail Object Browse to and highlight an E-mail object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields according to Table 31-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command an E-mail Object Browse to and highlight an E-mail object. Press the F2 (Command) key.
Use the Spacebar and the Backspace key to cycle through the list of
commands until the desired command appears. Press Enter.
Delete an E-mail Object Browse to and highlight an E-mail object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
N30 Supervisory Controller User’s Manual 31-9
Detailed Procedures
Adding an E-mail Object
To add an E-mail object:
1. Browse to and highlight the Operator Devices container.
2. Press the F3 (Add) key.
3. Highlight the E-mail object from the list that appears and press
Enter. The first of two E-mail object configuration screens
appears (Figure 31-4). The second screen is shown in Figure 31-5.
4. Press Enter.
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: The Pager object supports only a basic notification function
that communicates to alphanumeric pager services that
support the Telocator Alphanumeric Protocol (TAP). The
pager service port must be set to accept N30 pager
notifications: Data bits = 8, Parity = None, and Stop bits = 1
The Pager object does not support Acknowledgement,
Systems Management Server (SMS) and Wireless
Application Protocol (WAP) solutions, or other similar
advanced functions.
For standard alarming, the Pager object routes alarms based on
filtering criteria defined in the Pager object attributes. However, for
BACnet alarming, set the Pager object as a destination of the BACnet
Notification Class object in order to route alarms.
This chapter describes how to:
• add a Pager object
• edit a Pager object
• command a Pager object
• delete a Pager object
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: Pager devices are connected via modem through a Dialout
N30 port. More than one Pager object can be related to a
Dialout port by setting the Port Number attribute. However,
only one Pager object at a time can use the port.
The Pager object can share a Dialout port only with other
Pager objects (not with other devices).
If another Pager object is already using the Dialout N30 port, the Pager
object stores the message in a queue and attempts to dial again at one
minute intervals.
Once the pager service receives the message, the pager service routes
the SNR message to the pager (see Figure 32-1).
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
SER B7F3 SUPPLY FAN Fault 04 Jun 2001 11:05:47 CALL MAINTENANCE SERVICE @ 555-4703
pagermsg
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.
Active Filter
Selects the type of filtering in effect for the Pager object. The filter
types are as follows:
• Pass None - No SNR messages sent.
• Pass All - Send all SNR messages.
• Filter A - Send SNR messages based on the settings of Filter A.
• Filter B - Send SNR messages based on the settings of Filter B.
• Filter A and B - Send SNR messages based on the settings of
Filter A and Filter B.
32-4 N30 Supervisory Controller User’s Manual
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.
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.
Procedure Overview
Table 32-1: Pager Object Procedure Overview
To Do This Follow These Steps:
Add a Pager Object Browse to and highlight the Operator Devices container. Press the
F3 (Add) key. Highlight Pager, and press Enter. Fill in the fields using
Table 32-2. Press the F3 (Save) key. Check the User Assistance area of
the screen to verify if the save was successful or if there were errors.
Press any key to continue. Press the F4 (Cancel) key to return to the
container hierarchy.
Edit a Pager Object Browse to and highlight a Pager object. Press Enter to open the object.
Press the F3 (Edit) key. Edit the fields according to Table 32-2. Press the
F3 (Save) key. Check the User Assistance area of the screen to verify if
the save was successful or if there were errors. Press any key to
continue. Press the F4 (Cancel) key to return to the container hierarchy.
Command a Pager Object Browse to and highlight a Pager object. Press the F2 (Command) key.
Use the Spacebar and the Backspace key to cycle through the list of
commands until the desired command appears. Press Enter.
Delete a Pager Object Browse to and highlight a Pager object. Press Enter to open the object.
Press the Delete key. Press the Tab key to confirm the deletion.
32-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Adding a Pager Object
To add a Pager object:
1. Browse to and highlight the Operator Devices container.
2. Press the F3 (Add) key.
3. Highlight the Pager object from the list that appears and press
Enter. The first of two Pager object configuration screens appears
(Figure 32-2). The second screen is shown in Figure 32-3.
7. Press Enter.
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.
Chapter 33
Introduction
Note: Do not confuse the BACnet™ Group object with the
Johnson Controls Group object. For information on the
Group object, refer to the Working with Group Objects
chapter (LIT-6892060) of the N30 Supervisory Controller
User’s Manual or the Group chapter (LIT-694420) of the
Object Dictionary.
The BACnet Group object provides the user with the ability to
customize the organization of objects within the site. The BACnet
Group object simplifies the exchange of information between objects
by calling all members of the group at once. A group consists of any
combination of object types. For example, you can use the BACnet
Group object to monitor the temperature in different rooms throughout
a floor of a building.
This chapter describes the difference between BACnet Group objects
and Group objects and how to:
• add a BACnet Group object
• edit a BACnet Group object
• delete a BACnet Group object
Note: The BACnet Group object is not VT100 configurable. You
must use Project Builder to configure the BACnet Group
object.
See the American Society of Heating, Refrigerating, and
Air-conditioning Engineers (ASHRAE) Standard 135-1995 for
information on this object and the BACnet communication standard.
Key Concepts
BACnet Group Object vs Johnson Controls Proprietary Group
Object
Differences between BACnet Group objects and Johnson Control
Proprietary Group objects are:
• BACnet Group objects are compliant with the BACnet protocol,
while Group objects are not.
• BACnet Group objects reference any object except another
BACnet Group object as long as all members of the group reside in
the same device that maintains the BACnet Group object. Group
objects can reference other Group objects and objects that do not
reside in the same device.
• BACnet Group objects have no limit to the number of members in
a group, and each object member within the group includes one or
more of its attributes. The Group object can hold up to 75 group
members.
• BACnet Group objects list multiple attributes of the group
members while the Group objects only list the Present Value of the
group members.
For information on the Group object, refer to the Working with Group
Objects chapter (LIT-6892060) of the N30 Supervisory Controller
User’s Manual or the Group chapter (LIT-694420) of the Object
Dictionary.
Attributes
The values of an object’s attributes determine how the object operates.
The BACnet Group object attributes are described below.
For additional information about the BACnet Group object and its
attributes, refer to the BACnet Group chapter (LIT-694180) of the
Object Dictionary.
Object Name
Identifies the object on the user interface.
Description
Provides optional information to further describe the object.
N30 Supervisory Controller User’s Manual 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.
Detailed Procedures
Notes: The BACnet Group object is not VT100 configurable. You
must use Project Builder to configure the BACnet Group
object.
Before performing the following procedures, start Project
Builder and open or create the project in which you want to
add a BACnet Group object. Refer to the Getting Started
chapter (LIT-693215) of Project Builder User’s Guide.
3. Click the List Elements button. The List Of Group Members dialog
box appears (Figure 33-2).
33-6 Working with BACnet Group Objects
Controls Group
507 E. Michigan Street
P.O. Box 423 www.johnsoncontrols.com
Milwaukee, WI 53201 Printed in U.S.A.
N30 Supervisory Controller User’s Manual 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 attribute’s value. For example, the Event Enrollment
object can monitor the temperature value from a room thermostat and
report an event if the temperature falls below a low limit parameter
value.
Note: The Event Enrollment object is not VT100 configurable.
You must use Project Builder to configure the Event
Enrollment object.
This chapter describes how to:
• add an Event Enrollment object
• edit an Event Enrollment object
• command an Event Enrollment object
• delete an Event Enrollment object
• edit Event Parameters - examples
Key Concepts
Event Enrollment Object
Unlike the Analog Alarm objects and Multistate Alarm objects in the
N30 Supervisory Controller, Event Enrollment objects are compliant
with BACnet™ protocol. The Event Enrollment object’s attributes
contain information for generating events. The object is configured to
trigger an event when the value of the user-defined referenced attribute
changes and meets the specified criteria. When an event occurs, a
notification message is sent to the user-defined recipients. Notification
message recipients are devices defined in the Notification Class object
referenced by the Event Enrollment object.
See the Event Enrollment/BACnet Event Enrollment chapter
(LIT-694160) of the Object Dictionary or the American Society of
Heating, Refrigerating and Air-conditioning Engineers (ASHRAE)
Standard 135-1995 for information on this object and the BACnet
communication standard.
Attributes
The values of an object’s attributes determine how the object operates.
The Event Enrollment object attributes are described below.
Object 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.
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.
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.
Detailed Procedures
Notes: The Event Enrollment object is not VT100 configurable.
You must use Project Builder to configure the Event
Enrollment object.
Before performing the following procedures, start Project
Builder and open or create the project in which you want to
add an Event Enrollment object. Refer to the Getting Started
chapter (LIT-693215) of Project Builder User’s Guide.
Select True or False for the To Off Normal, To Fault, and To Normal attributes.
Click Done.
Notify Type Select Event or Alarm as the Notify Type for this Event Enrollment object.
Notification Class Type the Object Identifier (Object ID) of the Notification Class object from
which you are routing alarms.
Alarm Message Text Type the desired text of the alarm message for event notification (optional).
4. Press Enter.
Figure 34-3: M-View Edit Attributes Dialog Box - Change of Bitstring Example
2. Select Change of bitstring in the Event Type drop-down menu.
3. Click the Event Parameters button. The Change of Bitstring Event
Parameters dialog box appears (Figure 34-4).
N30 Supervisory Controller User’s Manual 34-11
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 Working with Event Enrollment Objects
Figure 34-8: M-View Edit Attributes Dialog Box - Change of State Example
2. Select Change of state in the Event Type drop-down menu.
3. Click the Event Parameters button. The Change of State Event
Parameters dialog box appears (Figure 34-9).
N30 Supervisory Controller User’s Manual 34-15
Figure 34-15: M-View Edit Attributes Dialog Box - Command Failure Example
2. Select Command Failure in the Event Type drop-down menu.
3. Click the Event Parameters button. The Command Failure Event
Parameters dialog box appears (Figure 34-16).
34-22 Working with Event Enrollment Objects
Figure 34-17: M-View Edit Attributes Dialog Box - Floating Limit Example
2. Select Floating limit in the Event Type drop-down menu.
3. Click the Event Parameters button. The Floating Limit Event
Parameters dialog box appears (Figure 34-18).
34-24 Working with Event Enrollment Objects
Figure 34-19: M-View Edit Attributes Dialog Box - Out of Range Example
2. Select Out of range in the Event Type drop-down menu.
3. Click the Event Parameters button. The Out of Range Event
Parameters dialog box appears (Figure 34-20).
34-26 Working with Event Enrollment Objects
Controls Group
507 E. Michigan Street
P.O. Box 423 www.johnsoncontrols.com
Milwaukee, WI 53201 Printed in U.S.A.
N30 Supervisory Controller User’s Manual 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.
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 8
N2 Binary Input N2 Binary Input
Object Object
(Output Alarm) (Comfort Alarm)
2 6
N2 Binary Output
Load Object
Object
5 4 1
N2 Pulse Counter Pulse Meter
DLLR Object
Object Object
2 6
N2 Binary Output
Load Object
Object
4 3 9
Pulse Meter Utility Profile
Schedule Object
Object Object
DLLR Flow
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.
Procedure Overview
Table A-4: Building an Energy Management Application
To Do This Follow These Steps:
Build an Energy Management Add N2 point objects to the database, including N2 Pulse Counter objects.
Application Add the DLLR object. Add a Pulse Meter object referencing the N2 Pulse
Counter object and the DLLR object. Add a Utility Profile object to the
same device as the Pulse Meter and DLLR objects. Add another Pulse
Meter object referencing the N2 Pulse Counter object and the Utility
Profile object. Add Load objects referencing output loads to potentially be
shed and referencing objects representing an Output Alarm and a
Comfort Alarm. Add a Schedule object referencing the Utility Profile
object. Verify that the energy management application is operating
correctly.
N30 Supervisory Controller User’s Manual A-7
Detailed Procedures
Building an Energy Management Application
To build an energy management application:
1. Add N2 point objects to the database, including N2 Pulse Counter
objects. See the N30 Supervisory Controller Point Mapping
Technical Bulletin (LIT-6891400).
2. Add the DLLR object. One DLLR object exists per meter
hardware piece. For example, a building with three electric meters
should have three DLLR objects to regulate the system. Multiple
DLLR objects can exist in one N30.
3. Add a Pulse Meter object referencing the N2 Pulse Counter object
and the DLLR object. The Pulse Meter should be on the same
device as the DLLR object.
4. Add a Utility Profile object to the same device as the Pulse Meter
and DLLR objects.
5. Add another Pulse Meter object referencing the N2 Pulse Counter
object and the Utility Profile object. One Pulse Meter object
should be dedicated to one Utility Profile object.
6. Add Load objects referencing output loads to potentially be shed
and referencing objects representing an Output Alarm and a
Comfort Alarm. A maximum of 80 Load objects can register to
one DLLR. A maximum of 80 output objects can be referenced by
the 80 Load objects.
7. Add a Schedule object referencing the Utility Profile object. This
Schedule is required to reset the Utility Profile object at the end of
each billing period. Enter the name of the Utility Profile object
and schedule the Utility Profile’s Reset attribute to go to 1 at the
time you want a new billing period to start, and to go back to 0
one minute later. Setting back the reset attribute is necessary to
avoid a premature start of the billing period if the Schedule’s fast
clock feature should run.
8. Verify that the energy management application is operating
correctly. Refer to the Troubleshooting section of this document.
A-8 N30 Supervisory Controller User’s Manual
Troubleshooting
This section provides some guidelines for making an energy
management application successful.
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.
Key Concepts
Message Router Purpose
The Message Router object controls where important dynamic system
information is recorded or displayed. This information can include:
• object changes into and out of alarm
• changes offline and online by controllers or other devices
• reports from the system, such as those generated when elements of
the site exceed user defined limits
This information is contained within Status Notification Reports
(SNRs) that are generated by alarm objects and routed to various
destinations for acknowledgment or storage.
Routing SNRs
The SNRs can be routed to defined destinations such as printers and
VT100s. The Message Router and Report Server internal objects
(one per site) are responsible for transmitting and managing
acknowledgement for the defined set of destination devices. The
routing mechanism uses the priority, BACnet event state and
timestamp of non-acknowledged events to provide the oldest, highest
priority SNR to the acknowledging devices. The initiating alarm object
provides this data.
Unacknowledged messages that appear on a VT100 may be replaced
without user acknowledgement if the same event for the same object
occurs before the acknowledgement of the original event. For
example, an analog alarm has a value of High Alarm and is displayed
on a VT100. If the alarm returns to a Normal state and then again goes
into a Normal state, the VT100 displays the data for the newest High
Alarm event.
An acknowledgement message, Acknowledged by: System,
is sent to non-acknowledging devices. Non-acknowledging devices,
such as printers, receive SNRs in the order of their occurrence.
The Message Router feature distributes SNRs from the various
sources. The Message Router examines each SNR and routes it to the
appropriate destinations based on the types of SNRs each destination is
configured to receive.
For information about how SNRs appear on a VT100, refer to the
Getting Started (LIT-6892030) chapter in this manual.
B-4 N30 Supervisory Controller User’s Manual
Filtering
Filtering is done by each destination using the priority, category, and
message type of each SNR received. Two separate filters exist for each
destination: Filter A and Filter B. The filtering operation allows output
of SNRs based on a match on priority, category, and message type.
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 1
Alarm Objects Message Router
(Analog and Multisate) Object 4
VT100 Objects
MR Flow
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.
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 4
Any Binary Object
Optimal Start Object
7 (Warmup and Cooldown)
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.
Procedure Overview
Table C-3: Building an Optimal Start Application
To Do This Follow These Steps:
Build an Optimal Start Add N2 Controller and point objects to the database. Add the Schedule
Application 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.
N30 Supervisory Controller User’s Manual C-5
Detailed Procedures
Building an Optimal Start Application
To build an Optimal Start application:
1. Add N2 Controller and point objects to the database. See the
N30 Supervisory Controller Point Mapping Technical Bulletin
(LIT-6891400) and the Project Builder User’s Guide.
2. Add the Schedule object scheduling the Binary object controlling
zone occupancy. See the Working with Schedule Objects
(LIT-6892070) chapter in this manual or the Adding and Editing
Schedules (LIT-693235)chapter of the Project Builder User’s
Guide.
3. Make sure valid start and stop times are entered into the Schedule
object.
4. Add the Optimal Start object referencing the above Schedule
object, the Binary objects designated as zone occupancy and
warmup/cooldown, and the analog attributes of objects designated
as modes, temperatures, and setpoints. See the Working with
Optimal Start Objects (LIT-6892090) chapter in this manual. Or,
in Project Builder software, drag the Optimal Start collection from
the Devices and Collections folders in the Object Library into the
Energy Container of your N30 database. With the object selected
in the database, select Edit Object on the Edit menu to enter
M-View. In M-View, enter your references and attributes. You
can then download the new database to any N30 that should have
the same Optimal Start settings.
C-6 N30 Supervisory Controller User’s Manual
Troubleshooting
This section provides some solutions for problems in an Optimal Start
application.
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.
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 5
3 1 6
4 7
INTL Flow
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.
Example
Figures D-2 through D-5 show screens from a sample completed
Interlock object. This sample object uses the Logic Equation attribute.
Procedure Overview
Table D-3: Building an Interlock Application
To Do This Follow These Steps:
Build an Interlock Application Consider what the Interlock object needs to do and determine which
objects need to be involved. Make sure all of the objects involved in the
Interlock application are added to the database. Verify/record the exact
object and attribute names involved. Add the Interlock object referencing
all of the required objects.
D-8 N30 Supervisory Controller User’s Manual
Detailed Procedures
Building an Interlock Application
To build an Interlock application:
1. Consider what the Interlock object needs to do and determine
which objects need to be involved.
2. Make sure all of the objects involved in the Interlock application
are added to the database. See the appropriate chapters in this
manual.
3. Verify/record the exact object and attribute names to be involved
in the Interlock application.
4. Add the Interlock object referencing all of the required objects.
See the Working with Interlock Objects (LIT-6892140) chapter in
this manual.
N30 Supervisory Controller User’s Manual E-1
Appendix E
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.
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 5
N2 Analog N2 Analog
Input Object Output Object
(Zone) (Setpoint)
3 1 6
N2 Analog N2 Analog
Signal Select Object
Input Object Output Object
(Zone) (Setpoint)
4 7
N2 Analog N2 Analog
Input Object Output Object
(Zone) (Setpoint)
SSA Flow
receives.
2 5
N2 Binary N2 Binary
Input Object Output Object
(Zone) (Setpoint)
3 1 6
N2 Binary N2 Binary
Signal Select Object
Input Object Output Object
(Zone) (Setpoint)
4 7
N2 Binary N2 Binary
Input Object Output Object
(Zone) (Setpoint)
SSB Flow
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.
Procedure Overview
Table E-4: Building a Signal Select Application
To Do This Follow These Steps:
Build a Signal Select Add N2 Controller and point objects to the database. Verify/record the
Application exact object and attribute names to be involved in the Signal Select
application. Add the Signal Select objects referencing the objects with the
desired analog or binary attributes.
E-6 N30 Supervisory Controller User’s Manual
Detailed Procedures
Building a Signal Select Application
To build a Signal Select application:
1. Add N2 Controller and point objects to the database. See the
N30 Supervisory Controller Point Mapping Technical Bulletin
(LIT-6891400).
2. Verify/record the exact object and attribute names to be involved
in the Signal Select application.
3. Add the Signal Select objects referencing the objects with the
desired analog or binary attributes. See the Working with Signal
Select Objects (LIT-6892150) chapter in this manual.
N30 Supervisory Controller User’s Manual F-1
Appendix F
Introduction
Notification Class objects receive alarm messages and route them to
destinations such as printers and VT100s. They also handle routing
messages requiring acknowledgement to the Report Server object.
Using Notification Class objects to route alarms is one of two alarm
routing options. The Message Router feature can also be used to route
alarms. See Appendix B: Building a Message Router Application
(LIT-6892320) in this manual for information on routing alarms using
the Message Router object. Only one of these two methods can be
used on a site. If routing to third-party (non-Metasys) BACnet devices
is required, then Notification Class objects need to be used for alarm
routing.
This appendix describes aspects of the Notification Class feature,
including how Status Notification Reports are routed, how message
filtering is configured, and how the Notification Class object interacts
with other objects.
For further information about the objects described in this appendix,
see the Working with Notification Class Objects (LIT-6892290)
chapter in this document and the relevant object chapters in the Object
Dictionary. For information about generating N30 databases using
Project Builder, refer to the N30 Supervisory Controller Quick Start
Technical Bulletin (LIT-6891200).
Key Concepts
Routing SNRs
The SNRs are routed to the destinations defined in the Recipient List
of the Notification Class object. These destinations need to be
configured in every Notification Class object. When adding a new
destination, such as a printer, add it to the Recipient List of all
Notification Class objects from which SNRs are desired.
The Notification Class object determines if acknowledgement is
required. (Unlike the Message Router Feature, where the Alarm object
determines if acknowledgement is required). If acknowledgement is
required, the SNRs are also automatically routed to the Report Server
for delivery to VT100s. The Report Server and VT100 function as
described in Appendix B: Building a Message Router Application
(LIT-6892320) in this manual.
One Notification Class object can distributes SNRs from various
sources. The Notification Class object examines each SNR and routes
it to the appropriate destinations based on the types of SNRs each
destination is configured to receive.
For information about how SNRs appear on a VT100, refer to the
Getting Started (LIT-6892290) chapter in this manual.
Filtering
For filtering, configure the Recipient List in the Notification Class
object. Filter options include valid days, times and types of SNRs. See
the Working with Notification Class Objects (LIT-6892290) chapter in
this manual for details.
N30 Supervisory Controller User’s Manual F-3
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 1
Alarm Objects Notification Class
(Analog and Multisate) Object
4
VT100 Objects
BNC Flow