unity/metasys supplement

UNITY/Metasys Supplement Version 5.8

POWER

TEC DOC # LIT-TD-1026 09/2002

2

Table of Contents UNITY/Metasys Supplement UNITY 5.8

The documentation contained in this publication is the exclusive property of Johnson Controls, Inc., and its use is restricted to the licensed software with which it is furnished. This publication may not be used for any other purpose without the express written consent of Johnson Controls, Inc. Johnson Controls, Inc., reserves the right to update specifications when appropriate. Information contained in this document is based on specifications believed to be correct at the time of publication.

Echelon ©, Coactive©, Windows NT©, and General Electric© are registered trademarks and service marks of companies other than Johnson Controls, Inc. FSC™, CPL™ and NexSys™ are trademarks of Johnson Controls, Inc.

© 2002 Johnson Controls, Inc. All Rights Reserved

System Products www.johnsoncontrols.com 9410 Bunsen Parkway Revised 09/2002

Louisville, KY 40220 Printed in U.S.A.

3

UNITY 5.8 UNITY/Metasys Supplement Table of Contents

Chapter 1: Overview ............................................................... 5 1 Metasys Hardware Overview ................................................................................... 6

1.1 Network Control Module (NCM) ............................................................................ 6 1.2 Network Control Unit (NCU) .................................................................................. 6 1.3 Metasys Network and UNITY Interface ................................................................ 6

2 Metasys Objects ......................................................................................................... 7 2.1 Hardware Objects ...................................................................................................... 7

2.1.1 CS .................................................................................................................................. 7 2.1.2 CSG .............................................................................................................................. 7

2.1.2.1 Object Attributes ....................................................................................................... 8 2.1.3 LCG .............................................................................................................................. 8 ..............................................................................................................

ects ...................................................................................................................................................................................................................ts .........................................................................................................ts (AI) ................................................................................................

puts(AO) ........................................................................................... (AD) .................................................................................................

ts (BI) .................................................................................................ut (BO) ............................................................................................. (BD) ..................................................................................................r (ACM) ............................................................................................. (CR) ..................................................................................................

tabases ................................................................................................base ....................................................................................................ase ......................................................................................................atabase ..............................................................................................NITY/Metasys Subsystem ..........................................................

UNITY/Metasys Subsystem ..........................................................oints in UNITY ................................

2.2 Control Objects .......................................................................................................... 8 2.2.1 PIDL ............................................................................................................................. 8

2.3 Point Objects .............................................................................................................. 8 2.3.1 Analog Inputs (AI) ..................................................................................................... 8 2.3.2 Analog Outputs(AO) ................................................................................................ 9 2.3.3 Analog Data (AD) ...................................................................................................... 9 2.3.4 Binary Inputs (BI) ...................................................................................................... 9 2.3.5 Binary Output (BO) .................................................................................................. 9 2.3.6 Binary Data (BD) ....................................................................................................... 9 2.3.7 Accumulator (ACM) .................................................................................................. 9 2.3.8 Card Reader (CR) ....................................................................................................... 9

3 Metasys Databases ................................................................................................... 10 3.1 Global Database ....................................................................................................... 10 3.2 NCM Database ......................................................................................................... 10 3.3 Controller Database ................................................................................................. 10

4 Enable the UNITY/Metasys Subsystem ............................................................. 11 5 Disable the UNITY/Metasys Subsystem ............................................................. 12 Chapter 2: Metasys Points in UNITY ..................................13 1 Add/Modify a Metasys System .............................................................................. 14 2 Delete a Metasys System ........................................................................................ 16 3 Read Points from Metasys System ........................................................................ 17 4 Map Metasys Points to UNITY Groups ............................................................... 18 5 Delete Metasys Points from a UNITY Group .................................................... 20 6 Delete a UNITY Group .......................................................................................... 21 7 Print UNITY Groups Reports on Metasys Points .............................................. 22 Chapter 3: Point Commands ................................................ 23 1 Request Point Status ............................................................................................... 24 2 Command Points ...................................................................................................... 26

2.1 Command a Binary/Digital Point ........................................................................ 26 2.2 Command an Analog Point ................................................................................... 27

3 Alarand Alarm Messages ......................................................................................... 28 3.1 Communication Alarm ............................................................................................ 28 3.2 Panel Alarm .............................................................................................................. 28 3.3 Point Alarms ............................................................................................................. 28

4

Table of Contents UNITY/Metasys Supplement UNITY 5.8

Chapter 4: Cable Guide ........................................................ 29 1 Metasys Direct Connections .................................................................................. 30 2 Metasys with Short Haul Modem .......................................................................... 31 3 Metasys with Leased Line Modems ...................................................................... 32 4 Metasys with Fiber Optic Converter .................................................................... 36 Metasys Index ....................................................................... 37

Chapter 1: Overview

Chapter Overview This chapter of the UNITY/Metasys Supplement will: • Give an overview of Metasys hardware. • Discuss Metasys object and databases. • Demonstrate how to enable/disable the UNITY/Metasys

system.

Chapter 1: Overview UNITY/Metasys UNITY 5.8

6

1 Metasys Hardware Overview Johnson Control’s Metasys is an open Facilities Management System (FMS) using existing communication standards and models. Designed in a loosely coupled, object oriented format, Metasys provides access to all object data from any point in the network. The Network Control Module serial port allows access to all Metasys network data through a simple system of English object names. This supplement is intended to be used by people who are knowledgeable about general building automation, and have a working knowledge of the Metasys field equipment. This document is not an introductory course to the Metasys field equipment. However, the terminology used to describe the Metasys field equip-ment will be covered.

