. LIEBERT MONITORING GROUP OpenComms Network Interface Card INSTALLATION & USER MANUAL
Note To Our Valued Customer To help us better serve you, please contact us with any comments you have about this manual or product in general. We encourage you to comment and would appreciate your assistance in improving Liebert products. Liebert Monitoring Group Applications Engineering (U.S.) upstech@liebert.
Table of Contents Section 1: INTRODUCTION ...............................................................6 Specifications.....................................................................................7 Section 2: INSTALLATION ................................................................8 Retrofit Installation ............................................................................8 Environmental Installation.............................................................8 NPower Installation .....
Read/Write Holding Registers (0x03, 0x06, 0x10) ..............32 Read Input Registers (0x04) ....................................................32 Read, Set Coil Status (0x01, 0x05, 0x0F) .............................33 Read Input Status (0x02)..........................................................33 Error Handling ...........................................................................33 Modbus Packet Formats...............................................................
Internet Web Browser Network Management System Ethernet OpenComms NIC Modbus EIA-485 Building Management System Figure 1.
Section 1: INTRODUCTION The Liebert OpenComms Network Interface Card provides multiple connectivity options for your Liebert equipment. The OpenComms Network card transforms Liebert units to intelligent managed nodes on your network, enabling in-band communications with network management systems (NMS). For the first time, the system that monitors the well-being of your computing/communication infrastructure can comprehensively monitor your Liebert equipment as well.
SPECIFICATIONS Electrical Requirements: Voltage: 18VAC to 24VAC 50/60 Hz, Single Phase 12VDC to 36VDC Power: 6VA maximum Environmental Conditions: Operating Ambient Temperature: 5°C to 40°C 41°F to 104°F Storage Ambient Temperature: -20°C to 60°C -4°F to 140°F Relative Humidity: 10% to 90% RH (Non-condensing) Dimensions: Net: 178mm x 102mm x 38mm 7.0” x 4.0” x 1.5” As shipped: 178mm x 64mm 9.75” x 7.0” x 2.5" 0.2kg 0.4lbs 248mm 0.6kg 1.
Section 2: INSTALLATION The OpenComms NIC card may be ordered as a factory installed option, or in a kit for field retrofit to existing Liebert units or as a self-contained unit in its own enclosure. If ordered as a factory-installed option, proceed directly to subsection on User Connections. As a retrofit kit, the circuit board is secured to a metal mounting plate. The mounting plate then is attached to a flat metal surface in a low-voltage section of the Liebert unit.
Figure 2. Deluxe System/3 Control Cavity Figure 3.
Figure 4.
Figure 5. Challenger Installation Location The OpenComms Network card mounts to the Lplate for Challenger units.
System Wiring (SM, AM, AG Microprocessors) Two wiring harnesses are included with the retrofit kit, one for the power connection and the second for communications. They are of sufficient length for use with the Deluxe System/3 and ICS units and the microprocessors listed above. For the Challenger product series, use the longer wiring harnesses included with the NIC-K-Chall kit. NOTE: Board illustrations are shown only for location of connections.
Caution: Do NOT tap power from the auxiliary 24VAC terminals T5/G5 on the SM/AM/AG environmental controllers. Damage to controller and interface card may occur. Communication Connection (SM, AM, AG Microprocessor) The second wiring harness provided (p/n 159083G1) has a connector fitted at either end and is the communications connection between the unit microprocessor and the NIC. To put it in the system: 1.
MiniMate2 and Units Where Internal Mounting is Not Feasible An enclosure is recommended for use with ceiling-mounted environmental units or where internal mounting of the Network Interface Card is not feasible. Older-generation Deluxe and Challenger units may require external mounting. Power Connection for External Enclosures Power for the OpenComms Network card should be sourced from the supplied wall-plug transformer.
NPower Installation As a minimum there will be an IFM board (communications interface) mounted at the mid-point on the door. Other options may also have been previously installed. The Option boards mount on the inside of the option door. Options can be located in any available option slot, however the OpenComms – Network Interface Card should be mounted in the topmost (top cable entry) or bottom most (bottom cable entry) position.
Figure 7.
USER CONNECTIONS FOR OPENCOMMS NIC Since the OpenComms NIC can use simultaneous connections, Up to 3 user connections are may be required: a permanent network connection, a Modbus 485 connection and a temporary serial connection for configuration/setup. Confer with the network administrator or other responsible party for arranging a network drop to the Liebert equipment. The OpenComms Network card communicates via standard 10baseT Ethernet network connection.
Section 3: SYSTEM CONFIGURATION DIP SWITCH SETTINGS A four-position DIP switch is provided, but no user configuration via DIP switches is necessary at this time. SERVICE TERMINAL Refer to User Connections in Section 2 for instructions to physically connect to the serial port. By default, the service terminal communication parameters are: 9600 bps 8 data bits No parity 1 stop bit After connecting to the OpenComms NIC card, press the space bar or key to activate the service terminal session.
Service Terminal Navigation Main Menu 1. System Information 1.1 Name 1.2 Contact 1.3 Location 1.4 Description 2. Network Interface 2.1 Speed / Duplex [fixed] 2.2 Boot Mode 2.2.1 Static 2.2.2 BootP 2.2.3 DHCP 2.3 IP Address 2.4 NetMask 2.5 Default Gateway 3. SNMP Communications 3.1 Enable SNMP agent [y/n] 3.2 Enable Authentication Traps [y/n] 3.3 Display / Modify Communities 3.4 Display / Modify Trap Communities 4. Web Server 4.1 Enable Web Server [y/n] 4.2 Change User Name / Password 4.2.
1. System Information Menu The System Information Menu seeks descriptive input to enable the unit to be identified. This data is readable via SNMP queries. The (“) character is not permitted in any of the descriptive fields 2. Network Interface Menu The Network Interface Menu configures network parameters essential for proper network operation. The network administrator or other personnel responsible for the network should be consulted for the proper parameters to be entered in this menu.
is received. When this condition is encountered, pushing the "enter" key returns the unit to the service terminal mode. 3. SNMP Communications Menu The SNMP (Simple Network Management Protocol) Communications Menu specifies parameters particular to the SNMP interface. Communities are used as a means of security for SNMP v1; only specified hosts with the appropriate community name(s) are allowed to perform particular SNMP operations. Up to 20 different communities can be assigned.
5. Firmware Update Menu The Firmware Update Menu is intended for Liebert service personnel only. No user configurable parameters are accessed in this selection. If entered, to escape, power must be cycled on the card. 6. Factory Settings Menu The Factory Settings Menu displays the manufacture date, serial number and MAC address of the card. These parameters are read-only.
Section 4: OPERATION SNMP The OpenComms Network Interface Card supports “get,” “getnext,” “set,” “response” and “trap” packets of SNMP (Simple Network Management Protocol). The OpenComms NIC supports MIB-II, RFC1628 and Liebert Global Products MIBs. The terms, “alarms” and “conditions” will be used interchangeably through out this description. Alarms are generated and maintained through the RFC 1628 UPS MIB. Conditions are generated and maintained through the Liebert Global Products MIB.
provides the condition ID, the condition description, and the condition time. RFC 1628 UPS MIB UPS units log alarms in the RFC 1628 UPS MIB. Traps for the UPS units are generated out of the RFC 1628 UPS MIB. There are four traps that may be sent for the UPS units: Trap On Battery, Trap Test Completed, Trap Alarm Entry Added and Trap Alarm Entry Removed. The Trap on Battery is sent when the UPS is operating on battery power.
The MIBs for the OpenComms Network Interface Card are available for download on the Liebert Web site, www.liebert.com. Navigate through Products, then Site Monitoring & Software and proceed to the OpenComms support information area. The RCF 1628 MIB can be downloaded at www.ietf.org (the Internet Engineering Task Force). Physical media containing MIB files do not ship with the hardware. HTTP Status and alarm information can be queried by web browsers via HTTP v1.1 (Hyper Text Transfer Protocol).
MODBUS RTU See Section 5 for a complete explanation of the Modbus slave. SYSTEM RESET The OpenComms Network card contains an on-board real time clock and watchdog circuitry. The card is self-monitoring and self-correcting. Nevertheless, a pushbutton is provided in the event that a manual system reset in desired. The Reset pushbutton is labeled S1 on the interface card: press and hold for 3 seconds before to releasing to initiate hardware reset.
DS13 DS14-19 IGM Port Transmit Not used Figure 8.
Section 5: MODBUS COMMUNICATIONS & CONNECTIVITY This section describes the Modbus communications protocol as supported by the OpenComms NIC card. It includes information on how to pass information to and from the OpenComms NIC card via Modbus. It is also intended to help facilitate answering questions regarding supported types, frame format, function code support etc.
delay time if HTTP, SNMP and Modbus are going to be utilized simultaneously. TRANSMISSION FORMAT The OpenComms NIC module supports Modbus RTU (Remote Terminal Unit) transmission modes. The OpenComms NIC communication rate is fixed at 9600 baud, 8 data bits, No parity, 1 Stop bit. The communication media is fixed using EIA-485 standards. PHYSICAL CONNECTION A Modbus network should consist of one, and only one, host client, and up to 255 slaves uniquely identifiable by their slave ID.
Modbus RTU Master EIA-485 9600,N,8,1 Maximum of 32 devices with a total cable length of 4000feet. Figure 9.
Modbus RTU Master EIA-485 9600,N,8,1 Maximum of 32 devices with a total cable length of 4000feet. R Maximum of 32 devices with a total cable length of 4000feet. R Maximum of 32 devices with a total cable length of 4000feet. Figure 10. Exceeding Maximum Specifications The maximum specification may be exceeded if measures are taken to drive or boost the EIA-485 communication line. Two wire EIA485 repeaters are available through the Liebert Corpration.
A datum should consist of one or multiple registers. The leftmost byte contains the MSB and the rightmost byte contains the LSB. Function Code Support The OpenComms NIC implements the following Modbus functions. However, integrators will use function code 0x03, and 0x06 most often due to the type of data to be acquired.
Up to 125 input registers can be read by a single query using function code 0x04. Read, Set Coil Status (0x01, 0x05, 0x0F) Coil status contains bit-mapped status accessible to the users. In principle, a coil status can be read, set or cleared by the host client. Multiple coil status can be read by specifying the index of bits of the first coil and the number of consecutive coils in a single query. Coil status can be read by function code 0x01.
Exception Response Server Address 1 byte Function Code (0x80) 1 byte Exception code 1 bytes 16 bit CRC 2 bytes Exception code is one of the following: 01: Unsupported Function code 02: Out-of-range data addresses 03: Out-of-range data value (write to holding registers) 04: There is currently no LMD device connected to the server 05: Server is composing response but cannot response to the client within the time limit required by Modbus specification.
Function Code: The function code field tells the addressed slaves what function to perform. Function codes are specifically designed invoke a specific action by the slave device. The function code range is from 1 to 127. However, the OpenComms NIC module primarily uses Function Code 3 (Read Holding Registers) and Function Code 6 (Preset Single Register). Data Field(s): The data field varies in length depending on whether the message is a request or a response to a packet.
RTU Framing Examples READ REGISTERS (FUNCTION CODE 0X03 & 0X04) Query: for reading holding /input registers (requested by a client) Server Function Index of Number of 16 bit Addres Code starting register registers to be read CRC s (0x3/0x4) 1 byte 1 byte 2 bytes 2 bytes 2 bytes Response: for reading holding/input registers (response by the server) Server Function Byte Data from registers 16 bit Addres Code Count CRC s (0x3/0x4) 1 byte 1 byte 1 2*m bytes (= Byte Count) 2 bytes bytes WRITE SINGLE HOLDING REG
Section 6: NIC Setup and Testing The NIC has a specific setup that must be in place before the card will function properly. There are jumpers on the board that must be in the correct locations. The positions of these jumpers are numbered on the board itself. A small triangle silk screened on the board represents pin 1 for each set of pins to which jumpers may be applied. JUMPER PLACEMENTS J13, J14, and J18 on the board must have jumpers installed on them. J32 must have a jumper installed on pins 2 and 3.
requests. Once the information has been verified, press to return to the main menu and select “x” to exit out of the card. Then, reboot the card. The card may be rebooted by pressing switch S1 on the card for approximately 2 seconds until the DS9 link light turns off. If the card still does not connect to the network, or ping still does not receive a reply from the card, verify proper set up on the card itself. DS4 should be illuminated if the card detects the network.
Once this information is verified, reboot the card and try to access SNMP again. WEB TROUBLESHOOTING If the card does not serve up a web page, but the Service Terminal is functioning, SNMP is functioning, and the card is connected to the network (verified through ping), then reboot the card. In this case, the web server has been lost and needs to be restarted.
Also verify that the proper slave ID has be set in service terminal.
OpenComms NIC Network Interface Card THE COMPANY BEHIND THE PRODUCTS With more than 500,000 installations around the globe, Liebert is the world leader in computer protection systems. Since its founding in 1965, Liebert has developed a complete range of support and protection systems for sensitive electronics: • • • • • Environmental systems: precision air conditioning from 1.5 to 60 tons. Power conditioning and UPS with power ranges from 250 VA to more than 1000 kVA.
