Database Dynamos for Intellution s 32 Bit FIX Owner s Manual A6V10324337 Us En

System 600 APOGEEDatabase Dynamosfor Intellution's 32-Bit FIXOwner’s Manual125-2161 Rev. 3, 9/00

Rev. 3, September, 2000

NOTICE

This document contains information proprietary to Siemens Building Technologies, Inc. (“Siemens” ). Any reproductionor disclosure of this information to unauthorized persons is prohibited, except as is allowed by prior written permission ofSiemens.

Every effort has been made to ensure that the contents of this manual are accurate. Siemens reserves the right tochange the specifications in this manual without notice. Siemens assumes no responsibility for maintaining or upgradingthe contents of this document. THE INFORMATION IN THIS MANUAL IS PRESENTED FOR INFORMATION PURPOSESONLY. IT IS NOT A CONTRACTUAL COMMITMENT OR A MODIFICATION OF ANY CONTRACT THAT MAY EXISTBETWEEN US. THIS INFORMATION IS SUBJECT TO CHANGE WITHOUT NOTICE, AND IS PRESENTED AS IS.

All software described in this document is furnished under a license and may be used or copied only inaccordance with the terms of such license.

SERVICE STATEMENT

Control devices are combined to make a system. Each control device is mechanical in nature and allmechanical components must be regularly serviced to optimize their operation. All Siemens BuildingTechnologies, Inc. branch offices and authorized distributors offer Technical Support Programs that willensure your continuous, trouble-free system performance.

For further information, contact your nearest Siemens Building Technologies, Inc. representative.

Copyright 2000 by Siemens Building Technologies, Inc.

TO THE READER

Your feedback is important to us. If you have comments about this manual, please submit them [email protected]

APOGEE is a trademark of Siemens Building Technologies, Inc.

Microsoft is a registered trademark, Windows and Windows NT are registered trademarks of MicrosoftCorporation.Intellution and THE FIX are registered trademarks of Intellutions, Inc.FIX MMI Dynamo Object are trademarks of Intellution, Inc.DigiBoard is a registered trademark of Digi International, Inc.Company and product names mentioned in this manual are trademarks or registered trademarks of theirrespective companies.

All Rights Reserved. No part of this manual may be reproduced, in any form or by any means, without permission inwriting from Siemens.

Printed in U.S.A.

Table of Contents

Introduction ...................................................................................................................1-1

Relationship between FIX and System 600 APOGEE ...........................................1-1

System Components ...............................................................................................1-2

DigiBoard Serial Card ...........................................................................................1-2

LocalNet Device ...................................................................................................1-2

AsyncSvc Service..................................................................................................1-2

MsgManager Service ...........................................................................................1-3

Setting Up the Hardware..............................................................................................2-1

Setting up the Workstation .....................................................................................2-1

Minimum FIX hardware requirements.................................................................2-1

Software Key ............................................................................................................2-2

Operating System....................................................................................................2-2

DigiBoard..................................................................................................................2-2

Cabling.....................................................................................................................2-2

Installing the Software Module....................................................................................3-1

Prerequisites...........................................................................................................3-1

Installing the System 600 APOGEE Database Dynamos .....................................3-2

Configuration...........................................................................................................3-3

Updating DDB Spreadsheet...................................................................................3-4

Uninstalling the Database Dynamos.....................................................................3-6

System 600 APOGEE Blocks .........................................................................................4-1

Overview ..................................................................................................................4-1

Point Type Definitions ..............................................................................................4-2

Logical Analog Input (LAI)......................................................................................4-3

Field Descriptions ..................................................................................................4-3

Logical Analog Output (LAO)................................................................................4-11

Logical Digital Input (LDI) .......................................................................................4-12

Logical Digital Output (LDO)..................................................................................4-13

Logical Fast/Slow/Stop Latched (LFSSL) ...............................................................4-14

Logical Fast/Slow/Stop Pulsed (LFSSP) ..................................................................4-15

Logical On/Off/Auto Latched (LOOAL) ...............................................................4-16

Logical On/Off/Auto-Pulsed (LOOAP) ..................................................................4-17

Logical Two State Latched (L2SL)..........................................................................4-18

Logical Two State Pulsed (L2SP).............................................................................4-19

Logical Pulsed Accumulator Input (LPACI) ..........................................................4-20

Summary of Field Characteristics ..........................................................................4-21

Conversion Utility ..........................................................................................................5-1

Installing the CNVT_FIX Utility ..................................................................................5-1

Overview of the Conversion Utility ........................................................................5-1

Converting from FIX32 GDB to CSV.......................................................................5-2

Converting from CSV to FIX32 GDB.......................................................................5-3

CSV File Structure.....................................................................................................5-4

Microsoft Excel Spreadsheet Example ...............................................................5-4

CSV Text File Example...........................................................................................5-4

Inserting Comments..............................................................................................5-5

Field Data Requirements .....................................................................................5-5

Verifying CSV File Content .....................................................................................5-6

Specifying an Alternate CSV or GDB File Name..................................................5-7

Logging Conversion Output...................................................................................5-7

Troubleshooting .......................................................................................................5-7

Adding Points to the View Application ......................................................................6-1

Adding a Data Link to a Picture ............................................................................6-1

Adding a Block to the Database ..........................................................................6-4

Point Attribute Field Descriptions ...........................................................................6-5

Point Characteristic Field Descriptions..................................................................6-7

Point Command Field Descriptions .......................................................................6-8

Point Status Field Descriptions................................................................................6-9

Data Link Design Considerations...........................................................................6-10

Viewing the Data Links ...........................................................................................6-14

Troubleshooting ............................................................................................................7-1

System Components ...............................................................................................7-1

Database Dynamos .............................................................................................7-1

DigiBoard Serial Card ...........................................................................................7-1

Table of Contents

v

LocalNet Driver......................................................................................................7-2

AsyncSvc Service..................................................................................................7-2

MsgManager Service ...........................................................................................7-2

Run Time Information ..............................................................................................7-2

Common Problems .................................................................................................7-2

Using the NT Event Viewer ......................................................................................7-3

Using the Alarm History Window ............................................................................7-4

MsgManager Service Messages .........................................................................7-5

Fix32 Application Messages.................................................................................7-5

Registry Entries..........................................................................................................7-8

DbSizeInMbytes .....................................................................................................7-8

MessagePoolSize...................................................................................................7-8

OnlineWaitInSec ...................................................................................................7-8

ReloadWaitInSec ..................................................................................................7-8

Siemens Building Technologies, Inc. IStaefa Product Group

How to Use This Manual

The System 600 APOGEE Database Dynamos for Intellution® 32-Bit FIX® for Windows NT®,hereafter referred to as the Database Dynamos, provides communication between FullyIntegrated Control System (FIX) automation software and System 600 APOGEE networks.

This manual provides information for installing and configuring the Database Dynamos. It iswritten primarily for the following audience:

• integrators

• design engineers

• project managers

• system specialists

The manual contains the following chapters:

• Chapter 1, Introduction, discusses the relationship between FIX and System 600APOGEE.

• Chapter 2, Setting up the Hardware, describes the hardware configuration issues thataffect the operation of the Database Dynamos.

• Chapter 3, Installing the Software Module describes installing the System 600APOGEE Database Dynamos software.

• Chapter 4, System 600 APOGEE Blocks explains adding System 600 APOGEEpoints to the FIX database.

• Chapter 5, Conversion Utility discusses converting System 600 APOGEE pointinformation into a FIX32 import file.

• Chapter 6, Adding Points to the View Application describes how to add data links tographically monitor and command System 600 APOGEE points on a View Screen.

• Chapter 7, Troubleshooting, describes how to troubleshoot communication problemsbetween the FIX workstation and the System 600 APOGEE Building Level Network(BLN).

System 600 APOGEE Database Dynamos for Intellution's 32-Bit FIX Owner's Manual

II Siemens Building Technologies, Inc.Staefa Product Group

Manual Conventions

The following table lists conventions to help you use this manual in a quick and efficientmanner.

Convention Example

Numbered Lists(1,2,3…) indicate aprocedure withsequential steps.

1. Turn OFF power to the computer. Turn ON power to the computer.

2. Check to see that LEDs on memory board are lit.

Actions that youshould perform arespecified in boldfacefont.

Click OK to save changes and close the dialog box.

Manual Symbols

The following table lists the symbols used in this manual to draw your attention to importantinformation.

Notation Symbol Meaning

WARNING Indicates that personal injury or loss of life may occur to theuser if a procedure is not performed as specified.

CAUTION Indicates that equipment damage or loss of data may occur ifthe user does not follow a procedure as specified.

Related Documents

The FIX software includes a complete set of online help manuals, also known as ElectronicBooks. The following online help manuals are referenced in this Database Dynamos manual.

• How To Use FIX Electronic Books

• Introduction to FIX Software

• Basics Manual

• Environmental Setup Manual

• System Configuration Manual

• Database Builder Manual

• Database Reference Manual

• Alarming & Messaging Manual

How to Use This Manual

Siemens Building Technologies, Inc. IIIStaefa Product Group

• Security Manual

• Draw Manual

• Historical Trending Manual

• View Manual

Accessing the FIX Electronic Books

The FIX Electronic Books can be accessed using one of the following methods:

• From Windows NT, click Start, Programs, Intellution FIX, and then FIX ElectronicBooks.

• While working anywhere within the FIX program, click Help from the main menu andthen click FIX Electronic Books.

Where To Send Comments

Your feedback is important to us. If you have comments about this manual, please submitthem to [email protected].


IV Siemens Building Technologies, Inc.Staefa Product Group

Siemens Building Technologies, Inc. 1-1

1Introduction

The Database Dynamos provides communication between Fully Integrated Control System(FIX) automation software and System 600 APOGEE networks. The Database Dynamosoperate with 32-bit FIX software v6.15. The Database Dynamos is not included with FIX andmust be purchased separately from Siemens Building Technologies, Inc.

Chapter 1 discusses the following topics:

• Relationship between FIX and System 600 APOGEE

• System Components

Relationship between FIX and System 600 APOGEE

The FIX workstation is a node on the System 600 APOGEE Building Level Network. TheSystem 600 APOGEE point names, entered as tags in the FIX database, define the linksbetween the two systems.

Once all the point “links” are established, the FIX workstation receives only the data from theSystem 600 APOGEE points that have been reported to have changed by more than theirrespective significant Changes of Value (COVs). Significant COVs are defined within eachpoint definition in the System 600 APOGEE database.

