ICC ETH-1000 User manual

January 15, 2012
ICC #10724 © 2012 Industrial Control Communications, Inc.
ICC
INDUSTRIAL CONTROL COMMUNICATIONS, INC.
ETH-1000
Multiprotocol Ethernet / RS-485
Gateway
Instruction Manual

1
ICC
ETH-1000
User's Manual
Part Number 10724
Printed in U.S.A.
©2012 Industrial Control Communications, Inc.
All rights reserved
NOTICE TO USERS
Industrial Control Communications, Inc. reserves the right to make changes and
improvements to its products without providing notice.
Industrial Control Communications, Inc. shall not be liable for technical or editorial
omissions or mistakes in this manual, nor shall it be liable for incidental or
consequential damages resulting from the use of information contained in this
manual.
INDUSTRIAL CONTROL COMMUNICATIONS, INC.’S PRODUCTS ARE NOT
AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE-SUPPORT
DEVICES OR SYSTEMS. Life-support devices or systems are devices or
systems intended to sustain life, and whose failure to perform, when properly
used in accordance with instructions for use provided in the labeling and user's
manual, can be reasonably expected to result in significant injury.
No complex software or hardware system is perfect. Bugs may always be present
in a system of any size. In order to prevent danger to life or property, it is the
responsibility of the system designer to incorporate redundant protective
mechanisms appropriate to the risk involved.
This user’s manual may not cover all of the variations of interface applications,
nor may it provide information on every possible contingency concerning
installation, programming, operation, or maintenance.
The contents of this user’s manual shall not become a part of or modify any prior
agreement, commitment, or relationship between the customer and Industrial
Control Communications, Inc. The sales contract contains the entire obligation of
Industrial Control Communications, Inc. The warranty contained in the contract
between the parties is the sole warranty of Industrial Control Communications,
Inc., and any statements contained herein do not create new warranties or modify
the existing warranty.
Any electrical or mechanical modifications to this equipment without prior written
consent of Industrial Control Communications, Inc. will void all warranties and
may void any UL/cUL listing or other safety certifications. Unauthorized
modifications may also result in equipment damage or personal injury.

2
ICC
APPLICABLE FIRMWARE
Main Processor:
Modbus – BACnet Firmware Version 2.300
Metasys – Toshiba Firmware Version 2.200
Sullair – Chillgard Firmware Version 2.400
FLN – Basys Firmware Version 2.400
DMX-512 – M-Bus Firmware Version 2.300
AIN – PDNP Firmware Version 2.300
Coprocessor:
Ethernet Multiple V2.320

3
ICC
Usage Precautions
•Please use the interface only when the ambient temperature of the
environment into which the unit is installed is within the following
specified temperature limits:
Operation: -10 ∼+50°C (+14 ∼+122°F)
Storage: -40 ∼+85°C (-40 ∼+185°F)
•Avoid installation locations that may be subjected to large shocks or
vibrations.
•Avoid installation locations that may be subjected to rapid changes in
temperature or humidity.
Operating Environment
•Proper ground connections are vital for both safety and signal reliability
reasons. Ensure that all electrical equipment is properly grounded.
•Route all communication cables separate from high-voltage or noise-
emitting cabling (such as ASD input/output power wiring).
Installation and Wiring

4
ICC
TABLE OF CONTENTS
1. Introduction ................................................................................ 10
2. Features ...................................................................................... 11
3. Gateway Concepts..................................................................... 13
4. Precautions and Specifications................................................ 15
4.1 Installation Precautions.........................................................................15
4.2 Maintenance Precautions......................................................................16
4.3 Inspection..............................................................................................16
4.4 Maintenance and Inspection Procedure................................................16
4.5 Storage .................................................................................................17
4.6 Warranty ...............................................................................................17
4.7 Disposal................................................................................................17
4.8 Environmental Specifications................................................................17
5. Gateway Overview ..................................................................... 18
5.1 Power Supply Electrical Interface..........................................................19
5.2 Power over Ethernet (PoE) ...................................................................19
5.3 RS-485 Port Electrical Interface............................................................20
6. Installation .................................................................................. 22
6.1 Mounting the Gateway..........................................................................22
6.1.1 Panel / Wall Mounting....................................................................22
6.1.2 DIN Rail Mounting..........................................................................23
6.2 Wiring Connections...............................................................................24
6.3 Grounding.............................................................................................24
7. LED Indicators............................................................................ 25
7.1 Module/Network Status.........................................................................25
7.2 RS-485 Network Status.........................................................................26
7.3 Ethernet Status.....................................................................................26
8. Configuration Concepts ............................................................ 27
8.1 USB Configuration Utility.......................................................................27
8.2 Finder Tab.............................................................................................28
8.3 Timeout Configuration Tab....................................................................30
8.3.1 Timeout Time.................................................................................30
8.3.2 Timeout Object Configuration ........................................................30
8.4 Port Configuration Tabs Protocol Selection Group................................31
8.5 Service Object Configuration ................................................................32

