6295125

Metasys Connectivity Technical Manual 629.5Metasys Integrator Section

Technical BulletinIssue Date 0900

2000 Johnson Controls, Inc. www.johnsoncontrols.comCode No. LIT-6295125

TECHNICAL BULLETIN

Metasys Integrator 300 Series Point Mapping

Metasys Integrator 300 Series Point Mapping....................................3

Introduction.........................................................................................................3

Key Concepts......................................................................................................4

Related Information ........................................................................................................ 4

Integration Limitations..................................................................................................... 4

MIG Hardware Object ..................................................................................................... 4

Point Types..................................................................................................................... 5

Auto Restore Configuration............................................................................................. 6

Metasys NCM Standard Object Mapping ........................................................................ 6

Metasys NCM CS Object Mapping ................................................................................. 7

Troubleshooting .................................................................................................8

Metasys Integrator2

Metasys Integrator 300 Series Point Mapping 3

Metasys Integrator 300 SeriesPoint Mapping

IntroductionThis document explains how to incorporate the vendor point data intoa Metasys Network after the Metasys Integrator 300 Series unithas been installed and commissioned.

Use this document with the vendor-specific application notes, whichcontain specific details about integrating vendor equipment (e.g., cablepinouts and point mapping tables). For information on vendorcontrollers, see vendor documentation (obtainable from your vendorrepresentative).

This technical bulletin outlines the concepts and issues you shouldconsider when integrating points into a Metasys system.

Your main source of point mapping information is the vendor-specificapplication note. For example, point mapping information for Carrierequipment is in the Metasys Integrator Carrier ApplicationApplication Note under Point Mapping Tables.

For information on setting up a Metasys Integrator site and using theMetasys Integrator unit, refer to Table 1.

Metasys Integrator4

Key Concepts

Related Information

Table 1 describes where to find information on how to perform tasksother than doing network setup for a Metasys Integrator unit.

Table 1: Related Information

Description Tab DocumentMounting an EN-EWC25-0Enclosure

UPM Universal Packaging Module TechnicalBulletin (LIT-6363070, FAN 636.3)

Installing a Metasys IntegratorUnit

Metasys Integrator Metasys Integrator 300 Series InstallationTechnical Bulletin (LIT-6295122, FAN 629.5)

Commissioning a MetasysIntegrator Unit

Metasys Integrator Metasys Integrator 300 SeriesCommissioning Technical Bulletin(LIT-6295124, FAN 629.5)

Specific Vendor ApplicationInformation

Metasys Integrator The appropriate vendor application note(FAN 629.5)

Integration Limitations

The Metasys Integrator vendor ports can connect to one vendor familyper vendor port.

Each Metasys Integrator unit can support up to 256 addressed vendordevices. This limit is a theoretical limit based on N2 address space(allocated memory). To view available allocated memory, see theAdvanced Diagnostics screen of the Metasys Integratorcommissioning interface. Also consider the memory limitations of thenetwork controller (such as Network Control Module [NCM] or N30Supervisory Controller).

MIG Hardware Object

Before defining points at a network controller, you must define theN2OPEN Metasys Integrator hardware object as type MIG. MIG, asubset of N2OPEN objects, is the generic name for all vendor devicesconnected through the Metasys Integrator unit.


Point Types

A vendor points Network Point Type (NPT) specifies the objectspoint type (such as AI [Analog Input], BD [Binary Data]). The vendorpoints Network Point Address (NPA) specifies the objects pointaddress (1256). The NPT and NPA for each point are listed in thevendor-specific application note under Point Mapping Tables.

Table 2 lists the characteristics of the Metasys Integrator unit pointtypes.

Table 2: Point Type Mapping

Hardware Point Types PointAddressRange

MetasysSystemAdjust

Command/Override*

Can Mapto

MetasysObject:

Can Map toCompanion

Point:

Can Map toN30 Object:

AI Analog Input 1 to 256 Yes AI, CS AI, AO AI, MSI, AO, MSO

BI Binary Input 1 to 256 Yes BI, CS BI, BO BI, BO

AO Analog Output 1 to 256 Yes AOS, CS AO AO, MSO

BO Binary Output 1 to 256 Yes BO, CS BO BO

ADF Analog Data Float 1 to 256 Yes CS only AI, AO AI, MSI, AO, MSO

ADI Analog Data Integer 1 to 256 Yes CS only AI, AO AI, MSI, AO, MSO

BD Binary Data 1 to 256 Yes CS only AI, AO, BI, BO AI, MSI, AO,MSO, BI, BO

* Though all points can be overridden and adjusted, only commands to AO and BO points are actuallysent to the vendor controller.

Note: Control System (CS)Analog Output Setpoint (AOS)Multi-State Input (MSI)Multi-State Output (MSO)

Vendor AO and BO Points

After commanding a vendor controllers AO point, the resulting valueof that point may not match the value originally sent from the Metasyscontroller for the following reasons:

The value sent was outside the safety limits in the device.

The value sent was outside the limits specified in the VendorCommunication Table (VCT). In this case, the command is stillsent. However, for low values, the low limit value is sent; and forhigh values, the high limit value is sent.

A control process in the vendor controller may change the value.

Metasys Integrator6

After commanding a vendor controllers BO point, the resulting valueof that point may not match the value originally sent from the Metasyscontroller for the following reasons:

A control process in the vendor controller may be in control of thevalue.

The output may be locally controlled.

Note: Release commands are not sent to the vendor controllerunless otherwise specified in the vendor application note.

Auto Restore Configuration

The Metasys NCM CS objects, Companion BO points, andN30 objects automatically command objects to their last commandedvalue whenever a device is brought online (unless the command hasbeen released). This feature is known as auto restore.

