MicroTech III Rooftop and Self Contained Unit Controller Protocol Information

Transcription

1 Engineering Data ED Group: Controls Part Number: ED Date: February 2011 Supersedes: ED MicroTech III Rooftop and Self Contained Unit Controller Protocol Information Networks Networks Applied Rooftop Models: RPE, RDE, RPS, RDT, RFS, RDS and RAH Self-Contained Models: SWT, SWP Maverick II Commercial Rooftop Model: MPS 2011 McQuay International

2 Table of Contents Table of Contents... 2 Revision History...3 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 Networks...6 MicroTech III Unit Controller Device Object...8 Network Considerations...9 Networks...11 Typical Application: Minimum Integration Set up the Unit for Network Control...16 Display Important Data Points...16 Network Off...16 Network Occupancy Scheduling...16 Alarms...17 Unit Controller Sequence of Operation...18 Comprehensive Data Point Tables Standard Objects...19 Variables...24 Detailed Data Point Information AHU Loc/Net...28 Application Mode...28 Airflow Switch (Fault)...29 Airflow Switch (Warning)...29 Application Version...30 Building Static Pressure...30 Building Static Pressure Setpoint...30 Conductivity...31 Control Temp Source...31 Control Temperature...32 Cooling Capacity...32 Cooling Status...32 Date...33 Dew Point Setpoint...33 Dew Point Temperature...34 Dirty Filter Switch...34 Discharge Air Temperature...34 Duct High Limit Switch...35 Duct Static Pressure...35 Duct Static Pressure Setpoint...35 Economizer Capacity...36 Economizer Enable...36 Economizer Status...37 Effective Discharge Air Temperature Setpoint...38 Effective Setpoint Output...38 Emergency Off Switch...39 Emergency Override...39 Energy Recovery Discharge Air Temperature...40 Energy Recovery Exhaust Air Temperature...40 Energy Recovery Wheel Status...41 Energy Recovery Wheel Speed...41 Entering Fan Temperature / Leaving Coil Temp...41 Entering Water Temperature...42 Exhaust Fan Capacity...42 Exhaust Fan Capacity Input...43 Freeze Switch (Fault)...43 Freeze Switch (Problem)...43 Heat Fail Input...44 Heating Capacity...44 Heating Status...45 High Pressure Circuit 1 Switch...45 High Pressure Circuit 2 Switch...46 High Pressure Circuit 3 Switch...46 High Pressure Circuit 4 Switch...46 High Pressure Circuit 5 Switch...47 High Pressure Circuit 6 Switch...47 High Pressure Circuit 7 Switch...48 High Pressure Circuit 8 Switch...48 HVAC Unit Type Identifier...48 Local OA Temperature...49 Local Space Temperature...49 Low Pressure Circuit 1 Switch...50 Low Pressure Circuit 2 Switch...50 Low Pressure Circuit 3 Switch...50 Low Pressure Circuit 4 Switch...51 Low Pressure Circuit 5 Switch...51 Low Pressure Circuit 6 Switch...52 Low Pressure Circuit 7 Switch...52 Low Pressure Circuit 8 Switch...52 Maximum Discharge Air Heating Setpoint...53 McQuay AHU Unit Status...53 Minimum Discharge Air Cooling Setpoint...54 Minimum Send Time...55 Mixed Air Temperature...55 Network Discharge Air Cooling Setpoint...56 Network Discharge Air Heating Setpoint...56 Object Request...56 Object Status...57 Occupancy...58 Occupancy Mode...59 Occupancy Scheduler Input...60 Occupied Cooling Setpoint...61 Occupied Heating Setpoint...62 Outdoor Air Damper Minimum Position Input...62 Outdoor Air Temperature...63 Outdoor Air Temperature Input...63 Outdoor Airflow...64 Outdoor Airflow Setpoint...64 Primary Cool Enable...64 Primary Heat Enable...65 Receive Heartbeat...66 Reheat Capacity...67 Relative Humidity...67 Relative Humidity Input...68 Relative Humidity Setpoint...68 Remote Return/Exhaust Fan Capacity Control Flag...68 Remote Supply Fan Capacity Control Flag...69 Return Air Temperature...70 Return/Exhaust Fan Capacity...70 Exhaust Fan Status...71 Return Fan Capacity Input...71 Send Heartbeat...72 Space CO Space IAQ Input...73 Space Temperature...73 Space Temperature Input...73 Sump Pump Water Level Switch...74 Supply Fan Capacity...74 Supply Fan Capacity Input...75 Temperature Setpoint Input...75 Time...75 Unit State...76 Unit Support...77 Unoccupied Cooling Setpoint...77 Unoccupied Heating Setpoint...78 VAV Box Output...78 Water Flow Switch...79 Water Regulating Valve...79 Waterflow Switch Input...80 Alarms...81 Fault Alarms (Highest Priority)...81 Problem Alarms (Medium Priority)...82 Warning Alarms (Lowest Priority)...83 Alarm Monitoring ED

