Sie sind auf Seite 1von 690

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 (VAV and AHU only) . . . . . . . . . . . . . . . . 11-36
Stage 2 Heating Setpoint Offset (VAV and AHU only) . . . . . . . . . 11-37
Stage 3 Heating (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 (AHU only) . . . . . . . . . . . . . . . . . . . . . 11-38
Stage 2 Cooling Setpoint Offset (AHU only) . . . . . . . . . . . . . . 11-38
Stage 3 Cooling (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 (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-39
Compressor #2 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-39
Compressor #3 (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
Heater Strip #2 (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-40
Heater Strip #2 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-40
Heater Strip #3 (HPMP only) . . . . . . . . . . . . . . . . . . . . 11-40
Heater Strip #3 Setpoint Offset (HPMP only) . . . . . . . . . . . . . 11-41
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.

I/NET Seven Technical Reference Guide 1-3


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.

1-4 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 1-5


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.

1-6 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 1-7


LAN Communication System Configuration

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.

1-8 I/NET Seven Technical Reference Guide


System Configuration LAN Communication

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

I/NET Seven Technical Reference Guide 1-9


LAN Communication System Configuration

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.

1-10 I/NET Seven Technical Reference Guide


System Configuration LAN Communication

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.

I/NET Seven Technical Reference Guide 1-11


LAN Communication System Configuration

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

1-12 I/NET Seven Technical Reference Guide


System Configuration LAN Communication

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.).

I/NET Seven Technical Reference Guide 1-13


LAN Communication System Configuration

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.

1-14 I/NET Seven Technical Reference Guide


System Configuration LAN Communication

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

I/NET Seven Technical Reference Guide 1-15


LAN Communication System Configuration

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.

1-16 I/NET Seven Technical Reference Guide


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 Seven Technical Reference Guide 1-17


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.

1-18 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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.

I/NET Seven Technical Reference Guide 1-19


I/NET Configuration System Configuration

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.

1-20 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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

I/NET Seven Technical Reference Guide 1-21


I/NET Configuration System Configuration

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

1-22 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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

I/NET Seven Technical Reference Guide 1-23


I/NET Configuration System Configuration

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.

1-24 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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.

I/NET Seven Technical Reference Guide 1-25


I/NET Configuration System Configuration

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.

1-26 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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.

Note: You must have Windows Administrator rights in order to make any
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.

I/NET Seven Technical Reference Guide 1-27


I/NET Configuration System Configuration

Client/Server Infrastructure
Note: You must have Windows Administrator rights in order to make any
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.

1-28 I/NET Seven Technical Reference Guide


System Configuration I/NET Configuration

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.

I/NET Seven Technical Reference Guide 1-29


I/NET Configuration System Configuration

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.

1-30 I/NET Seven Technical Reference Guide


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 Seven Technical Reference Guide 1-31


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.

1-32 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 1-33


I/NET System Hardware System Configuration

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.

1-34 I/NET Seven Technical Reference Guide


System Configuration I/NET System Hardware

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.

I/NET Seven Technical Reference Guide 1-35


I/NET System Hardware System Configuration

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.

1-36 I/NET Seven Technical Reference Guide


System Configuration I/NET System Hardware

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.

I/NET Seven Technical Reference Guide 1-37


I/NET System Hardware System Configuration

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.

1-38 I/NET Seven Technical Reference Guide


System Configuration I/NET System Hardware

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
TCON117, Door Processor Unit 7920
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

I/NET Seven Technical Reference Guide 1-39


I/NET System Hardware System Configuration

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.

1-40 I/NET Seven Technical Reference Guide


System Configuration I/NET System Hardware

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.

I/NET Seven Technical Reference Guide 1-41


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

1-42 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 1-43


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.

1-44 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 1-45


User-defined Tools System Configuration

1-46 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 2-1


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

2-2 I/NET Seven Technical Reference Guide


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).

I/NET Seven Technical Reference Guide 2-3


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.

2-4 I/NET Seven Technical Reference Guide


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).

