Professional Documents
Culture Documents
Seven
Front Cover
TCON30004/13
We at Schneider Electric have tried to make the information contained in this manual as
accurate and reliable as possible. Nevertheless, Schneider Electric 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 Schneider
Electric 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 Schneider Electric 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: TCON30004/13
On October 1st, 2009, TAC became the Buildings business of its parent company Schneider
Electric. This document reflects the visual identity of Schneider Electric; however, there
remains references to TAC as a corporate brand in the body copy. As each document is
updated, the body copy will be changed to reflect appropriate corporate brand changes.
Use of Third Party Software
Schneider Electric software is delivered for use on IBM and compatible PCs. While your PC
is capable of running other third-party software while running TAC I/NET Seven, 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 Schneider Electric software
is also memory-resident. The use of more than one memory-resident program at the same
time may impose unresolvable 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 TAC 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 Schneider Electric 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.
Schneider Electric makes no claims or commitments regarding the use of any third-party
software, other than MS-DOS and the Windows operating system in conjunction with
the PC programs supplied by Schneider Electric, and offers no support in accommodating
the use of same. Furthermore, Schneider Electric accepts no liability for system failures that
may result from the use of any third-party software with Schneider Electric software.
Chapter 2 Communication
7800 Tap Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Host Taps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
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-10
Host Workstation Setup for Integrated Dial . . . . . . . . . . . . . . . . 2-10
Modem Setup for Integrated Dial . . . . . . . . . . . . . . . . . . . . 2-12
Call Initiating (Host) End . . . . . . . . . . . . . . . . . . . . . . 2-12
Call Receiving (78010 Tap) End . . . . . . . . . . . . . . . . . . . 2-12
Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Auto-dial/Auto-answer (AD/AA) Tap Function . . . . . . . . . . . . 2-14
Embedded 4x Dial Tap . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Adding a Modem to Windows 7 Professional . . . . . . . . . . . . . . . 2-17
Chapter 16 SevenTrends
SevenTrends Data Storage . . . . . . . . . . . . . . . . . . . . . . . 16-3
Collecting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
1
48
System Configuration
Overview
TAC I/NET Seven is an integrated solution for building manage-
ment that combines environmental control, access control, and
energy management. TAC 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 TAC
I/NET system includes both hardware and software solutions.
Host Workstations
TAC I/NET Seven uses one or more workstations to run host soft-
ware, allowing you to perform programming, record keeping, and
system communication with the controllers, and ultimately, your
environmental or access control equipment.
Notes: TAC I/NET Seven will not run on a Windows workstation that is
configured as a Domain Controller.
You must have administrative privileges in order to install programs
on a Windows workstation.
Your Windows system must be configured to use NTFS in order to
support electronic file encryption (EFS).
For any version of Windows after Windows XP, the online help for
TAC I/NET Seven requires that you manually install the necessary
WinHelp executable. On the internet, search Microsoft for the
keyword KB917607.
Caution: The database server should not be shut down while TAC 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 TAC I/NET Seven software consists not only of the main host
software, but also includes several companion programs that
perform specialized functions. Table 1-1 contains a list of the
primary software components and a brief description of their
specific function.
SQL Server Caution: The database server should not be shut down while TAC
I/NET Seven 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 TAC I/NET Seven host workstation needs to communicate
with many external devices, including other host workstations,
NPRs, Xenta 527/527-NPRs, Taps, and controllers. TAC I/NET
Seven uses a companion program, I/O Server, to facilitate efficient
communication functions.
I/O Server must be running for most TAC I/NET Seven communi-
cation functions to occur. Each time it is started, TAC I/NET Seven
launches I/O Server, which runs in the background. By default, I/O
Server continues to run as a background task even after TAC I/NET
Seven is shut down. This enables your host software to continue to
receive TAC I/NET data even if the host software is not operating.
Should you need to disable the I/O Server temporarily, you can
shut it down manually. You can also instruct TAC I/NET Seven to
shut down all TAC I/NET Seven-related background tasks auto-
matically.
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 TAC 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.
Ethernet LAN
TAC I/NET supports Ethernet LAN communication, allowing you
to take advantage of an existing Ethernet commercial network.
There is no need to run special cable or separate network commu-
nication.
Host workstations, NetPlus Routers (NPRs), and Xenta
527/527-NPRs connect to the LAN through Ethernet adapters
installed in each device. Host workstations and Xenta
527/527-NPRs may use a 10 MBPS or 100 MBPS Ethernet
segment. However, NPRs require a 10 MBPS segment. The system
network topology can take almost any shape and can be
constructed of 10-base T (shielded twisted pair), 10-base 2 (Coax),
or fiber optic interfaced devices.
You may connect up to 250 host workstations and 99 NPRs or
Xenta 527/527-NPRs on a single Ethernet LAN/WAN. Connection
is not limited to a single site and may be made through either dial
or Internet connections.
TCP/IP
TAC I/NET 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.
Note: TAC I/NET Seven requires Microsofts TCP/IP protocol. While TAC
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.
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
Link Support
Host workstations communicate with controller LANs through
Links. Within TAC I/NET Seven, a link may represent a hardware
device (i.e., a Tap, NPR, or Xenta 527/527-NPR) or it may represent
a distributed link (i.e., a single link address that is being shared
among multiple NPRs or Xenta 527/527-NPRs). The information
within this section focuses on TAC I/NET Sevens traditional use of
link devices. For information about distributed links, refer to
Distributed Link Architecture (DLA) Support, starting on page
1-11.
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. TAC 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
TAC I/NET Seven 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.
Note: TAC I/NET Sevens system-wide limits of 6,400 controllers and 100
link addresses must be observed, regardless of whether or not DLA
functions are enabled. For example, if your TAC I/NET Seven 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 TAC I/NET
Seven system.
Before you upgrade an NPR from TAC I/NET 2000 to TAC
I/NET Seven (i.e., before you download DLA-compatible
binary software to an NPR), ensure that you first install TAC
I/NET Seven on all host workstations in your system, begin-
Figure 1-5. TAC I/NET Seven Host PC's Do Not Provide DLA
Functions
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.
User Authentication
TAC I/NET Seven displays an Authentication editor under the
following circumstances:
When you initially attempt to connect to a TAC I/NET Seven
SQL database.
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.
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 TAC I/NET Seven environments,
because you can change system parameters simply by selecting a
different profile.
Most of the configuration parameters are saved in the system
registry and IP routing information specific to each profile is stored
in a .DAT file.
Note: There may be differences in the routing data for each configuration
profile; consequently, you should not change configuration profiles in
a stable TAC I/NET Seven network.
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.
The Link type specified dictates which other parameters are avail-
able in the Configuration Profile editor.
Link Numbers
After selecting the Link type, you must map a hardware link
number to a system link number. While you may use any number
for the hardware link, care should be taken to avoid duplicating
system link numbers. If you assign a system link number that is
already in use, either on the same, or different, host workstation,
TAC I/NET Seven 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.
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,
TAC I/NET Seven 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 TAC I/NET Seven device, it uses the addressing
information contained in the routing table to determine the desti-
nation path. I/O Server stores the routing table in a .DAT file.
To facilitate both the initial building and the updating of the
routing table, the I/O Server uses a reference host. The reference
host may be any host workstation, NPR, or Xenta 527/527-NPR on
the Ethernet LAN and is specified by its IP address. Each time the
I/O Server is launched, it uses the information in the routing table
on the reference host and updates the local routing table, accord-
ingly.
It is best to use a common reference host for all the hosts, NPRs,
and Xenta 527/527-NPRs in the TAC I/NET Seven system.
However, the only specific requirement is that the designated refer-
ence 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 desig-
nate more than one reference host as a precautionary measure. You
should also assign a reference host to the TAC I/NET Seven work-
stations, NPRs, or Xenta 527/527-NPRs that are acting as reference
hosts.
As an example of proper reference host assignments, Figure 1-7
shows each NPR at a remote site defining a host PC on the Ethernet
as a reference host. This reference host also points back to one of
the remote NPRs. This will ensure that proper communication can
be established during the commissioning of this system, or when
the system comes up following a communication interruption.
Explanation:
File Equalization
Note: You must have Windows Administrator rights in order to make any
changes to your TAC I/NET Seven configuration that will affect file
equalization.
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).
Note: You must have Windows Administrator rights in order to make any
changes to your TAC I/NET Seven configuration that will effect file
equalization.
TAC I/NET Seven hosts by default are standalone workstations.
While standalone workstations may allow remote clients to
connect to them to use their database, they do not equalize their
TAC I/NET Seven database with a filemaster. When you set the
Workstation type to Filemaster in the Configure program, you
are promoting that workstation to filemaster status. When you
configure a workstation to receive equalized 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 TAC I/NET Seven database.
When you promote a workstation to be an equalized client, TAC
I/NET Seven requires that you provide proper authentication as an
authorized TAC I/NET Seven user of the filemaster, and as a data-
base administrator of the local TAC I/NET Seven database and of
the filemasters database. This helps to ensure that no data on the
filemaster gets distributed to unauthorized clients.
Multiple Access
TAC I/NET Seven 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. TAC I/NET Seven will display a message if, because of
multiple access, your edits could not be saved.
Client/Server Infrastructure
Note: You must have Windows Administrator rights in order to make any
changes to your TAC I/NET Seven configuration that will affect the
client/server configuration.
Client and server workstations must use matching versions of SQL
Server, either 2000 or 2005.
Filemaster Server
The Server
Note: Client and server workstations must use matching versions of SQL
Server, either 2000 or 2005.
The workstation being used as the server will not only manage and
maintain the TAC I/NET Seven database, but it will also be respon-
sible for collecting and storing trend and AMT data. This will
require that the routing masks on the server be configured to allow
collection of trend and AMT data. No remote clients should be
configured to collect trend and AMT data.
When a TAC I/NET Seven workstation is used as the server, all
remote clients must be configured as Remote Client. Refer to
Remote Clients on page 1-31 for more information.
Server without TAC I/NET Seven Installed
The server in a client/server network is not required to run TAC
I/NET Seven. The server must be on the Ethernet, provide SQL
services, allow authorized clients to connect, and have a TAC I/NET
Seven database. You can create the initial TAC I/NET Seven data-
base on the server remotely from a TAC I/NET Seven host worksta-
tion. Refer to the DbCreate chapter in TCON298, TAC I/NET Seven
Getting Started, for instructions.
Because the server does not run TAC I/NET Seven, it will be the
responsibility of a remote client workstation to write trend and
AMT data to the TAC I/NET Seven database. Only one remote
client should have this ability. This client must be configured as
Remote Client w/IO and its routing mask settings must allow for
collection of trend and AMT data. All other clients must be config-
ured as Remote Client. Refer to Remote Clients on page 1-31
for more information.
Remote Clients
System Limits
TAC I/NET Seven 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 convenience.
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.
Xenta 527/527-NPR
Like the NPR, the Xenta 527 and Xenta 527-NPR connect multiple
networks of TAC 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.
TAC I/NET NetPlus Router The TAC I/NET NetPlus Router
allows you to connect multiple networks of TAC 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 TAC I/NET devices into your LonWorks network. In addi-
tion to being a web-based presentation system for LonWorks
networks, you can also use the Xenta 527 to provide web access into
a TAC 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 TAC I/NET
networks. You cannot download XBuilder projects to the Xenta
527-NPR. You can, however, configure this device through a web
browser.
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: TCON098, Model 7750 Distributed Control Unit CSI Building
Manager
7760 (Unitary Controller Interface)
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.
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 TAC 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.
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
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 TAC I/NET Seven system consists of a series of
alphanumeric characters, each describing the route from the top of
the LAN hierarchy to the final device or input/output point. This
addressing structure consists of four pairs of numbers and the
point type. The format for the address is:
LLSSPPBB PT
where:
The point (PP) portion of the address can be 28, 29, 30, and 31 (the
only addresses selectable using a rotary switch located inside of the
arming terminal). The OP5 Arming Terminals bit offset (BB) will
always be 08.
User-defined Tools
There are two types of user-defined tools that you can create within
TAC I/NET Seven. 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.
See Also: Chapter 1, TAC I/NET Seven Basics, in TCON299, TAC I/NET
Seven Operator Guide.
2
36
Communication
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)
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-10).
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-10).
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:
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 Type
Parameter Description
Host Link Site
Firmware The current revision number and date the revision occurred
Status (display only).
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.
Tap Type
Parameter Description
Host Link Site
Direct-Connect Function
The direct-connect function provides continuous two-way
communication within your TAC 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).
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 TAC I/NET
functions.
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).
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.
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.
Phone Numbers
TAC I/NET Seven provides a Phone Numbers editor only when the
active configuration has been set to use the Integrated Dial func-
tion (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.
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.
Note: Ensure that your entire TAC I/NET Seven system is configured to use
the same AD/AA protocol either synchronous, or asynchronous.
Mixing protocols will cause communication errors.
Type
This parameter defines the type of device the controller LAN calls.
This setting determines at what baud rate to attempt the remote
connection. The 78060 Tap can dial out from 300 to 1200 baud to
a 7804x or 7805x Tap, or to a beeper. The 78061 Tap can dial out
from 1200 to 19.2K baud to a 7804x or 7805x Tap, or to a beeper.
Note: When setting the Type parameter, do not choose a rate higher than
9600 baud. This is currently the highest supported baud rate.
Link
This is the system address (0099) assigned to the link. This must
match the system link address defined in the Configure program if
you want to receive on-line messages when the host initiates the
phone call. Also, the telephone number in the 7806x Tap editor
must match the telephone number of the 7804x or 7805x Tap you
entered in the host Network Configuration editor.
Group
This parameter further defines the dialing characteristics of each
phone number entered. You can have up to eight different groups,
each containing one phone number, or one group containing eight
phone numbers. The total number of phone numbers cannot be
greater than eight. Refer to the following example for ideas.
Example
Have the Tap call the phone numbers in group 1 if a fire alarm
occurs and call the phone numbers in group 2 if an electrical failure
occurs. Or, call one group for alarms in one building, and a
different group for alarms in a different building. By having more
than one phone number in a group, you increase the chances of the
message getting through. The Tap will continue to dial the phone
numbers (in the order in which they appear within TAC I/NET
Seven) until it successfully uploads the corresponding message to
one of the numbers in the group.
Dial Mask
The dial mask works like the printer and message masks you define
in the host configuration editor. When a Tap dials out, the point
mask of the point(s) initiating the action is compared to the dial
mask in the Tap. If any of the active point mask positions matches
an active mask position in this field, the Tap dials out. The messages
are sent and then compared at the workstation to determine if the
workstation accepts the messages. If the masks do not match, the
workstation ignores the call.
Note: Use only distribution group 1 with 78060/1 Taps. These Taps require
distribution group 1 to initiate a dial-out.
Non-Volatile
This read-only parameter provides an indication of the telephone
numbers storage location within the Tap. Phone numbers are
stored in either of the following locations:
Non-Volatile = Y indicates phone numbers are stored in
NOVRAM memory (and in RAM memory for the MIP
78060/1 Taps only).
Non-Volatile = N indicates phone numbers are stored in
RAM memory only.
Pager
Definition
Character
Pager
Definition
Character
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
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 TAC I/NET system. See 7800 Tap Overview on
page 2-2 for a discussion of these Tap functions.
Downloadable Firmware
Like many TAC I/NET devices, the NPR has downloadable binary
firmware. You can download firmware to this device from the TAC
I/NET Seven host application (refer to Software Restore on page
5-15), or from the I/O server configuration utility (refer to
TCON298, TAC I/NET Seven Getting Started).
The Xenta 527/527-NPR is also downloadable; however, you
cannot download firmware to this device from TAC I/NET Seven.
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 TAC I/NET Seven Configure program is used to enter the setup
parameters for NPRs and Xenta 527/527-NPRs. Refer to
TCON298, TAC 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 TAC I/NET controller LAN or the commercial LAN.
Once installation is complete and the device is fully connected to
the TAC I/NET system and commercial network, changes to the
setup can be performed either locally (through a connected
Note: After entering the configuration parameters (see below), you must
exit Configure and I/O Server. (This will require you to shutdown
TAC I/NET Seven, if running.) The new configuration will not take
effect until I/O Server is shutdown and restarted. (I/O Server starts
automatically when TAC I/NET Seven or Configure is started.)
Configuration Parameters
Name
Each NPR or Xenta 527/527-NPR must be given a unique name.
This name is used to identify the unit to other devices in the TAC
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-32).
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.
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.
IP Filtering
IP filters are available from the I/NET Configuration program.
Using IP filtering, you can configure each TAC I/NET Seven 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
TAC I/NET device on the Ethernet, its IP address is compared with
the target devices IP filters.
Beginning with the highest priority filter, TAC I/NET Seven deter-
mines if the filter pertains to the incoming IP address. If it does, the
filters block or allow setting will determine whether or not
communications are allowed. If the filter does not pertain to the
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.
TAC I/NET Seven 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, communications will be allowed or blocked, depending on
the setting of the Permission parameter. If the result of both oper-
ations are not equal, this filter will have no affect.
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).
3
60
System Messages
Caution: The database server should not be shut down while TAC I/NET
Seven 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 TAC I/NET device, including hosts, Taps, controllers, and
points in the system, have individual message parameters. These
parameters 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
configuration 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,
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.
Dist. Group 1 2 3 4
Mask
Active 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
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).
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.
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.
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.
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 TAC I/NET controller that is loaded with
firmware 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 TAC
I/NET Seven feature.
Message Queue
Every device in TAC 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 unso-
licited controller LANs (RS485) or upstream devices (Link Tap or
workstation). The size of the queue is a function of the device. All
TAC 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 configura-
tion to suit your needs.
Each LAN device is designed to provide a maximum of 10 messages
per second on an unsolicited token passing RS485 LAN. To reduce
the effects of this system limitation, care should be taken regarding
system architecture, scan rates on points, broadcast change counts
on analog points, scans between broadcast on global pulse input
points, etc.
Buffer Capability
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 TAC I/NET Seven version
2.0 = approximately 150 messages.
Controller software for TAC I/NET Seven 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
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.
AMT
Caution: The database server should not be shut down while TAC I/NET
Seven 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.)
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 TAC I/NET environment. Event notices pertaining to access
control, such as door reader activity, are transactions.
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-49)
Note: Static image verification window settings are not saved. Any open
static image verification windows will be discarded upon logoff, and
will not reappear upon subsequent login.
Security
The AMT functions, including window display, may be protected
by password. When you set password access in the Host Passwords
editor, you may select which AMT functions can be accessed with
that password. Refer to Host Passwords in Chapter 4, Host Func-
tions.
Configuration
The AMT configuration editor allows you to set the display param-
eters for 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.
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:
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. It also
allows you to configure AMT to produce audible alarms for specific
alarm events.
You can choose one of the following options when defining audible
alarms:
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.
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.
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.
Alarms
TAC I/NET Seven 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 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.
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.
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, TAC I/NET Seven Database
Connectivity and Reporting, for more information about integrating
CCTV with TAC 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-89 for
more information.
Event Messages
The TAC I/NET Seven system uses event messages to notify you of
specific event occurrences. When you enter your point informa-
tion, 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).
Field Description
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.
(Transaction only) The access control zone for the key/card
Zone
reader.
Cell The SevenTrends cell number assigned to alarms from this point.
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-89 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, TAC I/NET Seven Database
Connectivity and Reporting, for more information about integrating
CCTV with TAC 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.
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 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.
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
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
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 message storage
Host configuration
capacity of a DCU has
editor message/
DCU queue ovflw DCU NA NA been exceeded.
alarm mask: group
Messages are being
1, far left position
lost.
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable
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
Deny entry dsbl R, P, C NA was denied because
SCU1284 editor
the key/card used is
disabled.
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
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.
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)
* R = Routine, P = Priority, C = Critical, NA = Not Applicable
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
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.
Site (LAN) The controller LAN
Tap, Link has undergone
Host, link, or LAN
Tap, Host reconfiguration
LAN reconfigure Tap configuration NA R, P, C
Tap, NPR, because a device was
editor
Xenta 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.
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.
The message storage
capacity of a LAN Tap
Host or Link Host or Link Tap
LAN Tap Ovflw NA NA has been exceeded.
Tap configuration editor
Messages are being
lost.
I/NET has
LAN Tap Host or Link Host or Link Tap reestablished
NA R, P, C
restored 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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
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.
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.
* R = Routine, P = Priority, C = Critical, NA = Not Applicable
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
Required Required
Message Enabled by
Source Alarm Message Description
Type Mask/Priority of:
Priority* Priority*
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: Only distribution Group 1 messages will cause a Dial Tap to dial out.
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.
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.
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.
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.
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.
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 TAC I/NET Seven
Configuration in TCON298, TAC 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.
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.
Esc
Character
Sequence
Esc
Character
Sequence
\ 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.
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 a Pelco
digital CCTV system with TAC I/NET Seven. For instructions on
how to integrate and use digital CCTV with TAC I/NET Seven,
including information on how to use CCTV from within AMT,
refer to TCON301, TAC 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.
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 (TAC I/NET Seven 2.12 or earlier)
OR
ARC_YYMMDDX.ARC (TAC 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 (TAC I/NET Seven 2.12 or earlier) = indicates a file in
Microsoft standard database format.
OR
.ARC (TAC I/NET Seven 2.13 or later) = indicates a file in SQL
database format.
Number of Records
Records are archived in batches of 1000. An archive will only run if
the current online (unarchived) records exceeds the minimum
online records by at least 1000. The minimum online records is set
in the Archive Configuration editor (see Archive Configuration
Editor below).
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.
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.
Unknown DCU
This message indicates an internal error contact technical support.
response error
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 TAC I/NET Seven
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.
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.
4
36
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.
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.
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 TAC I/NET Seven. 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.
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.
Note: Any DCU save files that are created with encryption will not be
restorable in versions of TAC I/NET Seven prior to version 2.41.
After enabling encryption, any new DCU save files you create will
have the DCU password stored in an encrypted format. Already
existing DCU saves are not affected and will not contain encrypted
DCU passwords unless they get overwritten by new save files.
Each DCU save files encryption key is stored within the file itself.
Therefore, if you ever change the encryption key in the Host
Configuration editor, existing DCU save files will still decrypt
properly.
Password Encryption Key
To enable encryption, use this field to define an encryption key of
up to 16 characters. If you leave this field blank, no encryption will
be performed.
Host Passwords
Passwords are used in TAC I/NET Seven to control user access and
privileges. You can assign host passwords to users and DCU pass-
words to controllers. Host passwords provide system-level security.
When you assign host passwords to users, you can specify which
TAC I/NET Seven 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
TAC I/NET Seven 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
previously 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-17).
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. TAC I/NET
Seven will not accept your parameter settings if the password
confirmation fails.
Initials Use up to four characters to define the operators
initials.
Alternate ID Use this for either of the following purposes:
Create a text string to appear in custom reports
Have this user inherit permissions and/or window
settings from another users account. Refer to Indirect
User Settings in the Passwords chapter of TCON299,
TAC I/NET Seven Operator Guide for more information.
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 TAC I/NET Seven, 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
TAC I/NET Seven.
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 () 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, TAC I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related 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, TAC I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related features.
Add, modify, copy, or delete DVRs. Refer to TCON301, TAC I/NET
CCTV - DVR Seven Database Connectivity and Reporting, for more information
about CCTV-related features.
Modify CCTV camera message masks in the Camera Parameters
editor.
CCTV - Message Parameters
Refer to TCON301, TAC I/NET Seven Database Connectivity and
Reporting, for more information about CCTV-related features.
Change Password Replace users existing host password with a new password
Configuration View controller, Tap, and host configuration summaries
Function/Editor Action
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 TAC I/NET Seven
Live Graphic Page View live system graphic pages
Manual Control Take a point out of automatic operation and place it in manual mode
Multi-Point Trend Access the multi-point trend plot editor
Off Normal Point View offnormal (in alarm) point summaries
Page View the graphic page point summaries
Page Acknowledge Alarms Acknowledge all alarms on the current alarm summary screen page
Control a point to a specific state or value. This function allows
Point Control
operator control of the environmental equipment
Test Off Take a point out of test mode
Test On Place a point into test mode
Work Offline Configure controller-level settings without establishing a connection.
Host Computer
Archive Data Archive SevenTrends data
Configuration The host configuration editor
Data Inquiry/Edit View SevenTrends sample data
Definitions Create, modify, or delete SevenTrends definitions.
Graphics Editor The system pages editor
Host ATS The automatic time schedule editor in the host workstation
Host Trend Log The 12-point host trend log function
Network Configuration Edit the network configuration
Function/Editor Action
Setup automatic DCU saves, time synchronization, special day
Network Functions broadcasts, offnormal point and disabled point displays; print
database tables
Passwords The host passwords editor. By default, this function is not selected
Phone Numbers The phone number editor in a Dial host workstation
Software Restore Database and software restore editor for all downloadable devices
Transfer Configuration Setup parameters for transferring SevenTrends records.
Trend Delete Delete a previously defined trend or cell definition from SevenTrends.
Host Tap
Host Tap The host Tap configuration/status editor.
Link Tap
Link Tap The configuration/status editors for link Taps.
Site Tap
The remote dial Tap configuration editor (when connecting through a
Remote Dial Tap Configuration
controller LAN)
Site Tap Configuration The configuration/status editors for LAN Taps.
Site Tap Restore The 7806x Tap phone number restore function.
Site Tap Save The 7806x Tap phone number save function.
DCU
MRI, MCI, or I/SITE LAN editor used to define MR-AHU or MR-VAV
ASC Parameters
operational parameters.
Alarm Inhibit The alarm inhibit (AI) extension editor
Calculation The calculated (CA) point extension editor
Configuration The controller configuration editor
Consumption The consumption (CN) extension editor
Control Descriptions Define up to 8 control description pairs for a DCU
Conversion Coefficients Define mathematical constants used for A/D conversion
DPU Configuration The DPI resident door processing unit configuration editor
Demand Control The demand control (DC) extension editor
Direct Digital Control The DDC editor
Dynamic Data Upload Initiate a data upload from a controller
The access control elevator (EL) editor used to control elevator
Elevators
pushbuttons within the selected DPI, MCI, or I/SITE LAN
Engineering Units Define up to 16 units of measure
Function/Editor Action
Equipment Mapping Define equipment mapping parameters for a 7750 Building Manager.
Event Actions Message/report/conversion editor
Event Definition The event definition (EV) point extension editor
Event Sequences The event sequences editor
I/STAT Parameters I/STAT parameters editor for MRs and ASCs
Input Configuration Edit DPU parameters
I/SITE I/O and I/SITE LAN editor used to define ViewCon page
LCD Page Definition
displays
Lighting Circuit Add, delete, modify, or copy a lighting circuit in a 7780 DLCU
Lookup Tables Define a lookup table for a 7716, 7718, 7756, or 7728
MCU Configuration The MCI or I/SITE LAN resident MR/ASC/DPU configuration editor
MR Configuration The MRI resident MR configuration editor
The MR resident parameters, factory coefficients, and standalone
MR Functions
ATS editors
The editor used to copy operating parameters from one MR to
MR to MR Copy
another.
Override Access Codes Define codes for remotely initiating overrides
Override Parameters The override billing (OB) extension editor
Passwords The controller passwords editor
Resident I/O Point The resident I/O point editor
Runtime The runtime (RT) extension editor
Special Days The special days editor
State Descriptions Define the descriptors used to indicate point and device status
Station Restore Restore controller database from disk
Station Save Save controller database to disk
Temperature Control The temperature control (TC) extension editor
Time Scheduling The time scheduling (TS) extension editor
Trend Plot Initiate a trend plot
Trend Sampling The trend sampling (TR) extension editor
UC Configuration The UC configuration editor
UC to UC Copy The editor used to copy operating parameters from one UC to another
Unitary Control The unitary control (UC) editor
Zone Definition Define a lighting zone
Function/Editor Action
Host Access
The menu item Access Access Initiated Control.
Access Initiated Control Selecting this menu item opens an editor you can use to define
access initiated control parameters
The menu item Access Access Wizard.
Access Wizard Selecting this menu item causes a wizard to open and guide you
through the process of adding an individual to a tenant.
The menu item Access Door Schedules.
Door Schedules Selecting this menu item causes the Door Selection Summary to
open.
The menu item Access Doors.
Doors Selecting this menu item opens an editor you can use to define door
operating parameters.
The menu item Access Generate PINs.
Generate PINs Selecting this menu item opens an editor you can use to generate a
list of personal identification numbers (PINs)
The menu item Access Generate PINs.
Groups Selecting this menu item opens an editor you can use to define
groups.
The menu item Access Individuals.
Selecting this menu item opens an editor you can use to to define
individual parameters. A password being used as the second
Individuals
password required to save changes to an individual record must also
have this function enabled (refer to Second Password Required for
Individuals on page 9-85 for more information).
The menu item Access Key/Card Translations.
Key/Card Translations Selecting this item opens an editor you can use to translate key/card
numbers
The menu item Access Options.
Options Selecting this menu item opens an editor you can use to customize
the individuals editor display parameters
The menu item Access Personnel Schedules.
Personnel Schedules Selecting this menu item opens an editor you can use to define
individual valid times of entry/exit
The menu item Access Recycle Bin and all parameters
associated with the recycle bin function.
Recycle Bin
The recycle bin can be used to temporarily store deleted Access
Control items.
Recycle Bin Purge Purge deleted Access Control items from the recycle bin
Function/Editor Action
Allow deleted Access Control items to be recovered from the recycle
Recycle Bin Restore
bin
The menu item Access Tenants.
Tenants Selecting this menu item opens an editor you can use to define
groups of individuals
DCU Access
The menu item Edit Controller Access Initiated Control.
Selecting this menu item opens an editor you can use to define
Access Initiated Control
access initiated control sequences for all points within the selected
DPI, MCI, or I/SITE LAN.
The menu item Edit Controller Door Schedules.
Door Schedules Selecting this menu item causes the Door Selection Summary to
open.
The menu item Edit Controller Doors.
Selecting this menu item opens an editor you can use to define the
Doors
door operating parameters for all doors within the selected DPI, MCI,
or I/SITE LAN
The menu item Edit Controller Personnel Schedules.
Personnel Schedules Selecting this menu item opens an editor you can use to define valid
entry/exit times for individuals
AMT
Acknowledge Acknowledge an alarm
Alarm Window View alarm messages
Archive Window View archived messages
Access the Camera Assignment editor. Refer to TCON301, TAC
Assign Camera to Point I/NET Seven Database Connectivity and Reporting, for more
information about CCTV-related 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
Function/Editor Action
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, TAC
Show Video I/NET Seven Database Connectivity and Reporting, for more
information about CCTV-related 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 configuration profiles using INETCFG
Exit Shutdown IO Server
Window
Allow AMT Alarm wnd. close Allow the user to close the AMT alarm window
Allow AMT Alarm wnd. move
Allow the user to move and size the AMT alarm window
and size
Allow AMT Event wnd. close Allow the user to close the AMT event window
Allow AMT Event wnd. move
Allow the user to move and size the AMT event window
and size
Allow AMT main wnd. close Allow the user to close the AMT main window
Allow AMT main wnd. move
Allow the user to move and size the AMT main window
and size
Allow I/NET to be closed Allow the user to close the TAC I/NET Seven main window
Allow I/NET to move and size Allow the user to move and size the TAC I/NET Seven main window
Allow all wnd. to be closed Allow the user to close all TAC I/NET Seven windows
Allow all wnd. to move and size Allow the user to move and size all TAC I/NET Seven windows
Allow graphics to be closed Allow the user to close graphic windows
Allow graphics to move and
Allow the user to move and size graphic windows
size
Allow tree wnd. to be closed Allow the user to close tree windows
Allow tree wnd. to move and
Allow the user to move and size tree windows
size
Seven Reports
Seven Reports Allow access to Seven Reports.
Station Selection
You may restrict controller access by assigning each controller a
password. When you combine this with preassigned password
levels, operators do not have to remember the controller password
when connecting to a password-protected controller. This speeds
up connection and simplifies day-to-day operation.
Preassignment of passwords is a three step process. The first step is
to assign the appropriate password level (Level 2/Level 3/Level 4) to
the desired host password in the host passwords DCU selection
editor. Secondly, assign the actual password and associated pass-
word level to each link/controller listed in the DCU passwords
editor. The third step is to assign the same password and associated
password level in the DCU passwords editor of the controller. Refer
to Controller Passwords in Chapter 5, Controller Functions.
Tenant/Group Selection
Tenant selection allows access control system password protection
for each tenant defined in the system. You may select from the
complete list of tenants, the maximum is 255 tenants. Only the
tenants selected will appear in the tenants, group, and individual
editors for an operator using this password.
Besides assigning full tenant access to a user, you can also limit the
users access to specific groups within select tenants. After logging
into TAC I/NET Seven, the limited-access user will be unable to
modify any parameters or access any TAC I/NET Seven features
associated with groups that have not been assigned to the user.
Refer to Limited-access Users on page 4-17 for more informa-
tion.
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.
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
Note: An example of limited-access users in provided in the Passwords
chapter of TCON299, TAC I/NET Seven Operator Guide.
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 remove allowed groups to and from the
individual, 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 TAC
I/NET Seven's main menu, the following restrictions will apply:
Can only see individuals associated with allowed groups.
Can only see doors associated with allowed groups.
Cannot Delete groups for which the user has read-only access.
Cannot Modify groups for which the user has read-only
access.
Can Add groups. The user will automatically receive full
access to the groups he adds. By default, no other users will
have access to groups added by this user (only a person with
password privileges can assign these groups to other users).
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.
File Formats
TAC I/NET Seven saves graphic pages and library symbols in
different formats than previous versions of TAC I/NET. Graphic
pages from earlier versions of TAC I/NET have a .pag file extension
and library symbols have a .bol extension. TAC I/NET Seven pages
will have a .gpg extension and library symbols will have a .gls exten-
sion. However, TAC 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 TAC I/NET Seven 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 referenced, TAC I/NET Seven will first attempt to open a .gpg
file of the same name. If a .bol file is being referenced, TAC I/NET
Seven will first attempt to open a .gls file of the same name.
For example: if a page marker links to a file named
c:\pages\mypage.pag, TAC I/NET Seven will first attempt to open
a file named c:\pages\mypage.gpg. If the file is not found, TAC
I/NET Seven will then search alternate paths for mypage.gpg
(refer to Alternate Graphic Paths below). If the result of this
search is unsuccessful, TAC I/NET Seven will open the file named
c:\pages\mypage.pag.
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.
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 TAC 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:
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.
Type Purpose
Network Functions
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.
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.
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.
Note: A change in the DCU time will result in the loss of all trend data that
has not yet been uploaded.
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.
date and time for the scheduled broadcast. This does not have to be
the same day as the date you want the special day schedule to go
into effect, this is simply the date when the broadcast will occur.
If a communications failure occurs and the system in unable to
broadcast the special day schedule to all selected controllers, it
displays the extent of this failure in the messages table and prints
the error message Special day lost along with the link and station
address (LLSS) of the failed transaction. Always check the messages
after you issue a special day broadcast to make sure the broadcast
was successful. In order to receive this message, the host worksta-
tions far left mask position in distribution group 1 must be acti-
vated.
Broadcast Failure
The system alerts you when it is unable to connect to a controller
that has been selected to receive the special day broadcast. At this
time you can try selecting the controller again or you can choose to
abort the procedure. In order to receive this message, the host
workstations far left mask position in distribution group 1 must be
activated.
Broadcast Review
If you are not sure which special day schedule you selected to be
broadcast, connect to the controller in question and inspect the
special day editor. Refer to Chapter 7, Point Extensions for details
on the special day and time scheduling editors.
Off-normal Points
Off-normal is another term used to describe points that are in an
alarm state. The off-normal points option in the Network Func-
tions editor allows you to choose which controllers will be interro-
gated for off-normal point summaries. The interrogation is
initiated, and off-normal points are displayed, when you select the
off-normal points option from the summary options menu. Refer
to the section on Summaries in TCON299, TAC 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.
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-
tion of the TAC I/NET Seven 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.
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.
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
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.
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.
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.
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.
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 TAC I/NET
Seven 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, TAC
I/NET Seven will present a list of the remote sites defined on this
host.
5
50
Controller Functions
Controller Passwords
TAC I/NET Seven 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 preassignment function. Password preassign-
ment enables an operator to access assigned controllers without
entering the controller passwords.
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-
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.
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.
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.
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
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 a TAC I/NET
Seven host.
Refer to Reliable Messaging on page 3-7 for more information
about this TAC I/NET Seven 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.
Daylight Savings
Use this function to enter the beginning and ending dates and
times for Daylight Savings time, using the following parameters:
Month (112): This is the month daylight savings time
begins/ends. January is month 1, February is month 2, and so
on, ending with December as month 12.
Week (15): This is the week daylight savings time
begins/ends.
Enter a 1 if the daylight savings start falls during the first
seven days of the month (17).
Enter a 2 if the daylight savings start falls during the
second seven days of the month (814).
Enter a 3 if the daylight savings start falls during the third
seven days of the month (1521).
Enter a 4 if the daylight savings start falls during the
fourth seven days of the month (2228).
Enter a 5 if the daylight savings start falls after the 28th
day of the month.
Day (17): This is the day daylight savings time begins/ends.
Sunday is day 1, Monday is day 2, and so on, ending with
Saturday as day 7.
At 2:00 a.m. (02:00) on the day specified, the clocks will move
forward (begin date) or backward (end date) one hour.
Program Extensions
Use this section to activate or deactivate specific control extensions
for all points in this controller. The parameters displayed are
dependent upon connected controller and may not always be avail-
able.
Note: Activating these functions does not add the related extension to any
point(s) in the controller. Use the appropriate extension editor to
specify the appropriate extensions to add to each point.
Time Scheduling
Activate or deactivate Time scheduling for points in this
controller.
When activated, all the time scheduling program extensions in this
controller are selected. Once activated, the controller looks back as
far as the previous midnight to determine the point state during the
next minute and issues the proper command.
When time scheduling is deactivated and the controller has time
scheduling programs working, the individual loads remain in the
state that existed when the program was turned off.
Temperature Control
Activate or deactivate Temperature control for points in this
controller.
If this function is not activated for the controller, the individual
temperature control extensions on the attached point(s) will not be
activated.
Demand Control
Activate or deactivate Demand control for points in this controller.
If you deactivate this function, the demand program ceases. All
loads that were currently shed by the demand program are restored
after honoring their minimum off (minimum trip or close) time as
defined for the individual point. Even if turned off, the demand
program will continue to gather KW and KWH data.
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.
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.
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.
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). TAC I/NET Seven 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
() the Restore from Local Host option on any hosts that should
have the ability to perform Automatic DPU restores to this link.
Ethernet LAN
TAP
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 TAC I/NET Seven Performs the Automatic DPU Restore
To ensure that door controllers receive updated databases, any TAC
I/NET Seven 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 TAC I/NET Seven 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 (), 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.
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 TAC 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 TAC I/NET LAN communica-
tions, 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 TAC I/NET Seven software.
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, TAC I/NET Seven restores
software from the DATA subdirectory defined during TAC I/NET
Seven 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.
Note: Each time you exercise this option a copy of the midnight data is
placed in the host.
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.
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
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.
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.
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:
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.
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.
Converter
Count Range
Type
8-bit 0 255
12-bit 0 4,095
16-bit 0 65,535
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:
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.
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, TAC I/NET Seven 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.
Ohms inputs:
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.
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.
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.
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
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
Table 5-10. 7756 PCU (Lower I/O Board) and 10K Thermistor
Lookup Tables
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
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.
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
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.
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).
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.
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.
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, TAC I/NET Seven Forms and Worksheets, to organize
and design the event sequences you need at your facility. Event
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.
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.
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.
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
Skip if zero (nonzero), this 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.
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
Report 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.
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.
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.
Point Selection
In addition, you must specify the points to be graphed on the trend
plot. Up to six points may be selected.
You may add a point, modify a selected point, or delete a selected
point. You may use the modify option to replace a selected point
with a different point.
Point Definition
The point definition screen allows you to specify how the data for
the point will be displayed.
The top portion of the window shows the point address and name
of the selected point. Use the Select button at the bottom of the
screen to choose the desired point (see Point Selection on page
5-46).
The point definition options are as follows.
Pen Color The color for the data line for this point. Select
one of the sixteen colors available. The default is yellow for all
points. If you do not change the default color, all lines will be
plotted in yellow.
A box next to the pen color field displays a sample of the
selected color.
Note: The plot display background is black. A black line on the display will
not be visible. A printed plot will have blank paper as the back-
ground. Choose your colors accordingly.
Axis The y-axis scale used by this line. Specify either the
Y1 or Y2 axis for each point. (Refer to Plot Definition on
page 5-43 for a discussion of the Y1 and Y2 scales.)
Print Indicates whether this line will appear on a printed
plot. If this box is not selected, the line will appear on the
screen plot, but will not be included in a printed plot.
Point Selection
The point selection screen is the same one used in other applica-
tions. It is divided into four main windows. The first window, in the
upper left corner, will display the trended points from the
connected controller. Only points with a trend sampling extension
will appear.
The other three windows allow you to specify a controller. The
trended points from each controller will appear in the designated
window. Use the Station button at the bottom of the screen to
select a controller for display for each window.
You may select a point from any quadrant, or enter the point
address in the boxes at the bottom of the screen. The full point
address, including point type, is required.
Link The LL portion of the LLSSPPBB PT address for the
desired point. This field is automatically entered if you select a
point from one of the four quadrants.
Station The SS portion of the LLSSPPBB PT address for
the desired point. This field is automatically entered if you
select a point from one of the four quadrants.
Point The PP portion of the LLSSPPBB PT address for the
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.
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
Note: These changes affect the current plot display only. They do not modify
the plot definition.
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.
6
28
Input and Output Points
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)
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.
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.
Maximum
Controller Minimum Pulse Duration Comments
Pulse Rate
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)
1 1
2 2
4 3
8 4
16 5
32 6
64 7
128 8
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.
* = 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.
Forms are available to help you in planning and entering your point
parameters. These forms can be found in TCON157, TAC I/NET
Seven 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.
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 TAC I/NET system (full globalization).
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.
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.
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.
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.
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
TAC I/NET Seven and can be any value.
Note: A cell number of zero indicates that no cell number is assigned, and
no SevenTrends data will be sent to the host workstation.
State Descriptions
This field is used with DI, DA, DM, DC, and DO point types only.
You should select the line number corresponding to the first line of
the state descriptor set you want to use to describe this point. This
will be any even number between 0 and 30, assuming you began
entering state description pairs on line zero. For multiple-bit DI
and DA points, the number entered here is the first state descrip-
tion of the four (2-bit point) or eight (3-bit point) state descrip-
tions being used. Refer to State Descriptions in Chapter 5,
Controller Functions.
Number of Bits
This field is used with DI and DA point types only. Select 1, 2, or 3
to describe the number of bits monitored by the DI or DA point.
1-bit points are by far the most common but 2-bit and 3-bit points
are sometimes necessary. You should be familiar with the point as
it exists in your system and therefore you should know the number
of bits required before you get to this stage in developing your data-
base. Each bit represents one contact in one of two states: 0 (open)
or 1 (closed).
1-bit
Using one bit results in two states: one contact in a 0 or 1 state.
What these states are depends on your system, how it is wired, and
the nature of the discrete point.
2-bit
Using two bits results in four states: two contacts, each in a 0 or 1
state (2 2 = 4). Because there are two bits there are four possible
permutations, here listed in their binary order: 00, 01, 10, and 11.
A 2-bit input requires 2 consecutive bit offset addresses, but only
the first point address must be defined in the database. You must
remember not to assign the second address to another point. The
addresses used for a 2-bit DI must be consecutive and must contain
the same point number.
You must also reserve four consecutive state descriptions, one for
each of the possible permutations listed above. You need to take
this into account when you first enter state descriptions. You need
to have four together that make sense for your 2-bit point. You
enter the first of the four into the state description field when you
define the point and the system automatically uses the next three
state descriptions for the point.
3-bit
Using three bits results in eight states: three contacts, each in the 0
or 1 state (2 2 2 = 8). Because there are three bits there are eight
possible permutations, here listed in their binary order: 000, 001,
010, 011, 100, 101, 110, or 111.
A 3-bit input requires three consecutive bit offset addresses, but
only the first address must be defined in the database. The point
address selected for multiple bits must be located in a controller
with sufficient available addresses. The second and third addresses
must fall within the same point number and cannot be used for any
other purpose. For example, in a 7716 controller, if you define 0004
DI as 3-bit, then hardware inputs 0005 DI and 0006 DI must also
be available.
You must also reserve eight consecutive state descriptions, one for
each of the possible permutations listed above. You need to take
this into account when you first enter state descriptions. You need
to have eight together that make sense for your 3-bit point.
Example of a multi-bit point: You have a fan that has four possible
operational modes: OFF, LOW, MEDIUM, and HIGH. Each time
the fan moves to a different state (00, 01, 10, or 11) the appropriate
state description is displayed next to a point icon on a graphic
system page, for example. A more complicated device might have
eight possible states.
Normal State
This field is used with DA point types only. Select 1 (normally
closed) or 0 (normally open) to indicate the normal state of this
point.
You must know how your system is wired before you can enter a
number here. The normal state is displayed in green. The opposite
Alarm state is displayed in flashing red.
Alarm Delay
This field is used with DA, DM, AI, and GI point types. Enter a
number between 0 and 32,767. This is the number of seconds the
system must continuously detect an alarm condition before
reporting it. Any return to the normal state during the specified
alarm delay period resets the counter.
Control Description
This field is used with DC and DO point types only. Select a
number between 0 and 15. This is the first line number of the
control description pair (STRT/STOP, ON/OFF, etc.) entered in the
Station Parameters editor. This determines the control command
(0/1) issued to the associated discrete output point. Refer to
Control Descriptions in Chapter 5, Controller Functions.
Momentary Duration
This field is used with DC and DO point types only. Enter a
number between 0 and 2.55. This is the duration (in seconds)
during which the start or stop output contact/relay is energized
when the appropriate command is issued.
Note: This function is not available on DO points in UC, MR, and ASC
products.
Note: TAC I/NET Seven 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.
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
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).
Conversion Equation
This field is used with AI, GI, AO, GO, and PI point types. Select
Linear or Flow. This designates the equation the system will use
when calculating conversion coefficients (see Conversion Coeffi-
cients Tables in Chapter 5, Controller Functions).
Engineering Units
This field is used with AI, GI, AO, GO, and PI point types. Select a
number between 0 and 15 that corresponds to the line number of
the engineering unit table (defined in the Station Parameters
editor) containing the unit you want to describe the value of this
point. Refer to Engineering Units Table in Chapter 5, Controller
Functions for more information.
Conversion Coefficients
This field is used with AI, GI, AO, GO, and PI point types. Select a
number between 0 and 15 that corresponds to the line number in
the conversion coefficients table (defined in the Station Parameters
editor) containing the slope (m) and offset (b) coefficients you
wish to use with this point. Refer to Conversion Coefficients
Tables in Chapter 5, Controller Functions for information on
calculating and entering conversion coefficients.
Offset
This field is used with AI, GI, AO and GO point types. Enter a
number between 128 and 127. This is the number of offset equip-
ment unit value counts required to eliminate sensor input or trans-
ducer output error.
Use this parameter to calibrate sensors or to adjust for increased
resistance due to long wire runs. To calculate this number, divide
the actual error in reading by the m value of the appropriate
conversion coefficient pair.
To compensate for sensor error, enter the same count value, but
with an opposite sign. For example, enter an offset value of +15
counts to compensate for a sensor error of 15 counts. Refer to
Digital Input (GI) Points on page 6-2 and Digital Output (GO)
Points on page 6-6 for a discussion on equipment unit value
counts.
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.
Lookup
Controller Type Used For
Table #
Accumulator Type
This field is used with PI point types only. Select the type of accu-
mulator. TAC I/NET Seven provides three separate and distinct
types of accumulators:
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.
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, 2-Resistor, or 3-resistor configuration.
The 3-resistor setting is only used for an intrusion alarm system.
Refer to TCON314, Intrusion Alarm System Installation Guide, for
a description of this type of supervision.
7
52
Point Extensions
A A D D D D D G G P
Ext Description Pg
I O A C I M O I O I
A A D D D D D G G P
Ext Description Pg
I O A C I M O I O I
You may wish to use the forms provided in TCON157, TAC I/NET
Seven Forms and Worksheets, to help you design and define point
extensions. This simplifies the final data entry process.
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.
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.
Use internal points when the result of the calculation is used for
informational purposes, such as an intermediate step in a chain of
calculations, as an input to a DDC module, as an initiator for an
event sequence, or as a repository for an accumulation.
The calculated state or value must match the point type to which it
is assigned. If you expect your calculation to produce an analog
value you must direct it to an analog point or a PI (accumulator)
point. If you expect your calculation to produce a binary answer
(true or false, 1 or 0), you must direct it to a discrete point.
Each calculation is processed in ascending point address order and
at the scan interval defined for the target point address in the resi-
dent input/output editor where you originally defined the point. If
two points (input and output) have been defined at the same
address, and both have been assigned the same scan rate, the
output point calculation will be processed first, followed by the
input point. It is sometimes helpful to make use of the sequential
scan order to detect changes that occur between scan updates or
when you wish to note changes in one direction only. For example,
you may wish a PI point to accumulate only starts or stops.
The state or value of a calculation is reinforced each time the point
is scanned. If you wish to force a point that is controlled by a calcu-
lation to a specific state or value, you must first put the point in test
or manual mode, or control it with one of the lock commands in
the event definition extension editor.
Operators
Calculation parameters (points and constants) are connected by
operators. There are four main types of operators: arithmetic, rela-
tional, boolean, and function. Arithmetic operators perform a
mathematical calculation. Relational operators evaluate the rela-
tionship between two values. Boolean operators evaluate a condi-
tional statement involving two or more values, and return a true
or false condition (1 or 0). In addition, special function operators
have been included to perform predefined calculations.
The following table lists the available operators, along with their
data entry symbol, type, and rank (16). A higher rank number
indicates that the operator or function is performed in an equation
before an operator with a lower rank. Each operator is described in
detail on the following pages.
Boolean Operators
Boolean operators evaluate the stated condition, and return a
true or false response. Use these operators in a calculation to
produce a discrete state, either a 0 or a 1. A 0 corresponds to false
and a 1 corresponds to true.
Each section of the boolean expression is called a statement. The
statement may be a single term, such as the state of a discrete point,
or a complex equation, such as a comparison of several values or a
calculation. For complex expressions, it is recommended that you
use parentheses to define the statements.
And This operator requires all statements connected by AND
to be true before the total expression is true. If any statement is
false, the entire expression is false. An example AND expression
is shown below.
(P0=P1)&(P2*C0<C1)
Exclusive or This operator allows only one statement to be true
in order for the expression to be true. If multiple statements are
true, or all statements are false, the expression becomes false. An
example EXCLUSIVE OR expression is shown below.
(P0=P1)^(P2*C0<C1)
Or This operator allows two or more statements connected by
OR to yield a true expression even if only one of the statements is
true. The expression is only false if none of the statements are true.
An example OR expression is shown below.
(P0=P1) -| (P2*C0<C1)
Table 7-3 below illustrates how the AND, OR, and EXCLUSIVE OR
operators work together. In this table, A represents the first state-
ment, and B represents the second statement.
Relational Operators
Relational operators are very similar to boolean operators. These
operators also evaluate the stated condition, and return a true or
false response. Using these operators results in a calculation that
produces a discrete state, either a 0 or a 1. A 0 corresponds to false
and a 1 corresponds to true.
Equal This is a relational equality: 7=7, 1=1. An example
expression is shown below.
(P0+P1)=P2
Greater than This is a relational greater than: 78 > 10. An
example expression is shown below.
(P0+P1)>P2
Arithmetic Operators
Arithmetic operators are used to perform basic mathematical
calculations. The result may be the value of the point itself, or may
be part of a complex calculation using any combination of boolean,
relational, and function operators.
Addition This is simple addition, 1+2. An example expression
is shown below.
P0+C0
Subtraction This is simple subtraction, 12. An example
expression is shown below.
P0C0
Division This is simple division, 1/2. An example expression is
shown below.
P0/C0
Multiplication This is simple multiplication, 1*2. An example
expression is shown below.
P0*C0
Function Operators
Function operators are used to perform specific, predefined calcu-
lations. Some function operators (such as HIGH, LOW, AVG,
SUM, etc.) are designed to work only with numeric values. Other
function operators (such as DAY, MPM, etc.) are designed to work
on DCU dates or times.
Average of values This function calculates the average value
from a list of up to 10 parameters (points and/or constants). If one
of the parameters fails (i.e., a sensor goes into an old data condi-
tion), the value of that parameter will not be included in the
average calculation. An example expression is shown below.
AVG(P0,P1,P2,P3,P4)
Day of month This function calculates the day of the month in
the DCU. This function returns a value between 1 and 31. An
example expression is shown below.
DAY<=C0
Day of week This function calculates the day of the week in the
DCU. This function returns a value between 1 and 7 (1 = Sunday,
2=Monday, etc.). An example expression is shown below.
DOW<=C0
Highest value This function selects the highest value from a list
of up to 10 parameters (points and/or constants). You may also
establish a minimum value by entering a constant in the parameter
list. For example, if you are selecting the highest room temperature
for a group of offices, you might define the constant as 72 degrees.
If all the office temperatures are lower than 72, then 72 becomes the
value of the calculation. This feature is a useful safeguard to prevent
unnecessary heating if a sensor malfunctions and produces an
excessively low temperature. An example expression is shown
below.
HIGH(P0,P1,P2,P3,P4,P5,C0)
Hour This function calculates the hour in the DCU. This func-
tion returns a value between 0 (zero) and 23. An example expres-
sion is shown below.
HR<=C0
Julian date This function converts the date in the DCU to the
Julian date (an integer). The Julian date is a number between 1 and
366: January 1 is day 1, December 31 is day 365 (day 366 in leap
year). The computer cannot manipulate or compare dates
(MM/DD/YY) as it can simple constants. For example, the
computer cannot subtract March 5 from July 24; but it can subtract
64 from 205. This is a convenient method for performing calcula-
tions involving dates rather than trying to manipulate them in
terms of months and weeks. An example expression is shown
below.
JULD<=C0
Lowest value This function selects the lowest value from a list of
up to 10 parameters (points and/or constants). You may also estab-
lish a maximum value by entering a constant in the parameter list.
For example, if you are selecting the lowest room temperature for a
group of offices, you might define the constant as 85 degrees. If all
the office temperatures are higher than 85, then 85 becomes the
value of the calculation. This feature is a useful safeguard to prevent
unnecessary cooling if a sensor malfunctions and produces an
excessively high temperature. An example expression is shown
below.
LOW(P0,P1,P2,P3,P4,P5,C0)
Minute of hour This function calculates the minutes after the
hour in the DCU. This function returns a value between 0 (zero)
and 59. An example expression is shown below.
MIN<=C0
Minutes past midnight This function calculates the minutes
elapsed since the previous midnight in the DCU. The system
displays a value between 0 (zero) and 1,439. There are 1,440
minutes in a 24-hour day. The computer cannot manipulate or
compare times in hours and minutes as it can simple constants. For
example, the computer cannot subtract 6:15 a.m. from 8:30 a.m.,
but it can subtract 375 minutes from 510 minutes. You simply
convert the time at which you want the point controlled by this
calculation to do something (turn on/off, display a message, etc.)
into minutes. An example expression is shown below.
MPM<=C0
Month This function calculates the month of the year in the
DCU. The system displays a value between 1 and 12 (1 = January,
2=February, etc.). An example expression is shown below.
MO<=C0
Old data This function returns a 1 if the state/value of the
monitored point (P0) is questionable (e.g., an AI point falls below
its low sensor limit). The operator returns a 0 if the state/value of
the monitored point is at an acceptable value (e.g., an AI point
returns to a value within the sensor limit values). An example
expression is shown below.
OLD(P0)
Square root This function returns the square root of a given
number. This is the number which, when multiplied by itself,
results in the original number (for example, 9 = 3 ). An example
expression is shown below.
SQRT(P0)
Time to start This function returns the number of minutes (0
1439), until the point is scheduled to be started by an automatic
time schedule. It returns a 0 if the next scheduled action is not a
start command (this usually means that the previous action was a
start command). It returns a question mark (?) if the point does
not have a time scheduling extension appended to it. Although this
function is designed primarily for optimized start commands, it
will work with regular start commands as well. An example expres-
sion is shown below.
TTS(P0)
Dew point This function calculates the dew point when you
supply dry bulb temperature and relative humidity. Example
expressions are shown below.
Consumption (CN)
The consumption editor is available on all controllers. This point
extension can be used with PI (accumulator) points, such as KWH
meters.
Adding this extension to a point requires approximately 8 bytes of
memory.
Add this extension to a PI point if you want to direct the accumu-
lated value of a PI point to a particular consumption cell for
storage, and zero the value stored in the DCU for the PI point at
midnight.
Note: Restoring the DCU will reset the accumulated consumption data to
zero (0). Consumption data is always reset to zero (0) at midnight,
even if the PI point is in the Test mode.
Note: You must also define the trend in the host workstation. Refer to
Chapter 16, SevenTrends, for more information.
Demand Meter
When you select demand control for a point, you must enter the
demand metering information for that point. The entry fields for
this extension editor are as follows:
Demand interval The demand interval is a time period,
measured in minutes, over which the calculation of demand is
based. This is determined by the power-generating public
utility or distribution authority. You may enter any value
between 5 and 90, in five-minute increments (5, 10, 15, 65, 70,
etc.).
Note: You must also define the trend in the host workstation. Refer to
Chapter 16, SevenTrends, for more information.
Note: If you enter constants for the KW demand setpoint in the schedule
portion of the demand editor, the shed level takes effect after the date
in the editor, not before. For example, a setpoint entry of 500 on
01/31 will be in effect from 01/31 until the next entered date (such as
2/28), not from 01/01 to 01/31.
Note: Priority 7 loads will be shed only if the predicted demand exceeds the
emergency shed level setpoint AND all loads with priority 1 through
6 have either been shed or are not available for shedding (see
Selecting Loads to Shed in Chapter 8, Dynamic Control).
Note: The emergency shed level is always honored. If the override control
point is in the energized (1) state, both the override and emergency
setpoints will be used. If the override control point is in the deener-
gized (0) state, both the normal and emergency setpoints will be used.
Note: The shed level takes effect after the date in the editor, not before. For
example, a setpoint entry of 500 on 01/31 will be in effect from 01/31
to the next entered date (such as 2/28), not from 01/01 to 01/31.
Demand Loads
Use the Demand Loads Screen to specify which loads (DO and DC
points) to shed, in what order they should be shed, and the size of
the load. Load size lets TAC I/NET Seven determine the fewest
number of loads that can be shed to bring demand under the
acceptable limit. You may assign up to 127 demand loads to each
demand meter, and up to 255 demand loads to each controller.
Please fill out the Demand Loads form provided in TCON157, TAC
I/NET Seven Forms and Worksheets, before entering data in this
screen.
The entry fields for this section of the extension editor are shown
below:
Load The name or address of the point you wish to shed if
it becomes necessary. Enter only points that may be shed.
Caution: Do not enter a point in this portion of the demand control editor if it
is extremely critical (i.e., you would rather go over your emergency
demand setpoint than shut off the device controlled by the point).
Note: This parameter applies only to off time due to load shedding. It does
not affect off time due to time scheduling or temperature control
functions.
Elevator (EL)
The elevator extension editor is available on 7791, 7793, and 7798
controllers. This point extension can be added to any door point
(DO point with bit offset BB 08 or 09) that is defined as an elevator.
Adding this extension to a point requires 2 bytes of memory.
Adding enable and select points consume 8 bytes of memory.
The elevator control function works in conjunction with the access
control parameters and personnel schedules to control access to
elevator floors. In addition to supplying the door parameters at the
door controller level, it is necessary to supply the controller with
the information required to associate an elevator reader with the
discrete output points that enable the floor relays, and the discrete
input points that monitor the button selection. The process
controlled by this editor is as follows:
1. The access key or card is accepted by the appropriate reader.
2. The appropriate DO points for that user are activated, ener-
gizing the designated elevator floor buttons.
3. User pushes one of the elevator buttons.
4. The DI point for the floor button selected in the
DPU/SCU/DCU changes states, and the elevator allows access
to the selected floor.
Note: This field is on the summary page, and affects all elevators.
Event Point
Description
Type Type(s)
Any alarm, high or low limit, causes this point to initiate an event sequence
Alarm AI, GI
or event action.
The high alarm limit you specified when you defined the point in the Resident
High limit
AI, GI I/O Points editor is used here. If the value of the point is greater than the high
alarm
alarm limit, this triggers an event sequence or event action.
The low alarm limit you specified when you defined the point in the Resident
Low limit
AI, GI I/O Points editor is used here. If the value of the point is less than the low
alarm
alarm limit this triggers an event sequence or event action.
Event Point
Description
Type Type(s)
Return to If a point value returns from the low limit or high limit alarm range, this triggers
AI, GI
normal an event sequence or event action.
This is typically a different value than high limit alarm value, although it
High value AI, AO,
functions similarly. When the point value rises above the value you define as
crossing GI, GO
the high value crossing, this triggers an event sequence or event action.
This is typically a different value than low limit alarm value, although it
Low value AI, AO,
functions similarly. When the point value falls below the value you defined as
crossing GI, GO
the low value crossing, this triggers an event sequence or event action.
State change requires a point to change from one state to another to initiate
State an event sequence or event action. Note that the event occurs in both
DI, DO
change directions; i.e., when the discrete point changes from 0 to 1 and when it
changes from 1 to 0.
Specified state initiates an event sequence or action when the point
transitions to a specific state (0 or 1). For specified state events, the point
Specified
DI, DO must have been in the opposite state for at least one scan and then
state
transitioned to the specified state before the DCU will determine that the
event occurred.
This event type is available for DO points; however, it is only functional with
Door
DO door points. Door forced initiates an event sequence or action when the door
forced
point (BB = 08 or 09) registers that the door has been forced open.
This event type is available for DO points; however, it is only functional with
door points. Door open too long (DOTL) initiates an event sequence or action
Door open
DO when the door point (BB = 08 or 09) registers that the door has been open for
too long
too long. The time setting for the open duration is set in the door parameters
editor
This event type is available for DO points; however, it is only functional with
Door door points. Door normal initiates an event sequence or action when the door
DO
normal point (BB = 08 or 09) returns to a normal condition after previously being in
an abnormal (door forced or DOTL) condition.
This event type is available for DO points; however, it is only functional with
Bad card door points. Bad card read initiates an event sequence or action when the
DO
read door point (BB = 08 or 09) card reader is unable to determine the validity of
the presented card.
This event type is available for DO points; however, it is only functional with
Request to
DO door points. Request to exit initiates an event sequence or action when the
exit
door point (BB = 08 or 09) is unlocked from a push-button or motion detector.
This event type is available for DO points; however, it is only functional with
Door
DO door points. Door relocked initiates an event sequence or action when the
relocked
door point (BB = 08 or 09) is re-locked after being opened.
Event Point
Description
Type Type(s)
This event type is available for DO points; however, it is only functional with
Mode APB door points. Mode APB reset initiates an event sequence or action when the
DO
reset mode schedule on the door point (BB = 08 or 09) resets all anti-passback
flags.
This event type is available for DO points; however, it is only functional with
Mode PIN door points. Mode PIN enable initiates an event sequence or action when the
DO
Enable mode schedule on the door point (BB = 08 or 09) changes the door state to
require a personal identification number (PIN) for entry or exit.
Lighting Circuits
A lighting circuit is a single point in the controller. This may be a
single source (lamp), or several sources that have been daisy-
chained together into the same controller point (for example, a
floor within a facility). The field entries for lighting circuits are
described below:
Delay before off The number of minutes (0127) after the
wink cycle ends before the point turns off.
On duration The number of seconds (1255) for the
length of the on part of the wink cycle.
Note: This Override Input is the override point specified for the lighting
zone (see Override Billing (OB) on page 7-33). It is not related to
the Override Billing extension available with the 7750 Building
Manager.
Delay before off 10 The grace period is ten minutes after the wink
cycle finishes.
On duration 29 The lights are on for 29 seconds at a time during
the wink cycle.
Off duration 1 The lights will be off for one second each time.
Wink cycles 2 The lights will wink off two times.
Control sources Activate Automatic Time Scheduling as a control
source, to indicate that ATS can initiate a wink
cycle. Override input is also selected (by default),
so that a wink cycle can also be initiated when the
override time period expires.
Based on these entries, the lights will wink off for 1 second at
7:00:00 p.m. (19:00:00). They will come back on at 7:00:01
(19:00:01) and remain on for 29 seconds. They will go off again at
7:00:30 (19:00:30), and back on again at 7:00:31 (19:00:31).
Another on cycle of 29 seconds completes the wink cycle at 7:01:00
(19:01:00). Then the 10-minute delay begins, with the lights ulti-
mately going off (assuming no override is initiated) at 7:11:00
(19:11:00).
Note: If a tenant activates the override point at any time during the wink
cycle, the wink cycle is halted and the override timer goes into effect
(if the override type is set to Timed). If override input is activated
as a control source input, the wink cycle will begin again at the end of
the override period.
Lighting Zones
A lighting zone is a group of lighting circuits that can be controlled
together. A lighting circuit can belong to more than one lighting
zone. The lighting zone point must use addresses LLSS1200
LLSS1507.
When you add the lighting zone (LZ) extension to the DO point,
you must define the override settings for the zone before you can
select the zones circuits or time schedule. The override function
allows you to energize all the circuits in the lighting zone, regardless
of the zone time schedule. The override is assigned to a zone, and
affects all circuits assigned to that zone.
Note: If a circuit is assigned to multiple zones, the circuit will remain ener-
gized as long as any override is in effect.
Note: In the ATS editor, lighting zone time schedule On commands will
appear as Start, and Off commands will appear as Stop.
Note: The minimum trip and minimum close times for discrete outputs in
other DCUs controlled via the 7750 DCU are not honored when the
Building Manager initiates control to these output points.
Access Codes
Use this option to establish access codes for each zone. These are
used as passwords when telephoning the 7750 to initiate an over-
ride. Enter a code containing up to six digits for each zone. This is
the number that must be entered from a touch-tone phone in order
to access and override the normal time schedule for a specific zone.
The field entries for access codes are described below:
Non-billable A non-billable access code is typically used by
night cleaning or maintenance personnel when they dial up
the 7750 to place the zone requiring cleaning or maintenance
into override. The amount of non-billable electrical
consumption and override time is accumulated on a daily
basis for each zone and is updated at midnight. If a non-bill-
able override and a billable override overlap each other, the
non-billable override always takes precedence.
Interrogate A code containing up to six digits for interro-
gate access. This code lets you call the 7750 and inquire about
the state or value of any input or output point on the LAN.
You must know whether the point is an input or output, and
its eight-digit point address. This information must be
entered into the system from a touch-tone phone when you
want to interrogate the point.
Control A code containing up to six digits for control
access. This code lets you call the 7750 and control any output
point on the LAN to a certain state or value. You must know
the eight-digit point address of the output point because you
will need to enter it into the system from a touch-tone phone
when you want to control the point.
Equipment Mapping
Use this option to specify the load size of the equipment point
being controlled, the base load, and the percentage of the total load
that can be assessed to each zone. It also lets you specify how the
points are distributed among multiple zones. This makes it easy for
you to bill the appropriate users/tenants for energy use during the
override period.
Note: Only those points defined in the resident I/O points editor as indirect
and with a non-zero bit offset (BB = 0109) can be equipment
points.
Override Parameters
Use this option to specify distribution group, distribution mask,
cell priority, cell number, and to specify the indirect points
controlled by the zone point. The override parameters screen lets
you assign up to 12 points to each zone for override control.
The override parameters screen also lets you specify a wink interval
to notify the user or tenant that the override period is about to
expire. This wink function is similar to the wink function in
lighting control (see Lighting Circuits on page 7-29).
Note: Only those points defined in the Resident I/O Points editor with zero
bit offset (BB = 00) can be zone points.
Note: You must also define the trend in the host workstation. Refer to
Chapter 16, SevenTrends, for more information.
Note: The equipment will wink off only once. Unlike the wink function for
lighting control, you cannot specify the number of winks.
Runtime (RT)
The runtime editor is available in all controllers. This point exten-
sion can be used with DI, DO, and DC points.
Adding this extension to a point requires 13 bytes of memory.
Use this extension editor to define runtime parameters for a
discrete input or output point so that daily runtime information
can be collected. This information can then be used in SevenTrends
reports.
The field entries for the runtime editor are described below:
On state A 0 (open) or 1 (closed) that indicates the ON
state for this point. This determines when runtime data is
accumulated for this point.
Distribution group and Mask The distribution group (1
4) and active mask position(s) desired. Refer to Masking in
Chapter 3, System Messages.
Priority The priority for sending information from this
extension editor. The options are None, Routine, Priority, and
Critical. Refer to Priorities in Chapter 3, System Messages.
Cell number This field is used for grouping SevenTrends
data in displays and reports. Enter a number between 1 and
1,023. You must assign a value other than zero in order for
SevenTrends to store the trend information. Otherwise, this
field is not used in TAC I/NET Seven and can be any value. A
cell number of zero (0) indicates that no cell number is
assigned, and no SevenTrends data will be sent to the host
workstation.
Note: You must also define the trend in the host workstation. Refer to
Chapter 16, SevenTrends, for more information.
Note: The two lookahead entry fields below are used for adaptive optimiza-
tion (OSTART and OSTOP), a function that monitors HVAC system
performance to determine when to begin optimized start or stop
actions. These functions require an ATS extension on the output
point.
Note: The space temperature must meet the cooling/heating target temper-
ature sometime after the optimized start time, in order for Ostart to
work properly. This is required before the Start Performance
Constant calculation can begin its minutes/degree processing. The
optimized start command will not begin to advance the start time
until this calculation occurs.
Note: If the device has both heating and cooling setpoints, a mode decision
(heating vs. cooling) is made automatically, based on the position of
the space temperature as compared to the setpoints. If the space
temperature is below the heating setpoint, the mode is selected as
heating; if the space temperature is above the cooling setpoint, the
mode is selected as cooling.
Caution: The heating setpoint may never be greater than the cooling setpoint.
There must be a deadband area (0.5 minimum) of no control
between the heating and cooling zones, so that the controller is aware
of the transition from heating to cooling or vice versa. The heating or
cooling zone range is defined as the target of the differential
range. This applies to both heating and cooling ranges.
Note: You must also define the trend in the host workstation. Refer to
Chapter 16, SevenTrends, for more information.
Caution: When this number is reached, the DCU discards the oldest trend
sample to make room for the newest sample. Make sure SevenTrends
data has previously been stored by the workstation to prevent loss of
data.
Note: This editor assumes a 1 to be the ON state. If the point has 1 as the
OFF state (0 as ON state), you must define an internal point
containing a simple negate calculation that reverses this, and use
the address of this internal point in the trend sampling editor. Refer
to Calculations (C) on page 7-4 for more information on calcula-
tions.
Field Description
This action energizes a point controlled by this schedule at the desired time of day. This
Start
action issues the first control command (0 or 1) of the point.
This action deenergizes a point controlled by this schedule at the desired time of day. This
Stop
action issues the second control command (0 or 1) of the point.
This action lets you select the time you wish duty cycling to start, and indicates the duty
cycle pattern (minutes off, minutes on) for the point controlled by this schedule. A duty cycle
pattern might be 10 minutes off and 50 minutes on. Once started, the cycle repeats
indefinitely until it is overridden by a start or stop command or another cycle command. The
stop command is always issued at the beginning of a cycle period, followed by the start
command.
Cycle
Room temperature is not a factor in a cycle. A cycle turns a point on or off regardless of the
current temperature. The advantage of a cycle command is that it gives you the opportunity
to save energy and money by staggering the on and off times of different pieces of
equipment. If everything comes on at once, this creates a surge in your energy demand and
costs you money. Staggering times decreases the total energy demand at any given time
and can save you money.
Optimized Start is a special start command related to room temperature and outside air
temperature. When you use optimized start, the time you enter is actually the target
occupancy time. The system actually starts up the device before this time in order to achieve
the desired temperature at the target occupancy time. The target temperature information
Ostart
is defined in the temperature control extension editor. Refer to the section on Temperature
Control (TC) for detailed information on target temperature selection and scheduling. Refer
to Temperature Control in Chapter 8, Dynamic Control, for additional information on actual
optimized start operation.
Optimized Stop is a special stop command related to room temperature. When you use
optimized stop, the time you enter is actually the target vacancy time. This lets the system
shut off an HVAC unit while the room is still occupied but maintain the desired temperature.
Ostop
This saves the energy (and dollars) required to run the fan or HVAC unit for the extra
minutes involved. Refer to Temperature Control in Chapter 8, Dynamic Control, for
additional information on actual optimized stop operation.
Optimized cycling retains the advantages of regular duty cycling but gives you some control
over room temperature. You define the cycle start time and number of minutes off and on
just as you do for a normal duty cycle. Optimized duty cycling shortens the off time of the
cycle and lengthens the on time of the cycle if the temperature deviates from the target
temperature defined for the point. The target temperatures and cycle modifiers are entered
Ocycle in the temperature control extension editor.
The time subtracted from the off portion of the cycle is added to the on time. This keeps the
total cycle time the same no matter how great the temperature deviation and the resulting
compensation. This is important in maintaining a staggered order of on/off times and the
resulting energy savings. If the temperature drifts from the target enough, the point
ultimately remains ON: cycle ON time equals the maximum and cycle OFF time equals zero.
Slave Schedule
You must enter a master schedule before you can enter any slave
schedules. When you enter a slave schedule, you must specify which
master schedule it will follow. The slave and master schedules must
reside in the same controller.
The action lines in the slave schedule match those in the master
schedule, by line number. The master schedule actions and times
will appear on the screen, but you will not be able to change them.
The slave schedule mirrors, optimizes, or ignores a particular line
of the master schedule, regardless of which action is currently on
that line. You may enter an adjustment, so that the equipment
starts and stops will be staggered.
Note: Keep track of which actions are on which lines in the master schedule.
This is especially important any time you modify an existing master
schedule.
8
24
Dynamic Control
Time Scheduling
The purpose of time scheduling is quite simple: turn a point on, or
off, based on the time of day and day of week. Two different editors
are used to input time scheduling information: Time Scheduling
and Special Days. The Time Scheduling editor schedules day-to-
day control activities, and sets alternate schedules for later use. The
Special Days editor is used to temporarily replace the normal
schedule for specific dates with special days schedules (defined in
the Time Scheduling editor).
There are three types of schedules: master, slave, and independent.
A master schedule can also be used as a base schedule by other
points.
A slave schedule follows a specific master schedule, but allows
you to define an offset period for each action, or even ignore
the action entirely.
An independent schedule is used only for a particular point:
its control decisions are not based on the schedule of any
other point.
A schedule is assigned to a specific point. Each of the schedule types
(master, slave, and independent) also allow you to enter actions
and times for alternate schedules.
Note: The operator may decide to control a point based on the time at
which sunrise or sunset occurs. The time of sunrise and sunset are
functions of latitude, longitude, deviation from Greenwich Mean
Time (GMT), and daylight savings time entries. These parameters
must be entered for each DCU, in the DCU Configuration/Summary
editor.
Temporary Schedules
This feature permits the operator to override the normal schedule
for one or more days, up to one week ahead. For example, you may
need to operate your facility on a day it is normally closed.
Two temporary schedules are provided. You may select either, or
both, temporary schedules for any particular day. A temporary
schedule flag (1 = schedule 1, 2 = schedule 2, B = both) indicates a
temporary schedule assignment.
Note: The temporary schedule flag will disappear once it has been
processed.
Caution: Temporary schedule flags are not saved or restored as part of the
DCU database. If the DCU database is restored, any temporary
scheduling flags will be erased.
Note: It is recommended that you populate special day commands for all
special days, especially for points that are to be turned on during a
special day period.
The Time Scheduling editor defines the schedule for the special
day; that is, it specifies what commands will be processed when a
day is designated as a special day. The Special Days editor actually
specifies when the special day schedule will be in effect.
Caution: If a particular point has no special day information defined, then the
point will stay in its last commanded state for the duration of the
special day period; it will not maintain its normal schedule. For
example, a point is turned on at 08:00 and off at 17:00 every
weekday. The DCU enters a special day period at 00:00 on a Monday.
This point has no special day information defined for it. This point
would stay off Monday since its last commanded state (on the
preceding Friday) was off.
Processing
Control decisions for time scheduling are made on the minute
change in the DCU, but are NOT reinforced every minute.
Time schedules are reinforced in a DCU via a look-back to
midnight routine which is invoked in the following cases:
1. A time schedule is modified or added.
2. The DCU is reset either via a power restoration or through
pressing the DCU reset button.
3. The time scheduling program is turned on via the DCU
Configuration/summary editor. The time scheduling
program can also be turned off via the same editor, thus
causing all points under time scheduling control to remain in
their last commanded states.
Temperature Control
Temperature control provides control of discrete points based on
up to 4 different setpoints: Normal Cooling, Normal Heating, Set
Up Cooling, and Set Back Heating. The setpoints are invoked based
on the time schedule assigned to the same point and the mode
(cooling or heating) that is applicable.
Temperature control provides adaptive optimized start and stop
functions which, based on historical building characteristics, turn
equipment on/off before scheduled start/stop times to maintain
building comfort while maximizing energy savings. Temperature
control also provides an optimized cycling function which
lengthens the On portion of a cycle based on a desired setpoint.
Equations
The equations stated below define the action of the output when
using temperature control.
Heating (Normal/Setback)
Vn = [T < HSP D2] OR [Vn1 AND (HSP D2 < T < HSP + D2)]
Cooling (Normal/Setup)
Vn = [T > CSP + D2] OR [Vn1 AND (CSP D2 < T < CSP + D2)]
where:
Mode Selection
If the device has both heating and cooling setpoints populated, the
temperature control function selects the mode (heating or cooling)
automatically, based on the position of the space temperature as
compared to the setpoint(s).
If the space temperature is below the active heating setpoint,
the mode is selected as heating.
If the space temperature is above the active cooling setpoint,
the mode is selected as cooling.
Note: The heating setpoint(s) may never be greater than the cooling
setpoint(s).
Caution: The heating setpoint plus 12 of its differential may never overlap the
cooling setpoint minus 12 of its differential.
Optimization
Actions in an independent or slave schedule may be optimized to
save energy and money. (Master schedules are optimized only
through related slave schedules.) Optimization is a special function
that uses the Temperature Control and Time Control editors in
tandem. An action is specified as an optimization in the Time
Schedule editor.
Optimized Cycle
The objective of optimized cycling is to increase the On time of a
cycle period in order to compensate for temperature differences
from the setpoint. The following information must be provided:
Cooling and heating setpoints. These elements are entered in
the Temperature Control editor.
Note: Cooling and heating setpoints affect all temperature control actions
for that point, not just optimization.
Note: The cycle period itself is never disregarded. The fact that a points
cycle periods remain synchronized is very important when using this
function in conjunction with demand limiting.
Note: Cooling and heating setpoints affect all temperature control actions
for that point, not just optimization.
Target time is the time by which you wish to reach the speci-
fied temperature. The target time is entered in the Time
Schedule editor, as the time for the optimized action.
Note: The performance constant can only be calculated if the space reaches
the target temperature during normal operating times. An optimized
start or stop action cannot take place until this target temperature is
achieved.
Processing
The processing of points assigned to temperature control is based
on whether the point is being controlled to a heating/cooling
setpoint or if it is being controlled to a cycling setpoint.
If a point has started to control to a heating/cooling setpoint
(a scheduled On, Off, Optimized Start, or Optimized Stop)
and a differential has been assigned, then temperature control
decisions are made on the minute change in the DCU, and
reinforced every minute thereafter.
If a point is being optimized to control to a heating/cooling
setpoint (a scheduled Optimized start or Optimized stop) and
no differential (zero) has been assigned, then no temperature
control decisions are made by the Temperature Control
editor.
If a point has started to control to a cycling setpoint (a sched-
uled Optimized Cycle), then temperature control decisions
are made at the scheduled time, and are reinforced every
minute thereafter.
Demand Control
The demand program monitors the consumption of electrical
power. Demand control allows you to:
Monitor daily KWH consumption The daily KWH
consumption total, daily peak KW demand, and time of daily
peak KW demand are automatically recorded in the specified
SevenTrends table.
Maintain a monthly total of KWH consumption You may
specify a point to accumulate a monthly consumption total.
Monitor demand You may specify a point to reflect current
KW demand. This point may then be placed on system pages,
as a display value.
Turn off (shed) loads An important part of demand
control is the ability to shed loads, which are discrete output
(DO or DC) points, in order to prevent the actual demand
from exceeding a specified target. Load shedding takes place
according to a priority arrangement with some loads being
shed before others, and can be limited in time to avoid
damage to equipment or unwanted effects on the environ-
ment.
Note: Enter only the loads that may be shed. If the equipment controlled by
a point is critical, (i.e., you would rather go over the maximum KW
demand level than turn off the equipment) do not enter that point in
the demand loads portion of the Demand Control editor.
Max off time The maximum time that this load may
remain Off due to shedding. Note that this does not
affect the scheduled On and Off times for this point. This
parameter is entered in the demand loads portion of the
Demand Control editor for the demand meter (PI) point.
Minimum off time The minimum time this point
must be off before it may be turned on. This entry is very
important, to allow the equipment adequate shutdown
time between uses. This parameter is entered in the Resi-
dent I/O Points editor for the load (DO or DC) point.
Minimum on time The minimum time this point
must be on before it may be turned off. This entry is very
important, to prevent short-cycling the equipment. This
parameter is entered in the Resident I/O Points editor for
the load (DO or DC) point.
SevenTrends tables If you wish to track consumption and
demand information for reports, you must define trends to
store the data, as follows:
Demand trend This trend will receive the daily
consumption information from the demand meter (PI)
point. The total daily consumption, daily peak demand,
and time of peak demand will be recorded. This trend
must be defined for the demand information to be avail-
able for reporting.
Analog Sample trends If you wish to track and report
current demand data, you must set the trend sampling
extension on the current demand point, and define an
analog sample trend to store the information. Likewise, if
you wish to track and report monthly consumption data,
you must set the trend sampling extension on the
monthly consumption point, and define an analog
sample trend to store the information.
Monitoring Consumption
The demand program uses input from the demand meter (PI)
point to calculate electrical consumption. The DCU takes the
starting value of the accumulator, and adds the incremental counts
Note: Upon database restoration, all accumulators are reset to zero. You
may wish to manually record all accumulator values before a data-
base restoration and reset the starting value(s) of the accumulator(s)
via the Test command after performing the database restoration. An
accumulator will not start collecting data until after the database
restoration is complete, therefore, any data changes which occur
during database restoration are lost.
Daily Consumption
The demand meter (PI) point will automatically collect the daily
consumption information. The program resets the value of the
accumulator to zero at midnight each day.
If a cell number is specified in the Demand Control editor, the daily
consumption information will be automatically routed to the trend
table at midnight. This allows you to store consumption informa-
tion for viewing and reporting purposes. The daily total consump-
tion, daily peak demand, and time of daily peak demand will be
recorded in the demand trend.
Monthly Consumption
An internal accumulator point may be defined to store the month-
to-date accumulation of electrical consumption. You may use
either an AI or PI point for this purpose (PI point recommended).
This function is commonly used to place month-to-date consump-
tion information on system pages.
In order for this function to work properly, the appropriate dates
must be entered in the Schedules portion of the Demand Control
editor for the demand meter (PI) point. The dates entered should
be the last day of each month. At midnight of the specified date, the
monthly consumption accumulator will be reset to zero.
Calculating Demand
The demand calculation is based on the electrical consumption
and the demand interval. The program measures the demand by
dividing the demand interval (entered in the Demand Control
editor to match the interval set by the local electric utility
company) into 10 equal time-based segments which we will refer to
as control periods.
control
demand interval period
{
}
period (n) and the previous four control periods (n1, n2, n3,
and n4). These consumption values are used to predict the
demand for the next control period (n+1). See Figure 8-2.
a b c d e f g h i j
n4 n3 n2 n1 n n+1
In the current control period (f), the system will calculate the projected
demand for control period (g), using the demand from the current control
period (f) and the four previous control periods (be).
Note: You may wish to assign a high limit value to the current demand
input point. When an alarm is received for this point, this alarm
reflects the fact that the actual measured demand has exceeded the
value you have defined.
a b c d e f g h i j k l m n o
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
a b c d e f g h i j k l m n o
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
a b c d e f g h i j k l m n o
n- n-9 n-8 n-7 n-6 n-5 n-4 n-3 n-2 n-1 n
Note: When the demand program is first started, you must wait for one full
demand interval to pass before the reported current demand becomes
meaningful (see Table 8-1 on page 8-23).
Shedding Loads
The main purpose of the demand control function is to limit the
demand segment of the electric utility charges by limiting the
maximum KW draw. This limiting is achieved by automatically
and selectively turning loads off (i.e., shedding loads).
Warning: As a minimum, you should use the rated KW value (normally found
on the motor nameplate) of the equipment when defining loads in
the demand program. An approximation is sufficient; an entry of
zero (0) is not. If you assign zero ratings to the loads, the demand
program will shed every 0 KW-rated load, then restore them the very
next control period.
If the predicted demand is less than the target minus the differen-
tial, loads are turned back on. For example, if the normal shed level
is set at 95 kilowatts and you define the differential as 5, the system
does not begin restoring loads until the predicted demand is less
than 90 kilowatts.
Loads are restored according to the following criteria:
1. Loads with the highest priority are restored first.
2. Within a priority, loads will be restored in the same order as
they were shed (i.e., the first load shed will be the first load
restored).
3. To be restored, a load must meet its minimum off time, as set
in the Resident I/O points editor.
4. The kilowatt rating of the load must be such that restoring the
load will not cause the demand to exceed the setpoint.
10000
1000
100
10
Consumption, KWH
Demand, KW
1
Forecast Demand, KW
t10
t12
t14
t16
t18
t20
t22
t0
t2
t4
t6
t8
9
96
Access Control
Note: The editors used for access control will not be available unless you
enable access control in the TAC I/NET Seven active configuration.
Refer to the TAC I/NET Seven Configuration chapter in TCON298,
TAC I/NET Seven Getting Started, for more information.
LAN Tap
MR MR MR
Key/Card Numbers
Note: Only the SCU1284 and the DPU7920 (with installed DPU48K)
using revision 3.24 or later firmware have the ability to support up to
32,000 individuals per tenant. All other door controllers support up
to 24,000 individuals per tenant.
Note: When you define translation table entries for key/cards, you force the
system to store the corresponding lookup records at the door
controller. The door controller must also store the entire contents of
the Key/Card Translation table. These items will consume memory in
the door controller.
Note: TAC I/NET Seven allows you to assign a large key/card number
directly to an individual, or translate the number using the Key/Card
Translation table. However, within a single tenant, TAC I/NET
Seven will not allow you to perform both actions with the same
key/card number or with the same individual.
Decimal Conversion
Convert binary data to a decimal value as follows:
32768
16384
8192
4096
2048
1024
512
256
128
64
32
16
8
4
2
1
+ 512
+ 256
+ 32
+ 1
(Add these values together) Decimal Value = 35,617
HexiDecimal Conversion
Convert binary data to a hexidecimal value as follows:
e eeeeeeee eeeeoooooooooooo o
Facility Code Card Number
3. Pad the incomplete group on the left with two more 0s.
Example: 0000 1100 0100 0101 0111 1111 1111 1101.
4. Now, convert each group into a hexidecimal value.
Example: 0000 = 0
Example: 1100 = C
Example: 0111 = 4
Example: 0100 = 5
Example: 0101 = 7
Example: 0111 = F
Example: 0111 = F
Example: 1101 = D
5. The final hexidecimal value for this card is 0C457FFD. This is
the value that you would enter into TAC I/NET Seven.
1024 KB of memory. Not all of the memory within the SLI is avail-
able for storing access control records. Each platform consumes
over 100 KB of memory as fixed overhead. Station parameters for
subLAN devices can consume up to 30 KB of SLI memory. Addi-
tionally, the use of embedded Tap emulation within the SLI will
consume another 28 KB to 58 KB of memory. Refer to the following
table to determine the approximate number of access control
records that can be stored within an SLI.
Users with
Resident Secondary Remaining Cached
Users Schedules Bytes Messages OR Users
100 100 58,100 4,841 3,631
500 100 57,700 4,808 3,606
1,500 100 56,700 4,725 3,543
3,000 100 55,200 4,600 3,450
6,000 100 52,200 4,350 3,262
12,000 100 46,200 3,850 2,887
18,000 100 40,200 3,350 2,512
24,000 100 34,200 2,850 2,137
36,000 100 22,200 1,850 1,387
48,000 100 10,200 850 637
Users with
Resident Secondary Remaining Cached
Users Schedules Bytes Messages OR (Messages + Users)
100 100 1,944,200 162,017 76,683 64,000
500 100 1,943,800 161,983 76,650 64,000
1,500 100 1,942,800 161,900 76,567 64,000
3,000 100 1,941,300 161,775 76,442 64,000
6,000 100 1,938,300 161,525 76,192 64,000
12,000 100 1,932,300 161,025 75,692 64,000
18,000 100 1,926,300 160,525 75,192 64,000
24,000 100 1,920,300 160,025 74,692 64,000
36,000 100 1,908,300 159,025 73,692 64,000
48,000 100 1,896,300 158,025 72,692 64,000
64,000 100 1,880,300 156,692 71,358 64,000
Note: The editors used for access control will not be available unless you
enable access control in the TAC I/NET Seven active configuration.
Refer to the TAC I/NET Seven Configuration chapter in TCON298,
TAC I/NET Seven Getting Started, for more information.
Access control elements (individuals, doors, key/cards, schedules,
etc.) are configured through separate editors. Changes made in one
editor can affect the operation and contents of other editors. The
following paragraphs describe what order of operations to use
when configuring the access control system and how to track
configuration changes.
Note: As you modify your access control system, the changes you make are
sent to the applicable door controllers when you close each editor. If a
communication error between your host workstation and a door
controller prevents changes from being downloaded, TAC I/NET
Order of Operations
You must observe the following order of operations when
performing access control database entry.
1. Configure the door controller.
2. Define the station parameters (define control descriptions
and state descriptions for door points).
3. Add door points in the Resident I/O Points editor.
4. Save door points in the Network Configuration editor.
5. Define the doors in the Door Parameters editor.
6. Define door mode schedules.
7. If desired, translate key/tag numbers greater than 32,000
using the Key/tag Translation editor.
8. Define tenants using the Tenants editor.
9. Define groups using the appropriate editors.
10. Define individuals.
11. If necessary, implement elevator control (details in this
chapter).
Recycle Bin
Newly introduced with TAC I/NET Seven is the access control
recycle bin. When enabled, the recycle bin provides a temporary
storage location for deleted individual, group, and tenant records.
When one of these records is moved to the recycle bin, it no longer
appears in any editors or summaries. Recycle bin records can later
be restored, or they can be permanently purged from the system.
Access to the recycle bin is restricted to users with proper permis-
sions. This allows your system to be configured in such a way that
only select operators are allowed to delete, restore, or purge
records. Refer to Host Passwords on page 4-4 for more informa-
tion about passwords and permissions.
Deleting a Group
When you delete a group to the recycle bin, the following informa-
tion is retained within a single recycle bin record:
The groups door assignments
The groups links to other groups
The recycle bin does not retain references to a deleted group. There-
fore, if you delete a group that is assigned to an individual, or that
is being referenced by another group, the links to the group will be
destroyed. Even though you can restore the group later, the
previous links to this group will not be restored. The system alerts
Purging Records
You can permanently delete access control records contained in the
recycle bin by purging them. Once purged, these records no longer
exist and therefore, they can not be restored.
TAC I/NET Seven offers you the following three methods for
purging records from the recycle bin:
Open the recycle bin and purge selected records directly.
Configure TAC I/NET Seven to automatically purge records
that have been in the recycle bin for a specified number of
days. This function runs every 60 seconds. It uses the deletion
time and date stamp contained in each recycle bin record to
determine whether or not the record should be purged.
Configure TAC I/NET Seven to automatically purge all recycle
bin records at log off. Records can be purged silently at log off,
or you can configure the system to first prompt the user.
When prompted, the user can choose whether or not to purge
the recycle bin. The prompt also allows the user to turn off
future prompting and allow the system to silently purge the
recycle bin at log off.
DPU Configuration
The DPU configuration process identifies for the DPI, MCI, or
I/SITE LAN which devices to poll for successful communication.
The DPI and I/SITE LAN each support up to 32 devices. An MCI is
a two-station device that allows a maximum of 64 subLAN devices
(32 per station). Each point address for the controller to which you
are currently connected can be defined as one of the following
types:
Internal Tells the DPI, MCI, or I/SITE LAN that there is no
controller at that address to poll.
DPU Tells the DPI, MCI, or I/SITE LAN that there is a
DPU7910A, DPU7920, or SCU1284 at this address and to poll
it.
DIO Tells the DPI, MCI, or I/SITE LAN that there is a
DIO7940 or SCU1280 at this address and to poll it.
Doors
Door points can be added to TAC I/NET Seven using the Resident
I/O Points editor. Door point addresses use the same structure as
all other TAC I/NET points; however, the following actions must be
taken when defining a door point:
The bit offset defined in the point address must be either 08
or 09 (first or second door point in the door controller,
respectively)
The point type must be set to DO
The point class must be set to internal
The three-state output parameter must be enabled.
After door points have been defined in the Resident I/O Points
editor, they must be saved in the Network Configuration editor.
Only door points that have been saved in the Network Configura-
tion editor are available to the access control system.
TAC I/NET Seven lets you add, delete, modify, or copy door access
control extensions in your system. When you add or modify a door
access control extension, the system provides the following.
Door parameters
Mode schedules
Note: Changes made through the Door Extension editor generate a door
edit audit trail message. Refer to Audit Trail Messages on page
9-16 for more information.
Note: When deleting a door from a 7791 DPI, 7793 MCI, or 7798 I/SITE
LAN, make sure to delete the door extension before deleting the door
(DO) point. Deleting the door point without previously deleting the
door extension may cause unpredictable system performance.
ABA 115 ABA data format with 115 bit data length
ABA 85 ABA data format with 85 bit data length (CSI specification)
I/DISC TAC I/DISC button
ITracs Indala readers using CSI proprietary data format
Tracs TAC proprietary data format
Watermark Standard Watermark data format
Wiegand 26-bit Standard Wiegand data format reader
Wiegand 32-bit TAC proprietary Wiegand data format reader
Wiegand 66-bit TAC proprietary Wiegand data format reader
Generic Wiegand data format reader. When this option is selected, define
Custom Wiegand the bit data length of the card number (2664).
(supported only on the
SCU1284 and If you select this reader, the reader type must match the selection for AC
DPU7920 with MIP) Reader Port in the active configuration. Refer to the section on TAC I/NET
Seven Configuration in TCON298, TAC I/NET Seven Getting Started.
Generic ABA data format reader. When this option is selected, define the
Custom ABA
bit data length of the card number (919).
Note: If the reader type is I/DISC, this setting will be ignored unless the
door controller is a DPU7920 or an SCU1284.
Activate this option if you wish to track entry and exit transactions
that are made using a PIN. If you do not wish to track this informa-
tion, you may leave this field inactive.
If this option is activated, then reader entry messages will indicate
whether a PIN was used. For example, a door equipped with both
a card reader and a PIN pad will generate one of two messages:
either Reader entry or Reader entry - PIN. This allows the oper-
ator to determine the access method used to unlock the door.
PIN Retry Count
This option indicates the number of times a user may attempt to
enter a PIN before generating a Denied - PIN message. This
message will be either an alarm or a transaction, depending on the
setting for this event in the Message Type section of this editor.
This option is available only if the PIN pad option is activated.
(This option is only available on door controllers with firmware revi-
sion 2.20 or later.)
Note: If the reader type is I/DISC, this setting will be ignored unless the
door controller is a DPU7920 or an SCU1284.
Exit Reader
The exit reader parameter determines whether or not an exit reader
will be used with the selected door point. If an exit reader will be
used, this parameter also determines whether or not to tie the
reader to a time schedule.
Depending on whether or not the door is configured with a PIN
pad, the following Exit Reader options are available.
Door without PIN pad:
None Do not use exit reader for egress.
Anytime Valid key/cards are granted exit at all times,
regardless of active personnel schedules (i.e., 24 hours, 7
days-a-week).
Scheduled Tie the exit reader validation to active
personnel schedules.
Door with PIN pad:
None Do not use exit reader or PIN pad for egress.
Anytime Valid key/cards are granted exit at all times,
regardless of active personnel schedules (i.e., 24 hours, 7
days-a-week). No PIN is required.
Sched. w/PIN Tie the exit reader validation to active
personnel schedules. Entry of a valid PIN is required to
exit the area when the door is operating in the PIN
Enable mode.
Sched. w/o PIN Tie the exit reader validation to active
personnel schedules. No PIN is required to exit the area.
Note: If you have defined one door in a DPU7920, and the doors Exit
Reader parameter is set to anything besides No, then the second
reader port automatically becomes the exit reader. If you have
defined two doors (08DO or 09DO) in a DPU7920, neither door can
have an exit reader defined.
Only the first two doors in the SCU1284 can have an exit reader. If
you assign an exit reader to the first door, the reader input for a third
door will instead be used for the first door's exit reader. If you assign
an exit reader to the second door, the reader input for a fourth door
will instead be used for the second door's exit reader.
Note: This value is not updated if you select a different reader. If you switch
between reader formats, the default value in this field may not be
valid for the selected card type.
Card Translation
If the door controller is loaded with firmware version 3.18 or later,
a Card Translation option is available. Activate this option if you
wish to translate high I/DISC or Watermark key/card numbers to
values that are within a 1-to-32,000 key/card range.
Anti-passback
Notes: 1. Anti-passback/anti-tailgate requires that a door controller have
both an entry reader and an exit reader. An elevator door
controller will support only an entry reader, and therefore, will
not support anti-passback/anti-tailgate.
2. Anti-passback/anti-tailgate cannot span mulitple station
addresses. The zones beneath one station address are monitored
seperately from the zones under another station address.
Note: If the Anti-tailgate option is enabled, any door between the secured
area and the non-secured area must have the same zone number for
both exit and entry (see Entry and Exit Zone Number on page
9-27). The non-secured area is any region not under access control,
such as a lobby, public area, or the outdoors.
Note: The zones beneath one station address are monitored seperately from
the zones under another station address. Therefore, Anti-passback
and Anti-tailgate cannot span mulitple station addresses.
The Entry and Exit Zone parameters are available only if the Anti-
passback option is enabled. The valid zone range is 064.
Each exterior door shown in the example has entry reader and exit
reader zone numbers that match. This causes TAC I/NET to
generate only one zone entry or exit message after a valid read at an
exterior door. This also makes it unnecessary to use a zone number
for the exterior (non-controlled) area of the building.
Anti-passback Reset Time
The Anti-passback Reset Time accepts a value from 0 to 60
minutes. (This parameter is only available on door controllers with
firmware revision 2.20 or later, and only if the Anti-passback option
is enabled.)
By setting this parameter to a non-zero value, you can cause the
door controller to start a timer when an individual is granted access
through the currently selected door. When the timer duration
expires, the door controller will reset the individuals APB flag for
this door. The individuals APB flag for all other doors in the same
zone will also be reset, as long as the door controllers for these
doors reside on this doors controller LAN.
Note: This option is only available on door controllers with firmware revi-
sion 3.22 or later.
Note: The door open too long message is only generated when the door is in
the Secure mode; it is not generated when the door is in Unlocked
mode.
Note: This option is only available on door controllers with firmware revi-
sion 3.21 or earlier. For door controllers with firmware revision 3.22
or later, refer to First Key Mode on page 9-36.
Note: If you want access enabled after hours based upon personnel sched-
ules, use the first key auto-unlock function.
Mode Schedules
A door Mode Schedule controls the operating mode of the door at
specific times of the day. Each door extension includes scheduling
parameters for defining each door.
Action
The only difference between a mode schedule and other TAC
I/NET time schedules is the available schedule actions. The
following mode schedule actions are available.
APB Reset
This action resets anti-passback memory for this door. Any indi-
vidual who previously entered the zone assigned to this door, but
who has not yet exited, can now successfully reenter the same zone.
This function is applicable only to the door containing the mode
schedule and is not globalized for zone anti-passback. Conse-
quently, each door using anti-passback should contain an APB
reset command at the end of each day in its mode schedule.
Lock
This action inhibits entry and exit through the door. All readers
and release buttons for a specified door are disabled when lock is in
action.
Unlock
This action enables the door for open access. Key/card readers are
still enabled for continued access control audit.
Note: When a door mode schedule defines unlock at the end of a lock
period, the door automatically unlocks at the scheduled time. If you
want the door to remain locked during the scheduled unlock time,
until authorized personnel have entered the area, you must define a
secure (or PIN enable) period immediately preceding the unlock
period and use the first key auto-unlock function. Refer to First Key
Auto-unlock on page 9-33 for more information.
Secure
This action returns the door to authorized access only. All
key/cards will be validated based on personnel schedules, tenant,
key/card issue number, anti-passback, and access level.
PIN Enable (Door Controller Firmware 3.20 or Earlier)
OR
Sec/PIN (Door Controller Firmware 3.21 or Later)
When this mode is active, the PIN reader on the DPU will be
enabled. This mode is the same as the Secure mode except that it
also requires the individual to enter a valid PIN after a valid
key/card read. If an individual enters an invalid PIN, the setting of
the PIN Retry Count parameter (described on page 9-23) will
determine how many retries (if any) the individual can use to enter
a valid PIN.
You can schedule a door's PIN pad to become disabled without
unlocking the door by following this mode with a Secure mode.
When the Secure mode becomes active, individuals will no
longer be required to enter a PIN in order to gain access through
the door.
Note: TAC I/NET Sevens PIN function also supports a duress code for use
in emergency situations. See your TAC I/NET Seven system adminis-
trator for more information about this feature.
Note: This option is only available on door controllers with firmware revi-
sion 3.22 or later. For door controllers with firmware revision 3.21 or
earlier, refer to First Key Auto-unlock on page 9-33.
Using the first key mode, you can configure the mode schedule to
switch to a secondary mode if a valid entry sequence occurs at the
door. Once operating in the secondary mode, the door will remain
in this mode until the next scheduled action becomes active.
The first key mode is only active when you set the mode schedule
action to Secure, Sec/PIN, or Sec/Code. The options available for
the first key mode parameter will differ depending on the mode
schedule action setting.
When you configure an action to use the first key mode, it will be
displayed in the Door Mode Schedule editor with the main action
shown first, followed by an arrow (->), and then the secondary
mode.
For example:
An action of Sec/PIN with a first key mode setting of Sec/Code
will be shown as:
Sec/PIN>Sec/Code
In this example, the door will operate in the Sec/PIN mode until an
individual gains access by swiping their card and entering their
PIN. The door will then switch to the Sec/Code mode, allowing
subsequent individuals to gain access simply by typing the door
code at the PIN pad.
The points that you can assign to a function must reside in the door
controller. When assigning a point to a PIN pad function, you need
only specify the bit offset (BB) portion of the points address. The
link (LL), station (SS), and point (PP) portions of the address will
match the address of the selected door.
Assigning Points in an SCU1284 Controller
The SCU1284 has the capability to control up to four doors. In
order to control more than two doors, the SCU1284 must operate
in a double-address mode. In this mode, the SCU uses two
consecutive subLAN point addresses. The SCUs first address is
used with its first two doors and the next consecutive address is
used with the second two doors.
As described earlier, in order to assign a point to a PIN pad func-
tion, you only specify the points bit offset. The rest of the points
address will match that of the selected door. Since the SCUs doors
can be split across two subLAN addresses, you must take care not
to assign points from one subLAN address to PIN pad functions on
the other subLAN address.
Refer to TCON312, SCU 1200-series Installation Guide for more
information about how points are mapped in the SCU.
Intruder Alarm System Functions
You can use PIN pad functions to control an intruder alarm system.
In order to do this, you must first enable the Intruder Alarm System
option. Once enabled, the following parameters become available:
Arm Ready Bit Offset
Use the Arm Ready Bit Offset parameter to specify which DI point
will receive the arm ready status signal from the alarm system. The
state of this point will be used to determine whether or not the
alarm system can be armed.
You must use a DI point on the current door controller to receive
the arm ready status from your alarm system. For this reason you
need only specify the points bit offset. For example, if this signal
enters the door controller at DI point 00 (TB1-1 on a DPU 7920),
then enter a bit offset of 00.
Note: PIN pad functions are not available for use while the door is oper-
ating in the Sec/Code mode. Refer to Sec/Code (Firmware Version
3.22 or Later) on page 9-36 for more information.
You can control the use of PIN pad functions on a per-user basis. A
users personnel schedule will determine whether or not the user
can access a particular PIN pad function. Refer to Personnel
Schedules on page 9-54 for more information.
The Control door mode option causes the door mode to automat-
ically change when a user arms or disarms the alarm system from
the PIN pad. If the user arms the alarm system, the door mode
changes to Secure. If the user disarms the alarm system, the door
mode changes to Unlock.
Door mode
The Door mode function allows an authorized user to control the
operating mode of a door from the PIN pad. This function
provides the following options:
Secure (key 0)
Unlock (key 1)
Lock (key 2)
When an authorized user selects this function, the LED on the PIN
pad displays the currently active door mode as follows:
Blank = Secure mode
Green = Unlock mode
Red = Lock mode
If only one option is enabled for this function, the user can imme-
diately set the door mode just by selecting the function. In this case,
the user is not required to press a second key.
When at least two options are enabled for this function, the user
must press the appropriate second key (0, 1, or 2) to control the
door mode. After the user successfully changes the door mode
through the PIN pad, the updated door mode displays.
Discrete Status
The Discrete Status function allows an authorized user to view the
current status of up to ten DI points from the PIN pad. This func-
tion provides the following options:
First input
Last input
Use the First input parameter to specify the bit offset of the first DI
point you wish to assign to this function. Use the Last input to
specify the bit offset of the last DI point. You can assign a single DI
point to this function by setting the First input and Last input to
the same bit offset.
When an authorized user selects this function, if only one DI point
has been assigned, the PIN pad immediately displays the points
status. If multiple DI points have been assigned, the user is required
to choose the appropriate DI point by selecting the points bit offset
(09) on the PIN pad. A yellow LED on the PIN pad indicates that
this function is waiting for the user to specify a bit offset.
The indications provided by the LED on the PIN pad will depend
on whether or not you have enabled the Intruder Alarm System.
The indications are as follows:
Intruder alarm system enabled:
Green = Selected DI points state matches the Arm Ready
State setting.
Red = Selected DI points state does not match the Arm
Ready State setting.
Yellow = Waiting for user to choose a DI point.
Intruder alarm system disabled:
Green = Selected DI points state matches the setting of
the Green LED State parameter.
Red = Selected DI points state does not match the setting
of the Green LED State parameter.
Yellow = Waiting for user to choose a DI point.
Control Relay
The Control Relay function allows an authorized user to energize
or de-energize, or view the current status of up to eight relays. This
function provides the following options:
First relay
Last relay
Use the First relay parameter to specify the bit offset of the first
relay DO point you wish to assign to this function. Use the Last
input to specify the bit offset of the last relay DO point. You can
assign a single relay to this function by setting the First input and
Last input to the same DO point bit offset.
When an authorized user selects this function, if only one relay has
been assigned, the PIN pad immediately displays the relays status.
If multiple relays have been assigned, the user is required to choose
the appropriate DO point by selecting the points bit offset (07) on
the PIN pad. A yellow LED on the PIN pad indicates that this func-
tion is waiting for the user to specify a relay.
When the user chooses a relay, its current status is displayed on the
PIN pad. If necessary, the user can manually de-energize or ener-
gize the selected relay by pressing 0 or 1, respectively.
The indications provided by the LED on the PIN pad for this func-
tion are as follows:
Green = Selected relay is de-energized.
Red = Selected relay is energized.
Yellow = Waiting for user to choose a relay
Using Door Attributes
Note: Door attributes are not available for use while the door is operating
in the Sec/Code mode. Refer to Sec/Code (Firmware Version 3.22
or Later) on page 9-36 for more information.
Elevators
The elevator control function works in conjunction with access
control parameters and personnel schedules to control access to
banks of elevators. Enabling the elevator option in the Door
Parameters editor causes the door controller to process each reader
transaction as though it were an entry into an elevator cab.
Elevator Processing
Once elevator control has been implemented, elevator processing
will proceed as follows:
1. A key/card is passed through a reader at the elevator cab and
validated by the parent door controller.
2. The door controller sends a message to the DPI, MCI, or
I/SITE LAN that contains the elevator floor numbers to which
this key/card holder has been granted access (using the
Personnel Schedule editor).
3. The DPI, MCI, or I/SITE LAN will issue a Start control action
to the discrete output point for each floor enable relay, and
start a timer to limit the amount of time that the key/card
holder has to respond.
4. When a floor is selected, the DI point that is monitoring the
floor button will change state and invoke the following
actions:
a. A transaction message, containing the elevator entry
transaction information, plus a two-character designa-
tion for the selected floor, will be broadcast on the
controller LAN, and forwarded to the parent host(s).
Elevator Extension
You can add an elevator extension on each door point (BB08 and
BB09) assigned as an elevator in the DPI, MCI, or I/SITE LAN.
After adding the elevator extension to a point, you must define
elevator parameters such as floor selection time, floor designation
description, button enable point and button selection point.
Floor Selection time
Enter the amount of time in seconds that the key/card user has to
make a selection from the floor buttons in the elevator cab. After
this time limit expires, the floor buttons are disabled. The key/card
user must successfully perform another key/card read to enable the
floor buttons. When a selection is made, the floor buttons are
disabled and a message is sent to the host with the floor designation
description attached to the elevator entry message.
Floors
For each elevator floor extension assigned to a point in the DPI,
MCI, or I/SITE LAN, there must be an associated DO and DI point
attached to the elevator extension. This association of DO and DI
point produces a closed-loop feedback allowing the controller to
identify an elevator floor selection with each successful key/card
reader access.
Floor Index
TAC I/NET Seven allows you to add, delete, or modify a floor index
for an elevator point. The floor index is a number (162) that will
typically represent the floor number. When adding a floor index,
you define a floor designation using one or two alphanumeric char-
acters. For example, the first level of a basement could be repre-
sented as B1. The floor designation appears along with any
messages generated by this point.
Button Enable
Each floor is assigned a button enable point that energizes after a
successful key/card read. The button enable point is typically an
indirect point with its parent point (an external DO point) located
in another controller.
Button Selection
Each relay point must have a DI point assigned to provide a closed-
loop feedback to the controller, indicating which floor button is
selected by the key/card holder.
Personnel Schedules
You can assign up to 31 personnel schedules to each door. Each
personnel schedule can contain up to seven access intervals. An
access interval is the time period during which a key/card can
access the door. As part of the process of assigning a group or indi-
vidual to a door, one of the schedules is selected. Thereafter, this
particular schedule is used to grant or deny access when a key/card
is presented at the door.
Features
Note: Door features are only available if the selected door meets the
following requirements:
The door controller is loaded with firmware version 3.18 or later.
For PIN pad functions, the keypad must provide an 8-bit burst
output.
The DPU7920 with firmware version 3.16 also provides door features
except for the attributes used for the two-man rule.
Note: The access control system does not support a master/slave scheduling
relationship between points as does the standard TAC I/NET Time
Scheduling editor.
Shift Rotations
Note: This feature is supported only in door controllers loaded with firm-
ware version 3.01 or later.
Among the personnel schedules that you can define for each door,
you can also define shift rotations. A shift rotation is a collection of
personnel schedules that are activated in sequence and at a speci-
fied interval.
Rotation List and Order
The Shift Rotation editor provides a complete list of all personnel
schedules defined for the selected door. Using the Add and
Remove commands, you can choose which personnel schedules to
include in the rotation. You can also use the Move Up and Move
Down commands the adjust the position of a highlighted schedule
in the list.
When you assign a shift rotation to an individual or group door, its
personnel schedules are activated one at a time, beginning with the
top-most personnel schedule in the list. When the time interval you
specify in this editor expires, the next personnel schedule in the list
is activated. After the last personnel schedule in the list has been
used, the top-most personnel schedule is activated once again and
this process continues.
Rotation Start
As part of the shift rotation definition, you must specify a start date
and time. By default, the date and time parameters are set to the
current date and time, allowing the shift rotation to start immedi-
ately. If necessary, change these settings to the appropriate date and
time.
Rotation Properties
Specify the Rotation Interval in either Days or Hours. This
interval determines how often the system switches from one
personnel schedule to the next in the shift rotation. The rotation
start date and time settings will be used to determine exactly when
the interval causes the switch from one schedule to the next. For
example, if the shift rotation starts on January 1, 2003 at 6:00 a.m.,
and the interval is 7 days, then on January 8, 2003 at 6:00 a.m. the
second personnel schedule in the shift rotation will become active.
Note: The parameters displayed within the Access Initiated Control editor
will differ depending on the firmware loaded in your systems control-
lers. Refer to the description of the Access Initiated Control editor in
TCON299, TAC I/NET Seven Operator Guide, for more informa-
tion.
The access initiated control (AIC) function lets you configure TAC
I/NET to automatically initiate a control action in response to an
access transaction for a selected tenant, group, or individual. Each
DPI, MCI, or I/SITE LAN supports up to 64 AIC actions, regardless
of how many tenants are defined. Although a control action is
directed to a single point, additional actions can be initiated
through the event sequence and event action editors.
When you add a new AIC action, you assign a new AIC number,
define a name, select a tenant, enter a valid discrete output (DO)
point, and assign individual numbers. When assigning individual
numbers, you can choose to assign all individual numbers defined
for the tenant, specific individual numbers defined for a group, or
specific individual numbers associated with the tenant. Whenever
a selected key/card transaction is processed for a matching tenant
code and individual number, a control action (start/stop) is issued
to the DO point.
Note: Access initiated control changes generate an AIC edit audit trail
message. Refer to Audit Trail Messages on page 9-16 for more infor-
mation.
Control Actions
Note: The parameters to which you can assign control actions will differ
depending on the firmware loaded in your systems controllers. Refer
to the description of the Access Initiated Control editor in TCON299,
TAC I/NET Seven Operator Guide, for more information.
You can enter a control action (none, start, or stop) for any corre-
sponding key/card transactions. The stop action is not available
for any of the Denied... key/card transactions. The start control
action will issue a control command 0 and the stop control
action will issue a control command 1. These control actions are
the equivalent of an event sequence defined with a Start or Stop
action. Refer to Chapter 7, Point Extensions for a description of
event sequences.
Doors
TAC I/NET Seven lists all of the tenants doors associated with the
selected SLI. You must decide which of the tenants doors will have
the AIC action assigned to them.
Individual Numbers
When assigning individual numbers to an AIC, you can assign all
individual numbers defined for the tenant or you may assign
specific individual numbers. If you choose to assign specific indi-
vidual numbers, all individuals assigned to the current tenant are
available for selection. Selecting Group will cause the All Yes and
All No functions to affect only the individuals associated with the
group for easier selection.
TAC I/NET Seven lists each individual by individual number, and
includes the last name, first name, group assignment, and record
type. You can decide which specific individual numbers within this
group/tenant you want to trigger the selected control action. You
can select All Yes, All No, or select each number individually.
Before you can assign specific individual numbers, you must first
enter a base (starting) individual number (132,000). The
maximum number of individuals available for each AIC is 500. You
must add a second AIC if more than 500 consecutive individual
entries are desired for a specific AIC action. You must also add a
Key/Card Translations
Tenants
The concept of tenants, as used in TAC I/NET, lets you assign access
controlled doors to more than one tenant. Tenants are usually
different groups that inhabit the same facility but that are
controlled separately. For example, a single large building may be
inhabited by several companies. Each company would be consid-
ered a separate tenant.
TAC I/NET Seven allows you to add, copy, modify, and delete
tenants. If you delete a tenant from your access control system, all
references to that tenant are purged from access editors. Deleting
the tenant will not delete the individuals that were assigned to the
tenant, but their key/cards will no longer be accepted at any of the
doors. Also, if you create a new tenant by copying an existing
tenant, all door assignments associated with the existing tenant are
copied to the new tenant.
When you add a tenant to the system, you must define the block of
individual numbers that will be allocated to that tenant and you
must define through which doors that tenant will have access.
Note: Tenant editor changes generate a Tenant edit audit trail message.
Refer to Audit Trail Messages on page 9-16 for more information.
Tenant Code
Use up to 8 digits to define the tenant code. This is the tenant code
that is embedded in the key/cards. Depending on the key/card tech-
nology, this code is commonly referred to as the Facility code or
the Site code. This field is not available for Tenant 0.
First Individual Number
Define the starting individual number for this tenant (132,000).
Any individual numbers less than the number you define here are
not accepted for this tenant. This field is not available for Tenant 0.
Number of Individuals
Define the total number of individuals available to this tenant (1
32,000). The absolute limit is 32,000 individuals for a single tenant.
If a single facility requires more than 32,000 individuals, you can
define multiple tenants with matching Tenant Codes. This field is
not available for Tenant 0.
Although TAC I/NET supports up to 32,000 individuals per tenant,
the model type and revision date of a tenants door controllers will
ultimately determine how many individuals will be supported. The
following table shows the capacity of various door controllers. For
any door controller with revision 2.2x or later firmware, you would
have to define multiple tenants in order to reach the door
controllers maximum storage capacity.
DPU7910,
2.1x and earlier Up to 24,000 per door
DPU7920
DPU7910,
Up to 48,000 per controller
DPU7920 without DPU48K
2.2x to 3.23
DPU7920 with DPU48K,
Up to 48,000 per door
SCU1284
DPU7920 with DPU48K,
3.24 and later Up to 64,000 per door
SCU1284
Warning: This checkbox setting does not take effect until you select OK to exit
the Tenants editor.
Groups
Individuals can be collected in groups to simplify access control
parameter definition and maintenance. A group is defined for a
particular tenant. You cannot copy a group from one tenant to
another, nor can you assign an individual to a group from a
different tenant. The exception is groups defined for Tenant 0,
which are global groups available to all tenants. Global groups are
designated by a ~ symbol in front of the group name.
TAC I/NET Seven allows you to add, copy, modify, or delete a
group. Groups are represented by a unique 64-character name.
Note: When you edit a group, TAC I/NET Seven generates a Group edit
audit trail message to provide a high-level audit trail for group
updates. The message contains the date and time the edit was
performed, the name of the edited group, and the initials of the
person who did the edit.
Note: Groups defined for Tenant 0 (all tenants) do not have group parame-
ters.
Group Parameters
Groups are defined using the following parameters:
Record Type
The default record type for a group is Permanent. This allows all
individuals assigned to this group to be granted access based on the
personnel schedule assigned to each group door.
Selecting Temporary in this field causes all individuals in the
group to be processed as temporary. The groups begin and end
date/time parameters must be satisfied before access is granted.
Selecting Disabled allows you to preprogram a group and its
associated individuals and activate them at a future time, or even
immediately deny access to all group doors until the record type is
changed back to Permanent or Temporary.
Begin Date/Time
Enter the date on which the temporary access begins, in
MM/DD/YY format. Enter the time on which time temporary
access begins, in 24-hour HH:MM format.
End Date/Time
Enter the date on which the temporary access ends, in MM/DD/YY
format. Enter the time on which time temporary access ends, in 24-
hour HH:MM format.
Door Selection
Door selection allows you to define those doors to which key/card
holders in this group have access. Only those doors assigned to the
current tenant are available. When you select a door, you then
select schedules for the doors to be available to this group. From the
Group editor, you may add, modify, copy, or delete any personnel
schedule.
You may assign a group to one or more existing groups, making it
a member of the selected groups. Any personnel schedules selected
for the groups doors will override the schedules for the referenced
group(s). Refer to Group Hierarchy on page 9-83 for more infor-
mation on access priority when multiple groups are involved.
Individuals
TAC I/NET Seven lets you add individuals to your access control
system. You assign an individual number and card number to indi-
viduals, assign schedule access to doors, and populate the users
personnel record. If there are multiple tenants, you choose the
tenant to which the individual belongs.
Individual Parameters
Note: The type of information displayed within the Individuals editors, as
well as your ability to add, delete, or modify individuals, is depen-
dent upon the privileges assigned to your host password (refer to
Host Passwords in Chapter 4, Host Functions, for more informa-
tion).
Card Number
First Name
Use up to 50 characters to define an individuals first name.
Fields 3-18
Each tenant has an associated access control database table. You
may customize the names of fields 3 through 18 as you wish (refer
to Field Names on page 9-77). The fields accept up to 50 charac-
ters, and can be used for any number of different uses: drivers
license number, vehicle type, employee number, date of birth,
height, weight, and so on.
Note: One of the user fields may be designated as a Unique Field in the
Access Control - Options editor (see Options on page 9-85). The
designated Unique Field may be left blank. If a value is entered, it
must be unique across all tenants and individuals.
Card
The individuals current card numbers are listed in both the hexa-
decimal and decimal values. Refer to Card Number on page 9-67
for more details. Use the Add New Card option to enter additional
card numbers for this individual.
Each card number must be unique across all users and tenants. You
may have multiple individuals with no card number (null), but if
you assign a card number of zero (0), only one individual can have
that card number.
Hex Number
The number for this card, in hexadecimal format. If you enter the
card number in decimal format, this value is calculated automati-
cally.
Decimal Number
The number for this card, in decimal format. If you enter the card
number in hexadecimal format, this value is calculated automati-
cally.
Resident in DPU
This parameter indicates whether this card will be stored as a resi-
dent record in the device controlling the door point(s) assigned to
this user. A card that is resident in the door controller can be veri-
fied even if communication has been lost between the door
controller and the SLI. Resident records are given priority in the
door controllers memory. Refer to Database Caching in the Door
Controller on page 9-11.
Note: All individual key/card numbers which use a translation table will be
resident in the door controller, regardless of the setting of this param-
eter. Refer to Database Caching in the Door Controller on page
9-11.
If your image file is in a format other than the ones listed, you must
first convert it to one of the supported formats using a third-party
graphic program.
Image Thumbnails
To conserve memory resources, the selected image will be resized to
fit the display window (maintaining aspect ratio), and a thumbnail
version is saved to the database as a .JPG file.
Each thumbnail is 222 x 191 pixels, and consumes approximately
46 KB of memory space. When adding a large number of thumb-
nails, be aware of the size of your database file. Refer to TAC I/NET
Seven Software in Chapter 1, System Configuration.
Record Type
Caution: When defining the Record Type, be aware that it is the job of the
Automatic DPU Restore function to download Temporary indi-
vidual records to door controllers beneath specific links. If you have
not enabled the Automatic DPU Restore function for a link, no
temporary individuals will be granted access through the link's doors.
APB
This parameter is used to determine the system response if a user
attempts to enter a zone without exiting, when the door(s) are
controlled by anti-passback and/or anti-tailgate. The following
options are available:
Hard (default) access is denied, generates an alarm.
Soft access is granted, generates an alarm.
Graced access is granted, no alarm is generated. This
effectively cancels anti-passback for the individual.
Note: This option is only available in systems using large key/card numbers
(see Large Number Support on page 9-5). The anti-passback
scheme is only active if anti-passback is activated for the door (see
Anti-passback on page 9-26). The same scheme is used for both
anti-passback and anti-tailgate, if activated (see Anti-tailgate on
page 9-26).
PIN
The personal identification number (PIN) for this individual. The
PIN is only required at doors configured to use a keypad to control
access. The default PIN is automatically generated using the
selected algorithm (see PIN Algorithm on page 9-88).
This field is read-only unless the User Defined PIN parameter is
activated in the Access Control Options editor (see User-defined
PIN on page 9-88). The PIN field displays and accepts six digits;
However, only the SCU1284 and DPU7920 with MIP (firmware
3.16 or later) support six digit PINs. Other door controllers
support five-digit PINs (refer to Door Controller Firmware Revi-
sions on page 9-80 for more information). If you define a PIN that
is less than six digits in length, the editor will automatically add
leading zeros to your entry when you click the OK button. Leading
zeros can be omitted when a user is inputting the PIN at a door.
Refer to Personal Identification Numbers (PINs) on page 9-78
for more information about the PIN feature.
Note: TAC I/NET Sevens PIN function also supports a duress code for use
in emergency situations. See your TAC I/NET Seven system adminis-
trator for more information about this feature.
Issue Number
Note: If your access control system is configured to use Wiegand cards, the
Issue Number described below will only affect the PIN assigned to the
individual. The card will never generate a Deny Issue message,
regardless of the Issue Number setting.
Door Selection
Define those doors to which this individual is to have access. Only
those doors that have already been assigned to the currently
selected tenant are available.
If the same door is selected for an individual and for the group to
which that individual is assigned, the individual assignment always
overrides the group assignment. This allows individuals to be
assigned to a group from which they receive the bulk of their access
privileges, but still be offered individual treatment for selected
doors. See Figure 9-4 for the logical flow of door assignments.
TAC I/NET Seven displays the door address and point type, the
name assigned to the point, and individual schedules by number
and name. Group schedules are also displayed by number and
name if the individual is assigned a group name.
Note: This feature is supported only in door controllers loaded with firm-
ware version 3.01 or later.
GOTO
GOTO lets you define a particular field at which you want the
displayed listing to start. For example, if the display order is set to
individual number, you can enter the individual number at which
you want the listing to start. This option is useful if you have many
individuals in your system and simply scrolling through the list is
too time-consuming.
Allocate Range
The allocate range function allows you to add a large number of
individual numbers to the system at once. This is useful for easily
adding a consecutive range of individuals to the system with group
access. Once you allocate a range, you may enter the individual
information using the Modify function from the Individuals editor.
The system prompts you if the range is invalid (Invalid Entry
message), or if the individuals already exist (Individual number
conflict message).
Access Request
Door Schedule
Check Defined Yes
Within
Indiv/Group Time Range?
Doors
"-- No Access" No
or
"-- Unselect"
Doorr Schedule
Check
Defined Yes
Secondary Within
Group Time Range?
Doors
"-- No Access" No
or
"-- Unselect"
Access Access
Denied Granted
The system then allows you to choose the group name, or select
none. The group must already exist within the system.
Note: The system will display the individual numbers as they are being
created and downloaded. Depending on the range of individuals, it
may take several minutes to complete the process.
Field Names
Each tenant within the system may create a unique set of text to
represent user-defined field entries #1 through #16 in the individ-
uals parameter editor. The field names may be modified to better
represent the contents of the record entry (i.e., field #1 can be
changed to Department #). Enter any 50 alpha-numeric charac-
ters for each field.
Display Options
Note: The actual fields displayed within the Display Options editor will be
determined by the access rights associated with your host password.
The information below assumes that all parameters are displayed.
Refer to Individual Field Selection in Chapter 4, Host Functions,
for more information.
The Option function allows you to set the presentation order of the
individuals. The presentation order can be determined based on
record type, individual number, or record field entries. The display
option parameters are as follows:
Permanent Records
This option can be enabled or disabled (Yes or No). Enabling this
option will include all personnel records with a record type of
Permanent.
Temporary Records
This option can be enabled or disabled (Yes or No). Enabling this
option will include all personnel records with a record type of
Temporary.
Disabled Records
This option can be enabled or disabled (Yes or No). Enabling this
option will include all personnel records with a record type of
Disabled.
Display Order
This field allows you to determine the presentation order of
personnel records by selecting a record field. For example, selecting
01. Individual causes personnel records to be displayed in order
of their assigned individual number. Selecting 02. Last Name
causes personnel records to be displayed in ascending order by their
last name.
Note: When you base the display order on the hexadecimal card number,
TAC I/NET Seven will not allow you to add, delete, or copy individ-
uals. Choose some other display order to re-enable the add, delete,
and copy functions.
Note: User-defined PINs require the use of large key/card numbers and are
not supported with key/card translation. Refer to Key/Card
Numbers on page 9-4 for more information about large key/card
numbers
PIN entry will complete automatically upon entry of the final digit.
Otherwise, you can manually complete the PIN entry by pressing
the # button as described in the following section.
Note: For best results, do not mix DPU firmware version 2.30 or later with
older DPU firmware versions if you wish to enter user-defined PINs.
It is possible to create a situation where the user's PIN is one number
(system-generated) for certain doors, and another number (user-
defined) on other doors, in which case the PIN shown in the Indi-
vidual Parameters editor would not be accurate for all doors.
Six-digit PINs
Six digit PINs are supported on the SCU1284 and on the DPU7920
with MIP (firmware 3.16 or later). All other door controllers
support PINs with a maximum of five digits.
If your system includes a mix of door controllers (i.e., some
controllers that do support six-digit PINs and some controllers that
do not support six-digit PINs), you should avoid assigning six-digit
PINs. This will prevent users from being locked out of certain doors
because a door's controller will not accept the user's complete PIN.
Generating PINs
You must ensure that the PIN Algorithm parameter within the
Access Control Options Editor is set properly for your application.
Refer to User PIN Code for more information.
The pin generation utility generates a list of PINs for specific card
numbers. A PIN generated within this utility is the same as the PIN
that can be viewed from the Individual Parameters editor.
This utility provides the following additional benefits:
More than one PIN can be viewed at a time.
PINs can be printed out for later viewing, or printed lists can
be provided to tenants.
When you generate PINs, a PIN table is created. You can print a
PIN report from this table. You can also preview the PIN report
before sending it the printer. Refer to the TAC I/NET Seven Oper-
ator Guide for complete instructions.
GROUP MODE
Permanent Temporary
INDIVIDUAL MODE
None with with Disabled
w/o Doors w/o Doors
Doors Doors
with Doors A A, B A A, D A A
Permanent
w/o Doors X B X D X X
with Doors C C, F C C, E C C
Temporary
w/o Doors X F X E X X
Disabled X X X X X X
Access Rights:
Individual doors Access is allowed through all individual doors during
A
each doors assigned personnel schedule.
Group doors Access is allowed through all group doors during each
B
doors assigned personnel schedule.
Individual doors (temporary individual) Same as A except access is
C additionally restricted to the dates and times defined for the individuals
temporary schedule.
Group doors (temporary group) Same as B except access is
D additionally restricted to the dates and times defined for the groups
temporary schedule.
Group doors (temporary individual/group) Same as B except access
E is additionally restricted to the dates and times defined for both the
individual and the group temporary schedules.
Group doors (temporary individual) Same as B except access is
F additionally restricted to the dates and times defined for the individuals
temporary schedule.
X No doors Access is not allowed through any doors.
Note: When the same door is assigned at both the individual level and at
the group level, the individuals personnel schedule will be used.
In addition to a users individual and group door assignments,
supplemental group schedules also affect a users access privileges.
Refer to Assigning Secondary Group Doors to the Individual on
page 9-74 for more information.
Group Hierarchy
If the individual is assigned to multiple groups, or to a group that
is a member of another group, the individuals ability to gain access
at a door will be determined by the heirarchy of his/her groups and
the schedule defined within each group.
The group displayed on the Door Selection summary indicates
only the topmost group in the Member of list (from the Group
Selection summary) that has a schedule for the door. This is not
necessarily the only group schedule used to determine access for
the individual or group. For example, if the top group does not
have any schedules assigned for this door, the Door Selection
summary will list the second group but it could be the schedule
for the third or fourth group that results in access being granted or
denied at a particular day and time.
Note: As the system steps through the hierarchy of schedules that affect an
individuals access at a door, the first occurance of No Access within
a schedule will deny entry at the door and processing will terminate.
Note: If the schedule hierarchy described above results with access being
denied, the door controller will then check for a secondary group
schedule that would provide access. Refer to Assigning Secondary
Group Doors to the Individual on page 9-74 for more information.
Options
The system allows the following system parameters to be modified
from the access control editor:
Supply Card Number from Reader
Note: The Supply Card Number From Reader option described below is
available only after you set the AC Reader Type to I/DISC or
Wiegand and the AC Reader Port to a COM port in the Configure
program. Refer to TCON298, TAC I/NET Seven Getting Started, for
more information about configuring TAC I/NET Seven.
If you are adding or modifying a record, the prompt for the second
operators host password will be displayed when you select OK to
exit the Individual Parameters editor. If you are deleting a record,
the prompt will be displayed after you confirm the delete request.
The second operators host password must meet the following
criteria in order to be accepted:
Defined The second operators password must have already
been added to the system.
Unique The currently logged in operators password cannot
be used again as the second password.
Authorized The second operators password must have the
Individuals function enabled. Otherwise, TAC I/NET Seven
displays an Insufficient Password Level error message. Refer
to Function Selection on page 4-7 for more information.
TAC I/NET Seven will only accept the second password if it meets
the criteria described above. Otherwise, the action you are
attempting will not be accepted (i.e., no records will be added or
deleted, and no modifications to a record will be saved).
Note: You must define the following audit trail parameters before any host
workstations (remote or local) will be capable of receiving audit trail
messages from this host workstation. Refer to Audit Trail Messages
on page 9-16 for more information.
User-defined PIN
This option specifies whether the operator can edit the personal
identification number (PIN) for individuals using the Individual
Parameters editor (see PIN on page 9-72).
When this feature is activated, the selection in PIN Algorithm
(below) specifies the method used to generate the default PIN. If
this feature is not enabled, the generated PIN is read-only.
User-defined PINs are supported when all of the following require-
ments are met:
The door controllers firmware is version 2.30 or later. (You
must use system-generated PINs for door controllers with a
firmware revision prior to 2.30).
DIP switch 7 at the door controller is ON or the Card Transla-
tion option is enabled in the Door Extension editor
The individual is directly assigned a large key/card number
(i.e., a key/card translation table is not being used to translate
the users key/card number).
PIN Algorithm
This option specifies which algorithm is used to calculate the
default personal identification numbers (PINs) for key/card
holders. If the User defined PIN parameter is activated, the default
PIN can be edited from the Individual Parameters editor. If not, the
PIN is read-only at the host workstation (i.e., within the Individual
Parameters editor and the PIN Generator utility). The following
options are available:
None Choose this setting if you do not wish to automati-
cally generate user PINs. When entering a new individual, the
operator must manually enter a PIN; you will not be able to
save the individual parameters until a PIN is entered. This
option is only available if the User Defined PIN checkbox is
activated.
Standard Choose this setting if your access control system is
configured to use any reader type other than Wiegand 66.
Wiegand 66 Choose this setting only when your access
control system is configured to use Wiegand 66 readers.
When a user field is selected as the unique field, the system does not
verify that existing data is unique. However, if an individual record
is opened in the Individual Parameters editor (see Individual
Parameters on page 9-66), the designated unique field is evaluated
and must be made unique before any changes can be saved. The
operator may choose to cancel the changes and thus leave the field
in a non-unique condition.
Individual Activity Manager - Configure
Use this option to enable and configure the Individual Activity
Manager (IAM) system. Refer to the following section for more
information.
Two-man Rule
Note: The two-man rule requires that the door controller is an SCU1284.
Depending on the requirements of your access control system, you
may wish to restrict certain individuals from entering into a secure
area without an escort. For example, you may allow visitors to enter
your companys product center, but only if they are accompanied
by a member of the marketing department.
Using a combination of door attributes and personnel schedule
settings, you can implement a two-man rule for select doors in TAC
I/NET. The following door attributes are used for this purpose:
Note: Before you can enable either of the following door attributes in a
personnel schedule, you must first add these attributes to the door.
Sequence of Events
The sequence of events that occur when using the two-man rule are
as follows:
1. An Escort Required key/card is presented at the door. This
key/card may also have the Escort attribute, however, as the
first key/card of the sequence it is not interpreted as an
Escort key/card.
2. TAC I/NET validates the Escort Required key/card:
If the key/card is not valid for any reason, access is
denied.
If the key/card is valid, processing continues.
3. The key/card reader enters into a 10-second wait mode,
waiting for another key/card.
4. Another key/card is presented at the door:
If the key/card is not presented before the 10-second wait
mode expires, access is denied.
If the key/card is presented during the 10-second wait
mode, processing continues.
5. TAC I/NET validates the Escort key/card:
If the key/card is not an Escort key/card, or it is not
valid for any reason, the 10-second wait mode restarts
and the reader continues to wait for another Escort
key/card. If no other key/card is presented before the 10-
second duration elapses, access is denied.
If the key/card is a valid Escort key/card, access is
granted.
10
18
Intrusion Alarm System
Note: The editors used for an intrusion alarm system will not be available
unless you connect to a 7798C with firmware revision 1.07 or later.
TACs intruder alarm system (IAS) consists of a mix of security
control products that can be combined and configured to provide
intruder detection and alarm functions.
OP5 Event
Door Parameter AMT Entry Description
Log Entry
Reader entry Reader Entry Login User successfully logged on at the OP5
User logged out of the OP5 (manually or
Reader exit Reader Exit Logout
automatically)
User attempted to login during a time not
Denied - schedule Deny entry Sched Log Fail
allowed by his/her personnel schedule.
Denied - APB / ATG NA NA NA
User attempted to login with an incorrect
Denied - tenant Deny entry Ten. Log Fail code or login timed out while OP5 was
operating in Secure mode.
Level 3 user attempted to log on while
Denied - disable Deny entry Dsbl. Log Fail
Maintenance was turned OFF
User attempted to login at an OP5 that has
Denied - selection Deny entry Sel. Log Fail not been assigned to the user or his/her
group(s), or the user is disabled.
User attempted to login with an incorrect
Denied - PIN Deny entry PIN Log Fail code or login timed out while OP5 was
operating in Secure/PIN mode.
Duress entry NA NA NA
Duress exit NA NA NA
Bad card read NA NA NA
Door open too long NA NA NA
Door forced NA NA NA
Door normal NA NA NA
SLI not available NA NA NA
Door re-locked NA NA NA
Mode messages NA NA NA
Request to exit NA NA NA
Note: IAS operators have the ability to change their own PIN from an
arming terminal. This makes it possible for two or more IAS opera-
tors to have the same PIN. For this reason, PINs do not count toward
the number of unique codes provided by the system.
State: Description:
NRdy Norm NRdy: Zone or sensor is not ready.
Norm NRdy
Norm: Zone or sensor is ready.
Tamp Tamp
TmpS TmpS Tamp: Zone or sensor is in a tamper condition
Falt Falt (open circuit).
Alrm Alrm
TmpS: Zone or sensor is in a tamper condition
Inhb Inhb
(short circuit).
Islt Islt
Falt: Zone or sensor is in a fault condition.
Alrm: Zone or sensor is in an alarm condition.
Inhb: Sensor is inhibited.
Islt: Sensor is isolated.
Note: If you delete a point from TAC I/NET Seven without removing it
from the IAS, any new point you create at the same point address
could adversely affect the operation of the IAS. To correct this issue,
you can simply open the IAS editor and then close it again by clicking
the OK button. This will remove references to the deleted point from
the IAS.
the 7798c, the Ethernet cable gets unplugged from the dialer,
or the dialer losses communication with the ARC.
Bit offset: any
Suggested name: Dialer Fault
Type: DA
Class: Internal
Number of bits: 3
State descriptions: Norm, NRdy, Tamp, TmpS,
Falt, Alrm, Inhb, Islt
Normal state: 0 (Norm)
Supervision: None
SubLAN Fault Controlled by the IAS. Changes from 0 to 1
if a fault is detected on the subLAN. This can occur if an OP5
arming terminal or an SCU gets disconnected or losses power.
Bit offset: any
Suggested name: SubLAN Fault
Type: DA
Class: Internal
Number of bits: 3
State descriptions: Norm, NRdy, Tamp, TmpS,
Falt, Alrm, Inhb, Islt
Normal state: 0 (Norm)
Supervision: None
EPS Fault Shows a 1 if the SCU losses power from the
transformer connected at TB1. This point is required on each
SCU that is being used as a power supply in the IAS (i.e., each
SCU that connects to a transformer). This point must have
the point address (PP) of the SCUs primary address number.
Bit offset: 09 (on SCUs primary address)
Suggested name: EPS Fault
Type: DA
Class: Internal
Number of bits: 1
State descriptions: Norm, NRdy, Tamp, TmpS,
Falt, Alrm, Inhb, Islt
Normal state: 0 (Norm)
Supervision: None
IAS Messages
If you configure the host masks on your TAC I/NET Seven worksta-
tion to accept messages from the IASs 7798C, you can view IAS
activity in AMT. This is the same type of information that a user
can view in the error log accessible from an OP5 arming terminal.
However, AMT on the TAC I/NET Seven host will have the added
ability of displaying the actual first and last name associated with
an IAS operator. The error log displayed at an arming terminal can
only show the tenant number and individual number of an IAS
operator.
Example of AMT messages vs. error log messages
In the following example, a user at an arming terminal has issued a
Set command to a zone. The zone has an exit route and therefore
transitions to Stg before going to Set. The users first and last
name are included in AMT but do not appear in the event log
viewed from an arming terminal. The users group membership is
also not included in the event log.
AMT messages:
11
58
Direct Digital Control
Points
Points can be used as inputs to DDC modules when the input is the
result of a calculation (internal point), the state/value sensed by an
external point, or the state/value of a point controlled by the oper-
ator. Points can also receive module output when you want an
action to occur as the result of a DDC module algorithm. Define
module inputs and outputs as points by entering either the point
name or the point address.
Lines
It is often desirable, or necessary, to chain several DDC modules
together in a cascade of control. This requires some way of making
the output of one module available to other modules. This is
accomplished with lines. These lines can transmit analog or
discrete data. Lines are equivalent to pneumatic tubing intercon-
necting pneumatic control devices and generally follow the same
rules:
Only one module should output to a specific line number.
When possible, assign the same number to a module and the
line to which it is delivering its output. This eliminates confu-
sion as to which line belongs with which module and vice
versa.
On the other hand, a specific line can act as an input to as
many modules as is necessary.
Note: The HiLo and Floating module types have two outputs. When you
assign a line number to the first output of one of these modules, we
recommend that you leave the next available line number blank to
avoid future confusion if and when you add the second output.
Constants
Constants are values or state conditions that never change. You can
enter a constant as a value (72 degrees) or a state (0 or 1). A
constant may be used as a DDC module input; however, a constant
may not be used as an output of a module. A constant output from
a DDC module would make the module unnecessary.
DDC Modules
TAC I/NET carries out direct digital control through a series of
modules. Module parameters are explained in this chapter. Each
module has its own algorithm. With a basic understanding of
control theory and application, these algorithms are easy to under-
stand and apply.
Technically, there are seven types of DDC modules; however, no
one controller type provides all seven module types. The seven
DDC module types are:
Two-position HiLo
PID Relay
Floating Calculation
Reset
The DCUs and PCUs provide all but the Calculation module.
Micro Regulator (MR) controllers provide all but the HiLo
module. Application Specific Controllers (ASCs) provide all but
the HiLo Module. UCs provide variations of the PID and Floating
modules.
Each module type has its own data entry screen where you define
parameters such as inputs, algorithm modifiers, and output desti-
nations. These data entry screens are described in the Operator
Guide chapter dealing with direct digital control.
100 O hl O ll Ts Td
V n = V n 1 + --------- --------------------- E n E n 1 + ----- E n + ------ E n 2E n 1 + E n 2
PB I hl I ll Ti Ts
PP II D
D
The elements used in the PID control action algorithm are listed
and described in Table 11-2. The PID module output response is
governed by the actuator mode selected. In direct mode, a positive
error produces a positive output correction. In the reverse mode, a
positive error produces a negative output correction. Refer to
Output Mode on page 11-41 for more information.
Element Description
th
Vn Output at the n sample (i.e., current output).
th
Output at the n 1 sample (i.e., previous output).
Vn1 Note: This element, Vn1 , is set to the control point (failsafe) value, Co , when the
module is initialized.
Element Description
Proportional band. The percentage error in the process variable that produces full range
PB
output travel.
Ohl Output high limit (in output units).
Oll Output low limit (in output units).
Ihl Input high limit (in output units).
Ill Input low limit (in input units).
th
Error at the present (n ) sample (i.e., the difference between the input, PV, and the
En
setpoint, SP (in input units)).
th
En1 Error at the previous (n 1) sample (in input units).
th
En2 Error at the second most previous (n 2) sample (in input units).
Ti Integral reset interval (in seconds).
Td Derivative rate interval (in seconds).
Ts Sample interval (in seconds).
The parameters for the PID module are listed in Table 11-3.
Note: P-Only mode is not available in the EPROM versions of the 7700 and
7740 DCUs.
or
100 O hl O ll
Output = Control Point + --------- --------------------- Input Setpoint
PB I hl I ll
In this P-only mode, the input range (input high limit minus low
limit) must be centered around the setpoint, the module output
must always be 0100, and the control point must be 50. The input
low and high limits are not used as the limits of the process variable
for failsafe purposes. However, if the value of the input rises or falls
outside the input high or low limits, the module output is clamped
20, the input limits are 0100, the output limits are 0100, the
current error (En) is 2, and the error at the last sample interval
(En1) was 0. The calculation is as follows:
The example values used in the equation above caused the module
output to increase from 50% to 60%. In the next sample interval,
the 60% output from the calculation above becomes the value for
Vn 1 and the previous value of En becomes the value of En 1 . If the
input variable has not yet responded to our control output (actual
mixed air temperature is still 57F), then the current error (En) is
still 2 and the calculation would be:
consistent with that sample rate (i.e., the mixed air temperature is
not changing any faster than every 60 seconds). If we change the
proportional band to 5%, we observe the following change in
performance:
We can see that this change instructs the output portion of the
module to move to a position equivalent to 90% of its output
range. This action will, in all likelihood, result in severe overshoot
and induce oscillation.
Assuming that the process controller can produce a rapid change in
the controlled process and the process variable drops from 57F to
53F, we can see that the next sample, taken 60 seconds later, will
result in the following action:
T
I = -----s E n
Ti
In this example, we will assume that our process (mixed air) has
settled at 56F and that proportional control is no longer making
corrections. We will use a sample interval of 30 seconds and a reset
interval of 600 seconds. The calculation is as follows:
Once the process variable is less than the setpoint, the integral
contribution is negative and we correct the overshoot. Overshoot
caused by the integral element is generally small in magnitude and,
by its very nature, is self-correcting. The reset contribution at this
interval is now 0.025% and the proportional contribution is
2.5%. We add these values to the previous output (52.35%) for a
total P & I output of 49.825%.
Increasing the integral or reset interval to 1200 reduces the effect of
the integral increase or decrease by one half. Using the first
example, but substituting 1200 as the reset interval, we observe that
the contribution is 0.125% as opposed to the 0.25% previously.
100 30
I = --------- ------------ 56 55
20 1200
I = 5 0.025 1
I = 0.125%
I = 0.5%
While this is not a complex relationship, it is one that is very impor-
tant and must be understood by the controls engineer and by the
operating engineer. It is also noteworthy that decreasing the reset
interval, while the sample interval remains constant, will increase
the magnitude of the integral contribution. When selecting a reset
interval, it is best to start high.
With a reasonably accurate selection of parameters, the integral
portion of PID quickly reduces the offset to zero, thereby achieving
the desired result; our process (HVAC system, chiller, etc.) running
exactly at setpoint.
Controls engineers are generally bound to strive for the most
comfortable control for the least expenditure of energy. The ability
to control overshoot, undershoot, and offset, permits the controls
engineer to more closely coordinate the complete control scheme.
Occasionally, it is desirable to allow some offset since small correc-
tions could actually cause the expenditure of energy unnecessarily.
Derivative Corrections
Now that we have a process running in equilibrium, we must come
back to real world conditions and recognize that external forces are
constantly working to upset our process. We may observe a quick
change in the load imposed on our HVAC system by a rapid
increase in body heat and lighting load, for instance, at 8 a.m.,
when everyone reports to work. In order to prevent substantial
overshoot in our control action, we need to be able to observe,
measure, and correct for the speed (rate) at which our process is
Since the result is zero, the derivative element has no effect. If there
is no change in error, there can be no rate of change derived.
Now we assume that the return air temperature starts to rise (due
to people occupying space, lighting load, etc.) and the impact is
sufficient to raise the mixed air temperature to 56F. Keep in mind
that for the previous two rate intervals there has been no error.
and corrects for the rate of change. The effect works just the oppo-
site if the process variable moves toward the setpoint at a rapid rate
such as might be observed during morning recess in a school room.
In this example, we will assume the process to be room control. We
are sensing room temperature, and we are controlling a reheat coil
valve. The setpoint for this example is 70F. During the three inter-
vals that we are concerned with, the errors are: En = 0, En 1 = 1,
and En 2 = 4.
100 60
D = --------- ------ 0 2 1 4
20 30
D = 5 2 2
TR PB Ts Td
V n = --------------------- E n E n 1 + ----- E n + ------ E n 2En 1 + E n 2
I hl I ll Ti Ts
PP II D
D
Element Description
th
Output at the n sample (i.e., current output). A positive value
Vn here results in an increase pulse. A negative value results in a
decrease pulse (on a direct acting Floating module).
TR Throttling range. Actuator stroke time in seconds.
Proportional band. The percentage error in the process variable
PB
that produces full range output travel.
Ihl Input high limit (in input units).
Ill Input low limit (in input units).
th
Error at the present (n ) sample (i.e., the difference between the
En
input, PV, and the setpoint, SP (in input units)).
th
En1 Error at the previous (n 1) sample (in input units).
Error at the second most previous (nth 2) sample (in input
En2
units).
Ti Integral reset interval (in seconds).
Td Derivative rate interval (in seconds).
Ts Sample interval (in seconds).
output when the discrete input (coil) value is 0. When the discrete
input (coil) is 1, the module passes the state/value of the DI = 1
port to the output.
This module can also function as an interval time delay relay
(INT), as a delay-before-break relay (DBB), or as a delay-before-
make relay (DBM). Refer to Settings (Relay Types) on page 11-48
for detailed information regarding these relay types.
The parameters for the Relay module are listed in Table 11-11.
The CALC module plays a central role for the other DDC modules
in the MR controller and ASC. The active setpoint (occupancy
detection, Heat/Cool selection, schedule, etc.) for the other DDC
Sample Interval
Modules
Two-position, PID, Floating, Reset, HiLo, Relay, and Calculation
Description
A number between 1 and 255 that represents the number of
seconds between module outputs. This option lets you adjust the
speed of the module to match either the expected response time of
the process variable input (Two-position, PID, Floating, Reset, or
HiLo modules) or the desired response time of the output (Relay
and Calculation modules). For example, a module controlling
static pressure might require a sample interval as short as one
second since the process (static pressure) responds very quickly to
the control output. Room temperature control normally requires a
much slower sample interval, in the range of 60 seconds, since the
temperature in a room does not change rapidly.
Setpoint
Modules
Two-position, PID, and Floating
Description
The desired value of the input point being controlled. Typically this
is the desired room temperature or something similar. It may be
represented by a line, point, or constant. Refer to Input and
Output Designations on page 11-1 for more information about
each of these setpoint options.
Setpoint Offset
Modules
Two-position, PID, and Floating
Description
You may want to use setpoint offset if you have defined your
setpoint as a line or point. If your setpoint is a constant then offset
is typically not used. The setpoint offset value can be between 100
and 100. The default is zero. Setpoint offsets are useful when you
want cascaded control. That is, you have several modules which
share a common setpoint (line or point) which need to be stag-
gered in their operating range. In this case, use the same setpoint
(line or point) for each module and assign each module a unique
setpoint offset value. The setpoint offset is displayed in the same
engineering units as the line or point setpoint it offsets.
Setpoint Differential
Modules
Two-position
Description
The degree of precision for this module. Differential is the temper-
ature range over which no action takes place. The temperature is
allowed to rise or fall unchecked until it reaches the opposite limit
of the differential. In a situation where temperature is critical, you
may want a very small or even non-existent differential. Define a
larger differential for situations where exact temperature control is
less important.
A larger differential means that equipment is turned on and off less
often. This saves energy and money spent on equipment operation.
You must weigh this against the temperature needs of the environ-
ment affected by this module.
To determine the actual temperature control range, divide the
differential in half. The controlled range is equal to the setpoint
plus or minus one-half of the differential. For example, if your
setpoint is 76 and you select a differential of four, the measured
temperature must rise above 78 degrees before the module controls
an HVAC unit on (space is too warm). The temperature must fall
below 74 before the point controls an HVAC unit off (space is too
cool). This creates a control range of 74 to 78 degrees.
value at the low end of the normal acceptable range of the module
setpoint. The default value is zero. If the setpoint will vary below
zero, such as for a refrigeration case, this value must be set to a
lower value than default. If the setpoint drops below the input low
limit, the module immediately declares a bad input and,
depending on the applicable module, one of the following actions
occur:
The Two-position module outputs the failsafe command state
(0 or 1).
The PID module outputs the control point value, unless oper-
ating in P-only mode. In P-only mode, the PID module
clamps the output to either the output high limit or the
output low limit, depending on the actuator mode setting
(refer to P-only Mode of Operation on page 11-7 and
Output Mode on page 11-41).
The Floating module stops any pulse outputs.
Process Variable
Modules
Two-position, PID, and Floating
Description
The input for the module (i.e., the point, line, or constant which
represents the value of the process being controlled (air tempera-
ture, water pressure, etc.)). The input for all DDC modules may be
a line, point, or constant. Refer to Input and Output Designa-
tions on page 11-1 for more information about each of these input
options.
Output
Modules
Two-position, PID, Reset, Relay, and Calculation
Description
You can direct the output of the module to a line or point. Select a
line if the output is used by another DDC module. Select a point if
the output is used to initiate an event sequence, to provide interme-
diate control, or to directly control an action. If you select a line,
enter a number (164 for non-MRs, 116 for MRs) that corre-
sponds to the number of this module. If you select a point, the type
of point you may use depends on the module being used:
In the Two-position module, you may use an external or
internal DO or DC point (or an internal DI or DA point in
non-MR controllers). Use an external point when you want
the Two-position module output to directly control an action
such as turning on a fan, or turning off a pump. Select an
internal point to initiate an event sequence.
Increase Output
Modules
Floating
Description
In a DCU or PCU, you may use a line or a DO point for this param-
eter. In an MR or ASC, only a DO point (not a line) can be used as
the output. In the UC, the user simply enters the hardware bit (0
7) to be controlled by the UC Floating extension.
The Floating module issues timed pulse outputs to rotate a bidirec-
tional motor. This parameter directs a timed pulse to increase the
output. This results in a specific action, such as the opening of a
valve.
When issuing a pulse to a DO point, the actual output from the DO
point (energize or deenergize) is determined by the definition of
the points control command pair (refer to Control Description
in Chapter 6, Input and Output Points for information concerning
control descriptions and commands). It is critical to define the first
control command of the pair as the energize or one command.
Note: If you select Point for Increase output in an MR, make sure you
also select the correct output point from the point drop-down box. If
you leave the default value of None in the drop-down box, the first
output point on the MR is automatically pulsed. This can cause a
Decrease Output
Modules
Floating
Description
In a DCU or PCU, you may use a line or a DO point for this param-
eter. In an MR or ASC, only a DO point (not a line) can be used as
the output. In the UC, the user simply enters the hardware bit (0
7) to be controlled by the UC Floating extension.
This parameter reverses the activity instigated by the output
increase, described above. For example, if the increase pulse opens
a valve, the decrease pulse closes a valve.
When issuing a pulse to a DO point, the actual output from the DO
point (energize or deenergize) is determined by the definition of
the points control command pair (refer to Control Description
in Chapter 6, Input and Output Points for information concerning
control descriptions and commands). It is critical to define the first
control command of the pair as the energize or one command.
Note: If you select Point for Decrease output in an MR, make sure you
also select the correct output point from the point drop-down box. If
you leave the default value of None in the drop-down box, the first
output point on the MR is automatically pulsed. This can cause a
conflict if there is any other control action on that point (time
schedule, temperature control, DDC module, etc.), potentially
causing the point to be energized and de-energized constantly.
High Output
Modules
HiLo
Description
This parameter directs the maximum output value to either a line
or a point. The HiLo module is capable of providing the high signal
output and low signal output simultaneously.
Low Output
Modules
HiLo
Description
This parameter directs the minimum output value to either a line
or a point. The HiLo module is capable of providing the high signal
output and low signal output simultaneously.
Note: If you enter a 0 in this parameter, the output will never change
(i.e., 0% of any output range is 0).
Note: In a PID module where I and/or D are being used, you can enter any
desired output range, such as 318 (psi) or 400800 (cfm). In a P-
only PID module (see P-only Mode of Operation on page 11-7) an
output range of 0100 must be used.
Note: The operation described here does not occur if the PID module is
operating in P-only mode. P-only mode operation only occurs if you
enter a zero in both the rate interval and reset interval parameters.
Refer to P-only Mode of Operation on page 11-7. P-Only mode is
not available in the EPROM versions of the 7700 and 7740 DCUs.
Description
In DCUs and PCUs, this is the percent of the input range (the range
between the high and low input limits) that the input value must
change in order to change the output from zero to 100 percent. This
parameter setting can be a value between 1 and 1,000.
In DCUs and PCUs, proportional band is defined by the following
equation:
Control Band-
------------------------------- 100
Input Range
Note: In the PID module, if you enter a reset interval value other than zero,
the module operates in either PI or PID mode. In either mode, the
standard PID algorithm is used (refer to PID Algorithm on page
11-5).
If you enter a reset interval value of zero, the PID module operates in
either PD or P-only mode. The PD mode uses the standard PID algo-
rithm. The P-only mode uses an algorithm specific to that mode
(refer to P-only Mode of Operation on page 11-7). P-only mode is
not available in the EPROM versions of the 7700 and 7740 DCUs.
Note: In the PID module, if you enter a rate interval value other than zero,
the modules operates in either PD or PID mode. In either mode, the
standard PID algorithm is used (refer to PID Algorithm on page
11-5).
If you enter a rate interval value of zero, the PID module operates in
either PI or P-only mode. The PI mode uses the standard PID algo-
rithm. The P-only mode uses an algorithm specific to that mode
(refer to P-only Mode of Operation on page 11-7). P-only mode is
not available in the EPROM versions of the 7700 and 7740 DCUs.
Failsafe Command
Modules
Two-position
Description
The action executed when the input or setpoint is no longer valid.
Use this option to plan system response to a setpoint or sensor
failure. Acceptable settings are 0 or 1. The default is 0.
The failsafe command is executed if the setpoint exceeds the
setpoint high or input low limits or if the process variable input
exceeds its sensor limits as defined in the Resident I/O Points
editor. A setting of 0 results in the first control command (of the
control command pair assigned to this output) being issued. A
setting of 1 results in the second control command being issued to
Note: A 0 command results in the first control command of the pair being
issued to the output point. This could represent either the energized
or deenergized state of the output depending on how the point's
control descriptions and commands are defined in the station param-
eters editor. Likewise, a 1 command results in the second control
command of the pair being issued to an output point.
Output Mode
Modules
Two-position, PID and Floating
Description
This parameter defines the response of the module. The actual
response differs depending on the selected module:
Two-position module: The mode you select determines what
happens when the input is higher or lower than the setpoint
(plus or minus one-half the differential).
PID or Floating module: The mode you select determines
whether module output increases or decreases as the error
(input minus setpoint) increases (input rises). This function
must be used to fit the response of the end device controlling
the process (i.e., normally open or normally closed valve or
damper).
The mode selection is similar to the decision you must make when
you buy an electric thermostat. Do you want one that is normally
open or normally closed, a heating or cooling thermostat?
There are two mode options:
Direct
Two-position module: If you select this mode, the two-
position module issues a 0 command to the output point
or line if the input rises above the setpoint plus one-half
Note: A 0 command results in the first control command of the pair being
issued to the output point. This could represent either the energized
or deenergized state of the output depending on how the point's
control descriptions and commands are defined in the station param-
eters editor. Likewise, a 1 command results in the second control
command of the pair being issued to an output point.
Adaptive Control
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
Maximum Bump
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
A number between 0 and 100 percent. The default is 5 percent. This
parameter determines the size of the PID or Floating output step
change for automatic tuning in reference to the module control
point (PID) or midscale position (Floating). The bump should be
large enough to cause a change in the input (process variable) that
is greater than the noise band, but not so large as to damage the
controlled equipment. The typical range is 5 to 25 percent.
Settling Time
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
The settling time can be between 10 and 1,800 seconds. The default
is 120 seconds. This parameter is an estimate of the time it takes for
the input (process variable) to settle down after a setpoint change.
It is used for automatic and adaptive tuning as the minimum time
interval between a process disturbance and the next action. For
automatic tuning, it is the time interval between setting the output
to either the control point (PID) or to midscale (Floating) and the
Maximum Overshoot
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
This parameter is a number between 0 and 100 percent. The default
is 10 percent. This parameter, along with target damping
(described below), controls the shape of the initial output response
to a process disturbance. The magnitude of the module response is
a qualitative measure of the controller. The typical range for this
parameter is between 10 and 50 percent.
Target Damping
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
Target damping can be set to a value between 1 and 75 percent. This
parameter represents the desired reduction in the process variable
overshoot from the first overshoot (maximum overshoot) to the
second, and so on. A value of 25 percent means the second over-
shoot magnitude should be 25 percent of the first. The recom-
mended value for this parameter is the default: 25.
Noise Band
Modules
PID and Floating
Description
This tuning parameter is available in the PID and Floating modules
of DCUs and PCUs; it is not available in MRs, UCs, and ASCs.
Noise band can be set to a value between 0 and 100 percent. The
default is 2 percent. This parameter, specified as a percentage of the
input range, is the minimum process variable change that initiates
an adaptive calculation of the module parameters (provided the
Adaptive Control discrete point described above is equal to one).
Because adaptive tuning attempts to reshape the process variable
response after every such change, it is important to make the noise
band big enough to prevent inadvertent unnecessary tuning. The
typical range is between 2 and 10 percent.
Primary Input
Modules
Reset
Description
Select a line, point, or constant for this parameter. It is most
commonly a point, usually a sensed variable such as outside air
temperature. It can also be a line that is output from another
module, or a constant. In an MR- or ASC-resident module, only a
line or point can be specified a constant cannot be used.
Note: At primary input 1, the module outputs the value entered as primary
output 1; the same occurs with primary input 2 and primary output
2. This lets you define either a directly proportional reset schedule or
an inversely proportional reset schedule.
Secondary Input
Modules
Reset
Description
Select a line, point, or constant for this parameter. In the boiler
example described previously, this would be an AI point sensing
the space temperature. This input secondarily resets the output
Inputs 1 4
Modules
HiLo
Description
A line, point, or constant. Each of the four inputs are normally the
same type (analog or discrete). Mixing of discrete states and analog
values is typically not done.
DI = 0
Modules
Relay
Description
This is the state/value passed to the output by the Relay module
when the discrete input (see above) is 0. Select a line, point, or a
constant. A constant is often used here to direct a setpoint to an
unoccupied value when a point, such as an air handling unit, is off,
in order to close a modulating valve or perform a similar task.
DI = 1
Modules
Relay
Description
This is the state/value passed by the module when the discrete input
(see above) is 1. Select a line, point, or a constant.
Delay Before Make This relay type delays the output of the
DI = 1 state/value following a transition of the discrete input from
0 to 1. The duration of the delay is defined by the time delay param-
eter. The time delay only affects the output of the DI = 1
state/value. When the discrete input transitions from 1 back to 0,
the relay immediately directs the DI = 0 state/value to the module
output.
Delay Before Break This relay type delays the output of the
DI = 0 state/value following a transition of the discrete input from
1 to 0. The duration of the delay is defined by the time delay param-
eter. The time delay only affects the output of the DI = 0
state/value. When the discrete input transitions from 0 to 1, the
relay immediately directs the DI = 1 state/value to the module
output.
Interval Timer This relay type sustains the output of the DI = 1
state/value for a specified duration following a transition of the
discrete input from 0 to 1. The DI = 1 state/value is directed to the
module output for a duration defined by the time delay parameter.
When the time delay expires, the output automatically reverts back
to the state/value of the DI = 0 input, regardless of the discrete
input state.
Time Delay
Modules
Relay
Description
This parameter defines the number of seconds for the interval
timer, delay-before-break, and delay-before-make relays. Enter a
number between 0 and 86,400 seconds (24 hours). The default is
zero seconds. Time delays are not used by the standard relay.
DI Select
Modules
Relay
Description
This input can be a line or a point. If you select a point you must
use a DO, DI, DC, or DA point type. If you select a line it must carry
a discrete state (0 or 1) rather than an analog value. This parameter
is comparable to a relay coil. If the state of the line or point entered
here is a 1, the relay module is energized and the module passes
the state/value entering at the DI = 1 port. When the Relay module
is deenergized, the DI = 0 state/value is passed to the module
output.
History
TAC I/NET provides an on-line tuning capability for PID and
Floating modules (up to four modules per controller). In order to
activate the tuning function, you must first add the PID or Floating
module(s) to the history record.
Due to memory requirements, there is a limit of four modules that
can be contained in the controllers history record at any one time.
If you try to add a fifth module, you will receive an error message.
If you need to add another module, delete an existing module first.
Tuning
Tuning is the on-line, automatic adjustment of PID or Floating
module parameters. TAC I/NET provides the following tuning
functions:
Manual Tune
Automatic Tune
Input/Output Plot
Each of these tuning features is described in the following para-
graphs.
Manual Tune
The manual tune function displays current module parameter
values and allows you to adjust these values. You may then monitor
the module operation and, if necessary, make further adjustments.
The manual tune parameters are described in the following para-
graphs. Refer to the individual PID and Floating module descrip-
tions earlier in the chapter for extended definitions of setpoint,
proportional band, reset interval, and rate interval.
Setpoint
This is the current value of the setpoint (line or point) or the
permanent setpoint (constant; defined when you created the PID
or Floating module). You may manipulate the current setpoint
value.
Proportional Band (percent)
This displays the permanent and current proportional band values.
The permanent proportional band is the one you defined when you
created the PID or Floating module. You may vary the current
proportional band between 1 and 1000 percent.
Reset interval (seconds)
This displays the permanent and current reset interval values. The
permanent reset interval is the one you defined when you created
the PID or Floating module. You may vary the current reset interval
between 0 and 3,600 seconds.
Rate Interval (seconds)
This displays the permanent and current rate intervals. The perma-
nent rate interval is the one you defined when you created the PID
or Floating module. You may vary the current rate interval between
0 and 3,600 seconds.
Input/Output Plot
This feature displays a plot of the input and output of the selected
module. You can then observe the on-line results of the changes
you made in the Manual Tune editor.
Automatic Tune
This function provides automatic calculation of the P, I, and D
constants used in the PID and Floating modules. This is done by
driving the output of the PID module to the control point value, or
to midscale in the case of a Floating module, for the duration of the
settling time. The output is then alternately forced up and down
numerous times by the value of the maximum bump percentage.
Settling time and maximum bump are defined earlier in this
chapter. By monitoring the resulting changes in the process vari-
able input to the module, the controller automatically calculates
and enters the P, I, and D constants into the module editor.
Automatic Tuning Parameters
There are two parameters associated with automatic tuning.
Tsettle = settling time.
Vbump% = maximum bump percent.
A third parameter is derived from those already defined:
Vbump = maximum bump, which is the maximum bump
percent multiplied by the difference between the output high
limit and the output low limit (see below).
Vbump = Vbump% (Output High Limit Output Low Limit)
Automatic Tuning Process
Figure11-1, Automatic Tuning illustrates the automatic tuning
process. The process is explained thereafter.
For a PID module, at time To , the output is moved to the control
point (failsafe) output value specified for the module, and the scan
rate is changed to 1 second. The output stays at the control output
for the settling time (Tsettle).
For a Floating module, at time To , the increase output is pulsed for
a period equal to two times the throttling range. This is followed by
the decrease output being pulsed for a time equal to one-half of the
throttling range. This is done to ensure that the output is at
midscale (50%). At this time, the scan rate is changed to 1 second.
The output stays at 50% for the settling time.
Settling Time
Max.
Output Bump
Max.
Input Bump
T0 TX TX + 1 TX + 2
Auto-Tune Input at
Start T0 + T settle 1 Cycle 1 Cycle Last Cycle
5 Cycles
In either case (PID or Floating), after the settling time, the input is
recorded, and the output is then increased by Vbump . The editor
determines how long it takes for the input (PV) to settle-out (rate
of change less than 5%).
Warning: The settling time (Tsettle) should be the amount of time it takes for the
rate of change of the input (PV) to become 5% or less AFTER it has
changed by an amount greater than 5% due to the output being
changed by the maximum bump (Vbump). After any change in the
output, the rate of change of the input must become 5% or less within
the settling time or a time-out error will occur.
The output is then decreased from either the control point (fail-
safe) output, Co , (PID module) or midscale (Floating module) by
Vbump . The output stays there until the input becomes the value
which it was at Time = To + Tsettle .
Warning: If the input does not cross the value of the input at Time = To + Tsettle
within the settling time, a time-out error will occur.
the time at each change of output (Tx , Tx+1 , ... Tx+10) is stored. The
minimum and maximum input value during each cycle is also
stored.
Automatic tuning now goes about the task of calculating the
PID/Floating module scan rate, proportional band, mode of oper-
ation (i.e., reverse or direct), and Integral (Ti ) and Derivative (Td )
coefficients. These parameters are determined as follows:
The mode of operation is determined by noting how the
input reacts to a change in the output (i.e., does it increase
when the output is increased?).
Module scan rate (Ts) is determined from the information
stored during the tuning process and is one-tenth (1/10) of the
average fundamental period of the process (Tpavg). In mathe-
matical terms:
T x + 1 T x + T x + 2 T x + 1 + ...
10T s = ------------------------------------------------------------------------------------- = T pavg
5
Note: You may wish to obtain reference material concerning the Ziegler-
Nichols approach for linear approximation which is available from
most libraries.
Adaptive Tuning
Once commissioned, adaptive tuning ensures that a process is
being controlled optimally by changing the proportional band,
integral, and derivative coefficients to best react to a process whose
environmental characteristics are subject to change.
The following paragraphs describe when adaptive tuning is
performed but do not address the theory behind adaptive tuning
nor its mathematical implementation. TACs implementation of
adaptive tuning is proprietary in nature and cannot be detailed.
Adaptive Tuning Parameters
There are four parameters associated with adaptive tuning:
ACP = adaptive control point
NB% = noise band percent
MO% = maximum overshoot percent
TD% = target damping percent
Adaptive Tuning Process
The first part of the process is to allow adaptive tuning to occur. It
may sound like a very simple question, but it may not be. Some of
the questions that have to be answered include:
NB
NB
Fundamental
Frequency NB
the noise band. If the noise band has been exceeded, adaptive
tuning can occur.
Now that the PID/Floating parameters are going to be adapted, the
maximum overshoot percent (MO%) parameter is used to deter-
mine what will be adapted. The maximum overshoot is a
percentage applied to the input range of the module (the difference
between the input high limit and the input low limit) to determine
which of the PID coefficients will be adapted. For example, if input
low limit = 10, input high limit = 30, and maximum overshoot
(MO%) = 10, then the range is 20 and the resulting maximum
overshoot is 10% of 20, or 2.
Note: The adaptation of the integral and derivative coefficients are func-
tions of time and the remaining PID parameter, target damping, and
are proprietary to TAC.
Max.
Overshoot NB
I,D Adapt
Max.
Overshoot NB
No Adapt
D1
D3
D2
Output
See Also: Direct Digital Control in TCON299, TAC I/NET Seven Operator
Guide
ASHRAE1 handbook titled HVAC Applications
1.
American Society of Heating, Refrigerating & Air-Conditioning Engineers, Inc.
12
48
Unitary Control
Caution: You may recall that you entered a minimum trip/close time for DO
and DC points when you first defined those points in the resident I/O
points editor. These times are honored only when the UCI issues a
command to the point (demand, time scheduling, temperature
control, or calculated point), but not when one of the UCs issues a
command. This includes the VAV-UC, AHU-UC, and HPMP-UC
editors described in this chapter.
You should consider increasing scan times of the parent point
(through the resident I/O points editor), widening differentials, as
well as using activation delays or interstage delays (through the UC-
specific editor) provided in the UC to prevent damage to mechanical
equipment.
UC Resident Programming
The following editors reside in the UC:
Station parameters
Control commands
Conversion coefficients
Resident I/O points
Unitary control
VAV-UC extensions
AHU-UC extensions
HPMP-UC extensions
UC-PID extensions
UC-FLT extensions
General
The first discrete output address in the UC (typically point address
LLSSPP00) is referred to as the parent point of the controller. The
desired UC extension (VAV, AHU, or HPMP) is appended to the
point as an extension through the Unitary Controller editor. This
editor contains the specific parameters for the type of UC extension
you selected.
A time scheduling extension is typically appended to the UC parent
point. When the schedule commands the UC parent point on (1),
the UC switches to its normal setpoints. When the schedule
commands the UC parent point off (0), the UC switches to its
setup/setback setpoints. You can also append a temperature control
extension to the UC parent point if you want optimized start or
stop.
UC Damper/Valve Control
The VAV, AHU, and HPMP UCs can provide direct digital control
for accurate control of damper and valve actuators typically used in
VAV boxes, packaged roof-top air handling units, small built up air
handling units, and packaged heat pump units. You may use either
a PID extension with a PWM control output, or a FLT extension
with dual pulsed outputs for bidirectional electric damper/valve
operators.
The DO-PID and DO-FLT extensions are used when you have a
specific application that requires modulated control and the
output to be 0 (closed) when the DO-PID or DO-FLT parent point
is commanded off. A typical application is AHU or HPMP mixing
damper control. The setpoint of a DO-PID or DO-FLT can only be
a constant.
DO-PID and DO-FLT extensions are very similar to the PID and
Floating modules used in all other TAC I/NET controllers. Refer to
Chapter 11, Direct Digital Control, for a complete discussion of all
DDC modules.
AO-PID and AO-FLT extensions are similar to DO-PID and DO-
FLT extensions. The major difference is that the AO extensions are
appended to an AO point, whereas the DO extensions are
appended to a DO point. This difference lets you use a varying
setpoint. The setpoint used by the AO-PID or AO-FLT is the
current value of the AO parent point itself. (Remember that the
setpoint for a DO-PID or DO-FLT is a constant). Unlike the DO
extensions, the output of an AO extension will not automatically
drive the output to 0 if the parent point is off (0).
Pulse Width Modulation, or PWM, is a technique used to direct the
output of a PID extension to an external AO point address. The UC
automatically ranges the output in percent full scale and converts
the output to a timed duration pulse.
As an example, assume an AO point is designated as the control
output for the mixed air damper and identified as the output target
of the DO-PID extension. The conversion coefficient pair is m =
0.03922, and b = 0.39222. These coefficients produce a full range
ATC
VAV-UC Schedule
Parent Point
Internal DO
Internal DO
SSPP01
SSPP00 ATS
Schedule ***
Central Plant
Heat
Option
* *
Internal DI
OR
SSPP02
Fan
* External DO
SSPP05 Output Point
Internal DO **
Economy SSPP01 Stage 1 Heat
Override
Option
* External DO
SSPP04 Output Point
Internal DI OR
SSPP05
External DO Stage 2 Heat
* SSPP03 Output Point
Setpoint Adj
Potentiometer External AI
Option SSPP03 External DO Stage 3 Heat
OR SSPP02 Output Point
Override
Pushbutton External DI VAV-UC
SSPP04
Option Extension
Internal DO Central Plant
SSPP01 Temperature Heat
Indicator
Setpoint
Override
Point
External DO
OR
SSPP02
Output
AO-FLT Parent Point
CFM Setpoint
Temperature
to CFM Convertor
Internal AO
Sp
AO-FLT SSPP07
Extension
External AI CFM Airflow
Outputs Pv SSPP06 Sensor
Inc Dec
ATC
VAV-UC Schedule
Parent Point
Internal DO
Internal DO
SSPP01
SSPP00 ATS
Schedule ***
Central Plant
Heat
Option
* *
Internal DI
OR
SSPP02
Fan
* External DO
SSPP05 Output Point
Internal DO **
Economy SSPP01 Stage 1 Heat
Override
Option
* External DO
SSPP04 Output Point
Internal DI OR
SSPP05
External DO Stage 2 Heat
* SSPP03 Output Point
Setpoint Adj
Potentiometer External AI
Option SSPP03 External DO Stage 3 Heat
OR SSPP02 Output Point
Override
Pushbutton External DI VAV-UC
SSPP04
Option Extension
Central Plant
Internal DO Heat
SSPP01 Temperature
Indicator
Setpoint
Override
Point
External DO
OR
SSPP02
Damper Override
Interlock
Mode
Outputs Pv
Inc Dec
Temperature Hardware
Controller Output Bit 6 Increase and Decrease
Database Point Output Signals to
Address not Required Bi-Directional
Hardware Damper Actuator
Output Bit 7
78
76
H1 OFF
74
1/2 Differential
Normal H2 OFF
Heating 72
Setpoint
1/2 Differential H2
Offset from
70 Setpoint H3
H1 ON Offset from
Setpoint
H3 OFF
68
H2 ON
66
H3 ON
64
62
NOTES: 1. Diagram above represents the control actions which would occur if the
Controller was set up with the following parameters:
Heating Setpoint = 72 Degrees
Differential = 4 Degrees
Heat 2 Offset = 4 Degrees
Heat 3 Offset = 6 Degrees
If the central air supply system provides warm air during the
heating season, the VAV-UC will modulate the CFM air flow to
maintain the desired space temperature. When operating in the
central plant heat mode, the output of the VAV control strategy is
set to reverse acting.
AHU Control
Refer to Figure 12-4 for a block diagram of the AHU function.
Refer to Figure 12-5 for an example of AHU-UC cooling/heating
staging.
If the space temperature falls below the active setpoint minus one-
half the differential, the AHU-UC turns on the fan and the first
stage of heat. If there is more than one stage of heat, the second and
third stages of heat come on after the fan and first stage of heat,
provided their individual temperature offsets have been honored.
As the temperature then begins to rise, the stages of heat turn off in
the opposite order that they were turned on; last on is first off.
When the temperature reaches the active setpoint plus one-half the
differential, the first stage of heat and the fan are turned off.
If the space temperature rises above the active setpoint plus one-
half the differential, the AHU-UC turns on the fan and the first
stage of cooling. If there is more than one stage of cooling, the
second and third stages of cooling come on after the fan and first
stage of cooling, provided their individual temperature offsets and
interstage delays have been honored. As the temperature then
begins to fall, the stages of cooling turn off in the opposite order
AHU-UC ATC
Parent Point Extension
Internal DO
SSPP00 ATS
Schedule ***
*
Space Temp External AI
Sensor SSPP00
External DO Fan Output
See Note Point
Economy
Internal DO
See Note ** External DO Stage 1 Cooling
Override
Option
* I O See Note Output Point
Internal DI
See Note
OR n u
External DO Stage 2 Cooling
p t
* u p
See Note Output Point
Setpoint Adjustment
Potentiometer External AI t u External DO Stage 3 Cooling
SSPP03 t See Note Output Point
Option s
s Stage 1 Heating
External DO
See Note Output Point
Override
Pushbutton
External DI
See Note
AHU-UC
Option
Extension External DO Stage 2 Heating
Output Point
See Note
Internal DO
See Note Damper
Indicator External DO Stage 3 Heating
Override Control
See Note Output Point
Point
External DO
OR
See Note
Internal DO Internal DO
See Note OR See Note
Extension Extension
External AI External AI
See Note Pv Pv See Note
Outputs
Database
Point Address
Note: The only "fixed" or reserved addresses in the AHU-UC are: External AI SSPP00 (Space Not Required
Temperature) and External AI SSPP03 (Setpoint Adjustment) when the CSI Model LTS80U
Sensor are used. All other input addresses or output addresses are NOT reserved and can
be used for any external field device up to the maximum point count of the controller.
The AHU-UC Controller only has eight input addresses and eight output addresses
This drawing is intended to show all the functions of the Editor and therefore more than
eight output points are shown. (ONLY EIGHT ARE AVAILABLE)
80
78
C3 ON
76
C2 ON
C3
Offset from
C2 C3 OFF Setpoint
74 Offset from
C1 ON
Setpoint
Normal 1/ Differential
Cooling 72 2
Setpoint 1/ Differential C2 OFF
2
C1 OFF
70
H1 OFF
Normal H2 OFF
1/ Differential
Heating 68 2
Setpoint 1/ Differential
2 H2
Offset from
H1 ON H3
66 Setpoint
Offset from
Setpoint
H3 OFF
64
H2 ON
62
Interstage Interstage H3 ON
Delay Delay
60
NOTES: 1. Diagram above represents the control actions which would occur if the
Controller was set up with the following parameters:
Cooling Setpoint = 72 Degrees
Differential = 2 Degree
Cool 2 Offset = 3 Degrees
Cool 3 Offset = 5 Degrees
Heating Setpoint = 68 Degrees
Differential = 2 Degrees
Heat 2 Offset = 4 Degrees
Heat 3 Offset = 6 Degrees
that they were turned on; last on is first off. When the temperature
reaches the active setpoint minus one-half the differential, the first
stage of cooling and the fan are turned off.
HPMP-UC ATC
Parent Point Extension
Internal DO
SSPP00 ATS
Schedule ***
* Fan Output
External DO
See Note Point
Space Temp External AI
Sensor SSPP00
** External DO
Reversing
Valve Output
See Note Point
Internal DO
Economy See Note
External DO Compressor 1
Override
Option
* I O See Note Output Point
Internal DI
See Note
OR n u
External DO Compressor 2
p t
* u p
See Note Output Point
Setpoint Adjustment
Potentiometer External AI t u External DO Compressor 3
SSPP03 t See Note Output Point
Option s
s Heat Strip 1
External DO
See Note Output Point
Override
Pushbutton
External DI
See Note
HPMP-UC
Option
Extension External DO Heat Strip 2
Output Point
See Note
Internal DO
See Note Damper
Indicator External DO Heat Strip 3
Control
Override See Note Output Point
Point
External DO
OR
See Note
Internal DO Internal DO
See Note OR See Note
Extension Extension
External AI External AI
See Note Pv Pv See Note
Outputs
Database
Point Address
Not Required
Note: The only "fixed" or reserved addresses in the AHU-UC are: External AI SSPP00 (Space
Temperature) and External AI SSPP03 (Setpoint Adjustment) when the CSI Model LTS80U
Sensor are used. All other input addresses or output addresses are NOT reserved and can
be used for any external field device up to the maximum point count of the controller.
The AHU-UC Controller only has eight input addresses and eight output addresses
This drawing is intended to show all the functions of the Editor and therefore more than
eight output points are shown. (ONLY EIGHT ARE AVAILABLE)
C3 ON
78
C2 ON
C3
Offset
C2 C3 OFF
76
C1 ON Offset
REV VALVE
Normal OFF 1/ Diff.
Cooling 74 2
Setpoint 1/ Diff. C2 OFF
2
C1 OFF
72
C1 OFF
Normal
1/ Diff. C2 OFF
Heating 70 2
Setpoint 1/ Diff.
REV VALVE 2 C2
ON Offset
C1 ON C3
68
C3 OFF Offset
C2 ON H1
66
H1 OFF Offset
H2
Offset
C3 ON H3
64
H2 OFF Offset
NOTES: 1. Diagram above represents the control actions which would occur if the H3 ON
Controller was set up with the following parameters:
Cooling Setpoint = 74 Degrees Compressor 2 Offset = 3 Degrees
Differential = 2 Degrees Compressor 3 Offset = 5 Degrees
Heating Setpoint = 70 Degrees Heat Strip 1 Offset = 7 Degrees
Differential = 2 Degrees Heat Strip 2 Offset = 8 Degrees
Heat Strip 3 Offset = 9 Degrees
2. The Reversing Valve is turned OFF when the temperature rises above the Cooling Setpoint.
The Reversing Valve is turned ON when the temperature falls below the Heating Setpoint.
3. In the Cooling Mode, Compressor 1 is turned ON at Cooling Setpoint plus 1/2 Differential.
In the Cooling Mode, Compressor 1 is turned OFF at Cooling Setpoint minus 1/2 Differential.
In the Heating Mode, Compressor 1 is turned ON at Heating Setpoint minus 1/2 Differential.
In the Heating Mode, Compressor 1 is turned OFF at Heating Setpoint plus 1/2 Differential.
6. In the Heating Mode, Heat Strip 1 is turned ON at Heating Setpoint minus H1 Offset.
In the Heating Mode, Heat Strip 1 is turned OFF at Heating Setpoint minus C3 Offset.
7. In the Heating Mode, Heat Strip 2 is turned ON at Heating Setpoint minus H2 Offset.
In the Heating Mode, Heat Strip 2 is turned OFF at Heating Setpoint minus H1 Offset.
8. In the Heating Mode, Heat Strip 3 is turned ON at Heating Setpoint minus H3 Offset.
In the Heating Mode, Heat Strip 3 is turned OFF at Heating Setpoint minus H2 Offset.
Note: If the error in reading is negative, the offset counts entered should be
positive. If the error in reading is positive, negative offset counts
should be entered.
Remote Override
You may wish to allow a tenant who wants heating or cooling after
normal operating hours to turn on his individual VAV, AHU, or
heat pump. To do this you must install a normally open momen-
tary (or maintained) push-button in the area served by the VAV
Note: Only two lookup tables (1 and 2) have been implemented. Lookup
Table #3 is for future use.
Pickup
Fan Probes
Damper
Duct
UC UC/UCI UC/UCI
Low Velocity A/D Non-Linear Conversion
Voltage Counts Eng. Units CFM Point
High Pressure Converter Look-Up Coefficients
Transducer 2.7323.332 (8-Bit) (0 255) Table (0 13000) Value
y=m x+b
VAV-UC
(Model 7211/7212)
2.7623.332
VAV-UCII
(Model 7261/7262)
y=m x+b
Whe re y = CFM
Whe re x = Equipment units from non-linear look-up table
square footage of duct
m = K factor
100
b=0
Where "square footage of duct" = Length Width (Box)
or
R adius2 (Circle)
K factor =VAV box airflow constant
For example, assume you wish to sense CFM using a Titus Velocity
Pressure Probe and Hoffman Velocity Pressure transducer in an 8-
inch round duct. In the VAV-UC resident database editor, you must
use the flow equation described above and Non-Linear Lookup
Table number 1. The conversion coefficients are:
b=0
m = (2304 0.3490)/100 = 8.04096
where 2304 equals the Titus Airflow Constant and 0.3490 equals
the duct square footage calculated as follows:
duct square footage = R2
(where R = radius of duct in feet)
duct square footage = 3.1415 0.3332
duct square footage = 0.3490
Note: The editor will allow either the AO-PID address or the AO-FLT
address to be used as the target for the heating/cooling interlock or the
damper override. Insure that the heating/cooling interlock is applied
to the AO-PID address and the damper override is applied to the AO-
FLT address.
Note: Bit offset addresses 08 and 09 can only be used as internal or indirect
points on a UC defined with a type of Internal. These addresses
cannot be used when a UC type is defined as VAV, AHU, HPMP, or
General. If you are using the UC to UC copy function, bit offset
points 08 and 09 must not exist in the source UC during the copy
process. You may add bit offset points 08 and 09 (in an internal UC
through the resident I/O points editor after using the UC copy editor.
DDC modules are not available for use in UCs. However, you can
set up PID or Floating control in any of the unitary controllers.
This topic is described in detail later in this chapter.
Caution: When setting up any of the Unitary Controllers, it is vital that the
UC Parent Point (internal or external DO) use the following control
command pair:
STRT 1
STOP 0
Figures 12-1 (page 12-9) and 12-2 (page 12-10) show block
diagrams of typical VAV-UC editor setup. Figure 12-4 (page 12-14)
shows a block diagram of a typical AHU-UC editor setup.
Figure 12-6 (page 12-17) shows a block diagram of a typical
HPMP-UC Editor setup.
Setpoints
Each setpoint consists of a number between 0 and 127.5 for the
setpoint target and a number between 0 and 10 for the differential.
You may use a 0.5 decimal entry for all setpoint targets and differ-
entials. If you enter a decimal value less than 0.5, the system drops
the decimal (e.g., 79.4 becomes 79). If you enter a decimal value
greater than 0.5, the system replaces the decimal with 0.5 (e.g., 79.9
becomes 79.5).
Cooling Setup
This setpoint limits the high temperature in the space conditioned
by the unit controlled by this UC when the space is unoccupied
(DO parent point is off; equal to 0). If the sensed temperature
exceeds the setpoint plus one-half the differential during this time,
the UC starts the fan and executes the control necessary to cool the
space.
Cooling Economy
Use this setpoint in conjunction with a DI/DO point (economy
override); e.g., an external personnel sensor or internal point
controlled by demand control, to raise the setpoint if the space is
unoccupied during normal hours (DO parent point is on; equal to
1 and economy override equal to 1). Occupancy is determined
through use of the economy override function described below.
When the personnel sensor again senses occupancy (economy
override=0) or demand control restores the economy override
point, the setpoint reverts to normal cooling setpoint.
Cooling Normal
This setpoint is used when the unit is on (parent point = 1) and the
sensed space temperature is higher than the setpoint plus one-half
the differential.
Heating Normal
This setpoint is used when the DO parent point is on (equal to 1)
and the sensed space temperature is lower than the setpoint minus
one-half the differential.
Heating Economy
This setpoint may be used with a DI/DO point (economy over-
ride); e.g, an external personnel sensor, or internal point controlled
by demand control, to lower the setpoint if the space is unoccupied
during normal hours (DO parent point is off; equal to 0 and
economy override equal to 1). Occupancy is determined by the
economy override function, described below. When the personnel
sensor again senses occupancy, or demand control restores the
economy override point, the setpoint reverts to normal heating
setpoint.
Heating Setback
This setpoint limits the low temperature in the space conditioned
by the unit controlled by this UC when the space is unoccupied
(DO parent point is off; equal to 0). If the sensed temperature
drops below the setpoint less one-half the differential during this
time, the UC starts the fan and executes the control necessary to
heat the space.
Note: If any of the above setpoints are not used, do not change the default
setpoint and differential. Ensure that the heating setpoint plus differ-
ential does not overlap the cooling setpoint plus differential, or be
higher than the cooling setpoint. The reverse is true of the cooling
setpoint.
Only one of six setpoints above is ever in effect at any time
(depending on current time and space temperature values).
The changeover from cooling setpoint to heating setpoint occurs when
the space temperature drops below the heating setpoint plus half the
differential. The setpoint changes to the cooling setpoint when the
space temperature rises above the cooling setpoint plus half the differ-
ential.
Overrides
There are several separate override options available in the UC type
you selected.
Setpoint Adjustment
This parameter is a point address or name. When a CSI space
temperature sensor with a setpoint adjustment knob, or a CSI
space temperature sensor with a setpoint adjustment knob and an
override push-button is used, enter the default AI address
(LLSSPP03) here. Refer to Remote Setpoint Adjustment on page
12-20 for the setup of this point.
Range
This parameter is a number between 0 and 10. When a CSI sensor
with a setpoint adjustment knob is used, the value entered here
limits the setpoint adjustment to plus or minus the value entered.
If you enter a five, the full rotation of the knob will never change
the setpoint by more than ten degrees (five degrees up or down).
Refer to Remote Setpoint Adjustment on page 12-20 for the use
of this editor entry.
Timed Override
This parameter is a point address or name. When a CSI space
temperature sensor with setpoint adjustment and override push-
button is used, the push-button can be hardwired back to any avail-
able DI input point. The UC senses the activation of this DI point
(open to close, 0 to 1) and initiates a timed override for the dura-
tion you define. You may also use a maintained contact closure
device or a spring wound timer instead of a pushbutton.
Note: The override period is initiated when the spring-wound timer contact
first closes. The duration of the override honors the timed override
editor entry regardless of the external timer duration.
The timed override function is only operative during unoccupied
hours, i.e., when the UC parent point has been turned off (0) by an
ATS schedule. An ATS schedule on the parent point is required to
allow the timed override to work properly.
Note: You must observe the polarity of this point! A 1 always causes the UC
to switch to the economy setpoint when the parent point is ON (1).
You may also use the economy override function to shift the
setpoint in response to a Demand Program shed command. If
you select this option you might use LLSSPP01 DO (internal),
as the demand load address. The response is the same as that
described for the personnel sensor. Once again you must
observe the polarity. A control command of 1 must be issued
to the internal DO point to cause the UC to shift from normal
to economy setpoints.
Damper Override (VAV only)
This parameter is a point name or AO point address (typically
address SSPP07 AO). Use the damper override function if you want
to have the VAV airflow control damper travel to its fully closed (0)
position when the VAV parent point is off (0) and the space temper-
ature is within the setup/setback targets.
Note: To use this function, the low limit of the AO point designated as the
floating parent point (typically SSPP07 AO) must be 0 and the input
low limit of the AO-floating extension must be 0. Refer to Figures
12-1 (page 12-9) and 12-2 (page 12-10).
Note: This feature only works when the AHU-UC or HPMP-UC parent
point is commanded on (1) by the time scheduling program, not
when the fan output point turns on and off as a result of automatic
fan control by the AHU-UC or HPMP-UC.
Space Temperature
This parameter is the hardware address of the space temperature
sensor. If you are using a CSI LTS80U space sensor, enter the default
address LLSSPP00 AI (external). You may use another address if
you use another sensor. To use one sensor to control several UCs
you must make a calculation, in the appropriate UCI, and reflect
the value of the common sensor to each UC with the appropriate
point (PP) address for each UC.
Central Plant Heat (VAV only)
The VAV-UC can change its control response from direct acting to
reverse acting if the central air supply system is subject to seasonal
supply air temperature changeover. This means that during the
cooling season, the supply air system carries cool air, and during
the heating season, the supply air system carries warm air. The UC
must change from direct acting to reverse acting; i.e., it must open
its air supply damper on a call for heating and close it when the
space is overheated. To accomplish this, it must know when the
supply air has changed from cool to warm. This changeover notifi-
cation is accomplished by using a DI or DO point at the address
named Central Plant Heat. When this point state is 1, the AO-PID
attached to LLSS06 AO (refer to Figure 12-1 on page 12-9) switches
to reverse acting. When the state is 0 (or is not populated in the
VAV extension editor), the AO-PID extension functions as direct
acting.
Temperature Setpoint (VAV only)
This parameter is an AO PID or Floating parent point assigned as
the space temperature setpoint. To reset the CFM (cubic feet per
minute) setpoint by the temperature error, enter the AO PID
parent point address (e.g., LLSSPP06 AO; see Figure 12-1 on page
12-9). If you wish to bypass the CFM control and control the
damper position directly from the temperature error, enter the AO
Floating parent point address (e.g., LLSSPP07 AO; see Figure 12-2
on page 12-10).
Fan
This is the external DO point address that controls the fan
(LLSSPP05 DO).
PID Parameters
The PID parameters described below are used on DO PID and AO
PID extensions:
Setpoint (DO-PID only)
This parameter is a value in degrees. This is the target temperature
to be maintained by the extension. This value is a constant.
Input (Process Variable)
The AI address of the sensor measuring the process. This is typi-
cally a duct/space/fluid temperature sensor.
Input Filter
This parameter is a number between 0 and 5. This option lets you
average up to five previous sequential input samples with the
current sample to reduce the impact of rapidly changing input
values. An entry of zero means filtering is not being used.
The mode you select determines what happens when the input rises
higher or falls lower than the setpoint. Direct acting PID extensions
increase their output if the input (process variable) rises above the
module setpoint and decrease their output if the input (process
variable) falls below the setpoint. Reverse acting PID extensions act
in the opposite manner.
FLT Parameters
Refer to Chapter 11, Direct Digital Control, for a detailed descrip-
tion of these parameters. The FLT extension uses the following
parameters:
Setpoint (DO-FLT only)
This parameter is a value in degrees. This is the target temperature
to be maintained by the extension. This value is a constant.
Input (Process Variable)
The AI address of the sensor measuring the process. This is typi-
cally a duct/space/water temperature sensor.
Input Filter
This parameter is a number between 0 and 5. This option lets you
average up to five previous sequential input samples with the
current sample to reduce the impact of rapidly changing input
values. A value of zero indicates that filtering is not being
performed.
Input Low Limit
This parameter is a value below which the extension declares the
setpoint no longer valid. At this value, the floating extension ceases
to output increase or decrease pulses.
Input High Limit
This parameter is a value above which the extension declares the
setpoint no longer valid. At this value, the floating extension ceases
to output increase or decrease pulses.
Output (Increase)
This parameter is a number between 0 and 7. This is the bit offset
address of the increase hardware output. You do not need to specif-
ically define a point address for this purpose, you need only enter
the value of the hardware bit to which the output is wired. The bit
offsets can still be defined as internal AO or DO points for another
purpose if desired.
Output (Decrease)
This parameter is a number between 0 and 7. This is the bit offset
of the decrease hardware output. Like the increase described above,
enter the value of the hardware bit that corresponds to the physical
location of the decrease pulse.
Throttling Range
This parameter is a number between 0 and 255 seconds. This is the
number of seconds required for the bidirectional motor controlled
by the floating extension to transition from fully closed to fully
open (or from fully open to fully closed).
Turn-Around Time
This parameter is a value, in seconds. This is the time required for
the motor to stop and reverse direction. Typically you will leave this
field at the default (zero).
Proportional Band
This parameter is a number between 0 and 1,000. This is the
percent of the input range (input high limit input low limit) that
the input value must change in order to drive the output from fully
open to fully closed.
Reset Interval
This parameter is a number between 0 and 3,600 seconds. The
default is zero seconds. Use this function to eliminate a persistent
error (called offset) that has remained constant from one
Floating sample to another. Without reset, this situation (offset)
results in undesirable static module output. This function defines
reset calculation constants used to modify the output of the
Floating extension.
Rate Interval
This parameter is a number between 0 and 3,600 seconds. The
default is zero. This is the time between calculations of the rate
portion of the FLT algorithm. Use this function to account for large
input changes by comparing the direction and magnitude of the
error between samples and correcting the output accordingly.
Mode
Select Direct or Reverse. The default is Direct. This parameter
defines the response of the FLT extension. If you choose direct
acting, the FLT increase output pulses as the process variable rises.
If you choose reverse acting, the FLT increase output pulses as the
process variable falls. This function must be used to fit the response
of the FLT extension to the end device controlling the process.
The mode you select determines what happens when the input rises
higher or falls lower than the setpoint. Direct acting FLT extensions
pulse the increase output if the input rises above the setpoint and
pulse the decrease output if the input falls below the setpoint.
Reverse acting FLT extensions act in the opposite manner.
Alarm Inhibit
Time Scheduling
Special Days
Temperature Control
Demand Control
UC-PID Extensions (AO and DO)
UC-FLT Extensions (AO and DO)
Trend Sampling
Trend Plot
13
12
Micro Regulator Control
An asterisk (*) at the end of the Type column indicates that the
MRI, MCI, or I/SITE LAN cannot establish communication with
the MR. The asterisk disappears when successful communication is
established.
Note: Except for the MR160, bit offset addresses that are not used by the
MR may be used by the MRI/MCI as internal or indirect points. The
MR160 has no output point capability. Therefore, for this Micro
Regulator type, output point addresses may not be used as internal or
indirect points by the MRI/MCI.
Note: The Minimum Trip and Minimum Close parameters are not used for
MR output commands. The editor lets you enter a value in these
fields; however, this information is not downloaded to the MR.
MR Parameters
This option only appears when you are connected to a 7792 MRI,
7793 MCI, or 7798 I/SITE LAN. These options let you define the
hardware-specific parameters for each MR on the subLAN.
Note: These parameters are not available with the MR160. Although this
editor can be accessed when connected to an MR160, attempts to
enter data into any of the fields will result in an MCU mem over-
flow error message.
Note: The parameters in this edit screen are used by the I/STAT or M/STAT
(an intelligent thermostat connected to the MR). The I/STAT or
M/STAT controls and monitors points and devices connected to the
MR.
Entry Fields
Table 13-1 lists and describes the fields available for configuring an
I/STAT or M/STAT for the Micro Regulator.
Field Description
The point address or name of the point to be used as the master device control point
Master Device is entered here. This point is either a DO or DC point. The Interval field allows you
Control to specify the time from 0 to 255 minutes that the interval timer will be turned on
when this point is activated through the On/Off button on the I/STAT.
This address and point type defines the point that is controlled on or off when you
Call Address
press the I/STATs Call button. This point may be a DO or DC point.
The I/STAT and M/STAT use two inactivity timeouts to exit from the Service function
or return to the Home LED display when in the normal mode. The timer starts
Inactivity
counting down from the time the last button is pressed. For both the Escape from
Timeouts
Service and Return to Home LED timeout intervals enter a duration of 0 255
seconds.
The I/STAT or M/STAT has built in security in the form of a three-digit numeric
password. The password restricts access to the Service function on the I/STAT or
Password
M/STAT (the ability to make calibration, point, and parameter changes through the
Digits
I/STAT or M/STAT). Enter the three-digit numeric password for the I/STAT or
M/STAT in this field.
LED Functions
There are four LEDs on the I/STAT or M/STAT. Any of the four
LEDs may be designated as the Home LED. Using the select keys,
each of the four point addresses associated with the LEDs may be
selected for viewing. The I/STAT or M/STAT will return the display
to the selected Home LED after the Return to Home LED inac-
tivity timeout expires.
LED 1 allows you to enter a master setpoint address as the Base
address and a local setpoint address as the Adjust address. Both the
Base address and the Adjust address must be local to the same MR
(they must have the same PP portion defined in their address). This
allows you to locally make changes to a common system setpoint
from the I/STAT or M/STAT using the Change +/ keys and display
the newly adjusted setpoint value at the I/STAT or M/STAT. The
displayed value is a summation of the Base (common) address
value and the Adjust (local) address value.
Note: Without a Base address defined, only the value of the Adjust address
will display through the I/STAT or M/STAT. If the Adjust address is
not defined, then no value will display through the I/STAT or
M/STAT.
Hardware Coefficients
These conversion parameters set the FM (factory slope) and FB
(factory offset) conversion coefficients in the MR. The m value can
vary between 0 and 1.9997, and the b value can vary between 127
and 127. These parameters are primarily used by TAC for factory-
made adjustments. The end-user should avoid altering these hard-
ware coefficient settings.
The Span field offers a normal span and narrow span. The normal
span allows the full range of the 05 VDC or 010 VDC to be used.
The narrow span allows a 24 VDC range to be used on 05VDC
inputs, and a 48 VDC range to be used on 010 VDC inputs.
Lookup Tables
MR88, MR632, MR160, and MR88R Lookup Tables
Micro Regulator models MR88, MR632, MR160, and MR88R
provide four lookup tables to accurately translate the non-linear
characteristics of thermistors. These are designated LUT #1
Normal, LUT #1 Narrow, LUT #2 Normal, and LUT #2 Narrow.
Low High
The output from the lookup table is used with the user-defined m
and b conversion coefficients to create the engineering unit value.
The typical m and b coefficients are as follows:
For engineering units of C: m = 0.0100 b = 100
For engineering units of F: m = 0.0180 b = 148
When connecting a 10 K ohm thermistor or I/STAT to the space
sensor input on an MR, specify the database point to use Lookup
Table 1. Table number 1 accounts for an elevated self-heating error
that is a function of the I/STAT communication interface. A sepa-
rate lookup table, defined as Table number 2, is provided in the
MR55X firmware to support accommodation of thermistors on the
other four general purpose inputs. Table number 3 is used only to
translate the characteristics of the on-board CFM velocity sensor.
Note: Only Normal lookup tables 1 and 2 are available in the MR55.
Narrow lookup tables are not available.
Standalone ATS
Normal ATS functions are supported in the MCI, MRI, and I/SITE
LAN. Standalone ATS is intended to be the fall-back solution for
ATS scheduling if there is a break in the MR subLAN communica-
tion.
The Standalone ATS is an MR-resident ATS schedule programmed
into the MRs. Standalone ATS allows a single start and stop time for
each day of the week, and controls the point designated as the
master device control point in the MR parameters editor.
Note: MR-resident DDC is not available with the MR160. Although this
editor can be accessed when connected to an MR160, attempts to
enter a DDC module will result in a repetitive MCU mem overflow
error message.
Note: MR-resident DDC modules only reside in the MR (not in the MCI,
MRI, or I/SITE LAN. Therefore, these DDC modules are not avail-
able for use in any MR tagged as Internal in the MCU configuration
editor.
The lines that interconnect the DDC modules are numbered so that
the line number always corresponds to the DDC module number
that outputs to the line.
To preserve MR memory, the PV input to the PID, Floating, and
Two-pos modules, the primary and secondary inputs to the Reset
module, and the coil input to the Relay module cannot be defined
as Constant. Instead, these inputs are selectable as Line or
Point. For the same reason, the Floating (FLT) module can only
be defined as Point. Refer to DDC Modules in Chapter 11,
Direct Digital Control, for descriptions of each DDC module.
Note: In a 7792 MRI, 7793 MCI, or 7798 I/SITE LAN, DC/DM points
should only be controlled by 7792/3/8 resident programs. This
includes the calculations, ATS, temperature control, and demand
control editors. MR-resident DDC should not be used to control
DC/DM points.
Calculation Module
This is a new module that exists only in the MR controllers. The
Calculation module is edited similarly to the existing DCU calcu-
lated point in the TAC I/NET Seven program. The module also
operates similarly with some exceptions. These exceptions and a
description of the Calculation module are provided in Chapter 11,
Direct Digital Control.
MR-to-MR Copy
This function copies the data in one MR to another MR. The data
copied using this function consists of resident I/O point data,
extensions, and MR-resident DDC modules. The MR-to-MR copy
function does not copy any of the MR parameters (hardware coef-
ficients, standalone ATS, or I/STAT parameters).
MR-Resident Programming
The following editors reside in both the MR and the MRI, MCI, or
I/SITE LAN controller:
Station parameters
Control commands
Conversion coefficients
Resident I/O points
MR-resident DDC modules
14
12
Application Specific Controllers
Note: The MCI must contain the resident point record for the data to
display properly. Refer to Updating the Interface Controller on
page 14-7 for the procedure of equalizing the MCI with the ASC.
System Status
The following system status parameters appear on the display
screen:
Space Temperature
This point displays the current (sensed) value of the space temper-
ature, the primary input to the controller.
Active Setpoint
If the SPd parameter is set to actual, then depending on the space
temperature (described above), the active setpoint will be set to one
of two values: either the active cooling setpoint or the active heating
setpoint. If the space temperature is closer to the active cooling
setpoint, then that value becomes the active setpoint. If the space
temperature is closer to the active heating setpoint, then that value
becomes the active setpoint.
If the SPd parameter is set to average, then the active setpoint is
the midpoint between the active cooling and heating setpoints.
Loading
This point displays the load currently being placed on the
controller. The value of this parameter is determined as follows:
Cooling: 0 to +100 for 0 to 100% cooling load as the tempera-
ture rises across Cb.
Heating: 0 to 100 for 0 to 100% heating load as the tempera-
ture falls across Hb.
Setpoint Parameters
The following setpoints appear on the display:
Active Cooling Setpoint
This setpoint displays one of the following three values:
Occupied cooling setpoint when demand is Off as adjusted by
the Stat Offset adjustment
Demand setup setpoint when demand is On during occu-
pancy
Setup cooling setpoint when unoccupied.
Active Heating Setpoint
This setpoint displays one of the following three values:
Occupied heating setpoint when demand is Off as adjusted by
the Stat Offset adjustment
Demand setback setpoint when demand is On during occu-
pancy
Setback heating setpoint when unoccupied.
Stat Offset Adjustment
This point displays the current offset adjustment from the I/STAT
or S/STAT as adjusted by the occupant across its range. (Its span
can be adjusted.)
System Setpoint
This point displays the single target setpoint defined from an MCI.
(The parameter SPo must be greater than 0.)
Damper Position
This point reflects the damper actuator, as a percentage, and ranges
from 0 to 100. Normally it is controlled by the VAV control
program, based on the air volume required to maintain the space
temperature. The point can also be controlled by an operator from
a host workstation, or by an event sequence in the connected MCI,
or further upstream PCU. In that case it would be necessary to put
the point in the Manual mode from the workstation, or issue the
control command with Lock from the event sequence, to prevent
the VAV control program from changing it back.
Airflow
This will display the current airflow reading.
Outputs
This section of the display data screen contains the status of the
ASC outputs as defined in the ASC parameters. Certain points will
be displayed as a percentage from 0% to 100% open. These points
can be defined as 2-position or modulating from the parameter
modification screen. Refer to the installation/reference guide for
your particular product.
Modifying Parameters
If you choose to accept the factory defaults for setpoints, bands,
configurations, etc., you do not need to change any ASC parame-
ters. If you do elect to modify parameters, you may use either the
I/STAT or M/STAT, or the ASC editor in the TAC I/NET Seven host.
Note: Names must be assigned to all ASCs being updated to the MCI.
All four sets of station parameters are also updated in the interface
controller to reflect the station parameters required by ASCs.
Station parameters previously defined by the operator are not over-
Caution: When deleting ASC point information from the interface controller,
you must ensure that the ASC is set to Internal in the MCU
Configuration editor. Failure to do so will result in the deletion of
points from the ASC.
If points in the ASC are not required to be viewed from the host,
you can delete the unnecessary point information from the MCI
database using the Resident I/O Points editor. This will allow the
host workstation to be updated faster when connecting to an MCI
whose database does not match the SAVE file stored at the host.
Use the following steps to delete ASC point information from the
interface controller:
1. Connect to the interface controller (MCI, MRI, or I/SITE
LAN).
2. Enter the MCU Configuration editor and toggle the appro-
priate ASCs to Internal. Failure to perform this step will result
in the actual deletion of points from the ASC during the next
step.
3. Enter the Resident I/O Points editor and delete the unneces-
sary ASC points from the interface controller.
4. Return to the MCU Configuration editor and toggle the
appropriate ASCs from Internal back to their correct
setting.
Order of Operations
The following sequence assumes the ASCs have been installed and
configured for operation from the I/STAT.
1. Enter the MCU configuration editor from the interface
controller (MCI, MRI, or I/SITE LAN). Toggle the ASCs on
the subLAN from Internal to ASC.
2. Assuming communication has been confirmed, enter the ASC
parameters editor. Use the modify option to define each ASC
name.
3. Once the names are defined, enter the MCI update editor. Use
this editor to upload all point records and station parameters
to the interface controller.
4. Perform a station save. Disconnect from the interface
controller and then re-connect. Use the DCU summary or
individual editors to view the database.
Note: The station save does not contain the ASC parameters.
Free Points
The ASC can be configured so that specific input and output points
are available for use by other MRI, MCU, or I/SITE LAN applica-
tions. In this case, sensors or dry contacts can be connected to free
input points, and output points can be connected to discrete actu-
ators or contactors in the same manner as in Micro Regulators
(MRs).
When a free point is to be used in another application, the points
parameters, and even its type, can be modified using the resident
I/O points editor.
Caution: The resident I/O points editor does not protect against modifications
of non-free points. Any modifications to non-free points, except for
point names which have no impact on the operation of the point, will
cause the ASC to work improperly.
15
8
7771 Industrial Controller Interface
Note: As with other controllers, you must enter the station address into the
ICI using a hand-held console (HHC). Please refer to the user guide
accompanying your ICI unit for the correct procedure.
Field Description
Note: The parameters you define here must agree with the parameters
defined in the MODBUS host. As described above, the ICI emulates a
PLC 584 so make sure the MODBUS host is configured to recognize
the ICI as such.
A DI or DA point monitors the state of a MODBUS coil and a GI point monitors the state
DI, GI, DA
of a set of coils through a force or preset control command from the MODBUS host.
These point types are always used as a pair. A DM point receives the state of a
MODBUS coil through a force or preset control command from the MODBUS host.
DM and DC
A DC point sends the state of a discrete output to a MODBUS input for the MODBUS
host to read.
The ICI sends the state of a TAC I/NET discrete output point or set of points (using a
DO, GO
GO point) to a MODBUS input for the MODBUS host to read.
An AI point receives the value of a MODBUS holding register (memory location)
through a force or preset control command from the MODBUS host. The data is
AI
sent as an integer value which is then converted to a digital state that TAC I/NET can
accept.
The ICI gives the value of the output to a MODBUS input register (memory location)
AO for the MODBUS host to read. The data is sent as an integer value and must be
converted for use by the MODBUS system.
This point accumulates pulses from the MODBUS coil and converts the pulses to
PI
engineering unit values. The ICI does not support it as an external point.
MODBUS Addresses
The MODBUS database uses an addressing system that differs from
the eight-digit system used in TAC I/NET. The MODBUS logical
addresses for a series of points runs from one to 9,999. However,
the connection between TAC I/NET and the MODBUS is limited to
255 points per ICI. A register is an AI memory location in a
MODBUS device. The MODBUS uses four point types and assigns
each type a different number. Each point type has a certain number
of addresses available to it as described below:
Type 0 registers 00001 to 00256
Type 1 registers 10001 to 10256
Type 3 registers 30001 to 30256
Type 4 registers 40001 to 40256
Holding Registers
These registers accept a number between 0 and 65,535 from the
host and may be used by the PLC to perform functions such as
modulation of a local process variable such as an AO point. The
MODBUS host controls and reads the holding register value. The
MODBUS protocol refers to these as Type 4 registers (40001 to
49999).
Direct mapping of the points between the MODBUS and the TAC
I/NET controller LAN establishes the numeric relationship as listed
in the table. The first digit of the MODBUS point can be 0, 1, 3, or
4, depending on the MODBUS point type it represents.
Point Class
All ICI I/NET points, except those defined as internal, connect with
a similar point type in the MODBUS system. All MODBUS points
should match a similar TAC I/NET external class point.
If you accidentally associate a MODBUS point with an internal
TAC I/NET point, the ICI returns an error message when the
MODBUS tries to query or command that point. This error
message appears in the EVENTS table or on a printer, but will not
appear on your screen.
Point Name
Each point in the ICI is assigned a unique 16-character name. This
name is the connection to the MODBUS address. An effective
method of naming your points is to type MB at the beginning of the
MODBUS point address, then the address, a space, and the
MODBUS point type: MB40129 Hold Reg.
Scan Interval
This is the number of seconds between each scan of the point you
are defining. The range is 1255 seconds. For most points the
default setting is the proper scan rate. The scan rate should not
exceed the physical response capability of the point it controls or
monitors. The scan rate of global points should also match the scan
rate of those points that use data from global points.
16
30
SevenTrends
Caution: The database server should not be shut down while TAC I/NET
Seven 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.)
Collecting Data
The operator workstation will collect and store a vast amount of
data if a few tasks are performed properly. You must:
Set the SevenTrends group and active mask positions to the
appropriate values and positions in the host configuration
editor for the host workstation.
Set the appropriate parameters in the functional editors and
the resident I/O editors in the DCUs.
The distribution group and mask must match at least one
active position in the host workstation.
The cell number must be greater than zero (0)
The priority must be other than None
Data Flow
All SevenTrends information is stored in the DCU, which routes
the data to an operator station. Before you begin, it is helpful to
understand how DCUs, Taps, and operator stations work together
to provide SevenTrends information.
Simple TAC I/NET Seven Configurations
The sequence of actions occurs as follows for an online host:
1. When a DCU is ready to send information to an operator
workstation, it sends an Upload or Sample data request to the
Tap (which is connected to the operator station), as shown in
Figure 16-1 (step #1).
DCU
Note: Only upload and sample data requests are buffered. The SevenTrends
data is not available to the host until the data is transferred from the
DCU/PCU/MRI/DPI/MCI. The host honors all pending upload and
sample data requests. In some cases, where lengthy communication
delays occur or if a host workstation has been powered off for long
periods of time, the host will honor multiple requests for the same
point, and as a result may duplicate data in SevenTrends tables. This
will occur if the workstation is turned off and the Tap is left on. To
avoid this situation, turn the Tap off whenever you turn the worksta-
tion off. Better yet, it is recommended that host workstations used for
storing SevenTrends data, and their associated Taps, be left on.
3
78032
DCU
Tap
1 2
78010 78022 The circled numbers indicate
Tap Tap the order in which upload or
sample data requests will be
stored. When the Tap's memory
is full, the next Tap in line
will begin storing requests.
Operator
Station
(offline)
sample data requests. If you tell the programs not to dial the oper-
ator station, upload or sample data requests are stored in the
78060/1 Tap. If this Tap becomes full, the DCUs start storing their
own upload requests.
Controller LAN
78050 78060
Tap Tap
DCU *
Host LAN
OR Controller LAN
78041 78061
Tap Tap
sample count, base time, and interval, you are in fact sending 100
messages to the Tap at the same time for it to come and get the data
from the controller where the trending is taking place. This can
overload the Taps buffer capacity, causing lost cell data. To avoid
this situation, you must stagger the base time so that fewer upload
request messages are sent to the Tap at any one time.
If you tell the DCU programs to dial an operator station (on a host
LAN) and the workstation is turned off, then the 78010 Tap buffers
the messages until it is full, followed by the 78050/1 Tap, and then
the 78060/1 Tap. When an online operator station receives an
upload or sample data request, the operator station gets the data for
that particular upload or sample data request as well as for any
other upload requests that might be stored in the 78060/1 Tap, as
shown in Figure 16-3 on page 16-7. The 78041 and 78061 Tap
follow the same procedure.
Typically, the Trend editor will have a Priority assignment and will
have to wait until the Tap receives a Critical message or the Tap
reaches its assigned Percent full threshold or Dial later limit. If
another message with a Critical priority assignment requests an
upload, the Priority request will piggyback on the transmission
to minimize dialing activity. This capability is especially important
if the call incurs long-distance charges.
Data Transfer Schedules
The different DCU editors send information to SevenTrends at
different times, as shown in Table 16-1.
Troubleshooting
If you are encountering difficulty in collecting SevenTrends data,
check the following items:
I/O Server is running.
The cell number in the host workstation is not zero (0).
The cell number in the DCU is not zero (0).
The trend type is appropriate to the data being collected.
The distribution group number is the same in the host and
DCU.
There is a match between the SevenTrends distribution group
and at least one active mask position in the host and DCU.
The priority in the DCU editor is set to at least Routine for a
direct connect system, or Critical for a dial system.
SevenTrends Types
SevenTrends allows you to define six different types of trend. The
trend type specifies the type of information that will be recorded.
Each trend type has specific fields associated with it. All samples
have date and time fields. Other trend fields vary depending on the
type of information collected. Table 16-2 provides descriptions of
the various trend types and shows the fields associated with each .
Defining Trends
Use the SevenTrends Definition function to define trends in a host
workstation. These are used to store data collected by the TAC
I/NET DCUs. Please take some time to consider what type of
SevenTrends reports you plan to generate and what information
you want to appear in those reports. There is no greater frustration
than to decide to generate a sophisticated report and then find that
the raw data has not been collected and stored.
You may find it helpful to document your system (recording trend
names, types, etc.). This will allow you to modify your reports as
your system grows and changes, and to troubleshoot your system if
anything goes wrong. You may wish to use the forms provided in
TCON157, TAC I/NET Seven Forms and Worksheets, for this
purpose.
Name
The unique name for this trend or cell, up to 30 characters. The
default name varies, as follows:
If you are connected to the controller and select the point
from a pane on the Point Selection editor, the default name is
in the form Point Name -- Trend Type.
If you are connected to the controller but manually enter the
point address in the fields at the bottom of the Point Selection
editor, the default name is in the form Point Address --
Trend Type.
If you are not connected to the controller when selecting a
point from the Point Selection editor, the default name is in
the form Point Address -- Trend Type.
If the SevenTrends definition is generated automatically from
a cell definition, the default name is in the form Point
Address -- Trend Type.
If you are defining a cell, the default name is in the form Cell
Number -- Trend Type.
If you do not enter a name, the default name will change automat-
ically with the point (or cell number) and trend type selection
when you are creating a new trend. You may change the name of a
trend or cell definition at any time without loss of data.
If you choose not to use the default names, give some thought to
your naming system before you begin. The use of combinations of
names and numbers is recommended; i.e., CHWS TEMP 1, CHWS
TEMP 2, and so on.
Type
The type of SevenTrends information you wish to collect from this
point. The selected type cannot be changed once a trend or cell is
defined.
Transient Duration
Use this field to discard data that has been in the system for the
specified number of days (145). For example, if you enter a 3, then
SevenTrends stores the last three days of information. On the
fourth day, the oldest stored information is replaced with informa-
tion collected on the fourth day.
Note: Transient duration is used to delete records only when the system is
due to perform an automatic transfer. Therefore, it is possible that
individual samples will be kept beyond their transient duration
period. If you change the transient duration for a cell or trend, the
new value will not be used until the next-scheduled automatic
transfer.
Note: If you are connected to the controller in any of the quadrants, the
default trend name will use the point name. Refer to SevenTrends
Parameters Editor on page 16-11 for a full discussion of default
names.
Link
The LL portion of the LLSSPPBB PT address for the desired point.
This field is automatically entered if you select a point from one of
the four quadrants.
Station
The SS portion of the LLSSPPBB PT address for the desired point.
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.
Note: For manually defined trends, the cell number in the DCU editor does
not need to match the cell number for the trend definition. The cell
number in the trend definition is the one that will appear on reports.
Caution: Exercise care when modifying cells. The system does not differentiate
between trends generated automatically from the cell definition and
trends defined manually. All trends with a matching trend type and
cell number will be affected.
DCU Editors
This section is a combination of two nearly-identical sections: one
from the front part of the book and one from a specific chapter.
Duplicate information was removed without showing editing
marks. The opening and closing paragraphs are combinations of
the respective paragraphs in each section.
There are certain editors in the DCU that can provide information
to SevenTrends. The data may be collected as often as once per
minute, or as seldom as once per day, depending on the editor used.
The following editors may provide information that SevenTrends
will use or that will affect the storage of SevenTrends data:
Trend Sampling
In each of these editors, you will find common fields that pertain to
SevenTrends data. Remember that the edit menu selections change
depending on the type of controller to which you are connected,
and your password level.
Note: The SevenTrends masking for the DCU points can be set from any
host workstation. SevenTrends masking for a host workstation can be
set only at that workstation.
Priority Description
SevenTrends Inquiry
The SevenTrends Data Inquiry function allows you to review or
modify existing data, and to backfill any missing data. All nonar-
chived samples may be edited, and missing data may be backfilled.
The SevenTrends Inquiry summary lists all defined trends, sorted
by name, whether or not there are data records for that trend. Select
a trend from the list to begin.
Earliest Time
The desired beginning time for the listed records. This sets only the
time on the designated earliest date. The default value is midnight
(00:00:00).
Note: The Line and Date fields are used for all trend types. The remaining
fields that may appear are listed in alphabetical order.
Binary State
The binary state (07) of the sampled point. (Discrete sample
trends.)
Consumption
The daily consumption for the sampled point. (Demand trends.)
Exclusive
The amount of energy (in kwh) expended in exclusive billable over-
ride functions at the sampled point. (Override trends.)
NonExclusive
The amount of energy (in kwh) expended in exclusive nonbillable
override functions at the sampled point. (Override trends.)
NonShared
The amount of energy (in kwh) expended in shared (nonexclusive)
nonbillable override functions at the sampled point. (Override
trends.)
NonTime
The total nonbillable override time, in minutes, accumulated at the
sampled point. (Override trends.)
Peak Time
The time the highest daily demand occurred at the sampled point.
(Demand trends.)
Peak Value
The highest daily demand at the sampled point. (Demand trends.)
Shared
The amount of energy (in kwh) expended in shared (nonexclusive)
billable override functions at the sampled point. (Override trends.)
State Text
The description for the binary state of the sampled point. (Discrete
sample trends.)
Note: The initial entry for this field comes from the state description table
for the controller. This field, like the other SevenTrends fields, may be
edited. The edited text may or may not match the descriptions
entered in the state table.
Time
The total billable override time, in minutes, accumulated at the
sampled point. (Override trends.)
Value
The value on the trended point at the time this sample was taken.
The information available in this field will vary depending on the
trend type. (Analog sample, consumption, runtime trends.)
Note: If you know the sample information, you can manually recreate a
record using the Add function.
Note: The 2GB limit is imposed by the Microsoft MSDE 2000 program
distributed with TAC I/NET Seven. Facilities using SQL Server 2000
instead of MDSE 2000 are not affected by this limit.
There are two ways to manage the SevenTrends data in TAC I/NET
Seven:
Transfer this moves SevenTrends samples to a separate
online database. Transferred samples are still available online
for viewing, editing, and report generation. Refer to Seven-
Trends Transfer Configuration Editor on page 16-25.
Archive this moves SevenTrends samples offline. Archived
samples are still available for report generation, but are no
longer available for viewing or editing from within TAC
I/NET Seven. Archived samples can be used for backup
purposes, as they can be moved or copied to any computer, or
onto removable media such as a floppy disk. Refer to
Archiving SevenTrends Data on page 16-28.
Sample Size
Each trend type uses a different number of bytes per sample when
stored on your hard drive. Use the information provided in
Table 16-4 to help you compute the amount of space you will be
using in your database file to store online (nonarchived) Seven-
Trends samples.
Bytes per
Trend Type
Sample
Analog Sample 73
Consumption 73
Demand 77
Discrete Sample 78
Override 89
Runtime 71
SevenTrends Messages
SevenTrends generates a message whenever a transfer or archive is
attempted, and also warns against loss of data when the databases
reach full capacity. The messages and their meanings are shown in
Table 16-5.
Message Description
Message Description
Distribution Parameters
The fields in this section specify the message routing for Seven-
Trends information. This refers only to messages generated by the
SevenTrends transfer and archive functions (see SevenTrends
Messages on page 16-24). This editor does not affect whether
SevenTrends samples are received at this workstation.
Distribution group Select the distribution group for transfer
messages.
Distribution mask Select the desired mask settings for transfer
messages.
Alarm priority The priority for sending information from this
extension editor. The options are None, Routine, Priority, and Crit-
ical. Refer to Priorities in Chapter 3, System Messages.
Primary Online Storage
This section allows you to select the method you wish to use to
determine which records should be transferred. After selecting the
method, enter the threshold level for that method.
In all cases, the older samples are transferred, leaving the most
recent samples in INETDB.
Note: The threshold level you enter defines the minimum samples that
should remain in INETDB; that is, it defines the samples that will
not be transferred.
Limit by date This option will transfer all samples older than
the specified number of days. Each day begins at midnight, and
includes the current day. For example, if you enter a value of 1, all
records prior to the current day will be transferred.
Limit by record count This option will transfer all but the spec-
ified number of records. The level is set in thousands, and the
system always rounds down, so the actual number of samples left
in INETDB can be more than that amount, but will never be less.
For example, if this field is set to 30 (thirty thousand samples) and
there are 46,123 samples in INETDB at the time the transfer starts,
then 16,000 records will be transferred and 30,123 will remain in
INETDB.
Note: If the system is busy, it is possible that the transfer will not start at
precisely the time specified.
Buttons
OK Accepts any changes and closes the editor.
Note: Before transferring for the first time, you must select either OK or
Apply to accept the default settings (or your own) to enable the
Transfer Now button. This first setting is necessary to create the
transfer database.
End date the ending date for archived samples. The default
value is the last day of the previous year.
End time the ending time for archived samples. The
default value is one second before midnight (23:59:59) of the
selected day.
These parameters are inclusive: all samples with a date and time up
to and including the selected parameters will be moved to the
archive database. The samples are removed from the online data-
bases (INETDB and/or ITrendDB) and are no longer available for
viewing, editing or deletion from within the TAC I/NET Seven
editors.
The archive database will be stored in the location specified as the
Archive directory in TAC I/NET Sevens Configure program. Refer
to TCON298, TAC I/NET Seven Getting Started, for more informa-
tion on setting directories.
Each archive is stored in a separate file. The file naming convention
is as follows:
TARCH_YYYYMMDDMPMSS.mdf (I/NET Seven 2.12 or earlier)
OR
TARCH_YYYYMMDDMPMSS.ARC (I/NET Seven 2.13 or later)
where:
TARCH_ = indicates a trend sample archive
YYYY = four-digit year
MM = two-digit month (0112; 01 = January, 12 = December)
DD = day of month (0131)
MPM = four-digit minutes past midnight (00001339)
SS = two-digit seconds (0059)
.mdf (I/NET Seven 2.12 or earlier) = indicates a file in
Microsoft standard database format.
OR
.ARC (I/NET Seven 2.13 or later) = indicates a file in SQL
database format.
A
8
DCU Control Hierarchy
AO Analog Output
CP Calculated Point
DC Discrete Control
DO Discrete Output
EV Event
GO Digital Output
TC Temperature Control
TS Time Scheduling
DMD**
TC* CP***
OB
B
VAV **** EV HW
M
TS OB EV DO/DC
NON W/L
OB
DI
AIC
Priority
lowest highest
CP***
VAV****
EV HWM
EV
AHU**** W/L AO
UC-PID**** HHC
M
HPMP****
AIC
Priority
lowest highest
TCON30004/13
CHAPTER
12 11 10 9 8 7 6 5 4 3 2 1 24 23 22 21 20 19 18 17 16 15 14 13 12
B-1
CHAPTER
C
14
Controller Point Addressing
7750 Building Manager The 7750 is a special case in that it contains 32 zones for a one-station
TCON098 device and 64 zones for a two-station device. Each zone is an internal
(software) DO point with bit offset 00. All output points on the 7750 are
internal or indirect.
DI / AI / PI 0000 3109
7771 MODBUS DO / PWM 0000 3109
TCON102
This controller can have up to 640 resident hardware or software points
per station address.
Base unit inputs 0000 0007
Expansion board #1 inputs 0100 0107
Expansion board #2 inputs 0200 0207
7780 Distributed Lighting Expansion board #3 inputs 0300 0307
Control Unit (DLCU)
TCON100 Matrix Board #1 outputs 0000 0107
Matrix Board #2 outputs 0200 0307
Matrix Board #3 outputs 0400 0507
Matrix Board #4 outputs 0600 0707
7791: 1 channel with up to 32 devices (DIO, DIU, DPU, SCU)
7792: 2 channels with up to 32 devices each (MR, ASC)
7790 LIU TCON109 7793: 2 channels with up to 32 devices each (MR, ASC, DIO, DIU, DPU,
SCU)
7797: depends on the ICI it is connected to and the devices the ICI is
supporting
7798 I/SITE LAN
1 channel of up to 32 devices (MR, ASC, DIO, DIU, DPU, SCU)
TCON138
MR-VAV-AX Application AI / DI 00 03
Specific Controller (ASC) DO / PWM (low voltage triac) 00 02
TCON147 CFM velocity sensor input 09
MR-VAV-X1 Application AI / DI 00 03
Specific Controller (ASC) DO / PWM (low voltage triac) 00 05
TCON155 CFM velocity sensor inputs 08 09
Note: The total points possible listed for each controller are theoretical
maximums. Typically you will never need or use this many points in
a single controller. The actual capacity of a controller depends on the
point types and the extensions you associate with those points. If you
use analog point types or multiple extensions per point, the controller
capacity drops. Certain extensions require more memory than others,
I/STAT input 1
Universal inputs 15
MR160 Micro Regulator
Total hardware points 16
(MR) TCON126
Total software points (input points only) 4
Total possible points (input points only) 20
I/STAT input 1
Universal inputs 5
Low voltage triac outputs 3
MR632 Micro Regulator
Analog outputs (0 10 V) 2
(MR) TCON126
Total hardware points 11
Total software points 9
Total possible points 20
Analog or discrete input 4
Analog or discrete output 6
MR-AHU Application
Specific Controller (ASC) Total hardware points 10
TCON153
Total software points 10
Total possible points 20
Analog input 4
Analog or discrete output 3
MR-VAV-AX Application CFM input 1
Specific Controller (ASC)
TCON147 Total hardware points 8
Total software points 12
Total possible points 20
Analog input 4
Analog or discrete output 6
MR-VAV-X1 Application CFM input 1
Specific Controller (ASC)
TCON155 Total hardware points 11
Total software points 9
Total possible points 20
Address Structure
A The structure of the address defining
the link, station, point, bit offset, and
Action Messages point type on the TAC I/NET
controller LAN shown as four pairs of
These are predefined instructions or
numbers and two letters describing
information automatically routed to
the point address: LLSSPPBB PT
specific host stations for printing or
(link, station, point, bit offset, and
storing. They provide additional
point type).
information when a point transitions
into or out of an alarm state or a spec- AHU-UC
ified state or value.
An Air Handling Unit Unitary
Access Control Controller is a cost-efficient TAC
controller containing a reduced point
A part of the TAC I/NET Seven system
count and typically controlling one
that controls, monitors and restricts
packaged Air Handling Unit.
access using Door Processor Units.
Air Handling Unit (AHU)
Access Initiated Control
Equipment that mixes air of various
A TAC I/NET Seven function that lets
temperatures to produce cooling or
you initiate a control action in
heating.
response to an access transaction for a
selected tenant number, and one or Alarms
more key/card numbers.
Conditions that meet or exceed user-
Adaptive Tuning defined limits. TAC I/NET Seven indi-
cates alarm conditions, return-to-
This is the DDC process where TAC
normal conditions, and provides a
I/NET Seven successively changes the
means to acknowledge and purge
output to a device and observes the
these alarms. TAC I/NET Seven
resultant changes to the process vari-
signals alarms with an audible tone,
ables in order to recalculate the P, I,
which may be turned off, and with a
and D module parameters.
visual message displayed in the top left
corner of your screen.
Backup Boolean
The action of creating a duplicate set A type of algebra relating to logical
of current files on floppy diskettes, concepts incorporating operators such
hard disk, or tape. You normally as AND, OR, and NOR. A boolean
create backups to ensure that a cata- function combines values that are
strophic loss of files or host computer either true or false (binary 1 or 0) with
equipment will not wipe out the logical operators.
current operating files.
Building Manager
Backup Station A specific type of DCU. The 7750
A workstation that is fully dedicated Building Manager provides an easy
to backup host workstation data files. way to override normal day-to-day
schedules for various pieces of equip-
Baud ment within a facility, such as lighting
A unit of measurement indicating the and environmental controls. The
number of bits that can be transmitted override totals are accumulated for
each second. For example, 1200 baud each zone, and the totals are available
indicates that the device can transmit for generating energy-usage reports
1200 bits of information per second. and billing.
Binary Byte
This term refers to the base 2 number A group of bits forming a unit of
system that uses only the digits 1 and storage in a computer. A byte is
0. In this system, a binary number is usually eight bits long and is usually
the sum of successive powers of two. represented by one alphanumeric
For example, the binary number 1011 character.
is equal to the decimal number 11.
(1 23) + (0 22) + (1 21) + (1 20)
= (8) + (0) + (2) + (1) = (11). This
term also refers to a discrete situation
where only two conditions can exist C
(on or off, open or closed, alarm or
Calculations
normal, etc.).
Calculations are performed either
Bit through the calculation extension
This is a digit in the binary system editor or the calculation module (MR
represented by 0 or 1. A bit is the only). Calculations let you manipulate
smallest storage unit in a computer. data to control equipment or produce
reports.
Circuit Consumption
A single point in the 7780 DLCU A point extension editor and function
controller. This point may control a that directs the accumulated value of a
single source (lamp), or several PI point to a SevenTrends table.
sources that have been daisy-chained Consumption monitors the amount
together into the same controller of a consumable resource that is being
point (such as a specific floor or physically measured by the system.
tenant space within a facility).
Control Descriptions and Commands
Closed Loop This is a station parameter editor.
A type of process control where a Here you define pairs of control
computer can respond to feedback descriptions such as start and stop, on
from a sensor or control equipment and off, open and closed, etc. You
without human intervention. For must correlate each pair with a
example, the computer could lower or specific output command (0 or 1).
raise the temperature in a room if a
sensor indicates the temperature is too Control Parameters
warm or too cold. Parameters you define to help you
control a DCU. These parameters
Configuration Editors include date, time, distribution
These are TAC I/NET Seven editors groups, masking, and priority.
that let you set the parameters of the
host station, Taps, DCUs, and other Controller
devices while online with TAC I/NET A general term for DCUs (distributed
Seven. control units), PCUs (process control
units), DLCUs (distributed lighting
Controller LAN
A local area network that connects D
two or more DCUs. These DCUs can
then exchange point data. Database
A collection of data organized for
Conversion Coefficients rapid search and retrieval by a
This is a station parameter editor. computer. TAC I/NET Seven uses a
Conversion coefficients are mathe- database to organize and store data
matical constants a controller uses to collected by the DCUs.
convert analog input/outputs from
the digital value (counts) used by the DCU
microprocessor to analog display Distributed Control Unit. A micro-
values. Conversion coefficients are processor-based controller used as a
also used to convert digital values part of the TAC I/NET Seven system.
(counts) from the microprocessor into The DCU connects directly to the
analog outputs which are then used by controller LAN and works in conjunc-
field interface devices. tion with other controllers and work-
stations on the LAN. The DCU,
CRT depending on the model, is capable of
Cathode Ray Tube. This term usually monitoring and controlling up to 640
refers to the screen on your computer. addressable points while providing
DDC, energy management functions,
Current Loop and process control.
A serial transmission standard in
which a pair of wires connecting the Demand Control
receiving and sending devices Use this editor to monitor electrical
transmit binary 0 when no current power consumption, and calcu-
flows and binary 1 when current late/predict electrical demand. You
flows. can maintain a daily or monthly
consumption total. Demand control
DPI
Door Processor Interface. The 7791
provides a communications gateway
E
between the controller LAN and the Editor Line
DPUs. It passes information between
Line 1 of the display in TAC I/NET
the host, controller, and subLANs.
Seven 3.x versions. The first five char-
You can attach up to 32 DPUs to one
acters are reserved for the printer
DPI. The DPI occupies a single
malfunction, alarm, and message
controller LAN address, effectively
icons. The rest of the line displays the
extending the span of controllers that
host date, time, and day of week. The
may be assigned to a single controller
menu function or editor currently
LAN.
accessed is also displayed on this line.
DPU
Engineering Units
The Door Processor Unit. The DPU
A station parameters editor. These are
7900, 7910A, and 7920 are used to
units of measurement applied to
control access through doors, gates
analog input and accumulator point
and elevators. Door readers may be
values in system messages. DegF,
attached to them providing either
DegC, KW, and KWH are examples of
multiple entry readers or entry and
engineering units.
exit readers for anti-passback zones.
Elevator Reader
Driver
A reader that performs access control
Communications protocol between
in elevator cabs by controlling the
the computer terminals operating
floors that the elevator can access.
system and the TAC I/NET Seven soft-
ware. The driver receives transmis- EPROM
sions (messages, alarms, or data) from
the controller(s) and routes them to Erasable Programmable Read-Only
the appropriate place (system page Memory. A type of ROM that can be
display, alarm or message summary, erased (with ultraviolet light) and
SevenTrends database, etc.). The reprogrammed.
driver can run in background
Equation
(continue to route TAC I/NET Seven
data while other programs are An arithmetic statement containing at
running). least two expressions; e.g., 3 + 4, 6 2.
Firmware Status
Display only field in DCU configura-
tion/status editor. This field lists the
G
revision number and the date of the Global Points
firmware installed in the controller.
A point defined through TAC I/NET
First Key Auto-unlock Seven to broadcast its data for sharing
with other points and DCUs. You can
A security function that can be
define a point as global to a controller
programmed in a DPU. This function
LAN, host LAN, or to the entire TAC
keeps a door locked until a person
I/NET system.
uses a valid key/card in a door reader
after the doors mode schedule unlock Graphic Symbols
cycle has begun.
Symbols used on a system page repre-
Floating Module senting monitored and controlled
equipment.
A DDC module with two discrete
outputs (increase and decrease) used Graphics Printer
to drive bidirectional actuators with
A printer that is equipped to print
dual windings or coils.
graphics rather than just ASCII char-
Floor acters. This printer can print XY plots,
trend logs, and time-based plots.
An elevator extension parameter that
defines a DO and DI point for assign- Groups
ment with a DPI floor extension
Individuals can be collected in groups
point. This association of these DO
to simplify access control parameter
and DI points produces a closed loop,
definition and maintenance. The indi-
allowing the controller to identify an
viduals are assigned to specific groups
elevator floor selection with each
in the individuals editor.
successful key/card reader access.
FM Coefficient
The factory setting for the m or slope
conversion coefficient. This is one of
the parameters used to convert analog
H
inputs from the digital value (counts) Hand-held Console (HHC)
used by the microprocessor to analog A device that lets you communicate
display values. directly with a controller without
See also: Conversion Coefficients using a workstation. You use the HHC
to program addresses, baud rates, and
Hi-Lo Module IK
A DDC module that compares up to
four input values and simultaneously I/DISC
provides individual high and low Small metal buttons that can be used
outputs that can be used as inputs to for access control in place of keys or
other modules. cards.
Issue Level
Some cards and keys allow up to four
issues of the same key/card number. If
a different issue number is read on a
key/card than is recorded in the data-
base for it, access is denied.
MCI
Micro Control Interface. The 7793
M MCI functions identically to the 7791
DPI and 7792 MRI, with the addition
M/STAT of the demand control editor. You can
Maintenance thermostat. A portable attach up to 64 MRs/ASCs/DPUs to
space sensor with local temperature one MCI. The MCI occupies two
and setpoint display, override select, consecutive controller LAN addresses,
and setpoint adjustment. The M/STAT extending the total controllers that
is a portable version of the I/STAT, may be assigned to a single controller
with a plug-in jack, and is functionally LAN.
identical to the I/STAT.
See also: I/STAT, S/STAT Megabit (Mb)
One million bits.
Manual Off
A system action that enables all auto- Megabyte (MB)
matic control commands to a DCU One million bytes.
resident point or door.
Mask
Manual On Part of message masking, a filtering
A system action that prohibits all system used to route messages, alarms,
automatic control commands to a and data to host workstations. TAC
DCU resident point or door. I/NET Seven has eight mask positions
in each of four distribution groups,
Masking for a total of 32 possible mask posi-
A filtering system used to route tions. Both the distribution group and
messages, alarms, and data to system at least one active mask position must
workstations. Masking consists of the match for the message to be received
distribution group and active mask and stored at a host workstation.
positions. The pattern of active and See also: Masking
inactive mask positions in each distri-
bution group determines whether a
host workstation will accept the
message. Both the distribution group
Operand
The data upon which an operation
(such as adding, dividing, etc.) is
P
performed. For example, in the Parameter (Calculated Point)
expression 3 + 4, 3 and 4 are the A type of operand (P0P9) used in
operands, and + is the operator. calculated point editor or in a MR-
resident calculation module editor as
Operator Station
opposed to constants (C0C9).
Any computer terminal used as a
workstation on TAC I/NET Seven. PCU
Operator stations are also known and Process Control Unit. A specialized
referred to as host workstations or type of controller or DCU. The 7716
hosts. and 7718 controllers are PCUs.
S SevenTrends
S/STAT A data storage and report generation
program within TAC I/NET Seven.
Slide thermostat. An intelligent space You can produce recurring/nonrecur-
sensor with local temperature and ring tabular reports, XY plots, and
setpoint display, override select, and time-based plots.
setpoint adjustment. The S/STAT is
similar to the I/STAT, but with a slide Signon
control instead of a keypad.
Entering the TAC I/NET Seven system
See also: I/STAT, M/STAT
with a valid password
SLI
Signoff
The SubLAN Interface (SLI) acts as a
Exiting the TAC I/NET Seven system,
communication gateway, allowing
securing the host from unauthorized
controllers on its subLAN to commu-
use.
nicate with the rest of the TAC I/NET
system. The 7791 DPI, 7793 MCI, and Shunt
7798 I/SITE LAN are SLIs.
A parameter in the door parameters
editor. This option is used to bypass
an in-house alarm system when the
door is opened because of a valid
key/card read.
Thermistor
A specialized temperature-sensing
T device that can be connected to
certain controllers. It contains a semi-
Tap conductor sensing element where the
A communication device that lets resistance falls in a highly non-linear
operator stations communicate with fashion as the temperature rises. Ther-
DCUs on controller LANs. mistors are very accurate over small
temperature spans.
Temperature Control
A point extension for DC and DO Time Scheduling
points that provides information for A point extension editor that lets you
optimized cycling, optimized start/ schedule start, stop, and cycle times
for a DO/DC point.
Unlock Visitor
A mode schedule parameter that An individual or group allowed
enables a door for open access during temporary access to a door or group
a scheduled cycle. Key/card readers are of doors.
still enabled for continued access
control auditing (roll call).
Workstation
A computer and its associated hard-
Utilities ware and software. In TAC I/NET
These TAC I/NET programs perform Seven the term workstation is used
specific specialized functions not interchangeably with operator
normally covered by TAC I/NET station, host workstation, and
Seven. Utility programs are usually host.
involved in basic housekeeping func-
tions such as backups, restores, and
XY Plot Report
file copying. A SevenTrends report showing the
relationship of data from two system
points: one plotted on the x-axis, the
other on the y-axis. The intersection
of the two data cells produces a point
VZ on the plot. XY plots produce a series
of points that are connected with a
VAV-UC line.
Variable Air Volume UC. This UC
controls pressure dependent/indepen- Zone
dent single-duct, cooling, or heating A term associated with the lighting
terminal boxes. They are also used to control, override billing, and door
control double-duct terminal boxes. point extension editors. A zone
They have either one or two velocity usually refers to a specific area of a
Zoom
The zoom command on a system page
lets you move automatically from the
selected icon to a point or point exten-
sion editor.
O
off-normal points 4-29
N offset 6-24
NetPlus Router 1-8, 1-34, 1-35, 2-262-34 operator stations, maximums 1-33
address 2-29, 2-32 operator time-out 4-3
configuration 2-282-33 action 4-2
activating 2-29 override
entry fields 2-292-33 data transmission 16-8
restoring 2-33 description 16-10
saving 2-33
controller LAN address 2-32 override billing
diagnostic LEDs 2-34 access codes 7-35
diagnostics 2-34 equipment mapping 7-36
domain name override parameters 7-36
domain name 2-30 wink 7-37
gateway address 2-30 zones 7-34
integrated dial function 2-27 override parameters 7-31
IP address 2-29 override trend
link address 2-32 memory requirements 16-23
modem 2-27
name 2-29
network connection 2-32
password 2-33
reference host 2-31
SNMP 2-31
P
station address 2-32 pager operation
subnet mask 2-30 78060/1 Tap 2-22
Tap functions 2-27 character definitions 2-22
network configuration 4-20, 4-24 pages, system 4-19
normal state 6-20 password
NPR see NetPlus Router adding a new host 4-5
AMT 3-11
number of samples 4-34 authorization levels 4-16
DCU password editor 4-16
DCU passwords 4-16
function selection 4-7
S special days
see time scheduling
SAVE file 4-31 state 5-18
save, automatic DCU 4-27 close 5-18
trip 5-18
scan interval 6-14
VZ
VAV
see unitary controller
workstation requirements 1-3
Xenta 527/527-NPR 1-35
zone definitions
override parameters 7-31
Schneider Electric
Buildings Americas
1650 W. Crosby Rd.
Dallas, TX 75006 USA
Phone: +1 (972) 323 1111
Fax: +1 (972) 242 0026
Schneider Electric
Buildings Asia-Pacific
Level 3/2A Lord Street
Botany NSW 2019
Australia
Phone: +61 (0) 2 8336 6100
Fax: +61 (0) 2 8336 6190
www.schneider-electric.com/buildings
TCON30004/13