ORCAview Technical Reference Manual 340.pdf

EDIT>SEARCH

ORCAview

Version 3.40 Technical Reference Manual

Front Matter First Released as ORCAview 3.20 PDF files May 1, 2000 (Rev. 1.0) First Printed as 3-Ring paper manual June, 2000 (Rev. 1.01) Released as revised ORCAview 3.21 PDF files April 3, 2001 (Rev. 1.10) Released as revised ORCAview 3.22 PDF files September 28, 2001 (Rev. 1.20) Released as revised ORCAview Beta 3.30 PDF files September 23, 2003 (Rev. 1.30) Released as revised ORCAview 3.30 PDF files May 1, 2004 (Rev. 1.30) Released as revised ORCAview 3.30 Release 2 PDF files April 30, 2005 (Ed. 1.40) Released as revised ORCAview 3.30 Release 3 PDF files September 30, 2005 (Ed. 1.50) Released as revised ORCAview 3.33 Release 1 PDF files May 3, 2006 (Ed. 1.60) Released as revised ORCAview 3.33 Release 2 PDF files November 22, 2009 (Ed. 1.70) Released as revised ORCAview 3.40 Release 1 PDF files December 9, 2011 (Ed. 1.80)

Copyright © Delta Controls Inc. All rights reserved Document Title: Document Number Current Edition Date of current revision

ORCAview Version 3.40 Technical Reference Manual None – PDF files included on Release CD 1.80 ORCAview 3.40 Release 1 Final December 9, 2011

No part of this manual may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language (natural or computer), in any form or by any means, without the prior written permission of Delta Controls Inc. Limited permission is granted to reproduce documents released in Adobe Portable Document Format (PDF) electronic format in paper format. Documents released in PDF electronic format may be printed by end-users for their own use using a printer such as an inkjet or laser device. Authorized distributors of Delta Controls Inc. products (Delta Partners) may print PDF documents for their own internal use or for use by their customers. Authorized Delta Partners may engage a printing or copying company to produce copies of released PDF documents with the prior written permission of Delta Controls Inc. Information in this document is subject to change without notice and does not represent a commitment to past versions of this document on the part of Delta Controls Inc. Delta Controls Inc. may make improvements and/or changes to this manual/the associated software/or associated hardware at any time. BACspec, BACstat, the Delta logo, the ORCA logo, ORCApower, the ORCAview logo, ORCAweb, enteliWEB, enteliBUS, enteliMESH, enteliTOUCH, enteliZONE, enteliSTAT, enteliCON and enteliSYSTEM are trademarks of Delta Controls Inc. BACstat®, ORCA®, ORCAview®, Virtual Stat® and Earthright® are registered trademark of Delta Controls Inc. Windows Vista and Windows XP and Windows 7 are registered trademarks of Microsoft Corporation. USRobotics is a trademark of 3Com Corporation. Intel is a registered trademark of Intel Corporation. ECHELON LONW ORKS are U.S. registered trademarks of Echelon Corporation.

All other trademarks are the property of their respective owners.

Document Control Title: ORCAview Version 3.40 Release 1 Technical Reference Manual Edition 1.80 Product Number: None – PDF files included on Release CD Rev

Date

Changes

1.0

April 30, 2000

Original manual for Version 3.20 ORCAview. Released as PDF files only.

1.01

June 22, 2000

Revised document for release as paper-based manual DOC810-20. Added Data Exchange and ORCAview PIC Statements sections to Chapter 9 Controller Networks. Fixed error in table for Event Object on page 44 of Chapter 11 General Control Language (GCL+). Fixed minor format and copy editing issues in all chapters. Add text to copyright allowing limited reproduction and distribution of the PDF electronic files in paper format.

1.10

April 3, 2001

Revised manual for Version 3.21 ORCAview. Released as PDF files only. Added new appendices for Derived Network Addressing (DNA) and Using ORCAview with Version 2 Sites. Added install information for Windows ME/2000 to Chapter1 Introduction. Added objects to Chapter 10 Software Objects Reference. Included a section describing special functions for use with Room Controllers, BACstats and LINKnet in Chapter 11 General Control Language (GCL+). Revised Appendix D MicroNet. Chapter 4 Tutorial has been excluded from this revision.

1.20

September 28, 2001

Revised manual for Version 3.22 ORCAview. Released as PDF files only. The DAC products can now do functions such as alarming, routing and data exchange formerly only found on a DCU. Revised objects in Chapter 10 Software Objects Reference to include additional BACnet features and also to update the additional objects (MI, MIC, TL, MT, SCH) fully supported by DAC products. Added Appendix G for Working with MS/TP and LINKnet and Appendix H Service Port Access. Included Adobe Catalog full-text index files for use with Acrobat Reader 5.0 with Search and Accessibility or Reader 4.05 with Search. Chapter 4 Tutorial has again been excluded from the revision.

1.30

May 1, 2004

Revised manual for ORCAview 330 Release 1. Released as PDF files only.

1.40

April 30, 2005

Revised manual for release with ORCAview 330 Release 2. Includes improved printing of objects and alarms

1.50

September 30, 2005

1.6

May 3, 2006

1.7

November 22, 2009

Supports Vista and Windows 7 plus multi-core processors. Support for DHMI, CON768BT Bluetooth converter and Embedded Web Server. New Navigator features include Software Version Mismatch and Description Column. Extensive changes to LG and HS objects. Includes MN and SD objects. Changes to DEV, SUA, and OS. Appendix F Service Port Access includes CON-768BT.

1.80

December 9, 2011

The headings of sections with significant changes have a green highlight. Document new suite installer that handles installation, upgrades and maintenance for up to six Delta software applications in a single install process. Dialogs, icons and overall look are updated throughout the product. Ch. 3 Navigator has updates to Bluetooth, Communication Control and Objects Security (Lock, Unlock and Temporary Logon). Include new enteliBUS hardware. Include Start graphic from a command line in a running graphic. Ch. 4 Tutorial is eliminated. Add new objects to Ch. 10: SCH BACnet R4 supports 3 types of values plus partial day scheduling, BDE, IPS, ORS, IOM, ZigBee® Wireless objects[x3] and SV. Add Intrinsic Alarming for AI, AO, BI, BO and MI. Significant changes to BMD, DEV, EVC, EVL, EVR, LG, LNK, Net, OS, PG, SSS plus Access Objects. Ch06 include support for multiple Historians. Ch. 11 includes new constructs: IntDate/IntTime, Read/Write, SetTime and ToSeconds. Update App. E and F plus increased PG size.

Chapter 1 – INTRODUCTION Chapter 1 Contents DESCRIPTION ....................................................................................................... 1–2 Matching Products for Release ............................................................. 1–2 SYSTEM REQUIREMENTS ...................................................................................... 1–3 SUITE INSTALLER FUNCTION ................................................................................ 1–4 Supported Scenarios ............................................................................. 1–4 Unsupported Scenarios ......................................................................... 1–6 OWS DEFAULT DIRECTORIES .............................................................................. 1–7 NEW INSTALLATION ............................................................................................. 1–7 Workstation Number ............................................................................. 1–8 Concise: Installation Procedure ........................................................... 1–9 To install Delta products from the ORCA Suite CD: .............. 1–9 To install Delta products from the desktop: .......................... 1–10 Detailed: Installation Procedure ........................................................ 1–11 To install ORCAview from the ORCAview CD: .................. 1–11 MS HTML Help ................................................................................... 1–18 UPGRADE INSTALLATION ................................................................................... 1–18 Upgrade Procedure............................................................................. 1–19 To upgrade ORCAview from the ORCAview 3.40 CD: ....... 1–19 COEXISTANCE INSTALLATION ............................................................................ 1–23 To coexist ORCAview from the ORCAview 3.40 CD: ........ 1–23 APPLICATION MAINTENANCE: ........................................................................... 1–27 Add/Remove Software ......................................................................... 1–27 Repair Software .................................................................................. 1–29 Uninstall Software............................................................................... 1–30 CONCISE INSTALLATION OF HISTORIAN ............................................................. 1–31 To install Historian from the ORCA Suite CD:..................... 1–32 To install Historian from the desktop: ................................... 1–32 Historian Install Microsoft SQL Server 2005 Setup ........................... 1–33 WINDOWS XP / WINDOWS 7 SENTINEL DRIVER UPDATE ................................... 1–39 To manually update the Sentinel driver from the ORCAview 3.40 CD: ....................................................... 1–39 CUSTOMIZING THE DESKTOP SHORTCUT FOR AUTOMATIC LOGIN ..................... 1–41 To create a shortcut for automatic ORCAview login: ........... 1–42 SYSTEM ARCHITECTURE .................................................................................... 1–43 Networking Information in Other Chapters ........................................ 1–43 Architecture Design ............................................................................ 1–44 Ethernet – BACnet MS/TP .................................................................. 1–45 Operator Workstation Connections .................................................... 1–46

Total Pages in this Section: 46

ORCAview Version 3.40 Technical Reference Manual Ed. 1.80 Original Page 1–1

1–2

Introduction

Thank you for buying the Delta Controls ORCAview® program. ORCAview operates in a graphical Windows world and has powerful facilities management tools. We trust that this product will satisfy your building control needs. We are continuing our efforts to more fully express the vision Integrated Facilities Management Solutions Simplified in the ORCAview product.

Description The ORCAview software is a native Windows® application and has been written to look and operate like most Windows applications. The operator can view project data graphically or with the interactive Microsoft Windows Explorer™ style Navigator. Both these interfaces to the DDC system provide real-time data to the PC, with updates as quick as five second if needed. Real-time data can be shown in a group of objects, single objects, multiple objects, on-line graphics, or in any combination. The user interface has an object-oriented design. This approach allows quick access to menus by just clicking on an object using the right mouse button. At the click of a button, the operator can change from viewing a graphic to editing the graphic using the optional Illustrator tool created by Delta Controls. This makes it easier to draw and test graphics. For more detailed information on the drawing program Illustrator, see the Illustrator Technical Reference Manual which is included on the release CD. ORCAview currently has four methods to access a DDC system through Windows networking. The LAN/WAN connections from the PC to the DDC system are: •

BACnet IP (UDP/IP)

•

BACnet Ethernet (10 Mbits/s)

•

BACnet MS/TP (Up to 76.8K Baud) PC to controller CON-768/ CON-768BT

•

BACnet PTP RS-232 (Up to 38.4Kbytes/s) Local and Dial-in/Dial-out

Matching Products for Release The following is a list indicating the matching builds of product for ORCAview V3.40 Build 3073 or later. •

ORCAview OWS (Build 3073)

•

ORCAweb™ (Build 3073)

•

Flash Loader (Build 3073)

•

System Loader (Build 3073)

•

Rainbow Sentinel Drivers (7.5.1 or later)

ORCAview Version 3.40 Technical Reference Manual Ed. 1.80 Original Page 1–2 Total Pages in this Section: 46

System Requirements •

DSC/DAC – BN155693

•

Tetra – EN155693

•

DFM /DRP– FM155693

•

V2 Micro – – RC114575

•

DCU – 340.3073

1–3

System Requirements To run the Delta Controls ORCAview® software, Delta Controls offers the following minimum requirements: Minimum Requirements Operating System

Windows XP 32 Pro; Server 2003/Win2K3; Vista 32/64 (Business, and Ultimate); 2008 Server; Windows 7 32/64 (Pro, Business and Ultimate).

Processor

Pentium or Athlon @ 1 GHz ORCAview supports multi-core processors.

RAM

at least 2 GB

Disk Drive

CD-ROM if installing from a CD, otherwise an electronic form can be used

Hard Disk Drive

2 GB of free space for ORCAview

Video Settings

1024 x 768 resolution with 16-bit color

Modem

USRobotics modem if dialup needed

Serial ports

COM Ports for PTP direct use and Service Port Access

USB Ports

For Service Port Access over a wireless connection

Windows 95, Microsoft Windows 98, Windows NT and Windows Millennium Edition (ME), are NOT supported. Windows 2003 and 2008 Server are supported for installing and running the ORCAweb product. Although ORCAview will run on many less capable machines, performance may be much slower in many cases (e.g., Multi-Trends), and you risk other performance-related problems. If any performance problems are encountered on PCs not meeting these specifications, the first recommendation will be to upgrade to a more suitable machine. To run the Delta Controls ORCAview™ software, Delta Controls offers the following recommended requirements: Recommended Specification


Operating System

Vista 32/64 (Business, and Ultimate); 2008 Server; Windows 7 32/64 (Pro, Business and Ultimate).

Processor

Intel Core 2 Duo – 2.6 GHz

RAM

4 GB+

Disk Drive

CD-ROM if installing from a CD, otherwise an electronic form can be used

ORCAview Version 3.40 Technical Reference Manual Ed.. 1.80 Original Page 1–3

1–4

Introduction

Hard Disk Drive

10 GB of free space

Video Settings

1280 x 1024 resolution with 32-bit color

Modem

USRobotics modem if dialup needed

Serial ports

COM Ports for PTP direct use and Service Port Access

USB Ports

For Service Port Access over a wireless connection

Suite Installer Function This section lists the scenarios that the V3.40 Suite Installer supports and the ones it does not. The aim is to provide information that helps to make the behavior of the installer clearer.

Supported Scenarios All scenarios will be supported for both default and custom install locations. If you change only the disk drive letter in a default path, ORCAview still treats the path as the default directory. For example, you might just change the C: to D: and leave the rest of the default path unchanged. A custom install is one that has the names in the default path changed. Note: All scenarios will be supported for both default and custom install locations.


Suite Installer Function

1–5

Supported Scenarios Case

See

Action

Clean Install

New Installation section on page 1–3

Suite installation with no existing Delta product installed

Suite Build-toBuilt upgrade

Upgrade Installation section on page 1–18

Upgrade ALL installed product from older build to latest build of the current version. All site specific files are upgraded if necessary.

E.g. 3.40.2159 suite -> 3.40.3073 suite Upgrading from a beta build is NOT recommended. Uninstall the Beta build and then re-install a released version.. Suite Version Upgrade

Suite Version Upgrade, keep previous OWS



Upgrade ALL installed product from older version to current version. All site specific files are upgraded.

E.g. 3.33.1917 suite -> 3.40.3073 suite If Historian is installed, it will not be possible to keep old OWS on upgrade. The old OWS is not upgraded. A new 3.40 OWS is installed alongside it. All other components are upgraded.

E.g. 3.33.1917 suite -> 3.33.1917 OWS and 3.40.3073 suite Coexistence of OWS only (with 3.40 now includes Coexistence of Loaders)

Coexistance Installation on page 1–23

Install the current version of OWS and Loaders alongside the existing older version suite (excluding Historian). Or, install the current version suite (excluding Historian) alongside the existing older version OWS and Loaders. No site specific files are upgraded. Both installations are treated as separate.

E.g. 3.33.1917 suite -> 3.33.1917 suite and 3.40.3073 OWS/SystemLoader *** *** Once in this configuration, and you want to upgrade your suite to 3.40, you must remove 3.40 OWS and Loaders and then upgrade your 3.33 suite. E.g. 3.33.1917 OWS/FlashLoader -> 3.33.1917 OWS/FlashLoader and 3.40.3073



1–6

Introduction

Supported Scenarios Case

See

Action

suite Complete Removal

Uninstall Software topic in Application Maintenance section on page 1–30

Modify Components, Add or Remove

Add/Remove Software topic in Application Maintenance section on page 1–27

Repair

Repair Software topic in Application Maintenance section on page 1–29

Uninstall ALL installed product of current Version only.

E.g. 3.40.3073 suite -> no product Add and/or Remove individual suite components to current installation of Delta product.

E.g. 3.40.3073 OWS and ORCAweb -> 3.40.3073 OWS and Historian If a malfunction occurs such as power failure and a software application no longer runs, it is possible to repair the installation quickly. The core files are refreshed and it is not necessary to do an uninstall / install of the software product and this approach saves time.

Unsupported Scenarios If the Suite Installer does not offer a particular install option, then this scenario is not allowed by the installer. Unsupported Scenarios Partial Build-to-Build upgrade resulting in mixed builds of the current version. Version Upgrade of versions older than 3.33 R2. Version Coexistence if Historian installed. Add or Remove components during an Upgrade. Upgrade of versions older than 3.33 R2. Those version would first need to be upgraded to 3.33 R2. Uninstall of older versions. Install mixed versions of various non-OWS/Loader products in the suite (e.g., 3.33 Web and 3.40 ODBC Driver).

In some cases, you would uninstall the Suite and then re-install it.


OWS Default Directories

1–7

OWS Default Directories The Install Path is consistent between Windows XP/Server2003/Vista/7. It depends on processor bit-width. If 32-bit, install directory will be: C:\Program Files\Delta Controls\3.40\ If 64-bit, install directory will be: C:\Program Files (x86)\Delta Controls\3.40\ The users/custom directory is different between Windows XP/Server 2003 and Windows Vista/7, however, it is consistent between processor bit-width. If Windows XP/Server 2003, user directory will be: C:\Documents and Settings\Public\Delta Controls\3.40\ If Windows Vista/7, user directory will be: C:\Users\Public\Delta Controls\3.40\ C:\Users\Public maps to the environment variable %PUBLIC%.

New Installation With 3.40, ORCAview has a suite installer which provides a choice of six applications to install. You may have a CD or downloaded folder with an executable install file named ORCA Suite Setup.exe. The Suite Installer handles multiple applications in one installation process. •


ORCAview 3.40 (includes Illustrator but needs to be enabled on a hardware key)

•

Delta Historian

•

ORCAweb

•

Delta ODBC Driver

•

Delta Flash Loader

•

Delta System Loader


1–8

Introduction In the previous figure, the checkbox for Delta ODBC Driver is Red indicating that the software key does not have this product enabled. You can still select this product for installation or press the Cancel button to exit. If installation is completed without the software key fully enabled, the disenabled products will not run.

Before you begin your installation you will need to do the following: •

Choose a directory – You may let the install program place ORCAview in the default directory or choose a different destination. See OWS Default Directories on page 1–71–7 If the directory does not exist, then the install program will create it.

•

Determine the name of the site. For example, you could enter International Airport.

•

Determine the name of the workstation on your local network. For example, you could enter Main ORCAview PC.

•

Determine the number of the workstation on the network. See the following section titled Workstation Number.

Workstation Number Every device on the same site must have a unique controller number. ORCAview calls this the workstation number. The PC that will receive the new ORCAview installation must have a unique workstation number. Note: Choose the workstation number carefully, as you must re-install the software to change it. To avoid conflicting workstation numbers, maintain a list of device numbers for large sites. Devices requiring unique numbers include the following: •

All connected Controllers or Workstations


New Installation

1–9

The PC where the new ORCAview is being installed must have a unique workstation number assigned to it. The workstation number must: •

be different than any other workstation number,

•

be different than any other controller address,

•

not be 0, 254, 65534 or 65535

•

not be greater than 4194302 if only V3 hardware

•

not be within any Micro Panel range.