I/NET Seven Technical Reference Guide 2-5


Tap Configuration Parameters Communication

Table 2-1. Tap Configuration Parameters (Continued)

Tap Type
Parameter Description
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).

2-6 I/NET Seven Technical Reference Guide


Communication Direct-Connect Function

Table 2-1. Tap Configuration Parameters (Continued)

Tap Type
Parameter Description
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).

I/NET Seven Technical Reference Guide 2-7


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.

2-8 I/NET Seven Technical Reference Guide


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.
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.
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.

I/NET Seven Technical Reference Guide 2-9


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.

2-10 I/NET Seven Technical Reference Guide


Communication Integrated Dial Function

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

I/NET Seven Technical Reference Guide 2-11


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-12 I/NET Seven Technical Reference Guide


Communication Integrated Dial Function

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.

I/NET Seven Technical Reference Guide 2-13


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

2-14 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 2-15


Auto-dial/Auto-answer (AD/AA) Tap Function Communication

Add a link as follows:


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.

2-16 I/NET Seven Technical Reference Guide


Communication Auto-dial/Auto-answer (AD/AA) Tap Function

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).

I/NET Seven Technical Reference Guide 2-17


Auto-dial/Auto-answer (AD/AA) Tap Function Communication

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.

2-18 I/NET Seven Technical Reference Guide


Communication Auto-dial/Auto-answer (AD/AA) Tap Function

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.

I/NET Seven Technical Reference Guide 2-19


Auto-dial/Auto-answer (AD/AA) Tap Function Communication

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

2-20 I/NET Seven Technical Reference Guide


Communication Auto-dial/Auto-answer (AD/AA) Tap Function

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.

I/NET Seven Technical Reference Guide 2-21


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.

2-22 I/NET Seven Technical Reference Guide


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:
Add a link as follows:

I/NET Seven Technical Reference Guide 2-23


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.
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.
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

2-24 I/NET Seven Technical Reference Guide


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).

I/NET Seven Technical Reference Guide 2-25


NPRs and Xenta 527/527-NPRs Communication

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.)

2-26 I/NET Seven Technical Reference Guide


Communication NPRs and Xenta 527/527-NPRs

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.

I/NET Seven Technical Reference Guide 2-27


NPRs and Xenta 527/527-NPRs Communication

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.

2-28 I/NET Seven Technical Reference Guide


Communication NPRs and Xenta 527/527-NPRs

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 Seven Technical Reference Guide 2-29


NPRs and Xenta 527/527-NPRs Communication

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

2-30 I/NET Seven Technical Reference Guide


Communication NPRs and Xenta 527/527-NPRs

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

I/NET Seven Technical Reference Guide 2-31


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

2-32 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 2-33


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).

2-34 I/NET Seven Technical Reference Guide


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.

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.)

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,

I/NET Seven Technical Reference Guide 3-1


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

3-2 I/NET Seven Technical Reference Guide


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
Dist. Group Information from this
1 2 3 4 editor will be received at
Mask workstations 1 and 3.

Editor C
Dist. Group Information from this
1 2 3 4 editor will be received at
Mask workstations 2 and 3.

Editor D
Dist. Group Information from this
1 2 3 4 editor will not be received
Mask at any workstation.

Figure 3-2. Masking and Data Transmission

I/NET Seven Technical Reference Guide 3-3


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.

3-4 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 3-5


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

3-6 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 3-7


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.

3-8 I/NET Seven Technical Reference Guide


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

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.)

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 Seven Technical Reference Guide 3-9


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.

3-10 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-11


I/NET AMT System Messages

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.

3-12 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-13


I/NET AMT System Messages

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.

3-14 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-15


I/NET AMT System Messages

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

3-16 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-17


I/NET AMT System Messages

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.

3-18 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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


TCON299, I/NET Seven Operator Guide
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).

I/NET Seven Technical Reference Guide 3-19


I/NET AMT System Messages

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.

3-20 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-21


I/NET AMT System Messages

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.