To prevent inadvertently commanding objects (in particular,commands that clear counts, reset devices, or write to EEPROM), donot map these points to auto restorable objects or points.

At a Metasys NCM, you can take several steps to prevent objects frombeing auto restored. For CS models, if the output points must bemapped, set both Priority 2 and Priority 3 command flags to N. ForAOS and BO objects, set the auto restore attribute to No. Also, sincethe Metasys Integrator unit returns the actual value for outputs (unlessotherwise documented), set the Initial Value attribute to None. Formore information, see the Analog Output Setpoint (AOS) ObjectTechnical Bulletin (LIT-636084) and the Binary Output (BO) ObjectTechnical Bulletin (LIT-636090) in the Metasys Network TechnicalManual (FAN 636).

Metasys NCM Standard Object Mapping

The advantage of mapping each point to a standard object is greaterversatility for point monitoring. AI objects allow alarm and/or warningnotification. BI objects allow alarm and/or trouble notification.

Using BI objects when the value triggers a process, and AI objectswhen the status triggers a process, improves system performance. Forspecific procedures and object descriptions, see the object technicalbulletins in the Metasys Network Technical Manual (FAN 636).


Metasys NCM CS Object Mapping

CS objects often represent an entire device. They also use less memoryin the NCM than a corresponding group of standard objects.

The Metasys Integrator Tables and Models CD-ROM includes areference software model, in DDL syntax, for each vendor application.The models typically have the same name as the .VCT files to whichthey correspond, but they have a .DDL extension. For example, for theMcQuay centrifugal chiller application (SG_CENC.VCT), the modelis SG_CENC.DDL. The vendor-specific application note lists theprovided software model under the Metasys Network Setup section ofeach application

You can use the provided models as a basis for CS objects, or createyour own models. For information on defining software models andCS objects, see the Control System (CS) Object Technical Bulletin(LIT-636102) in the Metasys Network Technical Manual (FAN 636).

Metasys Integrator8

TroubleshootingTable 3 lists some possible network setup problems and solutions.

Table 3: Possible Network Setup Problems

Condition Problem SolutionMetasys controller is notcommunicating with theMetasys Integrator unit.

N2 Bus setup is incorrect. Verify that the N2 polarity iscorrect (see N2 CommunicationsBus Technical Bulletin[LIT-636018]).

Verify that there is an End-of-Line(EOL) device, and ensure that it iscorrectly set.

Verify that N2 addresses havebeen correctly assigned (forexample, no double-mappedaddresses).

The vendor device does notcome online.

The N2 address at the NCM doesnot match the N2 address definedat the Metasys Integrator unit.

Check the N2 addresses defined onthe Network Modify/Add/Deletescreens of the Metasys Integratorsystem.

The Metasys Integrator unit is notcommunicating with the vendordevice.

Verify that the vendor device iscommunicating (see Troubleshootingin the Metasys Integrator 300 SeriesCommissioning Technical Bulletin[LIT-6295124]).

One or more object valuesare unreliable.

Metasys NCM sets any valuelarger than 1 million as unreliable.Also, any value that has moresignificant digits than allowed bythe display field on the focuswindow displays an unreliablevalue.

Verify that the analog value islarger than 1 million, or themaximum value allowed on thefocus window, via the Show PointData screen. Check to see if thereis an alternate point in the pointlisting for the .VCT that scales thevalue. For example, the samepiece of data may be mapped totwo different points in the .VCT.

If there is no alternate point,report the problem to the FieldSupport Center.

Operator Workstation decimalpoint placement value is incorrect.For example, if the value is 1000and the decimal place is 4, thevalue displays as unreliable at theMetasys NCM.

Determine the correct decimal pointplacement for the range of the point.

The wrong point is mapped.One or more object valuesare incorrect or one or moreobjects are unreliable.

The point does not exist.

Verify that the correct point ismapped at the Metasys NCM. Notethat only those points that actuallyexist at the Metasys Integrator unitare reliable.

Continued on next page . . .


Condition (Cont.) Problem SolutionCommands do not execute. The execution of commands is

restricted by a password at thevendor device.

See the vendor application note forpossible solutions.

Value is commanded outside thevalid range for the point.

Command the object value within thevalid range for the point.

The corresponding point at theMetasys Integrator unit is not anAO or BO point. Only commandsto AO and BO points are sent tothe field device.

If a solution is required, a customapplication must be developed. Thisis possible only if the vendor devicesupports having the correspondingpoint commanded.

Device repeatedly togglesonline and offline.

Vendor device may not supportcommands.

If you are sending commands, verifythat the device is commissioned tosupport commands. Be aware thatthe Auto Restore function of Metasyscontrollers resends commands asdevices report online.

The Metasys NCM may put adevice offline if a point does notexist at the Metasys Integratorunit.

Delete the point from the controllerdatabase.

For further assistance, refer to the Design Considerations andComponent Requirements sections of the vendor documents. If noresolution is determined, call the Field Support Center. To expediteassistance, follow the instructions for collecting screen data prior tomaking the call (refer to Collecting Screen Data in the MetasysIntegrator 300 Series Commissioning Technical Bulletin[LIT-6295124]).

Metasys Integrator10

Notes


Notes

Metasys Integrator12

Notes

www.johnsoncontrols.comControls Group FAN 629.5507 E. Michigan Street Metasys Connectivity Technical ManualP.O. Box 423 Release 9.0Milwaukee, WI 53201 Printed in U.S.A.

Metasys Integrator 300 Series Point MappingIntroductionKey ConceptsTroubleshooting

6295125

Documents

Transcript of 6295125