5
ICC
8.5.1 Description of Common Fields.......................................................32
8.5.2 Viewing the Status of a Service Object..........................................34
8.6 General Object Editing Options.............................................................34
8.7 Ethernet Protocol Configuration............................................................36
8.7.1 Ethernet Configuration Subtab.......................................................36
8.7.2 BACnet /IP Client...........................................................................37
8.7.3 BACnet/IP Server ..........................................................................40
8.7.4 BBMD ............................................................................................43
8.7.5 EtherNet/IP Client..........................................................................44
8.7.6 EtherNet/IP Server.........................................................................53
8.7.7 CSP Client .....................................................................................55
8.7.8 CSP Server....................................................................................56
8.7.9 Mitsubishi MELSEC/SLMP Client ..................................................57
8.7.10 Mitsubishi MELSEC/SLMP Server.................................................63
8.7.11 Modbus/TCP Client........................................................................64
8.7.12 Modbus/TCP Server ......................................................................68
8.7.13 PROFINET IO................................................................................71
8.8 RS-485 Protocol Configuration .............................................................72
8.8.1 A.O. Smith AIN Slave.....................................................................72
8.8.2 A.O. Smith PDNP Master...............................................................77
8.8.3 BACnet MS/TP Client ....................................................................81
8.8.4 BACnet MS/TP Server...................................................................88
8.8.5 TCS Basys Master.........................................................................96
8.8.6 DMX-512 Master..........................................................................102
8.8.7 DMX-512 Slave............................................................................104
8.8.8 M-Bus Master ..............................................................................107
8.8.9 Metasys N2 Master......................................................................113
8.8.10 Metasys N2 Slave........................................................................118
8.8.11 Modbus RTU Master....................................................................125
8.8.12 Modbus RTU Slave......................................................................130
8.8.13 Modbus RTU Sniffer ....................................................................136
8.8.14 Siemens FLN Slave .....................................................................140
8.8.15 Sullair Supervisor Master.............................................................141
8.8.16 Toshiba ASD Master....................................................................145
9. Interacting With the Filesystem.............................................. 150
9.1 Initiating FTP via the Finder Tab.........................................................151
9.2 Using FTP with Windows Explorer......................................................152
9.3 Using FTP with a Windows Command Prompt ...................................154
9.4 Using FTP with Core FTP LE..............................................................156
10. Embedded Web Server............................................................ 158
10.1 Overview.............................................................................................158

6
ICC
10.2 Authentication.....................................................................................159
10.3 Navigation Menu Tree.........................................................................160
10.4 Activity Window...................................................................................160
10.5 Monitor Menu......................................................................................160
10.5.1 Activity Indicator...........................................................................160
10.5.2 Database .....................................................................................161
10.6 MELSEC/SLMP Client Menu ..............................................................162
10.6.1 MELSEC Client Enable................................................................162
10.6.2 Connection Object Configuration .................................................162
10.6.3 Service Object Configuration .......................................................162
10.6.4 Submitting Changes.....................................................................163
10.7 EtherNet/IP Client Menu .....................................................................164
10.7.1 EtherNet/IP Client Enable............................................................164
10.7.2 Connection Object Configuration .................................................164
10.7.3 Service Object Configuration .......................................................164
10.7.4 Submitting Changes.....................................................................165
10.8 Modbus/TCP Client Menu...................................................................166
10.8.1 Modbus/TCP Client Enable..........................................................166
10.8.2 Connection Object Configuration .................................................166
10.8.3 Service Object Configuration .......................................................166
10.8.4 Submitting Changes.....................................................................167
10.9 BACnet/IP Client Menu.......................................................................168
10.9.1 BACnet/IP Client Enable..............................................................168
10.9.2 Device Object Configuration ........................................................168
10.9.3 Service Object Configuration .......................................................168
10.9.4 Submitting Changes.....................................................................169
10.10 BACnet/IP Server Menu......................................................................170
10.10.1 BACnet/IP Server Enable ............................................................170
10.10.2 Device Object Configuration ........................................................170
10.10.3 BACnet Object Configuration.......................................................170
10.10.4 Submitting Changes.....................................................................171
10.11 BBMD Menu........................................................................................172
10.11.1 BBMD Enable..............................................................................172
10.11.2 Broadcast Distribution Table (BDT) Configuration .......................172
10.11.3 Foreign Device Table (FDT) ........................................................173
10.11.4 Submitting Changes.....................................................................173
10.12 EtherNet/IP Server Menu....................................................................174
10.12.1 EtherNet/IP Enable......................................................................174
10.12.2 Run/Idle Flag Behavior ................................................................174
10.12.3 Device Identification.....................................................................174
10.12.4 Class 1 (I/O) Data Configuration..................................................175
10.12.5 Submitting Changes.....................................................................175