3-22 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-23


I/NET AMT System Messages

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:

3-24 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-25


I/NET AMT System Messages

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

3-26 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-27


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
Host editor message/
DCU-save failed NA NA remote controller has
workstation alarm mask: group
failed to reach the
1, far left position
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
access controlled door
DPU or Door extension
Deny entry dsbl R, P, C NA was denied because
SCU1284 editor
the key/card used is
disabled.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-28 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*

Entry through an
access controlled door
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
access controlled door
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
access controlled door
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
access controlled door
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
DPU or Door extension
Deny exit dsbl R, P, C NA denied because the
SCU1284 editor
key/card used is
disabled.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-29


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*

Exit through an access


controlled door was
DPU or Door extension denied because an
Deny exit PIN R, P, C NA
SCU1284 editor invalid personal
identification number
(PIN) was entered.
Exit through an access
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.
Exit through an access
controlled door was
denied because a door
DPU or Door extension
Deny exit sel R, P, C NA and personnel
SCU1284 editor
schedule has not been
selected for the
individual.
Exit through an access
controlled door was
denied because the
individuals key/card is
DPU or Door extension
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-30 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
An access controlled
DPU or editor for door
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
1, far left position
lost.
Resident I/O points
A duress code has
DPU or editor for door
Duress elev R, P, C NA been entered at an
SCU1284 parent point (BB =
elevator PIN pad.
08 or 09)
A duress code has
DPU or Door extension
Duress entry R, P, C NA been entered at an
SCU1284 editor
entry reader PIN pad.
A duress code has
DPU or Door extension
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
Host editor message/
DVR Srv Offline NA NA communicate with the
Workstation alarm mask: group
Digital Video Recorder
1, far left position
(DVR) server.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-31


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
Host editor message/
Edit AIC NA NA access initiated control
workstation alarm mask: group
editor has been made.
1, far left position
Host configuration
A change in the DCU
Host editor message/
Edit DCU PW NA NA passwords editor has
workstation alarm mask: group
been made.
1, far left position
Host configuration
A change in the
Host editor message/
Edit Door NA NA access control door
workstation alarm mask: group
editor has been made.
1, far left position
Host configuration
A change in the
Host editor message/
Edit Elev. NA NA elevator editor has
workstation alarm mask: group
been made.
1, far left position
Host configuration
A change in the
Host editor message/
Edit Group NA NA access control group
workstation alarm mask: group
editor has been made.
1, far left position
Host configuration
A change in the host
Host editor message/
Edit Hst PW NA NA passwords editor has
workstation alarm mask: group
been made.
1, far left position
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.
Host configuration A change in the
Host editor message/ access control
Edit P/Schd NA NA
workstation alarm mask: group personnel schedule
1, far left position editor has been made.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-32 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*

