Database Dynamos For Intellution S 32 Bit FIX Owner S Manual A6V10324337 Us en

System 600 APOGEE Database Dynamos for Intellution's 32-Bit FIX Owners Manual
125-2161 Rev. 3, 9/00
Rev. 3, September, 2000 NOTICE

This document contains information proprietary to Siemens Building Technologies, Inc. ( Siemens ). Any reproduction or disclosure of this information to unauthorized persons is prohibited, except as is allowed by prior written permission of Siemens. Every effort has been made to ensure that the contents of this manual are accurate. Siemens reserves the right to change the specifications in this manual without notice. Siemens assumes no responsibility for maintaining or upgrading the contents of this document. THE INFORMATION IN THIS MANUAL IS PRESENTED FOR INFORMATION PURPOSES ONLY. IT IS NOT A CONTRACTUAL COMMITMENT OR A MODIFICATION OF ANY CONTRACT THAT MAY EXIST BETWEEN 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 in accordance with the terms of such license. SERVICE STATEMENT Control devices are combined to make a system. Each control device is mechanical in nature and all mechanical components must be regularly serviced to optimize their operation. All Siemens Building Technologies, Inc. branch offices and authorized distributors offer Technical Support Programs that will ensure 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 to technical.editor@sbt.siemens.com APOGEE is a trademark of Siemens Building Technologies, Inc. Microsoft is a registered trademark, Windows and Windows NT are registered trademarks of Microsoft Corporation. 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 their respective companies.
All Rights Reserved. No part of this manual may be reproduced, in any form or by any means, without permission in writing 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
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
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 Fully Integrated Control System (FIX) automation software and System 600 APOGEE networks. This manual provides information for installing and configuring the Database Dynamos. It is written 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 600 APOGEE. Chapter 2, Setting up the Hardware, describes the hardware configuration issues that affect the operation of the Database Dynamos. Chapter 3, Installing the Software Module describes installing the System 600 APOGEE Database Dynamos software. Chapter 4, System 600 APOGEE Blocks explains adding System 600 APOGEE points to the FIX database. Chapter 5, Conversion Utility discusses converting System 600 APOGEE point information into a FIX32 import file. Chapter 6, Adding Points to the View Application describes how to add data links to graphically monitor and command System 600 APOGEE points on a View Screen. Chapter 7, Troubleshooting, describes how to troubleshoot communication problems between the FIX workstation and the System 600 APOGEE Building Level Network (BLN).
Siemens Building Technologies, Inc. Staefa Product Group
System 600 APOGEE Database Dynamos for Intellution's 32-Bit FIX Owner's Manual
Manual Conventions
The following table lists conventions to help you use this manual in a quick and efficient manner. Convention
Numbered Lists (1,2,3) indicate a procedure with sequential steps. Actions that you should perform are specified in boldface font. 1. 2.
Example
Turn OFF power to the computer. Turn ON power to the computer. Check to see that LEDs on memory board are lit.
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 important information. Notation
WARNING
Symbol
Meaning
Indicates that personal injury or loss of life may occur to the user if a procedure is not performed as specified.
CAUTION
Indicates that equipment damage or loss of data may occur if the user does not follow a procedure as specified.
Related Documents
The FIX software includes a complete set of online help manuals, also known as Electronic Books. The following online help manuals are referenced in this Database Dynamos manual.
II
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
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 Electronic Books. While working anywhere within the FIX program, click Help from the main menu and then click FIX Electronic Books.
Where To Send Comments

Your feedback is important to us. If you have comments about this manual, please submit them to technical.editor@sbt.siemens.com.
III
IV
1
Introduction
The Database Dynamos provides communication between Fully Integrated Control System (FIX) automation software and System 600 APOGEE networks. The Database Dynamos operate with 32-bit FIX software v6.15. The Database Dynamos is not included with FIX and must 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. The System 600 APOGEE point names, entered as tags in the FIX database, define the links between the two systems. Once all the point links are established, the FIX workstation receives only the data from the System 600 APOGEE points that have been reported to have changed by more than their respective significant Changes of Value (COVs). Significant COVs are defined within each point definition in the System 600 APOGEE database. The most critical factor contributing to the efficiency of the data exchange between the two systems is the amount of COV traffic on the System 600 APOGEE network. Proper system management by the user can contribute significantly to increased efficiency in communications performance. You may want to consider the following suggestions when designing a FIX database with a large number of points: COV values for the System 600 APOGEE points should be practical; for example, the maximum allowed by the control applications. In order to limit requests for dynamic points in the System 600 APOGEE, avoid requesting the redundant data associated with point values that may be derived from multiple points. For example, Cubic Feet per Minute (CFM) values for the air volume are typically determined from air velocity sensor readings. If the COV traffic efficiency is important, the data for only one of the points should be requested by the Database Dynamos.
Siemens Building Technologies, Inc.
1-1
The System 600 APOGEE is a distributed control system. Therefore, the overall control algorithms should be distributed. Calculations, monitoring, and control applications should be performed at the field panels, as much as possible, since the necessary data is most readily available. For example, when monitoring the status of a chiller, it may be beneficial to define virtual points and change their values via the resident Powers Process Control Language (PPCL) application only when the undesired condition occurs. This is done instead of reporting all the current chiller sensor values on the network. The FIX database could then include the virtual points since 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 600 APOGEE 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 primary blocks that can serve to schedule chains of block operations. Communication between the blocks and System 600 APOGEE equipment takes place through three additional layers of software components (MsgManager service, AsyncSvc service and LocalNet driver) and a DigiBoard serial card.
DigiBoard Serial Card

The DigiBoard is a multi-port serial communications adapter. It provides dedicated hardware assistance for low level System 600 APOGEE network functions, thereby processing demands on the operator workstation.
LocalNet Device
The LocalNet Device is the lowest layer of the software components. LocalNet is a Windows NT 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 a unified method for sharing System 600 APOGEE messaging resources. The AsyncSvc acts as a clearing-house, allowing multiple clients to receive information from it without creating excessive System 600 APOGEE network traffic.
1-2
Introduction
MsgManager Service
MsgManager Service is the next level of the software layers and provides the capability for System 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 Database Dynamos software. FIX32 applications and the MsgManager service share run-time System 600 APOGEE block information using event message queues and a shared database file, PROXY.{A5BF7110F9F7-11CF-96F0-00AA00597DC2}. (The file extension is a COM GUID indication of the object type.) A companion file, PROXY.LOG contains detailed error logging information about database operations that is not normally logged to the FIX Alarm History File. Additional detailed logging information about the operation of MsgManager service is contained in the file MSG.LOG.
1-3
1-4
2
Setting Up the Hardware
Chapter 2 discusses hardware configuration issues that affect the operation of the Database Dynamos. Chapter 2 discusses the following topics: 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 operating system 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 Building Technologies, Inc. recommends 64 MB RAM for SCADA nodes of 1000 or more System 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 APOGEE Database Dynamos software. CD-ROM drive. NETBIOS-compatible or TCP/IP-compatible network interface adapter (not required for stand-alone nodes). VGA or SVGA color graphics monitor and 100% IBM-compatible adapter.
2-1
Two-button mouse or compatible pointing device.
Software Key
A software key is required to run FIX. Refer to the Intellution Environmental Setup Manual for information 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 Setup Manual provides information required in order to change the operating systems configuration for FIX.
DigiBoard
A Digi Xe intelligent asynchronous serial communication board is required in order for the FIX workstation to access the System 600 APOGEE field panels. This DigiBoard (Xe board) is supplied 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 a down, up, up, down orientation for the switches. Use the following steps to install the Xe board. For more detailed information, refer to the Installation Guide included in the Digi Xe box. 1. Turn off the computers 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 computers cover.
Cabling
Figure 2-1 illustrates the basic wiring hookup between the P2 Controller and the FIX workstation, along with cable lengths and cable connector configurations. Figure 2-2 illustrates the wiring requirements for connecting the 9-pin PC/Xe board channel one port at the FIX work station to the Trunk Interface II (TI-II) module. The maximum cable length allowed (RS-232 type) is 50 feet (15.24 meters). The cable provided with the system is 6 feet (1.83 meters) long.
2-2
Setting Up the Hardware
Figure 2-3 illustrates the RS-485 hookup between the Trunk Interface II module and the P2 Controller BLN port connector.
RS-485 1000' (350m) MAX. P2 Controller

