Magnitude TM Chiller Unit Controller Protocol Information

Transcription

1 Engineering Data ED Group: Controls Part Number: ED Date: April 2010 Supersedes: New Magnitude TM Chiller Unit Controller Protocol Information Networks (MS/TP, IP, Ethernet) Networks Daikin McQuay Magnitude Magnetic Bearing Centrifugal Chiller, Single- Compressor Model WME 2010 McQuay International

2 Table of Contents Networks (MS/TP, IP, Ethernet) Networks... 1 Table of Contents... 2 REVISION HISTORY...4 SOFTWARE REVISION...4 REFERENCE DOCUMENTS...4 NOTICE...4 LIMITED WARRANTY...4 Introduction... 5 UNIT CONTROLLER DATA POINTS...5 PROTOCOL DEFINITIONS...5 Basic Protocol Information... 6 SETTING UNIT CONTROLLER COMMUNICATIONS PARAMETERS...6 BACNET NETWORKS...6 MAGNITUDE CHILLER UNIT CONTROLLER DEVICE OBJECT...8 Network Considerations ACCESS TO PROPERTIES...11 BACNET NETWORKS...11 BACNET DEVICE MANAGEMENT...13 Configuring the Unit Controller NETWORKS...15 Typical Application: Minimum Integration 20 SET UP THE UNIT CONTROLLER FOR NETWORK CONTROL...20 DISPLAY IMPORTANT DATA POINTS...20 ALARMS...21 Protocol Point Summary Protocol Point Summary NETWORK OUTPUT VARIABLES...25 NETWORK INPUT VARIABLES...26 NETWORK CONFIGURATION PARAMETERS...27 Detailed Data Point Information ACTIVE SETPOINT...28 ACTUAL CAPACITY...28 ALARM DIGITAL OUTPUT...29 APPLICATION VERSION...29 CAPACITY LIMIT...29 ACTIVE CAPACITY LIMIT OUTPUT...30 CAPACITY LIMIT SETPOINT - NETWORK...30 CHILLER ENABLE...31 CHILLER ENABLE OUTPUT...31 CHILLER ENABLE SETPOINT...32 CHILLER CAPACITY LIMITED...32 CHILLER LOCAL/NETWORK...34 CHILLER LOCATION CHILLER MODE CHILLER MODE OUTPUT CHILLER MODE SETPOINT - NETWORK CHILLER MODEL CHILLER ON OFF CHILLER STATUS CLEAR ALARM NETWORK COMPRESSOR AVERAGE CURRENT COMPRESSOR AVERAGE VOLTAGE COMPRESSOR DISCHARGE REFRIGERANT PRESSURE COMPRESSOR DISCHARGE REFRIGERANT TEMPERATURE COMPRESSOR DISCHARGE SATURATED REFRIGERANT TEMPERATURE COMPRESSOR PERCENT RLA COMPRESSOR POWER COMPRESSOR RUN HOURS COMPRESSOR SELECT COMPRESSOR STARTS COMPRESSOR SUCTION SATURATED REFRIGERANT TEMPERATURE COMPRESSOR SUCTION REFRIGERANT PRESSURE COMPRESSOR SUCTION REFRIGERANT TEMPERATURE CONDENSER ENTERING WATER TEMPERATURE CONDENSER FLOW SWITCH STATUS CONDENSER LEAVING WATER TEMPERATURE CONDENSER PUMP RUN HOURS CONDENSER REFRIGERANT PRESSURE CONDENSER SATURATED REFRIGERANT TEMPERATURE CONDENSER WATER FLOW RATE CONDENSER PUMP STATUS COOL SETPOINT - NETWORK COOL SETPOINT CURRENT DATE & TIME DEFAULT VALUES EVAPORATOR ENTERING WATER TEMPERATURE EVAPORATOR FLOW SWITCH STATUS ED 15117

3 EVAPORATOR LEAVING WATER TEMPERATURE...51 EVAPORATOR PUMP RUN HOURS...52 EVAPORATOR PUMP STATUS...52 EVAPORATOR WATER FLOW RATE...53 FILE DIRECTORY ADDRESS...53 HEAT RECOVERY ENTERING WATER TEMPERATURE...53 HEAT RECOVERY LEAVING WATER TEMPERATURE...54 HEAT SETPOINT - NETWORK...54 HEAT SETPOINT...55 ICE SETPOINT - NETWORK...55 ICE SETPOINT...55 MAXIMUM SEND TIME...56 MINIMUM SEND TIME...56 OBJECT STATUS...57 OBJECT REQUEST...58 OUTDOOR AIR TEMPERATURE...59 PUMP SELECT...59 RECEIVE HEARTBEAT...60 RUN ENABLED...60 SOFTWARE IDENTIFICATION (MAJOR VERSION)...61 SOFTWARE IDENTIFICATION (MINOR VERSION)...61 UNITS...61 Alarms ALARM CLASSES...63 BACNET ALARM HANDLING...63 Clearing Alarms BACNET ALARM MESSAGES...65 Alarms CURRENT ALARM...67 Clearing Alarms ALARM MESSAGES...68 Appendix A: Protocol Implementation Conformance Statement (PICS)...70 BACNET PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT...70 PRODUCT DESCRIPTION...70 BACNET STANDARDIZED DEVICE PROFILE..70 BACNET INTEROPERABILITY BUILDING BLOCKS (BIBBS) SUPPORTED...70 STANDARD OBJECT TYPES SUPPORTED...72 DATA LINK LAYER OPTIONS...74 SEGMENTATION CAPABILITY...74 DEVICE ADDRESS BINDING...74 NETWORKING OPTIONS...74 CHARACTER SETS SUPPORTED...74 NON-BACNET EQUIPMENT/NETWORK(S) SUPPORT...74 Index of Detailed Point Information...75 ED