1.1 Network Control Module (NCM)

work options.

directly support 250-300 objects.

ace

network or up to four directly connected networks.

line and on-line polling, and general communications. UNITY

like the NCMs, XMs, and ASCs.

The “brain” of Metasys is the network control module (NCM), a 386 computer without a hard drive. The NCM executes programs, performs trending, point history and alarm analysis, and keeps the clock time for the entire system. Submodules inside the NCM provide memory, communication, I/O, and net-work options.

1.2 Network Control Unit (NCU) The NCM, the digital control module (DCM), and the multiplex modules (XMs) are housed inside a field panel, the network control unit (NCU). Each NCU can directly support 250-300 objects.

1.3 Metasys Network and UNITY Interface A Metasys network is a group of related facility management system (FMS) equipment controlled by at least one NCM and interconnected by an N1 LAN (or modem and phone lines, if remote). A facility can have just one or multiple networks. The operator workstation (OWS) can be used to monitor just one network or up to four directly connected networks. The NCMs are connected daisy chain fashion within an ARCNET network. UNITY is connected to a NCM via an RS-232 serial port, not the ARCNET. Each NCM has one N2 Bus, an RS-485 protocol network, to link it to controllers and point interfaces. This N2 Bus is a daisy chain configuration which supports offline and on-line polling, and general communications. UNITY is an OS/2 WARP program. UNITY/Metasys subsystem is compatible with all Metasys hardware, like the NCMs, XMs, and ASCs.

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

Figure 1-1 . A Sample Metasys System Setup with N1 ARCNET and N2 BUS.

UNITY 5.8 UNITY/Metasys Chapter 1: Overview

7

2 Metasys Objects Metasys must recognize hardware like the NCMs and printers, control objects like the PID loop or GPL process, and points like the ACMs (accumulators) and BD (Binary Data). So, Metasys defines each “object” with a 16 digit name. The first eight digits are the system name, and many object can share the same system name. The second eight digits are the object name and are unique to each object. Metasys allows 255 objects per hardware panel. An object is a software description for either a sensor or controller type, a hardware device, or a program that analyses inputs and calculates and sends outputs to perform a function. Metasys recognizes three types of objects: hardware objects, control objects, and point objects.

A hardware object is a software description of a hardware device. Such objects might include the OWS, NCMs, and printers.

Control systems are a variety of configurable ASCs that can stand alone. The two formally defined CSs that Metasys uses are C210A and C260A. C210As monitor

Metasys must recognize hardware like the NCMs and printers, control objects like the PID loop or GPL process, and points like the ACMs (accumulators) and BD (Binary Data). So, Metasys defines each “object” with a 16 digit name. The first eight digits are the system name, and many object can share the same system name. The second eight digits are the object name and are unique to each object. Metasys allows 255 objects per hardware panel. An object is a software description for either a sensor or controller type, a hardware device, or a program that analyses inputs and calculates and sends outputs to perform a function. Metasys recognizes three types of objects: hardware objects, control objects, and point objects.

2.1 Hardware Objects A hardware object is a software description of a hardware device. Such objects might include the OWS, NCMs, and printers.

2.1.1 CS Control systems are a variety of configurable ASCs that can stand alone. The two formally defined CSs that Metasys uses are C210A and C260A. C210As monitor the temperature and velocity pressure of VAV boxes so they can send the commands to maintain a zone temperature. C260As are similar. They monitor the temperature and humidity of a heating/cooling system that uses a water-source heat pump, and C260As issue the commands to make the necessary mechanical changes. UNITY does not support the C210A or the C260A control system objects.

2.1.2 CSG A set of inputs and outputs can be grouped together and called a generic control system (CSG). A generic control system may be used to program an ASC. This way any new ASC added to Metasys will have a protocol to follow. This object type allows a maximum of 16 AIs, 16 AOs, 16 BIs, and 16 BOs. UNITY supports the CSG via CS objects. A CS object is an addressable entity in the Metasys database that allows an operator to view and manipulate various data in an application specific controller (ASC) defined as a Control System. The database must define the configuration of the controller in the MODELS.UND file. The software model in the MODELS.UND file tells the system how to map ASC definitions to CS objects. This configuration specifies how hardware or software data within the controller maps to attributes of the CS object. Individual .UND files define ASCs for each NCM. These files will specify the ASC type, its hardware address, software model, and so on. CS objects are “windows” into the controller’s internal data, including field information, intermediate calculations, or parameters for internal programming.


8

2.1.2.1 Object Attributes CS object attributes are the analog or digital data values that are addressable via a CS object. A CS object is a collection of attributes from a Metasys system defined by a software model. A software model designates which attributes the CS object will display and the order the attributes display in, contains brief descriptions of each attribute, determines which attribute value will display when a status is requested, and sets which engineering units the attributes have. The object may include ASC parameters or point data. The object will display the value of a single attribute when a status is requested from the Metasys front end. To display information on CS object attributes in UNITY, you must map each attribute of a CS object to a UNITY point.

requested, and sets which engineering units the attributes have. The object mayinclude ASC parameters or point data. The object will display the value of a single

information on CS object attributes in UNITY, you must map each attribute of a CS object to a UNITY point. Typically, a Metasys system should map to only one UNITY group. Attribute

supported. NOTE: The same hardware point may be an attribute of multiple CS objects.

This controller can be used with other switchable loads, as well.

specific controllers (ASCs) are among the control objects.

The proportional, integral, derivative loop generates outputs using a variety ofinputs and variables so that it can issue closed loop control commands to a certainDCM.