Any V3 DCU that is used as an IP router to local V2 devices (DCU's or Turbos, etc) must be addressed lower than 32767. If the Version 2 protocol is being installed, the workstation number must: •

not be greater than 32766 (If greater than 32766, then a message on the dialog warns that this Workstation Address is invalid with Version 2 networks.)

•

not include any number from 250 to 255,

•

not be 999

If an invalid number is typed in during install, it will be increased to the next valid number or decreased if it cannot go any higher. For example, if you enter 254 for a workstation number for a site that has V2 Hardware, the system changes it to 256.

Concise: Installation Procedure

To install Delta products from the ORCA Suite CD:

•

Insert the CD. If the autorun brings up the interface, select the installer and follow the instructions to complete the installation process

OR: 1.


If the autorun does not bring up the interface, use the My Computer icon or the Explorer view to find the ORCA Suite Setup.exe file.


1–10

Introduction 2.

Double-click ORCA Suite Setup.exe file to start the Suite Installer.

3.

Follow the instructions from the Welcome screen to complete the installation process.

See the detailed Installation Procedure section starting on page 1–11 for more information. To install Delta products from the desktop:

1

Click on the ORCA Suite folder that you downloaded.

2

Use the My Computer icon or the Explorer view to find the ORCA Suite Setup.exe file.

3

Double-click the ORCA Suite Setup.exe file to start the Suite Installer.

4


See the detailed Installation Procedure section following on this page for more information.


New Installation

1–11

Detailed: Installation Procedure Note: If you plan to use Ethernet, install an Ethernet card before installing ORCAview. See the tables in the Suite Installer Function section starting on page 1–4 for supported and unsupported install scenarios. To install ORCAview from the ORCAview CD:

1.

Preliminary Steps

a.

Check that the programs identified on the software key are correct for the site. Use only the specific software key that came with the software for the site.

b.

Turn off the PC and attach a software key to your USB or Parallel port. When the key is attached, turn on the PC. •

USB Port: This software key that attaches to your USB port.

•

Parallel Port: This software key attaches to a Parallel port. Attach the software key, shown in the following figure, to the computer parallel port at the back of the PC. The thumbscrew heads should point away from the PC. The pins go into the computer parallel port plug.

Caution: Never remove or attach the software key to the PC while the power is on. The key may be damaged if this caution is not heeded.

Note: If a software key is not present at installation or a product is not enabled on the key (indicated by a Red checkbox), you have the option to proceed with the complete installation of the ORCA products or exit. If installation is completed without the software key, the products will not run.



1–12

Introduction

2.

c.

Exit all other programs.

d.

Insert the CD into the CD-ROM drive.

e.

Use the My Computer icon or Explorer to view the contents of the CD.

•

If the autorun brings up the interface: Select the installer and follow the instructions to complete the installation process. Go to step 2 of this procedure.

•

If the autorun does NOT bring up the interface: Find and open the ORCAview 3.40 in the Delta V3.40 Software Suite Installer software folder. Double click ORCA Suite Setup.exe file to start the Suite Installer.

f.

The install screen displays and the ORCAview installation starts.

Welcome screen. a.

At the Welcome screen, click Next.

b.

Check the dialog for a list of installed ORCA Suite software.


New Installation 2.

Application Maintenance (Check for installed ORCA software).

a. 3.

Click next.

Software License Agreement. a.


1–13

After reading the agreement, click Yes to accept the terms of the agreement.


1–14

Introduction 4.

Select Products

For this example, the ORCAview OWS, Delta Flash loader and Delta System loader are selected in the following figure. The other product options must be unchecked. A red checkbox (Delta ODBC Driver) indicates that a product is not enabled on the hardware key.


New Installation 5.

1–15

Chose Destination Folder.

a.

The install program chooses default folders for you. Click Browse to choose or create another folder.

Note: If you change only the disk drive letter in a default path, ORCAview still treats the path as the default directory. For example, you might just change the C: to D: and leave the rest of the default path unchanged. b. 6.

Click Next to continue.

Workstation Setup

a.

Enter the Site Name information. You must enter the Site Name.

b.

Enter a Workstation Name for ORCAview.

Note: The Site and Workstation Name fields do not allow invalid characters ( \ /:*?"’< >| $ #) and accept a maximum of 79 characters assuming an installation that uses the default path.



1–16

Introduction

7.

8.

c.

Enter your PC’s Workstation Number on the local network. The workstation number must be unique. See the workstation Number section on page 1–8 for more information.

d.


e.

If any entries are invalid, a warning message appears. The errors must be corrected before you can begin.

Ready to Install

a.

This dialog box shows the software selected for installation

b.

Click < Back if you wish to make any changes or review your decisions.

c.


Copying ORCAview Files. a.

A status bar shows the current status of the procedure. Files are now copied to your PC.


New Installation

b.

9.

1–17

If any special adapters are needed, or if any conflicts occur during installation, a message displays. Write down any such messages for future reference.

Setup Complete.

a.

All necessary files have been loaded onto your hard drive.

b.

Click finish to complete Setup.

The Installation Procedure is finished. You may need to read First Time Login Problems section on page 2–6 in Chapter 2 – Getting Started of the ORCAview Technical Reference Manual. Note: The firewall included with Windows XP may block the Siserver, when you first run ORCAview after installation. On the Windows Security Alert dialog, click Unblock to allow the Siserver program to run. This message will only appear when logging in via UDP/IP.



1–18

Introduction

MS HTML Help ORCAview now uses the MS HTML help format (.chm) and the viewer is included with Windows. Previously, it was necessary to download the non-distributable Winhelp viewer from a Microsoft site.

Upgrade Installation Caution: Although the Upgrade procedure will save site graphics and databases, we strongly recommend that you back up these items. Also back up any other files or objects you have created for your system.

Windows 95, Microsoft Windows 98, Windows NT and Windows Millennium Edition (ME) are NOT supported. Windows 2003and 2008 Server are supported for installing ORCAweb. During an upgrade, the installation program searches your computer for previous versions of the Delta Controls ORCAview. If the previous version is found to be incompatible with version 3.40, the installation program offers to uninstall the previous version. If you click Yes, the previous version is uninstalled. See the New Installation starting on page 1–7. If the previous version is found to be compatible with version 3.40, the installation program continues. See the tables in the Suite Installer Function section starting on page 1–4 for supported and unsupported install scenarios. Do the Upgrade Procedure that follows on this page. Note: Commander Version 3.10 cannot be directly upgraded to ORCAview Version 3.22, 3.30, 3.33 or 3.40.


Upgrade Installation

1–19

The 3.40 Suite Installer can only upgrade from 3.33. If you have an earlier version (3.20 to 3.30), you need to first upgrade to 3.33 using the 3.33 Installer. The 3.40 Suite Installer can handle the upgrade from 3.33 to 3.40. Note: If the palette, database or graphics files are large or numerous, the upgrade process could be lengthy. The upgrade process might take an hour depending on the size of the site and the performance of the PC.

Upgrade Procedure Note: If the user stops the Upgrade process by clicking Cancel, then all files are automatically restored to the original version by the Upgrade Installation program.

Note: If you plan to use Ethernet, install an Ethernet card before installing ORCAview. No special driver is needed to get Ethernet working as it uses the Windows drivers.

To upgrade ORCAview from the ORCAview 3.40 CD:

1.

Close all programs.

2.


3.


•

If the autorun brings up the interface: Select the installer and follow the instructions to complete the installation process. Go to step 2.

•

If the autorun does NOT bring up the interface: Find and open the ORCAview 3.40 in the Delta V3.40 Software Suite Installer software folder. Double click ORCA Suite Setup.exe file to start the Suite Installer.

•

If you want to do a New Installation, See Step 2 on page 1–12. a.


The Welcome screen displays and the ORCAview installation starts.


1–20

Introduction 4.

Welcome screen.

a. 5.


Setup

 If ORCAview detects an incompatible previous installation: •

You may need to upgrade from versions before 3.33 using the 3.33R2 installer which is included with the ORCA 3.40 suite.

•

You may also need to uninstall the current products and then re-install them.

–OR–  If ORCAview detects a compatible previous installation:


Upgrade Installation

1–21

In the following figure, 3.33.1917 can be upgraded to 3.40.3073


6.

The Ready to Upgrade dialog box appears. Click Next to continue the Upgrade procedure.

7.

Copying and Configuring Delta Controls ORCA Suite Files


1–22

Introduction a.

The install program now begins copying files to your PC. When all files are copied over to your PC, the install program upgrades any existing graphics, palettes, or panel database files. If the palette, database or graphics files are large or numerous, the upgrade process could be lengthy.

b.

The installation program shows the status of the file conversions and upgrades.

c.

All files should be successfully upgraded or converted.

d.

Click OK to continue.

10. Setup Complete

a.

Click Finish to complete Setup.

The Upgrade Procedure is finished. Note: The ORCAview Installation program will now remove SNS, UDP, and Tunnelling adapters from OWS databases during an upgrade. The OWS will re-create these adapters from the registry bindings automatically. This applies to upgrade of older pre 3.33R2 installations.


Coexistance Installation

1–23

Coexistance Installation Coexistance allows ORCAview Version 3.20/ 3.21/ 3.22/ 3.30/ 3.33 and 3.40 to be installed on the same computer. With Windows XP, 3.33 can co-exist only with 3.30 or 3.22a. ORCAview 3.40 does not support version independence which means that you cannot have more than one instance of ORCAview 3.40 running at the same time. See the tables in the Suite Installer Function section starting on page 1–4 for supported and unsupported install scenarios. Note: ORCAview Version 3.20/3.21/3.22/3.30/3.33 must be installed before ORCAview Version 3.40 can be installed as coexistance.

To coexist ORCAview from the ORCAview 3.40 CD:

1.

Close all programs.

2.


3.


•

If the autorun brings up the interface: Select the installer and follow the instructions to complete the installation process. Go to step 4.

•

If the autorun does NOT bring up the interface: Find and open the ORCAview 3.40 in the Delta V3.40 Software Suite Installer software folder. Double click ORCA Suite Setup.exe file to start the Suite Installer. The Welcome screen displays and the ORCAview installation starts.

4.

Welcome.

a.




1–24

Introduction 5.

6.

Application Maintenance: Detected ORCA Suite Software

a.

Select the second option "Install ORCA Suite (3.40.3073) product(s) alongside the existing product(s)".

b.

Click Next.

Select Products

a.

Select the products for installation and uncheck the one that you do not want installed.

b.

Click Next.


Coexistance Installation 7.

8.


1–25

Destination Folder

a.

Select the Program and data folders. You can just accept the default paths.

b.

Click Next.

Workstation setup

a.

Enter the workstation settings.

b.

Click Next.


1–26

Introduction 9.

Ready to Install

a.

Click Next to do the actions in the Ready to Install list.

b.

A dialog indicates that Windows is preparing to install the ORCA Suite.

c.

A dialog indicates the progress as Windows configures the ORCA Suite.

10. Setup Complete

a.

Click Finish to complete setup.


Application Maintenance:

1–27

Application Maintenance: The Suite Installer allows you to change your install by adding, removing, repairing or uninstalling selected software. In some situations, Application Maintenance options would be offered while running the suite. See the tables in the Suite Installer Function section starting on page 1–4 for supported and unsupported install scenarios.

Add/Remove Software


1.

In the following figure, the Add/remove 3.40 ORCA Suite software option is selected.

2.

Click Next.


1–28

Introduction 3.

Select the Products to install.

a.

To remove an application, uncheck the box so that the checkmark is removed. In this example, the Delta Flash Loader needs to be unchecked.

b.

Press the Next button.

Note: You cannot use the Add/remove option to uninstall the whole ORCA Software suite. At least one option must be selected. To uninstall the whole suite, you use the Uninstall your 3.40 ORCA Suite software option. The following figure shows that Flash Loader will be removed. The ORCAview OWS (333.1917) and (3.40.3073) will remain. 4.

Ready to Modify

a.

Click next to remove the selected products.


Application Maintenance:

1–29

Repair Software The Repair option provides a way to put the core files of a selected product back to their initial conditions. For example, if a product malfunction occurs after a power failure, Repair would refresh the core files quickly. It avoids the need to take the time to do a complete uninstall / re-install sequence. 1.

2.

Application Maintenance

a.

Select the repair option.

b.

Click Next.

c.

The Ready to Repair dialog appears.

Ready to Repair

a.


Click Nest if you wish to repair the list product(s).


1–30

Introduction

Uninstall Software Uninstall provides a way to remove selected software. 1.

2.

Application Maintenance

a.

Select the Uninstall option.

b.

Click Next.

c.

The Ready to Uninstall dialog appears.

Ready to Uninstall

a.

Click Next to begin removal of the listed software products.

b.

Wait until the Installer completes uninstalling the software.

c.

A dialog indicates that Windows is preparing to install the ORCA Suite.

d.

A dialog indicates the progress as Windows configures the ORCA Suite.


Concise Installation of Historian 3.

1–31

Setup Complete

a.

Click Finish.

Concise Installation of Historian With 3.40, ORCAview has a suite installer which provides a choice of six applications to install. The Suite Installer handles multiple applications in one installation process. See the tables in the Suite Installer Function section starting on page 1–4 for supported and unsupported install scenarios.

The releases build will be 3073 or later. This example uses Build 3.40.3051.



1–32

Introduction Note: With the ORCA 3.40 Suite Installer, you do NOT need to install OWS first and then log in over the desired network connection before beginning to install Historian. This approach was necessary with 3.33R2.

To install Historian from the ORCA Suite CD:

•

Insert the CD-ROM. If the autorun brings up the interface, select the installer and follow the instructions to complete the installation process

—OR — 1.

If the autorun does not bring up the interface, use the My Computer icon or the Explorer view to find the ORCA Suite Setup.exe file.

2.

Double-click ORCA Suite Setup.exe file to start the Suite Installer.

3.


To install Historian from the desktop:

1

Click on the ORCA Suite folder that you downloaded.

2

Use the My Computer icon or the Explorer view to find the ORCA Suite Setup.exe file.

3

Double-click the ORCA Suite Setup.exe file to start the Suite Installer.

4


Because Historian requires access to a large database, a Database Management System (DBMS) is included with Historian. The default DBMS included with 3.40 is Microsoft SQL Server 2005 Express which the installer prompts you to let it install automatically. If Microsoft SQL Server 2005 Express or SQL Server is already on the system, you may not need to install a DBMS.


Concise Installation of Historian

1–33

With Microsoft SQL Server 2005 Express, you need to define a strong password which means that the password contains a variety of character types. A strong password contains a combination of lowercase, uppercase, numbers and special characters such as $ or # etc.

Historian Install Microsoft SQL Server 2005 Setup 1


When you first install Historian, you may need to Install a database server. The default is Microsoft SQL Server 2005 Express.

a.

Enter a password.

b.

Click next.


1–34

Introduction 2

3

License Agreement

a.

Click the checkbox to accept the agreement.

b.

Click Next.

Installing Prerequisites

a.

Inspect the list of prerequisite components

b.

Click the Install button to continue.


Concise Installation of Historian c.

4


1–35

A dialog shows the progress on installing the prerequisites.

System Configuration Check

a.

Wait while the SQL Server Setup scans your computer.

b.

A dialog shows the progress in installing SQL components.


1–36

Introduction

5

Completing Setup

a.

Inspect the summary logs to see if any failures occurred during setup.


Concise Installation of Historian 6

7


1–37

Password

a.

Enter a password for DQL Server Express.

b.

Click the Install SQL Server Express button.

c.

Click Next.

ORCA Suite – Ready to Install

a.

Inspect the install list of ORCA software.

b.

Click Next.

c.

A dialog shows the progress of the install process.


1–38

Introduction 8

ORCA Suite

a.

Click Finish.

b.

Inspect the install list of ORCA software.


Windows XP / Windows 7 Sentinel Driver Update

1–39

Windows XP / Windows 7 Sentinel Driver Update You may need to manually update the Sentinel Driver System. The installer handles the initial installation of the Sentinel driver but not handle the upgrading of the Sentinel Driver. The 3.40 CD includes the version 7.5.1 Sentinel System Driver Installer in \Delta Software Suite - V3.40 Release 1.0\Delta V3.40 Software Suite Installer\Third Party Software. To manually update the Sentinel driver from the ORCAview 3.40 CD:


1

Close all programs.

2


3


4

Open the Delta V3.40 Software Suite Installer\Third Party Software folder on the release CD.

5

Find the Sentinel_System_Driver_Installer_7.5.1 file and double click it.

6

Sentinel System Driver – InstallShield Wizard

•



1–40

Introduction 7


•


8


In some situations, you may upgrade the Sentinel driver.


Customizing the Desktop Shortcut for Automatic Login •

Click Install to continue.

9


•

Click Finish to complete the installation of the Sentinel Drivers.

1–41

Customizing the Desktop Shortcut for Automatic Login These instructions create a desktop shortcut that allows automatic login to ORCAview. This icon automatically provides the username and password to ORCAview and bypasses the ORCAview security features. Caution: Do not use a shortcut providing automatic login unless you are certain the site does not need username and password security, or, that the username automatically logged in lacks permission to alter security objects such as the SUA and UA objects or objects otherwise important to site functions. When you use the shortcut for automatic login, the following objects will exist on your system:


•

A System User Access (SUA) object in the ORCAview PC that uses the automatic-login username and password. — If not, then you must create a SUA object in the ORCAview PC containing the username and password. (See the Creating a New User section in the System Security chapter.)

•

A System User Access (SUA) object in the Network Security Panel that uses the automatic-login username and password. — If not then you must create such a SUA object. (See the Creating a New User section in the System Security chapter.)

•

A Site Settings (SS) object in the ORCAview PC that uses the site-name. If not then you must create a SS object using the site name that you intend to enter for automatic login. You cannot alter an existing SS object. (See the Multiple Sites section in the Navigator chapter.)


1–42

Introduction To create a shortcut for automatic ORCAview login:

1.

Right click the ORCAview shortcut icon and click Properties. An ORCAview.exe Properties dialog will appear. Click on the Shortcut tab as shown.

"C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" 2.

In the Shortcut tab, there is a Target field that specifies the shortcut path. In Windows 7- 32 bit: "C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" In Windows XP: “C:\Program Files\Delta Controls\3.40\System\ORCAview.exe”. After the last quotation mark in the shortcut path, leave one space and then type the following information: user=username/password site=sitename. You place your username/password and sitename after the shortcut path in the target field. The modified target field will read:

For Windows 7 – 32 bit: "C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" user=username/password site=sitename. For Windows XP: "C:\Program Files\Delta Controls3.40\System\ORCAview.exe" user=username/password site=sitename.


System Architecture

1–43

Note: The username and password must not contain spaces. The

sitename may contain a space between the first and last letter of the sitename but must be in quotations. Example: site= “site name”. The following invalid characters cannot be used in the username, password, or site name: ! \ / * ? : “ ‘ < > | $ #

System Architecture System architecture is defined as the design of a communications system, which includes the hardware, software, access methods, protocols, and method of control. The following figures explain the ORCA hardware architecture and illustrate the use of Delta Control hardware in typical networks. •

Architecture Design

•

Ethernet – BACnet MS/TP

•

Operator Workstation Connections

Networking Information in Other Chapters See Chapter 9 — Controller Networks of this manual for a treatment of networking concepts and practices. See Appendix C — Derived Network Addressing (DNA) of this manual for a detailed explanation of the DNA addressing scheme included in ORCAview 3.30. Chapter 3 — Navigator provides a basic explanation of DNA. See Appendix E — Working with MS/TP and LINKnet of this manual to configure and program these products. See Appendix F — Service Port Access of this manual for an explanation of how to use ORCAview typically on a laptop to connect to a network using the Service Jack on a DAC, DSC or BACstat controller. Use of the CON-768 and newer CON-768BT converters is explained.



1–44

Introduction

Architecture Design The ORCA Hardware architecture is based on a hierarchical design. This allows for simple and efficient communications in large Wide Area Networks and small stand-alone systems. The ORCA® architecture is extremely flexible and can be built up in a variety of configurations. There are four levels to the ORCA hardware architecture: AREA level, SYSTEM level, SUBNET level, and LINKnet level. AREA Level controllers are primarily used to break-up large segments of a WAN. One controller per segment may be configured as an AREA Level controller.

AREA Level

DSC-1212E, DSC-1616E, DSC-1280E, DSM RTR

SYSTEM Level

SUBNET Level

LINKnet Level


System Architecture

1–45

SYSTEM Level controllers are used to logically distribute networks into manageable building segments. SYSTEM Level Controllers are I/O controllers for major equipment systems such as AHU’s. SYSTEM Level controllers have Real-Time Clocks, EIA-232 serial ports, and battery backup. This will allow the individual segments to function normally if network cabling is damaged and communications between SYSTEM Level controllers is not possible or interrupted. Only DSC and DSM model controllers can be placed at the SYSTEM Level. Any DSC model can have a subnet of controllers beneath it. DAC model controllers cannot be installed in the SYSTEM Level.

Ethernet – BACnet MS/TP The following architecture illustrates the flexibility of the Delta ORCA Native BACnet control system. Here, two SYSTEM level controllers have the Ethernet option. This allows them to route from Ethernet to BACnet MS/TP at both the SYSTEM Level (NET1 MS/TP port) and the SUBNET Level (NET2 MS/TP port). OWS 3.40 supports the newer enteliBUS™ family of controllers including the enteliTOUCH™ HMI and associated enteliBUS hardware.

Ethernet

DSC

DSC

DSC

Subnet Level

LINKnet Level

DAC DAC LINKnet Newtork communicating @ 76.8 Kbaud

DACs

BACnet MSTP Network

DSC-1616E or DSC-1212E or DSC-1280E or DSC-1616EX

BACnet MSTP Network

System Level

BACnet MSTP Network

BACnet MSTP Network

DNS-24

DFM-202



1–46

Introduction

Operator Workstation Connections This diagram shows the possible workstation connections. A distinctive connection point is the BACstat Service Port. Using Delta’s 232/485 converter (CON-768) or the newer CON-768BT you can connect any laptop running ORCAview software to the BACstat Service Port and see the entire Delta Controls Network. This simplifies commissioning and troubleshooting, allowing the Engineer to connect a workstation through a BACstat® near the problem area. There are also several standard connection points such as EIA-232 ports using BACnet PTP, directly or through a modem. ORCAview connects directly to the Ethernet network through a Standard Ethernet Network Interface Card connected to the ORCAview PC. It is also possible to use ORCAview to connect to the network across the Internet using BACnet/IP protocols There is a service port on most Delta ORCA hardware. This service port supplies power to the EIA-232/485 converter (CON-768) or wireless Bluetooth to wired RS-485 CON-768BT converter so that the operator does not have to provide a separate power supply for powering the converter. ORCAweb and the newer enteliWEB™ provide additional means to access a network. Ethernet

Modem

DSC-1616E, DSC-1212E, DSC-1280E, DSC-1616EX, DSM RTR

BACnet MSTP connection through the Service Port using Delta's CON-768 (EIA-232 / EIA-485 Converter)

BACnet MSTP Network

INTERNET

Laptop computer Workstation


LINKnet Newtork communicating @ 76.8 Kbaud

Laptop computer

Workstation

IBM Compatible


DNS-24 Object created virtually in Device 101

DFM-202 Object created virtually in Device 101


Laptop computer

Chapter 2 – GETTING STARTED Chapter 2 Contents OVERVIEW ........................................................................................................... 2–2 STARTING ORCAVIEW ........................................................................................ 2–2 Logon Dialog Box ................................................................................. 2–3 To log on to ORCAview: ........................................................ 2–4 Logon Dialog: Advanced Button Connections ...................................... 2–5 Multiple Connections .......................................................................... 2–12 OWS DIRECTORY CONVENTIONS ...................................................................... 2–13 CUSTOMIZING THE DESKTOP SHORTCUT FOR AUTOMATIC LOGIN ..................... 2–14 To create a shortcut for automatic ORCAview login: ........... 2–14 START GRAPHIC THROUGH A COMMAND LINE ................................................... 2–16 SOLVING FIRST TIME LOGON PROBLEMS ........................................................... 2–17 Windows XP Firewall Blocks Siserver ................................................ 2–17 Controller Turned Off ......................................................................... 2–17 To access your network: ........................................................ 2–18 ORCAview PC is Not Properly Connected to the Controller.............. 2–18 Incorrect Ethernet Card Selected........................................................ 2–18 Delta Version 2 Protocol is not Enabled ............................................ 2–18 To manually enable Version 2 Security and designate a Security Panel: ................................................................. 2–19 IDENTIFYING MAIN COMPONENTS OF ORCAVIEW ............................................ 2–20 ORCAview Dashboard ........................................................................ 2–20 To set the ORCAview Preferences: ....................................... 2–21 Navigator ............................................................................................ 2–26 Delta Server ........................................................................................ 2–26 To see the Delta Server operation: ........................................ 2–27 General Control Language ................................................................. 2–27 Illustrator ............................................................................................ 2–27 GETTING HELP ................................................................................................... 2–28 MS HTML Help ................................................................................... 2–28 To read or print the help files: ............................................... 2–29 ADJUST TIME ..................................................................................................... 2–30 Set Time and Date in Windows for the PC .......................................... 2–30 To set the Windows Date and Time: ..................................... 2–30 Check Controller Time ........................................................................ 2–31 To check the time on a particular controller: ......................... 2–31 To send the current PC Time to all controllers:..................... 2–32 EXITING ORCAVIEW ......................................................................................... 2–32 To exit ORCAview: .............................................................. 2–33 To Log on ORCAview as another user or through another network connection: ........................................................ 2–33

Total Pages in this Chapter: 33


2–2

Getting Started

Overview This chapter covers: •

Starting ORCAview on page 2–2

•

Logon Dialog: Advanced Button Connections starting on page 2–5

•

Multiple Connections starting on page 2–12

•

Start Graphic through a Command Line on page 2–16

•

Solving First Time Logon Problems on page 2–17

•

Identifying Main Components of ORCAview on page 2–20

•

Getting Help on page 2–28

•

Exiting ORCAview on page 2–32

You need to connect power and communications to the controller before you start ORCAview. Chapter 8 – Modems and Printers provides wiring diagrams to ensure that the controller is wired properly. The Chapter also describes how to make different types of cables.

Starting ORCAview This section discusses two methods of starting ORCAview. The ORCAview Installation program creates the first method. Note: The firewall included with Windows XP may block the Siserver, when you

first run ORCAview after installation. On the Windows Security Alert dialog, click unblock to allow the Siserver program to run. This message will only appear when logging in via UDP/IP.

First Method  After installation, click the Start Button in the lower left corner of the screen. When you click the Start button, the Start Menu appears. Choose All Programs, select Delta Controls, select 3.40, and then click ORCAview. The computer displays a Windows 7 desktop similar to the following figure:

ORCAview Version 3.40 Technical Reference Manual Ed. 1.80 Original Page: 2–2


Starting ORCAview

2–3

Click the ORCAview program. ORCAview then displays the Logon dialog box. See Logon Dialog Box on page 2–3. Second Method  You can start ORCAview from the ORCAview icon on the desktop. Double click on the icon to start ORCAview.

Logon Dialog Box

The Logon dialog contains the following fields: Username  Enter a name that corresponds to an SUA object. Password  Enter the password for the SUA object entered in the Username field. Site  A drop-down provides a list of the available choices. A Site Settings (SS) object defines login parameters for each site. Connection  The network settings include details such as the communications port, the network speed and the type of network connection. The network connection settings are configured during installation and shown at the bottom of the dialog box.


ORCAview Version 3.40 Technical Reference Manual Ed.1.80 Original Page 2–3

2–4

Getting Started To log on to ORCAview:

1.

When the Logon Dialog box displays, type your Username and Password. Your supervisor or the person who installed the ORCAview system assigns your Username and Password.

2.

Click OK on the Logon dialog box. ORCAview starts up as shown in the following figures. If this is your first-time logging-on, and no connection is made, see Solving First Time Logon Problems section on page 2–17 of this chapter.

The following Windows figure shows three main components: •

ORCAview Dashboard

•

Navigator

•

Delta Server Icon

ORCAview Dashboard

Navigator

Delta Server Icon The ORCAview Dashboard  In the previous figure, the Dashboard displays the site name which is International Airport. The Dashboard contains a menu bar and toolbars for controlling ORCAview. Navigator  Navigator is used to monitor and make adjustments to your control system. Using easily-identified software objects within Navigator, you can do most site functions, including alarming, trending, scheduling, and adjusting setpoints. Delta Server Icon  The Delta Server Icon indicates that the Delta Server is operating. The Delta Server processes information from BACnet or Version 2 networks. The page Identifying Main Components of ORCAview section of this chapter starting on page 2–20 contains more details about these components.



Starting ORCAview

2–5

Logon Dialog: Advanced Button Connections Advanced Button  The Advanced button on the Logon Dialog allows you to change the type of connection used to log onto your site. The selected connection type is shown at the bottom of the dialog box to the right of the Connection name. The Advanced button is grayed out if Historian or ORCAweb is already running on the PC. Note: Click on the Advanced button to see other communication parameters.

Place the cursor in a field and then press F1 to get help.

In the previous figure, ORCAview uses the Ethernet card(s) already installed through Windows. Connect Using Options  The available Connect Using options are: • • • • • •


Ethernet (Can have more than one Ethernet card) on this page Bluetooth: BACnet MS / TP on page 2–6 Serial (BACnet MS/TP) on page 2–7 Serial (BACnet PTP) [Direct, Modem Dial-out, Modem Answer] on page 2–8 Serial (Version 2) on page 2–10 UDP/IP (Local network, Remote network) on page 2–11


2–6

Getting Started

Connect Using Ethernet Options

This connection uses the Ethernet card(s) that were installed by Windows. With an Ethernet connection, there are no parameters to configure. You do need to ensure that the correct Ethernet card is selected. To reconfigure ORCAview with multiple connections, the network setup must be modified using the BACnet Protocol Settings (BCP) object once you are logged in. See the Multiple Connections section starting on page 2–12.

Bluetooth: BACnet MS / TP

With Bluetooth: BACnet MS/TP selected in the Connect Using dropdown, the following fields display on the dialog. Bluetooth BACnet MS/TP is selected when connecting OWS via wireless Bluetooth CON-768BT.



Starting ORCAview

2–7

If you click on the Add New Con768BT button, the Add Bluetooth Device Wizard from Windows opens. COM Port  This field defines the COM port for communications. Only valid virtual COM ports associated with the CON-768BT are listed in the Com Port Drop down menu when Bluetooth: BACnet MS/TP is selected. Address  For a Bluetooth: BACnet MS/TP connection, an editable Address box displays to the right of the Speed dropdown. This is the address the OWS will use on the MS/TP network and must be a unique address on the particular MS/TP network that the OWS is connecting to. A value of 0 to 127 can be entered in this field. The default value is 127. You can use any number in this field as long as it is not used by another device on the MS/TP network. It is suggested to use a restricted range of 100 to 127 for this field which will help to ensure that the OWS address does not conflict with any controller communicating on the MS/TP network. This field maps directly to the Address field under the MS/TP Protocol on the Setup tab of the BACnet Protocol Settings (BCP) object in the OWS. Serial 1 (BACnet MS/TP)


With Serial BACnet MS/TP selected in the Connect Using dropdown, the following fields display on the dialog. Serial BACnet MS/TP is selected when connecting OWS via wired CON-768.


2–8

Getting Started COM Port  This field defines the COM port for communications. Only valid detected COM ports are listed in the Com Port Drop down menu when Direct Connection type or MS/TP is selected. These do not include virtual COM ports associated with the CON-768BT. Speed  The choices for communication speed are 9600, 19200, 38400, and 76800. The default is 76800. Address  For an MS/TP connection, an editable Address box displays to the right of the Speed dropdown. This is the address the OWS will use on the MS/TP network and must be a unique address on the particular MS/TP network that the OWS is connecting to. A value of 0 to 127 can be entered in this field. The default value is 127. You can use any number in this field as long as it is not used by another device on the MS/TP network. It is suggested to use a restricted range of 100 to 127 for this field which will help to ensure that the OWS address does not conflict with any controller communicating on the MS/TP network. This field maps directly to the Address field under the MS/TP Protocol on the Setup tab of the BACnet Protocol Settings (BCP) object in the OWS.

Connect Using Serial: BACnet PTP Options

Following the Login process, the network objects in the OWS are automatically re-configured to reflect the desired BACnet modem connection. The objects affected are the BACnet Protocol Settings (BCP) object, the Version 2 Protocol Settings (V2P) object, the Serial (RS-232) Port Settings 1 (SNS) object, and the Remote Panel Settings (RPS) object. The new settings that will be applied when you log in are shown in the following dialog:

Connect Using  With Serial, the options are either Serial BACnet MS/TP, Serial BACnet PTP or Serial Version 2. Connect Type For BACnet PTP  The options are Direct, Modem Dial-out or Modem Answer.



Starting ORCAview

2–9

COM Port  This field defines the COM port for communications. The options are Com1-Com4. Speed  The choices for communication speed are 9600, 19200, 38400, 57600, 76800, 115200. The default is 9600. Chapter 8 – Modems and Printers of the ORCAview Technical Reference manual describes how to use the Advanced Button options of the Logon dialog for a serial modem connection. The following figure shows the Connect Using field with Serial 2 (BACnet PTP) and the Connect Type field with Direct selected.

The following figure shows the Connect Using field with Serial 2 (BACnet PTP) and the Connect Type field with Modem Dial-out selected.



2–10

Getting Started Phone Number  The phone number for the device that is to be dialed. This field accepts the Area Code and the Long distance prefix. Communications are established with a device using a Modem Dial-out when the phone number is dialed. The following figure shows the Connect Using field with Serial 2 (BACnet PTP) and the Connect Type field with Modem Answer selected.

The following figure shows the Connect Using field with Serial 3 (Version 2) and the Connect Type field with Direct selected.



Starting ORCAview

2–11

Connect Using UDP/IP Option

The following figure shows the Connect Using field with UDP/IP and the Connect To field with Local Network selected.

Connect Using  With UDP/IP selected, the following fields are available. The IP address is for the PC Ethernet card. This Ethernet address is stored in the UDP/IP Settings (UNS) object but cannot be changed there. Connect Type For BACnet PTP  The options are Direct, Modem Dial-out or Modem Answer. UDP/IP Port  The port defines which UDP port number that UDP/IP communication will use. The available range is 0 to 65535 with 47808 being the default. These port numbers are assigned by Internet standard with 47808 being assigned for the use of BACnet networks. It is important that this port number is not changed arbitrarily as many of the other port numbers have other purposes that would conflict with BACnet. All devices on the same UDP/IP network must use the same Port number.



2–12

Getting Started Select Remote network in the Connect to field and enter a Remote Panel IP Address

Remote Panel IP Address  This field becomes available when Remote network is selected in the Connect To field. This is the IP Address of the remote BBMD device.

Multiple Connections ORCAview can connect to different networks using separate connections. For example, your PC might use two Ethernet cards at the same time. Multiple connections are enabled in the Network Settings (NET1) Object for a DAC/DSC controller or the Setup tab of the BACnet Protocol Settings (BCP) object for an older DCU controller.

Note: If ORCAview is configured with multiple connections, clicking the

Advanced button will clear the multiple selections immediately. To reconfigure ORCAview with multiple connections, the network setup must be modified using the BACnet Protocol Settings (BCP) object once you are logged in.



OWS Directory Conventions

2–13

The following Warning Message will appear if you click on the advanced button on the Logon dialog. This message explains that by clicking the advanced button, all Network adapters except for one will be disabled. You will not be able to enable more than one network adapter when using the Advanced button dialog. If you wish to re-enable multiple network adapters, you can do so via the local BCP object when the OWS is started.

The Advanced button is grayed out if Historian or ORCAweb is already running on the PC.

OWS Directory Conventions The Install Path is consistent between Windows XP/Server2003/Vista/7. It depends on processor bit-width. If 32-bit, install directory will be: C:\Program Files\Delta Controls\3.40\ If 64-bit, install directory will be: C:\Program Files (x86)\Delta Controls\3.40\ The users/custom directory is different between Windows XP/Server 2003 and Windows Vista/7; however, it is consistent between processor bit-width. If Windows XP/Server 2003, user directory will be: C:\Documents and Settings\Public\Delta Controls\3.40\ If Windows Vista/7, user directory will be:



2–14

Getting Started C:\Users\Public\Delta Controls\3.40\ C:\Users\Public maps to the environment variable %PUBLIC%.

Customizing the Desktop Shortcut for Automatic Login These instructions create a desktop shortcut that allows automatic login to ORCAview. This icon automatically provides the username and password to ORCAview and bypasses the ORCAview security features. Caution: Do not use a shortcut providing automatic login unless you are certain the site does not need username and password security, or, that the username automatically logged in lacks permission to alter security objects such as the SUA and UA objects or objects otherwise important to site functions. When you use the shortcut for automatic login, the following objects will exist on your system: •

A System User Access (SUA) object in the ORCAview PC that uses the automatic-login username and password. — If not, then you must create a SUA object in the ORCAview PC containing the username and password. (See the Creating a New User section in the System Security chapter.)

•

A System User Access (SUA) object in the Network Security Panel that uses the automatic-login username and password. — If not then you must create such a SUA object. (See the Creating a New User section in the System Security chapter.)

•

A Site Settings (SS) object in the ORCAview PC that uses the site-name. If not then you must create a SS object using the site name that you intend to enter for automatic login. You cannot alter an existing SS object. (See the Multiple Sites section in the Navigator chapter.)

To create a shortcut for automatic ORCAview login:

1.

Right click the ORCAview shortcut icon and click Properties. An ORCAview.exe Properties dialog will appear. Click on the Shortcut tab as shown.



Customizing the Desktop Shortcut for Automatic Login

2–15

"C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" 2.

In the Shortcut tab, there is a Target field that specifies the shortcut path. In Windows 7- 32 bit: "C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" In Windows XP: “C:\Program Files\Delta Controls\3.40\System\ORCAview.exe”. After the last quotation mark in the shortcut path, leave one space and then type the following information: user=username/password site=sitename. You place your username/password and sitename after the shortcut path in the target field. The modified target field will read:

For Windows 7 – 32 bit: "C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" user=username/password site=sitename. For Windows XP: "C:\Program Files\Delta Controls3.40\System\ORCAview.exe" user=username/password site=sitename.

Note: The username and password must not contain spaces. The sitename may

contain a space between the first and last letter of the sitename but must be in quotations. Example: site= “site name”. The following invalid characters cannot be used in the username, password, or site name: ! \ / * ? : “ ‘ < > | $ #



2–16

Getting Started

Start Graphic through a Command Line The command line structure now supports a new graphic launch command. When ORCAview is running, a new graphic can be launched through Run... using the CMD prompt. This new graphic command can also be added to the target field in a desktop shortcut for ORCAview. This new option in the form of: graphic=mystartgraphic.gpc

For example, a valid desktop shortcut might be:

For Windows 7 – 32 bit:

"C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" graphic=Gauges.gpc

For Windows XP:

"C:\Program Files\Delta Controls\3.40\System\ORCAview.exe" graphic=Gauges.gpc

If no path is provided, the system searches the default locations. Alternatively you can specify a path.

With Windows 7 – 32 bit, the default location might be:

C:\Users\Public\Delta Controls\3.40\Sites\International Airport Terminal 1\Graphics

With XP, the default location might be:

C:\Documents and Settings\Public\Delta Controls\3.40\Sites\International Airport\Graphics

If you use spaces you must use double quotes to enclose the part with spaces. graphic=”my start graphic.gpc” For example, a valid desktop shortcut might be: For Windows 7 – 32 bit: "C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe" graphic="Propane Gas Gauges.gpc" For windows XP: "C:\Program Files\Delta Controls\3.40\System\ORCAview.exe" graphic="Graphic with Basic Shapes.gpc" For a programmer, this feature allows an outside script to determine what graphic to load. You can use a macro to open a particular graphic based on conditions. This behavior is not dependent on a predefined SUA. A graphic can be launched from outside the OWS. For example, from the CMD prompt: Orcaview.exe graphic=mygraphic1.gpc Orcaview.exe graphic=mygraphic2.gpc Orcaview.exe graphic=mygraphic3.gpc

The previous code will launch the OWS if it is not already running and open these three specified graphics. If a starting graphic is also defined in the User Data tab of the SUA object for a user, both graphics opens when OWS is started from a shortcut but the command line graphic opens on top and has focus.



Solving First Time Logon Problems

2–17

Solving First Time Logon Problems The first time you log in to your network after installing ORCAview, you may be unable to immediately view your network. These are some possible causes: •

Windows XP Firewall Blocks Siserver

•

Power to the controller(s) was turned off at login

•

ORCAview PC is not properly connected to the network or controller(s)

•

For Ethernet, incorrect Ethernet card is selected

•

For a serial connection, Baud Rate or COM Port may be incorrect

•

Delta Version 2 Protocol is not enabled

Windows XP Firewall Blocks Siserver The firewall included with Windows XP may block the Siserver, when you first run ORCAview after installation. On the Windows Security Alert dialog, click unblock to allow the Siserver program to run. This message will only appear when logging in via UDP/IP.

Controller Turned Off You will be unable to see your network if you only have one controller on your network and the controller is turned off when you try to log in. Turning on the controller after ORCAview has started will not immediately allow you to log into the network. You need to re-initialize the Descriptors to get the controller to appear.



2–18

Getting Started To access your network: 1. Click File on the ORCAview menu bar, and select Logoff. When the message box appears stating that all ORCAview windows will close click Yes. A login

dialog box appears.

2.

Turn on the controller.

3.

Log in to ORCAview using the Logon dialog box.

ORCAview PC is Not Properly Connected to the Controller Chapter 8 Modems and printers provides wiring diagrams to ensure that the controller is wired properly.

Incorrect Ethernet Card Selected Make sure that you have the correct Ethernet card selected. On the Logon dialog, press the Advanced button and select the card in the Connect Using field.

Delta Version 2 Protocol is not Enabled By default, for new installations, ORCAview will assume that the Version 2 protocol is disabled. When you enter the login name and password, ORCAview provides access to ORCAview alone. It will not allow access to any of the Version 2 devices on the network. If you want access to a V2 controller on a network, you must manually enable the Version 2 protocol and designate a V2 panel as the Security Panel.



Solving First Time Logon Problems

2–19

To manually enable Version 2 Security and designate a Security Panel:

1.

From the ORCAview Dashboard, choose Tools. Select Setup and click on Site. The Site Settings object displays.

2.

Click the Advanced tab and change the Security Panel number to match a panel on your network.

3.

Click the Application Protocol and enable the Delta Version 2 Protocol check box.

4.

Click OK.

5.

Exit ORCAview. Wait five seconds for the Delta Server to unload. Restart ORCAview. You can now access your network.

Enter the address of your V2 Security panel here. Enter the address of your BACnet Security panel here.

The following section explains the main components of ORCAview in more detail.



2–20

Getting Started

Identifying Main Components of ORCAview This section introduces the main components of ORCAview. Each component has a specific function for building control. The main components of ORCAview are: •

ORCAview Dashboard on this page

•

Navigator starting on page 2–26

•

Delta Server starting on page 2–26

•

General Control Language Editor starting on page 2–27

•

Illustrator Graphic Program starting on page 2–27

ORCAview Dashboard From the ORCAview Dashboard, you can start all the components of ORCAview. Whenever ORCAview runs, the Dashboard displays on your screen. The Dashboard also displays the menus for other components. ORCAview Dashboard

Standard Dashboard

Menu Bar

PC / System Time

When the Dashboard first opens, it displays the standard dashboard and menu bar. The Dashboard always displays the PC time in the lower right hand corner. To change the time displayed, you must go through the Windows settings. See the Adjust Time section starting on page 2–30 of this chapter for more details. Docking  You can place the Dashboard along the top or bottom side of the monitor where it displays as a solid bar. The Dashboard is docked when it displays as a solid bar along the top or bottom side of the monitor. You can combine docking with other display options such as Always on Top or Autohide. The ORCAview Preferences dialog box allows you to select these options.



Identifying Main Components of ORCAview

2–21

To set the ORCAview Preferences:

1.

From the ORCAview Dashboard, click Tools.

2.

Select Preferences and then click ORCAview. The following dialog box opens. Select your preferences by clicking the checkboxes.

In the previous figure, the Windows 7 Graphic Path is: C:\Users\Public\Delta Controls\3.40\Sites\International Airport Terminal 1\Graphics\

3.

4.


Set the following display preferences at this time: •

Always on Top: Select this option to always place the ORCAview Dashboard on top of any other programs currently running.

•

Auto Hide: When the Dashboard is docked against the top or bottom edge of your screen, it is automatically hidden unless you place your mouse at that edge of the screen.

•

Show Navigator on Startup: The Navigator always open when you start ORCAview.

Click OK to close the ORCAview Settings dialog box and save your settings.


2–22

Getting Started Dashboard Menus  The ORCAview Dashboard has the following main menus: •

File

•

Edit

•

Search

•

View

•

Tools

•

Window

•

Help

The Dashboard File Menu provides the following commands: •

Create New panel object, site graphic, view, report, user, and site.

•

Open object dialog and site graphic.

•

Saving and loading databases, and importing and exporting files.

•

Save as Web Page available in Illustrator mode with a site graphic file open

•

Save as HMI Page available in Illustrator mode with a site graphic file open

•

Print, Print Preview and Print Setup.

•

Recent File List.

•

Logoff and Exit.




2–23

The Dashboard Edit Menu provides the following commands: •

Cut

•

Copy

•

Paste

•

Delete

•

Select All

The Dashboard Search Menu allows you to find text and objects.



2–24

Getting Started The Dashboard View Menu provides the following commands: •

Select which toolbars are visible.

•

Select ORCAview status bar to be visible or invisible.

•

How Navigator organizes Networks.

•

How Navigator displays objects.

•

Filtering.

•

Refresh.




2–25

The Dashboard Tools Menu provides the following commands: •

Set Controller Time

•

Set Password

•

Convert Graphics (Convert V2 Graphics, Convert Graphics to Web pages)

•

Controls system setup

•

Command outputs plus Communication Control… and Reconfigure

The Dashboard Window menu selects which windows are currently active. The Dashboard Help menu provides access to the Help File and contains important version information about ORCAview. See the Getting Help section of this chapter starting on page 2–28. Menu Changes  When components of the ORCAview program are open, the Dashboard menu changes to match the currently selected component. For example, when Navigator is open, the Dashboard menu provides access to the Navigator functions. When Illustrator is open, the Dashboard menu includes a Drawing Menu as well as changes to existing menu items.

ORCAview

Menu Change

Navigator


Menu Change

Menu Change

GCL Editor

Illustrator


2–26

Getting Started Taskbar Icons  When ORCAview is operating, icons are placed in the Windows Taskbar to tell you of other components that are running. Taskbar Icon

Meaning Shows that an active alarm is present. Shows that the Delta Server is running.

Navigator Navigator displays system information and provides operator interface to building equipment. Navigator is a component of the ORCAview. See Chapter 3 – Navigator of the ORCAview Technical Reference Manual for details. Filter Box

Delta Server The Delta Server provides ORCAview with a link to the outside world. The DDE (Direct Data Exchange) also use the Delta Server as a communication link. The server routes information from the network to ORCAview. All requests for information or commands affecting objects on the Delta Controls network pass from ORCAview to the server and out into the network. Whenever the Delta Server is running, an icon appears in the tray of the Windows taskbar on the lower left.

Delta Server Icon




2–27

To see the Delta Server operation:

1.

Right click on the server icon in the taskbar.

2.

Select Server Windows and then click Status.

Other commands available on this right click menu are as follows: •

Descriptors – Displays memory used by the Descriptors and provides option to reinitializes Descriptors.

•

About – Displays version and build numbers.

•

Exit Delta Server.

General Control Language The General Control Language (GCL+) Editor is used for creating, editing and displaying GCL+ programs. The editor displays GCL+ code using colors that depend on the particular GCL+ keywords in each program line. The use of color helps to clarify the structure of the GCL+ programs. The Editor provides line by line checking of syntax. The use of the GCL+ Editor is described in Chapter 11, General Control Language (GCL+).

Illustrator Use the Illustrator software module to create site graphics that display building information. Illustrator graphics also include graphical controls for starting and stopping equipment and adjusting heating and cooling. Illustrator is an optional software module available from Delta Controls. A separate Illustrator Technical Reference Manual explains the use of Illustrator.



2–28

Getting Started

Getting Help In ORCAview, online help is always available. To get help for any part of the program, press F1 on your keyboard. A help screen opens and provides help for your current task. Help is also available from the entry fields of most dialog boxes. To get help, you place the cursor in the entry field and press the ? help button. When using the GCL+ Editor, help is available for every GCL+ program element. You place the cursor on the program element and press F1 on your keyboard.

Place the cursor in any entry field and press F1

Click the Help button

MS HTML Help ORCAview now uses the MS HTML help format (.chm) and the viewer is included with Windows. Previously, it was necessary to download the non-distributable Winhelp viewer from a Microsoft site.



Getting Help

2–29

To read or print the help files: 1. Click Help on the ORCAview Dashboard. Choose Help Topics from the

drop-down menu.

2.

Select Contents (or Index). A window opens, and the display shows topics arranged in books by subject. See the following figure.

3.

To read a help file, double click on a book or topic.

4.

To print a help file, right click on any book or topic and click the Print… button.

Book

Topic



2–30

Getting Started 5.

When you click Print…, the following submenu displays. Select one of the two options to either print a single selected topic or to print all the topics in a book.

Adjust Time ORCAview uses the Date/Time that you set in Windows. The Set Panel Time command on the Tools menu of the Dashboard sends the current Date/Time to all the controllers on the Network.

Set Time and Date in Windows for the PC ORCAview uses the time produced by the PC. The time and date for the PC is set from the Windows® control panel. To set the Windows Date and Time:

1.

From the Windows Start button, choose Settings.

2.

Select Control Panel and double click on Date/Time.



Adjust Time

2–31

You could also display the Date/Time Properties by: •

Double clicking on the time in the task bar.

-OR•

Right clicking on the time in the task bar and selecting Adjust Date/Time.

Check Controller Time You may want to confirm the time on a particular controller. A Schedule that uses the time on a controller may not run at the expected time. Over the course of a year, an offset may have developed between the Controller Time and actual time. You can confirm the controller time by opening the Device (DEV) object for a controller and selecting the Time Info tab.

To check the time on a particular controller:


1.

In Navigator, select a controller in the left pane.

2.

Then open the Device (DEV) object for the controller in the right pane of Navigator.

3.

Click on the Time Info tab.


2–32

Getting Started Send PC Time to All Controllers  The Set Controller Time command on the Tools menu of the Dashboard sends the current PC Date/Time to all the controllers on the Network. Change the Windows Time and Date if the time in the following Set Panel Time dialog is incorrect.

To send the current PC Time to all controllers:

1.

From the Tools menu on the Dashboard, choose Set Controller Time.

2.

Confirm that Date shown is correct. If not, adjust PC Time.

3.

Then click OK to send this information to all the controllers.

Exiting ORCAview When you exit ORCAview, information about your building system, such as preferences, is automatically saved onto the ORCAview PC or OWS. Setpoints and other settings that you change are saved in the controller. It is not necessary to save files before exiting. Although it is not necessary to save the controller databases every time you exit, you should back up controller databases periodically. Whenever you make database changes, you should also make a backup



Exiting ORCAview

2–33

To Exit, click the X here, -ORSelect File and Exit

To exit ORCAview:  From the ORCAview Dashboard, choose File, and then click Exit. –OR–  Click the X Close button in the top right hand corner of the ORCAview Dashboard. Logoff  Selecting Logoff from the ORCAview File menu causes ORCAview to exit. You can then do one of the following: •

Log on to ORCAview as another user;

–OR– •

Log on to ORCAview through another network connection.

To Log on ORCAview as another user or through another network connection: 1. From the ORCAview Dashboard, choose File and click Logoff. 2.

When the Logon dialog box appears, enter your Username and Password.

3.

To change network connection, click the Advanced tab. Select the correct network connection information.

4.

Click OK.

The Advanced button is grayed out if Historian or ORCAweb is already running on the PC.



Chapter 3 – NAVIGATOR Chapter 3 Contents OVERVIEW .............................................................................................................. 3–4 DESCRIPTION .......................................................................................................... 3–4 NAVIGATOR FUNCTIONS ......................................................................................... 3–6 Viewing your System ................................................................................. 3–6 Monitoring and Control of Equipment ....................................................... 3–6 Responding to Alarms ................................................................................ 3–6 Managing Databases ................................................................................... 3–6 THE NAVIGATOR WINDOW ..................................................................................... 3–7 Left Pane ..................................................................................................... 3–7 Network Object Types ................................................................................ 3–8 Right Pane................................................................................................. 3–10 To adjust the size of the left and right panes: ................................... 3–10 LEFT PANE VIEWS................................................................................................. 3–10 To change left pane views: ............................................................... 3–10 Network .................................................................................................... 3–11 Logical ...................................................................................................... 3–12 Custom ...................................................................................................... 3–12 Options...................................................................................................... 3–13 Network Connection Information: Status Icons........................................ 3–13 Controller Addressing ............................................................................... 3–17 VERSION MISMATCH WARNING FEATURE (REGISTRY ENABLED)......................... 3–17 Enable with Registry Key ......................................................................... 3–18 Version Mismatch Function Explained .................................................... 3–18 Resolving a Mismatched Version Problem............................................... 3–19 Example: Compatible and Mismatched BBMD Controllers..................... 3–20 NAVIGATOR: NEW DESCRIPTION COLUMN FEATURE (REGISTRY ENABLED) ........ 3–23 Enable with Registry Key ......................................................................... 3–23 Initial Setup of Column Display in Navigator .......................................... 3–24 Description Column Function Explained .................................................. 3–24 VIEWING CONTROLLER OBJECTS .......................................................................... 3–25 Using Details View ................................................................................... 3–25 To switch Show Real-Time Data ON or OFF: ................................. 3–25 To change the rate at which data is updated automatically: ............. 3–26 Organizing Details View .......................................................................... 3–27 To sort by column: ........................................................................... 3–28 To resize a column: .......................................................................... 3–28 To move columns: ............................................................................ 3–28 Filtering Basics ......................................................................................... 3–29 Filtering Advanced ................................................................................... 3–30 System Objects ......................................................................................... 3–32 To Hide System Objects:.................................................................. 3–32 Active Alarms Filter ................................................................................. 3–33 WORKING WITH CONTROLLER OBJECTS ............................................................... 3–34 Selecting an Object ................................................................................... 3–34 To Select a Single Object: ................................................................ 3–34 To select a group of adjacent objects: .............................................. 3–34 To select a group of non-adjacent objects: ....................................... 3–34 Opening an Object .................................................................................... 3–34 Object – Right-Click Menu....................................................................... 3–36



3–2

Navigator

To save a database for a single controller device: ........................... 3–37 Creating New Objects .............................................................................. 3–38 To create a new object using the dialog box: ................................... 3–38 NAVIGATOR (RIGHT PANE) COMMAND >COPY... ................................................. 3–39 Copying Objects Dialog ........................................................................... 3–40 Copy and Paste Single Object .................................................................. 3–41 To create a single new object using copy and paste: ....................... 3–41 Copy and Paste Multiple Objects ............................................................. 3–42 To copy and paste multiple objects: ................................................ 3–42 NETWORK VIEW – RIGHT-CLICK MENU ............................................................... 3–43 Controller Commands .............................................................................. 3–44 Controller Off-Line .................................................................................. 3–44 Controller On-Line (Right-click) ............................................................. 3–45 To remove an unwanted Area Number setting from the network:... 3–47 Object Security (Lock, Unlock and Temporary Login Commands) ........ 3–48 To save a database for a single controller device: ........................... 3–51 Delta Network Commands ....................................................................... 3–52 To use the Load All Descriptors feature: ......................................... 3–52 To connect through ORCAview using a CON-768BT .................... 3–54 To save databases for all network devices ....................................... 3–55 Graphics Folder ........................................................................................ 3–56 To make the Graphics folder appear in the Navigator left pane: ..... 3–56 PRINTING FORMS IN NAVIGATOR ......................................................................... 3–56 To select long or short form: ........................................................... 3–56 Printing Objects........................................................................................ 3–57 To print a single object: ................................................................... 3–58 To print multiple adjacent objects: .................................................. 3–58 To print multiple non-adjacent objects: ........................................... 3–58 Searching .................................................................................................. 3–58 To open the Search dialog box: ....................................................... 3–59 To find objects using the Object Reference: .................................... 3–59 CREATING MULTIPLE SITES ................................................................................. 3–60 Overview .................................................................................................. 3–60 To create a new Site Settings object: ............................................... 3–60 GENERAL.............................................................................................................. 3–61 ADVANCED........................................................................................................... 3–61 V2 Master Panel ....................................................................................... 3–61 V2 Security Panel ..................................................................................... 3–61 BACnet Master Panel ............................................................................... 3–62 BACnet Security Panel ............................................................................ 3–62 User Logging............................................................................................ 3–62 User Log File ........................................................................................... 3–62 APPLICATION PROTOCOL...................................................................................... 3–63 AUTO SITE CREATION .......................................................................................... 3–64 Using Auto Site Creation ................................................................. 3–64 Deleting a Site Settings Object................................................................. 3–64 CUSTOM VIEWS .................................................................................................... 3–65 Sample Custom Views ............................................................................. 3–65 To open the sample custom view:.................................................... 3–65 To create new sub-folders:............................................................... 3–66 Creating New Custom Views ................................................................... 3–67 To create a custom view folder:....................................................... 3–67 To filter objects for custom view folders: ........................................ 3–67 To filter using object references: ..................................................... 3–67 Filter Examples ........................................................................................ 3–68



Overview

3–3

To filter by descriptor name for all objects containing the letter A: ................................................................................................ 3–68 To filter by descriptor name for objects in controller 100 containing the letter A: ............................................................... 3–68 To filter by descriptor name for all objects starting with an A, B, C: ................................................................................................ 3–69 To filter by object type for all Analog Inputs: .................................. 3–69 To filter by object type for all the Programs and Analog Variables:.................................................................................... 3–70 Export & Import ....................................................................................... 3–71 To Export a Custom View:............................................................... 3–71 To Import a Custom View:............................................................... 3–71



3–4

Navigator

Overview Navigator provides control and visualization of complex facility systems. Navigator is the object management interface of the ORCAview Operator Work Station (OWS). Navigator presents the building system components as a group (or groups) of objects. It has a similar look and feel to the Windows Explorer application created by Microsoft. This chapter explains how to use Navigator to view and change objects: •

Using Navigator Functions starting on page 3–6.

•

The Navigator Window starting on page 3–7.

•

How to use Left Pane Views starting on page 3–10.

•

Viewing Controller Objects starting on page 3–25.

•

Working with Controller Objects starting on page 3–34.

•

Using Network View – Right Mouse Menu starting on page 3–43.

•

Printing in Navigator starting on page 3–56.

•

Multiples Sites starting on page 3–60.

•

Creating Custom Views starting on page 3–65.

•

Reconnect Bluetooth Command starting on page 3–52.

•

Optional Version Mismatch Warning starting on page 3–17.

•

Optional Navigator Description Column Feature starting on page 3–23.

•

New in 3.40 – new controller icons starting on page 3–8.

•

New in 3.40 – improved Copy OK to All starting on page 3–39.

•

New in 3.40 – new Lock / Unlock commands for Object Security starting on page 3–48.

•

New 3.40 – Access Folder

•

New in 3.40 – improved Communication Control to All starting on page 3– 46.

Description Navigator provides you with tools for viewing, changing and controlling your system. Navigator and the ORCAview Dashboard are shown on the Windows desktop in the following figure:



Description

3–5

If Navigator is not open, you can start Navigator by selecting Tools in the ORCAview Dashboard and then clicking Navigator. You could also click the Navigator button on the toolbar located on the ORCAview Dashboard. It is assumed that you have Navigator permissions. More than one Navigator window can be open at the same time.



3–6

Navigator

Navigator Functions Navigator provides you with many functions. The following text describes these functions using four typical tasks: •

Viewing your System.

•

Monitoring and Control of Equipment.

•

Responding to Alarms.

•

Managing Databases.

Viewing your System Navigator provides different methods of viewing your application and the components within it: •

View the system as a network of controllers.

•

View the system as a logical collection of systems.

•

View the system as a collection of customized folders.

•

Navigate among the devices / systems.

Monitoring and Control of Equipment Objects provide monitoring and control of field equipment and the Delta Controls system. Objects allow you to: •

Manage alarms and equipment control.

•

Adjust setpoints.

•

Sort the objects in your system.

•

Create, copy, and edit objects.

Responding to Alarms •

View alarms directly from Navigator or from the Active Alarms Folder.

•

Sort alarms in Navigator windows or in the Active Alarm Folder.

•

Acknowledge alarms.

•

View past alarms from a Event Log.

Managing Databases •

Load and Back up databases.

•

Back up all controllers at the site.



The Navigator Window

3–7

The Navigator Window This chapter introduces the Navigator Window and describes the functions available with the window. Navigator presents information about your system. Navigator is divided into 2 panes. The left pane shows the network of controllers. The splitter bar separates the left and right panes. If you position the mouse pointer over the splitter bar and left click and hold the mouse down, you can adjust the position of the splitter bar. The right pane shows the contents of the controller or folder selected in the left pane. Left Pane

Splitter Bar

Right Pane

Navigator in Small Icon View

Left Pane The Navigator left pane includes a network tree that shows the connected controllers and ORCAview PCs. Typical network elements include the following:


•

Delta Network.

•

BACnet and Version 2 Protocol.

•

ORCAview PCs.

•

Controllers.

•

Active Alarm folder.

•

Graphics folder (usually).

•

Reports Folder

•

Access Folder (if RPL exists on the local OWS)


3–8

Navigator

Network Object Types Types of objects visible in the default setting include the following: NAVIGATOR LEFT PANE ICONS Icon 3.40

Icon 3.33R2


Item

Meaning

Delta Network

The top of a network at the current site.

Protocol

The communications protocol that connects the controllers. Protocol is visible only in network view.

Local ORCAview PC

The local PC with the ORCAview software.

Remote ORCAview PC

A remote PC on the network with the ORCAview software

Gateway

A gateway such as a Modbus application.

Historian

A Historian PC. OWS 3.40 supports multiple Historians on a site.

Controller

A Delta Control Unit, programmable Zone Controller, Plus Panel, Turbo or Mini-Turbo Panel, Micro Panel.

BACnet VAV or VVT Zone Controller

A Version 3 VAV or VVT Room Controller such as a DAC-V304 or DAC-304.

BACstat I

A device that acts as a temperature sensor on MS/TP.

BACstat II

A device that acts as a temperature sensor on MS/TP or LINKnet networks. Also could be a Zone controller.

3rd Party Controller

A BACnet controller supplied by another vendor.

BACnet Room Controller DSC

A Version 3 Room Controller such as a DAC-T305.

HVAC Delta Application Controller (Medium Enclosure, Red PCB)

A medium Universal Controller such as a DAC-606.

HVAC Delta System Controller (Large Enclosure, Red PCB)

A large HVAC DSC controller such as DSC1616/DSC-1212/DSC-1280.


The Navigator Window

3–9

NAVIGATOR LEFT PANE ICONS HVAC Delta System Controller Plus (Large Enclosure, Red PCB)

Indicates an older large image DSC controller.

Lighting Controller (Green PCB)

A Lighting Controller such as DLC-G1212/DLCP1036.

Lighting Controller Plus

An older Lighting Controller such as DLC-G1212.

Access Delta System Controller (Medium Enclosure, Blue PCB)

An Access Controller such as ASM-24X/24EX.

LINKnet Device

A LINKnet device such as a DFM-200 or DFM-400

Fancoil

A Fan Controller such as a DFC-304

enteliTOUCH

A Delta enteliTOUCH device such as the eTCH7ET

enteliBUS Controller

A BACnet Building Controller such as an eBCON which supports I/O modules.

enteliBUS Manager

A device that performs a function similar to an RTR router controller but on an enteliBUS network.

enteliBUS Touch Manager

An enteliBUS manager but with a HMI provided by an enteliTOUCH screen.

Active Alarms Folder  The Active Alarms Folder generally contains all the active alarms at the site. The Active Alarms folders can appear in two different ways. When no active alarms are present, the active alarms folder appears as on the left. When active alarms are present, the Active Alarms folder appears with a large red alarm icon as on the left. Open the folder to view or acknowledge active alarms. When the Active Alarm Folder is selected, its contents can be printed by choosing File and then clicking Print from the ORCAview dashboard. Graphics Folder  The Graphics folder contains the site graphics. Although it appears by default, it is an optional folder. To change the option, from the ORCAview Dashboard, choose Tools, select Preference, and then select Navigator. Next disable or enable the Show Graphics Folder checkbox.



3–10

Navigator

Right Pane The Navigator right pane shows the objects that exist in the controller that is currently selected in the left hand pane. For example, some of the objects in a controller are inputs, outputs, programs, variables and control loops. Each object type has its own symbol or icon to distinguish it from other objects. To adjust the size of the left and right panes:

You can vary the size of the left and right panes by dragging the splitter bar.

1.

Place the mouse cursor over the splitter bar.

2.

Click the splitter bar and hold down the left mouse key.

3.

Move the mouse cursor left or right and the splitter bar will follow.

Left Pane Views To change the left pane view, right-click on any blank area in the left pane and select a new view from the menu. The following views are available: •

Network — View the system as a network of controllers. This is the default view.

•

Logical — View the system as a collection of physical devices.

•

Custom — Allow views to be created that show the system by mechanical systems, instead of by controller. Custom views are further explained at the end of this section. A sample custom view is provided.

•

Options — View the setup and preference objects as groups of folders.

To change left pane views:

 Right-click once on the white area of the left pane. Select the view you wish to use.

–OR–

 From the ORCAview Dashboard click on View and select Network, Logical, or Custom view.



Left Pane Views

3–11

Network Network shows the connected controllers by protocols and is the default view setting for Navigator. By default, Navigator will only display the highest level controllers of the network hierarchy with the lower level controllers “Collapsed” in the Network Tree. This is shown by a + or – sign next to the system or area controllers. Click on the + sign and the network tree will expand, revealing the subnet controllers. For example, Subnet Application controllers are collapsed under System controllers and System controllers are collapsed under Area Controllers, etc. The following figure shows Navigator with Network Tree collapsed.

The following figure shows Navigator with the Network Tree expanded.



3–12

Navigator

Logical Lists all the connected controllers in numerical order based on device addresses.

Custom Displays the system by mechanical systems instead of controller. See the Custom Views section starting on page 3–65 for information on how to create and use Custom Views.



Left Pane Views

3–13

Options The Options folder is another way to access the Preference menu.

You can also view the Preference menu from the ORCAview Dashboard by clicking Tools, and selecting Preference.

Network Connection Information: Status Icons The controller icons shown provide information about the quality of the network connection between controllers and the ORCAview workstation. The following figure

shows the status icons that may appear on a controller icon in the left pane:

Query Controller  The yellow question mark appears when the Controller's information that is cached by ORCAview is out of date or has not been loaded. If ORCAview is set to not auto-load descriptors, the yellow question mark may stay on a controller until the controller is selected.

Being Queried



3–14

Navigator

Off Line Controller  When a controller is not responding, or is responding incorrectly to ORCAview requests, a red X is shown on top of the controller.This may be caused by a broken network connection to the controller, or loss of power to the controller.

16x0 Controller 103 (103) Unable to Connect

Online Controller  The ORCAview PC has loaded up the names at login and established good communication with the controller.

All Controllers have a good connection



Left Pane Views

3–15

Misconfigured Controller  The yellow wrench appears when ORCAview detects a controller with a misconfigured address.

Device 30100 (30100) is Misconfigured.

Note: When a misconfiguration occurs it will normally be accompanied by the display of

an on screen message like the following:

Address misconfigurations are normally handled by right-clicking on the controller in the Navigator left pane and selecting Reconfigure in the Command sub-menu. Non-existent Controller  The red question mark appears when ORCAview attemps to communicate with a controller that does not exist on the network. This can be caused by a site graphic or GCL program that references a controller which does not exist, or an Active Alarm List entry that references a controller that does not exist. This icon usually shows up after re-initializing ORCAview descriptors. This problem be fixed by correcting the link within the graphic or GCL program, or by deleting the errant Active Alarm List entry. If the controller does actually exist on the network, then this is an indication that the controller is not communicating with ORCAview.



3–16

Navigator

(103) does not exist

Software Version Mismatch on Controller  ORCAview has an optional feature that warns the operator when the ORCAview (or ORCAweb) software version does not match the firmware version (controller operating system) in a controller. In some situations, an operator may have a WAN network with different buildings running different firmware. This feature is enabled using a Windows registry key entry. Refer to the Version Mismatch Warning Feature (Registry Enabled) section starting on page 3–17 for details. An indicator ( ) displays in the left pane Navigator tree on a device icon to immediately indicate the mismatched-version devices.

The mismatched version mask (a little red octagon (eight sided figure) with a white exclamation point) appears on the controller icons in the left pane of the Navigator tree to immediately indicate when a device does not have the same version as the OWS. This mask displays only when there is not another mask on the controller icon. The following figure shows a portion of the left pane of the Navigator tree. OWS 27234 does not match the version of the Device 6300 and BBMD2 9600 controllers.



Version Mismatch Warning Feature (Registry Enabled)

3–17

Controller Addressing Controller addressing is very important since each controller must have a unique address within the network. In Navigator, the controller’s address is the number in brackets (100). The name of the Controller has no impact on the address. In the following figure, Device200’s address is (300).

Address of the DCU in bracket (100)

See Appendix C: Derived Network Addressing for detailed information on addressing.

Version Mismatch Warning Feature (Registry Enabled) ORCAview has a feature that warns the operator when the ORCAview (or ORCAweb) software version does not match the firmware version (controller operating system) in a controller. In some situations, an operator may have a WAN network with different buildings running different firmware. The intention is to allow the operator to view most of the data on the network but to avoid database integrity problems that may result when a modified database is saved to a controller using a mismatched software version. If the operator must write data to a controller, a matching version of the software is required. For example, an operator might shut down OWS 3.40 and instead use OWS 3.33R2 to make changes to a controller.



3–18

Navigator

Enable with Registry Key A registry DWORD key (DetectControllerVersion) must be set to 1 for the feature to work. If the registry key is 0 or is not present, warnings do not appear. By default, the version mismatch feature is enabled. You can edit the registry using a utility such as regedit.exe which is included with Microsoft Windows.

The registry key is:

KEY_LOCAL_MACHINE | SOFTWARE | Delta Controls | 3.40 | Commander | DetectControllerVersion

Version Mismatch Function Explained The Version Mismatch feature manifests itself in three specific ways: 1. An indicator ( ) displays in the left pane Navigator tree on a device icon to immediately indicate the mismatched-version devices.

The mismatched version mask (a little red octagon (eight sided figure) with a white exclamation point) appears on the controller icons in the left pane of navigator tree to immediately indicate when a device does not have the same version as the OWS. This mask displays only when there is not another mask on the controller icon. The following figure shows the status icons that may appear on a controller icon in the left pane.

The following figure shows a portion of the left pane of the Navigator tree. OWS 27234 does not match the version of the Device 6300 and BBMD2 9600 controllers.




3–19

2. The Version Warning message displays when an object dialog is opened with a mismatched version of ORCAview (or ORCAweb). When a new object dialog or an existing object dialog is opened on a controller with a different software version, a message displays informing the user that versions do not match and that writing to the controller may adversely affect database integrity. The same warning message is used in both ORCAview and ORCAweb.

3. The same Version Warning message displays for a hard-coded data link in a site graphic to a device that does not match the ORCAview (ORCAweb) version. When a site graphic with hard coded links to devices is opened, each link is checked. The warning message displays after the revised graphic is saved and put into Run mode.

Resolving a Mismatched Version Problem With the general knowledge that there is a mismatch between the OWS and the firmware version on a controller, you would need to get specific version information to resolve the problem if you wished to save a database. The version of the OWS or controller Firmware can be determined through the Device (DEV) object | Product Tab | Firmware Version and Application SW Version fields. The version mismatch features uses the datestamps on the DIC files as displayed in the Dictionary Version datestamp field on the Database tab of the Database Information (DBI) object.



3–20

Navigator

Example: Compatible and Mismatched BBMD Controllers The following figure shows OWS 12345 with two BBMD’s shown in a partial left pane Navigator tree. BBMD1 is compatible with the OWS 12345 software version. BBMD2 indicates a mistmatch with the OWS version. [3.40 matches OWS 3.40]

[3.33 NOT match OWS 3.40] [3.40 OWS]

First, we can examine the Device object for the ORCAview OWS. The following figure shows that the OWS340 is from Delta Controls and has an Application SW Version of 3.40.

The following figure shows the Device object for the BBMD1 device which matches the ORCAview OWS V3.40 version.




3–21

From the previous figure, the eBCON controller has application SW Version of V340. This matches with the parameters for the ORCAview OWS 12345 which is V3.40 Application Software Version.

The following figure shows the Device object for the BBMD2 device has a version (V3.33) which does not match with the ORCAview OWS (V3.40).



3–22

Navigator

The BBMD2 controller is a Delta Controls DSC_1616E (Delta System Controller) with Application SW Version V3.33. The controller does not match with ORCAview OWS 3.40.



Navigator: New Description Column Feature (Registry Enabled)

3–23

Navigator: New Description Column Feature (Registry Enabled) ORCAview has a feature that provides a means to display the contents of the Description tab for an object in Navigator. The previous Description column is now more appropriately named as Object Type and lists the type of the object for each Navigator entry. The Description Column features is not enabled by default and a customer would only enable it if they had a specific need as it places higher data transfer demands on the network. The following figure shows the current function of the Object Type column.

The following figure shows the Description columns heading at the extreme right column of Navigator. The Description column contains sample text that was added to the Description tab for each of the first three Analog Input Configuration (AIC) objects.

Enable with Registry Key A registry DWORD key (ShowNADescription) must be set to 1 for the feature to work. If the registry key is 0 or not present, the Description field does not appear. By default, the Description column is not enabled and the property is not included in the registry. You can use a utility such as the standard MS Windows regedit.exe to add the required entry to the appropriate place in the registry.

The registry key is:

KEY_LOCAL_MACHINE | SOFTWARE | Delta Controls | 3.40 | Commander | ShowNADescription



3–24

Navigator

Initial Setup of Column Display in Navigator Depending on the status of the ShowNADescription registry property, a new Description column will appear as the last column in the upper right of the Navigator window.

You can adjust the size of the Navigator window and then grab (position cursor, left click and hold, then move the column heading) the Description column and move it.

The Description column may have a very small width the first time that it appears. You need to expand the Description column width. You can resize the column width by positioning the mouse over the last column marker of the current Description column heading and then left click and hold the mouse while you drag to resize the column. Navigator remembers the settings when it is opened afterwards.

Description Column Function Explained This feature provides means to view enlarged amounts of text that is saved in the Description tab of an object. To view the complete text for an object, first open the particular object and then read the entire text included on the Description tab. It is possible to adjust the width of the Description column so that more text is visible in Navigator.

The following figure shows the column headings of Navigator arranged to allow a very wide Description column.



Viewing Controller Objects

3–25

Viewing Controller Objects When a controller is selected in the Navigator left pane, the right pane displays the objects contained within the controller. These objects include alarms, inputs, outputs, trend logs, and schedules. The right hand Navigator pane has four possible views useful for viewing, changing and creating controller objects. The views can be selected from the ORCAview Dashboard using the View toolbar, or by right-clicking in the white space of the right hand Navigator pane.

Viewing Controller Objects Icon

Item

Meaning

Large Icon

Displays objects as large icons. The icon shows object type.

Small Icon

Displays objects as small icons. The icon shows object type.

List

Displays objects in a list form with their small icons.

Details

Displays objects in columns with their icons and information received from the controller. The objects can be sorted by column. The operator can vary the refresh rate for the data in Details view. Information updating can also be turned off.

Using Details View Details View presents the most information about your site. Details View shows live dynamic data with sort, find, and filter tools. In Details View, the Navigator display varies depending on whether the data is being updated. The Show Real-time Data command on the right mouse menu toggles the display of dynamic data ON or OFF. Show Real-time Data ON  In the ON setting, data from the controller is periodically updated. The Name, Object, Description, Value, Auto Manual, Commissioned, Objects, Units, and Alarm columns display. Show Real-time Data OFF  If Show Real-time data is turned OFF, some of the columns in the Navigator right hand pane are removed as the display is not updated. The Value, Auto Manual, Commissioned, Objects, Units, and Alarm fields do not display any data. The Name, Object, and Description columns display data. The update of the display stops and the Refresh icon in the bottom lower right of the Navigator window disappears. To switch Show Real-Time Data ON or OFF:

1.


Right-click on a blank area of the Navigator right hand pane.


3–26

Navigator

2.

Click Show Real-time Data. Show Real-time Data is active when the check mark is beside the menu item.

Note: Only the data visible on the display is refreshed. When you resize or scroll down the

Navigator window, Navigator will refresh the newly visible information

Refresh Bar

Auto Refresh Rate

To change the rate at which data is updated automatically: Updates increase network traffic. Depending on the demands on your system, you may wish to slow down the rate of data updates. The choices for Auto Refresh are 5, 10, 30, or 60 seconds. 

Right-click on the refresh icon in the lower right of the Navigator window. Select the update rate from the pop-up menu. The default rate is 5 seconds.

–OR– 

From the ORCAview Dashboard, choose Tools, select Preference, and click Navigator.




3–27

Organizing Details View The following figure shows the information in the Details View columns. Alarm State Value Name

Object Reference

Units

Manual or Automatic Commissioned or not commissioned

Object Status Type of Object

ORCAview has a feature that provides a means to display the contents of the Description tab for objects in Navigator. The previous Description column is now more appropriately named as Object Type and lists the type of the object for each Navigator entry. The Description Column feature is not enabled by default and a customer would only enable it if they had a specific need as it places higher data transfer demands on the network. Refer to the optional Navigator Description Column Feature section starting on page 3–23. Sort  You can sort by clicking the top of any column name in the Navigator right hand pane. ORCAview then does one more scan of all the objects, not just those visible on the screen and sorts them. When sorting by Value, Units, Alarms, Comissioned, Manual, or Status, the Refresh icon in the bottom right corner may change from green to red to show that information must be updated manually through the right mouse menu. A Hand also appears over the Refresh icon (in the bottom right hand corner of Navigator) to indicate Manual Refresh.The Refresh icon turns red only when all the objects are not visible in the right pane. The Refresh icon stays green if all the objects are visible in the right pane during a sort.



3–28

Navigator

Auto Refresh and Manual Refresh Auto Refresh

The Auto Refresh rate choices are 5, 10, 30, or 60 seconds.

Manual Refresh

In the details view, if you sort on a dynamic field such as Value or Status, the right hand side pane stops automatically refreshing. The refresh changes from Auto Refresh to Manual Refresh as indicated by the Manual Refresh icon in the lower right of the Navigator window. To get back into Auto Refresh mode, you must click on the heading at the top of any non-dynamic column such as name or Object.

To sort by column:

Click on any column header. To resize a column:

1.

Place the mouse cursor over the lines that divide the column headers.

2.

The cursor will become a double-headed arrow.

3.

Click and drag the mouse cursor to resize the column.

To move columns:

1.

Place the mouse cursor over a column. Click and drag the column to the left or right.

2.

A grey shadow will show the column location while you move it. The column will be inserted where you release the mouse button.

Note: If the columns are moved or resized, then the changes remain the next time anyone logs in. The settings are saved for the PC and cannot be made specific to a particular user.




3–29

Filtering Basics Filtering is used to sort and display specific types of objects. Filter objects by typing the filter in the filter box and pressing Enter. The setting of the Filter Icon in the lower left pane affects the objects that display for an entry in the filter Box. The choices for the Filter Icon are Hide System Objects, Show Only System Objects, and Show All. Filter Box

Filter Icon Wildcards can be used to filter by descriptor name. For instance, typing Hot* in the Filter box and pressing ENTER will display all object names starting with Hot. Wildcards can represent any letter or number.

It is also possible to filter for object type. Type the Object References such as ai bo (or AI BO) with a space between them. You need to press ENTER for the matching objects to appear. Multiple filters can be entered at one time as long as a space is present between each filter entry.



3–30

Navigator

Type in both objects with a space between them and press ENTER to see more than one type of object.

Note: Filters for descriptor names such as AHU2 are not case sensitive. If you type either

ahu2 or AHU2 and then press ENTER, the same matching objects will display in the right hand pane. Filters for object types such as BI or AO are also not case sensitive.

Filtering Advanced The Filter Box has AND OR > < = properties. Generally the query is in a form of: [Objects].[Property Conditions] [Object] can be an object name pattern, an object type with individual instance, or an instance range. [Object] defaults to * if it is not specified. Filter For

Filter Box Entry

Comment

Object Reference

bi

This entry finds all Binary Input objects. BI* would give the same result.

Object Reference Multiple Entries Separated by a Space

bi bo AI AO

This entry finds all Input and Output objects. (Not case sensitive)

Descriptor Name

ahu2

These entries are not case sensitive. AHU2 gives the same result as ahu2

Wildcard

bi*

This entry finds all instances of Binary Input objects.

Descriptor Name with Wildcard

ahu*

This entry finds all names that start with ahu and is not case sensitive.




Default to Value Property

av > 70

If a property is not specified, then by default the value property is tested in any operation. The entry av.Value > 70 would give the same result.

Equality Operator

*=Stopped

This entry finds all objects whose value is equal to Stopped.

Inequality Operators

AV<10 AV>90

AV<10, AV>90 with a comma after 10 would give the same result.

Object Property

*.OutofService = 1

This entry finds all objects with a status of Out of Service.

Logical Operator:

AV.(Name = "*A*" and Value > 74)

The "and" "or" operators only apply to Property Conditions.

AV.(Name = "*A*" or Value > 74)

The "and" "or" operators only apply to Property Conditions.

Object Instance

av(1,3,5)

This entry finds all Analog Variable objects with the specified instance numbers.

Object Instance Range

av(1-7)

This entry finds all Analog Variable objects within a range of instance numbers.

Real-time Property Query

ai.Calibration > 0

This entry checks a property condition.

Object Search by Name

Temp > 23

This entry finds the object named Temp that has a value greater than 23.

Array Property, Text Comparison

eva.TransitionText[1] = "*fail*"

This entry checks a text property.

Multiple Object Type with Shared Property

(ai(1-7), av, ao).ManualOverride = TRUE

This entry finds Analog Input objects with instances numbers of 1-7, all Analog Variable objects, and all Analog Output objects that are in a manual Override condition.

Multiple Property Criteria

(ai, ao).(ManualOverride = TRUE and Value > 50)

This entry finds all Analog Input and all Analog Output objects that are in a manual Override condition and have a value greater than 50.

Multiple Query String Separated by a Comma

ai > 6, bv = "Fan On"

This entry finds all Analog Input objects with a value greater than 6 and also any Binary Output objects with a value of Fan ON.

Logical OR Operators with Other Criteria

AV.(Value <26 or Value > 74)

This entry finds all Analog Variable objects that have a value that is less than 26 OR greater than 74.

Logical AND Operators with Other Criteria

AV.(Value > 26 and Value < 74)

This entry finds all Analog Variable objects that have a value that is greater than 26 AND less than 74.

AND Logical Operator: OR


3–31


3–32

Navigator

The "and" "or" only apply to Property Conditions. e.g. AV.(Name = "*A*" or Value > 74) Your filter could be done by •

AV<26 AV>74

•

AV<26, AV>74

•

AV.(Value <26 or Value > 74)

In case you need "and", the first 2 option will not work. You will need to type: •

AV.(Value > 26 and Value < 74)

System Objects System objects are needed for setup but are not normally needed for day-to-day operation of the system. System objects can be hidden from view in the Navigator window. The following are examples of System Objects: •

System User Access (SUA)

•

Event Class (EVC)

•

Analog Input Configuration (AIC)

•

Analog Output Configuration (AOC)

•

Binary Device Configuration (BDC)

By default, system objects are hidden. The Filter Icon in the lower right corner of the Navigator window gives the user three options: Hide System Objects Show Only System Objects Show All To Hide System Objects:

•

Right-click on the filter icon in the lower right corner of the Navigator window. Click on Hide System Objects.




3–33

Active Alarms Filter Navigator can also display the active alarms that are on each individual Controller. This is done by right-clicking on the object filter at the bottom right hand corner of Navigator and selecting Active Alarms.

Select Active Alarms here

When Navigator is in Active Alarms view, it gives the details about the active alarms on the Controller. Navigator appears as shown in the following figure.

From this view the active alarms can be opened, acknowledged or deleted just as they can when the viewing the active alarms folder. Alarms can be opened, acknowledged or deleted from the Active Alarms folder. This can be done by right-clicking on the alarm entry and choosing either Open, Acknowledge or Delete.

For more information about alarming see Chapter 5: Event Management System.



3–34

Navigator

Working with Controller Objects When you select a controller in the left hand Navigator pane, the objects within the controller's database are shown on the right hand Navigator pane.

Selected Controller

Controller Objects

Selecting an Object A single click on any object will select the object. Objects may also be selected in groups. To Select a Single Object:

Click once on the object with the left mouse key. To select a group of adjacent objects:

1.

Click the first object in the group.

2.

Press and hold down Shift.

3.

Click the last object of the group.

To select a group of non-adjacent objects:

1.

Press and hold the Ctrl key.

2.

Click on each object once to select it.

Opening an Object All objects can be opened by double-clicking the object, or by choosing open in the rightclick menu. When an object is opened, it is displayed as a dialog box. A dialog box allows the display and modification of the object’s settings using standard Windows methods. OK, Cancel, and Apply Buttons All objects have OK, Cancel and Apply buttons as shown in the following figure.



Working with Controller Objects

OK button makes the changes you select and closes the dialog

Cancel button discards the changes you made and closes the dialog

Apply button makes the changes you select without closing the dialog box.

3–35

Help [ ? ] button provides information about the object

Help Button  Help for an object is available by clicking on the ? button on the dialog box or pressing F1. Refresh Indicator  A green dot appears next to the object icon and shows the refresh rate of the data in the dialog. The dot changes state for each occurrence of a refresh. Each time that the dot blinks, the user gets a visual cue that the information is refreshed.

Refresh Indicator dot (green)

The refresh rate is set in the System User Access (SUA) object. On the ORCAview Dashboard, use Tools\Setup\CurrentUser. Select the User Data tab and set the Refresh Rate for Objects. The Refresh Rate can vary between 5 seconds and 60 seconds. Do not confuse the green dot refresh rate for the dialogs with the Refresh Rate for the Navigator window data.



3–36

Navigator

Object – Right-Click Menu When an object or a group of objects is selected in the Navigator right pane, the objects can be commanded by clicking once with the right mouse button.

The following commands are available from the right-click menu: Open  Opens the selected object(s). Command  This opens a sub-menu. These options are available when certain objects are selected in Navigator or when an object is selected with Illustrator in the RUN mode. The sub-menu commands follow: Note: The ORCAview Dashboard provides the same functions as this right-click menu.

Right-Click Menu Item

Dashboard Button

Function

Auto

Switches the object to Auto Mode.

Manual

Puts and analog object into Manual Mode.

Manual Value

Assigns a value to the selected object.

Manual On

Sets a binary object to manual ON.

Manual Off

Sets a binary object to manual OFF.

Acknowledge

Permits the operator to acknowledge an Alarm. See Chapter 5 on Alarming for further information.

Reset

Clears any historical information stored in an object. Typical object types would be trend log and totalizer. The Reset function varies depending on the particular object.

Add to Historian


N/A

Instructs Historian to begin archiving the selected Trend Log if there is a Historian device on the network. For more information please read Chapter 6 and 10 (Data Trending and Archiving and Software Objects Reference)


Working with Controller Objects

3–37

Next Object

Skips to the next object from the list in the right hand Navigator pane.

Next Panel

Skips to the next controller (panel) from the list in the left hand Navigator pane.

Previous Object

Skips to the previous object from the list from the right hand Navigator pane.

Previous Panel

Skips to the previous controller (panel) from the list in the left hand Navigator pane.

Find Object  Find Object allows you to search for objects throughout your system. Use wildcards for a partial name search. Cut  [Cut is not available] Copy  Places a copy of the selected object into temporary memory. Paste  Places copied object into the selected controller. Delete  Erases the selected objects from the controller database. Rename  Renames the currently selected object or group of selected objects. Renaming a group of objects displays a pop-up that allows you to replace text in the names of the selected objects. You can also append or prepend text to the names of the selected objects. Save As  Saves the currently selected object to the PC as a pob file. With DAC/DSC controllers, the Save As and Save All commands cause the controller to first save the database to flash memory and then to write a copy of the flash contents to the specified file. The DCU controller does not first save to flash during a Save As or Save All operation. (To reload the object from the PC to the controller, first select the controller. Then, rightclick and select the Load option). To save a database for a single controller device: 1. Select the controller device in the left pane of Navigator.

2.

Right-click and choose Save As from the pop-up menu.

3.

Type in a suitable File name.

4.

Click Save. The file is saved in the Site folder by default.

Print  Prints to any Windows printer attached to the PC. See page 3–56 for more information about printing.



3–38

Navigator

Creating New Objects New objects are easily created in Navigator. You can create new objects using a dialog box or you can copy and paste an existing object. Some objects, such as the Event Settings (EVS) object and Data Exchange Settings (DES), are automatically created by the system and cannot be created or copied by the programmer. To create a new object using the dialog box:

1.

In the left hand Navigator pane, select the controller in which you want to create a new object.

2.

In the right hand Navigator pane, right-click on the empty white space. From the popup menu, select New…. The Create Object dialog box will open.

3.

You can put in the entries for the dialog box in any order. As the dialog box will suggest some of the information for you, start with what you know. For example, if you know what type of object you wish to create but do not know the Object Reference, put in the Type of Object Entry first. The dialog box automatically assigns an Object Reference and an Object Number.

The entry fields are as follows: Name: The name of the object. e.g.: AHU1 Supply Air Temperature. Underscores are not needed between words when creating objects in BACnet controllers. Version 2 still requires underscores in object names. Names that contain ‘ “ * & | / \ (backslash and forward slash) should be avoided.



Navigator (Right Pane) Command >Copy...

3–39

Object Reference: The object reference is made as follows: Protocol Type, Controller Address. Object, and Number. The object reference does not need to be directly named as the system automatically provides it for you. BACnet Protocol Controller Address Object Type and Number BAC.100.AI17 Type of Object: Object types are described in Chapter 10 – Objects of this manual. Your choice of objects will vary depending upon the type of device selected in the left hand pane. Object Number: The specific instance of this object type. For example, if a controller has twenty Analog Inputs, they typically have object numbers from 1 to 20. For input and output objects, the object number tells you which hardware input or output is being used. Each object of the same type must have a different number. Copy and Paste  New objects can be created using the copy and paste functions of the Navigator right-click menu. ORCAview will suggest a new object number and will prompt for a new object name. The Navigator (Right Pane) Command >Copy section starting on page 3–39 explains the function including the Cancel All and OK to All buttons.

Navigator (Right Pane) Command >Copy... The Copy command has been improved so that it is easier to copy and paste objects within a controller or to another controller. Typically, you would select and copy multiple objects on one controller and then paste them into another controller. You can use the Shift and Ctrl keys to define blocks that form a collection of objects to copy.



3–40

Navigator

In a paste action, the OK To All and Cancel All buttons can now be used to avoid clicking the OK or Cancel buttons many times to provide input for each individual object. With OK to All and Cancel All, you do not have to inspect each individual object and this approach can save time.

Copying Objects Dialog The Copying Object submenu provide a flexible and efficient copy and paste function. It has following fields and buttons: Object Name

This is the name of the object. For example: AHU1 Supply Air Temperature. Underscores are not needed between words when creating objects in BACnet controllers, but are required in Version 2. Avoid names that contain the special characters: ' " * &. The name is specified when the object is created. Object Number

This is the specific instance of this object type. For example, if a controller has twenty Analog Inputs, they typically have object numbers from 1 to 20. For input and output objects, the object number tells you which hardware input or output is being used. Each object of the same type must have a different number. The object number is specified when the object is created. Buttons

The Copying Objects dialog has the following buttons.



Navigator (Right Pane) Command >Copy...

Button

Explanation

OK

Pressing this button pastes a single object with the current Object Name and Object Number in the Copying Objects dialog.

OK to All

Pressing this button pastes the remaining objects in the paste collection with the default Object Name and Object Number. It asks for confirmation only when an Object Name or Object Number conflicts with an existing object on the controller. If there are no conflicts, the remaining objects are pasted in a single operation.

Cancel

Pressing this button skips pasting the single object with the current Object Name and Object Number in the Copying Objects dialog. The next object in the paste collection with suggested Object Name and Object Number then appears in the Copying Objects dialog.

Cancel All

Pressing this button cancels the creation of any more objects in the paste collection. The remaining objects in the paste list are not pasted and the copy and paste operation is immediately ended.

Help

Pressing this button bring up the help topic for the Copying Objects dialog.

3–41

Copy and Paste Single Object A new object can be created using the copy and paste functions of the Navigator right-click menu. To create a single new object using copy and paste: 1. Select an object in the right pane of Navigator.

2.

Right-click and select Copy.

3.

Select the controller where the new object is needed.

4.

In the right pane of Navigator, right-click and select Paste.

5.

ORCAview suggests an object number.

If the object is copied to the same controller, then the object number is the next available number, and ORCAview asks for a new object name.



3–42

Navigator

Copy and Paste Multiple Objects

When multiple objects are copied, you can select whether to paste each individual object or not using the OK and Cancel buttons in the Copying dialog box. The OK to All button pastes all the remaining objects only asking for confirmation when the Object Name or Object Number conflict with an existing object on the controller. The Cancel All button aborts the pasting of any remaining copied objects.

To copy and paste multiple objects: 1. Select a collection of object in the right pane of Navigator using the Shift and Ctrl keys.

2.

Right-click and select Copy.

3.

Select the controller where the new objects are needed.

4.

In the right pane of Navigator, right-click and select Paste.

5.

For each object, ORCAview suggests an object number.

• •

If the object is copied to the same controller, then the object number is the next available number, and ORCAview asks for a new Object Name. If the object is copied to a different controller, then the object number is the next available number and the same Object name is used.



Network View – Right-Click Menu

6.

3–43

Decide if the suggested Object Number and Object Name are acceptable and then press OK to accept.

OR: • Press Cancel to skip pasting this individual object. The suggested Object Number 7.

and Object Name for the next copied object to paste displays in the dialog. Continue the process of inspecting the suggested Object Number and Object Name for each individual copied object. (pressing OK or Cancel)

•

If you want to not paste any of the remaining objects, press Cancel All. This action ends the operation immediately and any remaining objects are not pasted.

OR: • If you want to paste all the remaining objects, press OK to All. This action pastes all the remaining objects with the default suggestions only asking for confirmation when the suggested Object Name or Object Number conflicts with an existing object on the controller.

Network View – Right-Click Menu When, in Network View, the left pane of the Navigator window shows all the connected controllers. Right-clicking on a controller provides the following commands.

Note: All Right-Click Menu options can also be accessed within the Logical view, except for commands directly related to Protocol.



3–44

Navigator

Controller Commands These commands are available from the pop-up menu following a right-click on a controller. A different menu is shown depending on whether the controller is currently on-line or off-line.

Controller Off-Line A controller is off-line when a red X appears on top of the controller icon. Right-click on the controller to access the following commands.

Query Device  Tries to reestablish communication with the off-line controller. Command  When a controller is offline, the Communication Control…, Remove Area, Reconfigure and Reset commands are available. The commands are explained in the next section titled Controller On-Line (Right-click). Delete  Removes this controller from the Navigator left pane network. No further tries to communicate with this controller will be made.




3–45

Controller On-Line (Right-click) The controller is on-line when it is communicating with ORCAview. Right-click on the controller to access the following commands.

Open  Opens the controllers Device (DEV) or CP object. If a graphic is specified on the Device Graphic tab of the Navigator Settings (NVS) / Device Graphic List (DGL) object, the designated site graphic opens instead of the Device (DEV) object when you open a controller or device from the left pane of Navigator. The assigned device graphic only displays from the left pane when you open the Device from the File menu on the Dashboard or use the right mouse Open command. If you double-click on a controller in the Right Pane of Navigator, then the Device (DEV) object dialog opens as before. Command  This opens a sub-menu. The Command sub-menu follows: Load From Flash  Restores a saved to flash memory database to RAM in the controller. This feature is not applicable to all controllers. Note: The controller pauses operation (i.e. outputs remain at their last state, programs

pause execution) during a Load From Flash. Once the database is loaded into the controller, it begins operation of the loaded database. Save To Flash  Saves the current RAM database to the controller’s flash memory. Once saved to flash memory, the database is safe from loss due to power failures. This feature is not applicable to all controllers.



3–46

Navigator

Note: The controller pauses operation (i.e. outputs remain at their last state, programs

pause execution) during a Save To Flash. Once the database is saved to flash, the controller continues operation. Clear Database  Clears the current database in RAM. Does not clear the flash memory. To clear the flash memory, first use the clear database command. Then use the Save to Flash command. The blank database will be saved to flash memory. This feature is not applicable to all controllers Caution: Use these Load From Flash, Save To Flash and Clear Database commands with care. You may otherwise delete a database from a controller by mistake. Update Active Alarm List  The active alarm list in a controller can be manually updated. This may be necessary if the controller has logged into the network without auto loading the Active Alarm Lists or if the situation arises where the Active Alarm List on the controller becomes out of synch with the Active Alarm Lists on the other devices. Communication Control  The Communication Control submenu specifies how a device communicates over the network using the Enable, Disable, or Disable Initiation commands and an optional time duration setting. A Password is needed to change the selected option. You need at least Edit permissions to the Device object to modify this password. The Communication Control submenu is used to: •

Stop a device from sending too much traffic down a network for a specified duration.

•

Set a device to only respond to requests and not initiate communication for a specified duration.

•

Locate the device causing problems when troubleshooting a network.




3–47

Three Communication Modes are available: •

Enable allows a device to communicate normally on both its peer and subnet levels. This is the default setting.

•

Disable stops a device from communicating on both its peer and subnet levels. Only Communication Control and Reinitialize Device messages are processed and no messages are initiated.

•

Disable Initiation stops a device from initiating communication. All messages received are processed and responded to as required, but no messages are initiated.

The Disable and Disable Initiation choices can be applied for a fixed duration. When the duration expires, the device reverts back to the Enable mode and full communication resumes. Selecting the Enable Duration checkbox and specifying a Duration causes the Disable option to be applied temporarily. If no duration is applied, then the Disable option applies indefinitely until an Enable command is received or until the disabled device is reset.

In the Duration field, a spin box accepts a number from 0 to 65535 and a dropdown allows you to specify the time unit as either minutes or hours. Remove Area  This command can be used to remove unwanted Area number inhertances from the BACnet address of system and subnet controllers. To remove an unwanted Area Number setting from the network:

1.

Right-click a single controller with the Area setting that you wish to remove.

2.

Select Command and click Remove Area. The unwanted Area Number will be removed from the BACnet address of all the controllers that inherited it.

Reconfigure  The Reconfigure command is used to resolve address conflicts when connecting new controllers onto a network. A wrench icon on a controller shows that Reconfigure changes the address of a controller so that it can communicate on the network. See Appendix C: DNA for more information. Reset  Performs a reset on the selected controller. This is the end of the Command sub-menu. Find Object  Search for an object. Use wildcards for a partial name search. Connect  This function is not currently used.



3–48

Navigator

Reload  Reload opens a sub-menu that allows descriptors or system objects to be relocated from the selected controller to ORCAview.

The Reload sub-menu follows: Descriptors  Reloads descriptors from the selected controller to ORCAview. System Objects  Reloads system objects such as Zone Controller Formats (ZF) from the selected controller to ORCAview. This is only needed if you are communicating with Version 2 controllers. Active Alarms  Reloads the active alarm list from the selected controller device to ORCAview. Reload Replicated Objects  Reloads replicated objects to the selected controller. This feature is mainly used for Access Control. This is the end of the Reload sub-menu.

Object Security (Lock, Unlock and Temporary Login Commands) With a controller selected in the left pane of Navigator, right-click to open the command menu. Selecting the Object Security option provides the Unlock, Lock, and Temporary Login command options. If the selected controller does not support Object security, then the three options are grayed out. If the selected controller does support Object Security, then the options are available in the context menu.




3–49

When you click on one of the Object Security commands, the following ORS Login dialog appears:

To request that the controller enter a specific state, the OWS transmits a BACnet Confirmed Private Transfer containing the requested state, user ID, and password. The controller response to the BACnet Confirmed Private Transfer is either a BACnet success or a BACnet error. Unlock

In the Unlock state, the controller allows all requests. The rules defined in any ORS objects are ignored. To enter the Unlock state, the request’s User ID and Password must match the Master SUA specified in ORS1.

Lock

In the Lock state, the controller restricts access to the controller based on the rules specified in ORS1 (instance 1).

To enter this state: a) the controller is reset, and the database contains ORS1, or b) the requestor’s User ID and Password must match the Master SUA specified in ORS1 Temporary Login