4 Revision History ED15117 April 2010 Preliminary release. Software Revision This edition documents all versions of the standard Magnitude Chiller Unit Controller software and all subsequent revisions until otherwise indicated. You can determine the revision of the application software from the display. The version is located on the Service screen. can also read the software revision by reading the Application_Software_Version property of the Device Object. Reference Documents Company Number Title Source McQuay International OM 1034 McQuay International IM 963 McQuay International IM 965 American Society of Heating, Refrigerating and Air-Conditioning Engineers ANSI/ ASHRAE Magnitude Frictionless Centrifugal Chiller Operation and Maintenance Manual Magnitude Frictionless Centrifugal Chiller, Communication Module (MSTP, IP/Ethernet) Installation Manual Magnitude Frictionless Centrifugal Chiller, Communication Module Installation Manual A Data Communication Protocol for Building Automation and Control Networks LonMark Interoperability Association G LonMark Layers 1-6 Interoperability Guidelines, Version LonMark Interoperability Association LonMark Interoperability Association G LonMark Application Layer Interoperability Guidelines, Version _10 LonMark Functional Profile: Chiller, Version Echelon Corporation G FTT-10A Free Topology Transceiver Users Guide Notice 2010 McQuay International, Minneapolis MN. All rights reserved throughout the world McQuay International reserves the right to change any information contained herein without prior notice. The user is responsible for determining whether this product is appropriate for his or her application. The following are trademarks or registered trademarks of their respective companies: from American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. Echelon,, LONMARK, and LonTalk from Echelon Corporation, Windows from Microsoft Corporation, and McQuay, Daikin McQuay, and Magnitude from McQuay International. Limited Warranty Consult your local McQuay Representative for warranty details. Refer to Form Y. To find your local McQuay Representative, go to 4 ED 15117