7
ICC
10.13 MELSEC/SLMP Server Menu.............................................................176
10.13.1 MELSEC Server Enable ..............................................................176
10.13.2 TCP Port......................................................................................176
10.13.3 Timeout Time Setting...................................................................176
10.13.4 Submitting Changes.....................................................................177
10.14 Modbus/TCP Server Menu..................................................................178
10.14.1 Modbus/TCP Server Enable ........................................................178
10.14.2 Timeout Time Setting...................................................................178
10.14.3 Register Remap Configuration.....................................................178
10.14.4 Submitting Changes.....................................................................179
10.15 PROFINET IO Menu...........................................................................180
10.15.1 PROFINET IO Enable..................................................................180
10.15.2 Device Identification.....................................................................180
10.15.3 Cyclic (I/O) Data Configuration ....................................................180
10.15.4 Submitting Changes.....................................................................181
10.16 Network Settings Menu.......................................................................182
10.16.1 Authentication..............................................................................182
10.16.2 Network Configuration .................................................................182
10.16.3 MAC Address...............................................................................183
10.16.4 Submitting Changes.....................................................................183
10.17 Alarm Menu.........................................................................................184
10.17.1 Email Configuration......................................................................185
10.17.2 Alarm Configuration.....................................................................186
10.17.3 Submitting Changes.....................................................................188
10.18 Dashboard Menu ................................................................................189
10.18.1 Gauge Window Navigation ..........................................................189
10.18.2 Gauge Window Configuration......................................................190
10.18.3 Submitting Changes.....................................................................193
10.19 Timeout Menu.....................................................................................194
10.19.1 Timeout Object Configuration ......................................................194
11. Protocol-Specific Information................................................. 195
11.1 A.O. Smith AIN Slave..........................................................................195
11.1.1 Overview......................................................................................195
11.1.2 AIN Service Objects.....................................................................195
11.2 A.O. Smith PDNP Master....................................................................196
11.2.1 Overview......................................................................................196
11.2.2 PDNP Service Objects.................................................................196
11.3 BACnet................................................................................................197
11.3.1 Protocol Implementation Conformance Statement.......................197
11.3.2 BACnet/IP and BACnet MS/TP Client..........................................201
11.3.3 BACnet/IP and BACnet MS/TP Server ........................................203