Typically, a Metasys system should map to only one UNITY group. Attribute types include analog inputs (CSAI), analog outputs (CSAO), binary inputs (CSBI), binary outputs (CSBO), analog data (CSAD), binary data (CSBD), working setpoint (CSSP), and multi-state (CSMS). In UNITY, the CSAI, CSAO, CSAD, and CSSP attributes may be mapped to analog points, and the CSBI, CSBO, and CSBD attributes may be mapped to digital points. CSMS attributes are not supported.

NOTE: The same hardware point may be an attribute of multiple CS objects. 2.1.3 LCG

The lighting controller group object is an ASC that is programmed to switch off/ on a group of building light circuits on the Intelligent Lighting Controller (ILC). This controller can be used with other switchable loads, as well.

2.2 Control Objects A control object is a software program that analyzes inputs, calculates, and sends outputs to perform a function. PID loops, demand limiting groups, control sequences, graphic programming language (GPL) process, and the application specific controllers (ASCs) are among the control objects.

2.2.1 PIDL The proportional, integral, derivative loop generates outputs using a variety of inputs and variables so that it can issue closed loop control commands to a certain DCM. From the Metasys Operator Workstation (OWS), the value of a PIDL object (which appears in logs and in the PIDL object’s Object Focus window) is actually its “setpoint” value. Typically, this setpoint is a desired temperature. If you wish, UNITY can display this setpoint value, as well as the output value, or several other attributes of the PIDL that are visible/commandable from the PIDL object’s Object Focus window. These attributes are Setpoint, Output, Input #1-6, Offset, Low Saturation Limit, High Saturation Limit, Auxilliary Switch Input, or Selector Input Signal.

2.3 Point Objects A point object is a software description of a sensor or controller type equipment. These points include the accumulator (ACM), analog data (AD), analog input (AI), analog output digital (AOD), analog output setpoint (AOS), binary data (BD), binary input (BI), binary output (BO), and card reader (CR).

2.3.1 Analog Inputs (AI) Analog inputs are sensors that report a value. This value is typically a temperature or relative humidity reading.


9

2.3.2 Analog Outputs(AO) Analog outputs are analog controls that adjust variable position devices. Analog output points include analog output digital (AOD) and analog output setpoint (AOS). AOD is used with a PID loop object for position control. AOS is used for position control and setpoint control, but is not used in conjunction with a PID loop.

2.3.3 Analog Data (AD) An analog data object is not a readout from any physical sensor or device. Rather, it is the analog value assigned by an operator or generated as the result of a control process. Although it is not a direct readout from a sensor, it is given the characteristics and software capabilities of an AI object.

2.3.4 Binary Inputs (BI) Binary inputs are points from a hardware device monitoring a two state field condition. For example, a switch is on or off.

2.3.5 Binary Output (BO) Binary outputs are points that control two position output devices. These devices are typically relays. Three position devices (off/auto/on) require two output points. These two points are automatically assigned when the point is set up.

2.3.6 Binary Data (BD) A binary data object is not a readout from any physical sensor or device. Rather, it is the binary value assigned by an operator or generated as the result of a control process. Although it is not a direct readout from a relay or switch, it is given the characteristics and software capabilities of an BI object.

2.3.7 Accumulator (ACM) An accumulator (ACM) object is the software representation of a hardware point from a BI device measuring flow or consumption by monitoring a rate of contact change.

2.3.8 Card Reader (CR) A card reader object is used with card access and is not supported by UNITY.


10

3 Metasys Databases Metasys has three types of databases: global, NCM, and controller. Global and NCM databases are uploaded and downloaded from the NCU panel, and controller databases are only downloaded from the NCU panel. UNITY does not support the upload or download of these databases.

3.1 Global Database The global database contains network configuration, the devices system, systems, report/access groups, and the password database.

3.2 NCM Database The NCM database contains process code, object and feature data such as GPL process objects, object definition and trend data.

3.3 Controller Database Each object in a network has its own database record (file) containing information such as where it is located in the network, engineering data, input/output assignments, etc. and resides at the NCM where it was defined.


11

4 Enable the UNITY/Metasys Subsystem The Metasys system must be enabled before UNITY will recognize the NCUs. Until the system is enabled, UNITY will not be able to issue commands to or receive data from the NCUs.

Note: The default setting is enabled. 1) Select Enable/Disable from Metasys system menu.

The system menu is displayed on the left. Once the Enable/ Disable feature is selected, the System Command dialog box appears (Figure 1-2).

Figure 1-2. System Command Dialog Box Used to Enable the System. 2) Select the System Enable radio button.

3) Click .

The System Command message box appears (Figure 1-3). The UNITY/ Metasys subsystem is enabled.

Figure 1-3. Request Completed Dialog Box.

4) Click .

The System Command message box disappears.


12

5 Disable the UNITY/Metasys Subsystem When the UNITY/Metasys subsystem is disabled, UNITY will ignore any connected NCU field panels. As long as the system is disabled, UNITY will not be able to issue commands to or receive data from the panels. 1) Select Enable/Disable from the Metasys menu of the System pull-down

menu. The system menu will look similar to the one at the left. After selecting the Enable/Disable menu, the System Command dialog box will appear (Figure 1- 4).

Figure 1-4. System Command Dialog Box Used to Disable the System. 2) Select the System Disable radio button.

3) Click .

The System Command message box appears (Figure 1-5). The UNITY/ Metasys subsystem is disabled.

Figure 1-5. Request Completed Dialog Box.

4) Click .

The System Command message box disappears.

Chapter 2: Metasys Points in UNITY

Chapter Overview This chapter of the UNITY/Metasys Supplement: • Tells how to add, modify, and delete Metasys point systems

