Table of Contents
Advertisement
Advertisement
Table of Contents
Troubleshooting
Related Manuals for Liebert MONITORING OpenComms
Summary of Contents for Liebert MONITORING OpenComms
- Page 1 ONITORING OpenComms NIC ANUAL...
-
Page 3: Table Of Contents
TABLE OF CONTENTS NTRODUCTION OpenComms Compatibility ..... . . 2 NSTALLATION Retrofit Kit ........5 Self-Contained Unit . - Page 4 Modbus Slave Functions ......21 5.4.1 Data Type........21 5.4.2 Function Code Support .
- Page 5 Mini-Mate2 ........39 Emerson Network Power (CEMS100 / LECS15) ..40 UPS Installation.
- Page 6 Figure 1 Typical installation of OpenComms NIC card ....1 Figure 2 Connections ......... . 5 Figure 3 Null modem cable diagram .
-
Page 7: Introduction
NTRODUCTION The OpenComms NIC Card transforms Liebert units into manageable nodes within your Network, NMS, and BMS systems. The OpenComms NIC Card contains a standard Ethernet and EIA-485 (2-wire) port designed to support viewing and management through: • HTTP for Web browsers (I.E. 5.5 or later) •... -
Page 8: Opencomms Compatibility
• Mini-Mate2 • Level 00—Deluxe System3, Challenger 3000 • Level 10—Deluxe System3, Challenger 3000 • Level 05/15 (UK) • Himod • Emerson Network Power (CEMS100 / LECS15) 3-Phase UPS • Npower • Hiross 7200 (Italy) • Hiross HiPulse (Italy) 3-Phase Power •... -
Page 9: Table 1 Opencomms Availability
Contact your sales / service representative or liebert global services for installation. For Australian units, contact the international sales department @ YC.KOK@emersonnetwork.com.au Retrofit Kits are designed specifically for individual units. Consult your local Emerson and Liebert sales representative for pricing, part numbers and installation help. Factory Retrofit... -
Page 10: Table 2 Specifications
Table 2 Specifications Electrical Requirements Environmental Conditions, °F (°C) Operating Ambient Temperature Storage Ambient Temperature Relative Humidity Dimensions, Inches (mm) Weight, lb (kg) Voltage Power 10% to 90% RH (Non-condensing) Unit Only 7 x 4 x 1.5 (178 x 102 x 38) As Shipped 9.75 x 7.0 x 2.5 (248 x 178 x 64) Unit Only... -
Page 11: Installation
NSTALLATION The OpenComms NIC card may be ordered as a factory-installed option, and it may be installed as a kit for field retrofit to existing Lie- bert units or as a self-contained unit in its own enclosure. If ordered as a factory-installed option, proceed to 2.3 - User Connec- tions for OpenComms NIC. -
Page 12: User Connections For Opencomms Nic
NIC communicates via standard 10 Base-T Ethernet network connec- tion. Route the 10 Base-T cable to the Liebert unit and connect to J3, the RJ45 jack on the interface card. The OpenComms Network card will operate with any 10 Base-T Ethernet, regardless of operating sys- tem used. -
Page 13: Figure 3 Null Modem Cable Diagram
Accessing the Configuration Port What you will need: • PC capable of running a terminal emulation application, such as Microsoft Windows® HyperTerminal®. • DB9 Null modem or file transfer cable. (The correct cable will have at a minimum, pins 2 and 3 crossed at the ends.) Null modem cables are commonly found in computers stores and may also be referred to as a file transfer cable. -
Page 14: Figure 4 Nic Main Menu In Hyperterminal
the Enter key on your keyboard. This will initiate communications with the card and the following screen should be displayed. Figure 4 NIC main menu in HyperTerminal (You can also cycle power on the OpenComms NIC card. This will also initiate communications and provide information on current revision status.) 6. -
Page 15: System Configuration
YSTEM 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 Accessing the Configuration Port on page 7 for explicit details on accessing the service terminal / configuration port. By default, the service terminal communication parameters are: •... -
Page 16: Table 3 Service Terminal Navigation
Table 3 Service terminal navigation Main Menu 1. System Information 1.1 Name 1.2 Contact 1.3 Location 1.4 Description 2. Network Settings 2.1 Boot / IP Settings 2.1.1 Boot Mode 2.1.2 IP Address 2.1.3 Netmask 2.1.4 Default Gateway 2.2 SNMP Communications 2.2.1 SNMP agent (enable/disable) 2.2.2 Authentication Traps (enable/disable) 2.2.3 Display / Modify Communities... -
Page 17: System Information Menu
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 Network Settings Menu The Network Settings Menu configures network parameters essential for proper network operation. -
Page 18: Factory Settings Menu
destination IP address, and the community name for that host. Up to 20 trap communities can be assigned. For Communities and Trap Communities, the information can be entered as a “complex” line — all parameters space-delimited on the command line. Otherwise, the menu items will prompt for each individual parameter. -
Page 19: Auxiliary Communications
Auxiliary Communications The Auxiliary Communications Menu allows the user to set up the parameters necessary for Modbus communications. The user can enable / disable the Modbus sessions as well as assign the slave ID. Q. <q> will abort all changes. X. -
Page 20: Operation
PERATION SNMP The OpenComms Network Interface Card supports “get,” “getnext,” “set,” “response” and “trap” packets of SNMP (Simple Network Man- agement Protocol). The OpenComms NIC supports MIB-II, RFC1628 and Liebert Global Products MIBs. The terms “alarms” and “condi- tions” will be used interchangeably through out this description. Alarms are generated and maintained through the RFC 1628 UPS MIB. -
Page 21: Rfc 1628 Ups Mib
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. - Page 22 [OIDALARMS] 1.3.6.1.2.1.33.1.6.3.1:upsAlarmBatteryBad{} 1.3.6.1.2.1.33.1.6.3.2:upsAlarmOnBattery{} 1.3.6.1.2.1.33.1.6.3.3:upsAlarmLowBattery{} 1.3.6.1.2.1.33.1.6.3.4:upsAlarmDepletedBattery{} 1.3.6.1.2.1.33.1.6.3.5:upsAlarmTempBad{} 1.3.6.1.2.1.33.1.6.3.6:upsAlarmInputBad{} 1.3.6.1.2.1.33.1.6.3.7:upsAlarmOutputBad{} 1.3.6.1.2.1.33.1.6.3.8:upsAlarmOutputOverload{} 1.3.6.1.2.1.33.1.6.3.9:upsAlarmOnByPass{} 1.3.6.1.2.1.33.1.6.3.10:upsAlarmBypassBad{} 1.3.6.1.2.1.33.1.6.3.11:upsAlarmOutputOffAsRequested{} 1.3.6.1.2.1.33.1.6.3.12:upsAlarmUpsOffAsRequested{} 1.3.6.1.2.1.33.1.6.3.13:upsAlarmChargerFailed{} 1.3.6.1.2.1.33.1.6.3.14:upsAlarmUpsOutputOff{} 1.3.6.1.2.1.33.1.6.3.15:upsAlarmUpsSystemOff{} 1.3.6.1.2.1.33.1.6.3.16:upsAlarmFanFailure{} 1.3.6.1.2.1.33.1.6.3.17:upsAlarmFuseFailure{} 1.3.6.1.2.1.33.1.6.3.18:upsAlarmGeneralFault{} 1.3.6.1.2.1.33.1.6.3.19:upsAlarmDiagnosticTestFailed{} 1.3.6.1.2.1.33.1.6.3.20:upsAlarmCommunicationsLost{} 1.3.6.1.2.1.33.1.6.3.21:upsAlarmAwaitingPower{} 1.3.6.1.2.1.33.1.6.3.22:upsAlarmShutdownPending{} 1.3.6.1.2.1.33.1.6.3.23:upsAlarmShutdownImminent{} 1.3.6.1.2.1.33.1.6.3.24:upsAlarmTestInProgress{} To summarize, event traps generally are parsed by the NMS for any of the information contained in the trap. A process should be put in place by the NMS to recognize whether the event trap is a new condition or a cleared condition by looking at the trap type.
-
Page 23: Mib
See 5.0 - Modbus Communications and Connectivity for a com- plete 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-correct- ing. However, a push button is provided to permit a manual system reset. -
Page 24: Diagnostics
Diagnostics A number of LEDs are provided on the interface card to provide infor- mation for diagnostic purposes. The following table summarizes their indications: Description Identifier Ethernet Port Collision Ethernet Port Receive Ethernet Port Transmit Ethernet Port Link Not used Not used Repeater Port Receive IGM Port Receive... -
Page 25: Modbus Communications And Connectivity
ODBUS This section describes the Modbus communications protocol as sup- ported by the OpenComms NIC card. It includes information on how to pass information to and from the OpenComms NIC card via Mod- bus. It is also intended to help facilitate answering questions regard- ing supported types, frame format, function code support etc. -
Page 26: Physical Connection
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. The slave ID of each OpenComms NIC is set through the service terminal (configu- ration) port. (See section 3, System Configuration for more details.) The OpenComms NIC supports multi-drop connection over RS485. -
Page 27: Modbus Slave Functions
Figure 7 Exceeding maximum specifications Modbus RTU Master EIA-485 9600,N,8,1 Maximum of 32 devices with combine cable length of 4000 feet Modbus RTU Master EIA-485 9600,N,8,1 Maximum of 32 devices with combine cable length of 4000 feet The maximum specification may be exceeded if measures are taken to drive or boost the EIA-485 communication line. -
Page 28: Function Code Support
5.4.2 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. 0x01 Read Coil Status 0x02 Read Input Status 0x03 Read Holding Registers 0x04... -
Page 29: Read Input Status (0X02)
5.4.6 Read Input Status (0x02) The input status block contains read-only status accessible to the users. It can be read by using function code 0x02 in the same as read- ing coil status. 5.4.7 Error Handling According to the Modbus specification, the OpenComms NIC composes the following exception responses to the client if an exception or error occurs. -
Page 30: Rtu Framing Examples
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. This field typically contains infor- mation required by the slave device to perform the command specified or to pass back data to the master device. -
Page 31: Nic Setup And Testing
NIC Setup and Testing NIC S ETUP AND ESTING 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. -
Page 32: Testing The Network
Testing the Network “Ping” is a tool used to test the network. At the command prompt, type, “ping <address of card>”. Ping will respond that it received a reply from the card if the card is functioning properly on the network. If the card is not functioning properly or is not connecting to the net- work, ping will respond that the request it sent to the card has timed out. -
Page 33: Web Troubleshooting
Then, select number 2 for Display/Modify Communities. Verify that the IP Addresses listed are valid for your network. Verify that you are typing in the correct community name when trying to access SNMP. The community name is case sensitive. Once this information is verified, reboot the card and try to access SNMP again. -
Page 34: Firmware
IRMWARE The firmware in the OpenComms NIC card can be updated to take advantage of the latest release of software that may contain feature enhancements, new unit compatibility or service patches. The firm- ware is updated through the OpenComms NIC cards’ serial port, using a terminal emulation program like HyperTerminal in MS Windows Operating Systems. -
Page 35: Establishing Communication-Service Terminal
Establishing Communication—Service Terminal Settings 1. Launch HyperTerminal. Once you see the following screen, select Cancel. 2. Select the disconnect icon from the menu bar step ensures that you will be able to modify the configuration settings. 3. Go to File > Properties to make configuration changes. -
Page 36: Firmware Update Procedure
Firmware Update Procedure 1. After the communication settings are adjusted, press the Enter key on your keyboard. This will initiate communications with the card and display the screen at right. You can also cycle power on the Open- Comms NIC card. This action will also ini- tiate communications and provide information on current revision status. - Page 37 8. When the above prompt is displayed, start the file download process by selecting Transfer – Send File… from the HyperTerminal menu, as shown at right. 9. Select Xmodem for the Protocol and browse to locate the file OCNIC_REVx.x00.0_BLDxxx_FILE1.s19. 10. Click on Send in the dialog box. NOTE Do not press any keys on your keyboard or the firmware download will abort.
- Page 38 Firmware Updates Once the last file is downloaded, the screen at right will appear. Repeat Steps 2 through 4 to change the baud rate back to 9600 bps as show in the illustration below right. After the communication settings are adjusted, hit the Enter key on your key- board.
-
Page 39: External
XTERNAL Power Connection Power for the OpenComms Network card should be sourced from the supplied wall-plug transformer. Use field-supplied wiring to connect the outer terminals on the transformer to the screw connectors at TB3 on the Network Interface card. A field-supplied ground wire attaches to the center terminal on the transformer and connects to the ground- ing stud in the lower corner of the enclosure. -
Page 40: Retrofit
ETROFIT Environmental Installation Retrofit kits are designed specifically for individual units. Consult your local Liebert representative for pricing, part numbers and instal- lation help. 9.1.1 Deluxe System/3 Position the OpenComms card in the low voltage/control cavity of the Liebert Deluxe System 3 unit. Refer to Figures 10, 11 and 12 for typ- ical positioning. -
Page 41: Figure 11 Deluxe System 3 Chilled Water Control Cavity
Figure 11 Deluxe System 3 chilled water control cavity TB2 - Connects to screw terminals 77 and 78; (see schematic) Figure 12 ICS control cavity TB2 - Connects to screw terminals 77 and 78; (see schematic) Retrofit Installation... -
Page 42: Figure 13 Challenger Installation Location
Retrofit Installation Figure 13 Challenger installation location TB2 - Connects to screw terminals 77 and 78; (see schematic) Electric Panel The OpenComms Network card mounts on the Challenger’s L-plate. -
Page 43: System Wiring (Sm, Am, Ag Microprocessors)
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 suf- ficient length for use with the Deluxe System/3 and ICS units and the microprocessors listed above. -
Page 44: Communication Connection
9.3.2 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. Remove the existing wire located on P25 of the environmental controller, cut off the red connector and reconnect the wires to TB2 of the interface card. -
Page 45: System Wiring (Himod)
9.4.1 System Wiring (Himod) Two wiring harnesses are included with the retrofit kit, one for the power connection and the second for communications. They are of suf- ficient length for use with the Himod unit. NOTE Board illustrations are shown only for location of connections. Board location and wire length may change depending upon the specific installation. -
Page 46: Emerson Network Power (Cems100 / Lecs15)
Emerson Network Power (CEMS100 / LECS15) The kit includes a special cable to allow simple interconnection between the controller and the OpenComms NIC. Questions about the retrofit kits should be directed to the Interna- tional Sales department. Contact: yc.kok@emersonnetwork.com.au UPS Installation Retrofit kits are designed specifically for individual units. -
Page 47: Figure 15 Npower Ups Nic Installation
Figure 15 NPower UPS NIC installation Power Supply Board Control Door Option Section SiteScan IFM 24VAC Detail Retrofit Installation OpenComms NIC location (see detail) IGMnet... -
Page 48: 7200 Ups
7200 UPS Retrofit Kits are designed specifically for individual units. Consult your local sales / service representative for pricing, part numbers and installation help. CAUTION Before installing the kit P/N 4645114G for Network Interface Card (P/N 4590063X), in the 7200 Series UPS, it is necessary to power down that unit. -
Page 49: Figure 16 7200 Ups Nic Installation
Retrofit Installation Figure 16 7200 UPS NIC installation Logic Operator Board Network Interface Card... -
Page 50: Hipulse Ups
9.10 HiPulse UPS Retrofit Kits are designed specifically for individual units. Consult your local sales / service representative for pricing, part numbers and installation help. CAUTION Before installing the kit P/N 4645114D for Network Interface Card (P/N 4590063X), in the HiPulse UPS, it is necessary to power down that unit. -
Page 51: Figure 17 Hipulse Installation
Retrofit Installation Figure 17 HiPulse installation... -
Page 52: Static Switch2
9.11 Static Switch2 Retrofit kits are designed specifically for individual units. Consult your local sales / service representative for pricing, part numbers and installation help. Figure 18 STS2 typical NIC location RS-232 (DB-9 connector) for setup only. Uses standard computer serial port cable NETWORK INTERFACE CARD (NIC) 416241GX See Note 2... -
Page 53: Sts
Figure 20 STS2 NIC installation, 100 - 600A units CONTROL WIRING Front View With Front Door Removed 9.12 Retrofit kits are designed specifically for individual units. Consult your local sales / service representative for pricing, part numbers and installation help. STS units require the use of an external enclosure. - Page 54 Retrofit Installation...
- Page 56 OpenComms NIC The Company Behind the Products With over a million 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: •...