8
ICC
11.3.4 BBMD ..........................................................................................205
11.4 TCS Basys Master..............................................................................206
11.4.1 Overview......................................................................................206
11.4.2 Basys Service Objects.................................................................206
11.4.3 Read-Only Monitoring Variables..................................................206
11.4.4 Holiday Scheduling Parameters...................................................206
11.4.5 Parameter Scaling .......................................................................206
11.5 Chillgard Monitor.................................................................................208
11.5.1 Overview......................................................................................208
11.5.2 Data Mapping ..............................................................................209
11.6 DMX-512.............................................................................................214
11.6.1 DMX-512 Master..........................................................................214
11.6.2 DMX-512 Slave............................................................................215
11.7 EtherNet/IP .........................................................................................216
11.7.1 Overview......................................................................................216
11.7.2 EtherNet/IP Client........................................................................217
11.7.3 EtherNet/IP Server.......................................................................218
11.8 Allen Bradley CSP...............................................................................235
11.8.1 Overview......................................................................................235
11.8.2 Tag Reference.............................................................................235
11.8.3 SLC-5/05 Example: Read Database............................................236
11.8.4 SLC-5/05 Example: Multiple MSG Instructions............................241
11.8.5 SLC-5/05 Example: Reading and Writing.....................................241
11.9 M-Bus Master......................................................................................243
11.9.1 Overview......................................................................................243
11.9.2 M-Bus Service Objects ................................................................243
11.10 MELSEC/SLMP ..................................................................................244
11.10.1 Overview......................................................................................244
11.10.2 MELSEC Client............................................................................244
11.10.3 MELSEC Server ..........................................................................246
11.11 Metasys N2.........................................................................................248
11.11.1 Metasys N2 Master......................................................................248
11.11.2 Metasys N2 Slave........................................................................250
11.12 Modbus...............................................................................................252
11.12.1 Modbus/TCP................................................................................252
11.12.2 Modbus RTU................................................................................256
11.13 PROFINET IO.....................................................................................261
11.13.1 Customizing the GSDML..............................................................261
11.14 Sullair Supervisor Master....................................................................263
11.14.1 Sullair Service Objects.................................................................264
11.14.2 Parameter Mapping .....................................................................264
11.15 Toshiba ASD Master...........................................................................265

9
ICC
11.15.1 Overview......................................................................................265
11.15.2 Toshiba Service Objects..............................................................266
11.15.3 Parameter Mapping .....................................................................266
12. Troubleshooting....................................................................... 267
13. Appendix A: Database Endianness........................................ 269
13.1 Ex: Modbus - Profibus.........................................................................271
13.2 Ex: Modbus - DeviceNet .....................................................................272
13.3 Ex: BACnet - DeviceNet......................................................................273
13.4 Ex: BACnet - Modbus (Analog Objects-Registers)..............................275
13.5 Ex: BACnet - Modbus (Binary Objects-Discretes)...............................276
14. Appendix B: Status Information............................................. 278

10
ICC
1.
Introduction
Congratulations on your purchase of the ICC ETH-1000 Multiprotocol Ethernet
Communications Gateway. This gateway allows information to be transferred
seamlessly between various industrial Ethernet networks and one of several RS-
485-based networks. In addition to the supported fieldbus protocols, the gateway
hosts a USB interface for configuring the gateway via a PC.
Before using the gateway, please familiarize yourself with the product and be
sure to thoroughly read the instructions and precautions contained in this manual.
In addition, please make sure that this instruction manual is delivered to the end
user of the gateway, and keep this instruction manual in a safe place for future
reference or unit inspection.
For the latest information, support software and firmware releases, please visit
http://www.iccdesigns.com.
Before continuing, please take a moment to ensure that you have received all
materials shipped with your kit. These items are:
•ETH-1000 Gateway in plastic housing
•Documentation CD-ROM
•DIN rail adapter with two pre-mounted screws
•Four black rubber feet
Note that different gateway firmware versions may provide varying levels of
support for the various protocols. When using this manual, therefore, always
keep in mind that the firmware version indicated on your unit must be listed on
page 2 for all documented aspects to apply.
This manual will primarily be concerned with the gateway’s hardware
specifications, installation, wiring, configuration and operational characteristics.
To maximize the abilities of your new gateway, a working familiarity with this
manual will be required. This manual has been prepared for the gateway installer,
user, and maintenance personnel. With this in mind, use this manual to develop a
system familiarity before attempting to install or operate the gateway.

11
ICC
2.
Features
Supported Protocols
The gateway currently provides support for the following Ethernet protocols:
•BACnet/IP Client
•BACnet/IP Server
•BBMD (BACnet/IP broadcast management device)
•CSP (also known as PCCC or Allen Bradley Ethernet) Client
•CSP Server
•EtherNet/IP Client
•EtherNet/IP Server
•Mitsubishi MELSEC/SLMP Client
•Mitsubishi MELSEC/SLMP Server
•Modbus/TCP Client
•Modbus/TCP Server
•PROFINET IO
The gateway also currently provides support for the following RS-485 based
fieldbus protocols:
•A.O. Smith AIN Slave
•A.O. Smith PDNP Master
•BACnet MS/TP Client
•BACnet MS/TP Server
•TCS Basys Master
•MSA Chillgard Monitor
•DMX-512 Master
•DMX-512 Slave
•M-Bus (“Meter-Bus”) Master
•Johnson Controls Metasys N2 Master
•Johnson Controls Metasys N2 Slave
•Modbus RTU Master
•Modbus RTU Slave
•Modbus RTU Sniffer
•Siemens FLN Slave
•Sullair Supervisor Network Master
•Toshiba ASD Protocol Master
Supported Baud Rates
The gateway supports the following baud rates on the RS-485 port:
•300
•600
•1200
•2400
•4800
•9600
•19200
•38400
•57600
•76800
•115200