in UNITY. • Describes how to map Metasys points into UNITY groups. • Tells how to modify, delete, and print reports on Metasys

points in UNITY groups.

Chapter 2: Metasys Points in UNITY UNITY/Metasys UNITY 5.8

14

1 Add/Modify a Metasys System Metasys organizes its objects in systems that the user defines. A system is a list of objects or points. Objects are generally organized in a logical manner, not necessarily based on the physical location of those objects. Each NCM can control many different systems. Each system can have a total of 250 systems can be supported. A Metasys/UNITY group can have a maximum of 255 points. For UNITY integration, all the systems must be identified and brought into UNITY. To do this the NC*.UND file for a paricular NCM must be obtained from the Metasys workstation. You must also acquire the MODELS.UND file for the entire FMS. The .UND files must be placed into the datafile directory of the subsystem. The .UND represents a decompiled version of the corresponding NCM database. These files contain a text description of all the systems present on a particular NCM and points within those systems.

Note: Download the databases to the OWS and run UNDDL to break the database into the .UND files. Store the .UND files in the datafile sub-directory of the UNITY/ Metasys subsystem.

To support CS and PIDL objects in the UNITY/Metasys subsystem, convert the appropriate attributes of the CS and PIDL objects to available UNITY points. You may map any or all of the CS or PIDL attributes into UNITY. UNITY can display several attributes (see PIDL in Chapter 1) of the PIDL that are typically visible/commandable from the Metasys OWS. UNITY automati-cally creates 13 available attribute points when a PIDL point is encountered in a .UND file. Since each attribute point will reference the same Metasys object, these points share the same system and object names. To differentiate between them, we display a new attribute column in the Available Metasys Points list. This identifies which of the above attributes a given point will reference.

Note: Of the available attribute points, all of them are commandable except the Output attribute point which is set by the PIDL process.

CS object attributes are not predefined like PIDL attributes are. The MODELS.UND file defines the visible/commandable attributes of all CS objects by storing the software models. As a result, when you import points from a UND file that contains CS objects, you need to verify that the appropriate MODELS.UND file is in the \UNITY\SUBSYSxx\DATAFILE directory. Depending on the complex-ity of the software model, and the number of CS objects, it is possible to generate far more than 255 available points from a system.

Note: No restriction prevents a Metasys database from referencing the same hardware with more than one CS object. If this happens, UNITY generates a set of attribute points for each CS object, even though they duplicate the behavior of the previously mapped points. When mapping these points into UNITY, simply ignore the duplicate points. Examine the default descriptors of attribute points to determine which hardware device a CS attribute point references.

Follow these steps to input the Metasys system points into UNITY.

1) Select Edit Systems from the System pull-down menu. The system menu is shown at the left. Edit system is highlighted. When this selection is made, the dialog box shown in Figure 2-1 will appear.

2) Click to add a system or to edit an exitsting system.

The appropriate dialog box will display.

UNITY 5.8 UNITY/Metasys Chapter 2: Metasys Points in UNITY

15

1 Add/Modify a Metasys System - continued

Figure 2-1. System Editor Dialog Box.

Figure 2-2. Edit Metasys System Name Dialog Box.

Figure 2-3. Edit Metasys System Name Dialog Box. 3) Enter the Metasys system name into the System field or change the

existing name. 4) Enter the NCMs .UND file name into the UND File Name field or edit

the existing name. Do NOT include the file extension (.UND). When Metasys is installed, all the objects must be defined. These objects are defined using the Graphic Program Language (GPL) and Data Definition Language (DDL), or the FMS software. Each NCM has an associated .UND file, which is the decompiled version of the .DDL file. It is this name that must be typed in here for the program to recognize the object. For more information refer to the Metasys User’s Guide.

5) Use the spin box to select the NCM address. 6) Use the spin box to select the subnet address.

Systems with internet bridges use the subnet number. For most systems, however, this is set to the default.

7) Click to return to the previous screen.

8) Choose to close the window.


16

2 Delete a Metasys System To delete points from the system, follow these steps. 1) Select Edit Systems from the System pull-down menu.

The system menu is shown at the left. Edit system is highlighted. When this selection is made, the dialog box shown in Figure 2-4 will appear.

Figure 2-4. System Editor Dialog Box. 2) Place the cursor on the system to be deleted. Choose . That

system of points will be removed. Note: If the system contains points that have been mapped into UNITY groups, an asterisk

will appear next to the system name. If a system has been mapped (has an asterisk), it cannot be deleted. In that case, the delete button will be grayed out.

3) Choose to close the window.


17

3 Read Points from Metasys System Once the Metasys systems have been added, their points must be read. These Metasys points can then be mapped into UNITY. 1) Pull down the System menu and select Edit System.

The Edit System menu appears at the left. When the Edit system choice is made, the following message box will appear. This is the same window used to add, modify and delete systems (Figure 2-5).

Figure 2-5. System Editor. 2) Highlight the system of point that will be read into UNITY. 3) Click .

UNITY will scan the .UND file in the database file or directory on the hard disk and pull in all the points from that system. The information that is extracted for each point in the system is the point type, descriptor and analog high and low limits. The message box in Figure 2-6 will appear. Click . The points can now be mapped using the Edit menu.

Figure 2-6. Request Completed Message Box. Note: If a Metasys system is reprogrammed, you must download the databases to the OWS

and run UNDDL again. Replace the .UND files in the datafile directory of the UNITY/Metasys subsystem. Then you must use this procedure again to update the list of system points.


18