In the Temporary Login state, the controller temporarily enters the login state, where access is based on a specified ORS other than ORS1. This state remains for the amount of time specified in the request. If the user selects Temporary Login, then the request is sent to the device with a 20 minute timeout. The ORS that is used is based on the User ID in the request. The User ID should match one of the SUA’s in the controller’s database. The ORS used for the rules is the one specified in the SUA object.



3–50

Navigator

Temporary Login In lockdown mode, the controller is reasonably secure because only the exposed points are accessible. The service technician must take the device out of lockdown mode to change the controller’s Object Security rules. It is possible for a service technician to log in to a controller and make changes without completely disabling Object Security (i.e. unlocking the controller). A controller-login request saves the MAC address of the requestor (i.e. service tech) and their corresponding Object Security level. During the login period, the controller will apply the rules of the saved Object Security level to all requests from this MAC address while still enforcing the Object Security rules of the default (ORS1) level for all other device/user requests. This service technician feature allows tiered access to the controller’s objects,but it has limitations since the packets are not encrypted and there is no protection from spoofing or replay attacks. This feature supports up to five simultaneous logins. A user remains logged in as long as the controller continues to receive requests from the requestor device. Users are automatically logged out if they remain inactive for the SUA.Auto-Logoff period. New  Creates new objects in the controller. Paste  Places copied object info into the selected controllers. The Navigator (Right Pane) Command >Copy section starting on page 3–39 explains the function including the Cancel All and OK to All buttons. Load  Loads a complete controller database or single object to the selected controller. For a BACstat, only the values for the pre-defined objects are loaded. Note: It is standard practice to load a database from the same controller type into a