3 Alarm Notification Alarm Clearing Objects Clear Alarms Notification Class - Faults Notification Class - Problem Notification Class - Warnings Warning Alarm Problem Alarm Fault Alarm Airflow Fault Airflow Switch Warning Conductivity Warning Control Temp Fault Dirty Filter Warning Discharge Sensor Fault Duct High Limit Fault Emergency Off Fault Entering Fan Temp / Leaving Coil Temp Problem Entering Water Temp Problem Freeze Fault Freeze Problem Heat Fail Problem High Discharge Temp Fault High Pressure Circuit 1 Problem High Pressure Circuit 2 Problem High Pressure Circuit 3 Problem High Pressure Circuit 4 Problem High Pressure Circuit 5 Problem High Pressure Circuit 6 Problem High Pressure Circuit 7 Problem High Pressure Circuit 8 Problem High Return Temp Fault Low Discharge Temp Fault Low Pressure Circuit 1 Problem Low Pressure Circuit 2 Problem Low Pressure Circuit 3 Problem Low Pressure Circuit 4 Problem Low Pressure Circuit 5 Problem Low Pressure Circuit 6 Problem Low Pressure Circuit 7 Problem Low Pressure Circuit 8 Problem Mixed Air Temp Problem Outdoor Temp Problem Return Temp Problem Space Temp Problem Sump Water Level Problem Waterflow Switch Problem Water Regulating Valve Problem Device Management DeviceCommunicationControl - Disable DeviceCommunicationControl - Enable ReinitializeDevice (Reset) Appendix A: Protocol Implementation Conformance Statement (PICS) Protocol Implementation Conformance Statement Product Description Standardized Device Profile Standard Object Types Supported Data Link Layer Options Segmentation Capability Device Address Binding Networking Options Character Sets Supported Index Revision History ED15112 September 2008 Preliminary release. ED October 29, 2008 Added 2 notification class objects to. There are now a total of 3 objects (faults, problems & warnings). ED January 22, 2009 The only change was to the Networking Options section of the Protocol Information Conformance Statement (PICS). The BBMD does support registration by foreign devices. This was previously marked no. Changed the enumeration for the Water Regulating Valve object from 0=Open and 1=Closed to 0=normal and 1=alarm. ED March 11, 2009 The only change was to the Standard Object Types Supported section of the Protocol Information Conformance Statement (PICS). Present Value, Priority Array were removed from the optional list for Binary Outputs. These properties are required. Removed Alarm Value from the optional list for Binary Outputs. This is not a propertie of this object. Also removed Priority Array from Binary Inputs. This is not a property of this object. Modified the optional properties for Multi-state Input. Modified the optional properties for Multi-state Output ED November, 2009 Added Maverick II (MPS) model. Modified keypad navigation per new global standard. Updated points affected by removal of heartbeat function (changed points from commandable to writable and removed reference to writing at priority 8). Added the following points: Heat Fail 199, Heat Fail Problem BV, ERDAT (AV), EREhht (AV), ERWhlOnOff (MV), ERWheelSpd (AV), Min OA Flw Spt (AV) ED December, 2009 Changed ER Discharge Air Temp & ER Exhaust Air Temp object types from AV to AI.Updated firmware version from to in Software Revision and PICs sections. ED February, 2010 Changed ER Wheel Speed object types from AV15 to AI15. Removed reference to energy recovery from Return Fan Capacity Input & Exhause Fan Capacity Input (Detailed Data Information section). Changed Application Mode enumerations in detailed data section. Updated PICS to include software v ED June, 2010 Changed nvounitstatus_inalarm_ to nvo WarnAlarm, nvoprobalarm, and nvofaultalarm in detailed data section. Updated software revision to v Removed references to S7 switch on fig. 4. ED February 2011 Added Control Temp Source (MSV 39) to. This is available in application Added DAC checkbox to Relative Humidity Input on the Standard Objects Table. Added Low/High Pressure Circuit Switch 7 and 8, added Low/High Pressure Circuit 7 and 8 Problem, changed Sump Pump Switch to Sump Pump Water Level Switch, changed Sump Pump Fail Problem to Sump Water Level Problem. ED