4 Map Metasys Points to UNITY Groups By mapping Metasys attributes to UNITY points, you may display multiple CS objects in UNITY simultaneously. From the Metasys front end, you may view only one CS object at a time.

1) Choose Groups from the Edit menu. The edit menu is shown at the left. The Edit Groups window will appear.

Figure 2-7. Edit Groups Window.

2) Type in the appropriate group number and select or .

If you are adding a new group, the Selesct NCM dialog box will display.

Figure 2-8. Select NCM Dialog Box. 3) If you are adding a new group, use the spin box to select the appropriate

NCM address and click . Once the NCM has been chosen, the following dialog box appears. The field on the right contains all the points in this NCM, and it could include points from multiple systems. The right field has three column. The first designates the system, the second indicates the object, and the last column defines the attribute. Each atrribute of an object must be individually highlighted and added (or mapped) to a UNITY point.

Figure 2-9. The Edit Group Dialog Box with Points to be Mapped into UNITY. 4) Type an appropriate description of the group into the Descriptor field,

if desired. Steps 1-4 must be completed before mapping any points. However, binary and analog points have different engineering units. Therefore, a different list of engineering units will display.


19

4 Map Metasys Points to UNITY Groups - continued 5) Using the cursor highlight the UNITY point number in the left column

and the system/object/attribute in the right column that will be mapped to the UNITY point. Click .

A list of engineering units will appear. Figure 2-10 shows the binary engineering units, and Figure 2-11 shows the analog engineering units.

Figure .2-10. Binary Engineering Units. Figure 2-11. Analog Engineering Units 6) Change the descriptor in the Descriptor field, if desired.

When a point is selected, the descriptor is automatically read in from the .UND file. However, a different name may be typed into the Descriptor field now. The default descriptor of a point will include the short Metasys descriptor and the software model which includes the system name and the hardware device name. Note: Analog high and low alarm limits are also read in from the .UND file. They are not

displayed here, but they can be seen in the point status display window. 7) Choose the appropriate engineering unit and click .

This dialog box will close, displaying the previous point mapping window. Select another point and repeat steps 5-7. When points have been mapped in, the window will look similar to the one in Figure 2-12.

Figure 2-13. Edit Group Dialog Box with Points Mapped to a UNITY Group.

8) When all the points have been mapped into UNITY, click .

9) Click to close the Edit Group dialog box.


20

5 Delete Metasys Points from a UNITY Group 1) Select Groups from the Edit menu.

The Edit menu is shown at the left. The Edit Groups dialog box will appear (Figure 2-14).

Figure 2-14. Edit Group Dialog Box. 2) Enter the assigned number of the system of points that needs to be

deleted. Enter the group number into the Enter Group Number field and click

. The Edit Group dialog box appears (Figure 2-15).

Figure 2-15. Edit Group Dialog Box. 3) Select the point number from the UNITY Point list that is to be deleted

and click . The point is removed from the UNITY point list and added to the Metasys point list.

4) Repeat step 3 for each point being deleted in the group.

5) Click .

6) Click .


21

6 Delete a UNITY Group 1) Select Groups from the Edit menu.

The Edit menu is shown at the left. The Edit Groups dialog box appears (Figure 2-16).

Figure 2-16. Edit Groups Dialog Box. 2) Enter the number of the group being deleted.

Enter the group number into the Enter Group Number field and click . A warning message box appears (Figure 2-17).

Figure 2-17. A Delete Warning Dialog Box.

3) If the group being deleted is the correct group click . If the group

is not the one to be deleted, click .

4) Click .


22

7 Print UNITY Groups Reports on Metasys Points 1) Select Groups from the Edit menu.

The Edit menu is shown at the left. The Edit Groups dialog box appears (Figure 2-18).

Figure 2-18. Edit Groups Dialog Box. 2) Enter the number of the group being printed into the Enter Group

Number field.

3) Click .

The Print Group dialog box appears (Figure 2-19).

Figure 2-19. Select Printer Dialog Box. 4) Click the appropriate button for the Group information to be printed.

Click for a report with the group number, point numbers, point descriptors, point types and the corresponding hardware points to be printed on the destination printer. Click for a report with the group number, point numbers, message names and alarm types printed at the destination printer. Click for a report with a complete TOD programming list for this group’s points printed at the destination printer.

5) Click . The print Groups dialog box closes and the Edit Groups dialog box reappears.

6) Click .

The Edit Groups dialog box closes.

Chapter 3: Point Commands

Chapter Overview This chapter of the UNITY/Metasys Supplement: • Tells how to request point status. • Details how to command points. • Describes alarms and alarm messages.

Chapter 3: Point Commands UNITY/Metasys UNITY 5.8

24 .

1 Request Point Status 1) Select Point from the Commands menu.

The Commands menu is shown at the left. Choose Points and the Point Command dialog box appears (Figure 3-1).

Figure 3-1. Point Command Dialog Box. 2) Enter the point address in the Point field.

If the point address is known, enter it in the Point edit field. If the address is unknown, click on one of the red arrows on either side of the Point edit field and select the appropriate point. The commands available for the point appear in the Commands box (Figure 3-2).

Figure 3-2. Point Command Dialog Box Showing Available Commands.

UNITY 5.8 UNITY/Metasys Chapter 3: Point Commands

25

1 Request Point Status - continued 3) Click .

Information about the point appears in the Status and Detail boxes (Figure 3- 3).

Figure 3-3. Point Command Dialog Box with Status and Detail Panels for a BO Point. 4) Repeat steps 2 and 3 for the status request of each point. 5) Click .

The Point Command dialog box disappears. Note: For more information on the Point Command dialog box, see Chapter 2 of the User’s