GW0583R1
RS-232 50' (350m) MAX. TI II
Fix Workstation
25DB(m) to 9DB(I) Connectors on Cable

Figure 2-1. Interconnect Block Diagram.
CLEAR
GW0584R1
TI-II CONNECTION
RS-485 CABLE
P2 CONTROLLER BLN PORT CONNECTION
Figure 2-2. RS-232 Hookup.
SCREW EADS FACE UP
BLACK
RED
SCREW HEADS FACE DOWN
2-3
9-PIN FEMALE CONNECTOR DCD 1 DSR 6 RXD 2
25-PIN MALE CONNECTOR 4 DTR 2 RXD 3 TXD 1 DCD 6 DSR 5 GND 7 RTS 8 CTS
FIX WORKSTATION
TXD 3 DTR 4 GND 5 RTS 7 CTS 8
TI-II
GW0585R1
RS-232 CABLE
MALE FEMALE
Figure 2-3. RS-485 Hookup.
2-4
3
Installing the Software Module
The System 600 APOGEE Database Dynamos software is installed using the System 600 Database Dynamos for Intellution FIX32 CD-ROM. Chapter 3 discusses the following topics: 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 the workstation DigiBoard Xe has been installed on the FIX workstation System 600 APOGEE points have been configured in their System 600 APOGEE field panels Any existing FIX32 databases have been exported Any previous System 600 APOGEE Database Dynamos installations have been uninstalled FIX32 system has been shut down You are logged on to the workstation with administrator level privileges
3-1
Installing the System 600 APOGEE Database Dynamos

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. The user should be a domain administrator for that particular NT machine. Make sure that the user does not have any other conflicting user rights. 2. Insert the System 600 Database Dynamos for Intellution FIX32 CD-ROM into the CDROM 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. The self-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 RAM and hard drive resources for the blocks (2k of each per block). Accuracy is important because 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 DB Dynamos v1.X.
6. The install program will ask if you would like to configure the new block types. Click Yes to 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 to have access to Database Dynamo Blocks for all eleven System 600 APOGEE point types. If not all blocks are needed, you may choose only the ones applicable to the application.
3-2
Table 1-1 lists the optional files, relative to the point types that must be supported.
Table 1-1. Optional Files.
Block
btk_L2L.dll btk_L2P.dll btk_LAI.dll btk_LAO.dll btk_LDI.dll btk_LDO.dll btk_LFL.dll btk_LFP.dll btk_LOL.dll btk_LOP.dll btk_LPA.dll
System 600 APOGEE Point Type

L2SL Point Type L2SP Point Type LAI Point Type LAO Point Type LDI Point Type LDO Point Type LFSSL Point Type LFSSP Point Type LOOAL Point Type LOOAP Point Type LPACI Point Type
After installation, run the Intellution Database Dynamo Configurator utility BTKCFG.EXE to add or remove Database Dynamo Block types. BTKCFG.EXE is normally located in the Fix32 root directory (C:\Fix32\ BtkCfg.exe ). Export any existing FIX32 databases before 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 Configuration Utility. 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, LocalNet is properly configured with 1 Digiboard. To close this utility, click the Close button. 5. From the Microsoft Windows NT Toolbar, click Start, Settings, Control Panel, and then Services. 6. Confirm that the service AsyncSvc is Started and Automatic.
3-3
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 Database Builder 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 fields added). This field count appears after the comment lines (lines beginning with a !) and is indicated by a number. It is good practice to add another comment line indicating that the 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.
3-4
Figure 3-1. DBBFLD.CFG Screen Part 1.
Figure 3-2. DBBFLD.CFG Screen Part 2.
3-5
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 FIXs database export utility. This is a good practice to eliminate the potential of corrupting the database. There is also no guarantee that 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 600 APOGEE Database Dynamo Blocks from the current FIX configuration.
3-6
4
System 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
Overview
There 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 in Chapter 5. This conversion utility is useful for automating the entry of a large number of points. Use the System 600 APOGEE block dialog boxes, similar to the generic block dialog boxes used while editing a FIX database. There are eleven System 600 APOGEE block dialog boxes used to configure database blocks for eleven of the System 600 APOGEE point types. Table 4-1 lists the eleven System 600 APOGEE points that can be directly configured on a FIX node.
Table 4-1. System 600 APOGEE Points Supported by FIX.
Point Type
LAI LAO LDI LDO L2SL L2SP LFSSL LFSSP LOOAL LOOAP LPACI
Description
Logical Analog Input Logical Analog Output Logical Digital Input Logical Digital Output Logical Two State Latched Logical Two State Pulsed Logical Fast/Slow/Stop Latched Logical Fast/Slow/Stop Pulsed Logical On/Off/Auto latched Logical On/Off/Auto Pulsed Logical Pulsed Accumulator Input
Database Dynamo
btk_lai.dll btk_lao.dll btk_ldi.dll btk_ldo.dll btk_l2l.dll btk_l2p.dll btk_lfl.dll btk_lfp.dll btk_lol.dll btk_lop.dll btk_lpa.dll
4-1
Run the Intellution Database Dynamo Configurator utility BTKCFG.EXE to add or remove supported Database Dynamo Block types. Export any existing FIX32 databases before running this utility.
NOTE:
The Logical Controller (LCTLR) point type is not supported by the Database Dynamos.
Point Type Definitions