4 Software Revision Keypad Menu Path Version Information\App Version= The software part number is encoded in the controller s memory and is available for display on the keypad/display. The part number is available via system integration tools. The software part number codification is as follows: Implied digits on all MicroTech III Air Handling software Base part number (6017 indicates standard software) Version Revision This edition documents Network Protocols for version of the standard MicroTech III Unit Controller application and all subsequent versions until otherwise indicated. However, if your software is of a later version, some of the information in this document may not completely describe your application. You can determine the revision of the application software from the keypad/display. The path for this information from the main menu is Version Information\App Version=. Reference Documents Company Number Title Source McQuay International OM 920 MicroTech III Unit Controls for Applied Rooftop and Self- Contained Systems Operation Manual American Society of Heating, ANSI/ A Data Communication Protocol for Building Refrigerating and Air- ASHRAE 135- Automation and Control Networks Conditioning Engineers 2004 LonMark Interoperability G LonMark Layers 1-6 Interoperability Guidelines, Version Association 3.4 LonMark Interoperability G LonMark Application Layer Interoperability Guidelines, Association Version 3.4 LonMark Interoperability 8500_10 LonMark Functional Profile: Space Comfort Controller, Association Version 1.0 LonMark Interoperability 8600_10 LonMark Functional Profile: Discharge Air Controller, Association Version McQuay International ED MicroTech III Rooftop and Self-Contained Systems Protocol Implementation and Conformance Statement (PICS) Echelon Corporation G FTT-10A Free Topology Transceiver Users Guide Notice 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, Maverick II and MicroTech III 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

