Niagara AX integration with Eaton product

Transcription

1 Application Paper AP152001EN Contents Description Page Overview....2 Considerations of a local matter....2 Protocol communication enablement...2 Communication port hardware...2 Communication network speed....2 Modbus integration with Eaton meter, relay, and Gateway products IQ 35M family...2 IQ 130/140/150 family...2 IQ 250/260 family...3 Power Xpert Meter 2000 series....3 Power Xpert Meter 4000/6000/8000 series...3 E-Series relay family...3 RS-485 PONI (MPONI)....4 Modbus troubleshooting common configuration issues...4 Adding and working with basic Modbus register channels....4 Modifying the Modbus byte order configuration in Niagara AX...5 Addressing extended registers with Niagara AX...5 Resolving issues regarding slow data polling....5 BACnet integration with Eaton meter, relay, and Gateway products How BACnet applies to Eaton....6 Data sharing via BACnet objects BACnet device discovery of Eaton products....7 BACnet troubleshooting common configuration issues....7 I can discover devices, but I cannot see data....8 I cannot override object values...8

2 Application Paper AP152001EN Overview Eaton s high-tech meter, relay, and communication products provide customers with durable and flexible networking solutions. Through the use of standard communication network protocols, data from Eaton devices can be shared and exchanged with a wide variety of vendors. This enables customers to connect their power quality devices into other smart building infrastructures such as a building automation system. Within the building automation market space, TridiumT, an independent business entity of Honeywell, develops and sells software and hardware products that bridge multiple protocols into one common platform. The software enabling this is known as the Niagara FrameworkT. Tridium sells their product through their own traditional distribution channel (known as VykonT), and has several hundred thousand products installed globally. This document provides general guidance of how easily Eaton s line of meters, relays, and software communication products integrate with Niagara AX products sold by Tridium, as well as over 30 different OEM partners. Modbus integration with Eaton meter, relay, and Gateway products Various products sold and distributed by Eaton support native Modbus communications through use of Modbus RTU over RS-485, as well as Modbus TCP. Both of these protocol driver options are available for Tridium Niagara AX products. Modbus RTU requires the use of the ModbusAsync module within Niagara AX. Modbus TCP requires the use of the ModbusTCP module within Niagara AX. Considerations of a local matter Prior to integrating s using the Niagara Framework, the following considerations should be taken into account. Protocol communication enablement Depending on where a Niagara Framework product was purchased, it may/may not be enabled to communicate ModbusT or BACnetT to field level devices. Communication drivers for Modbus, BACnet, and other protocols are separate license add-ons. Integrators should consult their supplier or vendor for information on licensing and obtaining drivers for their Niagara product. Communication port hardware Some Niagara Framework products ship with single or multiple communication ports. Integrators should carefully plan for scenarios involving multiple serial and Ethernet network topologies. Communication network speed Eaton products that support Modbus RTU are capable of supporting a wide variety of network baud rates. Configuration for network baud rate and slave address assignment can be achieved commonly through the local display of the unit or via Web browser for Ethernet enabled products. The most common configuration for Eaton meters and relays communicating Modbus is 9600 or bps, 8 Start Bits, No Parity, 1 Stop Bit. However, the integrator must make certain that the COM port on their hardware has been set appropriately to match the network. The following sections of this document provide qualification guidelines of Niagara AX connectivity s. Qualification is based on product family and connection methodology. IQ 35M family Modbus TCP via Power Xpert Gateway verified (Pass-Through and Cached) in Niagara must be set for IQ 130/140/150 family Modbus TCP direct verified Modbus TCP via Power XpertT Gateway verified (Pass-Through and Cached) in Niagara must be set for 2

3 Application Paper AP152001EN IQ 250/260 family Modbus TCP direct verified Modbus TCP via Power Xpert Gateway verified (Pass-Through and Cached) in Niagara must be set for Power Xpert Meter 2000 series Modbus TCP direct via Gateway card verified Order 1032 Modbus TCP via PXG verified (Pass-Through and Cached) in Niagara must be set for Integration considerations The Niagara AX Framework s Modbus implementation of register addressing revolves around the standard Modbus register range of To address extended register address ( ), integrators must address extended registers in hexadecimal format. This document later provides general guidance on how to achieve this. Power Xpert Meter 4000/6000/8000 series Modbus TCP direct verified Integration considerations The Niagara AX Framework is limited to support 32-bit floating point data type values natively. Some energy values contained within this family support double-precision floating point values (64-bit data). Integrators may find it necessary to use customized Niagara AX logic to combine two 32-bit registers to achieve proper value monitoring. Assistance for integrating 64-bit data can be obtained through Tridium s technical support services group as methods will vary based on an integrator s style of programming and commissioning. The Niagara AX Framework s Modbus implementation of register addressing revolves around the standard Modbus register range of To address extended register address ( ), integrators must address extended registers in hexadecimal format. This document later provides general guidance on how to achieve this. E-Series relay family Modbus TCP direct verified Modbus TCP via PXG verified (Pass-Through and Cached) in Niagara must be set for Integration considerations The Niagara AX Framework is limited to support 32-bit floating point data type values natively. Some energy values contained within this family support double-precision floating point values (64-bit data). Integrators may find it necessary to use customized Niagara AX logic to combine two 32-bit registers to achieve proper value monitoring. Assistance for integrating 64-bit data can be obtained through Tridium s technical support services group as methods will vary based on an integrator s style of programming and commissioning. The Niagara AX Framework s Modbus implementation of register addressing revolves around the standard Modbus register range of To address extended register address ( ), integrators must address extended registers in hexadecimal format. This document later provides general guidance on how to achieve this. 3