12
ICC
Note that not all protocols support every baud rate listed above. Refer to section
11 for more information.
Field-Upgradeable
As new firmware becomes available, the gateway can be upgraded in the field by
the end-user. Refer to section 8.1 for more information.
USB Interface
The gateway can be connected to a PC via a USB mini type-B cable. This
simultaneously supplies power while providing the ability to configure the
gateway, monitor data, and update firmware on the device using the ICC
Gateway Configuration Utility. Refer to section 8.1 for more information.
Power over Ethernet (PoE) Enabled
The gateway can be externally powered according to the PoE specification (IEEE
802.3af). Refer to section 5.2 for more information.
Alarm Evaluation with Email Notification
The gateway can autonomously monitor any database address and send emails
to up to four recipients when a certain condition is detected. Alarm conditions
have both value and time constraints, and can be configured to retrigger at a
fixed interval as long as the alarm condition continues to be satisfied. Twenty
individually-configurable alarms are available. Refer to section 10.17 for more
information.
Embedded Web Server
The gateway supports real-time web browser-based interaction via an Adobe®
Flash Player plug-in. This includes support for configuration, database
interaction, and a dashboard GUI with multiple windows, each of which can be
configured to display data in a variety of meter/graph/gauge formats. Refer to
section 10 for more information.
User-Configurable Network Timeouts
The gateway can be configured to perform a specific set of actions when network
communications are lost. This allows each address in the database to have its
own unique “fail-safe” condition in the event of network interruption (support for
this feature varies depending on the protocol). Refer to section 10.19 for more
information.
Flexible Mounting Capabilities
The gateway includes all hardware for desktop, panel/wall and DIN-rail mounting
capabilities. Refer to section 6.1 for more information.

13
ICC
3.
Gateway Concepts
The ETH-1000 is a member of the Millennium Series communication gateways.
Members of this family are designed to provide a uniform interface, configuration
and application experience. This commonality reduces the user’s learning curve,
reducing commissioning time while simplifying support. All Millennium Series
gateways are configured using the ICC Gateway Configuration Utility. The ETH-
1000 provides simultaneous support for many different communication protocols,
allowing complex interchanges of data between otherwise incompatible networks.
The heart of the Millennium Series concept is its internal database. The database
is a 4 KB, byte-wise addressable data array. The database allows data to be
routed from any supported network to any other supported network. Data may be
stored into the database in either big-endian style (meaning that if a 16-bit or 32-
bit value is stored in the database, the most significant byte will start at the lowest
address) or little-endian style (meaning that if a 16-bit or 32-bit value is stored in
the database, the least significant byte will start at the lowest address).
The other fundamental aspect of the Millennium Series is the concept of a
configurable “service object”. A service object is used for any master/client
protocol to describe what service (read or write) is to be requested on the
network. The gateway will cycle through the defined service objects in a round-
robin fashion; however, the gateway does implement a “write first” approach. This
means that the gateway will perform any outstanding write services before
resuming its round-robin, read request cycle.
Additionally, the database and service objects provide the added benefit of “data
mirroring”, whereby current copies of data values (populated by a service object)
are maintained locally within the gateway itself. This greatly reduces the request-
to-response latency times on the various networks, as requests (read or write)
can be entirely serviced locally, thereby eliminating the time required to execute a
secondary transaction on a different network.
Regardless of their network representation, all data values are stored in the
gateway’s internal database as integer values (either 8-, 16- or 32-bits in length,
depending on the protocol and/or object configuration). This means that even if a
network variable is accessed by the gateway as a 32-bit floating-point number,
this native representation will always be converted to an equivalent integer
representation prior to being stored in the database. Once in the database, this
value will then be accessible to the network operating on the other port of the
gateway, which may then impose its own conversion process on the data. A
port’s conversion may be implicit (e.g. all Modbus holding registers are
interpreted by the protocol as 16-bit unsigned integers) or explicit (as configured
in a BACnet service object).
In order to facilitate the free scaling and conversion of native data values, a user-
configurable “multiplier” and “data type” exist for some network configurations. All
network values are scaled by a multiplier prior to being stored into the database
or after being retrieved from the database. The data type is used to determine

