APPLICATION NOTE JC/85

Transcription

1 Metasys Network Technical Manual 636 App. Notes: Network Communications Section Application Note Issue Date 0401 APPLICATION NOTE JC/85 Gateway Introduction Page 3 Application Details *3 Hardware and Software Requirements 7 Engineering 9 Design Considerations 9 Definition Procedures *10 Troubleshooting Procedures 13 If the JC/85/40 Download Fails *13 If the Gateway NCM Download Fails *13 * Indicates those sections where changes have occurred since the last printing Johnson Controls, Inc. 1 Code No. LIT

2 2 App. Notes: Network Communications JC/85 Gateway

3 Introduction Application Details The JC/85 Gateway is an NCM (Network Control Module) that allows you to control and monitor JC/85/40 points from a Metasys Operator Workstation (OWS). By mapping JC/85/40 points to Analog Data (AD) or Binary Data (BD) objects in the Metasys system, you use the latest technology in your facility without replacing existing equipment. Note: The JC/85 Gateway NCM type does not support the NCM diagnostic mapping explained in N1 Traffic and Diagnostics in the Quick Start section of the Analog Data (AD) Technical Bulletin (LIT ). This document describes the steps for defining JC/85/40 software points on the Metasys system. For details on setting up the JC/85 Gateway, refer to the NCM200 and NCM300 technical bulletins in the Control Modules section of this manual. IMPORTANT: All Analog Data and Binary Data points on the JC/85 Gateway must be mapped to points on the JC/85/40 in order to successfully download the JC/85 Gateway. Command Priority When the Metasys system issues a command to an AD or BD object mapped to a JC/85/40 point, the JC/85 Gateway NCM converts the commands according to the commanded JC/85/40 point type. Here are some general rules that apply to command mapping. Table 1 lists all of the possible Metasys commands and their JC/85/40 equivalents. When the Metasys system issues Alarms, Warnings, Enable, or Disable commands, the JC/85 Gateway does not issue the equivalent command to the JC/85/40 system. The Metasys command priority for all JC/85/40-generated commands is at the Metasys system s manual command priority or equivalent. When the Metasys system issues a Set BD 1 or Set BD 0 command at a Manual 3 priority to a BD object mapped to a JC/85/40 SST point, the JC/85/40 interprets the command and priority as a Manual Start or Stop command at Priority 15. The commanded state does not update the BD Current Value attribute. Instead, the JC/85/40 Change-of-State (COS) updates the BD object s Current Value and Normal State attributes, and performs the appropriate COS analysis. App. Notes: Network Communications JC/85 Gateway 3

4 Table 1: Object Command and Priority Mapping Metasys Object and Command JC/85/40 Command Initial BD Setup value for priority table Set BD 1 BD Start Open (Stop) Set BD 0 BD Stop Close (Start) Set BD 1 BD Start Open (Stop) Set BD 0 BD Stop Close (Start) Override 1 BD Start Open (Stop) Override 0 BD Stop Close (Start) JC/85/40 Point Types SST, OPC (for OPN/CLO) SST, OPC (for OPN/CLO) SST, OPC (for OPN/CLO) SST, OPC (for OPN/CLO) SST/OPC (for OPN/CLO) SST, OPC (for OPN/CLO) SST, OPC (for OPN/CLO) Auto BD SST, OPC (for OPN/CLO) Metasys Feature and Priority Initial Value used to set up value for priority table to Manual 3. Manual or Feature 3. Current Value updated when COS is issued from JC/85/40. Manual or Feature 3. Current Value updated when COS is issued from JC/85/40. Feature 2. Current Value updated when COS is issued from JC/85/40. Feature 2. Current Value updated when COS is issued from JC/85/40. Manual 1. Current Value updated when COS is issued from JC/85/40. Manual 1. Current Value updated when COS is issued from JC/85/40. Next Lower Unlatch BD Reset BIN Initial AD Setup Value for Priority Table ADJ Initial Value used to set up value for priority table to Manual 3. Set AD AD Adjust ADJ Manual 3. Updates Setpoint. Current Value updated when COS is issued from JC/85/40. Set AD AD Adjust ADJ Feature 2. Updates Setpoint. Current Value updated when COS is issued from JC/85/40. Override AD Adjust ADJ Manual 1. Update Setpoint. Current Value updated when COS is issued from JC/85/40. Auto AD ADJ Next Lower Warnings AD Alarms AD Enable Disable AD or BD AD or BD Enable update of value from JC/85/40. Disable update of value from JC/85/40. Override AD ANA or ACM Set Value. Disable update of value from JC/85/40. Auto AD ANA or ACM Enable update of value from JC/85/40. Override 1 BD BIN Set Value. Disable update of value from JC/85/40. Override 0 BD BIN Set Value. Disable update of value from JC/85/40. Auto BD BIN Enable update of value from JC/85/40. JC/85/40 Priority Manual 15 Manual 15 Optimum Start 10 Optimum Start 10 Demand Limit 3 Demand Limit 3 Next Lower 4 App. Notes: Network Communications JC/85 Gateway