5 Introduction This document contains the necessary information you need to incorporate a MicroTech III Unit Controller (i.e. Applied Roofto, Self-Contained, or Maverick II Unit) from McQuay International into a building automation system (BAS). It lists all properties, variables, and corresponding MicroTech III 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 MicroTech III Unit Controller contains data points or unit variables that are accessible from three user interfaces: the unit keypad, a network (/IP 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 920 (available on for keypad details. This document contains the network details necessary to incorporate the MicroTech III Unit Controller into the network. Protocol Definitions The MicroTech III Unit Controller can be configured in either an interoperable or network. The 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, MS/TP (Master/Slave Token Passing), and. There are two modules: one in accordance with the LonMark Space Comfort Controller (General) functional profile and one in accordance with the Discharge Air Controller functional profile. 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. Networks A control network specification for information exchange built upon the use of LonTalk 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 modules are LonMark 3.4 certified in accordance with the Space Comfort Controller (SCC) and Discharge Air Controller (DAC) functional profiles. 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 four communication module options ( IP, MS/TP, SCC or DAC). 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. The bold parameters can be changed using the keypad display located on the unit controller. Communication Setup Parameter Settings Parameter Name IP MS/TP LON (DAC or SCC) DHCP On N/A N/A IP Address DHCP Enabled N/A N/A IP Subnet Mask DHCP Enabled N/A N/A Given IP Address N/A N/A Given IP Subnet Mask N/A N/A Given Gateway Address N/A N/A UDP Port Number N/A N/A MSTP MAC Address 2 N/A 18 N/A MSTP Baud Rate N/A N/A Device Instance Number variable variable N/A Max APDU Length N/A Device Object Name POL908_FF2BEE 3 POL904_AD45EC28 4 N/A Receive Heartbeat 0Sec 0Sec 0Sec Max Master N/A 127 N/A Max Info Frames N/A 1 N/A Term Resistor N/A No 5 N/A Notes: 1. These addresses are used if DHCP is set to Off. For changes to these parameters to take effect, use the keypad display and set Apply IP Chg on the IP Setup menu to Yes and cycle power. 2. The MSTP MAC Address is set via the keypad/display. You must cycle power after changing it for the changes to take effect. 3. The last 6 digits are the last 6 digits of the MAC address. The MAC address is printed a sticker affixed to the communication module. 4. The last 8 digits are computed from the production number and date code. 5. Term Resistor is only changeable via the keypad/display. This item must be set to Yes for the first and last unit on the MS/TP network. On all other units, this variable should be set to No (default). Networks Compatibility The MicroTech III Unit Controller 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 MicroTech III 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 MicroTech III 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 (read/write properties, e.g., setpoints) from the network and others can only be interrogated (readonly properties, e.g., status information). Each data point accessible from a network is described with a table that gives the, Identifier, Full Reference or path, and the Name enumeration of the property. 6 ED

7 Example of Data Point Keypad Menu Path Standard Menus\Flow Summary\Ret/Exh Fan= Binary Output 4 1 Present_Value 85 <Device Name>.ExhFanState.Present_Value 0 = Off 1 = On 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 Return/Exhaust Fan Status (See page 71.) 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 Object Identifier 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. Object names 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 1. Identifier Each object has a number of properties or attributes. Each property has a unique identifier of Identifier data type. identifiers are an enumerated set; a number identifies each member. The Identifier enumeration number is shown in the ID column. In the example above the property identifier is 85. Name Each property also has a unique name. names are character strings and shown in the Name column. In the example above the property name is Present Value. The full reference is the path of the property within the network where the MicroTech III Unit Controller resides. It is a character string equivalent to the object identifier and the property identifier. In the example above the full reference is <Device Name>.ExhFanState.Present_Value. 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 column of the data point listing. ED

8 MicroTech III Unit Controller Device Object Each compatible device must have one and only one Device Object. Device The MicroTech III 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 initial Device Object identifier is set at manufacturing. 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. The initial device object instance number is This number must be unique on the entire network. The object instance number can be changed via the keypad display. You must cycle power for the change to take effect.! 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 Object Name The Device Object Name uniquely specifies a device in the network. It must be unique in the network. The device name for the MicroTech III Unit Controller device is to be determined. The device name is the prefix of all object names in the MicroTech III Unit Controller. All objects include the device name and a period. preceding the object name. The Device Object name is also available to the network in the device. The property name is Object_Name and property identifier is 77. For a IP card, the default Object Name is POL908_###### where ###### is the last 6 digits of the MAC address. For a MS/TP card, the default Object Name is POL904_######## where ######## is computed from the production number and date code. Device Object Properties The device object contains many other informative properties as shown in Table 1. Table 1. MicroTech III Air Handling Unit Controller Device Object Properties Identifier Default Value Data Type 75 Device, variable ObjectIdentifier Object Name 77 POL908_FF2BEE 1 Character String Object Type 79 8 ObjectType System Status 112 DeviceStatus Vendor Name 121 McQuay Character String Vendor Identifier Unsigned 16 Model Name 70 AHU Character String Firmware Version 44 variable Character String Application Software Revision 12 variable Character String Location 58 Character String Description 28 MTech III AHU Character String Protocol Version 98 1 Unsigned Protocol Revision Unsigned Protocol Services Supported 97 ServicesSupported Protocol Object Types Supported 2 96 AI, AO, AV, BI, BO, BV, Cal, ObjectTypesSupported Device, MSI, MSO, NC, Sch, MSV Object List 76 Sequence of ObjectIdentifer Max APDU Length Accepted (IP) / 480 (MS/TP) Unsigned 16 8 ED

9 Identifier Default Value Data Type Segmentation Supported 107 None Segmentation Max Segments Accepted Unsigned Local Time3 57 variable Time Local Date 3 56 variable Date UTC Offset (Range: ) Integer Daylight Savings Status 24 variable Boolean APDU Segment Timeout Unsigned APDU Timeout Unsigned Number of APDU Retries 73 3 Unsigned Device Address Binding 30 Sequence of AddressBinding Database Revision Unsigned Active COV Subscriptions 152 List of COVSubsriptions 1. For IP, the last 6 digits are the last 6 digits of the MAC address. The MAC address is printed a sticker affixed to the communication module. For MS/TP, the last 8 digit are computed from the production number printed on the bar code label affixed to the side of the module. 2. While the MicroTech III Unit Controller supports the entire set of object types, not all object types are used. See the Object List for details. 3. The communication module and the MicroTech III Unit Controller both have their own time clocks. The date and time read via could differ from the date and time in the unit controller the date or time is changed via the keypad display. The two time clocks resynchronize approximately every minutes and after every power cycle of the unit controller or communication module. 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. /IP Addressing The /Internet Protocol (/IP) address of the MicroTech III Unit Controller in a /IP network consists of the four-octet Internet Protocol address followed by the two-octet UDP (User Datagram Protocol) port number. The /IP address is a six-octet value analogous to a MAC address. The IP address portion of the /IP address must be unique in the /IP network segment. The default UDP port number in the MicroTech III Unit Controller is (BAC0 in hexadecimal). The device object of the MicroTech III Unit Controller contains a Given Internet Protocol Subnet Mask (Default is ) and a default Given IP address of The controller does support DHCP (Dynamic Host Configuration Protocol) IP addressing which is enabled by default. The keypad/display can be used to configure the /IP addressing. The keypad will display the current IP address only when the network is connected. The MicroTech III Unit Controller can be incorporated into a /IP network dedicated to devices only or an Ethernet network shared with devices and other devices. Shared Ethernet Networks Integrating the MicroTech III Unit Controller into a shared Ethernet LAN requires close cooperation with the network administrator of the shared Ethernet network. First, verify whether DHCP should or should not be enabled. If not, obtain the IP Subnet Mask of the shared network from the network administrator. Then, obtain static IP Addresses for all MicroTech III Unit Controllers you are integrating into the shared network. Finally obtain the address of an IP Router to use for sending IP messages to and from the IP subnets. Once you have these, refer to Setting Unit Controller Communication Parameters in the Basic Protocol Information section found previously in this document. ED

10 Configuring the Unit Controller The MicroTech III Unit Controller with attached communication module is ready to operate with the default values of the various parameters. Default values may be changed with the unit s keypad or via the network. See the MicroTech III Unit Controller Operation Manual (OM 920). MS/TP Network Addressing The MS/TP device address (Media Access Control [MAC] address) of the MicroTech III Air Handling Unit Controller in a Master Slave/Token Passing (MS/TP) Local Area Network (LAN) is set using the keypad/display. Navigate to the Advanced Menus\MSTP Setup menu to change this value. You must cycle power (turn the unit controller off and then on again) in order for the new address to take effect. 10 ED

11 Networks technology, developed by Echelon Corporation, is the basis for LonMark interoperable systems. This technology is independent of the communications media. The LonMark Interoperable Association has developed standards for interoperable technology systems. In particular they have published standards for HVAC equipment including the Discharge Air Controller functional profile and the Space Comfort Controller functional profile. These profiles specify a number of mandatory and optional standard network variables and standard configuration parameters. This manual defines these variables and parameters available in the MicroTech III Unit Controller. Compatibility The MicroTech III Unit Controller with communication module operates in accordance with the Discharge Air Controller (DAC) functional profile or the Space Comfort Controller (SCC) functional profile of the LonMark Interoperability standard. Variables MicroTech III Unit Controllers incorporate network variables to access unit data points. The unit controller uses Standard Network Variable Types (SNVT) from each 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 (output network variables, nvo) (read only attributes, e.g., status information). Configuration variables (nci) are included with the read/write attributes. 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 Reference and the SCPT Index. Example of Data Point LonWorks LonWorks Name Profile SNVT Type SNVT Index nvobldgstatpress DAC, SCC SNVT_press_p 113 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 network variable is nvobldgstatpress. Profile The profile column designates the MicroTech III Communication Module that incorporates this network variable. The variable itself may not be a standard component of that particular profile, but the communications module does implement and it is available to the network. SNVT Type This column gives the name of the standard network variable type from the master list. SNVT Index This column gives the number of the standard network variable type from the master list. SCPT Reference This column gives the name of the Standard Configuration Parameter Type (SCPT) from the master list. SCPT Index This column gives the number 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 communications. 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. ED

12 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 for further details (see Reference Documents section). Free topology networks may take on the following topologies: Bus Ring Star Mixed - Any combination of Bus, Ring, and Star Note: Limitations to wire lengths apply and must be observed. 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 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. Refer to Echelon FTT-10A Transceiver User s Guide for further details. Figure 2. Combining Network Segments with a Repeater Termination FTT-10A FTT-10A Termination 12 ED

13 Free Topology Restrictions Although free topology wiring is very flexible, there are restrictions. A summary follows, refer to the Echelon FTT-10A User s Guide for details. 1. The maximum number of nodes per segment is The maximum total bus length depends on the wire size: Wire Size Maximum Node-to-Node Length Maximum Cable 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) 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. a. The total length of all cable in a segment must not exceed the maximum total cable length. 3. 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. See Figure 3. 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. Refer to Echelon FTT-10A Transceiver User s Guide. Note: Limitations to wire lengths apply and must be observed. Figure 3. Doubly Terminated Network Topology Termination Termination Doubly Terminated Topology Restrictions The restrictions on doubly-terminated bus topology are as follows: 1. The maximum number of nodes per segment is The maximum total bus length depends on the wire size: Wire Size 24 AWG 2952 ft (900 m) 22 AWG 4590 ft (1400 m) 16 AWG 8855 ft (2700 m) Maximum Cable Length 3. The maximum stub length is 9.8 ft (3 m). The length of the MicroTech III Air Handling cable harness stub is 7.2 ft (2.19 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. 4. 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. Refer to Echelon FTT-10A Transceiver User s Guide. LonWorks 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. ED

14 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 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. network variables for both the Discharge Air Controller and the Space Comfort Controller are defined below. Variables are used in both the Space Comfort Controller and Discharge Air Controller profiles unless marked otherwise. 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. External Interface File (XIF) LonMark guidelines specify exact documentation rules so that proprietary configuration tools are not required to commission and configure devices. The MicroTech III Communication Module is selfdocumenting 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 also available so that any network tool can design and configure it prior to installation. XIF files are available on Configuring the Unit Controller 1. The MicroTech III Unit Controller is designed, programmed, and configured to be a rooftop or self-contained unit controller in accordance with either the LONMARK Discharge Air Controller (DAC) or LonMark Space Comfort Controller (SCC) functional profile. The unit is ready to operate with the default values of the various parameters set at the factory. Default values may be changed with the unit s keypad or via the network. See the MicroTech III Unit Controller Operation Manual (OM 920). 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 bound. If data points listed in Table 2 do not change after a given time, the controller reverts to local control. In the case of the LonWorks module, the variables will revert to their default values. 14 ED

15 Table 2. Receive Heartbeat Variables Data Point Occupancy Scheduler Input Application Mode Supply Fan Capacity Input Outdoor Air Temperature Space Temperature Primary Cool Enable Primary Heat Enable Economizer Enable Exhaust Fan Capacity Input Return Fan Capacity Input Water Flow Switch Input Space Indoor Air Quality (IAQ) Input Relative Humidity Input LonWorks Variable nvioccschedule nviappliccmd nvisupfancap nvioutdoortemp nvispacetemp nvipricoolenable nvipriheatenable nvieconenable nviexhfancap nviretfancap nvicwflow nvispaceiaq nvispacerh ED

16 Typical Application: Minimum Integration When you have integrated the unit into your network, you can monitor and control unit operation from your workstation. At a minimum, you can: Display and monitor a minimum of important data points on your workstation display Turn the unit on or off from your workstation Set the schedule from your workstation and Operate the unit safely This section gives you the basic information and outlines a procedure to set up the unit for network control. Set up the Unit for Network Control To control the MicroTech III Unit Controller over the network, set the Control Mode function to AUTO from the unit keypad. The keypad password (2526) is required to edit this function. For a detailed description of how to use the keypad, refer to MicroTech III Unit Controller Operation Manual (OM 920). Display Important Data Points Typical workstation displays of MicroTech III 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 Comprehensive Data Point 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 Configuration No Temperatures/Pressures No Setpoints No Clear Alarms 1 Unit State (76) 5 Discharge Air Temperature (34) 2 Application Mode (28) 6 Return Air Temperature (70) 3 Occupancy (58) 7 Outdoor Air Temperature (63) 4 Occupancy Mode (59) 9 Duct Static Pressure Setpoint (35) 10 Unoccupied Cooling Setpoint (77) 11 Occupied Cooling Setpoint (61) 8 Duct Static Pressure (35) 12 Occupied Heating Setpoint (62) 13 Unoccupied Heating Setpoint (78) 14 Clear Alarms (85) You can display any number of additional data points based on job requirements or individual preference. See Variables for lists of all Variables available to a network. See Standard Objects on page 19 for a list of all Standard Objects available to a network. For a more detailed description of all available data points, see the Detailed Data Point Information section. Network Off The unit can be turned off over the network by writing to the Application Mode. Writing AUTO to Application Mode allows the unit controller to determine its mode of operation based on input conditions. Writing OFF to Application Mode shuts down the unit, etc. The Emergency Override Mode Flag can also be used to shut down the unit from the network. Network Occupancy Scheduling Using the keypad, set the Occupancy Mode to Auto. Schedule unit operation over the network with the Occ Scheduler input. Switching from OCC, UNOCC, BYPASS (TntOvrd), or AUTO commands the unit into the mode you select. 16 ED

17 Alarms Alarms in a MicroTech III 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 MicroTech III Unit Controllers may have their alarms monitored by one of four methods: 1) individually by Binary Values, 2) Alarm value using one Analog Value, 3) Alarm class, or 4) Notification Classes. 1. To monitor alarms individually, read the Present_Value of the desired Binary Value object. Each alarm has its own Binary Value object. If the Present_Value is Inactive (0), the alarm is not active. If the Present_Value is Active (1), the alarm is active. 2. To monitor alarms by alarm value, read the Present_Value property of the Alarm Value Analog Value object. The Present_Value displays a value that corresponds to the highest priority alarm that is active. It is possible to have multiple active alarms, but only the highest priority is displayed. For example, if there is a simultaneous Dirty Filter Warning (value of 24) and a Freeze Fault (value of 252), then the Freeze Fault value of 252 will display in the Present_Value because it is the higher priority alarm of the two. Once the Freeze Fault condition is corrected and the fault is cleared, the next priority active alarm value (in this example, value of 24 for Dirty Filter alarm) 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. 3. To monitor alarms by alarm class, read the Present_Value of the appropriate Analog Value object (Warnings, Problems and Faults). The Present_Value displays a value that corresponds to the highest priority alarm that is active for that particular alarm class. It is possible to have multiple active alarms, but only the highest priority is displayed. 4. To monitor alarms using the Notification Class objects, see the Alarm Notification section. MicroTech III Unit Controllers may have their alarms monitored by one of two methods: 1) by using the In_alarm attribute of nvounitstatus or 2) by alarm class. 1. Alarms within MicroTech III Unit Controllers can be monitored individually by using the In Alarm attribute of the Unit Status Network Variable Output (i.e. nvounitstatus_in_alarm). This attribute displays a value that corresponds to the highest priority alarm that is active. It is possible to have multiple active alarms, but only the highest priority is displayed in this attribute. For example, if there is a simultaneous Dirty Filter Warning (value of 24) and a Freeze Fault (value of 252), then the Freeze Fault value of 252 will display in nvounitstatus_in_alarm because it is the higher priority alarm of the two. Once the Freeze Fault condition is corrected and the fault is cleared, the next priority active alarm value (in this example, value of 24 for Dirty Filter alarm) is displayed. The values for all alarms are described in the Alarms section tables. If the attribute nvounitstatus_in_alarm displays a zero, there are no active alarms. When the nvounitstatus_in_alarm attribute reads a value in the range of 1 to 99, a Warning Alarm is active. When the attribute reads a value in the range of 100 to 199, a Problem Alarm is active. When the attribute reads a value in the range of 200 to 255, a Fault Alarm is active. 2. To monitor alarms by alarm class, read nvowarnalarm, nvoprobalarm and nvofaultalarm. The value corresponds to the highest priority alarm that is active. It is possible to have multiple active alarms, but only the highest priority is displayed. Clearing MicroTech III Unit Controllers have one Multi-State Value objects that can be used to clear alarms. All alarms of a particular class may be cleared by writing the appropriate value to the Present Value property of ClearAlarms (2=ClearAllFaults, 3=ClearAllProblems, 4=ClearAllWarnings). All alarms of all three classes can be cleared by writing a 5 (ClearAllAlarms) to Present_Value. Once the alarms are cleared, the Present_Value of this object goes back to None (1). MicroTech III Unit Controllers have one variable that can be used to clear alarms; nviclearalarms. All alarms of a particular class may be cleared by writing the appropriate value to nviclearalarms (1=ClearAllFaults, 2=ClearAllProblems, ED

18 3=ClearAllWarnings). All alarms of all three classes can be cleared by writing a 4 (ClearAllAlarms) to nviclearalarms. Once the alarms are cleared, this variable goes back to None (0). Unit Controller Sequence of Operation The sequence of operation for a MicroTech III Unit Controller depends on the control type. Refer to the MicroTech III Unit Controller Operation Manual (OM 920) for sequence of operation details, including keypad operation. 18 ED

