TAC INET Seven System - Technical Reference Guide - New PDF

Technical Reference Guide
I/NET Seven System
Front Cover
TCON300 06/08
ii I/NET Seven Technical Reference Guide
We at TAC have tried to make the information contained in this manual as accurate and reli-
able as possible. Nevertheless, TAC disclaims any warranty of any kind, whether express or
implied, as to any matter whatsoever relating to this manual, including without limitation
the merchantability or fitness for any particular purpose.
Information in this document is based on specifications determined at the time of publica-
tion. As we introduce design enhancements, we reserve the right to make changes in speci-
fications and models without obligation to notify the purchaser. In no event shall TAC be
liable for any indirect, special, incidental, or consequential damages arising out of purchase
or use of this manual or the information contained herein.
The software described in this document is furnished under a license agreement or nondis-
closure agreement. The software may be used or copied only in accordance with the terms
of the agreement. It is against the law to copy TAC I/NET System software onto magnetic
tape, disk, or any other medium for any purpose other than the purchaser's personal use.
Printed in the United States of America.
Document Number: TCON30006/08
Copyright 20012008 TAC. All rights reserved.

TAC and Andover Controls and product names are trademarks of TAC. All other trade-
marks mentioned belong to their respective owners.
iv I/NET Seven Technical Reference Guide
Use of Third Party Software
TAC software is delivered for use on IBM and compatible PCs. While your PC is capable of
running other third-party software while running I/NET, trying to do so may present
general operational difficulties. This is particularly true if the third-party software is
memory-resident. When used as it is intended, the TAC software is also memory-resident.
The use of more than one memory-resident program at the same time may impose unre-
solvable PC system parameter conflicts and may cause one or more of the memory-resident
programs to fail.
No computer system is immune to software viruses, and they can be extremely damaging
should they attack databases and/or operating programs. Such an attack on the I/NET
system may be particularly damaging since its database output is directed toward control.
The only absolute safeguard against viral attack is to prevent any third-party software from
being installed on the same computer with the TAC software. An acceptable safeguard is to
allow only authorized operators to run third party software and to make sure that all such
software is original, direct from a reputable vendor, and that the software has not been
copied from some other machine: i.e., if the seal is broken, dont use it.
TAC makes no claims or commitments regarding the use of any third-party software, other
than MS-DOS and Windows 98/2000/NT/XP in conjunction with the PC programs
supplied by TAC, and offers no support in accommodating the use of same. Furthermore,
TAC accepts no liability for system failures that may result from the use of any third-party
software with TAC software.
I/NET Seven Technical Reference Guide v

vi I/NET Seven Technical Reference Guide
Contents
Chapter 1 System Configuration

Overview . . . . . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-1
I/NET Hardware . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-1
I/NET Software . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-2
I/NET Seven Documentation . . . . .. .. . .. . . . . . . . . . . . . 1-2
Host Workstations . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-3
Minimum System Requirements . . . .. .. . .. . . . . . . . . . . . . 1-3
Software Components . . . . . . . .. .. . .. . . . . . . . . . . . . 1-4
System Communication . . . . . . .. .. . .. . . . . . . . . . . . . 1-5
LAN Communication. . . . . . . . .. .. . .. . . . . . . . . . . . . 1-6
Ethernet LAN . . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-7
TCP/IP . . . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-8
Host LAN . . . . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-9
Controller LAN . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-9
Link Support . . . . . . . . . . . .. .. . .. . . . . . . . . . . . . 1-9
Distributed Link Architecture (DLA) Support .
. .. . . . . . . . . . . . 1-10
DLA Guidelines . . . . . . . . . . . .. .. . . . . . . . . . . . 1-11
Overview of I/NET Link Communications . .. . . . . . . . . . . . 1-12
Benefits of Xenta 527/527-NPRs and DLA-enabled NPRs . . . . . . . . . . 1-15
DLA Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
I/NET Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
The Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
I/NET Seven Authentication . . . . . . . . . . . . . . . . . . . . . 1-18
Database Authentication . . . . . . . . . . . . . . . . . . . . . . 1-18
Filemaster Database Authentication . . . . . . . . . . . . . . . . . 1-19
Authentication Types . . . . . . . . . . . . . . . . . . . . . . . . 1-19
I/NET Seven Technical Reference Guide vii

Configuration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Serial Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Link Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Host Address . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Reference Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
File Equalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
The Filemaster . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Equalized Clients . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Promoting and Demoting Workstations . . . . . . . . . . . . . . . 1-27
Multiple Access . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Client/Server Infrastructure . . . . . . . . . . . . . . . . . . . . . . . 1-28
The Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Remote Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Multiple Access . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
System Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
I/NET System Hardware . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Series 2000 NetPlus Router . . . . . . . . . . . . . . . . . . . . . . . 1-33
Xenta 527/527-NPR . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Xenta 527 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Xenta 527-NPR . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Distributed Control Units . . . . . . . . . . . . . . . . . . . . . . . . 1-35
7700 (Distributed Control Unit) . . . . . . . . . . . . . . . . . . . 1-35
7716 (Process Control Unit) . . . . . . . . . . . . . . . . . . . . . 1-35
7718 (Process Control Unit) . . . . . . . . . . . . . . . . . . . . . 1-36
7728 (I/SITE I/O) . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
7740 (Distributed Control Unit) . . . . . . . . . . . . . . . . . . . 1-36
7750 (Building Manager) . . . . . . . . . . . . . . . . . . . . . . 1-36
7760 (Unitary Controller Interface) with Unitary Controllers . . . . . . 1-37
7770 ICI (MODBUS) . . . . . . . . . . . . . . . . . . . . . . . . 1-37
7780 (Distributed Lighting Control Unit) . . . . . . . . . . . . . . . 1-38
7791 (Door Processor Interface) with Door Processor Units . . . . . . . 1-38
viii I/NET Seven Technical Reference Guide

7792 (Micro Regulator Interface) with Micro Regulators and
Application Specific Controllers . . . . . . . . . . . . . . . . . 1-39
7793 (Micro Control Interface) with Door Processor Units,
Micro Regulators, and Application Specific Controllers . . . . . . . 1-40
7797 (Industrial Controller Interface) . . . . . . . . . . . . . . . . 1-40
7798 (I/SITE LAN) . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
7800 Tap Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
Hand-held Console (HHC) . . . . . . . . . . . . . . . . . . . . . . . 1-42
I/STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
System Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Building an Address . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
UC, DPU, SCU, and MR Addresses . . . . . . . . . . . . . . . . . . . . 1-43
User-defined Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
The Shortcut Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
The Event Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45
Running User-defined Tools . . . . . . . . . . . . . . . . . . . . . . . 1-45
Chapter 2 Communication
7800 Tap Overview . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-1
Host Taps . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-3
Link Taps . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-4
Site Taps . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-4
Printer Taps . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . 2-5
Tap Configuration Editors . . . . . .. . . . . . . . . . . . . . . . . . 2-5
Tap Configuration Parameters . . . .. . . . . . . . . . . . . . . . . . 2-5
Direct-Connect Function . . . . . . .. . . . . . . . . . . . . . . . . . 2-7
Host Workstation Setup for Direct-Connect . . . . . . . . . . . . . . . . . 2-8
Direct Connection to a Host LAN . . . . . . . . . . . . . . . . . . . 2-8
Direct Connection to a Controller LAN . . . . . . . . . . . . . . . . . 2-9
Integrated Dial Function . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Host Workstation Setup for Integrated Dial . . . . . . . . . . . . . . . . 2-10
Modem Setup for Integrated Dial . . . . . . . . . . . . . . . . . . . . 2-11
Call Initiating (Host) End . . . . . . . . . . . . . . . . . . . . . . 2-12
I/NET Seven Technical Reference Guide ix

Call Receiving (78010 Tap) End . . . . . . . . . . . . . . . . . . . 2-12
Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Auto-dial/Auto-answer (AD/AA) Tap Function . . . . . . . . . . . . 2-14
Embedded 4x Dial Tap . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Modem Setup Examples . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Synchronous Modem Settings . . . . . . . . . . . . . . . . . . . . 2-16
Asynchronous Modem Settings . . . . . . . . . . . . . . . . . . . 2-17
7806x Tap Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Telephone Number . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Dial Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Non-Volatile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
7806x Tap Pager Operation . . . . . . . . . . . . . . . . . . . . . . . 2-20
7806x Tap Beeper Operation . . . . . . . . . . . . . . . . . . . . . . . 2-21
7806x Tap Save and Restore . . . . . . . . . . . . . . . . . . . . . . . 2-22
Site Tap Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Site Tap Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Multiple Site Dial Function . . . . . . . . . . . . . . . . . . . . . . . 2-22
Multi-link Dial Function . . . . . . . . . . . . . . . . . . . . . . . . 2-23
NPRs and Xenta 527/527-NPRs . . . . . . . . . . . . . . . . . . . . 2-24
Communication to I/NET . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Downloadable Firmware . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . 2-27
Managing Configurations . . . . . . . . . . . . . . . . . . . . . . 2-30
Diagnostics (NPR only) . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
IP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Filter Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Filter Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
x I/NET Seven Technical Reference Guide

Chapter 3 System Messages
Routing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Reliable Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Buffer Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Reliable Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Defining a Reliable Tap . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Storing Messages During a Communication Failure . . . . . . . . . . . . . 3-8
Retaining Messages During a Power Failure . . . . . . . . . . . . . . . . . 3-9
I/NET AMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
File Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
I/NET AMT Screen . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Window Options Editor . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Alarm Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Alarm Notification . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Alarm Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Event Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Message Display . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Transactions and Alarms . . . . . . . . . . . . . . . . . . . . . . 3-44
Transaction Filter . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
Text Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Image Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Image Verification Configuration Editor . . . . . . . . . . . . . . . 3-49
I/NET Seven Technical Reference Guide xi

Image Verification Door Filter Editor .
. . . . . . . . . . . . . . . . 3-49
CCTV . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 3-50
Archives . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 3-50
Archive Configuration Editor . . . .
. . . . . . . . . . . . . . . . 3-52
Archive Confirmation Editor . . . .
. . . . . . . . . . . . . . . . 3-55
Database Wrap-Around . . . . . . .
. . . . . . . . . . . . . . . . 3-56
Archive Window . . . . . . . . . .
. . . . . . . . . . . . . . . . 3-57
DCU Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Chapter 4 Host Functions

Host Configuration . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Main Window Title . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
SevenTrends Masks . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Group 14. . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Distribution Mask . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Refresh Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Auto AMT startup/shutdown . . . . . . . . . . . . . . . . . . . . . 4-2
Default System Page . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Operator Timeout Action . . . . . . . . . . . . . . . . . . . . . . . 4-2
Operator Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Windows Logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Size/Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Host Passwords . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . 4-3
Function Selection . . . . . .. . . . . . . . . . . . . . . . . . . . . . 4-6
Station Selection . . . . . . .. . . . . . . . . . . . . . . . . . . . . 4-13
Tenant/Group Selection . . . .. . . . . . . . . . . . . . . . . . . . . 4-14
Individual Field Selection . . .. . . . . . . . . . . . . . . . . . . . . 4-14
DCU Password Preassignment . . . . . . . . . . . . . . . . . . . . . . 4-14
Password Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Limited-access Users . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
System Pages (Graphics Editor) . . . . . . . . . . . . . . . . . . . . 4-17
xii I/NET Seven Technical Reference Guide

File Formats . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 4-17
References to Files .
. . . . . . . . . . . . . . . . . . . . . . . . 4-17
Alternate Graphic Paths .
. . . . . . . . . . . . . . . . . . . . . . . . 4-18
Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Link Configuration Summary . . . . . . . . . . . . . . . . . . . . . . 4-21
Site Configuration Summary . . . . . . . . . . . . . . . . . . . . . . 4-21
Station Configuration Summary . . . . . . . . . . . . . . . . . . . . . 4-21
MCU Configuration Summary . . . . . . . . . . . . . . . . . . . . . 4-22
Door Configuration Summary . . . . . . . . . . . . . . . . . . . . . . 4-22
Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
DCU Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
DCU Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Daylight Savings Time . . . . . . . . . . . . . . . . . . . . . . . 4-25
Automatic DCU Save . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Special Day Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Setup (Day Format) . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Broadcast Failure. . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Broadcast Review . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Off-normal Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Disabled Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Database Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Configuration Summaries . . . . . . . . . . . . . . . . . . . . . . . 4-29
Software Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Host Trend Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Host ATS (Automatic Time Schedule) . . . . . . . . . . . . . . . . . 4-33
Phone Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Chapter 5 Controller Functions

Controller Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Configuration and Status . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Control Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
I/NET Seven Technical Reference Guide xiii

Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Memory Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Database Last Changed . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Loading Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Firmware Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Controller Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Distribution Parameters. .. . . . . . . . . . . . . . . . . . . . . . . . 5-4
Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Priority . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 5-5
Reliable Tap . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 5-5
Sunrise/Sunset . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 5-5
Daylight Savings . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 5-6
Program Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Time Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Demand Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
All Lights On/Off . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Editing the Database while Offline . . . . . . . . . . . . . . . . . . . . 5-8
Connecting Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Station Save and Restore . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Station Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Station Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Station Restore on a DPI . . . . . . . . . . . . . . . . . . . . . . 5-10
Station Restore on a DPU or SCU1284 . . . . . . . . . . . . . . . . 5-10
Automatic DPU Restore . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Recording Offline Door Controllers . . . . . . . . . . . . . . . . . 5-11
Restore from Local Host . . . . . . . . . . . . . . . . . . . . . . 5-12
Restore Host Selection . . . . . . . . . . . . . . . . . . . . . . . 5-12
How I/NET Performs the Automatic DPU Restore . . . . . . . . . . . 5-14
The Memory Interface Processor Module . . . . . . . . . . . . . . . . . 5-14
Software Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Dynamic Data Upload . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
xiv I/NET Seven Technical Reference Guide

Station Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Control Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Control Descriptions for Doors . . . . . . . . . . . . . . . . . . . 5-18
State Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Conversion Coefficients Tables. . . . . . . . . . . . . . . . . . . . . . 5-19
Pop-up Calculator . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Calculating Coefficients . . . . . . . . . . . . . . . . . . . . . . . 5-20
Engineering Units Table . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Lookup Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Lookup Table Calculation . . . . . . . . . . . . . . . . . . . . . . 5-24
7728 Lookup Tables . . . . . . . . . . . . . . . . . . . . . . . . 5-28
7756 Thermistor Lookup Table . . . . . . . . . . . . . . . . . . . 5-29
LCD Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Points and Point Extensions . . . . . . . . . . . . . . . . . . . . . . 5-31
Test and Manual Point Control . . . . . . . . . . . . . . . . . . . . . 5-31
Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Special Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Event Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Message Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Report Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
DIF Conversion Actions . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Trend Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Multi-Point Trend Plot . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Trend Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Trend Report Definition . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Plot Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Point Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Trend Plot Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
I/NET Seven Technical Reference Guide xv

Axis Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Plot Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Chapter 6 Input and Output Points
Resident Input/Output Point Types . . . . . .
. . . . . . . . . . . . . 6-1
Discrete Input (DI) Points . . . . . . . . . . . .
. . . . . . . . . . . . . 6-1
Digital Input (GI) Points . . . . . . . . . . . .
. . . . . . . . . . . . . 6-2
Discrete Alarm (DA) Points . . . . . . . . . . .
. . . . . . . . . . . . . 6-3
Analog Input (AI) Points . . . . . . . . . . . .
. . . . . . . . . . . . . 6-4
Pulsed Input (PI) Points . . . . . . . . . . . .
. . . . . . . . . . . . . 6-4
Analog Output (AO) and Pulse Width Modulated (PWM) Output Points . . . . 6-5
Digital Output (GO) Points . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Discrete Output (DO) Points . . . . . . . . . . . . . . . . . . . . . . . 6-8
Discrete Monitor (DM) and Discrete Control (DC) Points . . . . . . . . . . 6-8
Global and Indirect Points . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Sending Information . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Old Data State . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Indirect Points in subLAN Devices . . . . . . . . . . . . . . . . . . 6-13
Input and Output Addressing . . . . . . . . . . . . . . . . . . . . . 6-13
Point Database Parameters . . . . . . . . . . . . . . . . . . . . . . . 6-13
Point Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Point Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Scan Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Global Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Alarm Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Distribution Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Message Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Cell Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
State Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Number of Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
1-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
2-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
3-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
xvi I/NET Seven Technical Reference Guide

Normal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Alarm Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Control Description . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Momentary Duration . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Expected State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Restart Control Action . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Minimum Trip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Minimum Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Time To State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Three-State Output. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Monitor Point Address . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Conversion Equation . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Conversion Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Low Sensor Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
High Sensor Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Low Alarm Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
High Alarm Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Broadcast Change Counts . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Non-linear Lookup Table . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Accumulator Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Scans Between Broadcast . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Supervised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Chapter 7 Point Extensions
Alarm Inhibit (AI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Calculations (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Selecting a Calculated Point Address . . . . . . . . . . . . . . . . . . . . 7-5
Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Boolean Operators . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Relational Operators . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Arithmetic Operators . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Function Operators . . . . . . . . . . . . . . . . . . . . . . . . 7-11
I/NET Seven Technical Reference Guide xvii

Thermodynamic Function Operators . . . . . . . . . . . . . . . . . 7-14
Helpful Hints for Calculations . . . . . . . . . . . . . . . . . . . . . . 7-15
Consumption (CN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Demand Control (DC) . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Demand Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Demand Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Elevator (EL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Event Definition (EV). . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Lighting Control (LC) . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Lighting Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Lighting Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Override Billing (OB) . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Some Important Information Before You Begin . . . . . . . . . . . . . . 7-34
Access Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Equipment Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Override Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Runtime (RT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Temperature Control (TC) . . . . . . . . . . . . . . . . . . . . . . . 7-39
Trend Sampling (TR) . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Time Scheduling (TS). . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Independent and Master Schedules . . . . . . . . . . . . . . . . . . . . 7-47
Slave Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
Chapter 8 Dynamic Control
Time Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Time Scheduling Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Normal Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Temporary Schedules . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Special Day Schedules . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Special Days Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
xviii I/NET Seven Technical Reference Guide

Temperature Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Temperature Control Editor . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Equations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Mode Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Optimized Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Optimized Start and Stop . . . . . . . . . . . . . . . . . . . . . . . 8-8
Demand Control Override . . . . . . . . . . . . . . . . . . . . . . . 8-11
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Demand Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Monitoring Consumption . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Daily Consumption . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Monthly Consumption . . . . . . . . . . . . . . . . . . . . . . . 8-16
Calculating Demand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Projected Demand . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Current Demand . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Shedding Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Selecting Loads to Shed . . . . . . . . . . . . . . . . . . . . . . . 8-21
Load Shedding Process . . . . . . . . . . . . . . . . . . . . . . . 8-22
Restoring Loads . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Measurement and Forecasting . . . . . . . . . . . . . . . . . . . . . . 8-23
Chapter 9 Access Control
Access Control Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Firmware-specific Parameters and Options . . . . . . . . . . . . . . . 9-4
Key/Card Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Large Number Support . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Large Number Guidelines . . . . . . . . . . . . . . . . . . . . . . . 9-6
Hexidecimal Number Support . . . . . . . . . . . . . . . . . . . . . . . 9-7
Key/Card Data Formats and Conversions . . . . . . . . . . . . . . . . . . 9-7
Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
26-bit Wiegand Format . . . . . . . . . . . . . . . . . . . . . . . . 9-8
I/NET Seven Technical Reference Guide xix

32-bit Wiegand Format . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Database Caching in the Door Controller . . . . . . . . . . . . . . . 9-10
SLI Storage Capacities . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
SLI and Door Controller Cache Interaction . . . . . . . . . . . . . . . . 9-11
Managing Cache Space in the Door Controller . . . . . . . . . . . . . . . 9-13
Access Control Configuration . . . . . . . . . . . . . . . . . . . . . 9-13
Order of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Audit Trail Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Recycle Bin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Deleting an Individual . . . . . . . . . . . . . . . . . . . . . . . 9-17
Deleting a Tenant . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Restoring Records from the Recycle Bin . . . . . . . . . . . . . . . . 9-17
Purging Records . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
DPU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Doors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Reader and Door Parameters . . . . . . . . . . . . . . . . . . . . . . 9-20
Reader Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
PIN Pad or PIN Type . . . . . . . . . . . . . . . . . . . . . . . . 9-21
PIN Message Enable . . . . . . . . . . . . . . . . . . . . . . . . 9-22
PIN Retry Count . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Exit Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
User Defined Length . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Intercard Interval (sec) . . . . . . . . . . . . . . . . . . . . . . . 9-24
LED Polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Elevator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Card Translation . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Anti-passback . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Anti-tailgate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Entry and Exit Zone Number . . . . . . . . . . . . . . . . . . . . 9-26
Anti-passback Reset Time . . . . . . . . . . . . . . . . . . . . . . 9-29
Door Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Door Strike . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
xx I/NET Seven Technical Reference Guide

Strike Duration . . . . . . . . . . . . . . . . .. . . . . . . . . 9-30
Door Open Too Long . . . . . . . . . . . . . . .. . . . . . . . . 9-30
Door Sense Switch . . . . . . . . . . . . . . . .. . . . . . . . . 9-30
Door Release Switch . . . . . . . . . . . . . . .. . . . . . . . . 9-31
Re-lock Timer . . . . . . . . . . . . . . . . . .. . . . . . . . . 9-31
Shunt . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 9-31
First Key Auto-unlock . . . . . . . . . . . . . .. . . . . . . . . 9-31
Door Closed Timer . . . . . . . . . . . . . . . .. . . . . . . . . 9-32
Mode Schedules . . . . . . . . . . . . . . . . . . .. . . . . . . . . 9-33
Action . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 9-33
First Key Mode . . . . . . . . . . . . . . . . .. . . . . . . . . 9-35
User-definable Door Attributes and PIN Pad Functions . .. . . . . . . . . 9-36
Assigning Points to PIN Pad Functions . . . . . . .. . . . . . . . . 9-36
Assigning Points in an SCU1284 Controller . . . . .. . . . . . . . . 9-37
Intruder Alarm System Functions . . . . . . . . .. . . . . . . . . 9-37
Using PIN Pad Functions . . . . . . . . . . . . .. . . . . . . . . 9-38
Using Door Attributes . . . . . . . . . . . . . .. . . . . . . . . 9-43
Resetting the Anti-Passback Flag . . . . . . . . . . . .. . . . . . . . . 9-44
Automatic (Timed) Reset . . . . . . . . . . . . .. . . . . . . . . 9-44
Manual Reset . . . . . . . . . . . . . . . . . .. . . . . . . . . 9-45
Elevators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
Elevator Control Schemes . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Traditional Elevator Control . . . . . . . . . . . . . . . . . . . . . 9-46
Extended Elevator Control . . . . . . . . . . . . . . . . . . . . . 9-47
Implementing Elevator Control . . . . . . . . . . . . . . . . . . . . . 9-48
Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . 9-48
Combining Traditional and Extended Elevator Control . . . . . . . . . 9-49
Elevator Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Elevator Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Floor Selection time . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Floors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Personnel Schedules and Shift Rotations . . . . . . . . . . . . . . . . 9-52
Personnel Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
I/NET Seven Technical Reference Guide xxi

End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Days of the Week . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Special Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Temporary Schedules . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
Shift Rotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Rotation List and Order . . . . . . . . . . . . . . . . . . . . . . . 9-55
Rotation Start . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Rotation Properties . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Access Initiated Control. . . . . . . . . . . . . . . . . . . . . . . . . 9-56
Control Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 9-56
Doors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-57
Individual Numbers . . . . . . . . . . . . . . . . . . . . . . . . 9-57
Key/Card Translations . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Tenant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Tenant Number . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
Tenant Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
Tenant Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
First Individual Number . . . . . . . . . . . . . . . . . . . . . . 9-60
Number of Individuals . . . . . . . . . . . . . . . . . . . . . . . 9-61
Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Group Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Record Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Begin Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
End Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Door Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Individuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Individual Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
xxii I/NET Seven Technical Reference Guide

New Individual Number . . . . . . . . . . . . . . . . . . . . . . 9-65
Card Number . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Group Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Last Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
First Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Fields 3-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-67
Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-68
Record Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-69
Temporary Schedule . . . . . . . . . . . . . . . . . . . . . . . . 9-69
APB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-70
PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Issue Number . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Door Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Selectively Assigning Doors to the Individual . . . . . . . . . . . . . 9-72
Assigning Group Doors to the Individual . . . . . . . . . . . . . . . 9-72
Assigning Secondary Group Doors to the Individual . . . . . . . . . . 9-72
GOTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73
Allocate Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-74
Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-75
Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-75
Permanent Records . . . . . . . . . . . . . . . . . . . . . . . . . 9-75
Temporary Records. . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Disabled Records . . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Display Order . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Low/High Individual Number . . . . . . . . . . . . . . . . . . . . 9-76
ASCII Text Fields. . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
Personal Identification Numbers (PINs) . . . . . . . . . . . . . . . . 9-77
Entering Your PIN at a Door . . . . . . . . . . . . . . . . . . . . . . 9-77
Omitting Leading Zeros . . . . . . . . . . . . . . . . . . . . . . . . . 9-78
Door Controller Firmware Revisions . . . . . . . . . . . . . . . . . . . 9-78
User-defined PINs . . . . . . . . . . . . . . . . . . . . . . . . . 9-78
Six-digit PINs . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-79
Generating PINs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-79
I/NET Seven Technical Reference Guide xxiii

Combining Individual and Group Record Types. . . . . . . . . . . . 9-79
Group Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-81
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-83
Supply Card Number from Reader . . . . . . . . . . . . . . . . . . 9-83
Second Password Required for Individuals . . . . . . . . . . . . . . 9-83
Audit Trail Distribution Group . . . . . . . . . . . . . . . . . . . 9-84
Audit Trail Distribution Mask . . . . . . . . . . . . . . . . . . . . 9-84
Audit Trail Cell Number . . . . . . . . . . . . . . . . . . . . . . 9-84
DPU Dial Type. . . . . . . . . . . . . . . . . . . . . . . . . . . 9-84
DPU Dial Delay/Schedule . . . . . . . . . . . . . . . . . . . . . . 9-85
User Defined PIN . . . . . . . . . . . . . . . . . . . . . . . . . 9-85
PIN Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-86
Recycle Bin Enable . . . . . . . . . . . . . . . . . . . . . . . . . 9-86
Recycle Bin Autopurge Age . . . . . . . . . . . . . . . . . . . . . 9-86
Empty Recycle Bin at Log Off . . . . . . . . . . . . . . . . . . . . 9-87
Unique User Field . . . . . . . . . . . . . . . . . . . . . . . . . 9-87
Individual Activity Manager - Configure . . . . . . . . . . . . . . . 9-87
Individual Activity Manager . . . . . . . . . . . . . . . . . . . . . . 9-88
Monitoring Door Controller Activity . . . . . . . . . . . . . . . . . . . 9-88
Per Individual Settings . . . . . . . . . . . . . . . . . . . . . . . . . 9-89
Dial After Edit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-89
Two-man Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-90
Configuring I/NET to Use the Two-man Rule. . . . . . . . . . . . . . . . 9-90
Sequence of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-91
Chapter 10 Direct Digital Control
Input and Output Designations . . . .. . . . . . . . . . . . . . . . 10-1
Points . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 10-2
Lines . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 10-2
Constants . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 10-2
DDC Modules. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 10-3
Two-Position Module (Two-Pos) . . . . .. . . . . . . . . . . . . . . . 10-3
Proportional, Integral, Derivative Module (PID) . . . . . . . . . . . . . . 10-4
xxiv I/NET Seven Technical Reference Guide

PID Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
P-only Mode of Operation . . . . . . . . . . . . . . . . . . . . . 10-7
PID Tuning Parameters . . . . . . . . . . . . . . . . . . . . . . . 10-8
PID Equation Examples . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Proportional Corrections . . . . . . . . . . . . . . . . . . . . . . 10-8
Integral Corrections . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Derivative Corrections . . . . . . . . . . . . . . . . . . . . . . . 10-15
Floating Module (FLOAT). . . . . . . . . . . . . . . . . . . . . . . . 10-19
Floating Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Floating Module Tuning Parameters . . . . . . . . . . . . . . . . . 10-21
Reset Module (RESET) . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
HiLo Module (HILO). . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Relay Module (RELAY) . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Calculation Module (CALC). . . . . . . . . . . . . . . . . . . . . . . 10-24
DDC Module Parameters . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Module Number and Name . . . . . . . . . . . . . . . . . . . . . . . 10-26
Sample Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Setpoint Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Setpoint Differential . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
Setpoint Low Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28
Setpoint High Limit . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Process Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Process Variable Filter . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Increase Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Decrease Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
High Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Low Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Output Ramp Limit . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Output Low Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Output High Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Output Control Point (Failsafe) . . . . . . . . . . . . . . . . . . . . . 10-36
Output Throttling Range . . . . . . . . . . . . . . . . . . . . . . . . 10-36
I/NET Seven Technical Reference Guide xxv

Output Turn-around Time . .
. . . . . . . . . . . . . . . . . . . . . 10-37
Output Proportional Band . .
. . . . . . . . . . . . . . . . . . . . . 10-37
Output Reset Interval . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-39
Output Rate Interval . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-39
Failsafe Command . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-40
Output Mode . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-41
Adaptive Control . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-42
Maximum Bump . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-43
Settling Time . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-43
Maximum Overshoot . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-44
Target Damping . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-44
Noise Band . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-45
Primary Input . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-45
Primary Inputs 1 and 2 . . . .
. . . . . . . . . . . . . . . . . . . . . 10-45
Primary Outputs 1 and 2 . . .
. . . . . . . . . . . . . . . . . . . . . 10-46
Secondary Input . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-46
Secondary Inputs 1 and 2 . . .
. . . . . . . . . . . . . . . . . . . . . 10-47
Secondary Outputs 1 and 2 . .
. . . . . . . . . . . . . . . . . . . . . 10-47
Inputs 1 4 . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-48
DI = 0 . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-48
DI = 1 . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-48
Settings (Relay Types). . . . .
. . . . . . . . . . . . . . . . . . . . . 10-48
Time Delay . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-49
DI Select . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-50
History . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-50
Tuning. . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-50
Manual Tune . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-51
Setpoint . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 10-51
Proportional Band (percent). . . . . . . . . . . . . . . . . . . . . 10-51
Reset interval (seconds) . . .
. . . . . . . . . . . . . . . . . . . . 10-51
Rate Interval (seconds) . . .. . . . . . . . . . . . . . . . . . . . 10-51
Input/Output Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-51
Automatic Tune . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-52
Automatic Tuning Parameters . . . . . . . . . . . . . . . . . . . . 10-52
xxvi I/NET Seven Technical Reference Guide

Automatic Tuning Process. . . . . . . . . . . . . . . . . . . . . . 10-52
Adaptive Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-55
Adaptive Tuning Parameters . . . . . . . . . . . . . . . . . . . . . 10-55
Adaptive Tuning Process . . . . . . . . . . . . . . . . . . . . . . 10-55
Chapter 11 Unitary Control
The Parent Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Configuring the Unitary Controller Interface . . . . . . . . . . . . . 11-2
UC/UCI Editor Location . . . . . . . . . . . . . . . . . . . . . . . . 11-4
UCI Resident Programming . . . . . . . . . . . . . . . . . . . . . . . 11-4
UC Resident Programming . . . . . . . . . . . . . . . . . . . . . . . 11-5
UC Editor Theory of Operation . . . . . . . . . . . . . . . . . . . . 11-5
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
UC Damper/Valve Control . . . . . . . . . . . . . . . . . . . . . . . 11-7
VAV Box Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
AHU Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Heat Pump (HPMP) Control . . . . . . . . . . . . . . . . . . . . . . 11-16
AHU and HPMP Damper Control . . . . . . . . . . . . . . . . . . . . 11-19
Other Control Features . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Remote Setpoint Adjustment . . . . . . . . . . . . . . . . . . . . 11-20
Remote Override . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Conversion of Velocity Pressure to CFM (VAV only) . . . . . . . . . . 11-23
Lini-Temp Temperature Sensors . . . . . . . . . . . . . . . . . . . 11-25
Warmup/Cooldown (AHU and HPMP only) . . . . . . . . . . . . . 11-26
Interlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26
Creating the UC/UCI Database. . . . . . . . . . . . . . . . . . . . . 11-28
Unitary Control Parameters . . . . . . . . . . . . . . . . . . . . . . 11-29
Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Cooling Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Cooling Economy . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Cooling Normal . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Heating Normal . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
Heating Economy . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
I/NET Seven Technical Reference Guide xxvii

Heating Setback . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Setpoint Adjustment . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Timed Override . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Timed Override Indicator . . . . . . . . . . . . . . . . . . . . . . 11-33
Timed Override Duration . . . . . . . . . . . . . . . . . . . . . . 11-33
Economy Override . . . . . . . . . . . . . . . . . . . . . . . . . 11-33
Damper Override (VAV only) . . . . . . . . . . . . . . . . . . . . 11-34
Warmup/Cooldown (AHU, HPMP only) . . . . . . . . . . . . . . . 11-34
Inputs and Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
Space Temperature . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Central Plant Heat (VAV only) . . . . . . . . . . . . . . . . . . . . 11-35
Temperature Setpoint (VAV only) . . . . . . . . . . . . . . . . . . 11-35
Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Cooling Fan Control (VAV only) . . . . . . . . . . . . . . . . . . . 11-36
Heating Fan Control (VAV only) . . . . . . . . . . . . . . . . . . . 11-36
Stage 1 Heating (VAV and AHU only) . . . . . . . . . . . . . . . . 11-36
Activation Delay (VAV only) . . . . . . . . . . . . . . . . . . . . . 11-36
Stage 2 Heating Setpoint Offset (VAV and AHU only) . . . . . . . . . 11-37
Stage 3 Heating Setpoint Offset (VAV and AHU only) . . . . . . . . . 11-37
Fan Control (AHU and HPMP only) . . . . . . . . . . . . . . . . . 11-37
Stage 1 Cooling (AHU only) . . . . . . . . . . . . . . . . . . . . . 11-37
Interstage Delay (AHU and HPMP only) . . . . . . . . . . . . . . . 11-37
Stage 2 Cooling Setpoint Offset (AHU only) . . . . . . . . . . . . . . 11-38
Stage 3 Cooling Setpoint Offset (AHU only) . . . . . . . . . . . . . . 11-38
Reversing Valve (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-38
Compressor #1 (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-39
Compressor #2 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-39
xxviii I/NET Seven Technical Reference Guide

Compressor #3 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-40
Heater Strip #1 (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-40
Heater Strip #1 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-40
Damper Control (AHU and HPMP only) . . . . . . . . . . . . . . . 11-41
PID Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-41
Setpoint (DO-PID only) . . . . . . . . . . . . . . . . . . . . . . 11-41
Input (Process Variable) . . . . . . . . . . . . . . . . . . . . . . 11-41
Input Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-41
Input Low Limit . . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
Input High Limit. . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-42
Output Control Point. . . . . . . . . . . . . . . . . . . . . . . . 11-42
Output Ramp Limit . . . . . . . . . . . . . . . . . . . . . . . . 11-42
Output Low Limit . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
Output High Limit . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
Proportional Band . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
Reset Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
Rate Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-43
FLT Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Setpoint (DO-FLT only) . . . . . . . . . . . . . . . . . . . . . . 11-44
Input (Process Variable) . . . . . . . . . . . . . . . . . . . . . . 11-44
Input Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Input Low Limit . . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Input High Limit. . . . . . . . . . . . . . . . . . . . . . . . . . 11-44
Output (Increase) . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Output (Decrease) . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Throttling Range . . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Turn-Around Time . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Proportional Band . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
Reset Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-45
I/NET Seven Technical Reference Guide xxix

Rate Interval .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
Mode . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-46
General (Universal)Unitary Controller . . . . . . . . . . . . . . . . . 11-46
Chapter 12 Micro Regulator Control

Micro Regulator Configuration. . . . . . . . . . . . . . . . . . . . . 12-1
Creating the MRI Database . . . . . . . . . . . . . . . . . . . . . . . 12-3
MR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Entry Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
LED Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Hardware Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Lookup Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
MR88, MR632, MR160, and MR88R Lookup Tables . . . . . . . . . . 12-7
MR55X Lookup Tables . . . . . . . . . . . . . . . . . . . . . . . 12-8
Standalone ATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Direct Digital Control Modules . . . .. . . . . . . . . . . . . . . . 12-10
Calculation Module . . . . . . . . . .. . . . . . . . . . . . . . . . 12-11
MR-to-MR Copy . . . . . . . . . . . .. . . . . . . . . . . . . . . . 12-11
Micro Regulator Editors . . . . . . . .. . . . . . . . . . . . . . . . 12-11
MCI, MRI, or I/SITE LAN Resident Programming . . . . . . . . . . . . . 12-12
MR-Resident Programming . . . . . . . . . . . . . . . . . . . . . . . 12-12
Chapter 13 Application Specific Controllers
Displaying ASC Data . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Setpoint Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Air Status (MR-VAV only) . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Modifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Modifying ASC Names . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Copying ASC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 13-6
xxx I/NET Seven Technical Reference Guide

Saving and Restoring ASC Parameters . . . . . . . . . . . . . . . . . 13-7
Updating the Interface Controller . . . . . . . . . . . . . . . . . . . 13-7
Removing ASC Points from the Interface Controller . . . . . . . . . 13-8
Updating the ASC. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Order of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Free Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
ASC Related Editors . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Chapter 14 7771 Industrial Controller Interface

Assigning a Station Address . . . . . . . . . . . . . . . . . . . . . . 14-1
Configuring the 7771 . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Points and Addressing . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
MODBUS Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
MODBUS PLC Point Types . . . . . . . . . . . . . . . . . . . . . . . 14-4
Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Input Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Holding Registers . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Point and Database Mapping . . . . . . . . . . . . . . . . . . . . . . 14-5
Mapping the ICI on the Controller LAN . . . . . . . . . . . . . . . . . 14-5
Mapping the ICI on the MODBUS . . . . . . . . . . . . . . . . . . . . 14-6
ICI Mapping Conversion . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Point Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Point Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Scan Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Chapter 15 SevenTrends
SevenTrends Data Storage . . . . . . . . . . . . . . . . . . . . . . . 15-3
Collecting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Simple I/NET Configurations . . . . . . . . . . . . . . . . . . . . 15-4
I/NET Seven Technical Reference Guide xxxi

Complex I/NET Configurations . ..
. . . . . . . . . . . . . . . . 15-6
Dial I/NET Configurations . . . ..
. . . . . . . . . . . . . . . . 15-6
Data Transfer Schedules . . . . . ..
. . . . . . . . . . . . . . . . 15-8
Troubleshooting . . . . . . . . ..
. . . . . . . . . . . . . . . . 15-9
SevenTrends Types . . . . . . . . . ..
. . . . . . . . . . . . . . . . 15-9
Defining Trends . . . . . . . . . . . ..
. . . . . . . . . . . . . . . . 15-10
SevenTrends Parameters Editor . . . ..
. . . . . . . . . . . . . . . . 15-11
Point Selection Editor . . . . . . . . ..
. . . . . . . . . . . . . . . . 15-13
Modifying and Deleting Trends . . . ..
. . . . . . . . . . . . . . . . 15-14
Using Cells to Generate Trend Definitions .. . . . . . . . . . . . . . . . 15-14
Modifying Cell Definitions . . . . . . . . . . . . . . . . . . . . . 15-15
DCU Editors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
SevenTrends Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
Inquiry Date Range . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-19
SevenTrends Data Summary . . . . . . . . . . . . . . . . . . . . . . . 15-20
Modifying SevenTrends Data . . . . . . . . . . . . . . . . . . . . . . 15-22
Deleting SevenTrends Data . . . . . . . . . . . . . . . . . . . . . . . 15-22
SevenTrends Data Management . . . . . . . . . . . . . . . . . . . . 15-22
Database Size Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22
Sample Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23
SevenTrends Messages . . . . . . . . . . . . . . . . . . . . . . . 15-24
SevenTrends Transfer Configuration Editor . . . . . . . . . . . . . . . . 15-25
Archiving SevenTrends Data . . . . . . . . . . . . . . . . . . . . . . . 15-28
Appendix A DCU Control Hierarchy
Appendix B Time Zone Map
Appendix C Controller Point Addressing
Glossary
Index
CHAPTER
1
46
System Configuration
Overview
I/NET Seven is an integrated solution for building management
that combines environmental control, access control, and energy
management. I/NET Seven can be customized for any building
management application including small office buildings,
skyscrapers, office and school campuses, buildings with specialized
environmental control requirements, and remote sites. The I/NET
system includes both hardware and software solutions.
I/NET Hardware
The hardware solutions are:
Sensing and controlling devices such as sensors, actuators,
transducers, signal converters, door sensors, and door strikes.
Controllers which provide the ability to monitor and control
environmental and access devices. Information may be shared
with multiple controllers by linking them together on a
controller LAN.
Host workstations run the I/NET Seven software to monitor,
control, and report on all aspects of the building management
system. Host workstations may be linked together on a host
LAN or commercial Ethernet LAN.
Taps and NetPlus Routers provide communication links
between the various network levels of the I/NET system.
I/NET Seven Technical Reference Guide 1-1

Overview System Configuration
I/NET Software
The I/NET Seven software is a 32-bit open-architecture platform
which provides a friendly, comprehensive, and customizable set of
tools that control and monitor the I/NET network. The software
employs a non-proprietary database engine that can use either of
the following database servers:
Microsoft SQL Server 2000 A comprehensive database
package that includes analysis and management tools. This
software must be purchased through a third party.
Microsoft MSDE 2000 A freeware successor to the data-
base engine used in previous versions of I/NET. This software
is distributed with I/NET Seven.
Note: The MSDE 2000 server software distributed with I/NET Seven
imposes a 2 GB restriction on database size. Larger facilities, particu-
larly those using image verification and/or AMT archiving, could
potentially encounter data storage problems due to this restriction,
and should consider upgrading to SQL Server 2000.
When using MSDE 2000, we recommend that you limit your system
to no more than five concurrent I/NET users. As you exceed this
recommended limit, database performance can begin to degrade.
Consider upgrading to SQL Server 2000 if your facility typically
requires more than 5 concurrent I/NET users.
The software also includes a specialized graphics editor for creating

graphical displays of your I/NET system, and utilities to export data
and create custom reports.
I/NET Seven Documentation

I/NET Seven documentation is composed of the following guides:
TCON298, I/NET Seven Getting Started
TCON299, I/NET Seven Operator Guide
TCON300, I/NET Seven Technical Reference Guide
TCON301, I/NET Seven Database Connectivity and Reporting
1-2 I/NET Seven Technical Reference Guide

System Configuration Host Workstations
In addition to the printed documentation listed above, a compre-

hensive, context sensitive on-line help system is available in the
I/NET Seven software.
TCON298, I/NET Seven Getting Started, and TCON299, I/NET
Seven Operator Guide, provide step-by step guidance on how to
configure and use the I/NET Seven software. This Technical Refer-
ence Guide provides supplementary technical information on how
I/NET actually works.
Host Workstations
I/NET uses one or more workstations to run host software,
allowing you to perform programming, record keeping, and system
communication with the controllers, and ultimately, your environ-
mental or access control equipment.
Minimum System Requirements

The minimum recommended configuration for a host workstation
running I/NET Seven is:
Pentium III (500 MHz)
256 MB RAM for a standalone workstation or equalized
client.
512 MB RAM for a filemaster.
3 GB of available hard drive space.
Note: The use of Image Verification, AMT Archiving, or
Microsoft SQL 2000 Server will require additional disk space.
CD-ROM drive
Video display of 800 600
Microsoft Windows 2000, Windows XP Professional, or
Windows Server 2003
Notes: I/NET Seven will not run on a Windows workstation that is config-
ured as a Domain Controller.
You must have administrative privileges in order to install programs
on a Windows workstation.

Host Workstations System Configuration
Your Windows system must be configured to use NTFS in order to

support electronic file encryption (EFS).
Sound card and speakers (required for AMT audible alarms)

While not required, an uninterruptable power supply (UPS)
is highly recommended.
If you plan to use I/NET with an Ethernet LAN, you must also have
a valid LAN connection that includes the following:
Microsoft TCP/IP
Properly assigned static IP address
IP Mask
Gateway IP address
If you plan to print event action messages from your workstation,
you must also have the following:
A printer capable of printing single lines of text without
ejecting the page between each line. Dot-matrix printers typi-
cally support this single line feed capability and are recom-
mended for use as the event printer.
Please contact your network system administrator if you have any
questions on these requirements.
Caution: The database server should not be shut down while I/NET is
running. Shutting down the database server drops all existing
connections to the database, and can result in corrupted data
displays. (Only users with administrative privileges on the worksta-
tion can stop or start the database server.)
Software Components
The I/NET Seven software consists not only of the main host soft-
ware, but also includes several companion programs that perform
specialized functions. Table 1-1 contains a list of the primary soft-
ware components and a brief description of their specific function.

System Configuration System Communication
Table 1-1. I/NET Software Components

Component Description
I/NET Host Software (INETW) Primary host workstation software.
Handles all required functions for receiving and acknowledging
Alarms, Messages,
alarms, messages, and transactions. AMT is started by INETW and
Transactions (AMT)
cannot be run independently.
A utility program that specifies system and communication
Configure
parameters. Configure is also used for NetPlus Router configuration.
A companion program that performs the majority of the host
workstation communication functions. I/O Server is launched
I/O Server
automatically by INETW. It should be configured to run as a
background task when I/NET is shut down.
This programs primary functions is to transfer I/NET system
messages to the database file. SQL Server is launched
automatically by INETW and will run as a background task, along
with I/O Server, when I/NET is shut down.
SQL Server Caution: The database server should not be shut down while I/NET
is running. Shutting down the database server drops all
existing connections to the database, and can result in
corrupted data displays. (Only users with administrative
privileges on the workstation can stop or start the
database server.)
A utility program that specifies the parameters for archiving system
Archive Configure
events (alarms, messages, and transactions).
System Communication
Your I/NET host workstation needs to communicate with many
external devices, including other host workstations, NPRs, Xenta
527/527-NPRs, Taps, and controllers. I/NET uses a companion
program, I/O Server, to facilitate efficient communication func-
tions.
I/O Server must be running for most I/NET communication func-
tions to occur. Each time it is started, I/NET launches I/O Server,
which runs in the background. By default, I/O Server continues to
run as a background task even after I/NET is shut down. This
enables your host software to continue to receive I/NET data even
if the host software is not operating. Should you need to disable the

LAN Communication System Configuration
I/O Server temporarily, you can shut it down manually. You can
also instruct I/NET to shut down all I/NET-related background
tasks automatically.
When I/O Server is running, an icon is visible in the Windows
system tray. The specific icon loaded will depend upon whether the
workstation is directly connected to a Tap. Right-clicking on the
icon allows you to manually shut down I/O Server, start the config-
uration program, or start the archive configuration program.
LAN Communication
The I/NET system is made of a series of LANs that perform
different functions according to the equipment to which they are
connected.
Configure your system with between one and 6,400 LANs, and up
to 4.096 million monitored/controlled points. The system auto-
matically reconfigures the LAN if a controller fails, to keep things
running smoothly.
I/NET forms a tiered hierarchy of up to four LAN types (see
Figure 1-1):
Ethernet LAN The Ethernet LAN is at the top of the I/NET
structure and can be used to connect multiple host worksta-
tions, via TCP/IP. NetPlus Routers (NPR) and Xenta
527/527-NPRs provide access from the Ethernet LAN directly
to the Controller LAN.
Host LAN Below the Ethernet LAN is the host LAN. Host
workstations connect to the host LAN through specialized
communication devices called Taps.
Controller LAN Below the host LAN is the controller LAN
where the controllers reside. Controller LANs use Taps to
connect to the host LAN and NetPlus Routers to connect
directly to an Ethernet LAN. Controllers connect to the
controller LAN directly, without the use of an adapter or Tap.

System Configuration LAN Communication
Figure 1-1. LAN hierarchy showing possible configurations
Controller subLAN Some controllers, such as the Micro

Regulator Interface, Micro Controller Interface, Unitary
Controller Interface, and the I/SITE LAN, provide subLAN
connections. Unitary controllers, Door Processing Units, and
Micro Regulators reside on subLANs.
Ethernet LAN
I/NET Seven supports Ethernet LAN communication, allowing
you to take advantage of an existing Ethernet commercial network.
There is no need to run special cable or separate network commu-
nication.
Host workstations, NetPlus Routers (NPRs), and Xenta
527/527-NPRs connect to the LAN through Ethernet adapters
installed in each device. Host workstations and Xenta
527/527-NPRs may use a 10 MBPS or 100 MBPS Ethernet
segment. However, NPRs require a 10 MBPS segment. The system

network topology can take almost any shape and can be

constructed of 10-base T (shielded twisted pair), 10-base 2 (Coax),
or fiber optic interfaced devices.
You may connect up to 250 host workstations and 99 NPRs or
Xenta 527/527-NPRs on a single Ethernet LAN/WAN. Connection
is not limited to a single site and may be made through either dial
or Internet connections.
TCP/IP
I/NET Seven uses industry-standard TCP/IP communication
protocols to communicate between host workstations, NPRs, and
Xenta 527/527-NPRs to transfer controller data, route messages
and alarms, and to equalize files.
TCP/IP is actually two protocols, defined below, that are
commonly used together to transfer data across networks.
Transmission control protocol (TCP) This protocol divides
information into packets that are small enough to be transferred
across the network. When a packet reaches its destination, TCP
verifies that the packet has arrived intact. Finally, after all the
packets arrive, it reassembles them into a complete structure.
Internet Protocol (IP) This protocol is responsible for the actual
routing of the data across a network (i.e., determining a path from
point A to point B).
I/NET can exist on a pure TCP/IP network or on a mixed protocol
Ethernet such as NetWare and TCP/IP.
Note: I/NET requires Microsofts TCP/IP protocol. While I/NET Seven can
coexist with another vendors networking software, (Novell or
Banyan, for example) it will not use any other version of TCP/IP. You
can add Microsofts TCP/IP in the Network options of the Control
Panel.
See Also: The section on Setup and Network Configuration in TCON299,

I/NET Seven Operator Guide, and I/NET Configuration in
TCON298, I/NET Seven Getting Started.

Host LAN
A host LAN supports up to 8 Host Taps and 16 Link Taps. Each
Host Tap can connect directly to a workstation or indirectly to a
workstation through a modem. Use the host LAN to connect
multiple host workstations over a large area, segregating functions
at each station. Devices on the host LAN communicate with each
other at 19.2 Kbaud or 9600 baud. The host LAN reconfigures
automatically as devices are added or removed.
Controller LAN
All controllers reside on a controller LAN. The controller LAN can
hold up to 32 controllers on a segment of the LAN. Using a 7808
repeater Tap, you can increase the maximum number of controllers
to 64 on a controller LAN. Controller LANs connect to host LANs
through Link Taps.
The controllers on a controller LAN pass a software token along the
LAN, allowing each controller to broadcast in turn. If a controller
fails, or the communication wire is broken, the system reconfigures
itself, counting the controllers that can still pass the token. The
controller with the token becomes the master controller on the
LAN and restarts the token passing procedure. The controllers on
the other side of the wiring break do the same, even if there is only
one controller.
Even if the ability to communicate on the controller LAN and
possibly with the host LAN is impaired, normal functions at each
controller continue without interruption. When communication is
re-established with the other portions of the controller LAN, the
system reconfigures itself.
Link Support
Host workstations communicate with controller LANs through
Links. Within I/NET, a link may represent a hardware device (i.e.,
a Tap, NPR, or Xenta 527/527-NPR) or it may represent a distrib-
uted link (i.e., a single link address that is being shared among
multiple NPRs or Xenta 527/527-NPRs). The information within

this section focuses on I/NETs traditional use of link devices. For

information about distributed links, refer to Distributed Link
Architecture (DLA) Support, starting on page 1-10.
You can address up to 16 Link Taps on a single host LAN. Address
additional Link Taps through workstations, NPRs, or Xenta
527/527-NPRs on the Ethernet LAN, or through additional host
LANs. I/NET supports up to 100 system link addresses (099).
Link Taps connect the operator station from the host LAN to a
controller LAN. You perform link definition from the Configure
program. Here you enter the system link name, the hardware link
number (the actual address, 0 to 15, assigned to the Link Tap), and
the system link number (099). The connection to the link is made
using the system link number when addressing the link through
I/NET software. If you selected Direct configuration, the hardware
and system addresses are typically set the same (00).
Note: You must always define all hardware and system links in the
Configure program. This ensures proper system operation.
Even though each host LAN is limited to16 links, the entire system
can support up to 100 links (099). All links on a system must be
mapped. This information can be shared through an Ethernet LAN
with all other workstations. You can connect through a link which
is not on your host LAN. This use of the Ethernet LAN allows
communication to controller LANs without having to connect a
Link Tap for that controller LAN. This is helpful if your worksta-
tions do not need continual connection with certain controller
LANs.
Distributed Link Architecture (DLA) Support

I/NET allows you to define a system-wide total of up to 100 links in
order to connect controller LANs to the I/NET system. In the tradi-
tional I/NET 2000 system, if you use NPRs or Xenta 527/527-NPRs
to connect remote controller LANs (i.e., sites) to I/NET, each site
consumes one unique link address. This limits the traditional
I/NET 2000 system to a maximum of 100 sites.

I/NET Seven adds Distributed Link Architecture (DLA) capabili-

ties to NPRs and Xenta 527/527-NPRs, and to the I/NET IOServer,
in order to allow multiple devices to share the same link number. In
a system that is configured to use DLA-enabled devices, up to 64
sites can share a single link address. The shared link is referred to as
a distributed link. The use of distributed links allows the I/NET
Seven system to support up to 6400 sites.
Note: I/NETs system-wide limits of 6,400 controllers and 100 link

addresses must be observed, regardless of whether or not DLA func-
tions are enabled. For example, if your I/NET system already
contains 6400 controllers, implementing DLA will not allow you to
expand the system with additional sites of controllers.
DLA Guidelines
Before you configure your system to use DLA, ensure that you
understand the following basic guidelines. This will help to prevent
communication failures from occurring within your I/NET system.
Before you upgrade an NPR from I/NET 2000 to I/NET Seven
(i.e., before you download DLA-compatible binary software
to an NPR), ensure that you first install I/NET Seven on all
host workstations in your system, beginning with worksta-
tions that are being used as a Reference Host. If necessary,
refer to TCON298, I/NET Seven Getting Started, for installa-
tion and upgrade instructions.
In order to enable and use DLA in even a single NPR, you
must ensure that all NPRs within your system are loaded with
DLA-compatible binary software.
Even with DLA-compatible firmware loaded in your systems
NPRs, the DLA functionality will not be available until it has
been enabled.
Only Xenta 527/527-NPRs and DLA-enabled NPRs can share
the same distributed Link address. If a non-DLA NPR dupli-
cates the Link address of any other NPR or Xenta
527/527-NPR within your system, a communication error
will occur.

Ensure that you assign a unique Site address to each NPR and
Xenta 527/527-NPR that shares the same distributed Link
address. Duplicate Site addresses are not supported within the
same distributed Link.
Overview of I/NET Link Communications
Using a traditional Host LAN and Link LAN architecture, I/NET
Seven has the ability to support multiple sites directly connected to
the same Link device. However, this feature requires the use of
7802x Link Taps communicating with 7803x LAN Taps. Referring
to the example configuration in Figure 1-2, you will see that Link
Figure 1-2. Traditional Host LAN/Link LAN Architecture
Tap 01 has a permanent, direct connection to Buildings A and B

using 7802x/7803x Link/LAN Taps, and a Telco-provided leased-
line infrastructure. A single 78025 Link Tap can communicate with
up to 63 78035 LAN Taps. Therefore, a single Host LAN with 16

78025 Link Taps will allow a total direct-connected site capability

of 1008 sites. With I/NET Seven and multiple Host LANs
connected over TCP/IP, this limit is raised to a total of 6,300 sites.
A limitation of this implementation is that typically, the cost of
multi-dropped Telco leased-lines is high, and Link/LAN communi-
cation rates are 9600-baud maximum.
With the use of NetPlus Routers, systems can be designed to replace
the Host LAN/Link LAN infrastructure with high-speed Ethernet
LANs. These designs replace the architecture shown in Figure 1-2
with the architecture shown in Figure 1-3.
Figure 1-3. Traditional Architecture
By using the DLA capabilities build into the I/NET Seven NPR,
IOServer, and Xenta 527/527-NPR, you can create system architec-
tures similar to the one shown in Figure 1-4. DLA implementation
takes advantage of the fact that most sites typically have less than
the maximum 64 primary controllers (DCU/PCU/SLI, etc.).

Figure 1-4. DLA Architecture
Although I/NET Sevens IOServer is DLA-compatible, it does not

provide the same duplicate link functions as the NPR and Xenta
527/527-NPR. For example, local site I/NET Host PCs (as shown at
Buildings C and D in Figure 1-5) do not have the ability to support
directly connected controller LANs with the same Link address.
Only Xenta 527/527-NPRs and DLA-enabled NPRs (as shown at
Buildings A and B in Figure 1-5) provide this capability.
To implement this system with a TCP/IP infrastructure, either
these controller LANs will consume an entire Link address, or addi-
tional Xenta 527/527-NPRs and/or DLA-enabled NPRs can be
installed as shown in Figure 1-6.

Figure 1-5. I/NET Host PC's Do Not Provide DLA Functions
Benefits of Xenta 527/527-NPRs and DLA-enabled NPRs

Xenta 527/527-NPRs and DLA-enabled NPRs allow existing instal-
lations to replace Dial or Direct Connected Link/LAN infrastruc-
tures with TCP/IP-based infrastructures, while still maintaining
the ability to connect to more than 100 sites. The benefits of this
replacement include:
Replace many, expensive, low-speed dial-up telephone lines
with a facility's existing high-speed TCP/IP WAN or the
Internet.
Replace many, expensive, low-speed leased telephone lines
and difficult to obtain and maintain synchronous modems
with a high-speed TCP/IP WAN or the Internet.
Maintain all existing I/NET database configurations,
including:
Graphic Pages
Controller SAV files

Figure 1-6. Adding DLA-enabled Devices
DocutrendTM/SevenTrends data
Site installation and commission costs are minimal.
As DLA configured devices can co-exist with non-DLA configured
devices, site expansion can be selective. That is, existing I/NET 2000
installations with non-DLA configured NPRs can be expanded
beyond 100 sites without re-engineering or re-commissioning the
existing installation. All NPRs on the site, however, must be
upgraded with the new DLA compatible binary should only one
NPR be configured as DLA enabled.
As with 7802X/7803X Link/LAN Tap installations, the actual
number of sites that an I/NET Seven system can support with DLA
enabled devices will be dependent on the number of controllers
installed at each site. DLA architecture provides for a maximum of
6,400 controllers distributed over 100 Link addresses.

System Configuration I/NET Configuration
DLA Functions
A DLA-enabled system provides the following major functions:
Allows duplicate Link addresses in multiple NPRs and Xenta
527/527-NPRs connected to the same system.
Detects conflicting Link/Site Number configurations and
notifies the user.
Attaches the correct Link and Site Number to all Alarms,
Messages and Transactions generated by the controller envi-
ronment before routing them to an I/NET Seven Host.
Checks for a valid DLA configuration before enabling the
DLA capability.
Provides non-DLA enabled device operation if a valid DLA
configuration is not present.
Allows Xenta 527/527-NPRs and DLA-enabled NPRs to
coexist gracefully with NPRs that are not DLA enabled,
provided they are all at the same binary software revision
level.
I/NET Configuration
I/NET uses a separate program called I/NET Configuration
(INetCfg.exe), to specify system and communication parameters
for I/O Server and I/NET. Within the I/NET Configuration
program, you may define communication parameters, set periph-
eral parameters, modify the default directory structure, define host
masking and configure NetPlus Routers and Xenta 527/527-NPRs.
Note: Instructions for using the I/NET Configuration program are in

TCON298, I/NET Seven Getting Started.
The Database Server

I/NET host software provides an interface to data that resides in a
database server. The database server may be local or remote,
depending on the configuration of your workstation.

I/NET Configuration System Configuration
When an I/NET PC is configured as a Standalone, Filemaster, or

Equalized client workstation, it will use its own SQL services to
maintain a local I/NET database.
An I/NET PC configured as a Remote client will not maintain a
local I/NET database. Instead, this type of workstation will use the
SQL services and I/NET database located on another I/NET work-
station. Any workstation that maintains a local I/NET database can
be used as the database server for a remote client.
User Authentication
I/NET displays an Authentication editor under the following
circumstances:
When you initially attempt to connect to an I/NET SQL data-
base.
When you attempt to add or modify a configuration profile
while the I/O Server is not running.
When you change the setting of the Workstation Type param-
eter in the Configuration Profile Editor.
When you click the Connection button in the Configuration
Profiles Editor in order to change the way the workstation
connects to the SQL database.
I/NET Seven Authentication
The authentication process will attempt to verify that you are a
valid I/NET user on the database server or filemaster workstation,
and that the Configuration system tray function is enabled for
your password.
If you are configuring a standalone workstation, this authentica-
tion is for the local I/NET SQL database. Otherwise, this authenti-
cation is for the I/NET SQL database on the filemaster or server
workstation to which this workstation will connect.
Database Authentication
During the authentication process, the login you provide must
enable public and db_owner roles for I/NETs database.

If you are configuring a remote client workstation, this authentica-

tion is for the I/NET SQL database on the server. Otherwise, this
authentication is for the local I/NET SQL database on your work-
station.
Filemaster Database Authentication
This form of authentication is only active when you are configuring
an equalized client workstation. It is used to authenticate you as a
valid administrator of the I/NET SQL database located on the file-
master. The login you provide must enable public and
db_owner roles for I/NETs database on the filemaster.
Authentication Types
Default This type of authentication will use an I/NET-
generated default username and password to connect to the
I/NET database on the database server. Use this option when
the I/NET database to which you are connecting was created
using the Default Account option in DbCreate.
Current Windows User This option is intended for use on
large I/NET installations where user permissions will be
administered using Enterprise Manager. This option allows
the Windows account of the currently logged in user to also
be used as the login for the I/NET database. This option will
only work if the Windows user account is that of a Windows
system administrator on the database server, or it has been
assigned the public and db_owner roles for I/NETs data-
base.
Manual Selecting this option causes the Database User
Name and Database User Password fields to become active
in the Authentication editor, allowing you to manually log
into a database server.
Configuration Profiles
The I/NET Configuration program allows you to specify and save
more than one set of configuration specifications. These specifica-
tions are called profiles. The majority of host workstations only
require one profile. However, multiple profiles are useful if you
work with several different I/NET environments, because you can
change system parameters simply by selecting a different profile.

Most of the configuration parameters are saved in the system

registry and IP routing information specific to each profile is stored
in a .DAT file.
Note: There may be differences in the routing data for each configuration
profile; consequently, you should not change configuration profiles in
a stable I/NET network.
Serial Port Configuration

I/NET can only use one serial port, or modem, at a time. The
I/NET Configuration program allows you to either define a serial
port, or select a modem that has been previously installed under
Windows. If you need to configure multiple serial ports or commu-
nication devices, you can use separate configuration profiles.
Link Types
For each serial port you configure, you must specify a link type.
Possible link types are:
Directa host TAP.
NetPlus Routera NetPlus Router or Xenta 527/527-NPR.
This link type is useful when you are configuring a NetPlus
Router or Xenta 527/527-NPR. When communicating with a
directly connected NetPlus Router or Xenta 527/527-NPR,
the baud rate is fixed at 19,200.
Embedded 4.x Diala modem that communicates with a
7806x Dial Tap.
Integrated Diala modem that initiates calls to a host or
controller LAN. This setting supports outgoing calls only. It
does not answer incoming calls.
Integrated NPR Diala modem that initiates calls to a
NetPlus Router or Xenta 527/527-NPR. This setting is other-
wise identical to the Integrated Dial option.
Note: Refer to the Communication chapter for detailed information on

configuring Dial functions.
The Link type specified dictates which other parameters are avail-
able in the Configuration Profile editor.

Link Numbers
After selecting the Link type, you must map a hardware link
number to a system link number. While you may use any number
for the hardware link, care should be taken to avoid duplicating
system link numbers. If you assign a system link number that is
already in use, either on the same, or different, host workstation,
I/NET produces an error message when it tries to use that system
link.
You can also set up a Multi-Link Dial capability. Multi-link Dial
permits a single host workstation, and modem, to support up to
100 links. To do this, assign multiple system link numbers (099)
to a hardware link number of 0.
Note: Refer to the Communication chapter and to TCON298, I/NET

Seven Getting Started, for detailed information on configuring
specific link types, including Multi-link Dial.
TCP/IP Configuration
TCP/IP configuration includes assigning a host address and desig-
nating a reference host.
Host Address
Assign each host a host address number (1 through 250). This
number must be unique. If a duplicate host address is detected,
I/NET produces an error message.
Reference Hosts
A host workstation, NPR, or Xenta 527/527-NPR must have
knowledge of the other devices on the network in order to commu-
nicate with them. This knowledge is stored in what is commonly
called a routing table. A routing table will contain the IP address of
the devices known to the host workstation. When the host has data
to route to another I/NET device, it uses the addressing informa-
tion contained in the routing table to determine the destination
path. I/O Server stores the routing table in a .DAT file.
To facilitate both the initial building and the updating of the
routing table, the I/O Server uses a reference host. The reference
host may be any host workstation, NPR, or Xenta 527/527-NPR on

the Ethernet LAN and is specified by its IP address. Each time the
I/O Server is launched, it uses the information in the routing table
on the reference host and updates the local routing table, accord-
ingly.
It is best to use a common reference host for all the hosts, NPRs,
and Xenta 527/527-NPRs in the I/NET system. However, the only
specific requirement is that the designated reference host be
constantly powered. While a host workstation provides greater
memory and processing power, an NPR or Xenta 527/527-NPR is
more likely to be always available. You may designate more than
one reference host as a precautionary measure. You should also
assign a reference host to the I/NET workstations, NPRs, or Xenta
527/527-NPRs that are acting as reference hosts.
As an example of proper reference host assignments, Figure 1-7
shows each NPR at a remote site defining a host PC on the Ethernet
as a reference host. This reference host also points back to one of

the remote NPRs. This will ensure that proper communication can
be established during the commissioning of this system, or when
the system comes up following a communication interruption.
Explanation:
Figure 1-7. Example of Reference Host Assignments

File Equalization
Note: You must have Windows Administrator rights in order to make any
changes to your I/NET configuration that will affect file equalization.
File equalization is essential in I/NET systems where multiple host

workstations will be used to manage access control or I/NETs
network configuration. It allows host workstations connected to an
Ethernet LAN to share certain database information while still
maintaining their own I/NET database.
File equalization is a function of the SQL server that is installed on
I/NET workstations. The SQL server ensures that each individual
workstation has up-to-date copies of equalized information. The
equalized information includes:
Network configuration (links, sites, stations, etc.)
Host passwords
Controller passwords
Tenant data
User-defined tenant field labels
Individual records
Group door assignments
Elevator floor assignments
Trend plot data
The Filemaster
In an equalized I/NET system, one host workstation is designated
as the filemaster. This designation is performed in the I/NETs
Configuration Profile editor and is maintained in the configuration
profile. When you set the Workstation type to Filemaster, I/NET
automatically completes the Filemaster name field with the
Computer name (found in the Identification tab under Windows
Network settings). The Filemaster name field is read-only on the
filemaster station and cannot be changed.
It is important that the workstation designated as the filemaster be
constantly powered and that its SQL service be running. The SQL
service will dock an icon in the system tray to indicate it is active.

Caution: If the filemaster workstation is powered off, or if SQL services are not
available, file equalization cannot occur. It is recommended that the
filemaster workstation be powered by a uninterruptable power
supply (UPS).
All host workstations configured as equalized clients must connect

to the filemasters SLQ database using the Computer name of the
filemaster workstation. SQL services run on all equalized clients
allowing the I/NET database to be constantly updated, even when
I/NET is shut down.
When you promote a workstation to filemaster, I/NET requires
that you provide proper authentication as an authorized database
administrator. As other workstations are being promoted to equal-
ized client status, they will also be asked to provide proper authen-
tication before they can begin receiving equalized data from this
filemaster. This helps to ensure that no data on the filemaster gets
distributed to unauthorized clients.
Equalized Clients
Equalization clients are I/NET workstations that receive network
configuration and access control data from a filemaster. You can
view a list of all the client workstations that reference your file-
master workstation.
I/NET displays the File Equalization Clients editor when you select
Clients from the I/NET Configuration editor on a filemaster work-
station. On client and standalone workstations, the Clients button
appears grey and is non-functional.
The File Equalization Clients editor lists all equalization clients that
reference this workstation as their filemaster. The following infor-
mation is displayed for each client appearing in the list:
Client This is the computer name assigned to the client
workstation.
Last Status This is the result of the last successful communi-
cation between the filemaster and client.
Time This is the time of the last successful communication
between the filemaster and client.

Elapse (min) This is the number of minutes that have

elapsed since the last time the filemaster and client success-
fully communicated with each other.
Options
The following commands are available from within the File Equal-
ization Clients editor:
Refresh Use this command to update the list of clients.
Drop If necessary, you can highlight a client in the list and
use the Drop command to prohibit the selected client from
receiving further updates from this filemaster. This is not the
same thing as demoting the client to a standalone worksta-
tion. However, if you wish to re-establish equalization
between the filemaster and the client, you will have to demote
the client to a standalone workstation, and then back to a
client workstation.
Snapshot
When you designate a workstation to be a filemaster, the SQL
server immediately creates an image of that workstations current
database. This image is a database snapshot that will be distrib-
uted to other workstations as they are promoted from being a stan-
dalone workstation to an equalized client. Along with the snapshot,
client workstations also receive any information that may have
changed since the filemasters snapshot was created.
At a scheduled time each day, the filemaster will regenerate its snap-
shot. This allows any changes that may have occurred since the last
snapshot was created to be captured in the new snapshot.
Note: A snapshot is not equalized among existing client workstations it is

only sent to a standalone workstation as it is being promoted to a
client. Existing client workstations are equalized and should therefore
already have up-to-date data.

Promoting and Demoting Workstations
Caution: Before upgrading an I/NET Seven filemaster or client to a newer host

software build, ensure that you first demote the workstation back to
standalone status. Otherwise, you risk corrupting database contents
among all equalized workstations.
changes to your I/NET configuration that will effect file equalization.
I/NET hosts by default are standalone workstations. While standa-
lone workstations may allow remote clients to connect to them to
use their database, they do not equalize their I/NET database with
a filemaster. When you set the Workstation type to Filemaster in
the Configure program, you are promoting that workstation to file-
master status. When you configure a workstation to receive equal-
ized data from a filemaster, you are promoting that workstation to
equalized client status.
When you promote a workstation to filemaster, you will be
prompted to provide proper authentication as an authorized data-
base administrator of the local I/NET database.
When you promote a workstation to be an equalized client, I/NET
requires that you provide proper authentication as an authorized
I/NET user of the filemaster, and as a database administrator of the
local I/NET database and of the filemasters database. This helps to
ensure that no data on the filemaster gets distributed to unautho-
rized clients.
Multiple Access
I/NET allows multiple operators to edit equalized data. Thus, it is
possible that two or more operators may be attempting to edit the
same record at the same time.
Each time a record change is saved, it is sent the SQL server on the
filemaster for processing. So, in the case of multiple edits, the last
one processed by the filemaster is the version that will then be
distributed. I/NET will display a message if, because of multiple
access, your edits could not be saved.

Client/Server Infrastructure
changes to your I/NET configuration that will affect the client/server
configuration.
I/NET's client/server configuration allows multiple workstations

connected to an Ethernet LAN to share a single SQL database. On
the Ethernet, any host workstation that is configured as Standa-
lone, Filemaster, or Equalized Client can be used as the SQL data-
base server.
Much like file equalization, the client server infrastructure ensures
that each participating workstation has up-to-date data concerning
the following areas of I/NET:
NETCON (network configuration)
Host passwords
Controller passwords
Tenant data
User-defined tenant field labels
Individual records
Group door assignments
Elevator floor assignments
Trend plot data
Perhaps the biggest difference between the client/server infrastruc-
ture and file equalization is that in a client/server system, a single
I/NET database is being shared among multiple workstations.
Remote clients do not maintain a local database.

The following illustration shows some of the key differences

between file equalization and the client/server infrastructure:
File Equalization Client/Server Infrastructure
Filemaster Server
Equalized Equalized Equalized

Client Client Client Remote Remote Remote
Client Client Client
Key points: Key points:

Each workstation maintains its Only the server maintains an
own SQL database. SQL database.
Each equalized client uses local Fewer system resources are
system resources to maintain required on each remote client
the local SQL database. since there is no local SQL
If the filemaster goes offline, database.
each equalized client can Anytime the server is offline, no
continue to operate. remote clients can run I/NET.
Inherent database redundancy The use of a single shared
lowers risk of data loss after a database raises the risk of data
catastrophic system failure on loss following a catastrophic
the filemaster. system failure on the server.
The Server
Caution: If the server workstation is powered off, disconnected from the

Ethernet, or its SQL services are not available, I/NET on remote
clients cannot operate. It is recommended that the server workstation
be powered by a uninterruptable power supply (UPS).
Any I/NET workstation that is not configured as a remote client can

be used as a database server. This workstation will have access to
I/NETs full functionality limited only by its specific configuration
settings and the operators privileges.

Because remote clients rely heavily on the servers database for their
operability, it is imperative that the server always remain powered
up and online. If the server goes offline, I/NET on remote client
workstations will stop responding until the server comes back
online or until I/NET times out.
Remote Clients
Note: You must have Windows Administrator rights in order to configure a

workstation to be a remote client.
An I/NET workstation configured as a remote client must connect

to another workstation that is being used as its data server. These
clients will rely completely on the servers database. Therefore,
remote client workstations do not require SQL services. A remote
client communicates directly with the SQL services on the worksta-
tion specified as its server.
You can configure a workstation to be a remote client by setting the
Workstation type to Remote client in the Configure program.
When you configure the workstation as a remote client, I/NET
requires that you connect to a server by specifying a server name
and logging into the server with a valid user name and password.
This helps to ensure that no data on the server gets accessed by
unauthorized remote clients.
Remote clients do not have access to I/NETs full functionality.
When using a remote client, the following areas of I/NET are not
accessible:
Network functions
Automatic DPU restore (see the note below)
Archiving
Dial after edit
Note: The link configuration parameters associated with Automatic DPU

Restore are greyed out on remote clients. When setting these parame-
ters on other workstations, do not define a remote client workstation
as a restore host. Remote client workstations do not provide restore
host functions.

System Configuration System Limits
In addition to the remote client limitations listed above, mask

settings in the AMT Configuration editor on remote clients are
ignored. Only the AMT mask settings on the server will control
what messages are received in AMT. You can, however, use unique
filter settings at each remote client to control what AMT messages
are displayed.
Multiple Access
I/NETs client/server infrastructure allows multiple operators to
edit the database. Thus, it is possible that two or more operators
may be attempting to edit the same record at the same time.
Each time a record change is saved, it is stored in the database by
the SQL server on the server workstation. So, in the case of multiple
edits, the last one processed by the SQL server is the version that
will then be stored in the database.
System Limits
I/NET has physical limits concerning the connections of hardware
and LANs. While these limitations will not affect you in most cases,
Table 1-2, System Hardware Limits is provided for your conve-
nience.
Table 1-2. System Hardware Limits
Max. # on Max. # on Max. # on

Equipment System Totals
Ethernet LAN Host LAN Controller LAN
Host Workstation 250 8 64 250
NetPlus Router 99 1 99
Host Taps N/A 8 (1 per host) 64 (1 per host) 1 per host
Controller LAN (Link) Taps N/A 16 64 100
Controllers (without
N/A N/A 32 3200
repeater)
Controllers (with repeater) N/A N/A 64 6400
Limited to number
Unitary Controllers N/A N/A 32 per UCI
of UCI LANs

I/NET System Hardware System Configuration
Table 1-2. System Hardware Limits (Continued)
Max. # on Max. # on Max. # on

Equipment System Totals
Ethernet LAN Host LAN Controller LAN
32 per I/SITE LAN
Door Processing Units / Limited to number
N/A N/A 32 per DPI
Security Control Units of subLANs
64 per MCI
64 per MRI
Limited to number
Micro Regulators / ASCs N/A N/A 64 per MCI
of subLANs
32 per I/SITE LAN
There are also limits on LAN distances (refer to Table 1-3, LAN
Specifications). These limits can be extended by using a repeater
to lengthen a LAN segment.
Table 1-3. LAN Specifications
Station Communication Connection Maximum Distance
RS485 at 19,200 baud or 9,600 baud

Controller LAN (Fixed at 19,200 baud for a NPR 5,000 ft.
controller LAN)
25,000 ft. using maximum of
Controller with LAN Repeater RS485 at 19,200 baud or 9,600 baud four repeaters, each at
5,000 ft.
I/NET System Hardware

I/NET requires several pieces of hardware in order to function:
One or more host workstations that run the I/NET software,
providing the controlling information, collecting and storing
the data, and compiling reports. Controllers that provide the
output and input points to sense, record, and control the
devices attached to them.
Depending upon your network configuration, you may also
include NetPlus Routers.
Taps linking controller and host LANs.

System Configuration I/NET System Hardware
A hand-held console (HHC) providing immediate, local

access to controllers for initial programming of addresses,
baud rates, and to field check data and parameters. (This
equipment is not required with 7728 and 7798 DCUs.)
Series 2000 NetPlus Router

The NetPlus Router (NPR) connects multiple networks of I/NET
controllers to any 10 MBPS Ethernet LAN or WAN using TCP/IP.
NPRs provide an efficient, robust, and low-cost platform for direct
connection to a commercial LAN.
The NPRs primary function is to route data traffic between a
controller LAN and the Ethernet LAN. They provide the capability
for one or more I/NET workstations to supervise and manage
single and multiple facilities remotely. The NPR provides both host
and Link Tap functions for your host workstation.
NPRs are designed to withstand more rigorous conditions than a
PC and can be physically located in facility maintenance areas.
Some specific features are listed below.
Microsofts TCP/IP protocol provides easy integration of
I/NET network with commercial Ethernet LAN/WAN.-
Link support allows distribution of commercial LAN down to
the single-controller environment.
LAN/WAN point globalization distribution to selected nodes,
with operator-defined limits on distribution to minimize
network traffic.
Message, alarm, and globalization buffering provides local
storage of data until distribution.
Battery protection of buffered data in case of power outages.
Note: Refer to TCON184, Series 2000 NetPlus Router Installation Guide

for additional information on NPRs.

Xenta 527/527-NPR
Like the NPR, the Xenta 527 and Xenta 527-NPR connect multiple
networks of I/NET controllers to any Ethernet LAN or WAN using
TCP/IP. Xenta 527/527-NPRs can communicate over 10 MBPS or
100 MBPS networks.
Xenta 527
TACs Xenta 527 combines the capabilities of the following two
devices:
Xenta 511 The Xenta 511 is a web-based presentation
system for LonWorks networks. Using a standard web
browser, the operator can easily view and control the devices
in the LonWorks network via the Internet or a local intranet.
I/NET NetPlus Router The I/NET NetPlus Router allows
you to connect multiple networks of I/NET controllers over
an Ethernet local area network (LAN) or wide area network
(WAN) using TCP/IP transport protocols.
Using the Xenta 527, you can create a hardware bridge that inte-
grates I/NET devices into your LonWorks network. In addition to
being a web-based presentation system for LonWorks networks,
you can also use the Xenta 527 to provide web access into an I/NET
system.
TACs XBuilder is the programming tool you can use to design,
generate, and maintain web pages in the Xenta 527.
Xenta 527-NPR
The Xenta 527-NPR provides the same NetPlus Router capabilities
as the standard Xenta 527, but does not have the capability of being
a web-based presentation system for LonWorks or I/NET
networks. You cannot download XBuilder projects to the Xenta
527-NPR. You can, however, configure this device through a web
browser.
Note: Refer to Engineering TAC Xenta Server - Xenta 527/527-NPR

Supplement (0-004-7682) on TACs web site for more information on
Xenta 527/527-NPRs.

Distributed Control Units

The 7700 family of controllers provides the muscle of the I/NET
System. Through them you can monitor and control your energy
use and facility environment and access. By connecting various
sensors, actuators, transducers, signal converters, relay boards,
door readers and door strikes to the controllers, you can measure
interior/exterior temperatures and control HVAC equipment and
lighting, or control access to doors in the facility. Since several
controllers normally operate on a single controller LAN, they can
share information from sensors on other controllers, as well as data
on devices connected to their internal input/output points. This
lets you control the environment in a building by programming the
controllers, meeting energy conservation requirements while
providing maximum comfort.
7700 (Distributed Control Unit)
The majority of controllers used in many I/NET configurations are
7700s. This controller provides automatic control and information
about building operation and is located on the controller LAN.
This controller provides 16 discrete/pulse width modulation
(PWM) outputs, 16 analog inputs, and eight discrete/pulse inputs.
Optional hardware modules can add an additional twelve analog
input points, eight discrete/pulse input points, four additional
analog output points and eight discrete/PWM output points.
Because it can monitor and control so many points, this controller
is I/NETs workhorse.
See Also: TCON095, Model 7700 Distributed Control Unit

7716 (Process Control Unit)
The 7716 provides the same functional capabilities of the larger
7700/7740 controllers on a smaller, less expensive board. The
smaller package size and reduced I/O point count make it ideal for
small applications. The base board of the 7716 provides eight
outputs and eight universal inputs. The inputs may be defined as
analog, discrete or pulse inputs, and may be supervised. Expansion
cards provide the 7716 with additional flexibility by adding input
and output points in different combinations and I/O types.

When used with an RS232 serial port expansion option, the 7716
can provide synchronous or asynchronous communication,
depending upon the type of device connected to it. The 7716 has
the ability to connect directly to a host workstation without using
a 7801 Tap. This controller is found on the controller LAN.
See Also: TCON096, Model 7716 Process Control Unit Installation Guide
7718 (Process Control Unit)
The 7718 controller is primarily designed for European distribu-
tion, but is sold in all markets. It is functionally similar to the 7716
controller, described above.
See Also: TCON106, Model 7718 Process Control Unit

7728 (I/SITE I/O)
The 7728 I/SITE I/O is a satellite controller with a built-in display
screen, providing 14 universal inputs, four analog outputs, and 10
triac outputs. It is designed to support local operation without a
local workstation or HHC. It is functionally similar to the 7716 and
7718 controllers.
See Also: TCON114, 7728 I/Site I/O

7740 (Distributed Control Unit)
The 7740 is less expensive than the 7700. It provides the same basic
I/O point capabilities, but does not use the optional hardware
modules for I/O point expansion. It is used in situations where the
basic hardware meets the requirements for the number of I/O
points and price consideration. This controller is found on the
controller LAN.
See Also: TCON097, Model 7740 Distributed Control Unit

7750 (Building Manager)
The Building Manager provides an easy way for building occupants
to override normal day-to-day schedules for lighting, heating and
air conditioning of their area during after-hours work. The 7750
keeps track of these override requests by zone to generate energy
use bills.

By calling up the 7750 and answering questions using the telephone

keypad, the basic programming of the controller can be tempo-
rarily changed. Access codes prevent unauthorized access and are
assigned to each building zone. After a set amount of time, the
override ends. This controller is located on the controller LAN.
See Also: TCON098, Model 7750 Distributed Control Unit CSI Building
Manager
7760 (Unitary Controller Interface) with Unitary Controllers
The Unitary Controller Interface (UCI) provides a communication
gateway between the controller LAN and the unitary controllers
(UCs) 7210/7211, 7251, 7260 and 7270. The UCI passes infor-
mation between the controller LAN and the UC subLAN. Up to 32
UCs operate on one UC subLAN under one UCI that can then be
connected to a controller LAN. The UCI appears as a controller on
the controller LAN and provides control functions that augment
the UCs and internal software I/O points.
The UCs provide a smaller number of I/O points than do the 7700
or 7740. They are specifically designed to monitor and control
cooling/heating VAV terminal boxes, air handling units, and heat
pumps. Each UC usually has eight outputs and eight inputs.
Different UC models can receive different types of input signals.
See Also: Chapter 11, Unitary Control

TCON069, Model 7200 Unitary Controllers
TCON099, Model 7760 Unitary Controller Interface
7770 ICI (MODBUS)
The 7770 Industrial Controller Interface is a specialized controller
that provides a gateway from I/NET to a MODBUS system. The
7770 is similar to the 7760 UCI, although the 7770 processes I/O
data through an interface to and from the MODBUS, whereas the
7760 UCI manipulates real world data/controls through its
network of Unitary Controllers.

The 7770 can support up to 256 points in each direction of the

gateway, appearing as a DCU on the I/NET controller LAN, and a
slave on the polled MODBUS system.
See Also: Chapter 14, 7771 Industrial Controller Interface

TCON102, Model 7771 MODBUS Interface
7780 (Distributed Lighting Control Unit)
The 7780 connects directly to the controller LAN and works in
conjunction with other controllers and workstations on the LAN.
The 7780 is a specialized controller that controls up to 64 lighting
control relays in its maximum configuration. The 7780 is similar to
the 7716 controller but is designed specifically for lighting control.
Like the 7716, the 7780 offers the functional capabilities of a larger
controller at a lower cost through new, highly integrated tech-
nology, a smaller package size, and a reduced number of available
input/outputs.
The 7780 lets you populate databases, map circuits to zones to
override switches (circuits can be in more than one zone), and
create schedules by zone including wink parameters and zone over-
ride times. Features include downloadable firmware, up to 32
zones per controller, sequenced relays that minimize power
requirements, and on-board trending of all I/O points.
See Also: Chapter 7, Point Extensions

TCON100, Model 7780 Lighting Controller
7791 (Door Processor Interface) with Door Processor Units
The 7791 DPI is a SubLAN Interface (SLI), providing a communi-
cation gateway between the controller LAN and the Door Processor
Unit (DPU7900, DPU7910A, DPU7920, and SCU1284), Discrete
Input Unit (DIU7930 and SCU1200) and Discrete Input/Output
Unit (DIO7940 and SCU1280) controllers. Up to 32
DPU/DIO/DIU/SCU controllers operate on a subLAN connected
to a DPI. The 7791 DPI appears on the controller LAN as a DCU.
The DPI maintains a portion of the database and control parame-
ters for up to 32 DPU/SCU controllers connected to its Channel A
LAN port.

The 7930 DIU provides 8 inputs and no outputs on each of its two
stations (16 total inputs), and the 7940 DIO provides a total of 8
inputs and 8 outputs.
The SCU1200 and SCU1280 controllers provide 8 inputs on their
first station and 4 inputs on their second station. The SCU1280 also
provides 8 outputs.
The DPI and DPU, DIO, DIU, and SCU comprise the Access
Control element of the I/NET integrated system. Through the DPI
and DPU/DIO/DIU/SCU, you may monitor, control, or restrict
access to various areas of your facility. Using Access Initiated
Control you may tie access control events from the Access Control
side of the system to the Facility Management side of I/NET.
See Also: Chapter 9, Access Control

TCON109, 7790 Sub-Controller Interface
TCON115, Door Processor Unit 7900
TCON116, Door Processor Unit 7910A
TCON124, DIU 7930
TCON125, DIO 7940
TCON306, Door Processor Unit 48K
TCON312, 1200-series Security Control Unit
7792 (Micro Regulator Interface) with Micro Regulators and
Application Specific Controllers
The 7792 is a SubLAN Interface (SLI), providing a communication
gateway between the Controller LAN and the Micro Regulator
controllers (MR123-210MB, MR123-430MB, MR123-032MB,
MR123-400MB, MR88, MR632, MR160, and MR88R) and Appli-
cation Specific Controllers (MR-AHU and MR-VAV ASCs). The
MRs and ASCs operate on a subLAN on one of two channels
connected to an MRI. Each channel may contain up to 32 MRs and
ASCs. The MRI appears on the controller LAN as a DCU, and uses
two consecutive addresses, one for each channel. The MRI main-
tains the complete database (refer to Chapter 12, Micro Regulator
Control, and Chapter 13, Application Specific Controllers) and

control parameters for up to 64 MRs and ASCs connected to its two

MR LAN ports. The MRI supports the definition of internal points
with all of the extension capabilities typical of the 7716 PCU. The
internal points in the MRI are defined only for point addresses not
currently used by it associated MRs or ASCs.
The Micro Regulator controllers provide stand-alone DDC. The
number of output points and their type vary by model. Both
discrete and PWM modulated control are supported by the MRs.
Depending upon the model, high or low voltage triac outputs, or
Form-C relay outputs are available.
The Application Specific Controllers also provide stand-alone
DDC, but the DDC modules have been preprogrammed. The
number of output points and their type vary by model. Both
discrete and PWM modulated control are supported by the ASCs.
See Also: Chapter 12, Micro Regulator Control

Chapter 13, Application Specific Controllers
TCON109, 7790 LAN Interface Unit
TCON113, Micro Regulator Controllers
7793 (Micro Control Interface) with Door Processor Units,
Micro Regulators, and Application Specific Controllers
The 7793 is a SubLAN Interface (SLI), providing a communication
gateway for all DPU types (DPU7910A, DPU7920, and SCU1284),
micro controllers (DIU7930, DIO7940, SCU1200, and SCU1280),
MRs, and ASCs. The 7793 functions identically to the 7791 and
7792 with the addition of the Demand editor. The 7793 MCI is a
two-station controller that supports up to 32 MRs/ASCs/DPUs/
SCUs on each port, for a total of 64 MRs/ASCs/DPUs.
7797 (Industrial Controller Interface)
The 7797 provides a communication gateway into the I/NET
system for third-party controllers. You can configure the 7797 to
interface with one of several different third-party controllers. The
point count available to the 7797 depends upon the third-party
controller it connects to. Configuration of the 7797 is accom-
plished by configuring the ICI in the configuration/status editor,
and then performing a software restore of the appropriate .BIN file.

See Also: Chapter 14, 7771 Industrial Controller Interface

TCON122, 7797 Industrial Controller Interface
7798 (I/SITE LAN)
The 7798 is a SubLAN Interface (SLI), providing stand-alone
controls for Micro Regulator Controllers (MRs), Application
Specific Controllers (ASCs), Door Processor Units (DPUs), and
Security Control Units (SCUs). This allows the operator or
building manager to control the building through a ViewCon (a
built-in operator interface), a local host workstation, a modem to a
remote workstation, or an optional I/NET controller LAN.
When connected to an I/NET host workstation, it also provides a
communication gateway between the I/NET system and the
MRs/ASCs/DPUs/SCUs.
The 7798 can support up to 32 MRs, ASCs, DPUs, SCUs, or any
combination on a subLAN. The I/SITE LAN also supports internal
points with all of the extension capabilities typical of the 7793 MCI.
The internal points are defined only for point addresses not
currently used by subcontrollers.
7800 Tap Support

Taps provide communication links between various components
of the I/NET system, from an operator station to a host LAN or
from a host LAN to one or more controller LANs, for example.
I/NET architecture allows for economical configurations on very
small systems and can be expanded to much larger configurations.
The 7800 family of Taps let operator stations connect directly to a
single controller LAN, directly to a host LAN, or to a multi-drop or
polling Tap for communication between a single operator station
and multiple remote controller LANs.
I/NET uses a proprietary, token-passing protocol operating in a
tiered LAN architecture. The operator stations require a gateway
or access into the LAN to communicate with the controllers. While
the Taps are required to provide a variety of functions in the I/NET
architecture, one of the most important is to handle communica-
tion between the RS232 output of the operator stations and the
RS485 format of the LAN.

System Addresses System Configuration
See Also: Chapter 2, Communication

TCON101, Model 7800 Series Tap Products
Hand-held Console (HHC)

The HHC is used during installation of controllers and AD/AA
Taps to set station addresses and other parameters. It is used to field
check controller input/output wiring and to verify that program-
ming information entered in the controller by I/NET is actually
present. It is also used as a troubleshooting tool and for day-to-day
system maintenance.
See Also: TCON073, Model HC7410 Hand-held Console
I/STAT
The I/STAT is an intelligent thermostat that connects to the micro
regulators, application specific controllers, and 7728 I/SITE I/O. It
may be used to control and monitor points in the controller to
which it is connected.
See Also: Chapter 12, Micro Regulator Control

TCON113, Micro Regulator Controllers
TCON126, I/STAT and Micro Regulator Controllers
System Addresses
Each individual input and output point, controller, Tap, host work-
station, NPR, and Xenta 527/527-NPR has a unique number that
identifies it in the system. These identification numbers are called
system addresses. Each point address is determined by the address
of the equipment passed through to reach it.
Building an Address
An address in the I/NET system consists of a series of alphanumeric
characters, each describing the route from the top of the LAN hier-
archy to the final device or input/output point. This addressing

System Configuration System Addresses
structure consists of four pairs of numbers and the point type. The
format for the address is:
LLSSPPBB PT
where:
LL = the 2-digit link number

SS = the 2-digit station number
PP = the 2-digit point number
BB = the 2-digit bit offset number
PT = the 2-letter point type
The link (LL) number (0099) is the software link address

that the operator connects through to connect to a specific
controller LAN.
The station (SS) number (0063) is the address of the
controller on that controller LAN.
Every controller provides 32 point address (PP) numbers
(0031), each with ten bit offset (BB) numbers (0009).
For example, to connect to a discrete input (DI) point on a 7740
with the system address 07222804 DI you would connect to link 07
which connects you to the controller LAN. On the controller LAN
you select controller #22, which contains DI point 28 with bit offset
04.
UC, DPU, SCU, and MR Addresses

Connecting to a UC, DPU, SCU, or MR is similar. The link (LL)
and station (SS) portion of the address is exactly the same. The
station is the UCI, DPI, MRI, or MCI on the controller LAN.
However, the point (PP) and bit offset (BB) sections are slightly
different, because of the subLAN structure.
The UCI provides addresses (PP) for 32 UCs (0031), each of
these having eight input and output points using bit offset
(BB) addresses 0007.
The DPI provides addresses (PP) for 32 DPUs/SCUs/DIOs/
DIUs (0031), each of these having ten input and ten output
points using bit offset (BB) addresses 0009.

User-defined Tools System Configuration
The MRI provides addresses (PP) for 32 MRs/ASCs (0031)

on two LANs, each of these having ten input and ten output
points using bit offset (BB) addresses 0009.
The MCI provides addresses (PP) for 32 MRs/ASCs/DPUs/
SCUs (0031) on two LANs, each of these having ten input
and ten output points using bit offset (BB) addresses 0009.
For example, to connect to a UC, DPU, SCU, or MR discrete alarm
(DA) point with the system address of 07230607 DA, select link 07
for the controller LAN and select the UCI/DPI/MRI at station
number 23 on that controller LAN. Then connect to
UC/DPU/SCU/MR/ASC at point address (PP) 06 and the DA point
at bit offset (BB) 07.
See Also: Chapter 6, Input and Output Points

Appendix C, Controller Point Addressing
The specific user and installation guides for the controllers in your
system.
User-defined Tools
There are two types of user-defined tools that you can create within
I/NET. The first type, a shortcut, will launch the file that you
specify. The second, an event, allows you to start a list of event
sequences in controllers on the network.
The Shortcut Tool

The shortcut tool attempts to start any file stored on the local
machine or on any networked drive. This tool uses Windows to
either run the file in the case of an executable file (for example .EXE
or .BAT files), or start the application that corresponds to the data
file (for example Word for a .DOC file or Excel for a .XLS file). The
relationships between file extensions and applications are config-
ured by Windows when applications such as Word or Excel are
installed. This means that a data file will not run if it has no known
association with an application.

System Configuration User-defined Tools
The Event Tool

The event tool starts its associated event sequence(s). The event
tool can only run event sequences that have already been defined
within controllers. When you run an event tool, it communicates
with each controller in its list and starts the appropriate sequences.
If an associated controller is offline, the sequences for that
controller do not run and the tool continues to the next controller.
Running User-defined Tools

There are two methods for running user-defined tools. One way to
run a tool is to launch it from a graphic page. Using a tool marker,
you can associate a graphic page item with a tool. When you click
the item in a live graphic page, the associated user-defined tool
runs.
Another way to run a tool is by launching it from a user-defined
button. You can create up to 16 buttons that are accessible from
I/NETs main menu. Each button can be associated with any user-
defined tool. Click a button to run its associated tool.
See Also: Chapter 1, I/NET Basics, in the I/NET Seven Operator Guide.

User-defined Tools System Configuration

CHAPTER
2
34
Communication
The backbone of I/NET is communication of data between the

various system components. Communication is provided through
the 7800 family of Taps, and NetPlus Routers. I/NET architecture
allows for economical configurations on very small systems and
can be expanded to much larger configurations.
Taps, NPRs, and Xenta 527/527-NPRs provide communication
links between the components and layers of your I/NET system.
For example, Taps link an operator station to a host LAN and a host
LAN to one or more controller LANs. NPRs and Xenta
527/527-NPRs link controller LANs to host workstations over an
Ethernet connection.
I/NET uses a proprietary, token-passing protocol, operating in a
tiered LAN architecture. Taps, NPRs, and Xenta 527/527-NPRs are
the gateway required by host workstations to gain access into the
LAN and communicate with the DCUs. While these devices
provide a variety of functions in the I/NET architecture, one of the
most important is to handle communication between the RS232
output of the operator stations and the RS485 format of the LAN.
See Also: TCON101, Model 7800 Series Tap and Repeater Installation Guide
TCON184, Series 2000 NetPlus Router Installation Guide
Engineering TAC Xenta Server - Xenta 527/527-NPR Supplement
(0-004-7682)
7800 Tap Overview

The 7800 family Taps allow an operator station to connect directly
to a single controller LAN, directly to a host LAN, or to a multi-
drop or polling Tap for communication between a single operator
station and multiple remote controller LANs.

7800 Tap Overview Communication
Each Tap provides specific functions and capabilities. Some Taps

are used when communication lines are hard-wired between loca-
tions. Others are needed when communication takes place over
telephone lines.
The configuration of an I/NET host LAN creates an environment
that allows one or more operator stations to operate in a direct-
connect mode, an auto-dial/auto-answer (AD/AA) mode, or both,
while communicating with over 1,000 different networks. Each
host LAN can support up to eight operator stations connected to
7801 Taps, and up to 16 link Taps (78050, 7802x and 7805x), in any
combination.
Taps connected to a controller LAN provide communication to a
single operator station or one or more host LANs through hard-
wired, polling communication modules (COMMODs), or AD/AA
modems.
The configuration requirements of a specific system determine the
quantity and type of Taps required. There are four types of Model
7800 Taps, each performing a different task (see Figure2-1, I/NET
Communication Example):
Workstation to host LAN or controller LAN communication
(Host Tap). Connects an operator station directly to a
controller LAN or host LAN. You may also set up remote
communication with a LAN. For remote communication, a
companion Tap is typically connected to the LAN at the
receiving end.
Host LAN to controller LAN communication (Link Tap). Use
link Taps to connect a host LAN to one or more controller
LANs.
Controller LAN to host LAN communication (Site Tap). This
family of Taps connects to a link Tap (a Tap connected to a
host LAN).
Special purpose Taps. These Taps fill specialized functions in
the I/NET communication network. There are two types of
special purpose Taps; LAN repeater and printer Taps. The
LAN repeater lets you extend the number of DCUs on a
segment of the controller LAN from 32 to 64, extend your
system beyond the 5000-foot (1500 m) limit for a LAN, or use

Communication 7800 Tap Overview
a T connection in excess of the 300-foot (90 m) limit. The

printer Tap connects a stand-alone serial printer to a
controller LAN.
Figure 2-1. I/NET Communication Example
Host Taps
Host Taps are used in the following configurations:
Host workstation to host LAN. This configuration requires a
workstation to be connected to a host LAN. This can be a
direct-connect or an Integrated Dial Tap (refer to Direct-
Connect Function on page 2-7 or to Integrated Dial Func-
tion on page 2-9).

7800 Tap Overview Communication
Host workstation to controller LAN. This configuration

requires a workstation to be connected to a controller LAN.
This can be a direct-connect or an Integrated Dial Tap (refer
to Direct-Connect Function on page 2-7 or to Integrated
Dial Function on page 2-9).
Host workstation to multiple controller LANs. This configu-
ration requires a workstation to be connected through a host
Tap to one or more controller LAN Taps. This can be a direct-
connect or an AD/AA Tap (refer to Direct-Connect Func-
tion on page 2-7 or to Auto-dial/Auto-answer (AD/AA) Tap
Function on page 2-14).
Note: You may share a telephone connection from a host or link Tap to a
site Tap with a second host. The procedure to connect is the same as if
you were using a Tap connected to your host. Each host must connect
to the 7806X Tap at the shared site in order to establish the shared
connection.
Link Taps
Link Taps are used in the following configurations:
Host LAN to controller LAN. Connects a host LAN directly to
a controller LAN. This is a direct-connect Tap.
Host LAN to multiple controller LANs. Connects a host LAN
to up to 64 controller LANs. This can be a direct-connect or
an AD/AA Tap.
Site Taps
Site Taps (also referred to as LAN Taps) are used in the following
configurations:
Controller LAN(s) to Host Tap. Communicates between each
controller LAN and a host Tap. This can be a direct-connect
or an AD/AA Tap.
Controller LAN(s) to Link Tap. Communicates between each
controller LAN and a link Tap. This can be a direct-connect or
an AD/AA Tap.

Communication Tap Configuration Editors
Printer Taps
Printer Taps connect to a controller LAN or a host LAN and allow
messages from the controllers to print without using a host.
Tap Configuration Editors

Tap configuration editors allow you to set parameters for each Tap
during initial system configuration, and later, when you add a new
Tap or change the configuration of an existing Tap. The following
Tap configuration editors are available:
Host Tap Configuration editor
Link Tap Configuration editor
Site Tap Configuration editor
Printer Tap Configuration editor
Before configuring your Taps, make sure each Tap address is set
properly with the switches found on the Tap. Refer to TCON101,
Model 7800 Series Tap Products, for information on Tap switch
settings.
Tap Configuration Parameters

When you update parameters in a Tap configuration editor, the
changes will take effect when you disconnect from the Tap. If the
changes are made to a shared dial Tap, the changes will take effect
when the last connected host disconnects from the Tap. Table 2-1
lists and describes Tap configuration editor parameters.
Table 2-1. Tap Configuration Parameters
Tap Type
Parameter Description
Host Link Site
Name The name assigned to the Tap, up to 16 characters.
Firmware The current revision number and date the revision occurred
Status
(display only).

Tap Configuration Parameters Communication
Table 2-1. Tap Configuration Parameters (Continued)
Tap Type
Host Link Site
The communication baud rate for a Link Tap to its family of

Speed LAN Taps. This parameter can be any speed from 1200 to
9600 baud, depending on the Tap.
Select modem baud rate for data connection or Beep for
Type pager dial.
This parameter applies only to Dial Taps (7804x, 7805x, and
7806x).
On: Calls to and from the Tap are heard through an 8-ohm
speaker connected to the Tap speaker port or the speaker in
the external modem. The speaker remains on throughout the
Speaker call, whenever the user is connected to the Tap.
Off: The speaker is off.
Auto: Only the dialing portion of the connection is heard. The
speaker remains on through the dialing or call receiving
process but turns off when a connection is made or broken.
This applies only to Taps which reside on a controller LAN
LAN Address (78020, 7803x, 78010, and 7806x). This identifies the Tap
address (0063) on the controller LAN.
This applies to Taps which reside on a controller LAN (78010,
LAN Speed 78020, 7803x, and 7806x). This identifies the LAN speed
(9600 or 19,200 baud) for RS485 ports.
These parameters specify the distribution group number,
message priority and the message mask. The distribution
group number can be a value from one to four. The priority
Control
Parameters can be None, Routine, Priority, or Critical. The distribution
group and mask should match at least one active mask
position on each the host workstation to which you want the
Tap to send messages.
Note: When using dual emulated Tap functions (Host Tap and Site Tap) in a 7716, 7718, 7728, 7756,
7791, 7792, 7793, or 7798, the values entered under Control Parameters in one Tap editor
are used by all Tap editors within the same DCU. Only one set of Control Parameters have
been provided in each DCU.
This parameter is for AD/AA Site Taps (7806x) only. It
specifies the number of Priority messages that will be stored
in the Taps RAM, as a percent of the total available memory,
Percent Full before the Tap calls the host. This is a deferred dialing
parameter for Priority alarms (refer to Priorities in Chapter 3,
System Messages).

Communication Direct-Connect Function
Table 2-1. Tap Configuration Parameters (Continued)
Tap Type
Host Link Site
Note: An outgoing Critical message or alarm will upload all pending Priority messages and alarms.
The only messages stored by the AD/AA Taps for future dialing are Priority messages and
alarms.
This parameter is for AD/AA Site Taps (7806x) only. It
specifies the time interval from the occurrence of an alarm or
Dial Later message that must transpire before the site Tap calls the host
workstation. This is a deferred dialing parameter for Priority
alarms (refer to Priorities in Chapter 3, System Messages).
Note: The message priorities behave as follows when used with an AD/AA Site Tap:
Routine: Ignore the message or alarm.
Priority: Report the message or alarm after the Percent Full limit is reached or the Time
Interval occurs.
Critical: Report the message or alarm immediately.
Direct-Connect Function
The direct-connect function provides continuous two-way
communication within your I/NET system. This function requires
dedicated communication circuits that are continuously active
(e.g., RS485 twisted pair cabling, dedicated phone lines, leased
lines, etc.). The direct-connect function supports the following
types of connections:
host workstation connection to a host LAN
host workstation connection to a controller LAN
host LAN connection to a controller LAN
The Model 7801x, 7802x, and 7803x Taps support the direct-
connect function. Several of the 7802x and 7803x Taps are polling
devices that have the CSI line driver or modem communication
module (COMMOD).

Direct-Connect Function Communication
Host Workstation Setup for Direct-Connect

Use a 7801x Host Tap to connect a host workstation directly to a
host LAN or controller LAN. At the controller LAN, the 7801 Tap
may be emulated by a controller. In this case, you may connect the
workstation to the device that is emulating the 7801 Tap.
You must use Configure to enable the direct-connect function
within the host workstation. Instructions on how to use Configure
are available in the I/NET Configuration chapter within TCON298,
I/NET Seven Getting Started.
Within Configure, perform the following tasks:
Set the link type to Direct.
Choose the COM port to which the 7801x Host Tap (or
device that is emulating a 7801 Tap) is connected.
Set the baud rate to the highest speed supported by both your
COM port and the device connected to that port.
Define each link that will be available through this COM port.
The procedures for defining links will depend on whether you
are connecting the workstation to a host LAN or to a
controller LAN. Each of these types of connections are
described in the following paragraphs.
Exit Configure and I/NET (if running). Depending on your
system setup, I/O Server may shut down automatically at this
point. If not, manually exit I/O Server.
Restart I/NET to begin using the Direct configuration.
Direct Connection to a Host LAN
This configuration allows the host workstation to connect directly
to the host LAN through a 78010 Host Tap. In this case, you must
define each link that is available from the host LAN (i.e., each 7802x
or 7805x Tap connected to the host LAN).
Define the links for this configuration as follows:
Set the hardware address to a value from 0 to 15. This address
should match the value assigned to a link device (i.e., 7802x or
7805x Tap) connected to the host LAN.

Communication Integrated Dial Function
Set the system address to a value from 0 to 99. The system

address must be unique for each device within your system.
Define a name for the link. This name will appear in the list of
available links when you select Connect in I/NET.
If the link device is a 7805x Tap, activate the Dial Link param-
eter. You may also define additional links for the same 7805x
Tap. Refer to Multi-link Dial Function on page 2-23 for
more information.
Repeat these tasks as necessary to define up to 16 hardware links.
Direct Connection to a Controller LAN
This configuration allows the host workstation to connect directly
to a controller LAN through a 7801x Host Tap, or through a device
(i.e., controller, NPR, or Xenta 527/527-NPR) that is emulating the
78010 Tap. In this case, you must define a single link for the work-
station COM port.
Define the link for this configuration as follows:
Set the hardware address to 0.
address must be unique for each device within your system.
Define a name for the link. This name will appear in the list of
available links when you select Connect in I/NET.
Ensure that the Dial Link parameter is deactivated.
If the device at this COM port is a 78012, 78013, or 78015 Tap, you
can use the Network Configuration editor to define up to 64 sites
available through this link.
Integrated Dial Function
Note: The Integrated Dial description in this section is also applicable to the
Integrated NPR Dial function. Therefore, the term Integrated Dial
will be used throughout this section to describe both I/NET functions.

Integrated Dial Function Communication
The Integrated Dial function allows you to remotely connect from

a workstation to a host LAN or controller LAN using asynchronous
modems and standard voice-grade telephone lines. I/NET will
allow a single Integrated Dial connection at any one time; however,
you may store parameters for up to 64 separate connections.
Note: Integrated Dial connections can only be initiated from a host work-
station; the host LAN or controller LAN can not initiate the call. If
your application requires dial-out from a host LAN or controller
LAN, use the AD/AA Tap function (refer to Auto-dial/Auto-answer
(AD/AA) Tap Function on page 2-14).
You must connect an asynchronous modem (internal or external)

to each remote host that will be used to initiate an Integrated Dial
call. You must also connect an external asynchronous modem to a
78010 Tap (or a device emulating a 78010 Tap) at each LAN that
will be dialed.
Host Workstation Setup for Integrated Dial

Before you can use the Integrated Dial function, you must
configure your host workstation as follows:
Add a modem to your Windows environment. If necessary,
refer to your Windows documentation, on-line help, or
modem documentation for installation instructions.
Use Configure to enable the Integrated Dial function. Instruc-
tions on how to use Configure are available in the I/NET
Configuration chapter within TCON298, I/NET Seven Getting
Started
Set the link type to Integrated Dial or Integrated NPR
Dial. This setting will cause a Phone Numbers editor to
become available within I/NET. You will later use the
Phone Numbers editor to define parameters for each
remote device to be dialed.
The baud rate used for Integrated Dial or Integrated NPR
Dial is controlled by Windows and the speed negotiated
by the modems. Therefore, the baud rate field is disabled.

Choose the modem to be used for this link. Only

modems that have been added to your Windows environ-
ment will be listed.
Add a link as follows:
Set the hardware address to a value from 0 to 15.
If the workstation will be used to dial into a host
LAN, this address should match the value assigned
to a link device (i.e., a 7802x or 7805x Tap)
connected to the host LAN. You can add additional
links to this COM port for each link device at the
host LAN.
If the workstation will be used to dial into a
controller LAN, set the hardware address to 0.
Set the system address to a value from 0 to 99. The
system address must be unique for each link within
your system.
Define a name for the link. This name will appear in
the list of available links when you select Connect in
I/NET.
If this link defines a 7805x Tap, activate the Dial Link
parameter. Otherwise, ensure that the Dial Link
parameter is deactivated.
Shut down Configure and I/NET (if running). Depending on
your system setup, I/O Server may shut down automatically at
this point. If not, manually shut down I/O Server.
Restart I/NET to begin using the Integrated Dial configura-
tion.
Use the Phone Numbers editor within I/NET to define
parameters for up to 64 connections. Refer to Phone
Numbers on page 2-13 for more information.
Modem Setup for Integrated Dial

The modem at the call initiating end connects directly (internally
or externally) to your host workstation; no Tap is required at this
location. You can configure I/NET to use an asynchronous modem

Integrated Dial Function Communication
that has already been added to the Windows environment. If neces-

sary, refer to the Windows documentation or on-line help for
instructions on adding a modem to Windows.
Call Initiating (Host) End
I/NET uses the Telephony Application Programming Interface
(TAPI) within Windows to initiate the Integrated Dial phone call.
No special modem configuration strings or switch settings are
required by I/NET to initiate an Integrated Dial call.
For an external modem connection, use a standard modem cable to
connect the modem to the COM port of the host workstation. You
may also use TAC cable model number CBL008 for this connec-
tion.
Call Receiving (78010 Tap) End
The modem at the call receiving end (i.e., connected to the 78010
Tap, DCU, NPR, or Xenta 527/527-NPR at the host LAN or
controller LAN) must be configured to automatically answer
incoming calls. The procedures required to configure the modem
for this operation will depend upon the brand of modem being
used. Some modems provide configuration switches. Others
require you to connect the modem to a computer and issue config-
uration strings from a terminal emulator. Refer to the documenta-
tion included with your modem for instructions on placing the
modem in the auto-answer mode.
Note: If your modem requires you to issue configuration strings, ensure that
the modem is capable of saving settings in non-volatile memory
(NOVRAM). This will allow the modem to retrieve the settings at
power-up.
Modem Setup Example

In the following example, the HyperTerminal application within
Windows is used to issue standard AT command strings to an
external modem connected to COM1 of a PC.
1. Using a standard modem cable, or TAC cable model number
CBL008, connect the modem to COM1 of the PC.

2. Start the HyperTerminal (HYPERTRM.EXE) application

within Windows. If necessary, refer to your Windows docu-
mentation or on-line help for instructions on using this appli-
cation.
Note: Use the following step to ensure that the communication speed
between the 78010 Tap (or device emulating a 78010 Tap) and the
modem is supported by both devices.
3. Set the Port settings in HyperTerminal to the highest speed

supported by both your modem and the device to which the
modem will be connected.
Examples:
9600 Baud (or faster) Modem connected to a 78010 Tap.
Set the port settings in HyperTerminal to 9600 baud.
28.8 Kbaud (or faster) Modem connected to a DCU.
Set the port settings in HyperTerminal to 19200 baud.
Ensure the Tap Baud Rate within the DCU is also set to
19200 baud.
4. Within HyperTerminal, issue the following AT commands
directly to COM1.
AT&F (resets modem to factory default settings)
ATS0=1 (instructs modem to answer after 1 ring)
AT&W0 (stores settings in NOVRAM for retrieval at power-up)
The modem is now configured to automatically answer incoming
calls. Disconnect the modem from the PC and connect it to a 78010
Tap (or a controller that is emulating a 78010 Tap) at the remote
host LAN or controller LAN.
Phone Numbers
I/NET provides a Phone Numbers editor only when the active
configuration has been set to use the Integrated Dial function (refer
to Host Workstation Setup for Integrated Dial on page 2-10). Use
the Phone Numbers editor to define parameters for up to 64
remote devices per link.

Auto-dial/Auto-answer (AD/AA) Tap Function Communication
Address Use this parameter to identify the system address

of a remote device. This may be a value from 0 to 63.
Name Use this parameter to define a name for the remote
site. The name can be up to 16 characters.
Telephone Number Use this parameter to define a tele-
phone number (up to 31 characters). Start the number with a
T for tone dialing. No T indicates pulse dialing. If neces-
sary, use a comma (,) to indicate a two-second pause.
Auto-dial/Auto-answer (AD/AA) Tap Function

The AD/AA function allows I/NET to use voice-grade telephone
lines for communication between a host LAN, or stand-alone host
workstation, and a controller LAN. Like the Integrated Dial func-
tion, AD/AA allows the connection to be initiated from a host
workstation or host LAN. However, AD/AA also enables the
controller LAN to initiate the connection (i.e., dial out) automati-
cally based upon point alarms, messages, and other user-defined
conditions.
Tap models 78040, 78041, 78050, 78051, 78060, and 78061 support
the AD/AA function. These Taps are referred to as Dial Taps. Dial
Taps can be divided into the following groups:
Dial Taps with Internal Modem The 78040, 78050, and
78060 Taps contain an integral synchronous modem.
Dial Taps with External Modem Interface Models 78041,
78051, and 78061 provide an RS232 interface allowing
connection to an external modem.
As described above, the 78041, 78051, and 78061 Taps communi-
cate through an external modem. You may use a synchronous or an
asynchronous external modem, depending on the application
requirements of your system. The following rules apply to each
type of modem:
Synchronous You must use synchronous modems if 78040,
78050, or 78060 Taps (i.e., Taps with integral synchronous
modems) are used anywhere on your I/NET system. If using

Communication Auto-dial/Auto-answer (AD/AA) Tap Function
synchronous modems on an I/NET Seven system, ensure that

the entire system is configured for synchronous AD/AA
communication.
Asynchronous Asynchronous modems may be used only
when the entire system is configured for asynchronous
AD/AA communication (i.e., no 78040, 78050, or 78060 Taps
will be used).
Note: Ensure that your entire I/NET system is configured to use the same
AD/AA protocol either synchronous, or asynchronous. Mixing
protocols will cause communication errors.
Embedded 4x Dial Tap

I/NET Seven allows the host workstation to emulate the 78041 Tap.
This allows you to use an asynchronous modem connected directly
to the host workstation (internal or external) for AD/AA commu-
nication. If you use this function, ensure that your entire I/NET
system is configured for asynchronous AD/AA communication.
Before you can use the 78041 embedded Tap function, you must
configure your host workstation as follows:
Add a modem to your Windows environment. If necessary,
refer to your Windows documentation, on-line help, or
modem documentation for installation instructions.
Use Configure to enable the 78041 embedded Tap function.
Instructions on how to use Configure are available in the
I/NET Configuration chapter within TCON298, I/NET Seven
Getting Started.
Set the link type to Embedded 4x Dial.
Choose the modem to be used for this link. Only
modems that have been added to your Windows environ-
ment will be listed.


The hardware address must be 0 and will be set auto-
matically.
Set the system address to a value from 0 to 99. The
system address must be unique for each link within
your system.
Define a name for the link. This name will appear in
the list of available links when you select Connect in
I/NET.
The Dial Link parameter must be activated and will
be set automatically.
The Embedded 4x Dial Tap function allows you to define
multiple links. This is referred to as Multi-link Dial.
Refer to Multi-link Dial Function on page 2-23 for
more information.
Exit Configure and I/NET (if running). Depending on your
system setup, I/O Server may shut down automatically at this
point. If not, manually exit I/O Server.
Restart I/NET to begin using the Embedded 4x Dial Tap
configuration.
Use the Network Configuration editor within I/NET to define
each of up to 64 sites available through this link. If you are
using the Multi-link Dial function (i.e., you have defined
multiple links for the same Embedded 4x Dial Tap), you
may define up to 64 sites for each link. Refer to Multi-link
Dial Function on page 2-23 for more information.
Modem Setup Examples

In the following examples, a terminal emulator (such as the Hyper-
Terminal application within Windows) is used to issue standard AT
command strings to an external modem connected to a PC.
Synchronous Modem Settings
The examples below describe the setup procedure necessary to
configure common Hayes synchronous modems.

Hayes 2400 Baud SmartModem

Issue the following settings to your Hayes 2400 baud Smartmodem
prior to connecting the modem to the Tap:
1. AT&F
2. ATM1Q0&C1&D2&M1
3. ATS0=1S7=60
4. ATE0V0&W0
5. Cycle power on the modem to store the setup commands of
the users profile to the modems NOVRAM.
Hayes Optima Series SmartModem
Issue the following settings to your Hayes Optima modem prior to
connecting the modem to the Tap:
1. AT&F
2. ATM1Q0&C1&D2&Q1
3. ATS0=1S7=60 (Optima 24)
or
ATS0=1S7=60S37=0 (Optima 96, Optima 14.4, or Optima
28.8 V.34 + Fax + Voice)
4. ATE0V0&W0
5. Cycle power on the modem to store the setup commands of
the users profile to the modems NOVRAM.
Asynchronous Modem Settings
Issue the following settings to your asynchronous modem prior to
connecting the modem to the Tap:
1. AT&F
2. ATS0=1
3. AT&W0
The modem is now configured to automatically answer incoming
calls. Disconnect the modem from the PC and connect it to a
78041, 78051, or 78061 Tap (or a device that is emulating an
AD/AA Tap).

7806x Tap Parameters

The following parameters are specific to the 7806x Taps.
Telephone Number
The 7806x Taps can have up to eight phone numbers defined, each
using up to 31 characters (this includes any commas or T charac-
ters in the number). Telephone numbers preceded by a T indicate
touch-tone dialing. Phone numbers without a T are pulse dialed.
A comma causes the system to pause for two seconds between char-
acters.
The phone numbers of the 7806x Taps are stored in both
NOVRAM and RAM memory (up to the storage capacity of the
NOVRAM). The 7806x Taps always call out to their stored phone
numbers from NOVRAM memory.
When NOVRAM is exceeded, the remainder of the phone numbers
of the MIP 7806x Taps are stored in RAM memory only. This allows
a MIP 7806x Tap, to call out from NOVRAM and RAM, up to eight
phone numbers, each with a maximum of 31 digits. A MIP 7806x
Tap with lost or damaged RAM can still call out to as many phone
numbers as were stored in NOVRAM.
Time-out
This parameter defines the number of seconds (30 or 60) the Tap
waits when calling out before hanging up if a connection is not
made.
Type
This parameter defines the type of device the controller LAN calls.
This setting determines at what baud rate to attempt the remote
connection. The 78060 Tap can dial out from 300 to 1200 baud to
a 7804x or 7805x Tap, or to a beeper. The 78061 Tap can dial out
from 1200 to 19.2K baud to a 7804x or 7805x Tap, or to a beeper.
Note: When setting the Type parameter, do not choose a rate higher than
9600 baud. This is currently the highest supported baud rate.

Link
This is the system address (0099) assigned to the link. This must
match the system link address defined in the Configure program if
you want to receive on-line messages when the host initiates the
phone call. Also, the telephone number in the 7806x Tap editor
must match the telephone number of the 7804x or 7805x Tap you
entered in the host Network Configuration editor.
Group
This parameter further defines the dialing characteristics of each
phone number entered. You can have up to eight different groups,
each containing one phone number, or one group containing eight
phone numbers. The total number of phone numbers cannot be
greater than eight. Refer to the following example for ideas.
Example
Have the Tap call the phone numbers in group 1 if a fire alarm
occurs and call the phone numbers in group 2 if an electrical failure
occurs. Or, call one group for alarms in one building, and a
different group for alarms in a different building. By having more
than one phone number in a group, you increase the chances of the
message getting through. The Tap will continue to dial the phone
numbers (in the order in which they appear within I/NET) until it
successfully uploads the corresponding message to one of the
numbers in the group.
Dial Mask
The dial mask works like the printer and message masks you define
in the host configuration editor. When a Tap dials out, the point
mask of the point(s) initiating the action is compared to the dial
mask in the Tap. If any of the active point mask positions matches
an active mask position in this field, the Tap dials out. The messages
are sent and then compared at the workstation to determine if the
workstation accepts the messages. If the masks do not match, the
workstation ignores the call.
Note: Use only distribution group 1 with 78060/1 Taps. These Taps require
distribution group 1 to initiate a dial-out.

Non-Volatile
This read-only parameter provides an indication of the telephone
numbers storage location within the Tap. Phone numbers are
stored in either of the following locations:
Non-Volatile = Y indicates phone numbers are stored in
NOVRAM memory (and in RAM memory for the MIP
78060/1 Taps only).
Non-Volatile = N indicates phone numbers are stored in
RAM memory only.
7806x Tap Pager Operation

Pagers may be called using the 7806x Tap. There are several addi-
tional phone number character strings for use with dial strings.
The following table shows the characters and their definitions.
Table 2-3. Pager Character Definition
Pager
Definition
Character
Waits for five seconds, replaces the need for numerous

@
commas.
Causes an immediate hang up, and should be used at the
;
end of every pager number dialed.
Issues a Hook flash, forcing the phone to go on-hook for 0.5
!
seconds.
W Wait for a dial tone.
It is important that you be familiar with your pager service and

phone system so that you know of any specific characters that may
be required to place a successful call. For example, if you were to
enter a phone number for SWB MobileComm pagers in a 78060/1
Tap, using an ITT System 3100 PBX you would use the following
format:
T9W8172731511#@123456;
The T at the beginning of the character string initiates tone dialing,
the 9 obtains an outside line. The W causes the Tap to wait for the
modem to receive a dial tone before dialing the pager service phone

number. At the end of the phone number is a # sign which causes

the PBX to perform speed dialing, eliminating any unwanted
delays.
The @ character causes the 7806x to wait five seconds and then
sends the code that will display on the recipients pager. The Tap
then uses the ; character to signal the modem to immediately go
on-hook, ending the call.
If your telephone system has no speed dial function, but has a
period of silence exceeding five seconds before the connection is
made, add additional @ characters or commas to prevent the Tap
from prematurely sending the pager code.
7806x Tap Beeper Operation

Beeper calls are used for notification of specific condition occur-
ring in the I/NET system. This condition is user-definable, and uses
message masking and priorities. The beeper is only a notification
tool; it does not have the ability to display an originating code or
phone number. It issues either a tone, or it vibrates the beeper. To
specify a beeper call, select Beep in the Type field of the 7806x
Configuration editor. If a Beeper service is used, enter the Beeper
service phone number. If human response is expected, enter an @
symbol at the end of the beeper number. This allows the 7806x Tap
to retry during busy or no answer conditions.
The @ symbol causes the modem to listen for a five-second period
of silence once the first ring is detected. The length of time that the
modem will listen for this silent period is established by the
Timeout field in the editor. If a period of silence is detected, the call
is considered to be complete.
Since this Beeper function is used to dial out to numbers that must
have a human response, it is necessary to accommodate differences
in the manner in which beeper systems and humans respond.When
using an external modem (78061 Tap emulation), you should
initialize your Hayes-compatible modem with the X4 command
(factory default). This enables your modem to return the busy
response code if it is expected that a person will answer (or not
answer) the telephone. This will provide a rapid response to a busy
error.

Multiple Site Dial Function Communication
Some experimentation with the timeout period that is set in the

Tap editor may be required. This timeout period should be long
enough to cause the modem to hang-on-the-line until the five-
second period of silence can be detected.
Note: It is imperative that any modem used to interface with a beeper

operate as described above.
7806x Tap Save and Restore

The following parameters are available when you are connected to
a 7806x Tap.
Site Tap Save
The Site Tap Save option saves the Tap parameters in a host SAVE
file. Refer to 7806x Tap Parameters on page 2-18 for descriptions
of these parameters.
Site Tap Restore
Use this function to restore the 7806x Tap parameters if you previ-
ously saved them using the Site Tap Save function.
Multiple Site Dial Function

The multiple site dial feature of I/NET allows you to connect to
more than one site at a time. Each host may connect to up to eight
dial sites at a time from a graphic system page. Each host may also
use additional connections for background tasks (i.e., DCU
synchronization) as well as software restore functions. You must
dial through a 7805x Link Tap on the local host LAN or through a
7804x Host Tap. These dial links must have been previously defined
and saved in the Network Configuration editor.
The number of possible dial links available to a host is restricted by
whether the system is stand-alone or an ethernet LAN configura-
tion, and the system limitations of I/NET. The maximum number
of physical links on a single host LAN is 16, the maximum number
of system links is 99.

Communication Multi-link Dial Function
When a dial link is chosen from a system page, I/NET will attempt
to use the dial Tap associated with the dial link. If that Tap is busy,
the system will roll to the next available system Link Tap (i.e. link
Tap 67 is busy, the system rolls to Link Tap 68). The system
continues until it finds a Dial Tap that is unused, or it reaches the
system limit (e.g. link Tap 99), at which point it rolls to Link Tap 01
and continues the search for an unused Dial Tap.
Multiple site dial connections are made either from the Connect
main menu selection or through graphic dial icons on the graphic
pages.
Multi-link Dial Function

The Multi-link Dial function allows a single 7804x or 7805x Dial
Tap (or Embedded 4x Dial Tap) to be defined as more than one link
within your system. There are two major advantages to this func-
tion:
A single Dial Tap can be used to communicate with more than
64 sites (i.e., you can define up to 64 sites per link).
Separate links can be defined for specific sites. This provides
the following advantages:
The link address associated with an incoming message
will allow you to more easily identify the origin of the
message.
Station addresses assigned to controllers at one site can
also be assigned to controllers at another site. Defining
separate links eliminates the risk of mistaking one
controller for another.
You can implement the Multi-link Dial function within the
Configure editor. While defining the serial port settings for the
active configuration, perform the following tasks:

NPRs and Xenta 527/527-NPRs Communication
Set the hardware address

For a 7804x Tap, set the hardware address to 0.
For an Embedded 4x Dial Tap, the hardware address
must be 0 and will be set automatically.
For a 7805x Tap, set the hardware address to a value
from 0 to 15. This address should match the value set
through the DIP switches on the Tap.
address must be unique for each link within your system.
Define a name for the link. This name will appear in the
list of available links when you select Connect in I/NET.
Ensure that the Dial Link parameter is activated.
Repeat these tasks to create additional links. Repeat the same
hardware address for each link. Only the system address and
link name should be unique for each link.
NPRs and Xenta 527/527-NPRs

NPRs and Xenta 527/527-NPRs allow you to connect multiple
networks of I/NET controllers over an Ethernet local area network
(LAN) or wide area network (WAN) using TCP/IP transport
protocols. This provides an efficient, robust, and low-cost platform
for direct connection to the commercial LAN/WAN network envi-
ronment.
This LAN/WAN network connection provides the capability for
one or more I/NET workstations to supervise and manage a single
facility or multiple facilities from across the street or around the
world, while providing high-speed continuous access and presen-
tation of facility information. This allows you to have a central
control location for multiple facilities. You may also use this ability
to set up a backup control facility in case the primary facility expe-
riences a power outage or other communication problem.
Note: NPRs and Xenta 527/527-NPRs permit the simple and efficient
extension of controller LAN communications over small or large
LANs and WANs while preserving the full station capacity and

Communication NPRs and Xenta 527/527-NPRs
wiring flexibility at each controller LAN. Individual controller LANs

are still limited to the 5000-foot (1500 m) maximum cable length
(25,000 feet/7500 meters with repeaters).
NPRs and Xenta 527/527-NPRs provide Host and Link Tap func-
tions for your I/NET system. See 7800 Tap Overview on page 2-1
for a discussion of these Tap functions.
Communication to I/NET
NPRs and Xenta 527/527-NPRs can communicate with I/NET in
several ways:
Direct communication with devices and workstations
connected to the same controller LAN. This includes buff-
ering messages in the same manner as a Tap.
If the NPR or Xenta 527/527-NPR is connected to a commer-
cial LAN system, it can communicate with I/NET host work-
stations that also reside on the commercial LAN.
A modem may be connected to the NPR or Xenta
527/527-NPR, allowing communication through an I/NET
workstation equipped with a modem. This provides access to
the NPR or Xenta 527/527-NPR configuration and buffered
messages, and to I/NET devices on the same controller LAN.
Refer to Integrated Dial Function on page 2-9.
A portable workstation can be plugged directly into the NPR
or Xenta 527/527-NPR, providing access to the devices
configuration and buffered messages, and to I/NET devices
on the same controller LAN.
Note: Receiving messages through the NPR or Xenta 527/527-NPR requires

at least one matching mask position. Refer to Masking in
Chapter 3, System Messages.
Downloadable Firmware
Like many I/NET devices, the NPR has downloadable binary firm-
ware. You can download firmware to this device from the I/NET
host application (refer to Software Restore on page 5-15), or
from the I/O server configuration utility (refer to TCON298,
I/NET Seven Getting Started).

The Xenta 527/527-NPR is also downloadable; however, you

cannot download firmware to this device from I/NET. If the need
should arise to reload this devices firmware, you can download it
from TACs web site. Before installing downloaded firmware,
review its release information to verify compatibility with your
hardware.
Configuration
The I/NET Configure program is used to enter the setup parame-
ters for NPRs and Xenta 527/527-NPRs. Refer to TCON298, I/NET
Seven Getting Started, for more information about Configure.
Perform the initial setup for the NPR or Xenta 527/527-NPR
through a local workstation connected directly to the device. This
initial setup must be performed before connecting the NPR to
either the I/NET controller LAN or the commercial LAN. Once
installation is complete and the device is fully connected to the
I/NET system and commercial network, changes to the setup can
be performed either locally (through a connected portable work-
station) or through the I/NET Seven editors on a host workstation.
The Xenta 527/527-NPRs have the additional capability of being
configured directly from a web browser.
For installations with multiple NPRs and/or Xenta 527/527-NPRs,
the initial setup can be performed on all the devices at a central
location, before sending them out to the field for installation. This
is important because the setup requires information that is gener-
ally available only to the network administrator for the commercial
LAN system.
Note: After entering the configuration parameters (see below), you must
exit Configure and I/O Server. (This will require you to shutdown
I/NET, if running.) The new configuration will not take effect until
I/O Server is shutdown and restarted. (I/O Server starts automati-
cally when I/NET or Configure is started.)

Configuration Parameters
Name
Each NPR or Xenta 527/527-NPR must be given a unique name.
This name is used to identify the unit to other devices in the I/NET
system. The name can be up to 15 characters. Only letters,
numbers, and the hyphen (-) symbol are allowed in machine
names. Spaces, underscores, and other characters may NOT be
used.
This field is required if the unit resides on an Internet domain (refer
to Domain Name Service (DNS) on page 2-29).
Address
The IP (Internet Protocol) address for this unit. Each machine
(host workstation, NPR, and Xenta 527/527-NPR) that communi-
cates across the commercial network (LAN/WAN) must have a
unique IP address. Your system administrator should provide you
with the appropriate IP address(es), or your network should use
DHCP to automatically assign IP addresses. If you are using a
stand-alone configuration with only a single unit, you may skip this
section.
A unique IP address must be assigned to each unit. Failure to do so
can result in communication errors beginning at the time of
connection to the Ethernet.
Note: A host workstation connected directly to the controller LAN does not
need an IP address to communicate across the controller LAN. An IP
address is only necessary if that host workstation needs to communi-
cate across the commercial network.
The IP address is a four-octet value, with the octets separated by

periods (.). An example IP address is 168.192.200.68. The router
is shipped with a default address (this address will vary).
While I/NET Seven fully supports dynamic IP addressing through
the use of DHCP, a static fixed IP address is preferred. A duplicate
IP address will cause a system error message in I/NET, and will
initiate the appropriate LED error code.

Subnet Mask
This field indicates which sections of the IP address (see above) are
used to indicate the network on which the unit resides. This infor-
mation is typically supplied by the network administrator.
For example: an entry in this field of 255.255.255.0 means that the
first three bytes of the IP address are part of the network identifica-
tion. Therefore, if the entry in the IP address field is
168.192.200.68, the network identification is 168.192.200 (the
first three octets). The example given (255.255.255.0) is the default
mask, which will typically be encountered in the field.
Domain Name
This field indicates the name of the internet or intranet domain to
which the unit is connected. An example domain name is tac.com.
If the NPR or Xenta 527/527-NPR is connected to a private
network, this field may be left blank.
Gateway
The IP address for the network IP router or gateway for your
LAN/WAN system (your network router, not the NPR or Xenta
527/527-NPR). This address is provided by your network adminis-
trator.
This field may be left at the default (000.000.000.000) for systems
which do not include a TCP/IP network router.
Reference Hosts
The reference host is any I/NET workstation, NPR, or Xenta
527/527-NPR that you want to know your IP address, and that can
provide IP addresses to you. You may specify up to a total of eight
(8) reference hosts.
You cannot duplicate entries in the Reference Hosts list. If the IP
address or machine name you entered is already listed as a reference
host, the existing entry will be highlighted when you return to the
configuration screen. The entry place that you selected will not
retain the duplicate entry.

Dynamic Host Configuration Protocol (DHCP)

DHCP's purpose is to enable individual computers and devices on
an IP network to extract their configurations from a server (the
DHCP server). The overall purpose of this is to reduce the work
necessary to administer a large IP network. The most significant
piece of information distributed in this manner is the IP address.
Activate the DHCP option only if your networks IP addresses are
generated by a DHCP server.
Simple Network Management Protocol (SNMP)
If your network is running Simple Network Management Protocol
(SNMP), you may configure the NetPlus Router to send a block of
information (a trap) when a specific event occurs (for example,
when the error count reaches a predetermined number). Both the
machine name and the IP address of the trap host must be entered.
Trap Host Name: The machine name of the host machine
that will receive trap data from this NetPlus Router. This
information is required for the trap to be received and
retained at the host machine.
The trap host name must include the domain. For an
example, an entry of ADMIN.CSICONTROLS.COM indicates
a machine name of ADMIN in the domain CSICON-
TROLS.COM.
Trap Host IP Address: The IP address of the host machine
that will receive trap data from this NetPlus Router. This
information is required for the trap to be received and
retained at the host machine.
Domain Name Service (DNS)
DNS translates domain names into IP addresses. For example, the
domain name www.example.com might translate to 198.105.232.4.
If your network is configured to use DNS, enter the IP address of
the DNS server. If you have activated the DHCP option, the DNS
IP address may be automatically set by the DHCP server.

I/NET Link Address

As with the Taps, each NPR and must be assigned a system link
address (099). This is the LL portion of the LLSSPPBB I/NET
address (see I/NET Controller LAN Address, below).
This number must be unique on the I/NET system. A duplicate link
address will cause a system error message in I/NET, and will initiate
the appropriate LED error code on the NPR (see Diagnostics
(NPR only) on page 2-31).
I/NET Controller LAN Address
The NPR or Xenta 527/527-NPR resides as a device on the
controller LAN, and must be given a station address (063). This is
the SS portion of the LLSSPPBB address.
Controller LAN Speed (Xenta 527/527-NPR only)
The Xenta 527/527-NPR has the ability to communicate on the
controller LAN at a selectable baud rate either 19200 or 9600.
Choose the speed setting that matches all other devices on the
controller LAN.
Network Connection (NPR only)
Each NPR has two different network connection ports, to support
two different network protocols. Both ports are active for all NPR
models, but only one port can be activated at a time. The port selec-
tion will depend on the network cable connection available at the
remote site.
In order to connect to the network, you must have a network outlet
installed on-site.
Managing Configurations
Saving and Restoring Configurations
The NPR or Xenta 527/527-NPR configuration may be saved to a
local hard drive on the host workstation. The saved configuration
file may be downloaded to the unit using the restore function. This
is similar to the controller save and restore options described in
Station Save and Restore in Chapter 5, Controller Functions.
The configuration save file is in the form:
NAME.NPR

where NAME indicates the name given to this device. This file is
saved in the directory that you have specified for save files (refer to
TCON298, I/NET Seven Getting Started).
The configuration save file allows you to view configuration infor-
mation even if the unit is off-line, and provides a backup in case the
configuration becomes corrupted.
You may also modify a saved configuration off-line, but the
changes will not take effect until:
the unit is on-line, and
the restore function is used to download the changed configu-
ration to the device.
Security
The NPR or Xenta 527/527-NPR configuration may be protected
with a password to prevent unauthorized changes. If a password
has been set for the unit, the configuration cannot be viewed or
changed unless the user enters a password.
The password must also be used before saving or restoring config-
urations.
Diagnostics (NPR only)

The NPR is equipped with a self-diagnostic function that runs
every time the unit is powered up. Four LEDs on the upper right
side of the unit provide feedback of the progress of this test, and
indicate any error conditions.
If the NPR fails the automatic diagnostic pattern, one or more of
the LEDs will remain lit. Other error conditions can also cause the
LEDs to light up. The pattern of lit LEDs indicates the nature of the
error. The diagnostic patterns can be divided into four main cate-
gories: self-test failure, addressing error, firmware failure, and
remote diagnostic session.
See Also: TCON184, Series 2000 NetPlus Router Installation Guide

IP Filtering Communication
IP Filtering
IP filters are available from the I/NET Configuration program.
Using IP filtering, you can configure each I/NET host to only see
specific sections of the overall network. This allows you to create
segmented networks that can be secured from outside access.
Filter Priority
Within the I/NET Configuration program you can select any host
workstation, NPR, or Xenta 527/527-NPR that is currently
communicating with your local host, and view a summary of its IP
filters. These filters are listed and executed in order of their priority.
The first IP filter in the list has the highest priority. The last IP filter
in the list has the lowest priority.
Each filter is configured to affect only one or more specific IP
addresses. When a device attempts to communicate with another
I/NET device on the Ethernet, its IP address is compared with the
target devices IP filters.
Beginning with the highest priority filter, I/NET determines if the
filter pertains to the incoming IP address. If it does, the filters
block or allow setting will determine whether or not commu-
nications are allowed. If the filter does not pertain to the incoming
IP address, or if it allows communication, processing proceeds with
the next highest priority filter in the list. If at any point a filter
blocks the IP address, communications with the device will be
prohibited and no lower priority filters will be processed.
By default, I/NET automatically creates a single filter for each
workstation, NPR, or Xenta 527/527-NPR on the network. This
default filter allows communications with all IP addresses. You can
modify or delete this default filter, and create new filters.
Caution: When configuring IP filtering, be careful not to remove all entries

from the selected device. This would leave the device inaccessible.
I/NET allows you to create the following types of IP filters:

Single IP Address

Communication IP Filtering
Range of IP Addresses
Mask
Filter Mask
This option allows you to filter IP addresses based on a base IP
address and a mask. The mask is used to identify the portion of the
Base IP address that defines a network or subnetwork.
When defining a mask, type 255 for each octet of the Base IP
address that represents a portion of the network address or subnet
address. For example: if the Base IP address defines a class B
network, define a mask of 255.255.0.0. If the base IP address defines
a subnet or Class C network, set the mask to 255.255.255.0.
I/NET performs a bitwise AND operation on the Mask and the
Base IP address. This operation is also performed on the mask and
the incoming IP address of any host that attempts to communicate
with this host. If the result of both operations are equal, communi-
cations will be allowed or blocked, depending on the setting of the
Permission parameter. If the result of both operations are not
equal, this filter will have no affect.

IP Filtering Communication
Heres two examples:
Base IP: 10.0.12.0

(Class B Network: 10.0)
(Subnet Address: 10.0.12)
Mask: 255.255.255.0
Example 1:
Incoming IP Address = 10.0.12.5
1. Perform a bitwise AND of the base IP and mask:
10.0.12.0 (00001010.00000000.00001100.00000000)
AND 255.255.255.0 (11111111.11111111.11111111.00000000)
result: 10.0.12.0 (00001010.00000000.00001100.00000000)
2. Perform a bitwise AND of the incoming IP and mask:
10.0.12.5 (00001010.00000000.00001100.00000101)
AND 255.255.255.0 (11111111.11111111.11111111.00000000)
result: 10.0.12.0 (00001010.00000000.00001100.00000000)
3. The result of 1 and 2 are the same; therefore, allow or block the incoming
IP address according to the setting of the Permission parameter.
Example 2:
Incoming IP Address = 10.0.10.0
1. Perform a bitwise AND of the base IP and mask:
10.0.12.0 (00001010.00000000.00001100.00000000)
AND 255.255.255.0 (11111111.11111111.11111111.00000000)
result: 10.0.12.0 (00001010.00000000.00001100.00000000)
2. Perform a bitwise AND of the incoming IP and mask:
10.0.10.0 (00001010.00000000.00001010.00000000)
AND 255.255.255.0 (11111111.11111111.11111111.00000000)
result: 10.0.10.0 (00001010.00000000.00001010.00000000)
3. The result of 1 and 2 are not the same; therefore, do nothing.
Processing passes to the next filter (if any).

CHAPTER
3
58
System Messages
System messages provide information about events occurring in

the system. A message can be generated when a point changes state,
when an alarm occurs, when a user signs on to a host or controller,
or when virtually any change takes place in the system.
Every I/NET device, including hosts, Taps, controllers, and points
in the system have individual message parameters. These parame-
ters include group, mask, and priority. Routing and storing of these
messages is determined by these parameters. Location of the stored
messages is determined by the Message/masking field in the host
configuration editor.
Routing Parameters
Every I/NET device, including hosts, Taps, controllers, and points
in the system, have individual message parameters. These parame-
ters include message masking and priority. Routing and storing of
messages is determined by these parameters. Storing of messages is
determined by the message masking field in the AMT configura-
tion editor.
Masking
Masking is a combination of the distribution group and active
message mask positions for a system event that generates a message
or alarm. The distribution group and active mask(s) of a message
or alarm determine where that message or alarm will be stored,

Routing Parameters System Messages
displayed and printed. Data will be received, stored, displayed, and

printed only at those host workstations whose distribution group
and active mask selection match the entry for the system event
generating the message.
Note: Masking for the DCU points can be set from any host workstation.
Masking for a host workstation can be set only at that workstation.
You can assign a unique mask in each of the four distribution

groups on each host workstation and printer. Each point and
controller also has a mask and distribution group number that
must correspond to an active position in the mask of the intended
receiving host workstation or printer.
Using this setup allows you to manage your message and alarm
routing. For instance, routine messages (such as door activity) may
be sent to a single workstation, while critical alarms may go to
several, if not all, workstations.
The distribution group is any number from one to four. Each
distribution group has eight mask positions. This makes a total of
32 mask positions (4 8 = 32) that you can use to determine which
workstation(s) will receive which messages and alarms.
Dist. Group 1 2 3 4
Mask
Active Positions
Figure 3-1. Activating Mask Positions
Each DCU editor may have active mask positions in only one
distribution group. The host workstation(s) may have active mask
positions in any or all of the distribution groups.
Note: The far left masking position in distribution group 1 must be acti-
vated in the printer and message/alarm masking configurations
defined in the AMT configuration editor for system-specific messages
to be received at the host or the printer. These messages include Host

System Messages Routing Parameters
sign on, Host sign off, Host lost/restored, Online 90%/95% full,
Online data lost, Special day lost, Time-sync failed, DCU-save failed,
ATS-mstr failed, Auto-DIF failed, and all audit trail messages.
To set the masking, select a distribution group (14), and then acti-
vate each mask position desired. When a DCU generates a message
or alarm, it is sent to all directly-connected workstations. Only
those workstations that have a matching active mask position in the
corresponding distribution group can store, display, and print the
message (see Figure 3-2).
Workstation 1 Workstation 2 Workstation 3

Group 1
Group 2
Group 3
Group 4
Editor A
Dist. Group Information from this
1 2 3 4 editor will be received at
Mask all three workstations.
Editor B
Mask workstations 1 and 3.
Editor C
Mask workstations 2 and 3.
Editor D
1 2 3 4 editor will not be received
Mask at any workstation.
Figure 3-2. Masking and Data Transmission

Routing Parameters System Messages
Note: The active mask position(s) in any resident I/O point or extension
editor must match at least one mask position activated for the desired
workstation(s). If there is no workstation with a matching distribu-
tion group and mask, the message or alarm will be lost (see Editor
D in Figure3-2, Masking and Data Transmission). You may
choose to designate a special workstation with ALL distribution
groups and masks defined, to receive all generated messages and
alarms.
It is recommended that you plan your distribution groups and

masks in advance. Be consistent when assigning the mask posi-
tions. If you use the far right position to send the information to
workstation #1, then use that same position for any and all points
whose messages/alarms are to go to that workstation.
Priorities
Message Priority and Alarm Priority are controlled separately,
though they use the same definitions. Priorities have the greatest
effect on messages and alarms sent through Dial Taps. When
connected through a direct-connect Tap, assigning any priority
level other than None () causes the alarm or message to be sent to
the host immediately. Dial Taps act upon the message or alarm
depending upon the priority.
There are three priority level settings: Routine, Priority, and Crit-
ical. You may also set the priority level to None () for no priority.
The priority level determines how a Dial Tap will handle the
message. A direct-connect host will receive any message with a
priority of Routine or higher. Dial Taps will not send a message
unless it has a priority of Priority or Critical. Priority messages will
cause the Dial Tap to dial out when the deferred dialing parameters
are met, while Critical messages cause the Dial Tap to dial out
immediately.
When used with an auto-dial/auto-answer (AD/AA) LAN Tap, the
message priorities behave as described in Table 3-1.

System Messages Message Queue
Table 3-1. AD/AA LAN Tap Message Priorities
Priority Action
Routine Ignore the message.
Report the message after the Dial Taps Percent Full limit is reached or the Dial Later
Priority
Time Interval has expired.
Critical Report the message immediately.
A Critical message generated by a Dial Tap will also upload all pending Priority messages.
Reliable Tap
If you are configuring an I/NET controller that is loaded with firm-
ware dated 08/21/06 or later, you can implement reliable messaging
by specifying a Reliable Tap. Refer to Reliable Messaging on page
3-7 for more information about this I/NET feature.
Message Queue
Every device in I/NET contains a message queue to store incoming
point messages, alarms, transactions, upload requests, system
broadcasts, etc. The purpose of the message queue is to support
large surges of message traffic for distribution onto unsolicited
controller LANs (RS485) or upstream devices (Link Tap or work-
station). The size of the queue is a function of the device. All I/NET
controllers contain a fixed-length queue and all external Taps
contain a variable-length queue. Any time a queue gets full, the
device will replace the oldest message with the newer message on a
first-in, first-out (FIFO) basis. Consequently, it is important to
understand how the system distributes and stores system messages
in order to determine the best system configuration to suit your
needs.
Each LAN device is designed to provide a maximum of 10 messages
per second on an unsolicited token passing RS485 LAN. To reduce
the effects of this system limitation, care should be taken regarding
system architecture, scan rates on points, broadcast change counts
on analog points, scans between broadcast on global pulse input
points, etc.

Buffer Capability System Messages
Buffer Capability
Even though every device in the system contains a message queue,
only a few of the devices will successfully buffer the queued
messages for later distribution. All controllers and Taps distribute
messages out of their RS485 port even with the absence of any LAN
communication. This is due to the fact that there is no requirement
for an acknowledgment to be received at the generating device. The
RS485 LAN is for both solicited and unsolicited message traffic.
The only devices that perform extended buffering are the ones
which directly communicate to polling devices such as the 7801
Taps, 7803 Taps, 7804 Taps, and all DPUs/SCUs. The MRs, ASCs,
and UCs do not generate messages; messages relating to these
devices are generated by the relevant MRI, MCI, etc.
The following is a detailed breakdown of each device and its avail-
able message buffering capacity:
7801/7803/7804/7806 EPROM Taps = approximately 1000
messages
7801/7803/7804/7806 MIP Taps = approximately 1200
messages
7716xx/7718xx/7756xx/7780xx/7792xx = approximately 150
messages
7791xx/7793xx/7798xx
Controller software prior to I/NET version 2.0 = approx-
imately 150 messages.
Controller software for I/NET version 2.0:
Without embedded Tap = approximately 100
messages
With embedded Tap = approximately 1000 messages
DPU7910A and DPU7920
Controller software before version 2.20 = exactly 100
messages

System Messages Reliable Messaging
Controller software version 2.20 and later = variable,

based on the number of resident individuals (refer to
Table 9-2, DPU7910A or DPU7920 Memory Manage-
ment, in Chapter 9).
DPU48K = variable, based on the number of resident individ-
uals and active secondary schedules (refer to Table 9-3,
SCU1284 and DPU7920 w/DPU48K Memory Management,
in Chapter 9).
SCU1284 = variable, based on the number of resident indi-
viduals and active secondary schedules (refer to Table 9-3,
SCU1284 and DPU7920 w/DPU48K Memory Management,
in Chapter 9).
NetPlus Router = approximately 1000 messages
Note: xx represents the embedded 7801/7803/7806 Taps functions
All other controllers (RS485 only), 7802 Taps, 7805 Taps, Micro
Regulators (MRs), Application Specific Controllers (ASCs), and
Unitary Controllers (UCs) contain no buffering capability. The
message buffering capacities listed above are true for all message
types except Action messages, which require twice as much
memory.
An overflow message is generated by a DPU/SCU whenever the
message queue gets full and at least one transaction has been lost.
The overflow message is stored in a protective memory location
and is the first message uploaded when communication is restored
to the controller.
The buffering approximations on Taps are due to the varying sizes
of the Taps downloaded binary file and editor entries such as
phone numbers.
Reliable Messaging
Reliable messaging describes a way of configuring controllers so
that they verify that their messages are being received by a target
device.

Reliable Messaging System Messages
Each controller on a controller LAN can distribute its messages in

either of the following ways:
through its RS485 port
through its RS232 port when emulating a tap
A controller communicating through its RS232 port will automat-
ically use reliable messaging to ensure that its messages are being
delivered.
A controller communicating through its RS485 port may or may
not use reliable messaging, depending on its configuration.
Defining a Reliable Tap

Using the DCU configuration editor in I/NET, you can configure a
controller (firmware dated 08/21/06 or later) for reliable messaging
by specifying a reliable tap. The reliable tap can be any tap (or
device emulating a tap) that is being used to route messages from
the controller to an I/NET host.
When a controller is configured to communicate with a reliable tap,
it will not purge a sent message from its queue, nor will it send any
other messages, until it has received an acknowledgment from the
reliable tap.
Storing Messages During a Communication Failure

When a controller loses communication with its reliable tap, it
begins storing messages in its message queue. If communications
between the controller and its reliable tap are not restored before
the message queue gets full, the controller will begin replacing its
oldest messages with newer messages on a first-in, first-out (FIFO)
basis.
When communications between a controller and its reliable tap are
restored, the controller will once again begin transmitting its
messages at a rate of up to 10 messages per second. If any messages
were lost during the communication outage, the controller will
send a DCU Queue ovflw message. The date/time stamp for this
message will be the date and time of the first message that was lost.

System Messages I/NET AMT
The value assigned to the DCU Queue ovflow message represents

the number of messages that were lost during the communication
outage.
Retaining Messages During a Power Failure

Any messages stored in a controller's message queue are battery-
backed and are protected from loss during a power failure. This is
true regardless of whether or not the device has been configured
with a reliable tap.
I/NET AMT
I/NET AMT (Alarms, Messages, and Transactions) is the program

that controls communication traffic relating to I/NET Seven
system events. Event notices are divided into three categories
(alarms, messages, and transactions). The I/NET system generates
and sends a notice anytime a specific event occurs.
The I/O Server program must be running in order to store and
route system communication traffic. You do not need to be
running the I/NET Seven host interface or AMT. Refer to
TCON298, I/NET Seven Getting Started, for more information
about I/O Server.
Warning: If I/O Server is not running the system will not record any incoming
event notices (alarms, messages, or transactions) or SevenTrends
data.
Overview
Each system event is a message; something that happened within
the I/NET environment. Event notices pertaining to access control,
such as door reader activity, are transactions.

I/NET AMT System Messages
Certain messages and transactions may also be classified as alarms,

if somebody needs to be aware of the event. Any alarm is also either
a message or a transaction. An alarm is a higher level notice, as
somebody must acknowledge receipt of the event notice. Alarms
are further divided into three levels: Routine, Priority, and Critical.
File Storage
All I/NET AMT events (messages, transactions, and alarms) are
stored in a database table. This database includes individual tables
for events (messages and transactions) and alarms. The database is
capable of storing up to 20 million AMT records.
The alarm database table stores the active alarms of each priority.
Each alarm event is also stored in the events table.
I/NET AMT Screen
The I/NET AMT screen allows you to open up multiple windows,
each of which can be configured separately. Preconfigured
windows provide the classic I/NET window layouts.
Display Mode
There are two display modes: tile and cascade. In tile mode, the
windows are automatically sized to fit into the AMT screen without
overlapping, showing all windows at once. In cascade mode the
windows are placed one on top of the other (overlapping), showing
only one window at a time.
You may toggle between display modes at any time using the
Windows menu options.
Active Window
Only one AMT window is active at any given time. The active
window is designated by a solid title bar. A window must be active
to scroll through, or update, the window entries.
Note: Only entries in Alarm windows may be updated. Updating entries

includes acknowledging and purging alarms, and entering dispatch
messages.

Toolbar
The toolbar options on the AMT screen provide an alternate
method of accessing selected menu commands. The toolbar may be
docked or floating.
Depending on the active window, one or more toolbar options may
be grayed out or unavailable. The operators access level may also
cause one or more toolbar buttons to be grayed out, if the operator
is not authorized to perform that function.
User Settings
AMT saves the settings for each user. When you log into AMT, the
settings will be the same as the last time you logged out. The
following settings are saved:
Configuration settings (see Configuration on page 3-12):
Alarm and archive color settings
Toolbar and status bar settings
Alarm topmost setting
Settings for open windows:
Size and placement
Window options, including name and filter selection (see
Window Options Editor on page 3-16)
Auto-image verification settings, including door filter
and field selection, for open event windows (see Image
Verification on page 3-48)
Note: Static image verification window settings are not saved. Any open
static image verification windows will be discarded upon logoff, and
will not reappear upon subsequent login.
Security
The AMT functions, including window display, may be protected
by password. When you set password access in the Host Passwords
editor, you may select which AMT functions can be accessed with
that password. Refer to Host Passwords in Chapter 4, Host Func-
tions.

Configuration
The AMT configuration editor allows you to set the display param-
eters for I/NET AMT.
Miscellaneous
This section allows you to set display options in AMT.
Display site address 0 as blank This option, when activated,
leaves the Site Address field blank in open windows, if the site
address is zero (0). This allows you to quickly skim the list for dial
and/or Distributed Link Architecture (DLS) sites.
See Also: Integrated Dial Function in Chapter 2, Communication

Distributed Link Architecture (DLA) Support in Chapter 1,
System Configuration
Alarm topmost This option, when activated, will cause the
AMT screen to come to the front of the computer screen when a
new alarm is received. The AMT screen will move in front of any
other program screen you are currently viewing, including an
I/NET screen or any other application.
See Also: Alarm Notification on page 3-18

Max Online Events The upper limit for events stored online, in
thousands (an entry of 100 indicates 100,000 online events). Once
this number is reached, old events are replaced by new ones, on a
first-in, first-out basis, and can no longer be viewed on the AMT
screen. This field is for display only.
See Also: CCTV on page 3-50

Alarm Colors
This section allows you to determine the colors used to indicate the
status of an alarm. These colors are used only in the AMT windows,
and are not part of the actual database files. If you change the
colors, all existing alarm entries will change to reflect the new color
scheme.
Foreground Select the foreground color for each alarm status.
This is the color of the text within the entry.

Background Select the background color for each alarm status.

This is the color of the table cell within the entry.
To select a color, click under either foreground or background on
the appropriate alarm status:
Unack Alarm This status indicates a point that is currently in
alarm, and the alarm has not yet been acknowledged by an oper-
ator. All new alarms will have this color until they are either
acknowledged or return to normal.
Ack Alarm This status indicates a point that is currently in
alarm, but the alarm has been acknowledged by an operator.
Unack RTN This status indicates a point that is not currently in
alarm, but previously had an alarm that remains unacknowledged.
A selection window will pop up, showing the available colors. The
selected color will appear in the block next to the selected status.
Image Window
This section allows you to set a timer that controls the length of
time that the image verification window stays open. You can set a
time of up to 60 minutes. A setting of zero causes the image verifi-
cation window to stay open until it is manually closed by the oper-
ator.
Archive Colors
This section allows you to specify the foreground and background
colors for archived events. These colors are used only in the AMT
windows, and are not part of the actual database files. If you change
the colors, all archived events listed will change to reflect the new
color scheme.
Foreground Select the foreground color for archived events.
This is the color of the text within the entry.
Background Select the background color for archived events.
This is the color of the table cell within the entry.
To select a color, click under either foreground or background, and
select the desired color from the color selection palette.

Relay Tap
This section contains two options, Priority and Critical. When you
enable an option in this section, it's corresponding relay in the
7801R tap will activate if an alarm of the correct priority passes
through, unless it is one of the following:
Return to normal Sign on Host

Door normal Sign off Host
Action message Sign on DCU
Dispatch message Sign off DCU
LAN reconfigure Host restored
Station restored LAN tap restored
MCU restored
Note: It is important not to check these boxes unless there is an actual 7801
or 7801R tap connected. Otherwise, enabling these options will result
in messages/alarms not being displayed in AMT.
Audible Alarms
This section allows you to determine which alarms shall generate
an audible alarm, and the duration of the audible tone. For each
alarm type (Routine, Priority, and Critical), select the type of
audible alarm that will be generated.
None: an alarm of this type will not generate an audible tone.
Once: and alarm of this type will generate and audible tone
that plays once.
Timed: an alarm of this type will generate an audible tone that
lasts for a specific time period (see below), or until the alarm
is acknowledged or silenced, whichever comes first.
Constant: an alarm of this type will generate an audible tone
that continues until the alarm is acknowledged or silenced.
Audible duration Enter the duration of a Timed audible alarm,
in seconds.

A default .WAV sound file is supplied for each alarm priority.

However, you may elect to assign a .WAV sound file of your own
choosing to be played when an alarm of the appropriate priority is
received. Please note that only .WAV sound files may be used for
audible alarms.
Note: If an alarm sound is already playing and a new alarm arrives, the
sound which is already playing will only be stopped if the new alarm
is of greater priority.
Message/Alarm
Use this section to set the message and alarm masking for this
workstation. Refer to Masking on page 3-1 for a complete
description of message masking.
Printer
Use this section to set the message and alarm masking for a printer
connected to this workstation. If no printer is connected to the
workstation, you may skip this section. Refer to Masking on page
3-1 for a complete description of message masking.
Note: The message mask must match at least one workstation mask to be
received, and must also match at least one printer mask in order to be
sent to the printer.
Force Dispatch
Use this option when you wish to require a dispatch message on
alarms. To use this option, set the desired distribution group(s) and
mask position(s). Any alarms with at least one matching mask
position can be acknowledged, but must have a dispatch message
before they can be cleared from the alarm window.
Acknowledge Return-to-Normal
Use this option when you wish to require a separate acknowledg-
ment for a return-to-normal message. To use this option, set the
desired distribution group(s) and mask position(s). Alarms which
have returned to normal will still remain in the alarm window, even
after the original alarm is acknowledged, until the return to normal
message is also acknowledged.

Window Options Editor

The Window Options editor allows you to individually configure
each window you open in I/NET AMT. The window settings will
remain as long as the window is open. Open windows and their
settings are saved at log-off, and will display when you log back in.
This editor appears automatically when you open a new window
(except for predefined windows), and may also be opened manu-
ally any time you wish to change the display options for the active
window.
Selected
The parameters listed here will appear in the selected window. The
order of the columns will be the same as displayed here, with the
top parameter being the left-most column. Use the Move Up and
Move Down buttons to rearrange the column order.
De-Selected
The parameters listed here will not appear in the selected window.
Use the Add, Remove, Add All, and Remove All buttons to move
the parameters between the Selected and De-Selected lists.
Sort By
This option allows you to select the parameter that you wish to use
as the sort criteria for the window. This option is only available for
alarm windows. Only the parameters in the Selected list are avail-
able. Once you have selected the parameter to sort by, select
whether the sort is to be in Ascending or Descending order.
Filter
Select the filter to use for this window. All existing filters appro-
priate to this window type are listed.
Note: Only one filter may be applied to an AMT window. If the active
window is already using a filter, including one of the predefined
filters, selecting a filter here will change the window to use only the
selected filter.
See Also: Filtering on page 3-23

Use Default Window Name

This checkbox indicates whether you wish the windows title bar to
contain only the default information: filter name, sort column
(alarm windows only), and pause indicator (if applicable). Disable
this box to enter a custom window name.
Window Name
The custom name for this window. The name will be added to the
windows title bar. The default data (see above) remains in the title
bar as well. This option is only available if the Use default window
name box is disabled.
Alarms
I/NET alerts you to alarm conditions and gives you a way to locate,
acknowledge, and purge these alarms, as well as add dispatch
messages to them.
The I/NET AMT alarm windows display the active alarms for the
selected filter criteria. The window header lists the filter name, the
number of alarms, and the number of unacknowledged alarms.
The specific data listed for each entry depends on the selected
window settings. The alarms are shown in reverse order, with the
most recent alarm listed first. If you have a system printer with
appropriate masking, the alarms will also be printed on the system
printer.
The Archive utility allows you to save these records indefinitely,
depending only on the storage space available on your system.
Alarm Totals
Each alarm window shows the number of active alarms and the
number of unacknowledged alarms. These totals apply only to
alarms which meet the selected filter criteria.
Alarms is the number of points currently in alarm. If a point
was in alarm but has returned to a normal state, it is not
counted in this total.

Unack Alarms is the number of points with unacknowledged

alarms. If a point was in alarm but has returned to a normal
state, it is still counted in this total if the alarm was never
acknowledged. Thus, you could have a situation where your
unacknowledged alarm total is higher than your alarm total.
The AMT header contains the total number of active alarms and
unacknowledged alarms, for all points. If your alarm window is
unfiltered, the totals on the alarm window will match the totals in
the AMT header.
If AMT is minimized, you can check the alarm totals by placing
your cursor over the AMT taskbar item. The popup window will
show the current alarm and unacknowledged alarm totals.
Alarm Notification
If you have a message/printer mask and distribution group defined,
then points matching at least one of the active mask positions will
store/display/print the alarm messages. Any host workstation with
a matching distribution group and active message mask will receive
the alarm.
There are three forms of alarm notification. Depending on your
configuration settings, you may have one, two, or all three methods
active.
Flashing bar Whenever there is an unacknowledged alarm
(any priority), the taskbar button for AMT will flash. The title
bars for minimized alarm windows with unacknowledged
alarms will also flash. This is an automatic notification, which
cannot be disabled.
Top screen If you selected the Alarm topmost option in
the AMT configuration screen, a new alarm will cause the
appropriate AMT window to move to the front of your
desktop, on top of any open application windows (such as
I/NET).
You may select another application window, which will then
move in front of the screen, but any additional incoming
alarms will move AMT to the front of the desktop again.

Audible tone If you specified an audible alarm for one or

more alarm priorities, any incoming alarm with the desig-
nated priority will initiate the alarm tone. This tone will
sound for the duration set, or until the alarm is acknowledged
or silenced, whichever comes first.
The F2 function key will silence the alarm. You may also
silence the alarm using the Silence Alarm option on the
Actions menu, or by selecting the Silence Alarm button.
The audible alarm is not related to the Alarm topmost option:
the alarm will sound whether I/NET AMT is the top window
or not.
See Also: Configuration on page 3-12

Alarm Windows
Alarm windows display all active alarms for the selected filter.
These are points that are, or have been, in alarm.
Three status indicators are available for alarms. Use the Colors
section of the AMT configuration editor to set the color for each
condition (see Configuration on page 3-12). The conditions are
as follows:
Alarm. The point is currently in alarm, and the alarm has not
yet been acknowledged.
Alarm Ack. The point is currently in alarm, and has already
been acknowledged.
Ret. Normal. The point went into alarm, but has since
returned to its normal (non-alarm) state without the alarm
being acknowledged.
The alarm fields are listed in Table 3-2. Your window may or may
not display all of the fields, depending on the settings you selected
in the Window Options editor for this window (see Window
Options Editor on page 3-16).

Table 3-2. Alarm Field Descriptions
Field Description
Date The date and time this entry was last updated. Initially, this shows
the date and time that the original alarm occurred. Any activity
Time (alarm, return to normal, acknowledge, or dispatch message)
updates the date and time for the entry.
Cycle count indicating how many times the point has gone into
alarm. The count increases each time the point cycles into alarm.
The count continues until the entry is purged.
Count
Note: The count does not differentiate between acknowledged
and unacknowledged alarms: it merely counts the number
of alarms.
Address The point address generating the alarm.
The name of the link containing the device that generated the
alarm. If the alarm is generated by a host or link, this field will be
Link name blank and the host or link name will be in the Device Name field
(see below). The value of this field is determined by the name given
to the link in the network configuration.
The name of the station containing the device that generated the
alarm. If the alarm is generated by a host, link, or station, this field
will be blank and the host, link, or station name will be in the
Station name
Device Name field (see below). The value of this field is
determined by the name given to the station in the network
configuration.
The name of the device generating the alarm.
If the device generating the alarm is an MCU, this field will be
blank, as the Link Name and Station Name fields identify the
Device name device.
If the device generating the alarm is a door, this field will contain
the door name, if available. If the door name is not available, the
point name is displayed.
The site number (01-63) assigned to the device which generated
Site name
the message.
Event Type The specific event causing the alarm condition.
Priority The priority setting for this alarm.
The current state of this alarm: unacknowledged, acknowledged,
Acknowledge Status
or returned to normal (unacknowledged).
If an event action has been defined for this event type, the action
message will display in this field. If the alarm is a Bad Card Read
Action Message
generated by a card number not in the system, this field will
indicate the card number. Otherwise, the field will be blank.

Table 3-2. Alarm Field Descriptions (Continued)
Field Description
If an operator has entered a dispatch message for this alarm, the
Dispatch Message
message will display in this field. Otherwise, this field will be blank.
The number assigned to the CCTV camera that generated the
alarm. This field is blank when the alarm is not associated with a
Camera CCTV camera. Refer to TCON301, I/NET Seven Database
Connectivity and Reporting, for more information about integrating
CCTV with I/NET Seven.
The value of a user-defined field for the individual associated with
the alarm. Use the Access Control Options editor to designate one
Unique Field of the 16 user-defined fields as a unique user field. Refer to the
description of the Unique User Field parameter on page 9-87 for
more information.
Event Messages
The I/NET system uses event messages to notify you of specific
event occurrences. When you enter your point information, you
specify the actions which will generate messages. Message masking
is used to determine which messages are stored/printed at specific
operator workstations.
Message Display
The AMT database can contain up to five million events. Events are
listed chronologically, with the most recent message at the top of
the list. The messages displayed will depend on the filter selected
for the window. Each message includes the information described
in Table 3-3. Your window may or may not display all of the fields,
depending on the settings you selected in the Window Options
editor for this window (see Window Options Editor on page
3-16).
Table 3-3. Message Field Descriptions
Field Description
Date The date this message was generated.

Time The time of day (in 24-hour time) this message was generated.
The system address of the point or station address of the host or
Address
controller which generated the message.

Table 3-3. Message Field Descriptions (Continued)
Field Description
The name of the link containing the device that generated the
message. If the message is generated by a host or link, this field
Link name will be blank and the host or link name will be in the Device Name
field (see below). The value of this field is determined by the name
given to the link in the network configuration.
The name of the station containing the device that generated the
message. If the message is generated by a host, link, or station,
this field will be blank and the host, link, or station name will be in
Station name
the Device Name field (see below). The value of this field is
determined by the name given to the station in the network
configuration.
The assigned name associated with the Tap, controller, or point
Device Name
which generated the message.
The site number (01-63) assigned to the device which generated
Site
the message.
Event type The event that generated this message.
First Name (Transaction only) The first name of the individual.
Last Name (Transaction only) The last name of the individual.
Group Name (Transaction only) The primary group assigned to the individual.
Tenant (Transaction only) The tenant number for this individual.
Individual (Transaction only) The individual number.
The analog value of a point in alarm, or the analog value of a
Value
manually commanded point.
If an operator has entered a dispatch message for an entry, the
dispatch message will display in this field. Otherwise, this field will
Message
be blank. This field can only be populated if this event also
generated an alarm.
Zone (Transaction only) The access control zone for the key/card reader.
Cell The SevenTrends cell number assigned to alarms from this point.

Table 3-3. Message Field Descriptions (Continued)
Field Description
The value of a user-defined field for the individual associated with
the event. Use the Access Control Options editor to designate one
Unique Field of the 16 user-defined fields as a unique user field. Refer to the
description of the Unique User Field parameter on page 9-87 for
more information.
The number assigned to the CCTV camera that generated the
alarm. This field is blank when the alarm is not associated with a
Camera CCTV camera. Refer to TCON301, I/NET Seven Database
Connectivity and Reporting, for more information about integrating
CCTV with I/NET Seven.
Filtering
Use the Filter editor to select criteria used to select events for
display. If you do not use filters, the system displays all messages
from all possible point types and all possible point addresses. You
may find that this produces an unmanageable amount of informa-
tion.
The filter editor will have a slightly different appearance,
depending on the type of window selected.
If the active window is an event window, or if there are no
open windows, the Event Filter editor displays. This version of
the editor includes the Event Info section, used to select indi-
vidual event types for display in event windows, and the
button to open the Transaction Filter editor. Filters defined
through this editor are available for all window types, but
alarm windows will ignore any event and/or transaction
filtering parameters.
If the active window is an alarm window, the Alarm Filter
editor displays. Alarm filters do not include the Event Info
section or access to the Transaction Filter editor.
Note: Archiving and filtering both use a great deal of system resources.
While archiving, particularly when there are a large number of
online AMT records, it may appear as though your AMT filters are
not operating properly. Filter operation will return to normal when
the archive function is complete.

The system displays messages in chronological order, with the most

recent messages displayed first. The range options include date
range, time range, and point address range. You may wish to use
one or more range options to limit the information displayed on
the message screen. The range options are co-dependent: only
messages which meet all three range entries will appear in the
display window.
Point Address
Set the Point address range Start and End parameters to limit the
resulting message list to specific addresses. Messages originating
from addresses outside of this range will be excluded.
Device Name
The desired Device name. The default is [All] for all devices. Enter
up to 16 characters, including the wildcard characters ? (single
character replace) and * (multiple character replace).
Priority
Select the Priority for the system message. Only messages with the
selected priority (set in the DCU editor) will be included in the
window view.
Site
Select the starting and ending Site numbers. Messages originating
from sites outside of this range will be excluded.
Cell
Select the starting and ending Cell numbers. This corresponds to
the cell number entered in the Resident I/O Points editor for the
selected point(s). Messages originating from points will cell
numbers outside of this range will be excluded.
Filter Date Range
This section allows you to use a date or date-time range to filter
events. The date-time range is typically used when attempting to
pinpoint a particular event. There are two steps to this process:

Specify the type of range you wish to use, either date only or
date and time. Do not activate the checkboxes if you do not
wish to filter by date. You cannot filter by time unless you are
also filtering by date.
Specify the start and end of the selected chronological range.
The range is inclusive.
Note: If you enter a time range but have not activated time range filtering,
the time entries are ignored.
Event Info
This option only appears in the Event Filter editor, which appears
when the active window is an event window, or when there are no
open windows (and thus no active window) when the filter editor
is accessed. This feature is used to filter the displayed events
according to the type of event. These option settings are ignored if
the filter is applied to an alarm window.
This listbox contains a list of all possible messages. Select which
events will be listed in the active event window. You will probably
want to select only certain event types, to produce a manageable
number of messages.
Note: This filtering only controls which messages are displayed in the
I/NET AMT event windows. Messages are generated according to the
parameters set in the individual DCU point databases. If this filter is
applied to an alarm window, event filtering is ignored.
If at least one transaction (access control) event is selected, the Tran

Filtering button becomes active, allowing access to the Transaction
Filter editor. Refer to Transaction Filter on page 3-45.
Event types are listed in Table 3-4. This table also shows the
description, source, and the masking and priority required to
receive each message.

Table 3-4. Event Types
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Operator has
Host configuration
acknowledged an
Host editor message/
Acknowledge NA NA Online 90% full, Online
workstation alarm mask: group
95% full, or Online
1, far left position
data lost message.
An event-driven
message was
generated (point went
Event actions
Action message DCU NA R, P, C into/out of an alarm
editor
state, to a specified
state, or crossed a
certain value).
Resident I/O points
Alarm An alarm has been
editor for DA, DM,
acknowledge DCU R, P, C NA acknowledged by an
DO, DC, and AI
operator operator.
points
The archive activity
completed
successfully. If
Archive
Host verification was
Archive complete configuration audit R, P, C NA
workstation enabled, this message
trail mask
indicates that
verification was
successful.
The archive activity did
Archive not complete
Host
Archive failed configuration audit R, P, C NA successfully. The type
workstation
trail mask of error is listed in the
event description field.
Automatic
DCU configuration Temperature Control
ATC start DCU NA R, P, C
editor in the DCU was
enabled.
Automatic
DCU configuration Temperature Control
ATC stop DCU NA R, P, C
editor in the controller was
disabled.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

Table 3-4. Event Types (Continued)
Required Required
Message Enabled by
Priority* Priority*
Resident I/O points Automatic Time

ATS control DCU editor for DO/DC NA R, P, C Schedule control has
points commanded this point.
Automatic Time
DCU configuration
ATS start DCU NA R, P, C Scheduling in the DCU
editor
was enabled.
Automatic Time
DCU configuration Scheduling in the
ATS stop DCU NA R, P, C
editor controller was
disabled.
An Automatic Time
Host configuration Schedule master
Host editor message/ schedule
ATS-mstr failed NA NA
workstation alarm mask: group programming attempt
1, far left position has failed to reach a
remote controller.
The card reader was
unable to validate the
card entered by the
user.
If the DPU/SCU is
Resident I/O points currently sensing a
DPU or editor for door Wiegand reader
Bad card read R, P, C NA
SCU1284 parent point (BB = tamper condition, this
08 or 09) message can occur
each time a
subsequent Reader
Tamper signal is
received at the
DPU/SCU.
An unsuccessful
Resident I/O points command was issued
Command error DCU editor for output R, P, C NA to a point
points (communication
failure).
Resident I/O points This point was
Host
Control editor of DC, DO, NA R, P, C commanded by a host
workstation
AO, and GO points workstation.

Required Required
Message Enabled by
Priority* Priority*
Operator
Host, link, or LAN acknowledged a DCU
Host
DCU alm ack Tap configuration NA R, P, C Lost, DCU Restored,
workstation
editor mask or DCU SW Lost
message.
The downloadable
software in a controller
DCU software DCU configuration has been lost. You
DCU NA R, P, C
lost editor mask must restore the
controller software and
database.
An automatic
Host configuration
controller save from a
DCU-save failed NA NA remote controller has
failed to reach the
host.
Resident I/O points The point has been
Demand control DCU editor for DO/DC NA R, P, C shed or restored by
points demand control.
The predicted demand
Resident I/O points at the end of the
Demand editor for Demand current demand
DCU R, P, C NA
exception programs current interval will exceed the
demand point user-specified shed
target.
Entry through an
access controlled door
was denied until the
DPU or Door extension individual exits the
Deny entry APB R, P, C NA
SCU1284 editor same door or another
door within the same
anti-passback (APB)
zone.
Entry through an
DPU or Door extension
Deny entry dsbl R, P, C NA was denied because
SCU1284 editor
the key/card used is
disabled.

Required Required
Message Enabled by
Priority* Priority*
Entry through an
DPU or Door extension was denied because
Deny entry PIN R, P, C NA
SCU1284 editor an invalid personal
identification number
(PIN) was entered.
Entry through an
DPU or Door extension was denied because
Deny entry sched R, P, C NA
SCU1284 editor the individual is not
allowed access at the
time attempted.
Entry through an
was denied because a
DPU or Door extension door and personnel
Deny entry sel R, P, C NA
SCU1284 editor schedule has not been
selected for the
individual, or the
individual is disabled.
Entry through an
was denied because
the individuals
Deny entry DPU or Door extension key/card is not in the
R, P, C NA
tenant SCU1284 editor system, or the
individual is attempting
to enter a door
assigned to a different
tenant.
Exit through an access
controlled door was
Deny exit dsbl R, P, C NA denied because the
SCU1284 editor
key/card used is
disabled.

Required Required
Message Enabled by
Priority* Priority*

controlled door was
DPU or Door extension denied because an
Deny exit PIN R, P, C NA
SCU1284 editor invalid personal
(PIN) was entered.
controlled door was
DPU or Door extension denied because the
Deny exit sched R, P, C NA
SCU1284 editor individual is not
allowed access at the
time attempted.
controlled door was
denied because a door
Deny exit sel R, P, C NA and personnel
SCU1284 editor
schedule has not been
selected for the
individual.
controlled door was
denied because the
individuals key/card is
Deny exit tenant R, P, C NA not in the system, or
SCU1284 editor
the individual is
attempting to exit a
door assigned to a
different tenant.
Resident I/O points
An operator entered
or Tap
dispatch message has
Configuration
Host been
Dispatch editor of point or R, P, C R, P, C
workstation generated/printed in
device which
response to a
reported original
point/device alarm.
alarm
DCU configuration Demand control in the
DMD start DCU NA R, P, C
editor DCU was enabled.

Required Required
Message Enabled by
Priority* Priority*
Demand control in the

DCU configuration
DMD stop DCU NA R, P, C controller was
editor
disabled.
Resident I/O points
An access controlled
DPU or editor for door
Door normal R, P, C NA door has returned to
SCU1284 parent point (BB =
normal.
08 or 09)
Resident I/O points
Door re-locked R, P, C NA door has automatically
SCU1284 parent point
re-locked.
(BB = 08 or 09)
A Door Open Too Long
Resident I/O points alarm has been
DPU or editor for door received.
DOTL R, P, C NA
SCU1284 parent point (BB = This alarm will not be
08 or 09) generated if the door is
in Unlocked mode.
The message storage
Host configuration
capacity of a DPU has
DPU or editor message/
DPU queue ovflw NA NA been exceeded.
SCU1284 alarm mask: group
Messages are being
lost.
Resident I/O points
A duress code has
Duress elev R, P, C NA been entered at an
elevator PIN pad.
08 or 09)
A duress code has
Duress entry R, P, C NA been entered at an
SCU1284 editor
entry reader PIN pad.
A duress code has
Duress exit R, P, C NA been entered at an exit
SCU1284 editor
reader PIN pad.
The host workstation
Host configuration
is currently unable to
DVR Srv Offline NA NA communicate with the
Workstation alarm mask: group
Digital Video Recorder
(DVR) server.

Required Required
Message Enabled by
Priority* Priority*
The host workstation

Host configuration is successfully
Host editor message/ communicating with
DVR Srv Online NA NA
Workstation alarm mask: group the Digital Video
1, far left position Recorder (DVR)
server.
Host configuration
A change in the
Edit AIC NA NA access initiated control
editor has been made.
Host configuration
A change in the DCU
Edit DCU PW NA NA passwords editor has
been made.
Host configuration
A change in the
Edit Door NA NA access control door
Host configuration
A change in the
Edit Elev. NA NA elevator editor has
been made.
Host configuration
A change in the
Edit Group NA NA access control group
Host configuration
A change in the host
Edit Hst PW NA NA passwords editor has
been made.
Host configuration A change in the
Host editor message/ access control
Edit Indiv. NA NA
workstation alarm mask: group individuals editor has
1, far left position been made.
Edit P/Schd NA NA
workstation alarm mask: group personnel schedule
1, far left position editor has been made.

Required Required
Message Enabled by
Priority* Priority*
Host configuration
A change in the
Edit Tenant NA NA access control tenant
Edit Trans. NA NA
workstation alarm mask: group key/card translation
1, far left position editor has been made.
A valid key/card was
DPU or Door extension used in an access
Elev entry R, P, C NA
SCU1284 editor controlled elevator
reader.
A valid personal
Elev entry - PIN R, P, C NA was used in an access
SCU1284 editor
controlled elevator
reader.
Resident I/O points A point has been
DCU or
Event control editor for output NA R, P, C commanded by an
SCU1284
points event sequence.
Resident I/O points
Forced Door R, P, C NA door has been forced
open.
08 or 09)
Resident I/O points A point has been
HHC control HHC editor for DC, DO, NA R, P, C commanded by an
AO, and GO points HHC.
Resident I/O points An analog or digital
High limit alarm DCU editor for AI/GI R, P, C NA input point exceeded
points its high limit value.
Remote host Host configuration I/NET has lost
work-station editor message/ communications over
Host lost NA NA
on same alarm mask: group the Ethernet LAN with
Ethernet LAN 1, far left position a host workstation.

Required Required
Message Enabled by
Priority* Priority*
The host LAN has

reconfigured because
Host LAN Host Tap
Host Tap NA R, P, C a device has been
reconfigure configuration editor
added or taken away
from the LAN.
Remote Host I/NET has established
workstation communication with a
Host configuration NA NA
on same host workstation over
Host restored Ethernet LAN editor message/ the Ethernet LAN.
alarm mask: group
1, far left position I/NET program
Any Host
NA NA background driver
workstation
started.
The downloadable
software in a Host Tap
Host Tap
Host Tap Host Tap, has been lost. You
configuration editor NA R, P, C
software lost NPR must restore the Tap
mask
software and
database.
Host configuration The downloading of
Host editor message/ Individuals information
Ind. D/L failed NA NA
workstation alarm mask: group to a DPU/SCU has
1, far left position failed.
The IP address
selected for the NPR
or Xenta 527/527-NPR
NPR or Xenta NetPlus Router
IP Addr Conflict N/A N/A is a duplicate of
527/527-NPR configuration editor
another IP address
already residing on the
system.
The controller LAN
Site (LAN)
has undergone
Tap, Link Tap, Host, link, or LAN
reconfiguration
LAN reconfigure Host Tap, Tap configuration NA R, P, C
because a device was
NPR, Xenta editor
added or taken away
527/527-NPR
from the LAN.
Host or Link Tap An operator has
Host
LAN Tap ack configuration editor NA R, P, C acknowledged the
workstation
mask LAN Tap lost alarm.

Required Required
Message Enabled by
Priority* Priority*
I/NET has lost

Host or Link Host or Link Tap
LAN Tap lost NA R, P, C communication with
Tap configuration editor
this LAN Tap.
I/NET has
Host or Link Host or Link Tap reestablished
LAN Tap restored NA R, P, C
Tap configuration editor communication with
this LAN Tap.
The downloadable
software in a LAN Tap
LAN Tap
LAN Tap Site (LAN) has been lost. You
configuration editor NA R, P, C
software lost Tap must restore the Tap
mask
software and
database.
A control action has
Resident I/O points been issued to a
editor for lighting lighting zone and its
Lighting control 7780 DLCU NA R, P, C
zones and/or associated circuits by
circuits the override
pushbutton.
An operator has
Host Tap
Host acknowledged a Link
Link ack configuration editor NA R, P, C
workstation Tap Software Lost
mask
alarm.
The link address
Link # Conflict N/A N/A is a duplicate of
another link address
already residing on the
system.
The downloadable
software in a Link Tap
Link Tap
Link Tap software has been lost. You
Link Tap configuration editor NA R, P, C
lost must restore the Tap
mask
software and
database.

Required Required
Message Enabled by
Priority* Priority*
Resident I/O points An analog or digital

Low limit alarm DCU editor for AI/GI R, P, C NA input point exceeded
point its low limit value.
A point has been taken
Resident I/O points out of the manual
Manual off
DCU editor for output NA R, P, C mode and placed back
operator or HHC
points into automatic
operation.
A point has been taken
Resident I/O points out of automatic mode
Manual on
DCU editor for output NA R, P, C and is under manual
operator or HHC
points operation from a host
workstation.
This micro control unit
DCU configuration
(UC, MR, ASC, SCU,
Host editor mask for
MCU alm ack NA R, P, C or DPU) alarm was
workstation MCI, MRI, UCI,
acknowledged from a
DPI or I/SITE LAN
host workstation.
UCI, DPI, MRI, MCI, or
I/SITE LAN has lost
communication with
DCU configuration
UCI, DPI, this micro control unit
editor mask for
MCU lost MRI, MCI, or NA R, P, C (UC, MR, ASC, SCU,
MCI, MRI, UCI,
I/SITE LAN or DPU). Usually due
DPI or I/SITE LAN
to communication
failure or power loss at
the MCU.
DCU configuration RAM has been
MCU mem
MR editor for MCI, MRI, NA R, P, C exceeded in
overflow
or I/SITE LAN associated MR.
The MR or ASC has
DCU configuration
been reset due to an
editor mask for
MCU Reset MR/ASC NA R, P, C application timeout, a
MCI, MRI, UCI,
power interruption, or
DPI or I/SITE LAN
a manual reset.

Required Required
Message Enabled by
Priority* Priority*
This MCU (UC, MR,

DCU configuration ASC, SCU, or DPU)
UCI, DPI,
editor mask for has reestablished
MCU restored MRI, MCI, or NA R, P, C
MCI, MRI, UCI, communications with
I/SITE LAN
DPI or I/SITE LAN the UCI, DPI, MRI,
MCI, or I/SITE LAN.
DCU configuration
DPU or editor mask for A DPU/SCU has failed
Memory failure NA NA
SCU1284 MCI, MRI, UCI, checksum.
DPI or I/SITE LAN
The Mode Schedule
Resident I/O points
for this door has
Mode APB reset NA NA performed a reset of
SCU1284 parent point
the anti-passback
(BB = 08 or 09)
flags.
Resident I/O points The Mode Schedule
DPU or editor for door for this door has
Mode lock NA NA
SCU1284 parent point changed its status to
(BB = 08 or 09) locked.
Mode PIN enable NA NA
(BB = 08 or 09) require a PIN for entry.
Mode secure NA NA
(BB = 08 or 09) secured.
Mode unlock NA NA
(BB = 08 or 09) unlocked.

Required Required
Message Enabled by
Priority* Priority*
Indicates a low
memory condition in
the NPR or Xenta
527/527-NPR. Try
NPR Table Mem NPR or Xenta NetPlus Router
N/A N/A reducing the number
Low 527/527-NPR configuration editor
of globalized points or
message routing
masks in order to free
memory in the unit.
Host configuration RWONLN file is 90%
Host editor message/ full. When this file is
Online 90% full NA NA
workstation alarm mask: group full, all incoming data
1, far left position will be lost.
Host configuration The RWONLN file is
Host editor message/ 95% full. When this file
Online 95% full NA NA
workstation alarm mask: group is full, all incoming
1, far left position data will be lost.
The RWONLN file is
Host configuration
full and has not been
Online data lost NA NA archived. All
subsequent incoming
data has been lost.
A point has been
Resident I/O points commanded by a 7750
Override control 7750 DCU editor for DO/DC NA R, P, C Building Manager
points zone or a points ATS
has been overridden.
Power to the indicated
DCU or Tap device (usually a Tap
Power restored DCU or Tap NA R, P, C
configuration editor or controller) has been
restored.
DPU or Door extension used to enter through
Reader entry R, P, C NA
SCU1284 editor an access controlled
door.

Required Required
Message Enabled by
Priority* Priority*
A valid personal
Reader entry - DPU or Door extension
R, P, C NA was used to enter
PIN SCU1284 editor
through an access
controlled door.
DPU or Door extension used to exit through an
Reader exit R, P, C NA
SCU1284 editor access controlled
door.
A valid personal
Reader exit - PIN R, P, C NA was used to exit
SCU1284 editor
through an access
controlled door.
The door was
DPU or Door extension unlocked due to a
Request to exit R, P, C NA
SCU1284 editor pushbutton or motion
detector activation.
This point has
returned to its normal
Resident I/O points
value from a high or
Return to normal DCU editor for AI/GI/DA/ R, P, C NA
low limit alarm or to its
DM points
normal state if it is a
discrete point.
A runtime accumulator
Resident I/O points
Runtime reset DCU NA R, P, C point has been reset to
editor for PI point
zero.
Analog or discrete
sample data has been
Host configuration
lost. Usually due to
Sample data lost NA NA communication failure
or because no file
space is available on
the hard disk.
The date was set on
DCU configuration this device from an
Set date DCU or HHC NA R, P, C
editor HHC or host
workstation.

Required Required
Message Enabled by
Priority* Priority*
The time was set on

DCU configuration this device from an
Set time DCU or HHC NA R, P, C
editor HHC or host
workstation.
This operator has
DCU configuration
Sign off DCU DCU NA R, P, C disconnected from this
editor
controller.
Host configuration This operator at a host
Host editor message/ workstation has
Sign off host NA NA
workstation alarm mask: group disconnected from a
1, far left position Host Tap in I/NET.
This operator has
DCU configuration
Sign on DCU DCU NA R, P, C connected to this
editor
controller.
Host configuration This operator has
Host editor message/ connected from a host
Sign on host NA NA
workstation alarm mask: group workstation to a Host
1, far left position Tap in I/NET.
The site address
Site # Conflict N/A R, P, C is a duplicate of
another site address
already used on the
same distributed link.
A non-resident
individual could not be
DPU or Door extension verified because
SLI not available R, P, C NA
SCU1284 editor communication could
not be established with
the SLI.
Host configuration
An attempted special
Special day lost NA NA day broadcast failed to
reach a remote DCU.
Resident I/O points A discrete points state
State change DCU NA R, P, C
editor for DI point has changed.

Required Required
Message Enabled by
Priority* Priority*
I/NET lost
Site (LAN)
communication with
this controller (usually
Station lost Host Tap, Tap configuration NA R, P, C
due to communication
NPR, Xenta editor
failure or power loss at
527/527-NPR
the controller).
Site (LAN)
Controller has
reestablished
Station restored Host Tap, Tap configuration NA R, P, C
communications with
NPR, Xenta editor
I/NET.
527/527-NPR
Resident I/O points A point state change
Status alarm DCU editor for DA/DM R, P, C NA (defined as an alarm)
points has occurred.
Host configuration
Downloading tenant
Ten. D/L failed NA NA information to a
DPU/SCU has failed.
Test off Resident I/O points A point has been taken
DCU NA R, P, C
operator editor for any point out of test mode.
All points in the
DCU configuration controller have been
Test off HHC HHC NA R, P, C
editor taken out of test mode
by an HHC.
A point has been
placed into test mode.
Test on Resident I/O points
DCU NA R, P, C The point is no longer
operator editor for any point
displaying real-time
data.
All points in the
DCU configuration controller have been
Test on HHC HHC NA R, P, C
editor placed into test mode
by an HHC.
Host configuration Controller time
Host editor message/ synchronization
Time-sync failed NA NA
workstation alarm mask: group attempt failed to reach
1, far left position a remote DCU.

Required Required
Message Enabled by
Priority* Priority*
SevenTrends
consumption,
override, demand, or
Host configuration runtime cell
Host editor message/ information has been
Upload data lost NA NA
workstation alarm mask: group lost. Usually due to
1, far left position communication failure
or because no file
space is available on
the hard disk.
The CCTV system has
CCTV system DVR Server notified I/NET of an
Video Alarm NA NA
DVR server Message mask alarm condition at this
video camera.
The CCTV system has
notified I/NET that an
CCTV system DVR Server
Video Alarm RTN NA NA alarm condition has
DVR server Message mask
ended at this video
camera.
The CCTV system
CCTV system DVR Server DVR server has lost
Video lost NA NA
DVR server Message mask communication with
this video camera.
The CCTV system
CCTV system CCTV Camera video camera has
Video Motion NA NA
DVR server Message mask detected motion at this
video camera.
The CCTV system
video camera has
Video Motion CCTV system CCTV Camera
NA NA stopped detecting
RTN DVR server Message mask
motion at this video
camera.
The CCTV system
DVR server has re-
CCTV system DVR Server
Video Restored NA NA established
DVR server Message mask
communication with
this video camera.

Transactions
Transactions are specific event messages related to access control
functions. These messages are stored in the TRANSACT table in
the database. Transactions may be stored indefinitely using the
Archive utility.
The actual distribution of these messages is determined by
assigning the event as a transaction or as an alarm. The event type
selection (either alarm or transaction) will determine which distri-
bution group, mask, cell number and report priority will be used.
Note: All alarms are also stored as transactions.
The following parameters are available in the door parameters

editor for controlling message distribution:
Group and Mask
The distribution group and mask of a message determine where
that message will be stored/printed.
Note: Only distribution Group 1 messages will cause a Dial Tap to dial out.
See Also: Masking on page 3-1

Cell Number
The desired cell number (01023). You must assign a value other
than zero in order for SevenTrends to store the information. Other-
wise, this field is not used in I/NET Seven and can be any value.
This field provides backward compatibility for systems which
previously used the DocutrendTM data collection system. If desired,
you may use the cell number to provide a grouping function on
reports.
See Also: Chapter 15, SevenTrends

Report Priority
This parameter can be set to one of the following settings:
Routine Used for Direct connect systems.

Priority Used in Dial systems. The messages are stored in the

7806x Tap until a specified percentage of the buffer is filled or
a time delay expires, and then are sent to the host.
Critical Send Dial request immediately without any delays.
Transactions and Alarms
For each transaction type, you can select whether you want a trans-
action event to generate no event notice (ignore the event), a trans-
action, or an alarm. The transaction types are listed in Table 3-5.
Table 3-5. Transaction Event Types
Event Transaction or Alarm Message(s)
Reader entry. A valid key/card was used to enter through an access controlled
door. Message includes the individuals name, tenant, and key/card number.
Reader entry Elev. entry. A valid key/card was used in an access controlled elevator reader.
Message includes the individuals name, tenant, key/card number, and floor
selection.
Reader exit. A valid key/card has been used to exit through an access controlled
Reader exit
door. Message includes the individuals name, tenant, and key/card number.
Deny entry Sched. Entry through an access controlled door was denied because
Denied the individual is not allowed access at the time attempted.
schedule Deny exit Sched. Exit through an access controlled door was denied because
the individual is not allowed access at the time attempted.
Deny entry PIN. Entry through an access controlled door was denied because
an invalid Personal Identification Number (PIN) was entered.
Denied PIN
Deny exit PIN. Exit through an access controlled door was denied because an
invalid PIN was entered.
Deny entry APB. Entry through an access controlled door was denied until the
Denied APB individual exits the same door or another door within the same anti-passback
(APB) zone.
Deny entry Ten. Entry through an access controlled door was denied because
the individuals key/card is not in the system, or the individual is attempting to
enter a door assigned to a different tenant.
Denied - tenant
Deny exit Ten. Exit through an access controlled door was denied because the
individuals key/card is not in the system, or the individual is attempting to exit a
door assigned to a different tenant.

Table 3-5. Transaction Event Types (Continued)
Event Transaction or Alarm Message(s)
Deny entry Iss. Entry through an access controlled door was denied because the
key/card used has an invalid issue level.
Denied - issue
Deny exit Iss. Exit through an access controlled door was denied because the
key/card used has an invalid issue level.
Deny entry Sel. Entry through an access controlled door was denied because a
Denied - door and personnel schedule has not been selected for the individual.
selection Deny exit Sel. Exit through an access controlled door was denied because a door
and personnel schedule has not been selected for the individual.
Duress entry. A duress code has been entered at an entry reader PIN pad.
Duress entry
Duress elev. A duress code has been entered at an elevator PIN pad.
Duress exit A duress code has been entered at an exit reader PIN pad.
The card reader was unable to validate the card entered by the user. This may
Bad card read
indicate a faulty card, a user error, or a problem with the reader.
Door open too long. The door has been opened longer than the __ time set in
DOTL
the door parameters editor.
Forced door An access controlled door has been forced open.
Door return to normal. An access control door has returned to normal from
Door normal
either a Door Open Too Long or Forced Door alarm condition.
Transaction Filter
This function allows you to further refine your filter for display of
transactions. This function is only available if you have selected at
least one transaction in the Event Info section of the Event Filter
(see Event Info on page 3-25).
The fields for defining a transaction filter are shown in Table 3-6.
Print
The print function allows you to print a list of all events that pass
through the current filter. Statistics concerning non-elevator reader
entries, elevator reader entries, reader exits, and reader denies for
the selected readers are included at the bottom of the printout.

Table 3-6. Transaction Filter Field Descriptions
Group Field Description
These fields are alphanumeric fields that allow you to determine

search criteria for data within each field. You may enter up to 16
Last name
characters, including the wildcard characters ? and *. The filter
First name may include all elements or only one.
Name
Selection For example, if you place J* in the last name field, all transactions
will be filtered for individuals with a last name beginning with a J
Group name (James, Johnson, etc.) If you place Johns?n in the last name field,
all transactions will be filtered for individuals with a last name using
a form of Johnson (e.g., Johnson or Johnsen).
The starting and ending tenant numbers for displayed transactions.

Tenant
The default values include all tenants (0255).
The starting and ending key/card numbers for displayed
Key/Card
Range transactions. The default values include all keys/cards (032,000).
Selection
Note: Tenant 0 and Key/Card 0 are used for specific transactions, such as Bad
Card Read. Excluding them from the filter range will eliminate these
transactions.
The starting and ending access control zones for displayed
Zone
transactions. The default values include all zones (031).
Select whether transactions from individuals with a record type of
Permanent
Permanent will be included in the transaction display.
Record Type Select whether transactions from individuals with a record type of
Temporary
Selection Temporary will be included in the transaction display.
Select whether transactions from individuals with a record type of
Disabled
Disabled will be included in the transaction display.
The default is to print the entire contents of the window. You may
use the options in the print dialog window to specify a range of
pages.
To determine which page(s) you wish to print, move the mouse
cursor to the Date/Time field in the active window. Do not click in
the field, but just place the mouse cursor over it. After a slight delay,
a popup window will indicate which page that transaction is on.
Note: The page number feature does not work on alarms that contain a
dispatch message: the popup window shows the dispatch text instead.
To see which page an alarm is on, check the page number for the
event above or below it.

The actual number of pages printed depends on the number and

size of columns displayed in the window. Enough sheets will print
for each page to show all columns. For example, if you have an
active event window that includes all of the possible columns,
printing requires three sheets per page in landscape mode
(default). For each page you select to print, three actual pages will
be printed.
Text Library
This feature allows you to specify a text message to send across a
serial (COM) port when a point goes into alarm. This can be used
to send commands to third-party hardware that can accept ASCII
text instructions, such as CCTV and paging or intercom systems.
The serial port and transmission rate are set in the I/NET Config-
uration active profile. Refer to the section on I/NET Configuration
in TCON298, I/NET Seven Getting Started.
Point Address
Each entry in the text library must have a unique point address;
only one entry is allowed for each point. When the point goes into
alarm, the text command is sent out over the designated COM
port.
Note: The point address cannot be changed when modifying an existing

entry. Use the copy function to copy the information from an existing
entry to a new entry.
Text
The text message can be up to 127 characters long, including alpha-
numeric characters and special escape sequences. Escape sequences
always start with the backslash (\) character to indicate the escape
(Esc) command. The supported escape sequences are shown in
Table 3-7. Escape sequences count as a single character.

Table 3-7. Text Library Escape Sequences
Esc
Character
Sequence
\xxx ASCII character code, up to 3 digits

\a Alert bell
\b Backspace
\f Form feed
\n New line
\r Carriage return
\t Horizontal tab
\v Vertical tab
\ Single quote
\ Double quote
\\ Backslash
\? Literal question mark
Image Verification
Image verification allows the operator to view the picture of the
individual associated with transactions (access control events). The
image verification window is set to always on top. There are two
image verification options:
Automatic: the system can be set to create an image verifica-
tion window for an AMT event window. This window will
automatically display the image associated with the individual
from the most recent transaction, updating at the screen
refresh rate (every two seconds). At every refresh, the window
shows the image associated with the most recent transaction
event.
Note: If more than one transaction occurs during the refresh interval, the
earlier events will not have an image displayed in the automatic
image verification window.
On demand: the operator can open a static image window, to

view the image associated with a particular transaction in an
event window, or a transaction alarm in an alarm window.

The procedure for adding image verification is as follows:

1. Add user images to the individual record in the Individual
Parameters editor (refer to Individual Parameters in
Chapter 9, Access Control).
2. Select the desired fields for image verification windows in the
Image Verification Configuration editor (see Image Verifica-
tion Configuration Editor on page 3-49).
3. (Automatic image verification only) Complete the following:
a. Select the doors for the image verification window in the
Image Verification Door Filter editor (see Image Verifi-
cation Door Filter Editor on page 3-49).
b. Open an event window, or select an existing event
window. The event window must be the active window.
c. Activate automatic image verification for the selected
event window.
4. (On demand image verification only) Open a static image veri-
fication window for an event or transaction alarm.
Image Verification Configuration Editor
Use this editor to select up to seven individual parameters to
display in the image verification windows, along with the image.
After selecting the desired fields, arrange them in the desired order.
If you change the selected parameters while there are image verifi-
cation windows open, any automatic image verification windows
will be updated with the new information.
Static image verification windows for specific transactions will not
be updated if the parameters are changed. To update a static image
verification window, close the window and re-open it for the same
transaction.
Image Verification Door Filter Editor
Use this editor to specify the doors to include in the automatic
image verification window for the active event window. A separate
filter may be set for each event window.

AMT will retain the door filters for an event window, as long as the
window is left open. You may turn off the automatic image verifi-
cation, and even shut down AMT, and the door filter settings will
remain until the event window is closed.
Note: This filter does not affect the events displayed in the event window. It
only affects the events shown in the automatic image verification
window.
CCTV
CCTV features are available only after you have integrated an Inte-
gral digital CCTV system with I/NET Seven. For instructions on
how to integrate and use digital CCTV with I/NET Seven,
including information on how to use CCTV from within AMT,
refer to TCON301, I/NET Seven Database Connectivity and
Reporting.
Archives
The archive function allows you to periodically save AMT events to
a separate database. This allows you to store events indefinitely, and
to have the stored events available for viewing and reporting
purposes. Refer to the help file for information on the report func-
tions available.
Note: Archiving and filtering both use a great deal of system resources.
While archiving, particularly when there are a large number of
online AMT records, it may appear as though your AMT filters are
not operating properly. Filter operation will return to normal when
the archive function is complete.
The archive database will be stored in the location specified as the

Archive directory in I/NETs Configure program. Refer to
TCON298, I/NET Seven Getting Started, for more information on
setting directories.
There are two ways to create an archive: triggered and manual.
A triggered archive is one that is initiated by the system, based
on reaching a certain number of online events (threshold
trigger), or a certain passage of time (scheduled trigger).

Triggered archives may be set to run automatically, or to

require confirmation from the operator.
A manual archive is one that is initiated by the operator,
through the Archive Now button on the Archive Configura-
tion editor.
Note: Each archive file consumes a minimum amount of disk space due to
the identifying parameters that must be saved. Frequent archive
activity resulting in small archive files can therefore consume a large
amount of disk space. To conserve disk space, archive parameters
resulting in fewer, larger archive files are recommended.
File Naming
Each archive is stored in a separate file. The file naming convention
is as follows:
ARC_YYMMDDX.mdf (I/NET Seven 2.12 or earlier)
OR
ARC_YYMMDDX.ARC (I/NET Seven 2.13 or later)
where:
ARC_ = indicates an event archive
YY = last two digits of the year
MM = month
DD = day of month
X = sequential letter used to differentiate multiple archives
created on the same day. The first archive of the day will not
have a letter (for example: ARC_061025.mdf). The second
archive will have the letter A appended (for example:
ARC_061025A.mdf), the third will have the letter B, and so
on.
.mdf (I/NET Seven 2.12 or earlier) = indicates a file in
Microsoft standard database format.
OR
.ARC (I/NET Seven 2.13 or later) = indicates a file in SQL
database format.

Number of Records
Records are archived in batches of 1000. An archive will only run if
the current online (unarchived) records exceeds the minimum
online records by at least 1000. The minimum online records is set
in the Archive Configuration editor (see Archive Configuration
Editor below).
The number of records available for archive is calculated as:
current records minimum online records
This number is rounded up, as it is unlikely the current number of
records is an exact multiple of 1000. Therefore, the actual number
of records in an archive will vary. The more frequently you run
archives (either triggered or manual), the smaller each archive file
will be.
Archive Reminders
If a triggered archive is set to require operator confirmation, the
operator has the choice of postponing the archive. If an archive has
been postponed, a reminder screen will appear when an operator
logs on.
In addition, the Archive Confirmation editor will reappear every 24
hours, or when another trigger point is reached, until an archive is
successfully completed.
Archive Configuration Editor
I/O Server must be running to enter or edit the archive configura-
tion.
Archive Settings
Enable event archiving Indicate whether you wish to archive
events. If this checkbox is not activated, all AMT archiving func-
tions are disabled. When the number of events exceeds the set
maximum (see Maximum Online Events on page 3-53), old
events are discarded as new ones come in on a first-in, first-out
basis. If events are not archived, this will result in loss of data.
Verify archive contents Indicate whether you wish the system
to verify the number of records archived. If this checkbox is acti-
vated, then an Archive complete message indicates that the veri-
fication was successful.

Archive Failure Alarm Set the alarm level for a failed archive
attempt: Routine, Priority, or Critical.
Archive device Enter the path to the storage location for the
archive files. This must be an existing folder on your local drive.
Click the browse button (...) to search for a folder.
Online Event Storage
Minimum Online Events Enter the minimum number of
events that must be saved in online storage, in thousands (13000).
This is the minimum number of events that will remain unar-
chived. This entry should be the smallest number in this section.
The maximum entry of 3000 indicates three million online events.
Archive Threshold Enter the number of unarchived events
required to initiate a threshold archive, in thousands (14,000).
When the system reaches this number of unarchived events, an
automatic archive will be initiated (see Threshold Trigger on
page 3-54). This entry should be higher than the Minimum Online
Events, and smaller than the Override Threshold. The maximum
entry of 4000 indicates four million online events. This field is
unavailable if the Threshold Trigger is set to Disabled.
Override Threshold Enter the number of unarchived events
that will trigger an override archive, in thousands (14900). When
this number is reached, an automatic archive will be generated,
regardless of the settings for the threshold trigger. This is to prevent
data loss in the case where the operator has postponed a confirmed
archive, or an unusual number of events have occurred between
scheduled archives. This entry should be higher than the Archive
Threshold, and less than the Maximum Online Events. The
maximum entry of 4,900 indicates 4.9 million online events.
Note: The only way to prevent an archive at the Override Threshold is to

disable the Enable event archiving checkbox.
Maximum Online Events Enter the maximum number of

events you wish to view online, in thousands (15000). Depending
on the other settings in this section, these will be a combination of
online and archived events. This is the total number of events that
can be viewed through the AMT editor, after which incoming

events will overwrite old ones on a first-in, first-out basis. This

entry should be the highest number in this section. The maximum
entry of 5000 indicates five million online events.
Note: The maximum online events parameter should be changed as little as

possible. See Database Wrap-Around on page 3-56.
Audit Trail
Distribution Group Select the group (14). A distribution
group extends the scope of the eight-position mask, described
below, increasing the available masking positions to 32.
Distribution Mask Enable or disable each of the eight available
positions to create the audit trail distribution mask. Audit trail
messages will then appear at the host workstations with a matching
distribution group and active mask position. Refer to Masking
on page 3-1 for a complete discussion of masking.
Triggers
Threshold Trigger Select the action that will occur when the
unarchived events reach the Archive Threshold: Confirm, Auto-
matic, or Disable.
Confirm will trigger the Archive Confirmation editor when

the threshold is reached. The operator may either approve the
archive, allowing it to start, or postpone the archive. Refer to
Archive Confirmation Editor on page 3-55.
Automatic will trigger an automatic archive. The records will
be archived without any user intervention or notification.
Disabled means that no threshold archives will take place.
When this trigger is disabled, the Archive Threshold field in
the Online Event Storage section is also disabled.
Note: Even if the Threshold Trigger is disabled, an automatic archive will

take place if the number of unarchived records reaches the Override
Threshold.
Scheduled Trigger Select the action that will occur on a speci-

fied schedule: Confirm, Automatic, or Disable.

Confirm will trigger the Archive Confirmation editor when

the specified amount of time has passed. The operator may
either approve the archive, allowing it to start, or postpone
the archive. Refer to Archive Confirmation Editor on page
3-55.
Automatic will trigger an automatic archive. The records will
be archived without any user intervention or notification.
Disabled means that no scheduled archives will take place.
When this trigger is disabled, the fields used to define the
schedule are also disabled.
Note: Even if the Scheduled Trigger is disabled, an automatic archive will

take place if the number of unarchived records reaches the Override
Threshold.
Elapsed Time Select this radio button if you wish to generate an

archive based on strict passage of time. Selecting this button will
de-select the Day of Week radio button. If you select this button,
you must also select the number (131) and the units (days or
weeks).
Day of Week Select this radio button if you wish to generate a
weekly archive on a specific day. Selecting this button will de-select
the Elapsed Time radio button. If you select this button, you must
also select the desired day from the drop-down box.
Time of Day Enter the time you would like the archive to start.
If either of your triggers is set to Confirm, this should be a time
when the station is occupied. Other system activity may cause a
delay, but the archive will start (or the Archive Confirmation editor
appear) within 15 minutes of the selected time.
Archive Confirmation Editor
The Archive Confirmation editor appears when:
an archive is triggered by threshold or schedule, and the
matching trigger is set to Confirm; or
the operator initiates a manual archive.
Thousands of records to archive Sets the number of records
that will be archived, in thousands. The number cannot be set to
more than (current online events minimum online events). The

default number is the maximum records that can be archived. The

operator may reduce this number to archive fewer records, but it
cannot be set to a higher number than the default.
Verify archive contents Indicates whether the system will verify
that the number of records in the archive matches the number of
records that should have been archived. The default for this
matches the setting in the Archive Configuration editor. The oper-
ator may change the setting.
Start button Approves the archive settings and starts the
archive.
Cancel button Closes the window without starting the archive.
This will postpone a triggered archive, or abort a manual archive.
Database Wrap-Around
The maximum size of the AMT portion of the I/NET database is set
using the Maximum Online Events parameter in the AMT Archive
Configuration editor (see Archive Configuration Editor on page
3-52). This parameter should be changed as little as possible,
because of the way the data wrap-around works in the database.
When you first create the database, the default for maximum
online events (1000) sets aside a block for one million records. Any
changes to this value increases or decreases the block accordingly.
Once the designated block is full, new records overwrite old records
on a first-in, first-out (FIFO) basis. To prevent data loss, it is
important to set your archive parameters so that the data is
archived before this occurs.
A potential problem arises when the designated block is full (i.e.,
FIFO has commenced), and then the number of online records is
decreased. Say for example that you change the maximum online
events to 75,000 records. The system then changes its focus to the
most recent 75,000 records, ignoring any older messages.
If you again increase the database size, the system allocates the
appropriate additional space at the end of the current database.
Thus, the latent records are still there, taking up database space, but
are never accessed again by I/NET.

System Messages DCU Error Messages
Each time the maximum online events setting is decreased and

then increased, another dead section of latent records could
potentially be created. Over time, this can greatly increase your
overall database size, affecting system performance.
Archive Window
The archive file contents may be opened from the System menu.
Archives are displayed in an event window. The title bar for an
archive window includes the archive file name.
Window options (see Window Options Editor on page 3-16) and
filtering (Filtering on page 3-23) are available on archive
windows.
DCU Error Messages

In the course of system operation, a DCU error message may
appear in a pop-up window on the I/NET screen. These messages
are generated by the DCU or by a communication problem
between I/NET and the DCU. The error messages and their mean-
ings are shown in Table 3-8.
Table 3-8. DCU Error Messages
Error Message Description
Unknown DCU
This message indicates an internal error contact technical support.
response error
I/NET I/O Server did not reply. Check to make sure I/O Server is running.
You may have to restart I/O Server to clear the error.
No reply from
I/O Server Note: Restarting I/O Server requires you to shut down I/NET and
Configure (if running). If this is an Access Control filemaster
workstation, you must also shutdown the equalization server.
No reply from Host Tap The Host Tap is not responding. Check the Tap connections.
The DCU is not responding to the connection request. Check the DCU
No reply
connections and communication link.
No carrier (Dial connections only.) Telephone connection is not active.
Invalid password The password entered is not valid for the attempted connection.
A command issued from the host has no associated function in the
Invalid subcommand
receiving controller.

DCU Error Messages System Messages
Table 3-8. DCU Error Messages (Continued)
Error Message Description

A command parameter included in the message issued from the host is
Invalid parameter
invalid for the command type used.
Host database differs from DCU database. This may be due to multiple
Entry not found
computers editing the same DCU database at the same time.
One or more bits of the issued command was not received properly. This
LRC error
may be due to line noise or other interference during the transmission.
Less than 256 bytes
DCU memory is nearly exhausted.
remaining in DCU
Memory error DCU memory exhausted.
Note: DCU error messages are not stored in the database.

CHAPTER
4
34
Host Functions
Host Configuration
The Host Configuration editor allows you to define user-interface
parameters for the current workstation. The changes you make
here go into effect as soon as you exit the editor.
Main Window Title

This allows you to customize the title of the I/NET window (shown
in the blue bar, unless you have customized your window settings).
Enter up to 79 characters.
SevenTrends Masks
SevenTrends data is sent only to the workstations whose distribu-
tion group (14) and active mask position(s) match an active mask
position in the originating point. Both the distribution group and
active mask position must match for the data to be received.
Group 14
All message masks are assigned to one of four distribution groups.
The distribution group extends the number of possible masks in a
system to 32. In order for a mask to match, it must find an active
mask position in the assigned distribution group. Each distribution
group may contain up to eight active mask positions.
Note: System messages always use the far left mask position in distribution
group 1. Dial messages always use distribution group 1.

Host Configuration Host Functions
Distribution Mask
Use masks to screen data sent from DCUs to SevenTrends database
tables by accepting only those messages with the same group
number and matching active mask positions. Refer to information
on message routing in Chapter 3, System Messages, and to the point
parameter descriptions in Chapter 6, Input and Output Points.
Monitor
The host configuration editor provides monitor options that allow
you to further customize I/NET. The following monitor options are
available.
Refresh Interval
This option controls the number of seconds between screen
refreshes when a system page or summary is being displayed. The
refresh rate can be adjusted from 1 to 60 seconds.
Note: Page refresh will be suspended during host tasks such as software
downloads, station saves, and station restores.
Auto AMT startup/shutdown

This option specifies whether AMT should automatically start
when I/NET is started, and shut down when I/NET is shutdown.
Activate this checkbox if you with AMT to start and shutdown in
tandem with I/NET. This does not affect your ability to start AMT
independently.
Default System Page
The default system page selection determines which system page is
displayed by default. Any existing system page may be specified.
Refer to System Pages (Graphics Editor) on page 4-17.
Operator Timeout Action
Specify the action that will occur when the operator time-out
interval expires. There a four options as follows:
Signoff Determines that the system will automatically sign
the current operator off when the operator timeout expires.

Host Functions Host Passwords
Default page Displays the default system page when the

operator timeout expires.
Both Enables both the signoff and auto page functions.
None Specifies that no action will occur when the operator
timeout interval expires. Use this option if you do not wish to
use the operator timeout function.
Operator Timeout
This option controls the number of minutes (up to 255) of inac-
tivity (no mouse or keyboard activity) that can elapse before the
Operator Timeout Action is enabled. A setting of zero (0) disables
the operator timeout.
Note: The timeout function only monitors keyboard and mouse activity.
Functions such as a software restore will not halt the timer. If lengthy
automatic operations are to be performed, the operator timeout func-
tion should be disabled to ensure they will be completed.
Windows Logoff
The parameters in this section allow you to prohibit or allow the
closing, resizing, or moving of I/NET windows while no operator
is logged into I/NET. Once a user logs in, their host password
settings will determine what window controls are available.
Size/Move
If this option is deactivated, I/NET windows cannot be resized or
moved until an operator logs into I/NET.
Close
If this option is deactivated, I/NET windows cannot be closed until
an operator logs into I/NET.
Host Passwords
Passwords are used in I/NET to control user access and privileges.
You can assign host passwords to users and DCU passwords to
controllers. Host passwords provide system-level security. When

Host Passwords Host Functions
you assign host passwords to users, you can specify which I/NET
editors, remote host, and tenants a user can access. You can also
preassign controller passwords and controller access levels to host
passwords, enabling users to access certain controllers without the
need to enter a controller password.
Note: Whenever you add a new host to a commercial LAN with existing
I/NET hosts, the system prompts you to update the host passwords
from the filemaster. In this case, the default user of TAC and
default password of DACS may not be functional at the new host.
This prevents someone at the new host from overwriting all previ-
ously defined passwords. To use the new host, you must already be
familiar with the existing passwords.
The host password editor lets you assign individual user passwords
and specify which editors, remote host LAN systems, and access
control tenants the user can access. This editor also lets you preas-
sign controller passwords to users, enabling them to access certain
controllers without the need to enter a controller password. You
may print out a report of a users password authorizations for refer-
ence (see Password Report on page 4-15).
The host password parameters are as follows:
Name Use up to 30 characters to define the operators name.
The following characters cannot be used within the operator
name: " / \ [ ] : ; | = , + * ? < >.
Display Name Use up to 30 characters to define a display
name for the operator. The following characters cannot be
used within the display name: " / \ [ ] : ; | = , + * ? < >.
Password Each operators password can contain up to 127
characters. All keyboard characters are valid.
Confirmation Confirm that the password has been entered
correctly by retyping it in the Confirmation field. I/NET will
not accept your parameter settings if the password confirma-
tion fails.
Initials Use up to four characters to define the operators
initials.
Alternate ID Use this for either of the following purposes:
Create a text string to appear in custom reports

Have this user inherit permissions and/or window

settings from another users account. Refer to Indirect
User Settings in the Passwords chapter of TCON299,
I/NET Seven Operator Guide for more information.
Enable Password Re-use By default, I/NET does not allow
operators to define a password that they have already used in
the past. However, you can enable password re-use if neces-
sary.
Enable Password Expiry You can force operators to periodi-
cally change their password by enabling password expiry.
Expiry Interval (days) If you have enabled password expiry,
you can specify how often the system forces the operator to
change their password. After the specified number of days
have elapsed since the Expiry Start Date, the system will force
the operator to change their password the next time that they
attempt to log onto the system.
Expiry Start Date The Expiry Interval countdown begins
upon the Expiry Start Date. The operator will be prompted to
enter a new password when they log in after the start date plus
the expiry period. The logic for this is:
If current date > (Expiry Start date + Expiry Interval)
then change password.
Once the operator has entered a new password, the start date
will be reset to the current date and the process repeats. If the
operator chooses to change the password before it expires,
then the start date will be reset to the current date.
Card/I-Disc If you define a card/I-Disc number, I/NET can
allow the operator to logon by presenting their Wiegand
card/I-Disc at a Wiegand reader connected to the host work-
stations RS232 port. This feature requires that the AC Reader
Type and AC Reader Port fields must to be setup in the I/NET
configuration editor for the active profile. Refer to Periph-
erals in the I/NET Configuration chapter of TCON298,
I/NET Seven Getting Started.
If password expiry is enabled, a dialog box will appear the first time
the operator signs on after the password has expired. This will
force the operator to enter and confirm a new password.

If the new and confirmation passwords match, the new password

will replace the old one. If the passwords do not match, then the
dialog will display an error message and the operator will need to
re-enter the passwords. This process will continue indefinitely
until the operator enters two matching passwords.
In the event that the operator cancels the forced password change
process, they will be logged out of the system. However, if the oper-
ator voluntarily chooses to change their password while already
logged into I/NET, then they will be allowed to cancel the process
and remain logged on.
Function Selection
Note: When changing a host password's function assignments, the changes
do not take affect until the next time the associated operator logs into
I/NET.
Function selection allows you to assign I/NET functions to a pass-

word. After signing on, only the functions that have been assigned
to the password are accessible to the operator. These functions are
categorized as follows:
Command line functions Functions used to view or
summarize I/NET system status, generate reports, manually
control points or devices, or acknowledge alarms.
Host computer functions System-level editors and functions
available to an operator. When an operator accesses the I/NET
system, only the system-level editors associated with the oper-
ators password appear on the screen.
Tap configuration/status editors Includes host, link, and site
Tap editors.
DCU functions Controller-level editors and functions avail-
able to an operator. When an operator connects to a
controller, only the controller-level editors associated with the
operators password appear on the screen.
Access functions Editors and functions used for access
control. Access functions are divided into Host Access func-
tions and DCU Access functions.

AMT functions Editors and functions used in Alarms,

Messages, and Transactions (AMT).
System tray functions Editors and functions accessed from
the I/NET IOSRV icon in the system tray.
Window control functions Functions used for moving,
closing, and resizing I/NET and AMT windows. Refer to
Setting and Controlling the Layout of I/NET Windows for
more information.
Seven Reports functions Functions used for accessing the
Seven Reports application.
The functions are detailed in Table 4-1.
Table 4-1. Function Select Editor Fields
Function/Editor Action
Command Line
Enable the Host Masks, NP Routers, and Advanced IP buttons in
Advanced WAN Options
the I/NET Configuration Profile editor.
Create new report generation schedules, or modify/delete existing
Auto Report Generation
schedules.
Automatic Control Take a point out of manual operation and place it in automatic mode
Allow display of a CCTV button in the I/NET Configuration Profiles
editor. The Enable CCTV option must also be activated (5) in the
active profile in order for this button to be displayed.
When present, the CCTV button provides access to the editors
CCTV
necessary for viewing and configuring DVR servers and CCTV
cameras.
Refer to TCON301, I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related I/NET features.
Modify CCTV camera parameters in the Camera Parameters editor.
This does not affect the message masking parameters in the Camera
CCTV - Camera Parameters Parameters editor.
Add, modify, copy, or delete DVRs. Refer to TCON301, I/NET Seven
CCTV - DVR Database Connectivity and Reporting, for more information about
CCTV-related I/NET features.

Table 4-1. Function Select Editor Fields (Continued)
Modify CCTV camera message masks in the Camera Parameters
editor.
CCTV - Message Parameters
Change Password Replace users existing host password with a new password
Configuration View controller, Tap, and host configuration summaries
Controller View controller point summaries
Disabled Point View disabled (test or manual mode) point summaries
Door APB Reset Reset antipassback for doors from the door summary display.
Door Lock Manually lock doors from the door summary display
Place doors back to the automatic mode from the door summary
Door Manual Off
display
Allow momentary access through doors from a summary or system
Door Momentary Release
page
Door Secure Manually secure doors from the door summary display
Door Summary View door point summaries
Door Unlock Manually unlock doors from the door summary display
Exit Exit from I/NET
Live Graphic Page View live system graphic pages
Manual Control Take a point out of automatic operation and place it in manual mode
Multi-Point Trend Access the multi-point trend plot editor
Off Normal Point View offnormal (in alarm) point summaries
Page View the graphic page point summaries
Page Acknowledge Alarms Acknowledge all alarms on the current alarm summary screen page
Control a point to a specific state or value. This function allows
Point Control
operator control of the environmental equipment
Test Off Take a point out of test mode
Test On Place a point into test mode
Work Offline Configure controller-level settings without establishing a connection.
Host Computer
Archive Data Archive SevenTrends data
Configuration The host configuration editor
Data Inquiry/Edit View SevenTrends sample data
Definitions Create, modify, or delete SevenTrends definitions.

Graphics Editor The system pages editor
Host ATS The automatic time schedule editor in the host workstation
Host Trend Log The 12-point host trend log function
Network Configuration Edit the network configuration
Setup automatic DCU saves, time synchronization, special day
Network Functions broadcasts, offnormal point and disabled point displays; print
database tables
Passwords The host passwords editor. By default, this function is not selected
Phone Numbers The phone number editor in a Dial host workstation
Software Restore Database and software restore editor for all downloadable devices
Transfer Configuration Setup parameters for transferring SevenTrends records.
Trend Delete Delete a previously defined trend or cell definition from SevenTrends.
Host Tap
Host Tap The host Tap configuration/status editor.
Link Tap
Link Tap The configuration/status editors for link Taps.
Site Tap
The remote dial Tap configuration editor (when connecting through a
Remote Dial Tap Configuration
controller LAN)
Site Tap Configuration The configuration/status editors for LAN Taps.
Site Tap Restore The 7806x Tap phone number restore function.
Site Tap Save The 7806x Tap phone number save function.
DCU
MRI, MCI, or I/SITE LAN editor used to define MR-AHU or MR-VAV
ASC Parameters
operational parameters.
Alarm Inhibit The alarm inhibit (AI) extension editor
Calculation The calculated (CA) point extension editor
Configuration The controller configuration editor
Consumption The consumption (CN) extension editor
Control Descriptions Define up to 8 control description pairs for a DCU
Conversion Coefficients Define mathematical constants used for A/D conversion
DPU Configuration The DPI resident door processing unit configuration editor
Demand Control The demand control (DC) extension editor
Direct Digital Control The DDC editor

Dynamic Data Upload Initiate a data upload from a controller
The access control elevator (EL) editor used to control elevator
Elevators
pushbuttons within the selected DPI, MCI, or I/SITE LAN
Engineering Units Define up to 16 units of measure
Equipment Mapping Define equipment mapping parameters for a 7750 Building Manager.
Event Actions Message/report/conversion editor
Event Definition The event definition (EV) point extension editor
Event Sequences The event sequences editor
I/STAT Parameters I/STAT parameters editor for MRs and ASCs
Input Configuration Edit DPU parameters
I/SITE I/O and I/SITE LAN editor used to define ViewCon page
LCD Page Definition
displays
Lighting Circuit Add, delete, modify, or copy a lighting circuit in a 7780 DLCU
Lookup Tables Define a lookup table for a 7716, 7718, 7756, or 7728
MCU Configuration The MCI or I/SITE LAN resident MR/ASC/DPU configuration editor
MR Configuration The MRI resident MR configuration editor
The MR resident parameters, factory coefficients, and standalone
MR Functions
ATS editors
The editor used to copy operating parameters from one MR to
MR to MR Copy
another.
Override Access Codes Define codes for remotely initiating overrides
Override Parameters The override billing (OB) extension editor
Passwords The controller passwords editor
Resident I/O Point The resident I/O point editor
Runtime The runtime (RT) extension editor
Special Days The special days editor
State Descriptions Define the descriptors used to indicate point and device status
Station Restore Restore controller database from disk
Station Save Save controller database to disk
Temperature Control The temperature control (TC) extension editor
Time Scheduling The time scheduling (TS) extension editor
Trend Plot Initiate a trend plot
Trend Sampling The trend sampling (TR) extension editor
UC Configuration The UC configuration editor

UC to UC Copy The editor used to copy operating parameters from one UC to another
Unitary Control The unitary control (UC) editor
Zone Definition Define a lighting zone
Host Access
Access control editor used to define access initiated control
Access Initiated Control
parameters
Doors Access control editor used to define door operating parameters
Generate PINs Generate a list of personal identification numbers (PINs)
Access control editor used to locally separate individuals into groups
Groups
for easy editing.
Access control editor used to define individual parameters. A
password being used as the second password required to save
Individuals changes to an individual record must also have this function enabled
(refer to Second Password Required for Individuals on page 9-83 for
more information).
Key/Card Translations Access control sub-editor used to translate key/card numbers
Access control editor used to customize individuals editor display
Options
parameters
Personnel Schedules Access control editor used to define individual valid times of entry/exit
Recycle Bin Temporarily store deleted Access Control items in a recycle bin
Recycle Bin Purge Purge deleted Access Control items from the recycle bin
Allow deleted Access Control items to be restored from the recycle
Recycle Bin Restore
bin
Tenants Access control editor used to define groups of individuals
DCU Access
The access control editor used to define access initiated control
sequences for all points within the selected DPI, MCI, or I/SITE LAN.
The access control editor used to define the door operating
Doors
parameters for all doors within the selected DPI, MCI, or I/SITE LAN
The access control editor used to define valid entry/exit times for
Personnel Schedules
individuals
AMT
Acknowledge Acknowledge an alarm
Alarm Window View alarm messages
Archive Window View archived messages

Access the Camera Assignment editor. Refer to TCON301, I/NET
Assign Camera to Point Seven Database Connectivity and Reporting, for more information
about CCTV-related I/NET features.
Auto-Image Verification Enable automatic display of user images for transactions
Configuration Configure AMT operation
Critical Alarm Window View critical alarms
Dispatch Dispatch messages for alarms
Event Window View events
Exit Shutdown AMT
Filters Define filters for AMT event and alarm windows
Home Page Display the home page for a point that is in alarm
Message Window View system messages
Print Print messages in an AMT window
Priority Alarm Window View priority alarms
Purge Purge alarms from the system
Routine Alarm Window View routine alarms
View CCTV video associated with an event. Refer to TCON301,
Show Video I/NET Seven Database Connectivity and Reporting, for more
information about CCTV-related I/NET features.
Transaction Window View transactions
Window Options Choose how information is displayed within AMT windows
System Tray
Define parameters for archiving AMT records using the AMT Archive
Archive Configuration
Configuration editor
Configure Add, modify, or delete I/NET configuration profiles using INETCFG
Exit Shutdown IO Server
Window
Allow AMT Alarm wnd. close Allow the user to close the AMT alarm window
Allow AMT Alarm wnd. move
Allow the user to move and size the AMT alarm window
and size
Allow AMT Event wnd. close Allow the user to close the AMT event window
Allow AMT Event wnd. move
Allow the user to move and size the AMT event window
and size
Allow AMT main wnd. close Allow the user to close the AMT main window

Allow AMT main wnd. move
Allow the user to move and size the AMT main window
and size
Allow I/NET to be closed Allow the user to close the I/NET main window
Allow I/NET to move and size Allow the user to move and size the I/NET main window
Allow all wnd. to be closed Allow the user to close all I/NET windows
Allow all wnd. to move and size Allow the user to move and size all I/NET windows
Allow graphics to be closed Allow the user to close graphic windows
Allow graphics to move and
Allow the user to move and size graphic windows
size
Allow tree wnd. to be closed Allow the user to close tree windows
Allow tree wnd. to move and
Allow the user to move and size tree windows
size
Seven Reports
Seven Reports Allow access to Seven Reports.
Station Selection
You may restrict controller access by assigning each controller a
password. When you combine this with preassigned password
levels, operators do not have to remember the controller password
when connecting to a password-protected controller. This speeds
up connection and simplifies day-to-day operation.
Preassignment of passwords is a three step process. The first step is
to assign the appropriate password level (Level 2/Level 3/Level 4) to
the desired host password in the host passwords DCU selection
editor. Secondly, assign the actual password and associated pass-
word level to each link/controller listed in the DCU passwords
editor. The third step is to assign the same password and associated
password level in the DCU passwords editor of the controller. Refer
to Controller Passwords in Chapter 5, Controller Functions.

Tenant/Group Selection
Tenant selection allows access control system password protection
for each tenant defined in the system. You may select from the
complete list of tenants, the maximum is 255 tenants. Only the
tenants selected will appear in the tenants, group, and individual
editors for an operator using this password.
Besides assigning full tenant access to a user, you can also limit the
users access to specific groups within select tenants. After logging
into I/NET, the limited-access user will be unable to modify any
parameters or access any I/NET features associated with groups
that have not been assigned to the user. Refer to Limited-access
Users on page 4-15 for more information.
Individual Field Selection

Note: The Individual Field Selection feature described below affects only
host passwords that have the Individuals function enabled ([X]).
Refer to Function Selection on page 4-6 for more information.
This option allows you to specify which individual fields will be

visible to the operator. This feature can be used to provide multiple
levels of security in an access control environment by specifying
each field that the operator will be able to view and edit. You must
have at least one individual defined for this option to be available.
Only the fields and buttons selected will be available to an operator
using this password.
If you wish to allow a user to view, but not edit, the fields, de-select
the OK Button parameter. When the user accesses the Individuals
Parameter editor, all displayed fields will be read-only. The user will
not be able to select the OK button to exit the editor, but must use
the Cancel button instead.
DCU Password Preassignment

I/NET allows you to preassign controller passwords to individual
host passwords. This allows users to connect to password-protected
controllers without typing a password. The preassigned password
is sent to the controller automatically. If the preassigned password
is valid for the selected controller, then the user is granted access.

After preassignment, when the operator connects to the controller

level, the preassigned controller password for the operators
assigned level is compared to the controller password assigned to
the same level. If they match, the operator is granted access. The
controller passwords and associated level entered for the individual
host password must match the passwords and associated level
entered in the DCU password editor.
There are four password authorization levels, each relating to the
degree of access permitted the user of the password. Each password
may be up to four characters in length. Refer to Table 5-1,
Controller Access Levels, in Chapter 5 for a description of the
degrees of access granted at each of the four password authoriza-
tion levels.
Caution: Only level 4 lets you add or modify passwords. At least one user must
have a level 4 password. Also, if two passwords are identical but have
different priorities, the higher priority is granted to the user.
Password Report
Any operator with host password privileges may print a report of
other operators password authorizations from the Host Passwords
Summary editor. Select the operator(s) whose authorizations you
wish to include on the report. At least one operator must be
selected to activate the print function.
Limited-access Users
When adding or modifying a user in I/NET's Host Passwords
editor, you can use the tenant selection process to limit the users
access based on specific groups. After logging into I/NET, the
limited-access user will be unable to modify any parameters or
access any I/NET features associated with groups that have not been
assigned to the user.
The restrictions placed on a limited-access user are described
below.

Tenants
When a limited-access user selects Access ` Tenants from
I/NET's main menu, the following restriction will apply:
Cannot Add, Delete, Modify, or Copy any tenants for which
full access is not allowed.
Individuals
When a limited-access user selects Access ` Individuals from
I/NET's main menu, the following restrictions will apply:
Can only see individuals associated with allowed groups
Cannot Add or Delete individuals. The limited-access user
can only Modify existing individuals.
Individual Doors
When a limited-access user is modifying an individual and selects
the Doors button, the following restrictions will apply:
Can only see doors associated with allowed groups
Can assign the individual direct schedules to allowed doors
Individual Groups
When a limited-access user is modifying an individual, selects the
Doors button, and then selects the Groups button, the following
restrictions will apply:
Can only add and delete allowed groups to and from the indi-
vidual, respectively.
Can only change the priority of allowed groups.
Cannot remove an allowed group if doing so would cause the
limited-access user to lose access to the individual.
Groups
When a limited-access user selects Access ` Groups from I/NET's
main menu, the following restrictions will apply:
Can only see individuals associated with allowed groups
Cannot Add or Delete groups. The limited access user can
only Modify allowed groups.

Host Functions System Pages (Graphics Editor)
Group Doors
When a limited-access user is modifying a group and selects the
Doors button, the following restrictions will apply:
Can assign the group direct schedules to allowed doors
Can assign allowed groups to the group
System Pages (Graphics Editor)

I/NET includes a graphics editor that you can use to develop graph-
ical system pages. System pages serve a variety of functions but are
designed primarily to let you graphically depict the location and/or
current state or value of your system components. Each point on a
system page can represent an internal, external, or remotely
connected system component. Use any one point as often as you
require it. Display discrete points in ASCII text, with icons, or with
dynamic graphic symbols. Display analog data in decimal form,
with icons, or as horizontal or vertical bar charts.
File Formats
I/NET Seven saves graphic pages and library symbols in different
formats than previous versions of I/NET. Graphic pages from
earlier versions of I/NET have a .pag file extension and library
symbols have a .bol extension. I/NET Seven pages will have a .gpg
extension and library symbols will have a .gls extension. However,
I/NET Seven has the capability to open and automatically convert
both .pag and .bol graphic files.
References to Files
Graphic pages can include references to other graphic pages (i.e.,
page markers) and external graphic images (i.e., background
images and library symbols). When I/NET encounters a referenced
file, it will first attempt to locate a version of the file that has been
saved in a newer file format. Therefore, if a .pag file is being refer-
enced, I/NET will first attempt to open a .gpg file of the same name.
If a .bol file is being referenced, I/NET will first attempt to open a
.gls file of the same name.

Network Configuration Host Functions
For example: if a page marker links to a file named

c:\pages\mypage.pag, I/NET will first attempt to open a file
named c:\pages\mypage.gpg. If the file is not found, I/NET will
then search alternate paths for mypage.gpg (refer to Alternate
Graphic Paths below). If the result of this search is unsuccessful,
I/NET will open the file named c:\pages\mypage.pag.
Alternate Graphic Paths

I/NET can automatically search alternate paths for missing files or
for files of a newer format (as described above). You can define
unique alternate paths for page references and for graphic symbol
references. When I/NET attempts to locate a referenced file, it uses
the following search sequence:
Path defined by the object (i.e., page marker, discrete point,
library symbol, etc.).
Alternate paths defined for the object type (i.e., page or
symbol).
When defining multiple alternate paths, separate each path with a
semicolon (;). In the following example, the system will search
c:\graphics and d:\pages if a graphic page file cannot be found
at its original location.
Example alternate path definition: c:\graphics;d:\pages
Refer to TCON299, I/NET Seven Operator Guide, for more infor-
mation on the graphics editor.
Network Configuration
You must create a permanent record of the devices you want
included in your system. If links or DCUs exist and are communi-
cating successfully, they automatically appear in the Network
Configuration editor. In this case, all you have to do is save the
configuration.

Host Functions Network Configuration
As you penetrate the system, the first level is link configuration

followed by site configuration, station (DCU) configuration,
UC/DPU/MR/ASC configuration, and door configuration (if
applicable). This follows I/NETs tiered hierarchy of host LAN,
controller LAN, and UC/MR/ASC/DPU subLAN.
Depending on which link you penetrate, you may move to another
link configuration screen, a site configuration screen, or a
controller configuration screen.
Note: Before assigning doors in access control you must first penetrate the
system and save each level configuration. Refer to Chapter 9, Access
Control for more information.
Summary Information
Each summary provides basic information about the devices
defined in the system, and the status of their configuration. The
information displayed in a summary will be determined by the type
of device (i.e., Link, Link/LAN, Dial Link, etc.) being summarized.
The following items may appear in the summary, depending on the
device being summarized:
Note: An asterisk appearing next to an items value indicates a mismatch

between the information in the network configuration and the infor-
mation actually residing in the system.
Link The logical address assigned to the link.

Within the Link Summary, this item is a column that displays
each link defined in the host. If the host is communicating on
an Ethernet LAN, the Link column will include the links on
every other host communicating on the LAN.
Within other summaries, this item shows the link address of
the penetrated link device.
Host This item displays the number of the host through
which the connection is made.
Site The logical address assigned to the site Tap.
Type The type of device through which the connection is
made. I/NET displays the appropriate model number.

Name The name of the link. A visual cue is presented when

there is a mismatch between the name listed in the network
configuration and the name given to the device residing in the
system. Mismatches are almost always caused by the replace-
ment of one type of equipment with another.
Download (Dn) Determines whether or not the device can
be downloaded via the software restore editor.
Telephone Number This is the telephone number that other
devices dial to reach this device. This option is active only for
dial Taps 7804 Host/Link, 7805 Link, and 7806 Dial LAN.
R/H The R/H column displays the number of a host work-
station that will restore this links door controllers when
required due to a download failure during an access control
edit session. An L in this column indicates that the local
host workstation will perform any necessary automatic DPU
restore. A D indicates that the automatic DPU restore
feature is disabled. Refer to Automatic DPU Restore in
Chapter 5, Controller Functions, for more information about
the Restore Host.
Speed (7806 Taps only) The Tap baud rate. The baud rate
can be from 300 to 9600.
Stations This determines the number of stations occupied
by the device. Most controllers occupy a single station;
however, the 7750, 7792, and 7793 may represent two
stations. The 7797 may represent up to eight stations for
specific ICI types.
Cnf This item indicates whether the device is communi-
cating successfully and whether the device has been saved in
the network configuration. The following indications are
possible:
+ The device is successfully communicating but has not
been saved in the network configuration.
The previously saved device is not communicating
successfully.
blank The device is on-line and communicating properly as
defined in the last configuration save.

Host Functions Network Configuration
Link Configuration Summary

The Link Configuration Summary lists each link defined in the
host. If the host is communicating on an Ethernet LAN, this
summary will include the links on every other host communicating
on the LAN.
Table 4-2 lists the types of devices that may appear in the Link
Configuration Summary. This table also describes the purpose of
each device.
Table 4-2. Link Device Types
Type Purpose
7802 Link/LAN Connects a host LAN to the controller LAN

7802 Link Connects a host LAN to LAN Taps in a multiple controller LAN setup.
7805 Link Connects a host LAN to an external modem or directly to a telephone line.
7801 Host/Link/LAN Connects a workstation to the controller LAN.
7801 Host/Link Connects a workstation to host LAN Taps in a multiple controller LAN setup.
7804 Host/Link Connects a workstation to an external AD/AA host Tap.
2000 NetPlus Router Connects a controller LAN to an Ethernet network.
Both the Xenta 527 and the Xenta 527-NPR connect an I/NET controller LAN
Xenta 527 to an Ethernet network. The Xenta 527 also provides web-based access into
the I/NET system (the Xenta 527-NPR does not provide web-based access).
Site Configuration Summary

The Site Configuration Summary is displayed when you penetrate
a 7802 Link, 7804 Dial Host/Link, or 7805 Dial Link Tap. This
summary contains a list of all defined 7803 and 7806 Taps.
You must save the link configuration through which you accessed
the site configuration before I/NET will let you save a site configu-
ration.
Station Configuration Summary

The Station Configuration Summary is available after penetrating
the system through a Link or Site Configuration Summary. The
Station Configuration Summary contains a list of all connected
controllers.

If your controller configuration includes a 7760 Unitary Controller

Interface, 7791 Door Processor Interface, 7792 Micro Regulator
Interface, 7793 Micro Controller Interface, or 7798 I/SITE LAN,
then you may continue to penetrate the system through one of
these controllers. Otherwise, the controller level is the deepest level
of your configuration.
This is the only summary that includes the Stations item. This
item shows the number of stations occupied by the controller. Most
controllers occupy a single station; however, the 7750, 7792, and
7793 may represent two stations. The 7797 may represent up to
eight stations for specific ICI types.
MCU Configuration Summary

I/NET displays the MCU Configuration Summary when you pene-
trate an interface unit in the Station Configuration Summary.
Interface units provide support for micro control units (MCUs)
connected to a subLAN. The MCU Configuration Summary shows
the MCUs defined for an interface unit.
Door Configuration Summary

I/NET displays this summary when you penetrate a Door Processor
Unit (DPU) from the MCU Configuration Summary. This
summary shows the doors defined for the DPU or SCU1284.
You may modify a door to enter a name (up to 64 characters) in the
Door Parameters editor. This editor is used only to assign a name
to a door point. If you do not enter a name in this editor, all
windows and editors that display a door will use the point name
entered in the Resident I/O Points editor.

Host Functions Network Functions
Network Functions
Note: Network Functions are not available on a workstation configured as a

Remote Client in a client/server network. Refer to Client/Server
Infrastructure on page 1-28 for more information.
The I/NET Network Functions editor lets you perform a variety of
special functions. You can synchronize the date/time of your
controllers, select automatic DCU save for all or some of your
controllers, broadcast special day schedules, display off-normal
and disabled points, and print all or some of the information
currently residing in your system database.
The following program functions are available from the Network
Functions editor:
DCU synchronization Off-normal points

Automatic DCU save Disabled points
Special day broadcast Database print
DCU Selection
Select the controllers you wish to receive the network function. The
system displays each of the links configured for your system. This
list includes the link type and link name. The link type consists of
a Tap number followed by one of the following designations:
Host/Link/LAN
Link/LAN
Link
NetPlus Router
When you choose a link, the system lists controllers associated with
the link. If you selected a link type of Host/Link/LAN,
Link/LAN, or NetPlus Router, the system allows you to choose
specific controllers. If you selected a link type of Link, the system
allows you to choose a site. After choosing a site, the system displays
all controllers at that site. At this point you can choose which
controllers will receive the network function.

Network Functions Host Functions
DCU Synchronization
Note: The DCU Synchronization function is intended for use with direct-
connect, TCP/IP, or auto-dial/auto-answer (AD/AA) communica-
tion only. If the communication path from your host workstation to
the controller consists of an Integrated Dial or NPR Dial connection,
do not activate the DCU Synchronization function for that
controller.
The DCU synchronization function allows you to periodically

synchronize the hardware clocks in your controllers with the host
workstation clock. While the hardware clocks are quite accurate,
they do drift slightly over long periods of time. DCU synchroniza-
tion lets you automatically re-establish synchronization at a speci-
fied time, without any further action on your part.
Note: If the time in the controller is ahead or behind the workstation clock
by more than one minute, the controllers clock will be reset to the
workstation time. This will cause any existing trend samples to be
cleared from the controllers memory. If the trend samples must be
retained, ensure that they are directed to a SevenTrends table/cell.
The following four synchronization options are available:

None This option changes controllers to no synchroniza-
tion. This is I/NETs default setting.
Daily Use this option to synchronize controllers on a daily
basis. Synchronization occurs at 3:15 a.m. (03:15) each day.
Weekly This option synchronizes controllers on a weekly
basis. Synchronization occurs each Sunday at 3:15 a.m.
(03:15).
Monthly Use this option to synchronize controllers on the
link on a monthly basis. Synchronization occurs on the first
day of the month at 3:15 a.m. (03:15).
Note: A change in the DCU time will result in the loss of all trend data that
has not yet been uploaded.

Daylight Savings Time

As a part of DCU Synchronization, you can also broadcast daylight
savings time settings to controllers. Using this feature you can avoid
having to manually connect to each controller.
As the host workstation synchronizes the daylight savings time
settings in a controller, it will also check for the existence of a corre-
sponding SAV file. If a SAV file for the controller is found, the host
workstation processes it as follows:
SAV file is current If the controller's SAV file is current, the
host automatically updates it with the daylight savings
settings from this editor. This ensures that if you later restore
the controller using this SAV file, the correct daylight savings
time settings will be downloaded.
SAV file is old If the controller's SAV file is out-of-date, the
host does not change it. In this case, you can manually update
the controller's SAV file or use the Automatic DCU Save func-
tion in order to create an up-to-date SAV file for the
controller. Refer to Station Save and Restore for more infor-
mation.
Note: If no SAV file is found for the controller, the host workstation will not
create one. Only the Automatic DCU Save function can create a SAV
file automatically.
Automatic DCU Save

Note: The Automatic DCU Save function is intended for use with direct-
connect, TCP/IP, or auto-dial/auto-answer (AD/AA) communica-
tion only. If the communication path from your host workstation to
the controller consists of an Integrated Dial or NPR Dial connection,
do not activate the Automatic DCU Save function for that controller.
If you activate this option for a controller, the system performs an

automatic save of controller programming each 24-hour period at
3:15 a.m. (03:15), provided a change has been made to the
programming. The host workstation must pass through midnight
and be allowed to continuously run uninterrupted until 3:15 a.m.
(03:15) for this period.

Special Day Broadcast

Use this option to distribute previously-defined temporary special
day schedules to selected controllers as needed. Special day
start/stop/cycle schedules are defined using the time scheduling
point extension editor and are assigned to a particular date (S1S7)
in the special day editor. These I/NET features are discussed in
detail in Chapter 7, Point Extensions, and Chapter 8, Dynamic
Control.
The special day broadcast function is similar to the controller-level
special day function in that it lets you assign a previously-defined
special day schedule to a particular date. However, the controller-
level special day function would require that you enter the special
schedule separately for each controller you wish to control. By
using the special day broadcast function from the host, you can
quickly direct special schedules to multiple controllers. This option
is extremely useful for snow days in a school district or sale days in
retail outlets where you may need to quickly place hundreds of
controller points under the same special schedule.
Setup (Day Format)
Establish the following parameters for the special day broadcast
function.
Date
This parameter is used to define the starting month and day of the
temporary special day.
Duration
This is the duration of the special day schedule. The duration may
be between 0 and 127 days. A duration of one day causes the system
to execute the changed schedule only on the date defined by the
date parameter.
Schedules S1 Through S7
These are the seven available special day schedules. These must be
pre-defined in the time scheduling point extension editor discussed
in Chapter 7, Point Extensions, and Chapter 8, Dynamic Control. It
is helpful if you have previously set aside one special schedule in
each DCUs ATS schedule for this purpose. If, for example, S2 is

defined identically in all ATS schedules, you can be sure all

controller points are following the same special schedule when a
special day 2 broadcast is executed.
Broadcast Time
You may delay the broadcast of the temporary special day schedules
to take advantage of reduced telephone tariffs or delay the broad-
cast to a time when communications lines are unloaded. Enter the
date and time for the scheduled broadcast. This does not have to be
the same day as the date you want the special day schedule to go
into effect, this is simply the date when the broadcast will occur.
If a communications failure occurs and the system in unable to
broadcast the special day schedule to all selected controllers, it
displays the extent of this failure in the messages table and prints
the error message Special day lost along with the link and station
address (LLSS) of the failed transaction. Always check the messages
after you issue a special day broadcast to make sure the broadcast
was successful. In order to receive this message, the host worksta-
tions far left mask position in distribution group 1 must be acti-
vated.
Broadcast Failure
The system alerts you when it is unable to connect to a controller
that has been selected to receive the special day broadcast. At this
time you can try selecting the controller again or you can choose to
abort the procedure. In order to receive this message, the host
workstations far left mask position in distribution group 1 must be
activated.
Broadcast Review
If you are not sure which special day schedule you selected to be
broadcast, connect to the controller in question and inspect the
special day editor. Refer to Chapter 7, Point Extensions for details
on the special day and time scheduling editors.
Off-normal Points
Off-normal is another term used to describe points that are in an
alarm state. The off-normal points option in the Network Func-
tions editor allows you to choose which controllers will be interro-

gated for off-normal point summaries. The interrogation is

initiated, and off-normal points are displayed, when you select the
off-normal points option from the summary options menu. Refer
to the section on Summaries in TCON299, I/NET Seven Operator
Guide.
Disabled Points
Disabled is another term used to describe points that are in test or
manual mode. Use this option to select controllers containing the
points you want displayed when you select the disabled point
summary option from the summary option menu.
Database Print
Use this option to print a copy of any or all controller database
point or extension entries. This lets you see exactly what points,
point extensions, and DDC modules you have added to the
controllers on your system.
Note: The system lets you select more than one link; however, this may
result in a very lengthy printing session. The selected DCU must be
defined on the system.
The database print function provides the following options:

Setup Use this option to select those parameters you wish to
print for selected controllers.
Print Use this option to proceed to the actual printing. Since
database prints may be lengthy, make sure no manual
commands from the workstation are needed during the time
required for printing. If the workstation is configured with an
operator time-out option, you may wish to turn off this func-
tion. The print process may be interrupted but there may be a
delay while the printer buffer empties.
Note: Even though the system keyboard is unavailable for use while a data-
base print is in process, the workstation is still available to the system
for data collection and message processing. The background opera-

Host Functions Configuration Summaries
tion of the I/NET system software guarantees that any interrupt

generated by a field condition is handled at a higher priority than the
printing task.
Configuration Summaries
Configuration summaries give you a quick glance at the devices
communicating at a particular level in your system. You must be
connected at the level of the summary you wish to display.
Table 4-3 lists and describes the configuration summaries available.
Table 4-3. Configuration Summaries
Summary Description
If your system is configured with an Ethernet LAN, the host summary displays all
operator stations connected to the EtherNet LAN. If your host is on a host or
Host Summary
controller LAN, the host summary displays the Host Taps name and revision
level.
Displays all link Taps available through the connected operator station. If you
Link Summary connect to a remote operator station through the EtherNet LAN, this summary
displays the available links at the remote operator station.
Displays the controllers available through the connected link Tap. The summary
identifies the separate controller LANs on a link with multiple LAN Taps. The
Station Summary station summary lists only LAN Taps and their phone numbers on a dial link Tap.
If you request a station summary after you connect to a controller LAN through
a dial link Tap, this displays all the stations on that controller LAN.
Displays all the unitary controllers connected to the 7760 controller (UCI) to
UC Summary
which you are connected.
Displays all the micro regulator controllers connected to the 7792 (MRI) 7793
MR Summary
(MRI), or 7798 (I/SITE LAN) on the associated controller LAN.
Displays all the DPUs/SCUs/DIUs/DIOs connected to the 7791 (DPI),7793
DPU Summary
(MCI), or 7798 (I/SITE LAN) on the associated LAN.
Table 4-4 lists the information that may be included in the

summary, depending on which summary is selected.

Software Restore Host Functions
Table 4-4. Configuration Summary Fields
Field Summary Type(s) Definition

The system address of the operator station, link Tap,
or controller.
The UC address includes the UCI address. For
Host, Link, Station, UC, example, 2401 indicates UCI 24 and UC 01.
Address
MR, DPU The MR address includes the MRI address. For
example, 2401 indicates MRI 24 and MR 01.
The DPU address includes the DPI address. For
example, 2401 indicates DPI 24 and DPU 01.
Host PC Name Host The name assigned to the operator station.
Host (direct connect),
Tap Name The name assigned to the Tap.
Link
Revision The revision level of the Tap or controller firmware.
Link, Station
Type Link, Station, UC, MR, Type of Tap or controller.
DPU
The site number for the controller. This is a user-
Site Station, UC, MR, DPU
assigned number for multiple LANs (typically AD/AA).
Station Name Station The name assigned to this controller.
The number of stations occupied by the controller.
Most controllers occupy one station. Some controllers
Stations Station (7750, 7791, 7792, 7793) may occupy up to two
stations. The 7797 controller may have up to eight
stations, depending on the ICI controller type.
The current communication status of the controller.
Communicating means the device is
Status UC, MR, DPU communicating properly.
Unknown means the system has lost
communications with the controller.
Software Restore
The software restore function allows you to restore software and
previously-saved controller database information. Controller data-
base information is stored in SAVE files that are automatically
created when you perform a controller save. If a SAVE file does not
exist for a particular controller, then you cant perform a database

Host Functions Software Restore
download; however, you can still perform a software download.

Software for Taps and controllers is stored in binary files added to
your system during the installation or upgrade process.
When you select the software restore option, the system provides a
list of all the Taps and controllers you previously defined as down-
loadable in the network definition portion of the network configu-
ration editor (refer to Summary Information on page 4-19). You
may mark devices to receive downloadable software (binary files)
and downloadable database information (SAVE files). Taps do not
have databases and therefore cannot be selected to receive down-
loadable database information.
When you use the software download option, the system starts the
download from the default data subdirectory defined during instal-
lation. If you do not want to restore from the default directory, you
may enter a different path for an external drive, or a different path
on the hard drive.
For each device marked for download, the system restores any
selected controller/Tap software first, and then the controller data-
base. The download of both types of information is completed
before the system moves on to the next device marked in the list. If
a download was successful, the device marked for download
becomes unmarked. If the device does not become unmarked, then
either:
a SAVE file does not exist (the system could not find a data-
base to download); or
the specified address (LLSS) does not match the address for
the DCU; or
a communication failure has occurred.
Default SAVE files exist in the SAV directory for the 7728, 7780, and
7791 controllers. These save files are downloaded to the appro-
priate controller if no SAVE file exists with the correct link and
station address for the target controller. These files contain the
necessary basics for initial programming.

Host Trend Log Host Functions
Host Trend Log

The host trend log lets you generate your own customized tabular
trend log reports. A trend log can contain up to 12 unique discrete
or analog point addresses.
Note: Do not mix point types in a trend log. Each trend log should contain
all discrete points, or all analog points.
For each address, sampled data is stored and printed. You can
specify how often the points are sampled, how often the trend log
is printed, and during what part of the day the printing takes place.
Note: The host trend log is designed to print sampled data for points. It
assumes that a valid sample has been stored for each point in the
trend log before it is requested to print the report. If, for whatever
reason, a sample has not been stored for a point, the value ????????
is printed. This is normally not a problem except when the print and
sample intervals are set the same and the first trend log is being
printed. A host software change has been made to ensure that valid
sample data appears for points in this first host trend log (at the print
begin time), when the sample interval and the print interval have
been set to the same values.
Table 4-5 lists and describes trend log options.
Table 4-5. Trend Log Options
Option Description
Use this option to change point sample interval, print times, and print start and
Parameter Edit
stop times. Table 4-6 list the parameters for this option.
Use this option to add a point to the host trend log. You may add up to 12 points
to your host trend log. When you add a point to the trend log editor, this
automatically adds a DCU trend sampling extension to the associated point.
You cannot add a point to the trend log editor if the point already contains a
Add Point DCU Trend Sampling extension.
The newly-added DCU trend sampling extension contains the same sample
interval value as the one entered in the host trend log editor. The number-of-
samples value equals the host trend logs print interval divided by the sample
interval plus five.

Host Functions Host ATS (Automatic Time Schedule)
Table 4-5. Trend Log Options
Option Description
Delete Point Use this option to delete a point from the host trend log.
Manual Generation Use this option to display and print a host trend log.
Table 4-6. Editable Trend Log Parameters
Enter a number between 1 and 1,440. The default is 1. This is the number of
Sample Interval (min) minutes between samples. A point can be sampled as often as once each
minute or only once each 24-hour period.
Enter a number between 1 and 1,440. The default is 1,440. This is the
Print Interval (min) number of minutes between host trend log prints. You can print each minute,
once a day, or at any time interval in between.
Enter the time (hh:mm) you wish printing to begin. Time is entered in 24-hour
Print Begin
format where PM hours are entered as the time plus 12 hours.
Enter the time (hh:mm) you wish printing to end. Time is entered in 24-hour
Print End
format where PM hours are entered as the time plus 12.
Note: If points are going to be used in the host trend log, the above parameter entries must be
entered through the host trend log for the point(s), not through the DCU-resident trend
sampling editor.
Host ATS (Automatic Time Schedule)

Time scheduling allows you to define how controller-resident
output points will operate based on the day of the week and the
time of day. Time schedules can be defined at the controller level
using the time scheduling (TS) point extension (refer to Chapter 7,
Point Extensions for more information).
The host ATS function allows you to define schedules at the host
level and distribute this information to controller-resident master
time schedule points. This way you dont need to access each
controller separately. Instead, you can create a master schedule that
is edited from the workstation and affects points with master
schedules (along with their associated slave schedules) in multiple
controllers. You cannot download a host time schedule to an inde-
pendent time schedule.

Phone Numbers Host Functions
Note: When modifying an existing host ATS, pay special attention to the
date and time values. When you modify an existing schedule, the
default values for the date and time fields will be the current date and
time, even if the user previously defined a different date and time.
When you select the host ATS option, the system provides a list of
previously-defined host time schedules. If a schedules download
time has not already occurred, the date on which it will be down-
loaded is also shown. The system allows you to add, delete, modify,
or copy host time schedules.
Phone Numbers
The Phone Numbers editor is available only when the Link Type is
set to Integrated Dial or Integrated NPR Dial in the I/NET
active configuration. Use this option to define the address, name,
and telephone number of up to 64 remote devices per host link.
The system allows you to add, delete, modify, or copy phone
numbers. When you attempt to connect to a remote site, I/NET will
present a list of the remote sites defined on this host.

CHAPTER
5
50
Controller Functions
Controller Passwords
I/NET uses passwords to control operator access and privileges.
Separate passwords are used for host access and controller access.
Host passwords are assigned to operators and DCU passwords may
be assigned to controllers. You can link controller passwords and
access levels to host passwords by using the DCU password preas-
signment function. Password preassignment enables an operator to
access assigned controllers without entering the controller pass-
words.
Controller passwords add an additional level of security for the
indicated controller. Operators must enter a valid password to gain
access to a password-protected controller. This additional security
may not be necessary in systems with only one principal operator.
Each controller may have up to four passwords; one password for
each access level. Access to certain functions and editors depend on
the access level of the password used to connect to the controller.
Refer to Table 5-1 on page 5-2 for a list and description of
controller access levels.
When the DCU password preassignment feature is used an oper-
ators host password is linked with specific controller passwords.
The operator enters one password to sign on to the system and is
not prompted for controller passwords. The operators access to
controller functions depend upon the access level granted in the
DCU password preassignment. If the operator does not have the
correct access level he will not be able to view the controller editors,
even though he is connected to the controller.
If the DCU password preassignment feature is not used, the oper-
ator must enter a separate controller password for each password-

Configuration and Status Controller Functions
protected controller. The level of access is determined by the pass-

word the operator enters.
Note: If you are assigning passwords to a 7728 or 7798 controller, the pass-
words must be numeric only (no alpha characters) and must be 4
digits long. Failure to observe these rules will not allow sign-on from
the controllers remote LCD panel.
Assign controller passwords for each level, as described in

Table 5-1, and then decide which operators should have which
access level. All operators can connect to the controller but their
capabilities are limited by the level of their password. Lastly, deter-
mine whether to preassign specific controller passwords to each
operators host password, or to have each operator enter the indi-
vidual controller passwords as needed.
See Also: Host Passwords in Chapter 4, Host Functions
Table 5-1. Controller Access Levels
Password Level Access

Level 1 Display-only access.
These operators can display controller data, issue commands,
Level 2
and acknowledge alarms.
These operators can display data, issue commands,
Level 3 acknowledge alarms, and edit all functions except the DCU
password function.
This operator can display data, issue commands, acknowledge
Level 4 alarms, and edit all functions including the DCU password
function.
Configuration and Status

The controller configuration/status editor lets you display and edit
various parameters associated with each selected controller. You
must be connected to the controller in order to use this editor.
The screen is divided into sections. Some sections may be edited,
and some are for display only.

Controller Functions Configuration and Status
Control Parameters
This section allows you to set the basic features of the controller.
Name
You may enter any alphanumeric string as the controller Name, up
to 16 characters. The default name for each device is the controller
type (i.e. PCU 7716). If the device is downloadable, the text boot
appears next to the type (i.e. PCU 7716 Boot).
Date
Date shows the current date, according to the controller. This date
matches the date on the workstation if you perform a station
restore. If you wish to change the date, enter it in MM/DD/YY
format (or the date convention defined in your Windows settings).
Time shows the current time according to the controller. The time
is entered in 24-hour format. AM hours are entered as the regular
time. PM hours are entered as the time plus 12 hours. If you leave
the minutes or seconds field blank, the system defaults to zero
minutes, zero seconds.
If you perform a station restore, the time is taken from the work-
station. This is important to remember if your workstation is
located in a different time zone than the controller. If this is the
case, you will always want to use this editor to set the correct time
after a station restore.
Memory Status
These fields are informational only. You cannot make changes.
Total bytes available shows the total memory space available in
the controller for your modifications and additions. Bytes
remaining shows the unused memory space. Not all unused
memory is available for use.
Database Last Changed

Save file shows the date of the most recent station save. Controller
indicates the date of the most recent changes. Changes that have
not been saved are indicated with an asterisk (*).

Loading Details
Note: This field contains information that is usually of interest only to
high-level users. This information can also be obtained using the
hand-held console.
These fields are display only. You cannot make changes. The first
field displays the Controller processor percent loading (0
100%). This number is an indication of how busy the controller is.
If this number is 100, control actions may be lost or delayed. LAN
percent loading shows the percentage of controller LAN commu-
nication attributable to this controller.
Firmware Status
Shown is the Revision number and Date of the firmware installed
in the controller.
Controller Memory
Note: This field contains information that is usually of interest only to
high-level users. This information can also be obtained using the
hand-held console.
Address lets you specify a memory address (up to four characters)

and Contents displays the location value (0000FFFF) within the
controller. You cannot control the value; you can only display it.
Distribution Parameters
This panel sets the message masking and priority for messages sent
from the controller. These parameters only affect controller
messages (such as power failure, sign-on, sign-off, etc.). All point-
related messages are controlled by the masking and priority set for
the point and its assigned extension editor(s), if any.
Masking
Select a Distribution group and activate the desired Message
mask positions. Messages from the controller will be
received/stored/printed only at workstations with a matching

distribution group and at least one matching active mask position.

Refer to Masking in Chapter 3, System Messages for more infor-
mation.
Note: Dial Taps only recognize masks in distribution group 1.
Priority
There are three priority levels: Routine, Priority, and Critical. A
selection of None (-) indicates no priority.
This level applies to messages originating from this controller.
Routine messages are for direct connect systems. A direct connect
host will receive any message with a priority of Routine, Priority,
or Critical. Only Priority and Critical messages are applicable to
Dial Taps.
The message priorities behave as follows when used with an
AD/AA LAN Tap:
Routine Ignore the message.
Priority Report the message when the Dial Taps Percent
Full limit is reached or the Time Interval has transpired.
Critical Report the message immediately. All pending
Priority messages will also be reported.
Reliable Tap
If the controller is loaded with firmware dated 08/21/06 or later,
you can implement reliable messaging by specifying a reliable tap.
The reliable tap can be any tap (or device emulating a tap) that is
being used to route messages from the controller to an I/NET host.
Refer to Reliable Messaging on page 3-7 for more information
about this I/NET feature.
Sunrise/Sunset
These parameters are used to calculate sunrise and sunset. The
required information, longitude, latitude, and time zone informa-
tion, can be found in a variety of public places. Try newspapers,
atlases, almanacs, and libraries.

Provide the Longitude and Latitude information for the facility in

degrees, minutes, and direction.
Enter the Time zone for the facility (124). Time zones begin at
Greenwich, England (Greenwich Mean Time = zone 1) and
increase from east to west. Refer to the time zone world map
located in Appendix B, Time Zone Map. Enter 0 to disable this
function. Enter a decimal number for regions in half-time zones.
I/NET rounds the number to the nearest half.
Daylight Savings
Use this function to enter the beginning and ending dates and
times for Daylight Savings time, using the following parameters:
Month (112): This is the month daylight savings time
begins/ends. January is month 1, February is month 2, and so
on, ending with December as month 12.
Week (15): This is the week daylight savings time
begins/ends.
Enter a 1 if the daylight savings start falls during the first
seven days of the month (17).
Enter a 2 if the daylight savings start falls during the
second seven days of the month (814).
Enter a 3 if the daylight savings start falls during the third
seven days of the month (1521).
Enter a 4 if the daylight savings start falls during the
fourth seven days of the month (2228).
Enter a 5 if the daylight savings start falls after the 28th
day of the month.
Day (17): This is the day daylight savings time begins/ends.
Sunday is day 1, Monday is day 2, and so on, ending with
Saturday as day 7.
At 2:00 a.m. (02:00) on the day specified, the clocks will move
forward (begin date) or backward (end date) one hour.

Program Extensions
Use this section to activate or deactivate specific control extensions
for all points in this controller. The parameters displayed are
dependent upon connected controller and may not always be avail-
able.
Note: Activating these functions does not add the related extension to any
point(s) in the controller. Use the appropriate extension editor to
specify the appropriate extensions to add to each point.
Time Scheduling
Activate or deactivate Time scheduling for points in this
controller.
When activated, all the time scheduling program extensions in this
controller are selected. Once activated, the controller looks back as
far as the previous midnight to determine the point state during the
next minute and issues the proper command.
When time scheduling is deactivated and the controller has time
scheduling programs working, the individual loads remain in the
state that existed when the program was turned off.
Temperature Control
Activate or deactivate Temperature control for points in this
controller.
If this function is not activated for the controller, the individual
temperature control extensions on the attached point(s) will not be
activated.
Demand Control
Activate or deactivate Demand control for points in this controller.
If you deactivate this function, the demand program ceases. All
loads that were currently shed by the demand program are restored
after honoring their minimum off (minimum trip or close) time as
defined for the individual point. Even if turned off, the demand
program will continue to gather KW and KWH data.

Editing the Database while Offline Controller Functions
All Lights On/Off

Activate or deactivate all lights on/off for points in this controller
(available on the 7780 controller only).
This performs the same function as codes 8 and 9 on the HHC.
Activating All Lights On enables input address 0000 to be used to
energize all associated RR7 relays. Activating All Lights Off enables
input point address 0001 to be used to de energize all associated
RR7 relays. This function does not permanently override lighting
circuit control commands. Even after an All Lights On/Off
command has been issued, the lighting zone can still issue controls
to the lighting circuit.
Note: When using All Lights On/Off, input 0000DI and 0001DI should not
be used for any other input point. If you do, lighting control will not
be as expected.
Editing the Database while Offline

I/NET allows you to add controllers, and copy or edit controller
databases when you are not actually connected to the controllers.
This will allow DCU parameters, Host Access Control parameters,
Host parameters and Graphics pages to be created, added and/or
modified without a physical connection.
Note: If you elect to work offline after a connection has been made, your
connection will be terminated automatically and you must reconnect
before you can resume working in online mode.
Connecting Offline
When Connect is selected, and you are working in offline mode,
the Connect Offline dialog will be presented. This will allow you to
select the .SAV file you wish to edit from among a list of those avail-
able. This dialog will display the Link address, station address,
controller type, station name, number of stations, save date and
filename. Additionally, you may Add, Delete, and/or Copy your
files.

Controller Functions Station Save and Restore
Station Save and Restore

This feature lets you save controller database modifications to the
host workstation. Automatic controller save is also available.
Station restore is used to restore a database to the controller from a
previously saved version. This may be necessary if the database has
been corrupted following power outages that out last the controller
batterys ability to retain memory, or for large-scale recurrent
seasonal changes to the controller that may be necessary at your
facility.
Station Save
Once modifications have been made to a controller database, use
this function to save the modifications to the hard disk or a
diskette. You must be connected to the controller whose configura-
tion you wish to save.
Data is saved to the directory specified in the Configure program.
The length of time the system needs to perform the save is deter-
mined by a number of factors. Dial connections increase the save
time; slower baud rate equals slower save time. Other factors
include: LAN speed, number of points on the controller, number of
time schedules, and number of calculations. The save file is named
DCUllss.SAV where ll is the link address and ss is the station address
of the controller associated with the save file.
Station Restore
Use this option to restore a database file to a specified controller.
This is useful if the controller database has been lost, corrupted, or
if you need to install a new controller. The last saved version of the
programming can then be restored to the controller. This avoids
the time-consuming job of reentering the entire program.
The restore procedure uses the directory specified in the Configure
program. The factors that increase the duration of a station save
also increase the duration of a station restore.

Station Save and Restore Controller Functions
Station Restore on a DPI

When you perform a station restore on a DPI, this cold starts the
DPI and then downloads the save file for the controller. This
includes points, access initiated control, and elevator data.
Station Restore on a DPU or SCU1284
When you perform a station restore on a DPU/SCU, this cold starts
the DPU/SCU and then downloads all access control data from the
host, including individual data, tenants, and translation table. All
points and extensions associated with the DPU/SCU including
door extensions, personnel schedules, and elevator extensions are
downloaded from the DPI (not the host).
Automatic DPU Restore

Note: The Automatic DPU Restore parameters in the Link Parameters
editor will be disabled if either of the following conditions are true:
Access control is disabled in the I/NET Configuration editor.
The workstation is configured as a Remote Client in a client/
server network. Refer to Client/Server Infrastructure on page
1-28 for more information.
The Automatic DPU Restore function serves two purposes:
At the appropriate start and end dates, this function activates
and deactivates temporary individuals in the door controller.
Following a communication error, this function automati-
cally updates door controllers with any changes that may have
occurred to the configuration of the access control system.
Using the Link Parameters editor, you can configure the Automatic
DPU Restore feature and select restore hosts for a link. Any door
controllers located beneath the link will be automatically restored
by a restore host when required due to a download failure during
an edit session, or when a door controller comes online with a
Memory Failure message.

Unlike a manually performed DPU Restore, the Automatic DPU

Restore does not typically cold start the door controller. However,
in the event that the door controller comes back online with a
Memory Failure message, the system will cold start the door
controller just as if you had manually initiated the DPU Restore.
The Automatic DPU Restore function divides I/NET host worksta-
tions into the following two categories:
Local Hosts Local hosts are any I/NET host workstations
that are being used to modify access control data.
Restore Hosts Restore hosts are any I/NET host worksta-
tions that are responsible for performing an automatic DPU
restore.
Local hosts and restore hosts are not necessarily separate
computers. If you activate (5) a links Restore from Local Host
option, you allow it to become one of several possible restore hosts
for the link.
Recording Offline Door Controllers
As mentioned earlier, when you make changes to the access control
system, your local host immediately attempts to download these
changes to affected door controllers. If an attempt to update a door
controller fails because of a communications loss, the local host
stores a record of the failed download in an equalized DpuRestore
table. The local host then skips the offline door controller and
continues on to the next device.
When creating a record of a failed download, the local host stores
the following information:
The offline door controller's address (i.e., Link, Station, and
Point).
The host number of the restore host that has responsibility for
updating the door controller.
A time stamp (i.e., the local host's current time in hh:mm:ss
format)
The table that stores this information (i.e., the DpuRestore table) is
equalized among all equalized hosts.

Restore from Local Host

The Restore from Local Host option's setting is not equalized.
Activate this option on each host you want capable of performing
automatic DPU restores for this link.
A host could be required to perform an automatic DPU restore for
the following two reasons:
It was assigned as a Restore Host on this link
A value of 0 was used in a Restore Host field
In either of these cases, the Restore from Local Host option must
be activated in order for the host to perform an automatic DPU
restore.
Be aware that if the local host is currently assigned as a restore host
in any of the four Restore Host fields for this link, the Restore from
Local Host option will be activated automatically. In this case, the
option will also be grey-out to prevent it from being deactivated.
Restore Host Selection
Caution: Before assigning restore hosts to a link, ensure that you have enabled
File Equalization. Otherwise, a restore host could download out-of-
date information to the link's DPUs and SCU1284s.
The restore hosts you define for links are equalized among all hosts.
You can define up to four restore hosts for a link. When assigning
Restore Hosts, choose hosts that are most likely to always be online.
For performance reasons, you may also wish to choose hosts that
are not being used as the file master.
For each of up to four Restore Host fields, enter a host number (1
to 250). I/NET automatically activates and greys out the Restore
from Local Host option on each restore host you assign to this link.
You can leave any field at its default value of 0 to designate any host
as a restore host. When you use a setting of 0, be sure to also activate
(5) the Restore from Local Host option on any hosts that should
have the ability to perform Automatic DPU restores to this link.

Use the following guidelines when choosing restore hosts:

Ensure that message masking on the restore host worksta-
tion(s) allows detection of restore messages. This requires that
the left-most mask in distribution group 1 be selected.
For a link directly connected to your local workstation, set
Restore Host 1 to the host number of the local workstation.
For a link directly connected to a remote workstation, set
Restore Host 1 to the host number of the remote workstation.
See Figure 5-1 for example restore host settings.
Ethernet LAN
Host 1 Host 2 Host 3
TAP
TAP TAP TAP NPR
Link 01 Link 02 Link 03 Link 04

Restore Host 1 = 2 Restore Host 1 = 2 Restore Host 1 = 3 Restore Host 1 = 1
Figure 5-1. Example Restore Host Settings
When the local host creates a record of a failed download, it uses

settings from the Link Parameters Editor to determine which
restore host to include in the record. It is this restore host that will
have responsibility for updating the door controller when it comes
back online.
In order to determine which one of its restore hosts to use, the local
host first checks the current status of Restore Host 1. If it is online,
its host number is stored. Otherwise, the local host checks the

status of next restore host, and so on. The first restore host found
to be online will be given the responsibility of updating the door
controller.
While checking the status of restore hosts, if the local host reaches
a Restore Host field that is set to 0, it will store its own host number
in the failed download record and will stop checking the status of
any other restore hosts. Even if no field is set to 0, the local host will
store its own host number in the record if no restore hosts are
online.
How I/NET Performs the Automatic DPU Restore
To ensure that door controllers receive updated databases, any
I/NET host that detects a restore message of any kind will check the
equalized DpuRestore table to see if it is responsible for performing
an automatic DPU restore. All I/NET hosts also perform this check
every 15 minutes, regardless of whether or not a restore event
occurs.
When a host checks the DpuRestore table, it first looks for any
records that have a non-zero time stamp (i.e., a time stamp that is
not 00:00:00). If a record with a non-zero time stamp is found, the
host then checks for its own host number in the record. If it finds
its own host number, it then checks the status of the Restore from
Local Host option in the Link Parameters Editor. If this option is
activated (5), the host performs an Automatic DPU Restore on the
door controller. The Automatic DPU Restore requires that all 255
Tenants be sent to the door controller to ensure that tenant-related
changes correctly take affect.
When the door controller has been successfully updated, the
restore host changes the time stamp of the record in the DpuRestore
table. This will prevent the restore host from performing an un-
needed Automatic DPU Restore at the next 15-minute interval, or
when another restore message occurs.
The Memory Interface Processor Module

If the controller has a Memory Interface Processor (MIP) card
installed, you must download the controllers software using the
software restore function. Some controller types, including the

Controller Functions Software Restore
7716, 7718, 7780, 7791, 7792, 7793, 7728, and 7797 are built on
downloadable platforms that enable them to receive a downloaded
software file without a MIP.
The MIP plugs into existing CPU sockets in I/NET controllers and
Taps where it enhances product function and expands RAM. The
MIP lets you download software from the host workstation to a Tap
or controller without a technician visiting the job site. This is
supported through direct-connect I/NET LAN communications,
Ethernet commercial LAN communications, or remotely accessed
phone lines.
The MIP module contains a new microprocessor, expanded RAM
memory, on-board battery backup and the necessary hardware and
firmware to support downloadable firmware to the control-
lers/Taps. You can add the MIP card to all Taps and controllers with
the following exceptions:
The speech module in the 7750 Building Manager does not
leave room for a MIP card at this time.
The 78012/13/15 host Taps, the 78022/23/25 link Taps and
78032/33/35 LAN Taps have an onboard communications
module that prevents you from installing a MIP card.
The MIP can only be used with certain 78020 link Taps with
base card part number 330190.
Note: If you install a MIP card, LAN address 63 is no longer valid for the
7803 LAN Tap and the 78061 Dial Tap.
Software Restore
The Software Restore database download capability is similar to the
Station Restore option. Taps, of course, do not require a database,
but do require software to perform their function.
While controller database data is stored in save (.SAV) files, the
software for Taps and controllers is stored in binary (.BIN) files that
are included with the I/NET software.

Dynamic Data Upload Controller Functions
When you select this option, the screen displays all the Taps and
controllers that you previously defined as downloadable in the
Network Definition portion of the Network Configuration editor.
You can individually select or deselect stations, or you can use All
Yes and All No to speed the selection process. Stations that you
select to receive the software restore will display a Y in the Software
or the Database column of the list.
If necessary, define the drive and path to the directory that contains
the software to be restored. By default, I/NET restores software
from the DATA subdirectory defined during I/NET installation.
For each device selected, the system downloads any selected
controller/Tap software first, and then the controller database. The
download of both types of information is completed before the
system moves on to the next device in the list. If a download was
successful, the Y in the Software or Database column changes to
, meaning you have just completed the download and there is
nothing more to download. If you try to download a controller
database and the Y does not change to for that controller, this
means a save file does not exist (the system could not find a data-
base to download) or a communications failure has occurred.
Default save files exist in the SAV directory for the 7728, 7780 and
7791 controllers. These save files are downloaded to the appro-
priate controller if no save file exists with the correct link and
station address for the target controller. These save files contain the
necessary basics for initial programming.
Dynamic Data Upload

This option lets you upload the latest midnight SevenTrends data
for demand, override billing, consumption and runtime statistics
to the appropriate SevenTrends database tables in the host.
This option executes within sixty seconds of starting the upload.
Note: Each time you exercise this option a copy of the midnight data is
placed in the host.

Controller Functions Station Parameters
Station Parameters
Control Descriptions
Control descriptions are English-language displays that define the
controllable states of discrete output points. The descriptions are
used in pairs (i.e., STRT/STOP). You may enter up to eight pairs of
commands.
Each control description is limited to four alphanumeric charac-
ters. The first control description should always be the Start or On
command of the pair, followed by the Stop or Off command on the
next line.
See Also: State Descriptions on page 5-18

Command
Correlates the control description with the desired state of the
output. For example, you can make an On command issue a 1 to
the points database and to the hardware. This energizes the open
collector transistor or relay in the controller. If you have the On
command issue a 0, this deenergizes the hardware. This also deter-
mines the fail-safe state for the point.
For example, if you control lights in an interior space you might
want to have the lights On in the event of a system failure. In this
case you have the On command issue a 0 and the Off command
issue a 1, and wire the light to a normally closed (NC) contact.
Note: The DO point used for a lighting circuit must have a 0 command
as its first control descriptor. The DO point used for a lighting zone
must have a 1 command as its first control descriptor.
Delay
Specify a time delay (0127 seconds) between sequential
commands which use the same control command pair. This feature
prevents multiple loads from starting simultaneously when power
is restored to the controller, or when simultaneous commands are
received from an automatic program such as time scheduling. This

Station Parameters Controller Functions
prevents massive overload of motor control centers. An example

might be morning start-up at a business or school: if everything
came on at once the electrical system could overload.
A delay of one to three seconds is normally adequate for preventing
problems. However, if you have very large loads at your facility you
may wish to extend the delay. The maximum delay is 127 seconds.
For multiple commands, the delay is honored after the first
command is issued.
Note: You should not use control command delays on VAV-UC, AHU-UC,
or HPMP-UC parent points, or on the UC pushbutton override indi-
cator point.
Control Descriptions for Doors

You must define the following parameters for DPU-resident door
points (LLSSPP08 or LLSSPP09).
Table 5-2. Door Control Descriptions
Description Command Delay

SECR (secure) 0 0
UNLK (unlock) 0 0
LOCK 0 0
State Descriptions
All discrete points should have state descriptions assigned to them.
Analog point types display/control values, not states, so this
parameter does not apply to them. State descriptions are associated
with various discrete input and output points to describe the
current state of the device being controlled or monitored.
A descriptor pair typically describes the two states of the device: On
or Off, Open or Closed, Alarm or Normal, and so on. The first
descriptor of the pair should describe the trip or the deenergized
(0) condition of a discrete output point or the open (0) condition
of a status point. The second descriptor of the pair should describe
the closed or energized (1) condition of a discrete output point
or the closed (1) condition of a status point.

Enter up to 16 pairs of descriptors to describe a discrete point state

(On and Off, Open and Clos, Alrm and Nrml, and so on). Each
description can be up to four characters long.
Some devices require multiple state descriptions. Refer to Number
of Bits in Chapter 6, Input and Output Points.
See Also: Control Descriptions on page 5-17
Conversion Coefficients Tables

Conversion coefficients are the mathematical constants the
controller uses to convert analog inputs from the digital value
(counts) used by the microprocessor to analog display values. They
are also used to convert digital commands from the microprocessor
into analog outputs which are then used by field interface devices.
You may enter up to 16 sets of conversion coefficients in each
controller.
The linear equation y = m(x) + b can be used for all conversion
types: analog to digital (A/D), digital to analog (D/A), and pulse
width modulation (PWM). The flow conversion equation
y = m x + b may be used for A/D and D/A only, depending on
the type of transducer being used. The variables are defined in
Table 5-3 below:
Table 5-3. Conversion Equation Variables
Variable Definition
The output of the conversion equation expressed in
y
engineering units (i.e., degrees, lbs, percent, etc.).
Conversion coefficient that represents the engineering unit
m
weight of each count (bit).
x The counts (A/D and D/A) or time units (PWM).
The engineering unit value that is equivalent to 0 (zero) A/D
b
or D/A converter counts.
Pop-up Calculator
To help you calculate conversion coefficients, you have the option
of using a pop-up calculator. The following parameters are used
with the pop-up calculator:

Equipment counts low A number between 0 and 65,535.

This number is typically zero.
Equipment counts high A number between 0 and 65,535.
For a 16-bit A/D converter, enter 65,535. For a 12-bit A/D
converter, enter 4095. For an 8-bit converter, enter 255.
Note: Different controllers use different converters, with different count and
voltage ranges. Please refer to the appropriate installation guide(s)
for specific information concerning the controller(s) installed in your
facility.
Engineering units low The units being measured (degrees,

etc.) for the sensor when the device is at its low count value.
For example, a Lini-Temp sensor which operates between
40 and 230F with voltage readings between 2.33 and 3.83
volts respectively, reads 459.4F at zero volts (0 counts) and
440.6F at 5 volts (4095 counts). This example assumes AI
input is 05 VDC.
Engineering units high The units being measured for the
sensor when the device is at its high count value.
Once you enter the four numbers described above and choose Flow
or Linear as the equation type, the pop-up calculator can automat-
ically calculate the slope and intercept values. You can then choose
to have the calculated values added to your list of conversion coef-
ficients. The m and b values automatically appear on the line. If the
line already contains m and b values, they are replaced by the new
values.
Calculating Coefficients
Coefficients are used to convert one type of data into another type.
I/NET supports three specific conversion types: analog to digital
(A/D), digital to analog (D/A), and digital to pulse width modula-
tion (PWM).
Note: Different controllers use different converters, with different count and
voltage ranges. Please refer to the appropriate installation guide(s)
for specific information concerning the controller(s) installed in your
facility.

Analog to Digital Conversion

The analog to digital (A/D) converter is an 8-, 12-, or 16 bit device
that converts electrical input (for example, 420 mA) into counts
corresponding to the engineering units displayed. The count
ranges for the different converters are as follows:
Table 5-4. A/D Converter Count Ranges
Converter Type Count Range

8-bit 0 255
12-bit 0 4,095
16-bit 0 65,535
For example, if the transmitter you are using is measuring relative

humidity from 8 to 100 percent and its signal into a 7700 (8-bit)
controller is 420 mA, use the linear equation. This converts the
analog signal to digital format by dividing the full range of the rela-
tive humidity measurement (92 percent, 100 8 = 92) by the
number of bits available in the A/D converter (4,095). The equation
is solved as follows:
Table 5-5. Example Analog to Digital Conversion

y = m (x) + b The basic linear equation.
Substitute 100 for y (top end of scale is 100% relative
100 = m (x) + b
humidity).
100 = m (4095) + b Substitute 4,095 for x (number of counts).
Substitute 8 for b (low current of 4 mA is equivalent to
100 = m (4095) + 8
8% relative humidity).
92 = m (4095) Subtract 8 from each side.
m = 92 / 4095 Divide each side by 4,095.
m = 0.022466 m is equal to 92 divided by 4,095.
The entries you put in the conversion table are:

m = 0.022466 b=8

For the CSI Lini-Temp sensor, when connected to a DCU with a 12-
bit A/D converter (such as the 7716), the conversion coefficients
are:
Degrees Fahrenheit: m = 0.17592 b = 279.4
Degrees Celsius: m = 0.09762 b = 173.0
Digital to Analog Conversion
Calculation of the digital to analog (D/A) conversion coefficients is
similar to A/D conversion. The D/A conversion uses either an 8-bit
or 12-bit converter. The range for x is either 0 255 counts (8-bit
converter) or 0 4,095 counts (12-bit converter).
For example, if we wish to calculate the conversion coefficients for
a 420 mA (0 255 counts) output from a 7700 (8-bit) controller
to a 3 15 PSI I/P transducer and would like the AO to read 3 15
PSI, we solve the equation this way:
Table 5-6. Example Digital to Analog Conversion

15 = m (x) + b Substitute 15 for y.
15 = m (x) + 3 Substitute 3 for b.
15 = m (255) + 3 Substitute 255 for x.
12 = m (255) Subtract 3 from both sides of the equation.
m = 12 / 255 Divide both sides of the equation by 255.
m = 0.047059 m is equal to 12 divided by 255.

m = 0.04705 b=3
Digital to Pulse Width Conversion
I/NET lets you direct an analog output software value to a discrete
output hardware point in a time-based manner known as pulse
width modulation. This is accomplished by the fact that the dura-
tion of the pulse (the width) is proportional to the value of the
corresponding analog value.

Use the linear equation as in the previous examples. This time,

however, x is the desired range of time. The full range is 0 to 65,535
time units, with each time unit equal to 10 milliseconds (0 655.35
seconds).
For example, we wish to use a Pulse Width Modulated (PWM)
output point to control a PSI transducer with an input range
between 0.2 and 25.3 seconds (x), and an output range between 3
and 18 PSI.
Although the equation is the same as the one described above, it is
solved in a slightly different way. We do this because we are gener-
ally dealing with a PID module with an output range of 0 to 100
percent. This requires two calculations: one to determine m, and a
second to determine b.
To determine m, substitute the high limits for x and y into the
linear equation. Substitute 0 for b, and solve for m. Once m has
been calculated, substitute the low limits for x and y into the linear
equation. Substitute the calculated value for m, and solve for b.
Table 5-7. Example Digital to Pulse Width Conversion

100 = m (x) + b Substitute 100 for y.
100 = m (x) + 0 Substitute 0 for b
100 = m (2530) + 0 Substitute 2530 time units (25.3 seconds) for x (move
decimal two places to the right to change 25.3 to 2530).
100 = m (2530) Subtract 0 from each side of the equation.
m = 100 / 2530 Divide both sides of the equation by 2530.
m = 0.039526 m is equal to 100 divided by 2530.
y = 0.039526 (x) + b Substitute 0.039526 for m.
0 = 0.039526 (x) + b Substitute 0 for y.
0 = 0.039526 (20) + b Substitute 20 time units (0.2 seconds) for x (move decimal
over two places to the right to change 0.2 to 20).
0 = 0.79052 + b Multiply 0.039526 and 20.
b = 0.79052 Subtract 0.79052 from each side of the equation.

m = 0.039526 b = 0.79052

Note: The output range of the transducer does not enter into the equation
in any way, and x is expressed in time units rather than counts.
Engineering Units Table

This feature lets you define the units of measure for analog
input/output points and accumulator points. These descriptions
only appear in point-related alarms or messages stored in the
system message queue or printed on the system printer.
You may enter up to 16 different units descriptions, each consisting
of up to four characters. This might be gallons (GAL), kilowatts
(KW), kilowatt-hours (KWH), and so on.
Lookup Tables
The 7716, 7718, 7728, and 7756 controllers let you define up to 32
lookup tables, each consisting of up to 31 entries. These lookup
tables may be used for several purposes. You may use the lookup
tables to create engineering units, or to create sensor limits that
focus on a specific span of interest. The primary use of user-defined
lookup tables is to provide simple translation and monitoring of
non-linear signal sources.
Sensors that produce non-linear voltage, current, or resistance
signals are usually accompanied by a graph or table defining the
sensors output characteristics relative to the engineering unit
being monitored. The lookup table allows you to define the desired
span and resolution of translation that is appropriate for the task.
Lookup Table Calculation
A worksheet for calculating A/D counts and adjusted counts is
available in TCON157, I/NET Forms and Worksheets. Fill in the
worksheet using the following steps.
Note: It is usually not necessary to use the entire span of the sensor. Select
the lowest and highest engineering units of interest. Populate this
span mostly with samples from the area of your interest, focusing the
tables accuracy in this area.

1. Enter the voltage, current, or ohms information from the

sensor manufacturers information into column B of the chart
for the span that you desire to monitor.
2. Enter the Engineering Units (degrees, flow per minute, etc.)
into column C that correspond to the voltage/current/ohms
listed on the same row.
3. The Calculated A/D Count column translates the measure-
ment units (V/mA/Ohms) to a positive integer count as
generated by the A/D convertor on the 7716, 7718, 7728, and
7756 controller. Calculate these counts as follows.
Voltage inputs:
12-bit resolution:
A/D Count = (volts/5) 4095 05 V input span
(volts/10) 4095 010 V input span
16-bit resolution:
A/D Count = (volts/5) 65535 05 V input span
(volts/10) 65535 010 V input span
Obtained from column B of Table 5-8, Sample 16-bit Lookup
Table Calculation Chart
Current inputs:
12-bit resolution:
A/D Count = (mA/20) 4095 020 mA input span
(mA/40) 4095 040 mA input span
16-bit resolution:
A/D Count = (mA/20) 65535 020 mA input span
(mA/40) 65535 040 mA input span
Note: The mA formulas assume a 249-ohm resistor configuration in the

7716, 7718, 7728 or 7756. Refer to the appropriate installation guide
for details.
Ohms inputs:

12-bit resolution:
A/D Count = [Ohms/(Ohms+10,000)] 4095
16-bit resolution:
A/D Count = [Ohms/(Ohms+10,000)] 65535
Note: The ohm formula assumes a 10K voltage divider circuit is in place
(refer to the appropriate installation guide for details). Accuracy of
ohms conversion is dependent upon accuracy of 5 V excitation. Use of
the on-board 5 V supply for excitation typically yields 2% accuracy,
5% maximum. Use external precision references and resistors to
excite resistance sensors when better accuracy is required.
1. An arbitrary Bias value is used to raise or lower the engi-

neering unit in column C to be above zero and as close to zero
as possible. A bias result in the range of 020 is desired for the
lowest Engineering Unit entry (table entry line 1). The Engi-
neering Unit is added to the Bias value for all entries and the
result is placed in column F.
Note: The Lookup Table entry cannot be negative. If the Engineering Unit
was 32C, a bias of 40 would raise the value to a positive integer.
2. An arbitrary Multiplier is applied to all Bias Results. The

highest Bias Result (table entry line 11) should be raised to a
value less than or equal to 65,535 for all 16-bit resolution, and
4095 for all 12-bit resolution.
a. For example, calculating for 16-bit resolution a Bias
Result of 120 could be used with a multiplier of 540 (120
540 = 64,800) but not 550 (120 550 = 66,000, which
exceeds 65,535).
b. Calculating for 12-bit resolution a Bias Result of 120
could be used with a multiplier of 30 (120 30 = 3600)
but not 40 (120 40 = 4800, which exceeds 4095).
Place the result of multiplying the Bias Result by the Multi-
plier in the Adjusted Count column.

3. Enter the Adjusted Counts (column H) value into the lookup

table editor in the Adjusted Counts column and the associated
calculated A/D Count (column D) value is entered in the
Counts column.
Note: The maximum value that may be placed in the Adjusted Count
column of the lookup table is 65,535 for 16-bit resolution DCUs, and
4095 for 12-bit resolution DCUs. The lookup table editor allows
entry of up to 65,535 counts for all devices; therefore, make sure that
no more than 4095 counts are entered for 12-bit resolution devices.
To convert the adjusted counts to engineering units use the engi-
neering unit conversion formula y = m(x) + b, with m = 1/Multiplier
and b = Bias.
Table 5-8 on page 5-27 shows a finished lookup table calculation

chart. It is based upon a 5 V sensor connected to a 7756 DCU (16-
bit A/D converter), and does not use the full span of the sensor as
defined by the manufacturer. This example focuses resolution
upon a span of interest of 1258C, and increases the resolution
over that span.
Table 5-8. Sample 16-bit Lookup Table Calculation Chart
A B C D E F G H
Sensor
Manufacturer
Table
Information Calculated Bias Adjusted
Entry Bias Multiplier
A/D Count Result Counts
Number
V / mA / Eng.
Ohms Units
1 1 32 819 40 8 540 4320
2 2.2 20 1802 40 20 540 10800
3 2.8 10 2293 40 30 540 16200
4 3.4 2 2785 40 42 540 21600
5 3.8 12 3112 40 52 540 28080
6 4 18 3276 40 58 540 31320
7 4.2 25 3440 40 65 540 35100
8 4.4 33 3604 40 73 540 39420
9 4.6 44 3757 40 84 540 45360

Table 5-8. Sample 16-bit Lookup Table Calculation Chart (Continued)
A B C D E F G H
Sensor
Manufacturer
Table
Information Calculated Bias Adjusted
Entry Bias Multiplier
A/D Count Result Counts
Number
V / mA / Eng.
Ohms Units
10 4.8 58 3931 40 98 540 52920

11 5 80 4095 40 120 540 64800
12
7728 Lookup Tables

The 7728 does not have a set of lookup tables included in its
EPROM, as do the UCs, MRs, and ASCs. In order to use the CSI
I/STAT or a 10K ohm thermistor, you must use one of the lookup
tables provided in the DEF7728.SAV file. The 7728 I/SITE I/O does
not support hardware inputs in the 03xx range. The lookup tables
for the four AI external points defined with those tables are
contained in the default database.
Table 5-9 shows the four lookup tables provided in the
DEF7728.SAV file. When these lookup tables are used, the
following conversion coefficients (m and b) must also be used:
F: m = 0.1 b = 300
C: m = 0.05 b = 150
Table 5-9. 7728 I/STAT and Thermistor Lookup Tables
F Thermistor F I/STAT C Thermistor C I/STAT
Adjusted Adjusted Adjusted Adjusted

Counts Counts Counts Counts
153 521 153 520 153 601 153 600

344 1062 344 1060 344 1202 344 1200
816 1604 816 1600 816 1804 816 1800
1245 1875 1245 1870 1245 2105 1245 2100
1827 2146 1827 2140 1827 2406 1827 2400
1914 2182 1914 2176 1914 2446 1914 2440

Table 5-9. 7728 I/STAT and Thermistor Lookup Tables
F Thermistor F I/STAT C Thermistor C I/STAT
Adjusted Adjusted Adjusted Adjusted

2003 2218 2003 2212 2003 2486 2003 2480

2048 2236 2048 2230 2048 2506 2048 2500
2093 2254 2093 2248 2093 2526 2093 2520
2183 2290 2183 2284 2183 2566 2183 2560
2274 2326 2274 2320 2274 2606 2274 2600
2366 2361 2366 2356 2366 2646 2366 2640
2457 2397 2457 2392 2457 2686 2457 2680
2548 2433 2548 2428 2548 2726 2548 2720
2637 2469 2637 2464 2637 2766 2637 2760
2725 2505 2725 2500 2725 2806 2725 2800
2812 2541 2812 2536 2812 2845 2812 2840
2897 2577 2897 2572 2897 2885 2897 2880
3209 2756 3209 2752 3209 3084 3209 3080
3577 2934 3577 2932 3577 3283 3577 3280
3923 3293 3923 3292 3923 3681 3923 3680
7756 Thermistor Lookup Table

Use Table 5-10 to establish a lookup table for 10K Thermistors
connected to the lower I/O board of a 7756. When these lookup
tables are used, the following conversion coefficients (m and b)
must also be used:
F: m = 0.018 b = 148
C: m = 0.01 b = 100
Table 5-10. 7756 PCU (Lower I/O Board) and 10K Thermistor
Lookup Tables
Count Adjusted Count F C

128 32846 443.22 288.46
2048 20039 212.70 100.39
4096 17584 168.52 75.84

LCD Pages Controller Functions
Table 5-10. 7756 PCU (Lower I/O Board) and 10K Thermistor
Lookup Tables (Continued)
Count Adjusted Count F C

6144 16185 143.34 61.85
8192 15180 125.24 51.80
10240 14373 110.72 43.73
11264 14016 104.29 40.16
12288 13681 98.26 36.81
13312 13363 92.53 33.63
14336 13058 87.04 30.58
15360 12762 81.72 27.62
16384 12474 76.54 24.74
17408 12191 71.44 21.91
18432 11910 66.38 19.10
19456 11629 61.33 16.29
20480 11346 56.23 13.46
21504 11058 51.04 10.58
22528 10762 45.72 7.62
23552 10455 40.19 4.55
24576 10132 34.37 1.32
26624 9412 21.42 5.88
28672 8514 5.26 14.86
30720 7161 19.10 28.39
32640 2438 104.11 75.62
LCD Pages
The 7728 I/SITE I/O and the 7798 I/SITE LAN allow you to view
named pages for review and control from the I/SITEs operator
interface. Both the 7728 and 7798 support up to 64 pages, with each
page containing up to 640 points. The points on each page may be
from the local 7728/7798, or another DCU on the same controller
LAN. In either case, all points on the same LCD page must reside in
the same DCU.

Controller Functions Points and Point Extensions
Points and Point Extensions

A controller database consists of multiple points. These points
provide input information (temperature is 75 degrees, door is
closed) to the controller which then makes decisions (turns fan on,
turn light off) and provides information or commands to output
points. Each controller may contain up to 640 points: 320 input
points and 320 output points. Points residing in other controllers
may share information with, or may be controlled by, other
controllers through the use of indirect points. If a resident point is
defined as a global point, it can control an indirect point in another
controller and the controllers can share that points data. Refer to
Chapter 6, Input and Output Points for more information about
points.
Point extensions are used to assign pre-defined functions to speci-
fied points. The extensions available to each point depend on the
point type and the type of controller where the point resides. Refer
to Chapter 7, Point Extensions for more information.
Test and Manual Point Control

I/NET provides two methods for you to manually control points.
Both the Test mode and the Manual mode allow you to set the state
or value of a point. Each of these two modes are described below.
Test Mode
Caution: Hardware connected to an output point stops being controlled when
the point is placed in Test mode. The actual output from that point is
frozen at the state/value that exists when the point is placed in Test
mode.
The Test mode isolates an input or output point from the outside
world. This allows you to manipulate the controller database for
that point, or verify normal controller operation, without
using/affecting the external input or output hardware.

Special Days Controller Functions
If an output point in Test mode is not also placed in Manual mode,

the controller continues to control the database for that point. In
this case, operator-entered states/values can be overridden by the
controller. You can stop the controller from overriding your
states/values by also placing the point in Manual mode. Because the
point is in the Test mode, operator-entered point states/values do
not affect the connected external hardware.
Manual Mode
The Manual mode allows you to freeze an output point at its
current state or value and then, if desired, manually control the
point. This mode is limited to output points only. Manual mode
differs from Test mode in that hardware connected to the external
output point will continue to be controlled unless the point is also
in Test mode (refer to Test Mode description, above).
Manual mode overrides all other methods of point control
including automatic time scheduling (ATS), temperature control
(TC), lighting control (LC), etc.
Special Days
The special days editor is used with the time scheduling point
extension. You may define up to seven different special days in the
time scheduling editor. You then use the special days editor to
assign these special days to specific calendar days in the controller.
Entries made in this editor do not require additional bytes of
memory.
If you have a special day defined in a DCU, there must be a special
day schedule (S1S7) defined for all the time schedule-controlled
points in the DCU. If a time schedule does not have a special day
schedule defined, the point will remain at its last commanded state
until the special day period is over.
Special days are ideal for holidays which are known well in advance,
and do not change from year to year. This lets you alter the opera-
tion times of all the equipment controlled by this controller and
schedule these changes up to one year in advance. For instance, if
your facility is not used on Christmas Day you could create a

Controller Functions Special Days
special day which keeps your lights off and your heating at a lower
level than you want when the facility is occupied. You would do this
by using the time scheduling editor to create a special day schedule
for each point that controls the equipment involved in heating and
lighting your facility. Then you would use the special days editor to
assign this as a permanent special schedule on December 25th
(12/25). Every Christmas, this special schedule will go into effect.
Temporary special day schedules can be used for one-time occa-
sions that require a different schedule, or holidays that change dates
from year to year (such as Hanukkah). Once the selected date is
past, the temporary schedule is erased from that date. For example,
if your facility will be closed on Hanukkah, you could use the same
special day schedule that you created in the example above. When
you assign it to Hanukkah (for example, 12/18), assign it as a
temporary special schedule. This schedule will be in effect on
Hanukkah, and then the special day schedule marker will be erased,
so that December 18 of the next year will use the normal schedule.
Note: Temporary special day schedules must be reassigned every year for
holidays that do not always occur on the same date.
You may want to reserve a special day slot, such as S7, for special
day broadcasts (see Special Day Broadcast in Chapter 4, Host
Functions) initiating from the host workstation. In this way you can
be sure a special day broadcast activates the same schedule in each
controller receiving the broadcast.
Note: When the date assigned to the special day occurs, the special day
schedule (S1 S7) replaces all normal (Sunday Saturday) sched-
ules in the DCU. In an ATS schedule, if the S1 S7 column is left
with all , no commands occur on that day. The point(s) will
remain in the last commanded state for the duration of the special
day.
The field entries for this editor are as follows:

Date Enter the date of the special day. For a holiday that
lasts more than one day enter the first day of the holiday.
Enter the date as MM/DD. It is not necessary to enter a zero
before a single-digit month or day (enter July 4th as 7/4).

Special Days Controller Functions
Dates do not have to be entered chronologically. Dates will be

sorted automatically when you exit the editor. You may also
assign more than one special day schedule to a single date, in
effect creating a new special day type.
Duration This is the length of the special day. Enter the
number of days (1127) this schedule is in effect. For the
Christmas holiday in a business environment, you might
enter a 1, while a school district might enter 7 days as the
duration of their Christmas schedule. If you enter a duration
of zero (0), this special day will be deleted when you exit the
editor.
Note: Special days cannot extend beyond the end of the year. If you have a
single holiday period beginning at Christmas and extending into
January (typical school holiday schedule) you must create two special
days: one beginning 12/25 and having a duration of seven days and
another beginning 1/1 and lasting the remaining number of days in
the holiday period.
Special Days The next seven columns are labeled S1

through S7. The default is a dash () in each column. This
indicates that no special day is assigned. Select , P, or T.
indicates no special day. If you do not select any
special days (all in S1S7), this special day will be
deleted when you exit the editor.
P is a permanent special day that remains in the
controllers memory from year to year. Assign a P to a
holiday that occurs on the same date each year (New
Years Day, Christmas Day).
T is a temporary special day. Assign a T to holidays that
occur on different days each year (Hanukkah, Good
Friday). The special day will be removed automatically
once the date has passed.

Controller Functions Event Sequences
Event Sequences
The event sequences editor is used with the event definition point
extension. Adding an action sequence to a point requires 8 bytes of
memory plus additional bytes for each action defined in the
sequence. The memory required for each event sequence action is
shown in Table 5-11.
Table 5-11. Event Sequence Action Memory Requirements
Memory
Action
Required
Start
Start with Lock
Stop
Stop with Lock
Lock Door 5 bytes
Lock Door with lock
Inhibit alarm
Enable alarm
Event Unlock
Output
9 bytes
Output with Lock
Skip if Zero
Skip if Non-Zero 6 bytes
Unconditional Skip
Use this editor to define a specific set of actions that occurs when
an event defined in the event definitions extension editor takes
place. For example, this function lets you plan what control or
output commands will be initiated in an emergency situation.
In addition to emergency planning, event sequences let you
program normal sequential operations such as the start up of a
conveyor line, a chilled water plant, or any other sequential process
you may require at your facility.
It is strongly recommended you use the forms provided in
TCON157, I/NET Forms and Worksheets, to organize and design
the event sequences you need at your facility. Event sequences may

Event Sequences Controller Functions
be quite complicated and it is virtually impossible to enter the

information into the computer unless you have put the informa-
tion on paper.
Note: Event sequences run in a linear manner. They must run from the first
item in the sequence through to the last item in the sequence. Once
started, the sequence must finish before it may be called again.
The field entries for the event sequences editor are described below:
Sequence Number The sequence/action number (064)
you entered in the event definition extension editor. You may
define up to 64 event sequences for each controller. You may
also specify an event sequence #0, that runs at power-up, after
a controller reset, or after a database restore of the DCU. The
restart control action for any DO/DC point that is controlled
by event sequence #0 should be None. No other event
sequences run at power up. If more than one sequence (18
commands) are required, the SKIP command can be used to
connect as many sequences as required.
Sequence Name The name you wish to associate with this
sequence. The name can consist of up to 8 alphanumeric
characters. Be careful to enter a unique name for each event
sequence since the system allows duplicate names to be
entered.
Delay The delay in seconds (03,600) to be honored before
the defined sequence command on the same line is executed.
Typically the delay function is used for timing between
commands.
Action The action the system is to take is entered here.
Event sequences always issue the first of a control descrip-
tion/command pair as a start command and the second of the
control description/command pair as a stop command. Verify
that your control description/command pairs are defined
accordingly. The valid actions are listed in Table 5-12.
Point The name or address of the point to receive the
action you specified.

Table 5-12. Action Types Event Sequences
Action Description
This command issues a start command (first command of the points control
description/command pair) to the designated piece of equipment. If you issue
this command to a door, it places the door into the Secure mode.
Start The Start command can be overridden by any other automatic program that
normally starts or stops this point, or by a person using a workstation or HHC. In
the case of a door point, this command can also be overridden from a PIN pad
by a user with access to the appropriate user-defined PIN pad function.
This action issues a stop command (second command of the points control
description/command pair) to the designated piece of equipment. If you issue
this command to a door, it places the door into the Unlock mode.
Stop The Stop command can be overridden by any other automatic program that
normally starts or stops this point, or by a person using a workstation or HHC. In
the case of a door point, this command can also be overridden from a PIN pad
by a user with access to the appropriate user-defined PIN pad function.
This command should not be used with indirect points. This action issues a start
command to the designated piece of equipment and locks the device in this
state. If you issue this command to a door, it places the door into a fixed Secure
mode.
Start with Lock With its state locked, the point cannot be controlled by any automated processes
other than another event sequence. However, the locked state can still be
overridden manually through the use of a host workstation or HHC.
An Event Unlock command can be used to unlock the point, allowing it to once
again be controlled by normal automated processes.
This command should not be used with indirect points. This action issues a stop
command to the designated piece of equipment and locks the device in this
state. If you issue this command to a door, it places the door into a fixed Unlock
mode
Stop with Lock With its state locked, the point cannot be controlled by any automated processes
other than another event sequence. However, the locked state can still be
overridden manually through the use of a host workstation or HHC.
An Event Unlock command can be used to unlock the device, allowing it to once

Event Sequences Controller Functions
Table 5-12. Action Types Event Sequences (Continued)
Action Description
This command will lock the specified door (i.e., it changes the doors mode to
Lock).
Lock Door The Lock Door command can be overridden by any other automatic program that
normally starts or stops this point. It can also be overridden manually by a person
using a workstation, HHC, or PIN pad (if the user has access to the appropriate
user-defined PIN pad function).
As with the Lock Door command, this command will lock the specified door.
However, this command will also lock the doors state. With its state locked, the
door cannot be controlled by any automated processes other than another event
sequence. The locked state can still be overridden manually through the use of
Lock Door with a host workstation or HHC.
lock
An Event Unlock command issued to the door point will unlock the doors state
and reinforce the doors normal operating mode (i.e., Lock, Unlock, or Secure).
With the door state unlocked, it can once again be controlled by normal
automated processes.
This pair of commands lets you inhibit or enable the alarm function of any point.
Unlike the alarm inhibit/enable extension, this function allows points to be
Inhibit/Enable
enabled/inhibited immediately, and does not depend upon the state of another
Alarm
point. This command overrides an inhibit or enable condition set by the alarm
inhibit/enable extension, and vice versa.
This command can be used to unlock a device that was previously locked by any
of the following commands:
Stop with lock
Output with lock
Event Unlock Lock Door with lock
The locked state of a device can only be changed manually (i.e., using a
workstation or HHC) or by another event sequence. After issuing the Event
Unlock command to a device, the devices state can once again be controlled by
normal automated processes.
This command lets you designate an analog value that is output to an AO/GO
point as part of this event sequence. This output does not override the high or
low output limit you specified when you defined the point. This desired output is
Output
entered in the Value field. This action is later subject to override by any other
automatic program that normally starts or stops this point, or by a person using
a workstation or HHC.

Table 5-12. Action Types Event Sequences (Continued)
Action Description
This command should not be used with indirect points. As in the Start with Lock
and Stop with Lock commands, the Output with Lock issues a command that
cannot be overridden by any automatic program other than another event
sequence. The points locked state can still be overridden manually through the
use of a host workstation or HHC.
Output with Lock The Output with Lock feature lets you pre-plan a specific value or position. Due
to memory limitations, if using only Output with Lock commands, you may only
use 12 line items per event sequence instead of the normal 18 line items per
event sequence.
An Event Unlock command can be used to unlock the point, allowing it to once
Tells the controller to refer to another system point to see if it is currently in the 0
state and, if so, command the event sequence to either skip to another sequence
or to another element in the same sequence. If the point state is 1 (nonzero), this
Skip if zero line in the sequence is ignored and the sequence proceeds to the next entered
item. The point to be verified does not need to be an element in the sequence.
Typically, the point being verified is an input feedback point such as a DM or DI
point that monitors the state of a commanded device.
This command functions just as the zero command described above. In this
Skip if non-zero case, however, the controller checks to see if the point in question is in the 1
(nonzero) state.
This command allows the sequencing of commands to skip to another sequence
Unconditional
number or skip a specified number of actions in the same sequence following the
skip
current line number.
Note: Lock commands have the highest possible priority. For example, use lock commands for
stairwell pressurization fans when a fire alarm signal is received to pressurize the stairwell
when smoke is detected.
Skip/Value Use this option to chain more than one event

sequence to an event definition, or to skip certain elements in
the sequence when the Zero or Nonzero conditional state-
ments are used. Enter the number of actions to be skipped,
the event sequence to skip to, or the analog value to be issued
in the case of an output analog value command.

Event Actions Controller Functions
Event Actions
The event actions editor is used with the event definition point
extension. It allows the operator to print a message when a specific
event occurs.
Adding an action message requires four bytes of memory for the
editor, plus one byte of memory per character in the message. The
maximum memory used is 68 bytes per message (4 for the editor
plus 64 characters in the message).
Use this editor to generate action messages in response to an event
or condition defined using the event definition editor.
You may define up to 64 event actions for each controller. Each
action type contains unique parameters required to perform the
function including message distribution parameters.
Message Actions
The field entries for message actions are described below:
Action Message The message to display or print in
response to the event defined. The limit is one line per
message. Each line may contain up to 64 alphanumeric char-
acters. The message will be printed on the host workstations
event printer, and stored in the host workstation alarm table.
Distribution Group and Mask The distribution group (1
4) and active mask position(s) desired. With four possible
distribution groups and eight possible masks, there are a total
of 32 mask positions (4 8 = 32). Distribution groups and
masks direct information from this editor to those worksta-
tions with a matching distribution group and active mask
position.
Priority The priority for sending information from this
editor. The options are None , Routine, Priority, and Critical.
None indicates no priority (no message will be generated).
Select Routine if you want only directly connected worksta-
tions to receive the action message when the event occurs in
the controller. Select Priority or Critical if you want both
remote AD/AA and directly connected workstations to receive

Controller Functions Trend Plot
the action message when the event occurs in the controller.

Priority will cause the Dial Tap to dial the workstation when
the 7806x LAN Tap deferred dialing parameters are met, and
upload all messages that are pending. Critical will cause the
Dial Tap to dial the workstation immediately and upload all
messages, including any pending Priority messages.
Report Actions
This function is reserved for future use.
DIF Conversion Actions

This function is reserved for future use.
Trend Plot
The trend plot editor automatically plots the data collected
according to the parameters defined in the trend sample extension
editor. Data is plotted on an x-y graph. The x-axis represents time
and the y-axis spans the point value range.
The trend plot begins displaying sampled data at the rate of 35
samples per page (five samples per major division). When the 36th
sample is collected, the time scale (x-axis) changes to 70 samples
per page (10 samples per major division). The scale continues to
change to 140 (20 samples per division), 280 (40 samples per divi-
sion), and 560 (80 samples per division), as needed. The maximum
samples per page is 560. At this point, data is displayed on a second
page.
The actual time stamps on the x-axis are determined by the base
time and interval you entered in the trend sampling editor. If you
are sampling every 10 minutes starting at 12:00, the time stamps are
1200, 1250, 1340, and so on. After 36 samples, this scale changes to
1200, 1340, 1520, and so on.

Multi-Point Trend Plot Controller Functions
Multi-Point Trend Plot

This function allows you to plot up to six different points on the
same trend plot. The points do not have to be on the same
controller, nor do you have to be connected to the controller(s)
where the points reside. Any direct connect point on the system
may be used; dial points are not available.
The features of the multi-point trend plot include:
Live or historical data display. The historical data will show all
of the trend data currently residing in the controller. The live
display plots real-time data.
Grid option. This option displays a grid over the plot. The grid
may be turned on and off as desired when viewing data.
Multiple scaling. Two y-axes may be defined, to be used simul-
taneously on the display. This allows you to define the specific
data range(s) of interest. Each point on the plot is assigned to
one or the other y-axis, and will be plotted against that scale.
Only one x-axis is displayed at a time.
Automatic scaling. This option will change the y-axis scales to
the optimum values for displaying data. This prevents off-
scale data, which can cause gaps in the plot. You may switch
back and forth from automatic scaling to the manual scaling
entered in the plot definition.
Clip Board. This option will copy the data into the Windows
clipboard, allowing you to paste it into a third-party program.
See Plot Functions on page 5-47 for a more detailed description
of these options.
Trend Data
In order to use this function, the points to be plotted must have
trend sampling data available. Refer to Chapter 7, Point Extensions,
for information on adding the trend sampling (TR) extension to a
point.

Controller Functions Multi-Point Trend Plot
This plot uses the trend information stored in the controller. This
limits the maximum number of samples to 1440 for each point.
Trend sampling parameters should be set so as to provide data over
the desired period of time within that sample number.
Note: This plot does not use data stored in SevenTrends tables, only what is
currently stored in the controller. Once a trend sample is overwritten
with new data in the controller, the old sample data is unavailable for
this trend plot.
Trend Report Definition

Trend plot definitions are stored on the host workstation, and can
be called up at a later date. This is useful in cases where the same
trend information is desired on a periodic basis.
The trend editor has a window for selecting a plot definition. When
you first enter the editor, this report selection window is empty.
This is because no plots have been defined yet.
The options in this editor are as follows:
Add Create a new plot definition.
Delete Remove the selected plot definition. You will be
asked to verify that you wish to delete the definition. Once
deleted, the definition cannot be restored.
Modify Change the selected plot definition. Any or all
parameters of the definition may be edited, including the
name.
Copy Copy the selected plot definition to another defini-
tion. You must specify the target definition name, which may
be either an existing definition, or a new one.
Graph Display the selected plot. Refer to Trend Plot
Display on page 5-46.
Plot Definition
The field entries to define a multi-point trend plot are described
below:
Name The name for this plot definition. This name may be
up to eight characters long, and must be unique.

Title The title for this plot definition, up to 48 characters.

The title appears at the top of the plot display, and is included
when a plot is printed.
Y1 Axis Interval The interval between tick marks for the
first y-axis. This axis will appear on the left edge of the plot
display. The default for this field is 10.
Y1 Axis Low The low value for the first y-axis. Values
below this level will be off the edge of the plot when the
manual scale option is used. The default for this field is 4.
Y1 Axis High This display-only value is calculated auto-
matically, based on the low value and interval selected for the
first y-axis. Each axis will have 10 tick marks above the low
value, at the interval specified. Values above this level will be
off the edge of the plot when the manual scale option is used.
The default for this field is 100.
For example, an interval of 15 with a low value of 60 will
result in a high of 210. The tick marks will be at 75, 90, 105,
120, 135, 150, 165, 180, 195, and 210.
Y2 Axis Interval The interval between tick marks for the
second y-axis. This axis will appear on the right edge of the
plot display. The default for this field is 10.
Y2 Axis Low The low value for the second y-axis. Values
below this level will be off the edge of the plot when the
manual scale option is used. The default for this field is 4.
Y2 Axis High This display-only value is calculated auto-
matically, based on the low value and interval selected for the
second y-axis. Each axis will have 10 tick marks above the low
value, at the interval specified. Values above this level will be
off the edge of the plot when the manual scale option is used.
The default for this field is 100.
Live Scan Rate The interval for polling the controller
when the live (real-time) display option is selected. Refer to
Plot Functions on page 5-47. This may be any value
between 0 and 32,767 seconds. The default for this field is 5
seconds.

Point Selection
In addition, you must specify the points to be graphed on the trend
plot. Up to six points may be selected.
You may add a point, modify a selected point, or delete a selected
point. You may use the modify option to replace a selected point
with a different point.
Point Definition
The point definition screen allows you to specify how the data for
the point will be displayed.
The top portion of the window shows the point address and name
of the selected point. Use the Select button at the bottom of the
screen to choose the desired point (see Point Selection on page
5-46).
The point definition options are as follows.
Pen Color The color for the data line for this point. Select
one of the sixteen colors available. The default is yellow for all
points. If you do not change the default color, all lines will be
plotted in yellow.
A box next to the pen color field displays a sample of the
selected color.
Note: The plot display background is black. A black line on the display will
not be visible. A printed plot will have blank paper as the back-
ground. Choose your colors accordingly.
Axis The y-axis scale used by this line. Specify either the
Y1 or Y2 axis for each point. (Refer to Plot Definition on
page 5-43 for a discussion of the Y1 and Y2 scales.)
Print Indicates whether this line will appear on a printed
plot. If this box is not selected, the line will appear on the
screen plot, but will not be included in a printed plot.

Point Selection
The point selection screen is the same one used in other applica-
tions. It is divided into four main windows. The first window, in the
upper left corner, will display the trended points from the
connected controller. Only points with a trend sampling extension
will appear.
The other three windows allow you to specify a controller. The
trended points from each controller will appear in the designated
window. Use the Station button at the bottom of the screen to
select a controller for display for each window.
You may select a point from any quadrant, or enter the point
address in the boxes at the bottom of the screen. The full point
address, including point type, is required.
Link The LL portion of the LLSSPPBB PT address for the
desired point. This field is automatically entered if you select a
point from one of the four quadrants.
Station The SS portion of the LLSSPPBB PT address for
the desired point. This field is automatically entered if you
select a point from one of the four quadrants.
Point The PP portion of the LLSSPPBB PT address for the
Bit Offset The BB portion of the LLSSPPBB PT address for
the desired point. This field is automatically entered if you
select a point from one of the four quadrants.
Type The PT portion of the LLSSPPBB PT address for the
Controller The controller type for this point address. This
field is not required for the multi-point trend plot.
Trend Plot Display

The trend plot display lists the plot title in the bar at the top of the
screen. This is the title entered when defining the report (see Plot
Definition on page 5-43). The plot area itself, a black rectangle,
occupies the majority of the screen.

Axis Displays
The Y1 axis is on the left side of the plot area, and the Y2 axis is on
the right side. Each of these may have a different scale (see Plot
Definition on page 5-43).
The x-axis appears at the bottom of the plot area. A slide bar below
the axis allows you to scroll across the plot display. The axis labels
will depend on the type of display selected.
When historical data is displayed, the tick marks on the x-axis
are labeled with the time the sample was collected, in
HH:MM format.
When live data is plotted, the x-axis labels will be the elapsed
time since live data was requested, in minutes and seconds.
The tick marks will be spaced according to the scan interval.
Note: The sample intervals of the selected points can be different. For
example, one point may be sampling at one-minute intervals, while
another is sampled at five-minute intervals. The intervals between
ticks on the x-axis will be the lowest common denominator of all
participating sample intervals, and the x-axis time span will account
for the largest number of samples.
Plot Functions
Several functions allow you to control the plot display. The func-
tions are described below:
Historical / Live Switch the plot display between historical
and live data.
The default display is historical data. This is a plot of all
the trend samples currently stored in the controller(s) for
the selected points. The plot begins with the oldest
samples on the left, and proceeds to the right with newer
samples.
The live data option allows you to poll the current status
of the plotted points. This option polls the controller(s),
using the live scan interval set in the plot definition. The
data is then plotted on a real-time basis. When this
option is selected, the plot will initially be blank. The first

sample(s) will be plotted at the left edge of the graph, and

proceed to the right. When the screen fills, the old
samples will slide off the left side of the screen.
Grid Places a grid over the data, spaced at the tick marks
on each axis. Select this option again to toggle the grid off.
Print Print the plot. The Print option is not available (i.e.,
it appears gray) if no points have the Print checkbox selected.
This option will print the currently displayed plot. Only
points selected for printing will be included (see Point Selec-
tion on page 5-45). A header page is included with each
print, which includes the title and a legend, including the
name and description of each point.
If historical data is printed, all of the collected data will be
printed.
If live data is printed, only the data shown on the current
screen will be printed.
Auto Scale / Manual Scale Switches between automatic
and manual scaling for the Y1 and Y2 axes.
The default scaling is manual. Each axis will have ten tick
marks using the low value and interval selected (see Plot
Definition on page 5-43). Point values above or below
this range will not appear on the plot.
Automatic scaling will adjust the low value and interval
for each axis, to accommodate all sample values.
Options Allows you to modify the plot display.
Note: These changes affect the current plot display only. They do not modify
the plot definition.
X Scale This option allows you to compress the scale

shown on the x-axis. The default value is a factor of 1,
which is the normal scale. You may compress the scale by
a factor of 2, 5, 10, 15, 30, or 60. This allows you to show
a longer time period on one screen.
Y1 Interval and Y1 Low Value This allows you to
change the scale and range of the Y1 axis.

Y2 Interval and Y2 Low Value This allows you to

change the scale and range of the Y2 axis.
Live Scan Rate This allows you to change the scan
rate for a live display. This option is not available during a
historical display.
Clip Board Copies the current data into the Windows
system clipboard function. This function captures the data
being plotted (value and time), not the plot itself. The data is
in OEM Text format, which can be pasted into most (third-
party) spreadsheet programs.
Note: Depending on your PCs free resources and available memory, it may
not always be possible to cut and paste all values stored in the Multi-
point Trend plot to other Windows applications.


CHAPTER
6
28
Input and Output Points
Resident Input/Output Point Types

Resident input and output (I/O) points reside in the controller.
They are either external points connected to the outside world (a
temperature sensor is one example), internal points such as a calcu-
lation, or indirect points such as a common outside air tempera-
ture among controllers. There are 10 point types:
Discrete Input (DI)
Digital Input (GI)
Discrete Alarm (DA)
Analog Input (AI)
Pulsed Input (PI)
Analog Output (AO)
Digital Output (GO)
Discrete Output (DO)
Discrete Monitor (DM)
Discrete Control (DC)
Discrete Input (DI) Points

DI points sense the state of a contact that can be measured with
single or multiple closures. The point is considered binary if it
exists in one of two possible states: ON or OFF, OPEN or CLOSED,
etc. The maximum number of states for a point is eight, which
requires three contacts (bits).
Typical DI points are flow verification (yes/no) on a fan or pump,
high level float switch closure, or door switch (open or closed).
This point type may be supervised (monitored for breaks or shorts
in the line), but it will not produce an alarm indication.

Resident Input/Output Point Types Input and Output Points
If the controller supports point supervision, adding a supervised

resident DI point to a controller requires 38 bytes of memory.
Adding an unsupervised resident DI point to a controller requires
28 bytes of memory.
Note: Supervision is available for DI points in the following controllers:

7716, 7718, 7756, DPU7910A, DPU7920, DIU7930, DIO7940, and
SCU12xx. Refer to the Installation Guide included with your
controller for wiring diagrams and detailed information.
Digital Input (GI) Points

This is a specialized DI point that requires the use of eight consec-
utive bit offset addresses. Only the first address (typically bit offset
BB = 00) is defined in the database. The location of these addresses
varies depending on the type of controller.
Adding a resident GI point requires 44 bytes of memory.
Digital input points create an equipment value based on the state
of eight contacts using one point address (PP) and all eight of its
associated bit offsets (BB values 0007). Depending on the bit or
bits energized, an equipment unit value, called counts (X), is
produced.
The equipment unit value (X) ranges from 0 to 255 (see Table 6-1
below). Equipment values are additive. For example, all contacts
open results in an equipment unit value of zero (0); all contacts
closed results in an equipment unit value of 255; contacts 00, 01,
and 07 energized results in an equipment value of 131 (1 + 2 + 128
= 131).
7700 or 7740
You must use point addresses 2800, 2900, 3000, or 3100. A GI point
assigned to any other point address such as 2801 or 0300 will
not work.
7716, 7718, 7728, 7756, 7760, 7780, 7791, 7792, 7793, 7798
Again you need eight consecutive addresses but you must use bit
offsets of 00 (0000, 0100, etc.).

Input and Output Points Resident Input/Output Point Types
DI 07 DCU
(128)
DI 06
(64)
DI 05
(32)
DI 04
(16)
"X" "Y" Application
Field Conversion
Database Programs
Device(s) Coefficients
DI 03 0255 Eng. (Editors)
(8) counts Units
DI 02
(4)
DI 01
(2)
DI 00
(1)
Figure 6-1. Digital Input Conversion Diagram
Table 6-1. Digital Input Equipment Unit Values
Point Address Equipment Unit

(BB) Value (X)
00 1
01 2
02 4
03 8
04 16
05 32
06 64
07 128
7750 or 7770
These controllers do not support external GI points.
Discrete Alarm (DA) Points

This is a specialized DI point. Use it when you want to be aware of
an alarm condition sensed by a contact opening/closing. Multiple
contacts may be monitored for up to eight states for the point. For

a binary (two-state) point, the two states of a DA point are

NORMAL and ALARM. You determine which state (0 or 1) is
normal. This point may be supervised (monitored for shorts or
breaks in the line).
Adding a resident DA point requires 30 bytes of memory.
Note: Supervision is available for DA points in the following controllers:

7716, 7718, 7756, DPU7910A, DPU7920, DIU7930, DIO7940, and
SCU12xx. Refer to the Installation Guide included with your
controller for wiring diagrams and detailed information.
Analog Input (AI) Points

AI points sense a variable and convert the input from current or
voltage (analog value) to counts and then to a displayed value. It
differs from a DI point in that it senses a value (such as 72 degrees)
rather than a binary condition of one of two possible states.
Adding a resident AI point to a controller requires 44 bytes of
memory.
Pulsed Input (PI) Points

PI or accumulator points accumulate pulses from the data environ-
ment and convert them into engineering unit values. External PI
points are capable of accepting pulses from such devices as electric
demand pulse meters, flow meters, or other devices that convert a
flow to a pulsed output. Internal accumulators can accumulate not
only pulses but analog values as well, and in the case of an inte-
grating accumulator, can convert an instantaneous rate input into
a total value.
Note: Internal PI points are always the target of a calculated point, and
must use a conversion coefficient pair of m = 1.0 and b = 0.0.
Adding a resident PI point to a controller requires 36 bytes of

memory.
Different controllers vary in the external pulse rates they can
handle, as shown in Table 6-2. All controllers are shipped from
TAC configured for a maximum input rate of 4 pulses per second

(120 msec recommended minimum duration). Some controllers

can accept an absolute maximum input rate of 20 pulses per second
(absolute 20 msec minimum duration). This includes the 7718,
7728, and 7756 DCUs.
Table 6-2. Pulse Rate Limits
Maximum
Controller Minimum Pulse Duration Comments
Pulse Rate
7200 UC 4 per second 120 msec recommended

7700 DCU 4 per second 120 msec recommended
7716 PCU 4 per second 120 msec recommended
4 per second 120 msec recommended HHC code 10 = 0
7718 PCU
20 per second absolute 20 msec absolute HHC code 10 = 1
4 per second 120 msec recommended HHC code 10 = 0
7728 I/SITE
20 per second absolute 20 msec absolute HHC code 10 = 1
4 per second 120 msec recommended upper I/O board
7756 PCU
20 per second absolute 20 msec absolute lower motherboard
7780 DLCU 4 per second 120 msec recommended
MR 4 per second 120 msec recommended
Analog Output (AO) and Pulse Width Modulated (PWM)

Output Points
AO and PWM points both use analog point processing. If you have
a 7700, 7716, 7718, 7756, MR123-032MB, MR632, or 7728 I/SITE
I/O controller you have the option of using true AO points or
PWM points. All other controllers provide only PWM points. A
true AO point uses a digital-to-analog converter to convert counts
to analog signals. Refer to Digital to Analog Conversion in
Chapter 5, Controller Functions for more information.
Typically the output, either 420 mA or 010 VDC, is used to repo-
sition a device such as a valve actuator or damper operator.

A PWM point does not use a digital-to-analog converter. In the

equation described in Digital to Pulse Width Conversion in
Chapter 5, Controller Functions, x is expressed in time units (10
milliseconds per unit) rather than counts. In terms of the hard-
ware, a PWM output point is really a DO point operating with AO
point processing. As the value of the PWM point varies, so does the
pulse duration of the hardware output.
Adding a resident AO point to a controller requires 40 bytes of
memory.
Note: When using Pulse Width Modulated (PWM) outputs in any

controller equipped with relay outputs (i.e., 7716, 7756, MR88R,
7200UC, etc.), a very small pulse may be observed even when the
output of the PWM point is at zero percent. This pulse typically only
energizes the LED associated with the output point for a small dura-
tion, but may last long enough to briefly energize the onboard PWM
output relay.
Therefore, for best results, transducers with minimum input ranges

starting at 0.1 seconds (rather than 0.0 seconds) should be used. This
includes TAC model PWM-C, PWM-P, or PWM-V transducers
(with input ranges of 0.1 to 25.6 seconds or 0.1 to 5.2 seconds, for
example). These transducers are designed to ignore input pulses of
less than 0.1 seconds.
Digital Output (GO) Points

This is a specialized DO point that, like the GI point type, requires
eight consecutive point addresses. The 7750 and 7770 do not
support external GO points.
As with the GI point, only the first address is defined. The next
seven hardware inputs and addresses are not defined; however, they
cannot be used for any other purpose. The point addresses for GO
points varies by controller. On some controllers, these addresses
will have the same point portion (PP), with bit offsets (BB) 0007.
On other controllers, the point portion (PP) will be different, and
all bit offsets (BB) will be 00. Refer to Appendix C, Controller Point
Addressing for GO point addressing for specific controllers.

Adding a resident GO point to a controller requires 40 bytes of

memory.
Digital output points energize up to eight consecutive discrete
output points, based on an equipment unit value (X). Engineering
unit value (Y) is converted to equipment unit value (X) using
conversion coefficients.
DCU DO 07
(128)
DO 06
(64)
DO 05
(32)
DO 04
Application (16)
"Y" Conversion "X"
Programs Database Coefficients
(Editors) Eng. 0255
DO 03
Units counts
(8)
DO 02
(4)
DO 01
(2)
DO 00
(1)
Figure 6-2. Digital Output Conversion Diagram
The equipment unit value, called counts (X), ranges from 0 to

255. Calculation of the slope (m) and Y-intercept (b) is identical to
that for an analog output point driving a D/A converter, except the
equipment unit value (X) determines which of the 8 discrete
outputs will be energized (see Table 6-3). Equipment values are
additive. For example, if the equipment unit value (X) is 75,
discrete outputs 1, 2, 4, and 7 are energized (1 + 2 + 8 + 64 = 75)
Table 6-3. Digital Output Equipment Unit Values
Equipment Unit Discrete Output

Value (X) Energized
1 1
2 2

Table 6-3. Digital Output Equipment Unit Values (Continued)
Equipment Unit Discrete Output

Value (X) Energized
4 3
8 4
16 5
32 6
64 7
128 8
Discrete Output (DO) Points

DO points control the state of binary outputs. These points are
typically used for turning devices such as fans, pumps, and lights
on and off. DO points are also used for door-related points (door
strike) if you are using access control. Door points must use bit
offset addresses of 08 or 09. Keep this in mind when assigning an
address to a door point.
Adding a resident DO point to a controller requires 33 bytes of
memory.
Discrete Monitor (DM) and Discrete Control (DC) Points

These points are always used in a pair. They control devices that
would otherwise be controlled by an ordinary DO but are consid-
ered critical enough to warrant a DM/DC combination. The DC
point does the actual controlling (opening and closing of the hard-
ware contact) and the DM point provides positive feedback from
an external discrete device (for example, an air flow switch).
The DM point is typically wired to a proof-of-flow switch that
transitions when the controlled device is started or stopped. It may
also be used to monitor an auxiliary contact on a motor starter if a
proof-of-flow switch is not installed. However, used in this way, the
only information you are really receiving is that the contacts have
closed or opened, but not whether the device is actually running.
The DC point senses deviation between the commanded state and
the monitored state, and provides an alarm if the controller
commands the DC point ON or OFF and the DM point does not

transition. The DC point also generates an alarm if an external

force alters the state of the DM input point and the output point
was not changed; for example, an operator using a Hand-Off-
Auto switch.
Adding a resident DM point to a controller requires 30 bytes of
memory. Adding a resident DC point to a controller requires 37
bytes of memory.
When controlling DC/DM points using DCU/PCU resident DDC,
calculated points, or automatic temperature control (ATC), the
Resident I/O Points editor entries of Scan Interval, Time to State,
and Alarm Delay are very important. Use the guidelines below to
ensure that an alarm is correctly generated any time the DM points
actual state conflicts with its respective DC points Expected State:
Regardless of which program is used, the time to state and
alarm delay entries for the points should always be set large
enough that the point being controlled is allowed ample time
to change state (start, stop, etc.) before the point is declared to
be in alarm. The DM points alarm delay value should always
be set greater than the DC points time to state value.
In DCU/PCU resident DDC, the scan interval of the module
should be set greater than the time to state and scan interval
entries of the DC point being controlled.
When using a calculated point extension to drive a DC/DM
pair, the DC points time to state should be less than the scan
interval of the point.
When using ATC to control a DC/DM pair, it is important to
remember that the point will always be issued a command by
the program at the rollover of each minute. If the space
temperature exceeds the cooling setpoint plus 1 2 the differen-
tial at 35 seconds past the minute, the DC point will be
controlled ON in 25 seconds, again 60 seconds later, again 60
seconds later, and so on. When using ATC, it is recommended
that the scan interval, alarm delay, and time to state entries all
be set less than 60 seconds, allowing this alarm checking to be
completed prior to the rollover of the next minute, when ATC
issues its next command.

Global and Indirect Points

Global points are used to share information from one controller to
another. If a point is not a global point, the state or value of that
point is available only to other points in the same controller. If a
point is specified as global, you may use it to control an indirect
point in another controller. Any internal or external point may be
designated as a global point.
When a point is defined as global, a corresponding indirect point
must be set up in the additional controller(s). Indirect points reside
in a different controller from the global point, and act as receptors
for value or status information broadcast from the global point.
When entering an indirect point, you must specify the name or
address of the associated global point. The global point must be
designated with the appropriate globalization level. There are four
different levels of globalization, as shown in Table 6-4.
Table 6-4. Globalization Levels
Globalization Level Description

This point provides information only to this controller. A global setting of
None
None indicates that this is not a global point.
This point may provide information to an indirect point in any device
LAN
connected to this controller LAN.
Link
connected to this host LAN.
System
connected to the I/NET system.
Note: Adding a large number of global and indirect points can adversely
affect the system response time. Each globalization and request for
globalization is a message from the DCU. A large number of global
and indirect points can overload the DCUs message capability. This
can reduce system performance, and may cause the system to discard
messages.
An indirect point uses the same amount of memory as a direct

point of the same type. For example, an indirect DI point would
use 38 bytes of memory, just like an internal or external DI point.

The different global levels are illustrated in Figure 6-3 on page

6-11. For this example, the controller marked with contains a *
global point. The other symbols show the controllers that may have
indirect points reflecting the value of the global point, and the
globalization level that would be required.
Global Level Symbol

LAN
Link
System
* = global point
Host Host
Workstation Workstation
Host/Link/
Host Tap Ethernet LAN Tap
LAN
Host LAN
Link Tap
Link/LAN
Tap
Site Taps
*
Controller LANs
Figure 6-3. Global Point Levels
Sending Information
Global points communicate with their indirect point counterparts
on solicited basis and unsolicited basis, as described below.
Unsolicited Communication
Global points periodically broadcast their state/value to corre-
sponding indirect points on a unsolicited basis. The frequency of
the broadcast depends on the point type.

All point types broadcast under the following conditions:

The DCU is restarted by pressing the reset button.
A global output point is changed from Auto to Manual,
or from Manual to Auto. This does NOT apply to the
TEST mode.
A global input point changing to or recovering from the
old data state due to either a communication failure, or
an input point falling outside or re-entering its sensor
limits.
Global analog points (AI, AO, GI, GO) broadcast whenever
their value changes through a range greater than the specified
broadcast change counts parameter.
Global discrete points (DI, DA, DM, DC, DO) broadcast
whenever their state changes.
Global pulsed input points (PI) broadcast whenever their
scans between broadcast parameter is exceeded.
Solicited Communication
Rather than waiting for a global points unsolicited broadcast to
occur, an indirect point can request an update from the associated
global point if any of the following events occur:
A LAN reconfiguration occurs on the controller LAN where
the indirect point resides.
A Station Lost/Restored message is received from the station
where the global point resides.
The indirect point gets added, copied, or modified with the
Resident I/O Points Editor (or gets created as a result of a
Station Restore).
Direction of Flow
If the global point is an input point, its change of state or value is
broadcast to all associated indirect point(s). If the indirect point is
an input point, its change of state or value is not broadcast to the
associated global point (one-way broadcast only).
All output points (both global and indirect) broadcast their state or
value changes to the other associated point(s) (two-way broadcast).

Input and Output Points Input and Output Addressing
Old Data State

Indirect points are flagged as Old anytime an update request is
initiated and no response is received from the global point. Updates
are requested based upon any of the three conditions described in
the Solicited Communication discussion, above. If no response is
received within 2 scan intervals of the indirect point, the Old Data
flag is set.
Indirect Points in subLAN Devices
When using indirect points with a UCI, DPI, MRI, MCI, or I/SITE
LAN, always add indirect points at addresses not used by subLAN
devices. Add the indirect points at addresses that are left as internal
(default) in the associated configuration editor.
Input and Output Addressing

Each controller has a certain number of available inputs and
outputs. Inputs and outputs are further broken down into discrete,
PWM, analog, and pulse categories.
Each point is assigned a ten-character point address composed of
link, station, point, and bit offset numbers, and the two-letter point
type. The point address is in the form LLSSPPBB PT, where LL
designates the link, SS designates the station, PP designates the
point, BB designates the bit offset, and PT designates the point
type.
See Also: Appendix C, Controller Point Addressing
Point Database Parameters

I/NET provides several point database parameters. Some of the
parameters such as point name and point class are universal to
all point types. Other parameters are specific to a single point type
or group of point types. For example, only PI points have the
parameter scans between broadcast.

Point Database Parameters Input and Output Points
Forms are available to help you in planning and entering your point
parameters. These forms can be found in TCON157, I/NET Forms
and Worksheets.
Point Name
This field is used with all point types. Enter a name up to 16 char-
acters in length. Indirect point names are limited to eleven charac-
ters.
You can use the default name which is the point address and point
type, or you can be more descriptive: Exhaust Fan E4 or Chiller C2
are typical point names.
Point Class
This field is used with all point types. All points belong to a point
class: external, internal, or indirect. Select the appropriate point
class.
The default point class is external. External (hardware) points are
physically connected to the outside world or they may control an
output. Internal (software) points exist only within the software
and are used for intermediate functions such as calculations. Indi-
rect points are used to mirror globalized points from other control-
lers.
Scan Interval
This field is used with all point types. Enter a number between 1
and 255. This is the length of time in seconds that elapses between
point scans.
If the point is an external input point, the controller scans the
point at the interval you specify here, and updates its
state/value in RAM memory of the DCU.
If the point is an external output point, or an internal input or
output point, the scan interval determines how often a calcu-
lated point equation controlling the point (if applicable) is
processed.

Input and Output Points Point Database Parameters
If the point is an indirect input or output point, the scan

interval governs the time it will take to go to the old data
state (refer to Old Data State on page 6-13).
The default scan interval is 10 seconds for input points and 60
seconds for output points. All points can have their own unique
scan intervals. All external discrete input points are scanned for
discrete contact changes at 100 millisecond intervals.
Note: Defining an individual scan interval reduces available RAM memory

in the DCU by approximately four bytes. You can conserve DCU
memory by using the same scan interval for multiple points.
Global Level
This field is used with all point types. If you wish to globalize a
point, you must determine what level of globalization is needed:
Local, LAN, Link, or System. Select a global level if the point
contains information that would be useful to points in other
controllers.
Local The point information is only available on this
controller (no globalization).
LAN The point information is available to all controllers on
the same controller LAN.
Link The point information is available to all controllers on
the same host LAN.
System The point information is available to all controllers
on the I/NET system (full globalization).
See Also: Global and Indirect Points on page 6-10
Alarm Priority
This field is used with all point types. Select the priority for alarm
messages originating from this point. The choices are routine,
priority, and critical.

The default is None, which indicates no alarm originating from

this point is ever displayed or printed at any host workstation.
Alarm messages originating from this point are displayed or printed

Routine
only to a direct connect host.
Same as Routine, except that this priority will also cause a dial Tap
Priority
to dial out whenever the deferred dialing parameters are satisfied.
Same as Routine, except that this priority will also cause a dial Tap
Critical
to dial out immediately.
Distribution Group
This field is used with all point types. This field is used in conjunc-
tion with the mask field (see below). You must designate one of
four distribution groups that matches a host workstation distribu-
tion group or no message masks will be matched. For a message
mask to match it must be part of the correct distribution group.
Masks
This field is used with all point types. Activate the position(s)
corresponding to the workstation(s) that should receive messages
originating from this point. Both the distribution group and at
least one active mask position must match in order to receive
messages.
This field is used in conjunction with the Distribution Group field
(see above). You must activate a mask position that matches a host
workstation active mask position, or no messages will be received
regardless of the message priority you assign the point. Message
masking is mandatory when more than one host workstation is
connected to a LAN. Messages from specific points are received
only by workstations with a matching mask pattern. There are eight
possible masking options and four distribution groups, defining a
total of 32 mask positions.
See Also: Masking in Chapter 3, System Messages

Message Priority
This field is used with all point types. Select the priority for
messages originating from this point. The choices are routine,
priority, and critical.
The default is None, which indicates no message or data origi-
nating from this point is ever sent to any Tap or host workstation.
Routine Send messages/data only to a direct connect host.

Same as Routine, except that this will also cause a Dial Tap to
Priority
dial out whenever the deferred dialing parameters are satisfied.
Same as Routine, except that this will also cause a Dial Tap to
Critical
dial out immediately (send dial request).
Caution: Points storing information to SevenTrends tables/cells must have at

least a priority of Routine when attached to a direct connect host, or
the table/cell will not receive the data. On dial out Tap systems points
storing information on SevenTrends tables/cells must have at least a
priority of Priority, or the Tap will not send the data.
SevenTrends data is also distributed according to message priority

and masking. These point parameters must match the SevenTrends
priority and masking defined in the host configuration editor in
order to receive SevenTrends data. A cell is a data storage location
in SevenTrends. Use this parameter to assign a set of priorities for
report purposes. This is unrelated to the alarm priority specified
above. This is the priority level for SevenTrends data storage only.
SevenTrends tables/cells record certain events or classes of events,
which are then available for later inspection and analysis over a
defined time period.
Cell Number
Note: When entering point information, do not enter SevenTrends parame-
ters (priority, mask, or cell number) if you are not planning to collect
SevenTrends data. In this situation, these fields should be left blank.

If you enter SevenTrends parameters without defining the corre-

sponding trend, you may experience a system slowdown as the
controllers generate upload requests that are never answered.
This field is used with all point types. This field is used for grouping
SevenTrends data in displays and reports. Enter a number between
1 and 1,023.
You must assign a value other than zero in order for SevenTrends to
store the trend information. Otherwise, this field is not used in
I/NET Seven and can be any value.
Note: A cell number of zero indicates that no cell number is assigned, and
no SevenTrends data will be sent to the host workstation.
State Descriptions
This field is used with DI, DA, DM, DC, and DO point types only.
You should select the line number corresponding to the first line of
the state descriptor set you want to use to describe this point. This
will be any even number between 0 and 30, assuming you began
entering state description pairs on line zero. For multiple-bit DI
and DA points, the number entered here is the first state descrip-
tion of the four (2-bit point) or eight (3-bit point) state descrip-
tions being used. Refer to State Descriptions in Chapter 5,
Controller Functions.
Number of Bits
This field is used with DI and DA point types only. Select 1, 2, or 3
to describe the number of bits monitored by the DI or DA point.
1-bit points are by far the most common but 2-bit and 3-bit points
are sometimes necessary. You should be familiar with the point as
it exists in your system and therefore you should know the number
of bits required before you get to this stage in developing your data-
base. Each bit represents one contact in one of two states: 0 (open)
or 1 (closed).

1-bit
Using one bit results in two states: one contact in a 0 or 1 state.
What these states are depends on your system, how it is wired, and
the nature of the discrete point.
2-bit
Using two bits results in four states: two contacts, each in a 0 or 1
state (2 2 = 4). Because there are two bits there are four possible
permutations, here listed in their binary order: 00, 01, 10, and 11.
A 2-bit input requires 2 consecutive bit offset addresses, but only
the first point address must be defined in the database. You must
remember not to assign the second address to another point. The
addresses used for a 2-bit DI must be consecutive and must contain
the same point number.
You must also reserve four consecutive state descriptions, one for
each of the possible permutations listed above. You need to take
this into account when you first enter state descriptions. You need
to have four together that make sense for your 2-bit point. You
enter the first of the four into the state description field when you
define the point and the system automatically uses the next three
state descriptions for the point.
3-bit
Using three bits results in eight states: three contacts, each in the 0
or 1 state (2 2 2 = 8). Because there are three bits there are eight
possible permutations, here listed in their binary order: 000, 001,
010, 011, 100, 101, 110, or 111.
A 3-bit input requires three consecutive bit offset addresses, but
only the first address must be defined in the database. The point
address selected for multiple bits must be located in a controller
with sufficient available addresses. The second and third addresses
must fall within the same point number and cannot be used for any
other purpose. For example, in a 7716 controller, if you define 0004
DI as 3-bit, then hardware inputs 0005 DI and 0006 DI must also
be available.

You must also reserve eight consecutive state descriptions, one for
each of the possible permutations listed above. You need to take
this into account when you first enter state descriptions. You need
to have eight together that make sense for your 3-bit point.
Example of a multi-bit point: You have a fan that has four possible
operational modes: OFF, LOW, MEDIUM, and HIGH. Each time
the fan moves to a different state (00, 01, 10, or 11) the appropriate
state description is displayed next to a point icon on a graphic
system page, for example. A more complicated device might have
eight possible states.
See Also: TCON299, I/NET Seven Operator Guide
Normal State
This field is used with DA point types only. Select 1 (normally
closed) or 0 (normally open) to indicate the normal state of this
point.
You must know how your system is wired before you can enter a
number here. The normal state is displayed in green. The opposite
Alarm state is displayed in flashing red.
Alarm Delay
This field is used with DA, DM, AI, and GI point types. Enter a
number between 0 and 32,767. This is the number of seconds the
system must continuously detect an alarm condition before
reporting it. Any return to the normal state during the specified
alarm delay period resets the counter.
Control Description
This field is used with DC and DO point types only. Select a
number between 0 and 15. This is the first line number of the
control description pair (STRT/STOP, ON/OFF, etc.) entered in the
Station Parameters editor. This determines the control command
(0/1) issued to the associated discrete output point. Refer to
Control Descriptions in Chapter 5, Controller Functions.

Momentary Duration
This field is used with DC and DO point types only. Enter a
number between 0 and 2.55. This is the duration (in seconds)
during which the start or stop output contact/relay is energized
when the appropriate command is issued.
Note: This function is not available on DO points in UC, MR, and ASC
products.
Any time a momentary duration is entered, the system uses the

point itself as the 0 control command output and the next consec-
utive hardware output as the 1 control command output. For
example, if the control command pair of STRT (1)/STOP (0) is
entered, a STOP command would energize the point itself for the
specified interval, and a STRT command would energize the next
consecutive output for the specified interval. If the opposite control
command pair of STRT (0)/STOP (1) is used, the results are also
opposite: a STRT command would energize the point itself for the
specified interval, and a STOP command would energize the next
consecutive output for the specified interval.
Note: I/NET automatically uses the next consecutive output point. You do
not have to populate the point using the Resident I/O Points editor.
Expected State
This field is used with DC point types only. Select either 1 (closed)
or 0 (open) to correspond to the state of the associated DM point
when the DC point issues a command of 0.
For example, if the control command pair is ON = 0 and OFF = 1,
and the DM is wired so the contact is closed when the fan is
running and therefore produces a 1 in the ON (0) state, enter a 1 in
this field as the Expected State.
Another example: if the flow sensor is wired as a normally closed
device and opens upon flow, the DM senses a 0 in the ON state, so
enter a 0 as the Expected State.

Restart Control Action

This field is used with DC and DO point types only. Select Rein-
force, None, Trip, or Close. This action tells the controller what to
do to the DO/DC point when a DCU restart occurs due to a power
cycle or manual reset.
Do not confuse this with the control fail-safe value which is in
effect when the controller database is cleared. The selection you
make here refers only to the state assumed when the DCU restarts,
provided the database remains intact.
Select Reinforce if you want the point to return to the state it was in
prior to the DCU power failure. Select None if you want the point
to default to the way the point is wired, either normally open or
normally closed. Select Trip if you want the point commanded to
the deenergized or 0 state. Select Close if you want the point
commanded to the energized or 1 state.
Note: These settings only specify the initial state the point will default to
upon restart. The normal control activity will then resume governing
the state of the point.
Minimum Trip
number between 0 and 255. This is the number of minutes that
must elapse following a 0 command from the controller before a 1
command can be issued.
A 0 command opens or breaks a circuit and thus deenergizes it.
This is also referred to as a trip command. A 1 command closes the
circuit, energizing it. These parameters protect equipment from
short cycling and are assigned the highest priority level. The only
higher levels of priority are operator action from a workstation or
HHC, and event control.
Minimum Close
number between 0 and 255. This is the number of minutes that
must elapse following a 1 command from the controller before a 0

command can be issued. A 1 command closes a contact,

completing a circuit and energizing a point. A 0 command opens
or breaks a circuit by deenergizing a point.
Note: The minimum trip and close parameters are not used for Unitary
Controller (UC), Micro Regulator (MR), or Application Specific
Controller (ASC) output commands. The editor lets you enter a value
in this field. However, the UCI, MRI, MCI, or I/SITE LAN replaces
the entered value with the default value of 0 when it is downloaded to
the UC, MR, or ASC.
Time To State
This field is used with DC point types only. Enter a number
between 0 and 32,767. This is the number of seconds the system
waits for a device that has been issued a start or stop command to
reach the expected velocity or output before checking the DM
point to determine an alarm condition. Once the time entered here
has elapsed, the point reports an alarm if the monitored point has
not transitioned to the correct 0 or 1 state.
Three-State Output
This field is used with DO point types only. All door points used in
door controllers must be defined as three-state
(secure/unlocked/locked). Enable this option for door points only
(must have bit offset 08 or 09).
Monitor Point Address

This field is used with DC point types only. Select the point address
for the DM point monitoring the device being controlled by this
DC point.
Conversion Equation
This field is used with AI, GI, AO, GO, and PI point types. Select
Linear or Flow. This designates the equation the system will use
when calculating conversion coefficients (see Conversion Coeffi-
cients Tables in Chapter 5, Controller Functions).

Engineering Units
This field is used with AI, GI, AO, GO, and PI point types. Select a
number between 0 and 15 that corresponds to the line number of
the engineering unit table (defined in the Station Parameters
editor) containing the unit you want to describe the value of this
point. Refer to Engineering Units Table in Chapter 5, Controller
Functions for more information.
Conversion Coefficients
This field is used with AI, GI, AO, GO, and PI point types. Select a
number between 0 and 15 that corresponds to the line number in
the conversion coefficients table (defined in the Station Parameters
editor) containing the slope (m) and offset (b) coefficients you
wish to use with this point. Refer to Conversion Coefficients
Tables in Chapter 5, Controller Functions for information on
calculating and entering conversion coefficients.
Offset
This field is used with AI, GI, AO and GO point types. Enter a
number between 128 and 127. This is the number of offset equip-
ment unit value counts required to eliminate sensor input or trans-
ducer output error.
Use this parameter to calibrate sensors or to adjust for increased
resistance due to long wire runs. To calculate this number, divide
the actual error in reading by the m value of the appropriate
conversion coefficient pair.
To compensate for sensor error, enter the same count value, but
with an opposite sign. For example, enter an offset value of +15
counts to compensate for a sensor error of 15 counts. Refer to
Digital Input (GI) Points on page 6-2 and Digital Output (GO)
Points on page 6-6 for a discussion on equipment unit value
counts.
Low Sensor Limit

This field is used with AI and GI point types only. Enter a number
within the acceptable engineering unit range for the sensor associ-
ated with this point.

If the sensor produces a number below the value you enter here, the
sensor is considered to be in error and is declared inoperative (old).
If you do not enter a value here, this field defaults to the b value
of the appropriate conversion coefficient pair.
High Sensor Limit

ated with this point.
If the sensor produces a number above the value you enter here, the
sensor is considered to be in error and is declared inoperative (old).
If you do not enter a value here, this field defaults to the highest
value this input can sense.
Low Alarm Limit

ated with this point. If the sensor records a value less than the
number you enter here, the point goes into alarm.
High Alarm Limit

ated with this point. If the sensor records a value greater than the
number you enter here, the point goes into alarm.
Broadcast Change Counts

This field is used with AI, GI, AO, and GO point types. Enter a
number between 1 and 255. This is the number of counts the
measured value of the point must increase or decrease before the
point broadcasts a new value if global.
To calculate the number of counts, divide the desired change value
in engineering unit readings by the m value of the appropriate
conversion coefficient pair. Round the result to the nearest count
and enter that figure in this field.

For example, assume you have a DCI Lini-Temp sensor (displaying

in F) connected to a 7716 PCU with conversion coefficients of:
m = 0.17592 b = 279.4
You want to broadcast the new temperature to all other DCUs
whenever the temperature changes by 3F. Calculate the broadcast
change counts as follows:
3 / 0.17592 Divide the desired degree change by the m coefficient

= 17.05 (degrees per count).
= 17 counts Round off counts to the nearest whole number.
In this example, you would enter 17 in the Broadcast Change

Counts field.
Non-linear Lookup Table

This field is used with AI points only. This feature allows non-linear
count readings from the A/D converter to be translated into usable
count readings corresponding to known sensor characteristics.
Enter a number between 0 and 3 that corresponds to the embedded
non-linear lookup table to use. Refer to Table 6-5 for guidelines on
using the proper lookup table.
Table 6-5. Non-linear Lookup Table Usage
Lookup
Controller Type Used For
Table #
All 0 Indicates no lookup table

1 Hoffman pressure transducers for 7211 UC
Unitary Controllers
2 Auto Trans pressure transducers in 7261 and 7262 UCs
(UCs)
3 Not used
1 I/STAT or 10K thermistor inputs on I/STAT port (bit offset 07)
Micro Regulator
2 10K thermistors on all other inputs (bit offset 0006)
Controllers
3 Not used
1 I/STAT or 10K thermistor inputs on I/STAT port (bit offset 07)
MR55 Series
Controllers 2 10K thermistors on all other inputs (bit offset 0006)
(MR55X)
3 On-board Auto Tran velocity pressure transducer

Accumulator Type
This field is used with PI point types only. Select the type of accu-
mulator. I/NET provides three separate and distinct types of accu-
mulators:
External (8-bit/16-bit) Accumulates externally-generated
pulses and converts them to engineering units for measure-
ment or use elsewhere in the system. 16-bit is used only for
upgrading model 8000 systems. Use 8-bit for all other
controllers.
Reflective (internal or indirect points) Accumulates the
value resulting from a calculation.
Integrating (internal or indirect points) Accepts the result
of a calculation. The accumulator divides an instantaneous
rate (value of the calculation) by the fraction of an hour since
it was last calculated and adds the value to the previously
stored value. This type accumulator is used to convert and
store values such as kilowatt hours to kilowatts, or gallons per
hour to gallons.
Note: Internal Pulsed Input (PI) point types are always the target of a
calculated point.
Scans Between Broadcast

This field is used with PI point types only. Enter a number from
1255. This is the number of point scans (see Scan Interval on
page 6-14) that will take place before the information is sent to
indirect PI points in other DCUs.
Since the value of an accumulator is always increasing, you need to
select a broadcast frequency rather than a magnitude of change
between broadcasts. For example, if you wish to broadcast the value
of an accumulator every five minutes and the value of the Scan
Interval is set at 10 seconds, enter 30 in this field [300 seconds (5
minutes) divided by 10 seconds (scan interval) equals 30].

Supervised
This field is used with DI and DA point types only. Select the type
of supervision used for this point. You may enable either the 1-
Resistor or 2-Resistor configuration.
Note: The one-resistor configuration represents a three-state discrete input

(open, closed, or cut). The two-resistor configuration represents a
four-state discrete input (open, closed, cut, or short). You do not need
to make the input point multiple bits, and point supervision does not
take up additional hardware addresses.
You may define DI or DA points on certain controllers (notably the

7716 PCU, 7718 PCU, 7756 PCU, DPU7910A, DPU7920,
DIU7930, DIO7940, and SCU12xx) as supervised points. Refer to
the installation guide for the appropriate controller for wiring
diagrams and detailed information.

CHAPTER
7
52
Point Extensions
Point extension editors perform predefined special functions on

specified points. Certain extension editors are only applicable to
specific point types. Table 7-1 below shows the general function of
each extension, and the point types which may use that extension.
Each extension description includes the page number (Pg
column) for more detailed information on the extension type.
Table 7-1. Point Extensions by Point Type
Point Extension and Description Point Types
A A D D D D D G G P
Ext Description Pg
I O A C I M O I O I
Alarm Inhibit prevents nuisance alarms

AI that may occur when a piece of equipment is 7-3
off.
Calculations defines calculations on

points to expand the capability of the
C 7-4
controller or provide information that cannot
be obtained from a sensor.
Consumption directs the accumulated

value of a PI point to a particular
CN consumption cell for storage. Also zeroes 7-17
the value stored in the DCU for the PI point
at midnight.
Demand Control monitors PI points for

electrical power consumption, predicts
demand, and maintains daily and monthly
DC power consumption totals. Includes load 7-18
shedding capability (ability to control points
off). Not available on 7750, 7770, 7780, or
7791 controllers.

Point Extensions
Table 7-1. Point Extensions by Point Type (Continued)
Point Extension and Description Point Types
A A D D D D D G G P
Ext Description Pg
I O A C I M O I O I
Elevator sets access parameters for

elevators. May only be used for door points
(bit offset BB 08 or 09) defined as elevators.
EL Each elevator will have associated DO (floor 7-24
relay) and DI (floor selection button) points.
This extension is only available in the 7791
DPI, 7793 MCI and 7798 I/SITE LAN.
Event Definition specifies a certain

condition (event) and the response that
EV condition initiates (event action or event 7-26
sequence). Events are limited to specific
point types.
Lighting Control controls lighting points by

zone. Lighting control may be a cycle or a
LC 7-29
time schedule. This extension is only
available in the 7780 DLCU.
Override Billing allows you to use the 7750

Building Manager, with dial-in access, to
OB control points residing in other controllers. 7-33
This extension is only available in the 7750
DCU.
Runtime defines runtime parameters for a

discrete point (input or output) so that
RT 7-38
runtime information can be collected for
SevenTrends reports.
Temperature Control controls output

points managing HVAC units. Also provides
TC optimized start/stop, night setback/setup 7-39
control, and demand temperature override
control.
Trend Sampling sets parameters for

TR recording data from this point for graphs or 7-44
SevenTrends plots.
Time Scheduling controls output points

TS 7-47
according to the schedule entered.

Point Extensions Alarm Inhibit (AI)
You may wish to use the forms provided in TCON157, I/NET

Forms and Worksheets, to help you design and define point exten-
sions. This simplifies the final data entry process.
Alarm Inhibit (AI)

The Alarm Inhibit editor is available on all controllers. This point
extension is used with AI, GI, DA, and DM points.
Adding this extension to a point requires 7 bytes of memory.
Add this extension to a point to prevent nuisance alarms that may
occur when a piece of equipment is off. For example, you may wish
to inhibit alarms from a chilled water supply temperature point if
the chiller is not running. You may also use this extension to deter-
mine which state (0 or 1) of the controlled device enables the
alarm.
Note: This editor processes on the rollover of the minute in the DCU. If
faster inhibit/enabling is required, use the event control extension
editor with the inhibit and enable commands in the event sequence
editor.
The entry fields for this extension editor are as follows:

Status input The point name or address of the device that
determines the inhibiting or enabling of the alarm point. In
the case of a chiller this would be the DO or DC point that
controls the chiller.
Enable state Indicate the state of the enabling device
(status input) you wish to use as the enable state, either 0
(deenergized) or 1 (energized).
Delay before enable The number of minutes (0255) you
wish the alarm point to remain inhibited after the status input
point transitions to the enable state. If the point is still in an
alarm state when this delay time is up, an alarm is generated.
Delay before inhibit The number of minutes (0255) you
wish the alarm point to remain enabled after the status input
point transitions to the inhibit state.

Calculations (C) Point Extensions
Calculations (C)
The calculated point editor is available in all controllers. This point
extension can be used with all point types.
Note: Calculations may be used only with internal or external points. Indi-
rect points may not use the calculations extension.
Adding this extension to a point requires 4 bytes of memory for

each variable in the equation, 5 bytes for each constant, and 2 bytes
for each function (min, day).
Add this extension to internal or external points to expand the
capability of the controller in some way or provide information
that cannot be obtained from a sensor. A calculated point extension
can be used to calculate the state or value of an input point rather
than read the value of an external sensor. When added to output
points, calculations let you develop customized applications in the
controller which cannot be accomplished by using the standard
programs furnished in the controller (such as temperature control
or time scheduling). Typical examples of calculated points are:
summation of several flow sensor inputs to derive total flow,
display tons of refrigeration from sensed supply and return
water temperatures and flow through a chiller,
accumulating compressor start ups on a daily basis, and
deriving seasonal changes based on monthly data.
Any condition that can be defined using arithmetic, boolean, or
relational operators can be defined as a calculation. Other special
function operators (month, day, year, enthalpy, dew point, relative
humidity, etc.) are also provided.
Equation Enter the appropriate calculation, using C0C9
for constants, P0P9 for points, and the necessary operators.
Do not enter actual numbers or point addresses. The calcula-
tion may be up to 80 characters long.

Point Extensions Calculations (C)
Do not use spaces in the calculation. You may use parentheses

to ensure that the operations are carried out in the order you
intend. If you are in doubt about the order of operations, use
parentheses: any unnecessary parentheses will be deleted
automatically when the calculation is downloaded to the
DCU. (The calculation on the screen will not be updated until
you exit and reenter the editor.)
You may enter up to 10 point parameters (P0 through P9) and
10 constant parameters (C0 through C9) in any one calcula-
tion. You may use the same parameter more than once.
Points Give the point address for each point used in the
calculation (P0P9). Point addresses must already be defined
in the DCU.
Constants Give the value for each constant used in the
calculation (C0C9). Constants may be up to 16 digits long.
However, only 6 significant digits will be used in the calcula-
tion. Any additional digits will be rounded off. For example,
123,456,789 becomes 123,457,000; 1,234.56789 becomes
1,234.57.
You may use as many parameters as necessary to perform your
calculation, within limits. Since the rule for determining the total
number of parameters and operators is very complex, and beyond
the scope of this manual, the best test is to enter the calculation and
observe whether or not the controller accepts it. If not, break the
calculation into two or more equations. The result of the first
calculation can then be used as a parameter in the second calcula-
tion.
Selecting a Calculated Point Address

The target point address (the point whose value will change as a
result of the calculation) must reside in the controller where the
calculation exists, and may be either internal or external. Most
calculations are assigned to internal points but external output
points are occasionally used as the target of a calculation.
Use external points when you wish to have the result of the calcu-
lation cause a state change (DC or DO points) or change the value
of an output (AO or GO points).

Use internal points when the result of the calculation is used for
informational purposes, such as an intermediate step in a chain of
calculations, as an input to a DDC module, as an initiator for an
event sequence, or as a repository for an accumulation.
The calculated state or value must match the point type to which it
is assigned. If you expect your calculation to produce an analog
value you must direct it to an analog point or a PI (accumulator)
point. If you expect your calculation to produce a binary answer
(true or false, 1 or 0), you must direct it to a discrete point.
Each calculation is processed in ascending point address order and
at the scan interval defined for the target point address in the resi-
dent input/output editor where you originally defined the point. If
two points (input and output) have been defined at the same
address, and both have been assigned the same scan rate, the
output point calculation will be processed first, followed by the
input point. It is sometimes helpful to make use of the sequential
scan order to detect changes that occur between scan updates or
when you wish to note changes in one direction only. For example,
you may wish a PI point to accumulate only starts or stops.
The state or value of a calculation is reinforced each time the point
is scanned. If you wish to force a point that is controlled by a calcu-
lation to a specific state or value, you must first put the point in test
or manual mode, or control it with one of the lock commands in
the event definition extension editor.
Operators
Calculation parameters (points and constants) are connected by
operators. There are four main types of operators: arithmetic, rela-
tional, boolean, and function. Arithmetic operators perform a
mathematical calculation. Relational operators evaluate the rela-
tionship between two values. Boolean operators evaluate a condi-
tional statement involving two or more values, and return a true
or false condition (1 or 0). In addition, special function operators
have been included to perform predefined calculations.

The following table lists the available operators, along with their
data entry symbol, type, and rank (16). A higher rank number
indicates that the operator or function is performed in an equation
before an operator with a lower rank. Each operator is described in
detail on the following pages.
Table 7-2. Operators for Calculations
Rank Symbol Description Type Page
1 (performed last) & And Boolean 7-8

^ Exclusive or Boolean 7-8
| or -| Or Boolean 7-8
2 (performed fifth) = Equal Relational 7-9
> Greater than Relational 7-9
>= Greater than or equal Relational 7-10
< Less than Relational 7-10
<= Less than or equal Relational 7-10
<> Not equal Relational 7-10
3 (performed fourth) + Addition Arithmetic 7-10
Subtraction Arithmetic 7-10
4 (performed third) / Division Arithmetic 7-10
* Multiplication Arithmetic 7-10
5 (performed second) ~ Logical negate Boolean 7-9
Negate Arithmetic 7-11
6 (performed first) AVG Average of values Function 7-11
DAY Day of month Function 7-11
DOW Day of week Function 7-11
DP or DPSI Dew point Function 7-14
EDP or EDPSI Enthalpy from dew point Function 7-15
ERH or ERHSI Enthalpy from relative humidity Function 7-15
HIGH Highest value Function 7-11
HR Hour Function 7-12
JULD Julian date Function 7-12
LOW Lowest value Function 7-12
MIN Minute of hour Function 7-12
MPM Minutes past midnight Function 7-12

Table 7-2. Operators for Calculations (Continued)
Rank Symbol Description Type Page

6 (performed first) MO Month Function 7-13
OLD Old data Function 7-13
RH or RHSI Relative humidity Function 7-15
SQRT Square root Function 7-13
TTS Time to start Function 7-13
YR Year Function 7-14
Boolean Operators
Boolean operators evaluate the stated condition, and return a
true or false response. Use these operators in a calculation to
produce a discrete state, either a 0 or a 1. A 0 corresponds to false
and a 1 corresponds to true.
Each section of the boolean expression is called a statement. The
statement may be a single term, such as the state of a discrete point,
or a complex equation, such as a comparison of several values or a
calculation. For complex expressions, it is recommended that you
use parentheses to define the statements.
And This operator requires all statements connected by AND
to be true before the total expression is true. If any statement is
false, the entire expression is false. An example AND expression
is shown below.
(P0=P1)&(P2*C0<C1)
Exclusive or This operator allows only one statement to be true
in order for the expression to be true. If multiple statements are
true, or all statements are false, the expression becomes false. An
example EXCLUSIVE OR expression is shown below.
(P0=P1)^(P2*C0<C1)
Or This operator allows two or more statements connected by
OR to yield a true expression even if only one of the statements is
true. The expression is only false if none of the statements are true.
An example OR expression is shown below.
(P0=P1) -| (P2*C0<C1)

Table 7-3 below illustrates how the AND, OR, and EXCLUSIVE OR
operators work together. In this table, A represents the first state-
ment, and B represents the second statement.
Table 7-3. Boolean Operations
Statement Result of Boolean Expression
And: Or: Excl. Or:

A B
A&B A -| B A^B
False (0) False (0) False = 0 False = 0 False = 0

True (1) False (0) False = 0 True = 1 True = 1
False (0) True (1) False = 0 True = 1 True = 1
True (1) True (1) True = 1 True = 1 False = 0
Logical negate This operator is a boolean state change. A calcu-

lation of ~P0 reverses the state of the point (for the purposes of the
calculation). A 1 becomes 0 and vice versa. The logical negate can
be combined with other boolean operators, to change a single
statement, or to reverse the result of the total expression. Please
note that the position of the logical negate symbol is very impor-
tant. The three expressions shown below are NOT equivalent:
~(P0<C0) -| (P2&P3)
(P0<C0) -| ~(P2&P3)
~((P0<C0) -| (P2&P3))
Relational Operators
Relational operators are very similar to boolean operators. These
operators also evaluate the stated condition, and return a true or
false response. Using these operators results in a calculation that
produces a discrete state, either a 0 or a 1. A 0 corresponds to false
and a 1 corresponds to true.
Equal This is a relational equality: 7=7, 1=1. An example
expression is shown below.
(P0+P1)=P2
Greater than This is a relational greater than: 78 > 10. An
example expression is shown below.
(P0+P1)>P2

Greater than or equal This is a relational combination of

greater than and equal: 6 >= 6, 6 >= 5. An example expression
is shown below.
(P0+P1)>=P2
Less than This is a relational less than: 0 < 6. An example
(P0+P1)<P2
Less than or equal This is a relational combination of less
than and equal: 6 <= 6, 6 <= 7. An example expression is shown
below.
(P0+P1)<=P2
Not equal This is a relational non-equality: 5 <> 6. An example
(P0+P1)<>P2
Arithmetic Operators
Arithmetic operators are used to perform basic mathematical
calculations. The result may be the value of the point itself, or may
be part of a complex calculation using any combination of boolean,
relational, and function operators.
Addition This is simple addition, 1+2. An example expression
is shown below.
P0+C0
Subtraction This is simple subtraction, 12. An example
P0C0
Division This is simple division, 1/2. An example expression is
shown below.
P0/C0
Multiplication This is simple multiplication, 1*2. An example
P0*C0

Negate This is an arithmetic sign change. (9) = 9, (9) = 9.

An example expression is shown below.
P0
Function Operators
Function operators are used to perform specific, predefined calcu-
lations. Some function operators (such as HIGH, LOW, AVG,
SUM, etc.) are designed to work only with numeric values. Other
function operators (such as DAY, MPM, etc.) are designed to work
on DCU dates or times.
Average of values This function calculates the average value
from a list of up to 10 parameters (points and/or constants). If one
of the parameters fails (i.e., a sensor goes into an old data condi-
tion), the value of that parameter will not be included in the
average calculation. An example expression is shown below.
AVG(P0,P1,P2,P3,P4)
Day of month This function calculates the day of the month in
the DCU. This function returns a value between 1 and 31. An
example expression is shown below.
DAY<=C0
Day of week This function calculates the day of the week in the
DCU. This function returns a value between 1 and 7 (1 = Sunday,
2=Monday, etc.). An example expression is shown below.
DOW<=C0
Highest value This function selects the highest value from a list
of up to 10 parameters (points and/or constants). You may also
establish a minimum value by entering a constant in the parameter
list. For example, if you are selecting the highest room temperature
for a group of offices, you might define the constant as 72 degrees.
If all the office temperatures are lower than 72, then 72 becomes the
value of the calculation. This feature is a useful safeguard to prevent
unnecessary heating if a sensor malfunctions and produces an
excessively low temperature. An example expression is shown
below.
HIGH(P0,P1,P2,P3,P4,P5,C0)

Hour This function calculates the hour in the DCU. This func-
tion returns a value between 0 (zero) and 23. An example expres-
sion is shown below.
HR<=C0
Julian date This function converts the date in the DCU to the
Julian date (an integer). The Julian date is a number between 1 and
366: January 1 is day 1, December 31 is day 365 (day 366 in leap
year). The computer cannot manipulate or compare dates
(MM/DD/YY) as it can simple constants. For example, the
computer cannot subtract March 5 from July 24; but it can subtract
64 from 205. This is a convenient method for performing calcula-
tions involving dates rather than trying to manipulate them in
terms of months and weeks. An example expression is shown
below.
JULD<=C0
Lowest value This function selects the lowest value from a list of
up to 10 parameters (points and/or constants). You may also estab-
lish a maximum value by entering a constant in the parameter list.
For example, if you are selecting the lowest room temperature for a
group of offices, you might define the constant as 85 degrees. If all
the office temperatures are higher than 85, then 85 becomes the
value of the calculation. This feature is a useful safeguard to prevent
unnecessary cooling if a sensor malfunctions and produces an
excessively high temperature. An example expression is shown
below.
LOW(P0,P1,P2,P3,P4,P5,C0)
Minute of hour This function calculates the minutes after the
hour in the DCU. This function returns a value between 0 (zero)
and 59. An example expression is shown below.
MIN<=C0
Minutes past midnight This function calculates the minutes
elapsed since the previous midnight in the DCU. The system
displays a value between 0 (zero) and 1,439. There are 1,440
minutes in a 24-hour day. The computer cannot manipulate or
compare times in hours and minutes as it can simple constants. For
example, the computer cannot subtract 6:15 a.m. from 8:30 a.m.,
but it can subtract 375 minutes from 510 minutes. You simply

convert the time at which you want the point controlled by this
calculation to do something (turn on/off, display a message, etc.)
into minutes. An example expression is shown below.
MPM<=C0
Month This function calculates the month of the year in the
DCU. The system displays a value between 1 and 12 (1 = January,
2=February, etc.). An example expression is shown below.
MO<=C0
Old data This function returns a 1 if the state/value of the
monitored point (P0) is questionable (e.g., an AI point falls below
its low sensor limit). The operator returns a 0 if the state/value of
the monitored point is at an acceptable value (e.g., an AI point
returns to a value within the sensor limit values). An example
OLD(P0)
Square root This function returns the square root of a given
number. This is the number which, when multiplied by itself,
results in the original number (for example, 9 = 3 ). An example
SQRT(P0)
Time to start This function returns the number of minutes (0
1439), until the point is scheduled to be started by an automatic
time schedule. It returns a 0 if the next scheduled action is not a
start command (this usually means that the previous action was a
start command). It returns a question mark (?) if the point does
not have a time scheduling extension appended to it. Although this
function is designed primarily for optimized start commands, it
will work with regular start commands as well. An example expres-
sion is shown below.
TTS(P0)
Note: This operator does not look past midnight.

Year This function calculates the year (any number between 0

and 99) in the DCU. The system displays only the last two digits of
the year. For example, 1995 is displayed as 95, and 2000 is displayed
as 00. An example expression is shown below.
YR<=C0
Thermodynamic Function Operators

These operators are a special type of function operator. Thermody-
namic functions deal specifically with heat relations. The calcula-
tions are based on the psychrometric chart which is familiar to you
if youve studied thermodynamics or air conditioning theory.
These four functions make use of the same three parameters: rela-
tive humidity, dew point, and dry bulb temperature. The dry bulb
temperature is the temperature reading you obtain from a simple
thermometer. In order to use these functions, you must have access
to a temperature sensor (dry bulb temperature) and a sensor for
either dew point or relative humidity. Either dew point or relative
humidity can be calculated, but you cannot calculate both: you
must have one of these parameters, as well as dry bulb temperature,
to calculate the other.
Each function allows calculations in both English and metric
(Standard International) units. The units for your sensor entries
must match the calculation selected for the results to be correct.
The units used for each calculation type are shown in Table 7-4
below.
Table 7-4. Thermodynamic Function Units
Parameter English Units Metric Units
Dew point degrees Fahrenheit (F) degrees Celsius (C)

Enthalpy British Thermal Units per pound (BTU/lb) kilojoules per kilogram (kJ/kg)
Relative humidity percentage (%) percentage (%)
Dry bulb temperature degrees Fahrenheit (F) degrees Celsius (C)
Dew point This function calculates the dew point when you
supply dry bulb temperature and relative humidity. Example
expressions are shown below.

English units: DP(P0,P1)

Metric units: DPSI(P0,P1)
The first parameter (P0) is the dry bulb temperature sensor
address. The second parameter (P1) is the relative humidity sensor
address.
Enthalpy (using dew point) This function calculates enthalpy
when you supply dry bulb temperature and dew point. Example
expressions are shown below.
English units: EDP(P0,P1)
Metric units: EDPSI(P0,P1)

address. The second parameter (P1) is the dew point sensor
address.
Enthalpy (using relative humidity) This function calculates
enthalpy when you supply dry bulb temperature and relative
humidity. Example expressions are shown below.
English units: ERH(P0,P1)
Metric units: ERHSI(P0,P1)

address. The second parameter (P1) is the relative humidity sensor
address.
Relative Humidity This function calculates the relative
humidity when you supply dry bulb temperature and dew point.
Example expressions are shown below.
English units: RH(P0,P1)
Metric units: RHSI(P0,P1)

address. The second parameter (P1) is the dew point sensor
address.
Helpful Hints for Calculations

If the target point of a calculation is a discrete input or output
point, then the calculation must be either true (1) or false (0). The
state of a DI point is simply an indicator but the state of a DO point
affects the hardware it controls. A 0 (false) command to a DO/DC

point issues the first control command of the points control

description/command pair to the output hardware. A 1 (true)
command to a DO/DC point issues the second command of the
points control description/command pair to the output hardware.
If you wish to add the newest result of a calculation to a previously
accumulated value, you can include the target point as a parameter.
For example, P0+(P1*P2), where P0 is entered as the target point.
If you wish to accumulate only one state of a transition (starts or
stops, ons or offs), use the scan sequence to catch the transition
from 0 to 1 or vice versa.
For example, a DO or DC point might have an address of 0000.
Establish a calculated point which reflects the state of the DO or DC
into an internal DI, at address 3107. The calculation for DI point
3107 would be P0 where P0 is the address of the DO/DC point
(0000). Establish a PI point as a reflective accumulator to collect the
desired state change. For this example, the PI point will be address
1600. Lets assume ON is 0 and construct the following calculation:
P0+(P1<>P2)*(P1=C0)
where:
P0 = PI (accumulator) point address 1600

P1 = DO (Ext) point address 0000
P2 = DI (Int) point address 3107
C0 = Constant of 0
The order of the point addresses is critical; the exact address

numbers are not important. Available addresses vary by controller
and the configuration of your system.
If you want to accumulate data from this point on a daily basis,
then you can enter the PI point address into the consumption point
extension editor where it will be reset to zero each day at midnight.

Point Extensions Consumption (CN)
Consumption (CN)
The consumption editor is available on all controllers. This point
extension can be used with PI (accumulator) points, such as KWH
meters.
Adding this extension to a point requires approximately 8 bytes of
memory.
Add this extension to a PI point if you want to direct the accumu-
lated value of a PI point to a particular consumption cell for
storage, and zero the value stored in the DCU for the PI point at
midnight.
Note: Restoring the DCU will reset the accumulated consumption data to
zero (0). Consumption data is always reset to zero (0) at midnight,
even if the PI point is in the Test mode.

Distribution group and Mask The distribution group (1
4) and active mask position(s) desired. Refer to Masking in
extension editor. The options are None, Routine, Priority, and
Critical. Refer to Priorities in Chapter 3, System Messages.
Cell number This field is used for grouping SevenTrends
data in displays and reports. Enter a number between 1 and
1,023. You must assign a value other than zero in order for
SevenTrends to store the trend information. Otherwise, this
field is not used in I/NET Seven and can be any value. A cell
number of zero (0) indicates that no cell number is assigned,
and no SevenTrends data will be sent to the host workstation.
Note: You must also define the trend in the host workstation. Refer to
Chapter 15, SevenTrends, for more information.

Demand Control (DC) Point Extensions
Demand Control (DC)

The demand control editor is available on all controllers except the
7750, 7770, 7780, and 7791. This point extension can only be used
with PI points.
Adding this extension to a point requires approximately 145 bytes
of memory, plus 150 bytes if any load points have been populated.
Add this extension to a PI point to monitor electrical power
demand (KW) and consumption (KWH), and maintain daily
and/or monthly power consumption (KWH) totals. When
combined with the load shedding capability (ability to control
points off), you have an extremely powerful and flexible electrical
demand control program.
The load shedding feature of demand control lets you establish
target KW demand shed level setpoint(s). The controllers on the
LAN shed (turn off) and restore (turn on) loads (DO and DC
points) as needed to operate your facility within the targeted
demand level. This limits the demand segment of your electric
utility charges. Loads are shed and restored according to a priority
you assign, with lower level loads shed before loads assigned a
higher priority. Loads are restored in reverse order; those with the
highest priority are restored first.
See Also: Demand Control in Chapter 8, Dynamic Control
Demand Meter
When you select demand control for a point, you must enter the
demand metering information for that point. The entry fields for
this extension editor are as follows:
Demand interval The demand interval is a time period,
measured in minutes, over which the calculation of demand is
based. This is determined by the power-generating public
utility or distribution authority. You may enter any value
between 5 and 90, in five-minute increments (5, 10, 15, 65, 70,
etc.).

Point Extensions Demand Control (DC)
It is most helpful to select the same demand interval specified

by the power company with which you do business. Demand
intervals are typically 15 to 30 minutes in range.
Current demand point This is an optional entry and is not
necessary to enable the demand program. If you wish to use
an internal point to store or display current demand, enter the
name or address of that point here. This entry must be an
existing PI or AI point.
Monthly consumption point This is an optional entry and
is not required for the demand program to operate. If you
wish to use an internal point to store month-to-date
consumption, enter the name or address of that point here.
This entry must be an existing PI or AI point.
This point directs three separate pieces of information to its

SevenTrends table at midnight each day: todays daily KWH
consumption, todays peak KW demand, and the time of
todays peak demand.
Normal shed level This is the maximum demand target
value, in kilowatts, for the meter under the normal (non-
override) state. This may be either a point or a schedule.

If you select a point, enter the name or address of the

point whose value is the normal shed level. This must be
an existing point. Shedding occurs as soon as the
predicted demand exceeds the value of the selected point.
This point value is usually the result of a calculated point.
If you select a schedule, use the schedule date and level
fields to enter the shed levels (see below). Shedding
begins when predicted demand exceeds the level set for
the current time period.
Note: If you enter constants for the KW demand setpoint in the schedule
portion of the demand editor, the shed level takes effect after the date
in the editor, not before. For example, a setpoint entry of 500 on
01/31 will be in effect from 01/31 until the next entered date (such as
2/28), not from 01/01 to 01/31.
Normal shed differential The number (032,767) of kilo-

watts subtracted from the normal shed level before restora-
tion begins. Defining a differential prevents short cycling
when shedding/restoring begins. If the normal shed level is set
at 95 kilowatts and you define the differential as 5, the system
does not begin restoring loads (turning things back on) until
the predicted demand is less than 90 kilowatts.
Emergency shed level This is the maximum demand
target, in kilowatts, that determines when emergency loads
(priority 7) will be shed. The emergency shed level is only
used if shedding priority 1 through 6 loads is not sufficient to
keep predicted demand below the demand setpoint.
Note: Priority 7 loads will be shed only if the predicted demand exceeds the
emergency shed level setpoint AND all loads with priority 1 through 6
have either been shed or are not available for shedding (see Selecting
Loads to Shed in Chapter 8, Dynamic Control).
The emergency shed level should be greater than both the

normal and override shed levels. This may be either a point or
a constant.


point whose value is the emergency shed level. This must
be an existing point. Shedding occurs as soon as the
If you select a constant, enter the emergency shed level
(032,767) in kilowatts.
Emergency shed differential As with the normal shed
differential, select a differential (032,767)for the emergency
shed level. This prevents emergency loads from turning off
and on in rapid succession when the predicted demand level
is near the setpoint.
Override shed control point The name or address of the
discrete point that will determine whether the normal shed
level or the override shed level is in effect. When this point is
in a 1 state, the override shed level is used. When this point is
in a 0 state, the normal shed level is used.
The most common use for this capability is on-peak and
off-peak demand control. Typically, a time schedule associ-
ated with a user-defined internal discrete point turns it ON
(1) during on-peak times and OFF (0) during off-peak
times. By entering the address of this internal point in this
portion of the editor, the demand program can be switched
between the normal (0, off-peak) shed level and override (1,
on-peak) shed level.
Note: The emergency shed level is always honored. If the override control
point is in the energized (1) state, both the override and emergency
setpoints will be used. If the override control point is in the deener-
gized (0) state, both the normal and emergency setpoints will be used.
Override shed level This is the maximum demand target

value, in kilowatts, for the meter under the override state.
This value replaces the normal shed level when the override
control point is in the ON (1) state. The emergency shed level is
not affected by this parameter. This may be either a point or a
constant.


point whose value is the override shed level. This must be
an existing point. Shedding occurs as soon as the
If you select a constant, enter the override shed level (0
32,767) in kilowatts.
Override shed differential As with the normal shed
differential, select a differential (032,767) for the override
shed level. This differential operates like the normal and
emergency shed differentials but is in effect only when the
override shed level replaces the normal shed level.
Schedule date Enter the desired schedule dates, up to 12.
The defaults for each of the scheduled dates is the last day of
each month. You can change these as necessary to meet your
facility requirements.
This field affects two different processes: the schedule option
for normal shed levels, and zeroing out the monthly accumu-
lator point (if applicable).
If the schedule option was selected for the normal shed
level, this field specifies the ending date for each schedule
period (changing from one schedule level to another).
If a monthly consumption point was specified, this field
specifies the last day of the month. At midnight of the
listed date, the specified accumulator point value is reset
to zero (0).
Schedule level If the schedule option was selected for the
normal shed level, this field specifies the shed level (032,767
kilowatts) for each time period.
Note: The shed level takes effect after the date in the editor, not before. For
example, a setpoint entry of 500 on 01/31 will be in effect from 01/31
to the next entered date (such as 2/28), not from 01/01 to 01/31.

Demand Loads
Use the Demand Loads Screen to specify which loads (DO and DC
points) to shed, in what order they should be shed, and the size of
the load. Load size lets I/NET determine the fewest number of
loads that can be shed to bring demand under the acceptable limit.
You may assign up to 127 demand loads to each demand meter, and
up to 255 demand loads to each controller. Please fill out the
Demand Loads form provided in TCON157, I/NET Forms and
Worksheets, before entering data in this screen.
Note: If indirect points are to be controlled, it is imperative that their asso-

ciated global points be declared as global at the DCU(s) in which the
points reside.
The entry fields for this section of the extension editor are shown
below:
Load The name or address of the point you wish to shed if
it becomes necessary. Enter only points that may be shed.
Caution: Do not enter a point in this portion of the demand control editor if it
is extremely critical (i.e., you would rather go over your emergency
demand setpoint than shut off the device controlled by the point).
Priority The priority level (07) for this load. Priority 0 is

the lowest priority; loads assigned a priority of 0 are shed
most often. Priority 6 is the highest in the normally available
pool of loads. Those loads assigned a priority of 6 are shed
least often. Assign a priority of 7 to those points that you want
shed only in an emergency.
On state The controller must know which state (0 or 1)
represents the ON state for this load. This determines whether
the load is available for shedding.
Load size This is the load size, in kilowatts, for this load.
The Demand Control load shedding program operates by
calculating the smallest number of loads it must shed in order
to bring the predicted demand level under the demand limit.
Use the following formula to determine load size:
Three-phase power: (Voltage Amperage 3 ) 1000

Elevator (EL) Point Extensions
Single-phase power: (Voltage Amperage) 1000

Max off The maximum off time, in minutes, for this load.
This ensures that no point is turned off and left off indefi-
nitely. Once the load has been shed (turned off), a counter
starts running. When the counter exceeds the number of
minutes you enter in this field, the load is restored regardless
of the demand level.
Note: This parameter applies only to off time due to load shedding. It does
not affect off time due to time scheduling or temperature control
functions.
Elevator (EL)
The elevator extension editor is available on 7791, 7793, and 7798
controllers. This point extension can be added to any door point
(DO point with bit offset BB 08 or 09) that is defined as an elevator.
Adding enable and select points consume 8 bytes of memory.
The elevator control function works in conjunction with the access
control parameters and personnel schedules to control access to
elevator floors. In addition to supplying the door parameters at the
door controller level, it is necessary to supply the controller with
the information required to associate an elevator reader with the
discrete output points that enable the floor relays, and the discrete
input points that monitor the button selection. The process
controlled by this editor is as follows:
1. The access key or card is accepted by the appropriate reader.
2. The appropriate DO points for that user are activated, ener-
gizing the designated elevator floor buttons.
3. User pushes one of the elevator buttons.
4. The DI point for the floor button selected in the
DPU/SCU/DCU changes states, and the elevator allows access
to the selected floor.
5. All enabled DO points are deenergized.

Point Extensions Elevator (EL)
For each elevator floor extension, there must be an associated DO

and DI point entered in the elevator extension. This association of
DO and DI point produces a closed-loop feedback, allowing the
controller to identify an elevator floor selection with each
successful key/card reader access.
The entry fields for this extension editor are:
Floor selection time The amount of time in seconds (0
255) that the key/card user has to make a floor button selec-
tion in the elevator cab. After this time limit expires, the floor
buttons are deenergized, and the user must successfully
perform another key/card read to reenable the floor buttons.
When a valid selection is made, the floor buttons are deener-
gized and a message is sent to the host workstation with the
selected floor designation attached to the elevator entry
message.
Note: This field is on the summary page, and affects all elevators.
Floor index number The index number for this floor on

the summary list. This number controls the order in which
floors are listed on the summary screen.
Floor designation The floor designation, which may be
one or two alphanumeric characters. For example, the first
level of a basement could be represented as B1. The floor
designation appears along with any messages generated by
this point.
Button enable Each floor is assigned a button enable
point that energizes after a successful key/card read. A list of
all possible discrete output points in the controller is
displayed. The button enable point is typically an indirect
point with its associated global point (an external DO point)
located in another controller on the same subLAN. Choose the
desired point from the list.
Note: Using a global point on a different controller on the controller LAN as

the source for the button enable point is NOT recommended. This
can cause an unacceptable time delay before enabling the button.

Event Definition (EV) Point Extensions
Button selection Each enable DO point must have a DI

select point assigned to provide a closed loop feedback to the
controller, indicating which floor button was selected by the
key/card holder. A list of discrete input points available for
selection displays.
Event Definition (EV)

The event definition editor is available in all controllers. This point
extension can be used with all points.
Adding this extension to a point requires 5 initial bytes of memory
plus 4 additional bytes for each event action defined.
Use this extension to specify a certain condition and the response
that condition initiates. The event you define causes an event
sequence or an event action to be initiated. Once you define the
event in this editor you must access the event sequence or event
actions editor to define the event sequence or event action to be
performed.
See Also: Event Sequences and Event Actions in Chapter 5, Controller

Functions
The entry fields for this extension editor are described below:
Event type The condition that causes this point to initiate
an event sequence or event action. The valid event types are
described in Table 7-5.
Table 7-5. Event Types
Event Point
Description
Type Type(s)
Any alarm, high or low limit, causes this point to initiate an event sequence or
Alarm AI, GI
event action.
The high alarm limit you specified when you defined the point in the Resident
High limit
AI, GI I/O Points editor is used here. If the value of the point is greater than the high
alarm
alarm limit, this triggers an event sequence or event action.
The low alarm limit you specified when you defined the point in the Resident
Low limit
AI, GI I/O Points editor is used here. If the value of the point is less than the low
alarm
alarm limit this triggers an event sequence or event action.

Point Extensions Event Definition (EV)
Event Point
Description
Type Type(s)
Return to If a point value returns from the low limit or high limit alarm range, this triggers
AI, GI
normal an event sequence or event action.
This is typically a different value than high limit alarm value, although it
High value AI, AO,
functions similarly. When the point value rises above the value you define as
crossing GI, GO
the high value crossing, this triggers an event sequence or event action.
This is typically a different value than low limit alarm value, although it
Low value AI, AO,
functions similarly. When the point value falls below the value you defined as
crossing GI, GO
the low value crossing, this triggers an event sequence or event action.
State change requires a point to change from one state to another to initiate
State an event sequence or event action. Note that the event occurs in both
DI, DO
change directions; i.e., when the discrete point changes from 0 to 1 and when it
changes from 1 to 0.
Specified state initiates an event sequence or action when the point
transitions to a specific state (0 or 1). For specified state events, the point
Specified
DI, DO must have been in the opposite state for at least one scan and then
state
transitioned to the specified state before the DCU will determine that the
event occurred.
This event type is available for DO points; however, it is only functional with
Door
DO door points. Door forced initiates an event sequence or action when the door
forced
point (BB = 08 or 09) registers that the door has been forced open.
door points. Door open too long (DOTL) initiates an event sequence or action
Door open
DO when the door point (BB = 08 or 09) registers that the door has been open for
too long
too long. The time setting for the open duration is set in the door parameters
editor
Door door points. Door normal initiates an event sequence or action when the door
DO
normal point (BB = 08 or 09) returns to a normal condition after previously being in
an abnormal (door forced or DOTL) condition.
Bad card door points. Bad card read initiates an event sequence or action when the
DO
read door point (BB = 08 or 09) card reader is unable to determine the validity of
the presented card.
Request to
DO door points. Request to exit initiates an event sequence or action when the
exit
door point (BB = 08 or 09) is unlocked from a push-button or motion detector.
Door
DO door points. Door relocked initiates an event sequence or action when the
relocked
door point (BB = 08 or 09) is re-locked after being opened.

Event Definition (EV) Point Extensions
Event Point
Description
Type Type(s)
Mode APB door points. Mode APB reset initiates an event sequence or action when the
DO
reset mode schedule on the door point (BB = 08 or 09) resets all anti-passback
flags.
Mode PIN door points. Mode PIN enable initiates an event sequence or action when the
DO
Enable mode schedule on the door point (BB = 08 or 09) changes the door state to
require a personal identification number (PIN) for entry or exit.
Sequence/Action Specifies whether this event results in

an event sequence or an event action.
Num The number (164) that corresponds to the event
sequence or event action to be triggered. You must define the
sequence or action in the event sequences or event actions
editor.
State/Value This parameter is only active when the Spec-
ified State event type is chosen for a discrete point, or when
the High Crossing or Low Crossing event type is chosen
for an analog point.
Analog Point If you define the event type as High
Value Crossing or Low Value Crossing, enter the value
which, when crossed, initiates an event sequence or event
action. Analog sensor input failure, as defined in your
analog input point I/O database, will not initiate any
event you define as high/low crossing or high/low alarm.
Only a valid value above the low sensor limit or below the
high sensor limit can be used to trigger an event.
Discrete Point When defining this parameter setting for
a non-door discrete point, choose a setting of either 0 or
1. The state descriptors you defined for this point state in
the State Descriptions editor automatically appear next
to each state at this time.

Point Extensions Lighting Control (LC)
Lighting Control (LC)

Lighting control is available only in the 7780 controller. You can
define and control up to 96 lighting circuits. The first 64 circuits
can be 7780 DLCU local/external points, and the last 32 circuits can
be remote/indirect DO points in other DCUs.
Adding this extension to a point requires 17 bytes of memory for
each zone, and 12 bytes of memory for each circuit. Each circuit is
listed by address and name. The display also indicates the zones to
which the circuit is attached. There are 32 possible zones.
The 7780 controller supports up to 32 lighting zones, 64
local/external lighting circuits, and 32 remote/indirect lighting
circuits. The 64 local/external points are addressed between
LLSS0000 and LLSS0707. The 32 remote/indirect points are
addressed between LLSS0800 and LLSS1107. You can assign each
circuit to one or more zones. You must define your lighting circuits
before you can assign them to zones.
You must add points in the Resident I/O Points editor before you
can assign lighting circuits, lighting zones, or override points. No
option is available for automatically adding these points.
The wink function is used to blink the lights off and on, as a
warning that the off period of the lighting schedule is
approaching. You can set the length of the winks, and the grace
period after the wink before the lights go off.
Lighting Circuits
A lighting circuit is a single point in the controller. This may be a
single source (lamp), or several sources that have been daisy-
chained together into the same controller point (for example, a
floor within a facility). The field entries for lighting circuits are
described below:
Delay before off The number of minutes (0127) after the
wink cycle ends before the point turns off.
On duration The number of seconds (1255) for the
length of the on part of the wink cycle.

Lighting Control (LC) Point Extensions
Off duration The number of seconds for the length of the

off part of the wink cycle. The options are 0.5, 1.0, 1.5, and
2.0 seconds.
Wink cycles Enter a number between 0 and 16. This is the
number of times the point winks off and on prior to
commencing the delay before off countdown.
Wink sources You must specify which control sources you
want to initiate a wink cycle. You can manually initiate the
wink cycle using the workstation or a hand-held console. If
you appended a time scheduling extension to the lighting
zone, you can use that to initiate the wink cycle. Select the
desired option(s). The default is off (inactive) for all except
the Override input. You will typically want the wink cycle
active for this control source.
Note: This Override Input is the override point specified for the lighting
zone (see Override Billing (OB) on page 7-33). It is not related to
the Override Billing extension available with the 7750 Building
Manager.
For example, assume that there is a time scheduling extension on

the point, set to turn off the lights at 7:00 p.m. (19:00). You wish to
blink the lights to warn any tenants who may still be in the building
that the lights will soon be going off, and allow them 10 minutes to
either vacate the building or activate the override point. You decide
upon a wink pattern of two winks of 1 second each, with 29 seconds
in between. In this case, you would make the following entries:
Delay before off 10 The grace period is ten minutes after the wink
cycle finishes.
On duration 29 The lights are on for 29 seconds at a time during
the wink cycle.
Off duration 1 The lights will be off for one second each time.
Wink cycles 2 The lights will wink off two times.
Control sources Activate Automatic Time Scheduling as a control
source, to indicate that ATS can initiate a wink
cycle. Override input is also selected (by default),
so that a wink cycle can also be initiated when the
override time period expires.

Point Extensions Lighting Control (LC)
Based on these entries, the lights will wink off for 1 second at
7:00:00 p.m. (19:00:00). They will come back on at 7:00:01
(19:00:01) and remain on for 29 seconds. They will go off again at
7:00:30 (19:00:30), and back on again at 7:00:31 (19:00:31).
Another on cycle of 29 seconds completes the wink cycle at 7:01:00
(19:01:00). Then the 10-minute delay begins, with the lights ulti-
mately going off (assuming no override is initiated) at 7:11:00
(19:11:00).
Note: If a tenant activates the override point at any time during the wink
cycle, the wink cycle is halted and the override timer goes into effect
(if the override type is set to Timed). If override input is activated
as a control source input, the wink cycle will begin again at the end of
the override period.
Zone map This display-only section indicates the zone(s)

that this circuit is assigned to. When you are first entering a
circuit, this section will be empty, as the circuit has not yet
been assigned to any zones.
Lighting Zones
A lighting zone is a group of lighting circuits that can be controlled
together. A lighting circuit can belong to more than one lighting
zone. The lighting zone point must use addresses LLSS1200
LLSS1507.
When you add the lighting zone (LZ) extension to the DO point,
you must define the override settings for the zone before you can
select the zones circuits or time schedule. The override function
allows you to energize all the circuits in the lighting zone, regardless
of the zone time schedule. The override is assigned to a zone, and
affects all circuits assigned to that zone.
Note: If a circuit is assigned to multiple zones, the circuit will remain ener-
gized as long as any override is in effect.
The field entries for override parameters are shown below:

Input point The address of the DI point that will initiate a
lighting control override. Select a point from the drop-down
list.

Lighting Control (LC) Point Extensions
Input type The choices are Single-pushbutton, Dual-push-

button, or Latched. Regardless of the input type, override is
initiated when the input point transitions from 0 to 1.
Single-pushbutton refers to a momentary spring-loaded
button. Pressing the button results in a closed contact
(1). Releasing the button results in an open contact (0).
Dual-pushbutton refers to a two-button switch. Pressing
one button results in a closed contact (1), and pressing
the other button results in an open contact (0).
Latched refers to a light switch: once you flip the switch
(1), it stays that way. This also refers to a button you press
(1) that stays pressed until you press it again (0).
Override type You must now define an override type.
Select either Permanent or Timed. If you select Permanent,
the override will continue indefinitely, until the button or
switch is moved again. If you select Timed, the override will
run for a specified number of minutes.
Note: If you create a schedule on this screen, it is automatically defined as

an independent schedule. If you wish to edit a schedule that you orig-
inally defined in the ATS editor, it must be an independent schedule.
Master and slave time schedules can be used to control lighting zones,
but cannot be edited from the lighting control editor.
Override time (minutes) If you selected timed as the over-

ride type, you must define the number of minutes (0120)
you want the override to last. The default is 60 minutes.
The function buttons on this screen allow you to assign circuits to
the zone, and/or set the time schedule for the zone.
Circuit If you select this option, the system displays the
currently defined circuits by number (196), DO point
address, and name. You defined these parameters in the
lighting circuits editor. This screen allows you to assign a
circuit to one or more zones.
ATS If you select this option, the system displays a time
scheduling edit screen similar to the time scheduling editor.
As with the time schedule editor, you can select actions to
begin and end at a specific time (including sunrise and

Point Extensions Override Billing (OB)
sunset), define temporary schedules, and assign schedules to

special days. However the only actions available in this screen
are ON and OFF.
Note: In the ATS editor, lighting zone time schedule On commands will
appear as Start, and Off commands will appear as Stop.
You may create a new schedule, or edit a schedule that was

previously entered either here or in the automatic time
schedule (ATS) editor. Any changes made in one editor are
also reflected in the other editor.
Note: If you create a schedule on this screen, it is automatically defined as

an independent schedule. If you wish to edit a schedule that you orig-
inally defined in the ATS editor, it must be an independent schedule.
Master and slave time schedules can be used to control lighting zones,
but cannot be edited from the lighting control editor.
Override Billing (OB)

Override billing is available only in the 7750 Building Manager
controller. This point extension can be used with DO points only.
Override billing requires 78 bytes of memory, plus 68 bytes of
memory for equipment mapping extension.
This extension lets you use the 7750 to control points residing in
other controllers. You can call the 7750 with a touch-tone phone,
enter the appropriate access code, and override previously defined
time schedules for points.
You can also use this extension to define zones. In this way you can
control multiple points within the same zone. A wink feature
warns you that the override period is expiring, by controlling the
first zone point OFF for a brief period.
In addition, this extension lets you track the number of overrides
requested, the amount of time a zone (point) was in override, and
the electricity consumed during the override time period. If an

Override Billing (OB) Point Extensions
output point is controlled by several zones (a chiller is one

example), this extension lets you identify the electricity use of indi-
vidual zones.
Note: These features are invaluable in establishing billing information in a

building inhabited by multiple tenants. You can request tenants pay
electrical bills that reflect their actual consumption patterns. Tenants
who use a great deal of electricity will be faced with appropriately
large electrical bills. Tenants who use less electricity are not penalized
for inhabiting the same building as a heavy electrical user.
Some Important Information Before You Begin

The override portion of this extension lets you override normal
time schedules for points that reside in any I/NET controller.
A 7750 that occupies one station on the LAN may contain up to 32
zones. A 7750 that occupies two stations on the LAN may contain
up to 64 zones.
A zone override point must be an internal DO point with a zero bit
offset address (BB = 00). For example, if the 7750 were addressed at
station 16/17, the first override zone address would be LL160000;
the 32nd zone would be LL163100; the 33rd zone would be
LL170000; and the 64th zone would be LL173100. These addresses
are fixed in the 7750 DCU.
Each zone may have up to 12 equipment points associated with it.
These 12 points must be DO or DC points with non-zero bit
offsets; e.g., 0101 DO, and are typically indirect points. The actual
hardware outputs being controlled in other DCUs should be
defined as global points. The 7750 can override up to 128 unique
points.
Note: The minimum trip and minimum close times for discrete outputs in
other DCUs controlled via the 7750 DCU are not honored when the
Building Manager initiates control to these output points.
An override of a 7750 DCU zone point may be initiated by any of

the following:

Calling the 7750 with a touch-tone telephone and using its

built-in telephone interface to override existing zone time
schedules. This can be done up to 24 hours in advance.
Closing a discrete switch wired to the optional 64 point inter-
face board that is connected to the 7750. Each input point on
the interface board is dedicated to a specific 7750 zone.
Attaching any of the automatic control programs included
with the 7750 to the zone.
Access Codes
Use this option to establish access codes for each zone. These are
used as passwords when telephoning the 7750 to initiate an over-
ride. Enter a code containing up to six digits for each zone. This is
the number that must be entered from a touch-tone phone in order
to access and override the normal time schedule for a specific zone.
The field entries for access codes are described below:
Non-billable A non-billable access code is typically used by
night cleaning or maintenance personnel when they dial up
the 7750 to place the zone requiring cleaning or maintenance
into override. The amount of non-billable electrical
consumption and override time is accumulated on a daily
basis for each zone and is updated at midnight. If a non-bill-
able override and a billable override overlap each other, the
non-billable override always takes precedence.
Interrogate A code containing up to six digits for interro-
gate access. This code lets you call the 7750 and inquire about
the state or value of any input or output point on the LAN.
You must know whether the point is an input or output, and
its eight-digit point address. This information must be
entered into the system from a touch-tone phone when you
want to interrogate the point.
Control A code containing up to six digits for control
access. This code lets you call the 7750 and control any output
point on the LAN to a certain state or value. You must know
the eight-digit point address of the output point because you
will need to enter it into the system from a touch-tone phone
when you want to control the point.

Override Billing (OB) Point Extensions
Equipment Mapping
Use this option to specify the load size of the equipment point
being controlled, the base load, and the percentage of the total load
that can be assessed to each zone. It also lets you specify how the
points are distributed among multiple zones. This makes it easy for
you to bill the appropriate users/tenants for energy use during the
override period.
Note: Only those points defined in the resident I/O points editor as indirect
and with a non-zero bit offset (BB = 0109) can be equipment
points.
The field entries for equipment mapping are described below:

Load size Enter a number between 0 and 32,767 to specify
the kilowatt (KW) rating for this load so that kilowatt-hour
(KWH) calculations may be made.
Base load percent The number (0100) representing the
percentage of base load. This number is multiplied by the load
size to determine the minimum number of kilowatt hours a
zone accumulates when the load is overridden by a zone.
Zones If the point, such as a chiller, is shared among
multiple zones, you must enter the percentage of the load
which applies to each zone. The total must equal 100 percent.
If the point is only controlled from one zone, enter 100% for
the point in the appropriate zone.
Override Parameters
Use this option to specify distribution group, distribution mask,
cell priority, cell number, and to specify the indirect points
controlled by the zone point. The override parameters screen lets
you assign up to 12 points to each zone for override control.
The override parameters screen also lets you specify a wink interval
to notify the user or tenant that the override period is about to
expire. This wink function is similar to the wink function in
lighting control (see Lighting Circuits on page 7-29).

Note: Only those points defined in the Resident I/O Points editor with zero
bit offset (BB = 00) can be zone points.
The field entries for override parameters are described below:

Wink off interval (seconds) A number (0255) that spec-

ifies how long the first equipment point in the zone is turned
off or winked before being turned back on to indicate the
override period is about to expire.
Wink on interval (minutes) A number (0255) that speci-
fies how long before the end of the override period the system
winks the first equipment point of the zone.
For example, assume a wink off interval of 2 seconds and a
wink on interval of 5 minutes. All equipment connected to
the first point in the zone will turn off for two seconds and
then back on, at the end of the override period. If the override
is not reactivated within this time period, all points in the
zone will be deenergized.
Note: The equipment will wink off only once. Unlike the wink function for
lighting control, you cannot specify the number of winks.

Runtime (RT) Point Extensions
Equipment points This feature allows you to assign

specific points to specific zones. You may assign up to 12 indi-
rect points that a 7750 can override in this particular zone.
The first point is reserved as the winked point to be controlled
by the wink off and wink on commands.
Runtime (RT)
The runtime editor is available in all controllers. This point exten-
sion can be used with DI, DO, and DC points.
Use this extension editor to define runtime parameters for a
discrete input or output point so that daily runtime information
can be collected. This information can then be used in SevenTrends
reports.
The field entries for the runtime editor are described below:
On state A 0 (open) or 1 (closed) that indicates the ON
state for this point. This determines when runtime data is
accumulated for this point.

Point Extensions Temperature Control (TC)
Runtime accumulator (PI point) The name or address of

the internal PI point (this type of point is reflective) collecting
perpetual runtime data for this discrete point. This accumu-
lator point collects runtime in hours.
This perpetual runtime accumulator is not reset at midnight.
Instead, it is reset by the next entry, Reset Mode.
Reset mode The reset mode resets the internal runtime
accumulator (PI point) you just defined (not the runtime
value of the discrete point to which this runtime extension is
attached). There are three reset mode options: None,
Constant, and Point.
If you select None, the data will accumulate runtime data
forever, or until you manually reset the point.
If you select Constant for the reset mode, enter the
number of hours (065,535) the internal PI point accu-
mulates data before being reset. When the discrete point
has been running the number of hours you specify here,
the internal PI point automatically resets to 0.
If you select Point for the reset mode, enter the name or
address of a discrete point which resets the internal PI
point when it transitions from the 0 state to the 1 state.
Temperature Control (TC)

The temperature control editor is available in all controllers. This
point extension can be used with DO and DC points. Temperature
Control is an application program that lets you do the following:
Provide the traditional red wire control of packaged rooftop
HVAC units.
Provide optimized start, optimized stop, optimized duty
cycling, night setback/setup control, and demand tempera-
ture override control of HVAC units.

Temperature Control (TC) Point Extensions

Temperature control commands are issued and reinforced by the
controller every 60 seconds, at the rollover of the minute in the
DCU.
Detailed information concerning the equations and logic for
temperature control can be found in Chapter 8, Dynamic Control.
The field entries for the temperature control extension are
described below:
Outside air temperature The point name or address for
the outside air sensor. This address can be an external,
internal, or indirect point address. This entry is mandatory if
optimized start/stop is used, otherwise its use is optional.
Space temperature The point name or address for the
space sensor. This address can be either an external, internal,
or indirect point address. This entry is mandatory.
Note: The two lookahead entry fields below are used for adaptive optimiza-
tion (OSTART and OSTOP), a function that monitors HVAC system
performance to determine when to begin optimized start or stop
actions. These functions require an ATS extension on the output
point.
Optimized start lookahead The number of minutes (0

480) for the maximum optimized start lookahead time. A 0
entry means that Ostart does not take place: the unit is turned
on at the start time you entered in the time scheduling (TS)
editor. Ostart causes the controller to start the HVAC unit at
the latest possible moment and still reach the target occu-
pancy temperature. The number you enter here is the
maximum length of time before the target occupancy time
that the HVAC unit is allowed to turn on. If the HVAC unit
can heat/cool the room in less time than the number of
minutes specified, it will do so. If it needs more time than the
number of minutes specified, it will not reach the target
temperature by the target occupancy time. Ostart should only
be used for the first start command of the day. The Ostart
command cannot be optimized back farther than midnight.

Note: The space temperature must meet the cooling/heating target temper-
ature sometime after the optimized start time, in order for Ostart to
work properly. This is required before the Start Performance
Constant calculation can begin its minutes/degree processing. The
optimized start command will not begin to advance the start time
until this calculation occurs.
Optimized stop lookahead The number of minutes (0

480) for the maximum optimized stop lookahead time. A 0
entry means that Ostop does not take place: the unit turns off
at the STOP time you entered in the time scheduling (TS)
editor. Ostop causes the controller to stop the HVAC unit at
the earliest possible minute and still stay within the differen-
tial until the end of occupancy time. The number you enter
here is the maximum length of time before the end of the
occupied period that the controller will control the HVAC
unit off. This number does not affect the Ostop process unless
it is less than the maximum time the unit can be off and still
maintain the target occupancy temperature until the end of
the occupied period. In this case the unit is not operating at
peak efficiency because it is prevented from shutting off at the
earliest possible moment.
Demand temperature override This function gives you
the opportunity to override demand control you have in
effect for this point. If you enable this function, this point
ceases to respond to demand control in certain circumstances.
It will not shut off or be shed by the demand program
according to its assigned priority level (06) when the space
temperature is outside its differential. When the space
temperature is higher/lower than the setpoint plus/minus the
differential, the priority of this point is automatically changed
to the highest demand shed level (emergency priority 7). This
prevents the point from being turned off except under emer-
gency demand conditions. Within priority 7, the point is
further prioritized based on its demand editor load priority
(7AF); e.g., a priority 3 point becomes a priority 7C. The
point is (re)assigned its normal priority (06) when the
temperature is within its differential.

Temperature Control (TC) Point Extensions
In this case, temperature control overrides demand control

only until the temperature moves within the differential.
Then demand control takes priority and will shut off the
point if necessary. If the temperature moves outside the
differential after the demand program controls the unit off,
the temperature control function controls the unit back on
after observing the minimum off time: defined as either the
minimum trip or close time in the resident I/O points editor
(depending on which control command is the off state). Refer
to Demand Control (DC) on page 7-18 for more informa-
tion.
Target Use these fields to define the target temperatures
for the HVAC unit controlled by this output point.
Cooling This is the cooling temperature the unit
attempts to reach and maintain when you issue a START
command to the output point. This is also the target
temperature at occupancy time used by the OSTART
command (in the ATS editor).
Setup This cooling temperature setpoint is only rele-
vant when the output point has been issued a STOP
command.This is the high limit setpoint for this system
when the space is unoccupied, typically at the end of the
day. If the temperature rises above this setpoint (+ the
differential) the HVAC unit controlled by this point turns
on until the temperature is once again below the setpoint
( the differential). The setup target is irrelevant to a
cycle since it only comes into play when the point is
issued a stop command.
Heating This is the heating temperature the unit
attempts to reach and maintain when you issue a START
command to the output point. This is also the target
temperature at occupancy time used by the OSTART
command.
Setback This heating temperature setpoint is only
relevant when the output point has been issued a STOP
command.This is the low limit setpoint for this system
when the space in unoccupied, typically at the end of the
day. If the temperature drops below this setpoint ( the
differential) the HVAC unit controlled by this point turns

on until the temperature is once again above the setpoint

(+ the differential). The setback target is irrelevant to a
cycle since it only comes into play when the point is
issued a stop command.
Note: If the device has both heating and cooling setpoints, a mode decision
(heating vs. cooling) is made automatically, based on the position of
the space temperature as compared to the setpoints. If the space
temperature is below the heating setpoint, the mode is selected as
heating; if the space temperature is above the cooling setpoint, the
mode is selected as cooling.
Caution: The heating setpoint may never be greater than the cooling setpoint.
There must be a deadband area (0.5 minimum) of no control
between the heating and cooling zones, so that the controller is aware
of the transition from heating to cooling or vice versa. The heating or
cooling zone range is defined as the target of the differential
range. This applies to both heating and cooling ranges.
Differential Use these fields to define the degree of preci-

sion you feel is necessary for temperature control. A differen-
tial is the temperature range over which no action takes place.
When using the temperature control editor, the sum of any
setpoint and one-half its differential must not be less than
zero or greater than 127.5. The temperature is allowed to rise
or fall unchecked until it reaches the limits of the active
setpoint plus or minus one-half the differential. In a situation
where temperature is critical (e.g., an operating room or a
laboratory containing delicate instruments), you want a very
small differential. In a situation where exact temperature is
less important (eg.,a shipping/receiving area or an unoccu-
pied office complex), you want a larger differential. A larger
differential means that the equipment is turned on and off
less often, saving energy and money. You must weigh this
against the temperature needs of the people, plants, and
equipment in your facility.
To determine the actual temperature control range, divide the
differential in half to determine the degree of separation from
the setpoint. Subtract one-half from the target temperature.
For example, if the cooling target is 75 degrees and its associ-

Trend Sampling (TR) Point Extensions
ated differential is 4, the measured temperature must rise

above 77 degrees before the temperature control editor
controls the unit on (call for cooling). The temperature must
fall below 73 degrees before the temperature control editor
controls the unit off. This creates an actual temperature range
between 73 and 77 degrees.
Do not define a differential if this point is being controlled by
Ostart or Start and the unit needs to run continuously. Also,
do not define a differential if a point is being controlled by a
Cycle or Ocycle command. Entering a differential ignores the
cycle adjustment multiplier, causing the unit to cycle on and
off according to the temperature rather than cycle.
Cycle adjustment This value determines the minutes per
degree adjustment to be made to the Ocycle pattern of an
HVAC unit controlled by this point. If you enter a 2 for the
cooling cycle adjustment, this indicates the load is turned on
an additional two minutes every cycle (defined in the ATS
editor) for each degree the actual space temperature is above
the cooling setpoint. The opposite applies for a heating cycle
adjustment entry. In this case the unit is turned on an addi-
tional two minutes every cycle for each degree the actual
temperature is below the heating setpoint. Do not enter a
value in this field if you have defined a differential in the
previous field.
Trend Sampling (TR)

The Trend Sampling editor is available in all controllers. This point
extension can be used with all points.
Every Trend Sampling extension requires 27 bytes of overhead plus
one byte for every discrete sample required, and 2 bytes for every
analog sample. For example, if you add Trend Sampling to a DO
point with the maximum number of samples (1440), then you have
consumed 1,467 bytes of controller memory. Be careful when
selecting the number of samples in the Trend Sampling editor,
because you may end up using a great deal of DCU memory.

Point Extensions Trend Sampling (TR)
Assign this extension to a point if you want to collect data to be

used in a graph or printed in a SevenTrends report. This editor lets
you determine how often and when to sample the point. You may
also specify the length of time between samples. This may be useful
if you wish to stagger multiple point sampling, point A at 8:00,
point B at 8:05, point C at 8:10, and so on.
The field entries for the trend sampling extension are described
below:
Cell sample count The number of samples (030) you

wish collected before the controller sends out a message indi-
cating that samples are ready for uploading. The number you
enter here cannot exceed one-half of the number you select
for the Number of Samples field (below). This number multi-
plied by the sample interval determines the frequency at
which sample data moves from the controller to a host work-
station. In an AD/AA system, SevenTrends data is moved
from the DCU to the workstation only if the workstation calls
the site, or the site calls the workstation.

Trend Sampling (TR) Point Extensions
Base time (hh:mm) The time used to synchronize the

sampling of data points. This entry is useful for synchronizing
multiple trend sample data points. The default base time is
00:00 (midnight).
Interval (minutes) The number of minutes (11,440) per
sample interval. This is the elapsed time between samples.
Number of samples The total number of samples (1
1,440) to be stored in the controller.
Caution: When this number is reached, the DCU discards the oldest trend
sample to make room for the newest sample. Make sure SevenTrends
data has previously been stored by the workstation to prevent loss of
data.
Sample control mode Use this field to coordinate trend

sampling with a designated time schedule or with another
point. The options here are None, Times, and Point. If you
leave the mode as None, the controller continually gathers
data at the specified sample interval. Time allows you to
define the time period during which data is collected. Point
allows you to collect samples from this point only when
another point is in the ON (1) state.
If you select Time for sample control mode, enter the
start and stop times in 24-hour format. For example, you
can use this option to limit data collection to occupied
hours.
If you select Point for sample control mode, enter the
name or address of the discrete point. For example, you
could use this option to collect temperature samples of
an AI point only when an associated fan (DO) point is
ON.
Note: This editor assumes a 1 to be the ON state. If the point has 1 as the
OFF state (0 as ON state), you must define an internal point
containing a simple negate calculation that reverses this, and use
the address of this internal point in the trend sampling editor. Refer
to Calculations (C) on page 7-4 for more information on calcula-
tions.

Point Extensions Time Scheduling (TS)
Time Scheduling (TS)

The time scheduling editor is available in all controllers. This point
extension can be used with DO and DC points only.
The time scheduling extension uses 9 bytes of memory for each
independent schedule, and 12 bytes of memory for each master or
slave schedule. Each action you include in a schedule requires 46
bytes, depending on the command.
This extension controls output points according to the schedule(s)
entered. Use this editor to create a schedule for any day of the week.
For example, you might have one schedule running Monday
through Friday and a different schedule in place for the weekends.
You may also create up to seven special day schedules (a holiday is
the most obvious example of a special day) and two temporary
schedules.
There are three schedule types: independent, master, and slave. An
independent schedule is used when the schedule applies to only
one point. A master schedule is used if the schedule is to be used for
several points. A slave schedule is used if this point is to follow a
previously-defined master schedule.
Schedule actions can be entered in random order, with no attention
to the chronological order of events. When you exit from the
schedule, the controller reorders the actions into chronological
order for independent schedules. Master and slave schedule actions
will remain in the order in which they were entered.
Independent and Master Schedules

The field entries for independent and master schedules are defined
below:
Action Select up to 17 actions for each schedule. Refer to
Table 7-6 for a list of valid action types. You can assign any or
all of these options to a regular weekday, a special day, or a
temporary schedule.
The optimized commands (Ostart, Ostop, and Ocycle) are
available for independent schedules only. Optimization for
master schedules is selected at the slave level.

Time Scheduling (TS) Point Extensions
Table 7-6. Independent/Master Schedule Actions
Field Description
This action energizes a point controlled by this schedule at the desired time of day. This
Start
action issues the first control command (0 or 1) of the point.
This action deenergizes a point controlled by this schedule at the desired time of day. This
Stop
action issues the second control command (0 or 1) of the point.
This action lets you select the time you wish duty cycling to start, and indicates the duty
cycle pattern (minutes off, minutes on) for the point controlled by this schedule. A duty cycle
pattern might be 10 minutes off and 50 minutes on. Once started, the cycle repeats
indefinitely until it is overridden by a start or stop command or another cycle command. The
stop command is always issued at the beginning of a cycle period, followed by the start
command.
Cycle
Room temperature is not a factor in a cycle. A cycle turns a point on or off regardless of the
current temperature. The advantage of a cycle command is that it gives you the opportunity
to save energy and money by staggering the on and off times of different pieces of
equipment. If everything comes on at once, this creates a surge in your energy demand and
costs you money. Staggering times decreases the total energy demand at any given time
and can save you money.
Optimized Start is a special start command related to room temperature and outside air
temperature. When you use optimized start, the time you enter is actually the target
occupancy time. The system actually starts up the device before this time in order to achieve
the desired temperature at the target occupancy time. The target temperature information
Ostart
is defined in the temperature control extension editor. Refer to the section on Temperature
Control (TC) for detailed information on target temperature selection and scheduling. Refer
to Temperature Control in Chapter 8, Dynamic Control, for additional information on actual
optimized start operation.
Optimized Stop is a special stop command related to room temperature. When you use
optimized stop, the time you enter is actually the target vacancy time. This lets the system
shut off an HVAC unit while the room is still occupied but maintain the desired temperature.
Ostop
This saves the energy (and dollars) required to run the fan or HVAC unit for the extra minutes
involved. Refer to Temperature Control in Chapter 8, Dynamic Control, for additional
information on actual optimized stop operation.
Optimized cycling retains the advantages of regular duty cycling but gives you some control
over room temperature. You define the cycle start time and number of minutes off and on
just as you do for a normal duty cycle. Optimized duty cycling shortens the off time of the
cycle and lengthens the on time of the cycle if the temperature deviates from the target
temperature defined for the point. The target temperatures and cycle modifiers are entered
Ocycle in the temperature control extension editor.
The time subtracted from the off portion of the cycle is added to the on time. This keeps the
total cycle time the same no matter how great the temperature deviation and the resulting
compensation. This is important in maintaining a staggered order of on/off times and the
resulting energy savings. If the temperature drifts from the target enough, the point
ultimately remains ON: cycle ON time equals the maximum and cycle OFF time equals zero.

Time Each action must have an associated time defined.

The options are Time, Sunrise, and Sunset. Time is entered in
24-hour format. Sunrise and sunset are calculated from the
latitude, longitude, and time zone you entered in the
controller configuration editor, and from the daylight savings
setting entered in your Windows system date/time setup. This
option is typically used to control outdoor lights (on at
sunset, off at sunrise).
Cycle off/on times These fields are active only when you
select Cycle or Ocycle as the action. These fields represent the
minutes (1127) the device controlled by this point is OFF
and ON per cycle period. The off command is always issued at
the beginning of a cycle.
Days of the week The days of the week are listed from left
to right. Enable the appropriate column(s) to perform an
action on a specific day.
As an example, say you have a start and a stop action that you
want to occur Monday through Friday. You enable the five
columns (MO, TU, WE, TH, FR) on the line containing the
START command, and again on the line containing the STOP
command. Make sure the columns you enable correspond to
the desired action and day of the week. If you want different
start/stop times on the weekend, you must define additional
start/stop actions with the appropriate times, and enable the
corresponding rows in the Saturday and Sunday columns. You
may define more than one start, stop, or cycle command for
any given day, up to a total of 17 different actions per
schedule. Your individual facility needs are the limiting factor.
Special days These fields are located to the right of the
weekdays. They are labeled S1 through S7. A special day (typi-
cally a holiday) is a schedule consisting of the starts, stops,
and cycles you want to occur on the special day. For example,
you want a start and a stop to occur on special day 1 (S1). You
would define the start and stop times and then enable both
the start and stop rows in the S1 column. You can define addi-
tional starts, stops, or cycles for any special day. The actual
dates for the special day schedule(s) are entered through the

Time Scheduling (TS) Point Extensions
special days editor. Refer to Special Days in Chapter 5,

Controller Functions. Special days override normal (Sunday
through Saturday) schedules.
Temporary schedules Define a temporary schedule as
you would any other schedule by defining the starts, stops,
and cycle commands you want to occur. You can define a
temporary schedule up to one week in advance.
Once you have defined a temporary schedule, move to
the top row where the action defined is Temporary. This
row contains an N (no) in each weekday column. The
other options are 1, 2, and B. Select 1 for temporary
schedule one, 2 for temporary schedule two, and B for
both temporary schedules.
Once the day containing the temporary schedule is over
(at midnight), the temporary schedule indicator (flag)
disappears. If you want a different temporary schedule
you need to redefine one of the two available temporary
schedules. Temporary schedules override both special
days and normal (Sunday through Saturday) schedules.
Slave Schedule
You must enter a master schedule before you can enter any slave
schedules. When you enter a slave schedule, you must specify which
master schedule it will follow. The slave and master schedules must
reside in the same controller.
The action lines in the slave schedule match those in the master
schedule, by line number. The master schedule actions and times
will appear on the screen, but you will not be able to change them.
The slave schedule mirrors, optimizes, or ignores a particular line
of the master schedule, regardless of which action is currently on
that line. You may enter an adjustment, so that the equipment
starts and stops will be staggered.
Note: Keep track of which actions are on which lines in the master schedule.
This is especially important any time you modify an existing master
schedule.
The field entries for slave schedules are defined below:

Reaction Select the action the slave schedule will take,

relative to the matching line number in the master schedule.
Select Mirror, Optimize, or Ignore.
Ignore causes the slave point to ignore or skip the speci-
fied action.
Mirror causes the slave point to copy the specified action.
Optimize causes the slave point to optimize the start,
stop, or cycle action defined in the master point. Refer to
the descriptions of the Ostart, Ostop, and Ocycle
commands in Table 7-6, Independent/Master Schedule
Actions, on page 7-48.
Adjustment Select a time adjustment for the slave action,
in minutes (127 to 127). This causes the action to occur
sooner or later than the time you defined in the master
schedule. A negative number causes an action to take place
earlier than the indicated (master schedule) time; a positive
value causes the action to take place later than the indicated
(master schedule) time. The adjustment field is not applicable
if you have entered an Ignore in the reaction field because an
Ignore causes the system to skip the entire command, regard-
less of any adjustments made to it.

CHAPTER
8
24
Dynamic Control
Three DCU application programs are used to control discrete

output points: temperature control (TC), demand control (DC),
and time scheduling (TS). They are grouped together because they
are the only DCU programs whose control decisions are interde-
pendent.
A single discrete output point may have one, two, or all three of
these programs affect its state. That being the case, it is important
to note that the final control decision will be made based on the
following hierarchy:
Time scheduling has the lowest priority. The time scheduling
decision takes place only when not countermanded by either a
temperature control or demand control decision.
Temperature control has the middle priority. The tempera-
ture control decision takes precedence over the time sched-
uling decision, but can be overridden by a demand control
decision.
Demand control has the highest priority. The demand control
decision always takes precedence over temperature control
and time scheduling.
Note: For discrete output points which have temperature control or

demand control defined but have no time scheduling defined, the
point is considered to be in the On state. It is prudent to define a time
schedule when using either of these programs.
This chapter discusses the underlying logic and processing of these

editors. Refer to the appropriate sections in Chapter 7, Point Exten-
sions for detailed information on selecting and using these editors.

Time Scheduling Dynamic Control
Time Scheduling
The purpose of time scheduling is quite simple: turn a point on, or
off, based on the time of day and day of week. Two different editors
are used to input time scheduling information: Time Scheduling
and Special Days. The Time Scheduling editor schedules day-to-
day control activities, and sets alternate schedules for later use. The
Special Days editor is used to temporarily replace the normal
schedule for specific dates with special days schedules (defined in
the Time Scheduling editor).
There are three types of schedules: master, slave, and independent.
A master schedule can also be used as a base schedule by other
points.
A slave schedule follows a specific master schedule, but allows
you to define an offset period for each action, or even ignore
the action entirely.
An independent schedule is used only for a particular point:
its control decisions are not based on the schedule of any
other point.
A schedule is assigned to a specific point. Each of the schedule types
(master, slave, and independent) also allow you to enter actions
and times for alternate schedules.
Time Scheduling Editor

In this editor the operator assigns a schedule to a point. Each
schedule permits you to define times at which the point is to be
turned on or off, or turns on and off on a cyclical basis.
The operator can also enter alternate schedules for the point. There
are two types of alternate schedules: temporary schedules that will
be used once and then erased, and special day schedules that may
be used repeatedly.
Normal Schedules
You may define up to 17 actions and times for each point, based on
the day of the week. This day-to-day schedule is referred to as the
normal schedule for the point.

Dynamic Control Time Scheduling
Note: The operator may decide to control a point based on the time at
which sunrise or sunset occurs. The time of sunrise and sunset are
functions of latitude, longitude, deviation from Greenwich Mean
Time (GMT), and daylight savings time entries. These parameters
must be entered for each DCU, in the DCU Configuration/Summary
editor.
Temporary Schedules
This feature permits the operator to override the normal schedule
for one or more days, up to one week ahead. For example, you may
need to operate your facility on a day it is normally closed.
Two temporary schedules are provided. You may select either, or
both, temporary schedules for any particular day. A temporary
schedule flag (1 = schedule 1, 2 = schedule 2, B = both) indicates a
temporary schedule assignment.
Note: The temporary schedule flag will disappear once it has been
processed.
Caution: Temporary schedule flags are not saved or restored as part of the
DCU database. If the DCU database is restored, any temporary
scheduling flags will be erased.
Special Day Schedules

Special day schedules are used for alternate schedules that will be
used several times during the year. For example, you may set up a
standard holiday schedule. Special day schedules are not erased
after processing, allowing you to use them repeatedly. Special day
schedules are entered in the same way as normal schedules.
Note: It is recommended that you populate special day commands for all
special days, especially for points that are to be turned on during a
special day period.
The Time Scheduling editor defines the schedule for the special
day; that is, it specifies what commands will be processed when a
day is designated as a special day. The Special Days editor actually
specifies when the special day schedule will be in effect.

Time Scheduling Dynamic Control
Special Days Editor

This editor defines the time period(s) during which the special day
schedule (entered in the Time Schedule editor) will replace the
normal schedule. When the DCU determines that it has entered a
special day period, it searches all of the points for which time
scheduling has been defined and replaces the normal schedule with
the appropriate special day (S1S7) schedule.
Caution: If a particular point has no special day information defined, then the
point will stay in its last commanded state for the duration of the
special day period; it will not maintain its normal schedule. For
example, a point is turned on at 08:00 and off at 17:00 every
weekday. The DCU enters a special day period at 00:00 on a Monday.
This point has no special day information defined for it. This point
would stay off Monday since its last commanded state (on the
preceding Friday) was off.
Processing
Control decisions for time scheduling are made on the minute
change in the DCU, but are NOT reinforced every minute.
Time schedules are reinforced in a DCU via a look-back to
midnight routine which is invoked in the following cases:
1. A time schedule is modified or added.
2. The DCU is reset either via a power restoration or through
pressing the DCU reset button.
3. The time scheduling program is turned on via the DCU
Configuration/summary editor. The time scheduling
program can also be turned off via the same editor, thus
causing all points under time scheduling control to remain in
their last commanded states.

Dynamic Control Temperature Control
Temperature Control
Temperature control provides control of discrete points based on
up to 4 different setpoints: Normal Cooling, Normal Heating, Set
Up Cooling, and Set Back Heating. The setpoints are invoked based
on the time schedule assigned to the same point and the mode
(cooling or heating) that is applicable.
Temperature control provides adaptive optimized start and stop
functions which, based on historical building characteristics, turn
equipment on/off before scheduled start/stop times to maintain
building comfort while maximizing energy savings. Temperature
control also provides an optimized cycling function which
lengthens the On portion of a cycle based on a desired setpoint.
Temperature Control Editor

The temperature control function will:
Energize the point if the space temperature is below the
heating or setback setpoint minus half the differential or if the
space temperature is above the cooling or setup setpoint plus
half the differential.
De-energize the point if the space temperature is above the
heating or setback setpoint plus half the differential or if the
space temperature is below the cooling or setup setpoint
minus half the differential.
Reinforce the same command to the output if the tempera-
ture has not changed by more than one degree or if the
temperature is within the differential.
The temperature control program is based on 8-bit integer arith-
metic, the ramifications of which are:
1. Any setpoint may vary from 0 to 127 inclusive.
2. Any setpoint and its differential added together cannot exceed
128.
3. Negative setpoints are not possible.
4. Setpoints with decimal portions are not possible.

Temperature Control Dynamic Control
Equations
The equations stated below define the action of the output when
using temperature control.
Heating (Normal/Setback)
Vn = [T < HSP D2] OR [Vn1 AND (HSP D2 < T < HSP + D2)]
Cooling (Normal/Setup)
Vn = [T > CSP + D2] OR [Vn1 AND (CSP D2 < T < CSP + D2)]
where:
Vn = the controller output at the nth sample. The output is ON if the

Boolean expression is true; OFF if otherwise.
Vn1 = the controller output at the sample n1 (on=1/off=0).
T = space temperature.
CSP = cooling setpoint in effect (normal or setup).
HSP = heating setpoint in effect (normal or setback).
D = differential associated with setpoint in effect.
Temperature control operates on up to four different setpoint

temperatures, depending on the time schedule for the target point.
The four target temperatures are as follows:
1. Normal cooling
2. Setup cooling
3. Normal heating
4. Setback heating
The normal versus setup/setback decision is based on the time
schedule for the point. Normal is selected when a point is scheduled
On; Setup/setback when a point is scheduled Off (during duty
cycling temperature control is disabled). The operator can individ-
ually enable and disable actions, based on any of these setpoints.

Mode Selection
If the device has both heating and cooling setpoints populated, the
temperature control function selects the mode (heating or cooling)
automatically, based on the position of the space temperature as
compared to the setpoint(s).
If the space temperature is below the active heating setpoint,
the mode is selected as heating.
If the space temperature is above the active cooling setpoint,
the mode is selected as cooling.
Note: The heating setpoint(s) may never be greater than the cooling
setpoint(s).
Caution: The heating setpoint plus 12 of its differential may never overlap the
cooling setpoint minus 12 of its differential.
Optimization
Actions in an independent or slave schedule may be optimized to
save energy and money. (Master schedules are optimized only
through related slave schedules.) Optimization is a special function
that uses the Temperature Control and Time Control editors in
tandem. An action is specified as an optimization in the Time
Schedule editor.
Optimized Cycle
The objective of optimized cycling is to increase the On time of a
cycle period in order to compensate for temperature differences
from the setpoint. The following information must be provided:
Cooling and heating setpoints. These elements are entered in
the Temperature Control editor.
Note: Cooling and heating setpoints affect all temperature control actions
for that point, not just optimization.
Optimized Cycle action. This tells the time schedule and

temperature control functions that this cycle will be opti-
mized. This action is entered in the Time Schedule editor.

Cycle ON time. This is the minimum number of minutes the

point will be energized in a cycle. This element is entered in
the Time Schedule editor.
Cycle OFF time. The is the maximum number of minutes the
point will be deenergized in a cycle. This element is entered in
the Time Schedule editor.
Cycle adjustment multiplier. Cycle adjustment is in minutes
per degree. This is the number of additional minutes to
increase the On time for this cycle, for each degree of temper-
ature difference between current temperature and setpoint
temperature. This element is entered in the Temperature
Control editor.
For combined heating and cooling devices using optimized cycling,
temperature control uses the mode selection process to determine
whether to optimize to the heating or cooling setpoint.
Note: The cycle period itself is never disregarded. The fact that a points
cycle periods remain synchronized is very important when using this
function in conjunction with demand limiting.
Optimized Start and Stop

Optimized start and stop actions involve four elements: target
temperature, target time, performance constant, and lookahead
time.
Target temperature is the inside temperature you wish to
achieve. This is entered in the Temperature Control editor as
the Cooling and Heating setpoint(s).
Note: Cooling and heating setpoints affect all temperature control actions
for that point, not just optimization.
Target time is the time by which you wish to reach the speci-
fied temperature. The target time is entered in the Time
Schedule editor, as the time for the optimized action.

The performance constant is an internal calculation. The

DCU calculates the rate of change in temperature, in minutes
per degree. In this way, the system determines when it will
need to perform the optimized action in order to reach the
target temperature by the target time.
The performance constant for optimized start is the
average of the actual minutes per degree achieved during
the last three days of optimized start commands.
The performance constant for optimized stop command
is the actual minutes per degree achieved during the last
stop command.
Note: The performance constant can only be calculated if the space reaches
the target temperature during normal operating times. An optimized
start or stop action cannot take place until this target temperature is
achieved.
Lookahead time tells the system when to start checking the

current status (inside temperature and outside temperature)
against the performance constant and target temperature, to
see if it needs to perform the action yet.
Lookahead time is entered in minutes, as an offset to target
time. This is entered in the Temperature Control editor. Sepa-
rate lookahead times are entered for optimized starts and
optimized stops. The DCU will evaluate the conditions every
minute of the lookahead time.
Note: If the lookahead time is insufficient, it may not be possible to reach

the target temperature by the specified time.
For example, suppose you wish your facility to have an inside

temperature of 70F by 8:00 a.m., when the workers arrive. You
have set the lookahead time to 120 minutes (2 hours). The system
will start checking outside air temperature, space temperature, and
the performance constant (minutes/degree) at 6:00 a.m., to deter-
mine whether the heating or cooling should be started. This will
continue every minute, until the equipment is energized.

Optimized Start Calculation

The computer performs the calculations and acts as necessary to
start the device at the latest possible time and still reach the normal
heat/cool temperature setpoints by the scheduled On time. Under
no circumstance will optimized start advance the schedule before
midnight of the current day.
The calculation for an optimized start command is:
TimeOstart [ ( | TSpace TTarget | + | TSpace TOutside | ) CPerf ]
where:
TimeOstart = time entry for the optimized start command

TSpace = space temperature
TTarget = target temperature
TOutside = outside temperature
CPerf = performance constant
For combined heating and cooling devices using optimized start,

temperature control uses the mode selection process to determine
whether to optimize to the heating or cooling setpoint.
Optimized Stop Calculation
The computer performs the calculations and acts as necessary to
stop the device at the earliest possible time and still maintain the
normal heat/cool temperature setpoints up to the scheduled Off
time. Under no circumstance will optimized stop advance the
schedule beyond midnight of the current day.
The calculation for an optimized stop is:
TimeOstop [ | TSpace TTarget | CPerf ]
where:
TimeOstop = time entry for the optimized stop command

TSpace = space temperature
TTarget = target temperature
CPerf = performance constant

For combined heating and cooling devices, optimized stop is not

performed. Optimized stop is only performed for heating only or
cooling only devices. This is due to the fact that temperature
control has no means of knowing which normal setpoint to use,
since optimized stop is only used when the space temperature is less
than the normal cooling temperature setpoint or greater than the
normal heating temperature setpoint.
Demand Control Override

Finally, temperature control allows you to assign a demand over-
ride feature to the point. This function is used for points which are
subject to demand control shedding. This feature causes the point
to become a demand priority 7 when it is On due to the space
temperature being outside its setpoint plus/minus its differential.
These points (loads) are not shed until an emergency demand is
predicted. Once the space temperature returns to within its
setpoint plus or minus its differential, the point (load) returns to its
assigned priority level (06).
Processing
The processing of points assigned to temperature control is based
on whether the point is being controlled to a heating/cooling
setpoint or if it is being controlled to a cycling setpoint.
If a point has started to control to a heating/cooling setpoint
(a scheduled On, Off, Optimized Start, or Optimized Stop)
and a differential has been assigned, then temperature control
decisions are made on the minute change in the DCU, and
reinforced every minute thereafter.
If a point is being optimized to control to a heating/cooling
setpoint (a scheduled Optimized start or Optimized stop) and
no differential (zero) has been assigned, then no temperature
control decisions are made by the Temperature Control
editor.
If a point has started to control to a cycling setpoint (a sched-
uled Optimized Cycle), then temperature control decisions
are made at the scheduled time, and are reinforced every
minute thereafter.

Demand Control Dynamic Control
Demand Control
The demand program monitors the consumption of electrical
power. Demand control allows you to:
Monitor daily KWH consumption The daily KWH
consumption total, daily peak KW demand, and time of daily
peak KW demand are automatically recorded in the specified
SevenTrends table.
Maintain a monthly total of KWH consumption You may
specify a point to accumulate a monthly consumption total.
Monitor demand You may specify a point to reflect current
KW demand. This point may then be placed on system pages,
as a display value.
Turn off (shed) loads An important part of demand
control is the ability to shed loads, which are discrete output
(DO or DC) points, in order to prevent the actual demand
from exceeding a specified target. Load shedding takes place
according to a priority arrangement with some loads being
shed before others, and can be limited in time to avoid
damage to equipment or unwanted effects on the environ-
ment.
See Also: Demand Control (DC) in Chapter 7, Point Extensions

The following parameters are components of demand control
processing:
Demand meter This is the PI point that is connected to the
actual meter. Set the demand control extension on this point
to accumulate daily consumption, in kilowatt-hours (KWH).
This accumulator is automatically reset to zero every night at
midnight.
Demand interval This is the unit of time, in minutes, over
which demand calculations are made (preferably set to match
the interval set by the local power-generating public utility or
distribution authority). This information can be provided by
your local utility company.

Dynamic Control Demand Control
Conversion coefficients The slope (m) conversion coeffi-

cient for the demand meter (PI) point is used to calculate the
consumption. This value should convert the incremental
counts (pulses) into kilowatt-hours (KWH). The intercept (b)
conversion coefficient should be set to zero (0). These param-
eters are selected in the Resident I/O points editor for the
demand meter (PI) point, and entered in the Station Parame-
ters editor.
Shed levels You must define the maximum demand level
(in KW) for three conditions: Normal shed level, Emer-
gency shed level, and Override shed level. The shed levels
determine when loads will begin to be shed. Each shed level
can be entered either as a point or a constant. If it is a
constant, shedding begins when the projected demand
exceeds the entered value. If it is a point, shedding begins
when the projected demand exceeds the value of the specified
point. Shed levels are described in detail in Demand Meter
in Chapter 7, Point Extensions.
Shed differentials For each shed level (see above), you
must also define a Shed Differential. This is the size (in KW)
for the deadband between shedding and restoring. Shed loads
will not be restored until the projected demand is below the
shed level by at least the amount of the shed differential. This
prevents the system from restoring loads, only to find that it
once again needs to shed loads to remain below the shed level.
This parameter is entered in the Demand Control editor for
the demand meter (PI) point.
Current demand This is an optional internal point that
you may define to display the current equipment demand, in
kilowatts (KW). This allows you to display and view the actual
current demand, in addition to the daily accumulation stored
in the demand meter (PI) point. The Current demand point
may be either a PI or an AI point. The address of this point is
entered in the Demand Control editor for the demand meter
(PI) point. Trend sampling may be set for this point if reports
are desired.
Monthly consumption This is an optional internal point
that you may define to display accumulated monthly
consumption. The Monthly consumption point may be

either a PI or an AI. The address of this point is entered in the

Demand Control editor for the demand meter (PI) point. The
data will be collected until the date(s) entered in the Demand
Control editor for the demand meter. This point will be
zeroed out at midnight on the date(s) specified. Trend
sampling may be set for this point, if reports are desired.
Demand Loads Each load that may be shed must be identi-
fied in the demand loads portion of the Demand Control
editor for the demand meter (PI) point.
Note: Enter only the loads that may be shed. If the equipment controlled by
a point is critical, (i.e., you would rather go over the maximum KW
demand level than turn off the equipment) do not enter that point in
the demand loads portion of the Demand Control editor.
The demand loads information is used to determine which

loads to shed. Refer to Selecting Loads to Shed on page 8-21
for a discussion on how these decisions are made. The
following information is required for each load (DO or DC)
point:
Priority This is the priority level (07) for the load.
This is used to determine which loads will be shed most
often, all the way up to the loads to shed only in emer-
gency situations. This parameter is entered in the
demand loads portion of the Demand Control editor for
the demand meter (PI) point.
On You must specify whether the 0 state or the 1 state
is the On state for the load (DO or DC) point. This
parameter is entered in the demand loads portion of the
Demand Control editor for the demand meter (PI) point.
Load size The energy draw for the load (DO or DC)
point, in kilowatts (KW). This parameter is entered in
the demand loads portion of the Demand Control editor
for the demand meter (PI) point. Refer to Demand
Loads in Chapter 7, Point Extensions for information on
calculating this value.

Max off time The maximum time that this load may
remain Off due to shedding. Note that this does not
affect the scheduled On and Off times for this point. This
parameter is entered in the demand loads portion of the
Demand Control editor for the demand meter (PI) point.
Minimum off time The minimum time this point
must be off before it may be turned on. This entry is very
important, to allow the equipment adequate shutdown
time between uses. This parameter is entered in the Resi-
dent I/O Points editor for the load (DO or DC) point.
Minimum on time The minimum time this point
must be on before it may be turned off. This entry is very
important, to prevent short-cycling the equipment. This
parameter is entered in the Resident I/O Points editor for
the load (DO or DC) point.
SevenTrends tables If you wish to track consumption and
demand information for reports, you must define trends to
store the data, as follows:
Demand trend This trend will receive the daily
consumption information from the demand meter (PI)
point. The total daily consumption, daily peak demand,
and time of peak demand will be recorded. This trend
must be defined for the demand information to be avail-
able for reporting.
Analog Sample trends If you wish to track and report
current demand data, you must set the trend sampling
extension on the current demand point, and define an
analog sample trend to store the information. Likewise, if
you wish to track and report monthly consumption data,
you must set the trend sampling extension on the
monthly consumption point, and define an analog
sample trend to store the information.
Monitoring Consumption
The demand program uses input from the demand meter (PI)
point to calculate electrical consumption. The DCU takes the
starting value of the accumulator, and adds the incremental counts

it has sensed between point scans. This value is multiplied by the

conversion coefficient (m) specified for the point to obtain
consumption in KWH.
Two consumption values may be monitored: daily consumption
and monthly consumption. Daily consumption is monitored auto-
matically, as part of demand control. Monitoring monthly
consumption is optional.
Note: Upon database restoration, all accumulators are reset to zero. You
may wish to manually record all accumulator values before a data-
base restoration and reset the starting value(s) of the accumulator(s)
via the Test command after performing the database restoration. An
accumulator will not start collecting data until after the database
restoration is complete, therefore, any data changes which occur
during database restoration are lost.
Daily Consumption
The demand meter (PI) point will automatically collect the daily
consumption information. The program resets the value of the
accumulator to zero at midnight each day.
If a cell number is specified in the Demand Control editor, the daily
consumption information will be automatically routed to the trend
table at midnight. This allows you to store consumption informa-
tion for viewing and reporting purposes. The daily total consump-
tion, daily peak demand, and time of daily peak demand will be
recorded in the demand trend.
Monthly Consumption
An internal accumulator point may be defined to store the month-
to-date accumulation of electrical consumption. You may use
either an AI or PI point for this purpose (PI point recommended).
This function is commonly used to place month-to-date consump-
tion information on system pages.
In order for this function to work properly, the appropriate dates
must be entered in the Schedules portion of the Demand Control
editor for the demand meter (PI) point. The dates entered should
be the last day of each month. At midnight of the specified date, the
monthly consumption accumulator will be reset to zero.

Month-to-date information is not automatically sent to a Seven-

Trends table. If you wish to create reports for month-to-date infor-
mation, use the trend sampling extension on the monthly
consumption point, and define an analog sample trend to collect
and store this information.
Calculating Demand
The demand calculation is based on the electrical consumption
and the demand interval. The program measures the demand by
dividing the demand interval (entered in the Demand Control
editor to match the interval set by the local electric utility
company) into 10 equal time-based segments which we will refer to
as control periods.
control
demand interval period
{
}
control demand interval

period
Figure 8-1. Demand Interval and Control Periods
Two demand values are calculated: projected demand and current

demand. Projected demand is calculated automatically, as part of
demand control. Displaying the current demand calculated value is
optional.
Projected Demand
The projected demand is used to determine whether loads will
need to be shed in order to keep demand below the desired level.
(Refer to Demand Meter in Chapter 7, Point Extensions for a
discussion of shed levels.)
The projected demand calculation looks ahead in time and esti-
mates what the demand will be. During each control period (n), the
projected demand is calculated for the next control period (n+1).
This calculation is based on the consumption for current control

period (n) and the previous four control periods (n1, n2, n3,
and n4). These consumption values are used to predict the
demand for the next control period (n+1). See Figure 8-2.
current control period (n) demand will be predicted

for this control period (n+1)
a b c d e f g h i j
n4 n3 n2 n1 n n+1
control periods used in projected

demand calculation
In the current control period (f), the system will calculate the projected
demand for control period (g), using the demand from the current control
period (f) and the four previous control periods (be).
Figure 8-2. Time Periods for Projected Demand Calculation
Refer to Shedding Loads on page 8-19 for a discussion on how

this calculation fits into the load shedding process.
Current Demand
An internal accumulator point may be defined to store the current
electrical demand. You may use either an AI or PI point for this
purpose (AI point recommended). This function is commonly
used to place current demand information on system pages.
Note: You may wish to assign a high limit value to the current demand
input point. When an alarm is received for this point, this alarm
reflects the fact that the actual measured demand has exceeded the
value you have defined.
The current demand calculation is based on the last ten control

periods, for a full demand interval. This method of calculating the
demand is sometimes referred to as the sliding window tech-
nique.
At each control period (n), the consumption values (in KWH) of
the last ten control periods (n1, n2, n3, n4, n5, n6, n7,
n8, n9, and n10) are added together. The total consumption (in

current control period
a b c d e f g h i j k l m n o
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
control periods used to calculate current demand
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
Figure 8-3. Current Demand Calculation Sliding Window
KWH) is divided by the demand interval (in minutes), and the

result is multiplied by 60 to convert the value to KW. The equation
for this calculation is shown below:
Consumption ( kWh )- 60min
------------------------------------------------------- ----------------
Interval ( min ) hour
Note: When the demand program is first started, you must wait for one full
demand interval to pass before the reported current demand becomes
meaningful (see Table 8-1 on page 8-23).
Shedding Loads
The main purpose of the demand control function is to limit the
demand segment of the electric utility charges by limiting the
maximum KW draw. This limiting is achieved by automatically
and selectively turning loads off (i.e., shedding loads).

The operator may specify up to three demand target setpoints on

which load control decisions will be based. They are:
Normal Demand The normal demand setpoint is in effect
unless replaced by the override demand setpoint.
Override Demand The override demand target is used
when a specific condition is satisfied. Such conditions might
include: a utility company-specified higher or lower demand
tier during certain hours over certain days; unusually high
outside air temperatures; or some unusual condition within
the facility.
Emergency Demand The emergency demand is always in
effect and must be specified as the highest demand target.
Emergency demand determines when the highest priority
loads will be shed.
After the demand setpoints have been defined, the operator speci-
fies the discrete outputs (loads) that can be shed to avoid exceeding
the target demand. Each load is assigned a priority and a maximum
OFF time. The ON state and kilowatt rating are also entered for
each load.
Warning: As a minimum, you should use the rated KW value (normally found
on the motor nameplate) of the equipment when defining loads in
the demand program. An approximation is sufficient; an entry of
zero (0) is not. If you assign zero ratings to the loads, the demand
program will shed every 0 KW-rated load, then restore them the very
next control period.
The demand target differential prevents over correction (oscilla-

tion) from minor demand perturbations. If the predicted demand
stays within the differential (defined by the target minus the differ-
ential), loads will neither be shed nor restored. There is one excep-
tion to this rule: if a load has been shed for its maximum OFF time
it will be restored regardless of the effect on demand. However, if
the predicted effect is that the demand will exceed the target,
another load will be shed, even if the new load has a higher priority.

Control decisions for points assigned to demand control are made

every tenth of the demand interval, e.g., if the demand interval were
10 minutes, a control decision is made every minute. Control deci-
sions are not reinforced, but are issued only when a change of state
is to be made.
Selecting Loads to Shed
The following parameters are used to determine which loads to
shed: predicted demand, load state (on or off), minimum On time,
shed priority, and load kilowatt size. The selection process for load
shedding is as follows:
1. Determine the need for load shedding (predicted demand).
2. Determine the loads available for shedding.
3. Select the loads to be shed, based on shed priority and kilo-
watt rating.
Predicted Demand
In order to avoid exceeding the demand target, starting at the tenth
control period, the demand program predicts what the demand will
be in the next control period, based on the previous five control
period samples. If the predicted demand is greater than the target,
loads will be shed to reduce the demand below the target. See
Calculating Demand on page 8-17 for a discussion of the
predicted demand calculation.
Availability
When the demand program decides that shedding is necessary, it
looks at its list of loads and decides which one(s) are available for
shedding. To be available for shedding, the load must be on, and
must have met the minimum on time specified for the point.
Priority
Loads are assigned priorities which range from zero to seven. Loads
with a priority of zero (0) are shed first and restored last. Loads
with a priority of six are shed last and restored first. Loads with a
priority of seven are shed only when the predicted demand is
greater than the emergency demand setpoint and all lower priority
loads have already been shed.

Within a single priority, loads are shed and restored in a round-

robin fashion, i.e., first load that was shed will not be shed again
until other loads in that priority have been shed. However, loads
with a lower priority level may be shed and restored many times
before a load from the next higher priority is shed.
Kilowatt Rating
The program attempts to shed loads whose cumulative kilowatt
ratings equal that of the reduction needed, while shedding the
fewest number of loads possible.
Loads in the higher priority levels will not be shed unless all loads
in all of the lower priority levels have been shed, or are otherwise
not available for shedding (see Availability above).
Load Shedding Process
After determining the need for load shedding and the loads avail-
able for shedding, the program calculates the difference between
the predicted demand and the shed level setpoint. As it searches
through the loads available for shedding, it makes note of the
priority levels and kilowatt rating you have assigned each load.
Starting with the lowest priority level, loads are then selected for
shedding. The program will continue to shed loads until the
predicted demand falls below the setpoint, while selecting the
minimum number of loads possible.
If at any control period, the demand control program cannot shed
enough loads to meet the kilowatt reduction needed, then and only
then will it generate a Peak Demand Alarm message. The
predicted demand value will be reported, taking into account the
loads the program was able to shed.
Restoring Loads
If a load has been shed for its maximum off time it will be restored
regardless of the effect on demand. If the result is that the predicted
demand will exceed the target, another load will be shed, even if the
new load has a higher priority than the restored load.

If the predicted demand is less than the target minus the differen-
tial, loads are turned back on. For example, if the normal shed level
is set at 95 kilowatts and you define the differential as 5, the system
does not begin restoring loads until the predicted demand is less
than 90 kilowatts.
Loads are restored according to the following criteria:
1. Loads with the highest priority are restored first.
2. Within a priority, loads will be restored in the same order as
they were shed (i.e., the first load shed will be the first load
restored).
3. To be restored, a load must meet its minimum off time, as set
in the Resident I/O points editor.
4. The kilowatt rating of the load must be such that restoring the
load will not cause the demand to exceed the setpoint.
Measurement and Forecasting

In order to help you get a better feel for the demand program, the
following table illustrates KWH measurement, demand measure-
ment, and demand forecasting. The example data in Table 8-1 is
based on a demand interval of 10 minutes. A graph of these values
is shown in Figure8-4, Consumption and Demand.
Table 8-1. Consumption and Demand Data
Control Period Consumption (KWH) Demand (KW) Predicted Demand (KW)

a 0 0 N/A
b 50 300 N/A
c 52 612 N/A
d 53 930 N/A
e 52 1242 N/A
f 43 1500 N/A
g 54 1824 N/A
h 57 2166 N/A
i 58 2514 N/A
j 62 2886 N/A
k 65 3276 4330

Table 8-1. Consumption and Demand Data (Continued)
Control Period Consumption (KWH) Demand (KW) Predicted Demand (KW)

l 62 3348 3780
m 60 3396 3290
n 62 3450 3680
o 63 3516 3970
p 71 3684 4730
q 65 3750 4160
r 62 3780 3150
s 65 3822 3840
t 60 3810 3560
u 68 3828 4130
v 71 3882 4970
w 75 3972 4910
Consumption and Demand
10000
1000
100
10
Consumption, KWH
Demand, KW
1
Forecast Demand, KW
t10
t12
t14
t16
t18
t20
t22
t0
t2
t4
t6
t8
Tim e, m inutes ( Dem and Interval = 10)
Figure 8-4. Consumption and Demand

CHAPTER
9
92
Access Control
Note: The editors used for access control will not be available unless you
enable access control in the I/NET active configuration. Refer to the
I/NET Configuration chapter in TCON298, I/NET Seven Getting
Started, for more information.
I/NET readily supports integration of access control with energy

management. The system can trigger events or actions to occur
based on individuals passing through specific doors (or elevators)
at specific times. In this way, HVAC and lighting can be turned on
when tenants arrive in the morning, or key employees may have
their location displayed on a graphical floor plan.
The access control system requires hardware specifically designed
for access control. Individuals are issued a key or card that they
must use to gain access into controlled areas. Doors at the bound-
aries of controlled areas must have a key/card reader. This device
reads information encoded on a users key/card, identifies the user,
and passes this information to a door controller.
The door controller contains a database that is used to determine
whether or not to grant access to the individual. Access rights are
determined by the following database-stored information (defined
by the I/NET administrator):
Tenant, group, and individual access rights
Personnel schedules
Mode schedules
Zones and anti-passback (if implemented)
Floors (if using elevators)
If access is granted, the door controller releases the locking device
at the door. The locking device may be a door strike, electromagnet,
or any other electrically-controlled locking mechanism. If the door

Access Control Hardware Access Control
is actually an elevator, the door controller does not control a

locking mechanism, but rather, enables the floor selection buttons
that are authorized for the individual.
The door controller connects to the I/NET system through an
interface device. This interface may provide only access control
functions; or the device may also provide energy management
functions. Door controllers communicate with the interface device
through a subLAN. The interface device, in turn, communicates
with an I/NET host workstation over a controller LAN.
Access Control Hardware

Access Control is implemented in I/NET by using one or more
door controllers (DPUs and SCU1284s), and possibly one or more
Discrete Input Units (DIU7930s or SCU1200s) or Discrete Input
Monitoring and Output Control Units (DIO7940s or SCU1280s).
These devices are connected together on a subLAN and communi-
cate with other components of the I/NET controller LAN. SubLAN
Interface (SLI) controllers serve as a gateway between the subLAN
and the I/NET controller LAN. These specialized controllers
include the Model 7791 Door Processor Interface (DPI), the 7793
Micro Controller Interface (MCI), and the 7798 I/SITE LAN. See
Figure 9-1 for an example of I/NET subLANs.
The 7791 DPI supports up to 32 DPUs, SCUs, DIUs, or DIOs on a
single subLAN. The DPI maintains the complete database and
control parameters for all devices on its subLAN.
The 7793 MCI supports up to 32 devices (DPUs, SCUs, DIUs,
DIOs) on each of two subLANs. The MCI also supports Micro
Regulators (MRs) and Application Specific Controllers (ASCs)
mixed with the other devices. As with the 7791 DPI, the 7793 MCI
maintains the complete database and control parameters for all
devices on its subLANs.
The 7798 I/SITE LAN provides the same single-subLAN capabili-
ties as the 7791 DPI, but also allows a mix of Micro Regulators as
does the 7793 MCI. In addition, the 7798 allows some local control
and display capabilities using a built-in ViewCon panel. As with the

Access Control Access Control Hardware
LAN Tap
I/NET Controller LAN
DPI MCI DCU/PCU I/SITE LAN

A B
DPU DPU DPU DPU
DIU DIU DIU DIU
DIO DIO DIO DIO
MR MR MR
ASC ASC ASC
Figure 9-1. I/NET SubLANs
7791 DPI and 7793 MCI, the 7798 I/SITE LAN maintains the
complete database and control parameters for all devices on its
subLAN.
The DPI, MCI, I/SITE LAN, and DIO/DIU/DPU/SCU are the
devices that comprise the access control element of the I/NET inte-
grated system. Through these devices you may control or restrict
access to various areas of your facility. Using access initiated
control, you may tie access control events from DPU/SCU readers
to the facility management side of I/NET.
See Also: Chapter 7, Point Extensions

TCON109, 7790 LAN Interface Unit
TCON114, 7798 I/SITE LAN
TCON115, 7900 Door Processor Unit
TCON116, 7910A Door Processor Unit
TCON124, Discrete Input Unit 7930

Firmware-specific Parameters and Options Access Control
TCON125, Discrete Input Monitoring & Output Control Unit 7940

TCON312, 1200-series Security Control Unit
Firmware-specific Parameters and Options

Some I/NET editors used to configure your access control system
contain parameters and options that will differ, depending on the
firmware revision loaded within your systems controllers. The
editor descriptions within this chapter describe all parameters and
options that may be present. When applicable, these descriptions
include explanations of the system configuration required in order
for the parameter or option to be displayed.
Key/Card Numbers
Note: Only the SCU1284 and the DPU7920 (with installed DPU48K)
using revision 3.24 or later firmware have the ability to support up to
32,000 individuals per tenant. All other door controllers support up
to 24,000 individuals per tenant.
I/NET has the ability to support up to 32,000 individuals per

tenant. Traditionally, I/NET has required that the key/card number
assigned to an individual match the individual number. For
example, key/card number 10 would be issued to individual
number 10. Therefore, key/card numbers would be in the range of
1 to 32,000. However, it is not uncommon to find that the actual
number preprogrammed on a key/card is greater than 32,000. In
order to accommodate these larger key/card numbers, I/NET has
the ability to translate large key/card numbers directly to individual
numbers. This can be done as simply as assigning a large key/card
number directly to an individual, or you can use a Key/Card Trans-
lation table to translate ranges of key/card numbers. Using a trans-
lation table, you can define up to 128 ranges of large key/card
numbers and the starting target number (1 to 32000) for each
range (refer to Key/Card Translations on page 9-58 for more
information).

Access Control Key/Card Numbers
Large Number Support

The I/NET system is capable of translating large key/card
numbers (i.e., numbers greater than 32,000) directly to a lower
number, without the use of the Key/Card Translation table.
However, this functionality requires that the SLI and door
controller binary loads are I/NET 2000 revision 2.x or I/NET Seven
revision 1.x (or later) compatible, and that DIP switch 7 at the door
controller is ON or the Card Translation option is enabled in the
Door Extension editor. For door controllers with earlier firmware
versions, the use of the Key/Card Translation table is still required
when key/card numbers are greater than 32,000.
Advantages
Two of the main advantages for assigning large key/card numbers
directly to individuals, rather than using key/card translations, are
described below:
Ability to Increase Available Memory at the Door Controller
One advantage to using large key/card numbers without the Trans-
lation table is that the lookup record associated with the key/card
can be stored at the SLI level, rather than at the door controller.
This functionality requires that the SLI and door controller binary
loads are I/NET 2000 revision 2.x or I/NET Seven revision 1.x (or
later) compatible, and that DIP switch 7 at the door controller is
ON or the Card Translation option is enabled in the Door Exten-
sion editor. You must also ensure that the Resident in DPU option
is not enabled in the Individual Editor.
By freeing memory space within a door controller, you allow it to
store a greater number of incoming messages. Refer to Database
Caching in the Door Controller on page 9-10 for more informa-
tion.
Note: When you define translation table entries for key/cards, you force the
system to store the corresponding lookup records at the door
controller. The door controller must also store the entire contents of
the Key/Card Translation table. These items will consume memory in
the door controller.

Key/Card Numbers Access Control
Fill-in the Gaps within Ranges of Translated Key/Cards

Another reason for assigning large key/cards directly to individuals
is that you regain use of undefined individual records within ranges
of translated key/cards.
For example, say that you have 50 I/DISCs with key/card numbers
ranging anywhere from 35000 to 35499. If you use the Key/Card
Translation table to translate this 500-key/card range, but you only
have 50 actual I/DISCs, then 450 individual records will remain
unused. If you later translate 50 more I/DISCs ranging from
key/card number 40000 to 40499, then the new I/DISCs are beyond
the first 500-key/card range, and the 450 unused records are
waisted. However, rather than translating the new I/DISCs, you
could instead assign them directly to any of the previously unused
450 records. You would then have 400 unused records within the
500-key range that could be used sometime in the future. This
feature is especially useful in large systems as the number of indi-
viduals approaches the single tenant limit of the 32,000.
Note: I/NET allows you to assign a large key/card number directly to an

individual, or translate the number using the Key/Card Translation
table. However, within a single tenant, I/NET will not allow you to
perform both actions with the same key/card number or with the
same individual.
Large Number Guidelines

In summary, the guidelines for using large key/card numbers are:
All SLIs and door controllers must use I/NET 2000 revision
2.x or I/NET Seven revision 1.x (or later) compatible binary
software.
All door controllers must have DIP switch 7 set to ON or the
Card Translation option must be enabled in the Door Exten-
sion editor.
Within a single tenant, you can assign a large key/card
number directly to an individual, or translate the number
using the Key/Card Translation table, but not both (i.e., you
cannot have duplicate key/card numbers or individual
numbers within a single tenant).

Note: If you directly assign a key/card to an individual, and later translate

the same key/card for another individual, only the translated
key/card will be operational within I/NET.
Hexidecimal Number Support

In addition to large key/card number support, I/NET 2000
version 2.x and greater also allows you to enter key/card numbers
in a hexidecimal format. The traditional decimal format is
supported as well.
When you enter a hexidecimal key/card value, the decimal equiva-
lent is automatically calculated and displayed. Entering a decimal
number also causes the system to display the equivalent hexidec-
imal value. Refer to Card Number on page 9-65 for more infor-
mation.
Key/Card Data Formats and Conversions

Typically, a key/cards pre programmed number is physically
printed or stamped on the device. However, you may occasionally
need to convert the binary bit pattern read from a key/card to a
number that can be entered into I/NET.
Conversions
Use the information described below to determine the decimal
and/or hexidecimal value of a key/card.
Decimal Conversion
Convert binary data to a decimal value as follows:
Binary Pattern (example): Results:

1000101100100001 32,768
+ 2,048
32768
16384
8192
4096
2048
1024
512
256
128
64
32
16
8
4
2
1
+ 512
+ 256
+ 32
+ 1
(Add these values together) Decimal Value = 35,617

Key/Card Numbers Access Control
HexiDecimal Conversion
Convert binary data to a hexidecimal value as follows:
Binary Pattern (example): Results:

01000101100100001
1. Working from right to left, divide the
data string into groups of 4 bits: 0 1000 1011 0010 0001
2. Pad the left group with 0s in order to
make it 4 bits wide: 0000 1000 1011 0010 0001
3. Convert each group to a hexidecimal
value. 0 8 B 2 1
Hexidecimal Value = 8B21
26-bit Wiegand Format

Bit Pattern:
e eeeeeeee eeeeoooooooooooo o
Facility Code Card Number
Starting (e = even parity, o = odd parity) Ending

Parity Bit Parity Bit
(Even) (Odd)
The CSI/TAC 26-bit Wiegand card contains 2 parity bits and 24

data bits. I/NET interprets the data pattern as follows:
Starting Parity Bit (1 bit) Even parity.
Facility Code (8 bits) This 8-bit segment may also be
referred to as the Site Number or the Tenant Code.
Card Number (16 bits) This 16-bit segment may also be
referred to as the Card Number. The decimal value of this
segment cannot exceed 65,535.
Ending Parity Bit (1 bit) Odd parity.
Conversion Example:
Card Data: 0 10001010 0111111111111101 0
Decimal Conversion:
In this example, the binary Facility Code is 10001010. This
converts to a decimal value of 138.

The binary Card Number is 0111111111111101. This converts

to a decimal value of 32765.
Hexidecimal Conversion:
1. Excluding the parity bits, string the 24 data bits together.
Example: 100010100111111111111101.
2. Divide the string into groups of 4 bits.
Example: 1000 1010 0111 1111 1111 1101.
3. Now, convert each group into a hexidecimal value.
Example: 1000 = 8
Example: 1010 = A
Example: 0111 = 7
Example: 1111 = F
Example: 1111 = F
Example: 1101 = D
4. The final hexidecimal value for this card is 8A7FFD. This is
the value that you would enter into I/NET.
32-bit Wiegand Format
Bit Pattern:
o eoeoeoe oeoeoeoe oeoeoeoeoeoeoeo e

Sensor Code Facility Code Card Number
Starting (e = even parity, o = odd parity) Ending

Parity Bit Parity Bit
(Odd) (Even)
The CSI/TAC 32-bit Wiegand card contains 2 parity bits and 30

data bits. I/NET interprets the data pattern as follows:
Starting Parity Bit (1 bit) Odd parity.
Sensor Code (7 bits) The proprietary binary Sensor Code
for CSI/TAC key/cards is 0011000. The decimal value is 24.
Facility Code (8 bits) This 8-bit segment may also be
referred to as the Site Number or the Tenant Code.
Card Number (15 bits) This 15-bit segment may also be
referred to as the Card Number. The decimal value of this
segment cannot exceed 32,767.
Ending Parity Bit (1 bit) Even parity.

Database Caching in the Door Controller Access Control
Conversion Example:
Card Data: 0 0011000 10001010 111111111111101 0
Decimal Conversion:
In this example, the binary Sensor Code is 0011000. This
converts to a decimal value of 24.
The binary Facility Code is 10001010. This converts to a
decimal value of 138.
The binary Card Number is 111111111111101. This converts
to a decimal value of 32765.
Hexidecimal Conversion:
1. Excluding the parity bits, string the 24 data bits together.
Example: 001100010001010111111111111101.
2. Working right to left, divide the string into groups of 4 bits.
Example: 00 1100 0100 0101 0111 1111 1111 1101.
3. Pad the incomplete group on the left with two more 0s.
Example: 0000 1100 0100 0101 0111 1111 1111 1101.
4. Now, convert each group into a hexidecimal value.
Example: 0000 = 0
Example: 1100 = C
Example: 0111 = 4
Example: 0100 = 5
Example: 0101 = 7
Example: 0111 = F
Example: 0111 = F
Example: 1101 = D
5. The final hexidecimal value for this card is 0C457FFD. This is
the value that you would enter into I/NET.
Database Caching in the Door Controller

Within I/NET, you have the option of configuring your access
control system to store individual lookup records at the SLI level
rather than at the door controller-only level. You can then use a
Resident in DPU option in the Individual Parameters editor to

Access Control Database Caching in the Door Controller
specify that certain individual lookup records also be stored

(cached) residentially at the door controller level. This caching
feature requires that the SLI and door controller binary loads are
compatible with I/NET 2000 revision 2.x or I/NET Seven revision
1.x (or later) host software, and that DIP switch 7 at the DPU is ON
(for DPU firmware 3.18 or earlier) or that the Card Translation
option is enabled in the Door Extension editor (for DPU firmware
version 3.20 or later).
When your system is configured for database caching, the SLI
stores all individual lookup records. The DPU stores individual
lookup records for any key/cards that are configured as Resident
in DPU. The DPU also stores key/card translation tables.
SLI Storage Capacities

The 7791 DPI and 7793 MCI offer approximately 256 KB of
memory. The 7798 and 7798B I/SITE LANs offer approximately
512 KB of memory. The 7798B1 I/SITE LAN offers approximately
1024 KB of memory. Not all of the memory within the SLI is avail-
able for storing access control records. Each platform consumes
over 100 KB of memory as fixed overhead. Station parameters for
subLAN devices can consume up to 30 KB of SLI memory. Addi-
tionally, the use of embedded Tap emulation within the SLI will
consume another 28 KB to 58 KB of memory. Refer to the following
table to determine the approximate number of access control
records that can be stored within an SLI.
Table 9-1. SLI Storage Capacities

7791 DPI or 7798/7798B 7798B1
Tap Emulation
7793 MCI I/SITE LAN I/SITE LAN
None 10,616 records 32,461 records 76,152 records
7801 8,171 records 30,016 records 73,707 records
7803 or 7806 5,671 records 27,516 records 71,207 records
SLI and Door Controller Cache Interaction

The door controller can retrieve SLI-stored lookup records as
needed to verify access privileges when a non-resident user
attempts to gain access through a controlled door. After retrieving
a lookup record from the SLI, the door controller stores (i.e.,

Database Caching in the Door Controller Access Control
caches) the record locally as a transient record. With fewer lookup

records being stored at the door controller level, the door controller
can use its increased available memory for storing messages.
The door controller has a limited amount of memory space avail-
able for storing individual records and messages. Resident in
DPU individual records are given priority in storage: they are
never discarded. Transient (non-resident) individual records and
messages are stored on a space-available basis. When the memory
capacity is reached, records must be discarded as messages
continue to be generated. All records are discarded on a first-in,
first-out (FIFO) basis, so that the remaining records are the most
recent ones. Records are discarded in the following order:
Transient individuals.
Messages. If there are no more transient individuals to
discard, routine messages will be lost.
The SLI continually requests messages from its door controllers.
Retrieved messages are queued within the SLI until they can be sent
to the appropriate host workstation(s).
When the SLI queue is full, it will not request any AMT messages
from the door controller. It will continue to seek and accept state
and value changes, thus ensuring that any Event Initiated Control
actions are properly carried out.
When the door controller message queue gets full, it will discard
data as explained above, generating a queue overflow message to
warn that data was lost.
Once the SLI queue is emptied, including the buffer full warning,
it will resume polling and accepting messages from the door
controller, including the queue overflow message and any SLI
not available messages, until the door controller queue is empty.
It is strongly recommended that the SLI be connected to the host
through the embedded Tap, to minimize the chance that the SLI
will be unable to connect to the host, thus possibly filling the queue
and losing messages. A backup power source is strongly recom-
mended to reduce the likelihood that the SLI will lose power.

Access Control Access Control Configuration
Managing Cache Space in the Door Controller

The DPU7910A and DPU7920 each provide 64 kilobytes of
onboard memory. In these devices, care should be taken to limit the
number of resident individuals. The more individuals you make
resident in the door controller, the less memory storage space is
available for queueing of messages. If you have a lot of individuals
resident in the door controller, consider connecting to the door
controller more often, to minimize the possibility of lost messages.
Table 9-2 shows examples of memory usage in the DPU7910A and
DPU7920.
The SCU1284 and the DPU7920 with a DPU48K add-on board
installed provides two megabytes of onboard memory. Even with
100 kilobytes of memory used for overhead, there is still enough
memory remaining to support storing all 48,000 individuals resi-
dentially in the controller. Table 9-3 shows examples of memory
usage in the DPU48K.
When there are resident users in the door controller, one byte of
memory space is allocated for each user. Where possible, it is
advantageous to assign users starting from lowest to highest user
number.
Each message takes up 12 bytes of memory; each cached user takes
up 16 bytes. Table 9-2 and Table 9-3 shows how the number of resi-
dent users affects the number of messages and cached users that
can be stored in the door controller.
Access Control Configuration
Note: The editors used for access control will not be available unless you
enable access control in the I/NET active configuration. Refer to the
I/NET Configuration chapter in TCON298, I/NET Seven Getting
Started, for more information.
Access control elements (individuals, doors, key/cards, schedules,
etc.) are configured through separate editors. Changes made in one
editor can affect the operation and contents of other editors. The
following paragraphs describe what order of operations to use

Access Control Configuration Access Control
Table 9-2. DPU7910A or DPU7920 Memory Management
Total Memory = 65,536 (64K) Resident User = 1 byte

Overhead = 6,036 Cached User = 16 bytes
Usable Memory = 59,500 Message = 12 bytes
Sec Sched (per user) = 13 bytes
Users with
Resident Secondary Remaining Cached
Users Schedules Bytes Messages OR Users
100 100 58,100 4,841 3,631
500 100 57,700 4,808 3,606
1,500 100 56,700 4,725 3,543
3,000 100 55,200 4,600 3,450
6,000 100 52,200 4,350 3,262
12,000 100 46,200 3,850 2,887
18,000 100 40,200 3,350 2,512
24,000 100 34,200 2,850 2,137
36,000 100 22,200 1,850 1,387
48,000 100 10,200 850 637
Table 9-3. SCU1284 and DPU7920 w/DPU48K Memory Management

Total Memory = 2,048,000 (2M) Resident User = 1 byte
Overhead = 102,400 Cached User = 16 bytes
Usable Memory = 1,945,600 Message = 12 bytes
Sec Sched (per user) = 13 bytes
Users with
Resident Secondary Remaining Cached
Users Schedules Bytes Messages OR (Messages + Users)
100 100 1,944,200 162,017 76,683 64,000
500 100 1,943,800 161,983 76,650 64,000
1,500 100 1,942,800 161,900 76,567 64,000
3,000 100 1,941,300 161,775 76,442 64,000
6,000 100 1,938,300 161,525 76,192 64,000
12,000 100 1,932,300 161,025 75,692 64,000
18,000 100 1,926,300 160,525 75,192 64,000
24,000 100 1,920,300 160,025 74,692 64,000
36,000 100 1,908,300 159,025 73,692 64,000
48,000 100 1,896,300 158,025 72,692 64,000
64,000 100 1,880,300 156,692 71,358 64,000
when configuring the access control system and how to track

configuration changes.

Note: As you modify your access control system, the changes you make are
sent to the applicable door controllers when you close each editor. If a
communication error between your host workstation and a door
controller prevents changes from being downloaded, I/NET will
attempt to perform an Automatic DPU Restore as soon as a restore
message of any kind is detected. Refer to Automatic DPU Restore
on page 5-10 for more information.
Order of Operations
You must observe the following order of operations when
performing access control database entry.
1. Configure the door controller.
2. Define the station parameters (define control descriptions
and state descriptions for door points).
3. Add door points in the Resident I/O Points editor.
4. Save door points in the Network Configuration editor.
5. Define the doors in the Door Parameters editor.
6. Define door mode schedules.
7. If desired, translate key/tag numbers greater than 32,000
using the Key/tag Translation editor.
8. Define tenants using the Tenants editor.
9. Define groups using the appropriate editors.
10. Define individuals.
11. If necessary, implement elevator control (details in this
chapter).
Audit Trail Messages

I/NET supports an access control audit scheme for tracking data-
base edits associated with all pertinent access control editors. Audit
trail messages provide information about configuration changes
made to the access control system. These messages contain the date
and time an edit was performed, the site number, and the key/card

Access Control Configuration Access Control
number and initials of the person who performed the edit. This
provides a high-level audit trail for updates. Separate audit trail
messages are generated for the following items:
Individual edits
Group edits
Personnel schedule edits
Door edits
Tenant edits
Translation table edits
Elevator edits
Access initiated control (AIC) edits
Host password edits
DCU password edits
Audit trail messages can be marked with a SevenTrends cell
number for later evaluation and report generation purposes. Audit
trail message distribution information (group, mask, cell) is
defined from the access control Options editor.
Recycle Bin
Newly introduced with I/NET Seven is the access control recycle
bin. When enabled, the recycle bin provides a temporary storage
location for deleted individual, group, and tenant records. When
one of these records is moved to the recycle bin, it no longer
appears in any editors or summaries. Recycle bin records can later
be restored, or they can be permanently purged from the system.
Access to the recycle bin is restricted to users with proper permis-
sions. This allows your system to be configured in such a way that
only select operators are allowed to delete, restore, or purge
records. Refer to Host Passwords on page 4-3 for more informa-
tion about passwords and permissions.
Deleting a Group
When you delete a group to the recycle bin, the following informa-
tion is retained within a single recycle bin record:
The groups door assignments

The groups links to other groups

The recycle bin does not retain references to a deleted group. There-
fore, if you delete a group that is assigned to an individual, or that
is being referenced by another group, the links to the group will be
destroyed. Even though you can restore the group later, the
previous links to this group will not be restored. The system alerts
you of this functionality by displaying a warning when you attempt
to delete the group. This allows you to cancel the delete request if
necessary.
Deleting an Individual
When you delete an individual to the recycle bin, the following
information is retained within a single recycle bin record:
The individual record
The individuals key/card assignment
The individuals tenant assignment
The individuals door and group assignments
Deleting a Tenant
When you delete a tenant to the recycle bin, all of its groups and
individuals are also deleted to the recycle bin and linked to the
deleted tenant. The following information is retained within a
single recycle bin record:
The tenant record
The tenants door assignments
The tenants individuals and groups.
Restoring Records from the Recycle Bin
The restore operation recreates an active record from the informa-
tion stored in the recycle bin. Only a single record at a time can be
restored. However, when you restore a deleted tenant, any groups
and individuals that were defined for that tenant are also restored.
Restoring a record from the recycle bin is much like adding a new
record. The system displays the Add dialog that corresponds with
the record type that is being restored. This dialog will already
contain the tenant or individual number or the group name of the
record being restored. You have the option of accepting the default

DPU Configuration Access Control
setting or changing it. When you select OK to proceed, the system

validates the entry and then displays the appropriate editor with
information retrieved from the recycle bin record already filled in.
Purging Records
You can permanently delete access control records contained in the
recycle bin by purging them. Once purged, these records no longer
exist and therefore, they can not be restored.
I/NET offers you the following three methods for purging records
from the recycle bin:
Open the recycle bin and purge selected records directly.
Configure I/NET to automatically purge records that have
been in the recycle bin for a specified number of days. This
function runs every 60 seconds. It uses the deletion time and
date stamp contained in each recycle bin record to determine
whether or not the record should be purged.
Configure I/NET to automatically purge all recycle bin
records at log off. Records can be purged silently at log off, or
you can configure the system to first prompt the user. When
prompted, the user can choose whether or not to purge the
recycle bin. The prompt also allows the user to turn off future
prompting and allow the system to silently purge the recycle
bin at log off.
DPU Configuration
The DPU configuration process identifies for the DPI, MCI, or
I/SITE LAN which devices to poll for successful communication.
The DPI and I/SITE LAN each support up to 32 devices. An MCI is
a two-station device that allows a maximum of 64 subLAN devices
(32 per station). Each point address for the controller to which you
are currently connected can be defined as one of the following
types:
Internal Tells the DPI, MCI, or I/SITE LAN that there is no
controller at that address to poll.

Access Control Doors
DPU Tells the DPI, MCI, or I/SITE LAN that there is a

DPU7910A, DPU7920, or SCU1284 at this address and to poll
it.
DIO Tells the DPI, MCI, or I/SITE LAN that there is a
DIO7940 or SCU1280 at this address and to poll it.
DIU Tells the DPI, MCI, or I/SITE LAN that there is a
7930DIU or SCU1200 at this address and to poll it.
MR Tells the MCI or I/SITE LAN that there is a Micro Regu-
lator at this address and to poll it. This type is not available
when connected through a DPI.
ASC Tells the MCI or I/SITE LAN that there is an Applica-
tion Specific Controller at this address and to poll it. This type
is not available when connected through a DPI.
Doors
Door points can be added to I/NET using the Resident I/O Points
editor. Door point addresses use the same structure as all other
I/NET points; however, the following actions must be taken when
defining a door point:
The bit offset defined in the point address must be either 08
or 09 (first or second door point in the door controller,
respectively)
The point type must be set to DO
The point class must be set to internal
The three-state output parameter must be enabled.
After door points have been defined in the Resident I/O Points
editor, they must be saved in the Network Configuration editor.
Only door points that have been saved in the Network Configura-
tion editor are available to the access control system.
I/NET lets you add, delete, modify, or copy door access control
extensions in your system. When you add or modify a door access
control extension, the system provides the following.
Door parameters
Mode schedules

Doors Access Control
Note: Changes made through the Door Extension editor generate a door
edit audit trail message. Refer to Audit Trail Messages on page
9-15 for more information.
Note: When deleting a door from a 7791 DPI, 7793 MCI, or 7798 I/SITE
LAN, make sure to delete the door extension before deleting the door
(DO) point. Deleting the door point without previously deleting the
door extension may cause unpredictable system performance.
Reader and Door Parameters

Door parameters can be defined when adding or modifying a door
access control extension. The various door and reader parameters
are described below.
Reader Type
I/NET supports several types of key/card readers. The reader type
parameter defines which reader type to associate with the selected
door point. The options available for this parameter are listed in
Table 9-4.
Table 9-4. I/NET-Supported Reader Types
Reader Type Description
ABA 115 ABA data format with 115 bit data length
ABA 85 ABA data format with 85 bit data length (CSI specification)
I/DISC TAC I/DISC button
ITracs Indala readers using CSI proprietary data format
Tracs TAC proprietary data format
Watermark Standard Watermark data format
Wiegand 26-bit Standard Wiegand data format reader
Wiegand 32-bit TAC proprietary Wiegand data format reader
Wiegand 66-bit TAC proprietary Wiegand data format reader

Table 9-4. I/NET-Supported Reader Types (Continued)
Reader Type Description
Generic Wiegand data format reader. When this option is selected, define
the bit data length of the card number (2664).
Custom Wiegand If you select this reader, the reader type must match the selection for AC
Reader Port in the active configuration. Refer to the section on I/NET
Configuration in TCON298, I/NET Seven Getting Started.
Generic ABA data format reader. When this option is selected, define the bit
Custom ABA
data length of the card number (919).
Note: Selecting a custom reader type automatically invokes the large

number system for key/card numbers. Refer to Large Number
Support on page 9-5.
PIN Pad or PIN Type

depending on the version of firmware loaded in the door
controller, either a PIN Pad option or PIN Type list appears in the
Door Extension editor, as described below:
PIN Pad This option appears when the door controller uses
firmware prior to version 3.18. By default, the PIN Pad option
is greyed out. It becomes available when you set the Reader
Type to I/DISC or Wiegand 66 in the step above
(Wiegand 26 and Wiegand 32 readers always have an implied
PIN pad if the door's PIN Enable mode schedule is active).
Activate the PIN Pad option if a PIN pad will be used to
control access at the chosen door point.
PIN Type This parameter appears when the door controller
uses firmware version 3.18 or later. By default, the PIN Type
parameter is greyed out. It becomes available when you set the
Reader Type to I/DISC, Wiegand 26/32/66, or Custom
Wiegand.
Use the PIN Type drop-down list to specify whether or not a
PIN pad is to be used at the door. By default, this parameter is
set to None. To configure this door to use a PIN pad, specify
the type of PIN pad being used; either 8-bit or 26-bit. Be
aware that user-defined PIN pad functions require an 8-bit
PIN pad.

When you configure the door to use a PIN pad, a person

attempting to gain access through the door will be
required to enter a valid PIN whenever the door is oper-
ating in the PIN enable mode (refer to Mode Sched-
ules on page 9-33 for more information about this door
mode).
Note: This option is automatically deactivated if you select a reader type

that does not support PIN pads. If you then select a reader type with
PIN pad support, you must manually activate this option again.
PIN Message Enable

This option specifies whether entry and exit transaction messages
will indicate that a PIN was used. This option is available only if the
PIN pad option is activated. (This option is only available on door
controllers with binary software revision 2.20 or later.)
Note: If the reader type is I/DISC, this setting will be ignored unless the
door controller is a DPU7920 or an SCU1284.
Activate this option if you wish to track entry and exit transactions
that are made using a PIN. If you do not wish to track this informa-
tion, you may leave this field inactive.
If this option is activated, then reader entry messages will indicate
whether a PIN was used. For example, a door equipped with both
a card reader and a PIN pad will generate one of two messages:
either Reader entry or Reader entry - PIN. This allows the oper-
ator to determine the access method used to unlock the door.
PIN Retry Count
This option indicates the number of times a user may attempt to
enter a PIN before generating a Denied - PIN message. This
message will be either an alarm or a transaction, depending on the
setting for this event in the Message Type section of this editor.
This option is available only if the PIN pad option is activated.
(This option is only available on door controllers with firmware revi-
sion 2.20 or later.)

Note: If the reader type is I/DISC, this setting will be ignored unless the
door controller is a DPU7920 or an SCU1284.
An entry of zero (0) indicates zero retries; a Denied - PIN

message will be generated whenever an incorrect PIN is entered. An
entry of 1 indicates one retry: the user may attempt to enter a
correct PIN a total of two times (the original attempt plus one
retry) before the message is generated. The maximum is three
retries, which allows four total attempts at entering a correct PIN.
Exit Reader
The exit reader parameter determines whether or not an exit reader
will be used with the selected door point. If an exit reader will be
used, this parameter also determines whether or not to tie the
reader to a time schedule.
Depending on whether or not the door is configured with a PIN
pad, the following Exit Reader options are available.
Door without PIN pad:
None Do not use exit reader for egress.
Anytime Valid key/cards are granted exit at all times,
regardless of active personnel schedules (i.e., 24 hours, 7
days-a-week).
Scheduled Tie the exit reader validation to active
personnel schedules.
Door with PIN pad:
None Do not use exit reader or PIN pad for egress.
Anytime Valid key/cards are granted exit at all times,
regardless of active personnel schedules (i.e., 24 hours, 7
days-a-week). No PIN is required.
Sched. w/PIN Tie the exit reader validation to active
personnel schedules. Entry of a valid PIN is required to
exit the area when the door is operating in the PIN
Enable mode.
Sched. w/o PIN Tie the exit reader validation to active
personnel schedules. No PIN is required to exit the area.

Note: If you have defined one door in a DPU7920, and the doors Exit
Reader parameter is set to anything besides No, then the second
reader port automatically becomes the exit reader. If you have
defined two doors (08DO or 09DO) in a DPU7920, neither door can
have an exit reader defined.
Only the first two doors in the SCU1284 can have an exit reader. If
you assign an exit reader to the first door, the reader input for a third
door will instead be used for the first door's exit reader. If you assign
an exit reader to the second door, the reader input for a fourth door
will instead be used for the second door's exit reader.
User Defined Length

If you selected either Custom Wiegand or Custom ABA in the
Reader Type parameter (see Reader Type on page 9-20), enter the
bit data length for the selected reader here. This field is disabled if
any other reader type is selected.
Note: This value is not updated if you select a different reader. If you switch
between reader formats, the default value in this field may not be
valid for the selected card type.
Intercard Interval (sec)

This parameter can be set to a value from 0 to 255 seconds. Use this
parameter to define the acceptable interval between consecutive
key/card reads. Following a valid key/card read, the reader is
disabled for the specified duration. This function can be used to
control the flow of traffic or speed at which access is granted.
LED Polarity
This parameter can be set to either Cathode or Anode to specify the
polarity of the corresponding LEDs on the key/card reader.
A Dorado setting is also available. Use this setting to support the
use of a three-LED Dorado reader.
Refer to the installation guide for your particular door controller
for more information about LED control.

Elevator
This parameter can be either enabled or disabled. Enable this
parameter if the reader associated with this point controls an
elevator cab (refer to Elevators on page 9-45 for information
about implementing elevator control). Enabling this parameter
adds a Floors menu item to the schedule parameters in the
Personnel Schedules editor.
Card Translation
If the door controller is loaded with firmware version 3.18 or later,
a Card Translation option is available. Activate this option if you
wish to translate high I/DISC or Watermark key/card numbers to
values that are within a 1-to-32,000 key/card range.
Anti-passback
This parameter can be either enabled or disabled. The purpose of
the anti-passback function is to prevent persons who have success-
fully gained access into an access controlled area from passing their
key/card back to another person desiring access. Anti-passback is
enabled or disabled for a door in this editor, but the system
response depends on the setting in the Individual Parameters
editor (see APB on page 9-70).
Although the Anti-passback parameter is used to enable anti-pass-
back, implementing anti-passback also requires that you define
access control zones. Refer to Entry and Exit Zone Number below
for information about implementing anti-passback.
Note: Anti-passback requires that a door controller have both an entry

reader and an exit reader. An elevator door controller will support
only an entry reader, and therefore, will not support anti-passback.
Anti-tailgate
This parameter can either be enabled or disabled. This option is
available only if the Anti-passback option is enabled (see Anti-
passback on page 9-25). The purpose of the anti-tailgate option is
to discourage users from following another person through an

access-controlled door without reading their own keys/cards for

access. Anti-tailgate is a more stringent security measure than anti-
passback alone.
In anti-passback, users are never prevented from leaving a zone,
only from re-entering the same zone without exiting. The anti-
passback (APB) flag is set for the particular zone the user last
entered. When the user enters a new zone, the APB flag for the
previous zone is cleared. Only the last-entered zone is affected by
the APB flag.
With anti-tailgate, users are not able to exit a zone that they have
not entered with a valid key/card read. The anti-tailgate (ATG) flag
limits entry to zones immediately adjacent to the last-entered zone.
This forces users to read both exit and entry readers for each zone
they pass through.
Note: If the Anti-tailgate option is enabled, any door between the secured
area and the non-secured area must have the same zone number for
both exit and entry (see Entry and Exit Zone Number on page
9-26). The non-secured area is any region not under access control,
such as a lobby, public area, or the outdoors.
Entry and Exit Zone Number

The Entry and Exit Zone parameters are available only if the Anti-
passback option is enabled. The valid zone range is 064.
Note: If the Anti-tailgate option is enabled (see Anti-tailgate on page

9-25), any door between the secured area and the non-secured area
must have the same zone number for both exit and entry. The non-
secured area is any region not under access control, such as a lobby,
public area, or the outdoors.
When a user moves between zones (e.g., uses a key/card at an entry

or exit reader), the system generates a zone exit message followed
by a zone entry message, and broadcasts these messages to the other
readers in the system. The user must use their key/card to enter or
exit a zone. If they do not (for example, they leave a zone when
another person uses their key/card), then an APB violation will
occur.

Moving from Zone 1 to Zone 3, the door controller broadcasts a

Reader Exit message from Zone 1, and a Reader Entry message to
Zone 3.
I/NETs response to anti-passback is dependant upon the setting of
each individuals APB parameter:
Hard When an individuals APB setting enables hard anti-
passback, the system will allow the user to be in only one zone
at a time. For example, if the individual properly enters a zone
but then does not use their key/card when exiting the zone,
I/NET will not allow the individual to re-enter this zone or
enter any other zone using their key/card. Only by properly
exiting the zone will the individual be allowed to enter
another zone or re-enter this zone.
Soft When an individuals APB setting enables soft anti-
passback, the system will not prevent the user from being in
more than one zone. For example, if the individual properly
enters a zone but then does not use their key/card when
exiting the zone, I/NET will still allow the individual to re-
enter this zone or enter another zone using their key/card.
Graced When an individuals APB setting is graced, the
system will not track the users movement through zones.
Positioning of Readers
I/NET denies access due to anti-passback on entry readers only. A
key/card is never denied access on an exit reader due to anti-pass-
back.
When using anti-passback for single or multiple zones, decide
which side of the door you want to restrict with anti-passback. The
reader on that side of the door should be configured as the entry
reader. For example, if you are in Zone 2 and attempting to enter
Zone 3, the entry reader should be designated as 2 and the corre-
sponding exit reader as 3.
Zone Numbering Rules
When populating the Door editor, enter the zone number where
the reader is physically located. Entry readers should be located on
the exterior of a controlled zone. Exit readers should be located on
the interior of a controlled zone.

Exterior doors, in access control terms, are doors that lead from a
non-controlled area into an access controlled area. These doors are
not necessarily on the exterior of the building. The entry reader at
an exterior door is physically located in an area that has no zone
number (i.e., a non-controlled area). The zone number assigned to
the entry reader of an exterior door should match the zone number
assigned to the exit reader of that door.
Figure 9-2 shows an example of a facility with three anti-passback
zones that share doors. Using the example, the door leading from
zone 1 to zone 3 has an entry reader physically located in zone 1.
The zone number assigned to the entry reader is 1, even though this
reader is used to gain access into zone 3. This door also has an exit
reader that is physically located in zone 3. The zone number
assigned to the exit reader is, therefore, 3.
Figure 9-2. Sample Multiple Anti-passback Zones
Each exterior door shown in the example has entry reader and exit
reader zone numbers that match. This causes I/NET to generate
only one zone entry or exit message after a valid read at an exterior
door. This also makes it unnecessary to use a zone number for the
exterior (non-controlled) area of the building.

Anti-passback Reset Time

The Anti-passback Reset Time accepts a value from 0 to 60
minutes. (This parameter is only available on door controllers with
firmware revision 2.20 or later, and only if the Anti-passback option
is enabled.)
By setting this parameter to a non-zero value, you can cause the
door controller to start a timer when an individual is granted access
through the currently selected door. When the timer duration
expires, the door controller will reset the individuals APB flag for
this door. The individuals APB flag for all other doors in the same
zone will also be reset, as long as the door controllers for these
doors reside on this doors controller LAN.
Note: The anti-passback timer for each door runs independently.
A setting of zero (0) in this field disables timed individual anti-

passback for this door. Regardless of this parameters setting, an
individuals APB flag can also be reset as follows:
When the individuals key/card is read and accepted at any of
this zones exit readers. This resets the individuals APB flag
for all doors within the same zone.
When you send a manual APB Reset command from the
Point Control editor or Door Summary to a selected door.
This resets the APB flag for all individuals within the same
zone as the selected door.
When the doors mode schedule places the door in the APB
Reset mode. This resets the individuals APB flag for this door
only.
Door Code
Note: This option is only available on door controllers with firmware revi-
sion 3.22 or later.
On a door controller with firmware version 3.22 or later, a six-digit

door code is supported. This feature allows individuals to gain
access simply by typing a specific door code at the doors PIN pad
anytime the door is operating in the Sec/Code mode.

While entering the door code, the user can omit leading zeros by
beginning the entry with the first non-zero digit. In this case, the
user must press the # button after the last digit in order to complete
the door code entry.
When defining the door code in the Door Extension editor, if you
enter less than six digits, leading zeros will be appended to the code
automatically. You can leave the door code blank; however, a door
code of 000000 is not allowed.
Door Strike
This parameter determines when the door strike (magnetic lock) is
to be controlled. Set this parameter to None for no control, Enter
for entry only, Exit for exit only, or Both, if the strike is to be
controlled for both entry and exit.
Strike Duration
This parameter can be set to a value from 1 to 255 seconds. Use this
parameter to define the strike duration. This controls the time that
the door will remain unlocked after a key/card is read or a release
button is pressed. The strike will be relocked immediately following
the detection of the sense switch (door closure).
Door Open Too Long
This parameter can be set to a value from 0 to 7,200 seconds. Use
this parameter to define the length of time that can pass before a
door open too long message is generated following a valid
key/card read. The time starts once the door is opened (sense
switch required).
Note: The door open too long message is only generated when the door is in
the Secure mode; it is not generated when the door is in Unlocked
mode.
Door Sense Switch

This parameter is used to define whether or not a sense switch
exists at this door, and if so, the normal state of the switch. Set this
parameter to None if there is no sense switch at this door. If there
is a sense switch, set this parameter to normally-closed (NC) or

normally-open (NO). Refer to Anti-passback on page 9-25 for

information about how the door sense switch effects the anti-pass-
back function.
Door Release Switch
This parameter is used to define whether or not a release switch
exists at this door, and if so, the normal state of the switch. Set this
parameter to None if there is no release switch at this door. If there
is a release switch, set this parameter to normally-closed (NC) or
normally-open (NO).
Re-lock Timer
This parameter determines the amount of time that passes between
the door opening and re-energizing the lock. The timer may be set
from 0 to 255 seconds, in 1-second intervals. The default is 4
seconds. (This option is only available on door controllers with firm-
ware revision 2.20 or later.)
Shunt
This parameter can be either enabled or disabled. Enable this
option if there is a shunt installed with this door. This option is
used to shunt an in-house alarm system when the door is opened
because of a valid key read. Enabling the shunt option will cause the
next consecutive relay to the strike to be energized following a valid
key/card read.
Shunting is automatic for a DPU7910A: the shunt is enabled upon
a valid key read. When using a DPU7920 or SCU1284, the shunt
relay will only be energized (upon a valid key read) if this option is
enabled.
First Key Auto-unlock
sion 3.21 or earlier. For door controllers with firmware revision 3.22
or later, refer to First Key Mode on page 9-35.
This function is controlled by the mode schedules in the Door

editor (refer to Mode Schedules on page 9-33). Enabling this
function permits the door to remain in the secure or PIN enable
mode past the scheduled unlock time, until the first valid entry

sequence (i.e., valid key/card read for Secure mode, or valid

key/card read and valid PIN entry for PIN Enable mode) is
performed. The door then remains in the unlock mode for the
specified time. If there is no valid entry sequence performed during
the unlock period, the door will remain in the secure or PIN enable
mode. If first key auto-unlock is used, then a secure mode or PIN
enable mode must precede the designated unlock schedule. See
Figure 9-3 for an example of the mode schedule of a typical first key
auto-unlock scenario.
Note: If you want access enabled after hours based upon personnel sched-
ules, use the first key auto-unlock function.
Figure 9-3. Typical Mode Schedule with/without First Key

Auto-unlock
If you disable this function, the door will automatically unlock

(Auto-unlock) according to the mode schedule, whether or not a
valid entry sequence occurs during the unlock mode schedule.
Door Closed Timer
This option is used to minimize false forced door alarms by
setting a timer within which the door may bounce while closing
without generating the forced door message. The timer may be set

from 0 to 25.5 seconds, in 0.1-second intervals. The default is 2

seconds. (This option is only available on door controllers with firm-
ware revision 2.20 or later.)
Mode Schedules
A door Mode Schedule controls the operating mode of the door at
specific times of the day. Each door extension includes scheduling
parameters for defining each door.
Action
The only difference between a mode schedule and other I/NET
time schedules is the available schedule actions. The following
mode schedule actions are available.
APB Reset
This action resets anti-passback memory for this door. Any indi-
vidual who previously entered the zone assigned to this door, but
who has not yet exited, can now successfully reenter the same zone.
This function is applicable only to the door containing the mode
schedule and is not globalized for zone anti-passback. Conse-
quently, each door using anti-passback should contain an APB
reset command at the end of each day in its mode schedule.
Lock
This action inhibits entry and exit through the door. All readers
and release buttons for a specified door are disabled when lock is in
action.
Unlock
This action enables the door for open access. Key/card readers are
still enabled for continued access control audit.
Note: When a door mode schedule defines unlock at the end of a lock
period, the door automatically unlocks at the scheduled time. If you
want the door to remain locked during the scheduled unlock time,
until authorized personnel have entered the area, you must define a
secure (or PIN enable) period immediately preceding the unlock
period and use the first key auto-unlock function. Refer to First Key
Auto-unlock on page 9-31 for more information.

Secure
This action returns the door to authorized access only. All
key/cards will be validated based on personnel schedules, tenant,
key/card issue number, anti-passback, and access level.
PIN Enable (Door Controller Firmware 3.20 or Earlier)
OR
Sec/PIN (Door Controller Firmware 3.21 or Later)
When this mode is active, the PIN reader on the DPU will be
enabled. This mode is the same as the Secure mode except that it
also requires the individual to enter a valid PIN after a valid
key/card read. If an individual enters an invalid PIN, the setting of
the PIN Retry Count parameter (described on page 9-22) will
determine how many retries (if any) the individual can use to enter
a valid PIN.
You can schedule a door's PIN pad to become disabled without
unlocking the door by following this mode with a Secure mode.
When the Secure mode becomes active, individuals will no
longer be required to enter a PIN in order to gain access through
the door.
Note: I/NETs PIN function also supports a duress code for use in emer-
gency situations. See your I/NET system administrator for more
information about this feature.
Sec/Code (Firmware Version 3.22 or Later)

This mode is similar to the Secure mode; however, rather than
using a key/card to gain access, the user simply uses the PIN pad to
enter the door's assigned code. If the individual enters the correct
door code, the door will open.
Refer to Door Code on page 9-29 for more information.
Note: When the door is operating in the Sec/Code mode, user-definable

door attributes and PIN pad functions (described on page 9-36) are
not available.

First Key Mode
sion 3.22 or later. For door controllers with firmware revision 3.21 or
earlier, refer to First Key Auto-unlock on page 9-31.
Using the first key mode, you can configure the mode schedule to
switch to a secondary mode if a valid entry sequence occurs at the
door. Once operating in the secondary mode, the door will remain
in this mode until the next scheduled action becomes active.
The first key mode is only active when you set the mode schedule
action to Secure, Sec/PIN, or Sec/Code. The options available for
the first key mode parameter will differ depending on the mode
schedule action setting.
When you configure an action to use the first key mode, it will be
displayed in the Door Mode Schedule editor with the main action
shown first, followed by an arrow (->), and then the secondary
mode.
For example:
An action of Sec/PIN with a first key mode setting of Sec/Code
will be shown as:
Sec/PIN>Sec/Code
In this example, the door will operate in the Sec/PIN mode until an
individual gains access by swiping their card and entering their
PIN. The door will then switch to the Sec/Code mode, allowing
subsequent individuals to gain access simply by typing the door
code at the PIN pad.

User-definable Door Attributes and PIN Pad Functions

Note: User-definable door attributes and PIN pad functions are only avail-
able if the selected door meets the following requirements:
The door controller is loaded with firmware version 3.18 or later.
For PIN pad functions, the keypad must provide an 8-bit burst
output
The DPU7920 with firmware version 3.16 also provides user-defined
door attributes and PIN pad functions except for the attributes used
for the two-man rule.
In addition to I/NETs standard door features, user-definable

features are also available. For example, if your door uses a PIN pad
to control access, you can configure it to also allow users to operate
and monitor system functions. Using an extended mode of the PIN
pad, a user can arm or disarm an alarm system, place the door into
the Lock, Unlock, or Secure mode, energize or de-energize a relay,
or monitor a DI point in your door controller.
The user-definable features available for a door can be categorized
into the following two groups:
Attributes Door attributes are used to initiate specific
actions in the access control system when select users perform
a key/card read at the door.
Functions PIN pad functions allow users to operate and
monitor system functions directly from a PIN pad.
Assigning Points to PIN Pad Functions
When adding PIN pad functions to a door, you are sometimes
required to assign one or more I/NET points to the function. For
example, you can assign a range of I/NET points to the Discrete
Status PIN pad function.
The points that you can assign to a function must reside in the door
controller. When assigning a point to a PIN pad function, you need
only specify the bit offset (BB) portion of the points address. The
link (LL), station (SS), and point (PP) portions of the address will
match the address of the selected door.

Assigning Points in an SCU1284 Controller

The SCU1284 has the capability to control up to four doors. In
order to control more than two doors, the SCU1284 must operate
in a double-address mode. In this mode, the SCU uses two
consecutive subLAN point addresses. The SCUs first address is
used with its first two doors and the next consecutive address is
used with the second two doors.
As described earlier, in order to assign a point to a PIN pad func-
tion, you only specify the points bit offset. The rest of the points
address will match that of the selected door. Since the SCUs doors
can be split across two subLAN addresses, you must take care not
to assign points from one subLAN address to PIN pad functions on
the other subLAN address.
Refer to TCON312, SCU 1200-series Installation Guide for more
information about how points are mapped in the SCU.
Intruder Alarm System Functions
You can use PIN pad functions to control an intruder alarm system.
In order to do this, you must first enable the Intruder Alarm System
option. Once enabled, the following parameters become available:
Arm Ready Bit Offset
Use the Arm Ready Bit Offset parameter to specify which DI point
will receive the arm ready status signal from the alarm system. The
state of this point will be used to determine whether or not the
alarm system can be armed.
You must use a DI point on the current door controller to receive
the arm ready status from your alarm system. For this reason you
need only specify the points bit offset. For example, if this signal
enters the door controller at DI point 00 (TB1-1 on a DPU 7920),
then enter a bit offset of 00.
Arm Ready State
Use the Arm Ready State parameter to specify the state (0 or 1)
that constitutes an arm ready condition. For example, if your
alarm system sends a level 1 discrete signal when its ready to be
armed, then choose 1. Otherwise, choose 0. If the state of the arm

ready DI point (specified by the Arm Ready Bit Offset parameter

above) matches this setting, the alarm system is considered ready to
be armed.
The state that you choose for this parameter will also be used for
comparison when a user checks the status of DI points through the
PIN pad. Refer to the Discrete Status function on page 9-41 for
more information.
Arm Relay Bit Offset
Use the Arm Relay Bit Offset parameter to specify which DO point
will be used to control the relay that will arm or disarm the alarm
system.
You must use a DO point on the current door controller to arm the
alarm system. For this reason you need only specify the points bit
offset. For example, if you use the relay at DO point 07 (TB9-
10/11/12 on a DPU7920), then enter a bit offset of 07.
Arm Relay State
Use the Arm Relay State parameter to specify the state (0 or 1) that
will cause the relay to arm the alarm system. For example, if you
must energize the relay in order to arm the alarm system, then
choose 1. Otherwise, choose 0.
Using PIN Pad Functions
Note: PIN pad functions are not available for use while the door is oper-
ating in the Sec/Code mode. Refer to Sec/Code (Firmware Version
3.22 or Later) on page 9-34 for more information.
You can control the use of PIN pad functions on a per-user basis. A
users personnel schedule will determine whether or not the user
can access a particular PIN pad function. Refer to Personnel
Schedules on page 9-52 for more information.
A user must initiate an extended mode of the PIN pad in order to
access the user-defined PIN pad functions. After initiating the
extending mode, the user can access a function by pressing its
corresponding key on the PIN pad. If the user presses an invalid
key, the red LED on the PIN pad blinks for two seconds.

You can set an Extended mode timeout to limit how long the PIN
pad will wait for input from the user. If the user fails to press a valid
key within the timeout period, the PIN pad automatically exits the
extended mode. If you set the timeout to 0, you effectively disable
the extended mode and prevent anyone from accessing the PIN pad
functions.
Entering Into the PIN Pads Extended Mode
A user must press the # key in order to initiate the PIN pads
extended mode. If no user-defined functions are available, the red
LED on the PIN pad blinks for 2 seconds and the PIN pad returns
to the idle state (i.e., it exits the extended mode).
If the PIN pad contains user-defined functions, a steady yellow
LED comes on and the extended mode timeout counter starts. At
any time before timeout occurs, the user can restart the counter by
pressing the # key. If the timeout counter expires, the yellow LED
goes out and the PIN pad automatically exits the extended mode.
The user can manually exit the extended mode at any time by
pressing the * key.
Validating the Current User
Upon entering the extended mode, the PIN pad requires the user to
read their card. Depending on the currently active door mode, the
user may also have to enter their PIN. If these credentials are valid,
and the users personnel schedule allows access to PIN pad func-
tions, the PIN pads LED flashes an alternating red and green
pattern. This indicates that the PIN pad is waiting for the user to
select a function key.
If the users credentials are not valid, or if their personnel schedule
does not allow access to PIN pad functions, the red LED on the PIN
pad blinks for 2 seconds and the PIN pad exits the extended mode.
PIN Pad Functions
While the PIN pads LED is flashing the alternating red and green
pattern, the user can access an available function by pressing the
functions associated key.
Depending on the function, the user may be required to press a
second key in order to complete the task. For example, if the user
presses a function key that allows switching between the Secure,

Unlock, and Lock door modes, the user will then have to press 0, 1,
or 2, respectively. However, if this function is configured to allow
selection of only one door mode (Unlock for example), then the
second key input is not required.
While waiting for the input of a second key, several functions will
show the current state of the selected function. For example, if the
user selects the Door mode function, the currently active door
mode is displayed on the PIN pads LED until the user controls the
door mode by pressing another key or until the extended mode is
exited (timeout occurs or user presses the * key).
The following sections describe the available PIN pad functions.
Arm/Disarm
The Arm/Disarm function allows an authorized user to control an
alarm system from the PIN pad. This function provides the
following options:
Disarm (key 0)
Arm (key 1)
Control door mode
When an authorized user selects this function, the PIN pads LED
displays the current status of the alarm system (i.e., armed or
disarmed). If the alarm system is armed, the PIN pads red LED
comes on. If the alarm system is disarmed, the PIN pads green LED
comes on.
When the Disarm and/or Arm option is enabled, the user can press
the appropriate key (0 or 1, respectively) to control the alarm
system. After the user successfully arms or disarms the alarm
system through the PIN pad, the updated alarm system status
displays.
The Control door mode option causes the door mode to automat-
ically change when a user arms or disarms the alarm system from
the PIN pad. If the user arms the alarm system, the door mode
changes to Secure. If the user disarms the alarm system, the door
mode changes to Unlock.

Door mode
The Door mode function allows an authorized user to control the
operating mode of a door from the PIN pad. This function
provides the following options:
Secure (key 0)
Unlock (key 1)
Lock (key 2)
When an authorized user selects this function, the LED on the PIN
pad displays the currently active door mode as follows:
Blank = Secure mode
Green = Unlock mode
Red = Lock mode
If only one option is enabled for this function, the user can imme-
diately set the door mode just by selecting the function. In this case,
the user is not required to press a second key.
When at least two options are enabled for this function, the user
must press the appropriate second key (0, 1, or 2) to control the
door mode. After the user successfully changes the door mode
through the PIN pad, the updated door mode displays.
Discrete Status
The Discrete Status function allows an authorized user to view the
current status of up to ten DI points from the PIN pad. This func-
tion provides the following options:
First input
Last input
Use the First input parameter to specify the bit offset of the first DI
point you wish to assign to this function. Use the Last input to
specify the bit offset of the last DI point. You can assign a single DI
point to this function by setting the First input and Last input to
the same bit offset.
When an authorized user selects this function, if only one DI point
has been assigned, the PIN pad immediately displays the points
status. If multiple DI points have been assigned, the user is required

to choose the appropriate DI point by selecting the points bit offset

(09) on the PIN pad. A yellow LED on the PIN pad indicates that
this function is waiting for the user to specify a bit offset.
The indications provided by the LED on the PIN pad will depend
on whether or not you have enabled the Intruder Alarm System.
The indications are as follows:
Intruder alarm system enabled:
Green = Selected DI points state matches the Arm Ready
State setting.
Red = Selected DI points state does not match the Arm
Ready State setting.
Yellow = Waiting for user to choose a DI point.
Intruder alarm system disabled:
Green = Selected DI points state matches the setting of
the Green LED State parameter.
Red = Selected DI points state does not match the setting
of the Green LED State parameter.
Yellow = Waiting for user to choose a DI point.
Control Relay
The Control Relay function allows an authorized user to energize
or de-energize, or view the current status of up to eight relays. This
function provides the following options:
First relay
Last relay
Use the First relay parameter to specify the bit offset of the first
relay DO point you wish to assign to this function. Use the Last
input to specify the bit offset of the last relay DO point. You can
assign a single relay to this function by setting the First input and
Last input to the same DO point bit offset.
When an authorized user selects this function, if only one relay has
been assigned, the PIN pad immediately displays the relays status.
If multiple relays have been assigned, the user is required to choose

the appropriate DO point by selecting the points bit offset (07) on

the PIN pad. A yellow LED on the PIN pad indicates that this func-
tion is waiting for the user to specify a relay.
When the user chooses a relay, its current status is displayed on the
PIN pad. If necessary, the user can manually de-energize or ener-
gize the selected relay by pressing 0 or 1, respectively.
The indications provided by the LED on the PIN pad for this func-
tion are as follows:
Green = Selected relay is de-energized.
Red = Selected relay is energized.
Yellow = Waiting for user to choose a relay
Using Door Attributes
Note: Door attributes are not available for use while the door is operating
in the Sec/Code mode. Refer to Sec/Code (Firmware Version 3.22
or Later) on page 9-34 for more information.
Door attributes are used to initiate specific actions in the access

control system when select users perform a key/card read at the
door. You can control the use of door attributes on a per-user basis.
A users personnel schedule will determine whether or not the door
attribute is active for the user. Refer to Personnel Schedules on
page 9-52 for more information.
The following sections describe the available door attributes.
Auto Disarm
By default, if the intruder alarm system is armed and the door is
operating in the Secure mode, the doors access control scheme will
function much like the Lock mode. The armed alarm system will
prevent a user from gaining authorized access through the door
even when the user has a valid card read and is authorized access
according to their personnel schedule.
Using the Auto Disarm feature, you can configure the door to auto-
matically disarm the alarm system when a user is granted access
through the controlled door. No user action is required other than
a normal card read and PIN entry (if required).

Escort Required
The Escort Required door attribute is used to support I/NETs
two-man rule. When an individuals personnel schedule enables
this door attribute, the individual will require an escort in order to
gain authorized access at this door. Refer to Two-man Rule on
Escort
The Escort door attribute is used to support I/NETs two-man rule.
Any individual whos personnel schedule enables this door
attribute can be an escort in order to allow another user to gain
authorized access. Refer to Two-man Rule on page 9-90 for more
information.
Resetting the Anti-Passback Flag

The anti-passback flag is used to prevent multiple people from
using a single key/card to gain entry into an access controlled area.
Once a key/card has been used to enter the secure area, it must be
used to exit that area before it can be used to gain entry again.
Sometimes this flag will need to be reset. For example, people
might leave the area without using the exit reader because of a fire
or other emergency. Or a person may piggy-back on another
users card, exiting with another person without using their own
card. I/NET provides both manual and automatic means to reset
the anti-passback flag.
Automatic (Timed) Reset
Automatic resets entered as part of the door extension. To establish
automatic resets throughout your system, all doors must have reset
parameters entered.
There are two different ways to enter an automatic reset.
The Anti-passback Reset Time field in the Reader Parameters
section of the Door Extensions editor. This field sets the time
period for a staggered reset time, based on when an individual
entered the secure area. The timer starts when an individual
uses a key/card to enter the area. During this time, the
key/card will not open the door. When the timer expires, the

Access Control Elevators
APB flag is reset for this individual, and the key/card is once
again authorized for that door, even if the individual has not
used an exit reader to leave the area.
An APB Reset action in a door mode schedule. This action
clears all APB flags for the door at the specified time. This
reset action overrides the timer described above.
Manual Reset
The operator can manually reset APB flags for an individual, a
tenant, or all individuals/tenants for the door. When an operator
performs a manual reset of the APB flag, an audit trial message gets
generated.
The manual reset is available from the following editors.
The Point Control screen accessed from the Controller
Summary.
Use this screen if you wish to reset individuals from more
than one tenant. This screen allows you to select a tenant, or
all tenants assigned to the door. Within a tenant, you may
select a single individual, or all individuals assigned to the
door.
The Door Summary.
Use this screen if you wish to reset individuals from a partic-
ular tenant, or if there is only one tenant assigned to a partic-
ular door. Since you must select a tenant to reach the Door
Summary window, you cannot select a tenant for the APB
Reset function. Within the selected tenant, you may select a
single individual, or all individuals assigned to the door.
Elevators
The elevator control function works in conjunction with access
control parameters and personnel schedules to control access to
banks of elevators. Enabling the elevator option in the Door
Parameters editor causes the door controller to process each reader
transaction as though it were an entry into an elevator cab.

Elevators Access Control
Note: Changing the elevator parameter setting generates an Elevator edit

audit trail message. Refer to Audit Trail Messages on page 9-15 for
more information.
Elevator Control Schemes

There are two types of elevator control that you can implement
within I/NET Seven:
Traditional Elevator Control Tradition elevator control
allows each elevator to support up to 62 floors. This type of
control has been used for as long as elevators have been
supported within I/NET.
Extended Elevator Control Extended elevator control does
away with floor mapping and allows you to assign floors
directly to tenants. Using this type of elevator control, each
elevator can support up to 79 floors.
You can use either type of control, or a combination of both, in
order to implement elevators within your system. By allowing you
to mix both types of control, I/NET gives you the ability to begin
using extended elevator control without reconfiguring your tradi-
tional elevator control system.
The following sections describe each elevator control type.
Traditional Elevator Control
Traditional elevator control allows each elevator to support up to
62 floors. As part of implementing this type of control, you assign
the elevator door point to one or more tenants. You then create
floor maps that associate floors with personnel schedules (see
Defining Floor Maps, below). After performing these tasks, any
individual (or group) assigned to the elevator can gain access to the
floors that are associated with their personnel schedule
Assigning the Elevator to Tenants
Tradition elevator control requires you to assign the elevator to one
or more tenants. Until you perform this task, the Floors button in
the Elevator editor will not be available (i.e., it remains grey).

Defining Floor Maps

Floor maps are only necessary when you are configuring your
I/NET system for traditional elevator control. Floor maps deter-
mine which floors are enabled during each schedule that a tenant
defines for the elevator.
For example:
Tenant 1 has a personnel schedule named 24 Hour defined for
the elevator. This schedule provides 24-hour access, seven days-a-
week. The elevators floor map associates the floor enable points for
floors 1 and 2 with Tenant 1s 24 Hour schedule. This allows
Tenant 1 individuals using the 24 Hour schedule to select floor 1
or floor 2 at any time.
Use the Floors button in the Elevator editor to create floor maps as
follows:
1. Choose a tenant.
2. Select a schedule from up to 31 personnel schedules defined
for the elevator.
3. Select an entry from up to seven access intervals defined for
the schedule.
4. Assign floor enable points to the schedules access interval.
Floor enable points cause the elevator buttons for those floors
to be enabled for selection by the key/card holder.
Up to 62 floor enable points can be assigned to each access
interval. Any floor enable points beyond 62 are not available
when using traditional elevator control. These higher floor
enable points are only available for use with extended elevator
control, as described below.
Repeat these steps as necessary to create floor maps for each of up
to 31 personnel schedules assigned to the elevator by a tenant.
Extended Elevator Control
I/NET Seven now offers an alternative to the traditional elevator
control just described. Enhancements to the I/NET system provide
support for up to 79 floors per elevator.

Instead of assigning the elevator door point to the tenant, you can
implement extended elevator control by assigning floors to the
tenant. The DI/DO pairs that you add to an elevator from the
Elevator editor are listed in the Tenant editor, much like normal
door points. Select the floors that you wish to assign to the tenant.
Implementing Elevator Control

Adding an elevator extension to the door point provides access to
elevator-related features and editors within I/NET and allows
floors to be assigned. Each floor assigned to an elevator must have
an associated DO and DI point. The DO point is used to enable the
elevator button for the specific floor. The DI point provides feed-
back indicating whether the floor button has been selected.
Implementation Sequence
The overall sequence for implementing elevator control in I/NET is
as follows:
1. Use the Resident I/O Points editor to define a door point.
Refer to Doors on page 9-19 for more information.
2. Save the door in the Network Configuration editor. Refer to
Network Configuration on page 4-18 for more information.
3. Use the Door Parameters editor to add an access control
extension to the door and define the door point as an elevator.
4. Use the Personnel Schedules editor to define up to 31 sched-
ules for the elevator. Refer to Personnel Schedules and Shift
Rotations on page 9-52 for a detailed description of this
editor. Add schedules to an elevator as follows:
a. Define a schedule name for a new schedule to be added to
the selected elevator door point.
b. Define access intervals for the schedule. Access intervals
define the days and times when access is allowed. Up to 7
access intervals can be defined for each schedule.
5. Use the Resident I/O Points editor to define a floor enable
point (DO) and a floor selection point (DI) for each floor that
will be assigned to an elevator. These points will typically be
indirect points located in a separate controller on the same

subLAN; however, these points may be located in a separate

controller on another controller LAN or subLAN in the
system.
6. Use the Elevator editor to add an elevator (EL) extension and
floors to the elevator door point. For each floor serviced by
the elevator, select a floor enable point and floor selection
point from those defined in Step 5. Also set the floor selection
time parameter in this editor. Refer to Elevator Extension
on page 9-51.
7. How you proceed from this point will depend upon the type
of elevator control you are implementing. Use the appropriate
steps below:
Traditional Elevator Control
a. From the Elevator editor, use the Floors button to create
floor maps for the elevator. Refer to Defining Floor
Maps on page 9-47 for more information.
b. Assign the elevator (i.e., the door point with the elevator
extension) to the tenant.
c. Assign the elevator to individuals and/or groups as neces-
sary.
Extended Elevator Control
a. Assign floors (i.e., door enable points) to the tenant.
b. Assign floors to individuals and/or groups as necessary.
Combining Traditional and Extended Elevator Control
In order to support the migration of a traditional elevator control
system to extended elevator control, I/NET allows you to use both
types of control simultaneously.
For example, if you have an elevator door point assigned to a
tenant, you can use traditional floor maps to provide access for up
to 62 floors. For the same elevator, you can also take advantage of
extended elevator control by assigning floors directly to the tenant,
controlling access for up to 79 floors.

I/NET takes into consideration both types of elevator control in

order to determine an individuals access rights to a floor at any
given time. Therefore, if an individuals access is being controlled
by a schedule that uses a combination of floor-maps and directly-
assigned floors, access to a floor will be granted if either control
scheme allows access.
Elevator Processing
Once elevator control has been implemented, elevator processing
will proceed as follows:
1. A key/card is passed through a reader at the elevator cab and
validated by the parent door controller.
2. The door controller sends a message to the DPI, MCI, or
I/SITE LAN that contains the elevator floor numbers to which
this key/card holder has been granted access (using the
Personnel Schedule editor).
3. The DPI, MCI, or I/SITE LAN will issue a Start control action
to the discrete output point for each floor enable relay, and
start a timer to limit the amount of time that the key/card
holder has to respond.
4. When a floor is selected, the DI point that is monitoring the
floor button will change state and invoke the following
actions:
a. A transaction message, containing the elevator entry
transaction information, plus a two-character designa-
tion for the selected floor, will be broadcast on the
controller LAN, and forwarded to the parent host(s).
b. A Stop control action is issued to each of the floor enable
points that were started in step 3 once a floor button is
selected or the floor selection time has expired.

Elevator Extension
You can add an elevator extension on each door point (BB08 and
BB09) assigned as an elevator in the DPI, MCI, or I/SITE LAN.
After adding the elevator extension to a point, you must define
elevator parameters such as floor selection time, floor designation
description, button enable point and button selection point.
Floor Selection time
Enter the amount of time in seconds that the key/card user has to
make a selection from the floor buttons in the elevator cab. After
this time limit expires, the floor buttons are disabled. The key/card
user must successfully perform another key/card read to enable the
floor buttons. When a selection is made, the floor buttons are
disabled and a message is sent to the host with the floor designation
description attached to the elevator entry message.
Floors
For each elevator floor extension assigned to a point in the DPI,
MCI, or I/SITE LAN, there must be an associated DO and DI point
attached to the elevator extension. This association of DO and DI
point produces a closed-loop feedback allowing the controller to
identify an elevator floor selection with each successful key/card
reader access.
Floor Index
I/NET allows you to add, delete, or modify a floor index for an
elevator point. The floor index is a number (162) that will typi-
cally represent the floor number. When adding a floor index, you
define a floor designation using one or two alphanumeric charac-
ters. For example, the first level of a basement could be represented
as B1. The floor designation appears along with any messages
generated by this point.
Button Enable
Each floor is assigned a button enable point that energizes after a
successful key/card read. The button enable point is typically an
indirect point with its parent point (an external DO point) located
in another controller.

Personnel Schedules and Shift Rotations Access Control
Button Selection
Each relay point must have a DI point assigned to provide a closed-
loop feedback to the controller, indicating which floor button is
selected by the key/card holder.
Personnel Schedules and Shift Rotations

You can define multiple time schedules for each door within your
I/NET system. These door-specific schedules determine when indi-
viduals shall be allowed to gain access or access user-defined PIN
pad functions.
When you assign a door to an individual or to a group, you must
specify which one of the doors personnel schedules the individual
or group shall use. This schedule, along with the doors current
mode (i.e., Lock, Secure, or Unlock), shall be used to help deter-
mine if an individual is allowed to gain access through the door.
Personnel schedules are also used to determine whether or not a
particular door feature will be available to the current user. Door
features are supported on door controllers loaded with firmware
version 3.18 or later. Refer to User-definable Door Attributes and
PIN Pad Functions on page 9-36 for more information about this
feature.
Another use of personnel schedules is to define shift rotations to
control access. This feature is supported on door controllers loaded
with firmware version 3.01 or later. Refer to Shift Rotations on
Personnel Schedules
You can assign up to 31 personnel schedules to each door. Each
personnel schedule can contain up to seven access intervals. An
access interval is the time period during which a key/card can
access the door. As part of the process of assigning a group or indi-
vidual to a door, one of the schedules is selected. Thereafter, this
particular schedule is used to grant or deny access when a key/card
is presented at the door.

Access Control Personnel Schedules and Shift Rotations
Note: Personnel schedule changes generate a Personnel Schedule edit

more information.
Personnel schedules are similar to the schedules defined in the

Time Scheduling editor, but they do not have any actions. Instead,
each schedule can contain up to seven access intervals defined with
a start and stop time entered in 24-hour format. You can then
assign the schedule you create as a temporary schedule, a special
day schedule, or a regular schedule for any day of the week.
Personnel schedules contain the following parameters:
Begin
Enter the time at which you want the access interval to begin. Enter
time in 24-hour format.
End
Enter the time at which you want the access interval to end. Enter
time in 24-hour format. For example, an entry of 23:59 will grant
access up to 23:59:59.
Days of the Week
The days of the week are listed from left to right. Enable days as
necessary and assign begin/end times. You can assign the same
begin/end times to more than one day of the week.
Special Days
These fields are labeled S1 through S7. A special day, typically a
holiday, is a schedule consisting of the beginning and ending times
you want to occur on the special day. The actual special day
schedule is defined in the controllers Special Days editor. All
normal scheduling in the controller will be ignored on a special day
and only the schedules associated with the special day are honored.
Temporary Schedules
Once you define the begin and end times, move to the temporary
row. Set the temporary schedule to N, 1, 2, or B for each day of the
week. N is no temporary schedule, 1 is temporary schedule #1, 2 is
temporary schedule #2, and B is both temporary schedules. You

Personnel Schedules and Shift Rotations Access Control
can define temporary schedules up to one week in advance. Once

the day containing the temporary schedule is over, the temporary
schedule indicator disappears from the weekday schedule. If you
want a different temporary schedule, you need to redefine one of
the two available temporary schedules.
Caution: Temporary schedules override special days and regular schedules.
Features
Note: Door features are only available if the selected door meets the
following requirements:
The door controller is loaded with firmware version 3.18 or later.
For PIN pad functions, the keypad must provide an 8-bit burst
output.
The DPU7920 with firmware version 3.16 also provides door features
except for the attributes used for the two-man rule.
The door features that can be enabled in a personnel schedule are

unique for each door and reflect the doors current configuration.
The actual features that are available will depend on which features
have been defined for the door you have selected.
Enabling a particular door feature in the personnel schedule allows
an authorized user to use the feature during the time period speci-
fied in the schedule.
Refer to User-definable Door Attributes and PIN Pad Functions
on page 9-36 for more information about door features.
Note: The access control system does not support a master/slave scheduling
relationship between points as does the standard I/NET Time Sched-
uling editor.

Access Control Personnel Schedules and Shift Rotations
Shift Rotations
Note: This feature is supported only in door controllers loaded with firm-
ware version 3.01 or later.
Among the personnel schedules that you can define for each door,
you can also define shift rotations. A shift rotation is a collection of
personnel schedules that are activated in sequence and at a speci-
fied interval.
Rotation List and Order
The Shift Rotation editor provides a complete list of all personnel
schedules defined for the selected door. Using the Add and
Remove commands, you can choose which personnel schedules to
include in the rotation. You can also use the Move Up and Move
Down commands the adjust the position of a highlighted schedule
in the list.
When you assign a shift rotation to an individual or group door, its
personnel schedules are activated one at a time, beginning with the
top-most personnel schedule in the list. When the time interval you
specify in this editor expires, the next personnel schedule in the list
is activated. After the last personnel schedule in the list has been
used, the top-most personnel schedule is activated once again and
this process continues.
Rotation Start
As part of the shift rotation definition, you must specify a start date
and time. By default, the date and time parameters are set to the
current date and time, allowing the shift rotation to start immedi-
ately. If necessary, change these settings to the appropriate date and
time.
Rotation Properties
Specify the Rotation Interval in either Days or Hours. This
interval determines how often the system switches from one
personnel schedule to the next in the shift rotation. The rotation
start date and time settings will be used to determine exactly when
the interval causes the switch from one schedule to the next. For

Access Initiated Control Access Control
example, if the shift rotation starts on January 1, 2003 at 6:00 a.m.,

and the interval is 7 days, then on January 8, 2003 at 6:00 a.m. the
second personnel schedule in the shift rotation will become active.
Note: The parameters displayed within the Access Initiated Control editor
will differ depending on the firmware loaded in your systems control-
lers. Refer to the description of the Access Initiated Control editor in
TCON299, I/NET Seven Operator Guide, for more information.
The access initiated control (AIC) function lets you configure
I/NET to automatically initiate a control action in response to an
access transaction for a selected tenant, group, or individual. Each
DPI, MCI, or I/SITE LAN supports up to 64 AIC actions, regardless
of how many tenants are defined. Although a control action is
directed to a single point, additional actions can be initiated
through the event sequence and event action editors.
When you add a new AIC action, you assign a new AIC number,
define a name, select a tenant, enter a valid discrete output (DO)
point, and assign individual numbers. When assigning individual
numbers, you can choose to assign all individual numbers defined
for the tenant, specific individual numbers defined for a group, or
specific individual numbers associated with the tenant. Whenever
a selected key/card transaction is processed for a matching tenant
code and individual number, a control action (start/stop) is issued
to the DO point.
Note: Access initiated control changes generate an AIC edit audit trail
message. Refer to Audit Trail Messages on page 9-15 for more infor-
mation.
Control Actions
Note: The parameters to which you can assign control actions will differ
depending on the firmware loaded in your systems controllers. Refer
to the description of the Access Initiated Control editor in TCON299,
I/NET Seven Operator Guide, for more information.

Access Control Access Initiated Control
You can enter a control action (none, start, or stop) for any corre-
sponding key/card transactions. The stop action is not available
for any of the Denied... key/card transactions. The start control
action will issue a control command 0 and the stop control
action will issue a control command 1. These control actions are
the equivalent of an event sequence defined with a Start or Stop
action. Refer to Chapter 7, Point Extensions for a description of
event sequences.
Doors
I/NET lists all of the tenants doors associated with the selected SLI.
You must decide which of the tenants doors will have the AIC
action assigned to them.
Individual Numbers
When assigning individual numbers to an AIC, you can assign all
individual numbers defined for the tenant or you may assign
specific individual numbers. If you choose to assign specific indi-
vidual numbers, all individuals assigned to the current tenant are
available for selection. Selecting Group will cause the All Yes and
All No functions to affect only the individuals associated with the
group for easier selection.
I/NET lists each individual by individual number, and includes the
last name, first name, group assignment, and record type. You can
decide which specific individual numbers within this group/tenant
you want to trigger the selected control action. You can select All
Yes, All No, or select each number individually.
Before you can assign specific individual numbers, you must first
enter a base (starting) individual number (132,000). The
maximum number of individuals available for each AIC is 500. You
must add a second AIC if more than 500 consecutive individual
entries are desired for a specific AIC action. You must also add a
second AIC if a desired individual number exceeds the base
number by 500 or more, even if less than 500 individual numbers
have been assigned to the AIC action. For example, if an existing
AIC has a base individual number of 200, then the maximum indi-
vidual number that can be assigned to this AIC is 699. If you wish
to assign individual number 800, you must create a new AIC with

Key/Card Translations Access Control
a base individual number of at least 301. The 500 consecutive indi-

vidual limitation does not apply when assigning all tenant indi-
vidual numbers to an AIC.
Key/Card Translations
Note: If you directly assign a key/card to an individual, and later translate

the same key/card for another individual, only the translated
key/card will be operational within I/NET.
If desired, you may use the Key/Card Translation editor to translate

large key/card numbers, such as those used by I/DISC and Water-
mark, into smaller numbers. I/NET Seven is capable of translating
large key/card numbers directly to a lower number. Refer
toKey/Card Numbers on page 9-4 for more information.
Note: All individual key/card numbers that have a corresponding transla-

tion table entry will be resident in the door controller. Refer to Data-
base Caching in the Door Controller on page 9-10.
The Key/Card Translation editor translates the I/DISC and Water-

mark key/cards as well as the following additional key/card types:
ABA-115
ABA-85
Wiegand 26-bit
Wiegand 32-bit
Support for these additional key/card types is available when the
key/card reader is connected to a door controller configured to use
key/card translations (i.e., DIP switch 7 on the DPU is ON or the
Card Translation option is enabled in the Door Extension editor).
Refer to TCON116, DPU7910A Installation Guide, TCON117,
DPU7920 Installation Guide, or TCON312, 1200-series SCU
Installation Guide for more information).
Note: Key/tag translation editor changes generate a Translation table edit

more information.

Access Control Tenants
I/NET allows you to create a maximum of 128 sets of translation

parameters. The key/card translation parameters are described
below:
Source
This parameter defines the starting key/tag number to be trans-
lated. This can be 16 digits long.
Target
The Target parameter defines the key/tag number (132,000) to
which the source key/tag number (defined above) will be trans-
lated. The remaining source numbers will be translated to consec-
utive key/tag numbers following the target number you define here.
Count
This is the total number of key/tag numbers to be translated (0
32,000).
Tenant
Define the tenant number (1 to 255) to which this block of key/tags
will be assigned.
Key/card Translation Example:
Parameter Settings: Result:

Source = 123456 Key/card number 123456 = 1000
123457 = 1001
Target = 1000
123458 = 1002
Count = 5000

128455 = 4999
Tenants
The concept of tenants, as used in I/NET, lets you assign access
controlled doors to more than one tenant. Tenants are usually
different groups that inhabit the same facility but that are

Tenants Access Control
controlled separately. For example, a single large building may be

inhabited by several companies. Each company would be consid-
ered a separate tenant.
I/NET allows you to add, copy, modify, and delete tenants. If you
delete a tenant from your access control system, all references to
that tenant are purged from access editors. Deleting the tenant will
not delete the individuals that were assigned to the tenant, but their
key/cards will no longer be accepted at any of the doors. Also, if you
create a new tenant by copying an existing tenant, all door assign-
ments associated with the existing tenant are copied to the new
tenant.
When you add a tenant to the system, you must define the block of
individual numbers that will be allocated to that tenant and you
must define through which doors that tenant will have access.
Note: Tenant editor changes generate a Tenant edit audit trail message.
Refer to Audit Trail Messages on page 9-15 for more information.
The following parameters are available:

Tenant Number
Assign a unique number for this tenant (1255). This number is
used throughout the I/NET system to uniquely identify this tenant.
Tenant Name
Use up to 16 characters to define the tenant name. The tenant name
is saved only in the workstation database. This means that the same
tenant can have different names at different workstations.
Tenant Code
Use up to 8 digits to define the tenant code. This is the tenant code
that is embedded in the key/cards. Depending on the key/card tech-
nology, this code is commonly referred to as the Facility code or
the Site code. This field is not available for Tenant 0.
First Individual Number
Define the starting individual number for this tenant (132,000).
Any individual numbers less than the number you define here are
not accepted for this tenant. This field is not available for Tenant 0.

Access Control Tenants
Number of Individuals
Define the total number of individuals available to this tenant (1
32,000). The absolute limit is 32,000 individuals for a single tenant.
If a single facility requires more than 32,000 individuals, you can
define multiple tenants with matching Tenant Codes. This field is
not available for Tenant 0.
Although I/NET supports up to 32,000 individuals per tenant, the
model type and revision date of a tenants door controllers will ulti-
mately determine how many individuals will be supported. The
following table shows the capacity of various door controllers. For
any door controller with revision 2.2x or later firmware, you would
have to define multiple tenants in order to reach the door
controllers maximum storage capacity.
Table 9-5. Door Controller Capacities
Firmware Maximum Number

Door Controller
Revision of Individuals
DPU7910,
2.1x and earlier Up to 24,000 per door
DPU7920
DPU7910,
Up to 48,000 per controller
DPU7920 without DPU48K
2.2x to 3.23
DPU7920 with DPU48K,
Up to 48,000 per door
SCU1284
DPU7920 with DPU48K,
3.24 and later Up to 64,000 per door
SCU1284
If assigning a door to a tenant causes the allocation of individuals

for a single door controller to exceed the door controller limit, you
will get an error message. If you violate any of these limits, an error
message appears on your screen.
Disabled
Use this checkbox to deny access to all individuals for this tenant.
All key/cards for individuals assigned to this tenant will be disabled.
This field is not available for Tenant 0.

Groups Access Control
This function allows you to quickly prevent all members of a

particular tenant from entering the building or other access-
controlled area, providing security during transitional periods
such as when adding or deleting a tenant, or in an emergency situ-
ation.
When a tenant is disabled, the tenant selection display in all
summary lists and drop-down boxes shows Disabled instead of the
number of keys/cards assigned to the tenant.
Warning: This checkbox setting does not take effect until you select OK to exit
the Tenants editor.
Groups
Individuals can be collected in groups to simplify access control
parameter definition and maintenance. A group is defined for a
particular tenant. You cannot copy a group from one tenant to
another, nor can you assign an individual to a group from a
different tenant. The exception is groups defined for Tenant 0,
which are global groups available to all tenants. Global groups are
designated by a ~ symbol in front of the group name.
I/NET allows you to add, copy, modify, or delete a group. Groups
are represented by a unique 64-character name.
Note: When you edit a group, I/NET generates a Group edit audit trail
message to provide a high-level audit trail for group updates. The
message contains the date and time the edit was performed, the name
of the edited group, and the initials of the person who did the edit.
If you delete a group, all individuals assigned to that group remain

in the system but they cannot gain access through any door, unless
they have individual access.
If you add or modify a group, define the following:
Group parameters
Door selection

Access Control Groups
Note: Groups defined for Tenant 0 (all tenants) do not have group parame-
ters.
Group Parameters
Groups are defined using the following parameters:
Record Type
Note: When you assign an individual to a group, the individuals access

rights will be determined by the combination of their individual and
group record types. The following description (i.e., group record type)
assumes that the individual record type is set to Permanent. Refer
to Combining Individual and Group Record Types on page 9-79 for
more information.
The default record type for a group is Permanent. This allows all
individuals assigned to this group to be granted access based on the
personnel schedule assigned to each group door.
Selecting Temporary in this field causes all individuals in the
group to be processed as temporary. The groups begin and end
date/time parameters must be satisfied before access is granted.
Selecting Disabled allows you to preprogram a group and its
associated individuals and activate them at a future time, or even
immediately deny access to all group doors until the record type is
changed back to Permanent or Temporary.
Begin Date/Time
Enter the date on which the temporary access begins, in
MM/DD/YY format. Enter the time on which time temporary
access begins, in 24-hour HH:MM format.
End Date/Time
Enter the date on which the temporary access ends, in MM/DD/YY
format. Enter the time on which time temporary access ends, in 24-
hour HH:MM format.
Note: The defaults associated with the temporary parameters begin at

00:00 a.m. on the day the group was added and end at 02:00 a.m. the
following day.

Individuals Access Control
Door Selection
Door selection allows you to define those doors to which key/card
holders in this group have access. Only those doors assigned to the
current tenant are available. When you select a door, you then
select schedules for the doors to be available to this group. From the
Group editor, you may add, modify, copy, or delete any personnel
schedule.
You may assign a group to one or more existing groups, making it
a member of the selected groups. Any personnel schedules selected
for the groups doors will override the schedules for the referenced
group(s). Refer to Group Hierarchy on page 9-81 for more infor-
mation on access priority when multiple groups are involved.
Individuals
I/NET lets you add individuals to your access control system. You
assign an individual number and card number to individuals,
assign schedule access to doors, and populate the users personnel
record. If there are multiple tenants, you choose the tenant to
which the individual belongs.
The personnel database table is a global database table that is main-
tained by the filemaster host and distributed to each workstation
on the LAN. When you delete an individual from your access
control system, the individual is purged from the system. I/NET
sends a message to every door controller that controls a door
through which the individual has access.
When you add or modify an individual, the system displays the
following editors:
Individual parameters
Door selection
Note: Individuals editor changes generate an Individual edit audit trail

message to provide a high-level audit trail for individual updates.
The message contains the date and time the edit was performed, the
site number, the individual number, and the initials of the person
who performed the edit.

Access Control Individuals
Individual Parameters
Note: The type of information displayed within the Individuals editors, as
well as your ability to add, delete, or modify individuals, is depen-
dent upon the privileges assigned to your host password (refer to
Host Passwords in Chapter 4, Host Functions, for more informa-
tion).
Define parameters for each individual in your access control

system. The following parameters are available:
New Individual Number
Use this parameter to assign a number to the individual. The range
of valid values for this parameter will depend on the First Indi-
vidual Number and the Number of Individuals defined for the
tenant (refer to the description of these parameters starting on page
9-60 for more information). When entering a new individual, the
system automatically defaults to the next available number. The
number that you assign to this individual must fall within the range
of individual numbers assigned to the tenant. A maximum of
32,000 individuals can be assigned to a tenant.
Card Number
Note: The Card Number parameter, described below, is displayed only if

the privileges assigned to your host password allow you to view and
modify this information (refer to Individual Field Selection on
page 4-14 for more information).
I/NET allows you to assign a large key/card number directly to an
individual, or translate the number using the Key/Card Translation
table. However, within a single tenant, I/NET will not allow you to
perform both actions with the same key/card number or with the
same individual. If you directly assign a key/card to an individual,
and later translate the same key/card for another individual, only the
translated key/card will be operational within I/NET. Refer to
Key/Card Numbers on page 9-4 for more information.
Use the Card Number parameter to define the value that is encoded
within the individuals key/card. You may enter the card number as
either a hexadecimal (base 16) or decimal (base 10) value; the other

scale will be calculated automatically. Rather than manually

entering this value, I/NET allows you to optionally read the value
into the system from an I/DISC wand or Wiegand reader connected
directly to the host workstation (refer to the Supply Card Number
from Reader option described on page 9-83 for more informa-
tion).
Group Name
This is the name of the group, if any, to which the individual is
assigned. The * symbol indicates that the individual is a member of
more than one group. The ~ symbol indicates a global group
(available to all tenants). A user may be assigned group access in
addition to individual access. The group name assigned must
already exist before the system will allow you to assign an indi-
vidual to this group. Refer to Groups on page 9-62 for group
explanation.
Last Name
Use up to 50 characters to define an individuals last name.
First Name
Use up to 50 characters to define an individuals first name.
Fields 3-18
Each tenant has an associated access control database table. You
may customize the names of fields 3 through 18 as you wish (refer
to Field Names on page 9-75). The fields accept up to 50 charac-
ters, and can be used for any number of different uses: drivers
license number, vehicle type, employee number, date of birth,
height, weight, and so on.
Note: One of the user fields may be designated as a Unique Field in the
Access Control - Options editor (see Options on page 9-83). The
designated Unique Field may be left blank. If a value is entered, it
must be unique across all tenants and individuals.

Card
The individuals current card numbers are listed in both the hexa-
decimal and decimal values. Refer to Card Number on page 9-65
for more details. Use the Add New Card option to enter additional
card numbers for this individual.
Each card number must be unique across all users and tenants. You
may have multiple individuals with no card number (null), but if
you assign a card number of zero (0), only one individual can have
that card number.
Hex Number
The number for this card, in hexadecimal format. If you enter the
card number in decimal format, this value is calculated automati-
cally.
Decimal Number
The number for this card, in decimal format. If you enter the card
number in hexadecimal format, this value is calculated automati-
cally.
Resident in DPU
This parameter indicates whether this card will be stored as a resi-
dent record in the device controlling the door point(s) assigned to
this user. A card that is resident in the door controller can be veri-
fied even if communication has been lost between the door
controller and the SLI. Resident records are given priority in the
door controllers memory. Refer to Database Caching in the Door
Controller on page 9-10.
Note: All individual key/card numbers which use a translation table will be
resident in the door controller, regardless of the setting of this param-
eter. Refer to Database Caching in the Door Controller on page
9-10.
This option cannot be activated if the card number field is blank.

This option is only available on door controllers with firmware
revision 2.20 or later.

Disabled
This field is used to temporarily disable an access card, or disable a
card without deleting it from the users record. A disabled card will
be denied entry at all access controlled points.
Image
This parameter allows you to select an image of the individual. This
image can be displayed in AMT when the individual triggers an
event or alarm (see Image Verification in Chapter 3, System
Messages).
Image Path
Specify the local or remote path to the image. If the picture resides
on a remote device (i.e., on another PC's drive for example), or if
the picture is on your local drive and must be accessible from other
I/NET host workstations, ensure that you define a UNC path (see
description below) to the picture. Otherwise, if an operator at
another I/NET host workstation double-clicks the image thumb-
nail, I/NET will be unable to locate and display the full-size image.
Universal Naming Convention (UNC) In a network, the
Universal Naming Convention (UNC) is a way to identify a shared
file without having to specify (or know) the storage device on which it
resides. In the Windows operating system, the UNC name format is:
\\servername\sharename\path\filename
Supported Formats
The following file types are supported:
.JPG .TIF
.BMP .PNG
.GIF
If your image file is in a format other than the ones listed, you must
first convert it to one of the supported formats using a third-party
graphic program.

Image Thumbnails
To conserve memory resources, the selected image will be resized to
fit the display window (maintaining aspect ratio), and a thumbnail
version is saved to the database as a .JPG file.
Each thumbnail is 222 x 191 pixels, and consumes approximately
46 KB of memory space. When adding a large number of thumb-
nails, be aware of the size of your database file. Refer to I/NET
Software in Chapter 1, System Configuration.
Record Type
Caution: When defining the Record Type, be aware that it is the job of the
Automatic DPU Restore function to download Temporary indi-
vidual records to door controllers beneath specific links. If you have
not enabled the Automatic DPU Restore function for a link, no
temporary individuals will be granted access through the link's doors.
Note: When you assign an individual to a group, the individuals access

rights will be determined by the combination of their individual
record type and their group record type. Refer to Combining Indi-
vidual and Group Record Types on page 9-79 for more information.
This parameter determines if the individual has permanent status,

is temporary, or if the entire record for the individual is disabled.
An individual with a temporary status is a visitor with a temporary
schedule that has a begin and end date. The Disabled record type
allows you to enter all of the individual parameters into the
personnel database, including door and schedule assignments,
without allowing access. A disabled individual parameter record is
activated when the record type is changed to permanent or tempo-
rary.
Temporary Schedule
The following begin and end parameters are applicable only when
the individuals record type is defined as Temporary. The default
date and times associated with the temporary schedule permits
immediate access for the visitor and grants access up to 02:00 a.m.
the following day.

Begin Date
Enter the date on which you want the visitors access capability to
begin, in MM/DD/YY format. The default is the day the individual
was added to the system.
Begin Time
Enter the time at which you want the access capability to begin on
the date listed above, in HH:MM 24-hour format. The default is
00:00 on the day the record was added to the system.
End Date
Enter the date on which you want the visitors access capability to
expire, in MM/DD/YY format. The default is the day after the date
that the record was added.
End Time
Enter the time at which you want the access capability to expire on
the date listed above, in HH:MM 24-hour format. The default is at
02:00 a.m. on the next day from the time the record was added.
APB
This parameter is used to determine the system response if a user
attempts to enter a zone without exiting, when the door(s) are
controlled by anti-passback and/or anti-tailgate. The following
options are available:
Hard (default) access is denied, generates an alarm.
Soft access is granted, generates an alarm.
Graced access is granted, no alarm is generated. This
effectively cancels anti-passback for the individual.
Note: This option is only available in systems using large key/card numbers
(see Large Number Support on page 9-5). The anti-passback
scheme is only active if anti-passback is activated for the door (see
Anti-passback on page 9-25). The same scheme is used for both
anti-passback and anti-tailgate, if activated (see Anti-tailgate on
page 9-25).

PIN
The personal identification number (PIN) for this individual. The
PIN is only required at doors configured to use a keypad to control
access. The default PIN is automatically generated using the
selected algorithm (see PIN Algorithm on page 9-86). This field
is read-only unless the User Defined PIN parameter is activated in
the Access Control Options editor (see User Defined PIN on page
9-85).
Refer to Personal Identification Numbers (PINs) on page 9-77
for more information about this feature.
Note: I/NETs PIN function also supports a duress code for use in emer-
gency situations. See your I/NET system administrator for more
information about this feature.
Issue Number
Note: If your access control system is configured to use Wiegand cards, the
Issue Number described below will only affect the PIN assigned to the
individual. The card will never generate a Deny Issue message,
regardless of the Issue Number setting.
Set the issue number to a value from 1 to 4. The issue number on

each key/card is checked during key/card validation. If the key/card
is not the most recent issue, I/NET denies access and generates an
appropriate message.
Issue number is not used for systems using large key/card numbers.
Refer to Key/Card Numbers on page 9-4.
Door Selection
Define those doors to which this individual is to have access. Only
those doors that have already been assigned to the currently
selected tenant are available.
If the same door is selected for an individual and for the group to
which that individual is assigned, the individual assignment always
overrides the group assignment. This allows individuals to be

assigned to a group from which they receive the bulk of their access
privileges, but still be offered individual treatment for selected
doors. See Figure 9-4 for the logical flow of door assignments.
I/NET displays the door address and point type, the name assigned
to the point, and individual schedules by number and name. Group
schedules are also displayed by number and name if the individual
is assigned a group name.
Selectively Assigning Doors to the Individual
Enable individual access to a door by selecting a door and choosing
one of 32 available schedules. I/NET allows you to add, delete,
modify, or copy a schedule. You can then manipulate personnel
schedules without having to exit this editor and go to the Personnel
Schedules editor.
Note: Each door in the system supports 32 unique schedules, including a

schedule #0 which is a No Access schedule.
Assigning Group Doors to the Individual

Enable group access to a door by selecting one or more existing
groups. When multiple groups are selected, the order of the groups
in the Member of list determines which group schedule will take
priority. Refer to Group Hierarchy on page 9-81 for more infor-
mation on access priority when multiple groups are involved.
Assigning Secondary Group Doors to the Individual
Note: This feature is supported only in door controllers loaded with firm-
ware version 3.01 or later.
On occasion you may wish to temporarily supplement an indi-

viduals access privileges for selected doors. One way to accomplish
this task is to make manual adjustments to the individuals access
privileges on the day that you wish the supplemental access to
begin. You must then remember to restore the individuals previous
access privileges (assuming you remember what they were) once
the need for the supplemental access has expired.

A better way to accomplish the task just described is to assign a

secondary group to the individual. Secondary group schedules
supplement the schedules that are already assigned to the indi-
vidual. For example, if an individual is allowed access through a
door Monday through Friday, you can assign the individual a
secondary group that allows Saturday and Sunday access. The indi-
vidual will then have 7-day-a-week access as long as the secondary
group assignment is in effect.
Any group defined for the current tenant can be used as a
secondary group. When assigning a secondary group to an indi-
vidual, define a beginning and ending date and time. The
secondary group schedules will be active only within the dates and
times you specify.
Door controllers store secondary group schedules separately from
other schedules. When a user attempts to gain access through an
access-controlled door, the door controller first checks to see if the
individual is allowed access because of his or her individual or
group door assignments (see Figure 9-4). If these assignments do
not provide access, or if they specifically deny the user access, the
door controller then checks for an applicable secondary group
schedule. If a secondary group schedule provides access, the user
will be granted entry.
The parallel storage of secondary group schedules causes them to
be logically ORed with the individuals other door schedule assign-
ments, effectively allowing the individual to have two active
personnel schedules at once.
GOTO
GOTO lets you define a particular field at which you want the
displayed listing to start. For example, if the display order is set to
individual number, you can enter the individual number at which
you want the listing to start. This option is useful if you have many
individuals in your system and simply scrolling through the list is
too time-consuming.

Access Request
Door Schedule
Check Defined Yes
Within
Indiv/Group Time Range?
Doors
"-- No Access" No
or
"-- Unselect"
Doorr Schedule
Check
Defined Yes
Secondary Within
Group Time Range?
Doors
"-- No Access" No
or
"-- Unselect"
Access Access
Denied Granted
Figure 9-4. Logical Flow of Door Assignments
Allocate Range
The allocate range function allows you to add a large number of
individual numbers to the system at once. This is useful for easily
adding a consecutive range of individuals to the system with group
access. Once you allocate a range, you may enter the individual
information using the Modify function from the Individuals editor.

The system prompts you if the range is invalid (Invalid Entry

message), or if the individuals already exist (Individual number
conflict message).
The system then allows you to choose the group name, or select
none. The group must already exist within the system.
Note: The system will display the individual numbers as they are being
created and downloaded. Depending on the range of individuals, it
may take several minutes to complete the process.
Field Names
Each tenant within the system may create a unique set of text to
represent user-defined field entries #1 through #16 in the individ-
uals parameter editor. The field names may be modified to better
represent the contents of the record entry (i.e., field #1 can be
changed to Department #). Enter any 50 alpha-numeric charac-
ters for each field.
Display Options
Note: The actual fields displayed within the Display Options editor will be
determined by the access rights associated with your host password.
The information below assumes that all parameters are displayed.
Refer to Individual Field Selection in Chapter 4, Host Functions,
for more information.
The Option function allows you to set the presentation order of the
individuals. The presentation order can be determined based on
record type, individual number, or record field entries. The display
option parameters are as follows:
Permanent Records
This option can be enabled or disabled (Yes or No). Enabling this
option will include all personnel records with a record type of
Permanent.

Temporary Records
Temporary.
Disabled Records
Disabled.
Display Order
This field allows you to determine the presentation order of
personnel records by selecting a record field. For example, selecting
01. Individual causes personnel records to be displayed in order
of their assigned individual number. Selecting 02. Last Name
causes personnel records to be displayed in ascending order by their
last name.
Note: When you base the display order on the hexadecimal card number,
I/NET will not allow you to add, delete, or copy individuals. Choose
some other display order to re-enable the add, delete, and copy func-
tions.
Low/High Individual Number

These are numeric fields allowing you to select a range of individual
numbers. These fields default to 1 and 32,000 respectively. Selecting
a range will limit the display of records to between the two
numbers.
ASCII Text Fields
These fields are alphanumeric fields that allow you to determine
search criteria for data within each field. You may enter up to 50
characters (16 characters for Group Name field), including the
wildcard characters ? and *. The ? wildcard searches for any
single character, while the * wildcard searches for any characters
in that position and after. The default is the * wildcard. Entering
Fo* in the last name parameter would cause the display of all
personnel records containing a last name starting with the letters
Fo, such as Ford, Forney, etc.

Access Control Personal Identification Numbers (PINs)
Personal Identification Numbers (PINs)

A users personal identification number (PIN) is used to provide
access through doors equipped with a PIN pad. The PIN pad
provides extra security under certain circumstances (such as after
hours), by requiring both a card read and manual entry of the
proper code. I/NET Seven allows the operator to define the PIN, if
desired, or to use an automatically-generated PIN.
The method I/NET uses to manage user PINs is selectable in the
Access Control Options editor. Two parameters control the PIN
selection:
User defined PIN This checkbox, when activated, makes the
PIN field editable in the Individual Parameters editor. If the
checkbox is not activated, the PIN will be generated automat-
ically using the algorithm specified below, and cannot be
changed.
PIN algorithm This drop-down box is used to select the
algorithm used to automatically generate PIN codes. This
algorithm determines the default PIN. If the User defined PIN
box is activated, the generated PIN may be changed. Refer to
Access Control Options editor for a description of the algo-
rithm options.
Using the PIN algorithm, I/NET automatically defines a PIN for
each individual you add to the system. If your system is configured
to allow user-defined PINs, you can edit the PIN.
Entering Your PIN at a Door

Note: The maximum number of digits allowed in the user's PIN, and
support for user-defined PINs, will depend on the type and configu-
ration of door controller being used to control a particular door. Refer
to Door Controller Firmware Revisions, below, for more informa-
tion.

Personal Identification Numbers (PINs) Access Control
When attempting to gain access through a door operating in a PIN-

enabled secure mode, you can simply type all digits of your
assigned PIN at the doors keypad. Upon entering the final digit,
the door controller will process the PIN to determine if access is
allowed.
Omitting Leading Zeros

You can omit leading zeros by beginning the PIN entry with the
first non-zero digit. In this case, you must press the # button after
the last digit in order to complete the PIN entry.
Door Controller Firmware Revisions

The way PINs are supported in your access control system will
depend on the type and configuration of the door controller being
used to control a particular door. The following sections describe
how PIN features are supported.
User-defined PINs
User-defined PINs require door controller firmware revision 2.30
or later. I/NET Seven does not verify the door controller's firmware
revision; the User Defined PIN checkbox in the Access Control
Options editor will be active regardless of your system configura-
tion.
If a door controller has a firmware revision prior to 2.30, the only
valid PIN is the system-generated PIN, regardless of the entry in the
Individual Parameters editor. If you have mistakenly enabled user-
defined PINs on a system with older firmware, simply disable user
defined PINs in the Access Control Options editor, and restore the
DPU(s) to return to system-generated PIN numbers.
Note: For best results, do not mix DPU firmware version 2.30 or later with
older DPU firmware versions if you wish to enter user-defined PINs.
It is possible to create a situation where the user's PIN is one number
(system-generated) for certain doors, and another number (user-
defined) on other doors, in which case the PIN shown in the Indi-
vidual Parameters editor would not be accurate for all doors.

Access Control Combining Individual and Group Record Types
Six-digit PINs
Six digit PINs are supported on the SCU1284 and on the DPU7920
with MIP (firmware 3.16 or later). All other door controllers
support PINs with a maximum of five digits.
If your system includes a mix of door controllers (i.e., some
controllers that do support six-digit PINs and some controllers that
do not support six-digit PINs), you should avoid assigning six-digit
PINs. This will prevent users from being locked out of certain doors
because a door's controller will not accept the user's complete PIN.
Generating PINs
You must ensure that the PIN Algorithm parameter within the
Access Control Options Editor is set properly for your application.
Refer to User PIN Code for more information.
The pin generation utility generates a list of PINs for specific card
numbers. A PIN generated within this utility is the same as the PIN
that can be viewed from the I/NET Individual Parameters editor.
This utility provides the following additional benefits:
More than one PIN can be viewed at a time.
PINs can be printed out for later viewing, or printed lists can
be provided to tenants.
When you generate PINs, a PIN table is created. You can print a
PIN report from this table. You can also preview the PIN report
before sending it the printer. Refer to the I/NET Seven Operator
Guide for complete instructions.
Combining Individual and Group Record Types

When you assign an individual to a group or groups, the record
type settings for both the individual and the group(s) will combine
to determine the individuals access rights for specific doors.

Combining Individual and Group Record Types Access Control
Table 9-6 lists the possible combinations of individual and group

record types, and explains how these settings affect the individuals
access rights.
Table 9-6. Individual and Group Access Matrix
GROUP MODE
Permanent Temporary
INDIVIDUAL MODE
None with with Disabled
w/o Doors w/o Doors
Doors Doors
with Doors A A, B A A, D A A
Permanent
w/o Doors X B X D X X
with Doors C C, F C C, E C C
Temporary
w/o Doors X F X E X X
Disabled X X X X X X
Access Rights:
Individual doors Access is allowed through all individual doors during
A
each doors assigned personnel schedule.
Group doors Access is allowed through all group doors during each
B
doors assigned personnel schedule.
Individual doors (temporary individual) Same as A except access is
C additionally restricted to the dates and times defined for the individuals
temporary schedule.
Group doors (temporary group) Same as B except access is
D additionally restricted to the dates and times defined for the groups
temporary schedule.
Group doors (temporary individual/group) Same as B except access
E is additionally restricted to the dates and times defined for both the
individual and the group temporary schedules.
Group doors (temporary individual) Same as B except access is
F additionally restricted to the dates and times defined for the individuals
temporary schedule.
X No doors Access is not allowed through any doors.
Note: When the same door is assigned at both the individual level and at
the group level, the individuals personnel schedule will be used.
In addition to a users individual and group door assignments,
supplemental group schedules also affect a users access privileges.
Refer to Assigning Secondary Group Doors to the Individual on

Access Control Combining Individual and Group Record Types
Group Hierarchy
If the individual is assigned to multiple groups, or to a group that
is a member of another group, the actual access schedule for the
individual is a combination of all the involved groups.
The group displayed on the Door Selection summary indicates
only the topmost group in the Member of list (from the Group
Selection summary) that has a schedule for the door. This is not
necessarily the only group schedule used to determine access for
the individual or group. For example, if the top group does not
have any schedules assigned for this door, the Door Selection
summary will list the second group but it could be the schedule
for the third or fourth group that results in access being granted or
denied at a particular day and time.
Access privileges are determined according to the following hier-
archy:
1. Individual schedule. The system will first check to see if the
individuals schedule allows access at this time.
2. Group A schedule. If the individual schedule has no entry for
this time period, the system will check the topmost entry in
the Member of list on the Groups Selection summary.
Note: No schedule entry is not the same as No Access. If the system finds
a No Access schedule entry, entry is denied.
3. Group B schedule. If the top group in the list has no entry for
this time period, the system moves to the next group in the
list, to check for access.
4. Groups C, D, etc. schedules. The system will continue down
the list of selected groups, until:
a. A group contains a schedule entry for this period. Access
is allowed, unless the entry is No Access, in which case
access is denied.
b. The system reaches the end of the assigned groups
without finding a schedule entry. Access is denied.

Combining Individual and Group Record Types Access Control
If one of the selected groups is a member of another group, then

checking that groups schedule includes checking the schedules of
any groups that group is a member of.
For example, if Group A is a member of Groups X and Y (in that
order), and Group B is a member of Group Z, then the actual hier-
archy of schedules includes groups X, Y, and Z as follows:
1. Individual schedule.
2. Group A schedule.
3. Group X schedule.
4. Group X group schedule (if X is a member of another group).
5. Group Y schedule.
6. Group Y group schedule (if Y is a member of another group).
7. Group B schedule.
8. Group Z schedule.
9. Group Z group schedule (if Z is a member of another group).
10. Group C, D, etc. schedules.
Note: If the schedule hierarchy described above results with access being
denied, the door controller will then check for a secondary group
schedule that would provide access. Refer to Assigning Secondary
Group Doors to the Individual on page 9-72 for more information.
Because of this hierarchy, a general rule of thumb when assigning

groups is to order the groups from specific (special access limited
to a few individuals) at the top to general at the bottom.

Access Control Options
Options
The system allows the following system parameters to be modified
from the access control editor:
Supply Card Number from Reader
Note: The Supply Card Number From Reader option described below is
available only after you set the AC Reader Type to I/DISC or
Wiegand and the AC Reader Port to a COM port in the Configure
program. Refer to TCON298, I/NET Seven Getting Started, for more
information about configuring I/NET.
This option can be enabled or disabled. Enable this option if you

want to use an I/DISC wand or a Wiegand reader to enter card
numbers in the Individuals editor. This option also enables you to
determine the identity of an unidentified card or I/DISC tag by
reading it from the Individuals Summary. The individual is high-
lighted if a successful match is found.
Second Password Required for Individuals
This option is provided in order to help prevent I/NET operators
from making unauthorized changes to the Individuals records
within your access control system. With this option enabled, I/NET
will require a second operator to enter their host password when
you attempt to add, delete, or modify an individual record.
If you are adding or modifying a record, the prompt for the second
operators host password will be displayed when you select OK to
exit the Individual Parameters editor. If you are deleting a record,
the prompt will be displayed after you confirm the delete request.
The second operators host password must meet the following
criteria in order to be accepted:
Defined The second operators password must have already
been added to the system.
Unique The currently logged in operators password cannot
be used again as the second password.

Options Access Control
Authorized The second operators password must have the

Individuals function enabled. Otherwise, I/NET displays an
Insufficient Password Level error message. Refer to Func-
tion Selection on page 4-6 for more information.
I/NET will only accept the second password if it meets the criteria
described above. Otherwise, the action you are attempting will not
be accepted (i.e., no records will be added or deleted, and no modi-
fications to a record will be saved).
Note: You must define the following audit trail parameters before any host
workstations (remote or local) will be capable of receiving audit trail
messages from this host workstation. Refer to Audit Trail Messages
on page 9-15 for more information.
Audit Trail Distribution Group

Select the group (14). A distribution group extends the scope of
the eight-position mask, described below, increasing the available
masking positions to 32.
Audit Trail Distribution Mask
Enable or disable each of the eight available positions to create the
audit trail distribution mask. Audit trail messages will then appear
at the host workstations with a matching distribution group and
active mask position. Refer to Masking in Chapter 3, System
Messages for a complete discussion of masking.
Audit Trail Cell Number
This field is used for grouping events in displays and reports. Enter
a number between 0 and 1,023.
DPU Dial Type
Immediately Dial affected remote sites immediately
following access control edits. The DPU dial delay will be
honored before dialing begins.
Scheduled Dial affected remote sites at a specified time (see
DPU Dial Delay/Schedule), following access control edits.

Never Do not dial remote sites automatically for access

control edits. In this case, you must manually dial the remote
site and perform a station restore to the affected door
controller.
DPU Dial Delay/Schedule
Use this parameter to specify when the system should begin dialing
remote sites. Depending on your selection under DPU Dial Type
above, the field label will read either DPU Dial Delay or DPU
Dial Schedule.
DPU Dial Delay
This option is used when the dial type is set to Immediately, and
allows you to set a delay period before the first dial attempt. Enter
the desired length of the delay in minutes, up to 60. An entry of zero
(0) means that the system should begin dialing the remote site(s)
as soon as the edit is completed.
DPU Dial Schedule
This option is used when the dial type is set to Scheduled, and
allows you to enter a specific time of day to dial the remote site(s).
Enter the time in 24-hour format. If you perform edits that require
a remote site to be dialed, and the time specified in this parameter
has already passed, the system will dial the sites on the following
day.
User Defined PIN
This option specifies whether the operator can edit the personal
identification number (PIN) for individuals using the Individual
Parameters editor (see PIN on page 9-71).
When this feature is activated, the selection in PIN Algorithm
(below) specifies the method used to generate the default PIN. If
this feature is not enabled, the generated PIN is read-only.
This feature requires door controller firmware version 2.30 or later.
You must use system-generated PINs for door controllers with a
firmware revision prior to 2.30.

Options Access Control
PIN Algorithm
This option specifies which algorithm is used to calculate the
default personal identification numbers (PINs) for key/card
holders. If the User defined PIN parameter is activated, the default
PIN can be edited from the Individual Parameters editor. If not, the
PIN is read-only at the host workstation (i.e., within the Individual
Parameters editor and the PIN Generator utility). The following
options are available:
None Choose this setting if you do not wish to automati-
cally generate user PINs. When entering a new individual, the
operator must manually enter a PIN; you will not be able to
save the individual parameters until a PIN is entered. This
option is only available if the User Defined PIN checkbox is
activated.
Standard Choose this setting if your access control system is
configured to use any reader type other than Wiegand 66.
Wiegand 66 Choose this setting only when your access
control system is configured to use Wiegand 66 readers.
Recycle Bin Enable
Activate this option to have I/NET temporarily store deleted access
control records in a recycle bin. Using this feature, you can restore
deleted individual, group, and tenant records at a later time. You
can also purge the records from the recycle bin in order to perma-
nently delete them. Refer to Recycle Bin on page 9-16 for more
information.
Recycle Bin Autopurge Age
This parameter is available only if you have activated the Recycle
Bin Enable option. Use this parameter to have I/NET automatically
purge records that have been deleted for a specified number of days
(from 0 to 127). A setting of zero (0) prohibits I/NET from purging
deleted records because of their age.

Empty Recycle Bin at Log Off

This parameter is available only if you have activated the Recycle
Bin Enable option. This feature allows you to configure I/NET to
automatically purge deleted records from the recycle bin when the
user logs off.
Choose any of the following three options for this parameter:
Never - This setting prevents I/NET from purging deleted
records from the recycle bin at system log off.
Prompt - This setting causes I/NET to display a prompt at
system log off if deleted records reside in the recycle bin. The
prompt allows the user to choose whether or not the records
will be purged.
Always - This setting allows I/NET to silently purge the
recycle bin at system log off.
Unique User Field
This parameter is used to select one of the user fields as a unique
key. Any of the 16 user-defined fields may be selected from the
drop-down. The designated field, if populated, must contain a
unique entry for each individual, across all tenants. The unique
field may be left blank in the user record.
When a user field is selected as the unique field, the system does not
verify that existing data is unique. However, if an individual record
is opened in the Individual Parameters editor (see Individual
Parameters on page 9-65), the designated unique field is evaluated
and must be made unique before any changes can be saved. The
operator may choose to cancel the changes and thus leave the field
in a non-unique condition.
Individual Activity Manager - Configure
Use this option to enable and configure the Individual Activity
Manager (IAM) system. Refer to the following section for more
information.

Individual Activity Manager Access Control
Individual Activity Manager

The Individual Activity Manager (IAM) system monitors specific
tenants for individual activity. If an individual of a monitored
tenant fails to use their key/card within a specified duration, the
individual automatically becomes disabled.
Configure the Individual Activity Manager system by specifying
which tenants this host workstation will monitor for individual
activity. You can also specify the duration of inactivity that will
cause a user to become disabled.
The tenant selections that you make in IAM editor are not global-
ized; therefore, you must visit this editor and select the appropriate
tenants on each host workstation that will monitor door controller
activity.
You can choose a duration setting of None, Daily, Weekly, Monthly,
or Yearly. If you choose None, no activity monitoring will be
performed from this host workstation.
You must also choose a Duration Interval setting. The available
range for this value varies depending on which duration setting you
chose. Regardless of which duration setting you chose, the
maximum limit is equivalent to 4 years.
Monitoring Door Controller Activity

An I/NET host workstation can only monitor activity at a door
controller if the appropriate tenant is selected in the IAM editor
and at least one of the following criteria are met:
The message masking you've defined for your system allows
the host workstation to receive transaction messages from the
door controller.
OR
The host workstation shares the same filemaster as another
host workstation that receives transaction messages from the
door controller and has the appropriate tenant selections. In
this case, the door controller activity is globalized daily at
12:30 AM.

Access Control Dial After Edit
An individual can become disabled because of inactivity at moni-

tored door controllers, even though the individual has had suffi-
cient activity at un-monitored door controllers. Ensure that your
system's message masking or file equalization allows for proper
monitoring of door controller activity. Refer to Chapter 3, System
Messages, for information about routing parameters and message
masking.
Per Individual Settings

By default, all individuals are monitored for activity when you
enable the Individual Activity Manager for the tenant. If you would
like to exclude specific individuals from activity monitoring, you
can use the Individual Parameters Editor to set the individual's
IAM parameter to Graced.
If the system disables a monitored individual because of inactivity,
the individual remains disabled until you use the Individual
Parameters Editor to deactivate () the individual's Disabled
IAM parameter. Refer to Individuals on page 9-64 for more
information.
Dial After Edit

As you build or change the access control system, data from the
host is automatically sent to directly connected interface units (i.e.,
DPIs, MCIs, and I/SITE LANs) as necessary. The interface units, in
turn, will automatically update their associated door controllers.
However, when this data needs to be sent to a remote site, the host
must send the information over a dial connection to the interface
unit.
The host workstation will attempt to make the dial connection
automatically. If the connection is successful, the access control
data will be sent to the remote interface unit and the affected door
controllers will be automatically updated. You can configure I/NET
to initiate dial connections immediately after your edits are
completed, or you can specify a time of day when the dial connec-
tions should begin (refer to DPU Dial Type and DPU Dial
Delay/Schedule above).

Two-man Rule Access Control
The system will attempt to dial four times (the initial attempt plus
three retries). If an automatic connection is not successful, I/NET
will generate an error message (Dial Retry Failed, for example).
In this case, you must manually dial the remote sites and perform a
station restore to each affected door controller.
Two-man Rule
Note: The two-man rule requires that the door controller is an SCU1284.
Depending on the requirements of your access control system, you
may wish to restrict certain individuals from entering into a secure
area without an escort. For example, you may allow visitors to enter
your companys product center, but only if they are accompanied
by a member of the marketing department.
Using a combination of door attributes and personnel schedule
settings, you can implement a two-man rule for select doors in
I/NET. The following door attributes are used for this purpose:
Note: Before you can enable either of the following door attributes in a
personnel schedule, you must first add these attributes to the door.
Escort Required Enable this door attribute in an indi-

viduals personnel schedule in order to restrict their ability to
enter a secure area without an escort.
Escort Enable this door attribute in an individuals
personnel schedule to authorize the individual to act as an
escort.
Configuring I/NET to Use the Two-man Rule.

Use the following steps to implement the two-man rule in I/NET.
Remember that the door controller must be an SCU1284.
1. Add the Escort and Escort Required door attributes to the
selected door.
2. Enable these attributes in one or more personnel schedules.

Access Control Two-man Rule
3. Assign the personnel schedules to individuals. The following

guidelines apply:
If an individuals personnel schedule enables only the
Escort Required attribute, the individual will require
an escort into the secure area. For as long as the Escort
Required attribute remains in effect, this individual
cannot enter the secure area without an escort.
If an individuals personnel schedule enables only the
Escort attribute, the individual can escort someone else
into the secure area. This individual can also enter the
secure area alone (i.e., not acting as an escort)
If an individuals personnel schedule enables both the
Escort Required and the Escort attribute, the indi-
viduals access will be controlled as follows:
If this individual initiates the access request, they will
require an escort.
If another individual initiates the access request, this
individual can be the escort.
Regardless of who initiates the access request, this indi-
vidual cannot enter the secure area alone for as long as
the Escort Required attribute remains in effect.
Refer to User-definable Door Attributes and PIN Pad Functions
on page 9-36 of this manual for more information about door
attributes.
Sequence of Events
The sequence of events that occur when using the two-man rule are
as follows:
1. An Escort Required key/card is presented at the door. This
key/card may also have the Escort attribute, however, as the
first key/card of the sequence it is not interpreted as an
Escort key/card.
2. I/NET validates the Escort Required key/card:
If the key/card is not valid for any reason, access is
denied.

Two-man Rule Access Control
If the key/card is valid, processing continues.

3. The key/card reader enters into a 10-second wait mode,
waiting for another key/card.
4. Another key/card is presented at the door:
If the key/card is not presented before the 10-second wait
mode expires, access is denied.
If the key/card is presented during the 10-second wait
mode, processing continues.
5. I/NET validates the Escort key/card:
If the key/card is not an Escort key/card, or it is not
valid for any reason, the 10-second wait mode restarts
and the reader continues to wait for another Escort
key/card. If no other key/card is presented before the 10-
second duration elapses, access is denied.
If the key/card is a valid Escort key/card, access is
granted.
Anytime access is denied, an Deny entry dsbl message is gener-
ated. If access is granted, two Reader entry messages are gener-
ated one for each of the two individuals.

CHAPTER
10
58
Direct Digital Control
I/NET offers you microprocessor-based direct digital control

(DDC). I/NET DDC emulates pneumatic control devices using an
on-line module editor. This control program measures a variable,
compares the measured variable against a desired value to deter-
mine the error, processes the error according to a specific software
algorithm, and produces an output that modifies the controlled
variable.
DDC is many things. It may be something as simple as measuring
an input temperature, comparing the temperature against the
defined setpoint, determining the difference between the input and
the setpoint temperatures, and determining if that difference is
positive or negative. The system then issues the appropriate
command to bring the input temperature in line with the setpoint.
DDC also operates at a more complex level. It can take into consid-
eration such factors as the magnitude of an error change since the
last time the point was sampled. It can also determine the speed at
which the error is increasing or decreasing and make corrections as
appropriate. This is an example of proportional, integral, derivative
(PID) control. PID is just one of the module types available with
I/NET.
There is an unfortunate tendency to interchange the terms DDC
and PID. The two are not synonymous. All electronic PID control
is DDC; however, not all DDC is PID control.
Input and Output Designations

DDC module inputs are referred to as setpoints or process vari-
ables. Outputs are referred to as control outputs. I/NET requires
that all DDC inputs be defined as points, lines, or constants.
Outputs can be defined as either lines or points.

Input and Output Designations Direct Digital Control
Points
Points can be used as inputs to DDC modules when the input is the
result of a calculation (internal point), the state/value sensed by an
external point, or the state/value of a point controlled by the oper-
ator. Points can also receive module output when you want an
action to occur as the result of a DDC module algorithm. Define
module inputs and outputs as points by entering either the point
name or the point address.
Lines
It is often desirable, or necessary, to chain several DDC modules
together in a cascade of control. This requires some way of making
the output of one module available to other modules. This is
accomplished with lines. These lines can transmit analog or
discrete data. Lines are equivalent to pneumatic tubing intercon-
necting pneumatic control devices and generally follow the same
rules:
Only one module should output to a specific line number.
When possible, assign the same number to a module and the
line to which it is delivering its output. This eliminates confu-
sion as to which line belongs with which module and vice
versa.
On the other hand, a specific line can act as an input to as
many modules as is necessary.
Note: The HiLo and Floating module types have two outputs. When you
assign a line number to the first output of one of these modules, we
recommend that you leave the next available line number blank to
avoid future confusion if and when you add the second output.
Constants
Constants are values or state conditions that never change. You can
enter a constant as a value (72 degrees) or a state (0 or 1). A
constant may be used as a DDC module input; however, a constant
may not be used as an output of a module. A constant output from
a DDC module would make the module unnecessary.

Direct Digital Control DDC Modules
DDC Modules
I/NET carries out direct digital control through a series of modules.
Module parameters are explained in this chapter. Each module has
its own algorithm. With a basic understanding of control theory
and application, these algorithms are easy to understand and apply.
Technically, there are seven types of DDC modules; however, no
one controller type provides all seven module types. The seven
DDC module types are:
Two-position HiLo
PID Relay
Floating Calculation
Reset
The DCUs and PCUs provide all but the Calculation module.
Micro Regulator (MR) controllers provide all but the HiLo
module. Application Specific Controllers (ASCs) provide all but
the HiLo Module. UCs provide variations of the PID and Floating
modules.
Each module type has its own data entry screen where you define
parameters such as inputs, algorithm modifiers, and output desti-
nations. These data entry screens are described in the Operator
Guide chapter dealing with direct digital control.
See Also: TCON299, I/NET Seven Operator Guide
Two-Position Module (Two-Pos)

This module requires approximately 49 bytes of memory. The Two-
position module is similar to an electric thermostat but responds
much more precisely and predictably. This module compares input
and setpoint values and provides an ON/OFF output signal to a
DO/DC point or line. This type of control is commonly used for
simple heating or cooling systems, starting and stopping motors,
controlling water sprays for humidification, etc. The parameters
for the Two-position module are listed in Table 10-1.

DDC Modules Direct Digital Control
Table 10-1. Two-position Module Parameters
Parameter Described on page:

Module number and name 10-26
Sample interval 10-26
Setpoint 10-27
Offset 10-27
Differential 10-28
Low limit 10-28
High limit 10-29
Process variable 10-30
Filter 10-30
Output 10-31
Failsafe command 10-40
Mode 10-41
Proportional, Integral, Derivative Module (PID)

This module requires approximately 149 bytes of RAM in a
DCU/PCU. In the MR, it uses 40 bytes of NOVRAM and 14 or 19
bytes of RAM (depending on whether filtering is used). The terms
proportional, integral and derivative describe the output response
of a module based on a varying set of conditions occurring by the
process variable. Each of the three elements of PID has a distinctive
purpose:
Proportional This element can best be described as coarse
control, which provides a rapid response to an error (i.e., the
difference between the setpoint and the process variable). All
proportional control has an inherent flaw called offset,
which simply means that it will always control at a point
above or below setpoint.
Integral The integral element of PID can best be described
as fine tuning proportional control. It produces a long-term
effect which is designed to reduce the offset (inherent in
proportional control) to zero.

Derivative This element has the function of measuring the

rate at which the deviation from setpoint (error) is increasing
or decreasing and taking quick corrective action to eliminate
the error.
The PID module is commonly used for the control of modulating
valves, vanes or modulating motors where an analog output point
is used. This module compares the current input and setpoint to
determine the current error. Proportional, Integral, and Derivative
corrections to an analog output point can then be made depending
on the magnitude and direction of this error.
PID Algorithm
This manual is not intended to provide a detailed explanation of
the theory of PID algorithms. The PID algorithm implemented in
I/NET is derived from that in the ASHRAE (American Society of
Heating, Refrigerating and Air-Conditioning Engineers, Inc.)
handbook titled HVAC Applications. You may wish to refer to
this publication for additional information. The control action of
the PID module can be described by the following equation:
100 O hl O ll Ts Td
V n = V n 1 + --------- --------------------- ( E n E n 1 ) + ----- E n + ------ ( E n 2E n 1 + E n 2 )
PB I hl I ll Ti Ts

PP II D
D
The elements used in the PID control action algorithm are listed
and described in Table 10-2. The PID module output response is
governed by the actuator mode selected. In direct mode, a positive
error produces a positive output correction. In the reverse mode, a
positive error produces a negative output correction. Refer to
Output Mode on page 10-41 for more information.
Table 10-2. PID Algorithm Elements
Element Description
th
Vn Output at the n sample (i.e., current output).
th
Output at the n 1 sample (i.e., previous output).
Vn1 Note: This element, Vn1 , is set to the control point (failsafe) value, Co , when the
module is initialized.

Table 10-2. PID Algorithm Elements (Continued)
Element Description
Proportional band. The percentage error in the process variable that produces full range
PB
output travel.
Ohl Output high limit (in output units).
Oll Output low limit (in output units).
Ihl Input high limit (in output units).
Ill Input low limit (in input units).
th
Error at the present (n ) sample (i.e., the difference between the input, PV, and the
En
setpoint, SP (in input units)).
th
En1 Error at the previous (n 1) sample (in input units).
th
En2 Error at the second most previous (n 2) sample (in input units).
Ti Integral reset interval (in seconds).
Td Derivative rate interval (in seconds).
Ts Sample interval (in seconds).
The parameters for the PID module are listed in Table 10-3.
Table 10-3. PID Module Parameters

Setpoint 10-27
Offset 10-27
Low limit 10-28
High limit 10-29
Filter 10-30
Output 10-31
Ramp limit 10-34
Low limit 10-28
High limit 10-35
Control point (failsafe) 10-36
Proportional band 10-37

Table 10-3. PID Module Parameters (Continued)

Reset interval 10-39
Rate interval 10-39
Mode 10-41
The proportional (P) element of PID is used in all PID module

calculations. However, use of the integral (I) and derivative (D)
elements is controlled by the reset interval and rate interval param-
eters, respectively. The integral element is not used if the reset
interval is zero. The derivative element is not used when the rate
interval is zero. When both the reset interval and rate interval are
zero, the PID module operates in P-only mode and a different algo-
rithm is used. The P-only mode of operation and algorithm are
described below.
P-only Mode of Operation
The PID module functions in P-only mode (no integral or deriva-
tive corrective actions) if the reset interval and rate interval entries
in the PID editor are left at zero.
Note: P-Only mode is not available in the EPROM versions of the 7700 and
7740 DCUs.
The equation that is specific to the P-only mode of operation is as

follows:
Output = Control Point + ( Gain Error )
or
100 O hl O ll
Output = Control Point + --------- --------------------- ( Input Setpoint )
PB I hl I ll
In this P-only mode, the input range (input high limit minus low
limit) must be centered around the setpoint, the module output
must always be 0100, and the control point must be 50. The input
low and high limits are not used as the limits of the process variable
for failsafe purposes. However, if the value of the input rises or falls

outside the input high or low limits, the module output is clamped
to its output high or low limit value depending on the actuator
mode setting (refer to Output Mode on page 10-41). When the
input returns to within the input limits, the module does not go to
its control point value; the module simply outputs a proportional
value according to the equation above.
PID Tuning Parameters
The tuning parameters listed in Table 10-4 are available in the
PCU/DCU PID modules (they are not available in the MR, UC, or
ASC PID modules).
Table 10-4. PID Tuning Parameters
Adaptive control 10-42

Maximum bump 10-43
Settling time 10-43
Maximum overshoot 10-44
Target damping 10-44
Noise band 10-45
PID Equation Examples

Lets work through examples of PID control by substituting values
in the equation. Well start with the proportional element.
Proportional Corrections
In this example well say that the setpoint is 55F, and the actual
mixed air temperature is 57F. Well say that the value output at the
last sample interval (Vn1) was 50%, the proportional band (PB) is

20, the input limits are 0100, the output limits are 0100, the
current error (En) is 2, and the error at the last sample interval
(En1) was 0. The calculation is as follows:
Module Previous Proportional

= +
Output Output Correction
100
Vn 50% --------- ( 2 0 )
20
5 2%
10%
60% = 50% + 10%
The example values used in the equation above caused the module
output to increase from 50% to 60%. In the next sample interval,
the 60% output from the calculation above becomes the value for
Vn 1 and the previous value of En becomes the value of En 1 . If the
input variable has not yet responded to our control output (actual
mixed air temperature is still 57F), then the current error (En) is
still 2 and the calculation would be:

= +
100
Vn 60% --------- ( 2 2 )
20
5 0%
0%
60% = 60% + 0%

If we now assume that the process variable begins to respond to our

control output and mixed air temperature begins to fall, we would
observe the following action if the process variable decreases to
56.5F (setpoint remains at 55F):

= +
100
Vn 60% --------- ( 1.5 2 )
20
5 0.5 %
2.5 %
57.5% = 60% + 2.5%
We have decreased the output by 2.5% in response to the error (En)

decreasing. Assume that the mixed air temperature continues to fall
to 56F. The module will continue to decrease its output until ulti-
mately the error term (En (En 1)) is equal to zero. At that point,
the error term will cease to change from sample to sample and the
output value (Vn) will also cease to change. However, we are still
not at the desired setpoint of 55F. This is offset. Assuming that
we have properly selected the proportional band setting and the
sample rate is appropriate, the equation will act as follows:

= +
100
Vn 55% --------- ( 1 1 )
20
5 0%
0%
55% = 55% + 0%
At this point, the equation is in equilibrium and no further change

will be made to the output. From this example, it is apparent how
offset occurs. We will address this problem and its solution in our
discussion of integral control.
It is important to note how the selection of proportional band and
sample rate affect the operation of the proportional portion of the
module. Using the first example above, let us assume that we have
a sample rate of 60 seconds and the time constant of the process is

consistent with that sample rate (i.e., the mixed air temperature is
not changing any faster than every 60 seconds). If we change the
proportional band to 5%, we observe the following change in
performance:

= +
100
Vn 50% --------- ( 2 0 )
5
20 2 %
40%
90% = 50% + 40%
We can see that this change instructs the output portion of the
module to move to a position equivalent to 90% of its output
range. This action will, in all likelihood, result in severe overshoot
and induce oscillation.
Assuming that the process controller can produce a rapid change in
the controlled process and the process variable drops from 57F to
53F, we can see that the next sample, taken 60 seconds later, will
result in the following action:

= +
100
Vn 90% --------- ( 2 2 )
5
20 4 %
80 %
10% = 90% + 80%
When the process temperature reaches 53F, or less, we have a situ-

ation where both error terms are algebraically negative (2 2).
The large negative result creates an enormous change in the nega-
tive direction. We have now succeeded in inducing wild oscillation,
which equates to on-off control, and without the help of derivative
control, we have no hope of ever dampening the control action. It
is very likely that even the introduction of the derivative control
action will not correct a problem of this magnitude.

Remember that when selecting Proportional Band that you are

selecting the percentage of the span of control that will cause the
output of the PID module to change its output from 0% to 100%.
When selecting a proportional band value, start high. For example
lets assume that you have entered the input low limit as 50F and
the input high limit as 80F. You have defined a span of control of
30. If you select a Proportional Band of 100%, the process variable
will have to change 30 to cause the output to change from 0% to
100%. If you select a Proportional Band of 50%, the process vari-
able will have to change 15 to cause the output to change from 0%
to 100%. Conversely, a Proportional Band of 200% will produce a
change of only 50% of the output over a full input range change
(30). You can readily see that it is as important to select a reason-
able span of control (input high limit input low limit) as it is to
select the proper Proportional Band.
Integral Corrections
Previously, we discovered that proportional control alone had an
inherent defect in that it always produces offset (i.e., it will always
settle at a point above or below the setpoint). In order to make our
process control as accurate, and therefore as efficient, as possible,
we need some fine tuning help. This is where integral control is
useful. Integral control (or reset control) takes over where
proportional control leaves off. The portion of the PID equation
used in integral control is as follows:
T
I = -----s E n
Ti
The following assumptions will be made for this example:

Ts = 30 seconds (Sample Interval)
Ti = 600 seconds (Reset Interval)
En = 56F 55F (Current Error)
100
--------- = 5% (assume 20% Proportional Band, Input Low
PB
Limit = 0, Input High Limit = 100; from previous
example)

In this example, we will assume that our process (mixed air) has
settled at 56F and that proportional control is no longer making
corrections. We will use a sample interval of 30 seconds and a reset
interval of 600 seconds. The calculation is as follows:
Module Previous Proportional Integral

= + +
Output Output Correction Correction
100 100 30-
Vn 55% --------- ( 1 1 ) --------- -------- ( 56 55 )
20 20 600
5 0% 5 0.05 1
0% 0.25%
55.25% = 55% + 0% + 0.25%
The resultant reset contribution at this interval is 0.25%. The

proportional contribution is 0%. These values are added to the
previous output causing the total output of the module to now
equal 55.25%. We will now assume that the next time the module
calculates the process (mixed air), the temperature is 55.4F:

= + +
100 100 30-
Vn 55.25% --------- ( 0.4 1 ) --------- -------- ( 55.4 55 )
20 20 600
5 0.6 % 5 0.05 0.4
3 % 0.1%
52.35% = 55.25% + 3% + 0.1%

The reset contribution at this interval is only 0.1%. The propor-

tional contribution is 3%. These values are added to the previous
output (55.25%) for a total P & I output of 52.35%. One step
further and, assuming that we have produced a process tempera-
ture of 54.9F, we can observe the reversal of the process:

= + +
100 100 30-
Vn 52.35% --------- ( 0.1 0.4 ) --------- -------- ( 54.9 55 )
20 20 600
5 0.5 % 5 0.05 0.1
2.5 % 0.025 %
49.825% = 52.35% + 2.5% + 0.025%
Once the process variable is less than the setpoint, the integral
contribution is negative and we correct the overshoot. Overshoot
caused by the integral element is generally small in magnitude and,
by its very nature, is self-correcting. The reset contribution at this
interval is now 0.025% and the proportional contribution is
2.5%. We add these values to the previous output (52.35%) for a
total P & I output of 49.825%.
Increasing the integral or reset interval to 1200 reduces the effect of
the integral increase or decrease by one half. Using the first
example, but substituting 1200 as the reset interval, we observe that
the contribution is 0.125% as opposed to the 0.25% previously.
100 30
I = --------- ------------ ( 56 55 )
20 1200
I = 5 0.025 1
I = 0.125%
Conversely, an increase in the sample rate interval produces an
increase in the contribution. Using the same first example, but
changing the sample rate to 60 seconds, we mathematically observe
that the contribution is now 0.5%.

100 60
I = --------- --------- ( 56 55 )
20 600
I = 5 0.1 1
I = 0.5%
While this is not a complex relationship, it is one that is very impor-

tant and must be understood by the controls engineer and by the
operating engineer. It is also noteworthy that decreasing the reset
interval, while the sample interval remains constant, will increase
the magnitude of the integral contribution. When selecting a reset
interval, it is best to start high.
With a reasonably accurate selection of parameters, the integral
portion of PID quickly reduces the offset to zero, thereby achieving
the desired result; our process (HVAC system, chiller, etc.) running
exactly at setpoint.
Controls engineers are generally bound to strive for the most
comfortable control for the least expenditure of energy. The ability
to control overshoot, undershoot, and offset, permits the controls
engineer to more closely coordinate the complete control scheme.
Occasionally, it is desirable to allow some offset since small correc-
tions could actually cause the expenditure of energy unnecessarily.
Derivative Corrections
Now that we have a process running in equilibrium, we must come
back to real world conditions and recognize that external forces are
constantly working to upset our process. We may observe a quick
change in the load imposed on our HVAC system by a rapid
increase in body heat and lighting load, for instance, at 8 a.m.,
when everyone reports to work. In order to prevent substantial
overshoot in our control action, we need to be able to observe,
measure, and correct for the speed (rate) at which our process is
moving toward or away from setpoint. This requirement brings us
to the final element of the PID module; Derivative. The equation
for the Derivative element is as follows:
T
D = -----d- ( En 2E n 1 + E n 2 )
Ts

The term En 2En 1 + En 2 determines two things:

The rate of change between samples
The direction of the change (i.e., whether the process variable
is approaching or moving away from setpoint)
Since derivative action has no effect when the process has reached
a steady state, look at the impact (or lack thereof) in this condition.
We will again use mixed air control as an example. The setpoint
remains at 55F.
The following assumptions will be made for this example:
Td = 300 seconds (Rate Interval)
Ts = 30 seconds (Sample Interval)
En = 0 (Current Error)
En 1 = 0 (Error one sample prior to the current sample)
En 2 = 0 (Error two samples prior to the current sample)
100
--------- = 5% (assume 20% Proportional Band, Input Low
PB
Limit = 0, Input High Limit = 100; from previous
example)
The derivative calculation is as follows:
Module Previous Proportional Derivative

= + +
100 100
Vn 55% --------- ( 0 0 ) --------- 300
--------- ( 0 ( 2 0 ) + 0 )
20 20 30
5 0% 5 10 0
0% 0%
55% = 55% + 0% + 0%
Since the result is zero, the derivative element has no effect. If there
is no change in error, there can be no rate of change derived.

Now we assume that the return air temperature starts to rise (due
to people occupying space, lighting load, etc.) and the impact is
sufficient to raise the mixed air temperature to 56F. Keep in mind
that for the previous two rate intervals there has been no error.

= + +
100 100
Vn 55% --------- ( 1 0 ) --------- 300
--------- ( 1 ( 2 0 ) + 0 )
20 20 30
5 1% 5 10 1
5% 50%
110% = 55% + 5% + 50%
In this example, we see the multiplication effect that rate has on

even a relatively small error. Rate tries to add 50% to the previous
proportional output of 55% but it cannot put out more than 100%
output.
Unlike the proportional (P) band and reset (I) interval, when
selecting the rate (D) interval, it is best to start low. We need to have
a relatively small rate interval to take action quickly and in smaller
increments. If we substitute a rate interval of 60, we observe that the
correction is 10%:

= + +
100 100
Vn 55% --------- ( 1 0 ) --------- 60
------ ( 1 ( 2 0 ) + 0 )
20 20 30
5 1% 521
5% 10%
70% = 55% + 5% + 10%
This output is in addition to the 5% change added by the propor-

tional action of the module, giving a total P & D output of 70%.
The derivative element senses a rapid change away from setpoint
and corrects for the rate of change. The effect works just the oppo-
site if the process variable moves toward the setpoint at a rapid rate
such as might be observed during morning recess in a school room.

In this example, we will assume the process to be room control. We

are sensing room temperature, and we are controlling a reheat coil
valve. The setpoint for this example is 70F. During the three inter-
vals that we are concerned with, the errors are: En = 0, En 1 = 1,
and En 2 = 4.
100 60
D = --------- ------ ( 0 ( 2 1 ) 4 )
20 30
D = 5 2 2
D = 20 % (D contribution at Output Vn)
The resulting decrease in output is 20% which starts to open the

heating valve rapidly to adjust for the load. Assuming that the valve
is correctly sized, the proportional band is correct, and the coil heat
exchange capability is adequate, we will see the system adjust to the
rapid increase in offset. In the examples below, the three error
terms for the equation are provided (see Table 10-5).
Table 10-5. Derivative Control Examples
Terms Example 1 Example 2 Example 3 Example 4
En 1 0.5 0.5 0.5

En 1 2 1 0.5 0.5
En 2 1 2 1 0.5
Results: +2 0.5 0.5 0
The answer derived from the table examples is multiplied by Td/Ts

and the result is added to the proportional and integral elements.
This value is then multiplied by the term 100/PB% before
becoming corrective output.
After the process has reached stability, as indicated in example 4,
derivative control has no further effect and the algorithm depends
on the integral portion to gently nudge the input back to setpoint.
To achieve fine control, we must make the rate calculation often
enough to catch significant deviation trends and correct them with
the least amount of control action. You may consider making the
rate interval the same as the sample interval; however, examination
of the equation shows that this produces a multiplying effect of 1

(Td/Ts = 1) and doesnt produce the quick control action desired. A

large rate value also subjects the module to upsets caused by tran-
sient perturbations.
Floating Module (FLOAT)

This module requires approximately 149 bytes of RAM in a
DCU/PCU. In an MR, it uses 40 bytes of NOVRAM and 12 or 17
bytes of RAM (depending on whether filtering is being used). The
Floating module operates much like the PID module, described
above. The operation of the algorithm is the same and the entries
which modify the proportional band, reset interval, and rate
interval are identical. The difference between the two modules lies
in the outputs to the final control element.
The PID module has inherent positional feedback (i.e., the module
always knows where the output is) because the module equation
uses the term Vn1 (previous position). The output of the PID
module is always a percentage of the full scale output. The output
of the Floating module is directed to two separate DO points as an
increase command and a decrease command. The module does not
know the exact position of the controlled valve or damper and
assumes that the controlled device was driven to the correct posi-
tion. You need this module and its outputs when the final control
element (valve, damper, etc.) is controlled by a bidirectional motor.
Floating Algorithm
TACs Floating algorithm is derived from that in the ASHRAE
handbook titled HVAC Applications. The control action of the
Floating module can be described by the following equation:
TR PB Ts Td
V n = --------------------- ( E n E n 1 ) + ----- E n + ------ ( E n 2E n 1 + E n 2 )
I hl I ll Ti Ts

PP II D
D
The elements used in the Floating control action algorithm are
listed and described in Table 10-6. The Floating module output
response is governed by the actuator mode selected. In direct
mode, a positive error (and subsequent Vn value) produces a posi-

Table 10-6. Floating Algorithm Elements
Element Description
th
Output at the n sample (i.e., current output). A positive value
Vn here results in an increase pulse. A negative value results in a
decrease pulse (on a direct acting Floating module).
TR Throttling range. Actuator stroke time in seconds.
Proportional band. The percentage error in the process variable
PB
that produces full range output travel.
Ihl Input high limit (in input units).
Ill Input low limit (in input units).
th
Error at the present (n ) sample (i.e., the difference between the
En
input, PV, and the setpoint, SP (in input units)).
En1 Error at the previous (nth 1) sample (in input units).
th
Error at the second most previous (n 2) sample (in input
En2
units).
Ti Integral reset interval (in seconds).
Td Derivative rate interval (in seconds).
Ts Sample interval (in seconds).
tive output correction. In the reverse mode, a positive error (and

subsequent Vn value) produces a negative output correction. Refer
to Output Mode on page 10-41 for more information.
The parameters for the Floating module are listed in Table 10-7.
Table 10-7. Floating Module Parameters

Setpoint 10-27
Offset 10-27
Low limit 10-28
High limit 10-29
Filter 10-30
Increase output 10-32

Table 10-7. Floating Module Parameters (Continued)

Decrease output 10-33
Throttling range 10-36
Turn-around time 10-37
Proportional band 10-37
Reset interval 10-39
Rate interval 10-39
Mode 10-41
Floating Module Tuning Parameters

The tuning parameters listed in Table 10-8 are available in the
PCU/DCU Floating modules (they are not available in the MR,
UC, or ASC Floating modules).
Table 10-8. Floating Tuning Parameters
Adaptive control 10-42

Maximum bump 10-43
Settling time 10-43
Maximum overshoot 10-44
Target damping 10-44
Noise band 10-45
Reset Module (RESET)

This module requires approximately 84 bytes of RAM in the
DCU/PCU. In the MR, this module uses 48 bytes of NOVRAM and
2 bytes of RAM. The reset module produces a primary reset
schedule and modifies the results of that schedule based upon a
secondary input. The output of this module typically provides a
setpoint to another module and generally does not directly control
an output point. The Reset module is typically used to reset the
setpoint of a controlling module (Two-position, PID, Floating)

based on one or two measured inputs. This increases the rate of

space temperature modification but does not improve control
capability.
This reset function is probably familiar to control engineers as the
technique used to reset the setpoint of a boiler according to outside
air temperature. As the outside temperature drops, the tempera-
ture of the water must increase to maintain the desired temperature
in the spaces served by the boiler (the heating load increases). The
two temperatures are inversely proportional to each other.
Reset control is also used to reset the discharge temperature of an
HVAC unit based on the space temperature.
The parameters for the Reset module are listed in Table 10-9.
Table 10-9. Reset Module Parameters

Primary input 10-45
Inputs 1 and 2 10-45
Outputs 1 and 2 10-46
Secondary input 10-46
Inputs 1 and 2 10-47
Outputs 1 and 2 10-47
Output 10-31
Low limit 10-35
High limit 10-35
HiLo Module (HILO)

The HiLo module requires approximately 41 bytes of RAM in the
DCU/PCU. This module does not exist in the UC or MR. A Calc
module can be used in the MR to achieve the same results (see
Calculation Module (CALC) on page 10-24). The HiLo module
provides a convenient means to extract the highest and/or lowest
value from among several values. You can also accomplish this with

the High and Low operator calculations in the DCU/PCU. This

module is not available in MRs or ASCs; instead the Calculation
module can be used.
The HiLo module is commonly used to derive the highest space
temperature needed to reset an air handling unit (AHU) cold deck
discharge setpoint, and to select the lowest space temperature
needed to reset an AHU hot deck discharge setpoint.
The module is capable of providing both the high signal output and
the low signal output simultaneously, if desired, making it unnec-
essary to use an additional module.
The parameters for the HiLo module are listed in Table 10-10.
Table 10-10. HiLo Module Parameters

High output 10-34
Low output 10-34
Inputs 14 10-48
Relay Module (RELAY)

This module requires approximately 39 bytes of RAM in the
DCU/PCU. In the MR, this module uses 20 bytes of NOVRAM and
2 or 4 bytes of RAM (2 bytes for standard relay, 4 bytes for DBB,
DBM, or INT relay). The Relay module performs multiple func-
tions as part of overall I/NET DDC capabilities. As you become
more familiar with I/NET you will discover many uses for the Relay
module.
In its simplest form, this module is similar to a single-pole double-
throw relay. It has an input which acts as a coil (discrete input), a
normally closed port (DI = 0 input), a normally open port (DI = 1
input), and a common output. When used as a traditional relay, the
module passes the state/value from the DI = 0 port to the common
output when the discrete input (coil) value is 0. When the discrete
input (coil) is 1, the module passes the state/value of the DI = 1
port to the output.

This module can also function as an interval time delay relay

(INT), as a delay-before-break relay (DBB), or as a delay-before-
make relay (DBM). Refer to Settings (Relay Types) on page 10-48
for detailed information regarding these relay types.
The parameters for the Relay module are listed in Table 10-11.
Table 10-11. Relay Module Parameters

DI = 0 10-48
DI = 1 10-48
Settings 10-48
Time delay 10-49
DI select 10-50
Output 10-31
Calculation Module (CALC)

The Calculation module exists only in MR controllers and ASCs.
This module is edited and operates similarly to the existing DCU
calculated point editor in I/NET. The exceptions for this module
are:
It has different memory requirements as described in
Table 10-12.
It occupies a DDC module number rather than a point exten-
sion.
Its output or result may be directed to a line or an output
point. If directed to a line, the line number must equal the
module number.
In addition to points and constants, equation parameters may
also include lines.

Most of the operators available in the Calculations point

extension editor are also available in the MR-DDC Calcula-
tions module; however, the following operators are not avail-
able:
Relative Humidity Day of Week

Dewpoint Hour
Enthalpy (RH) Minutes
Enthalpy (DP) MPM
Year Julian Date
Month Time to Start
Day
The memory requirements for the Calculation module are
explained in Table 10-12.
Table 10-12. MR-Calculation Module Memory Requirements
Item NOVRAM (Bytes) RAM (Bytes)

Module overhead (fixed) 6 2
Each operator (+, , *, /, >, <, etc.) 1 N/A
Each point address (P0, P1, etc.) 2 N/A
Each constant (C0, C1, etc.) 4 N/A
Each line (L0, L1, etc.) 1 N/A
Calculate total based on items listed above and
Total for module 2
round up to the nearest 4 bytes.
Note: Do not count parenthesis when determining memory usage
Count <= (less than or equal to) as one operator. Count >= (greater than or equal to) as one
operator.
Count each occurrence of a Parameter, Operator, Constant, or Line when determining memory
usage. For example: P0*P0*P0 would be 2+1+2+1+2=8.
Count each Line only once when it is used as the output from a DDC module. Do not count the
same Line a second time when it is subsequently used as an input to other modules.
The CALC module plays a central role for the other DDC modules
in the MR controller and ASC. The active setpoint (occupancy
detection, Heat/Cool selection, schedule, etc.) for the other DDC

DDC Module Parameters Direct Digital Control
modules can be established using a CALC module. Refer to Calcu-

lations (C) in Chapter 7, Point Extensions for details on calcula-
tions.
Note: Indirect AO points cannot be used as the input to a Calculation

module.
DDC Module Parameters

The following paragraphs list and describe DDC parameters. The
applicable modules for each parameter are also listed.
Module Number and Name

Modules
Two-position, PID, Floating, Reset, HiLo, Relay, and Calculation
Description
Each module is assigned a number (116). The user may enter a
name used to describe the module. This name can be up to eight
alphanumeric characters.
Sample Interval
Modules
Two-position, PID, Floating, Reset, HiLo, Relay, and Calculation
Description
A number between 1 and 255 that represents the number of
seconds between module outputs. This option lets you adjust the
speed of the module to match either the expected response time of
the process variable input (Two-position, PID, Floating, Reset, or
HiLo modules) or the desired response time of the output (Relay
and Calculation modules). For example, a module controlling
static pressure might require a sample interval as short as one
second since the process (static pressure) responds very quickly to
the control output. Room temperature control normally requires a
much slower sample interval, in the range of 60 seconds, since the
temperature in a room does not change rapidly.

Direct Digital Control DDC Module Parameters
Modules in MRs may process at less than the requested sample

interval. This can happen if you have several modules set to short
intervals. As the interval decreases, the microprocessor in the MR
may not be able to keep up with all modules and all points. For
example, if ten modules are all set to a sample interval of one
second, the effective interval might be five seconds. The actual
results are affected by the type and complexity of the modules
involved, the sample interval of each module, and the quantity of
points that must be processed by the MR.
The majority of all HVAC processes do not require, nor should you
use, sample intervals of less than 10 seconds. Exceptions would be
flow control loops, such as static pressure control of VSDs, or
dump dampers with true floating control.
Setpoint
Modules
Two-position, PID, and Floating
Description
The desired value of the input point being controlled. Typically this
is the desired room temperature or something similar. It may be
represented by a line, point, or constant. Refer to Input and
Output Designations on page 10-1 for more information about
each of these setpoint options.
Setpoint Offset
Modules
Description
You may want to use setpoint offset if you have defined your
setpoint as a line or point. If your setpoint is a constant then offset
is typically not used. The setpoint offset value can be between 100
and 100. The default is zero. Setpoint offsets are useful when you
want cascaded control. That is, you have several modules which
share a common setpoint (line or point) which need to be stag-
gered in their operating range. In this case, use the same setpoint

(line or point) for each module and assign each module a unique
setpoint offset value. The setpoint offset is displayed in the same
engineering units as the line or point setpoint it offsets.
Setpoint Differential
Modules
Two-position
Description
The degree of precision for this module. Differential is the temper-
ature range over which no action takes place. The temperature is
allowed to rise or fall unchecked until it reaches the opposite limit
of the differential. In a situation where temperature is critical, you
may want a very small or even non-existent differential. Define a
larger differential for situations where exact temperature control is
less important.
A larger differential means that equipment is turned on and off less
often. This saves energy and money spent on equipment operation.
You must weigh this against the temperature needs of the environ-
ment affected by this module.
To determine the actual temperature control range, divide the
differential in half. The controlled range is equal to the setpoint
plus or minus one-half of the differential. For example, if your
setpoint is 76 and you select a differential of four, the measured
temperature must rise above 78 degrees before the module controls
an HVAC unit on (space is too warm). The temperature must fall
below 74 before the point controls an HVAC unit off (space is too
cool). This creates a control range of 74 to 78 degrees.
Setpoint Low Limit

Modules
Description
This parameter defines the lower limit of the setpoint (not the
process variable input). The module declares the setpoint no longer
valid if the setpoint value drops below the input low limit. Set the

value at the low end of the normal acceptable range of the module
setpoint. The default value is zero. If the setpoint will vary below
zero, such as for a refrigeration case, this value must be set to a
lower value than default. If the setpoint drops below the input low
limit, the module immediately declares a bad input and,
depending on the applicable module, one of the following actions
occur:
The Two-position module outputs the failsafe command state
(0 or 1).
The PID module outputs the control point value, unless oper-
ating in P-only mode. In P-only mode, the PID module
clamps the output to either the output high limit or the
output low limit, depending on the actuator mode setting
(refer to P-only Mode of Operation on page 10-7 and
Output Mode on page 10-41).
The Floating module stops any pulse outputs.
Setpoint High Limit

Modules
Description
This parameter defines the upper limit of the setpoint (not the
process variable input). The module declares the setpoint no longer
valid if the setpoint value rises above the input high limit. Set the
value at the high end of the normal acceptable range of the module
setpoint. The default value is 100. If the setpoint is to vary above
100, this value must be set to a higher value than default. If the
setpoint value exceeds the input high limit, the module immedi-
ately declares a bad input and, depending on the applicable
module, one of the following actions occur:
The Two-position module outputs the failsafe command state
(0 or 1).
The PID module outputs the control point value, unless oper-
ating in P-only mode. In P-only mode, the PID module
clamps the output to either the output high limit or the

output low limit, depending on the actuator mode setting

(refer to P-only Mode of Operation on page 10-7 and
Output Mode on page 10-41).
The Floating module stops any pulse outputs.
Process Variable
Modules
Description
The input for the module (i.e., the point, line, or constant which
represents the value of the process being controlled (air tempera-
ture, water pressure, etc.)). The input for all DDC modules may be
a line, point, or constant. Refer to Input and Output Designa-
tions on page 10-1 for more information about each of these input
options.
Process Variable Filter

Modules
Description
This option lets you average up to five previous input values with
the current input value to reduce the impact of rapidly changing
inputs. Adjustable input filtering is available with 7700 and 7740
controllers (EPROM versions only) and UCs. For these controllers,
the input filter parameter can be a value from zero to five. The
default is zero (no filtering). This parameter represents the number
of previous input values to be averaged with the current input
value.
All other DCUs/PCUs and MRs use a Yes or No setting, rather than
a value, for the input filter parameter. These devices automatically
average the last five inputs with the current input if their input filter
parameter is set to Yes. The number of samples averaged is not
adjustable for these devices.

Output
Modules
Two-position, PID, Reset, Relay, and Calculation
Description
You can direct the output of the module to a line or point. Select a
line if the output is used by another DDC module. Select a point if
the output is used to initiate an event sequence, to provide interme-
diate control, or to directly control an action. If you select a line,
enter a number (164 for non-MRs, 116 for MRs) that corre-
sponds to the number of this module. If you select a point, the type
of point you may use depends on the module being used:
In the Two-position module, you may use an external or
internal DO or DC point (or an internal DI or DA point in
non-MR controllers). Use an external point when you want
the Two-position module output to directly control an action
such as turning on a fan, or turning off a pump. Select an
internal point to initiate an event sequence.
Note: In order to conserve memory in the Micro Regulator products, you

can output MR-resident Two-Position DDC modules to discrete
output points (internal or external) and MR-resident DDC lines. You
cannot output to input points (DI/DA) in an MR-resident Two-posi-
tion module.
In the PID and Reset modules, you may use an external or

internal AO point. The AO point may be at a normal DO
hardware address for pulse width modulation (PWM)
control. A true AO point may be used for true current or
voltage output to a valve/damper actuator.
You may also direct the output to an internal AO point if the
output is used for some intermediate purpose. You will
primarily direct PID outputs to AO points. Use an external
point when you want the PID or Reset module output to
directly control an action such as modulating a valve or
damper. Select an internal point to initiate an event sequence
or provide some intermediate control.

In the Relay module, you may use an external or internal AO,

DO, or DC point (or internal DI or DA point in non-MR
controllers). The output from the Relay module may be
analog or discrete, depending on the DI = 0 and DI = 1
inputs. An analog output may be assigned to an AO point at a
normal DO hardware address for PWM control. A true AO
point may be used for current or voltage output to a valve or
damper.
Use an internal point if the Relay output is used to initiate an
event sequence or to provide some intermediate control. Use
an external point when you want the Relay module output to
directly control an action such as modulating a valve (analog
output) or turning on a fan (discrete output).
Increase Output
Modules
Floating
Description
In a DCU or PCU, you may use a line or a DO point for this param-
eter. In an MR or ASC, only a DO point (not a line) can be used as
the output. In the UC, the user simply enters the hardware bit (0
7) to be controlled by the UC Floating extension.
The Floating module issues timed pulse outputs to rotate a bidirec-
tional motor. This parameter directs a timed pulse to increase the
output. This results in a specific action, such as the opening of a
valve.
When issuing a pulse to a DO point, the actual output from the DO
point (energize or deenergize) is determined by the definition of
the points control command pair (refer to Control Description
in Chapter 6, Input and Output Points for information concerning
control descriptions and commands). It is critical to define the first
control command of the pair as the energize or one command.
Note: If you select Point for Increase output in an MR, make sure you
also select the correct output point from the point drop-down box. If
you leave the default value of None in the drop-down box, the first
output point on the MR is automatically pulsed. This can cause a

conflict if there is any other control action on that point (time

schedule, temperature control, DDC module, etc.), potentially
causing the point to be energized and de-energized constantly.
When issuing a pulse to a line, the Floating module issues a zero.

When the pulse duration expires, the line returns to a one state.
Note: The MR Floating module outputs can be placed in Manual mode to

override the output of the module. Refer to Chapter 5, Controller
Functions, for a description of the Manual mode.
Decrease Output
Modules
Floating
Description
In a DCU or PCU, you may use a line or a DO point for this param-
eter. In an MR or ASC, only a DO point (not a line) can be used as
the output. In the UC, the user simply enters the hardware bit (0
7) to be controlled by the UC Floating extension.
This parameter reverses the activity instigated by the output
increase, described above. For example, if the increase pulse opens
a valve, the decrease pulse closes a valve.
When issuing a pulse to a DO point, the actual output from the DO
point (energize or deenergize) is determined by the definition of
the points control command pair (refer to Control Description
in Chapter 6, Input and Output Points for information concerning
control descriptions and commands). It is critical to define the first
control command of the pair as the energize or one command.
Note: If you select Point for Decrease output in an MR, make sure you
also select the correct output point from the point drop-down box. If
you leave the default value of None in the drop-down box, the first
output point on the MR is automatically pulsed. This can cause a
conflict if there is any other control action on that point (time
schedule, temperature control, DDC module, etc.), potentially
causing the point to be energized and de-energized constantly.

When issuing a pulse to a line, the Floating module issues a zero.

When the pulse duration expires, the line returns to a one state.
Note: The MR Floating module outputs can be placed in Manual mode to

override the output of the module. Refer to Chapter 5, Controller
Functions, for a description of the Manual mode.
High Output
Modules
HiLo
Description
This parameter directs the maximum output value to either a line
or a point. The HiLo module is capable of providing the high signal
output and low signal output simultaneously.
Low Output
Modules
HiLo
Description
This parameter directs the minimum output value to either a line
or a point. The HiLo module is capable of providing the high signal
output and low signal output simultaneously.
Output Ramp Limit

Modules
PID
Description
The output ramp limit is a value (percent) between 0 and 100 used
to define the magnitude of the largest change in output you want
the system to issue between samples. Defining this parameter as less
than 100 percent helps protect equipment from wide swings in

output, smoothing output in an oscillating process situation. The

actual maximum output is this ramp limit percent multiplied by
the output range (Output High Limit Output Low Limit).
Note: If you enter a 0 in this parameter, the output will never change
(i.e., 0% of any output range is 0).
Output Low Limit

Modules
PID and Reset
Description
The output low limit defines the minimum output value. The
default is zero because the output of the module is typically in
percent. For example, you could use this parameter to limit travel
in a valve or damper actuator.
Output High Limit

Modules
PID and Reset
Description
The output high limit defines the maximum output value. The
default is 100 because the module output is typically in percent. For
example, you could use this parameter to limit travel in a valve or
damper actuator.
Output from a PID module is typically expressed in percent
between 0 and 100. The output is converted to volts, milliamperes,
or time duration pulses (PWM) by using appropriate conversion
coefficients on the analog output point controlled by the PID or
Reset module.
Note: In a PID module where I and/or D are being used, you can enter any
desired output range, such as 318 (psi) or 400800 (cfm). In a P-
only PID module (see P-only Mode of Operation on page 10-7) an
output range of 0100 must be used.

Output Control Point (Failsafe)

Modules
PID
Description
This is a number between 0 and 100 percent. The default is 50
percent. Except in the P-only mode, this parameter value is output
from the PID module under the following conditions:
The setpoint exceeds the modules input high or low limit
parameters, OR:
The input point (input to the module) exceeds its sensor high
or low limit you specified when you defined the AI point in
the Resident I/O Points editor.
The control point (failsafe) value also provides a starting point for
the PID module upon initial processing of the module. This occurs
when you exit the module editor.
Note: See P-only Mode of Operation on page 10-7
Output Throttling Range

Modules
Floating
Description
This parameter defines the number of seconds it takes for the actu-
ator to move from being fully open to fully closed and vice versa.
This time becomes the maximum increase/decrease pulse duration
time. For the Floating module, enter a number between 0 and 255
seconds. The default is zero.

Output Turn-around Time

Modules
Floating
Description
This parameter defines the number of seconds it takes to complete
a reversal in the bidirectional motor rotation (i.e., changing from
clockwise to counter-clockwise or vise versa). Whenever the
Floating module changes direction (from increase to decrease or
vise versa) this turn-around time is added to the calculated output
pulse (for example, resulting in a longer decrease pulse if the
module were changing from increase to decrease). Enter a number
between 0 and 255 for this parameter. The default is zero.
Output Proportional Band

Modules
PID and Floating
Note: The operation described here does not occur if the PID module is
operating in P-only mode. P-only mode operation only occurs if you
enter a zero in both the rate interval and reset interval parameters.
Refer to P-only Mode of Operation on page 10-7. P-Only mode is
not available in the EPROM versions of the 7700 and 7740 DCUs.
Description
In DCUs and PCUs, this is the percent of the input range (the range
between the high and low input limits) that the input value must
change in order to change the output from zero to 100 percent. This
parameter setting can be a value between 1 and 1,000.
In DCUs and PCUs, proportional band is defined by the following
equation:
Control Band-
------------------------------- 100
Input Range

In MRs, UCs, and ASCs, if an output range of 100 is being used

(i.e., output low limit = 0 and output high limit = 100), the propor-
tional band equation is the same as the DCU/PCU equation above.
Otherwise, the proportional band for MRs, UCs, and ASCs is
defined by the following equation:
Control Band- --------------------------------

100
------------------------------- - 100
Input Range Output Range
For example, if the DCU/PCU PID module input low limit is 55

and the input high limit is 85, the difference between the two
numbers is 30. This is the input range. If you set the proportional
band to 90 (percent), the input must increase/decrease by 27 units
(90 percent of 30 is 27) to cause a 100 percent change in the output.
If you set the proportional band to 20 (percent) here, with the input
range still at 30, the input must increase or decrease by only 6 units
(20 percent of 30 is 6) to account for a 100 percent change in the
output.
If you select a larger proportional band, the output response rate
slows down or diminishes. In the example described above, it takes
longer for the input to move by 27 units than by 6. Conversely, a
smaller proportional band speeds up or increases the output
response rate.
Pure proportional control almost never results in an input reaching
and maintaining the specified setpoint because the closer the input
value approximates the setpoint the smaller the increment or
decrement of the output. At some point, the input value stops
changing between samples and the resulting output remains
constant. This condition is called offset. Offset can be eliminated
through the use of the reset interval parameter, described below.

Output Reset Interval

Modules
PID and Floating
Description
Use this function to eliminate a persistent error that is not of suffi-
cient magnitude (as measured at the specified sample interval) to
create a change in the output. This error, called offset, is described
in the proportional band parameter description. Enter a number
between 0 and 3,600 seconds for the reset interval.
The Reset Interval is divided into the Scan Interval to determine a
constant (Scan Interval Reset Interval) which is multiplied
against the current error (input minus setpoint). If you select a
small number for this interval, offset errors are corrected more
quickly. A large number entered here causes the opposite effect.
The reset interval is also referred to as the integral correction (I).
Note: In the PID module, if you enter a reset interval value other than zero,
the module operates in either PI or PID mode. In either mode, the
standard PID algorithm is used (refer to PID Algorithm on page
10-5).
If you enter a reset interval value of zero, the PID module operates in
either PD or P-only mode. The PD mode uses the standard PID algo-
rithm. The P-only mode uses an algorithm specific to that mode
(refer to P-only Mode of Operation on page 10-7). P-only mode is
Output Rate Interval

Modules
PID and Floating
Description
This is the rate portion of the PID or Floating module algorithm.
The rate interval is also referred to as the derivative correction (D).
Enter a number between 0 and 3,600 seconds for the rate interval.

The default is zero seconds. Use this function to compensate for

large input changes by comparing the direction and magnitude of
the error between samples and correcting the output accordingly.
The Rate Interval is divided by the Scan Interval to determine a
constant ( Rate Interval Scan Interval ) which is multiplied against
the change in error over the last three samples.
Note: In the PID module, if you enter a rate interval value other than zero,
the modules operates in either PD or PID mode. In either mode, the
standard PID algorithm is used (refer to PID Algorithm on page
10-5).
If you enter a rate interval value of zero, the PID module operates in
either PI or P-only mode. The PI mode uses the standard PID algo-
rithm. The P-only mode uses an algorithm specific to that mode
(refer to P-only Mode of Operation on page 10-7). P-only mode is
Failsafe Command
Modules
Two-position
Description
The action executed when the input or setpoint is no longer valid.
Use this option to plan system response to a setpoint or sensor
failure. Acceptable settings are 0 or 1. The default is 0.
The failsafe command is executed if the setpoint exceeds the
setpoint high or input low limits or if the process variable input
exceeds its sensor limits as defined in the Resident I/O Points
editor. A setting of 0 results in the first control command (of the
control command pair assigned to this output) being issued. A
setting of 1 results in the second control command being issued to

the output point. Refer to Control Description in Chapter 6,

Input and Output Points for information concerning control
descriptions and commands.
Note: A 0 command results in the first control command of the pair being
issued to the output point. This could represent either the energized
or deenergized state of the output depending on how the point's
control descriptions and commands are defined in the station param-
eters editor. Likewise, a 1 command results in the second control
command of the pair being issued to an output point.
Output Mode
Modules
Two-position, PID and Floating
Description
This parameter defines the response of the module. The actual
response differs depending on the selected module:
Two-position module: The mode you select determines what
happens when the input is higher or lower than the setpoint
(plus or minus one-half the differential).
PID or Floating module: The mode you select determines
whether module output increases or decreases as the error
(input minus setpoint) increases (input rises). This function
must be used to fit the response of the end device controlling
the process (i.e., normally open or normally closed valve or
damper).
The mode selection is similar to the decision you must make when
you buy an electric thermostat. Do you want one that is normally
open or normally closed, a heating or cooling thermostat?
There are two mode options:
Direct
Two-position module: If you select this mode, the two-
position module issues a 0 command to the output point
or line if the input rises above the setpoint plus one-half

the differential. The module issues a 1 command to the

output point or line if the input falls below the setpoint
minus one-half the differential.
PID module: If you select this mode, the module
increases its output if the input rises. The module
decreases its output value if the input falls.
Floating module: If you select this mode, the module
issues an increase pulse if the input rises. The module
issues a decrease pulse if the input falls.
Reverse
Two-position module: If you select this mode, the two-
position module issues a 1 command to the output point
or line if the input rises above the setpoint plus one-half
the differential. The module issues a 0 command to the
output point or line if the input falls below the setpoint
minus one-half the differential.
Note: A 0 command results in the first control command of the pair being
issued to the output point. This could represent either the energized
or deenergized state of the output depending on how the point's
control descriptions and commands are defined in the station param-
eters editor. Likewise, a 1 command results in the second control
command of the pair being issued to an output point.
PID module: If you select this mode, the module

decreases its output if the input rises. The module
increases its output value if the input falls.
Floating module: If you select this mode, the module
issues a decrease pulse if the input rises. The module
issues an increase pulse if the input falls.
Adaptive Control
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.

This parameter defines the point address or name of the discrete

point that will be used to enable/disable adaptive control. Adaptive
control is enabled/disabled by the state of the specified discrete
point (disabled = 0 and enabled = 1). Refer to Adaptive Tuning
on page 10-55.
Maximum Bump
Modules
PID and Floating
Description
A number between 0 and 100 percent. The default is 5 percent. This
parameter determines the size of the PID or Floating output step
change for automatic tuning in reference to the module control
point (PID) or midscale position (Floating). The bump should be
large enough to cause a change in the input (process variable) that
is greater than the noise band, but not so large as to damage the
controlled equipment. The typical range is 5 to 25 percent.
Settling Time
Modules
PID and Floating
Description
The settling time can be between 10 and 1,800 seconds. The default
is 120 seconds. This parameter is an estimate of the time it takes for
the input (process variable) to settle down after a setpoint change.
It is used for automatic and adaptive tuning as the minimum time
interval between a process disturbance and the next action. For
automatic tuning, it is the time interval between setting the output
to either the control point (PID) or to midscale (Floating) and the

beginning of the tuning cycle. For adaptive tuning, it is the

minimum time that will be observed between parameter calcula-
tions.
You can best estimate the settling time by observing the input
settling time after a natural process disturbance. To do this, you
measure the time interval from the point of the disturbance to a
point where the effects of the disturbance are negligible. The
typical range is between 30 and 150 seconds.
Maximum Overshoot
Modules
PID and Floating
Description
This parameter is a number between 0 and 100 percent. The default
is 10 percent. This parameter, along with target damping
(described below), controls the shape of the initial output response
to a process disturbance. The magnitude of the module response is
a qualitative measure of the controller. The typical range for this
parameter is between 10 and 50 percent.
Target Damping
Modules
PID and Floating
Description
Target damping can be set to a value between 1 and 75 percent. This
parameter represents the desired reduction in the process variable
overshoot from the first overshoot (maximum overshoot) to the
second, and so on. A value of 25 percent means the second over-
shoot magnitude should be 25 percent of the first. The recom-
mended value for this parameter is the default: 25.

Noise Band
Modules
PID and Floating
Description
Noise band can be set to a value between 0 and 100 percent. The
default is 2 percent. This parameter, specified as a percentage of the
input range, is the minimum process variable change that initiates
an adaptive calculation of the module parameters (provided the
Adaptive Control discrete point described above is equal to one).
Because adaptive tuning attempts to reshape the process variable
response after every such change, it is important to make the noise
band big enough to prevent inadvertent unnecessary tuning. The
typical range is between 2 and 10 percent.
Primary Input
Modules
Reset
Description
Select a line, point, or constant for this parameter. It is most
commonly a point, usually a sensed variable such as outside air
temperature. It can also be a line that is output from another
module, or a constant. In an MR- or ASC-resident module, only a
line or point can be specified a constant cannot be used.
Primary Inputs 1 and 2

Modules
Reset
Description
These input values, in engineering units of the primary sensed vari-
able, are the major factor in determining the primary output. In
our water heating example, these entries are the minimum and

maximum outside air temperature values over which we wish to

reset the primary output.
Primary Outputs 1 and 2

Modules
Reset
Description
These two values define the module output in conjunction with the
primary inputs. In our boiler example, these entries determine the
minimum and maximum outputs at the primary input values.
Note: At primary input 1, the module outputs the value entered as primary
output 1; the same occurs with primary input 2 and primary output
2. This lets you define either a directly proportional reset schedule or
an inversely proportional reset schedule.
Lets continue our example by entering some actual numbers. For

primary input values, use 0F and 65F. For primary output values,
use 150F and 80F. This creates the following reset schedule:
Outside Air Temp (Input) Hot Water Temp (Output)
(Primary 1) 0F 150F
(Primary 2) 65F 80F
In this schedule, the boiler setpoint varies linearly and inversely

proportionally to the outside air temperature. For finer control we
enter the next two sets of parameters: Secondary Inputs 1 and 2,
and Secondary Outputs 1 and 2.
Secondary Input
Modules
Reset
Description
Select a line, point, or constant for this parameter. In the boiler
example described previously, this would be an AI point sensing
the space temperature. This input secondarily resets the output

from the module. In an MR- or ASC-resident module, only a line

or point can be specified a constant cannot be used.
Secondary Inputs 1 and 2

Modules
Reset
Description
These input values, in engineering units of the secondary measured
variable, provide a second modifier for the module output. In our
boiler example we generally use the space temperature and enter
two values, one above and one below the desired space tempera-
ture.
Secondary Outputs 1 and 2

Modules
Reset
Description
These output values, in engineering units of the controlled vari-
able, offset the setpoint derived by the primary input/output
schedule. A typical secondary input/output schedule might look
like this:
Space Temp (Input) Water Temp (Output)
(Secondary 1) 75F 20F
(Secondary 2) 68F +20F
Adding the influence of the secondary schedule values to the above

developed primary schedule provides the following results:
Outside Air Temp Space Temp Water Temp
(Primary) (Secondary) (Output)
0F 68F 170F
0F 75F 130F
65F 68F 100F
65F 75F 60F

Inputs 1 4
Modules
HiLo
Description
A line, point, or constant. Each of the four inputs are normally the
same type (analog or discrete). Mixing of discrete states and analog
values is typically not done.
DI = 0
Modules
Relay
Description
This is the state/value passed to the output by the Relay module
when the discrete input (see above) is 0. Select a line, point, or a
constant. A constant is often used here to direct a setpoint to an
unoccupied value when a point, such as an air handling unit, is off,
in order to close a modulating valve or perform a similar task.
DI = 1
Modules
Relay
Description
This is the state/value passed by the module when the discrete input
(see above) is 1. Select a line, point, or a constant.
Settings (Relay Types)

Modules
Relay
Description
Standard This is the default relay type. Its transition is
completed based upon the sample interval (refer to Sample
Interval on page 10-26).

Delay Before Make This relay type delays the output of the
DI = 1 state/value following a transition of the discrete input from
0 to 1. The duration of the delay is defined by the time delay param-
eter. The time delay only affects the output of the DI = 1
state/value. When the discrete input transitions from 1 back to 0,
the relay immediately directs the DI = 0 state/value to the module
output.
Delay Before Break This relay type delays the output of the
DI = 0 state/value following a transition of the discrete input from
1 to 0. The duration of the delay is defined by the time delay param-
eter. The time delay only affects the output of the DI = 0
state/value. When the discrete input transitions from 0 to 1, the
relay immediately directs the DI = 1 state/value to the module
output.
Interval Timer This relay type sustains the output of the DI = 1
state/value for a specified duration following a transition of the
discrete input from 0 to 1. The DI = 1 state/value is directed to the
module output for a duration defined by the time delay parameter.
When the time delay expires, the output automatically reverts back
to the state/value of the DI = 0 input, regardless of the discrete
input state.
Time Delay
Modules
Relay
Description
This parameter defines the number of seconds for the interval
timer, delay-before-break, and delay-before-make relays. Enter a
number between 0 and 86,400 seconds (24 hours). The default is
zero seconds. Time delays are not used by the standard relay.

History Direct Digital Control
DI Select
Modules
Relay
Description
This input can be a line or a point. If you select a point you must
use a DO, DI, DC, or DA point type. If you select a line it must carry
a discrete state (0 or 1) rather than an analog value. This parameter
is comparable to a relay coil. If the state of the line or point entered
here is a 1, the relay module is energized and the module passes
the state/value entering at the DI = 1 port. When the Relay module
is deenergized, the DI = 0 state/value is passed to the module
output.
History
I/NET provides an on-line tuning capability for PID and Floating
modules (up to four modules per controller). In order to activate
the tuning function, you must first add the PID or Floating
module(s) to the history record.
Due to memory requirements, there is a limit of four modules that
can be contained in the controllers history record at any one time.
If you try to add a fifth module, you will receive an error message.
If you need to add another module, delete an existing module first.
Tuning
Tuning is the on-line, automatic adjustment of PID or Floating
module parameters. I/NET provides the following tuning func-
tions:
Manual Tune
Automatic Tune
Input/Output Plot
Each of these tuning features is described in the following para-
graphs.

Direct Digital Control Tuning
Manual Tune
The manual tune function displays current module parameter
values and allows you to adjust these values. You may then monitor
the module operation and, if necessary, make further adjustments.
The manual tune parameters are described in the following para-
graphs. Refer to the individual PID and Floating module descrip-
tions earlier in the chapter for extended definitions of setpoint,
proportional band, reset interval, and rate interval.
Setpoint
This is the current value of the setpoint (line or point) or the
permanent setpoint (constant; defined when you created the PID
or Floating module). You may manipulate the current setpoint
value.
Proportional Band (percent)
This displays the permanent and current proportional band values.
The permanent proportional band is the one you defined when you
created the PID or Floating module. You may vary the current
proportional band between 1 and 1000 percent.
Reset interval (seconds)
This displays the permanent and current reset interval values. The
permanent reset interval is the one you defined when you created
the PID or Floating module. You may vary the current reset interval
between 0 and 3,600 seconds.
Rate Interval (seconds)
This displays the permanent and current rate intervals. The perma-
nent rate interval is the one you defined when you created the PID
or Floating module. You may vary the current rate interval between
0 and 3,600 seconds.
Input/Output Plot
This feature displays a plot of the input and output of the selected
module. You can then observe the on-line results of the changes
you made in the Manual Tune editor.

Tuning Direct Digital Control
Automatic Tune
This function provides automatic calculation of the P, I, and D
constants used in the PID and Floating modules. This is done by
driving the output of the PID module to the control point value, or
to midscale in the case of a Floating module, for the duration of the
settling time. The output is then alternately forced up and down
numerous times by the value of the maximum bump percentage.
Settling time and maximum bump are defined earlier in this
chapter. By monitoring the resulting changes in the process vari-
able input to the module, the controller automatically calculates
and enters the P, I, and D constants into the module editor.
Automatic Tuning Parameters
There are two parameters associated with automatic tuning.
Tsettle = settling time.
Vbump% = maximum bump percent.
A third parameter is derived from those already defined:
Vbump = maximum bump, which is the maximum bump
percent multiplied by the difference between the output high
limit and the output low limit (see below).
Vbump = Vbump% (Output High Limit Output Low Limit)
Automatic Tuning Process
Figure10-1, Automatic Tuning illustrates the automatic tuning
process. The process is explained thereafter.
For a PID module, at time To , the output is moved to the control
point (failsafe) output value specified for the module, and the scan
rate is changed to 1 second. The output stays at the control output
for the settling time (Tsettle).
For a Floating module, at time To , the increase output is pulsed for
a period equal to two times the throttling range. This is followed by
the decrease output being pulsed for a time equal to one-half of the
throttling range. This is done to ensure that the output is at
midscale (50%). At this time, the scan rate is changed to 1 second.
The output stays at 50% for the settling time.

Settling Time
Max.
Output Bump
Max.
Input Bump
T0 TX TX + 1 TX + 2
Auto-Tune Input at
Start T0 + T settle 1 Cycle 1 Cycle Last Cycle
5 Cycles
Figure 10-1. Automatic Tuning
In either case (PID or Floating), after the settling time, the input is
recorded, and the output is then increased by Vbump . The editor
determines how long it takes for the input (PV) to settle-out (rate
of change less than 5%).
Warning: The settling time (Tsettle) should be the amount of time it takes for the
rate of change of the input (PV) to become 5% or less AFTER it has
changed by an amount greater than 5% due to the output being
changed by the maximum bump (Vbump). After any change in the
output, the rate of change of the input must become 5% or less within
the settling time or a time-out error will occur.
The output is then decreased from either the control point (fail-
safe) output, Co , (PID module) or midscale (Floating module) by
Vbump . The output stays there until the input becomes the value
which it was at Time = To + Tsettle .
Warning: If the input does not cross the value of the input at Time = To + Tsettle
within the settling time, a time-out error will occur.
The output is once again increased by Vbump , and this process of

increasing and decreasing the output is repeated for 5 cycles after
the first output increase/decrease transition. During the process,

the time at each change of output (Tx , Tx+1 , ... Tx+10) is stored. The
minimum and maximum input value during each cycle is also
stored.
Automatic tuning now goes about the task of calculating the
PID/Floating module scan rate, proportional band, mode of oper-
ation (i.e., reverse or direct), and Integral (Ti ) and Derivative (Td )
coefficients. These parameters are determined as follows:
The mode of operation is determined by noting how the
input reacts to a change in the output (i.e., does it increase
when the output is increased?).
Module scan rate (Ts) is determined from the information
stored during the tuning process and is one-tenth (1/10) of the
average fundamental period of the process (Tpavg). In mathe-
matical terms:
( T x + 1 T x ) + ( T x + 2 T x + 1 ) + ...
10T s = ------------------------------------------------------------------------------------- = Tpavg
5
Proportional Band is determined by:
Calculating the average of the input maximums recorded
at each sample during the tuning process.
Calculating the average of the input minimums recorded
at each sample during the tuning process.
Calculating the difference between the input maximum
average value and the input minimum average value and
dividing it by two.
This value is then divided by the input span (i.e., the
difference between the input high limit and the input low
limit) in order to determine the percent change of input
which was caused by a known change in the output (i.e.,
the maximum bump, Vbump).
With the percent change input known and the percent
change in output known (the maximum bump percent,
Vbump%), the percent change in input is divided by the
percent change in output to determine the proportional
band.
The integral and derivative coefficients (Ti and Td , respec-
tively) can be determined as a function of the proportional

band and the average fundamental frequency of the process

(Tpavg) if one uses either:
Laplace transformations to determine poles and zeros,
which yields Nyquist intervals (difference in poles and
zeroes). The coefficients are then calculated via a loop
transfer function which was the basis for your Laplace
transformations.
Linear Approximation and the Zeigler-Nichols approach,
which is the method TAC uses in determining the inte-
gral and derivative coefficients.
Note: You may wish to obtain reference material concerning the Ziegler-
Nichols approach for linear approximation which is available from
most libraries.
Adaptive Tuning
Once commissioned, adaptive tuning ensures that a process is
being controlled optimally by changing the proportional band,
integral, and derivative coefficients to best react to a process whose
environmental characteristics are subject to change.
The following paragraphs describe when adaptive tuning is
performed but do not address the theory behind adaptive tuning
nor its mathematical implementation. TACs implementation of
adaptive tuning is proprietary in nature and cannot be detailed.
Adaptive Tuning Parameters
There are four parameters associated with adaptive tuning:
ACP = adaptive control point
NB% = noise band percent
MO% = maximum overshoot percent
TD% = target damping percent
Adaptive Tuning Process
The first part of the process is to allow adaptive tuning to occur. It
may sound like a very simple question, but it may not be. Some of
the questions that have to be answered include:

Is the equipment on?

You dont want the system to adapt the PID/Floating parame-
ters if the equipment isnt running.
Is associated equipment on?
The equipment which is being controlled directly may be
running, but can it react (e.g., heat or cool) without some
other equipment running.
Is this a start up situation?
If the equipment is just starting, can it react immediately (e.g.,
heat or cool instantaneously) or does it need some time delay
to come up to capacity.
The adaptive control point (ACP) is a discrete point address in the
system used to enable adaptive tuning. When this point is in the 1
state, adaptive tuning is enabled. In short, the adaptive control
point should be on (true), 1, when equipment is running
normally. Refer to Adaptive Control on page 10-42.
Now that the PID/Floating parameters can be adapted, the noise
band percent (NB%) parameter is used to determine when adap-
tion shall occur. The noise band is a percentage applied to the input
range of the module (the difference between the input high limit
and the input low limit) to determine how much change in the
input can be tolerated before adaptive tuning occurs. For example,
if input low limit = 10, input high limit = 30, and noise band
(NB) = 5%, then the range is 20 and the resulting noise band is 5%
of 20, or 1. Adaptive tuning will occur anytime the input of the
module changes by more than 1.
Before any check is made against the noise band, the input must
traverse through three classic decay cycles. A decay cycle can be
defined as a process disturbance and the resultant settling time.
Each of these must have exceeded the noise band AND have
occurred within the fundamental cycle of the process (see
Figure10-2, Three Decay Cycles).
Samples of the input value are collected during the three decay
cycles. A total of three sets of 10 samples are collected. A center line
for these samples is determined. The highs and lows of the cycle are
compared to this center line and the difference is compared with

NB
NB
Fundamental
Frequency NB
Figure 10-2. Three Decay Cycles
the noise band. If the noise band has been exceeded, adaptive
tuning can occur.
Now that the PID/Floating parameters are going to be adapted, the
maximum overshoot percent (MO%) parameter is used to deter-
mine what will be adapted. The maximum overshoot is a
percentage applied to the input range of the module (the difference
between the input high limit and the input low limit) to determine
which of the PID coefficients will be adapted. For example, if input
low limit = 10, input high limit = 30, and maximum overshoot
(MO%) = 10, then the range is 20 and the resulting maximum
overshoot is 10% of 20, or 2.
Caution: Noise band must be less than maximum overshoot.
If noise band AND maximum overshoot are exceeded, the propor-

tional band only is adjusted (see Figure10-3, PID Coefficients
Adaption) and is in fact doubled (i.e., the gain is cut in half). The
proportional band is doubled every three fundamental frequencies
of the process until either the maximum overshoot is satisfied or
both the maximum overshoot and noise band are satisfied.
If maximum overshoot is satisfied, but the noise band is exceeded,
then the integral and derivative coefficients are adapted (see
Figure10-3, PID Coefficients Adaption). Once maximum over-
shoot and noise band are satisfied, adaption is finished.
Note: The adaptation of the integral and derivative coefficients are func-
tions of time and the remaining PID parameter, target damping, and
are proprietary to TAC.
The final PID parameter, target damping percent (TD%), is your

input as to how you would like an input to react. Keeping in mind

Max.
Overshoot NB
Max. P Only Adapt

Overshoot NB
I,D Adapt
Max.
Overshoot NB
No Adapt
Figure 10-3. PID Coefficients Adaption

the decaying cycles, typically this value is 25%. With a value of
25%, the goal is to make the subsequent cycles 25% of the previous
(i.e., current error is 25% of the previous error). Figure10-4,
Target Damping illustrates target damping.
D1
D3
D2
Output
Figure 10-4. Target Damping
See Also: Direct Digital Control in TCON299, I/NET Seven Operator

Guide
ASHRAE1 handbook titled HVAC Applications
1.
American Society of Heating, Refrigerating & Air-Conditioning Engineers, Inc.

CHAPTER
11
48
Unitary Control
Unitary controllers (UCs) and their associated interface (UCI) let

I/NET distribute intelligence to the level of the terminal unit. The
unitary controller interface (UCI) acts as an interface between the
I/NET controller LAN and the I/NET UC network. The controller
LAN operates using a token passing protocol at 9600 baud or 19.2
KB and the UC network operates using a scanning/polling protocol
operating at 9600 baud.
The UCI can contain all the database and application parameters
for up to 32 unitary controllers. The UCI also provides for the
globalization of data, collects data for trending, and performs save
and restore tasks. The UCI lets you perform all database develop-
ment on-line without being physically connected to the remote
UCs.
UCs contain unique modular application strategies designed to
provide economic control of several different types of equipment.
The VAV module provides distributed control for single- and
double-duct (constant or variable) VAV boxes. The AHU module
provides distributed control for packaged roof-top and small built-
up air handling units. The HPMP module provides distributed
control for packaged heat pump units.
In addition to the dedicated functions for these devices, the UC
provides specialized DDC control that mimics the PID and FLT
DDC modules found in other controller types. These DDC func-
tions are not contained in DDC Modules as in other controller
types but are implemented as point extensions much like ATS and
calculated points are done.

The Parent Point Unitary Control
The Parent Point

The 7760 Unitary Controller Interface is the only controller that
uses the term parent point. A parent point is nothing more than
the AO or DO point to which you add a UC extension: VAV, AHU,
PID, FLT, or HPMP. The functioning of the extension is directly
tied to the state (0 or 1 in the case of a DO point) of the parent point
and the command pairing (refer to the Caution on page 11-28 for
the accepted control command pairing). All parent points must be
internal or external DO or AO points. For comparison, in a DCU
you could think of the point to which you add any extension (such
as Runtime or Consumption) as the parent point of that extension.
The parent point is usually assigned the first output address in the
UC (LLSSPP00), but this is not a hard and fast rule.
Note: A DC point should not be used as the parent point of a UC extension.
Caution: You may recall that you entered a minimum trip/close time for DO
and DC points when you first defined those points in the resident I/O
points editor. These times are honored only when the UCI issues a
command to the point (demand, time scheduling, temperature
control, or calculated point), but not when one of the UCs issues a
command. This includes the VAV-UC, AHU-UC, and HPMP-UC
editors described in this chapter.
You should consider increasing scan times of the parent point
(through the resident I/O points editor), widening differentials, as
well as using activation delays or interstage delays (through the UC-
specific editor) provided in the UC to prevent damage to mechanical
equipment.
Configuring the Unitary Controller Interface

You assign a type designation to a UC through the UC Configura-
tion editor. The UC type can be VAV, AHU, HPMP, General, or
Internal. A VAV, AHU, HPMP, or General type indicates that data-
base points are to be defined in the UCIs resident I/O points editor
for actual UC hardware. A General type indicates the UCI is func-

Unitary Control Configuring the Unitary Controller Interface
tioning as a universal UC with eight inputs and eight outputs. After

you define a UC as VAV, AHU, HPMP, or General, the UCI begins
to poll and scan the hardware associated with the type you selected.
An Internal type indicates that the point(s) reside in the UCI. Since
these points reside in the UCI itself, the UCI does not attempt to
communicate with actual UCs defined as Internal. This type
(Internal) is commonly used for calculated points. See Calcula-
tions (C) in Chapter 7, Point Extensions, for information on calcu-
lated points.
The Internal type can also be used to set up your database before
the equipment hardware is ready. This allows you to define the
specific parameters and points for the UC using a workstation, Tap,
and a UCI before the UC-LAN is installed. When the UCs are
powered up and communications are established, change the UC
configuration type from Internal to VAV, AHU, HPMP, or General
for those addresses that represent actual UC hardware, and then
exit the editor to begin actual system control. The database infor-
mation will automatically be downloaded to the UC when the type
is changed from Internal to any other type. The off-line database
editor can also be used to build UCI/UC databases.
See Also: The chapter on Controller Configuration in TCON299, I/NET

Seven Operator Guide.
An Internal UC, when changed to a VAV, AHU, HPMP or
General UC, and not communicating with the UCI, will display all
internal or external points as old data. If the UC is changed to a
VAV, AHU, HPMP or General UC, and is communicating properly,
all internal and external points will show up with no old data
flags.
An asterisk beside a UC address in the UC configuration editor
indicates the UCI cannot establish communications with the UC.
The asterisk disappears when successful communications are
established.
When you perform a station restore on a UCI, all of the program-
ming information is downloaded to the UCI. In addition, the UCI
further distributes information to UCs you define as VAV, AHU,

Configuring the Unitary Controller Interface Unitary Control
HPMP, or General. This allows the UCs to function in a stand-

alone mode if communications are severed between the UCI and
the UCs.
Because this transfer of information between the host workstation,
UCI, and UCs can be rather lengthy, a Please Stand By message
appears anytime you perform a station save or station restore to a
7760 controller (UCI).
Note: Assigning a type (AHU, HPMP, VAV, General) to a UC in the UC

configuration editor is purely for informational purposes and does
not automatically define the UC as that type. You assign the appro-
priate extension to the parent point in the Unitary Control editor
(refer to The Parent Point on page 11-2 and also Unitary Control
Parameters on page 11-29). This ultimately determines the UC
type.
UC/UCI Editor Location

Even though an extension is resident in the UCI, it may be used to
perform a control function in a UC. Keep in mind the possibility of
lost communications due to a severed communications link
between the UCI and UCs. Only those editors listed below as resi-
dent in the UC can continue to work correctly if communications
are severed between the UCI and UC.
UCI Resident Programming

The following editors reside in the UCI:
Configuration/Status Event Sequences

Station Save Event Actions
Station Restore Runtime
Station Parameters Consumption
Control Descriptions Alarm Inhibit
Control Commands Time Scheduling
State Descriptions Demand Control
Conversion Coefficients Temperature Control
Engineering Units Special Days

Unitary Control UC Editor Theory of Operation
Resident I/O Points Unitary Control

Calculations UC-History/Tuning
Event Definitions UC Configuration
UC Resident Programming
The following editors reside in the UC:
Station parameters
Control commands
Conversion coefficients
Resident I/O points
Unitary control
VAV-UC extensions
AHU-UC extensions
HPMP-UC extensions
UC-PID extensions
UC-FLT extensions
UC Editor Theory of Operation
General
The first discrete output address in the UC (typically point address
LLSSPP00) is referred to as the parent point of the controller. The
desired UC extension (VAV, AHU, or HPMP) is appended to the
point as an extension through the Unitary Controller editor. This
editor contains the specific parameters for the type of UC extension
you selected.
A time scheduling extension is typically appended to the UC parent
point. When the schedule commands the UC parent point on (1),
the UC switches to its normal setpoints. When the schedule
commands the UC parent point off (0), the UC switches to its
setup/setback setpoints. You can also append a temperature control
extension to the UC parent point if you want optimized start or
stop.

UC Editor Theory of Operation Unitary Control
Instead of using time scheduling and temperature control exten-

sions to change over between day and night, a calculated point or
event sequence can be used to toggle the UC parent point from 0
(night) to 1 (day). However, if you want push-button remote over-
ride (all extension types) or mixing dampers warmup/cooldown
control (AHU and HPMP only), you must append a time sched-
uling extension to the parent point.
During occupied hours, when the state of the economy override
point (internal or external DI or DO point) goes to 1, the unit
switches to the economy setpoints. When the economy override
point returns to the 0 state, the UC returns to the normal setpoints.
For example, you may wish to have the demand control program
shed or restore a particular AHU, VAV box, or heat pump. This can
be accomplished several ways. One of the loads in the demand
control editor could be for the UC parent point that forces the
AHU or VAV box or heat pump to its setup/setback setpoints
during a shed condition, or one of the loads in the demand control
editor could be for the economy override internal DO address in
which case the AHU, VAV box, or heat pump switches to its
economy setpoints during a shed condition.
The current setpoint (normal, economy, or setup/setback), is used
to control:
The VAV box fan or heat stages (if present) while honoring
the activation delay (stage 1 only) and the setpoint offsets
(stages 2 and 3). All three stages of heat are locked off during
the activation delay time-out.
The AHU fan, stages of cooling (if present), or stages of
heating (if present), always honoring the interstage delays
(stages 1 to 2 cooling and stages 2 to 3 cooling only) and the
setpoint offsets (stages 2 and 3 cooling and stages 2 and 3
heating).
The heat pump fan, reversing valve, compressor stages, or
heat stage strips (if present) always honoring the interstage
delays (stages 1 to 2 compressor and stages 2 to 3 compressor
only) and the setpoint offsets (stages 2 and 3 compressor and
stages 1, 2, and 3 heat strip).

UC Damper/Valve Control
The VAV, AHU, and HPMP UCs can provide direct digital control
for accurate control of damper and valve actuators typically used in
VAV boxes, packaged roof-top air handling units, small built up air
handling units, and packaged heat pump units. You may use either
a PID extension with a PWM control output, or a FLT extension
with dual pulsed outputs for bidirectional electric damper/valve
operators.
The DO-PID and DO-FLT extensions are used when you have a
specific application that requires modulated control and the
output to be 0 (closed) when the DO-PID or DO-FLT parent point
is commanded off. A typical application is AHU or HPMP mixing
damper control. The setpoint of a DO-PID or DO-FLT can only be
a constant.
DO-PID and DO-FLT extensions are very similar to the PID and
Floating modules used in all other I/NET controllers. Refer to
Chapter 10, Direct Digital Control, for a complete discussion of all
DDC modules.
AO-PID and AO-FLT extensions are similar to DO-PID and DO-
FLT extensions. The major difference is that the AO extensions are
appended to an AO point, whereas the DO extensions are
appended to a DO point. This difference lets you use a varying
setpoint. The setpoint used by the AO-PID or AO-FLT is the
current value of the AO parent point itself. (Remember that the
setpoint for a DO-PID or DO-FLT is a constant). Unlike the DO
extensions, the output of an AO extension will not automatically
drive the output to 0 if the parent point is off (0).
Pulse Width Modulation, or PWM, is a technique used to direct the
output of a PID extension to an external AO point address. The UC
automatically ranges the output in percent full scale and converts
the output to a timed duration pulse.
As an example, assume an AO point is designated as the control
output for the mixed air damper and identified as the output target
of the DO-PID extension. The conversion coefficient pair is m =
0.03922, and b = 0.39222. These coefficients produce a full range

output from 0.1 seconds to 25.6 seconds (0100 percent). By use of

an external transducer, this AO point may then be converted to
pressure, voltage, or current signal as appropriate.
The output of the extension is defined as an external AO point
address. The actual setpoint of the extension is defined as the value
of the internal AO parent point address of the PID extension, if an
AO-PID is used.
If your final controlled device requires a separate increase and
decrease output, for example bidirectional damper/valve motors,
you would select an AO-FLT or DO-FLT extension for this applica-
tion.
VAV Box Control

Refer to Figures 11-1 and 11-2 for a block diagram of the VAV func-
tion. Refer to Figure 11-3 for a VAV-UC heating staging diagram.
The control strategy of the VAV-UC can be altered to accommodate
various configurations of VAV boxes. The most basic control strat-
egies are concerned with whether the central air supply system is
providing warm air during the heating season or whether heat
strips (or hot water valves) are used for heating purposes. (Note
that there are configurations when neither are present.) Another
strategy may be implemented that is dependent upon whether a
CFM airflow sensor is present (pressure-independent system) or
not present (pressure-dependent system).
In the heating mode of the VAV-UC extension, if there are heat
strips or hot water valves present (i.e., no central plant heat), the
UC turns on the fan and the first stage of heat if the space temper-
ature falls below the active setpoint minus one-half the differential.
If there is more than one stage of heat, the second and third stages
of heat come on after the fan and first stage of heat, provided their
individual temperature offsets have been honored. As the temper-
ature begins to rise, the stages of heat turn off in the opposite order
that they were turned on; last on is first off. When the temperature
reaches the active setpoint plus one-half the differential, the first
stage of heat and the fan are turned off.

ATC
VAV-UC Schedule
Parent Point
Internal DO
Internal DO
SSPP01
SSPP00 ATS
Schedule ***
Central Plant
Heat
Option
* *
Internal DI
OR
SSPP02
Fan
* External DO
SSPP05 Output Point
Internal DO **
Economy SSPP01 Stage 1 Heat
Override
Option
* External DO
SSPP04 Output Point
Internal DI OR
SSPP05
External DO Stage 2 Heat
* SSPP03 Output Point
Setpoint Adj
Potentiometer External AI
Option SSPP03 External DO Stage 3 Heat
OR SSPP02 Output Point
Override
Pushbutton External DI VAV-UC
SSPP04
Option Extension
Internal DO Central Plant
SSPP01 Temperature Heat
Indicator
Setpoint
Override
Point
External DO
OR
SSPP02
Damper Override Mode

Interlock Internal AO
Sp
SSPP06
AO-PID
AO-PID Parent Point
Space Temp External AI Space Temp Setpoint Extension
Sensor SSPP00 Pv
Output
AO-FLT Parent Point
CFM Setpoint
Temperature
to CFM Convertor
Internal AO
Sp
AO-FLT SSPP07
Extension
External AI CFM Airflow
Outputs Pv SSPP06 Sensor
Inc Dec
CFM Controller Hardware

Output Bit 6 Increase and Decrease
Database Point Output Signals to
Address not Required Bi-Directional
Hardware Damper Actuator
Output Bit 7
* Point Address could also be an external point.

** Fan Interlock
*** ATS Schedule required if override pushbutton option is being used.
Figure 11-1. VAV-UC Editor Block Diagram

Pressure-Independent Single-Duct VAV Box Control
(CFM Setpoint Reset by Space Temperature)

ATC
VAV-UC Schedule
Parent Point
Internal DO
Internal DO
SSPP01
SSPP00 ATS
Schedule ***
Central Plant
Heat
Option
* *
Internal DI
OR
SSPP02
Fan
* External DO
SSPP05 Output Point
Internal DO **
Economy SSPP01 Stage 1 Heat
Override
Option
* External DO
SSPP04 Output Point
Internal DI OR
SSPP05
External DO Stage 2 Heat
* SSPP03 Output Point
Setpoint Adj
Potentiometer External AI
Option SSPP03 External DO Stage 3 Heat
OR SSPP02 Output Point
Override
Pushbutton External DI VAV-UC
SSPP04
Option Extension
Central Plant
Internal DO Heat
SSPP01 Temperature
Indicator
Setpoint
Override
Point
External DO
OR
SSPP02
Damper Override
Interlock
Space Temp External AI

Sensor SSPP00
Mode
Sp Internal AO AO-FLT Parent Point

AO-FLT SSPP07 Temperature Setpoint
Extension
Outputs Pv
Inc Dec
Temperature Hardware
Controller Output Bit 6 Increase and Decrease
Database Point Output Signals to
Address not Required Bi-Directional
Hardware Damper Actuator
Output Bit 7

** Fan Interlock
*** ATS Schedule required if override pushbutton option is being used.
Figure 11-2. VAV-UC Editor Block Diagram

Pressure-Dependent Single-Duct VAV Box Control
(No CFM Reset)

78
76
H1 OFF
74
1/2 Differential
Normal H2 OFF
Heating 72
Setpoint
1/2 Differential H2
Offset from
70 Setpoint H3
H1 ON Offset from
Setpoint
H3 OFF
68
H2 ON
66
H3 ON
64
62
NOTES: 1. Diagram above represents the control actions which would occur if the
Controller was set up with the following parameters:
Heating Setpoint = 72 Degrees
Differential = 4 Degrees
Heat 2 Offset = 4 Degrees
2. Heat Stage 1 is turned ON at Setpoint minus 1/2 Differential.

Heat Stage 1 is turned OFF at Setpoint plus 1/2 Differential.
3. Heat Stage 2 is turned ON at Setpoint minus H2 Offset.

Heat Stage 2 is turned OFF at Heating Setpoint

Heat Stage 3 is turned OFF at Setpoint minus H2 Offset.
Figure 11-3. VAV-UC Heating Staging
If the central air supply system provides warm air during the
heating season, the VAV-UC will modulate the CFM air flow to
maintain the desired space temperature. When operating in the
central plant heat mode, the output of the VAV control strategy is
set to reverse acting.

Note in the following discussion, if there is no CFM air flow sensor

present, the AO-PID extension is not used and the output of the
VAV extension is applied directly to the AO-FLT extension.
In the VAV-UC the current setpoint (Normal, Economy, or
Setup/Setback) value is output to an internal AO point (SSPP06
AO; the temperature setpoint entry in the VAV editor). This point
is referred to as the AO-PID parent point because an AO-PID
extension is typically attached to it. The current value of this
internal AO point becomes the setpoint of the AO-PID extension.
The scan rate of the AO point becomes the sample rate of the AO-
PID extension.
This AO-PID extension continually compares the difference
between the actual space temperature (e.g., external AI point:
address LLSSPP00) and the desired space temperature setpoint
(e.g., internal AO point: address LLSSPP06), and varies its output
to the next internal AO point address (e.g, internal AO point:
address LLSSPP07, CFM setpoint) accordingly. The addresses
listed here are those typically used; however, you can use any avail-
able address.
For example, in a cooling application assume the current space
temperature setpoint (value of internal AO LLSSPP06) is 72
degrees. If the actual space temperature rises above 72 degrees, the
AO-PID extension increases its output calling for more CFM. If the
actual space temperature falls below 72 degrees, the AO-PID exten-
sion decreases its output calling for less CFM.
The output of the AO-PID extension drives another internal AO
point (address LLSSPP07). This address is referred to as the AO-
FLT parent point because an AO-FLT extension is attached to it.
The current value of this internal AO is the setpoint of the AO-FLT
extension. The scan rate of the internal AO point is the sample rate
of the AO-FLT extension.
The AO-FLT extension actually controls the VAV box damper actu-
ator. If a CFM airflow sensor is present, the AO-FLT continually
compares the actual CFM air flow (external AI point: address
LLSSPP06) to the desired CFM setpoint (the value of the internal
AO point address LLSSPP07) and opens or closes the VAV box
damper accordingly. If a CFM airflow sensor is not present, the
AO-FLT continually compares the space temperature sensor input

with the temperature setpoint output of the VAV extension and

adjusts the VAV box damper accordingly. An AO-FLT extension is
used because typically a bidirectional pulsed output is required to
drive the damper actuator.
Therefore, the VAV-UC controls cooling in the area being served by
the VAV box by actually controlling the VAV box CFM air flow and
resets this air flow setpoint according to the actual space tempera-
ture. On a call for heating, the CFM can be controlled to its
minimum value if desired (as a function of the AO-PID setup
parameters).
Interlocks are provided which prevent conflicting operating
modes. These interlocks are a heating/cooling interlock, and a
fan/heat interlock. The heating/ cooling interlock prevents the UC
from being in both the heating and cooling mode at the same time,
while the fan/heat interlock insures that all heat stages are
commanded to OFF if the fan is off.
AHU Control
Refer to Figure 11-4 for a block diagram of the AHU function.
Refer to Figure 11-5 for an example of AHU-UC cooling/heating
staging.
If the space temperature falls below the active setpoint minus one-
half the differential, the AHU-UC turns on the fan and the first
stage of heat. If there is more than one stage of heat, the second and
third stages of heat come on after the fan and first stage of heat,
provided their individual temperature offsets have been honored.
As the temperature then begins to rise, the stages of heat turn off in
the opposite order that they were turned on; last on is first off.
When the temperature reaches the active setpoint plus one-half the
differential, the first stage of heat and the fan are turned off.
If the space temperature rises above the active setpoint plus one-
half the differential, the AHU-UC turns on the fan and the first
stage of cooling. If there is more than one stage of cooling, the
second and third stages of cooling come on after the fan and first
stage of cooling, provided their individual temperature offsets and
interstage delays have been honored. As the temperature then
begins to fall, the stages of cooling turn off in the opposite order

AHU-UC ATC
Parent Point Extension
Internal DO
SSPP00 ATS
Schedule ***
*
Sensor SSPP00
External DO Fan Output
See Note Point
Economy
Internal DO
See Note ** External DO Stage 1 Cooling
Override
Option
* I O See Note Output Point
Internal DI
See Note
OR n u
External DO Stage 2 Cooling
p t
* u p
See Note Output Point
Setpoint Adjustment
Potentiometer External AI t u External DO Stage 3 Cooling
SSPP03 t See Note Output Point
Option s
s Stage 1 Heating
External DO
Override
Pushbutton
External DI
See Note
AHU-UC
Option
Extension External DO Stage 2 Heating
Output Point
See Note
Internal DO
See Note Damper
Indicator External DO Stage 3 Heating
Override Control
Point
External DO
OR
See Note
Internal DO Internal DO
See Note OR See Note
Mixed Air Mixed Air

Temperature Temperature
Setpoint Constant Sp
DO-PID DO-FLT Sp Setpoint Constant
Extension Extension
External AI External AI
See Note Pv Pv See Note
Outputs
Mixed Air Output Inc Dec

Mixed Air
Pulse Width Modulated External DO Hardware Hardware

Discrete Output Point See Note Output Bit Output Bit
Database
Point Address
Note: The only "fixed" or reserved addresses in the AHU-UC are: External AI SSPP00 (Space Not Required
Temperature) and External AI SSPP03 (Setpoint Adjustment) when the CSI Model LTS80U
Sensor are used. All other input addresses or output addresses are NOT reserved and can
be used for any external field device up to the maximum point count of the controller.
The AHU-UC Controller only has eight input addresses and eight output addresses
This drawing is intended to show all the functions of the Editor and therefore more than
eight output points are shown. (ONLY EIGHT ARE AVAILABLE)

** Fan Interlock.
*** ATS Schedule required if override pushbutton and/or warmup/cooldown mode are being used.
Figure 11-4. AHU-UC Editor Block Diagram

80
78
C3 ON
76
C2 ON
C3
Offset from
C2 C3 OFF Setpoint
74 Offset from
C1 ON
Setpoint
Normal 1/ Differential
Cooling 72 2
Setpoint 1/ Differential C2 OFF
2
C1 OFF
70
H1 OFF
Normal H2 OFF
1/ Differential
Heating 68 2
Setpoint 1/ Differential
2 H2
Offset from
H1 ON H3
66 Setpoint
Offset from
Setpoint
H3 OFF
64
H2 ON
62
Interstage Interstage H3 ON
Delay Delay
60
NOTES: 1. Diagram above represents the control actions which would occur if the
Cooling Setpoint = 72 Degrees
Differential = 2 Degree
Cool 2 Offset = 3 Degrees
Cool 3 Offset = 5 Degrees
Heating Setpoint = 68 Degrees
Differential = 2 Degrees
2. Cooling Stage 1 is turned ON at Setpoint plus 1/2 Differential.

Cooling Stage 1 is turned OFF at Setpoint minus 1/2 Differential.
3. Cooling Stage 2 is turned ON at Setpoint plus C2 Offset.

Cooling Stage 2 is turned OFF at Cooling Setpoint.
4. Cooling Stage 3 is turned ON at Setpoint plus C3 Offset.

Cooling Stage 3 is turned OFF at Setpoint plus C2 Offset.
5. Heat Stage 1 is turned ON at Setpoint minus 1/2 Differential.

Heat Stage 1 is turned OFF at Setpoint plus 1/2 Differential.

Heat Stage 2 is turned OFF at Heating Setpoint.

Heat Stage 3 is turned OFF at Setpoint minus H2 Offset.
Figure 11-5. AHU-UC Cooling/Heating Staging

that they were turned on; last on is first off. When the temperature
reaches the active setpoint minus one-half the differential, the first
stage of cooling and the fan are turned off.
Heat Pump (HPMP) Control

Refer to Figure 11-6 for a block diagram of the HPMP function.
Refer to Figure 11-7 for an example of HPMP-UC cooling/heating
staging.
If the space temperature falls below the active heating setpoint, the
reversing valve is turned on. If the space temperature continues to
fall below the active setpoint minus one-half the differential, the
HPMP-UC turns on the fan and the first compressor stage. If there
is more than one compressor stage, the second and third
compressor stages come on after the fan and first compressor stage,
provided their individual temperature offsets and interstage delays
have been honored. If the space temperature continues to fall, up to
three stages of auxiliary heat are staged on, provided their indi-
vidual temperature offsets have been honored.
As the temperature then begins to rise, the compressor stages and
stages of auxiliary heat turn off in the opposite order that they were
turned on; last on is first off. When the temperature reaches the
active setpoint plus one-half the differential, the first compressor
stage and the fan are turned off.
If the space temperature rises above the active cooling setpoint, the
reversing valve is turned off. If the space temperature continues to
rise above the active setpoint plus one-half the differential, the
HPMP-UC turns on the fan and the first compressor stage. If there
is more than one compressor stage, the second and third
compressor stages come on after the fan and first compressor stage,
provided their individual temperature offsets and interstage delays
have been honored. As the temperature then begins to fall, the
compressor stages turn off in the opposite order that they were
turned on; last on is first off. When the temperature reaches the
active setpoint minus one-half the differential, the first compressor
stage and the fan are turned off.

HPMP-UC ATC
Parent Point Extension
Internal DO
SSPP00 ATS
Schedule ***
* Fan Output
External DO
See Note Point
Sensor SSPP00
** External DO
Reversing
Valve Output
See Note Point
Internal DO
Economy See Note
External DO Compressor 1
Override
Option
* I O See Note Output Point
Internal DI
See Note
OR n u
External DO Compressor 2
p t
* u p
Setpoint Adjustment
Potentiometer External AI t u External DO Compressor 3
SSPP03 t See Note Output Point
Option s
s Heat Strip 1
External DO
Override
Pushbutton
External DI
See Note
HPMP-UC
Option
Extension External DO Heat Strip 2
Output Point
See Note
Internal DO
See Note Damper
Indicator External DO Heat Strip 3
Control
Override See Note Output Point
Point
External DO
OR
See Note
Internal DO Internal DO
See Note OR See Note
Mixed Air Mixed Air

Setpoint Constant Sp
DO-PID DO-FLT Sp Setpoint Constant
Extension Extension
External AI External AI
See Note Pv Pv See Note
Outputs
Mixed Air Output Inc Dec

Mixed Air
Pulse Width Modulated External DO Hardware Hardware

Discrete Output Point See Note Output Bit Output Bit
Database
Point Address
Not Required
Note: The only "fixed" or reserved addresses in the AHU-UC are: External AI SSPP00 (Space
Temperature) and External AI SSPP03 (Setpoint Adjustment) when the CSI Model LTS80U
Sensor are used. All other input addresses or output addresses are NOT reserved and can
be used for any external field device up to the maximum point count of the controller.
The AHU-UC Controller only has eight input addresses and eight output addresses
This drawing is intended to show all the functions of the Editor and therefore more than
eight output points are shown. (ONLY EIGHT ARE AVAILABLE)

** Fan Interlock.
*** ATS Schedule required if override pushbutton and/or warmup/cooldown mode are being used.
Figure 11-6. HPMP-UC Editor Block Diagram

C3 ON
78
C2 ON
C3
Offset
C2 C3 OFF
76
C1 ON Offset
REV VALVE
Normal OFF 1/ Diff.
Cooling 74 2
Setpoint 1/ Diff. C2 OFF
2
C1 OFF
72
C1 OFF
Normal
1/ Diff. C2 OFF
Heating 70 2
Setpoint 1/ Diff.
REV VALVE 2 C2
ON Offset
C1 ON C3
68
C3 OFF Offset
C2 ON H1
66
H1 OFF Offset
H2
Offset
C3 ON H3
64
H2 OFF Offset
Interstage Interstage H1 ON H3 OFF

62 Delay Delay
H2 ON
NOTES: 1. Diagram above represents the control actions which would occur if the H3 ON
Cooling Setpoint = 74 Degrees Compressor 2 Offset = 3 Degrees
Differential = 2 Degrees Compressor 3 Offset = 5 Degrees
Heating Setpoint = 70 Degrees Heat Strip 1 Offset = 7 Degrees
Differential = 2 Degrees Heat Strip 2 Offset = 8 Degrees
Heat Strip 3 Offset = 9 Degrees
2. The Reversing Valve is turned OFF when the temperature rises above the Cooling Setpoint.
The Reversing Valve is turned ON when the temperature falls below the Heating Setpoint.
3. In the Cooling Mode, Compressor 1 is turned ON at Cooling Setpoint plus 1/2 Differential.
In the Cooling Mode, Compressor 1 is turned OFF at Cooling Setpoint minus 1/2 Differential.
In the Heating Mode, Compressor 1 is turned ON at Heating Setpoint minus 1/2 Differential.
In the Heating Mode, Compressor 1 is turned OFF at Heating Setpoint plus 1/2 Differential.
4. In the Cooling Mode, Compressor 2 is turned ON at Cooling Setpoint plus C2 Offset.

In the Cooling Mode, Compressor 2 is turned OFF at Cooling Setpoint.
In the Heating Mode, Compressor 2 is turned ON at Heating Setpoint minus C2 Offset.
In the Heating Mode, Compressor 2 is turned OFF at Heating Setpoint.
5. In the Cooling Mode, Compressor 3 is turned ON at Cooling Setpoint plus C3 Offset.

In the Cooling Mode, Compressor 3 is turned OFF at Cooling Setpoint plus C2 Offset.
In the Heating Mode, Compressor 3 is turned ON at Heating Setpoint minus C3 Offset.
In the Heating Mode, Compressor 3 is turned OFF at Heating Setpoint minus C2 Offset.
6. In the Heating Mode, Heat Strip 1 is turned ON at Heating Setpoint minus H1 Offset.
In the Heating Mode, Heat Strip 1 is turned OFF at Heating Setpoint minus C3 Offset.
In the Heating Mode, Heat Strip 2 is turned OFF at Heating Setpoint minus H1 Offset.
In the Heating Mode, Heat Strip 3 is turned OFF at Heating Setpoint minus H2 Offset.
Figure 11-7. HPMP-UC Cooling/Heating Staging

AHU and HPMP Damper Control

Typically a DO-PID extension controls the AHU or Heat Pump
OA/RA Mixing Damper actuator. This extension continually
compares the actual AHU Mixed Air temperature (external AI
point address) to the desired Mixed Air temperature setpoint
(operator defined constant) and modulates the AHU or Heat
Pump Mixing Dampers using Pulse Width Modulation to maintain
the desired Mixed Air Temperature.
It may be necessary to close the AHU or heat pumps OA/RA
Mixing Dampers when the AHU or heat pump is shut down. Estab-
lish this interlock by entering the damper DO-PID parent point
address in the appropriate UC editor as the damper control param-
eter. This entry interlocks the DO-PID parent point address with
the UC parent point address such that, when the UC parent point
is commanded off (0) by the time scheduling extension, the DO-
PID damper parent point address is also commanded off (0). This
drops the output of the DO-PID extension to zero percent (closed).
When the AHU or heat pump parent point is commanded on (1),
the DO-PID damper extension is also commanded on (1), enabling
the AHU or heat pumps mixing dampers to be modulated to
maintain the mixed air temperature.
Note that a DO-FLT extension could be used in place of a DO-PID
extension if a pair of bidirectional pulsed outputs is required to
drive the AHU or heat pump OA/RA mixing dampers rather than
using Pulse Width Modulation. To make sure the mixing damper
closes, the DO-FLT extension will pulse its Decrease hardware
output for a duration equal to twice the programmed Throttling
Range when the DO-FLT parent point is commanded off (0); i.e.,
if the DO-FLT extension had a value of 90 seconds entered as its
Throttling Range, a Decrease pulse equal to 180 seconds is issued
to close the mixing damper actuator when the AHU or heat pump
parent point is commanded off (0).

Other Control Features

Remote Setpoint Adjustment
You may wish to have the NORMAL, SETUP/SETBACK or
ECONOMY setpoints remotely adjustable. An external AI point in
the UC database must be defined and a potentiometer must be
installed and wired to the unitary controller. If the potentiometer
being used is an integral part of a CSI Lini-Temp LTS80UX Space
Sensor, it will be at address SSPP03.
You must define the conversion coefficients for the external AI
point. The range of this AI point must be set up to vary between
1.0 to +1.0. The Analog-to-Digital (A/D) convertor in the UC is
an 8-bit convertor with a maximum of 255 counts. This A/D
convertor is calibrated between 2.732 VDC (0 counts) to 3.332
VDC (255 counts).
If the setpoint adjustment potentiometer on the sensor is turned
completely counterclockwise (cooler), the value of the external AI
point becomes 2.892 VDC. This results in an output of 68 counts
from the A/D convertor. If the setpoint adjustment potentiometer
on the sensor is turned completely clockwise (warmer), the value
of the external AI point becomes 3.174 VDC. This results in a
change of 188 counts from the A/D convertor.
Knowing this, the conversion coefficients are calculated as follows:
Basic Equation: y = m(x) + b

Fully Counterclockwise: 1 = m(68) + b
Fully Clockwise: +1 = m(188) + b
Therefore; b = 1 (68)m
Plug into 2nd Equation: 1 = 188m + (1 68m)
Solving for m: 2 = 120m
m = 2/120 = 0.016666
Solving for b: b = 1 68(0.016666)
b = 1 1.13333 = 2.13333

To make sure the setpoint adjustment potentiometer is calibrated

properly, the coefficients calculated above should be entered for the
external AI point in the UC database and the potentiometer should
be placed to its mid-scale position. The value indicated on the
HHC or host workstation should then read zero.
To zero-out the potentiometer, determine the difference (either
positive or negative) between the actual AI reading and the
midscale (zero) position. Divide this error by the m value calcu-
lated above to determine the number of counts the error repre-
sents. Then enter this number into the AI point editor as the value
for the offset parameter.
Note: If the error in reading is negative, the offset counts entered should be
positive. If the error in reading is positive, negative offset counts
should be entered.
Once the external AI point used for remote setpoint adjustment is

set up properly, you must determine the desired temperature
adjustment range. Enter this range into the appropriate UC exten-
sion editor in degrees. This range is used as a multiplier with the
setpoint adjustment AI point to determine the actual value to be
added to or subtracted from the current Normal, Setup/Setback, or
Economy setpoints.
For example, assume the UC is currently honoring a Setup setpoint
of 82 degrees. Also assume the setpoint adjustment AI point is
correctly defined over the range of 1.0 to +1.0 and the adjustment
range entered is five degrees. With this range defined, each division
on the cover of the sensor assembly represents one degree. If a
tenant adjusts the setpoint adjustment potentiometer fully coun-
terclockwise (cooler) so that the value of the external AI point is
1.0, the new UC Setup setpoint is:
82 degrees + (1.0 5 degrees) = 82 5 = 77 degrees
Remote Override
You may wish to allow a tenant who wants heating or cooling after
normal operating hours to turn on his individual VAV, AHU, or
heat pump. To do this you must install a normally open momen-
tary (or maintained) push-button in the area served by the VAV

box, AHU, or heat pump. The push-button can be an integral part

of the CSI Lini-Temp LTS80U Space Sensor and can be wired to any
of the eight input points of the controller.
To convert this momentary contact input to a desired duration of
equipment operation (60 minutes, 120 minutes, etc.), an interme-
diate controller DO address called Override Indicator must be
used. You must also define the desired duration of after-hours
operation (in minutes) in the appropriate UC extension editor.
You must append a time scheduling extension to the UC parent
point. This schedule must define the period of occupancy.
If the push-button is momentarily pressed during time schedule-
defined unoccupied hours, the associated UC DO override indi-
cator point address is commanded ON (1). It will latch-up, and
remain ON until the specified duration time expires. At this time,
the override indicator DO address returns to its OFF (0) state.
Anytime the override indicator point is ON, the UC switches to its
Normal setpoints. When the indicator point returns to OFF, the
UC returns to its Setback/Setup setpoints. If the override push-
button is pressed and subsequently the indicator point is
commanded ON during occupied hours, the UC is already
honoring its Normal setpoints and therefore no switching of
setpoints occurs.
At times, it may be necessary to have the UC switch to its normal
setpoints when the override push-button is pressed, as well as
perform the following other control action (depending on the type
of UC):
Command the AHU serving the VAV box on.
Command the chiller or boiler in the central plant serving the
AHU on.
Command a loop water pump in the central plant serving the
heat pump on.
Any of these actions can be accomplished by defining the override
indicator DO address as indirect in the UCI-resident database
editor. When commanded ON, a message is broadcast onto the
controller LAN, received as a global point in another controller that
performs the actual additional commands.

Conversion of Velocity Pressure to CFM (VAV only)

Select the resident I/O points editor while connected to a 7760 UCI.
Add an AI point. You will notice an additional parameter, Non-
Linear Lookup Table. Enter a 0, 1, 2, or 3.
Note: Only two lookup tables (1 and 2) have been implemented. Lookup
Table #3 is for future use.
An entry of 0 signifies that a Non-Linear Lookup Table is not being

used and the VAV-UC AI point is processed like any standard AI
point in a controller: counts from the A/D convertor are used in the
selected conversion equation with the selected conversion coeffi-
cients to calculate the displayed value for the AI point.
Entering 1 or 2 causes the VAV-UC to take the counts from the A/D
convertor for a particular AI point and match it to a velocity pres-
sure in the desired lookup table before it is used in a conversion
equation with a given set of conversion coefficients. See
Figure 11-8.
Pickup
Fan Probes
Damper
Duct
UC UC/UCI UC/UCI
Low Velocity A/D Non-Linear Conversion
Voltage Counts Eng. Units CFM Point
High Pressure Converter Look-Up Coefficients
Transducer 2.7323.332 (8-Bit) (0 255) Table (0 13000) Value
y=m x+b
VAV-UC
(Model 7211/7212)
2.7623.332
VAV-UCII
(Model 7261/7262)
y=m x+b
Whe re y = CFM
Whe re x = Equipment units from non-linear look-up table
square footage of duct
m = K factor
100
b=0
Where "square footage of duct" = Length Width (Box)
or
R adius2 (Circle)
K factor =VAV box airflow constant
Figure 11-8. Velocity Pressure to CFM Conversion Process

This is done to more accurately match the non-linear velocity pres-

sure signals that are common when trying to sense airflow. The
actual numbers stored in both lookup tables are equal to the
velocity pressure multiplied by 10,000.
Non-Linear Lookup Table number 1 is incorporated for use with
the Hoffman velocity pressure transducer (CSI part numbers
603500-0002 (transducer/ actuator assembly) and 603500-0003
(transducer only)). This transducer is for use only with the VAV-
UC (Model 7211/7212) controller. Non-Linear Lookup Table
number 2 is incorporated for use with the AutoTran velocity pres-
sure transducer (CSI part number 605540-0002) that is optionally
provided on the VAV-UC II (Model 7261/7762) controller. This
second lookup table translates the output of the AutoTran trans-
ducer to produce an offset-compensated value of zero when the
velocity pressure drops below 0.02" (actual value = 0.0174) of water
column.
Since we are trying to control the VAV box airflow in CFM, this AI
point must be stored in CFM. The basic equation used to calculate
CFM from velocity pressure (sensor input) is:
CFM (airflow) = velocity pressure airflow constant duct sq. ft.
Therefore, you must use the flow conversion equation

y = m x + b when populating the CFM AI point address in the
Resident Points I/O editor. The x in the flow equation is repre-
sented by the velocity pressure value from the Analog Input after it
has passed through the appropriate lookup table. The m in the
equation is represented by the airflow constant multiplied by the
duct area in square feet or:
airflow constant duct sq. ft.
m = --------------------------------------------------------------------
100
and the y-intercept (b) is 0.
The airflow constants for various CFM pickup rings/probes vary
according to the type and manufacturer. We divide the slope calcu-
lation (m) by 100 to compensate for the fact that the numbers
stored in the Non-Linear Lookup Table have been multiplied by
10,000 (the square root of 10,000 is 100).

For example, assume you wish to sense CFM using a Titus Velocity
Pressure Probe and Hoffman Velocity Pressure transducer in an 8-
inch round duct. In the VAV-UC resident database editor, you must
use the flow equation described above and Non-Linear Lookup
Table number 1. The conversion coefficients are:
b=0
m = (2304 0.3490)/100 = 8.04096
where 2304 equals the Titus Airflow Constant and 0.3490 equals
the duct square footage calculated as follows:
duct square footage = R2
(where R = radius of duct in feet)
duct square footage = 3.1415 0.3332
duct square footage = 0.3490
Note: The velocity pressure pickup ring/probe constant is typically provided

by VAV box manufactures.
Lini-Temp Temperature Sensors

The output range of the CSI Lini-Temp Sensor used with the
Unitary Controller is 2.732 VDC at 32F to 3.332 VDC at 140F.
This is the same Lini-Temp Sensor used with all other DCUs. The
A/D convertor in the Unitary Controller is an 8-bit convertor, cali-
brated to output 0 counts at 2.732 VDC and 255 counts at 3.332
VDC. When used with a UC, the conversion coefficients for this
space temperature sensor are:
Basic Equation: y = m(x) + b

At 32F.: 32 = m(0) + b
At 140F.: 140 = m(255) + b
Solving for b: b = 32
Solving for m: 140 32 = 255m
m = 108/255 = 0.423529

Warmup/Cooldown (AHU and HPMP only)

It may be necessary for the mixing dampers to be in the fully closed
position (0% Outside Air and 100% Return Air) for a predeter-
mined time period after the AHU or heat pump is commanded on
in the morning by its time scheduling extension. Enter a value
between 0 and 254 (minutes) in the appropriate controller data
entry screen in the Warmup/Cooldown field.
You must append a time scheduling extension to the UC parent
point. This schedule must define the period of occupancy (e.g.,
STRT at 08:00 and STOP at 17:00).
The AHU-UC or HPMP-UC editor ensures the mixing dampers
remain fully closed during morning start-up (the warmup/
cooldown time period). This keeps the AHU outside air dampers
fully closed and the return air dampers fully open, allowing the
space temperature to warm up or cool down as desired. At the end
of the specified warmup/cooldown period, the mixing dampers are
then allowed to open or close as necessary to maintain the desired
mixed air temperature setpoint.
Interlocks
Heating/Cooling Interlock
An interlock exists to ensure that any of the UC types cannot be in
both the heating and cooling modes at the same time.
In the VAV-UC, this interlock is applied to the point identified in
the VAV editor as the temperature setpoint entry. This address
should be the address of the AO-PID extension, and will become
inoperative if the damper override entry is the same address. This
interlock will be disabled if a central plant heat DI or DO point has
been populated in the VAV-UC editor and this DI/DO is equal to a
1.
Note: The editor will allow either the AO-PID address or the AO-FLT
address to be used as the target for the heating/cooling interlock or the
damper override. Insure that the heating/cooling interlock is applied
to the AO-PID address and the damper override is applied to the AO-
FLT address.

Fan/Heat Interlock (VAV only)

An interlock exists to ensure that all stages of heat (13) are
commanded to off if the fan is off. Even though it has been added
primarily for safety purposes, the fan/heat interlock makes
programming for other shutdowns easier to implement. For
example, you can create an event sequence in any controller
including the UCI, which issues a Stop with Lock command to
the VAV-UC fan output point. By controlling just the fan, all stages
of heat would also be controlled off.
Fan/Heat/Cool Interlock (AHU and HPMP only)
An interlock exists to ensure that all stages of heat (13) and
cooling (13) are commanded off if the fan is off. Even though it
been added primarily for safety purposes, it makes programming
for other shutdowns easier to implement. For example, you can
create an event sequence in any controller including the UCI which
issues a Stop with Lock command to the AHU or HPMP fan
output point. By controlling just the fan, all stages of heat or
cooling would also be controlled off.
PID/FLT Extension Failsafe
The PID and the FLT DDC extensions contain fail-safe logic that
causes the output of the extension to behave in a predictable
manner clamping the output to its low or high limit value.
If the analog input (process variable) exceeds the extension high or
low input limits, the extension continues to vary its output.
However, if the analog input (process variable) exceeds its sensor
high or low limits, as established in the resident I/O editor for the
AI point, the extension output is forced to its control point value as
established in the extension editor. For the FLT extension, the result
is that no output pulses are generated.
If the setpoint input exceeds the extension high or low input limits
(only on AO-PID or AO-FLT), the extension output is forced to its
control point value as established in the extension editor. Again, for
the FLT extension, the result is that no output pulses are generated.

Creating the UC/UCI Database Unitary Control
Creating the UC/UCI Database

Database entries for each UC are made by connecting to a UCI and
then entering the resident I/O points editor.
See the Chapter 6, Input and Output Points and Chapter 7, Point
Extensions for a detailed description of database parameters and
the mechanics of database entry.
The UCI and UCs use bit offset (BB) addresses for hardware output
points. This makes it possible for all eight input and output points
(00-07) to reside at the same point (PP) address and allows a UCI
with 32 UCs to occupy only one station (SS) address. Remember
that a point address is in the form LLSSPPBB (link, station, point,
and bit offset).
Note: Bit offset addresses 08 and 09 can only be used as internal or indirect
points on a UC defined with a type of Internal. These addresses
cannot be used when a UC type is defined as VAV, AHU, HPMP, or
General. If you are using the UC to UC copy function, bit offset
points 08 and 09 must not exist in the source UC during the copy
process. You may add bit offset points 08 and 09 (in an internal UC
through the resident I/O points editor after using the UC copy editor.
DDC modules are not available for use in UCs. However, you can
set up PID or Floating control in any of the unitary controllers.
This topic is described in detail later in this chapter.
Caution: When setting up any of the Unitary Controllers, it is vital that the
UC Parent Point (internal or external DO) use the following control
command pair:
STRT 1
STOP 0
Failure to observe this convention results in erratic and unpredictable

UC operation.

Unitary Control Unitary Control Parameters
Figures 11-1 (page 11-9) and 11-2 (page 11-10) show block
diagrams of typical VAV-UC editor setup. Figure 11-4 (page 11-14)
shows a block diagram of a typical AHU-UC editor setup.
Figure 11-6 (page 11-17) shows a block diagram of a typical
HPMP-UC Editor setup.
Unitary Control Parameters

Once you have defined several UC resident points in the resident
I/O points editor, you can append UC extensions to parent points.
If you select an AO point, you can only append PID and FLT exten-
sions. These are described later in this chapter. If you select a DO
point, you can append VAV, AHU, PID, FLT, and HPMP extensions.
The VAV, AHU, and HPMP extensions are described here:
The Variable Air Volume (VAV-UC) provides economical
distributed control of single- and double-duct (constant or
variable) VAV boxes. With the exception of the PWM or
Floating output used to drive the VAV box damper(s), all
other outputs are typically discrete in nature. The VAV-UC
also contains differential pressure transducer(s) for sensing
CFM airflow.
The Air Handling Unit Unitary Controller (AHU-UC)
provides economical distributed control for packaged roof-
top and small built-up air handling units. With the exception
of the Pulse Width Modulated output typically used to drive
mixing dampers, all other outputs are discrete in nature,
providing open or closed contacts to field devices.
The Heat Pump Unitary Controller (HPMP-UC) provides
economical distributed control for packaged heat pump
installations. With the exception of the Pulse Width Modu-
lated output typically used to drive mixing dampers, all other
outputs are discrete in nature, providing open or closed
contacts to field devices.
The following pages discuss the parameters for the VAV, AHU, and
HPMP controller types. Some of the parameters are common to all
extension types and some are specific to a particular UC extension.
If this is the case, this information is posted beside the parameter

Unitary Control Parameters Unitary Control
description in this document. For example, the parameter

Damper Override has the words VAV only posted beside it.
This indicates that the parameter is specifically for the VAV exten-
sion.
Setpoints
Each setpoint consists of a number between 0 and 127.5 for the
setpoint target and a number between 0 and 10 for the differential.
You may use a 0.5 decimal entry for all setpoint targets and differ-
entials. If you enter a decimal value less than 0.5, the system drops
the decimal (e.g., 79.4 becomes 79). If you enter a decimal value
greater than 0.5, the system replaces the decimal with 0.5 (e.g., 79.9
becomes 79.5).
Cooling Setup
This setpoint limits the high temperature in the space conditioned
by the unit controlled by this UC when the space is unoccupied
(DO parent point is off; equal to 0). If the sensed temperature
exceeds the setpoint plus one-half the differential during this time,
the UC starts the fan and executes the control necessary to cool the
space.
Cooling Economy
Use this setpoint in conjunction with a DI/DO point (economy
override); e.g., an external personnel sensor or internal point
controlled by demand control, to raise the setpoint if the space is
unoccupied during normal hours (DO parent point is on; equal to
1 and economy override equal to 1). Occupancy is determined
through use of the economy override function described below.
When the personnel sensor again senses occupancy (economy
override=0) or demand control restores the economy override
point, the setpoint reverts to normal cooling setpoint.
Cooling Normal
This setpoint is used when the unit is on (parent point = 1) and the
sensed space temperature is higher than the setpoint plus one-half
the differential.

Heating Normal
This setpoint is used when the DO parent point is on (equal to 1)
and the sensed space temperature is lower than the setpoint minus
one-half the differential.
Heating Economy
This setpoint may be used with a DI/DO point (economy over-
ride); e.g, an external personnel sensor, or internal point controlled
by demand control, to lower the setpoint if the space is unoccupied
during normal hours (DO parent point is off; equal to 0 and
economy override equal to 1). Occupancy is determined by the
economy override function, described below. When the personnel
sensor again senses occupancy, or demand control restores the
economy override point, the setpoint reverts to normal heating
setpoint.
Heating Setback
This setpoint limits the low temperature in the space conditioned
by the unit controlled by this UC when the space is unoccupied
(DO parent point is off; equal to 0). If the sensed temperature
drops below the setpoint less one-half the differential during this
time, the UC starts the fan and executes the control necessary to
heat the space.
Note: If any of the above setpoints are not used, do not change the default
setpoint and differential. Ensure that the heating setpoint plus differ-
ential does not overlap the cooling setpoint plus differential, or be
higher than the cooling setpoint. The reverse is true of the cooling
setpoint.
Only one of six setpoints above is ever in effect at any time
(depending on current time and space temperature values).
The changeover from cooling setpoint to heating setpoint occurs when
the space temperature drops below the heating setpoint plus half the
differential. The setpoint changes to the cooling setpoint when the
space temperature rises above the cooling setpoint plus half the differ-
ential.

Overrides
There are several separate override options available in the UC type
you selected.
Setpoint Adjustment
This parameter is a point address or name. When a CSI space
temperature sensor with a setpoint adjustment knob, or a CSI
space temperature sensor with a setpoint adjustment knob and an
override push-button is used, enter the default AI address
(LLSSPP03) here. Refer to Remote Setpoint Adjustment on page
11-20 for the setup of this point.
Range
This parameter is a number between 0 and 10. When a CSI sensor
with a setpoint adjustment knob is used, the value entered here
limits the setpoint adjustment to plus or minus the value entered.
If you enter a five, the full rotation of the knob will never change
the setpoint by more than ten degrees (five degrees up or down).
Refer to Remote Setpoint Adjustment on page 11-20 for the use
of this editor entry.
Timed Override
This parameter is a point address or name. When a CSI space
temperature sensor with setpoint adjustment and override push-
button is used, the push-button can be hardwired back to any avail-
able DI input point. The UC senses the activation of this DI point
(open to close, 0 to 1) and initiates a timed override for the dura-
tion you define. You may also use a maintained contact closure
device or a spring wound timer instead of a pushbutton.
Note: The override period is initiated when the spring-wound timer contact
first closes. The duration of the override honors the timed override
editor entry regardless of the external timer duration.
The timed override function is only operative during unoccupied
hours, i.e., when the UC parent point has been turned off (0) by an
ATS schedule. An ATS schedule on the parent point is required to
allow the timed override to work properly.

Timed Override Indicator

This parameter is a point address or name. The timed override
indicator is a DO point (internal or external) energized when the
DI push-button (timed override) point is pressed. If you wish to
turn on a light when this function is activated, the point address,
typically LLSSPP02 DO (external), can be used. This indicator
point remains energized for the entire timed override duration
time. When energized, the UC DO parent point is also turned on
and the UC switches to its normal or economy setpoints. When de-
energized, the UC DO parent point turns off and the UC returns to
its unoccupied setpoints.
Timed Override Duration
This parameter is a number between 0 and 254. This is the number
of minutes the UC energizes the timed override indicator (and
parent point) after the timed override push-button is pressed (i.e.,
the UC continues to honor the normal setpoint for the specified
duration). Cancel the override by activating the timed override DI
input point (i.e., pushbutton) a second time.
Economy Override
This parameter is a point name or address. This function can be
used in two ways.
Use it as an input from a personnel sensor to determine if the
space is occupied during the time the UC parent point is on
(1). If you select this option, wire the personnel sensor to an
input point, typically LLSSPP05 DI (external), and enter that
address here. When the UC observes the value of the point as
1 (space is unoccupied) and the parent point is ON (1), it
switches the setpoint from normal to economy. When a
person re-enters the space, the personnel sensor detects them,
opens its auxiliary contact, outputs a 0 to the UC, and the UC
reverts to the normal heating or cooling setpoint.
Note: You must observe the polarity of this point! A 1 always causes the UC
to switch to the economy setpoint when the parent point is ON (1).

You may also use the economy override function to shift the
setpoint in response to a Demand Program shed command. If
you select this option you might use LLSSPP01 DO (internal),
as the demand load address. The response is the same as that
described for the personnel sensor. Once again you must
observe the polarity. A control command of 1 must be issued
to the internal DO point to cause the UC to shift from normal
to economy setpoints.
Damper Override (VAV only)
This parameter is a point name or AO point address (typically
address SSPP07 AO). Use the damper override function if you want
to have the VAV airflow control damper travel to its fully closed (0)
position when the VAV parent point is off (0) and the space temper-
ature is within the setup/setback targets.
Note: To use this function, the low limit of the AO point designated as the
floating parent point (typically SSPP07 AO) must be 0 and the input
low limit of the AO-floating extension must be 0. Refer to Figures
11-1 (page 11-9) and 11-2 (page 11-10).
Warmup/Cooldown (AHU, HPMP only)

of minutes after morning start-up (AHU or HPMP parent point
controlled from OFF (0) to ON (1) by an ATS schedule) during
which the damper control output is held at its closed (0) position
to facilitate morning warmup or cooldown. When this time period
expires, the AHU-UC or HPMP-UC starts the damper control
output point (1). This lets the dampers begin to maintain mixed air
temperature setpoints.
Note: This feature only works when the AHU-UC or HPMP-UC parent
point is commanded on (1) by the time scheduling program, not
when the fan output point turns on and off as a result of automatic
fan control by the AHU-UC or HPMP-UC.
Inputs and Outputs

The input and output parameters you define instruct the UC where
to find the information it needs to function.

Space Temperature
This parameter is the hardware address of the space temperature
sensor. If you are using a CSI LTS80U space sensor, enter the default
address LLSSPP00 AI (external). You may use another address if
you use another sensor. To use one sensor to control several UCs
you must make a calculation, in the appropriate UCI, and reflect
the value of the common sensor to each UC with the appropriate
point (PP) address for each UC.
Central Plant Heat (VAV only)
The VAV-UC can change its control response from direct acting to
reverse acting if the central air supply system is subject to seasonal
supply air temperature changeover. This means that during the
cooling season, the supply air system carries cool air, and during
the heating season, the supply air system carries warm air. The UC
must change from direct acting to reverse acting; i.e., it must open
its air supply damper on a call for heating and close it when the
space is overheated. To accomplish this, it must know when the
supply air has changed from cool to warm. This changeover notifi-
cation is accomplished by using a DI or DO point at the address
named Central Plant Heat. When this point state is 1, the AO-PID
attached to LLSS06 AO (refer to Figure 11-1 on page 11-9) switches
to reverse acting. When the state is 0 (or is not populated in the
VAV extension editor), the AO-PID extension functions as direct
acting.
Temperature Setpoint (VAV only)
This parameter is an AO PID or Floating parent point assigned as
the space temperature setpoint. To reset the CFM (cubic feet per
minute) setpoint by the temperature error, enter the AO PID
parent point address (e.g., LLSSPP06 AO; see Figure 11-1 on page
11-9). If you wish to bypass the CFM control and control the
damper position directly from the temperature error, enter the AO
Floating parent point address (e.g., LLSSPP07 AO; see Figure 11-2
on page 11-10).
Fan
This is the external DO point address that controls the fan
(LLSSPP05 DO).

Note: A DC point with an associated DM point cannot be used as a fan

point in a UC. Only a DO point may be used.
Cooling Fan Control (VAV only)

Select On, Off, or Auto to determine the operation of the fan in the
cooling mode (space temperature above the active cooling
setpoint). If you select Auto, the fan turns on when the space
temperature reaches the active cooling setpoint plus one-half the
differential. The fan turns off when the space temperature reaches
active cooling setpoint minus one-half the differential. If you select
On or Off, this causes the fan to be constantly on or off in the
cooling mode.
Heating Fan Control (VAV only)
Select On, Off, or Auto to determine the operation of the fan in the
heating mode (space temperature below the active heating
setpoint). The fan runs according to the same criteria described
above for the cooling fan control.
Stage 1 Heating (VAV and AHU only)
This parameter is the point address for the Stage 1 heat output.
This address is typically LLSSPP04 DO (external). The first heating
stage is activated when the space temperature falls below the active
heating setpoint minus one-half the differential. Stage 1 heat turns
off when the temperature climbs above the active setpoint plus
one-half the differential. See Figures 11-3 (page 11-11) and 11-5
(page 11-15).
Activation Delay (VAV only)
of seconds between the start of the fan and the activation of the first
heat stage or the deactivation of the first heat stage and the stop of
the fan.
This parameter is the point address for the Stage 2 heat output, if
one is used. This address is typically LLSSPP03 DO (external). See
Figures 11-3 (page 11-11) and 11-5 (page 11-15).

Stage 2 Heating Setpoint Offset (VAV and AHU only)

This parameter is a number between 1 and 10 degrees which
defines the temperature offset below the current heating setpoint at
which you want Stage 2 heating to turn on. Stage 2 heat turns off
when the space temperature returns to the active heating setpoint.
See Figures 11-3 (page 11-11) and 11-5 (page 11-15).
This parameter is the point address for the Stage 3 heat output, if
one is used. This address is typically LLSSPP02 DO (external). See
Stage 3 Heating Setpoint Offset (VAV and AHU only)
This parameter is a number between 1 and 10 degrees which
defines the temperature offset below the current heating setpoint at
which you want Stage 3 heating to turn on. Stage 3 heat turns off
when the space temperature returns to the heating setpoint minus
the Stage 2 heating setpoint offset. This setpoint offset is not added
to the Stage 2 setpoint offset, so make sure this number is greater
than the number you defined for the Stage 2 setpoint offset. See
Fan Control (AHU and HPMP only)
Select On if you want the fan to run continuously during occupied
hours (when parent DO = 1) or Auto if you want the fan to cycle
on and off as the temperature rises and falls across the active
setpoint when the space is occupied.
Stage 1 Cooling (AHU only)
This parameter is the external DO point address for the Stage 1
cooling. The first cooling stage is activated when the sensed
temperature is greater than the active cooling setpoint plus one-
half the differential. See Figure 11-5 on page 11-15.
Interstage Delay (AHU and HPMP only)
of seconds that a cooling stage (AHU) or compressor (HPMP)
must be activated before the next stage/compressor can turn on.
See Figures 11-5 (page 11-15) and 11-7 (page 11-18).


cooling, if applicable. The second stage is activated when the sensed
temperature is greater than the cooling setpoint plus the Stage 2
setpoint offset. Stage 2 cooling is turned off when temperature falls
below the active cooling setpoint. See Figure 11-5 on page 11-15.
Stage 2 Cooling Setpoint Offset (AHU only)
This parameter is a number between 1 and 10. This is the temper-
ature offset above the current setpoint at which you want Stage 2
cooling to turn on. See Figure 11-5 on page 11-15.
cooling, if applicable. The third stage is activated when the sensed
temperature is greater than the cooling setpoint plus the Stage 3
setpoint offset. Stage 3 cooling is turned off when the temperature
falls below the active cooling setpoint plus the Stage 2 cooling
offset. See Figure 11-5 on page 11-15.
Stage 3 Cooling Setpoint Offset (AHU only)
This parameter is a number between 1 and 10 that, when added to
the current setpoint, is the temperature at which the third cooling
stage is activated. This setpoint offset is not added to the Stage 2
setpoint offset, so make sure this number is greater than the
number you defined for the Stage 2 cooling setpoint offset. See
Figure 11-5 on page 11-15.
Reversing Valve (HPMP only)
This parameter is the external DO address of the point controlling
the reversing valve. Heat Pumps operate on a reverse cycle principal
so we must be able to reverse the flow of refrigerant when heating
becomes necessary. The UC switches the position of the valve as the
sensed temperature crosses the opposite heating or cooling
setpoint. The valve is energized in the heating mode and de-ener-
gized in the cooling mode. If, for example, the normal heating
setpoint is 72 and the normal cooling setpoint is 75, the reversing
valve switches from heating to cooling (energized to de-energized)
when the space temperature rises above 75 degrees.

If the space temperature drops, the reversing valve switches from

cooling to heating (de-energized to energized) when the space
temperature falls below 72 degrees. See Figure 11-7 on page 11-18.
Compressor #1 (HPMP only)
This parameter is the external DO address of the hardware point
controlling the heat pumps first stage compressor (used for cooling
and heating). In cooling mode, this point turns on when the space
temperature exceeds the appropriate cooling setpoint plus one-half
the differential. In heating mode, this point turns on when the
space temperature is lower than the appropriate heating setpoint
minus one-half the differential. See Figure 11-7.
This parameter is the EXT DO address of the hardware point
controlling the heat pumps second stage compressor (used for
heating and cooling), if applicable. Compressor #2 is staged on
when the sensed temperature is greater than the active cooling
setpoint plus the Stage 2 offset, or when the sensed temperature is
less than the active heating setpoint minus the Stage 2 offset.
Compressor #2 is staged off when the sensed temperature reaches
the active heating or cooling setpoint. See Figure 11-7 on page
11-18.
Compressor #2 Setpoint Offset (HPMP only)
This parameter is the number of degrees from 0 to 10 (above or
below the active setpoint) that must fall/rise before the second stage
compressor is turned on.
controlling the third stage compressor (used for heating and
cooling), if applicable. Compressor #3 is staged on when the sensed
temperature is greater than the active cooling setpoint plus the
Stage #3 offset, or when the sensed temperature is less than the
active heating setpoint minus the Stage #3 offset. Compressor #3 is
staged off when the sensed temperature falls below the active
cooling setpoint plus the stage #2 offset or when the sensed temper-
ature rises above the active heating setpoint minus the Stage #2
offset. See Figure 11-7 on page 11-18.

Compressor #3 Setpoint Offset (HPMP only)

This parameter is the number of degrees from 0 to 10 (above or
below the active setpoint) that must fall/rise before the third stage
compressor is turned on. This setpoint offset is not added to the
Stage 2 setpoint offset, so make sure this number is greater than the
number you defined for the Stage 2 setpoint offset. See Figure 11-7
on page 11-18.
Heater Strip #1 (HPMP only)
controlling the heat pumps first stage of auxiliary heat, if appli-
cable. The first heater strip turns on only after its setpoint offset is
exceeded.
Heater Strip #1 Setpoint Offset (HPMP only)
This parameter is the number of degrees (from 1 to 10) below the
active heating setpoint the temperature must fall before the first
stage of auxiliary heating can turn on. Make sure this offset is
greater than compressor #1, #2, or #3 offset values. See Figure 11-7
on page 11-18.
controlling the heat pumps second stage of auxiliary heat, if appli-
cable.
active heating setpoint the temperature must fall before the heat
pumps second stage of auxiliary heating is turned on. Make sure
this offset is greater than compressor #1, #2, or #3 offset values, and
Heater Strip #1 setpoint offset. See Figure 11-7 on page 11-18.
controlling the heat pumps third stage of auxiliary heat, if appli-
cable.


active heating setpoint the temperature must fall before the third
stage of auxiliary heating is turned on. Make sure this offset is
greater than compressor #1, #2, or #3 offset values, and heater strip
#1 and #2 setpoint offsets. See Figure 11-7 on page 11-18.
Damper Control (AHU and HPMP only)
This parameter is the point name or point address of the DO point
with either a DO PID or DO FLT extension added to it. The damper
control is enabled by the state of the parent point which is depen-
dent on the command issued to it by the time scheduling program.
This control function is discussed in UC Damper/Valve Control
on page 11-7.
Use the damper control function if you want to have the
AHU/HPMP airflow mixing dampers remain in their fully closed
(0) position for a preset time duration after the AHU/HPMP
parent point is has been commanded ON by its ATS schedule.
PID Parameters
The PID parameters described below are used on DO PID and AO
PID extensions:
Setpoint (DO-PID only)
This parameter is a value in degrees. This is the target temperature
to be maintained by the extension. This value is a constant.
Input (Process Variable)
The AI address of the sensor measuring the process. This is typi-
cally a duct/space/fluid temperature sensor.
Input Filter
This parameter is a number between 0 and 5. This option lets you
average up to five previous sequential input samples with the
current sample to reduce the impact of rapidly changing input
values. An entry of zero means filtering is not being used.

Input Low Limit

This parameter is a value below which the extension declares the
setpoint no longer valid. At this value, the output from the PID
extension will be driven to its control point value.
Input High Limit
This parameter is a value above which the extension declares the
setpoint no longer valid. At this value, the output from the PID
extension will be driven to its control point value.
Output
This parameter is the name or address of a previously defined
external AO point that provides the pulse width modulated output
to the pneumatic, current, or voltage transducer. Refer to UC
Damper/Valve Control on page 11-7 for details. At this point you
have completed the input and output entries and need only fill in
the output high and low limits along with characterizing the PID
module to complete the extension.
Output Control Point
is 50 percent. This is the fail-safe value for the output, the percent
of the output range (output high limit output low limit) which
the module will output during a fail-safe condition. This
percentage is output under three conditions:
The setpoint of the PID is outside the limits assigned in the
high and low input limit parameters defined above.
The input (process variable) exceeds its sensor high or low
limits (defined in the resident I/O points editor).
This is the initialized position that is output when escaping
to exit the PID editor.
Output Ramp Limit
is 100 percent. This defines the magnitude of the largest change in
output you want the PID to issue between samples. Defining this
parameter as less than 100 percent helps protect equipment from
wide swings in output values.

Output Low Limit

This parameter is a number used to define the minimum output
value of the PID extension.
Output High Limit
This parameter is a number used to define the maximum output
value of the PID extension.
Proportional Band
This parameter is a number between 0 and 1,000. This is the
percent of the input range (input high limit input low limit) that
the input value must change in order to drive the output percent
from 0 to 100.
Reset Interval
This parameter is a number between 0 and 3,600 seconds. The
default is zero seconds. Use this function to eliminate a persistent
error (called offset) that has remained constant from one PID
sample to another. Without reset, this situation (offset) results in
undesirable static module output. This function defines reset
calculation constants used to modify the output of the PID exten-
sion.
Rate Interval
default is zero seconds. This is the time between calculations of the
rate portion of the PID algorithm. Use this function to account for
large input changes by comparing the direction and magnitude of
the error between samples and correcting the output accordingly.
Mode
Select Direct or Reverse. The default is Direct. This parameter
defines the response of the PID extension. If you choose direct
acting, the PID output increases as the process variable rises (error
increases). This function must be used to fit the response of the PID
extension to the end device controlling the process. If set to
Reverse, the PID output decreases as the process variable rises.

The mode you select determines what happens when the input rises
higher or falls lower than the setpoint. Direct acting PID extensions
increase their output if the input (process variable) rises above the
module setpoint and decrease their output if the input (process
variable) falls below the setpoint. Reverse acting PID extensions act
in the opposite manner.
FLT Parameters
Refer to Chapter 10, Direct Digital Control, for a detailed descrip-
tion of these parameters. The FLT extension uses the following
parameters:
Setpoint (DO-FLT only)
This parameter is a value in degrees. This is the target temperature
to be maintained by the extension. This value is a constant.
Input (Process Variable)
The AI address of the sensor measuring the process. This is typi-
cally a duct/space/water temperature sensor.
Input Filter
This parameter is a number between 0 and 5. This option lets you
average up to five previous sequential input samples with the
current sample to reduce the impact of rapidly changing input
values. A value of zero indicates that filtering is not being
performed.
Input Low Limit
This parameter is a value below which the extension declares the
setpoint no longer valid. At this value, the floating extension ceases
to output increase or decrease pulses.
Input High Limit
This parameter is a value above which the extension declares the
setpoint no longer valid. At this value, the floating extension ceases
to output increase or decrease pulses.

Output (Increase)
This parameter is a number between 0 and 7. This is the bit offset
address of the increase hardware output. You do not need to specif-
ically define a point address for this purpose, you need only enter
the value of the hardware bit to which the output is wired. The bit
offsets can still be defined as internal AO or DO points for another
purpose if desired.
Output (Decrease)
This parameter is a number between 0 and 7. This is the bit offset
of the decrease hardware output. Like the increase described above,
enter the value of the hardware bit that corresponds to the physical
location of the decrease pulse.
Throttling Range
This parameter is a number between 0 and 255 seconds. This is the
number of seconds required for the bidirectional motor controlled
by the floating extension to transition from fully closed to fully
open (or from fully open to fully closed).
Turn-Around Time
This parameter is a value, in seconds. This is the time required for
the motor to stop and reverse direction. Typically you will leave this
field at the default (zero).
Proportional Band
This parameter is a number between 0 and 1,000. This is the
percent of the input range (input high limit input low limit) that
the input value must change in order to drive the output from fully
open to fully closed.
Reset Interval
default is zero seconds. Use this function to eliminate a persistent
error (called offset) that has remained constant from one
Floating sample to another. Without reset, this situation (offset)
results in undesirable static module output. This function defines
reset calculation constants used to modify the output of the
Floating extension.

General (Universal)Unitary Controller Unitary Control
Rate Interval
default is zero. This is the time between calculations of the rate
portion of the FLT algorithm. Use this function to account for large
input changes by comparing the direction and magnitude of the
error between samples and correcting the output accordingly.
Mode
Select Direct or Reverse. The default is Direct. This parameter
defines the response of the FLT extension. If you choose direct
acting, the FLT increase output pulses as the process variable rises.
If you choose reverse acting, the FLT increase output pulses as the
process variable falls. This function must be used to fit the response
of the FLT extension to the end device controlling the process.
The mode you select determines what happens when the input rises
higher or falls lower than the setpoint. Direct acting FLT extensions
pulse the increase output if the input rises above the setpoint and
pulse the decrease output if the input falls below the setpoint.
Reverse acting FLT extensions act in the opposite manner.
General (Universal)Unitary Controller

The General (Universal) UC is a non-specific unitary controller
that, with certain limitations, may be used for nearly all functions
and extensions available in other DCUs. A General or Universal UC
is a UC in which a VAV, AHU, or HPMP Editor is not being used.
You may use a General (Universal) UC and an associated UCI to
perform/define any of the following editors:
Resident and Indirect Points
Calculated Points
Event Definitions
Event Sequences (up to 64)
Event Actions (up to 64)
Runtime
Consumption

Unitary Control General (Universal)Unitary Controller
Alarm Inhibit
Time Scheduling
Special Days
Temperature Control
Demand Control
UC-PID Extensions (AO and DO)
UC-FLT Extensions (AO and DO)
Trend Sampling
Trend Plot

CHAPTER
12
12
Micro Regulator Control
Micro Regulators (MRs) are small point count controllers that

operate on a subLAN connected to a Micro Regulator Interface
(MRI), Micro Controller Interface (MCI), or 7798 I/SITE LAN.
The MRI, MCI, or I/SITE LAN provide the communications
gateway to the I/NET controller LAN and support all of the stan-
dard DCU functions typical of the model 7716 PCU. The 7792 MRI
and the 7793 MCI provide two communication channels
(subLANs) for MRs. These controllers will occupy a DCU station
address for each subLAN implemented. The 7798 I/SITE LAN
provides only a single communication channel (subLAN) and will
occupy a single DCU address. Each subLAN will support up to 32
MRs of any type. The subLANs of the MCI and the I/SITE LAN will
also support access control devices (i.e., DPU7910A, DPU7920,
DIU7930, DIO7940, and SCU12xx controllers) mixed with MRs.
The subLANs of all three controllers (MRI, MCI, and I/SITE LAN)
also support ASCs mixed with MRs.
See Also: TCON109, 7790 LAN Interface Unit

TCON130, Micro Regulator (MR55 Series)
TCON147, Application Specific Controller (MR-VAV-AX)
TCON153, Application Specific Controller (MR-AHU)
Micro Regulator Configuration

The MR Configuration editor, for use with the 7792 MRI, and the
MCU Configuration editor, for use with both the 7793 MCI and
7798 I/SITE LAN, define which MRs are currently connected to the

Micro Regulator Configuration Micro Regulator Control
controller. These editors indicate if the MR is successfully commu-

nicating over the subLAN Primary channel, Secondary channel
(not supported by 7792 MRI) or not at all.
These editors present all 32 MRs (single-channel) or 64 MRs (two-
channel) for individual selection. If the MR is defined as Internal,
the controller does not attempt to transmit at that address. If the
entry is defined as MR, the controller expects the MR to success-
fully communicate at the selected address.
When a station restore is performed on an MRI, MCI, or I/SITE
LAN, all of the programming information is downloaded to that
controller. In addition, the MRI, MCI, or I/SITE LAN further
distributes information to MRs you define as external. This allows
the MRs to function in a stand-alone mode if subLAN communi-
cation is severed between the MRI, MCI, or I/SITE LAN and the
MRs.
Because this transfer of information between the host (MRI, MCI,
or I/SITE LAN) and MRs can be rather lengthy, a Please Stand By
Message appears anytime you perform a station save or station
restore to a 7792 MRI, 7793 MCI, or 7798 I/SITE LAN.
Note: An MR must be specified as MR, a door controller must be speci-

fied as DPU, and an ASC must be specified as ASC. Failure to do
so will result in communication problems to the subLAN device.
An asterisk (*) at the end of the Type column indicates that the
MRI, MCI, or I/SITE LAN cannot establish communication with
the MR. The asterisk disappears when successful communication is
established.
Note: For the MCI and I/SITE LAN, closed-loop communication is

supported that enables primary and secondary path communication.
In the event of communication failures, one of three characters will
appear at the end of the Type column. A 1 indicates normal
communication from the channels primary port. A 2 indicates
communication over the channels secondary port due to a primary
port communication failure. If there is a red asterisk (*) at the end
of the Type column, it means that there is a total communication
failure with this MR.

Micro Regulator Control Creating the MRI Database
Creating the MRI Database

Database entries for each MR are made by connecting to an MRI,
MCI, or I/SITE LAN and then selecting the desired point or exten-
sion editor from the main edit menu.
The MRI, MCI, or I/SITE LAN and MRs can use bit offset (BB)
addresses for hardware output points. This makes it possible for all
ten input and output points (0009) to reside at the same point
(PP) address and allows an MRI, MCI, or I/SITE LAN with 32 MRs
to occupy only one station (SS) address. Remember that a point
address is in the form LLSSPPBB (link, station, point, and bit
offset).
Note: Except for the MR160, bit offset addresses that are not used by the
MR may be used by the MRI/MCI as internal or indirect points. The
MR160 has no output point capability. Therefore, for this Micro
Regulator type, output point addresses may not be used as internal or
indirect points by the MRI/MCI.
For MRs and DPUs defined as Internal in the MCU Configuration

editor, bit offset addresses 0009 can be defined as External, Internal,
or Indirect resident points. However, for MRs, DPUs, and ASCs
defined as MR, DPU, DIO, DIU, or ASC in the MCU
configuration editor, only Internal and External resident points
should be defined Indirect resident points should not be used.
Note: The Minimum Trip and Minimum Close parameters are not used for
MR output commands. The editor lets you enter a value in these
fields; however, this information is not downloaded to the MR.

Chapter 7, Point Extensions

MR Parameters Micro Regulator Control
MR Parameters
This option only appears when you are connected to a 7792 MRI,
7793 MCI, or 7798 I/SITE LAN. These options let you define the
hardware-specific parameters for each MR on the subLAN.
Note: These parameters are not available with the MR160. Although this
editor can be accessed when connected to an MR160, attempts to
enter data into any of the fields will result in an MCU mem over-
flow error message.
The parameters editor defines the points that will be controlled or

displayed locally with the I/STAT or M/STAT. Using this parameters
editor, the operator can establish the master device control point,
the call point, the inactivity timeout intervals used by the I/STAT or
M/STAT, and the I/STAT or M/STAT password.
Note: The parameters in this edit screen are used by the I/STAT or M/STAT
(an intelligent thermostat connected to the MR). The I/STAT or
M/STAT controls and monitors points and devices connected to the
MR.
These parameters are stored in the MRs NOVRAM. They can be

cleared only by clearing NOVRAM memory with the I/STAT or
M/STAT. These parameters are not saved in the database save file. If
an MR is replaced or NOVRAM is cleared, the parameters must be
reentered manually.
See Also: TCON109, 7790 LAN Interface Unit


Micro Regulator Control MR Parameters
Entry Fields
Table 12-1 lists and describes the fields available for configuring an
I/STAT or M/STAT for the Micro Regulator.
Table 12-1. Micro Regulator Parameters Field Entries
Field Description
The point address or name of the point to be used as the master device control point
Master Device is entered here. This point is either a DO or DC point. The Interval field allows you
Control to specify the time from 0 to 255 minutes that the interval timer will be turned on
when this point is activated through the On/Off button on the I/STAT.
This address and point type defines the point that is controlled on or off when you
Call Address
press the I/STATs Call button. This point may be a DO or DC point.
The I/STAT and M/STAT use two inactivity timeouts to exit from the Service function
or return to the Home LED display when in the normal mode. The timer starts
Inactivity
counting down from the time the last button is pressed. For both the Escape from
Timeouts
Service and Return to Home LED timeout intervals enter a duration of 0 255
seconds.
The I/STAT or M/STAT has built in security in the form of a three-digit numeric
password. The password restricts access to the Service function on the I/STAT or
Password
M/STAT (the ability to make calibration, point, and parameter changes through the
Digits
I/STAT or M/STAT). Enter the three-digit numeric password for the I/STAT or M/STAT
in this field.
LED Functions
There are four LEDs on the I/STAT or M/STAT. Any of the four
LEDs may be designated as the Home LED. Using the select keys,
each of the four point addresses associated with the LEDs may be
selected for viewing. The I/STAT or M/STAT will return the display
to the selected Home LED after the Return to Home LED inac-
tivity timeout expires.
LED 1 allows you to enter a master setpoint address as the Base
address and a local setpoint address as the Adjust address. Both the
Base address and the Adjust address must be local to the same MR
(they must have the same PP portion defined in their address). This
allows you to locally make changes to a common system setpoint
from the I/STAT or M/STAT using the Change +/ keys and display
the newly adjusted setpoint value at the I/STAT or M/STAT. The
displayed value is a summation of the Base (common) address
value and the Adjust (local) address value.

The Adjust (local) address must be an AO point so that changes

may be made through the I/STAT or M/STAT. The Base address
may be an AI or AO point. Both points may be external or internal
points.
If the Base address master setpoint is received from another address
external to the MR, you must attach a calculation extension to the
base address (i.e. P0 = Master Setpoint) in the MRI/MCI.
Note: Without a Base address defined, only the value of the Adjust address
will display through the I/STAT or M/STAT. If the Adjust address is
not defined, then no value will display through the I/STAT or
M/STAT.
If the displayed value of the Adjust address and Base address is

needed for other applications, you must create a separate calculation
module that sums the two point address values and outputs the result
of the calculation to another internal AO point or line.
Depending upon the point type being displayed, certain parame-

ters can be defined for each LED.
AI no parameters allowed. This point type is display only on
the I/STAT or M/STAT.
AO there are three parameters that this point type supports:
Increment the value by which the analog output value
is changed each time a Change arrow button is pressed
on the I/STAT or M/STAT.
Low the lowest value to which the point may be
adjusted.
High the highest value to which the point may be
adjusted.
DO/DC/DI/DM/DA these point types support up to 2
I/STAT state descriptions. Each I/STAT state description may
be 3 characters long. Any alphanumeric character which can
be displayed on a 7-segment display can be defined in the 3-
character I/STAT state description.

Note: The following characters do not map to the 7-segment display on

the I/STAT or M/STAT, and therefore cannot be used in the I/STAT
state descriptions: K, M, Q, R, T, V, W, X, Y, and Z.
Hardware Coefficients
These conversion parameters set the FM (factory slope) and FB
(factory offset) conversion coefficients in the MR. The m value can
vary between 0 and 1.9997, and the b value can vary between 127
and 127. These parameters are primarily used by TAC for factory-
made adjustments. The end-user should avoid altering these hard-
ware coefficient settings.
The Span field offers a normal span and narrow span. The normal
span allows the full range of the 05 VDC or 010 VDC to be used.
The narrow span allows a 24 VDC range to be used on 05VDC
inputs, and a 48 VDC range to be used on 010 VDC inputs.
Lookup Tables
MR88, MR632, MR160, and MR88R Lookup Tables
Micro Regulator models MR88, MR632, MR160, and MR88R
provide four lookup tables to accurately translate the non-linear
characteristics of thermistors. These are designated LUT #1
Normal, LUT #1 Narrow, LUT #2 Normal, and LUT #2 Narrow.
Note: There are several variations of curves, dissipation characteristics, and

accuracies available for 10K ohm thermistors not all 10K ther-
mistors are alike. Contact TAC to identify the required thermistor
specifications.
Table 12-2. Lookup Table 1 and 2 Ranges
Low High
Table 1 Normal 104F 1,134F

Table 1 Narrow 24.5F 91.6F
Table 2 Normal 104F 1,134F
Table 2 Narrow 25.3F 94.1F
Note: Usable range depends upon the capabilities
of the selected sensor.

The lookup tables translate the thermistor-controlled voltage

directly to temperature in degrees centigrade with a 100 positive
bias to permit readings below zero. The lookup table entries are
defined by the equation 100 (C + 100). The output from the
lookup table is used with the user-defined m and b conversion
coefficients to create the engineering unit value. The typical M and
B coefficients are as follows:
For engineering units of C: m = 0.0100 b = 100
For engineering units of F: m = 0.0180 b = 148
When connecting a 10K ohm thermistor to the space sensor input
on an MR, you should specify the database point to use Lookup
Table 1. The factory-defined lookup tables take into consideration
the normal versus narrow span selection and no change to the
conversion coefficients is required. There is actually a Normal Table
number 1 and a Narrow Table number 1.
Table number 1 accounts for an elevated self-heating error that is a
function of the I/STAT communication interface. A separate pair
(normal and narrow) of lookup tables defined as Table number 2,
is provided in the MR firmware to support accommodation of
thermistors on the other universal inputs of the MR.
MR55X Lookup Tables
The MR55X provides two lookup tables (Table 1 Normal and Table
2 Normal) to accurately translate the non-linear characteristics of
thermistors, and one lookup table (Table 3) to translate the charac-
teristics of the on-board CFM velocity sensor. These lookup tables
are not the same as the lookup tables in the other MRs, because of
the different temperature span.
Note: There are several variations of curves, dissipation characteristics, and

accuracies available for 10K ohm thermistors not all 10K ther-
mistors are alike. Thermistor characteristics must correspond to Dale
part # IM1002-C3 (Dale curve #1) to be used with the MR family.
The lookup tables translate the thermistor-controlled voltage

directly to temperature in degrees centigrade with a 100 positive
bias to permit readings below zero. The lookup table entries are
defined by the equation 100(C + 100).

The output from the lookup table is used with the user-defined m
and b conversion coefficients to create the engineering unit value.
The typical m and b coefficients are as follows:
For engineering units of C: m = 0.0100 b = 100
For engineering units of F: m = 0.0180 b = 148
When connecting a 10 K ohm thermistor or I/STAT to the space
sensor input on an MR, specify the database point to use Lookup
Table 1. Table number 1 accounts for an elevated self-heating error
that is a function of the I/STAT communication interface. A sepa-
rate lookup table, defined as Table number 2, is provided in the
MR55X firmware to support accommodation of thermistors on the
other four general purpose inputs. Table number 3 is used only to
translate the characteristics of the on-board CFM velocity sensor.
Note: Only Normal lookup tables 1 and 2 are available in the MR55.
Narrow lookup tables are not available.
Refer to TCON130, MR55 Series Micro Regulators, for CFM analog

input point setup and calibration procedures.
Standalone ATS
Normal ATS functions are supported in the MCI, MRI, and I/SITE
LAN. Standalone ATS is intended to be the fall-back solution for
ATS scheduling if there is a break in the MR subLAN communica-
tion.
The Standalone ATS is an MR-resident ATS schedule programmed
into the MRs. Standalone ATS allows a single start and stop time for
each day of the week, and controls the point designated as the
master device control point in the MR parameters editor.
Note: If MR power is lost and subsequently restored following an

MRI/MCI-to-MR communication failure, the master device control
point (controlled by the MR Standalone ATS schedule) will default to
its deenergized state. No further time-based commands will be issued
to the point until MRI/MCI-to-MR communication is reestablished.

Direct Digital Control Modules Micro Regulator Control
Direct Digital Control Modules
Note: MR-resident DDC is not available with the MR160. Although this
editor can be accessed when connected to an MR160, attempts to
enter a DDC module will result in a repetitive MCU mem overflow
error message.
The MR controllers support six DDC module types and an inter-

connected control configuration of up to 16 DDC modules,
depending upon the type of modules. The DDC modules
supported include: the Two-Position (Two-pos) module, Propor-
tional, Integral, Derivative (PID) module, Floating (FLT) module,
Reset module, Relay module, and Calculation (Calc) module. The
HiLo module is not supported by the MR controllers. Assign DDC
modules to an MR by connecting to the desired MRI, MCI, or
I/SITE LAN and selecting MR DDC from the edit menu.
Note: MR-resident DDC modules only reside in the MR (not in the MCI,
MRI, or I/SITE LAN. Therefore, these DDC modules are not avail-
able for use in any MR tagged as Internal in the MCU configuration
editor.
The lines that interconnect the DDC modules are numbered so that
the line number always corresponds to the DDC module number
that outputs to the line.
To preserve MR memory, the PV input to the PID, Floating, and
Two-pos modules, the primary and secondary inputs to the Reset
module, and the coil input to the Relay module cannot be defined
as Constant. Instead, these inputs are selectable as Line or
Point. For the same reason, the Floating (FLT) module can only
be defined as Point. Refer to DDC Modules in Chapter 10,
Direct Digital Control, for descriptions of each DDC module.
Note: In a 7792 MRI, 7793 MCI, or 7798 I/SITE LAN, DC/DM points
should only be controlled by 7792/3/8 resident programs. This
includes the calculations, ATS, temperature control, and demand
control editors. MR-resident DDC should not be used to control
DC/DM points.

Micro Regulator Control Micro Regulator Editors
Calculation Module
This is a new module that exists only in the MR controllers. The
Calculation module is edited similarly to the existing DCU calcu-
lated point in the I/NET program. The module also operates simi-
larly with some exceptions. These exceptions and a description of
the Calculation module are provided in Chapter 10, Direct Digital
Control.
Note: Indirect AO points cannot be used as the input to a Calculation

module for MRIs, MCIs, and resident MRs.
See Also: Calculations (C) in Chapter 7, Point Extensions
MR-to-MR Copy
This function copies the data in one MR to another MR. The data
copied using this function consists of resident I/O point data,
extensions, and MR-resident DDC modules. The MR-to-MR copy
function does not copy any of the MR parameters (hardware coef-
ficients, standalone ATS, or I/STAT parameters).
Micro Regulator Editors

The Micro Regulator, with certain limitations, may be used for
nearly all functions and extensions available in other DCUs. You
may use a Micro Regulator and an associated MRI, MCI, or I/SITE
LAN to access the editors associated with any of the following func-
tions and extensions:
Alarm Inhibit Trend Plot

Calculated Points Time Scheduling
Event Definitions Special Days
Event Sequences Temperature Control
Event Actions Demand Control
Runtime Trend Sampling
Consumption MR-Resident DDC
Resident and Indirect Modules
Points

Micro Regulator Editors Micro Regulator Control
Even though an extension is resident in the MRI, MCI, or I/SITE

LAN, it may be used to perform a control function in an MR. Keep
in mind the possibility of lost communication due to a severed
subLAN communication link between the controller and MRs.
Only those editors listed below as resident in the MR can continue
to work correctly if communication is severed between the
controller and MR.
MCI, MRI, or I/SITE LAN Resident Programming

The following editors only reside in the MRI, MCI, or I/SITE LAN:
Configuration/Status Event Sequences

Station Save Event Actions
Station Restore Runtime
Station Parameters Consumption
Control Descriptions Alarm Inhibit
Control Commands Time Scheduling
State Descriptions Demand Control
Conversion Coefficients Temperature Control
Engineering Units Special Days
Resident I/O Points MR-DDC History/Tuning
Calculations MR Configuration
Event Definitions
MR-Resident Programming
The following editors reside in both the MR and the MRI, MCI, or
I/SITE LAN controller:
Station parameters
Control commands
Conversion coefficients
Resident I/O points
MR-resident DDC modules

CHAPTER
13
12
Application Specific Controllers
Application Specific Controllers (ASCs) are Micro Regulators

(MRs) that use hardware and software designed for specific appli-
cations. Some of the key ASC features are:
ASCs can be used in stand-alone configurations. No interface
controller (MRI, MCI, or I/SITE LAN) or host workstation is
required in this case.
All 20 resident points (10 input, 10 output) are pre-config-
ured from the factory. The operator is not required to build a
point database within the resident I/O points editor.
Parameters (including station parameters) are pre-configured
to default settings from the factory.
There are input points and output points within the ASC that
can be free for use in other MRI-resident applications. ASC
free points provide all the capabilities of MR-resident points
except for MR-to-MR copy, and MR-resident DDC functions.
Refer to Free Points on page 13-10.
The ASC controller can be configured from the ASC editor. This
editor is available when the I/NET system is connected to a 7792
(MRI), 7793 (MCI), or 7798 (I/SITE LAN). The editor options let
you display ASC data and configure, display, and distribute ASC
parameters to other ASCs and their points and to the MRI, MCI, or
I/SITE LAN interface controller.
I/NET will list the available ASCs. This list contains only ASCs
no other controllers are listed. Only the ASCs that have been
declared as external in the MCU configuration screen appear in the
list.

Displaying ASC Data Application Specific Controllers
Displaying ASC Data

You may display data from the ASC parameters editor menu. This
screen shows ASC dynamic data. The information displayed on this
screen is view-only none of the information can be edited from
this screen. The data is dynamically updated.
Note: The MCI must contain the resident point record for the data to
display properly. Refer to Updating the Interface Controller on
page 13-7 for the procedure of equalizing the MCI with the ASC.
System Status
The following system status parameters appear on the display
screen:
Space Temperature
This point displays the current (sensed) value of the space temper-
ature, the primary input to the controller.
Active Setpoint
If the SPd parameter is set to actual, then depending on the space
temperature (described above), the active setpoint will be set to one
of two values: either the active cooling setpoint or the active heating
setpoint. If the space temperature is closer to the active cooling
setpoint, then that value becomes the active setpoint. If the space
temperature is closer to the active heating setpoint, then that value
becomes the active setpoint.
If the SPd parameter is set to average, then the active setpoint is
the midpoint between the active cooling and heating setpoints.
Loading
This point displays the load currently being placed on the
controller. The value of this parameter is determined as follows:
Cooling: 0 to +100 for 0 to 100% cooling load as the tempera-
ture rises across Cb.
Heating: 0 to 100 for 0 to 100% heating load as the tempera-
ture falls across Hb.

Application Specific Controllers Displaying ASC Data
Central Plant Heat/Warmup

This VAV point will indicate the mode of operation of the damper
actuator. If Off, the damper modulates to cool the space. If On, the
damper modulates to heat the space.
Occupancy
This point displays the current occupancy condition (On or Off).
An On condition indicates that the space is occupied. The condi-
tion is controlled by either time of day or occupant override.
Demand Control
This point displays the current demand condition (On or Off). An
On condition indicates that demand control is being used. The
demand function can be controlled by the I/NET demand program
or by calculations base on heat load, cool load, sun load, or other
extraordinary circumstances for energy conservation.
Shutdown/Purge/Lockout
This point displays the current Shutdown/Purge/Lockout value
from the connected MCI or from the local SPL input. This points
value provides an indication of the ASCs current operating mode.
Refer to the documentation provided with your ASC for a descrip-
tion of ASC operating modes and their associated Shutdown/
Purge/Lockout values.
Enthalpy Control (MR-AHU and MR-HP)
This point displays the current enthalpy condition (On or Off)
from the connected MCI or from the local enthalpy input. If the
outside air enthalpy is lower than the return air enthalpy, then
enthalpy will be On and economizer operation will be available for
use.
Outside Air Temp
This point displays the current temperature read from one outside
air temperature sensor which is connected to the outside air
point for each ASC by calculated points in the MCI.

Displaying ASC Data Application Specific Controllers
Setpoint Parameters
The following setpoints appear on the display:
Active Cooling Setpoint
This setpoint displays one of the following three values:
Occupied cooling setpoint when demand is Off as adjusted by
the Stat Offset adjustment
Demand setup setpoint when demand is On during occu-
pancy
Setup cooling setpoint when unoccupied.
Active Heating Setpoint
This setpoint displays one of the following three values:
Occupied heating setpoint when demand is Off as adjusted by
the Stat Offset adjustment
Demand setback setpoint when demand is On during occu-
pancy
Setback heating setpoint when unoccupied.
Stat Offset Adjustment
This point displays the current offset adjustment from the I/STAT
or S/STAT as adjusted by the occupant across its range. (Its span
can be adjusted.)
System Setpoint
This point displays the single target setpoint defined from an MCI.
(The parameter SPo must be greater than 0.)
Air Status (MR-VAV only)

Setpoint
These are the airflow setpoints for cooling and for Central Plant
heat/warmup. Their value is based on the space temperature and its
distance from the active setpoint.

Application Specific Controllers Modifying Parameters
Damper Position
This point reflects the damper actuator, as a percentage, and ranges
from 0 to 100. Normally it is controlled by the VAV control
program, based on the air volume required to maintain the space
temperature. The point can also be controlled by an operator from
a host workstation, or by an event sequence in the connected MCI,
or further upstream PCU. In that case it would be necessary to put
the point in the Manual mode from the workstation, or issue the
control command with Lock from the event sequence, to prevent
the VAV control program from changing it back.
Airflow
This will display the current airflow reading.
Outputs
This section of the display data screen contains the status of the
ASC outputs as defined in the ASC parameters. Certain points will
be displayed as a percentage from 0% to 100% open. These points
can be defined as 2-position or modulating from the parameter
modification screen. Refer to the installation/reference guide for
your particular product.
Modifying Parameters
If you choose to accept the factory defaults for setpoints, bands,
configurations, etc., you do not need to change any ASC parame-
ters. If you do elect to modify parameters, you may use either the
I/STAT or M/STAT, or the ASC editor in the I/NET host.
Note: If parameter fields display incorrectly (i.e., ***** appears instead of

an actual number), then the memory in the ASC is corrupted.
Perform an update to return the ASC to its factory default settings, or
perform a copy to use the parameters of an existing ASC.
The parameters available for you to modify depend on the type of

ASC being configured. Refer to the documentation included with
your ASC for parameter descriptions and configuration proce-
dures.

Modifying ASC Names Application Specific Controllers
Modifying ASC Names

ASC names serve as a reference while in ASC-specific editors. The
ASC name will also be added at the beginning of the 20 resident
point names in the MCI. Refer to Updating the Interface
Controller on page 13-7 for details.
I/NET lists all ASCs communicating with the connected interface
controller (MRI, MCI, or I/SITE LAN). Assign or modify an ASC
name by choosing an ASC from the list and typing a new name. If
the modified name matches the name of an existing ASC, the func-
tion fails. In this case, an asterisk is placed beside the ASC with the
matching name and an error message will appear. The asterisk
makes it easier for you to locate the matching name in a long list of
ASCs.
Once the names are assigned, the operator must disconnect from
the DCU and then re-connect to see the changes made (changes
may be viewed from the DCU summary or resident I/O points
editor). An MCI update must be performed to get the complete
point record from the ASC and to define the station parameters
(refer to Updating the Interface Controller on page 13-7).
Copying ASC Parameters

You can copy the configuration of one ASC to one or more other
ASCs. The copy will include ASC parameters, I/STAT parameters,
and stand-alone ATS. I/NET presents a list of available ASCs. You
may select a source ASC from this list.
The system then lists only ASCs of the same type and revision as the
source ASC (AHU, VAV, etc.). The source ASC and ASCs of a
different type are omitted from the list.
You may individually select ASCs from the list. You may also
choose All Yes or All No to speed the selection process. When you
have selected all desired ASCs, start the copy process.

Application Specific Controllers Saving and Restoring ASC Parameters
Saving and Restoring ASC Parameters

Once you have finished configuring an ASC, you can save the
configuration (including the I/STAT parameter settings) to a SAV
file. You can then restore the configuration later if you wish. This
can be beneficial especially following an ASC Update, since
performing the update causes the ASC to lose its settings.
During the Save process, I/NET creates a separate SAV file for each
marked ASC. I/NET automatically assigns a filename that indicates
the link (LL), station (SS), and point (PP) of the ASC the file repre-
sents. For example, a file named ASC970300.SAV contains the
settings of an ASC on link 97, station 03, at point address 00. The
saved ASC files are stored on the current host workstation, in the
SAV directory defined for your system.
Updating the Interface Controller

Once you have assigned an ASC, you must perform an MCI update
to copy the point information from the ASC to the interface
controller (MCI, MRI, or I/SITE LAN). An MCI update must occur
in order to view the correct ASC point data from the host. Once the
MCI is updated, the operator must disconnect from the MCI and
then re-connect to upload the new database image to the host.
Following an update of the interface controller, each ASC-resident
point defined in the resident I/O points editor is displayed with the
ASC name occupying the first eight characters separated by a
and then followed by the 7-character ASC point name. This makes
up the total 16-character point name.
Note: Names must be assigned to all ASCs being updated to the MCI.
All four sets of station parameters are also updated in the interface
controller to reflect the station parameters required by ASCs.
Station parameters previously defined by the operator are not over-
written the ASC station parameters are simply placed in avail-
able fields. Any pre-defined parameters that exactly match ASC
parameters (case sensitive) are retained and are not duplicated.

Removing ASC Points from the Interface Controller Application Specific Controllers
If a station parameter set is full (no null spaces available) when the
update attempts to add a new entry, the MCI update is not
performed.
Removing ASC Points from the Interface Controller
Caution: When deleting ASC point information from the interface controller,
you must ensure that the ASC is set to Internal in the MCU
Configuration editor. Failure to do so will result in the deletion of
points from the ASC.
If points in the ASC are not required to be viewed from the host,
you can delete the unnecessary point information from the MCI
database using the Resident I/O Points editor. This will allow the
host workstation to be updated faster when connecting to an MCI
whose database does not match the SAVE file stored at the host.
Use the following steps to delete ASC point information from the
interface controller:
1. Connect to the interface controller (MCI, MRI, or I/SITE
LAN).
2. Enter the MCU Configuration editor and toggle the appro-
priate ASCs to Internal. Failure to perform this step will
result in the actual deletion of points from the ASC during the
next step.
3. Enter the Resident I/O Points editor and delete the unneces-
sary ASC points from the interface controller.
4. Return to the MCU Configuration editor and toggle the
appropriate ASCs from Internal back to their correct
setting.
Note: You can restore deleted point information by performing an MCI

Update. Refer to Updating the Interface Controller on page 13-7
for more information.

Application Specific Controllers Updating the ASC
Updating the ASC

In order to update a controller with TACs latest binary load, a tech-
nician would normally have to replace a controller EPROM.
Depending on the mounting location of the controller, this could
be a difficult task. The binary instruction set for the ASC is main-
tained in NOVRAM and may be updated using the factory default
update file.
I/NET presents a list of available ASCs. You may individually select
ASCs from the list. You may also choose All Yes or All No to speed
the selection process. When all desired ASCs are selected, begin the
update process.
Order of Operations
The following sequence assumes the ASCs have been installed and
configured for operation from the I/STAT.
1. Enter the MCU configuration editor from the interface
controller (MCI, MRI, or I/SITE LAN). Toggle the ASCs on
the subLAN from Internal to ASC.
2. Assuming communication has been confirmed, enter the ASC
parameters editor. Use the modify option to define each ASC
name.
3. Once the names are defined, enter the MCI update editor. Use
this editor to upload all point records and station parameters
to the interface controller.
4. Perform a station save. Disconnect from the interface
controller and then re-connect. Use the DCU summary or
individual editors to view the database.
Once Step 4 is accomplished, the operator has the ability to
perform all normal point-related operations such as defining alarm
limits, editing free points, and adding automatic time schedules.
Performing a station save will save the contents of the interface
controller as usual.

Free Points Application Specific Controllers
Note: The station save does not contain the ASC parameters.
A station restore will download the interface controller database to

the ASC in the same manner as MRs. Any resident I/O point modi-
fications will be downloaded to the ASC.
Free Points
The ASC can be configured so that specific input and output points
are available for use by other MRI, MCU, or I/SITE LAN applica-
tions. In this case, sensors or dry contacts can be connected to free
input points, and output points can be connected to discrete actu-
ators or contactors in the same manner as in Micro Regulators
(MRs).
When a free point is to be used in another application, the points
parameters, and even its type, can be modified using the resident
I/O points editor.
Caution: The resident I/O points editor does not protect against modifications
of non-free points. Any modifications to non-free points, except for
point names which have no impact on the operation of the point, will
cause the ASC to work improperly.
Refer to the documentation included with your ASC for more

information about free points and instructions for making points
free.
ASC Related Editors

Table 13-1 lists the I/NET controller editors available when the
system is connected to an MRI, MCI, or I/SITE LAN. Next to each
editor name is a code indicating the editors use related to ASCs.

Application Specific Controllers ASC Related Editors
Table 13-1. Editors
Code Editor Code Editor

M Configuration/status A Alarm inhibit (AI)
M Station save O Time scheduling (TS)
M Dynamic data upload O Special days
M Passwords F Temperature control (TC)
F Station parameters D Demand control (DC)
F Resident I/O points A Trend sampling (TR)
F Calculations (C) A Trend plot
A Event definition (EV) M MR configuration
F Event sequences M MR parameters
A Event actions X MR resident DDC
A Runtime (RT) X MR to MR copy
X Consumption (CN) A ASC parameters
Legend:
A (All) Used with all ASC points
D (Demand) Used only with the demand point in each ASC
F (Free) Used only with free ASC points (refer to Free Points on page 13-10)
O (Occupancy) Used only the with the MCI occupancy point in each ASC
M (MCI) Used for MCI operations (not point related)
X (None) Not associated with ASC

CHAPTER
14
8
7771 Industrial Controller Interface
The 7771 Industrial Controller Interface or ICI is an I/NET hard-

ware component. The ICI acts as a bridge between the controller
LAN and another online data communication system/network that
uses MODBUS protocol. The ICI lets you transfer analog or
discrete point data between the two systems. It provides data buff-
ering, storage, and translation between the two systems. If commu-
nication between the ICI and the I/NET host computer is lost, the
ICI stores data from the MODBUS system and transmits it to the
I/NET host when communication is restored. The ICI appears as a
Programmable Logic Controller (PLC 584) on the MODBUS
system. The MODBUS host passes information to and from the ICI
and the other PLCs.
The ICI is addressed, programmed, and controlled just like the
other controllers. It uses the same data point types and provides a
database for the parameters and values associated with the data
points. When you define a point, the ICI automatically makes a
connection with the PLC database.
Assigning a Station Address

All controllers must be assigned a station address. The station
address is any two-digit number between 00 and 63 you have not
already assigned to another controller. You must assign the station
address before you begin adding points to the database because
part of the point address is the station address. The station address
is always the second two digits of the eight-digit point address.
Note: As with other controllers, you must enter the station address into the
ICI using a hand-held console (HHC). Please refer to the user guide
accompanying your ICI unit for the correct procedure.

Configuring the 7771 7771 Industrial Controller Interface
Configuring the 7771

The ICI is configured for the MODBUS system using the ICI
configuration editor accessed through the edit menu. The ICI
configuration editor option only appears when you are connected
to a 7771. This lets you set the communication parameters of the
ICI on the MODBUS system. The fields are described in Table 14-1
below:
Table 14-1. ICI Configuration Field Descriptions
Field Description
ICI Port Status Select Enable or Disable. The default is Enable.

ICI Interface Type Select RS232, RS422, or RS485. The default is RS232.
Select 300, 600, 1200, 2400, 4800, 9600, or 19,200 baud. The default is
Baud Rate
9600 baud.
Data Bits Select 7 or 8. The default is 8.
Stop Bits Select one or two. The default is one.
Parity Select Even, Odd, or None. The default is Even.
ICI Protocol Select ASCII or Binary. The default is Binary.
ICI Slave Address Enter a number between 0 and 255. The default is one.
Select the amount of time the ICI waits for a response after sending a
Character Completion
request, in time units (1 time unit = 10 milliseconds). The range is 02550
Timeout
time units (02.55 seconds).
Select the amount of time the ICI waits to perform an action after receiving
Delay Before
a request, in time units (1 time unit = 10 milliseconds). The range is 02550
Response
time units (02.55 seconds). The default is zero time units.
Note: The parameters you define here must agree with the parameters
defined in the MODBUS host. As described above, the ICI emulates a
PLC 584 so make sure the MODBUS host is configured to recognize
the ICI as such.
Points and Addressing

The I/NET and MODBUS systems use different sets of point types.
The ICI converts MODBUS point types so that I/NET can recog-
nize them and vice versa. All MODBUS points should have a corre-

7771 Industrial Controller Interface Configuring the 7771
sponding external point defined in I/NET. Points defined as

internal in the ICI exist only in the I/NET software, they do not
send information to or from the MODBUS. If you accidentally
assign an internal I/NET point to a MODBUS point, the ICI gives
you an error message when you attempt to command or receive
data from the MODBUS host.
The ICI supports all standard I/NET input and output point types.
Below is a brief description of each point type as it functions with
the ICI.
Table 14-2. Point Types
Point Type Description
A DI or DA point monitors the state of a MODBUS coil and a GI point monitors the state
DI, GI, DA
of a set of coils through a force or preset control command from the MODBUS host.
These point types are always used as a pair. A DM point receives the state of a
MODBUS coil through a force or preset control command from the MODBUS host.
DM and DC
A DC point sends the state of a discrete output to a MODBUS input for the MODBUS
host to read.
The ICI sends the state of an I/NET discrete output point or set of points (using a GO
DO, GO
point) to a MODBUS input for the MODBUS host to read.
An AI point receives the value of a MODBUS holding register (memory location)
through a force or preset control command from the MODBUS host. The data is
AI
sent as an integer value which is then converted to a digital state that I/NET can
accept.
The ICI gives the value of the output to a MODBUS input register (memory location)
AO for the MODBUS host to read. The data is sent as an integer value and must be
converted for use by the MODBUS system.
This point accumulates pulses from the MODBUS coil and converts the pulses to
PI
engineering unit values. The ICI does not support it as an external point.
Using the peer-to-peer communications on the I/NET controller

LAN, the ICI output points use I/NETs indirect points in other
DCUs to obtain point data (states or values) from other controllers.
ICI input points use I/NETs controller LAN broadcast capability
to share a state or value from the MODBUS with other controllers
on the LAN.
See Also: Resident Input/Output Point Types in Chapter 6, Input and

Output Points

Configuring the 7771 7771 Industrial Controller Interface
MODBUS Addresses
The MODBUS database uses an addressing system that differs from
the eight-digit system used in I/NET. The MODBUS logical
addresses for a series of points runs from one to 9,999. However,
the connection between I/NET and the MODBUS is limited to 255
points per ICI. A register is an AI memory location in a MODBUS
device. The MODBUS uses four point types and assigns each type
a different number. Each point type has a certain number of
addresses available to it as described below:
Type 0 registers 00001 to 00256
MODBUS PLC Point Types

The MODBUS PLC supports these point types:
Coils
These are DO points that control the state (ON or OFF, OPEN or
CLOSED, etc.) of field equipment. The MODBUS host reads and
controls these points. MODBUS protocol refers to coils as Type 0
registers (00001 to 09999).
Inputs
These are DI points that typically monitor the state (OPEN or
CLOSED) of a switch contact or a piece of equipment. These points
are read-only, the MODBUS host computer cannot control them.
MODBUS protocol refers to inputs as Type 1 registers (10001 to
19999).
Input Registers
This point type provides the MODBUS host with variable quanti-
tative information, typically analog input or pulse count values.
The input register provides 16 bits of resolution and typically
displays a value between 0 and 65,535. MODBUS protocol refers to
these as Type 3 registers (30001 to 39999).

7771 Industrial Controller Interface Point and Database Mapping
Holding Registers
These registers accept a number between 0 and 65,535 from the
host and may be used by the PLC to perform functions such as
modulation of a local process variable such as an AO point. The
MODBUS host controls and reads the holding register value. The
MODBUS protocol refers to these as Type 4 registers (40001 to
49999).
Point and Database Mapping

The data points exchanging information between I/NET and the
MODBUS system must have a defined relationship. You establish
this relationship by entering the point data into the ICI database.
As mentioned earlier, the ICI automatically makes the logical
connection between the I/NET addresses and the MODBUS PLC
addresses from its database.
The ICI is active on the I/NET controller LAN and can broadcast
data. On the MODBUS system, the ICI is passive and waits for the
MODBUS host to poll it for data, or send data to it. Information
broadcast from DO/DC or AO/GO outputs on the I/NET
controller LAN are placed in the ICI I/NET database.
When the MODBUS host polls the ICI, the data is sent to input or
input register points. Since the ICI cannot talk directly with the
PLCs, it must wait for the MODBUS host to ask for or send it data.
The MODBUS host sends the state/value of coil and holding
register points to the ICI at defined MODBUS addresses. The ICI
then converts the data for broadcast on the I/NET controller LAN.
Mapping the ICI on the Controller LAN

Before you can place data into the ICI database from the I/NET
controller LAN, you must do the following:
Define as global points those ICI points that are to broadcast
their states or values to other DCUs on the controller LAN.
Define an indirect point in the ICI to receive desired broad-
cast point data from other I/NET controllers.

Point and Database Mapping 7771 Industrial Controller Interface
Mapping the ICI on the MODBUS

To move data from the MODBUS PLCs to I/NET points, you must
do the following:
Define the I/NET ICI point as a global point.
Define an indirect point in the controller to receive the
desired broadcast point data.
ICI Mapping Conversion

The ICI provides direct conversion and mapping of inputs and
outputs between the MODBUS interface and the I/NET interface.
The conversion and mapping are shown in the table below:
Table 14-3. MODBUS to I/NET Conversions
MODBUS I/NET
0000 to 3107 (PPBB)

Coils 00001 to 00256, DO
Discrete Inputs DI, DA, or DM
0000 to 3107 (PPBB)
Holding Registers 40001 to 40256, AO
Analog and Digital Inputs (AI and GI)
0000 to 3107 (PPBB)
Inputs 10001 to 10256, DI
Discrete Outputs DO or DC
0000 to 3107 (PPBB)
Input Registers 30001 to 30256, AI, PI
Analog/Digital Outputs AO or GO
Direct mapping of the points between the MODBUS and the

I/NET controller LAN establishes the numeric relationship as listed
in the table. The first digit of the MODBUS point can be 0, 1, 3, or
4, depending on the MODBUS point type it represents.

7771 Industrial Controller Interface Point and Database Mapping
Table 14-4. MODBUS to I/NET Direct Mapping
MODBUS I/NET MODBUS I/NET MODBUS I/NET MODBUS I/NET

Point PPBB Point PPBB Point PPBB Point PPBB
X0001 0000 X0065 0800 X0129 1600 X0193 2400

X0002 0001 X0066 0801 X0130 1601 X0194 2401
X0003 0002 X0067 0802 X0131 1602 X0195 2402
X0004 0003 X0068 0803 X0132 1603 X0196 2403
X0005 0004 X0069 0804 X0133 1604 X0197 2404
X0006 0005 X0070 0805 X0134 1605 X0198 2405
X0007 0006 X0071 0806 X0135 1606 X0199 2406
X0008 0007 X0072 0807 X0136 1607 X0200 2407
X0009 0100 X0073 0900 X0137 1700 X0201 2500
* * * * * * * *
* * * * * * * *
X0061 0704 X0125 1504 X0189 2304 X0253 3104
X0062 0705 X0126 1505 X0190 2305 X0254 3105
X0063 0706 X0127 1506 X0191 2306 X0255 3106
X0064 0707 X0128 1507 X0192 2307 X0256 3107
Point Class
All ICI I/NET points, except those defined as internal, connect with
a similar point type in the MODBUS system. All MODBUS points
should match a similar I/NET external class point.
If you accidentally associate a MODBUS point with an internal
I/NET point, the ICI returns an error message when the MODBUS
tries to query or command that point. This error message appears
in the EVENTS table or on a printer, but will not appear on your
screen.
Point Name
Each point in the ICI is assigned a unique 16-character name. This
name is the connection to the MODBUS address. An effective
method of naming your points is to type MB at the beginning of the
MODBUS point address, then the address, a space, and the
MODBUS point type: MB40129 Hold Reg.

Point and Database Mapping 7771 Industrial Controller Interface
Scan Interval
This is the number of seconds between each scan of the point you
are defining. The range is 1255 seconds. For most points the
default setting is the proper scan rate. The scan rate should not
exceed the physical response capability of the point it controls or
monitors. The scan rate of global points should also match the scan
rate of those points that use data from global points.

CHAPTER
15
30
SevenTrends
This chapter is based on the former stand-alone Docutrend refer-

ence guide (TCON 239). With the changes in I/NET Seven, there is
no longer enough information to justify a separate book.
The following general changes were made during the conversion
process, in order to make this document easier to read:
Some information was moved in its entirety to a different
section (for example, from an overview section to a function-
specific section). In such cases, change bars and edit markings
are used only to indicate actual text changes and not the entire
moved text.
Some section headings were renamed or removed, as appro-
priate, without showing change bars or edit markings.
Sections referring to extraction and Doc to DIF have been
deleted entirely. These deleted sections are not shown as
edited text.
Sections referring to formatting and printing reports have
been deleted, as the information previously found in these
sections will be covered in the new Database Connectivity
and Reporting guide (TCON303). These deleted sections are
not shown as edited text.
The description of masking has been changed to a reference to
the Messages chapter. This is not shown as edited text, as the
original was a copy of the same information found in that
chapter.
References to RWONLN and the file size calculation section
has been removed. They will be replaced by a discussion of the
data storage space required for I/Trend tables. This issue is
still up in the air, as we reconsider the archiving system, so
those sections are not complete.
Sections discussing functions dependent on the archive
method were deleted, as they need to be completely rewritten.

SevenTrends
SevenTrends is a multi-purpose data collection and custom

reporting utility that is included with your I/NET building
management system. This program collects data stored by the
DCU and sends it to the operator station for storage, retrieval, and
report generation.
This document presents the basic phases of SevenTrends definition

and programming. The phases you must complete to use Seven-
Trends are:
define the trends you wish to track using SevenTrends (see
Defining Trends on page 15-10)
collect trend data in the DCU, PCU and MRI/DPI/MCI (see
DCU Editors on page 15-15)
collect trend data at the operator station (see Data Flow on
page 15-4)
define transfer activity for SevenTrends data (see Seven-
Trends Transfer Configuration Editor on page 15-25)
Note: You may begin collecting SevenTrends data in the

DCU/PCU/MRI/DPI/MCI before defining the trend(s) in the oper-
ator station. However, no SevenTrends data can be uploaded to the
operator station until the trends have been defined. To avoid losing
data, it is recommended that you define the trends in the operator
workstation prior to collecting SevenTrends data in the
DCU/PCU/MRI/DPI/MCI.
Forms are available to help you in planning and entering your

SevenTrends information. These forms can be found as part of
TCON157, I/NET Forms and Worksheets.
SevenTrends data may be used to generate reports, either automat-
ically by a set schedule, or manually as required. Refer to the help
file for more information.

SevenTrends SevenTrends Data Storage
SevenTrends Data Storage

SevenTrends data can be stored on any operator station in the
I/NET system. In most cases, the information you collect will not
be stored on all operator stations. Only the operator stations with
a matching distribution group and at least one matching active
mask position will receive and store the data (refer to Masking in
Chapter 3, System Messages). In a large system, this helps keep any
one operator station from being overwhelmed with data storage
and collection. It also lets you assign different operator stations
different tasks, such as monitoring a specific area.
SevenTrends collects and maintains your data in tables in the
INETDB database. A transfer database is available for extended
online storage. SevenTrends records may also be archived.
The TrendDefinition table stores the parameters for all defined
trends (type, point, etc.). SevenTrends sample data for each trend
type is stored in a separate database table. The amount of data
stored in each table will vary, depending on the parameters you
choose for the individual trends and the SevenTrends transfer
configuration.
See Also: SevenTrends Data Management on page 15-22
Collecting Data
The operator workstation will collect and store a vast amount of
data if a few tasks are performed properly. You must:
Set the SevenTrends group and active mask positions to the
appropriate values and positions in the host configuration
editor for the host workstation.
Set the appropriate parameters in the functional editors and
the resident I/O editors in the DCUs.
The distribution group and mask must match at least one
active position in the host workstation.
The cell number must be greater than zero (0)
The priority must be other than None

SevenTrends Data Storage SevenTrends
Define the appropriate trend types in the host workstation,

with the appropriate (non-zero) cell number(s).
The operator station can only receive and store data when the
I/NET I/O Server is running. The I/NET program does not have to
be actively running. This allows you to continue to collect data
while running a program other than I/NET.
DCUs store trend data in an operator station only if the point
address, cell type, distribution group and active mask position
match. In addition, the SevenTrends priority must be adequate to
ensure communication to the desired host. Use the host configura-
tion editor to set the SevenTrends masking for an operator station.
Note: SevenTrends requires either a direct connection, a network connec-

tion (i.e., Ethernet or internet connection using a NetPlus Router), or
Auto-dial/Auto-answer (AD/AA) dial functions. The integrated dial
function does not allow the Tap or modem to initiate a call, and thus
does not provide a reliable data transfer mechanism.
See Also: Defining Trends on page 15-10

SevenTrends Data Management on page 15-22
Masking in Chapter 3, System Messages
Priorities in Chapter 3, System Messages
Host Configuration in Chapter 4, Host Functions
Data Flow
All SevenTrends information is stored in the DCU, which routes
the data to an operator station. Before you begin, it is helpful to
understand how DCUs, Taps, and operator stations work together
to provide SevenTrends information.
Simple I/NET Configurations
The sequence of actions occurs as follows for an online host:
1. When a DCU is ready to send information to an operator
workstation, it sends an Upload or Sample data request to the
Tap (which is connected to the operator station), as shown in
Figure 15-1 (step #1).

1 Upload or Sample 1 Upload or Sample

Data Request Data Request
DCU
Operator 2 Process Upload 3 Request Data Stores data,

78010 Tap generates upload
Station or Sample Data
Request or sample data
requests.
5 Transmit Data 4 Transmit Data
Figure 15-1. Basic I/NET Configuration
2. The operator station tells the Tap that it is ready to receive

SevenTrends information (step #2). At this time, the Tap
sends a message to the DCU asking it to send the data (step
#3).
3. The DCU sends the data to the Tap (step #4), which passes it
on to the operator station (step #5).
When the operator station is not online (i.e., powered off or
disconnected) the Tap stores upload or sample data requests in a
queue. The Tap has enough memory to hold about 100 upload or
sample data requests (without a MIP). The 78010 Tap stores as
many upload or sample data requests as it can. If the Tap becomes
full, the oldest upload or sample data request is deleted and
replaced with the newest request, and an error message is gener-
ated.
Note: Only upload and sample data requests are buffered. The SevenTrends
data is not available to the host until the data is transferred from the
DCU/PCU/MRI/DPI/MCI. The host honors all pending upload and
sample data requests. In some cases, where lengthy communication
delays occur or if a host workstation has been powered off for long
periods of time, the host will honor multiple requests for the same
point, and as a result may duplicate data in SevenTrends tables. This
will occur if the workstation is turned off and the Tap is left on. To
avoid this situation, turn the Tap off whenever you turn the worksta-
tion off. Better yet, it is recommended that host workstations used for
storing SevenTrends data, and their associated Taps, be left on.

Complex I/NET Configurations

Adding more Taps to the system increases the buffering effect. The
more complex system configuration shown in Figure 15-2
produces the following actions:
3
78032
DCU
Tap
1 2
78010 78022 The circled numbers indicate
Tap Tap the order in which upload or
sample data requests will be
stored. When the Tap's memory
is full, the next Tap in line
will begin storing requests.
Operator
Station
(offline)
Figure 15-2. Complex I/NET Configuration
1. If the operator station is offline the 78010 Tap stores the

upload or sample data requests (step #1).
2. When the 78010 Tap is full, upload or sample data requests
begin to be stored in the 78022 Tap (step #2).
3. When the 78022 Tap becomes full, the 78032 Tap starts
storing upload or sample data requests (step #3).
Dial I/NET Configurations
In certain situations the communication link to the DCUs may go
through a dial telephone link. This example is similar to the
complex I/NET configurations discussed above. However, in this
configuration, you tell the different programs in the DCU if and
when to dial the operator station with upload or sample data

requests. If you tell the programs not to dial the operator station,
upload or sample data requests are stored in the 78060/1 Tap. If this
Tap becomes full, the DCUs start storing their own upload
requests.
Controller LAN
78050 78060
Tap Tap
DCU *
Host LAN
* Stores upload or sample data

78010 requests. Calls 7805 or 7804
Tap (through 7806 or 78061) when
Operator
there is a dial request. Delivers all
Station
upload and sample data requests
once connected to the 7805/7804.
OR Controller LAN
78041 78061
Tap Tap
High Speed Modems
Figure 15-3. Sample Dial I/NET Configuration
A 78010 Tap can buffer approximately 100 messages at a time while

the workstation is reading or writing to the hard drive (1200 with a
MIP module installed). Every time you send A_sample or
D_sample cell information, it is considered an Upload request
message at the Tap. If you are trending 100 points with the same cell

sample count, base time, and interval, you are in fact sending 100
messages to the Tap at the same time for it to come and get the data
from the controller where the trending is taking place. This can
overload the Taps buffer capacity, causing lost cell data. To avoid
this situation, you must stagger the base time so that fewer upload
request messages are sent to the Tap at any one time.
If you tell the DCU programs to dial an operator station (on a host
LAN) and the workstation is turned off, then the 78010 Tap buffers
the messages until it is full, followed by the 78050/1 Tap, and then
the 78060/1 Tap. When an online operator station receives an
upload or sample data request, the operator station gets the data for
that particular upload or sample data request as well as for any
other upload requests that might be stored in the 78060/1 Tap, as
shown in Figure 15-3 on page 15-7. The 78041 and 78061 Tap
follow the same procedure.
Typically, the Trend editor will have a Priority assignment and will
have to wait until the Tap receives a Critical message or the Tap
reaches its assigned Percent full threshold or Dial later limit. If
another message with a Critical priority assignment requests an
upload, the Priority request will piggyback on the transmission
to minimize dialing activity. This capability is especially important
if the call incurs long-distance charges.
Data Transfer Schedules
The different DCU editors send information to SevenTrends at
different times, as shown in Table 15-1.
Table 15-1. Editor Data Transmission Schedule
DCU Editor Schedule
Resident I/O Points Sends information to SevenTrends when a

Doors message or transaction is generated.
Consumption
Demand Sends information to SevenTrends at one minute
Override past midnight, according to the clock on the DCU.
Runtime
Sends information to SevenTrends based on the
Trend Sampling trend sampling interval and cell sample count
assigned to the point.

SevenTrends SevenTrends Types
Troubleshooting
If you are encountering difficulty in collecting SevenTrends data,
check the following items:
I/NET I/O Server is running.
The cell number in the host workstation is not zero (0).
The cell number in the DCU is not zero (0).
The trend type is appropriate to the data being collected.
The distribution group number is the same in the host and
DCU.
There is a match between the SevenTrends distribution group
and at least one active mask position in the host and DCU.
The priority in the DCU editor is set to at least Routine for a
direct connect system, or Critical for a dial system.
SevenTrends Types
SevenTrends allows you to define six different types of trend. The
trend type specifies the type of information that will be recorded.
Each trend type has specific fields associated with it. All samples
have date and time fields. Other trend fields vary depending on the
type of information collected. Table 15-2 provides descriptions of
the various trend types and shows the fields associated with each .
Table 15-2. Trend Types
Type Description Table Fields
A_sample (analog sample) trends store the value Date/Time

of a particular analog, digital, or pulse (AI, AO, GI, Value
A_Sample
GO, or PI) point, at the sample interval defined in
the trend sampling editor.
Consumption trends store the accumulated value Date/Time
of a consumable used each day. Points directed to Daily consumption
a consumption cell are always PI (accumulator)
Consumption points. These trends can also store calculated
values such as Cooling degree days or Heating
degree days. There is only one entry stored per
day, at midnight (DCU time).

Defining Trends SevenTrends
Table 15-2. Trend Types (Continued)
Type Description Table Fields

Demand trends store the peak KW demand, time Date/Time
at which the peak demand occurred, and the total Daily consumption (KWH)
Demand
KWH consumed each day. There is only one entry Daily peak time
stored per day, at midnight (DCU time). Daily peak demand value (KW)
D_sample (discrete sample) trends store the state Date/Time
(door is closed, pump is on) of a particular discrete Value (integer)
point (DI, DA, DM, DC, or DO), at the sample State (text)
interval time you defined in the trend sampling
D_Sample editor. The actual state stored in a D_sample trend
is a 0 for open and 1 for closed, not the state
description pair of the point itself. You may enter a
text description for the point states as part of the
trend definition.
Override trends store the values associated with Date/Time
the 7750 Building Manager zones. Those values Billable exclusive KWH
are usually a zones individual (exclusive) KWH, Billable shared KWH
Override shared KWH, and daily KWH in the override Billable daily KWH
mode. Billable and non-billable override times and Non-billable exclusive KWH
values are stored. There is only one entry stored Non-billable shared KWH
per day, at midnight (DCU time). Non-billable daily KWH
Runtime trends store the runtime (in minutes for Date/Time
each day) of the point you selected in the runtime Daily runtime in minutes
Runtime
editor. There is only one entry stored per day, at
midnight (DCU time).
Defining Trends
Use the SevenTrends Definition function to define trends in a host
workstation. These are used to store data collected by the I/NET
DCUs. Please take some time to consider what type of SevenTrends
reports you plan to generate and what information you want to
appear in those reports. There is no greater frustration than to
decide to generate a sophisticated report and then find that the raw
data has not been collected and stored.

SevenTrends Defining Trends
You may find it helpful to document your system (recording trend

names, types, etc.). This will allow you to modify your reports as
your system grows and changes, and to troubleshoot your system if
anything goes wrong. You may wish to use the forms provided in
TCON157, I/NET Forms and Worksheets, for this purpose.
SevenTrends Parameters Editor

This editor allows you to define the parameters for the SevenTrends
data you wish to track. Each definition is for one trend type on a
specific point.
Point
The point for this trend. Select or enter the desired point from the
Point Selection editor (refer to Point Selection Editor on page
15-13). The selected point cannot be changed once a trend is
defined.
Note: This field is not used when defining a cell.
Name
The unique name for this trend or cell, up to 30 characters. The
default name varies, as follows:
If you are connected to the controller and select the point
from a pane on the Point Selection editor, the default name is
in the form Point Name -- Trend Type.
If you are connected to the controller but manually enter the
point address in the fields at the bottom of the Point Selection
editor, the default name is in the form Point Address --
Trend Type.
If you are not connected to the controller when selecting a
point from the Point Selection editor, the default name is in
the form Point Address -- Trend Type.
If the SevenTrends definition is generated automatically from
a cell definition, the default name is in the form Point
Address -- Trend Type.
If you are defining a cell, the default name is in the form Cell
Number -- Trend Type.

If you do not enter a name, the default name will change automat-
ically with the point (or cell number) and trend type selection
when you are creating a new trend. You may change the name of a
trend or cell definition at any time without loss of data.
If you choose not to use the default names, give some thought to
your naming system before you begin. The use of combinations of
names and numbers is recommended; i.e., CHWS TEMP 1, CHWS
TEMP 2, and so on.
Type
The type of SevenTrends information you wish to collect from this
point. The selected type cannot be changed once a trend or cell is
defined.
Transient Duration
Use this field to discard data that has been in the system for the
specified number of days (145). For example, if you enter a 3, then
SevenTrends stores the last three days of information. On the
fourth day, the oldest stored information is replaced with informa-
tion collected on the fourth day.
Note: Transient duration is used to delete records only when the system is
due to perform an automatic transfer. Therefore, it is possible that
individual samples will be kept beyond their transient duration
period. If you change the transient duration for a cell or trend, the
new value will not be used until the next-scheduled automatic
transfer.
Make sure that the transient duration is sufficient for your

reporting purposes. For example, if the collected data is to be used
to generate an automatic monthly report, the duration must be set
at a number high enough to ensure availability of all data for a
month, plus a few extra days to account for the possibility of a
power failure, printer failure, paper outage, or any other mishap
which might delay the printing of the report. A trend used for a
monthly report should, therefore, have a transient duration of 34
to 36 days. On the 35th (or 37th) day, the oldest information would
be replaced with new information, and the process would continue
on a first-in, first-out basis.

If you enter a zero (0), SevenTrends collects information for this

cell until you either archive the trend, delete the trend, change this
field, or the database reaches 100% of capacity. You will need to
archive the data whenever the database approaches full capacity to
avoid losing collected data. Refer to SevenTrends Data Manage-
ment on page 15-22.
Cell Number
The desired cell number (01023). You must assign a value other
than zero in order for SevenTrends to store the trend information.
This field can be used to auto generate trend definitions. Other-
wise, this field is not used in I/NET Seven and can be any value.
This field provides backward compatibility for systems which
previously used the DocutrendTM data collection system. If desired,
you may use the cell number to provide a grouping function on
reports.
Point Selection Editor

The Point Selection editor is the same one used in other functions.
It is divided into four main windows. Use the Station button at the
bottom of the screen to select a controller for display for each
window. Each window allows you to specify a controller. The
trended points from the selected controller will appear in the desig-
nated window.
You may select a point from any quadrant, or enter the point
address in the boxes at the bottom of the screen. The full point
address, including point type, is required.
Note: If you are connected to the controller in any of the quadrants, the
default trend name will use the point name. Refer to SevenTrends
Parameters Editor on page 15-11 for a full discussion of default
names.
Link
The LL portion of the LLSSPPBB PT address for the desired point.
This field is automatically entered if you select a point from one of
the four quadrants.

Station
The SS portion of the LLSSPPBB PT address for the desired point.
the four quadrants.
Point
The PP portion of the LLSSPPBB PT address for the desired point.
the four quadrants.
Bit Offset
The BB portion of the LLSSPPBB PT address for the desired point.
the four quadrants.
Type
The PT portion of the LLSSPPBB PT address for the desired point.
the four quadrants.
Controller
The controller type for this point address.
Modifying and Deleting Trends

When you modify a trend definition, only the name, transient
duration, and cell number may be changed. (If you change the
transient duration for a cell or trend, the new value will not be used
until the next-scheduled automatic transfer.)
Deleting a trend definition deletes all reference to a trend and all
associated raw data. Once deleted, a trend and its data cannot be
retrieved, even if it was previously archived.
Using Cells to Generate Trend Definitions

I/NET Seven does not support cells in the same way that the
previous DocutrendTM system did. Data is no longer stored in cells,
but in database tables by type of trend. SevenTrends requires a
separate trend definition for each point address and trend type.

The cell function in SevenTrends is designed to streamline the

trend definition process by using cell definitions to automatically
create multiple trend definitions. Instead of entering separate
SevenTrends definitions for multiple points, you can define a cell
for a specific trend type, and assign that cell number to the trend in
the DCU. When a sample is received, SevenTrends will automati-
cally create the trend definition from the cell definition.
Note: For manually defined trends, the cell number in the DCU editor does
not need to match the cell number for the trend definition. The cell
number in the trend definition is the one that will appear on reports.
The process flow is shown in Figure 15-4.

Modifying Cell Definitions
When you modify a cell definition, the only parameters that can be
changed are the cell name and the transient duration. Changing the
transient duration will affect all defined trends with a matching
trend type and cell number. (If you change the transient duration
for a cell or trend, the new value will not be used until the next-
scheduled automatic transfer.)
Caution: Exercise care when modifying cells. The system does not differentiate
between trends generated automatically from the cell definition and
trends defined manually. All trends with a matching trend type and
cell number will be affected.
DCU Editors
This section is a combination of two nearly-identical sections: one
from the front part of the book and one from a specific chapter.
Duplicate information was removed without showing editing
marks. The opening and closing paragraphs are combinations of
the respective paragraphs in each section.
There are certain editors in the DCU that can provide information
to SevenTrends. The data may be collected as often as once per
minute, or as seldom as once per day, depending on the editor used.
The following editors may provide information that SevenTrends
will use or that will affect the storage of SevenTrends data:

Figure 15-4. Cell Process Flow
Host Computer Configuration

Host Tap Configuration
LAN Tap Configuration
Link Tap Configuration
Resident I/O Points
Consumption
Demand Control
Doors
Override Billing
Runtime

Trend Sampling
In each of these editors, you will find common fields that pertain to
SevenTrends data. Remember that the edit menu selections change
depending on the type of controller to which you are connected,
and your password level.

Chapter 7, Point Extensions
Masking
Best described as Where to send the SevenTrends data? Masking
for SevenTrends data works in exactly the same way as masking for
event messages and alarms. However, the configuration editor for
host workstations has a separate section for the SevenTrends data
masking. It is possible for the SevenTrends data masking to be
completely different from the masking for messages and alarms.
Note: The SevenTrends masking for the DCU points can be set from any
host workstation. SevenTrends masking for a host workstation can be
set only at that workstation.
See Also: Masking in Chapter 3, System Messages

Use the host configuration editor to set the SevenTrends masking
for the operator station. Make sure that the workstations Seven-
Trends masking matches the distribution group and at least one
active mask position selected in the different DCU editors. The
masking should be set the same in each DCU editor. If it does not
match, then your data will not be stored on the host workstation,
and will not be lost.
You may use multiple active mask positions for each operator
station to select data from different DCUs and from different loca-
tions as appropriate. There is no one correct way to set masks as
long as the ones you set in the operator station match with at least
one active position in the DCU where the data you want will be
collected and transmitted.

Depending upon the operation circumstances of your facility, you

may wish to send tenant billing data directly to an operator station
in the accounting department, electrical alarms to the electrical
maintenance department, HVAC alarms and operational data to
the air conditioning maintenance department, and all of the data to
the facilities or operations department. This can all be done
through the use of message routing and the appropriate use and
matching of active mask positions.
Alarm/Message Priority
Best described as To send or not send the SevenTrends data?
Priority in SevenTrends indicates whether a DCU will generate an
upload request to an operator station. The default is None.
Table 15-3. Message Priorities
Priority Description
None Do not send data from this point.

Routine Send information only to directly connected host workstation(s).
Send all data when the Tap Percent Full or Dial Later limit is reached on AD/AA
Priority
configurations. Send information immediately to directly connected host workstation(s).
Send all data originating from this point to the host workstation(s) immediately (send dial
Critical request on AD/AA configurations). Send information immediately to directly connected
host workstation(s).
See Also: Priorities in Chapter 3, System Messages

Cell Number
The cell number is a parameter carried forward from the previous
data trending system, DocutrendTM. Although trend data is no
longer stored in cells, you must select a cell number other than 0 (1
1,023) if you wish to collect SevenTrends data.
This field can be used to auto generate trend definitions (see
SevenTrends Inquiry on page 15-19). Other than this, I/NET
Seven does not use the cell number internally in any way, and the
only check is to see whether the cell number is greater than 0. You
may choose to use the cell number in any way you wish, including:
Carry over previous Docutrend cell numbers, for continuity.

SevenTrends SevenTrends Inquiry
Assign cell numbers in groups (for example, assigning all

trends on motors to cell 17). This will allow you to sort data
on reports that you generate.
Make all cell numbers the same, or select numbers randomly.
As long as the cell number is not 0, the data will be collected.
Sample Count
The Trend Sampling editor asks for one additional piece of infor-
mation relating to SevenTrends not found in other editors. This is
best described as When to send the sampled SevenTrends data?
Because trend sampling can collect information over a wide period
of time, you must tell the system how often to collect the sample.
Since the trend sampling editor takes a point sample on a periodic
basis, you must tell it to send the information to the host worksta-
tion after a certain number of samples have been taken. Seven-
Trends will generate a trend sample upload request when the
number of trend samples collected is equal to the user-specified
quantity.
For example, if the trend interval is two minutes, and you define the
cell sample count as five, then information will be sent to the host
workstation every ten minutes.
SevenTrends Inquiry
The SevenTrends Data Inquiry function allows you to review or
modify existing data, and to backfill any missing data. All nonar-
chived samples may be edited, and missing data may be backfilled.
The SevenTrends Inquiry summary lists all defined trends, sorted
by name, whether or not there are data records for that trend. Select
a trend from the list to begin.
Inquiry Date Range

This editor allows you to filter out older records from the display.
Earliest Date
The desired beginning date for the listed records. The default value
is 01/01/83 (January 1, 1983).

SevenTrends Inquiry SevenTrends
Earliest Time
The desired beginning time for the listed records. This sets only the
time on the designated earliest date. The default value is midnight
(00:00:00).
SevenTrends Data Summary

This editor displays the list of records for the selected trend, minus
any records before the selected date and time. The column names
for this editor will vary, depending on the type of trend selected.
Line
An index number for the displayed record. This field is for refer-
ence only, and refers only to the position on the displayed list. The
Line number is not part of the SevenTrends data record.
Date
The date and time for the record. This field is used for all trend
types.
Note: The Line and Date fields are used for all trend types. The remaining
fields that may appear are listed in alphabetical order.
Binary State
The binary state (07) of the sampled point. (Discrete sample
trends.)
Consumption
The daily consumption for the sampled point. (Demand trends.)
Exclusive
The amount of energy (in kwh) expended in exclusive billable over-
ride functions at the sampled point. (Override trends.)
NonExclusive
The amount of energy (in kwh) expended in exclusive nonbillable
override functions at the sampled point. (Override trends.)

SevenTrends SevenTrends Inquiry
NonShared
The amount of energy (in kwh) expended in shared (nonexclusive)
nonbillable override functions at the sampled point. (Override
trends.)
NonTime
The total nonbillable override time, in minutes, accumulated at the
sampled point. (Override trends.)
Peak Time
The time the highest daily demand occurred at the sampled point.
(Demand trends.)
Peak Value
The highest daily demand at the sampled point. (Demand trends.)
Shared
The amount of energy (in kwh) expended in shared (nonexclusive)
billable override functions at the sampled point. (Override trends.)
State Text
The description for the binary state of the sampled point. (Discrete
sample trends.)
Note: The initial entry for this field comes from the state description table
for the controller. This field, like the other SevenTrends fields, may be
edited. The edited text may or may not match the descriptions
entered in the state table.
Time
The total billable override time, in minutes, accumulated at the
sampled point. (Override trends.)
Value
The value on the trended point at the time this sample was taken.
The information available in this field will vary depending on the
trend type. (Analog sample, consumption, runtime trends.)

SevenTrends Data Management SevenTrends
Modifying SevenTrends Data

You may modify the values for an existing record, or add a new
record. When the desired trend samples are displayed in the Seven-
Trends Data summary, select either Add or Modify.
When you modify an existing record, you cannot change the
sample date and time. All other fields can be edited.
When you add a new record, enter the date and time of the
sample, along with the value(s) for the other sample field(s).
Deleting SevenTrends Data

You may delete individual SevenTrends samples by selecting Delete
from the SevenTrends Data summary. Once deleted, a sample may
not be retrieved.
Note: If you know the sample information, you can manually recreate a
record using the Add function.
SevenTrends Data Management

The primary storage location for SevenTrends information is the
INETDB database. This file also contains the information needed
to run your I/NET system and any AMT events and alarms routed
to this workstation.
A large database can cause a delay every time I/NET Seven accesses
the information stored there. For best system performance, it is
best to keep INETDB as small as possible.
Database Size Limit

The maximum size for any I/NET Seven database, including the
transfer and archive databases, is 2GB. This file size is sufficiently
large that you should not encounter any storage problems.
However, larger facilities could potentially have many points gener-
ating a large number of trends, and thus a storage problem could
occur.

SevenTrends SevenTrends Data Management
Note: The 2GB limit is imposed by the Microsoft MSDE 2000 program
distributed with I/NET Seven. Facilities using SQL Server 2000
instead of MDSE 2000 are not affected by this limit.
There are two ways to manage the SevenTrends data in I/NET

Seven:
Transfer this moves SevenTrends samples to a separate
online database. Transferred samples are still available online
for viewing, editing, and report generation. Refer to Seven-
Trends Transfer Configuration Editor on page 15-25.
Archive this moves SevenTrends samples offline. Archived
samples are still available for report generation, but are no
longer available for viewing or editing from within I/NET
Seven. Archived samples can be used for backup purposes, as
they can be moved or copied to any computer, or onto remov-
able media such as a floppy disk. Refer to Archiving Seven-
Trends Data on page 15-28.
Sample Size
Each trend type uses a different number of bytes per sample when
stored on your hard drive. Use the information provided in
Table 15-4 to help you compute the amount of space you will be
using in your database file to store online (nonarchived) Seven-
Trends samples.
Table 15-4. Memory Requirements by Trend Type
Bytes per
Trend Type
Sample
Analog Sample 73
Consumption 73
Demand 77
Discrete Sample 78
Override 89
Runtime 71
To determine the space requirements for the samples, you must

know the number and type of trends defined in your system, and
how frequently you are gathering and storing samples.

SevenTrends Messages
SevenTrends generates a message whenever a transfer or archive is
attempted, and also warns against loss of data when the databases
reach full capacity. The messages and their meanings are shown in
Table 15-5.
Table 15-5. SevenTrends Messages
Message Description
The transfer of data from INetDB to ITrendDB

completed successfully. Includes the number of
Trnd Trnsf Cmplt
records transferred. If verification is enabled, this
message indicates that all data passed verification.
The transfer of data from INetDB to ITrendDB failed.
Trnd Trnsf Fail See the Message field in the AMT message for
details of the failure.
The archive of data from INetDB and/or ITrendDB
completed successfully. Includes the number of
Trnd Arch Cmplt
records archived. If verification is enabled, this
message indicates that all data passed verification.
The archive of data from INetDB and/or ITrend DB
Trnd Arch Fail failed. See the Message field in the AMT message
for details of the failure.
The SevenTrends transfer database has reached
90% of capacity. Samples should be archived to
prevent loss of data. This message will be generated
every time a sample is received when the database
is at 90% capacity or higher.
Trnd Strg 90% Note: This message is repeated every time new
data is added to the database and the
capacity is at or above 90%, until it reaches
100% capacity. To avoid data loss, you must
archive data before the database reaches
100% capacity.
The SevenTrends transfer database (ITrendDB)
reached 100% capacity. The oldest 10% of
Trnd Strg 100%
messages were deleted to bring the capacity back
down to 90%.

Table 15-5. SevenTrends Messages (Continued)
Message Description
The archive database has reached 90% capacity.

This message will be generated every time a sample
is received when the database is at 90% capacity or
higher.
Trnd Arch 90%
Note: This message is repeated every time new
data is added to the database and the
capacity is at or above 90%, until it reaches
100% capacity.
The SevenTrends archive database reached 100%
Trnd Arch 100% capacity. The oldest 10% of messages were deleted
to bring the capacity back down to 90%.
SevenTrends Transfer Configuration Editor

The SevenTrends Transfer Configuration editor is used to define
when to transfer the SevenTrends samples from INETDB to the
transfer database (ITrendDB), and which records to transfer. The
transferred records remain online, and are available for viewing
and editing.
You can configure the system to transfer files automatically, or
perform a manual transfer at any time. The SevenTrends Transfer
Configuration editor is very similar in appearance and function to
the AMT Archive Configuration editor (see CCTV in Chapter 3,
System Messages).
Transfer Settings
The fields in this section specify the type of transfers you will be
performing.
Enable auto transferring Indicate whether you wish to use the
automatic transfer option. This will transfer samples when the
storage limits are reached (see Primary Online Storage on page
15-26) without operator intervention.
Verify transfer contents Indicate whether you wish the system
to verify the number of samples transferred. This features only veri-
fies that the correct number of records were transferred; it does not
verify sample data.

Distribution Parameters
The fields in this section specify the message routing for Seven-
Trends information. This refers only to messages generated by the
SevenTrends transfer and archive functions (see SevenTrends
Messages on page 15-24). This editor does not affect whether
SevenTrends samples are received at this workstation.
Distribution group Select the distribution group for transfer
messages.
Distribution mask Select the desired mask settings for transfer
messages.
Alarm priority The priority for sending information from this
extension editor. The options are None, Routine, Priority, and Crit-
ical. Refer to Priorities in Chapter 3, System Messages.
Primary Online Storage
This section allows you to select the method you wish to use to
determine which records should be transferred. After selecting the
method, enter the threshold level for that method.
In all cases, the older samples are transferred, leaving the most
recent samples in INETDB.
Note: The threshold level you enter defines the minimum samples that
should remain in INETDB; that is, it defines the samples that will
not be transferred.
Limit by date This option will transfer all samples older than
the specified number of days. Each day begins at midnight, and
includes the current day. For example, if you enter a value of 1, all
records prior to the current day will be transferred.
Limit by record count This option will transfer all but the spec-
ified number of records. The level is set in thousands, and the
system always rounds down, so the actual number of samples left
in INETDB can be more than that amount, but will never be less.
For example, if this field is set to 30 (thirty thousand samples) and
there are 46,123 samples in INETDB at the time the transfer starts,
then 16,000 records will be transferred and 30,123 will remain in
INETDB.

Limit by physical size This option directly assesses the memory

space used by the SevenTrends samples only. If the SevenTrends
portion of the INETDB database exceeds this level, enough samples
will be transferred to reduce the memory space used below the
selected threshold. For example, if this level is set to 16MB and the
SevenTrends samples take up 20MB, then approximately 4MB of
samples will be transferred. The size of the transferred samples may
not be exactly 4MB in this example, because different sample types
require different memory space (see Sample Size on page 15-23).
As with the Limit by record count parameter, the system will
always round down so that the samples in INETDB do not fall
below the entry in this field.
Transfer Schedule
Use this section to specify how often records should be transferred.
This section is only active if the Enable auto transferring
checkbox is activated.
Occurs Select either Daily or Weekly. In this case, Daily does
not necessarily mean every day; it means that transfers will occur a
set number of days apart.
Every Select the number of days or weeks (1366) between
automatic transfers. If you selected a weekly transfer, select the day
of the week for the automatic transfer.
This feature allows you the flexibility to create any transfer schedule
you like. For example, if you select Weekly, enter 2 in this field and
click Tuesday and Saturday, the transfer will occur every other
week, on both Tuesday and Saturday of that week.
Occurs at Select the time you would like the transfer to start.
(The screen currently says Occurs once at, but I have asked Jay to
remove once to avoid confusion.)
Note: If the system is busy, it is possible that the transfer will not start at
precisely the time specified.
Buttons
OK Accepts any changes and closes the editor.

Cancel Closes the editor, discarding any unapplied changes. If

you selected the Apply button after making changes, those changes
are not discarded.
Apply Saves the current changes without closing the editor.
This button is disabled if no changes have been made.
Transfer Now Begins a manual transfer. This button is disabled
if there are changes in the editor which have not yet been applied.
The transfer is limited by the parameter selected in Online Trend
Storage: depending on the settings and the time since the last
transfer, it is possible that no records will be available for transfer.
Note: Before transferring for the first time, you must select either OK or
Apply to accept the default settings (or your own) to enable the
Transfer Now button. This first setting is necessary to create the
transfer database.
Archiving SevenTrends Data

The archive feature allows you to retain older information offline,
enabling you to store data indefinitely. Archived data may be used
in reports, but cannot be viewed online through I/NET Seven.
I/NET Seven does not connect to the archive database, and thus it
can be moved out of the I/NET directory to a different directory,
to a network drive, or to portable media such as a ZIP or tape drive
for offsite storage.
Note: Archiving is available only for SevenTrends definitions that have a

transient duration of zero (0), indicating no transient duration. If the
trend definition includes a transient duration greater than zero, those
samples are discarded after the specified number of days. Even if you
archive daily and have a transient duration of 10 days, those samples
will not be archived. If you wish to keep samples indefinitely, make
sure the transient duration for the SevenTrends definition is set to
zero.
Archiving is a manual task, and does not occur automatically.

When you archive SevenTrends samples, the following parameters
are available:

End date the ending date for archived samples. The default
value is the last day of the previous year.
End time the ending time for archived samples. The
default value is one second before midnight (23:59:59) of the
selected day.
These parameters are inclusive: all samples with a date and time up
to and including the selected parameters will be moved to the
archive database. The samples are removed from the online data-
bases (INETDB and/or ITrendDB) and are no longer available for
viewing, editing or deletion from within the I/NET Seven editors.
The archive database will be stored in the location specified as the
Archive directory in I/NETs Configure program. Refer to
TCON298, I/NET Seven Getting Started, for more information on
setting directories.
Each archive is stored in a separate file. The file naming convention
is as follows:
TARCH_YYYYMMDDMPMSS.mdf (I/NET Seven 2.12 or earlier)
OR
TARCH_YYYYMMDDMPMSS.ARC (I/NET Seven 2.13 or later)
where:
TARCH_ = indicates a trend sample archive
YYYY = four-digit year
MM = two-digit month (0112; 01 = January, 12 = December)
DD = day of month (0131)
MPM = four-digit minutes past midnight (00001339)
SS = two-digit seconds (0059)
.mdf (I/NET Seven 2.12 or earlier) = indicates a file in
Microsoft standard database format.
OR
.ARC (I/NET Seven 2.13 or later) = indicates a file in SQL
database format.


APPENDIX
A
8
DCU Control Hierarchy
I/NET provides you with a number of automatic control programs

that you may attach to the different controller points. The
different automatic control programs relate to one another in a
hierarchy of control. When two or more control programs affect
the same point, only one has priority. Knowing which control
programs take precedence over others helps you avoid an unex-
pected control action, and at the same time understand why a
certain control action occurs.
The following pages contain figures that address the hierarchy of
control for output points (the only points that are controlled) in
the controllers. Refer to the key of abbreviations when reading the
figures to determine which automatic control program or point
type is referenced in the diagram. Read the diagram from left to
right. An automatic control program located to the right of another
will make the final control decision; i.e., it has the higher priority.
Automatic control programs with the same ranking are located on
top of each other in the diagrams.
AHU Unitary Controller Air Handling Unit Extension
AIC Access Initiated Control
AO Analog Output
ASC MR-AHU or MR-VAV Control
CP Calculated Point
DC Discrete Control
DDC Direct Digital Control (DCU or MR)
DMD Demand Control
DO Discrete Output
EL Elevator Control (Floor Relays)
I/NET Seven Technical Reference Guide A-1

EV Event
EVW/L Event with Lock
GO Digital Output
HHCM Manual Command from Hand Held Console
HPMP Unitary Controller Heat Pump Extension
HWM Manual Command from Host Workstation
LC Lighting Control (Circuits)
OBDI Override Billing: Discrete Input
OBNON Override Billing: Non-Billable
OVB Override Billing: Billable
TC Temperature Control
TS Time Scheduling
UC-FLT Unitary Controller FLT Extension
UC-PID Unitary Controller PID Extension
VAV Unitary Controller VAV Extension
Note: Not all editors are available in all DCU types.
A-2 I/NET Seven Technical Reference Guide

Figure A-1. DO and DC Points: 7700, 7716, 7718, 7740, 7750,

7756, 7780, and 7791 Controllers

Figure A-2. AO and GO Points: 7700, 7716, 7718, 7740, 7750,

7756, 7780, and 7791 Controllers

DMD**
TC* CP***
OB
B
VAV **** EV HW
M
TS OB EV DO/DC
NON W/L
AHU **** UC-PID**** HHC

M
OB
DI
HPMP **** UC-FLT****
AIC
Priority
lowest highest
* - command is issued every minute change

** - command is issued every 1/10 demand interval
*** - command is issued every point scan
**** - command is issued every scan of the parent point
Figure A-3. DO and DC Points: 7760 UCI and 72xx UC

CP***
VAV****
EV HWM
EV
AHU**** W/L AO
UC-PID**** HHC
M
HPMP****
AIC
Priority
lowest highest
*** - command is issued every point scan

**** - command is issued every scan of the parent point
Figure A-4. AO Points: 7760 UCI and 72xx UC

Figure A-5. DO and DC Points: 7792 MRI, 7793 MCI, 7798

I/SITE LAN, and MR-AHU or MR-VAV

Figure A-6. AO Points: 7792 MRI, 7793 MCI, 7798 I/SITE

LAN, and MR-AHU or MR-VAV

2
B
APPENDIX
12 11 10 9 8 7 6 5 4 3 2 1 24 23 22 21 20 19 18 17 16 15 14 13 12
I/NET Seven Technical Reference Guide

Time Zone Map
International Date Line

Regions are half time zones
B-1
APPENDIX
C
14
Controller Point Addressing
Point Addresses by Controller

Table C-1 gives point address information for the various TAC
controllers. For additional information, please refer to the indi-
vidual User or Installation Guide(s) for the specific controller(s) in
use at your facility.
Table C-1. Controller Point Addresses
Hardware Point Addresses

Controller
Point or Board Type Range (PPBB)
DI / PI base unit 2800 2807

DI / PI expansion slot 3 2900 2907
7700 Distributed Control DO / PWM base unit 0000 1500

Unit (DCU) TCON095 DO / PWM expansion slot 1 1600 2300
AI base unit 0000 1500
AI expansion slot 4 1600 2700
AO expansion slot 2 2400 2700
AO expansion slot 3 2800 3100
I/NET Seven Technical Reference Guide C-1

Table C-1. Controller Point Addresses (Continued)

Controller
Universal input (UI) base unit 0000 0007
DO base unit 0000 0007
UI / DO expansion board:Inputs 0100 0107
Outputs 0100 0107
7716 Process Control UI/AO expansion board:Inputs 0100 0107

Unit (PCU) TCON096 Outputs 3100 3103
RTD expansion board 0100 0107
AO expansion board 3100 3103
Base HOA switch feedback BB 08 & 09 on points 00 07
Expansion HOA switch feedback BB 08 & 09 on points 08 15
Universal Input base unit 0000 0007
DO / PWM base unit 0000 0007
DO / PWM expansion board 0100 0107
7718 Process Control 0100 0107
AI / DI / PI expansion board
Unit (PCU) TCON106 0200 0207
AO base unit 3100 3107
Base HOA switch feedback BB 08 & 09 on points 00 07
Expansion HOA switch feedback BB 08 & 09 on points 08 15
0000 0007
Universal inputs
0100 0103
I/STAT 0104 0105
7728 I/SITE TCON114 Analog outputs 3100 3103
0000 0007
Triac outputs
0100 0101
Auxiliary outputs 0102 0103
DO / PWM base unit 0000 1500
7740 Distributed Control
AI base unit 0000 1500
Unit (DCU) TCON097
DI / PI base unit 2800 2807
DI (optional interface module) 0000 0707
7750 Building Manager The 7750 is a special case in that it contains 32 zones for a one-station
TCON098 device and 64 zones for a two-station device. Each zone is an internal
(software) DO point with bit offset 00. All output points on the 7750 are
internal or indirect.
C-2 I/NET Seven Technical Reference Guide


Controller
DI / AI / PI upper motherboard 0000 0007
0100 0107
DI / AI / PI lower I/O board 0200 0207
0300 0307
7756 Process Control DO / PWM upper motherboard 0000 0007
Unit (PCU) TCON127
DO / PWM lower I/O board 0100 0107
AO lower I/O board 3100 3107
HOA switch feedback upper motherboard BB 08 & 09 on points 00 07
HOA switch feedback lower I/O board BB 08 & 09 on points 08 15
7760 Unitary Control DI / AI (32 UCs) 0000 3107
Interface (UCI)
TCON099 DO / PWM (32 UCs) 0000 3107
DI / AI / PI 0000 3109
7771 MODBUS DO / PWM 0000 3109
TCON102
This controller can have up to 640 resident hardware or software points
per station address.
Base unit inputs 0000 0007
Expansion board #1 inputs 0100 0107
Expansion board #2 inputs 0200 0207
7780 Distributed Lighting Expansion board #3 inputs 0300 0307
Control Unit (DLCU)
TCON100 Matrix Board #1 outputs 0000 0107
Matrix Board #2 outputs 0200 0307
7791: 1 channel with up to 32 devices (DIO, DIU, DPU, SCU)
7792: 2 channels with up to 32 devices each (MR, ASC)
7790 LIU TCON109 7793: 2 channels with up to 32 devices each (MR, ASC, DIO, DIU, DPU,
SCU)
7797: depends on the ICI it is connected to and the devices the ICI is
supporting
7798 I/SITE LAN
1 channel of up to 32 devices (MR, ASC, DIO, DIU, DPU, SCU)
TCON138


Controller
DI / DA (sense and release inputs) 00 03
7900 and 7910A Door Form-C relay outputs 00 03

Processing Unit (DPU) DA (tamper switch input) 08
TCON115, TCON116
If addresses 08 and 09 are configured as door points, then DO addresses
00 and 01 are not available for use as internal or external points.
AI / DI / DA (sense and release inputs) 00 07
Form-C relay outputs 00 07
7920 Door Processing
Unit (DPU) TCON117 DA (tamper switch & battery status inputs) 08 09
If output addresses 08 and 09 are configured as door points, then DO
addresses 0003 are not available for use as internal or external points.
DI / DA inputs (up to 16 total) 00 07 in each station
7930 Door Input Unit
DA (tamper switch & battery status inputs) 08 09 in first station only
(DIU) TCON124
Note: This unit supports one or two station addresses.
DI / DA inputs 00 07
7940 Door Input/Output
Relay outputs 00 07
(DIO) TCON125
DA (tamper switch & battery status inputs) 08 09
DO / PWM 00 04
MR55 Series Controllers DI / Thermistor 00 03

(MR) TCON130 CFM / LPS transducer (MR55X only) 04
I/STAT or Thermistor 07
Universal inputs 00 06
MR88 Micro Regulator
DO (low voltage triac) 00 07
(MR) TCON126
I/STAT 07
Universal inputs 00 06
MR88R Micro Regulator
Form-C relay outputs 00 07
(MR) TCON126
I/STAT 07
AI 00, 01
DO (high voltage triac) 00 02
MR123-032MB Micro
Regulator (MR) DI 02 04
TCON113
AO 03, 04
I/STAT 07


Controller
DO (high voltage triac) 00
MR123-210MB Micro AI 00, 01

TCON113 DO (low voltage triac) 03, 04
I/STAT 07
AI 00, 01
MR123-400MB Micro DI 02 04
Regulator (MR)
TCON113 DO (low voltage triac) 03 06
I/STAT 07
AI 00, 01
DO (high voltage triac) 00 02
MR123-430MB Micro
TCON113
I/STAT 07
0000 0007
MR160 Micro Regulator Universal inputs
0100 0106
(MR) TCON126
I/STAT 0107
MR632 Micro Regulator Universal inputs 00 04
(MR) TCON126 AO 03, 04
I/STAT 07
MR-AHU Application AI / DI 00 03
Specific Controller (ASC)
TCON153 DO / PWM (low voltage triac) 00 05
MR-VAV-AX Application AI / DI 00 03
Specific Controller (ASC) DO / PWM (low voltage triac) 00 02
TCON147 CFM velocity sensor input 09
MR-VAV-X1 Application AI / DI 00 03
TCON155 CFM velocity sensor inputs 08 09


Controller
AI / DI 00 03
MR-VAV-X2 Application
TCON164
CFM velocity sensor input 09
7251 UNIV-UC and 7270 Universal inputs 00 07
UNIV-UC II Unitary
Controllers (UC) Discrete outputs 00 07
TCON069
Analog inputs 00 03
721x VAV-UC Unitary Discrete inputs 04 05
Controller (UC)
TCON069 CFM velocity sensor input 06
Discrete outputs 02 07
AI / DI 00 05
726x VAV-UC II Unitary
Controller (UC) CFM velocity sensor inputs 06 07
TCON069
Discrete outputs 02 07
Point Capacity by Controller

Table C-2 gives point capacity information for the various TAC
controllers. For additional information, please refer to the indi-
vidual User or Installation Guide(s) for the specific controller(s) in
use at your facility.
The Total Software Points refers to points that are not external
hardware points. An internal point may be used in place of any
external (hardware) point.
Note: The total points possible listed for each controller are theoretical
maximums. Typically you will never need or use this many points in
a single controller. The actual capacity of a controller depends on the
point types and the extensions you associate with those points. If you
use analog point types or multiple extensions per point, the controller
capacity drops. Certain extensions require more memory than others,

and limit the maximum point capacity accordingly. Please contact

TAC customer support if you feel your system configuration requires
a number of points close to the theoretical maximum for a controller.
Table C-2. Controller Point Capacities

Controller
Point Type Max.
Discrete / PWM outputs 24

Analog inputs 28
Analog outputs 8
Discrete / PWM inputs 32
7700 Distributed Control
Unit (DCU) TCON095 Total hardware points 76
Total software points 564
Total possible points 640
The 7700 is expandable up to the maximum number of
inputs and outputs described here.
Universal (analog or discrete) inputs 16
7716 Process Control Unit Analog outputs (010 V or 420 mA) 4

(PCU) TCON096 Total hardware points 32
Universal (analog or discrete) inputs 24
7718 Process Control Unit Analog 0 10 V outputs 8

(PCU) TCON106 Total hardware points 40

Table C-2. Controller Point Capacities (Continued)

Controller
Point Type Max.
Universal (analog, discrete, or pulse) inputs 12
I/STAT inputs 2
Analog outputs (0 10 V) 4
Low voltage triac outputs 10
7728 I/SITE TCON114
Auxiliary outputs 2
Total hardware points 30
Analog inputs 16
7740 Distributed Control Discrete / Pulse inputs 8
Unit (DCU) TCON097 Total hardware points 40
Discrete inputs 64
7750 Building Manager Total hardware points 64

TCON098 Total software points 576
12-bit Analog / Discrete / Pulse inputs 8
PWM / Discrete outputs 8
16-bit Analog / Discrete / Pulse inputs 24
7756 Process Control Unit Analog outputs 8

(PCU) TCON127 Triac PWM / Discrete outputs 8
Discrete / Analog inputs 256
7760 Unitary Control Analog (PWM) / Discrete outputs 256

Interface (UCI) Total hardware points 512


Controller
Point Type Max.
Analog / Discrete inputs 320
7771 MODBUS
Analog / Discrete outputs 320
TCON102
Discrete inputs 32
7780 Discrete Lighting Discrete outputs (RR7 Lighting Control Relays) 64

Control Unit (DLCU) Total hardware points 96
The point capacity of the 7790 series varies according to
the attached devices. The point capacity is governed by
7790 LIU TCON109
the system limit of 640 possible total points (including
hardware and software points) per channel.
The point capacity of the 7798 I/SITE LAN varies
7798 I/SITE LAN according to the attached devices. The point capacity is
TCON138 governed by the system limit of 640 possible total points
(including hardware and software points) per channel.
Discrete / Alarm inputs (door sense and release) 4
Tamper alarm input 1
7900 and 7910A Door Discrete outputs 4
Processing Unit (DPU)
TCON115, TCON116 Total hardware points 9
Discrete / Alarm inputs 8
Tamper alarm and battery status inputs 2
7920 Door Processing Unit Discrete outputs 8

(DPU) TCON117 Total hardware points 18


Controller
Point Type Max.
Discrete / Alarm inputs (2 station) 16

7930 Door Input Unit (DIU)
TCON124
Total possible points (2 station) 40
Discrete inputs 8
7940 Door Input/Output Form-C relay outputs 8

(DIO) TCON125 Total hardware points 18
I/STAT or Thermistor input 1
DI or Thermistor input 4
DO / PWM output 5
MR55 Series Micro
Regulators (MR) CFM / LPS transducer (MR55X only) 1
TCON160
I/STAT input 1
Universal inputs 7
MR88 Micro Regulator Low voltage triac outputs 8

(MR) TCON126 Total hardware points 16
I/STAT input 1
Universal inputs 7
MR88R Micro Regulator Relay outputs 8

(MR) TCON126 Total hardware points 16


Controller
Point Type Max.
I/STAT input 1
Analog inputs (0 10 V) 2
Discrete inputs 3
MR123-032MB Micro Discrete (high voltage triac) outputs 3
Regulator (MR)
TCON113 Analog outputs (0 10 V) 2
I/STAT input 1
Analog inputs (010 V) 2
Discrete inputs 3
MR123-210MB Micro Low voltage triac outputs 2
Regulator (MR)
TCON113 High voltage triac output 1
I/STAT input 1
Analog inputs 2
MR123-400MB Micro Discrete inputs 3

Regulator (MR) Discrete (low voltage triac) outputs 4
TCON113 Total hardware points 10
I/STAT input 1
Analog inputs (010 V) 2
Discrete inputs 3
MR123-430MB Micro Discrete (low voltage triac) outputs 4
Regulator (MR)
TCON113 Discrete (high voltage triac) outputs 3


Controller
Point Type Max.
I/STAT input 1
Universal inputs 15
(MR) TCON126
Total software points (input points only) 4
Total possible points (input points only) 20
I/STAT input 1
Universal inputs 5
Low voltage triac outputs 3
Analog outputs (0 10 V) 2
(MR) TCON126
Analog or discrete input 4
Analog or discrete output 6
MR-AHU Application
Specific Controller (ASC) Total hardware points 10
TCON153
Analog input 4
MR-VAV-AX Application CFM input 1
Analog input 4
MR-VAV-X1 Application CFM input 1


Controller
Point Type Max.
Analog input 4
MR-VAV-X2 Application CFM input 2
Universal inputs 8
Discrete outputs 8
7251 UNIV-UC and 7270 Total hardware points 16
UNIV-UC II Unitary
Controllers (UC) Total software points 0
TCON069 Note: You may have internal software points in UNIV-
UCs, but only at the expense of an external point.
Analog inputs 4
Discrete inputs 2
CFM velocity sensor input 1
721x VAV-UC Unitary
Controller (UC) Discrete outputs 6
TCON069
Analog or discrete inputs 6
CFM velocity sensor inputs 2
726x VAV-UC II Unitary Discrete outputs 6
Controller (UC)

26
Glossary
Address Structure
A The structure of the address defining
the link, station, point, bit offset, and
Action Messages point type on the I/NET controller
LAN shown as four pairs of numbers
These are predefined instructions or
and two letters describing the point
information automatically routed to
address: LLSSPPBB PT (link, station,
specific host stations for printing or
point, bit offset, and point type).
storing. They provide additional
information when a point transitions AHU-UC
into or out of an alarm state or a spec-
An Air Handling Unit Unitary
ified state or value.
Controller is a cost-efficient TAC
Access Control controller containing a reduced point
count and typically controlling one
A part of the I/NET system that
packaged Air Handling Unit.
controls, monitors and restricts access
using Door Processor Units. Air Handling Unit (AHU)
Access Initiated Control Equipment that mixes air of various
temperatures to produce cooling or
An I/NET function that lets you
heating.
initiate a control action in response to
an access transaction for a selected Alarms
tenant number, and one or more
Conditions that meet or exceed user-
key/card numbers.
defined limits. I/NET indicates alarm
Adaptive Tuning conditions, return-to-normal condi-
tions, and provides a means to
This is the DDC process where I/NET
acknowledge and purge these alarms.
successively changes the output to a
I/NET signals alarms with an audible
device and observes the resultant
tone, which may be turned off, and
changes to the process variables in
with a visual message displayed in the
order to recalculate the P, I, and D
top left corner of your screen.
module parameters.
I/NET Seven Technical Reference Guide Glossary-1

Alarm Inhibit/Enable Anti-passback Zone
Alarm Inhibit/Enable Alternate Path

A function of the I/NET software that A communication path defined in the
lets you program the system to ignore host stations configuration file
nuisance alarms when a particular (S7000DRV.CNF) to provide backup
piece of equipment is turned off. communications if the primary path
is interrupted.
Algorithm
A predefined equation or set of Analog Output (AO)
instructions to solve a problem in a set A point type which converts counts or
number of steps. pulsed transmissions to analog
signals. On certain controllers, you
All Lights ON/OFF can select true AO points. All control-
This is a control parameter you define lers provide PWM (pulse width
for the 7780 DLCU in the DCU modulated) points. A true AO point
configuration/status editor. Acti- uses a digital-to-analog converter to
vating this option enables input convert counts to analog signals and
addresses 0000 and 0001 to be used to works faster than a PWM point.
control all relays to an energized (all However, PWM points are less expen-
lights on) or deenergized (all lights sive.
off) state.
Analog Points
Alphanumeric Analog Inputs sense variable parame-
Alphabetic-numeric. Indicates data ters and convert the input from
consisting of numbers and letters. current or voltage to engineering
units. Analog outputs convert an
Analog Data analog software value expressed in
Continuously varying (versus engineering units to current or
discrete) data that is described by voltage, which is transmitted to a
engineering terminology such as device.
temperature, humidity, voltage, or
flow. Anti-passback Zone
A feature of access control. When a
Analog Input (AI) user enters a zone, all other doors in
Input point that receives a changing the same zone will be flagged to indi-
(as opposed to a constant) value. cate the users presence. Thereafter,
These differ from DI points in that the user must use an exit reader in this
they sense a value (such as 72 degrees) zone before the next entry attempt by
rather than a binary condition of one that users key/card will be accepted.
of two possible states.
Glossary-2 I/NET Seven Technical Reference Guide

APB Reset Background Running
APB Reset Authorization Levels

A system action that resets anti-pass- Defined levels of passwords that let
back memory for a specific door. Any you access different editors. Level 1
individual who previously entered the grants display-only access. Level 2 lets
zone assigned to this door, but did not users display controller data, issue
use his key/card when exiting, can commands, and acknowledge alarms.
now successfully reenter the same Level 3 lets users display data, issue
zone. commands, acknowledge alarms, and
edit all functions except the password
Application Specific Controller (ASC) function. Level 4 allows users access to
A special type of micro regulator all of the above and edit passwords.
(MR), designed for a specific purpose. One user must always have a level 4
ASCs are designed to reduce total password.
installation cost through pre-engi-
neered control algorithms. Automatic Tuning
See also: MR-AHU, MR-VAV A DDC process where the software
automatically recalculates a modules
Arithmetic Operator P, I, and D parameters when a variable
An operator performing addition, exceeds preset limits.
subtraction, multiplication, or divi-
sion. Automatic Report Generation
A function of SevenTrends where a
ASCII report is compiled from a set of previ-
American Standard Code for Infor- ously defined criteria, and printed
mation Interchange. A standard according to a specific schedule.
seven-bit code usually with a parity bit
(to make eight bits per character).
This is a standard established to
achieve compatibility between
different equipment. B
Audit Trail Message Background Running
A message containing the date and The ability of a program to continue
time an edit was performed, and the to function while another program is
initials of the person who did the edit. running. In this manual, background
running specifically refers to the
drivers ability to route I/NET data
while other programs are running.
See also: Driver

Backup Calculations
Backup Boolean
The action of creating a duplicate set A type of algebra relating to logical
of current files on floppy diskettes, concepts incorporating operators such
hard disk, or tape. You normally as AND, OR, and NOR. A boolean
create backups to ensure that a cata- function combines values that are
strophic loss of files or host computer either true or false (binary 1 or 0) with
equipment will not wipe out the logical operators.
current operating files.
Building Manager
Backup Station A specific type of DCU. The 7750
A workstation that is fully dedicated Building Manager provides an easy
to backup host workstation data files. way to override normal day-to-day
schedules for various pieces of equip-
Baud ment within a facility, such as lighting
A unit of measurement indicating the and environmental controls. The
number of bits that can be transmitted override totals are accumulated for
each second. For example, 1200 baud each zone, and the totals are available
indicates that the device can transmit for generating energy-usage reports
1200 bits of information per second. and billing.
Binary Byte
This term refers to the base 2 number A group of bits forming a unit of
system that uses only the digits 1 and storage in a computer. A byte is
0. In this system, a binary number is usually eight bits long and is usually
the sum of successive powers of two. represented by one alphanumeric
For example, the binary number 1011 character.
is equal to the decimal number 11.
(1 23) + (0 22) + (1 21) + (1 20)
= (8) + (0) + (2) + (1) = (11). This
term also refers to a discrete situation
where only two conditions can exist C
(on or off, open or closed, alarm or
Calculations
normal, etc.).
Calculations are performed either
Bit through the calculation extension
This is a digit in the binary system editor or the calculation module (MR
represented by 0 or 1. A bit is the only). Calculations let you manipulate
smallest storage unit in a computer. data to control equipment or produce
reports.

Calculation Module (MR only) Controller
Calculation Module (MR only) Configure

A DDC module allowed in micro The configuration process establishes
regulators. This module functions physical and software parameters.
similarly to calculations added to a
point through the calculation exten- Constant
sion editor. An operand in a calculation that is
always a specific number. A constant
Cell Number can be a value (72 degrees) or a state
An index number for grouping Seven- (0 or 1). For example, if the value is in
Trends and system message records in minutes and you wish to convert it
the I/NET Seven windows and on into hours, you would divide the value
reports. by a constant of 60.
Circuit Consumption
A single point in the 7780 DLCU A point extension editor and function
controller. This point may control a that directs the accumulated value of a
single source (lamp), or several PI point to a SevenTrends table.
sources that have been daisy-chained Consumption monitors the amount
together into the same controller of a consumable resource that is being
point (such as a specific floor or physically measured by the system.
tenant space within a facility).
Control Descriptions and Commands
Closed Loop This is a station parameter editor.
A type of process control where a Here you define pairs of control
computer can respond to feedback descriptions such as start and stop, on
from a sensor or control equipment and off, open and closed, etc. You
without human intervention. For must correlate each pair with a
example, the computer could lower or specific output command (0 or 1).
raise the temperature in a room if a
sensor indicates the temperature is too Control Parameters
warm or too cold. Parameters you define to help you
control a DCU. These parameters
Configuration Editors include date, time, distribution
These are I/NET editors that let you groups, masking, and priority.
set the parameters of the host station,
Taps, DCUs, and other devices while Controller
online with I/NET. A general term for DCUs (distributed
control units), PCUs (process control
units), DLCUs (distributed lighting

Controller LAN Demand Control
control units), DPIs (door processor Cursor

interfaces), MCIs (micro controller A position indicator on your screen. It
interfaces), MRIs (micro regulator moves as you type and usually blinks,
interfaces), I/SITE I/O or I/SITE LAN. indicating your current location on
Controller is often used interchange- the screen. Typically, you need to
ably with DCU, which has a specific highlight an item on your screen with
meaning but is also used as general the cursor before you can select it.
term for PCUs, DLCUs, ICIs, UCIs,
DPIs, MRIs, MCIs, etc.
Controller LAN
A local area network that connects D
two or more DCUs. These DCUs can
then exchange point data. Database
A collection of data organized for
Conversion Coefficients rapid search and retrieval by a
This is a station parameter editor. computer. I/NET uses a database to
Conversion coefficients are mathe- organize and store data collected by
matical constants a controller uses to the DCUs.
convert analog input/outputs from
the digital value (counts) used by the DCU
microprocessor to analog display Distributed Control Unit. A micro-
values. Conversion coefficients are processor-based controller used as a
also used to convert digital values part of the I/NET system. The DCU
(counts) from the microprocessor into connects directly to the controller
analog outputs which are then used by LAN and works in conjunction with
field interface devices. other controllers and workstations on
the LAN. The DCU, depending on the
CRT model, is capable of monitoring and
Cathode Ray Tube. This term usually controlling up to 640 addressable
refers to the screen on your computer. points while providing DDC, energy
management functions, and process
Current Loop control.
A serial transmission standard in
which a pair of wires connecting the Demand Control
receiving and sending devices Use this editor to monitor electrical
transmit binary 0 when no current power consumption, and calcu-
flows and binary 1 when current late/predict electrical demand. You
flows. can maintain a daily or monthly
consumption total. Demand control

Diagnostics Discrete Output Points
enables demand shedding of electrical Discrete Control (DC)

power to output points, and the resto- This point type is always used with a
ration of the power when demand Discrete Monitor (DM) feedback
levels drop. point. As a pair, they control devices
that would otherwise be controlled by
Diagnostics
an ordinary DO point but are consid-
A program that tests the system for ered critical enough to warrant a
faults. DM/DC combination.
Digital Input (GI) Discrete Monitor (DM)
A specialized DI point whose value is This point type is always used with a
determined by the addition of the Discrete Control (DC) point. As a
eight inputs in a binary fashion. This pair, they control devices that would
point type requires eight consecutive otherwise be controlled by an ordi-
point addresses. nary DO point but are considered
critical enough to warrant a DM/DC
Digital Output (GO) combination.
A specialized DO point in which the
eight outputs are energized in a binary Discrete Input Points
fashion. This point type requires eight Discrete inputs sense the state of a
consecutive point addresses. contact closure. A discrete input (DI)
point shows only the state (on/off,
Direct Digital Control (DDC) open/closed, etc.) of a device. Discrete
A system that measures a variable, alarm (DA) points have a normal and
compares the variable with a known an alarm state. The alarm state
value to determine the error, processes produces an alarm to warn the oper-
the error using a specific software ator. The discrete monitor (DM)
algorithm, and then produces an point provides positive feedback for
output to modify the controlled vari- discrete control (DC) points.
able.
Discrete Output Points
Discrete Alarm (DA) Discrete outputs control the state of a
Use this point type when you want to contact closure. Discrete output
be aware of an alarm condition sensed points include two point types,
by a contact opening/closing. It is a discrete control (DC) and discrete
specialized DI point. output (DO). DC points are used with
DM points, providing a positive check
on two associated states. DO points

Dispatch Message DOTL Alarm
are used to control devices that dont Door

require the additional feedback A point in a DPU with bit offset 08 or
attributes of the DC/DM pair. 09, and a door extension defined.
These points may identify either a
Dispatch Message
door or elevator within the I/NET
An operator-entered message that is Access Control system.
appended to an alarm notification on
both the alarm summary and message Door Sense Switch
summary screens. This function A normally open or normally closed
allows the operator(s) to place notes switch (DI point) that monitors the
on specific alarms, such as Handled door position (open or closed)
by Operator #10 or Spurious connected to a DPU.
alarm.
Door Release Switch
Distributed Network
A normally open or normally closed
A network where communication switch (DI point) that allows access
between various terminals and through a DPU-controlled door when
computers may take place through its state changes.
alternative communication lines.
DOS Error Codes
Distribution Group
A number displayed by the system
Part of message masking, a filtering when it encounters a DOS-related
system used to route messages, alarms, operating error.
and data to system workstations.
I/NET has four distribution groups, DOS
each with eight mask positions, for a
Disk Operating System. DOS is the
total of 32 possible mask positions.
software that lets you use English
Both the distribution group and at
language commands telling your
least one active mask position must
workstation what you want it to do.
match for the message to be received
DOS also contains instructions for the
and stored at a host workstation.
workstation on how to access disk
See also: Masking
devices that store data.
DLCU DOTL Alarm
Distributed Lighting Control Unit. A Door Open Too Long alarm. A DPU
specialized type of controller. The
door parameter that defines how long
7780 is a DLCU. The DLCU is specifi-
a door can remain open without
cally designed for lighting control. generating an alarm (07,200
seconds).

DPI Equation
DPI
Door Processor Interface. The 7791
provides a communications gateway
E
between the controller LAN and the Editor Line
DPUs. It passes information between
Line 1 of the display in I/NET 3.x
the host, controller, and subLANs.
versions. The first five characters are
You can attach up to 32 DPUs to one
reserved for the printer malfunction,
DPI. The DPI occupies a single
alarm, and message icons. The rest of
controller LAN address, effectively
the line displays the host date, time,
extending the span of controllers that
and day of week. The menu function
may be assigned to a single controller
or editor currently accessed is also
LAN.
displayed on this line.
DPU
Engineering Units
The Door Processor Unit. The DPU
A station parameters editor. These are
7900, 7910A, and 7920 are used to
units of measurement applied to
control access through doors, gates
analog input and accumulator point
and elevators. Door readers may be
values in system messages. DegF,
attached to them providing either
DegC, KW, and KWH are examples of
multiple entry readers or entry and
engineering units.
exit readers for anti-passback zones.
Elevator Reader
Driver
A reader that performs access control
Communications protocol between
in elevator cabs by controlling the
the computer terminals operating
floors that the elevator can access.
system and the I/NET software. The
driver receives transmissions EPROM
(messages, alarms, or data) from the
controller(s) and routes them to the Erasable Programmable Read-Only
appropriate place (system page Memory. A type of ROM that can be
display, alarm or message summary, erased (with ultraviolet light) and
SevenTrends database, etc.). The reprogrammed.
driver can run in background
Equation
(continue to route I/NET data while
other programs are running). An arithmetic statement containing at
least two expressions; e.g., 3 + 4, 6 2.

Event Definition Firmware
Event Definition (counts) used by the microprocessor

An editor that lets you specify certain to analog display values.
definable conditions which can trigger See also: Conversion Coefficients
actions, reports, or messages.
FCOPY
Event Sequences An I/NET program that allows the
An editor that lets you define copying of files between hosts on an
responses (control actions) to Ethernet LAN, or to different directo-
predefined conditions. ries on a single host workstation.
Expiration Date Field

The date that a visitors key/card Storage units that are grouped to form
access privileges stop. A visitor whose a record.
key/card number has passed the expi-
File Equalization
ration date is denied entry or exit
through access controlled areas. A special function used only in
Ethernet LAN systems. This function
Expiration Time ensures that certain critical I/NET files
The time that a visitors key/card are the same on every workstation.
access privileges stop. A visitor whose Files that are equalized include host
key/card number has passed the expi- passwords and several access control
ration time is denied entry or exit files. The file versions on the worksta-
through access controlled areas. tion designated as the filemaster
station are copied to all other worksta-
External Point tions on the Ethernet LAN.
A hardware input or output contact Filemaster
that can be wired to an outside source
or device. A host workstation designated in the
workstations configuration file
(S7000DRV.CNF) that keeps global
system information (password and
access editor information) available
F on an Ethernet LAN.
FB Coefficient Firmware
The factory setting for the b or inter- A program that is built into a circuit
cept conversion coefficient. This is one or EPROM. It cannot be altered like
of the parameters used to convert software or other programs.
analog inputs from the digital value

Firmware Status Hand-held Console (HHC)
Firmware Status
Display only field in DCU configura-
tion/status editor. This field lists the
G
revision number and the date of the Global Points
firmware installed in the controller.
A point defined through I/NET to
First Key Auto-unlock broadcast its data for sharing with
other points and DCUs. You can
A security function that can be
define a point as global to a controller
programmed in a DPU. This function
LAN, host LAN, or to the entire I/NET
keeps a door locked until a person
system.
uses a valid key/card in a door reader
after the doors mode schedule unlock Graphic Symbols
cycle has begun.
Symbols used on a system page repre-
Floating Module senting monitored and controlled
equipment.
A DDC module with two discrete
outputs (increase and decrease) used Graphics Printer
to drive bidirectional actuators with
A printer that is equipped to print
dual windings or coils.
graphics rather than just ASCII char-
Floor acters. This printer can print XY plots,
trend logs, and time-based plots.
An elevator extension parameter that
defines a DO and DI point for assign- Groups
ment with a DPI floor extension
Individuals can be collected in groups
point. This association of these DO
to simplify access control parameter
and DI points produces a closed loop,
definition and maintenance. The indi-
allowing the controller to identify an
viduals are assigned to specific groups
elevator floor selection with each
in the individuals editor.
successful key/card reader access.
FM Coefficient
The factory setting for the m or slope
conversion coefficient. This is one of
the parameters used to convert analog
H
inputs from the digital value (counts) Hand-held Console (HHC)
used by the microprocessor to analog A device that lets you communicate
display values. directly with a controller without
See also: Conversion Coefficients using a workstation. You use the HHC
to program addresses, baud rates, and

Heat Pump UC I/STAT
other parameters into a DCU before Host Station

connecting the DCU to the controller An operator station that runs the
LAN. The HHC is also useful for trou- I/NET host software, enabling it to
bleshooting. control, monitor, and program DCUs
and points.
Heat Pump UC
A unitary controller used to control
heat pumps.
Hi-Lo Module IK
A DDC module that compares up to
four input values and simultaneously I/DISC
provides individual high and low Small metal buttons that can be used
outputs that can be used as inputs to for access control in place of keys or
other modules. cards.
Home Page I/SITE I/O

A system page designated as the The 7728 I/SITE I/O is a satellite
primary system page for a point. You controller, designed to support local
can set up I/NET to make a reference operation without a local host work-
to a specific system page (designated station or HHC. It is functionally
as a points home page) when that similar to the 7716 and 7718 PCU
point goes into alarm. Typically, the controllers.
home page will contain necessary
information about the point. I/SITE LAN
The 7798 I/SITE LAN provides stand-
Host LAN alone controls for MRs, ASCs, and
A local area network connecting DPUs through a ViewCon, a local host
I/NET operator stations and link Taps. workstation, a modem to a remote
workstation, or an optional TAC
Host Address controller LAN.
The host address is the system address
(SS) of a particular operator station I/STAT
on an Ethernet or commercial LAN. Intelligent thermostat. An intelligent
This can be any number between 01 space sensor with local temperature
and 250. and setpoint display, override select,
and setpoint adjustment. The I/STAT
may be programmed from a host

ICI Key/Tag Translation
workstation, or locally through the Inactivity Timeout

keypad on the I/STAT. The period of inactivity allowed by the
See also: M/STAT, S/STAT system on a host before the host logs
the user off the system.
ICI
Industrial Controller Interface. This Indirect Point
type of controller allows data transfers An input or output point which
between I/NET and a specific third- resides in a different controller as an
party system (MODBUS, Trane, external or internal global point. If
McQuay, York Talk, etc.). you specify a point as global to the
LAN, link, or system, you can use the
Icons
point to control an indirect point in
A graphic symbol that represents a another controller. Indirect points act
point, point extension, DDC module, as receptacles for values or status
DDC line, or page. These icons are information broadcast from other
incorporated into graphic system controllers.
pages.
Individuals
Intercard Interval
Users assigned key/card numbers in
The acceptable interval between the I/NET Access Control system. The
consecutive card reads (0255 I/NET editor used to enter users into
seconds). This function can be used to the database.
control the flow of traffic or speed at
which access is granted. Key/Tag Translation
An editor populated when I/DISCs are
Internal Point
to be used with a DPU/reader. The
An input or output software point editor is responsible for translating
that is not connected to any hardware. actual I/DISC numbers to system
Internal points can hold a calculated compatible key numbers.
value, or may store information from
an extension editor (such as runtime).
Issue Level
Some cards and keys allow up to four
issues of the same key/card number. If
a different issue number is read on a
key/card than is recorded in the data-
base for it, access is denied.

LAN Lock
Lighting Control (LC)

L This is a point extension editor for
DO points associated with the 7780
LAN DLCU. It lets you define zones and
assign lighting circuits to the zones.
Local Area Network. A LAN is a series
of devices connected on a cable, that Line
pass data and files to each other
A special feature unique to DDC that
according to a standard communica-
allows the output of one DDC module
tions format.
to be used as input to other DDC
LAN Adapter modules. A line operates in a similar
fashion to an indirect point, but does
A LAN adapter is a special-purpose
not occupy a point address.
card that lets you connect an operator
station to the Ethernet LAN. Link
Leased Line I/NET allows a total of 100 communi-
cation links on the system. Each host
A permanent communication line
LAN can support up to 16 links. Use
providing full-time access between
an Ethernet LAN to connect host
two communication devices (modems
stations to each other.
or Taps).
Loading
LED
A display-only field in the DCU
Light Emitting Diode. A semicon-
configuration/status editor. This field
ductor diode that emits light when a
indicates how busy a controller is, and
current is passed through it. LEDs are
also shows the percentage of
typically used for displays on devices
controller LAN communication
such as the HHC.
attributable to the controller.
LED Polarity
Local
Cathode or Anode. This function in
Indicates devices that are directly
the door parameters editor deter-
connected to a DCU through on-
mines the polarity of the corre-
board input/outputs.
sponding LEDs on the key/card reader
and how they will function. Lock
A system action that inhibits entry
and exit through a door.

Lookup Tables Mask
Lookup Tables and at least one active mask position

A table in a DCU used to convert non- must match for the message to be
linear input points for use by the received and stored at a host worksta-
DCU. tion.
See also: Distribution Group, Mask
MCI
Micro Control Interface. The 7793
M MCI functions identically to the 7791
DPI and 7792 MRI, with the addition
M/STAT of the demand control editor. You can
Maintenance thermostat. A portable attach up to 64 MRs/ASCs/DPUs to
space sensor with local temperature one MCI. The MCI occupies two
and setpoint display, override select, consecutive controller LAN addresses,
and setpoint adjustment. The M/STAT extending the total controllers that
is a portable version of the I/STAT, may be assigned to a single controller
with a plug-in jack, and is functionally LAN.
identical to the I/STAT.
See also: I/STAT, S/STAT Megabit (Mb)
One million bits.
Manual Off
A system action that enables all auto- Megabyte (MB)
matic control commands to a DCU One million bytes.
resident point or door.
Mask
Manual On Part of message masking, a filtering
A system action that prohibits all system used to route messages, alarms,
automatic control commands to a and data to host workstations. I/NET
DCU resident point or door. has eight mask positions in each of
four distribution groups, for a total of
Masking 32 possible mask positions. Both the
A filtering system used to route distribution group and at least one
messages, alarms, and data to system active mask position must match for
workstations. Masking consists of the the message to be received and stored
distribution group and active mask at a host workstation.
positions. The pattern of active and See also: Masking
inactive mask positions in each distri-
bution group determines whether a
host workstation will accept the
message. Both the distribution group

Message Priority (DCU) Momentary Release
Message Priority (DCU) MODBUS Interface

This is one of the DCU control A hardware device that acts as a
parameters you define in the DCU gateway between I/NET and another
configuration/status editor. There are on-line system that uses MODBUS
three priority levels: routine, priority, protocol. The MODBUS Interface
and critical. None (shown as - in appears as a DCU on the I/NET
version 3.x) indicates no priority. The system and as a programmable logic
priority level you assign here refers to controller on the MODBUS system.
messages originating from the
controller. Modem
Modulator-Demodulator. A device
Message Priority (Point) that converts digital data output from
This is a point parameter common to one device, into analog data that can
all points. There are three alarm and be sent over communication lines.
message priority levels: routine Modems also convert analog data back
(alarms/messages originating from into digital data so that it can be
this point are only displayed or accepted by devices such as
printed on a local host workstation), computers.
priority (alarms/messages originating
from this point are displayed or Mode Schedule
printed on a local host, and stored for Standard time scheduling parameters
later distribution to a dial host work- for scheduling door related opera-
station), and critical (alarms/messages tions. The parameters include APB
originating from this point are Reset, Lock, Unlock and Secure.
displayed or printed on a local host
and immediately sent to a dial host Momentary Duration
workstation). Regardless of the This is a DO/DC point parameter.
priority, alarms and messages only Momentary duration is the number of
appear at terminals or printers with a seconds during which the start or stop
distribution group and active mask output contact/relay is energized
position that match the distribution when the appropriate command is
group and active mask(s) assigned to issued.
the point.
Momentary Release
MIP A door summary command allowing
A Memory Interface Processor board one time entry/exit through a DPU-
capable of being installed on certain controlled door.
DCUs or Taps, allowing the devices
firmware to be downloaded from a
host operator station.

MR NOVRAM
MR DPUs to one MRI. The MRI occupies

The Micro Regulator (MR) is used in a a two consecutive controller LAN
variety of applications to control addresses, extending the total control-
mechanical equipment (for example, lers that may be assigned to a single
fans and valves) in either high- or low- controller LAN.
voltage applications. MRs have
Multiplexing
various input and output points,
depending upon the MR model The process of using a device to
number. handle several other devices or opera-
tions at the same time.
MR-AHU
Micro Regulator Air Handling Unit,
an Application Specific Controller
(ASC). This controller provides appli-
cations flexibility to address multiple
N
AHU configurations. It can operate as Network
a stand-alone controller, over a
A system made up of workstations
modem to a remote workstation, or
and connected devices, including
with an optional TAC controller LAN.
controllers and modems.
MR-VAV See also: LAN
Micro Regulator Variable Air Non-recurring Tabular Report
Volume, an Application Specific
One of the four reports available in
Controller (ASC). This controller
SevenTrends. This report is usually a
provides single duct pressure indepen-
summary of trend data from points on
dent VAV box control. The MR-VAV
the I/NET system.
may have up to two built-in trans-
ducer assemblies. It can operate as a Nonvolatile Memory
stand-alone controller, over a modem
Memory that retains data after power
to a remote workstation, or with an
is turned off.
optional TAC controller LAN.
NOVRAM
MRI
Nonvolatile random access memory.
Micro Regulator Interface. The 7792
A special type of memory chip that
MRI provides a communications
does not lose stored data after the
gateway between the controller LAN
power is turned off. This memory is
and the MRs/ASCs/DPUs on the
often used to store system and hard-
subLAN. It passes information
ware parameters in I/NET subLAN
between the controller and MR LANs.
devices (for example, UCs and MRs).
You can attach up to 64 MRs/ASCs/

Offline Database Edit PCX
Override Billing
O A point extension editor that lets you
compute the amount of time a
Offline Database Edit customer overrode the normal after-
hours operating parameters for
This facility lets you modify controller
heating, cooling, and lighting. The
databases without having to connect
associated costs for the override are
to the actual controller.
computed for billing purposes.
Online System
Override
I/NET is an online system. It lets you
The act of circumventing the normal
process data from a terminal. Online
operating parameters.
systems can be used by multiple users.
This is the opposite of a batch system
where functions are performed as a
result of a program without any
human interaction. P
Operand Parameter (Calculated Point)
The data upon which an operation A type of operand (P0P9) used in
(such as adding, dividing, etc.) is calculated point editor or in a MR-
performed. For example, in the resident calculation module editor as
expression 3 + 4, 3 and 4 are the opposed to constants (C0C9).
operands, and + is the operator.
PCU
Operator Station Process Control Unit. A specialized
Any computer terminal used as a type of controller or DCU. The 7716
workstation on I/NET. Operator and 7718 controllers are PCUs.
stations are also known and referred
to as host workstations or hosts. Personnel Schedule
You can assign up to 31 time schedules
Operator Time-out to each door. Each time schedule can
A time limit that can be programmed contain up to seven access intervals,
into I/NET. When an operator station and defines the time period during
has no keyboard or mouse activity for which a key/card can access a door.
the programmed time limit, I/NET
will sign the user off of the host PCX
station. This is an extension used on certain
bit-mapped graphic files produced by
popular paint programs.

PID Module RAM
PID Module Pre-signon Passwords

Proportional, Integral, Derivative Passwords assigned through the pass-
DDC module that uses analog output word editor that let an operator auto-
to control AO points. These points matically connect to a DCU without
can be true AO points (420 mA) or entering a separate password.
pulse-width modulated (PWM)
outputs. Pulsed INPUT
Pulsed input (PI) points accumulate
Point Address pulses from the connected device and
The address of a point on a controller. convert them to engineering unit
This term can describe the entire values, such as gallons or kilowatt-
LLSSPPBB PT address of the point, or hours.
just the PP portion of the address. The
point numbers (PP) usually range PWM
from 00 to 31. Pulse Width Modulation. A method
used to translate an analog value into
Point Extension a discrete output pulse duration.
A pre-defined function that can be PWM points function like true AO
attached to a point. points but do not require a digital-to-
analog converter. In terms of the hard-
Pop-up Calculator ware, a PWM is really an AO point
An online option that helps you calcu- operating at an address usually used
late conversion coefficients while in for a DO point.
the conversion coefficient portion of
the station parameters editor.
Primary Path
A communication path defined in the R
host stations configuration file RAM
(S7000DRV.CNF) to provide commu-
nications to connected devices. Random Access Memory. A type of
See also: Alternate Path memory where any location can be
accessed directly. RAM is erased when
Prompt/Menu Line power is lost.
versions. This line shows the prompts
or menus associated with each screen.

RCOPY Resident I/O Points
RCOPY Relay Module

Record copy. An I/NET utility that lets A DDC module that acts like an elec-
you copy records (system pages, tric-to-pneumatic relay. Its program-
SevenTrends reports, or library ming causes it to act as through it has
symbols), from one operator station a coil, two input ports, and an output
to another over the Ethernet LAN. port. This module also allows time
delays in its programming.
Reader Type
A parameter in the door editor that Remote
identifies one of eight reader data Devices that are connected to a
formats to be used by the reader computer through some sort of a
connected to the DPU. communication device such as a
modem.
Reboot See also: Local
This means restarting your computer.
A cold reboot occurs when you turn Remote Operator Station
the power off and then on again. A An operator station which is accessed
warm reboot occurs when you press by connecting from another operator
and hold [Ctrl] and [Alt] and then station on the same Ethernet LAN.
press [Delete].
Reset Module
Record A DDC module that provides a
A group of logically related fields proportional varying analog value to
treated as a unit. A group of records another module according to a
make up a file. primary (coarse) and secondary (fine)
input.
Recurring Tabular Report
A SevenTrends report containing Resident I/O Points
recurring data elements. This type of All input and output points found in
report can extend for many pages and I/NET are resident input/output
usually encompasses great amounts of points. They can be external, internal,
repetitive detailed data. or indirect points. There are ten point
types. They can be defined, examined,
Relational Operator and modified through the resident I/O
Operators that compare two values, points editor.
such as > (greater than) and < (less
than).

Restore Shunt
Restore Secure
A utility found in the I/NET shell A system parameter in door mode
menu that lets you restore backed up schedules that returns a door to
files from a floppy diskette onto the limited access at a specific day and
hard drive. time.
Runtime Setpoints
A point extension editor that lets you A setpoint is an analog value, usually a
collect runtime data, in minutes, from temperature, that I/NET strives to
DI/DO points. maintain.
SevenTrends
A data storage and report generation
program within I/NET. You can
S produce recurring/nonrecurring
tabular reports, XY plots, and time-
S/STAT
based plots.
Slide thermostat. An intelligent space
sensor with local temperature and Shell Menu
setpoint display, override select, and For I/NET 3.x versions, this menu lets
setpoint adjustment. The S/STAT is you access utility programs, enter
similar to the I/STAT, but with a slide I/NET operation, or exit to the system
control instead of a keypad. prompt.
See also: I/STAT, M/STAT
Signon
SLI
Entering the I/NET system with a
The SubLAN Interface (SLI) acts as a valid password
communication gateway, allowing
controllers on its subLAN to commu- Signoff
nicate with the rest of the I/NET
Exiting the I/NET system, securing the
system. The 7791 DPI, 7793 MCI, and
host from unauthorized use.
7798 I/SITE LAN are SLIs.
Shunt
Scan Interval
A parameter in the door parameters
A parameter common to all points.
editor. This option is used to bypass
The scan interval is the number of
an in-house alarm system when the
seconds that elapse between point
door is opened because of a valid
scans.
key/card read.

Software Restore Status Line
Software Restore energized condition of a discrete

Use this facility to download software output point or closed condition of
to any controller or Tap that can a discrete input point.
accept downloaded software. 7716,
Station
7718, 7756, 7780, 7791, 7792, 7793,
and 7798 controllers can accept down- Another generic term for a controller
loaded software without any modifi- or DCU.
cation. Other controllers can accept
downloaded software only with a MIP
Station Name
card installed (i.e., 7700, 7740, etc.). The name you assign to a controller.
Special Day Assignments Station Parameters

The function within the special day An I/NET editor divided into four
editor that lets you define specific days subeditors. You must use these editors
when schedules or events are different to define your control descriptions
from normal operations. and commands, your state descrip-
tions, your conversion coefficients,
Special Day Broadcast and your engineering units. This
This host workstation function lets information is required for each
you quickly broadcast special day controller-resident input/output
settings to DCUs in remote locations. point.
Stand-alone ATS Station Restore

Time scheduling function that is resi- This facility lets you restore DCU
dent in the DCU or subLAN, allowing database information you saved using
automated control of equipment the station save facility.
without connecting to the I/NET host
LAN.
Station Save
An I/NET facility that lets you save a
State Descriptions DCU database. Data is saved to the
This is a station parameter editor. Use directory you selected during the
this editor to enter pairs of descriptors installation process (specified in the
that describe the current state of the S7000DRV.CNF file).
device being controlled or monitored.
The first descriptor of the pair should
Status Line
describe the trip or deenergized Line 2 of the display in I/NET 3.x
condition of a discrete output point or versions. This line displays the system
the open condition of a discrete connection information.
input point. The second descriptor of
the pair should describe the close or

String Compare (SCP) Test On
String Compare (SCP)

A SevenTrends function that allows
you to compare two ASCII strings.
T
Tap
Strike Duration
A communication device that lets
A parameter in the door parameters
operator stations communicate with
editor. The amount of time (0255
DCUs on controller LANs.
seconds) that a door will remain
unlocked after a key/card is read or a Temperature Control
release button is pressed.
A point extension for DC and DO
Supervised Inputs points that provides information for
optimized cycling, optimized start/
Input points that are monitored for
stop, night setback/setup control and
shorts or breaks in the line by the
demand temperature override infor-
addition of two resistors in the circuit.
mation for output points.
Symbol Library Tenant
A collection of predefined graphic
In the I/NET Access Control system,
symbols used on system pages.
groups of individuals that inhabit the
System Alarms/Messages Line same facility but that are controlled
separately.
versions. When I/NET detects an Test Off
alarm, the appropriate message
A system action that takes DCU-resi-
appears on this line.
dent points out of test mode. Auto-
System Pages matic control commands are re-
enabled.
A graphics area where points or
processes are displayed graphically. Test On
You can add or delete points from a
A system action that places DCU-resi-
system page. The system page is an
dent points into test mode. While in
interactive display of the I/NET
test mode, the operator may manually
system in operation.
change the value or state of the point,
but no commands are carried out and
no data is transmitted. Automatic
control commands are disabled.

Thermistor Unitary Controller (UC)
Thermistor Toggle Switch

A specialized temperature-sensing A switch with only two positions (on
device that can be connected to or off).
certain controllers. It contains a semi-
conductor sensing element where the Trend Sampling
resistance falls in a highly non-linear A point extension editor that lets you
fashion as the temperature rises. Ther- track any or all points in each DCU
mistors are very accurate over small with resolution of one minute incre-
temperature spans. ments. The trend samples can then be
directed to the SevenTrends tables for
Time Scheduling permanent archiving or temporary
A point extension editor that lets you storage.
schedule start, stop, and cycle times
for a DO/DC point. Trend Plot
A graphic plot showing data collected
Time-based Plot Report through trend sampling over a period
A SevenTrends report showing a plot of time.
of data from one or more points over
a period of time. Twisted Pair
A pair of wires formed by twisting
Time Zone together individual conductors, used
The world is divided into 24 time for voice communication and data
zones. Time zones begin at Green- transmission.
wich, England (1) and increase from
east to west. Refer to Appendix B, Two-Position Module
Time Zone Map for a world map A DDC module with an on/off output
showing time zones. You must define used to control DO or DC points.
a time zone and Daylight Savings
start/stop times (if applicable) to use
the sunrise/sunset commands in the
time scheduling editor.
U
Toggle
Unitary Controller (UC)
To switch an entry field back and forth
between two different selections, such The UC family is a specialized set of
as yes or no. controllers with a relatively small
number of input/output points
compared to other controllers. These
controllers are specifically designed to
monitor and control cooling or

Unitary Controller Interface (UCI) Workstation
heating variable air volume terminal programs are usually involved in basic
boxes, air handling units, and heat housekeeping functions such as
pumps. They typically have eight backups, restores, and file copying.
inputs and eight outputs per UC.
Unitary Controller Interface (UCI)

The DCU 7760 provides a communi-
cations gateway between the VZ
controller LAN and the UCs. It passes
VAV-UC
information between the controller
and UC LANs. You can attach up to 32 Variable Air Volume UC. This UC
UCs to one UCI. The UCI occupies a controls pressure dependent/indepen-
single controller LAN address, effec- dent single-duct, cooling, or heating
tively extending the span of control- terminal boxes. They are also used to
lers that may be assigned to a single control double-duct terminal boxes.
controller LAN. They have either one or two velocity
pressure sensor assemblies, and eight
Universal UC universal input and eight output
The universal UC is used in a variety points.
of applications to control mechanical
ViewCon Panel
equipment (exhaust fans, water
heaters, lighting) that dont need a Built-in user interface, available on
unique control algorithm available in selected controllers, that allows access
the unitary controllers. Universal UCs to controller functions without a host
have eight universal input points and workstation or HHC.
eight universal output points.
Visitor
Unlock An individual or group allowed
A mode schedule parameter that temporary access to a door or group
enables a door for open access during of doors.
a scheduled cycle. Key/card readers are
Workstation
still enabled for continued access
control auditing (roll call). A computer and its associated hard-
ware and software. In I/NET the term
Utilities workstation is used interchangeably
These I/NET programs perform with operator station, host work-
specific specialized functions not station, and host.
normally covered by I/NET. Utility

XY Plot Report
XY Plot Report
A SevenTrends report showing the
relationship of data from two system
points: one plotted on the x-axis, the
other on the y-axis. The intersection
of the two data cells produces a point
on the plot. XY plots produce a series
of points that are connected with a
line.
Zone
A term associated with the lighting
control, override billing, and door
point extension editors. A zone
usually refers to a specific area of a
building. Information is gathered and
points are controlled according to
zones.
Zoom
The zoom command on a system page
lets you move automatically from the
selected icon to a point or point exten-
sion editor.

Index
mode schedules 9-33

parameters 9-209-32
Numerics PIN message enable 9-22
PIN pad 9-21
26-bit Wiegand Format 9-8 PIN retry count 9-22
32-bit Wiegand Format 9-9 reader type 9-20
7800 Tap 1-41 re-lock timer 9-31
shunt 9-31
78041 embedded Tap 2-15 strike duration 9-30
elevator
extension 7-24, 9-51
function 7-24
A parameters 7-247-26, 9-51
9-52
access control group parameters 9-63
dial after edit 9-89 groups
doors assigning 9-64, 9-72
adding 9-19 hierarchy 9-819-82
anti-passback 9-25 multiple 9-66
anti-passback reset time 9-29 individuals
door closed timer 9-32 allocate range 9-74
door code 9-29 display options 9-75
door release switch 9-31 door selection 9-71
door sense switch 9-30 field names 9-75
door strike 9-30 parameters 9-65
DOTL 9-30 reposition 9-73
elevator 9-25 secondary group doors 9-72
entry zone 9-26 selection of 9-64
exit reader 9-23 key/card translation
exit zone 9-26 Card Translation option 9-25
exit/entry zone numbers 9-26 key/tag translations 9-58
first key auto-unlock 9-31 options 9-839-87
intercard interval 9-24 permanent 9-63
LED polarity 9-24 personnel schedules 9-52
I/NET Seven Technical Reference Guide Index-1

A
secondary group 9-72 air handling unit see unitary controller

shift rotation 9-55 alarm delay 6-20
temporary 9-63
tenants alarm inhibit 7-3
adding 9-59 delay before enable 7-3
parameters 9-609-61 delay before inhibit 7-3
visitor enable state 7-3
see access control, temporary memory requirements 7-3
9-63 status input 7-3
access initiated control 9-569-58 alarm priority

critical 6-16
accumulator type dial Tap 3-4
external 6-27 direct connect Tap 3-4
integrating 6-27 none 6-16
reflective 6-27 priority 6-16
ACNxxx file 9-75 routine 3-4, 6-16
action messages see also message priority
memory requirements 5-40 alarm system control 9-37
action, operator time-out 4-2 alarms 3-173-21
Activity Manager, Individual 9-88 notification of 3-18
summary screen 3-19
address totals 3-17
bit offset 1-43 see also AMT
building of 1-42
DCU 1-43 AMT 1-5, 3-93-45
link 1-43 active window 3-10
point 1-43 alarm 3-173-21
point type 1-43 action message 3-20
station 1-43 address 3-20
system 1-42 audible 3-19
Tap count 3-20
see address, link date 3-20
dispatch message 3-21
AHU display order 3-17
see unitary controller event type 3-20
AI fields 3-203-21
see alarm inhibit name 3-20
see analog input time 3-20
AIC alarm duration 3-14
see access initiated control alarm totals 3-17
Index-2 I/NET Seven Technical Reference Guide

A
audible alarms 3-14 print 3-45

cascade display 3-10 report priority 3-43
configuration 3-123-15 transaction filter 3-45
alarm topmost 3-12 fields 3-45??, 3-46??
audible alarm duration 3-14 name 3-46
background color 3-13 range 3-45
constant alarm 3-14 record type 3-46
foreground color 3-12, 3-13 analog input 6-4
message/alarm masking 3-15
printer masking 3-15 analog output 6-5, 6-8
timed alarm 3-14 analog sample cell
database description 15-9
tables 3-43 analog sample trend
display mode 3-10 memory requirements 15-23
file storage 3-10
masking 3-15 Analog to digital conversion 5-21
message 3-213-24 anti-passback 9-25, 9-449-45
address 3-21 defining reader 9-25
date 3-21 entry zone number 9-26
dispatch message 3-22 exit zone number 9-26
display order 3-21 reset time 9-29
event 3-22 reset, timed 9-44
event types 3-263-42 reset. manual 9-45
fields 3-213-22 zones 9-269-29
name 3-22 AO
number of records 3-21 see analog output
site 3-22
time 3-21 APB 9-449-45
value 3-22 reset, manual 9-45
message filter 3-233-24 reset, timed 9-44
event info 3-25 Application Specific Controller (ASC)
message/alarm masking 3-15 data display 13-2
password 3-11 active cooling setpoint 13-4
printer masking 3-15 active heating setpoint 13-4
tile display 3-10 active setpoint 13-2
toolbar 3-11 AHU loading 13-2
transaction 3-433-45 airflow 13-5
cell number 3-43 damper position 13-5
event types 3-443-45 demand control 13-3
group and mask 3-43 enthalpy control 13-3

B
occupancy 13-3 building manager 1-36

outside air temp 13-3 buttons, user-defined
setpoint 13-4 see user-defined tools
shutdown/purge/lockout 13-3
space temperature 13-2
stat offset adjustment 13-4
system setpoint 13-4
description of 13-1 C
editors used with 13-10
free points 13-10 calculations
modifying names 13-6 calculated point address 7-5
parameters HiLo module 10-23
copying 13-6 hints 7-15
modifying 13-5, 13-6 memory requirements 7-4
removing ASC points from the module in micro regulators 12-11
interface controller 13-8 operators 7-67-14
updating Card Translation 9-25
ASC 13-9
Card Translation option 9-25
interface controller 13-7
CCTV 3-50
ATS
host 4-33 cell
stand-alone in MRs 12-9 data transfer 15-415-8
deleting 15-14
Audit Trail Messages 9-15
inquiry/edit 15-10
Auto-dial/Auto-answer message mask 15-17
external modem 2-14 modifying 15-14
RS232 2-14 number 15-13, 15-18
automatic DCU save 4-25 priority 15-18
sample count 15-19
automatic DPU restore 5-10
transient duration 15-12
types 15-9
description 15-9
circuit assignment 7-32
B Client/Server Infrastructure 1-28
backup stations, maximums 1-31 CN
binary file 4-30 see consumption
bits 6-186-20 commercial LAN

see LAN, Ethernet
broadcast change counts 6-25

D
communication conversion coefficients 5-195-24, 6-24,

impairment of 1-9 12-7
configuration flow equation 5-19
AMT 3-123-15 linear equation 5-19, 5-21, 5-22
host 4-1 Lini-Temp sensor
link 4-21 Celsius 5-22
NetPlus Router 2-262-31 Fahrenheit 5-22
network 4-18, 4-23 pop-up calculator 5-19
site 4-21 conversions, key/card 9-7
stations 4-21 cycle
summaries 4-29 see time scheduling
see also summary
configuration profiles 1-19
configure 1-5, 1-17
connect D
graphic page 2-23
multi-site dial 2-23 DA
see discrete alarm
consumption
data transmission 15-8 data extraction
description 15-9 equation operators 7-67-14
pulse input 7-17 data storage 15-3
consumption trend archiving 15-28
memory requirements 15-23 editors 15-16
receiving data 15-4
control commands
transient duration 15-12
command 5-17
delay 5-17 data upload, dynamic 5-16
control descriptions database
command 5-17 last changed 5-3
DC and DO points 6-20 print 4-28
definition 5-17 database caching 9-10
doors 5-18
DC
control sources 7-30 see demand control
controller LAN 1-6, 1-9 see discrete control
controller pulse rates 6-4 DCU
7700 1-35
controller subLAN 1-7
7716 PCU 1-35
7718 PCU 1-36

D
7728 I/SITE I/O 1-36 maximum off time 7-24

7740 1-36 monthly consumption point 7-19
7750 Building Manager 1-36 normal shed differential 7-20
7760 UCI 1-37 on state 7-23
7770 ICI 1-37 override control point 7-21
7780 DLCU 1-38 override shed differential 7-22
7791 DPI 1-38 priority 7-23
7792 MRI 1-39 shed level 7-22
automatic save 4-25 see also temperature control
configuration 5-2 demand trend
database last changed 5-3 memory requirements 15-23
firmware status 5-4
maximums 1-31 derivative, rate interval 10-39
memory status 5-3 DI
overview 1-35 see discrete input
password preassignment 4-14 dial after edit 9-89
resident points 6-1
selection 4-13 differential
synchronization 4-23 how to determine 10-28
time scheduling 5-7 see temperature control
token passing 1-9 digital CCTV 3-50
DDC digital input 6-2
damper control 11-41 digital output 6-6
description of 10-1
lines 10-2 digital to analog conversion 5-22
modules in MRs 12-10 digital to pulse width conversion 5-22
PID 10-1 direct digital control
description of 10-1 see DDC
two-position module 10-3 see unitary controller
default system page 4-2 direct-connect 2-7
demand disabled points 4-28
data transmission 15-8
description 15-10 discrete alarm 6-3
demand control 7-18 discrete control 6-8

current demand point 7-19 discrete input 6-1
demand interval 7-18 discrete monitor 6-8
emergency shed differential 7-21
load 7-23 discrete sample cell
load size 7-23 description 15-10

E
discrete sample trend transient users 9-10

memory requirements 15-23 DPU database caching 9-10
Distributed Link Architecture (DLA) 1-10 DPU summary 4-29
distribution group 4-1, 15-17 dynamic data upload 5-16
messages 6-16
Tap configuration 2-6
see also masking
DM
see discrete monitor E
DO elevator 9-25
see discrete output access control 7-24
Docutrend control function 7-24
dynamic data upload 5-16 door point 7-24, 9-51
editors 15-16 extension 7-24, 9-51
functions floor designation 7-25, 9-51
order of 15-2 process, control of 9-50
midnight statistics 5-16 embedded 4x Dial Tap 2-15
door embedded 78041 Tap 2-15
closed timer 9-32
engineering units 6-24
code 9-29
release switch 9-31 entry zone 9-26
sense switch 9-30 Ethernet LAN 1-6, 1-7
strike 9-30
Ethernet LAN, requirements 1-4
doors
EV
access control 9-199-34
see event definition
control descriptions 5-18
data transmission 15-8 event actions 5-40
DOTL 9-30 event definition
action message 7-26
download
analog sensor input failure 7-28
controller/Tap 5-15
event sequence 5-35, 7-26
MIP 5-14
memory requirements 7-26
DPU sequence/message 7-28
7793 MCI 1-40
event sequence
7797 ICI 1-40
action 5-36, 5-39
7798 I/SITE LAN 1-41
delay 5-36
database caching 9-10
event definition 5-35
resident users 9-10

F

event tool
see user-defined tools
G
exit reader 9-23 gateway address 2-28
exit zone 9-26 GI
Extended mode timeout 9-39 see digital input
external modem global point

AD/AA 2-14 broadcast 6-11
integrated dial 2-11 definition 6-10
direction of flow 6-12
extraction equation operators 7-67-14 illustration 6-11
level 6-15
old data state 6-13
on subLAN device 6-13
F GO
see digital output
field names group parameters 9-63
access control database file 9-75
customizing 9-75 group selection 4-14
File Equalization groups
Multiple Access 1-31 assigning 9-64, 9-72
hierarchy 9-819-82
filemaster 1-24
multiple 9-66
filter, IP 2-32
firmware status 5-4
first key auto-unlock 9-31
Float H
see Floating module
hand-held console 1-42
Floating module
memory requirements 10-19 hardware coefficients 12-7
output decrease 10-33 hardware link 1-21
throttling range 10-36 Hayes-compatible modem
turn-around 10-36 setup for AD/AA 2-17
flow equation 5-19 setup for integrated dial 2-11
function selection 4-6 switch settings for 78010 2-11
functions, user-defined 9-36 Hexidecimal Number Support 9-7

I
HHC ICI
see hand-held console see industrial controller interface
high alarm limit 6-25 indirect point 6-10
high sensor limit 6-25 see also global point
HiLo Individual Activity Manager 9-88

see HiLo module industrial controller interface (ICI)
HiLo module baud rate 14-2
high operators 10-22 database mapping 14-5
low operators 10-22 delay 14-2
memory requirements 10-22 direct mapping 14-6
global points 14-5
host address 1-21 indirect points 14-5
host ATS 4-33 interface status 14-2
host configuration 4-1 mapping conversion 14-6
MODBUS
host LAN 1-6, 1-9 addresses 14-4
backup stations not permitted 1-9 host agreement 14-2
maximum number of PCs 1-9 PLC point types
host passwords 4-3 coils 14-4
host summary 4-29 holding registers 14-5
input registers 14-4
host Taps 2-3 inputs 14-4
maximums 1-31 protocol 14-1
HPMP parity 14-2
see unitary controller point addressing 14-3
AI 14-3
AO 14-3
DA 14-3
DC 14-3
I DI 14-3
DM 14-3
I/NET
DO 14-3
complex configuration 15-6
GI 14-3
off-line configuration 15-5
GO 14-3
remote configuration 15-6
PI 14-3
simple configuration 15-4
point class 14-7
I/NET configuration 1-17 point mapping 14-5
I/O Server 1-5 point name 14-7
point types 14-4
I/STAT 1-42

KL
port status 14-2 distance limits 1-31

program, logic controller 14-1 equipment limitations 1-31
protocol 14-2 Ethernet 1-7
register type 0 14-4 host 1-9
register type 1 14-4 specifications 1-32
register type 3 14-4 Large Number Support 9-5
register type 4 14-5
register types 14-4 LCD pages 5-30
scan interval 14-8 LED polarity 9-24
slave address 14-2 lighting circuits
stop bits 14-2 delay before off 7-29
timeout 14-2 local/external 7-29
Integral digital CCTV 3-50 number of 7-29
integrated dial 2-9 off duration 7-30
host workstation setup 2-10 on duration 7-29
modem setup 2-11 remote/indirect 7-29
wink cycles 7-30
integrated NPR dial 2-9
lighting control 7-297-32
intercard interval 9-24 7780 DLCU 1-38
interval, refresh 4-2 circuits 7-29
Intruder Alarm System 9-37 see also lighting circuits
control sources 7-30
IP Filtering 2-32 memory requirements 7-29
override input 7-30
point addresses 7-29
wink example 7-30
KL zones 7-31
limit
Key/Card Numbers high alarm 6-25
26-bit Wiegand Format 9-8 high sensor 6-25
32-bit Wiegand Format 9-9 low alarm 6-25
Conversions 9-7 low sensor 6-24
Hexidecimal Number Support 9-7
Limited-access Users 4-15
Large Number Support 9-5
Overview 9-4 linear equation
Translating 9-58 analog to digital conversion 5-19, 5-21
digital to analog conversion 5-22
Key/Card Translations 9-58
digital to pulse width conversion 5-22
LAN
Lini-Temp conversion coefficients 5-22
controller 1-9

M
link configuration 4-21 bit offset addresses 12-3

link summary 4-29 editors used by 12-12
resident programming 12-12
link support station restore 12-2
see Tap, link support
memory interface processor
link Tap see MIP
addresses 1-10
maximums 1-31 memory requirements
action messages 5-40
link Taps 2-4 alarm inhibit 7-3
link types 1-20 analog input 6-4
links 1-9 analog output 6-6
calculations 7-4
lookup tables 5-24 digital input 6-2
low alarm limit 6-25 digital output 6-7
low sensor limit 6-24 discrete alarm 6-4
discrete control 6-9
discrete input 6-2
discrete monitor 6-9
discrete output 6-8
M event definition 7-26
event sequence 5-35
Manager, Individual Activity 9-88 Floating module 10-19
manual mode 5-32 HiLo module 10-22
PID module 10-4
mask 15-17
pulse width modulation 6-6
IP filter 2-33
pulsed input 6-4
operator station 15-4, 15-17
Relay module 10-23
priority 15-18
Reset module 10-21
masking runtime 7-38
active positions 3-2 special days 5-32
assignment 3-3 temperature control 7-40
definition 3-1 time scheduling 7-47
example 3-3
memory status 5-3
message/alarm 3-15
messages 6-16 message filter 3-233-24
planning 3-4 event info 3-25
printer 3-2, 3-15 message mask
system messages 3-2 distribution group 6-16
MCI Tap configuration 2-6
see also masking

M
message priority MCI resident programming 12-12

critical 3-4, 5-5, 6-17 MRI resident programming 12-12
definition of 2-7, 3-5, 5-5 MRI/MCI/MR resident programming
dial Tap 3-4 12-12
direct connect Tap 3-4 stand-alone ATS 12-9
none 3-4, 5-5, 6-17 micro regulator interface
priority 3-4, 5-5, 6-17 see MRI
routine 3-4, 5-5, 6-17
Tap configuration 2-6 minimum close 6-22
message routing minimum trip 6-22

system messages MIP 5-14
ATS-mstr failed 3-3 MODBUS
auto-DIF failed 3-3 see industrial controller interface
DCU-save failed 3-3
host lost/restored 3-2 modem
host signon 3-2 setup for integrated dial 2-11
on-line 90%/95% full 3-2 workstation cable 2-12
online data lost 3-2 momentary duration 6-21
received at host 3-2 monitor 4-2
received at printer 3-2
signoff 3-2 monitor point address 6-23
special day lost 3-3 MR summary 4-29
time-sync failed 3-3 MRI
see also masking bit offset addresses 12-3
messages 3-213-24 configuration 12-2
and alarm masks 4-1 editors used by 12-12
cell mask 6-16 multi-link dial 1-21
description of 3-1
distribution group 6-16 Multiple Access 1-31
event types 3-263-42 multiple site dial
routing parameters connection 2-23
see message routing number of sites 2-22
see also AMT required Tap 2-22
micro control interface multi-point trend plot 5-425-49
see MCI
micro regulator
DDC modules 12-10
editors used with 12-11
hardware coefficients 12-7

P
offset 6-24
N operator stations, maximums 1-31

operator time-out 4-3
NetPlus Router 1-7, 1-33, 1-34, 2-242-31 action 4-2
address 2-27, 2-30 override
configuration 2-262-31 data transmission 15-8
activating 2-26 description 15-10
entry fields 2-272-30
restoring 2-30 override billing
saving 2-30 access codes 7-35
controller LAN address 2-30 equipment mapping 7-36
diagnostic LEDs 2-31 override parameters 7-36
diagnostics 2-31 wink 7-37
domain name zones 7-34
domain name 2-28 override parameters 7-31
gateway address 2-28 override trend
integrated dial function 2-25 memory requirements 15-23
IP address 2-27
link address 2-30
modem 2-25
name 2-27
network connection 2-30 P
password 2-31
reference host 2-28 pager operation
SNMP 2-29 78060/1 Tap 2-20
station address 2-30 character definitions 2-20
subnet mask 2-28 pages, system 4-17
Tap functions 2-25
password
network configuration 4-18, 4-23 adding a new host 4-4
normal state 6-20 AMT 3-11
authorization levels 4-15
NPR see NetPlus Router
DCU password editor 4-15
number of samples 4-32 DCU passwords 4-15
function selection 4-6
host 4-3
NetPlus Router 2-31
O password preassignment, DCU 4-14
PC requirements 1-3
off-normal points 4-27

P
PCU alarm priority 6-15

7716 1-35 broadcast change counts 6-25
7718 1-36 cell number 6-17
personnel schedule class 6-14
access control 9-52 external 6-14
door access 9-52 indirect 6-14
internal 6-14
phone numbers, remote dial 2-13 control description 6-20
PI conversion coefficients 6-24
see pulse input conversion equation 6-23
PID data transmission 15-8
control point 10-36 disabled 4-28
description of 10-1 distribution group 6-16
failsafe 10-36 engineering units 6-24
memory requirements 10-4 expected state 6-21
output high limit 10-35 global 6-10
output low limit 10-35 see also global point
output ramp limit 10-34 global level 6-15
P-only mode 10-7 high alarm limit 6-25
proportional band 10-37 high sensor limit 6-25
reset interval 10-39 lookup table 6-26
reverse mode 10-42 low alarm limit 6-25
tuning low sensor limit 6-24
maximum bump 10-43 manual mode 5-31
maximum overshoot 10-44 masks 6-16
noise band 10-45 message priority 6-17
setting time 10-43 minimum close 6-22
target damping 10-44 minimum trip 6-22
momentary duration 6-21
PIN monitor point address 6-23
algorithm 9-86 name 6-14
PIN message enable 9-22 normal state 6-20
PIN pad 9-21 number of bits 6-18
1-bit 6-19
PIN Pad Functions 9-36 2-bit 6-19
PIN retry count 9-22 3-bit 6-19
point off-normal 4-27
accumulator type 6-27 offset 6-24
addresses 6-13 restart control action 6-22
alarm delay 6-20 scan interval 6-14

R
scans between broadcast 6-27 consumption 7-17

state descriptions 6-18 definition of 6-4
supervised 6-28 pulse rates 6-4
test mode 5-31
three-state output 6-23 pulse width modulation 6-5
time to state 6-23 pure proportional control 10-7
types 6-16-13 PWM
analog input (AI) 6-4 see pulse width modulation
analog output (AO) 6-5
dicrete input (DI) 6-18
digital input (GI) 6-2
digital output (GO) 6-6
discrete alarm (DA) 6-3, 6-18 R
discrete control (DC) 6-8
discrete input (DI) 6-1 rate interval 10-39
discrete monitor (DM) 6-8 reader type 9-20
discrete output (DO) 6-8
reference host 1-21, 2-28
DM/DC vs. DO 6-8
global 6-10 refresh interval 4-2
see also global point relay
indirect points 6-10 see Relay module
multi-bit points 6-18
Relay module
pulse input 6-4
DI = 0 input 10-48
pulse width modulation (PWM)
DI = 1 input 10-48
6-5
discrete input 10-50
supervised 6-28
point control relay types, standard 10-48
manual mode 5-31 time delay 10-49
test mode 5-31
reliable
P-only mode 10-7 messaging 3-7
pop-up calculator 5-19 tap 3-8, 5-5
preassignment, DCU password 4-14 re-lock timer 9-31
print, database 4-28 remote dial phone numbers 2-13
printer reset
Taps 2-5 see Reset module
Proportional, Integral, Derivative Reset module
see PID memory requirements 10-21
primary input 10-45
pulse input

S
primary inputs 10-45 tenant 4-14

primary outputs 10-46 sensor input, lookup tables 5-24
reset interval 10-39
secondary input 10-46 serial port configuration 1-20
secondary inputs 10-47 Series 2000 NetPlus Router
secondary outputs 10-47 see NetPlus Router
resident in DPU 9-67 SevenTrends
resident individuals 9-10, 9-67 data
space requirements 15-23
resident points, data transmission 15-8 functions 15-2
resident users 9-10 DCU editors 15-15
restore, software 4-30 editors 15-15
runtime Shift Rotation 9-55

accumulator 7-39 shortcut tool
data transmission 15-8 see user-defined tools
description 15-10 shunt 9-31
on state 7-38 Simple Network Management Protocol
reset mode (SNMP) 2-29
constant 7-39 site configuration 4-21
point 7-39 site Taps 2-4
runtime trend slave schedule
memory requirements 15-23 see time scheduling
SNMP 2-29
software restore 4-30
S special days
see time scheduling
SAVE file 4-30 state 5-18
save, automatic DCU 4-25 close 5-18
trip 5-18
scan interval 6-14
state descriptions 5-18, 6-18
scans between broadcast 6-27
station configuration 4-21
secondary group 9-72
station parameters
selection
conversion coefficients 5-195-24,
DCU 4-13
6-24
function 4-6
engineering units 5-24
group 4-14

T
lookup tables 5-24 site 2-4

state descriptions 5-18 configuration editors
station restore 5-9 parameters 2-5
parameters updated 2-5
station save 5-9 gateway to LAN 1-41, 2-1
station summary 4-29 integrated dial 2-9
strike duration 9-30 link connections 2-4
link support 1-9
subnet mask 2-28 overview 2-1
summary pager operation 2-20
DPU 4-29 restore 2-22
host 4-29 restore function 2-22
link 4-29 save 2-22
MR 4-29 save function 2-22
station 4-29 special purpose 2-2
UC 4-29 TCP/IP
synchonization, DCU 4-23 configuration 1-21
system definition 1-8
default page 4-2 telephone numbers 2-18
equipment limitations 1-31 temperature control
hardware requirements 1-32 cooling target 7-42
limits 1-31 cycle adjustment 7-44
pages 4-17 demand control 7-41
system addresses 1-42 demand temperature override 7-41
system limits 1-31 differential 7-43
optimized cycle 7-44
system link 1-21 optimized start 7-44
system requirements 1-3 optimized stop 7-44
heating target 7-42
optimized start lookahead 7-40
optimized stop lookahead 7-41
T red wire control 7-39
setback 7-42
Tap
setup 7-42
78060/1 Tap field descriptions 2-18
configuration tenant selection 4-14
host 2-3 tenants
link 2-4 adding 9-59
printer 2-5 parameters 9-60

T
test mode 5-31 trend

time scheduling name 15-11
cycle 7-48 types 15-12
on/off 7-49 trend log 4-32
room temperature 7-48 trend plot
setback 7-43 multi-point 5-425-49
setup 7-42
days of the week 7-49 trend sampling 15-19
extension 5-7 base time 7-46
memory requirements 7-47 cell sample count 7-45
optimized cycle 7-48 cell sample counts 15-19
optimized start 7-48 data transmission 15-8
optimized stop 7-48 interval 7-46
slave schedule number of samples 7-46
ignore action 7-51 relation to trend log 4-32
mirror action 7-51 sample control mode 7-46
optimize action 7-51 point 7-46
special day broadcast 5-33 times 7-46
special days 5-32 trend interval 15-19
date 5-33 TS
definition 7-49 see time scheduling
duration 5-34 tuning
end of year 5-34 maximum bump 10-43
memory requirement 5-32 maximum overshoot 10-44
start 7-48 noise band 10-45
stop 7-48 setting time 10-43
temporary schedules 7-50 target damping 10-44
time to state 6-23 Two-position module
time-out, operator 4-3 differential 10-28
tokens 1-9 direct mode 10-42
failsafe command 10-40
tools, user-defined input filter 10-30
see user-defined tools input lower limit 10-28, 10-29
transactions 3-433-45 reverse mode 10-42
event types 3-443-45 sample interval 10-26
filter 3-45 setpoint 10-27
see also AMT
transient individuals 9-10
transient users 9-10

U
Ostop 11-5
overall control loop 11-5
U override options 11-32
parent point 11-2
UC PID 11-7
see unitary controller PID parameters 11-4111-44
UC summary 4-29 PID/FLT failsafe 11-27
UCI range 11-32
7760 1-37 remote override 11-21
maximums 1-31 remote setpoint adjustment 11-20
station restore 11-3 reversing valve 11-38
setpoint adjustment 11-32
unitary controller setpoints 11-30
activation delay 11-36 space temperature 11-35
AHU 11-2, 11-29 temperature setpoint 11-35
AHU control loop 11-19 timed override 11-32
central plant heat 11-35 duration 11-33
CFM 11-23 indicator 11-33
compressor 11-39 types of 11-2
cooling stages 11-37 UC/UCI resident programming 11-5
damper control 11-41 UCI resident programming 11-4
damper override 11-34 VAV 11-2, 11-29
DDC 11-28 VAV control loop 11-12
fan 11-35 velocity pressure, conversion to CFM
fan control 11-37 11-23
fan/heat interlock 11-27 warmup/cooldown 11-34
FLT 11-7
FLT parameters 11-4411-46 universal UC 11-46
heat strip 11-40 User, Limited-access 4-15
heat strip setpoint offset 11-40, 11-41 User-defined PIN Pad Functions 9-36
heating fan control 11-36
heating setpoint offset 11-37 user-defined tools
heating stages 11-36 event tool 1-45
HPMP 11-2, 11-29 overview 1-44
HPMP control loop 11-19 running 1-45
internal configuration 11-3 shortcut tool 1-44
Lini-temp sensors 11-25 users, limited-access 4-15
maximums 1-31
minimum trip/close 11-2
mixing dampers 11-26
Ostart 11-5

VZ
VZ
VAV
see unitary controller
workstation requirements 1-3
Xenta 527/527-NPR 1-34
zone definitions
override parameters 7-31

TAC
Corporate Headquarters
Jgershillgatan 18
213 75 Malm
Sweden
Phone: +46 40 38 68 50
Fax: +46 40 21 82 87
www.tac.se
TAC Americas
P.O. Box 59469
Dallas, TX 75229 USA
Phone: +1 (972) 323 1111
Fax: +1 (972) 242 0026
www.tac-americas.com
TAC Asia-Pacific
Level 3/2A Lord Street
Botany NSW 2019
Australia
Phone: +61 (0) 2 8336 6100
Fax: +61 (0) 2 8336 6190
www.tac.com
You may obtain copies of this document by ordering

document number TCON300.
TCON300 06/08

TAC INET Seven System - Technical Reference Guide - New PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TAC INET Seven System - Technical Reference Guide - New PDF

Caricato da

Copyright:

Formati disponibili

Technical Reference Guide

I/NET Seven System

Copyright 20012008 TAC. All rights reserved.

I/NET Seven Technical Reference Guide v

Chapter 1 System Configuration

I/NET Seven Technical Reference Guide vii

viii I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide ix

x I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xi

Chapter 4 Host Functions

xii I/NET Seven Technical Reference Guide

Chapter 5 Controller Functions

I/NET Seven Technical Reference Guide xiii

xiv I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xv

xvi I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xvii

xviii I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xix

xx I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xxi

xxii I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xxiii

xxiv I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xxv

xxvi I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xxvii

xxviii I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide xxix

Chapter 12 Micro Regulator Control

xxx I/NET Seven Technical Reference Guide

Chapter 14 7771 Industrial Controller Interface

I/NET Seven Technical Reference Guide xxxi

I/NET Seven Technical Reference Guide 1-1

The software also includes a specialized graphics editor for creating

I/NET Seven Documentation

1-2 I/NET Seven Technical Reference Guide

In addition to the printed documentation listed above, a compre-

Minimum System Requirements

I/NET Seven Technical Reference Guide 1-3

Your Windows system must be configured to use NTFS in order to

Sound card and speakers (required for AMT audible alarms)

1-4 I/NET Seven Technical Reference Guide

Table 1-1. I/NET Software Components

I/NET Seven Technical Reference Guide 1-5

1-6 I/NET Seven Technical Reference Guide

Figure 1-1. LAN hierarchy showing possible configurations

Controller subLAN Some controllers, such as the Micro

I/NET Seven Technical Reference Guide 1-7

network topology can take almost any shape and can be

See Also: The section on Setup and Network Configuration in TCON299,

1-8 I/NET Seven Technical Reference Guide

I/NET Seven Technical Reference Guide 1-9

this section focuses on I/NETs traditional use of link devices. For

Distributed Link Architecture (DLA) Support

1-10 I/NET Seven Technical Reference Guide

I/NET Seven adds Distributed Link Architecture (DLA) capabili-

Note: I/NETs system-wide limits of 6,400 controllers and 100 link

I/NET Seven Technical Reference Guide 1-11

Figure 1-2. Traditional Host LAN/Link LAN Architecture

Tap 01 has a permanent, direct connection to Buildings A and B

1-12 I/NET Seven Technical Reference Guide