5 COS Reporting Date and Time Synchronization The JC/85/40 issues a change-of-state when: the AD or BD object referencing a JC/85/40 point is added, and the JC/85/40 is downloaded. the value of an SST, BIN, or OPC (for OPN/CLO) changes. When the state of the SST, BIN, or OPC (for OPN/CLO) point value changes, the Current Value attribute for the Metasys BD object to which the SST or OPC (for OPN/CLO) point is mapped is automatically updated. an SST or OPC (for OPN/CLO) point is commanded. When an SST or OPC (for OPN/CLO) point is commanded at the JC/85/40 system, the COS updates the Normal State attribute for the Metasys BD object to which the SST or OPC (for OPN/CLO) point is mapped. the value of an ANA, ACM, or ADJ value exceeds the filter increment. If an ANA, ACM, or ADJ point exceeds its defined filter increment, the Current Value attribute for the Metasys AD object to which the ANA, ACM, or ADJ point is mapped is automatically updated. a BIN goes into the Trouble or Alarm state. When a BIN point goes into the Trouble or Alarm state, the Current Value and Status attributes for the Metasys BD object to which the BIN is mapped is automatically updated. the JC/85/40 goes offline. If the JC/85/40 goes offline, all associated AD and BD objects indicate Offline, and a report is issued saying that the JC/85/40 is offline. a mapped JC/85/40 point goes offline or comes online. When a JC/85/40 point goes offline or comes online, the Metasys object to which it is mapped is updated to indicate that it is offline or online. A report for the associated AD or BD object is issued to the Metasys system when a JC/85/40 remote point goes offline. To keep the JC/85/40 and the Metasys systems in sync, the JC/85 Gateway NCM requests the current date and time from the JC/85/40 at 12:03 a.m. each day. The NCM then updates the Metasys system at 12:05 a.m. Note: The O,DAT command at the JC/85/40 I/O device sends a new date and time to the JC/85 Gateway. This command resets the date and time for the Metasys system. App. Notes: Network Communications JC/85 Gateway 5

6 Uploading and Downloading Databases The Metasys database downloads from the Metasys Operator Workstation (OWS). Uploads of the NCM database can also be performed from the Metasys OWS. For detailed instructions on performing a download from the JC/85/40, refer to JC/85 Gateway - User Data (01-12) in the Programming Options section of the JC/85 Software Data Book. For detailed instructions on performing an NCM download from the Metasys system, refer to the Uploading and Downloading Databases section in the Operator Workstation User s Manual (FAN 634) and the Uploading and Downloading Databases Technical Bulletin (LIT ) in the Metasys Network Technical Manual (FAN 636). Downloading to the JC/85 Gateway from the Metasys System A download can be initiated from the Metasys system by performing an NCM download. When a download is initiated from the Metasys system to the JC/85 Gateway NCM, the data is automatically downloaded from the NCM to the JC/85/40 system. Upon receiving the downloaded data, the JC/85/40 automatically initiates an upload of its data back to the JC/85 Gateway NCM. A partial download automatically occurs when an AD or BD object that is mapped to a JC/85/40 point is added to the Metasys system. All downloads to the JC/85/40 set the JC/85/40 points as remote points in the JC/85 Gateway NCM and, in turn, prompts the JC/85/40 system to mark them as public points. A report is generated upon completion of the NCM download. In addition, a report is generated upon a JC/85/40 download completion. Note: If the JC/85/40 trunk is offline, the download from the Gateway automatically occurs when the trunk comes back online. Uploading the JC/85 Gateway NCM Uploading the JC/85 Gateway NCM copies the online NCM database, located at the NCM to the archive NCM database, located in the archive PC (Personal Computer). During the upload, all object and feature databases are uploaded. You cannot upload an individual database; however, when you add an AD or BD object online, perform an NCM upload in order to archive the added object. The Metasys system generates a report when an upload is in progress and another report when the upload is complete. 6 App. Notes: Network Communications JC/85 Gateway