The most critical factor contributing to the efficiency of the data exchange between the twosystems is the amount of COV traffic on the System 600 APOGEE network. Proper systemmanagement by the user can contribute significantly to increased efficiency incommunications performance. You may want to consider the following suggestions whendesigning a FIX database with a large number of points:

• COV values for the System 600 APOGEE points should be practical; for example, themaximum allowed by the control applications.

• In order to limit requests for dynamic points in the System 600 APOGEE, avoidrequesting the redundant data associated with point values that may be derived frommultiple points. For example, Cubic Feet per Minute (CFM) values for the air volumeare typically determined from air velocity sensor readings. If the COV traffic efficiencyis important, the data for only one of the points should be requested by the DatabaseDynamos.


1-2 Siemens Building Technologies, Inc.

• The System 600 APOGEE is a distributed control system. Therefore, the overallcontrol algorithms should be distributed. Calculations, monitoring, and controlapplications should be performed at the field panels, as much as possible, since thenecessary data is most readily available. For example, when monitoring the status ofa chiller, it may be beneficial to define virtual points and change their values via theresident Powers Process Control Language (PPCL) application only when theundesired condition occurs. This is done instead of reporting all the current chillersensor values on the network. The FIX database could then include the virtual pointssince they are not updated as often as the diagnostic points associated with them.

System Components

System 600 APOGEE Database Dynamos (loadable blocks) are similar to PLC “register”block types (e.g., AR, DR) in the sense that field updates to or from the System 600APOGEE network points are communicated immediately, rather than waiting for Scan, Alarm,and Control (SAC) to scan the blocks. In addition, System 600 APOGEE blocks are primaryblocks that can serve to schedule “chains” of block operations.

Communication between the blocks and System 600 APOGEE equipment takes placethrough three additional layers of software components (MsgManager service, AsyncSvcservice and LocalNet driver) and a DigiBoard serial card.

DigiBoard Serial Card

The DigiBoard is a multi-port serial communications adapter. It provides dedicated hardwareassistance for low level System 600 APOGEE network functions, thereby processingdemands on the operator workstation.

LocalNet Device

The LocalNet Device is the lowest layer of the software components. LocalNet is a WindowsNT device driver, providing the communications engine for driving the DigiBoard serial card.

AsyncSvc Service

The AsyncSvc Service software sits above the LocalNet Device software and provides aunified method for sharing System 600 APOGEE messaging resources. The AsyncSvc actsas a clearing-house, allowing multiple clients to receive information from it without creatingexcessive System 600 APOGEE network traffic.

Introduction


MsgManager Service

MsgManager Service is the next level of the software layers and provides the capability forSystem 600 APOGEE blocks to exchange messages with the AsyncSvc service process.This service is added to the Windows NT service list during installation of the DatabaseDynamos software.

FIX32 applications and the MsgManager service share run-time System 600 APOGEE blockinformation using event message queues and a shared database file, PROXY.{A5BF7110-F9F7-11CF-96F0-00AA00597DC2}. (The file extension is a COM GUID indication of theobject type.) A companion file, PROXY.LOG contains detailed error logging information aboutdatabase operations that is not normally logged to the FIX Alarm History File. Additionaldetailed logging information about the operation of MsgManager service is contained in thefile MSG.LOG.




2Setting Up the Hardware

Chapter 2 discusses hardware configuration issues that affect the operation of the DatabaseDynamos.


• Setting up the Workstation

• Minimum FIX hardware requirements

• Software Key

• Operating System

• DigiBoard

• Cabling

Setting up the Workstation

Refer to the Intellution Environment Setup Manual for more detail on hardware and operatingsystem setup.

Minimum FIX hardware requirements• IBM 80486DX or Pentium-based computer.

• 32 MB RAM for SCADA nodes and 24 MB RAM for View modes. Siemens BuildingTechnologies, Inc. recommends 64 MB RAM for SCADA nodes of 1000 or moreSystem 600 APOGEE points.

• 80 MB of free hard drive space for a typical FIX system (for example, pictures,databases, and alarm files) plus an additional 30 MB for the System 600 APOGEEDatabase Dynamos software.

• CD-ROM drive.

• NETBIOS-compatible or TCP/IP-compatible network interface adapter (not requiredfor stand-alone nodes).

• VGA or SVGA color graphics monitor and 100% IBM-compatible adapter.



• Two-button mouse or compatible pointing device.

Software Key

A software key is required to run FIX. Refer to the Intellution Environmental Setup Manual forinformation regarding the software key and procedures for installing the key.

An additional software key is provided for the System 600 APOGEE Database Dynamos.This software key must be piggy-backed on the FIX software key.

Operating System

Windows NT 4.0 is required by the Database Dynamos. The Intellution Environmental SetupManual provides information required in order to change the operating system’s configurationfor FIX.

DigiBoard

A Digi Xe intelligent asynchronous serial communication board is required in order for the FIXworkstation to access the System 600 APOGEE field panels. This DigiBoard (Xe board) issupplied with the System 600 APOGEE Database Dynamos.

Set the DIP switches for I/O address 200h as follows: 1=ON, 2=OFF, 3=OFF, 4=ON. This is adown, up, up, down orientation for the switches.

Use the following steps to install the Xe board. For more detailed information, refer to theInstallation Guide included in the Digi Xe box.

1. Turn off the computer’s power and remove the cover.

2. Locate an available 16-bit slot in the computer and remove the slot plate.

3. Plug the Xe board into the slot and screw the endplate to the computer chassis.

4. Replace the computer’s cover.

Cabling

Figure 2-1 illustrates the basic wiring hookup between the P2 Controller and the FIXworkstation, along with cable lengths and cable connector configurations.

Figure 2-2 illustrates the wiring requirements for connecting the 9-pin PC/Xe board channelone port at the FIX work station to the Trunk Interface II (TI-II) module. The maximum cablelength allowed (RS-232 type) is 50 feet (15.24 meters). The cable provided with the system is6 feet (1.83 meters) long.

Setting Up the Hardware


Figure 2-3 illustrates the RS-485 hookup between the Trunk Interface II module and the P2Controller BLN port connector.

P2 Controller TI II Fix Workstation

RS-485 1000' (350m) MAX.

RS-232 50' (350m) MAX.

25DB(m) to 9DB(I) Connectors on CableG

W05

83R

1

Figure 2-1. Interconnect Block Diagram.

RED

BLACKSCREW

HEADS FACE DOWN

SCREW EADS FACE

UP

TI-II CONNECTION

P2 CONTROLLER BLN PORT

CONNECTION

CLEAR

RS-485 CABLE

GW

0584

R1

+

-

s

+

-

s

Figure 2-2. RS-232 Hookup.



TI-IIFIX

WORK- STATION

4 DTR

DTR 4

2 RXD

RXD 2 3 TXD

TXD 3 1 DCD

DCD 1

25-PIN MALE

CONNECTOR

9-PIN FEMALE

CONNECTOR

6 DSR

DSR 6

5 GNDGND 5

7 RTSRTS 7

8 CTSCTS 8

MALE

RS-232 CABLE

FEMALEGW

0585

R1

Figure 2-3. RS-485 Hookup.


3Installing the Software Module

The System 600 APOGEE Database Dynamos software is installed using the System 600Database Dynamos for Intellution FIX32 CD-ROM.


• Prerequisites

• Installing the System 600 APOGEE Database Dynamos

• Configuration

• Updating DDB Spreadsheet

• Uninstalling the Database Dynamos

Prerequisites

Before installation begins, the following must be accomplished:

• NT 4.0 operating system and Intellution FIX software have been loaded on theworkstation

• DigiBoard Xe has been installed on the FIX workstation

• System 600 APOGEE points have been configured in their System 600 APOGEEfield panels

• Any existing FIX32 databases have been exported

• Any previous System 600 APOGEE Database Dynamos installations have beenuninstalled

• FIX32 system has been shut down

• You are logged on to the workstation with administrator level privileges



Installing the System 600 APOGEE DatabaseDynamos

To install the System 600 APOGEE Database Dynamos, proceed as follows:

1. Log onto Windows NT as an administrator or as a user in the Administrator group. Theuser should be a domain administrator for that particular NT machine. Make sure that theuser does not have any other conflicting user rights.

2. Insert the System 600 Database Dynamos for Intellution FIX32 CD-ROM into the CD-ROM drive (for example, the “D” drive).

• If the installation program starts automatically, proceed to Step 5.

• If installation does not start, proceed to Step 3.

3. From the Microsoft Windows NT Toolbar, click Start, and then Run.

4. Type D:\setup.exe (where “D” represents the CD-ROM drive letter). Proceed to Step 5.

5. The System 600 APOGEE Database Dynamos Installation Setup screen appears. Theself-explanatory screen messages lead you through the following steps:

• Choose the destination location for the Database Dynamos. The default is C:\FIX32.

• Enter the maximum number of FIX 32 Blocks. This number is used to allocate RAMand hard drive resources for the blocks (2k of each per block). Accuracy is importantbecause overestimating could result in installation failure due to lack of memory.

• Enter the System 600 APOGEE network node number of the workstation.

• Enter the System 600 APOGEE network communication rate in bps.

• Enter a Program Folder name for the Database Dynamos. The default is S600 DBDynamos v1.X.

6. The install program will ask if you would like to configure the new block types. Click Yesto choose the System 600 APOGEE block types you will need for the FIX application.

7. When the Intellution Database Dynamo Configurator dialog appears, click ADD ALL tohave access to Database Dynamo Blocks for all eleven System 600 APOGEE pointtypes. If not all blocks are needed, you may choose only the ones applicable to theapplication.

Installing the Software Module


Table 1-1 lists the optional files, relative to the point types that must be supported.

Table 1-1. Optional Files.

Block System 600 APOGEE Point Type

btk_L2L.dll L2SL Point Type

btk_L2P.dll L2SP Point Type

btk_LAI.dll LAI Point Type

btk_LAO.dll LAO Point Type

btk_LDI.dll LDI Point Type

btk_LDO.dll LDO Point Type

btk_LFL.dll LFSSL Point Type

btk_LFP.dll LFSSP Point Type

btk_LOL.dll LOOAL Point Type

btk_LOP.dll LOOAP Point Type

btk_LPA.dll LPACI Point Type

After installation, run the Intellution Database Dynamo Configurator utility BTKCFG.EXEto add or remove Database Dynamo Block types. BTKCFG.EXE is normally located inthe Fix32 root directory (C:\Fix32\ BtkCfg.exe ). Export any existing FIX32 databasesbefore running BTKCFG.EXE.