14
ICC
how many bytes are allocated for the value in the database and whether or not to
interpret the number as signed or unsigned upon retrieval from the database.
A typical use of the multiplier feature is to preserve the fractional components of
a network value for insertion into the database. For example, if the floating-point
value “3.19” is read by the gateway from a remote BACnet device, then we could
use a multiplier value of 0.01 to preserve all of the significant digits of this value:
the network representation (3.19) will be divided by the multiplier value (0.01) to
obtain a resultant value of 319, which will then be inserted into the database.
Similarly, when a value in the database corresponding to a specific service object
is changed (which therefore requires that this updated value be written to the
associated remote device on the network), the service object’s multiplier value
will first be multiplied by the database value in order to obtain the resultant
network value. For example, if 3000 is written to the database at a location
corresponding to a certain service object on the other port, and that service
object’s multiplier value is 0.1, then the database value (3000) will be multiplied
by the multiplier value (0.1) to obtain the resultant network value of 300.0, which
will then be written to the network as a native floating point value.
An appropriate data type should be selected based on the range of the network
data values. For example, if the value of an Analog Output on a remote BACnet
device can vary from –500 to 500, a 16-bit signed data type should be used. If
the value can only vary from 0 to 150, for example, an 8-bit unsigned data type
may be used. Care must be taken so that a signed data type is selected if
network data values can be negative. For example, if 0xFF is written to the
database at a location corresponding to a service object with an 8-bit unsigned
data type, the resultant network value will be 25510 (assuming a multiplier of 1).
However, if 0xFF is written to the database at a location corresponding to a
service object with an 8-bit signed data type, the resultant network value will be
−110 (again, assuming a multiplier of 1). It is also important to select a data type
large enough to represent the network data values. For example, if a value of 257
is read by the gateway from a remote device and the data type corresponding to
that service object is 8-bit unsigned, the value that actually will be stored is 1
(assuming a multiplier of 1). This is because the maximum value that can be
stored in 8-bits is 255. Any value higher than this therefore results in overflow.
The Millennium Series gateways also provide a powerful data-monitoring feature
that allows the user to view and edit the database in real time, as well as view the
status of service objects via the ICC Gateway Configuration Utility’s Monitor tab
when connected via USB to a PC. The ability to interact with the database is also
available via the embedded web server.
When properly configured, the gateway will become essentially “transparent” on
the networks, and the various network devices can engage in seamless dialogs
with each other.

15
ICC
4.
Precautions and Specifications
Rotating shafts and electrical equipment can be hazardous.
Installation, operation, and maintenance of the gateway shall be
performed by Qualified Personnel only.
Qualified Personnel shall be:
•Familiar with the construction and function of the gateway, the
equipment being driven, and the hazards involved.
•Trained and authorized to safely clear faults, ground and tag
circuits, energize and de-energize circuits in accordance with
established safety practices.
•Trained in the proper care and use of protective equipment in
accordance with established safety practices.
Installation of the gateway should conform to all applicable National
Electrical Code (NEC) Requirements For Electrical Installations, all
regulations of the Occupational Safety and Health
Administration, and any other applicable national, regional, or
industry codes and standards.
DO NOT install, operate, perform maintenance, or dispose of this
equipment until you have read and understood all of the following
product warnings and user directions. Failure to do so may result in
equipment damage, operator injury, or death.
4.1
Installation Precautions
•Avoid installation in areas where vibration, heat, humidity, dust,
metal particles, or high levels of electrical noise (EMI) are
present.
•Do not install the gateway where it may be exposed to
flammable chemicals or gasses, water, solvents, or other fluids.
•Where applicable, always ground the gateway to prevent
electrical shock to personnel and to help reduce electrical noise.
Note: Conduit is not an acceptable ground.
•Follow all warnings and precautions and do not exceed
equipment ratings.