7 Hardware and Software Requirements The JC/85 Gateway NCM is a Metasys N1 node, and it communicates with other NCMs on the Metasys N1 Bus. The JC/85 Gateway NCM has all the software needed to manage the Metasys global database. The software to perform this function is part of the standard Metasys software package documented in the Operator Workstation Technical Bulletin (LIT ) of the Metasys Network Technical Manual (FAN 636). For information on setting up the JC/85 Gateway NCM, refer to the NCM200 and NCM300 technical bulletins in the Control Modules section of Metasys Network Technical Manual (FAN 636). For information on the hardware connection between the JC/85 Gateway NCM and the JC/85/40, refer to JC/85 Gateway - Engineering Data ( ) in the Programming Options section of the JC/85 Software Data Book. App. Notes: Network Communications JC/85 Gateway 7

8 8 App. Notes: Network Communications JC/85 Gateway

9 Engineering Design Considerations When mapping JC/85/40 software points to Metasys objects, keep the following design considerations in mind: The following JC/85/40 patches (obtained from the Facility Management Systems home page on The Advisor) are required to control JC/85/40 points from the Metasys system: Table 2: JC/85/40 Patches Patch No. Maint. No. Log No. Description L2827A Allows the Current Value of a remote SST mapped to a pseudo point to update at the remote system after being started when other starts are already in progress for other points in the same Start group. L2829A Allows non-manual commands to be sent to non-pseudo SST points from a network node even when higher priority commands are pending Allows a change-of-state to be reported for an SST point that doesn t have a feedback point (or if the feedback doesn t follow the command) when the SST is commanded from a logical slave node. Large JC/85/40 databases require more than 2 MB of memory, the standard memory configuration for the NCM300. There can be a maximum of 2500 Reference IDs (RIDs) per NCM. To calculate the number of RIDs for the NCM, use the following equation: Number of Local Objects (ADs and BDs) Number of JC/85/40 Points Referencing Remote Objects + Number of Devices on the Network (OWSs, printers, and NCMs) Total Number of RIDs on the NCM A point can be latched at either the JC/85/40 headend or at the Metasys system, but not both. If the point is defined as latched at both systems, two unlatch commands are required (one at each system). The Warning Delay parameter in the Metasys AD Object Definition window is the same as the delay time to be used on the Adjust command at the JC/85/40. If the object status is unreliable, the object displays???? even if the object is still online. App. Notes: Network Communications JC/85 Gateway 9

10 If an SST change-of-state occurs from the JC/85/40, the Current Value and Normal State attribute of the BD object are updated; however, the Normal State attribute of the BD object does not automatically refresh in the Focus window. You must manually refresh the Focus window. An Adjust command to an AD object automatically refreshes the Setpoint attribute. A BD object mapped to a JC/85/40 point cannot be assigned as a Demand Limiting or Load Rolling load. Definition Procedures To map a JC/85/40 software point to a Metasys AD or BD object: 1. Ensure that the software point is defined at the JC/85/40 headend. Refer to JC/85 Gateway - Engineering Data in the Programming Options section of the JC/85 Software Data Book for details on defining JC/85/40 software points. IMPORTANT: A field point within the JC/85/40 can be marked as a remote point or a public point, but not both. 2. Download the self-extracting 8540DDL.EXE file from the Facility Management Systems home page on The Advisor. a. Create a L3.DAT file. b. Type L3DDL /G to convert the JC/85/40 points into DDL source code for the AD and BD objects. Detailed instructions for creating the L3.DAT file and using the L3DDL conversion tool can be found in its Readme file. Note: You can manually define the object, as well, but using the L3DDL conversion tool ensures that the objects are defined correctly. (If an object is not defined, or is not defined correctly, the Download of that remote point fails.) The conversion tool automatically defines the following parameters; however, if you add the AD or BD online using an Operator Workstation, you must: replace all spaces with the underscore character ( _ ) replace all slash characters ( / ) with a right bracket ( ] ) In addition, the field instructions below must be followed: The Object Name field must contain the JC/85/40 System Type (F, S, or H), the JC/85/40 Point Type (BIN, SST, ANA, ADJ, INT, ACM, or OPC for OPN/CLO), and the Level 3 name, separated by an underscore, for example, HANA_OAT. If the object name contains a blank space, replace it with a dash (-). 10 App. Notes: Network Communications JC/85 Gateway