The 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 and lighting). Logical Digital Output (LDO) - Provides one commandable digital state (used to command two-position ON/OFF devices such as fans and lighting). Logical Two-State Latched (L2SL) - Provides one commandable latched digital output (ON/OFF) and monitors one digital input for proof. Logical Two-State Pulsed (L2SP) - Provides two commandable pulsed digital outputs (ON/OFF) and monitors one latched digital input as a proof point. Logical FAST/SLOW/STOP Latched (LFSSL) - Provides commandable latched digital outputs (FAST/SLOW/STOP) and one optional digital input as a proof. Logical FAST/SLOW/STOP Pulsed (LFSSP) - Provides three commandable pulsed digital outputs (FAST/SLOW/STOP) and one optional digital input used as a proof. Logical ON/OFF/AUTO Latched (LOOAL) - Provides two commandable latched digital outputs and one digital input that can be used as a proof point. Logical ON/OFF/AUTO Pulsed (LOOAP) - Provides two commandable latched digital outputs (ON/OFF) and one commandable latched output (AUTO). The digital input may be used as an optional proof point. Logical Pulsed Accumulator (LPACI) - Counts pulses of one digital input point.
4-2
Logical Analog Input (LAI)

Figure 4-1 shows the dialog box used for configuring an LAI point block. An LAI point monitors the value of an analog input point (e.g., temperature, flow, pressure). A description of 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 a point/block connection is made, a snapshot of these fields is displayed when the screen is opened.
Tag Name
A unique identifier in the FIX Process Database. You can use a maximum of 30 alphanumeric characters, starting with a letter. No spaces are allowed.
Next Block
Tag Name of the next block in the chain.
4-3
Description
Alphanumeric explanation of Tag Name displayed in Alarm Summary, Reports, View. You can use a maximum of 40 alphanumeric characters.
NOTE:
This is the FIX description, not the System 600 APOGEE point descriptor resident in the System 600 APOGEE field panel.
Start Block on Scan

Scan, Alarm, and Control (SAC) automatically processes all primary blocks that have this box checked 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. This is similar to the System 600 APOGEE concept of points being online or offline, with online correlating to automatic. Most primary blocks are set as automatic and secondary blocks as manual.
NOTE: NOTE:
Scan Time
The interval that determines how often the Scan, Alarm, and Control (SAC) program processes a block in the process database (PDB).
NOTE:
System 600 APOGEE Blocks do not depend on the SAC Scan Time for reading and writing block values. This is similar to the function of a FIX PLC register block.
4-4
The System 600 APOGEE blocks have a default of 10 seconds for Scan Time which is appropriate for these blocks when used as stand-alone blocks. If the System 600 APOGEE blocks are used as primary blocks in a chain, the chain will use the Scan Time for the processing rate. There are two types of scan time: Table 4-2 shows Time Based scans:
Table 4-2. Time-Based Scan Times.
Increment
Subseconds Seconds Minutes Hours
Range
0.05 - 0.95 1 59 1M - 59M 1H - 24H
One-shot processing:
SAC program processes a block only once. The block does not trigger again unless the SAC 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 the FIX database for this block. The name can be verified by pointing to the Start button, and clicking Settings, Control Panel, Network, Identification, and Computer Name. Network Trunk Name or number of the System 600 APOGEE P2 network trunk on which the point is located. This field is case sensitive. Refer to the example on the following page. Cabinet Number Number of the System 600 APOGEE field panel where the point resides. Point Name System 600 APOGEE Point Name.
4-5
Example:
PC_1.P2Trunk_0.12.OATEMP NT workstation is PC_1 Point OATEMP is located in cabinet 12 on trunk 0 When creating multiple blocks, cut and paste the network address from one block to the next to avoid retyping the common portions of the field.
NOTE:
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 (if writing the point attribute). Table 4-3 lists the priorities in ascending order, with None being the lowest priority and Operator being the highest.
Table 4-3. Point Priorities.
Floating Point
0 5 32 34 35
Siemens Building Technologies, Inc. Text Meaning

None PDL Emergency Smoke 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 EA PA TE TH BOI BINC CBE identifies if the point is defined as Alarmable identifies if the point is defined for Enhanced Alarming identifies if the point is defined for Printing of Alarms identifies if Totalization for the point is Enabled identifies if Totalization is in Hours identifies if the point is defined to have its Binary Output Inverted identifies if the point is defined to have its Binary Input Normally Closed identifies if the point is defined to have Both Edges counted for totalization (applies to LPACI point type only) When the above conditions are true, the abbreviations are displayed. When the condition is false, the field is empty.
NOTE:
4-6
Present Value
Displays the System 600 APOGEE points 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 A An C O ODSB PDSB HAND COV indicates the point is failed indicates the point is in alarm indicates an enhanced alarm (n = alarm level) indicates the point has been commanded into alarm indicates the point is out of service indicates an operator has disabled the alarm printing indicates a program has disabled the alarm printing indicates a point is in manual override indicates the COV link for the point is active When the above conditions are true, the abbreviations are displayed. When the condition is false, the field is empty.
NOTE:
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 points value must change before it is reported. It is also the smallest denomination a point can be commanded to. For example, a point with a COV limit of 1 cannot report changes of 0.2 units and 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 units for each point in the database. Table 4-4 provides the information necessary to calculate the minimum and maximum values based on information from the System 600 APOGEE. In addition to the formulas, the following information must be known to determine the high and low 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 the formulas shown in Table 4-4.
4-7
Table 4-4. Minimum and Maximum Value Fields.
Field Panel
MBC MBC MBC MBC MBC MBC MBC ALL SCU SCU SCU SCU SCU SCU SCU RCU P2 RCU P2 RCU P2
where:
Point Module Type

Al_E (010 Vdc) Al_I (4-20 mA) Al_100K ohms Al_RTD AO_E (010 Vdc) AO_I (420 mA) AO_P (020 psi) Virtual Al_E (010 Vdc) Al_I (420ma) Al_P AI_100K AO_E AO_I AO_P Al_E (010 Vdc) AO_E AO_P
Point Type
LAI LAI LAI LAI LAO LAO LAO LAI/LAO LAI LAI LAI LAI LAO LAO LAO LAI LAO LAO
Sensor Type
V (Voltage) I (Current) T (Thermistor) I (Current) N/A N/A N/A N/A V (Voltage) I (Current) T (Thermistor) T (Thermistor) N/A N/A N/A V (Voltage) N/A N/A
Min. Point Value

=m( 3,584 ) + b =m( 3,584 ) + b =-40F(-17.7C ) =m(11543) + b =b =b =b =b =b =b+800m =b+1120m =-40F(-17.7C ) =b =b =b =b + 4200 =b =b + 42
Max. Point Value