19 Comprehensive Data Point Tables These comprehensive data point tables contain the significant parameters of specific data points. The shaded data points with numbers are the data points listed in Table 3. Standard Objects Network Control (Keypad attributes available as Standard Objects for network control of the unit) Page Read, Write Object Type Instance SCC DAC Description Unit Status/Settings Unit State 76 R MSV 15 1=Off, 2=Start, 3=Recirc, 4=FanOnly, 5=MinDAT, 6=Htg, 7=Econo, 8=Clg McQuay AHU Unit Status 53 R MSV 1 Mode: 1=Enabled, 2=OffMan, 3=OffManCtrl, 4=OffNet, 5=OffAlm, 6=OffFanRetry Cooling Status 32 R MSV 2 1=Enabled, 2=None, 3=OffAmb, 4=OffAlarm, 5=OffNet, 6=OffMan Heating Status 45 R MSV 4 1=Enabled, 2=None, 3=OffAmb, 4=OffAlarm (Not Used), 5=OffNet, 6=OffMan Economizer Status 37 R MSV 3 1=Enabled, 2=None, 3=OffAmb, 4=OffAlarm (Not Used), 5=OffNet, 6=OffMan Cooling Capacity 32 R AV 1 cooling capacity (%) Heating Capacity 44 R AV 2 heating capacity (%) Supply Fan Capacity 74 R AI 8 Current supply fan capacity (%) Return/Exhaust Fan Capacity 70 R AI 10 Current return or exhaust fan capacity (%) Economizer Capacity 36 R AV 15 Feedback value (%) Emergency Override 39 W MSV 10 1=Normal, 2=Off (Shuts unit off via a network signal, puts Unit Status = OffNet) Application Mode 1 28 W MSV 5 1=Off, 2=HeatOnly, 3=CoolOnly, 4=FanOnly, 5=Auto, 6=NA Applies only when Ctrl Mode=Auto Occupancy Occupancy 58 R MSV 6 1=Occ, 2=Unocc, 3=TntOvrd Occupancy Mode 59 W MSV 7 1=Occ, 2=Unocc, 3=TntOvrd, 4=Standby (not used) 5=Auto. Temperatures Control Temperature 32 R AI 14 Current reading of sensor Discharge Air Temperature 34 R AI 1 Current reading of sensor Return Air Temperature 70 R AI 2 Current reading of sensor Space Temperature 73 R AI 3 Current reading of sensor Outdoor Air Temperature 63 R AI 4 Current reading of sensor Entering Fan / Leaving Coil Temp 40 R AI 7 Current reading of sensor Entering Water Temperature 42 R AI 6 Current reading of sensor Mixed Air Temperature 55 R AI 5 Current reading of sensor Flow Status Exhaust Fan Status 71 R BV 1 0=Off, 1=On VAV Box Output 78 R MSV 14 N/A 1=Heat (Off), 2=Cool (On) SAF Spd Control Duct Static Pressure 35 R AV 6 N/A Current reading of sensor. If unit has two sensors the lower of the two is displayed Duct Static Pressure Setpoint 35 W AV 7 N/A Default = 1.00 WC Remote Supply Fan Capacity 69 W MSV 11 1=DSP, 2=Speed, 3=Space Control Flag Supply Fan Capacity Input 1 75 W AV 21 N/A Default = (Null) Applies only when MSV11=Speed (2) RF/EF Spd Control Building Static Pressure 30 R AI 9 Current reading of sensor value Building Static Pressure Setpoint 30 W AV 8 Default = WC ED