Host configuration
A change in the
Host editor message/
Edit Tenant NA NA access control tenant
workstation alarm mask: group
editor has been made.
1, far left position
Host configuration A change in the
Host editor message/ access control
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
identification number
DPU or Door extension
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
An access controlled
DPU or editor for door
Forced Door R, P, C NA door has been forced
SCU1284 parent point (BB =
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-33


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-34 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
selected for the NPR
or Xenta 527/527-NPR
NPR or Xenta NetPlus Router
Link # Conflict N/A N/A is a duplicate of
527/527-NPR configuration editor
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-35


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-36 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
DPU or editor for door
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.
Resident I/O points The Mode Schedule
DPU or editor for door for this door has
Mode PIN enable NA NA
SCU1284 parent point changed its status to
(BB = 08 or 09) require a PIN for entry.
Resident I/O points The Mode Schedule
DPU or editor for door for this door has
Mode secure NA NA
SCU1284 parent point changed its status to
(BB = 08 or 09) secured.
Resident I/O points The Mode Schedule
DPU or editor for door for this door has
Mode unlock NA NA
SCU1284 parent point changed its status to
(BB = 08 or 09) unlocked.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-37


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
Host editor message/
Online data lost NA NA archived. All
workstation alarm mask: group
subsequent incoming
1, far left position
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.
A valid key/card was
DPU or Door extension used to enter through
Reader entry R, P, C NA
SCU1284 editor an access controlled
door.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-38 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*

A valid personal
identification number
Reader entry - DPU or Door extension
R, P, C NA was used to enter
PIN SCU1284 editor
through an access
controlled door.
A valid key/card was
DPU or Door extension used to exit through an
Reader exit R, P, C NA
SCU1284 editor access controlled
door.
A valid personal
identification number
DPU or Door extension
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
Host editor message/
Sample data lost NA NA communication failure
workstation alarm mask: group
or because no file
1, far left position
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-39


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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
selected for the NPR
or Xenta 527/527-NPR
NPR or Xenta NetPlus Router
Site # Conflict N/A R, P, C is a duplicate of
527/527-NPR configuration editor
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
Host editor message/
Special day lost NA NA day broadcast failed to
workstation alarm mask: group
reach a remote DCU.
1, far left position
Resident I/O points A discrete points state
State change DCU NA R, P, C
editor for DI point has changed.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-40 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*

I/NET lost
Site (LAN)
communication with
Tap, Link Tap, Host, link, or LAN
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
Tap, Link Tap, Host, link, or LAN
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
Host editor message/
Ten. D/L failed NA NA information to a
workstation alarm mask: group
DPU/SCU has failed.
1, far left position
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

I/NET Seven Technical Reference Guide 3-41


I/NET AMT System Messages

Table 3-4. Event Types (Continued)

Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable

3-42 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-43


I/NET AMT System Messages

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.

3-44 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-45


I/NET AMT System Messages

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.

3-46 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-47


I/NET AMT System Messages

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.

3-48 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-49


I/NET AMT System Messages

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).

3-50 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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.

I/NET Seven Technical Reference Guide 3-51


I/NET AMT System Messages

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.

3-52 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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

I/NET Seven Technical Reference Guide 3-53


I/NET AMT System Messages

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.

3-54 I/NET Seven Technical Reference Guide


System Messages I/NET AMT

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

I/NET Seven Technical Reference Guide 3-55


I/NET AMT System Messages

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.

3-56 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 3-57


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.

3-58 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-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.

4-2 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 4-3


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

4-4 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

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.

I/NET Seven Technical Reference Guide 4-5


Host Passwords Host Functions

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.

4-6 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

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.
Refer to TCON301, I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related I/NET features.
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.

I/NET Seven Technical Reference Guide 4-7


Host Passwords Host Functions

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
Modify CCTV camera message masks in the Camera Parameters
editor.
CCTV - Message Parameters
Refer to TCON301, I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related I/NET features.
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.

4-8 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
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

I/NET Seven Technical Reference Guide 4-9


Host Passwords Host Functions

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
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

4-10 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
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
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

I/NET Seven Technical Reference Guide 4-11


Host Passwords Host Functions

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
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

4-12 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

Table 4-1. Function Select Editor Fields (Continued)

Function/Editor Action
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.

I/NET Seven Technical Reference Guide 4-13


Host Passwords Host 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.

4-14 I/NET Seven Technical Reference Guide


Host Functions Host Passwords

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.

I/NET Seven Technical Reference Guide 4-15


Host Passwords Host Functions

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.
Can only see doors associated with allowed groups

4-16 I/NET Seven Technical Reference Guide


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 only see doors associated with allowed groups
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.

I/NET Seven Technical Reference Guide 4-17


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.

4-18 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-19


Network Configuration Host Functions

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.

4-20 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-21


Network Configuration Host Functions

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.

4-22 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-23


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.

4-24 I/NET Seven Technical Reference Guide


Host Functions Network Functions

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.

I/NET Seven Technical Reference Guide 4-25


Network Functions Host Functions

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

4-26 I/NET Seven Technical Reference Guide


Host Functions Network Functions

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-

I/NET Seven Technical Reference Guide 4-27