4 Application Paper AP152001EN RS-485 PONI (MPONI) Protocol enablement Order The New dialog will appear. Table 1. Niagara AX and Eaton Modbus Device Quick Reference Product Family Protocol Method Verified Modbus Byte/Float Order Config. IQ 35M Modbus RTU Direct Yes Order 3210 IQ 130/140/150 Modbus RTU Direct Yes Order 3210 Modbus TCP Direct Yes Order 3210 IQ 250/260 Modbus RTU Direct Yes Order 3210 Modbus TCP Direct Yes Order 3210 PXM2000 Modbus RTU Direct Yes Order 3210 Modbus TCP Gateway Card Yes Order 1032 PXM4/6/8K Modbus RTU Direct Yes Order 3210 Modbus TCP Direct Yes Order 3210 E-Series relay Modbus RTU Direct Yes Order 3210 Modbus TCP Direct Yes Order 3210 RS-485 PONI Modbus RTU Direct Yes Order 1032 Adding register channels will depend on the type of information you want to address. This is achieved by using the Type to Add and Data Type combo boxes. The table below provides general guidance on selections to make for specific common channels. Modbus Channel Type Niagara Type to Add Niagara Data Type (if applicable) Analog input Numeric point Float, long, or integer (based on device) Holding register Numeric point Float, long, or integer (based on device) Digital input Boolean point Boolean value Coil output Boolean point Boolean value Bit string Supports one of the following: Register bit point (for unsigned) Enumerated bit point (for enumerated value morphing) Numeric bit point (for float, long, and scaled integer morphing) Depends on bit point type selected 3. You can then assign a name to the channel point that describes what it is. If you incorrectly specified the Modbus Address and/or the Data Type and Register Type, you have the ability to change these parameters prior to clicking OK to create the point and add it into the database. If you selected a bit-string value, additional parameters will be available for the bit position you want to focus on, as well as the total number of bits. Modbus troubleshooting common configuration issues The following are common issues that could possibly be presented during a routine troubleshooting call involving with our products. Adding and working with basic Modbus register channels The Niagara AX Framework utilizes its framework standard for addressing Modbus registers. As a result, adding points into the system may not be as straightforward as it is with SCADA systems and other front-end software products commonly used in the electro-mechanical industry. To address a Modbus register channel in Niagara AX, perform the following steps: 1. From the Device s Point Database, click the New button. 4

5 Application Paper AP152001EN Modifying the Modbus byte order configuration in Niagara AX The most common problem observed with Niagara AX integrators attempting to communicate s is misconfiguration of the Modbus Byte Order within the client driver. By default, Niagara AX interprets Modbus register data in Order 3210 for all Modbus devices. Product dependent, the Byte Order (commonly referred to as Order 3210 or Order 1032) can be overridden at the device configuration level. To override, perform the following steps: 1. Right-click the Modbus device in question and select Views>Property Sheet. 2. In the Property Sheet View, expand Modbus Config. 3. Set Override Network = True. 4. Set Float Byte Order and Long Byte Order to the appropriate order based on device and connection method shown in the previous tables provided in this document. Niagara also provides expert controls for how write capabilities are used. By default, writing to registers with Niagara AX is done in a singular manner. For situations that require multiple registers to be written, the Force Multiple coil and Preset Multiple Register can be set to True if necessary. In most applications, however, this is unnecessary. Addressing extended registers with Niagara AX The Niagara AX Modbus implementation supports the ability to address registers in Decimal, Hex, or traditional Modbus format. The traditional Modbus format that Tridium uses only supports the standard 5-digit range (e.g., ). To address extended range registers, the register address must be converted to hex format and entered into Niagara AX. Niagara AX interprets hex register addresses to be one-based. Therefore, if an integrator is working with a zero-based device, they subtract a value of one from the register address prior to converting it to its hexadecimal value. In the example below, using a PXM2000 (a zero-based device), the Niagara Integrator may need to subtract a value of one from the extended register and then convert it to a hex value. Example: Frequency Register Address = The hexadecimal equivalent of is 2AF7. Resolving issues regarding slow data polling Niagara AX deterministically polls Modbus registers in a block manner; however, it has been known to fall back to reading each register individually in situations where a technician or a programmer may have entered registers into the system in a singular fashion. To configure Niagara AX to read multiple registers in a block fashion, you can have the technician configure the Device Poll Configuration. To do this, perform the following steps: 1. Right-click the Modbus device in question and select Views>Property Sheet. 2. In the Property Sheet View, find the Device Poll Config entry. 3. Right-click this entry, and select Actions>Learn Optimal Device Poll Configuration. 4. Niagara may prompt you to replace the existing configuration. Click OK to do so. The Device Poll Configuration node can be expanded to view the blocks upon which the registers are polled. Existing configuration entries can also be tweaked if necessary. 5