=m(29,184) + b = m(29,184) + b =257F(125C) =m(18571)+b =m (30,720)+b = m(30,720)+b = m(30,720)+b = m(32,767)+b =4000m+b =4000m+b =2400m+b =257F(125C) =m(255) + b =m(255) + b =m(255) + b =m(21000) + b =m(1023) + b =m(255) + b
m = slope value for the point b = intercept value for the point
4-8
Alarms
The following dialog box (Figure 4-3) is accessed by clicking the Alarms and Security button on the Logical Analog Input dialog box.
NOTE:
These fields help define FIX alarming functionality for particular FIX tags. They do not 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 and requires a response. Allows other blocks to detect an alarm from the block. An entire chain can be affected when you disable alarms for a block. Enable Messaging - provides information about database events, operator inputs, or system activities that do not imply potential problems. Records process activity, but does not require an acknowledgment. Is sent to the same destinations as alarms for a given block, but messages do not appear in the alarm summary link. Output blocks generate messages whenever a value is written. If you check Enable Messaging, you must check both the Enable Alarming and the Event Msg check boxes.
4-9
Alarm Areas
Alarm areas are configured within a nodes System Configuration Utility (SCU). Entering the letter of an alarm area (letters A through P) specifies the local and remote nodes to which the blocks 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 blocks alarm priority is greater than or equal to the nodes alarm priority, then it is recorded by the node and sent to pre-configured alarm destinations. If it is less than the nodes priority, it is not sent to other nodes and does not appear at any alarm or messaging services.
Alarm Limits
Alarm Limits determine when alarms occur. When the current value extends outside the range 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 for enhanced alarming, the high and low limits defined in the panel are automatically filled in as defaults in the process database. For points with enhanced alarming enabled, an Alarm Block must be used. An Alarm Block and a LAI block are both primary blocks, which require a Program Block to link them.
Security Areas
Provides write protection for the block. A user must have access to the security area to change 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, the block is not write-protected.
4-10
Logical Analog Output (LAO)

Figure 4-5 shows the dialog box used to configure an LAO point block. An LAO provides one commandable 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 those described for the Logical Analog Input Dialog Box. Refer to the LAI descriptions for more information regarding these fields.
Initial Value
For Intellution programming use. Allows the operator to set the value of a point when it is placed 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.
4-11
Logical Digital Input (LDI)

Figure 4-7 shows the dialog box used to configure an LDI point block. An LDI point monitors the 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 Dialog Box. Refer to the LAI descriptions for more information regarding these fields. The only difference is that the Engineering Limits field is replaced with Labels field, which is described as follows:
Labels
Can be a label of up to 13 characters displayed when using an ASCII Data Link. System 600 APOGEE 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
0.0 1.0
ASCII
OFF ON
4-12
Logical Digital Output (LDO)