Network Functions Host Functions

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-

4-28 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-29


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
Host (direct connect),
Revision The revision level of the Tap or controller firmware.
Link, Station
Host (direct connect),
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

4-30 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 4-31


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.

4-32 I/NET Seven Technical Reference Guide


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

Parameter Description

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.

I/NET Seven Technical Reference Guide 4-33


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.

4-34 I/NET Seven Technical Reference Guide


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-

I/NET Seven Technical Reference Guide 5-1


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.

5-2 I/NET Seven Technical Reference Guide


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


These fields are informational only. You cannot make changes.
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 (*).

I/NET Seven Technical Reference Guide 5-3


Configuration and Status Controller Functions

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
These fields are informational only. You cannot make changes.
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

5-4 I/NET Seven Technical Reference Guide


Controller Functions Configuration and Status

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.

I/NET Seven Technical Reference Guide 5-5


Configuration and Status Controller Functions

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.

5-6 I/NET Seven Technical Reference Guide


Controller Functions Configuration and Status

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.

I/NET Seven Technical Reference Guide 5-7


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.

5-8 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 5-9


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.

5-10 I/NET Seven Technical Reference Guide


Controller Functions Station Save and Restore

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.

I/NET Seven Technical Reference Guide 5-11


Station Save and Restore Controller Functions

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.

5-12 I/NET Seven Technical Reference Guide


Controller Functions Station Save and Restore

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
Restore Host 2 = 1 Restore Host 2 = 1 Restore Host 2 = 1 Restore Host 2 = 3
Restore Host 3 = 3 Restore Host 3 = 3 Restore Host 3 = 2 Restore Host 3 = 2
Restore Host 4 = 0 Restore Host 4 = 0 Restore Host 4 = 0 Restore Host 4 = 0

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

I/NET Seven Technical Reference Guide 5-13


Station Save and Restore Controller Functions

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

5-14 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 5-15


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.

5-16 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 5-17


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.

5-18 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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:

I/NET Seven Technical Reference Guide 5-19


Station Parameters Controller Functions

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.

5-20 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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

I/NET Seven Technical Reference Guide 5-21


Station Parameters Controller Functions

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


y = m (x) + b The basic linear equation.
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.

The entries you put in the conversion table are:


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.

5-22 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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


y = m (x) + b The basic linear equation.
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.

The entries you put in the conversion table are:


m = 0.039526 b = 0.79052

I/NET Seven Technical Reference Guide 5-23


Station Parameters Controller Functions

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.

5-24 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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
Obtained from column B of Table 5-8, Sample 16-bit Lookup
Table Calculation Chart

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:

I/NET Seven Technical Reference Guide 5-25


Station Parameters Controller Functions

12-bit resolution:
A/D Count = [Ohms/(Ohms+10,000)] 4095
16-bit resolution:
A/D Count = [Ohms/(Ohms+10,000)] 65535
Obtained from column B of Table 5-8, Sample 16-bit Lookup
Table Calculation Chart

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.

5-26 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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

I/NET Seven Technical Reference Guide 5-27


Station Parameters Controller Functions

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
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

5-28 I/NET Seven Technical Reference Guide


Controller Functions Station Parameters

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
Counts Counts Counts Counts

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

I/NET Seven Technical Reference Guide 5-29


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.

5-30 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 5-31


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

5-32 I/NET Seven Technical Reference Guide


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).

I/NET Seven Technical Reference Guide 5-33


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.

5-34 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 5-35


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.

5-36 I/NET Seven Technical Reference Guide


Controller Functions Event Sequences

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
again be controlled by normal automated processes.

I/NET Seven Technical Reference Guide 5-37


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.

5-38 I/NET Seven Technical Reference Guide


Controller Functions Event Sequences

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
again be controlled by normal automated processes.
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.

I/NET Seven Technical Reference Guide 5-39


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

5-40 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 5-41


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.

5-42 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 5-43


Multi-Point Trend Plot Controller Functions

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.