5 Introduction This document contains the necessary information you need to incorporate a Daikin McQuay Magnitude Chiller Unit Controller into a building automation system (BAS). It lists all properties, variables, and corresponding Magnitude Chiller Unit Controller data points. It also contains the Protocol Implementation Conformance Statement (PICS). and terms are not defined. Refer to the respective specifications for definitions and details. Unit Controller Data Points The Magnitude Chiller Unit Controller contains data points or unit variables that are accessible from three user interfaces: the unit controller OITS panel, a network (/IP, Ethernet, or MS/TP), or a network. Not all points are accessible from each interface. This manual lists all important data points and the corresponding path for each applicable interface. Refer to OM 1034 (available on for display details. This document contains the network details necessary to incorporate the Magnitude Chiller Unit Controller into the network. Protocol Definitions The Magnitude Chiller Unit Controller can be configured in either an interoperable or network. The unit controller must have the corresponding communication module installed for network integration (see Reference Document section for corresponding part numbers). There are three communication modules: IP/Ethernet, MS/TP (Master/Slave Token Passing), and. Protocol is a standard communication protocol for Building Automation and Control Networks developed by the American National Standards Institute (ANSI) and American Society of Heating, Refrigeration and Air-conditioning Engineers (ASHRAE) specified in ANSI/ASHRAE standard It addresses all aspects of the various systems that are applied to building control systems. provides the communication infrastructure needed to integrate products manufactured by different vendors and to integrate building services that are now independent. The Magnitude Chiller Unit Controller is tested according to the Testing Laboratory (BTL) Test Plan. It is designed to meet the requirements of the Standard (ANSI/ASHRAE ) as stated in the Protocol Implementation and Conformance Statement (PICS). However, it is not BTL listed. The PICS are located at the end of this manual or the separate PICS document, ED (available on Networks A control network specification for information exchange built upon the use of the LonTalk protocol for transmitting data developed by the Echelon Corporation. LonTalk Protocol A protocol developed and owned by the Echelon Corporation. It describes how information should be transmitted between devices on a control network. LonMark Certification LonMark certification is an official acknowledgement by the LonMark Interoperability Association that a product communicates using the LonTalk protocol and transmits and receives data per a standard LonMark functional profile. The communication module is LonMark 3.4 certified in accordance with the Chiller functional profile. ED

6 Basic Protocol Information Setting Unit Controller Communications Parameters There are 12 communication parameters involved in setting up the unit controller for proper communication with the three communication module options ( IP/Ethernet, MS/TP, ). These parameters are set differently depending on which communication module is ordered and shipped with the unit. The table below lists the three possible sets of default parameter settings. Not all the parameters apply to all the module options. All parameters, except for Receive Heartbeat, are configurable via the unit controller display. The boldface settings can only be configured via the unit controller OITS (Operator Interface Touch Screen). See Magnitude Chiller Unit Controller Operation Manual, OM 1034, for details. The items in parenthesis indicate whether the parameter is Read-Only (R) or Read/Write (W) from the network. Communication Parameter Settings Parameter Name IP MS/TP Ethernet IP Address N/A N/A N/A IP Subnet Mask N/A N/A N/A Default Gateway Address None N/A N/A N/A UDP Port N/A N/A N/A MSTP MAC Address N/A 1 N/A N/A MSTP Baud Rate N/A N/A N/A Device Instance Number (W) N/A N/A Max APDU Length (R) N/A Device (W) Magnitude 3 Magnitude 3 Magnitude 3 N/A Max Master (W) N/A 127 N/A N/A Max Info Frames (W) N/A 5 N/A N/A APDU Retries (W) 3 3 N/A N/A APDU Timeout (W) N/A N/A Receive Heartbeat 1 N/A N/A N/A 0Sec 1. All parameters, except for Receive Heartbeat, are configurable via the OITS panel. 2. If the IP Address is set to from the unit controller OITS panel or through the network, DHCP addressing will be enabled and the IP address will be requested from the network DHCP server. 3. Device value must be unique on the network. Networks Compatibility The Magnitude Chiller Unit Controller is tested according to the Testing Laboratory (BTL) Test Plan. It is designed to meet the requirements of the Standard (ANSI/ASHRAE ) as stated in the Protocol Implementation and Conformance Statement (PICS). However, it is not BTL listed. The PICS is located at the end of this manual or the separate PICS document, ED (available on Objects Magnitude Chiller Unit Controllers incorporate standard object types (i.e., object types defined in the Standard) that conform to the Standard. Each object has properties that control unit variables or data points. Some object types occur more than once in the Magnitude Chiller Unit Controller; each occurrence or instance has different properties and controls different unit variables or data points. Each instance is designated with a unique instance index. Some properties can be adjusted 6 ED 15117

7 (read/write properties, e.g., setpoints) from the network and others can only be interrogated (read-only properties, e.g., status information). Each data point accessible from a network is described with a table that gives the Object Identifier,, Full Reference or path, and the Name enumeration of the property. Example of Data Point Binary Output 4 5 Present Value 85 AlarmDigitalOutput Property Values 0 = No Alarm 1 = Alarm s are each designated with an Object type as defined in the specification. The first column of the data point definition gives the object type. This object happens to be Alarm Digital Output. The object identifier is a property of the object that you can read from the object. The name of the property is Object_Identifier and the property identifier is 75. Each object in the unit controller has a unique identifier. object identifiers are two-part numbers of data type. The first part identifies the object type (the first 10 bits of the 32-bit [See ANSI/ASHRAE A Data Communication Protocol for Building Automation and Control Networks]). The first column of the data point definition gives the object type. The second part identifies the instances of that particular object type (the last 22 bits of the 32-bit ). The object identifier is shown in the data points listing as two numbers. The first number is shown in the Type ID column and designates the Object type enumeration. The second number is shown in the Instance column and designates the instance of that particular object type. The object identifier is a property of the object that you can read from the object code. The name of the property is Object_Identifier and the property identifier is 75. The ASHRAE specification reserves the first 128 numbers for ASHRAE defined objects. Manufacturers may define additional object types and assign a number above 127 as long as they conform to the requirements of the ASHRAE specification. Each object also has a name. s are character strings. The object name is a property of the object that you can read from the object. The name of the property is Object_Name and the property identifier is 77. Objects are sometimes referred to as an Object Type and Instance Number as they are in the specification. The example object above would be: Binary Output, Instance 5. Each object has a number of properties or attributes. Each property has a unique identifier of data type. Property identifiers are an enumerated set; a number identifies each member. The enumeration number is shown in the Property ID column. In the example above the property identifier is 85. ED

8 Property Name Each property also has a unique name. Property names are character strings and shown in the Property Name column. In the example above the property name is Present Value. The is the name of the object in the device. s must be unique within each device. In the example above the object name is AlarmDigitalOutput. Enumerated Values Some properties are standard data types and some are enumerated sets. If the property value is an enumerated set, all enumerated values and corresponding meaning are given in the Enumeration column of the data point listing. Magnitude Chiller Unit Controller Device Object Each -compatible device can only have a single Device Object. Device The Magnitude Chiller Unit Controller Device uniquely specifies the unit within the network. The device object type for all devices is fixed by ASHRAE at 8. Therefore the device object instance number must be unique. The device object instance will be read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the device object instance parameter during runtime. If the device object instance is changed at the controller during run-time, the update will be automatically applied to the communication module as soon as the change is received. The allowable range of values for the device object instance will be 0 to (The value is reserved by BTL for reading a device s object id.) If a value greater than is read from the controller, the following default value will be used: Default device object instance: address* *Address = the last two octets of the MAC Address For example: MS/TP: 3023 Ethernet: ( F75A) /IP: CDB ( ) The device object identifier can be read from the unit controller. The name of the property is Object_Identifier and the property identifier is 75. Changing the device object ID may affect the operation of other devices on the network that have previously discovered the device. The object instance number can be changed via the unit controller OITS panel.! CAUTION If another device in the network already has this object identifier (instance number), you must change the instance number of one device object, so that all devices in the network have a unique device identifier. Device The Device uniquely specifies a device in the network. It must be unique in the network. The device object name will be read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the device object name parameter during run-time. If the device object name is changed at the controller during runtime, the update will be automatically applied to the 8 ED 15117

9 communication module as soon as the change is received. The allowable range of characters for the device object name will be 1 to 31 characters. If an empty string is read from the controller, the following default name will be used: Default device object name: MTE Chiller UCA - address* *Address = the MAC Address For example: MS/TP: MTE Chiller UCA-23 Ethernet and /IP: MTE Chiller UCA Note: If the constructed name is longer than 31 characters, the numeric portion of the name will be shortened to fit the name into the 31 character limit. The Device Object name is also available to the network in the device. The property name is Object_Name and property identifier is 77. Changing the device object name may affect the operation of other devices on the network that have previously discovered the device. The object name can be changed via the unit controller OITS panel. Device Object Properties The device object contains many other informative properties as shown in Table 1. Items in bold are configurable via the network. Table 1. Magnitude Chiller Unit Controller Device Object Properties Default Value Data Type 75 Device, variable ObjectIdentifier 77 Magnitude Character String Object Type 79 8 ObjectType System Status 112 DeviceStatus Vendor Name 121 McQuay International Character String Vendor Identifier Unsigned 16 Model Name 70 WME Character String Firmware Revision 44 variable Character String Application Software Version 12 variable Character String Location 58 Character String Description 28 McQuay Chiller Character String Protocol Version 98 1 Unsigned Protocol Revision Unsigned Protocol Services Supported 97 readproperty, readpropertymultiple, writeproperty, writepropertymultiple, devicecommunicationcontrol, timesynchronization, who-has, who-is, utctimesyncronization, ServicesSupported ED

10 Default Value Data Type reinitializedevice Protocol Object Types Supported 1 96 AI, AO, AV, BI, BO, BV, Device, ObjectTypesSupported MSI, MSO, MSV Object List 76 Sequence of ObjectIdentifer Max APDU Length Accepted (IP) / 480 (MS/TP) Unsigned 16 Segmentation Supported 107 None Segmentation APDU Timeout Unsigned Number of APDU Retries 73 3 Unsigned Max Master (Range: ) Unsigned Max Info Frames 63 5 (Range: 1.. 5) Unsigned Device Address Binding 30 Sequence of AddressBinding Database Revision Unsigned Local Time 2 57 variable (read from the controller) Time Local Date 2 56 variable (read from the controller) Date UTC Offset (Range: ) Integer Daylight Savings Status 24 0 (False) Boolean 1. While the Magnitude Chiller Unit Controller supports all shown object types, not all object types are used. See the Object List for details. 2. The device properties will be read-only. The controller values are writable from via the TimeSynchronization services. 10 ED 15117

11 Network Considerations Access to Properties Object properties are accessible from the network by specifying the device object identifier, object identifier, and the property identifier. To access a property, you must specify the object identifier including the device object identifier or the object name including the device object name and the property identifier. Networks The communication module supports three separate data link layers: MS/TP Ethernet /IP Only one data link layer may be used at one time. During initialization, the communication module reads a parameter in the Magnitude Chiller Unit Controller to select the data link layer. If the value read is not one of the supported data link layers, the communication module initialization loops in this phase of the initialization until a supported data link layer value is read from the unit controller. The communication module s active data link layer may not be changed at run-time. If the unit controller parameter is changed during run-time, the communication module requires a reset in order to re-initialize with the new data link layer selection. The different data link layers have different parameters. All parameters that require configuration are read from the unit controller by the communication module via the unit controller OITS panel. The communication module reads only those parameters relevant to the selected data link layer. During initialization, the communication module must read a complete set of valid parameters for the network layer and selected data link layer before proceeding to build a set of objects for the device. Ethernet Communications Parameters None of the Ethernet Data Link Layer or Physical layer parameters require configuration. /IP Communications Parameters The key parameters for setting up /IP are described in the following sub-sections. The parameters are accessible and configurable via the unit controller OITS panel. They are not accessible from the network. IP Address The IP address is read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module can be configured for Dynamic Host Configuration Protocol (DHCP) addressing by setting the IP Address to using the unit controller OITS panel. The communication module continues to poll the IP address parameter during run-time. If the IP address is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. The validity of the IP address is verified against the Subnet Mask. If the address is not valid, /IP communications cannot be established and the device does not initiate or respond to messages. If the IP address is changed at run-time and the IP address is not valid, /IP ED

12 communications are disabled. However, once a valid IP address is received, /IP communications are then enabled. Changing the IP address may affect the operation of other devices on the network. This parameter can only be accessed and configured via the unit controller OITS panel. Subnet Mask The Subnet Mask is read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the Subnet Mask parameter during run-time. If the Subnet Mask is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. The validity of the Subnet Mask is verified against the IP address. If the Subnet Mask is not valid, the communication module does not enable /IP communications and the device does not initiate or respond to messages. If the Subnet Mask is changed at runtime and is not valid, the /IP communications are disabled. However, once a valid Subnet Mask is received, /IP communications are then enabled. Changing the Subnet Mask may affect the operation of other devices on the network. This parameter can only be accessed and configured via the unit controller OITS panel. UDP Port The UDP Port is read from the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the UDP Port parameter during run-time. If the UDP Port is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. Changing the UDP Port may affect the operation of other devices on the network. This parameter can only be accessed and configured via the unit controller OITS panel. Default Gateway Address The default gateway address is read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the default gateway address parameter during run-time. If the default gateway address is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. Modifying the default gateway address may affect the operation of other devices on the network. This parameter can only be accessed and configured via the unit controller OITS panel. BBMD Address The BBMD address is read from the Magnitude Chiller Unit Controller during the communication module s initialization phase. If the BBMD address is not , the communication module sends a Register-Foreign-Device message to the address. If the result code returned is X 0000, the communication module renews the registration at the period defined by the Foreign Device Time-To-Live value. The communication module continues to poll the BBMD address parameter during run-time. If the BBMD address is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. If the new value is , a Delete-Foreign-Device-Table-Entry message is sent to the BBMD address. If the new value is non-zero, a Register-Foreign-Device message is sent to the BBMD address. Changing the BBMD address may affect the operation of other devices on the network. This parameter can only be accessed and configured via the unit controller OITS panel. 12 ED 15117

13 Foreign Device Time-To-Live The Foreign Device Time-To-Live (FDTTL) value is read from the Magnitude Chiller Unit Controller during the communication module s initialization phase. The communication module continues to poll the FDTTL parameter during run-time. If the FDTTL is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. If the new value is different from the existing value, a Register-Foreign-Device message is sent to the BBMD address. This parameter can only be accessed and configured via the unit controller OITS panel. MS/TP Communication Parameters The MS/TP communication setup parameters consist of: the Device, Device, Max Master, Max_Info_Frames, MAC Address and Baud Rate. These parameters can only be accessed and configured via the unit controller OITS panel. Both the MAC Address and the Baud Rate settings require configuration prior to establishing communication from the unit controller to the network. MAC Address The MAC address is read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. This parameter can only be accessed and configured via the unit controller OITS panel. It is not accessible from the network interface (i.e. Building Automation System workstation). The communication module continues to poll the MAC address parameter during run-time. If the MAC address is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. Changing the MAC address may affect the operation of other devices on the network. The allowable range of values for the MAC address is: Since the communication module is always configured as an MS/TP master, only addresses are valid. If a value greater than 127 is read from the unit controller, the communication module defaults to a MAC address of 127. The MAC address must be unique on the MS/TP network. Baud Rate The baud rate is read from a parameter in the Magnitude Chiller Unit Controller during the communication module s initialization phase. The Baud Rate must match the other devices on the same MS/TP network and requires configuration prior to establishing communications from the unit controller to the network. This parameter can only be accessed and configured via the unit controller OITS panel. It is not accessible from the network interface (i.e. Building Automation System workstation). The communication module continues to poll the baud rate parameter during run-time. If the baud rate is changed at the unit controller during run-time, the update is automatically applied to the communication module as soon as the change is received. Baud rates supported are as follows: 9600, 19200, (default) and bps. Device Management The following functions are specific to the device. These functions are used for maintenance and testing. A network management tool such as VTS is typically used to issue the network commands. DeviceCommunicationControl - Disable The purpose of this command is to reduce network traffic for diagnostic testing of the network. When the communication module receives a network command to Disable communications it stops communicating information to the network. An optional time may be specified for how long to ED

14 suspend communications. The unit continues to operate during the Disabled state. A password of 1234 is required. DeviceCommunicationControl - Enable When the Communication module receives a network command to Enable, the chiller unit controller communication to is restored. A password of 1234 is required. ReinitializeDevice (Reset) When the Communication module is capable of receiving a network ReinitializeDevice command to reboot itself (cold start or warm start). The functionality of a cold and warm start are the same and simply reboot the Communication module. The chiller controller can never be reset via the network. Reinitialize Device is implemented with a non-changeable password of ED 15117

15 Configuring the Unit Controller The Magnitude Chiller Unit Controller can operate with the default values of the various parameters. However, certain communication parameters must be configured appropriately (see the appropriate Magnitude Communication Module Installation Manual for details). Default values may be changed using the unit controller OITS panel or via the network (see the Magnitude Chiller Unit Controller Operation & Maintenance Manual, OM 1034 for details). Networks technology, developed by Echelon Corporation, is the basis for LONMARK Interoperable Systems. This technology is independent of the communication media. The LONMARK Interoperable Association has developed standards for interoperable technology systems. In particular they have published standards for HVAC equipment including the Chiller Functional profile. This profile specifies a number of mandatory and optional standard network variables and standard configuration parameters. This manual defines the variables and parameters available in the Magnitude Chiller Unit Controller. Compatibility The Magnitude Chiller Unit Controller, along with the Communication Module, operates in accordance with the Chiller Functional profile of the LONMARK Interoperability Association. Variables The Magnitude Chiller Unit Controller incorporates network variables to access unit data points. The controller uses Standard Network Variable Types (SNVT) from the profile. Some data points can be adjusted (input network variables, nvi) (read/write attributes, e.g., setpoints) from the network and others can only be interrogated (network variables, nvo) (read only attributes, e.g., status information). Configuration variables (nci) are included with the input network variables. Each data point accessible from a network is described with a table that gives the Name, Profile, SNVT Type, and SNVT Index. If the variable is a configuration variable the table also includes the SCPT (Standard Configuration Parameter Type) Reference and the SCPT Index. Example of Data Point Name Profile SNVT Type SNVT Index SNVT Size nvosuctiontemp McQuayChiller SNVT_temp_p 105 two bytes Name Each network variable has a name that you use to access the data point. This is the name of the variable from the profile. In the example above, the name of the variable is nvosuctiontemp. Profile The profile column designates whether the variable is defined in the LONMARK Chiller functional profile or is a McQuay proprietary variable. The variable itself may not be a standard component of the profile, but the unit controller implements it and it is available to the network. The Profile column indicates Chiller for LONMARK standard network variables or McQuayChiller for proprietary variables. SNVT Type This column gives the name of the standard network variable type from the master list. In the example above, the SNVT is SNVT_temp_p. ED

16 SNVT Index This column gives the Index of the standard network variable type from the master list. In the example above, the SNVT Index is 105. SNVT Size This column gives the size of the standard network variable type in number of bytes. In the example above, the SNVT Size is two bytes. SCPT Reference This column gives the name of the Standard Configuration Parameter Type (SCPT) from the master list. SCPT Index This column gives the Index of the Standard Configuration Parameter Type (SCPT) from the master list. Network Considerations Network Topology Each Communication Module is equipped with an FTT-10A transceiver for network communication. This transceiver allows for (1) free topology network wiring schemes using twisted pair (unshielded) cable and (2) polarity insensitive connections at each node. These features greatly simplify installation and reduce network commissioning problems. Additional nodes may be added with little regard to existing cable routing. Free Topology Networks A free topology network means that devices (nodes) can be connected to the network in a variety of geometric configurations. For example, devices can be daisy-chained from one device to the next, connected with stub cables branching off from a main cable, connected using a tree or star topology, or any of these configurations can be mixed on the same network as shown in Figure 1. Free topology segments require termination for proper transmission performance. Only one termination is required. It may be placed anywhere along the segment. Refer to Echelon FTT-10A Transceiver User s Guide. Free topology networks may take on the following topologies: Bus Ring Star Mixed - Any combination of Bus, Ring, and Star Limitations to wire lengths apply and must be observed. 16 ED 15117

17 Figure 1. Singly Terminated Free Topology Ring Topology Singly Terminated Bus Topology Stub Star Topology Termination Termination } Termination Mixed Topology Termination A network segment is any part of the free topology network in which each conductor is electrically continuous. Each of the four diagrams in is a illustration of a network segment. Some applications may require two or more segments. See Free Topology Restrictions. If necessary, segments can be joined with FTT-10A-to-FTT-10A physical layer repeaters. See Figure 2. Figure 2. Combining Network Segments with a Repeater Termination FTT-10A FTT-10A Termination Free Topology Restrictions Although free topology wiring is very flexible, there are restrictions. A summary follows: The maximum number of nodes per segment is 64. The maximum total bus length depends on the wire size: Wire Maximum Node-to-Node Maximum Size Length Length 24 AWG 820 ft (250 m) 1476 ft (450 m) 22 AWG 1312 ft (400 m) 1640 ft (500 m) 16 AWG 1640 ft (500 m) 1640 ft (500 m) Cable The longest cable path between any possible pair of nodes on a segment must not exceed the maximum node-to-node distance. If two or more paths exist between a pair of nodes (e.g., a loop topology), the longest path should be considered. Note that in a bus topology, the longest node-to-node distance is equal to the total cable length. The total length of all cable in a segment must not exceed the maximum total cable length. One termination is required in each segment. It may be located anywhere along the segment. Doubly Terminated Networks You can extend the maximum total cable length without using a repeater by using doubly-terminated network topology. The trade-offs are (1) this network topology must be rigorously followed during the installation and subsequent retrofits and (2) two terminations must be installed at the ends of the bus for proper transmission performance. Limitations to wire lengths apply and must be observed. ED

18 Figure 3. Doubly Terminated Network Topology Termination Termination Doubly Terminated Topology Restrictions The restrictions on doubly-terminated bus topology are as follows: The maximum number of nodes per segment is 64. The maximum total bus length depends on the wire size: Wire Size Maximum Cable Length 24 AWG 2952 ft (900 m) 22 AWG 4590 ft (1400 m) 16 AWG 8855 ft (2700 m) The maximum stub length is 9.8 ft (3 m). A stub is a piece of cable that is wired between the node and the bus (see Figure 1.) Note that if the bus is wired directly to the node, there is no stub, and thus the stub length is zero. If you are wiring to a field terminal strip on a unit, be sure to account for any factory wiring between the terminal strip and the controller. This wiring is considered part of the stub. Two terminations are required in each segment. One must be located at each end of the bus. Network Cable Termination network segments require termination for proper data transmission performance. The type and number of terminations depend on network topology. Network Addressing Every Neuron Chip has a unique 48-bit Neuron ID or physical address. This address is generally used only at initial installation or for diagnostic purposes. For normal network operation, a device address is used. Device addresses are defined at the time of network configuration. All device addresses have three parts. The first part is the Domain ID, designating the domain. Devices must be in the same domain in order to communicate with each other. The second part is the Subnet ID that specifies a collection of up to 127 devices that are on a single channel or a set of channels connected by repeaters. There may be up to 255 subnets in a domain. The third part is the Node ID that identifies an individual device within the subnet. A group is a logical collection of devices within a domain. Groups are assembled with regard for their physical location in the domain. There may be up to 256 groups in a domain. A group address is the address that identifies all devices of the group. There may be any number of devices in a group when unacknowledged messaging is used. Groups are limited to 64 devices if acknowledged messaging is used. A broadcast address identifies all devices within a subnet or domain. Commissioning the Network Pressing the service pin, switch on the Communication Module, generates a service pin message, which contains the Neuron ID and the program code identification of the node. A service pin message is a network message that is generated by a node and broadcast on the network. It can be used to commission the network. A network configuration tool maps device Neuron IDs to the domain/subnet/node logical addressing scheme when it creates the network image, the logical network addresses and connection information for all devices (nodes) on the network. 18 ED 15117

19 External Interface File (XIF) LONMARK guidelines specify exact documentation rules so that proprietary configuration tools are not required to commission and configure devices. The Chiller Communication Module is self-documenting so that any network management tool can obtain all the information needed over the network to connect it into the system and to configure and manage it. An external interface file (a specially formatted PC text file with an extension.xif) is available so that any network tool can design and configure it prior to installation. XIFs are available on or Resource Files The Magnitude Chiller Unit Controller supports variables defined by the LONMARK Chiller functional profile as well as McQuay proprietary variables. The variable itself may not be a standard component of the profile, but the unit controller implements it and it is available to the network. Resource Files provide definitions of functional profiles, type definitions, enumerations, and formats that can be used by network configuration tools such as Echelon s LonMaker program. Refer to the Detailed Data Section for each variable to determine if it is supported by the standard LONMARK Chiller functional profile or is a proprietary variable. Within the Detailed Data Section, each parameter includes a table with a Profile column. The Profile column indicates Chiller for a LONMARK standard network variable or McQuayChiller for a proprietary variable. The Resource Files define the format of how these McQuay-specific variables are displayed when using a tool such as LonMaker. The Resource Files are available on or Unit Controller Default Values The Magnitude Chiller Unit Controller and the Communication Module are designed in accordance with the LONMARK chiller functional profile. The unit can operate with the default values of the various parameters. However, the Protocol Type must be set to. Additional configuration may be necessary for optimal unit performance and network integration. Default values may be changed via the unit controller OITS panel and/or the network. Refer to the appropriate operation manual for default values and unit controller operating instructions (see Reference Documents section for details.) Data Integrity The integrity of some data depends on a valid network connection to maintain current values. The following data points require a valid network connection. If a data point listed in Table 2 does not change after a given time (receive heartbeat), the controller reverts to the value contained in the corresponding network configuration variable (nci). The receive heartbeat feature is only applicable when ncidefaults is set to 0. Table 2. Receive Heart Beat Variables Data Point Capacity Limit Setpoint Chiller Enable Setpoint Cool Setpoint Heat Setpoint Ice Setpoint Chiller Mode Setpoint Variable nvicapacitylim nvichillerenable nvicoolsetpt nviheatsetpt nviicespt nvimode ED

20 Typical Application: Minimum Integration This section gives you the basic information required for integrating the Magnitude Chiller Unit Controller to a BAS and outlines a procedure to set up the unit for network control. Set up the Unit Controller for Network Control From the unit controller OITS panel, follow the steps below: 1. Set the Control Source on the SET/UNIT screen to USER. 2. Change the BAS Network Protocol default to the appropriate BAS Protocol on the SET/BAS screen. 3. Verify with the chiller/control company technician that the chiller is operational on the BAS. 4. Set the Control Source on the SET/UNIT screen to BAS. Display Important Data Points Typical workstation displays of Magnitude Chiller Unit Controller attributes include the following significant data points (page number of detailed description in parenthesis). Each data point is identified with a number that also identifies it in the respective or Protocol Point Summary tables. These data points are also shaded in the comprehensive tables so that you can distinguish them from the rest of the data points in the table. References in the text of this section also identify these data points with a number and shading. Table 3. Significant Data Points No. Configuratio n 1 Chiller Status (37) 5 2 Chiller Mode Set-point (36) 6 3 Actual Capacity (28) 7 4 Chiller Enable Setpoint (32) No. 8 Temperatures Evaporator Entering Water Temperature (50) Evaporator Leaving Water Temperature (51) Condenser Entering Water Temperature (45) Condenser Leaving Water Temperature (46) No Setpoints Cool Setpoint Network (49) Capacity Limit Setpoint Network (30) No Alarms Alarm Digital Output (29) Clear Alarm Network (38) You can display any number of additional data points based on job requirements or individual preference. See Protocol Point Summary section (Tables 4-7) for a complete list of all variables or points available to the network. For a detailed description of all available data points, see the Detailed Data Point Information section. 20 ED 15117

21 Alarms Alarms in a Magnitude Chiller Unit Controller are divided into three classes: Faults, Problems, and Warnings. Fault Alarms have the highest priority. Problem Alarms have medium priority. Warning Alarms have the lowest priority. Notification Magnitude Chiller Unit Controllers may have their alarms monitored by one of two methods: 1) a Binary Output indicating whether any alarms exist, or 2) Alarm value using three Analog Value objects. 1. To monitor whether or not any alarms exist, monitor the Alarm Digital Output variable. If the Present_Value property is a 1, an alarm is active. A value of 0 for the Present_Value property indicates that there are no active alarms. 2. To monitor alarms by alarm value, read the Present_Value property of the three Alarm Analog Value objects (Fault Alarm, Problem Alarm and Warning Alarm). The Present_Value displays a value that corresponds to the highest numbered alarm that is active. It is possible to have multiple active alarms, but only the highest numbered is displayed. The values for all alarms are described in the Alarms section tables. If the Present_Value displays a zero, there are no active alarms. Magnitude Chiller Unit Controllers may have their alarms monitored by one of two methods: 1) by using the In_alarm attribute of nvochillerstat or 2) by reading nvoalarmdescr. 1. The In Alarm attribute of the Chiller Status Network Variable Output (i.e. nvochillerstat.in_alarm) indicates whether any alarm is active (1). If the attribute nvochillerstat.in_alarm displays a zero, there are no active alarms. 2. To monitor which alarms are currently active, read nvoalarmdescr. The unit controller can accommodate 15 simultaneous alarms. Alarm messages are sent sequentially one every five seconds. Clearing Magnitude Chiller Unit Controllers has one Binary Value object that can be used to clear alarms; ClearAlarms Network. A value of 1 will attempt to clear all alarms. Once the alarms are cleared, the Present_Value of this object goes back to 0. Magnitude Chiller Unit Controllers have one variable that can be used to clear alarms; nviclearalarm. Changing the State portion of this SNVT_switch to a value of 1 will attempt to clear all alarms. Once the alarms are cleared, the Present_Value of this object goes back to 0. The Value portion of this SNVT_switch is not used. ED