Figure 4-9 shows the dialog box used to configure an LDO point block. An LDO point provides one commandable digital state (used to command two-position ON/OFF devices such 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 Logical Analog Input Dialog Box. Refer to the LAI descriptions for more information regarding these fields. The two exceptions are the addition of the Initial Value field, and the replacement of the 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 is placed on scan (e.g., to turn on all fans before a batch is run). This does not affect the initial value set in field panels.
Labels
Can be a label of up to 13 characters displayed when using an ASCII Data Link. System 600 APOGEE 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.
Floating Point
0.0 1.0
ASCII
OFF ON
4-13
Logical Fast/Slow/Stop Latched (LFSSL)

Figure 4-11 shows the dialog box used to configure an LFSSL point block. An LFSSL provides commandable latched digital outputs (FAST/SLOW/STOP) and one optional digital input 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 to the LAI descriptions for more information regarding these fields. The two exceptions are the addition of the Initial Value field, and the replacement of the 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 is placed on scan. (For example, to turn on all fans before a batch is run.) This does not affect the initial value set in field panels.
Labels
Can be a label of up to 13 characters. System 600 APOGEE labels are the default and may be overridden by entering the label of choice. Defaults are listed in Table 4-10.
Floating Point
0.0 1.0 2.0
ASCII
STOP SLOW FAST
4-14
Logical Fast/Slow/Stop Pulsed (LFSSP)

Figure 4-13 shows the dialog box used to configure an LFSSP point block. An LFSSP provides three commandable pulsed digital outputs (FAST/SLOW/STOP) and one optional digital input used as a proof.
Figure 4-13. Logical Fast/Slow/Stop Pulsed Dialog Box.
Initial Value
Labels
Floating Point
0.0 1.0 2.0
ASCII
STOP SLOW FAST
4-15
Logical On/Off/Auto Latched (LOOAL)

Figure 4-15 shows the dialog box used to configure a LOOAL point block. A LOOAL provides two commandable latched digital outputs and one digital input that can be used as a proof point.
Figure 4-15. Dialog Box for an LOOAL Point Block.
Initial Value
Labels
Floating Point
0.0 1.0 2.0
ASCII
OFF ON AUTO
4-16
Logical On/Off/Auto-Pulsed (LOOAP)

Figure 4-17 shows the dialog box used to configure a LOOAP point block. A LOOAP point provides two commandable latched digital outputs (ON/OFF) and one commandable latched output (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
Floating Point
0.0 1.0 2.0
ASCII
OFF ON AUTO
4-17
Logical Two State Latched (L2SL)

Figure 4-19 shows the dialog box used to configure an L2SL point block. An L2SL point provides one commandable latched digital output (Logical ON/OFF) and monitors one digital input (Logical) for proof.
Figure 4-19. Logical Two State Latched Dialog Box.
Initial Value
Labels
Floating Point
0.0 1.0
ASCII
OFF ON
4-18
Logical Two State Pulsed (L2SP)

Figure 4-21 shows the dialog box used to configure an L2SP point block. An L2SP point provides two commandable pulsed digital outputs (Logical ON/OFF) and monitors one latched digital input (Logical) as a proof point.
Figure 4-21. Logical Two State Pulsed Dialog Box.
Initial Value
Labels
Floating Point
0.0 1.0
ASCII
OFF ON
4-19
Logical Pulsed Accumulator Input (LPACI)

Figure 4-23 shows the dialog box used to configure an LPACI point block. An LPACI point counts 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 those described for the LAI block. Refer to the LAI descriptions for more information regarding these fields.
Initial Value
4-20
Summary of Field Characteristics

Figure 4-25 is a summary of the information available for each point type. For instructions on viewing this information on a FIX View Screen, refer to Chapter 6, Adding Points to the View Application.
Figure 4-25. Summary of Field Characteristics.
4-21
4-22
5
Conversion Utility
The CNVT_FIX utility provides a means for converting System 600 APOGEE point information into a FIX32 import file (e.g., a GDB file) through the use of a Comma-Separated Variable (CSV) file. The utility can also be used to convert a FIX32 import file to a CSV text file. Chapter 5 discusses the following topics: 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 System 600 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; CSV to FIX32 GDB and FIX32 GDB to CSV. The switch entered on the command line determines which conversion will be performed.
5-1
Convention:
CNVT_FIX station_name trunk_ID [/g] [/c] [/v] [filename.csv] [filename.gdb]
Mandatory Parameters:
station_name trunk_ID The NT Network name of the computer running FIX32 The P2 trunk number associated with the points in the CSV file being converted
Switch Parameters (select one):

/g /c /v Create CSV spreadsheet file from FIX32 GDB import file Create FIX32 GDB import file from CSV spreadsheet file Verify CSV spreadsheet file
Optional Parameters:
filename.csv filename.gdb Override default CSV file name (dbase.csv) 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 station name 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 the conversion:
CAUTION: Any dbase.csv file already present in this directory will be overwritten! Back up any files to be saved before executing CNVT_FIX.EXE.
In a directory that includes both the CNVT_FIX.EXE program and the FIX32 import file dbase.gdb, run the CNVT_FIX program with the /g command line switch.
5-2
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 the dbase.gdb import file in the same subdirectory in which the conversion was run. If the conversion is successful, the following message displays, Conversion Completed Successfully!If the conversion is not successful, the following message displays Conversion 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 the conversion: 1. Create a CSV file to be converted to a FIX32 GDB import file. Name the file dbase.csv or provide the extra command line parameter to override the default CSV filename. This file can 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 proprietary tools. The file can be generated manually using any ASCII text based editor such as EDIT.EXE (Available with DOS version 3.3 or higher). The file must conform to the structure 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 file and create the dbase.gdb FIX32 GDB import file. If the conversion is successful, the following message displays, Conversion Completed Successfully!If the conversion is not successful, the following message displays Conversion NOT Successful!, in addition to the reason for the failure.
5-3
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 Microsoft Excel.
Microsoft Excel Spreadsheet Example

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

This example shows the same CSV file structure when using any text editor such as Microsoft DOS editor EDIT. For complete information on entering this information, see the Field 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 EFN2CO,EF2 FAN SSP,L2SL,00000P06,0 EFN3CO,EF3 FAN SSP,L2SL,00000P08,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
5-4
Conversion Utility
Inserting Comments
To put comments in the CSV file, insert a semicolon (;) as the first character in the row or line. All other lines are considered as input data and are validated according to the following formatting requirements.
CAUTION: If using the Point Checkout Data Report as input, you must place a semicolon at the beginning of the first line (the line containing the headings).
Field Data Requirements

The following formatting characteristics are required for each data field using the following CSV file structure: ;Point,Descriptor,Type,Address,Controller Comma-separated fields of data lines may be padded with spaces. The maximum line length is 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 points descriptor. This value will be overwritten dynamically in the FIX32 GDBs database whenever a change is made to the descriptor field at the controller. It serves mostly to provide an additional descriptive comment when generating the CSV file from the current contents of the FIX32 GDB import file with CNVT_FIX.EXES /g command line option. Maximum length: 16 characters Minimum length: 0 character Valid characters: A to Z, 0 to 9, and spaces
5-5
Type
The third data field contains the type of the preceding System 600 APOGEE point. Maximum length: 5 characters Minimum length: 3 characters Valid strings: LDI, LDO, LAI, LAO, L2SL, LOOAP, LPACI, L2SP, LOOAL, LFSSL, LFSSP Since LCTLR points are not supported through the FIX32 GDB, the conversion utility skips LCTLR points. Point names must be unique in the System 600. The conversion utility will accept the first instance of any particular point name and skip any subsequently duplicated point name.
NOTE: NOTE:
Address
The fourth data field contains the point's System 600 APOGEE Physical Address . This is an optional field and may be left blank.
Controller
The fifth data field contains the System 600 APOGEE field panel (cabinet) number where the point resides Maximum length: 2 characters Minimum length: 1 character 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 previous section. 2. In the directory that includes both the CNVT_FIX.EXE program and the CSV file, run the CNVT_FIX program with the /v command line switch.
Convention:
CNVT_FIX station_name trunk_ID /v [filename.csv] [filename.gdb]
5-6
Conversion Utility
Example:
CNVT_FIX NODE1 0 /v The conversion utility will display its version banner. The utility will read and verify the dbase.csv file. If the verification is successful, the following message displays, Number Of Unique Points Verified = x. Informational and warning messages may also display. These messages start with the text Inform: or Warning: . Look for error messages of the form Error: , which indicate that the CSV file is not suitable to generate the FIX32 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. Simply type the new filename(s) at the end of the command line. No backslash character is required as with other options previously mentioned. However, the filename suffix (.csv or .gdb) must be 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 named cnvt_log.txt. Open this file with a text editor to view the displayed conversion output. This information can be useful for reference or troubleshooting. Close the file before performing a conversion or the CNVT_FIX program will try to open or create the file. This may cause a file sharing violation, or create incorrect cnvt_log.txt file contents.
Troubleshooting
When the message Conversion NOT Successful displays, a reason for the failure displays. 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 disk integrity by using scandisk.exe or checkdisk.exe.
5-7
Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message: Cause: Message:
Unable To Open filename.gdb The import file from FIX32 must be present in same directory as CNVT_FIX.EXE. Unable To Open filename.csv File dbase.csv must be present in same directory as CNVT_FIX.EXE. Unable To Close File filename.csv Probably ran out of disk space. Unable To Close File filename.gdb Probably ran out of disk space. Error Creating Point xxxxxx Probably ran out of disk space. Error: Invalid File Name filename.xxx Valid filenames must have either a CSV or GDB extension. Error: Point Name 'xxxxxxxx' Improper Length Either nothing was entered for the point name in the appropriate field or the point name exceeds the maximum length of six characters. Error: Point Name 'xxxxxx' Contains Illegal Character 'x' Legal characters are A to Z and 0 to 9. Warning: Duplicate Point Name 'xxxxxx' System 600 APOGEE point names must be unique. Only the first instance of a particular point name is used. Subsequent names are ignored. Error: Unknown Point Type 'xxx' Refer to the CSV File Structure section of this document for valid point types. Inform: LCTLR Point Type Found 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. Error: Invalid Cabinet Number 'xx Valid cabinet numbers are from 0 to 99. 00 is also valid. Error: Invalid P2 Trunk Number Valid P2 trunk numbers are from 0 to 7. The trunk number must be entered as a single digit. Error: Point Descriptor 'xxxxxxxxxxxxxx' Too Long Maximum number of characters for a point descriptor is twelve . Characters may be alphanumeric. Unable To Write To File filename.csv Check for a write protected disk, low disk space, or file attributes of dbase.csv using attrib.exe. Unable To Add Point xxxxxx
5-8
Conversion Utility
Cause: Message: Cause:
Check for a write protected disk or low disk space. Unable To Open File CNVT_LOG.TXT An other application has already opened this file and is still using it. Close the file in your text editor and try again since this is probably a file sharing access violation. It is possible to have run out of disk space. Unable To Close File CNVT_LOG.TXT Probably ran out of disk space.
Message: Cause:
5-9
5-10
6
Adding Points to the View Application
Chapter 6 describes how to add data links to graphically monitor and command System 600 APOGEE points on a View Screen. Chapter 6 discusses the following topics: 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 screen and click the left mouse button once. The Data Link dialog box, similar to Figure 6-1, appears.
6-1
Figure 6-1. Data Link Dialog Box.
Field Descriptions Tagname

The Tagname field represents the tag that displays on the View Application. Either enter the point name (example: IBS_PC2.P2Trunk_0.0.LAI) in the Tagname field and press ENTER or click ? 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 the node, tag, and field to be represented by the data link and click OK. If the desired tag is not listed, click the Add button and follow the directions in the Adding a Block to the Database section. 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 to System 600 APOGEE points are described later in this chapter.
6-2
Figure 6-2. Field Select Window "A" Type.
Figure 6-3. Field Select Window "F" Type.
6-3
Dynamic Coloring
The value displayed by the Data Link can change color according to value or alarm condition of 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. For complete 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. The Choose Data Entry Method dialog box appears. In this dialog box, select the type of data entry you want the operation to perform. Refer to the Intellution Draw Manual for complete details 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 Select window. The Select a Type dialog box appears allowing the operator to select and add the database block to the database. This list includes the eleven System 600 APOGEE point 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.
6-4
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 dynamic attributes are input and output fields. The abbreviation in parenthesis indicates the nomenclature used on the Field Select window.
Address (ADDRESS)
This field displays the address entered for the FIX Block to link the FIX Database with the appropriate System 600 APOGEE point. Alarm Level (ALARM_LVL)
When a point is in an alarm state, the Alarm Level field indicates the severity of the alarm. Points defined using the System 600 APOGEE Enhanced Alarming Feature will have an Alarm Level value (1 to 6) correlating with the operator-defined priority of the alarm. If a point is commanded into alarm, or if the point is defined without selecting the Enhanced Alarming feature, this field will indicate 0x00. When a points Point Status field indicates that its alarm state is inactive, the Alarm Level field is meaningless. This field is also meaningless if the point is not defined as being Alarmable. Comments are representative of status conditions displayed by a System 600 APOGEE MMI point log report.
6-5
COV Limit (COV_LIMIT)
The Change Of Value (COV) Limit is the resolution in engineering units at which an analog point value is reported over the network. This value is also used to establish a dead band around high and low alarm limits for non-enhanced alarmable points. The COV Limit data type is REAL. Current Value (CV)
This field represents a System 600 APOGEE points Current Value. The data type is REAL. For some of the point types, these values have a corresponding textual representation which better describes their state to the user. The textual representation is what the user views. The REAL representation is what is used for calculations involving the block. High Alarm Limit (HI_ALARM)
The Alarm Limit fields are only meaningful for System 600 APOGEE points defined as Alarmable and defined without selecting the Enhanced Alarming Feature. The data type is REAL and is expressed in the same engineering units as the points Present Value. Initial Value (IV)
The Initial Value is for FIX programming use. It allows the operator to set the value of a tag when it is placed on scan. For example, turn the fans on before a batch is run. This does 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 as Alarmable and defined without selecting the Enhanced Alarming Feature. The data is of type REAL and is expressed in the same engineering units as the points Present Value. Point Priority (PRIORITY)
This field reflects either a point's current priority (if reading the point attribute) or desired priority (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
6-6
Print Alarms (PRT_ALARMS)
This indicates that alarms generated by this particular point have been sent to all designated 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. Points are 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 that have been enabled for totalization.
Point Characteristic Field Descriptions

This section provides a detailed description of each point characteristic field. These static characteristics are defined in the System 600 APOGEE Field Panel during setup and cannot be changed from FIX. The abbreviation in parenthesis indicates the nomenclature used on the 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 APOGEE field panel performs checking to determine whether or not the point is in the alarm state whenever the point changes value. Binary Output Inverted (BOUT_INVERT)
Indicates the point was defined to have its logical output to be inverted. This reverses the energize and de-energize commands for a digital output point meaningless for all point types except LDO. Binary Input Normally Closed (BIN_CLOSED)
Indicates a digital points input was defined to interface to a normally closed source. (for example, 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/on transition.
6-7
Descriptor (DESCRIPTIOR)
All System 600 APOGEE logical points allow the assignment of a point descriptor. This descriptor is an ASCII string of twelve alphanumeric characters (blank spaces are allowed). It is used to provide additional information to an operator when displaying points. Descriptors are not used by either the system or operator to call up displays or to command 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 present value of analog and pulse accumulator points (for example, " DEG F" or "KWH"). The field is composed of a text string. The string is used for reference purposes, and it has no effect on numerical representation or calculation of any point property. The string need not be unique. Unused characters must be padded with null terminators (0x00). The units field may also contain a null string. Enhanced Alarms (ENH_ALARM)
This indicates that the point was defined to support the System 600 APOGEE Enhanced Alarming feature. Totalize (TOTAL_ENB)
This indicates that the point was defined as enabled for Totalization. Totalized data is maintained locally at the points local System 600 APOGEE controller. Totalize in Hours (TOTAL_HOURS)
This indicates that the points Totalization Interval is defined as hourly; otherwise, every five 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 a point. 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 a light 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 light button will indicate current status.
6-8
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. The abbreviation in parenthesis indicates the nomenclature used on the Field Select dialog box. Status (STATUS)
This field is a textual summary of the points 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.
6-9
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 does not change after sending the command, the result status will indicate whether the command was successful, indicating that the totalized value has not changed or if there was an error in processing the command.
Data Link Design Considerations

Table 6-3 and Table 6-5 provide detailed information about each field, which is important for screen design considerations.
Table 6-1. Point Attribute Field Design. Point Name A_ADDRESS A_ALARM_LVL F_ALARM_LVL A_COV_LIMIT F_COV_LIMIT A_CV F_CV A_DESCRIPTOR A_ETAG A_HI_ALARM F_HI_ALARM A_IV F_IV A_LO_ALARM F_LO_ALARM A_PRIORITY F_PRIORITY A_TOTAL F_TOTAL
* Writable from Database Builder only
Description Network Address Enhanced Alarm Level
Read/ Write R/W* R
Point Types Used With ALL ALL
Information 128 Character Dotted Address Non-Enhanced, Level n, n=1 to 6 0, 1 to 6
COV Limit
LAI, LAO, LPACI
13 Characters Working Range
Current (Present) Value
R/W
All
Point Descriptor Engineering Units Hi Alarm Limit
R R R
All LAI, LAO, LPACI LAI, LAO, LPACI
17 Characters 7 Characters 13 Characters Working Range
Initial Value
R/W
Except LAI, LDI
Low Alarm Limit
LAI, LAO
Command Priority
R/W
All
None, PDL, Emergency, Smoke, Operator 0, 5, 32, 34, 35
Totalized Value
Except LPACI
6-10
Table 6-2. Point Characteristic Field Definitions. Point Name A_CHARACTER A_ALARMABLE F_ALARMABLE A_ENH_ALARM F_ENH_ALARM A_PRT_ALARMS F_PRT_ALARMS A_TOTAL_ENB F_TOTAL_ENB A_TOTAL_HRS F_TOTAL_HRS A_BOUT_INVERT Description Characteristics Summary Alarmable Enhanced Alarmable Print Alarms Totalize Enabled Totalize Hourly Binary Output Inverted Read/ Write R R R R R R R Point Types Used With All All All All Except LPACI Except LPACI LDO, L2SL, L2SP, LFSSL, LFSSP, LOOAL, LOOAP LDI LPACI Information from: A EA PA TE TH BOI BINC CBE NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES
F_BOUT_INVERT A_BIN_CLOSED F_BIN_CLOSED A_BOTH_EDGES F_BOTH_EDGES
Binary Input Normally Closed Count Both Edges
R R
0 or 1 NO or YES 0 or 1 NO or YES 0 or 1
6-11
Table 6-3. Point Command Field Definitions. Point Name F_SERVICE Description Command Into/Out of Service Command Into/Out of Alarm Command Back to Normal Enable/Disable Alarm Printing Update Totalized Value Read/ Write R/W Point Types Used With All Information 1 = Put Into Service 0 = Put Out of Service R/W All 1 = Into Alarm 0 = Back to Normal R/W All 1 = Enable Alarm Printing 0 = Disable Alarm Printing W All Any Value
F_NORMAL
F_PRINT
F_TOTALIZE
Table 6-4. Point Label Field Descriptions. Point Name A_AUTO_LABEL A_FAST_LABEL A_OFF_LABEL Description AUTO State Value FAST State Value OFF State Value Read/ Write R/W* R/W* R/W* Point Types Used With LOOAL, LOOAP LFSSL, LFSSP LDI, LDO, LOOAL, LOOAP, L2SL, L2SP LDI, LDO, LOOAL, LOOAP, L2SL, L2SP LFSSL, LFSSP LFSSL, LFSSP Information 13 Characters 13 Characters 13 Characters
A_ON_LABEL
ON State Value
R/W*
13 Characters
A_SLOW_LABEL A_STOP_LABEL
SLOW State Value STOP State Value
R/W* R/W*
13 Characters 13 Characters
* Writable from Database Builder only
6-12
Table 6-5. Point Status Field Descriptions. Point Name A_STATUS A_FAILED F_FAILED A_IN_ALARM F_IN_ALARM A_CMD_ALARM F_CMD_ALARM A_OUT_OF_SVC F_OUT_OF_SVC A_OPR_DISABL F_OPR_DISABL A_PRG_DISABL F_PRG_DISABL A_MANUAL_OVR Description Status Summary Failed In Alarm Commanded Into Alarm Out of Service Operator Disabled Program Disabled Manual Override Read/ Write R R R R R R R R Point Types Used With All All All All All All All LDI, LDO, L2SL, L2SP,LOOAL , LOOAP All All Information from: F, A, An CA O ODSB PDSB HAND COV NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES 0 or 1 NO or YES
F_MANUAL_OVR A_COV_LINK F_COV_LINK A_RESULT F_RESULT
COV Link Active Command Result
R R/W **
0 or 1 NO or YES 0 or 1 13 Characters
** Writing clears the error message.
6-13
Viewing the Data Links

This section demonstrates how to switch to the View application using the QuickView function. 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 your Siemens 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 with the hardware. The problem could be that the connection between S600 Database Dynamos and the S600 network point has not been established. 2. To return to the Draw application, click QuickDraw from the View menu, or press CTRL+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 with dynamic information from the Siemens Building Technologies, Inc. system.
6-14
7
Troubleshooting
Chapter 7 provides an overview of how to troubleshoot communication problems between the FIX workstation and the System 600 APOGEE Building Level Network (BLN). An understanding of the system components will be helpful in troubleshooting communication problems. Chapter 7 discusses the following topics: 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 APOGEE network points are communicated immediately, rather than waiting for SAC to scan the blocks. In addition, System 600 APOGEE blocks are primary blocks that can serve to schedule chains of block operations. Communication between the blocks and System 600 APOGEE equipment takes place through three additional layers of software components (MsgManager service, AsyncSvc service and LocalNet driver) and a DigiBoard serial card.
DigiBoard Serial Card

The DigiBoard is a multi-port serial communications adapter. It provides dedicated hardware assistance for low level System 600 APOGEE network functions. thereby processing demands on the operator workstation.
7-1
LocalNet Driver
The LocalNet driver is the lowest layer of the software components. LocalNet is a Windows NT 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 unified method for sharing System 600 APOGEE messaging resources. The AsyncSvc service acts as a clearing house, allowing multiple clients to receive information from it without creating excessive System 600 APOGEE network traffic.
MsgManager Service
MsgManager service is the next level of the software layers and provides the capability for System 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 Dynamo software.
Run Time Information

FIX32 applications and the MsgManager service share run-time System 600 APOGEE block information using event message queues and a shared database file, PROXY.{A5BF7110F9F7-11CF-96F0-00AA00597DC2}. (The file extension is a COM GUID indication of the object type) A companion file, PROXY.LOG, contains detailed error logging information about database operations that is not normally logged to the FIX Alarm History File. Additional detailed logging information about the operation of MsgManager service is contained in the file MSG.LOG.
Common Problems
Some of the most common problems encountered when setting up and using Database Dynamos are caused by one or more of the following: Using incorrect or faulty cable connections. Verify the connection configurations in Chapter 2, Setting Up the Hardware of this manual. Failing to match the baud rate and node number expected by the System 600 APOGEE. 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 the installation process.
7-2
Troubleshooting
Using the same port or memory address space for the DigiBoard as another computer expansion board. The LocalNet Configuration Utility is a good place to start to ensure proper functioning of the DigiBoard. Computer hardware resource allocation can also be checked through the Windows NT Diagnostics program. The AsyncSvc service has not started. To check this, select Services from the Control Panel. AsyncSvc must have a status of Started. The MsgManager service has not started. To check this, select Services from the Control Panel. MsgManager must have a status of Started. The LocalNet device driver has not started. To check this, select Devices from the Control Panel. LocalNet must have a status of Started. The Sentinel device driver has not started. To check this, select Devices from the Control 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 on the 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 a description of these classifications.
Table 7-1. Windows NT Event Type Classifications.
Event type
Information Warning
Description
Information events note infrequent but significant successful operations. Warning events indicate problems that are not significant, but indicate potential future errors or other problems. Errors that are recovered without loss of function or data are classified as warnings.
7-3
Error
Error events indicate significant problems that have occurred and that the user should know about. Errors usually indicate a loss of functionality or data. For example, if a service cannot be loaded as the system boots, an Error event can be logged.
The NT Event Viewer has display options for viewing the System Log, Application Log, or Security 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 particular entry 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 APOGEE Database Dynamos. To start the Alarm History Window, click the Alarm History icon while in the Intellution Program Manager.
Figure 7-2. Alarm History Window.
The Alarm History Window displays messages concerning the results of operations performed on System 600 APOGEE Database Dynamo Blocks by both FIX applications and the System 600 APOGEE MsgManager service. Refer to Figure 7-2. The messages related to 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 the alarm history window. Executing process can be one of the following: DBB - FIX Database Builder application
DRAW - FIX Draw application MSG VIEW - S600 MsgManager service - FIX View application
WSAC - FIX SAC task
7-4
Troubleshooting
The message text field indicates the result of block related operation. This message line may be preceded in the Alarm History window by one or more detailed information lines of the following format: interfaceName::functionName - text This information may be used by Siemens Building Technologies, Inc. support personnel to correlate Alarm History messages with Proxy Database log file entries when resolving problems with the operation of System 600 APOGEE Database Dynamos.
MsgManager Service Messages

MsgManager Service messages for System 600 APOGEE network communication operations 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
CommandAlarm CommandPoint PostAlarmStatus PostPriority PostServiceStatus ReadProcessData ReadTotalizedValue RegisterCov
Description
Force a System 600 APOGEE point alarm status. Command the present value of a System 600 APOGEE point at operator priority level. Command the alarm printing status of a System 600 APOGEE point. Command the priority level of a System 600 APOGEE point. Command the service status of a System 600 APOGEE point. Monitor static point characteristics and non-event based reporting of dynamic point properties. Monitor the totalized value of a System 600 APOGEE point. 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 codes listed in the APOGEE Field Panel Users Manual (125-3000).
Fix32 Application Messages

Messages from FIX applications for System 600 APOGEE Database Dynamo blocks conform to the following format: block name : exception type - operation [exception number] ADDRESS ERROR - FindPoint
7-5
This exception indicates that an internal error occurred while processing the point address from a System 600 APOGEE block. The block may be corrupted and should be deleted from the FIX database and recreated. ADDRESS EXCEPTION - FindPoint This exception indicates that an incomplete or badly formed System 600 APOGEE point address was found in the named System 600 APOGEE block when attempting to locate a System 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 read from or write to a System 600 APOGEE point. The corresponding block may be corrupted and 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 point failed. This failure is generally the result of competition by applications accessing the Proxy Database, and is normal under high load conditions such as system startup or System 600 APOGEE network failures. The operation may be repeated automatically depending on the application 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 object failed during a System 600 APOGEE block operation. This failure can occur due to competition by applications accessing the Proxy Database. However, if this failure occurs repeatedly for the same System 600 APOGEE block, the corresponding object in the Proxy Database 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 the corresponding object in the Proxy Database could not be created while attempting to find a System 600 APOGEE point on the network. The cabinet specification may be incorrect. Point addresses have the following format: network.trunk.cabinet.point where the cabinet field panel is a number from 0 - 99. HANDLE ERROR - FindPoint, GetAttributes, Refresh, Register, SetAttributes, Unregister
7-6
Troubleshooting
This exception indicates that an internal error occurred while processing a System 600 APOGEE block. The block may be corrupted and should be deleted from the FIX database and recreated. NETWORK EXCEPTION - FindPoint This exception indicates that a System 600 APOGEE network could not be located or the corresponding object in the Proxy Database could not be created while attempting to find a System 600 APOGEE point on the network. The network specification may be incorrect. Point addresses have the following format: network.trunk.cabinet.point 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 the corresponding object in the Proxy Database could not be created while attempting to find a System 600 APOGEE point on the network. The point specification may be incorrect. Point addresses have the following format: network.trunk.cabinet.point 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 match the point type of the corresponding point found on the network. Delete the block from the FIX database or the point from the System 600 APOGEE cabinet and recreate the block or point with the correct point type. TAG ERROR - FindPoint, GetAttributes, Register, SetAttributes, Unregister This exception indicates that an internal error occurred while processing a System 600 APOGEE block. The block may be corrupted and should be deleted from the FIX database and 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 the corresponding object in the Proxy Database could not be created while attempting to find a System 600 APOGEE point on the network. The trunk specification may be incorrect. Point addresses have the following format: network.trunk.cabinet.point where the trunk is a string of the form: P2Trunk_0.
7-7
Registry Entries
A number of parameters used to configure the operation of System 600 APOGEE Database Dynamos are stored in the Windows NT registry. Some entries under KEY_LOCAL_MACHINE\Landis&Staefa\Intellution\PlugIn\ProxyNetwork may require adjustment 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 during installation according to the number of System 600 APOGEE points that will be used by FIX applications. Each point requires approximately 1 KB of storage in this file. The value of this key 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 600 APOGEE Database Dynamos and the MsgManager service. The value of this key is normally set 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 the number of points estimated during installation.
OnlineWaitInSec
This entry determines how quickly a System 600 APOGEE block will attempt to reestablish COV registration with the corresponding System 600 APOGEE network point whenever the registration has failed. The default value of this key (30) is set to avoid excessive System 600 APOGEE network traffic during field panel failures.
ReloadWaitInSec
This entry determines how quickly a System 600 APOGEE block will attempt to reestablish COV registration with the corresponding System 600 APOGEE network point when a FIX database is first loaded or reloaded. The value of this key is typically set to the time required to establish COV registration for the total number of System 600 APOGEE blocks in the FIX database. The default is set to 300 seconds.
7-8

Database Dynamos For Intellution S 32 Bit FIX Owner S Manual A6V10324337 Us en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Database Dynamos For Intellution S 32 Bit FIX Owner S Manual A6V10324337 Us en

Загружено:

Авторское право:

Доступные форматы

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

125-2161 Rev. 3, 9/00

Rev. 3, September, 2000 NOTICE

How to Use This Manual

Siemens Building Technologies, Inc. Staefa Product Group

Click OK to save changes and close the dialog box.

How to Use This Manual

Security Manual Draw Manual Historical Trending Manual View Manual

Accessing the FIX Electronic Books

Where To Send Comments

Siemens Building Technologies, Inc. Staefa Product Group

Siemens Building Technologies, Inc. Staefa Product Group

Relationship between FIX and System 600 APOGEE

Siemens Building Technologies, Inc.

DigiBoard Serial Card

Siemens Building Technologies, Inc.

Siemens Building Technologies, Inc.

Siemens Building Technologies, Inc.

Setting up the Workstation

Minimum FIX hardware requirements

Siemens Building Technologies, Inc.

Two-button mouse or compatible pointing device.

Siemens Building Technologies, Inc.

Setting Up the Hardware

RS-485 1000' (350m) MAX. P2 Controller

RS-232 50' (350m) MAX. TI II

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

P2 CONTROLLER BLN PORT CONNECTION

Figure 2-2. RS-232 Hookup.

Siemens Building Technologies, Inc.

SCREW EADS FACE UP

SCREW HEADS FACE DOWN

9-PIN FEMALE CONNECTOR DCD 1 DSR 6 RXD 2

TXD 3 DTR 4 GND 5 RTS 7 CTS 8

Siemens Building Technologies, Inc.

Siemens Building Technologies, Inc.

Installing the System 600 APOGEE Database Dynamos

Siemens Building Technologies, Inc.

Installing the Software Module

System 600 APOGEE Point Type

Siemens Building Technologies, Inc.

Updating DDB Spreadsheet

Siemens Building Technologies, Inc.

Installing the Software Module

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

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

Siemens Building Technologies, Inc.

Uninstalling the Database Dynamos

Siemens Building Technologies, Inc.

Siemens Building Technologies, Inc.

Point Type Definitions

Siemens Building Technologies, Inc.

System 600 APOGEE Blocks

Logical Analog Input (LAI)

Figure 4-1. Logical Analog Input Dialog Box.

Siemens Building Technologies, Inc.

Start Block on Scan

Siemens Building Technologies, Inc.

System 600 APOGEE Blocks

Siemens Building Technologies, Inc.

Siemens Building Technologies, Inc. Text Meaning

Siemens Building Technologies, Inc.

System 600 APOGEE Blocks