Guide to UNITY.


26 .

2 Command Points All the Metasys/UNITY point commands are similar. The following sections go over how to command binary and analog points. UNITY refers to binary points as digital points. The binary/digital points include BI, BO, and BD. The analog points include AI, AOD, AOS, AD, ACM, CSG, CS, LC, and PIDL points. Remember that this is not the only way to command points. These points can also be commanded from a graphic or the programs. Refer to Chapter 2 of the User’s Guide to UNITY for more information. Metasys assigns priorities to commands. Priorities range from one to three where one is the highest priority. Override and auto are priority one commands, commands issued by processes or programs are priority two, and adjust and release commands are priority three. UNITY will only issue override and auto commands. Therefore, a point commanded by UNITY must be released in UNITY before priority two or three Metasys commands will be implemented. For analog points, the UNITY set is the same as the Metasys override, and the UNITY release is equivalent to Metasys auto. For digital points, the UNITY on/ off is the same as Metasys override, and UNITY release is equivalent to Metasys auto. UNITY will not issue the Metasys adjust or release commands.

2.1 Command a Binary/Digital Point 1) Select Point from the Commands menu.

The Commands pull-down menu is shown at the left. Select Points and the Point Command dialog box appears.

2) Enter the point address into the Point field. If the point address is known, enter it into the Point edit field. If the address is unknown, click on one of the red arrows on either side of the Point edit field and select the appropriate point. The commands available for the point appear in the Commands box.

3) Click . Information about the point appears in the Status and Detail boxes.

Figure 3-4. Point Command Dialog Box Showing Available Commands and Current Status. 4) Select the command to be issued.

A “Request Complete” message appears in the bottom right corner of the Point Command dialog box showing that the command request has been completed.

UNITY 5.8 UNITY/Metasys Chapter 3: Point Commands

27

2.1 Command a Binary/Digital Point - continued 5) Repeat steps 2 - 4 for each point being commanded. 6) Click .

2.2 Command an Analog Point 1) Select Point from the Commands menu.

The Commands pull-down menu is shown at the left. Select Points and the Point Command dialog box appears.

2) Enter the point address into the Point field. The commands available for the point appear in the Commands box.

3) Click . The point information appears in the Status and Detail boxes.

Figure 3-5. Point Command Dialog Box Showing Point Information. 4) Enter a new value in the parameter field and click 5) Select the command to be issued.

A “Request Complete” message appears in the bottom right corner of the Point Command dialog box showing that the command request has been completed.

6) Repeat steps 2 - 5 for each point being commanded. Note: The analog input will display values in the Detail box after high and low. Analog

outputs will have a n/a after high and low in the Detail box. 7) Click .

Note: You can also command a point from a graphic. For more information, see Chapter 2 of the User’s Guide to UNITY.


28 .

3 Alarms and Alarm Messages UNITY is responsible for generating and reporting alarms. Standard UNITY alarm types will be used for the Metasys alarms generated. Point alarms can be use as events to trigger EIAs from a given point. The following section lists the alarms that UNITY can issue.

3.1 Communication Alarm If for any reason UNITY is disconnected from the Metasys panel a communica-tion down alarm will occur. Once communication is restored, a communications up alarm will be displayed.

3.2 Panel Alarm The Metasys panel can generate several panel alarms. Those alarms include panel off, panel on, and hardware reset. These alarms come directly from the Metasys panel and are represented in UNITY as a text string in the alarm region.

3.3 Point Alarms The following list contains alarms that may be displayed for points within the UNITY system. •Alarm - Binary alarms occur when a binary point changes from its normal to alarm state. These alarms are generated by binary status points when they are not in the correct state, or by commandable binary points when the sensed state does not agree with the commanded state.

•High Alarm - High alarms occur when an analog point’s assigned high limit is exceeded.

•High Warning - High warning alarms occur when an analog point’s assigned high limit warning is exceeded.

•Low Alarm - Low alarms occur when an analog point’s assigned low limit is exceeded.

•Low Warning - Low warning alarms occur when an analog point’s assigned low limit warning is exceeded.

•Normal - Normal alarms occur when a point changes from an alarm state to normal. These alarms are generated by a group or point and signify that an alarm has been reset, or that an error has been corrected. This is also the normal status of a point not in error.

•Trouble - Trouble alarms are generated by fire points when an open loop condition exists.

•Unmapped Point Alarm - If a point alarm comes in from the Metasys panel and the point has not been mapped into UNITY, the unmapped point alarm will be displayed.

Chapter 4: Cable Guide

Chapter Overview This chapter of the UNITY/Metasys Supplement will: • Direct Connections • Short Haul Connections • Leased Line Connections • Fiber Optic Connections

Chapter 4: Cable Guide UNITY/Metasys Supplement UNITY 5.8

30

1 Metasys Direct Connections The NCUs are connected daisy chain fashion within an ARCNET network. UNITY is connected to a NCM via an RS-232 serial port, not the ARCNET. Each NCM has one N2 Bus, an RS-485 protocol network, to link it to controllers and point interfaces. This N2 Bus is a daisy chain configuration which supports offline and on-line polling, and general communications. By default UNITY will look for a connection to the NCM with address 1. If you wish to use an NCM with a different address to connect with UNITY, you must specify the address using the HA command line parameter when you start the subsystem. You must start Metasys with a command line similar to START METASYS SUBSYSXX HA=YY. The subsystem number is XX, and the NCM address for the connection is YY. To connect with an NCM, you must verify the setting in the Metasys front end. The NCM with the RS-232 connected with UNITY must be configured as an Operator Workstation (OWS). This NCM must also be designated as the port for the report groups that receive critical alarms. In order for the critical alarms to register on the UNITY front end, the Metasys group called UNITY must be added to the Metasys front end Report Access group on the OWS PC. Finally, the UNITY subsystem needs three .UND files from the Metasys front end. Place the GLOBAL.UND, NCM.UND, and MODEL.UND in the ..\UNITY\SUBSYSXX\DATAFILE directory.

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