16
ICC
4.2
Maintenance Precautions
•Do Not attempt to disassemble, modify, or repair the gateway.
Contact your ICC sales representative for repair or service
information.
•If the gateway should emit smoke or an unusual odor or sound,
turn the power off immediately.
•The system should be inspected periodically for damaged or
improperly functioning parts, cleanliness, and to determine that
all connectors are tightened securely.
4.3
Inspection
Upon receipt, perform the following checks:
•Inspect the unit for shipping damage.
•Check for loose, broken, damaged or missing parts.
Report any discrepancies to your ICC sales representative.
4.4
Maintenance and Inspection Procedure
Preventive maintenance and inspection is required to maintain the gateway in its
optimal condition, and to ensure a long operational lifetime. Depending on usage
and operating conditions, perform a periodic inspection once every three to six
months.
Inspection Points
•Check that there are no defects in any attached wire terminal crimp points.
Visually check that the crimp points are not scarred by overheating.
•Visually check all wiring and cables for damage. Replace as necessary.
•Clean off any accumulated dust and dirt.
•If use of the interface is discontinued for extended periods of time, apply
power at least once every two years and confirm that the unit still functions
properly.
•Do not perform hi-pot tests on the interface, as they may damage the unit.
Please pay close attention to all periodic inspection points and maintain a good
operating environment.

17
ICC
4.5
Storage
•Store the device in a well-ventilated location (in its shipping carton, if
possible).
•Avoid storage locations with extreme temperatures, high humidity, dust, or
metal particles.
4.6
Warranty
This gateway is covered under warranty by ICC, Inc. for a period of 12 months
from the date of installation, but not to exceed 18 months from the date of
shipment from the factory. For further warranty or service information, please
contact Industrial Control Communications, Inc. or your local distributor.
4.7
Disposal
•Contact the local or state environmental agency in your area for details on
the proper disposal of electrical components and packaging.
•Do not dispose of the unit via incineration.
4.8
Environmental Specifications
Item Specification
Operating Environment
Indoors, less than 1000m above sea level, do not
expose to direct sunlight or corrosive / explosive
gasses
Operating Temperature -10 ∼+50°C (+14 ∼+122°F)
Storage Temperature -40 ∼+85°C (-40 ∼+185°F)
Relative Humidity 20% ∼90% (without condensation)
Vibration 5.9m/s2{0.6G} or less (10 ∼55Hz)
Grounding Non-isolated, referenced to power ground
Cooling Method Self-cooled
This device is lead-free / RoHS-compliant.

18
ICC
5.
Gateway Overview
Gateway Overview (Front)
RS-485 TX
and RX LEDs
Shielded RJ45
Ethernet jack
USB connector
Ethernet activity
LED (green)
Ethernet link LED
(amber)
Module Status (MS) and
Network Status (NS) LEDs
MAC ID (on bottom)
Chassis GND
RS-485 terminals
Power terminals
Gateway Overview (Back)

19
ICC
5.1
Power Supply Electrical Interface
When the gateway is not plugged into a PC via the USB cable, it must be
powered by an external power source or via Power over Ethernet (PoE: refer to
section 5.2). When using an external power source connected to the gateway’s
power and ground terminals, ensure that the power supply adheres to the
following specifications:
Voltage rating ......................... 7 - 24VDC
Minimum Current rating.......... 150mA (@24VDC)
•ICC offers an optional 120VAC/12VDC power supply (ICC part number
10755) that can be used to power the gateway from a standard wall outlet.
•The power supply must be connected to the gateway’s terminal block at
terminals TB:5 (POWER) and TB:6 (GND) as highlighted in Figure 1.
Figure 1: Terminal Block Power Supply Connections
5.2
Power over Ethernet (PoE)
The gateway supports the IEEE 802.3af Power over Ethernet (PoE) standard as
a mode A or mode B powered device (PD). In mode A, the Ethernet jack pins 1-
2 (pair #2 in T568B wiring) form one side of the DC supply and pins 3-6 (pair #3
in T568B) form the other side. These are the same two pairs used for data
transmission in 10Base-T and 100Base-TX, allowing the provision of both power
and data over only two pairs in such networks.
In mode B, the Ethernet jack pins 4-5 (pair #1 in both T568A and T568B cabling
standards) form one side of the DC supply and pins 7-8 (pair #4 in both T568A
and T568B) provide the return; these are the "spare" pairs in 10BASE-T and