11 The System Name field must contain the JC/85/40 Level 1 and Level 2 names, separated by an underscore, for example, LIBR_FAN. If the Level 1 or Level 2 name contains a blank space, replace it with a dash (-). The Alarm Delay field (BD only) must equal zero when mapping to BIN point types and non-zero when mapping to an SST or OPC (for OPN/CLO) point types. The Warning Delay field (AD only) must equal zero when mapping to ANA and ACM point types and non-zero when mapping to an ADJ point type. (The JC/85/40 uses the AD s warning delay time value as the ADJ feedback timer.) Notes: The JC/85 Gateway NCM type does not support the NCM diagnostic mapping explained in N1 Traffic and Diagnostics in the Quick Start section of the Analog Data (AD) Technical Bulletin (LIT ). The Delay All Alarms field and the Adjust Disable field are set to No internally for all BD, AD, MSD objects defined at the Network Port. The following table lists the types of supported objects and the JC/85/40 points they can be mapped to. The JC/85/40 Intercom and 3Mode point types are not supported. Table 3: Supported Objects with JC/85/40 Points Metasys Object Type JC/85/40 Point Type Analog Data (Input) Analog Data (Output) Binary Data (Input) Binary Data (Output) ANA, ACM ADJ BIN SST, OPC (for OPN/CLO) Note: The Trouble condition is reported for supervised FPU points (BIS, BIF, and SST-102); however, this does not make the JC/85 Gateway NCM Underwriter s Laboratories, Inc. (UL) Listed, either for fire (UL 864) or security (UL 1076). 3. Use DDL to define the JC/85 Gateway NCM, PC group, and system in the Global file. For details on defining the NCM, PC groups, and systems, refer to the DDL Programmer s Manual (FAN 630). 4. Compile the DDL Global file to generate the NCM, PC group, and system database. 5. Compile the DDL NC file to generate the AD and BD objects. 6. Perform the NCM code and data download to enable the points on the JC/85/40 side. App. Notes: Network Communications JC/85 Gateway 11

12 12 App. Notes: Network Communications JC/85 Gateway

13 Troubleshooting Procedures If the JC/85/40 Download Fails If the Gateway NCM Download Fails If a download to the JC/85/40 fails, check the following: Are the objects on the Metasys system already remote points on the JC/85/40? Is the JC/85/40 point defined on the JC/85/40? If the Download to the Gateway NCM fails, check the following: Did you use the correct JC/85/40 system type, point type, and Level 3 name to define the object name for the Metasys object? Are the point type and Level 3 name separated by an underscore? HANA_ OAT Point Type Level 3 Name System Type Underscore Name1 Figure 1: System Type, Point Type, and Level 3 Name Did you use the correct JC/85/40 Level 1 and Level 2 name to define the Metasys system name for the Metasys object? Are the Level 1 and Level 2 names separated by an underscore? LIBR _ FA N Level 1 Name Underscore Level 2 Name Name2 Figure 2: Level 1 and Level 2 Name App. Notes: Network Communications JC/85 Gateway 13

14 Are any of the JC/85/40 points that you converted Intercom points? If so, delete them from DDL. Are any of the Metasys AD objects diagnostic mapping objects? If so, delete those objects. Refer to N1 Traffic and Diagnostics in the Quick Start section of the Analog Data (AD) Technical Bulletin (LIT ). 14 App. Notes: Network Communications JC/85 Gateway

15 Notes App. Notes: Network Communications JC/85 Gateway 15

16 Notes Controls Group FAN E. Michigan Street Metasys Network Technical Manual P.O. Box 423 Release Milwaukee, WI Printed in U.S.A. 16 App. Notes: Network Communications JC/85 Gateway