6 Application Paper AP152001EN BACnet integration with Eaton meter, relay, and Gateway products Specific products within Eaton s product line support BACnet network communications allowing most building automation systems to collect energy and other electrical data for use within BAS operation workstations and other software products. BACnet communications s occur over the BACnet/IP data link layer. BACnet/IP is a UDP-based network that supersedes the original BACnet/Ethernet (8802-3) networking layer. BACnet communications is performed using the bacnet module within Niagara AX. Virtual devices are considered downstream devices on a inter-connected BACnet network. Because BACnet uses flat communications architecture, the use of a unique network number is required. This network number, known as a virtual routing network number, is similar to a BACnet MS/TP network number. As such, the following rules apply: 1. The network number must be unique and cannot conflict with any downstream network presently in service on the network, e.g., BACnet MS/TP, BACnet PTP, etc. 2. Each virtual device will automatically include its own BACnet Device ID and MAC Address as assigned in our product setup configuration. Similar to native BACnet devices, each device (physical and virtual) must have its own unique device ID regardless of whether it exists on a different network number from other devices. Prior to setup and configuration, it is recommended that BAS integrators have a full understanding of their current BACnet network with respect to device IDs and previously assigned network numbers to reduce the potential for communication problems during commissioning. How BACnet applies to Eaton Eaton products operate as BACnet gateways consisting of a physical device acting as a router for downstream virtual IP devices. The figure below provides a simple illustration of this methodology. Data sharing via BACnet objects Eaton products use standard primitive BACnet object types for modeling electrical data parameters that we monitor. Eaton does not use proprietary objects and properties within its system architecture. This decision was made to ensure successful interoperability with most popular building automation systems. Eaton products conform to Protocol Revision 10 of the BACnet communication protocol standard. The following object types are used within our devices: Analog Input Binary Input Binary Value Device Multi-State Input Multi-State Value Character String Value Positive Integer Value Date Time Value It is important to note that Character String, Positive Integer, and Date Time Value objects were added to the standard in January of Niagara AX integrators should make certain that they are using the latest revision of programming tools available from Tridium that supports these objects. In many cases, Character String and Positive Integer objects hold read-only configuration data that may hold little to no value to BAS users. Date Time Value objects often hold Peak Event Occurrence Dates, but can be replicated with internal tools available to Tridium users. Niagara AX v3.8, Tridium products are capable of discovering and addressing all BACnet objects listed above. If you are using an earlier revision of Niagara AX, please contact your supplier regarding available software upgrades. 6

7 Application Paper AP152001EN BACnet device discovery of Eaton products The BACnet protocol supports an auto-discover of devices that are present on a properly configured BACnet network. As seen below, all devices residing on the LAN should reply appropriately to the inquiry that Niagara AX sends onto the network. Devices are returned upon the order in which Niagara polls for information. Devices can then be filtered and sorted through table views provided within Tridium s software. Devices can be sorted based on their assigned Device ID, Network Number (which is the Virtual Routing Network Number assigned within Eaton products), and model. 7

8 Application Paper AP152001EN BACnet troubleshooting common configuration issues The following are common issues that could happen during a routine troubleshooting call involving s. I can discover devices, but I cannot see data Sometimes, a caller may claim that they cannot see values, or values are coming into the system as question mark symbols. When this occurs, one of two issues are present. 1. The Virtual Routed Network Number configuration for the Eaton device either conflicts with another Eaton device or downstream BACnet network on the system. All Virtual Routed Network Numbers must be unique. a. One common issue many integrators cause is having the Tridium system s BACnet/IP network number conflict with the Virtual Routed Network Number in an Eaton product. Ensure that these values are unique. 2. The Device ID for the meter, the gateway card, and the I/O card conflict with another Eaton device or third-party BACnet device on the system. All devices must have a unique Device ID. I cannot override object values The Tridium Niagara AX Framework supports monitoring and control. Sometimes, a vendor may want to gain control of the Relay Outputs or Analog Outputs on a card that may be installed within a product. Eaton products reflect read-only data and do not support over the network control commands via BACnet. Eaton 1000 Eaton Boulevard Cleveland, OH United States Eaton.com 2014 Eaton All Rights Reserved Printed in USA Publication No. AP152001EN / Z15579 August 2014 Eaton is a registered trademark. All other trademarks are property of their respective owners.