controller. However in some situations, it is useful to load a database from a DCU/DSC controller type into a DAC. DAC products have a smaller amount of database memory than a DCU or DSC If a database is too large for a DAC, you can remove some objects (such as unnecessary Inputs, Outputs, or Trend Logs) or GCL programming from the database before you load it. You can also delete or rename objects after a database is loaded. If a database fails to load properly, a failed message appears and the controller will load the database that was previously saved to flash (or will create the default database if there is no database saved to flash).

Note: A password may restrict the use of the Save and Load commands. The Save and Load

Password is defined in the Reset field on the Configuration tab of the Device (DEV) object. You need at least edit permission for the Device object to change this password. Due to memory size limits, there are some objects that do not function in certain Toshiba based controllers (DAC, DNT, and DLC products). If you load a database, that contains any of these objects, into any of these controllers, these objects are loaded, but they are not functional.




3–51

Unavailable Objects for Certain DAC, DNT, DLC Access Event Log (AEL)

Elevator Controller (EC)

Access Group (AG)

Event Router (EVR)

Access Keypad (AK)

Gateway (GW)

Access Setup (AS)

Gateway Translation (GWT)

BBMD List (BMD)

Pulse Input (PI)

Card User (CU)

Remote Panel Settings (RPS)

Card Reader (CR)