8. From the File menu, click Save.

9. Reboot the system when prompted before continuing.

Configuration

After the system starts, configure the new LocalNet device and Async Server as follows:

1. From the Microsoft Windows NT Toolbar, click Start, and then click Programs.

2. From the S600 DB Dynamos v1.X Program Folder, select LocalNet ConfigurationUtility.

3. Select Locate if the utility does not automatically start to find the Digiboard.

4. The Utility will search for the Digiboard and display the following message, LocalNetis properly configured with 1 Digiboard. To close this utility, click the Closebutton.

5. From the Microsoft Windows NT Toolbar, click Start, Settings, Control Panel, and thenServices.

6. Confirm that the service AsyncSvc is Started and Automatic.



7. Select the service MsgManager.

8. Select Startup. The Startup dialog box appears.

9. Select Automatic.

10. Click OK.

11. Click Close.

12. Reboot the system before continuing.

Updating DDB Spreadsheet

The following procedure adds the System 600 APOGEE Tag Fields to the FIX DatabaseBuilder spreadsheet columns list. All System 600 APOGEE column names begin with“600…”.

1. Make a backup of the file DBBFLD.CFG from the FIX installation directory.

2. Open DBBFLD.CFG with a text editor.

3. Append the entire contents of the DBBFLD.UPDATE file (located in the same directory)to the end of DBBFLD.CFG.

4. At the top of the DBBFLD.CFG file, increase the field count by 16 (the number of fieldsadded). This field count appears after the comment lines (lines beginning with a “!”) andis indicated by a number. It is good practice to add another comment line indicating thatthe new columns were added to this file.

Example: ! Added 16 System 600 Logical Point Types on 6/7/97

5. Click Save and close this file.

Installing the Software Module


Figure 3-1. DBBFLD.CFG Screen Part 1.

Figure 3-2. DBBFLD.CFG Screen Part 2.



Uninstalling the Database Dynamos

An uninstall utility is included for the System 600 APOGEE Database Dynamos application.

Before uninstalling the Database Dynamos, do the following:

1. Back up any existing FIX32 databases using FIX’s database export utility. This is a goodpractice to eliminate the potential of corrupting the database. There is also no guaranteethat upgraded software will work properly on a FIX database unless it is new or imported.

2. Stop FIX.

To uninstall the application, perform the following:

1. From the Microsoft Windows NT Toolbar, click Start, and then Programs.

2. Click S600 DB Dynamos v1.X.

3. Click Uninstall S600 DB Dynamos.

4. Follow the menu prompts.

5. Delete the S600 DB Dynamos v1.X Program Folder including program shortcuts.

6. Run the BTKCFG.EXE utility located in the FIX32 directory to remove the System 600APOGEE Database Dynamo Blocks from the current FIX configuration.


4System 600 APOGEE Blocks

Chapter 4 explains adding System 600 APOGEE points in a FIX database.

This chapter discusses the following topics:

• Overview

• Point Type Definitions

OverviewThere are two ways to enter System 600 APOGEE points in a FIX Database.

• Use the System 600 APOGEE - Intellution 32-Bit FIX Conversion Utility described inChapter 5. This conversion utility is useful for automating the entry of a large numberof points.

• Use the System 600 APOGEE block dialog boxes, similar to the generic block dialogboxes used while editing a FIX database. There are eleven System 600 APOGEEblock dialog boxes used to configure database blocks for eleven of the System 600APOGEE point types. Table 4-1 lists the eleven System 600 APOGEE points thatcan be directly configured on a FIX node.

Table 4-1. System 600 APOGEE Points Supported by FIX.

Point Type Description Database Dynamo

LAI Logical Analog Input btk_lai.dll

LAO Logical Analog Output btk_lao.dll

LDI Logical Digital Input btk_ldi.dll

LDO Logical Digital Output btk_ldo.dll

L2SL Logical Two State Latched btk_l2l.dll

L2SP Logical Two State Pulsed btk_l2p.dll

LFSSL Logical Fast/Slow/Stop Latched btk_lfl.dll

LFSSP Logical Fast/Slow/Stop Pulsed btk_lfp.dll

LOOAL Logical On/Off/Auto latched btk_lol.dll

LOOAP Logical On/Off/Auto Pulsed btk_lop.dll

LPACI Logical Pulsed Accumulator Input btk_lpa.dll



Run the Intellution Database Dynamo Configurator utility BTKCFG.EXE to add or removesupported Database Dynamo Block types. Export any existing FIX32 databases beforerunning this utility.

NOTE: The Logical Controller (LCTLR) point type is not supported by the DatabaseDynamos.

Point Type DefinitionsThe following System 600 APOGEE point types are supported by FIX:

• Logical Analog Input (LAI) - Monitors the value of an analog input point (e.g.,temperature, flow, pressure).

• Logical Analog Output (LAO) - Provides one commandable analog output point(e.g., position valves and dampers).

• Logical Digital Input (LDI) - Monitors the state of digital input points (e.g., fans andlighting).

• Logical Digital Output (LDO) - Provides one commandable digital state (used tocommand two-position ON/OFF devices such as fans and lighting).

• Logical Two-State Latched (L2SL) - Provides one commandable latched digitaloutput (ON/OFF) and monitors one digital input for proof.

• Logical Two-State Pulsed (L2SP) - Provides two commandable pulsed digitaloutputs (ON/OFF) and monitors one latched digital input as a proof point.

• Logical FAST/SLOW/STOP Latched (LFSSL) - Provides commandable latcheddigital outputs (FAST/SLOW/STOP) and one optional digital input as a proof.

• Logical FAST/SLOW/STOP Pulsed (LFSSP) - Provides three commandable pulseddigital outputs (FAST/SLOW/STOP) and one optional digital input used as a proof.

• Logical ON/OFF/AUTO Latched (LOOAL) - Provides two commandable latcheddigital outputs and one digital input that can be used as a proof point.

• Logical ON/OFF/AUTO Pulsed (LOOAP) - Provides two commandable latcheddigital outputs (ON/OFF) and one commandable latched output (AUTO). The digitalinput may be used as an optional proof point.

• Logical Pulsed Accumulator (LPACI) - Counts pulses of one digital input point.

System 600 APOGEE Blocks


Logical Analog Input (LAI)Figure 4-1 shows the dialog box used for configuring an LAI point block. An LAI pointmonitors the value of an analog input point (e.g., temperature, flow, pressure). A descriptionof each field follows Figure 4-1.

Figure 4-1. Logical Analog Input Dialog Box.

Field Descriptions

This section describes fields within the System 600 APOGEE point block dialog boxes.

NOTE: The “grayed” fields are read-only in Database Builder screens. After apoint/block connection is made, a “snapshot” of these fields is displayed whenthe screen is opened.

Tag Name

A unique identifier in the FIX Process Database. You can use a maximum of 30 alphanumericcharacters, starting with a letter. No spaces are allowed.

Next Block

Tag Name of the next block in the chain.



Description

Alphanumeric explanation of Tag Name displayed in Alarm Summary, Reports, View. Youcan use a maximum of 40 alphanumeric characters.

NOTE: This is the FIX description, not the System 600 APOGEE point descriptorresident in the System 600 APOGEE field panel.

Start Block on Scan

Scan, Alarm, and Control (SAC) automatically processes all primary blocks that have this boxchecked whenever SAC starts or the database is loaded.

Initial Mode

• Automatic - sends/receives data to/from System 600 APOGEE devices.

• Manual - accepts data from the keyboard, another block, or a command script.

NOTE: This is similar to the System 600 APOGEE concept of points being online oroffline, with online correlating to automatic.

NOTE: Most primary blocks are set as automatic and secondary blocks as manual.

Scan Time

The interval that determines how often the Scan, Alarm, and Control (SAC) programprocesses a block in the process database (PDB).

NOTE: System 600 APOGEE Blocks do not depend on the SAC Scan Time forreading and writing block values. This is similar to the function of a FIX PLCregister block.



The System 600 APOGEE blocks have a default of 10 seconds for Scan Time which isappropriate for these blocks when used as stand-alone blocks. If the System 600 APOGEEblocks are used as primary blocks in a chain, the chain will use the Scan Time for theprocessing rate.

There are two types of scan time:

• Table 4-2 shows Time Based scans:

Table 4-2. Time-Based Scan Times.

Increment Range

Subseconds 0.05 –- 0.95

Seconds 1 — 59

Minutes 1M –- 59M

Hours 1H –- 24H

• One-shot processing:

SAC program processes a block only once. The block does not trigger again unless theSAC is restarted, and the database is reloaded. To process a block only once, enter zero(0) in the Scan Time field.

I/O Device

System 600 APOGEE virtual I/O device. No other choice is supported.

Address

• Station – Windows NT workstation name given to the Intellution node containing theFIX database for this block. The name can be verified by pointing to the Start button,and clicking Settings, Control Panel, Network, Identification, and ComputerName.

• Network Trunk – Name or number of the System 600 APOGEE P2 network trunk onwhich the point is located. This field is case sensitive. Refer to the example on thefollowing page.

• Cabinet Number – Number of the System 600 APOGEE field panel where the pointresides.

• Point Name – System 600 APOGEE Point Name.



Example:

PC_1.P2Trunk_0.12.OATEMP

− NT workstation is PC_1

− Point OATEMP is located in cabinet 12 on trunk 0

NOTE: When creating multiple blocks, cut and paste the network address from oneblock to the next to avoid retyping the common portions of the field.

Descriptor

System 600 APOGEE point description as defined in the System 600 APOGEE panel.

Priority

Reflects either a point's current priority (if reading the point attribute) or desired priority (ifwriting the point attribute). Table 4-3 lists the priorities in ascending order, with None beingthe lowest priority and Operator being the highest.

Table 4-3. Point Priorities.

Floating Point Siemens Building Technologies, Inc. Text Meaning

0 None

5 PDL

32 Emergency

34 Smoke

35 Operator

Character

This field displays an overview of the point's characteristics in the following format:

A EA PA TE TH BOI BINC CBE

Where:

A identifies if the point is defined as AlarmableEA identifies if the point is defined for Enhanced AlarmingPA identifies if the point is defined for Printing of AlarmsTE identifies if Totalization for the point is EnabledTH identifies if Totalization is in HoursBOI identifies if the point is defined to have its Binary Output InvertedBINC identifies if the point is defined to have its Binary Input Normally ClosedCBE identifies if the point is defined to have Both Edges counted for totalization

