i/net® seven system€¦ · we at schneider electric have tried to make the information contained...

TAC I/NETSeven

Operator Guide

I/NET® Seven System

Front Cover

TCON299–05/10

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: TCON299–05/10

Copyright 2001–2010 Schneider Electric. All rights reserved.

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.

© 2001–2010 Schneider Electric. All rights reserved. iiiTCON299–05/10

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, don’t use it.

Schneider Electric makes no claims or commitments regarding the use of any third-party software, other than MS-DOS® and Windows® Server 2003/XP/Vista/7 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.

© 2001–2010 Schneider Electric. All rights reserved. vTCON299–05/10

Contents

Chapter 1 TAC I/NET Seven BasicsAbout This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

File Names and Menu Commands . . . . . . . . . . . . . . . . . . . . . 1-1Keystrokes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Standard Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Selecting Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Menu Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Toolbar Selection . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Highlighting an Item . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Entering Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Screen Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Grayed Out Selections . . . . . . . . . . . . . . . . . . . . . . . . 1-7Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Text Fields and Spindials . . . . . . . . . . . . . . . . . . . . . . . 1-7Edit Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Buttons and Checkboxes . . . . . . . . . . . . . . . . . . . . . . . 1-8Message Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10List Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Drop-down Boxes . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Starting TAC I/NET Seven . . . . . . . . . . . . . . . . . . . . . . . 1-13

Connecting to the System. . . . . . . . . . . . . . . . . . . . . . . . 1-15

Disconnecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Exiting TAC I/NET Seven. . . . . . . . . . . . . . . . . . . . . . . . 1-18

System Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Building an Address . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Creating a Controller Address . . . . . . . . . . . . . . . . . . . . 1-19Creating a UC, DPU, SCU, or MR Address . . . . . . . . . . . . . . 1-20

© 2001–2010 Schneider Electric. All rights reserved. viiTCON299–05/10

Forms and Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Controlling Window Layouts in TAC I/NET Seven . . . . . . . . . . 1-23

Retrieving Obstructed Windows . . . . . . . . . . . . . . . . . . . . 1-24

Creating User-defined Tools and Buttons . . . . . . . . . . . . . . . 1-25

Configuring User Tools . . . . . . . . . . . . . . . . . . . . . . . . . 1-26Configuring User Buttons . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Using the System View Interface . . . . . . . . . . . . . . . . . . . . 1-31

The System View Window. . . . . . . . . . . . . . . . . . . . . . . . 1-31The Left-side Pane . . . . . . . . . . . . . . . . . . . . . . . . . 1-31The Right-side Pane . . . . . . . . . . . . . . . . . . . . . . . . 1-32

Expanding and Collapsing Items . . . . . . . . . . . . . . . . . . . . . 1-32Using Drag and Drop . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Displaying a Context-sensitive Popup Menu . . . . . . . . . . . . . . . . 1-33Print and Print Preview . . . . . . . . . . . . . . . . . . . . . . . . . 1-33

Using Your Windows Login with TAC I/NET Seven . . . . . . . . . . 1-35

Configuring I/NET Seven to Accept a User's Windows Logon . . . . . . . . 1-35Logging In Using Your Windows Account . . . . . . . . . . . . . . . . . 1-36

Auto-launching TAC I/NET Seven at Startup . . . . . . . . . . . . . 1-36

Running I/O Server as a Windows Service . . . . . . . . . . . . . . . 1-38

Why Run I/O Server as a Windows Service? . . . . . . . . . . . . . . . . 1-38Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38Configuring I/O Server to be a Windows Service . . . . . . . . . . . . . . 1-39Configuring I/O Server to Stop Being a Windows Service . . . . . . . . . . 1-43

Manually Shutting Down IO Server . . . . . . . . . . . . . . . . . . 1-45

Stopping IO Server from Windows Services . . . . . . . . . . . . . . . . 1-45Stopping IO Server from the Windows System Tray . . . . . . . . . . . . 1-47Stopping IO Server from the Windows Task Manager. . . . . . . . . . . . 1-48

Registering INetEqzMerge as a Windows Service . . . . . . . . . . . . 1-49

Checking for the INetEqzMerge Service . . . . . . . . . . . . . . . . . . 1-50Manually Registering INetEqzMerge as a Windows Service. . . . . . . . . . 1-51

viii © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Chapter 2 Setup and Network ConfigurationTAC I/NET Seven Configuration . . . . . . . . . . . . . . . . . . . . . 2-1

Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Defining the Network Configuration. . . . . . . . . . . . . . . . . . . 2-5

Using System View to Configure Your Network . . . . . . . . . . . . . . . 2-6Viewing Each Level of Your Network . . . . . . . . . . . . . . . . . . 2-6Displaying Popup Menus . . . . . . . . . . . . . . . . . . . . . . . 2-7Refreshing the System View Window . . . . . . . . . . . . . . . . . . 2-9Network Status Indicators. . . . . . . . . . . . . . . . . . . . . . 2-11

Using NETCON to Configure Your Network . . . . . . . . . . . . . . . 2-12Penetrating the Levels of Your Network . . . . . . . . . . . . . . . . 2-12Storing Network Configuration Records . . . . . . . . . . . . . . . 2-12Network Summaries . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Adding a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Adding a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Adding a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Adding an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Adding a Door Point . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Adding a Floor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

DCU Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Automatic DCU Save . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Special Day Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Special Day Broadcast Setup. . . . . . . . . . . . . . . . . . . . . 2-35Global Special Day Broadcast Setup . . . . . . . . . . . . . . . . . 2-36Broadcast Review . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Off Normal Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Disabled Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Database Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Chapter 3 Tap ConfigurationTap Configuration Editors . . . . . . . . . . . . . . . . . . . . . . . . 3-1

© 2001–2010 Schneider Electric. All rights reserved. ixTCON299–05/10

Tap Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Integrated Dial Function . . . . . . . . . . . . . . . . . . . . . . . . . 3-478060 and 78061 Tap Configuration . . . . . . . . . . . . . . . . . . . . 3-5

Site Tap Save / Restore . . . . . . . . . . . . . . . . . . . . . . . . 3-7Printer Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Multiple Site Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Chapter 4 Controller ConfigurationController Configuration/Status . . . . . . . . . . . . . . . . . . . . . 4-1

Configuring the Controller . . . . . . . . . . . . . . . . . . . . . . . . 4-1Controller Details . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Distribution Parameters . . . . . . . . . . . . . . . . . . . . . . . 4-4Sunrise/Sunset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Daylight Savings . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Program Extensions . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Viewing Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Memory Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Database Last Changed . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Loading Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Firmware Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Controller Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Editing the Database while Offline . . . . . . . . . . . . . . . . . . . . 4-9

Connecting Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Adding a .SAV File Offline . . . . . . . . . . . . . . . . . . . . . . 4-10Deleting a .SAV File Offline . . . . . . . . . . . . . . . . . . . . . 4-12Copying a .SAV File Offline . . . . . . . . . . . . . . . . . . . . . 4-12

Station Save and Restore . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Station Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Station Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Station Restore on a DPI . . . . . . . . . . . . . . . . . . . . . . 4-14Station Restore on a DPU . . . . . . . . . . . . . . . . . . . . . . 4-14

The Memory Interface Processor Module . . . . . . . . . . . . . . . . . 4-14

Software Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

x © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Performing a Software Restore to Taps and Controllers . . . . . . . . . . . 4-15Performing a Software Restore to DPUs and SCUs . . . . . . . . . . . . . 4-17

Dynamic Data Upload . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Defining and Entering Station Parameters . . . . . . . . . . . . . . . 4-19

Entering the Station Parameters . . . . . . . . . . . . . . . . . . . . . 4-20Control Descriptions and Commands . . . . . . . . . . . . . . . . 4-20State Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Conversion Coefficients. . . . . . . . . . . . . . . . . . . . . . . . . 4-23Pop-up Calculator . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Engineering Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Lookup Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Chapter 5 Point Definition and AddressingAdding Points to Your Controller . . . . . . . . . . . . . . . . . . . . 5-1

Modifying Points in Your Controller . . . . . . . . . . . . . . . . . . . 5-3

Copying Points in Your Controller . . . . . . . . . . . . . . . . . . . . 5-3

Deleting Points from Your Controller . . . . . . . . . . . . . . . . . . 5-4

Sorting Points in Your Controller . . . . . . . . . . . . . . . . . . . . 5-5

Input/Output and Addressing . . . . . . . . . . . . . . . . . . . . . . 5-5

Tips for Point Addresses . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Chapter 6 System MessagesAMT Menus and Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

AMT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Alarm Colors and Archive Colors . . . . . . . . . . . . . . . . . . . . . 6-6Image Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Relay Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Audible Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Message/Alarm and Printer Masks . . . . . . . . . . . . . . . . . . . . . 6-9

Managing Windows in AMT . . . . . . . . . . . . . . . . . . . . . . 6-10

© 2001–2010 Schneider Electric. All rights reserved. xiTCON299–05/10

Opening a New AMT Window. . . . . . . . . . . . . . . . . . . . . . 6-11Alarm Window . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Event Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Predefined Windows . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Closing an AMT window . . . . . . . . . . . . . . . . . . . . . . . . 6-13Arranging multiple windows . . . . . . . . . . . . . . . . . . . . . . 6-13

Cascading Windows . . . . . . . . . . . . . . . . . . . . . . . . 6-15Tiled Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Printing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16Changing the Window Display. . . . . . . . . . . . . . . . . . . . . . 6-17

Pausing the Message Update . . . . . . . . . . . . . . . . . . . . . 6-18Column Width. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Window Options. . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Alarm Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30

Acknowledging an Alarm . . . . . . . . . . . . . . . . . . . . . . . . 6-34Purging Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Silence Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Dispatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Dispatch Strings Library . . . . . . . . . . . . . . . . . . . . . . . . 6-35Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37

Event Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37

Text Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39Creating a Text Entry . . . . . . . . . . . . . . . . . . . . . . . . 6-39Modifying a Text Entry . . . . . . . . . . . . . . . . . . . . . . . 6-41Copying a Text Entry . . . . . . . . . . . . . . . . . . . . . . . . 6-41Deleting a Text Entry . . . . . . . . . . . . . . . . . . . . . . . . 6-42

Image Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42Activating Image Verification . . . . . . . . . . . . . . . . . . . . 6-43De-activating Automatic Image Verification . . . . . . . . . . . . . . 6-46

Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47

Event Archive Configuration. . . . . . . . . . . . . . . . . . . . . . . 6-47Performing Event Archiving . . . . . . . . . . . . . . . . . . . . . 6-49

xii © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Triggered Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51Automatic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52Confirmed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52

Manual Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53Opening an Event Archive. . . . . . . . . . . . . . . . . . . . . . . . 6-54

CCTV in AMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55

CCTV Message Timestamps . . . . . . . . . . . . . . . . . . . . . . . 6-55Opening the AMT Video Window . . . . . . . . . . . . . . . . . . . . 6-56Viewing the Selected Event’s Captured Video . . . . . . . . . . . . . . . 6-56Viewing Live Video. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56Searching Captured Video. . . . . . . . . . . . . . . . . . . . . . . . 6-57

Chapter 7 SummariesController Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Controlling a Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Point Acknowledge . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Reset Anti-passback . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Zooming to a Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Sorting the Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Off Normal Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Disabled Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Configuration Summaries . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Host Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Link Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Station Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11UC Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12MR Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12DPU Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Door Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

© 2001–2010 Schneider Electric. All rights reserved. xiiiTCON299–05/10

Page Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Chapter 8 System PagesThe Graphics Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Working with System Pages . . . . . . . . . . . . . . . . . . . . . . . . 8-3Creating a New System Page . . . . . . . . . . . . . . . . . . . . . . 8-3Editing an Existing System Page . . . . . . . . . . . . . . . . . . . . 8-4Exiting the Graphics Editor . . . . . . . . . . . . . . . . . . . . . . 8-4TAC I/NET 4.x Graphic Pages . . . . . . . . . . . . . . . . . . . . . 8-5

Working with Graphic Objects. . . . . . . . . . . . . . . . . . . . . . . 8-7Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Deselecting Objects. . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8Positioning Objects. . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9Resizing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Mouse Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

System Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13File Management. . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Library Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14Importing Graphics . . . . . . . . . . . . . . . . . . . . . . . . 8-16Printing Functions . . . . . . . . . . . . . . . . . . . . . . . . . 8-17Address Conversion . . . . . . . . . . . . . . . . . . . . . . . . 8-18Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

View Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Graphics Properties . . . . . . . . . . . . . . . . . . . . . . . . 8-20Page Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Zooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28Window Backgrounds . . . . . . . . . . . . . . . . . . . . . . . 8-28Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Displaying Toolbars . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Edit Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Undo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

xiv © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Lock/Unlock. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Rotate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Flip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Select All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Clear All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Select Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Zoom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Library Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Entering Text . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Fill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Square . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Rectangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Rounded Rectangle. . . . . . . . . . . . . . . . . . . . . . . . . 8-38Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Ellipse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Polylines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Chord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40Pie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40Arc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40Free Pen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40

Arrange Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41Bring to Front . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41Send to Back. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41Step Forward . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42Step Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42Ungroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42

© 2001–2010 Schneider Electric. All rights reserved. xvTCON299–05/10

Alignment Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43Coordinates Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45Pen and Fill Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45

Pen Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46Pen Width. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46Pen Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46Fill Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47Fill Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47

Text Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48Text Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49Back Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49Center Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Left Align Text . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Right Align Text . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Auto Word Wrap . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Auto Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50

I/NET Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51

Connecting to Multiple Controllers . . . . . . . . . . . . . . . . . 8-51Digital Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53Analog Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57

Door Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-59Adding Point Extensions . . . . . . . . . . . . . . . . . . . . . . . . 8-60

Extension Editors . . . . . . . . . . . . . . . . . . . . . . . . . 8-61Adding DDC Modules . . . . . . . . . . . . . . . . . . . . . . . . . 8-62Adding DDC Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-64Page Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-66

Adding Page Markers . . . . . . . . . . . . . . . . . . . . . . . . 8-66Using Page Markers . . . . . . . . . . . . . . . . . . . . . . . . 8-67

Adding Multiple Site Dial . . . . . . . . . . . . . . . . . . . . . . . . 8-68Adding a Graphic Dial Icon . . . . . . . . . . . . . . . . . . . . . 8-68Dialing from a Graphic Page. . . . . . . . . . . . . . . . . . . . . 8-69Disconnecting From a Dial Site . . . . . . . . . . . . . . . . . . . 8-69

Adding ASC Markers . . . . . . . . . . . . . . . . . . . . . . . . . . 8-70

xvi © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Adding Tool Markers . . . . . . . . . . . . . . . . . . . . . . . . . . 8-71Adding CCTV Markers . . . . . . . . . . . . . . . . . . . . . . . . . 8-73

Live System Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-73

Viewing Live System Pages . . . . . . . . . . . . . . . . . . . . . . . 8-73Viewing another Page. . . . . . . . . . . . . . . . . . . . . . . . 8-74Setting a Default System Page . . . . . . . . . . . . . . . . . . . . 8-74

Icons and Editor Access . . . . . . . . . . . . . . . . . . . . . . . . . 8-75Replacing Icons . . . . . . . . . . . . . . . . . . . . . . . . . . 8-76

Chapter 9 PasswordsHost Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Adding a Host Password . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Function Selection . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Station Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Tenant Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Individual Selection . . . . . . . . . . . . . . . . . . . . . . . . 9-10DCU Password Preassignment . . . . . . . . . . . . . . . . . . . . 9-11

Indirect User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

Limited-access Users . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15Example: A Medical Center with Three Access-controlled Labs . . . . . 9-17Implementing and Using this Example . . . . . . . . . . . . . . . . 9-21

Printing a Host Password Report . . . . . . . . . . . . . . . . . . . . . 9-26Searching for a Host Operator Password . . . . . . . . . . . . . . . . . 9-26Deleting a Host Password . . . . . . . . . . . . . . . . . . . . . . . . 9-27Modifying a Host Password . . . . . . . . . . . . . . . . . . . . . . . 9-27Copying a Host Password . . . . . . . . . . . . . . . . . . . . . . . . 9-28Printing a Host Passwords Report . . . . . . . . . . . . . . . . . . . . 9-28

Assigning Controller Passwords . . . . . . . . . . . . . . . . . . . . 9-29

DCU Password Editor . . . . . . . . . . . . . . . . . . . . . . . . . 9-29DCU Password Recover . . . . . . . . . . . . . . . . . . . . . . . . . 9-30

© 2001–2010 Schneider Electric. All rights reserved. xviiTCON299–05/10

Chapter 10 Dynamic ControlTime Scheduling (TS). . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Adding a Point Time Schedule . . . . . . . . . . . . . . . . . . . . . . 10-1Adding an Independent or a Master Schedule . . . . . . . . . . . . . 10-3Adding a Slave Schedule. . . . . . . . . . . . . . . . . . . . . . . 10-5

Modifying a Point Time Schedule . . . . . . . . . . . . . . . . . . . . 10-7Copying a Point Time Schedule . . . . . . . . . . . . . . . . . . . . . 10-7Deleting a Point Time Schedule . . . . . . . . . . . . . . . . . . . . . 10-8

Host ATS (Automatic Time Schedule) . . . . . . . . . . . . . . . . . 10-8

Adding a Host Time Schedule . . . . . . . . . . . . . . . . . . . . . . 10-9Modifying a Host Time Schedule. . . . . . . . . . . . . . . . . . . . . 10-12Copying a Host Time Schedule . . . . . . . . . . . . . . . . . . . . . 10-12Deleting a Host Time Schedule . . . . . . . . . . . . . . . . . . . . . 10-13

Special Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14

Adding Special Days . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14Modifying Special Days . . . . . . . . . . . . . . . . . . . . . . . . . 10-16Deleting Special Days . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16

Temperature Control (TC) . . . . . . . . . . . . . . . . . . . . . . . 10-16

Adding a Temperature Control Point Extension . . . . . . . . . . . . . . 10-16Modifying a Temperature Control Point Extension . . . . . . . . . . . . . 10-20Copying a Temperature Control Point Extension. . . . . . . . . . . . . . 10-21Deleting a Temperature Control Point Extension. . . . . . . . . . . . . . 10-22

Demand Control (DC) . . . . . . . . . . . . . . . . . . . . . . . . . 10-22

Adding a Demand Control Point Extension . . . . . . . . . . . . . . . . 10-23Modifying a Demand Control Point Extension. . . . . . . . . . . . . . . 10-29Copying a Demand Control Point Extension . . . . . . . . . . . . . . . 10-29Deleting a Demand Control Point Extension . . . . . . . . . . . . . . . 10-30

Auto Report Generation . . . . . . . . . . . . . . . . . . . . . . . . 10-31

Adding an Auto Report Generation Schedule . . . . . . . . . . . . . . . 10-31

xviii © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Chapter 11 CalculationsCalculations (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Adding a Calculated Point. . . . . . . . . . . . . . . . . . . . . . . . 11-1Modifying a Calculated Point . . . . . . . . . . . . . . . . . . . . . . 11-4Copying a Calculated Point . . . . . . . . . . . . . . . . . . . . . . . 11-4Deleting a Calculated Point . . . . . . . . . . . . . . . . . . . . . . . 11-5

Chapter 12 TrendingTrend Sampling (TR) . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Adding Trend Sampling. . . . . . . . . . . . . . . . . . . . . . . . . 12-1Modifying Trend Sampling . . . . . . . . . . . . . . . . . . . . . . . 12-4Copying Trend Sampling . . . . . . . . . . . . . . . . . . . . . . . . 12-4Deleting Trend Sampling . . . . . . . . . . . . . . . . . . . . . . . . 12-5Trend Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6

Multi-Point Trend Plot . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Defining a Multi-Point Trend Plot . . . . . . . . . . . . . . . . . . . . 12-8Adding a Plot Definition . . . . . . . . . . . . . . . . . . . . . . 12-8Modifying a Plot Definition . . . . . . . . . . . . . . . . . . . . . 12-9Copying a Plot Definition . . . . . . . . . . . . . . . . . . . . . . 12-10Deleting a Plot Definition . . . . . . . . . . . . . . . . . . . . . . 12-10Trend Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Displaying a Multi-Point Trend Plot . . . . . . . . . . . . . . . . . . . 12-13Display Functions . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

Trend Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Deleting a Trend Log . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20

Chapter 13 Distributed ControlConsumption (CN). . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Adding a Consumption Point Extension . . . . . . . . . . . . . . . . . 13-1Modifying a Consumption Point Extension . . . . . . . . . . . . . . . . 13-3Copying a Consumption Point Extension . . . . . . . . . . . . . . . . . 13-3Deleting a Consumption Point Extension . . . . . . . . . . . . . . . . . 13-4

© 2001–2010 Schneider Electric. All rights reserved. xixTCON299–05/10

Runtime (RT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Adding a Runtime Point Extension . . . . . . . . . . . . . . . . . . . . 13-5Modifying a Runtime Point Extension . . . . . . . . . . . . . . . . . . 13-7Copying a Runtime Point Extension . . . . . . . . . . . . . . . . . . . 13-7Deleting a Runtime Point Extension . . . . . . . . . . . . . . . . . . . 13-8

Alarm Inhibit (AI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9

Adding an Alarm Inhibit Point Extension . . . . . . . . . . . . . . . . . 13-9Modifying an Alarm Inhibit Point Extension . . . . . . . . . . . . . . . 13-11Copying an Alarm Inhibit Point Extension . . . . . . . . . . . . . . . . 13-11Deleting an Alarm Inhibit Point Extension . . . . . . . . . . . . . . . . 13-12

Event Definition (EV). . . . . . . . . . . . . . . . . . . . . . . . . . 13-12

Adding an Event Definition Point Extension. . . . . . . . . . . . . . . . 13-12Modifying an Event Definition Point Extension . . . . . . . . . . . . . . 13-15Copying an Event Definition Point Extension . . . . . . . . . . . . . . . 13-15Deleting an Event Definition Point Extension . . . . . . . . . . . . . . . 13-16

Event Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16

Adding an Event Sequence . . . . . . . . . . . . . . . . . . . . . . . 13-17Modifying an Event Sequence . . . . . . . . . . . . . . . . . . . . . . 13-19Copying an Event Sequence . . . . . . . . . . . . . . . . . . . . . . . 13-20Deleting an Event Sequence . . . . . . . . . . . . . . . . . . . . . . . 13-21

Event Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21

Adding an Event Action . . . . . . . . . . . . . . . . . . . . . . . . . 13-21Modifying an Event Action . . . . . . . . . . . . . . . . . . . . . . . 13-23Copying an Event Action . . . . . . . . . . . . . . . . . . . . . . . . 13-23Deleting an Event Action . . . . . . . . . . . . . . . . . . . . . . . . 13-24Configuring Event Printing on a Host Workstation . . . . . . . . . . . . . 13-25

Chapter 14 Direct Digital ControlAccessing the DDC Module Editors . . . . . . . . . . . . . . . . . . 14-1

Two Position Module (2-Pos). . . . . . . . . . . . . . . . . . . . . . 14-3

Proportional, Integral, Derivative Module (PID) . . . . . . . . . . . 14-6

xx © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

P-only Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . 14-10

Floating Module (Float) . . . . . . . . . . . . . . . . . . . . . . . . 14-10

Reset Module (Reset) . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15

HiLo Module (HiLo) . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17

Relay Module (Relay) . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19

History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

Manual Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22Input/Output Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23Automatic Tune . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23

Helpful Hints for DDC Modules . . . . . . . . . . . . . . . . . . . . 14-24

Chapter 15 Lighting ControlLighting Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Adding a Lighting Circuit . . . . . . . . . . . . . . . . . . . . . . . . 15-2Circuit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 15-4Wink Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

Modifying a Lighting Circuit . . . . . . . . . . . . . . . . . . . . . . 15-5Deleting a Lighting Circuit . . . . . . . . . . . . . . . . . . . . . . . 15-5Copying a Lighting Circuit . . . . . . . . . . . . . . . . . . . . . . . 15-5

Lighting Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

Adding a Lighting Zone . . . . . . . . . . . . . . . . . . . . . . . . . 15-6Circuit Assignments . . . . . . . . . . . . . . . . . . . . . . . . 15-8Automatic Time Schedule (ATS) . . . . . . . . . . . . . . . . . . . 15-9

Modifying a Lighting Zone . . . . . . . . . . . . . . . . . . . . . . . 15-10Deleting a Lighting Zone . . . . . . . . . . . . . . . . . . . . . . . . 15-10Copying Lighting Zones . . . . . . . . . . . . . . . . . . . . . . . . 15-10

Chapter 16 Unitary ControlConfiguring the Unitary Controller Interface . . . . . . . . . . . . . 16-1

Configuring the Unitary Controller . . . . . . . . . . . . . . . . . . 16-2

© 2001–2010 Schneider Electric. All rights reserved. xxiTCON299–05/10

Creating the UCI Database . . . . . . . . . . . . . . . . . . . . . . . 16-3

The Parent Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

UC Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Activating the New UC . . . . . . . . . . . . . . . . . . . . . . . . . 16-4

Unitary Control Parameters . . . . . . . . . . . . . . . . . . . . . . 16-5

VAV Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . 16-8Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9Delays and Offsets . . . . . . . . . . . . . . . . . . . . . . . . . 16-9

AHU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . 16-12Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12Delays and Offsets . . . . . . . . . . . . . . . . . . . . . . . . . 16-13

HPMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . 16-15Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16Delays and Offsets . . . . . . . . . . . . . . . . . . . . . . . . . 16-17

DDC Damper Control . . . . . . . . . . . . . . . . . . . . . . . . . 16-18

PID Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18Setpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19

Float (FLT) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 16-20Setpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21

UC Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22

xxii © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Chapter 17 Access ControlAccess Control Editors . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Access Control Order of Operations . . . . . . . . . . . . . . . . . . 17-2

Recycle Bin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Restoring Records from the Recycle Bin . . . . . . . . . . . . . . . . . . 17-4Purging Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

DPU/MCU Configuration . . . . . . . . . . . . . . . . . . . . . . . 17-6

Doors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

Adding a Door Extension . . . . . . . . . . . . . . . . . . . . . . . . 17-9Mode Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19User-defined Door Features . . . . . . . . . . . . . . . . . . . . . . . 17-22Sounder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-27Modifying a Door Extension . . . . . . . . . . . . . . . . . . . . . . 17-29Copying a Door Extension . . . . . . . . . . . . . . . . . . . . . . . 17-29Deleting a Door Extension . . . . . . . . . . . . . . . . . . . . . . . 17-30

Personnel Schedules and Shift Rotations . . . . . . . . . . . . . . . . 17-30

Personnel Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31Adding a Personnel Schedule . . . . . . . . . . . . . . . . . . . . 17-32Modifying a Personnel Schedule . . . . . . . . . . . . . . . . . . . 17-36Copying a Personnel Schedule . . . . . . . . . . . . . . . . . . . . 17-36Copy All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-37Deleting a Personnel Schedule . . . . . . . . . . . . . . . . . . . . 17-37

Shift Rotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38Adding a Shift Rotation . . . . . . . . . . . . . . . . . . . . . . . 17-38Modifying a Shift Rotation . . . . . . . . . . . . . . . . . . . . . 17-40Copying a Shift Rotation . . . . . . . . . . . . . . . . . . . . . . 17-40Deleting a Shift Rotation . . . . . . . . . . . . . . . . . . . . . . 17-41

Elevators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41

Adding an Elevator Extension . . . . . . . . . . . . . . . . . . . . . . 17-42Floors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-43

Key/Card Translations . . . . . . . . . . . . . . . . . . . . . . . . . 17-47

© 2001–2010 Schneider Electric. All rights reserved. xxiiiTCON299–05/10

Adding a Key/Card Translation . . . . . . . . . . . . . . . . . . . . . 17-48Modifying a Key/Card Translation . . . . . . . . . . . . . . . . . . . . 17-49Deleting a Key/Card Translation . . . . . . . . . . . . . . . . . . . . . 17-49

Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-50

Adding a New Tenant . . . . . . . . . . . . . . . . . . . . . . . . . . 17-51Modifying Tenant Parameters . . . . . . . . . . . . . . . . . . . . . . 17-53Copying Tenant Parameters . . . . . . . . . . . . . . . . . . . . . . . 17-53Deleting a Tenant . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55

Adding an Access Group . . . . . . . . . . . . . . . . . . . . . . . . 17-57Modifying an Access Group . . . . . . . . . . . . . . . . . . . . . . . 17-62Copying an Access Group . . . . . . . . . . . . . . . . . . . . . . . . 17-62Deleting an Access Group . . . . . . . . . . . . . . . . . . . . . . . . 17-63

Individuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63

Adding an Individual . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-78Field Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80Allocate Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-81Copying an Individual . . . . . . . . . . . . . . . . . . . . . . . . . 17-84Deleting an Individual . . . . . . . . . . . . . . . . . . . . . . . . . 17-85

PIN Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-86

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-87

Individual Activity Manager . . . . . . . . . . . . . . . . . . . . . . 17-92

Access Initiated Control. . . . . . . . . . . . . . . . . . . . . . . . . 17-94

Add Access Initiated Control . . . . . . . . . . . . . . . . . . . . . . 17-96Modifying Access Initiated Control . . . . . . . . . . . . . . . . . . . 17-101Copying Access Initiated Control. . . . . . . . . . . . . . . . . . . . 17-101Deleting Access Initiated Control. . . . . . . . . . . . . . . . . . . . 17-101

User Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-102

SCU Tamper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-103

SCU Tamper Summary . . . . . . . . . . . . . . . . . . . . . . . . 17-104

xxiv © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Editing Tamper Settings. . . . . . . . . . . . . . . . . . . . . . . . 17-104

Chapter 18 Intrusion Alarm SystemIntrusion Alarm System Configuration . . . . . . . . . . . . . . . . 18-2

System Sensor Selection . . . . . . . . . . . . . . . . . . . . . . . . 18-7

Adding a System Status Point . . . . . . . . . . . . . . . . . . . . . . 18-8Adding a Common Sensor . . . . . . . . . . . . . . . . . . . . . . . 18-8Delaying ARC Notification of EPS Fault Signals . . . . . . . . . . . . . . 18-8Overriding a Point’s Not-ready Condition. . . . . . . . . . . . . . . . . 18-9

IAS Access Level Setup . . . . . . . . . . . . . . . . . . . . . . . . . 18-10

Arming Terminal Configuration . . . . . . . . . . . . . . . . . . . . 18-11

Intrusion Alarm Zone Configuration . . . . . . . . . . . . . . . . . 18-14

Intrusion Alarm System Dial Parameters. . . . . . . . . . . . . . . . 18-17

Overriding a Point's Not-ready Condition . . . . . . . . . . . . . . . 18-20

Chapter 19 Override BillingBefore You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Override Billing Extension Editors . . . . . . . . . . . . . . . . . . . 19-3

Override Parameters . . . . . . . . . . . . . . . . . . . . . . . . 19-3Override Access Codes . . . . . . . . . . . . . . . . . . . . . . . 19-3Equipment Mapping . . . . . . . . . . . . . . . . . . . . . . . . 19-3

Entering Override Parameters . . . . . . . . . . . . . . . . . . . . . 19-3

Distribution Parameters . . . . . . . . . . . . . . . . . . . . . . 19-5End of Override Notice Parameters. . . . . . . . . . . . . . . . . . 19-6Equipment Points . . . . . . . . . . . . . . . . . . . . . . . . . 19-6

Adding Access Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6Adding Equipment Mapping . . . . . . . . . . . . . . . . . . . . . . 19-8

Chapter 20 7771 Industrial Controller InterfaceConfiguring the 7771 . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Points and Addressing . . . . . . . . . . . . . . . . . . . . . . . . . 20-3

© 2001–2010 Schneider Electric. All rights reserved. xxvTCON299–05/10

Chapter 21 Micro Regulator ControlConfiguring the Interface Controller . . . . . . . . . . . . . . . . . . 21-2

Creating the MR Database . . . . . . . . . . . . . . . . . . . . . . . 21-3

MR Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3

Configuring the Micro Regulators . . . . . . . . . . . . . . . . . . . . 21-4MR-Resident DDC . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Adding an MR-resident DDC Module . . . . . . . . . . . . . . . . 21-6Deleting an MR-resident Module . . . . . . . . . . . . . . . . . . 21-7Modifying an MR-resident DDC Module . . . . . . . . . . . . . . . 21-8Copying an MR-resident DDC Module . . . . . . . . . . . . . . . . 21-8

Standalone ATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9Hardware Coefficients . . . . . . . . . . . . . . . . . . . . . . . . . 21-9MR (I/STAT) Parameters . . . . . . . . . . . . . . . . . . . . . . . . 21-11

Button Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 21-12Inactivity Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . 21-13LED Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13

Chapter 22 Application Specific ControllersDisplaying ASC Data . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2

Modifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 22-3

Modifying ASC Names . . . . . . . . . . . . . . . . . . . . . . . . . 22-4

Copying ASC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 22-5

Saving and Restoring ASC Parameters . . . . . . . . . . . . . . . . . 22-6

Updating the Interface Controller . . . . . . . . . . . . . . . . . . . 22-7

Updating the ASC. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8

Chapter 23 I/SITE LCD PageDefining the I/SITE LCD Page . . . . . . . . . . . . . . . . . . . . . 23-1

Adding an LCD Page . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2Deleting an LCD Page. . . . . . . . . . . . . . . . . . . . . . . . . . 23-4Modifying an LCD Page. . . . . . . . . . . . . . . . . . . . . . . . . 23-4

xxvi © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

Copying an LCD Page . . . . . . . . . . . . . . . . . . . . . . . . . 23-5

Chapter 24 SevenTrendsSequence of Operations. . . . . . . . . . . . . . . . . . . . . . . . . 24-1

Configuring the DCU. . . . . . . . . . . . . . . . . . . . . . . . . . 24-1

Defining Trends and Cells . . . . . . . . . . . . . . . . . . . . . . . 24-3

Modifying Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7Modifying Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7Deleting Trends and Cells . . . . . . . . . . . . . . . . . . . . . . . . 24-8

Configuring the Host Station. . . . . . . . . . . . . . . . . . . . . . 24-9

Archiving SevenTrends Data . . . . . . . . . . . . . . . . . . . . . . 24-9

Performing Trend Archiving. . . . . . . . . . . . . . . . . . . . . . . 24-11

Managing SevenTrends Data . . . . . . . . . . . . . . . . . . . . . . 24-13

Dynamic Data Upload . . . . . . . . . . . . . . . . . . . . . . . . . 24-16

Index

© 2001–2010 Schneider Electric. All rights reserved. xxviiTCON299–05/10

C H A P T E R52

1

© 2001–2010 SchTCON299–05/10

TAC I/NET Seven Basics

About This Manual

This Operator Guide provides the step-by-step requirements for entering data and navigating through the TAC I/NET Seven program. For detailed information about theory of operation and programming the system refer to TCON300, TAC I/NET Seven Technical Reference Guide.

This operator guide follows a standard screen notation and style indicating keystrokes, cursor movement, navigation, and data entry specific to TAC I/NET Seven. TAC I/NET Seven software is intended to be used primarily with a mouse. However, you may use keyboard equivalents as indicated below.

File Names and Menu CommandsFile names appear in this manual as they appear on the screen of your computer. To further identify them as files, they appear as uppercase, italicized letters with any file extensions included. For instance, the configuration file used by your computer upon start up is shown as CONFIG.SYS.

Menu selections are shown in bold with initial capitalization as in Edit. A menu item with the arrow symbol () indicates another menu level.

KeystrokesKeystrokes are shown in bold surrounded by square brackets. For example, the Y key is shown as [Y], and the Enter key is shown as [Enter].

neider Electric. All rights reserved. 1-1

About This Manual TAC I/NET Seven Basics

Standard Keys

Certain standard keys are used within the TAC I/NET Seven program to perform certain system functions within editors, message boxes, etc. These are the [Enter], [Esc], [Tab], and Up and Down Arrow keys.

[Enter] Key

The [Enter] key is used to accept or activate a function, typically a highlighted button.

[Esc] Key

The [Esc] key is used to cancel an action or editor. You may use the [Esc] key to backup from successive levels of windows until you return to the main TAC I/NET Seven window.

[Tab] Key

The [Tab] key is used to cycle through the available active buttons or entry fields in an editor or screen.

Up/Down Arrows

The Up and Down Arrows can move the highlighted selection from one item to another in the various list, drop-down, and combo boxes found in the editors.

Selecting ItemsClick the left mouse button once to select an icon under the pointer, a menu selection on the menu bar, a button, a checkbox, or list item in an editor or dialog box.

You can also use the keyboard to select menu items or buttons on an editor or message box.

Menu Selection

Selecting a function from the menu bar can be done with the mouse or with the keyboard. When you select a menu item, the associated editor appears in a separate window, or a subordinate menu level drops down. You may then select another menu item from the subordinate menu.

1-2 © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

TAC I/NET Seven Basics About This Manual

When this manual provides a menu selection, the beginning and end of the path is shown. For instance, if you are to select the Seven-Trends definition function from the main menu, you would read the following text:

Select Edit Host Computer SevenTrends Definitions.

Using the Mouse

To select SevenTrends Definitions from the menu with a mouse, place the arrow on Edit and click once using the left mouse button. Select Host Computer, click once. Select SevenTrends and click once (a menu item with the symbol indicates another menu level is available). Select Definitions and click once (see Figure 1-1). The editor associated with the menu item appears.

Using the Keyboard

You may select a menu item from the menu bar by pressing [Alt] and then pressing the underlined letter of that item. For instance, to select Edit from the main menu, press [Alt], and then press [E]. To select an item from a subordinate menu level using keystrokes, simply type the initial letter of the item. If there are more than one menu items in a level with the same initial letter, pressing the letter again will select the next menu item with the same initial letter. Press [Enter] to open that editor.

Either method provides the same results, and they may be used interchangeably.

Figure 1-1. Menu Selection

© 2001–2010 Schneider Electric. All rights reserved. 1-3TCON299–05/10


Toolbar Selection

Many menus have a toolbar option, that allows you to display the menu selections as a series of buttons at the top of the screen. Clicking on the appropriate button produces the same effect as selecting the item from the menu.

Each command available on the toolbar is represented by a button. Each button has an icon (picture) on it, which relates to the corre-sponding menu command.

To determine which command is represented by a particular button, position the cursor over the button without clicking any mouse buttons. After a few seconds, a tooltip appears, giving the name of the command represented by the button.

When you are directed to select a menu option that has a corre-sponding toolbar button, a picture of the button is displayed in the left margin, as shown Figure 1-2.

Displaying Toolbars

To display a toolbar, select View Toolbars from the main menu, then select the desired toolbar from the menu. Active toolbars will have a check next to the toolbar name in this menu.

The toolbar appears in the toolbar section (gray area) at the top of the TAC I/NET Seven screen. Each toolbar will have a border around it.

To hide a toolbar, select the active (checked) toolbar from the View Toolbars menu.

Arranging Toolbars

The toolbar may be “docked” on any edge of the TAC I/NET Seven screen, or even placed as a separate toolbox in the main section of the TAC I/NET Seven screen. When you dock the toolbar on an

1. Select Connect.

Figure 1-2. Toolbar button and Equivalent Menu Option



edge of the screen, the toolbar area (gray shading) will automati-cally expand to allow room for all of the toolbars docked at that edge.

To move the toolbar, place the cursor in the area between the buttons and the border of the toolbar. Press and hold the mouse button, and drag the toolbar to the desired location. A dotted border shows the progress of the move. Release the mouse button to place the toolbar.

✦ Drag the toolbar into the middle of the TAC I/NET Seven screen to create a separate toolbar on the screen. This toolbar may be minimized into the taskbar if desired.

✦ Drag the toolbar to any edge of the TAC I/NET Seven screen to dock the toolbar on that edge.

✦ Drag the toolbar around the existing toolbar area to rearrange the open toolbars as desired.

As you move the toolbar, the dotted border changes shape to show the result of the move. For example, if you are moving the toolbar from the top to the side, the shape will change to a vertical rectangle to show the new orientation.

Depending on the location of the dotted border when you release the mouse button, the toolbar may adjust its position.

✦ The toolbar will automatically move up/down and left/right as necessary to sit squarely on the designated toolbar line.

✦ The direction of movement is determined by the location of the horizontal and vertical center of the toolbar; it will move in the direction that contains the majority of the toolbar.

✦ If you drag the toolbar on top of another toolbar, it will adjust its position to be next to the other toolbar — you cannot stack toolbars on top of one another. The direction of movement will depend on the relative positions of the toolbar centers (i.e., the toolbar whose center is to the left of the other toolbar’s center will end up on the left).

Highlighting an Item

To highlight an item, place the arrow on the item and click the left mouse button once. The text in any of the editable or selectable fields, or on a menu under the arrow will be highlighted.



If you want to use the keyboard after you have selected a list, drop-down, or combo box, you can select the items in it by pressing the up or down arrow on your keyboard. To select buttons in an editor you may do so by pressing the [Tab] key. Each time you press [Tab] the next button will be selected. A selected button has a slightly heavier outline around it. To activate the button or item from a list, press [Enter].

Entering Data

Entering data depends upon the type of data entry box. Edit fields and combo boxes allow you to select the field and enter or replace text with what you type. Refer to “Screen Display” below for a description of the various data display and entry methods.

Screen DisplayAt the bottom of the main TAC I/NET Seven window is a status bar that displays system information. This information includes the connection path, the current operator initials and the host time and date (see Figure 1-3).

The connection path displays, from left to right, the number of the host, the initials of the signed-on operator in parentheses, and the connected link. Any subsequent automatic or manual connections to links, LANs, or controllers are also displayed by device name, address, and assigned name on this line. Points are displayed by point address and assigned name on this line.

At the bottom of every editor is a static text field that displays a basic message prompting you to enter or select items pertaining to the selected field. Figure 1-4 shows the Door Editor prompting you to enter a value of 8 or 9 for the door address.

Figure 1-3. Screen Display



Grayed Out Selections

On occasion you will encounter menu selections or buttons that are grayed out instead of being displayed in their normal colors. This indicates that the selection is not valid for this particular situ-ation. Sometimes, selecting an item in an editor will cause a grayed out item to become valid. You may then select the item.

Screens

Context-sensitive, online help is available. Click the Help button, usually located at the bottom, right corner of the window or dialog box. This will access information specific to the editor or dialog box.

Text Fields and Spindials

A static text field is a box containing text from the TAC I/NET Seven system that you cannot directly edit (see Figure 1-5).

The information displayed may also be associated with a spindial as shown in Figure 1-6. In this case there is more than one item that may be displayed. A static text field with a spindial allows you to select an option or value. Place the pointer over the up or down arrow and click once to display a different value or option. The item displayed will be selected when you click OK.

Figure 1-4. Door Editor Prompt

Figure 1-5. Static Text Field



Edit Fields

Edit fields are boxes within a dialog or editor box that require you to enter text. An example of this is shown in Figure 1-7, where the Host Password editor contains an edit field allowing you to search for a user name.

An edit field may also be associated with a spindial. In that case you may either use the spindial to set the value, or type it in directly (see Figure 1-8).

Buttons and Checkboxes

Buttons, radio buttons, and checkboxes let you select functions or options in the editors and message boxes. Position your arrow cursor over the button or checkbox and click once.

Buttons

Buttons generally perform either a system function or a program function when clicked. An example of system buttons are the OK and Cancel buttons (see Figure 1-9).

Figure 1-6. Static Text Field with Spindial

Figure 1-7. Edit Field

Figure 1-8. Edit Field with spindial

Figure 1-9. System Buttons



Program functions can either be confined to a single editor, or repeated in several editors. Figure 1-10 shows the Add, Delete, and Copy buttons. These buttons are repeated in several editors.

Radio Buttons

A radio button is a button in a series. Only one of the buttons may be chosen or activated at a time. When you place your pointer over a deactivated radio button and click on it, the previous radio button automatically deactivates and the new button is activates. Figure 1-11 shows a typical series of radio buttons.

Checkboxes

A checkbox shows whether an item is active or not. When it is acti-vated, a checkmark appears in the box (see Figure 1-12). More than

one checkbox can be active in a group, as in a message mask, shown in Figure 1-13 .

Figure 1-10. Program Buttons

Figure 1-11. Radio Buttons

Figure 1-12. Checkbox

Figure 1-13. Message Mask Checkbox



Message Boxes

The message box presents a message or a request for confirmation of an action. The message could be a warning that a procedure or connection could not be completed, a caution that completing the action will change system values or data, or information about what is happening. In all cases, in order for you to proceed, you must select a button in the message box. The button will either be a Yes or a No, or some variation. (see Figure 1-14).

List Boxes

The list box contains a list of items you can select. List boxes can be fixed-width (i.e., the column width is set) or adjustable-width (i.e., you can change the width of the columns). Both types of list boxes will display a scroll bar on the right-hand side if the number of items is greater than can be displayed in the list box.

Fixed Width

In a fixed-width list box, the data is presented in columns, with no grid lines. The columns are static text fields for you to select an option: you cannot change the data. Position the pointer on the up or down arrows and click to move the list one line in that direction. You can also drag the scroll bar, or click in the scroll bar area to move the list. (see Figure 1-15).

Adjustable Width

In an adjustable-width box, the data is presented in a table, with grid lines (see Figure 1-16). The first column is always a static text field, that you cannot change. Subsequent columns may be editable or static, depending on the displayed screen.

Figure 1-14. Message Box



Figure 1-15. Fixed-width List Box

Figure 1-16. Adjustable-width List Box



To adjust the width of a column:

1. Place your cursor on the line at the RIGHT edge of the field title for the column you wish to resize. the cursor will change to show a double-headed arrow (see Figure 1-17).

In the example above, the Field Name field width is being adjusted. To adjust the width of the Value field, the cursor would have to be at the right edge of that field.

2. Click and hold the mouse button.

3. Move the cursor to change the location of the right edge of the selected column. A faint line follows the cursor movement, displaying the column width that will result.

✧ If you move the cursor to the left, the column will get narrower.

✧ If you move the cursor to the right, the column will get wider.

4. Release the mouse button to change the column width.

Drop-down Boxes

Drop-down boxes can consist of either a list box or a combo box. The combo box allows you to enter text as well as select from the items listed in the box.

To display the contents of the box position the pointer on the down arrow located on the right of the box and click. Choose an item from the list by placing the pointer over it and clicking, or by typing a new item into the box (see Figure 1-18).

Figure 1-17. Resizing a Column

Cursor


TAC I/NET Seven Basics Starting TAC I/NET Seven

Starting TAC I/NET Seven

Refer to TCON298, TAC I/NET Seven Getting Started, for informa-tion on installing and configuring TAC I/NET Seven. After you have completed the initial configuration, use the following proce-dure to launch TAC I/NET Seven.

1. Select the Windows Start menu.

2. Select Programs I/NET. The resulting menu is shown in Figure 1-19. You will see several options in the menu.

Figure 1-18. Drop-Down Box

Figure 1-19. Starting TAC I/NET Seven


Starting TAC I/NET Seven TAC I/NET Seven Basics

3. Select I/NET. As TAC I/NET Seven launches, a balloon-style message at the task bar informs you that the I/O Server is starting the SQL service.

4. The TAC I/NET Seven program then starts and the Log On Dialog box appears. Log onto TAC I/NET Seven as follows:

a. If your Windows user account has already been added to TAC I/NET Seven's passwords, you can activate () the Current Windows User checkbox. In this case, you can jump to Step d below. Refer to “Configuring I/NET Seven to Accept a User's Windows Logon” on page 1-35 for instructions on adding Windows user accounts to TAC I/NET Seven’s passwords.

b. Type your Operator Name. This name can contain up to 30 characters. The following characters cannot be used within the Operator Name: " / \ [ ] : ; | = , + * ? < >

c. Enter your password in the Host password field and click OK. This password can contain up to 127 charac-ters. All keyboard characters are valid for use within this password.

Figure 1-20. Starting the SQL Service

Figure 1-21. Log On Prompt


TAC I/NET Seven Basics Connecting to the System

The default system password is “DACS.” If the system has just been installed and no other host passwords have been assigned, this default password should still be avail-able. After host passwords have been assigned to all authorized users, you may wish to remove the default password to prevent unauthorized users from gaining access.

The system displays an asterisk for each character you type.

d. Select OK to continue.

Note: You can configure TAC I/NET Seven to allow operators to logon simply by swiping their key/card at a Weigand reader connected directly to the host workstation’s RS232 port. Refer to “Peripherals” in the TAC I/NET Seven Configuration chapter of TCON298, TAC I/NET Seven Getting Started, for more information.

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

When you’re ready to log off, select System Log Off from the main menu. TAC I/NET Seven can also automatically log you off the system. If the Operator Timeout setting is greater than zero and the Operator Timeout Action is set to Signoff or Both, automatic log off will occur if the system times out. Refer to “Host Configu-ration” on page 2-2 for more information about these options.

Connecting to the System

To access any part of the TAC I/NET Seven system, you have to connect through links and Taps to controllers. Depending on your configuration and system level, you may see different options presented in the Connect dialog box.


Connecting to the System TAC I/NET Seven Basics

1. After logging on, select Connect from the main menu. The system displays the Connect summary (see Figure 1-22).

When you first select Connect from the TAC I/NET Seven main menu, the connection process displays a list of up to 100 Links. A Link address (0–99) and Link name is displayed for each item in the list.

Each link can represent either a physical hardware device (i.e., a Tap or an NPR) or a distributed link (i.e., a collection of up to 64 NPRs that share the same link address). Distributed links can be recognized as such by their name. For each distributed link. the list displays the generic name “DLA Link #”, followed by the link number, (for example, “DLA Link #28”). Refer to the System Configuration chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for a complete description of “Link Support” within TAC I/NET Seven.

2. Highlight a link in the list box and select OK to connect to the link.

Figure 1-22. Connect Summary


TAC I/NET Seven Basics Connecting to the System

3. To connect to the next level in the network, click Connect again. If the link connects directly to a controller LAN, a listing of available controllers, similar to that shown in Figure 1-23, displays.

4. Highlight a controller in the list box and select OK to connect to the controller.

Note: Depending upon your network, you may have to connect to a Site, before you can connect to a specific controller. Simply select the Site, click OK and then click Connect again to display the list of available controllers.

DisconnectingWhen you exit TAC I/NET Seven you will automatically be discon-nected from any controller. However, you may want to disconnect from a controller without exiting the TAC I/NET Seven software. To do so:

1. Select Disconnect from the menu, or click the Disconnect tool on the toolbar.

2. You will have to disconnect from each level in the network. For example, suppose you are connected to a controller on link 10 and you want to connect to a controller on link 12.

Figure 1-23. Connect — Controller Summary


Exiting TAC I/NET Seven TAC I/NET Seven Basics

You would disconnect once from the controller, and then disconnect again from link 10. At that point you can connect to link 12.

Exiting TAC I/NET Seven

You can end your TAC I/NET Seven session by selecting System Exit from the main menu, or by clicking on the button in the upper right corner of the TAC I/NET Seven window. Refer to “Starting TAC I/NET Seven” on page 1-13 for more information.

Note: If you do not log off the system is not secure from unauthorized use.

System Addresses

Each individual input and output point, controller, Tap, operator station, and backup station has a unique number that identifies it in the system. These identification numbers are called system addresses. Each address is built using the address of the equipment passed through to reach it.

Building an AddressAn address in the TAC I/NET Seven system consists of a series of numbers, each describing the route from the top of the LAN hier-archy to the final device or input/output point (see Figure 1-24).

This addressing structure consists of four pairs of numbers:

Figure 1-24. Addressing Structure

LL SS PP BB

Link 00–99 Bit Offset 00–09 (00–07 for UCs)

Point 00–31Station 00–63


TAC I/NET Seven Basics System Addresses

✦ The link number (00–99) is the System Link address that the operator connects through to connect to a specific controller LAN.

✦ The station number (00–63) is the controller on that controller LAN.

✦ Every controller provides 32 point address numbers (00–31), each with ten bit offset numbers (00–09).

✦ SubLAN interfaces and their microcontrollers provide addresses as follows:

✧ The UCI provides point addresses 00 through 31 for up to 32 UCs on a subLAN. Each UC provides eight input and eight output bit offset addresses (00–07).

✧ The DPI provides point addresses 00 through 31 for up to 32 devices (DPUs or SCUs) on a subLAN. Each device on the subLAN provides ten input and ten output bit offset addresses (00–09).

✧ The MRI provides point addresses 00 through 31 for up to 32 MRs on two subLANs. Each MR provides ten input and ten output bit offset addresses (00–09).

✧ The MCI provides point addresses 00 through 31 for up to 32 devices (MRs, DPUs, and SCUs) on two subLANs. Each device on the subLAN provides ten input and ten output bit offset addresses (00–09).

✧ The 7798 I/SITE LAN and 7798C provide point addresses 00 through 31 for up to 32 devices (MRs, DPUs, DIOs, DIUs, and SCUs) on a subLAN. Each device on the subLAN provides ten input and ten output bit offset addresses (00–09).

Creating a Controller Address

To connect to a discrete input point on a 7740 with the system address 07222804, perform the following steps:

1. Connect to link 07 which connects you to the controller LAN.

2. Select controller #22.

3. Select discrete input point 28.

4. Select bit offset 04.


Forms and Worksheets TAC I/NET Seven Basics

Creating a UC, DPU, SCU, or MR Address

Connecting to a UC, DPU, SCU, or MR is similar to the procedure just described. To connect to a UC, DPU, SCU, or MR point with the system address of 07230607, perform the following steps:

1. Select link Tap 07 which connects you to the controller LAN.

2. Select UCI, DPI, MRI, or I/SITE LAN 23 on that controller LAN to connect to the interface unit.

3. Select UC, DPU, SCU, or MR 06 on that interface unit to connect to the controller.

4. Select point 07 on that controller.

The type of point, input or output, depends on how you defined the point. Refer to the chapter concerning input and output points in TCON300, TAC I/NET Seven Technical Reference Guide, or to the specific user or installation guides accompanying the controllers in your system.

Forms and Worksheets

There is no substitution for thorough planning and record keeping in the development and maintenance of your TAC I/NET Seven system. We recommend that you use the forms located in TCON157, TAC I/NET Forms and Worksheets Getting Started, to document your system configuration. These forms are referred to frequently throughout this manual. Make extra copies of the forms to use as worksheets when planning your database (be sure to keep an original form for making copies). Once you fill out the forms, creating the database becomes a simple data entry task. The care and attention to detail taken as you prepare your database entry forms translates directly to how easily you can bring your system on-line.


TAC I/NET Seven Basics Backups

Backups

Note: The DbCreate utility allows you to create a backup of your TAC I/NET Seven SQL database. However, it does not backup the entire contents of your TAC I/NET Seven directory (i.e., graphic pages, library symbols, DCU save files, etc.). Use the information in this section to define a backup methodology appropriate for your system.

Refer to the TAC I/NET Forms and Worksheets Getting Started guide for more information about the DbCreate utility.

Many things can happen to computerized data. A disk can fail, files may be accidentally deleted or become corrupted, or you can lose a machine due to theft, fire or flood. All TAC I/NET Seven users should backup data and configuration files on a regular basis. You should also consider testing your backup methods by staging a mock recovery to make sure that everything works as you expected.

In order to define your backup methodology you must make deci-sions on the value of your data, the backup media, the backup storage location, the frequency of backups and the tools to use. These issues apply, not only to TAC I/NET Seven data, but also to any computerized data you maintain.

✦ Data value — You must determine what the value of your TAC I/NET Seven data is to you. This will vary between customers. If your TAC I/NET Seven system is managing a high security facility the loss of the TAC I/NET Seven system data may be much more serious than if you are managing a small office building. To determine the value of your TAC I/NET Seven data consider the worst case scenario—the loss of the entire host machine. Would this merely be a minor inconvenience or a major disaster?

✦ Media — There are many options in backup media. The most basic is a simple floppy disk. You can also add a special backup device (such as a Zip or Jaz drive) to your system. These devices allow you to store a greater quantity of data than a regular floppy and are relatively inexpensive. Other options include saving backups on a network drive or using an Internet backup service.


Backups TAC I/NET Seven Basics

✦ Storage — A recommended practice for valuable data is to store the backup data in a different location. This protects the backup data from disasters such as flood or fire. To minimize the inconvenience of going offsite for data retrieval you can keep a copy of your most recent backup locally and store the previous backups in an alternative location.

✦ Tools — There are numerous tools to assist you in backing up your files. Backups can be performed simply by copying files to the chosen media. Also, utility programs that compress your data may be used for backup purposes. Microsoft includes a special backup program with Windows and NT systems. Alternatively, many other vendors offer backup utili-ties for sale. Many of the backup utilities can be configured to perform the backup at regular intervals without your inter-vention. Evaluate your options and then choose the tool that is most appropriate for your needs.

✦ Frequency — The frequency with which you perform backups should depend upon how often you expect the data to change and how valuable that data is to you. Irreplaceable data that changes regularly should be backed up on a daily basis. At a minimum you should backup your data weekly. You should also perform special backups prior to any system configuration changes.

Table 1-1 lists the TAC I/NET Seven files that you should consider for inclusion in your backup routine. Devise a backup method-ology that is suitable for your environment and implement it for all TAC I/NET Seven host PCs.


TAC I/NET Seven Basics Controlling Window Layouts in TAC I/NET Seven

Controlling Window Layouts in TAC I/NET Seven

TAC I/NET Seven allows you to assign window control functions to each user's password. These functions control a user's ability to close, move, or size windows. Refer to the description of “Host Passwords” in the Host Functions chapter of the TAC I/NET Seven Technical Reference Guide for more information.

As the administrator of a TAC I/NET Seven system, you can take advantage of these window control functions in order to define unique window layout schemes for particular TAC I/NET Seven operators.

For example, you may have a TAC I/NET Seven operator who must monitor AMT alarms and events. As the administrator of the TAC I/NET Seven system, you can define the window layout for this user as follows:

1. Log into TAC I/NET Seven using this user's logon and pass-word.

2. Open the Host Password Assignment editor (see Figure 9-2 on page 9-3) and ensure that the window control functions are enabled for this user.

Table 1-1. Recommended Files for Backup

Function File(s) to Backup

Host PC configurationINET\INETIOSRV*.DATINET\HOSTMASKS*.DAT

TAC I/NET Seven database Microsoft SQL Server\MSSQL\DATA\INETDB*.*

AMT Archives INET\ARCH\ARC_*.MDF

Graphic System PagesINET\DATA\*.PAG (I/NET 4.3 pages)INET\DATA\*.GPGINET\DATA\HOMEPAGE

Graphic Library SymbolsINET\SYMBOLS\*.BOL (I/NET 4.3 Symbols)INET\SYMBOLS\*.GLSINET\SYMBOLS\*.BMP

DCU Save Files INET\SAV\*.SAV

Note: The default paths are shown for the data files. Depending on your system configuration, the specific data path may be different.


Retrieving Obstructed Windows TAC I/NET Seven Basics

3. Close the Host Password Assignment editor and open the appropriate windows for use by this operator. For this example you would open an AMT alarm window and event window.

4. Position the windows on the screen as necessary.

5. Return to the Host Password Assignment editor and de-select the appropriate window control functions for this user. For this example you may wish to de-select the following func-tions:

✧ Allow AMT Alarm wnd. close

✧ Allow AMT Alarm wnd. move and size

✧ Allow AMT Event wnd. close

✧ Allow AMT Event wnd. move and size

6. Log out of TAC I/NET Seven.

Now when the user logs onto TAC I/NET Seven, AMT will open with the alarm and event windows positioned accordingly. The position of these windows will be fixed (i.e., the user will not be able to close, move, or size these windows).

TAC I/NET Seven and AMT save window position information during log-off and program shutdown. Therefore, if you do not disable the user’s ability to close windows, any windows that are closed when the user logs off or shuts down the system will not automatically come up the next time the user logs on.

Retrieving Obstructed Windows

TAC I/NET Seven allows you to have multiple graphic pages open at the same time. You can also have the System View window open while graphic pages are being displayed. Occasionally, a window may become obstructed by other open windows. In order to bring an obstructed window to the foreground, you could use the stan-dard Windows keyboard convention of [Ctrl]+[Tab] to cycle through the open windows until the obstructed window activates. However, TAC I/NET Seven provides an alternative method that allows you to activate a window without cycling through all open


TAC I/NET Seven Basics Creating User-defined Tools and Buttons

windows. Using the Open Graphic Pages dialog box, you can view a list of TAC I/NET Seven’s open windows and activate any window directly.

1. Select Window Windows from the main menu. The system displays the Open Graphic Pages dialog box (see Figure 1-25).

2. Highlight an entry in the list of open windows.

3. Click the Select button to bring the selected window to the foreground.

4. Select Close to close the dialog box.

Note: The Open Graphic Pages dialog always remains in front of any other TAC I/NET Seven windows that are open, until you close the dialog box.

Creating User-defined Tools and Buttons

TAC I/NET Seven now provides you with the ability to create custom tools. These tools can be used to initiate event sequences defined in your system’s controllers, or to launch external files and applications on your host workstation.

Figure 1-25. Open Graphic Pages


Creating User-defined Tools and Buttons TAC I/NET Seven Basics

You can activate user-defined tools from TAC I/NET Seven’s main menu, or from tool markers placed on graphic pages. The number of tools you can create is limited only by the amount of resources (i.e., memory and hard drive space) available on your workstation.

Configuring User ToolsCreate custom tools using the following steps:

1. Select Tools Define Tools from the main menu. The system displays the User Tool Configuration editor (see Figure 1-26).

2. Create a new user tool by selecting Add. The system displays a dialog box allowing you to define a name and choose a tool type for the new tool (see Figure 1-27).

a. Define a Name for the new user tool. Use up to 50 char-acters.

Figure 1-26. User Tool Configuration Editor

Figure 1-27. Creating a User Tool



b. Choose the type of tool you wish to create. Two kinds of tools are available:

✢ Event – Use this tool type to execute an event sequence defined in a controller.

✢ Shortcut – Use this tool type to launch another application, open a file, visit a web site, etc.

3. Select OK to accept these settings.

4. Use the steps below that are appropriate for the type of tool you are creating:

Creating an Event ToolIf you chose the Event tool type in Step 2 above, TAC I/NET Seven displays the Event Selection dialog (see Figure 1-28). Use this dialog to specify one or more event sequences to be executed by the user tool.

Figure 1-28. Event Selection Dialog Box



The Event Selection dialog is divided into three sections as follows:

✧ Link Selection – This section provides a drop-down list of all link devices defined in your system.

✧ Station Selection – This section provides a list of all stations that communicate through the link device selected in the Link Selection section.

✧ Event Selection – This section lists all event sequences defined for the station selected in the Station Selection section.

Select event sequences as follows:

a. Select a link in the Link Selection section.

b. Highlight a station in the Station Selection section.

c. Use the Event Selection section to assign event sequences to the user tool as follows:

✢ Highlight an event sequence in the left-hand list and use the right-arrow button (-->) to add the sequence to the list on the right.

✢ If necessary, continue adding event sequences to the list on the right. When the user tool is activated, it will execute its event sequences in the order that they appear in the right-hand list.

✢ Remove an event sequence from the user tool by highlighting the sequence in the right-hand list and clicking the left-arrow button (<--) to remove it.

d. Select OK to accept these settings and close the Event Selection dialog. Proceed to Step 5.

Creating a Shortcut ToolIf you chose the Shortcut tool type in Step 2, TAC I/NET Seven displays a file selection dialog (see Figure 1-29). Use this dialog to choose the file or application to be launched by the tool.



Specify the name of the file or application to assign to the user tool and select Open. The file selection dialog box closes. Proceed to the next step.

5. The newly created tool now appears in the list of tools contained in the User Tool Configuration editor (see Figure 1-26 on page 1-26).

Select OK to close this editor.

You can use the tool(s) that you just created by performing either of the following tasks:

✦ Create Tool Markers – You can assign tools to tool markers that you place on graphic pages. When you click on a tool marker on a live graphic page, the tool activates. Refer to “Adding Tool Markers” on page 8-71 for instructions.

✦ Create User Buttons – You can assign tools to user-defined buttons that become available from TAC I/NET Seven’s main menu. Instructions for performing this task are provided below.

Configuring User ButtonsCreate up to 16 user-defined buttons as follows:

1. Select Tools Define Buttons from the main menu. The system displays the User Button Configuration editor (see Figure 1-30).

Figure 1-29. File Selection Dialog Box



2. Highlight one of the 16 entries from the scrollable list. You can modify an existing button, or any blank button.

3. Select Modify. The system displays the User Tool Configura-tion editor (see Figure 1-26).

4. Highlight the tool that you wish to assign to the user-defined button. If you need to create a new tool, you can do so now (refer to “Configuring User Tools” on page 1-26 for instruc-tions).

5. Select OK to accept the highlighted tool and to close the User Tool Configuration editor.

6. The name of the tool that you selected is now displayed in the highlighted entry in the User Button Configuration editor. Select OK to accept this setting.

The user-defined button that you just created is now available from TAC I/NET Seven’s main menu. Select Tools from the main menu to display the available user-defined buttons (see Figure 1-31 for an example).

You can activate a tool by selecting its button in the Tools menu. Any buttons that appear gray have not been configured and cannot be selected.

Figure 1-30. User Button Configuration Editor


TAC I/NET Seven Basics Using the System View Interface

Using the System View Interface

This version of TAC I/NET Seven provides an alternate user inter-face that you can use to setup your network configuration, and to configure your access control system. Rather than using standard menu commands, you can instead use a tree-based interface by selecting View System View from the main TAC I/NET Seven menu.

See Also: “Using System View to Configure Your Network” on page 2-6

The System View WindowWhen you launch System View, it is displayed as a double-pane window (see Figure 1-32). This window is non-modal, meaning that you can open other windows and editors while the System View window is open.

The Left-side Pane

The left-side pane contains a hierarchical tree that represents the structure of your system. Along the bottom of the left-side pane is an Access tab and a Netcon tab. By default, the Access tab is active, causing the main area of the left-side pane to display a list of

Figure 1-31. Tools Menu


Using the System View Interface TAC I/NET Seven Basics

the tenants defined in your access control system. This list contains an “All Tenants” entry as well as an entry for each tenant that you have already defined (if any).

If you select the Netcon tab, the access control information in the left-side pane is replaced with network configuration information.

The Right-side Pane

The right-side pane provides a Context tab and a System tab. By default, the Context tab is active, allowing the pane to display information about items you highlight in the left-side pane.

You can use the System tab to duplicate the functionality of the left-side pane in the right-side pane. This is especially useful when you wish to drag items from one pane and drop them into the other pane (refer to “Using Drag and Drop” on page 1-33).

Expanding and Collapsing ItemsYou can expand an item by clicking its plus (+) symbol (see Figure 1-33). This causes subordinate items to display, indented beneath the expanded item. Subordinate items may also have a plus symbol, indicating that they too can be expanded. After expanding an item, the plus sign changes to a minus (–) sign. Click the minus sign to collapse the expanded item.

Figure 1-32. Initial System View Display


TAC I/NET Seven Basics Using the System View Interface

Using Drag and DropOne benefit to using the System View interface is that you can drag and drop items from the right-hand pane to items in the left-hand pane. For example, you could drag a Group from the right pane to an individual in the left in order to assign that group to the indi-vidual.

Displaying a Context-sensitive Popup MenuBy clicking with the right mouse button, you can display a popup menu of available functions. This popup menu is context sensitive, meaning that it can display functions that are only applicable to a selected item, as well as functions that are common among all items. When you right-click a blank area, the popup menu shows functions that are applicable to the System View window.

Print and Print PreviewAt any time you can print the entire contents of the left-side pane by right-clicking anywhere in the pane and selecting Print from the resulting context menu. Only the items that are currently displayed

Figure 1-33. Expanding Items in System View


Using the System View Interface TAC I/NET Seven Basics

in the pane will be included in the printed output. Therefore, no subordinate information for collapsed items will be included in the printed output.

You can display a preview of the printed output by right-clicking anywhere in the pane and selecting Print Preview from the resulting context menu. Using the preview window, you can switch between a one-page and two-page display, navigate from one page to another, zoom in and out, and send the output to a printer.


TAC I/NET Seven Basics Using Your Windows Login with TAC I/NET Seven

Using Your Windows Login with TAC I/NET Seven

In addition to the traditional method of logging onto TAC I/NET Seven (that is, entering an operator name and host password), you can configure TAC I/NET Seven to automatically log you in based on your Window's logon.

Configuring I/NET Seven to Accept a User's Windows Logon

Note: The following steps can only be performed by a TAC I/NET Seven operator with password access rights.

To add a user's Windows account to TAC I/NET Seven1. Select Edit Host Computer Passwords from TAC I/NET

Seven's main menu to open the Host Password editor.

2. Select Add to open the Host Passwords Assignments editor.

3. In the Name field, use up to 30 characters to define the user's Windows account name. Use the following syntax for this field:

machine_name\user_name

—OR—

domain_name\user_name

The entry you make in the Name field must exactly match the user's Windows account name. The following characters cannot be used within the name: " / [ ] : ; | = , + * ? < >. You must also avoid using the @ symbol if you intend to use this account as the source of indirect user settings (refer to “Indi-rect User Settings” on page 9-13 for more information).

4. The Password and Confirmation fields become inactive and are not used for this type of account. Skip these fields.

5. Continue filling in the other fields and assigning functions to the account. If necessary, refer to the “Adding a Host Pass-word” on page 9-2 for instructions.


Auto-launching TAC I/NET Seven at Startup TAC I/NET Seven Basics

Logging In Using Your Windows AccountIf your Windows account has already been added to TAC I/NET Seven, you can use it to log onto TAC I/NET Seven.

To log in using your Windows account1. From the Log On dialog, activate () the Current Windows

User checkbox.

2. Select OK to log onto TAC I/NET Seven.

Auto-launching TAC I/NET Seven at Startup

By placing a TAC I/NET Seven shortcut in the Windows Startup folder, you can configure your system to automatically launch TAC I/NET Seven each time Windows starts. The instructions for this type of configuration are described below.

To configure Windows to auto-launch TAC I/NET Seven1. Open the Startup folder.

For example, open:

C:\Documents and Settings\your_username\Start Menu\Programs\Startup

To have TAC I/NET Seven automatically launch for all users of this PC, open the “All users” Startup folder.

For example, open:

C:\Documents and Settings\All Users\Start Menu\Programs\Startup

2. In the Startup folder, create a shortcut to TAC I/NET Seven as follows:

a. Right-click a blank area in the Startup folder and select New Shortcut from the resulting popup menu. This will launch a wizard that will help you to create the new shortcut.

b. Follow the wizard's onscreen instructions to create a shortcut to TAC I/NET Seven's main program file (INetW.exe).

For example:


TAC I/NET Seven Basics Auto-launching TAC I/NET Seven at Startup

C:\Program Files\INET Seven\INetW.exe

With a shortcut to TAC I/NET Seven now in the Startup folder, TAC I/NET Seven will automatically launch each time you start Windows.

Bypassing TAC I/NET Seven's Logon Dialog

You may wish for the auto-launched TAC I/NET Seven system to automatically log you in without displaying the logon dialog. TAC I/NET Seven accepts a command line switch that instructs it to bypass the logon dialog and automatically logon the current Windows user.

Use the following instructions to add a command line switch to the TAC I/NET Seven shortcut that you created in the Startup folder.

1. Ensure that you have configured TAC I/NET Seven to use Windows logons. Refer to “Configuring I/NET Seven to Accept a User's Windows Logon” on page 1-35 for instruc-tions.

2. Locate the TAC I/NET Seven shortcut that you created in the Startup folder.

3. Right-click the shortcut and select Properties from the resulting popup menu.

4. In the Target field, add a space and /winuser to the end of the existing text.

For example:

"C:\Program Files\INET Seven\INetW.exe" /winuser

5. Click OK to close the shortcut's property window.

Now when TAC I/NET Seven auto-launches, it will automatically logon the current user if their Windows user account has been added to TAC I/NET Seven. If the current user's Windows account has not been added to TAC I/NET Seven, the normal logon dialog will open when TAC I/NET Seven launches.

Refer to “Configuring I/NET Seven to Accept a User's Windows Logon” on page 1-35 for instructions on adding Windows user accounts to TAC I/NET Seven.


Running I/O Server as a Windows Service TAC I/NET Seven Basics

Running I/O Server as a Windows Service

Note: You must have Windows system administrator rights in order to perform the procedures described in this section.

A Windows “service” is an application that loads automatically at Windows startup and runs as a constant background task. TAC I/NET Seven’s I/O Server can be configured to run as a Windows service.

Why Run I/O Server as a Windows Service?By running I/O Server as a service on your local PC, you can help ensure that client TAC I/NET Seven workstations will successfully maintain communications with TAC I/NET Seven on this PC.

Running I/O Server as a service is especially useful for the following applications:

✦ Using the PC as a TAC I/NET Seven database server for other PCs configured as Remote Clients.

✦ Using the PC as a Filemaster for other PCs configured as Equalized Clients.

Refer to Chapter 3 in TCON298, TAC I/NET Seven Getting Started, for more information about using file equalization and using a client/server configuration.

Before You BeginBefore you configure I/O Server to run as a Windows service, you should first set it to run continuously – even during periods when no clients are connected.

To configure I/O Server to run continuously1. Launch TAC I/NET Seven’s Configure program by clicking the

Windows Start button and then selecting Programs INET INET Configuration.


TAC I/NET Seven Basics Running I/O Server as a Windows Service

2. Open the Configuration Profile editor to modify TAC I/NET Seven’s active profile. If necessary, refer to TCON298, TAC I/NET Seven Getting Started, for instructions on how to modify a profile.

3. In the Configuration Profile editor, set the I/O Server with no clients parameter to “Maintain”.

4. Click OK to close the Configuration Profile editor.

5. Click Close to close the Configure program.

6. Ensure that both TAC I/NET Seven and I/O Server are shut-down.

Configuring I/O Server to be a Windows ServiceTo configure I/O Server to run as a service

1. Click the Windows Start button and then click Run....

2. In the Run dialog box, type cmd and click OK.

3. In the resulting command window, navigate to the I/NET Seven directory as follows:

a. Type cd %PROGRAMFILES%\Inet Seven



b. Press the Enter key

4. In the command window, unregister I/O Server as follows:

a. Type inetiosrv /unregserver


5. In the command window, set TAC I/NET Seven’s I/O Server to run as a Windows service as follows:

a. Type inetiosrv /service




To start the I/O Server service1. Click the Windows Start button, right-click My Computer

and select Manage from the resulting popup menu.

2. In the left-hand panel of the Computer Management window, expand the “Services and Applications” section and highlight Services.

3. In the right-hand panel, scroll down and locate the INet7IoSrv service, right-click it, and select Properties from the resulting popup menu.

4. In the Properties editor, perform the following tasks:

a. Verify that the Startup Type parameter is set to “Auto-matic”.



b. Start the service by clicking the Start button.

c. Click OK to close the Properties editor.

5. Close the Computer Management window.

6. Close the command window.

7. Verify TAC I/NET Seven’s I/O Server is running by locating its icon in the Windows system tray.

The actual icon used to represent IO Server will depend on how your system is configured. Refer to Chapter 3 in TCON298, TAC I/NET Seven Getting Started, for more infor-mation about IO Server icons.

8. Reboot the computer.

9. Upon returning to Windows, locate I/O Server’s icon in the system tray to verify that it has started automatically.



Configuring I/O Server to Stop Being a Windows ServiceIf you decide that you no longer wish to run I/O Server as a Windows service, you can reconfigure it to run as a normal appli-cation. The procedures for this type of reconfiguration are described below.

To configure I/O Server to stop running as a service1. Click the Windows Start button and then click Run....





4. In the command window, unregister I/O Server as follows:

a. Type inetiosrv /unregserver




5. In the command window, set TAC I/NET Seven’s I/O Server to run as a normal Windows application as follows:

a. Type inetiosrv /regserver

b. Press the Enter key.

Verify that I/O Server is no longer a Windows service1. Click the Windows Start button, right-click My Computer



3. In the right-hand panel, scroll down and verify that INet7IoSrv is no longer included in the list of services.





TAC I/NET Seven Basics Manually Shutting Down IO Server

Manually Shutting Down IO Server

Depending on how IO Server is configured to run on your system, it may not automatically shutdown when you exit TAC I/NET Seven. For example, IO Server may be configured as a service that runs for as long as Windows is running.

If IO Server is not configured to automatically showdown, there are three ways of shutting it down manually:

✦ Stop the INet7IoSrv service from Windows Services.

✦ Stop the I/NET IO Server application from the Windows system tray.

✦ Stop the INet7IoSrv.exe process from the Windows Task Manager.

Each of these methods for manually shutting down IO Server are described in the sections below.

Stopping IO Server from Windows ServicesIf IO Server is running as a Windows service on your PC, use the procedures described below to shutdown IO Server.

To stop the I/O Server service1. Click the Windows Start button, right-click My Computer




Manually Shutting Down IO Server TAC I/NET Seven Basics

3. In the right-hand panel, scroll down and locate the INet7IoSrv service, right-click it, and select Properties from the resulting popup menu.

4. In the Properties editor, perform the following tasks:

a. Stop the service by clicking the Stop button.

b. Click OK to close the Properties editor.


TAC I/NET Seven Basics Manually Shutting Down IO Server

Stopping IO Server from the Windows System TrayIf IO Server is not running as a Windows service on your PC, you can manually shut it down from the Windows system tray using the procedures described below.

To shutdown I/O Server from the Windows system tray1. Locate the IO Server icon in the Windows system tray.

The actual icon used to represent IO Server will depend on how your system is configured. Refer to Chapter 3 in TCON298, TAC I/NET Seven Getting Started, for more infor-mation about IO Server icons.

2. Right-click the IO Server icon and select Exit from the resulting popup menu. If the exit command is greyed out, it is because you are still logged into IO Server. In this case, select Logout first and then select Exit.


Manually Shutting Down IO Server TAC I/NET Seven Basics

Stopping IO Server from the Windows Task ManagerYou can manually shutdown IO Server from the Windows Task Manager using the procedures described below.

To shutdown I/O Server from the Windows system tray1. Right-click the clock in the Windows system tray and select

Task Manager from the resulting menu.

2. In the Windows Task Manager, locate and highlight the INetIoSrv.exe process.

3. Click End Process to shutdown IO Server.


TAC I/NET Seven Basics Registering INetEqzMerge as a Windows Service

Registering INetEqzMerge as a Windows Service

TAC I/NET Seven includes an executable file named INetEqzMerge that is used to support file equalization. This executable file must run as a Windows service on each equalized client workstation that is using either of the following SQL servers as the server for TAC I/NET Seven’s database:

✦ SQL Server 2005 Express

✦ SQL Server 2008 Express

Note: MSDE 2000, SQL Server 2005 Standard/Enterprise, and SQL Server 2008 Standard do not require INetEqzMerge. These SQL servers already provide the necessary services for file equalization.

During the process of installing TAC I/NET Seven on your PC, the Install program will attempt to automatically register INetEqzMerge as a Windows service. However, depending on your PC’s security settings, the Install program may not have the authority to register a service. In this case, INetEqzMerge will not be a registered service and file equalization will not be available.

If you you are preparing to implement file equalization on a TAC I/NET Seven workstation that uses SQL Server 2005/2008 Express, proceed with the steps described in this section.


Registering INetEqzMerge as a Windows Service TAC I/NET Seven Basics

Checking for the INetEqzMerge ServiceTo see if INetEqzMerge is registered as a Windows Service

1. Click the Windows Start button, right-click My Computer and select Manage from the resulting popup menu.


3. In the right-hand panel, scroll down and see if INetEqzMerge is included in the list of services.

4. If INetEqzMerge is included in the list, verify that its Startup Type is defined as Automatic. If necessary, you can double-click on the service to open its properties and set it to automatic.


If INetEqzMerge was not included in the list, proceed with the next set of steps to manually register it as a Windows service.


TAC I/NET Seven Basics Registering INetEqzMerge as a Windows Service

Manually Registering INetEqzMerge as a Windows ServiceTo register INetEqzMerge as a Windows service

1. Click the Windows Start button and then click Run....





4. In the command window, unregister INetEqzMerge as follows:

a. Type INetEqzMerge /unregserver



Registering INetEqzMerge as a Windows Service TAC I/NET Seven Basics

5. In the command window, set INetEqzMerge to run as a Windows service as follows:

a. Type INetEqzMerge /service




8. Verify that INetEqzMerge has been successfully registered as a Windows service by repeating the steps in “Checking for the INetEqzMerge Service” on page 1-50.


C H A P T E R42

2

© 2001–2010 SchTCON299–05/10

Setup and Network Configuration

There are four steps to configuring your TAC I/NET Seven system.

1. Network Design—Advance planning of your TAC I/NET Seven system is essential to the configuration process.

2. TAC I/NET Seven Communication Configuration—An overall configuration of your communication parameters. This step includes designating serial port usage, baud rate, printer parameters, and default file directories.

3. Host Configuration—Specifies user-interface parameters for a specific host workstation.

4. Network Configuration—Identifies the devices connected to your TAC I/NET Seven network.

TAC I/NET Seven Configuration

TAC I/NET Seven uses two supplementary programs to handle system configuration and communication functions. Configure is responsible for defining communication parameters and certain system parameters. Some of the parameters established in Configure are used directly by TAC I/NET Seven and others are used by the I/O Server program. I/O Server handles all communi-cation between your workstation and other hosts or NetPlus Routers (NPRs).

Within Configure, you can set up serial port, and TCP/IP commu-nication parameters, select a printer port, and alter TAC I/NET Seven’s default directory structure. You can also use Configure to set up NetPlus Routers and define host masks for message routing requirements between other hosts and NetPlus Routers. If neces-sary, you can create multiple configuration profiles and customize your TAC I/NET Seven environment simply by switching profiles.


Host Configuration Setup and Network Configuration

You should review the System Configuration chapter in TCON300, TAC I/NET Seven Technical Reference Guide, prior to establishing your configuration parameters. This chapter provides information essential to establishing an efficient TAC I/NET Seven network.

After you have planned the network configuration, you will use Configure to set up certain functions in I/O Server and TAC I/NET Seven. The Configure program is fully documented in TCON298, TAC I/NET Seven Getting Started, and is not duplicated here. Refer to the TAC I/NET Seven Configuration chapter for assistance.

After you complete the network design and TAC I/NET Seven configuration, you can proceed with the Host Configuration.

Host Configuration

The Host Configuration Editor lets you define certain interface parameters. The changes you make here go into effect as soon as you click the OK button.

Figure 2-1. Host Configuration Editor


Setup and Network Configuration Host Configuration

1. Select Edit Host Computer Configuration from the main menu. The system displays the Host Configuration Editor (see Figure 2-1).

2. Define the Main Window Title for TAC I/NET Seven. Type the desired text string. This text will appear in the title bar of the main TAC I/NET Seven window after you accept the changes to this editor.

3. Set the SevenTrends masks. All message masks are assigned to one of four distribution groups. In order for a SevenTrends to be accepted, it must match at least one checkbox active in the assigned distribution group. Each distribution group may contain up to eight masks.

Data sent to SevenTrends tables will be accepted by this oper-ator station only if their group number and mask matches one of these masks. Refer to the chapter on message routing in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

a. Set each of eight mask positions to the desired state, either active () or inactive ().

b. Repeat for each distribution group you want active.

4. Select a screen refresh interval in seconds (1–60) using the Refresh Interval (sec) spindial.

Note: Page refresh will be suspended during host tasks such as software downloads, station saves, and station restores.

5. Set the SysView Refresh Interval parameter to a value from 0 to 60 minutes. A setting of zero prevents System View from ever performing an automatic system-wide refresh. A setting of 1 to 60 minutes causes System View to perform automatic system-wide refreshes at the specified interval. Refer to “Refreshing the System View Window” on page 2-9 for more information.

6. Choose an operator timeout action from the Operator timeout action drop-down list. There are four options: Signoff, Default page, Both, and None.


Host Configuration Setup and Network Configuration

✧ Signoff – determines that the system will automatically sign the current operator off when the operator time-out expires.

If the Graphic Editor is open when signoff occurs, the open page is saved as BackupX.gpg, where X is the next incremental number assigned to each new backup page. For example, if Backup01.gpg already exists, the next file is named Backup02.gpg.

The Alarms, Messages and Transactions program is closed automatically as well.

If any editor was open, the system will back out to the main menu level without saving any changes or additions in progress.

✧ Default page – displays the default system page (defined in the next step) when the operator timeout expires.

✧ Both – enables both the signoff and default page func-tions.

✧ None – disables both.

7. Select the number of minutes (0–255) before the Operator Timeout Action is enabled using the Operator timeout (min) spindial. This controls the number of minutes of keyboard or mouse inactivity before the system initiates the operator timeout action. If you specify zero, then operator timeout will not occur.

8. Select an DCU Password Timeout value (0 to 240 minutes). After a user has connected to a password-protected controller, this parameter determines how many minutes of keyboard or mouse inactivity can elapse before the system requires the operator to re-enter the controller's password.

9. If desired, you can activate () the Do not notify on oper-ator time-out option in order to prevent the the system from displaying a timeout message each time an operator timeout occurs.

10. The default system page displays automatically each time TAC I/NET Seven is started. Enter a system page filename in the Default system page edit box.


Setup and Network Configuration Defining the Network Configuration

Alternatively, you can click File Open to display the browser in Figure 2-2. Select the system page file and click Open. You

will return to the Host Configuration Editor and the filename will display in the Default system page edit box.

11. Activate () or deactivate () the Size/Move option. If this option is deactivated (), TAC I/NET Seven windows cannot be resized or moved until an operator logs into I/NET.

12. Activate () or deactivate () the Close option. If this option is deactivated (), TAC I/NET Seven windows cannot be closed until an operator logs into I/NET.

13. Click OK to save the changes to the host configuration and close this editor.

Defining the Network Configuration

Note: The network configuration is equalized among all equalized clients if you enable File Equalization. Refer to Chapter 3, TAC I/NET Seven Configuration in TCON298, TAC I/NET Seven Getting Started, for more information about File Equalization.

Figure 2-2. Default System Page File Selection Editor


Defining the Network Configuration Setup and Network Configuration

Before you begin operation you need to define the devices included in your system and save the configuration. To do this you will pene-trate each device level (i.e., Link, Site, Station (DCU) and UC, DPU, SCU, or MR) and save each configuration level.

If links or DCUs exist and are communicating successfully, they appear automatically in the network configuration interface. In this case, all you have to do is save the configuration at each level. If there is no link or eligible DCU, you cannot penetrate to the next lower level.

Note: Functions that are network oriented (i.e., Automatic DCU Synchro-nization, Automatic DCU Save, Printing, Access Control) require the network configuration to be saved, or else they will not work.

Before assigning doors in Access Control you must first penetrate the system and save each level configuration. Refer to the chapter concerning Access Control in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Using System View to Configure Your NetworkTAC I/NET Seven retains the traditional NETCON functionality while offering an alternative tree-based network configuration interface. This new interface is named System View. Rather than displaying devices in successive summary screens, System View allows you to view your network as a tree. Within this tree, you can expand and collapse items in order to show or hide the next level in the hierarchy.

Refer to “Using the System View Interface” on page 1-31 for a basic overview of System View.

Viewing Each Level of Your Network

When you first open System View and select the Netcon tab at the bottom of the left-side panel, your system’s hosts and NPRS are displayed in the left panel’s tree view. This is the top-most level of your network.

When you expand an item by clicking its plus (+) symbol, the next level of your network that is associated with the expanded item is displayed. For example, when you expand a host item, any links



that exist at that host are displayed indented beneath it. You can then expand any of these links to view devices at the next level of the network. You can continue to expand items and penetrate through the network until you reach the lowest level. Figure 2-3 shows an example of items expanded to show each level of the network.

Parent and Child Items

Any item that can be expanded to show subordinate items can also be referred to as a parent item. Any item that is subordinate to another item can be referred to as a child item. For example, in Figure 2-3, DLA Link #97 is the parent item of the NPR-03 child item. But NPR-03 is not just a child item, it is also the parent item of the 7793-Doors-1, DCU 7728-xxxxxxx, and 7798-Center1 child items.

Displaying Popup Menus

Within System View, you can display popup menus of common functions by clicking with the right mouse button. The contents of these popup menus will vary depending on where you click within the System View interface. Figure 2-4 shows a typical popup menu available within System View.

Divided Popup Menus

A popup menu may have a horizontal line that divides the menu into an upper and lower section (see Figure 2-5). In this case, the upper section contains items that are common to the pane in which you clicked. For example, if you right-click anywhere in the left-side pane, the first two items in the popup menu are Print and Print

Figure 2-3. Expanding Items to View Each Network Level



Preview (refer to “Print and Print Preview” on page 1-33 for more information about these functions). The lower section contains functions that are applicable to the highlighted item (refer to the following section titled “Typical Popup Menu Functions” for more information).

Typical Popup Menu Functions

The following functions are typically available when you right-click on a network item in System View:

✦ Save ItemUse this function to save a record of the selected item. This function is available when no record of the selected item already exists in your database. If the selected item is a child of a parent item (i.e., the selected item is a level beneath another item), then the parent item must have already been saved; otherwise, this option does not appear in the popup menu.

✦ Save SubTreeThis function is available if your host workstation is able to establish communications with the selected device; otherwise, this function does not appear in the popup menu. Use this function to save a record of the selected item, as well as the records of its subordinate items that are currently communi-

Figure 2-4. Right-clicking a Host in System View

Figure 2-5. Divided Popup Menu



cating. By using this function, you can avoid the process of manually penetrating each level of your network in order to save device records to your database.

✦ Add Child ItemThis function allows you to add an item to the next level beneath the currently selected item. For example, if you right-click on a DLA link, the Add Child Item function allows you to add a new Site device (i.e., a Tap or an NPR).

✦ Modify ItemThis function is available if your host workstation is able to establish communications with the selected device; otherwise, this function does not appear in the popup menu. This func-tion opens the editor appropriate for the selected item, allowing you to make changes to the item’s parameters. For example, if you right-click on a 7793 MCI, the Modify Item function opens the Station Parameters editor.

✦ Delete ItemThis function removes the record of the selected item from your database. If your host workstation is still able to commu-nicate with the deleted item, the item remains visible in the tree and its status indicator changes to show that it has not been saved. If your host workstation cannot establish commu-nications with the deleted item, the item is removed from the tree.

Refreshing the System View Window

When you first open the System View interface and select the Netcon tab, TAC I/NET Seven automatically polls your entire system to determine what devices are connected and communi-cating. The results of this poll are then compared to the records stored in your database to determine the status of each device (refer to “Network Status Indicators” on page 2-11 for more informa-tion). Finally, System View builds the hierarchical tree that repre-sents your network.

Beyond the initial building of the network tree, the information in the System View interface remains static until any of the following events occur:

✦ User presses the F5 function key.



You can refresh the System View window at any time by pressing the F5 function key. This is a system-wide refresh that updates all information in the System View window.

✦ User highlights or expands an item.

When you highlight or expand an item in the System View interface, TAC I/NET Seven automatically re-polls the item and all of its subordinate items.

✦ The SysView Refresh Interval elapses.

The SysView Refresh Interval parameter in the Host Configuration editor allows you to specify how often System View automatically updates its system-wide information. You can set this parameter to a value from 0 to 60 minutes. A setting of zero prevents System View from ever performing an automatic system-wide refresh. A setting of 1 to 60 minutes causes System View to perform automatic system-wide refreshes at the specified interval.

An interval does not begin until an active system-wide refresh is completed. For example, a setting of 5 minutes causes System View to perform a refresh 5 minutes following the completion of any previous system-wide refresh.

You can continue using System View during an active refresh. The mouse cursor will show both an arrow and an hourglass, indicating that the system is refreshing while remaining available for use.



Network Status Indicators

Each item displayed in the network tree is capable of displaying its current status. Table 2-1 lists the status indicators and describes their meaning.

Table 2-1. Network Status Indicators

Status Indicator Example Description

Online and Saved

Blank Status icons are clear at each level of the tree.

Offline and Saved

“X”(red)

When an item is offline and not saved, it reports a red “X” status. If the item is the parent of any other items, then all child items associated with it report the red “X” status. The red “X” status continues to be reported at all items that are at lower levels in the branch.

Child Item Offline and Saved

“!”(yellow)

When an item displays a red “X” status, its parent (if online and saved) will report the yellow “!” status. If the parent is a child of a higher-level parent item, then this higher-level parent will also report a yellow “!” status. The yellow “!” status continues to be reported at each higher level parent item in the branch.

Item Online and Not Saved

“+”(red)

When an item is online and not saved, it reports a red “+” status. If the item is the parent of any other items, you must save it before you can save any of its child items.

Child Online and Not Saved

“+”(yellow)

When an item displays a red “+” status, its parent (if online and saved) will report the yellow “+” status. If the parent is a child of higher-level parent item, then this higher-level parent will also report a yellow “+” status. The yellow “+” status continues to be reported at each higher level parent item in the branch.



Using NETCON to Configure Your NetworkThe traditional TAC I/NET Seven system allows you to configure your network through a series of summary screens and editors. Starting with the Link Summary, you save the devices communi-cating at that level, then penetrate down to the next subordinate summary. With each new summary screen, you continue to save devices and penetrate to the next level until all communicating devices have been saved. This series of network configuration summary screens, and their associated editors, are collectively referred to as “NETCON”.

Penetrating the Levels of Your Network

To penetrate from one level of your network to the next, highlight an item in a summary and select Penetrate. This option is only available when the item that you select links to another level of your network.

Storing Network Configuration Records

Save items appearing in any of the network configuration summa-ries using the following procedures:

1. To save only one item, highlight the item and select Save.

2. To save all items select Save All.

Network Summaries

As described earlier, NETCON is a collection of summary screens and editors that enable you to configure your network. There is one summary screen for each level of your network. These summaries are described below.

Note: An asterisk (*) appearing next to an item in a summary indicates that the data saved in TAC I/NET Seven's database does not match the information currently being received from the device. In this case, you can update TAC I/NET Seven's database by deleting the item's record (an item currently communicating with TAC I/NET Seven will not disappear from the summary when you press the Delete button) and then re-save it by pressing the Save button. Any devices residing beneath this device will also have to be re-saved.



Link Summary

The Link Summary is the first dialog displayed when you select Edit Host Computer Network Configuration from the main TAC I/NET Seven menu. The Link Summary shows the Link Taps, DLA links, and non-DLA NetPlus Routers available or defined in your configuration.

From the Link Summary you can add, delete, or modify links. This is the first level that you can save and penetrate to other levels through a selected link.

The summary includes columns for the Link number, Link Type and Name. The Dn column indicates if the device can be programmed by downloading a file from the host workstation. The Host column displays the number of the host through which the connection is made. If a Telephone number is assigned to this device, it is displayed in the next column.

The R/H column displays the number of the first restore host (i.e., Restore Host 1) assigned to the link device. This column will display a “D” (disabled) if you have not enabled Automatic DPU Restore on the link. An “L” will be displayed if you have set Restore Host 1 to “0”, designating this workstation (i.e., your “local” host) as the first restore host.

The Cnf column contains the status of the link. A plus sign (+) indicates the device is communicating, but is not saved in this configuration file. A minus sign (–) indicates the device has been saved, but is not now communicating. If this field is blank, the device has been saved in this configuration and is communicating.

As an enhancement to the normal operation of Link Summary, the Type and Name fields have the added capability of indicating that a link is being shared among one or more DLA-enabled NPRs. As shown by the highlighted link in Figure 2-6 below, the Link Type is “Distributed Link” and the Link Name is “DLA Link #nn,” indi-cating that the link is being shared.

1. Select Edit Host Computer Network Configuration from the main menu. The system displays the Link Summary window (see Figure 2-6).



2. Use the following functions to configure your system:

✢ Add, delete, or modify

✢ Save a single link.

✢ Save all links.

Procedures for each of these functions are described below.

3. To penetrate to the next level of a link, highlight the link and then select Penetrate. The Site Summary or Station Summary screen appears.

4. When you are finished, select Close.

Site Summary

The Site Summary is available after you select a Tap and penetrate the link. The Site Summary contains a list of all connected 7803 and 7806 Taps. The Cnf column can contain a “D” to indicate a 7806x Dial Tap. TAC I/NET Seven will not check the status of a Dial Tap unless you penetrate it.

Figure 2-6. Link Summary



1. From the Link Summary, highlight a 7801 Host/Link, 7802 Host/Link, 7804 Dial Host/Link, or 7805 Dial Link and then select Penetrate. The Site Summary displays as shown in Figure 2-7.

2. The following functions are available from this screen:

✧ Add, delete, modify, and penetrate

✧ Save a single site.

✧ Save all sites.

Note: You must manually enter remote site dial Taps including baud rate and telephone number.

Figure 2-7. Site Summary



Station Summary

The Station Summary is available after penetrating through a link or site Tap summary. The Station Summary contains a list of all connected controllers.

1. Highlight a Tap in the Site or Link Summary.

2. Select Penetrate. The Station Summary displays as shown in Figure 2-8.


✧ Add, delete, modify, and penetrate

✧ Save a single station.

✧ Save all stations.

Procedures for using these function are described below.


Figure 2-8. Station Summary



MCU Summary

Note: An asterisk (*) appearing next to a device's address indicates that the device is configured as a two-station device, but the MCU Configura-tion setting for the device's second address is set incorrectly. Correct this issue by changing the device's setting in the MCU Configuration editor, or by configuring the device to operate in a single-address mode.

The MCU Summary is available after penetrating a UCI, DPI, MRI, or MCI, or I/SITE LAN. The MCU Summary contains a list of all connected UCs, DPUs, DIUs, DIOs, SCUs, MRs, ASMRs, and OP5s.

1. Highlight a station in the Station Summary.

2. Select Penetrate. The MCU Summary displays as shown in Figure 2-9.


✧ Add, delete, and modify.

Figure 2-9. MCU Summary



✧ Save a single station.

✧ Save all stations.

Procedures for using each of these functions are described below.


Adding a LinkUse the following steps to add a Link to the network configuration:

1. Depending on the interface you are using, perform one of the following actions:

✧ Using System View, right-click any blank area in the left-side pane and select Add Link from the resulting popup menu.

✧ Using NETCON, select Add from the Link Summary screen.

The system displays the Link Address dialog box (see Figure 2-10).

2. Enter the Link number (system address) for this link (0 – 99) and then select OK. The system displays the Link Parameters window (see Figure 2-11).

3. Choose the Type of Tap link from the drop-down list. The Tap types are discussed in the chapter on host functions in TCON300, TAC I/NET Seven Technical Reference Guide.

4. Enter the name you want to describe the link in the Name edit field. You may use up to 16 characters.

Figure 2-10. Link Address



5. Choose a Downloadable setting. Choose Yes if this link Tap can be downloaded from the Software Restore editor.

The Downloadable parameter is automatically set to Yes and is greyed-out if you set the Type to “2000 NetPlus Router.” It is automatically set to No and is greyed-out if you set the Type to “Xenta 527” (refer to the document entitled Engi-neering TAC Xenta Server on www.tac.com for information concerning the Xenta 527).

6. If necessary, change the Host Number for this link. This parameter is not available when the link Type is defined as “2000 NetPlus Router” or “Xenta 527.”

7. Enter the Phone Number if the link address you selected is a dial Tap. Use up to 31 characters. This is the number remote Taps use to reach this dial Tap located at the host PC. The number you enter here must match the number you enter in the Remote Site Dial Tap editor (refer to “78060 and 78061 Tap Configuration” on page 3-5).

Figure 2-11. Add/Modify a Link – Link Parameters


http://www.tac.com


Note: If you want messages to be received during a PC-initiated call, such as point controls, alarms, etc., the telephone number must be defined for a 7804 and 7805 tap in this editor. This phone number must match the telephone number entered in the Site Tap Configuration editor for the remote 7806 tap.

The two numbers do not have to match exactly since the phone numbers are stripped of all non-numeric characters, and the shorter of the two numbers is compared by the system from right to left. For example:

7804 Network Definition Telephone Number = 24355947806 Site Tap Configuration Telephone Number = T9,18172435594

The 7804 telephone number (2435594) is the shorter, and is compared, from right to left, with the stripped version of the 7806 telephone number (918172435594). The first seven digits, counting from the right, match.

Additionally, the system link number (0–99), which is defined for each phone number in the 7806 Site Tap Configuration editor, must match the system link defined in the Configure program for the respective dial tap that will be called.

Note: If you are using multi-link dial, the phone number for every system link must be populated. Under most circumstances, each host soft-ware link would use the same phone number. Refer to the chapter on system configuration in TCON300, TAC I/NET Seven Technical Reference Guide for a description of multi-link dial configuration.

8. An Automatic DPU Restore feature can be configured for this link if both of the following conditions are true:

• The Enable access control option has been activated () in the I/NET Configuration Editor.

• The workstation is not being used as a Remote Client in a client/server network configuration. Refer to the descrip-tion of Client/Server Architecture in TCON300, TAC I/NET Seven Technical Reference Guide, for more informa-tion.



Configure the Automatic DPU Restore feature for this link as follows:

a. If necessary, activate () the Restore from Local Host option. This option's setting is not equalized. Activate this option on each host you want capable of performing automatic DPU restores for this link.

This option will be activated and grey-out if your local host is already assigned as a restore host in any of the four Restore Host fields described in the next step.

Caution: Before assigning restore hosts to a link in the following step, ensure that you have enabled File Equalization. Otherwise, the restore host could download out-of-date information to the link's DPUs.

b. Specify up to four restore hosts (Restore Host 1-4) for this link. The restore hosts you define for links are equal-ized among all hosts.

For each Restore Host field, 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 define here.

Note: Do not use a workstation that is configured as a Remote Client as a restore host. Each restore host must maintain its own database. Refer to the description of Client/Server Architecture in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

You can leave any field at its default value of 0 to desig-nate 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 on this link.

For more information about restore hosts, refer to the description of the “Automatic DPU Restore” feature in TCON300, TAC I/NET Seven Technical Reference Guide.

9. Select OK to save the configuration.



Adding a SiteThe Site Configuration editor allows you to configure the site number, Tap type, the device name, download capability, and the baud rate and telephone number if it is a 7806 Tap.

Note: You must save the link configuration through which you accessed the site configuration before TAC I/NET Seven will let you save a site configuration.

Use the following steps to add a site to the network configuration:


✧ Using System View, right-click any link in the left-side pane and select Add Child Item from the resulting popup menu.

✧ Using NETCON, select Add from the Site Summary screen

The system displays the window shown in Figure 2-12:

2. Enter the Site address (0–63).

Figure 2-12. Site Address Editor



3. Select OK. TAC I/NET Seven displays the Site Parameters window (see Figure 2-13).

4. Choose the Type from the drop-down list. The 7803 direct-connect Tap and the 7806 dial Tap are the available site Tap options.

5. Enter the name you want to describe the site in the Name edit field.

6. Choose a Downloadable setting for this Tap. Choose Yes if this site Tap can be downloaded from the software restore editor.

7. Choose the Baud Rate (300–19200) from the drop-down list.

8. Enter the Phone Number of this Tap. Use up to 31 characters. This is the number local Taps use to reach this remote dial Tap.

9. Select OK to save this configuration.

Adding a StationWhen you add a station to your network, you can configure the station address, controller type, the device name, download capa-bility, and the number of stations if it is a multi-station controller.

Use the following steps to add a station to the network configura-tion:

Figure 2-13. Site Parameters Editor




✧ Using System View, right-click an NPR, LAN Tap, or Site Tap in the left-side pane and select Add Child Item from the resulting popup menu.

✧ Using NETCON, select Add from the Station Summary screen.

The system displays the dialog shown in Figure 2-14:

Note: Keep in mind that you can have only 64 controllers maximum per link Tap. This means that, although you can assign up to 64 control-lers to one LAN (site) Tap, you cannot have the same controller address assigned to two different site Taps. If you have all 64 control-lers on one site Tap, you can have only one site Tap communicating with the link Tap. Or, if you have 64 site Taps communicating with the link Tap, you can have only one controller per site Tap. One easy way to check if you have a conflict is to run a configuration summary. This summary lists the site number and controller number side by side. For example, if you have controller #35 on site #1 and site #2, this is a conflict. Change your system configuration accordingly.

2. Enter the Station address (0–63).

3. Select OK. TAC I/NET Seven displays the Station Parameters window (see Figure 2-15).

4. Choose the controller Type from the drop-down list.

5. Enter the name you want to describe the controller in the Name edit field.

Figure 2-14. Station Configuration – Address



6. Choose a Downloadable setting for the station. Choose Yes if this station can be downloaded from the software restore editor.

7. Enter the Number of Stations (1–2) on this controller.


Adding an MCUUse the following steps to add an MCU to the network configura-tion:


✧ Using System View, right-click any SLI (i.e., any 7760 UCI, 7791 DPI, 7792 MRI, 7793 MCI, or 7798 I/SITE LAN) in the left-side pane and select Add Child Item from the resulting popup menu.

✧ Using NETCON, select Add from the MCU Summary screen.

The system displays the window shown in Figure 2-16:

2. Enter the UCI, DPI, MRI, or MCI, or I/SITE LAN Station address (0–63).

3. Enter the MCU number.

4. Select OK. TAC I/NET Seven displays the MCU Parameters window (see Figure 2-17).

5. Choose the MCU Type from the drop-down list.

Figure 2-15. Station Configuration – Station Parameters



6. If you set the MCU Type to “DPU,” “DIO,” or “DIU,” in the previous step, perform the following actions:

a. Choose a Device Type from the drop down list.

b. If the Device Type is “DPU7920”, choose an option for the Downloadable setting (either Yes or No). Only the SCU1200, SCU1280, SCU1284, and the DPU7920 with a DPU48K add-on board can be downloaded. Selecting a Device Type of SCU1200, SCU1280, SCU1284, or OP5 forces the Downloadable setting to Yes.

When you set this parameter to Yes, the DPU or SCU gets included in the list of downloadable devices that appears in the DPU Software Restore editor (refer to “Performing a Software Restore to DPUs and SCUs” on page 4-17 for more information).

Figure 2-16. MCU Configuration – Address

Figure 2-17. MCU Parameters



c. If the Device Type is SCU1200, SCU1280, or SCU1284, set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON).

In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode.

d. Enter the Revision number. If the device is loaded with software revision 3.00 or later and is successfully commu-nicating with your host workstation, this value will be filled in automatically.


Adding a Door PointIf you added a DPU, SCU1284, or OP5 to your network, then you can add door points. Use the following steps to add a door point to the network configuration:


✧ Using System View, right-click any DPU7910, DPU7920, SCU1284, or OP5 in the left-side pane and select Add Child Item from the resulting popup menu.

✧ Using NETCON, perform the following two steps:

✢ Highlight a DPU7910, DPU7920, SCU1284, or OP5 in the MCU Summary and select Penetrate. The system displays the Door Summary, shown in Figure 2-18.

✢ Click Add.



TAC I/NET Seven displays the Door Address window (see Figure 2-19).

2. Enter the bit offset of the Door (8 or 9) and select OK to save the address. This field will be read-only (i.e., forced to bit offset 8) for an OP5.

TAC I/NET Seven displays the Door Parameters dialog (see Figure 2-20).

Figure 2-18. Door Summary

Figure 2-19. Door Address Editor

Figure 2-20. Door Parameters Editor



3. Enter the Name of the door and select OK to save the door name and return to the Door Summary.

4. Click Close to save this configuration.

Adding a FloorIf you added a door to your network, then you can add floors. Use the following steps to add a floor to the network configuration:


✧ Using System View, right-click a door in the left-side pane and select Add Child Item from the resulting popup menu.

✧ Using NETCON, perform the following two steps:

✢ Highlight a door in the Door Summary and select Penetrate. The system displays the Floor Summary.

✢ Click Add.

The system displays the Floor Editor (see Figure 2-21).

2. Enter the floor Index number (from 1 to 79).

3. Enter the floor enable DO Point address using the LLSSPPBB format (i.e., link, station, point, and bit offset). For example, a DO point on link 03, station 02, point 36, and bit offset 00 would be: 03023600 DO.

Figure 2-21. Floor Editor


Network Functions Setup and Network Configuration

4. Select OK to accept your changes. The system will then display the Floor Parameters Editor (see Figure 2-22).

5. Type a Point Name for the floor enable point. This name may be up to 16 characters long.

6. Type a Floor Name for the floor enable point. This name may be up to 16 characters long.

7. Select OK to accept your changes.

Network Functions

Note: Network functions are not equalized when File Equalization is enabled. Refer to Chapter 3, TAC I/NET Seven Configuration in TCON298, TAC I/NET Seven Getting Started, for more information about File Equalization.

Network Functions are not available on a workstation configured as a Remote Client in a client/server network. Refer to Chapter 3, TAC I/NET Seven Configuration in TCON298, TAC I/NET Seven Getting Started, for more information about using a client/server configura-tion.

Network functions are a grouping of functions that let you manip-ulate controllers remotely. These functions are:

✦ Synchronize the date/time of your controllers.

✦ Select automatic DCU save for some or all of your controllers.

✦ Select broadcast days for special day schedules.

Figure 2-22. Floor Parameters Editor


Setup and Network Configuration Network Functions

✦ Display off normal points.

✦ Display disabled points.

✦ Print Database

DCU SynchronizationThis function lets you periodically synchronize the hardware clocks in your controllers with the host PC clock. While the clocks provided are quite accurate, they do drift slightly over long periods of time. This function lets you automatically re-establish synchro-nization at a specified frequency, without any further action on your part. Synchronization will occur at 3:15 a.m. (03:15) on the appropriate days.

You can also use this editor to synchronize daylight savings time settings in your controllers.

1. Select Edit Host Computer Network Functions from the main menu. The system displays the screen shown in Figure 2-23.

Figure 2-23. Network Functions Screen



2. Select the link of the controller(s) you wish to synchronize from the drop-down list. The system now displays the controllers on the link you selected.

3. Above the list are six push-buttons. Select Sync.

4. Select those controllers you wish to mark for DCU synchroni-zation by either clicking on individual controllers in the list or by selecting Set All. Controllers that are marked for synchro-nization will show the frequency of synchronization (Day, Week, Month) in the Sync column of the list. Each click on a controller in the list will toggle the Sync function between the next selection starting from Day.

5. Select the frequency (None, Day, Week, or Month) of synchronization by choosing the radio button.

6. If you wish to synchronize daylight savings time settings in your controllers, perform the following steps:

a. Click the Setup button. This causes the Daylight Savings Sync editor to open.

b. Click Enable. The Begin date and End date parameters become active.

c. Enter the Begin date. Enter the month (1-12), week (1-5), and day (1-7) daylight savings time begins (Standard Time ends). On that date at 2:00 a.m. (02:00), the DCU clock moves ahead one hour.

Figure 2-24. Daylight Savings Synchronization



Use the following guidelines for setting the date:

d. Enter the End date. Follow the procedure described above to enter the month, week, and day the DCU clock moves back one hour and return to Standard Time. This process occurs at 2:00 a.m. (02:00) on the specified day.

e. Select OK to save these settings and to close this editor.

7. Select OK when finished.

Automatic DCU SaveIf you activate this option for a particular controller, the system performs an automatic save of controller programming each 24-hour period at 3:15 a.m. (03:15) provided a change has been made to the programming.


2. Select the link of the controller(s) you wish to automatically save from the drop-down list. The system now displays the controllers on the link you selected.

Month January is month 1, February is month 2, and so on, ending with December as month 12.

Week 1 Enter a 1 if the daylight savings start falls during the first seven days of the month (1-7).

Week 2 Enter a 2 if the daylight savings start falls during the second seven days of the month (8-14).

Week 3 Enter a 3 if the daylight savings start falls during the third seven days of the month (15-21).

Week 4 Enter a 4 if the daylight savings start falls during the fourth seven days of the month (22-28).

Week 5 Enter a 5 if the daylight savings start falls after the 28th day of the month.

Day Sunday is day 1, Monday is day 2, and so on, ending with Saturday as day 7.



3. Above the list are six push-buttons. Select the Save push-button.

4. Select those controllers you wish to mark for Automatic DCU Save by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for Auto-matic DCU Save will show a “Y” in the Save column of the list. Each click on a controller in the list will toggle the Save function between “–” and “Y”.

Special Day BroadcastUse this option to distribute a previously-defined special day schedule to selected controllers as needed. Special day start/stop/cycle schedules are defined using the Time Scheduling point extension editor and are assigned to a particular Special Day (S1–S7). These TAC I/NET Seven features are discussed in detail in the chapter dealing with host functions in TCON300, TAC I/NET Seven Technical Reference Guide.


2. From the drop-down list, select the link of the controller(s) to which you want to distribute the special day schedule. The system now displays the controllers on the link you selected.

3. Above the list are six push-buttons. Click the Spec push-button.

4. Select the type of Special Days to broadcast by choosing one of the following radio buttons:

✧ None — Remove current special day broadcast setting.

✧ Special Day — Broadcast a single special day schedule definition to all controllers marked with “S”.

✧ Global — Broadcast a list of special day schedule defini-tions to all controllers marked with “G”.



5. Select those controllers you wish to mark for special day broadcast by either clicking on individual controllers in the list or by selecting Set All. Controllers that are marked for special day broadcast will show the type (“-” for None, “S” for Special Day, or “G” for Global) in the Spec column of the list.

Subsequent clicks on controllers in the list will cycle the Special Days setting to the next option.

6. Select Setup to define special day schedules and broadcast date/time. Depending on the type of Special Days chosen in Step 4, one of the following editors will open:

Special Day — The Special Day Broadcast Setup editor opens. Refer to “Special Day Broadcast Setup” below for instructions on using this editor.

Global — The Global Special Days editor opens. Refer to “Global Special Day Broadcast Setup” on page 2-36 for instructions on using this editor.

Special Day Broadcast Setup1. Enter the special day schedule starting date in the Date edit

box. You may enter the date as 4 5, 4/5, or 04 05 as long as a space or “/” divides the month from the day.

2. Enter the Duration of the special day schedule (0–127 days). If you enter a “1,” the system executes the changed schedule only on the date entered in the date field.

Figure 2-25. Special Day Broadcast Editor



3. Activate the special day schedule (S1–S7) checkboxes for broadcast.

Broadcast Time1. Enter the date for the special day schedule to be broadcast to

the controller in the Date edit box.

2. Enter the time for the broadcast in the Time edit box in 24-hour format.


If you return to this editor before the special day schedule has expired, the date and time you enter here continue to appear in this field.

Note: If a communication failure occurs and the system is unable to broad-cast the special day schedule to all selected controllers, it defines and displays the extent of this failure as a message event and sends the error message “Special day lost” along with the Link and Station address of the failed transaction. Always check the messages after you issue a special day broadcast to make sure the broadcast was successful.

Global Special Day Broadcast Setup

This editor summarizes all currently defined execution dates for special day schedules. Up to 32 execution dates can be defined.

The following options are available:

✦ Add – Use this option to create a new execution date. When you select this option, the system displays the Special Days editor.

✦ Delete – Use this option to delete an existing execution date. Delete an execution date by selecting it in the summary and pressing Delete.

✦ Modify – Use this option to modify an existing execution date. When you highlight an entry in the summary and select this option, the system displays the Special Days editor.



Broadcast Time

You may select to delay the broadcast of the special day schedule execution dates. Enter the date and time for the scheduled broad-cast. This does NOT have to be the same day as the date you want the special day schedule(s) to go into effect.

1. Enter the date for the broadcast to occur in the Date edit box.

2. Enter the time for the broadcast in the Time edit box in 24-hour format.


If you return to this editor before the special day schedule has expired, the date and time you enter here continue to appear in this field.

Figure 2-26. Global Special Days Broadcast Editor



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 10, Dynamic Control, for details on the Special Day and Time Scheduling editors.

Off Normal PointsOff normal is another term used to describe points that are in an alarm state. Use this option to select controllers containing the points you want to inspect for off normal status when you select the Off normal Points option from the Summary options menu. Refer to Chapter 7, Summaries, for more information on the Summary option.


2. From the drop-down list, select the link of the controller(s) you wish to interrogate for off normal point status. The system now displays the controllers on the link you selected.

3. Above the list are six push-buttons. Select the Nrml push-button.

4. Choose those controllers you wish to mark for interrogation by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for interroga-tion will show a “Y” in the Nrml column of the list. Each click on a controller in the list will toggle the Nrml function between “–” and “Y”.

Disabled PointsDisabled 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 to inspect for disabled status when you select the Disabled Points option from the Summary options menu. Refer to Chapter 7, Summaries, for more information on the Summary option.




2. Choose the link of the controller(s) you wish to interrogate for test/manual point status from the drop-down list. The system now displays the controllers on the link you selected.

3. Above the list are six push-buttons. Select the Dsbl push-button.

4. Choose those controllers you wish to mark for interrogation by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for interroga-tion will show a “Y” in the Dsbl column of the list. Each click on a controller in the list will toggle the Dsbl function between “–” and “Y”.


Database PrintUse this option to print a copy of any or all controller database point or extension entries. This lets you get a printout of exactly what points and point extensions you have added to the controllers on your system.


2. Choose the link of the controller(s) you wish to print from the drop-down list. The system now displays the controllers on the link you selected.

3. Above the list are six push-buttons. Select the Print push-button.

4. Choose the controllers you wish to mark for printing by either clicking on individual controllers in the list or by selecting All Yes. Controllers that are marked for printing will show a “Y” in the Print column of the list. Each click on a controller in the list will toggle the Print function between “–” and “Y”.



5. Select the Setup push-button at the bottom of the window. The window shown in Figure 2-27 appears.

6. If you want the database report to print to the screen activate the Print to screen checkbox.

7. Select the database items that you want to print by clicking on the Select checkbox.

8. To select multiple links follow Steps 2 through 6 for each link and controller, selecting Close from the Database Print window to return to Network Functions, until you have selected each controller.

Note: The TAC I/NET Seven system lets you select more than one link at a time but this results in a very lengthy printing session. If you do not want to tie up the printer for an extended period of time select only one link at a time.

Figure 2-27. Database Print Parameter Selection



If N/A appears in the print column this means that the station exists for this controller, but no save file exists in the save file directory.

9. When you have selected the appropriate parameters, select Print to start the printing.

10. When you have selected the appropriate parameters, select Close to return to the Network Functions window.

Since database prints may be very long, make sure no manual control commands from the PC are needed during the time required for printing.

11. Select Close to return to the Network Functions window.


C H A P T E R10

3

© 2001–2010 SchTCON299–05/10

Tap Configuration

Tap Configuration Editors

Use the Tap editors to set parameters for each Tap during initial system configuration, and when you add a new Tap. Specify the Tap address, the LAN or host name, the baud rate, and other informa-tion relating to how you want to use the Tap in your system.

Before configuring your Taps, make sure each Tap address is set properly with the switches found on the Tap. Refer to TCON101, Model 7800 Series Tap and Repeater Installation Guide, for informa-tion on Tap switch settings.

To edit a Tap, you must connect through the system to the level at which the Tap resides. The Host Tap connects directly to your workstation and can be edited at any time. To edit a Link Tap, you must connect to a link. To edit a Site Tap, you must connect to a site. As you penetrate the system, the address of each connected Tap appears in the status bar at the bottom of the TAC I/NET Seven window.

Tap ConfigurationWhen you update parameters in a Tap, the changes take effect when you disconnect from the Tap. If the changes are to a shared Dial Tap, the changes take effect when the last connected host discon-nects from the Tap.

Use the following steps to configure a Tap. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for a description of Tap configuration parameters.

1. Connect to the desired Tap.


Tap Configuration Editors Tap Configuration

2. Select Edit Tap Host Tap (or Link Tap, or Site Tap) from the main menu. The system displays the appropriate Tap Configuration editor (see Figure 3-1 for an example of the Host Tap Configuration editor).

The Link Tap and Site Tap configuration editors are similar to the Host Tap Configuration editor. This procedure describes the differences.

3. Assign a Tap name to the Host, Link, or Site Tap (up to 16 characters).

4. The LAN addr (0 to 63) identifies the Tap address on the controller LAN. When a 7801 Tap is connected to a Host LAN, the LAN address is set by DIP switches on the Tap and this field does not appear.

5. Depending on the type of Tap, do one of the following:

✧ On Host and Site Taps, use the spindial to choose a LAN speed.

✧ On Link Taps, use the spindial to choose a Speed.

✧ On Dial Taps, choose a Speaker setting from the drop-down list (Off, Auto, or On).

6. The Firmware Status parameters show the current Revision number and Revision date. These fields are display only and cannot be edited.

Figure 3-1. Host Tap Configuration Editor


Tap Configuration Tap Configuration Editors

7. Select the Distribution group number (1–4) to match the distribution group of the host PCs to which you want the Tap to send messages.

8. Set the Message mask to match the mask(s) of the host PCs to which you want the Tap to send messages.

9. Set the Message priority to None, Routine, Priority, or Crit-ical.

Note: When utilizing dual Tap functions (Site Tap and LAN Tap) in a 7716, 7718, 7728, 7756, 7780, 7791, 7792, 7793 (configured as -03 or -06), or 7798, the values entered under “Control Parameters” in one Tap editor are used by all Tap editors emulated within the same DCU. Only one set of “Control Parameters” have been provided in each DCU.

10. The % Full field is for AD/AA LAN Taps only. It specifies the number of messages that will be stored in the LAN/Site Tap’s RAM, as a percent of the total available memory, before the Tap calls the host PC. This is a deferred dialing parameter for “Priority” alarms.

A setting of “–” causes the Tap to immediately initiate a call whenever it receives a Priority message, regardless of the message buffer usage (i.e., the same functionality as the receipt of a Critical message). When using this setting, the Tap will ignore the Dial Later setting described in the next step.

11. The Dial later fields are for AD/AA LAN Taps only. These fields specify the time interval that must transpire following a “priority” alarm before the LAN/Site Tap calls the host PC. These are deferred dialing parameters for “Priority” alarms.

The Dial Later settings become the initial value of an elapsed-time counter. This counter begins counting down as soon as the Tap receives a priority message. When the time period has elapsed, the Tap initiates a call to the corresponding host to upload all messages in its buffer. This call may also be initi-ated before the time has elapsed if the % Full criteria is met (see Step 10 above). When message uploading is complete, the Tap hangs up. If the Tap then receives another Priority message, this process repeats itself.



Integrated Dial FunctionThis function provides communication between a workstation and one or more LANs. The workstation can dial the LAN, but the LAN cannot dial the workstation. You must use a Hayes or Hayes-compatible modem and a 78010 Tap at each LAN you want to call. You must have a second Hayes or Hayes-compatible modem, installed under Windows and connected to the workstation.

Define the phone numbers for the PC using the Phone Numbers editor. This editor is only be available if your Link type, defined in Configure, is Integrated Dial or Integrated NPR Dial.

You must configure the modems attached at the call initiating end (modem connected to the host PC) and the call receiving end (78010 Tap on the controller LAN) so they communicate with each other. Refer to the “Communication” chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for the necessary modem switch settings.

Define the address, name, and telephone number of up to 64 remote sites per host.

1. Select Edit Host Computer Phone numbers from the main menu. The system displays the Phone Number editor (see Figure 3-2).

This editor allows you to add, delete, modify, or copy phone numbers. This editor also lists the remote sites you can access from this host. If you have not added any sites, the fields are blank.

2. Select Add. The system displays the Phone Numbers - Add editor (see Figure 3-3).

3. Enter an Index number. This number controls the order in which the phone numbers are displayed in the editor.

4. Enter a Name for the remote site (up to 16 characters).

5. Specify the Phone number (up to 31 characters). Start the number with a “T” for tone dialing. No “T” indicates pulse dialing. Use a comma to indicate a two-second pause.



78060 and 78061 Tap ConfigurationThese Taps provide two-way communication between one or more controller LANs and a PC using a 7804x Tap, or between the controller LANs and a host LAN using a 7805x Tap.

1. Ensure you are connected to a site (i.e., a controller LAN) through a 78040/1 or 78050/1 Tap, or through an Ethernet connection.

2. Depending on your connection to the site and your worksta-tion's configuration, use one of the following methods to access the Site Tap Configuration editor:

✧ Select Edit Tap LAN from the main menu.

Figure 3-2. Phone Numbers Editor

Figure 3-3. Phone Numbers - Add Editor



✧ Select Edit Tap Remote Site Tap Configuration from the main menu. Then choose a device from the Dial Tap Selection editor.

✧ Select Edit Remote Site Tap Configuration from the main menu. Then choose a device from the Dial Tap Selection editor.

The first part of the screen is similar to the configuration screens for other Tap types. Complete the Tap Details and Distribution Parameters just as you would for any other Tap.

3. The Group Details panel allows you to establish group param-eters. In the Telephone Number Details you will link each phone number to one of these groups. This capability links specific phone numbers with specific alarm message types. You may define up to eight groups.

Figure 3-4. 78060/1 Tap Configuration Editor



Assign a system address (0–99) to the Link for each group you wish to define. The system link address must be the same as that defined in the Configure program for a 7804x or 7805x Tap, if you want to receive on-line messages.

4. Set the Dial mask positions for each group you wish to define.

5. You may specify up to eight phone numbers in the Telephone Number Details. Each phone number may use up to 31 char-acters (this includes any commas or “T” characters in the number). To add a new number, select Add.

6. The Telephone Number Details editor appears. Select the Group to which you want to link this phone number.

You may link all eight available phone numbers to one group, or you may have one phone number per group, or any combi-nation in between. You may not, however, have more than eight groups or eight phone numbers.

7. Select the Type of connection to be made. Available options include a variety of baud rates (the highest currently available is 9600) and a Beeper type.

8. Use the Timeout field to define the number of seconds (30 or 60) the Tap waits when calling out before hanging up if a connection is not made.

9. Enter the Telephone number for the connection.

The number must match the telephone number of the 7804x or 7805x Tap entered in the Network Configuration editor.

Site Tap Save / Restore

The Site Tap Save and Site Tap Restore functions allow you to save the Tap configuration to a file and restore the configuration at a later time, much like the Station Save and Restore functions at the controller level.

Note: You must be connected to the Site Tap to perform these functions.



To save the file, click the Site Tap Save button on the Taps toolbar. A dialog box will ask you to confirm the request. Click Yes to save the file.

To restore the configuration, click the Site Tap Restore button on the Taps toolbar. A dialog box will ask you to confirm the request. Click Yes to perform the restore.

Printer TapThe Printer Tap allows messages to be printed directly from a controller LAN or host LAN without the use of a host PC. Use the following procedure to configure a Printer Tap. You must be connected to the Printer Tap.

1. Select Edit Tap Printer from the main menu. The system displays the Printer Tap Configuration editor.

2. Enter the Tap name (up to 16 characters).

3. The Firmware Status panel shows the current revision number and date the revision occurred. These fields are display only, you cannot edit them.

4. Using the spindial, choose a Baud rate.

5. Choose a CTS handshake.

6. Using the spindial choose the number of Data bits.

7. Using the spindial choose the number of Stop bits.

8. Choose a Parity from the drop-down list.

9. Set the Group masks as required to determine the masking filter for all messages, alarms, or transactions to be printed.

10. Click OK to save the settings and exit this procedure.


Tap Configuration Multiple Site Dial

Multiple Site Dial

The multiple site dial feature of TAC I/NET Seven allows you to connect to multiple dial sites at one time from a graphic system page. Each site must have been previously defined and saved in the Network Configuration editor. You may make these connections by double-clicking graphic dial icons on graphic pages.

For more information about this function, refer to “Adding Multiple Site Dial” on page 8-68.


C H A P T E R28

4

© 2001–2010 SchTCON299–05/10

Controller Configuration

Controller Configuration/Status

The Controller Configuration/Status editor lets you display and edit various parameters associated with each selected controller.

Configuring the ControllerUse the following procedures to configure the controller. Refer to the Controller Functions chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for additional information.

1. Select Connect or click the Connect tool on the Connect toolbar. The system displays a list of available links or control-lers, depending on your configuration. Select a link and click OK.

Note: Links that are not currently available, are displayed with an asterisk to the left of the link name.

If you selected a link from the list, you are now connected to that link. If you selected a controller, then you are now connected to that controller and you may skip step 2 (go to step 3).

2. Select Connect again. The system displays a list of available controllers. Select one and click OK. You are now connected to a controller.

3. Select Edit Controller Configuration from the main menu or click the Configuration tool on the Controller toolbar. The system displays the DCU Configuration editor (see Figure 4-1).

4. Configure the following parameters:


Controller Configuration/Status Controller Configuration

✧ Controller Details

✧ Distribution Parameters

✧ Sunrise/Sunset

✧ Daylight Savings

✧ Program Extensions

Procedures for configuring these parameters are described below.

5. Use the following parameters for informational purposes only:

✧ Memory Status

✧ Database Last Changed

✧ Loading Details

Figure 4-1. DCU Configuration editor


Controller Configuration Controller Configuration/Status

✧ Firmware Status

✧ Controller Memory

These parameters are described below, following these proce-dures.

6. Select OK to accept your changes and to leave the DCU Configuration editor.

Controller Details

Use the following steps to configure controller details:

1. Enter a Name for the controller. Use up to 16 characters. The default name for each device is the controller type (i.e. DCU 7716). If the device is downloadable and has not been down-loaded with firmware, the text “boot” appears next to the type (i.e. DCU 7716 Boot).

2. Enter a Date. This field shows the current date according to the controller. This date matches the date on the PC if you perform a station restore. If you wish to change the date, enter it in mm/dd/yy (month/day/year) format.

3. Select Download Date. The date is immediately downloaded to the controller.

4. Enter the Time. This field shows the current time according to the controller. The time is entered in 24-hour (military) format. AM hours are entered as the regular time. PM hours are entered as the time plus 12 hours.

For example, 3 p.m. is entered as 15:00:00 (3 + 12 = 15). 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 PC. This is important to remember if your PC 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.

5. Select Download Time. The time is immediately downloaded to the controller.



Distribution Parameters

Use the following steps to configure distribution parameters:

1. Choose a Distribution Group. 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. When a message is sent from a DCU to a host, it must match a message mask in the assigned distribution group. Each distri-bution group may contain up to eight masks.

Note: Dial Taps are only capable of generating AD/AA messages with masks from distribution Group 1.

2. Define a Message Mask. This option lets you determine which PC stations receive messages from this controller.

There are eight available mask positions. The only require-ment is that at least one mask position and the distribution group selected for this controller must match a masking posi-tion and distribution group selected in the host configuration editor. If any of the eight mask positions assigned to the controller match any of the eight mask positions entered for the host, and the masks are in the same group, the host will receive the message.

The default for each of the eight positions is deactivated (). Before you activate masking positions here, you should know your system configuration in order to create the appropriate matching masking patterns. Activate () the appropriate masking positions.

3. Choose a Message Priority from the drop-down list. There are three priority levels: Routine, Priority, and Critical. A selection of None indicates no priority. This only prevents controller messages (such as power failure, sign-on, sign-off, etc.) from being sent to the host. All point-related messages may still be received at the host.



The level you assign here refers 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 after the dial Tap’s Percent Full limit is reached or the Time Interval has transpired.

✧ Critical – Report the message immediately.

4. If the controller is loaded with firmware dated 08/21/06 or later, you can implement reliable messaging by specifying a Reliable Tap. Refer to Reliable Messaging in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about this TAC I/NET Seven feature.

Sunrise/Sunset

cSunrise and sunset are automatically calculated from the informa-tion you enter here as well as the information in the next section titled Daylight Savings. Use the following steps to enter the longi-tude, latitude, and time zone of the controller.

1. Enter Longitude in degrees, minutes, and direction (west or east).

2. Enter Latitude in degrees, minutes, and direction (north or south). This feature does not work above latitudes of 68 degrees north or below 68 degrees south.

3. Enter a Time zone between 1 and 24. Time zones begin at Greenwich, England (Greenwich Mean Time - zone 1) and increase from east to west. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for a time zone world map. Enter zero here to disable this function. Enter a decimal number for regions in half-time zones. TAC I/NET Seven rounds the number to the nearest half.



Longitude, latitude, and time zone information can be found in a variety of public places. Try newspapers, atlases, almanacs, and libraries.

Daylight Savings

Use the following steps to enter daylight savings data.

1. Enter the Begin date. Enter the month (1-12), week (1-5), and day (1-7) daylight savings time begins (Standard Time ends). On that date at 2:00 a.m. (02:00), the DCU clock moves ahead one hour.

Use the following guidelines for setting the date:

2. Enter the End date. Follow the procedure described above to enter the month, week, and day the DCU clock moves back one hour and return to Standard Time. This process occurs at 2:00 a.m. (02:00) on the specified day.

Program Extensions

Use the following steps to define program extensions.

1. Activate () or deactivate () the Time scheduling exten-sion.

Month January is month 1, February is month 2, and so on, ending with December as month 12.

Week 1 Enter a 1 if the daylight savings start falls during the first seven days of the month (1-7).

Week 2 Enter a 2 if the daylight savings start falls during the second seven days of the month (8-14).

Week 3 Enter a 3 if the daylight savings start falls during the third seven days of the month (15-21).

Week 4 Enter a 4 if the daylight savings start falls during the fourth seven days of the month (22-28).

Week 5 Enter a 5 if the daylight savings start falls after the 28th day of the month.

Day Sunday is day 1, Monday is day 2, and so on, ending with Saturday as day 7.



When activated, all the time scheduling program extensions in this controller are stopped. Once activated, the controller looks back as far as midnight to determine the proper point state and during the next minute issues the proper command.

When time scheduling is deactivated and the controller has time scheduling programs defined, the individual loads remain in their state that existed when the program was turned off.

2. Activate () Temperature Control to turn the temperature control program extensions in this controller On. Deactivate () to turn the temperature control program extensions Off.

3. Activate () or deactivate () the Demand control exten-sion.

If you select the deactivated state, the demand program stops. 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 KWH data and predict KW demand values.

4. Activate () or deactivate () the All Lights On/Off exten-sion (available on the 7780 controller only).

This performs the same function as codes 8 and 9 on the hand-held console. Activating () All Lights On enables input address 0000 to be used to energize all associated RR7 relays. Activating All Lights Off enables input point address 0001 to be used to deenergize all associated RR7 relays. This function does not permanently override lighting circuit control commands. Even after an All Lights On/Off command has been issued, the lighting zone can still issue controls to the lighting circuit.

Note: When using “All Lights On/Off”, input 0000DI and 0001DI should not be used for any other input point. If you do, lighting control will not be as expected.

5. If the controller is an ICI (I/NET Communications Interface), select the ICI controller type from the drop-down box.



Viewing Controller StatusIn addition to configuring the controller, use the DCU Configura-tion editor to view controller status. The following controller infor-mation is available from the DCU Configuration editor.

Memory Status

These fields are informational only. You cannot make changes. The Total Bytes Available field shows the total memory space available in the controller for your modifications and additions. The Bytes remaining field shows the unused memory space. Not all unused memory is available for use.

Database Last Changed

These fields are informational only. You cannot make changes. The Save file field shows the date of the most recent Station Save. The Controller field shows the date of the most recent changes. Changes that have not been saved are displayed with an asterisk.

Loading Details

Note: This field contains information that is usually of interest only to high-level users. This information can also be obtained using the hand-held console.

These fields are display only. You cannot make changes. The first field shows the controller Processor % loading (0-100%). This is simply an indication of how busy the controller is. If this number is 100, control actions which are supposed to occur are lost or delayed. The second field, LAN % loading, shows the percentage of controller LAN communication attributable to this controller.

Firmware StatusThese fields are informational only. You cannot make changes. These fields list the revision number and date of the firmware installed in the controller.


Controller Configuration Editing the Database while Offline

Controller Memory

Note: This field contains information that is usually of interest only to high-level users. This information can also be obtained using the hand-held console.

Address lets you specify a memory address (up to four characters) and Contents displays the location value (0000-FFFF) within the controller. You cannot control the value, you can only display it.

Editing the Database while Offline

TAC I/NET Seven allows you to add controllers, and copy or edit controller databases when you are not actually connected to the controllers. This will allow DCU parameters, Host Access Control parameters, Host parameters and Graphics pages to be created, added and/or modified without a physical connection.

Before attempting to perform offline edits of your database, you should ensure that the latest version of the .SAV file is present on the client from which you will be performing the edits. To down-load the .SAV file, perform a Station Save. For more information on Station Saves, refer to “Station Save and Restore” on page 4-12.

To perform edits while in offline mode, select System Work Offline.

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


Editing the Database while Offline Controller Configuration

Once you have highlighted the file you wish to edit and pressed OK, select Edit from the main menu and choose either Host Computer or Controller. You may then select the editor you wish to modify using the sub-menus presented in the same way you would when operating in Online mode.

Once you have finished modifying your .SAV files, perform a Station Restore to have the changes applied globally. For more information on Station Restores, please see “Station Save and Restore” on page 4-12.

Adding a .SAV File Offline

To add a .SAV file to the system directory while working in offline mode, select Add from the Connect Offline dialog. You must provide a Link number, Station number, controller type, and enter the number of stations before the file can be created.

1. Either manually enter or use the spin dials to select the Link number. The Link number must be between 00 and 99.

2. Either manually enter or use the spin dials to select the Station number. The Station number must be between 00 and 63.

Figure 4-2. Connect Offline Dialog


Controller Configuration Editing the Database while Offline

3. Using the drop-down list box, select the appropriate DCU type from the list of those available.

4. Either manually enter or use the spin dials to select the number of stations you wish to assign for your DCU type. The maximum number of stations available is dependant on the type of DCU you have selected. Refer to the table below for more information.

Figure 4-3. Offline Add Dialog

Table 4-1. DCU Type Stations Available

Offset DCU Type Max Stations

0 7700 DCU 1

1 7750 ORB 2

2 7730 DCU 8

3 7760 UCI 1

4 7720 DCU 2

5 7770 ICI 1

6 7810 Tap 1

7 7716 PCU 1

8 7780 LCU 1

9 7718 PCU 1

10 7792 MRI 2

11 7791 DPI 1

12 7797 ICI 8

13 7728 PCU 1

14 7793 MCI 2


Station Save and Restore Controller Configuration

Deleting a .SAV File Offline

To delete a .SAV file while working offline, select Delete from the Connect Offline dialog. You will be prompted to confirm your choice before the file is deleted.

Copying a .SAV File Offline

To copy a .SAV file while working offline, select Copy from the Connect Offline dialog. This allows you to duplicate an existing .SAV file with a new Link and/or Station number. If a file with the same Link and Station number exists, you will be prompted to replace the existing file.

Station Save and Restore

This facility lets you save/restore controller database modifications to/from the host PC. Automatic controller save is also available (refer to Chapter 2, Setup and Network Configuration). Station restore is used to restore a database to the controller from a previ-ously saved version. This may be necessary if the database has been

15 7798 MCI 1

16 7756 PCU 1

Figure 4-4. Offline Copy Dialog

Table 4-1. DCU Type Stations Available

Offset DCU Type Max Stations


Controller Configuration Station Save and Restore

corrupted following power outages that outlast the controller battery's ability to retain memory or for large scale recurrent seasonal changes to the controller that may be necessary at your facility.

Station SaveOnce modifications have been made to a controller database, save the modifications to the Host PC’s hard disk or a diskette using the following procedure:

1. Connect to the controller that has been modified.

2. Select Edit Controller Station Save, or click the Station Save tool on the Controller toolbar. The system displays the following prompt:

Are you sure you want to save station XXX?

3. The default is Yes. Select Yes to perform the save.

The default Save directory is defined in TAC I/NET Seven’s Config-uration program. The length of time the system needs to perform the save is determined by a number of factors. If you are performing the save through a modem, the save time increases. The baud rate affects the save time: slower baud rate = longer save time. Other factors also affect save time: LAN speed, number of points in the controller, number of time schedules, number of calculations, etc. The more points and point extensions associated with the controller, the longer the save time. 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 RestoreUse this option to cold start and 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. This avoids the time-consuming job of reentering the entire program. Taps, of course, do not require a database. After the station restore, the last saved version of the programming can be restored to the controller (refer to “Software Restore” on page 4-15).

Perform a station restore using the following procedure:


Station Save and Restore Controller Configuration

1. Connect to the controller to be restored.

2. Select Edit Controller Station Restore, or click the Station Restore tool on the Controller toolbar. The system displays the following prompt:

Are you sure you want to restore station XXX?

3. The default is Yes. Select Yes to perform the restore.

The restore procedure uses the Save directory specified in the Configure program. The same factors that increase the duration of a station save will have the same effect on a station restore.

Station Restore on a DPI

When you perform a station restore on a DPI, this cold starts the DPI and then downloads the save file for the controller. This includes points, Access Initiated Control, and Elevator Data.

Station Restore on a DPU

When you perform a station restore on a DPU or SCU1284, this cold starts the device and then downloads all access control data from the host, including Individual Data, Tenants, and Translation table information. In addition, all points and extensions associated with the DPU/SCU including Door extension, Personnel sched-ules, and elevator extensions are downloaded from the DPI (not the host).

The Memory Interface Processor ModuleIf the controller has a Memory Interface Processor (MIP) card installed, you must download the controller’s software using the Software Restore function (refer to “Software Restore” on page 4-15). Some controller types, including the 7716, 7718, 7780, 7791,7792,7793, 7728, 7797, and all models of SCUs are built on downloadable platforms that enable them to receive a downloaded software file without a MIP. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for additional information concerning the MIP module.

Note: If you install a MIP card, LAN address 63 is no longer valid for the 7803 LAN tap and the 78061 dial tap.


Controller Configuration Software Restore

Software Restore

The Software Restore download capability is similar to the Station Restore option described above. While a station restore is used to restore just the controller database, the software restore can be used to restore the controller programming (firmware) and, if necessary, the controller database.

Controller database information is stored in .SAV files that are automatically created when you perform a controller save. If a .SAV file does not exist for a particular controller, then you can’t perform a database download.

Performing a Software Restore to Taps and ControllersSoftware for Taps and controllers is stored in binary files added to your system during the installation or upgrade process.

1. Select Edit Host Computer Software Restore, or click the Software Restore tool on the Controller toolbar. The system displays the Software Restore screen (see Figure 4-5).

Figure 4-5. Software Restore Screen


Software Restore Controller Configuration

This screen displays all the Taps and controllers that you previously defined as downloadable in the Network Defini-tion portion of the Network Configuration editor. Refer to Chapter 2, Setup and Network Configuration, in this manual for more information.

2. Use the Software and Database check boxes to control which stations receive a download. If you check Software, the selected station will receive a software download. If you check Database, the selected station will receive a database down-load.

You can use the SW Yes and DB Yes buttons to activate the Software and Database check boxes, respectively, for all stations. Use the All No button to deselect Software and Database for all stations.

3. If necessary, define the drive and path to the directory that contains the software to be restored in the Software Direc-tory field. By default, TAC I/NET Seven restores software from the Data directory defined in the Configure program.

4. If necessary, use the DPU/SCU button to select subLAN devices to receive software and/or database downloads. Refer to “Performing a Software Restore to DPUs and SCUs” on page 4-17 for instructions on how to restore software in a subLAN device.

5. When you have selected the necessary stations, select Down-load to begin the software restore process.

The system begins downloading binary files to stations that have a Y in the Software column. Database .SAV files are downloaded to stations that have a Y in the Database column.

6. Select Close to leave the Software Restore screen. If the soft-ware restore is still running, it will continue until completed.

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 check box in the Software or Database column


Controller Configuration Software Restore

clears, meaning you have just completed the download and there is nothing more to download. If you try to download a controller database and the check box does not clear 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 Save 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.

Performing a Software Restore to DPUs and SCUsTAC I/NET Seven displays the DPU Software Restore editor (see Figure 4-6) when you select DPU/SCU from the Software Restore editor described above.

This editor operates similarly to the Software Restore editor. The only devices that are listed in this editor are DPU7920s that have a DPU48K add-on board installed, all models of SCUs, and OP5

Figure 4-6. DPU Software Restore Editor


Software Restore Controller Configuration

arming terminals. These devices must be saved in NETCON as downloadable before they will appear in the DPU Software Restore editor. Refer to “Adding an MCU” on page 2-25 for more informa-tion.

All three versions of the SCU (i.e., the SCU1200, SCU1280, and SCU1284) can be configured in NETCON as downloadable devices. Defining an SCU as downloadable allows it to be included in the DPU Software Restore editor. SCU1200 and SCU1280 controllers that you configure as downloadable, though not func-tioning as door processing units, will also be included in the DPU Software Restore editor’s list of downloadable devices.

Use the following procedures to perform a software restore to DPUs and SCUs.

1. Use the Software and Database check boxes to control which devices receive a download. The Database check boxes are not provided for SCU1200 and SCU1280 controllers since these devices do not store access control databases.

If you check Software, the selected device will receive a soft-ware download. If you check Database, the selected device will receive a database download.

You can use the SW Yes and DB Yes buttons to activate the Software and Database check boxes, respectively, for all devices. Use the All No button to deselect Software and Data-base for all devices.

2. When you have selected the necessary DPUs, SCUs, and OP5s, select Download to begin the software restore process.

3. The system begins downloading binary files to devices that have a Y in the Software column. Database .SAV files are downloaded to devices that have a Y in the Database column.

4. Select Close to leave the DPU Software Restore editor. If the software restore is still running, it will continue until completed.


Controller Configuration Dynamic Data Upload

Dynamic Data Upload

This option lets you upload the latest midnight SevenTrends data for demand, override billing, consumption, and runtime statistics to the appropriate SevenTrends tables in the host.

Select Edit Controller Dynamic Data Upload, or click the Dynamic Data Upload tool on the Controller toolbar. The following message appears:

Dynamic data upload request has been initiated

This option executes within 60 seconds of starting the upload.

Note: Each time you exercise this option a copy of the midnight data is placed in the SevenTrends tables. This can cause duplicate data in SevenTrends reports. Make sure the data has not been automatically uploaded before exercising this option.

Defining and Entering Station Parameters

This section describes how to create, enter, and implement a working database in a controller. Station parameter data is entered into the controller using the following editors:

✦ Control Descriptions editor

✦ State Descriptions editor

✦ Conversion Coefficients editor

✦ Engineering Units editor

✦ Look-up Tables editor (7716, 7718, 7728, and 7756 controllers only)

There is no substitute for thorough planning and record keeping in the development and maintenance of your TAC I/NET Seven system controller database. Once the database is entered into the controller, any additions, deletions, or modifications can be saved using the Station Save function. However, we recommend that you always keep written notes of these modifications.


Defining and Entering Station Parameters Controller Configuration

As with other data entry processes we recommend you use the forms located in TCON157, TAC I/NET Seven Forms and Work-sheets. There are four main station parameter forms corresponding to the first four station parameter categories described above. These forms are referred to frequently throughout the remainder of this chapter. We suggest you make extra copies of the forms (be sure to keep one copy for an original) to use as work sheets when plan-ning your database. The last station parameters editor, Lookup Tables, is used only with the 7716, 7718, and 7728 controllers.

Entering the Station ParametersOnce you have designed the database for your facility using the forms discussed above, you are ready to use the editors to enter the station parameters and create the database. Refer to the Controller Functions chapter in TCON300, TAC I/NET Seven Technical Refer-ence Guide, for a description of parameters used in the editors.

Make sure you are connected to the desired controller. If not, make the necessary connections. Follow your worksheet and make the appropriate entries using the procedures described below.

Control Descriptions and Commands

Use the Control Descriptions form as you go through this section.

1. Select Edit Controller Station Parameters Control Descriptions, or click the Control Descriptions tool on the Station Parameters toolbar. The system displays the editor shown in Figure 4-7.

2. Enter a control Description. Use up to four alphanumeric characters. The first control description should always be the start command of the pair, followed by the stop command.

3. Enter a time Delay from 0 to 127 seconds. This delay is honored between multiple automatic control actions that use the same control entry, when they are issued at the same time.

Note: You should not use Control Command Delays on VAV-UC, AHU-UC, or HPMP-UC parent points, as well as the UC Pushbutton Override Indicator point.


Controller Configuration Defining and Entering Station Parameters

4. Activate the appropriate control Command. (0 = de-ener-gized output, 1 = energized output)

5. Repeat the steps above to define up to eight pairs of commands.

6. Select OK to leave the editor.

Note: You must enter a set of three state descriptions in your 7791 DPI or 7793 MCI. These are SECR, UNLK, and LOCK. They describe a three-state door point.

State Descriptions

Using the State Descriptions form as a worksheet, enter up to sixteen pairs of descriptors. These are associated with various discrete input and output points to describe the current state of the device being controlled or monitored.

1. Select Edit Controller Station Parameters State Descriptions, or click the State Descriptions tool on the Station Parameters toolbar. The system displays the editor shown in Figure 4-8.

2. Enter a state Description. Use up to four alphanumeric char-acters.

Figure 4-7. Control Descriptions and Commands



The first descriptor of the pair should describe the “trip” or the de-energized (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 “close” or energized (1) condition of a discrete output point or the “closed” (1) condition of a status point.

3. Use the steps above to define up to 16 pairs of descriptions.

4. When you are finished, select OK to save the descriptions and leave the editor.

Note: You must enter a set of three state descriptions in your 7791 DPI or 7793 MCI. These are SECR, UNLK, and LOCK. They describe a three-state door point and require Command to be set to 0.

It is important to make these descriptors as definitive as possible since they appear on the graphic system pages along with the asso-ciated point icons. They also appear in a controller or Page summary display (refer to Chapter 8, System Pages) and are stored and/or printed when an alarm or state change occurs.

Figure 4-8. State Descriptions



Conversion CoefficientsConversion coefficients are the mathematical constants the controller uses to convert analog inputs or outputs from the digital value used by the microprocessor to analog display values. They are also used to convert digital commands from the microprocessor into analog outputs which are then used by field interface devices. You may enter up to 16 sets of conversion coefficients in each controller.

1. Select Edit Controller Station Parameters Conversion Coefficients, or click the Conversion Coefficients tool on the Station Parameters toolbar. The system displays the Conver-sion Coefficients editor (see Figure 4-9).

2. Select the desired coefficient fields and enter the M Value and B Value conversion coefficients. If necessary, use the pop-up calculator to calculate the conversion coefficients. Refer to “Pop-up Calculator” below.

3. When you have finished entering conversion coefficients, select OK to save your changes and exit the editor.

Figure 4-9. Conversion Coefficients Editor



Pop-up Calculator

You have the option of using a pop-up calculator to help you calcu-late conversion coefficients.

1. From the Conversion Coefficients editor, select Calculate. The system displays the Conversion Coefficients Calculator (see Figure 4-10).

2. Choose a Coefficient Index. This determines which line in the Conversion Coefficients editor will receive the resulting M and B values of this calculation.

3. Choose the desired type of Conversion Equation — either Linear or Flow.

4. Enter an Equipment counts low value. This can be a number from 0 to 65,535. Typically, this number is zero.

5. Enter an Equipment counts high value. This can be a number from 0 to 65,535. For analog inputs, use the following values:

✧ For a 16-bit A/D converter (used on the lower I/O board of the 7756 PCU), enter 65,535.

✧ For a 12-bit A/D converter (used in all other controllers except MCUs), enter 4095.

✧ For an 8-bit A/D converter (used in MRs and UCs), enter 255.

Figure 4-10. Pop-up Calculator



Analog outputs use 8-bit D/A converters with a low count of zero and a high count of 255.

6. Enter an Engineering units low value. This parameter repre-sents the lowest value (measured in engineering units — degrees, volts, amperes, etc.) for the sensor when the device is at its low count value.

Example:

A Lini-Temp sensor which operates between –40F (2.33 volts) and +230F (3.83 volts), reads –459.4F at zero volts (0 counts) and +440.6F at 5 volts (4095 counts). This example assumes an AI input of 0 to 5 VDC.

7. Enter an Engineering units high value. This parameter represents the highest value (measured in engineering units) for the sensor when the device is at its high count value.

8. Select OK to calculate the M and B values and exit the pop-up calculator. The system displays the window shown in Figure 4-11.

9. To accept the resulting values, select OK. The resulting values are automatically entered in the Conversion Coefficients editor.

Engineering UnitsThis feature lets you define the units of measure for analog input/output points and accumulator points. These descriptions only appear in point-related alarms or messages stored in the system message queue or printed on the system printer.

Figure 4-11. Pop-up Calculator Results



1. Select Edit Controller Station Parameters Engi-neering Units, or click the Engineering Units tool on the Station Parameters toolbar. The system displays the Engi-neering Units editor (see Figure 4-12).

2. Enter up to 16 engineering units. Each engineering unit may be up to 4 characters.

3. Select OK to save your changes and exit the editor.

Lookup TablesThe 7718, 7716, 7756, and 7728 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.

1. Calculate lookup table entries using the worksheet in TCON157, TAC I/NET Seven Forms and Worksheets, and the procedures in TCON300, TAC I/NET Seven Technical Refer-ence Guide.

Figure 4-12. Engineering Units Editor



2. Ensure you are connected to a 7716, 7718, 7756, or 7728 controller.

3. Select Edit Controller Station Parameters Lookup Tables, or click the Lookup Tables tool on the Station Param-eters toolbar. The system displays the Lookup Table editor (see Figure 4-13).

Figure 4-13. Lookup Table Definitions



4. Highlight the desired point from the list and select Add. The system displays the Lookup Table Definition editor (see Figure 4-14).

5. Enter a Counts value. Only integers may be entered in the lookup table. You may place count values in any order, the editor will sort the entries numerically in order.

6. Enter the Adj. Count value. Adjusted counts may be an increasing or decreasing slope.

7. Repeat Steps 5 and 6 as necessary for up to 31 lookup table entries.

8. When you are finished building the lookup table, select OK.

9. Repeat Steps 4 through 8 as necessary for each point.

10. Select Close to exit the Lookup Table editor.

Figure 4-14. Lookup Tables editor


C H A P T E R6

5

© 2001–2010 SchTCON299–05/10

Point Definition and Addressing

Adding Points to Your Controller

The following steps describe how to access the Resident I/O Points editor and add points to your controller. Also, refer to the Input and Output Points chapter in TCON300, TAC I/NET Seven Tech-nical Reference Guide, for additional information.

1. Connect to the controller where you want to add points.

2. Select Edit Controller Resident I/O Points, or click the Resident I/O Points tool on the Controller toolbar. The system displays the Resident I/O Point editor (see Figure 5-1).

Figure 5-1. Resident I/O Points Editor


Adding Points to Your Controller Point Definition and Addressing

This screen displays all the points currently defined in this controller. The display lists the point address, type, class, and name. If point extensions have been added to the point, a Y is displayed in the column under that extension. No points are listed if you have not yet added any points to this controller.

3. Select Add. The system displays the New Resident Point editor (see Figure 5-2).

4. Define the point address. Since you are already connected to the link and station, you only need to enter the last four digits of the point address (point and bit offset).

5. Choose a point type from the drop-down list.

6. Select OK. The system automatically displays the appropriate edit screen for the point type you select.

7. Enter the parameters for the point. Refer to the appropriate chapters in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about each parameter.

Note: We recommend that you complete the forms in TCON 157, Forms and Worksheets, to plan and document your TAC I/NET Seven system. If you do, you can use the information on your form as a guide for the point parameters.

8. When you finish, select OK to return to the Resident I/O Points editor. The new point is added to the list. The points are ordered by their address; not by the order in which they are added to the controller.

Figure 5-2. New Resident Point Editor


Point Definition and Addressing Modifying Points in Your Controller

Modifying Points in Your Controller

The following steps describe how to modify existing points.

1. Connect to the controller containing the points you want to modify.

2. Select Edit Controller Resident I/O Points, or click the Resident I/O Points tool on the Controller toolbar. The system displays the Resident I/O Points editor (see Figure 5-1).

3. Select the desired point and click Modify. The system displays the editor associated with the point.

4. Modify the point as necessary. Select OK when you finish to return to the Resident I/O Points screen.

You can continue to add, delete, copy, or modify points, or you can select Close to leave the Resident I/O Points editor.

Copying Points in Your Controller

The following steps describe how to copy an existing point. This function is extremely useful when you are adding a number of points with similar parameters. In this case you simply add the first point and then copy it as many times as necessary, making the necessary parameter changes to each copied point rather than reen-tering identical information for a number of points.

1. Make sure you are connected to the controller where want to copy a point.

2. Select Edit Controller Resident I/O Points or click the Resident I/O Point tool on the Controller toolbar. The system displays the Resident I/O Points editor (see Figure 5-1).

3. Highlight the desired source point and select Copy. The system displays the Copy editor (see Figure 5-3).


Deleting Points from Your Controller Point Definition and Addressing

4. Define the new target point address to which you will be copying the existing point. Since you are already connected to the link and station, you need only enter the last four digits of the point address (point and bit offset).

5. Select OK. The system automatically displays the appropriate edit screen for the point type. Refer to the appropriate chap-ters in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about each parameter.

6. Modify the parameters as necessary and select OK to return to the Resident I/O Point editor.

7. You can continue to add, delete, copy, or modify points at this time, or select Close to exit the Resident I/O Point editor.

Deleting Points from Your Controller

The following steps describe how to delete a point from your controller.

1. Make sure you are connected to the controller containing the point you want to delete.

2. Select Edit Controller Resident I/O Points, or click the Resident I/O Point tool on the Controller toolbar. The system displays the Resident I/O Point editor (see Figure 5-1).

3. Select the desired point and click Delete. The system displays a Delete confirmation dialog box.

Figure 5-3. Copy Resident Point Editor


Point Definition and Addressing Sorting Points in Your Controller

4. Select Yes to delete the point or select No to cancel the Delete function.

5. You can continue to add, delete, copy, or modify points, or select Close to leave the Resident I/O Points editor.

Sorting Points in Your Controller

The Resident I/O Point editor allows you to sort the point list by either the point address or the point name. Selecting Sort causes the system to display the dialog box shown in Figure 5-4.

1. Chose the sort order you desire, either Point number or Point name.

2. Click OK. The Resident I/O point editor will display the avail-able points in the chosen sort order.

Input/Output and Addressing

Each controller has a certain number of available inputs and outputs. Inputs and outputs are further broken down into discrete, PWM, analog, and pulse categories.

Each point is assigned an eight-digit point address composed of link, station, point, and bit offset number. The first pair of digits designates the link, the second pair of digits designates the station, the third pair designates the point, and the last pair designates the bit offset. Refer to the chapter dealing with input and output points in TCON300, TAC I/NET Seven Technical Reference Guide. Also, refer to Chapter 1, TAC I/NET Seven Basics, in this manual.

Figure 5-4. Point Sort


Input/Output and Addressing Point Definition and Addressing

Tips for Point Addresses✦ Assign software points to any bit offset address. You may also

assign a software point to a hardware address if it is not needed for a hardware point.

✦ At any given address there may be one input and one output point.


C H A P T E R58

6

© 2001–2010 SchTCON299–05/10

System Messages

System messages provide information on events occurring in the system. System messages include normal messages, alarms, and transactions. For example, a message can be generated when an operator logs on, when a point changes state, or when an alarm occurs. Transactions are messages that are generated by the key/card readers.

TAC I/NET Seven’s system messages are controlled by the AMT application (Alarms, Messages and Transactions). AMT is a sepa-rate application that allows you to monitor messages, alarms, and transactions that occur within your TAC I/NET Seven system. The AMT application may start and stop automatically every time you launch and exit TAC I/NET Seven, depending on the setting in the Host Configuration editor (see “Host Configuration” in Chapter 2, Setup and Network Configuration).

Note: When you use the Windows Control Panel to change your system's regional date and time format, the changes are immediately viewable within AMT. However, AMT printed output will not reflect date and time format changes until after the host workstation has been rebooted.

AMT provides two types of windows: alarm and event. Predefined filters allow you to view Messages, Routine Alarms, Priority Alarms, Critical Alarms, and access control Transactions, just as in previous versions of TAC I/NET. You may choose to display all, a few, or none of these windows, and to customize the display of each. You may also minimize AMT to the task bar and open it only when you need to view system messages.


System Messages


Operator access to AMT windows and certain functions is depen-dent upon the privileges granted in the host passwords editor. (Refer to “Host Passwords” in Chapter 9, Passwords.) If an operator does not have access to view a specific window, the window does not display, and functions specific to the window are grayed out.

Message priority assignments control when messages and alarms are relayed to host workstations. Although they are controlled separately, both messages and alarms can fall into one of three cate-gories: Routine, Priority, and Critical. None (–) indicates no priority. The following tables detail how each priority level is handled by the three different types of Taps: Integrated Dial, Auto Dial/Auto Answer, and Direct Connect.

Table 6-1. Integrated Dial Taps

Priority Tap Action

Routine Message is ignored.

PriorityMessage is passed when a connection is established by the host.

CriticalMessage is passed when a connection is established by the host.

Table 6-2. Auto Dial /Auto Answer Taps (AD/AA)

Priority Tap Action

Routine Message is ignored.

PriorityMessage is passed when the dial parameters are met or critical message triggers an auto dial.

Critical Triggers an auto dial connection and message is passed immediately. Priority messages will also be passed.


System Messages AMT Menus and Toolbar

AMT Menus and Toolbar

AMT has its own set of menus and a toolbar that cannot be accessed from within TAC I/NET Seven. All menu commands or toolbar choices presented in this chapter are located on the AMT menu (or toolbar).

As in TAC I/NET Seven, many of the commands available on the menus are also available on the toolbar. You may choose to display the toolbar by selecting View Toolbar, from the AMT menu. Like TAC I/NET Seven toolbars, the AMT toolbar can be docked or floating. For assistance with manipulating toolbars refer to “Arranging Toolbars” in Chapter 1, TAC I/NET Seven Basics.

Also like TAC I/NET Seven, you may choose to remove the status bar located at the bottom of the main AMT window. Select View. A checkmark next to the Status Bar option indicates that the status bar is displayed. Click Status Bar to remove the checkmark. If you wish to display the status bar, select View Status Bar again.

Some AMT menu items are context-dependent. That is, the func-tions of certain menu items will vary, depending upon whether you selected an alarm, a message, or a transaction. Other menu items, and their corresponding toolbar buttons, that are not applicable to the selected item will be grayed out. Also, if an individual operator does not have access to a specific function, the menu option, and any toolbar button, will be grayed out.

AMT saves the configuration 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 “AMT Configuration” on page 6-4):

Table 6-3. Direct Connect Tap

Priority Tap Action

Routine Message is passed immediately.

Priority Message is passed immediately.

Critical Message is passed immediately.


AMT Configuration System Messages

✧ Alarm and archive color settings

✧ Toolbar and status bar settings

✧ Alarm topmost setting

✦ Settings for open windows:

✧ Size and placement

✧ Window options, including window name and filter selection (see “Window Options” on page 6-18)

✧ Auto-image verification window settings, including door filter and field selection, for open event windows (see “Image Verification” on page 6-42)

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.

AMT Configuration

Note: This configuration is not the same as the I/NET Configure program. Changes made on this screen take place immediately when you select OK to exit the screen. It is not necessary to exit the program for the changes to go into effect.

The AMT Configuration Editor, shown in Figure 6-1, allows you to set your AMT preferences. You can control the alarm and archive colors, establish audible alarms and select .WAV sound files to play for the various alarm types, and define message masks.

To access the editor, select Edit Configuration.

The Configuration editor is divided into six panels. The options in each panel are described below.

MiscellaneousThe Miscellaneous panel allows you to choose the manner in which the alarm notification window displays when a new alarm is received and to view the maximum number of online events (x1000) at any given time.


System Messages AMT Configuration

If desired, check the box for Display site address 0 as blank. This option will leave the site address field in AMT windows blank if the site address is zero (0).

You may check the box for Alarm topmost in order to have the alarm notification window always brought to the top for imme-diate attention and convenience when a new alarm arrives. If you uncheck the box and have minimized the alarm notification window, the window will remain minimized in the system tray and will flash when a new alarm arrives.

The Max Online Events field shows the upper limit for events stored online, in thousands (an entry of 100 indicates 100,000 online events). Once this number is reached, old events are replaced by new ones, on a “first-in, first-out” basis, and can no longer be viewed on the AMT screen.

Note: Archived events are not lost: they are still available for viewing and reporting purposes through a third-party software tool that supports SQL.

See Also: “Archives” on page 6-47

Figure 6-1. AMT Configuration Editor



Section on Archives in TCON300, TAC I/NET Seven Technical Reference Guide

Section on AMT Archives in TCON300, TAC I/NET Seven Technical Reference Guide

Alarm Colors and Archive ColorsThe Alarm Colors and Archive Colors panels allow you to set the text and background colors of alarm statuses and archives. Use the following steps to change the colors Alarm Colors:

1. Select the alarm type: Routine, Priority or Critical, using the drop down menu.

2. Click on the colored button under either Foreground or Background, depending on which you wish to change for the various alarm types, respectively.

The Color palette displays, as shown in Figure 6-2.

3. Select your color and click OK. The color you chose displays in the color panel.

To change the colors for Archive Colors, use the following steps:

Figure 6-2. Color Palette



1. Click on the colored button under either Foreground or Background, depending on which you wish to change. The Color palette displays (see Figure 6-2).

2. Select your color and click OK. The color you chose displays in the color panel.

Image WindowThis panel allows you to set a timer for the image verification window. Use the Image timer to set the length of time that the image verification window stays open after being automatically opened because of a transaction at a monitored door.

You can set a time of up to 60 minutes. A setting of zero causes the image verification window to stay open until it is manually closed by the operator.

Note: When you change the image timer setting, the previous setting remains in effect until a transaction causes a new image to display, or until you restart TAC I/NET Seven; whichever comes first.

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

✦ Return to normal ✦ Sign on Host

✦ Door normal ✦ Sign off Host

✦ Action message ✦ Sing on DCU

✦ Dispatch message ✦ Sign off DCU

✦ LAN reconfigure ✦ Host restored

✦ Station restored ✦ LAN tap restored

✦ MCU restored



Audible AlarmsThe Audible Alarms panel allows you to configure AMT to produce an audible alarm for routine, priority, and critical alarms. You may choose one of the following options:

✦ None—No audible alarm.

✦ Once—The alarm sounds once.

✦ Constant—The alarm sounds until it is acknowledged.

✦ Timed —The alarm sounds for the time specified in the Audible duration field.

The default setting for each alarm type is Once. To change this setting, perform the following steps:

1. Click the down-arrow on the appropriate drop-down box.

2. Select one of the other three options, None, Timed, or Constant.

3. If you select Timed, enter the number of seconds the alarm should sound in the Audible duration (sec) field. This setting will affect all alarms that are set to Timed.

A default .WAV sound file is supplied for each alarm priority. However, you may elect to assign a .WAV sound file of your own choosing to be played when an alarm of the appropriate priority is received. Please note that only .WAV sound files may be used for audible alarms.

To change the default .WAV sound file to one of your own choosing, perform either of the following:

✦ Enter the directory path to where your .WAV sound files are located. Example: C:\Sounds\Claxon.wav.

✦ Browse to the location where your .WAV sound files are located using the browse (...) buttons at the end of each field.

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 and Printer Masks

Note: AMT mask settings are ignored on a workstation set as a Remote Client in a client/server configuration. Only the AMT mask settings on the server will control what messages are received in AMT on the client. You can, however, use unique filter settings at the remote client to control what AMT messages are displayed.

Refer to Chapter 3, TAC I/NET Seven Configuration in TCON298, TAC I/NET Seven Getting Started, for more information about using a client/server configuration.

TAC I/NET Seven uses a filter system to determine where messages, alarms, and data from input/output points, controllers, and Taps are sent. These filters are known as masks.

A mask is an eight-position parameter with each position being either active () or inactive (). The message mask is assigned to one of four distribution groups. Distribution groups allow large systems considerable flexibility in assigning hosts to receive messages. The combination of distribution groups and masking positions allows for up to 32 different masks. Refer to the chapter dealing with system messages in TCON300, TAC I/NET Seven Technical Reference Guide, for a complete discussion of message masking.

Note: The far left masking position in distribution group 1 must be acti-vated in the printer and message masking configurations defined in the host configuration editor for system messages to be received at the host or the printer.

Set your masks for the host workstation by activating and deacti-vating the masking positions, as desired, for the following parame-ters.

✦ Message/Alarm — This parameter controls which messages are received at this host workstation. If there is not a matching group and mask position, the workstation ignores the message.


Managing Windows in AMT System Messages

✦ Printer — If you want to have messages and alarms automati-cally printed, set the Printer masks, as well. This option will route the matching messages and alarms directly to the printer attached to the host workstation.

✦ Force Dispatch — Select which mask positions will require a dispatch message on alarms. 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. The settings of these masks will be common among all equalized client workstations.

✦ Acknowledge Return-to-Normal — Select which mask posi-tions will require a separate acknowledgment for a return-to-normal message. 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. The settings of these masks will be common among all equalized client workstations.

Note: Although the Force Dispatch and Acknowledge Return-to-Normal mask settings are equalized, they are not globalized. This means that host workstations not using file equalization can have unique settings for these masks.

Therefore, even though your equalized host workstation may force you to dispatch a message when acknowledging an alarm, an oper-ator on a non-equalized workstation may be able to acknowledge the same alarm without dispatching a message.

Managing Windows in AMT

There are two basic window types in AMT, alarm windows and event windows. For each window type, there are some predefined windows that filter the message display for a specific type of message.

The AMT display can contain several windows at one time, each window showing different information. There are three ways to control which messages are displayed in each window:


System Messages Managing Windows in AMT

✦ Window Options allow you to select the way messages are displayed in the window. Refer to “Window Options” on page 6-18.

✦ Filters allow you to set parameters to determine which messages are displayed in the window. Refer to “Filters” on page 6-21.

✦ Predefined windows are either event or alarm windows with preselected window options and filters. Once the window is open, you may use the window options and/or filtering to change the display. Refer to “Predefined Windows” on page 6-12.

Opening a New AMT WindowThe messages in a window are listed chronologically, with more recent events listed first. Scroll down to see additional messages.

Alarm Window

Alarm windows display system alarms for points outside their defined “normal” boundaries. To open an alarm window:

1. Select System New Alarm Window.

2. Complete the Window Options editor to set the viewing options for the window. Refer to “Window Options” on page 6-18.

Note: Each alarm is also either a message or a transaction, but may not appear in the corresponding window due to filtering.

Event Window

Event windows display system messages (network activity) and transactions (access control and door activity).

1. Select System New Event Window.

2. Complete the Window Options editor to set the viewing options for the window. Refer to “Window Options” on page 6-18.



Predefined Windows

There are five predefined window types, corresponding to the static windows displayed in previous versions of TAC I/NET. Each predefined window shows all fields in the default order, and uses one of the system filters (see “Filters” on page 6-21).

When opening a pre-defined window type, the Window Options editor does not appear. You may manually open the Window Options editor to change the window settings.

Note: Below, toolbar icons are shown for each type of pre-defined window. As an alternative to using menus, you can simply click on an icon in the toolbar to quickly open a pre-defined window. If the icon you click is for a window type that is already open, the existing window will be brought to the top and will become active.

Routine Alarms

This window shows only alarms with a priority level of “Routine” in the editor generating the alarm. Select System New Routine Alarms Window.

Priority Alarms

This window shows only alarms with a priority level of “Priority” in the editor generating the alarm. Select System New Priority Alarms Window.

Critical Alarms

This window shows only alarms with a priority level of “Critical” in the editor generating the alarm. Select System New Critical Alarms Window.

Messages

This window shows all system message traffic, including alarms. Transactions are not included. Select System New Messages Window.



Transactions

This window shows only access-control related messages, including alarms. Other system messages are not included. Select System New Transactions Window.

Note: Each window can have only one filter. If you change the selected filter for a predefined window, it is no longer using the predefined filter. Refer to “Filters” on page 6-21 for more information.

Closing an AMT windowTo close any window in AMT, click the button marked X in the upper right hand corner of the window.

Arranging multiple windows

Note: AMT allows you to open an unlimited number of separate windows. The system remembers the window arrangement for each user: the next time you log in, the open windows and their arrangement will be the same as when you logged out. The active window is indicated by the blue bar at the top (your bar color may be different, depending on your Windows configuration). To select a new active window, which is also displayed on top, click the desired window’s title bar or press Ctrl + Tab until the desired window is on top. Clicking on a preconfigured window button will open a new window, instead of moving an existing window to the top. Take care that you do not have too many windows open, as this will adversely affect system performance.

You can perform standard window functions. You can click the Minimize button (located on the top right corner of each window) to minimize any window. You can resize the window or drag it to a new location. For example, suppose you do not want to display Messages or Transactions, you can minimize those windows and, perhaps, enlarge the Critical Alarms window. The resulting AMT appearance might be as shown in Figure 6-3.

To quickly view all of the open windows at once, you may specify whether the windows are displayed tiled or cascaded.



Figure 6-3. Customized AMT Window Display



Cascading Windows

Cascading windows arranges the open windows in an overlapping pattern, without changing the size or shape of the windows. Because of this, some windows may extend beyond the boundaries of the AMT window. Figure 6-4 shows cascading windows. When you select this option, the active window is always placed on top.

To specify this style, select Windows Cascade from the AMT menu.

Figure 6-4. AMT - Cascaded Windows



Tiled Windows

The tiled display shrinks each window so that all open windows fit into the AMT window. The size of the windows will depend on the number of windows you have open, and the size of the AMT window display. The tiled display is shown in Figure 6-5.

To specify the tiled display, select Windows Tile. The active window is indicated by the blue (the actual color may vary depending upon your color settings) title bar. In Figure 6-5, the active window is Messages.

Printing MessagesTo print messages, select Actions Print, or click the Print tool from the menu. Click OK in the Print Dialog box to send the list to the printer.

Figure 6-5. AMT - Tiled Windows



The default is to print the entire contents of the window. You may use the options in the print dialog window to specify a range of pages.

To determine which page(s) you wish to print, move the mouse cursor to the Date/Time field in the active window. Do not click in the field, but just place the mouse cursor over it. After a slight delay, a popup window will indicate which page that transaction is on.

Note: The page number feature does not work on alarms that contain a dispatch message: the popup window shows the dispatch text instead. To see which page an alarm is on, check the page number for the event above or below it.

The actual number of pages printed depends on the number and size of columns displayed in the window. Enough sheets will print for each “page” to show all columns. For example, if you have an active event window that includes all of the possible columns, printing requires three sheets per page in landscape mode (default). For each page you select to print, three actual pages will be printed.

Changing the Window DisplayThere are several ways in which you can change the window display in TAC I/NET Seven.

✦ The display can be temporarily paused, and resumed at will. Refer to “Pausing the Message Update” on page 6-18.

✦ The Window Options editor allows you determine which data fields are included in each window, and arrange the fields in the desired order. Refer to “Window Options” on page 6-18.

✦ Advanced filtering allows you to fine-tune window displays to only the messages of interest. Filters are saved on the system, and are available to all users with filter privileges. Refer to “Filters” on page 6-21.

These options are common to all AMT windows. In addition, there are some specialized commands that are specific to the window type. Refer to the section on the appropriate window type for a discussion of the special commands.



See Also: “Alarm Windows” on page 6-30

“Event Windows” on page 6-37

Pausing the Message Update

One menu option that is common to all AMT windows is the Pause function. If messages or alarms are coming in too fast, you can pause the update to the window display. Click in the window you wish to pause and select Actions Pause, or click the Pause tool. If a window is paused, it is noted in the window’s titlebar.

When you are ready to receive new messages, select Actions Resume or click the Resume tool. Any messages that arrived while the window was paused immediately appear, and new messages appear as they arrive.

Column Width

The information displayed in each window is divided into columns. You may adjust the width of the columns by dragging the column dividers to the left or right. If you wish to return the columns to their default width, select Actions Reset Column, or click the Reset Column tool.

Window Options

The Window Options editor allows you to customize each window in AMT. This editor appears automatically when you open a new window (except for predefined windows). You may also open the editor to change the parameters of an active window.

This editor allows you to configure each window as follows:

✦ Choose which columns are displayed in the window.

✦ Select the order in which columns are arranged.

✦ Select how messages are sorted (alarm windows only).

✦ Select the filter for the messages. (Refer to “Filters” on page 6-21 for a complete discussion of filtering.)



Use the following procedures to set the window options:

1. Do one of the following to open the Window Options editor (see Figure 6-6):

✧ Open a new alarm window by selecting System New Alarm Window, or click on the appropriate toolbar button.

✧ Open a new event window by selecting System New Event Window, or click on the appropriate toolbar button.

✧ With the desired window set as the active window, select Edit Window Options, or click on the appropriate toolbar button.

✧ Right-click in the desired window and select Window Options from the context menu that appears.

2. Choose which columns to display or hide as follows:

Figure 6-6. Window Options Editor



a. To display a column, highlight the column name in the De-selected list and select Add. This moves the column name into the Selected list.

b. To hide a column, highlight the column name in the Selected list and select Remove. This moves the column name into the De-selected list.

c. Alternatively, you can quickly hide or display all columns by selecting Remove All or Add All.

3. Arrange columns by selecting the name in the Selected list and using the Up and Down options to adjust their position. AMT window columns are displayed in the same order as listed, with the top column being the first column in the window.

4. (Alarm window only) If desired, select how the messages will be sorted, as follows:

a. Select a parameter from the Sort By drop-down. Only parameters in the Selected list are available.

b. Select the sort order, either Ascending or Descending.

If you do not select a sort order, messages are sorted by date/time in descending order (newest message on top).

5. If desired, select a filter for the messages. Refer to “Filters” on page 6-21 for information on creating filters.

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.

6. If you wish to enter a customized window name, perform the following:

a. Disable () the Use default window name check box.

b. Enter the desired Window name, up to 30 characters. The selected name will be added to the filter name and sort column (if applicable) in the window’s title bar.



7. Click OK to close the Window Options editor and view the window with the selected options, or Cancel to close the window without saving the changes.

Note: If you were opening a new window and select Cancel, the window will not be created.

Filters

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.

You may use message filters to select criteria for the types of messages that display in a window. If you do not apply a filter, all messages display.

When a filter is applied to a window, the filter name is shown in the window’s title bar. For example, in Figure 6-7, the Messages window is using the filter named “Host Restore.”

Figure 6-7. Example Filtered Window



Your ability to create and edit filters is controlled by the options set for your password in the Host Passwords editor. Refer to “Host Passwords” in Chapter 9, Passwords.

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 new filter will change the window to use only the selected filter.

Creating a Filter Definition

TAC I/NET Seven includes predefined filters, corresponding to the predefined window selections. Depending on the privileges associ-ated with your password, you may define new filter criteria.

To create a filter definition:

1. Select Edit Filters, or click the Filter tool. The system displays the Filters summary screen (see Figure 6-8) with a listing of defined filters.

Note: If there are no open windows, all defined filters are listed. Filters created in this manner are available for all window types.

2. Click the Add button. The system displays the Filter Name dialog (see Figure 6-9).

Figure 6-8. Filter Summary Dialog



3. Enter the name for the new filter and click OK. The system displays the Filter editor for the appropriate window type, either Event Filter or Alarm Filter.

Both Filter editors include the General Filter Options and Filter Date Range sections. The Event Info section and Trans-action Filtering option are available on the Event Filter editor only. Figure 6-10 shows the Event Filter editor.

Figure 6-9. Filter Name Dialog

Figure 6-10. Event Filter Editor



4. Complete the General Filter Options section. The settings and ranges determine which messages will be displayed in the window view; any parameter outside the selected range(s) will not be included.

a. Set the Point address range Start and End parameters to limit the resulting message list to specific addresses. Messages originating from addresses outside of this range will be excluded.

b. Enter the desired Device name. The default is [All] for all devices. You may enter up to 16 characters, including the following wildcard characters:

% The % character is like the * character in windows find-files. Searching for a device name of “%device%” would return any device name containing the string “device”.

_ The underscore character allows any single char-acter. For example, searching for a device name of “device_” would return “device1”, “device2”, “devices” etc.

[ ] The left and right closed brackets allow a single char-acter to be within a specified range (for example: [a-c]) or within a set of characters (for example, [abcd]). Searching for a device name of “device[a-f]” would return “devicea” through to “devicef” but not “deviceg”.

[^] This is the negation of the previous wildcard. It spec-ifies that a single character should not be within a set of characters (for example, [^a-c] or [^abcd]).

c. Priority – The alarm level for events defined as alarms: Routine, Priority, or Critical.

d. Select the Priority for the system message. Only messages with the selected priority (set in the DCU editor) will be included in the window view.

e. Select the starting and ending Site numbers.



f. Use the Camera All or Select button if you wish to include CCTV camera messages in the resulting AMT window.

The Select button in only available when the All option is not enabled. If you click the Select button, an editor will open allowing you to select and de-select specific cameras (see Figure 6-11). Unselected cameras will be excluded from the resulting AMT window unless you enable the filter's Camera All option.

After making your selections, click OK to close the editor.

Note: If you enable () the Camera All option, messages associated with any camera will be included in the resulting AMT window, regardless of any camera selections you make using the Select button.

5. If you wish to filter the messages by the date and/or time they were generated, complete the Filter Date Range section.

a. Activate () the Enable Date Filtering check box. This field must be activated in order to set the parameters in this section.

b. If desired, activate () the Enable Time Range Filtering check box.

c. Enter the desired Start and End dates. You will see all messages that occurred between these two dates.

Figure 6-11. Selecting Cameras



d. If you activated the time range filtering check box, enter the desired Start and End times to limit the resulting message list to specific times. Messages occurring before the start time or after the end time will be excluded.

6. (Alarm Filter editor only) The following steps do not apply to alarm filters. Proceed to Step 9.

7. (Event Filter editor only) In the Event Info section, activate ([X]) all message types (events) you wish to include in the message filter and deactivate ([ ]) any that you do not wish to include. You can use the Messages Only, Trans Only, All Yes and All No buttons to speed the selection process.

Note: Refer to the System Messages chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for a description of each message type.

8. (Event Filter editor only) If you wish to filter transactions by individual parameters, click the Tran Filtering button to open the Transaction Filter editor (see Figure 6-12). This button is enabled only if at least one transaction is selected in the Event Info section.

Figure 6-12. Transaction Filter Editor



a. If desired, enter the filter parameters for Last Name, First Name, and Group Name. These are alphanumeric fields that allow you to determine search criteria for data within each field. You may enter up to 50 characters, including the following wildcard characters:

% The % character is like the * character in windows find-files. Searching for a name of “%john%” would return any name containing the string “john” (e.g, “johnson”).

_ The underscore character allows any single char-acter. For example, searching for a name of “mar_” would return “mark”, “mars”, “mary” etc.

[ ] The left and right closed brackets allow a single char-acter to be within a specified range (for example: [a-c]) or within a set of characters (for example, [abcd]). Searching for a name of “name[a-f]” would return “namea” through to “namef” but not “nameg”.

[^] This is the negation of the previous wildcard. It spec-ifies that a single character should not be within a set of characters (for example, [^a-c] or [^abcd]).

b. If desired. enter a starting and ending range for Tenant number associated with the individual.

c. If desired, enter a start and end range for the Key/Card number assigned to the individual.

Note: Tenant 0 and Key/Card 0 are used for specific transactions, such as Bad Card Read. Excluding them from the filter range will eliminate these transactions.

d. If desired, enter a start and end range for the anti-pass-back Zone associated with the door.



e. Select the individual record type(s) you wish to view in the window by activating () one or more of the options:

✢ Permanent

✢ Temporary

✢ Disabled

f. Select OK to confirm the transaction filter parameters and return to the Event Filter editor, or Cancel to return to the filter editor without saving the transaction filter changes.

9. When you finish defining the filter, select OK. The system returns you to the Filter summary dialog (see Figure 6-8 on page 6-22).

Modifying a Filter

Existing filters can be modified. When you modify a filter, all open windows using that filter will update to reflect the new filter param-eters.

Note: You cannot modify the predefined filters: Messages, Transactions, Routine Alarms, Priority Alarms, and Critical alarms.

To modify a filter:

1. Select Edit Filters, or click the Filter tool. The system displays the Filters summary screen (see Figure 6-8 on page 6-22) with a listing of defined filters.

2. Select the filter you wish to modify and click the Modify button. The system displays the Filter editor for the appro-priate window type.

3. Change the desired parameters. Refer to the instructions in “Creating a Filter Definition” on page 6-22.

4. When finished, select OK to save the changes and return to the Filters summary dialog, or Cancel to exit without saving the changes.

Filter changes take effect immediately. All open windows using the filter will be updated to use the new parameters.



Copying a Filter

Copying a filter allows you to use the parameters already defined for one filter as the starting point for defining another filter.

For example, if you wish to refine a filter but don’t wish to affect open windows already using that filter, you can copy the filter and then enter just the changes.

To copy a filter:

1. Select Edit Filters, or click the Filter tool. The system displays the Filters summary screen (see Figure 6-8) with a listing of defined filters.

2. Select the filter you wish to use as the basis for the new filter and click the Copy button. The system displays the Filter Name dialog (see Figure 6-9 on page 6-23).

3. Enter the name for the new filter and click OK. The system displays the Filter editor for the appropriate window type. The settings for all parameters are the current settings for the filter you selected in Step 2.

4. Change the desired parameters. Refer to the instructions in “Creating a Filter Definition” on page 6-22.

5. When finished, select OK to save the changes and return to the Filters summary dialog, or Cancel to exit without saving the changes.

If you select Cancel, the new filter is not saved and will not appear on the Filters summary dialog

Deleting a Filter

You can delete a filter that you no longer wish to use, such as a special filter created to monitor a specific circumstance. When you delete a filter, it is no longer available for selection. Any open windows using the filter will change to an unfiltered event or alarm window, depending on the window type.

Note: You cannot delete the predefined filters: Messages, Transactions, Routine Alarms, Priority Alarms, and Critical alarms.

To delete a filter:


Alarm Windows System Messages


2. Select the filter you wish to delete and click the Delete button. A confirmation screen will appear.

3. Select Yes to delete the filter, or No to cancel the request. You will return to the Filters summary dialog.

Applying a Filter

There are two ways to apply a filter to a window:

✦ Select the desired filter from the drop-down box in the Window Options editor. Refer to “Window Options” on page 6-18.

✦ Select a filter from the Filters summary dialog.

To apply a filter from the Filters summary dialog, follow the proce-dure below:


2. Select the desired filter definition from the list and click the Select button to apply the filter to the active window. The filter is applied immediately.

Note: If the active window is an alarm window, any Event Info or Transac-tion filtering will be ignored.

3. Click the Close button to close the Filters summary dialog and return to the AMT window display.

Alarm Windows

A sample Alarm Window is shown in Figure 6-13.

The header for each window contains the following information:

✦ Filter name for this window


System Messages Alarm Windows

✦ Number of alarms for this filter

✦ Number of unacknowledged alarms for this filter

The AMT window header shows the total number of alarms, and the total number of unacknowledged alarms. If AMT is minimized, you can move your cursor over the AMT task bar item to check the number of alarms without maximizing AMT.

The alarm windows may contain the following columns, in the order designated in the Window Options editor (see “Window Options” on page 6-18):

✦ Date/Time — date (mm/dd/yy) and time (hh:ss) of the message.

✦ Count — number of times an entry has cycled in and out of alarm.

✦ Address — system address of the point or the station of the host, or controller, that generated the alarm.

✦ Link Name — 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 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 during network configuration.

✦ Station Name — 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 “Device Name” field (see below). The value of this field is determined by the name given to the station during network configuration.

Figure 6-13. Sample Alarm Window



✦ Device Name — name of the device that generated 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.

✧ If the device generating the alarm is a door, this field will contain the door name. If the door name is not available, the point name is displayed.

✧ If the device generating the alarm is a door, this field will contain the door name. If the door name is not available, the point name is displayed.

✦ Site — The Host LAN or Dial site.

✦ Event Type — the event that triggered the alarm.

✦ First Name — the first name of the individual associated with an alarm. This field is blank when the alarm is not associated with an individual (for example, a Door Forced alarm cannot be tied to an individual and will therefore have no First Name value).

✦ Last Name — the last name of the individual associated with an alarm. This field is blank when the alarm is not associated with an individual (for example, a Door Forced alarm cannot be tied to an individual and will therefore have no Last Name value).

✦ Tenant — the name of the tenant associated with an access control alarm. This field is blank when the alarm is not associ-ated with access control.

✦ Individual — the number assigned to the individual associ-ated with an alarm. This field is blank when the alarm is not associated with an individual (for example, a Door Forced alarm cannot be tied to an individual and will therefore have no Individual value).

✦ Value — the value of the point that generated the alarm. This field is left blank for alarms that are not associated with a point.

✦ Priority — the alarm level for this event: Routine, Priority, or Critical.

✦ Ack Status — indicates if the alarm has been acknowledged.



✦ Action Message—displays the action message if an event action message was attached to this point.

✦ Dispatch Message—displays the dispatch message if a dispatch message was attached to the alarm.

✦ Camera — displays the number assigned to the CCTV camera that generated the alarm. This field is blank when the alarm is not associated with a CCTV camera. Refer to TCON301, TAC I/NET Seven Database Connectivity and Reporting, for more information about integrating CCTV with TAC I/NET Seven.

✦ Unique Field — displays the value of a user-defined field for the individual associated with the alarm. Use the Access Control Options editor to designate one of the 16 user-defined fields as a unique user field. Refer to the description of the Unique user field parameter on page 17-92 for more information.

Depending upon your window size, you may have to scroll to the right to view the entire row. You can also adjust the width of each column by dragging the column dividers to the left or right.

The alarm windows display all points that are in alarm or have been in alarm, but have not been acknowledged. The appearance of the alarm text is dependent upon its current status. The following table shows the default color scheme. You may change these colors in the AMT Configuration editor (see “Alarm Colors and Archive Colors” on page 6-6).

If you have minimized an alarm window and a point goes into alarm, the title bar of the minimized window will flash to indicate that it has received an alarm. To view the alarm message, open the window by double-clicking the title bar or clicking the Windows Maximize button.

Red - flashing The point is in alarm and has not been acknowledged.

Red - steady The point is in alarm and has been acknowledged.

GreenThe point was in alarm and returned to normal without being acknowledged.

Blue The point is normal.



Note: If you have minimized AMT, the task bar button flashes to indicate an alarm. You can also enable the Alarm Topmost function or the audible indicator. Refer to “AMT Configuration” on page 6-4.

Acknowledging an AlarmTo acknowledge an alarm, select Actions Acknowledge or click the Acknowledge tool on the toolbar (shown in the left margin). Alternatively, you can right-click on the alarm message and select Acknowledge from the resulting context menu. The point will change from red to blue (if the default colors have not been changed). If the point has already returned to normal, acknowl-edging the alarm also purges the alarm message. When an acknowl-edgment is performed on a point, the system generates an acknowledge message.

Purging AlarmsYou can delete alarms after they have been acknowledged. To purge an individual alarm, select the alarm message, and click the Purge tool or select Actions Purge.

Purging an alarm only removes it from the alarm windows. A copy of the alarm is retained in the online events file. The alarm will continue to appear in event windows, and will be archived when appropriate.

Silence AlarmThe Silence Alarm functions allows you to halt the audible indi-cator of an alarm without acknowledging the alarm. Select Actions Silence Alarm or click the Silence Alarm tool.

DispatchThe Dispatch option allows you to attach a message to an alarm and acknowledge the alarm at the same time. The dispatch message is sent to the message queue, and the dispatch text is placed in the Dispatch message column. To attach a dispatch message



1. Highlight the alarm and click the Dispatch tool, or select Actions Dispatch. Alternatively, you can right-click on the alarm message and select Dispatch from the resulting context menu. The Dispatch Message Editor displays, as shown in Figure 6-14.

2. Enter the dispatch text in the edit field using either of the following methods:

✧ Type a text string of up to 64 characters.

— OR —

✧ Select the ... button to select text from a list of pre-defined dispatch strings. Refer to “Dispatch Strings Library” on page 6-35 for more information about storing dispatch strings.

3. Click OK to accept the dispatch string. The dispatch text displays in the Dispatch Message column of the appropriate alarm window and is also sent to the messages window. Dispatch messages in the messages window are indicated by an icon at the beginning of the message row.

Dispatch Strings LibraryTAC I/NET Seven displays the Dispatch Strings Library editor (see Figure 6-15) when you select Edit Dispatch Strings from the AMT main menu. Use this editor to build a database of stored dispatch strings. The strings you store here become available from the Dispatch Message Editor (see Figure 6-14).

Figure 6-14. Dispatch Message Editor



The following options are available within the Dispatch Strings Library editor:

✦ Add — Use this option to add a new dispatch string. The system displays the Dispatch Strings Editor (see Figure 6-16). Use this window to enter a new dispatch string.

Figure 6-15. Dispatch Strings Library

Figure 6-16. Dispatch String Editor


System Messages Event Windows

✦ Delete — Use this option to remove a previously-defined dispatch string from the library. When you highlight a dispatch string and select this option, the system immediately deletes the stored string (i.e., there is no confirmation message).

✦ Modify — Use this option to modify a previously-defined dispatch string. When you highlight a dispatch string and select Modify, the system displays the Dispatch Strings Editor. You can then modify the string as necessary. Select OK to replace the selected string with the new dispatch string.

✦ Copy — Use this option to create a new dispatch string by copying from a previously defined dispatch string. When you highlight a dispatch string and select Copy, the system displays the Dispatch Strings Editor. You can then modify the string as necessary. Select OK to add the new dispatch string to the library.

Home PageIf a point has been assigned to a system page, selecting the Home page option displays the page. For instructions on designating a home page refer to “Points” in Chapter 8, System Pages. To view the home page, highlight an alarm message and select Actions Home Page or click the Home page tool.

Event Windows

Event windows contain a summary record of all system traffic, including messages (system events), transactions (access control events) and alarms. Figure 6-17 illustrates a sample event window.

Event windows may contain the following columns, in the order designated in the Window Options editor (see “Window Options” on page 6-18):

✦ Date—date (mm/dd/yy) of the message.

✦ Time—time (hh:ss) of the message.

✦ Address—system address of the point or the station of the host, or controller, that generated the alarm.


Event Windows System Messages

✦ Site—The Host LAN or Dial site.

✦ Link Name—name of the link containing the device that generated the message. If the message is generated by a host or link, this field 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 during network configuration.

✦ Station Name —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 the “Device Name” field (see below). The value of this field is determined by the name given to the station during network configuration.

✦ Device Name—name of the device that generated the alarm.

✦ Event Type—the event responsible for the message. An expla-nation of the potential event types is located in the System Messages chapter of TCON300, TAC I/NET Seven Technical Reference Guide.

✦ Value—the value of the point.

✦ Message—The event or dispatch message text.

✦ Last name—individual’s last name.

✦ First name—individual’s first name.

✦ Individual—Individual’s key/card number.

✦ Tenant — tenant name.

✦ Group name — group name.

✦ Zone — access control zone.

Figure 6-17. Event Window



✦ Camera — displays the number assigned to the CCTV camera that generated the alarm. This field is blank when the alarm is not associated with a CCTV camera. Refer to TCON301, TAC I/NET Seven Database Connectivity and Reporting, for more information about integrating CCTV with TAC I/NET Seven.

Messages are listed in chronological order with the most recent being displayed first.

Text LibraryThis feature allows you to specify a text message to send across a serial (COM) port when a point goes into alarm. This can be used to send commands to third-party hardware that can accept ASCII text instructions, such as CCTV and paging or intercom systems.

The serial port and transmission rate are set in the I/NET Config-uration active profile. Refer to the section on I/NET Configuration in TCON157, TAC I/NET Forms and Worksheets Getting Started.

Creating a Text Entry

To create a text library entry:

1. Select Edit Text Library from the AMT main menu. The system displays the Text Library screen, as shown in Figure 6-18.

2. Select Add. The Text Editor appears, as shown in Figure 6-19.

3. Enter the Point Address, in LLSSPPBB PT format. This must be unique; only one text command is allowed per point address.

4. Enter the desired Text, up to 127 characters. You may use the following characters:

✧ Letters (a–z, A–Z)

✧ Numbers (0–9)

✧ ASCII special character codes, in the format \nnn, where nnn is the ASCII decimal notation for the desired char-acter. This is considered a single text character.



Figure 6-18. Text Library Screen

Figure 6-19. Text Editor



✧ Limited escape sequences, as follows:

✢ \a (alert bell)

✢ \b (backspace)

✢ \f (form feed)

✢ \n (new line)

✢ \r (carriage return)

✢ \t (horizontal tab)

✢ \v (vertical tab)

✢ \’ (single quote)

✢ \” (double quote)

✢ \\ (backslash)

✢ \? (literal question mark)

Each escape sequence counts as a single text character.

5. Select OK to save the text string, or Cancel to return to the Text Library without saving the changes.

Modifying a Text Entry

To modify an existing text entry:

1. Select Edit Text Library from the AMT main menu. The system displays the Text Library screen, as shown in Figure 6-18 on page 6-40.

2. Select the entry you wish to change and select Modify. The Text Editor appears, as shown in Figure 6-19 on page 6-40.

3. Edit the text entry. The point address cannot be changed.

4. Select OK to save the changes, or Cancel to return to the Text Library screen without saving the changes.

Copying a Text Entry

To copy an existing text entry to a new entry:




2. Select the entry you wish to use and select Copy. The Text Editor appears, as shown in Figure 6-19 on page 6-40. The fields will already contain the previous entry’s point address and text entry.

3. Edit the point address. Duplicate addresses are not allowed; you must change the point address to save the new entry.

4. If desired, edit the text entry.

5. Select OK to save the changes, or Cancel to return to the Text Library screen without saving the changes.

Deleting a Text Entry

To delete an entry from the text library:


2. Click to select the entry you wish to delete.

3. Select Delete. You will be asked to confirm the deletion. Select Yes to delete the entry, or No to cancel the request.

Image VerificationThis feature allows you to display an individual’s saved image for a transaction (access control event). In order to use this feature, you must have included individual images (pictures) in the Individual Parameters editor. There are two options to this feature:

✦ Automatic: the system can be set to create an image verifica-tion window for an AMT event window. This window will automatically display the image associated with the individual from the most recent transaction, updating at the screen refresh rate (every two seconds). At every refresh, the window shows the image associated with the most recent transaction event.

Note: If more than one transaction occurs during the refresh interval, the earlier events will not have an image displayed in the automatic image verification window.



✦ On demand: the operator can open a static image window, to view the image associated with a particular transaction in an event window, or a transaction alarm in an alarm window.

The image verification window is set to “always on top.” The window can be resized and moved on the AMT screen.

Activating Image Verification

The procedures to set up image verification are as follows:

1. Add user images to the individual record in the Individual Parameters editor. Refer to “Adding an Individual” in Chapter 17, Access Control.

2. Select the desired fields for image verification windows:

a. Select Edit Image Verification from the AMT main menu. The system displays the Image Verification Configuration editor (see Figure 6-20).

Figure 6-20. Image Verification Configuration Editor



b. Select up to seven user fields to display in the image veri-fication window by clicking the selected field and selecting <- Add, or by double-clicking the field name. Use the Remove -> key to de-select a field.

c. Use the Move Up and Move Down buttons to arrange the fields in the Selected list into the desired order. Fields will be displayed in the image verification window in the same order as they are shown in this editor.

d. Select OK to accept the field selections, or Cancel to close the window without saving the changes.

Note: Changing the image verification configuration will cause any auto-matic image verification windows to update, but will not affect any open static image verification windows.

3. (Automatic image verification only) Select the doors for the image verification window:

a. Select Actions Door Selection from the AMT menu. The system displays the Image Verification Door Filter (see Figure 6-21).

b. Select ([X]) the doors you wish to include in the auto-matic image verification window. You may use the Select All and Select None buttons to speed your selection process.

Note: You must select at least one door to use automatic image verification. Only transactions from the selected door(s) will generate an auto-matic image. If you activate automatic image verification the window will appear, whether any doors are selected or not.

c. When finished, select OK to accept the door filter selec-tions, or Cancel to close the editor without saving the changes.

Note: Changing the door selection will cause any automatic image verifica-tion windows to update, but will not affect any static image verifica-tion windows.



4. (Automatic image verification only) Complete the following to activate automatic image verification:

a. Open an event window, or select an existing event window. The event window must be the active window.

b. Select Actions Image Verification from the AMT main menu, or select the toolbar icon. The automatic image verification window will appear (see Figure 6-22).

5. (On-demand image verification only) Right-click on the desired transaction or transaction alarm and select Image from the pop-up context menu. The static image verification window will appear (see Figure 6-23).

The static window will have the properties set in Step 2. If you change the selected fields in the Image Verification Configura-tion editor, the changes will affect any open automatic image verification windows, but will not affect any open static image verification windows.

Figure 6-21. Image Verification Door Filter Editor



De-activating Automatic Image Verification

If the automatic image verification window is open, you can close it by clicking the X in the upper right-hand corner. However, this action does not de-activate the automatic image verification func-tion. Therefore, the occurrence of an applicable event will cause the image verification window to re-open.

In order to de-activate automatic image verification, ensure that the image verification window is open and select Action Image Verifi-cation from the AMT main menu or select the toolbar icon. This will cause the automatic image verification function to toggle off and the image verification window will close.

Note: If you attempt to de-activate automatic image verification while the image verification window is closed, the window will open and the automatic image verification function will remain enabled. In this

Figure 6-22. Automatic Image Verification Window

Figure 6-23. Static Image Verification Window


System Messages Archives

case, you must again select Action Image Verification from the AMT main menu or select the toolbar icon to de-activate the function and close the image verification window.

Archives

Note: Archiving and filtering both use a great deal of system resources. While archiving, particularly when there are a large number of online AMT records, it may appear as though your AMT filters are not operating properly. Filter operation will return to normal when the archive function is complete.

The archive function allows you to save AMT events or on-line trend data to a separate database. This allows you to store the archived data indefinitely. Refer to the section on Archives in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

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.

Event Archive ConfigurationI/O Server must be running to enter or edit the archive configura-tion.

The Event Archive Configuration editor is displayed by default when you right-click the I/O Server icon in the Windows System Tray and select Archive Configuration from the resulting pop-up menu.

If you wish to configure SevenTrends archiving, select the Trend Archive Configuration option to display the SevenTrends Archive Configuration editor. In this case, refer to “Archiving SevenTrends Data” on page 24-9 for more information.


Archives System Messages

Using the Event Archive Configuration editor, you can configure TAC I/NET Seven to save on-line event data to an archive file. Archives can occur automatically based on triggers, or you can manually initiate an archive. Archived data may be used in reports, but cannot be viewed online through TAC I/NET Seven.

The archive database is stored in the location specified as the Archive Directory in the I/NET Configuration Editor. 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 = two-digit month (01–12; 01 = January, 12 = December)

✦ DD = day of month (01–31)

Figure 6-24. Event Archive Configuration



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

Performing Event Archiving1. You must activate () the Enable event archiving option in

order for any type of event archiving (i.e., manual or trig-gered) to occur. If you do not activate this option, only the Maximum Online Events parameter will be active.

2. Activate () the Verify archive contents option to have TAC I/NET Seven verify the integrity of the archived data after it has been written.

3. Use the Archive device field to specify a directory to accept the archive database file when the archive completes.

4. Set the following Online Event Storage parameters:

✧ Minimum Online Events – This setting specifies the minimum number of event records not to archive. There must be at least this many unarchived event records before an archive (automatic or manual) can occur.

✧ Archive Threshold – This setting specifies the number of unarchived event records at which the system will start requesting to archive with the option for the operator to defer.

✧ Override Threshold – This setting specifies the number of unarchived event records at which the system will start an archive without giving the operator the option to defer.



✧ Maximum Online Events – This setting specifies the total number of unarchived events that can be online before the oldest record will get overwritten with a new incoming record.

5. Set the following Distribution Parameters to specify how messages generated by archive activity will be distributed.

✧ Distribution Group – This will determine which set of 8 masks will be used for comparison at the Tap or host level.

✧ Distribution Mask – Set each of eight masking positions to the desired state, either activated () or deactivated ().

✧ Message Priority – This setting controls when messages will be sent.

6. Set the following Trigger parameters:

✧ Threshold Trigger – This setting specifies what to do when the Archive Threshold count is reached. The following options are available:

✢ Disabled – Disable archive threshold trigger.

✢ Confirm – Ask operator to confirm (allow) archive.

✢ Automatic – Start archive without confirmation.

Note: The Scheduled Trigger (described below) honors the Minimum Online Events parameter; therefore, if the scheduled trigger occurs before the number of unarchived records has reached the Minimum Online Events setting, no archive will occur.

✧ Scheduled Trigger – This setting specifies what to do when the schedule time is reached. The following options are available:

✢ Disabled – Disable the schedule trigger.

✢ Confirm – Ask the operator to confirm (allow) the archive.

✢ Automatic – Start archive without confirmation.



Note: The next three items are available only if the Scheduled Trigger setting is not “Disabled.”

✧ Time of day – This setting specifies the time of day to begin a scheduled archive.

✧ Elapse time – Select this option to schedule archives based on an elapsed time since the last archive. Use the fields that accompany this option to specify an elapse time.

✧ Day of week – Select this option to schedule archives for a specific day of the week. Use the drop-down list to choose a day.

Note: Due to system activity, the archive may not occur at the exact time specified.

7. Click one of the following buttons to archive events:

✧ OK – Click this button to save the settings and exit the editor. If you have activated () the Enable event archiving option, TAC I/NET Seven will use the settings in this editor to automatically initiate event archives.

✧ Archive Now – This button is only available when the Enable event archiving option is selected. Click this button to manually initiate an event archive. If you click this button before the number of unarchived records has reached the Minimum Online Events setting, you will receive an error message informing you that no archive can occur.

Triggered ArchivesA triggered archive is one that is initiated by the system based on entries in the archive configuration. The system initiates archives either by the passage of time (Scheduled Trigger) or by reaching a particular number of online events (Threshold Trigger).



Automatic

When the archive trigger is set to Automatic, the archive activity is not visible to the user. The only way you will be able to tell events are archived is that their appearance in the AMT windows will change to the colors set for archived events (see “Alarm Colors and Archive Colors” on page 6-6).

Confirmed

If an archive trigger is set to Confirm, then the system will display the Confirm Archive editor (see Figure 6-25) when the trigger point is reached.

Approving the Archive1. If desired, use the spin dial to change the Thousands of

records to archive. The default number is based on the Archive Configuration entries. You may decrease this number to archive fewer records, but you may not increase the number of records to archive.

2. Activate () or deactivate () the archive verification by clicking on the Verify archive contents check box. The default is the setting from the archive configuration.

3. Press the Start button to begin the archive.

Figure 6-25. Confirm Archive



Postponing the Archive

To postpone the archive, click Cancel on the Confirm Archive editor.

Until the records are archived, the Confirm Archive editor will reappear every 24 hours, or when another trigger point is reached. In addition, a reminder screen will appear whenever a new oper-ator logs on (see Figure 6-26).

Manual ArchivesYou can create an archive any time the current number of online events exceeds the Minimum Online Events setting in the Archive Configuration editor by at least 1,000 (records are archived in blocks of 1,000).

Note: Manual archives can result in small archive files, making it difficult to run reports on archived events. Refer to the section on Archives in TCON300, TAC I/NET Seven Technical Reference Guide.

I/O Server must be running to create an archive.

1. Right-click on the I/O Server icon and select Archive Config from the context menu. The system displays the Event Archive Configuration editor as shown in Figure 6-24 on page 6-48.

2. Click the Archive Now button. The system displays the Confirm Archive editor (see Figure 6-25 on page 6-52).

Figure 6-26. Archive Reminder Screen



3. If desired, use the spin dial to change the Thousands of records to archive. The default number is the maximum records available for archiving. You may decrease this number to archive fewer records, but you may not increase the number of records to archive.

4. Activate () or deactivate () the archive verification by clicking on the Verify archive contents check box. The default is the setting from the archive configuration.

5. Click Archive Now to begin the archive, or Cancel to return to the Event Archive Configuration editor without archiving.

6. Click OK to close the Archive Configuration editor.

Opening an Event ArchiveEvent archive files may be opened in an AMT event window for viewing. Only one archive may be opened in each window. To open an archive file in an AMT window:

1. Select System Open Archive from the AMT menu. The Archives Summary appears (see Figure 6-27).

Figure 6-27. Archive Summary


System Messages CCTV in AMT

Use Archive Summary to open archived TAC I/NET Seven AMT data or TAC I/NET 2000 AMT data that you have imported into the TAC I/NET Seven system.

2. Highlight the desired archive and select OK. The Window Options editor opens (see Figure 6-6 on page 6-19).

Use this editor to customize the AMT window that will show the archive that you are currently opening. Refer to “Window Options” on page 6-18 for more information.

The archive window will show the name of the archive file in the title bar, along with the window and filter names (if applicable). All of the entries in this window will display the colors specified for archived records in the AMT Options editor (see “Alarm Colors and Archive Colors” on page 6-6).

Since the records in the archive file will not change, this window is not updated by the system. Therefore there is no need to pause this window display, although the Pause function is not disabled (refer to “Pausing the Message Update” on page 6-18).

CCTV in AMT

CCTV features are available only after you have integrated a Pelco CCTV system with TAC I/NET Seven. For instructions on how to integrate digital CCTV with TAC I/NET Seven, refer to TCON301, TAC I/NET Seven Database Connectivity and Reporting.

Using AMT’s CCTV features, you can review recorded video and view live video from AMT. You can also perform searches for specific video clips.

CCTV Message TimestampsWhen TAC I/NET Seven receives a timestamped message from the CCTV system, it records the message with the date and time of the CCTV server's date and time adjusted for the TAC I/NET Seven PC's regional settings. “DVR Srv Offline” and “DVR Srv Online” messages are not timestamped by the CCTV system and are always recorded with the host PC's time and date.


CCTV in AMT System Messages

Opening the AMT Video WindowThe AMT Video window is AMT’s main interface to live and captured CCTV system video. You can access the AMT Video window as follows:

1. Right-click on any event that has a video clip (i.e., any event that contains a icon) and select Video from the resulting pop-up menu.

Alternatively, you can click on any event that has a video clip and then click the show video icon in the AMT toolbar.

The AMT Video window opens (see Figure 6-29).

2. Use the AMT Video window to view the captured video. The video clip plays automatically when you first open the AMT Video window.

The AMT Video window has two video display areas. The left display area shows captured video. The right display area shows live video.

Viewing the Selected Event’s Captured VideoWithin the AMT Video Window, you can replay an event’s captured video by pressing the Play ( ) button. You can also use the other buttons to manually move forward and backward within the video clip.

Viewing Live VideoUse the drop-down list next to the slider to select the source camera for the live video display. The selected camera will also be used as criteria for the search function described below.

Figure 6-28. Right-clicking an Event


System Messages CCTV in AMT

Searching Captured VideoSearch for video by performing the following steps:

1. Use the following fields to specify date and time criteria:

✧ Begin (date and time) – Use these fields to specify the start of the time span you wish to search.

✧ End (date and time) – Use these fields to specify the end of the time span you wish to search.

2. Use the Camera drop-down list to select the source camera for the search function.

3. When you are satisfied with the criteria settings, press the video control button to start the search function.

4. When the search function is complete, the Playback portion of the editor will begin playing the resulting video.

Figure 6-29. AMT Video


CCTV in AMT System Messages


C H A P T E R18

7

© 2001–2010 SchTCON299–05/10

Summaries

Summaries give you a quick glance at the devices communicating at a particular level in your system. Summaries are available for Controllers, Off Normal points, Disabled points, Configuration, Doors, and Pages. The summaries are accessed through Summary on the main menu or using the tools on the Summary toolbar.


Controller Summary

This summary lists all of the points in the controller to which you are currently connected. The columns in the list box show the following information:

✦ Address – the system address and point type of the point. This is also the default name assigned to a point by TAC I/NET Seven.

✦ Class – the point class of the point (internal, external, indi-rect).

✦ Name – the point name assigned by TAC I/NET Seven, or by a user.

Follow the steps below to display a Controller Summary:

1. Connect to the desired controller.

2. Select Summary Controller, or click the Controller tool on the Summary toolbar. The system displays the Controller Summary screen (see Figure 7-1).


Controller Summary Summaries

In line with each point is the status or value of the point as well as a “–” or “Y” in the Value, Alm, Inh, Tst, Man, Old, and Ack columns. These indicators stay in line with the points if you move the position of the list box. Table 7-1 lists and describes each column in the point line.

Figure 7-1. Controller Summary

Table 7-1. Controller Summary Values and Indicators

Column Description

Value This column shows the current state or value of the point. This is updated at the refresh interval you supplied in the Host Configuration editor.

Alarm (Alm) This column indicates whether the point is in alarm or not.

Inhibit(Inh)

The Inh column indicates whether or not a point is inhibited by an alarm inhibit-enable extension associated with this point. This is applicable only for AI, GI, DM, and DA points. A Y in this column indicates that this point is inhibited and will not report an alarm if the point goes into alarm.

Test Mode (Tst)

The Tst column indicates whether or not the point is in test mode. The Test mode lets you set the value of output or input points to a desired value or state. Refer to “Test Mode” on page 7-4 for more information.

Manual Mode (Man)

The Man column indicates whether or not the point is in the manual mode. This lets you selectively freeze the operation of a point in its current position. This function is available for output points only. Refer to “Manual Mode” on page 7-4.


Summaries Controller Summary

From the Controller Summary you can control a point or zoom from a selected point to that point’s editor. You may also sort the summary list by either point number or name.

Controlling a PointUse the following procedures to control a point.

1. Select the point in the Controller Summary list.

2. Select Control. The system displays the Point Control screen (see Figure 7-2).

This screen provides the following options for controlling a point:

✧ Test Mode On/Off

✧ Manual Mode On/Off

✧ Point Acknowledge

✧ Release

✧ APB Reset

OldThe Old column indicates whether or not the point value is invalid or no longer communicating.

Acknowledge (Ack)

The Ack column indicates whether the point has an unacknowledged alarm condition. You may acknowledge an alarm from this summary by highlighting the point and then selecting Alarm Ack.The Y in the Ack column will disappear. If the point is still in an alarm state, it continues to display in red indicating its continued alarm status.

Figure 7-2. Point Control Screen

Table 7-1. Controller Summary Values and Indicators (Continued)

Column Description



3. Choose the desired control option. Procedures for using each option are described below.

4. When you are finished, select Close to return to the Control Summary screen.

Test Mode

Use the Test mode to isolate one or more points from external hardware. This allows you to verify controller operation for selected points without affecting or using the external hardware. This also allows you to manually enter states/values for points. Refer to the chapter dealing with controller functions in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about the Test mode.

1. From the Point Control screen, select Test On. The system displays TEST in the point status bar while the point is in Test mode.

2. If necessary, set a state or value for the point and select Down-load. The state/value displayed in the point status bar changes to the new setting.

Note: While using the Test mode, the controller continues to update the database for the selected point. Your states or values for the point can be overridden by the controller. To prevent the controller from over-riding your states or values, also place the point in Manual mode.

3. When you are finished using Test, exit the mode by selecting Test Off. The TEST indication is removed from the point status bar.

4. Select Close to leave the Point Control screen and return to the Controller Summary screen.

Manual Mode

Use the Manual mode to freeze an output point at its current state/value and, if desired, manually control the point. Unlike the Test mode, the point is not isolated from connected hardware while in Manual mode. States or values that you download to the point


Summaries Controller Summary

are sent to the connected hardware. An exception to this is when both the Manual mode and Test mode are selected at the same time. Refer to the note in the Test mode description above.

1. From the Point Control screen, select Manual. The system displays MAN in the point status bar while the point is in Manual mode.

2. If necessary, set a state or value for the point and select Down-load. The state/value displayed in the point status bar changes to the new setting.

Note: If external hardware is connected to the selected point, the state or value you enter is also sent to the connected hardware.

3. When you are finished using Manual, exit the mode by selecting Automatic. The MAN indication is removed from the point status bar.

4. Select Close to leave the Point Control screen and return to the Controller Summary screen.

Point Acknowledge

If ACK is displayed in the point status bar (or in the status line for the point in the Controller Summary screen), then the point has gone into alarm and has not yet been acknowledged. You can acknowledge the alarm from the Point Control screen by selecting Acknowledge. This option is also available on the Controller Summary screen.

Release

Use the release option to unlock a door for the programmed strike duration. From the Point Control screen, select Release. This option is only available for door points.

Reset Anti-passback1. If the selected point is a door, the APB Reset button can be

used to manually reset the anti-passback function for an indi-vidual. From the Point Control screen, select APB Reset to open the Manual APB Reset screen (see Figure 7-3).



2. Select a Tenant from the drop-down list to display the indi-viduals assigned to this door. You may select all tenants for a list of all individuals assigned to the door.

3. Select the individual you wish to reset, or select All from the individuals list to reset all individuals for the selected tenant.

4. Click the OK button to reset the selected individual and return to the Point Control screen, or Cancel to close the screen without resetting.

Zooming to a PointThe Controller Summary screen allows you to “zoom” to the Resi-dent I/O Point editor for the selected point. Selecting Zoom is the same as selecting Edit Controller Resident I/O Points from the main menu, and then selecting the desired point from the point list. Refer to Chapter 5, Point Definition and Addressing, for more information about the Resident I/O Points editor and its uses.

Sorting the PointsThe Controller Summary screen allows you to sort the summary list by either the point address or the point name.

Figure 7-3. Manual APB Reset Screen – Point Control


Summaries Off Normal Summary

1. Select Sort to display the dialog box shown in Figure 7-4.

2. Chose the sort order you desire, either Point Number or Point Name.

3. Click OK. The controller summary list will display the avail-able points in the chosen sort order.

Off Normal Summary

This summary displays all points in an alarm or in a questionable state (old).

Note: Before a point will display in this summary, you must select the controller containing these points in the Network functions editor (refer to Chapter 2, Setup and Network Configuration).

1. Select Summary Off Normal Point, or click the Off Normal tool on the Summary toolbar. The system displays a dialog box informing you that the summary is being prepared.

2. All off normal points display in a dialog box shown in Figure 7-5.

3. You may acknowledge a point in alarm by highlighting the point in the list, and then selecting Acknowledge.

4. You may move to the system page that contains the point in alarm by highlighting the point and then selecting Page Ack.

5. Select Close when you are finished.

Figure 7-4. Point Sort Type


Disabled Summary Summaries

Disabled Summary

The disabled summary displays all points that are in test or manual mode.

Note: Before a point will display in this summary, you must select the controller containing these points in the Network Functions editor (refer to Chapter 2, Setup and Network Configuration).

1. Select Summary Disabled Point, or click the Disabled Point tool on the Summary toolbar. The system displays a dialog box notifying you that the summary is being prepared.

2. All disabled points display in the Disabled points summary shown in Figure 7-6.

3. Select Close when you are finished.

Figure 7-5. Off Normal Points Summary


Summaries Configuration Summaries

Configuration Summaries

Select Configuration from the list of summary options. You must be connected at the level of the configuration you wish to display.

Host SummaryTo display the available Host Taps connected to your system press Host. If your system is configured with an Ethernet LAN, the host summary displays all operator and backup stations connected to the Ethernet LAN.

If your host is on a host or controller LAN, the host summary displays the Host Tap’s name and revision level.

The potential columns in the list show the following information:

✦ Address – the system address for that Tap or host.

✦ Host PC name - the assigned host name.

✦ Type – the type of device.

Figure 7-6. Disabled Points Summary


Configuration Summaries Summaries

✦ Revision – the revision number and date of the firmware in the device.

1. Select Host to display connected Host Taps.

2. Highlight the desired link and then select Link or Station to display available devices connected to that host Tap.

3. Select Close to return to the main menu.

Link SummaryThis option displays all link Taps available through the connected operator station. If you connect to a remote operator station through the Ethernet LAN, this summary displays the available links at the remote station. The screen display is similar to the Host Summary screen in Figure 7-7.

The columns in the list show the following information:

✦ Address – the system address for that Tap.


✦ Link tap name – the assigned name of the device.


1. Select the Link to display connected links.

Figure 7-7. System Configuration – Host Summary


Summaries Configuration Summaries

2. Highlight the desired link and then select Station to display available stations connected to that link Tap.


Station SummaryThis option displays the controllers available through the connected link Tap. Separate controller LANs on a link with multiple LAN Taps are also identified. Only LAN Taps and their phone numbers are listed 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 (see Figure 7-8).



✦ Site – the address of the site Tap (if applicable).


✦ Station name – the assigned name of the device.

✦ Stations – the number of stations on this device.


Figure 7-8. System Configuration – Station Summary


Configuration Summaries Summaries

1. From a selected host or link, select Station to display the connected stations.


UC SummaryThis option displays all the unitary controllers connected to the 7760 controller (UCI) to which you are connected. This screen indicates whether a connected MR is communicating.



✦ Site – the address of the connecting site Tap (if applicable).


✦ Status – the communication status of the device.

1. From a selected host or link, select Station to display the connected stations.


MR SummaryThis option displays all the micro regulator controllers connected to the SLI controllers on the associated controller LAN. This screen indicates whether a connected MR is communicating.






1. From a selected host or link, select MR to display the connected stations.



Summaries Door Summary

DPU SummaryThis option displays all the DPUs (DPU7910s, DPU7920s, and SCU1284s), DIOs (DIO7940s and SCU1280s), and DIUs (DIU7930s and SCU1200s) connected to the SLI controllers on the associated LAN. This screen indicates whether a connected device is communicating.






✦ Rev/Date – The revision number and date of the device’s firmware.

1. From a selected host or link, select DPU to display the connected devices.


Door Summary

This summary lists all of the door points defined for the selected tenant. The columns in the list box show the following informa-tion:

✦ Select – doors marked with “[X]” are selected and doors marked with “[ ]” are not selected. You may toggle selection of doors and apply the Secure, Unlock, Lock, Manual Off, and Release functions to all selected doors.

✦ Address – this is the system address of the door point. This is also the default name assigned to the point by TAC I/NET Seven.

✦ Name – this is the point name assigned by TAC I/NET Seven or by a user.

✦ Man – this column displays an “M” for each door point that is in Manual mode.


Door Summary Summaries

✦ Value – this column shows the current state of the door point (Secure/Locked/Unlocked).

Follow the steps below to display a Door Summary:

1. Select Summary Door from the main menu. The system displays a list of Tenants (see Figure 7-9).

2. Choose the desired tenant and select the Summary button. The system displays the Door Summary (see Figure 7-10).

This screen lists all doors assigned to the selected tenant.

3. Use Secure, Unlock, Lock, Manual Off, and Release to control all selected door points. Click on the individual point to select ([X]) or deselect ([ ]) them. Use the mouse to toggle door point selection.

Note: Any time a door’s mode is changed, the door point is automatically placed in the “Manual” mode. Remember to return the door points to the Automatic mode when you are finished controlling them. (This does not apply to the Release operation.)

4. Select APB Reset to manually reset the anti-passback func-tion for an individual.

Figure 7-9. Tenants List


Summaries Door Summary

a. Click the APB Reset button. The Manual APB Reset screen appears (see Figure 7-11).

b. The Tenant that you selected when opening the door summary is already selected. The lower window lists the individuals assigned to the door from the selected tenant.

Note: You cannot change the tenant selection on this screen. To change the tenant, close the Manual APB Reset screen and the Door Summary, and select a different tenant for the Door Summary. If you wish to be able to select tenants during APB reset, use the APB reset function from the Point Control screen of the Controller Summary (see “Controlling a Point” on page 7-3).

c. Select the individual you wish to reset, or select All from the individuals list to reset all individuals for the selected tenant.

d. Click the OK button to reset the selected individual and return to the Door Summary, or Cancel to close the screen without resetting.

Figure 7-10. Door Summary


Page Summary Summaries

5. Select Close to return to the Tenant Selection window and then select Close again to return to the main menu.

Page Summary

This summary lists all of the points appearing on a system page. The columns in the list box show the following information:

Note: The point Class and Name are not displayed while the system is connected via a dial connection from a graphic page dial icon. The system has no way of knowing the point name or type. The point Class and Name will be displayed during direct connect.

✦ Address – includes the link (0-99), station (0-63), point (0-31), bit offset (0-9), and point type associated with each entry.

✦ Class – shows the Class assigned to a point (i.e. Ext, Int or Indirect).

Figure 7-11. Manual APB Reset Screen – Door Summary


Summaries Page Summary

✦ Name – 16 character name defined in the Resident I/O Points Editor. (See note above.)

✦ Value – current state or value of the associated point. This text is defined in the station parameters editor. The display is updated according to the refresh interval defined in the Host Configuration Editor.

✦ Alm – indicates that a point is in alarm.

✦ Ack – a "Y" appearing in this column indicates that the associ-ated point is in alarm or at one time was in alarm, and that the point has not been acknowledged by an operator.

✦ Inh – alarm Inhibit indicator. If a "Y" is present, the associated point is inhibited from generating/reporting any alarm condi-tion. This function requires an Alarm Inhibit extension on the point.

✦ Tst – test indicator for input and output points. For input points, this will ignore all input stimulus on the external hardware and allow normal processing of the commanded test value. For output points, this will allow normal processing of all manual and automatic functions but will not energize/control any hardware outputs.

✦ Man – manual indicator for output points only. This will disable all automatic functions from controlling the external hardware (i.e., ATS, DDC, Demand, etc.).

✦ Old – old data indicator for input and output points. If the system has determined that the point’s value is not valid, a "Y" will be placed in this column for the associated point.

Follow the steps below to display a Page Summary:

1. You must already be displaying a system page before you initiate a Page Summary. If a system page is not displayed, select System Live Graphic Pages, or click the Live Graphic Page tool on the System toolbar, and select a system page.

2. Select Summary Page, or click the Page tool on the Summary toolbar. The system displays the Page Summary screen (see Figure 7-12) This screen lists all points appearing in the system page.


Page Summary Summaries

The following functions are available from the Page Summary:

✦ Control – this function takes you to the point control dialog where the selected point can be controlled.

✦ Clipboard – this function copies the entire summary to the Windows Clipboard.

✦ Zoom – this function takes you to the appropriate editor for the specific point type.

✦ Acknowledge – use this function to acknowledge a point in alarm.

✦ Page Ack – this function acknowledges all displayed points that are in alarm. This function only affects the points currently displayed. The point list can display 18 points at a time. If necessary, scroll up or down to display more points and then select Page Ack again.

Figure 7-12. Page Summary


C H A P T E R78

8

© 2001–2010 SchTCON299–05/10

System Pages

System pages are graphical representations of your system. They can include graphic images, as well as the current state and value of your system components.


You can construct as many pages as you need to represent your system. Each page can represent a portion of the system. For example, if you are controlling multiple buildings you may want separate pages for each building. Or, you may want one single page to represent a specific, vital function.

The components you place on each page are up to you. Figure 8-1 and Figure 8-2 are examples of the type of system pages you can construct.

Figure 8-1 shows a system page depicting an office layout. Notice that there are indicators for the door status and temperature. In addition, there are two icons that connect to other system pages. Figure 8-2 shows a simple representation of a mixed air handler.

As both examples illustrate, system pages may contain separate, dynamic data fields called points. Each point represents an internal, external, or remotely connected system component. You may use any one point as often as you require it.

System pages are constructed in TAC I/NET Seven’s Graphics Editor. The Graphics Editor provides a full range of graphic tools and easy access to TAC I/NET Seven points. You can save frequently used graphics as TAC I/NET Seven symbols (.gls) and you can


System Pages

import bitmap (.bmp) files created in other graphic programs. After constructing your system page within the Graphics Editor, you can display the page in “live” mode within TAC I/NET Seven.

System pages can contain the following objects:

Figure 8-1. Sample system page

Figure 8-2. Second sample system page


System Pages The Graphics Editor

✦ Text

✦ Graphics objects created with the TAC I/NET Seven Graphics Editor

✦ Imported graphics objects in bitmap (.bmp) files

✦ Library Symbols from the TAC I/NET Seven Symbol Library

✦ Page reference icons to jump to alternate system pages

✦ Points (dynamic data fields)

✦ Other icons (modules, lines, doors, etc.)

This chapter provides the information you need to create system pages and also includes instructions for displaying live pages. The system pages are an important part of the system and you will use them frequently as you learn the system and customize it to meet your individual needs.

The Graphics Editor

The TAC I/NET Seven Graphics Editor provides the tools you need to create and modify system pages. The Graphics Editor has its own set of menus and toolbars. Many of the menu commands are also available as a toolbar button. Where this is the case, the toolbar icon is displayed in the left margin and the equivalent menu command is on the right, in bold print.

Working with System PagesThis section explains how to access the Graphics Editor, open and close system pages, and set the default system page.

Creating a New System Page

Edit Host Computer Graphics Editor

1. Access the Graphics Editor, from TAC I/NET Seven, using the menu command, or by clicking on the New tool located on the System toolbar. You are automatically presented with a new, blank system page.

You may also use the New tool to create a new system page from within the Graphics Editor.


The Graphics Editor System Pages

Editing an Existing System Page

You can easily edit existing system pages. To open an existing system page from the Graphics Editor, perform the following steps:

File Open

1. From within the Graphics Editor, select the Open tool, using either the Open button on the System toolbar or the menu command above. The Open dialog box displays.

Note: You must be in the Graphics Editor to use the Open menu command. If you are in TAC I/NET Seven, use the Open toolbar button.

2. Scroll through the browser to locate the file. Select the file and click Open to begin editing the system page.

Note: Refer to “TAC I/NET 4.x Graphic Pages” on page 5, for information on using graphic pages created with a previous version of TAC I/NET,

If you select the Open tool button from the TAC I/NET Seven menu, you are automatically presented with the Graphics Editor menus.

Exiting the Graphics Editor

After you have finished editing your system page, you will need to return to the main TAC I/NET Seven system.

Saving and Exiting

The Close option in the Graphics Editor File menu allows you to close the Graphics Editor and return to the main TAC I/NET Seven menus.

1. Select File Close.

2. If you are editing a named, existing file and have made no changes, the editing session will be ended immediately.

3. If you made changes to a previously saved file, a dialog box prompts you to save the changes. From this dialog box, you have two options:

✧ Select Yes to overwrite the existing file.



✧ Select No to end the session, leaving the existing file unchanged.

4. If you are editing an new file, a dialog box prompts you to save the file. From this dialog box, you have two options:

✧ Select No to end the editing session, losing all graphics created during the session.

✧ Select Yes to display the Save As dialog box.

5. If you selected Yes in Step 4, specify a directory and filename for the save operation. Once the file is selected or entered, select OK .

TAC I/NET 4.x Graphic Pages

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.

Note: Refer to TCON157, TAC I/NET Forms and Worksheets Getting Started, for a complete discussion on converting system pages.

Opening *.PAG Files

Use the following procedure to open TAC I/NET 4.x graphic pages:

File Open

1. From within the Graphics Editor, select the Open tool, using either the Open button on the System toolbar or the menu command. The Open dialog box displays, as shown in Figure 8-3.

2. Select the correct directory.

3. Click the down-arrow and select I/NET 4.XX Graphic Page Files (*.pag) in the Files of type field. Only files with a *.pag extension will display in the browser.

4. Select the file and click Open to display the graphic page.



When you save the file, TAC I/NET Seven automatically saves it in the new format with a .gpg extension.

Loading a *.BOL file

You can use library symbols created with TAC I/NET 4.x by following the procedure below.

File Load Library Symbol

1. Use the menu command shown above to access the Open dialog box.

2. Select the correct directory.

3. Click the down-arrow and select I/NET 4.XX Library Symbol Files (*.bol) in the Files of type field. Only files with a *.bol extension will display in the browser.

4. Highlight the file and a preview appears in the bottom of the dialog box, as shown in Figure 8-4.

5. Select the file and click Open to load the symbol.

Figure 8-3. Open Dialog Box



6. You can insert the symbol just as you would one with a .gls extension by using the Graphic Insert tool on the Drawing toolbar.

Working with Graphic ObjectsThis section details the fundamental skills necessary to draw, insert, copy, import, position, resize, and reposition graphic objects, icons, points, and text.

Selecting Objects

If you wish to modify or reposition an object you will first need to select it.

Tools Select

1. To use the Select pointer ( ), click the Select button on the Drawing tools toolbar or select the menu command. (Refer to “Select Tool” on page 8-36.)

Figure 8-4. Open a Library Symbol dialog box.



2. Position the Select tool on the object to be selected, and click the left mouse button to display the object handles, as shown in Figure 8-5. Object handles indicate that the object is currently selected.

3. To select multiple objects, position the Select tool near the object to be selected. Click the left mouse button, and drag the mouse to enclose the desired objects within the selection box (a dashed line), as shown in Figure 8-6 on page 8-8. Release the mouse button to display the object handles.

An alternative way to select multiple objects is to press the Shift key while clicking on each object.

Deselecting Objects

To deselect a selected object(s), either select another object or posi-tion the pointer on a background area and click the left mouse button.

Deleting Objects

Objects on the Graphics Editor screen can be deleted by performing the following steps:

1. Select the object(s).

Figure 8-5. Selecting a Graphics Object

Figure 8-6. Selecting Multiple Graphics Objects



2. Select Edit Clear or press the Delete key.

Positioning Objects

Objects can be positioned by performing the following steps:

1. Select the object.

2. Click and hold the left mouse button while dragging the object to its new position.

3. When the object is in the new location, release the mouse button.

You can gain additional precision by using the arrow keys to posi-tion an object.


2. Move the object up, down, left, or right, 1 pixel at a time by pressing the appropriate arrow key. Move the object one grid setting at a time, by pressing the Control key simultaneously with the arrow key. Refer to page 8-30 for information on setting the grid width.

Copying Objects

Perform the following steps to copy an object.

1. Hold down the Control key, click and hold the left mouse button, and drag a copy of the object to a new position, as shown in Figure 8-7.

2. When the copy is in the desired position, release the mouse button and Control key.

Figure 8-7. Copying a Graphic Object



3. The Graphics Editor also supports Windows’ Cut [Ctrl + X], Copy [Ctrl + C], Paste [Ctrl + V] and Paste Special functions. You can access these functions on the Edit menu.

Resizing Objects

An object on the Graphics Editor screen can be resized by performing the following steps:


2. Position the Select tool on one of the object handles.

3. To enlarge the object, click and hold the left mouse button while dragging away from the object in a diagonal direction, as shown in Figure 8-9. To reduce the object, drag toward the center of the object.

4. When the object is the desired size, release the mouse button.

5. You can also resize object by used the Scale tool. Refer to page 8-34 for more information on this tool.

Mouse Shortcuts

Mouse shortcuts can be used when editing graphic pages to stream-line the process. These shortcuts work in exactly the same way as selecting the corresponding command from the TAC I/NET Seven Graphic Page editor menus and toolbars.

Figure 8-8. Selecting a Graphics Object Handle

Figure 8-9. Resizing a Graphics Object



Table 8-1. Graphics Editor Mouse Shortcuts

Selection Action Result

click select object

arc tool click and drag draw shape (size depends on start and end points)

arc tool right click cancel tool

arc tool Shift+click and drag draw shape with height = width

bezier curve tool click start object or add point

bezier curve tool click and drag draw segment

bezier curve tool double-click finish object

chord tool click and drag draw shape (size depends on start and end points)

chord tool right click cancel tool

chord tool Shift+click and drag draw shape with height = width

circle tool click and drag draw shape (size depends on start and end points)

circle tool right click cancel tool

circle tool Shift+click and drag draw shape with height = width

ellipse tool click and drag draw shape (size depends on start and end points)

ellipse tool right click cancel tool

ellipse tool Shift+click and drag draw shape with height = width

fill tool click set background color

fill tool right click deselect tool

free pen tool click and drag draw (while mouse button is pressed)

header double-click maximize page

library symbol click add currently selected symbol to selected location

line tool click and drag draw shape (size depends on start and end points)

line tool right click cancel tool

line tool Shift+click and drag draw straight line (horizontal or vertical)

menu bar double-click toggle between graphics menu and I/NET menu

object arrow (cursor) key move object one pixel

object click and drag select all objects within the defined rectangle

object Ctrl+arrow (cursor) move object (grid setting = number of pixels moved)

object Ctrl+click clone object

object drag move object

object drag (on handle) resize object

object right click view special menu for object

object right double-click edit object properties

object Shift+arrow (cursor) resize object



object Shift+click select multiple objects

object Shift+double-click de-select object (used with multiple selections)

object Tab change selection to next object

object + fill tool click fill selected object with current brush pattern/color

object + fill tool right click outline selected object with current pen pattern/color

object + polygon tool double-click toggle fill mode on selected object

pie slice tool click and drag draw shape (size depends on start and end points)

pie slice tool right click cancel tool

pie slice tool Shift+click and drag draw shape with height = width

point double-click open Resident I/0 Points editor

point right-click display the graphics editor pop-up menu

point right double-click display the Drawing Styles window

point (on live page) double-click display the Point Control dialog

point (on live page) right-click display a pop-up menu of commands

polygon tool click start object or add point

polygon tool click and drag draw segment

polygon tool double-click finish object

polyline tool click start object or add point

polyline tool click and drag draw segment

polyline tool double-click finish object

rectangle tool click and drag draw shape (size depends on start and end points)

rectangle tool right click cancel tool

rectangle tool Shift+click and drag draw shape with height = width

rounded rectangle tool click and drag draw shape (size depends on start and end points)

rounded rectangle tool right click cancel tool

rounded rectangle tool Shift+click and drag draw shape with height = width

splitter bars click split screen at location of click (vertical & horizontal)

splitter bars double-click remove split screen

text box double-click edit text

text tool click and drag define text box (size depends on start & end points)

toolbar double-click toggle dock/undock

toolbar drag dock/undock

toolbar dock right click toggle show toolbars

Table 8-1. Graphics Editor Mouse Shortcuts (Continued)




System ToolsSome of the functions discussed below are available on the TAC I/NET Seven System Toolbar. The remainder are on the Graphic Editor’s File menu. Refer to Chapter 1, TAC I/NET Seven Basics for information on the System Tools.

When a toolbar button is available it is shown in the left margin and the equivalent menu command is to the right in bold print.

File Management

File management includes creating new files, opening existing files, and saving files. Refer to “Working with System Pages” on page 8-3 for additional information on file management.

File New

This command opens a new, blank system page.

File Open

This command opens an existing system page. The Open dialog box allows you to browse through folders to locate the file you need.

File Close

This command closes the open system page. You will be prompted to save any changes you have made to the page. If that page is the only open page, Close also exits the Graphics Editor and returns to TAC I/NET Seven.

File Save

This command saves the system page. If you are saving the file for the first time, the Save As dialog box displays.

zoom tool click return to normal (1:1) magnification

zoom tool click and drag zoom to rectangle of the selected area

Table 8-1. Graphics Editor Mouse Shortcuts (Continued)




File Save as...

This command permits you to specify a new filename. The Save As dialog box automatically displays if you are saving a file for the first time. Otherwise, you must select the Save As command. This command is particularly useful for making copies of existing system pages.

Library Symbols

Library symbols provide you with the capability to save graphic objects outside of a system page. This feature is very handy for complicated graphics or graphic components that you will use on other system pages.

File Save As Library Symbol

1. Select the object you want to save.

2. Select File Save Library Symbol.

3. Locate the folder you want the file to be located in, enter a filename, and select Save. The file extension .gls indicates to TAC I/NET Seven that the file is a library symbol and is auto-matically added to the filename.

File Load Library Symbol

This command works exactly like Load Bitmap, (described below) except it loads TAC I/NET Seven library symbol files (.gls) instead of bitmaps. As with bitmap files, once the graphic is loaded you are automatically presented with the Symbol tool and can insert the graphic multiple times. You can load one of the standard library symbols supplied with TAC I/NET Seven or one that you have created.

TAC I/NET Seven supplies many library symbols. The installation program typically places the symbol files in a directory named Symbols. You may also load library symbols created in previous versions of TAC I/NET. Refer to “TAC I/NET 4.x Graphic Pages” on page 5 for more information.

To import an existing library symbol, perform the following steps:

1. Select File Load Library Symbol to display the Open dialog box as shown in Figure 8-10.



2. Select the filename of the desired library symbol file in the edit field and a preview appears in the preview box.

3. Select Open to close the dialog box. The Graphic Insert tool is automatically selected.

Figure 8-10. Select A Library Symbol Dialog Box



4. Position the pointer and click the left mouse button to insert the Library Symbol in the Graphics Editor screen as shown in the example in Figure 8-11.

Importing Graphics

The Graphics Editor provides two different functions to import bitmap(.bmp) graphics. You can insert a bitmap anywhere on the page or you can specify the bitmap be used as the system page back-ground.

To insert a bitmap anywhere on the page use the Load Bitmap command.

File Load Bitmap

This command calls the Load Bitmap dialog box shown in Figure 8-12.

1. Select File Load Bitmap.

2. Select the bitmap file and click Open.

3. Position the pointer and click the left mouse button to insert the object.

Figure 8-11. Loading A Library Symbol



Once you select the bitmap file, the Symbol tool (located on the Drawing tools toolbar) is automatically used to insert the graphic.

Follow the steps below to select a bitmap graphic to use for a system page background.

File Set Background

1. Select the bitmap (.bmp) file from the Select a Bitmap dialog box and click Open.

2. A dialog box appears asking if you want the bitmap stretched to fit the screen. Select Yes to resize it, or No to keep the orig-inal size.

3. To remove the background from the page, select File Remove Background.

Printing Functions

To access the printer setup functions:

1. Select File Printer Setup.

Figure 8-12. Load A Bitmap Dialog Box



2. From the print Setup dialog box, you can select a printer and specify the paper size, paper source, and print orientation.

To preview a printed page:

1. Select File Print Preview.

2. Print Preview will show you the page as it will be printed. You may use the Zoom button to enlarge the preview. Select Close to return to the Graphics Editor or Print to print the page.

To print a system page:

1. Select File Print from the Graphics Editor menu.

2. The Print dialog box allows you to print to a file, select a print range and specify a number of copies. Click OK to print the page.

Address Conversion

Occasionally, you may wish to change the address defined for one or more icons or markers on a graphic page. For example, you may have changed the station number assigned to a controller which, in turn, requires you to modify graphic icon addresses to reflect the controller’s new station number.

Perform the following steps to modify graphic item addresses:

1. Select File Address Conversions to display the editor, as shown in Figure 8-13.

2. Choose the appropriate icon type from Options section. Your choices are points, modules, lines, door icon, or ASC marker. The option you select determines which items are included in the scrolling list.

3. In the Items Defined on Page scroll list, click the items you need to change. An X appears in the first field of the list to indicate that entry is selected. Remove an entry from the selected list by clicking on it again. Use the All Yes and All No buttons to speed the selection process.

4. Select the Target Address options that you need to change by clicking in the appropriate checkbox. You do not have to select any parts of the address that do not require modifica-tion.



For example, if only the station number has changed, select only the Station option. In this case, the remaining options retain their previous values.

5. Select Replace to convert the address of the selected items.

6. Select Close to exit from the Address Conversion editor.

Summary

You can view information about the current system page with File Summary Information. The resulting Document Properties box has two tabs. The first tab, Summary, (shown on the left side of Figure 8-14) provides you with a convenient location for

Figure 8-13. Address Conversion Editor



comments and other information about the system page. Much of the information contained in the Summary page will be displayed when you select a file with the File Open command.

The second tab, Statistics is shown in the right side of Figure 8-14. Along with system data, Statistics provides a count of all the objects on the page, broken out by the number of points, the number of drawn objects and other objects.

View ToolsThe Graphics Editor allows you display a background grid, estab-lish default window colors, and arrange and view toolbars. The View Menu contains most of the tools you need to customize your workspace.

Graphics Properties

TAC I/NET Seven displays the Graphics Properties dialog when you select View Graphics Properties from the graphics editor menu (see Figure 8-15). Use this dialog to set default operational properties for your graphic pages.

Figure 8-14. Summary Information



Text Colors

Use the following options to set the default colors applied to the value of points placed on your graphics page.

✦ Text Pen – Use this option to choose a default foreground color for point text. When you select this option, the system displays the Color dialog. You can choose a standard system color, or you can define a custom color. This setting will be ignored if you have activated () the Use Object Pen option described below.

✦ Use Object Pen – When activated (), this option causes the default color for point values to be the color defined within the point's font properties. Otherwise, point values are displayed in the color you choose using the Text Pen option described above.

The Use object pen setting does not affect the color of text objects or markers. It also has no affect on points that have already been placed on the graphic page.

Figure 8-15. Graphics Properties



Live Colors

Use the following options to set the colors applied to the point icons on your graphics page based on the point's alarm status.

✦ Alarm – Use this option to choose a color for the icon of point that is in alarm.

✦ Return Normal – Use this option to choose a color for the icon of point that went into alarm and then returned to normal without being acknowledged.

✦ Acknowledge – Use this option to choose a color for the icon of point that is in alarm but has been acknowledged.

Alternate Graphics Path

When TAC I/NET Seven can't find a file referenced by a page marker or by a graphics symbol on your graphics page, it can search alternate paths for the missing file. Use the following options to define alternate paths.

✦ Pages – Use this option to specify one or more alternate paths for files referenced by page markers.

✦ Symbols – Use this option to specify one or more alternate paths for graphic symbols referenced by your graphic page. This includes files placed using the Graphics Insert function or graphic symbols used to display the 0 and 1 states of discrete points.

You can define multiple paths by separating each path with a semi-colon (;). In the following example, the system will search “C:\GRAPHICS” and “D:\PAGES” if a graphic page file cannot be found at its original location.

Example: c:\graphics;d:\pages

Attributes

Use the following options to adjust how graphic pages are displayed.

✦ Open pages maximized – Activate () this option to cause graphic pages to open maximized.



Depending on the setting of the Override window function option (described below), this option may be overridden by the window layout settings assigned to a user's host password. Refer to “Controlling Window Layouts in TAC I/NET Seven” on page 1-23 for more information.

✦ Override window function – Activate () this option to allow the Open pages maximized option (described above) to override the window layout settings assigned to a user's host password (i.e., graphic pages will always open maxi-mized, regardless of the user's stored window layout informa-tion).

Page Properties

TAC I/NET Seven displays this dialog when you select View Page Properties from the graphics editor menu (see Figure 8-16). You can also display this dialog by select Defaults... from the Fill, Pen, and Text menus.

Figure 8-16. Page Properties



This dialog provides the following tabbed panels:

✦ Attributes

✦ Default Fill

✦ Default Pen

✦ Default Text

Each panel is described below.

Attributes

The Attributes panel (see Figure 8-16) provides the following options:

✦ Page Size – Use the spindials in this section to specify the Width and Height of the graphic page. These values represent pixels.

✦ Grid – Use these parameters to configure and display a grid that can be used to help you create and position graphic objects.

✧ Show – Activate () this option to display the grid.

✧ Color – Use this option to set the grid color. The system displays the Color dialog, allowing you to choose a stan-dard color, or define a custom color.

✧ Width – Use this spindial to set the horizontal spacing for the grid. This value represents pixels.

✧ Height – Use this spindial to set the vertical spacing for the grid. This value represents pixels.

✦ Backdrop – Use the Backdrop properties to select and configure a background bitmap image for your page.

✧ Show – Activate () the Show option to display the backdrop.

✧ Stretch to fit – Activate () the Stretch to fit option to force an image to occupy the entire window. If you resize the window to a height or width that is larger than the image, the image will automatically stretch to fit. If you make the window smaller than the actual image size, than some areas of the image will be cropped out of view (i.e., the image will not be reduced smaller than original image size).



✧ Select – Use the Select button to browse for an image to be used as a backdrop. The path to the backdrop image will be displayed in the text field next to the Select button. You can also manually type a path in this field. This feature can be especially useful if you wish to define a relative path (e.g., ..\images\lobby.bmp) rather than an absolute path (e.g., c:\bldg01\images\lobby.bmp).

✦ Window Fill – Use the Window Fill properties to define and apply a fill to the background of your page.

✧ Show – Activate () the Show option to display the fill.

✧ Pattern – Choose a Pattern from the drop-down list. Refer to Fill Patterns for a description of the available patterns.

✧ Colors – Select Foreground to set the foreground color of the fill. When you select this option, the system displays the Color dialog. You can choose a standard system color, or you can define a custom color.

Select Background to set the background color of the fill. When you select this option, the system displays the Color dialog. You can choose a standard system color, or you can define a custom color.

Note: You can also use the Set Window Fill and Clear Window Fill options in the View menu to control the background fill.

Default Fill

This panel provides Fill Attribute options and a Preview. Use this panel for the following options:

Note: The Preview allows you to immediately view your settings before you accept them. If it appears that the Preview is not showing your changes, ensure that the foreground and background colors are not set to the same color.

✦ Pattern – Use this option to choose a fill pattern for your graphics. This option provides the same functions as the Fill menu item. Use Preview to view your selection.



✦ Foreground – Use this option to choose a foreground color for the fill pattern. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

✦ Background – Use this option to choose a background color for the fill pattern. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

✦ Transparent – Use this option to make the background of the fill transparent, allowing graphics behind the object to show through.

Default Pen

This panel provides Pen Attributes options and a Preview. Use this panel for the following options:

✦ Pattern – Use this option to choose a pen pattern for your graphics. This option provides the same functions as the Pen menu item. Use Preview to view your selection.

✦ Color – Use this option to set the pen color. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

✦ Line Weight – Use this option to set the line thickness (pixels) of the pen.

Default Text

This panel provides text options and a Preview. Use this panel for the following the options:

✦ Font – This option allows you to choose the default font for text. When you select this option, the system displays the Font dialog, allowing you to choose a font, font style, and size.

✦ Colors – This section provides functions that allow you to control the colors and transparency used for text.

✧ Foreground – Use this option to choose a foreground color for text. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.



✧ Background – Use this option to choose a background color for text. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

✧ Transparent – Use this option to make the background of text transparent, allowing graphics behind the text to show through.

✦ Alignment – Use this option to control the horizontal and vertical alignment of text. Use Preview to view your selec-tions.

✦ Attributes – This section provides functions that allow you to control miscellaneous text box attributes.

Note: The Word wrap function described below is only functional when you set the text alignment to “Top.”

✧ Word wrap – When you activate () this option, text will wrap as necessary to fit within the confines of the text box. If you deactivate () this option, the text will be cropped if it is wider or taller than the text box.

✧ Fit label – When you activate () this option, the text box will be automatically sized to allow all of its text to fit within the text box. If you deactivate () this option, text will be cropped if it does not fit within the confines of the text box.

✧ Use & to underline text – When you activate () this option, you can type an ampersand (&) before a char-acter to make the character be underlined. The amper-sand will not be visible within the text. If you deactivate () this option, ampersands will be shown and under-lining will not be possible.

✧ Box Text – Activate () this option to make the text box borders visible. If you deactivate () this option, text box borders will be invisible.



✧ Box Text as 3d box – Activate () this option to give text boxes a 3d appearance. When you activate this feature, the following additional options become avail-able:

✢ 3d Top – Use this option to choose the top and left side color for 3d text boxes. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

✢ 3d Bottom – Use this option to choose the bottom and right side color for 3d text boxes. The system displays the Color dialog, allowing you to choose a standard color, or define a custom color.

Zooming

View Zoom

Zoom enlarges a selected area for detailed viewing.

1. Select the Zoom tool, located on the Drawing Tools toolbar.

2. Drag an object selection box around the area you want to be enlarged. The area is enlarged.

3. To return to the normal view, select View Actual Size, or right-click on the page and select Actual Size from the context menu, or click the area a second time.

Window Backgrounds

The Graphics Editor allows you to set the color and fill pattern of a page, insert a bitmap graphic on the background, and display a grid.

If you have a bitmap graphic placed on the page background (refer to “Importing Graphics” on page 8-16) the graphic is placed on top of the window fill. The grid is displayed behind a graphic, but is placed on top of any color or fill patterns.



View Set Window Fill

View Clear Window Fill

Window Fill changes the page background to the color and fill settings specified in the Fill menu. If you later change the fill settings, the window background is not affected unless you select Set Window Fill again.

To set the page background:1. Select the color and fill options using the Fill menu or Pen

and Fill toolbar. Refer to “Fill Color” on page 8-47 for instruc-tions.

2. Select View Set Window Fill. Click Yes in the confirmation dialog box.

a. Alternatively, you can select the Fill tool on the Drawing Tools toolbar. Click on the page background and then click Yes in the confirmation dialog box.

b. Click the Selection tool to continue work on the page.

To clear a page background:

1. Select View Clear Window Fill.

2. Click Yes in the confirmation dialog box.

View Show Grid

Show Grid displays a grid on the current editing window to make it easier to align objects and create an accurately scaled system page.



View Set Grid

The Set Grid command calls a dialog box, shown in Figure 8-17, that allows you to specify the grid scale. The scale is in pixels with the width followed by height.

1. In the edit field, type the desired width, followed by a comma ( , ) , and then the height. If you enter only one number, the height and width will be proportional.

2. Click OK to close the dialog box.

Note: You must use the Show Grid option to view the grid.

View Redraw

Frequently, when working with graphic objects, remnants of deleted or moved objects appear to remain on the screen. The Redraw command redraws the window, eliminating any video trash from the display.

Toolbars

Many of the functions and tools available through the Graphics Editor’s menus are also available on a toolbar. You may choose which toolbars you wish to have displayed and you may choose their location on your workspace.

Table 8-2 lists the available toolbars and their function.

Displaying Toolbars

To conserve display space, you may want to display only the tool-bars that contain functions you use frequently. To choose the tool-bars to display:

Figure 8-17. Grid scale



1. Select View Toolbars. The menu shown Figure 8-18 displays.

2. Select the toolbar you wish to display. A checkmark to the left

of the toolbar option indicates that the toolbar is currently displayed.

3. To remove the toolbar from the display, click the toolbar. Use the Show all and Hide all to speed the toolbar selection process.

You can position the toolbars anywhere on your workspace. They may be docked or free-floating. Refer to “Toolbar Selection” on page 1-4 for additional information.

Table 8-2. Graphics Editor Toolbars

Toolbar Function

Arrange ToolbarSpecify the drawing order of selected objects

Coordinates Toolbar Display the position of the mouse pointer

Drawing Toolbar Graphic object drawing tools

Edit Toolbar Graphic object editing tools

I/NET Item Toolbar Access to points and other I/NET icons.

Alignment Toolbar Object alignment tools.

Pen and Fill Toolbar Pen and fill attribute tools

System Toolbar File administration tools

Text Toolbar Text appearance tools

Figure 8-18. Available toolbars



You may also specify whether to display the Status Bar, located at the bottom of the workspace. Choose View Status Bar to change the current status.

Edit ToolsThe Edit tools provide you with the capability to easily manipulate objects.

Included with the cut, copy, and paste functions are tools that rotate, flip, and alter the size of selected objects. All of the tools on the toolbar can also be found on the Edit menu.

Undo

Edit Undo

Reverses the last action.

1. Select Undo from the menu, or click the Undo tool, or type [Ctrl + Z], immediately after performing the action to be undone.

Cut

Edit Cut graphic

Cuts the selected object and places it on the clipboard.

1. Select the object to be cut.

2. Click the Cut tool or select it from the menu, or press [Ctrl + X]. The object is removed from the page and placed on the clipboard.

Copy

Edit Copy graphic

Places a copy of the selected object onto the clipboard.

Figure 8-19. Edit toolbar



1. Select the object to be copied.

2. Click the Copy tool or select it from the men, or press [Ctrl + C]. A copy of the object is placed on the clipboard. The object remains on the page.

Paste

Edit Paste graphic

Places the contents of the clipboard onto the page. Before you use the Paste function you must use either Cut or Copy to place an object onto the clipboard.

1. Click the Paste tool or select it from the menu, or press [Ctrl + V].

2. The clipboard contents are placed onto the page. Drag the object(s) to the location you prefer.

Clear

Edit Clear

Deletes the selected object(s).


2. Click the Clear tool or select it from the menu. The object is removed from the page.

Lock/Unlock

Edit Lock/Unlock

The lock setting prevents an object from being moved or modified. Set to Unlock if you need to edit the object later.


2. Click the Lock tool or select it from the menu.

3. To remove the lock setting, select the object and click the Lock tool again, or select Lock/Unlock from the menu.



Scale

Edit Scale

Scale can reduce or enlarge objects. The parameters are set as a percent of the x- and y-axes (i.e., width followed by height).

1. Select the object to be resized.

2. Click the Scale tool or select it from the menu. The Scale dialog box displays, as shown in Figure 8-20.

3. Enter the percent to scale. Numbers less than 100 reduce the object; numbers greater than 100 enlarge the object.

Note: If you enter a different number for the width than for the height, you will alter the proportion of the object as well as the size.

Rotate

The Rotate tools offer three different degrees of rotation. They all rotate in a counterclockwise direction.

Edit Rotate 90

Edit Rotate 180

Edit Rotate 270


2. Click the Rotate tool, or select it from the menu, that offers the degree of rotation you desire.

Figure 8-20. The Scale dialog box



Flip

This tool flips objects over a fixed horizontal or vertical axis.

Edit Flip Vertically

Edit Flip Horizontally


2. Click either the vertical or the horizontal Flip tool, or select it from the menu.

Select All

Edit Select All

This function selects all objects on the page. It is not available on the toolbar. Alternatively, you can press [Ctrl + A].

Clear All

Edit Clear All

This function deletes all objects on the page.

Drawing ToolsThe Graphics Editor contains a comprehensive selection of drawing tools. You will find these tools on the Tools menu or the Drawing Tools toolbar.

Many of these tools will remain active until you select either the Selection tool, another tool, or double-click in the workspace.

Figure 8-21. Drawing Tools



Select Tool

Tool Select

Choose the Select tool to return the pointer to normal selection mode.

Zoom

View Zoom

1. Select the Zoom tool.

2. Drag an object selection box around the area to be enlarged.

3. To return to the normal view, select View Actual Size or click the Zoom tool again.

Library Symbol

Tools Library Symbol

The Library Symbol tool function inserts the loaded symbol or bitmap. Refer to “Library Symbols” on page 8-14 for information on loading a library symbol or bitmap.

1. Select Tools Library Symbol or click the Graphic Insert tool to insert a previously loaded Library Symbol or bitmap graphic.

2. Position the pointer and click the left mouse button to insert the graphic in the page.

Entering Text

Tools Text

The Text tool function uses the current settings for text font and color. To define these settings, refer to “Font” on page 8-48 and “Text Color” on page 8-49.

1. Click the Text tool or select it from the menu.

2. Position the pointer and click the left mouse button. The pointer changes from an arrow ( ) to the text insertion symbol ( ). Drag the text box out to the desired size. Click in the text box and type the text.



Fill

Tools Fill

This tool fills selected objects with the current fill color and fill pattern.

1. Select Fill Solid.

To choose a fill color select Fill Color. Click on the color you prefer in the Color Palette and click OK. The current color selection displays on the Pen and Brush toolbar.

2. To choose a fill pattern, select Fill and click the desired pattern. For additional information on fill patterns refer to “Pen and Fill Tools” on page 8-45. The current pattern displays on the Pen and Brush toolbar.

3. Click the Fill tool or select it from the menu.

4. Click on the object you want to fill.

To set the window background, click on a blank area of the window.

Line

Tools Line

1. Click the Line tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn line reaches the desired length, release the mouse button. You may draw additional lines until you double-click or select another tool.

Square

Tools Square

1. Click the Square tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn square reaches the desired size, release the mouse button.



Rectangle

Tools Rectangle

1. Click the Rectangle tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn rectangle reaches the desired size, release the mouse button.

Rounded Rectangle

Tools Rounded Rect

1. Click the Rounded Rectangle tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn rectangle reaches the desired size, release the mouse button.

Circle

Tools Circle

1. Click the Circle tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn circle reaches the desired size, release the mouse button.

Ellipse

Tools Ellipse

1. Click the Ellipse tool or select it from the menu.

2. Click and hold the left mouse button while dragging the mouse. When the drawn ellipse reaches the desired size, release the mouse button.

Polygon

Tools Polygon

1. Click the Polygon tool or select it from the menu.

2. Click to insert the starting point and drag the mouse to draw the first side of the polygon.



3. Click to insert an anchor point. Drag the mouse to draw the second side of the polygon. Click to insert the next anchor point.

4. Repeat Step 3 to draw the remaining sides of the polygon.

5. To complete the polygon, double-click to insert the final anchor point.

Polylines

Tools Polyline

1. Click the Polyline tool or select it from the menu.

2. Click to insert the starting point. Drag the mouse to draw the first line segment.

3. Click to insert the second anchor point and drag the mouse to draw the third segment. click to insert the next anchor point.

4. Repeat Steps 3 to draw the remaining segments.

5. Double-click to insert the end point.

Curves

Tools Curves

This tool draws curved lines. You will need to set four points: the start point, two axis points, and the ending point.

1. Click the Curve tool or select it from the menu.

2. Click the left mouse button to set the starting point for the curve.

3. Reposition the pointer and click the left mouse button to set the first axis point for the curve. Repeat this step to set the second axis point.

4. Reposition the pointer and double-click the left mouse button to insert the curve and end the curve drawing sequence.

Note: By trial and error, you can gain experience in determining where to position the starting, axis, and ending points to create curves.



Chord

Tools Chord

A chord is a line segment connecting two points on a curved line.

1. Click the Chord tool or select it from the menu.

2. Click and drag the mouse to form a circle or ellipse. The point at which you release the mouse button will be the first anchor point.

3. Position the pointer and click to insert the second anchor point. You can reposition the anchor points, if necessary.

Pie

Tools Pie Slice

1. Click the Pie tool or select it from the menu.

2. Click and drag the mouse to form a circle or ellipse. The point at which you release the mouse button anchors the first segment of the pie shape.

3. Move the pointer around the circle and click to anchor the second line segment. You can reposition either segment, if necessary.

Arc

Tools Arc

1. Click the Arc tool or select it from the menu.

2. Click and drag the mouse to form a circle or ellipse. The point at which you release the mouse button anchors the first point on the arc.

3. Position the pointer where you want the ending point of the arc to be located and click to insert it. If necessary, you can reposition both of the anchor points.

Free Pen

Tools Free Pen

This tool allows you to draw freehand objects.



1. Click the Free Pen tool or select it from the menu.

2. Click to anchor the first point. The pointer changes to a pen icon. Press and hold the mouse button, drag the pointer to draw and release the mouse button to anchor the end point.

Arrange ToolbarIf the boundaries of one object overlap another object, one object is designated as “on top” of the other. This visual layering is called the z-order. (The term z-order refers to the z-axis found in three dimensional charts.)

The Arrange tools provide the ability to change the z-order or, in other words, the order in which objects are drawn on the screen.

You will find the Arrange tools on the Arrange toolbar or the Arrange menu.

Bring to Front

Arrange Bring to Front

This function moves the selected object to the top layer.

1. Select the object you wish to move.

2. Click the Bring to Front tool or select it from the menu, or press the Home key.

The object is placed on the top layer and remains selected.

Send to Back

Arrange Send to Back

This function moves the selected object to the bottom layer.


2. Click the Send to Back tool or select it from the menu, or press the End key.

Figure 8-22. The Arrange Tools toolbar



The object is placed on the bottom layer and remains selected.

Step Forward

Arrange Step Forward

This function moves the selected object up one layer.


2. Click the Step Forward tool or select it from the menu, or press the Page Up key.

The object is moved up to the next layer and remains selected.

Step Back

Arrange Step Back

This function moves the selected object down one layer.


2. Click the Step Backward tool or select it from the menu, or press the Page Down key.

The object is moved down one layer and remains selected.

Group

Arrange Group

This function places all the selected objects into one group, which may be treated as a single object.

1. Draw a selection box around the objects you wish to group.

2. Click the Group tool, or select it from the menu.

Each individual object’s selection handles disappear and selections handles for the group object appear. The objects will remain grouped until you ungroup them.

Note: For consistent results, perform all resizing, scaling, and flipping func-tions before grouping objects.

Ungroup

Arrange Ungroup

This function breaks up the objects in a group.



1. Select the grouped object.

2. Click the Ungroup tool, or select it from the menu.

The selection handles for each individual object appear.

Alignment ToolsAlignment tools enable you to precisely place objects on the page. The alignment functions are on the Arrange menu and the Align-ment toolbar is pictured in Figure 8-23. Alignment functions use the first item selected as a baseline.

Arrange Align To Grid

This function aligns the objects to the grid. To change the grid spacing, refer to “Window Backgrounds” on page 8-28.

1. Select the object(s) to be aligned. You can select all objects by choosing Edit Select All.

2. Click the Align to Grid tool or select it from the menu.

The Graphics Editor adjusts each object to be aligned with a grid line.

Arrange Align Left

This function aligns selected objects along the left boundary.

1. Select the objects to be aligned by drawing a selection box around them.

2. Click the Left Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align along the left.

Figure 8-23. Alignment toolbar



Arrange Align Center

This function aligns selected objects along the vertical center.


2. Click the Center Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align through the center.

Arrange Align Right

This function aligns selected objects along the right boundary.


2. Click the Right Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align along the right.

Arrange Align Top

This function aligns selected objects along the top boundary.


2. Click the Top Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align along the top.

Arrange Align Middle

This function aligns selected objects along the horizontal middle.


2. Click the Middle Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align along the middle.



Arrange Align Bottom

This function aligns selected objects along the bottom boundary.


2. Click the Bottom Align tool or select it from the menu.

The Graphics Editor will adjust each object so that they align along the bottom.

Coordinates ToolsThe Coordinates toolbar displays the X and Y coordinates of the mouse pointer. This information helps you align and size objects.

The following parameters are displayed:

✦ Coords

Shows the current position of the mouse pointer. The X and Y coordinates are updated as you move the pointer .

✦ Delta

This is coordinate is active when you draw an object. It displays the current position of the pointer in relation to the starting point of the object.

Pen and Fill ToolsThe functions of both the Pen menu and the Fill menu are combined on the Pen and Fill toolbar. The pen attributes affect the lines you use to draw objects, whereas the fill attributes affect the color and pattern inside the objects.

Once set, both the pen and the fill attributes remain valid until you change them again. Follow the steps below to change the settings.

To change any of the attributes for a specific object, select the object and then change the attribute.

Figure 8-24. Coordinates toolbar



The first box on the Pen and Fill toolbar graphically displays the current pen and fill settings.

Pen Color

Pen Color

This allows you to set the line color.

1. Click the Pen Color tool or select it from the menu. The Color palette displays.

2. Click on the desired color sample. A selector box displays around it.

3. Click OK. The line color should be displayed in the pen and fill settings box, located at the far left of the toolbar.

Pen Width

Pen Width

This allows you to set the line width, in pixels.

1. Click the Pen Width tool or select it from the menu. The Pen width dialog box displays.

2. Enter a number between 1 and 150 in the Pen Width field. Click OK. The line width is displayed in the pen and fill settings box.

Pen Styles

The Graphics Editor offers a variety of line styles.

Figure 8-25. Pen and Fill toolbar



Pen Solid

Dash

Dot

Dashdot

Dashdotdot

Invisible

1. Select the Pen Style tool by clicking on the appropriate toolbar or selecting it from the Pen menu. The default Pen style is now set.

Fill Color

Fill Color

This tool presents the Color palette so that you may choose the fill color.

1. Click the Fill Color tool or select it from the menu. The Color palette displays.

2. Click the desired color sample. A selection box displays around your choice.

3. Click OK. The default Fill color is now set.

Fill Options

Fill Solid

Fill Invisible

These options refer to the opacity of the fill. Solid displays the selected fill. If you select Invisible, the fill does not display. The default is Invisible.

Fill Fill option

The Graphics Editor offers a variety of fill options, ranging from various degrees of density, to several patterns. Figure 8-26 shows the available options.

To set a default fill pattern:



1. Select the Fill option by clicking the appropriate toolbar button or select it from the menu.

To fill only a selected object:

1. Select the object to be filled.

2. Select the Fill option.

Text ToolsThe Text tools control the current settings for text font and color. Before inserting text labels and identifiers in a system page using the Graphics Editor, you should first define the text font, point size, and color. All of the functions found on the Text toolbar, shown in Figure 8-27, are also available on the Text menu.

For information on inserting a textbox refer to “Entering Text” on page 8-36.

Font

Text Font

Sets the text font.

Figure 8-26. Fill options

Figure 8-27. Text Toolbar



1. Click the Font tool or select it from the menu. The Font dialog box displays, as shown in Figure 8-28.

2. Scroll through the font list to locate the font and click on the font name. A font sample appears in the Sample field.

3. Click on a font style and click on the desired point size.

4. Click OK to close the Font dialog box.

Text Color

Text Color

This tool displays the Color palette so that you can set the text color.

1. Select the Text Color tool. The Color palette displays.

2. Click the desired color sample. A selection box displays around your choice.

3. Click OK to close the box.

Back Color

Text Back Color

Figure 8-28. Font selection dialog box



This tool allows you to set the background color of the text. The example in Figure 8-29 shows a light gray text on a dark gray back-color.

Center Text

Text Center Text

Select the Center text tool to center text within the textbox.

Left Align Text

Text Left Align Text

Select the Left Align text tool to align the text to the left of the textbox.

Right Align Text

Text Right Align Text

Select the Right Align text tool to align the text to the right of the textbox.

Auto Word Wrap

Text Auto Word Wrap

Select the Word Wrap tool to automatically wrap the text within the text box.

Auto Fit

Text AutoFit

Select the Fit Label tool to automatically resize the textbox to the amount of text.

I/NET ToolsThe I/NET toolbar provides an easy and convenient way to provide access to I/NET items on system pages.

Figure 8-29. Text with a backcolor



You can add markers for points, doors, DDC modules and lines, as well as page markers, dial markers, and ASC markers.

Points Points are the link between your graphics and the physical world. Once you create a graphic image, you will usually associate one or more points with that image.

A point can be a hardware or a software point. A hardware point corresponds to an actual piece of equipment such as a temperature sensor or fire alarm contact. A software point is an internal or indi-rect point. It may correspond to a calculation, for example. Each point is referenced by a specific address which includes the link, station, point, and bit numbers as well as the point type.

To add points to a system page within the Graphics Editor, you must be connected to the controller containing the points you want to add. You can connect to up to four DCUs simultaneously, while adding points in a Graphics Editor session.

The Graphics Editor provides you with the option of inserting an icon to represent each point. You may use the icons included with TAC I/NET Seven or replace them with your own. Refer to “Replacing Icons” on page 8-76.

Connecting to Multiple Controllers

The Point Selection dialog (see Figure 8-31) provides four list boxes that you can use to select points. The first list box (in the upper-left corner) displays points from the currently connected controller (if any). The other three list boxes can display points from other controllers within your system.

Note: The Point Selection dialog provides a “Site” indication directly above a point list when you are connected to a controller through a distrib-uted link (see Figure 8-31 for an example). Refer to the System

Figure 8-30. I/NET Tools Toolbar



Configuration chapter in TCON300, TAC I/NET Seven Technical Reference Guide for more information about Distributed Link Archi-tecture (DLA) Support in TAC I/NET Seven.

To add controller connections, perform the following steps:

I/NET Points

1. Select the Point tool and click in the system page to display the Point Selection dialog box as shown in Figure 8-31. If you are already connected to a controller, the top left list box, displays the available points.

2. To connect to a second controller, activate one of the radio buttons (located at the top right corner of each pane) for the List 1, List 2, or List 3 windows.

3. Select the Station button to display the Connect dialog box (see Figure 8-32).

Figure 8-31. Sample Point Selection Screen

Note: Site Number indicates aconnection through a distributedlink.



4. Select a controller, and click OK to connect to the controller. The points associated with that controller now display in the selected pane.

5. Repeat Steps 1 and 2 to add up to two more connections, as needed.

6. Follow the instructions for inserting either discrete points or analog points. The procedure for inserting both digital points and analog points is basically the same. However, because digital points differ from analog points in their options, the instructions are presented separately.

Digital Points

The following procedure applies to discrete. Instructions for inserting analog points are located on page 8-57.

I/NET Points

1. Select the Point Tool and click on the page to insert the point. The Point Selection dialog box displays, as shown in Figure 8-31.

2. Position the selection highlight and select a discrete point.

3. To specify the point format, select the Option button to display the Drawing Styles dialog box similar to the example in Figure 8-33.

Figure 8-32. Selecting Multiple Controllers



4. Click a radio button in the Digital Point Style section to select a format. In Figure 8-33, we selected Icon plus value. The format is displayed in the Style Preview section.

5. If you select “Icon plus value” or “Value only”, choose a text Justification setting (Left, Middle, or Right). You can press Font Select to choose a font setting as well.

Note: Each point can have its own unique font settings. The font settings you choose for a point become the default settings for future points of the same type.

If you use the font Select button to set the point's font color, the color setting will be used only if the Use object pen option has been acti-vated () in the Graphics Properties dialog. Otherwise, the point's font color setting will be ignored and the graphic page's default text color will be used.

6. If you select “Graphic symbols”, refer to “Discrete Graphics” on page 8-55 for instructions.

7. Click OK. The Graphics Editor automatically inserts the icon for the type of point selected.

8. Click OK in the Point Selection dialog box to display the page with the point inserted.

Figure 8-33. Sample Digital Point Drawing Styles Dialog Box



Discrete Graphics

Discrete points exist in one of up to eight possible states. In many cases only two states are used: On or Off, High or Low, Open or Clsd, and so on. A fan is a discrete point that is either On or Off. A two position valve is another discrete point that is either Open or Clsd. An example of an eight-state discrete point would be a sensor in an Intrusion Alarm System (IAS) that uses resistor supervision to monitor multiple contacts. This discrete device may be capable of being in a NRdy, Norm, Tamp, TmpS, Falt, Alrm, Inhb, or Islt state.

As with a digital point, a discrete point can be represented on a graphic page as an icon, a value, or an icon plus value. You can also insert graphic objects to indicate discrete states. You can insert either bitmap (.bmp) or TAC I/NET Seven library symbol (.gls) files.

Suppose, for example, you need to know if a door is open or closed. You can insert a graphic of an open door to represent State 0 (open door), and second graphic of a closed door to represent State 1 (closed door).

I/NET Points

1. Click the Point tool, or select it from the menu, and click on the page to display the Point Selection screen.

2. Select a point and click the Option button to display the Drawing Styles dialog box.

3. In the Drawing Styles dialog box (sample shown in Figure 8-34), select Graphic Symbols.

Note: When Graphic Symbols is selected, the State 0 Select and State 1 Select buttons are enabled.

4. Use the Style Preview area to choose a graphic for each of up to eight discrete states. The first two states (i.e., the 0 and 1 state) of the point are shown in the preview area initially. You must define a graphic for at least these first two states. Using the slider bar, you can view all states with two states being shown at a time.



Click the Select button beneath a state to locate and select the necessary graphic. After you define a graphic for the state, the Select button changes to Delete on the last state defined (except for state 0 and 1 since these states are required). This allows you to delete a state’s graphic, beginning with the last state defined.

5. Activate or deactivate the Home Page option. Activating this option defines the current page as the home page for this point.

6. If the defined point goes into alarm, the number of this system page number appears on the Alarm Summary screen with the alarm message. You can define one home page for each point. The active home page for any point is always the last one entered by the operator.

Note: The Automatic Page Display feature is not currently implemented.

7. Activate or deactivate the Automatic Page Display option. This option causes the system page to automatically display if this point goes into alarm. System pages are displayed behind open editors and summary windows. Because system pages can be hidden by other windows, you may also wish to configure an audible alarm for the point.

Figure 8-34. Defining Graphic Symbols Digital Point Style



8. Click the State 0 Select button to display the Open dialog box.

9. Select the directory and filename of the graphics file (.bmp or .gls) and click Open.

10. Click the State 1 Select button and follow the same procedure to select the file for State 1.

11. Click OK from the Digital Point Drawing Styles screen and click OK on the Point Selection screen.

At any point in time, only the graphic image applicable to the current state is visible. In other words, if the point is in the 0 state, the image that represents that state displays. And, if the point is in the 1 state, then the image you selected to represent state 1 will display.

Analog Points

Analog points have continually changing values. A temperature sensor is an example of an analog point. Analog points can be represented on a system page as an icon, value, an icon and a value, or as a vertical or horizontal bar chart. Refer to Chapter 5, Point Definition and Addressing for additional information.

You can insert analog point icons and values by performing the following steps:

I/NET Points

1. Select the Point Tool and click on the page to insert the point. The Point Selection dialog box displays, as shown in Figure 8-31.

2. Select an analog point. Analog points are distinguished by having an AI or AO point identifier.

3. To specify the point format, select the Option button to display the Analog Point Drawing Styles dialog box.

4. Click a radio button in the Analog Point Style section to select a format. The format is displayed in the Style Preview section.



5. If you select “Icon plus value” or “Value only”, you can select a Font and choose a Text Justification setting (Left, Middle, or Right). In the Style Options section of the Analog Point Drawing Styles dialog box, enter the desired decimal display format.

Note: Each point can have its own unique font settings. The font settings you choose for a point become the default settings for future points of the same type.

If you use the font Select button to set the point's font color, the color setting will be used only if the Use object pen option has been acti-vated () in the Graphics Properties dialog. Otherwise, the point's font color setting will be ignored and the graphic page's default text color will be used.

6. If you select Horizontal or Vertical Bar, the graphic display will reflect the point’s changing value. You can specify the minimum (Bar min value) and maximum values (Bar max value) as well as the Bar length and Bar width, and colors.

7. You may also select Page Options as explained in the Discrete Points procedures. Click OK.

Figure 8-35. Analog Point Drawing Styles



8. Click OK in the Point Selection dialog box to display the page with the point

Door PointsThe Door tool allows you to add a door icon to your graphic page. When you display the page in live mode you can control the door, display its state (secure, unlock, lock), and access the door editor without having to leave the graphic page.

You can insert Door point icons and values by performing the following steps:

I/NET Doors

1. Click the Door tool, or select it from the menu, and click in the page to insert it. The Door Points dialog box, shown in the example in Figure 8-36, displays.

2. Select a Door point and then click the Option button to select the display format. The Drawing Styles dialog box is similar to the ones previously described for discrete and analog points.

3. You can also select the Extension button to add extensions, as described in “Adding Point Extensions” on page 8-60.

4. Click OK button(s) to close any opened dialog boxes and to insert the door point in the system page.

Figure 8-36. Door Points Dialog Box



Adding Point ExtensionsEach point type has certain extensions that can be associated with it. Attaching an extension icon to the point icon allows you to edit the point when the page is displayed or edited. Each extension icon accesses the appropriate point extension editor.

You can attach and display an extension to any point, but you must also add the extension to the point for it to be functional. To add the extension prior to entering the Graphics Editor, use the Edit Controller Point Extensions menu. Alternatively, you can add the extension from within the Graphics Editor as detailed in the procedure below.

Each type of extension is represented by a specific icon. You can add an extension icon to any point icon already on your system page by performing the following steps:

I/NET Points

1. Select the Point tool to display the Point Selection Dialog box.

2. Position the pointer and select a point.

3. Click Extension to display the Extensions dialog box.

Figure 8-37. Extensions Dialog Box



The extensions listed vary depending upon the type of point selected. Refer to “Extension Editors” on page 8-61 for a list of the editors available to each point type. The Extensions Dialog box shown in Figure 8-37 lists the extensions available for a DO point.

4. Activate the extension you want by clicking its Attach checkbox. If you also want the extension icon to display on the system page with the point, click the Display checkbox.

You must attach an extension before you select it to be displayed.

5. Click OK in the Extensions dialog box and then click OK in the Point Selection dialog box to display the system page.

6. If you have not also added the extension to the point, you may do so now. Select the point and click the right mouse button to display the context menu.

7. The extension you attached should be listed at the end. Select it and then click Yes in the confirmation dialog box.

8. The appropriate extension editor displays. Refer to the docu-mentation for each editor if you need additional information.

Extension Editors

Each of the editors referenced by an extension icon is also available on TAC I/NET Seven’s Edit Controller menu. A list of point types and their available extension editors is provided below:

DI (Discrete Input) Points:✦ Calc - Calculated Point editor

✦ Event - Event Definition editor

✦ Runtime - Runtime editor

✦ Trend - Trend Sampling editor

GI, AI (Analog Input), DA (Discrete Alarm), and DM (Discrete Monitor) Points:

✦ Calc - Calculated Point editor


✦ Alarm Inhibit - Alarm Inhibit editor




GO, AO (Analog Output) Points:✦ Calc - Calculated Point editor



✦ UC - Unitary Controller editor (7760 AO point only)

DC (Discrete Control) and DO (Discrete Output) Points:✦ Calc - Calculated Point editor


✦ Runtime - Runtime editor

✦ ATS - Time Scheduling editor

✦ ATC - Temperature Control editor


✦ UC - Unitary Controller editor (7760 DO points only)

✦ Override - Override Billing editor (7750 only)

✦ LC - Lighting Control editor (7780 only)

✦ Elev_Ctrl (7791/7793/7798 DO points at address LLSSPP08 and 09 only)

PI (Pulse Input) Points:✦ Calc - Calculated Point editor

✦ Consumption - Consumption editor

✦ Demand - Demand Control editor (all controllers except 7750 and 7770)


Adding DDC Modules Direct Digital Control (DDC) module icons allow you to go directly to a specific DDC module editor. For more information on DDC and MR-resident DDC modules, refer to Chapter 14, Direct Digital Control and Chapter 21, Micro Regulator Control. You can insert DDC module icons by performing the following steps:

I/NET DDC Modules



1. Click the Module tool, or select it from the menu, and click in the page to display the DDC Module Selection screen, as shown in Figure 8-38.

2. Enter the first two digits (i.e., the link portion) of the eight-digit DCU address into the Link field and the next two digits (i.e, the station portion) into the Station field. This associates the DCU address with the module.

3. DCU types 7792 MRI, 7793 MCI, and 7798 I/SITE LAN require the MR number. If the MR is on channel A of the MRI/MCI, the MR number is between 0 and 31. If it is on channel B of the MRI/MCI, the MR number is between 32 and 63. Enter the number in the MR Number field.

4. Choose a module number from the Module Number spindial.

5. Select a Controller from the drop-down list.

6. Choose a Module Type from the drop-down list. The module types available are dependent upon the Controller selection. The possible DDC modules are listed in the table below:

Figure 8-38. DDC Module Selection Screen

2_Pos Two-position module

PID Proportional/Integral/Derivative module

Float Floating module

Reset Reset module

HiLo HiLo module (all DCU types except the 7792 MRI, 7793 MCI, and 7798 I/SITE LAN)

Calc Calculation module (7792 MRI and 7793 MCI only)



7. If you selected “Relay” in step 6, choose a Relay Type from the drop-down list.

8. Click OK to insert the DDC module into the system page.

Note: If you have not already added the DDC module to the controller, you must do so before automatic control can be achieved. Access the DDC Editor from within the Graphics Editor by double-clicking on the DDC module icon. Alternatively, you can access the same editor from the TAC I/NET Seven menu (Edit Controller Direct Digital Control).

Adding DDC Lines Once you have added several DDC module icons to your system page you can link them with DDC line representations by performing the following steps:

I/NET DDC Lines

1. Click the DDC Line tool, or select it from the menu, to display the Line Options dialog box shown in Figure 8-39.

Relay

The following relay module types are available: Standard moduleDelay before make moduleDelay before break moduleInterval timer module

Figure 8-39. Sample DDC Line Options Dialog Box



2. For all DCU types except 7792 MRI, 7793 MCI, and 7798 I/SITE LAN, perform the following steps:

a. Enter the first two digits (i.e., the link portion) of the eight-digit DCU address into the Link field and the next two digits (i.e, the station portion) into the Station field.

b. Select a Controller from the drop-down list.

c. Enter the line number (between one and 64) in the Line field. Proceed to Step 4.

3. DCU types 7792 MRI, 7793 MCI, and 7798 I/SITE LAN only, perform the following steps:

a. Enter a four-digit number corresponding to the link (LL) and station (SS) of the MRI or MCI, by clicking on the Link and Station spindials.

b. Select a Controller from the drop-down list.

c. Enter the MR number in the MR Number field. The number is between 0 and 63, depending on whether the MR is on channel A of the MRI/MCI (0–31) or channel B of the MRI/MCI (32–63).

d. Enter the line number (between one and 32) in the Line field. (This is usually also the number of the module providing output to the line.)

4. Select an Icon Style (e.g., Value only, Icon only, or Icon plus value). The Style Preview section displays a sample of your choice.

5. If you elect to display a value (e.g., Value only or Icon plus value), enter a value in the Display Details section for the Integral and Fractional digits.

6. Click OK to accept the entries and insert the DDC Line icon on the system page.



Page MarkersThe Page marker allows you to jump to another system page by clicking on the page icon. Page markers use an absolute reference to the filename. If you move the file to another directory, the page marker will no longer be able to locate the referenced file.

Adding Page Markers

You will find the Page tool on the I/NET toolbar or you can use the TAC I/NET Seven menu.

I/NET Page Marker

1. Select the Page tool and click on the page to insert it. The Graphic Page Marker dialog box, shown in Figure 8-40, displays.

2. To include the icon with the Page marker label, click Icon and label. If you do not want the icon to display, click Label. The Style preview box illustrates the difference between the two choices.

3. Double-click in the Label edit field and type the name of the page marker. You could, for example, label the page marker, “Computer Lab,” to indicate that this icon jumps to the Computer Lab system page.

4. You may change the marker’s font, foreground color, and background color.

Figure 8-40. Graphic Page Marker dialog box



5. Click Destination page Select to select the system page that the icon will access. Select the desired file in the Open dialog box and click Open.

6. The File Details and Subject fields displays the name of the file you selected and a description, if one is available. Click OK to close the dialog box and insert the page marker.

Note: You may want to repeat this procedure to insert a page marker on the destination system page to establish a jump back to the origination system page.

Using Page Markers

To view a second system page from another system page using a page marker:

1. Select System Live Graphic Pages from the main TAC I/NET Seven menu as shown below in Figure 8-41. In the Open dialog box, select the page that contains the page marker. Click Open.

2. Double-click on the page marker to jump to the designated destination page.

3. The destination system page will be opened. If it is already open, it will be placed on top of your current window.

Figure 8-41. Viewing System Pages



Adding Multiple Site Dial The multiple site dial feature allows you to connect to more than one site at a time from the same page. You can place multiple dial icons on the page for multiple site dialing. Each graphic dial icon supports dialing to one site.

Adding a Graphic Dial Icon

Add Graphic Dial icons using the following steps:

I/NET Tools Dial Markers

1. Select the Dial Marker tool to display the Dial Marker dialog box shown in Figure 8-42.

2. Select a Display Option (Label Only or Icon and Label).

3. The dial icon Label contains the name of the Tap entered in the network configuration file. If you change the name of the Tap you must delete this icon and add it again to rename it.

4. Select Font to change the text font. Select Foreground to change the text color and select Background to change the background color.

5. Select a Site to be called when using this dial marker from the Site Details drop-down list.

6. Select OK to accept the entries and display the system page with the Dial Marker icon.

Figure 8-42. Dial Marker Editor



Dialing from a Graphic Page

Dial from a Dial Marker icon using the following steps:

1. Select System Live Graphic Page, or click the Graphic page tool on the system toolbar, and select a graphic page.

2. Double-click on the Graphic Dial Icon representing the link you want to establish. The Dial-Up Connection window appears.

3. Click the Dial push-button to start dialing. A dialog box appears showing the status of the dial attempt. When the dial connection is made, or you click on the Cancel push-button, the dialog goes away.

4. Close the Dial-Up Connection window by clicking on the Close push-button.

Note: If you had already established this connection and the opened the graphic dial icon, the Dial push-button would be replaced by a Hang-up push-button.

When one or more connections are made, the Host Dial icon (see Figure 8-43) displays over all existing windows and applications.

Double-clicking with the right mouse button on the Host Dial icon displays the Dial Connections Status window. You can view the current status of all connections or hang up a connection from your host through this window.

Disconnecting From a Dial Site

To end a dial connection through the Dial Connections Status window, use the following procedure.

1. Select a Site name from the drop-down list.

2. Select a connection source from the Site in use by list box.

Figure 8-43. Host Dial Icon



3. Click the Hang up push-button.

When all your host sources connecting to a site have been discon-nected, the site name will disappear from the Site drop-down list. If there are no site names displayed in the Site drop-down list, then the Host Dial icon will disappear when you leave the Dial Connec-tions Status window.

Caution: All dial connections are ended when you end the TAC I/NET Seven session.

Adding ASC MarkersASC markers allow you to go directly to the ASC Parameters editor for the specific ASC referenced by the marker. For more informa-tion on ASCs, refer to Chapter 22, Application Specific Controllers.

You can insert ASC markers by performing the following steps:

I/NET ASC Marker

1. Select the ASC Marker tool and click in the page to display the ASC Marker dialog box shown in Figure 8-44.

2. Select a Display Option (e.g. Label Only, Icon and Label).

3. Double-click the Label field and enter a name for the ASC marker.

Figure 8-44. ASC Marker Editor



4. Click Font Select to change the text font. Click Foreground color Select to set the text color. Click Background color Select to set the label background color.

5. Enter the MRI, MCI or I/SITE LAN’s Link number in the Link field and the station number in the Station field. You may click in these fields and type the number in or you can use the spindial arrows to select from the provided list.

6. Enter the ASC’s address in the ASC Number field. It must be between 0 and 31.

7. Choose an ASC Type from the drop-down list. The marker icon displayed depends on this setting. Figure 8-45 shows the possible icons.

8. Click OK to accept the entries and insert the ASC marker on the system page.

Adding Tool MarkersTool markers allow you to activate the user-defined tool referenced by the marker. For more information on user-defined tools, refer to “Creating User-defined Tools and Buttons” on page 1-25.

You can insert tool markers by performing the following steps:

I/NET Tool Marker

1. Select the Tool Marker tool and click in the page to display the Tool Marker dialog box (see Figure 8-46).

2. Select a Display Option (e.g. Label Only, Icon and Label, Graphic symbols).

3. Double-click the Label field and enter a name for the tool marker.

Figure 8-45. ASC Marker Icons



4. Click Font Select to change the text font. Click Foreground color Select to set the text color. Click Background color Select to set the label background color.

5. Click the Tool Name Select button to select a tool. The system displays the User Tool Configuration editor (see Figure 8-47).

6. Highlight the tool you wish to assign to the tool marker. If necessary, you can create a new tool (refer to “Configuring User Tools” on page 1-26 for instructions).

Figure 8-46. Tool Marker Editor

Figure 8-47. User Tool Configuration Editor


System Pages Live System Pages

7. Select OK to accept the highlighted tool and close the User Tool Configuration editor. The selected tool name is now displayed in the Tool Name field of the Tool Marker editor.

8. If you set the Display Options to “Graphic symbols” in step 2, click the Graphic symbol Select button to choose a graphic.

A dialog box opens, allowing you to browse your system. Highlight the graphic name and click Open to accept the selection. The dialog box closes and a thumbnail view of the selected graphic is displayed in the Tool Marker editor.

9. Select OK. The Tool Marker editor closes and the tool marker appears on the graphic page.

Adding CCTV MarkersAs part of TAC I/NET Seven’s integration with Pelco CCTV, you now have the ability to create CCTV markers on TAC I/NET Seven graphic pages. By clicking on a graphic page’s CCTV markers, a user can monitor live video.

This feature requires that you first integrate an Integral digital CCTV system with TAC I/NET Seven. For instructions on how to integrate and use digital CCTV within TAC I/NET Seven, including information about CCTV markers, refer to TCON301, TAC I/NET Seven Database Connectivity and Reporting.

Live System Pages

System pages can graphically display information about the oper-ating environment of a system, a portion of a system, an individual process, or a piece of equipment. In live mode, pages allow you to monitor the status of the system, as well as edit points and exten-sions.

Viewing Live System PagesThe Graphics Editor allowed you to create your system page, but the system page is not connected to your physical system. To view actual, “live” data, it is necessary to display your system page in TAC I/NET Seven.


Live System Pages System Pages

After you save your system page, close the Graphics Editor. To view a live system page, follow the procedure below.

System Live Graphics Pages

1. After you select the Graphic Pages command, the Open dialog box appears. Browse to locate the correct file.

Note: When you save a system page in the Graphics Editor, TAC I/NET Seven automatically gives the file a .gpg extension.

2. Select the file by double-clicking on it or place the selection highlight on it and click Open.

The system page you selected appears on the display. You can resize and position it anywhere on your display, just like any other window.

You may also simultaneously display additional system pages. Dynamic data fields (point values, line values, etc.) within each displayed system page are continually updated by TAC I/NET Seven at the scan rate specified in the Host Configuration editor.

Viewing another Page

Page markers (see “Adding Page Markers” on page 8-66) allow you to move quickly from one page to the next. While viewing a live system page, select the page marker icon to display a second system page.

If you did not include page markers, select System Live Graphics Pages and double-click on the filename, to display a second page.

Setting a Default System Page

You can specify a default system page to be automatically displayed in live mode, when the TAC I/NET Seven system is brought up. To define the default system page, perform the following steps:

1. Select Edit Host Computer Configuration from the Main menu to display the Host Configuration editor.



2. Enter the filename of your default page in the Default System Page text entry field. Alternatively, you can select File Open and select the correct file in the Open dialog box.

3. Click OK to close the Host Configuration Editor.

Icons and Editor AccessThe TAC I/NET Seven system uses icons to provide easier access to monitoring data and system changes.With the exception of Page marker icons, the primary function of the icons is to provide direct access to the editors that control a point.

The Graphic Dial icon allows you to connect to up to eight dial Taps simultaneously. You may connect or hang up connections from these icons. The ASC, Point, Point Extension, DDC Module, and Door icons allow you to call the pertinent editor. This capability allows you to view and modify editor parameters without closing the system page.

While displaying a live system page, you can access data for a specific point, and any editors associated with that point, by performing the following steps:

1. Select the point.

2. Click the right mouse button to display the context menu similar to the example in Figure 8-48.

Figure 8-48. Context Menu for a DO point



The contents of the menu will vary depending upon the type of object you selected. Generally, the context menu provides access to the editors or other functions that are applicable to that specific point type.

The example in Figure 8-48 shows the context menu for a DO point.

You can control the point inside the system page by double-clicking on it. This will bring up the Point Control dialog box. Refer to Chapter 5, Point Definition and Addressing for additional informa-tion on this function.

Replacing Icons

The default icons and markers used by TAC I/NET Seven graphic pages are stored in a dynamic-link library created during the instal-lation process. You may, however, create custom bitmap images to be in place of the default icons and markers. You must assign each custom bitmaps a specific name and place them in the DATA direc-tory. If it finds an image with the correct name, TAC I/NET Seven uses it in place of the default image.



Following are the default icons and markers. The filenames required for custom bitmap images are presented to the right of each icon.

Figure 8-49. TAC I/NET Seven Icons and Markers


C H A P T E R30

9

© 2001–2010 SchTCON299–05/10

Passwords

TAC I/NET Seven has two password editors, one for system-level security and one for controller-level security. Access the host pass-word editor through the host portion of the Edit menu. Use the host password editor to assign individual user passwords and specify which editors and tenants each operator can access. This editor also allows you preassign established controller passwords to operators, enabling them to auto-connect to individual controllers without the need to manually enter a controller password.

The Controller level of security is provided through the controller password editor, accessed through the controller section of the Edit menu. This editor allows you to assign access levels and passwords to individual controllers in the TAC I/NET Seven system. This added degree of security prevents unauthorized personnel from modifying your system. Operators must have the correct authori-zation level and enter the correct password before connecting to the controller.

While not required, the recommended order of operations for establishing passwords is as follows:

✦ Establish controller passwords, at the controller level, if needed.

✦ Enable the auto-connect function by setting the controller passwords at the host level.

✦ Set individual operator passwords and provide auto-connect access, if desired, to the controllers, at the host level.

Note: Whenever you add a new host to a 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 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.


Host Passwords Passwords

Host Passwords

Once you add a password for an operator, the operator can use the password to access any system host. The passwords are shared across TAC I/NET Seven on the commercial LAN. You can also delete, copy, or modify existing passwords. The copy feature saves you time at those sites where many operators are authorized at the same level for the same functions. You may also set operator pass-words for protected controllers. When you access the Host Computer Passwords function from the Edit menu, you may add, delete, modify, or copy the host level password information.

Adding a Host PasswordUse the following steps to add a new operator password and autho-rization assignment.

1. Select Edit Host Computer Passwords, or click the Pass-words tool on the Host toolbar. The system displays the Host Password editor (see Figure 9-1).

Figure 9-1. Host Password Editor


Passwords Host Passwords

2. Select Add. The system displays the Password Assignment screen (see Figure 9-2).

3. In the Name field, use up to 30 characters to define either of the following types of entries:

✧ TAC I/NET Seven operator name – At logon, this is the name that a user will enter in the Operator Name field of the Log On dialog. The user will also have to enter a valid Host Password in order to log onto TAC I/NET Seven.

✧ Windows user account name – By adding a user's Windows account to TAC I/NET Seven, the user can log onto TAC I/NET Seven without entering an operator name and password. Refer to “Using Your Windows Login with TAC I/NET Seven” on page 1-35 for more information.

Figure 9-2. Host Password Assignment Editor



The entry you make in the Name field must be unique. The following characters cannot be used within the name: " / [ ] : ; | = , + * ? < > . You must also avoid using the @ symbol if you intend to use this account as the source of indirect user settings (refer to “Indirect User Settings” on page 9-13 for more information).

4. If you defined a TAC I/NET Seven operator name (rather than a Windows user account) in the previous step, type the user’s password (up to 127 characters) in the Password field and in the Confirmation field. These fields must match before the system will accept your changes. The system displays an asterisk (*) for each character you type.

5. Type the operator Initials (up to four characters).

6. If necessary, enter an Alternate ID of up to 30 characters for this operator. This ID can be used for either of the following purposes:

✧ To appear in custom reports.

✧ To have this user inherit permissions and/or window settings from another user account. Refer to “Indirect User Settings” on page 9-13 for more information.

7. Activate () or deactivate () the Enable Password Re-use option. This option is deactivated by default. When you attempt to enter a new password, it will be checked against your password history and will be disallowed if it has been used before.

8. Activate () or deactivate () the Enable Password Expiry option. Activate this option to force the operator to change their password. When you activate this option, the following related parameters become available:

✧ Expiry Interval (days) – Specifies the number of days after the start date that the password will expire.

✧ Expiry Start Date – Specifies the start date.

For example, if you set the start date to January 1 and the interval to 15 days, then the operator can continue to use their current password until at least January 16. However, begin-



ning with their first logon after January 16, and repeating every 15 days thereafter, the user will be required to change their password.

9. If necessary, type the number of the Card/I-Disc issued to the operator. This feature allows an operator to log onto the TAC I/NET Seven system by swiping their card or I/DISC at a reader attached to the host workstation’s RS232 port. Refer to “Peripherals” in the TAC I/NET Seven Configuration chapter of TCON298, TAC I/NET Seven Getting Started, for more information.

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.

Functions are detailed in TCON300, TAC I/NET Seven Technical Reference Guide. Use the following procedure to assign functions and editors to a password.

1. Decide which functions you want this operator to access.

2. Mark functions by clicking on individual functions in the list or use All Yes and All No to speed the selection process. Only those functions/editors selected with “[X]” are enabled for the operator.

Station Selection

DCU password preassignment allows individual users to connect to specified controllers without entering a controller password. The Station editor allows you to choose which controllers the individual can access and the level of the access. This option is only available if you have saved the Link Summary under Network Configura-tion.

Refer to TCON300, TAC I/NET Seven Technical Reference Guide for a discussion of DCU password preassignment. Also refer to “DCU Password Preassignment” on page 9-11, for a description on setting up the controller passwords.

Preassign controller password levels using the following steps:



1. Select Station from the Host Passwords assignment editor. The system displays the Host Passwords - Station screen (see Figure 9-3). The actual screen is configuration-dependent.

2. Choose the communication link from the drop-down list. The editor will list the controllers through that link.

If the link is a link Tap or dial Tap, more than one controller LAN may be listed, indicating that this Tap can connect to multiple Taps. In this case, select the LAN to which you want to auto-connect. The link with all of its associated controllers appears on your screen.

3. Choose a controller from the list.

4. Use the Auto Connect Status portion of the screen to choose a password level for the selected controller(s).

5. Repeat these steps as necessary to assign the appropriate controller password levels to the Host password.

Figure 9-3. Host Passwords - Station Editor



6. Select OK to accept your changes and leave this editor.

Note: The controller passwords entered for the individual host password must match the passwords and associated level entered in the DCU password editor. Refer to “DCU Password Preassignment” on page 9-11.

Tenant Selection

Use this option to assign full or limited tenant access to the user of the host password. When assigning limited tenant access, you will be able to specify which of a tenant’s groups the user will be allowed to access (refer to “Limited-access Users” on page 9-15 for more information).

1. To assign tenant access, select Tenant from the Host Password assignment editor. The system displays the Tenant Selection screen (see Figure 9-4).

Figure 9-4. Tenant Selection Editor



2. By default, this editor lists only the tenants that have already been added to the system. If you wish to show all possible tenants, uncheck () the Only show defined tenants checkbox.

If you intend to limit which tenants (if any) the user will be allowed to add, uncheck the checkbox to show all possible tenants.

3. Select tenants by clicking on the checkbox in the Full or Limited column for any tenants in the list. The following guidelines apply:

✧ For tenants marked with in the Full column, the oper-ator will have unrestricted access.

✧ For any undefined tenants marked with in the Full column, the operator will have the ability to add the tenant to the system.

✧ For tenants marked with in the Limited column, the operator will have access that is restricted to specific groups (refer the next step and also to “Limited-access Users” on page 9-15 for more information).

✧ Tenants marked with in both columns will not be displayed for the operator when they use TAC I/NET Seven.

You can also use the All Full button to give the operator full access rights to all tenants, or the All No button to deselect all tenants.

4. When you click a checkbox in the Limited column, TAC I/NET Seven displays the Host Passwords - Group editor (see Figure 9-5). Using this editor, you can specify to which of the



selected tenant's groups the user will be allowed to gain limited-access.

a. Toggle the selection of groups by clicking on selection boxes for individual groups in the list. The following guidelines apply:

✢ The operator will have full access to parameters and TAC I/NET Seven features associated with any groups marked with in the Select column and in the Read Only column.

✢ The operator will have read-only access to parameters and TAC I/NET Seven features associated with any groups marked with in the Select column and in the Read Only column.

✢ The operator will have no access to parameters and TAC I/NET Seven features associated with any groups marked with in both the Select and Read Only columns.

Figure 9-5. Tenant Selection Editor



✢ You can use the All Yes button to select all groups or the All No button to deselect all groups.

b. When you have finished selecting the necessary groups, select OK to save your choices. The Host Passwords - Group editor will close.

5. When you have finished selecting the necessary tenants, select OK to save your choices. The Tenant Selection editor will close.

Individual Selection

This option allows you to specify which individual fields will be visible to the operator. This feature can be used to provide multiple levels of security in an access control environment by specifying each field that the operator will be able to view and edit. You must have at least one individual defined for this option to be available. Only the fields and buttons selected will be available to an operator using this password.

1. To assign individual access, select Individuals from the Host Password assignment editor. The system displays the Indi-vidual Field Selection screen (see Figure 9-6).

2. Choose one or more Tenants from the list, or use All Yes or All No to speed the selection process.

a. Select one or more of the individual editor fields for display. An operator using this password will not be able to view or edit any field not selected. The fields available for selection are:

✢ the 16 user-defined fields

✢ the individual’s card number

✢ the individual’s PIN

✢ beginning and ending dates and times for temporary records

b. If you wish the user to be able to view the doors assigned to this individual, select the Doors Button for display. If this item is not selected, an operator using this password will not be able to view or edit the doors assigned to the individual.



c. If you wish the user to be able to edit the individual records, select the OK Button for display. If this item is not selected, an operator using this password can view the selected fields, but cannot edit them.

DCU Password Preassignment

You may restrict controller access by assigning each controller a password. If you combine this with preassigned password levels, operators will not have to type the controller password each time they connect to the controller.

Note: Whenever you change a controller password, you must update the preassigned controller passwords. Otherwise, an “Invalid password” error message appears when you try to connect to a password-protected controller.

You can assign each controller up to four passwords, one password for each access level. The functions available to each operator depend upon the access level of the password they use to connect to

Figure 9-6. Individual Field Selection Editor



the controller. Refer to the controller functions chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Caution: Only Level 4 lets you add or modify passwords. At least one user must have a level 4 password.


2. Select DCU. This displays the DCU Password editor (see Figure 9-7).

3. Select the link that leads to the controller to which you want to preassign a password. The screen lists all the controllers on the link you selected.

4. Highlight the desired controller from the list.

Figure 9-7. DCU Password Editor



5. Enter a password for one or more password levels, as neces-sary. Use up to four characters for each password. This pass-word must match the passwords assigned at the controller level.

You can assign more than one password level to a controller for each host password. You can use the same password for each level if you want, but this is not necessary. If two pass-words are identical, but have different access levels, the higher access level is granted to the operator.

6. Repeat Steps 3 through 5 as necessary.

7. Select OK when you finish preassigning passwords levels. This returns you to the Host Password editor.

Indirect User SettingsWhen adding or modifying a user account in TAC I/NET Seven, you can configure the account to inherit settings from another user account. This requires that you type a properly formatted string in the Alternate ID field of the account that will inherit the user settings.

The following settings can be inherited from another user account:

✦ User permissions (refer to “Function Selection” on page 9-5 for more information)

✦ Window settings (refer to “Controlling Window Layouts in TAC I/NET Seven” on page 1-23 for more information)

Syntax

The string you type in the Alternate ID field to inherit indirect user settings is not case sensitive. Use the following syntax for the Alter-nate ID field string:

@U|Wusername{host}where:

@U = inherit user permissions from another user account.

@W = inherit window settings from another user account.

username = the name defined in the Name field of the user who's settings you wish to inherit.



host = use this variable to retrieve the host number assigned to the TAC I/NET Seven workstation that is being logged into.

Examples

In the following examples, users are configured to inherit indirect settings from user accounts with the following names:

✦ Guards – Defines typical user permissions for guards.

✦ GuardPC1 – Defines the window settings for the guard PC defined as TAC I/NET Seven host number 1.



Example 1: Assign user settings to a guard

Alternate ID:

@UGuards

Explanation:

The user will inherit the user permissions defined in the account named “Guards.”

Example 2: Assign window settings to a guard

Alternate ID:

@WGuardPC{host}

Explanation:

When the guard logs into a TAC I/NET Seven workstation, I/NET's windows will automatically position to the window settings defined for that workstation, as follows:

✧ At the guard PC defined as host number 1, the windows settings stored in the GuardPC1 account will be used.





Example 3: Assign user settings and window settings to a guard

Alternate ID:

@UGuards@WGuardPC{host}

Explanation:

When the guard logs into a TAC I/NET Seven workstation, he will inherit the user permissions defined in the account named “Guards.” TAC I/NET Seven's windows will automati-cally position to the window settings defined for that worksta-tion, as described in Example 2.

Limited-access UsersWhen adding or modifying a user in TAC I/NET Seven's Host Pass-words editor, you can use the tenant selection process (as described beginning on page 9-7) to limit the user’s access based on specific tenants and groups. When defining which of a tenant’s groups will be accessible to the user, you can choose no access, full access, or read-only access.

After logging into TAC I/NET Seven, the limited-access user will be unable to use some TAC I/NET Seven features associated with groups that have been limited by the user’s host password.

The restrictions placed on a limited-access user are described below.

Tenants

When a limited-access user selects Access Tenants from TAC I/NET Seven's main menu, the following restriction will apply:

✦ Cannot Add a new tenant.

✦ Cannot Delete, Modify, or Copy any tenants for which limited access has been assigned.

Individuals

When a limited-access user selects Access Individuals from TAC I/NET Seven's main menu, the following restrictions will apply:

✦ Can only see individuals associated with allowed groups.



✦ Cannot Add or Delete individuals. The limited-access user can only Modify existing individuals.

Individual Doors

When a limited-access user is modifying an individual and selects the Doors button, the following restrictions will apply:

✦ Can only see doors associated with allowed groups.

✦ Can assign the individual direct schedules to allowed doors.

Individual Groups

When a limited-access user is modifying an individual, selects the Doors button, and then selects the Groups button, the following restrictions will apply:

✦ Can only add and 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.


✦ 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 assign the group direct schedules to allowed doors.



✦ Can assign allowed groups to the group.

Example: A Medical Center with Three Access-controlled Labs

In a medical center their are three labs. Each lab has its own manager. The building manager for the medical center will give general lab access to lab personnel but will not specify which labs an individual can access. The lab managers must determine which individuals will be allowed to access specific labs. In this example, lab managers are given limited-access so that each manager can assign lab doors to individuals.

Although the limited-access managers will be prevented from modifying their assigned groups, they will have the ability to create new groups if necessary. When a limited-access user creates a new group, by default he automatically receives full-access to the group. All other limited-access users receive no access to the new group and will have no knowledge of its existance. The building manager will receive full-access to the new group because he is not a limited-

Figure 9-8. Lab Managers Assign Doors to Individuals

Lab Personnel

GROUPS:

Lab 1 Doors Lab 2 Doors Lab 3 Doors

BM(Building Manager)I/NET

OPERATORS:

Mgr1(Lab 1 Manager)

Mgr2(Lab 2 Manager)

Mgr3(Lab 3 Manager)

Full Access Limited Access(Read-only)

Limited Access(Read-only)

Limited Access(Read-only)

Lab 1 Lab 2 Lab 3



access user. If necessary, the building manager can give other limited-access users full access or read-only access to the new group.

TAC I/NET Seven Operators and Host Passwords

The host password accounts for TAC I/NET Seven operators in this example are described below. Any groups mentioned in the description of TAC I/NET Seven operators are explained in the next section.

✦ BM – The building manager.

This operator has full access to all tenants. The building manager will create and modify individuals in the access control system and will assign the “Lab Personnel” group to appropriate individuals.

The building manager will also manage TAC I/NET Seven host password accounts and will give each lab manager read-only access for specific groups as described below.

✦ Mgr1 – The manager of Lab 1.

The building manager will assign this operator read-only access for the “Lab Personnel”group and “Lab 1 Doors” group. This allows the operator to see the individuals and doors provided by these groups, but prevents the operator from modifying the groups.

The “Lab 2 Doors” and “Lab 3 Doors” groups will not be assigned to this operator. This prevents the operator from seeing doors that do not belong to Lab 1.









Besides being prevented from modifying the groups mentioned above, the limited-access lab managers will also be unable to remove the “Lab Personnel” group from individuals.

Groups

The building manager (BM) will create groups and assign opera-tors limited-access as described below:

✦ Lab Personnel – This group will have no door assignments. The purpose of this group is simply to allow lab managers to see a pool of individuals and to decide which of these individ-uals (if any) will be allowed to access a particular lab.

In the access control system, the building manager will assign this group to any individual that is authorized to access a lab.

The building manager will configure the host password account for each lab manager to provide read-only access to this group. This will allow each lab manager to see the indi-viduals that have been assigned the Lab Personnel group, but will prevent the managers from modifying this group or removing this group from an individual.

✦ Lab 1 Doors – This group will have door assignments appro-priate for lab 1. The purpose of this group is to allow the lab manager (Mgr1) to see this lab’s doors. Using doors from this group and individuals from the Lab Personnel group, the lab manager can assign doors to individuals.

The building manager will configure the lab manager’s host password for read-only access to this group. This allows the manager to see the group’s doors and to assign these doors to individuals, but prevents the lab manager from modifying the group.







To assign doors to the groups described above, the building manager will change the schedule for appropriate doors from “-- Unselect” to any other setting. Doors left in the “--Unselect” setting will not be visible to a lab manager.

Typically, the building manager will choose a schedule setting of “No Access” for each appropriate door. This allows the lab manager to see the doors but does not initially allow access at the doors in the event that this group gets assigned directly to an individual.

Note: The read-only group that defines a lab’s doors is not intended to be assigned directly to an individual. Instead, the lab manager is expected to assign doors to an individual. If necessary, the lab manager is free to create a new group that provides access to the lab’s doors. The lab manager can then assign this new group directly to an individual if so desired.



Implementing and Using this Example

This section describes the steps that must be performed in order to implement and use the example of a medical center with three access-controlled labs.

Prerequisites – Before continuing, ensure that the following prerequisites have been met:

✦ All necessary doors and personnel schedules have been defined in TAC I/NET Seven.

✦ The building manager has a TAC I/NET Seven host password acccount that provides full access to the tenant.

✦ The building manager has the necessary privileges for creating groups, individuals, and host passwords.

To create the groups:

The building manager creates the necessary groups (refer to “Groups” on page 17-55 for instructions on how to create groups).

1. To begin adding groups to the tenant:

a. The building manager selects Access Groups from TAC I/NET Seven’s main menu.

b. If there is more than one tenant, the building manager selects the Medical Center tenant from the Tenant Selec-tion – Group editor.

2. To create the “Lab Personnel” group:

a. In the Groups editor, the building manager selects Add.

b. In the resulting editor, the building manager types in a Group Name of Lab Personnel and selects OK.

c. In the resulting editor, the building manager selects OK.

3. To create the “Lab 1 Doors” group:

a. In the Groups editor, the building manager selects Add.

b. In the resulting editor, the building manager types in a Group Name of Lab 1 Doors and selects OK.

c. In the resulting editor, the building manager selects the Doors button.



d. In the resulting editor, the building manager selects a door appropriate for lab 1 and selects Schedules.

e. In the resulting editor, the building manager highlights the “No access” schedule and selects OK.

f. The building manager continues to add appropriate doors to the group by repeating the previous two steps as necessary.

g. Doors that building manager leaves with a schedule setting of “--Unselect” will be hidden from the the lab manager.

4. To create the “Lab 2 Doors” and “Lab 3 Doors” groups, the building manager respeats the steps used to create the “Lab 1 Doors” group. The building manager will select doors appro-priate for the group being created. Refer to Step 3 above.

Figure 9-9. Assigning a Door to the Group



To create the host passwords for limited-access operators:

The building manager creates a host password account for each lab manager. Refer to “Adding a Host Password” on page 9-2 for instructions on how to create host passwords.

1. The building manager creates a host password account for Mgr1 and gives this operator limited access to the tenant as follows:

a. From the host password editor, the building manager selects the Tenant button.

b. From the resulting Host Passwords – Tenant editor, the building manager deactivates () the Full checkbox for all unecessary tenants and activates () the Limited checkbox for the Medical Center tenant.

c. From the resulting Host Passwords – Groups editor, the building manager deactivates () Select checkboxes to hide disallowed groups and activates () Read-only access for the “Lab 1 Doors” and “Lab Personnel” groups.

Figure 9-10. Giving an Operator Limited-access to a Tenant

Figure 9-11. Giving an Operator Read-only Access to a Group




a. From the host password editor, the building manager selects Tenant and gives the operator limited access to the Medical Center tenant as described in Step 1b.

b. From the Host Passwords – Groups editor, the building manager deactivates () Select checkboxes to hide disal-lowed groups and activates () Read-only access for the “Lab 2 Doors” and “Lab Personnel” groups.


a. From the host password editor, the building manager selects Tenant and gives the operator limited access to the Medical Center tenant as described in Step 1b.

b. From the Host Passwords – Groups editor, the building manager deactivates () Select checkboxes to hide disal-lowed groups and activates () Read-only access for the “Lab 3 Doors” and “Lab Personnel” groups.





To assign the Lab Personnel group to an individual:

The building manager assigns the Lab Personnel group to all indi-viduals that will require access to a lab. Refer to “Adding an Indi-vidual” starting on page 17-65 for instructions on how to add an individual to the access control system and how to assign groups to the individual.

1. The building manager adds or modifies an individual and selects the Doors button.

2. From the resulting Individuals – Door Selection editor, the building manager selects the Groups button.

3. From the resulting Individuals – Group Selection editor, the building manager adds the Lab Personnel group to the indi-vidual.

Once this individual’s record is saved, the individual will become visible to all lab managers.

To assign lab doors to an individual:

Each lab manager can assign his own lab doors to any individual that has been assigned the Lab Personnel group. Refer to “Adding an Individual” starting on page 17-65 for instructions on how to add an individual to the access control system and how to assign doors to the individual.

1. The lab manager (Mgr1, Mgr2, or Mgr3) modifies an indi-vidual and selects the Doors button.

2. In the resulting Individuals – Door Selection editor, the lab manager highlights a door and selects the Schedules button.

3. In the resulting Individuals – Door Schedules editor, the lab manager highlights the desired schedule and selects OK.

Figure 9-14. Giving an Individual the Lab Personnel Group



4. The lab manager can continue adding other lab doors to the individuals as necessary.

Once this individual’s record is saved, the individual will have access to the corresponding lab.

Printing a Host Password ReportThe Print function in the Host Password editor allows you to print a report listing the password authorizations assigned to selected operators. In order to print the password report, you must sign on with a password that has host password privileges enabled.

Use the following steps to generate a password report.

1. Select Edit Host Computer Passwords, or click the Pass-words tool on the Host toolbar. The system displays the Host Password editor (see Figure 9-1 on page 9-2).

2. Select the operator(s) to include on the report by enabling the Print checkbox. You must select at least one operator to enable the print function.

3. Click the Print button to display the Windows print dialog for your printer.

4. Complete the print dialog box as you normally would and select the Print button. The report will list the password authorizations for the selected operator(s).

Searching for a Host Operator PasswordSearching for an operator allows you to find an operator and delete, modify, or copy the operator and password. Use the following steps.


2. Type the name you want to search for, or a portion of the name, in the Search name field.



Note: The search is conducted on the first string in the name. For example, typing “con” will find Control Systems International, but “int” will not.

3. Select Find. The system scrolls to the first match and high-lights it.

Note: Selecting Find a second time will not find another match. You must reenter a search string and select Find again.

4. You may now delete, modify, or copy using this operator.

Deleting a Host PasswordDeleting a password deletes an existing operator from the password list. Use the following steps.

Caution: Be careful not to delete all passwords that have access to the host’s password editor.

1. Choose an individual from the list of current operators.

2. Select Delete. The system prompts you for confirmation.

3. Select Yes to delete the operator or No to cancel the Delete operation.

Modifying a Host PasswordModifying a password allows you to change an operator's password level, access authorizations, preassignment password levels, and passwords. Use the following steps.

1. From the Host Password editor, select the operator name whose password authorization you wish to modify.

2. Select Modify. The system displays the Password Assignment screen (see Figure 9-2).

3. At this point, procedures for modifying the host password are the same as those described for adding a new host password. Refer to “Adding a Host Password” on page 9-2 for these procedures.



4. When you have finished modifying the host password, select OK to save the changes.

Copying a Host PasswordCopying a password allows you to create a new operator password using the password level and authorization of an existing operator record.

1. From the operators/passwords listed, select the operator name whose password authorization you wish to copy.

2. Select Copy. The system displays the Password Assignment screen (see Figure 9-2).

3. At this point, procedures for modifying the copied host pass-word are the same as those described for adding a new host password. Refer to “Adding a Host Password” on page 9-2 for these procedures.

4. Select OK to save the changes.

Printing a Host Passwords ReportThe host passwords report lists the privileges assigned to each oper-ator. In order to print the password report, you must sign on with a password that has host password privileges enabled.

Use the following steps to generate a password report.


2. Select the operator(s) to include on the report by enabling the Print checkbox. You must select at least one operator to enable the print function.

3. Click the Print button. The windows standard print dialog box appears.

4. Complete the print dialog box as you normally would and select the Print button. The report will list the password authorizations for the selected operator(s).


Passwords Assigning Controller Passwords

Assigning Controller Passwords

Do not confuse the controller password editor with the host pass-word editor. The controller password editor is distinct and repre-sents an additional level of security for the indicated controller. A controller password may not be necessary in systems run by only one principle operator.

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 controller’s remote LCD panel.

DCU Password Editor1. Select Edit Controller Passwords, or click the Passwords

tool on the Controller toolbar. The system displays the DCU Password dialog box (see Figure 9-15).

2. Type a password for each level that you wish to have pass-word-protected. Each password must be unique.

Caution: Only Level 4 lets you add or modify passwords. At least one user must have a level 4 password.

3. Select OK to save the changes.

Figure 9-15. DCU Passwords dialog box


Assigning Controller Passwords Passwords

DCU Password Recover

Caution: If you forget the DCU password you must have a DCU save file for the affected DCU. If you do, use the following procedure.

1. Erase the existing database in the DCU by changing its address with an HC7410, or ViewCon, and then reentering the original address.

2. Reconnect to the DCU using TAC I/NET Seven.

Note: Since there is no database, the DCU will allow a non-password protected connection.

3. Perform a Station Restore to the DCU using its save file.

4. Inspect the DCU Password editor to find the DCU’s pass-word.


C H A P T E R38

10

© 2001–2010 SchTCON299–05/10

Dynamic Control

TAC I/NET Seven provides three types of dynamic control:

✦ Time Scheduling (TS) – The TS extension is used to define and assign one or more time schedules to specific DO and DC output point(s).

✦ Temperature Control (TC) – The TC extension is used to define and assign temperature control programs to specific DO and DC output point(s).

✦ Demand Control (DC) – The DC extension is used to define and assign demand control programs to specific PI points which control specific DO and DC output point(s) according to demand levels.

Time Scheduling (TS)

Use this editor to create a schedule for any of the DC and DO points currently residing in a controller for any day of the week. Only DO and DC points are listed since they are the only point types to which you can add a Time Scheduling extension. You may assign more than one daily schedule to the same output point. For example, you might have one schedule running Monday through Friday and a different schedule in place for the weekends. You may also create up to seven Special Day schedules (a holiday is the most obvious example of a Special Day) and two Temporary schedules.

Refer to the section on Time Scheduling in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.w

Adding a Point Time Schedule

Note: You must be connected to the controller containing the points you want to control.


Time Scheduling (TS) Dynamic Control

1. Select Edit Controller Point Extensions Time Sched-uling, or click the Time Scheduling tool on the Extensions toolbar. The Resident I/O Points editor displays with the Time Scheduling (TS) option selected (see Figure 10-1).

This editor lists all of the DC and DO points currently residing in this controller. If there are more points than the screen can hold, you can scroll through the list using the scroll bar that appears to the right of the list.

Note: In the following step, if you choose a point that already has a time schedule, then the Add button is not enabled and a time schedule cannot be added. In this case you may either modify, copy, or delete the time schedule.

2. Highlight a point and select the Add button to append the Time Scheduling extension to the point. The system displays the Time Schedule - Add dialog box (see Figure 10-2).

Figure 10-1. Resident I/O Points - Time Scheduling Editor


Dynamic Control Time Scheduling (TS)

3. You must now choose the type of schedule to add. Use the appropriate procedures below to add Independent, Master, or Slave schedules.

Adding an Independent or a Master Schedule1. From the Time Schedule - Add dialog box, select Indepen-

dent or Master.

2. Select the OK button. The system displays an empty Time Schedule editor (see Figure 10-3).

3. Select the Add button. The system displays the Time Schedule Action editor (see Figure 10-4).

Figure 10-2. Time Schedule - Add

Figure 10-3. Time Schedule Editor



4. Choose an Action from the drop-down list. The drop-down list displays six actions for Independent points (Start, Stop, Cycle, Opt. Start, Opt. Stop and Opt. Cycle) and three actions for Master points (Start, Stop and Cycle). (None is not a valid option.)

5. Choose a Type from the drop-down list. The drop-down list displays Time, Sunrise, and Sunset.

Note: Sunrise and sunset are calculated by the system, so it is not necessary to enter a time when you select either of these types.

6. Enter a time using 24 hour format in the Time field.

Note: In the following step, Cycle On and Cycle Off fields are only active if you selected Cycle or Opt. Cycle in the Action Field.

7. Enter a number in the Cycle On and Cycle Off fields. These fields represent the minutes (0–127) the device controlled by this point is on and off per cycle period. The OFF command is always issued at the beginning of a cycle.

Figure 10-4. Time Schedule Action Editor



8. Select the days you want this action to run. A check mark next to the day indicates that the action is activated for that day. Each day can be toggled between activated () and deacti-vated ().

9. Select the OK button. The system displays the Time Schedule editor (see Figure 10-3) showing any schedules you have entered for this point.

10. Repeat Steps 2 through 9 as required for additional indepen-dent and master time schedule actions.

11. From the Time Schedule editor, select OK to save the settings and exit this procedure.

Adding a Slave Schedule

Note: To select Slave, you must have previously defined at least one Master schedule. The Slave and Master schedules must reside in the same controller.

1. From the Time Schedule - Add dialog box (see Figure 10-2), select Slave.

2. In the Master Point field, choose a master point from the drop-down list.

3. Click OK. The system displays the Time Schedule - Slave editor (see Figure 10-5).

This editor lists all actions defined in the Master schedule. By default, the Reaction defined in the Slave schedule is initially set to Mirror.

4. Choose an action from the list and select Modify. The Time Schedule Action editor displays. (see Figure 10-6).

5. Choose a Reaction from the drop-down list.

6. Set an Adjustment for the reaction.

7. Select the OK button. The system displays the Time Schedule - Slave editor again (see Figure 10-5).

8. Repeat steps 4 through 7 as necessary to configure each action.



9. Repeat Steps 1 through 8 as required to add additional slave time schedules.

Figure 10-5. Time Schedule - Slave Editor

Figure 10-6. Slave Schedule Action Editor



Note: If you have established any temporary actions, you can select the days you want them to run. Do not designate a day as temporary or special , if the special or temporary action is not already established. If you do, no actions will occur on that day.

10. From the Time Schedule editor, select OK to save the settings and exit this procedure.

Modifying a Point Time ScheduleModifying a time schedule point extension is similar to adding a time schedule point extension. Use the same procedure as described in “Adding a Point Time Schedule” on page 10-1 except you choose a point that already has a time schedule point extension and select Modify (rather than Add) from the Resident I/O Points editor.

Copying a Point Time ScheduleOnce you have added a time schedule, you can copy the time schedule to other points.

1. Select Edit Controller Point Extensions Time Sched-uling, or click the Time Scheduling tool on the Extensions toolbar. The Resident I/O Points editor displays with the Time Schedule (TS) option selected (see Figure 10-1).

2. Select the point whose time schedule you want to copy. This point is now designated as the Source.

3. Select Copy. The system displays the Copy (Time Scheduling) dialog box (see Figure 10-7).

Figure 10-7. Copy (Time Scheduling) Dialog Box


Host ATS (Automatic Time Schedule) Dynamic Control

4. In the Target field, choose a point from the drop-down list. The list includes all eligible DO and DC points on the controller that do not have time schedules.

5. Select OK. The system displays the Time Schedule editor (see Figure 10-3) for the selected point.

6. Change the time schedule as required.

7. Select OK.

8. Repeat Steps 2 through 7 as required for any additional time schedules that you want to copy.

9. Click Close to save the settings and exit this procedure.

Deleting a Point Time ScheduleOnce you have added a time schedule, you can delete it.

1. Select Edit Controller Point Extensions Time Sched-uling, or click the Time Scheduling tool on the Extensions toolbar. The Resident I/O Points editor displays with the time schedule (TS) option selected (see Figure 10-1).

2. Choose the point whose time schedule you want to delete.

3. Click Delete. The system displays the Delete confirmation dialog box.

4. Click Yes. The system deletes the time schedule and returns the Resident I/O Points editor (see Figure 10-1 on page 10-2).

5. Repeat Steps 2 through 4 as required for any additional time schedules that you want to delete.

6. Click Close to exit this procedure.

Host ATS (Automatic Time Schedule)

The Host ATS function allows you to define schedules at the host level and distribute this information to controllers containing master time schedule points. This way you don’t need to access each controller separately. Instead, you can create a master schedule that is edited from the workstation and affects points with


Dynamic Control Host ATS (Automatic Time Schedule)

master schedules (along with their associated slave schedules) in multiple controllers. You cannot download a host time schedule to an independent time schedule.

Adding a Host Time Schedule1. Select Edit Host Computer Host ATS, or click the Host

ATS tool on the Host toolbar. The system displays the Host ATS Schedules editor with a list of all host schedules, as shown in Figure 10-8.

2. Select Add. The system displays the Host ATS summary (see Figure 10-9).

Figure 10-8. Host ATS Summary

Figure 10-9. Host ATS Editor



3. Enter the schedule Name (up to 16 characters).

4. Click the Active checkbox to activate () or deactivate () the schedule.

5. Change the Date and Time as required. Enter the time in 24-hour (military) format.

6. Select OK. The Time Schedule editor displays (see Figure 10-3 on page 10-3).

7. Select Add. The system displays the Time Schedule Action editor (see Figure 10-4 on page 10-4).

Note: Keep in mind that you are defining a Master time schedule and the only actions available are Start, Stop and Cycle. No optimization is possible.

8. Choose an Action from the drop-down list. The drop-down list displays three actions (Start, Stop and Cycle). (None is not a valid option.)

9. Choose a Type from the drop-down list. The drop-down list displays Time, Sunrise, and Sunset.

Note: Sunrise and sunset are calculated by the system, so it is not necessary to enter a time when you select either of these types.

10. Enter a time using 24-hour format in the Time field.

Note: The Cycle On and Cycle Off fields are only active if you selected Cycle in the Action Field.

11. Enter a number in the Cycle On and Cycle Off fields. These fields represent the minutes (0–127) the device controlled by this point is ON and Off per cycle period. The OFF command is always issued at the beginning of a cycle.

12. Activate () or deactivate () the days you want this action to run. You can choose as many of the days as needed.

13. Select OK. The system displays the Time Schedule editor (see Figure 10-3) showing all schedule actions for this host.



14. Select OK. The system displays the Point List (see Figure 10-10). This editor displays the master time schedule

points that are controlled by the Host ATS schedule.

15. Select Add. The system displays the Host ATS Editor - New Point dialog box (see Figure 10-11). The list box displays the

address, station name and point name of all points assigned.

16. Enter the point address for a DO or DC point in the New point field and click OK.

The address must include the 8-digit address and the 2-char-acter point type and must have a Master ATS schedule defined.

17. Click OK to add the point to the Point List.

Figure 10-10. Point List Editor

Figure 10-11. Host ATS - New Point Dialog Box



18. To add more points, repeat Steps 15 through 17 as required.

19. Click Close to save the settings and return to the Host ATS Schedules editor (see Figure 10-9 on page 10-9).

20. Repeat Steps 2 through 19 as required for additional host time schedules.


Modifying a Host Time ScheduleModifying a host time schedule is similar to adding a host time schedule. Use the same procedure as “Adding a Host Time Schedule” on page 10-9 except that you choose a time schedule that already exists from the Host ATS Schedules editor (see Figure 10-9) and select Modify rather than Add.

Note: When modifying an existing Host ATS Schedule, pay special atten-tion to the date and time values. If you modify an existing schedule, the default values for the date and time fields are the current date and time, even if you previously defined a different date and time.

Copying a Host Time ScheduleOnce you have added a host time schedule, you can copy the host time schedule to other Host ATS schedules.

1. Select Edit Host Computer Host ATS, or click the Host ATS tool on the Host toolbar. The Host ATS editor (see Figure 10-9) displays.

2. Choose the time schedule you want to copy and click Copy. The Host ATS - Copy dialog box (see Figure 10-12) displays.

Figure 10-12. Host ATS - Copy Dialog Box



3. Enter a New schedule name (up to 16 characters) and click OK. The Host ATS editor (see Figure 10-9) displays.

4. Select OK. The system saves the settings and displays the Time Schedule editor (see Figure 10-3) with the added schedule.

Note: If you want to change the schedule, perform Steps 5 and 6.

5. Select Modify. The system displays the Time Schedule Action editor (see Figure 10-4).

6. Change the time schedule as required. Click OK to save the settings and return to the Time Schedule editor.

7. When you are finished, click OK to return to the Point List editor (see Figure 10-10).

Note: If you want to add points to the copied time schedule, perform Steps 8 through 10.

8. Select Add.

9. Enter the new point.

10. Click OK to add the point and return to the Point List editor (see Figure 10-10).

11. Repeat Steps 8 through 10 as required to add more points.

12. Click Close to return to the Host ATS Schedules editor.

13. Repeat Steps 2 through 12 as required for any additional host time schedules that you want to copy.

14. Click Close to exit this procedure.

Deleting a Host Time Schedule1. Select Edit Host Computer Host ATS, or click the Host

ATS tool on the Host toolbar. The Host ATS Schedules editor displays.

2. Choose the time schedule you want to delete and select Delete. The system displays the Delete confirmation dialog box.


Special Days Dynamic Control

3. Click Yes to delete the host time schedule and return to the Host ATS Schedules editor (see Figure 10-9 on page 10-9).

4. Repeat Steps 2 and 3 as required for any additional host time schedules that you want to delete. Select Close when you are finished.

Special Days

This editor is used to define the time period(s) during which the special day schedule (entered in the time schedule editor) will replace the normal schedule. This editor is not point-specific (it is not a point extension) and affects all time scheduled control points in the same DCU.

Refer to the section on Special Days in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding Special Days

Note: If you have a special day defined, there must be a special day schedule defined for all points in the DCU or the points will remain at their last commanded states until the special day period is over.

1. Select Edit Controller Special Days, or click the Special Days tool on the Controller toolbar. The Special Day Assign-ments editor displays (see Figure 10-13).

You can also access the Special Day Assignments editor by selecting the Spec Days button in the Personnel Schedules Summary. Refer to “Adding a Personnel Schedule” on page 17-32 for more information.

2. Select Add. The Special Day dialog box displays (see Figure 10-14).

3. In the Date field, enter the month and day of the start date.

4. Using the spindial in the Duration field, select the number of days (0–127) that you want this special day to be in effect. Special days with a duration of 0, are discarded by the system when you exit the editor.


Dynamic Control Special Days

Caution: When the date assigned to the special day occurs, the special day schedule (S1–S7) replaces all regular schedules in the DCU. In an ATS schedule, if the S1–S7 column is left with all “–”, no commands occur on that day.

5. For S1 through S7, use the spindial to choose “–” (not used), “T” (temporary) or “P” (permanent).

Note: If you select OK in the following step, all special days with a value of 0 in the Days column will be deleted.

Figure 10-13. Special Day Assignments Editor

Figure 10-14. Special Day Dialog Box


Temperature Control (TC) Dynamic Control

6. Click OK to return to the Special Day Assignments editor (see Figure 10-13).

Note: When you select OK in the next step, all special days with a value of 0 in the Days column will be deleted.

7. Select OK to save the settings and exit this procedure.

Modifying Special DaysModifying a special day schedule is similar to the “Adding Special Days” procedure on page 10-14 except that you choose a special day that already exists from the Special Day Assignments editor (see Figure 10-13) and select Modify rather than Add.

Deleting Special DaysOnce you have added a special day, you can delete it. Choose a special day that already exists from the Special Day Assignments editor (see Figure 10-13)and select Delete.

Temperature Control (TC)

This point extension is available only for DO and DC points. It is available on all controllers. Temperature Control allows you to:

✦ Mimic the traditional “red wire control” of packaged rooftop HVAC units

✦ Provide optimized start, optimized stop, night setback/setup control, and demand temperature override control informa-tion for output points controlling HVAC units.

Refer to the section on Temperature Control in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about temperature control and a description of the Temperature Control parameters.

Adding a Temperature Control Point Extension1. Connect to the controller containing the points you want to

control.


Dynamic Control Temperature Control (TC)

2. Select Edit Controller Point Extensions Temperature Control, or click the Temperature Control tool on the Exten-sions toolbar. The Resident I/O Points editor displays with the temperature control (TC) option selected (see Figure 10-15).

This editor lists all the points currently residing in this controller that will accept temperature control (DO and DC points). Each point is listed by address, class, and name. A Y in the TC column indicates that temperature control has been added to the point.

Note: If you choose a point that already has a temperature control exten-sion, then the Add button is not enabled and temperature control cannot be added. In this case you may either modify, copy, or delete the temperature control.

3. Choose a point that does not have a Y in the TC column and select Add. The system displays the Temperature Control editor (see Figure 10-16).

Figure 10-15. Resident I/O Points - Temperature Control



Select a point name or address for the outside air sensor from the drop-down list in the Outside air temperature field. The Outside Air Temperature entry is mandatory if optimized start/stop is used, otherwise its use is optional.

1. Select a point name or address for the space sensor from the drop-down list in the Space temperature field. This entry is mandatory.

Note: The two lookahead entry fields are used for adaptive optimized start/stop (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.

2. In the Optimized start lookahead field, enter a number from 0 to 480. This is the maximum number of minutes that OSTART can optimize. A zero entry means that Ostart does not take place.

3. In the Optimized Stop lookahead field, enter a number from 0 to 480. This is the maximum number of minutes that OSTOP can optimize. A zero entry means that Ostop does not take place.

Figure 10-16. Temperature Control Editor



4. Activate () or deactivate () Demand Temperature Over-ride. This function gives you the opportunity to allow Temperature Control to override demand control you have in effect for this point when the space temperature is outside its control band.

5. Use the Target (deg) fields to define the target temperatures for the HVAC unit controlled by this point. Each field is described below:

Caution: The heating setpoint may never be greater than the cooling setpoint. There must be a deadband area of no control between the heating and cooling zone ranges, so that the controller is aware of the transi-tion from heating to cooling or vice versa. The zone ranges are defined as the target, plus or minus one-half of the differential. This applies to both heating and cooling zone ranges. This deadband between the zone ranges must be at least 0.5 degrees.

✧ Cooling - This is the cooling temperature the unit attempts to reach and maintain when the Time Sched-uling program issues a START command to the output point. This is also the target temperature at occupancy time used by the Optimized Start command (in the ATS editor).

✧ Setup - This is the high limit setpoint for this system when the space is unoccupied. This Setup cooling temperature setpoint is only relevant when the output point has been issued a STOP command by the Time Scheduling program.

✧ Heating - This is the heating temperature the unit attempts to reach and maintain when the Time Sched-uling program issues a START command to the output point. This is also the target temperature at occupancy time used by the Optimized Start command (in the ATS editor).

✧ Setback - This is the low limit setpoint for this system when the space is unoccupied. This Setback heating temperature setpoint is only relevant when the output point has been issued a STOP command by the Time Scheduling program.



6. Use the Differential (deg) fields to define the degree of preci-sion you feel is necessary for temperature control. The target temperature plus one-half of the differential is the maximum temperature and the target temperature minus one-half of the differential is the minimum temperature.

✧ Cooling - This is the temperature range over which normal cooling will be controlled.

✧ Setup -This is the temperature range over which Setup cooling will be controlled.

✧ Heating - This is the temperature range over which normal heating will be controlled.

✧ Setback - This is the temperature range over which Setback heating will be controlled.

7. Use the Cycle Adjustment (min/deg) fields to define the minutes per degree adjustment to be made to the Optimum Duty Cycle period (Ocycle) for the HVAC unit controlled by this point.

✧ Cooling - This is the number of additional minutes per degree the space temperature is above the cooling setpoint that the unit will be turned on during each Ocycle period (defined in the ATS editor).

✧ Heating - This is the number of additional minutes per degree the space temperature is below the heating setpoint that the unit will be turned on during each Ocycle period (defined in the ATS editor).

8. Select OK. The system displays the Resident I/O Points editor with the temperature control (TC) option selected (see Figure 10-15). A Y now appears in the TC column of the chosen point.

Modifying a Temperature Control Point ExtensionModifying a temperature control point extension is similar to adding a temperature control point extension. Use the same proce-dure as described in “Adding a Temperature Control Point Exten-sion” on page 10-16 except that you choose a point that has a Y in



the TC column and select Modify (rather than Add) from the Resi-dent I/O Points editor with the temperature control (TC) option selected.

Copying a Temperature Control Point ExtensionOnce you have added a temperature control point extension, you can copy the extension to other points.


2. Choose a point that has a Y in the TC column. This is now the source point.

3. Select Copy. The system displays the Copy - Temperature Control dialog box (see Figure 10-17).

4. Choose a Target point from the drop-down list of all active DO and DC points on the controller that do not have temper-ature control.

5. Select OK. The system displays the Temperature Control editor (see Figure 10-16).

6. Modify the temperature control parameters as required. (Refer to “Adding a Temperature Control Point Extension” on page 10-16)

7. Select OK to return to the Temperature Control point exten-sion editor (see Figure 10-15).

Figure 10-17. Copy - Temperature Control Dialog box


Demand Control (DC) Dynamic Control

8. Repeat Steps 2 through 7 as required to copy temperature control to other points.

9. Select Close to exit this procedure.

Deleting a Temperature Control Point ExtensionUse the following procedure to delete a temperature control point extension.


2. Select the point whose temperature control you want to delete.


4. Click Yes. The system displays the Resident I/O Points editor with the Y removed from the TC column for this point.

5. Repeat Steps 2 through 4 for any additional temperature control extensions that you want to delete.

6. Select Close to exit.

Demand Control (DC)

This extension is used only with PI points. It is available on all controllers except the 7750, 7770, 7780, and 7791. Add this exten-sion to a PI point to monitor electrical power demand and consumption, and maintain daily and/or monthly power consumption totals. When combined with the load shedding capa-bility (ability to control points off), you have an extremely powerful and flexible electrical demand control program.

The load shedding feature of Demand Control lets you establish target demand shed level setpoint(s). The controllers on the LAN shed (turn off) and restore (turn on) loads (DO and DC points) as needed to operate your facility within the targeted demand level.


Dynamic Control Demand Control (DC)

This limits the demand segment of the electric utility charges. Loads are shed and restored according to a priority you assign, with lower level loads shed before loads assigned a higher priority. Loads are restored in reverse order; those with the highest priority are restored first.

Refer to the section on Demand Control in TCON300, TAC I/NET Seven Technical Reference Guide for more information.

Adding a Demand Control Point ExtensionUse the following procedure to add demand control to a point:

1. Select Edit Controller Point Extensions Demand Control, or click the Demand Control tool on the Extensions toolbar. The Resident I/O Points editor displays with the demand control (DC) option selected (see Figure 10-18).

This editor lists all the PI points currently residing in this controller. Each point is listed by address, class, and name. A Y in the DC column indicates that demand control has been added to the point.

Figure 10-18. Resident I/O Points Editor (DC selected)



Note: If you choose a point that already has demand control, then the Add button is not enabled and demand control cannot be added. In this case you may either modify, copy, or delete the demand control.

2. Choose a point that does not have a Y in the DC column and select Add. The system displays the Demand Control editor (see Figure 10-19).

3. Modify the parameters under Demand Details:

✧ Demand interval (minutes) - This is the time period over which the calculation of demand is based. You may enter any value between 5 and 90 minutes in 5-minute increments.

✧ Current demand point - If you wish to use an internal analog point to display current demand, choose the point from the pull-down list here. This entry is optional.

Figure 10-19. Demand Control Editor



✧ Monthly consumption point - If you wish to use an internal PI point to store month-to-date consumption, choose the point from the pull-down list here. This entry is optional.

4. Modify the parameters under SevenTrends:

a. Choose a Distribution group (1–4). The cell mask will be applied to this group.

b. Define the Distribution mask. Set each of eight masking positions to the desired state, either activated () or deactivated ().

c. Choose a Priority from the drop-down list.

d. Enter a Cell number (1–1023). You must assign a value other than zero (0) 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.

5. Modify the parameters under Normal Shed Level. The normal shed level is the maximum demand target value in kilowatts for the meter in the normal (non-override) state. You may select Point or Scheduled. At this value, priority loads 0–6 will be shed.

✧ Point - If you select Point, you must choose a point from the drop-down list. The value of the point is the normal shed level.

✧ Scheduled - If you selected scheduled, use the Sched-ules (Date and Level) fields to enter the shed levels (see Step 6).

✧ Differential - Enter the number of kilowatts (0–32,767) to subtract from the normal shed level before restoration begins.

6. If you selected Scheduled in Step 5, you may enter up to 12 schedule dates in the Schedules section. This field affects two different processes: the schedule option for normal shed levels and the zero out process for the monthly KWH accumulator point (if applicable).



✧ Date - Enter the ending date for each schedule period. The default is the end of the month.

If the scheduled option was selected for the normal shed level, this date specifies the ending date for each schedule period.

If a monthly consumption point was specified in Step 3, this field specifies the last day of the month. The monthly accumulator will be zeroed out on midnight of the day entered.

✧ Level - If the scheduled option was selected for the normal shed level, enter the shed level (0–32,767 kilo-watts) for each time period.

7. Modify the parameters under Emergency Shed Level. The emergency shed level is the maximum demand target value in kilowatts that determines when emergency loads (priority 7) will be shed. You may select Point or Constant.

✧ Point - If you select Point, you must choose a point from the drop-down list. The value of the point is the emer-gency shed level.

✧ Constant - If you select Constant, enter the emergency shed level in kilowatts (0–32,767 kilowatts).

✧ Differential - Enter the number of kilowatts (0–32,767) to subtract from the emergency shed level to determine the kilowatt value at which emergency loads will be restored. This prevents emergency loads from turning off and on in rapid succession when the demand level is near the shed level.

8. Modify the parameters under Override Shed Level. The override shed level is the maximum demand target value in kilowatts for the meter in the override state.

✧ Control Point - Specifies if Normal shed level (Control point = 0) or Override shed level (Control point = 1) is in effect.

✧ Point - If you select Point, you must choose a point from the drop-down list. The value of the point is the override shed level.



✧ Constant - If you select Constant, enter the override shed level in kilowatts (0–32,767 kilowatts).

✧ Differential - Enter the number of kilowatts (0–32,767) to subtract from the override shed level.This determines the kilowatt value at which override shed loads will be restored.

9. When you finish entering or modifying the Demand Control meter parameters, select Loads. The system displays the Demand Loads Summary editor (see Figure 10-20).

10. Select Add. The system displays the Demand Load Selection dialog box (see Figure 10-21).

Figure 10-20. Demand Load Summary Editor

Figure 10-21. Demand Load Selection Dialog Box



11. Choose a point from the drop-down list. Click OK to display the Demand Load Edit dialog box. (see Figure 10-22).

Use the Demand Load Edit dialog box (see Figure 10-22) to specify when the load is to be shed, whether the load is NO (on state = 1) or NC (on state = 0), the loads’s maximum off-time, 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 program, and up to 255 demand loads to each controller.

12. In the Priority field enter a priority level (0–7).

13. Select an On State (0 or 1).

14. In the Load Size field enter the DO or DC load size in kilo-watts (0–32,767) for this load.

15. In the Max Off (Min) field enter the maximum off time (0–127) in minutes for this DO or DC load.

16. Select OK. The system displays the Demand Load Summary editor (see Figure 10-20) with a list of the demand loads that you have entered.

17. Repeat Steps 10 through 16 as required to enter additional demand loads.

18. Click Close to return to the Demand Control editor (see Figure 10-19).

19. Select OK. The system displays the Resident I/O Points editor (see Figure 10-18).

Figure 10-22. Demand Load Edit Dialog Box



20. Repeat Steps 2 through 19 as required to add the demand control extension to additional accumulator points.


Modifying a Demand Control Point ExtensionModifying a demand control point extension is similar to adding a demand control point extension. Use the same procedure as described in “Adding a Demand Control Point Extension” on page 10-23 except that you choose a point that has a Y in the DC column and select the Modify button from the Resident I/O Points editor, rather than the Add button.

Copying a Demand Control Point ExtensionOnce you have added a demand control point extension, you can copy the extension to other accumulator points.

1. Select Edit Controller Point Extensions Demand Control, or click the Demand Control tool on the Extensions toolbar. The Demand Control point extension editor displays (see Figure 10-18).

2. Choose a point that has a Y in the DC column. This is now the source point.

3. Select Copy. The system displays the Copy - Demand Control dialog box (see Figure 10-23).

4. Choose a Target point from the drop-down list of all active PI points on the controller that do not have demand control.

Figure 10-23. Copy - Demand Control Dialog Box



5. Select OK to display the Demand Control editor (see Figure 10-19).

6. Modify the demand control parameters as required. (Refer to “Adding a Demand Control Point Extension” on page 10-23)

7. Modify the demand control load parameters. (Refer to Figure 10-20, Figure 10-21, and Figure 10-22 as required.)

8. Select OK to return to the Resident I/O Points editor (see Figure 10-18).

9. Repeat Steps 2 through 8 as required to copy demand control to other points.


Deleting a Demand Control Point ExtensionUse the following procedure to delete a demand control point extension.

1. Select Edit Controller Point Extensions Demand Control, or click the Demand Control tool on the Extensions toolbar. The Resident I/O Points editor displays with the demand control (DC) option selected (see Figure 10-18).

2. Select the point whose demand control you want to delete.


4. Click Yes. The system displays the Resident I/O Points editor (see Figure 10-18) with the Y removed from the DC column for this point.

5. Repeat Steps 2 through 4 for any additional demand control point extensions that you want to delete.



Dynamic Control Auto Report Generation

Auto Report Generation

The auto report generation function allows you to configure TAC I/NET Seven to generate unattended reports at scheduled times. You can choose to have a report generated only once, or at multiple dates and times. Generated reports can be created in any of several formats.

Before you create an Auto Report Generation schedule, confirm that the system date and time on your computer are accurate. The Windows Scheduled Tasks function relies on this information to run scheduled tasks. To verify or change this information, double-click the time indicator on the Windows taskbar.

Note: You must supply the password for the Windows account on which you want the scheduled task to run. The password cannot be blank.

Adding an Auto Report Generation ScheduleUse the following procedure to add an auto report generation schedule:

1. Select Edit Host Computer Auto Report Generation from the main menu. The system displays the Auto Report Name editor (see Figure 10-24).

Figure 10-24. Auto Report Generation Selection


Auto Report Generation Dynamic Control

2. Select Add to create a new automatic report generation schedule. The system displays the Auto Report Name editor (see Figure 10-25), allowing you to define a name for the new schedule.

3. Enter a Report schedule name. This name can be up to 40 characters long.

4. Choose the necessary type of report output. The following options are available:

• Print – Select this option to have the report sent to a printer.

• Export – Select this option to have the report exported into a file that you can open in another application.

5. Select OK to continue. One of the following events will occur:

• If you selected “Export” as the output type, the Auto Report Generation editor opens (see Figure 10-26).

• If you selected “Print” as the output type, the standard Windows print dialog opens, allowing you to choose and configure a printer. When you close the print dialog (by pressing the Print or Cancel button), the Auto Report Generation editor opens (see Figure 10-26).

Figure 10-25. Auto Report Name



6. Choose the necessary type of report output. The following options are available:

• Print – Select this option to have the report sent to a printer.

• Export – Select this option to have the report exported into a file that you can open in another application.

By default, the option that you selected from the Auto Report Name editor will be active.

7. Define the complete path and file name of the Reports source file (up to 516 characters). If necessary, use the “...” button to browse through your file system.

8. If the report is for export, define the complete path and file name of the Reports output file (up to 516 characters) and specify the desired format for the report output by selecting the “...” button. The system displays a file selection dialog box (see Figure 10-27).

a. Navigate through your file system as necessary to choose an output file location.

b. Define the output File name.

c. Use the Files of type drop-down list to choose an output format.

d. Select Open to accept these settings. The file selection dialog box closes.

Figure 10-26. Auto Report Generation



9. Click the Options button to define parameter settings for controlling how the resulting report gets formatted. The system displays the Auto Report Generation Format editor (the example shown in Figure 10-28 is for an Excel file).

The options available will depend on the type of report format you selected in Step 8, substep c. For information about the options available for each output type, refer to the electronic version of the Crystal Reports User Guide (requires Adobe Acrobat reader) located in the TAC I/NET Seven root directory.

Figure 10-27. Select Report File

Figure 10-28. Excel File Options



Note: Some report formats such as Text (*.TXT) have no available options. In this case, clicking the Options button will have no affect.

10. Click the Duration button to open an editor that allows you to define what period of information to include in the report (see Figure 10-29).

By default, the duration settings are configured to allow generation of a “full report” (that is, a report that includes all historical data).

Perform the following steps to modify the duration settings.

a. Choose a Time duration type. Changing this parameter from its default setting of “Full Report” to any other setting allows you to focus the report on a specific period of time.

Select whether the period of time should be a matter of years, months, weeks, days, or hours.

b. Choose a Time duration. This parameter’s setting will determine the number of years-, months-, weeks-, days-, or hours-worth of data to include in the report.

c. Activate () or deactivate () the Use Start Date option.

Activate this option if you would like to specify the start date of the data to include in the report.

Figure 10-29. Report Duration Editor



If you leave this option deactivated, the start date will be calculated each time the report runs. For example, if the report runs on 1/7/2006 and the duration is 3 days, then the start date will be 1/4/2006. In this case, data collected from 1/4/2006 to 1/7/2006 will be included in the report.

d. If you activated the Use Start Date option, use the Start date field to specify the starting date of data to include in the report.

For example, if you set the start date to 1/4/2006 and the duration is 3 days, then data from 1/4/2006 to 1/7/2006 will be included in the report.

e. Click OK to save these settings and close the duration editor.

11. Click the Recurrence button to define a schedule for the report. This causes TAC I/NET Seven to launch the Windows Scheduled Task editor (see Figure 10-30).

Figure 10-30. Windows Scheduled Task Editor



Most of the required parameters are already set when the task editor opens.

Note: While using the Scheduled Task editor, you can view help for any field by clicking the “?” button in the title bar and then clicking on the field.

12. Use the following steps to configure the report generation schedule:

a. The Run as parameter shows the Windows account of the currently logged in operator. You can leave this parameter at its current setting, or you can change it to define which Windows account to use when generating this report.

b. Click Set password... to enter the password assigned to the user account. You cannot leave the password blank.

c. Display schedule settings by clicking the Schedule tab.

d. If you have already defined the schedule needed for this report, you can select it from the drop-down list near the top of the dialog box. Otherwise, click New to define a new schedule.

e. Choose an appropriate setting from the Schedule Task drop-down list. This parameter allows you to choose from several recurring and non-recurring settings.

f. If you chose any setting except for “At Logon” or “At System Startup” in the previous step, one or more task-specific parameters become available. Set the param-eter(s) as necessary.

g. If you chose a setting of “Daily,” “Weekly,” or “Monthly” in Step e, you can use the Advanced... button to specify a Start Date and End Date, and to set Repeat task param-eters.

h. Display additional settings by clicking the Settings tab. Set the parameters as necessary. You can view help for any field by clicking the “?” button in the title bar and then clicking on the field.



i. Select OK to save your settings and close the editor.


C H A P T E R6

11

© 2001–2010 SchTCON299–05/10

Calculations

Calculations (C)

This point extension is used with all point types and is available in all controllers. Add this extension to a point if you need to create one or more internal or external points containing calculations that expand the capability of the controller in some way or provide information that cannot be obtained from a sensor. Refer to the section on Calculations in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding a Calculated Point

Note: You must be connected to the controller containing the points you want to add a calculation to.

Use the Calculated Point worksheet located in TCON157, TAC I/NET Seven Forms and Worksheets to help you define your calcu-lated point.

1. Select Edit Controller Point Extensions Calculation, or click the Calculation tool on the Extensions toolbar. The system displays the Resident I/O Points editor with the calcu-lation (C) option selected (see Figure 11-1).

This screen lists all points currently residing in this controller. Each point is listed by address, class, and name. A Y in the C column indicates that a calculation has been added to the point.

2. Select a point name from the list. This point is now desig-nated as the target of the calculation you plan to enter.

3. Click Add. The system displays the Calculations editor (see Figure 11-2).


Calculations (C) Calculations

Figure 11-1. Calculation Editor

Figure 11-2. Calculations Editor


Calculations Calculations (C)

Caution: The system cannot detect errors in calculations (e.g., dividing by zero). Be sure that your calculation is correct to avoid unwanted results.

4. Enter your calculation either by typing or by selecting param-eters and operators from the Calculations Text pad.

Calculations consist of parameters (points or constants) and operators. There are 10 possible point parameters labeled P0 through P9, and 10 possible constant parameters labeled C0 through C9. You may have all 10 point and/or constant parameters in one calculation if you like, but this is usually not necessary. Also, you can use a parameter more than once.

Refer to the Calculated Point worksheet you filled out. Enter the appropriate point and constant parameters and the neces-sary operators. Remember that all constants must be desig-nated with C0 through C9. You do not type an actual number into the calculation. Points are designated P0 through P9. You do not actually enter the point address into the calculation. Your calculation can contain a maximum of 80 characters.

For example, the calculation for determining the average of two temperatures could be: (P0 + P1)/C0. The parentheses () ensure that the various operations are carried out in the order you intend. In this case the values of the two points are added before their sum is divided by the constant.

5. When you have finished entering the calculation, define your points and constants.

Only the parameters included in the calculation have active fields. In the example above you listed two point parameters, P0 and P1. These would be AI points (temperature sensors).

Define a point as follows:

a. Select a Points field. The system displays a list of all active points in the controller.

b. Select the point for this parameter.

c. Repeat Steps a and b for each point in your calculation.

Define a constant as follows:



d. Select a Constant field.

e. Enter a number.

In the previous example, the constant is two; so you enter a 2 in the C0 field. Make sure the zero that was in the field is not included with your number. You can use any constant up to six significant digits. Numbers more than six digits long are rounded.

f. Repeat Steps d and e for each constant in your calcula-tion.

6. Verify that your calculation, points, and constants are correct. Change as required.

7. Select OK.

8. Repeat Steps 2 through 7 as required for additional calculated points.


Modifying a Calculated PointModifying a calculated point is similar to adding a calculated point. Use the same procedure described in “Adding a Calculated Point” on page 11-1 except that you choose a point that already has a Y in the C column and select Modify from the Resident I/O Points editor rather than Add.

Copying a Calculated PointOnce you have added a calculated point, you can copy the calcula-tion to other points.

1. Select Edit Controller Point Extensions Calculation, or click the Calculation tool on the Extensions toolbar. The system displays the Resident I/O Points editor with the calcu-lation (C) option selected (see Figure 11-1).

2. Select a point name that has a Y in the C column. This point is now designated as the source of the calculation you plan to copy.


Calculations Calculations (C)

3. Select Copy. The system displays the Extension Copy - Calcu-lation dialog box. (see Figure 11-3).

4. Select an active point in the Target field.

5. The Calculations Editor displays (see Figure 11-2) for the target point.

6. Modify the calculation or parameters as required.

7. Select OK.

8. Repeat Steps 2 through 7 as required for any additional calcu-lations that you want to copy.


Deleting a Calculated PointOnce you have added a calculated point, you can delete it.

1. Select Edit Controller Point Extensions Calculation from the main menu. The system displays the Resident I/O Points editor with the calculation (C) option selected.

2. Select a point name that has a Y in the C column.


4. Click Yes. The system deletes the calculation and displays Resident I/O Points editor with the calculation (C) option selected (see Figure 11-1). The Y has been removed from the C column for the selected point.

Figure 11-3. Calculation Extension Copy Window



5. Repeat Steps 2 through 4 as required for any additional calcu-lations that you want to delete.



C H A P T E R20

12

© 2001–2010 SchTCON299–05/10

Trending

Trend Sampling (TR)

This extension is available for all points on all controllers. Assign this extension to a point if you want to collect data to be used in a graph or printed in a SevenTrends report. This editor lets you determine how often and when to sample the point. You may also specify the length of time between samples. This may be useful if you wish to stagger multiple point sampling; point A at 8:00, point B at 8:05, point C at 8:10, and so on.

Refer to the section on Trend Sampling in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding Trend Sampling

Note: If both Trend Sampling and Trend Log are to be added on the same point, use the host Trend Log editor to define trending parameters — do not add a Trend Sampling extension or make edits through the DCU-resident Trend Sampling editor. Refer to “Trend Log” on page 12-18.

1. Ensure you are connected to the controller containing the points you want to sample.

2. Select Edit Controller Point Extensions Trend Sampling, or click the Trend Sampling tool on the Extensions toolbar. The system displays the Resident I/O Points editor with the trend sampling (TR) option selected (see Figure 12-1).

This screen lists all points currently residing in this controller. Each point is listed by address, class, and name. A Y in the TR column indicates that trend sampling has been added to the point.


Trend Sampling (TR) Trending

Note: In the following step, if you choose a point that already has trend sampling, the Add button is not enabled and trend sampling cannot be added. In this case you may either modify, copy, or delete the trend sampling.

3. Choose a point that does not have a Y in the TR column and select the Add button. The system displays the Trend Sampling editor (see Figure 12-2).

Note: Refer to TCON300, TAC I/NET Seven Technical Reference Guide for a description of the Trend Sampling screen parameters.

4. Set the parameters under SevenTrends:

a. Choose a Distribution group (1–4). The trending mask will be applied to this group.

b. Define the Distribution mask. Set each of eight masking positions to the desired state, either active () or inactive ().


Figure 12-1. Resident I/O Points Editor (TR selected)


Trending Trend Sampling (TR)

d. Select a Cell number (1–1023). You must assign a value other than zero (0) 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.

e. Enter a Sample count (0–30).

5. Set the parameters under Sample Control:

a. Enter the Base time in 24-hour format.

b. Enter the Interval (minutes) from 1–1440.

c. Enter the Number of samples (1–1440).

d. Select a Sample control mode. None is the default and requires no further action. If you select Time, perform Step e. If you select Point, perform Step f.

e. Enter the Start and Stop times in 24-hour format.

f. Choose a Point from the drop-down list.

6. If you would like to display a trend plot, select Graph. The system will plot the selected point. You can also display a trend plot without accessing the Trend Sampling editor (refer to “Trend Plot” on page 12-6.)

Figure 12-2. Trend Sampling Edit Window



7. When you are finished with the Trend Sampling editor, select OK. The system saves the settings and displays the Resident I/O Points editor with the trend sampling (TR) option selected (see Figure 12-1). The point you selected has a Y in the TR column.

8. Repeat Steps 3 through 7 for additional points.

9. Select Close to save the settings and exit this procedure.

Modifying Trend SamplingModifying trend sampling is similar to adding trend sampling. Use the same procedure as described in “Adding Trend Sampling” on page 12-1 except that you choose a point that has a Y in the TR column and select Modify (rather than Add) from the Resident I/O Points editor.

Copying Trend SamplingOnce you have added trend sampling, you can copy the trend sampling extension to other points.

1. Select Edit Controller Point Extensions Trend Sampling, or click the Trend Sampling tool on the Extensions toolbar. The system displays the Resident I/O Points editor with the trend sampling (TR) option selected (see Figure 12-1).

2. Select a point that has a Y in the TR column. This is now the source point.

3. Click Copy. The system displays the Extension Copy dialog box (see Figure 12-3).

Figure 12-3. Trend Sampling Extension Copy Window


Trending Trend Sampling (TR)

4. Choose a Target point from the drop-down list of all eligible points.

5. Select OK. The system displays the Trend Sampling Window (see Figure 12-2).

6. Set the trend sampling parameters as required. (Refer to “Adding Trend Sampling” on page 12-1)

7. Click OK. The system displays the Resident I/O Points editor with the trend sampling (TR) option selected (see Figure 12-1).

8. Repeat Steps 2 through 7 as required to copy trend sampling to other points.

9. Select Close to save the settings and exit this procedure.

Deleting Trend SamplingDelete Trend Sampling by removing the trend sampling (TR) extension from the controller point. Use the following procedure to delete trend sampling.

1. Select Edit Controller Point Extensions Trend Sampling, or click the Trend Sampling tool on the Extensions toolbar. The Resident I/O Points editor displays with the trend sampling (TR) option selected (see Figure 12-1).

2. Choose the point whose trend sampling you want to delete.

3. Select Delete. The system displays the Trend Sampling Delete prompt.

4. Click Yes. The system displays the Resident I/O Points editor with the trend sampling (TR) option selected (see Figure 12-1). The Y has been removed from the TR column for this point.

5. Repeat Steps 2 through 4 for any additional trend sampling that you want to delete.




Trend Plot This editor automatically plots the data collected according to the parameters defined in the Trend Sample extension editor. Data is plotted on an x-y axis. The x-axis represents time and the y-axis scales the point value range.

Use the following procedure to generate a trend plot:

1. Select Edit Controller Point Extensions Trend Plot, or click the Trend Plot tool on the Extensions toolbar. The system displays a blank graph.

2. Select a point from the Point selection drop-down box.

3. Now select I/O Plot to update the graph. The system displays a graph similar to the one shown in Figure 12-4.

Figure 12-4. Sample Trend Plot


Trending Multi-Point Trend Plot

4. To print this graph, select Print.

Note: When you print a Trend Plot, the scaling of the plot in the printed output may not match that of the plot displayed on your monitor. This in normal operation and is the result of the resolution differ-ences between the printer and the monitor.

5. To plot another point from the current graph, repeat Steps 2 and 3.

6. Select Close to exit the graph.

Multi-Point Trend Plot

This function allows you to plot up to six different points on the same trend plot. The points do not have to be on the same controller, nor do you have to be connected to the controller(s) where the points reside. Any direct connect point on the system may be used; dial points are not available.

In order to use this function, the points to be plotted must have trend data available. Refer to “Adding Trend Sampling” on page 12-1, for instructions 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.

Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for a description of the multi-point trend plot screen parameters.


Multi-Point Trend Plot Trending

Defining a Multi-Point Trend PlotSelect Trends Multi-Point Trend, or click the Multi-Point Trend tool on the Reports toolbar. The Multi-Point Trend Graphing menu will appear (see Figure 12-5). This screen provides a list of multi-point trend plots that have already been assigned. If you have not used this function previously, the list is empty.

Note: Points with Trend Sampling and Trend Log extensions may be added to Multi-Point Trend Plots.

Adding a Plot Definition1. Choose a blank line from the list and select Add to add a plot

definition. The system displays the Multi-Point Trend Graph editor (see Figure 12-6 on page 12-9).

2. Define a plot Name (up to 8 characters).

3. Enter the plot Title (up to 48 characters).

4. Enter the Interval spacing for the Y1 axis. The Y1 axis is the left axis.

5. Enter the Low value for the Y1 axis.

Figure 12-5. Multi-Point Trend Graphing Menu



6. Enter the Interval spacing for the Y2 axis. The Y2 axis is the right axis.

7. Enter the Low value for the Y2 axis.

8. Enter the Live Scan Rate (0–32,767 seconds).

9. Select up to six points for this plot using the procedure outlined in “Trend Points” on page 12-10.

10. When you are finished with the plot definition, select OK to save your parameters. The Multi-Point Trend Graphing selec-tion dialog box will reappear (Figure 12-5), with the new defi-nition in the list box.

Modifying a Plot Definition1. Choose the plot definition you wish to change and select

Modify. The system displays the Multi-Point Trend Graph editor for that plot definition (see Figure 12-6).

2. Select the field you wish to change, and enter the new value. See “Trend Points” on page 12-10 for instructions on adding and changing the points for the plot.

3. When you are finished, select OK to save your parameters. You will return to the Multi-Point Trend Graphing screen (Figure 12-5).

Figure 12-6. Multi-Point Trend Graph Editor



Copying a Plot Definition1. Choose the plot definition that you wish to copy from, and

select Copy. The Copy Multi-Point Trend screen will appear (see Figure 12-7).

2. Enter the name of the plot definition you wish to copy to. This may be either a new or existing definition.

3. Select OK. The Multi-Point Trend Graph editor will appear (Figure 12-6).

4. If you wish to make adjustments, select the field you wish to change and enter the new value. See “Trend Points” on page 12-10 for instructions on adding and changing the points for the plot.

5. When you are finished, select OK to save the parameters. You will return to the Multi-Point Trend Graphing screen (Figure 12-5).

Deleting a Plot Definition1. Select the plot definition you wish to remove, and select

Delete. The Delete confirmation dialog box displays.

2. Select Yes to delete the plot definition. If you do not wish to delete the plot definition, select No.

Trend Points

The Multi-Point Graph editor includes an editor that displays the points selected for this plot definition. If you have not previously defined any points for this plot definition, the editor is empty.

Figure 12-7. Copy Multi-Point Trend Screen



✦ To add a new point to the plot, select a blank line and select Add.

✦ To change a point on the plot, select the desired point and select Modify.

✦ To delete a point from the plot, select the desired point and select Delete.

If you are adding or modifying a point, the Point Definition dialog appears (see Figure 12-8). Within this dialog box you can select a point and establish the point details.

Point Details1. Select the Pen color for this point on the plot display. The

box to the right displays the selected color.

2. Select which Axis scale this point will use, either Y1 (left) or Y2 (right).

3. Check the Print box if you wish this point to be included on a printed plot. If you do not want the point included, or if you will not be printing plots, leave the checkbox blank.

Point Selection

It is not necessary to be connected to the controller(s) containing your points. However, you must manually enter the point address(es) for any point that resides on a controller you are not connected to.

1. Choose Select to pick a point. The system displays the Point Selection screen similar to the example in Figure 12-9.

Figure 12-8. Point Definition Screen



The first window, labeled List 0, displays the eligible points in the last controller you connected to. Only the points with trend sampling extensions are listed.

2. If desired, connect to up to three additional controllers:

a. Activate one of the radio buttons for the List 1, List 2, or List 3 windows.

b. Select the Station button to display the Controller Summary dialog box (see Figure 12-10).

c. Select a controller from the list, and select OK to connect to the controller. You will return to the Point Selection screen (Figure 12-9) and the eligible points from the selected controller will appear in the list window. Only the points with trend sampling extensions are listed.

d. Repeat Steps b and c as required to connect to additional controllers.

Figure 12-9. Point Selection



3. Select a point to include in the plot.

✧ Position the cursor and click the left mouse button to select a point from one of the list windows. The point address, point type, and controller type will automati-cally be entered in the Current Point boxes below.

— OR —

✧ Enter the full point address in the Current Point boxes at the bottom of the screen: Link (LL), Station (SS), Point (PP), Bit Offset (BB), and point Type (PT). The Controller type is optional.

4. Select OK to include the Current Point in the plot definition. You will return to the Point Definition screen (Figure 12-8).

Once you have selected the point to display and the point details, select OK. You will return to the Multi-Point Trend Graph editor (see Figure 12-6 on page 12-9). The point information will appear in the point display window.

Displaying a Multi-Point Trend PlotSelect Trends Multi-Point Trend, or click the Multi-Point Trend tool on the Reports toolbar. The Multi-Point Trend Graphing menu will appear (see Figure 12-5 on page 12-8). This screen provides a list of multi-point trend plots that have already been assigned. If you have not used this function previously, the list is empty. See “Defining a Multi-Point Trend Plot” on page 12-8 for instructions on adding a plot definition.

Figure 12-10. Controller Summary Dialog Box



Select the desired plot definition and select Graph. Allow time for the system to receive the trend data from the controllers for plot-ting. The trend plot will appear similar to the one shown in Figure 12-11.

Note: Multi-point trend plot is a global function and will not work if someone else is currently using the defined points for a trend plot.

Display Functions

Several functions allow you to change the display.

Live / Historical

The plot display originally displays historical data. This is the trend sampling data currently stored in the controller. Select Live to change to a live data display. The plot will then update the point at the interval specified in the Live Scan Rate.

Figure 12-11. Multi-Point Trend Plot Screen



When live data is displayed, the button changes to read “Historical”. Select Historical to change back to a historical data display.

Grid

Select Grid to enable a grid on the plot display. The grid lines are placed at the major tick marks on each axis. Select Grid again to disable the grid display.

Print

Select Print to print the sample data from the current plot. Only points with the Print check box selected will be printed (see “Point Details” on page 12-11).

✦ If the display is in historical data mode, all data for the points will be printed.

✦ If the display is in live data mode, only the data from the current screen will be printed.

Note: The Print option is not available (i.e., it appears gray) if no points have the Print check box selected.

When you print a Trend Plot, the scaling of the plot in the printed output may not match that of the plot displayed on your monitor. This in normal operation and is the result of the resolution differ-ences between the printer and the monitor.

Auto Scale / Manual Scale

The plot display originally displays the manual scale for the Y1 (left) and Y2 (right) axes. This is the scale you defined with the Interval and Low value entries for each axis (see “Adding a Plot Definition” on page 12-8). If the sample data is outside this range, the point will not appear on the plot (off-scale data).

Select Auto Scale to enable automatic axis scaling. The interval and low value for each axis will be adjusted to accommodate all data values.

When the automatic scale is enabled, the button changes to read “Manual Scale”. Select Manual Scale to change back to the original axis scales.



Options

This button allows you to change the display scales. Select Options to display the Trend Graph Options editor. This screen appears in front of the plot (see Figure 12-12).

As you change the values on this screen, you will be able to see the effect of the new value(s) on the plot behind the window. This allows you to achieve the desired configuration without multiple visits to this screen.

Note: This function changes only the existing plot display. It does not modify the plot definition.

The field entries are described below. When you are finished making changes, select Close to return to the plot display.

✦ Change the Y1 axis interval and Y1 axis low values to change the manual scale of the Y1 axis (on the left edge of the plot). If the current plot uses automatic scaling, you will not see any change.

✦ Change the Y2 axis interval and Y2 axis low values to change the manual scale of the Y2 axis (on the right edge of the plot). If the current plot uses automatic scaling, you will not see any change.

✦ Change the Live scan rate to increase or decrease the time interval between scans during a live data display (0–32,767 seconds). This option is not available if the current plot uses historical data.

Figure 12-12. Trend Graph Options Editor



✦ Change the X (time) scale to compress the time duration shown on the screen.

✧ The default value is a factor of x1, which is the regular time scale. Each tick mark is one minute (historical) or one second (live).

✧ x2 — Each tick mark is two minutes (historical) or two seconds (live).

✧ x5 — Each tick mark is five minutes (historical) or five seconds (live).

✧ x10 — Each tick mark is ten minutes (historical) or ten seconds (live).

✧ x15 — Each tick mark is fifteen minutes (historical) or fifteen seconds (live).

✧ x30 — Each tick mark is thirty minutes (historical) or thirty seconds (live).

✧ x60 — Each tick mark is sixty minutes (historical) or sixty seconds (live).

Clipboard

Select Clipboard to copy the data from the plot (not the graph itself) to the Windows clipboard. This data may then be pasted into a third-party program. Refer to TCON300, TAC I/NET Seven Tech-nical Reference Guide, for information on the data format.

Zooming to Multi-Point Plot Values

You can view the values for a specific time on the plot by double-clicking the left mouse button on the background at the desired point of the x-axis. A pop-up screen displays at the bottom of the plot window as shown in Figure 12-13.

A dotted line displays on the plot showing the selected x-axis point. The sample time is displayed in the pop-up window. Each point is displayed with the point address, point type, point name, color of the point’s plot line, the y-axis used, and the value of the plot on the y-axis.

DO and GO points will plot on the major divisions starting with the first major division. These plots may not reflect all of the state changes depending upon the trend sample interval. DO and GO


Trend Log Trending

points with two states will increment to the first minor division. GO points can increment up to the eighth minor division, for an eight-state point.

Trend Log

The trend log function within TAC I/NET Seven lets you generate your own customized trend log reports. A trend log can contain up to 12 unique discrete/analog point addresses.

Note: If both Trend Log and Trend Sampling are to be added on the same point, use the host Trend Log editor (described here) to define trending parameters — do not add a Trend Sampling extension or make edits through the DCU-resident Trend Sampling editor.

Figure 12-13. Values Zoom


Trending Trend Log

1. Select Edit Host Computer Host Trend Log, or click the Host Trend Log tool on the Host toolbar. The system displays the Trend Log editor (see Figure 12-14).

2. Select Add. The system displays the Trend Log Address dialog box (see Figure 12-15).

3. Enter a point Address. You must include the 8-digit address and the 2-digit point class designation. Do not use a point that already has a Trend Sampling extension (refer to the note at the beginning of these procedures).

4. Select OK. The system returns to the Host Trend Log editor (see Figure 12-14) with the address and name of the point selected.

5. Set the Trend parameters as required. Refer to the section on Trend Log in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

a. Enter a Sample interval (min) from 1 to 1440.

Figure 12-14. Host Trend Log Editor

Figure 12-15. Host Trend Log Address


Trend Log Trending

b. Enter a Print interval (min) from 1 to 1440.

c. Enter a Print begin (hh:mm) time in 24-hour format.

d. Enter a Print end (hh:mm) time in 24-hour format.

6. Repeat Steps 2 through 5 for additional points.


Deleting a Trend Log1. Select Edit Host Computer Host Trend Log from the

main menu. The system displays the Host Trend Log screen (see Figure 12-14) with a list of points having a trend log.

2. Choose a point.


4. Select Yes. The system displays the Trend Log screen (see Figure 12-14).

5. Repeat Steps 2 through 4 as required for any additional trend logs that you want to delete.

6. Select OK to exit this procedure.


C H A P T E R26

13

© 2001–2010 SchTCON299–05/10

Distributed Control

Consumption (CN)

This point extension is used only with PI (accumulator) points such as flow meters. It is available on all controllers. Refer to the section on Consumption in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding a Consumption Point ExtensionAdd the Consumption point extension to a PI point if you want to direct the accumulated value of a PI point to a particular consump-tion cell for storage, and/or zero the value stored in the DCU for the PI point at midnight.

Note: You must be connected to the controller containing the points to which you want to add this extension.

1. Select Edit Controller Point Extensions Consumption, or click the Consumption tool on the Extensions toolbar. The system displays the Consumption Point Extension screen (see Figure 13-1), which lists the PI points currently residing in this controller.

2. Choose a point that does not have a Y in the CN column. This point is now designated as the target of the consumption point extension you plan to enter.

3. Select Add. The system displays the Consumption Editor window (see Figure 13-2).

4. Modify the SevenTrends parameters as required:

a. Choose a Distribution group (1–4). The distribution mask will be applied to this group.


Consumption (CN) Distributed Control



d. Select a Cell number (1–1023). You must assign a value other than zero (0) 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.

Figure 13-1. Consumption Point Extension Screen

Figure 13-2. Consumption Data Details


Distributed Control Consumption (CN)

5. Select OK. The system displays the Consumption Point Exten-sion screen with a Y in the CN column.

6. Repeat Steps 2 through 5 as required to add this point exten-sion to additional points.


Modifying a Consumption Point ExtensionModifying a consumption point extension is similar to adding a consumption extension. Use the same procedure as described in “Adding a Consumption Point Extension” on page 13-1 except that you choose a point that has a Consumption extension and select the Modify button instead of the Add button.

Copying a Consumption Point ExtensionOnce you have added a consumption point extension to a point, you can copy the extension to other points.

1. Select Edit Controller Point Extensions Consumption, or click the Consumption tool on the Extensions toolbar. The system displays the Consumption Point Extension screen (see Figure 13-1).

2. Select a point that has a Y in the CN column. This is now the source point.

3. Select Copy. The system displays the Extension Copy window (see Figure 13-3).


Figure 13-3. Consumption Extension Copy Window


Runtime (RT) Distributed Control

5. Select OK. The system displays the Consumption Data Details dialog box. (see Figure 13-2).

6. Modify the consumption parameters as required. (Refer to “Adding a Consumption Extension” on page 13-1)

7. Select OK. The system displays the Consumption Point Exten-sion editor (see Figure 13-1).

8. Repeat Steps 2 through 7 as required to copy the consumption point extension to other points.


Deleting a Consumption Point ExtensionDelete a Consumption point extension by removing the consump-tion (CN) extension from the controller point. Use the following procedure to delete a consumption point extension.

1. Select Edit Controller Point Extensions Consumption, or click the Consumption tool on the Extensions toolbar. The system displays the Consumption Point Extension editor.

2. Select the point whose consumption point extension you want to delete.

3. Select Delete. The system displays the Delete confirmation dialog box.

4. Select Yes. The system displays the Consumption Point Extension editor (see Figure 13-1) with the Y removed from the CN column for this point.

5. Repeat Steps 2 through 4 for any additional consumption point extensions that you want to delete.


Runtime (RT)

This point extension is used with DO, DC, or DI points. It is avail-able on all controllers. Use this extension editor to define runtime parameters for a discrete input or output point so that runtime


Distributed Control Runtime (RT)

information can be collected. This information can then be printed in SevenTrends reports. See the section on Runtime in TCON300, TAC I/NET Seven Technical Reference Guide for more information.

Adding a Runtime Point Extension1. Select Edit Controller Point Extensions Runtime, or

click the Runtime tool on the Extensions toolbar. The system displays the Runtime Point Extension editor (see Figure 13-4), which lists the DI, DO, and DC points currently residing in this controller.

2. Choose a point that does not have a Y in the RT column. This point is now designated as the target of the runtime extension you plan to enter.

3. Select Add. The system displays the Runtime Editor (see Figure 13-5).

4. Change the parameters as required:

a. Select one of two On states (0 = open, 1 = closed).

Figure 13-4. Runtime Point Extensions Summary



b. Choose a Distribution group (1–4). The distribution mask will be applied to this group.

c. Define the Cell mask. Set each of eight masking posi-tions to the desired state, either active () or inactive ().

d. Choose a Cell priority from the drop-down list.

Note: A cell number of zero indicates that no cell number is assigned.

e. Define the Cell number (0–1023) used to store the daily runtime data.

f. Define a Runtime accumulator point. This is the address of an internal pulsed input (PI) point.

Note: In the following step, the Reset Mode refers to the internal runtime accumulator (PI) you just defined, not the discrete point to which this runtime extension is attached.

5. Select one of three Reset Modes:

✧ None - Internal runtime accumulator will accumulate forever or until you manually reset the point.

Figure 13-5. Runtime Editor


Distributed Control Runtime (RT)

✧ Constant - Enter a number of hours from 0 to 65,535 that the internal runtime accumulator will collect data before being reset.

✧ Point (reset point) - Define a reset point address. This point resets the internal runtime accumulator when it transitions from the 0 state to the 1 state.

6. Select OK. The system displays the Runtime Point Extension screen with a Y in the RT column.

7. Repeat Steps 2 through 6 as required to add this extension to additional points.


Modifying a Runtime Point ExtensionModifying a runtime point extension is similar to adding a runtime point extension. Use the same procedure as described in “Adding a Runtime Point Extension” on page 13-5 except that you choose a point with a Runtime extension and select Modify rather than Add from the Runtime screen.

Copying a Runtime Point ExtensionOnce you have added a runtime extension to a point, you can copy the extension to other points.

1. Select Edit Controller Point Extensions Runtime, or click the Runtime tool on the Extensions toolbar. The system displays the Runtime Point Extension editor (see Figure 13-4).

2. Select a point that has a Y in the RT column. This is now the source point.

3. Select Copy. The system displays the Runtime Extension Copy window (see Figure 13-6).

4. Choose a Target point from the drop-down list of all active points on the controller that do not have a runtime extension.

5. Select OK. The system displays the Runtime Editor window (see Figure 13-5).



6. Modify the runtime parameters as required. (Refer to “Adding a Runtime Point Extension” on page 13-5)

7. Select OK. The system displays the Runtime Point Extension screen (see Figure 13-4).

8. Repeat Steps 3 through 7 as required to copy additional runtime extensions.


Deleting a Runtime Point ExtensionDelete a Runtime point extension by removing the runtime (RT) extension from the controller point. Use the following procedure to delete a runtime point extension.

1. Select Edit Controller Point Extensions Runtime, or click the Runtime tool on the Extensions toolbar. The system displays the Runtime Point Extension editor.

2. Choose the point whose runtime extension you want to delete. This point must have a Y in the RT column.

3. Select Delete. The system displays the Delete prompt.

4. Select Yes. The system displays the Runtime Point Extension editor (see Figure 13-4) with the Y removed from the RT column for this point.

5. Repeat Steps 2 through 4 for any additional Runtime point extensions that you want to delete.


Figure 13-6. Runtime Extension Copy Window


Distributed Control Alarm Inhibit (AI)

Alarm Inhibit (AI)

This point extension is used with AI, GI, DA, and DM points. It is available on all controllers. Add this extension to a point to prevent nuisance alarms that may occur when a piece of equipment is off. You may also use this extension to determine which state (0 or 1) of the controlled device inhibits and/or enables the alarm. See the section on Alarm Inhibit in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding an Alarm Inhibit Point ExtensionUse the following procedure to add an alarm inhibit point exten-sion:

1. Select Edit Controller Point Extensions Alarm Inhibit, or click the Alarm Inhibit tool on the Extensions toolbar. The system displays the Alarm Inhibit Point Extension editor (see Figure 13-7), which lists the AI, GI, DA, and DM points currently residing in this controller.

Figure 13-7. Alarm Inhibit Point Extension Summary


Alarm Inhibit (AI) Distributed Control

2. Choose a point that does not have a Y in the AI column. This point is now designated as the target of the alarm inhibit extension you plan to enter.

3. Select Add. The system displays the Alarm Inhibit editor (see Figure 13-8).

4. Select a Status input from the drop-down list. The system displays a list of points (DA, DI, DO, DC, and DM) that can be used to determine the inhibiting or enabling of an alarm point.

5. Select an Enable state (0 = open, 1 = closed).

6. Set the Delay before enable (min) duration. Enter the number of minutes that the alarm is to remain inhibited after the status input point transitions to the enable state.

7. Set the Delay Before inhibit (min) duration. Enter the number of minutes that the alarm is to remain enabled after the status input point transitions to the inhibit state.

8. Select OK. The system displays the Alarm Inhibit Point Exten-sion screen with a Y in the AI column.



Figure 13-8. Alarm Inhibit Editor


Distributed Control Alarm Inhibit (AI)

Modifying an Alarm Inhibit Point ExtensionModifying an alarm inhibit point extension is similar to adding an alarm inhibit point extension. Use the same procedure as described in “Adding an Alarm Inhibit Point Extension” on page 13-9 except that you choose a point with an Alarm Inhibit extension and select Modify rather than Add from the Alarm Inhibit point extension screen.

Copying an Alarm Inhibit Point ExtensionOnce you have added an alarm inhibit extension to a point, you can use the following procedure to copy the extension to other points.

1. Select Edit Controller Point Extensions Alarm Inhibit, or click the Alarm Inhibit tool on the Extensions toolbar. The system displays the Alarm Inhibit Point Extension editor (see Figure 13-7).

2. Choose a point that has a Y in the AI column. This is now the source point.

3. Select Copy. The system displays the Alarm Inhibit Extension Copy window.


5. Select OK. The system displays the Alarm Inhibit editor (see Figure 13-8).

6. Modify the alarm inhibit parameters as required. (Refer to “Adding an Alarm Inhibit Point Extension” on page 13-9)

7. Select OK. The system displays the Alarm Inhibit Point Exten-sion screen (see Figure 13-7).

8. Repeat Steps 2 through 7 as required to copy a runtime exten-sion to other points.



Event Definition (EV) Distributed Control

Deleting an Alarm Inhibit Point ExtensionDelete an Alarm Inhibit point extension by removing the alarm inhibit (AI) extension from the controller point. Use the following procedure to delete an alarm inhibit point extension.

1. Select Edit Controller Point Extensions Alarm Inhibit, or click the Alarm Inhibit tool on the Extensions toolbar. The system displays the Alarm Inhibit Point Extension editor (see Figure 13-7).

2. Choose the point whose alarm inhibit extension you want to delete.


4. Select Yes. The system displays the Alarm Inhibit Point Extension screen (see Figure 13-7) with the Y removed from the AI column for this point.

5. Repeat Steps 2 through 4 for any additional alarm inhibit point extensions that you want to delete.


Event Definition (EV)

This point extension editor is used with all point types and is avail-able on all controllers. Use this point extension to specify a certain condition and the response that condition initiates. The event you define causes an Event Sequence or an Event Action to be initiated. Once you define the event in this editor, you must access the Event Sequence or Event Actions editors to define the event sequence or event action. See the section on Event Definition in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding an Event Definition Point ExtensionUse the following procedure to add an event definition point exten-sion:


Distributed Control Event Definition (EV)

1. Select Edit Controller Point Extensions Event Defini-tion, or click the Event Definition tool on the Extensions toolbar. The system displays the Event Definition Point Exten-sion screen (see Figure 13-9), which lists all points currently residing in this controller.

2. Choose a point that does not have a Y in the EV column. This point is now designated as the target of the event definition extension you plan to enter.

3. Select Add. The system displays the Event Definition editor (see Figure 13-10).

4. Change the Event Definition parameters as required. When this editor first appears, only the Event type field is active. After you select an event type, the other fields become active.

a. Choose an Event type from the drop-down list. The options available will depend on the type of point (i.e., discrete point, discrete door point, or analog point) currently selected.

Figure 13-9. Event Definition Point Extension Screen


Event Definition (EV) Distributed Control

b. Choose Sequence or Action from the drop-down list.

c. Using the Num spindial, select a Sequence/Action Number from 1 through 64.

d. The State/Value field is only active when the “Specified State” event type is chosen for a discrete point, or when the “High Crossing” or “Low Crossing” event type is chosen for an analog point. Factors such as the point type, the system’s current operating mode, and the connected SLI’s firmware revision level will determine which settings are available for this parameter. Refer to “Event Definition (EV)” in Chapter 7 of TCON300, TAC I/NET Seven Technical Reference Guide, for a complete description of this parameter.

5. Select OK. The system displays the Event Definition Point Extension screen with a Y in the EV column.



Figure 13-10. Event Definition Editor


Distributed Control Event Definition (EV)

Modifying an Event Definition Point ExtensionModifying an event definition extension is similar to adding an event definition extension. Use the same procedure as described in “Adding an Event Definition Point Extension” on page 13-12 except that you choose a point that has a Event Definition extension and select Modify rather than Add from the Event Definition point extension screen (see Figure 13-9).

Copying an Event Definition Point ExtensionOnce you have added an event definition extension to a point, you can use the following procedure to copy the extension to other points.

1. Select Edit Controller Point Extensions Event Defini-tion, or click the Event Definition tool on the Extensions toolbar. The system displays the Event Definition Point Exten-sion screen (see Figure 13-9).

2. Choose a point that has a Y in the EV column. This is now the source point.

3. Select Copy. The system displays the Event Definition Exten-sion Copy window.

4. Choose a Target point from the drop-down list. Only active points on the controller that do not have an event definition extension are listed.

5. Select OK. The system displays the Event Definition editor (see Figure 13-10).

6. Modify the event definition parameters as required. (Refer to “Adding an Event Definition Point Extension” on page 13-12)

7. Select OK. The system displays the Event Definition Point Extension screen (see Figure 13-9).

8. Repeat Steps 2 through 7 as required to copy a Runtime extension to other points.



Event Sequences Distributed Control

Deleting an Event Definition Point ExtensionDelete an Event Definition point extension by removing the event definition (EV) extension from the controller point. Use the following procedure to delete an event definition point extension.

1. Select Edit Controller Point Extensions Event Defini-tion, or click the Event Definition tool on the Extensions toolbar. The system displays the Event Definition Point Exten-sion screen (see Figure 13-9).

2. Choose the point whose event definition extension you want to delete.


4. Select Yes. The system displays the Event Definition Point Extension screen (see Figure 13-9) with the Y removed from the EV column for this point.

5. Repeat Steps 2 through 4 for any additional event definition point extensions that you want to delete.


Event Sequences

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 steps occur in an emergency situation before the emergency occurs.

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.

Use the Event Sequence form located in TCON300, TAC I/NET Seven Technical Reference Guide, to organize and design the event sequences you need at your facility. Event sequences may be quite complicated and it may be difficult to enter the information into the computer unless you have put the information on paper.


Distributed Control Event Sequences

Refer to the section on Event Sequences in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Note: Event sequences run in a linear manner. They will run from the first item in the sequence through to the last item in the sequence in order to finish. Once they are started they will finish the sequence before that sequence may be called again.

Adding an Event SequenceUse the following procedure to add an event sequence:

1. Select Edit Controller Event Sequences, or click the Event Sequences tool on the Controller toolbar. The system displays the Event Sequences Summary (see Figure 13-11).

Note: You may define up to 64 event sequences for each controller. You may also specify an event sequence number 0 that runs at power up, after a reset of controller power, or a database restore of the DCU. The restart control action for a DO/DC point (entered in the Resident I/O Points editor) that is controlled by event sequence number 0 should be “none”. No other event sequences run at power up.

2. Select a Sequence number and click Add. The system displays the Event Sequence editor (see Figure 13-12).

Figure 13-11. Event Sequences Summary



3. Enter a unique sequence Name (up to 8 characters) and click Add. The system displays the Event Sequence Details editor (see Figure 13-13).

Note: When the Event Sequence Details editor first appears, only the Action field is shown.

4. Edit the parameters as follows:

a. Select an Action from the drop-down list.

Figure 13-12. Event Sequence Editor

Figure 13-13. Event Sequence Details Editor


Distributed Control Event Sequences

b. Enter a Delay time in seconds (0 to 3600). You can use the spindial or type the number.

c. Choose a Point from the drop-down list. This is the point that receives the specified action.

Note: The Skip fields only appear if you choose “Skip if Zero”, “Skip if non–zero”, or “Unconditional Skip” as an action.

d. Under Skip, choose Sequence or Action from the drop-down list.

e. Under Skip, enter a numeric value (1 to 64). If you chose Sequence, the numeric value is the sequence number you want to skip to. If you chose Action, the numeric value is the number of actions to skip.

Note: The Value field only appears if you chose “Output” or “Output with Lock” from the action list.

f. Enter an analog Value that will be output to an AO point as part of this sequence.

5. Select OK. The system displays the Event Sequence editor listing the details of all events that you have entered.

6. Repeat Steps 3 through 5 as required to enter up to 18 events for this sequence.

7. Select OK. The system displays the Event Sequence Summary listing all sequences for this controller.

8. Repeat Steps 2 through 7 to enter up to 65 event sequences.


Modifying an Event SequenceModifying an event sequence is similar to adding an event sequence. Use the same procedure as described in “Adding an Event Sequence” on page 13-17 except that you choose a sequence that has already been defined and select Modify rather than Add from the Event Sequences Summary window (see Figure 13-11) and Sequence Details window (see Figure 13-12).



Copying an Event SequenceUse the following procedure to copy an event sequence:


2. Choose a Sequence # and select Copy. This event sequence is the source sequence. The system displays the Event Sequence - Copy dialog box (see Figure 13-14).

3. Enter a number in the Event sequence target field.

4. Select OK. The system displays the Event Sequence Details editor (see Figure 13-12).

5. Change the details as required, using the procedures outlined in “Adding an Event Sequence”.

6. Edit the Event Dialog parameters as described in the “Adding an Event Sequence” procedure on page 13-17 as required.

7. Select OK. The system displays the Sequence Details window showing the details of all events that have been entered.

8. Repeat Steps 5 through 7 as required to change additional event parameters.

9. Select OK. The system displays the Event Sequence Summary window listing all sequences that have been entered for this controller.

10. Repeat Steps 2 through 9 to copy additional event sequences.


Figure 13-14. Event Sequence - Copy Dialog Box


Distributed Control Event Actions

Deleting an Event SequenceUse the following procedure to delete an event sequence.


2. Choose an event sequence to delete from the list and select Delete. The system displays the Delete confirmation dialog box.

3. Select Yes to delete the event sequence. The system displays the Event Sequences Summary window with the sequence deleted.

4. Repeat Steps 2 and 3 to delete additional event sequences.


Event Actions

Use this editor to create action messages or initiate SevenTrends reports.

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.

Refer to the section on Event Actions in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Adding an Event ActionUse the following procedure to add an event action.

1. Select Edit Controller Event Actions, or click the Event Actions tool on the Controller toolbar. The system displays the Event Actions summary (see Figure 13-15).

2. Choose an event action number and click Add. The system displays the New Event Action Type dialog box (see Figure 13-16).


Event Actions Distributed Control

3. Select an Action Type (Message, Report, or Conversion) and click OK.

Note: The Report and Conversion options are reserved for future use, and are disabled in TAC I/NET Seven.

4. In the Action Message editor (see Figure 13-17) modify the parameters as required:

a. Enter the message that you want displayed or printed in response to the event defined. The message may be one line, up to 64 characters long.

b. Choose a Distribution group (1–4). The distribution mask will be applied to this group.

Figure 13-15. Event Actions Summary

Figure 13-16. New Event Action Type Dialog Box



c. Define the Message mask. Set each of the eight masking positions to the desired state, either activated () or deactivated ().

d. Choose a Message priority from the drop-down list.

e. Select OK. The system displays the Event Actions window.

5. Repeat Steps 2 through 4 as required for additional event actions.


Modifying an Event ActionModifying an event action is similar to adding an event action. Use the same procedure as described in “Adding an Event Action” on page 13-21 except that you choose an action that has already been defined and select Modify rather than Add from the Event Actions window (see Figure 13-15).

Copying an Event ActionUse the following procedure to copy an event action.

1. Select Edit Controller Event Actions, or click the Event Actions tool on the Controller toolbar. The system displays the Event Actions window (see Figure 13-15).

2. Choose the event action you want to copy. This event action is now the source of the action you plan to copy.

Figure 13-17. Action Message Editor


Event Actions Distributed Control

3. Select Copy. The system displays the Copy Event Action window (see Figure 13-18).

4. In the Event Action Target field, select the number of the action where you want to copy this event action from the drop-down list. The system displays a drop-down list of all event action numbers that do not have event actions assigned.

5. Select OK. The system displays the edit window for the type of action being copied.

6. Modify the parameters required. (Refer to “Adding an Event Action” on page 13-21.)

7. Select OK. The system displays the Event Actions summary (see Figure 13-15).

8. Repeat Steps 2 through 7 as required to copy additional event actions.

Deleting an Event ActionUse the following procedure to delete an event action.

1. Select Edit Controller Event Actions, or click the Event Actions tool on the Controller toolbar. The system displays the Event Actions summary (see Figure 13-15).

2. Choose the event action that you want to delete.


4. Select Yes to delete the event action.

5. Repeat Steps 2 through 4 to delete additional event sequences.


Figure 13-18. Event Action - Copy Dialog Box



Configuring Event Printing on a Host WorkstationIn order to print event action messages, you must connect a printer to an available port on a host workstation. The printer used as the event printer must be capable of supporting single line feeds. This will allow multiple messages to be printed on each page, even though the messages are processed and printed individually as they occur. Dot-matrix printers typically support single line feeds and are recommended for use as an event printer.

Perform the following steps to configure a host workstation for event printing:

1. Connect a printer (typically a dot matrix printer) to an avail-able port on the host workstation.

2. Within the “Peripherals” section of the I/NET Configuration Editor, perform the following steps:

a. Define the Printer Port to which the event printer is connected. TAC I/NET Seven will print event action messages directly to this port, without the use of a Windows printer driver.

b. Choose a Printer line spacing setting for the event printer. The options are “Single” and “Double.”

c. If necessary, define an Initialization string for the event printer. Refer to the documentation included with your printer to obtain this information.

d. Select OK to save these settings.

e. Shutdown and restart the I/O Server.


C H A P T E R24

14

© 2001–2010 SchTCON299–05/10

Direct Digital Control

TAC I/NET Seven offers a microprocessor-based direct digital control (DDC) program. DDC consists of modules which perform the following processes:

✦ Measure a variable.

✦ Compare the measured variable against a known value to determine the error.

✦ Process the error according to a specific software algorithm.

✦ Produce an output that modifies the controlled variable.

Each module has its own algorithm. With a basic understanding of control theory and application, these algorithms are easy to under-stand and apply.

Each of the six module types has its own data entry screen where you define parameters such as inputs, algorithm modifiers, and output destinations.

Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for a description of the DDC screen parameters.

Accessing the DDC Module Editors

By now you are probably familiar with the worksheets located in TCON157, TAC I/NET Seven Forms and Worksheets. There is a separate worksheet for each module type. We recommend you fill these out before entering the data into the system.

1. Connect to the controller where you want to introduce direct digital control.

2. Select Edit Controller Direct Digital Control, or click the Direct Digital Control tool on the Controller toolbar. The system displays the DDC modules summary (see Figure 14-1).


Accessing the DDC Module Editors Direct Digital Control

This screen provides a list of DDC modules that have already been assigned. If you have not used DDC previously, the list is empty.

3. Choose a blank line from the list and select Add to add a DDC module to the controller. The system displays the DDC Module—Add dialog box (see Figure 14-2).

4. Define a Module name (up to 8 characters).

Figure 14-1. DDC Modules Summary

Figure 14-2. DDC Module—Add Dialog Box


Direct Digital Control Two Position Module (2-Pos)

5. Choose a Module type from the drop-down list. You have the following options:

The following pages contain descriptions of each module, the module parameters, and a sample data entry screen for each module.

Two Position Module (2-Pos)

The Two Position module is similar to an electric thermostat, but it responds much more precisely and predictably. Figure 14-3 is a sample data entry screen.

Use the following procedure to configure the Two Position Module:

1. Set the Module parameters.

✧ 2-Pos ✧ Reset

✧ PID ✧ HiLo

✧ Floating ✧ Relay

Figure 14-3. Two Position Module Editor


Two Position Module (2-Pos) Direct Digital Control

Note: The Number field refers to the Mod # that you selected on the DDC Modules screen (see Figure 14-1) and cannot be changed.

a. Enter a Name (up to eight characters) to describe the module.

b. Enter the Sample interval (1 to 255). This is the number of seconds between module outputs.

2. Set the Setpoint parameters.

a. Select a Setpoint. This is the type of input value. All DDC inputs must be defined as lines, points, or constants. An input field appears under the choices.

b. Depending on your choice in Step a, do one of the following:

✢ Line—Enter a value (1 to 64).

✢ Point—Choose a point from the drop-down list.

✢ Constant—Enter a value in engineering units.

c. If you chose Line or Point in Step a above, enter a setpoint Offset (–100 to +100). The default is zero.

If you have several modules that share a common setpoint, you can use setpoint offsets to stagger the oper-ating range of each module.

d. Enter a Differential range. This is the degree of precision for the module.

e. Enter the Low limit value. The default is zero.

This parameter defines the lower limit of the setpoint. If the value goes below this parameter, the module output goes to the failsafe command.

f. Enter the High limit value. The default is 100.

This parameter defines the upper limit of the setpoint. If the value goes above this parameter, the module output goes to the failsafe command.

3. Set the Process Variable parameters.


Direct Digital Control Two Position Module (2-Pos)

a. Select a Process Variable. All DDC process variables must be defined as lines, points, or constants. An input field appears under the choices.





c. The Filter parameter allows you to reduce the impact of rapidly changing inputs and is controller dependent. For 7700 or 7740 controllers, you may enter a value from one to five. This parameter represents the number of previous inputs to be averaged with the current input value. All other controllers allow you to select Yes or No to apply a filter that will automatically average the last five inputs with the current input.

4. Set the Output parameters.

a. Select an Output. DDC outputs must be lines or points. An input field appears under the choices.


✢ Line—enter a value (1 to 64).

✢ Point—choose a point from the drop-down list.

c. Set the Failsafe command. This action is executed when the setpoint is no longer valid or the process variable point goes to old data status. The default is Off.

Note: The same input conditions, which cause the PID module to output its control point value, cause the Two Position module to go to its failsafe condition. Refer to the chapter dealing with Direct Digital Control in TCON300, TAC I/NET Seven Technical Reference Guide, for a description of the parameters.

d. Select a Mode. This is the action when the input is higher or lower than the setpoint (plus or minus one-half the differential).


Proportional, Integral, Derivative Module (PID) Direct Digital Control

Proportional, Integral, Derivative Module (PID)

The terms proportional, integral, and derivative describe the output response of the module based on a varying set of conditions occur-ring by the process variable. The PID module editor shown in Figure 14-4, allows you to define the PID module.

Use the following procedure to configure the PID Module:


Note: The Number field refers to the Mod # that you selected on the DDC Modules screen (Figure 14-1) and cannot be changed.


Figure 14-4. PID Module Editor


Direct Digital Control Proportional, Integral, Derivative Module (PID)



a. Select a Setpoint. This is the type of input value. All PID inputs must be defined as lines, points, or constants. An input field appears under the choices.





c. If you chose Line or Point in Step a above, enter a setpoint Offset (–100 to +100). The default is zero. If you have several modules that share a common setpoint, you can use setpoint offsets to stagger the operating range of each module.

d. Enter the Low limit value. The default is zero.

This parameter defines the lower limit of the setpoint. If the setpoint goes below this value, the module output goes to the failsafe parameter.

e. Enter the High limit value. The default is 100.

This parameter defines the upper limit of the setpoint. If the setpoint goes above this value, the module output goes to the failsafe parameter.


a. Select a Process Variable. All PID process variables must be defined as lines, points, or constants. An input field appears under the choices.






Proportional, Integral, Derivative Module (PID) Direct Digital Control


4. Set the Output parameters. Refer toTCON300, TAC I/NET Seven Technical Reference Guide, for a complete description of these parameters.

a. Select an Output. PID outputs must be lines or points. An input field appears under the choices.




c. Enter the output Ramp limit value (0 to 100 percent). This is the largest change in output you want the system to issue between samples. If you set this value to zero, the output will never change.

d. Enter the output Low limit value. The default is zero.

This parameter defines the lower limit of the output value. The default is zero because the output of the module is typically in percent.

e. Enter the output High limit value. The default is 100.

This parameter defines the upper limit of the output. The default is 100 because the output of the module is typi-cally in percent.

f. Enter a value (0 to 100 percent) in the Control point (failsafe) field. The default is 50 percent of the output high limit minus output low limit.

g. Enter the Proportional band value (1 to 1,000 percent). The default is 100.


Direct Digital Control Proportional, Integral, Derivative Module (PID)

h. Enter the Reset interval value (0 to 3,600 seconds). The default is 0.

i. Enter the Rate interval value (0 to 3,600 seconds). The default is zero.

j. Select a Mode. This is the action when the input is higher or lower than the setpoint.

Note: The following tuning parameters are available in the PCU/DCU PID modules but not in the MR or UC PID modules.

k. Choose an Adaptive control from the drop-down list. This parameter defines the point address or name of the discrete point that will be used to enable/disable adaptive control.

l. Enter the Maximum bump (%) value (0 to 100). The default is five.

This parameter determines the size of the PID output step change for automatic tuning in reference to the module control point (PID).

m. Enter the Settling time (sec) (10 to 1,800). The default is 120.

This is an estimate of the time it takes for the input (process variable) to settle down after a setpoint change.

n. Enter the Maximum overshoot (%) value (0 to 100). The default is 10.

This parameter, along with target damping, controls the shape of the initial output response to a process distur-bance.

o. Enter the Target damping (%) value (1 to 75). The default is 25.

This is the desired reduction in the process variable over-shoot from the first overshoot (maximum overshoot) to the second, and so on.


Floating Module (Float) Direct Digital Control

p. Enter the Noise band (%) value (0 to 100). The default is two. This parameter, specified as a percentage of the input range, is the minimum process variable change that initiates an adaptive calculation of the module parame-ters (provided the adaptive control discrete point is equal to one).

P-only Mode of OperationThis operational mode is available in all DCU types except the EPROM versions of the 7700 and 7740 DCUs. If you did not enter a reset or rate interval in the PID module, the module functions in P-only mode (no integral or derivative corrective actions).

Floating Module (Float)

The Floating module operates much like the PID module, described above. The operation of the algorithm is the same and the entries which modify the proportional band, reset interval, and rate interval are identical. The difference between the two modules lies in the outputs to the final control element.

The output of the Float module is directed to two separate DO points as an increase command and a decrease command. The module does not know the exact position of the controlled valve or damper and assumes it was driven to the correct position. You need this module and its outputs when the final control element is controlled by a bidirectional motor. The Floating Module editor shown in Figure 14-5, allows you to define the Floating module.

Note: The same input conditions, which cause the PID module to output its control point value, cause the Floating module to stop producing any output. Refer to the chapter dealing with Direct Digital Control in TCON300, TAC I/NET Seven Technical Reference Guide, for a description of the parameters.

Use the following procedure to configure the Floating Module:



Direct Digital Control Floating Module (Float)





a. Select a Setpoint. This is the type of input value. All Floating Module inputs must be defined as lines, points, or constants. An input field appears under the choices.





Figure 14-5. Floating Module Editor



c. If you chose Line or Point in Step a above, enter a setpoint Offset (–100 to +100). The default is zero.

If you have several modules that share a common setpoint, you can use setpoint offsets to stagger the oper-ating range of each module.

d. Enter the Low limit value. The default is zero.

This parameter defines the lower limit of the setpoint. If the setpoint goes below this value, the module stops producing any outputs.

e. Enter the High limit value. The default is 100.

This parameter defines the upper limit of the setpoint. If the setpoint goes above this value, the module stops producing any outputs.


a. Select a Process Variable. All Floating module process variables must be defined as lines, points, or constants. An input field appears under the choices.






d. If you want to reduce the impact of rapidly changing inputs, enter a value (1 to 5) in the Filter field.


Direct Digital Control Floating Module (Float)

This option lets you average up to five previous input values with the current input to reduce the impact of rapidly changing inputs.

4. Set the Output parameters. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for a complete description of these parameters.

a. Select an Increase.

✢ For a DCU or PCU you may select Line or Point.

✢ For an MR you may only select Point.

✢ For a UC enter the hardware bit (0 to 7).

b. Select a Decrease.

✢ For a DCU or PCU you may select Line or Point.

✢ For an MR you may only select Point.

✢ For a UC enter the hardware bit (0 to 7).

c. Enter the Throttling range (sec) value (0 to 255). The default is zero.

This is the number of seconds it takes for the actuator to move from being fully open to fully closed and vice versa.

d. Enter the Turn-around time (sec) value (0 to 255). The default is zero.

This is the time it takes to complete a reversal in the bidi-rectional motor rotation.

e. Enter the Proportional band value (1 to 1,000 percent). The default is 100.

f. Enter the Reset interval value (0 to 3,600 seconds). The default is 0.

g. Enter the Rate interval value (0 to 3,600 seconds). The default is zero.

h. Select a Mode. This is the action when the input is higher or lower than the setpoint.

Note: The following tuning parameters are available in the PCU/DCU Floating modules but not in the MR or UC Floating modules.



i. Choose an Adaptive control from the drop-down list. This parameter defines the point address or name of the discrete point that will be used to enable/disable adaptive control.

j. Enter the Maximum Bump (%) value (0 to 100). The default is five.

This parameter determines the size of the output step change for automatic tuning in reference to the midscale position.

k. Enter the Settling time (sec) (10 to 1,800). The default is 120.

This is an estimate of the time it takes for the input (process variable) to settle down after a setpoint change.

l. Enter the Maximum overshoot (%) value (0 to 100). The default is 10.

This parameter, along with target damping, controls the shape of the initial output response to a process distur-bance.

m. Enter the Target damping (%) value (1 to 75). The default is 25.

This is the desired reduction in the process variable over-shoot from the first overshoot (maximum overshoot) to the second, and so on.

n. Enter the Noise band (%) value (0 to 100). The default is two.

This parameter, specified as a percentage of the input range, is the minimum process variable change that initiates an adaptive calculation of the module parame-ters (provided the adaptive control discrete point is equal to one).


Direct Digital Control Reset Module (Reset)

Reset Module (Reset)

The Reset module produces a primary reset schedule and modifies the results of that schedule based upon a secondary input (see Figure 14-6). The output of this module is typically used to provide a setpoint to another module and does not directly control a process. The reset schedule can reset the setpoint of a controlling module based on one or two measured inputs.

An example of this function is the process used to reset the temper-ature of a water heater according to the outside air temperature. As the outside temperature drops, the temperature of the heater must increase to maintain the water at the same temperature (the heating load increases). The two temperatures are inversely proportional to each other.

Reset control is also used to reset the discharge temperature of an HVAC unit based on the space temperature. This increases the rate of space temperature modification but does not improve control capability.

Figure 14-6. Reset Module Editor


Reset Module (Reset) Direct Digital Control

Use the following procedure to configure the Reset Module:





2. Set the Primary Input parameters.

a. Select a Primary Input type. This is the type of input value. All Reset module inputs must be defined as lines, points, or constants.

b. Enter the Input 1 and Input 2 values. These input values, in engineering units of the primary sensed variable, are the major determining factor in determining the primary output.

c. Enter the Output 1 and Output 2 values. These values define the module output in conjunction with the primary inputs.

3. Set the Secondary Input parameters.

a. Select the Secondary Input type. This is the type of input value. All Reset module inputs must be defined as lines, points, or constants.

b. Enter the Input 1 and Input 2 values. These input values, in engineering units of the secondary sensed variable, provide a second modifier for the module output.

c. Enter the Output 1 and Output 2 values. These values, in engineering units of the controlled value, offset the setpoint derived by the primary input/output schedule.

4. Set the Output parameters.

a. Select an Output. DDC outputs must be lines or points. An input field appears under the choices.


Direct Digital Control HiLo Module (HiLo)


✢ Line—enter a value (1 to 64).

✢ Point—choose a point from the drop-down list.

c. Enter the Low limit value. The default is zero.

This parameter defines the lower limit of the output value. The default is zero because the output of the module is typically in percent.

d. Enter the High limit value. The default is 100.

This parameter defines the upper limit of the output. The default is 100 because the output of the module is typi-cally in percent.

HiLo Module (HiLo)

The HiLo module provides a convenient means to extract the highest and/or lowest values from among several values. If desired, you can also accomplish this with the HIGH and LOW Boolean operators. Refer to the chapter dealing with the Calculation point extension in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about these operators.

Inputs may be either analog values such as temperature or pressure, or discrete states (i.e., true (1) or false (0)). If you need to compare more than four values, you can have one module output to another by using multiple HiLo modules. This is called cascading.

The HiLo Module editor shown in Figure 14-7, allows you to define the HiLo Module.

Use the following procedure to configure the HiLo Module:


Note: The Number field refers to the Mod # that you selected on the DDC Modules screen (see Figure 14-1) and cannot be changed.


HiLo Module (HiLo) Direct Digital Control



2. Select the High output and Low output types. DDC outputs must be lines or points. An input field appears under the choices.

Depending on your choices, do one of the following:

✧ Line—enter a value (1 to 64).

✧ Point—choose a point from the drop-down list.

3. Select Input 1, Input 2, Input 3, and Input 4 as required. These are the types of input values. All HiLo Module inputs must be defined as lines, points, or constants.

Figure 14-7. HiLo Module Editor


Direct Digital Control Relay Module (Relay)

Relay Module (Relay)

The Relay module performs multiple functions as part of overall TAC I/NET Seven DDC capabilities. As you become more familiar with TAC I/NET Seven you will discover many uses for the relay module.

In its simplest form, this module is similar to a single-pole double- throw relay (SPDT). It has an input which acts as a coil (discrete input select), a normally-closed port (DI = 0 input), a normally open port (DI = 1 input), and a common output. When used as a traditional relay the module passes the state/value from the DI = 0 port to the common output when the discrete select input value is 0. When the discrete select input is 1, the module passes the state/value of the DI = 1 port.

This module can also function in the following ways:

✦ Act as an interval time delay relay (INT)

✦ Act as a delay-before-break relay (DBB)

✦ Act as a delay-before-make relay (DBM)

Each of these relay options is described below. The Relay module editor is shown in Figure 14-8.

Figure 14-8. Relay Module Editor


Relay Module (Relay) Direct Digital Control

Use the following procedure to configure the Relay module:





2. Select the DI = 0 type. This is the state/value passed to the output by the Relay module when the discrete input is zero.

3. Select the DI = 1 type. This is the state/value passed to the output by the Relay module when the discrete input is one.

4. Set the Settings parameters.

a. Select a relay type. Choose from Standard, Interval timer, Delay before make, or Delay before break.

b. Enter the Time delay (sec) value (0 to 86,400). The default is zero.

This is the number of seconds for the Interval timer, Delay before make, and Delay before break relays.

5. Select a DI Select type. This input can be a line, a point, or a constant. 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.

6. Select an Output type. DDC outputs must be lines or points. An input field appears under the choices.

Depending on your choices, do one of the following:

✧ Line—Enter a value (1 to 64).

✧ Point—Choose a point from the drop-down list.


Direct Digital Control History

History

TAC I/NET Seven provides an on-line tuning capability for PID and Floating modules (up to four per controller). In order to acti-vate the tuning function, you must first select the PID or Floating module(s) and add them to the history record. The history func-tion allows the DCU to begin to monitor the module input and output values.

1. Choose a PID or Floating module from the DDC Modules screen.

2. Select History. The system toggles the History function between disabled and enabled each time you select the History button. When history is enabled, a Y appears in the History column of the list.

Due to the memory required for the tuning function, there is a limit of four modules that can be contained in the history record of each controller. If you need to add another module, delete an old one first.

Tuning

Tuning is the on-line, automatic adjustment of PID or Floating module parameters.

When you have added the modules you wish to tune to the History portion of the DDC editor, use the following procedure to perform the Tuning function:

1. Choose a PID or Floating module from the DDC Modules screen. The module must have the History function enabled.

2. Select Tuning. The system displays the Input Output Plot screen (see Figure 14-9).

This screen allows you to choose the following options:

✧ Manual (Man) Tune

✧ Automatic (Auto) Tune (PID only)


Tuning Direct Digital Control

✧ Input/Output (I/O) Plot

Manual TuningThe Manual Tuning editor (see Figure 14-10) displays permanent and current module parameter values and allows you to adjust the current values.

Figure 14-9. Input Output Plot

Figure 14-10. Manual Tuning Editor


Direct Digital Control Tuning

Use the following procedure to adjust the Manual Tuning parame-ters:

1. Enter a Setpoint value.

This is the value of the input point being controlled.

a. Enter the Proportional band value (1 to 1,000 percent).

b. Enter the Reset interval value (0 to 3,600 seconds).

c. Enter the Rate interval value (0 to 3,600 seconds). The default is zero.

Input/Output PlotIf you select this option, the system 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 previously. See Figure 14-9.

Automatic TuneIf you select this option, the system displays a plot similar to the Input/Output plot.

This may be a lengthy process. In this editor, the controller auto-matically drives the module output(s) to preset values or positions and calculates the P, I, and D constants for 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. By monitoring the resulting changes in the process variable input to the module, the controller automatically calculates and enters the P, I, and D constants into the module editor.


Helpful Hints for DDC Modules Direct Digital Control

Helpful Hints for DDC Modules

✦ Prepare your DDC module worksheets in TCON157, TAC I/NET Seven Forms and Worksheets, before entering module editors.

✦ Check that you have no more than one DDC module directing its output to the same line number.

✦ Build a display page, with line values displayed, to check for intermediate states or values.


C H A P T E R12

15

© 2001–2010 SchTCON299–05/10

Lighting Control

The 7780 Distributed Lighting Control Unit (DLCU) supports up to 32 lighting zones, 64 local/external lighting circuits, and 32 remote/indirect lighting circuits. You can assign each circuit to one or more zones. You must attach a Lighting Control (LC) extension to a controller point and define the lighting circuit before you can assign the circuit to a zone.

Refer to the Lighting Control extension in the chapter dealing with point extensions in TCON300, TAC I/NET Seven Technical Refer-ence Guide, for more information about lighting circuits and zones.

To use the Lighting Control functions:

1. Define the lighting circuits (see below).

2. Define the lighting zones (see page 15-6).

3. For each zone:

a. Assign the desired circuit(s) to the zone (see page 15-8).

b. Assign a time schedule to the zone (see page 15-9).

Lighting Circuits

You can define up to 96 lighting circuits. The first 64 circuits can be local/external points and the last 32 circuits can be remote/indirect DO points. The 64 local/external points can be assigned to addresses between LLSS0000 and LLSS0707. The 32 remote/indi-rect points can be assigned to addresses between LLSS0800 and LLSS1107.


Lighting Circuits Lighting Control

Adding a Lighting CircuitYou need to define lighting circuits before you can assign them to a zone. Use the following steps to add a lighting circuit to a point.

1. Connect to a 7780 DLCU.

2. If the necessary DO point has not already been defined, use the Resident I/O Points editor to define the point. Refer to Chapter 5, Point Definition and Addressing.

Note: The DO point used for a lighting circuit must have a “0” command as its first control descriptor.

3. Select Edit Controller Lighting Circuit, or click the Lighting Circuit tool on the Controller toolbar. The system displays Lighting Circuit Point Selection editor (see Figure 15-1).

The screen lists currently defined controller DO points. Each point is listed by address, class, and name. A Y in the LC column indicates that the point is defined as a lighting circuit.

Figure 15-1. Lighting Point Selection Editor


Lighting Control Lighting Circuits

4. To change the order in which the points are displayed, click Sort. The Point Sort Dialog box displays. Select Point name or Point number and click OK. The Point Selection editor displays the points in the requested sort order.

5. Choose a DO point from the list. If you choose a point that is already defined as a lighting circuit, then the Add button is not enabled and a lighting circuit cannot be added. In this case you may either modify, copy, or delete the lighting circuit.

6. Select Add. The system displays the Lighting Control - Circuit definition editor (see Figure 15-2).

7. You must now define the circuit parameters and wink source parameters for the lighting circuit you are adding. Refer to “Circuit Parameters” on page 15-4 and “Wink Source” on page 15-4.

Figure 15-2. Lighting Control - Circuit Definition Editor


Lighting Circuits Lighting Control

Note: The Zone Map section of this screen is for informational purposes only and shows the zones to which this lighting circuit is assigned. Activating or deactivating zones from this screen has no affect. Refer to “Circuit Assignments” on page 15-8 for procedures on how to add a lighting circuit to a lighting zone.

8. Select OK to close the Lighting Control - Circuit definition editor (Figure 15-2) and return to the Point Selection editor (Figure 15-1).

9. Select Close to close the Point Selection editor.

Circuit Parameters

From the lighting circuit definition editor (Figure 15-2), define circuit parameters for the lighting circuit as follows:

1. Set the Delay before off parameter (0–127). This is the number of minutes that the point will remain On after the wink cycle ends. When the wink cycle is over and the delay duration expires, the point switches Off.

2. Set the On duration parameter (1–255). This is the number of seconds used for the On portion of the wink cycle.

3. Set the Off duration parameter (0.5–2.0). This is the number of seconds used for the Off portion of the wink cycle.

4. Set the Wink cycles parameter (0–16). This is the number of times the point winks on and off.

Wink Source

From the lighting circuit definition editor (Figure 15-2) choose the source(s) that will initiate the wink function. Your choices are:

✦ Manual host

✦ Manual - HHC

✦ Automatic time scheduling

✦ Demand limit/load shedding

✦ Event sequence

✦ Building manager

✦ Override input


Lighting Control Lighting Circuits

Click in the check box to toggle between activated () and deacti-vated () for each source.

Modifying a Lighting CircuitModifying a lighting circuit is similar to adding a circuit. Use the same procedure as described in “Adding a Lighting Circuit” on page 15-2 except select Modify rather than Add.

Deleting a Lighting CircuitLighting circuits are deleted by removing the Lighting Control (LC) extension from the controller point. Use the following proce-dure to delete a lighting circuit.

1. Select Edit Controller Lighting Circuit, or click the Lighting Circuit tool on the Controller toolbar. The system displays a Point Selection editor as shown in Figure 15-1.


2. Choose a point from the list. The point must have a Y in the LC column.

3. Select Delete. The Delete confirmation dialog box displays.

4. Select Yes to delete the lighting circuit.

Copying a Lighting Circuit1. Select Edit Controller Lighting Circuit, or click the

Lighting circuit tool on the Controller toolbar. The Point Selection editor displays, as shown in Figure 15-1.


2. Choose a point from the list. The point must have a Y in the LC column.

3. Select Copy. The Extension Copy dialog box displays, as shown in Figure 15-3.


Lighting Zones Lighting Control

4. Choose a target point from the drop-down list. Only DO points that are not defined as lighting circuits are listed.

5. Select OK to return to the point selection screen. You may now modify the new lighting circuit as necessary. Refer to “Modifying a Lighting Circuit” on page 15-5.

Lighting Zones

Once you have defined the lighting circuits, you may assign these circuits to zones. Lighting zones can be assigned to DO point addresses between LLSS1200 and LLSS1507.

Adding a Lighting ZoneUse the following steps to define lighting zones and assign lighting circuits.

1. Connect to a 7780 DLCU.

2. If the necessary DO point has not already been defined, use the Resident I/O Points editor to define the point. Refer to Chapter 5, Point Definition and Addressing.

Note: The DO point used for a lighting zone must have a “1” command as its first control descriptor.

3. Select Edit Controller Zone Definition, or click the Zone Definition tool on the controller toolbar. The Point Selection editor displays.

Figure 15-3. Extension Copy Editor


Lighting Control Lighting Zones

The screen lists currently defined controller DO points with addresses between LLSS1200 and LLSS1507. Each point is listed by address, class, and name. A Y in the LZ column indi-cates that the point is defined as a lighting zone.

4. Choose a DO point from the list. If you choose a point that already has a lighting zone extension, then the Add button is not enabled and a lighting zone cannot be added. In this case you may either modify, copy, or delete the lighting zone.

5. Select Add. The Lighting Control - Zone editor displays, as shown in Figure 15-4.

6. Choose an Input point from the drop-down list. This is the address of a pre-existing DI point that will be used to override the zone time schedule and energize all circuits in the lighting zone.

7. Choose an Input type from the drop-down list. The options for this parameter are: Single-pushbutton, Dual-pushbutton, or Latched.

8. Choose an Override type from the drop-down list. This parameter is only used when the Input type parameter is set to Single- or Dual-pushbutton. The options for this param-eter are: Permanent or Timed.

9. Set the Override time. This parameter is only used when the Override type parameter is set to Timed. Choose a setting from 0 to 60 minutes.

Figure 15-4. Lighting Zone Parameters Editor



10. Select Circuit to assign lighting circuits to this zone. Refer to “Circuit Assignments” on page 15-8.

11. Select ATS to define time schedules for this zone. Refer to “Automatic Time Schedule (ATS)” on page 15-9.

12. When you are finished, select OK.

Circuit Assignments

Use the following procedure to assign lighting circuits.

1. If you select Circuit from the Lighting Zone Parameters editor, the Lighting Control - Circuit Assignments editor displays (see Figure 15-5).

Use this screen to assign circuits to the currently selected zone. This screen displays the currently defined circuits by number (1–96), DO point address, and name. You defined the points in the Resident I/O Points editor. You defined the lighting circuit parameters for these points earlier in this chapter.

2. Assign circuits by selecting circuit names with the mouse to toggle between [X] (assigned) and [ ] (not assigned) in the Select field. A sample circuit assignment screen is shown in Figure 15-5.

Figure 15-5. Circuit Assignment Editor



You may also use the All Yes and All No buttons to quickly select which circuits are assigned to the zone.

3. Select Close to return to the lighting zone parameters window.

Automatic Time Schedule (ATS)

If you select ATS, the system displays a time scheduling edit screen similar to that shown in the Time Scheduling editor. However, the only actions available in this screen are ON and OFF. As with the TS editor, you can select actions to begin and end at a specific time, at sunrise, or at sunset. You can define temporary schedules and assign schedules to special days. Any changes you make here are also reflected in the Time Scheduling editor. Any changes you make in that editor are reflected here.

You can create the schedule here or use one you already created in the Time Scheduling editor. If you create it here, it is automatically defined as Independent. If you use a schedule you defined in the TS editor, it must be defined as an Independent schedule. Master and Slave time schedules are valid in the Lighting Control editor but cannot be edited from the LC editor. A sample screen is shown in Figure 15-6.

Figure 15-6. Time Schedule Editor



Modifying a Lighting ZoneModifying a zone is similar to adding a zone. Use the same proce-dure as described in “Adding a Lighting Zone” on page 15-6 except select Modify rather than Add.

Deleting a Lighting ZoneUse the following procedure to delete a lighting zone.

1. Select Edit Controller Zone Definition, or click the Zone Definition tool on the Controller toolbar. The Point Selec-tions editor lists currently defined controller DO points. Each point is listed by address, class, and name. A Y in the LZ column indicates that a lighting zone has been added to the point.

2. Choose a point from the list. The point must have a Y in the LZ column.

3. Select Delete. The Delete confirmation dialog box displays.

4. Click Yes.

Copying Lighting Zones1. Select Edit Controller Zone Definition, or click the Zone

Definition tool on the Controller toolbar. The Point Selection editor lists currently defined controller DO points. Each point is listed by address, class, and name. A Y in the LZ column indicates that a lighting zone has been added to the point.

2. Choose a DO point from the list. The point must have a Y in the LZ column.

3. Select Copy. The system displays the Extension Copy dialog box, similar to that shown in Figure 15-3.

4. Choose a target point from the drop-down list. Only DO points that are not already defined as lighting zones are listed.

5. Select OK. The system now displays the window similar to that shown in Figure 15-7.



6. Choose the zone parameters to be included in the copy. If you select No for all parameters, the lighting zone will not be copied.

7. Select OK to return to the point selection screen. You may now modify the new zone as necessary. Refer to “Modifying a Lighting Zone” on page 15-10.

Figure 15-7. Zone Parameters Editor


C H A P T E R22

16

© 2001–2010 SchTCON299–05/10

Unitary Control

Unitary controllers (UC) and their associated interface let TAC I/NET distribute intelligence to the level of the terminal unit. The unitary controller interface (UCI) acts as an interface between the TAC I/NET 7700 controller LAN and the TAC I/NET UC network. The controller LAN operates as a token passing protocol at 9600 baud or 19,200 baud and the UC network operates as a scan-ning/polling protocol operating at 9600 baud.

The UCI is an intermediate holding area for all database and appli-cations parameters for up to 32 unitary controllers. The UCI also lets you globalize data, collect data for SevenTrends and trending, and perform save and restore tasks. The UCI lets you perform all database development on-line without being physically connected to the remote UCs.

Configuring the Unitary Controller Interface

1. Connect to the UCI exactly as you do any other controller by connecting through the system and selecting the appropriate options until you are connected to the desired 7760 controller (UCI).

2. Select Edit Controller Configuration, or click the Config-uration tool on the Controller toolbar. The system displays the DCU configuration screen. This screen is identical to the configuration/status screen used by other controllers. Refer to Chapter 4, Controller Configuration, for information on configuring this controller.


Configuring the Unitary Controller Unitary Control

Configuring the Unitary Controller

1. Select Edit Controller UC Configuration, or click the UC Configuration tool on the Controller toolbar. This option is available only when you are connected to a 7760 controller (UCI). The system displays the editor shown in Figure 16-1.

2. Choose a type for each UC address. The default type is Internal.

3. Select OK to accept the changes and exit the editor.

You may want to use the Unitary Control editor (described below) first and define the specific parameters and points for the UC while the type is still defined as Internal (UCI not communicating with the UCs). You can then return to this editor and change the type from Internal to the appropriate type, and exit the editor to begin control, once the UCI is communicating with the UCs.

The system displays the addresses of all the UCs currently assigned to this UCI.

Figure 16-1. UC Configuration Editor


Unitary Control Creating the UCI Database

Creating the UCI Database

Point database entries for each UC are made as follows:

1. Connect to a UCI

2. Select Edit Controller Resident I/O Points, or click the Resident I/O Point tool on the Controller toolbar.

3. Refer to Chapter 5, Point Definition and Addressing, for the mechanics of database entry.

The Parent PointThe 7760 is the only controller that uses the term “parent point”. A parent point is nothing more than the AO or DO point to which you add a UC extension: VAV, AHU, PID, FLT, or HPMP. The func-tion of the extension is directly controlled by the parent point. (0 or 1 for a DO point and the setpoint for an AO point.) All parent points must be internal or external, DO or AO points. If it is helpful, you could think of the point to which you add any other extension such as Runtime or Consumption as the parent point of that extension. The parent point is usually assigned the first output address in the UC (LLSSPP00), but this is not a requirement.

UC Copy

This function copies the data in one UC to another UC. The data copied using this function consists of Resident I/O point data, station parameters, and extensions.

This function is useful if your site is adding one or more UCs whose databases are similar to that of an existing UC.

Perform a UC copy as follows:

1. Connect to a UCI.


3. Choose a source UC point to be copied from the point list.


UC Copy Unitary Control

4. Select UC Copy. This option only appears when you are connected to a 7760 controller (UCI). This function lets you copy database and extension programs from one UC to another UC.

The system displays the UC (MCU) Copy screen (see Figure 16-2).

5. Define a point address for the new UC point using the Station and Point spindials.

6. Select OK to add the new UC point.

When the copy is complete, the editor displays a list of UC points with the new UC added. The new points contain the same extensions as the points in the source UC. The only thing not duplicated is the point names. You may use the Resident I/O Points editor to name the new points.

Activating the New UC When you have completed a UC copy, you may activate the new UC by accessing the UC Configuration editor and declaring the UC type as VAV, AHU, HPMP, or General. This causes the UCI to download the new database to the UC and initiate its operation.

Figure 16-2. UC Copy Screen


Unitary Control Unitary Control Parameters

Unitary Control Parameters

Once you have defined several UC resident points in the Resident I/O Points editor, return to the main menu and select Edit Controller Unitary Control, or click the Unitary Control tool on the Controller toolbar.

This option only appears when you are connected to a 7760 (UCI). The Unitary Control editor displays (see Figure 16-3).

This screen lists all possible parent points (AO and DO) that can have a UC extension appended to them.

1. Choose a point from the list. The point should not have a Y in the UC column.

2. Select Add. The system displays the UC Extension screen (see Figure 16-4).

Figure 16-3. Unitary Control Screen


Unitary Control Parameters Unitary Control

3. Choose a UC extension type from the drop-down list. If you selected an AO point in the Unitary Control screen, your only options are PID and FLT. If you selected a DO point, your options are VAV, AHU, PID, FLT, and HPMP.

4. Select OK. The system displays the editor screen corre-sponding to the UC extension type you selected.

Since the control algorithm has already been written, tested, and is resident in the UC EPROM memory, all you need to do is define the parameters and identify sources and destinations to begin control-ling the unit.

From the UC Parameter Editor, you must now define the parame-ters. The following pages provide sample editor screens and general parameter descriptions for the VAV, AHU, and HPMP controller types. Refer to “DDC Damper Control” on page 16-18 for a description of the parameter entries for PID and FLT controller types. Some of the parameters are common to all extension types and some are specific to a particular UC extension.

For detailed descriptions of all UC parameters, refer to TCON300, TAC I/NET Seven Technical Reference Guide.

VAV ParametersA sample UC Parameter Editor screen for the Variable Air Volume (VAV) controller type is shown in Figure 16-5.

Figure 16-4. UC Extension Screen



The VAV UC Parameter Editor screen provides data entry fields for four types of parameters:

✦ Setpoints

✦ Inputs and Outputs

✦ Overrides

✦ Delays and Offsets

Note: When making entries in the VAV UC Parameter Editor, refer to TCON300, TAC I/NET Seven Technical Reference Guide, for descriptions of each parameter and instructions on determining the correct entries for your specific application.

Setpoints

For each setpoint, enter a number between zero and 127.5 for the setpoint target and a number between zero and 10 for the differen-tial. You may use a 0.5 decimal entry for all setpoint targets and differentials. If you enter a decimal value less than 0.5, the system

Figure 16-5. VAV UC Parameter Editor Screen



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.

Complete the Setpoints section in the VAV UC Parameter Editor by performing the following steps:

1. Enter a Target Setup/setback value for Cooling.

2. Enter a Differential Setup/setback value for Cooling.

3. Enter a Target Setup/setback value for Heating.

4. Enter a Differential Setup/setback value for Heating.

5. Enter a Target Economy value for Cooling.

6. Enter a Differential Economy value for Cooling.

7. Enter a Target Economy value for Heating.

8. Enter a Differential Economy value for Heating.

9. Enter a Target Normal value for Cooling.

10. Enter a Differential Normal value for Cooling.

11. Enter a Target Normal value for Heating.

12. Enter a Differential Normal value for Heating.

Inputs and Outputs

The input and output parameters instruct the UC where to find the information it needs to function.

Complete the Inputs and Outputs section in the VAV UC Param-eter Editor by performing the following steps:

1. Select a point address, if applicable, in the Space tempera-ture drop-down list.

2. Select a point address, if applicable, in the Temperature setpoint drop-down list.

3. Select a point address, if applicable, in the Fan drop-down list.

4. Select a point address, if applicable, in the Central plant heat drop-down list.



5. Select a point address, if applicable, in the Stage 1 heating drop-down list.



Overrides

There are several separate override options available for the VAV UC controller type.

Complete the Overrides section in the VAV UC Parameter Editor by performing the following steps:

1. Select a point address, if applicable, in the Setpoint adj. drop-down list.

2. In the Range field, enter a value between 0 and 10 to limit the range of a setpoint adjustment knob on a CSI sensor. This limits the adjustment to plus and minus the value entered.

3. Select a point address, if applicable, in the Timed override drop-down list.

4. Select a point address, if applicable, in the Indicator drop-down list.

5. In the Duration (min) field, enter a value between 0 and 254 for the number of minutes that the UC will energize the Timed override indicator.

6. Select a point address, if applicable, in the Economy override drop-down list.

7. Select a point address, if applicable, in the Damper override drop-down list.

Delays and Offsets

Complete the following Delays and Offsets parameters.

1. Activate the appropriate radio button (Off, On, or Auto) for Cooling Control.



2. Activate the appropriate radio button (Off, On, or Auto) for Heating Control.

3. In the Heater 1 activation delay (sec) field, enter a value between 0 and 254 seconds.

4. In the Heater 2 setpoint offset (deg) field, enter a value between 1 and 10 degrees.


6. Select OK to accept all changes in the VAV UC Parameter Editor screen.

AHU ParametersA sample UC Parameter Editor screen for the Air Handling Unit (AHU) controller type is shown in Figure 16-6.

Figure 16-6. AHU UC Parameter Editor



The AHU UC Parameter Editor screen provides data entry fields for four types of parameters:

✦ Setpoints


✦ Overrides


Note: When making entries in the AHU UC Parameter Editor, refer to TCON300, TAC I/NET Seven Technical Reference Guide, for descriptions of each parameter and instructions on determining the correct entries for your specific application.

Setpoints

For each setpoint, enter a number between zero and 127.5 for the setpoint target and a number between zero and 10 for the differen-tial. You may use a 0.5 decimal entry for all setpoint targets and differentials. 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.

Complete the Setpoints section in the AHU UC Parameter Editor by performing the following steps:


2. Enter a Differential Setup/setback value for Cooling.













Inputs and Outputs


Complete the Inputs and Outputs section in the AHU UC Param-eter Editor by performing the following steps:


2. Select a point address, if applicable, in the Fan drop-down list. Activate the appropriate Fan radio button (On or Auto).

3. Select a point address, if applicable, in the Stage 1 cooling drop-down list.






9. Select a point address, if applicable, in the Damper control drop-down list.

Overrides

There are several separate override options available for the AHU UC controller type.

Complete the Overrides section in the AHU UC Parameter Editor by performing the following steps:









7. In the Warmup/cooldown (min) field, enter a value between 0 and 254 minutes.

Delays and Offsets

Complete the Delays and Offsets section in the AHU UC Param-eter Editor by performing the following steps:

1. In the Cooling delay stage 1 field, enter a value between 0 and 254.

2. In the Cooling delay stage 2 field, enter a value between 0 and 254.

3. In the Cooling stage 2 setpoint offset field, enter a value between 1 and 10.

4. In the Cooling stage 3 setpoint offset field, enter a value between 1 and 10.

5. In the Heating stage 2 setpoint offset field, enter a value between 1 and 10.

6. In the Heating stage 3 setpoint offset field, enter a value between 1 and 10.

7. Click on the OK button to accept all changes in the AHU UC Parameter Editor screen.



HPMP ParametersA sample UC Parameter Editor screen for the Heat Pump (HPMP) controller type is shown in Figure 16-7.

The HPMP UC Parameter Editor provides data entry fields for four types of parameters:

✦ Setpoints


✦ Overrides


Note: When making entries in the HPMP UC Parameter Editor, refer to TCON300, TAC I/NET Seven Technical Reference Guide, for

Figure 16-7. HPMP UC Parameter Editor



descriptions of each parameter and instructions on determining the correct entries for your specific application.

Setpoints

For each setpoint, enter a number between zero and 127.5 for the setpoint target and a number between zero and 10 for the differen-tial. You may use a 0.5 decimal entry for all setpoint targets and differentials. 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.

Complete the Setpoints section in the HPMP UC Parameter Editor by performing the following steps:


2. Enter a differential Setup/setback value for Cooling.











Inputs and Outputs




Complete the Inputs and Outputs section in the AHU UC Param-eter Editor by performing the following steps:


2. Select a point address, if applicable, in the Fan drop-down list. Activate the appropriate Fan Control radio button (On or Auto).

3. Select a point address, if applicable, in the Damper control drop-down list.

4. Select a point address, if applicable, in the Reversing valve drop-down list.

5. Select a point address, if applicable, in the Compressor 1 drop-down list.



8. Select a point address, if applicable, in the Heater strip 1 drop-down list.



Overrides

There are several separate override options available for the HPMP UC controller type.

Complete the Overrides section in the HPMP UC Parameter Editor by performing the following steps:









7. In the Warmup/cooldown (min) field, enter a value between 0 and 254 minutes.

Delays and Offsets

Complete the Delays and Offsets section in the AHU UC Param-eter Editor by performing the following steps:

1. In the Compressor 1 delay (sec) field, enter a value between 0 and 254 seconds.

2. In the Compressor 2 delay (sec) field, enter a value between 0 and 254 seconds.

3. In the Compressor 2 setpoint offset (deg) field, enter a value between 1 and 10 degrees.

4. In the Compressor 3 setpoint offset (deg) field, enter a value between 1 and 10 degrees.




8. Select OK to accept all changes in the HPMP UC Parameter Editor screen.


DDC Damper Control Unitary Control

DDC Damper Control

The VAV, AHU, and HPMP UCs can provide direct digital control for accurate control of roof top or small built-up AHU dampers. You may use either a PID extension with a PWM control output or a FLT (floating) extension with dual pulsed outputs for bi-direc-tional electric damper operators.

PID ParametersThe PID UC Parameter Editor (see Figure 16-8) provides data entry fields for three sets of parameters:

✦ Setpoint

✦ Input

✦ Output

Note: When making entries in the PID UC Parameter Editor, refer to TCON300, TAC I/NET Seven Technical Reference Guide, for descriptions of each parameter and instructions on determining the correct entries for your specific application.

Figure 16-8. DO-PID Editor


Unitary Control DDC Damper Control

Setpoint

Enter a setpoint Value for a DO point. This field is not displayed if you are configuring an AO point. AO points use the setpoint of their parent point.

Input

Complete the Input section in the PID UC Parameter Editor by performing the following steps:

1. Select a point address, if applicable, in the Process variable drop-down list.

2. In the Filter samples field, enter a value between 0 and 5.

3. Enter a value in the Low limit field.

4. Enter a value in the High limit field.

Output

Complete the Output section in the PID UC Parameter Editor by performing the following steps:

1. Select a point address, if applicable, in the Variable drop-down list.

2. In the Output ramp limit (%) field, enter a value between 0 and 100 percent.

3. Enter a value in the Output low limit field.

4. Enter a value in the Output high limit field.

5. In the Control point limit (%) field, enter a value between 0 and 100 percent.

6. In the Proportional band field, enter a value between 0 and 1000.

7. In the Reset interval (sec) field, enter a value between 0 and 3600 seconds.

8. In the Rate interval (sec) field, enter a value between 0 and 3600 seconds.


DDC Damper Control Unitary Control

9. Activate the appropriate Mode radio button (Direct or Reverse).

10. Select OK to accept all changes in the PID UC Parameter Editor screen.

Float (FLT) ParametersThe Floating Module (FLT) UC Parameter Editor screen (see Figure 16-9) provides data entry fields for three sets of parameters:

✦ Setpoint

✦ Input

✦ Output

Note: When making entries in the FLT UC Parameter Editor, refer to TCON300, TAC I/NET Seven Technical Reference Guide, for descriptions of each parameter and instructions on determining the correct entries for your specific application:

Setpoint

Enter a setpoint Value for a DO point. This field is not displayed if you are configuring an AO point. AO points use the setpoint of their parent point.

Figure 16-9. DO Floating Editor


Unitary Control DDC Damper Control

Input

Complete the Input section in the FLT UC Parameter Editor by performing the following steps:

1. Select a point address, if applicable, in the Process variable drop-down list.

2. In the Filter samples field, enter a value between 0 and 5.

3. Enter a value in the Low limit field.

4. Enter a value in the High limit field.

Output

Complete the Output section in the FLT UC Parameter Editor by performing the following steps:

1. In the Increase field, enter a value between 0 and 7.

2. In the Decrease field, enter a value between 0 and 7.

3. In the Throttling range (sec) field, enter a value between 0 and 320 seconds.

4. Enter a value in the Turn-around time (sec) field.

5. In the Proportional band field, enter a value between 0 and 1000.

6. In the Reset interval (sec) field, enter a value between 0 and 3600 seconds.

7. In the Rate interval (sec) field, enter a value between 0 and 3600 seconds.

8. Activate the appropriate Mode radio button (Direct or Reverse).

9. Select OK to accept all changes in the FLT UC Parameter Editor screen.


UC Tips Unitary Control

UC Tips

1. Define and enter your database with the UC address defined as Internal in the UC Configuration editor as described above.

2. Define each individual UC using the Unitary Control editor as described above.

3. Create a graphic page to resemble the specific UC Editor screen. Define the point addresses and types in the static portion of the graphic page and place the point values appro-priately.

4. When you finish defining the parameters, perform a Station Save.

5. Return to the UC Configuration editor and change the UC type from Internal to VAV, AHU, HPMP, or GENERAL.

6. Perform a Station Restore to download the database from the TAC I/NET Seven host PC to the UCI and ultimately to the UC.

Note: Failure to perform the last two items listed above causes your graphic to display “????” in each live data position. The outputs on the UC may also fail to work as programmed.


C H A P T E R106

17

© 2001–2010 SchTCON299–05/10

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.

The Access Control side of TAC I/NET Seven requires an interface between itself and the energy management controllers. The SLI (SubLAN Interface) provides this communication gateway between the controller LAN on one side and the door processor LAN on the other side. Common SLIs are the 7791 Door Processor Interface (DPI), 7793 Micro Control Interface (MCI), or the 7798 I/SITE LAN. Access control devices in the TAC I/NET Seven system consist of Door Processor Units (DPU7910, DPU7920, SCU1284, and OP5 arming terminals), Discrete Input Units (DIU7930 and SCU1200), and Discrete Input Monitoring and Output Control Units (DIO7940 and SCU1280). The SLI passes information between the controller LAN and the Door Processor LAN.

In the current version of the DPI, the DPUs operate on a SubLAN connected to channel A of a DPI. The channel may contain up to 32 DPU controllers. The DPI appears on controller LANs as a Distributed Control Unit (DCU). The DPI maintains the complete database and control parameters for up to 32 DPU, DIO, or DIU controllers connected to its SubLAN port. The DPI supports the definition of internal points with all of the extension capabilities typical of the PCU7716.

The MCI connects to two SubLANs, one on channel A and another on channel B of the MCI. Each channel may contain up to 32 DPU, MR, ASC, DIO, or DIU controllers. The MCI supports the defini-tion of internal points with all of the extension capabilities typical of the PCU7716.

The 7798 I/SITE LAN and 7798C can support up to 32 MRs, ASCs, DPUs, SCUs, or any combination on a subLAN. With the 7798C, up to four OP5 arming terminals can also connect to the subLAN.


Access Control Editors Access Control

The 7798 and 7798C also support internal points with all of the extension capabilities typical of the 7793 MCI. The internal points are defined only for point addresses not currently used by subcon-trollers.

The SLI, DPUs, and SCUs comprise the Access Control element of the TAC I/NET Seven integrated system. Through the SLI and DPUs, SCUs, DIOs, or DIUs you may control, or restrict, access to various areas of your facility. Using Access Initiated Control you may tie access control events from DPU/SCU readers to the Facility Management side of TAC I/NET Seven.

Refer to the section on Access Control in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Access Control Editors

The following Access Control editors are available within TAC I/NET Seven:

✦ DPU Configuration (from controller)

✦ Doors (from host or controller)

✦ Elevator (from controller)

✦ Key/card Translation (from host)

✦ Personnel Schedules (from host or controller)

✦ Tenants (from host)

✦ Groups (from host)

✦ Individuals (from host)

✦ Options (from host)

✦ Access Initiated Control (from host or controller)

✦ Recycle Bin

Access Control Order of Operations

You must observe the following order of operations when performing access control database entry:


Access Control Recycle Bin

1. Configure the DPU/SCU.

2. Define the DPI/DPU/SCU Station parameters. (Refer to Chapter 2, Setup and Network Configuration.)

3. Add Door Points in the Resident I/O Points editor. (Refer to Chapter 5, Point Definition and Addressing.)

4. Save doors in the Network Configuration editor. (Refer to Chapter 2, Setup and Network Configuration.)

5. Define the Doors in the Door Extensions editor.

6. Define Door Mode Schedules.

7. Define Personnel Schedules.

8. Define Tenants.

9. If desired, translate large key/card numbers. This allows you to use smaller numbers in your access control database.

10. Define Groups.

11. Define Individuals.

12. Implement Elevator Control.

Recycle Bin

When enabled in the Options editor (see “Options” on page 17-87), the access control 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.

Note: Access to the Recycle Bin editor is restricted to users with proper permissions. 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 Chapter 9, Passwords, for more information about passwords and permissions.


Recycle Bin Access Control

Access the recycle bin by selecting Access Recycle Bin from TAC I/NET Seven’s main menu. The system displays the Recycle Bin (see Figure 17-1).

Each record listed in the recycle bin contains the following infor-mation:

✦ Deleted — The date and time this record was deleted.

✦ Tenant — The tenant number for this record.

✦ Type — The type (tenant, group, individual) of the deleted record.

✧ Tenant and group records include the name of the tenant or group.

✧ Individual records include the tenant number and indi-vidual number.

Restoring Records from the Recycle BinRestore deleted records by highlighting the record in the recycle bin and selecting Recover. The restore operation recreates an active record from the information stored in the recycle bin. Only a single record at a time can be restored. However, when you restore a

Figure 17-1. Recycle Bin


Access Control Recycle Bin

deleted tenant, any groups and individuals that were defined for that tenant are also restored. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for more information about deleting and restoring access control records.

Note: When you recover a deleted Group, non of its original links to indi-viduals are restored. Therefore, individuals who were a member of the group before it was deleted, will not automatically become a member of the group again when it is recovered. Instead, you must manually reassign the group to individuals as necessary.

Restoring a record from the recycle bin is much like adding a new record. The system displays the Add dialog that corresponds with the record type that is being restored. This dialog will already contain the or individual number or the group name of the record being restored. You have the option of accepting the default setting or changing it. When you select OK to proceed, the system validates the entry and then displays the appropriate editor with informa-tion retrieved from the recycle bin record already filled in.

Purging RecordsYou 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 using the Purge button.

✦ Use the Options editor (see “Options” on page 17-87) to 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.

✦ Use the Options editor (see “Options” on page 17-87) to 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.


DPU/MCU Configuration Access Control

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/MCU Configuration

This editor lets you define which devices (DPU, DIO, DIU, MR, ASC) are currently connected to the SLI ports.

1. There is a slightly different procedure if you are connecting through a DPI or MCI. If you are connecting through a 7791 DPI, perform Step a. If you are connecting through a 7793 MCI or 7798 I/SITE LAN, perform Step b.

a. Select Edit Controller DPU Configuration, or click the DPU Configuration tool from the Controller toolbar. The system displays the DPU Configuration editor. This screen is similar to the MCU Configuration editor, shown in Figure 17-2.

This editor lists all 32 point addresses for the controller to which you are currently connected. For example, if you are connected to controller #22, the editor lists addresses 2200 through 2231.

b. Select Edit Controller MCU Configuration, or click the MCU Configuration tool on the Controller toolbar. The system displays the MCU Configuration editor (see Figure 17-2).

An MCI is a two-station device that allows a maximum of 64 subLAN devices (32 per station). This editor lists all 64 point addresses for the stations to which you are currently connected. For example, if you are connected to stations #14 and #15, the editor lists addresses 1400 through 1431 and 1500 through 1531.

2. Using the spindials, choose the type of device that will be located at each address.

✧ Internal – there is no controller at this address to poll.


Access Control Doors

✧ DPU – poll the DPU7910A, DPU7920, SCU1284, or OP5 Arming Terminal at this address.

✧ DIO – poll the DIO7940 or SCU1280 at this address.

✧ DIU – poll the DIU7930 or SCU1200 at this address (and second address for a two station configuration).

✧ MR – poll the Micro Regulator at this address. (MR is not available on the DPI7791 controller.)

✧ ASC – poll the Applications Specific Controller (ASC) at this address. (ASC is not available on a DPI7791.)

3. Select OK to exit this procedure.

Doors

The door selection editor lets you add, modify, copy, or delete door access control extensions in your system. This is necessary for any point that will be associated with a door or OP5 arming terminal.

Figure 17-2. MCU Configuration Editor

Note: This dialog may also include a button labeled Station, Station 1, or Station 2. Refer to TCON302, TAC I/NET Seven System Troubleshooting Guide, for more information.


Doors Access Control

Note: Changes made through the door editor generate a “door edit” audit trail message. Refer to the section on Audit Trail Messages in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

1. Select Access Doors, or click the Doors tool on the Access toolbar. The system displays the Door Selection Summary (see Figure 17-3).

Note: The Access Doors command will cause this editor to display all of the points in the TAC I/NET Seven system that are eligible to be door points (see below for criteria). If you wish to see only the eligible points on the connected controller, use the Edit Controller Doors command to access this editor.

The Door Selection Summary lists currently defined controller points that meet the following criteria:

✧ The bit offset defined in the point address must be either 08 or 09 (i.e., the first or second door point in the DPU/SCU, respectively).

✧ The point type must be set to DO.

✧ The point class must be set to internal.

Figure 17-3. Door Selection Summary



✧ The three-state output parameter must be enabled.

Note: In addition to meeting door point criteria, the points must also have been saved in the Network Configuration Editor.

If the point meets all the criteria described above, you may add an access control extension (i.e., door extension) to the point from the Door Selection Summary.

Each point is listed by address and name. A Y in the A/C column indicates that an access control extension has been added to the point.

2. Select a door point from the summary list.

If you choose a point that already has an access control exten-sion, then the Add button is not enabled. In this case you may either modify, copy, or delete the door access control exten-sion.

Adding a Door ExtensionAdd a door extension to a point to configure the point as a typical door or to configure it as an OP5 arming terminal.

1. Click Add to define a new door access control extension. The system displays the Door Extensions editor (see Figure 17-4).

The fields and options displayed within this editor will vary, depending on the firmware version installed in the DPU/SCU/OP5.

The parameters within this editor are described in the chapter on Access Control in TCON300, TAC I/NET Seven Technical Reference Guide.

2. Define the Reader Parameters for the door, as follows:

a. Choose a Reader type from the drop-down list. This parameter specifies which reader type to associate with the chosen door point.

For an OP5 Arming Terminal, set this parameter to “Keypad only.”



Note: If you select a custom reader type, the selected reader type must match the selection for AC Reader Port in the active configuration. Refer to the section on TAC I/NET Seven Configuration in TCON157, TAC I/NET Forms and Worksheets Getting Started.

b. For configuring a PIN pad, one of the following parame-ters will appear in this editor depending on the version of firmware loaded in the door controller:

✢ PIN Pad – This option appears when the door controller uses firmware prior to version 3.18. By default, the PIN Pad option is greyed out. It becomes available when you set the Reader Type to “I/DISC” or “Wiegand 66” in the step above (Wiegand 26 and

Figure 17-4. Door Extensions Editor



Wiegand 32 readers always have an implied PIN pad if the door's “PIN Enable” or “Sec/PIN” mode schedule is active).

Activate () the PIN Pad option if a PIN pad will be used to control access at the chosen door point.

✢ PIN Type – This parameter appears when the door controller uses firmware version 3.18 or later. By default, the PIN Type parameter is greyed out. It becomes available when you set the Reader Type to I/DISC, Wiegand 26/32/66, Custom Wiegand, or Keypad only.

Use the PIN Type drop-down list to specify whether or not a PIN pad is to be used at the door. By default, this parameter is set to None. To configure this door to use a PIN pad, specify the type of PIN pad being used; either 8-bit or 26-bit. Be aware that user-defined PIN pad functions require an 8-bit PIN pad. An OP5 arming terminal also requires that you set this parameter to “8-bit.”

When you configure the door to use a PIN pad, a person attempting to gain access through the door will be required to enter a valid PIN whenever the door is oper-ating in the “PIN enable” or “Sec/PIN” mode.

c. If the door controller is loaded with firmware version 2.20 or later, a PIN Message Enable option appears in this editor. This option specifies whether entry and exit transaction messages will indicate that a PIN was used.

By default, the PIN Message Enable option is greyed out. It becomes available when you configure the door to use a PIN pad, as described in Step b.

Note: The “PIN message enable” option is automatically deactivated if you select a reader type that does not support PIN pads. If you then select a reader type with PIN pad support, you must manually activate this option again.



d. If the door controller is loaded with firmware version 2.20 or later, a PIN retry count parameter appears in this editor. By default, the PIN retry count parameter is greyed out. It becomes available when you configure the door to use a PIN pad, as described in Step b.

The PIN retry count indicates the number of times (0–3) 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.

An entry of zero (0) indicates zero retries; a Denied - PIN message will be generated whenever an incorrect PIN is entered. An entry of 1 indicates one retry: the user may attempt to enter a correct PIN a total of two times (the original attempt plus one retry) before the message is generated.

Caution: In the following step, a Doors mode schedule of “Lock” overrides the entry of “Anytime” for the Exit Reader parameter.

e. Choose an Exit reader setting from the drop-down list. This parameter determines whether or not an exit reader will be used with the chosen door point and specifies the type of exit reader.

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” or “Sec/PIN” 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 door’s Exit Reader parameter is set to anything besides “None,” 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.

f. If you selected either Custom Wiegand or Custom ABA in Step a, select the User Defined Length for the custom card number. This field is disabled if any other reader type is selected.

Note: The User Defined Length 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.

g. Set the Intercard interval (sec). This specifies the minimum acceptable interval between key/card reads. The interval can be from 0 to 255 seconds.



h. Choose the LED polarity. This is the polarity (either Cathode or Anode) of the corresponding LEDs on the key/card reader.

A “Dorado” setting is also available. Use this setting to support the use of a three-LED Dorado reader.

Refer to any of the following manuals for more informa-tion about three LED control:

✢ TCON116, DPU7910A Installation Guide

✢ TCON117, DPU7920 Installation Guide

✢ TCON312, SCU12xx Installation Guide

i. Activate () or deactivate () the Elevator option. Acti-vate this function if the reader associated with this point controls an elevator cab. (This option is not available if you activate the Anti-passback option described in Step k, below.)

j. If the door controller is loaded with firmware version 3.20 or later, a Card Translation option is available. Acti-vate () 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.

If the door controller is loaded with firmware prior to version 3.20, this option is greyed out. In this case card translation is enable via DIP switch 7 on the door controller.

k. Activate () or deactivate () the Anti-passback option. Activate this function to prevent persons who have successfully gained access into an access controlled area from passing their key/card back to another person desiring access. (This option is not available if you activate the Elevator option described in Step i, above.)

Note: The actual system response for both anti-passback and anti-tailgate (below) is controlled by the anti-passback scheme selected for the individual (see “Adding an Individual” on page 17-65).



l. If desired, enable () the Anti-tailgate check box. This option encourages users to use the entry and exit readers for each zone they enter by allowing entry only into zones adjacent to the last-entered zone. (This option is only available on DPUs with a firmware revision 2.20 or later, and only if the Anti-passback option is enabled.)

m. Enter an Entry zone number (0–63; or 0–31 for DPU firmware revisions prior to 2.20). This is the number of the zone where the entry reader is located. (This option is available only if the Anti-passback option is enabled.)

n. Enter an Exit zone number (0–63; or 0–31 for DPU firmware revisions prior to 2.20). This is the number of the zone where the exit reader is located. Leave this field blank if there is no exit reader. (This option is available only if the Anti-passback option is enabled.)

Note: If the Anti-tailgate option is enabled, any door between the non-secured area and the secured area must have the same zone number for both entry and exit. The non-secured area is any region not under access control, such as a lobby, public area, or the outdoors.

o. Set the Anti-passback reset time (0 to 60 minutes). Any value higher than zero (default) will cause the Anti-pass-back flag to be reset for an individual the specified number of minutes after the user passes through the door. Leave this parameter at zero to prevent an auto-matic reset of the APB flag. (This option is only available on DPUs with a firmware revision 2.20 or later, and only if the Anti-passback option is enabled.)

If an “APB Reset” action has been defined in the mode schedule of this door point, it will still be honored (i.e., the individual’s Anti-passback flag may be reset by the APB Reset action before the time specified in the field has expired).



p. On a door controller with firmware version 3.22 or later, you can define a six-digit Door Code for the door. If you enter less than six digits, leading zeros will be appended to the code automatically. You can leave this field blank; however, a Door Code of 000000 is not allowed.

3. Define the Transaction Distribution parameters and Alarm Distribution parameters.

Note: In the following step, only distribution group 1 messages will cause a dial Tap to dial out.

a. Choose a distribution Group (1–4). The message mask will be applied to this group.

b. Define the message Mask. Set each of eight masking posi-tions to the desired state, either activated () or deacti-vated ().

c. Select a Cell number (1–1,023). You must assign a value other than zero (0) 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.

d. Choose a message Priority from the drop-down list.

4. Set the Door Parameters as required.

a. Choose a Door strike setting from the drop-down list. This determines when the door strike (magnetic lock) is to be controlled.

b. Set the Strike duration (1 to 255 seconds). This controls the time that the door will remain unlocked after key/card is read or a release button is pressed.

c. Set the Door open too long duration (0 to 7200 seconds). This specifies the length of time that can pass before a “door open too long” message is generated following a valid key/card.

d. Choose a Door sense switch setting from the drop-down list. This determines whether or not a sense switch exists at this door, and if so, the normal state of the switch.



e. Choose a Door release switch setting from the drop-down list. This determines whether or not a release switch exists at this door, and if so, the normal state of the switch.

f. Enter the duration of the Re-lock timer, in seconds. The timer may be set from 0 to 255 seconds, in 1-second intervals. The default is 4 seconds. This option deter-mines the amount of time that passes between the door opening and re-energizing the lock. (This option is only available on DPUs with a firmware revision 2.20 or later.)

g. Activate () or deactivate () the Shunt option. Acti-vate this function if there is a shunt installed with this door.

h. On a door controller with firmware version 3.21 or earlier, activate () or deactivate () the First key auto-unlock option. Activate this function to permit the door to remain in the Secure or PIN Enable mode past the scheduled unlock time, until the first valid entry sequence is performed.

i. Enter the duration of the Door closed timer, in seconds. The timer may be set from 0 to 25.5 seconds, in 0.1-second intervals. The default is 2 seconds. This option is used to minimize false “forced door” alarms by setting a timer within which the door may bounce while closing without generating the forced door message. (This option is only available on DPUs with a firmware revision 2.20 or later.)

5. Choose a Message Type from the drop-down list for each of the messages listed in the Message Type section. The following message types are available:

Note: The Door open too long, Door forced, Door normal, SLI not avail-able, Door re-locked, Mode messages, and Request to exit messages use the masks and distribution group that have been defined within the DO point editor for the door point. All other messages listed in the Message Type section use the masks and distribution group defined in this editor.



✧ None – Choose this setting to prevent the message from being generated (i.e., the message will not be displayable within an AMT window and will not be available for use with Event Actions/Sequences).

✧ Transact – This option is available for all listed messages except Door Forced, Door Open Too Long, Door Normal, SLI Not Available, Door Relocked, Mode Messages, and request to Exit. Choose this setting to treat the message as a transaction. The masks and distribution group that you defined within this editor for transactions will be applied to all occurrences of this message from the chosen door point.

✧ Message – This option is only available for Door Forced, Door Open Too Long, Door Normal, and Mode messages. Choose this setting to treat the message as a normal message. These messages will use the masks and distribution group defined for the DO point.

✧ Alarm – This option is available for all listed messages. Choose this setting to treat the message as an alarm. If you are currently defining the Door Forced, Door Open Too Long, Door Normal, SLI Not Available, Door Relocked, Mode Messages, or request to Exit message type as “Alarm,” then the masks and distribution group that you defined within the DO point editor will be applied to all occurrences of this message from the chosen door point. If you are defining any other message type as “Alarm,” then the masks and distribution group that you defined within this editor for alarms will be applied to all occurrences of this message from the chosen door point.

6. Use the ATS button to define the Mode Schedules as described in “Mode Schedules” on page 17-19.

7. Use the Features button to define user-defined door attributes and PIN pad functions. Refer to “User-defined Door Features” on page 17-22 for instructions.

8. Use the Sounder button to configure sounder settings for a reader or for an OP5 arming terminal. Refer to “Sounder” on page 17-27 for instructions.



9. Select OK. The system displays the Door Selection summary (see Figure 17-3). The door point has a Y in the A/C column.

10. Repeat Steps 1 through 9 as required for additional door extensions.


Mode SchedulesEach access control extension will include standard time sched-uling parameters for scheduling non-access oriented operations. The only difference between a door schedule and other TAC I/NET Seven time schedules is the available schedule actions.

1. Select ATS from the Door Extensions editor (see Figure 17-4) or highlight a door and select Door ATS from the Door Selec-tion Summary (see Figure 17-3). The system displays the Doors – Schedule editor (see Figure 17-5).

Figure 17-5. Doors – Schedule Editor



2. Choose an action line that does not have a schedule and select Add. The system displays the Door – Actions editor (see Figure 17-6).

3. Choose an Action from the drop-down list. The following actions are available:

✧ APB Reset

Define the schedule for resetting anti-passback. At the specified time, all anti-passback flags associated with the door will be reset (enabling all key/cards).

Note: This will only reset anti-passback for this door. If zoned anti-pass-back is being used, an APB Reset command must be entered in each of the associated doors’ mode schedules.

✧ Lock

Define the schedule for issuing a Lock command to the door. The lock mode disables all reader transactions including the exit push button.

Figure 17-6. Door – Actions Editor



✧ Unlock

Define the schedule for issuing an Unlock command to the door. While in the unlocked state, the doors will not require a key/card read to gain access.

✧ Secure

This is the normal state of door(s). While in the secured state, the door must be opened using a valid key/card or the exit release push button (if so equipped). All key/cards will be validated based on personnel schedules, tenant, key/card issue number, anti-passback, and access level.

✧ PIN Enable (firmware version 3.20 or earlier)—OR—Sec/PIN (firmware version 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 param-eter in the Door Extension Editor will determine how many retries (if any) the individual can use to enter a valid PIN.

✧ Sec/Code (firmware version 3.22 or later)

This mode is similar to the “Secure” mode; however, rather than using a key/card to gain access, the user simply uses the PIN pad to enter the door's assigned code. If the individual enters the correct door code, the door will open.

When the door is operating in the Sec/Code mode, user-definable door attributes or PIN pad functions are not available.

4. For a door controller with firmware version 3.22 or later, a “first key mode” is supported. The First key mode parameter is only active when you set the Action (described in Step 3) to Secure, Sec/PIN, or Sec/Code.



Choose a setting for this parameter from the drop-down list. The options available for this parameter will differ depending on the setting of the Action parameter.

The door will switch to the mode you specify for this param-eter at the first occurrence of an individual gaining authorized access at the door. The door will remain in this mode until the next scheduled action becomes active.

5. Enter a time using 24-hour format in the Time field.

6. Select the days when you want this action to occur. A check mark next to the day indicates that the action will occur on that day. Each day can be toggled between activated () and deactivated ().

7. Select OK. The system displays the Doors – Schedule editor (see Figure 17-5 on page 17-19) showing the action parame-ters that you entered.

8. Repeat Steps 2 through 7 as required for additional Schedules.

9. Select Close to save the settings and return to the Door Extensions Editor (see Figure 17-4 on page 17-10) or to the Door Selection Summary (see Figure 17-3 on page 17-8).

User-defined Door Features

Note: User-definable door attributes and PIN pad functions are only avail-able if the selected door meets the following requirements:

✦ The door controller is loaded with firmware version 3.18 or later.

✦ For PIN pad functions, the keypad must provide an 8-bit burst output.

The DPU7920 with firmware version 3.16 also provides user-defined door features except for the attributes used for the two-man rule.

Only an OP5 arming terminal will provide the “Maintenance” door attribute.



TAC I/NET Seven displays this editor when you select Features from the Door Extension editor. The user-definable features avail-able for a door can be categorized into the following two groups:

✦ Attributes – Door attributes are used to initiate specific actions in the access control system when select users perform a key/card read at the door.

Door attributes will also determine a user’s access level when the user types a valid access code at an OP5 arming terminal.

✦ Functions – PIN pad functions allow users to operate and monitor system functions directly from a PIN pad.

Refer to “User-definable Door Attributes and PIN Pad Functions” in the TAC I/NET Seven Technical Reference Guide for an in depth description of this feature.

Adding Features to a Door

Add features to the door as follows:

1. Select Features from the Door Extensions editor (see Figure 17-4). The system displays the Door Features editor (see Figure 17-7).

Figure 17-7. Door Features



2. If necessary, configure the PIN pad to control an intruder alarm system as follows:

a. In the Intruder Alarm System section, activate () the Enable option.

b. Set the Arm Ready Bit Offset. The state of the DI point that receives the arm ready status signal from the alarm system will be used in TAC I/NET Seven 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 Status from your alarm system. For this reason you need only specify the point’s bit offset. For example, if this signal enters the door controller at DI point 00 (TB1-1 on a DPU7920), then enter a bit offset of 00.

c. Choose the appropriate discrete setting for the Alarm Ready State. For example, if your alarm system sends a level 1 discrete signal when its ready to be armed, then choose 1. Otherwise, choose 0.

d. Set the Arm Relay Bit Offset. The output from this DO point will be used to control the relay that will arm or disarm the alarm system.

You must use a DO point on the current door controller to arm the alarm system. For this reason you need only specify the point’s bit offset. For example, if you use the relay at DO point 07 (TB9-10/11/12 on a DPU7920), enter a bit offset of 07.

e. Choose the appropriate discrete setting for the Alarm Relay State. For example, if you must energize the relay in order to arm the alarm system, then choose 1. Other-wise, choose 0.

3. If you did not activate the Enable option in the Intruder Alarm System section, set the Green LED State to the appro-priate setting (0 or 1) for your system.

When you view the status of a discrete point from the PIN pad, the green LED will illuminate if the discrete point’s value matches the setting of the Green LED State parameter.



4. Assign user-defined attributes and PIN pad functions to the door as follows:

a. Use the Extended mode timeout parameter to specify how many seconds the system will wait for a user to press a valid function key. If you set this parameter to 0, you effectively disable the extended mode and prohibit users from accessing the PIN pad functions.

The timeout counter begins as soon as a user properly initiates the function-entry mode (for example, by pressing the # key and then swiping their card). If the user does not enter a valid code or press the # key within the specified timeout period, the system will automati-cally exit the function-entry mode.

b. Assign an attribute or PIN pad function to the door by highlighting the desired index number (key number for PIN pad functions) and selecting Add. The system displays the Feature Definition editor (see Figure 17-8).

c. Choose a feature from the Function/Attribute drop-down list. The following door features are available:

✢ Arm/disarm – Use to arm or disarm the alarm system, or to view the arm status.

✢ Door mode – Use to place the door into the Lock, Unlock, or Secure mode. Can also be used to view the door mode.

Figure 17-8. Feature Definition Editor



✢ Discrete status – Use to view the current status of specific DI points.

✢ Control relay – Use to manually control specific relays.

✢ Auto Disarm – Use to automatically disarm the alarm system when a user gains authorized access through the door.

✢ Escort Required – Use to restrict selected individ-uals from gaining access through this door without an escort. Can also be used to assign level 3 access to selected users of an Intrusion Alarm System.

✢ Escort – Use to allow selected individuals to escort restricted individuals through this door. Can also be used to assign level 2 access to selected users of an Intrusion Alarm System.

✢ Maintenance – This feature is only available on an OP5 arming terminal. Use this feature to assign a combination of level 2 and level 3 access to selected users of an Intrusion Alarm System.

d. Set the parameters for the selected feature. The following table describes each feature’s parameters.

Table 17-1. Door Feature Parameters

Feature Parameters

Arm/disarm

Disarm – Activate () to allow a user to disarm the alarm system.

Arm – Activate () to allow a user to arm the alarm system.

Control door mode – Activate () to have TAC I/NET Seven automatically change the door mode when a user arms or disarms the alarm system. If the user arms the alarm, the door mode changes to Secure. If the user disarms the alarm, the door mode changes to Unlock.

Note: If you deactivate () all of the above options, the Arm/disarm function will allow a user to simply view the current arm status.

Door mode

Secure – Activate () to allow a user to place the door into the Secure mode.

Unlock – Activate () to allow a user to place the door into the Unlock mode.

Lock – Activate () to allow a user to place the door into the Lock mode.

Note: If you deactivate () all of the above options, the Door mode function will allow a user to simply view the current door mode.



e. Select OK to save your settings.

f. If necessary, continue adding features to the door by repeating the above steps.

When you have finished adding features to the door, the features become available for selection in the door’s personnel schedules. This allows you to selectively choose which door features are active or inactive for individuals or groups that use these schedules. Refer to “Personnel Schedules and Shift Rotations” on page 17-30 for more information.

Sounder

Note: Sounder functions are only available with the SCU1284 door controller and OP5 arming terminal.

For door readers that allow an external device to control the reader’s internal sounder, the SCU1284 can be configured to control the sounder. The OP5 arming terminal provides an internal sounder that can also be configured.

Discrete status

First input – Define the bit offset of the first DI point that a user can monitor from the PIN pad.

Last input – Define the bit offset of the last DI point that a user can monitor from the PIN pad.

Control relay

First Relay – Define the bit offset of the first relay (DO point) that a user can control from the PIN pad.

Last Relay – Define the bit offset of the last relay (DO point) that a user can control from the PIN pad.

Auto Disarm None

Escort required None

Escort None

Maintenance None

Table 17-1. Door Feature Parameters (Continued)

Feature Parameters



1. Select Sounder from the Door Extension editor (see Figure 17-4). This button is visible only when the door controller is an SCU1284 or OP5 arming terminal. The system displays the Sounder Selection editor (see Figure 17-4).

2. Set the Sounder Polarity to the signal level (high or low) necessary to activate the sounder. If you choose the wrong setting, the sounder will activate shortly after you close this editor. In this case, the sounder will remain activated until you correct the Sounder Polarity setting.

3. Choose a sound pattern for each of the states listed in this editor. The states shown will differ depending on whether you are configuring an SCU1284 or an OP5 arming terminal

SCU1284:

Figure 17-9. Sounder Selection Editor

✦ Read ✦ Door re-locked

✦ Denied ✦ Door open too long

✦ Bad card read ✦ Door forced

✦ Door open ✦ Request to exit



OP5 Arming Terminal:

4. Select OK to save your settings and to close the editor.

Modifying a Door ExtensionModifying a door extension is similar to adding a door extension. Use the same procedure as described in “Adding a Door Extension” on page 17-9 except that you choose a point that has a Y in the A/C column and select the Modify button from the Door Selection (see Figure 17-3 on page 17-8) rather than the Add button.

Copying a Door ExtensionOnce you have added a door extension, you can copy it to other points.

1. Choose the door point whose door extension you want to copy from the Door Selection summary (see Figure 17-3 on page 17-8). This point is now the source of the door exten-sions you want to copy.

2. Select Copy. The system displays the Copy Target dialog box.

3. Choose the door point that you want to receive the schedule and select OK. The system displays the Door Extensions editor (see Figure 17-4 on page 17-10).

4. Modify the parameters as required. (Refer to “Adding a Door Extension” on page 17-9.)

5. On the Door Extensions editor select OK. The system displays the Door Selection summary (see Figure 17-3 on page 17-8).

Note: If a No Reply message is received, the door controller is not communi-cating with the MCI.

✦ Read ✦ Trouble/Fault

✦ Denied ✦ Door open too long

✦ Bad card read ✦ Door forced

✦ Entry/Exit in progress

✦ Request to exit


Personnel Schedules and Shift Rotations Access Control

6. Repeat Steps 1 through 5 as required to copy additional door points.


Deleting a Door ExtensionUse the following procedure to delete a door extension.

1. Choose the point whose door extension you want to delete from the Door Selection summary (see Figure 17-3 on page 17-8) and select Delete. The system displays the Door Exten-sion Delete confirmation dialog box.

2. Select Yes. The system deletes the door extension and displays the Door Selection summary (see Figure 17-3 on page 17-8).

3. Repeat Steps 1 and 2 as required to delete additional door points.


Personnel Schedules and Shift Rotations

Personnel schedules are similar to the schedules defined in the Time Scheduling editor, but they do not have any actions. The personnel schedules you define here become the door schedules available in the Adding an Individual procedure (see page 17-65). Once a door schedule is assigned to an individual or a group, that particular schedule is used to grant or deny access when a key/card is presented at the door.

In addition to personnel schedules, you can also define shift rota-tions to control access. This feature is supported only door control-lers loaded with firmware version 3.01 or later. Refer to “Shift Rotations” on page 17-38 for more information.


Access Control Personnel Schedules and Shift Rotations

Personnel SchedulesAccess personnel schedules as follows:

1. Select Access Personnel Schedules, or click the Personnel Schedules tool on the Access toolbar. The system displays the Door Selection summary (see Figure 17-10).

Note: The Access Personnel Schedules command will cause this editor to display all of the points in the TAC I/NET Seven system that are eligible to be door points. If you wish to see only the eligible points on the connected controller, use the Edit Controller Personnel Schedules command to access this editor.

2. Choose a door and select Schedules. The system displays the Personnel Schedules summary (see Figure 17-11). You can assign up to 31 time schedules to each door.

3. You may now add, modify, copy, or delete personnel sched-ules and shift rotations. Procedures for each of these options are described below.

4. When you are finished, select Close to exit this editor.

Figure 17-10. Door Selection Summary



Adding a Personnel Schedule1. From the Personnel Schedules summary, shown in

Figure 17-11, choose a schedule without a name and select Add. The system displays the New Schedule dialog box (see Figure 17-12).

2. Enter the schedule Name (up to 16 characters).

3. You must now choose which type of schedule that you wish to create. Choose the Personnel Schedule option.

Figure 17-11. Personnel Schedules Summary

Figure 17-12. New Schedule Dialog Box



4. Select OK. The system displays the Personnel Schedules editor (see Figure 17-13).

Each time schedule can contain up to seven access intervals. An access interval is the time period during which a key/card can access the door, defined with a start and stop time entered in 24-hour format. You can then assign the schedule you create as a temporary schedule, a special day schedule, or a regular schedule for a weekday or several weekdays

5. Choose an access interval number and select Add. The system displays the Schedule Details editor (see Figure 17-14).

Figure 17-13. Personnel Schedule Editor



The Schedule Details editor is divided into two sections: Schedule and Features. The features that appear in the Features section are unique for each door and reflect the door’s current configuration. The actual parameters that appear in the Features group on your system will depend on which features have been defined for the door you have selected.

6. Enter the Begin time and End time for this access interval in 24-hour format.

7. Select the days when you want the access interval to be enabled.

A checkmark next to the day indicates that the access interval is active for that day. Each day can be toggled between acti-vated () and deactivated ().

8. If necessary, assign this access interval to special day schedules and/or temporary schedules by activating () and deacti-vating () the necessary checkboxes.

Figure 17-14. Schedule Details Editor



Refer to “Special Days” and “Temporary Schedules” in the TAC I/NET Seven Technical Reference Guide for more infor-mation about these features.

9. If necessary, enable door features for this access interval by activating () and deactivating () the necessary checkboxes in the Features section of the editor. Refer to “User-defined Door Features” on page 17-22 for more information.

If the door is an OP5 arming terminal, the Escort, Escort required, and Maintenance features will determine a user’s access level in the IAS. Refer to TCON314, “Intrusion Alarm System Installation Guide,” for more information.

10. Select OK. The system displays the Time Schedule editor (see Figure 17-13) showing any access intervals that have been entered.

Note: If you have established any temporary schedules, you can select the days when you want them to run. Do not designate a day as having a temporary schedule if you have not established it. If you do, no actions will occur that day.

11. Repeat Steps 5 through 10 as required to add more access intervals (up to seven) for this schedule.

12. If you wish to use a Temporary schedule for this Personnel schedule, use the spindials to choose Temporary schedule 1, Temporary schedule 2, or Both.

13. If necessary, you can select the Spec Days button to define special days. Refer to “Adding Special Days” on page 10-14 for detailed instructions.

14. Select OK to save your settings and close the Personnel Sched-ules editor. The system displays the Personnel Schedules summary (see Figure 17-11 on page 17-32).

15. Repeat Steps 1 through 14 as required to add more door schedules (up to 31).

16. When you are finished adding door schedules, select Close. The system returns to the Door Selection summary (see Figure 17-10 on page 17-31).



17. Repeat this procedure as required to add schedules to other doors.

18. From the Door Selection summary, select Close to exit this procedure.

Modifying a Personnel Schedule

Modifying a door schedule is similar to adding a door schedule. Use the same procedure as described in “Adding a Door Schedule” on page 17-32 except that you choose a schedule that already exists and select Modify rather than Add from the Personnel Schedules editor (see Figure 17-11 on page 17-32).

Copying a Personnel Schedule1. From the Personnel Schedules editor (see Figure 17-11 on

page 17-32), choose the schedule you want to copy and select Copy. The system displays the New Schedule dialog box (see Figure 17-15).

2. Enter the new schedule Name (up to 16 characters).

3. Select the Schedule number that you want to receive the schedule.

4. Select OK. The system displays the Personnel Schedule editor (see Figure 17-13 on page 17-33).

5. Modify the access intervals as required (see “Adding a Door Schedule” on page 17-32).

6. Select OK. The system displays the Personnel Schedules editor (see Figure 17-11 on page 17-32) with the new schedule added.




7. Repeat Steps 1 through 6 as required to copy more schedules.


Copy All

The Copy All function allows you to copy all personnel schedules from the currently selected (source) door to a target door. Use the following steps to copy all personnel schedules:

1. From the Personnel Schedules editor (see Figure 17-11 on page 17-32), select Copy All. The system displays the Copy All dialog box (see Figure 17-16).

2. Choose a target door point from the list and select OK. The system copies the personnel schedules from the source door to the target door.

Deleting a Personnel Schedule

From the Personnel Schedules editor (see Figure 17-11 on page 17-32) choose the schedule that you want to delete and select Delete. The system deletes the schedule.

Figure 17-16. Personnel Schedules – Copy Dialog Box



Shift Rotations

Note: This feature is supported on door controllers loaded with firmware version 3.01 or later.

A shift rotation is a set of personnel schedules that are activated in a specific order and remain activated for a specific duration. You must have already created personnel schedules before you can create a shift rotation.

Access shift rotations just as you would access personnel schedules. If necessary, refer to “Personnel Schedules” on page 17-31 for instructions.

Adding a Shift Rotation1. From the Personnel Schedules editor (shown in Figure 17-11

on page 17-32) choose a schedule without a name and select Add. The system displays the New Schedule dialog (see Figure 17-12 on page 17-32).

2. Enter the shift rotation Name (up to 16 characters).

3. You must now choose which type of schedule that you wish to create. Choose the Shift Rotation option.

4. Select OK. The system displays the Shift Rotation editor (see Figure 17-17).

5. Add schedules to the shift rotation as follows:

a. Highlight a schedule from the list of Available Sched-ules on the right side of the dialog. (If no schedules are listed, you have not defined any personnel schedules for the selected door. In this case you must exit this dialog and add personnel schedules to the door. Refer to “Adding a Personnel Schedule” on page 17-32 for instructions.)

b. Select the <-Add button to add the highlighted schedule on the right to the shift rotation on the left.

c. Repeat these steps as necessary to add up to 32 schedules to the shift rotation.



d. Use the Move Up and Move Down commands to adjust the order of each schedule in the Rotation List. Shift rota-tion schedules are used in the order that you define here.

e. If necessary, use the Remove or Remove All buttons to remove schedules from the Rotation List.

6. Define the Rotation Start as follows:

a. Define the start Date. Click the drop-down button next to this field to display a calendar. Use the calendar to choose the start date.

b. Define the start Time. You can type the time directly or use the up and down arrows next to this field to adjust the time.

7. Define the Rotation Properties as follows:

a. Choose the Days or Hours option, depending on how often shift schedules will change.

Figure 17-17. Shift Rotation Editor



b. Set the Rotation Interval to a value from 1 to 365. This parameter will determine the number of days or hours that will elapse before the door switches from the current schedule to the next schedule in the shift rotation.

8. Select OK to save the Shift Rotation.

Modifying a Shift Rotation

Modifying a shift rotation is similar to adding a shift rotation. Use the same procedure as described in “Adding a Shift Rotation” on page 17-38 except that you choose a shift rotation that already exists and select Modify rather than Add from the Personnel Sched-ules editor (see Figure 17-11 on page 17-32).

Copying a Shift Rotation1. From the Personnel Schedules editor (see Figure 17-11 on

page 17-32), choose the shift rotation you want to copy and select Copy. The system displays the New Schedule dialog box (see Figure 17-15).

2. Enter the new shift rotation Name (up to 16 characters).

3. Select the Schedule number that you want to receive the shift rotation.

4. Select OK. The system displays the Shift Rotation editor (see Figure 17-17 on page 17-39).

5. Modify the shift rotation as required (refer to “Adding a Shift Rotation” on page 17-38 for instructions).



Access Control Elevators

6. Select OK. The system displays the Personnel Schedules editor (see Figure 17-11 on page 17-32) with the new shift rotation added.

7. Repeat Steps 1 through 6 as required to copy more shift rota-tions.


Deleting a Shift Rotation

From the Personnel Schedules editor (see Figure 17-11 on page 17-32) choose the shift rotation that you want to delete and select Delete. The system deletes the shift rotation.

Elevators

The Elevator control function will work in conjunction with the access control parameters and personnel schedules to control access to banks of elevators. Activating () the elevator option in the Door Extension editor (see Figure 17-4) will cause the door controller to process each reader transaction as though it were an entry into an elevator cab.

Note: Changing a Door from elevator to non-elevator, or vice versa, will cause the door controller to purge its database.

In addition to supplying the above parameters at the door controller level, it will also be necessary to supply the DPI, MCI, or I/SITE LAN with the information required to associate an elevator cab with the discrete output points that enable the floor relays, and the discrete input points that monitor the button selection.

There will be an elevator extension on each door point (BB 08 and 09) in the DPI, MCI, or I/SITE LAN that is assigned as an elevator. After adding the extension to the point you must define the Elevator parameters such as floor selection time, floor designation description, button enable point, and button selection point.

Before defining an elevator, you must do the following:


Elevators Access Control

1. Define a door point as an elevator in the Door Extensions editor (see Figure 17-4 on page 17-10).

2. Use the Resident I/O Points editor (see Chapter 5, Point Defi-nition and Addressing) to define a floor enable point (DO) and a floor selection point (DI) for each floor that will be assigned to an elevator.

3. Use the Personnel Schedules editor (see page 17-30) to define up to 31 schedules for the selected elevator door point.

Adding an Elevator ExtensionUse the following procedure to add an elevator extension:

1. Select Edit Controller Elevators, or click the Elevators tool on the Controller toolbar. The system displays the Resi-dent I/O Points summary with the elevators option selected (see Figure 17-19). This summary lists the available door (elevator) points.

Figure 17-19. Resident I/O Points Summary (EL selected)



2. Choose a point that represents a reader in an elevator cab and that does not have a Y in the EL column. Highlight the point and select the Add button. The system displays the Elevators summary (see Figure 17-20).

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.

1. Enter a Floor selection time (sec) (1–255). This is the amount of time in seconds that the key/card user has to make a selection from the floor buttons in the elevator cab. The default is 5.

2. Select Add. The system displays the Elevators – Floor Parame-ters editor (see Figure 17-21). This allows you to define the floor index attached to this elevator extension.

3. Enter the Floor index number (1–62). This is the line number in the Elevator summary list.

Figure 17-20. Elevators Summary



4. Enter the Floor designation (up to two characters).This identifies the floor. For example, the first level of a basement could be represented as B1.

5. In the Button enable field choose a point from the drop-down list of all possible discrete output points in the controller.

6. In the Button selection field choose a point from the list of all possible discrete input points in the controller.

7. Select OK. The system displays the Elevators summary (see Figure 17-20).

8. How you proceed from this point will depend upon the type of elevator control you are implementing. Refer to the Access Control chapter in the Technical Reference Guide for a description of Elevator Control Schemes, then use the appro-priate steps below:

Traditional Elevator Control

Tradition elevator control uses floor maps to allow each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within TAC I/NET Seven.

a. Select Floors. The system displays the Tenant Selection summary (see Figure 17-22).

b. Choose a tenant from the list and click the Select button. The system displays the Elevators – Floor Schedules summary (see Figure 17-23).

Figure 17-21. Elevators – Floor Parameters Editor



c. Choose a schedule from the list and select Select. The system displays the Elevators – Access Intervals Summary, shown in Figure 17-24.

d. Choose an access interval from the list and click Select. The system displays the Elevators – Floor Map summary (see Figure 17-25).

e. Choose the DO points which enable the floor selection buttons for the appropriate floors. Points marked with “[X]” will enable their respective floor selection button in the elevator cab.

Figure 17-22. Tenant Selection Summary

Figure 17-23. Elevators – Floor Schedules Summary



f. When you have finished choosing the appropriate DO points, select OK. The system returns to the Elevators – Access Intervals summary.

g. You may continue assigning floors to access intervals or you may exit the elevator functions by selecting Close at each editor.

Figure 17-24. Elevators – Access Intervals Summary

Figure 17-25. Elevators – Floor Map Summary


Access Control Key/Card Translations

Extended Elevator Control

Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors.

a. From the Tenant Editor, assign floors (i.e., door enable points) to the tenant. Refer to “Adding a New Tenant” on page 17-51 for more information.

b. Assign floors to individuals and/or groups as necessary. Refer to “Adding an Individual” on page 17-65 and “Adding an Access Group” on page 17-57 for more infor-mation.

Key/Card Translations

If desired, you may use the Key/card Translation editor to translate large key/card numbers, such as those used by I/DISC and Water-mark, into smaller numbers. This editor has a maximum of 128 sets of translation parameters.

Note: Key/card translations are required for systems using door controller firmware prior to version 2.20. For firmware version 2.20 or later, key/card translations are optional.

TAC I/NET Seven allows you to use combinations of translated and non-translated key/cards. Therefore, you must be careful not to duplicate the key/card assignments. If both a non-translated and a translated key/card are assigned to the same individual number, only the first one defined will work. The duplicate key/card will be ignored by the door controller.

1. Select Access Key/Card Translations, or click the Key/Card Translations tool on the Access toolbar. The system displays the Key/Card Translation summary (see Figure 17-26).

2. You may now add, modify, copy, or delete key/card transla-tions. Procedures for each of these options are described below.


Key/Card Translations Access Control

3. When you are finished, select OK to accept your changes and exit this editor.

Adding a Key/Card TranslationUse the following steps to add a key/card translation:

1. Select Add from the Key/Card Translation summary (see Figure 17-26). The system displays the Key/Card Translation editor (see Figure 17-27).

2. Enter a Source (starting) key/card number to be translated. This number can be up to 16 digits long.

Figure 17-26. Key/card Translation Summary

Figure 17-27. Key/Card Translation Editor


Access Control Key/Card Translations

3. Enter a Target key/card number (1–32,000) to which the source key/card number will be translated. The remaining key/card numbers will be translated to consecutive key/card numbers following the target number you define here.

4. Enter a Count value (1–32,000). This is the total number of key/card numbers to be translated.

5. Enter a Tenant number (1–255). This is the tenant to which this block of key/cards will be assigned.

6. Select OK. The system displays the Key/Card Translation summary (see Figure 17-26).

7. Repeat Steps 1 through 6 as required for additional key/card translations.

Using Figure 17-27 as an example, key/tag numbers 778240 to 802240 will be translated to key/tag numbers 1 to 24000, respec-tively.

Modifying a Key/Card TranslationModifying a key/card translation is similar to adding a key/card translation. Use the same procedure as described in “Adding a Key/Card Translation” on page 17-48 except that you choose an existing entry and select Modify rather than Add from the Key/Card Translation summary (see Figure 17-26).

Deleting a Key/Card Translation1. Choose the key/card translation you want to delete and select

Delete from the Key/Card Translation summary (see Figure 17-26). The system displays the Delete confirmation dialog box.

2. Select Yes. The system deletes the key/card translation and displays the Key/Card Translation summary (see Figure 17-26).


Tenants Access Control

Tenants

The concept of tenants, as used in TAC I/NET Seven, lets you assign access controlled doors to more than one tenant. Tenants are usually different groups that inhabit the same facility but that are billed separately. For example, a single large building may be inhab-ited by several companies. Each company would be considered a separate tenant.

When you add a tenant to the system, you must define the block of key/cards that will be allocated to that tenant and you must define through which doors that tenant will have access.

Each tenant is assigned a number (1–255). Tenant 0 (“All Tenants”) is used to define doors, groups, and schedules that are common to all tenants. Tenant 0 cannot be deleted. You cannot add individuals to Tenant 0.

1. Select Access Tenants, or click the Tenants tool on the Access toolbar. The system displays the Tenants summary (see Figure 17-28).

2. You may now add, modify, copy, or delete tenants. Procedures for each of these options are described below.

3. When you are finished, select Close to leave this editor.

Figure 17-28. Tenants Summary


Access Control Tenants

Adding a New Tenant

Note: The Add option in the Tenants Summary will be greyed out if the user's host password prevents full access to all remaining undefined tenants or if all 255 tenants have already been added.

1. From the Tenants summary (see Figure 17-28) select Add. The system displays the Add – Tenants dialog box (see Figure 17-29).

2. Enter the New tenant number (1 to 255) and select OK. The system displays the Tenants editor (see Figure 17-30).

3. Enter the Tenant name (up to 16 characters).

4. Enter the Tenant code (up to 8 digits). This field is not avail-able for Tenant 0.

Note: A system that uses I/DISCs requires tenant codes greater than 0.

5. Enter the First individual number (1 to 32,000). This field is not available for Tenant 0.

6. Enter the Number of individuals (0 to 32,000) that the tenant will receive. This field is not available for Tenant 0.

7. If desired, select a Duress Scheme from the drop-down box. See your TAC I/NET Seven system administrator or contact TAC Product Support Services for more information about duress.

Figure 17-29. Add – Tenants Dialog Box



8. Check () the Disabled check box if you wish to deny access to all individuals assigned to this tenant. All key/cards for individuals assigned to this tenant will be disabled. This field is not available for Tenant 0.

Warning: This check box setting does not take effect until you select OK to exit the Tenants editor.

9. Choose the doors (including elevator door points and/or floor enable points) that this tenant will be able to access. Activate [X] or deactivate [ ] individual doors. If the tenant is to have access to all of the doors, select All Yes. If the tenant is to have access to none of the doors, select All No.

Note: Only doors saved in the network configuration are listed.

10. Select OK. The system displays the Tenant summary (see Figure 17-28 on page 17-50).

Figure 17-30. Tenants Editor


Access Control Tenants

11. Repeat Steps 1 through 10 as required to add more tenants.


Modifying Tenant Parameters

Note: The Modify option in the Tenants Summary will be greyed out if the user's host password prevents full access to the currently selected tenant.

Modifying tenant parameters is similar to adding tenant parame-ters. Use the same procedure as described in “Adding a New Tenant” on page 17-51 except that you choose a tenant that already exists and select Modify rather than Add from the Tenants summary (see Figure 17-28 on page 17-50).

Copying Tenant Parameters

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

The Copy option in the Tenants Summary will be greyed out if the user's host password prevents full access to the currently selected tenant.

1. From the Tenants summary (see Figure 17-28 on page 17-50) choose the tenant whose parameters you want to copy and select Copy. The system displays the Copy – Tenants dialog box (see Figure 17-31).

2. Enter the New tenant number (1 to 255). This number cannot belong to anyone else.

Figure 17-31. Copy – Tenants Dialog Box



3. Select OK. The system displays the Tenants editor (see Figure 17-30).

4. Set the parameters and door selection as in “Adding a New Tenant” on page 17-51.

5. Select OK. The system displays the Tenants summary (see Figure 17-28 on page 17-50).

6. Repeat Steps 1 through 5 as required to copy additional tenant parameters.


Deleting a Tenant

Note: The Delete option in the Tenants Summary will be greyed out if “All Tenants” is selected or if the user’s host password prevents full access to the currently selected tenant.

When you delete a tenant from TAC I/NET Seven, all groups and individuals defined for the tenant will also be deleted. TAC I/NET Seven can be configured to temporarily store deleted tenants in a recycle bin (refer to the Recycle bin enable parameter in Step 12 on page 17-91). When using the recycle bin, all of the tenant’s groups and individuals are retained within the deleted tenant record. This allows you to restore the deleted tenant (along with its groups and individuals) to an active status as long as the tenant record resides in the recycle bin.

Note: If the recycle bin feature is not enabled when you delete a tenant, or if the deleted tenant record is purged from the recycle bin, the tenant (including all of its groups and individuals) is permanently purged from the system.

1. From the Tenants summary (see Figure 17-28 on page 17-50) choose a tenant to delete and select Delete. The system displays the Delete confirmation dialog box.

Note: You cannot delete Tenant 0.


Access Control Groups

2. Select Yes. The system deletes the tenant and displays the Tenants summary (see Figure 17-28 on page 17-50).

3. Repeat Steps 1 and 2 as required to delete more tenants.


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.

The information in this section describes how to define groups. For instructions on how to assign one or more groups to an individual, refer to Step 17 of the “Adding an Individual” precedure that starts on page 17-65.

Note: Using this editor 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 performed the edit.

1. Select Access Groups, or click the Groups tool on the Access toolbar.

• If your system has more than one tenant, the Tenant selec-tion – Group summary displays (see Figure 17-32). In this case proceed with step 2.

• If only a single tenant has been defined, the Groups — Summary List displays. In this case you can skip step 2 and proceed with step 3.


Groups Access Control

2. Highlight a tenant and click Select to display the Groups Summary List (see Figure 17-33).

Note: If your host password prevents full access to the selected tenant, only the groups that are allowed will be visible. Refer to “Limited-access Users” on page 9-15 for more information

Figure 17-32. Tenant Selection – Group Summary

Figure 17-33. Groups – Summary List



3. You may now add, modify, copy, or delete access groups. Procedures for each of these options are described below.

Note: Groups added to Tenant 0 will be available to all tenants.

4. When you are finished, select Close to leave this editor.

Adding an Access Group

Note: If your host password prevents full access to the selected tenant, the Add option will be greyed out. Refer to “Limited-access Users” on page 9-15 for more information

1. Select Add from the Groups – Summary List. The system displays the Add – Groups dialog box (see Figure 17-34).

2. In the Group name field enter the name of the group you want to add and select OK. The name will start with a ~ if the group is for Tenant 0 (All Tenants). The system displays the Group editor (see Figure 17-35).

Note: When defining a group for Tenant 0 (all tenants), the group name starts with the ~ symbol. This symbol is automatically placed as the first character, and cannot be deleted.

Figure 17-34. Add – Groups Dialog Box

Figure 17-35. Group Editor



3. Choose a Record type from the drop-down list. You have the following options:

✧ Permanent – Choose this option for a group of perma-nent employees with access privileges.

✧ Temporary – Choose this option for a group of visitors with a temporary schedule that has a begin and end date.

✧ Disabled – Choose this option to enter all of the group parameters into the personnel database, including door and schedule assignments, but without allowing the group access privileges.

Note: Each individual’s access rights will be determined by the combination of their individual and group record types. Refer to the Access Control chapter of TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

4. If you set the Record Type to “Temporary,” enter the Begin date, Begin time, End date, and End time during which access will be allowed.



5. Select Doors. The system displays the Groups – Door Selec-tion summary (see Figure 17-36) showing a list of doors assigned to the tenant this group belongs to. This list also includes elevator door points, floor enable points, and OP5 arming terminals.

Use this editor to define the schedules during which key/card holders in this group have access through the tenant’s doors. Only those doors assigned to the current tenant are displayed.

Note: If your host password is configured to limit your access to specific groups, this editor will only show doors associated with allowed groups.

Refer to “Limited-access Users” on page 9-15 for more information.

6. If you wish to use an existing group as the basis for the access schedule, perform the following:

a. Select the Groups button. The system displays the Groups – Group Selection summary (see Figure 17-37) with a listing of all currently defined groups.

Figure 17-36. Groups – Door Selection Summary



Note: If your host password is configured to limit your access to specific groups, only the groups that your password allows will be visible.


b. Select the desired group and click the <- Add button. The selected group will move from the Not Member of list to the Member of list. Repeat as necessary to add multiple groups.

c. If you selected more than one group in Step b, use the Move Up and Move Down buttons to set the desired priority order for the groups on the Member of list.

Note: If there is a schedule conflict between multiple groups selected for a door, the schedule for the higher group in the list overrides the schedule for any group lower in the list.

d. When finished, select the OK button to return to the Groups – Door Selection summary, or select Cancel to exit without saving your changes.

Figure 17-37. Groups – Group Selection Summary



7. If you wish to customize the schedule for this group, perform the following:

a. Choose a door and select the Schedules button. The system displays the Groups – Door Schedules summary (see Figure 17-38) with a listing of all currently defined schedules.

b. Choose a schedule and select the OK button. The system applies the schedule to the door and displays the Groups – Door Selection summary (see Figure 17-36 on page 17-59).

Note: In case of schedule conflict, this schedule overrides any group sched-ules selected for this door.

c. Repeat as required to add more doors and schedules for this group.

d. Select Close. The system displays the Groups editor (see Figure 17-35 on page 17-57).

8. Select OK. The system saves the settings and displays the Groups Summary List (see Figure 17-33 on page 17-56) with the new group added to the list.

9. Repeat Steps 1 through 8 to add more groups to this tenant.

Figure 17-38. Groups – Door Schedules Editor



10. Select Close from the Groups – Summary List.

11. Repeat Step 1 through 10 as required to add groups to other tenants.

Modifying an Access Group

Note: While modifying a group, you will only see doors associated with allowed groups if your host password is configured to limit your access. Refer to “Limited-access Users” on page 9-15 for more infor-mation.

Modifying an access group is similar to adding an access group. Use the same procedure as described in “Adding an Access Group” on page 17-57 except that you choose a group that already exists and select the Modify button from the Groups – Summary List (see Figure 17-33 on page 17-56) rather than the Add button.

When you modify a group, all groups and individuals that are members of this group (this group is listed in the Member of list of the Group Assignment summary) will reflect the change.

Copying an Access Group

Note: The Copy option will be greyed out if your host password prevents full access to the selected tenant. Refer to “Limited-access Users” on page 9-15 for more information.

1. From the Groups – Summary List (see Figure 17-33 on page 17-56) choose the group whose parameters you want to copy and select Copy. The system displays the Copy – Groups dialog box.

2. In the Enter group name field enter the name of the new group.

3. Select OK. The system displays the Groups – Summary List (see Figure 17-33 on page 17-56) with the new group added to the list.

4. Repeat Steps 1 through 3 as required to copy other access groups.



Access Control Individuals

Deleting an Access Group

Caution: If you delete a group, all individuals assigned to that group remain in the system but they cannot gain access through any door unless they have individual access or access through another group.

Note: The Delete option will be greyed out if your host password prevents full access to the selected tenant. Refer to “Limited-access Users” on page 9-15 for more information

TAC I/NET Seven can be configured to temporarily store deleted groups in a recycle bin (refer to the Recycle bin enable parameter in Step 12 on page 17-91). This feature allows you to restore a deleted group to an active status as long as the group record resides in the recycle bin.

Note: If the recycle bin feature is not enabled when you delete a group, or if the deleted group record is purged from the recycle bin, then the group is permanently purged from the system.

1. From the Groups – Summary List (see Figure 17-33 on page 17-56) choose the group you want to delete and select Delete. The system displays the Delete confirmation dialog box.

2. Select Yes. The system deletes the group and displays the Groups - Summary List (see Figure 17-33 on page 17-56).

3. Repeat Steps 1 and 2 as required to delete other groups.

4. Select Close from the Groups – Summary List to exit this procedure.

Individuals

TAC I/NET Seven provides an Individuals Summary screen that allows you to add individuals to your access control system. Here, you assign key/cards to individuals, assign schedule access to doors, configure individuals to be users of an intrusion alarm system, and populate the personnel database. The type of information displayed within the Individuals editors, as well as your ability to


Individuals Access Control

add, delete, or modify individuals, is dependent upon the privileges assigned to your host password (refer to Chapter 9, Passwords, for information).

1. Select Access Individual, or click the Individual tool on the Access toolbar. If you have more than one tenant, the Tenant selection – Individual summary displays (see Figure 17-39).

2. Choose the Tenant to which the individual belongs and select the Select button. The system displays the Individual Summary (see Figure 17-40) which shows all of the individ-uals assigned to this tenant.

The information displayed within the Individuals Summary is divided into columns. If necessary, you can use the mouse to resize the column widths. Refer to “List Boxes” in Chapter 1, TAC I/NET Seven Basics, for more information.

The Individuals Summary includes a “Sort” column. This column displays the content of the field selected as the display order field (refer to “Display Options” on page 17-78 for more information about choosing the display order). For instance, if you choose Field #1 as the display order field, the content of Field #1 is displayed in the Sort column.

If you base the display order on the hexadecimal card number, the summary displays multiple entries for any users with more than one assigned key/card. This causes the Add,

Figure 17-39. Tenant Selection – Individual



Delete, and Copy functions to become disabled. Choose some other display order to re-enable the Add, Delete, and Copy functions.

Adding an Individual

Note: Your ability to add an individual to the access control system will depend upon the privileges assigned to your host password. Refer to Chapter 9, Passwords, for more information.

If the Second password required for Individuals option is acti-vated () in the Options editor, TAC I/NET Seven will require entry of a second operator’s host password before allowing you to add an individual. Refer to “Options” on page 17-87 for more information.

When you sort the summary by the hexadecimal card number (using the Option button described on page 17-78), the Add, Delete, and Copy functions become disabled. Choose some other display order to re-enable the Add, Delete, and Copy functions.

Figure 17-40. Individuals Summary



1. Select Add. The system displays the Individuals – Add dialog box (see Figure 17-41).

2. Set the New individual number value. The default is the next available number. The range of valid values for this field will depend on the First individual number and the Number of individuals defined for the tenant (refer to “Adding a New Tenant” on page 17-51).

Note: The Card Number fields, described in the following step, are displayed only if the privileges assigned to your host password allow you to view and modify this information.

3. Enter the Card Number, if desired. This is the value encoded on the individual’s key/card. You may enter the card number as either a hexadecimal (base 16) or decimal (base 10) value; the other scale will be calculated automatically.

If your host station includes an I/DISC key reader, you may read the number directly instead of typing it in. Refer to “Options” on page 17-87, and the section on Configuration in TCON157, TAC I/NET Forms and Worksheets Getting Started.

If you make an individual a user of an Intrusion Alarm System, the individual’s Card Number will be the User ID that the user must type at on OP5 arming terminal in order to log on.

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

Figure 17-41. Individuals – Add Dialog Box



Seven will not honor both actions with the same key/card number or with the same individual. If you directly assign a key/card to an indi-vidual, and later translate the same key/card for another individual, only the translated key/card will be operational within TAC I/NET Seven. Refer to the Access Control chapter in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

4. Select OK to accept your settings. The system displays the Individual Parameters editor (see Figure 17-42). Use this editor to define parameters for each individual in your access control system.

Figure 17-42. Individual Parameters Editor



The information displayed within the Individuals Parameters editor is divided into columns. If necessary, you can resize the column widths. Refer to “List Boxes” in Chapter 1, TAC I/NET Seven Basics, for more information.

Note: The actual fields displayed within the Individuals Parameters editor will be determined by the access rights associated with your host pass-word. The steps below assume that all fields are displayed. Refer to Chapter 9, Passwords, for more information.

5. The read-only Group field lists the primary group this indi-vidual is assigned to. A * symbol in front of the group name indicates that the individual is assigned to more than one group. A ~ symbol in front of the group name indicates a global group (available for all tenants). Groups are assigned through the Group Selection Summary editor (see Step 17 below).

6. Enter the individual’s Last name and First name (up to 50 characters each).

Note: Every tenant has an Access Control database table where the unique field names for fields 3 through 18 are stored. The fields are named in the Field Names procedure on page 17-80.

7. Enter the appropriate information (up to 50 characters) in fields 3 through 18 (User Field 1–16) as required.

Note: One of the user fields may be designated as a Unique Field in the Access Control - Options editor (see “Options” on page 17-87). The designated Unique Field may be left blank. If a value is entered, it must be unique across all tenants and individuals.

8. The individual’s current card numbers are listed in both the hexadecimal and decimal values.

a. Click Add New Card in either the Hex Number or Decimal Number column to enter a new card number. You may edit either field. The value for the other scale will be calculated automatically.



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.

b. If you wish to store the card in the memory of the DPUs, activate ([X]) the DPU Res. option. (You will not be able to activate this field if the card number field is blank.) This parameter will only be used in door controllers capable of database caching (firmware revision 2.20 or later). Refer to the section on DPU Database Caching in TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Note: All individual key/card numbers that use a translation table will be resident in the door controller, regardless of the setting of this param-eter.

c. If you wish to disable the card, activate ([X]) the Disabled option. A disabled card will be denied entry at access controlled doors.

9. To add an individual Image, click the ... button or double-click the default image to browse for the individual’s picture.

The image formats that are supported are: .JPG, .GIF, .BMP, .TIF, and .PNG. If your image is in a different format, you must first convert it to one of the supported formats, using a third-party graphics program.

The best practice is to specify a fully qualified UNC path. This will help ensure that the image can be located regardless of which TAC I/NET Seven host workstation is being used to display the image. Refer to the description of the “Image Path” in the Access Control chapter of TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Caution: While performing the following step, 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. Refer to



Chapter 5, Controller Functions in TCON300, TAC I/NET Seven Technical Reference Guide, for more information about the Auto-matic DPU Restore function.

10. Choose a Record type from the drop-down list. The following options are available:

✧ Permanent – Choose this option if the individual is a permanent employee with access privileges.

✧ Temporary – Choose this option for visitors with a temporary schedule that has a begin and end date.

✧ Disabled – Choose this option to enter all of the indi-vidual parameters into the personnel database, including door and schedule assignment, but without allowing the individual access privileges.

If you assign a Record Type setting of Disabled in this editor, the individual's access to group doors will be disabled (other members of the group will still have access to group doors). Door assignments that are duplicated at both the individual and group level will use the individual's Record Type setting rather than the group's Record Type setting.

Caution: It is the job of the Automatic DPU Restore function to download “Temporary” individual records to DPUs 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. refer to the description of the “Automatic DPU Restore” feature in TCON300, TAC I/NET Seven Technical Reference Guide.

Note: If you change an existing individual's Record Type from Temporary to Permanent, and then later change it back to Temporary, ensure that you also edit at least one date or time field as described below in Step 11. Simply changing the Record Type from Permanent back to Temporary will not cause TAC I/NET Seven to once again use the Temporary record type.



11. If the individual’s record type is “Temporary,” perform the following steps:

a. Enter the Begin date and Begin time. Use the mm/dd/yy format to define the begin date. Use the 24-hour format to define the begin time. These parameters determine when the key/card will become valid.

b. Enter the End date and End time. Use the mm/dd/yy format to define the end date. Use the 24-hour format to define the end time. These parameters determine when the key/card will no longer be valid.

12. Select the APB (anti-passback) scheme for this individual. This determines the system response when an individual attempts to read into an area twice, through a door controlled by anti-passback.

✧ 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: The APB scheme is only active if anti-passback is activated for the door (see “Adding a Door Extension” on page 17-9). The same scheme is used for both anti-passback and anti-tailgate (if activated).

13. If desired, edit the Personal Identification Number (PIN) for the selected individual. The PIN can be edited only if the User defined PIN check box is activated () in the Access Control - Options editor (see “Options” on page 17-87). User-defined PINs will only be honored when the individual has been assigned a large key/card number.

Note: The individual record must include a PIN. If the default PIN is blank, you must enter a PIN before you can save the individual parameters.



The default PIN is generated automatically by the system and is based on the card number and issue number defined for the individual (i.e., changes to either of these numbers causes the system to generate a new PIN). The PIN is only necessary at doors configured to use a keypad to control access.

Note: TAC I/NET Seven’s 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.

TAC I/NET Seven includes a PIN generator which allows you to generate a list of PINs for a range of key/card numbers. Refer to “PIN Generation” on page 17-86 for more informa-tion.

Note: If your access control system is configured to use Wiegand cards, the Issue Number described in the following step will only affect the PIN assigned to the card. The card will never generate a “Deny Issue” message, regardless of the Issue Number setting.

14. Using the spindial, choose an Issue number. This must be the most recent issue of the key/card. If a person attempts to gain access using a card with an invalid Issue Number, the system will deny access and generate a “Deny Issue” message.

Note: Issue number is not used on systems utilizing large key/card numbers. Refer to “Key/Card Translations” on page 17-47 if you wish to use issue number to control access.

15. Use the two Individual Activity Manager (IAM) parameters as follows:

a. Activate () the Graced parameter if you wish to exclude this individual from activity monitoring.

b. The Disabled parameter is only available after the indi-vidual has become automatically disabled because of inactivity. Use this parameter to de-activate () the user's “disabled” status. This will cause activity moni-toring for this individual to restart from this point.



Refer to “Individual Activity Manager” on page 17-92 for more information.

16. Select Doors. The system displays the Individuals – Door Selection summary (see Figure 17-43).

Note: The access rights of an individual assigned to a group will be deter-mined by the combination of their individual and group record types. If the same door is selected for an individual, and for one or more groups to which that individual is assigned, the individual assign-ment 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. Refer to the Access Control chapter of TCON300, TAC I/NET Seven Technical Reference Guide, for more information.

Use this editor to define those doors (including elevator door points, floor enable points, and OP5 arming terminal points) to which this individual is to have access. Only those doors (up to 32,767) that have already been assigned to the currently selected tenant will appear on this summary. Your host password my further limit which doors appear in this editor (refer to “Limited-access Users” on page 9-15 for more information).

Figure 17-43. Individuals – Door Selection Summary



17. To assign one or more group schedules to the individual, or to assign a secondary group to the individual, perform the following:

a. Select the Groups button. The system displays the Indi-viduals – Group Selection summary (see Figure 17-44) with a listing of the available groups.

Note: If your host password is configured to limit your access to specific groups, the Group Selection Summary will be affected as follows:

✦ Only the groups that your host password allows, as well as any other groups that are influencing the selected individual, will be visible.

✦ For any group that is visible but is not allowed by your host pass-word, you will not be allowed to add it, remove it, or set its priority (move it up or down in the list).

✦ TAC I/NET Seven will not allow you to remove a group that would cause you to lose access to the individual.


Figure 17-44. Individuals – Group Selection Summary



A “~” in front of a group name indicates a global group (available for all tenants).

b. To assign one or more group schedules to the individual, Select the a desired group and click the <- Add button. The selected group will move from the Not Member of list to the Member of list. Repeat as necessary to add multiple groups.

c. If you selected more than one group in Step b, use the Move Up and Move Down buttons to set the desired priority order for the groups on the Member of list.


d. If necessary, you can temporarily supplement the sched-ules that you have assigned to the individual by also assigning a secondary group. Use the following steps:

Note: Secondary group schedules are supported only in door controllers loaded with firmware version 3.01 or later.

✢ Click the Secondary Group Add button. The system displays the Secondary Group editor (see Figure 17-45).

Figure 17-45. Secondary Group Editor



✢ Use the Group drop-down list to select a group. All groups defined for the current tenant and that are not blocked by your host password are included in this list. Global groups are not included.

Refer to “Limited-access Users” on page 9-15 for information about how groups can be blocked.

✢ Enter the Begin date and Begin time. Use the mm/dd/yy format to define the Begin date. Use the 24-hour (military format) to define the Begin time. These parameters determine when the Secondary Group assignment will become active.

✢ Enter the End date and End time. Use the mm/dd/yy format to define the End date. Use the 24-hour (mili-tary format) to define the End time. These parame-ters determine when the Secondary Group assignment will no longer be active.

✢ Select OK to accept the settings. The Secondary Group Editor closes, returning you to the Individuals – Group Selection summary. The Secondary Group is automatically positioned at the top of the Member of list and cannot be moved (“<-- Secondary” appears to the right of this group).

Note: When you assign a Secondary Group to an individual, the Secondary Group Add button changes to Modify. This button becomes unavail-able (i.e., turns grey) until you save the individual record by selecting OK from the Individual Parameters editor. After you save the indi-vidual’s record, you can return to this editor and the Modify button will be available, allowing you to view or modify the secondary group schedule.

e. When finished, select the OK button to return to the Individuals – Door Selection summary, or select Cancel to exit without saving your changes.

18. If you wish to customize the schedule for this individual, perform the following:



a. Choose a door from the available list and select Sched-ules. The system displays the Individuals – Door Sched-ules summary (see Figure 17-46). The schedules listed here are defined in Personnel Schedules on page 17-30.

Note: Each door in the system supports up to 31 unique schedules, a schedule “--” which is “Unselect,” and a schedule “00” which is a “No Access” schedule.

b. Choose a named schedule from the list to enable indi-vidual access to the selected door and select the OK button.


The system displays the Individuals – Door Selection summary (see Figure 17-43).

c. Repeat as required for additional doors.

d. Select Close. The system displays the Individual Parame-ters editor (see Figure 17-42 on page 17-67).

19. Select OK to accept the settings for the new individual.

Figure 17-46. Individuals – Door Schedules Summary



20. If your system prompts you to enter a second host password, the password must be entered before your settings will be accepted (see Figure 17-47). Refer to the Second password required for Individuals parameter on page 17-89 for more information about this option.

21. Upon accepting the new settings, the system displays the Indi-vidual Summary. Repeat Steps 1 through 20 as required to add more individuals.


Display Options

Note: The actual fields displayed within the “Individuals – Display Options” editor will be determined by the access rights associated with your host password. The steps below assume that all fields are displayed. Refer to Chapter 9, Passwords, for more information.

This function allows you to set the presentation order of personnel records information and determine what records to display.

1. From the Individuals Summary (see Figure 17-40) select Option. The system displays the Individuals – Display Options editor (see Figure 17-48).

The information displayed within the Individuals – Display Options editor is divided into columns. If necessary, you can use the mouse to resize the column widths. Refer to “List Boxes” in Chapter 1, TAC I/NET Seven Basics, for more infor-mation.

Figure 17-47. Second Password Prompt



2. Choose a Display order (field number) (1–21) from the drop-down list. Presentation order on the Individuals Summary List (see Figure 17-40) will be based on the chosen setting. The Sort column in the Individuals Summary List will display the content of the field used as the display order field.

Note: When you base the display order on the hexadecimal card number, the Add, Delete, and Copy functions become disabled in the Individ-uals Summary List. Choose some other display order to re-enable the Add, Delete, and Copy functions.

3. In the Individual fields enter the Low and High individual numbers.

4. Activate () or deactivate () Permanent record, Tempo-rary record, and Disabled record.

Figure 17-48. Individuals - Display Options Editor



Enabling any of these options will cause personnel records of that type to be displayed on the Individuals Summary List (see Figure 17-40).

5. Enter search criteria (up to 50 characters) in the options column of the field(s) you wish to use for the search.

These fields are alphanumeric fields that allow you to deter-mine search criteria for data within each field. You may enter up to 50 characters, including the wild card characters “?” and “*”.

6. Select OK. The system displays the Individual Summary (see Figure 17-40).

Field Names

Note: The actual fields displayed within the Field Names editor will be determined by the access rights associated with your host password. The steps below assume that all fields are displayed. Refer to Chapter 9, Passwords, for more information.

Every tenant has an Access Control database table where the unique field names for Fields 3 through 18 are stored. Initially, the names for fields 3 through 18 are the default names (e.g., Field #3, Field #4, etc.). Since each tenant has a separate ACN table, you may customize the field names for each tenant using the field names editor. For example, field #3 may be titled “Department”.

1. From the Individuals Summary (see Figure 17-40) select Field Names. The system displays the Field Names editor (see Figure 17-49).

Note: These field names will be applied to all individuals belonging to this tenant.

The information displayed within the Field Names editor is divided into columns. If necessary, you can use the mouse to resize the column widths. Refer to “List Boxes” in Chapter 1, TAC I/NET Seven Basics, for more information.

2. Enter the Field names as required.



3. Select OK. The system displays the Individuals Summary (see Figure 17-40).

Allocate RangesThis function allows you to add a number of unused individual numbers without adding each individual separately. Once you allo-cate a range you may enter the individual information using the Modify function from the Individuals Summary List (see Figure 17-40).

Note: Using this editor generates an “individual edit” audit trail message to provide a high-level audit trail for individual updates. The message contains the date and time the edit was performed, the site number, the individual number, and the initials of the person who performed the edit.

1. From the Individuals Summary (see Figure 17-40 on page 17-65) select Alloc Range. The system displays the Allocate Range editor (see Figure 17-50).

Figure 17-49. Individuals – Field Names Editor



2. If your system prompts you to enter a second host password, the password must be entered before your settings will be accepted (see Figure 17-47 on page 17-78). Refer to the Second password required for Individuals parameter on page 17-89 for more information about this option.

3. In the First individual number field enter the starting indi-vidual number. The default is the next available number.

4. In the Number of individuals field enter the number of indi-viduals that you want to assign.

5. To assign one or more group schedules, perform the following:

a. Select the Doors button. The system displays the Individ-uals - Door Selection summary (see Figure 17-43 on page 17-73).

b. Select the Groups button. The system displays the Indi-viduals – Group Selection summary (see Figure 17-44 on page 17-74) with a listing of all currently defined groups.

c. Select the desired group and click the <- Add button. The selected group will move from the Not Member of list to the Member of list. Repeat as necessary to add multiple groups.

d. If you selected more than one group in Step c, use the Move Up and Move Down buttons to set the desired priority order for the groups on the Member of list.

Figure 17-50. Allocate Range Editor




e. When finished, select the OK button to return to the Individuals – Door Selection summary, or select Cancel to exit without saving your changes.

6. If you wish to customize the schedule for this range of indi-viduals, perform the following:

a. Choose a door from the available list and select Sched-ules. The system displays the Individuals – Door Sched-ules summary (see Figure 17-46 on page 17-77). The schedules listed here are defined in Personnel Schedules on page 17-30.

Note: Each door in the system supports up to 31 unique schedules, a schedule “--” which is “Unselect,” and a schedule “00” which is a “No Access” schedule.

b. Choose a named schedule from the list to enable indi-vidual access to the selected door and select the OK button.


The system displays the Individuals – Door Selection summary (see Figure 17-43).

c. Repeat as required for additional doors.

d. Select Close. The system displays the Individuals summary (see Figure 17-40 on page 17-65).

7. Select OK. The system displays the Individual Summary (see Figure 17-40 on page 17-65).



Copying an Individual

Note: Your ability to copy an individual will depend upon the privileges assigned to your host password. Refer to Chapter 9, Passwords, for more information.

If the Second password required for Individuals option is acti-vated () in the Options editor, TAC I/NET Seven will require entry of a second operator’s host password before allowing you to copy an individual. Refer to “Options” on page 17-87 for more information.

1. From the Individual Summary choose the individual whose parameters you want to copy.

2. Select Copy. The system displays the Individuals – Copy dialog box.

3. Enter the target New individual number. The default is the next available number. The range of valid numbers for this field will depend on the First individual number and the Number of individuals defined for the tenant (refer to “Adding a New Tenant” on page 17-51).

Note: The Card Number fields, described in the following step, are displayed only if the privileges assigned to your host password allow you to view and modify this information.

4. Enter the target Card Number that is to receive these parame-ters. This is the value encoded on the individual’s key/card. You may enter the card number as either a hexadecimal (base 16) or decimal (base 10) value; the other scale will be calcu-lated automatically.

5. Select OK to accept the settings for the new individual.

6. If your system prompts you to enter a second host password, the password must be entered before your settings will be accepted (see Figure 17-47 on page 17-78). Refer to the Second password required for Individuals parameter on page 17-89 for more information about this option.

7. Repeat Steps 1 through 6 as required to copy additional indi-viduals.



Deleting an Individual

Note: When you delete an individual from your access control system, TAC I/NET Seven sends a message to every door controller that controls a door through which the individual has access.

Your ability to delete an individual will depend upon the privileges assigned to your host password. Refer to Chapter 9, Passwords, for more information.

If the Second password required for Individuals option is acti-vated () in the Options editor, TAC I/NET Seven will require entry of a second operator’s host password before allowing you to delete an individual. Refer to “Options” on page 17-87 for more information.

TAC I/NET Seven can be configured to temporarily store deleted individuals in a recycle bin (refer to the Recycle bin enable parameter in Step 12 on page 17-91). This feature allows you to restore a deleted individual to an active status as long as the indi-vidual record resides in the recycle bin.

Note: If the recycle bin feature is not enabled when you delete an indi-vidual, or if the deleted individual record is purged from the recycle bin, then the individual is permanently purged from the system.

1. From the Individual Summary (see Figure 17-40) choose the individual you want to delete.


3. Select Yes. to delete the selected individual from the list.

4. If your system prompts you to enter a second host password, the password must be entered before the individual will be deleted (see Figure 17-47 on page 17-78). Refer to the Second password required for Individuals parameter on page 17-89 for more information about this option.

5. Repeat Steps 1 through 4 as required to delete additional indi-viduals.


PIN Generation Access Control

PIN Generation

Note: TAC I/NET Seven’s 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.

The PIN Generation utility allows you to generate a list of personal identification numbers (PINs) for specific individuals. The PINs generated with this utility are the same as the PIN viewed from the Individual Parameters editor. TAC I/NET Seven calculates the PIN based upon the card number and issue number defined for an indi-vidual. If you change an individual’s card number or issue number, a new PIN will be generated. This utility enables you to view more than one PIN at a time and to print a list of PINs.

Access the PIN Generation utility by selecting Access Generate PINs. The PIN Generation editor displays, as shown in Figure 17-51.

Figure 17-51. PIN Generation Editor


Access Control Options

1. Choose a Tenant from the drop-down list. Within this list, the number that follows a tenant’s name is an indication of the number of keys allocated to that tenant.

Upon selecting a tenant, the Starting key field will be set to the lowest key value applicable to the tenant. The Ending key field will be set to the highest key value applicable to the tenant.

2. Enter the first key/card number in the Starting Key field.

3. Enter the last key/card number in the Ending Key field.

4. Select Calculate to generate the PINs. The key/card numbers and their associated PINs will fill the table in the lower half of the editor, as shown in Figure 17-52.

5. To preview the PIN report on the screen, activate () the Print preview option, enter the number of pages to preview, and select Print. The print preview displays. Click the Windows Close button (X) in the top right corner to move through the preview pages and close the preview on the last page.

To send the report to the printer, deactivate () the Print preview option and select Print.

Options

This editor allows you to enable an I/DISC reader and determine where audit trail messages will be sent.

Figure 17-52. PIN Table


Options Access Control

1. Select Access Options, or click the Options tool on the Access toolbar. The system displays the Options Editor (see Figure 17-53).

Note: The Supply card number from reader option described in the following step 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.

2. Activate () or deactivate () the Supply card number from reader option.

Enable this option if you want to use an I/DISC wand or a Wiegand reader to enter card numbers in the Individuals editor.

Figure 17-53. Options Editor



3. Activate () or deactivate () the Second password required for Individuals option.

With this option enabled, TAC I/NET Seven will require entry of a second operator’s host password before allowing you to add, delete, copy, or modify individual records. Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for details about this feature.

4. Select an Audit trail - distribution group (1–4). The mask that you define in the following step will be applied to this group.

5. Define the Audit trail - distribution mask. Set each of eight masking positions to the desired state, either activated () or deactivated ().

6. Enter a number (1–1023) in the Audit trail - cell number field. A cell number of zero (default) means that no data will be stored.

7. Choose a DPU dial type from the drop-down list. The following options are available:

✧ Immediately – This setting causes TAC I/NET Seven to immediately dial affected remote sites following Access Control. However, the DPU dial delay will be honored before dialing begins.

✧ Scheduled – This setting allows you to choose a time when TAC I/NET Seven will dial remote sites following Access Control changes.

✧ Never – This setting suppresses automatic dialing to a remote site following Access Control changes. The changes will not be sent to the remote DPU until a connection is made either manually, or through some other automatic dialing function (such as message uploads). In this case, you must manually dial the remote site and perform a station restore to the affected DPU.

Note: Performing the following access control changes will cause the system to immediately dial affected remote sites, regardless of the DPU Dial Type setting:


Options Access Control

✧ Changing an individual or group record type to “Temporary.”

✧ Modifying an individual or group temporary schedule.

Refer to TCON300, TAC I/NET Seven Technical Reference Guide, for more information about the access control “Dial After Edit” function.

8. If you selected “Immediately” in Step 7, enter the DPU dial delay (up to 60 minutes). This sets the amount of time the system will wait after the Access Control edit, before dialing the remote site.

9. If you selected “Scheduled” in Step 7, enter a time (24-hour format) in the DPU dial schedule field. This is the time of day when TAC I/NET Seven will dial remote sites affected by changes to the Access Control system.

10. Activate () or deactivate () the User defined PIN check box. When activated, the default PIN in the Individual Parameters editor can be changed to a customized number (refer to “Adding an Individual” on page 17-65).

Note: This feature requires door controller firmware version 2.30 or later. You must use system-generated PINs for door controllers with a firm-ware revision prior to 2.30.

11. Select the PIN algorithm 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 want the system to 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 not available if the User defined PIN check box is disabled ().



✧ Standard – Choose this setting if your access control system is configured to use any reader type other than Wiegand 66. If the User defined PIN check box is acti-vated, this algorithm generates a default PIN for new individuals, which the operator can edit. If the check box is not activated, this algorithm generates a read-only PIN.

✧ Wiegand 66 – Choose this setting only when your access control system is configured to use Wiegand 66 readers. If the User defined PIN check box is activated, this algo-rithm generates a default PIN for new individuals, which the operator can edit. If the check box is not activated, this algorithm generates a read-only PIN.

12. Activate () or deactivate () the Recycle bin enabled option. The default for this field is activated.

Activate this option to have TAC I/NET Seven temporarily store deleted access control records in a recycle bin. Using this feature, you can restore deleted individual, group, and tenant records at a later time. You can also purge the records from the recycle bin in order to permanently delete them.

13. When you activate the recycle bin feature in Step 12, the Recycle bin autopurge age parameter becomes available. Use this parameter to have TAC I/NET Seven automatically purge records that have been deleted for a specified number of days (from 0 to 127). A setting of zero (0) prohibits TAC I/NET Seven from purging deleted records because of their age.

14. The Empty recycle bin at log off parameter becomes avail-able when you active the recycle bin feature in Step 12. This feature allows you to configure TAC I/NET Seven to automat-ically purge deleted records from the recycle bin when the user logs off.

Choose any of the following three options for this parameter:

✧ Never – This setting prevents TAC I/NET Seven from purging deleted records from the recycle bin at system log off.


Individual Activity Manager Access Control

✧ Prompt – This setting causes TAC I/NET Seven to display a prompt at system log off if deleted records reside in the recycle bin. The prompt allows the user to choose whether or not the records will be purged.

✧ Always – This setting allows TAC I/NET Seven to silently purge the recycle bin at system log off.

15. If desired, select the Unique user field. Any of the 16 user-defined fields may be selected from the drop-down. The designated field, if populated, must contain a unique entry for all individuals, across all tenants.

If you edit this selection, a warning message will appear when you exit the editor, warning you that existing entries are not checked for uniqueness. Select OK to continue, or Cancel to cancel your change (to this field only) and remain in the editor.

16. If necessary, enable and configure the Individual Activity Manager feature by selecting the Configure button. For more information about this feature, refer to “Individual Activity Manager” below.

17. Choose a Default anti-passback setting of Hard, Soft, or Graced. The setting you choose here will be used as the initial setting of the ABP parameter in the Individual Parameters Editor (see Figure 17-42 on page 17-67) when you are adding an individual to the access control system.


Individual Activity Manager

The Individual Activity Manager (see Figure 17-54) allows TAC I/NET Seven to automatically disable the access privileges of indi-viduals whom have not used their key/card within a specified amount of time. TAC I/NET Seven displays this editor when you select the Individual Activity Manager Configure button from the Access Control Options editor.


Access Control Individual Activity Manager

The tenant selections that you make in this editor are not global-ized; therefore, you must visit this editor and select the appropriate tenants on each host workstation that will monitor door controller activity.

Caution: A TAC I/NET Seven host workstation can only monitor activity at a door if the appropriate tenant is selected in the Individual Activity Manager editor and at least one of the following criteria are met:

✦ The message masking you've defined for your system allows the host workstation to receive transaction messages from the door controller.

— OR —

✦ The host workstation shares the same filemaster as another host workstation that receives transaction messages from the door controller and has the appropriate tenant selections. In this case, the door controller activity is globalized daily at 12:30 AM.

Figure 17-54. Individual Activity Manager


Access Initiated Control Access Control

An individual can become disabled because of inactivity at “moni-tored” doors, even though the individual has had sufficient activity at un-monitored doors. Ensure that your system's message masking or file equalization allows for proper monitoring of door controller activity.

Configure individual activity management as follows:

1. Within the list of tenants, select () each tenant that this host workstation will monitor for activity. You can use the All Yes and All No buttons as necessary to help speed the selection process.

2. Specify the Duration of inactivity that will cause individuals to become disabled.

a. Choose a duration setting of None, Daily, Weekly, Monthly, or Yearly. If you choose None, no activity moni-toring will be performed.

b. Choose a Duration Interval setting. The available range for this value varies depending on the duration you spec-ified in the previous step. Regardless of which duration setting you chose, the maximum limit is equivalent to 4 years.

3. Select OK to accept these settings.

Note: If you would like to exclude specific individuals from activity moni-toring, you can use the Individual Parameters Editor to set the indi-vidual's IAM parameter to Graced.

Access Initiated Control

The Access Initiated Control (AIC) function lets you initiate a control action in response to an access transaction for a selected tenant number and one or more key/card numbers. Although the control action is to a single point, it can always be extended through the Event Sequences and Event Definitions editors.

Each DPI/MCI will support up to 64 AIC actions, regardless of how many tenants are defined.


Access Control Access Initiated Control

1. If you are not connected to the desired controller, perform the following steps from the host. Otherwise, skip to step 2.

a. Select Access Access Initiated Control, or click the Access Initiated Control tool on the Access toolbar. The system displays the Controller Selection Summary (see Figure 17-55).

b. Choose a controller from the list and select the Select button. The system displays the Access Initiated Control summary (see Figure 17-56).

c. You may now add, modify, copy, or delete AIC actions. Procedures for each of these options are described below.

d. Select Close to leave this editor.

2. If you are connected to the desired controller, perform the following steps:

a. Select Edit Controller Access Initiated Control, or click the Access Initiated Control tool on the Controller toolbar. The system displays the Access Initiated Control list (see Figure 17-56).

b. You may now add, modify, copy, or delete AIC actions. Procedures for each of these options are described below.

c. Select Close to leave this editor.

Figure 17-55. Controller Selection Summary



Add Access Initiated Control1. Choose an entry from the Access Initiated Control list (see

Figure 17-56) and select Add. The system displays the Access Initiated Control editor (see Figure 17-57).

2. Enter the AIC number (1–64). The system supplies the next available number.

3. Enter the AIC name (up to 16 characters).

4. Choose the Tenant to which this AIC number applies from the drop-down list.

5. Enter a valid discrete output point address in the Target point field.

Whenever one of the selected Message transactions is processed for a matching tenant code and individual number (specific individual numbers are defined in the Individual selection editor, below), a control action (start/stop) will be issued to this point.

Note: These control actions are the equivalent of an “Event control” command.

Figure 17-56. Access Initiated Control Summary



6. Activate () or deactivate () the Use all individuals in range option. Enable this option if you want to use all indi-viduals for the selected tenant.

7. Activate () the APB zone enable option if you wish to asso-ciate this AIC entry with a specific zone. For example, you may wish to initiate control when a “Reader entry” message occurs for zone 1.

8. If you activated the APB zone enable option, specify an APB zone.

9. Choose a control action (None, Start, or Stop) for any of the Message/Action Detail parameters. The Stop action is not available for any of the “Denied...” messages listed within this section.

Figure 17-57. Access Initiated Control Editor



Note: The following Message/Action Detail parameters are not used if the DPU or SCU1284 is loaded with firmware revision 2.1x or earlier:

✧ Reader entry w/PIN

✧ Reader entry w/PIN – elevator

✧ Reader exit w/PIN

✧ Duress entry

✧ Duress elevator

✧ Duress exit

✧ Denied entry – PIN

✧ Denied exit – PIN

10. Select the Doors button. The system displays the Access Initi-ated Control Doors (see Figure 17-58). This lists all doors associated with the selected DPI/MCU. You must now decide which doors will have the AIC action assigned to them.

11. Select All Yes, All No, or each door individually. Doors marked with [X] will have the AIC action assigned to them.

12. Select Close to save the selections. The system displays the Access Initiated Control editor (see Figure 17-57 on page 17-97).

Figure 17-58. Access Initiated Control Doors



Note: If Use All Individuals in Range was enabled in Step 6 above, go to Step 17.

13. Select the Individuals button. The system displays the Access Initiated Control Individuals editor (see Figure 17-59). This summary lists each individual by Individual number, and includes the last name, first name, group assignment, and record type.

14. Choose individuals from the list. An [X] in the Select column means that this individual’s key/card will trigger the selected control action.

The following editor functions describe the individual selec-tion process:

✧ The lowest individual number selected is displayed in the First selected field of the Individual Range information. This becomes the base individual number. The system limits each AIC definition to individual numbers within a 500-individual range unless you use all individuals for

Figure 17-59. Access Initiated Control Individual Editor



the selected tenant (refer back to Step 6 in this proce-dure). Therefore, if the base individual number is 200, the highest individual number you may select is 699 for a range of 500 individuals. Even if only some of these 500 individual are selected, the highest individual number selectable remains at 699. This individual number is displayed in the Maximum allowed field of the Indi-vidual Range information. In order to select a higher individual number, you must create another AIC defini-tion.

✧ Once you have selected at least one individual, the All No button becomes enabled. You may use this button to deselect all selected individuals.

✧ Once you have selected at least two individuals, the All Yes button becomes enabled. You may use this button to automatically select all individuals between the lowest and highest individual numbers selected.

✧ Use the Group drop-down list to limit the All Yes and All No buttons to individual numbers in the selected group. This filtering applies only to the All Yes and All No buttons — it does not change the displayed list of individuals. Therefore, you may continue to manually select or deselect individuals from any group.

Note: If the selected group includes other groups, listed individuals assigned to the secondary group(s) will also be affected by the All Yes and All No buttons.

15. Once you have selected the necessary individuals, select Close to save the selections. The system displays the Access Initiated Control editor (see Figure 17-57 on page 17-97).

16. Select OK to save the settings. The system displays the Access Initiated Control list (see Figure 17-55 on page 17-95).

17. Repeat Steps 1 through 16 as required to add more AIC func-tions.




Modifying Access Initiated ControlModifying an AIC is similar to adding an AIC. Use the same proce-dure as described in “Add Access Initiated Control” on page 17-96 except that you choose a schedule that already exists and select the Modify button from the Access Initiated Control list (see Figure 17-56) rather than the Add button.

Copying Access Initiated Control1. From the Access Initiated Control Summary (see Figure 17-56

on page 17-96) choose the AIC function that you want to copy and select Copy. The system displays the Access Initiated Control editor (see Figure 17-57 on page 17-97).

2. Set the parameters (including Doors and Individuals) as described in “Add Access Initiated Control” on page 17-96.

3. Select OK. The system copies the AIC function and displays the Access Initiated Control Summary (see Figure 17-56 on page 17-96).

4. Repeat Steps 1 through 3 as required to copy other AIC func-tions.


Deleting Access Initiated Control1. From the Access Initiated Control list (see Figure 17-56 on

page 17-96) choose the AIC function that you want to delete and select Delete. The system displays the Delete confirma-tion dialog box.

2. Select Yes. The system deletes the AIC function and displays the Access Initiated Control list (see Figure 17-56 on page 17-96).

3. Repeat as required to delete more AIC functions.



User Search Access Control

User Search

TAC I/NET Seven displays the User Search dialog box (see Figure 17-60) when you select Access User Search from the main menu. Use this dialog to quickly locate the access control record stored for a particular individual.

1. Use any combination of the following fields to locate the desired record:

• Last Name – Type the user's last name (up to 50 charac-ters).

• First Name – Type the user's first name (up to 50 charac-ters).

• Tenant – Use this drop-down list to narrow the search to a particular tenant, or to search through all tenant records.

• User ID – Type the User ID (1 to 32000) assigned to the individual.

• Custom Field – Choose a custom field from the drop-down list and then type the text that you wish to find (up to 50 characters).

The search is updated with each character that you type and the result is displayed in the list.

Figure 17-60. User Search


Access Control SCU Tamper

2. The result list shows all records returned by the search. Locate and highlight the desired record in the list.

3. Once you have located and highlighted the desired record, the following options become available:

• Picture – Select this option to display a User Search - Picture dialog. This dialog shows an image of the user and provides other information.

• Tree – Select this option to display the user in the System View interface.

• Zoom – Select the Zoom button to open the Individuals Parameter Editor. You can then view or change the indi-vidual's record as necessary.

4. If necessary, use the Clear button to clear all fields. This can be especially useful when you are preparing to perform a new search.

SCU Tamper

TAC I/NET Seven displays the SCU Tamper summary when you select Access SCU Tamper, or when you connect to an SLI and select Edit Controller SCU Tamper from the main menu. The SCU Tamper summary lists all of the SCUs defined in TAC I/NET Seven.

Figure 17-61. SCU Tamper Summary


SCU Tamper Access Control

Use this summary to view and set the tamper settings in your system’s SCUs.

SCU Tamper SummaryThe columns in the SCU Tamper summary show the following information:

✦ Address — This is the system address of the SCU.

✦ Front — A “Y” in this column indicates that the SCU is configured to monitor the optical tamper sensor mounted on the front of the controller.

✦ Rear — A “Y” in this column indicates that the SCU is configured to monitor the optical tamper sensor mounted on the rear of the controller.

✦ Switch —A “Y” in this column indicates that the SCU is configured to monitor a mechanical tamper switch connected to the controller.

✦ NC — A “Y” in this column indicates that the tamper switch is defined as a normally-closed switch.

Editing Tamper SettingsUse the following steps to edit an SCU's tamper settings:

1. Highlight an SCU in the list.

2. Click Select. The system displays the SCU Tamper Settings editor (Figure 17-62), allowing you to edit the selected SCU's tamper settings.

3. Activate any of the following options as necessary:

✧ Front Optical Tamper — Activate () this option to enable the SCU's front optical tamper sensor.

✧ Rear Optical Tamper — Activate () this option to enable the SCU's front optical tamper sensor.

✧ Tamper Switch — Activate () this option to have the SCU monitor a mechanical tamper switch wired to the controller.


Access Control SCU Tamper

✧ Normally-open/Normally-closed — Select the option appropriate for the installed tamper switch. For example, if you wire a normally-open tamper switch to the SCU, and the switch will be closed under tamper conditions, then you would select the “normally-open” option.

4. Click OK to save the tamper settings, or select Cancel to close this editor without saving. The system returns to the SCU Tamper summary.

5. Click Close to close the SCU Tamper summary.

Figure 17-62. SCU Tamper Settings


SCU Tamper Access Control


C H A P T E R22

18

© 2001–2010 SchTCON299–05/10

Intrusion Alarm System

Note: The editors used for configuring an intrusion alarm system will not be available unless you connect to a 7798C with firmware revision 1.07 or later.

This chapter provides instructions on how to use the TAC I/NET Seven editors that are associated with configuring an Intrusion Alarm System (IAS). Refer to the following documents for more information about the IAS.

✦ TCON300, TAC I/NET Seven Technical Reference Guide

✦ TCON314, Intrusion Alarm System Installation Guide

✦ TCON315, Intrusion Alarm System Operator Guide

Before You Begin

Before you begin configuring the IAS, you must have already defined all of the points that will be associated with OP5 arming terminals, sensors, zones, warning devices, and monitoring points. If necessary, refer to TCON314, “Intrusion Alarm System Installa-tion Guide,” for instructions.

Note: If you delete an IAS 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.

Complying with EN50131

EN50131-1 is the pan-European standard for Intruder and Hold Up Alarm Systems. The TAC I/NET Seven system provides intruder detection capablilities only — no hold-up functions are provided.


Intrusion Alarm System Configuration Intrusion Alarm System

Depending on how it is configured, the IAS can meet Grade 2 or Grade 3 of the EN50131-1 standard and Alarm Class 2 of SSF 1014. The IAS also meets the environmental class II requirements of EN50131-1.

It is the responsibility of the person(s) designing/installing the IAS to configure the system to meet the requirements of EN50131-1. If the system is configured in such a manner as to render it non-compliant with EN50131-1, all compliance labeling must be removed.

Intrusion Alarm System Configuration

TAC I/NET Seven displays the Intrusion Alarm System editor (see Figure 18-1) when you select Edit Controller Intrusion Alarm System from TAC I/NET Seven's main menu. Use this editor to configure an Intrusion Alarm System.

1. Activate () or deactivate () the Allow CLAN control from arming terminal option. While this option is activated (), level 3 IAS operators will be permitted to use an OP5 arming terminal to enable or disable the 7798Cs ability to communi-cate on the CLAN.

When an IAS operator attempts to disable CLAN communi-cation from an OP5 arming terminal, the request will be ignored if the Allow CLAN control from arming terminal option is deactivated (). If the option has been activated (), the operator's request will be honored and CLAN communications will stop immediately. This will cause TAC I/NET Seven hosts to exhibit the following behavior:

• A "Station lost" message will appear in AMT.

• IAS points on graphic pages will show question marks (????).

• If a TAC I/NET Seven operator attempts to connect to the IAS's 7798C, a "No entries in database" message will be displayed and no connection will be made.

• The IAS editor will be inaccessible for as long as CLAN communications at the IAS's 7798C are disabled.


Intrusion Alarm System Intrusion Alarm System Configuration

Note: Whenever power is cycled on the IAS's 7798C, the device will be permitted to communicate on the CLAN for the first five minutes after power up, regardless of whether or not CLAN communications have been disabled from an OP5 arming terminal.

2. Activate () or deactivate () the Disable IAS host alarm ack option. While this option is activated (), no TAC I/NET Seven operator can acknowledge an IAS alarm from within TAC I/NET Seven. In this case, the only way to acknowledge an IAS alarm will be for an authorized IAS operator to perform the acknowledgement from an OP5 arming terminal.

Figure 18-1. Intrusion Alarm System Editor



3. Configure the IAS to use warning devices by performing the following steps:

a. If the IAS will control an internal warning device, use the Internal point drop-down list to select the appropriate control point. The IAS will issue commands to the selected point in order to activate or deactivate the internal warning device.

b. Set the Duration parameter to the maximum number of seconds (0 to 900 in 5-second increments) that the internal warning device should remain on once activated.

c. If the IAS will control an external warning device, use the External point drop-down list to select the appropriate control point. The IAS will issue commands to this point in order to activate or deactivate the external warning device.

d. Set the Duration parameter to the maximum number of seconds (0 to 900 in 5-second increments) that the external warning device should remain on once activated.

4. If necessary, use the Ext warning device delay field to delay the operation of the external warning device for up to 1200 seconds (0 to 1200 in 5-second increments).

5. Use the Off-route Alarm field to configure the IAS to recheck off-route intrusion signals that may occur during an active entry procedure.

When an off-route alarm occurs during an active entry proce-dure, the IAS's internal warning device turns on. If the Off-route Alarm field setting is 0, the internal warning device will remain on until the zone is unset or until the warning device's maximum duration has been reached. If you set the Off-route Alarm field to a non-zero value (up to 255 seconds), the off-route alarm will be rechecked after the specified number of seconds.

After being rechecked, if the off-route sensor is no longer detecting an intruder, the internal warning device will turn off. However, if the intrusion signal is still active when the


Intrusion Alarm System Intrusion Alarm System Configuration

sensor is rechecked, the internal warning device will remain on until you unset the zone or until the warning device’s maximum duration expires.

6. Set the Login attempt disable count parameter to a value from 3 to 15. This determines the number of consecutive times that a user can unsuccessfully attempt to log into the IAS at an OP5 arming terminal before being temporarily locked out.

7. Set the Count to inhibit parameter to a value from 3 to 10 events. This determines how many matching signals from a single sensor will be recorded in the IAS's event log before it stops storing events from the sensor. This prevents a single sensor from filling the event log with an event that keeps repeating. However, while a sensor is operating in the soak mode, the event log will not limit the number of events it records from the sensor.

8. Use the SubLAN fault drop-down list to select a point that will be used to indicate whether or not a fault is being detected on the SubLAN. The IAS must constantly monitor the subLAN to ensure that devices are communicating prop-erly. If communication fault is detected, the selected point will be commanded to indicate a fault condition.

9. Use the Restart fault drop-down list to select a point that will be used to indicate whether or not the 7798C in the IAS has restarted. If the 7798C ever restarts (for example, following a power outage that exceeds the system's backup battery dura-tion), as the 7798C restarts the selected point will be commanded to a fault condition and then back to normal. The purpose of this is to cause the point that you set for this parameter to appear in the Active Sensors summary on the OP5 following a 7798C restart.

10. The read-only System sensors field indicates how many points have been defined as system status points or as common sensors.



Use the Select button to add or remove system status points and/or common sensors. When you select this button, the System Sensor Selection editor opens. Refer to “System Sensor Selection” on page 18-7 for more information.

11. Use the Arming Terminals buttons to add, delete, or modify OP5 arming terminals.

• Add – Use this button to add an OP5 arming terminal to the system. This causes TAC I/NET Seven to display the Arming Terminal Configuration editor. Refer to “Arming Terminal Configuration” on page 18-11 for more infor-mation.

• Delete – Use this button to delete an OP5 arming terminal from the system. When you highlight an arming terminal and select Delete, the system prompts you to confirm the deletion. Click Yes to delete the arming terminal or click No to cancel the delete request.

• Modify – Use this option to edit the highlighted OP5 arming terminal's parameters. This causes TAC I/NET Seven to display the Arming Terminal Configuration editor. Refer to “Arming Terminal Configuration” on page 18-11 for more information.

12. The read-only Access Levels section shows the current settings for user access levels. You can modify these settings by clicking the Level Setup button at the bottom of the editor. This will cause the Intrusion Alarm System Access Level Setup editor to appear. Refer to “IAS Access Level Setup” on page 18-10 for more information.

13. Use the Instrusion System Zones buttons to add, delete, or modify zones.

• Add – Use this button to add a zone to the system. This causes TAC I/NET Seven to display the Intrusion Alarm Zone Configuration editor. Refer to “Intrusion Alarm Zone Configuration” on page 18-14 for more informa-tion.

• Delete – Use this button to delete a zone from the system. When you highlight a zone and select Delete, the system prompts you to confirm the deletion. Click Yes to delete the zone or click No to cancel the delete request.


Intrusion Alarm System System Sensor Selection

• Modify – Use this option to edit the highlighted zone's parameters. This causes TAC I/NET Seven to display the Intrusion Alarm Zone Configuration editor. Refer to “Intrusion Alarm Zone Configuration” on page 18-14 for more information

14. Select OK to accept your changes and close the editor. If you click Cancel, no modifications to the IAS will be saved.

System Sensor Selection

TAC I/NET Seven displays the System Sensor Selection editor (see Figure 18-2) when you click the Select button in the Intrusion Alarm System editor in order to define system status points and/or common sensors. Additionally, you can use this editor to define an ARC notification delay for any EPS Fault points in your system.

This editor lists the DA and DI points defined in your TAC I/NET Seven system. Any of these points that have not been assigned to a

Figure 18-2. System Sensor Selection Editor


System Sensor Selection Intrusion Alarm System

zone are available for selection as either of the following types of IAS points:

✦ System status point – System status points are not associated with zones. Abnormal conditions reported from system status points do not cause zones to go into alarm but do prevent you from being able to set zones. These conditions may also cause the IAS to produce audible notifications locally and/or produce remote notifications to an alarm receiving center, depending on your system’s configuration.

✦ Common sensor – Common sensors contribute to the opera-tion of all zones in the IAS. If a common sensor detects an abnormal condition, the status of all zones will change to a state representative of the condition (for example, if a common sensor detects a fault, the status for all zones may change to Fault).

Adding a System Status PointActivate () the selection box in the System column for each point you wish to define as an IAS system status point. If you acti-vate this box on a point that is already defined as a common sensor, when your changes are saved the point will become a system status point and will no longer affect zones.

Adding a Common SensorActivate () the selection box in the Common column for each point you wish to define as an IAS common sensor. If you activate this box on a point that is already defined as a system status point, when your changes are saved the point will become a common sensor and its status will affect all zones.

Delaying ARC Notification of EPS Fault SignalsFor any system point the will be used as an EPS Fault point (i.e., a point used to detect a loss of power from the transformer connected at TB1of an SCU), you can define an ARC notifcation delay from 0 to 3600 seconds (i.e., up to 1 hour). EN50131 allows notification to an ARC to be delayed for up to one hour for EPS faults. This makes it possible for the IAS to experience a short-term AC power outage (i.e., an outage of less than 1 hour) without


Intrusion Alarm System System Sensor Selection

reporting it to the ARC. Because the EPS Fault point is a system point, the occurance of an EPS Fault will immediately make all unset zones become unsettable until power is restored and an authorized user acknowledges the fault(s).

To delay ARC notification of EPS fault signals1. Activate () the selection box in the EPS column for each

system status point that will be used as an EPS Fault point.

2. At the top of the editor, use the ARC dial delay parameter to set a delay of up to 3600 seconds.

3. Select OK to accept your settings. The System Sensor Selec-tion editor will close.

With the system configured to delay EPS fault notifications, the occurrance of an EPS fault will be processed as follows:

✦ At the moment an AC power outage occurs, the EPS fault point will go into its overriden not-ready condition (typically Fault; refer to “Overriding a Point’s Not-ready Condition” below) and all unset zones will become unsettable.

✦ If AC power returns before the ARC dial delay expires, no EPS fault message will be sent to the ARC.

✦ If AC power is still off when the ARC dial delay expires, an EPS Fault message will be sent to the ARC.

✦ When a user restores (i.e., acknowledges) an EPS fault point that has returned to normal, an EPS Fault Restore message will be sent to the ARC and all unset zones will again become settable.

Overriding a Point’s Not-ready ConditionYou can override the not-ready condition of a system status point or common sensor. This allows the IAS to process the not-ready condition as a fault or tamper condition. Refer to “Overriding a Point's Not-ready Condition” on page 18-20 for more information.


IAS Access Level Setup Intrusion Alarm System

IAS Access Level Setup

TAC I/NET Seven displays the IAS Access Level Setup editor (see Figure 18-3) when you select Level Setup from the Intrusion Alarm System Configuration editor (see Figure 18-1). Use this editor to define the permisions that will be granted to IAS users based on a user's access level.

This editor has two groups of parameters. One group is for defining Level 2 permissions and the other group is for defining Level 3 permissions. Buttons are also provided in the upper right corner of editor that allow you to quickly set all parameters to default settings appropriate for a particular security grade (either grade 2 or grade 3).

To quickly set all parameters to default settings✦ For a grade 2 system, click the Grade 2 button

— OR —

✦ For a grade 3 system, click the Grade 3 button

Figure 18-3. IAS Access Level Setup Editor


Intrusion Alarm System Arming Terminal Configuration

To customize access level permissions1. In the Level 2 permissions section, define permissions for

access level 2 users by activating () or deactivating () permissions for each of the following conditions:

• Intrusion – Choose permission that will be granted to a user at access level 2 when that user is dealing with an Intrusion alarm.

• Tamper – Activate () each permission that will be granted to a user at access level 2 when that user is dealing with an Tamper alarm.

• Fault – Activate () each permission that will be granted to a user at access level 2 when that user is dealing with an Fault alarm.

2. Using the Level 3 permissions section, repeat step 1 to define permissions for access level 3 users.

3. Select OK to accept these settings and close the editor.

For unsupervised discrete inputs, you can define overrides on a per-sensor basis if you wish to create exceptions to these settings.

Arming Terminal Configuration

TAC I/NET Seven displays the Arming Terminal Configuration editor (see Figure 18-4) when you add or modify an arming terminal from the Intrusion Alarm System Configuration editor.

Use this editor to define up to four OP5 arming terminals for your intrusion alarm system.

1. If you are adding a new arming terminal, use the Id field to assign a number (from 1 to 4) to the terminal. If you are modify an existing terminal, this field will be read-only.

2. Use the Point drop-down list to choose the DO point assigned to the OP5 arming terminal. This point must have already been configured as a door point and its address must be LLSS2808, LLSS2908, LLSS3008, or LLSS3108 (where LL = link number and SS = station number) in order for it to appear in the drop-down list.


Arming Terminal Configuration Intrusion Alarm System

3. Use the Location drop-down list to specify a location for the OP5 arming terminal. This will affect what type of indications are presented at the OP5 arming terminal when zones get set or unset, or when an alarm, fault, tamper, or trouble condi-tion occurs within a zone.

Only zones that have already been defined will be included in the drop-down list. If you have not already added the neces-sary zone to the system, you can temporarily set the arming terminal's location to "No Zone." Remember to reset the arming terminal's location later, after you have added the necessary zone.

4. Enter a value (from 5 to 30 seconds) for the Communica-tions loss detect parameter. The SLI constantly quick-polls its subLAN devices. If the OP5 arming terminal does not respond to the quick-polls within the number of seconds you enter for this parameter, an "MCU lost" event will occur.

Figure 18-4. Arming Terminal Configuration Editor


Intrusion Alarm System Arming Terminal Configuration

5. Enter a value (from 15 to 180 seconds) for the Entry complete parameter. This parameter is only used when the zone is defined with an entry route. This parameter deter-mines how long after entering a set zone the user will have to reach the OP5 arming terminal, login, and unset the zone. If the user does not unset the zone within the permitted time, the zone will go into alarm.

6. Enter a value (from 15 to 180 seconds) for the Exit complete parameter. This parameter is only used when the zone is defined with an exit route. This parameter determines how long after issuing a "Set" command to a zone that the user will have to exit the zone. If the user does not exit the zone within the permitted time, an intrusion alarm can occur that will cause the zone to go into alarm.

7. Enter a value (from 30 to 180 seconds) for the Inactivity timeout parameter. If no user activity is detected at the OP5 arming terminal for a period that exceeds this parameter's setting, the currently logged on user will be logged off auto-matically.

8. The Zones list shows all zones that have been added to the system. Use selection boxes () in this portion of the editor to define which zones will be controllable from this arming terminal, and to setup automatic setting of the zone and auto-matic loggoff of the user.

a. Make a zone controllable from this OP5 arming terminal by activating () the selection box in the Select column. This causes an addition selection box to appear in the Unset and Set Logoff columns of this zone.

b. If necessary, activate () the selection box in the Unset column to configure the zone to unset automatically when a user logs on at this terminal.

c. If necessary, activate () the selection box in the Set Logoff column to configure the OP5 arming terminal to automatically logoff the user when the user sets the zone from this terminal.

d. Repeat these steps for any other zones you wish to make controllable from this OP5 arming terminal.


Intrusion Alarm Zone Configuration Intrusion Alarm System

Note: When a user at the OP5 arming terminal issues a Set All or Unset All command, only the zones that have been made controllable from the terminal will be affected.

9. Select OK to save these settings and close the editor, or select Cancel to exit without saving.

Intrusion Alarm Zone Configuration

TAC I/NET Seven displays the Intrusion Alarm Zone Configura-tion editor (see Figure 18-5) when you add or modify a zone from the Intrusion Alarm System editor.

Figure 18-5. Intrusion Alarm System Zone Configuration Editor


Intrusion Alarm System Intrusion Alarm Zone Configuration

Use this editor to define up to 24 zones for your system.

1. If you are adding a new zone, use the Zone number field to assign a number (from 1 to 24) to the zone. If you are modify an existing zone, this field will be read-only.

2. Use the Zone status drop-down list to choose a point that will be used to represent the zone's status. This point must be available (i.e., it has not been assigned to another zone) and must be configured as an internal DA in order for it to appear in the drop-down list.

3. Use the Set/uset request drop-down list to choose a point that will issue a set or unset request to the zone. This point must be configured as an internal DO in order for it to appear in the drop-down list.

The IAS application will automatically control this point when a user at an OP5 arming terminal issues a set or unset command to the zone. An authorized TAC I/NET Seven oper-ator can also request to set or unset the zone by manually controlling this point to a 1 or 0, respectively.

4. Use the Zone mode drop-down list to choose a point that will be used to indicate the zone's mode. This point must be avail-able (i.e., it has not been assigned to another zone) and must be configured as an internal DI or DA in order for it to appear in the drop-down list.

5. If necessary, use the Zone set indication drop-down list to choose a point that will be used to indicate that the zone is set. The drop-down list will include all of your system's DO points. Choose the point that will be wired to PIRs in the zone.

The purpose of this point is to disable the LED on all PIRs within the zone whenever the zone is set. If your zone will not contain PIRs, or if you do not need to control the LED on PIRs, you can leave this parameter set to "None."

6. If necessary, use the Failed to set drop-down list to choose a point that will be used to indicate that the zone has failed to set. The drop-down list will include all of your system's DO points. Choose the point that will be wired to an indicator.


Intrusion Alarm Zone Configuration Intrusion Alarm System

If no failed-to-set indicator will be required for this zone, you can leave this parameter set to "None.".

7. Use the Entry timer field to delay alarms that may occur along the zone's entry route for a specific number of seconds (10 to 300 in 5-second increments). Refer to IAS Entry Procedure for more information.

8. Use the Exit timer field to delay alarms that may occur along the zone's exit route for a specific number of seconds (10 to 300 in 5-second increments). Refer to IAS Exit Procedure for more information.

9. Use the Fail to set duration field to specify the maximum number of seconds (0 to 100) that the failed-to-set indicator should remain on once activated.

10. Use the Sensor list to assign sensors to the zone. This list shows all of your system's discrete inputs. Using selection boxes () in this portion of the editor you can:

• Define which sensors will be assigned to the zone

• Choose whether or not a sensor will be an entry or exit route sensor.

• Choose whether or not a sensor can be used to start the zone's entry procedure.

• If necessary, define an override for the sensor.

Add sensors to the zone as follows:

a. For any sensor you wish to add to the zone, activate () the selection box in the Select column.

If a sensor has already been assigned to another zone or has been defined as a system sensor or common sensor, no selection box will be available in this column.

b. If the selected sensor should be included in this zone's entry route, activate () the selection box in the Entry column.

c. If the selected sensor should be used as a valid entry point into the zone (i.e., it is allowed to start the zone's entry procedure), activate () the selection box in the Start column.


Intrusion Alarm System Intrusion Alarm System Dial Parameters

d. If the selected sensor should be included in this zone's exit route, activate () the selection box in the Exit column.

e. If you wish to define custom codes for this sensor or override its not-ready condition, keeping the mouse cursor within the highlighted area of the selected point, double-click in the Rest NRdy Ovrd column. Use the resulting Intrusion Alarm System Dial Code Select dialog box to choose on override for the point's not-ready condition.

f. Repeat these steps as necessary to add other sensors to the zone.

11. Select OK to accept these settings or select Cancel to close this editor without saving.

Intrusion Alarm System Dial Parameters

TAC I/NET Seven displays the Intrusion Alarm System Dial Param-eters editor (see Figure 18-6) in the following instances:

✦ When you click the SIA Setup button in the Intrusion Alarm System editor.

✦ When you double-click the Dial Codes field in the Intrusion Alarm System Dial Code Select dialog box.

✦ When you double-click the Zone dial field in the Intrusion Alarm Zone Configuration editor.

Use this editor to define what codes will be sent to an alarm receiving center, how internal and external warning devices will behave, and what overrides (if any) should be used when state changes occur at IAS points.


Intrusion Alarm System Dial Parameters Intrusion Alarm System

Note: At any time while using this editor you can click the Defaults button to reset all parameters back to default settings, or click Clear All to clear all fields. No settings will be retained unless you click OK to save all settings.

1. Use the Dialer fault drop-down list to choose a discrete point that will be used to indicate the status of the dialer.

When the dialer is operating normally, this point will be commanded to its 0 state (i.e., ready). If a fault is detected in the dialer, the IAS will command this point to its 1 state (i.e., not-ready). Typically, you will also configure this point as a System Status point or as a Common Sensor and define a “Fault” override for its not-ready condition.

Figure 18-6. Intrusion Alarm System Dial Parameters Editor

Overrides

StandardSettings


Intrusion Alarm System Intrusion Alarm System Dial Parameters

2. Use the Phone # field to define the appropriate phone number or IP address for the alarm receiving center (ARC) that will accept incoming calls from your system's dialer. Enter up to 30 characters that will be sent as a string from the dialer when it attempts to establish a connection with the ARC.

3. Define the Dialer Account (up to 6 characters) appropriate for your system. This account string distinguishes your intru-sion alarm system from other systems that may report back to the same ARC.

4. Use the scrolling list in the upper portion of the editor to define the “standard” dial codes and warning device settings for the listed IAS conditions. The settings you define in this list will be used whenever a listed condition occurs and no override has been defined for the associated point.

a. Click in the Restore column of any set of standard settings that you wish to modify.

b. Type the code that will be sent to an alarm receiving center when a point without overrides gets restored. You can leave this entry blank if no restore code should be sent to the alarm receiving center.

c. Click in the Not Ready column of the selection and type the code that will be sent to an alarm receiving center when a point without overrides goes not-ready. You can leave this entry blank if no not-ready code should be sent to the alarm receiving center.

5. Use the scrolling list in the lower portion of the editor to define up to 25 sets of “override” settings. You can assign any set of overrides to specific points in the IAS on a per-point basis.

a. Click in the Restore column of any set of overrides that you wish to modify.

b. Type the code that will be sent to an alarm receiving center when a point with this override gets restored. You can leave this entry blank if no restore code should be sent to the alarm receiving center.


Overriding a Point's Not-ready Condition Intrusion Alarm System

c. Click in the Not Ready column of the selection and type the code that will be sent to an alarm receiving center when a point with this override goes not-ready. You can leave this entry blank if no not-ready code should be sent to the alarm receiving center.

d. Choose a setting for the not-ready condition override by double-clicking in the Override column of the selection. Use the resulting Intrusion Alarm System Dial Code Override Select dialog box to choose a setting .

6. Select OK to accept your settings or select Cancel to close this editor without saving.

Overriding a Point's Not-ready Condition

It is common to have single-bit discrete points that can indicate Normal/Not-ready (Normal/Alarm while the zone is set). However, there may also be a necessity to have single-bit points in the IAS that can indicate Normal/Fault or Normal/Tamper. You can accomplish this by defining overrides for not-ready conditions.

1. Double-click on the Ndx Rest NRdy E I Ovrd Rest Inh Iso column of a point in the System Sensor Selection editor (see Figure 18-2 on page 18-7) or in the Intrusion Alarm Zone Configuration editor (see Figure 18-5 on page 18-14).

2. Use the resulting Intrusion Alarm System Dial Code Select dialog box to choose an override for the point's not-ready condition.

Figure 18-7. Double-clicking on a Point to Override


Intrusion Alarm System Overriding a Point's Not-ready Condition

3. The read-only Sensor point field shows the address and point name of the point you are about to modify.

4. Use the Dial codes drop-down list to choose an override for the selected point's not-ready condition.

5. If the desired override is not listed in the drop-down list, you can add a new entry as follows:

a. Double-click on the Dial codes text field. This will cause the Intrusion Alarm System Dial Parameters editor (see Figure 18-6 on page 18-18) to open.

b. Use the editor to add the necessary entry. Refer to “Intru-sion Alarm System Dial Parameters” on page 18-17 for instructions.

c. Save your changes and close the editor. You will be returned to this dialog box.

d. Use the Dial codes drop-down list to choose the override that you just added.

6. Select OK to save your selection and close the dialog box.

Figure 18-8. Dial Code Select Dialog Box


Overriding a Point's Not-ready Condition Intrusion Alarm System


C H A P T E R12

19

© 2001–2010 SchTCON299–05/10

Override Billing

This is a special extension available only with DO points in the 7750 Building Manager. This extension lets you use the 7750 to control points residing in other controllers. You can call the 7750 with a touch-tone phone, enter the appropriate access code, and override the previously defined time schedules for these points.

Using the extension editor, you can define zones. In this way you can control multiple points within the same zone. A “wink” feature lets you control the first point assigned to the zone prior to the end of the override period. For example, you can use the wink feature to blink the lights alerting the user that the override period is about to expire.

In addition, this extension lets you track the number of overrides requested, the amount of time a zone (point) is in override, and the electricity consumed during the override time period. If an output point is controlled by several zones (a chiller is one example), this extension lets you identify the electricity use of individual zones.

Note: These features are invaluable in establishing billing information in a building inhabited by multiple tenants. You can request tenants pay electrical bills that reflect their actual consumption patterns. Tenants who use a great deal of electricity will be faced with appropriately large electrical bills. Tenants who use less electricity are not penalized for inhabiting the same building as a heavy electrical user.

Before You Begin

The override portion of this extension lets you override normal time schedules for points that reside in other DCUs.


Before You Begin Override Billing

Note: The minimum trip and minimum close times for discrete outputs in other DCUs are not honored when the Building Manager initiates control to these output points.

An override may be initiated by any of the following:

✦ Calling the 7750 with a touch-tone telephone and using its built-in telephone interface to override existing zone time schedules. This can be done up to 24 hours in advance.

✦ Closing a discrete switch wired to the optional 64 point inter-face board that is connected to the 7750.

Notes: Equipment points in other DCUs that will be controlled by the Building Manager must be defined as global (LAN, Link, or System). Refer to Chapter 5, Point Definition and Addressing.

An indirect point must be created for each remote global equipment point in the 7750 Building Manager database.

A 7750 that occupies one station on the LAN may contain up to 32 zones. A 7750 that occupies two stations on the LAN may contain up to 64 zones.

A zone must be an internal DO point with a zero bit offset address; e.g., 0100 DO. Each zone may have up to 12 points associated with it. These 12 points must be DO or DC points with non-zero bit offsets; e.g., 0101 DO, and should be indirect rather than resident in the controller. The 7750 can override up to 128 unique points. However, no more than 32 points should be controlled at any one time.

Each DI point address is associated with a particular zone number. If used, it must come from a particular terminal block pair on the 64 point DI module.


Override Billing Override Billing Extension Editors

Override Billing Extension Editors

The Override Billing extension includes three sub-editors:

Override Parameters

Use this option to define which points are associated with each zone. In addition, you may designate a point that is to wink at the time specified and for a specified interval to indicate that the over-ride time is about to expire.

Override 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. Access codes are not required if dial-in access is not desired.

Equipment Mapping

Use this option to specify the kilowatt rating of the points you want the 7750 to override. 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.

Entering Override Parameters

This option adds the actual override billing extension to the selected point. Use this option to specify distribution group, distri-bution 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 one zone point for override control. This lets you control up to 12 points when the zone point is put into override.

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.

Note: Only those points defined in the Resident I/O Points editor with zero bit offset; i.e., bb of llssppbb = 0, can be zone points.


Entering Override Parameters Override Billing

1. Select Edit Controller Override Parameters, or click the Override Parameters tool in the Controller toolbar. The system displays the Resident I/O Points editor with the over-ride billing (OB) option selected (see Figure 19-1).

This screen displays all the internal DO points (zones). These are the only point types to which you can add override parameters. A Y appears in the OB column of those points to which override billing has already been added.

2. Choose a point from the list. This point should not already have a Y in the OB column.

3. Select Add to add the override billing option to the point. The system displays the Override Parameters editor for this point (see Figure 19-2).

4. Set the following parameters:

✧ Distribution Group/Mask

✧ Cell Priority

✧ Cell Number

Figure 19-1. Resident I/O Points Editor (OB selected)


Override Billing Entering Override Parameters

✧ Wink Off Interval

✧ Wink On Interval

✧ Equipment Points

These parameters are described below.

5. Select OK to accept your changes and exit the Override Parameters editor.

Distribution Parameters1. Select a Distribution group.

2. Define a Distribution mask that matches the distribution group and mask(s) on the host PC(s) to which you want the override data sent. The data is stored in a SevenTrends Over-ride Billing table.

3. Select a Priority from the drop-down list for the override data upload request. A priority of None means no data is uploaded. Use Routine to steer override data to direct-connected host PCs. Use Priority or Critical to steer override data to remote

Figure 19-2. Override Parameters Editor



(dial) host PCs. (Priority will not require a dial site to report daily. Refer to Chapter 6, “System Messages” for additional information.)

4. Enter a Cell number between 1 and 1,023. You must assign a value other than zero (0) 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.

End of Override Notice Parameters 1. Enter a number between zero and 255 in Wink off interval

(sec). This specifies how long the first equipment point in the zone is turned off or winked before being turned back on to indicate the override period is about to expire.

2. In the Wink on interval (min), enter a number between zero and 255 to specify how long before the end of the override period the system winks the first equipment point of the zone.

Equipment Points

Assign specific points to specific zones. You may assign up to 12 indirect points that a 7750 can override in this particular zone. The first point is reserved as the winked point to be controlled by the Wink Off and Wink On commands.

Adding Access CodesThis step is only required if overrides will be initiated remotely. Use this option to designate access codes for each zone. These codes must be used to access the zone you wish to put in override when calling the 7750 Building Manager via a touch-tone phone.

1. Select Edit Controller Override Access Codes, or click the Override Access Codes tool on the controller toolbar. The system displays the Access Codes editor which contains the 64 points and their assigned access codes (see Figure 19-3).

2. Double-click on a point in the list, or select a point and click Modify. The system displays the Zone Access Code editor (see Figure 19-4)



3. Enter a code containing up to six digits for each zone. This is the number that must be entered via a touch-tone phone in order to access a zone and override the normal time schedule for a specific zone.

4. Select OK to accept your changes and return to the Access Codes editor.

5. Enter a code containing up to six digits for Non-billable access.

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.

Figure 19-3. Access Codes Editor

Figure 19-4. Zone Access Code Editor



The amount of non-billable electrical consumption and over-ride time is accumulated on a daily basis for each zone and is updated at midnight.

Note: If a non-billable override and a billable override overlap each other, the non-billable override always takes precedence.

6. Enter a code containing up to six digits for Interrogate access.

This code lets you call the 7750 and inquire about the state or value of any point on the LAN. You must know the eight-digit point address because you will need to enter it into the system from a touch-tone phone when you want to interrogate the point. You will also need to know whether the point is an input point or an output point.

7. Enter a code containing up to six digits for Control access.

This code lets you call the 7750, inquire about the state or value of any point on the LAN, and control any point on the LAN to a certain state or value. You must know the eight-digit point address because you will need to enter it into the system from a touch-tone phone when you want to control the point. You will also need to know whether the point is an input point or an output point.

8. When you finish entering these access codes, click OK to accept your changes and exit the Access Codes editor.

Adding Equipment MappingEquipment mapping allows you to bill tenants for override energy usage. Use this option to specify the load size of the equipment being controlled, the base load, and the percentage of the total load that can be assessed to each zone.

Note: Only those points defined in the Resident I/O Points editor as indirect and with a non-zero bit offset; i.e., bb of llssppbb = 1–9, can be equipment points.



The following procedure is used for Equipment Mapping.

1. Select Edit Controller Equipment Mapping, or click the Equipment Mapping tool on the Controller toolbar. The system displays the Resident I/O Points editor with the equip-ment mapping (EM) option selected (see Figure 19-5).

This screen displays the non-zero bit offset point addresses to which you may add equipment mapping. A Y appears in the EM column of those points to which an equipment map has already been added.

2. Choose a point from the list. This point should not already have a Y in the EM column.

3. Select Add to add the equipment mapping option to the point. The system displays the Equipment Mapping editor for this point (see Figure 19-6).

4. Enter a number between zero and 32,767 to specify the kilo-watt (KW) rating for this Load size so that kilowatt-hour (KWH) calculations may be made.

Figure 19-5. Resident I/O Points Editor (EM selected)



5. Enter a number between zero and 100 (percent) for the Base load. This number is multiplied by the load size to determine the minimum number of kilowatt hours a zone accumulates when the load is overridden by only one zone.

6. Select a zone and select Modify, or double-click on the desired zone. The Equipment Mapping - Modify dialog box will appear (see Figure 19-7).

7. Enter the percentage of the load assessed to this zone and select OK.

8. Click OK to return to the Equipment Mapping editor. Repeat as required to distribute this load over additional zones.

Note: The total distribution must equal 100 percent, even if a point is only controlled by one zone.

Figure 19-6. Equipment Mapping Editor

Figure 19-7. Equipment Mapping - Modify Dialog Box



9. When finished, select OK from the Equipment Mapping editor to return to the Resident I/O Points editor.

10. Click OK to accept your changes and exit the Equipment Mapping editor.


C H A P T E R4

20

© 2001–2010 SchTCON299–05/10

7771 Industrial Controller

Interface

The 7771 I/NET Communications Interface or ICI acts as a bridge between the controller LAN and another on-line data communica-tion system/network that uses MODBUS protocol. The ICI lets you transfer analog or discrete point data between the two systems. It provides data buffering, storage, and translation between the two systems.

Configuring the 7771

The ICI is configured for the MODBUS system using the ICI Configuration editor. The ICI Configuration editor option only appears when you are connected to a 7771. This lets you set the communication parameters of the ICI on the MODBUS system. The procedure is provided below.

1. Connect to a 7771 ICI.

2. Select Edit Controller ICI Configuration from the main menu. The system displays the ICI Configuration editor (see Figure 20-1).

3. Choose a setting for each parameter.

a. Choose an ICI port status from the drop-down list. The default is Enable.

b. Choose an ICI interface type from the drop-down list. The default is RS232.


Configuring the 7771 7771 Industrial Controller Interface

c. Choose a Baud rate from the drop-down list. The default is 9600.

d. Choose the appropriate number of Data bits from the drop-down list. The default is 8.

e. Choose the appropriate number of Stop bits from the drop-down list. The default is one.

f. Choose a Parity type from the drop-down list. The default is even.

g. Choose an ICI protocol from the drop-down list. The default is Binary.

h. Enter an ICI slave address (0 to 255). The default is one

i. Using the spindial, enter the Character completion timeout (sec) time (0 to 2.55). This is the amount of time the ICI waits for a response after sending a request.

j. Using the spindial, enter the Delay before response (sec) time. The default is zero. This is the amount of time the ICI waits to respond after receiving a request.

4. Select OK to accept your changes and exit the editor.

Figure 20-1. ICI Configuration Editor


7771 Industrial Controller Interface Points and Addressing

Note: The parameters you define here must agree with the parameters defined in the MODBUS host. The ICI emulates a PLC 584 so make sure the MODBUS host is configured to recognize the ICI as such.

Points and Addressing

The TAC I/NET and MODBUS systems use different sets of point types. The ICI converts MODBUS point types so that TAC I/NET can recognize them and vice versa. All MODBUS points should have a corresponding external point defined in I/NET. Points defined as internal in the ICI exist only in the TAC I/NET Seven software, they are not connected to the MODBUS. If you acciden-tally assign an internal TAC I/NET point to a MODBUS point, the ICI gives you an error message when you attempt to command or receive data from the MODBUS host.

The ICI supports all standard TAC I/NET input and output points. Refer to the chapter dealing with Input and Output Points in TCON300, TAC I/NET Seven Technical Reference Guide, for a detailed description of each point type.


C H A P T E R14

21

© 2001–2010 SchTCON299–05/10

Micro Regulator Control

Micro Regulators (MRs) operate on an MR LAN connected to a 7792 Micro Regulator Interface (MRI), 7793 Micro Control Inter-face (MCI), or 7798 I/SITE LAN. The MRI, MCI, or I/SITE LAN provides a communications gateway to the TAC I/NET controller LAN. The 7792 and 7793 interface controllers support connection of up to two MR LANs (one on each of two channels). The 7798 provides support for one MR LAN. Each MR LAN may contain up to 32 Micro Regulators. The MRI, MCI, or I/SITE LAN appears on host and controller LANs as a DCU, and uses one address for the 7798 and two addresses for the 7792 and 7793 (one for each channel).

The MRI and MCI maintains the complete database and control parameters for up to 64 MR controllers connected to its two MR LAN ports. The I/SITE LAN maintains the complete database and control parameters for up to 32 MR Controllers connected to its single MR LAN port.

The MRI, MCI, and I/SITE LAN supports the definition of internal points with all of the extension capabilities typical of the 7716 PCU. The internal points in the MRI, MCI, or I/SITE LAN are defined only for point addresses not currently used by its associated MR controllers.

The Micro Regulator controllers provide stand-alone DDC control of a collection of six hardware input and up to seven hardware output points. The number of output points and their type vary by model. Both discrete and PWM modulated control are supported by the MR controllers. Depending upon the model, high or low voltage outputs, or both are available.

Refer to TCON109, 7792 Micro Regulator Interface, TCON138, Model 7798 I/SITE LAN, and TCON113 and TCON126, I/STAT and Micro Regulator Controllers, for details.


Configuring the Interface Controller Micro Regulator Control

Configuring the Interface Controller

Use the following procedure to assign the addresses in the controller.

1. If you are connected to a 7792 MRI, select Edit Controller MR Configuration, or click the MR Configuration tool on the Controller toolbar,

If you are connected to a 7793 MCI or 7798 I/SITE LAN, select Edit Controller MCU Configuration, or click the MCU Configuration tool on the Controller toolbar. The system displays the MR/MCU Configuration editor shown in Figure 21-1.

Figure 21-1. MR Configuration Editor


Micro Regulator Control Creating the MR Database

This editor displays the addresses of all the MRs connected to this controller (32 addresses for a 7798 and 64 addresses for to a 7792 or 7793 controller).

Note: An MCI and I/SITE LAN will offer four options: DPU, MR, DIO, and DIU. DPU refers to the DPU7910, DPU7920, and SCU1284 controllers, DIO refers to the DIO7940 and SCU1280 controllers, and DIU refers to the DIU7930 and SCU1200 controllers. Other-wise, the MCI and I/SITE LAN will function identically to the MRI.

2. Using the spindials, choose the type of device that will be located at each address. The default type is Internal (i.e., no device connected at the address).

Note: Figure 21-1 shows an MRI defined as a dual station. A MRI or MCI, defined with two stations shows MRs in four adjacent columns numbered from XX00 to XX31 and YY00 to YY31. In this case, XX refers to the first address and YY refers to the second address of the MRI or MCI.

3. Select OK to accept the changes and exit the editor.

Creating the MR Database

1. Connect to an MRI, MCI, or I/SITE LAN.


3. See Chapter 5, Point Definition and Addressing, for a detailed description of database parameters and the mechanics of database entry.

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 and MRI, MCI, or I/SITE LAN resident extension editors only. The MR Copy function will not copy Standalone ATS or I/STAT Parameters.


MR Copy Micro Regulator Control

Use the following steps to perform the MR Copy function:

1. Connect to an MRI, MCI, or I/SITE LAN.


3. Choose a source MR point to be copied from the point list.

4. Select MR Copy. The system displays the MCU Copy screen (see Figure 21-2).

5. Define a point address for the new MR point using the Station and Point spindials.

6. Select OK. The system performs the MR Copy function.

Configuring the Micro RegulatorsOnce you have defined several MR-resident points in the Resident I/O Points editor, return to the main menu and select Edit Controller MR Functions, or click the MR Functions tool on the Controller toolbar.

This option only appears when you are connected to a 7792 (MRI), 7793 (MCI), or 7798 (I/SITE LAN). The system displays the MR Functions summary (see Figure 21-3).

Figure 21-2. MCU Copy Screen


Micro Regulator Control MR Copy

The MR Functions screen is used to access the following MR options:

✦ MR-resident Direct Digital Control (DDC)

✦ Standalone ATS (ATS)

✦ Hardware Coefficients (Hardware)

✦ MR Parameters (I/STAT)

The last three options on this screen let you define the hardware-specific parameters for each MR.

MR-Resident DDCBy now you are probably familiar with the worksheets located in TCON157, TAC I/NET Seven Forms and Worksheets. There is a separate worksheet for each module type. We recommend you fill these out before entering the data into the system.

Use the following steps to define MR-resident DDC modules:

1. Choose an MR point from the MR Summary list in the MR Functions summary (see Figure 21-3).

Figure 21-3. MR Functions Summary



2. Select DDC. The system displays the MR DDC Modules editor (see Figure 21-4). This screen displays all modules assigned to this MR.

3. Use this editor to perform the following functions:

✧ Add, Delete, Modify, or Copy an MR-resident DDC module.

✧ Mark a DDC module for use with the History function (refer to the chapter dealing with Direct Digital Control in TCON300, TAC I/NET Seven Technical Reference Guide, for a discussion of history).

✧ Perform Tuning on an MR-resident DDC module (refer to the chapter dealing with Direct Digital Control in TCON300, TAC I/NET Seven Technical Reference Guide, for a discussion of tuning).

Adding an MR-resident DDC Module

Use the following steps to add an MR-resident DDC module:

1. Choose a line (1 - 16) from the module summary. The line must not already have a module assigned.

Figure 21-4. MR DDC Modules Editor



2. Select Add. The system displays the Add MR DDC Module dialog box (see Figure 21-5).

3. Enter a Module name or accept the default name generated by the system.

4. Choose a Module type from the drop-down list. Module types and their associated parameters are discussed in the chapter dealing with Direct Digital Control in TCON300, TAC I/NET Seven Technical Reference Guide.

5. Select OK. The system displays the editor for the module type that you selected.

6. Set the parameters in the chosen module editor and select OK to save the settings. Refer to Chapter 14, Direct Digital Control, in this manual for DDC module configuration proce-dures.

7. Repeat Steps 1 through 6 as required to add more modules.


Deleting an MR-resident Module

Use the following procedure to delete an MR-resident DDC module:

1. From the MR DDC Modules screen (see Figure 21-4) choose the module and select Delete. The system displays the Delete confirmation prompt.

2. Select Yes. The system deletes the module and displays the DDC Modules screen.

Figure 21-5. Add MR DDC Dialog Box



3. Repeat Steps 1 and 2 as required to delete more DDC modules.


Modifying an MR-resident DDC Module

Modifying a DDC module is similar to adding a DDC module. Use the same procedure described in “Adding an MR-resident DDC Module” on page 21-6 with the following exceptions: choose a DDC module that already exists; select Modify from the MR DDC Modules screen rather than Add.

Copying an MR-resident DDC Module

Use the following procedure to copy a DDC module.

1. From the MR DDC Modules editor (see Figure 21-4) choose the module and select Copy. The system displays the DDC Copy dialog box (see Figure 21-6).

2. Enter the Module number or accept the default module number.

3. Enter the Module name. Use up to 8 characters.

4. Select an Module type.

5. Select OK. The system displays the editor for the type of module that you selected.

6. Modify the parameters as required and select OK. The system copies the parameters to the new module and displays the MR DDC Modules editor. (see Figure 21-4).

Figure 21-6. MR DDC Copy Dialog Box



7. Repeat Steps 1 through 6 as required to copy more modules.


Standalone ATSSelecting ATS from the MR Functions summary brings you to the Standalone ATS editor (see Figure 21-7). Normal ATS functions are supported through the MRI, MCI, and I/SITE LAN. Standalone ATS is a backup for ATS scheduling, should there be a break in the MR LAN communications.

The Standalone ATS is an MR-resident ATS schedule programmed into the MRs that allows a single start and stop time for each day of the week for the point designated as the Master Device Control point in the MR Parameters editor (see Figure 21-9). These commands are only issued if the MR and DCU are not communi-cating.

Hardware CoefficientsHardware coefficients correspond to FM (factory slope) and FB (factory offset) conversion coefficients. These parameters are primarily used by CSI for factory-made adjustments to the MR

Figure 21-7. Standalone ATS Editor



hardware inputs. The end-user should avoid altering these settings. However, if necessary, use the following steps to define hardware coefficients:

1. Choose an MR point from the MR Summary list in the MR Function screen.

2. Select Hardware. The system displays the Hardware Coeffi-cients editor (see Figure 21-8).

3. Enter an M value between 0 and 1.9997. This conversion parameter corresponds to the FM (factory slope) conversion coefficient in the I/STAT.

4. Enter a B value between –128 and 127. This conversion parameter corresponds to the FB (factory offset) conversion coefficient in the I/STAT.

5. Choose a Span setting from the drop-down list. The Span field offers a normal span and a narrow span. Normal span is used to set AI points to a range of 0–10VDC or a range of 0–5VDC. depending upon MR type. The narrow span is used to set AI points to a range of 4–8VDC or 2–4VDC, depending upon MR type.

Figure 21-8. Hardware Coefficients Editor



6. As necessary, repeat steps 3 through 5 for each bit.

7. Select OK to return to the MR Functions summary.

MR (I/STAT) ParametersThe MR (I/STAT) Parameters editor defines the points that will be controlled or displayed locally with an I/STAT. Using this editor to establish the Master Device Control Point, the Call button point, the inactivity timeout intervals used by the I/STAT, and the I/STAT password.

Use the following steps to configure MR parameters:

1. Choose an MR point from the MR Summary list in the MR Function screen.

2. Select I/STAT. The system displays the MR Parameters editor (see Figure 21-9).

Note: The parameters in this edit screen are used by the I/STAT, an intelli-gent thermostat connected to the MR. It controls and monitors points and devices connected to the MR.

Figure 21-9. MR Parameters editor screen



3. Set the following parameters:

✧ Button Parameters

✧ Inactivity Timeouts

✧ LED Functions

Procedures for configuring these parameters are described below.

4. When you are finished, select OK to leave this editor.

Button Parameters

Use the following steps to configure Button parameters:

1. Enter the Master device address. The point address or name of the point to be used as the Master Device Control Point is entered here. This point is either a DO or DC point and repre-sents the occupancy of the MR. It will be controlled from on (occupied) to off (unoccupied) depending upon the time of day.

2. Set an Interval. The Interval field allows you to specify the time, from 0 to 255 minutes, that the interval timer will countdown when the Master Device point is activated through the On/Off button on the I/STAT. The Master Device point will remain on until the interval timer has counted down to zero.

Note: If the Interval is set to 0, the On/Off button becomes a toggle switch (i.e., no countdown) for the Master Device point. In this case, the Master Device point is turned on when the On/Off button is first pressed and remains on until the On/Off button is pressed again.

3. Enter the Call button address. This address and point type define the point that is controlled on or off when you press the I/STAT’s Call button. This point may be a DO or DC point.

4. Enter a numeric, three-digit password for the I/STAT in the Password Digits field. The password restricts access to the Service function on the I/STAT (the ability to make point/parameter/calibration changes through the I/STAT).



Inactivity Timeouts

Use the following steps to configure Inactivity Timeouts:

1. Enter the Escape from service timeout (from 0 to 255 seconds). The I/STAT uses this timeout to return to Normal mode from its Service function. This timeout starts its count-down from the time the last button is pressed.

2. Enter the Return to home LED timeout (from 0 to 255 seconds). The I/STAT uses this timeout to return to the Home LED display when in the normal mode. This timeout starts its countdown from the time the last button is pressed.

LED Functions

There are four LEDs that are associated with points. Any of the four LEDs may be designated as the Home LED. The Home LED lights and the home LED point displays when the I/STAT is initialized, and after the “Return to Home LED” timeout interval expires.

LED 1 allows you to enter a master setpoint address as the Base address and a local setpoint address as the Adjust address. These two addresses must be local to the same MR (they must have the same PP in their address). This allows you to make changes to the system setpoint from the I/STAT using the Change +/– keys and display the new adjusted setpoint value at the I/STAT. The displayed value is a summation of the Base address value and the Adjust address value.

The Adjust address must be an AO point so that changes may be made through the I/STAT. The base address may be an AI or AO point. Both points may be external, internal, or indirect points.

If the Base address master setpoint is received from another address external to the MR, then you must attach a Calculation extension to the base address point (i.e., P0 = Master Setpoint).

Note: Without a Base address defined, only the value of the Adjust address will display through the I/STAT. If the Adjust address is not defined then no value will display through the I/STAT.



If the total value of the Adjust address and Base address is needed for other applications, you must create a separate calculation module that sums the two point address values and outputs the result of the calculation to another internal AO point.

Depending upon the point type, certain parameters can be defined for each LED.

✦ AI - no parameters required. This point type is display only on the I/STAT.

✦ AO - there are three parameters that this point type supports.

✧ Increment - the value by which an analog point is changed each time a Change arrow button is pressed on the I/STAT.

✧ Low - the lowest value to which the point may be adjusted (i.e., the lowest space temperature setpoint allowed).

✧ High - the highest value to which the point may be adjusted (i.e., the highest space temperature setpoint allowed).

✦ DO/DC/DI/DM/DA - these point types support 0, 1, or 2–3 character state descriptions states for states 0, 1, or 2 respec-tively.


C H A P T E R10

22

© 2001–2010 SchTCON299–05/10

Application Specific Controllers

Application Specific Controllers (ASCs) are configured from the ASC editor. This editor is available when you are connected to a 7792 (MRI), 7793 (MCI), or 7798 (I/SITE LAN).

Select Edit Controller ASC Parameters, or click the ASC Parameters tool on the Controller toolbar. The system displays the ASC editor (see Figure 22-1).

The following functions are available within the ASC editor:

✦ Displaying ASC Data

✦ Modifying Parameters

✦ Modifying ASC Names

✦ Copying ASC Parameters

Figure 22-1. ASC Editor


Displaying ASC Data Application Specific Controllers

✦ Updating the Interface Controller

✦ Updating the ASC

Procedures for each of these options are described below.

Displaying ASC Data

TAC I/NET Seven provides a read-only screen of ASC dynamic data. Use the following procedures to display ASC data:

1. Select an ASC from those listed in the ASC editor and click Display Data. The system displays the ASC Dynamic Data summary (see Figure 22-2).

The specific data on this summary varies depending on the ASC. (The screen shown in Figure 22-2 is for an MR-AHU.)

2. Select Close to exit from the ASC Dynamic Data summary.

Figure 22-2. ASC Dynamic Data Summary


Application Specific Controllers Modifying Parameters

Modifying Parameters

ASC parameters can be edited from the MR-ASC Parameters editor within TAC I/NET Seven, or from the I/STAT or M/STAT connected directly to the ASC. The parameters available, and their limits and functions, depend on the type of ASC being configured. Refer to the documentation supplied with your particular ASC for parameter descriptions and configuration procedures. Use the following basic procedures to modify ASC parameters from TAC I/NET Seven:

1. Select an ASC from the ASC editor and click Modify. The system displays the MR-ASC Parameters editor (see Figure 22-3).

Figure 22-3. MR-ASC Parameters Editor


Modifying ASC Names Application Specific Controllers

The parameters available within this editor depend on the type of ASC selected. (The editor shown in Figure 22-3 is for an MR-AHU.)

2. Use the documentation included with your ASC to modify the parameters as necessary.

3. When you have finished modifying parameters, select OK to accept your changes and exit this procedure.

Modifying ASC Names

TAC I/NET Seven allows you to assign a name to each ASC connected to your system. This name will be appended to the resi-dent point names in the MCI and will then serve as a reference while in ASC-specific editors. Use the following procedures to modify ASC names:

1. Select an ASC from the ASC editor and click Rename. The system displays the MR-ASC Name Assignment dialog box (see Figure 22-4).

2. Enter an ASC name (up to 8 characters) and select OK. Duplicate names are not accepted. If you enter a duplicate name ASC name will have an asterisk in the MR-ASC selec-tion editor.

3. Repeat Steps 1 and 2 for each ASC as necessary.

Figure 22-4. MR-ASC Name Assignment Dialog Box


Application Specific Controllers Copying ASC Parameters

4. Once the ASC names are assigned, you must disconnect (select Disconnect from the main menu) from the DCU and then re-connect to see the changes made (changes may be viewed from the DCU Summary or Resident I/O Points editor). Point names can be defined at any time.

5. An MCI update must be performed to get the complete point record from the ASC and to define the station parameters (refer to “Updating the Interface Controller” on page 22-7). The MCI update needs to be executed one time.

Copying ASC Parameters

You may copy the configuration of one ASC to one or more other ASCs. The copy will include ASC parameters, I/STAT parameters, and stand-alone ATS. Use the following procedures to copy ASC parameters:

1. Highlight a source ASC from the list and select Copy. The system displays the MR-ASC Copy Target editor (see Figure 22-5).

Figure 22-5. MR-ASC Copy Target Editor


Saving and Restoring ASC Parameters Application Specific Controllers

This editor lists only ASCs of the same type as the source ASC (AHU, VAV, etc.).

2. Select each ASC that should receive the copied parameters. You can use the All Yes and All No buttons to speed the selec-tion process.

3. When you are finished, click OK to begin the copy process.

Saving and Restoring ASC Parameters

TAC I/NET Seven allows you to save the parameter settings (including I/STAT parameters) of your ASCs. You can then restore the saved settings later if you wish. This can be beneficial especially following an ASC Update, since performing the update causes the ASC to lose its settings.

1. Choose which ASCs you wish to save or restore. Mark the necessary ASCs by clicking on their name in the list. Each time you click the ASC name, the S/R column indication toggles between selected ([X]) and unselected ([ ]).

You can use the All Yes and All No buttons to quickly select or unselect all listed ASCs.

Note: In the following step, you must have already saved an ASC’s settings before you can perform a restore on that ASC.

2. Select the Save or Restore function, as necessary. TAC I/NET Seven immediately begins processing the marked ASCs. As an ASC is processed, its S/R column indication changes to unse-lected ([ ]).

During the Save process, TAC I/NET Seven creates a separate SAV file for each marked ASC. TAC I/NET Seven automatically assigns a filename that indicates the link (LL), station (SS), and point (PP) of the ASC the file represents. For example, a file named ASC970300.SAV contains the settings of an ASC on link 97, station 03, at point address 00. The saved ASC files are store on the current host workstation, in the SAV directory defined for your system.


Application Specific Controllers Updating the Interface Controller

Updating the Interface Controller

Once you have assigned an ASC, you must perform the update to get the point information into the interface controller (MCI, MRI, or I/SITE LAN). Use the following procedures to update the inter-face controller:

Note: Names must be assigned to all ASCs being updated to the MCI. Refer to “Modifying ASC Names” on page 22-4 for ASC naming proce-dures.

1. Select Update MCI from the ASC editor. The system displays the MCI Update editor (see Figure 22-6).

This screen lists all ASCs communicating with the connected interface controller (MRI, MCI, or I/SITE LAN).

2. Select each ASC for which the interface controller will be updated. You can use the All Yes and All No buttons to speed the selection process.

Figure 22-6. MCI Update Editor


Updating the ASC Application Specific Controllers

3. When you are finished, click OK to begin the update process.

4. When the update is complete, you must disconnect (select Disconnect from the main menu) from the DCU and then re-connect to see the changes at the host workstation.

Updating the ASC

The binary instruction set for the ASC is maintained in NOVRAM and may be updated using the factory default update file. Use the following procedures to update the ASC:

1. Select ASC from the ASC editor. The system displays the ASC Update editor (see Figure 22-7).

This editor lists all ASCs communicating with the connected interface controller (MRI, MCI, or I/SITE LAN).

2. Select each ASC to be updated. You can use the All Yes and All No buttons to speed the selection process.

Figure 22-7. ASC Update Editor


Application Specific Controllers Updating the ASC

3. When you are finished, click OK to begin updating the selected ASCs. You will be prompted for an update path. Click on OK to accept the default path or enter the new path.

4. If updating an existing ASC and an MCI update has already been executed, you must get the point record defined in the MCI to the ASC. This is accomplished by exiting the ASC parameters editor, penetrating the MCU configuration editor, and toggling the ASC from “ASC” to “Internal” and back to “ASC.”


C H A P T E R6

23

© 2001–2010 SchTCON299–05/10

I/SITE LCD Page

The View Con panel on the Model 7728 I/SITE I/O or Model 7798 I/SITE LAN allows you to view pages for review and control. The I/SITE products support up to 64 pages, each page containing up to 640 points. The points on each page may be from the local 7728/7798, or another DCU on the same controller LAN. In either case, all points on a specific page must reside in the same DCU.

Defining the I/SITE LCD Page

To set up LCD pages on the I/SITE, you must connect to it through TAC I/NET Seven and define the pages with the LCD Page Defini-tion editor (see Figure 23-1). This editor is available if you are connected to a 7728/7798.

Figure 23-1. LCD Page Definition Editor


Defining the I/SITE LCD Page I/SITE LCD Page

Adding an LCD Page1. Connect to a 7728 or 7798 controller.

2. Select Edit Controller LCD Page Definition, or click the LCD Page Definition tool on the Controller toolbar. The LCD Page Definition editor displays, as shown in Figure 23-1. The editor lists the defined pages in the selected controller.

3. To add a new page, select Add. The Add dialog box displays (see Figure 23-2).

4. Enter a Page name. This name may be up to 16 characters long.

5. Select a Page number from 1 to 64.

6. Click OK. The system displays the Select DCU summary (see Figure 23-3).

Note: The “Select DCU” summary will display a separate entry for each station of a multi-station controller. See the highlighted item in Figure 23-3 for an example of this functionality.

7. Select a DCU from the list and click OK. The system displays the Select Points summary (see Figure 23-4).

8. Select the points that you want to appear on the LCD page display. Click on the point to select it ([X]) or to deselect it ([ ]). You can select the points individually or you can use the All Yes and All No controls.

9. Click OK to accept the selections and complete the LCD page definition.

Figure 23-2. Add Dialog Box


I/SITE LCD Page Defining the I/SITE LCD Page

Figure 23-3. Select DCU Summary

Figure 23-4. Select Points Summary


Defining the I/SITE LCD Page I/SITE LCD Page

Deleting an LCD PageTo delete an LCD page, connect to the 7728 or 7798 controller and use the following procedure.

1. Select Edit Controller LCD Page Definition, or click the LCD Page Definition tool on the Controller toolbar. The system displays the LCD Page Definition editor (see Figure 23-1)

2. Select the page that you want to delete.

3. Click Delete. The system displays the Delete confirmation prompt.

4. Click Yes to complete the delete operation or select No to abort.

Modifying an LCD PageTo modify an existing LCD page, connect to the 7728 or 7798 controller, and use the following procedure.

1. Select Edit Controller LCD Page Definition, or click the LCD Page Definition tool on the Controller toolbar. The system displays the LCD Page Definition editor (see Figure 23-1).

2. Select the page that you want to modify.

3. Click Modify to display the Select Points summary as shown in Figure 23-4.

4. Select or deselect points in the list, as desired. Click on the point to select it ([X]) or deselect it ([ ]). You can use the All Yes and All No options to speed the selection process.

5. When you have selected the point, click OK to complete the procedure.


I/SITE LCD Page Defining the I/SITE LCD Page

Copying an LCD PageTo copy an existing LCD page to a new page name/number, connect to the 7728 or 7798 controller and use the following procedure.

1. Select Edit Controller LCD Page Definition, or click the LCD Page Definition tool on the Controller toolbar. The system displays the LCD Page Definition editor (see Figure 23-1).

2. Select the page to be copied.

3. Click Copy to display the Add dialog box, shown in Figure 23-2.

4. Enter the Page name and Page number of the new LCD page. This is the page name and number that the selected LCD page will be copied to.

5. Click OK to display the Select DCU summary shown in Figure 23-3.

6. Select the DCU and click OK. The Select Points summary displays. (see Figure 23-4).

7. If desired, modify the LCD Page by selecting or deselecting points in the list.

8. Click OK to complete the copy operation.


C H A P T E R16

24

© 2001–2010 SchTCON299–05/10

SevenTrends

SevenTrends is a program that collects data sent from the DCU field devices for viewing and reporting. Refer to the SevenTrends chapter in TCON300, TAC I/NET Seven Technical Reference Guide for more in-depth SevenTrends information.


Sequence of Operations

The overall sequence for using the SevenTrends features of TAC I/NET Seven is as follows:

1. Configure DCUs to collect data.

2. Define trends in host stations to receive data.

3. Configure host stations to receive collected data.

4. Archive SevenTrends data.

5. Create SevenTrends reports (may be done any time after Step 3 is complete). Refer to the SevenReports help file for more information on creating reports.

Configuring the DCU

The first step in using SevenTrends is to collect data at the DCU level of your TAC I/NET Seven system.


Configuring the DCU SevenTrends

The following editors contain SevenTrends-related fields:

Remember that the editors available for each DCU change depending on the type of controller to which you are connected, the type of points defined within the controller, and your password level.

The following steps are used to configure the DCU to collect data for use with SevenTrends. Not all fields described below are avail-able within all editors. If a field does not exist within the editor, simply skip that step.

1. Choose the Distribution Group that matches the distribution group in the host station to which you want this point to send information.

2. Activate () or deactivate () each of eight mask positions that make up the Distribution Mask. At least one mask should match a distribution mask in the host station to which you want this point to send information.

3. Choose a Priority from the drop-down list. The priority determines whether a DCU is supposed to send an upload request to a host station. The priority must be set to at least Routine for direct-connect systems, or Critical for dial systems.

4. Select a Cell Number from 1 to 1023. You must assign a value other than zero (0) in order for SevenTrends to store the trend information. This field can be used to autogenerate trend definitions (see “Defining Trends and Cells” on page 24-3). Otherwise, this field is not used in TAC I/NET Seven and can be any value.

5. Define a value for Sample Count. This specifies the number of samples that have to be taken before data is sent to Seven-Trends.

✦ Doors ✦ Demand Control✦ Resident I/O Points ✦ Trend Sampling✦ Runtime ✦ Override Billing✦ Consumption


SevenTrends Defining Trends and Cells

Defining Trends and Cells

Before you can send data to the host workstations you must define the trend or cell in the host workstation so that the data has some-place to go.

✦ A trend is defined for a specific point and trend type.

✦ A cell is defined for a trend type, and multiple trends are automatically defined for all points referencing that cell number and trend type.

Use the following procedures to define trends and cells.

1. Select Trends Definitions from the main menu. The system displays the SevenTrends Definitions screen (see Figure 24-1).

2. Select either Add Trend or Add Cell. The system displays the SevenTrends Parameters editor (see Figure 24-4 on page 24-6).

3. If you are adding a trend, the system automatically and launches the Point Selection screen (see Figure 24-2) to select the point for this trend. If you are adding a cell, skip to Step 5 on page 24-6.

Figure 24-1. SevenTrends Definitions Screen


Defining Trends and Cells SevenTrends

Note: Although the Point Selection dialog can be used to select multiple points in other areas of TAC I/NET Seven (such as system pages), only one point may be selected for a trend definition.

4. Connect to the desired controller to select a point:

Note: You may enter point information manually in the Current Point section, bypassing the controller connection instructions below. When entering a point manually, make sure that the address, point type, and controller type are accurate.

a. If you are already connected to a controller, the top left list box displays the points resident in that controller. Skip to Step c if the desired point is in this controller.

Figure 24-2. Point Selection Screen

Note: Site Number indicates aconnection through a distributedlink.



b. If you are not currently connected to a controller, or if you wish to select a point from a different controller, complete the following steps to display the points in the desired controller:

✢ activate the radio button (located at the top right corner of each pane) for one of the other window panes.

✢ Select the Station button to display the Connect dialog box (see Figure 24-3).

✢ Select the desired link and click OK.

✢ If necessary, select the desired site and click OK.

✢ Select the desired controller and click OK to connect to the controller. The points associated with that controller now appear in the selected pane.

c. Click on the desired point to select it. The point address in the Current Point section is automatically populated with the full point address and type of the selected point. The Current Point section will automatically update this information every time you click on a point.

d. Select the controller type in the Control drop-down. This information is not automatically updated, and must be set manually.

Figure 24-3. Connect Dialog Box



e. Click OK to accept the selected point for this trend and return to the SevenTrends Definition editor.

Note: You may click the ... button to return to the Point Selection dialog at any time during the trend definition. However, once the trend defini-tion is saved, you cannot change the selected point.

5. Enter a Name for this trend or cell definition, up to 30 charac-ters. The default name for trends is in the format Point Name -- Trend Type if you are connected to the controller, and Point Address -- Trend Type if you are not connected. The default name for cells is Cell Number -- Trend Type.

6. Choose a Type from the drop-down list. The type cannot be changed once the definition is saved.

7. Define a Transient duration in days.

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.

8. Enter a Cell Number (0–1023). The cell number can be used to group samples in reports.

Figure 24-4. SevenTrend Parameters Editor



Note: The cell number for a trend definition can be modified. The cell number for a cell definition cannot be changed once the definition is saved.

9. Select OK to save your changes. The system returns you to the SevenTrends Definitions screen.

10. Select Close to leave the SevenTrends Definitions screen.

Modifying TrendsOnce a trend definition has been saved, only the name, transient duration, and cell number may be changed.

Existing samples for the trend are not updated with the new tran-sient duration and/or cell number; only new samples will reflect the changed information.

To modify a trend:

1. Select Trends Definitions from the main menu. The system displays the SevenTrends Definitions screen (see Figure 24-1 on page 24-3).

2. Select the desired trend from the list and click Modify. The system displays the SevenTrends Parameters editor.

3. Enter the new parameters, as desired. The point address and trend type are displayed, but cannot be edited.

4. Select OK to accept the changes and return to the SevenTrends Definitions screen, or Cancel to return to the SevenTrends Definitions screen without saving the changes.

Trend definition changes take place immediately. If you change the transient duration for a trend, the new value will not be used until the next-scheduled automatic transfer.

Modifying CellsOnce a cell definition has been saved, only the name and transient duration may be changed. If you change the transient duration of a cell, all trend definitions with a matching trend type and cell number will be updated, as though you had modified them manu-ally (see “Modifying Trends” above).



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.

Existing samples for the affected trends are not updated with the new transient duration; only new samples will reflect the changed information.

To modify a cell:


2. Select the desired cell from the list and click Modify. The system displays the SevenTrends Parameters editor.

3. Enter the new parameters, as desired. The trend type and cell number are displayed, but cannot be edited.

4. Select OK to accept the changes and return to the SevenTrends Definitions screen, or Cancel to return to the SevenTrends Definitions screen without saving the changes.

The system will immediately begin to change all trend definitions with a matching trend type and cell number. If you change the transient duration, the new value will not be used until the next-scheduled automatic transfer.

Deleting Trends and Cells

Note: Your ability to delete trend or cell definitions will depend upon the privileges assigned to your host password. Refer to Chapter 9, Pass-words, for more information.

When you delete a trend, all online samples associated with that trend are also deleted. Samples previously archived cannot be viewed or included on reports.

Caution: Exercise care when deleting 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.


SevenTrends Configuring the Host Station

To delete a trend or cell:


2. Select the desired trend or cell, and click Delete. The system displays the confirmation screen.

3. Select Yes to delete the trend or cell, or No to cancel the request. The system returns you to the SevenTrends Defini-tions screen.

Configuring the Host Station

DCUs send information to a host station only if the distribution group, distribution mask, and trend type of the DCU and the host station match.

Note: The cell number does not have to match between the DCU editor and the trend definition. The cell number in the trend definition is the one that will appear on reports.

✦ Use the SevenTrends Definitions editor, described in “Defining Trends and Cells” on page 24-3, to identify the trend types used.

✦ Use the Host Configuration editor, described in Chapter 2, Setup and Network Configuration, to define the SevenTrends distribution group and mask for a host station.

Archiving SevenTrends Data

Note: Trend archiving is available only for SevenTrends definitions that have a transient duration of zero (0), indicating no transient dura-tion. If the definition includes a transient duration greater than zero, those samples are discarded after the specified number of days. Use the SevenTrends Parameters Editor to set the Transient Duration parameter.


Archiving SevenTrends Data SevenTrends

TAC I/NET Seven displays the SevenTrends Archive Configuration editor (see Figure 24-5) when you select the Trend Archive Configuration option from the Event Archive Configuration editor (see Figure 6-24 on page 6-48).

Using the SevenTrends Archive Configuration editor, you can configure TAC I/NET Seven to save on-line trend data to an archive file. Archives can occur automatically based on triggers, or you can manually initiate an archive.

When samples are archived, they are removed from the online database and are no longer available for viewing, editing, or dele-tion through the TAC I/NET Seven editors; however, archived data may be used in reports.

TAC I/NET Seven does not connect to the archive database, and thus it can be moved out of the TAC I/NET Seven directory and into a different directory, to a network drive, or to portable media such as a ZIP or tape drive for offsite storage. You may keep your archive files on a floppy disk, or in a separate hard drive directory, if you want them in a readily accessible format.

Figure 24-5. SevenTrends Archive Configuration Editor


SevenTrends Archiving SevenTrends Data

The archive database is stored in the location specified as the Archive Directory in the INET Configuration Editor. 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 (01–12; 01 = January, 12 = December)

✦ DD = day of month (01–31)

✦ MPM = four-digit minutes past midnight (0000–1339)

✦ SS = two-digit seconds (00–59)

✦ .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 data-base format.

Performing Trend Archiving1. Activate () the Enable Seven Trends archiving checkbox.

2. If desired, activate () the Verify archive contents option to have TAC I/NET Seven verify the integrity of the archived data after it has been written.

3. Specify how much trend data should remain in Online Storage after an archive has completed:

✧ Limit by date – Use this option to specify the minimum number of days worth of data to retain online.

✧ Limit by record count – Use this option to specify the minimum number of records to retain online.

✧ Limit by physical size – Use this option to specify the minimum megabytes worth of data to retain online.


Archiving SevenTrends Data SevenTrends

4. Specify how messages generated by archive activity will be distributed:

a. Choose a Distribution group (1–4). The mask will be applied to this group.



5. Choose a setting for the Scheduled Trigger parameter. This setting specifies what to do when the schedule time is reached. The following options are available:

✧ Confirm – Ask the operator to confirm (allow) the archive.

✧ Automatic – Start archive without confirmation.

6. Use the Time of day field to specify the time of day to begin a scheduled archive.

Note: Due to system activity, the archive may not occur at the exact time specified.

7. Use one of the following options to specify on what days the archives will occur:

✧ Elapse time – Select this option to schedule archives based on an elapsed time since the last archive. Use the fields that accompany this option to specify an elapse time.

✧ Day of week – Select this option to schedule archives for a specific day of the week. Use the drop-down list to choose a day

8. Click one of the following buttons to archive trend data:

✧ OK – Click this button to save the settings and exit the editor. If you have activated () the Enable Seven Trends archiving option, TAC I/NET Seven will use the settings in this editor to automatically initiate trend archives.


SevenTrends Managing SevenTrends Data

✧ Archive Now – This button is only available when the Enable Seven Trends archiving option is selected. Click this button to manually initiate a trend archive. If you click this button before the number of unarchived records has reached the Minimum Online settings (as specified in the Online Storage section of this editor), you will receive an error message informing you that no archive can occur.

Note: There is no confirmation on this screen that the transfer has taken place. All success or failure messages are routed to AMT only, using the designated masking and priority.

Managing SevenTrends Data

You can view the data that is stored in the SevenTrends tables. You can also add, edit, or delete data. This allows you to clean up corrupted data or add missing data.

Note: Only online records can be viewed/edited; archived records are not accessible through the TAC I/NET Seven editors. Refer to the Seven-Reports help file for information on accessing archived SevenTrends data.

1. Select Trends Data Inquiry/Edit from the main menu. The system displays the SevenTrends Inquiry dialog, with a listing of the defined trends (see Figure 24-6).

Note: Cell definitions are not shown in this editor. Data can be viewed and edited only by trend definition, not by cell.

2. Choose the desired trend from the list and click the Select button, or double-click the trend to select it. The system displays the Inquiry Date Range screen (see Figure 24-7).

3. Enter the Earliest date and Earliest time to define the desired time period. Entries before this date/time will not be displayed.


Managing SevenTrends Data SevenTrends

4. When you have entered the desired start date and time, select the OK button.

The screen displays the SevenTrends Data screen, listing the online sample data for the selected trend. The fields shown on this screen will vary, depending on the trend type selected (see Figure 24-8).

5. To add a sample:

a. Select the Add button. The screen displays an entry screen, containing the appropriate entries for the selected trend type (see Figure 24-9).

b. Enter the date and time for the sample.

c. Enter the information for the selected trend type.

d. Select the OK button to add the entry to the trend table.

Figure 24-6. SevenTrends Inquiry Editor

Figure 24-7. Inquiry Date Range Selection


SevenTrends Managing SevenTrends Data

6. To modify a sample:

a. Select the desired entry from the list.

b. Select the Modify button. The screen displays an entry screen containing the current data. The contents of this screen will vary, depending on the type of trend selected.

Note: The date and time for the sample cannot be changed. If you need to alter the date and time for the sample, create a new entry with the desired date and time (see Step 5).

c. Enter the desired data in the appropriate field(s).

d. When all data is entered, select the OK button. The change takes place immediately.

7. To delete a sample:

a. Select the desired entry from the list.

Figure 24-8. Sample Consumption Cell Data

Figure 24-9. Adding Cell Data (Consumption Cell)


Managing SevenTrends Data SevenTrends

b. Select the Delete button. The system displays a confirma-tion screen.

c. Click Yes to verify that you want to delete the sample, or No to cancel the request.

The entry will be removed immediately. Deleted records cannot be restored, but the data may be re-entered manually (see Step 5).

Dynamic Data UploadThis option lets you manually upload the latest midnight Seven-Trends data for demand, override billing, consumption and runtime statistics. This option is useful when this data was not properly stored on the previous day because of communication problems, PC problems, etc.

1. Connect to the desired controller.

2. Select Edit Controller Dynamic Data Upload from the main menu. The system displays the following message:

Dynamic data upload request has been initiated.

3. Select OK. This dynamic data upload executes within sixty seconds.


Index

Aaccess control 17-1, 18-1

access initiated controladding 17-96copying 17-101deleting 17-101description 17-94modifying 17-101

door schedulesadding 17-32copy all 17-37copying 17-36deleting 17-37modifying 17-36

doorsadding 17-7, 17-9copying extension 17-29deleting extension 17-30mode schedules 17-19modifying extension 17-29

DPU configuration 17-6editors 17-2elevators 17-41

adding extension 17-42floors 17-43

groups 17-55adding 17-57assigning 17-82copying 17-62deleting 17-63modifying 17-62schedule conflict 17-60, 17-61

individualsadding key/card 17-65allocate ranges 17-81copying a key/card 17-84deleting a key/card 17-85display options 17-78field names 17-80schedule hierarchy 17-73, 17-77,

17-83selection of 17-63

key/card translationadding 17-48Card Translation option 17-14deleting 17-49description 17-47modifying 17-49

options 17-87order of operations 17-2personnel schedules 17-30tenants 17-50

adding 17-51copying 17-53deleting 17-54modifying 17-53

access group 17-55adding 17-57

© 2001–2010 Schneider Electric. All rights reserved. Index-1TCON299–05/10

A

copying 17-62deleting 17-63modifying 17-62schedule conflict 17-60, 17-61

access groupsassigning 17-82

access initiated control 17-94–17-101adding 17-96copying 17-101deleting 17-101modifying 17-101

action messageseditor 13-22printing 13-25

Activity Manager, Individual 17-72, 17-92

adaptive control 14-9, 14-14

addressbuilding of 1-18DCU 1-19link 1-18point 1-19system 1-18Tap

see address, link

AHU parameters 16-10

AIsee alarm inhibit

AI (analog input) pointsextension editors 8-61

AICsee access initiated control

alarm acknowledge 7-5display 7-3

alarm distribution 17-16

alarm inhibit 7-2, 13-9adding a point extension 13-9

copying a point extension 13-11deleting a point extension 13-12descriptioneditor, graphics 8-61modifying a point extension 13-11

alarm prioritydial Tap 6-2direct connect Tap 6-2routine 6-2see also message priority

alarmscontrolling 17-22totals 6-31

all lights on/off 4-7

allocate ranges 17-81

alternate graphics path 8-22

AMTalarm colors 6-6alarm totals 6-31audible alarms 6-8

AMT Video 6-57

analog points, defined 8-57

anti-passbackactivate 17-14entry zone 17-15exit zone 17-15hard, soft, graced 17-71manual reset 7-5–7-6, 7-14–7-15reset time 17-15reset, manual 7-5–7-6, 7-14–7-15reset, scheduled 17-15, 17-20

AO (analog output) pointsextension editors 8-62

APBactivate 17-14entry zone 17-15exit zone 17-15

Index-2 © 2001–2010 Schneider Electric. All rights reserved.TCON299–05/10

C

manual reset 7-5–7-6, 7-14–7-15parameter 17-71reset time 17-15reset, scheduled 17-15, 17-20

APB reset, manual 7-5–7-6, 7-14–7-15

application specific controllersdata, displaying 22-2description 22-1interface controller, updating 22-7markers, system pages 8-70names, modifying 22-4parameters, copying 22-5parameters, modifying 22-3updating 22-8

archive, Docutrenddescription of 24-9

arming terminal configuration 18-11

ASCsee application specific controllers

ATSsee automatic time schedule

Auto Report Generation 10-31

automatic DCU save 2-33

automatic page display 8-56

automatic time schedule 10-8host 10-8lighting zones 15-9standalone in micro regulators 21-9see also host time schedule

automatic tune 14-23

Bbackup 1-21–1-22

recommended files 1-23

binary file 4-15

broadcast review 2-38

broadcast time 2-36

button enable 17-44

button selection 17-44

button, extension (EXT)door points dialog box 8-59point selection dialog box 8-60

button, option (OPT)point selection dialog box 8-53, 8-55,

8-57

button, user-defined 1-25

bytes remaining 4-8

CC

see calculated point

Calc, DDC module 8-63

calculated point 11-1adding 11-1copying 11-4deleting 11-5editor 8-62editor, graphics 8-61, 8-62memory requirements 11-1modifying 11-4parameters 11-3

calculationssee calculated point.

Captured Video, CCTV 6-56

Card Number 17-66


D

Card Translation option 17-14

CCTVin AMT 6-55markers on system pages 8-73

cell mask 2-3

character completion timeout 20-2

circuit assignments 15-8

CNsee consumption

coefficient index 4-24

color palette 6-6

common sensor 18-8

configurationstation conflict 2-24

between sites 2-24summaries 7-1, 7-9

DPU 7-13host 7-9link 7-10MR 7-12station 7-11UC 7-12

connecting to the system 1-15

consumption 13-1editor, graphics 8-62point extension


pulse input 13-1

control commands 4-20

control descriptions 4-20

control point (failsafe) 14-8

controller

configuration/status 4-1details 4-3memory 4-9status, viewing 4-8summary 7-1

controller summaryalarm acknowledge 7-5manual mode 7-4momentary release 7-5test mode 7-4zoom 7-6

conversion coefficients 4-23, 21-9

conversion equation 4-24

CTS handshake 3-8

current demand point 10-24

cycle adjustment 10-20

DDA (discrete alarm) points

extension editors 8-61

data bits 3-8

data upload, dynamic 4-19, 24-16

database last changed 4-8

database print 2-39

daylight savings 4-6

DC (discrete control) pointsextension editors 8-62

DCUautomatic save 2-33backup files 1-23


D

configuration 4-1database last changed 4-8daylight savings 2-32, 4-6firmware status 4-8message mask 4-4station parameters 4-19temperature control 4-7time scheduling 4-7time zone world map 4-6

copying points 5-3download 4-15editing points 5-4modifying points 5-3passwords 9-29

editor 9-29preassignment 9-11

selection 9-5synchronization 2-31

DDCsee direct digital control

DDC menu option, graphics editorselecting 8-62, 8-64

default system page 2-4, 8-74

delaybefore break 14-20before make 14-20before off 15-4before response 20-2

demand controlgraphics editor 8-62point extension


demand interval 10-24

demand temperature override 10-19

deselecting objects 8-8

DI (discrete input) pointsextension editors 8-61

dialafter edit 17-90connections status, hang up 8-69integrated 3-4multiple site 3-9

dial parameters, IAS 18-17

dialog boxaddress conversion utility 8-18ASC marker 8-70DDC line options 8-64digital point drawing styles 8-57door parameters 2-28extensions 8-61load a small bitmap 8-17page marker 8-66point selection 8-54, 8-59select a library symbol 8-15

digital CCTV 6-55, 8-73

digital point drawing styles dialog boxstate 0 definition 8-55state 1 definition 8-55

digital state 0, setting 8-57

Direct digital controlmodules

RESET 8-63

direct digital controldamper control 16-18editors 14-1helpful hints 14-24history 14-21line

adding 8-64options dialog box 8-64


D

modules2-Pos 14-3adding 8-62Calc 8-63FLOAT 8-63, 14-10HiLo 8-63, 14-17PID 8-63, 14-6RELAY 14-19RESET 8-63, 14-15

tuning 14-21automatic tune 14-23input/output plot 14-23manual tune 14-22

see also system pages

disabled points 2-38

disabled summary 7-8

disconnecting 1-17

discrete points 8-55

display options 17-78

distribution group 2-3

distribution parameters 4-4

DM (discrete monitor) pointsextension editors 8-62

DO (discrete output) pointsextension editors 8-62

Docutrendarchiving data 24-9configuring the DCU 24-1configuring the host station 24-9dynamic data upload 4-19, 24-16editors 24-2midnight statistics 4-19, 24-16sequence of operations 24-1

doorcode 17-16mode schedules 17-19naming of 2-28

parameters 17-16release switch 17-17schedule

adding 17-32, 17-36copying 17-36deleting 17-37modifying 17-36

sense switch 17-16strike 17-16

door extensionadding 17-9copying 17-29deleting 17-30modifying 17-29

door features 17-22

door open too long 17-16

door summary 7-13

doorsaccess control 17-7–17-30menu option, graphics editor

selecting 8-70

Dorado LED control 17-14

downloadcontroller/tap 4-15date 4-3MIP 4-14time 4-3

DPUconfiguration 17-6dial type 17-89summary 7-13

driver, I/NETdescription 2-1setup 2-1

dynamic data upload 4-19, 24-16


E

Eeditor

action message 13-22alarm inhibit 8-61ASC marker 8-70calculated point 8-61, 8-62consumption 8-62demand control 8-62elevator control 8-62event definition 8-61, 8-62LCD, I/SITE Page 23-1lighting control 8-62override billing 8-62runtime 8-62temperature control 8-62time scheduling 8-62trend sampling 8-61, 8-62unitary controller 8-62

elevator 17-14, 17-41adding extension 17-42floor designation 17-43floors 17-43

elevator control editor 8-62

emergency shed level 10-26

engineering units 4-25

entry zone 17-15

equipmentcounts high 4-24counts low 4-24mapping 19-3

equipment mapping 19-8

EVsee event definition

event action 13-21–13-24adding 13-21

copying 13-23deleting 13-24message printing 13-25modifying 13-23

event definition 13-12–13-16action message 13-12editor, graphics 8-61, 8-62event sequence 13-12, 13-16memory requirements 13-12point extension


event printing 13-25

event sequence 13-16–13-21adding 13-17copying 13-20deleting 13-21event definitions 13-16modifying 13-19

exit reader 17-12

exit zone 17-15

exit, graphics editor file menu option 8-4

exiting I/NET 1-18

extension (EXT) buttondoor points dialog box 8-59point selection dialog box 8-60

extension editorssee editorssee also extension editors, graphics

extension editors, graphicsAI (analog input) points 8-61AO (analog output) points 8-62DA (discrete alarm) points 8-61DC (discrete control) points 8-62DI (discrete input) points 8-61


F

DM (discrete monitor) points 8-62DO (discrete output) points 8-62GI (analog input) points 8-61GO (analog output) points 8-62PI (pulse input) points 8-62

extensions dialog box 8-61

extensions, point, adding 8-60

Ffailsafe 14-8

failsafe command 14-5

features, door 17-22

field names 17-80

file menu, graphics editor 8-4address conversion option 8-18close option 8-4exit option 8-4load library symbol option 8-14open option 8-4, 8-5

files, bitmapimporting 8-3

firmware status 4-8

first key auto-unlock 17-17

Float DDC module 8-63, 14-10

floors 17-43designation 17-44index number 17-43selection time 17-43

FLT parameters 16-20

function selection 9-5

Functions, User-defined PIN Pad 17-22

GGI (analog input) points

extension editors 8-61

GO (analog output) pointsextension editors 8-62

graphic dial icon, adding 8-68

graphic page summary 7-16

graphic pagesASC markers 8-70backup files 1-23graphic dial icon

adding 8-68properties 8-20

graphics editorASC marker editor 8-70DDC menu option, selecting 8-62,

8-64doors menu option, selecting 8-70file menu options

address conversion 8-18exit 8-4load library symbol 8-14save as library symbol 8-14

mouse shortcuts 8-10shortcuts 8-10starting 8-4tool menu options

circle 8-38curve 8-39ellipse 8-38library symbol 8-36polygon 8-38rectangle 8-38round rectangle 8-38text 8-36

graphics properties 8-20


I

groups 17-55adding 17-57assigning 17-82copying 17-62deleting 17-63modifying 17-62read only 9-9, 9-15schedule conflict 17-60, 17-61

Hhandles, object 8-10

hardware coefficients 21-9

hardware points, defined 8-51

help screens 1-7accessing 1-7exiting from 1-7moving around in 1-7

highlightingusing a mouse 1-5using the keyboard

push-buttons 1-6text 1-6

HiLo DDC module 8-63, 14-17

history 14-21

host ATSsee host time schedule

host configuration, backup files 1-23

host dial icon 8-69

host passwords 9-2

host summary 7-9

host time scheduleadding 10-9copying 10-12

deleting 10-13modifying 10-12

HPMP parameters 16-14

II/NET Communications Interface

see ICI

I/STATinactivity timeouts 21-13LED functions 21-13MR parameters 21-11

IAS 18-1

ICIcontroller type selection 4-7interface type 20-1MODBUS

addresses 20-3protocol 20-1

point addressing 20-3point types 20-3port status 20-1program, logic controller 20-1protocol 20-2register types 20-3slave address 20-2

iconsASC markers 8-70host dial 8-69page reference 8-3

Image 17-69

importing bitmap files 8-3

independent schedule 10-3

Indirect User Settings 9-13


K – L

Individual Activity Manager 17-72, 17-92

individual number 17-66

individuals 17-63adding a key/card 17-65allocate ranges 17-81copying a key/card 17-84deleting a key/card 17-85display options 17-78field names 17-80schedule hierarchy 17-73, 17-77,

17-83

industrial controller interfacesee ICI

input filter 14-12

input high limit 14-4, 14-7, 14-12

input low limit 14-7, 14-12

input/output plot 14-23

Integral digital CCTV 6-55, 8-73

integrated dial 3-4

inter-card interval 17-13

interface controllerconfiguring 21-2

interval timer 14-20

intruder alarm system 17-22

Intrusion Alarm System 18-1

Intrusion Alarm Zone Configuration 18-14

IP dialer 18-17

K – Lkey/card translation 17-47, 17-47–17-49

adding 17-48deleting 17-49modifying 17-49

keyboardselecting push-buttons with 1-6selecting text with 1-6

LANaddress 3-2speed 3-2

latitude 4-5

LCD, I/SITE Page 23-1

LED polarity 17-14

library symbol. selecting 8-15

library symbolsbackup files 1-23importing 8-3

lighting circuit 15-1adding 15-2copying 15-5deleting 15-5modifying 15-5

lighting zone 15-6–15-11adding 15-6automatic time schedule (ATS) 15-8,

15-9circuit assignments 15-8copying 15-10deleting 15-10modifying 15-10

Limited-access Users 9-15

linkadding 2-14penetrating 2-12summary 2-12, 7-10

live colors 8-22

Live Video, CCTV 6-56


M

load a small bitmap dialog box 8-17

loading details 4-8

logging in 1-14

longitude 4-5

lookup tables 4-26

Mmain window title 2-3

Manager, Individual Activity 17-72, 17-92

manual mode 7-2, 7-4

manual tuning 14-22

markerASC 8-70CCTV 8-73dial 8-68page 8-66tool 8-71

master point 10-5

master schedule 10-3

maximum bump 14-9, 14-14

maximum overshoot 14-9, 14-14

MCIconfiguration editor 16-2micro regulators, number of 21-1MR LAN

channels 21-1number of micro regulators 21-1

MCUadding 2-25Summary 2-17

memory interface processordownload 4-15

module description 4-14

memory requirementscalculations 11-1runtime 13-4

memory status 4-8

menu selectionformat in manual 1-3using a mouse 1-2using the keyboard 1-3

message mask 4-4controller configuration 4-4

message prioritycritical 4-4, 6-2definition of 4-5dial Tap 6-2direct connect Tap 6-2none 4-4, 6-2parameter 4-4priority 4-4, 6-2routine 4-4, 6-2

message routingmask 2-3received at host 6-9received at printer 6-9

message type parameter 17-17

micro regulatorapplications, typical 21-1control description 21-1, 22-1copying data 21-3database, creating 21-3hardware coefficients 21-9interface, configuring 21-2MR copy 21-3resident DDC 21-5standalone ATS 21-9summary 7-12

MIP


N

see memory interface processor

MODBUSsee ICI

mode schedules 17-19

momentary release 7-5

monthly consumption point 10-25

mouse shortcuts 8-10

MR copy 21-3

MR summary 7-12

MRIconfiguration editor 16-2micro regulators, number of 21-1MR LAN

channels 21-1number of micro regulators 21-1

MR-resident DDC modules 8-62, 21-5

multi point trend plot 12-7–12-17

multiple site dialhost dial icon 8-69network configuration required 3-9

Nname, last and first 17-68

network configuration 2-5

network functions 2-30

new host passwords 9-1

noise band 14-10, 14-14

normal shed level 10-25

notationfile names 1-1menu selections 1-1

Oobjects

copying 8-9deleting 8-8deselecting 8-8handles 8-10importing 8-16positioning 8-9resizing 8-10selecting 8-7

off duration 15-4

off normal points 2-38

off normal summary 7-7

old value, point 7-3

on duration 15-4

OP5 arming terminal configuration 18-11

operator timeout 1-15, 2-4action 1-15, 2-3

optimized start lookahead 10-18

optimized stop 10-18

option (OPT) buttonpoint selection dialog box 8-53, 8-55,

8-57

options 17-87

output high limit 14-8

output low limit 14-8

output ramp limit 14-8

outside air temperature 10-18

override access codes 19-3

override billing 19-1access codes 19-3adding access codes 19-6


P

adding equipment mapping 19-8editor, graphics 8-62entering override parameters 19-3equipment mapping 19-3, 19-8equipment points 19-6extension editor 19-3override parameters 19-3wink off interval 19-6wink on interval 19-6

override parameters 19-3

override shed level 10-26

Ppage

acknowledge 7-7properties 8-23reference icons 8-3see also system pagesummary 7-16

parent point 16-3

parity 3-8

passwordsadding a host password 9-2adding a new host 9-1auto connect 9-6controller 9-29copying 9-28DCU passwords

preassignment 9-11recovery of 9-30

DCU selection 9-5deleting 9-27editor 9-1function selection 9-5host 9-2

modifying 9-27tenant selection 9-7

personal identification number 17-71

personnel schedulesaccess control 17-30copy all 17-37description 17-30door access 17-30

phone numbers 3-4

PIsee pulse input

PID DDC module 8-63, 14-6

PID parameters 16-18

PIN 17-22, 17-71

PIN enable 17-21

PIN Pad Functions 17-22

point extensions, adding 8-60

point selection dialog box 8-54, 8-59

point time scheduleadding 10-1copying 10-7deleting 10-8modifying 10-7

pointsadding to controller 5-1adding to system pages 8-51addresses 5-5addressing 5-5AI (analog input), extensions 8-61analog, defined 8-57AO (analog output), extensions 8-62controlling 7-3copying 5-3DA (discrete alarm), extensions 8-61DC (discrete control), extensions 8-62deleting 5-4


R

DI (discrete input), extensions 8-61disabled 2-38DM (discrete monitor), extensions

8-62DO (discrete output), extensions 8-62GI (analog input), extensions 8-61GO (analog output), extensions 8-62hardware, defined 8-51modifying 5-3printing 2-39software, defined 8-51value display 7-2zoom 7-6

pop-up calculator 4-24

preassigning DCU passwords 9-11

primary input 14-16

printerdatabase printing 2-39event 13-25

printer Tap 3-8

process variable 14-4

program extensions 4-6

proportional band 14-8, 14-13, 14-23

pulse inputconsumption 13-1extension editors, graphics 8-62

Rrate interval 14-9, 14-13, 14-23

reader type 17-9

Read-only groups 9-9, 9-15

Record type 17-58, 17-70

Recycle bin 17-63

Refresh Interval 2-3

refresh interval 2-3

relay module 14-19

report generation, automatic 10-31

reset interval 14-9, 14-13, 14-23

reset module 14-15

resident in DPU 17-69

Restore from Local Host option 2-21

restore hosts 2-21

restore, software 4-15

runtime 13-4editor, graphics 8-61, 8-62memory requirements 13-4point extension

adding 13-5copying 13-7deleting 13-8modifying 13-7parameters 13-5

Ssample control mode 12-3

SAVE file 4-15

schedule, auto report 10-31

SCU Sounder 17-27

SCU Tamper 17-103

Searching Captured Video 6-57

Sec/Code 17-21

Sec/PIN 17-21


S

secondary group schedule 17-74, 17-75

secondary input 14-16

settling time 14-9, 14-14

shift rotations 17-30

shortcuts 8-10

shunt 17-17

SIA setup 18-17

siteadding 2-22summary 2-14

slave schedule, adding 10-5

software points, defined 8-51

software restore 4-15

Sounder 17-27

space temperature 10-18

special days 10-14adding 10-14broadcast 2-34broadcast review 2-38deleting 10-16modifying 10-16

starting I/NET 1-13

state 4-21close 4-21trip 4-21

state descriptions 4-21state 0 selection, graphic page 8-55state 1 selection, graphic page 8-55

stationadding 2-23restore 4-12, 4-13

on a DPI 4-14on a DPU 4-14

save database 4-12, 4-13summary 2-16, 7-11

see also station conflictsee also station parameters

station conflict 2-24

station parameterscontrol descriptions and commands

4-20defining 4-19entering 4-20state descriptions 4-21, 4-22

status, controller 4-8

stop bits 3-8

stretch to fit 8-24

strike duration 17-16

summaryconfiguration 7-1, 7-9

DPU 7-13host 7-9link 7-10MR 7-12station 7-11UC 7-12

controller 7-1alarm acknowledge 7-5manual mode 7-4momentary release 7-5test mode 7-4zoom 7-6

disabled 7-8door 7-13DPU 7-13host 7-9MR 7-12off normal 7-7page 7-16station 7-11system page 7-16UC 7-12

sunrise/sunset 4-5


T

system driver 2-1

system pagesadding points 8-51ASC markers 8-70backup files 1-23controlling layout 1-23DDC lines 8-64DDC modules 8-65, 8-71default page 2-4, 8-74discrete points 8-55introduction 8-1modifying 8-4multiple site dial 8-68point extensions 8-61points 8-1retrieving obstructed 1-24summary 7-16testing 8-67using 8-73viewing 8-67, 8-73see also graphics editor

System Sensor Selection 18-7

System View 2-3configuring your network 2-6interface description 1-31

TTamper, SCU 17-103

TapAD/AA 3-5configuration editors 3-1

parameters 3-1parameters updated 3-1

download 4-15integrated dial 3-4

name 3-2

target damping 14-9, 14-14

target event action 13-24

TCsee temperature control

telephone number 3-4

temperature control 10-16editor, graphics 8-62point extension 4-7


tenant 17-50adding new 17-51copying parameters 17-53deleting 17-54modifying parameters 17-53selection 9-7

test mode 7-2, 7-4

throttling range 14-13

time delay 14-20

time schedulingeditor, graphics 8-62lighting zone definitions 15-9point extension 4-7see also point time schedule

time zones 4-5, 4-6

tool menu, graphics editorcircle option 8-38curve option 8-39ellipse option 8-38library symbol option 8-36polygon option 8-38text option 8-36

tools, user-defined 1-25


V – Z

total bytes available 4-8

TRsee trend sampling

transaction distribution 17-16

translation table 17-47–17-49

trend log 12-18deleting 12-20

trend plot 12-6multi point 12-7–12-17

trend sampling 12-1adding 12-1copying 12-4deleting 12-5editor 8-62editor, graphics 8-61, 8-62modifying 12-4

TSsee point time schedule

tuning 14-21

turn around time 14-13

two-man rule 17-26

two-position module 8-63, 14-3

UUC

copy 16-3pointers 16-22summary 7-12see also unitary controller

UCIsee unitary controller interface

unitary control parameters 16-5

unitary controlleractivating 16-4configuring 16-2copy 16-3editor 8-62editor, graphics 8-62inputs and outputs 16-8, 16-12,

16-15, 16-19, 16-21overrides 16-9, 16-12, 16-16parameters 16-5

AHU 16-10–16-13FLT 16-20–16-21HPMP 16-14–16-17PID 16-18–16-20VAV 16-6–16-10

pointers 16-22setpoints 16-7, 16-11, 16-15summary 7-12UC copy 16-3, 16-4

unitary controller interfaceconfiguring 16-1creating the database 16-3parent point 16-3

Use Object Pen 8-21

User, Limited-access 9-15

User-defined Door Features 17-22

user-defined PIN 17-71

user-defined tools and buttons 1-25

V – ZVAV parameters 16-6

windowscontrolling layout 1-23retrieving 1-24


V – Z

Windows user account 1-14, 9-3

wink cycles 15-4

wink source 15-4

zone definitionscircuit assignment 15-8copying zones 15-10time schedule 15-9

zoom 7-6


Schneider ElectricBuildings – EuropeJägershillgatan 18 213 75 MalmöSweden Phone: +46 40 38 68 50Fax: +46 40 21 82 87

Schneider ElectricBuildings – Americas1650 W. Crosby Rd.Dallas, TX 75006 USAPhone: +1 (972) 323 1111Fax: +1 (972) 242 0026

Schneider ElectricBuildings – Asia-PacificLevel 3/2A Lord StreetBotany NSW 2019 AustraliaPhone: +61 (0) 2 8336 6100Fax: +61 (0) 2 8336 6190

www.schneider-electric.com/buildings

You may obtain copies of this document by ordering the following document number:.

TCON299 – 05/10