System User Access (SUA)

Door Controller (DC)

System User Groups (SUG)

Door Group (DG)

Note: If a database is loaded into a DSC controller that doesn't match the database's

original address, then UDP/IP is disabled and Ethernet is enabled. If UDP/IP is required on the controller, then the settings in the NET object (i.e. new IP Address) must be set. If the database is reloaded into the original controller, then UDP/IP is enabled with the settings that are in the database. This approach avoids circular networks with multiple controllers having the same IP settings and allows the same database to be loaded in multiple Ethernet DSC's. A DCU behaves differently as it always disables UDP/IP whenever a database is loaded.

Save As  Saves the selected controller's database to a file for backup purposes. For a BACstat, only the values for the pre-defined objects are saved. With DAC/DSC controllers, the Save As and Save All commands cause the controller to first save the database to flash memory and then to write a copy of the flash contents to the specified file. The DCU controller does not first save to flash during a Save As or Save All operation. To save a database for a single controller device: 1. Select the controller device in the left pane of Navigator.

2.

Right-click and choose Save As from the pop-up menu.

3.

Type in a suitable File name.

4.

Click Save. The file is saved in the Site folder by default.

Print  This option prints information for an object. The amount of detail depends on whether Short Form or Long Form is selected. From the File menu, select Print Setup and then click either Short Form or Long Form. See Printing in Navigator starting on page 3–56.