(applies to LPACI point type only)

NOTE: When the above conditions are true, the abbreviations are displayed. Whenthe condition is false, the field is empty.



Present Value

Displays the System 600 APOGEE point’s Current (Present) Value.

Status

Displays the current state of the point in the following format:

F A An C O ODSB PDSB HAND COV

Where:

F indicates the point is failedA indicates the point is in alarmAn indicates an enhanced alarm (n = alarm level)C indicates the point has been commanded into alarmO indicates the point is out of serviceODSB indicates an operator has disabled the alarm printingPDSB indicates a program has disabled the alarm printingHAND indicates a point is in manual overrideCOV indicates the COV link for the point is active

NOTE: When the above conditions are true, the abbreviations are displayed. Whenthe condition is false, the field is empty.

Totalized Value

The current totalized value when the block was opened.

COV Limit

The Change of Value (COV) Limit of the point. COV Limit is the minimum a point’s valuemust change before it is reported. It is also the smallest denomination a point can becommanded to. For example, a point with a COV limit of 1 cannot report changes of 0.2 unitsand cannot be commanded to a decimal value such as 72.5.

Low and High Engineering Limit Fields

FIX requires that the maximum and the minimum values be expressed in engineering unitsfor each point in the database. Table 4-4 provides the information necessary to calculate theminimum and maximum values based on information from the System 600 APOGEE. Inaddition to the formulas, the following information must be known to determine the high andlow limits:

• slope

• intercept

• field panel type where the point resides (MBC or SCU)

• sensor type for which the point is defined (RTD, Thermistor, 0 to 10V, etc.)

The defaults for this field are 0 and 100. These fields MUST be changed according to theformulas shown in Table 4-4.



Table 4-4. Minimum and Maximum Value Fields.

FieldPanel

Point Module Type PointType

Sensor Type Min. Point Value Max. Point Value

MBC Al_E (0–10 Vdc) LAI V (Voltage) =m( 3,584 ) + b =m(29,184) + b

MBC Al_I (4-20 mA) LAI I (Current) =m( 3,584 ) + b = m(29,184) + b

MBC Al_100K ohms LAI T (Thermistor) =-40°F(-17.7°C ) =257°F(125°C)

MBC Al_RTD LAI I (Current) =m(11543) + b =m(18571)+b

MBC AO_E (0–10 Vdc) LAO N/A =b =m (30,720)+b

MBC AO_I (4–20 mA) LAO N/A =b = m(30,720)+b

MBC AO_P (0–20 psi) LAO N/A =b = m(30,720)+b

ALL Virtual LAI/LAO N/A =b = m(32,767)+b

SCU Al_E (0–10 Vdc) LAI V (Voltage) =b =4000m+b

SCU Al_I (4–20ma) LAI I (Current) =b+800m =4000m+b

SCU Al_P LAI T (Thermistor) =b+1120m =2400m+b

SCU AI_100K LAI T (Thermistor) =-40°F(-17.7°C ) =257°F(125°C)

SCU AO_E LAO N/A =b =m(255) + b

SCU AO_I LAO N/A =b =m(255) + b

SCU AO_P LAO N/A =b =m(255) + b

RCU P2 Al_E (0–10 Vdc) LAI V (Voltage) =b + 4200 =m(21000) + b

RCU P2 AO_E LAO N/A =b =m(1023) + b

RCU P2 AO_P LAO N/A =b + 42 =m(255) + b

where:

m = slope value for the point

b = intercept value for the point



Alarms

The following dialog box (Figure 4-3) is accessed by clicking the Alarms and Security buttonon the Logical Analog Input dialog box.

NOTE: These fields help define FIX alarming functionality for particular FIX tags. They donot alter System 600 APOGEE alarming characteristics.

Figure 4-3. Alarm and Security Screen.

• Enable Alarming - Defines whether alarm processing is enabled or disabled.Generates alarm messages indicating that a value has crossed pre-defined limits andrequires a response. Allows other blocks to detect an alarm from the block. An entirechain can be affected when you disable alarms for a block.

• Enable Messaging - provides information about database events, operator inputs, orsystem activities that do not imply potential problems. Records process activity, butdoes not require an acknowledgment. Is sent to the same destinations as alarms fora given block, but messages do not appear in the alarm summary link. Output blocksgenerate messages whenever a value is written. If you check Enable Messaging,you must check both the Enable Alarming and the Event Msg check boxes.



Alarm Areas

Alarm areas are configured within a node’s System Configuration Utility (SCU). Entering theletter of an alarm area (letters A through P) specifies the local and remote nodes to which theblock’s alarms will be sent. Alarm areas also route event messages.

• ALL allows alarms from the block to be received by all enabled alarm destinations.

• NONE specifies that alarms will not be sent to any nodes.

•

Priority

Used for filtering alarms according to severity. If the block’s alarm priority is greater than orequal to the node’s alarm priority, then it is recorded by the node and sent to pre-configuredalarm destinations. If it is less than the node’s priority, it is not sent to other nodes and doesnot appear at any alarm or messaging services.

Alarm Limits

Alarm Limits determine when alarms occur. When the current value extends outside therange of the high and low limits, an alarm is sent to the alarm areas.

For System 600 APOGEE points that are enabled for alarming and NOT enabled forenhanced alarming, the high and low limits defined in the panel are automatically filled in asdefaults in the process database. For points with enhanced alarming enabled, an Alarm Blockmust be used. An Alarm Block and a LAI block are both primary blocks, which require aProgram Block to link them.

Security Areas

Provides write protection for the block. A user must have access to the security area tochange the value of a write-protected block.

• ALL assigns the block to every security area.

• NONE does not assign the block to any security area. If there is no security area, theblock is not write-protected.



Logical Analog Output (LAO)Figure 4-5 shows the dialog box used to configure an LAO point block. An LAO provides onecommandable analog output point (e.g., position valves and dampers).

Figure 4-5. Logical Analog Output Dialog Box.

All of the fields in Figure 4-5, except for the Initial Value field, are the same as thosedescribed for the Logical Analog Input Dialog Box. Refer to the LAI descriptions for moreinformation regarding these fields.

Initial Value

For Intellution programming use. Allows the operator to set the value of a point when it isplaced on scan, e.g., to turn on all fans before a batch is run.

NOTE: This does not affect the initial value set in field panels for LAO points.



Logical Digital Input (LDI)Figure 4-7 shows the dialog box used to configure an LDI point block. An LDI point monitorsthe state of digital input points (e.g., fans and lighting).

Figure 4-7. Logical Digital Input Dialog Box.

The fields in Figure 4-7 are the same as those described for the Logical Analog Input DialogBox. Refer to the LAI descriptions for more information regarding these fields. The onlydifference is that the Engineering Limits field is replaced with Labels field, which isdescribed as follows:

Labels

Can be a label of up to 13 characters displayed when using an ASCII Data Link. System 600APOGEE labels are the default and may be overridden by entering the label of choice.Defaults are in Table 4-6.

Table 4-6. Default labels.

Floating Point ASCII

0.0 OFF

1.0 ON



Logical Digital Output (LDO)Figure 4-9 shows the dialog box used to configure an LDO point block. An LDO pointprovides one commandable digital state (used to command two-position ON/OFF devicessuch as fans and lighting).

Figure 4-9. Logical Digital Output Dialog Box.

All of the fields in Figure 4-9, except for two, are the same as those described for the LogicalAnalog Input Dialog Box. Refer to the LAI descriptions for more information regarding thesefields. The two exceptions are the addition of the Initial Value field, and the replacement ofthe Engineering Limits field with the Labels field.

Initial Value

For Intellution programming use. Allows the operator to set the value of a point when it isplaced on scan (e.g., to turn on all fans before a batch is run). This does not affect the initialvalue set in field panels.

Labels

Can be a label of up to 13 characters displayed when using an ASCII Data Link. System 600APOGEE labels are the default and may be overridden by entering the label of choice.Defaults are listed in Table 4-8.

Table 4-8. Default Labels.


0.0 OFF

1.0 ON



Logical Fast/Slow/Stop Latched (LFSSL)Figure 4-11 shows the dialog box used to configure an LFSSL point block. An LFSSLprovides commandable latched digital outputs (FAST/SLOW/STOP) and one optional digitalinput as a proof.

Figure 4-11. Logical Fast/Slow/Stop Latched Dialog Box.

Most of the fields in Figure 4-11 are the same as those described for the LAI block. Refer tothe LAI descriptions for more information regarding these fields. The two exceptions are theaddition of the Initial Value field, and the replacement of the Engineering Limits field with theLabels field.

Initial Value

For Intellution programming use. Allows the operator to set the value of a point when it isplaced on scan. (For example, to turn on all fans before a batch is run.) This does not affectthe initial value set in field panels.

Labels

Can be a label of up to 13 characters. System 600 APOGEE labels are the default and maybe overridden by entering the label of choice. Defaults are listed in Table 4-10.



0.0 STOP

1.0 SLOW

2.0 FAST



Logical Fast/Slow/Stop Pulsed (LFSSP)Figure 4-13 shows the dialog box used to configure an LFSSP point block. An LFSSPprovides three commandable pulsed digital outputs (FAST/SLOW/STOP) and one optionaldigital input used as a proof.

Figure 4-13. Logical Fast/Slow/Stop Pulsed Dialog Box.


Initial Value


Labels




0.0 STOP

1.0 SLOW

2.0 FAST



Logical On/Off/Auto Latched (LOOAL)Figure 4-15 shows the dialog box used to configure a LOOAL point block. A LOOAL providestwo commandable latched digital outputs and one digital input that can be used as a proofpoint.

Figure 4-15. Dialog Box for an LOOAL Point Block.


Initial Value


Labels




0.0 OFF

1.0 ON

2.0 AUTO



Logical On/Off/Auto-Pulsed (LOOAP)Figure 4-17 shows the dialog box used to configure a LOOAP point block. A LOOAP pointprovides two commandable latched digital outputs (ON/OFF) and one commandable latchedoutput (AUTO). The digital input may be used as an optional proof point.

Figure 4-17. Dialog Box for an LOOAP Point Block.


Initial Value


Labels




0.0 OFF

1.0 ON

2.0 AUTO



Logical Two State Latched (L2SL)Figure 4-19 shows the dialog box used to configure an L2SL point block. An L2SL pointprovides one commandable latched digital output (Logical ON/OFF) and monitors one digitalinput (Logical) for proof.

Figure 4-19. Logical Two State Latched Dialog Box.


Initial Value


Labels




0.0 OFF