Figure 4-1. Cable Pinout Connections for Metasys.

��

��

Figure 4-2. Metasys connects with UNITY via RS-232 to the COM port on the NCM.

UNITY 5.8 UNITY/Metasys Supplement Chapter 4: Cable Guide

31

2 Metasys with Short Haul Modem Metasys wiring connections to the NCM 101 via short haul modems are shown below. To use a nine pin connection from the IRM to the modem, use the cable supplied with the short haul modem (EVMBMC-0006). If a 25-pin connection is used, use a straight through cable.

Note: The straight through cable needs pins 1, 2, 3, 4, 5, 6, 7, 8, and 20. A 25 pin cable with only three wires will not work properly.

Use a 25-pin cable to connect the short haul modem with the NCM. For the NCM 300 use the cable specified for the 300, and for the NCM 200 use the cable specified for the 200.

��

��

��

��

�� !"#$�$"%&��'�(��

��(�)� %� �*��(+

,��

��

��

��

��

��

��

��(�)� %� �*��(+

��-��."/$01

��-��."/$01

�� !"#$�$"%&��'�(��

Figure 4-3. Cable Pinout Connections for Metasys Using Short Haul Modems.


32

3 Metasys with Leased Line Modems When the modem is operating, the display will indicate the current settings. For example, it might read “V.34 19200 ON LINE.” If you press the NO button, you will enter the modem setup mode. The modem will ask you a series of questions which reflect its current setting. If you wish to change a setting, you will press YES. Otherwise, you will press NO to leave the setting unchanged. All changes are dynamic. As soon as an entry is made, the modem will begin using it. When finished, you may store your options as a User Option Set. These options must be set up on both the IRM modem and the Metasys modem as indicated below. 1) Enter the setup mode by pressing the NO button. 2) The display will ask “DIAL STORED NUMBER?” Press NO. 3) The display will ask “DISPLAY STATUS?” Press NO. 4) The display will ask “SELECT TEST?” Press NO. 5) The display will ask “MODIFY CONFIGURATION?” Press YES.

When you press YES, you enter the configuration setup. From here, several sets of options may be changed.

6) The display will ask “CHANGE MODEM OPTIONS?” Press YES. If the option that displays is correct, press NO. If you wish to change the option, press YES. Use the list below to set the parameters on the two modems. After the modem reaches the end of this parameter list, it will again ask “CHANGE MODEM OPTIONS?” If you wish to go through the list one more time, press YES. Otherwise, press NO. IRM Modem:

LEASE LINE 4 WIRE MODULATION V.34 DCE MAX RATE 19200 DCE MIN RATE DISABLED V.34 RATE THRESH HIGH BER V.34 ASYM RATES ENABLED NORMAL FORCED ANSWER V.32B FAST TRAIN DISABLED AUTO RETRAIN ENABLED SQ AUTO RATE DISABLED INTERNAL CLOCK DIAL TX LEVEL -10 DBM RING FREQ LIMIT ENABLED LEASE TX LEVEL 0 DBM LINE CURRENT DIS LONG MANUAL DIAL BACKUP LOOKBACK TIME 15 MIN

Metasys Modem: Same as IRM, except the FORCED ANSWER should be NORMAL ORIGINATE.

7) The display will ask “CHANGE PROTOCOL OPTIONS?” Press YES. If the option that displays is correct, press NO. If you wish to change the option, press YES. Use the list below to set the parameters on the two modems. After the modem reaches the end of this parameter list, it will again ask “CHANGE PROTOCOL OPTIONS?” If you wish to go through the list one more time, press YES. Otherwise, press NO.


33

3 Metasys with Leased Line Modems - (continued) IRM Modem:

LAPM PROTOCOL ENABLED MNP PROTOCOL DISABLED PROTOCOL FALLBAK DISABLED NORMAL DATA COMPRESSION CONSTANT DTE SPEED DTE FLOW CONTROL RTS DCE FLOW CONTROL CTS XON/OFF PASSTHRU DISABLED INACTIVITY TIMER OFF BREAK OPTION #5 V.42 FAST DETECT ENABLED

Metasys Modem: Same as IRM.

8) The display will ask “CHANGE DTE OPTIONS?” Press YES. If the option that displays is correct, press NO. If you wish to change the option, press YES. Use the list below to set the parameters on the two modems. After the modem reaches the end of this parameter list, it will again ask “CHANGE DTE OPTIONS?” If you wish to go through the list one more time, press YES. Otherwise, press NO. IRM Modem:

ASYNC DATA DTE RATE 19200 8-BIT CHAR SIZE NO PARITY ‘AT’ COMMAND SET ENABLED IGNORE DTR CHANGE DSR FORCED HIGH DCD NORMAL CTS FORCED HIGH DTE FALLBACK DISABLED OPTIONS RETAINED AT DISC.

Metasys Modem: Same as IRM.

9) The display will ask “CHANGE TEST OPTIONS?” Press NO. 10) The display will ask “CHANGE DIAL LINE OPTIONS?” Press NO. 11) The display will ask “CHANGE SPEAKER OPTIONS?” Press NO. 12) The display will ask “LOAD OR STORE OPTION SET?” Press YES.