22 Protocol Point Summary - The following section defines the parameters for all objects available from the unit controller to the network (see Table 4 below). The shaded data points with numbers are the data points listed in Table 3. Table 4. Comprehensive List of Objects Network Control Property Page Read, Write 1 Object Type Instance Description Application Version 29 R Device * Application version software running in the chiller. Chiller Location 34 W Device * Defines where the chiller is physically located. By default, this is blank. Chiller Model 36 R Device * This defines the model of the chiller. Active Setpoint 28 R AV to F (-9.4 to 65.5 C) *Actual Capacity 28 R AV % *Active Capacity Limit (Output) 30 R AV % *Capacity Limit Setpoint - Network 30 W AV 3 0 to 100%; Default=100% *Chiller Enable Output 31 R BI 7 0=Disable, 1=Enable *Chiller Enable Setpoint 32 W BV 2 0=Disable, 1=Enable Chiller Capacity Limited 32 R BI 6 0=Not Limited, 1=Limited Chiller Local/Network 34 R BI 3 0=Network, 1=Local Chiller Mode Output 35 R MSV 2 1=Ice, 2=Cool, 3=Heat Chiller Mode Setpoint Network 36 W MSV 3 1=Ice, 2=Cool, 3=Heat, Default=Cool Chiller On Off 36 R BI 4 0=Chiller Off, 1=Chiller On *Chiller Status 37 R MSV 1 1=Off, 2=Start, 3=Run, 4=Preshutdown, 5=Service Compressor Average Current 40 R AI amps (less for some models) Compressor Discharge Refrigerant Pressure 40 R AI 81 0 to PSI Compressor Discharge Refrigerant 41 R AI F to 257 F (-40 C to 125 C) Temperature Compressor Discharge Saturated Refrigerant Temperature 41 R AV to 185 F (-26.2 to 85 C) Compressor Percent RLA 42 R AV 8 0% - 150% RLA Compressor Power 42 R AI kw Compressor Run Hours 42 R AV ,999 Compressor Starts 43 R AV ,535 Compressor Suction Refrigerant Temperature 44 R AI F to 257 F (-40 C to 125 C) Compressor Average Voltage 40 R AI ,000 volts *Condenser Entering Water Temperature 45 R AI 3-40 to 257 F (-40 to 125 C) Condenser Flow Switch Status 45 R BI 1 0=No Flow, 1=Flow *Condenser Leaving Water Temperature 46 R AI 4-40 to 257 F (-40 to 125 C) Condenser Pump #1 Run Hours 46 R AV ,999 Condenser Pump #2 Run Hours 46 R AV ,999 Condenser Refrigerant Pressure 47 R AI 99 0 to PSI (-140 to 2827 kpa) Condenser Saturated Refrigerant Temperature 47 R AV to 185 F (-26.2 to 85 C) Compressor Suction Refrigerant Pressure 44 R AI psi Compressor Suction Saturated Refrigerant 44 R AV to 104 F (-26.2 to 40 C) Temperature Condenser Water Flow Rate 47 R AI to 10, GPM (0 to 631 L/s) Condenser Pump #1 Status 48 R BI 11 0=Pump Off Request, 1=Pump On Request Condenser Pump #2 Status 48 R BI 12 0=Pump Off Request, 1=Pump On Request 22 ED 15117