1.0 ON



Logical Two State Pulsed (L2SP)Figure 4-21 shows the dialog box used to configure an L2SP point block. An L2SP pointprovides two commandable pulsed digital outputs (Logical ON/OFF) and monitors onelatched digital input (Logical) as a proof point.

Figure 4-21. Logical Two State Pulsed Dialog Box.


Initial Value


Labels




0.0 OFF

1.0 ON



Logical Pulsed Accumulator Input (LPACI)Figure 4-23 shows the dialog box used to configure an LPACI point block. An LPACI pointcounts pulses of one digital input point.

Figure 4-23. Logical Pulsed Accumulator Input Dialog Box.

All of the fields in Table 4-20, except for the Initial Value field, are the same as thosedescribed for the LAI block. Refer to the LAI descriptions for more information regardingthese fields.

Initial Value




Summary of Field CharacteristicsFigure 4-25 is a summary of the information available for each point type. For instructions onviewing this information on a FIX View Screen, refer to Chapter 6, Adding Points to the ViewApplication.

Figure 4-25. Summary of Field Characteristics.




5Conversion Utility

The CNVT_FIX utility provides a means for converting System 600 APOGEE pointinformation into a FIX32 import file (e.g., a GDB file) through the use of a Comma-SeparatedVariable (CSV) file. The utility can also be used to convert a FIX32 import file to a CSV textfile.


• Installing the CNVT_FIX Utility

• Overview of the Conversion Utility

• Converting from FIX32 GDB to CSV

• Converting from CSV to FIX32 GDB

• CSV File Structure

• Verifying CSV File Content

• Specifying an Alternate CSV or GDB File Name

• Logging Conversion Output

• Troubleshooting

Installing the CNVT_FIX Utility

The CNVT_FIX utility is automatically installed in the FIX32 root directory when the System600 APOGEE Database Dynamos for Intellution FIX32 package is installed.

Overview of the Conversion Utility

A single conversion utility, CNVT_FIX.EXE, is used to perform both types of conversion; CSVto FIX32 GDB and FIX32 GDB to CSV. The switch entered on the command line determineswhich conversion will be performed.



Convention:

CNVT_FIX station_name trunk_ID [/g] [/c] [/v] [filename.csv] [filename.gdb]

Mandatory Parameters:

station_name The NT Network name of the computer running FIX32

trunk_ID The P2 trunk number associated with the points in the CSV file being converted

Switch Parameters (select one):

/g Create CSV spreadsheet file from FIX32 GDB import file

/c Create FIX32 GDB import file from CSV spreadsheet file

/v Verify CSV spreadsheet file

Optional Parameters:

filename.csv Override default CSV file name (dbase.csv)

filename.gdb Override default GDB file name (dbase.gdb)

Examples:

• CNVT_FIX NODE1 0 /g

This creates a CSV file (dbase.csv) from a FIX32 import file (dbase.gdb). The stationname is “NODE1” and the points reside on trunk 0.

• CNVT_FIX NODE1 0 /c

This creates a FIX32 GDB import file (dbase.gdb) from a CSV file (dbase.csv).

• CNVT_FIX NODE1 0 /v

This verifies a CSV file (dbase.csv) only. It does not create a GDB file.

• CNVT_FIX NODE1 0 /v MyNewDB.csv

This verifies CSV file MyNewDB.csv only. It does not create a FIX32 GDB file.

Converting from FIX32 GDB to CSV

This option creates a CSV file from a FIX32 GDB import file. Do the following to perform theconversion:

CAUTION:

Any dbase.csv file already present in this directory will be overwritten! Back up anyfiles to be saved before executing CNVT_FIX.EXE.

In a directory that includes both the CNVT_FIX.EXE program and the FIX32 import filedbase.gdb, run the CNVT_FIX program with the /g command line switch.

Conversion Utility


Convention:

CNVT_FIX station_name trunk_ID /g [filename.csv] [filename.gdb]

Example:

CNVT_FIX NODE1 0 /g

The conversion utility will display its version banner. A dbase.csv file will be created from thedbase.gdb import file in the same subdirectory in which the conversion was run.

If the conversion is successful, the following message displays, Conversion CompletedSuccessfully!If the conversion is not successful, the following message displaysConversion NOT Successful! in addition to the reason for the failure.

Converting from CSV to FIX32 GDB

This option creates a FIX32 GDB import file from a CSV file. Do the following to perform theconversion:

1. Create a CSV file to be converted to a FIX32 GDB import file. Name the file dbase.csv orprovide the extra command line parameter to override the default CSV filename. This filecan be generated by doing one of the following:

• The file can be generated by your Siemens Building Technologies, Inc.representative directly from your System 600 APOGEE network utilizing proprietarytools.

• The file can be generated manually using any ASCII text based editor such asEDIT.EXE (Available with DOS version 3.3 or higher). The file must conform to thestructure defined in the CSV File Structure section in this chapter.

2. In the directory that includes both the CNVT_FIX.EXE program and the dbase.csv file,run the CNVT_FIX program with the /c command line switch.

Convention:

CNVT_FIX station_name trunk_ID /c [filename.csv] [filename.gdb]

Example:

CNVT_FIX NODE1 0 /c

The conversion utility will display its version banner. The utility will read the dbase.csv fileand create the dbase.gdb FIX32 GDB import file.

If the conversion is successful, the following message displays, ConversionCompleted Successfully!If the conversion is not successful, the following messagedisplays Conversion NOT Successful!, in addition to the reason for the failure.



3. Import the GDB file into FIX32 using the Import facility of the Database Builder.

CSV File Structure

The following example shows the CSV file structure as it appears when using MicrosoftExcel.

Microsoft Excel Spreadsheet Example

;Point Descriptor Type Address ControllerCCPTR1 CC PMP TRIG1 LDO 00000A08 0CCPTR2 CC PMP TRIG2 LDO 00000A09 0EFN1CO EF1 FAN SSP L2SL 00000P04 0EFN2CO EF2 FAN SSP L2SL 00000P06 0EFN3CO EF3 FAN SSP L2SL 00000P08 0EMALM EMERG. ALARM LDO 00000A11 0EQPALM EQUIP. ALARM LDO 00000A12 0HCPSS HC PUMP ONOF LDO 00000P09 0HUMOUT HUM VLV POUT LAO 00000P15 0HUMPOS HUM VLV POS LAO 00000A27 0

CSV Text File Example

This example shows the same CSV file structure when using any text editor such asMicrosoft DOS editor EDIT. For complete information on entering this information, see theField Data Requirements section.

;Point,Descriptor,Type,Address,Controller

CCPTR1,CC PMP TRIG1,LDO,00000A08,0

CCPTR2,CC PMP TRIG2,LDO,00000A09,0

EFN1CO,EF1 FAN SSP,L2SL,00000P04,0



EMALM,EMERG. ALARM,LDO,00000A11,0

EQPALM,EQUIP. ALARM,LDO,00000A12,0

HCPSS,HC PUMP ONOF,LDO,00000P09,0

HUMOUT,HUM VLV POUT,LAO,00000P15,0

HUMPOS,HUM VLV POS,LAO,00000A27,0

Conversion Utility


Inserting Comments

To put comments in the CSV file, insert a semicolon (;) as the first character in the row orline. All other lines are considered as input data and are validated according to the followingformatting requirements.

CAUTION:

If using the Point Checkout Data Report as input, you must place a semicolon at thebeginning of the first line (the line containing the headings).

Field Data Requirements

The following formatting characteristics are required for each data field using the followingCSV file structure:

;Point,Descriptor,Type,Address,Controller

Comma-separated fields of data lines may be padded with spaces. The maximum line lengthis restricted to 80 characters. Processing is not case sensitive.

Point

The first data field line must contain a System 600 APOGEE point name.

• Maximum length: 30 characters

• Minimum length: 1 character

• Valid characters: A to Z, 0 to 9

Descriptor

The second data field line contains the point’s descriptor. This value will be overwrittendynamically in the FIX32 GDB’s database whenever a change is made to the descriptorfield at the controller. It serves mostly to provide an additional descriptive comment whengenerating the CSV file from the current contents of the FIX32 GDB import file withCNVT_FIX.EXE’S ‘/g’ command line option.



• Valid characters: A to Z, 0 to 9, and spaces



Type

The third data field contains the type of the preceding System 600 APOGEE point.


• Minimum length: 3 characters

• Valid strings:LDI, LDO, LAI, LAO, L2SL, LOOAP, LPACI, L2SP, LOOAL, LFSSL, LFSSP

NOTE: Since LCTLR points are not supported through the FIX32 GDB, theconversion utility skips LCTLR points.

NOTE: Point names must be unique in the System 600. The conversion utility willaccept the first instance of any particular point name and skip anysubsequently duplicated point name.

Address

The fourth data field contains the point's System 600 APOGEE Physical Address. This isan optional field and may be left blank.

Controller

The fifth data field contains the System 600 APOGEE field panel (cabinet) number wherethe point resides



• Valid characters: 0 to 9

Verifying CSV File Content

The following steps will verify the content and syntax of a CSV file:

1. Create a CSV file to be converted to a FIX32 GDB import file as outlined in the previoussection.

2. In the directory that includes both the CNVT_FIX.EXE program and the CSV file, run theCNVT_FIX program with the /v command line switch.

Convention:

CNVT_FIX station_name trunk_ID /v [filename.csv] [filename.gdb]

Conversion Utility


Example:

CNVT_FIX NODE1 0 /v

The conversion utility will display its version banner. The utility will read and verify thedbase.csv file.

If the verification is successful, the following message displays, Number Of UniquePoints Verified = x. Informational and warning messages may also display. Thesemessages start with the text Inform: … or Warning: …. Look for error messages ofthe form Error: …, which indicate that the CSV file is not suitable to generate theFIX32 GDB import file.

Specifying an Alternate CSV or GDB File Name

This option allows you to override the default filenames, dbase.csv and dbase.gdb. Simplytype the new filename(s) at the end of the command line. No backslash character is requiredas with other options previously mentioned. However, the filename suffix (.csv or .gdb) mustbe specified.

Examples:

CNVT_FIX NODE1 0 /c dbase2.csv

CNVT_FIX NODE1 0 /c MyNewDb.gdb

CNVT_FIX NODE1 0 /c dbase2.csv MyNewDb.gdb

Logging Conversion Output

