Technical Document

NiagaraAX-3.x User Guide

May 1, 2007
NiagaraAX User Guide
Copyright © 2007 Tridium, Inc.
All rights reserved.
3951 Westerre Pkwy., Suite 350
Richmond
Virginia
23233
U.S.A.

Copyright Notice
The software described herein is furnished under a license agreement and may be used only in accordance with the terms of the
agreement.
This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium
or machine-readable form without prior written consent from Tridium, Inc.
The confidential information contained in this document is provided solely for use by Tridium employees, licensees, and system
owners; and is not to be released to, or reproduced for, anyone else; neither is it to be used for reproduction of this Control System
or any of its components.
All rights to revise designs described herein are reserved. While every effort has been made to assure the accuracy of this document,
Tridium shall not be held responsible for damages, including consequential damages, arising from the application of the information
contained herein. Information and specifications published here are current as of the date of this publication and are subject to
change without notice.
The release and technology contained herein may be protected by one or more U.S. patents, foreign patents, or pending applications.

Trademark Notices
BACnet and ASHRAE are registered trademarks of American Society of Heating, Refrigerating and Air-Conditioning Engineers.
Microsoft and Windows are registered trademarks, and Windows NT, Windows 2000, Windows XP Professional, and Internet
Explorer are trademarks of Microsoft Corporation. Java and other Java-based names are trademarks of Sun Microsystems Inc. and
refer to Sun's family of Java-branded technologies. Mozilla and Firefox are trademarks of the Mozilla Foundation. Echelon, LON,
LonMark, LonTalk, and LonWorks are registered trademarks of Echelon Corporation. Tridium, JACE, Niagara Framework,
NiagaraAX and Vykon are registered trademarks, and Workbench, WorkPlaceAX, and AXSupervisor, are trademarks of Tridium Inc.
All other product names and services mentioned in this publication that is known to be trademarks, registered trademarks, or
service marks are the property of their respective owners.The software described herein is furnished under a license agreement and
may be used only in accordance with the terms of the agreement.
 CONTENTS

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Document Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About NiagaraAX Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

Well designed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
The Niagara Framework solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
About control systems integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
About Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
About Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
About common networking and Internet protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
About programming for non-programmers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
About embedded systems capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
About distributed systems capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
About component software design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
About Niagara software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
About Baja . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
About APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
javax.baja . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
com.tridium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
About Niagara building blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
About modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
About module characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
About jar files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
About module versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
About module directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
About module benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
About components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
About slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–10
Slot type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Slot name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Slot definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
About master/slave components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–11
About point components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–11
About component naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–12
Escaped names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
About palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13
About presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
About presentation modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13
About presentation xml (px) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13
About presentation design philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14
About presentation media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14
About stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
About BOG files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–16
About ORDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16

NiagaraAX-3.x
i
User Guide
 May 1, 2007

Examples of ORDs: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–17

About schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–17
Types of schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–17
Types of space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–18
Types of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–18
About views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–19
About lexicons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–19

About Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1

Tour of the Workbench GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
About Workbench window controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
About the side bar panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
About side bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
About the side bar title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Types of side bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
About the bookmark side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
About the help side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
About the nav side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
Types of nodes in the nav side bar tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
About the nav side bar toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
About the palette side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
About the palette side bar toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
About the jobs side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
About the bound ords side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
About the widget tree side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
About the properties side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
About the view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–10
About the console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–11
About the menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–12
About the toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–12
About the locator bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–13
About the view selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–14
Types of popup menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–14
About the nav side bar popup menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
About the wire sheet popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
About the property sheet popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Px Editor popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Types of data–presentation controls and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–16
Table controls and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–17
Batch editing (or batch processing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–17
Chart controls and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–18
Customizing the Workbench environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–19
Creating Additional Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–19
Creating tabs in the view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–19
Types of Workbench options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–20
General Workbench options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–21
Alarm console options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–21
Alarm portal options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–22
Bajadoc options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–22
Text editor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–22
Lexicon editor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–23
Px editor options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–23
Wiresheet options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–24
Lexicon options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–24

Data and Control Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1

About control points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Types of control points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Other control components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
About data value categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

NiagaraAX-3.x
ii
User Guide
May 1, 2007

About point types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

About point Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
About point inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
About point actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
About override actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
About set (Fallback) action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Modifying default actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
About point facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Accessing and editing facets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Facets importance for Enum points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Effect of facets on point actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Effect of facets on proxy points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
About point extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
Extension process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9
Types of point extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–10
About the proxy extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–10
About control extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–11
Types of control extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11
About alarm extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–12
Types of alarm extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
About history extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–13
Types of history extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
About control triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
How triggers are used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–15
About related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–15
About point status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
Types of status flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–15
Priority of status indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–16
How status flags are set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–16
Simple control point status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
Propagate Flags status option (linked Math and Logic objects) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17
Proxy point status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
About “isValid” status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–18
About proxy points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–18
Location of proxy points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–19
How proxy points are made . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–19
Proxy points versus simple control points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–23
ProxyExt properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–23
About writable points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
About the priority scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–24
Priority input scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–24
Priority linking rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25
Priority level conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–25
About minimum On and Off times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–25
About composites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Some composite examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–26
Point-level composite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Folder-level composite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–28
Composite issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–29

Driver architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1

What are networks? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Where are networks located? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
About Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Network component hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
About network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
About device components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
About device extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
About the Driver Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4

NiagaraAX-3.x
iii
User Guide
 May 1, 2007

Driver Manager New and Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4

New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Common network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Network status properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
About network Alarm Source Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
About Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Monitor properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Monitor considerations by driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
About Tuning Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Tuning Policy properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Tuning Policy considerations by driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
About poll components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Poll scheduler operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Poll component properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
Additional network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–11
About communication components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
About driver-specific properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
About the Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Device New Folder and New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–13
New Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
All Descendants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Device Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–15
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
Device “gang” edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
About Device Discover, Add and Match (Learn Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–16
About Learn toggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Match (Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–18
Manager table features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–19
Table options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Column resorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Common device components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Device status properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–20
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Device Alarm Source Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–20
Device address properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–21
Poll Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
Driver-specific device slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–21
Virtual Gateway component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–21
About virtual component spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
About virtual gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
Types of device extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
About the Points extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–25
About the Histories extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–25
About the Retry Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–26
About the Alarms extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–26
Alarms extension properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
About the Schedules extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–27
About the Point Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Points New Folder and New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–28
New Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Point Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–30
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Proxy point “gang” edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31

NiagaraAX-3.x
iv
User Guide
May 1, 2007

About Point Discover, Add and Match (Learn Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–32

Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
About other Points views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–36
About Histories extension views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37
History Import Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–37
History Import New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
History Import Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
About History Import Discover, Add and Match (Learn Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39
History Export Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–41
History Export New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
History Export Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
About History Export Discover, Add and Match (Learn Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43
About Schedules extension views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44
Schedule Import Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–45
Schedule Import New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–45
Schedule Import Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–45
About Schedule Import Discover, Add and Match (Learn Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–47
Schedule Export Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–48
About the Niagara Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–49
NiagaraNetwork component notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–50
About the Fox Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
About History Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–51
Niagara Station Manager notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–54
Station Learn and Discover notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
Station Add notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–54
NiagaraStation component notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–55
About station status properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–55
About client connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–55
About server connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–55
About station “provisioning” extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–55
About the Bql Query Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–56
About Bql Query Find filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
About Bql Query Match filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–57
About Bql Query Save, Load, and Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
Niagara proxy point notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–59
Proxy of a proxy, other candidates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–59
Link control and Niagara proxy points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–59
Station Alarms notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–60
Station Schedules import/export notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–60
Niagara schedule import/export default configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–61
Schedule Export Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–61

Field Bus Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

Port and protocol variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Ethernet-connected driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Serial-connected driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Special-port driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Learn versus New devices and points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Serial tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Serial tunnel overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Client side (PC application) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Installing the serial tunnel client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
To install the serial tunnel client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Serial tunnel client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Serial tunnel client installation details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Station side (TunnelService) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Configuring the serial tunnel server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
To configure the station for serial tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
About serial tunnel connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6

NiagaraAX-3.x
v
User Guide
 May 1, 2007

Serial tunneling usage notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

Tunneling client messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7

About Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1

Types of History Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
About the history service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
About the history extension manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
About history service property sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
History service actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
About the audit history service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
About the log history service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
Types of history space views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
About the chart builder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
About Time Zones and the Chart Builder view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
About the database maintenance view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
About the nav container view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
Types of history views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
Types of history data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–10
About the history chart view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–10
About the history table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–10
About the collection table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–11
About the history summary view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–11
About the history editor view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–12
About the history process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–13
About delta logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–14
Add history extensions to a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–15
Configure history extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–16
About history names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–17
Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–18
About editing history data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–19

About alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1

Alarm examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Overview of the alarming process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
About alarm sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
About alarm extensions and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
About alarm extension properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
About alarm instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
About notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
About the alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
About memory alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
Common alarm controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8
Types of alarm service views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–9
About alarm extension manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–9
Types of extension manager display features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–10
About the Instructions Manager view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–11
About the alarm class summary view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–12
About the alarm database maintenance view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–13
About the Alarm details dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
Types of alarm database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
About alarm service property sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–15
About alarm class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15
About alarm escalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–16
About alarm class properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–16
About alarm class mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–17

NiagaraAX-3.x
vi
User Guide
May 1, 2007

Types of alarm recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–18

About the console recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–19
About the alarm console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–19
Types of alarm details view dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–20
About the station recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–22
About the email recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–23
About the lineprinter recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7–23

About Presentation XML (Px) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1

About Px views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
Px views as slot properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
About the New Px View wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
About Px files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Shared Px files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
About Px viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4
About Px Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5
About the Px Editor Canvas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
View Source XML dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6
About Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7
Widget layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Types of panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8
Widget painting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9
About widget properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–10
Animating Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Data binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–10
Types of bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–11
Types of binding properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–12
About bound label bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–13
About value bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–13
Types of Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–13
About spectrum bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–14
About setpoint bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–14
About increment setpoint bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–15
About spectrum setpoint bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–15
About action bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–15
About table bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–15
About field editor bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–16
Relative and absolute bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–16
About Px target media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–17
About Web Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–17
Default Wb Web Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–17
Basic Wb Web Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–18
Default Hx Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–18
Basic Hx Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–19
Px Editor workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–19
About the Make Widget wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–19
Make Widget wizard: examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
Create a bound label widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–21
Create a widget using a palette kit module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–23
Create a widget with a Workbench view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–26
Create a widget using a component properties option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–28
Create an action widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–30
Create a Time Plot widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–32
Create a Chart widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–34
About the Nav file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36

NiagaraAX-3.x
vii
User Guide
 May 1, 2007

Nav file elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–37

About the Nav File Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–38
Nav File Editor source objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–39
Nav File Editor result tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–39
Nav File Editor buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–39
About Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–40
About the reporting process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–40
Types of report components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–41
About the ReportService component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–41
About the ExportSource component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–41
About the EmailRecipient component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
About the ComponentGrid component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–42
About the ReportPane component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–43
About the SectionHeader component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–43
About the Grid Table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–44
About the Grid Label Pane view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–44
About the Grid Editor view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–46
About the Report Edit Row and Edit Column dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–46
About the ReportPx file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8–47

About Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1

Security model overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Categories and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
Users and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
About built-in users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
About authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
Permissions and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
About permission levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Component permission levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
File permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
History permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
UserService security notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
About user audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
AuditHistoryService configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
AuditHistory content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
Multi-station security notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
Domain-wide cookies authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
To configure domain-wide cookies authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
Alarm ack permission notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
UserService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
UserService properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–10
UserManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–10
User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–11
Lockout notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
PermissionsBrowser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–13
Show Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13
Permissions abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13
Access permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14
CategoryService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14
CategoryManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–15
Category properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16
Category caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16
CategoryBrowser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–16
Show Configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16
CategorySheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9–17

About Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1

About the scheduling model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
Schedule component categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–1
Schedule component views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–2

NiagaraAX-3.x
viii
User Guide
May 1, 2007

Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Schedule component links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–2
Weekly schedule links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Trigger schedule links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
Schedule special events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–3
Schedule exports and imports (master/slave) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–3
About weekly schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
Types of weekly schedule components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–4
About the BooleanSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
About the EnumSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
About the NumericSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
About the StringSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Weekly schedule output processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–4
Out slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Out Source slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Next Time and Next Value slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Weekly Scheduler view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–5
Weekly Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Special Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–7
Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–10
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–12
About calendar schedules (holidays) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13
CalendarSchedule Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13
Calendar Scheduler view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–13
Adding calendar events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–14
Right-click menus and other controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–15
Calendar day selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15
Date selection notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–15
Date range selection notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–16
Week and day selection notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–16
Custom selection notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–17
CalendarSchedule slots and other notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–17
About trigger schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–18
Trigger Scheduler view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–18
Adding trigger events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–19
Adding trigger event times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–19
Right-click menus and other controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–20
TriggerSchedule slots and other notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–21
Trigger Missed slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–21
Using schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–21
Adding a schedule or calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–21
To add a component from the schedule palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–21
To copy an existing, saved (configured) schedule component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22
Configuring schedules and calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22
Configuring weekly schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–22
To configure a weekly schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22
To configure a weekly schedule’s properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22
To configure the weekly (normal) schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22
To add and configure special events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–23
To review a weekly schedule’s configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–23
Configuring calendar schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–23
To configure a calendar schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–23
Configuring trigger schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–24
To configure a trigger schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–24
Linking schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–24
Linking weekly schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–24
To link a weekly schedule using the wire sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–24
To link a weekly schedule using the Nav tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–25
Linking trigger schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–25
To link a trigger schedule using the wire sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–25
To link a trigger schedule using the Nav tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–25
Importing schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–26
Importing NiagaraAX schedules or Bacnet Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10–26

NiagaraAX-3.x
ix
User Guide
 May 1, 2007

To import a NiagaraAX schedule or BACnet Schedule or Calendar . . . . . . . . . . . . . . . . . . . . . . . . . 10–26

About Workbench tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1

Types of Workbench Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
Alarm portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Bacnet service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
Color chooser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
Lexicon editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
Lexicon Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11–5
Lexicon Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11–5
Lexicon display options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11–6
Lonworks service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–6
Credentials manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–7
New driver wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–8
New module wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–8
New station wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–9
License request dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–9
Resource estimator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–10
Todo list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–10
Workbench job service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11
Workbench service manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11

Performing Workbench tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1

Starting and exiting Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
To start Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
To close a Workbench window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
To exit Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
Getting started with stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
To open a platform using Workbench GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
To connect to a platform using Workbench GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2
To close a platform using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
To disconnect from a platform using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
To start a station using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
To stop a station using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
To open a station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4
To close a station using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4
To connect to a station using Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4
To disconnect from a station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
Using the side bar pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
To open the side bar pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
To open the bookmarks side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
To open the help side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
To open the nav side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To open the palette side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To close a side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To close the side bar pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To vertically resize a side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To restore a side bar to a previous size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To maximize a side bar: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Using bookmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To add a bookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
To manage bookmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
To edit a bookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
To remove a bookmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7

NiagaraAX-3.x
x
User Guide
May 1, 2007

Using the help side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7

To search for topics in the help side bar: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
Using the nav side bar (tree) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
To refresh a nav side bar tree node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
To Go Into a nav side bar tree node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
Using the jobs side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
To view job details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
To cancel a job from the jobs side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
To dismiss a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
Using the palette side bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
To open a palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
To close a palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
To create a palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–10
To add a new component to a palette (PaletteFile.palette) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–10
To add a new component to a palette (module.palette) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–10
To copy a component to a palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
Using the view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
Editing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
Selecting a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
To select a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
To select multiple components in the nav tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
To select a multiple components in the wire sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
Viewing a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
To select a component view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
To reorder components (in a component container) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
To create a composite view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–13
Working with components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–13
To add a new component (property sheet, nav side bar, or wire sheet view) . . . . . . . . . . . . . . . . . . 12–14
To delete a component (property sheet, nav side bar, or wire sheet view) . . . . . . . . . . . . . . . . . . . . . 12–14
To rename a component (property sheet, nav side bar, or wire sheet view, slot sheet) . . . . . . . . . . 12–14
To duplicate a component (property sheet, nav side bar, or wire sheet view) . . . . . . . . . . . . . . . . . . 12–14
To paste a component (property sheet, nav side bar, or wire sheet view) . . . . . . . . . . . . . . . . . . . . . 12–15
To drag a component to the property sheet, nav side bar, or wire sheet (left–click method) . . . . . 12–15
To drag a component to the property sheet, nav side bar, or wire sheet (right–click method) . . . 12–15
Editing component data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–15
Using the property sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
To add an extension to a component property sheet view: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
To add a component facet: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
To remove a component facet: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
Using the wire sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
To pin a slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17
To paste a component onto the wire sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17
To drag a component to the wire sheet (left–click method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17
To drag a component to the wire sheet (right–click method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17
Using the slot sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
To add a new slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
To delete a slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
Using the link sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
To delete a link using the link sheet view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
To edit a link using the link sheet view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
Using alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
Creating alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
To set up alarm conditions for a control point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
Routing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
To add an alarm class to the alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
To add a console recipient to the alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
To add a station recipient to the alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–20
To add an email recipient to the alarm service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–20
Managing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–20
To acknowledge alarms from the alarm console view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–20
To acknowledge alarms from the alarm portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–21
To delete alarm records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22
Using the Px Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22

NiagaraAX-3.x
xi
User Guide
 May 1, 2007

Making widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22

To make a new widget using the Make New Widget wizard: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22
Binding widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22
To bind a value to a widget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
Editing widget properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
To edit a widget property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
Animating widget properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
To animate a widget property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
Using the Nav File Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
Creating a new Nav file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
To create a new nav file: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
To delete nav file (Delete Key): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
To delete nav file (popup menu): . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
To rename a nav file: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
Editing a Nav file in the Nav File Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25
To open a nav file in the Nav File Editor: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25
To add nodes to a nav file using the Nav File Editor: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25
To delete nodes from a nav file: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25
To edit the node hierarchy (tree structure) in a nav file: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–26
To edit nodes in a nav file: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–26
Working with modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–26
To create a new module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–26

Component Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1

Component Reference Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Components in alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Components in backup module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–4
Components in baja module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–5
Components in bajaui module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–9
Components in chart module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–12
Components in control module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–12
Components in converters module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Components in crypto module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Components in devkit module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Components in driver module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Components in email module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–18
Components in file module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–19
Components in fox module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Components in gx module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Components in help module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Components in history module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Components in kitPx module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
Components in ldap module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–26
Components in net module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–26
Components in niagaraDriver module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–27
Components in program module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–28
Components in pxeditor module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–28
Components in rdb module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29
Components in rdbDb2 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29
Components in rdbOracle module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29

NiagaraAX-3.x
xii
User Guide
May 1, 2007

Components in rdbSqlServer module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29

Components in report module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29
Components in schedule module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
Components in serial module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–31
Components in timesync module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–31
Components in tunnel module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–32
Components in web module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
Components in workbench module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33

Plugin Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14–35

Types of plugin modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–35
Plugins in alarm module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–35
Plugins in backup module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–37
Plugins in chart module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–37
Plugins in devkit module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–38
Plugins in driver module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–39
Plugins in email module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–40
Plugins in help module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–40
Plugins in history module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–41
Plugins in html module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–42
Plugins in ldap module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–46
Plugins in niagaraDriver module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–46
Plugins in program module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–47
Plugins in pxEditor module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–49
Plugins in raster module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–49
Plugins in rdb module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–49
Plugins in report module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–50
Plugins in schedule module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–50
Plugins in timesync module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–51
Plugins in wiresheet module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–51
Plugins in wbutil module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–53
Plugins in workbench module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–54

References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1
In this appendix (introduction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1
About keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1
Types of menu bar items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2
About the File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–2
About the Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–4
About the Search menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–5
About the Bookmarks menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
About the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
About the Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–6
About the Px Editor menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–7
About the History Ext Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–8
About the Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–8

NiagaraAX-3.x
xiii
User Guide
 May 1, 2007

Types of popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–8

About the nav side bar popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–9
About the wire sheet popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–9
About the property sheet popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–10
About the Px Editor popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–10
About the history extension manager popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–11
About the Todo list popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–11
About the point manager popup menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–11
Types of edit commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–12
Types of toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–13
Standard toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–13
Slot Sheet toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–14
Px Editor toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–14
About the history extension manager toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–14
About the history editor toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
About the Todo list toolbar icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
Types of console commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
Niagara shell commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–16
nre (station) commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–16
wb (Workbench) commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–17
plat (platform) commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–17
SVG Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–18

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1

NiagaraAX-3.x
xiv
User Guide
 CONTENTS

Preface
Document Change Log

Document Change Log

Updates (changes/additions) to this NiagaraAX User Guide document are listed below.
• Updated: May 1, 2007
Edited “About Workbench” to add new information throughout to reflect user interface changes that
are the result of NiagaraAX-3.1 and AX-3.2 enhancements.
Edited “Driver architecture” to add sections about NiagaraAX-3.2 virtual points feature, including
“About virtual gateways”, “About virtual component spaces”, and others.
Edited “About Histories” to add coverage of new History charting features (Hx view charting, Time
Zone handling improvements, zoom feature improvements) and other enhancements provided in
NiagaraAX-3.1 and AX-3.2.
Edited “About alarms” to add sections describing NiagaraAX-3.2 feature, Alarm Escalation (“About
alarm escalation”). Added section on Alarm Instructions (“About the Instructions Manager view”).
Added section “About Reporting” in “About Presentation XML (Px)” to describe the Reporting fea-
ture available in NiagaraAX-3.2. Added information regarding enhanced charting capabilities.
Edited “About Security” to add section “Alarm ack permission notes”.
Edited “About Scheduling”—made minor changes, corrections, and updates.
Edited “Performing Workbench tasks” to correct one alarm database maintenance procedure and
make editorial corrections.
Edited “Component Guides” to add component descriptions for VirtualComponent, VirtualGate-
way (new baja components with the NiagaraAX-3.2 virtual points feature). Also added component
descriptions for ComponentGrid, EmailRecipient, ExportSource, ReportPane, ReportService, and
SectionHeader, (components in the NiagaraAX-3.2 report module).
Edited “Plugin Guides” to add coverage of views related to the report component and the alarm In-
structions Manager: GridTable, GridLabelPane, ComponentGridEditor, AlarmExtManager.
• Updated: January 19, 2007
Applied “new look” formatting to print (PDF) version of this document, reducing total page count
yet adding “sidehead” white space to most pages (useful for note taking on printed pages).
Edited “Plugin Guides” chapter to provide more consistent section overviews (useful for navigation
in both html and pdf output) and a content summary of “Types of plugins” at beginning of chapter.
• Revised: August 1, 2006
Various new components and views added in the “Component Guides” and “Plugin Guides” sec-
tions, mostly related to the driver module containing the FileNetwork. Other minor edits and notes
related to NiagaraNetwork provisioning (see “NiagaraStation component notes”).
• Revised: April 4, 2006
Minor typographical fixes only.
• Revised: December 7, 2005
Added new sections in “Field Bus Integrations” section: “Port and protocol variations” on page 5-1
and “Serial tunneling” on page 5-2. Added component descriptions for SerialHelper, TunnelService,
SerialTunnel, and TunnelConnection in “Component Guides”.
Reversed order of this change log to put newest changes at top.
• Revised: October 31, 2005
Removed obsolete references to Raster Editor in “Component Guides”, and “Plugin Guides”.
Added procedures in “Performing Workbench tasks” sections “Using the palette side bar” (to create
and edit palettes) and “Working with modules” (to create a module).

NiagaraAX-3.x
xv
User Guide
 May 1, 2007

Edited section “New module wizard” in the “About Workbench tools” section.
Edited description of property “Time Delay” in the “About alarm extension properties” section to
note this property does not apply to status transitions to (or from) Fault.
• Revised: September 28, 2005
Edited graphics and callouts to standardize resolution, size, & layout in “About NiagaraAX Frame-
work”, “About Workbench”.
Edited links in “Component Guides” and “Glossary”
Added information about the Jobs palette to “About Workbench” and to “References”.
Edited “About the Window menu” and “About the locator bar”sections.
Added section “About the point manager popup menu items”.
• Revised: September 15, 2005
Edited and corrected broken links to online help, including links in “About Workbench tools”,
“About Security”, and “Component Guides”.
• Revised: August 31, 2005
Edited, added content, and renamed sections in “About Workbench tools”.
Added “Batch editing (or batch processing)” section.
Added “About the Todo list popup menu items” section to “Types of popup menu items”.
Added “About the Todo list toolbar icons” section to “Types of toolbar icons”.
• Revised: August 23, 2005
Added “Types of files” section to the “About ORDs” section.
Edited and added content to “About Workbench tools” section.
Added new procedures to “Using the palette side bar” section.
Added content to sections in the “Customizing the Workbench environment” section.
• Revised: August 17, 2005
Added new sections to “Customizing the Workbench environment”.
Edited and added sections to “About Workbench tools”.
• Revised: August 3, 2005
Added new sections: “About schemes”, “Types of schemes”, “Table controls and options”, “Chart
controls and options”, “About the History Ext Manager menu”, “About the history extension manag-
er popup menu items”, “About the history extension manager toolbar icons”, “Niagara shell com-
mands”, “nre (station) commands”, “wb (Workbench) commands”, “plat (platform) commands”.
Edited sections “About alarms” and “About Histories” to replace redundant text with references to
single description location. Added or corrected missing or incorrect property descriptions. Edited
“Plugin Guides”, “Component Guides”, “References” to augment references, correct missing or in-
accurate descriptions and update links.
• Revised: July 13, 2005
Added section “About delta logging” and edited section “Add history extensions to a component”.
• Published: June 24 2005
Added Copyright and Trademarks section to preface. Made minor changes in the “Component
Guides” and “Plugin Guides” sections, especially for the BackupService and BackupManager.
• Draft: June 15 2005
Added components to and edited some components in the following sections: “Components in kitPx
module”.
• Draft: June 8 2005
Added components to and edited some components in the following sections: “Components in
alarm module”, “Components in baja module”, “Components in bajaui module”, “Components in
history module”.
• Draft: June 6 2005
Provided more details about using the alarm class mapper in “About alarm class mapping”. Updated
alarm console and alarm portal screens in “Types of Workbench options” section. Added, removed
and updated information in the “Components in alarm module” section.
• Draft: June 1 2005
“Data and Control Model” section had various minor changes after a technical review, including
many updated screen captures. The section “Types of status flags” on page 3-15 shows default status
colors, in addition to describing them.
“Types of alarm service views” section edited to add property sheet view–in order to include descrip-
tion of “capacity” property. “About alarm class mapping” section added. Updated “About the alarm
database maintenance view” section updated to reflect new database editing option. Corrected de-
scription of “capacity in “About the history summary view” section.
• Draft: May 25, 2005 (Initial change log)
“Data and Control Model” section “About point actions” on page 3-3 was expanded to cover the re-
cent “set” (Fallback) action for writable points, including new sections “About override actions”,

NiagaraAX-3.x
xvi
User Guide
Chapter 3 –
May 1, 2007

“About set (Fallback) action”, and “Modifying default actions”. Various minor changes were also
made in other Data and Control Model sections.
“About alarms” section was reorganized and updated. Additional information added in the following
sections: About alarm extension properties, About alarm extension manager, About the alarm data-
base maintenance view, About the lineprinter recipient. The About memory alarm service section
was added. Various minor changes were also made in other About alarms sections.

NiagaraAX-3.x
3-xvii
User Guide
 Chapter 3 –
May 1, 2007

NiagaraAX-3.x
3-xviii
User Guide
 CHAPTER 1
About NiagaraAX Framework
Software frameworks provide a platform to allow businesses to more easily build their end-product
offerings. Tridium’s patented Niagara Framework® is targeted at solving the challenges associated with
managing diverse smart devices, unifying their data, and connecting them to enterprise applications.
Examples of smart devices include: monitoring and control systems, sensors, metering systems, and
embedded controls on packaged equipment systems.
framework, n. something composed of parts fitted together and united; a structural frame; a basic
structure (as of ideas); in object-oriented programming, a reusable basic design structure, consisting of
abstract and concrete classes, that assists in building applications.
Niagara Framework, n. a universal software infrastructure that allows companies to build custom, web-
enabled applications for accessing, automating, and controlling smart devices in real time over the
Internet.
NiagaraAX is the third generation of Tridium's Niagara Framework. This Java–based software
framework provides an infrastructure to enable systems integrators and developers to build device–to–
enterprise solutions, and Internet–enabled control and monitoring products. The Framework integrates
diverse systems and devices (regardless of manufacturer or communication protocol) into a unified
platform that can be easily managed in real time over the Internet (or intranet) using a standard web
browser. The Framework also includes a comprehensive toolset that enables non-programmers to build
rich applications in a drag-and-drop environment.
NiagaraAX is fully scalable, meaning that it can be run on platforms spanning the range from small,
embedded devices to enterprise class servers. Niagara is being successfully applied in energy–services,
building–automation, industrial–automation and M2M applications today.

Well designed
The Niagara Framework addresses the challenges of automation, control and device to enterprise
connectivity of real time systems. NiagaraAX, and its derivative products, offer compelling value to both
end users and partners. For OEM and reseller partners, the Niagara Framework solves several key
challenges present in all control-related industries:
• High development costs associated with the foundation or infrastructure layer of software that com-
municates with devices and manipulates the data from them.
• The need to transform information from real-time control processes into a homogeneous structure
enabling advanced product and service applications.
• Integration of legacy systems to enable companies to easily migrate their existing customers to new
technologies and product offerings.
Partners who adopt the Niagara Framework as their infrastructure eliminate substantial engineering
effort and are able to focus on their core competencies of application development and marketing. These
companies gain competitive advantage in their markets from lower development costs and quicker time-
to-market for their specific products, applications and value-add services.
End users of Niagara benefit from:
• Being able to preserve existing investments in control and monitoring devices as they move to new,
standards-based technologies.
• Being able to access and control all of their diverse systems through a standard web browser.
• Combining information from different systems to support better overall management of their enter-
prise assets.
• Being able to specify interoperable systems and applications from multiple vendors, thereby reduc-

NiagaraAX-3.x
1–1
User Guide
The Niagara Framework solution Chapter 1 – About NiagaraAX Framework
About control systems integration May 1, 2007

ing the potential for vendor lock-in.

Niagara is designed to address the following specific technical challenges:
• Platform independence - NiagaraAX works with a wide variety of operating systems and hardware
platforms.
Unification of diverse systems - NiagaraAX integrates heterogeneous systems, protocols, and field-
buses into normalized components.
Distributed architecture - NiagaraAX supports a highly distributed architecture. It successfully
combines Internet/IT technology with the services necessary to implement real-time, peer-to-peer
automation applications.
• Programming for non-programmers - NiagaraAX provides an environment and comprehensive
toolset to enable domain experts to create sophisticated applications without writing code.
• Extensibility - NiagaraAX provides an extensible component model and rich library of open APIs to
enable programmers to extend and enhance the Framework and build their own unique applications
and products
• Support for embedded systems - NiagaraAX can be embedded in small low cost devices

The Niagara Framework solution

The following section describes how the Niagara framework addresses these challenges:
• About control systems integration
• About Java
• About common networking and Internet protocols
• About programming for non-programmers
• About embedded systems capabilities
• About distributed systems capabilities
• About component software design

About control systems integration

Using the Niagara Framework, control systems integration means:
1. connecting devices on a common communications media
2. modeling those devices in software
3. programming applications to use the information in those devices
Before a device, such as a chiller, VAV box, or temperature sensor, can be used, information from those
devices must be pulled into the Niagara software.
Niagara then models those devices and their data types in software through the common object model.
This usually entails simplifying the device’s data types to make them easier to manipulate and control
through the software.
The Niagara common object model is then used to build applications, with the goal being to provide non-
programmers a means to program the system easily without developing raw code. The Niagara common
object model is similar to a programming language in that there are a few key concepts that are used, but
the real power is in the reusable libraries of applications and collections of objects that are available. Once
you understand the key concepts and you can put them to work, you can use Niagara objects to build
control system solutions quickly and efficiently.
The Niagara common object model, shown in Figure 1-1, allows the Niagara Framework to:
• provide two-way communication between devices and the Internet
• send real-time device information across the Internet
• control devices in real-time across the Internet.

NiagaraAX-3.x
1-2
User Guide
Chapter 1 – About NiagaraAX Framework The Niagara Framework solution
May 1, 2007 About Java

Figure 1-1 Niagara common object model

About Java
All of the Niagara software is written in Java, which means that it is platform independent. Prior to Java,
most software was written and compiled for a particular machine or operating system. If that software
needs to run on some other processor, the program has to be compiled again. Java, on the other hand,
compiles once. NiagaraAX software runs on embedded JACE controllers using the QNX operating
system and the IBM J9 Java Virtual Machine (JVM), and runs on Microsoft Windows desktop operating
system platforms, as well as Linux and Solaris using the HotSpot JVM.
About Virtual Machines
It is possible to compile code once and run it on any platform due to a layer of software that exists between
the machine and the software called the Java virtual machine (JVM). The Niagara framework uses the Java
VM as a common runtime environment across various operating systems and hardware platforms. The
core framework scales from small embedded controllers to high end servers. The framework runtime is
targeted for J2ME compliant VMs. The user interface toolkit and graphical programming tools are
targeted for J2SE 1.4 VMs.
There are a number of different virtual machines for different platforms on which the NRE is running,
but the NRE itself, and all of its modules, are the same regardless of platform. The VM is responsible for
defining how the software works with a given set of hardware-how it talks to a lonWorks adapter, how it
talks to the communications port, how it interacts with the operating system, among other tasks.

About common networking and Internet protocols

Niagara is designed from the ground up to assume that there will never be any one “standard” network
protocol, distributed architecture, or fieldbus. Niagara's design goal is to integrate cleanly with all
networks and protocols. The Niagara Framework standardizes what's inside the box, not what the box
talks to.
The Niagara software suite implements a highly efficient adaptation of the JavaBean component software
model and Internet technologies to provide true interoperability across a wide range of automation
products. The Niagara object model can be used to integrate a wide range of physical devices, controllers,
and primitive control applications including lonMark profiles, BACnet objects, and legacy control points.
The architecture supports future enhancements by allowing legacy systems to be brought forward, where
they can readily adopt new standards, solutions, and applications.
Enterprise-level software standards include Transmission Control Protocol/Internet Protocol (TCP/IP),
eXtensible Markup Language (XML), Hyper Text Transfer Protocol (HTTP), and others. These
standards provide the foundation on which to build solutions that allow information to be shared
between the control system and the enterprise information system.

About programming for non-programmers

Most features in the Niagara Framework are designed for dual use (for programmers as well as non-
programmers). These features are designed around a set of Java APIs to be accessed by developers writing
Java code. At the same time, most features are also designed to be used through high level graphical
programming and configuration tools. This vastly increases the number of users capable of building
applications on the Niagara platform.

NiagaraAX-3.x
1-3
User Guide
The Niagara Framework solution Chapter 1 – About NiagaraAX Framework
About embedded systems capabilities May 1, 2007

About embedded systems capabilities

NiagaraAX is one of the only software stacks designed to run across the entire range of processors from
small embedded devices to server class machines. Niagara is targeted for embedded systems capable of
running a Java VM. This excludes some very low-end devices that lack 32-bit processors or have only
several megabytes of RAM, but opens up a wide range of processor platforms.
To speed time to market for partners designing smart devices, Tridium has developed a reference design
processor core. Known as the Niagara Processor Module (NPM), this platform can be licensed from
Tridium and makes it possible to quickly develop NiagaraAX-based products.

About distributed systems capabilities

The framework is designed to provide scalability to highly distributed systems composed of tens of
thousands of nodes running the Niagara Framework software. Systems of this size span a wide range of
network topologies and usually communicate over unreliable Internet connections. Niagara is designed
to provide an infrastructure for managing systems of this scale.

About component software design

Niagara uses an architecture centered around the concept of “Component Oriented Development.” A
component is a piece of self-describing software that can be assembled like building blocks to create new
applications. A component–centric architecture solves many problems in Niagara:
• Data normalization
Components provide a model used to normalize the data and features of different types of protocols
and networks so that they can be integrated seamlessly.
• Graphic development tools
Applications can be assembled with components using graphical tools in the Niagara Workbench.
This allows new applications to be built without requiring a Java developer.
• Application visibility
Components provide unsurpassed visibility into applications. Since components are self-describing,
it is very easy for tools to look at how an application is assembled, configured, and to determine what
is occurring at any point in time. This provides great value in debugging and maintaining Niagara
applications.
• Software reuse
Components enable software reuse. NiagaraAX supports custom development and extension of the
framework. Niagara components are extensible and go beyond data and protocols to unify the entire
development environment.

About Niagara software architecture

There are four layers to the Niagara software architecture. The bottom layer, as shown in Figure 1-2 is the
host platform, either a JACE controller or a PC. The next layer is the Java virtual machine (JVM). The
JVM provides a layer between the hardware and its operating system and the Niagara software, known as
the Niagara run-time environment (NRE). On top of the NRE are the Niagara modules.

Figure 1-2 NiagaraAX software architecture

NiagaraAX software subsystems are illustrated in Figure 1-3 and the software processes and protocols are
shown in Figure 1-4.

NiagaraAX-3.x
1-4
User Guide
Chapter 1 – About NiagaraAX Framework About Baja
May 1, 2007 About Niagara software architecture

Figure 1-3 NiagaraAX major software subsystems

Figure 1-4 NiagaraAX software processes and protocols

About Baja
The core framework built by Tridium is designed to be published as an open standard. This standard is
being developed through Sun's Java Community Process as JSR 60. This JSR is still an ongoing effort, but
it is important to understand the distinction between Baja and Niagara.
Fundamentally Baja is an open specification and the Niagara Framework is an implementation of that
specification. As a specification, Baja is not a set of software, but rather purely a set of documentation.
The Baja specification will include:
• Standards for how Baja software modules are packaged
• XML schema for the component model;
• The component model and its APIs
• Historical database components and APIs
• Alarming components and APIs
• Control logic components and APIs
• Scheduling components and APIs
• BACnet driver components and APIs
• lonWorks driver components and APIs
Over time many more specifications for features will be added to Baja. But what is important to
remember is that Baja is only a specification. Niagara is an implementation of that specification.
Furthermore you will find a vast number of features in Niagara, that are not included under the Baja
umbrella. In this respect Niagara provides a superset of the Baja features.

NiagaraAX-3.x
1-5
User Guide
About Niagara building blocks Chapter 1 – About NiagaraAX Framework
About APIs May 1, 2007

About APIs
The API (Application Programming Interface) defines how software engineers access the capabilities of
software like the Niagara Framework. Workbench is the Niagara API — and using the Niagara
Workbench, you can create and edit the control logic for your job site.
Many features found in Niagara are exposed through a set of Java APIs. In the Java world, APIs are
grouped together into packages, which are scoped using DNS domain names. Software developed
through the Java Community Process is usually scoped by packages starting with “java” or “javax.” It is
important to understand the two types of APIs related to the Niagara framework:
• javax.baja
• com.tridium
javax.baja
The APIs developed for Baja (see “About Baja” on page 1-5 for more about Baja) are all grouped under
javax.baja. These are APIs that will be part of the open Baja specification and may be implemented by
vendors other than Tridium. Using these APIs guarantees a measure of vendor neutrality and backward
compatibility.
com.tridium
Software developed by Tridium which is proprietary and outside of the Baja specification is grouped
under the com.tridium packages. The com.tridium packages contain code specific to how Niagara imple-
ments the Baja APIs. The com.tridium code may or may not be documented. If com.tridium APIs are
publicly documented then Tridium encourages developers to use them, but does not guarantee backward
compatibility. Undocumented com.tridium APIs should never be used by developers.
Note: Tridium has developed some APIs under javax.baja even though they are not currently part of the Baja
specification. These are APIs that Tridium feels may eventually be published through Baja, but are
currently in a development stage.

About Niagara building blocks

This section describes some of the fundamental building blocks of the Niagara framework. It is important
to understand these concepts and associated terminology in order to fully benefit from the use of the
NiagaraAX Workbench. Concepts discussed in this section include the following:
• Modules
Modules are the most basic unit of software in NiagaraAX. For more details about modules, see
“About modules” on page 1-6.
• Components
Components are the primary building blocks of the NiagaraAX framework. For more details about
components, see “About components” on page 1-9.
• px
For more details about px., see “About presentation xml (px)” on page 1-13.
• stations
For more details about stations., see “About stations” on page 1-15.
• ORDs
For more details about ORDs, see “About ORDs” on page 1-16.
• Views
For more details about views, see “About views” on page 1-19.

About modules
Modules are the smallest units of software in the Niagara architecture.
Major releases of the Niagara software are distributed along with a set of release modules, but as new
modules are made available for that release of Niagara, they may be distributed as independent revisions
within that release.
Figure 1-5 shows a partial list of modules, as displayed in the nav side bar pane.

NiagaraAX-3.x
1-6
User Guide
Chapter 1 – About NiagaraAX Framework About modules
May 1, 2007 About module characteristics

Figure 1-5 Module listing in the nav side bar tree

Note: Don’t confuse modules with components. Components are used to build Niagara implementations, while
modules make up the Niagara software itself. Refer to “About components” on page 1-9 for more infor-
mation about components.
The following sections describe module characteristics and benefits.

About module characteristics

All modules:
• are composed of a single Java ARchive (JAR) file compliant with PKZIP compression
• contain an XML manifest
• are independently versioned and deployable
• state their dependencies on other modules and their versions
About jar files
JAR files are the standard mechanism for distributing Java modules. JAR stands for “Java archive.” A JAR
file (.jar) is basically a compressed package whose components can be viewed with WinZip or other
archive viewing tool. Do not attempt to unzip a JAR file—it will not work. JAR files are the add-ins that
are plugged into the software to give additional functionality. Inside the JAR file are the compressed
software; its documentation; in some cases, examples or pre-canned applications; and libraries.
Some modules, such as the lonWorks module, are distributed as multiple JAR files because there are so
many different lonWorks devices. The core protocol is packaged in a JAR file called lonWorks.jar. There
are individual JAR files for each LON device manufacturer (for example, lon_mfgName.jar). Every JAR
file or module is versioned independently.
About module versions
Niagara’s versioning system allows you to check to make sure that you have the latest available module
for your system. Versions are specified as a series of whole numbers separated by a period, for example
"1.0.42". To understand which version of a module is more recent, simply observe the module version
number. For example, 2.3.42 is later than 2.3.35 because 2.3.42 > 2.3.35.
Figure 1-6 shows modules listed, by name, with the version number and file name, as viewed in the
Workbench software manager.

Figure 1-6 Module descriptions viewed in the software manager

Niagara versioning uses the following set of conventions:

• Versions are specified using a base four-part version with optional patch versions.
• The first number specifies the specification revision. This number starts at one and is incremented
each time the specification of the module is incremented. It is used with Baja modules to track the
Baja specification version.
• The next two numbers specify a major Niagara release.
• The fourth number specifies a build number. A build number starts at zero for each major release
and increments each time all the software’s modules are built.
• Additional numbers may be specified for code changes made off a branch of a specific build. These
are usually minor changes and bug fixes.

NiagaraAX-3.x
1-7
User Guide
About modules Chapter 1 – About NiagaraAX Framework
About module benefits May 1, 2007

Every module has two versions. The first is the "bajaVersion" which maps the module to a Baja specifi-
cation version. If the module is not published under the Baja process then this value is "0". Secondly every
module declares a "vendor" name and "vendorVersion". The vendor name is a case insensitive identifier
for the company who developed the module and the vendorVersion identifies the vendor's specific
version of that module.
Tridium's vendorVersions are formatted as "major.minor.build[.patch]:
• Major and minor declare a feature release such as 3.0.
• The third number specifies a build number. A build number starts at zero for each feature release
and increments each time all the software modules are built.
• Addition numbers may be specified for code changes made off a branch of a specific build. These are
usually patch builds for minor changes and bug fixes.
So the vendorVersion "3.0.22" represents a module of build 22 in Niagara release 3.0. The vendorVersion
"3.0.45.2" is the second patch of build 45 in release 3.0.
About module directory structure
Every module is managed in its own directory structure. Figure 1-7 shows an example of a directory for
the alarm module.

Figure 1-7 Module directory structure

All of the source code that is used to build the module’s jar file is located under the "src" directory. During
the build process the "libJar" directory is used to build up the image, which will be zipped up for the
module's jar file.

About module benefits

Modular software development provides several benefits, including the following:
• Improves tracking deployment and versioning
Modular development assists in tracking the deployment and versioning of Niagara features and re-
leases. For example, if a new driver is available to be added to NiagaraAX Framework, it can be pack-
aged, delivered, and added in as a single module or with multiple modules, using the NiagaraAX
software manager, as shown in Figure 1-8. Refer to the Platform Guide section “Software Manager”
for more information about managing modules.

NiagaraAX-3.x
1-8
User Guide
Chapter 1 – About NiagaraAX Framework About components
May 1, 2007 About module benefits

Figure 1-8 Software manager view

• Requires less space on JACE

Niagara’s modular development allows you to save space on your JACE by only installing the mod-
ules that you need and choose for that JACE.
• Requires less space on the workstation
When you install NiagaraAX, you can choose the modules that you want to install with your appli-
cation and omit any modules that you do not need. Later, if want to add additional modules you can
do so with the Software Manager (as shown in Figure 1-8).
• Create new modules
Software developers can use the tools in NiagaraAX to create new modules and deploy them using
the New Module Wizard, as shown in Figure 1-9.
Refer to “New module wizard” on page 11-8 for more details about the New Module Wizard.

Figure 1-9 New module wizard

About components
A component is the primary building block that you use to engineer an application using NiagaraAX
Workbench. As described in the “About component software design” on page 1-4, components provide
many advantages for the application developer.
Components differ from modules in that components compose a Niagara implementation whereas
modules compose the Niagara software itself.
The following sections describe characteristics of components:
• About slots
• About master/slave components
• About point components

NiagaraAX-3.x
1-9
User Guide
About components Chapter 1 – About NiagaraAX Framework
About slots May 1, 2007

About slots
Niagara components are defined as a collection of “slots.” You can see all the slots that make up a
component by viewing the “slot sheet” as shown in Figure 1-10. Slots have the following types of
attributes:
• Slot type
• Slot name
• Slot definition
• Flags
• Facets

Figure 1-10 Slot sheet for a single component

Slot type
There are three types of slots:
• Property
Property slots represent a storage location of another Niagara object.
• Action
An action is a slot that specifies behavior that may be invoked either through a user command or by
an event. Actions provide the capability to provide direction to components. They may be issued
manually by the operator or automatically through links. Actions can be issued by right–clicking on
the component.
• Topic
Topics represent the subject of an event. Topics contain neither a storage location, nor a behavior.
Rather a topic serves as a place holder for a event source.
Slot name
Every slot is identified by a name that is unique within its Type. Slot names must contain ASCII letters or
numbers.
Slot definition
Slots are either frozen or dynamic. A frozen slot is defined at compile time within a Type's Java class. That
means that frozen slots are consistent across all instances of a specified Type – they don’t change.
Dynamic slots may be added, removed, renamed, and reordered during runtime – they can change. The
power of the Niagara Framework is in providing a consistent model for both frozen (compile time) slots
and dynamic (runtime) slots.
Flags
Slots have flags that allow modification of an object’s presentation or behavior. For example, “read–only”,
“operator allowed”, and “hidden”, are some of the slot flags that may be used to restrict the presentation
or behavior of an object.
Facets
Facets contain meta data – or additional data about an object. For example, “units of measurement” is a
type of facet. Facets may be viewed in the slot sheet and edited from a component property sheet, as
shown in Figure 1-11.

NiagaraAX-3.x
1-10
User Guide
Chapter 1 – About NiagaraAX Framework About components
May 1, 2007 About master/slave components

Figure 1-11 Editing facets from the property sheet

About master/slave components

Master components can be defined so that persistent properties are copied to slave components when
they are changed. This allows you to change a property in one component that automatically updates the
components that are linked to it as slaves. In this way a master component can update slave components
in all the other stations in a system.

About point components

In any NiagaraAX station, all real-time data is normalized within the station database as points, a special
group of components. Figure 1-12 shows several types of control points, as listed in the control module
palette in Workbench.

Figure 1-12 Point types

Each type of point may be used for different purposes in Workbench. When you engineer a job you may
want to name a point, as shown in Figure 1-13 (a NumericWritable point named CondSetpoint). Points
may be named and renamed but they retain their initial point type characteristics and their characteristic
icon color.

Figure 1-13 Numeric writable point named

Points serve as a type of shell in NiagaraAX, to which you may add point extensions. These extensions
allow you to select only those functions that you need and thereby limit your point properties to just those
that are necessary for your current application.

NiagaraAX-3.x
1-11
User Guide
About components Chapter 1 – About NiagaraAX Framework
About component naming May 1, 2007

Figure 1-14 Adding point extensions

For detailed information about points and point extensions, refer to “Data and Control Model” on page
3-1.

About component naming

In a NiagaraAX station, components should be properly named using the following set of rules:
• Only alphanumeric (A-Z, a-z, 0-9) and underscore (_) characters are used—spaces, hyphens, or oth-
er symbols characters (e.g: %, &, ., #, and so on) are illegal in component names. For further details,
see the next section “Escaped names”.
• The first character in the name must be a letter (not a numeral).
• Name must be unique for every component within the same parent component. Workbench auto-
matically enforces this rule, via a popup error dialog.
• Naming is case-sensitive—for example, zone21 and Zone21 are unique names.
Note: Case differences among names affect “name sorts” in table-based views, which order by ASCII
code sequence, that is capital letters (A-Z) first, lower case (a-z) following.
To convey multiple-word names without using spaces, naming “conventions” such as “CamelCase” and/
or underscores are often used, as needed. Examples of such component names are:
• Floor1 or Floor_1
• ReturnAirTemp or Return_Air_Temp
• Zone201_SAT or Zone_201_SAT

Escaped names
Workbench does allow you to name components “improperly,” such as with spaces or other non-alpha-
numeric characters, without any warning. Further, various NiagaraAX drivers have “learn” features to
automate the creation of points, some of which (by default) may also have such “improper” names—
reflective of the “native name” of the source object. For example, a BACnet proxy point might have the
default name “Zone 6 RH%” that matches the actual (native) BACnet object’s name.
In any case, be aware that the “actual” component name has all illegal characters “escaped” using a “$”
character, along with the ASCII code for that character, in hexadecimal. The proxy point mentioned
above, for example, will have the name “Zone$206RH$25”, where the $20 escapes the space and the $25
escapes the %. You can see these escaped names in the slot sheet of the component’s parent container. Or,
with the component selected, look at its ord (shortcut Ctrl + L) to see its actual name.
For the most part, this “escaped name” scheme is transparent to users. Whenever the name is displayed
to the user, say in the Nav side bar, property sheet, wire sheet, or a point manger, the component’s name
is “unescaped” by replacing the code (say, $20) with the actual ASCII character (say, a space). This way,
the user sees “Zone 6 RH%” and so on. This is the component’s “display name.”
In some cases, escaped names lead to confusion. You should avoid them if possible (rename using rules—
see “About component naming”). For example, if you add history extensions to escaped-named points,
you see those escape codes listed for source points when accessing the History Ext Manager (although
associated histories use the display names). Or, if you are building Px pages and manually typing in ords
in Px widgets, you probably know source points by “display names” only. If you manually type in an ord
without the actual (escaped) name, the widget binding fails with an error.
Note: If this sounds too complicated, remember that “drag and drop” operations resolve escaped names without
problems—for example, drag any point onto a Px page to get its proper ord.

NiagaraAX-3.x
1-12
User Guide
Chapter 1 – About NiagaraAX Framework About presentation
May 1, 2007 About palettes

About palettes
The palette provides a hierarchical view of available components. You may copy a component from the
palette and paste it where you need it — on a wire sheet, property sheet, Px View, or in the palette nav
side bar pane. For more information about using the palette side bar, refer to “About the palette side bar”
on page 2-7.

About presentation
The NiagaraAX framework provides a powerful presentation architecture based on XML and the Niagara
component model.
Presentation is a term that is used to describe how Niagara provides visualization of information across
different types of media. The terms information, visualization, and media may comprise the following:
• information
• real–time data
• historical data
• configuration data
• alarm data
• scheduling data
• graphical data
• textual data
• visualization
• bitmap and vector graphics
• text documents
• tables
• charts
• input controls (text fields, check boxes, trees)
• media
• desktop web browsers (HTML, CSS, JavaScript)
• workbench (Niagara stack)
• pdf
• printed pages
• svg
• handhelds
• cell phones

About presentation modules

Niagara’s presentation architecture is based on many modules and their associated public APIs:
• baja
The baja module defines the core component model upon which Niagara subsystems are built. This
document describes enhancements to the baja component model which will be used by the presen-
tation stack.
• gx
The gx module provides an API for drawing 2D graphics to a device. The gx module deals with draw-
ing primitives: color, strokes, gradients, vector geometries (line, rectangle, ellipse, paths), bitmap im-
ages, fonts, and transforms.
• bajaui
The bajaui module provides the widget toolkit. Widgets are the basis for graphical composition, lay-
out, user input, and data binding. The bajaui module builds upon gx to paint the widgets.
• PDF
The PDF implementation of the gx APIs.
• HTML
The HTML rendering and data binding engine.

About presentation xml (px)

An XML file format is used to define a Niagara presentation. This file format is called “px” for presen-
tation XML and the term “px” is commonly used to describe the Niagara presentation architecture.
Presentation is a term that describes how Niagara visualizes information (text, graphics, alarms, and so
on) across heterogeneous media – such as: Workbench, desktop browsers, handheld devices, and so on.
Niagara uses “presentation xml” (px) to accomplish this. Figure 1-15 shows an example of a Px file in the
Text Editor (px source file), the Px Editor view, and as displayed in the Px Viewer.

NiagaraAX-3.x
1-13
User Guide
About presentation Chapter 1 – About NiagaraAX Framework
About presentation design philosophy May 1, 2007

Figure 1-15 Px file in Text Editor, Px Editor, and Px Viewer

About presentation design philosophy

The presentation architecture is based on the following design principles:
• Component model
The core philosophy of every subsystem in Niagara is to build atop the component model. The pre-
sentation architecture is no exception. The design embraces a pure component model solution. The
component model is used for the normalized representation of presentation - the “document object
model” (DOM) of a Niagara presentation is always a BComponent tree.
• Unified visualization
Presentations include a unified approach to representing graphics, text, and input controls all within
a single component model. This allows all visualizations to share a common file format as well as a
rendering, layout, and input API.
• Unified media
The design goal of px is to build a single presentation that can be used across multiple media. For
example, given a px file, it can be automatically rendered using the workbench, as an HTML web
page, or as a PDF file. All presentations are stored in the normalized component model as px files.

About presentation media

There are four primary target medias that NiagaraAX supports.
• Workbench
The Niagara stack must be available to take full advantage of the presentation architecture. The
desktop version of Workbench provides a stand alone application that can render Niagara presenta-
tions with their full power. With the WbProfile feature, new custom applications can easily be built
using Workbench framework and its presentation engine.
• Workbench applet
Workbench applet allows the full Niagara stack to be downloaded to a client machine using a web
browser with the Java plug–in. Once loaded to the client, Workbench may be run as an applet within
an HTML page. In this scenario, the presentation engine will be available with the full feature set.
The WbProfile feature may be used to customize how Workbench is decorated inside the HTML
page.
• PDF
Adobe's PDF format is the standard way to export a presentation to be printed to paper. PDF pro-
vides explicit control for how a presentation is rendered on paper in various sizes. It is also a conve-
nient file format for access via HTTP or email. The presentation architecture includes an engine for
generating PDF files from px files.
• HTML
For the casual user where installing the Java plug–in or downloading Workbench is impractical, Nia-
gara supports an engine for generating plain HTML pages from Px. A simple set of HTML, CSS, and

NiagaraAX-3.x
1-14
User Guide
Chapter 1 – About NiagaraAX Framework About stations
May 1, 2007 About presentation media

JavaScript provide a web interface using common standards. This interface may also be used to sup-
port handheld devices and cell phones. Designers are limited to a subset of widgets when creating
HTML presentations (the Px tools provide this support).
Refer to “About Px target media” on page 8-17 for information about presentation media technologies.

Figure 1-16 Presentation media options

About stations
A station is the main unit of server processing in the Niagara architecture.
• A station database is defined by a single .bog file, for example:
"file:!stations/{name}/config.bog"
• Stations are booted from their config.bog file into a single Virtual Machine (VM), or process, on
the host machine.
• There is usually a one–to–one correspondence between stations and host machines (Supervisors or
Jaces). However it is possible to run two stations on the same machine if they are configured to use
different IP ports
A station runs the components of the Niagara Framework and provides the access for client browsers to
view and control these components. The primary parts of a station include components and services. It
is the combination of a database, a web server, and a control engine. The station either runs on a Web
Supervisor PC or a JACE controller.

Figure 1-17 Station in nav tree

A system can be a single station or multiple stations depending on the size of the project and it is defined
by a bog file.

NiagaraAX-3.x
1-15
User Guide
About ORDs Chapter 1 – About NiagaraAX Framework
About BOG files May 1, 2007

About BOG files

A bog file (baja object graph) contains Niagara components. It can be a complete database or any
collection of components. A bog file is a special file that describes the components in a database. All
views can be used on components in a bog file just as if they were in a station.

Figure 1-18 Sample bog file and nav tree presentation

About ORDs
An ORD is an "Object Resolution Descriptor". The ORD is the Niagara universal identification system
and is used throughout the Niagara framework. The ORD unifies and standardizes access to all infor-
mation. It is designed to combine different naming systems into a single string and has the advantage of
being parsable by a host of public APIs.
An ORD is comprised of one or more queries where each query has a scheme that identifies how to parse
and resolve to an object. ORDs may be displayed visually, as with the Open Ord locator or they may be
entered in a text field, as shown in the Open ORD dialog box (see Figure 1-19).

Figure 1-19 Open ORD and graphic locator system

ORDs can be relative or absolute. An absolute ORD usually takes the general format of
“host|session|space”, as illustrated in Figure 1-20.

Figure 1-20 Absolute ORD typical structure

• host
The host query identifies a machine – usually by an IP address such as "ip:hostname". For example
"fox:" indicates a fox session to the host.
• session
The session is used to identify a protocol being used to communicate with the host.
• space
The space query is used to identify a particular type of object. Common spaces are "module:", "file:",
"station:", "view:", “spy:”, or "history:".

NiagaraAX-3.x
1-16
User Guide
Chapter 1 – About NiagaraAX Framework About ORDs
May 1, 2007 About schemes

The local VM is a special case identified by "local:" which always resolves to BLocalHost.INSTANCE. The
local host is both a host and a session (since no communication protocols are required for access).
Both a slot path and a handle scheme can name components within a ComponentSpace. So the ORD for
a component usually involves both a space query and a path/handle.
Examples of ORDs:
• ip:somehost|fox:|station:|slot:/MyService
• ip:somehost|fox:|station:|h:/42
• ip:somehost|fox:|file:/C:/dir/file.txt
• local:|file:!lib/log.properties
• local:|module://icons/x16/cloud.png
• local:|spy:/
In Niagara you may view the complete list of installed ORD schemes at "spy:/sysManagers/registry-
Manager/ordSchemes" (“local:|fox:|spy:/sysManagers/registryManager/ordSchemes”).

About schemes
An ORD is a list of one or more queries separated by the "|" pipe symbol. Each query is an ASCII string
formatted as "<scheme>:<body>".

Figure 1-21 Example ORD scheme and body

• scheme
The scheme name is a globally unique identifier which specifies, in Niagara, how to find a piece of
code to lookup an object from the body string. Refer to “Types of schemes” for a listing of different
types of schemes.
• body
The body string is formatted differently, according to the requirements of the scheme. The only rule
is that it cannot contain a pipe symbol. Queries can be piped together to let each scheme focus on
how to lookup a specific type of object. In general, absolute ords are in the following format: host |
session | space (see Figure 1-20).
Some examples follow:
• ip:somehost|fox:|file:/dir/somefile.txt
In this example, the "ip" scheme is used to identify a host machine. The "fox" scheme specifies
a session to that machine usually on a specific IP port number. Finally, the “file” scheme iden-
tifies an instance of a file within the “somehost” file system.
• ip:somehost|fox:1912|station:|slot:/Graphics/Home
In this example, the "ip" scheme is used to identify a host machine using an IP address. The "fox"
scheme specifies a session to that machine usually on a specific IP port number. Finally, the “sta-
tion” and “slot” schemes identify a specific component in the station database.
• local:|module://icons/x16/cut.png
This example illustrates a special case. The scheme "local" which always resolves to BLocal-
Host.INSTANCE is both a host scheme and a session scheme. It represents objects found with-
in the local VM.

Types of schemes
• ip:
The "ip" scheme is used to identify an Ip Host instance. Ords starting with "ip" are always absolute
and ignore any base that may be specified. The body of a "ip" query is a DNS hostname or an IP ad-
dress of the format "dd.dd.dd.dd".
• fox:
The "fox" scheme is used to establish a Fox session. Fox is the primary protocol used by Niagara for
IP communication. A "fox" query is formatted as "fox:" or "fox:<port>". If port is unspecified then the
default 1911 port is assumed.
• file:
The "file" scheme is used to identify files on the file system. All file ords resolve to instances of jav-
ax.baja.file.BIFile. File queries always parse into a FilePath. File ords include the following examples:
• Authority Absolute: "//hostname/dir1/dir2"
• Local Absolute: "/dir1/dir2"
• Sys Absolute: "!lib/system.properties"

NiagaraAX-3.x
1-17
User Guide
About ORDs Chapter 1 – About NiagaraAX Framework
Types of space May 1, 2007

Sys absolute paths indicate files rooted under the Niagara installation directory identified via
Sys.getBajaHome().
• User Absolute: "^config.bog"
User absolute paths are rooted under the user home directory identified via Sys.getUser-
Home(). In the case of station VMs, user home is the directory of the station database.
• Relative: "myfile.txt"
• Relative with Backup: "../myfile.txt"
• module
The "module" scheme is used to access BIFiles inside the module jar files. The module scheme uses
the "file:" scheme's formatting where the authority name is the module name. Module queries can
be relative also. If the query is local absolute then it is assumed to be relative to the current module.
Module queries always parse into a FilePath:
• module://icons/x16/file.png
• module://baja/javax/baja/sys/BObject.bajadoc
• module:/doc/index.html
• station:
The "station" scheme is used to resolve the BComponentSpace of a station database.
• slot:
The "slot" scheme is used to resolve a BValue within a BComplex by walking down a path of slot
names. Slot queries always parse into a SlotPath.
• h:
The "h" scheme is used to resolve a BComponent by its handle. Handles are unique String identifiers
for BComponents within a BComponentSpace. Handles provide a way to persistently identify a
component independent of any renames which modify a component's slot path.
• service:
The "service" scheme is used to resolve a BComponent by its service type. The body of the query
should be a type spec.
• spy:
The "spy" scheme is used to navigate spy pages. The javax.baja.spy APIs provide a framework for
making diagnostics information easily available.
• bql:
The "bql" scheme is used to encapsulate a BQL query.

Types of space
Space defines a group of objects that share common strategies for loading, caching, lifecycle, naming, and
navigation. Following, is a list of some of the different types of space:
• station
• file
• history
• view

Types of files
In the file system, you may create and edit various types of files, as shown in Figure 1-22. Following, is a
list of some of the different types of files that reside in the file space:

Figure 1-22 Types of files available from the new file menu

• BogFile.bog
bog files are database files. Refer to “About BOG files” on page 1-16 for more information about this
type of file.
• HtmlFile.html
Html files are edited in the Text File Editor view and viewed in the Html View.

NiagaraAX-3.x
1-18
User Guide
Chapter 1 – About NiagaraAX Framework About views
May 1, 2007 Types of files

• JavaFile.java
Java files are edited in the Text File Editor view.
• PaletteFile.palette
These files are custom collections of components that you create and save for viewing in the palette
side bar. Refer to “To create a palette” on page 12-10 for information about creating custom palettes.
• PxFile.px
Px files are edited in the Px view and are used to store graphic presentations that are available for
viewing in the Px viewer and in a browser. Refer to “About presentation xml (px)” on page 1-13 for
more information about px files.
• TextFile.txt
Text files are edited and viewed in the text file editor.
• NavFile.nav
Nav files are edited in the nav file editor and viewed in the nav tree. Refer to “About the Nav file” on
page 8-36 for more information about nav files.

About views
There are many ways to visualize your system and its components. A “view” is a “visualization” of a
component. One way to view a component is directly in the side bar nav tree. In addition, you can right-
click on an item and select one of its views to display in the view pane. You can see many different views
of components. For example, a component that appears in the nav side bar tree may have a wire sheet
view, a property sheet view, and a slot sheet view, that all display in the view pane as shown in Figure 1-
23. Each component has a default view that appears whenever you activate a component (double-
clicking, for example) without specifying a particular view.

Figure 1-23 Views

See “About the view pane” on page 2-10 for more information on the view pane.
Refer to “Plugin Guides” for a comprehensive list of views.

About lexicons
NiagaraAX provides non-English language support by use of lexicons. Lexicons are identified by Java
locale codes, such as “fr” (French) or “de” (German). When installing NiagaraAX on your PC, an instal-
lation step asks you to select “language packages”—these are lexicons. Typically, you install only those
you might need, even though a “Select All” option is available.
Each lexicon is a folder that contains a collection of lexicon files (moduleName.lexicon). Lexicon files are
text files that map various entity “keys” (such as interface names or error and status values) to localized
language characters. Often, mapped characters use special encoding.
Note: Factory-supplied lexicons on a NiagaraAX installation CD typically require review and editing before they
can be used on an actual job. If needed, you can install lexicons from a NiagaraAX CD to your Workbench
PC by simply copying them from the CD’s lexicon folder into a “lexicon” directory created under your
Niagara release directory.
Lexicon files installed on your PC can be accessed and modified using a simple text editor. However, you
typically use the Workbench’s lexicon editor (Tools > Lexicon Editor). The lexicon editor not
only provides edit features, but also shows the default (English) value for each line entry.
In addition, the editor provides a “Lexicon Report” view, useful to see various statuses about a lexicon and
its contained files. For more details, see “Lexicon Editor” on page 11-5. Once reviewed and edited, you
typically install any needed lexicon into all JACE platforms. For more details, see the “Lexicon Installer”
section in the Platform Guide.

NiagaraAX-3.x
1-19
User Guide
About lexicons Chapter 1 – About NiagaraAX Framework
Types of files May 1, 2007

NiagaraAX-3.x
1-20
User Guide
 CHAPTER 2
About Workbench
Workbench is the term for the NiagaraAX graphic user interface. The following sections describe the
general layout and many of the features of the Workbench user interface. Refer to the following sections
for more information:
• Tour of the Workbench GUI
• Customizing the Workbench environment

Tour of the Workbench GUI

When you start Workbench, you will see the Workbench screen, as shown in Figure 2-1.

Figure 2-1 Niagara AX Workbench

Menu Bar

Tool Bar
Locator Bar

View Selector

Side Bar Pane

View Pane

Console

The primary window of the Workbench GUI is divided into three main areas:
• Side bar pane
Top-left area displays one or more side bars that you may choose from the Windows menu. For de-
tails, see “About the side bar panes” on page 2-2.
• View pane
Top-right area displays the currently selected view. For details, see “About the view pane” on page 2-
10.
• Console
Bottom area displays a command line that allows you to issue certain commands directly to the sys-
tem. For details, see “About the console” on page 2-11.

About Workbench window controls

The Workbench window provides typical Windows-type controls plus other features unique to Niagara,
as shown in Figure 2-2.

NiagaraAX-3.x
2–1
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About the side bar panes May 1, 2007

Figure 2-2 Windows controls

Title Bar

Scroll Bars

Border
Controls

Status Bar

You may create additional windows after starting Workbench—all have these basic features:
• Title bar
Has standard Windows title bar features, including windows name and icons to minimize, maxi-
mize, and close. Double-click the title bar to toggle between maximized and a sizable window.
• Border Controls
As needed, drag any outside border to resize the entire window. Drag the inside border between the
side bar and view areas, or (if shown) the console area to change their relative sizes.
• Scroll bars
Scroll bars appear in window areas when some content portions are not visible. They are along the
right and/or bottom portions of a window area (side bar, view, or console).
Simply drag a scroll slider (highlighted area) to scroll quickly. Or, click an ending scroll arrow to
move in small increments.
• Status bar
At the bottom left of the Workbench window is a status bar.
The status bar displays meanings of toolbar buttons. When working in a wire sheet view, other de-
tails are revealed in the status line.

About the side bar panes

Side bar panes are normally visible only if a side bar is open. When you close all side bars, the side bar
pane will collapse and the view pane and console pane (if open) will expand to fill the window. Two types
of side bar panes are:
• Primary side bar pane
The primary side bar pane is the first area on the left, below the locator bar, as shown in Figure 2-3.
• Px Editor side bar pane
This side bar pane appears on the right side of Workbench and is only available when the Px Editor
is active.

NiagaraAX-3.x
2-2
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About side bars

Figure 2-3 Side bar pane

You use a popup menu to perform all operations that are available from inside the side bars (such as
cutting or pasting). You use the title bar to open, close, and resize the side bars.
• For more information about the side bar title bar, see “About the side bar title bar” on page 2-3.
• For more information about types of side bars see “Types of side bars” on page 2-3.

About side bars

All side bars display in the side bar pane and have some common features, such as the side bar title bar.
The following sections describe characteristics of each type of side bar:
• About the side bar title bar
• Types of side bars
About the side bar title bar
All side bars have a title bar across the top as shown in Figure 2-4. You can click and drag on the title bar
to vertically resize the side bar or you can click on a minimized side bar to restore it to the previous size.

Figure 2-4 Side bar title bar

Title

Close Minimize/Maximize

In addition, all side bars have the following controls:

• Close menu
Drop down control used to close the side bar pane.
• Pane title
Icon and text that identifies the side bar.
• Maximize button
When more than one side bar is open, this button appears on the right side of any non-maximized
side bar. Clicking on the maximize button will expand the side bar to fill the side bar pane and the
restore button will change to the maximize button.
• Restore button
If the side bar pane is at maximum size, the restore button appears on the top right corner of the title
bar. Clicking on this button will restore the side bar pane to its previous size and the maximize but-
ton will change to the restore button.
To find out more about specific side bar panes and their controls see “Types of side bars”.
Types of side bars
The following side bars may be displayed in the side bar pane:

NiagaraAX-3.x
2-3
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About side bars May 1, 2007

• Bookmarks side bar

Displays a list of bookmarks. For details, see “About the bookmark side bar” on page 2-4.
• Help side bar
Provides a tree view of available help documentation. For details, see “About the help side bar” on
page 2-4.
• Navigator side bar
Provides a tree view of the system. For details, see “About the nav side bar” on page 2-5. For more
information about the nav side bar, see “Types of nodes in the nav side bar tree” on page 2-6, and
“About the nav side bar toolbar” on page 2-7.
• Palette side bar
Provides a tree view of components that are available in specific palettes. For details, see “About the
palette side bar” on page 2-7 and “About the palette side bar toolbar” on page 2-8.
• Jobs side bar
Provides a tree view of available components. For details, see “About the jobs side bar” on page 2-8.
• Bound ords side bar
Provides a listing of all bound ords used in a Px file. For details, see “About the bound ords side bar”
on page 2-9.
• Widget tree side bar
Provides a tree view of all widgets used in a Px file. For details, see “About the widget tree side bar”
on page 2-9.
• Properties side bar
Provides a listing of all properties for a component that is selected in the Px Editor. For details, see
“About the properties side bar” on page 2-10.
About the bookmark side bar
When you open the bookmark side bar, it appears in the side bar pane, as shown in Figure 2-5.

Figure 2-5 Bookmark side bar

From the bookmark side bar, you can double click on bookmark nodes or use popup menus to perform
all operations that are available from the side bar (for example, go directly to a bookmarked location,
manage bookmarks, edit bookmarks, and more). The quick access provided here is very helpful for
changing screens without having to go through multiple selections using other menus or submenus.
For more details about the bookmark side bar, refer to the following:
• To find out how to add or remove bookmarks in the bookmark side bar, see “To add a bookmark”
on page 12-6.
• For details about managing bookmarks, see “To manage bookmarks” on page 12-7
• For details about editing bookmarks, see “To edit a bookmark” on page 12-7
About the help side bar
When you open the help side bar, it appears in the side bar pane, as shown in Figure 2-6.

NiagaraAX-3.x
2-4
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About side bars

Figure 2-6 Help side bar

The help side bar has three tabs that you may select by clicking on the tab. The three help tabs are listed
and briefly described, as follows:
• Table of Contents
Contains a tree view of help topics, listed in alphabetical order by topic.
• API
Contains a tree view of help topics, listed in alphabetical order by module.
• Search
Contains a Find: text entry field and Search button. For details on using the Search, see “Using
the help side bar” on page 12-7.
About the nav side bar
When you open the nav side bar, it appears in the side bar pane, as shown in Figure 2-7. The nav side bar
contains the tree view that provides a hierarchical view of the whole system. From the nav side bar, you
can double click on nodes in the nav tree or use popup menus to perform all operations that are available
from the nav side bar (for example, connect or disconnect to a station, refresh a tree node, and more).
The expandable tree provided here is very useful for performing actions on nodes and for navigating
through various screens and views in the Workbench. Items are displayed in the tree with an icon that
represents the associated function or file type.
Items are displayed in the tree with a symbol based on type. If the item is a file, it will be based on file type.
Refer to “Types of nodes in the nav side bar tree” on page 2-6 for more details about file types. Refer to
“About the nav side bar popup menu items” on page A-9 for more details about the nav side bar popup
menu.

NiagaraAX-3.x
2-5
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About side bars May 1, 2007

Figure 2-7 Nav side bar

At the highest level, the nav side bar tree may include the following (when working from a localhost):
• My Host (local system)
• My Modules
• Platform
• Stations (connected or disconnected)
Types of nodes in the nav side bar tree
The nav side bar tree may include the following types of nodes and their child nodes:
• Host node
Represents a physical computer (hardware) that the rest of the nodes (subnodes) reside on. For more
details about how the host fits into the Niagara architecture, see “About Niagara software architec-
ture” on page 1-4.
• Module node
When expanded, displays a tree view of available modules, listed in alphabetical order by module.
For more details on modules, see “About modules” on page 1-6.
• File system node
Represents the top level of a tree view of the host file system. File system subnodes represent drives
and locations on the host system. It is important to understand that the file system provides access
to files that are outside of the station database.
• Station node
Represents a station (connected or disconnected). When expanded, the station node displays the
station contents in a hierarchical tree. For more details on stations, see “About stations” on page 1-
15.
• Platform
When expanded, displays a hierarchical view of the Niagara host platform. You can double-click on
the platform node and sub-nodes, or use a right-click shortcut menu to perform all operations that
are available on or under this node (connecting, disconnecting, refreshing, and more). For details on
the platform node and its subnodes, refer to “About a platform connection” in the Platform Guide
for more details.
• Station
When connected and expanded, displays a hierarchical view of the Niagara station. You can double-
click on the station node and sub-nodes, or use a right-click shortcut menu to perform all operations
that are available on or under this node (connecting, disconnecting, selecting views, and more). For
details on the station node, refer to “About stations” on page 1-15.
• Config node
When expanded, displays a tree view of the station contents or “configuration”.
The config node usually contains one or more of the following types of nodes:
• Component
When expanded, components (as containers) display a tree view of the sub-components that
they contain. Various component types may be displayed either in containers or at the root of

NiagaraAX-3.x
2-6
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About side bars

the component node. For more details on components, see “About components” on page 1-9.
• Control
Control points may be displayed directly in the root of the Config node. For more information
about Control points, see “About point components” on page 1-11 and “Data and Control Mod-
el” on page 3-1.
• Drivers
Provides a place to store driver modules (such as the Niagara Network, BACnet drivers, Mod-
bus, and more). When expanded, displays a tree view of loaded driver modules. For more details
about drivers, see “Driver architecture” on page 4-1.
• Services
Component for storing services, such as alarm service, history service, program service, and
more.
About the nav side bar toolbar
In addition to the standard side bar title bar (see “About the side bar title bar” on page 2-3 for more details)
the nav side bar has a toolbar, located just below the title bar as shown in Figure 2-8.

Figure 2-8 Nav side bar tool bar

Drop-down
New Tree
selector
Close Tree

The nav side bar toolbar includes the following:

• New tree button
When clicked, creates a new tree in the nav side bar. When you have more than one tree node, you
can select one to activate from the Drop-down tree selector.
• Close tree button
When clicked, closes the currently displayed palette.
• Drop-down tree selector
When palettes are open in the palette side bar, this selector allows you to choose which palette to
display
About the palette side bar
When you open the palette side bar, it appears on the left side of the Workbench in the side bar pane, as
shown in Figure 2-9. The palette side bar provides a place to open and view sets of modules or custom
palettes that you build for yourself. From the palette side bar, you can open multiple palettes (displaying
them one at a time), close palettes and view modules within palettes. You may also double-click or use
popup menus to perform all operations that are available from the palette side bar (for example, copy
modules, select a module view, refresh the tree node, and more). The expandable tree provided in the
palette allows you to perform actions on nodes within the palette and to navigate through the palette sub-
directories. Items are displayed in the tree with an icon that represents an associated function or file type.

NiagaraAX-3.x
2-7
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About side bars May 1, 2007

Figure 2-9 Palette side bar

For more details about the palette side bar, refer to the following:
• To find out how to use the palette side bar, see “Using the palette side bar” on page 12-9.
• For details about adding palettes to the palette side bar, see “To open a palette” on page 12-
9
About the palette side bar toolbar
In addition to the standard side bar title bar (see “About the side bar title bar” on page 2-3 for more details)
the palette side bar has a toolbar, located just below the title bar as shown in Figure 2-10.

Figure 2-10 Palette side bar tool bar

Open Drop-down
Palette palette selector

Close
Palette

The palette toolbar includes the following:

• Open palette button
When clicked, opens the Open Palette dialog box. Refer to “To open a palette” on page 12-9 for
information about opening palettes.
• Close palette button
When clicked, closes the currently displayed palette.
• Drop-down palette selector
When palettes are open in the palette side bar, this selector allows you to choose which palette to
display.
About the jobs side bar
The Jobs side bar shows all the current jobs in all the stations with which you have a connection. The
current status of each job is shown as: running, canceling, canceled, success, or failed. If the job is running
then a progress bar displays estimated progress. You may cancel a running job by pressing the Cancel
button. Normally, once a job has completed you are notified via the async notification feature. You may
then dismiss the job by pressing the Close button. The details of the job may be accessed using the ">>"
button to display the Job Log dialog box. For details about using the job side bar, refer to “Using the
jobs side bar” on page 12-8.

NiagaraAX-3.x
2-8
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About side bars

Figure 2-11 Jobs side bar

Dismiss Job

Cancel Job
Job Job
Type Status

Job Job View

Status Progress Job
Icon Bar Log

About the bound ords side bar

The bound ords side bar, in Figure 2-12, is available when the Px editor view is active. It displays a listing
of all the bound ords in the current Px view. Double click on any ORD in the list to display the ORD in
the ORD editor dialog box.

Figure 2-12 Bound ords side bar

About the widget tree side bar

The widget tree, in Figure 2-13, displays a tree hierarchy of the widgets (panes, labels, graphic elements,
and so on) that are in the current Px view.

NiagaraAX-3.x
2-9
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About the view pane May 1, 2007

Figure 2-13 Widget tree side bar

Note: It is often easier to use the Widget Tree to select objects when you have a lot of objects on a view–especially
when there are several layers of objects. When you select an object in the tree view it is selected in the Px
view as well and displays the selection borders and handles.
About the properties side bar
The properties side bar, shown in Figure 2-14, is available when the Px editor view is active. It displays a
listing of all the properties that are in the currently selected object in the Px view. Double click on any
object in the widget tree or in the in the Px viewer to display the properties dialog box (same infor-
mation as the properties side bar).

Figure 2-14 Properties side bar

About the view pane

The View pane is the largest window area and is located on the right side, below the locator bar, as shown
in Figure 2-15. Features of the view pane include tabbed views and a thumbnail view.

NiagaraAX-3.x
2-10
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About the console

Figure 2-15 View pane

Multiple tabbed views may be added to the view pane by using the tab feature. You can add, close, and
select tabs in the view window. The view area displays the currently selected view for the active tab. You
can change the selected view by doing any of the following:
• double-click on an item in the nav palette tree
• select a view or action from the nav palette popup menu
• select a command from a menu or submenu
• select a command from the locator bar
• select a view from the view selector or from the view popup menu
The thumbnail view, when active, appears in the top right corner of the window to help you find your way
around the wire sheet. For more details about the thumbnail view, refer to “Show Thumbnail” on page
14-52.
For more details about using tabs, refer to “Creating tabs in the view pane” on page 2-19.

About the console

The console, see Figure 2-16, is located along the bottom of the Workbench interface and may be alter-
natively hidden or shown by selecting Window > Hide Console or Window > Console from the
menu bar.

Figure 2-16 Niagara AX console

The console has scroll bars on the right side and the window size may be adjusted by dragging the top
border bar. The console provides you with access to a command line prompt without leaving the
Workbench environment. From the console you may type in commands directly, including the help
command for additional help. The following lines are some console level commands, parameters, and
options:

NiagaraAX-3.x
2-11
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About the menu bar May 1, 2007

>wb -help

usage:
wb [options] <ord>
parameters:
ord initial ord to display
options:
-profile:<type> workbench:WbProfile to use
-locale:<x> set the default locale (en_US)
-@<option> pass option to Java VM

About the menu bar

The menu bar is the row of pulldown menus located along the very top of the Workbench GUI, as shown
in Figure 2-17. You may use these menus to perform operations throughout the Workbench GUI. Many
of the menus on the menu bar are context-sensitive and only appear when certain views are active.

Figure 2-17 Menu bar

For detailed information about the menus, refer to “Types of menu bar items” on page A-2.

About the toolbar

The toolbar is the row of icons, just below the menu bar, as shown in Figure 2-18. The toolbar provides
menu choices for objects that appear in the view pane. Usually, toolbar icons provide single–click access
to many of the most commonly used features of the Workbench.

NiagaraAX-3.x
2-12
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 About the locator bar

Figure 2-18 Toolbar

In addition to the primary (always visible) toolbar, additional sets of toolbar icons are added to the toolbar
when different views are active. For example, when the wiresheet view is active, the Delete Links icon
is available. When an icon is dimmed, it is unavailable. For more information about specific toolbar icons,
refer to “Types of toolbar icons” on page A-13.

About the locator bar

The locator bar is the area just below the toolbar that spans horizontally from the left edge of the
Workbench GUI all the way to the right side, including the view selector on the right side, as shown in
Figure 2-19. The part of the locator bar that shows your current path (not including the view selector) is
referred to as the PathBar.

Figure 2-19 Locator bar

The purpose of the locator bar is to provide a graphical navigation field for selecting and displaying desti-
nation references. The locator serves two functions.
• First, it is automatically updated each time a new view is selected - so that it shows you the Ord of
each view.
• Second, since the Ord is displayed in a graphical row of icons, you may click on any icon along that
Ord or any child node from the Ord graphical dropdown menu.
Find the Open Ord command by selecting File > Open from the menu bar.

NiagaraAX-3.x
2-13
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
About the view selector May 1, 2007

About the view selector

The view selector appears on the right side of the locator bar, just below the tool bar, as shown in Figure 2-
20.

Figure 2-20 View selector

The view selector provides a context sensitive menu with commands that allow you to quickly display
different views of the information that is currently in the view pane. The commands in the view selector
differ, depending on the current view pane contents. For example, the view selector commands that are
available when you are viewing the platform in the view pane are different from the commands that are
available when you are displaying the driver manager view.

Types of popup menus

Workbench provides view–specific, or context–specific commands for editing components in many of
the views. Following, is a list of the standard Workbench popup (right–click) menus.
• Nav side bar
For an overview of the popup menus in the nav side bar, refer to “About the nav side bar popup
menus” on page 2-14.
For an overview of the nav side bar, refer to “About the nav side bar” on page 2-5.
• Wire sheet
For an overview of the popup menus in the wire sheet, refer to “About the wire sheet popup menu”
on page 2-15.
• Property sheet
For an overview of the popup menus in the property sheet, refer to “About the property sheet popup
menu” on page 2-15.
For descriptions of the property sheet popup menu items, refer to “About the property sheet popup
menu items” on page A-10.
• Px Editor
For an overview of the popup menus in the Px Editor, refer to “Px Editor popup menu” on page 2-16.
About the nav side bar popup menus
The nav side bar menu is the popup menu that displays command options when you right–click on a
component item in the nav side bar. The nav side bar popup menu is context-sensitive and displays items
that relate to the object that is currently selected. For example, the popup menu for a station is different
from a popup menu for a folder or a point. Figure 2-21 shows a popup menu for a selected node in the
nav side bar.

NiagaraAX-3.x
2-14
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 Types of popup menus

Figure 2-21 Nav side bar popup menu

If you right-click in a blank area of the pane (not selecting any items any the tree), the nav side bar pane
will display the Refresh Tree Node and Sync Tree commands. For descriptions of nav side bar
popup menu items, refer to “About the nav side bar popup menu items” on page A-9.
About the wire sheet popup menu
Figure 2-22 shows the wire sheet popup menu with a wire sheet object selected. The menu displays
different items depending on whether you right-click on an item or on a blank area of the wire sheet. For
descriptions of wire sheet popup menu items, refer to “About the wire sheet popup menu items” on page
A-9.

Figure 2-22 Wire sheet popup menu

For a description of the wire sheet, refer to “wiresheet-WireSheet” on page 14-51.

About the property sheet popup menu
Figure 2-23 shows the property sheet popup menu. For descriptions of wire sheet popup menu items,
refer to “About the property sheet popup menu items” on page A-10.

NiagaraAX-3.x
2-15
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
Types of data–presentation controls and options May 1, 2007

Figure 2-23 Property sheet popup menu

For a description of the property sheet refer to “workbench-PropertySheet” on page 14-56.

Px Editor popup menu
The Px Editor popup menu appears when you right-click on an object in the Px Editor view. The menu
commands are context-sensitive and are dimmed or available, depending on the type of object that you
select.
Figure 2-24 shows the Px Editor popup menu. For descriptions of the Px Editor popup menu items, refer
to “About the Px Editor popup menu items” on page A-10.

Figure 2-24 Px editor popup menu

For a description of the Px Editor view, refer to “workbench-WbPxView” on page 14-60.

Types of data–presentation controls and options

Workbench views often present information in text fields, charts, or tabular layouts. Similar views share
many of the same types of controls and options features. Those common features are described, by
category, in the following lists:

NiagaraAX-3.x
2-16
User Guide
Chapter 2 – About Workbench Tour of the Workbench GUI
May 1, 2007 Table controls and options

• Table controls and options

These controls affect the display of information in a table view. For details see “Table controls and
options” on page 2-17.
• Batch editing
Batch editing is available in many table views. For details see “Batch editing (or batch processing)”
on page 2-17.
• Chart controls and options
These controls affect the display chart views. For details see “Chart controls and options” on page 2-
18.

Table controls and options

Many views that present information in a table have one or more of the following display features and use
one or more of the controls and options described in the following list:

Figure 2-25 Table controls and options

Data Parameters

Title Bar Total Records

Column Headings

Column Borders

Table Options Context Sensitive

Menu Menu Items

• Data parameters
These controls include Delta (for history logging) and Time Range settings.
• Delta reporting option
This option is useful for history logging, when you want to display value changes (delta) in your
report. Refer to “About delta logging” on page 6-14 for information about delta logging.
• Time range option list
This list has a variety of predefined time range options, including an option that allows you to
restrict your data presentation to a particular date and time range that you specify.
• Title bar
This area of the table displays the name of the data collection on the left side of the title bar and in
some tables (collection table, history table, alarm extension manager, and others) displays the total
number of records in the table on the right side of the title bar.
• Column headings
Each column of data has a title that indicates the data type.
• Column boundaries
Each column has a movable column boundary that can be used to re-size the column using the
mouse control. Stretch or shrink column width by dragging the column boundary, as desired. Use
the Reset column widths menu item to reset all column widths to their default size.
• Table Options menu
This menu is located in the top right corner of the table and provides one or more of the following
controls and options. The standard table options menu includes the following items:
• Reset column widths
This menu item sets all columns in the table to their default widths. This is useful if you manu-
ally changed widths of columns, and now some contents are hidden (even after scrolling).
• Export
This menu item opens the Export dialog box where you can choose to export the table to PDF,
text, HTML, or CSV (comma separated variable).
• Context-sensitive menu items
Additional context-sensitive menu items appear in the table options menu, depending on
the component that you are viewing. These additional menu items allow you to select or dese-
lect the item in order to display or hide the column data in the table.

Batch editing (or batch processing)

Batch editing is available in many of the table views in Workbench. This is a process of editing or
processing more than one record at a time and typically includes the following general steps:
• Select multiple rows in a table by pressing the Ctrl or Shift key while clicking the desired rows.
• Use the popup (right-click, context-sensitive) menu or a toolbar icon to select an editing command

NiagaraAX-3.x
2-17
User Guide
Tour of the Workbench GUI Chapter 2 – About Workbench
Chart controls and options May 1, 2007

that performs an action or opens a dialog box editor that is appropriate for the view.
• Edit appropriate fields if a dialog box is used and click the OK button to process the edits.
Note: Some actions, such as moving rows, or editing certain types of fields, are not appropriate for
batch editing. In these cases – even though you can select multiple rows in the table, the action will be
performed on only one (usually the top, or highest) selected record in the table.
Figure 2-26 shows an example of batch processing three alarms by selecting three rows in a table view and
using the popup menu. In this case all three alarms are acknowledged when the Acknowledge
command is selected.

Figure 2-26 Batch processing (acknowledging) multiple alarms

Chart controls and options

Note: Some of the control and option features in the following description are available only in NiagaraAX-3.1
and later versions.
Many views that present information in a chart have one or more of the following display features and
use one or more of the controls and options described in the following list:

Figure 2-27 Chart view controls and options

• Data parameters
These controls include Delta (for history logging) and Time Range settings.
• Delta reporting option
This option is useful for history logging, when you want to display value changes (delta) in your
report. Refer to “About delta logging” on page 6-14 for information about delta logging.
• Time range option list
This list has a variety of predefined time range options, including an option that allows you to
restrict your data presentation to a particular date and time range that you specify.
• Chart Title
This area of the chart displays the name of the chart. This title is editable in the chart builder view.
• Y Axis
Displays units for the y axis.
• X Axis
Displays units for the x axis.
• Zoom Controls
Zoom controls appear when you drag the mouse cursor left-to-right or top-to-bottom in order to
zoom into the plotted data area. Use the zoom control to reduce the magnification amount, or to
move the chart left, right, up, or down. You can reduce the zoom level in increments by using the
“decrease zoom” icon . You can restore normal view (no zoom) in one click by clicking the “nor-
mal view” icon . Zoom Controls in Hx Web profile view are available from a popup menu, shown
in Figure 2-28, that is activated after you click once on the chart area.

NiagaraAX-3.x
2-18
User Guide
Chapter 2 – About Workbench Customizing the Workbench environment
May 1, 2007 Creating Additional Windows

Figure 2-28 Hx chart popup menu (for zoom controls)

The popup menu includes the following control-related menu items:

• Zoom In—zooms in one increment each time you select this menu item.
• Zoom Out—zooms out one increment each time you select this menu item.
• Original View—returns to the non-zoomed display (only available if you have zoomed in).
• Higher Quality—toggles between higher and lower quality graphic display for the chart.
• Charted Values
The color of the line and type of line is editable in the Chart Builder view.
• Popup menu (Export)
The popup menu displays the PDF Export menu item. This menu item opens the Export dialog
box where you can choose to export the chart to PDF, text, HTML, or CSV (comma separated vari-
able).
• Tool Tip
When you “hover” the mouse pointer over the chart, a “tool tip” displays the date, time, and value of
that location in the chart. The values are defined by chart axes and not the values of the actual data
points. Figure Figure 2-27.

Customizing the Workbench environment

You can customize your Workbench GUI as well as many of the settings in the Workbench environment.
Some settings require an acknowledgement via the OK button on a dialog box, while others are invoked
immediately and saved automatically on exit from Workbench. For example, when you exit Workbench
with four tabbed windows in your view pane, those same four windows will be displayed the next time
you open Workbench.
You can customize the Workbench environment in the following ways.
Customizing the Workbench GUI
• Creating Additional Windows
• Creating tabs in the view pane
• Bajadoc options
• General Workbench options
• Text editor options
• Wiresheet options
• Alarm portal options
• Alarm console options

Creating Additional Windows

Workbench allows you to create multiple fully functioning Workbench windows. Choosing File: >
New Window from the menu bar, creates a duplicate of your current Workbench window.
After you create multiple windows, you can then customize each individual window, as needed, to access
different information, allowing you to see multiple concurrent views. You can also copy and paste items
from one window into another window.

Creating tabs in the view pane

Workbench allows you to create multiple tabbed views within the view pane of a Workbench window, as
shown in Figure 2-29, by doing one of the following:
• From the menu bar, select File: > New Tab.
• If tabs already exist, right-click on a tab and select New Tab from the popup menu.
The new tab has a view identical to the previous one.

NiagaraAX-3.x
2-19
User Guide
Customizing the Workbench environment Chapter 2 – About Workbench
Types of Workbench options May 1, 2007

Figure 2-29 Tabs in view

As needed, you can use each tab to display a different view, component, or even host, all within the same
Workbench window. When you select a tab (make it active), the locator bar shows the current path and
view. Also, the menu and tool bars update to show appropriate options for the current view.
From the view of the active tab, you can copy items, select another tab, and then paste them into that view.
You can also drag items into an active view from the (Nav or Palette) side bar.
In the Workbench view pane you can use tabs to help organize and selectively display information.
Only one tab may be active at a time. In addition to simply clicking on a tab to make it active, you can
select File: > Next Tab from the menu bar to move to the next tab, moving left to right, or you
can move to the last tab by choosing File: > Last Tab from menu bar.
To close a tab, do any of the following:
• Right-click a tab and choose Close Tab to close that tab, or
• Right-click a tab and choose Close Other Tabs to close all tabs except that tab.
• From the menu bar, choose File: > Close Tab.
The currently active tab is closed.

Types of Workbench options

Use the Workbench options dialog box, shown in Figure 2-30, to customize your Workbench GUI and
to set other preferences. Open this dialog box by selecting Tools > Options from the menu bar.

Figure 2-30 Options dialog box

The following options are available in the options dialog box:

• General Workbench options
• Alarm console options
• Alarm portal options
• Text editor options
• Lexicon options
• Bajadoc options

NiagaraAX-3.x
2-20
User Guide
Chapter 2 – About Workbench Customizing the Workbench environment
May 1, 2007 General Workbench options

• Px editor options
• Wiresheet options

General Workbench options

General Workbench options, shown in Figure 2-31, include settings for a variety of Workbench display
and behavior options.

Figure 2-31 General Workbench options

Note: The Time Format and Unit Conversion parameters affect values that are displayed when connected to a
station using Workbench—regardless of the User preferences (set under User Manager). The User prefer-
ences that are set under the User Manager are in effect when connected to a station by a browser.
• Time Format
Choose from a format option to set the way that Workbench time values are displayed by default.
• Unit Conversion
Choosing the English or Metric option converts values that are displayed in Workbench to the
chosen unit type. Selecting None leaves units in the state that is assigned at the point facet.
• AutoLogoff Enabled
Setting this parameter to True will activate the AutoLogoff feature. When activated, the AutoLogoff
feature will automatically log off a user from a platform when there is no activity detected in Work-
bench for the period specified in the AutoLogoff Period field. Setting this parameter to False will
disable the AutoLogoff feature.
• AutoLogoff Period
Time until Workbench logs off a user when AutoLogoffEnable is set to True.
• Prompt For Name On Insert
When set to True, Workbench will display a Name dialog box, when a new item is added to the
workspace.
• Use Anti Alias
Anti-aliasing causes text to look crisper or smoother on the screen. When this parameter is set to
true, any editable text (for example a label or a text block) will be anti-aliased.
• Font Size
Choose between Normal and Large font options for Workbench display.

Alarm console options

Alarm console options, shown in Figure 2-32, allow you to customize both the appearance and behavior
of the alarm console.

Figure 2-32 Alarm console options

Alarm console options include the following:

NiagaraAX-3.x
2-21
User Guide
Customizing the Workbench environment Chapter 2 – About Workbench
Alarm portal options May 1, 2007

• Minimum Group Ack Priority

Set a minimum priority level at which groups of alarms (more than one at a time) may be acknowl-
edged.
• Needs Explicit Acknowledgement
When set to true, all alarms must be acknowledged by this console before they are removed from the
alarm table.
• Sounds Enabled
When set to true – causes a sound to accompany an alarm.
• Default Sound File
Sets the path to the default sound file.
• Continuous Alarm
When set to true, causes an alarm to repeat continually, until it is acknowledged or cleared.
• Low Priority Color
Choose a color to designate a low priority alarm.
• Mid Priority Color
Choose a color to designate a mid priority alarm.
• High Priority Color
Choose a color to designate a high priority alarm.
• Alarm Class Mapping
Provides a way for you to create alarm classes and map specific alarms to classes.

Alarm portal options

Alarm portal options, shown in Figure 2-33, allow you to customize both the appearance and behavior of
the alarm console.

Figure 2-33 Alarm portal options

Alarm console options include the following:

• Tray Icon Enabled
When set to True, displays an alarm icon in the system tray when the alarm portal is active.
• Alarm Popup Enabled
When set to True, displays an alarm popup window when the alarm portal is active.
• Alarm Popup Always On Top
When set to True, causes the alarm popup window to stay on top of other windows when the alarm
portal is active.
• Alarm Popup Uncloseable
When set to True, makes the alarm popup window uncloseable when the alarm portal is active.

Bajadoc options
Baja reference documentation includes both Java API details as well as Baja slot documentation.
• Show Baja Only
When set to True displays only the reference documentation for slots (Properties, Actions, and
Topics). When set to False, documentation on the Java constructors, methods and fields is also
displayed.
• Flatten Inheritance
This option allows you to flatten the inheritance hierarchy into a single set of documentation. When
set to False only the Java members and Baja slots declared in the specified class are displayed.
When set to True all Java members and Baja slots inherited from super classes are also shown.

Text editor options

These options offer a whole range of ways to customize the presentation and behavior characteristics of
the text editor tool. Settings include text and symbol color coding options, as well as key bindings for
shortcut keys. The text editor options properties are shown in Figure 2-34.

NiagaraAX-3.x
2-22
User Guide
Chapter 2 – About Workbench Customizing the Workbench environment
May 1, 2007 Lexicon editor options

Figure 2-34 Text editor options

Lexicon editor options

These options offer ways to customize the default settings of the lexicon editor. The lexicon editor
options properties are shown in Figure 2-35 and described in “Lexicon Editor” on page 11-5. All of these
properties may be overridden using the options that are available in the Lexicon

Figure 2-35 Lexicon editor options

Px editor options
These options offer ways to customize the presentation and behavior characteristics of the Px editor view.
The Px editor options properties are shown in Figure 2-36 and described in the following list:

Figure 2-36 Px editor options

• Show Grid
This property sets the default condition of the Px editor grid. Select true to make the grid visible
by default or select false to make the grid hidden by default. Either setting may be changed at any
time using the PxEditor menu.
• Grid Size
This property sets the size of the grid in the Px editor.
• Grid Color
This property sets the color of the grid in the Px editor. Click in the color field to display the Color
Choose dialog box. Use the Color Chooser to set the color that you want to assign to the grid.
• Use Snap
This property sets the default condition of the Snap feature in the Px editor. Select true to make
objects snap to locations when they are at a distance equal to the Snap Size. Select false to disable
the snap feature. Either setting may be changed at any time from the PxEditor menu.

NiagaraAX-3.x
2-23
User Guide
Customizing the Workbench environment Chapter 2 – About Workbench
Wiresheet options May 1, 2007

• Snap Size
Set an integer value in this field to define the interval between successive snaps.
• Show Hatch
This property sets the default condition of the Px editor hatching that displays on objects on the Px
editor canvas. Select true to make the hatching visible by default or select false to make the
hatching hidden by default. Either setting may be changed at any time using the PxEditor menu.
• Hatch Color
This property sets the color of the hatching in the Px editor. Click in the color field to display the
Color Choose dialog box. Use the Color Chooser to set the color that you want to assign to the Px
editor hatching.

Wiresheet options
Wiresheet options, shown in Figure 2-37, allow you to customize the appearance of the wire sheet.

Figure 2-37 Wire sheet options

Wire sheet options include the following:

• Show Grid
When set to True displays a grid background on the wire sheet view.
• Show Status Colors
When set to True, will display a different color for each status when it appears in the wire sheet.
• Show Thumbnail
When set to True – provides a small “thumbnail” view of the whole wiresheet for orientation and
navigation purposes.
• Thumbnail X
A field is provided here for setting the X axis for the default position of the thumbnail view.
• Thumbnail Y
A field is provided here for setting the Y axis for the default position of the thumbnail view.

Lexicon options
Lexicon options, shown in Figure 2-38, allow you to change the default filter settings for the lexicon
report and the lexicon editor.

Figure 2-38 Lexicon options

Lexicon options include the following options:

• Hide Ref Values
Ref Values are those filter values that begin with a / . Setting this to True will hide the filter values
from lexicon view. Use this if you do not want to localize references (like icons).
• Hide Accelerators
When set to True this option hides entries that define keyboard accelerators. Use this if you do not
want to localize the accelerators.
• Show Missing
When set to True this option hides entries that are localized. Use this if you do not want to see lo-
calized keys.

NiagaraAX-3.x
2-24
User Guide
 CHAPTER 3
Data and Control Model
In any NiagaraAX station, all real-time data is normalized within the station database as points, a special
group of components. Each point represents one data item.
Note: This applies to a Supervisor station as well as a JACE station, a shift from r2 Niagara data modeling.
Stations no longer have “external links” between them. Instead, proxy points under a Niagara network are
used. For more details, see “About the Niagara Network” on page 4-49.
The following sections provide more details:
• About control points
• About point extensions
• About control triggers
• About point status
• About proxy points
• About writable points
• About composites

About control points

In the most simple form, points are control points. Find them in palette control: Points.

Figure 3-1 Control points

Control points are the foundation for all points in the station, including all proxy points.
• Types of control points
• Other control components
• About data value categories
• About point types
• About point Out
• About point inputs
• About point actions
• About point facets

NiagaraAX-3.x
3–1
User Guide
About control points Chapter 3 – Data and Control Model
Types of control points May 1, 2007

Types of control points

As shown in Table 3-1 there are 8 different simple control points. Each type reflects a combination of a
data (value) category and a point type.

Table 3-1 Control point types

Boolean Category Numeric Category Enum Category String Category
BooleanPoint NumericPoint EnumPoint StringPoint
BooleanWritable NumericWritable EnumWritable StringWritable
See “About data value categories” on page 3-2 and “About point types” on page 3-2.

Other control components

Apart from the 8 simple points, many other components are found in both the control palette and the
kitControl palette. Briefly, these components include:
• Extensions
To “extend” point functionality. See “About point extensions” on page 3-9.
• Triggers
To provide periodic “actions.” See “About control triggers” on page 3-14.
• Other control objects
Found in various folders in the kitControl palette. Use these to provide station control logic based
on data obtained from points. Example objects include (numeric) math types, (Boolean) logic types,
and a PID loop, among others. Also, a few point extensions are in kitControl. See the section “Ap-
plication for kitControl components” in the kitControl Guide.

About data value categories

There are four distinct data value categories for points, as well as for other components (for example,
weekly schedules). These value types are:
• Boolean
Represents a binary value with only two states, such as “Off” or “On.”
• Numeric
Represents an analog value such as a temperature, level, rate or similar floating point number, or a
varying count (integer). Double-precision (64 bit) values are used.
• Enum
Represents an enumerated state (more than two), such as a multi-speed fan with states “Off,” “Slow,”
and “Fast.” Enums are often called multi-states or discretes. States typically derive from established
integer value/state name pairs.
• String
A string of one or more ASCII characters (and if alpha-numeric), often with some literal meaning.
Among the four categories, numeric and boolean points are the most common, as data usually falls into
these two categories.

About point types

Within each of the four point data categories, there are two point types:
• (read-only) e.g. BooleanPoint or NumericPoint
Represents a read-only data item. Unlike with the writable point type, there are no “input” type prop-
erties.
Note: As copied directly from the control palette, there is no application for read-only points.
However, proxy points based upon read-only points, identical except for a non-null proxy extension
and manner of creation, are both common and useful. For more details, see “About the proxy
extension” on page 3-10 and “About proxy points” on page 3-18.
• Writable
Represents a data item that can be written, as well as read by the station (typically). An array of 16
“InN” inputs, each with a different priority level, is available to write the value. By default, the point’s
value can also be set with an operator-issued action (right-click command), available at priority lev-
els 8 (override) and 1 (emergency). For more details, see “About point actions” on page 3-3. Writable
points also have other features. See, “About writable points” on page 3-24.

About point Out

Each point has a property “Out” that provides real-time information, as shown in Figure 3-2.

NiagaraAX-3.x
3-2
User Guide
Chapter 3 – Data and Control Model About control points
May 1, 2007 About point inputs

Figure 3-2 point Out provides real-time information

At a minimum, the Out property provides:

• value
Current value of the data item, within one of four possible data categories. See “About data value cat-
egories” on page 3-2.
• facets
Items affecting the display of the value, such as decimal places, engineering units, or text descriptors
for Boolean/enum states. See “About point facets” on page 3-7.
• status
Current status of the data, meaning the health and validity of the associated value. Status is specified
by a combination of status flags, such as “fault,” “overridden,” “alarm,” and so on. If no status flag is
set, status is considered normal and appears by default as “{ok}.”
Status flags are set in a number of ways. See “About point status” on page 3-15.
• priority
Currently active Niagara priority level (from a 16-level priority scheme), for writable control points
only. For more details on priority, see “About the priority scheme” on page 3-24.
Note: All writable control points include priority in status, including writable proxy points.
Priority appears at the end of the Out value, by default formatted as “@ n”, where n is 1 to 16, or if
the fallback value is in effect, formatted as “@ def”. For example: “Off {ok} @ 1”.

About point inputs

Writable points have 16 input properties: “In1” to “In16,” corresponding to priority levels. As needed, you
can link up to 14 of these inputs to another component in the station. Figure 3-3 shows a BooleanWritable
with links made to 3 inputs.
Note: Read-only (plain) points do not have any input properties.

Figure 3-3 Example links made to priority inputs

By default, a writable point’s glyph (shape on wire sheet) shows only inputs In10 and In16 “pinned” for
linking. However, when linking to a writable point, the Link editor shows all available priority inputs. For
more details, see “About the priority scheme” on page 3-24.

About point actions

Writable points have actions—by default, these appear in a right-click menu when you select a point in a
Workbench view or in the Nav tree (Figure 3-4).

NiagaraAX-3.x
3-3
User Guide
About control points Chapter 3 – Data and Control Model
About point actions May 1, 2007

Figure 3-4 Actions available on right-click menu

An action is a slot that defines a behavior. Some other control objects and extensions also have actions.
In the case of the 4 writable control points, default actions include the ability to:
• Override the point at priority levels 8 (override) and 1 (emergency override), where control can be
independently set or “auto’ed” at either level. An override can be for a defined (or custom) length
duration, as specified in the action’s popup dialog. See “About override actions” on page 3-4.
• Set the value of the point’s “Fallback” property. See “About set (Fallback) action” on page 3-4.
Often, you modify a writable point’s default actions—see “Modifying default actions” on page 3-5.
About override actions
Whenever a writable point is controlled from an action issued at either override level, it has an “override”
status. By default, override status color is magenta, as shown in Figure 3-4. For more point status details,
see “How status flags are set” on page 3-16.
An override action to a value (not an “auto”) prompts for an override duration, see Figure 3-5.

Figure 3-5 Override action duration (“argument”) dialog

By default, a “Permanent” override is the first choice in the drop-down list—the override value will
remain effective until the next time this action is auto’ed. Other timed durations are available, including
a “Custom” selection in which a user specifies a duration in hours, minutes, and seconds. After clicking
OK, the override action is issued to the point—if this is the highest effective priority level, the writable
point operates under this control. If this is a timed override, the action is automatically auto’ed upon
expiration of the override period.
About set (Fallback) action
Whenever a writable point has a “null” or “invalid” value at inputs In1—In16 (note this means that both
override levels are currently “auto’ed”), the Out slot is set to the value of the Fallback property. For more
details, see “About the priority scheme” on page 3-24.
By default, an operator-level user can change the Fallback property, using the “set” action. This produces
a popup dialog that displays the current Fallback value (Figure 3-6).

NiagaraAX-3.x
3-4
User Guide
Chapter 3 – Data and Control Model About control points
May 1, 2007 About point actions

Figure 3-6 Set action prompt to change writable point’s Fallback property

From the set action prompt, a “Cancel” leaves the current Fallback property unchanged. Otherwise, the
Fallback property is set to the value entered (or currently displayed value).
Note: The set action prompt does not display (or accept) a “null” value for Fallback. However, a Fallback of null
can be entered from the point’s property sheet.
A common application for this feature is with NumericWritables used as setpoints, particularly under a
NiagaraNetwork. As Niagara proxy points are always read-only points (not writable types), yet inherit any
actions of the source point, this feature provides user access to setpoints via px graphics without creating
additional proxy points. In particular, this “set” action is designed to work well with “SetPoint” type
widgets (found in the kitPx palette). For details, see “About Widgets” on page 8-7.
Note: Each of the four “constant” kitControl components also provides a “set” action that works in a similar
manner, including with kitPx widgets. However, a constant object (NumericConst, BooleanConst, etc.), has
no priority inputs or Fallback property—the set action simply writes directly to the component’s current
Out slot. For details, see the “About Constant components” section in the kitControl Guide.
Modifying default actions
Unless all the “defaults” for actions of a writable point are acceptable (display names, all actions available,
default user access), you may wish to modify action defaults. Do this from the slot sheet of the writable
point. For general information, see “About slots” on page 1-10, and “Using the slot sheet” on page 12-18.
The following sections provide more details:
• Display names — Change how the point’s popup action menu lists available actions
• Action access — Limit the actions that are made available, either by user level or for all users
Display names By default, action display names are generic (“Emergency Inactive” and so on). You can
change the display name for any action. From the slot sheet, click on an action’s Display Name for an
editor (Figure 3-7). When you change a display name from defaults, it appears in listed in bold.

NiagaraAX-3.x
3-5
User Guide
About control points Chapter 3 – Data and Control Model
About point actions May 1, 2007

Figure 3-7 Editing action display names from slot sheet

When a user invokes an action, the popup menu lists possible actions by more meaningful descriptors.
For example, you could change the “set” action display name from “Set” to “Set Fallback.”
Action access By default, for any writable point, all actions are available to any admin-level user, and all
actions except emergency-level ones are available to an operator-level user. As needed, you can selectively
“hide” actions (from any level user), or change default permissions for actions.
From the slot sheet, do this by editing the action’s config flags (right-click the action and select Config
Flags, as shown in Figure 3-8).

Figure 3-8 Editing config flags of action to “hide” or change permission level

In the Config Flags editor, you click to assign or remove config flags. As pertains to action slots, the
following flags are most often changed:
• Operator
If checked, only operator-level access is needed to invoke the action. If cleared, admin-level access
is needed. For details on permission levels, see “About permission levels” on page 9-5.
• Confirm Required
If checked, a second (confirmation) dialog appears after the action is invoked, before the action ex-
ecutes. An example confirmation dialog is shown in Figure 3-9. By default, this flag is cleared.
• Hidden
If checked, the action does not appear (is hidden) from the action popup menu—for any user. You
may wish to do this selectively for some actions, for example, the “set” action for Fallback access.
(Note that a user with admin-level rights to the point may still access the point’s slot sheet.)

NiagaraAX-3.x
3-6
User Guide
Chapter 3 – Data and Control Model About control points
May 1, 2007 About point facets

Figure 3-9 Action confirmation dialog (from “Confirm Required” config flag)

About point facets

Primarily, facets determine how the point’s value displays in the station. Examples include engineering
units and decimal precision for numeric types, and descriptive value (state) text for boolean and enum
types. With the exception of proxy points (with possible defined device facets), point facets do not affect
how the point’s value is processed.
Note: Besides control points, various other components have facets too. For example, many kitControl and
schedule components have facets. Details about point facets apply to these components too, unless
especially noted.
Topics about facets include:
• Accessing and editing facets
• Facets importance for Enum points
• Effect of facets on point actions
• Effect of facets on proxy points
Accessing and editing facets
Facets is a frozen slot in all control points and objects in the kitControl module. As shown in Figure 3-10,
you modify facet values in a point’s property sheet, using the Edit Facets dialog.

Figure 3-10 Point facets and edit dialog

Optionally, you can add or remove facet values in a point—however, for most points you will only modify
or provide new values for the default facets.
Note: For string-type points (StringPoint, StringWritable), facets have little practical application. By default, the
Facets slot is empty for string-type points.
Facets importance for Enum points
Facets for enum-type components (EnumPoint, EnumWritable, EnumSchedule, etc.) define the
operating range of the component, meaning its different possible enumerated states. Each state is defined
by a pairing of an integer value-to-text, also known as ordinal-tag. Each ordinal must be a unique integer,
and each tag must be unique text. By default, the point’s value displays using tag text.
If you add an enum point from the control palette, its Facets slot has a blank range entry. Until you edit
this facet and supply the ordinal-tag values, it can display only integer values. As shown in Figure 3-11, a
special Enum dialog appears when you edit range facets.

NiagaraAX-3.x
3-7
User Guide
About control points Chapter 3 – Data and Control Model
About point facets May 1, 2007

Figure 3-11 Enum dialog for enum point “range” facets

When defining range enumerations, instead of defining a custom one with your supplied ordinals and
tags text, you can also select from well known “frozen” enumerations, as defined in various installed
modules. A checkbox enables this and provides a drop-down list for you to select by module and enumer-
ation type (see Figure 3-12).

Figure 3-12 Frozen enum selection in Enum dialog

Depending on the driver/network type, the Point Manager under a device may automate this facets range
configuration when you add enum-type proxy points. For example, under a Lonworks device, if you add
a EnumPoint for a Lonworks NVO that uses an enumerated SNVT, that point’s facets will automatically
be configured with the correct range values.
Note: If an enum-type point receives an input value not included in its defined facets range, it displays the ordinal
integer value for that input. This varies from the multistate objects used in r2 Niagara, which would display
“Error” for any value not defined in its “stateText” entries.
Effect of facets on point actions
For some points with actions (see “About point actions” on page 3-3), facets also affect availability in the
point’s action (command) menu, as follows:
• EnumWritable
Upon an override or emergency action, a secondary drop-down selection dialog lists the possible

NiagaraAX-3.x
3-8
User Guide
Chapter 3 – Data and Control Model About point extensions
May 1, 2007 Extension process overview

enum values (in its range), using display tag text. This list appears ordered top-to-bottom by the tag
associated with each ordinal, lowest-to-highest.
• NumericWritable
Upon an override or emergency action, an entry dialog permits a value only between the facets “min”
and “max” values, inclusive. By default, these facets values for numeric-type points are min= -inf and
max= +inf (no effective range checking for an action).
For example, you could use this facet’s feature with a NumericWritable that sets a temperature con-
trol setpoint, by setting its facets min= 65 and max=85. After saving this change, any override or
emergency action issued to that NumericWritable would need to fall within this range. Otherwise,
a user would see a message showing the acceptable range, and be prompted to try again.
Note: Facets “min” and “max” values do not affect any received input values or proxied data, only
what can be issued via an action.
Effect of facets on proxy points
Each proxy point typically represents a piece of data in a remote device (see “About proxy points” on page
3-18). In cases for drivers that support a “learn” mechanism, a proxy point may be created with its facets
(units) already defined—these reflect its “Device Facets” (in its ProxyExt).
If needed, you can change the parent proxy point’s facets to use similar (same family) units. For example,
if a Lonworks proxy point for a temperature NVI (learned in degrees C), you can change the proxy points
facets to degrees F. The “default” conversion performed in the LonProxyExt automatically adjusts the
output value appropriately. In this case, facets directly affect the point’s out value.
Note: If you change a proxy point’s facets to use units that are dissimilar from the device facets in its ProxyExt
(without also changing its Conversion from “Default”), the proxy point will have a fault status (to show
misconfiguration). For example, if its device facets are temperature, and you change the point’s facets to
pressure, the point will have a fault status.
For details on properties common to the ProxyExt in all proxy points, including Device Facets and
Conversion, see “ProxyExt properties” on page 3-23.

About point extensions

As needed, you can add one or more extensions to a point, each as a child of that point. Extensions are a
way to add functionality to a point (or extend it) in a modular fashion.
The following topics provide more details on extensions:
• Extension process overview
• Types of point extensions
• About the proxy extension
• About control extensions
• About alarm extensions
• About history extensions
Note: Extensions also apply to most kitControl objects. See “Extensions and kitControl components” on page 1-4
for more details.

Extension process overview

Extensions are found in several palettes, including alarm, control, history, and kitControl.
You typically add an extension by either:
• dragging it into the property sheet of the point, or
• dropping it on the point’s icon in the Nav tree.
A point’s property sheet lists extensions below its normal (frozen) properties. You can expand each
extension to view and modify its properties, as shown in Figure 3-13.

NiagaraAX-3.x
3-9
User Guide
About point extensions Chapter 3 – Data and Control Model
Types of point extensions May 1, 2007

Figure 3-13 Extension expanded in a point’s property sheet

If a point has multiple extensions, they are processed in the same top-to-bottom order that they appear
listed in that point’s property sheet. You can re-order extensions in a point—from the top of the point’s
property sheet, or on the point’s icon in the Nav sidebar, right-click and select Reorder.
Note: If needed, you can also select and expose extension properties (for linking convenience) on the point’s glyph
by using the Composite editor of the parent point. For more details, see “About composites” on page 3-26.

Types of point extensions

Point extensions include the standard proxy extension (one for each point, see “About the proxy
extension” on page 3-10) and also optional extensions.
Optional extensions are in three main categories:
• control extensions
from control palette. See “About control extensions” on page 3-11.
• alarm extensions
from alarm and kitControl palette. See “About alarm extensions” on page 3-12.
• history extensions
from history palette. See “About history extensions” on page 3-13.

About the proxy extension

Each point has a proxy extension (Proxy Ext), a frozen property. The proxy extension is important—it
indicates how the point’s data originates, including details specific to the parentage of the point’s network
and communications (driver).
A point’s proxy extension is either:
• Null
For any point that you copy from the control palette (or add using the right-click menu), the proxy
extension is simply null (NullProxyExt)—an empty placeholder. The station itself originates the
point's default Out value.
• <DriverType>
For any proxy point, meaning any of the 8 point types you create using the Points extension under a
device represented in any of the network types, the proxy extension is <DriverType>ProxyExt. For
example, a BooleanWritable proxy point under the Points container of a Bacnet Device has a proxy
extension of “BacnetBooleanProxyExt.”
For any proxy point, its proxy extension contains information organized in child properties. Some
properties may be unique to that specific driver type.
Figure 3-14 compares property sheet views of the proxy extension properties for two BooleanWrit-
able points, on the left a control point, on the right a BACnet proxy point.

NiagaraAX-3.x
3-10
User Guide
Chapter 3 – Data and Control Model About point extensions
May 1, 2007 About control extensions

Figure 3-14 Proxy extension for control point (null) and a Bacnet proxy point.

For more details, see “About proxy points” on page 3-18 and “ProxyExt properties” on page 3-23.

About control extensions

Control extensions are found in palette control: Extensions (Figure 3-15). As needed, you can add
them to points along with alarm and history extensions.

Figure 3-15 Control extensions

Control extensions perform additional processing on a point’s received value. There are relatively few
types of control extensions. See “Types of control extensions” on page 3-11.
Types of control extensions
Table 3-2 lists all available control extension types and the applicable point parents.

Table 3-2 Control extension types

Control extension type Applies to point types What it does
(palette:Folder) (read-only) Writable
DiscreteTotalizerExt BooleanPoint BooleanWritable Accumulates runtime and change
(control:Extensions) EnumPoint EnumWritable of state (COS) count. Extension
actions permit resetting (zeroing)
— any object with single Bool- the runtime and COS count.
ean Out, e.g. kitControl:
Logic object “And”

NiagaraAX-3.x
3-11
User Guide
About point extensions Chapter 3 – Data and Control Model
About alarm extensions May 1, 2007

Control extension type Applies to point types What it does

(palette:Folder) (read-only) Writable
NumericTotalizerExt NumericPoint NumericWritable Accumulates numeric total using
(control:Extensions) — any object with single hourly or minutely totalization.
Numeric Out, e.g. kitControl: Extension has action to reset
Math object “Add” (zero) total.

ProxyExt (standard for any point, see ““About the proxy extension” Provides methods to driver com-
(control:Extensions) on page 3-10) munications.

About alarm extensions

Use an alarm extension for any point you wish to monitor for offnormal values, and show alarm
indication when a limit or value is met or exceeded. In an alarm extension, you also specify whether an
alarm annunciation should occur upon alarm transitions, plus many other parameters.
Find the alarm extensions in palettes alarm: Extensions (Figure 3-16) and kitControl:Alarm.

Figure 3-16 Alarm extensions

Alarm extension properties define items such as alarm enable (annunciation) transition types, alarm
delay times, associated alarm class, and alarm display text for different transition types. You define the
actual alarm limits or state(s) in properties in the extension’s “Offnormal Algorithm” slot. For more
details, see “About alarm extension properties” on page 7-3.
Types of alarm extensions
Table 3-3 lists all alarm extension types and the applicable point parents.

Table 3-3 Alarm extension types

Alarm extension type Applies to point types General description
(palette:Folder) (read-only) Writable
OutOfRangeAlarmExt NumericPoint NumericWritable Provides alarming based upon
(alarm:Extensions) — any object with single numeric alarm high and low limits.
numeric Out, e.g. kitControl: Includes configurable deadband.
Math object “Add”
BooleanChangeOfStateAlarmExt BooleanPoint BooleanWritable Provides alarming based upon one of
(alarm:Extensions) — any object with single Bool- two possible values (state) as an
ean Out, e.g. kitControl: alarm condition.
Logic object “And”
BooleanCommandFailureAlarm- — BooleanWritable Provides alarming based upon mis-
Ext match between commanded value
(alarm:Extensions) and actual (sensed) value. Extension
has feedbackValue input property
for linking.

NiagaraAX-3.x
3-12
User Guide
Chapter 3 – Data and Control Model About point extensions
May 1, 2007 About history extensions

Alarm extension type Applies to point types General description

(palette:Folder) (read-only) Writable
EnumChangeOfStateAlarmExt EnumPoint EnumWritable Provides alarming based upon one of
(alarm:Extensions) multiple possible values (state) as an
alarm condition.
EnumCommandFailureAlarmExt — EnumWritable Provides alarming based upon mis-
(alarm:Extensions) match between commanded value
and actual (sensed) value. Extension
has feedbackValue input property
for linking.
StatusAlarmExt any type that accepts any type that accepts exten- Provides alarming based upon any
(alarm:Extensions) extensions sions combination of status flags, includ-
ing overridden, null, etc.
LoopAlarmExt(kitCon- — LoopPoint Sliding alarm limit for LoopPoint
trol:Alarm) based upon controlled process devi-
ation from setpoint.
ElapsedActiveTimeAlarmExt BooleanPoint with BooleanWritable with Dis- Provides alarming based upon accu-
(kitControl:Alarm) DiscreteTotalizerExt creteTotalizerExt mulated runtime (elapsed active
— any object with single Bool- time). References a specific Discrete-
ean Out (also with a Discre- TotalizerExt under same parent
teTotalizerExt), e.g. kitCon- point.
trol: Logic object “And”
ChangeOfStateCountAlarmExt BooleanPoint with BooleanWritable with Dis- Provides alarming based upon accu-
(kitControl:Alarm) DiscreteTotalizerExt creteTotalizerExt mulated COS (change of states). Ref-
— any object with single Bool- erences a specific DiscreteTotalizer-
ean Out (also with a Discre- Ext under same parent point.
teTotalizerExt), e.g. kitCon-
trol: Logic object “And”

About history extensions

Add a history extension to any point for which you want to log historical data, that is collect a history. In
a point history, each collected sample of slot “Out” has a date-timestamp, point status and value. Point
history data is viewable in both a table and chart format.
Find the history extensions in palette history: Extensions (Figure 3-17).

Figure 3-17 History extensions

Each history extension has various properties in two major groups:

• Collector
Determines how or when data is collected, such as active time, and (if applicable) either change tol-
erance or the collection interval time.
• History Config
Determines how the data is stored and accessed in the system, such as history name, capacity, and

NiagaraAX-3.x
3-13
User Guide
About control triggers Chapter 3 – Data and Control Model
About history extensions May 1, 2007

full policy.
For more details, see About Histories.
Types of history extensions
Table 3-4 lists all history extension types and the applicable point parents.

Table 3-4 History extension types

History extension type Applies to point types General description
(read-only) Writable
BooleanChangeOfValue BooleanPoint BooleanWritable Collects upon each change of Bool-
— any object with single ean value (state) or status.
Boolean Out, e.g. kitCon-
trol: Logic object type
“And”
BooleanInterval as above as above Collects upon a repeating time
interval, as configured.
NumericChangeOfValue NumericPoint NumericWritable Collects upon each change of value
— any object with single (outside a specified tolerance) or
Numeric Out, e.g. kitCon- change of status.
trol: Math object type
“Add”
NumericInterval as above as above Collects upon a repeating time
interval, as configured.
EnumChangeOfValue EnumPoint EnumWritable Collects upon each change of enu-
— any object with single merated state or status.
Enum Out
EnumInterval as above as above Collects upon a repeating time
interval, as configured.
StringChangeOfValue StringPoint StringWritable Collects upon each change of string
— any object with single value or status.
String Out
StringInterval as above as above Collects upon a repeating time
interval, as configured.

About control triggers

There are two “time triggers” in the palette control:Trigger. These objects do not represent data, but
instead regularly fire a topic.

Figure 3-18 Control triggers

The two control trigger types are:

• Interval
Fires at a regular, repeating intervals specified in its Trigger Mode property.
For example, every n minutes, n hours, or whatever combination needed.
• Daily
Fires once a day at a specific time and day of week, as specified in its Trigger Mode property. For

NiagaraAX-3.x
3-14
User Guide
Chapter 3 – Data and Control Model About point status
May 1, 2007 How triggers are used

example, at 00:00:00 (midnight) all days of week except Sunday.

Each type has even more configuration capabilities to further define the fire time.

How triggers are used

To use a trigger, you typically link it to a selected action of a point extension (e.g. control, alarm, and
history) to automate an action. Often, you use a trigger as a child of a particular point (sibling to the linked
extension). Or, you can have a trigger in the same container as multiple points, and link it to more than
one point or point extension.
For example, a Daily trigger (defined for midnight) can be linked to the ResetElapsedActiveTime action
of a DiscreteTotalizerExt extension of a BooleanWritable point. In this case, that point’s DiscreteTotal-
izerExt would only show runtime accumulated during the current day.

About related objects

Other objects with trigger functions are found in various palettes. The most closely related is the Trigger-
Schedule object, found in the Schedule palette. See “About trigger schedules” on page 10-18.

About point status

Along with point value, point status is available at point Out. Status reflects status flags, which may get
set singly, or in combinations. Status flags are typed by a unique text string (for example: “alarm” or
“down”), and many have associated status colors (a background and a foreground). For example, the
default status colors for alarm is white text on red background.
Status without any flags set is considered normal (text “ok”), and is without color indication.
Note: For each installed lexicon, text strings for status flags (plus associated colors), are individually adjustable
by editing default values in that host’s baja lexicon, using Workbench’s Lexicon Editor. For a default
English installation, to change default status appearance settings, edit the en: baja lexicon. For more
details, see About Lexicons.
The following topics explain further details about point status:
• Types of status flags
• Priority of status indication
• How status flags are set
• About “isValid” status check

Types of status flags

Status flag types are listed in Table 3-5, along with associated default colors (if any).

Table 3-5 Status flag types

Type Default Colors, Exam- Meaning

ple

alarm white text, Point currently has a value in an alarm range, as defined by property in its
red background alarm extension.

fault black text, Originates from a proxy point only. Typically indicates a configuration or
orange background licensing error. If it occurs after normal operation, it may indicate a “native
fault” in device, or the point’s parent device has a fault status.

overridden black text, Current point control is from an action, meaning a user-invoked command
magenta background at either priority level 8 (override) or priority 1 (emergency).

disabled gray text, Originates from a proxy point only. Point (or its parent device or network)
light gray background has been manually disabled (property enabled = false).

NiagaraAX-3.x
3-15
User Guide
About point status Chapter 3 – Data and Control Model
Priority of status indication May 1, 2007

Type Default Colors, Exam- Meaning

ple

down black text, Originates from a proxy point only. Driver communications to the parent
yellow background device are currently lost, based upon the device status (Monitor) configu-
ration for that network.

stale black text, Originates from a proxy point only. Driver communications have not
tan background received a requested response for this data item within the configured
times (Tuning period).

null (no color indication) Current point control has entered a null state, vs. a specific value and pri-
ority level. Typical to fallback operation for a writable point.

unackedAlarm (no color indication) Last point alarm event has not yet received user acknowledgment. Point’s
alarm extension uses alarm class requiring acknowledgment.

Priority of status indication

Since status flags for a point or object can get set in combinations, status color indication uses a priority
method. Among those 6 status flags with associated colors, priorities (and default colors) are:
1.
disabled (dark gray)
Proxy point origination only. Point may have other status flags set. Typically, you manually set and
clear this status (unlike others). After disabled is set for a proxy point, it is no longer polled. Further
status changes do not occur until disabled is cleared.
2. fault (orange)
Proxy point origination only. See “Proxy point status” on page 3-18.
3. down (yellow)
Proxy point origination only. See “Proxy point status” on page 3-18.
4. alarm (red)
Point may have other status flags set.
5. stale (tan)
Proxy point origination only. See “Proxy point status” on page 3-18.
6. overridden (magenta)
Point may have other status flags set.
Note: Status types unackedAlarm and null do not affect the indicated status color.

How status flags are set

Status flags are set differently depending on the type of point or control object. The following sections
explain:
• Simple control point status
• Propagate Flags status option (linked Math and Logic objects)
• Proxy point status
Simple control point status
For simple control points (NullProxyExt) the following status flags are the only ones set and cleared:
• alarm
Point is currently in an alarm condition as defined in its alarm extension.
• unackedAlarm
Point has alarm extension assigned to an alarm class requiring acknowledgment, but the last alarm
event has not yet been acknowledged. Point may/may not be in alarm.
• override
Writable points only, during a user-initiated action at priority levels 8 (override) or 1 (emergency).
The override flag clears when the action “times out,” or when a user issues an “auto” action at that
same priority level.
• null
Writable point has “null” or otherwise “invalid” value at In1—In16, plus “null” configured as “Fall-
back” value. See “About “isValid” status check” on page 3-18.

NiagaraAX-3.x
3-16
User Guide
Chapter 3 – Data and Control Model About point status
May 1, 2007 How status flags are set

See Figure 3-19 for examples of override and alarm status in simple control points.

Figure 3-19 Status with simple control points

Propagate Flags status option (linked Math and Logic objects)

By default, kitControl objects maintain independent status flags from input-linked points. However, as a
configuration option in each math or logic-type kitControl object (kitControl palette folders “Math” and
“Logic”), you can specify “out” status to propagate from input status.
The object’s Propagate Flags property allows you to select any combination of the following status
types for propagation:
• disabled
• fault
• down
• alarm
• overridden
Note: If the math or logic object has multiple inputs, and you set the propagateFlags property to select one or more
of the statuses above, simple “OR” logic is used across all inputs for the propagation of each selected status.
Depending on usage, status propagation may be extensive. Note that four of the five status types (all
except alarm and overridden) are “invalid status,” meaning they cause the output of the object (if linked)
to be considered invalid at its destination target. See “About “isValid” status check” on page 3-18.
As an example of status propagation, some number of NumericWritable points are used to establish
setpoints, and you link them all to a Math: Average object for downstream zone control. In turn, the
Average object feeds a Math: Reset object. Both math objects have “override” enabled in their “propagate-
Flags” property. A user issues an override (action) to one of the NumericWritable points, to override a
setpoint (Figure 3-20).

Figure 3-20 Status propagation in linked writable points, kitControl objects

NiagaraAX-3.x
3-17
User Guide
About proxy points Chapter 3 – Data and Control Model
About “isValid” status check May 1, 2007

For the duration of the override, the linked Average object will also have an overridden status, as will the
Reset object, and so on. However, note that the linked writable point (NWcombined) in this example does
not have overridden status—status never propagates to any point.
Note: Status propagation did not occur in Niagara r2, and is a new configuration option in NiagaraAX. Before
using this feature in an actual job, you should test and evaluate results to be sure it has the desired effect.
For example, if a Logic or Math object is exposed in a graphic and appears overridden, a user may (incor-
rectly) assume that they can right-click command (perform an action) on that kitControl object, based on
status color indication.
Proxy point status
In addition to status flags that also apply to non-proxy points (see “Simple control point status” on page
3-16), some status flags in proxy points are set and cleared resulting from polled value or status updates
received via the parent driver’s communications subsystem, for example:
• down
Driver unable to receive reply from parent device, as per configuration in Monitor extension. In this
case, all proxy point children of the device will have status down.
• fault
Typically, this indicates an AX configuration error or license error. If a fault occurs following normal
(ok) status, it could be a “native fault” condition detected within the device, or perhaps some other
fault criteria that was met. The point’s proxy extension contains a “Fault Cause” text property that
contains more information.
• stale
Since the last poll update, the point’s value has not updated within the specified “Stale Time” of its
Tuning Policy. This stale status clears upon next received poll value.
Statuses above are set automatically, but you typically set a fourth status for a proxy point manually:
• disabled
Using the proxy extension’s Boolean property “Enabled” (default is true). While set to false (dis-
abled), polling stops for that point, as well as any further status changes.
Note: Typically, a proxy point has an alarm status only if its value falls in the “offnormal algorithm” limits
specified in its own (NiagaraAX) alarm extension. If the driver and protocol has “native” alarm determi-
nation methods (such as with BACnet), a proxy point may show alarm status that originated locally within
that device. In the case of the Niagara Bacnet driver, this also applies to override status, possibly a
“native” condition for a proxied BACnet object.

About “isValid” status check

When linking an input-type slot of a writable point or kitControl object, the value received at the input
is processed (evaluated) by that point or object only if it is valid.
Note: A valid input is one with none of the following status flags set:
• down
• fault
• disabled
• null
• stale
If any of the above status bits are set at an input, that input value is not used.
• If a kitControl object with a single input, by default that object uses the last known valid received (at
least until the input becomes valid again).
• If a kitControl object with a multiple inputs, only the valid inputs are evaluated.
• If a writable point, the priority scan continues. See “About the priority scheme” on page 3-24.

About proxy points

Proxy points are often the bulk of all points in a station. This is true whether a JACE or a Supervisor
station. Proxy points are any of the 8 simple control points (Table 3-1 on page 2), only with a non-null
proxy extension. See “About the proxy extension” on page 3-10.
These following sections provide more details about proxy points:
• Location of proxy points
• How proxy points are made
• Proxy points versus simple control points
• ProxyExt properties

NiagaraAX-3.x
3-18
User Guide
Chapter 3 – Data and Control Model About proxy points
May 1, 2007 Location of proxy points

Location of proxy points

In the AX station architecture, proxy points must reside under the driver network and device from which
the specific data originates. Proxy points are under that device’s Points container (Points extension), as
shown in Figure 3-21.

Figure 3-21 Proxy points location example

As needed, you can create folders under a device’s Points container to further organize the proxy points.
In addition to proxy points, you can also add simple control points (null proxy ext), schedule objects, and
other kitControl objects under a device’s Points container.
Note: See also “Location for kitControl components” in the kitControl Guide.
Depending on station type, proxy point locations will vary as follows:
• JACE station
Most proxy points are under non-Niagara driver networks, such as Lonworks, Bacnet, and Modbus,
to name a few. These points represent real-time data in various devices attached (or somehow net-
worked) to the JACE controller.
Like all AX stations, the JACE will also have a Niagara Network too. Any proxy points under it will
represent data received from other JACE stations and/or perhaps the Supervisor station.
• Supervisor station
Typically, most proxy points are under its Niagara Network, where each JACE appears as a station
device. Proxy points under each station device represent real-time data from that JACE. Typically,
most data in a JACE station also originates as a proxy point, and so these points are often a “proxy
of a proxy.” For details, see “About the Niagara Network” on page 4-49.
Note: If the Supervisor is specially licensed for direct field device communications, such as a BACnet
Supervisor or OPC Supervisor, its station will have many proxy points under other driver network
types, and perhaps only a few under its NiagaraNetwork. In Drivers architecture, it resembles a JACE.
For more details, see “Driver architecture” on page 4-1.

How proxy points are made

Note: You create proxy points in a station as one of the later stages in building a driver network. This section only
provides an overview of the proxy points portion. For more complete details, see “Driver architecture” on
page 4-1.
When you add a device under a network, one of its default extensions is a container named “Points.” The
default view for Points is a “Point Manager,” which you use to add proxy points to the station database.
An example Bacnet device Points Manager is shown in Figure 3-22.

NiagaraAX-3.x
3-19
User Guide
About proxy points Chapter 3 – Data and Control Model
How proxy points are made May 1, 2007

Figure 3-22 Points Manager example (Bacnet Device)

Typically, you have performed your previous station configuration of this network with the host (e.g.
JACE) networked and communicating to the devices of interest. This allows you to use the “Learn Mode”
feature (provided by most drivers). This feature is especially useful for adding proxy points to the station.
In the Point Manager, the Learn Mode toggles the view between only proxy points that are currently in
the station (“Database”), and a split view showing both a “Discovered” area and the “Database” area. See
“About Learn toggle” on page 4-16 for more details.
Clicking the Discover button launches a “point discovery job.” The driver queries the selected device
to retrieve available data. Depending on a number of factors (driver type, communications rate, amount
of data), this can take from only a few seconds to over a minute. See Figure 3-23.

Figure 3-23 Points Discover in progress

When the discover completes, the “Discovered” view portion provides a table of available data items.
Each row represents at least one item (a candidate for one proxy point). If there are multiple, closely-
related data items, that row appears with a leading plus (“+”). You can expand it to see other available data
items. Again, each row is a candidate for one proxy point.
Depending on the driver type, table column headings vary—for example a Bacnet points discover shows
“Object Name,” “Object ID,” etc., in the Discovered table (see Figure 3-24).

NiagaraAX-3.x
3-20
User Guide
Chapter 3 – Data and Control Model About proxy points
May 1, 2007 How proxy points are made

Figure 3-24 Points Discover completed

As needed, you click on column headers to resort and/or use the scroll bar to view available discovered
data items. After selecting one or more items by clicking on rows (to highlight), you can click the Add
button to start the proxy point creation process. The Add dialog appears (Figure 3-25).

Figure 3-25 Add points dialog

The Add dialog allows you to select each data item and change things about its default point creation
before it is added to the station database. Most important is “Type,” meaning the control point type—as
unlike other things (such as Name) you cannot change that after the creation. Apart from Name and
Type, most other properties are proxy extension properties.
Selecting the Type drop-down, alternate point types are available for selection, see Figure 3-26. If the
driver recognizes the data item as writable, this will include writable point types.

NiagaraAX-3.x
3-21
User Guide
About proxy points Chapter 3 – Data and Control Model
How proxy points are made May 1, 2007

Figure 3-26 Type drop-down in Add dialog

Typically, you do not change the data category type (Boolean, Numeric, etc.), but you may wish to select
either a read-only point or a writable point.
You click any discovered data item to select it for changing Type, or any other property. If a common
change is needed among data items (for example, Poll Frequency), you can select multiple items and edit
that property one time.
When you are satisfied with the point types shown for each item, you click the OK button at the bottom
of the Add dialog. Those proxy points are then created in the station database in the Points container,
and now appear as table rows in the “Database” (lower) table of the Point Manager view. The source data
items now appear “ghosted” in the “Discovered” (upper) table, to indicate that they now exist in the
station database. See Figure 3-27.

Figure 3-27 Proxy points added to station

You may repeat this process as needed to create additional proxy points, where you can toggle the display
of the Discovered portion off and on by clicking the Learn Mode tool.
Once in the Database table of the Points Manager, you can click to select (highlight) a proxy point, then
modify it using the Edit button, or simply double-click it. This produces an Edit dialog nearly identical
to the Add dialog, where you can change the same proxy extension properties and Name (but not Type).
You can also select multiple proxy points and use the Edit dialog to “gang edit” one or more of the same
properties that are common to each selected point.
In the Database portion, you can right-click a proxy point to access its normal views, including property
sheet. There, you can expand its Proxy Ext to see many of the same properties you saw in the Add and
Edit dialogs. Also, you can right-click a proxy point in the Database table to access any available point
actions (if a writable point).
Each Points container has other views besides the default Point Manager. For example, you can select its
Wire Sheet view to see and organize the proxy points glyphs (Figure 3-21 on page 19), add additional
objects from palettes control and/or kitControl, and so forth.
Note: The following notes apply when working with proxy points.
• In a Niagara Network, the Discover and Add process is different than in other driver networks.
There, you use a “BQL Query Builder” to select data items in a remote station. For more details, see

NiagaraAX-3.x
3-22
User Guide
Chapter 3 – Data and Control Model About proxy points
May 1, 2007 Proxy points versus simple control points

“About the Niagara Network” on page 4-49 and “About the Bql Query Builder” on page 4-56.
• Any Point Manager view only shows proxy points. If you added other objects (for example, control
points with null proxy extension, or kitControl objects), they do not appear in the Database table.
However, they are visible in the Nav tree and the Points wire sheet.
• If you want folders under Points to organize your proxy points and other objects, use the “New Fold-
er” button in the Point Manager to create each folder. This provides a Point Manager view for each
folder. For more details, see “About the Point Manager” on page 4-28.

Proxy points versus simple control points

Functionally, there is little difference between a simple control point (NullProxyExt) and the equivalent
proxy point. For example, you can add the same extensions (e.g. control, alarm, and history) to a proxy
point as to a simple control point—there is no need to “duplicate” the point first.
However, apart from the location differences (see “Location of proxy points” on page 3-19) and manner
of creation (see “How proxy points are made” on page 3-19), proxy points have the following differences
from simple control points:
• Status flag processing
Status flags of proxy points are affected by real-time changes that may occur in the remote device,
plus changes in communications between that device and the station. This is in addition to “AX-add-
ed” status flags set by an alarm extension (for example, “alarm” or “unackedAlarm”). See “Proxy
point status” on page 3-18.
Related are “global” status rules common among NiagaraAX drivers, set at both the network-level as
well as adjustable at the proxy-point level. For details, see “About Tuning Policies” on page 4-8.
• Point duplication
When you duplicate a proxy point, you are duplicating information in its Proxy Ext that might be
better left unique. This may result in redundant messages between the device and station for the
same data item, adding overhead. If duplicating a proxy point, you should have a clear idea of what
you will change to prevent this inefficiency.

ProxyExt properties
Regardless of the driver, the proxy extension (ProxyExt) for any proxy point has a number of core
properties that provide the same behavior. Depending on the driver, other ProxyExt properties are often
present—see the particular driver document for details on those properties.
Core properties in any ProxyExt include the following:
• Status
(read only) Status of the proxy extension, which in turn determines parent point status. See “Proxy
point status” on page 3-18.
• Fault Cause
(read only) If point has fault status, provides text description why.
• Enabled
Either true (default) or false. While set to false, the point’s status becomes disabled and polling is sus-
pended.
• Device Facets
(read only) Native facets used in proxy read or writes (Parent point’s facets are used in point status
display, and are available for edit in Add and Edit dialogs in Point Manager).
• Conversion
Specifies the conversion used between the “read value” (in Device Facets) and the parent point’s out-
put (in selected point facets).
Note: In most cases, except when working with particular Ndio proxy points, or perhaps Modbus
proxy points, the standard “Default” conversion selection is best.
Conversion selections include:
• Default
(The default selection). Conversion between “similar units” is automatically performed within
the proxy point. For example, if a Lon proxy point with a LonFloatProxyExt (Device Facets of
degrees C), if you set the point’s Facets to degrees F, its output value automatically adjusts.
If you set the parent point’s Facets to dissimilar units (say, in this case to kilograms), the parent
point has a fault status to indicate a configuration error.
• Linear
Applies to certain Ndio proxy points, such as NdioVoltageInput and NdioResistiveInput. Also
commonly used in some Modbus proxy points. For these points, you typically want the point’s
output value in some units other than Device Facets (if Ndio, voltage or resistance), and the Lin-

NiagaraAX-3.x
3-23
User Guide
About writable points Chapter 3 – Data and Control Model
About the priority scheme May 1, 2007

ear selection provides two fields to make the transition:

– Scale: Determines linear response slope.
– Offset: Offset used in output calculation.
• Reverse Polarity
Useful in a Boolean-type Ndio proxy point to reverse the logic of the hardware binary input. Al-
so, may be used in any driver’s proxied BooleanPoint, as a way to “flip” the read state of the na-
tive value.
Note: Be careful in the use of the reverse polarity conversion, as it may lead to later confusion
when troubleshooting logic or communications problems.
• Thermistor Type 3
Applies to an NdioThermistorInput point, where this selection provides a “built-in” input re-
sistance-to-temperature value response curve for Type 3 Thermistor temperature sensors.
• Tabular Thermistor
Applies to an NdioThermistorInput point, where this selection provides a control for a popup
dialog for a custom resistance-to-temperature value response curve, including ability to import
and export response curves.
• Tuning Policy Name
(most drivers) Associated network tuning policy for this proxy point, by name. Tuning policies are
used to separate poll rates and other driver features. See “About Tuning Policies” on page 4-8.
• Read Value
(read only) Last value read from the device, expressed in device facets.
• Write Value
(read only) Applies if writable point only. Last value written, using device facets.

About writable points

All writable points provide right-click actions. Override actions are evaluated within the priority scheme
used by any writable point. In the case of the “set” action, the point’s “Fallback” property is modified (see
“About point actions” on page 3-3). BooleanWritable points also offer built-in “minimum on/off ” timers.
• About the priority scheme
• About minimum On and Off times

About the priority scheme

Each writable point uses a 16-level priority scheme, with corresponding inputs In1—In16, plus a
“Fallback” property. Level 1 is the highest priority, and level 16 is the lowest.
The following topics further describe the priority scheme:
• Priority input scan
• Priority linking rules
• Priority level conventions
Priority input scan
For any writable point, the effective input value is determined by a priority scan, looking for a “non-auto”
action at level 1 (emergency), then the value at the highest valid input, going from level 2, to 3, and so on
to level 16. (At level 8, any “non-auto” action is evaluated as valid).
Like almost all control execution, this priority scan is event-driven, meaning it occurs when any input
value changes. An input’s value typically comes from a link—however, note that for most inputs, you may
enter a value directly in the point’s property sheet (as an alternative source).
Note: A valid input is one with none of the following status bits set:
• down
• fault
• disabled
• null
• stale
If all 16 priority levels are evaluated without a valid input (and without an action at levels 1 and 8), then
the fallback value is used.
Note: You can configure the writable point’s “Fallback” property to be “null,” so that the point’s Out has a null
status in this condition. Depending on the specific control sequence and usage of the writable point, this
may be an effective solution.

NiagaraAX-3.x
3-24
User Guide
Chapter 3 – Data and Control Model About writable points
May 1, 2007 About minimum On and Off times

However, note that by default, a “set” action exists on any writable point, which writes directly to the
Fallback value. See “About set (Fallback) action” on page 3-4. If you want a writable point to always have
a Fallback of “null,” go to its slot sheet and set the “Hidden” config flag on the “set” slot. Otherwise, a user
can invoke a right-click command to set Fallback to any value. For more details, see “Modifying default
actions” on page 3-5.
Priority linking rules
When linking to the priority inputs of a writable object, you may notice these default rules:
• Only one link per input (level).
• Levels 1 and 8 are unavailable for links. If a BooleanWritable, level 6 is also unavailable.
Priority levels 1 and 8 are reserved for actions (emergency and override). See “About point actions”
on page 3-3. Priority level 6 in a BooleanWritable is reserved for minimum on/off times. See “About
minimum On and Off times” on page 3-25.
Note: Both rules vary from the r2 Niagara priority input scheme, where a single priorityArray input was used for
a writable object (AnalogOutput, BinaryOutput, and so forth). That input could be linked to multiple
priority type outputs, including those with duplicate priority levels and/or levels also used for object
commands (emergency and manual).
Priority level conventions
The 16 priority levels used by writable points are modeled after corresponding BACnet priority levels,
using the following conventions, from highest to lowest:
1. Emergency (Manual Life Safety)—Unlinkable input, but available as action (command).
2. Automatic Life Safety
3. User Defined
4. User Defined
5. Critical Equipment Control
6. Minimum On/Off (BooleanWritable meaning only, see “About minimum On and Off times”)
7. User Defined
8. Override (Manual Operator)—Unlinkable input, but available as action (command).
9. Demand Limiting
10. User Defined
11. Temperature Override
12. Stop Optimization
13. Start Optimization
14. Duty Cycling
15. Outside Air Optimization
16. Schedule
Note: Although priority levels are patterned after BACnet, there is no direct linkage to BACnet priorities, even
with BACnet writable proxy points. Priority inputs of all AX writable points are strictly a station-centric
NiagaraAX implementation.

About minimum On and Off times

Each BooleanWritable point has built-in timers to specify minimum on and/or minimum off times. The
respective point properties are “Min Active Time” and “Min Inactive Time.” Usage is optional, and both
properties work independently. Typical usage is to prevent short-cycling of equipment controlled by the
point.
Default property times for a BooleanWritable are all zeros (“00000h 00m 00s”), which effectively disables
a timer. In either property, you can specify any value needed using of a mix of hours (h), minutes (m), and
seconds (s) to enable that timer.
A minimum timer is triggered by a state change transition to active or inactive. This results in the new
state value being stored in the point’s priority array (at priority level 6) for the duration of that timer.
While a minimum timer is in effect, only input changes at a higher priority (5 or above) or an emergency
action can affect the Out value.
For example, a BooleanWritable point controls a fan, with related properties set as follows:
• Min Active Time:00000h 01m 30s
Specifies that once started, the fan must run at least 90 seconds.
• Min Inactive Time:00000h 03m 5s

NiagaraAX-3.x
3-25
User Guide
About composites Chapter 3 – Data and Control Model
Some composite examples May 1, 2007

Specifies that once stopped, the fan must remain stopped at 3 minutes, 5 seconds.
Starting with the fan stopped at schedule level (priority 16), if a user gives it a manual override on (priority
level 8), the fan will run for 90 seconds at priority level 6 (a higher level). After this period, the fan
continues running at the override 8 level for the duration of the override.
During the initial 90 seconds, a different override action (off or auto) will be ineffective—as the higher
priority level 6 remains in control. See “Priority level conventions” on page 3-25.
Once stopped, the point’s minimum off time will keep the fan off at priority level 6 for the specified
duration (in this example, 3 minutes and 5 seconds). During this period, only an emergency command or
input change at In2—In5 can effect further change.

About composites
Currently, a composite is something that Workbench allows you do to virtually any component in a
station, notably control points and objects, and even folders that contain control logic. When you make
a composite, you expose slots of child components in the glyph (object shape) of that parent (composited)
component. This can simplify linking and promote reuse of control logic.

Caution Composites have associated issues—see “Composite issues” on page 3-29. For now, you should avoid
making folder composites in your control logic, and instead use the composite feature only at the point/
object level to expose extension slots (if necessary). See example “Point-level composite” on page 3-26.

When you composite a component (say a control point, meaning its contents), you select specific slots in
child components (say, properties and/or actions of its extensions) to be “exposed” in the “shape” of that
point. Then, when looking at that point in the wire sheet view of its parent folder, you can see exposed
properties of children as linkable slots (and/or available actions).
Note: If you are familiar with Niagara r2, the composite concept is similar to “Bundle” or “Composite” objects,
only more flexible—you can expose slots in containers many levels down, for example. However, please see
the Caution above.

Some composite examples

A few simple examples of composites are included here, as follows:
• Point-level composite
• Folder-level composite
Point-level composite
Figure 3-28 shows a proxy NumericPoint representing a space temperature value that has two extensions:
• an alarm extension (OutOfRangeAlarmExt)
• a history extension (NumericInterval)

Figure 3-28 Property sheet of proxy point with two extensions

In this example, when another system-related BooleanWritable (representing the system fan) has a false
(Off ) status, it is desired that this temperature point be:
• disabled from alarming, and
• disabled from continued history collection

NiagaraAX-3.x
3-26
User Guide
Chapter 3 – Data and Control Model About composites
May 1, 2007 Some composite examples

To achieve these “disable” functions, you must link the controlling source fan out to a slot of each
extension (visible in point’s wire sheet view, but not in the parent wire sheet for the point itself ).
Furthermore, other kitControl objects needed. Without making a composite, the necessary objects and
links may appear as shown in Figure 3-29.

Figure 3-29 Proxy point example without composite

kitControl
Objects

Proxy Numeric
Point

Proxy point’s wire sheet

(with linked extensions

Notice that when looking at the proxy NumericPoint in the wire sheet of its parent folder, it is not
apparent that this point has linked extensions.
By making a composite of the NumericPoint (acting as the container for both the extensions plus the
additional kitControl objects) you can simplify reuse and clarify available links. Figure 3-30 shows the
now-composited NumericWritable linked to the controlling BooleanWritable, and the wire sheet view of
the NumericWritable that contains the needed kitControl objects.

Figure 3-30 Proxy point as composited container

In this example, the exposed input slots in the composite were renamed from “In” to “almInhib” and
“histStop” respectively, to clarify what each does. When looking at the Composite Editor for this example
NumericPoint, it appears as shown in Figure 3-31.

NiagaraAX-3.x
3-27
User Guide
About composites Chapter 3 – Data and Control Model
Some composite examples May 1, 2007

Figure 3-31 Composite Editor for example NumericPoint

Folder-level composite
Note: Please see the related Caution on page 26.
Figure 3-32 shows a simple example of three Math objects chained together, located in a “LogicA” folder.
Together, they perform a “Celsius to Fahrenheit” conversion. A NumericWritable is also shown linked to
the first Math object to test.

Figure 3-32 Simple example of folder before compositing

If this application was needed later, you could copy all 3 linked objects again and insert in another
(perhaps already crowded) wire sheet. However, the middle “Multiply” object reveals an intermediary
result that is distracting. Or, you could just create a new subfolder with only the 3 linked objects and then
link directly to the child objects as needed (however, it would not be obvious from the parent’s wire sheet
that links to children in that folder were established).
It would be better to “encapsulate” this into a single object with only a single “input” (degrees F) and single
“output” (degrees C). You can do something like this by compositing the parent container, in this example
folder “FolderA.”
In this case, you would want to delete the link from the test NumericWritable first, then open the
Composite Editor for the parent component FolderA (Figure 3-33). The Composite Editor lets you
expand the tree of all contained components and “expose” those items of interest.

NiagaraAX-3.x
3-28
User Guide
Chapter 3 – Data and Control Model About composites
May 1, 2007 Composite issues

Figure 3-33 Launching and using the Composite Editor

In this example, only the “In A” of the first math object and the “Out” of the third math object is selected
to be exposed. The Composite Editor provides a tree pane showing slots of points and objects (by clicking
the expand controls), and a slot is exposed by simply double-clicking it. Other controls in the editor are
available to rename, remove, reorder and reverse exposed items, but are not used here. (For more details,
see Making a composite.)
After clicking OK to perform the composite, the item composited (in this example, “LogicA”) shows
exposed slots when viewed in its parent’s wire sheet. Figure 3-34 shows the test NumericWritable now
linked to the composited LogicA folder.

Figure 3-34 Example LogicA folder showing exposed input and output

You could later reopen this folder’s Composite Editor and rename the exposed properties differently,
perhaps “inDegF” and “outDegC” (to make the purpose of the composited folder clearer). This would not
affect the three (child) math objects in any way.

Composite issues
Although composites can simplify linking and make understanding logic flow easier, they always
introduce performance issues. Perhaps the biggest issue is that once you link a dynamic value to a
composite, for example the “out” of a proxy point, it essentially “pinned” into the “subscribed” state. This
means that proxy point will always be polling (regardless of any other usage).
In addition, each item exposed in a composite represents a link, where each link consumes some small
amount of station resources. If used excessively, composites could noticeably reduce the total capacity of
the station.

NiagaraAX-3.x
3-29
User Guide
About composites Chapter 3 – Data and Control Model
Composite issues May 1, 2007

NiagaraAX-3.x
3-30
User Guide
 CHAPTER 4
Driver architecture
In any NiagaraAX station, one or more driver networks are used to fetch and model data values. Data is
modeled with proxy points, lower-tier components in that driver’s architecture. For more details, see
“About proxy points” on page 3-18.
To support a driver’s proxy points, the station must have that driver’s network architecture.
The following main topics apply to common driver architecture:
• What are networks?
• About Network architecture
• About the Driver Manager
• Common network components
• About the Device Manager
• Common device components
• Types of device extensions
• About the Point Manager
• About Histories extension views
• About Schedules extension views
• About the Niagara Network

What are networks?

Networks are the top-level component for any NiagaraAX driver. For drivers that use field bus commu-
nications, such as Lonworks, BACnet, and Modbus (among many others), this often corresponds directly
to a physical network of devices. Often (except for BACnet), the network component matches one-to-one
with a specific comm port on the NiagaraAX host platform, such as a serial (RS-232 or RS-485) port,
Lonworks FTT-10 port, or Ethernet port.
Note: A BacnetNetwork component is unique because it supports multiple logical BACnet networks, which
sometimes use different comm ports (e.g. if a JACE-4/5 with BACnet MS/TP, one or more RS-485 ports).
See the Bacnet Guide for more details.
Other “non field bus” drivers also use a network architecture, for example the Ndio (Niagara Direct Input
/ Output) driver has an NdioNetwork to interface to physical I/O points on the host JACE (Ndio applies
only to a JACE model with onboard I/O or with an attached hardware I/O board). Also, “database” drivers
also use a network architecture, for example the “rdbSqlServer” driver includes an RdbmsNetwork.
(Database drivers apply only to Supervisor or SoftJACE hosts.)

Where are networks located?

In any NiagaraAX station, all driver networks are located under the DriverContainer component in the
station’s database (“Drivers” in the root of the station, as shown in Figure 4-1).

NiagaraAX-3.x
4–1
User Guide
About Network architecture Chapter 4 – Driver architecture
Network component hierarchy May 1, 2007

Figure 4-1 DriverContainer in Nav tree

Note: Currently, all stations require a NiagaraNetwork. It may be used to model data in other NiagaraAX
stations. Also, it contains the NiagaraFoxService required for Workbench-to-station communications. For
more details, see “About the Niagara Network” on page 4-49.
Note: By convention, you should keep all driver networks located under the station’s Drivers container—it is a
special component with a view that provides some utility. See “About the Driver Manager” on page 4-4 for
more details.

About Network architecture

To represent any driver in a station database, a consistent “driver framework” using a network archi-
tecture is used. This includes the upper-tier parent network component, and one or more child device
components, each with device ext (extension) child components.
The following sections explain further:
• “Network component hierarchy”
• “About network components”
• “About device components”
• “About device extensions”

Network component hierarchy

Hierarchically, the component parentage is: network, device, device extensions, points (Figure 4-2).

Figure 4-2 Example driver architecture (Bacnet)

To simplify driver modeling, the New Station wizard automatically creates the necessary “Drivers”
container, complete with a NiagaraNetwork (and its required component slots).
• If engineering a JACE station, you invariably add additional driver networks, opening the driver’s
palette and copying the network-level component into Drivers. Or, you can use the New button in
the Driver Manager. Examples are a LonNetwork or BacnetNetwork.
• If engineering a Supervisor (PC) station, the NiagaraNetwork may be the only one needed. Option-
ally, you may add a “database” network (providing the PC host is licensed for it). And, if a PC host
licensed as a direct “integration Supervisor” (e.g. BACnet Supervisor), you may add a driver network
(e.g. BacnetNetwork) directly into its Drivers container.
Note: Regardless of host platform, in most cases the network component is the only item you need to manually
copy from that driver’s palette. After that, you use “manager views” to add child components like devices
and proxy points, even if programming offline.

NiagaraAX-3.x
4-2
User Guide
Chapter 4 – Driver architecture About Network architecture
May 1, 2007 About network components

This enforces the correct component hierarchy under that driver as you engineer, and helps coordinate
mechanisms used by the driver for communications. Exceptions to this rule are noted (as applicable) in
other documentation about NiagaraAX drivers.

About network components

A network component (“generically”: DriverNetwork) is the top-level component for any driver, and by
default has mandatory (frozen) component slots, such as:
• “Health” and other status properties—see “Network status properties” on page 4-6.
• AlarmSourceInfo—see “About network Alarm Source Info” on page 4-6.
• PingMonitor—see “About Monitor” on page 4-7.
• TuningPolicyMap—see “About Tuning Policies” on page 4-8.
Access these slots in the DriverNetwork’s property sheet (Figure 4-3).

Figure 4-3 Example BacnetNetwork property sheet

Note: Depending on the specific driver, there may be additional slots in the DriverNetwork. For example, if a field
bus network, there may be “PollScheduler” and/or “CommConfig” slots. Some of these may require proper
configuration before driver communications occur. See “Additional network components” on page 4-11.
The DriverNetwork is also the parent container for all device-level components. Devices list in tabular
format in the default view for that network, the DeviceManager. See “About the Device Manager” on page
4-12. You use the Device Manager to create and manage device components, and (if the driver provides
this), use discover features.

About device components

A device component (“generically”: DriverDevice) is a second-tier component for any driver, and by
default has mandatory (frozen) component slots, such as:
• “Health” and other status properties—see “Device status properties” on page 4-20.
Note: Depending on the driver type, a device typically has other properties. For example, if a device
under a field bus, it may have a “Device Address” property, or a similar properties. See “Driver-specific
device slots” on page 4-21. Or, starting in AX-3.2, a device may have a “Virtual” gateway slot. See
“Virtual Gateway component” on page 4-21.
• One or more device extensions—for example “Points” (DriverDevicePointExt). See “About device ex-
tensions” on page 4-4.
Typically, the property sheet is the default view for a device component—you can access device
properties, slots, and its extensions using the device’s property sheet (Figure 4-4).

Figure 4-4 Example BacnetDevice property sheet

The DriverDevice is also the parent container for all device extensions. As shown in Figure 4-5, device
extensions (e.g. “Points”) are visible under the device when you expand it in the nav tree.

NiagaraAX-3.x
4-3
User Guide
About the Driver Manager Chapter 4 – Driver architecture
About device extensions May 1, 2007

Figure 4-5 Example BacnetDevice extensions in Nav tree

About device extensions

A device extension is a child of a device, and represents some functionality of the device. Each extension
contains properties and other components. Device extensions are container components, often with one
or more special views. For more details, see “Types of device extensions” on page 4-24.
For example, in any of the field bus networks, each device has a Points extension, the parent container for
proxy points. The default view of the Points extension is the Point Manager, which you use to create and
manage proxy points. See “About the Point Manager” on page 4-28 for details.
Note: Device extensions are required (frozen) components of a device—you cannot delete them. They are created
automatically when you add a device to the station database. This varies from the “point extension” model,
where you individually add/delete extensions under control points and components.

About the Driver Manager

The Driver Manager is the default view for the DriverContainer (showing all networks) in a station.
Figure 4-6 shows an example Driver Manager for a JACE station.

Figure 4-6 Driver Manager

By default, each driver network lists showing its name, a type description, a real-time status field, whether
it is enabled, and a fault cause field (empty, unless the network is in fault).
Within the Driver Manager view, network-level operations are available:
• Double-click a network to go to its Device Manager view. See “About the Device Manager” on page
4-12.
• Right-click a network to see its popup menu, including available actions. Available actions will vary
by driver, but may include “Ping,” “Upload,” and “Download” as examples.
Buttons at the bottom of the Driver Manager provide other functions. See the section “Driver Manager
New and Edit” on page 4-4.

Driver Manager New and Edit

Buttons at the bottom of the Driver Manager include:
• New

NiagaraAX-3.x
4-4
User Guide
Chapter 4 – Driver architecture Common network components
May 1, 2007 Driver Manager New and Edit

• Edit
Note: New and Edit are also on the Driver Manager toolbar and the Manager menu.
New
The New button in the Driver Manager allows you to add a new driver network to the station. This is
equivalent to copying a driver network component from that driver’s palette. The New dialog provides a
selection list for network type, and also the number of networks to add (Figure 4-7).

Figure 4-7 New dialog in Driver Manager

Note: Currently, you are allowed to add multiples of any driver network, as well as any network type (regardless
of the station’s host platform). However, please understand that many networks should be “one-only” per
station, e.g. a NiagaraNetwork and BacnetNetwork. Also, consider that networks shown in the selection list
reflect only the modules available on your Workstation, and may not be present (or supported) on the target
NiagaraAX host.
Edit
The Edit button in the Driver Manager allows you to rename a selected network, or to set it to disabled
(Figure 4-8).

Figure 4-8 Edit dialog in Driver Manager

Caution Whenever you set a network to disabled (Enabled = false), the network component and all child driver
components (all devices, proxy points, etc.) change to disabled status. If a field bus driver, communications
routines like polling and device status pings also suspend. By default, disabled status color is gray text on
a light gray background.

This network-wide action may be useful for maintenance purposes. Note that Enabled is also individually
available at the device-level and proxy point-level, using the Edit button/dialog in the Device Manager or
Point Manager, respectively.
A disable at the device-level disables all child (proxy points), as well as polling to that points under that
device. A disable at the proxy-point level disables the single point.

Common network components

Each driver network contains common properties and other components. This section describes those
items.

NiagaraAX-3.x
4-5
User Guide
Common network components Chapter 4 – Driver architecture
Network status properties May 1, 2007

• Network status properties

• About network Alarm Source Info
• About Monitor
• About Tuning Policies
• Additional network components

Network status properties

Status
The Status property of a network indicates if the driver is capable of communications—for any
configured driver, network Status is typically “{ok}.” However, when adding some networks, the initial
Status may be fault, as shown in Figure 4-9. This might mean a communications port is yet unassigned,
or there is a port conflict.
Note: A fault status also occurs if the host platform is not properly licensed for the driver being used. If a network
fault, see the Fault Cause property value for more details.

Figure 4-9 Network status properties

Enabled
By default, network Enabled is true—you can toggle this in the property sheet, or in the Driver Manager
(by selecting the network and using the Edit button). See related Caution on page 5.
Health
Network Health contains historical properties about the relative health of the network in the station,
including historical timestamps.

About network Alarm Source Info

A network’s Alarm Source Info slot holds a number of common alarm properties (Figure 4-10). These
properties are used to populate an alarm if the network does not respond to a monitor ping. See “About
Monitor” for details on the monitor mechanism.

Figure 4-10 Example Network Alarm Source Info properties

NiagaraAX-3.x
4-6
User Guide
Chapter 4 – Driver architecture Common network components
May 1, 2007 About Monitor

Alarm Source Info properties work the same as those in an alarm extension for a control point. For
property descriptions, see “About alarm extension properties” on page 7-3.
Note: Each child device object also has its own Alarm Source Info slot, with identical (but independently
maintained) properties. See “Device Alarm Source Info” on page 4-20.

About Monitor
A network’s Monitor slot holds configuration for the “ping mechanism” used by the driver network. In
the network’s property sheet, expand the Monitor slot to see configuration (Figure 4-11).

Figure 4-11 Example Monitor properties

Monitor provides verification of the general health of the network, plus the network’s “pingables”
(typically, devices) by ensuring that each device is minimally “pinged” at some repeating interval.
• If a device responds to the monitor ping, device status is typically “ok,” and normal communications
routines to it (proxy-point polling, plus reads of device schedules, trends, etc. if supported by the
driver) proceeds normally. Typically, this applies even if the device returns an error response to the
ping, because this indicates that the device is “alive.”
• If a device does not respond to the monitor ping, it is marked with a down status—this causes normal
communications routines to that device to be suspended. Upon the next successful monitor ping to
that device, device status typically returns to “ok” and normal communications routines resume.
Note: Whenever successful communications occur to a device, that device component’s Health property is updated
with the current time. The network ping Monitor will only “ping” the device if the time of last health verifi-
cation is older than the ping frequency. Therefore, in normal operation with most drivers, the proxy point
polling mechanism actually alleviates the need for the monitor ping, providing that the ping frequency is
long enough. Also, in most drivers if a point poll request receives no response (not even a “null”) from a
device, a “ping fail” condition is immediately noted, without waiting for the monitor ping interval.
The following sections provide more Monitor details:
• Monitor properties
• Monitor considerations by driver
Monitor properties
The monitor ping properties are as follows:
• Ping Enabled
• If true, (default) a ping occurs for each device under the network, as needed.
• While set to false, device status pings do not occur. Moreover, device statuses cannot change
from what existed when this property was last true.
Note: It is recommended you leave Ping Enabled as true in almost all cases.
• Ping Frequency
Specifies the interval between periodic pings of all devices. Typical default value is every 5 minutes
(05m 00s), you can adjust differently if needed.
• Alarm On Failure
• If true (default), an alarm is recorded in the station’s AlarmHistory upon each ping-detected de-
vice event (“down” or subsequent “up”).
• If false, device “down” and “up” events are not recorded in the station’s AlarmHistory.
• Startup Alarm Delay
Specifies the period a station must wait after restarting before device “down” or “up” alarms are gen-
erated. Applies only if the Monitor’s property Alarm On Failure is true.

NiagaraAX-3.x
4-7
User Guide
Common network components Chapter 4 – Driver architecture
About Tuning Policies May 1, 2007

Monitor considerations by driver

The monitor mechanism used by a specific driver may have unique characteristics.
• For example, in a BacnetNetwork, any monitor ping is directed to the device’s BACnet “Device Ob-
ject,” and in particular, to its “System_Status” property. In this unique case, a received response of
“non-operational” is evaluated the same as getting no response at all!
• Or, in any Modbus network, when a monitor ping message is sent, it is directed to the device’s “Ping
Address,” which is configured by several properties in the ModbusDevice object.
Other drivers may have specific considerations for the Monitor ping mechanism. For more information,
refer to the “Device Monitor Notes” section within any NiagaraAX driver document.

About Tuning Policies

A network’s Tuning Policies holds one or more collections of “rules” for evaluating both write requests
(e.g. to writable proxy points) as well as the acceptable “freshness” of read requests from polling. In some
drivers (such as Bacnet), also supported is association to different poll frequency groups (Slow, Normal,
Fast). Tuning policies are important because they can affect the status of the driver’s proxy points.
In the network’s property sheet, expand the Tuning Policies (Map) slot to see one or more contained
Tuning Policies. Expand a Tuning Policy to see its configuration properties (Figure 4-12).

Figure 4-12 Example Tuning Policies Map (Bacnet)

Note: Some driver networks do not have Tuning Policies, for example an RdbmsNetwork for a database driver.
Also, the NiagaraNetwork has greatly simplified Tuning Policies.
By default, a driver’s TuningPoliciesMap contains just a single TuningPolicy (“Default Policy”). However,
you typically create multiple tuning policies, changing those items needed differently in each one. Then,
when you create proxy points under a device in that network, you can assign each point (as needed) to
the proper set of “rules” by associating it with a specific tuning policy.
As a simple example (under a BacnetNetwork), you could duplicate the default tuning policy twice,
naming the first copy “Slow Policy” and the second copy “Fast Policy.” Then, in each copy change the “Poll
Frequency” property from “Normal” to “Slow” or “Fast,” respectively. You would then have 3 available
(and different) poll frequency groups to pick from when you create and edit proxy points.
The following sections provide more Tuning Policy details:
• Tuning Policy properties
• Tuning Policy considerations by driver
Tuning Policy properties
Tuning Policy properties for typical field bus drivers are as follows:
• Min Write Time
Applies to writable proxy points, especially ones that have one or more linked inputs. Specifies the
minimum amount of time allowed between writes. Provides method to throttle rapidly changing val-
ue so that only the last value is written. If property value is 0 (default), this rule is disabled (all value
changes attempt to write).
• Max Write Time
Applies to writable proxy points. Specifies the maximum “wait time” before rewriting the value, in
case nothing else has triggered a write. Any write action resets this timer. If property value is 0 (de-
fault), this rule is disabled (no timed rewrites).

NiagaraAX-3.x
4-8
User Guide
Chapter 4 – Driver architecture Common network components
May 1, 2007 About poll components

• Write On Start
Applies to writable proxy points. Determines behavior at station startup.
• If true, (default) a write occurs when the station first reaches “steady state.”
• If set to false, a write does not occur when the station reaches “steady state.”
• Write On Up
Applies to writable proxy points. Determines behavior when proxy point (and parent device) transi-
tions from “down” to “up.”
• If true, (default) a write occurs when the parent device transitions from down to up.
• If set to false, a write does not occur when the parent device transitions from down to up.
• Write On Enabled
Applies to writable proxy points. Determines behavior when a proxy point’s status transitions from
“disabled” to normal (enabled). Note this status can be inherited globally if the parent device was set
to disabled (or network-wide if driver network was set to disabled).
• If true, (default) a write occurs when writable point transitions from disabled.
• If set to false, a write does not occur when writable point transitions from disabled.
• Stale Time
Applies to all proxy points.
• If set to a non-zero value, points become “stale” (status stale) if the configured time elapses without
a successful read, indicated by Read Status “ok.”
• If set to zero (default), the stale timer is disabled, and points become stale immediately when unsub-
scribed.
Note: By default, proxy point status “stale” is indicated by tan background color. In addition, stale
status is considered “invalid” for any downstream-linked control logic. For more details, see “About
“isValid” status check” on page 3-18.
• Poll Frequency
(May not exist in some drivers) Applies to all proxy points. Provides a method to associate the tuning
policy with one of 3 Poll Rates available in the network’s Poll Service: Fast Rate, Normal Rate, or Slow
Rate. The default poll frequency is “Normal.”
Note: Depending on the driver, there may be a single “Poll Service” (or “Poll Scheduler”) slot under
the network, or as in the case of a BacnetNetwork, a separate “Poll Service” for each configured port
(IP, Ethernet, Mstp) under its BacnetComm > Network container. The NiagaraNetwork uses subscrip-
tions instead of polling.
Tuning Policy considerations by driver
Tuning policies used by a specific driver may have unique characteristics. For example, under a Niagar-
aNetwork, its TuningPolicy has only two properties: Min Update Time and Max Update Time. For more
details, see “NiagaraNetwork component notes” on page 4-50.
Other drivers may have specific considerations for tuning policies. For more information, refer to the
“Tuning Policy Notes” section within any NiagaraAX driver document.

About poll components

Many driver networks use a single polling mechanism (Poll component, named “Poll Service” or “Poll
Scheduler”) adjusted at the network level in the station. In the case of a BacnetNetwork, a separate
BacnetPoll is used for each port under the BacnetStack’s Network component, as shown in Figure 4-13.
• Poll scheduler operation
• Poll component properties
Note: The Niagara Network does not use polling, but uses subscriptions only.

NiagaraAX-3.x
4-9
User Guide
Common network components Chapter 4 – Driver architecture
About poll components May 1, 2007

Figure 4-13 Example BacnetPollService

Poll scheduler operation

Regardless of driver type, the Poll Service provides a “poll scheduler” that operates in the same fashion
via an ongoing scan of four “buckets” to service “pollables” as follows:
• The poll scheduler allocates three “rate group” buckets, one for each rate group (Slow, Normal, Fast).
“Pollables” (mainly proxy points) are associated with one of three “rate” groups (Slow, Normal, Fast)
via either:
• assigned Tuning Policy in each point’s proxy extension (BacnetNetwork)
• assigned Poll Frequency in each point’s proxy extension (drivers other than Bacnet)
In the case of device objects, a Poll Frequency property is used to select the rate directly.
• A fourth “dibs stack” bucket is allocated for pollables that transition to a subscribed state. This may
be a “temporary subscription,” such as results when viewing unlinked proxy points (without alarm
or history extensions) in Workbench or a browser. Or, it may occur when a permanently subscribed
point is first polled (thereafter, it is no longer “dibs stack-polled”).
Priority of polling by the scheduler occurs in this fashion:
1. Dibs stack. When first subscribed, a pollable moves to the top of the dibs stack (first dibs). The poll
scheduler always polls the dibs bucket before doing anything else. The dibs stack is polled last-in,
first-out (LIFO). As long as entries are in the dibs stack, they are polled as fast as possible with no
delays.
2. When the dibs stack is empty, the scheduler attempts to poll the components in each “rate” bucket
using an algorithm designed to create uniform network traffic.
For example, if the fast rate is configured to 10 seconds and there are 5 components currently sub-
scribed in the fast bucket, then the scheduler will attempt to poll one component every 2 seconds.
Note: Every ten seconds the poll scheduler rechecks the buckets for configuration changes. So if a pollable’s config-
uration is changed from slow to fast, it takes at most ten seconds for the change to take effect.
Poll statistics are also updated every ten seconds. You can manually reset the statistics by issuing the Reset
Statistics action to the Poll Service (Figure 4-14).

Figure 4-14 Reset Statistics action of PollService

NiagaraAX-3.x
4-10
User Guide
Chapter 4 – Driver architecture Common network components
May 1, 2007 Additional network components

Poll component properties

Properties of the poll component for typical field bus drivers include four writable properties and various
read-only statistics properties, as follows:
•Poll Enabled
• If true (default), polling occurs for all associated pollables (proxy points, devices) under the net-
work component, or if a BacnetPoll, under that BacnetStack, Network, Port.
• While set to false, polling is suspended and further value updates from polling do not occur.
Note: PollService actions Enable and Disable allow access to this property, see Figure 4-14.
• Fast Rate
Target poll interval for pollables assigned to this rate group (default often is 1 second).
• Normal Rate
Target poll interval for pollables assigned to this rate group (default often is 5 seconds).
• Slow Rate
Target poll interval for pollables assigned to this rate group (default often 30 seconds).
Note: All remaining properties are read-only statistics properties.
• Statistics Start
Timestamp reflecting either the last manual reset of poll statistics, or if statistics have not been reset,
the first “steady state” time immediately following the last station restart.
• Average Poll
Average time spent in each poll.
• Busy Time
Percentage of time spent busy doing polls.
• Total Polls
Total number of polls made and time spent waiting for polls to execute.
• Dibs Polls
Total number of polls made processing the dibs stack.
• Fast Polls
Total number of polls processing fast queue.
• Normal Polls
Total number of polls processing normal queue.
• Slow Polls
Total number of polls processing slow queue.
• Dibs Count
Current and average number of components in dibs stack.
• Fast Count
Current and average number of components in fast queue.
• Normal Count
Current and average number of components in normal queue.
• Slow Count
Current and average number of components in slow queue.
• Fast Cycle Time
Average cycle time of the fast queue.
• Normal Cycle Time
Average cycle time of the normal queue.
• Slow Cycle Time
Average cycle time of the slow queue.
Note: Depending on driver, additional statistics properties may be present in a Poll component. For example, a
BacnetPoll has additional properties Device Count, Point Count, and Object Count. See the specific driver
document for unique Poll Service features or notes.

Additional network components

Depending on the driver type, a network typically includes other components that define communica-
tions settings. Access these components on the property sheet of the network. More details are in the
following subsections:
• About communication components
• About driver-specific properties

NiagaraAX-3.x
4-11
User Guide
About the Device Manager Chapter 4 – Driver architecture
Additional network components May 1, 2007

About communication components

Communication components contain properties and possibly other components that configure and
represent communications ports, or other protocol layers. These components will vary from driver to
driver. Often, you must configure (or verify) these components to allow online operations.
For example, the NiagaraNetwork contains the NiagaraFoxService, a BacnetNetwork contains a Bacnet-
Stack (Bacnet Comm), a LonNetwork contains LonCommConfig (Figure 4-15).

Figure 4-15 LonNetwork’s LonCommConfig component

See the driver document for specific details on configuring a network’s communications components.
About driver-specific properties
Depending on the driver, other specific properties (or even component containers) may be found in the
network component’s property sheet.
For example, the NiagaraNetwork has container components Fox Service and History Policies, a
ModbusAsyncNetwork contains a number of properties for timeouts and byte-order conventions, and a
LonNetwork contains a LonNetmgt component with various child properties (Figure 4-16).

Figure 4-16 LonNetwork’s LonNetmgmt component

For more details see “About the Niagara Network” on page 4-49, or the corresponding driver document
for driver-specific properties and components of a network.

About the Device Manager

The Device Manager is the default view for any network container (for a NiagaraNetwork only, this view
is called the Station Manager). The Device Manager is a table-based view, where each row represents a
unique device (Figure 4-17). When building a network in the station, you use this view to create, edit, and
delete device-level components.

NiagaraAX-3.x
4-12
User Guide
Chapter 4 – Driver architecture About the Device Manager
May 1, 2007 Device New Folder and New

Figure 4-17 Example Device Manager (BacnetDeviceManager)

Following station configuration, this view provides a status and configuration summary for all devices
networked using that driver. The “Exts” column provides quick double-click access to device extensions,
such as Points for proxy points, Schedules for imported schedules, and so forth (see “Types of device
extensions” on page 4-24 for details). You can also use it to issue actions to selected devices, such as “ping,”
upload, and so forth.
At the bottom of the view, buttons “New Folder” and “New” let you create new device folders and devices
in the station database. The “Edit” button lets you edit one or more selected devices in the station
database. If the driver supports online “device learning,” buttons “Discover,” and “Match” are also
typically available. Finally, additional buttons may be available, depending on the driver.
For more details, see:
• Device New Folder and New
• Device Edit
• About Device Discover, Add and Match (Learn Process)
• Manager table features

Device New Folder and New

Buttons New Folder and New exist in the Device Manager view of a device-level component under any
driver network. Use of New Folder is optional. Typically, you use New only if the driver does not support
online discovery, or if you are programming offline.
Note: New Folder and New are also on the Device Manager toolbar and the Manager menu.
New Folder
The New Folder button in the Device Manager adds a special “DeviceFolder” component you can use
to organize devices. This is equivalent to copying that same component from that driver’s palette. A
Name dialog lets you name the folder before it is created (Figure 4-18).

Figure 4-18 Example New Folder dialog in Device Manager

When you click OK, a new DeviceFolder component is added under the network.
Note: A driver’s DeviceFolder component is different than a “normal” Folder component, as it provides that
driver’s Device Manager view by default (just like the parent network component). Also, an “All Descen-
dants” command is available from the root Device Manager, which allows you to see all devices in the
network.

NiagaraAX-3.x
4-13
User Guide
About the Device Manager Chapter 4 – Driver architecture
Device New Folder and New May 1, 2007

All Descendants
When in the Device Manager of a device folder, it is “unaware” of devices in other device folders (or in the
root of the network component). However, from the root Device Manager view (of the network), you can
“flatten” the folder structure to view all devices by selecting it from the Manager menu (Figure 4-19) or
by simply clicking the “All Descendants” tool on the toolbar (Figure 4-20).
Note: Be aware that in a large network, with many device folders and devices, using the all descendants feature
may decrease performance. This might result from so many devices/points being subscribed.

Figure 4-19 Manager menu “All Descendants” command

Figure 4-20 Device Manager “All Descendants” tool on toolbar

Note: If you are using device folders, and you click on a table column to resort devices, please be aware that any
device-to-device folder organization is lost during that view. However, you can always see contents of device
folders clearly in the Nav tree, and again when returning to the Device Manager view from another view.
New
The New button in the Device Manager allows you to add a new device component to the station. This is
equivalent to copying a device component from that driver’s palette. The New dialog provides a selection
list for device type, and also the number of devices to add (Figure 4-21).

Figure 4-21 Example New dialog in Device Manager

When you click OK, a new device-level component is added under the network. You usually need to edit
specific details for each new device, including addressing parameters for communications.

NiagaraAX-3.x
4-14
User Guide
Chapter 4 – Driver architecture About the Device Manager
May 1, 2007 Device Edit

Device Edit
In the Device Manager view, you can edit any device component in the station database by simply double-
clicking it. (Editing does not apply to device folders.)
Edit
The Edit dialog appears with the device listed (Figure 4-22).

Figure 4-22 Example Edit dialog in Device Manager (single device)

Note: The Edit dialog for a device component only shows some of the device component’s properties. Typically,
these are key properties required for communications, and will vary among drivers (to access all properties
of the device component, go to its property sheet).
When a single device is selected in the Edit dialog, you can edit any property except Type (it was fixed when
you added the device). Included is the ability to edit the Name of the device in the station. This is equivalent
to the right-click Rename command on the component.
The following related topics also apply:
• Device “gang” edits
• Manager table features
Device “gang” edits
The Edit button in the Device Manager allows you to edit one or more device components in the station
in a single dialog. Before clicking Edit, use standard Windows keyboard controls to highlight (select)
multiple devices (e.g. hold down Ctrl key and click desired devices).
Note: Edit is also available on the Device Manager toolbar and the Manager menu.
The “gang” edit feature is useful for making the same change in multiple (selected) devices. For example,
as shown in Figure 4-23, you can change “Poll Frequency” in multiple devices at the same time (versus
editing this individually).

NiagaraAX-3.x
4-15
User Guide
About the Device Manager Chapter 4 – Driver architecture
About Device Discover, Add and Match (Learn Process) May 1, 2007

Figure 4-23 Example “gang edit” in Edit dialog in Device Manager

When you have the Edit dialog open with multiple devices, you can also click on select ones to make
individual edits (e.g. Name, or any other editable property), during the same dialog session where you
made “gang” property edits. When you click OK, all the changes are applied to the device components as
made during your Edit session. For more details, see “About gang edits.”
Note: When you have multiple devices selected in the Edit dialog, properties that must be unique (such as Name)
are automatically unavailable (dimmed). However, note that some properties that typically should be
unique (often address properties) may still be available for “gang edit,” as this rule is not automatically
enforced. Typically, when editing these properties, you should verify only a single device component (row)
is highlighted in the table.

About Device Discover, Add and Match (Learn Process)

Online “device learns” are possible using the Device Manager for many drivers, for example the Niagar-
aNetwork, BacnetNetwork, LonNetwork, and NdioNetwork. Whenever available, this method is the
easiest way to accurately add device components to the station database.
Note: With the exception of a “Quik Learn” option in a LonNetwork, any device learn in NiagaraAX is a two-step
process where you first:
1. Discover device candidates for inclusion in the station database.
2. Select and Add from those candidates, creating device components in the network.
If you already added devices using New, you can also Match candidates to existing devices. For more
details see “Match (Device)” on page 4-18.
The Device Manager reinforces this process by providing two separate panes in the view whenever you enter
“Learn Mode.” See “About Learn toggle” on page 4-16.
About Learn toggle
Any driver that offers online “learns” of devices, points, and possibly schedules and log data (histories)
provides specialized “Manager” views. Any such view offers both a two-pane view (Learn Mode) and a
single-pane view (Database only).
At any time, you can toggle between Learn Mode and the single-pane (Database) view by clicking the
Learn Mode tool in the toolbar (Figure 4-24), or using the Learn Mode command in the Manager menu.
Also, note that the Discover tool (binoculars) is next to the Learn Mode tool.

Figure 4-24 Learn Mode toggle tool in any Manager

Note: Whenever in Learn Mode of any Manager view (DeviceManager, PointManager, and so forth) you can drag
the border between the two panes to resize, as necessary.

NiagaraAX-3.x
4-16
User Guide
Chapter 4 – Driver architecture About the Device Manager
May 1, 2007 About Device Discover, Add and Match (Learn Process)

Discover
The Discover button is available in the Device Manager only if the driver supports online discovery.
When you click Discover, the Device Manager view splits into two panes (Learn Mode), and at the same
time typically launches a discovery “job” (Figure 4-25).

Figure 4-25 Discover splits Device Manager view

Note: In some drivers, an intermediate dialog may appear before the discovery job begins. For example, in a
discover for a BacnetNetwork, a “Configure Device Discovery” dialog allows you to limit possible ranges of
devices, before discovery begins. For more details, see the Bacnet Users Guide.
The two panes in the Device Manager operate as follows:
• Discovered (top pane)
Lists devices discovered on the driver’s network, as candidates. Any device found that already exists
in the station database appears “ghosted” (faintly listed). A job “progress bar” is also included on top
of the Discovered pane.
Note: A Cancel button is available during a discovery job. If needed, use it to stop discovery.
• Database (bottom pane)
Lists devices and device folders that are currently in the station database.
Add
The Add button is available in the Device Manager in Learn Mode when you have one or more devices
selected (highlighted) in the top Discovered pane. When you click Add, an Add dialog appears that allows
you to edit items before the device component(s) are created in the station database (Figure 4-26).

Figure 4-26 Add dialog from Add button in Device Manager

NiagaraAX-3.x
4-17
User Guide
About the Device Manager Chapter 4 – Driver architecture
Match (Device) May 1, 2007

The Add dialog is nearly identical to the device Edit dialog, but allows you to edit Type as well as other
device properties. Often, device address properties in the Add dialog already have acceptable values for
operation (otherwise, communications to that device would not have occurred). Often, you change only
Name, unless you know other settings you wish to change. You can always Edit the device component(s)
after you click OK and add them to your station.
Note: When you have one or more devices selected in the top Discovered pane, an Add tool is also available on
the toolbar (“plus” symbol), as well as a command in the Manager menu. Also, you can simply double-click
a discovered device to bring it up in the Add dialog.

Match (Device)
Device Match is a feature that may be useful when you have an application replicated many times at the
device level, or if you have programmed offline using the New device feature.
• In the first case (replicated device application), you could discover and add one typical device, and
complete further engineering under it (learning and adding proxy points, point extensions, creating
other control logic, adding Px views, including all self-contained links and bindings).
Then, you could duplicate that typical device component (choosing Duplicate in its right-click
menu) for as many identical devices as exist. The Match feature now allows you to match each du-
plicated device component to a unique discovered device, saving engineering time. This repopulates
the necessary properties of the duplicated device object with the correct values from the discovered
device.
• In the second case (offline programming) where a connection to the actual device network is un-
available, you can manually add New devices and begin station engineering of a driver network. Typ-
ically, most component creations under a driver network are possible (including all levels) using the
New feature in the various “manager” views (Device Manager, Point Manager, other device exten-
sion managers). Or, you can add saved applications (from the device level on down) and edit as nec-
essary. Then, when online with the driver network later, you could use Match to “sync” to existing
components (device-level, proxy points, and so forth).
The Match button in the Device Manager becomes available when in Learn Mode, and you have:
1. Selected one device candidate in the top (Discovered) pane.
2. Selected one existing device component in the bottom (Database) pane.
Note: In this case, the toolbar also has an available Match tool, and the Manager menu has a Match command.
When you click Match, the Match dialog appears, as shown in Figure 4-27.

Figure 4-27 Match dialog example in Device Manager

Note: Match is strictly a “one-to-one” function for “discovered-to-database”—note that it is unavailable any time
you have multiple items selected either in either the top or bottom pane.
The Match dialog is nearly identical to the single-device Edit dialog, and typically provides the
“discovered” device address values. Often, most properties in the Match dialog already have acceptable
device address values required for operation (otherwise, communications to the discovered device would
not have occurred). You can always Edit the device component after you click OK and add it to your
station.

NiagaraAX-3.x
4-18
User Guide
Chapter 4 – Driver architecture Common device components
May 1, 2007 Manager table features

Manager table features

As with other table-based views in Workbench, manager views of various components under a driver’s
network provide common features that can be useful (see “About table controls” for a general overview).
These features apply to various component views found throughout a station’s driver architecture, for
example, the Driver Manager, Device Manager, Point Manager, History Import Manager, and so on.
Of particular utility are the following table features:
• Table options menu
• Column resorting
Table options menu
Use the table options drop-down menu (small control in upper table right, as shown in Figure 4-28) to
perform any of the following:

Figure 4-28 Table options menu in Device Manager

• Reset Column Widths

Useful if you manually changed widths of columns, and now some contents are hidden (even after
scrolling). The reset restores all columns to widths that accommodate contents.
• Export
Produce the standard Export dialog, where you can select exporting the table to PDF, text, HTML,
or CSV (comma separated variable). See “About table exports” for more details.
• select or clear columns for display
Depending on the driver, a certain “default” collection of columns is pre-selected for display in the
Manager view. You can change that by checking or clearing column headings.
Column resorting
Click on any column header to toggle the table sort between ascending (first click) and descending
(second click). The current table sort is indicated by a small triangle in the sorting column.

Common device components

Each device component has some number of required (frozen) slots and properties, which will vary by
driver. However, the following categories of components and slots are typical to most device-level
components:
• Device status properties
• Device Alarm Source Info
• Device address properties
• Driver-specific device slots
Also, a device component has one or more device extensions, which are visible when you expand the
device in the Nav tree. For more details, see “Types of device extensions” on page 4-24.
Note: Starting in AX-3.2, some drivers may implement “virtual components,” which typically adds a frozen
“Virtual” gateway slot under the device component. See “Virtual Gateway component” on page 4-21.

NiagaraAX-3.x
4-19
User Guide
Common device components Chapter 4 – Driver architecture
Device status properties May 1, 2007

Device status properties

Status
The Status property of a device indicates whether it is communicating—good status is “{ok}” (no status
flags). However, if using New to add a device, initial Status may be down or fault, as shown in Figure 4-
29. This could mean device address properties are yet unassigned, or are misconfigured.
Note: If a device status fault, see the Fault Cause property value for more details.

Figure 4-29 Device status properties

Status of devices is verified by successful polling, or the device status “ping” as configured in the network
component’s Monitor configuration. See “About Monitor” on page 4-7.
From the Device Manager view, you can also right-click a device, and from the popup menu select
Actions > Ping to manually verify communications.
Depending on conditions, a device may have one of various status flags set, including fault or disabled, or
others in combination, such as down, alarm, stale, and/or unackedAlarm. In the Device Manager, non-
ok status in indicated for any device by row color other than white.
Enabled
By default, device Enabled is true—you can toggle this in the property sheet, or in the Device Manager
(by selecting the device and using the Edit button). See Caution on page 5.
Health
Device Health contains historical properties about the last successful message received from the device,
including timestamps.

Device Alarm Source Info

A device’s Alarm Source Info slot holds a number of common alarm properties (Figure 4-10). These
properties are used to populate an alarm if the device does not respond to a monitor ping. This ping is
configured at the network level—see “About Monitor” on page 4-7.

Figure 4-30 Example Device Alarm Source Info properties

NiagaraAX-3.x
4-20
User Guide
Chapter 4 – Driver architecture Common device components
May 1, 2007 Device address properties

These properties work the same as those in an alarm extension for a control point. For property descrip-
tions, see “About alarm extension properties” on page 7-3.
Note: Each parent network component also has its own Alarm Source Info slot, with identical (but independently
maintained) properties. See “About network Alarm Source Info” on page 4-6.

Device address properties

Depending on the driver, a device-level component typically has one or more address type properties,
accessible from the device’s property sheet. For example, a BacnetDevice has an Address property with 3
separate fields (Figure 4-31).

Figure 4-31 Example device address properties

In the case of a Lon device (DynamicDevice) various address parameters are stored under a DeviceData
component, itself visible when you expand the device in the Nav tree. For more details on device-level
address properties, see the specific driver document.
Poll Frequency
Common to most devices is a Poll Frequency property, typically located below device address properties.
It provides a drop-down menu to select among 3 poll frequencies, as configured in the network’s Poll
Service. For more details, see “About poll components” on page 4-9.

Driver-specific device slots

A device-level component typically has slots unique to that driver, accessed on its property sheet. For
example, a Lon device has a large collection of nv slots (network variables nvi, nvo, and nci), each as an
expandable container holding numerous values. A BacnetDevice holds a number of properties that define
Bacnet “services” that it supports. For details, see the specific driver document.

Virtual Gateway component

Starting in AX-3.2, the ability for a device-level component to have a Virtual gateway child was
added. This is in addition to the “standard” collection of slots for device-level components (See “About
device components” on page 4-3.).
Note: Baja virtual components are not specific to just drivers. However, the original need for virtual components
(which are transient, and do not permanently reside in a station’s database) and a special “gateway”
component to access them, came about from driver “use case needs.” It is possible that other applications
for virtual gateways (and virtual components) may evolve in future builds of NiagaraAX.
In the NiagaraAX driver architecture, a device’s virtual gateway provides access to “virtual components”
in the station’s “virtual component space,” specific to that device. Currently, only the BACnet driver has
implemented virtual components.
About virtual component spaces
A NiagaraAX station contains object “types,” each within a defined “space” at a top level (Figure 4-32).

Figure 4-32 Top level object spaces

Object types in these spaces are:

• Components — in the component space under a Config node (regular component space).
• Files — in the files space under a Files node.
• Histories— in the histories space under a History node.

NiagaraAX-3.x
4-21
User Guide
Common device components Chapter 4 – Driver architecture
Virtual Gateway component May 1, 2007

A station uses these objects when running, and when it is stopped they persist—components in the
station’s database (config.bog), files in the station’s directory, and histories within the history database.
Virtual component spaces are different, in the following ways:
• There can be multiple virtual component spaces—each belongs to a different virtual gateway, which
are specialized components in the station’s component space (under Config).
• A virtual component space is a mapping of virtual components, organized in a tree fashion, created
at runtime when its virtual gateway is “started” (accessed).
• Virtual components are transient components created in the station only when needed. When no
longer necessary (i.e. become unsubscribed) they are automatically removed in the running station.
When the station is stopped, virtual components do not exist. This permits monitoring applications
in cases where normal proxy points would use too many resources.
• Virtual components have limitations, and should not be confused with other components (such as
proxy points). For example, links to and from virtual components, use of point extensions (history,
alarm, etc.), and typical copy/paste operations are not supported.
About virtual gateways
Virtual gateways reside in the station database, along with other components. Each virtual gateway
provides the link between the normal component space and its own virtual components. In the initial
“driver application” of virtual components, each device component in a driver network has its own virtual
gateway, as shown in Figure 4-33 for a BacnetDevice in the AX-3.2 bacnet palette.

Figure 4-33 One virtual gateway per device

This is a logical division of gateways (separating data by its source device). However, this is not to say that
future virtual component applications will always use this method of hierarchy for virtual gateways.
Gateway activation Unlike with a device’s extensions, there is no special view for a virtual gateway—you
simply double-click it to access the gateway’s property sheet, or expand it in the Nav tree. When you do
this for a device’s virtual gateway, a “driver-specific” call is made to the device to gather data, where the
results appear as child virtual components.
In the case of the BACnet driver, expanding a virtual gateway fetches “an object list,” where each BACnet
object in the device appears as a virtual component (slot) under the gateway. See Figure 4-34.

Figure 4-34 BacnetVirtualGateway functions as BACnet object list

As shown in Figure 4-35, you can expand any virtual component to see its “virtual property sheet,”
resulting in another incremental call to the device.

NiagaraAX-3.x
4-22
User Guide
Chapter 4 – Driver architecture Common device components
May 1, 2007 Virtual Gateway component

Figure 4-35 Property sheet of BacnetVirtualComponent

This “virtual view” property sheet reflects dynamic values, noting that virtual components are transient
vs. persisted components—meaning they are dynamically created (and subscribed) only when accessed,
and are not stored in the station database.
Note: Virtual components have limitations when compared with other components (such as proxy points). For
example, links to and from virtual components, use of point extensions (history, alarm, etc.), and typical
copy/paste operations are not supported.
Property sheet access of virtual components (as shown in Figure 4-35) can provide utility when config-
uring or commissioning a device, especially for “one time” modification of parameters (assuming that the
device permits writes). For example, you could quickly adjust an alarm limit setting, whereas (otherwise)
you would typically have to create a specific proxy point in the station database to do this.
The other common application for virtual components is for real-time monitoring of values in Px views
(graphics). See the next section “Virtual components in Px views” for more details.
Virtual components in Px views The AX-3.2 and later feature of “virtual components” provides utility
when reviewing and making “one-time” property value adjustments for objects in devices, as described
in “Gateway activation” on page 4-22. In addition, virtual components can be used to show real-time
values in Px views—at least when the built-in features of proxy points (right-click actions, status color-
ation) are not required.
Note: A virtual gateway cannot have its “own” Px view, but you can use its child virtual components in Px views
for other components, for example on the device component itself, or its Points extension, and so on.
The only persisted (permanent) record of such a virtual component is its ord in the Px binding to it, which
uses a “Virtual ord syntax” that includes the virtual gateway within it (and activates it at runtime). This
ord is automatically resolved when you drag a virtual component onto the Px page, and make your
property selection in the popup Px “Make Widget” dialog, as shown in the example in Figure 4-36.

Figure 4-36 Dragging virtual component into Px editor view, with resulting Make Widget popup

NiagaraAX-3.x
4-23
User Guide
Types of device extensions Chapter 4 – Driver architecture
Virtual Gateway component May 1, 2007

The selected property in the virtual component displays in the Px widget, for example in a “field editor”,
as shown in Figure 4-37.

Figure 4-37 BacnetVirtualComponent in Px view

Note: For complete details on Px views and widget editing, see “About Px Editor” on page 8-5.
Virtual ord syntax The general syntax for a “virtual ord” uses a specialized form as follows:
<ord to VirtualGateway>|virtual:/virtualPath
where virtualPath represents some hierarchy of virtual components and child properties.
For example, for BacnetVirtualComponents, the general virtual path syntax is:
<ord to VirtualGateway>|virtual:/objectType_Instance/propertyName
Or in the special case of an arrayed property:
<ord to VirtualGateway>|virtual:/objectType_Instance/propertyName/elementN
where N is the property array index.
For specific virtual ord details, refer to the corresponding driver document section about “Virtual Points”.

Types of device extensions

When you create a device-level component (New, Add, or simply drop from the driver’s palette), you may
notice that it has default children, collectively called device extensions. Device extensions group various
functions of a device.
Note: For any device, its extensions are typically visible both in the Nav tree and in the Device Manager view
(Figure 4-38), providing double-click access to each extension’s default view. One exception to this is for an
AX-3.1 or later AxSupervisor, in its Station Manager view of the NiagaraNetwork, where special “provi-
sioning” extensions for NiagaraStations do not appear. See “NiagaraStation component notes” on page 4-
55 for related details.

Figure 4-38 Device extensions in Nav tree and Device Manager

Perhaps the most important of all device extensions is the Points extension—the container for all proxy
points (representing data originating from that device).
Types of Device extensions include:
• Points extension—see “About the Points extension” on page 4-25.
• Histories extension—see “About the Histories extension” on page 4-25.

NiagaraAX-3.x
4-24
User Guide
Chapter 4 – Driver architecture Types of device extensions
May 1, 2007 About the Points extension

• Alarms extension—see “About the Alarms extension” on page 4-26.

• Schedule extension—see “About the Schedules extension” on page 4-27.

About the Points extension

A device’s Points extension (or simply Points) serves as the top parent container for real-time data values
originating from that device.

Figure 4-39 Points under a Lon device

These values are “proxied” using NiagaraAX control points, or proxy points. Values can be both read from
data values in that device, and written to value stores in the device. For details see “About control points”
on page 3-1 and “About proxy points” on page 3-18.
Note: You create all proxy points using the Point Manager view of Points—simply double-click Points under any
device component, or right-click Points and select Views > Point Manager. See “About the Point
Manager” on page 4-28 for more details.

About the Histories extension

Not all drivers have devices with a HistoryDeviceExt—notably, this exists only if the driver protocol (or
device) provides local data logging. Currently, this device extension exists under components NiagaraS-
tation, ObixClient, R2ObixClient, and BacnetDevice (under a BacnetDevice it is named “Trend Logs”).

Figure 4-40 Histories device extension (NiagaraStation)

A device’s Histories extension serves as the parent container for history descriptors—components that
specify how history-type collections (log data) are imported or exported. By default, it also contains a
Retry Trigger, see “About the Retry Trigger” on page 4-26.
Note: Creating history import and history export descriptors is how you save a Niagara history to a different
location (station) from where it originated. In a typical application, this is considered archiving. For
example, an originating history (with a limited record count) may be in a JACE station. If imported to a
supervisor station, its history import descriptor can be configured such that the imported history in the
supervisor has “unlimited” record capacity. The JACE history can run collecting only the last 500 records,
while the imported history in the supervisor will collect all (unlimited) records.
The difference between a history import and history export are as follows:

NiagaraAX-3.x
4-25
User Guide
Types of device extensions Chapter 4 – Driver architecture
About the Retry Trigger May 1, 2007

• Import
An imported history appears in the local station as a Niagara history, where data is effectively
“pulled” from a remote source device.
• If configured by a history import descriptor under Histories of a NiagaraStation device, the source
is another Niagara history in that remote station.
• If configured by a history import descriptor under Trend Logs of a BacnetDevice, the source is a
BACnet Trend Log object residing in that BACnet device.
• Export
(NiagaraStation only) An exported history is a Niagara history that exists in the local station, and is
configured by a history export descriptor to “push” its data to a remote NiagaraStation. This adds it
to the histories in that remote station.
Note: Under a BacnetNetwork, the single “LocalDevice” component (that represents station data
exported to BACnet) has a special view on its child Export Table component that permits
exporting station histories as BACnet Trend Log objects. See the BACnet Guide section “Bacnet server
configuration overview” for more details.
You create history import descriptors and export descriptors under the Histories extension of a device
using separate views. For details, see “About Histories extension views” on page 4-37.

About the Retry Trigger

By default, device extensions Histories and Schedules contain a “Retry Trigger”-named component,
appearing in the Nav tree but not in any Manager view (Figure 4-41).
Note: Retry Trigger is unique in that it requires no linking of its output for operation.

Figure 4-41 Retry Trigger under device Histories extension

Upon any unsuccessful execution of a history import/export descriptor or schedule import extension/
schedule export descriptor contained in that same device extension, the Retry Trigger defines subsequent
“retries” that will automatically occur upon the interval period defined (default value is 15 minutes). This
continues until successful execution occurs.

About the Alarms extension

Not all drivers have devices with an AlarmDeviceExt (Alarms)—notably, this exists only if the driver
protocol (or device) provides for local (native) alarming. Currently, only a device component under a
NiagaraNetwork (station), BacnetNetwork, or ObixNetwork has a child Alarms extension.
Alarms extension properties specify how alarms from that device are mapped into the station’s own
alarm subsystem, plus provide status properties related to alarm sharing. Unlike other device extensions,
there are no special views, nor does the extension contain other special components.
Alarms extension properties
The following properties apply:
• Alarm Class
(Available only if checkbox “Use Existing Alarm Class” is cleared) Provides selection list of local
AlarmClass, from which you select one to use for all alarms received from this device.
• Use Existing Alarm Class
(checkbox, applies to NiagaraStation only)
• If enabled (default), alarms from this remote station are routed to any “matching” AlarmClass,
that is, one with identical name as the “alarmClass” field in each alarm record. If no local
“matching” AlarmClass is found, the station’s default AlarmClass is used.
• If cleared, all received alarms are routed to the single local AlarmClass specified.

NiagaraAX-3.x
4-26
User Guide
Chapter 4 – Driver architecture Types of device extensions
May 1, 2007 About the Schedules extension

• Last Received Time

Timestamp when last alarm from this station was received. This is configured remotely, either in the
sending Niagara station or the BACnet device.
Note: Remaining properties apply to the Alarms extension under a NiagaraStation component only
(are not available in Alarms extension under a BacnetDevice).
• Last Send Time
Timestamp when last local alarm was routed to this device. This is configured under the local sta-
tion’s AlarmService with a corresponding StationRecipient or BacnetDestination component linked
to one or more AlarmClass components).
• Last Send Failure Time
Timestamp when last local alarm routed to this station could not be sent.
• Last Send Failure Cause
Text string describing failure cause routing local alarm to this station.

About the Schedules extension

Not all drivers have devices with a ScheduleDeviceExt (Schedules)—notably, this exists only if the driver
protocol (or device) provides local event scheduling. Currently, this device extension exists only under
components NiagaraStation and BacnetDevice.

Figure 4-42 Schedules device extension (NiagaraStation)

A device’s Schedules extension is the parent container for imported schedules—Niagara schedule compo-
nents with a ScheduleImportExt. Events in an imported schedule are obtained from that device, and are
read-only (often called “slave schedules”). By default, the Schedules extension also contains a Retry
Trigger, see “About the Retry Trigger” on page 4-26.
The Schedules extension can also contain schedule export descriptors. These correspond to local station
schedules that are exported (“pushed”) to that remote station (often called “master schedules”). A
schedule export descriptor is automatically created whenever a local schedule is “imported” into a remote
station.
The difference between a schedule import and schedule export are as follows:
• Import
An imported schedule appears in the local station as a Niagara schedule, where read-only schedule
events are configured/adjusted in a remote source device.
• If under a NiagaraStation device, the source is a Niagara schedule in that remote station.
• If under a BacnetDevice, the source is a BACnet Schedule or Calendar object residing in that BACnet
device. That object’s data is now modeled as a Niagara schedule component.
• Export
This is a Niagara schedule in the local station that is exported into a remote station (NiagaraNet-
work) or BACnet Schedule or Calendar object (BacnetNetwork). A resulting schedule export de-
scriptor allows configuration of a “push” mechanism to keep event configuration synchronized in
the remote device.
Note: Under a BacnetNetwork, the single “LocalDevice” component (that represents station data
exported to BACnet) has a special view on its child Export Table component that permits “exposing”
Niagara schedule components in the station as either a BACnet Schedule object or Calendar object.
For details, see the Bacnet Users Guide.
You create imported schedules under a device’s Schedules extension using an Import Manager view. A
separate Export Manager view provides access to schedule export descriptors. For details, see “About
Schedules extension views” on page 4-44.

NiagaraAX-3.x
4-27
User Guide
About the Point Manager Chapter 4 – Driver architecture
Points New Folder and New May 1, 2007

Note: Schedule components local to the station can reside anywhere under the station’s Config hierarchy and be
imported by one or more other stations. As this occurs, a schedule export descriptor is automatically
created under the NiagaraStation component that represents the remote station (and is located in its
Schedules container). On the other hand, if you import a schedule from another NiagaraStation or Bacnet-
Device, it must reside in that device’s Schedule container. Imported schedules are always under a specific
device.

About the Point Manager

The Point Manager is the default view for the Points extension under any device object. Like other
manager views, it is table-based (Figure 4-43). Here, each row represents a proxy point (or a points folder)
under Points.

Figure 4-43 Point Manager under a BacnetDevice

When building a network in the station, you use this view to create, edit, and delete proxy points in the
station database. See “About proxy points” on page 3-18.
Following station configuration, this view provides a status summary for proxy points. You can also use
it to issue an override action to a writable proxy point, e.g. “Active,” “Off,” and so on.
Note: Only proxy points appear in the Point Manager Database—any other components that may also reside
under Points do not appear. For example, you do not see kitControl or schedule components, or any control
point with a “null proxy extension.” However, you can use other views of Points (wire sheet, property sheet,
slot sheet) to access these items.
At the bottom of the view, buttons “New Folder” and “New” let you create new point folders and proxy
points in the station database. An “Edit” button lets you edit one or more selected proxy points. If the
driver supports online “device learning,” buttons “Discover,” and “Match” are also typically available.
Finally, additional buttons may be available, depending on the driver.
For more details, see:
• Points New Folder and New
• Point Edit
• About Point Discover, Add and Match (Learn Process)
• About other Points views

Points New Folder and New

Buttons New Folder and New exist in a device’s Point Manager view under any driver network.
Note: New Folder and New are tools on the Point Manager toolbar, and in the Manager menu.

NiagaraAX-3.x
4-28
User Guide
Chapter 4 – Driver architecture About the Point Manager
May 1, 2007 Points New Folder and New

New Folder
New Folder in the Point Manager adds a special “PointFolder” component that you can use to organize
proxy points. This is equivalent to copying that same component from that driver’s palette. A Name
dialog lets you name the folder before it is created (Figure 4-44).

Figure 4-44 Example New Folder dialog in Point Manager

When you click OK, a new PointFolder component is added under Points. Point folders are often useful,
especially if you are creating many proxy points, or need extra wire space for additional kitControl or
schedule components (and whatever links you wish to create between them).
Note: A devices’s PointFolder component is different than a “normal” Folder component, because it includes that
devices’s Point Manager view as its default view (just like the parent Points component). You can double-
click a point folder (either in the Point Manager view pane or in the Nav tree), to access its Point Manager.
Also, an “All Descendants” command is available from the root Points Manager, which allows you to see all
proxy points in that device.
All Descendants When in the Point Manager of a point folder, it is “unaware” of proxy points in other
point folders (or in the root of Points). However, from the root Point Manager view (of Points), you can
“flatten” the folder structure to view all proxy points by selecting “All Descendants” from the Manager
menu (Figure 4-45) or simply clicking the “All Descendants” tool on the toolbar (Figure 4-46). Note that
“all descendants” is also available at any point folder (level) as well—you just see all points in descendants
from that folder level on down.
Note: Be aware that in a device with many point folders and proxy points, using the all descendants feature
(particularly at the Points root level) may decrease performance. This might result from so many points
becoming subscribed.

Figure 4-45 Manager menu “All Descendants” command

NiagaraAX-3.x
4-29
User Guide
About the Point Manager Chapter 4 – Driver architecture
Point Edit May 1, 2007

Figure 4-46 Point Manager “All Descendants” tool on toolbar.

Note: If you are using point folders, and you click on a table to column to resort points, please be aware that any
proxy point-to-point folder organization is lost during that view. However, you can always see contents of
point folders clearly in the Nav tree, and again when returning to the Point Manager view from another
view.
New
New in the Point Manager is to add new proxy points to the station. Typically, you use New only if the
driver does not support online discovery, or if you are programming offline. Under any of the Modbus
drivers, for example, you use New to add proxy points.
Using New is equivalent to copying proxy points from that driver’s palette, except it provides more utility
to specify other parameters. Minimally, the New dialog provides a selection list for proxy point type, and
also the number of points to add (Figure 4-47).

Figure 4-47 Example New dialog in Point Manager

In some driver networks, the New dialog may provide other parameters, such as a starting address range
when adding multiple proxy points. When you click OK, the number and type of proxy points you
specified are added under Points or a point folder. You need to edit specific properties for each new proxy
point (note these are typically properties of its proxy extension).

Point Edit
In the Point Manager view, you can Edit any proxy point shown in the station database by simply double-
clicking it. (Edit does not apply to point folders.)
Edit
The Edit dialog appears with the proxy point listed (Figure 4-48).

NiagaraAX-3.x
4-30
User Guide
Chapter 4 – Driver architecture About the Point Manager
May 1, 2007 Point Edit

Figure 4-48 Example Edit dialog in Point Manager (single point)

Note: The Edit dialog for a proxy point shows mostly properties under its proxy extension, plus (typically) the
parent point’s Name and Facets. Many of the proxy extension values are required for communications, and
will vary among drivers. To access all properties of the proxy point, including all those under any of its
extensions, go to its property sheet.
When a single point is selected in the Edit dialog, you can edit any property except Type (fixed when you
added the point). Included is the ability to edit the Name of the proxy point in the station. This is equivalent
to the right-click Rename command on the point.
The following related topics also apply:
• Proxy point “gang” edits
• Manager table features
Proxy point “gang” edits
The Edit button in the Point Manager allows you to edit one or more proxy points in the station in a single
dialog. Before clicking Edit, use standard Windows keyboard controls to highlight (select) multiple points
(e.g. hold down Ctrl key and click desired points).
Note: Edit is also on the Point Manager toolbar and the Manager menu, if any point is selected.
The “gang” edit feature is useful for making the same change in multiple (selected) proxy points. For
example, as shown in Figure 4-49, you can change “Tuning” (point’s associated tuning policy) in multiple
points at the same time (versus editing this individually).

NiagaraAX-3.x
4-31
User Guide
About the Point Manager Chapter 4 – Driver architecture
About Point Discover, Add and Match (Learn Process) May 1, 2007

Figure 4-49 Example “gang edit” in Edit dialog in Point Manager

When you have the Edit dialog open with multiple points, you can also click on a specific one to make
individual edits (e.g. Name, or any other editable property), during the same dialog session where you
made “gang” property edits. When you click OK, all the changes are applied to the proxy points as made
during your Edit session. For more details, see “About gang edits.”
Note: When you have multiple points selected in the Edit dialog, properties that must be unique (such as Name)
are automatically unavailable (dimmed). However, note that some properties that typically should be
unique (often address properties) may still be available for “gang edit,” as this rule is not automatically
enforced. Typically, when editing these properties, you should verify only a single point component (row) is
highlighted in the table.

About Point Discover, Add and Match (Learn Process)

Online “point learns” are possible in some driver networks, for example the NiagaraNetwork, Bacnet-
Network, LonNetwork, and NdioNetwork. Whenever available, this method is the easiest way to
accurately add proxy points to the station database.
Any proxy point learn in NiagaraAX is a two-step process using the Point Manager, where you:
1.Under a selected device component, use its (Points device extension) Point Manager view to
Discover data items as point candidates for inclusion in the station database.
2. Select and Add from those candidates, creating proxy points under the device’s Points container. (If
you already used New to add points, you can also Match to those existing points).
Note: The Point Manager reinforces this process by providing two separate panes in the view whenever you enter
“Learn Mode.” See “About Learn toggle” on page 4-16.
Discover
The Discover button is available in the Point Manager only if the driver supports online discovery. When
you click Discover, the Point Manager view splits into two panes (Learn Mode), and at the same time
typically launches a discovery “job” (Figure 4-50).
Note: Under a LonNetwork, Point Manager has a Learn Mode, but no point Discover. All possible data items
were already discovered when the parent device was discovered and added. Here, enter Learn Mode by
toggling (see “About Learn toggle” on page 4-16).

NiagaraAX-3.x
4-32
User Guide
Chapter 4 – Driver architecture About the Point Manager
May 1, 2007 About Point Discover, Add and Match (Learn Process)

Figure 4-50 Discover splits Point Manager view

Note: Under a NiagaraNetwork (only), a Niagara Point Manager discover produces an intermediate dialog: the
Bql Query Builder. You use it to browse the remote station and specify what items to select from as
discovered proxy point candidates. For details, see “About the Bql Query Builder” on page 4-56.
In Learn Mode, the two panes in the Point Manager operate as follows:
• Discovered (top pane)
Lists data items discovered on the driver’s network, as proxy point candidates. For any data item
found that already exists in the station database, it will appear “ghosted” (listed faintly). Note items
listed may be “expandable”—see “Discovered selection notes” on page 4-33.
A job “progress bar” is also included on top of the Discovered pane.
Note: A Cancel button is available during a discovery job. If needed, use it to stop discovery.
• Database (bottom pane)
Lists proxy points and point folders that are currently in the station database.
Note: As necessary, drag the border between the two panes to resize. Also (at any time), toggle between the two-
pane Learn Mode and the single-pane (Database) view by clicking the Learn Mode tool in the toolbar
(Figure 4-24 on page 16), or using the Learn Mode command in the Manager menu.
Discovered selection notes Often, data items listed in the Point Manager’s discovered pane are
expandable, having one or more related items, each individually selectable. Expandable items are
indicated by a leading plus (+), which you click to expand (a toggle control).
Figure 4-51 shows an example item (Lonworks nvoUnitStatus) expanded to reveal individual numeric-
type elements, each selectable as a separate proxy point.

NiagaraAX-3.x
4-33
User Guide
About the Point Manager Chapter 4 – Driver architecture
About Point Discover, Add and Match (Learn Process) May 1, 2007

Figure 4-51 Expand discovered data items to see all point candidates

Here, if you selected only the top “mode” element to add, you would have one proxy EnumPoint to
monitor the enumerated unit status (auto, heat, cool, etc), but would not have any of the related numeric-
type items proxied as control points.
Depending on the driver/device type, expandable discovered items represent individual properties or
other “structured” data. Some examples:
• BacnetDevice—Each top item is typically the “present value” property of the BACnet object (most
commonly selected). Expand the item to see other properties of the object.
• NiagaraStation—Using Bql Query Filter defaults (Config, control, ControlPoint), each top item
is equivalent to the “Out” slot of the Niagara component (and most commonly selected). Expand the
item to see other slots in the component (including Out).
• LonDevice—Each top item is typically the first element (field) in a structured SNVT (multi-field data
structure), as used in that particular network variable (nv or nci). To access other data fields in the
SNVT’s structure, you must expand that item.
For specific details, refer to the “Point discovery notes” section in a particular driver document.
Add
The Point Manager's Add button is available in Learn Mode when you have one or more data items
selected (highlighted) in the top discovered pane. When you click Add, an Add dialog appears that allows
you to edit properties before the proxy point(s) are created in the station (Figure 4-52).
Note: Whenever you select one or more items in the top discovered pane, the toolbar also has an available Add
tool (“plus” symbol), and the Manager menu has an Add command. Also, you can simply double-click a
discovered item to bring it up in the Add dialog.

NiagaraAX-3.x
4-34
User Guide
Chapter 4 – Driver architecture About the Point Manager
May 1, 2007 About Point Discover, Add and Match (Learn Process)

Figure 4-52 Add dialog from Add button in Point Manager

The Add dialog is nearly identical to the point Edit dialog, but allows you to edit Type as well as other
properties.
Often, you may wish to change Type from the pre-selected one, at least between read-only points and the
equivalent writable control point within that data category. For example, if adding a proxy point for the
present value (default) property for a BACnet Binary Output object, you may wish it to be a read-only
BooleanPoint point rather than the default BooleanWritable. As shown in Figure 4-53, you can do this in
the Add dialog before it is added to the station database, (but not later using the point Edit feature).

Figure 4-53 Change Type as needed in point Add dialog

Note: In most cases, alternate point Types include StringPoint, and possibly others. Generally speaking, there are
few practical applications in changing the data category of a proxy point type (e.g. from Boolean to Enum
or Sting), however, this may be an option. Note that if working under a NiagaraNetwork, only read-only
proxy points are available.
Address-related properties in the Add point dialog already have acceptable values for operation
(otherwise, the data item would not have been discovered). It is possible you change only Name and
possibly Type, unless you know other settings you wish to change now. You can always Edit these
properties in the proxy point(s) after you click OK and add them to your station.
Match
Match is a feature that may be useful when you have an application with proxy points you wish to reuse,
or if you have programmed offline using the New point feature.

NiagaraAX-3.x
4-35
User Guide
About the Point Manager Chapter 4 – Driver architecture
About other Points views May 1, 2007

• In the first case (application for reuse), you could have some number of proxy points included in an
application that you have saved and now recopied under the target Points container. Often, address-
related properties in the copied proxy points are incorrect. However, you can use the Point Manag-
er’s Learn Mode and step through each proxy point in the copied application, and use the Match fea-
ture to “sync” with the intended (and discovered) data item.
• In the second case (offline programming) where a connection to the actual device network is un-
available, you can manually add New devices and New proxy points, and begin station engineering
of a driver network. Typically, most component creations under a driver network are possible (in-
cluding all levels) using the New command in the various “manager” views (Device Manager, Point
Manager, other device extension managers). Or, you can add saved applications (from the device lev-
el on down) and edit as necessary. Then, when online with the driver network later, you could use
Match to “sync” to existing components (device-level, proxy points, and so forth).
The Match button in the Point Manager becomes available when in Learn Mode, and you have:
1. Selected one point candidate in the top (Discovered) pane.
2. Selected one existing proxy point in the bottom (Database) pane.
Note: In this case, the toolbar also has an available Match tool, and the Manager menu has a Match command.
When you click Match, the Match dialog appears, as shown in Figure 4-54.

Figure 4-54 Match dialog example in Point Manager

Note: Match is strictly a “one-to-one” function for “discovered-to-database”—note that it is unavailable any time
you have multiple items selected either in either the top Discovered pane or bottom Database pane.
The Match point dialog is nearly identical to the single-point Edit dialog, and typically provides the
“discovered” point address values. Often, most properties in the Match dialog have acceptable address
values required for operation (otherwise, the item would not have been discovered). You can always Edit
the proxy point after you click OK and add it to your station.

About other Points views

Although you initially use the Point Manager (default) view of a device’s Points extension (and/or child
point folders), typically other views are needed when engineering a network. You can use the view
selector in the locator bar, or in the Nav tree right-click Points (and/or child point folders) and select one
of the View menu options.
Note: Remember that the Point Manager view provides access only to proxy points, and edit features apply only
to proxy extension properties.
Commonly used Points views include:
• Wire sheet
Shows all proxy points, plus any kitControl and schedule components, simple control points, and so
on, as well as links between them. Typically, you use this view to engineer control logic.
• Property sheet
Also includes all proxy points, plus any kitControl and schedule components, simple control points,

NiagaraAX-3.x
4-36
User Guide
Chapter 4 – Driver architecture About Histories extension views
May 1, 2007 History Import Manager

and so on. As needed, you can use this view to expand down to any level to access and edit properties.
For example, you can access an alarm extension under a proxy point.
• Slot sheet
Also includes all proxy points, plus any kitControl and schedule components, simple control points,
and so on. As needed, you can use this view to edit config flags from defaults (say, for security
schemes), edit config facets, and add name maps.
• Px view (New View)
(Optional) A custom graphical view that you define by creating a new px file or using an existing px
file. When created, this view becomes the default view for the device’s Points extension (or if created
for a points folder, its default view).

About Histories extension views

For an overview of a device Histories extension, see “About the Histories extension” on page 4-25. Special
views available on a device’s Histories extension may include:
• History Import Manager
• History Export Manager

History Import Manager

The History Import Manager is the default view for a device’s Histories extension. Like other managers,
it is a table-based view (Figure 4-55). Here, each row is a history import descriptor. Each descriptor
specifies how log data is imported (pulled) from the device into the station as a history.

Figure 4-55 History Import Manager under a NiagaraStation

When building a network in the station, you use this view to create, edit, and delete history import
descriptors. Each import descriptor you add results in the creation of a local Niagara history.
Following station configuration, this view provides a status summary for collecting imported histories.
You can also use it to issue manual “Archive” commands to one or more history descriptors. This causes
an immediate import request to pull logged data from the remote device.
Note: Only history import descriptors appear in the History Import Manager view—any other components that
may also reside under Histories do not appear. For example, you do not see the default “Retry Trigger”
component (see “About the Retry Trigger” on page 4-26). However, you can use the Histories property sheet
to access these items.
At the bottom of the view, the button “New” lets you manually create new import descriptors in the
station. An “Edit” button lets you edit one or more import descriptors. Buttons “Discover,” “Add” and
“Match” are also available, (these work similarly as in the Point Manager). An “Archive” button is
available to manually import (pull data) into one or more selected histories. Finally, additional buttons
may be available, depending on the driver.

NiagaraAX-3.x
4-37
User Guide
About Histories extension views Chapter 4 – Driver architecture
History Import Manager May 1, 2007

For more details, see:

• History Import New
• History Import Edit
• About History Import Discover, Add and Match (Learn Process)
History Import New
Button New exists in a device’s History Import view, but is typically used only if engineering offline—most
devices with a Histories extension support online discovery (a FileDevice is one exception). If used,
Match may be used later (when online with the device).
Note: A New tool is also on the History Import Manager toolbar, and in the Manager menu.
History Import Edit
In the History Import Manager, you can Edit any import descriptor in the station database by simply
double-clicking it.
Edit The Edit dialog appears with the import descriptor listed (Figure 4-56).

Figure 4-56 Edit dialog in History Import Manager (single history)

Note: The Edit dialog shows configuration properties of the history import descriptor, plus Name (equivalent to
the right-click Rename command on the descriptor). To access all properties, (including all status
properties) go to its property sheet.
The following related topics also apply:
• History Import properties
• History descriptor “gang” edits
• Manager table features
History Import properties Properties of history import descriptors available in the Edit or Add dialog
are as follows:
• Name
Name for history import descriptor component. If discovered, typically left at default.
Note: Editing name does not affect name of the resulting history (imported into station).
• History Id
If under a NiagaraStation, (NiagaraNetwork), this property specifies the history name in the local
station’s history space, using two parts: “/<stationName>” and “/<historyName>”. If learned, station
name is “^” (see note below) and history name reflects the source history name. Typically, you leave
both fields at default values, or edit the second (<historyName>) field only.
Note: The “^” character is basically a shorthand character to refer to the device name of the parent
container (NiagaraStation component). This may be useful if you have multiple JACEs with histories
named the same. You can create and configure a single History Import Descriptor and then duplicate
and paste it under the other stations without having to go in and change the station name each time.
If under a BacnetDevice, the fields apply to the source BACnet object (“trendLog,” instance number
<n>)—you typically leave learned values at defaults. You name the Niagara history using an addition-
al Local History Name property.
• Execution Time
Either Daily (default), Interval, or Manual. If Manual, properties below are not available:
• Time of Day (Daily)
Configurable to any daily time. Default is 2:00am.

NiagaraAX-3.x
4-38
User Guide
Chapter 4 – Driver architecture About Histories extension views
May 1, 2007 History Import Manager

• Randomization (Daily)
When the next execution time calculates, a random amount of time between zero milliseconds
and this interval is added to the Time of Day. May prevent “server flood” issues if too many his-
tory archives are executed at the same time. Default is zero (no randomization).
• Days of Week (Daily and Interval)
Select (check) days of week for archive execution. Default is all days of week.
• Interval (Interval)
Specifies repeating interval for archive execution. Default is every 15 minutes.
• Time of Day (Interval)
Specifies start and end times for interval. Default is 24-hours (start 12:00am, end 11:59pm).
• Enabled
Default is true. If set to false, does not execute import of history data.
• Capacity
Specifies local storage capacity for imported history, either as Unlimited or Record Count.
If set to Record Count, the following property is available:
• records
Number of records (samples) to locally store. Default is 500.
• Full Policy
Either Roll (default) or Stop. Applies only if capacity is set to record count
• If Roll, upon record count, oldest records become overwritten by newest records.
• If Stop, upon record count, importing stops (until history records are locally deleted).
Note: Bacnet History Import descriptors have additional properties, including a Local History Name
property visible from the Add or Edit dialog.
History descriptor “gang” edits The Edit button in the History Import (or Export) Manager allows you
to edit one or more descriptors in a single dialog. Before clicking Edit, use standard Windows keyboard
controls to highlight (select) multiple descriptors (e.g. hold down Ctrl key and click desired descriptors).
Note: Edit is also on the History Import (or Export) Manager toolbar and the Manager menu, if any descriptor
is selected.
The “gang” edit feature is useful for making identical changes in multiple (selected) descriptors. For
example, you can change “Execution Time” (when data is pulled into imported history) in multiple
descriptors at the same time (versus editing individually).
When you have the Edit dialog open with multiple descriptors, you can also click on select ones to make
individual edits (e.g. Execution, Time of Day), during the same dialog session where you made “gang”
edits. When you click OK, all the changes are applied to the descriptors as made during your Edit session.
For more details, see “About gang edits.”
Note: When you have multiple descriptors selected in the Edit dialog, properties that currently have different
values are automatically unavailable (dimmed). Only a property that currently has the same value (across
all selected descriptors) is available for gang edit.
About History Import Discover, Add and Match (Learn Process)
Unless working offline, you can use the learn process to import histories in the station. As with other
NiagaraAX learns, this is a two-step process in the History Import Manager, where you:
1.Under a selected device component, use its (Histories extension) Histories Import Manager view to
Discover log data (histories) as candidates for inclusion in the station as histories.
2. Select and Add from those histories, creating history descriptors under the device’s Histories
container.
Note: The Histories Import Manager reinforces this process by providing two separate panes in the view whenever
you enter “Learn Mode.” See “About Learn toggle” on page 4-16.
Discover When you click Discover, the Histories Import Manager splits into two panes (Learn Mode):
discovered items in the top pane, and existing import descriptors bottom pane (Figure 4-57).
Note: If under a BacnetDevice, a “Bacnet Trend Logs Discover” job is started, with a progress bar at top. If BACnet
Trend Log objects are found, they are listed in the discovered pane.

NiagaraAX-3.x
4-39
User Guide
About Histories extension views Chapter 4 – Driver architecture
History Import Manager May 1, 2007

Figure 4-57 Discover splits Histories Import Manager

Note: Under a NiagaraNetwork (only), the discovered pane shows the collapsed tree structure of all Niagara
histories of that selected NiagaraStation. Click to expand and select histories for import. See “Discovered
selection notes” on page 4-40 for more details.
In Learn Mode, the two panes in the Histories Import Manager operate as follows:
•Discovered (top pane)
Lists histories (Niagara) or Trend Logs (Bacnet) found in the device, as history descriptor candidates.
Any item that already exists as a history in the station is “ghosted” (faintly listed).
If a BacnetDevice, a job “progress bar” is also included on top of the Discovered pane.
Note: A Cancel button is available during a discovery job. If needed, use it to stop discovery.
• Database (bottom pane)
Lists history descriptors currently in the station database (each has an associated history).
Note: As necessary, drag the border between the two panes to resize. Also (at any time), toggle between the two-
pane Learn Mode and the single-pane (Database) view by clicking the Learn Mode tool in the toolbar
(Figure 4-24 on page 16), or using the Learn Mode command in the Manager menu.
Discovered selection notes In the Niagara History Import Manager, discovered histories of a Niagar-
aStation are under an expandable tree structure, organized by station name (Figure 4-58).

Figure 4-58 Expand Niagara stations to see all Niagara histories

NiagaraAX-3.x
4-40
User Guide
Chapter 4 – Driver architecture About Histories extension views
May 1, 2007 History Export Manager

Histories under the same station name as the parent NiagaraStation (device) component are local
histories for that station. Histories under any other stations represent histories currently imported into
(or exported to) that station.
For example, discovered histories in Figure 4-58 for NiagaraStation J403IP98 include local histories
(expanded); other “imported” histories from station NxMbTest56 are shown contracted.
Note: From any NiagaraStation, you can import both its “local” histories and already-imported histories, as
needed. However, unless circumstances warrant a “relay archive method,” it may be best to import histories
directly from the source station whenever possible.
Add The Add button is available in Learn Mode when you have one or more items selected (highlighted)
in the top discovered pane. When you click Add, a dialog appears that allows you to edit properties before
the history descriptor(s) are created in the station.
Note: Whenever you select one or more items in the top discovered pane, the toolbar also has an available Add
tool (“plus” symbol), and the Manager menu has an Add command. Also, you can simply double-click a
discovered item to bring it up in the Add dialog.
The Add dialog is identical to the history import descriptor Edit dialog. For details on properties, see
“History Import properties” on page 4-38.
Match Match, as an online function, is available if you have one history selected in the top (discovered)
pane and one history import descriptor selected in the bottom (database) pane. However, usage of Match
when importing histories from a device (NiagaraStation, BacnetDevice) is generally not recommended.
Instead, use the Discover and Add method to import histories.

History Export Manager

The History Export Manager view is available (only) on a NiagaraStation’s Histories extension.
Note: If using the Bacnet driver, Niagara histories in the local station can also be “exposed” to all networked
BACnet devices as BACnet “Trend Log objects”. However, this is done using a different view under the Local
Device component in the BacnetNetwork. See the Bacnet Users Guide for more details.
Like other managers, the History Export Manager is a table-based view (Figure 4-59). Each row repre-
sents a history export descriptor. Each descriptor specifies how data from a local history is exported
(“pushed”) from the station to a selected NiagaraStation, where it appears as a history.
Note: The “capacity” and “fullPolicy” configuration for each “exported” history (as created on the remote station),
is determined by that target station’s NiagaraNetwork component’s “History Policies.” Before exporting any
histories, you should review and adjust these policies as needed. For more details, see “About History
Policies” on page 4-51.

Figure 4-59 History Export Manager under a NiagaraStation

You use this view to create, edit, and delete history export descriptors. Each export descriptor you add
results in the creation of a Niagara history on that remote station.

NiagaraAX-3.x
4-41
User Guide
About Histories extension views Chapter 4 – Driver architecture
History Export Manager May 1, 2007

Following station configuration, this view provides a status summary for exporting local histories. You
can also use it to issue manual “Archive” commands to one or more history descriptors. This causes an
export “push” of history data into the selected histories at the remote Niagara station.
Note: Only history export descriptors appear in the History Export Manager view—any other components that
may also reside under Histories do not appear. For example, you do not see the default “Retry Trigger”
component (see “About the Retry Trigger” on page 4-26), or history import descriptors. However, you can
use the Histories property sheet or the Nav tree to access these items.
At the bottom of the view, the button “New” lets you manually create new export descriptors in the
station. An “Edit” button lets you edit one or more export descriptors. Buttons “Discover,” “Add” and
“Match” are also available, (these work similarly as in the Point Manager). An “Archive” button is
available to manually export (push data) into one or more selected histories. Finally, additional buttons
may be available, depending on the driver.
For more details, see:
• History Export New
• History Import Edit
• About History Import Discover, Add and Match (Learn Process)
History Export New
Button New exists in a NiagaraStation’s History Export view, but is used only if engineering offline (online
discovery is preferred). If used, Match may be used later (when online with the device).
Note: A New tool is also on the History Export Manager toolbar, and in the Manager menu.
History Export Edit
In the History Export Manager, you can Edit any export descriptor in the station database by simply
double-clicking it.
Edit The Edit dialog appears with the export descriptor listed (Figure 4-60).

Figure 4-60 Edit dialog in History Export Manager (single history)

Note: The Edit dialog shows configuration properties of the history export descriptor, plus Name (equivalent to
the right-click Rename command on the descriptor). To access all properties, (including all status
properties) go to its property sheet.
The following related topics also apply:
• History Export properties
• “History descriptor “gang” edits” on page 4-39
• “Manager table features” on page 4-19
History Export properties Properties of history export descriptors available in the Edit or Add dialog
are as follows:
• Name
Name for history export descriptor component. Typically left at default. Begins with “Local_” for
any history originating from the local station.
Note: Editing name does not affect name of resulting history (exported into remote station).
• History Id
This property specifies the history name to be created in the remote station’s history space, using
two parts: “/<stationName>” and “/<historyName>”. Histories originating in the local station show
a “^” (shorthand for local station name), and history name reflects the source history name. Typical-
ly, you leave both fields at default values.

NiagaraAX-3.x
4-42
User Guide
Chapter 4 – Driver architecture About Histories extension views
May 1, 2007 History Export Manager

•Execution Time
Either Daily (default), Interval, or Manual. If Manual, properties below are not available:
• Time of Day (Daily)
Configurable to any daily time. Default is 2:00am.
• Randomization (Daily)
When the next execution time calculates, a random amount of time between zero milliseconds
and this interval is added to the Time of Day. May prevent “server flood” issues if too many his-
tory archives are executed at the same time. Default is zero (no randomization).
• Days of Week (Daily and Interval)
Select (check) days of week for archive execution. Default is all days of week.
• Interval (Interval)
Specifies repeating interval for archive execution. Default is every 15 minutes.
• Time of Day (Interval)
Specifies start and end times for interval. Default is 24-hours (start 12:00am, end 11:59pm).
• Enabled
Default is true. If set to false, history data is not exported.
Note: The capacity and full policy of any exported history (created on the remote station) is determined by rules
under that station’s NiagaraNetwork “History Policies,” and is set at creation time only. For details, see
“About History Policies” on page 4-51.
About History Export Discover, Add and Match (Learn Process)
Unless working offline, you can use the learn process to export histories in the station. As with other
NiagaraAX learns, this is a two-step process in the History Export Manager, where you:
1.Under a selected NiagaraStation, use its (Histories extension) Histories Export Manager view to
Discover (local) station histories as candidates for export to that station as histories.
2. Select and Add from those histories, creating history descriptors under the station’s Histories
container.
Note: The Histories Export Manager reinforces this process by providing two separate panes in the view whenever
you enter “Learn Mode.” See “About Learn toggle” on page 4-16.
Discover When you click Discover, the Histories Export Manager splits into two panes, or Learn Mode
(Figure 4-61). The top discovered pane is a collapsed tree structure of all Niagara histories of the local
station. Click to expand and select histories for export. See “Discovered selection notes” on page 4-44 for
more details.

Figure 4-61 Discover splits Histories Export Manager

In Learn Mode, the two panes in the Histories Export Manager operate as follows:
• Discovered (top pane)
Lists all histories in the local station (station you are engineering). Any history that already exists as
a history in the selected NiagaraStation device is “ghosted” (listed faintly).

NiagaraAX-3.x
4-43
User Guide
About Schedules extension views Chapter 4 – Driver architecture
History Export Manager May 1, 2007

•
Database (bottom pane)
Lists history descriptors currently in the station database (each has an associated history, exported
to that remote station).
Note: As necessary, drag the border between the two panes to resize. Also (at any time), toggle between the two-
pane Learn Mode and the single-pane (Database) view by clicking the Learn Mode tool in the toolbar
(Figure 4-24 on page 16), or using the Learn Mode command in the Manager menu.
Discovered selection notes In the Niagara History Export Manager, discovered local histories are
under an expandable tree structure, organized by station name (Figure 4-62).

Figure 4-62 Expand Niagara stations to see all Niagara histories

Histories under the same station name as the local station originated in that station. Histories under any
other stations represent histories currently imported (or exported) into the local station.
For example, discovered histories in Figure 4-62 for local station NxMbTest56 include locally-originated
histories (expanded); other “imported” histories from station J403IP98 are shown contracted.
Note: To any NiagaraStation, you can export both a station’s “locally-originated” histories as well as already-
imported histories, as needed. However, unless circumstances warrant a “relay archive method,” it may be
best to export only “locally-originated” histories.
Add The Add button is available in Learn Mode when you have one or more items selected (highlighted)
in the top discovered pane. When you click Add, a dialog appears that allows you to edit properties before
the history export descriptor(s) are created in the station.
Note: Whenever you select one or more items in the top discovered pane, the toolbar also has an available Add
tool (“plus” symbol), and the Manager menu has an Add command. Also, you can simply double-click a
discovered item to bring it up in the Add dialog.
The Add dialog is identical to the history export descriptor Edit dialog. For details on properties, see
“History Export properties” on page 4-42.
Match Match, as an online function, is available if you have one history selected in the top (discovered)
pane and one history export descriptor selected in the bottom (database) pane. However, usage of Match
when exporting histories from a device (NiagaraStation, BacnetDevice) is generally not recommended.
Instead, use the Discover and Add method to export histories.

About Schedules extension views

For a Schedules device extension overview, see “About the Schedules extension” on page 4-27.
Special views on a device’s Schedules extension may include:
• Schedule Import Manager
• Schedule Export Manager
Note: Other standard views of a Schedules extension are commonly used. For example, the wire sheet may be used
when linking imported schedules to other control logic in the station.

NiagaraAX-3.x
4-44
User Guide
Chapter 4 – Driver architecture About Schedules extension views
May 1, 2007 Schedule Import Manager

Schedule Import Manager

The Schedule Import Manager is the default view for a device’s Schedules extension. Like other managers,
it is a table-based view (Figure 4-63). Each row corresponds to an imported Niagara schedule (read-only).
Configuration for each includes its name and whether it is enabled.

Figure 4-63 Schedule Import Manager under a NiagaraStation

When building a network in the station, you use this view to create, edit, and delete imported Niagara
schedules. In the case of a Niagara network (only), each schedule that you import results in the creation
of a remote “schedule export descriptor” in that remote Niagara station.
Following station configuration, this view provides a status summary for collecting imported schedules.
You can also use it to issue manual “Import” commands to one or more schedules. This causes an
immediate import request to pull schedule configuration data from the remote device.
Note: Only imported schedules appear in the Schedule Import Manager—any other components that may also
reside under Schedules do not appear. For example, you do not see the default “Retry Trigger” component
(see “About the Retry Trigger” on page 4-26), or if a NiagaraStation, schedule export descriptors. However,
the Nav tree and other views on Schedules provide you access to these items.
At the bottom of the view, the button “New” lets you manually create new imported schedules in the
station. An “Edit” button lets you edit a few properties of one or more imported schedules. Buttons
“Discover,” “Add” and “Match” are also available, (these work similarly as in the Point Manager). An
“Import” button is available to manually import (pull data) into one or more selected imported schedules.
Finally, depending on driver, additional buttons may be available.
For more details, see:
• Schedule Import New
• Schedule Import Edit
• About Schedule Import Discover, Add and Match (Learn Process)
Schedule Import New
Button New exists in a device’s Schedule Import Manager, but is used only if engineering offline (all
devices with a Schedules extension support online discovery). If used, Match2 may be used later (when
online with the device).
Note: A New tool is also on the Schedules Import Manager toolbar, and in the Manager menu.
Schedule Import Edit
In the Schedule Import Manager, you can Edit selected properties of a schedule in the station database
by simply double-clicking it.
Edit The Edit dialog appears with the imported schedule listed (Figure 4-64).

NiagaraAX-3.x
4-45
User Guide
About Schedules extension views Chapter 4 – Driver architecture
Schedule Import Manager May 1, 2007

Figure 4-64 Edit dialog in Schedule Import Manager (Bacnet)

Note: The Edit dialog shows some properties of the schedule’s ScheduleImportExt, plus Name—equivalent to the
right-click Rename command on the schedule component). To access all properties of the schedule
(including all status properties) go to its property sheet, or to see the imported schedule events, to its Weekly
Scheduler view.
To access the Scheduler, in the Nav tree you can simply double-click the schedule.
The following related topics also apply:
• Schedule Import properties
• Schedule Import or Export “gang” edits
• Manager table features
Schedule Import properties Properties of imported schedules available in the Edit or Add dialog of the
Schedule Import Manager are as follows:
• Name
Name for the imported Niagara schedule component. If discovered, will match the name of the
source schedule. Must be unique among other components in same container.
Note: Editing name does not affect name of the source schedule, nor the name of the corresponding
schedule export descriptor (if source is a Niagara schedule).
• Supervisor Id
(NiagaraStation only) Unique slot path of source Niagara schedule in that station.
• Object Id
(BacnetDevice only) Combination of BACnet object type (schedule or calendar) and instance num-
ber (unique within that object type in that device).
• Enabled
Default is true. If set to false, the imported schedule is disabled.
Note: While disabled, the schedule’s Out slot has status disabled. Any downstream logic linked to
Out no longer processes it. See “About “isValid” status check” on page 3-18.
• Execution Time
(BacnetDevice only) Specifies how event-configuration refresh (import) occurs with source sched-
ule, using a “pull” request method. Options are Daily, Interval, or Manual (default).
If Manual, some properties below are not available, as noted:
• Time of Day (Daily)
Configurable to any daily time. Default is 2:00am.
• Randomization (Daily)
When the next execution time calculates, a random amount of time between zero milliseconds
and this interval is added to the Time of Day. May prevent “server flood” issues if too many
schedule imports execute at the same time. Default is zero (no randomization).
• Days of Week (Daily and Interval)
Select (check) days of week for import execution. Default is all days of week.
• Interval (Interval)
Specifies repeating interval for import execution. Default is every 15 minutes.
• Time of Day (Interval)
Specifies start and end times for interval. Default is 24-hours (start 12:00am, end 11:59pm).
• Last Trigger

NiagaraAX-3.x
4-46
User Guide
Chapter 4 – Driver architecture About Schedules extension views
May 1, 2007 Schedule Import Manager

Timestamp of when last interval or daily import occurred.

• Next Trigger
Timestamp of when the next interval or daily import is configured to occur.
Schedule Import or Export “gang” edits The Edit button in the Schedule Import (or Export) Manager
allows you to edit one or more items in a single dialog. Before clicking Edit, use standard Windows
keyboard controls to highlight (select) multiple items (e.g. hold down Ctrl key and click desired
schedules).
Note: Edit is also on the Schedule Import (or Export) Manager toolbar and the Manager menu, if any item in the
database is selected.
The “gang” edit feature is useful for making identical changes in multiple (selected) items. For example,
as shown in Figure 4-65 when using Edit in the Niagara Schedule Export Manager, you can change the
“Execution Time, Interval” in multiple schedule export descriptors at the same time (versus editing
individually). For more details, see “About gang edits.”

Figure 4-65 Example “gang edit” in Edit dialog of Schedule Export Manager

About Schedule Import Discover, Add and Match (Learn Process)

Unless working offline, you can use the learn process to import schedules in the station. As with other
NiagaraAX learns, this is a two-step process in the Schedule Import Manager, where you:
1.Under a selected device component, use its (Schedules extension) Schedule Import Manager view
to Discover schedules as candidates for inclusion in the station as Niagara schedules.
2. Select and Add from those candidates, creating imported schedules under the device’s Schedules
container.
Note: The Schedule Import Manager reinforces this process by providing two separate panes in the view whenever
you enter “Learn Mode.” See “About Learn toggle” on page 4-16.
Discover When you click Discover, the Schedule Import Manager splits into two panes (Learn Mode):
discovered items in top pane, and existing imported schedules in bottom pane (Figure 4-66).
A schedule discovery job (either Niagara or Bacnet) is started, with a progress bar at top.
• If Niagara schedules are found in the remote station, they are listed in the discovered pane.
• If BACnet Schedule and/or Calendar objects are found, they are listed in the discovered pane.
Note: A Cancel button is available during a discovery job. If needed, use it to stop discovery.

NiagaraAX-3.x
4-47
User Guide
About Schedules extension views Chapter 4 – Driver architecture
Schedule Export Manager May 1, 2007

Figure 4-66 Discover splits Schedules Import Manager

In Learn Mode, the two panes in the Schedule Import Manager operate as follows:
•
Discovered (top pane)
Lists schedule components (Niagara) or Schedule and/or Calendar objects (Bacnet) found in the de-
vice, as candidates for imported schedules. Any item that already exists as a schedule in the station
is “ghosted” (faintly listed).
• Database (bottom pane)
Lists schedules currently imported in the station database (contained in Schedules container).
Note: As necessary, drag the border between the two panes to resize. Also (at any time), toggle between the two-
pane Learn Mode and the single-pane (Database) view by clicking the Learn Mode tool in the toolbar
(Figure 4-24 on page 16), or using the Learn Mode command in the Manager menu.
Add The Add button is available in Learn Mode when you have one or more items selected (highlighted)
in the top discovered pane. When you click Add, a dialog allows you to edit properties before the schedule
is created in the station. The Add dialog and Edit dialog are identical.
Note: Whenever you select one or more items in the top discovered pane, the toolbar also has an available Add
tool (“plus” symbol), and the Manager menu has an Add command. Also, you can simply double-click a
discovered item to bring it up in the Add dialog.
For details on properties, see “Schedule Import properties” on page 4-46.
Match2 Match, as an online function, is available if you have one schedule selected in the top
(discovered) pane and one schedule selected in the bottom (database) pane. However, usage of Match
when importing schedules from a device (NiagaraStation, BacnetDevice) is generally not recommended.
Instead, use the Discover and Add method to import schedules.

Schedule Export Manager

The Schedules extension of a NiagaraStation, ObixClient/R2ObixClient, or BacnetDevice has an
available Export Manager view. It allows management of schedule components in the local station made
available to that remote device.
Like other managers, the Schedule Export Manager is a table-based view (Figure 4-67). Each row repre-
sents a schedule export descriptor. Each descriptor specifies how/when configuration for a local schedule
is “pushed” to either:
• An imported schedule component in the designated NiagaraStation.
• An existing BACnet Schedule object or Calendar object in the designated BacnetDevice, or existing
schedule in the designated oBIX server.

NiagaraAX-3.x
4-48
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 Schedule Export Manager

Figure 4-67 Schedule Export Manager under a NiagaraStation

Note: A Schedule Export Manager works differently in NiagaraNetworks and BacnetNetworks/ObixNetworks.

• For NiagaraStation, you do not create export descriptors using this view—there is no “Learn Mode,”
Discover, Add, or New. Instead, each schedule export descriptor is automatically created upon the
remote Niagara station “importing” a local schedule component. For more details, see “Station
Schedules import/export notes” on page 4-60.
• For a BacnetDevice or ObixClient, you do use Learn Mode to discover BACnet Schedule/Calendar
objects or oBIX schedules in the device. Then, you select and add any as schedule export descrip-
tor(s). In each export descriptor, you must specify the station’s local schedule component that “ex-
ports” (writes) its event configuration to that remote schedule object. For more details, see the
NiagaraAX BACnet Guide or NiagaraAX oBIX Guide.
After configuration, this view provides a status summary for exporting local schedules. You can also use
it to issue manual “Export” commands to one or more schedules. This causes an export “push” of
schedule configuration into the remote device.
Note: Only schedule export descriptors appear in the Schedule Export Manager view—any other components
that may also reside under Schedules do not appear. For example, you do not see imported schedules or the
default “Retry Trigger” component (see “About the Retry Trigger” on page 4-26). However, the Nav tree and
other views on Schedules provide you access to these items.

About the Niagara Network

Currently, by default every NiagaraAX station has a Niagara Network under its Drivers container. The
Niagara Network is where data is modeled that originates from other stations. Generally, this is done using
the same driver architecture used by other (non-Niagara) drivers. See “About Network architecture” on
page 4-2.
A Niagara Network has the following unique differences:
• All proxy points under a NiagaraStation are “read only” types, namely one of the following:
• BooleanPoint
• EnumPoint
• NumericPoint
• StringPoint
However, note that a Niagara proxy point inherits any actions from the originating (remote) point
or object. For more details, see “Niagara proxy point notes” on page 4-59.
• Connections between stations occur as client and server sessions using the Fox protocol. The re-
questing station is the client, and target (responding) station is the server. A Workbench connection
to a station operates identically, where Workbench is the client, and station is server. Client authen-
tication (performed by the server) is required in all Fox connections.
For more details specific to a Niagara Network, see:
• NiagaraNetwork component notes
• Niagara Station Manager notes
• NiagaraStation component notes
• About the Bql Query Builder

NiagaraAX-3.x
4-49
User Guide
About the Niagara Network Chapter 4 – Driver architecture
NiagaraNetwork component notes May 1, 2007

• Niagara proxy point notes

• Station Alarms notes
• Station Schedules import/export notes

NiagaraNetwork component notes

In addition to common network components (see “Common network components” on page 4-5), the
Niagara Network contains components specific to Niagara, namely:
• Fox Service
A container for Fox protocol settings affecting client connections made to the local station, such as
from Workbench or from another station. Such connections appear locally as “server connections.”
For details, see “About the Fox Service” on page 4-50.
• History Policies
A container for “rules” that specify how remotely-generated histories should be changed when these
histories are pushed into the station (that is, exported from remote stations). For details, see “About
History Policies” on page 4-51.
Also, Tuning Policies for a NiagaraNetwork are simplified, with only 3 properties, as follows:
• Stale Time
• If set to a non-zero value, points become “stale” (status stale) if the configured time elapses
without a successful read, indicated by Read Status “ok.”
• If set to zero (default), the stale timer is disabled, and points become stale immediately when
unsubscribed.
• Min Update Time
The minimum amount of time between updates sent from the server to the client. It is used to throt-
tle data changing at a rate faster than minUpdateTime. Default value is 1 second.
• Max Update Time
Used to resend the value if it hasn't been sent for other reasons (such as a change). Default value is
15 minutes.
About the Fox Service
The NiagaraNetwork’s Fox Service holds configuration for the local station’s Fox settings. (This varies
from most other services, which are found instead under the station’s ServiceContainer). Included are
properties for the TCP/IP port number assigned to the Fox server, authentication method used, and
various timeout/trace settings. Typically, most properties are left at default values. See Fox Service
properties for more details.
Authentication is required when establishing any Fox connection to/from the station:
• If opening a station in Workbench, you must enter a valid station username and password for it in
the station login dialog (otherwise it does not open).
• If accessing a station in a browser as a user with a User
• If adding a NiagaraStation to a station’s NiagaraNetwork, you must configure username and pass-
word properties under its Client Connection slot (otherwise it remains “down”). Often, you enter the
username and password of a “super user”-level account in that station. You also specify the software
port used by that station’s Fox server.
Note: Often in a multi-station job, in each station you create a user account specifically for station-to-station
communications, with an assigned profile type of “super user.” This is the account that you reference when
you edit a NiagaraStation’s Client Connection properties, entering its username and password. See “Multi-
station security notes” on page 9-8.
The Fox Service also has a Server Connections container slot with a default ServerConnectionsSummary
view. Client connections to the station’s Fox server are dynamically modeled as “SessionN” child compo-
nents. The summary view allows you to see all current connections, and if necessary, perform a right-click
Force Disconnect action on one or more connected users.
Fox Service properties NiagaraNetwork Fox Service properties are as follows:
• Port
Specifies well-known TCP/IP port used by Fox server (default is 1911).
• Authentication Policy
Either Digest Md5 (default) or Basic. Applies to password authentication when establishing a client
connection.
• If Digest Md5, user password is encrypted. This is the recommended setting.
• If set to Basic, password is passed in clear text. Typically, Basic is used only if using LDAP.

NiagaraAX-3.x
4-50
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 NiagaraNetwork component notes

• Request Timeout
Time to wait for a response before assuming a connection is dead (default is 1minute).
• Socket Option Timeout
Time to wait on a socket read before assuming the connection is dead (default is 1minute).
• Keep Alive Interval
Interval between keep alive messages (default is 5 seconds). The keep alive should be well below the
request timeout and socket option timeout.
• Enable Announcement
Either true (default) or false. Enables multicast announcement messages for learn/discover.
• Multicast Time To Live
Number of hops to make before a multicast message expires (default is 4).
• Server Connections
Provides status information about current Workbench client connections to the local station (does
not reflect station-to-station Fox connections).
• Trace Session States
Either true or false (default). Debug usage for tracing session state changes.
• Trace Read Frame
Either true or false (default). Debug usage for dumping frames being read from the wire.
• Trace Write Frame
Either true or false (default). Debug usage for dumping frames being written to the wire.
• Trace Multicast
Either true or false (default). Debug usage for tracing multicast messaging.
About History Policies
The NiagaraNetwork’s “History Policies” (HistoryNetworkExt) holds “rules” that are used when remote
histories are “exported” into the local station. Unlike imported histories, which let you define (and adjust
later, if needed) the “capacity” and “full policy” settings in each HistoryImportDescriptor, histories that
are exported into the station have no associated component—only the history itself. The capacity and “full
policy” for each history is set only at creation time, using the local history policies.
Note: You export histories into the station working under a remote station—meaning, from a view of the Histories
device extension under the NiagaraStation that represents this (local) station. See “History Export
Manager” on page 4-41.
For an example scenario showing histories in two JACE stations that are exported to a Supervisor station,
and how history policies apply, see Figure 4-68.
Additional details are in the following sections:
• Default history policies
• Config Rules
• Example rules

NiagaraAX-3.x
4-51
User Guide
About the Niagara Network Chapter 4 – Driver architecture
NiagaraNetwork component notes May 1, 2007

Figure 4-68 History Policies in a supervisor station

As shown in Figure 4-68, the Supervisor’s History Policies “Config Rules” determine the capacity and
fullPolicy settings for each history upon export from the JACE stations “WestWing403” and
“EastWing403”. Rules are matched to remote station (device) names and history names, which determine
the corresponding capacity and full policy values to apply upon history creation. If a history does not
match any rule, it is created using the same capacity and full policy as in the source history. For an
example related to this scenario, see “Example rules” on page 4-53.
Default history policies By default, under a NiagaraNetwork’s History Policies, only a single “default
rule” exists—with wildcard matches to “all” stations and history names, specifying “unlimited” capacity
and a “roll” fullPolicy. This means that any history that is exported into the station (from any remote
station) is archived using a local history configured with unlimited capacity.
Given the vast storage capacity of a supervisor host PC, the default “one rule” setting may be acceptable
on the target of most exported histories (supervisor station). However, if for some reason you are
exporting histories to a JACE station, you should definitely change the “Default Rule” of the History
Policies under its NiagaraNetwork to specify smaller capacities. Even for a supervisor station, you may
wish to change the default rule, and/or add additional optional config rules, as needed.
Config Rules When a history is exported to the station (from another station), these rules are evaluated
to set the local (archived) history’s config properties “capacity” and “fullPolicy.” The first matching rule
is used. The “Default Rule” is always at top, and cannot be deleted or renamed.
Note: Rule priority is set by order—as the “Default Rule” is always first, it is highest priority. If you create other
rules (in Workbench, right-click a rule, then click “Duplicate”), you can edit, rename, and reorder as
needed.
Each rule under the network’s History Policies has the following configuration properties:

NiagaraAX-3.x
4-52
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 NiagaraNetwork component notes

• Device Pattern
String matching to device names, meaning name of NiagaraStation(s) that are exporting histories.
Default value is a wildcard (“*”), meaning all station names are matched.
• History Name Pattern
String matching to history names of histories being exported. Again, default value is a wildcard (“*”),
meaning all named histories are matched.
Note: Both device pattern and history name pattern must apply for the rule to be used—otherwise
the next rule down (in order) in History Policies is evaluated.
• capacity
The capacity setting to use when creating the local history, if matched by device and history names.
Either “unlimited,” or “Record Count,” with a finite record specified.
• fullPolicy
Applies if capacity is not “unlimited,” and specifies if collection continues when the capacity record
limit is reached (“roll”) or collection stops (“stop”).
Example rules As shown in the three-station scenario of Figure 4-68, histories in two JACE stations are
exported to the “Supervisor” station. As shown in Figure 4-69, the receiving supervisor station has 2
additional config rules under its History Policies of its NiagaraNetwork.

Figure 4-69 Example history policies config rules (supervisor station)

In this example, the highest-priority “Default Rule” matches all (any) stations exporting, with a history
name pattern of “Audit*”—this matches any “AuditHistoryLog”. Capacity is set to unlimited, as all
history records are wanted for archive.
The next two rules are applied to histories exported (by any stations), as follows:
• MetersRule — This rule applies to any station, for any history named beginning with “Meter”
(“Meter*”). Any such history is archived using unlimited capacity, as all records are wanted.
• EastWins — This rule applies only to stations named beginning with “East” (“East*”), for any histo-
ry. Such a history is archived using a capacity of 100,000 and a “roll” full policy.
Following this example (with exported histories in the JACE stations, as shown in Figure 4-68), the
histories are created in station “Supervisor” as follows:
• WestWing403
Histories are exported using following capacity and fullPolicy (from config rule):
• AuditHistoryLog: unlimited, roll (from Default Rule)
• LogHistory: 500 records, roll (no rule matched, using source history config, as in JACE)
• Meter1: unlimited, roll (from “MetersRule”)
• ZoneTemp1: 500 records, roll (no rule matched, using source history config, as in JACE)
• Meter2: unlimited, roll (from “Meters Rule”)
• ZoneTemp2: 500 records, roll (no rule matched, using source history config, as in JACE)
• EastWing403
Histories are exported using following capacity and fullPolicy (from config rule):
• AuditHistoryLog: unlimited, roll (from “Default Rule”)
• LogHistory: 100,000 records, roll (from “EastWins” rule)
• Meter4: unlimited, roll (from MetersRule)

NiagaraAX-3.x
4-53
User Guide
About the Niagara Network Chapter 4 – Driver architecture
Niagara Station Manager notes May 1, 2007

• ZoneTemp1: 100,000 records, roll (from “EastWins” rule)

• Meter3: unlimited, roll (from Meters Rule)
• ZoneTemp2: 100,000 records, roll (from “EastWins” rule)
Again, note that the rules are processed in priority order. In this example, if the two optional rules were
reordered (“EastWins” above “MeterRule”) before the JACE histories were exported, results would differ.
“Meter” histories from EastWing403 would have a 100,000 record capacity instead.

Niagara Station Manager notes

The Station Manager is the default view for the Niagara Network. It operates like the Device Manager for
most drivers that have online “device discovery” capability. For general information, see “About the
Device Manager” on page 4-12.
When using the Station Manager, the following notes apply:
• Station Learn and Discover notes
• Station Add notes
Station Learn and Discover notes
By default, a station discover uses IP address (vs. host name). Typically, this is the recommended method.
However, if Niagara hosts are installed on a network using DNS, you can toggle the discovery method to
use host name instead. Do this in the table options menu (click upper right small control) of the Station
Manager, as shown in Figure 4-70. You can also select other columns for display, and sort on any column.
See “Manager table features” on page 4-19 for more details.

Figure 4-70 Station Manager table options menu

By default, discovered stations list showing address. If a station uses a Fox port other than 1911 (default),
address includes the port number appended, for example: 192.168.1.112.1912.
Station Add notes
When you add a NiagaraStation to the database, the Add dialog includes its Fox port, along with fields
for station username and password (required for client connection) as shown in Figure 4-71.

NiagaraAX-3.x
4-54
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 NiagaraStation component notes

Figure 4-71 Add dialog for NiagaraStation

Typically, you enter a user name and password for a “super user” that exists in the remote station. By
convention, this may be a user especially for station-to-station access (for example, a user “m2m”). See
“Multi-station security notes” on page 9-8 for more details.
Note: When working in an AxSupervisor station running AX-3.1 or later, additional “platform” properties are
present, to specify the platform daemon credentials the Provisioning Service should use to connect to the
remote JACE platform, to run provisioning jobs. For more details, see “New station notes” in the Provi-
sioning Guide.
Note: After you add a station, in the Station Manager’s database pane just double-click it to bring up the Edit
dialog, which provides access to the same properties in the Add dialog (Figure 4-71). Or, you can access all
client connection properties from the NiagaraStation component’s property sheet (“Client Connection” slot,
along with status properties).
Adding a NiagaraStation automatically creates a reciprocal NiagaraStation in the remote station.
Reciprocal NiagaraStation component When you add a station under the Niagara Network, that
remote station automatically adds a “reciprocal” NiagaraStation component under its own Niagara
Network, representing your local station. However, it is created with its “Enabled” property set to false,
and so has a status of “disabled” (gray on gray background). This provides a visual clue for you to edit its
client connection username and password to a valid user account in the reciprocal station, and to set
Enabled back to true for operation.

NiagaraStation component notes

Explains items unique to Niagara Station components versus other device components.
• About station status properties
• About client connection properties
• About server connection properties
• About station “provisioning” extensions
About station status properties
Station status properties are typical of most device status properties. See “Device status properties” on
page 4-20.
About client connection properties
Client connection properties determine the Fox port used for station and Workbench connections, as
well as the user name and password used for station-to-station connections. Many properties are status
types, that contain either real-time or historical information.
About server connection properties
Server connection properties are all status properties that provide either real-time or historical infor-
mation.
About station “provisioning” extensions
In AX-3.1 or later, the NiagaraNetwork in an AxSupervisor station (only) has NiagaraStation components
that each contain four provisioning device extensions (in addition to the standard device extensions
described in “Types of device extensions” on page 4-24). For more details, see “Types of provisioning
extensions” in the Provisioning Guide. Note that provisioning extensions do not appear in the Station
Manager view, but do appear in the Nav tree.

NiagaraAX-3.x
4-55
User Guide
About the Niagara Network Chapter 4 – Driver architecture
About the Bql Query Builder May 1, 2007

About the Bql Query Builder

The Bql Query Builder is the initial dialog you use when you “Discover” proxy points in a station
under the Niagara Network. You also use it in discovers in other managers, for example, the Bacnet
Export Manager.
This dialog provides extensive Find and Match filters, plus other controls, which are briefly discussed in
the following sections:
• About Bql Query Find filters
• About Bql Query Match filters
• About Bql Query Save, Load, and Edit
Note that the default point Discover for a NiagaraStation produces a Bql Query Builder dialog with a Find
of (all) “Config,” type “Control Point,” and Match of “All,” as shown in Figure 4-72. While this may be
usable, typically you narrow this range, and run multiple point discovers, as needed.

Figure 4-72 Default Bql Query Builder from NiagaraStation point Discover

About Bql Query Find filters

By default, the Find filter preselects all control points in the target NiagaraStation (Config). Often, you
may wish to narrow this range. For example, you may wish to find Boolean proxy points only under a
specific driver network (during this particular Discover sequence).
To do this, simply click the Find icon (magnifying glass) which produces the Choose Root dialog, as
shown in Figure 4-73.

Figure 4-73 Choose Root dialog

As needed, expand Config to select the root component of interest and click OK (or simply double-click
the component of interest). The proxy point Find is now limited to that area of the station.
To change the type of component, click the “Of type” drop-down and make a selection (Figure 4-74).

NiagaraAX-3.x
4-56
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 About the Bql Query Builder

Figure 4-74 Select component type

The proxy point Find is now limited to that class of component.

Note: A basic understanding of the NiagaraAX component class structure is helpful when making type selections.
For example, selection of Boolean Point (as shown in Figure 4-74) includes all components that “subclass”
from the simple BooleanPoint. Included are all BooleanWritables, as well as many kitControl components
(Logic components, as one example in this case).
If you select type “Component,” you have a “full-width find.” This means that all components are
included—this includes everything listed in the “Of type” drop-down, plus extensions and many other items
(including kitControl objects not subclassed from Control Points, for example, “NumericConst,”
“DegreeDays,” and “LeadLagRuntime,” as a few examples).
About Bql Query Match filters
Use the Match filter when you wish to further limit proxy point candidates. For example, you may wish
to filter on object names (this translates to displayNames).
To see the match dialog options, click the plus (“+”) icon in the far right corner of the Bql Query Builder
dialog, and use Match entry fields as needed (Figure 4-75).

Figure 4-75 Expand Match to see fields, use entry fields as needed

In the Figure 4-75 example above, the Match filter is set to: displayName, like, “Fan*”. This point
discover returns components (within the Find parameters) that are named beginning with “Fan”.
This match would include all components named “Fan”, “FanAhu1”, “Fan21”, “Fantastic”, and so on.
However, components named “FAN” or “FAN21” would not be included (case-sensitivity), nor would
components named “AhuFan” or “BFan” be included—no leading wildcard (“*”) was used.
Note: You can click the Match plus (“+”) icon multiple times to add multiple match lines, and configure each
match line differently, as needed. Click the minus “–” icon to remove a match line.

NiagaraAX-3.x
4-57
User Guide
About the Niagara Network Chapter 4 – Driver architecture
About the Bql Query Builder May 1, 2007

If you have multiple match lines, note the drop-down selection beside Match (“All”, “Any”) becomes
important, and works as follows:
• All — Works as “AND” logic, where a match must occur as specified on every match line.
• Any — Works as “OR” logic, where a match must occur as specified on any match line.

About Bql Query Save, Load, and Edit

Save the setup of any Bql query by simply clicking the Save query icon (diskette). This produces a
Save Query dialog in which you give the query a unique name (Figure 4-76).

Figure 4-76 Save and name Bql Query

Saving a query allows you to recall it later to either use directly, or to modify further as a “starting point”
for another query. You can save as many Bql queries as you need. You can also edit a saved query
(meaning rename it or reorder it in your list of saved queries).
Note: Saved queries are unique to your Workbench instance, and not to any particular station.
To recall a saved query, click the Load saved query icon (folder), and make a selection, as shown in
Figure 4-77.

Figure 4-77 Load saved Bql Query

This loads that query into the Bql Query Builder dialog, where Find and Match entries automatically
change to reflect how that query was constructed.
To edit saved queries, click the Edit saved query icon (note pad). This produces a Save Query
dialog in which you can rename and/or reorder the queries in the list (Figure 4-78).

NiagaraAX-3.x
4-58
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 Niagara proxy point notes

Figure 4-78 Edit saved Bql Queries

Note: If you are interested in the Baja Query Language (BQL), you can learn about queries within the Edit dialog.
Make the dialog window wider, and study the syntax of a saved queries. For detailed information about
queries, see “BQL” in the Niagara Developer Guide.

Niagara proxy point notes

Niagara proxy points are always read-only types (BooleanPoint, EnumPoint, NumericPoint, and String-
Point), see “About point types” on page 3-2. No other types are available.
However, if the source component is a writable point type, any actions (commands) for that component
are available in the Niagara proxy point, as shown in Figure 4-79.

Figure 4-79 Niagara proxy point for writable point includes actions

Other concepts about Niagara proxy points are explained in the following sections:
• Proxy of a proxy, other candidates
• Link control and Niagara proxy points
Proxy of a proxy, other candidates
Often, the (remote) source component of a Niagara proxy point is itself a proxy point, typically under the
Points extension of device in a field bus driver network (Lonworks, Bacnet, and so on). Or, if the remote
station is in a JACE with its own I/O, the source component may be an Ndio proxy point.
Another possibility is for the (remote) source component to be a specific slot of a point extension under
a point, for example, the Total property of a NumericTotalizerExt. In other cases, the (remote) source
component may be a kitControl type, such as one of the Math or Logic types, or one of the other more
complicated types (for example, a LoopPoint or DegreeDays object).
Regardless of the source component, you model all remote Niagara data selecting from the “atomic”
model of the four read-only point types. If you need multiple pieces of data from the same source Niagara
object, you will need to create that many Niagara proxy points.
Link control and Niagara proxy points
Because Niagara proxy points have no inputs, you cannot link into them from local station logic (even if
the remote source component is a writable type). If you need this “inter-station link control,” you must
make another Niagara proxy point (in the remote station) that proxies whatever local source component
you need for the link.

NiagaraAX-3.x
4-59
User Guide
About the Niagara Network Chapter 4 – Driver architecture
Station Alarms notes May 1, 2007

Consider a Niagara proxy point for a BooleanWritable that controls a fan. You wish to provide link
control from a local And object, controlling at priority level 7. Figure 4-80 shows these objects.

Figure 4-80 Local object cannot link into Niagara proxy point

In the example above, you cannot link into the Niagara proxy point “BFanBO_1.”
So in the other (remote) station, you must make a Niagara proxy point for the And object, then link its
output to the source point for “BFanBO_1.” Figure 4-81 shows the wire sheet views with these objects.

Figure 4-81 Source control object now a Niagara proxy point in remote station

In a typical Supervisor station (with many Niagara proxy points), usually not much direct link control is
needed, so this rarely applies. In addition, the schedule import/export mechanism allows for central
scheduling control using local (imported) schedule components.
However, if you are engineering applications between JACE stations that require link control, please
understand you must always use Niagara proxy points in this fashion.

Station Alarms notes

To configure alarms in one station to be received in another station, you must add a StationRecipient in
the AlarmService container of the “sending” (source) station. See “About the station recipient” on page
7-22 for configuration details. You then link whatever AlarmClass components are needed to that
StationRecipient. See “About alarm class” on page 7-15 for more details.
It is not necessary to use the same AlarmClass components in the two stations (although that is one
approach). In the receiving station (often, the Supervisor), if desired you can configure all alarms from a
remote station to route to a single local AlarmClass. Do this in the Alarms extension under the Niagar-
aStation that represents the remote JACE. See “Alarms extension properties” on page 4-26.
Note: In the receiving station’s AlarmService, if you want the remotely-generated alarms to appear in any alarm
consoles, make sure to link the associated AlarmClass components to the necessary AlarmConsole compo-
nents.

Station Schedules import/export notes

You configure sharing of NiagaraAX schedule components between stations from the “receiving side”
station using the Niagara Schedule Import Manager. After you import each schedule component, a
corresponding “schedule export descriptor” is automatically created in the “sending side” station. If
necessary, you can review and adjust these export descriptors using the Niagara Schedule Export Edit
dialog.

NiagaraAX-3.x
4-60
User Guide
Chapter 4 – Driver architecture About the Niagara Network
May 1, 2007 Station Schedules import/export notes

Under a NiagaraStation device, the Schedule Export Manager works uniquely from other drivers, so it is
explained in more detail in the following sections.
• Niagara schedule import/export default configuration
• Schedule Export Edit
• “Schedule Import or Export “gang” edits” on page 4-47
Niagara schedule import/export default configuration
By default, when you import a schedule under a NiagaraStation using the Schedule Import Manager, the
import/export setup is initially configured on both sides as follows:
• Receiving (slave) side:
Niagara schedule component with a ScheduleImportExt configured with “Execution Time” of Man-
ual. The source schedule’s configuration is imported (“pulled”) only once, upon creation. If desired,
you can manually Import it again.
• Sending (master) side:
Corresponding schedule export descriptor with an “Execution Time” of Interval, at 5 minute rate.
You can adjust this in the export descriptor using Schedule Export Edit.
To review all properties of a schedule export descriptor, including status properties, you can view
its property sheet—in the Nav tree under Schedules, simply double-click its Export icon.
Note: Default configuration does not mean the same schedule configuration is continuously
exported (“pushed”) to the remote schedule at this rate. Instead, the export descriptor keeps a “Subor-
dinate Version” timestamp from the last export. If a configuration change occurs, the export descriptor
compares the subordinate version time against the configured interval, and if necessary exports the
schedule to the remote station.
The default “master push” configuration is the most efficient (and recommended) way to keep imported
schedules synchronized. However, if the stations are installed on a network configured such that this
method is not allowed (perhaps firewall issues), you can configure things in reverse. This means config-
uring receiving side ScheduleImportExts with “Interval” execution times (to periodically “re-pull”
schedule configuration), and set corresponding schedule export descriptors to be disabled.
Schedule Export Edit
In the Schedule Export Manager, you adjust any schedule export descriptor(s) shown by selecting
(highlighting) it and clicking the Edit button at the bottom of the view (or on the toolbar).
Note: Unlike in other Manager views, a double-click on a descriptor is not the same as Edit. Instead, double-click
provides the Scheduler view for that exported schedule component. This can be useful to review and if
necessary, make changes to its configuration. For details, see “Schedule component views” on page 10-2.
Edit The Edit dialog appears with the schedule export descriptor listed (Figure 4-82).

Figure 4-82 Edit dialog in Schedule Export Manager

Note: The Edit dialog shows some configuration properties of the schedule export descriptor.
To access all properties, (including all status properties) go to its property sheet. Note that if you double-
click the Nav tree icon for an export descriptor, its property sheet displays.
The following related topics also apply:
• Niagara Schedule Export properties
• Niagara schedule import/export default configuration
• “Manager table features” on page 4-19
Niagara Schedule Export properties Properties in the Edit dialog of a schedule export descriptor are:
• Enabled
By default true. While set to false (export descriptor disabled), export connections are not attempted

NiagaraAX-3.x
4-61
User Guide
About the Niagara Network Chapter 4 – Driver architecture
Station Schedules import/export notes May 1, 2007

to update the remote (imported) schedule.

• Execution Time
Determines when an export update is made to the remote (imported) schedule, providing that a con-
figuration change occurred in the local schedule that requires synchronization (export). For more de-
tails, see “Niagara schedule import/export default configuration” on page 4-61.Options are either
Daily, Interval (default), or Manual. If Manual, the following properties are unavailable:
• Time of Day (Daily)
Configurable to any daily time. Default is 2:00am.
• Randomization (Daily)
When the next execution time calculates, a random amount of time between zero milliseconds
and this interval is added to the Time of Day. May prevent “server flood” issues if too many
schedule exports are executed at the same time. Default is zero (no randomization).
• Days of Week (Daily and Interval)
Select (check) days of week for archive execution. Default is all days of week.
• Interval (Interval)
Specifies repeating interval for export execution. Default is every 15 minutes.
• Time of Day (Interval)
Specifies start and end times for interval. Default is 24-hours (start 12:00am, end 11:59pm).

NiagaraAX-3.x
4-62
User Guide
 CHAPTER 5
Field Bus Integrations
For purposes here, a field bus integration is any NiagaraAX driver besides the niagaraDriver (Niagara
Network). All Niagara AX drivers resemble each other in basic architecture, including the Niagara
Network. For more details, see “About Network architecture” on page 4-2, and “About the Niagara
Network” on page 4-49.
Field bus integrations such as BACnet, LON, Modbus, as well as various “legacy” drivers (typically serial-
connected) each have unique characteristics and features. This section provides a collection of topics that
apply to some of these drivers.
The following main sections are included:
• Port and protocol variations
• Learn versus New devices and points
• Serial tunneling

Port and protocol variations

With one exception, each field bus driver (network) associates with only one physical communications
port on the host platform, and uses a specific communications protocol. The exception is the BACnet
driver (BacnetNetwork), where multiple ports (Ethernet, RS-485 for MS/TP) and protocol variants
(BACnet-Ethernet, BACnet-IP, BACnet-MS/TP) may be used. See the Bacnet Guide for details.
Generally, field bus drivers can be categorized as one of the following:
• Ethernet-connected driver
• Serial-connected driver
• Special-port driver

Ethernet-connected driver
Many field bus drivers are Ethernet (port) connected, typically using some TCP/IP protocol for transport.
For example, the Modbus TCP driver (ModbusTcpNetwork) uses the Modbus TCP protocol—essentially
the Modbus protocol “wrapped” in TCP/IP. The SNMP driver (SnmpNetwork) uses SNMP, an appli-
cation-layer protocol within the TCP/IP protocol suite. These and other Ethernet-connected drivers
operate from a single Ethernet port without difficulty, due to the high bandwidth and efficiencies of IEEE
802 network (and TCP/IP) standards.
In addition to JACE platform usage, Ethernet-connected drivers are available for the AxSupervisor (PC)
platform as well, for “direct device integrations.” These are specially-licensed versions of the AxSuper-
visor (by default, an AxSupervisor is licensed only for JACE device communications, via the Niagar-
aNetwork).

Serial-connected driver
Serial-connected drivers use a specific serial port on the host (JACE) platform. For example, the Modbus
serial driver (ModbusAsyncNetwork) requires association with a specific COMn port on the JACE, which
you do from the property sheet of this network component (Figure 5-1).
Note: Only one network can be assigned to any one serial port (COMn) of the host JACE platform. That driver
network essentially “owns” that communications port.

NiagaraAX-3.x
5–1
User Guide
Learn versus New devices and points Chapter 5 – Field Bus Integrations
Special-port driver May 1, 2007

Figure 5-1 Serial port configuration for a serial-based driver

Slots under the “Serial Port Config” (SerialHelper) must be set to match the communications parameters
of other devices on the attached network. Note that in this ModbusAsync example, you also select either
the Modbus ASCII or Modbus RTU protocol (the driver supports either one, which you set according to
the type of networked Modbus devices).
Often, serial-connected drivers support “legacy type” device networks. In this case, the “serial tunneling”
feature may be useful to run vendor-specific legacy Windows applications to do device configuration and
maintenance (all from an IP station connection). See “Serial tunneling” on page 5-2.

Special-port driver
JACE controllers may include one or more special-use ports, for example one or more Echelon (LON)
FTT-10 ports. Usage of such a port requires a specific driver. In this example, the Lonworks driver (each
LonNetwork) associates with a specific LONn port, which is configured under that network component.
For details, see the Lonworks Guide.
Other special-use ports may appear as the evolution of JACE products continue.

Learn versus New devices and points

Many, if not most, field bus drivers provide the ability to “learn” devices and data points while connected
to that particular field bus. Exceptions include drivers where the field bus protocol does not provide the
ability for this, for example, any of the Modbus drivers.
For specific learn procedures, see the “Quick Start” section in the various driver documents.

Serial tunneling
A NiagaraAX station running one or more serial-based drivers can provide “tunneling” access to its
connected devices. This allows you to use a vendor’s Windows serial-based application (via the serial
tunnel client) to perform device-specific operations. Examples include application downloads or other
device configuration.
The tunneling client is separate from NiagaraAX Workbench—meaning that you can install it on various
PCs, as needed. The key advantage is that serial tunneling requires only a standard IP connection (to the
station), yet provides access as if the client PC was attached to the target serial network via a physical
COM port, for example RS-232.
Note: No special licensing is required to use tunneling features in NiagaraAX.
The following sections provide more details:
• Serial tunnel overview
• Client side (PC application)
• Station side (TunnelService)
• Serial tunneling usage notes

Serial tunnel overview

As shown in Figure 5-2, tunneling in NiagaraAX uses a client-server architecture.

NiagaraAX-3.x
5-2
User Guide
Chapter 5 – Field Bus Integrations Serial tunneling
May 1, 2007 Client side (PC application)

Figure 5-2 Serial tunnel architecture

Serial tunneling uses the following components:

•
Client (PC application) side
The NiagaraAX Serial Tunnel client installs on any Win32-based PC (independent of Nia-
gara Workbench). It provides a “Niagara AX Serial Tunneling” applet in the Windows Control Pan-
el, corresponding to a “virtual” COMn port. For details, see “Client side (PC application)” on page 5-3.
• Server (station) side
The host JACE must have the “tunnel” module installed to support serial tunneling. In addition, its
station must be configured with a TunnelService and a child SerialTunnel component. For
details, see “Station side (TunnelService)” on page 5-5.
Note: A LonTunnel (“lontunnel” module) is also available, and uses the same basic architecture. It allows
Lonworks application tunneling to connected LON devices on a JACE’s FTT-10 network. For details, see
“Lon tunneling” in the Lonworks Guide.

Client side (PC application)

The serial tunnel client is a self-installing executable: Install_Serial_Tunnel.exe, found in the
root of the NiagaraAX distribution CD (Figure 5-3). As needed, you may install it on any Windows XP/
2000 PC on which you use a Windows serial-based application.

Figure 5-3 Serial Tunnel Client installation file is in NiagaraAX CD root

See the following additional sections:

• Installing the serial tunnel client
• Serial tunnel client configuration
• Serial tunnel client installation details
Installing the serial tunnel client

To install the serial tunnel client

To install the serial tunnel client, at the Windows XP/2000 PC do the following:
Step 1 Access the file Install_Serial_Tunnel.exe, as found on the NiagaraAX CD (Figure 5-3).
Step 2 Double-click this file to launch the installation.
Click Yes to install (a command prompt window opens), and other popup appears (Figure 5-4).
Click Yes again to configure.
Step 3 In the Niagara AX Serial Tunnel dialog, enter any known information, or simply accept defaults
(Figure 5-5). Do not duplicate any existing serial (COMn) port already used by Windows. You can always
reconfigure using this dialog, by returning via the Windows Control Panel.
See “Serial tunnel client configuration” on page 5-4 for details on all fields in this dialog.
Step 4 Click OK to finish the install.

NiagaraAX-3.x
5-3
User Guide
Serial tunneling Chapter 5 – Field Bus Integrations
Client side (PC application) May 1, 2007

The “Installation Finished” dialog appears (Figure 5-6)—click OK again. See “Serial tunnel client instal-
lation details” on page 5-5 for a listing of installed components.

Figure 5-4 Serial tunnel client installation

Figure 5-5 Serial tunnel client configuration defaults

Figure 5-6 Serial tunnel client installation finished

Serial tunnel client configuration

After installation, access the serial tunnel configuration dialog from the Windows Control Panel. As
shown for an example session in Figure 5-7, all fields require a valid entry.

Figure 5-7 Serial tunnel client session example

Fields in this dialog are described as follows:

• Serial Port
The “virtual” COM port provided by this tunnel client. This should not conflict with any existing
COM port assignment, as known to Windows, for a physical serial port (e.g. COM1).
When you tunnel from a serial-based Windows application, you specify this “virtual” COM port.
• Host Address
The IP address (or hostname) of the tunnel server, meaning the target JACE running a station with
a serial-based network, TunnelService, and SerialTunnel.
• Tunnel Name
The COMn device name (identifier) of the JACE’s driver network to access. This will vary depending
on the configuration of the network and its corresponding SerialTunnel.

NiagaraAX-3.x
5-4
User Guide
Chapter 5 – Field Bus Integrations Serial tunneling
May 1, 2007 Station side (TunnelService)

• User Name
User in the target JACE station, where this station user must have admin write permissions for the
station’s TunnelService and child SerialTunnel(s).
• Password
Password for this station user.
• Interactive (checkbox)
If checked, this dialog reappears each time a serial-based application first opens this “virtual” COM
port. If cleared, this dialog displays only if an open fails to establish a connection to the tunnel server
(as stored from last entry). Typically, you leave Interactive checked.
Note: When this dialog appears interactively, the Serial Port setting is read-only. To change it,
you must access the Serial Tunneling applet from the Windows Control Panel.
Serial tunnel client installation details
You can install a newer version of the serial tunnel client without uninstalling the current version. The
following files are installed, with services referenced in the Windows registry:
•
Control Panel
<WINDOWS_SYSTEM_DIR>\vserax.cpl
• Network Tunnel Service
<WINDOWS_SYSTEM_DIR>\vserax.exe
Service name: vseraxSvc (vserax dependency)
• Serial Driver Service
<WINDOWS_SYSTEM_DIR>\vseraxx.sys
Service name: vserax
• Uninstaller
<WINDOWS_SYSTEM_DIR>\vseraxun.exe
Executable via “Add/Remove Programs” in Windows Control Panel
Note: If uninstalling (Start > Control Panel > Add or Remove Programs), and the uninstall
appears to fail, try reinstalling the tunnel client, and then uninstall again.

Station side (TunnelService)

To be a serial “tunnel server,” a JACE must have the tunnel module installed, and its station must have
a TunnelService (under its Services folder), as well as a child SerialTunnel component.
The following sections provide more details on the “station side” of serial tunneling:
• Configuring the serial tunnel server
• About serial tunnel connections
Configuring the serial tunnel server

To configure the station for serial tunneling

To configure the station for serial tunneling, do the following:
Step 1 In the palette side bar, open the tunnel palette.
Step 2 Open the JACE station and expand its Services folder.
• If no TunnelService exists, paste one from the palette into the Services folder.
• If a TunnelService does exist, go to next step.
Note: Only one TunnelService is needed in a station’s services, and it can hold multiple tunnel components
(SerialTunnel and LonTunnel). The TunnelService in the (serial) tunnel module is identical to the
TunnelService in the lontunnel module.
Step 3 From the palette, paste a SerialTunnel under the station’s TunnelService.
The station should now have a TunnelService and a child SerialTunnel component.
Step 4 In the SerialTunnel’s property sheet, expand the “Serial Port Config container” (Figure 5-8).
Here, type in the COMn “Port Name” used by the target driver network, and specify other parameters as
defined in the network’s configuration.
See SerialHelper on page 31 for details on various properties.
Note: If the JACE has multiple serial-type driver networks (and corresponding COM ports), you can copy the
same number of SerialTunnel components under the TunnelService. You can then associate each Serial-
Tunnel with a particular network (by its COMn port name), and set the other parameters accordingly.

NiagaraAX-3.x
5-5
User Guide
Serial tunneling Chapter 5 – Field Bus Integrations
Station side (TunnelService) May 1, 2007

Step 5 For any station user that needs to serial tunnel, make sure that they have admin write permissions for the
SerialTunnel(s). Following this and the review of SerialTunnel properties, tunneling is now provided by
the station.

Figure 5-8 TunnelService with child SerialTunnel (copied from tunnel palette)

About serial tunnel connections

Under any SerialTunnel, only one tunnel connection is supported at any one time—if a tunnel connection
is active and another tunnel client (PC) attempts to connect, that remote user sees a popup dialog saying
that the “Desired tunnel is busy.”
In the station (tunnel server), any active tunnel connection results in a TunnelConnection child
component, named as the remote (client’s) IP address or hostname, with a “#1” suffix (Figure 5-9).

Figure 5-9 TunnelConnection is dynamically created/removed

In the Figure 5-9 example, the remote host that is currently serial tunneling is “192.168.1.103.” When
a tunnel connection is terminated, this Tunnel Connection component is removed.

NiagaraAX-3.x
5-6
User Guide
Chapter 5 – Field Bus Integrations Serial tunneling
May 1, 2007 Serial tunneling usage notes

In addition to its statistical properties, a TunnelConnection has an available Disconnect action. This
disconnects the active tunnel connection, removing the parent TunnelConnection component. A popup
dialog “Connection closed by remote host” is seen on the client tunnel side.

Serial tunneling usage notes

Serial tunneling may not work with all vendor’s serial-connected Windows applications. Also, serial
tunneling is not supported for BACnet MS/TP usage—however, BACnet router functionality provided by
a station running a BacnetNetwork with multiple network ports (e.g. IpPort, MstpPort) provides IP
access to MS/TP connected devices.
When initiating a connection through the serial tunnel, client-side usage is transparent except for the
“virtual COMn” port used, and if “Interactive” is left enabled (typical) the resulting dialog right before the
connection is attempted. Figure 5-10 shows an example serial connection being initiated from the
Windows Hyperterminal application. Tunneling client messages appear if the connection fails.

Figure 5-10 Example Windows serial application (Hyperterminal) initiating tunnel connection

Speed of the tunnel connection may be slower that a direct serial connection, due to the overhead of
wrapping and unwrapping messages in Niagara Fox and TCP/IP protocols. Tunneling is not recom-
mended if using a “dialup modem” for connection to the target JACE station.
Tunneling client messages
When using a tunnel client, the specified user must be “authenticated” by the station’s UserService before
a connection is granted (established). If the user is not found, or if the entered password is incorrect, a
popup message appears on the client PC (Figure 5-11).

Figure 5-11 Authentication issue

Note: As in any station connection, note that User Name and Password are case-sensitive.
Currently, only one tunnel connection is allowed per SerialTunnel. If another client application attempts
a connection to that tunnel, a popup message appears on that PC (Figure 5-12).

Figure 5-12 Tunnel busy

NiagaraAX-3.x
5-7
User Guide
Serial tunneling Chapter 5 – Field Bus Integrations
Serial tunneling usage notes May 1, 2007

NiagaraAX-3.x
5-8
User Guide
 CHAPTER 6
About Histories
In Niagara, a data log is referred to as a history. Histories are ordered collections of timestamped records.
A single “history” is a collection of specific data values from a component within any station - local or
remote. Histories are organized by their source station (device), as shown in Figure 6-1.

Figure 6-1 History files organized by station

The following topics are relevant to understanding histories:

• History Services
The History Service, the Audit History service and the Log History service provide support for log-
ging data in a Niagara station. In order to provide database support for histories in a Niagara station,
the station must contain the History Service. Refer to “About the history service” on page 6-2 for de-
tails about the History Service. Refer to “About the audit history service” on page 6-3 and “About the
log history service” on page 6-4 for information about those services.
• History ORD scheme
Once you have a history service running, you can access histories that you create in the database us-
ing the “history” ORD scheme. The unique history scheme name “history” and each unique his-
tory ID provide identification for the individual histories. All history collections are identified by
this unique id. For information on using the ORD scheme to access individual histories, refer to
“About ORDs” on page 1-16.
• History space
History space provides a means for viewing and working with history files in the history database.
History space is visually represented in Workbench as a node in the nav tree and may be accessed by
using the nav tree or by using the Open ORD dialog box. Views on the History space include the fol-
lowing: History Chart Builder, Database Maintenance, Nav Container View. For more information
about history space and history space views, refer to “Types of history space views” on page 6-5.
• History views
History views present the history information in various formats for both analysis and editing. Refer
to “Types of history views” on page 6-9.
• History logging process
Using histories involves a process of collecting, storing and archiving data. You can configure the
history collection process to collect the data that you need and store the history records where you
want them - locally or remotely. This process is described in more detail in “About the history pro-
cess” on page 6-13.
• History Configuration
History configuration includes working with parameters such as ID, history source, timezone,
record type, and more. For more details on configuration, refer to “Configure history extensions” on
page 6-16.

NiagaraAX-3.x
6–1
User Guide
Types of History Services Chapter 6 – About Histories
About the history service May 1, 2007

• History data editing

You can edit and filter the history data in workbench using the history editor view (described in
“About the history editor view” on page 6-12). The editing process is described in more detail in
“About editing history data” on page 6-19.

Types of History Services

History services are available in the History Palette, as shown in Figure 6-2.

Figure 6-2 History services in the history palette

Each service is described in the following sections:

• “About the history service” on page 6-2
• “About the audit history service” on page 6-3
• “About the log history service” on page 6-4

About the history service

To use histories, each station must contain a single history service that provides http access to all of the
histories in a station. This service is responsible for creating the history database, as well as enabling the
collection and storage of histories in the database. If you do not have the history service in your active
station, you can add it by dragging and dropping a copy from the History Palette, as shown in Figure 6-3.

Figure 6-3 Adding the history service

The history service manages histories in ways that are not always visible to the user, including the
following:
• identifies histories
when the service is started (normally this is whenever the station is started) all existing histories are
added to the service.
• life cycle management
handles history management functions, such as creation and deletion of individual histories.
• namespace
maintains the naming convention (namespace) for all histories.
• configuration
maintains a global default configuration for the histories.
The history extension manager and the history property sheet are two views of the history service that
provide ways to work with history extensions. Refer to the following sections for more information about
these views:
• About the history extension manager
• About history service property sheet

NiagaraAX-3.x
6-2
User Guide
Chapter 6 – About Histories Types of History Services
May 1, 2007 About the audit history service

About the history extension manager

As the default view of the history service, the history extension manager shows all history extensions in
the station and displays their current status. Using this view as both a management and navigational tool,
you can double-click on any entry-row to go directly to the property sheet view of that extension. This
table has the standard table features. Use the Table Options menu in the top right corner of the
history table to modify the table view or to export the data in the view, as desired. Refer to “Table controls
and options” on page 2-17 for information about using the tabular view, including the Table Options
menu.

Figure 6-4 History extension manager

You can also Enable, Disable, or Rename any collection from this view by selecting the desired
history extension in the table and using the History Ext Manager menu, popup menu, or toolbar icons, as
described in the sections listed below:
• “About the History Ext Manager menu” on page A-8
• “About the history extension manager popup menu items” on page A-11
• “About the history extension manager toolbar icons” on page A-14
Note: If a history is disabled, its row is dimmed with a gray background in the history extension manager view.
About history service property sheet
The history service property sheet, shown in Figure 6-5, includes the following property:
• Max Open Time
this is an editable parameter for setting the amount of time that the history database may remain
open without being accessed before it is subject to being closed by the Close Unused Histo-
ries action. If the history is accessed more frequently than the Max Open Time, it is not closed
when Close Unused Histories action is invoked.

Figure 6-5 History service properties

History service actions

History service actions are available from the popup menu when you right-click the HistoryService node
in the nav side bar pane. Available actions include:
• Save Db
this action initiates a save of all histories to the history database.
• Close unused histories
this action closes any histories that have not been accessed within the Max Open Time (this time is
set in the history service property sheet).

About the audit history service

The Audit History Service keeps a history of the changes that are made by users. If this service is enabled,
it registers itself as the auditor for the system when the service is started. The easiest way to add the audit
history service (if not already present) is through a simple drag and drop method from the History Palette
(under the HistoryService) to the services area of the nav side bar pane, as shown in Figure 6-6.

NiagaraAX-3.x
6-3
User Guide
Types of History Services Chapter 6 – About Histories
About the log history service May 1, 2007

Figure 6-6 Adding audit history service

When enabled, the Audit History Service logs all property changes and all actions taken on a component,
such as the following:
• Property changed
• Property added
• Property removed
• Property renamed
• Properties reordered
• Action invoked
You can view the Audit History Service properties, enable or disable the Audit History Service, and set
record capacity parameters from the Audit History Service Property Sheet, as shown in Figure 6-7.

Figure 6-7 Audit history service properties

Refer to “About user audits” on page 9-7 for more details.

About the log history service

The Log History Service keeps a History of Niagara log records when it is enabled. This service maintains
a buffered history (“LogHistory”) of some of the messages seen in the station’s standard output. This can
be very helpful when you are troubleshooting problems with a station. If a station has Log History Service
enabled, you can check the log history for recent error messages. Refer to the Platform Guide section
“Station output” for more information about output messages.
The Log History Service is available in the History Module. The easiest way to add this service (if not
already present) is through a simple drag and drop from the History Palette (under the HistoryService)
onto the services area of the nav side bar pane, as shown in Figure 6-8.

NiagaraAX-3.x
6-4
User Guide
Chapter 6 – About Histories Types of history space views
May 1, 2007 About the log history service

Figure 6-8 Adding log history service

You can edit the Log History Service properties and set configuration properties in the property sheet, as
shown in Figure 6-9.

Figure 6-9 Log history service properties

In addition to the standard HistoryConfig properties, the following properties are available for editing:
• Enabled
select the true option to enable or the false option to disable the Log History Service.
• Minimum Severity
you can choose the level of output that you want to record by setting the log level Minimum Severity
property. This property is the lowest-level station output message that you want to log. The default
log level for Minimum Severity is Error. You can change this to Warning., Trace, or Message.

Types of history space views

The history space views shown in Figure 6-10 and listed below are particularly helpful in working with
multiple histories:

Figure 6-10 History space views

• Chart builder view

This is the default view of the History Space node (in the nave tree). Use this view to build any one
of several types of chart options from the data that is stored in one or more histories. See “About the
chart builder view” for details.
• Database maintenance view
Use this view to clear records or delete histories. Refer to “About the database maintenance view” on
page 6-8 for more information about this view.
• Nav container view
Use this view to display all histories in the station. See “About the nav container view” on page 6-9
for more details about this view.

NiagaraAX-3.x
6-5
User Guide
Types of history space views Chapter 6 – About Histories
About the chart builder view May 1, 2007

About the chart builder view

The chart builder view displays in Workbench, in all Workbench (Wb)Web profiles, and with
NiagaraAX-3.2 and later, the Default Hx, and Basic Hx profiles, as well.
Note: The following description discusses the Chart Builder view in terms of the Wb Web and the desktop
Workbench display profiles. Stations using NiagaraAX-3.2, can display the Chart Builder view in the
browser using the Default and Basic Hx (non-Java applet) profile views. Views displayed using Hx look
different but behave very similarly to the Workbench view. All field descriptions apply to both views.
The Chart Builder Workbench view (also Wb Web profile view) is shown in Figure 6-11, the Chart
Builder Hx view is shown in Figure 6-12. Using this view, you can select the histories, title, and configure
the charts that you want to generate.

Figure 6-11 Chart builder view (NiagaraAX-3.1 and later)

Figure 6-12 Chart builder view (NiagaraAX-3.2 and later Hx Web profile)

The display of the Chart Builder view is divided into three primary areas:
• Display configuration fields
• Time Range
Select a time parameter option from the list, including an option that allows you to set a specific
time range using the Edit Time Range dialog box.
• Title
Type a title for your chart in this text field.
• Grid Lines
Select Show or Hide to show or hide grid lines on the history chart.
• Rollup
Rollup (or Rollup Interval) is an interval of time that is used to determine what (and how) data
is presented in your chart. Each point displayed, using the rollup, represents a designated time
interval before the specified plot time. A rollup value of 1 hour will present data at a granularity
level of every one hour, while a rollup value of 15 minutes will show data for every 15 minutes
of logged data. Rollup options are:
– Average
This option plots the average value for the selected rollup period.

NiagaraAX-3.x
6-6
User Guide
Chapter 6 – About Histories Types of history space views
May 1, 2007 About the chart builder view

– Min
This option plots the minimum value for the selected rollup period.
– Max
This option plots the maximum value for the selected rollup period.
– Sum
This option plots the total of the values in the selected rollup period.
• Histories pane
This is the lower left area of the Chart Builder view. It displays all histories that are available in your
local station or any station histories that you import by means of the Niagara network or other net-
work driver (for example, BacnetNetwork). Histories are grouped under the station by station name.
Double-click (Wb Web profile) or click (Hx Web profile) on a history name to copy it to the Current
Charts pane.
Note: The histories that are displayed in this pane are the same histories that are displayed under
the history space node in the Workbench nav sidebar.
• Current Charts pane
This pane displays the histories that are selected to be plotted. For each history, you may select the
type of chart to generate, using the chart type option list, as displayed in Figure 6-13.
Note: NiagaraAX-3.2 has more chart type options than earlier versions.
Adjacent to the histories in this pane are icon-type controls that allow you to reorder histories in the
pane or remove histories from the pane.

Figure 6-13 Current chart pane options and controls

• Control buttons
The following control buttons are located at the bottom of the Chart Builder view:
• Build button
Click this button to build the chart using the histories that are in the selected Current Histories
pane.
• Clear button
Click this button to remove all histories from the Current Histories pane.
Figure 6-14 shows an example of chart that displays two histories.

Figure 6-14 Two different history line charts using chart builder view (Wb and Hx Web profiles)

NiagaraAX-3.x
6-7
User Guide
Types of history space views Chapter 6 – About Histories
About the database maintenance view May 1, 2007

Figure 6-15 History pie chart and area chart using chart builder view

About Time Zones and the Chart Builder view

When charting multiple histories that include different timezones, the Chart Builder uses a “zoneless”
time range configuration so that it can plot each history with reference to its own timezone. This means
that the resulting charts are aligned by local time. For example, if you select a time range of 8:00 AM
through 5:00 PM for two histories—one in EST and another in CST—then the values at 8:00 AM align so
that the 8:00 AM values may be visually compared.

About the database maintenance view

The database maintenance view is shown in Figure 6-16. Using this view, you can clear records and delete
complete histories from your history database. Select the database maintenance view by selecting the
history space node in the nav sidebar and using the view selector menu or the popup menu to choose the
database maintenance menu item.

Figure 6-16 Database maintenance view

The left side of the histories area contains the available histories window. This window
displays all histories that are available in your local station or any station histories that you import by
means of the Niagara network or other network driver (for example, BacnetNetwork). Histories are
grouped under the station by station name.
Note: The available histories are the same histories that are displayed under the history space node in the nav
sidebar.
The right side of the histories area contains the targeted histories window. This window displays the
histories that are affected when you click the Run Maintenance button. Move the histories that you
want manage into this window using the control buttons, as described below:
Controls and options for the database maintenance view are described in the following list:
• Add history button (right arrow)
Click this button to move histories that are selected in the available histories window to
the targeted histories window.
• Remove history button (left arrow)
Click this button to move histories that are selected in the targeted histories window to the
available histories window.

NiagaraAX-3.x
6-8
User Guide
Chapter 6 – About Histories Types of history views
May 1, 2007 About the nav container view

• Clear Old Records option

Select this option and use the Before date selector to remove records, based on date, from the his-
tories that are in the targeted histories window.
• Before date field
Use this field with the Clear old records option to set the year, month, day, and time param-
eters that you want to use for removing old records.
• Clear all records
Select this option to delete all records from the selected history database.
• Delete Histories
Select this option to delete all histories that are in the targeted histories window.
• Run Maintenance button
Click this button to execute the option that you have selected on the histories in the targeted histo-
ries window.

About the nav container view

The nav container view is shown in Figure 6-17. This view displays a row for each station that is repre-
sented in the history space. You can double-click on any of the station icons to display the individual
histories that are children to the station that is represented in the Name column of the nav container
view. Double click on a history in this view to display the history in the History Chart view.

Figure 6-17 Nav container view

In this view you can select any history and switch to any other view of that history (see “Types of history
views” on page 6-9) using the view selector or the popup menu. In this view you can also rename histories,
using the popup menu.

Types of history views

You can view histories in different ways in Workbench. Figure 6-18 shows a menu of views that are
available using either the Workbench view selector or a view popup menu. These views are listed and
described in the following sections.

Figure 6-18 History views available from popup menu

• History Chart
This view shows a plotted chart of the history data. This is the default history view. Refer to “About
the history chart view” on page 6-10 for more details.
• History Table
This table shows a view of history data that you can export and view in the following formats: PDF,
CSV, Text. In addition, you can modify the tabular view of history data by choosing to show or hide
columns and by filtering the data based on date and time. Use the Table Options menu in the
top right corner of the history table to modify the history table view or to export the data in the view,

NiagaraAX-3.x
6-9
User Guide
Types of history views Chapter 6 – About Histories
Types of history data fields May 1, 2007

as desired.
• Collection Table
This view shows a table of any data (in this case history data) that you can export and view in the
following formats: PDF, CSV, Text. Use the Table Options menu in the top right corner of the
collection table to modify the table view or to export the data in the view, as desired.
• History Summary
This view shows a summary of the history’s status and configuration properties.
• History Editor
This view allows you to actually edit data and filter histories.

Types of history data fields

The following types of data are common to several history table views and appear as columns that may
be hidden or displayed using the Table Options menu. Refer to “Table controls and options” on page
2-17 for information about using the Table Options menu.
• Timestamp
This data field indicates the time that the recorded value occurred.
• Trend Flags
This data field displays trend flag information about the recorded data - for trend record types.
These flags provide extra context information about the record data. For example: “Start”,
“OutofOrder”, “Hidden”, “Modified”, and “Interpolated” are possible trend flags.
• Status
This data field displays the status of the history’s parent component; for example, “OK” or “null”.
• Value
This data field displays the record value.

About the history chart view

The history chart view plots the data of the selected history log along x and y axes. This is the default view
of the history, so if you double-click on a history in the nav sidebar, the history chart view will appear. An
example of the history chart view is shown in Figure 6-19.

Figure 6-19 History chart view

The history chart view contains the standard chart controls and options to help you customize and view
the data. Refer to “Chart controls and options” on page 2-18.

About the history table view

The history table view displays history records with columns of data that you can customize by displaying
or hiding selected columns. An example of the history table view is shown in Figure 6-20. Refer to “Table
controls and options” on page 2-17 for details about table controls and options that are common to many
table views.

NiagaraAX-3.x
6-10
User Guide
Chapter 6 – About Histories Types of history views
May 1, 2007 About the collection table view

Figure 6-20 History table view

In addition to a title bar that displays the history name and number of records in the table, the history
table has the following four columns that are described in “Types of history data fields” on page 6-10.
• Timestamp
• Trend Flags
• Status
• Value
Use the Table Options menu in the top right corner of the history table to modify the table view or
to export the data in the view, as desired. Refer to “Table controls and options” on page 2-17 for a
description of the Table Options menu.

About the collection table view

The collection table view displays records with columns of data that you can customize by displaying or
hiding selected columns. Refer to “Table controls and options” on page 2-17 for details about table
controls and options that are common to many table views.
An example of the collection table view is shown in Figure 6-21.

Figure 6-21 Collection table view

In addition to a title bar that displays the history name and number of records in the table, the history
table has the following four columns that are described in “Types of history data fields” on page 6-10.
• Timestamp
• Trend Flags
• Status
• Value
Use the Table Options menu in the top right corner of the history table to modify the table view or
to export the data in the view, as desired. Refer to “Table controls and options” on page 2-17 for a
description of the Table Options menu.

About the history summary view

The history summary view is shown in Figure 6-22. This view displays the details of the history’s status
and configuration properties in two groups, as follows:

NiagaraAX-3.x
6-11
User Guide
Types of history views Chapter 6 – About Histories
About the history editor view May 1, 2007

Figure 6-22 History summary view

• Status parameters
these parameters display data that is updated as of the time you select the history summary view.
• Record count
this is the current number of total records, as of the Last Timestamp.
• First Timestamp
this is the date, time and timezone information for the initial history record.
• Last Timestamp
this is the date, time and timezone information for the latest recorded history record.
• Configuration parameters
these parameters display data that identifies and characterizes the specific history. Refer to “Config-
ure history extensions” on page 6-16 (see the History Config bullet item) for a description of the con-
figuration parameters.

About the history editor view

An example of the history editor view is shown in Figure 6-23. The history editor view allows you to edit
data and filter histories. This view also allows batch editing (selecting multiple rows and using the popup
menu or the Edit menu).

Figure 6-23 History editor view

The history editor view is comprised of the following main areas:

• Title bar
this area displays the history name and number of records in the history.
• Toolbar icons
these icons are available on the toolbar when the history editor view is displayed. Refer to “About the
history editor toolbar icons” on page A-15 for descriptions of these toolbar icons.
• Time range options
this menu is located in the top left corner of the history editor view. You can select one of the pre-
defined times or select the Time Range option that allows you to set a specific time range using
the Edit Time Range dialog box.
• Table options menu
Use the Table Options menu in the top right corner of the history editor view to change which
columns are displayed or to export the data in the view, as desired. The history table op-

NiagaraAX-3.x
6-12
User Guide
Chapter 6 – About Histories About the history process
May 1, 2007 About the history editor view

tions menu includes the following items:

• Table columns
In addition to a title bar that displays the history name and number of records in the table, the history
table has the following four columns that are described in “Types of history data fields” on page 6-10.
• Timestamp
• Trend Flags
• Status
• Value
Use the Table Options menu in the top right corner of the history table to modify the table view
or to export the data in the view, as desired. Refer to “Table controls and options” on page 2-17 for
a description of the Table Options menu.
• Control buttons
The following two control buttons are used to initiate record editing in the history editor view:
• Edit
this button is available when one or more records are selected in the history editor table. When
you click this button, the Edit Records dialog box appears.
• Select Outliers
this button is available when the outlier configuration parameters are active (when the option
box is selected in the Configure Outliers dialog box). When you click this button, the
Configure Outliers dialog box appears.
Use the Table Options menu in the top right corner of the history table to modify the table view or
to export the data in the view, as desired. Refer to “Table controls and options” on page 2-17 for infor-
mation about using the Table Options menu.

About the history process

There are essentially three steps in the “history logging” life cycle, as shown in Figure 6-24:

Figure 6-24 Simplified history process

• collect
involves defining the parameters that specify what data will be recorded and when (or how often) it
will be recorded. For example, you can collect data whenever a change of value occurs - or at a reg-
ular time interval that you specify.
To collect history information you need to:
• Add history extensions to a component (refer to “Add history extensions to a component”)
• Configure the extensions (refer to “Configure history extensions” on page 6-16)
• Use a valid history name (part of configuration, see, “About history names” on page 6-17)
Refer to “Add history extensions to a component” on page 6-15 for more details.
• store
involves defining the parameters of the history database file. For example, you can customize the
name of the database file, define the maximum number of records to save, and choose metadata to
add to the records. Refer to “Configure history extensions” on page 6-16 for more details.
• archive (transfer)
includes importing and exporting records from one station to another station. For example, you can
limit your local station records to a small number that you specify and archive all records to another
station. Refer to “Archiving” on page 6-18 for more details.
You can add extensions to a component’s property sheet in order to extend the functionality of the
component. By adding a history extension, the real-time value or status of the component’s output can
be collected as a time-stamped entry in the associated history table. History extensions are available in
the history palette, as shown in Figure 6-25. The history table is not stored as part of the component’s
data but is a separate collection of data simply referred to as the history.

NiagaraAX-3.x
6-13
User Guide
About the history process Chapter 6 – About Histories
About delta logging May 1, 2007

Figure 6-25 History extensions

About delta logging

When you are logging data, such as electric consumption (kWh) or other information that uses a running
total, you may want to know the difference between consecutive timestamped values instead of the actual
running total. The delta logging feature is provided for this type of calculation. For delta logging, data is
logged (as normal) using the appropriate NumericChangeOfValue or NumericInterval extension. Then,
in the history chart or history table view, you simply select the Delta option box (or use the toolbar icon)
to display the delta values instead of the running total value, as shown in Figure 6-27. Delta values are
computed by taking the difference between one numeric record and the next. The timestamp of the last
record (of the two) is used as the timestamp for the delta value.

Figure 6-26 Delta logging history values

Two other parameters that apply to delta logging are related to the concept of rollover.
Rollover occurs when a running total reaches a defined maximum number and then resets to “zero” or
another defined number. The defined maximum number is represented in the history extensions by the
Max Rollover Value parameter. The reset value (which is often zero) is represented in the history exten-
sions by the Min Rollover Value parameter. These parameters allow you to specify the behavior of the
delta logging when the rollover occurs. If you do not know these values or if they are not specified, then
select the null option for these parameters.

NiagaraAX-3.x
6-14
User Guide
Chapter 6 – About Histories About the history process
May 1, 2007 Add history extensions to a component

Figure 6-27 Using rollover value parameters with delta logging

Consider the following example. If you are logging energy consumption with the Max Rollover Value
parameter set to 999,999 and the Min Rollover Value set to 100, then when a rollover is detected, the delta
logging bases its delta calculations on a maximum value of 999,999 and a subsequent initial value of 100.
Refer to “Configure history extensions” on page 6-16 for a list and short description of all the history
extension parameters.

Add history extensions to a component

Extensions come in different types to match the data type of the component and the collection method
desired. You can add history extensions by dragging them onto your property sheet or into your nav side
bar pane from the history palette (see Figure 6-29). Refer to “To add an extension to a component
property sheet view:” on page 12-16 for steps for adding an extension.

Figure 6-28 History extensions in Workbench the history palette

Figure 6-29 History extensions in the property sheet

Extension types include:

• BooleanChangeOfValue
used to collect boolean values whenever those values change.
• BooleanInterval
used to collect boolean values at specified time intervals.
• NumericChangeOfValue
used to collect numeric values whenever those values change.

NiagaraAX-3.x
6-15
User Guide
About the history process Chapter 6 – About Histories
Configure history extensions May 1, 2007

• NumericInterval
used to collect numeric values at specified time intervals.
• EnumChangeOfValue
used to collect integer values (enumerations) whenever those values change.
• EnumInterval
used to collect integer values (enumerations) at specified time intervals.
• StringChangeOfValue
used to collect a string of characters whenever the characters change.
• StringInterval
used to collect a string of characters at specified time intervals.
For more details about extension types, refer to “Types of history extensions” on page 3-14.

Configure history extensions

When a history extension is first added to a component, it is set to be disabled by default. All that is really
necessary to enable collection is to change the 'Enable' property to 'true.' Of course, you may desire some
other property changes to better configure the collection to suit your actual needs.
Some configuration properties are common among all history extension types. A few properties are
unique to the data type or the collection type. Following, is a list of all the properties available.
• Status
read-only field that tells the user the current status.
• Fault Cause
read-only field that displays a reason that the extension is not working.
• Enabled
set either 'true' or 'false' to disable or enable the history extension.
• Active Period
specifies the days of the week as well as start and end times for record collection.
• Active
read - only value that indicates whether or not (true or false) the history collection is active (as de-
fined by the Active Period parameters.
• History Name
is a formatting convention used to provide a way to consistently name histories using a standardized
formatting pattern.
The history name format field provides a way to automatically name histories any time a new history
is created. The format %parent.name% is the default history name format and this will create a
name based on the parent object. Refer to “About history names” on page 6-17 for more details about
naming histories.
• History Config
These properties set up the attributes of the History record.
• Id
a unique identification for each history. The id value is the name that was automatically created
by the History Name Format or manually created in the name field or rename dialog box.

Figure 6-30 History Id

• Source
a read-only field that displays the ORD of the active history extension.
• Time Zone
a read-only field that displays the time zone of the active history extension.
• Record Type
displays the data that the record holds in terms of: extension type (history) and data type:(Bool-
eanTrendRecord, NumericTrendRecord, and so on).
• Capacity
allows you to set a finite number of records to collect or to choose to collect an unlimited num-
ber of records. If you choose the Record Count option, an additional “records” field displays.
In the “records” field, type in the maximum number of records that you want to save in the his-
tory database.
• Full Policy - (Roll or Stop)
allows you to choose what to do when the Capacity number is reached. The Roll option drops
off the oldest record to make room for the newest record. The Stop option simply causes the

NiagaraAX-3.x
6-16
User Guide
Chapter 6 – About Histories About the history process
May 1, 2007 About history names

history to stop recording.

• Interval
a read-only field that displays the selected collection type: regular on interval.
• valueFacets
allows you to use the Edit Facets dialog box to choose how you want to display the logged data.
• Change Tolerance
for COV based collections, the monitored variable has to change at least this much to be logged as a
changed value.
• Interval
for Interval-based collection, the cycle time, or how often the history parameters are checked. Any
time you change this parameter, a new history is created (or “split-off”) from the original history be-
cause histories with different intervals are not compatible.
• minRolloverValue
this is a number that is used as the starting point for calculations for cumulative logging after a roll-
over. Rollover occurs after a running total maximum value is reached. Select the null option if a
minRolloveValue is unknown. Refer to “About delta logging” on page 6-14 for more details about
rollover and delta logging.
• maxRolloverValue
this is a number that is used as a maximum value for calculations when a rollover is detected by the
history logging process. Using this parameter and the minRolloverValue parameter helps you avoid
getting negative numbers when you are logging running total data, such as energy usage. Refer to
“About delta logging” on page 6-14 for more details about rollover and delta logging.
• precision
this option allows you to select 32 bit or 64 bit options for the history data logging. 64 bit allows for
higher level of precision but consumes more memory.

About history names

By default, when a history extension is added to a component, a history format default string is set to the
following: “%parent.name%”. This string automatically names any histories with the name of the parent
component and appends a sequential number to additional names, as necessary. For example, a history
extension on a NumericWritable component will, by default, create a history name “NumericWritable” -
then if that component is duplicated, the name for the history will be duplicated and incremented to
“NumericWritable1”. You may add a literal name in front of, or after, the “%parent.name%” string, as
shown in Figure 6-31, to customize it without losing the automatic naming feature.
Note: If you use a literal name and not a script to name a history, you lose the automatic incrementing feature
that the script provides. Duplicating extensions that have a literal name duplicates the exact literal name
and therefore creates an invalid (non-unique) name. In this case, you must rename each duplicated history
manually to create a unique name and avoid a fault condition.

Figure 6-31 History naming relationships

As described in “Configure history extensions” on page 6-16, and illustrated in Figure 6-30, history names
are part of the unique history extension property “Id”. When you rename a history at the history
extension, you are renaming the history at its “source”. Therefore, the history configuration and the
history Id both change. This concept is illustrated in Figure 6-32.

NiagaraAX-3.x
6-17
User Guide
About the history process Chapter 6 – About Histories
Archiving May 1, 2007

Figure 6-32 Renaming a history in the history extension

If, however, you rename a history in a “history space” view, such as under the history space node in the
nav sidebar, or in the nav container view, you are changing the name of the history as it has been saved in
the history space–not at the configuration (or origination) level. Therefore, the history Id is not changed
and the history extension continues to produce records under the original history name as long as that
history extension is active and enabled. This results in a history “split”; the newly-named history is no
longer updated, as of the time of the renaming, but it contains all the records up to that time. In this
scenario, a history under the original name begins with the first record after the renaming and continues
recording as configured. This concept is illustrated in Figure 6-33.

Figure 6-33 Renaming a history in the history space

Renaming Summary:
• No history split
If you rename a history in either the property sheet view or the history extension manager view, you
are editing the actual history extension and therefore not forcing a history split.
• History split
If you rename a history in either the nav side bar view or the nav container view you are editing the
name in the history space and not actually changing the history ID – the history is split.

Archiving
Archiving is the process of saving a history out to a different location (station) from where it was origi-
nated. There are two general methods (or directions) for archiving, as described below:
• Pushing data (exporting histories)
is the process of exporting history data and is done using the history export manager, shown in
Figure 6-34. For details about exporting histories, refer to “History Export Manager” on page 4-41.

Figure 6-34 Niagara history export manager

NiagaraAX-3.x
6-18
User Guide
Chapter 6 – About Histories About editing history data
May 1, 2007 Archiving

• Pulling data (importing histories)

is the process of importing history data and is done using the history import manager, shown in
Figure 6-35. For details about importing histories, refer to “History Import Manager” on page 4-37.

Figure 6-35 Niagara history import manager

About editing history data

The history editor view, as described in “About the history editor view” on page 6-12, provides the ability
to review and modify the history data that you have collected.
In some cases, you may want to search through the history data and look for unusual data or “outliers.”
An “outlier” is a data value that is far apart from the rest of the data; an extreme value that is either much
lower or much higher than the rest of the values in the data set. Outliers are known to skew means or
averages, so it may be helpful to identify and edit or hide this data. This doesn’t mean that the data point
is necessarily bad – but in most cases the information is more helpful without the inclusion of this
“unusual” data.

Caution It is possible to alter good data and miss filtering some bad data points using the history editor view.

Workbench provides the ability to find and edit outliers based on parameters that you specify. The
Configure Outliers dialog box, shown in Figure 6-36, appears when you click the Configure
Outliers icon in the toolbar menu. Refer to “About the history editor toolbar icons” on page A-15 for
a list of toolbar icons specific to the history editor view.

Figure 6-36 Configure Outliers dialog box

• Configure Outliers check box

Outlier filtering is disabled by default. Select the check box to enable the outlier filtering feature and
use the parameters that are displayed in the dialog box. Clear the check box to disable outlier data
filtering. When outlier parameters are enabled, the Window and the Percent of Std Devia-
tion fields are available and allow you to specify the “intensity” of the search for outliers in the data.
• Window
Enter an integer in the Window field to define the number of surrounding data points to consider
when determining whether a given point is an outlier. For example, if you use the default value of
“4”, it will look at the two points before and after the point under investigation (PUI). This is a sur-
rounding “window” of 4 points–from which a standard deviation will be calculated and used with
the percentage parameter, as described, below.
• Percentage
Enter a value in this field to specify the percent of standard deviation (calculated from the window
of points) to apply for identifying whether or not the PUI should be considered a valid value (not an
outlier). If the PUI falls outside of this valid range, then it is considered to be an outlier and its value

NiagaraAX-3.x
6-19
User Guide
About editing history data Chapter 6 – About Histories
Archiving May 1, 2007

is replaced by the linear interpolation of the surrounding 2 valid points. If the PUI falls within the
range, then the data point is used and considered valid.

NiagaraAX-3.x
6-20
User Guide
 CHAPTER 7
About alarms
Figure 7-1 Typical alarm table display

Alarms notify personnel that a predefined set of parameters has been met. Typically, these are
“offNormal” or “Fault” parameters that are configured to notify specified recipients about the specified
condition and to record the conditions that exist when the monitored point meets these parameters. The
“normal” parameters for an individual point are properties that may be set and edited, as desired, by a
user with proper access and privileges.
• Alarm
An alarm is used to indicate that some value is not within an appropriate or expected range. For ex-
ample, the normal operating temperature range of a device may be 70 to 100 degrees F. You can set
the “out of range” parameters to generate an “alarm” if the operating temperature exceeds the upper
limit or goes below the lower limit of this range.
• Alert
This is an alarm that does not have a “normal” state. For example, a motor may require lubrication
after every 400 hours of operation (this is not an “out of range” condition). Using the alarming func-
tion in Workbench, you can configure an extension to send an email alert to you when the 400 hours
runtime has accumulated on the motor.
Alarm examples
The following are examples of possible ways that alarms are used:
• Out of operating range notification (offNormal)
An alarm is most commonly used to indicate that some value is not within an appropriate or expect-
ed range. For example, the normal operating temperature range of a device may be 70 to 100 degrees
F. You can set the “out of range” parameters to generate an “alarm” if the operating temperature ex-
ceeds the upper limit or goes below the lower limit of this range.
• Advisory notification (alert)
You may use an alarm in situations to report on a parameter that does not really have a “normal”
state. For example, a motor may require lubrication after every 400 hours of operation (this is not an
“out of range” condition). Using the alert function, a system integrator can setup an control point
that monitors accumulated device run-time and sends an email alert notification at or before the 400
hours run-time has occurred.
• Device fault notifications (fault)
Some devices may report values that are so far out of range that it is obvious that there is a device or
system “fault” that needs attention. For example, if a device with a normal operating temperature of
between 70 to 100 degrees reports a temperature of 0 degrees F or 1000 degrees F, then it is probable
that there is a device or system fault and that the reported temperature is not the actual temperature
at the device. The system engineer or supervisor can set parameters and enable alarms for a separate
notification for values that are judged to be “faults” as opposed to simply “out of range”.

NiagaraAX-3.x
7–1
User Guide
Overview of the alarming process Chapter 7 – About alarms
May 1, 2007

Overview of the alarming process

Each alarm is a single record in the alarm database that changes throughout its life cycle. An alarm has
four general “life cycle” states that it may be in:
•
new alarm
is the initial state of an alarm and this state remains in effect until that alarm is acknowledged.
• acknowledged alarm
is an alarm that has been acknowledged by the recipient. Acknowledged alarms may be normal
alarms.
• normal alarm
is an alarm that has a current status of “normal”.
• acknowledged normal alarm
is a normal alarm that has been acknowledged.
Note: An “Open Alarm” is an alarm that is in normal status and is not acknowledged (or acknowledged and in
alert status).
Typically, an alarm provides some visual and audible indication that a limit or value is met or exceeded.
Alarm notifications may be routed and displayed in a variety of ways, including the following:
NiagaraAX alarming is comprised of three primary actions:
• Creating alarms (refer to “About alarm sources” on page 7-3)
• Routing alarms (refer to “About the alarm service” on page 7-6)
• Managing alarms (refer to “About the alarm database maintenance view” on page 7-13

Figure 7-2 Simplified alarm process

Under these three processes NiagaraAX provides highly specific and flexible alarming life cycle
management, including the following alarming functions:
• creating alarms
Alarms are generated by components using an alarm extension (refer to “About alarm extensions
and components” on page 7-3). The alarm extensions create the alarm whenever specified values are
outside of “normal” range. Those alarms are then handled by the alarm service (refer to “About the
alarm service” on page 7-6).
• routing alarms
Alarms are handled by the alarm service which, in addition to allowing you to specify routing des-
tinations (including archiving destinations), provides notification and acknowledgement parame-
ters.
• notification
Alarms are routed to one or more recipients based on their alarm class. This includes notifica-
tion by email, at the alarm console, a lineprinter, or at remote stations.
• acknowledgment
Alarms may require a response from those who are notified. If a required acknowledgement is
not received within an optionally-specified time, alarms can be “escalated” and re-routed to
other designated alarm recipients.
• managing alarms
alarms are archived in records that are managed by the alarm database management interface.
The following list outlines the basic steps in the alarming process:
• add alarm extensions to components
Choose alarm extensions to match the component data type.
• configure alarm extensions
Configure the alarm parameters to define when a component is in an alarmed state.
• route alarms
Configure the alarm parameters to define where an alarm record is sent.
• manage the alarm archive
Use the alarm archive management tools to manage the storage of all alarms.

NiagaraAX-3.x
7-2
User Guide
Chapter 7 – About alarms About alarm sources
May 1, 2007 About alarm extensions and components

About alarm sources

The parameters that are set in a point’s “alarm point extension” determine when that point is in an
“alarmable” condition. You use the alarm extension to configure routing options, issue alarms to the
alarm service, and update the alarm to reflect a status change when the parent point goes back to a normal
state. The extension also notifies the point that an acknowledgement has been received. To set up the
alarm source on an object you need to:
• add a proper alarm extension to the component (see About alarm extensions and components)
• configure the alarm extension to meet your needs (see About alarm extensions)

About alarm extensions and components

To set up alarming on a component you need to add an alarm extension to the component’s property
sheet. Refer to “About alarm extensions” on page 3-12 for more details about the alarm extensions. Alarm
extension types must match their parent component type. For example, an OutOfRangeAlarmExt goes
with a Numeric point type and a BooleanChangeOfStateAlarmExt goes with a Boolean point type. For a
list of alarm extensions types and their associated point types, refer to “Types of alarm extensions” on
page 3-12.
Alarm extensions are contained in the alarm Palette, as shown in Figure 7-3.

Figure 7-3 Alarm extensions in alarm palette

For details on adding extensions to a property sheet, see “To add an extension to a component property
sheet view:” on page 12-16. Once the extension is added, configure the extension to meet your alarming
requirements. Refer to “About alarm extension properties” on page 7-3 for more details.

About alarm extension properties

Each alarm extension has a set of configurable properties that allow you to specify the alarming condi-
tions and certain routing options. Figure 7-4 illustrates and the following list describes each alarm
extension as it appears in a component property sheet.

NiagaraAX-3.x
7-3
User Guide
About alarm sources Chapter 7 – About alarms
About alarm extension properties May 1, 2007

Figure 7-4 Alarm extension properties

Following, are the alarm extension properties descriptions:

• Alarm Inhibit
A true value in this field prevents alarm generation due to any transition or state change.
For example, if there is a true value in this field and an Offnormal value is reached, a “toOffNormal”
status will not be communicated. When the state returns to Normal, a “toNormal” status will also
not be communicated. A false value in this field will prevent alarms from being inhibited (even if
an Inhibit Time is set).
Note: The purpose of the Alarm Inhibit property is to prevent unintended alarms, such as in after-
hours situations where a piece of equipment is turned off. A difference between Alarm Inhibit and
Alarm Delay is that the Alarm Inhibit is a boolean value (true/false) and may be controlled by
another device (for example, an ON/OFF value of a fan).
If the Alarm Inhibit value is set to true, the Inhibit Time property qualifies the behavior.
• Inhibit Time
The value of this property affects the length of time that the current Alarm Inhibit state will remain
in effect after an Alarm Inhibit state change. For example, when an Alarm Inhibit value changes from
true to false, alarm generation continues to be inhibited for a time that is specified by the Inhibit
Time property value. When an Alarm Inhibit value changes from false to true, alarm generation
may continue to be inhibited for a time that is dependent on the point type, as shown in Table 7-1.

Table 7-1 Time until Alarm Inhibit state change affects alarm generation
Alarm Inhibit tran- Point type
sition Discrete point Numeric point
True to False Inhibit Time property value Inhibit Time property value
False to True 3 x Inhibit Time property value 0 (zero)
• Alarm State
This field displays the current alarm state of the component: Normal, Low Limit, High Limit, Fault.
• Time Delay

NiagaraAX-3.x
7-4
User Guide
Chapter 7 – About alarms About alarm sources
May 1, 2007 About alarm extension properties

Note: Time Delay does not affect alarms generated by a Fault. There is no delay when transitioning
in or out of a Fault generated alarm.
This is the minimum time period that an alarm condition must exist before the object alarms. In oth-
er words, the object status must meet the “alarm” criteria for a continuous period equal to or greater
than defined in the Time Delay property value before an alarm is generated. The general purpose of
the Time Delay property is to provide a means to prevent nuisance alarms that may be caused by a
momentary change in a state value (Normal, Low Limit, High Limit).
Time Delay applies to properties that transition both in and out of alarm states. Therefore, an alarm
status may continue to display as Offnormal (for example) for a time (equal to the Time Delay) after
the value has come back into Normal parameters. The Time Delay is the minimum time period that
a normal condition must exist before the object comes out of alarm.
Note: Typically, when both Alarm Delay and Alarm Inhibit properties are used, Time Delay is less
(shorter) than Alarm Inhibit.
• Alarm Enable
Select any of the options to individually enable the generation of alarms when the following transi-
tions occur:
• toOffnormal
This is the time that the offNormal event occurred.
• toFault
This is the time that the Fault event occurred
Note: No alarms will be generated unless an Alarm Enable option is selected.
• To Offnormal Times
This property displays four pieces of information that are related to the time that the component sta-
tus changed to Offnormal. A “null” value means that the event has not occurred. See Figure 7-5.
• Alarm Time
This property displays the time that the To Offnormal event occurred.
• Ack Time
This property displays the time that the alarm was acknowledged.
• Normal Time
This property displays the time that the To Normal event occurred.
• Count
This field displays the total number of Offnormal events.

Figure 7-5 To Offnormal times

• To Fault Times
This property displays four pieces of information that are related to the time that the component sta-
tus changed to a Fault state. A “null” value means that the event has not occurred. See Figure 7-6.
• Alarm Time
This property displays the time that the To Fault event occurred.
• Ack Time
This property displays the time that the alarm was acknowledged.
• Normal Time
This property displays the time that the To Normal event occurred.
• Count
This field displays the total number of To Fault events.

Figure 7-6 To Fault times

• To Normal Times
This property displays the time that the component transitioned to a normal state.

NiagaraAX-3.x
7-5
User Guide
About the alarm service Chapter 7 – About alarms
About alarm instructions May 1, 2007

• Time in Current State

This property displays the elapsed time since the component transitioned to the current state.
• Source Name
This property displays the name of the alarm source. If you use the default script setting %parent.dis-
playName%, the source name field will show the “display name” of the alarm extension parent. You
can edit this script or type in a literal string to display.
• To Fault Text
This property enter the text that you would like to display when the component is in a fault state.
• To Offnormal Text
This property enter the text that you would like to display when the component is in a Offnormal
state.
• To Normal Text
This property enter the text that you would like to display when the component is in a Normal state.
• Hyperlink Ord
Use this property enter or choose an Ord, a BQL Query or a path to a component that you would
like to associate with an alarm status on the component you are configuring. When an alarm is re-
ported in the console, the Hyperlink button is active and uses this path. Use the folder icon to browse
to the file that you want to link to. Click the arrow icon to the right of the folder icon to test the Ord
that you enter.
• Sound File
This property enter or choose the path to a sound file that will execute when the current component
is in an alarm state. Use the folder icon to browse to the file that you want to use. Click the arrow
icon to the right of the folder icon to test the path that you enter.
• Alarm Icon
Use this property to enter or choose the path to a graphic file that will added to the display in the
“timestamp” column of the alarm table in the Console Recipient view. Use the folder icon to browse
to the file that you want to use. Click the arrow icon to the right of the folder icon to test the path
that you enter.
• Fault Algorithm
This property when available, displays fault parameters. Different options are available here, de-
pending on the alarm extension being used.
• Offnormal Algorithm
Use this property to enter high and low limit parameters for numeric components and select the
alarm value (on or off) to designate the alarm state for a boolean component. Different options are
available here, depending on the alarm extension being used.
• Alarm Class
Use this property to select an alarm class from the option list. The alarm class specifies the alarm
routing options for this component. Refer to “About alarm class” on page 7-15 for details about alarm
class.
• Meta Data
Use this property to enter new facets using the meta data property. See “About point facets” on page
3-7 for details about facets.

About alarm instructions

Each alarm can have “instructions” assigned to it so that any time an alarm is generated, the instructions
are presented with the alarm notification to provide information that may be important or helpful to the
user. Instructions are created, assigned, and edited from the Instructions view. Refer to “About the
Instructions Manager view” on page 11 for details about the Instructions view.

About notes
Notes are simple text entries that are associated with a particular alarm. It is possible to add a Note to one
alarm or to multiple alarms. Alarm records that have notes are indicated by a “note” icon”. Refer to “Types
of alarm details view dialog boxes” on page 20 for more information about Notes.

About the alarm service

Note: In addition to the standard file-based alarm service, described in this section, there is a memory alarm
service available. These two services should not run in the same station. Refer to “About memory alarm
service” on page 7-7 for details about the memory alarm service.

NiagaraAX-3.x
7-6
User Guide
Chapter 7 – About alarms About memory alarm service
May 1, 2007 About notes

Each station may contain a single alarm service that coordinates the routing of alarms within the
NiagaraAX framework and maintains the alarm database. The alarm service is available in the alarm
palette, as shown in Figure 7-7.

Figure 7-7 Alarm service in the alarm palette

If you do not have the alarm service in your active station, you can add it by dragging and dropping a copy
from the alarm palette, as shown in Figure 7-8.

Figure 7-8 Adding the alarm service

The alarm service may contain one or more alarm classes (refer to “About alarm class” for more infor-
mation about alarm class). An alarm class may route alarms to one or more alarm recipient types (refer
to “Types of alarm recipients” on page 7-18 for more information about alarm recipient).
The routing process includes getting alarm acknowledgements from the recipients back to the source,
and alarm notifications from the source to the recipients. The default view (wire sheet view) of the alarm
service makes it easy to visualize the relationships between the alarm class and the alarm recipient. These
relationships are created by linking the alarm class to the alarm recipient, as described in “About alarm
class” on page 7-15. In addition to the wire sheet and property sheet views, there are several other views
of the alarm service. See “Types of alarm service views” on page 7-9 for a description of the alarm service
views.

About memory alarm service

Note: MemoryAlarmService is an alarm service that provides an alternative to the standard file-based Alarm-
Service. A station should have only one alarm service. Do not enable both the standard AlarmService and
MemoryAlarmService on the same station.
Each station may contain a single alarm service that coordinates the routing of alarms within the
NiagaraAX framework. The memory alarm service is available in the alarm palette, as shown in Figure 7-
9.

Figure 7-9 Memory alarm service in the alarm palette

NiagaraAX-3.x
7-7
User Guide
Common alarm controls and indicators Chapter 7 – About alarms
About notes May 1, 2007

If you do not have the memory alarm service in your active station, you can add it by dragging and
dropping a copy from the alarm palette, as shown in Figure 7-8.

Figure 7-10 Adding the alarm service

Like the alarm service, the memory alarm service may contain one or more alarm classes. An alarm class
may route alarms to one or more alarm recipient types.
The routing process for the memory alarm service is the same as the standard file-based alarm service
and includes alarm acknowledgements from the recipients back to the source, and alarm notifications
from the source to the recipients. The default view (wire sheet view) of the alarm service makes it easy to
visualize the relationships between the alarm class and the alarm recipient. These relationships are
created by linking the alarm class to the alarm recipient, as described in “About alarm class” on page 7-
15. The memory alarm service has the same views available as the standard alarm service.
The main distinction of MemoryAlarmService is that when you use this service, alarms are not stored
persistently on the station host (typically a JACE) as they are with the standard file-based alarm service.
Choosing MemoryAlarmService might be appropriate for situations where you do not want to keep a
large store of alarms on your host and are looking primarily for immediate alarm notifications. Alarm
records are stored in memory and therefore they are lost in the case of a power failure.

Common alarm controls and indicators

The following alarm controls and indicators are common to several alarm views:
• Alarm control buttons
The following buttons appear in one or more alarm views:
•
Use the Acknowledge button to acknowledge all selected alarms.
•
Use the Hyperlink button to change the current view to the hyperlinked target associated
with the selected alarm. If no hyperlink is associated with the alarm, the Hyperlink button is not
available.
•
Click the Notes button to display the Notes dialog box and add a note to the selected alarm
or alarms.
•
Click the Silence button to stop the audible notification associated with the selected alarm.
•
Click the Filter button to display the Filters dialog box for setting the filter parameters.
•
Click the Close button to cancel the current interface actions without saving changes.
• Alarm icons
Alarm icons appear with color coding and symbolic images:
• A red alarm icon in the table indicates that the current state of the alarm source is not
“offnormal” and “not acknowledged”.
• An orange alarm icon in the table indicates that the current state of the alarm source is
“alert” and is “not acknowledged”.
• A yellow alarm icon in the table indicates that the current state of the alarm source is “not
acknowledged” and “acknowledged”.
• A green alarm icon in the table indicates that the current state of the alarm source is “nor-
mal” and “not acknowledged”.

NiagaraAX-3.x
7-8
User Guide
Chapter 7 – About alarms Types of alarm service views
May 1, 2007 About alarm extension manager

• A white alarm icon in the table indicates that the current state of the alarm source is “nor-
mal” and “acknowledged”.
• A note alarm icon (it may be any color) in the table indicates that there is a note associated
with the alarm
• A link icon in the table indicates that the alarm has a link associated with it. When an alarm
displays this icon, the Hyperlink button is also active.
• An optional icon may display if it is setup in the alarm properties. If included, this graphic
appears at the left end of the alarm record row.

Types of alarm service views

You can view the alarm service in different ways in Workbench. Figure 7-11 shows a menu of views that
are available using either the Workbench view selector or a popup menu.

Figure 7-11 Alarm service views available from popup menu

In addition to the standard Workbench views (Wire Sheet, Category Sheet, Slot Sheet, Link Sheet) there
are several views specific to the alarm service, including the following:
• Alarm Extension Manager view
The alarm extension manager is a view of the alarm service that provides a record of information
about each alarm extension. See “About alarm extension manager” on page 7-9 for details.
• Instructions Manager view
The Instructions Manager view provides a way to view, assign, and edit the instructions that can be
assigned to alarms. See “About the Instructions Manager view” for details.
• Alarm Class Summary
The alarm class summary view provides a concise list of information relative to each alarm class. Re-
fer to “About the alarm class summary view” on page 7-12
• Alarm Database Maintenance
“About the alarm database maintenance view” on page 7-13
• Alarm Service Property Sheet
The alarm service property sheet is a typical Workbench property sheet view that shows all the alarm
service slots. See “About alarm service property sheet” for details.

About alarm extension manager

The alarm extension manager view presents alarm extensions in a table format to make it easy for you to
see all the alarm extensions that are associated with points in your station. As with other tables, you can
show or hide columns and use other standard table controls and options that are provided in the Table
Options menu. The Table Options menu is located in the top right corner of the table and is
described in “Table controls and options” on page 2-17. Also, the export toolbar icon is available on the
toolbar when the alarm extension manager view is displayed.
An example of the alarm extension manager is shown in Figure 7-12.

NiagaraAX-3.x
7-9
User Guide
Types of alarm service views Chapter 7 – About alarms
About alarm extension manager May 1, 2007

Figure 7-12 Alarm extension manager

The alarm extension manager view provides the following data fields:
• Point
This field indicates the point that is the parent of the listed alarm extension.
• Extension
This field identifies the type of extension that is listed (for example: “OutOfRangeAlarmExt”, Status-
AlarmExt”, or others).
• Alarm State
This field displays the status of the listed alarm extension; for example, “High Limit” or “Normal”.
• toOffnormal Enabled
This field indicates (as True or False) if the toOffnormal parameter of the extension is enabled (true)
or not (false).
• toFault Enabled
This field indicates (as True or False) if the toFault parameter of the extension is enabled (true) or
not (false).
• Alarm Class
This field identifies the name of the alarm class that the extension is assigned to (defaultAlarmClass
or other class).
Types of extension manager display features
Extension manager display features include:
• Color coding
A colored background on a row in the alarm extension manager table indicates that the alarm state
of the parent component is not Normal.
• Hyperlinking
Double-click on any row in the Alarm Ext Manager view and the view will change to the property
sheet view of the alarm extension that you clicked on.
• Alarm extension editing (and batch editing)
Select one or more (for batch editing) alarm extensions and use the popup menu (shown in Figure 7-
13) to edit the extension(s).

Figure 7-13 Alarm extension manager popup menu

Edit alarm extensions from the alarm extension manager in the following ways:
• toOffnormal Enabled and toFault Enabled settings
You can toggle ON and OFF the toOffnormal Enabled and toFault Enabled param-
eters of each selected alarm extension using the popup menu.
• Edit Alarm Class
You can change the alarm class assignment of the alarm extensions. Select single or multiple
(for batch editing) and from the popup menu select the Edit Alarm Class menu item.
Choose the desired alarm class from the option menu and click the OK button to change the
alarm class setting for the selected alarm extension(s).

NiagaraAX-3.x
7-10
User Guide
Chapter 7 – About alarms Types of alarm service views
May 1, 2007 About the Instructions Manager view

About the Instructions Manager view

The Instructions Manager view displays a standard table-type report that provides a way to view, assign,
and edit alarm instructions. The view is comprised of three primary panes:
• Points
This pane is located in the left half of the Master Instructions view and displays all points that are
currently available for instruction assignment or editing. These points may have instructions as-
signed to them or they may have no instructions—they are simply the points that are available. The
“Point” column contains the name of the control point source associated with the alarm and the
“Conditions” column provides the name of property that is holds the alarm instructions.
Note: You can select more than one point at a time by using the Shift key or Ctrl key. If the alarm
instructions for all selected points are identical, then all associated instructions display in the Point
Instructions pane. If there are any differences in alarm instructions for the selected points, no instruc-
tions display.
• Point Instructions
This pane is located in the top right portion of the Assign Instructions dialog box and it in-
cludes a list of instructions that are associated with the point or points currently selected in the
Points pane.
You can add, remove, reorder, or edit instructions in this pane using the following controls:
Note: Always remember to click the Save button immediately after making any changes.
• Add
Clicking the Add button produces the Add dialog box that allows you to type in the text for an
instruction.
• Remove
Select an instruction then click the Remove button to delete the instruction.
• Edit
Select an instruction and then click the Edit button to open a dialog box that allows editing of
the selected instruction.
• Save
Clicking the Save button commits any changes made to the point instructions. The Save action
applies to all instructions and all points that are selected when the Save button is clicked.
Changes are lost if the screen or if just the pane is refreshed before saving.
• Move Up and Move Down
Select an instruction in the point instruction window, then click either the Move Up or Move
Down button to reorder the instructions in the window.
• Master Instructions List
This pane is located in the lower right portion of the Instructions Manager view and it displays all
master instructions that are available for adding to the Point Instructions pane. Master Instructions
allow you to choose and assign a pre-listed set of instructions to one or more points.
Note: You can select more than one Master Instruction at a time using the Shift key or Ctrl key. If
the alarm instructions for all selected points are identical, then all associated instructions display in
the Point Instructions pane. If there are any differences in alarm instructions for the selected points,
no instructions display.
To add or remove one or more Master Instruction to one or more selected points, first select the
Master Instruction(s) in the Master Instructions list and then click the Add From Master List
button. Be sure to click the Save button immediately after making any edits.
Figure 7-14 shows an example of the Instructions Manager view with one point and one master in-
struction selected. You can Add, Remove and Edit Master Instructions using the following controls:
• Add
Clicking the Add button produces the Add dialog box which allows entering a text instruction to the
Master Instructions list. The master instructions list allows you to enter instructions that are avail-
able to be assigned to any alarms. After entering instructions in the Master Instruction list, the in-
structions are available to be added to individual selected point instructions by first selecting the
instruction in the list and then clicking the Add From Master List button.
• Remove
Select an instruction in master instructions list and then click the Remove button to delete the in-
struction.
• Edit
Select an instruction and then click the Edit button to open a dialog box allowing the instruction
to be modified.

NiagaraAX-3.x
7-11
User Guide
Types of alarm service views Chapter 7 – About alarms
About the alarm class summary view May 1, 2007

Figure 7-14 Instructions Manager view with one point and one master instruction selected

About the alarm class summary view

The alarm class summary view provides a tabular presentation of data associated with all alarm classes
that are assigned to the alarm service. As with other tables, you can show or hide columns and use other
standard table controls and options that are provided in the Table Options menu. The Table
Options menu is located in the top right corner of the table and is described in “Table controls and
options” on page 2-17. Also, the export toolbar icon is available on the toolbar when the alarm class
summary view is displayed.
An example of the alarm class summary view is shown in Figure 7-15.

Figure 7-15 Alarm class summary view

The alarm class summary view has the following data fields:
• Name
This data field displays the alarm class name.
• Open
This data field displays the total number of open alarms associated with the alarm class.
• In Alarm
This data field displays the total number of alarms (points currently in alarm) associated with the
alarm class.
• UnAcked
This data field displays the total number of unacknowledged alarms associated with the alarm class.
• Last Alarm
This data field displays the timestamp of the last alarm associated with the alarm class.
• alarm.Class.priority
This data field lists the priority of each alarm transition type. For example, “toOffnormal=1”, “to-
Fault=60”, “toNormal=220”, and so on.
• To Path String
This data field identifies (as a string value) the path to the alarm class.
Alarm class summary view display features include:
Note: You can double-click on any row in the view and the view will change to the property sheet view of the alarm
class that you clicked on. You can also use the popup menu to select a view.

NiagaraAX-3.x
7-12
User Guide
Chapter 7 – About alarms Types of alarm service views
May 1, 2007 About the alarm database maintenance view

About the alarm database maintenance view

The alarm database maintenance view presents alarm data in a table view to make it easy to view and edit
the alarm database. As with other tables, you can show or hide columns and use other standard table
controls and options that are provided in the Table Options menu. The Table Options menu is
located in the top right corner of the table and is described in “Table controls and options” on page 2-17.
Also, the filter icon and the notes icon appear on the workbench toolbar when the alarm database
maintenance view is displayed.
An example of the alarm database maintenance view is shown in Figure 7-16.

Figure 7-16 Alarm database maintenance view

The Alarm Database Maintenance view has two main sections:

• Alarm History table
This table fills the upper part of the view and contains a table of alarm history records.
• Maintenance controls pane
These controls are located below the table pane and contain the following controls and parameter
options:
• Clear Old Records option
allows you to clear alarm records before a certain date and time. The Before field is provided
to allow you to set the date and time for removing old records.
• Clear All Before Selected Record option
allows you to delete all records that have a timestamp earlier than the timestamp of the record
that is currently highlighted in the table.
• Clear All Records options
allows you to delete all records, regardless of the date.
• Run Maintenance button
This button initiates the maintenance action.
The alarm database maintenance view has the following properties:
• UUID
This data field displays the unique universal identifier (UUID) of the alarm record.
• Source State
This data field displays the status of the listed alarm source; for example, “High Limit” or “Normal”.
• Ack State
This data field displays either “Acked” or “Unacked” to indicate whether the alarm has been ac-
knowledged or not.
• Ack Required
This data field displays either “True” or “False” to indicate whether or not an acknowledgement is
required for this alarm.
• Source
This data field displays the alarm source name.
• Alarm Class
This data field identifies the name of the alarm class that the extension is assigned to (defaultAlarm-
Class or other class).
• Priority
This data field displays the priority number of the alarm.

NiagaraAX-3.x
7-13
User Guide
Types of alarm service views Chapter 7 – About alarms
About the alarm database maintenance view May 1, 2007

• Normal Time
This data field displays the time that the alarm went to normal (if applicable)
• Ack Time
This data field displays the time that the alarm was acknowledged (if applicable)
• User
This data field identifies the name of the user that acknowledged the alarm. An unacknowledged
alarm will display “unknown” in this field.
• Alarm Data
This data field presents a detailed list of alarm data.
• Alarm Transition
This data field displays the last transition type of the alarm.
• Last Update
This data field displays the time of the last alarm update.
About the Alarm details dialog box
You can double-click on any row in the alarm database maintenance view table and the Alarm
Details dialog box appears, as shown in Figure 7-17.

Figure 7-17 Alarm details

The alarm details dialog box displays read-only details about the alarm that is displayed in the database
maintenance view.
Types of alarm database maintenance
The database maintenance view allows you to perform the following database maintenance actions on the
alarms, using the controls located at the bottom of the view:
• Clear Old Records
allows you to clear alarm records before a certain date and time. The Before field is provided to
allow you to set the date and time for removing old records.
• Clear All Before Selected Record
allows you to delete all records that have a timestamp earlier than the timestamp of the record that
is currently highlighted in the table.
• Clear All Records
allows you to delete all records, regardless of the date.
Refer to “Managing alarms” on page 12-20 for procedures about alarm database management.

NiagaraAX-3.x
7-14
User Guide
Chapter 7 – About alarms About alarm class
May 1, 2007 About alarm service property sheet

About alarm service property sheet

An example of the alarm service property sheet is shown in Figure 7-18. The property sheet view of the
alarm service displays all the recipients that are part of the alarm service and also has a capacity property
that is visible and editable. The alarm service capacity property limits the number of records that are
stored in the alarm service database. When the capacity is reached, the alarm records “roll”. This means
that the newer records overwrite the oldest records.

Figure 7-18 Alarm service property sheet

Note: For details about the alarm database manager views, refer to “About the alarm database maintenance
view” on page 7-13. For details about the alarm class summary view, refer to “About the alarm class
summary view” on page 7-12. For details about the alarm extension manager, refer to “About alarm
extension manager” on page 7-9.

About alarm class

The alarm class is maintained by the alarm extension and all alarm classes available to the system are
maintained as slots on the alarm service. The alarm class routes alarms with some similar set of properties
along common routes and they serve as channels for like data. Alarm class manages the persistence of the
alarms as needed via the alarm archive, but otherwise merely chains alarms from the alarm source via a
topic. The alarm class also manages which alarms require acknowledgement and is the basis for visual
grouping in the alarm console.
The alarm classes are located under the alarm service node in the nav side bar, as shown in Figure 7-19.

Figure 7-19 Alarm class in nav side bar

You can set up multiple alarm classes in order to have a variety of alarming and routing options available
for selection from the alarm extension properties. For example, you may set up an alarm class that routes
to the console recipient and station recipient, while you may use another alarm class that routes alarms
only to an email recipient, as shown in Figure 7-20.

Figure 7-20 Alarm classes and linked alarm recipients

For more information about alarm recipients, refer to “Types of alarm recipients” on page 7-18. For infor-
mation about configuring alarm classes, refer to “About alarm class properties” on page 7-16.

NiagaraAX-3.x
7-15
User Guide
About alarm class Chapter 7 – About alarms
About alarm escalation May 1, 2007

About alarm escalation

Alarm escalation is a feature that allows you to configure an alarm class so that unacknowledged alarms
that are assigned to that class can be re-routed if they are not acknowledged within a specified amount of
time. The following three levels of escalation are provided so that you can enable up to three opportu-
nities to re-route an alarm notification as the alarm remains unacknowledged:
• Escalation Level1
• Escalation Level2
• Escalation Level3

Figure 7-21 Escalation levels routed to three email recipients

Each level may be routed to a different alarm recipient, as shown in Figure 7-21, so that if an alarm
remains unacknowlwedged long enough, it may be sent to as many as four different recipients (including
the original recipient). However, if an alarm is acknowledged at any level, then it is not escalated to the
next Level.
In addition to having an Enable property, each alarm escalation level has a Delay property that allows you
to set the amount of time that you want to allow an alarm to remain at any level before it is moved to the
next escalation level. Refer to “About alarm class properties” on page 7-16 for more information about
Alarm Class properties.

About alarm class properties

Figure 7-22 Alarm class properties

The alarm class property sheet is shown in Figure 7-22 and described in the following list:
Note: Remember that these alarm class properties are specific to their parent alarm class and therefore, the
properties do not contain values that are assigned to other alarm classes.
• Ack Required
Any alarm assigned to this alarm class is required to have the selected alarm transitions acknowl-
edged when the associated option is selected (toOffnormal, toFault, toNormal, toAlert). If no option
is selected, then no ack is required.
• Priority
These fields allow for custom entry of priority levels for each alarm transition type. The priority lev-
els are associated with the alarms and are indicated graphically by colors that you can set in the alarm
options dialog box. Refer to “Alarm console options” on page 2-21 for details about setting priority
colors.

NiagaraAX-3.x
7-16
User Guide
Chapter 7 – About alarms About alarm class
May 1, 2007 About alarm class mapping

• Total Alarm Count

This property displays the total number of alarms that have been assigned to the alarm class from all
sources.
• Open Alarm Count
This property displays the current total number of open alarms.
Note: An “Open Alarm” is an alarm that is in normal status and is not acknowledged (or acknowl-
edged and in alert status).
• In Alarm Count
This property displays the total number of alarm conditions.
• Unacked Alarm Count
This property displays the total number of unacknowledged alarms.
• Time of Last Alarm
This property displays the time that the last alarm (assigned to this alarm class) was generated.
• Escalation Level(n) Enable (where n is 1, 2, or 3)
Select the true or false option of this property to enable or disable escalation at this level.
• Escalation Level(n) Delay (where n is 1, 2, or 3)
This property is the time since the alarm was generated until it is escalated. This is not the time be-
tween escalation levels. Set a time (in hours and minutes) that you want to allow an unacknowledged
alarm to remain unacknowledged before you escalate it to the next level. One minute is the smallest
increment that you can set for escalation level delay.

About alarm class mapping

Alarm class mapping is available using the alarm class mapper dialog box. This dialog box, shown
in Figure 7-23, provides a way for you to assign one or more alarm classes to a common set of alarm-
handling parameters. One benefit of this type of mapping is that you can import alarms from a variety of
alarm classes and have them display, link, or sound in a common manner. You do this by creating a alarm
class definitions and then “mapping” existing alarm classes to these definitions. Open the alarm class
mapper dialog box by choosing Alarm Class Mapping... from the Alarm menu. You can also
open this dialog box in the Alarm Console window inside the Workbench Options dialog box.

Figure 7-23 Alarm class mapper

Note: The Alarm menu is available when you are in the alarm console view.
The alarm class mapper dialog box has two primary windows, as shown in Figure 7-25 and described
below:
• Alarm Class Definitions window
This window is located at the top of the alarm class mapper dialog box. You can create, delete, or
edit alarm mapper definitions in this window and then assign any existing alarm classes to these def-
initions, as shown in Figure 7-25. Click on the Edit button to display the Edit dialog box (shown
in Figure 7-24) where you can configure the mapper alarm definition.

NiagaraAX-3.x
7-17
User Guide
Types of alarm recipients Chapter 7 – About alarms
About alarm class mapping May 1, 2007

Figure 7-24 Editing a mapper alarm class

Note: The icons, hyperlinks, and sounds in the alarm mapper definition do not override those that
are assigned in the alarm extension itself. If these parameters are assigned in both the alarm extension
and in the alarm class mapper definition, the alarm class mapper definition parameters are ignored.
• Alarm Class Definitions Mapping window
This window is located at the bottom of the alarm class mapper dialog box. You can map any existing
alarm classes to alarm mapper definitions. To do this, click the Add Mapping button to display the
Map Alarm Class dialog box, as shown in Figure 7-25. Choose an available alarm class in the up-
per option box and assign it to the mapper alarm class definition in the lower option box. Click the
OK button to complete the assignment. The mapping appears in the lower window. Remove map-
ping assignments by selecting the mapping in the lower window and clicking the Remove Map-
ping button.

Figure 7-25 Alarm class definitions mapping

Types of alarm recipients

Alarm recipients are linked to an alarm class (from the alarm topic on the alarm class to the routeAlarm
action on AlarmRecipient), as shown in Figure 7-20. Recipients may be configured to receive alarms at
certain times of the day, certain days of the week, and to receive alarms of only specified transitions.
There are several subclasses of the alarm recipient, as listed below:
• console recipient (refer to “About the console recipient” on page 7-19)
• station recipient (refer to “About the station recipient” on page 7-22)
• email recipient (refer to “About the email recipient” on page 7-23)
• lineprinter recipient (refer to “About the lineprinter recipient” on page 7-23)

NiagaraAX-3.x
7-18
User Guide
Chapter 7 – About alarms Types of alarm recipients
May 1, 2007 About the console recipient

About the console recipient

The console recipient manages the transfer of alarms between the alarm history and the alarm console.
For example, the console recipient gets unacknowledged alarms from the alarm history and updates the
history when they are actually acknowledged. Console recipient properties are displayed and edited in the
console recipient property sheet, as shown in Figure 7-26.

Figure 7-26 Console recipient properties

Console recipient properties are described in the following list:

• Time Range
allows you to set a limited period of time during a day for collection of alarms, using the following
parameters:
• Start Time
a time of day to begin alarm collection, defined by hour, minute and second.
• End Time
a time of day to end alarm collection, defined by hour, minute and second.
• Days Of Week
option boxes allow selection of specific days to collect alarms.
• Transitions
option boxes allow selection of specific alarm transitions to display in the console. Only those tran-
sitions that are selected will be displayed in the console – even though the alarms are still saved into
the alarm history.
The default view of the console recipient is the alarm console view (for details about the console view, see
About the alarm console).

About the alarm console

The alarm console is a view of the console recipient. It allows you to see all the alarms that have been
routed to the alarm console. Alarms are presented in a tabular view with columns that can be viewed or
hidden using the drop–down menu in the top right corner of the column title bar.

Figure 7-27 Alarm console

The alarm console manages alarms on a per–point basis. Each row in the alarm console is the most recent
alarm from a point. To view all the current alarms or to get more details about a particular alarm from
that point, use the alarm sources view and the associated dialog box displays.

NiagaraAX-3.x
7-19
User Guide
Types of alarm recipients Chapter 7 – About alarms
About the alarm console May 1, 2007

To view all the current alarms from a particular point in the open alarm sources view, double click the
desired row. The alarm details view appears, as shown in Figure 7-28.

Figure 7-28 Open alarm sources view

As with other tables, you can show or hide columns using the Table Options menu in the top right
corner of the table (refer to “Table controls and options” on page 2-17).
To acknowledge an alarm, select the desired alarm and click the Acknowledge button. An alarm is
cleared from the alarm console when both of the following conditions exist:
• alarm is acknowledged
• the point is in a “normal” state
Types of alarm details view dialog boxes
• alarm record dialog box
This dialog box shows additional detailed information about a specific point alarm, as shown in
Figure 7-29. It also allows you to:
• acknowledge an alarm using the Acknowledge button.
• jump directly to a point using the Hyperlink button.
• add notes to the alarm record using the notes dialog box (use the Notes button).

Figure 7-29 Alarm record dialog box

• Filters dialog box

The Filters dialog box displays parameters, as shown in Figure 7-30, that you can use to include
or exclude alarms from the alarm console by selecting or deselecting parameters. This filter action
only affects which alarms display in the alarm console, it does not edit any alarm record data or per-
form any alarm “maintenance”.

NiagaraAX-3.x
7-20
User Guide
Chapter 7 – About alarms Types of alarm recipients
May 1, 2007 About the alarm console

Figure 7-30 Filters dialog box

You can choose, for example, to filter out any alarms in the alarm console that are currently in a
“Normal” state by selecting the “Source State” check box and then selecting all states except “Nor-
mal” and clicking the OK button. This action filters out all alarm records that have “Normal” current
Source States. If the source state changes or if you change the settings in the Filters dialog box, the
alarm console table will update to change the display, as indicated.
Note: It is important to remember that the settings do not reset automatically—you must remove
any filters that you set in order to view all alarm records.
• Notes dialog box
Use the Notes dialog box to add a note to one or more alarms. To add a note to all the alarms from
a selected source, open the Notes dialog box directly from the alarm console view, using the Notes
button. If the selected alarm record represents a source with multiple alarms, any note that you add
is added to all the alarms associated with that alarm source. When there is more than one alarm as-
sociated with an alarm record, the Notes dialog box displays a <Multiple Alarms> message, as shown
in Figure 7-31.

Figure 7-31 Adding a single Note to more than alarm

The Notes dialog box is comprised of the following:

• Message pane
The message pane is located in the upper half of the dialog box. It displays the text of any notes
that are already associated with the selected alarm record. If multiple alarms are associated with
the selected alarm record, the message pane also displays a “<Multiple Alarms>” notice to alert
you to the fact that adding a note adds the note to all the alarms associated with the selected
alarm source.
• Editor pane
The Editor pane is located in the lower half of the dialog box and is a text field that allows you
to type the text for any note that you are adding.
• Add Note button
This button saves the note to the alarm record and dismisses the Notes dialog box.

NiagaraAX-3.x
7-21
User Guide
Types of alarm recipients Chapter 7 – About alarms
About the station recipient May 1, 2007

• Close button
This button closes the Notes dialog box without saving any information.
You can also open the Notes dialog box from the Alarm Record dialog box. Since the Alarm
Record dialog box displays single alarm records, notes are added to only one alarm at a time using
this method.

Figure 7-32 Opening the Notes dialog box from the Alarm Record dialog box

About the station recipient

The station recipient manages the transfer of alarms between the alarm service and a remote station. For
example, a station may send alarm notifications to a “supervisor” station – or any other remote station
that is defined under the NiagaraNetwork. The station recipient component provides a place to specify
the location and other details about that remote station. Station recipient properties are shown in
Figure 7-33. The properties on a station recipient include a field for selecting the remote station, as well
as alarm collection parameters.

Figure 7-33 Station recipient property sheet

Station recipient properties are described in the following list:

• Time Range
allows you to set a limited period of time during a day for collection of alarms, using the following
parameters:
• Start Time
a time of day to begin alarm collection, defined by hour, minute and second.
• End Time
a time of day to end alarm collection, defined by hour, minute and second.
• Days Of Week
option boxes allow selection of specific days to collect alarms.
• Transitions
option boxes allow selection of specific alarm transitions to display. Only those transitions that are
selected will be displayed – even though the alarms are still saved into the alarm history.

NiagaraAX-3.x
7-22
User Guide
Chapter 7 – About alarms Types of alarm recipients
May 1, 2007 About the email recipient

• Route Acks
when this parameter is set to true, Acks are routed to this recipient; when set to false, Acks are
not routed to the recipient.
• Remote Station
option selection displays eligible remote stations. Stations appear in the option list if there is a valid
network connection to the station. Alarms that are sent to a remote station are routed according to
the parameters defined in the Alarm class that is selected in the Alarm component under the remote
station’s NiagaraNetwork. Refer to “Station Alarms notes” on page 4-60 for more information about
remote station alarm routing.

About the email recipient

The email recipient is like other alarm recipients except that the alarm may be formatted into an email
message and delivered to another destination. An example of the email message format is shown in
Figure 7-34.

Figure 7-34 Email alarm message

The properties on an email message recipient (shown in Figure 7-35) include the data for the email
message fields as well as alarm collection parameters.

Figure 7-35 Email recipient property sheet

About the lineprinter recipient

The LinePrinterRecipient allows you to print alarms to line printers that are attached to a station that is
running on a Win32 platform. This recipient can print to local and remote line printers. Alerts may be
generated if the printing of an alarm fails, but the lineprinter recipient does not print alarms that it
generates itself. An example of the lineprinter recipient property sheet is shown in Figure 7-36.

NiagaraAX-3.x
7-23
User Guide
Types of alarm recipients Chapter 7 – About alarms
About the lineprinter recipient May 1, 2007

Figure 7-36 Lineprinter recipient properties

Lineprinter recipient properties are described in the following list:

• Time Range
allows you to set a limited period of time during a day for collection of alarms, using the following
parameters:
• Start Time
a time of day to begin alarm collection, defined by hour, minute and second.
• End Time
a time of day to end alarm collection, defined by hour, minute and second.
• Days Of Week
option boxes allow selection of specific days to collect alarms.
• Transitions
option boxes allow selection of specific alarm transitions to display in the console. Only those tran-
sitions that are selected will be displayed in the console – even though the alarms are still saved into
the alarm history.
• Route Acks
when this parameter is set to true, Acks are routed to this recipient; when set to false, only
alarms (not Acks) are routed to the recipient.
• Printer
this option list displays printers that are available for selection. Select a valid lineprinter from the list
or type in the name of the desired printer.
• Language
this field provides a place to enter the ISO 639 language code for the language associated with the
line printer. This is a two letter code (lower-case preferred). Refer to the following link for the com-
plete list of codes: http://www.loc.gov/standards/iso639-2/langcodes.html.
• Print Format
This field has the following editable default parameters.
• Source: %alarmData.sourceName%
this parameter sends the source name of the alarm to print on the first line.
• Timestamp: %timestamp%
this parameter sends the timestamp of the alarm to print on the second line
• State: %sourceState% / %ackState%
this parameter sends the alarm state and the acknowledged state to print on the third line
• Priority: %priority%
this parameter sends the alarm priority to print on the fourth line
• Alarm Class: %alarmClass%
• Text: %alarmData.msgText%
Note: For more information about how to format data in this field, click on the help icon to the
right of the field.
• Alert on Failure
when this parameter is set to true, an alert is generated if the printer fails to print the alarm.

NiagaraAX-3.x
7-24
User Guide
 CHAPTER 8
About Presentation XML (Px)
This section describes the presentation tools that are available in Niagara AX Workbench. Basic presen-
tation concepts and AX presentation architecture principles are described in “About presentation” on
page 1-13.
If you plan to visually display the control logic that you develop in Workbench (for operations or for
engineering purposes) then you need to understand the basic principles of Px and understand the capabil-
ities and limitations of your different target media. Obviously, graphics and text look different and have
greater limitations on a cell phone display, when compared with a computer-based web browser. It is
important to develop Px files with the target media types in mind and to test your Px views in the target
media types as you develop them.
Usually, it is easier to complete the engineering of your control logic using the wire sheet and other views
before beginning to design the presentation of that logic. There are features and tools in the Px Editor,
such as the Make Widget wizard, that allow you to drag and drop components from the nav tree onto
various panes in the Px Editor. If you have already built the logic, it should visible in the tree and available
for drag and drop.
The general process of creating presentations for control logic can follow many different paths. The three
major steps, shown in Figure 8-1, are provided as an example to help illustrate the process.

Figure 8-1 Simplified presentation process

• Create view
When you create a view, you are creating a relationship between a Px file and a component. The Px
file defines the view and that view may be associated with one or more components of various types,
such as folders and points.
Refer to the following sections for information related to Px views:
• “About Px views” on page 8-2
• “About Px files” on page 8-3
• “About Px viewer” on page 8-4
• Bind data
After creating a view with a Px file, you add graphic visualizations (called widgets) to the file and pass
data to these widgets using data binding. The bound data from the control objects animates and up-
dates the widgets.
Refer to the following sections for information related to widgets and data binding:
• “About Px Editor” on page 8-5
• “About Widgets” on page 8-7
• “Animating Graphics” on page 8-10
• “About Px target media” on page 8-17
• “About Web Profiles” on page 8-17
• “About the Make Widget wizard” on page 8-19
• “Make Widget wizard: examples” on page 8-21

NiagaraAX-3.x
8–1
User Guide
About Px views Chapter 8 – About Presentation XML (Px)
Px views as slot properties May 1, 2007

• Create a Nav file

In order to easily find and navigate between views, a special file type (“.nav” file) is available for cre-
ating a customizable navigation tree. Edit the Nav File using the Nav File Editor and assign a partic-
ular Nav File to a user in the user’s profile (using the User Manager view).
Refer to the following sections for information related to the Nav file:
• “About the Nav file” on page 8-36
• “About the Nav File Editor” on page 8-38

About Px views
A Px view is a custom graphical view that you define in a Px file. The purpose of a Px view is to provide a
visualization of information in a rich, dynamic format that is easy to create and to edit. By using the Px
Editor to build Px files, you can create the desired visualization of your control logic without having
software “programming” skills. When attached to a component, the Px view becomes the default view for
the component.
Looking at an object’s Px view in the property sheet (where it may be edited) helps illustrate what a Px
view is. A Px view is comprised of the following parts, as shown in Figure 8-2:
• Icon
Assign or change the icon file that appears to the left of the Px view display name. After assigning
this icon to the view, it appears in the view selector menu, the nav tree side bar, and in the property
sheet view.
Note: Icon graphics must be linked into your view from a module (for example, use the following
path to find a “folder” icon: “module://icons/x16/folder.png”). Icon graphics are not supported outside
of modules.
• Px File
Assign the Px file that is associated with active Px view. See “About Px files” on page 8-3 for more
about Px file.
• Required Permissions
Assign or edit the Operator and Admin permissions that are applicable when the view is active: Read
(r), Write (w), Invoke (I).
• Media
Edit the target media of the Px view: workbench or html. See “About Px target media” on page 8-17
for details about target media types.

Figure 8-2 Px view in a component property sheet

Px views as slot properties

The Px view is attached to a component as a dynamic slot property of the type “baja:PxView.” One way
to create a new Px view is to add it directly to a slot sheet (refer to “To add a new slot” on page 12-18, for
details about adding new slots). Figure 8-3 shows three Px views in a single component slot sheet.

Figure 8-3 Three Px views as slot properties

The Px view highest on the slot sheet is the default view. You can reorder Px views to change the default
Px view of a component. For an active component, all Px views (if any) appear in the view selector, as
shown in Figure 8-4.

NiagaraAX-3.x
8-2
User Guide
Chapter 8 – About Presentation XML (Px) About Px files
May 1, 2007 About the New Px View wizard

Figure 8-4 Three Px views in the view selector

About the New Px View wizard

You can create and delete Px views using the Slot Sheet view, as described in “Px views as slot properties”
on page 8-2. However, the easiest way to create a new Px view on a component is to use the New Px
View wizard. Start the New Px View wizard by selecting New View from the popup menu or from
the View Selector menu.
This wizard, shown in Figure 8-5, is a single dialog box that allows you to assign the view name, view icon,
and target media properties, as described in “About Px views” on page 8-2. The wizard creates a new Px
file and assigns it a default name unless you specify a name. You may choose to assign an existing Px file
to the view instead of creating a new one.

Figure 8-5 New Px View wizard

After completing the fields in the New Px View wizard, click the OK button to finish. The new Px view
is displayed in the Px Editor. If you choose to have the wizard create a new Px file, it will be a simple
default file, as shown in Figure 8-6 on page 3.

About Px files
The Px file defines the content and presentation of a Px view. The Px file is a special XML file that
describes the components in a database and can be any collection of components, up to a complete
database. All views (wire sheet view, property sheet view, category sheet view, and so on) can be used on
components in a Px file. This means that a Px view can be used to provide a complete variety of options
in the development of dynamic user interfaces.
The contents of a very basic Px file is shown in Figure 8-7, as it appears in the Text Editor. This file simply
contains an empty canvas pane nested in a scroll pane.

Figure 8-6 Basic default Px file in Text Editor View

NiagaraAX-3.x
8-3
User Guide
About Px viewer Chapter 8 – About Presentation XML (Px)
Shared Px files May 1, 2007

As you add more objects to the file, (typically using the Px Editor) the file looks more like the snippet
shown in Figure 8-7. The graphic components, value bindings, and their container elements and
attributes are all referenced in the Px file.

Figure 8-7 Px file in Text Editor View and in Px Editor View

The elements in the Px file are also graphically represented in the Widget Tree side bar pane.
• For information about the Px Editor, refer to “About Px Editor” on page 8-5.
• For information about the Widget Tree side bar, refer to “About the widget tree side bar” on page 2-
9.
• For more information about the Text Editor, refer to “workbench-TextFileEditor” on page 14-59.

Shared Px files
A single Px file may be used as part of one or more Px views. Since the bindings within a px file are always
resolved relative to the current ORD, you can reuse the same Px file across multiple components by speci-
fying bindings with relative ORDs. This allows you to create a single presentation and use it in views that
are assigned to components that can use identical graphic layout. The obvious advantage of this file
sharing is that you only need to create and edit one Px file for many views, thus saving time and ensuring
consistency among similar applications. However, it requires that you understand the following caution:

Caution Editing a Px file affects all views that use that particular Px file:

• Any time that you view a component in the Px Editor you have its Px file open for editing.
• If the Px file is shared with other Px views, then all of those Px Views are changed.

About Px viewer
The Px viewer presents Px in a non-editable display. The Px viewer allows the user (with required permis-
sions) to view information and invoke actions on controls in the display. Any time you select a Px view
from the right-click menu or from the View Selector menu, the Px viewer displays the active component’s
view, as shown in Figure 8-8. Use the Px editor to edit the Px file (as described in “About Px Editor” on
page 8-5).

NiagaraAX-3.x
8-4
User Guide
Chapter 8 – About Presentation XML (Px) About Px Editor
May 1, 2007 Shared Px files

Figure 8-8 Px Viewer

About Px Editor
When you select the Px Editor view of a component, or of a Px file, the Px Editor displays the Px file in
the Workbench view pane. Figure 8-9 shows a Px View of a component with several items selected.

Figure 8-9 Px Editor

The default view of the Px Editor comprises three main areas:

• Canvas
The largest area of the Px Editor (by default) is the canvas pane. Typically, you place widgets on the
canvas and edit them using one or more of the three side bars and additional dialog boxes. Refer to
“About Widgets” on page 8-7 for more information about widgets.
• Side bar pane
The Px Editor side bar pane appears on the far right side of the view pane only when the Px Editor
is active. Refer to “About the side bar panes” for more information about side bar panes. Use the Px
Editor toolbar menu to hide or display individual side bars or to show or hide the Px Editor side bar
pane. Refer to “Types of side bars” on page 2-3 for more information about individual side bars.
• Px Editor toolbar
The Px Editor toolbar displays above the view pane when the Px Editor is active. Refer to “Px Editor
toolbar icons” on page A-14 for more information about individual Px Editor toolbar icons.

NiagaraAX-3.x
8-5
User Guide
View Source XML dialog box Chapter 8 – About Presentation XML (Px)
About the Px Editor Canvas May 1, 2007

About the Px Editor Canvas

The Canvas, shown in Figure 8-10, is a graphic editor interface pane that defines the visual boundaries of
the graphic page that you produce in the Px Editor. The Canvas is also your work area for previewing the
Px file as you develop it using the tools in the Px Editor. The Canvas provides a view of the widgets (see
“About Widgets” on page 8-7) as you add them and bind data to them. Most of the time, the Canvas
provides a live view of any widgets that are added–without having to return to the Px Viewer. However,
some graphic features may only appear in the Px Viewer. See “About Px viewer” on page 8-4 for more
information about the Px Viewer.
The Canvas has the following optional work aids:
• Grid
This is a visual aid for graphical alignment. The grid lines display vertical and horizontal lines as well
as define the visible area of the page. Toggle the grid on or off using the Px Editor menu.
• Show Hatch
Hatching is an area of light-gray diagonal lines that define the boundaries of items that are placed on
the Px Editor Canvas. Toggle the hatching on or off using the Px Editor menu.
• Snap
This feature is an aid to precise placement when you are using the mouse to drag an object to a par-
ticular location. Snap pulls the item to the nearest grid line or nearest object for a matching vertical
or horizontal alignment. Toggle Snap on or off using the Px Editor menu.

Figure 8-10 Px Editor Canvas

View Source XML dialog box

The View Source XML dialog box allows you to view the source XML of a Px file in a separate read-only
window. Although you cannot edit the Px file in this dialog box, you can copy and paste text from the
window into the Text File Editor–or any other text editor, such as Notepad.
The View Source dialog box, shown in Figure 8-11, is a simple window with an OK button that closes the
window when you click it.

NiagaraAX-3.x
8-6
User Guide
Chapter 8 – About Presentation XML (Px) About Widgets
May 1, 2007 About the Px Editor Canvas

Figure 8-11 View Source XML dialog box

About Widgets
Widgets are components that provide visualization. You can use the Px Editor to work with widget
properties in defining user interface functions for control and information display. User widgets can
process input in the form of mouse, keyboard, and focus events. User events are grouped into these same
event categories. The bajaui module, the kitPx module, and the kitPxHvac module all contain widgets
that you can use for building rich user interfaces. You can find these widgets by opening them under the
palette side bar, shown in Figure 8-12, or you can find them using the Make Widget wizard.
• refer to “Using the palette side bar” on page 12-9 for instructions about using the palette side bar.
• refer to “About the Make Widget wizard” on page 8-19 for details about the Make Widget wizard.

Figure 8-12 Widgets in the bajaui palette

The widget tree side bar provides a good illustration of the hierarchy structure of all widgets in a Px file
(refer to “About the widget tree side bar” on page 2-9 for a summary of the widget tree side bar).
Some complicated widgets have mini-frameworks all to their own, such as the table widget, tree widget,
treeTable widget, and textEditor widget. Refer to the “Baja Widget Toolkit” in the NiagaraAX Developer
Guide for more details about these types of widgets and for developer-level information about widgets.

NiagaraAX-3.x
8-7
User Guide
About Widgets Chapter 8 – About Presentation XML (Px)
Widget layout May 1, 2007

The following sections discuss some of the primary characteristics of widgets, including:
• Widget layout
• Types of panes
• Widget painting
• Commands
• About widget properties

Widget layout
A tree-type hierarchy of Px elements defines widget relationships and physical layout, in a structure
where parent-child relationships exist between components. All widgets occupy a rectangular area that
is defined by a position and a size. The position of a widget is defined by its x, y coordinates relative to its
parent’s coordinate system and each widget may have a default (or preferred) size. The size of the widget
is defined by the width and height properties. Figure 8-13 shows a simple layout of a widget (C), held by
a parent widget (B), that is the child object of a widget (A).
Note: If either of the child objects are positioned outside of the view area of the parent, they will be clipped and
not be totally visible.

Figure 8-13 Scroll pane (A) holds canvas pane (B) with widget (C)

Some widgets are designed specifically to be container widgets that hold other widgets. These widgets are
called panes. Figure 8-14 shows the pane hierarchy in the widget tree and on the Px editor canvas. Refer
to “Types of panes” for a list of commonly used panes.

Figure 8-14 Pane hierarchy in the widget tree

Types of panes
Widgets that are designed to be containers for child widgets are called panes. Different types of panes
provide different functions. The following list is a summary of some commonly used panes:
• CanvasPane
used for absolute positioning.
• BorderPane
used to wrap one widget and provide margin, border, and padding similar to the CSS box model.
• EdgePane
supports five potential children: top, bottom, left, right, and center. The top and bottom widgets fill
the pane horizontally and use their preferred height. The left and right widgets use their preferred
width, and occupy the vertical space between the top and bottom. The center widget gets all the re-
maining space. See Figure 8-15 for an example.
• GridPane
lays out its children as a series of columns and rows. Extra space in the rows and columns is config-
urable a number of ways using the pane’s properties.

NiagaraAX-3.x
8-8
User Guide
Chapter 8 – About Presentation XML (Px) About Widgets
May 1, 2007 Widget painting

• SplitPane
supports two children with a movable divider between them.
• TabbedPane
supports multiple children - only one is currently selected using a set of tabs.
Note: Even though only one tab is visible at a time, all tabs must be loaded on the page, even if they
are not visible. If many tabs, with a lot of information, are on a single page, the page may load very
slowly.
• ScrollPane
supports a single child that may have a preferred size larger than the available bounds. The scroll
pane provides a set of scroll bars for viewing areas of the child widget that go outside of its bounds.
• ReportPane
supports headers and footers in report PDFs. The ReportPane allows its content to span multiple
pages, and allows each page to have a common logo as well as a page number and timestamp.
Figure 8-15 illustrates the edge pane layout using borders and labels.

Figure 8-15 Edge panes, borders, and labels on a canvas pane

Widget painting
Painting defines how widgets present themselves graphically (using: colors, transparencies, and so on), as
well as clipping. Graphics are always translated so that the origin 0,0 is positioned at the top, left corner
of the widget. The graphic's clip (visible area) is set to the widget's size. Alpha and transparent pixels blend
with the pixels already drawn. Widgets are drawn in property order, the first widget is drawn first (at the
bottom), and the last widget drawn last (on the top). Effective z-order is reverse of property order.

Commands
Widgets can have user commands that are commonly used with buttons and menu actions. Toggle
commands are commonly used with a checkbox, radio button, and other items. Menu commands are
available and used on fans, coils, and other widgets, as shown in Figure 8-16.

Figure 8-16 Widget commands

For more information about commands, refer to the “Baja Widget Toolkit” in the NiagaraAX Developer
Guide.

NiagaraAX-3.x
8-9
User Guide
Animating Graphics Chapter 8 – About Presentation XML (Px)
About widget properties May 1, 2007

About widget properties

Widget properties define many of the features, behaviors and appearance characteristics of widgets. By
editing widget properties, you set or change the widget attributes. In the Px Editor, you can edit widget
properties using the properties side bar or properties dialog box and their secondary dialog boxes. Many
of the properties (those that appear with the ellipsis icon) have these secondary dialog boxes that display
when you click a property field. The secondary dialog box provides more detailed property fields and
options.
Figure 8-17 shows the property side bar fields for a bound label. In this example, the text property of the
bound label is “bound” to the “slot:temp” value, as shown in the text property field. The binding of this
value allows the dynamic presentation of the temperature information in the Px view.

Figure 8-17 Widget properties

Animating Graphics
Animated graphics are graphics that change, or “update”, based on data values that come from object
sources that are connected (or “bound”) to them. A “graphic” can be as simple as a single word of text
(“ON”) or a number (“72”), or it can be an animated image (rotating fan). Widgets provide the graphic
visualization of data in Workbench, so animated graphics are comprised of one or more widgets
assembled in a Px file, available for display using the Workbench display media types. Widgets are
animated by binding any widget properties to a legitimate data source. This means that you can connect
numeric values to widget properties that use numeric values and you can connect binary values to objects
that can use binary values. By animating the properties of a widget, you can control text and image
appearance as well as a change a widget’s location on the page and even its visibility.
The following sections describe the different concepts that relate to animating graphics:
• Data binding
• Types of bindings
• Types of binding properties
• Relative and absolute bindings

Data binding
All widgets may be bound to data sources using data binding. Bindings are established between a widget
and an object using an ORD. A single binding consists of a single widget–object relationship. A binding’s
ORD property identifies the location of the object that updates and animates the widget.
For example, the most common type of binding, the value binding, provides some of the typical functions
that are associated with building real-time information for presentation as both text and graphics. This
includes support for mouse-over status and right-click actions. Additionally it provides a mechanism to
animate any property of its parent widget using converters that convert the target object into property
values. Figure 8-18 shows a value binding to a fan widget as viewed in the Edit Binding dialog box.

NiagaraAX-3.x
8-10
User Guide
Chapter 8 – About Presentation XML (Px) Animating Graphics
May 1, 2007 Types of bindings

Figure 8-18 Widget data binding

Figure 8-19 illustrates the object-to-widget property binding concept. In this example, a widget has three
separate data bindings. This means that each binding is coming from a different object and therefore each
binding has a different ORD that defines its binding. Each binding provides access to an object’s values
so that they may be used, as required, to animate the widget properties.

Figure 8-19 Widget with three bindings

Types of bindings
There are different types of bindings that may be used with widgets. Some bindings work with only a
certain type of widget (for example, a bound label binding) and other binding types may be used with
several types of widgets (for example, a value binding). Figure 8-20 shows bindings as they appear in a
Workbench options list.

Figure 8-20 Types of bindings

Following, is a list and short description of each binding type.

• Action binding
invokes an action on the binding target component when an event is fired by the parent widget. See
“About action bindings” on page 8-15 for details.
• Bound Label binding
connects a value to a bound label widget. See “About bound label bindings” on page 8-13 for details.
• Field Editor binding
used to bind field editor components to an object. See “About field editor bindings” on page 8-16 for
details.
• Setpoint binding
used to display the current value of a "setpoint" and also to provide the ability to modify it. See “About

NiagaraAX-3.x
8-11
User Guide
Animating Graphics Chapter 8 – About Presentation XML (Px)
Types of binding properties May 1, 2007

spectrum setpoint bindings” on page 8-15 for details.

• Spectrum binding
used to animate a widget's brush (color) property. See “About spectrum bindings” on page 8-14 for
details.
• Spectrum setpoint binding
used in conjunction with a spectrum binding. See “About spectrum setpoint bindings” on page 8-15
for details.
• Table binding
used to bind table data in a bound table. See “About table bindings” on page 8-15 for details.
• Value binding
used to bind to values that are typically under a component. See “About value bindings” on page 8-
13 for details.

Types of binding properties

One or more of the following properties are included with all binding types.
• ORD
this property specifies the ORD that is bound to the widget. This field must have a value if you want
the widget to be bound.
• Hyperlink
this property provides a link to another object. When the field is completed, the hyperlink is active
in the browser or in the Px viewer.
• Increment
this property is a value that can be set to increment (increase) or decrement (decrease) a current val-
ue by the assigned amount. A positive number in this property field increments a value; a negative
number in this field decrements a value.
• Summary
this property allows you to specify a display name for the widget in text or by means of a script.
• Popup Enable
this property has “true” or “false” options and allows you to specify if you want to allow a secondary
window or dialog box to appear when a user clicks on this label from a browser or Px viewer.
• Status Effect
this property provides the following three options for enabling or disabling status effects:
• Color
choose this option to enable a background color change when the bound value status changes.
• Color and blink
choose this option to enable a background color change and a blinking effect when the bound
value status changes.
• None
choose this option to disable any effects based on bound value status changes.
• Widget Property
this property allows you to specify the property that you are targeting in the binding’s parent widget.
For example, you can use a spectrum binding that has a bound label parent to change the back-
ground property of that parent label by selecting “background” in the Widget Property options field.
Or, you can change the foreground color by choosing “foreground”. You can target only one value
per binding but you may add additional bindings if you want to target more that one property in the
parent widget.
• Low Color
this spectrum binding property specifies the color that is used for the lowest value assignment for a
spectrum color binding. The low color displays when the bound target value is less than setpoint-
extent/2. As the value bound to this property increases above the minimum value specified, the color
approaches the color set by the Mid Color property.
• Mid Color
this spectrum binding property specifies the color that is used for the middle value assignment for a
spectrum color binding. This color is displayed when the bound value is exactly at the setpoint. As
the binding value increases above this point, the displayed color approaches the color set by the High
Color property. As the bound value decreases below this point, the displayed color approaches the
color set by the Low Color property.
• High Color
this spectrum binding property specifies the color that is used for the highest value assignment for
a spectrum color binding. The high color displays when the bound target is greater than set-
point+extent/2. As the bound value decreases below the maximum value specified, the color ap-

NiagaraAX-3.x
8-12
User Guide
Chapter 8 – About Presentation XML (Px) Animating Graphics
May 1, 2007 About bound label bindings

proaches the color set by the Mid Color property.

• Set Point
this binding property specifies the value that is used for displaying the Mid Color. For example, if
you set this value to “70”, then the color that you define for Mid Color will be displayed when the
bound value is “70”.
• Extent
this spectrum binding property represents the total range of the bound value which maps from low
to high.

About bound label bindings

Bound label bindings are used exclusively for connecting a value to a bound label widget. Bound labels,
which are located in the kitPx module, have properties that you can edit and access from the Px Editor
properties side bar. The properties pane for the bound label binding is shown in Figure 8-21.

Figure 8-21 Bound label binding properties

Bound label binding properties include the following:

• ORD
• Hyperlink
• Summary
• Popup Enabled
• Status Effect
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About value bindings

Value bindings are used to bind to values that are typically under a component. Widget properties may
be overridden by creating dynamic slots of the same name with a converter that maps the bound target
object into a property value. This capability is what allows animation of any widget property. Value
bindings support features such as real-time graphics, mouse-over, and right-click actions.
The properties pane for the bound label binding is shown in Figure 8-22.

Figure 8-22 Value binding properties

Value binding properties include the following:

• ORD
• Hyperlink
• Summary
• Popup Enabled
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.
Refer to “Types of Converters” for a list of converter types.
Types of Converters
Converters are used to change data from one type to another so that the data can be used to communicate
with a particular widget property value. In most cases, when you animate a property, the correct data
converter appears, by default, at the top of the list, as shown in Figure 8-23.

NiagaraAX-3.x
8-13
User Guide
Animating Graphics Chapter 8 – About Presentation XML (Px)
About spectrum bindings May 1, 2007

Figure 8-23 Types of converters

The following types of converters are available when using a value binding:
• Fixed Simple
• I Numeric to I Simple
• I Status to Simple
• Object to String

About spectrum bindings

This binding is used to animate a widget's brush (color) property by mapping a numeric value into a color
range defined by lowColor, midColor, and highColor properties. The properties pane for the spectrum
binding properties is shown in Figure 8-24.

Figure 8-24 Spectrum binding properties

Spectrum properties include the following:

• ORD
• Widget Property
• Low Color
• Mid Color
• High Color
• Set Point
• Extent
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About setpoint bindings

This binding is used to display the current value of a "setpoint" and also to provide the ability to modify
it. A setpoint is typically a status value property such as fallback. The setpoint binding ORD must
resolve down to the specific property that is being manipulated. If it is bound to a component or to a read-
only property, then the binding attempts to use a "set" action to save.
The properties pane for the spectrum setpoint binding is shown in Figure 8-25.

Figure 8-25 Setpoint binding properties

Setpoint properties include the following:

• ORD
• Hyperlink
• Summary
• Popup Enabled
• Widget Event
• Widget Property
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

NiagaraAX-3.x
8-14
User Guide
Chapter 8 – About Presentation XML (Px) Animating Graphics
May 1, 2007 About increment setpoint bindings

About increment setpoint bindings

This type of setpoint binding is used increment or decrement a numeric value. The properties pane for
the increment setpoint binding is shown in Figure 8-27.

Figure 8-26 Increment setpoint binding properties

Spectrum setpoint properties include the following:

• ORD
• Hyperlink
• Summary
• Popup Enabled
• Widget
• Increment
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About spectrum setpoint bindings

This binding is used in conjunction with a spectrum binding to animate the midColor properties. The
properties pane for the spectrum setpoint binding is shown in Figure 8-27.

Figure 8-27 Spectrum setpoint binding properties

Spectrum setpoint properties include the following:

• ORD
• Hyperlink
• Summary
• Popup Enabled
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About action bindings

This type of binding invokes an action on the binding target component when an event is fired by the
parent widget. The ORD of an action binding must resolve down to a specific action within a component.
Examples of actions include: “active”, “inactive”, “override”, and other commands. The properties pane
for the action binding is shown in Figure 8-28.

Figure 8-28 Action binding properties

Action binding properties include the following:

• ORD
• Widget Event
• Action Arg
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About table bindings

This type of binding is used to bind table data in a bound table. Table bindings can bind to any “collection”
using a BQL, SQL, or History ORD binding. For example, a table binding ORD might look like the
following:
station:|slot:/|bql:select toPathString,toString from control:BooleanPoint
The properties pane for the table binding is shown in Figure 8-29.

NiagaraAX-3.x
8-15
User Guide
Animating Graphics Chapter 8 – About Presentation XML (Px)
About field editor bindings May 1, 2007

Figure 8-29 Table binding properties

Table binding properties include the following:

• ORD
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

About field editor bindings

Field editor bindings are used to bind field editor components to an object. A field editor is a component
that is designed to view and edit an object property. Field editors are designed to be laid out on panes and
are built with standard widgets like buttons, text fields, check boxes, and so on.
The properties pane for the field editor binding is shown in Figure 8-30.

Figure 8-30 Field editor binding properties

Field editor binding properties include the following:

• ORD
Refer to “Types of binding properties” on page 8-12 for a description of the binding properties.

Relative and absolute bindings

Since ORDs can be relative or absolute and widgets are bound to data sources using an ORD, data binding
can be relative or absolute, as shown in Figure 8-31.

Figure 8-31 Absolutely bound ORDs and relatively bound ORDs

This is a particularly important point to remember if you want to design Px files that are used in multiple
views on a local station or even possibly for use across different stations. When you use the Px Editor tools
to bind data, the ORD is usually supplied in an absolute format, by default. The ORD is relative to the
station, such as: station:|slot:/Logic/HousingUnit/AirHandler/DamperPosition. This
absolute path ensures that the data always resolves to a single unique component (“DamperPosition”) in
the location that is specified by the ORD, regardless of where the Px file or the parent component is
located. If the same Px file is attached to a view that belongs to a different component, the ORD will still
resolve to the original “DamperPosition” component because of the absolute path. However, if you make
data binding relative, then the path will resolve relative to its current parent ORD. This relative path
makes the Px file resolve data bindings correctly to identically named components that reside in different
locations, thus making one Px file usable in many views.
You can open the Relativize ORDs dialog box from the Bound ORDs palette, as shown in Figure 8-
32. This Px Editor tool provides a convenient way to change absolute ORDs to relative ORDs.

Figure 8-32 Relativizing bound ORDs

NiagaraAX-3.x
8-16
User Guide
Chapter 8 – About Presentation XML (Px) About Px target media
May 1, 2007 Default Wb Web Profile

About Px target media

When you work in the Px Editor you have two client-side target media technologies to consider.
• Web Workbench
This technology allows the standard Workbench software to run inside a web browser using the Java
Plugin. Web Workbench uses a small applet to download modules as needed to the client machine
and to host the Workbench shell. These modules are cached locally on the browser's hard drive.
• Hx
In addition to Web Workbench, a suite of technology called Hx is available. The Hx framework is
comprised of a set of server side servlets and a client side JavaScript library. Hx allows a real-time
user interface to be built without use of the Java Plugin. It requires only web standards: HTML, CSS,
and JavaScript. If you are developing for a target media that is limited to browsers with HTML and
CSS with no applet plugins available, be sure to test your Px views often in the appropriate browser
as you proceed in your development. The goal of Hx is to satisfactorily present your Px views in non-
applet browsers, however, due to the difference in display technologies, you should verify that the Px
view displays in the browser as you expect it to.
Px files may be targeted for a specific media type, as described in “About presentation media” on page 1-
14. You can specify the target media in the property sheet view of a Px view, as shown in Figure 8-33.

Figure 8-33 Specifying the target media

This allows the Px Editor to advise you if you use any features in your Px file that are not supported by
the target media that you have designated.

About Web Profiles

Note: In Workbench, the concept of Profiles pertains to the different ways that Workbench is displayed while
using either the Java plugin or using Hx technology. In this context, it does not refer directly to security
settings or personal preferences.
Profiles provide NiagaraAX software engineers with the ability to customize both the desktop
Workbench and the Web Workbench interface. Using NiagaraAX, the software engineer can create
customized Workbench applications that provide different functionality. Refer to NiagaraAX Developer
Guide for more information about custom user interface development.
Custom user interface design, at the browser level, allows for different views that may include or exclude
features such as sidebars, navigation trees and other tools that are provided through the interface. Web
profiles are used to identify these different web interfaces. You can assign a single Web profile to each
user that is listed in the User Manager. Refer to “UserService” on page 9-9 for details about assigning web
profiles to users.
The following standard Web profile options are provided:
• Default Wb Web Profile
Includes all Workbench functions (refer to “Default Wb Web Profile” on page 8-17)
• Basic Wb Web Profile
Reduced feature set in Workbench interface (refer to “Basic Wb Web Profile” on page 8-18)
• Default Hx Profile
No Java plugin (refer to “Default Hx Profile” on page 8-18)
• Basic Hx Profile
No Java plugin with reduced feature set interface (refer to “Basic Hx Profile” on page 8-19)

Default Wb Web Profile

This profile provides all the features of the Web Workbench, using the full Java plugin download.An
example of the Default Wb Web Profile is show in Figure 8-34.

NiagaraAX-3.x
8-17
User Guide
About Web Profiles Chapter 8 – About Presentation XML (Px)
Basic Wb Web Profile May 1, 2007

Figure 8-34 Default Wb Web Profile example

Major features of the Default Wb Web Profile include:

• Dropdown menu list
This menu includes the following submenus: File, Edit, Search, Tools, SideBars, PxEditor. These
menus provide commands that are explained in “Types of menu bar items” on page A-2.
• Side Bar
You may show or hide this pane. It may include the nav side bar and the palette side bar. The nav
side bar displays the navigation hierarchy that is defined by the nav file.
• Locator Bar
This interactive graphic bar appears across the top of the view area and functions as explained in
“About the locator bar” on page 2-13.
• Real-Time Data
Data is displayed in real-time using the Java plugin.
• View selector
Provides the same view selection options that are available in the desktop Workbench views. Refer
to “About the view selector” on page 2-14 for details.

Basic Wb Web Profile

This profile uses a reduced set of features but provides a rich user interface using the Java plugin
download. An example of the Basic Wb Web Profile is show in Figure 8-35.

Figure 8-35 Basic Wb Web Profile example

Major features of the Basic Wb Web Profile include:

• Locator Bar
This graphic bar appears across the top of the view area.
• Real-Time Data
Data supplied in real time using the Java plugin.

Default Hx Profile
This profile uses Hx technology (described in “About Px target media” on page 8-17) and provides a real-
time user interface without the Java plugin download. An example of the Default Hx Web Profile is shown
in Figure 8-36.

NiagaraAX-3.x
8-18
User Guide
Chapter 8 – About Presentation XML (Px) Px Editor workflow
May 1, 2007 Basic Hx Profile

Figure 8-36 Default Hx Profile example

Major features of the Default Hx Profile include:

• Locator Bar
This graphic bar appears across the top of the view area and displays links that are defined by the nav
file.
• Real-Time Data
Data is displayed in real time using Hx technology instead of the Java plugin.
• View Selector
This dropdown option list provides a set of alternative views for the active object.

Basic Hx Profile
This profile uses Hx technology (described in “About Px target media” on page 8-17). It provides a
reduced set of features but includes real-time user interface without the Java plugin download. An
example of the Basic Hx Profile is shown in Figure 8-37.

Figure 8-37 Basic Hx Profile example

Major features of the Basic Hx Profile include:

• Locator Bar
This graphic navigation bar appears across the top of the view area and displays links that are defined
by the nav file.
• Real-Time Data
Data supplied in real time without using Hx technology instead of the Java plugin.

Px Editor workflow
There are various ways to work with the Px Editor. Some work sequences may depend on the type of
control logic you are working with and some may depend on your Px target media. The following sections
describe workflow patterns that may be used in some situations but may not be optimal–or even possible
with others. The Px Editor tools provide many ways to perform a single task. For example, you can edit
widget properties in the Properties side bar, or you may double-click on a widget to display a Properties
pane in a separate dialog box. Both means of editing the properties have the same effect.

About the Make Widget wizard

The Make Widget wizard is a convenient aid for quickly adding widgets to the Px file. The Make Widget
wizard is available when Px Editor is the active view. The wizard, shown in Figure 8-38, automatically
displays when you drag a component onto the Px Editor canvas.

NiagaraAX-3.x
8-19
User Guide
About the Make Widget wizard Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Note: The wizard does not display when you drag a widget object from a palette to the canvas.

Figure 8-38 Make Widget wizard

The following list describes the primary areas of the Make Widget wizard:
• Title Bar
This area displays a reminder that you are creating a widget that has a value that is bound to the ORD
of the object that you just dragged into the Px Editor. Double-click on the ORD area to browse for a
different component, if desired.
• ORD
This area displays the ORD of the object that you dragged into the Px Editor.
• Source
This area provides context-sensitive options for choosing the type and source of widget that you
want to bind to the ORD. Depending on the type of value that you want to link, the wizard displays
a variety of options in this area. For example, the Chart widget option would be available for a His-
tory Log object but it would appear dimmed (unavailable) if you dragged a Boolean Point object onto
the canvas.
The Widget Source option that you choose will change the display in the Property Options area and
the Property Sheet area.
• Secondary view
The secondary view area changes depending on what option is chosen in the Source area:
• Property Options (Bound Label only)
This area appears when you select Bound Label in the Widget Source options. It provides a set
of convenience options that allow you to set some of the commonly used label properties, by
selecting a check box. You may also use the property sheet area of the wizard or later use the
property fields in the property sheet dialog box or property sheet side bar to edit these proper-
ties.
• Module browser
This area appears when you select the From Palette option in the Source view and allows you
to browse for the desired widget.
• Sheet selector
This area appears when you select the Workbench View option in the Source view and allows
you to choose the Workbench view that you want to display for the object you just dragged into
the Px Editor.
• Property options
This area appears when you select the Properties option in the Source view and allows you to
choose options that relate to the properties of the object that you just dragged into the Px Edi-
tor.
Note: The Secondary view does not appear when the Actions option is selected in the Source area.

NiagaraAX-3.x
8-20
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

• Property Sheet
This area provides context-dependent options for you to select from (depending on the object that
you drop onto the Px Editor).
• Property Sheet
The complete property sheet view displays when you use the Bound Label, From Palette,
or Workbench View option.
• Properties List
A complete list of component properties (for the component you are dropping on the Px Editor
canvas) is listed in this area.
• Actions
A list of available actions is displayed here when you select the Actions option.

Make Widget wizard: examples

There are many ways to use the Make Widget wizard. The following procedures provide examples of one
way to use the Make Widget wizard to perform the following tasks:
• Create a bound label widget
• Create a widget using a palette kit module
• Create a widget with a Workbench view
• Create a widget using a component properties option
• Create an action widget
• Create a Time Plot widget
• Create a Chart widget

Create a bound label widget

To create a bound label widget using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-39.

Figure 8-39 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-40.

Note: The ORD for the selected component displays in the ORD area. Double click the ORD to browse for a
different component, if desired.
Step 3 Select the Bound Label option in the Source options list as shown in Figure 8-40

NiagaraAX-3.x
8-21
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Figure 8-40 Selecting Make Widget wizard options

The Secondary view area displays a list of property options that are available.
Step 4 In the Secondary view area, select the options that you want and set their properties, as desired, using
the adjacent property options lists, as shown in Figure 8-41.

Figure 8-41 Selecting Make Widget secondary view properties

Note: The Make Display Label option creates a separate unbound label that appears directly beside the
bound label when the widget displays on the canvas. Edit the display label properties using the properties
side bar after completing the Make Widget wizard.
Step 5 In the Properties sheet area, shown in Figure 8-42, edit the bound label properties.

NiagaraAX-3.x
8-22
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-42 Editing Make Widget properties

Note: Some of the options in the Secondary view area are also editable in the Properties sheet area. It is
possible to override an option by changing it in the properties sheet area.
Step 6 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new bound
label appears on the Px Editor canvas as shown in Figure 8-43.

Figure 8-43 Completed bound label on Px Editor canvas

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the widget in the Px Viewer, as shown
in Figure 8-44.

Figure 8-44 Completed (commandable) bound label in Px Viewer

Create a widget using a palette kit module

To create a palette kit-based widget using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-45.

NiagaraAX-3.x
8-23
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Figure 8-45 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-46.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the From Palette option in the Source options list as shown in Figure 8-46

Figure 8-46 Selecting Make Widget wizard options

The Secondary view area displays the palette side bar view.
Step 4 All palettes that are currently open in the palette side bar are available under the module option selector
arrow. Other palettes may be opened by clicking on the folder icon.
In the Secondary view area, expand the module tree to find and select the desired widget template,
as shown in Figure 8-47.

NiagaraAX-3.x
8-24
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-47 Selecting widget template

Step 5 In the Properties sheet area, shown in Figure 8-48, edit the widget template properties, as desired.

Figure 8-48 Editing widget template properties

Step 6 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new widget
appears on the Px Editor canvas as shown in Figure 8-49.

Figure 8-49 Completed widget on Px Editor canvas

NiagaraAX-3.x
8-25
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the widget in the Px Viewer, as
shown in Figure 8-50.

Figure 8-50 Completed (commandable) widget in Px Viewer

Create a widget with a Workbench view

You can create a Px view that duplicates the Workbench view of a component. To create a Workbench
view-based widget using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-51.

Figure 8-51 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-52.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the Workbench View option in the Source options list as shown in Figure 8-52

Figure 8-52 Selecting Make Widget wizard options

The Secondary view area displays a list of view options that are available for the selected component.
Step 4 In the Secondary view area, select the desired component view to add, as shown in Figure 8-53.

NiagaraAX-3.x
8-26
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-53 Selecting widget Workbench view

The Properties sheet area displays the component properties.

Step 5 In the Properties sheet area, shown in Figure 8-54, edit the widget template properties, as desired.

Figure 8-54 Editing widget template properties

Step 6 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new widget
view appears on the Px Editor canvas as shown in Figure 8-55. Use the handles on the widget view to
expand the view to the desired size or edit the Layout field in the properties side bar. Scroll bars will
appear if the widget view is larger that the canvas view area.

Figure 8-55 Completed widget on Px Editor canvas

NiagaraAX-3.x
8-27
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the widget in the Px Viewer, as
shown in Figure 8-56.

Figure 8-56 Completed (commandable) widget in Px Viewer

The view is fully functional in the Px viewer, where you can edit properties, invoke commands, or make
other edits to a component, just as if you are editing in the Workbench view.

Create a widget using a component properties option

To create a widget based on a component property using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-57.

Figure 8-57 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-58.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the Properties option in the Source options list as shown in Figure 8-58

NiagaraAX-3.x
8-28
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-58 Selecting Make Widget wizard properties option

The Secondary view area displays options that are available for creating the new widget.
Step 4 In the Secondary view area, select one or more options from the list, as shown in Figure 8-59.

Figure 8-59 Selecting Make Widget secondary view properties

• Make Display Name Labels

Choosing this option displays a separate unbound label that appears directly beside the bound label
when the widget displays on the canvas. Edit the display label properties using the properties side
bar after completing the Make Widget wizard
• Make Field Editors
Choosing this option displays an area that allows you to edit the property in the Px viewer (or in a
browser).
• Make from palette
This option displays the palette side bar view in the wizard and allows you to find and use a suitable
widget template from any available palette.
• Ord and Property Layout options (By Row or By Column)
These options affect how the fields will be arranged on the canvas when you complete the wizard.
Your choice of layout is optional and you may rearrange the layout after you place the items on the
canvas.
Step 5 In the Properties sheet area, select the properties that you want to bind to the widget. Hold down the
Ctrl key to select more than one property, as shown in Figure 8-60.

NiagaraAX-3.x
8-29
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Figure 8-60 Editing Make Widget properties

Step 6 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new property
widgets appear on the Px Editor canvas as shown in Figure 8-61.

Figure 8-61 Completed bound label and field editor widgets on Px Editor canvas

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the widgets in the Px Viewer, as shown
in Figure 8-62.

Figure 8-62 Completed bound label and field editor widgets in Px Viewer

Create an action widget

To add an action widget to a Px File using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-63.

NiagaraAX-3.x
8-30
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-63 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-64.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the Action option in the Source options list as shown in Figure 8-64.

Figure 8-64 Selecting Make Widget wizard action option

The Properties view area displays actions that are available for creating the new widget.
Step 4 In the Secondary view area, select one or more actions from the list, as shown in Figure 8-65.

Figure 8-65 Selecting Make Widget action properties

Step 5 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new property
widgets appear on the Px Editor canvas as shown in Figure 8-61.

Figure 8-66 Completed action widgets on Px Editor canvas

NiagaraAX-3.x
8-31
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Step 6 Toggle the view using the View/Edit Mode toolbar icon to display the widgets in the Px Viewer, as shown
in Figure 8-62.

Figure 8-67 Using completed action widgets in Px Viewer

Create a Time Plot widget

To add a time plot widget to a Px File using the Make Widget wizard, do the following:
Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-68.

Figure 8-68 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-69.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the Time Plot option in the Source options list as shown in Figure 8-69.

Figure 8-69 Selecting Make Widget wizard Time Plot option

The Secondary view area displays Minimum Value and Maximum Value fields.
Step 4 In the Secondary view area enter the desired minimum and maximum values that you want to display
in the Time Plot widget, as shown in Figure 8-70.

NiagaraAX-3.x
8-32
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-70 Entering Minimum and Maximum Time Plot Values

Step 5 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new Time Plot
widget appears on the Px Editor canvas as shown in Figure 8-71.

Figure 8-71 Completed Time Plot widget on Px Editor canvas

Step 6 Edit the widget, if desired, by doing one or both of the following:
• Resize the widget, as desired to allow the plot to display completely.
• Edit the Time Plot widget properties (header, lines, fonts, and so on) using the Widget Tree and
Properties palettes, as shown in Figure 8-72.

Figure 8-72 Editing Time Plot widget properties in the Px Editor

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the widgets in the Px Viewer, as shown
in Figure 8-73.

NiagaraAX-3.x
8-33
User Guide
Make Widget wizard: examples Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Figure 8-73 Completed Time Plot widget in Px Viewer

Create a Chart widget

Step 1 Open the nav side bar and expand the tree to locate the component that you want to add to the Px Editor
canvas.
Step 2 Drag and drop the desired component onto the canvas, as shown in Figure 8-74.

Figure 8-74 Dropping a component on the Px Editor canvas

The Make Widget wizard displays, as shown in Figure 8-75.

Note: The ORD for the selected component displays in the ORD area. Double-click the ORD to browse for a
different component, if desired.
Step 3 Select the Chart option in the Source options list as shown in Figure 8-75.

Figure 8-75 Selecting the Make Widget wizard chart option

The Secondary view area displays fields that allow you to choose the data for the x and y axes of the
chart and the Time Range.
Step 4 In the Secondary view area enter the value source for column 0 and for column 1. Also, choose the
desired range from the time range option list, as shown in Figure 8-76.

NiagaraAX-3.x
8-34
User Guide
Chapter 8 – About Presentation XML (Px) Make Widget wizard: examples
May 1, 2007 Basic Hx Profile

Figure 8-76 Entering chart axes values

Step 5 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new Chart
widget appears on the Px Editor canvas as shown in Figure 8-77.

Figure 8-77 Completed Chart widget on Px Editor canvas

Step 6 Edit the widget, if desired, by doing one or both of the following:
• Resize the widget, as desired to allow the plot to display completely.
• Edit the Chart widget properties (header, lines, fonts, and so on) using the Widget Tree and Proper-
ties palettes, as shown in Figure 8-78.

NiagaraAX-3.x
8-35
User Guide
About the Nav file Chapter 8 – About Presentation XML (Px)
Basic Hx Profile May 1, 2007

Figure 8-78 Editing Chart widget properties in Px Editor

Step 7 Toggle the view using the View/Edit Mode toolbar icon to display the Chart in the Px Viewer, as shown
in Figure 8-79.

Figure 8-79 Completed Chart widget in Px Viewer

About the Nav file

The Nav file is a special xml file that resides on the file system–not in the station database. You can create
as many Nav files as you want, however, a client may display only one Nav file at any time. This means
that any time you are viewing a station you can only see one nav file in the nav tree (or locator bar) but
since a station may be serving many clients, each client may be using different nav files concurrently –
based on their nav file assignment. The Nav file is user-specific, so when a user logs into a station, the Nav
file for that user is displayed in the nav tree or locator bar.
You can match a Nav file to a user by using the Workbench User Manager view. Refer to “UserService”
on page 9-9 for details about the User Manager.
You can create new nav files using the right-click menu, as shown in Figure 8-80. Refer to “Creating a new
Nav file” on page 12-24 for details about creating a new nav file.
Add details to your nav file and customize the hierarchy of your nav tree using the Nav File Editor, as
described in “About the Nav File Editor” on page 8-38.

NiagaraAX-3.x
8-36
User Guide
Chapter 8 – About Presentation XML (Px) About the Nav file
May 1, 2007 Nav file elements

Figure 8-80 Creating a new Nav file

Figure 8-81 shows three Nav files in the nav folder. Notice that the Nav side bar displays a tree hierarchy
of links directly under the station node. Each node of the tree has a context-appropriate icon to help the
user recognize the target link of each node in the tree. You can specify icons for the tree nodes, as
described in “About the Nav File Editor” on page 8-38.

Figure 8-81 Creating a new Nav file

Nav file elements

When you create a new nav file, in addition to the xml declaration, the file includes two default elements,
as listed below and illustrated in Figure 8-82:
• <nav> element
a single opening and closing set of <nav> elements hold all the nodes in the tree
• <node> element
the default <node> element includes an ORD path that points to the station root directory:
ord='station:|slot:/'
You can edit these nodes directly in the Text Editor or you can use the tools provided in the Nav File
Editor (refer to “Nav File Editor” on page 8-38).

Figure 8-82 Default nav file with home node only

Figure 8-83 shows what the elements in your nav file look like (when viewed in a text editor) once you add
a few nodes to your tree.

NiagaraAX-3.x
8-37
User Guide
About the Nav File Editor Chapter 8 – About Presentation XML (Px)
Nav file elements May 1, 2007

Figure 8-83 Simple nav file with home node only

Figure 8-84 shows what the elements in a nav file look like in the nav tree and in the Nav File Editor once
you add a few nodes to your tree.

Figure 8-84 Nav file viewed in nav tree and in Nav File Editor (Result Tree)

About the Nav File Editor

The Nav File Editor view provides a simple way for you to view and edit Nav files. When you select the
Nav File Editor view of a file, the Nav File Editor displays in the Workbench view pane.
The default view of the Nav File Editor comprises three main areas, as shown in Figure 8-85, and
described below:

Figure 8-85 Nav File Editor

• Source objects pane

This resizable pane displays in the top half of the Nav File Editor when you toggle ON the Show
Components button or the Show Files button on the control pane. The pane disappears when you
toggle the buttons OFF. Refer to “Nav File Editor source objects” on page 8-39 for details about
source objects.
• Result tree pane
This pane displays whenever the Nav File Editor is open. The pane appears in the bottom half of the
Nav File Editor when you toggle ON the Show Components button or the Show Files button on
the control pane and fills the view (above the control buttons) when the Show Components button
or the Show Files are toggled OFF. Refer to “Nav File Editor result tree” on page 8-39 for details about
the result tree.
• Controls
These buttons are always displayed horizontally across the bottom of the Nav File Editor. Refer to

NiagaraAX-3.x
8-38
User Guide
Chapter 8 – About Presentation XML (Px) About the Nav File Editor
May 1, 2007 Nav File Editor source objects

“Nav File Editor buttons” on page 8-39 for more information about the functions of each Nav File
Editor control button.

Nav File Editor source objects

Nav File source objects are those objects that may be used for creating you nav file. In order to appear in
the source object pane, the “source object” must be a Px file or a component with a Px view assigned to
it. The source objects populate the pane view based on the position of the Show Components and Show
Files buttons, as described in “Nav File Editor buttons” on page 8-39.

Figure 8-86 Source objects available in the source pane

To use the source objects pane for creating the nav file structure, you drag components or files from the
source objects pane down to desired tree location in the result tree pane. Refer to “Nav File Editor result
tree” on page 8-39 for details about the result tree pane.

Nav File Editor result tree

The result tree pane is where you build the nav file structure. You can drag and drop components and
files from the source objects pane to create new nodes in your tree. You can also create nodes directly,
using the New button or by using the popup menu directly in the result tree pane. Refer to “Editing a Nav
file in the Nav File Editor” on page 12-25 for procedures about editing nav files.

Figure 8-87 Result tree pane

Figure 8-88 shows an example of a source object being dragged to a specific location in the nav tree. The
result tree shows the exact hierarchy of your nav tree and allows you to set the indent levels by where you
drop the component.

Figure 8-88 Dragging a source object to the result tree pane

Nav File Editor buttons

The Nav File Editor buttons are aligned horizontally across the bottom of the Nav File Editor. They
include controls that you use to create, edit, delete, and rearrange nodes in the nav file. The following list
describes each of the of the Nav File editor buttons.
• New
This button displays the New Node dialog box that allows you to create a new node in the nav file
tree by specifying a name, target ORD and icon for the node. The new node is created as a child node
to the active point in the tree (the one you have selected).
• Edit
This button is available when you select a node in the Result Tree pane. It displays the Edit Node

NiagaraAX-3.x
8-39
User Guide
About Reporting Chapter 8 – About Presentation XML (Px)
About the reporting process May 1, 2007

dialog box that allows you to edit the node name, target ORD, and icon.
• Delete
This button deletes a selected node in the Result Tree pane.
• Move Up
This button allows you to move a selected node (or nodes) up in the nav file tree hierarchy.
• Move Down
This button allows you to move a selected node (or nodes) down in the nav file tree hierarchy.
• Show Components
This button toggles on and off. Toggle this button ON to display all eligible components in the Source
Objects pane.
• Show Files
This button toggles on and off. Toggle this button ON to display all eligible Px files in the Source Ob-
jects pane.

About Reporting
The Reporting function in NiagaraAX helps you design, display, and deliver data to online views and to
printed pages. Table layout features and report widgets are used in designing the reports. The report
service and the report export feature allow you to schedule and distribute reports by email at any time.
NiagaraAX Workbench views and services help you create and route reports. Figure 8-89 shows the
primary views that facilitate the reporting process.

Figure 8-89 Primary views used in creating and routing reports

The following topics describe the major concepts and views associated with reporting.
• “About the reporting process”
This section describes the major points in the reporting process.
• “Types of report components”
This section describes components that are located in the Reports module and available in the Re-
ports palette.
• “About the Grid Table view”
This section provides a description of the Grid Table view of the ComponentGrid.
• “About the Grid Label Pane view”
This section provides a description of the Grid Label Pane view of the ComponentGrid.
• “About the Grid Editor view”
This section provides a description of the Grid Editor view of the ComponentGrid.

About the reporting process

The process of creating and sending a report can be performed in a variety ways. The following points are
provided as an example to help illustrate the major parts of the reporting process.
• Setup the reporting service
Add the ReportService and child components (ExportSource and EmailRecipient) from the Report-
ing palette into your station Services folder.
• Layout report data in a ComponentGrid.
Add a ComponentGrid component (from the Reporting palette) onto the desired location in your
nav tree. Using the Grid Editor view, drag and drop points from the nav tree or use the popup menu
or main menu icons to add rows and columns to the ComponentGrid.
• Create a Px page display of the report
Using the Px editor, add the ComponentGrid to a ReportPxFile page and design the report layout
using ReportWidgets available from the Report palette.
• Configure ExportSource component
In the ExportSource property sheet, identify the report Px file and schedule the report delivery.
• Configure EmailRecipient component
In the EmailRecipient property sheet, identify the desired recipients and email account to use for de-
livery of the report.

NiagaraAX-3.x
8-40
User Guide
Chapter 8 – About Presentation XML (Px) About Reporting
May 1, 2007 Types of report components

Types of report components

Report components are found in the Report palette, shown in Figure 8-90.

Figure 8-90 Report palette

Types of report components include the following:

• ReportService
Refer to “About the ReportService component” on page 8-41 for details.
• ExportSource
Refer to “About the ExportSource component” on page 8-41 for details.
• EmailRecipient
Refer to “About the EmailRecipient component” on page 8-42 for details.
• ComponentGrid
Refer to “About the ComponentGrid component” on page 8-42 for details.
• ReportPane
Refer to “About the ReportPane component” on page 8-43 for details.
• SectionHeader
Refer to “About the SectionHeader component” on page 8-43 for details.
Note: For more information about using BFormat scripting, refer to the Engineering Note document, BFormat
(Baja Format) Property Usage.
About the ReportService component
ReportService is the parent, or container, for the ExportSource, EmailRecipient, and ComponentGrid
components. In order to use the report service, copy the ReportService component from the Report
module to the Services folder in the Workbench nav tree, as shown in Figure 8-91.

Figure 8-91 Copy the report service to the services directory and add report components

About the ExportSource component

The Export Source component should be located in the ReportService container. It allows you to define
a report display source (typically a Px file) for exporting and it allows you to schedule a time that you want
to export it. The property sheet view, shown in Figure 8-91, contains the properties that you configure
for these functions.

NiagaraAX-3.x
8-41
User Guide
About Reporting Chapter 8 – About Presentation XML (Px)
Types of report components May 1, 2007

Figure 8-92 Export Source component property sheet view

• Schedule
This property contains standard scheduling options that allow you to choose different options for
timing the delivery of your report. It also displays a “Last Trigger” and “Next Scheduled Trigger”
field.
• Source
This property specifies the report display that you want to email. An arrow button located at the
right end of the property display opens the Export Source Wizard diaIog box. This dialog box
provides two steps that assist you in assigning source location and selecting a PDF export or an oBix
driver export for your report.
About the EmailRecipient component
The email recipient component contains properties that allow you to specify where the report is to be
emailed. The property sheet view, shown in Figure 8-93, displays the properties that you configure for
this function.

Figure 8-93 Email Recipient component property sheet view

EmailRecipient component properties include the following:

• To
This is the email address of the email recipient (person who is to receive the emailed report).
• Cc
This is the email address of anyone that is to receive a copy of the email (and attached report).
• Bcc
This is the email address of anyone that should receive a copy of the email (and attached report) but
whose name you do not want to display in the delivered email.
• Language
This is the ISO 639 language code as two lower-case letters. For a list of codes, see the following:
http://www.loc.gov/standards/iso639-2/langcodes.html
• Language
This is the email address of the email recipient (person who is to receive the emailed report).
• Email Account
This is an option list that allows you to choose the email account that you want to use for sending
the report email.
About the ComponentGrid component
The component grid allows you to define and design your report content (typically in the Grid Editor
view). Use the component grid to link and layout the data that you want to put into your report.

NiagaraAX-3.x
8-42
User Guide
Chapter 8 – About Presentation XML (Px) About Reporting
May 1, 2007 Types of report components

Figure 8-94 ComponentGrid property sheet view

The component grid has most of the standard Workbench views, such as Property Sheet view (shown in
Figure 8-94), wire sheet, category sheet, slot sheet, and link sheet. Unique ComponentGrid views include
the following:
• Grid Table
This view displays your linked data in a typical Workbench table format. Refer to “About the Grid
Table view” on page 8-44 for details.
• Grid Label pane
This view displays your linked data in an tabular view that uses the GridLabelPane widget for dis-
playing the report data. Refer to “About the Grid Label Pane view” on page 8-44 for details.
• Grid Editor
This is the view that you use to specify row and column data for your report. Refer to “About the Grid
Editor view” on page 8-46 for details.
About the ReportPane component
The ReportPane widget, shown in Figure 8-95, is located in the ReportWidgets folder and provides a
container for layout of Px page report views. The ReportPane has the standard Visible, Enabled, and
Layout properties, but also has the following unique properties:

Figure 8-95 ReportPane property sheet view

• Logo
This property supports the linking of a graphic to the ReportPane component. When displayed in a
Px page, or a Report, the graphic originates at the top left corner of the page. Type or browse to the
desired graphic to set the file path in the property field. If no logo is used, the default value of “null”
should be set in the property field.
• Page#
When this property value is set to True, page numbering displays on each Report page.
• Timestamp
When this property value is set to True, a timestamp is displayed in the bottom right corner of the
report pages.
About the SectionHeader component
The SectionHeader component is used to put a title or heading at the top of a report.

NiagaraAX-3.x
8-43
User Guide
About Reporting Chapter 8 – About Presentation XML (Px)
About the Grid Table view May 1, 2007

Figure 8-96 Section header property sheet

About the Grid Table view

The Grid Table view is a view of the ComponentGrid component. This view provides a tabular display of
all the points that are assigned to the ComponentGrid. In the Grid Table view, you can write to points
(issue commands) using the popup menu, if you have write permissions. Points in the table also display
color-coded status, as shown in Figure 8-97.

Figure 8-97 Grid Table view

The table controls and options are similar those that are used in most Workbench table controls (see
“Table controls and options” on page 2-17.
When you use a GridTable view in a Px page, the editable table properties are accessed in the Properties
dialog box, as shown in Figure 8-98 and listed below:

Figure 8-98 Grid Table properties in Px Editor

• Enabled
When set to true, the table in the Px page interface is commandable using the popup menu. When
this property is set to false, the display is still visible but not commandable.
• Visible
When set to true, the table in the Px page interface is visible. When this property is set to false,
the display is not visible.
• Ord
This Ord is the link binding the display to the GridComponent that defines the table.
• Degrade Behavior
These options specify how the table behaves when the binding communications are not available.

About the Grid Label Pane view

The Grid Label Pane view is a view of the ComponentGrid component. This view provides a tabular
display of all the points that are assigned to the ComponentGrid. In the Grid Table Pane view, you can
write to points (issue commands) using the popup menu, if you have write permissions. Points in the table
also display color-coded status, as shown in Figure 8-99.

NiagaraAX-3.x
8-44
User Guide
Chapter 8 – About Presentation XML (Px) About Reporting
May 1, 2007 About the Grid Label Pane view

Figure 8-99 Grid table view of the GridComponent

In the Px Editor view, you can use the GridLabelPane widget to layout the table on a Px page and edit the
properties of the display properties, as shown in Figure 8-100. These properties allow you to change the
font-type and color, as well as set the text alignment of the table cells, table heading, and first column
properties.

Figure 8-100 Grid Label properties in Px editor

GridLabelPane properties include the following:

• Cell Align
This property provides options for setting the alignment of cell content (left, right, center, fill).
• Cell Brush
This property specifies the color of the content (for example, font color) within the table cells.
• Enabled
When set to true, the table in the Px page interface is commandable using the popup menu. When
this property is set to false, the display is still visible but not commandable.
• First Column Align
This property provides options for setting the alignment of cell content (left, right, center, fill) for
the first column in the table.
• First Column Brush
This property specifies the color of the content within the first column table cells.
• Header Align
This property provides options for setting the alignment of cell content (left, right, center, fill) for
the top row of the table (the table “heading”).
• Header Brush
This property specifies the color of the content within the table heading cells
• Header Font
This property allows you to set the font-type and font properties for the table heading.
• Layout
This property allows you to specify the size and location of the table in relation to its parent (X, Y,
coordinates, height and width). Alternatively, you can select a “fill” option to have the table expand
to the limits of its parent container.
• Visible
When set to true, the table in the Px page interface is visible. When this property is set to false,
the display is not visible.

NiagaraAX-3.x
8-45
User Guide
About Reporting Chapter 8 – About Presentation XML (Px)
About the Grid Editor view May 1, 2007

About the Grid Editor view

The Grid Editor view is a view of the ComponentGrid component. This view provides a layout display
that you use to assign points that you are going to use in a report. Figure 8-101 shows the Grid Editor view
with and without points assigned.

Figure 8-101 Adding rows and columns in the Grid Editor view

In the Grid Editor view, you can assign components to areas using the Add Column and Add Row
commands from the popup menu or from the Workbench main menu. You can edit existing rows or
columns by double-clicking on them to display the Edit Row or Edit Column dialog box, as shown
in Figure 8-102.
• Columns area
This area extends across the top of the Grid Editor view. Columns specify the slot path that identifies
the point data that goes in the table cell. Add columns after you have defined a template row in the
template area.
• Template area
This area is just below the column area and displays as yellow, with a caution message when it is
empty. The template row is used as a reference for picking columns, and therefore, there must be a
template row defined before you can add and save a column in the Grid Editor view. Double-click
on the template area to add a row using the Edit Template dialog box. If you add a row without
first adding a Template Row, then the first row you add becomes the Template Row by default and
automatically populates the template area.
• Row area
The row area extends across the lower part of the Grid Editor view. Add rows to define any point
data that goes in the table row. Rows work in conjuction with the columns to present data in a table
format.
About the Report Edit Row and Edit Column dialog boxes
The Edit Row or Edit Column dialog boxes, shown in Figure 8-102, display when you add a new row
or column—or when you choose to edit an existing row or column in the Grid Editor view.

NiagaraAX-3.x
8-46
User Guide
Chapter 8 – About Presentation XML (Px) About Reporting
May 1, 2007 About the ReportPx file

Figure 8-102 Edit Row and Edit Column dialog boxes

The following fields are associated with these edit dialog boxes:
• Name
This field is associated with the Edit Column dialog box. Type in a literal name to assign a display
name or title to the column.
• Format
This field is associated with the Edit Column dialog box. You can use literal text and BFormat
scripting to assign a value to the column.
• Ord
This field displays in both the Edit Column dialog box and the Edit Row.
Designate a point by browsing to or typing the Ord of the component that holds the value that you
want to display.
Note: For assigning rows, you can drag and drop a point onto the Grid Editor view and the Ord
automatically appears in the Ord field.

About the ReportPx file

ReportPx files are available from the New menu item on a popup menu when you right-click on an appro-
priate container for a Px file. The ReportPxFile is a regular Px file that has been “pre-loaded” with a
ReportPane widget, as shown in Figure 8-103.

Figure 8-103 Creating a new ReportPxFile

NiagaraAX-3.x
8-47
User Guide
About Reporting Chapter 8 – About Presentation XML (Px)
About the ReportPx file May 1, 2007

NiagaraAX-3.x
8-48
User Guide
 CHAPTER 9
About Security
This section explains security for any NiagaraAX station. Station security means access by a person using
either Workbench or a web browser, or station access by another station. Security determines if a station
connection is allowed, what can be accessed, and what operations can be performed. In the case of
individual users, it also typically determines navigation options and overall appearance.
A station’s security is based upon users and object categories, with each user’s permissions within any
category defined with specific permission levels. All configuration is stored in the station database, using
services, components, and component views.
Note: Niagara platform security is a different topic altogether. For more details, see the sections “About a
platform connection” and “Update Authentication” in the Platform Guide.
The following main sections provide more station security details:
• Security model overview
• UserService
• CategoryService

Security model overview

A station’s security is determined by the combination of categories, users, and permissions, as shown in
shown in Figure 9-1.
Note: In general, you create needed categories first, then assign objects to them. Then create users, to which you
assign permissions. However, you can engineer security in any order you want.

Figure 9-1 Station security includes categories, users, permissions

The following sections explain the various aspects of station security:

• Categories and security
• Users and security
• Permissions and security
• About permission levels
• UserService security notes
• About user audits
• Multi-station security notes
• Alarm ack permission notes

NiagaraAX-3.x
9–1
User Guide
Security model overview Chapter 9 – About Security
Categories and security May 1, 2007

Categories and security

Categories are integral to station security. A station’s CategoryService (under Services container)
provides a CategoryManager view for you to add, delete, and edit categories, as shown in Figure 9-2.

Figure 9-2 CategoryService and CategoryManager view

Each Category is really just an index (Category 1, Category 2, and so on), however, you typically name
them to reflect some logical grouping. For example, you could have “Lighting” and “Floor 3” categories,
and assign some objects to both, and others to just one category (or neither of these).
Note: By default, a new station (created using the New Station wizard) has no existing categories. However,
category slots (Category 1—8) exist, with all objects defaulting to slot 1.
As shown in Figure 9-3, you typically use the CategoryBrowser (default view of the CategoryService) to
assign objects in the station to different categories. Every object must be assigned to at least one category.

Figure 9-3 CategoryBrowser (CategoryService default view)

In the CategoryBrowser, you use an expandable tree to navigate to objects of interest, and click in table
cells to add or remove category assignments. As an alternative to explicitly assigning one or more
categories to an object, you can have it “inherit” the assigned categories of its parent. This affects
appearance in the CategoryBrowser, where:
• Yellow rows are objects explicitly assigned into one or more categories.
• Dimmed rows represent objects inheriting their parent’s category or categories.
Note: You can also review and assign components to categories individually at the component level, using any
component’s CategorySheet view. Included is a convenience link back to the CategoryBrowser (Category-
Service). See “CategorySheet” on page 9-17.
By themselves, categories have little security meaning. Only when you set a user’s permissions do you
reference categories. For more details on categories, see “CategoryService” on page 9-14 and “Category
caveats” on page 9-16.

Users and security

Users define possible connections to the station. Under the station’s Service container, a UserService
provides a default User Manager view (Figure 9-4) for you to add, delete, and edit users.

NiagaraAX-3.x
9-2
User Guide
Chapter 9 – About Security Security model overview
May 1, 2007 Users and security

Figure 9-4 UserService and default UserManager view

Typically, each user represents a specific person who uses Workbench or a web browser (or both) to
connect to the station. Properties for any user include various settings, including several affecting mostly
browser access, including Facets, Nav File, and Web Profile, as shown in Figure 9-5.

Figure 9-5 User properties

However, a user can be for one or more remote NiagaraAX stations to use (for client connection), in order
to share data and import/export histories and schedules. If a “station-type” user, in any remote
NiagaraAX station, you reference this user when adding that NiagaraStation device (under its Fox Client
Connection properties).
Two important security aspects are “built-in users,” and the authentication method used by a station.
• About built-in users
• About authentication
For further details on the UserService, including descriptions of service properties and views, as well as
properties of child (user) components, see “UserService” on page 9-9.
About built-in users
Any station has two built-in users that you can neither delete nor rename: admin and guest.
User admin User “admin” is unique from all other users in that you cannot disable it, set it to expire, or
assign permissions (it is always super user, meaning all permissions). This ensures every station always
has at least one super user.

NiagaraAX-3.x
9-3
User Guide
Security model overview Chapter 9 – About Security
Permissions and security May 1, 2007

When using the New Station Wizard tool to create a station, the wizard prompts for the password for the
admin user. In a typical “sandbox” environment, you could simply leave the password fields blank (no
password). However, never deploy any real station this way—that station would be vulnerable to anyone
with only a passing knowledge of NiagaraAX.
In general, it may be best to guard the password for the admin user from almost everyone, as well as use
it infrequently. If desired, you can duplicate the admin user, then rename, assign password, reassign
permissions, and so forth. If each person has their own (unique) user account, this also makes audit infor-
mation more valuable. See “About user audits” on page 9-7 for more details.
User guest User “guest,” if enabled, provides station access from a browser with no login required (no
authentication). Initially, any browser pointed to the host sees “home” in the Nav file assigned to guest.
The browser operator can then navigate in the normal fashion, providing that guest has read permissions
for objects. Access of an object lacking guest permissions produces the login prompt, whereby the
operator must login (as a non-guest user) to proceed.
Note: Password assigned to guest (if any) is ignored when accessing the station via a browser. However, if opening
the station in Workbench as user guest, password for guest is checked.
By default, the guest user is disabled. Whenever guest is disabled, all station access requires authenti-
cation, meaning a browser user is always prompted for user name and password. In this case, station login
as “guest” is not available (using either browser or Workbench).
About authentication
For a station connection attempt, the user’s login credentials (user name, password) are checked against
those users under the station’s UserService. This process is called authentication. The actual process (and
authentication mechanism used) can differ, where the three authentication points are:
• Workbench-to-station (FoxService)
The user is always prompted for user name and password. Fox authentication is used, which is con-
figurable via the FoxService (under the NiagaraNetwork) as either basic or digest. Digest (the de-
fault) is the preferred mechanism, since the password is never passed in clear text. However, if using
LDAP, then basic authentication must be configured.
• HTTP browser-to-station (WebService)
Again, the user is prompted for user name and password. The authentication mechanism used is
specified under the station’s WebService, as either cookie (the default), or basic. Cookie is required
if you have users configured for browser-based Workbench (e.g., Basic Wb Web Profile), and/or are
using the Domain-wide cookies authentication feature.
Note: If the guest user is enabled, browser access can occur without login (authentication).
• Station-to-station (FoxService)
A preconfigured user name and password is used (stored under NiagaraStation.clientConnection),
which must correspond to an existing user—typically, with super user permissions. Again, Fox au-
thentication is used, the same as with a Workbench to station connection.
In general, it is recommended you leave authentication mechanisms (FoxService and WebService) at
default settings, unless the station is configured for LDAP (LdapUserService).

Permissions and security

Permissions define what rights a user has within each of the categories in the station. There are two
Niagara permission levels: operator and admin. Within both levels, separate options exist for read access,
write access, and invoke (action) access. See “About permission levels” on page 9-5.
When you add a user, a Permissions field is available for you to set that user’s permissions, using a Permis-
sions popup dialog (permissions map), as shown in Figure 9-6.

NiagaraAX-3.x
9-4
User Guide
Chapter 9 – About Security Security model overview
May 1, 2007 About permission levels

Figure 9-6 Permissions in user’s properties

The built-in admin account has all possible rights for every category (super user). When logged in as the
admin user (or another “super user”), you can assign super user rights to any other user, using the Super
User checkbox. Or, you can use the Permissions dialog to include specific rights to only certain categories
for that user, such as shown in Figure 9-6.
To review and compare permissions among all users, the UserService provides a PermissionsBrowser
view, as shown in Figure 9-7. Typically, you use this view to adjust permissions for any user.

Figure 9-7 PermissionsBrowser (UserService view)

In the PermissionsBrowser, columns represent individual users defined in the station. An expandable tree
lets you navigate to objects of interest to review current permissions, shown in table cells using abbrevi-
ations (for read, write, and invoke). Operator level is small case; admin level is UPPER case.
Row coloring in the PermissionsBrowser provides the same data as in the CategoryBrowser, where:
• Yellow rows are objects explicitly assigned into one or more categories.
• Dimmed rows represent objects inheriting their parent’s category or categories.
You can double-click in any column to access that user’s permissions map. See “PermissionsBrowser” on
page 9-13 for more details.

About permission levels

Once a user has been authenticated (see “About authentication” on page 9-4), that user is granted or
denied permissions for each protected object in the system using the user’s “permissions map” (a
category-based matrix, for an example see Figure 9-20 on page 14).
Depending on object type, permission meanings vary as follows:
• Component permission levels
• File permissions
• History permissions
Component permission levels
Note: By design, the UserService component enjoys a special permission scheme. See “UserService security notes”
on page 9-7 for details.
Each slot in any component is assigned to one of two permission levels, called operator and admin. This
level is determined by whether the “Operator” config flag is set for that slot.

NiagaraAX-3.x
9-5
User Guide
Security model overview Chapter 9 – About Security
About permission levels May 1, 2007

• If set (checked), the slot can be accessed by a user with a minimum of operator-read permissions.
• If cleared (unchecked), a user requires at least admin-Read permissions to access the slot.
With admin-Write permissions, you can see and change slot flags from the slot sheet of any component,
as shown in Figure 9-8. By default, most slots are admin level (“out” is typically operator level).

Figure 9-8 Slot is admin level unless Operator flag is set

Permissions To control user access from a permission level, six permissions are derived, as follows:
• Operator-read — Allows the user to view operator-level information.
• Operator-write — Allows the user to modify operator-level information (if not read-only).
• Operator-invoke — Allows the user to view and invoke operator-level operations (actions).
• Admin-Read — Allows the user to view admin-level information.
• Admin-Write — Allows the user to modify admin-level information (if not read-only).
• Admin-Invoke — Allows the user to view and invoke admin-level operations (actions).
When you assign a user’s permissions, higher-level permissions automatically “include” lower-level ones.
For example, as shown in Figure 9-9 if you enable admin-level write (W), admin-level read (R) is automat-
ically enabled, as well as operator-level read and write (r and w).

Figure 9-9 Lower-level permissions include automatically

Ancestor permissions Often, you may wish to grant a user permissions to components using categories
not included in their parent components, such that permissions to a component’s “ancestor tree” are not
explicitly granted. In this case, the system automatically grants “Operator-read” access to all “ancestor”
components in the component tree. Otherwise, a user would be unable to navigate to target components
in the Nav tree.
This “automatic ancestor permission” assignment is done by the station periodically, but you can force it
at any time with a right-click “Update” action on the CategoryService.
File permissions
Largely, permissions given to categories used by files and folders are “operator-keyed,” as follows:
• Files
Files require operator-read access to view, and operator-write permissions for editing (if applicable).
For instance, a user with operator-write permissions to an .html file can modify it using the Text
File Editor in Workbench.
• Folders
Folders (directories) require operator-read access to list and to copy child files, and operator-write
access to create new (or delete existing) child files.
A few views for files require admin-write permissions to access, such as the Nav File Editor for a
“nav file.” There are also other special case file permissions.
Special case file permissions These additional rules apply to file system access from station access:

NiagaraAX-3.x
9-6
User Guide
Chapter 9 – About Security Security model overview
May 1, 2007 UserService security notes

• Files in any NiagaraAX module are automatically granted operator-read.

• If a user is not a “super user,” all access outside of the station’s home directory is denied.
History permissions
Currently, histories require only operator-read permission to access all available views (e.g. History
Chart, Collection Table, History Table). In addition, the ability to rename a history is included.

UserService security notes

In order to facilitate user management, a special permissions scheme applies to the UserService (only),
whereby permissions are inherited by users as follows:
• If a user has only operator-read permissions, they have read-only access to operator-level properties
of their own user account (all other users are hidden).
• If a user has operator-write permissions, they have read/write access to operator-level properties of
their own user account (all other users are hidden).
• If a user has admin-Read permissions, they have read-only access to all properties of all users.
• If a user has admin-Write permissions, they have read/write access to all properties of all users.
By default, operator properties of User are Password and Facets (time format and unit conversion). If
needed, from the slot sheet of User(s) you can edit config flags to change which slots are operator versus
admin. For example, you might change the email slot to operator.
This scheme is useful when you want to let each user reassign their own password, but not have access to
other users. In this case, assign the UserService component to a category where all users are given
operator-write permissions (only). Remember, any user granted super user permissions has all access to
all objects.

About user audits

An important aspect of station security is an audit trail to record user activity. Any NiagaraAX station
can be configured for user audits through use of the AuditHistoryService. While enabled, this
service creates a history of user-initiated changes to components in the station.
Note: If this service is not already in your station’s Services container, open the history palette and drag or
copy the AuditHistoryService into your station’s Services folder.
The following sections provide more details:
• AuditHistoryService configuration
• AuditHistory content
AuditHistoryService configuration
AuditHistoryService configuration is simplified by having only the following writable properties:
• Enabled
Either true (default) or false (disabled). Typically, you always leave this enabled.
• Capacity
Either: Record Count nnn records (default is 500) or Unlimited. Typically, unlimited is recom-
mended only for Supervisor stations, while JACE stations are set to some finite count. If a JACE sta-
tion, the resulting AuditHistory is typically exported to a Supervisor station for archives.
• Full Policy
Either Roll (default) or Stop. In almost all cases, you leave full policy at roll to ensure latest user ac-
tions are recorded.
AuditHistory content
The AuditHistory records user-initiated changes to property values, invoked actions, as well as any slots
that are added, deleted, reordered, and renamed. Each record appears as a row that includes the
timestamp of the change and the operation, plus other details including the responsible station user.
Using standard history views, you can review and resort data columns in the AuditHistory as needed to
analyze user activity. Figure 9-10 shows an AuditHistory displayed in the HistoryTable view. In this view
(as shown), you can double-click any row for a popup dialog displaying record details.

NiagaraAX-3.x
9-7
User Guide
Security model overview Chapter 9 – About Security
Multi-station security notes May 1, 2007

Figure 9-10 AuditHistory in station Histories

Standard fields in an AuditHistory record include the following:

• Timestamp
Timestamp of when the operation on the slot became effective.
• Operation
Type of user operation, which may include one of the following:
• Added — Added a slot (typically a point or extension)
• Changed — Changed a property (slot) value
• Invoked — Issued a command to an action slot
• Removed — Removed a slot (typically a point or extension)
• Reordered — Reordered one or more slots
• Target
Path to the container of affected slot, relative to the station root.
• Slot Name
Name of the affected slot.
• Old Value
Value of slot before a change.
• Value
Value of slot after the change.
• User Name
User name that initiated the operation.

Multi-station security notes

Some installations have multiple stations. Typically, this means a Supervisor station plus one or more
JACE stations. In this scenario, often the same user(s) need to access different stations. In addition, you
typically create a special “station-to-station user” in each station for use in the NiagaraNetwork. Please
note the following:
• By convention, a station-to-station user can be named something memorable (perhaps “m2m”), but
you should carefully guard its password—as you typically assign it “super user” permissions. When
adding this User, properties that apply to browser access are inconsequential, for example, Facets,
Nav File, and Web Profile. You reference this user in another station, when adding a NiagaraStation
device under a NiagaraNetwork. See “Station Add notes” on page 4-54.
• You can copy users under the UserService in one station into the UserService of another station.
Note that the permission map for each user is included—typically, this is ok if you created the same
categories (by index number) in each station, and are using the same basic security scheme.
• If you copy categories from station to station, the index property in each copied category is reset to
0, and the category has a disabled status (until you reassign the index).
• Often, a browser user that has already logged in is re-challenged for login (authentication) again.
This can happen when navigating from one station to another station. If your Niagara hosts are in-
stalled on a DNS domain, you can configure stations such that the same browser user is authenticat-
ed only once (upon initial station connection). See Domain-wide cookies authentication.

NiagaraAX-3.x
9-8
User Guide
Chapter 9 – About Security UserService
May 1, 2007 Alarm ack permission notes

Domain-wide cookies authentication

This feature is available for multi-station jobs where all Niagara hosts are installed on the same DNS
domain. It allows for stations that have the same user accounts (matching user credentials) to be accessed
by any such user using a “domain-specified” browser connection and a single, initial, login.

To configure domain-wide cookies authentication

Perform the following in any station that may provide the initial browser connection.
To configure domain-wide cookies authentication, do the following:
Step 1 Open the slot sheet of the WebService component (in the station’s Services container).
Step 2 Add a new slot, naming it “cookieDomain”, leaving other fields at defaults (type baja:String).
See “Using the slot sheet” on page 12-18 for details on adding a slot.
Step 3 Go to the property sheet of the WebService.
In the new cookieDomain property, enter your DNS domain name (see Figure 9-11 for example).
Step 4 Verify that the WebService’s property Authentication Scheme is set to Cookie.
Step 5 Save this configuration of the WebService.

Figure 9-11 Example configured WebService

Now, if a user points his or her browser to this Niagara host using the full DNS name (for example: super-
visor.metropolis.net), after station login, they can navigate using links to other stations without need for
login. The same credentials used in the initial login are used in other station connections.

Alarm ack permission notes

When assigning permissions to station users, keep in mind that all alarm ack (acknowledgement) rights
in NiagaraAX are determined only by a user’s permissions on AlarmClass components (and not on the
points with alarm extensions, which “generate” alarms). Alarm classes are under a station’s AlarmService.
As needed, you link alarm classes to alarm consoles, to define alarm routing in the station.
Specifically, a user requires “admin write” permissions on any alarm class in order to acknowledge alarms
or events routed by it. This is mentioned because this is a different alarm ack scheme than was used in
the older Niagara (r2) systems. Note that in a scenario where many “user-divided” ack rights are needed,
you may need to create additional alarm class objects, assigning them to different security categories.
For more details about alarming in general, and also AlarmClass components in particular, see “About
alarms” on page 7-1, and “About alarm class” on page 7-15.

UserService
The UserService is found under a station’s Services container. You use a station’s UserService to add, edit,
and delete users. If you have already configured categories in the station, you can use it to assign users
permissions as well.
Note: For an overview of station security and users, see “Security model overview” on page 9-1 and “Users and
security” on page 9-2.
Before working with users, you should review the UserService properties. After setting properties as
needed in the service, the following UserService views are your primary access to users:
• UserManager
• PermissionsBrowser

NiagaraAX-3.x
9-9
User Guide
UserService Chapter 9 – About Security
UserService properties May 1, 2007

UserService properties
Right-click the UserService and choose Views > Property Sheet, as shown in Figure 9-12.

Figure 9-12 UserManager property sheet access

UserService configuration properties are described as follows:

• Require Strong Passwords
Either false (default) or true. If enabled (true), any future user additions (or edits of a user’s password)
will require entry of a “strong password,” otherwise an “error” popup dialog results.
A strong password must meet these requirements:
• Minimum of 8 characters
• At least 1 character is a numeral (0—9) or special, such as “!”, “@”, “#”, “$”, or “%”.
• Lock Out Enabled
Either false or true (default). If enabled (true), then a number of consecutive authentication failures
will temporarily “lock out” login access to that user account, for the duration of the lock out period
(next property). Using lock out makes it difficult to automate guessing of passwords.
Note: Each user also has a “Clear Lock Out” action. See “Lockout notes” on page 9-12.
• Lock Out Period
Default is 10 seconds, adjustable to any duration in hours, minutes, seconds. If lock out is enabled,
then this is the period of time a user account is locked out before being reset. While locked out, any
login attempt (even a valid one) will be unsuccessful.

UserManager
Double-click the UserService for the UserManager (default view), as shown in Figure 9-13.

Figure 9-13 UserManager is table based view

Rows in the UserManager table represent existing users, where you can edit by either double-clicking a
single user, or clicking to select and then clicking the Edit button.
Note: As in other table-based manager views, you can select multiple rows (users) for edit. This can be useful for
a mass change to a property like Facets or Web Profile. However, be careful when doing multiple user edits
of things like Permissions and Passwords.
To add a new user, click the New button. This produces the New User dialog, as shown in Figure 9-14.

NiagaraAX-3.x
9-10
User Guide
Chapter 9 – About Security UserService
May 1, 2007 UserManager

Figure 9-14 New (user) dialog

You can create multiple users by typing in a number in “Number to Add.” When you click OK, the Add
dialog includes that number of user rows in the top table (Figure 9-15).

Figure 9-15 Adding multiple users

As needed, click to highlight a single user row before entering unique user properties such as User Name,
Full Name, Permissions, and so on. For properties you wish to enter identically for all users (for example,
Facets), hold down Shift and click to select all user rows, then enter property value.
Note: For a listing of all the User properties, see “User” on page 9-11.
When you click OK, the user(s) are added with the property values you entered. Users appear as rows in
the UserManager, and as child components under the UserService container.
User
All available user properties, as seen in the New or Edit user dialog (Figure 9-5 on page 3), are described
as follows:
• Name
Unique name of the user, as known to the station. Used in login credentials (along with Password),
also appears in audits of changes made by the user (see “About user audits” on page 9-7).
• Full Name
Full formal name of the user, or any descriptive name needed.
• Enabled
Either true (default) or false. Determines if the user account is operational. If disabled (false), login
attempts are blocked. By default, user guest is disabled.
• Expiration
Either “Never Expires” (default) or “Expires on <date>”. After the expiration date, login attempts are
blocked.
• Permissions
Either “Super User” (all permissions) or a specific permissions map (click “>>” control). Permissions
are category-based. For an overview, see “Permissions and security” on page 9-4 and also “About per-
mission levels” on page 9-5.
• Language
To specify a lexicon (typically two character language code, such as “fr” or “de”), as needed for lan-
guage support or other customizing.
• Password
Password entered by user in login credentials (along with user Name). Two entry fields are provided,
both entries must match. Can be any combination of alphanumeric characters.
Note: If the UserService is configured for strong passwords (property Require Strong Passwords), the
password must be a minimum of 8 characters, with at least one character being a numeral (0—9) or
any other special character, such as “!”, “@”, “#”, “$”, or “%”.
• Facets
Includes two separate settings, as follows:
• Time Format
How timestamps are formatted in property sheets, and so on. The default time format is
sourced from Baja lexicon.
• Unit Conversion

NiagaraAX-3.x
9-11
User Guide
UserService Chapter 9 – About Security
UserManager May 1, 2007

Selectable as either None (default), Metric, or English. Primarily affects value display of “out”
slots on control points.
• Nav File
To specify a Nav file that provides custom navigation for the user, defining locator bar content and
home page. Click the folder control for a File Chooser dialog to navigate to the location of the sta-
tion’s .nav files (by convention, a “Nav” folder under the station directory). For more details, see
“About the Nav file” on page 8-36.
Note: If guest is enabled, all browser connections to the host start using this Nav file.
• Web Profile
Includes three separate settings: two for station “auto logoff,” and one to specify the user’s expected
type and level of HTTP browser access. The web profile settings are as follows:
• Auto Logoff Enabled
Either true (default) or false. If true, a browser-connected user will be automatically disconnect-
ed from the station after the “auto logoff period” expires, providing that no user activity was de-
tected during that time (changing views, expanding/contracting containers, and so on).
If disabled (false), this browser-connected user is never automatically disconnected.
• Auto Logoff Period
Any number of hours, minutes, seconds needed (default is 15 minutes). Specifies the time peri-
od used by the auto logoff routine (“inactive user time”), if auto logoff is enabled for the user.
• Type
Specifies the user’s expected type and level of HTTP browser access. For more details on profile
types, see “About Web Profiles” on page 8-17. Web Profile Type is one of the following:
– Basic Hx Profile
Lowest level and simplest browser requirements (browser with Java plug-in not required).
Provides locator bar, ability to access properties and graphics (Px views).
– Default Hx Profile
Provides more navigation controls with simple browser requirements (browser with Java
plug-in not required). Provides locator bar, access to property sheets and graphics (Px
views), plus a view selector. Access to slot sheets is included, as well as PDF creation from
property sheets or graphics.
– Basic Wb Web Profile
Requires browser to have Java plug-in. Provides Workbench station access within a brows-
er (Fox connection), but without top menu bar or ability for side bars. View access is lim-
ited to property sheets and Px views.
– Default Wb Web Profile
Requires browser to have Java plug-in. Allows nearly full Workbench station access within
a browser (Fox connection), including top menu bar and side bars (palettes and Nav tree).
View access includes property sheets, wire sheets, category sheets, slot sheets, link sheets
and Px views.
Note: If the same user might need to access the station differently, that is from a simple browser
as well as from Workbench or a browser with Java plug-in support, you should create two user
accounts for that person, each with a different Web Profile. For example, create a user with
“Default Wb Web Profile” and another user with “Default Hx Profile.”
The simplest way to do this is to duplicate that user, then change the Web Profile type. That person will
need to login differently (unique user name) according to their access method.
Lockout notes
If you have lockout enabled in the UserService, a user will be locked out after several unsuccessful
attempts to login (login using their user name, but with incorrect password). A locked-out user is
indicated with a red row in the UserManager, as shown in Figure 9-16.

Figure 9-16 Locked out user is indicated by red

NiagaraAX-3.x
9-12
User Guide
Chapter 9 – About Security UserService
May 1, 2007 PermissionsBrowser

Note: The User component that represents each user has a boolean “Lock Out” slot that provides read-only status
of whether that user account is currently locked out (true) or not (false). If needed, you can link it to other
logic in the station.
If locked out, a user will be unable to login into the station until the lockout period expires, as specified
in the UserService. After that point, the user displays in the UserManager as normal.
As administrator, be aware that each user has an action “Clear Lock Out,” that you can invoke to clear
any lockout in progress. Access this command with a right-click on a user, either selected in the Nav tree
or in the UserManager, as shown in Figure 9-17.

Figure 9-17 Clear lockout action for any user

PermissionsBrowser
From the UserManager, use the view selector to select the PermissionsBrowser, as shown in Figure 9-7
on page 5. By default, the PermissionsBrowser shows the three object types collapsed into just three rows
in the tree: station (components), file, and history.
As needed, expand and contract the object tree to find objects that have been explicitly assigned into one
or more categories, and scroll across to see each user’s permissions for those objects.
Again, displayed row color provides the same data as in the CategoryBrowser, where:
• Yellow rows are objects explicitly assigned into one or more categories.
• Dimmed rows represent objects inheriting their parent’s category or categories.
You can also use Show Configured to automatically fully expand the tree.
Show Configured
Select Category Browser > Show Configured from the menu, or click the icon, as shown in
Figure 9-18. The PermissionsBrowser tree expands to show all explicitly assigned objects.

Figure 9-18 Show Configured in PermissionsBrowser

In each cell intersecting a user (column) and object (row), that user’s permissions are shown with abbre-
viations—see Permissions abbreviations. For any user, you can access permissions.
Permissions abbreviations
Permissions for each object are shown in each of the user columns using abbreviations (Figure 9-18).

NiagaraAX-3.x
9-13
User Guide
CategoryService Chapter 9 – About Security
PermissionsBrowser May 1, 2007

Figure 9-19 Permission abbreviations

Full permissions are “rwiRWI”, where the capital RWI is for admin-level Read, Write, Invoke. It is possible
for a user to have no permissions for some objects (blank cell), if those objects are assigned to a category
the user does not even have operator read “r” permissions for. See “About permission levels” on page 9-
5 for more details.
Access permissions
Double-click anywhere in a column to access a user’s permissions. This produces the same Permissions
dialog as from the user’s properties, only user name shows in the window title bar (Figure 9-20).

Figure 9-20 Permissions map from PermissionsManager

Note: If you double-click on any user with “super user” rights, a popup warning reminds you that you cannot
modify permissions, as shown in Figure 9-21.

Figure 9-21 Super user permissions warning

If you could see the permission map for any super user, it would simply be all possible permissions
checked for all possible categories (rows).
As shown in Figure 9-22, remember to Save after making any user permissions changes.

Figure 9-22 Save user permissions changes

CategoryService
The CategoryService is found under a station’s Services container. You use a station’s CategoryService to
add categories and assign objects (components, files, and histories) to those categories.

NiagaraAX-3.x
9-14
User Guide
Chapter 9 – About Security CategoryService
May 1, 2007 CategoryManager

Note: For an overview of station security including categories, see “Security model overview” on page 9-1, and
“Categories and security” on page 9-2.
Apart from being the container for child categories, the CategoryService has only two slots:
• Update Time
A property that sets the interval at which ancestor permissions are automatically assigned. Default
value is one (1) minute. If assigned a zero value, this feature is disabled.
• Update
An action to manually force ancestor permissions to be assigned to objects in the station.
Note: Typically, you leave the service’s update time at default, and use the update action only if needed while
testing (while actively assigning categories and/or changing permissions).
The two views of the CategoryService are:
• CategoryManager
• CategoryBrowser
The CategoryBrowser is the default view, and typically where you spend more time after initially creating
categories.
Note: In the case of components, you can also make category assignments directly from any component’s Catego-
rySheet view. See “CategorySheet” on page 9-17.

CategoryManager
You use the CategoryManager to add, edit, or delete categories. As shown in Figure 9-2 on page 2, you
can access the CategoryManager using the view selector from any CategoryService view.

Figure 9-23 CategoryManager is table based view

Rows in the CategoryManager table (Figure 9-23) represent existing categories, where you can edit by
double-clicking one. Typically, you edit only the category name, to clarify some logical grouping. All
categories must have both a unique name and index.
To add a new category, click the New button. This produces the New dialog, as shown in Figure 9-24.

Figure 9-24 New (category) dialog

You can create multiple categories by typing in a number in “Number to Add.” When you click OK, the
Add dialog includes that number of category rows in the top table (Figure 9-25).

Figure 9-25 Adding multiple categories

NiagaraAX-3.x
9-15
User Guide
CategoryService Chapter 9 – About Security
CategoryBrowser May 1, 2007

As needed, click to highlight a single category row before entering a unique Name. For a listing of all the
category properties, see “Category properties” on page 9-16.
When you click OK, the categories are added with the names you entered, and appear as rows in the
CategoryManager and as child components under the CategoryService container.
Note: While in theory unlimited categories could be created, in general it is recommended to limit the number of
categories to as few logical divisions as needed. Included are performance reasons, as well as other consid-
erations. See “Category caveats” on page 9-16.
Category properties
As shown in the New or Edit dialog (Figure 9-25), there are only 2 properties for a category, as follows:
• Index
Unique index number for the category, as it is known to the station.
• Name
Any descriptive name needed, typically to reflect some logical grouping.
Category caveats
Please note the following about using categories:
• Performance-wise, too many categories can consume excess station memory, as each object must
maintain a bitmap for category membership. With the default 8 categories, this is only 1 byte, but
increments another byte for each additional 8 categories added (9—16, then 17—24, and so on).
Therefore, you should limit categories to the fewest needed, and keep them indexed contiguously.
• If you delete a category (using the CategoryManager), you may notice it still appears listed in users’
permission maps, with default “Category n” name instead of its former user-assigned name. This un-
derscores that categories are simply indices to the station. Each category Name is simply “metadata”
(data about data).
Moreover, when you assign an component to one or more categories (e.g. using the CategoryBrows-
er), that component’s category bitmap is updated—as part of its configuration. If you copy that com-
ponent to another station or save it in a bog for reuse, please note that its category bitmap (to
category indices) is included.

CategoryBrowser
The CategoryBrowser is the default view of the CategoryService. By default, this view shows the three
object types collapsed into just three rows in the tree: station (components), file, and history. In this view,
the columns represent categories in the station.
Again, displayed row color provides the same data as in the PermissionsBrowser, where:
• Yellow rows are objects explicitly assigned into one or more categories.
• Dimmed rows represent objects inheriting their parent’s category or categories.
To automatically fully expand the tree, use Show Configured.
Show Configured
Select Category Browser > Show Configured from the menu, or click the icon, as shown in
Figure 9-18. The tree expands to show all objects explicitly assigned into one or more categories.

NiagaraAX-3.x
9-16
User Guide
Chapter 9 – About Security CategoryService
May 1, 2007 CategorySheet

Figure 9-26 Show Configured in CategoryBrowser

Objects in dimmed rows have a check mark in the first column (Inherit), meaning that they inherit the
category or categories of their parent container. As needed, in any object row, click either:
• In any category column to explicitly assign an object to a category, or again (toggle) to remove the
object from that category.
• In the Inherit column to return category assignments to match the object’s parent.
Note: With the exception of the three “root” objects (station, files, history), each object must either belong to at
least one category or inherit its parent’s category assignments. The three root objects cannot inherit—they
must belong to one or more categories.
As shown in Figure 9-27, remember to Save after making any needed category assignment changes.

Figure 9-27 Save category assignment changes

CategorySheet
Included for every component in the station database is a CategorySheet view, which you can access using
the right-click View menu (Figure 9-28) or by using the view selector.

Figure 9-28 Accessing CategorySheet view

This view lists all categories in the station, and shows a check mark beside any that are assigned to this
component.

NiagaraAX-3.x
9-17
User Guide
CategoryService Chapter 9 – About Security
CategorySheet May 1, 2007

In addition, the view’s right side offers various controls, as follows:

• Inherit (checkbox)
Click to toggle. While checked, this component inherits category assignments from its parent com-
ponent. While cleared, you can make explicit category assignments for this component.
• Select All
Effective if Inherit is cleared. Click to assign component to all categories in the station.
• Deselect All
Effective if Inherit is cleared. Click to remove all category assignments for this component.
Note: Either click again to assign the component to at least one category, or else click Inherit.
Otherwise, you receive an error when you try to Save (must be assigned to one category).
• Category Service
Click to go to the CategoryBrowser view. See “CategoryBrowser” on page 9-16.
Note: Remember to click Save after making any needed category assignment changes.

NiagaraAX-3.x
9-18
User Guide
 CHAPTER 10
About Scheduling
Schedules in NiagaraAX are done using schedule components, as found in the schedule palette
(Figure 10-1). You place these components in a station, configure, and link as needed to provide sched-
uling control of other components. Each schedule component has a “scheduler” view, which you use to
define events.

Figure 10-1 schedule palette

The following main sections provide more details:

• About the scheduling model
• About weekly schedules
• About calendar schedules (holidays)
• About trigger schedules
• Using schedules (schedule-related tasks)

About the scheduling model

NiagaraAX scheduling is summarized in the following sections:
• Schedule component categories
• Schedule component views
• Schedule component links
• Schedule special events
• Schedule exports and imports (master/slave)

Schedule component categories

The three categories of schedule components are as follows:
• Weekly schedules
These schedules define regular, repeating, events by “time-of-day” and “day-of-week.” Also, any
number of “special events” are configurable. Typically, these are the most used schedule compo-
nents. Four different types vary by data category (Boolean, Numeric, Enum, and String). Each is iden-
tical except for input/output. For more details, see “About weekly schedules” on page 10-3.
• Calendar schedule
A CalendarSchedule component is available to define specific days. Typically, you use them to define
days with scheduling exceptions (e.g. holidays), and reference them in the “special events” setup of
weekly schedules. For details, see “About calendar schedules (holidays)” on page 10-13.
• Trigger schedule
A TriggerSchedule component is used to schedule the firing of topics. As needed, you typically link
its output to an action of a control point or extension. For more details, see “About trigger schedules”
on page 10-18.

NiagaraAX-3.x
10–1
User Guide
About the scheduling model Chapter 10 – About Scheduling
Schedule component views May 1, 2007

Schedule component views

The default view for any schedule component is its “scheduler” view, where you define related days and
events.
• The Weekly Scheduler view for any weekly schedule component provides four tabs, as follows:
• Weekly Schedule — Specifies Sunday-through-Saturday (weekly) event times/values.
• Special Events — All exceptions to the defined weekly schedule, as special events.
• Properties — Important properties such as default output, schedule effective times, special
event cleanup operation, and schedule facets.
• Summary — For any selected day, provides summary of all schedule events, with source.
In addition, any weekly schedule component provides a “Current Day Summary” view, providing a
simple linear 24-hour graph of schedule event times and values for the current day.
• The Calendar Scheduler view for a CalendarSchedule provides a “calendar” where you add, edit, or
delete calendar days and establish relative priorities.
• The Trigger Scheduler view for a TriggerSchedule provides a two-part view combining a “day pick-
er” and an event “time picker” for specifying when topics are fired on those days.
At the bottom of any scheduler view are buttons Refresh and Save, described as follows:
Refresh
The Refresh button is always available.
When you click Refresh, one of two things happens:
• If the Save button is not available (no unsaved changes), clicking it re-synchronizes the view with
the component’s current configuration.
• If the Save button is available (unsaved changes), clicking it produces a dialog (Figure 10-2).

Figure 10-2 Refresh confirmation if unsaved changes

Your refresh confirmation dialog choices are as follows:

• Yes
Save all changes made in the view since last save. Equivalent to clicking Save.
• No
Clear all changes made in the view since last save (effective reset).
• Cancel
Cancels refresh, all unsaved changes remain as unsaved.
Save
The Save button is available only if you have made unsaved changes in the component’s scheduler.
Clicking it downloads your changes to the schedule component’s configuration. Immediately following,
the Save button is unavailable again.
Note: For weekly schedules (tabbed Weekly Scheduler view), you typically save while working in each tab, even
though any save applies to changes made on all tabs.

Schedule component links

To use weekly schedules and the trigger schedule, you link the component’s “Out” slot (as source) to a
slot on another component. The same schedule can be linked this way to many target components.
• Weekly schedule links
• Trigger schedule links
Typically, you do not link a CalendarSchedule. Instead, you reference one or more CalendarSchedules
from a weekly schedule, in its “special events” setup. This allows global editing of day definitions.
Weekly schedule links
Typically, you link a weekly schedule to one or more “writable” control points. For some examples, you
could link the Out slot of weekly schedule types as follows:
• BooleanSchedule to a BooleanWritable that is a proxy point for a Binary Output object in a BACnet
device.
• NumericSchedule to a NumericWritable that is a proxy point for setpoint NVI in a LON device.

NiagaraAX-3.x
10-2
User Guide
Chapter 10 – About Scheduling About weekly schedules
May 1, 2007 Schedule special events

By convention, when linking to a target writable point (with 16-level priority array), you select “In16”
among its different priority array inputs. However, you are free to select any available input level.
In a few cases, you may wish to “chain” weekly schedules from “Out” slot to “In” slot. This technique is
typically useful only if one of the chained schedules is “effective” during any period in time. In this case,
the Default Output value of all schedule components (except last in chain) must be null.
Trigger schedule links
Typically, you link a trigger schedule to an action of a control point or perhaps even more often, an action
of a point extension. For example, you could link a TriggerSchedule to the “ResetElapsedActiveTime”
action of a DiscreteTotalizerExt, a point extension for a BooleanPoint used to accumulate runtime. If the
trigger schedule was configured to fire only on the first day of every month (at 12:00am) that extension
could be used to hold the current month’s runtime.

Schedule special events

Special events apply to weekly schedules only, and are considered any exception to the (normal) weekly
schedule. Special events can be “one-time” only event changes or recurring event changes, such as
holidays. Configuration includes both day(s) of occurrence and related time-of-day events.
In the time-of-day event definitions of special events, you can have them “intermingle” with regular
weekly events, or completely override the weekly schedule. In addition, you visually prioritize special
events, via list order. This allows any overlapping special events to occur in an ordered fashion.
Each weekly schedule component has its own special events, configured on a Special Events tab in its
scheduler view. Event times (and values) entered for any special event apply to that schedule only.
However, if the special event is a “reference” type, days of its occurrence are specified in the Calendar-
Schedule component that is referenced. This allows you to globally change the days that special events
occur in weekly schedules, by editing one or more referenced CalendarSchedules. For more details, see
“CalendarSchedule Usage” on page 10-13.

Schedule exports and imports (master/slave)

Using the NiagaraAX driver architecture, you can create “master/slave” schedules in order to share
schedule configuration between devices. This allows you to globally update the configuration of any slave
schedule by simply making changes to its master schedule.
The typical application of this is in a multi-station Niagara network, where you:
• Import a schedule component from another station. Typically, you do this in a JACE station, import-
ing a schedule component that resides in a Supervisor station. This creates a local copy that you can
use and link into control logic, but cannot otherwise configure (change events, and so on).
When you import a NiagaraAX schedule, a “schedule export descriptor” is automatically created on the
sending (master) station, under the NiagaraStation component that represents the receiving side. This
allows for “sending-side” management of configuration synchronization. For more details, see “Station
Schedules import/export notes” on page 4-60.
If using the Bacnet driver, the same basic architecture is available. You can import BACnet Schedule and
Calendar objects from a BACnet device, and model them as NiagaraAX schedule components.
For more details, see the following topics in the Driver architecture section:
• “About the Schedules extension” on page 4-27.
• “About Schedules extension views” on page 4-44.
Note: The Bacnet driver lets you export NiagaraAX schedules from the station to existing BACnet Schedule and
Calendar objects in a BACnet device, acting as the “master” source. Also, you can expose Niagara schedule
components as BACnet Schedule or Calendar objects for access by any networked BACnet device. You do
this through configuration of the “Export Table” under the BacnetNetwork’s “Local Device.” For more
details, see the Bacnet Users Guide.

About weekly schedules

The following sections explain weekly schedule concepts:
• Types of weekly schedule components
• Weekly schedule output processing
• Weekly Scheduler view

NiagaraAX-3.x
10-3
User Guide
About weekly schedules Chapter 10 – About Scheduling
Types of weekly schedule components May 1, 2007

Types of weekly schedule components

Each component type varies only by data value category, meaning its Out slot (generally called “output”)
and its In slot (generally called “input”). For data category concepts, see “About data value categories” on
page 3-2. The schedule’s output and input are “Status<Type>” according to schedule component type, for
example, StatusBoolean if a BooleanSchedule, StatusEnum if an EnumSchedule.
The four weekly schedule component types are:
• BooleanSchedule
• EnumSchedule
• NumericSchedule
• StringSchedule
In typical use, only outputs of schedules are linked to other components for scheduling control, such as
“writable” points of the same type. Figure 10-3 shows a BooleanSchedule and NumericSchedule, each
linked to two writable points. See “Schedule component links” on page 10-2 for more details.

Figure 10-3 Schedules linked to writable points

About the BooleanSchedule

The BooleanSchedule is typically the most used weekly schedule. Use it directly for schedule control of
BooleanWritable points (typically proxy points). If needed, it also has application for linkage to slots in
extensions. For example, using an intermediate kitControl object (say, a “Not” logic-type object) use a
BooleanSchedule for linkage to the Enabled slot of an alarm extension.
About the EnumSchedule
The EnumSchedule allows schedule control of EnumWritable points (typically proxy points). For
example, link it to an EnumWritable that proxies a BACnet Multistate Output object, or to an
EnumWritable that proxies a LON NVI (using an enumerated SNVT).
To properly use an EnumSchedule, first define its Facets to match those in linked EnumWritable(s).
About the NumericSchedule
The NumericSchedule allows schedule control of NumericWritable points (typically proxy points),
which may represent setpoints, limits, or any number of other variables.
About the StringSchedule
The StringSchedule allows schedule control of StringWritable points (possibly proxy points).

Weekly schedule output processing

For any weekly schedule (BooleanSchedule, EnumSchedule, NumericSchedule, StringSchedule), output
recalculation occurs upon any of the following:
• any saved change to its configuration
• any change at its input
• station startup
• any change to the system clock
Each component has an Out slot and an Out Source slot. In addition, Next Time and Next Value slots are
available. By default, all of these slots are “pinned” on the component’s shape on the wire sheet, as shown
in Figure 10-3. Upon any output change, all of these slots are updated.
Out slot
A schedule’s output value is determined by the following, in highest-to-lowest priority:

NiagaraAX-3.x
10-4
User Guide
Chapter 10 – About Scheduling About weekly schedules
May 1, 2007 Weekly Scheduler view

1. To any “non-null” value at its In slot (if linked)

This value is immediately passed to its output. Otherwise (if null), processing continues.
2. If the schedule is not effective, the output goes to the default output value.
If the schedule is effective, the output goes to the (highest priority) active special event (if any).
3. To the active weekly schedule event (if any).
4. To the default output value.
For more details on effective schedules, see “Effective Period” on page 10-11.
Out Source slot
Out Source provides a string “source description” of the current output, as one of the following:
• Input
• Special Event: <SpecialEventName>
• Week: <day_of_week>
• Default Output
Examples might appear as “Week: monday” or “Special Event: Christmas Break”
Next Time and Next Value slots
These slots provide “look-ahead” data: the next known schedule output value, and its time of change.
• Next Time — Displays in Baja AbsTime format, for example: 03-Feb-05 5:00 PM
• Next Value — The next scheduled output value.
Typical application is for informational display. If needed, slots can be linked into control logic. For
example, TimeDifference and CurrentTime objects (kitControl, Timer) provide AbsTime slots too.

Weekly Scheduler view

Double-clicking any weekly schedule in Workbench produces its Scheduler view (Figure 10-4).

Figure 10-4 Scheduler view for weekly schedule

There are four tabs: Weekly Schedule, Special Events, Properties, and Summary, as described ahead.
Note: Buttons Refresh and Save apply to all tabs in the Scheduler view (not just the one displayed).
Weekly Schedule
Use this tab in the Weekly Scheduler view to enter regular schedule events, that is “normal schedule
events” that repeat from week to week, based on the day of the week and the time of day. By default, any
existing events appear as greenish blocks, while unscheduled (default output) time appears in white.
Use is mostly straightforward, to add a new event simply click in a day at the approximate event start time,
and drag down to define the start and finish time (Figure 10-5). The event remains selected (by default,
dark blue) when you release the mouse button.
Note: If an EnumSchedule, you should define its range facet from the Scheduler’s Properties tab before adding
events. See “Facets” on page 10-11 for more details.

NiagaraAX-3.x
10-5
User Guide
About weekly schedules Chapter 10 – About Scheduling
Weekly Scheduler view May 1, 2007

Figure 10-5 Click and drag to enter weekly events

As needed, click again and drag on the event’s top or bottom to change its start or finish time (in broad
increments).
Additional details about the Weekly Schedule tab are as follows:
• Event time “tuning”
• Output value
• Right-click menus
Event time “tuning” With any event selected, “fine tune” its start and finish time using the controls,
selecting the hours portion or minutes portion (Figure 10-6). Or, click and type values in directly.

Figure 10-6 Define start and finish time

Note: For any event, start time is inclusive, and the event extends to (but is exclusive of ) the end time. In other
words, there is no output “blip” between adjacent events, even if across days. For example, if a Monday
event ends at midnight, then a Tuesday event starts at midnight, the schedule output is continuous
(providing both events have the same Output value).
Output value For any event, you can select the “null” checkbox (the schedule’s calculated value is null
for that event). However, you typically select or type a value instead, as follows:
• If a Boolean or EnumSchedule select the event value in the output field, see Figure 10-7, left.
Note: If an EnumSchedule, first specify its facets (on Properties tab) before entering values. This
allows selection of possible values.
• If a NumericSchedule or StringSchedule, you type the value in the output field, then press Enter to
register it in the event block, as shown in Figure 10-7, right.

Figure 10-7 Select (Boolean, Enum) or type (Numeric, String) output value

Right-click menus Right-click in the weekly schedule area for an event menu. If you have any event
selected, this menu provides the most commands, as shown in Figure 10-8.

NiagaraAX-3.x
10-6
User Guide
Chapter 10 – About Scheduling About weekly schedules
May 1, 2007 Weekly Scheduler view

Figure 10-8 Right-click menu with event selected

Event menu options are straightforward, and may include the following:
• Delete Event — Deletes the selected event.
• Paste Day — Appears only if copy day option was used first. Copies all events into selected day.
• All Day Event — Makes currently selected (or last entered) event extend to entire day.
• Apply M-F — Copies all events in the selected day to Mon, Tue, Wed, Thu, and Fri (and overwrites
any existing events on those days).
• Copy Day — Copies all events in the selected day, to use with paste day option.
• Clear Day — Clears all events in the selected day.
• Clear Week — Clears all events in the entire weekly schedule.
Special Events
Use this Weekly Scheduler view tab to enter all exceptions to the schedule’s weekly schedule, broadly
called “special events.” For general information, see “Schedule special events” on page 10-3.
As shown in Figure 10-9, existing special events (if any) are listed in the table by name and summary.
When you select a special event, its day(s) of occurrence are highlighted in the monthly calendars at the
top of the view, and its associated event actions are displayed in the right-side column.

Figure 10-9 Special Events tab in weekly Scheduler

Additional details about the Special Events tab are as follows:

• Adding special events
• Event times and output values
• Special event priorities
• Right-click menus and other controls
Adding special events Click the Add button to add a new special event. An Add dialog appears, as
shown in Figure 10-10.

NiagaraAX-3.x
10-7
User Guide
About weekly schedules Chapter 10 – About Scheduling
Weekly Scheduler view May 1, 2007

Figure 10-10 Special Events Add dialog

Dialog options are described as follows:

• Name — Your descriptive name for special event, perhaps “Christmas_Break” or “Half_Day.” The
default value is simply “Event.” You can change this later, if needed.
• Type — Determines selection criteria for day or days, with the following choices:
• Date — (default) By various combinations of weekday, numerical date, month or month com-
binations, and year.
• Date Range — By start and end range, using for each a combination of day, month, year.
• Week and Day — By combination of day of week, week in month, month.
• Custom — By various combinations of day, month, weekdays, and year.
• Reference — By reference to a specific CalendarSchedule component in the station.
For details on most Type selections, see “Calendar day selections” on page 10-15. If you select type
Reference, a second Add dialog appears, as shown in Figure 10-11. It lists all CalendarSchedules
(Calendars) available in the station, by slot path. Select any one for the day(s) portion of this special event.

Figure 10-11 Reference special event Add dialog

After you have a name and type selected (and defined as needed), click OK to add it to this schedule’s
special events. It remains selected for further editing, except for type.
Event times and output values A newly-created special event has no events defined. With the special
event selected, click in the right-side events column and enter events as necessary. Start, finish, and
output controls work the same as in the Weekly Schedule tab. See “Event time “tuning”” on page 10-6 and
“Output value” on page 10-6 for details.
You can also right-click in the column for an event menu, as shown in Figure 10-12. This is useful to add
an all-day event or set the entire day to the schedule’s default value.

NiagaraAX-3.x
10-8
User Guide
Chapter 10 – About Scheduling About weekly schedules
May 1, 2007 Weekly Scheduler view

Figure 10-12 Special event schedule actions

Note: You must specify events for any special event to occur. Where nothing is scheduled, the special event relin-
quishes control back to any lower-priority schedule events, and finally “intermingles” with the weekly
schedule. To completely override the weekly schedule, configure a special event for the entire day.
Special event priorities All special events take priority over regular weekly events. Among special
events, you define relative priorities by the order of listing in the Special Events table, as follows:
• Highest priority is at top of list. Events in this special event, when active, always occur.
• Lowest priority is at bottom of list. Events occur only if not overlapped by other special events active
during the same period.
Change a special event’s priority by selecting it and using the priority arrow buttons (Figure 10-13).

Figure 10-13 Change priority by listing order

Right-click menus and other controls Right-click in the special events table for a menu. If you have any
special event selected, this menu provides the most commands, as shown in Figure 10-14.

Figure 10-14 Right-click menu with event selected

Special event menu options are straightforward, and may include the following:
• Add — Add a new special event (same as using Add button).
• Edit — Edit day(s) selection criteria (but not changing special event type). Same as Edit button.
• Rename — Rename selected special event (same as using Rename button).
• Priority (up) — Move special event up in priority list (same as using Priority button).
• Priority (down) — Move special event down in priority list (same as using Priority button).
• Delete — Removes selected special event from the schedule component.
Note: When you delete a special event, a confirmation dialog appears as shown in Figure 10-15.

NiagaraAX-3.x
10-9
User Guide
About weekly schedules Chapter 10 – About Scheduling
Weekly Scheduler view May 1, 2007

Figure 10-15 Delete special event confirmation

Click Yes to delete the special event, or No to keep it.

When you first access the Special Events tab, the current day is highlighted in the left-most calendar
month at the top of the view. As needed, click on Next Month and Prev Month, or Next Page and
Prev Page to traverse the calendar ahead or back in time.
When you select a special event in the table, if it occurs in any currently displayed month, its associated
day or days are highlighted as shown in Figure 10-16.

Figure 10-16 Special event highlights in calendar block

Note: A special event must have at least one defined event action to be highlighted in a calendar.
Return to the current calendar month and day by clicking the Today button.
Properties
As shown in Figure 10-17, this tab in Weekly Scheduler view is where you specify the schedule’s:
• Effective Period
• Default Output
• Facets
• Cleanup Special Events action

Figure 10-17 Properties tab in weekly Scheduler

NiagaraAX-3.x
10-10
User Guide
Chapter 10 – About Scheduling About weekly schedules
May 1, 2007 Weekly Scheduler view

Effective Period By default, a weekly schedule added from the schedule palette is always effective.
Whenever a schedule component is not effective, its output (Out slot) goes to its default output value,
regardless of its weekly schedule or any special events.
In most cases, you leave weekly schedules as always effective. However, if you have an application for a
schedule effective only at certain times, use the “start” through “end” range fields to limit the effective
period. When you Save the changes, only effective days in the calendar months are shown highlighted
green.
Default Output Whenever a schedule event (special or weekly) is not defined, the schedule component’s
output (“Out” slot) is this value. The white area in listed events indicates where the default value is used
and displays the current default value, as shown in Figure 10-18. The default output value is also used
whenever the schedule is not effective.

Figure 10-18 Default output is white area in schedule events

Note that “null” is an available choice—depending on control logic, this may be a valid choice.
As copied from the schedule palette, the default “Default Output” varies by schedule type, as follows:
• BooleanSchedule — false
• EnumSchedule — null
• NumericSchedule — null
• StringSchedule — null
Facets The schedule component’s facets determine how its output value is formatted for display. For
example, instead of “true” and “false” for a BooleanSchedule, you may need “On” and “Off ” instead.
Assigned facets appear in scheduler views when adding events, displaying summary data, and so on. For
complete details, see “About point facets” on page 3-7.
Note: Facets are especially important for EnumSchedules. You need to define “range” facets before you add weekly
schedule events (in order to pick an event’s enumerated value). Range facets should match those used in any
controlled (output-linked) EnumWritables. For related details, see “Facets importance for Enum points” on
page 3-7.
In the case of StringSchedules (as for all string-type components) facets have no application.
Figure 10-19 shows output selections for an EnumSchedule with its range facet defined as
“lonworks:LonOccupancyEnum,” one of the available frozen facets.

NiagaraAX-3.x
10-11
User Guide
About weekly schedules Chapter 10 – About Scheduling
Weekly Scheduler view May 1, 2007

Figure 10-19 Facets determine event value selections for EnumSchedules

By default, facets for schedule components as copied from the schedule palette are as follows:
• BooleanSchedule — trueText: true, falseText: false
• EnumSchedule — range: <not defined>
• NumericSchedule — units: (null), precision: 1
• StringSchedule — (not applicable)
Cleanup Special Events This property is either true (default) or false.
• If true, “one-time” special events that have occurred (and will not be effective again) are automati-
cally deleted. When a special event is deleted, a message is sent to the schedule log, and that special
event no longer appears in the Special Events tab.
• If false, “one-time” special events are retained, even though they will not occur again.
Summary
The summary tab in the Weekly Scheduler view shows a summary listing of all scheduled events for any
one selected day in a weekly schedule (Figure 10-20). Events may be from the normal weekly schedule,
special events, or a combination of both. Unlike with other tabbed views, this one is read-only.

Figure 10-20 Summary tab shows all events for any selected day

In the top calendar month area:

• Days with schedule events are shown highlighted green.

NiagaraAX-3.x
10-12
User Guide
Chapter 10 – About Scheduling About calendar schedules (holidays)
May 1, 2007 CalendarSchedule Usage

• Days without schedule events (only default output) are shown in white.
As needed, click on Next Month and Prev Month, or Next Page and Prev Page to traverse the
calendar ahead or back in time.
• Click any day to see its events.
• Click Today (at top) to see the current day’s events.
The table lists each event’s start timestamp, the schedule’s output value, and the event source. See “Out
Source slot” on page 10-5 for how event source information appears.

About calendar schedules (holidays)

Calendar schedules (CalendarSchedule component) specify entire days, using the following four types of
day event selections:
• Date
• Date Range
• Week and Day
• Custom
You can add as many day events as needed in the same CalendarSchedule. The following sections provide
more details:
• CalendarSchedule Usage
• Calendar Scheduler view
• Calendar day selections
• CalendarSchedule slots and other notes

CalendarSchedule Usage
Instead of linking CalendarSchedules, you typically “reference” them from the “special events” configu-
ration of one or more weekly schedules. Each referenced CalendarSchedule defines the “day portion” of
a special event. Then, you configure time-of-day events in each special event, as needed.

Figure 10-21 Example referenced CalendarSchedules

For example, Figure 10-21 shows a BooleanSchedule and a portion of its special events tab, listing five
special events. Three of these are “Reference” types, meaning their calendar day(s) are defined remotely
in the configuration of the referenced CalendarSchedules. Although all components are shown here in
the same container, quite often CalendarSchedules are located elsewhere in the station.
CalendarSchedule usage by “special event reference” allows global changing of day definitions, where
multiple weekly schedules can reference one or more CalendarSchedules. Any edit of a CalendarSchedule
affects all weekly schedules containing a special event that references it.

Calendar Scheduler view

Double-click a CalendarSchedule to see its default Calendar Scheduler view, as shown in Figure 10-22.

NiagaraAX-3.x
10-13
User Guide
About calendar schedules (holidays) Chapter 10 – About Scheduling
Calendar Scheduler view May 1, 2007

Figure 10-22 Calendar Scheduler view

As shown in Figure 10-22, existing calendar events (if any) are listed in the table by name and summary.
When you select a calendar event, its day(s) of occurrence are highlighted in green in the monthly
calendars at the top of the view.
Additional Calendar Scheduler topics include:
• Adding calendar events
• Right-click menus and other controls
Adding calendar events
Click the Add button to add a new calendar event. An Add dialog appears, as shown in Figure 10-23.

Figure 10-23 Special Events Add dialog

Dialog options are described as follows:

• Name — Your descriptive name for the calendar days, perhaps “Thanksgiving_Break” or
“Cleaning_2.” The default value is simply “Event.” You can change this later, if needed.
• Type — Determines selection criteria for day or days, with the following choices:
• Date — (default) By various combinations of weekday, numerical date, month or month combina-
tions, and year.
• Date Range — By start and end range, using for each a combination of day, month, year.
• Week and Day — By combination of day of week, week in month, month.
• Custom — By various combinations of day, month, weekdays, and year.
For details on Type selections, see “Calendar day selections” on page 10-15.
After you have a name and type selected (and defined as needed), click OK to add it to this calendar’s days.
It remains selected for further editing, except for type.

NiagaraAX-3.x
10-14
User Guide
Chapter 10 – About Scheduling About calendar schedules (holidays)
May 1, 2007 Calendar day selections

Right-click menus and other controls

Right-click in the calendar events table for a menu. If you have any calendar event selected, this menu
provides the most commands, as shown in Figure 10-24.

Figure 10-24 Right-click menu with event selected

Note: Priority selections (right-click menu or in bottom buttons) only affect the list order for events in a Calen-
darSchedule—true priority applies only to special events (in weekly schedules).
Calendar event menu options are straightforward, and may include the following:
• Add — Add a new calendar event (same as using Add button).
• Edit — Edit day(s) selection criteria (but not changing calendar type). Same as Edit button.
• Rename — Rename selected calendar event (same as using Rename button).
• Priority (up) — Move calendar event up in display list (same as using Priority button).
• Priority (down) — Move calendar event down in display list (same as using Priority button).
• Delete — Removes selected calendar event from the schedule component.
Note: When you delete a calendar event, a confirmation dialog appears as shown in Figure 10-25.

Figure 10-25 Delete calendar event confirmation

Click Yes to delete the calendar entry, or No to keep it.

When you first access the Calendar Scheduler, the current day is highlighted in the left-most calendar
month at the top of the view. As needed, click on Next Month and Prev Month, or Next Page and
Prev Page to traverse the calendar ahead or back in time.
Return to the current calendar month and day by clicking the Today button.

Calendar day selections

When adding calendar days in a CalendarSchedule, a special event in a weekly schedule, or a trigger event
in a trigger schedule, the following “Type” selections are available:
• Date — see “Date selection notes” on page 10-15
• Date Range — see “Date range selection notes” on page 10-16
• Week and Day — see “Week and day selection notes” on page 10-16
• Custom — see “Custom selection notes” on page 10-17
Date selection notes
As shown in Figure 10-26, Date calendar selection has 4 criteria: weekday, day-of-month, month-of-year,
and year.

Figure 10-26 Calendar selection by date

You can make only one selection in each criteria.

NiagaraAX-3.x
10-15
User Guide
About calendar schedules (holidays) Chapter 10 – About Scheduling
Calendar day selections May 1, 2007

Each criteria offers an “any” selection, in addition to a specific selection (weekday, day-of-month, month-
of-year, year). In addition, the month-of-year criteria provides an “every other month” selection, as one of
the following:
• Jan-Mar-May-Jul-Sep-Nov
• Feb-Apr-Jun-Aug-Oct-Dec
Result of selections is by “ANDing” all criteria. For example, if you select weekday of Tuesday, day of
month as 5, and remaining criteria “any,” the event is specified only on Tuesday, the fifth of any month
in any year. If a month does not have Tuesday the fifth, then there is no event that month.
Date range selection notes
As shown in Figure 10-27, Date Range calendar selection has a start range and end range, each with 3
criteria: day-of-month, month-of-year, and year.

Figure 10-27 Calendar selection by date range

You can make only one selection in each criteria.

Each criteria offers an “any” selection, in addition to a specific selection (day-of-month, month-of-year,
year). In addition, the month-of-year criteria provides an “every other month” selection, as one of the
following:
• Jan-Mar-May-Jul-Sep-Nov
• Feb-Apr-Jun-Aug-Oct-Dec
In each date range, result is from “ANDing” the criteria. In addition, the start day can be after the end
date. For example, as shown in Figure 10-27, the start day can be in December and the end date in March.
This event occurs December, January and February.
Week and day selection notes
As shown in Figure 10-28, Week and Day calendar selection has 3 criteria: weekday, week-in-month, and
month-of-year.

Figure 10-28 Calendar selection by week and day

You can make only one selection in each criteria.

Each criteria offers an “any” selection, in addition to a specific selection (weekday, week-in-month,
month-of-year). In addition, the following criteria offer additional selections, as follows:
• week-in-month: last 7 days
• month-of-year:
• Jan-Mar-May-Jul-Sep-Nov
• Feb-Apr-Jun-Aug-Oct-Dec
The result is from “ANDing” the criteria. For example, as shown in Figure 10-28, if selections are for
weekday as Monday, the month as February, and the week as 3, the event occurs only on the third Monday
in February.

NiagaraAX-3.x
10-16
User Guide
Chapter 10 – About Scheduling About calendar schedules (holidays)
May 1, 2007 CalendarSchedule slots and other notes

Custom selection notes

As shown in Figure 10-29, Custom calendar selection has 5 criteria: day-of-month, month-of-year,
weekday, week-in-month, and year.

Figure 10-29 Calendar selection by custom

Unlike with other calendar types, you can make multiple selections within each criteria (except if you
select “any,” which allows only that selection). To select multiples, first select something other than
“Any,” then hold down the Ctrl or Shift key while you select more values.
Each criteria offers an “any” selection, in addition to a specific selection. In addition, the following criteria
offer additional selections, as follows:
• day-of-month:
• Last Day
• Last 7 Days
• week-in-month: Last 7 Days
Within any criteria, selections are “OR’ed.” The overall result is from “AND’ing” all criteria. For example,
Figure 10-29 shows a custom selection for U.S. General Election Day, which must be configured as the
“first Tuesday after the first Monday in November.”

CalendarSchedule slots and other notes

The CalendarSchedule has a StatusBoolean input and output (slots “In” and “Out”). In most applications
they are left unlinked.
• Output is true during any configured calendar day(s), otherwise it is false.
• Input overrides the calendar schedule calculation (if linked). Any non-null input (true or false) is im-
mediately passed to the output.
By default, for any CalendarSchedule copied from the schedule palette, the following additional slots are
pinned on the component’s glyph (shape on wire sheet):
• Next Time
Time of next scheduled output change for the CalendarSchedule. If more than a year away, this value
is null.
• Next Value
The next scheduled output value, at “Next Time”. Value is meaningless if Next Time is null.
From the CalendarSchedule’s property sheet, you can access and change the following additional slots:
• Cleanup Expired Events
Either true (default) or false.
• If true, calendar events of type “Date” and “Date Range” that have already occurred, and cannot occur
again (as configured), are automatically deleted after they occur. This is recorded in the schedule
log, and you no longer see them in the Calendar Scheduler view.
• If false, all calendar events are retained, even if they cannot occur again (as configured).
• Facets
Facets applied to the input and output, which by default are simply “true” and “false.”

NiagaraAX-3.x
10-17
User Guide
About trigger schedules Chapter 10 – About Scheduling
Trigger Scheduler view May 1, 2007

About trigger schedules

TriggerSchedules are special-purpose schedules, providing scheduling control for either linked actions
or topics of other components. Figure 10-30 shows a simple example of a TriggerSchedule linked to an
action slot of a DiscreteTotalizerExt, which was “composited” in the parent BooleanWritable.

Figure 10-30 Example TriggerSchedule

This schedule is configured to simply fire once at midnight on the first day of every month. The trigger at
the “ResetElapsedActiveTime” slot zeroes the runtime accumulated from the previous month.
The following sections provide more TriggerSchedule details:
• Trigger Scheduler view
• TriggerSchedule slots and other notes

Trigger Scheduler view

Double-click a TriggerSchedule to see its default Trigger Scheduler view, as shown in Figure 10-31.

Figure 10-31 Trigger Scheduler view

As shown in Figure 10-31, the Trigger Scheduler has two sides:

• Calendar (left) side — where you add events. It operates like the Calendar Scheduler view.
• Time picker (right) side — where you add trigger times for the schedule to fire its trigger output. In-
cluded is the ability to add repeating intervals.
Note: Trigger times, as set in the time picker, apply to all calendar events (if more than one).
Existing trigger events (if any) are listed in the table by name and summary. When you select a trigger
event, its day(s) of occurrence are highlighted in green in the monthly calendars at the top of the view.
Trigger times are listed in the time picker area.
Additional Trigger Scheduler topics include:
• Adding trigger events
• Adding trigger event times

NiagaraAX-3.x
10-18
User Guide
Chapter 10 – About Scheduling About trigger schedules
May 1, 2007 Trigger Scheduler view

Adding trigger events

Click the Add button to add a new trigger event. An Add dialog appears, as shown in Figure 10-32.

Figure 10-32 Trigger Event Add dialog

Dialog options are described as follows:

• Name — Your descriptive name for the trigger events, perhaps “FirstDOM” or “Each_WorkHr.” The
default value is simply “Event.” You can change this later, if needed.
• Type — Determines selection criteria for day or days, with the following choices:
• Date — (default) By various combinations of weekday, numerical date, month or month combina-
tions, and year.
• Date Range — By start and end range, using for each a combination of day, month, year.
• Week and Day — By combination of day of week, week in month, month.
• Custom — By various combinations of day, month, weekdays, and year.
For details on Type selections, see “Calendar day selections” on page 10-15.
After you have a name and type selected (and defined as needed), click OK to add it to this calendar’s days.
It remains selected for further editing, except for type. Typically, you add one or more trigger event times
on the time picker side. See “Adding trigger event times” on page 10-19.
Adding trigger event times
By default, a single “midnight” trigger time already exists (you can delete it if desired). To add other
trigger times, use the controls at the bottom of the time picker side, as shown in Figure 10-33.

Figure 10-33 Trigger time picker controls

Set the desired time in the hour:minute editor, either by clicking up/down controls or typing in times
directly. Click the Add button to add a trigger at that time, which adds it to the list. You can also enter
multiple triggers simultaneously, using the Range option.
Range option To add multiple triggers that occur at a repeating interval, select the Range checkbox. This
enables the Range End and Range Interval fields for entering values, as shown in Figure 10-34.

NiagaraAX-3.x
10-19
User Guide
About trigger schedules Chapter 10 – About Scheduling
Trigger Scheduler view May 1, 2007

Figure 10-34 Range option in trigger time picker

When entering a trigger range, note that the top (hour:minute) editor acts as the first (or Range Begin)
trigger time. By default, the Range Interval is set to one hour (“+00001h 00m 00.000s”). You can set this
to whatever interval is needed.
To delete a trigger time, click to select, then click the Remove button. To select multiple trigger times,
hold down the Ctrl or Shift key while you select.
Right-click menus and other controls
The time picker (right side) has no right-click menu—simply use the bottom controls to configure trigger
times. The calendar (left side) has an available right-click menu. If you have any calendar event selected,
this menu provides the most commands, as shown in Figure 10-35.

Figure 10-35 Right-click menu with event selected

Note: Priority selections (right-click menu or in bottom buttons) only affect the list order for events in a Trigger-
Schedule—true priority applies only to special events (in weekly schedules).
Event menu options are straightforward, and may include the following:
• Add — Add a new calendar event (same as using Add button).
• Edit — Edit day(s) selection criteria (but not changing calendar type). Same as Edit button.
• Rename — Rename selected calendar event (same as using Rename button).
• Priority (up) — Move calendar event up in display list (same as using Priority button).
• Priority (down) — Move calendar event down in display list (same as using Priority button).
• Delete — Removes selected calendar event from the schedule component.
Note: When you delete a calendar event, a confirmation dialog appears as shown in Figure 10-36.

Figure 10-36 Delete calendar event confirmation

Click Yes to delete the calendar entry, or No to keep it.

NiagaraAX-3.x
10-20
User Guide
Chapter 10 – About Scheduling Using schedules
May 1, 2007 TriggerSchedule slots and other notes

When you first access the Trigger Scheduler, the current day is highlighted in the left-most calendar
month at the top of the view. As needed, click on Next Month and Prev Month, or Next Page and
Prev Page to traverse the calendar ahead or back in time.
Return to the current calendar month and day by clicking the Today button.

TriggerSchedule slots and other notes

By default, for any TriggerSchedule copied from the schedule palette, the main “Trigger” output slot is
pinned on the component’s glyph (shape on wire sheet), as well as the following additional ones:
• Enabled
Either true (default) or false. While false, firing of trigger outputs is disabled. If linking, note that this
slot uses simple Boolean, you may need a StatusBooleanToBoolean (kitControl) component.
• Last Trigger
Timestamp of the last firing of the trigger output.
• Next Trigger
Next scheduled trigger firing time.
From the TriggerSchedule’s property sheet, you can access the following additional slots:
• Next Trigger Search Limit
How far into the future to search for the next trigger. It is possible a poorly-configured schedule will
never fire a trigger. This setting prevents an infinite search. Default is one year (8760 hours).
• Last Modified
(read only) Timestamp of last configuration change.
• Status
(read only) Status of the schedule component, typically “{ok}.”
Trigger Missed slot
In addition to the “main” Trigger output slot, the TriggerSchedule has “Trigger Missed” slot, also a topic
type slot. If the station was not running when a scheduled trigger was to occur (appeared previously in
“Next Trigger” property), upon station startup the Trigger Missed slot fires once.
Note: Trigger Missed always fires only once, no matter how many triggers may have been missed.

Using schedules
The following main sections provide common tasks for working with schedules in NiagaraAX:
• Adding a schedule or calendar
• Configuring schedules and calendars
• Linking schedules
• Importing schedules

Adding a schedule or calendar

In your station, you can copy a default schedule component directly from the schedule palette, or copy a
pre-configured schedule component from a saved bog file or other station database.
Note: Once in your station and configured, you can also duplicate schedule components (see “To duplicate a
component (property sheet, nav side bar, or wire sheet view)” on page 12-14.

To add a component from the schedule palette

You can add (copy) a new schedule component from the schedule palette, dragging onto a container in
the Nav tree view or into the wire sheet view.
To add a new schedule component from the schedule palette, do the following:
Step 1 Open the schedule palette. See “Using the palette side bar” on page 12-9 for general details.
When the palette is open, schedule components are listed, as shown in Figure 10-1 on page 1.
Step 2 Drag the component needed from the palette to either:
• In the Nav tree, onto a folder in your station.
• In the view pane, into the wire sheet of a folder in your station.
A Name dialog appears.
Step 3 In the Name dialog, type the desired name and click OK.
The schedule or calendar is now in your station, with default values.

NiagaraAX-3.x
10-21
User Guide
Using schedules Chapter 10 – About Scheduling
Configuring schedules and calendars May 1, 2007

To copy an existing, saved (configured) schedule component

You can add (copy) a new schedule component from one previously configured, dragging onto a
container in the Nav tree view or into a folder’s wire sheet view.
To add a new schedule component as a copy of an existing saved component, do the following:
Step 1 In the Nav tree, expand My File System and navigate to the saved bog file or station config.bog file.
See “Editing components” on page 12-11 for more details.
Step 2 When you locate the desired schedule component, right-click and select Copy.
Step 3 Paste the copied component doing a right-click Paste from either:
• In the Nav tree, on a folder in your station
• In the view pane, in the wire sheet of a folder in your station.
A Name dialog appears.
Step 4 In the Name dialog, type the desired name and click OK.
The schedule or calendar is now in your station, with pre-configured values.

Configuring schedules and calendars

Typically, you perform most configuration of any schedule component from its default “scheduler” view.
For an overview, see “Schedule component views” on page 10-2.
• Configuring weekly schedules
• Configuring calendar schedules
• Configuring trigger schedules
Configuring weekly schedules
Weekly schedules (BooleanSchedule, EnumSchedule, NumericSchedule, and StringSchedule) are among
the most used schedule components.

To configure a weekly schedule

You use the Weekly Scheduler view to configure a weekly schedule. There are many ways you can
approach configuration, the following procedure is only one way.
To configure a weekly schedule, do the following:
Step 1 Double-click the weekly schedule component.
The Weekly Scheduler displays, as shown in Figure 10-4 on page 5.
Step 2 Configure important properties. See “To configure a weekly schedule’s properties” on page 10-22.
Step 3 Configure the normal weekly schedule. See “To configure the weekly (normal) schedule” on page 10-22.
Step 4 Configure special events, if any. See “To add and configure special events” on page 10-23.
Step 5 Review all configuration. See “To review a weekly schedule’s configuration” on page 10-23.

To configure a weekly schedule’s properties

To configure a weekly schedule’s properties, do the following:
Step 1 In the Weekly Scheduler view, click the Properties tab, and configure the following:
• Facets — This is critical if an EnumSchedule, and optional if a BooleanSchedule or NumericSched-
ule. Note that facets do not apply if a StringSchedule.
• Default Output — This is the schedule’s output whenever an event (either weekly or special event)
is not active. It is also used whenever the component is “not effective.”
Typically, you leave other properties at default values.
Step 2 Click Save.

To configure the weekly (normal) schedule

To configure the normal weekly schedule, do the following:
Step 1 In the Weekly Scheduler view, click the Weekly Schedule tab.
Step 2 In the events table, click and drag to add an event, and enter its output value.
For details, see “Event time “tuning”” on page 10-6 and “Output value” on page 10-6.
Note: If a Boolean or EnumSchedule, select output value from the drop-down control.
If a Numeric or StringSchedule, type the output value and press Enter.
Step 3 Right-click the event and use whatever menus are needed.

NiagaraAX-3.x
10-22
User Guide
Chapter 10 – About Scheduling Using schedules
May 1, 2007 Configuring schedules and calendars

For details, see “Right-click menus” on page 10-6.

Step 4 Continue to add, delete, or adjust events as needed.
Step 5 When the weekly schedule is what you want, click Save.

To add and configure special events

Special events are exceptions to the normal weekly schedule, and typically include recurring holidays and
“one-time” events. For more details, see “Schedule special events” on page 10-3.
To add and configure special events in a weekly schedule, do the following:
Step 1 In the Weekly Scheduler view, click the Special Events tab.
Step 2 Click the Add button for a dialog to add a special event.
In the Add dialog, specify:
• Name — Type a unique, identifiable name.
• Type — Select the calendar type, and enter specific day criteria (according to type).
For details, see “Adding special events” on page 10-7 and “Calendar day selections” on page 10-15.
Step 3 After naming, selecting the event type, and entering the selection criteria, click OK.
The special event is listed in the special events table, with your assigned name.
Step 4 Click the special event to select it.
Step 5 In the right-side events column, you can either:
• Click and drag to enter events that override (yet “intermingle” with) normal weekly events.
• Right-click and select an all-day event or default output value. This negates the normal weekly
schedule.
For more details see “Event times and output values” on page 10-8.
Step 6 Continue to add, edit, rename, or delete special events as needed. See “Right-click menus and other
controls” on page 10-9, and “Special event priorities” on page 10-9.
Step 7 When special events are like you want, click Save.

To review a weekly schedule’s configuration

Use the read-only Summary tab to review a weekly schedule’s configuration.
To review the configuration of a weekly schedule, do the following:
Step 1 In the Weekly Scheduler view, click the Summary tab.
The calendar shows the current day with its schedule events, including output and output source.
Step 2 Click any day on any calendar month to see its schedule events.
Step 3 If adjustments are necessary, click the Weekly Schedule, Special Events, or Properties tab as needed, and
make changes. Click Save when done.
Configuring calendar schedules
Calendar schedules let you globally specify holidays and other special days in the system. For details, see
“About calendar schedules (holidays)” on page 10-13.

To configure a calendar schedule

You use the Calendar Scheduler view to configure a CalendarSchedule.
To configure a calendar schedule, do the following:
Step 1 Double-click the CalendarSchedule component.
The Calendar Scheduler displays, as shown in Figure 10-22 on page 14.
Step 2 Click the Add button for a dialog to add a calendar event.
In the Add dialog, specify:
• Name — Type a unique, identifiable name.
• Type — Select the calendar type, and enter specific day criteria (according to type).
For details, see “Calendar day selections” on page 10-15.
Step 3 After naming, selecting the event type, and entering the selection criteria, click OK.
The calendar event is listed in the events table, with your assigned name.
Step 4 Continue to add, edit, rename, or delete calendar events as needed. See “Right-click menus and other
controls” on page 10-15.

NiagaraAX-3.x
10-23
User Guide
Using schedules Chapter 10 – About Scheduling
Linking schedules May 1, 2007

Step 5 When calendar events are like you want, click Save.
Configuring trigger schedules
Trigger schedules provide scheduling control for actions of linked components or their child extensions.
For details, see “About trigger schedules” on page 10-18.

To configure a trigger schedule

You use the Trigger Scheduler view to configure a TriggerSchedule.
To configure a trigger schedule, do the following:
Step 1 Double-click the TriggerSchedule component.
The Trigger Scheduler displays, as shown in Figure 10-31 on page 18.
This view has a calendar side (left) and time picker (right side).
Step 2 Click the Add button for a dialog to add a trigger event.
In the Add dialog, specify:
• Name — Type a unique, identifiable name.
• Type — Select the calendar type, and enter specific day criteria (according to type).
For details, see “Adding trigger events” on page 10-19 and “Calendar day selections” on page 10-15.
Step 3 After naming, selecting the event type, and entering the selection criteria, click OK.
The event is listed in the (calendar-side) events table, with your assigned name.
Step 4 Click an event to select it.
Step 5 In the right-side time picker area, add one or more triggers, as needed.
Note the following:
• By default, a “midnight” trigger may exist (00h:00m); you can delete it if needed.
• Using the Range option, you can add multiple triggers at some repeating interval.
• Triggers apply to all trigger events (calendar-side entries).
For more details see “Adding trigger event times” on page 10-19.
Step 6 Continue to add, edit, rename, or delete trigger events as needed. See “Right-click menus and other
controls” on page 10-20.
Step 7 When trigger events and triggers are like you want, click Save.

Linking schedules
As needed, you link weekly schedules and (if used) trigger schedules to other components to provide
scheduling control. For an overview, see “Schedule component links” on page 10-2.
• Linking weekly schedules
• Linking trigger schedules
Linking weekly schedules
You can link the output (Out slot) of a weekly schedule to any component with a like “Status<Type>”
input. For example, you might link the output of a BooleanSchedule to a BooleanWritable point.
• To link a weekly schedule using the wire sheet
• To link a weekly schedule using the Nav tree

To link a weekly schedule using the wire sheet

To link a weekly schedule to a component in the same wire sheet, do the following:
Step 1 In the wire sheet, mouse over the weekly schedule’s “Out” slot until highlighted.
Step 2 Click and drag the link wire from the weekly schedule to the bottom of the target component, and release
the mouse button.
A Link dialog appears. The source (left) side shows the schedule’s Out slot preselected.
Step 3 In the target (right) side of the Link dialog, click on the desired slot of the target component.
Note: By convention, if linking to a priority array input of a writable point, “In16” is used for schedule level control.
However, you can select any available level desired.
Step 4 With both source and target sides selected in the Link dialog, click OK.
The target point or component is now linked to the weekly schedule.

NiagaraAX-3.x
10-24
User Guide
Chapter 10 – About Scheduling Using schedules
May 1, 2007 Linking schedules

To link a weekly schedule using the Nav tree

Often, a weekly schedule is in a different container than the target component. In this case, the easiest
way to link is using the Nav tree.
To link a weekly schedule to a component using the Nav tree:
Step 1 Expand the Nav tree to locate the source weekly schedule, noting its name.
Step 2 Right-click the weekly schedule.
From the popup menu select Link Mark.
Step 3 Expand the Nav tree to locate the target component.
Step 4 Right-click the target component.
From the popup menu select Link From “<weekly schedule name>”.
A Link dialog appears.
Step 5 In the source (left) side of the Link dialog, click the schedule’s “Out” slot.
Step 6 In the target (right) side of the Link dialog, click the desired slot of the target component.
Note: By convention, if linking to a priority array input of a writable point, “In16” is used for schedule level control.
However, you can select any available level desired.
Step 7 With both source and target sides selected in the Link dialog, click OK.
The target point or component is now linked to the weekly schedule.
Linking trigger schedules
You can link the output (Trigger slot) of a TriggerSchedule to an action (or topic) of any component
(point or extension) with such a slot. For example, you might link a trigger schedule to the
“ResetChangeOfStateCount” action of a DiscreteTotalizerExt child of BooleanPoint.
Note: Often, you link trigger schedules to point extensions, not directly to a parent container point or component.
In this case, before linking you could first composite the target container component, selecting to expose the
extension’s action up in the parent point. Although optional, this can help reusability and link clarity. For
details, see “About composites” on page 3-26.
Note: Target actions or topics, unlike target property slots, can accept multiple link sources. In some cases, you
may wish to link the “Trigger Missed” slot of the trigger schedule to the same target. For details, see “Trigger
Missed slot” on page 10-21.
You can use either of these methods to link trigger schedules:
• To link a trigger schedule using the wire sheet
• To link a trigger schedule using the Nav tree

To link a trigger schedule using the wire sheet

To link a trigger schedule to a component in the same wire sheet, do the following:
Step 1 In the wire sheet, mouse over the trigger schedule’s “Trigger” slot until highlighted.
Step 2 Click and drag the link wire from the trigger schedule to the bottom of the target component, and release
the mouse button.
A Link dialog appears. The source (left) side has the trigger schedule’s Trigger slot preselected
Step 3 In the target (right) side of the Link dialog, click on the desired slot of the target component.
Step 4 With both source and target sides selected in the Link dialog, click OK.
The target component (point or extension) is now linked to the trigger schedule.

To link a trigger schedule using the Nav tree

Often, a trigger schedule is in a different container than the target component. In this case, the easiest
way to link is using the Nav tree.
To link a trigger schedule to a component using the Nav tree:
Step 1 Expand the Nav tree to locate the source trigger schedule, noting its name.
Step 2 Right-click the trigger schedule.
From the popup menu select Link Mark.
Step 3 Expand the Nav tree to locate the target component.
(In some cases, the target may be an extension of a point or other component.)
Step 4 Right-click the target component.
From the popup menu select Link From “<target schedule name>”.

NiagaraAX-3.x
10-25
User Guide
Using schedules Chapter 10 – About Scheduling
Importing schedules May 1, 2007

A Link dialog appears.

Step 5 In the source (left) side of the Link dialog, click the trigger schedule’s “Trigger” slot.
Step 6 In the target (right) side of the Link dialog, click the desired action of the target component.
Step 7 With both source and target sides selected in the Link dialog, click OK.
The target component (point or extension) is now linked to the trigger schedule.

Importing schedules
If the station is part of a multi-station NiagaraAX network, you can import NiagaraAX schedule compo-
nents between stations. You do this using the NiagaraAX Driver architecture, specifically, views of the
Schedules extension under a NiagaraStation (device-level) component.
If the Bacnet driver is used, you can also import BACnet Schedules and Calendars (as NiagaraAX
schedule components) from a BACnet device. The same basic architecture and methods are used.
Note: Under a BacnetNetwork, you can also export NiagaraAX schedules to a specific BACnet device (to
configure existing BACnet Schedules and Calendar objects).
For a brief overview, see “Schedule exports and imports (master/slave)” on page 10-3. For more complete
details, see “About the Schedules extension” on page 4-27, and “Station Schedules import/export notes”
on page 4-60.
Importing NiagaraAX schedules or Bacnet Schedules
Often, you import a NiagaraAX schedule when working in a JACE station, where the source (master)
schedule resides in a remote Supervisor station. BACnet Schedules and Calendars are also typically
imported into a JACE station (unless a BACnet Supervisor).

To import a NiagaraAX schedule or BACnet Schedule or Calendar

To import a NiagaraAX schedule or BACnet Schedule or Calendar, do the following:
Step 1 In the Nav tree, expand the Drivers folder of the station to receive the imported schedule.
Step 2 Expand the network, either NiagaraNetwork or BacnetNetwork.
Step 3 Expand the device that contains the source schedule (NiagaraStation or BacnetDevice).
In the Nav tree, the device’s children include: Points, Histories, Alarms, and Schedules.
Step 4 Double-click Schedules.
The Niagara or Bacnet Schedule Import Manager displays.
Any existing schedules (already imported) from this device are listed.
Step 5 Click Discover.
The manager view splits into two panes and a schedule discovery job is started. When complete,
schedules available for import appear in the top pane.
Step 6 In the top pane, click to select one or more schedules, then click Add.
An Add dialog allows you to edit the name of the schedule (as it appears in this station) and several other
properties. See “Schedule Import properties” on page 4-46 for details.
Step 7 After editing name and properties to suit, click OK.
NiagaraAX schedule components are created for the selected items, reside under that device’s Schedules
extension. You can link into station logic like any other schedules, but cannot configure these imported
schedules (add, delete, or change events or other properties).

NiagaraAX-3.x
10-26
User Guide
 CHAPTER 11
About Workbench tools
This section describes some of the standard “tools” available in Workbench. These tools provide
Workbench interfaces that are designed to facilitate specific tasks – from managing credentials to
monitoring alarms. All of the tools described in this section are available from the Tools menu.
However, as shown in Figure 11-1, navigational links to some of the tools also appear in the nav side bar
and in the nav container views.
Note: The nav side bar and nav container views do not display the tool icons until you initially open them using
the Tools menu.

Figure 11-1 Workbench tools

Nav Tree Tools Menu

NU
Some, but not all of the tools that are available under the Tools menu appear in the nav side bar when
you select them. When you first open Workbench, the “My Tools” node will not be present in the nav
tree. Therefore, if you configure a tool, such as the BACnet service tool, all the configuration data will be
lost when you close the current session of Workbench. Tools, such as the Alarm Portal, BACnet service,
Lonworks service, and the Workbench Job Service are available in Workbench when you do not have a
station open. This is provided as a convenience and may only be useful in a limited number of situations.
For example, you would probably more typically use the Job Service, BACnet service, and Lonworks
Service under the “Services” node of a specific station.
Refer to “Types of Workbench Tools” for a list of the tools that are available from the Tools menu.

Types of Workbench Tools

The following tools are available in Workbench:
• Alarm portal
Explains the options that appear in the alarm portal. Refer to “Alarm portal” on page 11-2.
• Bacnet service
Explains the options that appear in the Bacnet service. Refer to “Bacnet service” on page 11-4.
• Color chooser
Explains the options that appear in the color chooser. Refer to “Color chooser” on page 11-4.
• Lexicon editor
Explains the options that appear in the lexicon editor. For more details, see “Lexicon editor” on page
11-5. For information about the lexicon installer, refer to “Lexicon Installer” on page 1-20 of the Nia-

NiagaraAX-3.x
11–1
User Guide
Alarm portal Chapter 11 – About Workbench tools
May 1, 2007

garaAX Platform Guide.

• Lonworks service
Explains the options that appear in the lonworks service manager. Refer to “Lonworks service” on
page 11-6.
• Manage Credentials
Explains the options that appear in the credentials manager. Refer to “Credentials manager” on page
11-7.
• New driver wizard
Explains the options that appear in the new driver wizard. Refer to “New driver wizard” on page 11-
8.
• New module wizard
Explains how to modify the attributes of a new module. Refer to “New module wizard” on page 11-8.
• New station wizard
Explains the options in the new station wizard how to change the default attributes of a new station.
Refer to “New station wizard” on page 11-9.
• License request dialog box
Explains the options that appear in the license request dialog box. Refer to “License request dialog
box” on page 11-9.
• Resource estimator
Explains the options that appear in the resource estimator dialog box. Refer to “Resource estimator”
on page 11-10.
• Todo list
Explains the options that appear in the todo list dialog box. Refer to “Todo list” on page 11-10.
• Workbench job service
Explains the options that appear in the workbench job service view. Refer to “Workbench job ser-
vice” on page 11-11.
• Workbench service manager
Explains the options that appear in the service manager screen. Refer to “Workbench service man-
ager” on page 11-11.

Alarm portal
The alarm portal tool allows you to view and acknowledge alarms from many different stations using a
single viewer (portal). The alarm portal, shown in Figure 11-2, is divided into two resizable panes, and a
set of buttons along the bottom of the alarm portal window:
From the Alarm Portal, double click on any alarm listed in the alarm sources pane to see the alarm details
dialog box and the alarm record dialog box, as described in “About the alarm console” on page 7-19.

Figure 11-2 Alarm portal

Alarm
Console
Monitor

Open
Alarm
Sources

• Alarm Console Monitor

This pane displays information about the consoles that are being monitored and contains the follow-
ing information areas:
• Title bar

NiagaraAX-3.x
11-2
User Guide
Chapter 11 – About Workbench tools Alarm portal
May 1, 2007

Displays “Alarm Console Monitor” title on the left and the number of consoles that are con-
nected to the alarm portal on the right side of the title bar.
• Column headings
Displays the title of each of the columns that are displayed in the alarm console monitor.
• Alarm console list
Each row in the alarm console listing contains information about alarm consoles that are cur-
rently listed as available to monitor from the alarm console. Station identity information is dis-
played, as well connection status (connected or disconnected) and connect and disconnect
times.
• Open Alarm Sources
This pane displays information about individual alarm sources, as described below. If you double
click on a single alarm source, the Open Alarm Sources view opens. This view is described in “About
the alarm console” on page 7-19.
• Title bar
Displays “Open Alarm Sources” title on the left and the total number of points that are dis-
played in the list on the right side of the title bar.
• Column headings (click column heads to sort)
Displays the title of each of the columns in the open alarm sources list, as follows:
• Timestamp
displays the latest time that the point generated an alarm.
– Source State
displays the current state of the point (for example, Normal or Offnormal).
– Ack State
displays how many alarms have been generated at the point and how many of those alarms
have been acknowledged.
– Ack Required
displays “true” or “false” indicating that an acknowledgement is or is not required for that
alarm.
– Source
displays the path to the point that is generating the alarm.
• Alarm portal buttons
• Acknowledge All
Acknowledges all alarms at the selected source when an alarm is selected in the alarm source
pane.
• Hyperlink
is active when an alarm extension property (refer to “About alarm extension properties” on page
7-3) is set to allow hyperlinking. When clicked, displays the alarm source.
• Notes
displays a dialog box that allows you to add notes to an alarm record (see “About the console
recipient” on page 7-19 for more details about alarm record notes).
• Silence
when clicked, this button quiets the alarm sound for the selected point.
• Filter
displays the alarm filter dialog box for limiting the alarms that are displayed. See “About the
alarm console” on page 7-19 for more details about the alarm filter dialog box.
• Stop/Start/AutoStart
provides starting and stopping options for the alarm portal.
The alarm portal tool, when enabled, also places the alarm icon in your system tray and an alarm popup
window, as shown in Figure 11-3.
You can set options for the alarm portal in the Tools Options menu, as described in “Alarm portal
options” on page 2-22

Figure 11-3 Alarm portal popup window

NiagaraAX-3.x
11-3
User Guide
Bacnet service Chapter 11 – About Workbench tools
May 1, 2007

Bacnet service
Figure 11-4 shows an example of the Bacnet service property sheet. Select Tools > BACnet
Service from the Workbench main menu to add this service to the “My Tools” node of the nav tree.
The default view is the property sheet view.

Figure 11-4 Bacnet service property sheet view

Note: You can use this Workbench Tools service to configure a local Bacnet device in the same way as a you would
under a station, as described in the Bacnet Guide. However, any configuration that you do using the
Workbench Bacnet Service (under the “My Tools” node) will be lost when you close Workbench. Use Bacnet
Service under a station to save your Bacnet Service settings to a database.
Refer to the Bacnet Guide for a detailed description of the Bacnet service.

Color chooser
Figure 11-5 shows an example of the color chooser dialog box. This tool allows you define and save
custom colors or use the default colors provided. You can add custom colors to your custom color palette
located in the lower left area of the color chooser tool. Your custom color settings will then be available
in other tools, such as the Px Editor.

Figure 11-5 Color chooser tool

Color Chooser Color Range Current

Default
Palette

Add and
Manage
Palette
Color
Buttons
Definition
Custom Fields
Palette

Palette
Manager

• Default Palette
This palette contains predefined color swatches to choose from.
• Color Chooser area
This area provides more colors to choose from and is regulated by the Color Range setting.
• Color Range
Use this area to select the range of colors to display in the color chooser area.
• Current Selected Color
This area displays the color that is currently selected. It changes whenever you specify a different col-
or using any of the palettes or definition fields.
• Color Definition Fields
Use these fields to define specific colors, by percentages by hexadecimal, or by name. The “alpha”
field specifies the alpha channel, or transparency level. For example, 50% in this field specifies that
the color is 50% transparent.
• Add Button
Click this button to add the selected color to the custom palette.

NiagaraAX-3.x
11-4
User Guide
Chapter 11 – About Workbench tools Lexicon editor
May 1, 2007 Lexicon Report

• Manage Button
Click this button to open the Manage Palette.
• Manage Palette
Open this palette by clicking the Manage Palette button. Use this palette to add, delete, or rearrange
the colors on the custom palette.

Lexicon editor
For general information on lexicons, see “About lexicons” on page 1-19. For details on installing (edited)
lexicons in remote JACE platforms, see the Platform Guide section “Lexicon Installer”.
For information about using the lexicon editor tool refer to the following sections:
• Lexicon Report
• Lexicon Editor
• Lexicon display options

Lexicon Report
When selecting the lexicon editor from the Tools menu, the default view is the “Lexicon Report,” as
shown in Figure 11-6. The left side of this view lists all lexicons installed on your PC. As needed, you click
a lexicon to select it.

Figure 11-6 Lexicon report

Selecting a lexicon in report view shows various status parameters about each lexicon file (by module) in
columns on the right side. These status parameters include the following:
• module
The Niagara module translated by the lexicon file (moduleName.lexicon)
• module last modified
Timestamp of when the module lexicon was last modified
• missing
Number of keys that are missing values (from the lexicon for that module)
• lexicon last modified
Timestamp of when the lexicon was last modified
Note: Checkboxes at the top of report view allow you to “hide” values that could affect “missing” status counts, as
described in “Lexicon display options”.
From this view you can also add (new) lexicons or delete unwanted lexicons. In addition, you can launch
the Lexicon Editor by clicking any module row, which shows that lexicon file.

Lexicon Editor
The lexicon editor lets you view and edit the contents of an individual lexicon file installed on your
Workbench PC. Typically, you access the editor from the Lexicon Report view with a lexicon selected, by
double-clicking a selected row on the right side.

NiagaraAX-3.x
11-5
User Guide
Lonworks service Chapter 11 – About Workbench tools
Lexicon display options May 1, 2007

Figure 11-7 Lexicon editor

A lexicon in the lexicon editor shows a table listing all defined keys for that module, with columns for
mapping to a localized value, as follows:
• Key
Niagara interface entity, constant in that module from lexicon to lexicon
• Default
Default character value, used if no value is defined for that key (English equivalent).
• Value
Localized character value
Note: Checkboxes at the top of report view allow you to “hide” values that could affect “missing” status counts, as
described in “Lexicon display options”.
As needed, you can resort columns to find information needed, and simply click any row to select that
key. At the bottom of the editor, a Value edit field allows modifying (or adding) a value to the currently
selected key.

Lexicon display options

Both lexicon views (Lexicon Report and Lexicon Editor) use a type of tabular presentation with the
standard table features and options, as described in “Table controls and options” on page 2-17. Lexicon-
specific controls and options are displayed at the top of both the Lexicon Editor Report. These controls
and options are shown in Figure 11-8 and described below:

Figure 11-8 Lexicon display options

• Hide Ords
If enabled, it filters out and referenced based entries, such as modules://icons/x16/alarm.png
• Hide Accelerators
If enabled, it filters out entries that define keyboard accelerators.
• Hide Colors
If enabled, it filters entries that define colors, such as those defined by hexadecimal code #FFFF0000.
• Hide Fonts
If enabled, it filters entries that define fonts.
Note: The default settings for these display options are set in the Options dialog box, as described in “Lexicon
editor options” on page 2-23.

Lonworks service
The Lonworks service is available when you select it from the Tools menu. The default view is the Lon
device manager view, as shown in Figure 11-9.

NiagaraAX-3.x
11-6
User Guide
Chapter 11 – About Workbench tools Credentials manager
May 1, 2007 Lexicon display options

Figure 11-9 Lonworks service, Lon device manager view

Note: You can use this Workbench Tools service to configure a Lonworks in the same way as a you would under
a station, as described in the Lonworks Guide. However, any configuration that you do using the
Workbench Lonworks Service (under the “My Tools” node) will be lost when you close Workbench. Use
Lonworks Service under a station to save your Lonworks Service settings to a database.
Refer to the Lonworks Guide for more details.

Credentials manager
The Manage Credentials tool, or “Credentials Manager” provides a dialog to access and open any
previously “remembered” (cached) connection from your Workbench, including both platform and
station connections.

Figure 11-10 Manage Credentials dialog (credentials manager)

.
You can also remove or reset any cached credentials. Note that your credentials cache is populated
whenever you have the login (Authentication) dialog option “Remember these credentials”
(checkbox) enabled, as shown in Figure 11-10. For any initial platform or station connection, this option
is enabled by default.

NiagaraAX-3.x
11-7
User Guide
New driver wizard Chapter 11 – About Workbench tools
Lexicon display options May 1, 2007

Figure 11-11 Authentication defaults (Remember credentials)

The default caching of credentials is a convenience feature, such that you can simply open the platform
or station later by entering only the IP address, or simply clicking on that host’s ghosted platform or
station in the Nav tree of Workbench, or going to the credentials manager. Then, the login authentication
dialog (Figure 11-11) has the cached credentials already entered, and you simply click OK.
If you want tighter security for any platform or station connection from your Workbench PC, you should
clear this checkbox whenever opening (logging on) a platform or station. Furthermore, you should
remove any related entries using the credentials manager (Figure 11-10). This way, that platform or
station connection always requires full entry of both user name and password.

New driver wizard

The new driver wizard is available when you select Tools > New Driver from the main menu. The
first of four wizard dialog boxes is in Figure 11-12.

Figure 11-12 New driver wizard

New module wizard

The new module wizard is available when you select it from the Tools > New Module from the main
menu. The wizard presents a series of dialog boxes, as shown in Figure 11-13, that help you create and
save a new module.

NiagaraAX-3.x
11-8
User Guide
Chapter 11 – About Workbench tools New station wizard
May 1, 2007 Lexicon display options

Figure 11-13 New module wizard creates folders under working directory

This wizard creates a set of folders and files under a station directory that you assign during the wizard
process. After creating these files, you need to finish the process, as described in “Working with modules”
on page 12-26. Also see the Developer Guide for more detailed information about building modules.

New station wizard

The new station wizard is available when you select Tools > New Station from the main menu. The
wizard presents two dialog boxes, as shown in Figure 11-14, that help you create and save a new station.

Figure 11-14 New station wizard

New Station Wizard fields include the following:

• Station Name
This name is the name that is assigned to your station. The station folder will have this name.
• Station Directory
This read-only field specifies the location where the station folder is created (under the “Stations”
folder).
• Admin Password
This field allows you to assign an administrative level password for the station. You must type in the
password again in the Confirm Password field.
• Fox Port
This field allows you to assign a port for Fox communications. The default port is port 1911.
• HTTP Port
This field allows you to assign a port for HTTP communications. The default port is port 80.

License request dialog box

Use the license request tool by selecting it from the Tools menu. The submittal dialog box, is shown in
Figure 11-15.

NiagaraAX-3.x
11-9
User Guide
Resource estimator Chapter 11 – About Workbench tools
Lexicon display options May 1, 2007

Figure 11-15 License request dialog box

The license request fields include the following:

• Host ID
This is the unique ID of the host platform for your station.
• Name
This is the name of the person responsible or authorized to obtain a license for the station.
• Admin Password
This field allows you to assign an administrative level password for the station. You must type in the
password again in the Confirm Password field.
• Company
This is the name of the company that is authorized to license the station.
• Email
This field specifies the email address of the person requesting the license. This is the address that a
license is emailed to.
• PO # (REQUIRED)
This field contains the purchase order number that is used to pay for the licensed version of
NiagaraAX.
When all fields are complete, click the OK button and the license request is submitted.

Resource estimator
The resource estimator tool is available from the Tools menu. Use it as a worksheet to help you estimate
the total number of station resources that you will use in a projected station implementation. The
resource estimator view is as shown in Figure 11-16.

Figure 11-16 Resource estimator view

Todo list
The todo list is available when you select it from the Tools menu. This tool is provided to help you with
organizing, prioritizing and tracking tasks in Workbench. The todo list view is shown in Figure 11-17.

NiagaraAX-3.x
11-10
User Guide
Chapter 11 – About Workbench tools Workbench job service
May 1, 2007 Lexicon display options

Figure 11-17 Todo list view

The Todo list is a tabular view with standard table controls and options, as described in “Table controls
and options” on page 2-17. You can use this tabular list to create new lists or edit, group and rearrange
existing lists and items in your lists. In addition, you can use the filter fields at the top of the display to
filter what you see in the table, based on your summary description or group.

Workbench job service

The Workbench job service view, shown in Figure 11-18, is available when you select it from the Tools
menu. This job service tool keeps track of all Workbench jobs - that is jobs that are not initiated under a
specific station, but initiated by the Workbench environment.

Figure 11-18 Job service nav tree and property sheet view

Note: Workbench jobs are jobs that are initiated and run under the Workbench - not under a station. Jobs that
are run under a station are monitored and displayed in the Station Job Service (under the station Services
node in the nav side bar).

Workbench service manager

The service manager view is available when you select it from the Tools menu. The service manager
view, shown in Figure 11-19, is used to manage the life cycle and configuration of all services.

Figure 11-19 Workbench service manager view

The Workbench service manager is a tabular view with standard table controls and options, as described
in “Table controls and options” on page 2-17. From this view you can enable or stop any of the services
that are listed.

NiagaraAX-3.x
11-11
User Guide
Workbench service manager Chapter 11 – About Workbench tools
Lexicon display options May 1, 2007

NiagaraAX-3.x
11-12
User Guide
 CHAPTER 12
Performing Workbench tasks
Workbench provides a complete user interface to the Niagara Framework. It can directly access a station
and perform any action that the system supports. You can view and control any component using any of
the supported views.
Common Workbench tasks include the following:
• Starting and exiting Workbench
• Getting started with stations
• Using the side bar pane
• Using bookmarks
• Using the help side bar
• Using the nav side bar (tree)
• Using the palette side bar
• Using the view pane
• Editing components
• Using alarms
• Using the Px Editor
• Using the Nav File Editor
• Working with modules

Starting and exiting Workbench

Tasks involved with starting and exiting Workbench, include the following:
• To start Workbench
• To close a Workbench window
• To exit Workbench

To start Workbench
To start Workbench do one of the following:
• From the Windows Start menu, choose Programs > Niagara 3.0.xx > Workbench.
The Workbench GUI will appear.
• From a console command line, type wb.
Note: If you use a DOS command line, instead of the Niagara command line, you must type the full
path to the workbench directory.
The Workbench GUI will appear. For more information about the console, see “About the console”
on page 2-11.

To close a Workbench window

Note: Closing all Workbench windows will exit the Workbench GUI.
To close a Workbench window do one of the following:
• From the File menu, select the Close command.
The Workbench window will close.
• From the Niagara Workbench menu (located in the top left corner of the window title bar), se-
lect the Close command.
The Workbench window will close.
• Click the close icon (located in the top right corner of the window title bar).
The Workbench window will close.

NiagaraAX-3.x
12–1
User Guide
Getting started with stations Chapter 12 – Performing Workbench tasks
May 1, 2007

To exit Workbench
You can exit Workbench by using the Exit command (which will close all Workbench windows) or by
closing all Workbench windows.
To exit Workbench, do one of the following:
• From the File menu, select the Exit command.
The Workbench GUI will close.
• Close all Workbench windows.
The Workbench GUI will close when the final Workbench window is closed.

Getting started with stations

In order to communicate with a station, the station must be running and accessible. The following proce-
dures provide information about basic tasks that are required to start, stop, and communicate with
stations:
• To open a platform using Workbench GUI
• To connect to a platform using Workbench GUI
• To close a platform using Workbench
• To disconnect from a platform using Workbench
• To start a station using Workbench
• To stop a station using Workbench
• To open a station
• To close a station using Workbench
• To connect to a station using Workbench
• To disconnect from a station

To open a platform using Workbench GUI

To open a platform, do the following:
Step 1 From the menu bar, select File > Open > Open Platform.
The Open Platform dialog box appears.
Step 2 Complete the fields in the Open Platform dialog box as follows:
• Host
Select the IP or dialup option and type in the address of the computer that is running the platform
that you wish to access.
• Port
Select the IP or dialup option and type in the address of the computer that is running the platform
that you wish to access.
• Password
Select the IP or dialup option and type in the address of the computer that is running the platform
that you wish to access.
• Remember these credentials
Select the IP or dialup option and type in the address of the computer that is running the platform
that you wish to access.
Step 3 Click the OK button to accept all settings.
The platform opens with the Nav Container View displaying in the view pane.

To connect to a platform using Workbench GUI

Note: You cannot connect to a platform unless it is “open”. An open platform may be visible in your Workbench
nav side bar, but appear dimmed. If there is no platform icon in the nav side bar, you need to open the
platform before connecting (see “To open a platform using Workbench GUI” on page 12-2).
To connect to a platform, do the following:
Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
platform icon and select the Connect command from the popup menu.
The Authentication dialog box appears.
Step 2 Enter the credentials information as follows:
Note: Be sure to use the correct platform username and password – not the credentials information for the
station.
• Username

NiagaraAX-3.x
12-2
User Guide
Chapter 12 – Performing Workbench tasks Getting started with stations
May 1, 2007

Enter the username for the platform.

• Password
Enter the password for the platform.
• Remember these credentials option
Select the “Remember these credentials” option if you want to have Workbench remember the plat-
form username and password for this platform.
Step 3 Click OK to accept all settings.
If the platform credentials were correct, the platform is connected, the platform icon appears in the side
bar pane and the default Nav Container View appears in the view pane. If the platform credentials were
not correct, you are prompted to enter them again.

To close a platform using Workbench

To close a platform, do the following:
Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
platform icon and select the Close command from the popup menu.
The Close dialog box appears.
Step 2 In the Close dialog box, click OK to close the platform.
The platform is closed and the platform icon is removed from the nav side bar.

To disconnect from a platform using Workbench

To disconnect from a platform, do the following:
Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
platform icon and select the Disconnect command from the popup menu.
The Disconnect dialog box appears.
Step 2 In the Disconnect dialog box, click OK to disconnect.
The platform is disconnected and the platform icon is dimmed.

To start a station using Workbench

Note: Most station–platform functions can be performed from the Station Director view of a platform, however,
you must connect to the platform where a station is hosted before you can perform these tasks.
To start a station using Workbench, do the following:
Step 1 Connect to the station’s platform (see “To connect to a platform using Workbench GUI” on page 12-2 for
details, if necessary).
Step 2 In the nav side bar, expand the platform node in the nav tree by clicking on the plus sign (+) next to the
platform icon in the tree.
The contents of the platform node displays in the tree.
Step 3 In the nav side bar, double click on the station director icon.
The station director view appears in the view pane.
Step 4 In the station director view, select the desired station.
The desired station is highlighted in the table region of the view pane.
Step 5 In the station director view, select the following options, as desired:
• Select the Auto-Start option if you want the station to automatically start any time the station
host computer is re–booted. Clear the Auto-Start option to disable auto–start.
• Select the Restart on Failure option if you want the station to automatically attempt a restart
any time it fails. Clear the Restart option to disable automatic restart.
Step 6 In the station director view, do one of the following:
• Select the desired station in the station table and click Start.
• Right click the desired station in the station table and select Start from the popup menu.
The station starts.

To stop a station using Workbench

Note: Most station–platform functions can be performed from the Station Director view of a platform, however,
you must connect to the platform where a station is hosted before you can perform these tasks.
To stop a station using Workbench, do the following:

NiagaraAX-3.x
12-3
User Guide
Getting started with stations Chapter 12 – Performing Workbench tasks
May 1, 2007

Step 1 Connect to the station’s platform (see “To connect to a platform using Workbench GUI” on page 12-2 for
details, if necessary).
Step 2 In the nav side bar, expand the platform node in the nav tree by clicking on the plus sign (+) next to the
platform icon in the tree.
The contents of the platform node displays in the tree.
Step 3 In the nav side bar, double click on the station director icon.
The station director view appears in the view pane.
Step 4 In the station director view, select the desired station.
The desired station is highlighted in the table region of the view pane.
Step 5 In the station director view, do one of the following:
• With the desired station selected station table, click Stop.
• Right click the desired station and select Stop from the popup menu.
The station stops.

To open a station
To open a station, do the following:
Step 1 From the File menu, select Open > Open Station (Fox)
The Open Station dialog box appears.
Step 2 Enter the host and credentials information as follows:
Note: Be sure to use the correct station username and password – not the credentials information for the
platform.
• Host [connection type]
Select the IP option if you are using an IP connection to connect to the station.
Select the dialup option if you are using a dialup connection to connect to the station.
• Host [ID]
Enter the Host ID (if necessary) or select it from the dropdown menu, if available.
• Port
Enter (or change, if necessary) the Port port number that you will use to connect.
• Username
Enter the username for the station.
• Password
Enter the password for the station.
• Remember these credentials option.
Select the “Remember these credentials” option if you want to have Workbench remember the sta-
tion username and password.
Step 3 Click OK to accept all settings.
If the station credentials were correct, then the station connects, the station icon appears in the side bar
pane and the Nav Container View (or Station Summary View) appears in the view pane. If the station
credentials were not correct, you are prompted to enter them again.

To close a station using Workbench

To close a station, do the following:
Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
station icon and select the Close command from the popup menu.
The Close dialog box appears.
Step 2 In the Close dialog box, click OK to close the station.
The station is closed and the station icon is removed from the nav side bar.

To connect to a station using Workbench

To connect to a station, do the following:
Note: You cannot connect to a station unless it is “open”. An open station may be visible in your Workbench nav
side bar, but it appears dimmed. If there is no station icon in the nav side bar, you need to open the station
before connecting (see “To open a station” on page 12-4).
To connect to a station, do the following:

NiagaraAX-3.x
12-4
User Guide
Chapter 12 – Performing Workbench tasks Using the side bar pane
May 1, 2007

Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
station icon and select the Connect command from the popup menu.
The Authentication dialog box appears.
Step 2 Enter the credentials information as follows:
Note: Be sure to use the correct station username and password – not the credentials information for the
platform.
• Username
Enter the username for the station.
• Password
Enter the password for the station.
• Remember these credentials option
Select the “Remember these credentials” option if you want to have Workbench remember the sta-
tion username and password for this station.

To disconnect from a station

To disconnect from a station, do the following:
Step 1 In the nav side bar (refer to “Using the nav side bar (tree)” on page 12-8, if necessary) right–click on the
station icon and select the Disconnect command from the popup menu.
The Disconnect dialog box appears.
Step 2 In the Disconnect dialog box, click OK to disconnect.
The station is disconnected and the station icon is dimmed.

Using the side bar pane

The side bar pane displays all open side bars. The pane may be shown or hidden by selecting a command
from the Windows menu, as described in “To open the side bar pane” on page 12-5.
Following, are some facts about the behavior of side bars and the side bar pane:
• If you open a side bar, the side bar pane (if currently closed) will automatically open to display that
pane.
• When you open Workbench, the side bar pane returns to its last previous state (displayed or hidden).
• When you show the side bar after all side bar panes have been closed (causing the side bar pane to
hide) the side bar pane will be empty
• When you close all side bars, the side bar pane will close
• When you open Workbench, it will display the side bars that were open (if any) when the last session
was closed.
• When more than one side bar is open in the side bar pane, side bars may be resized vertically, max-
imized, or restored to their previous size using the title bar controls.
• Side bars always expand to fill the side bar pane horizontally.

To open the side bar pane

To open the side bar pane, do the following:
• From the menu bar, select Window > Side Bars > Show Side Bar command.
The side bar will appear.

To open the bookmarks side bar

To open the bookmarks side bar, do the following:
• From the menu bar, select Window > Side Bars > Bookmarks.
The bookmarks side bar appears in the side bar pane.

To open the help side bar

To open the help side bar, do the following:
• From the menu bar, select Window > Side Bars > Help.
The help side bar appears in the side bar pane.

NiagaraAX-3.x
12-5
User Guide
Using bookmarks Chapter 12 – Performing Workbench tasks
May 1, 2007

To open the nav side bar

To open the nav side bar, do the following:
• From the menu bar, select Window > Side Bars > Nav.
The nav side bar appears in the side bar pane.

To open the palette side bar

To open the palette side bar, do the following:
• From the menu bar, select Window > Side Bars > Palette.
The palette side bar appears in the side bar pane.

To close a side bar

To close the side bar pane, do the following:
• From the side bar title bar dropdown menu (left side), select the Close command.
The side bar pane closes.

To close the side bar pane

The side bar pane toggles on or off by selecting or deselecting the Show Side Bar command, as
described below. The side bar pane also closes when all palettes are closed.
To close the side bar pane, do the following:
• From the menu bar, select Window > Side Bars > Show Side Bar.
The side bar pane closes.

To vertically resize a side bar

To vertically resize a side bar, do the following:
• Click on the title bar and drag vertically.
The side bar will adjust to any size that fits in the side bar pane.

To restore a side bar to a previous size

To restore a side bar to it’s previous size, do the following:
• Click on the restore icon on the title bar.
The side bar will change to its previous state.

To maximize a side bar:

To maximize a side bar, do the following:
• Click on the restore icon on the title bar.
The side bar will expand to its maximum size in the side bar pane.

Using bookmarks
Bookmarks are simply linked “shortcuts” or “favorites” to help you quickly find views in just a couple of
clicks. The bookmark side bar provides a convenient place in the side bar pane to add, manage, edit, and
remove bookmarks. You can also do these “bookmarking” tasks using the Bookmarks menu on the
menu bar. For an overview of the bookmark side bar, see “About the bookmark side bar” on page 2-4.
This section describes the following tasks that are associated with the bookmark feature:
• To add a bookmark
• To manage bookmarks
• To edit a bookmark
• To remove a bookmark

To add a bookmark
To add a bookmark, do the following steps:
Step 1 Make sure that the view you want to bookmark is showing in the view pane, and then do one of the
following:
• From the menu bar, select Bookmarks: Add to Bookmarks.
• From the popup menu in the palette side bar, select Add to Bookmarks.

NiagaraAX-3.x
12-6
User Guide
Chapter 12 – Performing Workbench tasks Using the help side bar
May 1, 2007

Step 2 In the Add to Bookmarks dialog box, type a name for the bookmark, in the Name field.
Step 3 Optional: In the Add to Bookmarks dialog box, click the New Folder button to add a new folder,
if desired.
The New Folder dialog box appears. There you can name your new folder and click OK to save it.
Step 4 In the Add to Bookmarks dialog box, select the folder where you want to locate the bookmark and
click OK.
The bookmark is added.

To manage bookmarks
To manage your bookmarks, do the following steps:
Step 1 Do one of the following:
• From the menu bar, select Bookmarks: Manage Bookmarks.
• From the popup menu in the palette side bar, select Manage Bookmarks.
Step 2 In the Manage Bookmarks dialog box, click on one of the following buttons:
• New Folder buttons
To create new folders to organize your bookmarks
• New Bookmark button
To create new bookmarks
• Copy to button
To copy bookmarks to another location
• Move to button
To move bookmarks to another location
• Remove button
To delete the selected bookmark
• Edit button
To rename a selected bookmark
• Move Up or Move Down button
To move bookmarks up or down in the bookmark tree view

To edit a bookmark
To edit a bookmark, do the following steps:
Step 1 In the bookmarks side bar, right-click the bookmark that you want to change and select Edit from the
popup menu.
The bookmark Edit dialog box will appear.
Step 2 In the Edit dialog box, type the desired name for your bookmark in the Name field.
Step 3 In the Edit dialog box, type the ORD path or scroll Name field.

To remove a bookmark
To remove a bookmark, do the following:
• In the bookmarks side bar, right-click the bookmark that you want to change and select Remove
from the popup menu.
The bookmark is deleted from the bookmark list.

Using the help side bar

When you open the help side bar for the first time, the help side bar is empty except for the Load Help
button. The Load Help button will reappear any time any module's timestamp is changed or when a
new module is added or removed. When you click the Load Help button, Workbench searches through
all the available modules to create the help directory. The Help Sidebar provides a view of the available
Help.

To search for topics in the help side bar:

After you enter one or more words in the Find window, pressing the Search button creates a list of
documents that contain one or more occurrences of the words you have entered. The results show those
document's containing any of the words, not all of the words. The ranking order is based on how many
times any of the words appear in a given document.
To search for topics in the help side bar, do the following steps:

NiagaraAX-3.x
12-7
User Guide
Using the nav side bar (tree) Chapter 12 – Performing Workbench tasks
May 1, 2007

Step 1 In help side bar, click on the Search tab. The search display appears.
Step 2 In the Find field, type the word or phrase that you are looking for and click the Search button.
Topics that match your search word(s) will appear in side bar below the text field.
Step 3 Double-click on a topic to display the topic in the view pane.

Using the nav side bar (tree)

The nav side bar provides a hierarchical view of the system in a nav—tree presentation. Components that
appear in the tree may be acted on in various ways depending the component type:
The following sections describe how to use Nav side bar actions and the following procedures:
• To refresh a nav side bar tree node
• To refresh a nav side bar tree node
Nav side bar actions
• Expand
Click the plus sign next to an icon to expand a branch of the tree and show any child nodes.
• Collapse
Click the minus sign next to an icon to collapse a branch of the tree.
• Select
Click a node in the tree to select it.
• View
Double—click the minus sign next to an icon to collapse a branch of the tree and hide its child nodes.
• Use popup menu
Right—click the desired node to use the context—sensitive popup menu. Refer to “About the nav
side bar popup menu items,” page 9 for details about the nav side bar popup menu.
• Use file menu
With a node selected, choose a menu item from the File menu. Refer to “About the File menu” on
page A-2 for details about the file menu.

To refresh a nav side bar tree node

Refreshing a nav side bar tree node, updates the view to reflect any changes to the files of that node.
To refresh a nav side bar tree node, do the following steps:
Step 1 Click the node to select it.
Step 2 Do one of the following:
• From the File menu, select Refresh.
The tree node refreshes.
• From the popup menu, select Refresh Tree Node.
The tree node refreshes.

To Go Into a nav side bar tree node

The Go Into command allows you to re-root the nav tree at any arbitrary node. This will make that
node the new root of the tree and give you a new tree in the nav side bar window. You can get back to the
original tree by selecting it from the All the nodes you have "gone into" are persistently saved as a special
type of Bookmark. Use the pulldown to switch between them. This feature is quite handy when working
with multiple Stations or deep File systems and Databases.
To refresh a nav side bar tree node, do the following steps:
Step 1 Click the node to select it.
Step 2 Do one of the following:
• From the File menu, select Refresh.
The tree node refreshes.
• From the popup menu, select Refresh Tree Node.
The tree node refreshes.

Using the jobs side bar

The Jobs side bar provides a place to view and manage current jobs. Once a job has completed you are
notified via the async notification feature. You can also view job details using the ">>" button.
This section explains how to do the following:

NiagaraAX-3.x
12-8
User Guide
Chapter 12 – Performing Workbench tasks Using the palette side bar
May 1, 2007

• To view job details

• To cancel a job from the jobs side bar
• To dismiss a job

To view job details

To view job details from the jobs side bar, do the following:
• On the desired job, click the details (">>") button.
The job log details dialog box appears.

To cancel a job from the jobs side bar

To cancel a job from the jobs side bar, do the following:
• On the jobs side bar, click the cancel button.
The job is cancelled.

To dismiss a job
Once a job has been completed, you are notified via the async notification feature. You may then dismiss
the job from the jobs side bar, if desired.
To dismiss a job, do the following:
• From the Jobs side bar click the close button on the job that you want to dismiss.
The selected job is closed.

Using the palette side bar

The palette side bar provides a place to open, view, and access components in modules. For an overview
of the palette side bar, see “About the palette side bar” on page 2-7.
This section explains how to do the following:
• To open a palette
• To close a palette
• To create a palette
• To add a new component to a palette (PaletteFile.palette)
• To add a new component to a palette (module.palette)
• To copy a component to a palette

To open a palette
You can open one or more palettes in the palette side bar. Refer to “To open the palette side bar” on page
12-6 for details on how to open the palette side bar.
To open a new palette in the palette side bar, follow these steps:
Step 1 On the palette toolbar click the open palette button.
The Open Palette dialog box appears.
Step 2 In the Open Palette dialog box, select one or more palettes from the list, as desired.
Note: Hold down the Ctrl or Shift key to make multiple selections.
Step 3 Click OK.
The palette(s) opens in the palette side bar pane.

To close a palette
You can close any of the palettes that are open in the palette side bar. When you close all the palettes, the
palette side bar closes.
To close a palette, follow these steps:
Step 1 From the Drop-down palette selector, choose the palette that you want to close.
The selected palette displays in the side bar pane.
Step 2 Click the Close palette button.
The palette closes.

NiagaraAX-3.x
12-9
User Guide
Using the palette side bar Chapter 12 – Performing Workbench tasks
May 1, 2007

To create a palette
Palettes allow you to save copies of your work for future use. Palette files may reside under a station file
system or as part of a module. This procedure describes how to create a palette that resides in a station
file system. Refer to “Working with modules” on page 12-26 for information about creating a palette file
that is part of a module (jar file).
Note: For convenience and good organization, it is a good idea to create a “palette” folder on the file system to
hold all your custom palette files.
To create a palette, follow these steps:
Step 1 In the nav tree, right-click on (or under) the station file system node, in the desired location (see note,
above).
The popup menu appears.
Step 2 From the popup menu, select New > PaletteFile.palette.
The File Name dialog box appears with a default name.
Step 3 In the File Name dialog box, type the desired name for the new Palette file and click OK.
The File Name dialog box disappears and the new Palette file appears in the nav tree.
For more information about palette files, refer to “About the Nav file” on page 8-36. For information about
using the Nav File Editor, refer to “About the Nav File Editor” on page 8-38.

To add a new component to a palette (PaletteFile.palette)

You can add a new component to any of your own custom palettes, store the palette files on your file
system and view them in your palette side bar. The palette files must reside on the file system, not in the
station database. However, the components that you add to your palette file may reside in the station
database.
Note: For convenience and good organization, it is a good idea to create a “palette” folder on the file system to
hold all your custom palette files.
To add a new component to a palette using the wire sheet view, follow these steps:
Note: To add a new component using a view other than the wire sheet view, refer to the information in “Working
with components” on page 12-13.
Step 1 In the nav tree, double-click on the palette file that you want to open.
The default (Wire Sheet) view appears.
Step 2 Add a component to the wire sheet view using one of the following methods.
• Right click on the wire sheet view and select a new component from the New menu.
• Drag and drop a component from the nav side bar directly onto the wire sheet.
Step 3 Select File > SaveBog from the main menu.
The palette file is updated to contain the new component.
Note: If the updated palette is currently being viewed in the palette side bar, you must close and reopen the
palette after saving the station (SaveBog).

To add a new component to a palette (module.palette)

You can add new components to any of your palettes that have module.palette files associated with
them. A single module.palette file may be associated with each module that is stored in the modules
directory. You change a module.palette file by first making the desired changes to a module.palette file
that resides in a module “build” directory under your file system and then using the build process to
recreate the module that includes the changed palette file.
To add a new component to a palette (module.palette file), follow these steps:
Step 1 Double click on the desired module.palette file. It should be located in a module directory on your station
file system.
The default (Wire Sheet) view appears.
Step 2 Add a component to the wire sheet view using one of the following methods:
• Right click on the wire sheet view and select a new component from the New menu.
• Drag and drop a component or container from the nav side bar directly onto the wire sheet.
Step 3 Select File > SaveBog from the main menu.
Step 4 From the console command line (press F3 to open console window) navigate to the working directory and
type the build command followed by a space and then the name of the module folder. For example:

NiagaraAX-3.x
12-10
User Guide
Chapter 12 – Performing Workbench tasks Using the view pane
May 1, 2007 Selecting a component

C:\Niagara\Niagara-3.0.xx\workingDirectory> build moduleName

Press the Return key to initiate the build process. If the build is successful, the updated jar file is built
and overwrites the old jar file located in the modules folder. If the build is not successful, no jar file is built
and error messages are generated to help you troubleshoot the problem.
Step 5 Refer to “To create a new module” on page 12-26 for more detailed instructions about creating a module.

To copy a component to a palette

You can copy components to any of your own custom palettes, store the palette files on your file system
and view them in your palette side bar. The nav files must reside on the file system, not in the station
database. However, the components that you add to your palette file may reside in the station database.
The components that you add to your palette are copies and not connected to the original components
that you are copying.
Note: For convenience and good organization, it is a good idea to create a “palette” folder on the file system to
hold all your custom palette files.
To copy a component to a palette, using the Wire Sheet view, follow these steps:
Step 1 In the nav tree, double-click on the file palette file that you want to open.
The default (Wire Sheet) view appears.
Step 2 From the nav side bar, palette side bar, or other source, drag and drop the desire component to the wire
sheet.
The copied component is added to the palette file.
Step 3 Select File > SaveBog from the main menu.
The palette file is updated to contain the new component.
Note: If the updated palette is currently being viewed in the palette side bar, you must close and reopen the
palette in the palette side bar in order to see the new items.

Using the view pane

The view pane can display any component view that you choose (see “About views” on page 1-19 for an
introduction to views). Different views of components can provide different editing options. Most
component editing is done in the view pane, however, many editing functions also involve the nav tree
pane as well. The following sections describe some of the basic tools provided in Workbench for editing
components. These tools are context–sensitive and may be used in several – but not all – views and with
several – but not all – types of components.
For more details about viewing components, refer to “Viewing a component” on page 12-12

Editing components
Editing components in Workbench typically involves:
• Selecting a component
• Viewing a component
• Working with components
• Editing component data
The following sections describe these tasks.

Selecting a component
By selecting an item, you are defining the scope of your actions. In other words, the only components that
are directly affected by your edits are those that are “selected” during your edits. Of course, other compo-
nents may be influenced by the change in a component that communicates with it. It is also important to
remember the hierarchical nature of the component tree. If you delete or move a component that
contains other components, then you are deleting or moving all items that are contained in that container
component.
When items are selected, they appear in one of the following ways:
• In the nav tree view, the component text is changed to a white on purple highlight.
• In the wire sheet view, selected components have a red border with red handles.
• In the wire sheet view, selected links turn red.
For more information about views, refer to “About views” on page 1-19.

NiagaraAX-3.x
12-11
User Guide
Editing components Chapter 12 – Performing Workbench tasks
Viewing a component May 1, 2007

To select a component
To select a component, do one of the following:
• In the nav tree view or the wire sheet view, left–click the desired component.
The component is selected.
• In the nav tree view or the wire sheet view, right-click the desired component.
The component (or link) is selected.
• In the wire sheet view, drag around the desired component.
The component (or link) is selected.

To select multiple components in the nav tree

To select more than one component in the nav tree do the following:
Step 1 Select a single component or link, as described in “To select a component”.
Step 2 Hold down the Shift key or Ctrl key and select additional items.
Multiple components (or links) are selected.
Step 3 Optional: In the wire sheet view, drag around the group of elements that you want to select. Hold down
the Shift key or Ctrl key and select additional items to select or deselect them.
Multiple components (or links) are selected.

To select a multiple components in the wire sheet

To select more than one component in the wire sheet do the following:
Step 1 Select a single component or link, as described in “To select a component”.
Step 2 Hold down the Shift key or Ctrl key and select additional items.
Multiple components (or links) are selected.

Viewing a component
Each component that you select (in a view or in the nav tree) has a “default” view that appears in the view
pane. You can select a different view of the component using the view selector or the popup (right–click)
menu. The last view of an object becomes its default view during a Workbench session. If Workbench is
closed and restarted, default views are reset to the original default views.
For details on selecting component views, see “To select a component view” on page 12-12.
In addition to having different views, you can edit the way views display information. For details about
customizing a view, refer to the following procedures:
“To reorder components (in a component container)” on page 12-12
“To create a composite view” on page 12-13

To select a component view

To select a component view, do one of the following:
• Double-click on a component in the nav side bar.
This will display the default view of the component.
• Right–click a component and choose a view from the Views submenu.
• With a component selected, choose a view from the view selector menu

To reorder components (in a component container)

You can reorder the components that are contained in a “container” component using the property sheet
view, the nav tree view, or the wire sheet view.
To reorder components, do the following:
Step 1 Right–click the desired component.
The popup menu appears.
Step 2 From the popup menu, select Reorder.
The Reorder dialog box appears.
Step 3 In the Reorder dialog box, use the sort buttons, as follows:
• Move Up button
Select one or more items in the component list (use the Ctrl or Shift key to select multiples) and click
this button to move selected item(s) up (one position per click) in the list.

NiagaraAX-3.x
12-12
User Guide
Chapter 12 – Performing Workbench tasks Editing components
May 1, 2007 Working with components

• Move Down button

Select one or more items in the component list (use the Ctrl or Shift key to select multiples) and click
this button to move selected item(s) down (one position per click) in the list.
• Sort by Name button
Click this button to sort all items in the list in alphabetical order, by name. Each click toggles the sort
order between ascending and descending sort order.
• Sort by Type button
Click this button to sort all items in the list in order by component type. Each click toggles the sort
order between ascending and descending sort order.
• Reset button
Click this button to set the components in the list back to the order that they were in when the Re-
order dialog box was opened.
The components are sorted according to button selected.

To create a composite view

Composite views are available in the wire sheet view and in the property sheet view. Creating a composite
view of a component allows you to expose one or more child slots (that you designate) at the parent–view
level. For more information about composite views, refer to “About composites” on page 3-26.
To create a composite view, do the following:
Note: The component that you select in the following step must have a child component to be a legitimate parent
component. If no valid child component is available, then there cannot be a composite.
Step 1 In the wire sheet view or in the property sheet view, right–click on the desired parent object.
appears.
The popup menu appears.
Step 2 From the popup menu, select the Composite command.
The Composite Editor appears.
Step 3 In the Composite Editor, expand the tree to find and select the desired points to add to the parent
component. Select multiple points (if desired) by holding the Ctrl or Shift keys when selecting.
Step 4 With the desired point(s) selected, click the Add button to add one or more points to the right column of
the Composite Editor.
Step 5 Optional: Use the Composite Editor control buttons to do the following, if desired:
• Reverse
Reverse the chosen side (“in” or “out”) of a point that is being composited.
• Rename
Provide a custom name for the new slot created by composited point.
• Remove
Removes the composited item (slot) from right side of the Composite Editor.
• Move Up
Sort all selected points by moving them up in the Composite Editor (list (one position per click).
• Move Down
Sort all selected points by moving them down in the Composite Editor list (one position per click).
Step 6 Click the OK button.
The component composites are set.

Working with components

The following procedures describe basic tasks that are used when working with components:
• To add a new component (property sheet, nav side bar, or wire sheet view)
• To delete a component (property sheet, nav side bar, or wire sheet view)
• To rename a component (property sheet, nav side bar, or wire sheet view, slot sheet)
• To duplicate a component (property sheet, nav side bar, or wire sheet view)
• To paste a component (property sheet, nav side bar, or wire sheet view)
• To drag a component to the property sheet, nav side bar, or wire sheet (left–click method)
• To drag a component to the property sheet, nav side bar, or wire sheet (right–click method)

NiagaraAX-3.x
12-13
User Guide
Editing components Chapter 12 – Performing Workbench tasks
Working with components May 1, 2007

To add a new component (property sheet, nav side bar, or wire sheet view)
You can add (create) a new component to a container using the property sheet view, the nav tree view or
the wire sheet view. To add a slot refer to “To add a new slot” on page 12-18.
To add a new component, do the following:
Step 1 Right–click in the container where you want to place the new component. This can be a component in
the nav tree view, the wire sheet view or the property sheet view.
A popup menu appears.
Step 2 From the popup menu, choose the New command and select the desired type of component:
• Folder
• IconFolder
• TextBlock
• BooleanWritable
• NumericWritable
• EnumWritable
• StringWritable
The Name dialog box appears.
Step 3 Type the desired name for the new component in the text field and click the OK button.
The new component appears in the property sheet.

To delete a component (property sheet, nav side bar, or wire sheet view)
You can delete a component from a container, using the property sheet view, the nav tree view or the wire
sheet view. To delete a component using the slot sheet view, refer to To delete a slot refer to “To delete a
slot” on page 12-18.
To delete a component, do the following:
Note: If you delete a component that contains other components, all components in that container component
are deleted as well.
Step 1 Right–click the desired component.
A popup menu appears.
Step 2 From the popup menu, select the Delete command.
The component is deleted.

To rename a component (property sheet, nav side bar, or wire sheet view, slot sheet)
You can rename a component in the property sheet view, the nav tree view, the wire sheet view, or the
slot sheet view.
To rename a component, do of the following:
Step 1 In the desired view, right–click the component to rename.
The popup menu appears.
Step 2 From the popup menu, select the Rename command.
The Rename dialog box appears.
Step 3 In the Rename dialog box, type the desired name in the text field and click the OK button.
The component is renamed.

To duplicate a component (property sheet, nav side bar, or wire sheet view)
You can duplicate a component from the property sheet view, the nav tree view, or the wire sheet view.
To duplicate a component, do of the following:
Step 1 In the desired view, right–click the component to duplicate.
The popup menu appears.
Step 2 From the popup menu, select the Duplicate command.
The Name dialog box appears.
Step 3 In the Name dialog box, type the desired name in the text field (or use the default name) and click the OK
button.
The component is duplicated.

NiagaraAX-3.x
12-14
User Guide
Chapter 12 – Performing Workbench tasks Editing components
May 1, 2007 Editing component data

To paste a component (property sheet, nav side bar, or wire sheet view)
You can add a component to a container by pasting it to a container displayed the property sheet view,
the nav tree view, or the wire sheet view.
To add a component by pasting it, do the following:‘
Step 1 In the desired view, select the desired component and use the Copy (to duplicate) or Cut (to remove)
command to copy the component to the clipboard.
Copy and Cut commands are available on the popup (right–click) menu, the Edit menu, or from the
toolbar.
Step 2 Right–click in the container where you want to place the new component. This can be a component in
the nav tree view, the wire sheet view or the property sheet view.
The popup menu appears.
Step 3 From the popup menu, select the paste command.
The Name dialog box appears.
Step 4 Type the desired name for the new component in the text field and click the OK button.
The new component is added to the targeted container.

To drag a component to the property sheet, nav side bar, or wire sheet (left–click
method)
You can drag a component to the displayed property sheet view, the nav tree view, or the wire sheet view,
by using a right–click drag or by using a normal, left–click drag.
Note: A left–click drag always creates a copy of the original.
To drag a component using the left–click drag method, do the following:
Step 1 In the desired view, left–click the component to copy and drag it to the target container.
When you release the mouse button, the Name dialog box appears.
Step 2 Type the desired name for the new component in the text field and click the OK button.
The new component is added to the targeted container.

To drag a component to the property sheet, nav side bar, or wire sheet (right–click
method)
You can drag a component to the displayed property sheet by using a right–click drag or by using a
normal, left–click drag.
Note: A right–click drag always prompts you to choose a copy, move, or cancel command.
To drag a component to a property sheet by using the right–click drag method, do the following:
Step 1 In the desired view, right–click the component that you want to move (or copy) and drag it to the
property sheet.
When you release the right mouse button, a popup menu appears.
Step 2 From the popup menu, choose one of the following commands:
• Copy – this command makes a duplicate of the component to paste onto the property sheet.
The Name dialog box appears.
• Move – this command removes the original component and prepares to paste in onto the property
sheet.
The Name dialog box appears.
• Cancel – this command will stop the process, and the popup menu will disappear.
Step 3 Type the desired name for the new component in the text field and click the OK button.
The new component appears in the property sheet.

Editing component data

Many component editing functions in Workbench work the same, or similarly, in all component views.
However, some editing functions are restricted to particular component views. For information about the
standard edit commands (such as cut, copy, and paste, refer to “Types of edit commands” on page A-12.
The following sections describe some of the basic component editing procedures.
• Using the property sheet
• Using the wire sheet
• Using the slot sheet

NiagaraAX-3.x
12-15
User Guide
Editing components Chapter 12 – Performing Workbench tasks
Using the property sheet May 1, 2007

• Using the link sheet

Using the property sheet

The property sheet view is displayed in the view pane by selecting Property Sheet from the view
selector menu (see “About the view selector” on page 2-14) or by using one of the other methods
described in “About the view pane” on page 2-10.
For information about creating new components, deleting components, duplicating components, and so
on, refer to “Editing components” on page 12-11.

To add an extension to a component property sheet view:

For more information about extensions, refer to “Extension process overview” on page 3-9 or “About
point extensions” on page 3-9
Note: The following procedure may also be performed directly in the nav side bar tree (refer to “Using the nav side
bar (tree)” on page 12-8) for more information.
Step 1 Display the component property sheet view, as follows:
• In the nav pane tree, select the desired component.
• From the right–click popup menu (or from the view selector), select the component property sheet
view.
Step 2 Open the desired extensions palette from the palette side bar.
Step 3 Expand the extensions folder to find the extension that matches your data type and collection method.
Step 4 Drag and drop or copy and paste the extension onto the bottom of the properties sheet.
The extension is added. Refer to “Configure history extensions” on page 6-16

To add a component facet:

For more information about facets, refer to “About point facets” on page 3-7.
Step 1 In the property sheet view of a component, click the Edit Facet (>>) button.
The Edit Facets dialog box appears.
Step 2 In the Edit Facets dialog box, click the Add button.
The Add... dialog box appears.
Step 3 From the Key: options menu, select a parameter. Duplicates are not allowed.
Step 4 From the Type: options menu, select a parameter.
Step 5 Click the OK button.
The Add... dialog box closes and the Edit Facets dialog box displays the new information.
Step 6 From the Edit Facets dialog box, click the OK button.
The new facet is added.
Step 7 In the property sheet, click the Save button to your save changes.

To remove a component facet:

For more information about facets, refer to “About point facets” on page 3-7.
Step 1 In the property sheet view of a component, click the Edit Facet (>>) button.
The Edit Facets dialog box appears.
Step 2 In the Edit Facets dialog box, click the Remove button.
The Remove... dialog box appears.
Step 3 From the Remove... dialog box, choose a parameter(s) that you want to delete by selecting the
associated check box(es).
Step 4 Click the OK button.
The Edit Facets dialog box disappears and deleted parameter information does not appear.
Step 5 From the Edit Facets dialog box, click the OK.
The new facet is removed.
Step 6 In the property sheet, click the Save button to save changes.

Using the wire sheet

The following are common tasks associated with the wire sheet

NiagaraAX-3.x
12-16
User Guide
Chapter 12 – Performing Workbench tasks Editing components
May 1, 2007 Using the wire sheet

• To pin a slot
• To paste a component onto the wire sheet
• To drag a component to the wire sheet (left–click method)
• To drag a component to the wire sheet (left–click method)
• To drag a component to the wire sheet (right–click method)

To pin a slot
By default, some slots are visible in the wire sheet view of the slot. However, you can have any – or all slots
visible on the wire sheet by “pinning” open the slot(s).
To pin a slot:
Step 1 In the wire sheet view, right–click on the desired component.
The popup menu appears.
Step 2 From the popup menu, select the Pin Slots command.
The Pin Slots dialog box appears.
Step 3 In the Pin Slots dialog box, click to the left of all slots that you want to pin open.
A pin icon appears next to each icon you click.
Step 4 Click the OK button.
The slots are pinned and appear on the wire sheet with a knob next to the slot name.

To paste a component onto the wire sheet

You can add a component to the displayed property sheet by pasting it onto the property sheet or by
dragging it onto the property sheet.
To add a component to a property sheet by pasting it to the property sheet, do the following:
Step 1 Select the desired component and use the Copy (to duplicate) or Cut (to remove) command to copy the
component to the clipboard.
Copy and Cut commands are available on the popup (right–click) menu, the Edit menu, or from the
toolbar.
Step 2 Right–click on the property sheet.
The popup menu appears.
Step 3 From the popup menu, select the paste command.
The Name dialog box appears.
Step 4 Type the desired name for the new component in the text field and click the OK button.
The new component appears in the property sheet.

To drag a component to the wire sheet (left–click method)

You can drag a component to the displayed property sheet by using a right–click drag or by using a
normal, left–click drag.
To drag a component to a property sheet by using the left–click drag method, do the following:
Step 1 Select the desired component using a left–click and drag it to the property sheet.
When you release the mouse button, the Name dialog box appears.
Step 2 Type the desired name for the new component in the text field and click the OK button.
The new component appears in the property sheet.

To drag a component to the wire sheet (right–click method)

You can drag a component to the displayed property sheet by using a right–click drag or by using a
normal, left–click drag.
To drag a component to a property sheet by using the right–click drag method, do the following:
Step 1 Right–click the desired component and drag it to the property sheet.
When you release the right mouse button, a popup menu appears.
Step 2 From the popup menu, choose one of the following commands:
• Copy – this command makes a duplicate of the component to paste onto the property sheet.
The Name dialog box appears.
• Move – this command removes the original component and prepares to paste in onto the property

NiagaraAX-3.x
12-17
User Guide
Editing components Chapter 12 – Performing Workbench tasks
Using the slot sheet May 1, 2007

sheet.
The Name dialog box appears.
• Cancel – this command will stop the process, and the popup menu will disappear.
Step 3 Type the desired name for the new component in the text field and click the OK button.
The new component appears in the property sheet.

Using the slot sheet

The following are common tasks associated with the slot sheet
• To add a new slot
• To delete a slot

To add a new slot

To add a new slot, perform the following steps:
Step 1 In the slot sheet view, right–click in the pane.
The popup menu appears.
Step 2 From the popup menu, select the Add Slot command.
The Add Slot dialog box appears.
Step 3 In the Add Slot dialog box, enter the following information:
• Name: type in a name for the slot.
• Type: Select the component property type from the drop-down option lists.
• Choose the desired slot options from the Flags field.
Step 4 Click the OK button.
The slot is added to the slot sheet.

To delete a slot
To delete a slot, perform the following steps:
Step 1 In the slot sheet view, right–click on the slot that you want to delete.
The popup menu appears.
Step 2 From the popup menu, select the Delete command.
The slot is deleted.

Using the link sheet

The following are common tasks associated with the link sheet
• To delete a link using the link sheet view
• To edit a link using the link sheet view

To delete a link using the link sheet view

To delete a link using the link sheet view, perform the following steps:
Step 1 In the link sheet view, right–click on the link that you want to delete.
The popup menu appears.
Step 2 From the popup menu, select the Delete command.
The link is deleted.

To edit a link using the link sheet view

To edit a link using the link sheet view, perform the following steps:
Step 1 In the link sheet view, right–click on the link that you want to edit.
The popup menu appears.
Step 2 From the popup menu, select the Edit command.
The edit dialog box appears.
Step 3 In the edit dialog box, edit the following fields, as desired
• Source Ord
Type in (or browse to) the ORD for the desire source of the link.
• Source Slot Name
Type in a name for the Source.

NiagaraAX-3.x
12-18
User Guide
Chapter 12 – Performing Workbench tasks Using alarms
May 1, 2007 Creating alarms

• Target Slot Name

Type in a name for the Target Slot
• Enabled
Choose True of False from the Enable option list. True enables the link and False disables the
link.
Step 4 In the edit dialog box, click the OK button.
The edit dialog box disappears and the edits are saved.

Using alarms
The following are common tasks associated with setting up and working with alarms in NiagaraAX:
• Creating alarms
• Routing alarms
• Managing alarms

Creating alarms
To create an “alarmable” control point, you must add an appropriate alarm extension to a control point
and configure it to define your alarm condition requirements:

To set up alarm conditions for a control point

Note: Just as there are different types of control points (refer to “Types of control points” on page 3-2), there are
different types of control point extensions (refer to “Types of point extensions” on page 3-10). When adding
an alarm extension to a control point, you must add the proper type of extension to match the point, as
described in “Types of alarm extensions” on page 3-12.
To set up alarm conditions for a control point, do the following:
Step 1 Add an alarm extension to the control point property sheet as described in “To add an extension to a
component property sheet view:” on page 12-16. The alarm extension must match the control point type
(for example, BooleanChanegOfStateAlarmExt fits with a Boolean Writable point – and a
EnumChangeOfStateAlarmExt would not).
Step 2 Configure the alarm extension properties as desired. Refer to the “About alarm extension properties” on
page 7-3 for details about the alarm extensions properties.
Note: The Alarm Enable property options are not selected by default. You must select an AlarmEnable option
in addition to setting your alarm extension properties.

Routing alarms
The alarm service handles the routing of alarms by using alarm classes to coordinate the transfer of
messages between alarm sources and alarm recipients. Refer to “Types of alarm recipients” on page 7-18
for more information about alarm recipients.

To add an alarm class to the alarm service

For more information about alarm service, refer to “About the alarm service” on page 7-6. For more infor-
mation about alarm class, refer to “About alarm class” on page 7-15.
To add an alarm class to the alarm service, do the following:
Step 1 Right–click the AlarmService node in the nav side bar.
The popup menu appears.
Step 2 From the popup menu, select Views > WireSheet.
The alarm service Wire Sheet view appears.
Step 3 From the alarm palette, drag an AlarmClass component onto the wiresheet.
The Name dialog box appears.
Step 4 Type the desired name for the new alarm class in the text field and click the OK button.
The new alarm class appears in the wiresheet and is ready for configuration.

To add a console recipient to the alarm service

For more information about alarm service, refer to “About the alarm service” on page 7-6. For more infor-
mation about console recipient, refer to “About the console recipient” on page 7-19.
To add a console recipient to the alarm service, do the following:

NiagaraAX-3.x
12-19
User Guide
Using alarms Chapter 12 – Performing Workbench tasks
Managing alarms May 1, 2007

Step 1 Right–click the AlarmService node in the nav side bar.

The popup menu appears.
Step 2 From the popup menu, select Views > WireSheet.
The alarm service Wiresheet view appears.
Step 3 From the alarm palette, drag a ConsoleRecipient component onto the wiresheet.
The Name dialog box appears.
Step 4 Type the desired name for the new console recipient in the text field and click the OK button.
The new console recipient appears in the wiresheet and is ready for configuration.

To add a station recipient to the alarm service

For more information about alarm service, refer to “About the alarm service” on page 7-6. For more infor-
mation about station recipient, refer to “About the station recipient” on page 7-22.
To add a station recipient to the alarm service, do the following:
Step 1 Right–click the AlarmService node in the nav side bar.
The popup menu appears.
Step 2 From the popup menu, select Views > WireSheet.
The alarm service Wiresheet view appears.
Step 3 From the alarm palette, drag a StationRecipient component onto the wiresheet.
The Name dialog box appears.
Step 4 Type the desired name for the new station recipient in the text field and click the OK button.
The new station recipient appears in the wiresheet and is ready for configuration.

To add an email recipient to the alarm service

For more information about alarm service, refer to “About the alarm service” on page 7-6. For more infor-
mation about email recipient, refer to “About the email recipient” on page 7-23.
To add an email recipient to the alarm service, do the following:
Step 1 Right–click the AlarmService node in the nav side bar.
The popup menu appears.
Step 2 From the popup menu, select Views > WireSheet.
The alarm service Wiresheet view appears.
Step 3 From the email palette, drag an EmailRecipient component onto the wiresheet.
The Name dialog box appears.
Step 4 Type the desired name for the new email recipient in the text field and click the OK button.
The new email recipient appears in the wiresheet and is ready for configuration.

Managing alarms
To acknowledge alarms from the alarm console view
Note: Alarms are not removed from the alarm console until both the following conditions exist:
• alarm acknowledged
• alarm source is in a normal (not alarm) state
You can acknowledge alarms from the alarm portal as well as from the alarm console. To acknowledge
alarms from the alarm portal, refer to “To acknowledge alarms from the alarm portal” on page 12-21.
To acknowledge alarms from the alarm console view, do the following:
Step 1 Right–click on the ConsoleRecipient node in nav side bar pane.
The popup menu displays.
Step 2 From the popup menu, select Views > Alarm Console.
The alarm console view appears with all alarm sources displayed in a tabular view.
Step 3 In the alarm console view, select alarm sources that you want to acknowledge. Select multiple alarms, if
desired, using the Shift or Ctrl key.

NiagaraAX-3.x
12-20
User Guide
Chapter 12 – Performing Workbench tasks Using alarms
May 1, 2007 Managing alarms

Note: Each record that appears in the alarm console table represents one alarm source and one or more alarms
from that source. You may acknowledge either the latest (most recent) alarm or acknowledge all alarms
that are reported from that source by choosing either the “Acknowledge” command or the “Acknowledge
All” command, as described in the following step.
Step 4 Acknowledge selected alarm(s) by doing one of the following:
• From the Alarm menu, select Acknowledge (to acknowledge the latest alarm only)
The latest alarm from each selected choice is acknowledged.
OR
• From the Alarm menu, select Acknowledge All (to acknowledge all alarms reported from that
source). Alternatively, you may click the Acknowledge All button (located at the bottom of the
dialog box).
All alarms from each selected alarm source are acknowledged.

To acknowledge alarms from the alarm portal

The alarm portal must be running and configured to include all desired alarm consoles before it can be
used to acknowledge alarms. Refer to “Alarm portal” on page 11-2 for details about the alarm portal. Refer
to “Alarm portal options” on page 2-22 for details about alarm portal display options.
Note: Alarms are not removed from the alarm console (or portal) until both the following conditions exist:
• alarm acknowledged
• alarm source is in a normal (not alarm) state
You can acknowledge alarms from the alarm console as well as from the alarm portal. To acknowledge
alarms directly from the alarm console, refer to “To acknowledge alarms from the alarm console view”
on page 12-20.
To acknowledge alarms from the alarm portal, do the following:
Step 1 From the Tools menu, select Alarm Portal.
The Alarm Portal view displays in the view pane.
Step 2 If the desired Alarm Console does not appear in the Alarm Console Monitor table (top portion of the
Alarm Portal view) right–click in the Alarm Console Monitor area.
The popup menu, appears.
Step 3 Select Add Alarm Console.
The Add Alarm Console wizard appears.
Step 4 Complete the Add Alarm Console wizard by entering the following information:
• Host address information, as needed (IP or dialup)
• Credentials information (username and password)
• Choose the desired console, by Ord (if more than one is present at the host address)
Step 5 Click the Finish button to complete the Add Alarm Console wizard.
The alarm console appears in the Alarm Console Monitor table (top portion of the Alarm Portal
view). Any alarms will appear in the Open Alarm Sources table (bottom portion of the Alarm Portal
view).
Step 6 In the Open Alarm Sources table, select alarm sources that you want to acknowledge. Select multiple
alarms, if desired, using the Shift or Ctrl key.
Note: Each record that appears in the Open Alarm Sources table represents one alarm source and one or
more alarms from that source. You may acknowledge either the latest (most recent) alarm or acknowledge
all alarms that are reported from that source by choosing either the “Acknowledge” command or the
“Acknowledge All” command, as described in the following step.
Step 7 Acknowledge selected alarm(s) by doing one of the following:
• From the Alarm menu, select Acknowledge (to acknowledge the latest alarm only)
The latest alarm from each selected choice is acknowledged.
OR
• From the Alarm menu, select Acknowledge All (to acknowledge all alarms reported from that
source). Alternatively, you may click the Acknowledge All button (located at the bottom of the
dialog box) or use the popup menu to acknowledge the alarm(s).
All alarms from each selected alarm source are acknowledged.

NiagaraAX-3.x
12-21
User Guide
Using the Px Editor Chapter 12 – Performing Workbench tasks
Making widgets May 1, 2007

To delete alarm records

The Alarm Database Maintenance view provides three ways to delete alarm records from the alarm
database. To delete old alarm records, do the following:
Step 1 In the Alarm Database Maintenance view, select one of the following three options:
• Clear Old Records option
to clear alarm records before a certain date and time. The Before field is provided to allow you to
set the date and time for removing old records. The Before field is not available when you select ei-
ther of the other options.
• Clear All Before Selected Record option
to delete all records that have a timestamp earlier than the timestamp of the record that you select
in the Alarm History pane table. The selected record is not deleted.
• Clear All Records options
to delete all records that appear in the Alarm History pane table, regardless of the date.
Step 2 Click the Run Maintenance button to initiate the delete action.
The Confirm Clear dialog box displays to clarify that you are about to delete records and that the
operation cannot be “undone”.
Step 3 If the information in the Confirm Clear dialog box confirms that you are deleting the desired alarm
records, click the Yes button (otherwise click the No button).
The alarm records are deleted and removed from the Alarm History table in the Alarm History pane.

Using the Px Editor

The following are common tasks associated with setting up and working with the Px Editor in NiagaraAX:
• Making widgets
• Binding widgets
• Editing widget properties
• Animating widget properties

Making widgets
It is possible to make new widgets in several ways:

To make a new widget using the Make New Widget wizard:

Note: For more information about the Make Widget wizard, see the following:
• For a description of the Make Widget Wizard interface, refer to “About the Make Widget wizard” on
page 8-19.
• For examples of procedures using the Make Widget Wizard interface, with different types of bind-
ings, refer to “Make Widget wizard: examples” on page 8-21.
When you create a widget with the Make Widget Wizard, the wizard dialog box provides fields for
creating the widget bindings. To make a new widget using the Make New Widget wizard, do the
following:
Step 1 From the nav side bar, drag and drop a widget onto the Px Editor canvas.
The Make Widget Editor appears, with the ORD for the selected component displaying in the ORD area.
You can double-click the ORD to change it, if desired.
Step 2 From the Source options list, select the desired type of binding (choose from: Bound Label, Properties,
Actions, and others).
Note: Binding options that are dimmed indicate that they are not valid options for the selected component.
The Secondary view area displays fields and options that are related to the selected Source option.
Step 3 In the Secondary view area, choose a widget template, formatting options for display labels, or views,
as appropriate for your Source option.
Step 4 In the Properties sheet area, edit the properties or actions, as desired.
Step 5 Click the OK button to complete the wizard. The Make Widget wizard disappears and the new widget
appears on the Px Editor canvas.
Step 6 Toggle the view using the View/Edit Mode toolbar icon to display the widget in the Px Viewer.

Binding widgets
There are different ways to add a binding to a widget. You can add a binding to a widget using the Make
Widget wizard or you can add a binding to a widget that is already on the Px Editor canvas.

NiagaraAX-3.x
12-22
User Guide
Chapter 12 – Performing Workbench tasks Using the Px Editor
May 1, 2007 Editing widget properties

To bind a value to a widget

Step 1 In the Px Editor canvas, select the desired widget.
Step 2 In the Properties side bar, click the Add Binding toolbar icon.
The Add Binding dialog box appears.
Step 3 Select a binding type from the options list and click the OK button.
The binding type properties are added to the “binding” area at the bottom of the widget property sheet.
Step 4 Under the binding type properties, click the ORD property field.
The ORD dialog box appears.
Step 5 In the ORD dialog box, type or browse to the value that you want to bind to the widget and click the OK
button.
The ORD is added to the binding area of the widget property sheet.

Editing widget properties

To edit a widget property
To edit a widget, do the following:
Step 1 In the Px Editor canvas, select (or double-click) the desired widget.
The widget properties display in the properties side bar (or in properties dialog box, if you double-
clicked).
Step 2 In the Px Editor properties side bar (or dialog box) edit the widget properties, as desired:
• To edit a widget property: add, change, or remove a property value from the desired property field
in the properties side bar.
• To add a binding, click the Add Binding icon in the properties side bar (see “To bind a value to a wid-
get” on page 12-23).
• To animate a widget property, from the palette side bar, right-click in the properties field and select
Animate from the popup menu (refer to “Animating widget properties” for details).
• To delete a binding, click the Close icon (X) in the top right corner of the properties side bar.
Step 3 If you are working in the properties dialog box, click the OK button.
The edits are made and the widget properties are changed.

Animating widget properties

To animate a widget property
“Animating” a property means to link a widget property to a bound data component value, so that the
widget can display any change in value, as it happens. For more information about animating graphic
views, refer to “Animating Graphics” on page 8-10.
Note: Before you can animate a widget property, you must add a binding from the desired component to the
target widget. The binding must exist before the property can be animated. Refer to “Binding widgets” on
page 12-22 for details about adding a binding to a widget.
To animate a widget property, do the following:
Step 1 In the Px Editor canvas, select (or double-click) the desired widget that you want to animate.
The widget properties display in the properties side bar (or in properties dialog box, if you double-
clicked).
Step 2 In the Px Editor properties side bar (or dialog box) right-click on the properties field of the property that
you want to animate and select Animate from the popup menu.
The Animate dialog box appears. If you have more than one binding associated with the widget, all
bindings will be available in the Binding options list.
Step 3 From the Binding options list, select the binding that is associated with the component value you want
to link to.
Step 4 From the Converter Type options list, select the binding that is associated with the component value
you want to link to.
Note: The converter type that is selected by default is based on the component that you have selected and most of
the time will be the converter type that you want to use. For more information about converter types, refer
to “Types of Converters” on page 8-13.

NiagaraAX-3.x
12-23
User Guide
Using the Nav File Editor Chapter 12 – Performing Workbench tasks
Creating a new Nav file May 1, 2007

The Animate dialog box displays different fields, based on the type of value (and thus, converter) that
you animating.
Step 5 Complete the binding to the value using the controls in the Animate dialog box and click the OK button.
The Animate dialog box disappears and the binding appears in properties side bar (or dialog box).
Step 6 Click the OK button to close the properties dialog box, if necessary.
The property value is animated.

Using the Nav File Editor

The following tasks are commonly associated with setting up and working with the nav files in
NiagaraAX:
• Creating a new Nav file
• Editing a Nav file in the Nav File Editor

Creating a new Nav file

You may have more than one nav file associated with a station. The nav files must reside on the file
system, not in the station database.
Note: For convenience and good organization, it is a good idea to create a “nav” folder on the file system to hold
all your nav files.
For more information about nav files, refer to “About the Nav file” on page 8-36. For information about
using the Nav File Editor, refer to “About the Nav File Editor” on page 8-38.

To create a new nav file:

To create a new nav file, do the following:
Step 1 In the nav tree, right-click on (or under) the file system node.
The popup menu appears.
Step 2 From the popup menu, select New > NavFile.nav.
The File Name dialog box appears with a default name.
Step 3 In the File Name dialog box, type the desired name for the new Nav file and click OK.
The File Name dialog box disappears and the new Nav file appears in the nav tree.

To delete nav file (Delete Key):

To delete a nav file using the Delete key, do the following:
Step 1 In the nav tree, select the nav file that you want to delete.
Step 2 On the keyboard, press the Delete key.
The nav file is deleted.

To delete nav file (popup menu):

To delete a nav file using the popup menu, do the following:
Step 1 In the nav tree, right-click on the nav file that you want to delete.
The popup menu appears.
Step 2 From the popup menu, select Delete.
The nav file is deleted.

To rename a nav file:

To rename nav file, do the following:
Step 1 In the nav tree, right-click on (or under) the file system node.
The popup menu appears.
Step 2 From the popup menu, select Rename.
The Rename dialog box appears with the current name in the text field.
Step 3 In the Rename dialog box, type the desired name for the nav file in the text field and click OK.
The nav file is renamed.

NiagaraAX-3.x
12-24
User Guide
Chapter 12 – Performing Workbench tasks Using the Nav File Editor
May 1, 2007 Editing a Nav file in the Nav File Editor

Editing a Nav file in the Nav File Editor

You can edit nav files in the Text Editor or in the Nav File Editor. The following procedure describes how
to edit a Nav File in the Nav File Editor.
For more information about nav files, refer to “About the Nav file” on page 8-36. For information about
the Nav File Editor, refer to “About the Nav File Editor” on page 8-38.
The following procedures describe tasks involved with editing nav files:
• To open a nav file in the Nav File Editor:
• To add nodes to a nav file using the Nav File Editor:
• To delete nodes from a nav file:
• To edit the node hierarchy (tree structure) in a nav file:
• To edit nodes in a nav file:

To open a nav file in the Nav File Editor:

To open a nav file in the Nav File Editor, do one of the following:
Note: The nav file resides on the file system, not in the station database. You may keep all station nav files in a
“nav” folder to improve or simplify file organization on your station.
Step 1 In the nav side bar, find the nav file that you want to open, and do one of the following:
• Double-click on the desired nav file. OR
• Right-click on the Nav File and select View > Nav File Editor from the popup menu.
The Nav File Editor will open and display the file in the Result Tree pane.
Step 2 Edit the nav file, as desired.
Step 3 Click the Save icon on the toolbar or select File > Save to save changes to the nav file.

To add nodes to a nav file using the Nav File Editor:

There are several ways to add nodes to a nav file using the Nav File Editor.
To add nodes to a nav file do the following:
Step 1 Open the desired nav file in the Nav File Editor (refer to “To open a nav file in the Nav File Editor:”, if
necessary).
Step 2 Add a node to the Result Pane using any of the following methods:
• Copy and paste
Copy a component or Px file from the nav side bar and paste it into the Result Tree pane. The new
node appears in the Result Tree as a child node of the node that you target when pasting.
• Drag and drop (from nav side bar)
Drag a component or Px file from the nav side bar and drop it onto the Result Tree pane. A new node
appears in the Result Tree as a child node of the node that you target when dropping it.
• Popup menu
Right-click on the component that you want to add and select Copy from the popup menu. Right-
click the desired target area in the Result Tree, and select Paste from the popup menu. A new node
appears in the Result Tree as a child node of the node that you target when pasting.
• New button
Click the New button on the bottom of the Nav File Editor pane. The New Node dialog box appears.
Edit the Display Name, Target Ord, and Icon fields, as desired and click the OK button.
A new node appears in the Result Tree as a child node of the node that is selected.
• Drag and drop (from Source Tree)
Toggle the Show Components button and the Show Files button to display the desired objects
in the Source Tree pane. Drag the desired component or Px file from the Source Tree pane and drop
it onto the Result Tree pane at the desired location.
A new node appears in the Result Tree as a child node of the node that you target.
Step 3 Click the Save icon on the toolbar or select File > Save to save changes to the nav file.

To delete nodes from a nav file:

To delete nodes from a nav file, do the following:
Step 1 Open the desired nav file in the Nav File Editor (refer to “To open a nav file in the Nav File Editor:”, if
necessary).
Step 1 In the Result Tree, find the node that you want to delete, and then do one of the following:
• Select the node that you want to delete and click the Delete button. OR

NiagaraAX-3.x
12-25
User Guide
Working with modules Chapter 12 – Performing Workbench tasks
Editing a Nav file in the Nav File Editor May 1, 2007

• Select the node that you want to delete and press the Delete key on the keyboard. OR
• Right-click on the node that you want to delete and select Delete from the popup menu. OR
The node will disappear from the Result Tree pane.
Step 2 Save changes to the nav file by clicking the Save button on the toolbar or select Save from the File
menu.
The nav file changes are saved.
Step 3 Click the Save icon on the toolbar or select File > Save to save changes to the nav file.

To edit the node hierarchy (tree structure) in a nav file:

To edit the node hierarchy in a nav file, do the following:
Step 1 Open the desired nav file in the Nav File Editor (refer to “To open a nav file in the Nav File Editor:”, if
necessary).
Step 1 In the nav tree, find the nav file that you want to edit, and then do any of the following:
• Drag and drop the desired tree node from one location to another location in the tree.
• Select one or more tree nodes and use the Move Up or Move Down buttons to raised or lower the
node in its parent node.
Note: The Move Up and Move Down buttons will move nodes only within their parent node. To
move a node to a different parent, you must cut and paste the node.
The Nav File Editor displays the new node location in the Result Tree pane.
Step 2 Click the Save icon on the toolbar or select File > Save to save changes to the nav file.

To edit nodes in a nav file:

To edit a new nav file, do the following:
Step 1 Open the desired nav file in the Nav File Editor (refer to “To open a nav file in the Nav File Editor:”, if
necessary).
Step 2 In the nav tree, find the node that you want to edit, and then do one of the following:
• Double-click on the desired node. OR
• Select the desire node and click the Edit button.
• Right-click on the node File and select Edit from the popup menu.
The Edit dialog box will open and display the node properties.
Step 3 In the Edit dialog box, edit the node Display Name, Target Ord, and Icon properties, as desired and click
the OK button.
The node properties are changed.
Step 4 Click the Save icon on the toolbar or select File > Save to save changes to the nav file.

Working with modules

You can create and customize your own modules so that you have access to individual custom compo-
nents or complete folders of components and applications that you have designed and may use again. For
basic information about modules, see “About modules” on page 1-6.

To create a new module

You can create your own custom modules. This allows you to save copies of your work for future use in
the compressed (jar) module form. Palette and lexicon files may be customized and included as part of
the modules. Typically, if you choose to create a palette and a lexicon file, you select these options in the
New Module Wizard, which creates an empty “module.lexicon” and “module.palette” file that you edit,
as desired.
Note: For convenience, it is a good idea to create a “working” folder under the station directory (as described in
step 1, below) to hold all your custom files source material You can leave this folder in your station and use
it to hold source files for any modules that you create.
To create a new module using Workbench, follow these steps:
Step 1 Connect to the station that you want to work with and, in the nav side bar, expand the My File System
> Sys Home nodes. The station installation directory appears under this node.
Step 2 Right-click on the Sys Home node in the tree and select New > New Folder from the popup menu
to create a “working folder”. Give the folder a generic name, such as “ModuleSource” or
“workingModule”.

NiagaraAX-3.x
12-26
User Guide
Chapter 12 – Performing Workbench tasks Working with modules
May 1, 2007 Editing a Nav file in the Nav File Editor

Step 3 Use the New Module Wizard to create the directory and files required for a new module. Refer to
“New module wizard” on page 11-8 for more information about using the New Module Wizard. The
wizard creates a new folder under a directory that you specify (typically, you want to specify the “working
directory” that you create in step 1, above).
Step 4 In the nav side bar, create a new folder named “src” under the newly created module folder.
In the nav tree you should now have a folder structure similar to the following:
My File System/Sys Home/<workingDirectory>/<newModuleName>/src
Step 5 Add items to the src folder, as desired. Copy and paste components or files from your file system or from
the station database. You can add subfolders under the src folder to organize data, as desired, or you can
put everything directly into the src folder.
Step 6 In the <newModuleName> folder, double-click the “build.xml” file. It opens in Workbench text file
editor.
Step 7 In the “build.xml” file, after the last <dependency/> element, type in one or more <resources/>
elements to define the location of your source files.
For example, if you want to include all the “gif ” files that are in an “images” folder under your “src” folder,
you type the following line in the “build.xml” file:
<resources name=”/images/*.gif”/>
The following listing is an example of how your “build.xml” file might look.
<!-- Module Build File -->
<module
name = "newModuleName"
bajaVersion = "0"
preferredSymbol = "nM"
description = "My new graphic files"
vendor = "Acme"
>
<!-- Dependencies -->
<dependency name="baja" vendor="Tridium" vendorVersion="3.0" bajaVersion="0" />
<resources name="/images/*.*"/>
</module>
Step 8 Save and close the “build.xml” file.
Step 9 From the console command line in Workbench (press F3 to open console window) navigate to the
working directory and type the build command followed by a space and then the name of the module
folder. For example:
C:\Niagara\Niagara-3.0.xx\workingDirectory> build moduleName
Press the Return key to initiate the build process. If the build is successful, the new jar file is built and
located in the modules folder. If the build is not successful, no jar file is built and error messages are
generated to help you troubleshoot the problem.
Step 10 You must restart workbench to see the new module in the modules directory.
Note: If you chose to create a palette during the build process (using the New Module Wizard) an empty palette
is available with the new module. Refer to “To add a new component to a palette (module.palette)” on page
12-10 for instructions about adding components to the palette.

NiagaraAX-3.x
12-27
User Guide
Working with modules Chapter 12 – Performing Workbench tasks
Editing a Nav file in the Nav File Editor May 1, 2007

NiagaraAX-3.x
12-28
User Guide
 CHAPTER 13
Component Guides
These Component Guides provides summary information on common components.

Component Reference Summary

Note: For kitControl components, see “Alphabetical list of kitControl components” section in the KitControl
Guide.
Summary information is provided on components in the following modules:
• alarm
• backup
• baja
• bajaui
• chart
• control
• converters
• crypto
• devkit
• driver
• email
• file
• fox
• gx
• help
• history
• kitPx
• ldap
• net
• net
• niagaraDriver
• program
• pxeditor
• rdb
• rdbDb2
• rdbOracle
• rdbSqlServer
• report
• schedule
• serial
• timesync
• web
• workbench

Components in alarm module

• AlarmClass
• AlarmConsoleOptions
• AlarmPortalOptions
• AlarmService

NiagaraAX-3.x
13–1
User Guide
Components in alarm module Chapter 13 – Component Guides
May 1, 2007

• AlarmSourceExt
• AlarmSourceInfo
• BooleanChangeOfStateAlarmExt
• BooleanCommandFailureAlarmExt
• ConsoleRecipient
• FaultAlgorithm
• EnumChangeOfStateAlarmExt
• EnumCommandFailureAlarmExt
• LinePrinterRecipient
• MemoryAlarmService
• OffnormalAlgorithm
• OutOfRangeAlarmExt
• StationRecipient
• StatusAlarmExt
alarm-AlarmClass
An AlarmClass object is used to group Alarms that have the same routing and handling character-
istics. The AlarmClass is available in the Alarm Module.
• Refer to “About alarm class” on page 7-15 for more details about alarm class.
alarm-AlarmConsoleOptions
The AlarmConsoleOptions component allows you to configure the parameters of the alarm
console. The Options dialog box displays when you select the Workbench Tools > Options
menu item.
• Refer to “Alarm console options” on page 2-21 for details about the individual alarm console options.
• Refer to About the alarm console for details about the alarm console.
The component is stored under the “/users/{user}/options” directory.
alarm-AlarmPortalOptions
This component allows you to configure the alarm portal parameters. The Options dialog box
displays when you select the Workbench Tools > Options menu item.
• Refer to “Alarm portal options” on page 2-22 for details about the individual alarm console options.
• Refer to About the alarm console for details about the alarm console.
The component is stored under the “/users/{user}/options” directory.
alarm-AlarmService
The AlarmService uses AlarmClasses to route all Alarm messages between AlarmSources and
AlarmRecipients. Each Station contains a single AlarmService. The AlarmService is available in the
Alarm Module.
• Refer to “About the alarm service” on page 7-6 for more details.
alarm-AlarmSourceExt
AlarmSourceExt is the abstract superclass of all Baja control Alarming algorithms. The Alarm-
SourceExt is available in the alarm Module Extensions Directory. Some common alarm source exten-
sions include OutOfRangeAlarmExt, BooleanChangeOfStateAlarmExt,
BooleanCommandFailureAlarmExt, EnumChangeOfStateAlarmExt and EnumCommandFailure-
AlarmExt.
Refer to “About alarm extensions and components” on page 7-3 for more details.
AckAlarm Acknowledge the Alarm matching this ack request.
SilenceAlarm Silence the Alarm matching this silence request.
alarm-AlarmSourceInfo
AlarmSourceInfo is a container slot on any network component, and also on each child device
component. Properties under this slot are used to populate the alarm record when the network or
device does not respond to the network’s monitor ping. These properties work in the same fashion as
those in an alarm extension for any control point.
See the following links for more information:
• “About network Alarm Source Info” on page 4-6
• “About Monitor” on page 4-7 for details on the network monitor mechanism
• “About alarm extension properties” on page 7-3 for AlarmSourceInfo property descriptions

NiagaraAX-3.x
13-2
User Guide
Chapter 13 – Component Guides Components in alarm module
May 1, 2007

alarm-BooleanChangeOfStateAlarmExt
BooleanChangeOfStateAlarmExt implements a change of state alarm detection algorithm for
Boolean objects as described in BACnet Clause 13.3.2. This alarm extension is available in the Exten-
sions folder of the alarm palette.
See the following links for more information:
• “Types of alarm extensions” on page 3-12
• “About alarm extensions and components” on page 7-3
• “About alarm extension properties” on page 7-3
• “About alarm extension manager” on page 7-9
alarm-BooleanCommandFailureAlarmExt
BooleanCommandFailureAlgorithm implements command failure alarm detection algorithm for
Boolean objects as described in BACnet. If feedback and output values of the point are not equal for
timeDelay duration, an offnormal alarm is generated. This alarm extension is available in the Extensions
folder of the alarm palette.
See the following links for more information:
• “Types of alarm extensions” on page 3-12
• “About alarm extensions and components” on page 7-3
• “About alarm extension properties” on page 7-3
• “About alarm extension manager” on page 7-9
alarm-ConsoleRecipient
This component manages the transfer of alarms between the alarm history and the alarm console.
The ConsoleRecipient is available in the Alarm Module.
See the following links for more information:
• “About the console recipient” on page 7-19
• “Types of alarm recipients” on page 7-18
• “About the alarm service” on page 7-6
Scan Unacked Alarms Get all unacked Alarms that have been created (and unacked) since "alarm-
sSince".
Actions Actions include .
alarm-FaultAlgorithm
FaultAlgorithm is the super-class of all Fault detection mechanisms defined by Niagara. The default
implementation will never generate any toFault Alarms. The FaultAlgorithm is available in the
alarm Module Extensions Directory.
alarm-EnumChangeOfStateAlarmExt
EnumChangeOfStateAlarmExt implements a change of state alarm detection algorithm for Enum
objects as described in BACnet Clause 13.3.2. Each algorithm instance defines a set of enumerated
values that should be considered “offnormal” conditions and therefore generate an alarm. This alarm
extension is available in the Extensions folder of the alarm palette.
See the following links for more information:
• “Types of alarm extensions” on page 3-12
• “About alarm extensions and components” on page 7-3
• “About alarm extension properties” on page 7-3
• “About alarm extension manager” on page 7-9
alarm-EnumCommandFailureAlarmExt
EnumCommandFailureAlarmExt implements command failure alarm detection algorithm for
enum objects as described in BACnet. If feedback and output values of the enum point are not equal
for more than timeDelay, an offnormal alarm is generated. This alarm extension is available in the Exten-
sions folder of the alarm palette.
See the following links for more information:
• “Types of alarm extensions” on page 3-12
• “About alarm extensions and components” on page 7-3
• “About alarm extension properties” on page 7-3
• “About alarm extension manager” on page 7-9

NiagaraAX-3.x
13-3
User Guide
Components in backup module Chapter 13 – Component Guides
May 1, 2007

alarm-LinePrinterRecipient
The LinePrinterRecipient component provides the capability to print alarms to line printers that are
attached to a station that is running on a Win32 platform. This recipient can print to local and
remote line printers. Alerts may be generated if the printing of an alarm fails, but the lineprinter recipient
does not print alarms that it generates itself.
See the following links for more information:
• “About the lineprinter recipient” on page 7-23
• “Types of alarm recipients” on page 7-18
• “About the alarm service” on page 7-6
alarm-MemoryAlarmService
MemoryAlarmService provides an alternative to the standard file-based AlarmService. When you
use this service, alarms are not stored persistently on the station host as they are with the standard
file-based alarm service. The MemoryAlarmService is available in the Alarm Module.
• Refer to “About memory alarm service” on page 7-7 for more details.
alarm-OffnormalAlgorithm
BOffnormalAlgorithm is a super-class for all algorithms that check for off normal (not Fault) condi-
tions.
• Refer to “Types of control extensions” on page 3-11 for more information about “off normal”.
alarm-OutOfRangeAlarmExt
OutOfRangeAlarmExt implements a standard out-of-range alarming algorithm, and applies to
points with status numeric output. This alarm extension is available in the Extensions folder of the
alarm palette.
• Refer to “Types of control extensions” on page 3-11 for more information about “out of range”.
alarm-StationRecipient
Recipient for another station. This class receives Alarms and formats them for another station. The
StationRecipient is available in the Alarm Module.
See the following links for more information:
• “About the station recipient” on page 7-22
• “Types of alarm recipients” on page 7-18
• “About the alarm service” on page 7-6
alarm-StatusAlarmExt
StatusAlarmExt provides alarming based upon any combination of status flags, and applies to all
points/objects that accept extensions. This alarm extension is available in the Extensions folder of the
alarm palette.
• Refer to “Types of control extensions” on page 3-11 for more information about “off normal”.

Components in backup module

• BackupService
backup-BackupService
The BackupService provides for complete configuration backups to a Workbench PC or a browser
PC (user with Wb web profile). By default, the BackupService is included when you create a new
station using the New Station wizard. The target Niagara host (JACE, Supervisor) must have the
backup module installed.
A backup is a dist file (a zipped format) including minimally the station’s config.bog, current station
console output (.txt file), and backup.log file. If other station file types and subfolders are not excluded (in
the BackupService configuration), the backup dist file contains them too—for example, files of type: px,
nav, html, jpg, png, and so forth. Also, the backup dist contains the zipped “nre-config” for that host
(including license and certificates files), as well as pointers to the installed “nre-core,” OS, and JVM, each
by version. Essentially, a backup dist provides a “configuration snapshot” of the entire JACE platform in
zipped “dist” file format. This allows for a complete image restoration.
Note: Not included in a backup is runtime data that is actively managed by the station, such as the alarm and
history databases. This data should be “backed up” using standard alarm routing and history archiving to
a Supervisor host.

NiagaraAX-3.x
13-4
User Guide
Chapter 13 – Component Guides Components in baja module
May 1, 2007

To restore a backup dist from Workbench, you open a platform connection to the JACE, then use the
platform Distribution File Installer to install. Restoring from a backup may be necessary if the host
hardware was replaced.
The default view of a station’s BackupService is the BackupManager, which provides a Backup button to
manually initiate a backup. A backup automatically performs a local station save first, and is run as a
standard station Job. This means each backup provides a progress bar, and upon completion, a popup
notification. Under the station’s JobService, any backup appears as a “Fox Backup.”
BackupService configuration Configuration lets you define the file types and/or folders not included in
a station backup. The service’s property sheet provides the following properties for configuration:
• Enabled
Either true (default) or false. Currently, this setting makes no difference (manual backup still possi-
ble even if service has disabled status).
• Exclude Files
Specifies file types to exclude from the backup dist, either by name or extension (each delimited by
“;”). By default, the following files are excluded:
*.hdb;*.adb;*.lock;*backup*;console.*;config.bog.b*;config_backup*
• Exclude Directories
Specifies station subdirectories to exclude from the backup dist, using relative ORD syntax. An ORD
chooser control provides a Directory Chooser dialog in which you can select station subfolders. By
default, the following subfolders are excluded: file:^history, file:^alarm

Components in baja module

• Category
• CategoryService
• Component
• DataFile
• Directory
• FileSystem
• Folder
• Format
• IpHost
• Job
• JobService
• LocalHost
• Module
• ModuleSpace
• Permissions
• PermissionsMap
• PxView
• ServiceContainer
• Spy
• Station
• UnrestrictedFolder
• User
• UserService
• Vector
• VirtualComponent
• VirtualGateway
• WsTextBlock
• ZipFile
baja-Category
Each Category represents a custom logical grouping, and has a unique category index number. You
can assign components, files, and histories to one or more categories. All categorizable components
have a CategorySheet view, which shows you that component’s stored category memberships (Catego-
ryMask).
Categories reside under the station’s CategoryService, which has views CategoryBrowser and Category-
Manager. Categories play an integral role in station security, where you can give users permissions for
some (or all) categories. For a general review, see “Security model overview” on page 9-1.

NiagaraAX-3.x
13-5
User Guide
Components in baja module Chapter 13 – Component Guides
May 1, 2007

baja-CategoryService
The CategoryService is the station container for all Category(ies), which represent logical groupings
to which you can assign components, files, and histories. The default view of this service, the Catego-
ryBrowser, lets you centrally assign different objects to categories, using an expandable tree view of the
station.
The CategoryService also provides a CategoryManager view, for you to create, edit and delete categories.
Categories play an integral role in station security, where you can give users permissions for some (or all)
categories. By default, the CategoryService is included when you create a new station using the New
Station wizard. For more CategoryService details, see “CategoryService” on page 9-14.
baja-Component
Component is the required base class for all Baja component classes. The Component is available
in the baja Module.
Using Containers Containers allow you to logically group Components. The current container is the
Component that contains the Components in the display window. A container may be selected as the
current container by one of the following methods:
• Double-click the Component in the tree view.
• Right-click the Component in the tree view (which brings up the menu) and select a view.
• Right-clicking the Component in WireSheet (which brings up the menu) and select a view.
The Container Components include the following:
• Component can be used as a general container for Components. It allows you to place Compo-
nents and links in a container.
• Page is a special Component used to created a map of name/Ref pairs as dynamic slots.
baja-DataFile
DataFile represents a DataFile in the file system of a session.
baja-Directory
Directory is used to represent Directories in File space implementations.
baja-FileSystem
FileSystem is a FileSpace for the local machine's File system.
baja-Folder
Folder is a special Container designed to store objects. The Folder is available in the baja Module.
baja-Format
Format is used to format Objects into Strings using a standardized formatting pattern language. The
format String is normal text with embedded scripts denoted by the % percent character (use %% to insert
a real %). A script is one or more calls chained together using the . dot operator. Calls are mapped to
methods using reflections. Given call "foo", the order of reflection mapping is:
• special call (see below)
• getFoo(Context)
• getFoo()
• foo(Context)
• foo()
• get("foo")
The following special functions are available to use in a script:
• time() calls Clock.time() to get current time as an AbsTime
• lexicon(module:key) gets the specified lexicon text
Examples of formats:
• "hello world"
• "my name is %displayName%"
• "my parent's name is %parent.displayName%"
• "%value% {%status.flagsToString%} @ %status.priority%"
• "%time().toDateString%"
• "%lexicon(bajaui:dialog.error)%"
Format is available in the baja Module.
baja-IpHost
IpHost is used to represent a host machine that is identified with an IP address. The hostname of an
IpHost is either a a name resolvable via DNS or is a raw IP address.

NiagaraAX-3.x
13-6
User Guide
Chapter 13 – Component Guides Components in baja module
May 1, 2007

baja-Job
A Job is used to manage a task that runs asynchronously in the background, but requires user visibility.
Some example jobs include:
• StationSaveJob — From a station save, either initiated manually or from the auto-save function
(see “PlatformServiceContainer configuration parameters” on page 1-62).
• FoxBackupJob — From a station backup (zip) to a remote PC, see BackupService.
Many drivers also have various job types too. For example, the NiagaraDriver includes a StationDis-
coveryJob and NiagaraScheduleLearnJob.
Every job finishes displaying one of the following status descriptors:
• Success — Job completed successfully.
• Canceled — Job canceled by user.
• Failure — Job failed to complete.
• Completed — Job completed.
Also, if you have the station open in Workbench, you see a momentary “notification popup” in the lower-
right corner of your display.
You can monitor and cancel a job from within the particular view where you initiated it, or centrally from
the JobServiceManager view of a station’s JobService. You can also open a Jobs side bar to see all jobs in
all opened stations (see “Using the jobs side bar” on page 12-8).
Regardless of how you access jobs, note the following:
• To see details on a job, click the “>>” button next to its status descriptor. A popup Job Log dialog
displays all the interim steps about the job, including timestamps and relevant messages.
• To dispose of a job, click the close (“X”) button to remove it from the station.
Note: All jobs in a station are cleared upon a station restart.
baja-StationSaveJob
This component appears as a child of the job service and displays the following properties relative to the
save job:
• Job State
indicates which of the following states the save job is in currently: unknown, running, canceling, can-
celed, success, failed.
• Progress
indicates a percentage (0-100) of progress toward completing the job.
• Start Time
displays the time that the job started.
• Heart Beat Time
displays the time of the last indication that the job is alive.
• End Time
displays the time that the job ends
For related information, refer to:
• “baja-Job”.
• “baja-JobService”
Note: All jobs in a station are cleared upon a station restart.
baja-JobService
The JobService contains Jobs that were executed by different processes in the station. Each job
appears as a child component. By default, the JobService is included when you create a new station
using the New Station wizard. The default view of the JobService is the JobServiceManager.
Note: All jobs in a station are cleared upon a station restart.
baja-LocalHost
LocalHost represents the root of the Baja local Host namespace. The LocalHost is available in the
baja Module.
baja-Module
Module encapsulates a Baja software Module which is packaged and delivered as a JAR file with a
"meta-inf/module.xml" description. Modules are the unit of software deployment in the Baja archi-
tecture. Module names must be one to 25 ASCII characters in length and globally unique. Modules is
available in the ModuleSpace (called Modules under My Computer).

NiagaraAX-3.x
13-7
User Guide
Components in baja module Chapter 13 – Component Guides
May 1, 2007

baja-ModuleSpace
ModuleSpace is the Container for Modules which are keyed by their Module name. The
ModuleSpace is available as Modules under My Computer.
baja-Permissions
Permissions are a property used to define the permissions given to a user’s PermissionsMap.
baja-PermissionsMap
Defines the security permissions to grant to a user. Permissions are added as dynamic properties
with the name matching a Category and the value an instance of permissions. For more details, see
“Permissions and security” on page 9-4 and “About permission levels” on page 9-5. If a user has been
configured as a super user, then all permissions are automatically granted to all categories.
baja-PxView
PxView a dynamic view which may be added to Components as a property or by overriding
getAgents(). PxViews store the view contents in an XML file with a px extension. The view itself is
defined as a tree of bajaui:Widgets. The PxView is available in the baja Module.
baja-ServiceContainer
ServiceContainer provides a component to store services. The ServiceManager is its primary view.
The ServiceContainer is available in the baja Module.
baja-Spy
Spy is an Object wrapper for an instance of Spy.
baja-Station
Station is the component which represents a Station in the Baja framework. See Station in the
Developer Guide for more information. The Station is available in the baja Module.
Station Save Save the current state of the system to persistent storage. You should regularly backup
your station or stations using the Save Action on the station.
baja-UnrestrictedFolder
UnrestrictedFolder is a special container designed to store objects for use on a palette. Normal
isParentLegal() checks are not applied to UnrestrictedFolders. The UnrestrictedFolder is available in
the baja Module.
baja-User
User is the component that represents a station connection, typically a specific person who needs
to access the system. Users are children of the station’s UserService.
For more details, see the following sections:
• “Users and security” on page 9-2
• “User” on page 9-11 (all properties)
• “UserService security notes” on page 9-7
Also, see “Security model overview” on page 9-1.
baja-UserService
UserService is the service you use to add, edit, delete, and otherwise manage users of the station.
The UserManager is its primary view. Also available is a PermissionsBrowser view, in which you can
review and change permissions for any user’s assigned Category(ies). See “Users and security” on page 9-
2 and “UserService” on page 9-9 for more details. The UserService is available in the baja module. By
default, the UserService is included when you create a new station using the New Station wizard.
Note: To facilitate user management, the UserService component has a unique permissions scheme. See
“UserService security notes” on page 9-7 for details.
baja-Vector
Vector is a dynamic Struct which allows Properties to be added at runtime.
Vector is available in the baja Module.
baja-VirtualComponent
A VirtualComponent is the Baja base class for implementations of transient (non-persisted) compo-
nents that reside in the station’s “virtual component space,” as defined by a VirtualGateway. Initial
applications of virtual components are expected in various drivers for NiagaraAX. For a general expla-
nation about Baja virtual components, see the “Virtual Gateway component” on page 4-21.
Note: NiagaraAX 3.2 or higher is required for virtual components.

NiagaraAX-3.x
13-8
User Guide
Chapter 13 – Component Guides Components in bajaui module
May 1, 2007

baja-VirtualGateway
A VirtualGateway is the Baja base class for a component that resides under the station’s component
space (Config), and acts as a gateway to the station’s “virtual component space.” Note other object
spaces are Files and History. Initial applications of virtual gateways are expected in NiagaraAX
drivers. For a general explanation, see the “Virtual Gateway component” on page 4-21.
Note: NiagaraAX 3.2 or higher is required for virtual gateways and virtual components.
baja-WsTextBlock
WsTextBlock is a Niagara specific Component used to visualize text blocks on a WireSheet.
baja-ZipFile
ZipFile represents a ZipFile in the File system of a session.

Components in bajaui module

• BorderPane
• Bookmark
• BoundTable
• Button
• CanvasPane
• CheckBox
• ConstrainedPane
• EdgePane
• Ellipse
• ExpandablePane
• FlowPane
• GridPane
• Label
• Line
• RadioButton
• Rect
• Path
• Polygon
• ScrollPane
• Separator
• Slider
• SplitPane
• TabbedPane
• TextEditorOptions
• ToggleButton
• ValueBinding
bajaui-BorderPane
BorderPane provides a border content for a widget similar to the CSS Box Model. Margin defines
the space between the bounds and the border. Padding defines the space between the border and the
child bounds. Border defines the look and width of the border around each of the sides.
bajaui-Bookmark
Bookmark provides a bookmark.
bajaui-BoundTable
BoundTable is a Table implementation that is ready to use with TableBindings to populate its
model.
bajaui-Button
Button is a control button which fires an action when pushed.
bajaui-CanvasPane
CanvasPane is commonly used to provide absolute layout using Layout for most Widgets and Geom
for Shapes. CanvasPane also provides support for scaling and/or aligning its contents.
bajaui-CheckBox
CheckBox is a specialized ToggleButton which displays its label next to a box which can be checked
and unchecked.

NiagaraAX-3.x
13-9
User Guide
Components in bajaui module Chapter 13 – Component Guides
May 1, 2007

bajaui-ConstrainedPane
ConstrainedPane is a pane with a constrained size. It allows the pane to be restricted by minimum
width, maximum width, minimum height, and maximum height.
bajaui-EdgePane
EdgePane is a container with a layout like the java.awt.BorderLayout. It only supports five potential
children in the frozen slots top, bottom, left, right, and center. The top and bottom widgets fill the
pane horizontally use their preferred height. The left and right widgets use their preferred width, and
occupy the vertical space between the top and bottom. The center widget gets all the remainder space.
Any of the widgets may be a NullWidget.
bajaui-Ellipse
Ellipse renders a ellipse geometry.
bajaui-ExpandablePane
ExpandablePane contains two widgets. A summary widget is displayed all the time, with a button to
the right used to expand and collapse the pane. When expanded, the expansion widget is displayed
under the summary.
bajaui-FlowPane
FlowPane lays out its children from left to right and top to bottom fitting as many children as
possible in each row. It is based on the java.awt.FlowLayout.
bajaui-GridPane
GridPane provides flexible layout based on a grid with a predefined number of columns. Cells are
laid out left to right, flowing to the next row based on the columnCount property. Row height is
determined by the max preferred height of the widgets in the row. If uniformRowHeight is true then all
row heights are sized using the max row. Column width is determined by the max preferred width of the
widgets in the column. If uniformColumnWidth is true then all column widths are sized using the max
column. If rowLayout is set to fill then all widgets in a given row are sized to fill the row height. Otherwise
the widgets use their preferred height and are aligned accordingly. If columnLayout is set to fill then all
widgets in a given column are sized to fill the column width. Otherwise the widgets use their preferred
width and are aligned accordingly. The columnGap field specifies how many pixels to leave between
columns. The rowGap field specifies how many pixels to leave been rows. By default if the actual space of
the pane is bigger than the preferred size, then the horizontalPaneAlignment and verticalPaneAlignment
fields determine where to put the extra space. Or the stretchColumn and stretchRow properties may be
used to indicate that a specific column or row should be stretched to fill the additional space. Enabling
the stretch feature trumps pane alignment. If the colorRows field is true then alternating rows are shaded
to produce a stripped effect.
bajaui-HyperlinkLabel
The HyperlinkLabel has the same properties as the Label (see “bajaui-Label”), plus an ORD property
that allows you to assign an ORD to the label. When an ORD path is supplied for this property, the
HyperlinkLabel causes a mouse cursor to change to a standard link cursor and the component performs
a hyperlink when clicked.
bajaui-Label
Label is used to display text and/or an icon. Labels are always transparent, so their background is
defined by their parent. Their preferred size is always an exact fit to contain the text and/or icon.
Labels may be used by themselves to display information which cannot respond to user input, or they may
be embedded in widgets such as Buttons.
bajaui-Line
Line renders a line between two points.
bajaui-RadioButton
RadioButton is a specialized ToggleButton which displays its label next to a circle which can be
checked and unchecked. It is used with groups of other RadioButton's to provide an choice which is
exclusive of other options.
bajaui-Rect
Rect renders a rectangle shape.
bajaui-Path
Defines a general path to draw or fill, using a model and string format based on the SVG path
element.

NiagaraAX-3.x
13-10
User Guide
Chapter 13 – Component Guides Components in bajaui module
May 1, 2007

bajaui-Polygon
Models a closed area defined by a series of line segments, using string format “x,y,width,height”.
bajaui-ScrollPane
ScrollPane layouts one child using a viewport which may be scrolled to view the entire child's actual
size.
bajaui-Separator
Separator is used in ToolBars and Menus to provide a visible separator between groups of buttons.
bajaui-Slider
Slider provides a visual slider which is used to select and integer or floating point value between a
fixed range.
bajaui-SplitPane
SplitPane is a pane with a divider between two child widgets. The children can be laid out horizon-
tally or vertically.
bajaui-TabbedPane
TabbedPane is a container which displays a set of LabelPane children one at a time using a set of
"tabs" to select the currently displayed child. The LabelPane's label is used to label each tab, and the
content of the current selection fills the rest of the pane.
bajaui-TextEditorOptions
The TextEditorOptions stores the options used to configure text entry. The Status Colors options
allow you to view and change the following (default):
• Show Spaces (false)
• Show Tabs (false)
• Show Newlines (false)
• Tab To Space Conversion (2)
• Show Margin (0)
• Color Coding
• Foreground (00 00 00 black)
• Whitespace (c0 c0 c0 gray)
• Number Literal (80 00 80 purple)
• String Literal (80 00 80 purple)
• Identifier (00 00 00 black)
• Keyword (00 00 ff blue)
• Preprocessor (80 00 00 maroon)
• Bracket (ff 00 00 red)
• Line Comment (00 80 00 green)
• Multi Line Comment (00 80 00 green)
• Non Javadoc Comment (80 80 80 dark gray)
• Key Bindings (with default)
• Move Up Up
• Move Down Down
• Move Left Left
• Move Right Right
• Page Up PageUp
• Page Down PageDown
• Line Start Home
• Line End End
• Document Start Ctrl + Home
• Document End Ctrl + End
• Word Left Ctrl + Left
• Word Right Ctrl + Right
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Undo Ctrl + Z
• Redo Ctrl + Alt + Z
• Delete Delete
• Backspace Backspace
• Cut Line Ctrl + Y

NiagaraAX-3.x
13-11
User Guide
Components in chart module Chapter 13 – Component Guides
May 1, 2007

• Delete Word Ctrl + Delete

• Tab Forward Tab
• Tab Back Shift + Tab
• Toggle Slash Slash Esc
• Word Wrap Ctrl + W
• Goto Line Ctrl + G
• Find F5
• Find Next Ctrl + F
• Find Prev Ctrl + Shift + F
• Replace F6
• Reload Macros Ctrl + M
• Select All Ctrl + A
• Undo Navigation (true)
• Match Parens (true)
• Match Braces (true)
• Match Brackets (true)
These are stored under /user/{user}/textEditor.options.
bajaui-ToggleButton
ToggleButton provides a two-state widget which may be selected and unselected.
bajaui-ValueBinding
ValueBinding is used to bind to Values typically under a Component. Widget properties may be
overridden by creating dynamic slots of the same name with a Converter that maps the bound target
to the property value.

Components in chart module

• BarChart
• ChartCanvas
• ChartHeader
• ChartPane
• DefaultChartLegend
• LineChart
chart-BarChart
One of two chart types available (the other is LineChart).
chart-ChartCanvas
ChartCanvas is the canvas widget under a ChartPane.
chart-ChartHeader
ChartHeader is the header widget under a ChartPane.
chart-ChartPane
ChartPane is the container widget created when adding a Px chart.
chart-DefaultChartLegend
DefaultChartLegend is the legend widget under a ChartPane.
chart-LineChart
One of two chart types available (the other is BarChart).

Components in control module

• BooleanPoint
• BooleanWritable
• DiscreteTotalizerExt
• EnumPoint
• EnumWritable
• NullProxyExt
• NumericPoint
• NumericTotalizerExt
• NumericWritable
• StringPoint

NiagaraAX-3.x
13-12
User Guide
Chapter 13 – Component Guides Components in control module
May 1, 2007

• StringWritable
• TimeTrigger
control-BooleanPoint
BooleanPoint is a basic read-only control point, with default slots: Facets, Out, and ProxyExt. See
“About control points” on page 3-1 for details. The BooleanPoint is available in the Points folder of
the control palette.
control-BooleanWritable
BooleanWritable extends BooleanPoint to include 16 levels of command priority control. The
highest priority active command is reflected in the out property. Commands at the emergency and
manual levels (1 and 8) are stored persistently. See “About control points” on page 3-1, and “About
writable points” on page 3-24 for more details.
The BooleanWritable is available in the Points folder of the control palette.
control-DiscreteTotalizerExt
DiscreteTotalizerExt is a control point extension for accumulating runtime and change of state
counts on binary or enum values. Two actions are available to clear (zero) accumulated totals,
ResetChangeOfStateCount and ResetElapsedActiveTime.
The DiscreteTotalizerExt is available in the Extensions folder of the control palette.
control-EnumPoint
EnumPoint is a basic read-only control point, with default slots: Facets, Out, and ProxyExt. See
“About control points” on page 3-1 for details. The EnumPoint is available in the Points folder of the
control palette.
control-EnumWritable
WritableEnumPoint extends EnumPoint to include 16 levels of command priority control. The
highest priority active command is reflected in the out property. Commands at the emergency and
manual levels (1 and 8) are stored persistently. See “About control points” on page 3-1, and “About
writable points” on page 3-24 for more details.
The EnumWritable is available in the Points folder of the control palette.
control-NullProxyExt
NullProxyExt is the default implement AbstractProxyExt used to indicate that a point is not a Proxy.
The NullProxyExt is available in the control Module Extensions Directory.
control-NumericPoint
NumericPoint is a basic read-only control point, with default slots: Facets, Out, and ProxyExt. See
“About control points” on page 3-1 for details. The NumericPoint is available in the Points folder of
the control palette.
control-NumericTotalizerExt
NumericTotalizerExt is a control point extension used for integrating a numeric point value over
time. For example, a totalizer with a minutely totalization interval can convert an instantaneous flow
reading in cubic feet per minute (cfm) into a value representing total cubic feet consumed. An available
resetTotal action clears (zeroes) any accumulated total.
The NumericTotalizerExt is available in the Extensions folder of the control palette.
control-NumericWritable
NumericWritable extends NumericPoint to include 16 levels of command priority control. The
highest priority active command is reflected in the Out property. Commands at the Manual and
manual levels (1 and 8) are stored persistently. See “About control points” on page 3-1, and “About
writable points” on page 3-24 for more details.
The NumericWritable is available in the Points folder of the control palette.
control-StringPoint
StringPoint is a basic read-only control point, with default slots: Facets, Out, and ProxyExt. See
“About control points” on page 3-1 for details. The StringPoint is available in the Points folder of the
control palette.

NiagaraAX-3.x
13-13
User Guide
Components in converters module Chapter 13 – Component Guides
May 1, 2007

control-StringWritable
StringWritable extends StringPoint to include 16 levels of command priority control. The highest
priority active command is reflected in the Out property. Commands at the Manual and manual
levels (1 and 8) are stored persistently. See “About control points” on page 3-1, and “About writable
points” on page 3-24 for more details.
The StringWritable is available in the Points folder of the control palette.
control-TimeTrigger
TimeTrigger is a component that fires a topic at configured times. It is available configured as both
“Interval” or “Daily” in the Trigger folder of the control palette.

Components in converters module

• EnumToSimpleMap
converters-EnumToSimpleMap
EnumToSimpleMap maps ordinals to Simple instances of the same type.

Components in crypto module

• CryptoService
• SslProvider
crypto-CryptoService
CryptoService provides a central location to acquire cryptographic services, as SslProvider child
components. The CryptoService is available in the crypto palette.
crypto-SslProvider
Provides SSL configuration. Modification of the properties here will not modify a keystore. In other
words, the properties here must mirror the already existing keystore. For more details, see Bajadoc at
BSslProvider.bajadoc.

Components in devkit module

• LexiconOptions
devkit-LexiconOptions
The LexiconOptions stores the options used by the LexiconReport and LexiconEditor. The Lexicon
options allow you to change the following:
• Hide Ref Values
• Hide Accelerators
• Show Missing Only
These are stored under /user/{user}/lexicon.options.

Components in driver module

• ConfigRule
• DelimitedFileImport
• DriverContainer
• ExcelCsvFileImport
• FileDevice
• FileHistoryDeviceExt
• FileHistoryWorker
• FileNetwork
• HistoryNetworkExt
• PingMonitor
• SendTimer
• SendTimes
• TuningPolicy
• TuningPolicyMap

NiagaraAX-3.x
13-14
User Guide
Chapter 13 – Component Guides Components in driver module
May 1, 2007

driver-ConfigRule
ConfigRule is used to determine the configuration overrides for histories when they are exported to
the station. By default, the parent container HistoryNetworkExt (History Policies) contains only a
single ConfigRule, named “Default Rule.” Default settings are to configure “all” histories exported to the
station as “unlimited” capacity.
For more details, see “Config Rules” on page 4-52 and “About History Policies” on page 4-51.
driver-DelimitedFileImport
DelimitedFileImport is a history file import descriptor used to create a Niagara history based upon
data in a (local) delimited text file, such as comma-separated-values (CSV) or tab-delimited values
(delimiter to use is configurable). These import descriptors reside under the HistoryNetworkExt
(Histories extension) of a FileDevice in a FileNetwork. You use the Delimited File Import Manager
view of the Histories extension to add history file import descriptors.
Note: This import descriptor is similar to the ExcelCsvFileImport descriptor, but uses a “dumb” string tokenizer
to parse each line of the specified file, and separates table columns based solely on the specified delimiter.
Only “non-complex” CSV files should be imported using it, or any “non-CSV” delimited file (such as tab-
delimited, for example). For any CSV file created by Microsoft Excel, use the ExcelCsvFileImport descriptor
instead.
This import descriptor has properties “common” among all history import descriptors, such as Name,
History Id, and so on. See “History Import properties” on page 4-38. For other configuration properties,
see “Properties of history file import descriptors” on page 13-15.
driver-DriverContainer
DriverContainer is used by convention to store all DeviceNetworks in a station database. The
DriverManager is its primary view. See “About the Driver Manager” on page 4-4.
driver-ExcelCsvFileImport
ExcelCsvFileImport is a history file import descriptor used to create a Niagara history based upon
data in any (local) comma-separated-values (CSV) text file created by Microsoft Excel. These history
file import descriptors reside under the HistoryNetworkExt (Histories extension) of a FileDevice in a
FileNetwork. You use the DelimitedFileImportManager view of the Histories extension to add history file
import descriptors.
Note: This import descriptor is similar to the DelimitedFileImport descriptor, but assumes CSV data specifically
created by Microsoft Excel (it lacks the “Delimiter” property). This allows complex CSV-delimited data to
be successfully imported, using the special rules of Excel CSV generated files. For any other type of delimited
data (for example, tab-delimited or “pipe-delimited”), use the DelimitedFileImport descriptor instead.
This import descriptor has properties “common” among all history import descriptors, such as Name,
History Id, and so on. See “History Import properties” on page 4-38. See the next section “Properties of
history file import descriptors” for other configuration properties.
Properties of history file import descriptors History file import descriptors (DelimitedFileImport,
ExcelCsvFileImport) have the following set of configuration properties, which appear in the New and
Edit dialogs for the descriptors:
• Value Facets
Lets you specify the units with which to display values imported from the delimited file. On the im-
port descriptor’s property sheet, this is property is found under “Config Overrides”.
• Time Zone
Lets you specify the timezone for the imported history. On the import descriptor’s property sheet,
this is property is found under “Config Overrides”.
• File
(Important) Identifies the local delimited file to import, using standard “ord” file syntax. Typically,
you simply click the folder icon to open the File Chooser, and navigate as needed to click-select
an absolute file ord path to the file.
Of, if the parent FileDevice has a non-null “Base Ord” property (specifying a directory), you can type
in a file name or file path relative to that directory, using the following ord syntax:
file:fileName or filePath/toFileName
• Full Import On Execute
Default is disabled. If set to enabled, the entire history is re-filled afresh upon each import. If left at
default, only new data is appended to the history upon every import.
• Row Start
Along with Row End, lets you specify the start and end rows (lines) in the file to use for importing.
Note that both properties are zero-based, meaning that a Row Start of 1 means that it skips the first

NiagaraAX-3.x
13-15
User Guide
Components in driver module Chapter 13 – Component Guides
May 1, 2007

line (usually column headers), and begins importing on the second line.
• Row End
See Row Start, above. Row End is optional, and defaults to go to the end of the file (none).
• Delimiter
(appears only if a DelimitedFileImport descriptor) Specifies the text character used in the file to sep-
arate columns. For any ExcelCsvFileImport descriptor, a comma (“,”) is used by default.
• Timestamp Column Index
(Required, zero-based) Left-to-right index of the column in the file used to import the timestamp.
For example: if first column, this value is “0”; if second column, this value is “1”; and so on.
• Timestamp Format
(Required) String that specifies how timestamps are formatted in the file. A drop-down control lets
you select among several common formats—after selection, you can further edit if necessary (may
be necessary if you execute, and the descriptor is in fault). For timestamp format details and exam-
ples, see http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html
• Value Column Index
(Required, zero-based) Left-to-right index of the column in the file used to import the value. For ex-
ample: if the second column, this value is “1”; if the fifth column, this value is “4”; and so on.
• Value Format
Specifies the value type, meaning the type of history record to create, as one of the following:
• Numeric Type — (default) for a numeric type history.
• String Type — for a string type history.
• Boolean Type — for a boolean (two-state) type history.
• Status Column Index
(Usage optional). The left-to-right index (zero-based) of the column in the file used to import the
status, if available. Note that the imported status value must match the Niagara “status bits” imple-
mentaton in encoded-integer format, using the following decimal equivalent values (either singly, or
in the case of non-zero values in combinations):
• 0 - ok
• 1 - disabled
• 2 - fault
• 4 - down
• 8 - alarm
• 16 - stale
• 32 - overridden
• 64 - null
• 128 - unackedAlarm
• Identifier Column Index
(Usage optional). The left-to-right index (zero-based) of the column in the file used to filter rows for
inclusion, in combination with the Identifier Pattern property value (below). Default value is None
(no row filtering).
• Identifier Pattern
(Usage optional). Specifies the text string in the Indentifier Column (above) that is searched for in
all rows, where any row with the matching text string is imported. Note that wildcard (“*”) charac-
ters are supported. Default if value is * (everything matched).
driver-FileDevice
FileDevice is the AX-3.1 “device level” container to import local delimited-type files (such as CSV)
as Niagara histories. It resides under the FileNetwork. It has common device properties (see “Device
status properties” on page 4-20) and Health and Alarm Source Info slots.
The FileDevice’s only device extension, and most important child slot, is the FileHistoryDeviceExt
(Histories), under which you add file import descriptors. The sole configuration property of impor-
tance is “Base Ord”, where you can select a specific local directory (use drop-down control beside folder
icon, choose Directory Chooser). This allows you to enter relative file ord values in the “File”
property of history file import descriptors (under its child Histories extension). Otherwise (using the
default “null” Base Ord), you specify absolute “File” ord values in child descriptors. For related details, see
“Properties of history file import descriptors”.
Note: Typically, a FileNetwork is configured with only a single FileDevice, with a default “null” value Base Ord
property. However, if you wish to impose some logical grouping, you can create multiple FileDevices, and
use the Base Ord scheme (with different directory ords) to separate import descriptors by source.
Note: Unlike many fieldbus drivers, there is no “frozen” LocalFileDevice in a FileNetwork—any FileDevice named
“LocalFileDevice” is simply a standard FileDevice component.

NiagaraAX-3.x
13-16
User Guide
Chapter 13 – Component Guides Components in driver module
May 1, 2007

driver-FileHistoryDeviceExt
FileHistoryDeviceExt is the driver module implementation of HistoryDeviceExt, and is the only
device extension under a FileDevice. The default view is the DelimitedFileImportManager view,
which you use to add new (or edit existing) file import descriptors. Each descriptor adds a Niagara history
in the local history space.
driver-FileHistoryWorker
FileHistoryWorker manages the queue and and thread processing for history file import
descriptors. It is a frozen slot of the FileDevice, and requires no configuration.
driver-FileNetwork
FileNetwork is available in the AX-3.1 driver module, and acts as the “network level” container for
one or more FileDevice components. The FileDeviceManager is its primary view.
The purpose of a FileNetwork is to import data from local delimited-type files (such as CSV), as Niagara
histories. Often, a FileNetwork contains only a single FileDevice. Unlike in true “field bus” networks, the
standard NiagaraAX driver architecture (network: device: device extensions) provides no “real hardware”
equivalency, this is simply a modeling “convention.”
Figure 13-1 shows the architecture of a FileNetwork in the Nav tree, where the active (and most used)
view is the DelimitedFileImportManager view of the Histories extension (FileHistoryDeviceExt) of
the FileDevice.

Figure 13-1 FileNetwork architecture uses standard “device” modeling

Note that a FileDevice has none of the other “standard” device extensions (Points, Schedules, or
Alarms). See “Usage notes” for more details on a File Network.
Usage notes The following notes apply to using a FileNetwork.
• The FileNetwork requires special licensing in the host’s Tridium (Vykon) license—requiring the fea-
ture “fileDriver”. This feature may also contain a “history.limit=n” attribute, which defines
the number of files that can be imported as histories (number of history file import descriptors).
Without proper licensing, the FileNetwork and child components will have a fault status, and files
will not import as Niagara histories.
• Specific requirements must be met by each delimited text file for successful import, namely:
• It must have a single “timestamp” column that contains both date and time. Note this means if
a delimited file has two columns: one for date and another for time, you must perform external
“upstream” processing (outside of Niagara) to combine into a single column, before importing.
• It must have a single column that contains the “value” required in the imported history. Note
that when configuring the history file import descriptor, you specify the “Value Format” as one

NiagaraAX-3.x
13-17
User Guide
Components in email module Chapter 13 – Component Guides
May 1, 2007

of several types (Numeric, String, Boolean). “Value Facets” are also available in the descriptor.
• Optionally, it may also have a single column to use as “Status” in the history—however, this col-
umn must contain integer data (only) with values enumerated based upon Niagara “status bits”
values. See “Properties of history file import descriptors” on page 13-15 for related details.
Note the status import feature may be used mainly with data that first originated from a Niagara
history (that was exported to CSV), then subsequently “manipulated” outside of Niagara.
• Typically, FileNetwork usage applies more to an AxSupervisor (PC) host versus a JACE host, as it is
more likely to contain text-delimited files needed for import as Niagara histories. In particular, it
may be used with an AxSupervisor serving “Energy Services” reports to remote clients.
driver-HistoryNetworkExt
HistoryNetworkExt (History Policies) manages network-level functions for histories that are
exported to the station. Its is the container of the rules (ConfigRules) that specify how the configu-
ration of the local history (archive) should be set when the history is “pushed” (exported) into the station.
Configuration rules are applied only when the history is created, that is, when first archived to the station.
Changing a rule has no effect on existing histories. For more details, see “About History Policies” on page
4-51.
driver-PingMonitor
The PingMonitor periodically calls “ping” on all the “pingables” to monitor network and device
health. PingMonitor provides built-in support to generate alarms when pingables are down. The
PingMonitor is available in the property sheet of most networks as “Monitor.” See “About Monitor” on
page 4-7 for more details.
driver-SendTimer
This class file provides support for max and min send time on components implementing the
TimedWrites interface. The sendTimer will identify a SendTimes object in the parent path. The first
SendTimes encounter walking up from the immediate parent will be used. If no SendTimes object is
found then calls to newChange() will result in an single immediate call to sendWrite() on the parent. The
SendTimer is available in the driver Module.
driver-SendTimes
This class file provides the means to configure max and min send times for components imple-
menting the TimedWrites interface and containing SendTimer object. The SendTimes is available in
the driver Module.
driver-TuningPolicy
Contains a collection of properties typically used in the driver network’s evaluation of both write
requests (e.g. to writable proxy points) as well as the acceptable “freshness” of read requests. Also, can
associate with one of 3 Poll Rates in the network’s Poll Service.
You can create multiple TuningPolicies under a driver’s TuningPolicyMap. You can then assign one or
more proxy points to a specific TuningPolicy. See“About Tuning Policies” on page 4-8 for more details.
driver-TuningPolicyMap
Container for one or more TuningPolicy(ies), found in the property sheet of most network compo-
nents. You can create multiple TuningPolicies under a network’s TuningPolicyMap. You can then
assign one or more proxy points to a specific TuningPolicy. See“About Tuning Policies” on page 4-8 for
more details.

Components in email module

• Email
• EmailRecipient
• EmailService
• IncomingAccount
• OutgoingAccount
email-Email
Email represents an email message.
email-EmailRecipient
The top-level email Messaging service. This service manages the routing of all email messages from
message sources to message recipients. The EmailRecipient is available in the email palette.
Actions Actions include RouteAlarm.

NiagaraAX-3.x
13-18
User Guide
Chapter 13 – Component Guides Components in file module
May 1, 2007

RouteAlarm RouteAlarm routes the alarm.

email-EmailService
EmailService manages the life-cycle of Email. The EmailAccountManager is its primary view. The
EmailService is available in the email palette.
email-IncomingAccount
IncomingAccount is a Email that receives mail. A number of properties specify the SMTP host,
port, and user credentials to use, as well as other parameters. The IncomingAccount is available in
the email palette.
email-OutgoingAccount
OutgoingAccount is a Email that sends mail. A number of properties specify the SMTP host, port,
and user credentials to use, as well as other parameters. A “Max Sendable Per Day” property can limit
the number of station-generated emails, where the default value is 100. The OutgoingAccount is available
in the email palette.

Components in file module

• ApplicationFile
• AudioFile
• AudioFile
• BajadocFile
• BogFile
• BogScheme
• BogSpace
• CFile
• CssFile
• ExcelFile
• GifFile
• HtmlFile
• HtmlFile
• ImageFile
• JavaFile
• JpegFile
• NavFile
• PaletteFile
• PdfFile
• PngFile
• PowerPointFile
• PowerPointFile
• PrintFile
• PxFile
• TextFile
• VideoFile
• VisioFile
• WordFile
• XmlFile
file-ApplicationFile
ApplicationFile stores an application file.
file-AudioFile
AudioFile stores an audio file.
file-BajadocFile
BajadocFile represents Bajadoc documentation. Bajadoc is a special file that can describe compo-
nents in a database.
file-BogFile
BogFile represents a BogFile in the file system of a session. A Bog File is a special file that can
describe Components in a Database.

NiagaraAX-3.x
13-19
User Guide
Components in file module Chapter 13 – Component Guides
May 1, 2007

file-BogScheme
BogScheme represents a BogScheme in the file system of a session. A Bog File is a special file that
can describe Components in a Database.
file-BogSpace
BogSpace represents a BogSpace in the file system of a session. A Bog File is a special file that can
describe Components in a Database.
file-CFile
CFile stores a c source file.
file-CssFile
CssFile stores a CSS cascading style sheet.
file-ExcelFile
ExcelFile stores a Microsoft Excel file.
file-GifFile
GifFile stores a GIF image.
file-HtmlFile
HtmlFile stores HTML markup.
file-ImageFile
ImageFile stores an image.
file-JavaFile
JavaFile stores a java source file.
file-JpegFile
JpegFile stores a JPEG image.
file-NavFile
NavFile stores XML nav markup.
file-PaletteFile
Palette file is just a Bog File file with a different extension and icon.
file-PdfFile
PdfFile stores a Adobe PDF file.
file-PngFile
PngFile stores a PNG image.
file-PowerPointFile
PowerPointFile stores a Microsoft PowerPoint file.
file-PrintFile
PrintFile stores XML Print markup.
file-PxFile
PxFile is just a Bog File file with a different extension and icon.
file-TextFile
TextFile stores plain text.
file-VideoFile
VideoFile stores an video file.
file-VisioFile
VisioFile stores a Microsoft Visio file.
file-WordFile
WordFile stores a Microsoft Word file.
file-XmlFile
XmlFile stores an xml file.

NiagaraAX-3.x
13-20
User Guide
Chapter 13 – Component Guides Components in fox module
May 1, 2007

Components in fox module

• FoxClientConnection
• FoxFileService
• FoxServerConnection
• FoxService
• FoxSession
fox-FoxClientConnection
FoxClientConnection encapsulates a FoxSession connection. You must setup the Address,
Username and Password in order to access a remote station. The FoxClientConnection is
available in the fox Module.
Actions You can manually force/test a connection using Manual Connect and Manual
Disconnect actions.
fox-FoxFileSpace
FoxFileSpace maps "File:" remotely.
fox-FoxServerConnection
FoxServerConnection encapsulates a Fox (client) session connection to the station’s Fox server. It
represents user access (vs. access from another station). Child slots provide the connection state as
well as various historical data about last connect and disconnect activity. The FoxServerConnection is
available in the fox module.
Actions Available Action is Force Disconnect.
fox-FoxService
FoxService is the Baja Component wrapper for the FoxServer daemon. It is commonly used within
a NiagaraNetwork, but can be used stand alone to provide basic Fox accessibility.
fox-FoxSession
FoxSession is a host's session using a fox connection to a specific port.
fox-ServerConnections
ServerConnections is the container slot to store the current server-side FoxServerConnections
from non-station clients. The primary view is the ServerConnectionsSummary. The ServerConnec-
tions is available in the fox module.

Components in gx module
• Brush
gx-Brush
Brush is used to change presentation. The Brush is available in the gx Module.

Components in help module

• BajadocOptions
help-BajadocOptions
The BajadocOptions stores the options used by the BajadocViewer. The Bajadoc options allow you
to change the following:
• Show Baja Only
• Flatten Inheritance
These are stored under /user/{user}/bajadoc.options.

Components in history module

• AuditRecord
• AuditHistoryService
• BooleanCovHistoryExt
• BooleanIntervalHistoryExt
• ConfigRule
• ConfigRules
• CovAlgorithm

NiagaraAX-3.x
13-21
User Guide
Components in history module Chapter 13 – Component Guides
May 1, 2007

• EnumCovHistoryExt
• EnumIntervalHistoryExt
• FoxHistory
• FoxHistorySpace
• HistoryConfig
• HistoryDevice
• HistoryEditorOptions
• HistoryId
• HistoryService
• IntervalAlgorithm
• LocalDatabaseConfig
• LogHistoryService
• NumericCovAlgorithm
• NumericCovHistoryExt
• NumericIntervalHistoryExt
• NumericIntervalAlgorithm
• StringCovHistoryExt
• StringIntervalHistoryExt
history-AuditRecord
The AuditRecord keeps a History of changes made by users. If enabled, it registers itself as the
Auditor for the system when the service is started. The AuditRecord is available in the History
Module under the HistoryService.
history-AuditHistoryService
The AuditHistoryService keeps a history of changes made by users. If enabled, it registers itself as
the auditor for the station when the service is started. The AuditHistoryService is available in the
history palette.
One of the important aspects of security is the ability to analyze what has happened after the fact. The
Niagara Component model is designed to audit all property modifications and all Action invocations.
Auditable actions include:
• Property changed
• Property added
• Property removed
• Property renamed
• Properties reordered
• Action invoked
Component modifications are only audited when the modification method is passed a non-null Context
with a non-null User. The History Module includes a standard implementation of an audit trail stored to
a History Database File.
history-BooleanCovHistoryExt
BooleanCovHistoryExt is a history extension that is used for recording on change of value for
boolean point data. This extension is available in the history Module Extensions Directory. Refer
to “Types of history extensions” on page 3-14 for more information about this extension.
history-BooleanIntervalHistoryExt
BooleanIntervalHistoryExt is a history extension that is used for recording on intervals for boolean
point data. This extension is available in the history Module Extensions Directory. Refer to
“Types of history extensions” on page 3-14 for more information about this extension.
history-ConfigRule
ConfigRule is used to determine the overrides for an existing history configuration. The ConfigRule
is available in the history Module.
history-ConfigRules
ConfigRules is the container for rules that determine the configuration of histories that are pushed
to the local device. Configuration rules are applied when a history is created. Changing a rule has no
effect on existing histories. The ConfigRules is available in the history Module.
history-CovAlgorithm
CovAlgorithm determines when to log a point's value according to change of value. The CovAlgo-
rithm is available in the history Module Extensions Directory under some Change Of Value exten-
sions as Collector.

NiagaraAX-3.x
13-22
User Guide
Chapter 13 – Component Guides Components in history module
May 1, 2007

history-EnumCovHistoryExt
EnumCovHistoryExt is a history extension used to record on a change of value for Enum point data.
This extension is available in the history Module Extensions Directory. Refer to “Types of history
extensions” on page 3-14 for more information about this extension.
history-EnumIntervalHistoryExt
EnumIntervalHistoryExt is a history extension used to record on intervals for Enum point data. This
extension is available in the history Module Extensions Directory. Refer to “Types of history
extensions” on page 3-14 for more information about this extension.
history-FoxHistory
FoxHistory is the implementation of BIHistory that works with the FoxHistorySpace.
history-FoxHistorySpace
FoxHistorySpace provides access to a History Database using the fox protocol.
history-HistoryConfig
HistoryConfig is the configuration for a History in the History Database.
history-HistoryDevice
HistoryDevice represents a source device for histories.
history-HistoryEditorOptions
The HistoryEditorOptions stores the options used to configure history options.
These are stored under /user/{user}/textEditor.options.
history-HistoryId
HistoryId is a container for History id.
history-HistoryService
The History service provides http access to all histories in the Station. This service manages the
History lifecycle, including creation and deletion. Additionally, HistoryService maintains the
namespace for all Histories. As histories are created, they are added as slots to this service, and removed
upon deletion. When the service is started, all existing histories are added to the service. Additionally,
this service maintains global configuration for the histories. Each Station contains a single History-
Service. See the HistoryExtManager for more information on using histories. The HistoryService is
available in the History Module.
CloseUnusedHistories Close all Unused Histories in this service.
FlushHistories Flush all histories managed by this service.
history-IntervalAlgorithm
IntervalAlgorithm logs a value periodically at a fixed interval. The IntervalAlgorithm is available in
the history Module Extensions Directory under some Interval extensions as Collector.
history-LocalDatabaseConfig
LocalDatabaseConfig is the configuration for a LocalHistoryDatabase.
history-LogHistoryService
The LogHistoryService keeps a History of Niagara log records. If enabled, it registers itself as the
LogHandler for the system when the service is started. The LogHistoryService is available in the
History Module.
history-NumericCovAlgorithm
NumericCovAlgorithm determines when to log a numeric point's value according to change of
value. The NumericCovAlgorithm is available in the history Module Extensions Directory under
NumericChangeOfValue as Collector.
history-NumericCovHistoryExt
NumericCovHistoryExt is a history extension used to record on change of value for numeric point
data. This extension is available in the history Module Extensions Directory. Refer to “Types of
history extensions” on page 3-14 for more information about this extension.
history-NumericIntervalAlgorithm
NumericIntervalAlgorithm logs a numeric point's value according to a schedule. The Numeri-
cIntervalAlgorithm is available in the history Module Extensions Directory under NumericInterval
as Collector.

NiagaraAX-3.x
13-23
User Guide
Components in kitPx module Chapter 13 – Component Guides
May 1, 2007

Actions Actions include and .

Collect Collect a data point.
CommenceCollection Start Collection in the algorithm.
history-NumericIntervalHistoryExt
NumericIntervalHistoryExt is a history extension used to record on interval for numeric point data.
This extension is available in the history Module Extensions Directory. Refer to “Types of history
extensions” on page 3-14 for more information about this extension.
Actions Actions include and .
Collect Collect a data point.
CommenceCollection Start Collection in the algorithm.
history-StringCovHistoryExt
StringCovHistoryExt is a history extension used for collecting a string control value on change of
value. This extension is available in the history Module Extensions Directory. Refer to “Types of
history extensions” on page 3-14 for more information about this extension.
history-StringIntervalHistoryExt
StringIntervalHistoryExt is a history extension for collecting a string control value at intervals. This
extension is available in the history Module Extensions Directory. Refer to “Types of history
extensions” on page 3-14 for more information about this extension.

Components in kitPx module

• ActionBinding
• AnalogMeter
• Bargraph
• BoundLabel
• BoundLabelBinding
• GenericFieldEditor
• ImageButton
• IncrementSetPointBinding
• RefreshButton
• SaveButton
• SetPointBinding
• SetPointFieldEditor
kitPx-ActionBinding
kitPx-ActionBinding invokes an action on the binding target component when an event is fired by
the parent widget. The ORD of an action binding must resolve down to a specific action within a
component.
Additional information and related topics include:
• “About action bindings” on page 8-15
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-AnalogMeter
kitPx-AnalogMeter is a widget that is designed to look and act like a analog meter. This component
comes with a value binding that should be bound to a value by an ORD.
Additional information and related topics include:
• “About Widgets” on page 8-7
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-Bargraph
kitPx-Bargraph is a widget that is designed to display a single value in a bar graph. In addition to
action bindings, value and setpoint bindings are available.
Additional information and related topics include:
• “About value bindings” on page 8-13
• “Types of bindings” on page 8-11

NiagaraAX-3.x
13-24
User Guide
Chapter 13 – Component Guides Components in kitPx module
May 1, 2007

• “Types of binding properties” on page 8-12

To plot more than one value using a single widget (using a line chart), you can use a chart widget, as
described in “Create a Chart widget” on page 8-34, or for history tables, “About the history chart view”
on page 6-10.
kitPx-BoundLabelBinding
kitPx-BoundLabelBinding is used exclusively for connecting a value to a bound label widget. Bound
labels, which are located in the kitPx module, have properties that you can edit and access from the
Px Editor properties side bar.
Additional information and related topics include:
• “About bound label bindings” on page 8-13
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-BoundLabel
kitPx-BoundLabel is a widget that simply provides a label widget (see “bajaui-Label” on page 13-10)
with a binding already available.
Additional information and related topics include:
• “About bound label bindings” on page 8-13
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-GenericFieldEditor
kitPx-GenericFieldEditor is a field editor that allows you to edit properties from a graphic view on
non-specific fields. It is designed for layout on panes and is comprised of standard widgets like
buttons, text fields, and check boxes. Specialized field editor widgets include: SetPointFieldEditor (see
“kitPx-SetPointFieldEditor” on page 13-26).
Additional information and related topics include:
• “About field editor bindings” on page 8-16
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-ActionButton
kitPx-ActionButton is a button that uses images to display the state of the button. For example, the
action button may have three separate images to indicate the normal, mouseOver, and pressed
states. In addition to other properties, the image button includes the following distinctive properties:
• Mouse Over
this property allows you to assign an image that appears when the mouse hovers over the button.
• Normal
this property allows you to assign an image that appears when the button is not in a pressed or mou-
seOver state.
• Pressed
this property allows you to assign an image that appears when the button is pressed.
See the following topics for related information about buttons:
• “kitPx-RefreshButton” on page 13-26
• “kitPx-SaveButton” on page 13-26
• “bajaui-Button” on page 13-9
• “bajaui-ToggleButton” on page 13-12
kitPx-IncrementSetPointBinding
kitPx-IncrementSetPointBinding is used to increment (increase) or decrement (decrease) a
setpoint value.
Additional information and related topics include:
• “About increment setpoint bindings” on page 8-15
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12

NiagaraAX-3.x
13-25
User Guide
Components in ldap module Chapter 13 – Component Guides
May 1, 2007

kitPx-RefreshButton
kitPx-RefreshButton is used to issue a refresh command when it is clicked. The “Refresh” text
that appears on the button is included by default in the Text property–but, like the other properties,
it may be edited, as desired.
See the following topics for related information about buttons:
• “kitPx-ActionButton” on page 13-25
• “kitPx-SaveButton” on page 13-26
• “bajaui-Button” on page 13-9
• “bajaui-ToggleButton” on page 13-12
kitPx-SaveButton
kitPx is used to issue a save command when it is clicked. The “Save” text that appears on the
button is included by default in the Save property–but, like the other properties, it may be edited, as
desired.
See the following topics for related information about buttons:
• “kitPx-ActionButton” on page 13-25
• “kitPx-RefreshButton” on page 13-26
• “bajaui-Button” on page 13-9
• “bajaui-ToggleButton” on page 13-12
kitPx-SetPointBinding
kitPx-SetPointBinding is used to display the current value of a setpoint and also to provide the
ability to modify it. The setpoint binding ORD must resolve down to the specific property that is
being manipulated.
Additional information and related topics include:
• “About setpoint bindings” on page 8-14
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12
kitPx-SetPointFieldEditor
kitPx-SetPoinFieldEditor is a special field editor that is designed to allow you to edit setpoint values
from a graphic view. It is designed for layout on panes and is comprised of standard widgets like
buttons, text fields, and check boxes. For editing non-specific properties, use the kitPx GenericField-
Editor (see “kitPx-GenericFieldEditor” on page 13-25).
Additional information and related topics include:
• “About field editor bindings” on page 8-16
• “Types of bindings” on page 8-11
• “Types of binding properties” on page 8-12

Components in ldap module

• LdapClient
• LdapConfiguration
• LdapUserService
ldap-LdapClient
LdapClient is a client for Ldap. The LdapClient is available in the ldap Module.
ldap-LdapConfiguration
LdapConfiguration is a child of the LdapUserService that contains various properties that define
the LDAP attribute and connection methods. LdapConfiguration is available in the ldap palette.
ldap-LdapUserService
LdapUserService allows users to be downloaded from an LDAP server. LDAP users are stored
transiently and are hidden. If a non-transient user is found in the service at login, the LDAP server
will not be queried. The primary view is the UserManager. The LdapUserService is available in the ldap
Module.

Components in net module

• InternetAddress

NiagaraAX-3.x
13-26
User Guide
Chapter 13 – Component Guides Components in niagaraDriver module
May 1, 2007

net-InternetAddress
InternetAddress models an Internet address which is a composite of a hostname (or raw IP address) and
a port number.

Components in niagaraDriver module

• DistributedQuery
• NiagaraAlarmDeviceExt
• NiagaraFoxService
• NiagaraHistoryDeviceExt
• NiagaraHistoryImport
• NiagaraNetwork
• NiagaraPointDeviceExt
• NiagaraPointFolder
• NiagaraProxyExt
• NiagaraScheduleDeviceExt
• NiagaraScheduleImportExt
• NiagaraStation
• NiagaraStationFolder
• PointChannel
• QueryService
• StationDiscoveryTask
• StationWorker
niagaraDriver-DistributedQuery
DistributedQuery is the configuration for a distributed query against zero or more remote stations.
The DistributedQuery is available in the niagaraDriver Module.
niagaraDriver-NiagaraAlarmDeviceExt
NiagaraAlarmDeviceExt is used to map all native Alarms in a device into the Baja Alarm framework.
The NiagaraAlarmDeviceExt is available in the niagaraDriver Module.
niagaraDriver-NiagaraFoxService
NiagaraFoxService is a specialization of FoxService that knows how to map server connections to
the NiagaraStation serverConnection slot. NiagaraFoxService typically includes ServerConnections.
The NiagaraFoxService is available in the niagaraDriver Module.
niagaraDriver-NiagaraHistoryDeviceExt
NiagaraHistoryDeviceExt is the Niagara implementation of HistoryDeviceExt. NiagaraHistoryDe-
viceExt is available in the niagaraDriver Module.
niagaraDriver-NiagaraHistoryImport
NiagaraHistoryImport defines the local import parameters for a remote Niagara history, including
collection (“pull”) times, current status, local history Id, and config overrides. NiagaraHistoryImports
reside under the History extension of a Station in the Niagara Network.
niagaraDriver-NiagaraNetwork
NiagaraNetwork models the list of NiagaraAX devices (NiagaraStationNiagaraStationNiagaraSta-
tions) that a given station can communicate with. The primary view is the StationManager. Niagar-
aNetwork includes the NiagaraFoxService. The NiagaraNetwork is available in the niagaraDriver
Module.
niagaraDriver-NiagaraPointDeviceExt
NiagaraPointDeviceExt is the Niagara implementation of PointDeviceExt. The primary view is the
PointManager. The NiagaraPointDeviceExt is available in the niagaraDriver Module as Points in
Station.
niagaraDriver-NiagaraPointFolder
NiagaraPointFolder is the Niagara implementation of a folder under a NiagaraStation’s Points
extension. You add such folders using the New Folder button in the PointManager view of the Points
extension. Each NiagaraPointFolder has its own PointManager view. The NiagaraPointFolder is also
available in the niagaraDriver palette.

NiagaraAX-3.x
13-27
User Guide
Components in program module Chapter 13 – Component Guides
May 1, 2007

niagaraDriver-NiagaraProxyExt
NiagaraProxyExt is the Niagara implementation of BProxyExt. The NiagaraProxyExt is available in
the niagaraDriver Module as Proxy Ext under NiagaraNetwork.
niagaraDriver-NiagaraScheduleDeviceExt
This represents the schedules in a device. The NiagaraSchedule is available in the niagaraDriver
Module.
niagaraDriver-NiagaraScheduleImportExt
NiagaraScheduleImport defines the local import parameters for a remote Niagara schedule.
NiagaraScheduleImportExts reside under the Schedules extension of a NiagaraStation in the Niagara
Network.
niagaraDriver-NiagaraStation
NiagaraStation models a platform running a Niagara station including a JACE, NP, or Supervisor.
The NiagaraStation name must map to Station.stationName. NiagaraStation typically includes
FoxClientConnection, FoxServerConnection, NiagaraPointDeviceExt, NiagaraScheduleDeviceExt,
NiagaraHistoryDeviceExt and NiagaraAlarmDeviceExt. The NiagaraStation is available in the niagar-
aDriver Module as Station.
Ping Perform a ping test of the device.
niagaraDriver-NiagaraStationFolder
NiagaraStationFolder is the Niagara implementation of a folder under a NiagaraNetwork. You add
such folders using the New Folder button in the StationManager view of the Niagara network. Each
NiagaraStationFolder has its own StationManager view. The NiagaraStationFolder is also available in the
niagaraDriver palette.
niagaraDriver-PointChannel
PointChannel handles messages used by the NiagaraPointDeviceExt.
PushPointEvent This callback is linked to the various local Component's point properties for
subscriptions being pushed to the remote VM.
niagaraDriver-QueryService
QueryService is the service that processes distributed queries for a NiagaraNetwork. The Query-
Service is available in the niagaraDriver Module.
niagaraDriver-StationDiscoveryTask
StationDiscoveryTask is used to Discover the Stations on the Network. The StationDiscoveryTask
is available in the niagaraDriver Module.
niagaraDriver-StationWorker
StationWorker manages the queue and worker for communication to a specific station. The
StationWorker is available in the niagaraDriver Module.

Components in program module

• Program
• ProgramService
program-Program
Program uses an instance based classfile to implement user defined component logic. The Program
can be viewed and edited using the ProgramEditor. The Program is available in the program Module.
Actions Actions include Execute.
program-ProgramService
ProgramService is used to launch batch programs. The ProgramService is available in the program
Module.
Actions Actions include Run Robot.

Components in pxeditor module

• NewPxViewDialog

NiagaraAX-3.x
13-28
User Guide
Chapter 13 – Component Guides Components in rdb module
May 1, 2007

pxeditor-NewPxViewDialog
NewPxViewDialog allows you to create a new px view.

Components in rdb module

• RdbmsFolder
• RdbmsNetwork
• RdbmsWorker
rdb-RdbmsFolder
RdbmsFolder is used to organize databases under an RdbmsNetwork. It is created using the New
Folder button in the DriverManager view for any RdbmsNetwork.
rdb-RdbmsNetwork
RdbmsNetwork models a network of BRdbms objects. It is available in the any of the rdb (relational
database) palettes, such as rdbDb2, rdbOracle, and rdbSqlServer.
rdb-RdbmsWorker
RdbmsWorker manages the queue and worker for asynchronous operations on a single database. It
is available under any of the rdb (relational database) types, such as Db2Database, OracleDatabase,
and SqlServerDatabase.

Components in rdbDb2 module

• Db2Database
• Db2HistoryDeviceExt
rdbDb2-Db2Database
Db2Database models an Db2 relational database. It is available in the rdbDb2 palette.
rdbDb2-Db2HistoryDeviceExt
Db2HistoryDeviceExt is the Db2 implementation of HistoryDeviceExt. It is a child of a
Db2Database.

Components in rdbOracle module

• OracleDatabase
• OracleHistoryDeviceExt
rdbOracle-OracleDatabase
Db2Database models an Oracle relational database. It is available in the rdbOracle palette.
rdbOracle-OracleHistoryDeviceExt
OracleHistoryDeviceExt is the Oracle implementation of HistoryDeviceExt. It is a child of a Oracle-
Database.

Components in rdbSqlServer module

• SqlServerDatabase
• SqlServerHistoryDeviceExt
rdbSqlServer-SqlServerDatabase
SqlServerDatabase models an SqlServer relational database. It is available in the rdbSqlServer palette.
rdbSqlServer-SqlServerHistoryDeviceExt
SqlServerHistoryDeviceExt is the SqlServer implementation of HistoryDeviceExt. It is a child of an
SqlServerDatabase.

Components in report module

• ComponentGrid
• EmailRecipient
• ExportSource
• ReportPane

NiagaraAX-3.x
13-29
User Guide
Components in schedule module Chapter 13 – Component Guides
May 1, 2007

• ReportService
• SectionHeader
report-ComponentGrid
The ComponentGrid allows you to define and design your report content (typically in the Grid Editor
view). Use the component grid to link and layout the data that you want to put into your report. The
ComponentGrid component is available in the Reporting folder of the report palette. Refer to “About the
ComponentGrid component” on page 8-42 for more details.
report-EmailRecipient
The EmailRecipient component contains properties that allow you to specify where the report is to
be emailed. The property sheet view displays the properties that you configure for this function. The
EmailRecipient component is available in the Reports folder in the report palette. Refer to “About the
EmailRecipient component” on page 8-42 for more details.
report-ExportSource
The ExportSource component allows you to define a report display source (typically a Px file) for
exporting and it allows you to schedule a time that you want to export it. The property sheet view contains
the properties that you configure for these functions. This component is available in the report palette.
Refer to “About the ExportSource component” on page 8-41 for more details.

report-ReportPane
The ReportPane widget is available in the ReportWidgets folder of the Report palette. It provides a
container for layout of Px page report views. The ReportPane has the standard Visible, Enabled, and
Layout properties, but also has unique properties. Refer to “About the ReportPane component” on page
8-43 for more details.
report-ReportService
The report service is the parent, or container, for the ExportSource, EmailRecipient, and Compo-
nentGrid components. In order to use the report service, copy the ReportService component from the
Report module to the Services folder in the Workbench nav tree. It is available in the Reporting folder of
the Report palette. Refer to “About the ReportService component” on page 8-41 for more information
about the ReportService component.
report-SectionHeader
The SectionHeader component is used to put a title or heading at the top of a report. It is located in
the ReportWidgets folder in the Report palette. More information about the SectionHeader component
is available in “About the SectionHeader component” on page 8-43.

Components in schedule module

• BooleanSchedule
• CalendarSchedule
• EnumSchedule
• NumericSchedule
• StringSchedule
• TriggerSchedule
schedule-BooleanSchedule
A deployable weekly schedule that provides a continuous StatusBoolean output. Other weekly
schedule types include EnumSchedule, NumericSchedule, and StringSchedule. See “About weekly
schedules” on page 10-3 for more details.
Input - If the “in” property is linked and its value is non-null, then this value overrides the scheduled
output. The BooleanSchedule is available in the schedule palette.
Using Schedules Schedules allow you to program commands to occur at specific times. Each
schedule component is designed to provide an output based on the current time. Components can
receive this command by linking to this output. See the “Weekly Scheduler view” on page 10-5 for more
information on using schedules.
schedule-CalendarSchedule
The CalendarSchedule provides a calendar for scheduling holidays or other schedule overrides. The
CalendarSchedule is available in the schedule palette.

NiagaraAX-3.x
13-30
User Guide
Chapter 13 – Component Guides Components in serial module
May 1, 2007

schedule-EnumSchedule
A deployable weekly schedule that provides a continuous StatusEnum output. Other weekly
schedule types include BooleanSchedule, NumericSchedule, and StringSchedule. See “About weekly
schedules” on page 10-3 for more details.
Input - If the “in” property is linked and its value is non-null, then this value overrides the scheduled
output. The EnumSchedule is available in the schedule palette.
schedule-NumericSchedule
A deployable weekly schedule that provides a continuous StatusNumeric output. Other weekly
schedule types include BooleanSchedule, EnumSchedule, and StringSchedule. See “About weekly
schedules” on page 10-3 for more details.
Input - If the “in” property is linked and its value is non-null, then this value overrides the scheduled
output. The NumericSchedule is available in the schedule palette.
schedule-StringSchedule
A deployable weekly schedule that provides a continuous StatusString output. Other weekly
schedule types include BooleanSchedule, EnumSchedule, and NumericSchedule. See “About weekly
schedules” on page 10-3 for more details.
Input - If the “in” property is linked and its value is non-null, then this value overrides the scheduled
output. The StringSchedule is available in the schedule palette.
schedule-TriggerSchedule
A schedule that fires topics - there is no continuous output. The TriggerSchedule is available in the
schedule palette.

Components in serial module

• SerialHelper
serial-SerialHelper
Container slot that handles the serial port configuration of any serial-based driver (found under the
driver’s Network-level component as “Serial Port Config”).
Note: Also found under any SerialTunnel (in station’s TunnelService) to support a tunneling connection to the
same type of network. In this case, configure it the same as the SerialHelper of the associated driver
network.
SerialHelper contains the following properties:
• Status
Read-only status of the serial port, where it can be fault if a problem was detected, down if the serial
port is not properly configured, or ok otherwise.
• Port Name
String for the serial port, as known to the host platform. For example, COM1 or COM4.
• Baud Rate
Baud rate used in serial communications. Select from enumerated drop-down selections, from
Baud50 through Baud115200. Default value is Baud9600.
• Data Bits
Data bits used in serial communications. Select from enumerated drop-down selections, from Data
Bits8 through Data Bits5. Default value is Data Bits8.
• Stop Bits
Number of stop bits used, as either Stop Bit1 (default) or Stop Bit2.
• Parity
Parity to use, as either None, Odd, Even, Mark, or Space. Default value is None.
• Flow Control Mode
Parity to use, as either RtsCtsOnInput, RtsCtsOnOutput, XonXoffOnInput, XonXoffOnOutput,
or none (all checkboxes cleared). Default value is none.

Components in timesync module

• TimeSyncClient
• TimeSyncService

NiagaraAX-3.x
13-31
User Guide
Components in tunnel module Chapter 13 – Component Guides
May 1, 2007

timesync-TimeSyncClient
Slot of a TimeSyncService used to poll a time protocol server. The TimeSyncClient is available in
the timesync palette.
timesync-TimeSyncService
A time protocol (RFC 868) client and server. To synchronize with other servers, TimeSynClients
must be added to the service. As a convenience, a disabled default client has already been added (it
will need configuring). The service uses the clients to poll their configured servers, and if the service
detects a drift greater than the tolerance property, the service will reset the system time. The module
palette contains clients preconfigured for well known time protocol servers. The primary view of this
Component is TimeSyncManager.
From the PropertySheet, you can set Enabled and Server Enabled.Enabled (to false) to disable
the time sync client. Server Enabled enables the time sync server. In order to sync between stations,
enable master TimeSync service to be a server, then add a TimeSyncClient in the station, configured for
the server Station. The TimeSyncService is available in the timesync palette.
ForceSync Force Time Synchronization.
Sync Time Synchronization.

Components in tunnel module

• TunnelService
• SerialTunnel
• TunnelConnection
tunnel-TunnelService
Station server for “application tunneling,” where remote PCs with a NiagaraAX Tunnel Client
installed can use a legacy or vendor-specific PC application to access devices connected to one or
more driver networks. A tunnel connection allows the remote client application to operate as it were
directly attached to the driver network (via a “virtual” PC port).
A client PC tunnels using an IP (LAN/WAN) connection, which is granted only after authentication as a
station user (with admin write permissions for the particular child tunnel component accessed).
Currently, the following types of child tunnels are supported:
• SerialTunnel
• LonTunnel
In any station, only one TunnelService is recommended. It can hold the required number of child tunnels,
as needed.
The TunnelService contains the following properties:
• Enabled
Boolean that must be true to support any tunnel server operations.
• Server Port
Software port monitored for incoming client tunnel connections. Default port is 9973.
• Status
TunnelService status, which should be ok (no special licensing required).
• Connections
Number of active tunnel connections, which ranges from 0 (no active) to the number of child tunnel
components.
tunnel-SerialTunnel
. SerialTunnel is the “server side” component used to support tunneling of Windows serial-
connected PC applications to devices reachable in a station’s driver network. Typically, serial
tunneling is used with a “legacy” vendor-specific PC program to access RS-232 connected devices
attached to a JACE controller.
You can add one or more SerialTunnels under a station’s TunnelService. Each SerialTunnel associates
with one specific driver network (and corresponding JACE serial port). See “Serial tunneling” on page 5-
2 for more details.
Properties of the SerialTunnel are described as follows:
• Enabled
Boolean slot that must be enabled (true) to permit tunneling.

NiagaraAX-3.x
13-32
User Guide
Chapter 13 – Component Guides Components in web module
May 1, 2007

• Connections
Read-only slot to indicate the number of tunnel connections, as either 0 (none) or 1 (maximum).
• Status
Read-only status of the serial tunnel, typically ok (unless fault for no supporting COM port).
• Identifier
Read-only “reflection” of the entered Port Name slot in the Serial Port Config container (below),
used as the “Tunnel Name” when configuring the client-side Serial Tunneling dialog.
• Serial Port Config (container)
Holds configuration of the JACE serial port as used by the specific driver network. See SerialHelper
on page 31 for slot descriptions.
In addition, a SerialTunnel has an available (right-click) action:
• Disconnect All
Disconnects any active connection through this SerialTunnel (maximum of 1), causing removal of
the “TunnelConnection” below it. On the remote (serial tunnel client) side, a popup message “Con-
nection closed by remote host” is seen.
Note: Any TunnelConnection component also has its own “Disconnect” action, which effectively
performs the same function.
tunnel-TunnelConnection
. TunnelConnection is a dynamically-added component under a tunnel component (such as a Serial-
Tunnel) that reflects read-only information about this current tunnel connection.
Properties of a TunnelConnection (any tunnel type) are as follows:
• Established
Date-timestamp of when this tunnel connection was first established.
• User Name
User in the station that is currently tunneling.
• Remote Host
Windows hostname or IP address of the remote tunneling client.
• Protocol Version
Version of the (remote) NiagaraAX tunneling client application being used.
• Last Read
Date-timestamp of when the last read of a station item occurred over the tunnel connection.
• Last Write
Date-timestamp of when the last write to a station item occurred over the tunnel connection.
In addition, a TunnelConnection has an available (right-click) action:
• Disconnect
Disconnects the active tunnel connection, removing the parent TunnelConnection component.
This causes a popup “Connection closed by remote host” to be seen on the client tunnel side.
Note: A SerialTunnel component also has its own “Disconnect All” action, which effectively performs
the same function.

Components in web module

• WebService
web-WebService
WebService encapsulates access to the HTTP server as well as the servlet infrastructure used to
expose custom applications over HTTP. The WebService is available in the web palette. It is also one
of the default services in a station created by using the New Station tool. Only one WebService is
supported in a station.

Components in workbench module

• ComponentFinder
• WbFieldEditorBinding
• WbViewBinding
• WsOptions
workbench-ComponentFinder
The ComponentFinder dialog provides a means of finding Components.

NiagaraAX-3.x
13-33
User Guide
Components in workbench module Chapter 13 – Component Guides
May 1, 2007

Figure 13-2 Sample Window

workbench-WbFieldEditorBinding
WbFieldEditorBinding is used to bind WbFieldEditors to an object. It allows any existing WbField-
Editor (BooleanFE, EnumFE, AbsTimeFE,etc) to be used in a PX presentation.
workbench-WbViewBinding
WbViewBinding is used to bind WbViews to an object. It allows any existing WbView (Property-
Sheet, WireSheet, PointManager, etc.) to be used in a PX presentation.
workbench-WsOptions
The WireSheet options allow you to view and change the following:
•Show Thumbnail
• Show Grid
• Show Status Colors
These are stored under /user/{user}/wiresheet.options.

NiagaraAX-3.x
13-34
User Guide
 CHAPTER 14
Plugin Guides
There are many ways to view plugins (views). One way is directly in the tree. In addition, you can right-
click on an item and select one of its views. Plugins provide views of components.
In Workbench, access the following summary descriptions on any plugin by selecting Help > On View
(F1) from the menu, or pressing F1 while the view is open.

Types of plugin modules

Following, is a list of the types of plugin modules:
• Plugins in alarm module
• Plugins in backup module
• Plugins in chart module
• Plugins in devkit module
• Plugins in driver module
• Plugins in email module
• Plugins in help module
• Plugins in history module
• Plugins in html module
• Plugins in ldap module
• Plugins in niagaraDriver module
• Plugins in program module
• Plugins in pxEditor module
• Plugins in raster module
• Plugins in rdb module
• Plugins in report module
• Plugins in schedule module
• Plugins in timesync module
• Plugins in wiresheet module
• Plugins in wbutil module
• Plugins in workbench module

Plugins in alarm module

• alarm-AlarmConsole
• alarm-AlarmDbMaintenance
• alarm-AlarmDbView
• alarm-AlarmClassSummary
• alarm-AlarmExtManager
• alarm-AlarmInstructionsManager
• alarm-AlarmPortal
alarm-AlarmConsole
The Alarm Console allows you to view and acknowledge Alarms. It can be started by Right-clicking
the alarmRecipient in the AlarmService and selecting Views > Alarm Console.
Viewing Alarms Multiple Alarms from a single source are visualized as a single row in the alarm console.
Color coded icons provide a visual indication for unacknowledged/inAlarm, acknowledged/inAlarm, and
unacknowledged/not inAlarm.

NiagaraAX-3.x
14–35
User Guide
Plugins in alarm module Chapter 14 – Plugin Guides
May 1, 2007

• alarm
• redAlarm
• greenAlarm
• orangeAlarm
Double-clicking a row in the Table shows the history of the alarms associated with that point. You can
sort the Alarms in order of any column by pressing the column bar (once for ascending, twice for
descending). Available commands include:
• Acknowledge
• Hyperlink
• Notes
• Silence
• Filter
Acknowledging Alarms Select an Alarm by Left-clicking it. In order to acknowledge an Alarm, press
the Alarm Acknowledge toolbar button or select Alarm > Acknowledge from the Menu. You
can select multiple Alarms and acknowledge them simultaneously. In order to silence Alarms, press the
Alarm Silence toolbar button or select Alarm > Silence from the Menu.
Acknowledge Acknowledge allows you to acknowledge the currently selected Alarm(s).
Hyperlink Hyperlink allows you to hyperlink to Alarm URL.
Silence Silence allows you to silence the currently selected Alarm(s).
Filter Filter allows you to filter alarms.
Alarm Report Dialog From the Alarm console, you can view the Alarm Report to see all alarms on the
point. Select an Alarm and Double-click it to see the Alarm Report.
You can sort the Alarms in order of any column by pressing the column bar (once for ascending, twice
for descending). Available commands include:
• Acknowledge
• Hyperlink
• Notes
• Filter
Viewing Alarm Record From the Alarm Report Dialog, you can view the Alarm record to see all infor-
mation on the Alarm. Select an Alarm and Double-click it to see the Alarm record.
Available commands include:
• Acknowledge
• Hyperlink
• Notes
• Filter
Notes Notes allows you to add user notes to Alarm records.
alarm-AlarmDbMaintenance
AlarmDbMaintenance is a view of the alarm service. It allows you view and manage alarm records.
For more information refer to:
• “About the alarm database maintenance view”
• “About the alarm service”
alarm-AlarmDbView
AlarmDb is a view of the alarm service. It allows you view and sort alarm records.
For more information refer to:
• “About the alarm service”
alarm-AlarmClassSummary
AlarmClassSummary is a view of the alarm service. It presents a table of information about all alarm
classes that are assigned to the alarm service.
For more information refer to:
• “About the alarm class summary view”
• “About the alarm service”

NiagaraAX-3.x
14-36
User Guide
Chapter 14 – Plugin Guides Plugins in backup module
May 1, 2007

alarm-AlarmExtManager
AlarmExtManager allows you to manage Alarm extensions.
alarm-AlarmInstructionsManager
AlarmInstructionsManager view displays a standard table-type report that provides a way to view,
assign, and edit alarm instructions.. For details, refer to “About the Instructions Manager view”.
alarm-AlarmPortal
The Alarm Portal allows you to view and acknowledge Alarms from multiple Stations. It can be
started from the main Menu by selecting Tools > AlarmPortal.
From the Alarm Portal, you can view the Alarm record to see all information on the Alarm. Select an
Alarm and Double-click it to see the Viewing Alarm Record. Available commands include:
• Acknowledge
• Silence
• Hyperlink
• Notes
• Filter

Plugins in backup module

• backup-BackupManager
backup-BackupManager
The BackupManager is the default view for a station’s BackupService. From this view you can issue
a backup command, to back up the station’s configuration to your local PC, in dist file format. When
you issue a Backup command, a File Chooser dialog appears to select the destination directory on
your PC (see File Ord Chooser) and the file name for the backup dist file.
The default backup destination depends on your station connection, as either:
• Workbench (Fox) — !backups
A subdirectory “backups” under your Niagara release directory. If you have not previously made
station backups, this directory is automatically created.
• Browser access (Wb Web Profile) — !backups
A subdirectory “backups” under the Niagara subfolder of your installed Java 2 runtime environ-
ment (Java plugin).
For example: C:\Program Files\Java\j2rel1.4.2_05\niagara\backups.
If you have not previously made station backups, this directory is automatically created.
The default name for a backup file uses a format of: backup_stationName_YYMMDD_HHMM.dist
For example, “backup_J403IP98c_050618_1429.dist” for a backup made of station “J403IP98c” on June
18, 2005 at 2:29 pm.
In the BackupManager, a progress bar and Job Log (>> control) is provided for an initiated backup.
The BackupManager displays a table of the 10 most recent backups, with the following data columns:
• Timestamp
Station date and time when the backup was initiated.
• Host
IP address of the requesting (remote) PC for the backup.
• Path
File path used on the requesting (remote) PC for saving the backup. Typically, this is relative to the
default Niagara directory (!), however, it may be an absolute file path.
• User
The station user that initiated the backup.

Plugins in chart module

• chart-ResourceManager
chart-ResourceManager
The Resource Manager is an available view on any running station. It provides a line chart of both
CPU and memory usage of the host platform, and updates in real time. In addition, individual
resource statistics are provided in a table, which you can refresh by clicking the Update button.

NiagaraAX-3.x
14-37
User Guide
Plugins in devkit module Chapter 14 – Plugin Guides
May 1, 2007

Plugins in devkit module

• devkit-LexiconEditor
• devkit-LexiconReport
devkit-LexiconEditor
The LexiconEditor Plugin allows you to view and modify the localization of lexicon files. The
lexiconEditor is invoked by selecting Lexicon Tool from the main Tools Menu. From there you
can select a lexicon by clicking on one. The LexiconEditor is invoked if you Double-click on a Module. It
will present the list of keys with default and lexicon value. If you select a key, you can change the lexicon
value by entering it at the bottom and pressing Change. You can select a different lexicon or Module
using the selection list at the top. You can also check Hide Icons, Hide Accelerators and/or
Show Missing Only to select the keys that will be displayed.
LexiconEditor Menus The Workbench main menu functions are available. When the LexiconEditor is
visible, the following LexiconEditor menu functions are also available:
• Hide Ref Values
• Hide Accelerators
• Show Missing Only
LexiconEditor Pulldowns and Buttons The lexiconEditor has pulldowns and buttons that include:
• Lexicon
• Module
• Hide Ref Values
• Hide Accelerators
• Show Missing Only
• Value
• Change
• Add New Key
LexiconEditor Toolbar The Workbench toolbar contains navigation and editing buttons as described in
About the toolbar.
Lexicon Lexicon pulldown allows you to select another lexicon directly from the LexiconEditor.
Module Module pulldown allows you to select another Module directly from the LexiconEditor.
Hide Ref Values Filter values starting with / from lexicon view. This is available if you do not want to
localize references (like icons).
Hide Accelerators Hide entries that define keyboard accelerators. This is available if you do not want to
localize the accelerators.
Show Missing Only Hide entries that are localized. This is available if you do not want to see localized
keys.
Value Value allows you to enter a new value for a lexicon entry. You must press Change for the value
to be entered.
Change Change places the new value into the list of keys. You must press Save to write values to the
lexicon file.
Add New Key Add New Key allows you to add an additional key to the lexicon. You must press Save
to write values to the lexicon file.
devkit-LexiconReport
The LexiconReport Plugin provides a report on localization of lexicon files. The LexiconReport in
invoked by selecting Lexicon Tool from the main Tools menu. From there you can select a
lexicon by Clicking on one. It will present the list of Modules with lexicons and the last time that the
Module lexicon was modified and the last time the lexicon was modified. It also shows the number of keys
missing from the lexicon for each Module. You can check Hide Icons and/or Hide Accelerators
to ignore these keys which are not usually localized. If you Double-click a Module, you will go to the
LexiconEditor. You can create new lexicons and delete lexicons.
LexiconReport Menus The Workbench main menu functions are available. When the LexiconReport is
visible, the following LexiconReport menu functions are also available:
• Hide Ref Values
• Hide Accelerators
LexiconReport Pulldowns and Buttons The LexiconReport has pulldowns and buttons that include:

NiagaraAX-3.x
14-38
User Guide
Chapter 14 – Plugin Guides Plugins in driver module
May 1, 2007

• Hide Ref Values

• Hide Accelerators
• New Lexicon
• Delete Lexicon
LexiconReport Toolbar The Workbench toolbar contains navigation and editing buttons as described
in “About the toolbar” on page 2-12.
New Lexicon This allows you to define a new lexicon. It should follow the Java localization model.
Delete Lexicon This allows you to delete a lexicon.

Plugins in driver module

• driver-DelimitedFileImportManager
• driver-DeviceManager
• driver-DriverManager
• driver-FileDeviceManager
• driver-HistoryExportManager
• driver-HistoryImportManager
• driver-PointManager
driver-DelimitedFileImportManager
The Delimited File Import Manager view is the default view on the Histories
extension (FileHistoryDeviceExt) of a FileDevice (in a FileNetwork). See Figure 13-1 on page 17.
This manager view is similar to other driver’s history import managers—see “History Import Manager”
on page 4-37. However, there is no “Discover” feature to add history file import descriptors (types
ExcelCsvFileImport and DelimitedFileImport). Instead, you use the History Import New function to add
history file import descriptors, as each is simply to reference a local delimited-type text file (such as a CSV
type).
Like other manager views, the Delimited File Import Manager view is a table-based view, where you
create (New) history file import descriptors, or double-click existing import descriptors to make History
Import Edits. For details, see the next section “Delimited File Import Manager usage notes”.
Delimited File Import Manager usage notes The following notes apply specifically to using the
DelimitedFileImportManager view, the view most used within a FileNetwork (outside of property sheets
for created history file import descriptors).
• When adding a new descriptor, select the ExcelCsvFileImport type over the DelimitedFileImport
type whenever the source file is a CSV type that was created using Microsoft Excel. This provides
more support for importing “complex” CSV-formatted data—for example, including data that in-
corporates comma usage(s) within data fields.
• Add a single descriptor referencing a File that is patterned like other delimited files you wish to im-
port, then adjust configuration properties of that descriptor until it executes (imports a history)
properly—without a fault status. Note the Timestamp Format property may take some tweaking.
Then, duplicate that working import descriptor, (and before executing) change its File reference,
History Id, and whatever other properties you wish to keep unique. This saves engineering time.
For related details, see “Properties of history file import descriptors” on page 13-15.
driver-DeviceManager
The DeviceManager plugin allows you to create and manage devices. The DeviceManager is a view
on a network component in a station. For details, see “About the Device Manager” on page 4-12.
driver-DriverManager
The DriverManager plugin allows you to add and view drivers. It is available on the DriverContainer.
For more details, see “About the Driver Manager” on page 4-4.
driver-FileDeviceManager
The File Device Manager is the default view on a FileNetwork. For general information, see “About
the Device Manager” on page 4-12. See the section “driver-FileNetwork” on page 13-17 for more
details about a File Network. Also, note that the view used most often under a File Network is the Delim-
itedFileImportManager view of the Histories extension of a FileDevice.

NiagaraAX-3.x
14-39
User Guide
Plugins in email module Chapter 14 – Plugin Guides
May 1, 2007

driver-HistoryExportManager
HistoryExportManager provides a view of NiagaraHistoryDeviceExt. To see the view, right-click on
a NiagaraHistoryDeviceExt in a Station and select Views > History Export Manager. For
details, see “History Export Manager” on page 4-41.
driver-HistoryImportManager
HistoryImportManager provides a view of NiagaraHistoryDeviceExt. To see the view, right-click on
a NiagaraHistoryDeviceExt in a Station and select Views > HistoryImportManager. For
details, see “History Import Manager” on page 4-37.
driver-PointManager
PointManager provides an overview of the proxy points mapped into the PointDeviceExt. In a
NiagaraNetwork, PointManager is a view on the NiagaraPointDeviceExt of a NiagaraStation. To see
the PointManager, right-click on a Points device extension and select Views > Point Manager. For
details, see “About the Point Manager” on page 4-28.

Plugins in email module

• email-EmailAccountManager
email-EmailAccountManager
email Manager allows you to view email accounts. It is available on the EmailService.

Plugins in help module

• help-BajadocViewer
help-BajadocViewer
The BajadocViewer Plugin provides the ability to navigate and browse Baja reference documen-
tation. Baja reference documentation includes both Java API details as well as Baja slot documen-
tation. It shows documentation for the following:
• Subclasses
• Properties
• Actions
• Topics
• Constructors
• Methods
• Fields
In order to view Bajadoc, either right-click on a Bajadoc file and select Views > Bajadoc Viewer
or select Bajadoc On Target from the main Help Menu or popup Menu.
See Object Model in the Developer Guide for more information.
BajadocViewer Menus The BajadocViewer menu functions include:
• Show Baja Only
• Flatten Inheritance
Show Baja Only This option allows you to view only the documentation for slots (Properties, Actions,
and Topics). When it is set to false, documentation on the Java constructors, methods and fields is also
displayed.
Flatten Inheritance This option allows you to flatten the inheritance hierarchy into a single set of
documentation. When it is false only the Java members and Baja slots declared in the specified class are
displayed. When it is set to true all the Java members and Baja slots inherited from super classes are also
shown.
Subclasses Subclasses provides a subclass tree of all that are subclassed from this item.
Properties Properties represent a storage location of another Niagara object. Flags are boolean values
which are stored as a bitmask on each slot in a Baja Object. Some flags apply to all slot types, while some
only have meaning for certain slot types.

Table 14-1 Flags

Flag Char Applies Description
readonly r P The readonly flag is used to indicate slots which are not accessible to users.

NiagaraAX-3.x
14-40
User Guide
Chapter 14 – Plugin Guides Plugins in history module
May 1, 2007

Flag Char Applies Description

transient t P Transient properties do not get persisted when saving a object graph to the file system. Transient
properties are usually also readonly, unless they are designed to be a linkable input slot.
hidden h P,A,T Hidden slots are designed to be invisible to the user, and exist only for Java developers. User
interfaces should rarely display hidden slots.
summary s P Summary properties are the focal points of any given BComponent. This flag is used by user
interface tools to indicate primary properties for display. This might be as a columns in a Table,
or as a glyph in a graphical programming tool.
async a A By default Action are invoked synchronously on the callers thread. By using the async flag on
an Action, invocations are coalesced and executed asynchronously at some point in the near
future on the engine's thread.
noExecute x P No execute properties prevents start/stop from recursing on properties with this flag set.
defaultOnClone d P Specifies that when an object is cloned via the newCopy() method these properties retain their
default value, not the clone source's value.
confirmRe- c A When the Action is invoked by a user, a confirmation dialog must be acknowledged before pro-
quired ceeding.
operator c P,A,T This makes a slot as operator security level. By default when this flag is clear, the slot is an admin
security level.
userDefined1 1 P,A,T User defined.
userDefined2 2 P,A,T User defined.
userDefined3 3 P,A,T User defined.
userDefined4 4 P,A,T User defined.
See Config Flags for information on configuring flags on properties.
Actions An Action is a slot that specifies behavior which may be invoked either through a user command
or by an event. Actions provide the capability to provide direction to Components. They may be issued
manually by the operator or automatically through links. Actions can be issued by Right-clicking on the
Component. The Component bajadoc provides a complete list of Actions available for each Component.
Typical Actions include:
• Manual actions are available based on Component type. The following are commonly available:
• Auto (BooleanWritable, NumericWritable and EnumWritable)
• Active (BooleanWritable)
• Inactive (BooleanWritable)
• Override (NumericWritable and EnumWritable)
Each of the above actions is issued to the priorityArray of the Component at level 8 (Manual Oper-
ator).
• Many other Actions are available on other Components. Each Action available for a Component is
listed in the Actions sect2 of the Component bajadoc.
Topics Topics represent the subject of an event. Topics contain neither a storage location, nor a
behavior. Rather a topic serves as a place holder for a event source.

Plugins in history module

• history-DatabaseMaintenance
• history-HistoryChart
• history-HistoryChartBuilder
• history-HistoryEditor
• history-HistoryExtManager
• history-HistorySummaryView
• history-HistoryTable
history-DatabaseMaintenance
The DatabaseMaintenance allows you to maintain the histories in a station from the Workbench.
You can Clear Old Records, Clear All Records or Delete Histories.

NiagaraAX-3.x
14-41
User Guide
Plugins in html module Chapter 14 – Plugin Guides
May 1, 2007

history-HistoryChart
The HistoryChart is a view that allows you to view and configure charts of histories. Any point
History can be charted by double-clicking it in the History Service.
history-HistoryChartBuilder
The HistoryChartBuilder is a view that allows you to view and configure charts of one or more
histories. Add a history by double-clicking or dragging into the configuration area. For any chart, you
can specify a Time Range, Title, and whether to show grid lines. Each history has a selectable Chart Type
of either Line or Discrete Line. After you Build a chart, you can Save it.
history-HistoryEditor
The HistoryEditor allows you to view and query a History in a Station.
The HistoryEditor allows you to Hide or Unhide selected records.
history-HistoryExtManager
The HistoryExtManager provides a tabular view of all history extensions. It is the default view of the
HistoryService and provides information about the control point, extension type, name and status of
each entry. Refer to the following references for information about the history extension manager, its
associated menus, toolbar icons, and other details.
Refer to the following sections for related information:
• “About the History Ext Manager menu” on page A-8
• “About the history extension manager” on page 6-3
• “About the history extension manager popup menu items” on page A-11
history-HistorySummaryView
The HistorySummaryView allows you to view the summary information about a History from the
Workbench.
history-HistoryTable
The HistoryTable is a view that allows you to view tables of histories. The selected entries are shown
as timestamp, trendFlags, status and value in each row of the Table.
You can resize columns in the HistoryTable. If you move the cursor over the line between columns, it will
change to a resize cursor. You can then drag the line to the desired size.
If want to reorder the columns in the HistoryTable, drag the column header to a new location.
Query Query lets you select the period for the query. Selections include:
• Time Range
• Today
• Yesterday
• Last Week
• Last 7 Days
• Last Month
• Last Year
• Month-to-date
• Year-to-date
Filter Filter lets you use the filter you have configured for the data in the Table.
Filter Config Filter lets you configure the filter for the data in the Table.

Plugins in html module

• html-WbHtmlView
• html-SpyViewer
html-WbHtmlView
• Introduction
• HTML Support
• Stylesheet Support
Introduction The WbHtmlView allows you to view HTML files.
WbHtmlView Menus The Workbench main menu functions are available.

NiagaraAX-3.x
14-42
User Guide
Chapter 14 – Plugin Guides Plugins in html module
May 1, 2007

WbHtmlView Toolbar In the WbHtmlView, the toolbar contains navigation and editing buttons as
described in “About the toolbar” on page 2-12. In addition, Find, FindNext and FindPrev toolbar buttons
are available.
HTML Support HTML Tags The WbHtmlView attempts to ignore mismatched or missing Tags. It can
parse any HTML, no matter how badly messed up the Tags are, although it might do a pretty bad job of
rendering the results. It does simplistically attempt to repair missing <p>, but other problems are solved
by ignoring Tags. Warnings will appear on the command line showing its best guess as to what the
problem was. Valid tags include:
• a - anchor Ex:<a href="#fragment">Title<a> and <a name="fragment">Title<a> (At-
tributes href and name)
• applet - not supported
• b - bold text style Ex: <b>bold text<b>
• body - document body
• br - forced line break
• code - computer code fragment
• col - not supported
• colgroup - not supported
• dd - definition description
• div - not supported
• dl - definition list
• dt - definition term
• em - emphasis Ex: <em>emphasis text<em>
• font - local change to font (Attributes Color, name and size)
• h1 - heading Ex:<h1 class='title'>Title<h1>
• h2 - heading
• h3 - heading
• h4 - heading
• h5 - heading
• h6 - not supported
• head - document head
• hr - horizontal rule
• html - document root element
• i - italic text style
• img - embedded image Ex: <img src="../doc/icons/x16/home.png"> An <img> with-
out an align attribute is treated as an 'inline' image. An align of left or right causes text to flow
around the image.
• li - list item
• link - a media-independent link Ex:<link rel='StyleSheet' href='module://bajaui/
doc/style.css' type='text/css'/>
• meta - not supported
• object - not supported
• ol - ordered list
• p - paragraph Ex:<p class='note'>Note<p>
• pre - preformatted text
• span - not supported
• style - not supported
• table - table (Attributes align, border, bordercolor, cellpadding, cellspacing and width)
• tbody - not supported
• td - table data cell supports ALIGN (left, right, and center), BGCOLOR, COLSPAN, ROWSPAN and
WIDTH
• tfoot - not supported
• th - table header cell supports ALIGN (left, right, and center), BGCOLOR, COLSPAN, ROWSPAN
and WIDTH
• thead - not supported
• title - document title
• tr - table row supports ALIGN (left, right, and center) and BGCOLOR
• tt - teletype or monospaced text style
• ul - unordered list
HTML Attributes HTML Elements have associated properties, called attributes, which may have values.
Attribute/value pairs appear before the final ">" of an element's start tag. Valid attributes include:

NiagaraAX-3.x
14-43
User Guide
Plugins in html module Chapter 14 – Plugin Guides
May 1, 2007

• align - vertical or horizontal alignment Deprecated; elements: img, object? values: bottom, left,
middle, right or top.
• align - table position relative to window Deprecated; elements: table; values: center, left or right
• align - align, text alignment Deprecated; elements: div?, h1?, h2?, h3?, h4?, h5?, h6?, p; values: cen-
ter, justify, left or right
• align - alignment; elements: col?, colgroup?, tbody?, td, tfoot?, th, thead?, tr; values: center, char,
justify, left or right
• bgcolor - background Color Deprecated; elements: h1, h2, h3, h4, h5, h6?, p, td, th, tr
• border - controls frame width around table; elements: table
• cellpadding - spacing within cells; elements: table
• cellspacing - spacing between cells; elements: table
• class - class name or set of class names for stylesheets; elements: most elements
• color - text Color Deprecated; elements: font, h1, h2, h3, h4, h5, h6?, p, pre, td?, th?, tr?
• colspan - number of cols spanned by cell; elements: td, th
• content - associated information; elements: meta?
• href - URI for linked resource; elements: a, link
• id - name to an element; elements: most elements
• lang - Language Code; elements: most elements not supported
• name - named link end; elements: a
• name - meta information name; elements: meta?
• rel - forward link types; elements: link; values: stylesheet
• rowspan - number of rows spanned by cell; elements: td, th
• size - size of font; elements: font; value: fixed 1-7 or relative -7 to +7
• summary - purpose/structure for speech output; elements: table
• type - advisory content type; elements: link; values: text/css
• width - table width; elements: table
Character Entity References Character Entity References are supported including the following:
• &amp; - ampersand &
• &apos; - apostrophe '
• &copy; - copyright ©
• &gt; - greater than >
• &ldquo; - double quotation, left “
• &lsquo; - single quotation, left ‘
• &lt; - less than <
• &mdash; - em dash —
• &nbsp; - non breaking space " "
• &ndash; - en dash –
• &rdquo; - double quotation, right ”
• &rsquo; - single quotation, right ’
• &quot; - quotation mark "
• &reg; - registered trademark ®
• &trade; - trademark ™
Stylesheet Support Introduction Stylesheets are supported using a link in the header as follows:
<head>
<title>Sample<title>
<link rel='StyleSheet' href='module://bajaui/doc/style.css' type='text/css'/>
<head>
See the default stylesheet used for Niagara developer documentation: module://bajaui/doc/style.css or
the CSS stylesheet used for this document at docbook.css.
Pseudo-classes and Pseudo-elements Anchor pseudo-classes include:
• A:link unvisited links unsupported
• A:visited visited links unsupported
• A:active active links unsupported
CSS1 Properties Stylesheet elements supported include:
• background - The 'background' property is a shorthand property for setting the individual back-
ground properties (i.e., 'background-color', 'background-image', 'background-repeat', 'background-
attachment' and 'background-position') at the same place in the style sheet.
• background-attachment unsupported
• background-color - This property sets the background Color of an element.

NiagaraAX-3.x
14-44
User Guide
Chapter 14 – Plugin Guides Plugins in html module
May 1, 2007

• background-image unsupported
• background-position unsupported
• background-repeat unsupported
• border unsupported
• border-bottom unsupported
• border-bottom-width unsupported
• border-color unsupported
• border-left unsupported
• border-left-width unsupported
• border-right unsupported
• border-right-width unsupported
• border-style unsupported
• border-top unsupported
• border-top-width unsupported
• border-width unsupported
• clear unsupported
• color - This property describes the text Color of an element (often referred to as the foreground Col-
or).
• display unsupported
• float unsupported
• font unsupported
• font-family unsupported
• font-size unsupported
• font-style unsupported
• font-variant unsupported
• font-weight unsupported
• height unsupported
• letter-spacing unsupported
• line-height unsupported
• list-style-image unsupported
• list-style-position unsupported
• list-style-type unsupported
• margin unsupported
• margin-bottom unsupported
• margin-left unsupported
• margin-right unsupported
• margin-top unsupported
• padding unsupported
• padding-bottom unsupported
• padding-left unsupported
• padding-right unsupported
• padding-top unsupported
• text-align
• text-decoration unsupported
• text-indent unsupported
• text-transform unsupported
• white-space unsupported
• width unsupported
• word-spacing unsupported
html-SpyViewer
SpyViewer allows you to view diagnostic information about the system. It contains the following:
•sysinfo - sysinfo provides system information.
• stdout - stdout provides access to standard output.
• systemProperties - systemProperties provides access to system properties.
• logSetup - logSetup allows you to config your log severities dynamically. There is also an option to
flush the current settings to log.properties.
• sysManagers - sysManagers provides information on managers. These include:
• registryManager
• schemaManager
• componentNavEventManager
• moduleManager

NiagaraAX-3.x
14-45
User Guide
Plugins in ldap module Chapter 14 – Plugin Guides
May 1, 2007

• engineManager
• leaseManager
• serviceManager
• licenseManager
• stationManager
• navSpace - provides information on the navSpace.
• userinterface - if System - userInterface provides information on the user interface framework.
• fox - fox provides information on fox client and server sessions.

Plugins in ldap module

• ldap-LdapUserManager
ldap-LdapUserManager
LdapUserManager allows you to manage Ldap users. You can add new users and edit existing users.

Plugins in niagaraDriver module

• niagaraDriver-NiagaraHistoryExportManager
• niagaraDriver-NiagaraHistoryImportManager
• niagaraDriver-Niagara PointManager
• niagaraDriver-NiagaraScheduleExportManager
• niagaraDriver-NiagaraScheduleImportManager
• niagaraDriver-ServerConnectionsSummary
• niagaraDriver-StationManager
niagaraDriver-NiagaraHistoryExportManager
NiagaraHistoryExportManager provides a view of NiagaraHistoryDeviceExt. To see the view, right-
click on a NiagaraHistoryDeviceExt in a Station and select Views > Niagara History
Export Manager.
niagaraDriver-NiagaraHistoryImportManager
NiagaraHistoryImportManager provides a view of NiagaraHistoryDeviceExt. To see the view,
Right-click on a NiagaraHistoryDeviceExt in a Station and select Views > Niagara History
Import Manager.
niagaraDriver-Niagara PointManager
Niagara PointManager provides an overview of the Proxy points mapped into the PointDeviceExt.
The Niagara PointManager is a view on the NiagaraPointDeviceExt in a Station in a NiagaraNetwork.
To see the Manager:
• Right-click on a NiagaraPointDeviceExt in a Station and select Views > Niagara Point Man-
ager.
Learn Learn allows you to Discover other points that are available. Once you press Learn, you can
press Discover to start the BQL Builder to select the types of points that you would like to review.
You can then Add or Match points so that they are available in your Database.
Paste As Breakpoints In order to link two Components in different stations, follow these steps:
1. Right-click on the Component in the originating Station and select Copy.
2. From the Point Summary View on NiagaraPointDeviceExt (usually Points under station in
NiagaraNetwork) in the receiving Station, Right-click on the background and select Paste As
Breakpoints or press Paste as ProxyPoint. This will pop-up the Paste As Proxy
Dialog.
3. Double-click on the property to link (often out). This will cause the Source and Proxy Point to
be visible on the right.
4. Press Ok.
If you change the Proxy Point Type to a Writable type and select one of the priority levels, you can
make it commandable.
Create Graphics Page Create Graphics Page starts a Wizard to guide you through creation of a
graphics page.

NiagaraAX-3.x
14-46
User Guide
Chapter 14 – Plugin Guides Plugins in program module
May 1, 2007

niagaraDriver-NiagaraScheduleExportManager
The NiagaraScheduleExportManager Plugin allows you to Discover and view Stations. The Niagar-
aScheduleExportManager is a view on the NiagaraNetwork in a Station.
niagaraDriver-NiagaraScheduleImportManager
The NiagaraScheduleImportManager Plugin allows you to Discover and view Stations. The Niagar-
aScheduleImportManager is a view on the NiagaraNetwork in a Station.
niagaraDriver-ServerConnectionsSummary
The Server Connections Summary is the default view of the ServerConnections slot in the
Niagara Fox Service, under the NiagaraNetwork. It provides a table listing current client connections
to the station’s Fox server (station-to-station connections are not included).
Note: The main usage of this view is to perform a Force Disconnect action (right-click access) on any Fox
server session shown. In some station maintenance scenarios, this may be helpful.
Included in connections summary table are the following columns:
• Address
IP address of the Fox client connected to the station, along with its remote TCP port.
• User
Station user account used for authentication.
• Connection Time
Timestamp of when the Fox connection occurred.
• Application
Client software used to access the station (for example, Niagara Workbench 3.0.76).
From the table, to see more details on any Fox server session, double-click an entry. The view changes to
show the property sheet of that SessionN, with status slots of historical information, including connect
and disconnect entries.
Access the Server Connections Summary from the property sheet of the NiagaraNetwork. Expand
the Fox Service, then click the Server Connections slot.
niagaraDriver-StationManager
The StationManager Plugin allows you to Discover and view Stations. The StationManager is a view
on the NiagaraNetwork in a Station.

Plugins in program module

• program-BatchEditor
• program-ProgramEditor
• program-RobotEditor
program-BatchEditor
The BatchEditor allows you to modify a common slot for a set of BObjects. It is a view on the
ProgramService.
program-ProgramEditor
Introduction The ProgramEditor Plugin provides the ability to view and edit Program Compo-
nents. To view, Right-click a Program and select ProgramEditor. It shows ProgramEditor
Edit, ProgramEditor Slots, ProgramEditor Imports and ProgramEditor Source tabs.
ProgramEditor Edit Edit allows you to edit the onExecute, onStart, onStop and freeForm
methods. An example from the demo Database follows:
BStatusNumeric inA = getInA();
BStatusNumeric inB = getInB();
BStatusNumeric out = getOut();

out.setValue( inA.getValue() + inB.getValue() );

ProgramEditor Slots Slots allows you to view and change the slots of the program component. It
includes Slot, #, Name, Display Name, Definition, Flags and Type for each slot. See
SlotSheet for more information on slots.
ProgramEditor Imports Imports allows you to view the Modules that have been imported.
It also allows the following:
• ProgramEditor ImportType

NiagaraAX-3.x
14-47
User Guide
Plugins in program module Chapter 14 – Plugin Guides
May 1, 2007

• ProgramEditor ImportPackage
• ProgramEditor Remove
ProgramEditor ImportType ImportType allows you to import a new type.
ProgramEditor ImportPackage ImportPackage allows you to import a new type.
ProgramEditor Remove Remove allows you to import a new type.
ProgramEditor Source Source allows you to view and edit the source of the program component.
The editor supports special Color coding for Java Files. An example from the demo Database follows:
/* Auto-generated ProgramImpl Code */

import java.util.*; /* java Predefined*/

import javax.baja.sys.*; /* baja Predefined*/
import javax.baja.status.*; /* baja Predefined*/
import javax.baja.util.*; /* baja Predefined*/
import com.tridium.program.*; /* program Predefined*/

public class ProgramImpl

extends com.tridium.program.ProgramBase
{

////////////////////////////////////////////////////////////////
// Getters
////////////////////////////////////////////////////////////////

public BStatusNumeric getOut() { return (BStatusNumeric)get("out"); }

public BStatusNumeric getInA() { return (BStatusNumeric)get("inA"); }
public BStatusNumeric getInB() { return (BStatusNumeric)get("inB"); }

////////////////////////////////////////////////////////////////
// Setters
////////////////////////////////////////////////////////////////

public void setOut(javax.baja.status.BStatusNumeric v) { set("out", v); }

public void setInA(javax.baja.status.BStatusNumeric v) { set("inA", v); }
public void setInB(javax.baja.status.BStatusNumeric v) { set("inB", v); }

////////////////////////////////////////////////////////////////
// onExecute
////////////////////////////////////////////////////////////////

public void onExecute()

throws Throwable
{
BStatusNumeric inA = getInA();
BStatusNumeric inB = getInB();
BStatusNumeric out = getOut();

out.setValue( inA.getValue() + inB.getValue() );

}
}
ProgramEditor Menus The Workbench main menu functions are available. When the ProgramEditor
is visible, the following ProgramEditor menu function is also available:
• ProgramEditor ImportType
• ProgramEditor ImportPackage
• ProgramEditor Remove
• Add Slot Ctrl + A
• Delete
• Rename Slot Ctrl + R
• Reorder
• ProgramEditor Compile & Save F9
• ProgramEditor Compile Ctrl + F9
ProgramEditor Toolbar The Workbench toolbar contains navigation and editing buttons as described
in “About the toolbar” on page 2-12. When the ProgramEditor is visible, additional toolbar buttons
include:
• Find F5
• Replace F6
• ProgramEditor Compile & Save F9

NiagaraAX-3.x
14-48
User Guide
Chapter 14 – Plugin Guides Plugins in pxEditor module
May 1, 2007

• ProgramEditor Compile Ctrl + F9

• Console Prev
• Console Next
ProgramEditor Compile & Save CompileSave allows you to compile and save the source of the
program component. The shortcut is F9.
ProgramEditor Compile Compile allows you to compile the source of the program component.
The shortcut is Ctrl + F9.
program-RobotEditor
The RobotEditor is used to write Robots that can be run via the ProgramService.
RobotEditor Menus The Workbench main menu functions are available. When the RobotEditor is
visible, the following RobotEditor menu function is also available:
• RobotEditor Compile Ctrl + F9
• RobotEditor Compile & Run F9
RobotEditor Toolbar The Workbench toolbar contains navigation and editing buttons as described in
“About the toolbar” on page 2-12. When the RobotEditor is visible, additional toolbar buttons include:
• Find F5
• Replace F6
• RobotEditor Compile Ctrl + F9
• RobotEditor Compile & Run F9
• Console Prev (?need to find SearchConsolePrev.html source?)
• Console Next (?need to find SearchConsoleNext.html source?)
RobotEditor Compile Compile allows you to compile the source of the Robot component. The
shortcut is Ctrl + F9.
RobotEditor Compile & Run Compile& Run allows you to compile and run the source of the
Robot component. The shortcut is F9.

Plugins in pxEditor module

• pxEditor-PxEditor
pxEditor-PxEditor
The PxEditor provides tools for creating and editing px files. The px editor is the view that is used
to create graphic presentations in Niagara AX. For more details about the px editor, refer to the
following:
• About Px Editor
• About presentation xml (px)
• About the Px Editor menu

Plugins in raster module

• raster-RasterViewer
raster-RasterViewer
The RasterViewer is used to display bitmapped image files: GIF, JPEG, PNG. It displays the image
in the main window with Format and image Size at the bottom.

Plugins in rdb module

• rdb-RdbmsHistoryExportManager
• rdb-RdbmsSessionView
rdb-RdbmsHistoryExportManager
The RdbmsHistoryExportManager allows you to export records in an Rdbms database as Niagara
histories. It is a view on the Histories extension of an Rdbms database, for example
Db2HistoryDeviceExt, OracleHistoryDeviceExt, and SqlServerHistoryDeviceExt.
rdb-RdbmsSessionView
The RdbmsSessionView provides a view for a session to a relational database.

NiagaraAX-3.x
14-49
User Guide
Plugins in report module Chapter 14 – Plugin Guides
May 1, 2007

Plugins in report module

• report-GridTable
• report-GridLabelPane
• report-ComponentGridEditor
report-GridTable
The Grid Table view is a view of the ComponentGrid component. This view provides a tabular
display of all the points that are assigned to the ComponentGrid.
For more details, see “About the Grid Table view” on page 8-44.
report-GridLabelPane
The Grid Label Pane view is a view of the ComponentGrid component. This view provides a tabular
display of all the points that are assigned to the ComponentGrid. In the Grid Table Pane view, you
can write to points (issue commands) using the popup menu, if you have write permissions.
For more details, see “About the Grid Label Pane view” on page 8-44.
report-ComponentGridEditor
The Grid Editor view is a view of the ComponentGrid component. This view provides a layout
display that you use to assign points that you are going to use in a report.
For more details, see “About the Grid Editor view” on page 8-46.

Plugins in schedule module

• schedule-CalendarScheduler
• schedule-CurrentDaySummary
• schedule-Scheduler
• schedule-TriggerScheduler
schedule-CalendarScheduler
The CalendarSchedule view is used to define calendar days in a CalendarSchedule. Typically,
calendar days represent holidays.
Use the Add button to add a calendar day (or range of days). Each entry requires a unique name, a date
type, and other specific calendar data criteria. Other controls in the CalendarSchedule allow you to edit
priority, rename, or delete calendar date entries.
For more details, see “Calendar Scheduler view” on page 10-13.
schedule-CurrentDaySummary
The CurrentDaySummary view is available on BooleanSchedule, EnumSchedule, Numeric-
Schedule, and StringSchedule components. It provides a simple linear listing of all schedule events
for the current day, moving left-to-right from 0-to-24 hours.
For more details, see “Summary” on page 10-12.
schedule-Scheduler
The Scheduler allows you to view and edit schedule components, namely BooleanSchedule,
EnumSchedule, NumericSchedule, and StringSchedule. Each of these components has a Scheduler
view. The only difference between these different schedules is the output type.
Note: For more details, see “Weekly Scheduler view” on page 10-5.
There are four major elements in the Scheduler interface, separated by tabs in the view:
• Weekly Schedule
• Special Events
• Properties
• Summary
Weekly Schedule Defines the regular (repeating) day-of-week schedule events for each day of the week.
Creating A Time Range Right-click and drag down in the slider column for desired the day.
Deleting A Time Range Click on a time range and press the delete or backspace key.
Editing A Time Range Time can be adjusted four ways: Dragging the top, bottom or center of a time range,
or using the fine grained start and finish editors. To fine-tune a time range click on a time range then
adjust the times in the editors to the left.

NiagaraAX-3.x
14-50
User Guide
Chapter 14 – Plugin Guides Plugins in timesync module
May 1, 2007

Note: IMPORTANT: The finish time is exclusive; it is the first non-effective time after the effective period. The
start time is inclusive.
Output is assigned to each time range and can be edited just below the time editors on the left.
Special Events Special events override (yet intermingle with) events in the normal weekly schedule.
Adding, Prioritizing, Renaming, and Deleting. Use the controls at the bottom for this purpose.
Editing At least one time range must be present for an exceptional to work. Output is assigned to the time
ranges. The slider operates exactly like the normal weekly sliders.
Properties Define the schedule’s effective period, default output, facets, and whether automatic special-
event cleanup occurs.
Default Output This is the value of the schedule's output when no normal or exceptional schedule is
effective.
Cleanup Special Events If set to true (default), special events that have expired are automatically
removed from the view. This occurs on the day following the scheduled special event.
Summary Shows months with selectable days, including all schedule event activity for any day selected.
schedule-TriggerScheduler
The TriggerSchedule view is used to define schedule events in a TriggerSchedule. Trigger schedules
are defined by combination of calendar day (or days) and trigger event time(s), including time ranges,
each with a repeating interval.
Use the bottom-left Add button to add a scheduled day (or range of days). Each entry requires a unique
name, a date type, and other specific calendar data criteria. Other controls in the TriggerSchedule allow
you to edit priority, rename, or delete calendar day entries.
Use the bottom-right Add button to add trigger events to any selected scheduled day(s). Use the time
selector to specify the individual trigger event. Use the Range controls to define a time range with
repeating interval for trigger events to occur.
For more details, see “About trigger schedules” on page 10-18.

Plugins in timesync module

• timesync-TimeSyncManager
timesync-TimeSyncManager
The TimeSyncManager is used to display the status of TimeSyncClients, as well as add new or edit
existing TimeSyncClients. By default, it displays Server Name, Status, Poll Delta, Poll Local Time,
and Poll Server Time for each TimeSyncClient.

Plugins in wiresheet module

• wiresheet-WireSheet
wiresheet-WireSheet
The WireSheet view shows the contents of this Component. It can be used on a Component of a
running Station or a Component in a Bog File. If in a running station, it is active and real-time
updates are provided. In order to command or select a different view of the item, you may Right-click to
get the popup menu.
WireSheet Menus The WireSheet includes the following menus:
• WireSheet Main Menu
• WireSheet Component Menu
• WireSheet Background Menu
• WireSheet Link Menu
WireSheet Main Menu The WireSheet main menu functions are available. When the *wiresheet; is
visible, the following WireSheet menu functions are also available:
• Delete Links
• Arrange
• Select All
• Show Thumbnail
• Show Grid

NiagaraAX-3.x
14-51
User Guide
Plugins in wiresheet module Chapter 14 – Plugin Guides
May 1, 2007

• Show Status Colors

WireSheet Component Menu If you Right-click any Component in the WireSheet, you can choose
from the following:
• views - Go to any of the views of the Component.
• Actions - Perform any of the Actions on the Component.
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Duplicate Ctrl + D
• Delete Delete
• CompositeEditor
• Rename
• Reorder
• Pin Slots
WireSheet Background Menu If you Right-click the Background of the WireSheet, you can choose
from the following:
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Duplicate Ctrl + D
• Delete Delete
• Delete Links
• Arrange
• Select All
• workbench-CompositeEditor
WireSheet Link Menu If you Right-click any link in the WireSheet, you can choose from the following:
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Duplicate Ctrl + D
• Delete Delete
• Delete Links
• Arrange
• Select All
• CompositeEditor
WireSheet Toolbar The Workbench toolbar contains navigation and editing buttons as described in
“About the toolbar” on page 2-12. When the WireSheet is visible, additional toolbar buttons include:
• Delete Links
Delete Links Delete Links may be accessed from the Menu under Edit or from the toolbar.
It allows you to eliminate the selected link(s). You can Delete Links only in the WireSheet.
Pin Slots Pin Slots provides the capability to make Properties of a Component visible in the
WireSheet view of the Component. Right-click on the Component and select Pin Slots. This will
bring up the Pin Slots Dialog.
The selected Properties are now visible in the WireSheet.
Arrange Arrange allows you to arrange the items in the WireSheet. You can Arrange All or
Arrange Selection.
Select All Select All allows you to select all items in the WireSheet.
Show Thumbnail Show the thumbnail view in the upper right corner of the WireSheet. This allows you
to toggle whether this function is enabled. This function may be accessed from the Menu under
WireSheet. It allows you to display a thumbnail of the WireSheet view in the corner of the WireSheet.
You can use the thumbnail to move around the WireSheet by Dragging the shaded area in the thumbnail.
You can also hold down the Ctrl key and move the thumbnail around the WireSheet to keep it out of your
way.

NiagaraAX-3.x
14-52
User Guide
Chapter 14 – Plugin Guides Plugins in wbutil module
May 1, 2007

Show Grid When enabled, the Grid is displayed in the background of the WireSheet. This helps you to
align Components when you move them. You may control whether the Grid layer is enabled or visible
from the WireSheet Menu or the Tools > Options Menu. This allows you to toggle whether this
function is enabled.
Show Status Colors Show the Status Colors. This allows you to toggle whether this function is enabled.
This function may be accessed from the Menu under WireSheet. It allows you to display StatusColors in
the WireSheet.
workbench-PrintDialog Print provides the capability to print the WireSheet. The WireSheet will
remain fixed at logical size of 100 x 100 "blocks". Printing will scale the WireSheet drawing to fit the
page size (minus header and footer). Thus if you build your WireSheet logic in the top left corner, you will
get a large scale for your print out. If you use the entire WireSheet down to the bottom right corner, you
will get a much smaller scale for your print out. Margins are 1" for left and 1/2" for top, bottom, and right.
A standard header is included which displays container's reference and current date. A future version will
create a footer listing external links and knobs.
workbench-CompositeEditor Composite Editor provides the capability to expose child slots of a
Component as slots on the parent. Right-click on the Component and select Composite Editor.
This will bring up the Composite Editor Dialog. The selected Properties are now visible in the WireSheet.
workbench-ExportDialog Export provides the capability to Export views. You can Export any
Table found in the workbench (anything built with bajaui:Table). The Table options menu (that little
button to the right of the header), includes a Print and Export command. These commands allow you to
Export the Table to PDF, HTML, or CSV (ExcelFile). The Export uses the current sort order and visible
columns you have displayed.

Plugins in wbutil module

• wbutil-CategoryBrowser
• wbutil-CategoryManager
• wbutil-CategorySheet
• wbutil-PermissionsBrowser
• wbutil-ResourceEstimator
• wbutil-TodoList
• wbutil-UserManager
wbutil-CategoryBrowser
CategoryBrowser is the default view of a station’s CategoryService. Use it to assign objects in the
station into categories. This view presents an expandable tree table where the table columns are the
available categories, and rows are the categorizable objects.
• Yellow rows are objects explicitly assigned into a category.
• Dimmed rows represent objects inheriting their parent’s categories.
Note: For any object except the three root objects: station (components), file, and history, you can check to inherit
its parent’s categories. For root objects, you must select at least one category.
For any component, you can alternately use its CategorySheet view to assign it categories. See
“Categories and security” on page 9-2 for details on how categories affect security, and “Category-
Browser” on page 9-16 for more details on this CategoryService view.
wbutil-CategoryManager
CategoryManager is a view on the CategoryService that allows you to create, enable and delete
categories. Categories are used by the security model, as well as for future features. You can then use
the CategoryBrowser view to centrally assign objects to categories. Or, at the individual component level,
use a component’s CategorySheet view to assign it to categories.
You can assign an object to many categories at the same time. Each object stores its own categories. See
“Categories and security” on page 9-2 for details on how categories affect security, and “Category-
Manager” on page 9-15 for more details on this CategoryService view.
wbutil-CategorySheet
CatgegorySheet is used to assign a component into one or more categories (or configure it to inherit
categories). Every component has a CategorySheet view. See “Categories and security” on page 9-2
for details on how categories affect security, and “CategorySheet” on page 9-17 for more details on this
component view.

NiagaraAX-3.x
14-53
User Guide
Plugins in workbench module Chapter 14 – Plugin Guides
May 1, 2007

wbutil-PermissionsBrowser
PermissionsBrowser is an available view on the UserService, for reviewing the permissions any user
has on each object. It provides an expandable tree table (similar to the CategoryBrowser view of the
CategoryService). In the PermissionsBrowser, columns represent station user accounts, and rows are the
objects in the station, with each table cell showing user permissions.
• Yellow rows are objects explicitly assigned with permissions.
• Dimmed rows represent objects inheriting their permissions.
Double-click a cell to bring up the permissions dialog for that user (unless user has super user rights).
This allows you to globally change that user’s permission levels for any category in the station.
See “Permissions and security” on page 9-4 for details on how permissions affect security, and “Permis-
sionsBrowser” on page 9-13 for more details on this UserService view.
wbutil-ResourceEstimator
The Resource Estimator tool allows you to estimate station resources based a number of variables,
which you enter in various fields. It is one of several tools in Workbench’s Tools menu.
For more information, refer to “Resource estimator” on page 11-10.
wbutil-TodoList
The Todo List tool allows you to enter, summarize, group, and prioritize pending Workbench tasks.
It is one of several tools in Workbench’s Tools menu.
For more information, refer to “Todo list” on page 11-10.
wbutil-UserManager
The UserManager is the primary view of the UserService. You use it to add, edit, and delete users
for accessing the station. See “Users and security” on page 9-2 for details on how users affect security,
and “UserManager” on page 9-10 for more details on this UserService view.
For an overview on the station security model, see “Security model overview” on page 9-1.

Plugins in workbench module

• workbench-CollectionTable
• workbench-DirectoryList
• workbench-HexFileEditor
• workbench-JobServiceManager
• workbench-LinkSheet
• workbench-ModuleSpaceView
• workbench-NavContainerView
• workbench-NavFileEditor
• workbench-PropertySheet
• workbench-SlotSheet
• workbench-StationSummary
• workbench-TextFileEditor
• workbench-ServiceManager
• workbench-WbPxView
• workbench-WbServiceManagerView
workbench-CollectionTable
The CollectionTable allows you to view tables. One way to create a Table is through a BQL
collection like:
local:|fox:|station:|slot:/ControlObjects|bql:select displayName,type, out,
facets from control:ControlPoint
The Table options menu (see “Table controls and options” on page 2-17, for more details about the table
options), allows you to Reset Column Widths, Print and Export.
workbench-DirectoryList
The DirectoryList Plugin provides a listing of the subdirectories and files found in a given
Directory. If you Double-click an item, you will go to its default view.
Files will be displayed with an icon based on file type.
DirectoryList Menus The Workbench main menu functions are available. When the DirectoryList is
visible, the following popup menu functions are also available:

NiagaraAX-3.x
14-54
User Guide
Chapter 14 – Plugin Guides Plugins in workbench module
May 1, 2007

• Views - show the view menus for the Component.

• Actions - Perform any of the Actions on the Component.
• New - Create a new file of standard types (if a Directory).
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Duplicate Ctrl + D
• Delete Delete
• Rename
• Reorder
DirectoryList Toolbar The Workbench toolbar contains navigation and editing buttons as described in
“About the toolbar” on page 2-12.
Refresh Refresh allows you to synchronize the cached components with the actual file system.
New New allows you to make a new Folder or File in the selected Folder of these types:
• New Folder allows you to make a new Folder in the selected Folder.
• BogFile.bog
• HtmlFile.html
• JavaFile.java
• NavFile.nav
• PrintFile.print
• TextFile.txt
workbench-HexFileEditor
The HexFileEditor allows you to view hexadecimal files. It provides a binary view of a file's
contents.
workbench-JobServiceManager
The JobServiceManager is the default view on a station’s JobService. It provides a table listing of up
to the last 10 Jobs executed by the station since the last station start. Order is oldest job at top, most
recent job at bottom.
To see details on any job, click the “>>” button next to its status descriptor. A popup Job Log dialog
displays all the interim steps about the job, including timestamps and relevant messages.
To dispose of any job, click the close (“X”) button to remove it from the station.
Note: Only the last ten jobs are saved. All jobs in a station are cleared upon a station restart.
workbench-LinkSheet
The LinkSheet allows you to view and delete links. It provides a view of the links on a Component.
LinkSheet Main Menu The Workbench main menu functions are available. When the LinkSheet is
visible, the following LinkSheet menu functions are also available:
• Delete Links
• GoTo
LinkSheet Toolbar The Workbench toolbar contains navigation and editing buttons as described in
“About the toolbar” on page 2-12. When the LinkSheet is visible, additional toolbar buttons include:
• Delete Links
GoTo Go To goes to the selected item.
workbench-ModuleSpaceView
The ModuleSpaceView allows you to view Modules.
OptionsButton The Options Button provides the ability to toggle columns on and off like Mozilla
does.
workbench-NavContainerView
NavContainerView is a default listing of nav children.
workbench-NavFileEditor
The NavFileEditor allows you to view and edit Nav Files. It provides a view of the Pages in the station
and a view of the Nav Tree. You can drag Pages to the Nav Tree to add them to the Nav File. The
name and Ord are shown at the bottom of the window.

NiagaraAX-3.x
14-55
User Guide
Plugins in workbench module Chapter 14 – Plugin Guides
May 1, 2007

In order to use the Nav File, you must place the filename in the Default Nav File property of the
WebService.
workbench-PropertySheet
The Property Sheet shows all the user visible Properties of the Component. This view also lets you
change any Properties that you have authority to change. It can be used on a Component of a running
Station or a Component in a Bog File.
In order to see Properties of Components in the PropertySheet, press the + sign to expand the
Component.
When you want to enter a URL, you can Copy the Component or URL and Paste it into the Property-
Sheet using the Paste shortcut Ctrl + V.
When a Property has been changed, its symbol will become red until you press Save.
PropertySheet Menus The Workbench main menu functions are available. If you Right-click any
Component in the PropertySheet, you can choose from the following:
• Views - show the view menu for the Component.
• Actions - Perform any of the Actions on the Component.
• Cut Ctrl + X
• Copy Ctrl + C
• Paste Ctrl + V
• Duplicate Ctrl + D
• Delete Delete
• Rename
• Reorder
• Config Flags
PropertySheet Toolbar The Workbench toolbar contains navigation and editing buttons as
described in “About the toolbar” on page 2-12.
Config Flags Configure Flags on a component. This is available on Properties. Right-click a
Property to view the Config Flags Dialog.
Links Links provide the mechanism to dynamically attach Components. They allow you to attach
an output Property of one Component to an input Property of another Component. The links are
visible in the Property Sheet of the Component. Links show whether they are direct or indirect and their
source Property.
In order to view the Properties of the link, Left-click the + plus sign on the Component to expand it.
Each link shows the following:
• Link Type and source
• Source Ref - This is the linked Component.
• Source Slot Name - This is the linked Component's property.
• Target Slot Name - This is the current Component's property.
• Enabled - This shows whether the link is currently enabled.
See for more information on creating links.
OrdChooser In order to select an Ord instead of typing it, you can use one of the Ord editors. They
include:
• Bql Builder
• Directory Ord Chooser
• File Ord Chooser
• History Ord Chooser
• Ref Chooser
Once you have selected an editor, you can use the button to the right of the selection box. It will
present the selected editor.
workbench:FileOrdChooser In order to select a file Ord instead of typing it, you can use the FileOrd-
Chooser.
You can select FileSpaces, Bookmarks and directories and files. In addition toolbar functions are provided
including:
Back Back moves back to the previous view.
Uplevel Uplevel moves up one level in tree.

NiagaraAX-3.x
14-56
User Guide
Chapter 14 – Plugin Guides Plugins in workbench module
May 1, 2007

Home Home moves up one level in tree.

New Folder New Folder creates a new Directory.
ListView ListView allows you to use the list view.
DetailsView DetailsView allows you to use the details view.
Bookmarks You can press the Bookmarks button to add the selection to Bookmarks.
Show/Hide Preview Show/Hide Preview toggles whether the preview pane is visible.
workbench:DirectoryOrdChooser In order to select a Directory Ord instead of typing it, you can
use the DirectoryOrdChooser.
You can select FileSpaces, Bookmarks and directories. In addition toolbar functions are provided
including:
New Folder New Folder creates a new Directory.
Bookmarks You can press the Bookmarks button to add the selection to Bookmarks.
workbench:HistoryOrdChooser In order to select a reference Ord instead of typing it, you can use the
HistoryOrdChooser.
You can select items from the tree by type slot or Handle.
workbench:RefChooser In order to select a reference Ord instead of typing it, you can use the
RefChooser.
You can select items from the tree by type slot or Handle.
workbench:BqlQueryBuilder In order to select a BQL query instead of typing it, you can use the
BqlQueryBuilder.
BQL is one Scheme used to Query in the Niagara Framework. An Ord is made up of one or more Queries.
A Query includes a Scheme and a body. The bql Scheme has a body with one of the following formats:
• BQL expression
• Select projection FROM extent Where predicate
You can create the Ord Qualifier, Select, FROM and Where portions of a Query.
Ord Qualifier In the left window, you can select an Ord to use as the qualifier. It will immediately be
placed in the BQL statement at the top when you select it.
If you select the history Scheme, your options will vary from those shown here.
workbench:ProjectionBuilder In order to build the projection for a BQL request instead of typing it,
you can use the ProjectionBuilder in Bql Builder. You can select an item from the center window to use
with the select statement. Press the right arrow to add each one to the projection.
Bql Expressions" An expression can be one of the following:
• field like displayName
• x.y.z
• any method that returns non-void and takes zero parameters
After you build the BQL statement, you can remove the "Select" to provide a BQL expression instead of
a Select statement.
workbench:ExtentBuilder An extent can be one or more of the following:
• "*" all available from the target
• all property slots
• all methods that return non-void and take zero parameters
In order to build the Extent for a BQL request instead of typing it, you can use the ExtentBuilder in Bql
Builder. You can select the Restrict Type and choose the module and item to use with the FROM
clause. It will immediately appear in the BQL statement at the top.
This also changes the items that are available in the projection.
If you choose a history Scheme, the ExtendBuilder will provide different selections. The extent for a
History typically can be one of the following:
• "from /demo/Float" where demo is the station name
• "from !Float" where "!" signifies the current station
workbench:QualifierBuilder In order to build the Qualifier for a BQL request, you can type it in the
QualifierBuilder in Bql Builder. As you type, it will immediately appear in the BQL statement at the top.

NiagaraAX-3.x
14-57
User Guide
Plugins in workbench module Chapter 14 – Plugin Guides
May 1, 2007

Edit Facets Edit Facets allows viewing and editing of facets. In order to change facets, you use the
button to the right of the facets. It will present the Edit Facets dialog box.
From here you can Add, Remove or select the Enum Range Dialog.
Add Add allows you to add a Key and Type.
Remove Remove allows you to remove facets.
Enum Range Dialog In order to view or set the range of values for a Enum, you can use the . It will
present the Enum Range Dialog:
You can enter one of the standard Enumerations in the field under the Use Enum Type in Range
(module:name).
Press Use Enum Type in Range (module:name) to use the Enumeration that you entered. In
order to enter or change an Enumeration, enter the Ordinal in the field above the Add button. Next enter
the new value for the Tag and press Modify. Press OK to complete the dialog.
workbench-SlotSheet
The Slot Sheet shows all the user visible slots of the Component. This includes Properties,
Actions, and Topics.
The SlotSheet is a Table that shows the following for each slot:
• Slot
• #
• Name
• Display Name
• Definition
• flags
• Type
The SlotSheet also optionally shows any Name Maps. The SlotSheet includes the following menus:
• SlotSheet Main Menu
• SlotSheet Component Menu
SlotSheet Main Menu The Workbench main menu functions are available. When the SlotSheet is
visible, the following SlotSheet menu functions are also available:
• Add Slot Ctrl + A
• Rename Slot Ctrl + R
• Config Flags
• Config Facets
• Reorder
• Add Name Map
SlotSheet Component Menu If you Right-click any Component in the SlotSheet or the background,
you can choose from the following:
• Add Slot Ctrl + A
• Copy Ctrl + C
• Delete Delete
• Rename Slot Ctrl + R
• Config Flags
• Config Facets
• Add Name Map
SlotSheet Toolbar The Workbench toolbar contains navigation and editing buttons as described in
“About the toolbar” on page 2-12. When the SlotSheet is visible, additional toolbar buttons include:
• Add Slot
• Rename Slot
• Config Flags
• Reorder
Add Slot Add Slot allows you to add a slot to the Component.
Rename Slot Rename Slot allows you to rename a slot in the Component.
Add Name Map Add Name Map allows you to add a Name Map to the Component. You Right-
click on the Property displayNames to delete or rename Name Map and displayNames_xx to delete or
rename Name Map (xx) where xx is the Language Code.

NiagaraAX-3.x
14-58
User Guide
Chapter 14 – Plugin Guides Plugins in workbench module
May 1, 2007

Config Facets Configure Facets on the Component. This is available on Properties. Right-
click a Property to view the Config Facets Dialog.
workbench-StationSummary
StationSummary is the default view on a Station. It holds primary components (e.g. Config, Files,
History) and shows specific configuration information about the station’s host platform, including:
• Station Name
• Host
• Host Model
• Host Id
• Niagara Version
• Java Version
• OS Version
• Locale
• Current Time
workbench-TextFileEditor
The TextFileEditor Plugin provides a powerful Color coded text editor. It supports Color coding of
C, java and xml file types. See File Types for more information on Color coding of specific file types.
See TextEditorOptions to change editor options including Color coding.
TextFileEditor Menus The Workbench main menu functions are available.
TextFileEditor Toolbar The Workbench toolbar contains navigation and editing buttons as described
in “About the toolbar” on page 2-12.
File Types The TextFileEditor Plugin provides a powerful Color coded text editor. It supports Color
coding of C, java, properties, Python and xml file types. See TextEditorOptions to change editor
options including Color coding.
C Files The TextFileEditor supports special Color coding for C files including:
• Preprocessor - #include
• Line Comment - / comment /
• Multiline Comment - /* comment */
• String literal - "string" and 'string'
• Number literal - '0' and 'F'
• Keyword - blue - if
CSS Files The TextFileEditor supports special Color coding for CSS files including:
• Identifier - HTML element or CSS identifier
• Line Comment - / comment /
• Multiline Comment - /* comment */
• String literal - "string" and 'string'
• Number literal - '0' and 'F'
• Keyword - blue - if
HTML Files The TextFileEditor supports special Color coding for HTML files including:
• Identifier - HTML element
• Multiline Comment - <!-- Comments here -->
• String literal - "string" and 'string'
• Number literal - '0' and 'F'
• Keyword - blue - if
Java Files The TextFileEditor supports special Color coding for Java files including:
• Bracket - ( { [
• Keyword - if
• Line Comment - / comment /
• Multiline Comment - /* comment */
• String literal - "string" and 'string'
• Number literal - '0' and 'F'
JavaScript Files The TextFileEditor supports special Color coding for JavaScript files including:
• Bracket - ( { [
• Keyword - if
• Line Comment - / comment /

NiagaraAX-3.x
14-59
User Guide
Plugins in workbench module Chapter 14 – Plugin Guides
May 1, 2007

• Multiline Comment - /* comment */

• String literal - "string" and 'string'
• Number literal - '0' and 'F'
Properties Files The TextFileEditor supports special Color coding for properties files including:
• Line Comment - #
• Bracket - =
Python Files The TextFileEditor supports special Color coding for Python files including:
• Bracket - {}()[]
• Keyword - if
• Line Comment - #
• String literal - "string" and 'string'
• Number literal - '0' and 'F'
Xml Files The TextFileEditor supports special Color coding for Xml files including:
• Multiline Comment - <!-- comment -->>
• Bracket - < > < >
• String literal - "string" and 'string'
workbench-ServiceManager
Service Manager allows you to view services. It is available on the ServiceContainer.
workbench-WbPxView
PxView is a dynamic view which may be added to Components as a property. PxViews store the view
contents in a PxFile which is an XML file with a PX extension. The view itself is defined as a tree of
bajaui:Widgets.
For more information about Px views, refer to “About Px views” on page 8-2. For more information about
Px view menus, refer to “About the Px Editor menu” on page A-7. Related Px information is available as
listed below:.
• “About Px files” on page 8-3
• “About Px viewer” on page 8-4
• “About Px Editor” on page 8-5
WbPxView Menus The Workbench main menu functions are available. When the Px Viewer is
visible, the following menu functions are also available:
• PxViewer View Source Xml
PxViewer View Source Xml You can view the source XML of a PX Page by selecting View Source Xml
from the main menu.
workbench-WbServiceManagerView
Workbench Service Manager allows you to view services. It is available from the Tools menu.

NiagaraAX-3.x
14-60
User Guide
 CHAPTER A
References

In this appendix (introduction)

This appendix contains the following reference information:
• About keyboard shortcuts
Explains how to use the keyboard to enter menu bar and popup menu commands – without using
the mouse.
• Types of menu bar items
Describes the different menu items available from the menu bar. Refer to “About the menu bar” on
page 2-12 for an overview of the menu bar.
• Types of popup menu items
Describes the popup menus that appear in different views and contexts.
• Types of toolbar icons
Describes the types of icons that are in the toolbar. For an overview of the toolbar, refer to “About
the toolbar” on page 2-12.

About keyboard shortcuts

Workbench provides a number of keyboard shortcuts for common actions. These are performed by
holding down the combination of keys listed. They include:
• F1 - Help On View
• F3 - Console
• F4 - Hide Console
• F5 - searchFind;
• F6 - searchReplace;
• F7 - Goto File
• F8 - searchConsoleNext;
• F9 - Save amp; Compile
• Alt + Left - Back
• Alt + Right - Forward
• Alt + Up - Up Level
• Alt + Home - Home
• Alt + Space - Recent Ords
• Ctrl + A - Add Slot
• Ctrl + C - copyg;
• Ctrl + D - duplicate;
• Ctrl + F - Find Next
• Ctrl + G - Goto Line
• Ctrl + L - Open Ord
• Ctrl + N - New Window
• Ctrl + O - Open File...
• Ctrl + P - Print
• Ctrl + R - Rename Slot
• Ctrl + S - Save
• Ctrl + T - New Tab
• Ctrl + V - paste;
• Ctrl + W - Word Wrap

NiagaraAX-3.x
A–1
User Guide
Types of menu bar items Chapter A – References
About the File menu May 1, 2007

• Ctrl + X - cut;
• Ctrl + Z - undo;
• Ctrl + F1 - Find Bajadoc
• Ctrl + F4 - Active Plugin
• Ctrl + F5 - searchFindFiles;
• Ctrl + F6 - searchReplaceFiles;
• Ctrl + F9 - Compile
• Ctrl + PageUp - Next Tab
• Ctrl + PageDown - Previous Tab
• Shift + F8 - searchConsolePrev;
• Ctrl + Shift + F - searchFindPrev;
• Ctrl + Alt + Z - redo;

Types of menu bar items

This section describes the menu items that appear in the Workbench menu bar:
• File menu
See “About the File menu” on page A-2
• Edit menu
See “About the Edit menu” on page A-4
• Search menu
See “About the Search menu” on page A-5
• Bookmarks menu
See “About the Bookmarks menu” on page A-6
• Tools menu
See “About the Tools menu” on page A-6
• Window menu
See “About the Window menu” on page A-6
• Px Editor menu
See “About the Px Editor menu” on page A-7
• History Ext Manager menu
See “About the History Ext Manager menu” on page A-8
• Help menu
See “About the Help menu” on page A-8

About the File menu

The File menu in the menu bar has the following options:
The File menu in the menu bar provides the following options:
• Open Ord
You may open a ORD by selecting File > Open > Open Ord from the main menu or from the
toolbar open button.
The Ord Chooser also allows you to directly type the Ord of a location in order to go there. If no view
is specified, the default view for the item will be presented. You may also paste an Ord instead of typ-
ing it by pressing the paste shortcut Ctrl + V after you have copied a node or Ord into the clipboard.
• Open File
You may open a file by selecting File > Open > Open File... from the main menu.
• Open Directory
You may open a Directory by selecting File > Open > Open Directory... from the main
menu.
• Open Station (Fox)
You may open a Station by selecting File > Open > Open Station (Fox)... from the
main menu. This will cause the following popup window to be presented so that you can complete
each field.
Address - This is the address of the computer running the Station that you wish to access.
User name - This is the user name given to you by your system administrator.
Password - This is the password given to you by your system administrator.
Remember these credentials - This will save this connection in your connection list.
Once you successfully connect to the Station, it will appear in the tree and your home page will be
displayed.
If you will be away from the system, you should close the Station to prevent unauthorized access.

NiagaraAX-3.x
A-2
User Guide
Chapter A – References Types of menu bar items
May 1, 2007 About the File menu

• Open Platform
You may open a Platform by selecting File > Open > Open Platform... from the main
menu. This will cause the following popup window to be presented so that you can complete each
field.
Host - This is the address of the computer running the Platform that you wish to access.
Port - This is the port used.
Password - This is the password given to you by your system administrator.
Remember these credentials - This will save this connection in your connection list.
Once you successfully connect to the Platform, it will appear in the tree and the available tools will
be displayed.
• Find Stations
You may find Stations by selecting File > Open > Find Stations... from the main menu.
This command finds all the stations running on the network. It will search for 5 seconds, then display
a Table of all the stations found. You may display additional columns about each station using the
options button (on the right of the header). Double-click a Station to open a Fox connection to it.
• Back
Back allows you to go to the previous view. The shortcut is Alt + Left.
• Forward
Forward allows you to go to the next view. You must have used the Back command previously.
The shortcut is Alt + Right.
• Up Level
Up Level allows you to go to the next level up. The shortcut is Alt + Up.
• Save
Saves the value of the Component.
• Save Bog
Save the Component changes to the Bog File file.
• Save All
Save all open views. This saves all Tabs when browsing with multiple Tabs.
• Recent Ords
Recent Ords allows you to see recent Ords. The shortcut is Alt + Space.
• Refresh
Refresh allows you to refresh the current view.
• Home
Home allows you to go to the home view. The shortcut is Alt + Home.
• Printing
Printing provides the capability to print the current view. When it appears dimmed, printing is not
available.
• Export
Export provides the capability to Export the current view. When it appears dimmed, Export is not
available.
• Logging off the System
You may exit the system by a number of means. You may Close the session, Close All sessions,
Exit, or Close the current window. Each of these causes different actions and should be under-
stood.
• Close Session
You may logoff the Station at any time by selecting File > Close from the main menu.
Once you successfully close a session, it will be removed from the tree. This could leave a user inter-
face running without an open session.
• Disconnect
You may logoff the system at any time by Right-clicking the connected system in the tree and select
Disconnect. This allows you to close a session with a Station without removing it from the tree.
• Dismiss
You may logoff a connected system at any time by Right-clicking the connected system in the tree
and select Dismiss. This allows you to close a session with a Station and remove it from the tree.
• Exiting the System
You may exit the system at any time by selecting File > Exit from the main menu. This differs
from logoff in that it also causes the user interface to stop.
• Close the Current Window
You may close the current window at any time, if it is not the primary window, by any of the follow-
ing methods:
• selecting File > Close from the main menu
• pressing the box in the top left corner and selecting Close from the menu

NiagaraAX-3.x
A-3
User Guide
Types of menu bar items Chapter A – References
About the Edit menu May 1, 2007

• pressing the close icon in the top right corner of the window
• New Window
New Window requests that a new window be created identical to the current one. This allows you
to view multiple views concurrently.
• New Tab
New Tab requests that a new tab be created identical to the current one. This allows you to view
multiple views in the same Window. You can hold down the Ctrl key during a Double-click to hy-
perlink into a new tab. You can also Right-click to get a popup menu on tabs to close the tab, or close
all other tabs.
• Close Tab
Close Tab requests that a tab be closed.
• Close Other Tabs
Close Other Tabs requests that all other tabs be closed.
• Next Tab
Next Tab selects the next tab. The shortcut is Ctrl + PageUp.
• Previous Tab
Previous Tab selects the previous tab. The shortcut is Ctrl + PageDown.

About the Edit menu

• Cut
Cut copies the current Selection to the clipboard and changes its Color to gray until a Paste is per-
formed to delete it. If the Selection is a string, Cut makes a Copy of the current text selection and
places it in the clipboard and removes it from the current string. It is may be accessed by selecting
an item and:
• Right-clicking the item(s) and choosing Cut.
• Right-click in the tree and choosing Cut.
• In the Wire Sheet press the Cut toolbar icon.
• In the Wire Sheet select Edit > Cut from the main menu.
• pressing the shortcut key Ctrl + X (hold down Ctrl and press X) when in a window other than
the main browser window.
You can use Drag to Cut and Paste in one operation.
• Copy
Copy copies the current contents of the clipboard to the destination component as a set of new dy-
namic properties. If the Selection is a string, Copy makes a copy of the current text Selection and
places it in the clipboard. To Copy a Component, do any of the following:
• Right-click a Component in a view or tree and choose Copy
• Right-click the background in the Wire Sheet choosing Copy
• In the Wire Sheet press the Copy toolbar button.
• In the Wire Sheet select Edit > Copy from the main menu
• pressing the shortcut key Ctrl + C (hold down Ctrl and press C) when in a window other than
the main browser window.
You can copy a selected group of Components in the Wire Sheet.
You can use Drag to Copy also.
In order to Copy a Component, you must Copy it from the Palette or an existing Database. You can
follow one the following steps:
• In the Palette Sidebar, expand a module (like control) and sub-directory (like Points), Right-
click on a Component (like BooleanWritable) and select Copy.
• In the namespaces sidebar (tree), expand System, Modules, a module (like control), Files, mod-
ule.palette, and sub-directory (like Points), Right-click on a Component (like BooleanWritable)
and select Copy.
• OR Right-click on a Component that you want to Copy from a Wire Sheet, Property Sheet or
the tree and select Copy.
• Paste
Paste copies the contents of the clipboard to the destination Component as a set of new dynamic
properties. If the target is a string, Paste places a reference to the source that was cut or copied into
clipboard. It may be accessed by cutting or copying item(s) and:
• Right-clicking the item and choosing Paste
• Right-click in the tree and choosing Paste
• In the Wire Sheet press the Paste toolbar icon.
• In the Wire Sheet select Edit > Paste from the main menu
• pressing the shortcut key Ctrl + V (hold down Ctrl and press V) when in a window other than

NiagaraAX-3.x
A-4
User Guide
Chapter A – References Types of menu bar items
May 1, 2007 About the Search menu

the main browser window.

You can use Drag to Cut and Paste in one operation.
You can add a Component to a running Station or an offline Bog File file. You can do this using any
of the following:
• In the Wire Sheet, Right-click on the background and select Paste to add the new Component.
The new Component is created and is selected.
• In the tree, Right-click on a Container and select Paste to add the new Component inside the
Container.
See the Bajadoc Index for reference information. If you select Help > Guide On Target with
a Component selected, you will get the Guide for that Component. If you select Help > Bajadoc
On Target with a Component selected, you will get the bajadoc for that Component. The Bool-
eanWritable bajadoc is at module://control/doc/javax/baja/control/BBooleanWritable.bajadoc.
• Paste Special
Paste Special copies the contents of the clipboard to the destination Component when it is a Special
Transferable.
• Duplicate
Duplicate copies the current Selection and places a duplicate in the same Container. This function
may be access from the menu under Edit (shortcut Ctrl + D) or from the toolbar.
• Delete
Delete removes the current Selection from its parent Container. It may be accessed by selecting an
item and:
• Right-clicking the item(s) and choosing Delete
• Right-click in the tree and choosing Delete
• In the Wire Sheet press the Delete toolbar button.
• In the Wire Sheet select Edit > Delete from the main menu
• Undo
This reverses the last Action as if it had not been performed. It is only available for certain actions
such as:
• Paste Component
• Cut Component
• link
• Delete Links
• Redo
This restores an Action after Undo has removed it. It is only available after a successful Undo.

About the Search menu

The Search menu in the menu bar has the following options:
• Find
Find allows you to search in the file for the selected string. You can Match Case or Match Word.
The shortcut is F5.
• Find Next
Find Next allows you to find the next occurrence of the selected string. The shortcut is Ctrl + F
(hold down Ctrl and press F).
• Find Prev
Find Prev allows you to find the previous occurrence of the selected string. The shortcut is Ctrl +
Shift + F (hold down Ctrl and Shift and press F).
• Replace
Replace allows you to replace the next occurrence in the file. The shortcut is Ctrl + R (hold down
Ctrl and press R).
• Goto Line
Goto Line allows you to go to a line number in the file. The shortcut is Ctrl + G (hold down Ctrl and
press G).
• Goto File
Goto File allows you to go to a file. The shortcut is Ctrl + F3 (hold down Ctrl and press F3).
• Find Files
Find In Files allows you to find the all occurrences of a string in files. You can Match Case or
Match Word. You can choose Files to Find. You can select a Folder. You can choose wheth-
er to Search subfolders.
• Replace Files
Replace Files allows you to replace the all occurrences in the files.

NiagaraAX-3.x
A-5
User Guide
Types of menu bar items Chapter A – References
About the Bookmarks menu May 1, 2007

• Console Prev
Console Prev allows you to go to the previous console error. The shortcut is F7.
• Console Next
Console Next allows you to go to the next console error. The shortcut is F8.

About the Bookmarks menu

The Bookmarks menu in the menu bar has the following options:
• AddTo Bookmarks
You may add a Bookmark by selecting Bookmarks > Add to Bookmarks from the main menu.
• Manage Bookmarks
You may manage Bookmarks by selecting Bookmarks > Manage Bookmarks from the main
menu.
• Bookmarks Go Into
You may select Bookmarks by selecting Bookmarks > Go Into from the main menu.
• Bookmarks File
You may select Bookmarks by selecting Bookmarks > File from the main menu.

About the Tools menu

The Tools menu in the menu bar has the following options:
• Viewing and Changing the Options
The Options allow you to customize the framework for the way you use it. It can be selected from
the main Menu by selecting Tools > Options. It includes the following:
• General
• Lexicon
• Text Editor
• Wire sheet
• ColorChooser
The ColorChooser allows you to choose Colors.
• New Module Wizard
The New Module Wizard allows you to build a new Module. It can be selected from the main
Menu by selecting Tools > New Module.
• New Station Wizard
The New Station Wizard allows you to build a new station Database. It can be selected from
the main Menu by selecting Tools > New Station.
You must enter a Station Name. You can also choose whether this is a JACE Station or a Su-
pervisor Station. Press Next to proceed. Next you should enter an Admin Password.
You can also change the Fox Port and HTTP Port. Press Finish to proceed. You are then
presented a view of your newly created Station at local:|file:!stations/stationname/
config.bog|bog:|slot:/.
• Manage Credentials
Manage Credentials is available in the main Tools menu by selecting Manage Creden-
tials.... You can Reset or Remove selected Credentials or Remove All Credentials. You
can also Open selected Credentials.
• Request License
Request License is available in the main Tools menu by selecting Request License.... You
can request a license by submitting the form.

About the Window menu

The Window menu in the menu bar has the following options:
• Side Bars
• Show Side Bar
You can choose whether to have Side Bars by selecting Window > Side Bars > Show
Side Bar from the main menu.
For more information about the side bar refer to “About the side bar panes” on page 2-2.
• Bookmarks
You can choose to show the Bookmarks Side Bar by selecting Window > Side Bars >
Bookmarks from the main menu.
For more information about the Bookmarks side bar refer to “About the bookmark side bar” on
page 2-4.
• Help Sidebar

NiagaraAX-3.x
A-6
User Guide
Chapter A – References Types of menu bar items
May 1, 2007 About the Px Editor menu

The typical configuration provides a Help Sidebar frame in the left side of the main window.
If it is not open, you can choose to display the Help Side Bar by selecting Window > Side
Bars > Help from the main menu.
Initially, the Help Sidebar is empty until you press Load Help.
Load Help will reappear any time any Module's timestamp is changed or a new Mod-
ule is added or removed. Load Help searches through all the available Modules to cre-
ate the help Directory. The Help Sidebar provides a view of the available Help.
For more information about the Help Sidebar refer to “About the help side bar” on page 2-4.
• Jobs Sidebar
The Jobs SideBar shows all the current jobs in all the stations with which you have a connec-
tion. Controls are provided to allow you to view a job log or dismiss a completed job.
For more information about the Jobs side bar refer to “About the jobs side bar” on page 2-8.
• Nav
You can choose to show the Nav side bar by selecting Window > Side Bars > Nav from
the main menu.
For more information about the Nav side bar refer to “About the nav side bar” on page 2-5.
• Palette
You can choose to show the Palette Side Bar by selecting Window > Side Bars > Pal-
ette from the main menu.
For more information about the Palette side bar refer to “About the palette side bar” on page 2-
7.
• PathBar Uses NavFile
You can toggle this option ON or OFF by selecting Window > Side Bars > PathBar Uses
NavFile. When ON, the PathBar (located at the top of the Workbench main window) displays
your current path, as defined by the NavFile (logical path). When OFF (not selected) the PathBar dis-
plays your absolute path regardless of whether it is mapped to the NavFile or not. You must refresh
the view after changing this setting in order to see the PathBar change.
• Active Plugin
The Active Plugin function gives focus to the current view. From the main menu you can select
Window > Active Plugin or use the shortcut Ctrl + F4. It is very useful to use F3/Ctrl + F4 to
toggle between the Console and the Text File Editor.
• Hide Console
You can hide the console by selecting Window > Hide Console from the main menu or using
the shortcut Ctrl + F2.
• Console
The Console provides the capability to issue console commands directly. From the main menu you
can select Window and Console (F3) or Hide Console (F4) to determine if the console is visible.
Refer to “Types of console commands” on page A-15 for information about console commands.

About the Px Editor menu

The Px Editor menu appears in the menu bar when Px Editor is the active view. The Px Editor has the
following context–sensitive options:
• Toggle View/Edit Mode
This command toggles the active view between Px Editor (for editing) and Px View (view only). If
there are unsaved changes in your Px file, you are prompted to save before switching from Px Editor
to Px View.
• View Source Xml
Selecting this command displays the px source file in a separate read–only window.
• Go to Source Xml
Selecting this opens the px source (xml) file directly in the text file editor. Files can be edited and
saved using the editor.
• Grid
This command toggles the grid display on and off.
• Snap
This command toggles the snap–to–grid feature on and off.
• Show Hatch
This command toggles the hatching pattern visibility on and off. When hatching is on, dim angular
lines (hatching pattern) displays on objects to make them more visibly distinct.
• Set Target Media
This command is available when you are editing a Px file directly in the Px Editor–not when you are
editing the Px file as a view of a component. When selected, this command displays the Set Tar-

NiagaraAX-3.x
A-7
User Guide
Types of popup menu items Chapter A – References
About the History Ext Manager menu May 1, 2007

get Media dialog box to allow you to choose your expected media viewer (HTML Px Media or
Workbench Px Media). See “About presentation media” on page 1-14 for more details about media
types.

About the History Ext Manager menu

The History Ext Manager menu appears in the menu bar when History Extension Manager is the
active view. The History Ext Manager menu has the following options:
• Enable Collection
Select this menu item to enable (start the collection process) for the selected entries.
• Disable Collection
Select this menu item to disable (stop the collection process) for the selected entries.
• Rename History
Select this menu item to rename the selected history. This menu item displays the Set History Name
dialog box.

About the Help menu

The Help menu in the menu bar has the following options:
• Help Contents Index
The help contents provides a common point of access to all system documentation. It is accessed by
selecting Help > Contents Index from the menu or pressing the Help button on the toolbar
to see the Help Index.
• Help On View
This provides help for the current Plugin. It is accessed by selecting Help > On View from the
menu with the Plugin in use.
• Help Guide On Target
This provides context sensitive help for Components. It is accessed by selecting Help > Guide
On Target from the menu when the current view is a view of a Component. It is also available by
Right-clicking a Component and choosing Views > Guide Help.
• Help Bajadoc On Target
This provides context sensitive Bajadoc help for Components. It is accessed by selecting Help >
Bajadoc On Target from the menu when the current view is a view of a Component. It is also
available by Right-clicking a Component and choosing Views > Bajadoc Help.
• Help Find Bajadoc
This is accessed by selecting Help > Find Bajadoc from the menu. It searches for the requested
bajadoc.
• Help About
This is accessed by selecting Help > About from the menu. It provides the software release and
license information.

Types of popup menu items

Workbench provides view–specific, or context–specific commands for editing components in many of
the views. Following, is a list of the standard Workbench popup (right–click) menus.
• Nav side bar
For descriptions of the popup menu items that are available in the nav side bar refer to “About the
nav side bar popup menu items” on page A-9.
• Wire sheet
For descriptions of the wire sheet popup menu items, refer to “About the wire sheet popup menu
items” on page A-9
• Property sheet
For descriptions of the property sheet popup menu items, refer to “About the property sheet popup
menu items” on page A-10.
• Px Editor
For descriptions of the “About the Px Editor popup menu items” on page A-10.
• History extension manager
For descriptions of the “About the history extension manager popup menu items” on page A-11.
• Todo list
For descriptions of the “About the Todo list popup menu items” on page A-11.
• Point Manager
For descriptions of the “About the point manager popup menu items” on page A-11.

NiagaraAX-3.x
A-8
User Guide
Chapter A – References Types of popup menu items
May 1, 2007 About the nav side bar popup menu items

About the nav side bar popup menu items

The nav sidebar provides a tree–type hierarchical view of the system. For an overview of the nav side
bar, refer to “About the nav side bar” on page 2-5.
The nav side bar menu is the popup menu that displays command options when you right–click on a
component item in the nav side bar. The nav side bar menu has the following options:
• Views
Goes to any of the views of the selected component.
• Actions
Perform any available actions on the component.
• New
Create a new item of standard types.
• Cut
See “Types of edit commands” on page A-12.
• Copy
See “Types of edit commands” on page A-12.
• Paste
See “Types of edit commands” on page A-12.
• Duplicate
See “Types of edit commands” on page A-12.
• Delete
See “Types of edit commands” on page A-12.
• Find
This menu item displays the Component Finder dialog box.
• Link Mark
This menu item sets a selected point to your popup menu, making it temporarily available for “Link-
ing From” or Linking To” other points.
• Link From
This menu item allows you to link a selected point to another point that has been marked, using
Link Mark from the popup menu.
• Link To
This menu item allows you to link a selected point to another point that has been marked, using
Link Mark from the popup menu.
• Rename
Select this menu item to rename the selected point. This menu item displays the Set Point Name di-
alog box. You can only rename one point at a time.
• Reorder
This menu item displays the Reorder Points dialog box, which provides the following com-
mands for reordering points within the selected parent component.
• Move Up
• Move Down
• Sort by Name
• Sort by Type
• Reset
• Composite
This menu item displays the Composite Editor dialog box.
• Refresh
This menu item updates the display of the currently active view.
• Go Into
Go Into allows you to re-root the nav tree at any arbitrary node. Right-click the node and select the
"Go Into" command. This will make that node the new root of the tree. All the nodes you have "gone
into" are persistently saved as a special type of Bookmark. Use the pulldown to switch between them.
This feature is quite handy when working with multiple Stations or deep File systems and Databases.

About the wire sheet popup menu items

Most of the wire sheet menu commands are described in “About the nav side bar popup menu items”.
Following are wire sheet specific popup menu options:
• Arrange
Provides options for aligning components on the wire sheet in order to make them easier to view:
• Arrange All
Redistributes the layout of all components on the wire sheet.

NiagaraAX-3.x
A-9
User Guide
Types of popup menu items Chapter A – References
About the property sheet popup menu items May 1, 2007

• Arrange Selection
Redistributes the layout of all selected components on the wire sheet.
• Select all
Selects all components on the active wire sheet.

About the property sheet popup menu items

Most of the property sheet menu commands are described in
“About the nav side bar popup menu items”. Following are wire sheet specific popup menu options:
• Config flags

About the Px Editor popup menu items

The Px Editor popup menu displays when you right-click on an object in the Px Editor view. The menu
commands are dimmed or available, depending on the type of object that you select.
The following menu commands are on the Px Editor popup menu:
• New (refer to “About the Edit menu” on page A-4)
• Cut Ctrl + X (refer to “About the Edit menu” on page A-4)
• Copy Ctrl + C (refer to “About the Edit menu” on page A-4)
• Paste Ctrl + V (refer to “About the Edit menu” on page A-4)
• Duplicate Ctrl + D (refer to “About the Edit menu” on page A-4)
• Delete Delete (refer to “About the Edit menu” on page A-4)
• Edit Properties... (refer to “About the properties side bar” on page 2-10)
• Align > Left
This command is available when you select two or more objects in the Px Editor. Choose the Left
command to align the left edges of two or more objects along a vertical line.
• Align > Right
This command is available when you select two or more objects in the Px Editor. Choose the Right
command to align the right edges of two or more objects along a vertical line.
• Align > Top
This command is available when you select two or more objects in the Px Editor. Choose the Top
command to align the top edges of two or more objects along a horizontal line.
• Align > Bottom
This command is available when you select two or more objects in the Px Editor. Choose the Bot-
tom command to align the bottom edges of two or more objects along a horizontal line.
• Reorder > To Top
This command is available when you select one or more objects in the Px Editor. Choose the
To Top command to move the selected object to the top position (inside its parent object) in the
Widget Tree. This command will place the object in front (with respect to the view pane, or z-axis)
of all other objects in the parent object, but will not move the object out of its parent object.
• Reorder > Up
This command is available when you select one or more objects in the Px Editor. Choose the Up
command to move the selected object one position higher in the Widget Tree and forward one po-
sition in the view pane. This command will not move the object out of its parent object.
• Reorder > Down
This command is available when you select one or more objects in the Px Editor. Choose the Down
command to move the selected object one position lower in the Widget Tree and back one position
in the view pane. This command will not move the object out of its parent object.
• Reorder > To Bottom
This command is available when you select one or more objects in the Px Editor. Choose the
To Bottom command to move the selected object to the bottom position (inside its parent object)
in the Widget Tree. This command will place the object behind (with respect to the view pane, or z-
axis) all other objects in the parent object, but will not move the object out of its parent object.
• Border > Add Border
This command is available when you select one or more objects in the Px Editor. Choose the Add
Border command to wrap selected object(s) with a border pane. Each selection is wrapped in a sep-
arate border pane.
• Border > Remove Border
This command is available when you select one or more border panes in the Px Editor. Choose the
Remove Border command to delete selected border pane(s).

NiagaraAX-3.x
A-10
User Guide
Chapter A – References Types of popup menu items
May 1, 2007 About the history extension manager popup menu items

About the history extension manager popup menu items

The history extension manager popup menu has the following items:
• Views
This menu item provides a submenu that lists all the available views of the history extension man-
ager.
• Actions > Update History Id
This menu item provides a way to refresh the History Id after a rename. It applies the formatting
property of the Name Format field to the Id of the history config Id. See “About history names” on
page 6-17 for more information about history naming.
• Go To Point
This menu item displays the property sheet view of the point associated with the selected entry.
• Go To History
This menu item displays the default view of the history associated with the selected entry.
• Enable Collection
Select this menu item to enable (start the collection process) for the selected entries.
• Disable Collection
Select this menu item to disable (stop the collection process) for the selected entries.
• Rename History
Select this menu item to rename the selected history. This menu item displays the Set History Name
dialog box. You can only rename one history at a time.
Refer to “About the History Ext Manager menu” on page A-8 for information about the History Ext
Manager menu. Refer to “About the history extension manager” on page 6-3 for general information
about the history extension manager view.

About the Todo list popup menu items

The Todo list popup menu has the following items:
• Add
This menu item opens the Add dialog box, when clicked. Use this menu item to add a new item to
your Todo checklist and assign a Summary and Group to the item. This menu item is available even
if no items are selected.
• Mark Complete
This menu item, when clicked, dims and lines-through the selected item(s) in the Todo list so that
the item(s) appears to be “crossed off” the list. If an item is already marked complete and this menu
item is selected, the item will be restored to its “unmarked” state. With no items selected, this menu
item is dimmed (unavailable).
• Edit
Displays the Edit dialog box, when clicked, allowing you to change the Summary and the Group
fields associated with the item.
• Move to Top
Moves the selected item to the top of the list.
• Move Up
Moves the selected item up in the list, one increment per click.
• Move Down
Moves the selected item down in the list, one increment per click.
• Move to Bottom
Moves the selected item to the bottom of the list.
• Remove
Displays a “Remove selected items?” prompt, when clicked; deletes selected items when the prompt
is affirmed.
Refer to “Todo list” on page 11-10 for general information about the Todo list view.

About the point manager popup menu items

The point manager popup menu has the following items:
• Views
This menu item provides a submenu that lists all the available views of the point manager. These
same views are available from the view selector menu (see “About the view selector” on page 2-14)
when the point extension manager is the active view.
• Actions
This menu item allows you to perform any available actions on the component. For example, write
to a “writable” point.

NiagaraAX-3.x
A-11
User Guide
Types of edit commands Chapter A – References
About the point manager popup menu items May 1, 2007

• New
This menu item allows you to add a new component to the points manager. Valid options are pre-
sented in the submenu.
• Cut
See “Types of edit commands” on page A-12.
• Copy
See “Types of edit commands” on page A-12.
• Paste
See “Types of edit commands” on page A-12.
• Duplicate
See “Types of edit commands” on page A-12.
• Delete
See “Types of edit commands” on page A-12.
• Find
This menu item displays the Component Finder dialog box.
• Link Mark
This menu item sets a selected point to your popup menu, making it temporarily available for “Link-
ing From” or Linking To” other points.
• Link From
This menu item allows you to link a selected point to another point that has been marked, using
Link Mark from the popup menu.
• Link To
This menu item allows you to link a selected point to another point that has been marked, using
Link Mark from the popup menu.
• Rename
Select this menu item to rename the selected point. This menu item displays the Set Point Name di-
alog box. You can only rename one point at a time.
• Reorder
This menu item displays the Reorder Points dialog box, which provides the following com-
mands for reordering points within the selected parent component.
• Move Up
• Move Down
• Sort by Name
• Sort by Type
• Reset
• Composite
This menu item displays the Composite Editor dialog box.
• New Folder
This menu item allows you to add and name a new points folder.
• New
This menu item allows you to add and name a new point.
• Edit
This menu item displays the Point Editor dialog box.
Refer to “About the Point Manager” on page 4-28 for general information about the point manager view.

Types of edit commands

In addition to view–specific editing tools, Workbench provides commands for editing components in
many of the views. Following, is a list of descriptions of the standard commands that are available in
Workbench views for editing components.
• Drag
Dragging files or components only works within a single Workbench application. However, it is pos-
sible to drag files from Windows Explorer into the Workbench to see the default view. Dragging a
component or file using the left mouse button performs a Copy operation. Dragging a component
or file using the right mouse button always prompts you for a Copy, Move, or Cancel command
selection.
• Cut
Use the Cut command to delete the selected object and send it to the clipboard.
• Copy
Use the Copy to send the selected object to the clipboard without deleting it.

NiagaraAX-3.x
A-12
User Guide
Chapter A – References Types of toolbar icons
May 1, 2007 Standard toolbar icons

• Paste
Use the Paste command to copy the current contents of the clipboard to the destination as a set of
new dynamic properties.
• Duplicate
Use duplicate to create a copy of the current selection in the same container as the selection.
• Delete
Use the Delete command to remove a selected item from its parent container.
• Undo
Use the Undo command to reverse the previous command. Undo is only available for certain com-
mands, such as, Paste, Cut, Delete, and the Link action.
• Redo
Use the Redo command to restore a command–action after the Undo command has removed it.
• Rename
Use Rename to change the name of a Component.

Types of toolbar icons

For an overview of the Workbench toolbar, refer to “About the toolbar” on page 2-12.
Some icons are always visible as you navigate through the system. Additional icons may be added and
removed from view when different views are active. When icons appear dimmed, their functions are
unavailable. Icons that appear on the toolbar are grouped in the following categories:
• Standard toolbar icons
These icons may be dimmed (or unavailable in certain views) but they are always present on the tool-
bar. Refer to “Standard toolbar icons” on page A-13 for the listing of Standard toolbar icons.
• Slot sheet toolbar icons
These icons appear only when the Slot Sheet is active. Refer to “Slot Sheet toolbar icons” on page A-
14 for the listing of Slot Sheet toolbar icons.
• Px Editor toolbar icons
These icons appear only when the Px Editor or Px Viewer is active. Refer to “Px Editor toolbar icons”
on page A-14 for the listing of Px Editor toolbar icons.
• History extension manager toolbar icons
These icons appear when the History Editor view is active. Refer to “About the history extension
manager toolbar icons” on page A-14 for the listing of History Editor toolbar icons.
• History Editor toolbar icons
These icons appear when the History Editor view is active. Refer to “About the history editor toolbar
icons” on page A-15 for the listing of History Editor toolbar icons.
• Todo list toolbar icons
These icons appear when the Todo list view is active. Refer to “About the Todo list toolbar icons” on
page A-15 for the listing of Todo list toolbar icons.

Standard toolbar icons

For an overview description of the toolbar, refer to “About the toolbar” on page 2-12. Following are the
icons that appear in all views:
• Back. See “Back” on page A-3 for details about the Back function.
• Forward. See “Forward” on page A-3 for details about the Forward function.
• Up Level. See “Up Level” on page A-3 for details about the Up Level function.
• Recent Ords. See “Recent Ords” on page A-3 for details about the Recent Ords function.
• Home. See “Home” on page A-3 for details about the Home function.
• Refresh. See “Refresh” on page A-3 for details about the Refresh function.
• Left Side Bar. See “Side Bars” on page A-6 for details about the Side Bars function.
• Open. See “About the File menu” on page A-2 for details about all the Open functions.
• Save Ctrl + S. See “Save” on page A-3 for details on the Save function.
• Save Bog. See “Save Bog” on page A-3 for details on the Save Bog function.
• Printing Ctrl + P. See “Printing” on page A-3 for details on the Printing function.
• Cut Ctrl + X. See “Cut” on page A-12 for details on the Cut function.
• Copy Ctrl + C. See “Copy” on page A-12 for details on the Copy function.
• Paste Ctrl + V. See “Paste” on page A-13 for details on the Paste function.
• Duplicate Ctrl + D. See “Duplicate” on page A-13 for details on the Duplicate function.
• Delete Delete. See “Delete” on page A-13 for details on the Delete function.
• Undo Ctrl + Z. See “Undo” on page A-13 for details on the Undo function.

NiagaraAX-3.x
A-13
User Guide
Types of toolbar icons Chapter A – References
Slot Sheet toolbar icons May 1, 2007

• Redo Ctrl + Alt + Z. See “Redo” on page A-13 for details on the Printing function.

Slot Sheet toolbar icons

For an overview description of the toolbar, refer to “About the toolbar” on page 2-12. Following are the
icons that appear when the Slot Sheet view is active:
• Add Slot
Creates a new slot (appearing as a row) on the slot sheet.
• Rename Slot
Displays the Rename Slot dialog box, when clicked. This icon is dimmed when no slot, or more
than one slot is selected in the slot sheet editor view.
• Config Flags
Displays the Config Flags dialog box, when clicked. This icon is dimmed unless one or more
slots are selected in the slot sheet editor view.
• Reorder
Displays the Reorder dialog box, when clicked.

Px Editor toolbar icons

For an overview description of the toolbar, refer to “About the toolbar” on page 2-12. Following are the
icons that appear when the Px Editor is the active view:
• Toggle View/Edit Mode.
Displays, alternately, the Px Editor or the Px Viewer in the view pane. This icon appears inset when
the Px Editor view is active and it appears normal when the Px Viewer is active. See “About Px views”
on page 8-2 for more details about the Px Editor and Px Viewer.
• Right (Px Editor) side bar menu
Displays a dropdown menu of side bar options for the Px Editor. The following options are available:
• Bound Ords
Shows or hides the Bound Ords side bar (refer to “About the bound ords side bar” on page 2-9).
• Widget Tree
Shows or hides the Widget Tree side bar (refer to “About the widget tree side bar” on page 2-9).
• Properties
Shows or hides the Properties side bar (refer to “About the properties side bar” on page 2-10).
• Left align
Aligns left edges of selected objects along a vertical line.
• Right align.
Aligns right edges of selected objects along a vertical line.
• Top align
Aligns top edges of selected objects along a horizontal line.
• Bottom align
Aligns bottom edges of selected objects along a horizontal line.
• To Top
Moves selected objects to the highest position (with regard to z-order) in the parent object.
• To Bottom
Moves selected objects to the lowest position (with regard to z-order) in the parent object.
• Select
Activates the pointer tool used to select objects in the Px Editor view using the mouse.
• Add Polygon
Activates the polygon tool for drawing polygons.
• Add Path
Activates the path tool that allows you to draw bezier curves in the Px Editor view.
• Add Point
Activates the Add Point tool that allows you to add a point to a path or a polygon in the Px Editor
view.
• Delete Point
Activates the Delete Point tool that allows you to remove a point from a path or a polygon in the Px
Editor view.

About the history extension manager toolbar icons

The Workbench toolbar contains navigation and editing buttons as described in About the toolbar.
For an overview description of the history editor view, refer to “About the history extension manager” on
page 6-3. Following, are the icons that appear when the history extension manager view is active:

NiagaraAX-3.x
A-14
User Guide
Chapter A – References Types of console commands
May 1, 2007 About the history editor toolbar icons

• HistoryExtManager Enable Collection

Click this icon to enable (start the collection process) for the selected entries.
• HistoryExtManager Disable Collection
Click this icon to disable (stop the collection process) for the selected entries.
• HistoryExtManager Rename History
Click this icon to rename the selected history. When clicked, the Set History Name dialog box ap-
pears.

About the history editor toolbar icons

For an overview description of the history editor view, refer to “About the history editor view” on page 6-
12. Following are the icons that appear when the history editor view is active:
• Hide
With one or more records selected, this icon is available to set the trend flag of all selected records
to “hidden”. With no records selected, the icon is dimmed (unavailable).
• Unhide
With one or more records selected, this icon is available to set the trend flag of all selected records
to “hidden”. With no records selected, the icon is dimmed (unavailable).
• Filter
Displays the Configure Flags dialog box, when clicked. This icon is available even if no records
are selected.
• Configure Outliers
Displays the Configure Outliers dialog box, when clicked.

About the Todo list toolbar icons

For an overview description of the Todo list view, refer to “Todo list” on page 11-10. Following are the
icons that appear when the Todo list view is active:
• Add
This icon opens the Add dialog box, when clicked. Use this icon to add a new item to your Todo
checklist and assign a Summary and Group to the item. This icon is available even if no items are
selected.
• Mark Complete
This icon, when clicked, dims and lines-through the selected item(s) in the Todo list so that the
item(s) appears to be “crossed off” the list. If the item is already marked as completed and this icon
is selected, the item will be restored to its “unmarked” state. With no items selected, this toolbar icon
is dimmed (unavailable).
• Edit
Displays the Edit dialog box, when clicked, allowing you to change the Summary and the Group
fields associated with the item.
• Move to Top
Moves the selected item to the top of the list.
• Move Up
Moves the selected item up in the list, one increment per click.
• Move Down
Moves the selected item down in the list, one increment per click.
• Move to Bottom
Moves the selected item to the bottom of the list.
• Remove
Displays a “Remove selected items?” prompt, when clicked; deletes selected items when the prompt
is affirmed.

Types of console commands

The following sections provide descriptions of how to use the Workbench console in terms of:
The following types of commands may be typed in from the Workbench console.
• Niagara shell commands
These commands are used at the command line and may be typed in directly. See “Niagara shell
commands” on page A-16:
• nre commands
These commands are used at the command line and may be typed in using the “nre” prefix. See “nre
(station) commands” on page A-16.

NiagaraAX-3.x
A-15
User Guide
Types of console commands Chapter A – References
Niagara shell commands May 1, 2007

• wb commands
These commands are used at the command line and may be typed in using the “wb” prefix. See “wb
(Workbench) commands” on page A-17.
• plat commands
These commands are used at the command line and may be typed in using the “plat” prefix. See “plat
(platform) commands” on page A-17:

Niagara shell commands

• cd
This command displays and changes the current directory. Type cd <directory name> to
change to a specific directory. Type cd to display the current directory.
• debug
This command turns debug tracing on and off. Type debug on to turn on debug. Type debug off
to turn off debug.
• print
This command prints a message to the output stream. Type print <message> to print the literal
message to the console.
• reset
This command resets the environment to its default state. Type reset to set the environment to its
default state.
• set
This command displays and modifies environment variables.
• Type to set to display all the environment variables.
• Type set <prefix> to display all the environment variables that start with the specified pre-
fix.
• Type to set <name>= to remove the “named” variable.
• Type to set <name>=<value> to set the “named” variable to the “value” specified.
• which
This command resolves a filename in a path. Type to which <filename> to find the first occur-
rence of the specified “filename”.

nre (station) commands

Use the following syntax with the nre command:
nre [options] <class> [args]*
The following parameters may be used with the nre command.
• class
This is a class name or a module:classname to execute.
• args
This is the name of one or more arguments to pass through to main.
The following options may be used with the nre command.
• -version
This option displays the nre version.
• -modules:<x>
This option displays the modules that match the pattern defined by “x”.
• -hosted
This option displays the id for the system host.
• -licenses
This option displays a summary of the license information.
• -props
This option displays a list of the system properties.
• -locale:<x>
This option allows you to set the default locale. For example, to set the default locale to US English,
type: -locale:en_US
• -@option
This option allows you to pass the specified option to the Java VM.
• -testheap
This option tests and displays the max heap size.
• -buildreg
This option causes a rebuild of the registry.

NiagaraAX-3.x
A-16
User Guide
Chapter A – References Types of console commands
May 1, 2007 wb (Workbench) commands

wb (Workbench) commands
The wb command starts up an instance of Workbench. Use the following syntax with the wb command:
wb [options] <ord>
The following parameter may be used with the wb command.
• ORD
This option specifies the ORD of the initial view that you want display when Workbench starts up.
The following options may be used with the wb command.
• -profile
This option specifies the workbench profile to assign when Workbench starts up.
• -file:ord
This option specifies the initial file to display when Workbench starts up.
• -locale<x>
This option sets the locale on startup.
• -@<option>
This options allows you to pass the specified option to the Java VM.

plat (platform) commands

Use the following syntax with the plat command:
plat <command> <flags> <command-flags>
The following commands may be used with plat.
• details
This command displays a configuration summary for a remote host.
• fget
This command gets one or more files from a remote host.
• flist
This command provides file details for a single file, or for all files in a directory.
• ipconfig
This command displays the TCP/IP configuration for a remote host.
• jacejar
This command creates Niagara module files that can be run on embedded hosts.
• liststations
This command lists stations that are managed by the Niagara platform daemon.
• moduleinstall
This command installs Niagara modules to a remote host.
• reboothost
This command requests that a remote Niagara platform daemon reboot its host.
• script
This command runs one or more platform commands in a script.
• startstation
This command requests that a Niagara platform daemon start a station.
• stopstation
This command requests that a Niagara platform daemon stop a station.
• tellstation
This command sends text to the console of a running Niagara station.
• watchstation
This command monitors the output of a niagara station.
• installdaemon
This command installs the Niagara platform service (Win32 only).
• uninstalldaemon
This command removes the Niagara platform service (Win32 only).
• installdialup
This command installs the Niagara dialup service (Win32 only).
• unistalldialup
This command removes the Niagara dialup service (Win32 only).
The following options may be used with the plat command.
• -usage
plat -usage prints the help listing in the console
plat <command> -usage prints the command specific usage in the console

NiagaraAX-3.x
A-17
User Guide
SVG Colors Chapter A – References
plat (platform) commands May 1, 2007

• -?
• plat -? prints the help listing in the console
• plat <command> -? prints the command specific usage in the console
• -help
• plat -help prints the help listing in the console
• plat <command> -help prints the command specific usage in the console
• -locale:<x>
This option sets the default locale (en_US).
• -@<option>
This option passes the option to the Java VM.
• -buildreg
This option forces a rebuild of the registry.

SVG Colors
The following list provides information about X11 colors that are supported by popular browsers with
the addition of gray/grey variants from SVG 1.0. The list is the same as the SVG 1.0 color keyword names.
The two color swatches on the left illustrate setting the background color of a table cell in two ways: The
first column uses the named color value, and the second column uses the respective numeric color value.

Caution The appearance of colors varies in different media (print, screen, and so on). Colors presentation also vary
between browsers. The most reliable way to preview colors is in the browser type and version that it is are
targeted for.

Table A-1 SVG color table

Named Numeric Color name Hex rgb Decimal

aliceblue #f0f8ff 240,248,255

antiquewhite #faebd7 250,235,215

aqua #00ffff 0,255,255

aquamarine #7fffd4 127,255,212

azure #f0ffff 240,255,255

beige #f5f5dc 245,245,220

bisque #ffe4c4 255,228,196

black #000000 0,0,0

blanchedal- #ffebcd 255,235,205

mond

blue #0000ff 0,0,255

blueviolet #8a2be2 138,43,226

brown #a52a2a 165,42,42

burlywood #deb887 222,184,135

cadetblue #5f9ea0 95,158,160

chartreuse #7fff00 127,255,0

chocolate #d2691e 210,105,30

coral #ff7f50 255,127,80

cornflowerblue #6495ed 100,149,237

NiagaraAX-3.x
A-18
User Guide
Chapter A – References SVG Colors
May 1, 2007 plat (platform) commands

Named Numeric Color name Hex rgb Decimal

cornsilk #fff8dc 255,248,220

crimson #dc143c 220,20,60

cyan #00ffff 0,255,255

darkblue #00008b 0,0,139

darkcyan #008b8b 0,139,139

darkgoldenrod #b8860b 184,134,11

darkgray #a9a9a9 169,169,169

darkgreen #006400 0,100,0

darkgrey #a9a9a9 169,169,169

darkkhaki #bdb76b 189,183,107

darkmagenta #8b008b 139,0,139

darkolivegreen #556b2f 85,107,47

darkorange #ff8c00 255,140,0

darkorchid #9932cc 153,50,204

darkred #8b0000 139,0,0

darksalmon #e9967a 233,150,122

darkseagreen #8fbc8f 143,188,143

darkslateblue #483d8b 72,61,139

darkslategray #2f4f4f 47,79,79

darkslategrey #2f4f4f 47,79,79

darkturquoise #00ced1 0,206,209

darkviolet #9400d3 148,0,211

deeppink #ff1493 255,20,147

deepskyblue #00bfff 0,191,255

dimgray #696969 105,105,105

dimgrey #696969 105,105,105

dodgerblue #1e90ff 30,144,255

firebrick #b22222 178,34,34

floralwhite #fffaf0 255,250,240

forestgreen #228b22 34,139,34

fuchsia #ff00ff 255,0,255

gainsboro #dcdcdc 220,220,220

ghostwhite #f8f8ff 248,248,255

gold #ffd700 255,215,0

NiagaraAX-3.x
A-19
User Guide
SVG Colors Chapter A – References
plat (platform) commands May 1, 2007

Named Numeric Color name Hex rgb Decimal

goldenrod #daa520 218,165,32

gray #808080 128,128,128

green #008000 0,128,0

greenyellow #adff2f 173,255,47

grey #808080 128,128,128

honeydew #f0fff0 240,255,240

hotpink #ff69b4 255,105,180

indianred #cd5c5c 205,92,92

indigo #4b0082 75,0,130

ivory #fffff0 255,255,240

khaki #f0e68c 240,230,140

lavender #e6e6fa 230,230,250

lavenderblush #fff0f5 255,240,245

lawngreen #7cfc00 124,252,0

lemonchiffon #fffacd 255,250,205

lightblue #add8e6 173,216,230

lightcoral #f08080 240,128,128

lightcyan #e0ffff 224,255,255

lightgoldenro- #fafad2 250,250,210

dyellow

lightgray #d3d3d3 211,211,211

lightgreen #90ee90 144,238,144

lightgrey #d3d3d3 211,211,211

lightpink #ffb6c1 255,182,193

lightsalmon #ffa07a 255,160,122

lightseagreen #20b2aa 32,178,170

lightskyblue #87cefa 135,206,250

lightslategray #778899 119,136,153

lightslategrey #778899 119,136,153

lightsteelblue #b0c4de 176,196,222

lightyellow #ffffe0 255,255,224

lime #00ff00 0,255,0

limegreen #32cd32 50,205,50

linen #faf0e6 250,240,230

magenta #ff00ff 255,0,255

NiagaraAX-3.x
A-20
User Guide
Chapter A – References SVG Colors
May 1, 2007 plat (platform) commands

Named Numeric Color name Hex rgb Decimal

maroon #800000 128,0,0

mediumaqua- #66cdaa 102,205,170

marine

mediumblue #0000cd 0,0,205

mediumorchid #ba55d3 186,85,211

mediumpurple #9370db 147,112,219

mediumsea- #3cb371 60,179,113

green

mediumslate- #7b68ee 123,104,238

blue

mediumspring- #00fa9a 0,250,154

green

mediumtur- #48d1cc 72,209,204

quoise

mediumviole- #c71585 199,21,133

tred

midnightblue #191970 25,25,112

mintcream #f5fffa 245,255,250

mistyrose #ffe4e1 255,228,225

moccasin #ffe4b5 255,228,181

navajowhite #ffdead 255,222,173

navy #000080 0,0,128

oldlace #fdf5e6 253,245,230

olive #808000 128,128,0

olivedrab #6b8e23 107,142,35

orange #ffa500 255,165,0

orangered #ff4500 255,69,0

orchid #da70d6 218,112,214

palegoldenrod #eee8aa 238,232,170

palegreen #98fb98 152,251,152

paleturquoise #afeeee 175,238,238

palevioletred #db7093 219,112,147

papayawhip #ffefd5 255,239,213

peachpuff #ffdab9 255,218,185

peru #cd853f 205,133,63

pink #ffc0cb 255,192,203

plum #dda0dd 221,160,221

NiagaraAX-3.x
A-21
User Guide
SVG Colors Chapter A – References
plat (platform) commands May 1, 2007

Named Numeric Color name Hex rgb Decimal

powderblue #b0e0e6 176,224,230

purple #800080 128,0,128

red #ff0000 255,0,0

rosybrown #bc8f8f 188,143,143

royalblue #4169e1 65,105,225

saddlebrown #8b4513 139,69,19

salmon #fa8072 250,128,114

sandybrown #f4a460 244,164,96

seagreen #2e8b57 46,139,87

seashell #fff5ee 255,245,238

sienna #a0522d 160,82,45

silver #c0c0c0 192,192,192

skyblue #87ceeb 135,206,235

slateblue #6a5acd 106,90,205

slategray #708090 112,128,144

slategrey #708090 112,128,144

snow #fffafa 255,250,250

springgreen #00ff7f 0,255,127

steelblue #4682b4 70,130,180

tan #d2b48c 210,180,140

teal #008080 0,128,128

thistle #d8bfd8 216,191,216

tomato #ff6347 255,99,71

turquoise #40e0d0 64,224,208

violet #ee82ee 238,130,238

wheat #f5deb3 245,222,179

white #ffffff 255,255,255

whitesmoke #f5f5f5 245,245,245

yellow #ffff00 255,255,0

yellowgreen #9acd32 154,205,50

NiagaraAX-3.x
A-22
User Guide
 CHAPTER B
Glossary
action Action is a slot that defines a behavior which can be invoked on a Component. See help-
BajadocViewer Actions for more information.
administrator Administrator Security Permissions are defined to be the functions required to config-
ure a system. This person may need to view or edit all the features of the system. Administrator Edit in-
cludes creating Components and Linking Components in addition to editing Properties. See
Administrator Security for more information.
agent An agent is a special Object type that provides services for other Object types. Agents are regis-
tered on their target types via the Module manifest and queried via the Registry interface.
alarm Alarms provide the ability to be notified when a special event occurs. See AlarmConsole or
AlarmPortal for more information.
animate Animate allows you to change a property's value based on changing information. In the PxEd-
itor, right-click a property and select Animate.
API API is a Application Programming Interface. It defines how software engineers access the capabil-
ities of software like the Niagara Framework.
applet A small Java program that can be embedded in an HTML page. Applets differ from full-fledged
Java applications in that they are not allowed to access certain resources on the local computer, such as
files and serial devices (modems, printers, etc.), and are prohibited from communicating with most other
computers across a network. The common rule is that an applet can only make an Internet connection
to the computer from which the applet was sent. See also BAppletView.bajadoc for more technical infor-
mation.
archive Archive is a History that is stored in a different station from where it originated.
audit The Audit keeps a History of changes made by users. If enabled, it registers itself as the Auditor
for the system when the service is started. One of the important aspects of security is the ability to analyze
what has happened after the fact. See history-AuditHistoryService for more information.
back Back refers to the last location viewed by the browser. It is required in order to go forward.
BACnet BACnet refers to A Data Communication Protocol for Building Automation and Control Net-
works. Developed under the auspices of the American Society of Heating, Refrigerating and Air-Condi-
tioning Engineers (ASHRAE), BACnet is an American national standard, a European pre-standard, and
an ISO global standard. The protocol is supported and maintained by ASHRAE Standing Standard
Project Committee 135. See the BACnet Guide for more information on BACnet in the Niagara Frame-
work.
Baja Baja is a term coined from Building Automation Java Architecture. The core framework built by
Tridium is designed to be published as an open standard. This standard is being developed through Sun's
Java Community Process as JSR 60. See Baja vs. Niagara in the Developer Guide for more information.
Bajadoc Bajadoc is the Baja reference documentation. Baja reference documentation includes
both Java API details as well as Baja slot documentation. See help-BajadocViewer for more informa-
tion.
binding A Binding is used to bind a Widget to a data source. Bindings are bound to one Object
using an Ord. Subclasses are registered as Agents on the type of Objects to which they can be bound
to. See also BBinding.bajadoc for more technical information.

NiagaraAX-3.x
B–1
User Guide
 Chapter B – Glossary
May 1, 2007

bog file A Bog file contains Baja Components. It can be a complete Database or any Collection of Com-
ponents. A Bog File is a special file that can describe Components in a Database. All views can be used on
Components in a Bog File just as if they were in a Station. See Bog Files in the Developer Guide for more
information.
bookmark Bookmark identifies a single bookmark. See Bookmarks and About the bookmark side
bar for more information. Bajadoc is available at BBookmark.bajadoc.
BooleanPoint BooleanPoint defines a read only control point with only an output element. Ba-
jadoc is available at BBooleanPoint.bajadoc.
BQL BQL is an acronym for Baja Query Language. BQL has a select statement similar to the select state-
ment of Structured Query Language (SQL). It is typically used to provide programmable access to infor-
mation in Niagara. See “BQL” in the Niagara Developer Guide for more details.
bql scheme The "bql" Scheme is used to encapsulate a BQL query.
browser A browser is a program used to access Web Pages from a Web Server. A special browser is used
within the Workbench to access the Niagara Framework. Other common browsers include Microsoft In-
ternet Explorer, Mozilla and firefox.
build The build tool is used to build the Niagara Framework itself. You may utilize this build tool to
manage your own Niagara modules. See build.html in the Developer Guide for more information.
cancel Stop the current Action or ignore changes. See Edit Cancel for more information.
chart A chart is a graphical representation of data. The HistoryChart is a view that allows you to
view and configure charts of histories. See “Types of history views” on page 6-9 for more information.
click Click
means to press and release the primary or secondary mouse button.
client The client part of a client-server architecture. Typically, a client is an application that runs on one
computer and relies on a server to perform some operations. For example, an e-mail client is an applica-
tion that enables you to send and receive e-mail.
clipboard The clipboard contains the results of copy or cut operations and can be used for paste.
collection A collection represents a group of objects, known as its elements. Some collections allow du-
plicate elements and others do not. Some are ordered and others unordered. See Collection.bajadoc for
more technical information.
color Color stores a color specification via an alpha, red, green, and blue component. See BCol-
or.bajadoc for more information.
command Command typically refers to an Action in the Niagara Framework. See “About point actions”
on page 3-3 for more information on point commands.
component A Component is the primary building block of the Niagara Framework. See baja-
Component for more information.
composite A Composite allows you to expose child slots of a Component as slots on the parent.
See “About composites” on page 3-26 for more information.
connect Connect refers to entering a valid Address for the SYSTEM to connect, User Name and
Pass Phrase. This creates an active session for use of the system.
console Console provides a simple runtime console for managing and debugging the station. See
“About the console” on page 2-11 for more information.
container Containers allow you to logically group Components. The current Container is the Compo-
nent that contains the Components in the display window. See baja-Component Containers for more in-
formation.
context Context is used in operations which may perform differently depending on their context. Ex-
amples include operations which may require auditing or localization.
control The control module provides normalized components for representing control points. All con-
trol points subclass from the ControlPoint base class. Control points are typically used with the Driver

NiagaraAX-3.x
B-2
User Guide
Chapter B – Glossary
May 1, 2007

framework to read and write points in external devices. See Control in the Developer Guide for more in-
formation.
control point In the narrowest terms, control points refer to the 8 point types found in the Baja
control palette under the “Points” folder. See “About control points” on page 3-1.
In broader terms, control points include other components found in both the control and kitControl pal-
ettes. Most of these are "classed" from the 8 basic point types. See “Other control components” on page
3-2.
ControlPoint is the base class for all point types in the Baja control architecture. A ControlPoint typically
maps to one value being read or written via a driver. All ControlPoints have a StatusValue property called
"out". ControlPoints inherit from BooleanPoint, EnumPoint, NumericPoint and StringPoint.
If the predefined proxyExt is not a NullProxyExt then the point is considered a proxy point which means
that it is a local representation of a point which actually exists in an external device. The driver framework
is used to maintain synchronization.
copy Copy places a copy of the Selection in the clipboard for a future paste operation. The shortcut
is Ctrl + C (hold down Ctrl and press C). See Edit Copy for more information.
credentials Manage Credentials is available in the main Tools menu by selecting Manage
Credentials.... You can Reset or Remove selected Credentials or Remove All Credentials.
See “New module wizard” on page 11-8 for more information.
CSS CSS is cascading style sheet.
CSV The CSV ("Comma Separated Values") file format is used to exchange data between applications.
cut Cut places the Selection in the clipboard for a future paste operation. It is deleted from its cur-
rent location. The shortcut is Ctrl + X (hold down Ctrl and press X). See Edit Cut for more informa-
tion.
daemon Daemon typically refers to the Niagara platform daemon, the server process required by a Nia-
gara host to run a station. There is also a separate “dialup daemon” to handle dialup modem functions.
database Database is used to store information. Examples of databases include the Registry or a
Station database.
debug Debug refers to testing or correcting software. The Program Debugger provides debug capability
for program Components.
delete Delete removes the current Selection from its parent Container. The shortcut is Delete. See
Edit Delete for more information.
delete links Delete Links removes the selected links from the parent Container.
dependencies All Modules include zero or one dependencies element. This element contains zero or
more dependency elements which enumerate the Module's dependencies. Dependencies must be re-
solved by the framework before the Module can be successfully used. Each dependency has one required
attribute. The name attribute specifies the globally unique name of the dependent Module. A dependency
may also specify a bajaVersion and/or a vendor version. If the bajaVersion attribute is declared then it
specifies the lowest bajaVersion of the dependent Module required. It is assumed that higher versions of
a Module are backward compatible, thus any version greater than the one specified in a dependency is
considered usable. Likewise the vendor and vendorVersion may be specified to declare a dependency on
a specific implementation of a Module. The vendor attribute may be specified without the vendorVersion
attribute, but not vise versa. The required embed attribute specifies whether the dependency should be
enforced on embedded Niagara devices.
The ModuleSpaceView supports the ability to right click a Module and display all its dependencies. These
dependencies are as declared by the Module's manifest. To compute the dependencies needed to use a
specific API a new Dependencies command has been added to the BajadocViewer Menus. This command
will compute all the classes and Modules required to use a specific class in the API.
device extensions DeviceExt is the abstract base class for device extensions which provide feature in-
tegrations between the device's native protocol and model and the framework's normalized model. See
BDeviceExt.bajadoc for more information.

NiagaraAX-3.x
B-3
User Guide
 Chapter B – Glossary
May 1, 2007

directory Directory is the File type used to represent Directories in File space implementations. See
BDirectory.bajadoc for more information.
disabled Status disabled means a user manually disabled the component using the enabled property
(enabled = false). Disabled always propagates down. For example if you set the network disabled, that
forces all child devices disabled, which then forces all proxy points under each device disabled. See “About
point status” on page 3-15 for more information.
disconnect You may logoff the system at any time by Right-clicking the connected system in the tree
and select Disconnect. This allows you to close a session with a Station without removing it from the
tree.
discover Discover allows you to find items that are defined using a driver’s framework. See “About
Device Discover, Add and Match (Learn Process)” on page 4-16 and “About Point Discover, Add and
Match (Learn Process)” on page 4-32 for more information.
domain Security Domains may be assigned to any Component or set of Components in the sys-
tem. For example, security domains may be used to assign Components into application domains
such as hvac, fire, and lighting or security domains can be used to assign Components into customer
groups such as tenant 1, tenant 2, etc.
double-click Double-click
means to press and release the primary mouse button twice.
down Down means a communication error at the network or device level. Down always propagates
down. Down is controlled by the pingFail and pingOk methods. The reason why a device is down is always
stored in the health.lastFailCause property.
download Download refers to passing data down to a device. You may download a Station from its su-
pervisor.
drag Drag means to move the mouse while pressing the primary mouse button.
driver Drivers use "Managers" which provide a consistent look and feel for managing configuration and
learning of devices and points. The cornerstone of the driver tools is the ability to support batch edits and
Learns. See Driver Framework in the Developer Guide for more information.
duplicate Duplicate copies the current Selection and places a duplicate in the same Container.
The shortcut is Ctrl + D (hold down Ctrl and press D). See Edit Duplicate for more information.
edit Edit refers to changing software. Edit Mode allows you make changes to the system.
element The elements define the hierarchical structure of a document. The majority of elements have
opening and closing Tags. Among these Tags, pieces of text or even the whole documents can be found.
There are empty elements which contains only opening Tags without any content.
An element may also model one single piece of information in the Baja control architecture. The most
common types of elements are:
• BooleanElement
• NumericElement
• EnumElement
• StringElement
All elements regardless of their value type share common attributes. Every element has a status
property which provides a consistent mechanism to convey point status. Each element also contains a
priority level for informational purposes. If the priority is PriorityLevel.none, this is not a prioritized ele-
ment.
Elements are basic building blocks from which larger, more sophisticated control points are created. A
control point contains one or more input elements and one or more output elements. Elements can also
be linked between Baja Objects to move data.
enumeration Enumeration represents a value data item which has a fixed set of possible values. This
set of values is called the Enumeration's Range. The standard enumerations include:
• alarm:AlarmRecordTypes
• alarm:AlarmTransition
• baja:Month

NiagaraAX-3.x
B-4
User Guide
Chapter B – Glossary
May 1, 2007

• baja:Weekday
• control:AlarmState
• control:AlarmType
• control:CollectionState
• control:DisableAction
• control:LoopAction
• control:NotifyType
• control:PriorityLevel
• control:Reliability
• control:TotalizationInterval
• driver:ArchiveMode
• driver:ArchiveResult
• driver:ArchiveState
• driver:PollFrequency
• driver:ProxyState
See Enum Range Dialog or BEnum.bajadoc for more information.
EnumPoint EnumPoint defines a read only control point with only an output element. Bajadoc
is available at BEnumPoint.bajadoc.
export Export refers to providing data from the system for external use. You can export any Table found
in the workbench (anything built with bajaui:Table). The Table options menu (that little button to the
right of the header), includes a Print and Export command. These commands allow you to export the ta-
ble to PDF, HTML, or CSV (ExcelFile). The export uses the current sort order and visible columns you
have displayed. The Niagara Framework also exports its Database to XML for backup and conversion.
extension Extensions allow plug-in functionality to support features such as alarming and historical
data collection.
facets Facets represents a facets in the system. See “Facets” on page 1-10 or BFacets.bajadoc for
more information.
fault Faults always propagate down. The framework now performs "fatalFault" checking such as making
sure your device is under the right network type. Fatal faults will also be the mechanism used to perform
licensing checks. Developers can also manage their fault condition via the configFail() and configOk()
methods. The reason why a component is in fault is always stored in the faultCause property.
feature Feature encapsulates a feature specification for the licensing framework. A feature is uniquely
identified by a vendor and feature name. It contains an expiration and a set of optional properties. See
also Feature.bajadoc for more technical information.
file File represents a file in the file system of a session. See BogFile for some of the common file
types.
file scheme The "file" Scheme is used to identify files on the file system. All file ords resolve to instances
of javax.baja.file.BIFile. File queries always parse into a FilePath. File ords come in the following flavors:
• Authority Absolute: "//hostname/dir1/dir2"
• Local Absolute: "/dir1/dir2"
• Sys Absolute: "!lib/system.properties"
• Station Absolute: "^config.bog"
• Relative: "myfile.txt"
• Relative with Backup: "../myfile.txt"
Sys absolute paths indicate files rooted under the Niagara installation directory identified via Sys.getBa-
jaHome(). User absolute paths are rooted under the user home directory identified via Sys.getUser-
Home(). In the case of station VMs, user home is the directory of the station Database.
filter Filter is used to select specified items. An example is the Alarm Console Filter.
find Find allows you to search for the selected string. The shortcut is F5. See Search Find for more
information.
find files Find Files allows you to find the all occurrences in the files. See Search Find Files for
more information.
find next Find Next allows you to find the next occurrence of the selected string. The shortcut is
Ctrl + F (hold down Ctrl and press F). See Search Find Next for more information.

NiagaraAX-3.x
B-5
User Guide
 Chapter B – Glossary
May 1, 2007

find prev Find Prev allows you to find the previous occurrence of the selected string. The shortcut
is Ctrl + Shift + F (hold down Ctrl and Shift and press F). See Search Find Prev for more information.
Firefox Firefox is a browser used to access Web Pages from a Web Server. See http://www.mozilla.org/
index.htmlfor more information.
flag Flags are boolean values which are stored as a bitmask on each slot in a Baja Object. Some flags
apply to all slot types, while some only have meaning for certain slot types.
folder Folder represents a Folder in the file system of a session. See Folder for more information.
format Format is used to format Objects into Strings using a standardized formatting pattern language.
The
format String is normal text with embedded scripts denoted by the % percent character (use %% to insert
a real %). A script is one or more calls chained together using the . dot operator. Calls are mapped to
methods using reflections. Given call "foo", the order of reflection mapping is:
• special call (see below)
• getFoo(Context)
• getFoo()
• foo(Context)
• foo()
• get("foo")
The following special functions are available to use in a script:
• time() calls Clock.time() to get current time as an AbsTime
• lexicon(module:key) gets the specified lexicon text
Examples of formats:
• "hello world"
• "my name is %displayName%"
• "my parent's name is %parent.displayName%"
• "%value% {%status.flagsToString%} @ %status.priority%"
• "%time().toDateString%"
• * "%lexicon(bajaui:dialog.error)%"
forward Forward refers to the next location for the browser to return. It is only available after a
back.
Fox Fox is a proprietary protocol which is used for all network communication between Stations
as well as between the Workbench and Stations. Fox is a multiplexed peer to peer protocol which sits
onto of a TCP connection.
fox scheme The "fox" Scheme is used to establish a Fox session. Fox is the primary protocol used by
Niagara for IP communication. A "fox" query is formatted as "fox:" or "fox:<port>". If port is unspecified
then the default 1911 port is assumed.
FROM FROM is the mechanism to choose the extent. This may be a History or a class in a Station. See
ExtentBuilder for more information.
gadget Gadget is a visual representation of an arbitrary Object for views.
Gif Gif stands for Graphical Interchange Format. It is a file format used for graphical images.
glyph A Glyph is a visual representation.
GotoFile Goto File allows you to go to a file that has been indexed with the file indexer. The shortcut
is Ctrl + F3 (hold down Ctrl and press F3). See Search Goto File for more information.
GotoLine Goto Line allows you to go to a line number in the file. The shortcut is Ctrl + G (hold down
Ctrl and press G). See Search Goto Line for more information.
handle scheme The "h" Scheme is used to resolve a Component by its handle. Handles are unique
String identifiers for Components within a ComponentSpace. Handles provide a way to persistently iden-
tify a component independent of any renames which modify a Component's slot path.
Help Help refers to the electronic documentation available. It includes electronic manuals as well
as context specific help.

NiagaraAX-3.x
B-6
User Guide
Chapter B – Glossary
May 1, 2007

history History is an ordered Collection of timestamped records. Each History is identified by a

unique id. Histories can be periodically Archived to a remote History Database (Archive). A Histo-
ryDatabase is a set of histories. History: is also used as a Scheme in Ords to refer to collected histories.
Home Home refers to the originating page. Your home page in Niagara is the page that you see
after you enter your password. It is programmed in your user Component.
host Host is the navigation node used to organize navigation by hosts. Hosts are the first level of
the navigation tree. Hosts represent a physical box. LocalHost is used to represent the local machine.
Bajadoc is available at BHost.bajadoc.
HTML HyperText Markup Language is the primary language for Web Servers. It is used in areas
such as the electronic help. A thin client property sheet is available. This interface is built using only
HTML, CSS and JavaScript and doesn't require any Plugins. A Workbench style navbar with paths and
drop downs is available, plus field editors for the core types: boolean, int, enum, float, abstime, and rel-
time.
HTTP HTTP is short for HyperText Transfer Protocol, the underlying protocol used by the
World Wide Web (World Wide Web). HTTP defines how messages are formatted and transmitted,
and what actions Web Servers and browsers should take in response to various commands. For example,
when you enter a URL in your browser, this actually sends an HTTP command to the Web Server direct-
ing it to fetch and transmit the requested Web Page. The other main standard that controls how the
World Wide Web works is HTML, which covers how Web Pages are formatted and displayed.
HTTP is called a stateless protocol because each command is executed independently, without any
knowledge of the commands that came before it. This is the main reason that it is difficult to implement
World Wide Web sites that react intelligently to user input. This shortcoming of HTTP is addressed in a
number of technologies, including Java, JavaScript and cookies.
icon An icon is a graphical representation. Icons are used in the toolbar and in the tree.
image Image is a representation of a raster image. Bajadoc is available at BImage.bajadoc.
import Import refers to receiving data from an external source. The Niagara Framework imports its
Database from XML for backup and conversion.
ip scheme The "ip" Scheme is used to identify a BIpHost instance. Ords starting with "ip" are always
absolute and ignore any base which may be specified. The body of a "ip" query is a DNS hostname or an
IP address of the format "dd.dd.dd.dd".
Java Java is a high-level programming language developed by Sun Microsystems. Java source code
files (files with a .java extension) are compiled into a format called bytecode (files with a .class exten-
sion), which can then be executed by a Java interpreter. Compiled Java code can run on most computers
because Java interpreters and runtime environments, known as Java Virtual Machines (VMs), exist for
most operating systems, including UNIX, the Macintosh OS, and Microsoft Windows. Bytecode can also
be converted directly into machine language instructions by a just-in-time compiler (JIT).
Java is a general purpose programming language with a number of features that make the language well
suited for use on the World Wide Web. Small Java applications are called Java Applets and can be down-
loaded from a Web Server and run on your computer by a Java-compatible World Wide Web browser.
For more information, seehttp://java.com andhttp://java.sun.com/.
JavaScript JavaScript refers to the standard scripting language used in HTML documents. Mi-
crosoft Internet Explorer support is discussed at http://msdn.microsoft.com/scripting/jscript/de-
fault.htm. Mozilla support is discussed at http://www.mozilla.org/js/index.htmlSee http://www.ecma-
international.org/publications/standards/Ecma-262.htmfor more information on the official Standard
ECMA-262 ECMAScript Language Specification.
Jpeg Jpeg stands for Joint Photographic Experts Group. It is often abbreviated to JPG when the file
system is limited to a 3 character suffix. JPEG uses a Lossy compression method to create the final
file.
language code Language Code refers to ISO 639 language code -- two letter, lower-case preferred. See
http://www.loc.gov/standards/iso639-2/langcodes.html for the list.
learn Learn allows you to discover and add items that are defined using the driver framework. See
“About Learn toggle” on page 4-16 for more information.

NiagaraAX-3.x
B-7
User Guide
 Chapter B – Glossary
May 1, 2007

left-click Click
or
Left-click
means to press and release the primary mouse button. For most systems, this is the left mouse button.
lexicon Lexicon is used to provide support for other languages.
links Links are the relationships defined between Components. Links provide the means to pass
data between Components. See Links in the Developer Guide for more information.
local Local is a Scheme used in Ords. It is both a Host Scheme and a session Scheme. It represents Ob-
jects found within the local VM.
log Log is used to log events. The LogHistoryService keeps a History of Niagara log records. If enabled,
it registers itself as the LogHandler for the system when the service is started.
logoff Logoff refers to removing a user from an active session so that a password will have to be entered
to logon for use of the system.
logon Logon refers to entering a valid Address for the SYSTEM to connect, User Name and Pass Phrase.
This creates an active session for use of the system.
match Match allows you to match items that are discovered.
menu A Menu is a list of choices. The Niagara Framework uses the main pull down menu and popup
menus on the tree and Components. See menu for more information.
Microsoft Internet Explorer Microsoft Internet Explorer is a browser used to access Web Pages
from a Web Server. See http://www.microsoft.com/ie for more information.
MIME The Multipurpose Internet Mail Extensions (MIME) provide a mechanism to determine file
type in a standardized way.
module The first step in understanding the Niagara architecture is to grasp the concept of mod-
ules. Modules are the smallest unit of deployment and versioning in the Niagara architecture. A mod-
ule is:
• A JAR file compliant with PKZIP compression
• Contains a XML manifest in meta-inf/module.xml
• Is independently versioned and deployable
• States its dependencies on other modules and their versions
See “About modules” on page 1-6, or Modules in the Developer Guide for more information.
module scheme The "module" Scheme is used to access BIFiles inside the module jar files. The module
Scheme uses the "file:" Scheme's formatting where the authority name is the module name. Module que-
ries can be relative also. If the query is local absolute then it is assumed to be relative to the current mod-
ule. Module queries always parse into a FilePath.
monitor Monitor refers to observing. The PingMonitor periodically calls ping on all the Pingables
to monitor network and device health. PingMonitor provides built-in support to generate alarms
when pingables are down.
mouse The mouse is a device which allows you to control the on-screen pointer or cursor.
move Move is the same as Cut and Paste in one operation. See Edit Move for more information.
Mozilla Mozilla is a browser used to access Web Pages from a Web Server. See http://www.mozilla.org/
index.htmlfor more information.
name map Name Map defines a new Display Name for a Language Code. You can Add Name Map to
provide a new Display Name for a Language Code. A blank Language Code is used for all languages. You
Right-click on the Property displayNames to delete or rename Name Map and displayNames_xx to delete
or rename Name Map (xx) where xx is the Language Code. Bajadoc is available at BNameMap.bajadoc.
nav file Nav File stores XML nav markup. It allows you to define a navigation tree. You may use
the NavFileEditor to modify this file. Bajadoc is available at BNavFile.bajadoc.

NiagaraAX-3.x
B-8
User Guide
Chapter B – Glossary
May 1, 2007

Netscape Netscape is a browser used to access Web Pages from a Web Server. See http://
www.netscape.comfor more information.
network Network is a collection of devices. DeviceManager provides a summary of an attached
network. See BDeviceNetwork.bajadoc for more information.
Niagara Framework The Niagara Framework is a system designed to manage and control informa-
tion. Its primary application is for control systems because of its powerful and flexible integration capa-
bilities. The system is made up of Stations that run the Components of the Niagara Framework and views
that provide the ability to view and command these Components. See Baja vs. Niagara in the Developer
Guide for more information.
normalization Normalization is the process of removing unnecessary "." and ".." segments from the
path component of a hierarchical URI. Each "." segment is simply removed. A ".." segment is removed only
if it is preceded by a non-".." segment. Normalization has no effect upon opaque URIs.
null The null flag indicates that the associated value should not be used. It represents a don't care con-
dition. It is utilized in combination with priority arrays so that points may take or release control of their
level in a priority array based on their current state. It is also utilized in math, logic and other application
blocks that take a variable number of inputs. Any input with the null flag set is ignored.
NumericPoint NumericPoint defines a read only control point with only an output element. Ba-
jadoc is available at BNumericPoint.bajadoc.
object An Object is the base class required for all objects which conform to the Baja model. See
BObject.bajadoc for more technical information. See Object Model in the Developer Guide for more
information on the model.
offline Offline refers to accessing a Bog File file directly when the Station is not running.
open Open allows you to open any of the following:
• Ctrl + L
• Ctrl + O
•
•
• Ctrl + Shift + O
• Open Daemon (Niagarad)...
See the File menu reference for more information.
operator Operator Security Permissions are defined to be the functions required as a system operator
who may need to view or edit only the lowest level features of Components. See Operator Security for
more information.
options Options allow you to customize the framework for the way you use it. It can be selected
from the main Menu by selecting Tools > Options. See “Types of Workbench options” on page
2-20 for more information.
ORD Ord is an "Object Resolution Descriptor". An ORD is Baja's universal identification system for in-
tegrating heterogeneous naming systems into a single String. An ORD is composed of one or more que-
ries. Each query has a Scheme which identifies how to parse and resolve the query into an Object.
ord := query (ws "|" ws query)* query := scheme ws ":" ws body scheme := alpha
(alpha | digit)* body := bodyChar (bodyChar)* alpha := "a"-"z" | "A"-"Z" digit
:= "0"-"9" bodyChar := 0x32 - 0x127 except "|" ws := (space)*
See Naming in the Developer Guide orBOrd.bajadoc for more technical information.
overridden Overridden indicates that the user has manually overridden the component.
palette Palette provides a hierarchical view of available components. See “About palettes” on page
1-13 for more information.
paste Paste copies the contents of the clipboard to the selected location. The shortcut is Ctrl + V
(hold down Ctrl and press V). See Edit Paste for more information.
pathbar The pathbar is the line available in Workbench to see and select destination references. The
pathbar provides two functions. It is automatically updated each time a new view is selected to teach you
the Ord of each view. It also allows you to select the Ord directly to select that view. See “About the locator
bar” on page 2-13 for more information.

NiagaraAX-3.x
B-9
User Guide
 Chapter B – Glossary
May 1, 2007

PDF PDF refers to Adobe Portable Document Format (PDF) files.

permissions Permissions are a property used to define the permissions given to users in a Profile.
pin slots Pin Slots provides the capability to make Properties of a Component visible in the
WireSheet view of the Component. See Pin Slots in the WireSheet Plugin for more information.
platform Platform is the Niagara Platform Definition.
plugin A Plugin is a visualization for a Component. A WbPlugin is a widget designed to provide plugin
functionality in the Workbench tool environment.
Png PNG stands for Portable Network Graphics. The PNG image format uses lossless compres-
sion .
point extension Point extensions allow control point behavior to be extended in a consistent
manner. Each property of a ControlPoint which subclasses from PointExtension is considered an ex-
tension on the point. Extensions allow plug-in functionality such as alarming and historical data collec-
tion via special hooks that ControlPoint provides to PointExtension.
print Print provides automatic generation of a PDF for a view. Most standard widgets including
labels, point widget, tables, Charts, and most layout panes are handled. Access to the PDF visualiza-
tion is through the Print command in both Workbench and World Wide Web browser.
profile Security Profile may be assigned to any Component or set of Components in the system.
Users are assigned a security profile. The list of profile names map to Profile instances which are ac-
cessed from the UserService. A user can be assigned one profile. Profiles provide a convenient way to con-
figure Security Permissions on batches of users. Each profile is configured with a set of privileges for each
Security Domain.
properties Properties are the visible data associated with a Component. They provide the primary
means of interacting with Components. See help-BajadocViewer Properties for more information.
proxy Proxy is used locally to represent a remote Object. See “About the proxy extension” on page 3-10
for more information.
ProxyExt ProxyExt is the point extension supported in ControlPoints which are proxies for point data
in an external system. See “About the proxy extension” on page 3-10.
Px file A Px file contains Baja Components. It can be a complete Database or any Collection of
Components. A Px File is a special file that can provide a visualization for Components in a Database.
The PxEditor is a Plugin used to create and modify Px files. All views can be used on Components in a PX
just as if they were in a Station. See Bog Files in the Developer Guide for more information.
query Query is part of an "Object Resolution Descriptor". An ORD is composed of one or more queries.
Each query has a Scheme which identifies how to parse and resolve the query into an Object. A query is
made up of a Scheme and a body. See Naming in the Developer Guide orBOrd.bajadoc for more technical
information.
range Range of en Enumeration is a range of ordinal/name pairs. See Enum Range Dialog or BEnum-
Range.bajadoc for more information.
redo Redo causes an Action to be redone. It is only available after an undo. The shortcut is Ctrl +
Alt + Z (hold down Ctrl and Alt and press Z). See Edit Redo for more information.
refresh Refresh a page after its HTML source has been edited or if you encounter a reason to re-
load.
registry The registry is a term for a small Database built by Niagara Framework whenever it detects that
a module has been added, changed, or removed. The registry may be used to interrogate the system for
summary information about the Modules, types, Ord Schemes, and Agents installed without loading
Modules into memory. See RegistryDatabase.bajadoc for more information.
rename Rename allows you to change the name of a Component. It is available on a Component’s
right-click menu.
reorder Reorder allows you to reorder items in a station’s Nav tree. See “Using the nav side bar
(tree)” on page 12-8 for more information.

NiagaraAX-3.x
B-10
User Guide
Chapter B – Glossary
May 1, 2007

replace Replace allows you to replace the next occurrence in the file. The shortcut is Ctrl + R (hold
down Ctrl and press R). See Search Replace for more information.
replace files Replace Files allows you to replace the all occurrences in the files. See Search Replace
Files for more information.
restart Restart a Station. This causes a Station to be restarted.
right-click Right-click
means to press and release the secondary mouse button. For most systems, this is the right mouse button.
save Save causes a program to be evaluated and saved in the Database if valid. The shortcut is Ctrl
+ S (hold down Ctrl and press S).
scheme Scheme is part of an "Object Resolution Descriptor". The scheme identifies how to parse and
resolve the query into an Object. The scheme "local" is both a Host scheme and a session scheme. It rep-
resents objects found within the local VM. Some common schemes include:
• ip Scheme
• fox Scheme
• file Scheme
• module Scheme
• station Scheme
• slot Scheme
• handle Scheme
• spy Scheme
• bql Scheme
See Naming in the Developer Guide orBOrd.bajadoc for more technical information.
section Section is a portion of a Print document that is capable of containing Gadgets.
security Security in the Niagara framework covers some broad topics:
• Authentication: Logging in and verifying a user
• Encryption: When and how to use cryptography to secure data
• Permissions: Configuring and verifying user Permissions on objects
• Auditing: Logging user actions to create an audit trail
The heart of the Niagara security architecture is embodied by the UserService. The UserService contains
a Table of SecurityDomains (see Security model overview), Profiles (see Security model overview), and
Users. Domains are used to build groups of objects with common security needs. Profiles are used to de-
fine Permissions across zero or more Domains. Users are assigned to a Profile and used to represent an
entity (human or machine) requiring authentication and security checks. See Security in the Developer
Guide for more information.
SELECT SELECT is the primary statement used to access information in a Database. See work-
bench:ProjectionBuilder for more information.
selection The selection is the set of currently selected items. Most operations in the system act on
the selected items.
servlet A Java program that runs as part of a network service, typically an HTTP Web Server and re-
sponds to requests from clients. The most common use for a servlet is to extend a Web Server by gener-
ating World Wide Web content dynamically. For example, a client may need information from a
database; a servlet can be written that receives the request, gets and processes the data as needed by the
client and then returns the result to the client. Applets are also written in Java but run inside the JVM of
an HTML browser on the client. Servlets and Applets allow the server and client to be extended in a mod-
ular way by dynamically loading code which communicates with the main program via a standard pro-
gramming interface. See also HttpServlet.bajadoc for more technical information.
sidebar Sidebar allows you to choose whether to view sidebars by selecting Window > Side
Bars > Show Side Bar from the main menu. You can also select which sidebars you would like
to view. See “About side bars” on page 2-3 for more information.
slot Slots are the building blocks for defining Niagara Components. There are three types of slots:
• Property
• Action

NiagaraAX-3.x
B-11
User Guide
 Chapter B – Glossary
May 1, 2007

• Topic
See Slots in the Object Model section of the Developer Guide for more information.
slot scheme The "slot" Scheme is used to resolve a Value within a Complex by walking down a path of
slot names. Slot queries always parse into a SlotPath.
space Space defines a group of Objects which share common strategies for loading, caching, lifecycle,
naming, and navigation.
spy scheme The "spy" Scheme is used to navigate spy pages. The javax.baja.spy APIs provide a frame-
work for making diagnostics information easily available.
SQL SQL is an acronym for Structured Query Language. SQL is an American National Standards Insti-
tute (ANSI) standard for accessing Database systems.
stale Stale indicates that a situation has occurred which renders data untrustworthy. How stale is deter-
mined is a driver specific issue. However the common case is that a period of time has elapsed without a
successful read. TuningPolicy provides a staleTime property for configuring this period of time.
station Station is the Component which represents a Station in the Baja framework. See “About
stations” on page 1-15, or Station in the Developer Guide for more information.
station scheme The "station" Scheme is used to resolve the ComponentSpace of a station Database.
status Status provides a bit mask for various standardized status flags in the Baja control architecture.
Plus it provides for arbitrary extensions using facets.
See BStatus.bajadoc for more information.
statuscolors StatusColors are configurable by the baja lexicon and accessible by the Status API. You
may use the LexiconEditor to change these values. Entries include alarm, disabled, fault, down, overrid-
den and stale :
Status.alarm.bg=#FFFF0000 Status.alarm.fg=#FFFFFFFF
Status.disabled.bg=#FFD88AFF Status.disabled.fg=#FF000000
Status.fault.bg=#FFFFAA26 Status.fault.fg=#FF000000 Status.down.bg=#FFFFFF00
Status.down.fg=#FF000000 Status.overridden.bg=#FF86BEFF
Status.overridden.fg=#FF000000 Status.stale.bg=#FF00FF00
Status.stale.fg=#FF000000
The WireSheet options allow you to choose whether to Show Status Colors.
StatusFormat StatusFormat is used to provide a simple pattern language for formatting status values.
Patterns are strings with script commands embedded using the % character:
"Value=%value% Status=%status%"
Examples:
• %value% = value using facets
• %value(precision=2)% = value using 2 decimal places
• %value(units=null)% = value using facets with no units
• %value(units=null|precision=i:2)% = combination of previous two
• %status% = status fully specified
• {%status.flags%} %status.facets% = same as %status%
• %status.flags% = status flags, but not facets
• %status.facets% = status facets, but not flags
• %status.activeLevel% = status active level
• %value% {%status.flags%} @ %status.activeLevel%
The BNF grammar for the pattern language:
script := valScript | statusScript valScript := "value" [ "(" valFacets ")"
] valFacets := valFacet [ "|" valFacet ]* valFacet := valAddFacet | valRemove-
Facet valAddFacet := name "=" value valRemoveFacet := name "=null" value :=
DataUtil.marshal & unmarshal statusScript := "status" [ "." statusSubset ]
statusSubset := statusFlags | statusFacets | statusFacetKey statusFlags :=
"status.flags" statusFacets := "status.facets" statusFacetKey := "status."
name
See StatusFormat for more information.
StringPoint StringPoint defines a read only control point with only an output element. Bajadoc
is available at BStringPoint.bajadoc.

NiagaraAX-3.x
B-12
User Guide
Chapter B – Glossary
May 1, 2007

subclasses Subclasses provides a subclass tree of all that are subclassed from this item. See help-Baja-
docViewer Subclasses for more information.
tab Tab allows you to view multiple views in the same Window. See “Creating tabs in the view
pane” on page 2-19 for more information.
table Table displays a grid of rows and columns. See BTable.bajadoc for more technical informa-
tion.
tag An Element bounded by the marks "<" and ">" is a Tag. Tags are used to mark the semantic or
the structure of a document. HTML and XML use tags. A sample is the tag <title> to mark the
beginning of a title. See HTML Tags in the WbHtmlView for more information on tags supported by the
HtmlView Plugin.
toolbar A Toolbar is a row of button used to provide quick access to commonly used features. In the
Niagara Framework there are two rows of buttons on the toolbar. The first are the common buttons that
are always available. The second are the buttons based on the current view, mode and Selection.
topic Topic defines a Slot which indicates an event that is fired on a Component. See help-Baja-
docViewer Topics for more information.
tree The tree is the graphical representation of the hierarchy of the Components in the system. It pro-
vides a view of each Container and its contents when expanded. See Namespace Sidebar for more infor-
mation.
undo This reverses the last Action as if it had not been performed. In Niagara it is only available
for some actions. The shortcut is Ctrl + Z (hold down Ctrl and press Z). See Edit Undo for more in-
formation.
up level Up Level allows you to go to the next level up. The shortcut is Alt + Up. See “Types of
toolbar icons” on page A-13 for more information.
upload Upload refers to receiving data from a device. In Niagara you may upload a Station to its super-
visor so that you have a backup of its Database.
URI Uniform Resource Identifiers (URIs, aka URLs) are short strings that identify resources in the
World Wide Web: documents, images, downloadable files, services, electronic mailboxes, and other re-
sources. They make resources available under a variety of naming schemes and access methods such as
HTTP, FTP, and Internet mail addressable in the same simple way. They reduce the tedium of "log in to
this server, then issue this magic command ..." down to a single click.
It is an extensible technology: there are a number of existing addressing schemes, and more may be in-
corporated over time.
URL Uniform Resource Locator (URL) is the standard way of addressing over the Internet. The Niagara
Framework uses this convention for many of its resource locations.
user A User is a valid user name. It is used to logon to the system with a valid password.
vector Vector is a dynamic Struct which allows Properties to be added at runtime. See Vector for more
information.
view There are many ways to view your system. One way is directly in the tree. In addition, you can
Right-click on an item and select one of its views. Plugins also provide views of Components. See “About
the view selector” on page 2-14 and Viewing Components for more information.
Web Web refers to the World Wide Web. It is a system of Internet servers that support specially for-
matted documents. The documents are formatted in a markup language called HTML (HyperText Mark-
up Language) that supports links to other documents, as well as graphics, audio, and video files. This
means you can jump from one document to another simply by clicking on hot spots. Not all Internet serv-
ers are part of the World Wide Web. There are several applications called World Wide Web browsers
that make it easy to access the World Wide Web.
Web page A Web Page is a document on the World Wide Web. Every Web page is identified by a
unique URL (Uniform Resource Locator).
Web server A Web Server is a computer that delivers (serves up) Web Pages. Every Web server has an
IP address and possibly a domain name. For example, if you enter the URL http://www.niagaraframe-
work.com/ in your browser, this sends a request to the server whose domain name is niagaraframe-

NiagaraAX-3.x
B-13
User Guide
 Chapter B – Glossary
May 1, 2007

work.com. The server then fetches the page named index.html and sends it to your browser. Any
computer can be turned into a Web server by installing server software and connecting the machine to
the Internet. There are many Web server software applications, including public domain software from
NCSA and Apache, and commercial packages from Microsoft, Netscape and others.
wheel Wheel means to rotate the mouse wheel to scroll up or down.
WHERE The Where clause is used to specify that only certain rows of the Table are displayed, based
on the criteria described in that Where clause. See workbench:QualifierBuilder for more information.
widget Widget is a class used to create light weight user interface components which can seamlessly be
used in both the bajaui toolkit and in a 1.1 Applet environment.
window A Window is a graphical area used to present a view of the system. This can refer to the
primary window with Locator and tree or user created windows. See “Creating Additional Windows”
on page 2-19 for more information.
wizard Wizards are used to guide the user through common tasks. Some common wizards in-
clude:
• New Station Wizard
• Commissioning Wizard
• New Module Wizard
Workbench The Workbench is Niagara's Integrated Development Environment (IDE) for non-
programmers.
XML eXtended Markup Language (XML) is a standard for tagging data. It is a subset of the Standard
Generalized Markup Language (SGML) like HTML. See XML in the Developer Guide for more informa-
tion.

NiagaraAX-3.x
B-14
User Guide