You may save your settings as USER OPTION #1. After the modem reaches the end of this question series, it will again ask “LOAD OR STORE OPTION SET?” If you wish to go through the list one more time, press YES. Otherwise, press NO. When the modem asks: LOAD FACTORY OPTION SET, press NO. LOAD FROM USER OPTION SET, press NO. STORE PRESENT OPTIONS, press YES. STORE TO USER OPTION SET #1, press YES. ARE YOU SURE, press YES. USER OPTION 1 AT RESET CHANGE, press NO. LOAD OR STORE OPTION SET, press NO.

13) Again, the display will ask “MODIFY CONFIGURATION?” Press NO. 14) The display will ask “CHANGE PHONE NUMBERS?” Press NO. 15) The display will ask “FRONT PANEL FEATURES?” Press NO.


34

3 Metasys with Leased Line Modems - (continued) 16) The display will ask “DIAL STORED NUMBER?” Press NO. 17) The display will ask “DISPLAY STATUS?” Press NO. 18) When the display asks “SELECT TEST?”, you’ve reached the beginning

again. Press the Talk/Data button. The display should return to normal operation mode. For example, it might say “V.34 19200 ON LINE.”

Hardware connections for the Metasys subsystem using leased line modems are displayed schematically below.

��2�)��0.3

4�" 50�$#0��) ��06

��2�7��3

�#��$�01)� �

88��10�

��2,��103

��2(��103

��) ��06�4�" 50��$#0

4�" 50��$#0��) ��06��

��2�� 3

�� 2�� 3

��

��

��

��2�� 3

�� 2�� 3

��

��

��

��

��2�� 3

��2�� 3

��

��

�

��2�� 3

��2�� 3

��

��

�

Figure 4-4. Metasys Connections When Using Leased Line Modems.


35

3 Metasys with Leased Line Modems - (continued)

�$"%&��'80".018� 0��10��

�� !

��

��

��

��

��

��

��

��

��

��

��

��

"#�$��#"#��% &

��'

� " 1"�1�� %"/$09#.� 5�9�9�9�9�9�9�9�9�

�� !

��

��

��

��

��

��

��

��

��

��

��

��

"#�$��#"#��% &

��'

�$"%&��'80".018� 0��10��

�7�� :��080".018� 0�"/$0

2.#��$�01)-��10�3

�1�6�"��10.�5 " 01$0".01�� 0$� 0.

�$#0�

��) ��

��06��

4�" 50��)

��06

�4�" 50

��$#0

��:��0 ��7��80".018� 0�"/$0

2.#��$�01)-��10�3

��

��

Figure 4-5. Metasys connects with UNITY via Leased Line Modems.


36

4 Metasys with Fiber Optic Converter Metasys fiber optic wiring connections to the 300/350 NCM are shown below. The Fiber Driver jumper and switch settings must be set on both Fiber Driver devices for proper operation.

��

��

��

��(�)��*��

��

��

�8��;�4��8��;�4�

��/0��<0��/0��<0�

=

��

(�

�(

>:

�

��(�)��*��

��

�

��

��

�8��;�4�

��/0��<0��/0��<0�

=

��

(�

�(

>:

�

��/0�� %%"/$0

(�)��*��&��+�7#��0�.:�?4�:�?4�:�?�

�)� %�.0 ��(

��>��

��>��

��>��

��

�)� %�.0 ��(

�)� %�.0 ��(

��

(�)��*��&��+�7#��0�.:�?,�:�?4@�:�?�" 50�0$0% AA

�)� %�.0 ��(

AA�" 50.0$0% �� 10�0 1.� �0%"/$0.�B0" 1$0 5 �C�0$0% �0.�� 0. �" 50)��%�"%%#�" 0$6�"..0.1" "C�D.�� " 50�D�01�#��" 50�D$� 5�" 50

Figure 4-6. Cable Pinout Connections for Metasys Fiber Optic Wiring.

37

UNITY 5.8 UNITY/Metasys Index

Metasys Index L

LAN 6 LCG 8 Low Alarm 28 Low Warning 28

M

Map Points 18 Metasys Databases 10 Metasys Objects 7

N

N1 LAN 6 N2 BUS 6 NCM Database 10 Network Control Module (NCM) 6 Normal 28

O

Objects 7 Operator Workstation 6

P

Panel Alarm 28 PIDL 8 Point

Command 26, 27 Request Status 24, 25

Point Alarms 28 Point Objects 8 Points

Delete 20 Map 18, 19

Print Group Information 22

R

Read Points 17 Request Point Status 24, 25

S System

Add 14, 15 Delete 16

T

TOD 22 Trouble 28

U

Unmapped Point Alarm 28

A

Accumulator (ACM) 9 Add a Metasys System 14, 15 Alarm 28 Analog Data (AD) 9 Analog Inputs (AI) 8 Analog Outputs(AO) 9 ARCNET 6

B

Binary Data (BD) 9 Binary Inputs (BI) 9 Binary Output (BO) 9

C

Command a Binary/Digital Point 26, 27 Command an Analog Point 27 Communication Alarm 28 Control Objects 8 Control System Objects 7 Controller Database 10

D

Data Definition Language (DDL) 15 Databases 10 Delete a Group 21 Delete a Metasys System 16 Delete Points 20 Disable the Subsystem 12

E

EIAs 28 Enable the Subsystem 11

F

FMS 15

G

Global Database 10 Graphic Program Language (GPL) 15 Group

Delete 21 Print Information 22

H

Hardware Objects 7 High Alarm 28 High Warning 28

Index UNITY/Metasys UNITY 5.8

38

unity/metasys supplement

Documents