The console output from any conversion is streamed automatically into a file namedcnvt_log.txt. Open this file with a text editor to view the displayed conversion output. Thisinformation can be useful for reference or troubleshooting. Close the file before performing aconversion or the CNVT_FIX program will try to open or create the file. This may cause a filesharing violation, or create incorrect cnvt_log.txt file contents.

Troubleshooting

When the message “Conversion NOT Successful displays, a reason for the failuredisplays.

The following is a list of error messages, and the reason for the error message. An ‘x’represents some arbitrary character. If problems occur which are file-related, check diskintegrity by using scandisk.exe or checkdisk.exe.



Message: Unable To Open filename.gdb

Cause: The import file from FIX32 must be present in same directory asCNVT_FIX.EXE.

Message: Unable To Open filename.csv

Cause: File dbase.csv must be present in same directory as CNVT_FIX.EXE.

Message: Unable To Close File filename.csv

Cause: Probably ran out of disk space.

Message: Unable To Close File filename.gdb


Message: Error Creating Point xxxxxx


Message: Error: Invalid File Name filename.xxx

Cause: Valid filenames must have either a CSV or GDB extension.

Message: Error: Point Name 'xxxxxxxx' Improper Length

Cause: Either nothing was entered for the point name in the appropriate field or the pointname exceeds the maximum length of six characters.

Message: Error: Point Name 'xxxxxx' Contains Illegal Character 'x'

Cause: Legal characters are A to Z and 0 to 9.

Message: Warning: Duplicate Point Name 'xxxxxx'

Cause: System 600 APOGEE point names must be unique. Only the first instance of aparticular point name is used. Subsequent names are ignored.

Message: Error: Unknown Point Type 'xxx'

Cause: Refer to the CSV File Structure section of this document for valid point types.

Message: Inform: LCTLR Point Type Found

Cause: Refer to the CSV File Structure section of this document for valid point types.LCTLR points will not be validated or entered into the FIX32 GDB import file.

Message: Error: Invalid Cabinet Number 'xx’

Cause: Valid cabinet numbers are from 0 to 99. 00 is also valid.

Message: Error: Invalid P2 Trunk Number

Cause: Valid P2 trunk numbers are from 0 to 7. The trunk number must be entered as asingle digit.

Message: Error: Point Descriptor 'xxxxxxxxxxxxxx' Too Long

Cause: Maximum number of characters for a point descriptor is twelve. Characters maybe alphanumeric.

Message: Unable To Write To File filename.csv

Cause: Check for a write protected disk, low disk space, or file attributes of dbase.csvusing attrib.exe.

Message: Unable To Add Point xxxxxx

Conversion Utility


Cause: Check for a write protected disk or low disk space.

Message: Unable To Open File CNVT_LOG.TXT

Cause: An other application has already opened this file and is still using it. Close the filein your text editor and try again since this is probably a file sharing accessviolation. It is possible to have run out of disk space.

Message: Unable To Close File CNVT_LOG.TXT





6Adding Points to the View Application

Chapter 6 describes how to add data links to graphically monitor and command System 600APOGEE points on a View Screen.


• Adding a Data Link to a Picture

• Adding a Block to the Database

• Data Link Design Considerations

• Viewing the Data Links

Adding a Data Link to a Picture

To add a System 600 APOGEE point as a data link to a FIX View Screen:

1. Go to the Intellution FIX program and start the FIX software by clicking the Startup icon.

2. Click the Draw icon to load the Draw program and open a new picture.

3. Do one of the following:

• Select Data Link icon from the Toolbox.

• From the Tools menu, click Link and then Data Link.

4. The Data Link button appears on the screen. Position the button anywhere on the screenand click the left mouse button once. The Data Link dialog box, similar toFigure 6-1, appears.



Figure 6-1. Data Link Dialog Box.

Field Descriptions

Tagname

The Tagname field represents the tag that displays on the View Application. Either enter thepoint name (example: IBS_PC2.P2Trunk_0.0.LAI) in the Tagname field and press ENTER orclick ? for a list of points. Clicking the question mark (?) displays the Field Select window(Figure 6-2).

Figure 6-2 shows Node Selection, Tag Selection and Field Selection windows. Select thenode, tag, and field to be represented by the data link and click OK. If the desired tag is notlisted, click the Add button and follow the directions in the Adding a Block to the Databasesection.

Figure 6-2, and Figure 6-3 represent the Field Select windows for the A and F filter types. A_*fields are ASCII or alphanumeric. F_* fields are floating point format data. Fields specific toSystem 600 APOGEE points are described later in this chapter.

Adding Points to the View Application


Figure 6-2. Field Select Window – "A" Type.

Figure 6-3. Field Select Window – "F" Type.



Dynamic Coloring

The value displayed by the Data Link can change color according to value or alarm conditionof the database field. Dynamic foreground coloring has been built directly into the Data Link.Data Link can also have a background color different from the picture background color. Forcomplete instructions on coloring, refer to the Intellution Draw Manual.

Data Entry

To allow data entry into the link by the operators, check the Allow Data Entry box. TheChoose Data Entry Method dialog box appears. In this dialog box, select the type of dataentry you want the operation to perform. Refer to the Intellution Draw Manual for completedetails regarding data entry formats.

Format

Select the type of data being entered and the justification format desired.

Adding a Block to the Database

This section describes how to add a new block for use with the Data Link.

1. If the tag does not exist in the Intellution database, click Add from the Field Selectwindow. The Select a Type dialog box appears allowing the operator to select and addthe database block to the database. This list includes the eleven System 600 APOGEEpoint types.

2. Select the desired Tag type (e.g., Logical Analog Input [LAI]) and click OK. A dialog box,similar to Figure 6-4, appears.



Figure 6-4. Analog Input Block Dialog Box.

3. Enter information in the required Tag name and Address fields. Refer to Chapter 4,System 600 APOGEE Blocks for more information on System 600 APOGEE Blocks.

4. Click OK to save this configuration and exit this menu.

Point Attribute Field Descriptions

This section provides a detailed description of each attribute field. Most of these dynamicattributes are input and output fields. The abbreviation in parenthesis indicates thenomenclature used on the Field Select window.

Address (ADDRESS)

This field displays the address entered for the FIX Block to link the FIX Database with theappropriate System 600 APOGEE point.

• Alarm Level (ALARM_LVL)

When a point is in an alarm state, the Alarm Level field indicates the severity of thealarm. Points defined using the System 600 APOGEE Enhanced Alarming Feature willhave an Alarm Level value (1 to 6) correlating with the operator-defined priority of thealarm. If a point is commanded into alarm, or if the point is defined without selecting theEnhanced Alarming feature, this field will indicate 0x00. When a point’s Point Status fieldindicates that its alarm state is inactive, the Alarm Level field is meaningless. This field isalso meaningless if the point is not defined as being “Alarmable”. Comments arerepresentative of status conditions displayed by a System 600 APOGEE MMI point logreport.



• COV Limit (COV_LIMIT)

The Change Of Value (COV) Limit is the resolution in engineering units at which ananalog point value is reported over the network. This value is also used to establish adead band around high and low alarm limits for non-enhanced alarmable points. TheCOV Limit data type is REAL.

• Current Value (CV)

This field represents a System 600 APOGEE point’s Current Value. The data type isREAL. For some of the point types, these values have a corresponding textualrepresentation which better describes their state to the user. The textual representation iswhat the user views. The REAL representation is what is used for calculations involvingthe block.

• High Alarm Limit (HI_ALARM)

The Alarm Limit fields are only meaningful for System 600 APOGEE points defined asAlarmable and defined without selecting the Enhanced Alarming Feature. The data typeis REAL and is expressed in the same engineering units as the point’s Present Value.

• Initial Value (IV)

The Initial Value is for FIX programming use. It allows the operator to set the value of atag when it is placed on scan. For example, turn the fans on before a batch is run. Thisdoes not effect the initial value set in the field panels.

• Low Alarm Limit (LO_ALARM)

The Alarm Limit fields are only meaningful for System 600 APOGEE points defined asAlarmable and defined without selecting the Enhanced Alarming Feature. The data is oftype REAL and is expressed in the same engineering units as the point’s Present Value.

• Point Priority (PRIORITY)

This field reflects either a point's current priority (if reading the point attribute) or desiredpriority (if writing the point attribute). The priorities are listed here in ascending order,NONE being the lowest priority and Operator being the highest.

POINT PRIORITY

None

PDL

Emergency

Smoke

Operator



• Print Alarms (PRT_ALARMS)

This indicates that alarms generated by this particular point have been sent to alldesignated alarm printer stations on the System 600 APOGEE network.

• Totalized Value (TOTAL)

This field represents a point's present totalized value and the data type is REAL. Pointsare totalized to keep track of such things as the total run time of a piece of equipment,and the total volume from a flow rate sensor. This value is only meaningful for points thathave been enabled for totalization.

Point Characteristic Field Descriptions

This section provides a detailed description of each point characteristic field. These staticcharacteristics are defined in the System 600 APOGEE Field Panel during setup and cannotbe changed from FIX. The abbreviation in parenthesis indicates the nomenclature used onthe Field Select dialog box.

• Characteristics (CHARACTER)

This field is a textual summary of all the defined characteristics of a point.

• Alarmable (ALARMABLE)

This indicates that the point is defined as being alarmable. The System 600 APOGEEfield panel performs checking to determine whether or not the point is in the alarm statewhenever the point changes value.

• Binary Output Inverted (BOUT_INVERT)

Indicates the point was defined to have its logical output to be inverted. This reverses theenergize and de-energize commands for a digital output point meaningless for all pointtypes except LDO.

• Binary Input Normally Closed (BIN_CLOSED)

Indicates a digital point’s input was defined to interface to a normally closed source. (forexample, energized - contacts closed, de-energized - contacts open).

• Count Both Edges (BOTH_EDGES)

Indicates whether the point is defined for totalization to count both the on/off and off/ontransition.



• Descriptor (DESCRIPTIOR)

All System 600 APOGEE logical points allow the assignment of a point descriptor. Thisdescriptor is an ASCII string of twelve alphanumeric characters (blank spaces areallowed). It is used to provide additional information to an operator when displayingpoints. Descriptors are not used by either the system or operator to call up displays or tocommand points. Therefore, there is no need for them to be unique and they may be null(all characters 0x00). Unused characters must be padded with null terminators (0x00).

• Engineering Units (ETAG)

The Engineering Units field defines the engineering units associated with the presentvalue of analog and pulse accumulator points (for example, " DEG F" or "KWH"). Thefield is composed of a text string. The string is used for reference purposes, and it has noeffect on numerical representation or calculation of any point property. The string neednot be unique. Unused characters must be padded with null terminators (0x00). The unitsfield may also contain a null string.