5-44 I/NET Seven Technical Reference Guide


Controller Functions Multi-Point Trend Plot

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.

I/NET Seven Technical Reference Guide 5-45


Multi-Point Trend Plot Controller Functions

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
desired point. This field is automatically entered if you select a
point from one of the four quadrants.
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
desired point. This field is automatically entered if you select a
point from one of the four quadrants.
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.

5-46 I/NET Seven Technical Reference Guide


Controller Functions Multi-Point Trend Plot

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

I/NET Seven Technical Reference Guide 5-47


Multi-Point Trend Plot Controller Functions

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.

5-48 I/NET Seven Technical Reference Guide


Controller Functions Multi-Point Trend Plot

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.

I/NET Seven Technical Reference Guide 5-49


Multi-Point Trend Plot Controller Functions

5-50 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 6-1


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.).

6-2 I/NET Seven Technical Reference Guide


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

I/NET Seven Technical Reference Guide 6-3


Resident Input/Output Point Types Input and Output Points

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

6-4 I/NET Seven Technical Reference Guide


Input and Output Points Resident Input/Output Point Types

(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
7720 DCU 4 per second 120 msec recommended
4 per second 120 msec recommended HHC code 10 = 0
7728 I/SITE
20 per second absolute 20 msec absolute HHC code 10 = 1
7730 DCU 4 per second 120 msec recommended
7740 DCU 4 per second 120 msec recommended
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.

I/NET Seven Technical Reference Guide 6-5


Resident Input/Output Point Types Input and Output Points

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.

6-6 I/NET Seven Technical Reference Guide


Input and Output Points Resident Input/Output Point Types

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

I/NET Seven Technical Reference Guide 6-7


Resident Input/Output Point Types Input and Output Points

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

6-8 I/NET Seven Technical Reference Guide


Input and Output Points Resident Input/Output Point Types

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.

I/NET Seven Technical Reference Guide 6-9


Resident Input/Output Point Types Input and Output Points

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.
This point may provide information to an indirect point in any device
Link
connected to this host LAN.
This point may provide information to an indirect point in any device
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.

6-10 I/NET Seven Technical Reference Guide


Input and Output Points Resident Input/Output Point Types

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.

I/NET Seven Technical Reference Guide 6-11


Resident Input/Output Point Types Input and Output Points

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).

6-12 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 6-13


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.

6-14 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 6-15


Point Database Parameters Input and Output Points

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

6-16 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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.

See Also: Chapter 15, SevenTrends

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.

I/NET Seven Technical Reference Guide 6-17


Point Database Parameters Input and Output Points

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.

See Also: Chapter 15, SevenTrends

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).

6-18 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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.

I/NET Seven Technical Reference Guide 6-19


Point Database Parameters Input and Output Points

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.

6-20 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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.

I/NET Seven Technical Reference Guide 6-21


Point Database Parameters Input and Output Points

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
This field is used with DC and DO point types only. Enter a
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
This field is used with DC and DO point types only. Enter a
number between 0 and 255. This is the number of minutes that
must elapse following a 1 command from the controller before a 0

6-22 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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).

I/NET Seven Technical Reference Guide 6-23


Point Database Parameters Input and Output Points

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.

6-24 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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


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 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


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 records a value less than the
number you enter here, the point goes into alarm.

High Alarm 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 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.

I/NET Seven Technical Reference Guide 6-25


Point Database Parameters Input and Output Points

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

6-26 I/NET Seven Technical Reference Guide


Input and Output Points Point Database Parameters

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].

I/NET Seven Technical Reference Guide 6-27


Point Database Parameters Input and Output Points

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.

6-28 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 7-1


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.

7-2 I/NET Seven Technical Reference Guide


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.

I/NET Seven Technical Reference Guide 7-3


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.
The entry fields for this extension editor are as follows:
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.

7-4 I/NET Seven Technical Reference Guide


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).

I/NET Seven Technical Reference Guide 7-5


Calculations (C) Point Extensions

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)