3–52

Navigator

Delta Network Commands Right-clicking on the Delta Network gives five options: Find New Devices, Find Device, Load All Descriptors, Reconnect Bluetooth, and Save All.

Find New Devices  This command looks for new controllers on the network. It will search for both BACnet and Version 2 controllers.

Find Device  This command will search for a specific controller on the network by Panel Number. Load All Descriptors  This command automatically loads the descriptors from each controller on the network into ORCAview. The Load all Descriptors feature is useful for large or slow networks where Auto Loading descriptors is disabled. It allows ORCAview to load the descriptors from all known devices for which it has not already loaded descriptors. The user will not have to manually load the descriptors for every device on the network when Auto Loading desciptors is disabled. To use the Load All Descriptors feature:

1.

Right-click the Delta Network or BACnet Protocol icon at the top of the network tree in the left pane of Navigator

2.

Select Load All Descriptors. The OWS will load descriptors for all Devices that have not had their descriptors loaded.

Navigator: Reconnect Bluetooth  ORCAview has a feature within Navigator for reconnecting if the Bluetooth connection is lost. The feature is available when a Bluetooth device is present. The Reconnect Bluetooth command is in the Network context menu and performs the same function as logging out and then logging back into OWS typically using a portable laptop PC.




3–53

The Reconnect Bluetooth option is acccessed by right-clicking on the Network icon in the top left-pane of Navigator. It may take up to 30 seconds to reconnect.

For this feature to be available, a CON-768BT device must be connected to the Service Port of a hardware device such as a BACstat, DSC or DAC controller. The Bluetooth connection can be lost due to moving out of range or by losing power when the CON768BT is physically moved from one controller’s Service Port to another. The CON-768BT has a heartbeat feature that the OWS uses to detect loss of communication. The OWS then displays a message and ask if want to try to reconnect the CON-768BT.

Note: The Navigator Reconnect feature will only function if ORCAview is the only client

connected to SIServer. If other clients are connected (i.e. System Loader, ORCAweb, Historian etc.), they must be closed prior to using this function. The laptop needs to have Bluetooth hardware such as a USB Dongle or an internal Bluetooth device. It must be paired with the proper OUTGOING COM port to define a serial MS/TP connection with passkey security and a subnet address that does not clash with an existing address. The CON-768BT is designed to work best with the Windows Generic Bluetooth stack and the drivers that are included in Windows XP SP2 or later, Vista and Windows 7. Windows should automatically install the drivers when the USB dongle is plugged in.



3–54

Navigator

The range of the CON-768BT is limited to 10 meters (33 feet). Using a 100 meter USB dongle will not improve this range. Sometimes, it may be necessary to move physically closer to the CON-768BT that you wish to make a connection with especially for an environment with lots of electromagnetic noise. Many USB dongles with newer Widcomm or Toshiba (common with Dell laptops) Bluestacks stacks work with the CON-768BT. The pairing procedures with the Widcomm and Toshiba stacks are slightly different as described in the CON-768BT Dongle and Bluetooth Stack Guide found on the Delta Support Site. Refer to the CON-768BT Installation Guide for detailed information on specifications, installation and configuration of the device. To connect through ORCAview using a CON-768BT Connecting through ORCAview with a CON-768BT follows a similar procedure to the original CON-768.

1.

From Start, click Programs | Delta Controls | ORCAview.

2.

From the Logon dialog, click Advanced.

3.

In the Connect Using drop-down, select Bluetooth: BACnet MS/TP.

4.

Choose the virtual COM port associated with the CON-768BT.

5.

Leave the Speed as default. The CON-768BT automatically determines and connects at the correct baud rate to match the MS/TP network.

6.

If necessary, set the Address. In most cases, the OWS MS/TP Address can be left at the default 127. If another OWS is connected to the same MS/TP segment, their addresses must not conflict. Each address must be unique on the MS/TP network.

7.

Click OK to initiate connection.

8. When connected, the Blue Bluetooth LED is on, and flickering with Bluetooth communication. Both the red RX and the green TX LEDs flicker with MS/TP communication activity.




3–55

Save All  Saves all controller databases on the network. When you click on Save All in the menu, the following dialog box appears.

Base Name -The Base Name is used for all the output files. It serves as the root name for all the different devices on the network and the name of the controller is appended to this Base Name. A new Base Name such as Mar_2004 or Mar07_2004 should be used each time a backup is done so that the previous files are not overwriten. Typically, a site might require monthly backups of controller databases and you would keep more than one complete set of databases for the site. This approach limits the possible effect of any problematic database that is saved but will not reload if required. Path - The Browse button allows you to define the Path to the storage location for the database files. With 3.33 DAC/DSC or later controllers, the Save As and Save All commands cause the controller to first save the database to flash memory and then to write a copy of the flash contents to the specified file. The DCU controller does not first save to flash during a Save As or Save All operation. The following procedure allows you to back up all databases on the network with a single command. To save databases for all network devices


1.

Select the Delta Network in the left pane of Navigator

2.

Right-click and choose Save All from the pop-up menu.

3.

If necessary, use the Browse button to set the Path where the database will be saved.

4.

Type in a Base Name that serves as the root name for all the different devices on the network in the Save Database dialog box that pops up. A typical Base Name might be Mar_2011 or Mar07_2011. You would type in a new Base name each time that you did a backup of all databases.

5.

Click OK


3–56

Navigator

Graphics Folder These commands are available when the Graphics Folder is right-clicked in Navigator. If the folder is not visible, do the following: To make the Graphics folder appear in the Navigator left pane:

1.

From the ORCAview Dashboard, select Tools and then Preference. Click Navigator.

2.

Select Show Graphics Folder.

3.

Click OK.

Right-click on the Graphics folder in Navigator to get access to the following commands:

New  Creates either a new Folder for graphics or a new Site Graphic in the current folder. Find Object  Searches for specific object. Use wildcards for a partial name search. Delete  Deletes the currently selected folder and all its contents. A warning message asks if you want to delete the folder and all its contents. Properties  Displays the ORCAview Settings dialog to edit the Site Graphic Path.

Printing Forms in Navigator This section will teach you how to print objects in long or short form. For information on printing alarms, see the Printing Alarm Notifications section in Chapter 5 – Event Management System. For information on printing the Active Alarms Folder, see the Printing to a Windows Printer section in Chapter 5 – Event Management System. The Print command on the right-click menu is one method of printing an object. You can also use Print from the file menu on the dashboard. However, the setting of the Print Setup in ORCAview determines whether a Long or Short form is printed. Long form  Prints most of the properties of the selected object. Short form  Prints a one line summary of the selected object. Short form is the default setting. To select long or short form:

1.

In the ORCAview Dashboard, choose File and then click Print Setup. A Print Options dialog will appear with the following options:



Printing Forms in Navigator

2.

3–57

Choose either Long form or Short form and click OK.

The object printing features are enhanced in ORCAview. Printouts have headers and footers that contain identification information. A solid line separates the header or footer from the body. The header has the Username, the date and time that the printout was Generated On, and the Site requesting the printout.

The Username of the operator initiating the print job is included on the top left hand side of the Header in the format of Username: The Date and Time that the print job executed is displayed on the top right hand side of the Header in the format of Generated On: The Site Name is included immediately below the Generated On field in the format of Site: The footer has the program (ORCAview) that the printout was Generated By and also a current page number of the total page count. The system generating the print job is displayed in the top left of the Footer in the form:

Pagination is displayed in the top right of the Footer: It is in the format of Page of The Print preview features is no longer available for objects in ORCAview.

Printing Objects In Long Form, objects now have more comprehensive information. When you right-click on an object in Navigator and select print, the following symbols may appear in the printout.


[ Symbol ]

Meaning

!

Alarm

#

Overridden

X

OutOfService


3–58

Navigator

A

Auto

M

Manual

H

HVAC,

A

Access, or

L

Lighting object

The following procedures describe how to print using the right mouse Print command. You can use Print from the File menu on the Dashboard. The Print preview features is no longer available for objects in ORCAview. To print a single object:

1.

Right-click on the object in the Navigator and select Print from the menu. A Print window will appear.

2.

Click OK to print or Cancel to exit Print. This is also a good time to select the the appropriate windows printer.

To print multiple adjacent objects:

This method prints objects that are listed together in the Navigator window.

1.

Click once on the first object of a list of objects in Navigator. The object should be highlighted.

2.

Press and hold the Shift key.

3.

Click on the last object in the list. The entire list will be selected.

4.

Right-click on the selected object list and select Print from the menu.

To print multiple non-adjacent objects:

This method prints objects that are not adjacent to each other.

1.

Click on the first object to print.

2.

Hold down the Ctrl key and continue to click on the objects to print. Each clicked object will be highlighted.

3.

Right-click on the object in the Navigator and select Print from the menu A Print window will appear. Click OK to print or Cancel to exit Print.

Searching The Search Menu on the ORCAview Dashboard has a Find Object command that helps an operator find objects easily even in complex systems. The Find Object command of the Search Menu is also available from a right mouse click on a device. Like other ORCAview menus, the Search changes depending on the context. For example, when the GCL editor is open, the Search Menu includes text searching abilities within the GCL program. You can use wildcards in entries. For example, you could enter *AHU*



Printing Forms in Navigator

3–59

To open the Search dialog box:

1.

Select an object in either the left or right hand pane of Navigator. Right-click on the selected object and select Find Object on the menu. The Find Object dialog box opens. (From the ORCAview Dashboard, select Search and click on Find Object.)

2.

Type the name of the object you wish to search for, e.g.: AHU2 Mixed Air Dampers. Use wildcards for a partial name search. Click the Find button. The object name and reference appears in the lower part of the dialog box. When the object is selected, click Open to view the object. Also, double-clicking on the selected object opens it.

Note: Object names are case sensitive.

3.

Use wild cards to find groups of objects. For example, if AH* is typed, all objects in the system whose names start with AH are displayed.

To find objects using the Object Reference:

It is also possible to search for objects based on their object reference or ID. This is done on the following Object ID tab:



3–60

Navigator

Creating Multiple Sites Overview During the installation of ORCAview, a single site is setup. Multiple sites are needed in situations when ORCAview is running on a notebook that is carried from site to site, or a PC that is used to establish remote connections to more than one site. A new Site Settings object should be created for each different site that ORCAview will log in to. You may also transfer the site information from one workstation to another by using the Auto Site Creation feature. A Site Folder (created when a Site Settings object is created) may be copied from the Delta Controls Sites directory on one workstation and pasted into another workstation. ORCAview will automatically create the site from the copied Site folder the next time you login. Before copying a site in this manner, ensure that a site with the same site number does not already exist on the target workstation. ORCAview stores details about each site on the hard disk. This stored information allows ORCAview to log into a site much faster after the first login. The new Site Settings object contains details about the site such as whether Navigator was in details view or list view when ORCAview was last exited. It also holds data about the controllers on this site and descriptor names for the objects within each controller. Each site also has a different set of graphics. Creating a new Site Settings object will also create a new graphics folder within the new site folder. For most installations, the new site and graphics folders are found in: C:\Users\Public\Delta Controls\3.40\Sites\ New Site Settings objects are only created on the workstation. Do not create or change the Site Settings objects that exist in the controllers. To create a new Site Settings object:

1.

Select File/New Site from the ORCAview Dashboard. A new Site Settings (SS) object displays.



General

3–61

2.

Type in the information for the General, Advanced, and Application Protocol tabs. The following three sections describe the tabs of the Site Settings object.

3.

Click on the OK or Apply button to save the Site Setting object information.

General The general tab is used to hold information about the address of the site. The Site Name must be entered but all other fields in this tab are optional. Names for this object cannot contain the following characters: / \ “ ‘ * , $ # < >

Advanced The advanced tab is used to specify the Master and Security Panels on the network. User logging can be set up here as well.

V2 Master Panel If the Master Panel is chosen, ORCAview will automatically reload the system objects such as Units and Scale Ranges from that controller each time this site is logged into.

V2 Security Panel The chosen Security Panel is the one that ORCAview will use to verify the username and password typed at the logon screen. The Security Panel must contain a valid user access object that matches an SUA object on the workstation.



3–62

Navigator

BACnet Master Panel The BACnet Master Panel works similarily to the V2 Master Panel. However, this capability is not normally needed in the Version 3 system.

BACnet Security Panel The BACnet Security Panel can be used to verify the username and password typed at the logon screen when the BACnet Security Panel feature is in use. The Security Panel must contain a valid user access object that matches an SUA object in the workstation. See Chapter 7: Security for more information.

User Logging The User Logging is used to record activities from users who are logged into the system.

User Log File The name of the text file that the User Logging uses to write information.



Application Protocol

3–63

Application Protocol The application protocol tab is used to specify the protocol that is used to communicate with the network at this site. By default, BACnet protocol is enabled and Delta Version 2 protocol is disabled. If the Delta Serial Adapter is selected as the default adapter, the possible options are: •

BACnet Protocol (default)

•

BACnet protocol and Delta Version 2 protocol

•

Delta MicroNet (Micro/Zone) Protocol

•

Delta Version 2 Protocol

If the Ethernet Adapter is selected as the default adaptor, the Delta MicroNet Protocol is excluded from the list of protocol options.

Choosing OK will create the new site.



3–64

Navigator

Auto Site Creation Auto Site Creation allows you to copy the site information from one workstation to another workstation without having to manually recreate the site. In order to use the Auto Site Creation feature, the originating workstation and the destination workstation must have the same version and builds of ORCAview. Ensure that the destination workstation does not already have a site with the same site number. If a site already exists on the destination workstations with the specified site number then only one of the sites will be available in ORCAview. Using Auto Site Creation

The site folder is located at C:\Users\Public\Delta Controls\3.40\Sites on Workstation 1.

1.

Open the site folder on Workstation 1 and ensure that it includes Lsetup.dbr, Delta.dbr, setup.dbr, transactions.dbr, and sites.dbr.

2.

Copy the individual site folder and paste it into on onto a Network Drive or Floppy Disk that Workstation 2 has access to.

3.

Copy the site folder from the Network drive (or Floppy Disk) and paste it into C:\Users\Public\Delta Controls\3.40\Sites. Run ORCAview on Workstation 2.

4.

You will be able to select the new site from the Sites drop down menu at the ORCAview login screen.

Deleting a Site Settings Object If, at some point, you want to delete a previously created site, it is possible. However, ORCAview will not allow the original Site Settings object (SS1) to be deleted. After choosing to delete a Site Settings object, ORCAview will ask if you want to delete the site folder as well. The site folder: •

Contains the details about how the Navigator was configured to display that site: and,

•

Contains the site graphics folder.

•

Contains any saved databases from that site.

Any graphics or databases will be deleted if the site folder is deleted.



Custom Views

3–65

If yes is chosen, the entire folder for that site will be deleted. For most installations the folder in question is found in: C:\Users\Public\Delta Controls\3.40\Sites.

Custom Views Custom views are used to organize your site by mechanical systems or other criteria. You can sort by area, by system, by type, or by almost any other criteria you wish. A sample custom view is already provided in Navigator. Custom Views sort the controller objects from the project into a hierarchy of folders. The folders appear in the left Navigator pane in a tree structure and replaces the normal network view of the system. Folders can contain sub-folders or objects. The contents of a folder are displayed in the right Navigator pane, the same as network view. ORCAview automatically saves any custom views that are created.

Sample Custom Views A Sample Custom View is provided with ORCAview to demonstrate some of the possibilities available to a user. To open the sample custom view:

1.

Right-click in a blank area of Navigator’s left pane.

2.

From the pop-up menu select Custom and then click Sample Custom View.

In the sample view, the following folders are part of the folder Group By Name: •

Objects containing A (The filter is case sensitive.)

•

Objects on controller 1 with A

•

Objects start with A, B, C

Also in the sample view, the following folders are part of the folder Group By Object Type:


•

All Inputs

•

All Outputs

•

Program and Variables

•

Schedules

•

Zones and Controllers


3–66

Navigator

To create new sub-folders:

1.

Right-click on your Sample Custom View folder.

2.

Select New Folder. The Create New SubGroup dialog box appears.

3.

In the Description field, type the new subgroup name, and click OK. In this example the new group name is Group by Name.

4.

In this example, the new sub group has created the main Sample Custom View folder.

5.

You can add sub-folders to your Custom View at any level.



Custom Views

3–67

Creating New Custom Views Creating a custom view occurs in three steps: •

Create new views

•

Create folders and sub-folders

•

Change the folder properties to filter on certain objects.

To create a custom view folder:

1.

Right-click on a blank area of Navigator’s left pane.

2.

From the pop-up menu, select Custom and click New View.

3.

The New Custom View dialog box appears. Type a name in the Description field for your custom view.

4.

Click OK. Navigator will display the newly created view. The new view automatically contains the special folders Active Alarms and Graphics.

To filter objects for custom view folders:

The contents of the various folders in a custom view is sorted by filters. One or more filters can be used for each folder. The different filtering methods are described: •

Filter by object names. (The filter is case sensitive.)

•

Filter by object types such as inputs, outputs, schedules, programs, or variables.

To filter using object references:


1.

Right-click on any folder in your custom view. Select Properties… The ViewGroup dialog box appears.

2.

Double click in the area immediately below Physical. A check mark will appear. Type the object reference in the Descriptor area. For example, AI* will place all analog inputs for all controllers in the folder.

3.

Click Apply to record your filter. If you wish to close the ViewGroup dialog, click OK. The folder displays objects according to the filter you typed.


3–68

Navigator

Note: In the filter description, names are case-sensitive. For example, ahu will not produce the same results as AHU. Object references are not case-sensitive.

Filter Examples To filter by descriptor name for all objects containing the letter A:

1.

Right-click on the folder and select Properties. The ViewGroup dialog box opens.

2.

Double-click on a row under the Descriptor column and type *A* . Click Apply to accept changes and OK to exit. This folder will filter for all objects with an uppercase A in their descriptor name.

3.

In the left Navigator pane click on the folder, Objects containing A. All objects in the network with an A in their descriptor names will be listed in the right Navigator pane. The filter is case sensitive and would not pick an object that with a lower case a.

To filter by descriptor name for objects in controller 100 containing the letter A:

1.


2.

Double-click the row under the Descriptor column and type 100.*A* . Click Apply to accept changes and OK to exit.



Custom Views

3.

3–69

In the left Navigator pane click on the folder Objects on Controller 100 with A. All the objects in Controller 100 that have an uppercase A in their descriptor names are listed in the right Navigator pane. The filter is case sensitive and would not pick an object with a lowercase a.

To filter by descriptor name for all objects starting with an A, B, C:

1.


2.

Double-click on the 1st row under the Descriptor column and type A*

3. 4. 5. 6.

Double-click on the 2nd row under the Descriptor column and type B* Double-click on the 3rd row under the Descriptor column and type C* Click Apply to accept changes and OK to exit. In the left Navigator pane click on the folder. All the objects in the system that have descriptor names starting with an A or B or C, will be listed in the right Navigator pane. The filter is case sensitive and would not pick an object that started with a lower case letter.

To filter by object type for all Analog Inputs:

1.


2.

Double-click on the 1st row under the Physical column to enable the checkbox.

3.

Double-click on the 1st row under the Descriptor column and type *.AI*

4.


Click Apply to accept changes and OK to exit.


3–70

Navigator

5.

In the left Navigator pane click on the folder. All the Analog Input objects in the system will be listed in the right Navigator pane.

To filter by object type for all the Programs and Analog Variables:

1.


2.

Double-click on the 1st row under the Physical column to enable the checkbox. Double-click on the 1st row under the Descriptor column and type *.PG*

3.

Double-click on the 2nd row under the Physical column to enable the checkbox. Double-click on the 2nd row under the Descriptor column and type *.AV*

4.

Click Apply to accept changes and OK to exit.

5.

In the left Navigator pane click on the folder. As a result all the Program and Analog Variable objects in the system will be listed in the right Navigator pane.



Custom Views

3–71

Export & Import The Export and Import commands on the ORCAview Dashboard allow existing custom Views to be used on other ORCAview stations. Using these commands, it is possible to Export a Custom View, save it to a disk and then Import it into a different ORCAview workstation of the same version. This would work with multiple ORCAview workstations. When a Custom View folder is Exported, all the sub-folders below the top level are also saved. To Export an entire Custom View, it is only necessary to save the top-most folder. To Export a Custom View:

1.

Right-click any custom view folder. Select Export…

2.

Select the drive and directory where you want to save the folder. Type a file name in the File name field. Click Save.

3.

The selected folder and all its sub-folders will be saved to the selected directory.

To Import a Custom View:

1.

Select a folder in a Custom View. Right-click and Select Import

–OR–

2.

From the ORCAview Dashboard, click File and then click Import…

3.

In the Import Custom View dialog box, specify the file you wish to import.

4.

To import as a new Custom View, select Import as Root. To import as a sub-folder, select Import under the current folder. If no folder is selected in the current Custom View, only the Import as Root option is available.

5.

Click Open.

Note: Custom Views are saved with a .cvx extension.



3–72

Navigator

INDEX CHAPTER 3 NAVIGATOR —A —

active alarms filter · 3–33 Apply · 3–34

—B —

Bluetooth configuration · 3–53

—C —

command Lock / Unlock / Temporary Login · 3–48 CON-768BT range · 3–54 controller addressing · 3–17 CON-768BT Bluetooth · 3–53 icons, meaning of · 3–14 misconfigured address · 3–15 network status icons · 3–13 off line · 3–14 off-line · 3–44 on-line · 3–45 red question mark · 3–15 red X · 3–14 remove area · 3–47 software version mismatch · 3–16 yellow question mark · 3–13 yellow wrench · 3–15 cts right mouse menu · 3–36 custom views export and import · 3–71 Custom Views · 3–65

—D —

database Clear Database · 3–46 find object · 3–47 load · 3–50 Load From Flash · 3–45 save all · 3–55 Save To Flash · 3–45 descriptors reload · 3–48 Descriptors case sensitive · 3–59 Load All Descriptors · 3–52 reload · 3–48 Detail View · 3–25 Columns · 3–28

—F —

Filter Icon · 3–32 Filtering · 3–66


—G —

Graphics folder new folder or site graphic · 3–56 Graphics Folder delete folder · 3–56 delete with Site Settings Object · 3–64 find object · 3–56 make visible · 3–56 properties · 3–56 right click menu · 3–56 with new site · 3–60

—L —

Lock Unlock · 3–48 long form, printing · 3–56

—M —

master · 3–62 master panel function · 3–61 Site Settings Object · 3–61

—N —

Navigator · 3–4 Auto Refresh icon · 3–27 controllers and workstations · 3–44 create new object · 3–38 Description column display · 3–23 Detail View · 3–25 details view · 3–27 filter · 3–29 filter active alarms · 3–33 filtering, advanced · 3–30 Find Device · 3–52 Find New Devices · 3–52 functions · 3–6 graphics folder right click menu · 3–56 icons in left pane · 3–8 left pane objects · 3–8 left pane right click menu · 3–43 left pane views explained · 3–10 Load All Descriptors · 3–52 Lock Unlock · 3–48 Logical view · 3–12 manual Refresh icon · 3–27 Network View · 3–11 Object Security · 3–48 Object Type column · 3–23 ORS Login · 3–49 Refresh Rate Real Time data · 3–26 remove area · 3–47 right click menu · 3–44 right click menu, controllers and workstations · 3–44


Custom Views

right click menu, Graphics Folder · 3–56 right mouse menu · 3–36 right pane · 3–10 search menu · 3–58 Show Real-time Data · 3–25 software version mismatch · 3–17 sort objects · 3–28 sort, Details View · 3–27 temporary login · 3–50 Temporary Login · 3–48 Navigator Window · 3–7 network Bluetooth connection · 3–52 delete controller · 3–44 query device · 3–44 save all databases · 3–55 network connection disconnected or connected · 3–13 network object types · 3–8

—O —

Object Reference · 3–39 Object Restriction Settings (ORS) · 3–48 Object Security · 3–48 Object Type · 3–23 Objects copy and paste · 3–39 copy, Navigator right click menu · 3–37 create new · 3–38 create new, Navigator right click menu · 3–50 cut, Navigator right click menu · 3–37 filtering, advanced · 3–30 filtering, basics · 3–29 find database object · 3–47 find object · 3–59 find, Navigator right click menu · 3–37 help · 3–35 object number · 3–39 Object Security · 3–48 opening · 3–34 paste, Navigator right click menu · 3–37 paste, Navigator right click menu · 3–50 print information, Navigator right click menu · 3–37

print, Navigator right click menu · 3–15 print, Short or Long Form · 3–51 printing · 3–58 refresh indicator · 3–35 rename · 3–37 save as, Navigator right click menu · 3–37 Selecting and organizing in Navigator right pane · 3–34 selecting in Navigator · 3–34 unavailable certain products · 3–50 ORS Login · 3–49


3–73

—P —

Preference menu view · 3–13 Printing Long Form · 3–56 Objects · 3–58 Print Options dialog · 3–56 Short Form · 3–56 symbols, meaning of · 3–57

—R —

red question mark · 3–15 red X · 3–44 refresh indicator, objects · 3–35 reload descriptors · 3–48 replicated objects · 3–48 system objects · 3–48 remove area · 3–47 replicated objects reload · 3–48 Right click graphics folder · 3–56 right hand Navigator pane objects · 3–34

—S —

Search · 3–58 Security Panel as entered in Site Settings Object · 3–61 function · 3–61 Short Form, printing · 3–56 Show Real-time Data · 3–25 site Auto Site Creation · 3–64 Site configuration · 3–61 delete Site Settings Object · 3–64 master panel · 3–61, 3–62 multiple sites · 3–60 protocol · 3–63 security panel · 3–62 Site Settings Object, function · 3–60 Site Settings Objects, multiple · 3–60 Site Settings Object how to configure a new site · 3–61 software version mismatch · 3–17 system object hide or show · 3–32 system objects · 3–32 hide or show · 3–32 reload · 3–48

—T —

Temporary Login · 3–48


3–74

Navigator

—U —

Update Detail View · 3–25

—V —

version mismatch · 3–17


—W —

workstation or controller right click menu · 3–44

—Y —

yellow question mark · 3–13 yellow wrench · 3–15


Chapter 5 – EVENT MANAGEMENT SYSTEM Chapter 5 Contents OVERVIEW ........................................................................................................... 5–5 EVENT (EV) ...................................................................................................... 5–9 EVENT HEADER ................................................................................................... 5–9 GENERAL ........................................................................................................... 5–11 SETUP................................................................................................................ 5–12 Name .................................................................................................. 5–12 Alarm Type ........................................................................................ 5–13 Alarm Input ........................................................................................ 5–13 Alarm Lockout (Optional) ................................................................ 5–13 Setup: Time Delay ............................................................................ 5–13 HVAC, Access, and Lighting Checkboxes .................................... 5–14 MESSAGES ........................................................................................................ 5–15 Auto Generated Alarm Messages (DSC/DAC Only) ................... 5–17 EVENT CLASS TAB ON EVENT OBJECT............................................................. 5–20 Event Class ....................................................................................... 5–21 Notification Method .......................................................................... 5–21 Transitions, Send at Priority and Operator Acknowledged ........ 5–21 Destination List Dataview ................................................................ 5–22 DESCRIPTION .................................................................................................... 5–24 ALARM TYPES FOR EVENT ................................................................................ 5–24 Out of Range ..................................................................................... 5–24 Change of State ................................................................................ 5–27 Floating Limit ..................................................................................... 5–30 Command Failure ............................................................................. 5–33 Change of Value ............................................................................... 5–35 Value Type: Bitstring ........................................................................ 5–37 Change of Bitstring ........................................................................... 5–40 EVENT CLASS (EVC) ................................................................................... 5–46 Status ................................................................................................. 5–46 DEFAULT DATABASE EVENT CLASSES ............................................................. 5–47 TABS ON EVENT CLASS OBJECT ...................................................................... 5–56 Setup .................................................................................................. 5–56 HVAC, Access, and Lighting Checkboxes .................................... 5–57 Destination List Tab ......................................................................... 5–58 Description......................................................................................... 5–62 EVENT FILTER (EVF) ................................................................................... 5–63 MAIN .................................................................................................................. 5–63 Name .................................................................................................. 5–64 Priority Override ................................................................................ 5–64 Reference an EVF in an SUA ......................................................... 5–65 HVAC, Access, and Lighting Checkboxes .................................... 5–66 EVENT ROUTER (EVR) ................................................................................ 5–66



5–2

Event Management System ALARM FILTERING (UPDATED 3.40) ................................................................. 5–67 Name ................................................................................................. 5–67 Send Acknowledgements ............................................................... 5–67 Schedule Reference ........................................................................ 5–67 Classes and/or Events to Route .................................................... 5–68 SETUP ............................................................................................................... 5–70 Destination Type .............................................................................. 5–71 Message Format .............................................................................. 5–72 URL Address (HTTP Destination Type) ....................................... 5–73 End of Job Insert .............................................................................. 5–74 File Name .......................................................................................... 5–74 Printer Name .................................................................................... 5–74 Port Status ........................................................................................ 5–74 Baud Rate ......................................................................................... 5–75 Dial Retries ....................................................................................... 5–75 Init String ........................................................................................... 5–75 Modem Type ..................................................................................... 5–75 Dial Prefix .......................................................................................... 5–75 HVAC, Access, and Lighting Checkboxes ................................... 5–76 DESTINATIONS / ALARM ESCALATION TAB....................................................... 5–76 Current Selection ............................................................................. 5–77 Status................................................................................................. 5–77 First Destination to Try .................................................................... 5–79 Current Destination .......................................................................... 5–79 Auto Escalation ................................................................................ 5–79 Number of Alarm Retries ................................................................ 5–79 Retry Interval .................................................................................... 5–79 Debug Messages ............................................................................. 5–79 DESCRIPTION .................................................................................................... 5–80 EVENT LOG (EVL) ........................................................................................ 5–81 LOG TAB ........................................................................................................... 5–81 Top Dataview: .................................................................................. 5–82 Details on Highlighted Events ........................................................ 5–82 Buffer Ready ..................................................................................... 5–88 SETUP ............................................................................................................... 5–88 Name ................................................................................................. 5–88 Reliability ........................................................................................... 5–89 Maximum Log Entries ..................................................................... 5–89 Archival Buffer Notification Setup: ................................................. 5–89 HVAC, Access, and Lighting Checkboxes ................................... 5–90 ALARM FILTERING (UPDATED 3.40) ................................................................. 5–90 Schedule Reference ........................................................................ 5–91 Classes and/or Events to Log ........................................................ 5–91 DESCRIPTION .................................................................................................... 5–93 EVENT AND ALARM SETTINGS (EVS) ................................................... 5–94 SETUP ............................................................................................................... 5–94 V3 Alarms to Track .......................................................................... 5–95 Auto Load Active Event List(s) ....................................................... 5–95 Max Event Activities in List ............................................................. 5–95 Max Notification Buffer .................................................................... 5–96 Notification Retry Interval ............................................................... 5–96 STATS ............................................................................................................... 5–96 Event Activity Statistics ................................................................... 5–97 Event Class Statistics:..................................................................... 5–98

ORCAview Version 3.40 Technical Reference Manual Ed.. 1.80 Original Page 5–2 Total Pages in this Section: 176

Overview

5–3