• Enhanced Alarms (ENH_ALARM)

This indicates that the point was defined to support the System 600 APOGEE EnhancedAlarming feature.

• Totalize (TOTAL_ENB)

This indicates that the point was defined as enabled for Totalization. Totalized data ismaintained locally at the point’s local System 600 APOGEE controller.

• Totalize in Hours (TOTAL_HOURS)

This indicates that the point’s Totalization Interval is defined as hourly; otherwise, everyfive minutes. If Totalization is not enabled for this point, this indication is meaningless.

Point Command Field Descriptions

The following fields can be commanded for a point.

• Print (PRINT)

This is a toggle switch that allows an operator to enable and disable alarm printing for apoint. If a light button is chosen for this representation, the current state will be indicated.

• Service (SERVICE)

This toggle switch allows an operator to put a point into and out of service. Again, if alight button is used the current state will be indicated.

• Normal (NORMAL)

This toggle allows an operator to put a point into alarm or into a normal state. A lightbutton will indicate current status.



• Get Totalized Value (TOTALIZE)

This button allows an operator to retrieve the current totalized value for a point.

Point Status Field Descriptions

The following fields are used for monitoring purposes to display the status of a point. Theabbreviation in parenthesis indicates the nomenclature used on the Field Select dialog box.

• Status (STATUS)

This field is a textual summary of the point’s current state.

• Commanded Into Alarm (CMD_ALARM)

Point has been commanded into alarm by a user.

• COV Link Active (COV_LINK)

COV Reporting is currently enabled for the point.

• Failed (FAILED)

Point is currently failed.

• In Alarm (IN_ALARM)

Point is currently in alarm.

• Manual Override (MAN_OVER)

Point module is a manual override module and is currently in manual mode.

NOTE: This status bit is not available in the current software release.

• Operator Disable (OPER_DIS)

Alarm printing has been disabled by a user.

• Out of Service (OUT_OF_SVC)

Point is currently out of service.

• Program Disable (PROG_DIS)

Alarm printing has been disabled by the PPCL Program.



• Result (RESULT)

This status indicates whether the last command sent by the operator was successful.This is most useful for the “Get Totalized Value” command. If the Totalized value doesnot change after sending the command, the result status will indicate whether thecommand was successful, indicating that the totalized value has not changed or if therewas an error in processing the command.

Data Link Design ConsiderationsTable 6-3 and Table 6-5 provide detailed information about each field, which is important forscreen design considerations.

Table 6-1. Point Attribute Field Design.

Point Name Description Read/Write

Point TypesUsed With

Information

A_ADDRESS Network Address R/W* ALL 128 Character Dotted Address

A_ALARM_LVL Enhanced Alarm Level R ALL “Non-Enhanced”, “Level n”, n=1to 6

F_ALARM_LVL 0, 1 to 6

A_COV_LIMIT COV Limit R LAI, LAO,LPACI

13 Characters

F_COV_LIMIT Working Range

A_CV Current (Present) Value R/W All 13 Characters

F_CV Working Range

A_DESCRIPTOR Point Descriptor R All 17 Characters

A_ETAG Engineering Units R LAI, LAO,LPACI

7 Characters

A_HI_ALARM Hi Alarm Limit R LAI, LAO,LPACI

13 Characters

F_HI_ALARM Working Range

A_IV Initial Value R/W Except LAI,LDI

13 Characters

F_IV Working Range

A_LO_ALARM Low Alarm Limit R LAI, LAO 13 Characters

F_LO_ALARM Working Range

A_PRIORITY Command Priority R/W All “None”, “PDL”, “Emergency”,“Smoke”, “Operator”

F_PRIORITY 0, 5, 32, 34, 35

A_TOTAL Totalized Value R Except LPACI 13 Characters

F_TOTAL Working Range

* Writable from Database Builder only



Table 6-2. Point Characteristic Field Definitions.



Information

A_CHARACTER CharacteristicsSummary

R All from: “A EA PA TE TH BOIBINC CBE”

A_ALARMABLE Alarmable R All “NO” or “YES”

F_ALARMABLE — — — 0 or 1

A_ENH_ALARM Enhanced Alarmable R All “NO” or “YES”

F_ENH_ALARM — — — 0 or 1

A_PRT_ALARMS Print Alarms R All “NO” or “YES”

F_PRT_ALARMS — — — 0 or 1

A_TOTAL_ENB Totalize Enabled R Except LPACI “NO” or “YES”

F_TOTAL_ENB — — — 0 or 1

A_TOTAL_HRS Totalize Hourly R Except LPACI “NO” or “YES”

F_TOTAL_HRS — — — 0 or 1

A_BOUT_INVERT Binary Output Inverted R LDO, L2SL,L2SP, LFSSL,LFSSP,LOOAL,LOOAP

“NO” or “YES”

F_BOUT_INVERT — — — 0 or 1

A_BIN_CLOSED Binary Input NormallyClosed

R LDI “NO” or “YES”

F_BIN_CLOSED — — — 0 or 1

A_BOTH_EDGES Count Both Edges R LPACI “NO’ or “YES”

F_BOTH_EDGES — — — 0 or 1



Table 6-3. Point Command Field Definitions.



Information

F_SERVICE Command Into/Out ofService

R/W All 1 = Put Into Service

0 = Put Out of Service

F_NORMAL Command Into/Out of AlarmCommand Back to Normal

R/W All 1 = Into Alarm

0 = Back to Normal

F_PRINT Enable/Disable AlarmPrinting

R/W All 1 = Enable Alarm Printing

0 = Disable Alarm Printing

F_TOTALIZE Update Totalized Value W All Any Value

Table 6-4. Point Label Field Descriptions.



Information

A_AUTO_LABEL AUTO State Value R/W* LOOAL,LOOAP

13 Characters

A_FAST_LABEL FAST State Value R/W* LFSSL,LFSSP

13 Characters

A_OFF_LABEL OFF State Value R/W* LDI, LDO,LOOAL,LOOAP,L2SL, L2SP

13 Characters

A_ON_LABEL ON State Value R/W* LDI, LDO,LOOAL,LOOAP,L2SL, L2SP

13 Characters

A_SLOW_LABEL SLOW State Value R/W* LFSSL,LFSSP

13 Characters

A_STOP_LABEL STOP State Value R/W* LFSSL,LFSSP

13 Characters

* Writable from Database Builder only



Table 6-5. Point Status Field Descriptions.



Information

A_STATUS Status Summary R All from: “F, A, An CA OODSB PDSB HAND COV”

A_FAILED Failed R All “NO or “YES”

F_FAILED — — — 0 or 1

A_IN_ALARM In Alarm R All “NO or “YES”

F_IN_ALARM — — — 0 or 1

A_CMD_ALARM Commanded Into Alarm R All “NO or “YES”

F_CMD_ALARM — — — 0 or 1

A_OUT_OF_SVC Out of Service R All “NO or “YES”

F_OUT_OF_SVC — — — 0 or 1

A_OPR_DISABL Operator Disabled R All “NO or “YES”

F_OPR_DISABL — — — 0 or 1

A_PRG_DISABL Program Disabled R All “NO or “YES”

F_PRG_DISABL — — — 0 or 1

A_MANUAL_OVR Manual Override R LDI, LDO,L2SL,L2SP,LOOAL, LOOAP

“NO or “YES”

F_MANUAL_OVR — — — 0 or 1

A_COV_LINK COV Link Active R All “NO or “YES

F_COV_LINK — — — 0 or 1

A_RESULT Command Result R/W ** All 13 Characters

F_RESULT — — — —

** Writing clears the error message.



Viewing the Data Links

This section demonstrates how to switch to the View application using the QuickViewfunction. The View Screen shows the results of the data links added to the Draw Screen.

1. Do one of the following:

• Click the QuickView icon, .

• From the View menu, click QuickView to switch from Draw to the View application.Switching to View allows you to see the link updating with real data from yourSiemens Building Technologies, Inc. system.

The link should be updating with real-time data. If you see a group of question marks,such as ????????, this indicates that the driver is having problems communicating withthe hardware. The problem could be that the connection between S600 DatabaseDynamos and the S600 network point has not been established.

2. To return to the Draw application, click QuickDraw from the View menu, or pressCTRL+Q.

3. When the picture is complete, save the configuration as FILENAME.ODF (example:RMTEMP.ODF) by clicking Save-As from the File menu.

Continue with this process until you have finished populating all of the graphics screens withdynamic information from the Siemens Building Technologies, Inc. system.


7Troubleshooting

Chapter 7 provides an overview of how to troubleshoot communication problems between theFIX workstation and the System 600 APOGEE Building Level Network (BLN). Anunderstanding of the system components will be helpful in troubleshooting communicationproblems.


• System Components

• Run Time Information

• Common Problems

• Using the NT Event Viewer

• Using the Alarm History Window

• Registry Entries

System Components

Database Dynamos

System 600 APOGEE Database Dynamos (loadable blocks) are similar to PLC “register”block types (AR, DR) in the sense that field updates to or from the System 600 APOGEEnetwork points are communicated immediately, rather than waiting for SAC to scan theblocks. In addition, System 600 APOGEE blocks are primary blocks that can serve toschedule “chains” of block operations.

Communication between the blocks and System 600 APOGEE equipment takes placethrough three additional layers of software components (MsgManager service, AsyncSvcservice and LocalNet driver) and a DigiBoard serial card.

DigiBoard Serial Card

The DigiBoard is a multi-port serial communications adapter. It provides dedicated hardwareassistance for low level System 600 APOGEE network functions. thereby processingdemands on the operator workstation.



LocalNet Driver

The LocalNet driver is the lowest layer of the software components. LocalNet is a WindowsNT device driver, providing the communications engine for driving the DigiBoard serial card.

AsyncSvc Service

The AsyncSvc service sits above the LocalNet Device software and provides a unifiedmethod for sharing System 600 APOGEE messaging resources. The AsyncSvc service actsas a clearing house, allowing multiple clients to receive information from it without creatingexcessive System 600 APOGEE network traffic.

MsgManager Service

MsgManager service is the next level of the software layers and provides the capability forSystem 600 APOGEE blocks to exchange messages with the AsyncSvc service process.This service is added to Windows NT service list during installation of the Database Dynamosoftware.

Run Time Information

