English dropdown-ico

Emerson MONITORING OpenComms manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Emerson MONITORING OpenComms, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Emerson MONITORING OpenComms one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Emerson MONITORING OpenComms. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Emerson MONITORING OpenComms should contain:
- informations concerning technical data of Emerson MONITORING OpenComms
- name of the manufacturer and a year of construction of the Emerson MONITORING OpenComms item
- rules of operation, control and maintenance of the Emerson MONITORING OpenComms item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Emerson MONITORING OpenComms alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Emerson MONITORING OpenComms, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Emerson service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Emerson MONITORING OpenComms.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Emerson MONITORING OpenComms item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    M ONITORING OpenComms NIC U SER M ANUAL[...]

  • Page 2

    [...]

  • Page 3

    i T ABLE OF CONTENTS 1.0 I NTRODUCT ION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 OpenComms Compatibility . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 I NST ALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1 Retrofit Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [...]

  • Page 4

    ii 5.4 Modbus Slave Functions . . . . . . . . . . . . . . . . . . . . . . . . 21 5.4.1 Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.4.2 Function Code Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.4.3 Read/Write Hol ding Registers ( 0x03, 0x0 6, 0x10) . . . . . . 22 5.4.4 Read Input [...]

  • Page 5

    iii 9.3 Power Connection (SM, AM, AG Microprocessors). . . . 37 9.3.1 Power Connection (Level 0 and Level 10 Microprocessors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 9.3.2 Commu nication Connection (SM, AM, AG Microprocessor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 9.3.3 Commu nication Connect[...]

  • Page 6

    iv FIGURES Figure 1 Typical installation of Open Comms NIC card . . . . . . . . . . . . . . . 1 Figure 2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 3 Null modem cable diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 4 NIC main menu in H yperTerminal . . . . . [...]

  • Page 7

    Introduction 1 1.0 I 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 bro wsers (I.E. 5.5 o r later) • SNMP (v1, v2c) for net[...]

  • Page 8

    Introduction 2 1.1 OpenComms Comp atibility The OpenComms NIC may be installed and used with these units: Environmental Units • Deluxe Syst em3—Advanced Mi croprocessor with Graphics, Advanced Microprocessor and standard microprocessor • Challenger 3000—Ad vanced Microprocessor with Graphics, Advanced Microprocessor and standard microproces[...]

  • Page 9

    Introduction 3 Retrofit Kits are designed specif ically for individual unit s. Consult your local Emerson and Liebert sales representative for pricin g, part numbers and installation help. T able 1 OpenComms availability Unit Factory Option Retrofit Kit Retrofit Kit Part # Environmental Products Deluxe System 3 and ICS Yes Yes NIC-K-SYS3 Challenger[...]

  • Page 10

    Introduction 4 T able 2 Specifica tions Electrical Requirements Voltage 18 to 24VAC 50/60 Hz, Single Phase 12 to 36VDC Power 6VA maximum Environmental Conditions, °F (°C) Operating Ambient Temperat ure 41 to 104 (5 to 40) Storage Ambient Temperatur e -4 to 140 (-20 to 60) Relative Humidity 10% to 90% RH (Non-condensing) Dimensions, Inches (mm) Un[...]

  • Page 11

    Installation 5 2.0 I NSTA LLATION The OpenComms NIC card may be ordered as a factory- installed option, and it may be inst alled as a kit for field retrofit to existing Li e- bert units or as a self-conta ined unit in its own enclosure. If ordered as a factory-installed option, proceed to 2.3 - User Connec- tions for OpenComms NIC . 2.1 Retrofit Ki[...]

  • Page 12

    Installation 6 2.3 User Connections for OpenComms NIC The OpenComms NIC can use simult aneous connectio ns, sometimes requiring three user connections: • Permanent network connection • Modbus 485 connection • Temporary serial connectio n for configuration/setup 2.3.1 Network Port Consult with the network administrator or other responsibl e pa[...]

  • Page 13

    Installation 7 Accessing the Configuration Port What you will need: • PC capable of running a terminal emu lation application, such as Microsoft Windows® HyperTerminal®. • DB9 Null modem or fil e 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 comput ers sto[...]

  • Page 14

    Installation 8 the Enter key on your keyboard . Th is will initia te communications with the card and the following screen should be displayed. Figure 4 NIC main me nu in HyperT erminal (You can also cycle po wer on the OpenComm s NIC card. This will also initiate communication s and provide information on current revision status.) 6. When the mess[...]

  • Page 15

    System Configuration 9 3.0 S YSTEM C ONFIGURATION 3.1 DIP Switch Settings A four-position DIP switch is provided, but no user configuration via DIP switches is necessary at this time. 3.2 Service T erminal Refer to Accessing the Configuration Port on page 7 for expl icit details on accessing the service terminal / configuration port. By default, th[...]

  • Page 16

    System Configuration 10 T able 3 Service terminal navigatio n Main M enu 1. System Inf ormation 1.1 Nam e 1.2 Contact 1.3 Locatio n 1.4 Description 2. Network Setting s 2.1 Boot / IP Setting s 2.1.1 B oot Mode 2.1.1.1 Static 2.1.1.2 Boot P 2.1.1.3 DHCP 2.1.2 IP Addr ess 2.1.3 Ne tmask 2.1.4 Default Gateway 2.2 SNMP Communications 2.2.1 SNMP agent ([...]

  • Page 17

    System Configuration 11 System Information Menu The System Information Menu seeks descriptive input to enable the unit to be identified. This data is readabl e via SNMP queries. The (“) character is not permitted in any of the descriptiv e fields Network Settings Menu The Network Settings Menu configur es network parameters essential for proper n[...]

  • Page 18

    System Configuration 12 destination IP ad dress, and th e comm unity name for that host. Up to 20 trap communities can be assi gned. For Communities and Trap Communities, the informati on can be entered as a “complex” line — all parameters space-delimited on the command line. Otherwise, the menu items will prompt for each indi vidual paramete[...]

  • Page 19

    System Configuration 13 Auxiliary Communications The Auxiliary Communicati ons Menu al lows the user to set up the parameters necessary for Modbus communications. The user can enable / disa ble the Modb us s essions as well as assign the slave ID. Q. <q> will abort all changes. X. <x> will save configuration changes. Once all parameters[...]

  • Page 20

    Operation 14 4.0 O PERATION 4.1 SNMP The OpenComms Network Interface Ca rd supports “get,” “getnext,” “set,” “response” and “trap” packets of SNMP (Simple Network M an- agement Protocol). The OpenC omms NIC supports MIB-II, RFC1628 and Liebert Global Products MIBs. The terms “al arms” and “condi- tions” will be used inte[...]

  • Page 21

    Operation 15 4.3 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 Ad ded and Trap Alarm En try Removed. The trap On Battery is sent when the UPS is operating[...]

  • Page 22

    Operation 16 [OIDALARMS] 1.3.6.1. 2.1.33.1.6. 3.1:upsAla rmBatteryBad{ } 1.3.6.1. 2.1.33.1. 6.3.2:up sAlarmOn Battery{} 1.3.6.1. 2.1.33.1.6. 3.3:upsAla rmLowBattery {} 1.3.6.1.2.1 .33.1.6. 3.4:upsAla rmDepletedBattery {} 1.3.6.1. 2.1.33.1.6. 3.5:upsAl armTempBa d{} 1.3.6.1. 2.1.33.1 .6.3.6: upsAlarm InputB ad{} 1.3.6.1. 2.1.33.1. 6.3.7:up sAlarmOu [...]

  • Page 23

    Operation 17 4.4 MIB The Management Informat ion Base (MIB) is a formal document declaring the specifics of the information suppo rted by the SNMP implementation. The administrator fo r the NMS (or other applications utilizing SNMP to communicate with the Liebert units will need the MIB in order to integrate the Lie b ert units into the monitoring [...]

  • Page 24

    Operation 18 4.8 Diagnostics A number of LEDs are p rovided on the inte rface card to provide i nfor- mation for diagnostic purposes. The f ollowing table summarizes their indications: Figure 5 LED locations LED Identifier Description DS1 Ethernet Port Collision DS2 Ethernet Port Receive DS3 Ethernet Port Transmit DS4 Ethernet Port Link DS5 Not use[...]

  • Page 25

    Modbus Communi cations and Conn ectivity 19 5.0 M ODBUS C OMMUNICATIONS AND C ONNECTIVITY This section describes the Modbus communications protocol as sup- ported by the OpenComms NIC card. It includes in formation on how to pass information to and from the OpenComms NI C card via Mod- bus. It is also intended to h elp fa cilitate answering questio[...]

  • Page 26

    Modbus Communi cations and Conn ectivity 20 5.3 Physical Connection A Modbus network should consist of on e, and only one, h ost client, and up to 255 slaves uniquely ident ifiab le by their slave ID . The slave ID of each OpenComms NIC is set thro ugh the service terminal (configu- ration) port. (See section 3, System Configuration for more detail[...]

  • Page 27

    Modbus Communi cations and Conn ectivity 21 Figure 7 Exceeding maximum specifications The maximum specification may be ex ceeded if measures are taken to drive or boost the EIA-485 communic ation line. Two wire EIA485 repeaters are available through the Liebert Corporation. SiteScan’s “REPOPT” will work sufficiently for this application. Cons[...]

  • Page 28

    Modbus Communi cations and Conn ectivity 22 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 da ta to be acquired. 5.4.3 Read/Write Holdin g Registers (0x03, 0x06, 0x10) A holding register is a 16-bit message unit. In pri[...]

  • Page 29

    Modbus Communi cations and Conn ectivity 23 5.4.6 Read Input St atus (0x02) The input status block contains read-only status accessible to the users. It can b e read by us ing functi on code 0x02 in the same as read- ing coil status. 5.4.7 Error Handling According to the Modb us specificat io n, the OpenComms NIC compo ses the followin g exception [...]

  • Page 30

    Modbus Communi cations and Conn ectivity 24 the OpenComms NIC module primaril y uses Function Code 3 (Rea d Holding Regis ters) and Fu nction Code 6 (Preset Single Re gister). Data Field(s) The data field varies in length de pending on whether t he message is a request or a respon se to a packet. This field typically contains infor- mation required[...]

  • Page 31

    NIC Setup and Testing 25 6.0 NIC S ETUP AND T ESTING The NIC has a specific setup that must be in place befo re the card will function properly. There are jumpers on th e board that must be in the correct locations. The positions of these jumpers are numbered on the board itself. A small tri angle silk[...]

  • Page 32

    NIC Setup and Testing 26 6.2 T esting the Network “Ping” is a tool used to test the network. At the command prompt, type, “ping <address of card>”. Ping will respond t hat it received a reply from the card if the card is functioning properly on the network. If the card is not functioning proper ly or is not connecting to the net- work[...]

  • Page 33

    NIC Setup and Testing 27 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 na me when trying to access SNMP. The community name is case sensitive. Once this information i s verified, reboot the card and try to access SNMP again.[...]

  • Page 34

    Firmware Update s 28 7.0 F IRMWARE U P DATES The firmware in the OpenComms NI C card can be updated to take advantage o f the latest relea se of software th at may contain feature enhancements, new unit compatibility or service pa tches. The firm- ware is updated through the Open Co mms NIC cards’ serial port, using a terminal emulation program l[...]

  • Page 35

    Firmware Update s 29 7.2 Est ablishing Communication—Service T erminal Settings 1. Launch HyperTerminal. O nce you see the following screen, select Cancel . 2. Select the disconnect icon from the menu bar . This step ensures that you will be able to modify the configur ation settings. 3. Go to File > Properties to make configuration changes. U[...]

  • Page 36

    Firmware Update s 30 7.3 Firmware Up date Procedure 1. After the communication settings are adjusted, press the Enter key on your keyboard. This will initia te 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 in i- tiate communicati ons and provide information[...]

  • Page 37

    Firmware Update s 31 8. When the above prompt is displayed, start the file dow nload process by selecting Transfer – Send File… from the HyperTerminal menu, as shown at right. 9. Select Xmodem fo r the Protocol and browse to locate the file OCNIC_REVx.x00.0_BL Dxxx_FILE1.s19 . 10. Click on Send in the dialog box. 11. The screen at right will ap[...]

  • Page 38

    Firmware Update s 32 Once the last file is downloaded, the screen at right w ill appear. Repeat Steps 2 through 4 to change the baud rate back to 9600 bps as show in the il lustration below right. After the communication settings are adjusted, hit the Enter key on your key- board. The scree n at right will ap pear. You can also cycle power on the O[...]

  • Page 39

    External Enclosures 33 8.0 E XTERNAL E NCLOSURES 8.1 Power Connection Power for the OpenComms Network ca rd should be sourced from the supplied wall-plug transf ormer. Use field-supplied wiring to connect the outer terminals on th e transformer to the s crew connectors at TB3 on the Network Interface card. A fiel d-su pplied ground w ire attaches t[...]

  • Page 40

    Retrofit Installation 34 9.0 R ETROFIT I NST ALLATION 9.1 Environment al Inst allation Retrofit kits are designed specifically for indi vidual units. Consult your local Liebert representative fo r pricing, part numbers and instal- lation help. 9.1.1 Deluxe System/3 Position the OpenComms ca rd in the low voltage/contro l cavity of the Liebert Delux[...]

  • Page 41

    Retrofit Installation 35 Figure 1 1 Deluxe System 3 chilled water control cavity Figure 12 ICS control cavity P25 P43 TB1 TB2 - Connect s to screw terminals 77 and 78; (see schematic) TB3 P25 P43 TB1 TB2 - Connects to screw terminals 77 and 78; (see schematic) TB3[...]

  • Page 42

    Retrofit Installation 36 Figure 13 Challenger inst allation location The OpenComms Network ca rd mounts on the Challenger ’ s L-plate. P25 P43 TB1 TB2 - Connects to screw terminals 77 and 78; (see schematic) TB3 Electric Panel[...]

  • Page 43

    Retrofit Installation 37 9.2 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. Th ey are of suf- ficient length for use with the Delu xe System/3 and ICS units and the microprocessors listed above. For the Challenger product series, use[...]

  • Page 44

    Retrofit Installation 38 9.3.2 Communication Connection (SM, AM, AG Microprocessor) The second wiring harness provided (p/n 1590 83G1) has a connector fitted at either end and is the co mmunications connection between the unit microprocessor and the NIC. To put it in the system: 1. Remove the existing wire loca ted on P25 of the environm ental cont[...]

  • Page 45

    Retrofit Installation 39 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. Th ey are of suf- ficient length for us e with the Himod unit. 9.4.2 Power Connection (Himod) The harness supplied with the Op enComms Network Interface Card (p/n 159084G 1) is[...]

  • Page 46

    Retrofit Installation 40 9.6 Emerson Network Po wer (CEMS100 / LECS15) The kit includes a special cable to a llow simple interconnection between the controller and the OpenComms NIC. Questions about the retrofit kits sh ould be directed to the Interna- tional Sales departmen t. Contact: yc.kok@emersonnetwork.com.au 9.7 UPS Inst allation Retrofit ki[...]

  • Page 47

    Retrofit Installation 41 Figure 15 NPower UPS NIC inst allation Power Supply Board Option Section SiteScan IFM OpenComms NIC location (see detail) Control Door IGMnet Deta il 24V AC[...]

  • Page 48

    Retrofit Installation 42 9.9 7200 UPS Retrofit Kits are designed specif ically for individual unit s. Consult your local sales / service representa tive for pricing, part numbers and installation help. Refer to the UPS user manual for more details. If you encounter any problems with the procedures contained in this manual contact your loca l Lieber[...]

  • Page 49

    Retrofit Installation 43 Figure 16 7200 UPS NIC inst allation Logic Operator Board Network Interface Card[...]

  • Page 50

    Retrofit Installation 44 9.10 HiPulse UPS Retrofit Kits are designed specif ically for individual unit s. Consult your local sales / service representa tive for pricing, part numbers and installation help. Refer to the UPS or Network Interf ace Card user manual for more details. If you encounter any problems with the procedures contained in this ma[...]

  • Page 51

    Retrofit Installation 45 Figure 17 HiPulse inst allation[...]

  • Page 52

    Retrofit Installation 46 9.1 1 St atic Switch2 Retrofit kits are designed specifically for indi vidual units. Consult your local sales / service representa tive for pricing, part numbers and installation help. Figure 18 STS2 typical NIC loca tion Figure 19 STS2 NIC inst allation, 800-1000A unit s NETWORK INTERFACE CARD (NIC) 416241GX 1 3 2 TB2 P18 [...]

  • Page 53

    Retrofit Installation 47 Figure 20 STS2 NIC inst al lation, 100 - 600A unit s 9.12 STS Retrofit kits are designed specifically for indi vidual units. Consult your local sales / service representa tive for pricing, part numbers and installation help. STS units require the use of an exte rnal enclosure. Consult the corre- sponding section of th is ma[...]

  • Page 54

    Retrofit Installation 48[...]

  • Page 55

    [...]

  • Page 56

    T echnical Suppo rt / Service Web S it e www .liebert.com Monitoring 800-222-5877 monitoring@liebert.com Outside the US: 614-841-6755 Single-Phase UPS 800-222-5877 upstech@liebert.c om Outside the US: 614-841-6755 Three-Phase UPS 800-543-2378 powertech@liebert.com Environment al Systems 800-543-2778 Outside the United St ates 614-888-0246 Locations[...]