Notifications Statistics ...................................................................... 5–98 ACTIVE ALARM LISTS ........................................................................................ 5–99 Active Alarm List Sizing ................................................................... 5–99 Tracked Alarms in the Active Alarm List of a Device .................. 5–99 Auto Loading Active Alarm Lists on Startup ............................... 5–101 VIEWING ACTIVE ALARMS WITH NAVIGATOR.................................. 5–103 ACTIVE ALARMS FOLDER ................................................................................ 5–103 Update Active Alarms .................................................................... 5–104 ACTIVE ALARMS FILTER .................................................................................. 5–104 Update Active Alarm List ............................................................... 5–105 ROUTING NOTIFICATIONS TO PRINTERS, FILES, PAGERS AND EMAILS................................................................................................... 5–106 PRINTING ALARMS........................................................................................... 5–106 PRINTING TO A W INDOWS PRINTER................................................................ 5–107 Printing the Active Alarms Folder ................................................. 5–108 INSTALLING A DOT MATRIX PRINTER DRIVER ................................................ 5–109 PRINTING TO FILE............................................................................................ 5–113 Event Router Object 1 ................................................................... 5–113 ROUTING ALARM NOTIFICATIONS TO AN ALPHANUMERIC PAGER ................. 5–114 Setup for Alphanumeric Paging ................................................... 5–115 ROUTING ALARM NOTIFICATIONS TO A NUMERIC PAGER .............................. 5–118 Setup for Numeric Paging ............................................................. 5–118 ROUTING ALARM NOTIFICATIONS TO EMAIL ................................................... 5–121 Notification Buffers ......................................................................... 5–126 HTTP ALARM NOTIFICATION.................................................................. 5–127 INTRODUCTION ................................................................................................ 5–127 FEATURES ....................................................................................................... 5–127 LIMITATIONS .................................................................................................... 5–127 HTTP POST REQUEST MESSAGE CONTENT ................................................ 5–128 Example: HTTP POST request message ................................... 5–130 CONFIGURING HTTP ALARM NOTIFICATION .................................................. 5–130 Notification Buffers ......................................................................... 5–131 STATUS MESSAGES ........................................................................................ 5–132 W EB SERVER ASP/PHP EXAMPLES.............................................................. 5–132 Microsoft-IIS ASP Example........................................................... 5–133 Apache PHP Example ................................................................... 5–134 Generated Alarm Log .................................................................... 5–134 DSC PRINTING ............................................................................................ 5–135 DSC SERIAL PRINTING ................................................................................... 5–135 Selecting a Serial-to-Parallel Converter for a DSC ................... 5–135 Configure Event Router for Local Printing .................................. 5–136 ALARM NOTIFICATIONS .......................................................................... 5–137 SENDING ALARM NOTIFICATIONS OVER MODEM CONNECTIONS ................... 5–137 Sending Alarm Notifications to ORCAview via Modem ............ 5–137 ORCAVIEW AUTO-ANSWER FOR ALARMS ..................................................... 5–142 ALARM ESCALATION ............................................................................... 5–146 TABLE OF CONTENTS ...................................................................................... 5–146 INTRODUCTION: ALARM ESCALATION ............................................................. 5–147 Definitions ........................................................................................ 5–147



5–4

Event Management System Basic Operation.............................................................................. 5–148 Various Scenarios .......................................................................... 5–149 Alarm Flood Suppression ............................................................. 5–150 Network Layout .............................................................................. 5–151 Determining a Policy ..................................................................... 5–151 SETTING UP ALARM ESCALATION AND IMPLEMENTING THE POLICY ............. 5–153 System User Access (SUA) ......................................................... 5–153 Event Router (EVR) ....................................................................... 5–154 EXAMPLES ...................................................................................................... 5–158 EXAMPLE 1: TWO SEPARATE GROUPS (DAYTIME/EVENING) ........................ 5–158 Determining the Policy .................................................................. 5–158 Implement the Policy ..................................................................... 5–159 EXAMPLE 2: IT GROUP ................................................................................... 5–167 Determining the Policy .................................................................. 5–167 Implement the Policy ..................................................................... 5–168 EXAMPLE 3: MANUAL ESCALATION ................................................................ 5–174 IMPLEMENTATION GUIDELINES ....................................................................... 5–175


Overview

5–5

Overview The event management system provides the operator with a method of monitoring a property of an object and sending alarm notifications to devices. The event management system is made up of 6 main objects. Event –

EV on page 5–9

Event Class –

EVC on page 5–46

Event Router –

EVR on page 5–66

Event Filter –

EVF on page 5–63

Event Log –

EVL on page 5–81

Event Settings – EVS on page 5–94 If you have a site with Version 2 controllers, see Appendix D: – Using ORCAview with Version 2 Sites. BACnet Objects  The Event (EV) and Event Class (EVC) objects are defined by the BACnet protocol. In the BACnet specification, these objects are called Event Enrollment and Notification Class but we call them Event and Event Class in this document. The event management system is based on the classification of Events and Alarms as explained in the Notification Method section starting on 5– 21. For example alarms that indicate equipment maintenance is required could all be classified as Maintenance alarms. The actions that the Event Management system takes when an alarm occurs are frequently based on the classification of the alarm. In the example given, the Maintenance alarm could be printed in the service person's office. Event objects define the alarm condition to monitor for a specific object. The Event object contains setup information such as the type of activity that warrants a notification, the parameters required to set up each type of Event, the object and property to be monitored and the classification of the Event. Event Class objects provide a method of classifying Events as well as the distribution of Event notifications. The Event Class object specifies a list of devices that the event notifications are to be sent to and also determines the Notification Retry intervals. Proprietary Objects  The remaining 4 objects are the Event Router, Event Log, Event Settings, and the Event Filter. These objects are all proprietary to Delta Controls and cannot be seen by another vendor’s operator workstation. Event Router (EVR) objects are used to print, page, email, or save alarm notifications to text files. The Event Router contains setup information such as destinations for different alarm types and the list of events and event classes that are routed. It also contains parameters for the setup of email or pager routing. Event Filter (EVF) objects are used to specify which Event Notifications are to be ignored by ORCAview. The object also allows the supervisor to specify what Events are not acknowledgeable or removable by a specific user.



5–6

Event Management System The Event Log object specifies a list of Events or Event Classes. The corresponding notifications are recorded in the log. The Event Log stores details for each entry in the log. The Event Settings (EVS) object is used to set up general device event processing options. It specifies how large the active alarm list can be in the device, whether there is a master alarm device on the network and whether to track local or remote Events. It also holds statistical data about the event management system.


Overview

5–7

Event Sequence Flow Chart

Sequence for the High Limit Transition of an Event on a DCU 1 Event Transitions to High Limit

2 Event Management System checks the Event Class

3 Alarm Notification is loaded into Alarm Notification buffer

A

4 Alarm Notification is sent to Destination Devices

C

B

5 Remote DCU receives alarm notification

5 Local controller receives alarm notification

6 Event Log (EVL)

Local controller tracks its own active alarms in its Active Alarm List

6 Event Router (EVR)

7 Physical Printer


5 ORCAview PC receives alarm notification

ORCAview tracks all active alarms in its Active Alarm List

6 Event Router (EVR)

7 Physical Printer


5–8

Event Management System The following sequence of events is shown in the previous figure: 1

The Event goes through a Normal to High Limit transition. Ex: Room temp goes out of range.

2

The event management system looks to the referenced Event Class and determines which devices are to receive the alarm notification. By default the event management system will broadcast alarm notifications to every device on the network. (Except non-established modem connections)

3

The alarm notification is then loaded into the local device’s alarm notification buffer.

4

The local device then begins sending the notification to the each device listed in the Event Class objects. This part of the process happens in milliseconds unless a modem connection is needed to send the notification, which can take minutes. The local device is the device that contains the alarm.

5

The destination controller and ORCAview handle tracking remote alarms in a slightly different manner. A remote alarm is an alarm that was generated on another device.

6

7

A. The local controller will track its own active alarms in its Active Alarm List. B. A remote controller will not track active alarms from other devices in its Active Alarm List. C. A remote ORCAview workstation will track active alarms if the alarms are broadcast, or if the workstation is listed in the Destination List of the Event Class object. When a device receives a notification, the event management system looks to the Event Router and the Event Log for instructions on how to process it. A device can print and/or log Event notifications from these classes regardless of whether it is tracking remote alarms in its Active Alarm List. The notification is then routed to the destination Printer.

Note: The process that has been outlined above is only valid for devices that are

using the default event settings. The Event Management System can be customized resulting in different alarm processing methods.

Note: In the DAC family of controllers, only DSC controllers can process and

redirect alarms. The other controllers cannot redirect alarms to printers. Remote DAC’s cannot receive or process alarms.


Event Header

5–9

EVENT (EV) The Event object’s main purpose is to provide a method for identifying the conditions that warrant an alarm notification. This is done by selecting an alarm type and accompanying parameters. The type of Event is selected within the Event object. The Event object monitors the named property of an object. Note: An Event object does not function until the monitored Input or Output

object is commissioned. Each Input and Output has a Commissioned field. This field must be checked. When an Input or Output object is Decommissioned, a Lock symbol is shown beside it in Details view in Navigator. The Commissioned field applies only to the products of Delta Controls.

Note: To disable alarm pop-ups dialogs open the user’s SUA object on the Local

OWS, click on the User Data tab and place a checkmark in the field labeled Disable Alarm Pop-ups. For the changes to take effect the user must log out and log back in.

Event Header The header area of the Event object gives details about that particular Event and its alarm input object. The header displays the alarm type. The parameters for the particular alarm type are displayed directly below it. Directly below the parameters the Alarm Input object is displayed along with its present value.

The previous figure is an Out of Range alarm type. The Low Alarm and High Alarm fields display before the Alarm Input field. The header area also displays the Pending Alarm box. The Delay countdown is also displayed to the immediate right of Pending Alarm. Pending Alarm prevents the system from sending alarms unless an alarm condition persists for the Time Delay defined on the Setup tab of the Event object. When a temperature or other monitored object is in an alarm condition, the system can delay sending the alarm. The Pending Alarm field displays the specific alarm condition such as High-Alarm. This approach eliminates spurious alarm notifications caused by noise on a monitored value.



5–10

Event Management System The Last Alarm Input Value field displays in the header only for a Change of Value alarm type when the Value Type field is set to Increment. This field shows the last value that caused an alarm.

Object Mode:

The Event (EV) object has Auto and Manual modes. You toggle from one mode to the other by clicking on the hand icon near the top of the dialog. In Auto mode, the object will function normally and display the status of the monitored object. A typical status is Normal In Manual mode, the Event object ceases to monitor the Alarm Input defined in its Setup tab. When in Manual mode, it is possible to set the status value using the dropdown list that appears when the object is in manual.

Event Value: The value of the Event object is dependent on the alarm type that is monitoring the alarm input. The Event can have the following values: Normal  The Monitored value is operating as expected for all alarm types. Alarm  The Monitored value is not as expected for a Change of State or Command Failure. High Alarm  The Monitored value is greater than the High Limit for an Out of Range or Floating Limit alarm type.



General

5–11

Low Alarm  The Monitored value is less than the Low Limit for an Out of Range or Floating Limit alarm type. Fault  The fault flag of the monitored object is set. This may indicate an I/O problem such as a broken wire or a device that is off-line. For example, if an Event object monitors an Analog Input (AI) and a DCU controller is not properly connected to a Baseboard, then the AI goes into Fault. The Event issues a Fault alarm. Trouble  This value is part of the BACnet standard but Delta Controls does not use it. Unknown  This value is part of the BACnet standard but Delta Controls does not use it. Further descriptions for the Event values and transitions are given in the description for each alarm type.

General The General tab gives general information about the transitions of the Event object. It displays the time and date when that transition last happened as well as a transition count since it was last acknowledged. When a transition is acknowledged the "Transitions since Ack" count is reset back to 0.

Transition count since an operator acknowledged.

Time of last transition.


Shows that operator acknowledgement is not necessary for the transition.


5–12

Event Management System Note: If a transition does not need an operator acknowledgement the message

“No Acknowledgement Required” is displayed under the Transitions since Ack column.

Setup The monitored object the conditions that warrant an Event transition are specified on the Setup tab. The Setup tab contains such items as the alarm type and accompanying parameters for the selected alarm type.

Name This is the name given to the Event object at creation. This is an editable field. Name is a descriptive label given to an Object. Typically, a name is less than 20 characters in length. The length of a name is from 1 to 255 characters on a DCU or an OWS and 1 to 67 characters on a DAC. The name must be unique among the objects located on the same controller.



Setup

5–13

Alarm Type This field specifies the type of algorithm that will be performed on the alarm input object and property. When an alarm type is selected the parameters specific to the type will appear for setup. Available alarm types are: •

Out of Range on page 5–24

•

Change of State on page 5–27

•

Floating Limit on page 5–30

•

Command Failure on page 5–33

•

Change of Value on page 5–35

•

Change of Bitstring on page 5–40

See the Alarm Types for Events section starting on page 5–24 for more information. Note: With DAC/DSC, when you select an Alarm Type of Change Of Bitstring or

Change of Value, the Use Auto Generated Messages checkbox is automatically disabled. These alarm types do not automatically generate a message.

Alarm Input This field specifies the object and its property that is to be monitored by the Event. The field will accept entries in the following form: *.obj*.property. By default the property is "Value" but may be changed to any other valid property of the referenced Alarm Input object. The following list some examples of Alarm Input entries used to monitor the following: •

value of analog input 1 on device #1, enter: 1.AI1.Value

•

status flags of binary input 1 on device #2, enter: 2.BI1.statusFlags

•

fault flags of binary input 1 on device #2, enter: 2.BI1.Flags

Alarm Lockout (Optional) This setting is optional. It is provided for situations when the Event is to stop transitioning based on the state of a binary object. If the referenced binary object goes to its OFF state the Event will stop transitioning. The field will accept entries in the following form: *.obj*.property. By default the property is "Value" but may be changed to any other valid property of the lockout object.

Setup: Time Delay The amount of time in between the alarm input satisfying the conditions to alarm and the actual transition. If the alarm input returns to a normal condition before the timer counts down, the Event will not transition.



5–14

Event Management System In DAC/DSC products, there is no time delay when returning to Normal. All other transitions apply the time delay. The time delay is enforced as follows in DAC/DSC products: From-State

To-State

Delay Applied

Normal

Alarm

Yes

Alarm

Normal

No

Normal

Fault

Yes

Fault

Normal

No

Alarm

Fault

Yes

Fault

Alarm

Yes

In the OWS/DCU, there is a time delay when transitioning to Alarm and when returning to Normal. Fault transitions do not use the time delay. The time delay is enforced as follows in the OWS/DCU: From-State

To-State

Delay Applied

Normal

Alarm

Yes

Alarm

Normal

Yes

Normal

Fault

No

Fault

Normal

No

Alarm

Fault

No

Fault

Alarm

No

HVAC, Access, and Lighting Checkboxes These checkboxes indicate which application(s) the object is part of. Any combination of the HVAC, Access Control, and Lighting applications can be selected. Leaving all checkboxes blank is the same as checking them all. As a part of OWS security, these checkboxes allow an operator to see only the objects for a particular application(s). For example, a site may have separate operators for the HVAC and Access applications. It is possible for each operator to only see the objects related to their application. Note: For more information on how to set up and administer Object Application

Restrictions, see Chapter 7- Security of the ORCAview Technical Reference manual.



Messages

5–15

When a checkbox is checked, an indicator icon appears at the top of the dialog. The three application areas are:

Application HVAC (Red)

Icon

Access (Blue) Lighting (Green)

Messages The Messages tab allows a message to be specified for the Alarm, Fault, and Return to Normal transition messages.

Note: In ORCAview 3.30, the term off-normal was replaced with in-alarm.

The Use Auto Generated Messages checkbox is available on DSC/DAC controllers. Enter a message for the transition here. On a DCU controller, you need to enter messages for the Alarm, Fault, and Return to Normal fields. With a DSC/DAC, you can use the Use Auto Generated Messages feature or enter your own messages.



5–16

Event Management System The message text edit boxes accept event messages up to 255 characters long for each transition. The messages are included when the alarm notification is displayed on the workstation, printed to a printer, or logged to Event Log (EVL). Note: f a large message is entered and you are using alphanumeric paging or

short text message format to send alarm notifications, then the notification is truncated to 130 characters.

With a DCU controller, you need to manually enter messages so that the alarm printouts or print to files are useful. Typically a message would include a concise description of the problem with a typical response to the alarm. The message can include the object references (e.g. 890000.AI8) for an object. The following Alarm Notification shows the Alarm message that was entered in Alarm field on the Messages tab of the Event (EV) object.

A print out or a print or file using EVR1 might look like the following.



Messages

5–17

Auto Generated Alarm Messages (DSC/DAC Only) The Use Auto Generated Messages checkbox applies only to DAC and DSC controllers. If the user leaves the corresponding message field for an event blank or the event is intrinsic, then a standard message is generated and no additional message or spaces are appended to the printout or notification.

If there is text in the event message fields, then this will be included first with a space separating it from the auto generated alarm message that follows. Note: There is a ‘Use Auto Generated Messages’ checkbox in the Messages tab of the EV object. If it is checked, the Alarm Notification will contain the auto generated alarm message and the text entered in the message text box. When you select an Alarm Type of Change Of Bitstring or Change of Value, the Use Auto Generated Messages checkbox is automatically disabled. These two alarm types do not automatically generate a message. If the checkbox is unchecked, the Alarm Notification will only display the text entered in the message text box.



5–18

Event Management System The following figure shows a high limit alarm message for an Out of Range Alarm Notification.

Auto Generated Alarm Text

Alarm Messages (DSC/DAC Only) Alarm Type

Description

Change of Bitstring

Not Applicable

Change of State

<> (<>) is in ALARM

Change of Value

Not Applicable

Command Failure

<> (<>) does not match <> (<>)

Example: AHU1 Filter Status (Dirty) is in ALARM

Example: AHU1 Supply Fan Control (Start) does not match AHU1 Supply Fan Status (Stopped) Floating Limit

High-Limit <> (<>) has exceeded its HIGH LIMIT (<>) Example: AHU1 Supply Air Temperature (32.3) has exceeded its HIGH LIMIT (30.0)

Floating Limit

Low-Limit <> (<>) has dropped below its LOW LIMIT (<>) Example: AHU1 Supply Air Temperature (11.8) has dropped below its LOW LIMIT (13.0)



Messages

5–19

Alarm Messages (DSC/DAC Only) Alarm Type

Description

Out of Range

High-Limit <> (<>) has exceeded its HIGH LIMIT (<>) Example: AHU1 Mixed Air Temperature (28.9) has exceeded its HIGH LIMIT (26.0)

Out of Range

Low-Limit <> (<>) has dropped below its LOW LIMIT (<>) Example: AHU1 Mixed Air Temperature (8.0) has dropped below its LOW LIMIT (11.0)

Fault and Acknowledged Messages (DSC/DAC Only) Fault Messages

All fault messages are be in the same format. <> is in FAULT and needs attention Example: AHU1 Supply Fan Control is in FAULT and needs attention

Acknowledged Messages

All of the Alarms will have the same format for a generated Acknowledgement message. Delta Alarms <> <> Alarm Acknowledged by (<>) Example: AHU1 SAT HIGH LIMIT Alarm Acknowledged by Wen (Wen’s PC) rd

3 Party Alarms <> <> Alarm Acknowledged by <> Example: AHU1 SAT LOW LIMIT Alarm Acknowledged by Alerton PC



5–20

Event Management System

Returned to Normal Messages (DSC/DAC Only) Alarm Type

Description

Change of Bitstring

Not Applicable

Change of State

<< Alarm Input Name>> (<>) has returned to Normal

Change of Value

Not Applicable

Command Failure

<> (<>) has returned to Normal <> (<>)

Example: AHU1 Filter Status (Clean) has returned to Normal

Example: AHU1 Supply Fan Control (Start) has returned to Normal AHU1 Supply Fan Status (Start) Floating Limit

<> (<>) has returned to Normal Example: AHU1 Supply Air Temperature (23.4) has returned to Normal

Out of Range

<> (<>) has returned to Normal Example: AHU1 Mixed Air Temperature (15.9) has returned to Normal

Event Class Tab on Event Object The Event Class tab is where the user selects which Event Class the Event is to be a member of. All Events default to the Notification class. The Event Class is mainly used to specify the devices that the event notifications are to be sent to. By default notifications are broadcast to all devices on the network.

Event Class tab gives details about the selected Event Class.

The Notification Method is defined in the Notification EVC



Event Class Tab on Event Object

5–21

Event Class The Event Class object contains user settings like priority levels and acknowledgement settings. Once an Event Class is selected its settings are displayed. This makes it easier for the operator to confirm their choice. The data displayed is not editable from within the Event and must be adjusted through the Event Class itself. For more details about the Event Class see the Event Class section starting on page 5–46 of this chapter. If the EVC field is blank or invalid then by default notifications are sent to EVC1 but Acknowledgement is not required.

Notification Method Notifications can be specified as either Alarms or Events in the Event Class (EVC) object. When Event is selected, transitions for this Event Class will not cause the alarm bell to show up in the monitored object’s dialog header nor in Navigator's alarm state column for the monitored object or the taskbar tray. When the Notification Method is set to "Event", the external Alarm Flag is not set in the status flags of the monitored object. Operation is normal if the Notification Method is set to Alarm.

Transitions, Send at Priority and Operator Acknowledged The dialog displays the Send at Priority and Operator Acknowledged settings for the Alarm, Fault and Return to Normal Transitions of the assigned Event Class (EVC) object. The data displayed is not editable from within the Event object and must be adjusted through the Event Class object itself. Send at Priority (Defined in EVC)

The Send at Priority setting is necessary in cases where two events become active at the same time. The event management system uses the priority value to order event notifications in a notification queue. This includes both notifications generated by the local device and notifications received from a remote device. The queue is sorted from lowest priority number (highest priority) to highest priority number (lowest priority). Items are taken off of the queue and are routed to local peripherals and distributed to remote devices. A remote critical notification that is received at the same time as a local maintenance notification will be placed ahead of the maintenance alarm in the queue and will be routed before the maintenance alarm.

Operator Acknowledged (Defined in EVC)

Operator Acknowledged checkboxes determine whether or not an operator must acknowledge that transition. Events will remain in the active alarm list until the transition has returned to normal and has been acknowledged. By default the Alarm and fault transitions require acknowledgement.



5–22

Event Management System

Destination List Dataview The Destination List dataview displays the Device Address, Retry, Confirmed Transmission, and Process ID columns. Device Address (Defined in EVC)

The device address is the address of the BACnet device that will be sent a notification from any events that reference this class. By default the column is set to BROADCAST and the notifications will be sent to every device on the network. For an event to be sent to only a specific remote controller, the corresponding EVC objects in both the OWS and controller where the event originates must be identical. This column allows the user to enter either a logical address (e.g., 1.DEV1) or a physical network address (e.g., NET1).

Note: The default setting of “Broadcast” will not establish dial up connections. In order to establish a modem connection for an alarm transition, the specific network number must be entered into the “Device Address” column.

If the device address does not have ‘BROADCAST’ and if ORCAview is NOT named in the destination list: 1

The Operator Workstation will not display an alarm notification for Events of that class.

2

The active alarm will not be loaded when commanding the Active Alarms Folder to Update Alarms.

3

The active alarms of that class cannot be reloaded from a device.

For a logical address, just enter the .

ORCAview Technical Reference Manual 340.pdf

Recommend Documents