FIX32 applications and the MsgManager service share run-time System 600 APOGEE blockinformation using event message queues and a shared database file, PROXY.{A5BF7110-F9F7-11CF-96F0-00AA00597DC2}. (The file extension is a COM GUID indication of theobject type) A companion file, PROXY.LOG, contains detailed error logging information aboutdatabase operations that is not normally logged to the FIX Alarm History File. Additionaldetailed logging information about the operation of MsgManager service is contained in thefile MSG.LOG.

Common Problems

Some of the most common problems encountered when setting up and using DatabaseDynamos are caused by one or more of the following:

• Using incorrect or faulty cable connections. Verify the connection configurations inChapter 2, Setting Up the Hardware of this manual.

• Failing to match the baud rate and node number expected by the System 600APOGEE. Review Chapter 3, Installing the Software Module of this manual.

• Failing to add the FIX workstation as a node to the System 600 APOGEE BLN.

• Failing to install the S600 Database Dynamos FIX BTKCFG.EXE utility during theinstallation process.

Troubleshooting


• Using the same port or memory address space for the DigiBoard as anothercomputer expansion board. The LocalNet Configuration Utility is a good place to startto ensure proper functioning of the DigiBoard. Computer hardware resourceallocation can also be checked through the Windows NT Diagnostics program.

• The AsyncSvc service has not started. To check this, select Services from theControl Panel. AsyncSvc must have a status of “Started”.

• The MsgManager service has not started. To check this, select Services from theControl Panel. MsgManager must have a status of “Started”.

• The LocalNet device driver has not started. To check this, select Devices from theControl Panel. LocalNet must have a status of “Started”.

• The Sentinel device driver has not started. To check this, select Devices from theControl Panel. Sentinel must have a status of “Started”.

Using the NT Event Viewer

The NT Event Viewer is a standard NT tool showing the status of the programs operating onthe workstation. From the Start button, click Programs, and then click Administrative Tools(Common). The Event Viewer window (Figure 7-1) displays.

Figure 7-1. Event Viewer Window.

Windows NT classifies events as information, warnings, and errors. Table 7-1 contains adescription of these classifications.

Table 7-1. Windows NT Event Type Classifications.

Event type Description

Information Information events note infrequent but significant successful operations.

Warning Warning events indicate problems that are not significant, but indicate potential futureerrors or other problems. Errors that are recovered without loss of function or dataare classified as warnings.



Error Error events indicate significant problems that have occurred and that the usershould know about. Errors usually indicate a loss of functionality or data. Forexample, if a service cannot be loaded as the system boots, an Error event can belogged.

The NT Event Viewer has display options for viewing the System Log, Application Log, orSecurity Log. Administrative messages for device drivers are located in the System Log.Messages for services are located in the Application Log. Viewing the detail on any particularentry provides additional information on the nature of the event.

Using the Alarm History Window

The FIX Alarm History window contains information about the System 600 APOGEEDatabase Dynamos. To start the Alarm History Window, click the Alarm History icon while inthe Intellution Program Manager.

Figure 7-2. Alarm History Window.

The Alarm History Window displays messages concerning the results of operationsperformed on System 600 APOGEE Database Dynamo Blocks by both FIX applications andthe System 600 APOGEE MsgManager service. Refer to Figure 7-2. The messages relatedto these blocks have the following general layout:

time [FIX ] (application name) message text

The application name field indicates the executing process that posted the message to thealarm history window. Executing process can be one of the following:

DBB - FIX Database Builder application

DRAW - FIX Draw application

MSG - S600 MsgManager service

VIEW - FIX View application

WSAC - FIX SAC task

Troubleshooting


The message text field indicates the result of block related operation. This message line maybe preceded in the Alarm History window by one or more detailed information lines of thefollowing format:

interfaceName::functionName - text…

This information may be used by Siemens Building Technologies, Inc. support personnel tocorrelate Alarm History messages with Proxy Database log file entries when resolvingproblems with the operation of System 600 APOGEE Database Dynamos.

MsgManager Service Messages

MsgManager Service messages for System 600 APOGEE network communicationoperations conform to the following format:

MsgRequest - Type: [ type of network request]Return: [category]-[code]: [explanation]

Table 7-2 lists the types of network requests made by the MsgManager service.

Table 7-2. MsgManager Service Network Request Types.

Type Description

CommandAlarm Force a System 600 APOGEE point alarm status.

CommandPoint Command the present value of a System 600 APOGEE point at operatorpriority level.

PostAlarmStatus Command the alarm printing status of a System 600 APOGEE point.

PostPriority Command the priority level of a System 600 APOGEE point.

PostServiceStatus Command the service status of a System 600 APOGEE point.

ReadProcessData Monitor static point characteristics and non-event based reporting ofdynamic point properties.

ReadTotalizedValue Monitor the totalized value of a System 600 APOGEE point.

RegisterCov Initiate event based reporting for a System 600 APOGEE point.

The most common return category is (CEC), for Central Equipment Controller (MBC, SCU,Field Panel, etc.). The code that follows can be directly correlated with network error codeslisted in the APOGEE Field Panel User’s Manual (125-3000).

Fix32 Application Messages

Messages from FIX applications for System 600 APOGEE Database Dynamo blocks conformto the following format:

block name : exception type - operation [exception number]

ADDRESS ERROR - FindPoint



This exception indicates that an internal error occurred while processing the point addressfrom a System 600 APOGEE block. The block may be corrupted and should be deleted fromthe FIX database and recreated.

ADDRESS EXCEPTION - FindPoint

This exception indicates that an incomplete or badly formed System 600 APOGEE pointaddress was found in the named System 600 APOGEE block when attempting to locate aSystem 600 APOGEE point on the network. Point addresses have the following format:

network.trunk.cabinet.point

ATTRIBUTE ERROR - GetAttributes, SetAttributes

This exception indicates that an internal error occurred while processing a request to readfrom or write to a System 600 APOGEE point. The corresponding block may be corruptedand should be deleted from the FIX database and recreated.

ATTRIBUTE EXCEPTION - FindPoint, GetAttributes, Refresh, Register,SetAttributes, Unregister

This exception indicates that an attempt to read from or write to a System 600 APOGEE pointfailed. This failure is generally the result of competition by applications accessing the ProxyDatabase, and is normal under high load conditions such as system startup or System 600APOGEE network failures. The operation may be repeated automatically depending on theapplication that generated the failure.

BIND EXCEPTION - GetAttributes, Refresh, Register, SetAttributes,Unregister

This exception indicates that an attempt to “bind” or gain access to a Proxy Database objectfailed during a System 600 APOGEE block operation. This failure can occur due tocompetition by applications accessing the Proxy Database. However, if this failure occursrepeatedly for the same System 600 APOGEE block, the corresponding object in the ProxyDatabase may be corrupted and must be purged by restarting FIX and the MSG service.

CABINET EXCEPTION - FindPoint

This exception indicates that a System 600 APOGEE cabinet could not be located or thecorresponding object in the Proxy Database could not be created while attempting to find aSystem 600 APOGEE point on the network. The cabinet specification may be incorrect. Pointaddresses have the following format:


where the cabinet field panel is a number from 0 - 99.

HANDLE ERROR - FindPoint, GetAttributes, Refresh, Register,SetAttributes, Unregister

Troubleshooting


This exception indicates that an internal error occurred while processing a System 600APOGEE block. The block may be corrupted and should be deleted from the FIX databaseand recreated.

NETWORK EXCEPTION - FindPoint

This exception indicates that a System 600 APOGEE network could not be located or thecorresponding object in the Proxy Database could not be created while attempting to find aSystem 600 APOGEE point on the network. The network specification may be incorrect.Point addresses have the following format:


where the network is the name defined in the Registry entry:

HKEY_LOCAL_MACHINE\Landis&Staefa\Intellution\PlugIn\ ProxyNetwork

POINT EXCEPTION - FindPoint

This exception indicates that a System 600 APOGEE network could not be located or thecorresponding object in the Proxy Database could not be created while attempting to find aSystem 600 APOGEE point on the network. The point specification may be incorrect. Pointaddresses have the following format:


where the point is a valid System 600 APOGEE point name.

POINT TYPE EXCEPTION - FindPoint

This exception indicates that the point type of a System 600 APOGEE block does not matchthe point type of the corresponding point found on the network. Delete the block from the FIXdatabase or the point from the System 600 APOGEE cabinet and recreate the block or pointwith the correct point type.

TAG ERROR - FindPoint, GetAttributes, Register, SetAttributes,Unregister

This exception indicates that an internal error occurred while processing a System 600APOGEE block. The block may be corrupted and should be deleted from the FIX databaseand recreated, if it can be identified from the message.

TRUNK EXCEPTION - FindPoint

This exception indicates that a System 600 APOGEE trunk could not be located or thecorresponding object in the Proxy Database could not be created while attempting to find aSystem 600 APOGEE point on the network. The trunk specification may be incorrect. Pointaddresses have the following format:


where the trunk is a string of the form: P2Trunk_0.



Registry Entries

A number of parameters used to configure the operation of System 600 APOGEE DatabaseDynamos are stored in the Windows NT registry. Some entries underKEY_LOCAL_MACHINE\Landis&Staefa\Intellution\PlugIn\ProxyNetwork may requireadjustment for a particular site, including DbSizeInMbytes, MessagePoolSize,OnlineWaitInSec, and ReloadWaitInSec.

DbSizeInMbytes

This entry determines the size of the Proxy Database shared memory file and is set duringinstallation according to the number of System 600 APOGEE points that will be used by FIXapplications. Each point requires approximately 1 KB of storage in this file. The value of thiskey is specified in MB which corresponds to multiples of 1000 System 600 APOGEE points.

MessagePoolSize

This entry determines the size of the event message pool that is shared by the System 600APOGEE Database Dynamos and the MsgManager service. The value of this key is normallyset to the number of System 600 APOGEE blocks that will be used by FIX applications.

DbSizeInMbytes and may require alteration if the size of the database has increased from thenumber of points estimated during installation.

OnlineWaitInSec

This entry determines how quickly a System 600 APOGEE block will attempt to reestablishCOV registration with the corresponding System 600 APOGEE network point whenever theregistration has failed. The default value of this key (30) is set to avoid excessive System 600APOGEE network traffic during field panel failures.

ReloadWaitInSec

This entry determines how quickly a System 600 APOGEE block will attempt to reestablishCOV registration with the corresponding System 600 APOGEE network point when a FIXdatabase is first loaded or reloaded. The value of this key is typically set to the time requiredto establish COV registration for the total number of System 600 APOGEE blocks in the FIXdatabase. The default is set to 300 seconds.