Emerson MONITORING OpenComms User manual

MONITORING
OpenComms NIC-485
USER MANUAL
TABLE OF CONTENTS
1.0
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1
OpenComms Compatibility . . . . . . . . . . . . . . . . . . . . . . . 1
2.0
INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1
2.2
2.3
Retrofit Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Self-Contained Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
User Connections for OpenComms NIC-485 . . . . . . . . . 4
2.3.1
2.3.2
BMS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Configuration Port / Service Terminal . . . . . . . . . . . . . . . . 4
3.0
SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . 7
3.1
3.2
DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Service Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.0
OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1
4.2
4.3
Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
System Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.0
MODBUS COMMUNICATION AND CONNECTIVITY . . . . . . 12
5.1
5.2
5.3
5.4
Implementation Basics . . . . . . . . . . . . . . . . . . . . . . . . . 12
Transmission Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Physical Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Modbus Slave Functions . . . . . . . . . . . . . . . . . . . . . . . . 14
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.5
Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Read/Write Holding Registers (0x03, 0x06, 0x10) . . . . . . 15
Read Input Registers (0x04) . . . . . . . . . . . . . . . . . . . . . . . 15
Read, Set Coil Status (0x01, 0x05, 0x0F) . . . . . . . . . . . . . 15
Read Input Status (0x02) . . . . . . . . . . . . . . . . . . . . . . . . . 16
Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
RTU Framing Examples . . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.1
5.5.2
Read Registers—Function Code 0x03 & 0x04 . . . . . . . . . 17
Write Single Holding Register—Function Code 0x06 . . . 17
6.0
NIC-485 SETUP AND TESTING . . . . . . . . . . . . . . . . . . 18
6.1
6.2
6.3
Jumper Placements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Service Terminal Troubleshooting . . . . . . . . . . . . . . . . 18
Modbus Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 18
i
7.0
FIRMWARE UPDATES . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1
7.3
Establishing Communication—Necessary
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Establishing Communication—Service Terminal
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Firmware Update Procedure . . . . . . . . . . . . . . . . . . . . . 21
8.0
EXTERNAL ENCLOSURES . . . . . . . . . . . . . . . . . . . . . . 24
8.1
8.2
Power Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Communication Connection. . . . . . . . . . . . . . . . . . . . . . 24
9.0
RETROFIT INSTALLATION . . . . . . . . . . . . . . . . . . . . . . 25
9.1
Environmental Installation . . . . . . . . . . . . . . . . . . . . . . 25
7.2
9.1.1
9.2
9.3
Deluxe System/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
System Wiring—SM, AM, AG Microprocessors . . . . . . 28
Power Connection—SM, AM, AG Microprocessors . . . 28
9.3.1
9.3.2
9.3.3
9.4
Power Connection—Level 0 and Level 10
Microprocessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Communication Connection—SM, AM, AG
Microprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Communication Connection—Level 0 and Level 10
Microprocessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Himod—LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.4.1
9.4.2
9.4.3
9.5
9.6
9.7
9.8
System Wiring for Himod . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power Connection for Himod . . . . . . . . . . . . . . . . . . . . . . 31
Communication Connection for Himod . . . . . . . . . . . . . . 31
Mini-Mate2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Emerson Network Power (CEMS100 / LECS15) . . . . . 31
UPS Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Npower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9.8.1
9.8.2
9.9
9.10
9.11
9.12
9.13
Power Connection for NPower . . . . . . . . . . . . . . . . . . . . . 32
Communication Connection for NPower . . . . . . . . . . . . . 32
7200 UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
HiPulse UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Static Switch2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
STS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
PDU and DataWave with PMP & EPMP . . . . . . . . . . . 39
ii
FIGURES
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Null modem cable diagram . . . . . . . . . . . . . . . . . . . . . . . . . 5
NIC-485 main menu in HyperTerminal . . . . . . . . . . . . . . . 6
LED Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Typical maximum installation . . . . . . . . . . . . . . . . . . . . . . 13
Exceeding maximum specifications . . . . . . . . . . . . . . . . . . 14
NIC485-ENCL1 internal view . . . . . . . . . . . . . . . . . . . . . . 24
Deluxe System 3 NIC-485 installation . . . . . . . . . . . . . . . 25
Deluxe System 3 chilled water NIC-485 installation . . . . 26
ICS NIC-485 installation . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Challenger NIC-485 installation location . . . . . . . . . . . . . 27
Himod NIC-485 installation location. . . . . . . . . . . . . . . . . 30
NPower UPS NIC-485 installation . . . . . . . . . . . . . . . . . . 33
7200 UPS NIC-485 installation . . . . . . . . . . . . . . . . . . . . . 35
HiPulse NIC-485 installation. . . . . . . . . . . . . . . . . . . . . . . 37
STS2 typical NIC-485 connections. . . . . . . . . . . . . . . . . . . 38
STS2 NIC-485 installation, 800-1000A units . . . . . . . . . . 38
STS2 NIC-485 installation, 100 - 600A units . . . . . . . . . . 39
TABLES
Table 1
Table 2
Table 3
Table 4
Table 5
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
DIP switch default settings . . . . . . . . . . . . . . . . . . . . . . . . . 7
Service terminal navigation . . . . . . . . . . . . . . . . . . . . . . . . . 8
LED function indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Exception response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
iii
iv
Introduction
1.0
INTRODUCTION
The OpenComms NIC-485 transforms Liebert units into manageable
nodes within your BMS systems.
The OpenComms NIC-485 contains a standard EIA-485 (two-wire) port
designed to support viewing and management through Modbus RTU for
building management systems and SiteScan.
This standard open protocol allows simple integration into your monitoring system, leveraging prior infrastructure investments and established procedures.
1.1
OpenComms Compatibility
The OpenComms NIC-485 may be installed and used with these units:
Environmental Units
• Deluxe System3—Advanced Microprocessor with Graphics,
Advanced Microprocessor and standard microprocessor
• Challenger 3000—Advanced Microprocessor with Graphics,
Advanced Microprocessor and standard microprocessor
• 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
• PDU with PMP or EPMP monitoring
• DataWave with PMP or EPMP monitoring
• Static Switch
• Static Switch2
• Static Switch2/PDU
NOTE
All units are manufactured in North America unless otherwise
noted.
1
Introduction
Table 1
Specifications
Electrical Requirements
Voltage
18 to 24VAC
50/60 Hz, Single Phase
12 to 36VDC
Power
6VA maximum
Environmental Conditions, °F (°C)
Operating Ambient Temperature
41 to 104 (5 to 40)
Storage Ambient Temperature
-4 to 140 (-20 to 60)
Relative Humidity
10% to 90% RH (Non-condensing)
Dimensions, Inches (mm)
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)
Weight, lb (kg)
Unit Only
0.4 (0.2)
As Shipped
1.3 (0.6)
2
Installation
2.0
INSTALLATION
The OpenComms NIC-485 may be ordered as a factory-installed
option, and it may be installed as 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 to 2.3 - User Connections for OpenComms NIC-485.
2.1
Retrofit Kit
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.
2.2
Self-Contained Unit
The self-contained model packages the interface card inside a steel
enclosure, for mounting external to the Liebert unit. A low-voltage
transformer is also provided.
Figure 1
Connections
IGMnet or SiteScan
Comms from Unit
(input to TB1)
Input Power
(Input to TB3)
Modbus Output for BMS
(Output from TB2)
DTE Serial Port
for Configuration
3
Installation
2.3
User Connections for OpenComms NIC-485
Since the OpenComms NIC-485 can use simultaneous connections two
user connections may be required:
• Modbus 485 connection
• Temporary serial connection for configuration/setup
2.3.1
BMS Port
The Modbus 485 connection will use the terminals marked “Repeater.”
(TB2) The Modbus server uses RTU protocol and will allow for a maximum of 32 units on 4000ft. of wire on a common line. EIA-485 repeaters may be necessary to accommodate additional units or longer
cables. Point availability may be referenced in the document,
“SiteScan Reference Library,” which may be downloaded at
www.liebert.com under the OpenComms product family.
2.3.2
Configuration Port / Service Terminal
A temporary serial connection to the interface card is necessary for
configuration and setup.
Using a DB9F-DB9F null-modem cable, connect the “DTE Serial Port”
P18 to an ASCII terminal or computer running terminal emulation
application. HyperTerminal® and Procomm® are examples of terminal emulation applications running on Microsoft Windows® operating
systems. All trademarks are the property of their respective owners.
4
Installation
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.
Figure 2
Null modem cable diagram
DTE Device
Receive Rx (pin2)
Null Connection
Transmit Tx (pin3)
DTE Device
Receive Rx (pin2)
Transmit Tx (pin3)
NOTE
Turn off the power management on your PC or laptop to ensure
that the communication port will not “go to sleep” during the
configuration process.
1. Launch HyperTerminal. When you see the
screen at right, select Cancel.
2. Select the disconnect icon from the menu bar.
This step ensures that you will be able to
modify the configuration settings.
3. Go to File > Properties to make
configuration changes. Under the Connect
To setting, choose the appropriate communication port for your
computer. Generally this is Com 1.
4. Select the Configure button
and adjust the terminal
communication settings to:
• Bits per second: 9600
• Data Bits: 8
• Parity: None
• Stop Bits: 1
• Flow Control: None
• Select OK to close both windows.
5
Installation
5. After the communication settings are adjusted, press the Enter
key on your keyboard. This will initiate communication with the
card and Figure 3 should appear.
Figure 3
NIC-485 main menu in HyperTerminal
(You can also cycle power on the OpenComms NIC-485. This will
also initiate communication and provide information on current
revision status.)
6. When the message “Initializing Network…” appears, hit the
Enter key on your keyboard. (Additional network information
may appear)
!
CAUTION
Cycling power on either the 7200 or the HiPulse UPS is not
recommended unless the unit is in bypass mode. Consult the
UPS user manual for further instructions.
6
System Configuration
3.0
SYSTEM CONFIGURATION
3.1
DIP Switch Settings
A four-position DIP-switch is provided, but no user configuration via
DIP switches is necessary at this time.
Table 2
DIP
Switch
DIP switch default settings
Default
Setting
S2.1
Off
S2-2
Off
S2-3
Off
S2-4
Off
J13
Pin 1-2
J14
Pin 1-2
J18
Pin 1-2
J28
Pin 2-3
J32
Pin 2-3
P19
Open
7
System Configuration
3.2
Service Terminal
Refer to Accessing the Configuration Port on page 5 for details
on accessing the service terminal / configuration port.
The default service terminal communication parameters are:
• 9600 bps
• No parity
• 8 data bits
• 1 stop bit
• Flow Control: None
After connecting to the OpenComms NIC-485, press the space bar or
Enter key to activate the service terminal session. If no response is
apparent and you have verified connectivity, cycle power on the
Open-Comms NIC-485 and the service terminal sessions should
appear automatically.
!
CAUTION
Cycling power on either the 7200 or the HiPulse UPS is not
recommended unless the unit is in bypass mode. Consult the
UPS user manual for further instructions.
Table 3
Service terminal navigation
Main Menu
1.0 Firmware Updates
1.1 Initiate XMODEM Update
2.0 Factory Settings
2.1 Reset to Factory Defaults
2.2 Manufacture Date
(Read Only)
2.3 Serial Number
(Read Only)
2.4 Boot Version
(Read Only)
2.5 App Version
(Read Only)
2.6 Hardware Version
(Read Only)
3.0 Modbus Server
3.1 Control
3.2 Server ID
3.3 Communication Rate
(Read Only)
q Quit and abort changes
x Exit and save
8
System Configuration
Change User Name / Password
This section allows users to set or change the default user name and
password.
• Default user name is “Liebert” (case sensitive).
• Default password is “Liebert” (case sensitive).
Firmware Updates 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.
Factory Settings Menu
The Factory Settings Menu displays the manufacture date, serial
number and MAC address of the card. These parameters are readonly. Once all parameters have been entered, press Escape to return
to the Main menu; then press x to save configuration, exit and reboot
to enable the new configuration. All parameters are stored in non-volatile flash memory. Pressing q after Escape will abort all changes.
Neither selection is case-sensitive.
Auxiliary Communication
The Auxiliary Communication Menu allows the user to set up the
parameters necessary for Modbus communication. The user can
enable / disable the Modbus sessions as well as assign the slave ID.
Q. <q> will abort all changes.
X. <x> will save configuration changes.
Once all parameters have been entered, press <escape> to return
to the Main menu; then press exit and reboot using the new configuration. All parameters are stored in non-volatile flash memory.
Neither selection is case-sensitive.
9
Operation
4.0
OPERATION
4.1
Modbus RTU
See 5.0 - Modbus Communication and Connectivity for information about the Modbus slave.
4.2
System Reset
The OpenComms NIC-485 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.
4.3
Diagnostics
A number of LEDs are provided on the interface card to provide information for diagnostic purposes. The following table summarizes their
indications:
Table 4
LED function indicators
LED
Identifier
Description
DS1
N/A
DS2
N/A
DS3
N/A
DS4
N/A
DS5
Not used
DS6
Not used
DS7
Repeater Port Receive
DS8
IGM Port Receive
DS9
Microprocessor in Operation
DS10
Serial Port Receive
DS11
Serial Port Transmit
DS12
Repeater Port Transmit
DS13
IGM Port Transmit
DS14-19
Not used
10
Operation
Figure 4
LED Locations
DS8
DS9
DS8
DS13
11
Modbus Communication and Connectivity
5.0
MODBUS COMMUNICATION AND CONNECTIVITY
This section describes the Modbus communication protocol as supported by the OpenComms NIC-485. It includes information on how to
pass information to and from the OpenComms NIC-485 via Modbus. It
is also intended to help facilitate answering questions regarding supported types, frame format, function code support etc.
5.1
Implementation Basics
Protocol controls the language structure or message format between
devices in other words, the rules for communication. The rules for
communication include how master and slave devices initiate communication, as well as unit identification, message handling and error
checking. Modbus protocol simply refers to the control of the query
and response cycles between master and slave devices.
The OpenComms NIC-485 module is configured to act as a slave
device on a common network. The common network is a multi-drop or
daisy chain configuration over EIA-485, where multiple slaves reside
on a common wire or loop.
5.2
Transmission Format
The OpenComms NIC-485 module supports Modbus RTU (Remote
Terminal Unit) transmission modes. The OpenComms NIC-485 communication rate is fixed at 9600 baud, 8 data bits, No parity, 1 Stop
bit. The communication media is fixed using EIA-485 standards.
5.3
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-485 is set through the service terminal (configuration) port. (See 3.0 - System Configuration for details.) The OpenComms NIC-485 supports multi-drop connection over RS485. On the
OpenComms NIC-485, a client should connect to the OpenComms
NIC584 as a multi-drop connection via the RS485 “Repeater” port (TB2),
(Pin1 as minus and Pin2 as plus. J28-1 and J28-2 should be shorted.)
The OpenComms NIC485 card is designed to reside on a maximum
common line of 32 devices with a total cable length of 4000 feet. In a
“normal environment” all devices should be connected in “daisy-chain”
fashion, with “star configurations” or branches, being used at a minimum. See Figure 5 for details. A “normal environment” consists of an
installation where noise or electrical interference is minimal. This is
typical of communication wiring run in properly grounded conduit or
in areas where high voltage or radio transmissions are not present.
Otherwise, these conditions are designated as “noisy.”
12
Modbus Communication and Connectivity
Figure 5
Typical maximum installation
Modbus RTU Master
EIA-485 9600,N,8,1
Maximum of 32
devices with combined
cable length of 4000
feet
The recommended cable characteristics are:
Normal Environments:
• 18-22 gauge, twisted-pair, stranded (non- shielded)
Typical type is: Belden 8442
Noisy Environments:
• 18-22 gauge, twisted-pair, stranded (shielded)
Typical type is: Belden 9461
13
Modbus Communication and Connectivity
Figure 6
Exceeding maximum specifications
Modbus RTU Master
EIA-485 9600,N,8,1
Maximum of 32
devices with combined
cable length of 4000
feet
R
Modbus RTU Master
EIA-485 9600,N,8,1
R
Maximum of 32
devices with combined
cable length of 4000
feet
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 Corporation. SiteScan’s
“REPOPT” will work sufficiently for this application. Consult the
SiteScan price book for pricing schedule and alternative solutions.
5.4
Modbus Slave Functions
5.4.1
Data Type
The OpenComms NIC-485 supports data in a register block as one of
the following types: Signed integer (16 bit) / Unsigned integer (16 bit) /
Signed long (32 bit); IEEE floating-point (32 bit); Null terminated
String.
A datum should consist of one or multiple registers. The leftmost byte
contains the MSB and the rightmost byte contains the LSB.
14
Modbus Communication and Connectivity
Function Code Support
The OpenComms NIC-485 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
Read Input Registers
0x06
Write Single Holding Register
0x0F
Force Multiple Coils
0x10
Preset Multiple Holding Registers
5.4.2
Read/Write Holding Registers (0x03, 0x06, 0x10)
A holding register is a 16-bit message unit. In principle, a message in
a holding register is write / readable, but holding registers can be used
by read-only data as well. Holding registers are mapped into 4000149999 logic address range.
Holding registers can be read by function code 0x03. A maximum of
125 registers can be read by a single query.
Function code 0x06 requests the server to change the content of a single holding register, and function code 0x10 requests server to change
the contents of multiple holding registers adjacent to each other.
5.4.3
Read Input Registers (0x04)
The input register block contains read-only data accessible to the user.
A datum in the input register block occupies one or multiple registers
such as described in the previous section. The input registers are
mapped into 30000-39999 of the logic address range.
Up to 125 input registers can be read by a single query using function
code 0x04.
5.4.4
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.
Function code 0x05 set or clear a single coil, and function code 0x0F
set or clear multiple coils.
15
Modbus Communication and Connectivity
5.4.5
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 reading coil status.
5.4.6
Error Handling
According to the Modbus specification, the OpenComms NIC-485 composes the following exception responses to the client if an exception or
error occurs.
Table 5
Exception response
Server
Address
Function Code
(0x80)
Exception
Code
16 Bit
CRC
1 byte
1 byte
1 byte
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.
Modbus Packet Formats
Each Modbus packet consists of the following fields:
• Device Address
• Function Code
• Data Field(s)
• Error Check Field
Device Address
The address field immediately follows the beginning of the frame and
consists of eight bits. These bits indicate the user assigned address of
the slave device that is to receive the message sent by the attached
master device.
Each slave OpenComms NIC-485 must be assigned a unique address
and only the addressed slave will respond to a query that contains its
address.
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-485 module primarily uses Function Code 3
(Read Holding Registers) and Function Code 6 (Preset Single Register).
16
Modbus Communication and Connectivity
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 information required by the slave device to perform the command specified
or to pass back data to the master device.
Error Check Field
The Error Check Field consists of a 16-bit (2 byte) Cyclical Redundancy Check (CRC16). It allows the receiving device to detect a packet
that has been corrupted with transmission errors.
5.5
RTU Framing Examples
5.5.1
Read Registers—Function Code 0x03 & 0x04
Query: for reading holding /input registers (requested by a client)
Server
Address
Function Code
(0x3/0x4)
Index of starting
register
Number of
registers to
be read
16 bit
CRC
1 byte
1 byte
2 bytes
2 bytes
2 bytes
Response: for reading holding/input registers (response by the
server)
Server
Address
Function Code
(0x3/0x4)
Byte
Count
Data from
registers
16 bit
CRC
1 byte
1 byte
1 byte
2*m bytes (= Byte Count)
2 bytes
5.5.2
Write Single Holding Register—Function Code 0x06
Query: for writing a single holding register (requested by a client)
Server
Address
Function Code
(0x06)
Index of
the register
16 bit value
to be written
16 bit
CRC
1 byte
1 byte
2 bytes
2 bytes
2 bytes
Response: for writing a holding registers (response by the server)
Server
Address
Function Code
(0x06)
Index of
the register
16 bit value
been written
16 bit
CRC
1 byte
1 byte
2 bytes
2 bytes
2 bytes
17
NIC-485 Setup and Testing
6.0
NIC-485 SETUP AND TESTING
The NIC-485 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.
6.1
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.
J28 jumper positions will apply to future capabilities, but are not currently usable on the NIC-485.
NOTE
Your card was shipped with the jumpers properly installed.
6.2
Service Terminal Troubleshooting
If the card does not bring up a Service Terminal, check link light DS9.
DS9 should be illuminated within approximately 0.5 seconds of application of power. If DS9 is not illuminated and no other LED's are on,
verify that power has been applied to the card. If power has been
applied, verify wiring connected to TB3 is correct. TB3 should have
24VAC or 12 VDC applied. Reboot the card once the power to the card
has been verified.
6.3
Modbus Troubleshooting
If the card does not respond to Modbus requests, verify that DS7,
“repeater port receive” is flashing during a request. In proper communication DS12 will also be flashing indicating, “repeater port transmit”
Verify proper wiring on the EIA 485 network. Each OpenComms NIC485 should observe a “plus to plus” and “minus to minus” daisy chain
configuration.
Also verify that the proper slave ID has been set in service terminal.
Refer to 3.2 - Service Terminal for initiating a service terminal session
18
Firmware Updates
7.0
FIRMWARE UPDATES
The firmware in the OpenComms NIC-485 can be updated to take
advantage of the latest release of software that may contain feature
enhancements, new unit compatibility or service patches. The firmware is updated through the OpenComms NIC-485’s serial port, using
a terminal emulation program like HyperTerminal in MS Windows
Operating Systems. This procedure has multiple steps and requires
that three files be downloaded to the OpenComms NIC-485. The latest
firmware can be found at the following link:
http://www.liebert.com/dynamic/displayproduct.asp?id=1133&cycles=60hz
!
7.1
CAUTION
Read all instructions before to attempting a firmware
download.
Establishing Communication—Necessary
Components
• PC capable of running a terminal emulation application, such as
HyperTerminal.
• DB9 null modem or file transfer cable. (The correct cable will have
at a minimum, pins 2 and 3 crossed at the ends.)
• Firmware update files (3 files total with extensions of .s19)
NOTE
Turn off the power management on your PC or laptop to ensure
that the communication port will not “go to sleep” during the
upgrade process and corrupt the firmware on the OpenComms
NIC-485.
19
Firmware Updates
7.2
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
. This step
ensures that you will be able to
modify the configuration
settings.
3. Go to File > Properties to make
configuration changes. Under
the Connect To setting, choose
the appropriate communication
port for your computer. Generally this is Com 1.
4. Select the Configure button and adjust the terminal
communication settings to:
• Bits per second: 9600
• Data Bits: 8
• Parity: None
• Stop Bit: 1
• Flow Control: None
5. Select OK to close both windows.
20
Firmware Updates
7.3
!
Firmware Update Procedure
CAUTION
The firmware download process is timed. After the firmware
download is initiated as described below, the user has
approximately 1 minute to finish initialization. Before
beginning the download, determine the location of the
firmware files so that the download can be completed within
the time constraints.
1. After the communication settings are
adjusted, press the Enter key on your
keyboard. This will initiate
communication with the card and
display the screen at right.
You can also cycle power on the OpenComms NIC-485. This action will also
initiate communication and provide
information on current revision status.
Once the “Initializing Network…”
line appears, hit the Enter key on your
keyboard. (Additional network information may appear.)
2. Select the option for Firmware
Updates. Only one selection is offered.
Press 1.
3. When asked “Are you sure…” press Y.
4. 9.) Select the option to change the card’s communication rate to
115200 bps. The prompt line will advise you of the baud rate
change.
5. End the HyperTerminal session and adjust the communication
rate to match the card.
6. Pressing Enter will reestablish communication
with the card. This will
display the screen at right.
7. Pressing Enter again will
initiate the file download
process. The screen at
right should appear.
21
Firmware Updates
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. 15.) Click on Send in the dialog box.
NOTE
Do not press any keys on your keyboard or the firmware
download will abort.
11. The screen at right will appear
when the download begins.
The screen will display the
download progress,
disappearing when the
download is complete.
12. Once the file has completed
downloading, a prompt will
ask whether you with to
continue. Select Y to continue.
13. Select option 2 for Xmodem1K to
facilitate a faster download for the
remaining files. Press Enter twice
to initiate the download of the
second firmware file.
14. Select Transfer – Send File…
from the HyperTerminal menu.
15. Select 1K Xmodem for the protocol and browse to the location of:
OCNIC_REVx.x00.0_BLDxxx_FILE2.s19
16. Select Send; a progress prompt will be displayed.
Repeat Steps 11 through 16 to download the third firmware file. It is
named OCNIC_REVx.x00.0_BLDxxx_FILE3.s19
NOTE
The last file is the largest of the three and will take
approximately 20 minutes to download.
22
Firmware Updates
Once the last file is downloaded, the screen below 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
keyboard. The screen at right will
appear.
You can also cycle power on the OpenComms NIC-485. This action will also
initiate communication and provide
information on current revision status. Once the “Initializing Network…” line appears, hit the Enter
key on your keyboard.
Select X and the card will reboot.
To ensure that the latest firmware is
downloaded to the OpenComms
NIC-485, cycle power by removing
and restoring the power connection at
TB3. The information below will
appear.
NOTE
The information above, such as version values and numbers,
will change as Liebert releases new firmware.
23
External Enclosures
8.0
EXTERNAL ENCLOSURES
8.1
Power Connection
Power for the OpenComms NIC-485 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 NIC-485. A field-supplied ground wire attaches to the center terminal on the transformer and connects to the grounding stud in the
lower corner of the enclosure.
Figure 7
NIC485-ENCL1 internal view
To SiteScan
connection
terminals on unit
Refer to specific unit installation
communication connection
Field-supplied
use 18AWG
8.2
Communication Connection
Communication with the OpenComm NIC-485 is generally established by using the unit’s SiteScan interface port. The specifics on
location and wiring details can be found in the respective unit’s user
manual.
The unit’s communication port is EIA-422, which measures ~3-5VDC
between the positive and negative terminals. The connection is polarity sensitive, so use a voltmeter to verify polarity. The connection is
positive-to-positive and, negative-tonegative-. The result when the
card and the unit are connected together, a voltmeter will measure ~
3-5 VDC. Once proper communication has been established, voltage
readings will fluctuate.
24
Retrofit Installation
9.0
RETROFIT INSTALLATION
9.1
Environmental Installation
Retrofit kits are designed specifically for individual units. Consult
your local Liebert representative for pricing, part numbers and installation 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 8, 9 and 10 for typical
positioning. Use three #8 x 1/2" sheet metal screws to affix mounting
plate to the environmental unit.
Figure 8
Deluxe System 3 NIC-485 installation
P43
TB1 - Connects to
screw terminals
77 and 78
(see schematic)
TB1
P25
NIC-485 Board
25
Retrofit Installation
Figure 9
Deluxe System 3 chilled water NIC-485 installation
TB3
P43
P25
TB1
TB2 - Connects to screw terminals
77 and 78; (see schematic)
Figure 10 ICS NIC-485 installation
TB3
TB1
TB1 - Connects
to screw terminals
77 and 78;
(see schematic)
P43
P25
26
Retrofit Installation
Figure 11 Challenger NIC-485 installation location
TB1
TB3
TB1 - Connects to
screw terminals 77 and
78; (see schematic)
P43
P25
Electric Panel
The OpenComms NIC-485 mounts on the Challenger’s L-plate.
27
Retrofit Installation
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 communication. 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 NIC485-K-Chall kit.
NOTE
Board illustrations are shown only for location of connections.
Board location and wire length will change depending upon
the specific installation.
9.3
Power Connection—SM, AM, AG Microprocessors
The harness supplied with the OpenComms NIC-485
(p/n 159084G1) is equipped with three connectors, one at either end of
the harness and one in the middle. The harness taps power from the
24 VAC input to the control board of the environmental unit. To connect this power to the NIC-485:
1. 1. Locate the connector containing the two red wires plugged into
P43 on the control board and unplug it. Reconnect it to the
connector in the middle of the supplied harness.
2. 2. Plug one end of this harness into P43 on the control board and
the other end into TB3 of the OpenComms card.
9.3.1
Power Connection—Level 0 and Level 10
Microprocessors
To connect power to the NIC-485, wire as described above. However,
some field modification of the wiring harnesses is necessary for connection to legacy systems.
Level 0: Remove the power connector normally plugged into P43 and
wire to terminal connections 1-5 (24V)/1-10 (ground).
!
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.
28
Retrofit Installation
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 communication connection between the
unit microprocessor and the NIC-485.
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. Ensure correct polarity.
2. Connect one end of the wire harness to TB1 of the interface card;
the other end connects to P25 of the environmental controller.
9.3.3
Communication Connection—Level 0 and Level 10
Microprocessors
To connect communication wire to the NIC-485, wire as described
above. However, some field modifications of the wiring harnesses are
necessary for connection to legacy systems. Level 0 and Level 10:
Remove the red connector normally plugged into P25. Wire to terminal connection P25.
29
Retrofit Installation
9.4
Himod—LNA
Position the OpenComms card in the low voltage/control cavity of the
Liebert Himod unit. Refer to the drawing below for typical positioning.
Use three #8 x ½” sheet metal screws to affix mounting plate to the
Environmental unit.
Figure 12 Himod NIC-485 installation location
ATTENTION
USE COPPER
CONDUCTORS ONLY
ONE (OR MORE) ALARM DEVICES HAS BEEN
FACTORY CONNECTED TOTHE LOCAL ALARM
INPUT TERMINALS 24 & 50
135655P1
24 50 51 55 56 84 85 82 83 88 89 91 92 93
Unplug standard P43
harnesses from AM/AG
control board and
connect to harness
provided in Item 110 Kit
37C38C37B38B37 38 75 76 94 95 96 97 11 12
P43
P43
AM/AG
CONTROL
BOARD
P25
77 78
BLACK
RED
41 424344 45 46 47 48
110
TB3
Install 2 Harnesses
provided in Item 110 Kit
BLACK
110
UNPLUG STANDARD P25 HARNESS AND REMOVE
RED CONNECTOR. CUT AND STRIP WIRES
FOR INSTALLATION TO SCREW CONNECTOR
TB2 ON NIC BOARD AS SHOWN.
9.4.1
110
TB1
NIC
112
-+
RED
TB2
Item 111, manual,
to be inserted
in unit installation packet
Item 113, schematic, to be
attached to deadfront
System Wiring for Himod
Two wiring harnesses are included with the retrofit kit, one for the
power connection and the second for communication. They are of sufficient 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.
30
Retrofit Installation
9.4.2
Power Connection for Himod
The harness supplied with the OpenComms NIC-485
(p/n 159084G1) is equipped with three connectors, one at either end of
the harness and one in the middle. The harness taps power from the
24 VAC input to the control board of the environmental unit. To connect this power to the NIC-485:
1. Locate the connector containing the two red wires plugged into
P43 on the control board and unplug it. Reconnect it to the
connector in the middle of the supplied harness.
2. Plug one end of this harness into P43 on the control board and the
other end into TB3 of the OpenComms card.
9.4.3
Communication Connection for Himod
The second wiring harness provided (p/n 159083G1) has a connector
fitted at either end and is the communication connection between the
unit microprocessor and the NIC-485.
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. Ensure correct polarity.
2. Connect one end of the wire harness to TB1 of the interface card;
the other end connects to P25 of the environmental controller.
9.5
Mini-Mate2
An enclosure is recommended for use with ceiling-mounted environmental units or where internal mounting of the NIC-485 is not feasible. Older-generation Deluxe and Challenger units may also require
external mounting.
9.6
Emerson Network Power (CEMS100 / LECS15)
The kit includes a special cable to allow simple interconnection
between the controller and the OpenComms NIC-485.
Questions about the retrofit kits should be directed to the International Sales department.
Contact: yc.kok@emersonnetwork.com.au
9.7
UPS Installation
Retrofit kits are designed specifically for individual units. Consult
your local sales / service representative for pricing, part numbers and
installation help.
31
Retrofit Installation
9.8
Npower
As a minimum there will be an IFM board (communication 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. The OpenComms NIC-485 should be mounted in the bottommost (bottom cable
entry) position. Other options can be placed in any open option slot.
9.8.1
Power Connection for NPower
After mounting the NIC-485 in the uppermost or lowermost option
position, per the instructions above, route the wire harness from TB3
on the lower left of the NIC-485 to the power supply board on the back
of the control door. Follow the routing path indicated in Figure 13.
9.8.2
Communication Connection for NPower
Connect the 2-wire harness from TB1 on the bottom center of the
NIC-485 to TB-55 on the IFM card. The board is now ready to connect
customer inputs, which should be routed from either the top or bottom
cable entry points.
Figure 13 shows the single-line detail. Refer to the NPower option
manual for further installation details.
32
Retrofit Installation
Figure 13 NPower UPS NIC-485 installation
Power Supply Board
Option
Section
SiteScan IFM
Control Door
OpenComms
NIC-485
location
(see detail)
IGMnet
24VAC
Detail
33
Retrofit Installation
9.9
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. To maintain continuity of supply, the
load should first be transferred to the maintenance bypass
circuit following the procedure given in the UPS user manual.
Refer to the UPS user manual for more details.
If you encounter any problems with the procedures contained in this
manual contact your local Liebert representative or Liebert's Customer Service and Support Department at:
Liebert Hiross Service
Customer Service and Support Department
Fourth Avenue
Globe Park
Marlow
Buckinghamshire SL71YG
Telephone: +44 (0) 1628 403 200
Fax: +44 (0) 1628 403 296
34
Retrofit Installation
Figure 14 7200 UPS NIC-485 installation
Logic Operator
Board
Network
Interface Card
Ethernet
Connection
35
Retrofit Installation
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 NIC-485
(P/N 4590063X), in the HiPulse UPS, it is necessary to power
down that unit. To maintain continuity of supply, the load
should first be transferred to the maintenance bypass circuit
following the procedure given in the UPS user manual.
Refer to the UPS or Network Interface Card user manual for more
details.
If you encounter any problems with the procedures contained in this
manual contact your local Liebert representative or Liebert's Customer Service and Support Department at:
Liebert Hiross Service
Customer Service and Support Department
Fourth Avenue
Globe Park
Marlow
Buckinghamshire SL71YG
Telephone +44 (0) 1628 403 200
Fax +44 (0) 1628 403 296
36
Retrofit Installation
Figure 15 HiPulse NIC-485 installation
37
Retrofit Installation
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 16 STS2 typical NIC-485 connections
RS-232 (DB-9 connector)
for setup only. Uses standard
computer serial port cable
J3
P18
1 2 3
Ethernet Network
RJ-45 connector
See Notes 1 & 2
TB2
+ See Note 2
Customer-supplied
interconnecting cable
NETWORK INTERFACE
CARD (NIC) 416241GX
Customer-supplied
interconnecting cable
to Modbus
Figure 17 STS2 NIC-485 installation, 800-1000A units
See
Option
Location
Detail
REMOTE SOURCE
SELECT (OPTION)
PROGRAMMABLE RELAY
BOARD (OPTION)
PROGRAMMABLE RELAY
BOARD (OPTION)
INPUT CONTACT ISOLATOR
BOARD (OPTION)
CONTROL WIRING
Front View With Front Door Removed
Option
Location
Detail
38
NETWORK INTERFACE
CARD (NIC) (OPTION)
COMMS BOARD FOR SITESCAN,
EXTERNAL AND INTERNAL
MODEM INTERFACE (OPTION)
Retrofit Installation
Figure 18 STS2 NIC-485 installation, 100 - 600A units
See
Option
Location
Detail
REMOTE SOURCE
SELECT (OPTION)
PROGRAMMABLE RELAY
BOARD (OPTION)
PROGRAMMABLE RELAY
BOARD (OPTION)
INPUT CONTACT ISOLATOR
BOARD (OPTION)
CONTROL WIRING
Front View With Front Door Removed
9.12
Option
Location
Detail
NETWORK INTERFACE
CARD (NIC) (OPTION)
COMMS BOARD FOR SITESCAN,
EXTERNAL AND INTERNAL
MODEM INTERFACE (OPTION)
STS
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. Consult the corresponding section of this manual regarding installation details.
9.13
PDU and DataWave with PMP & EPMP
Retrofit Kits are designed specifically for individual units. Consult
your local sales / service representative for pricing, part numbers and
installation help.
All compatible PDU’s and DataWave’s require the use of an external
enclosure. Consult the corresponding section of this manual regarding
installation details.
39
Retrofit Installation
40
MONITORING
OpenComms NIC-485
USER MANUAL
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:
•
Environmental systems—close-control
air conditioning from 1 to 60 tons
•
Power conditioning and UPS with power
ranges from 300VA to more than
1000kVA
•
Integrated systems that provide both
environmental and power protection in a
single, flexible package
•
Monitoring and control—from systems
of any size or location, on-site or remote
•
Service and support through more than
100 service centers around the world
and a 24/7 Customer Response Center
While every precaution has been taken to
ensure the accuracy and completeness of
this literature, Liebert Corporation assumes
no responsibility and disclaims all liability for
damages resulting from use of this
information or for any errors or omissions.
© 2005 Liebert Corporation
All rights reserved throughout the world.
Specifications subject to change without
notice.
® Liebert and the Liebert logo are registered
trademarks of Liebert Corporation. All names
referred to are trademarks or registered
trademarks of their respective owners.
SL-28152 (01/05) Rev. 1
Technical Support/Service
Web Site
www.liebert.com
Monitoring
800-222-5877
monitoring@liebert.com
Outside the US: 614-841-6755
Single-Phase UPS
800-222-5877
upstech@liebert.com
Outside the US: 614-841-6755
Three-Phase UPS
800-543-2378
powertech@liebert.com
Environmental Systems
800-543-2778
Outside the United States
614-888-0246
Locations
United States
1050 Dearborn Drive
P.O. Box 29186
Columbus, OH 43229
Italy
Via Leonardo Da Vinci 8
Zona Industriale Tognana
35028 Piove Di Sacco (PD)
+39 049 9719 111
Fax: +39 049 5841 257
Asia
23F, Allied Kajima Bldg.
138 Gloucester Road
Wanchai
Hong Kong
+852 2 572 2201
Fax: +852 2 831 0114