HMS HMS-EN2MB-R User manual

+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
HMS Industrial Networks
Mailing address: Box 4126, 300 04 Halmstad, Sweden
Visiting address: Stationsgatan 37, Halmstad, Sweden
Connecting Devices
TM
E-mail: [email protected]
Web: www.anybus.com
User Manual
EtherNet/IP to Modbus-TCP
Linking Device
Doc.Id. SCM-1202-008
Rev. 1.1

Important User Information 2-1
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Important User Information
This document is intended to provide a good understanding of the functionality offered by the EtherNet/IP to Mod-
bus-TCP linking device. The reader of this document is expected to be familiar with high level software design,
and communication systems in general.
Liability
Every care has been taken in the preparation of this manual. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications
in the US and other countries.
Trademark Acknowledgements
Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their
respective holders.
Warning: This is a class A product. in a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
control procedures are not followed. Static control precautions are required when handling the prod-
uct. Failure to observe this may cause damage to the product.
Warning: DO NOT USE SD CARD OR USB CONNECTOR WHILE CIRCUIT IS LIVE UNLESS THE AREA IS
KNOWN TO BE FREE OF IGNITABLE CONCENTRATIONS OF FLAMMABLE GAS OR VAPORS.
EtherNet/IP to Modbus-TCP Linking Device User Manual
Rev 1.1
Copyright© HMS Industrial Networks AB
Nov 2016 Doc Id SCM-1202-008

Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Table of Contents
Preface About This Document ..................................................................... 6
Related Documents..................................................................................................................... 6
Document History ...................................................................................................................... 6
Conventions & Terminology..................................................................................................... 6
Chapter 1 EtherNet/IP to Modbus-TCP Linking Device............................... 7
Introduction ................................................................................................................................. 7
Unique Integration into Studio 5000 .................................................................................. 7
Configuring the EtherNet/IP Network .................................................................................. 7
Functional Overview .................................................................................................................. 8
Data Exchange............................................................................................................................. 9
I/O Mapped Data..................................................................................................................... 10
Parameter Data .......................................................................................................................... 10
Control/Status Word................................................................................................................ 10
Live List ...................................................................................................................................... 11
Transaction Status List ............................................................................................................. 12
Exception Code List ................................................................................................................. 13
Chapter 2 About the HMS-EN2MB-R Linking Device..................................14
External View ............................................................................................................................ 14
Mounting the Linking Device ................................................................................................. 15
DIN-rail Mounting.......................................................................................................... 15
Wall Mounting................................................................................................................. 16
Status LEDs ............................................................................................................................... 17
EtherNet/IP Connectors......................................................................................................... 18
USB Connector.......................................................................................................................... 18
Modbus-TCP Connectors........................................................................................................ 18
Power Connector ...................................................................................................................... 19
Chapter 3 Studio 5000 Implementation Example ...........................................20
Step by Step Guide.................................................................................................................... 20
Chapter 4 SD Card Functionality ....................................................................27
General Advice and Guidelines .............................................................................................. 27
Starting Up ................................................................................................................................. 28
Easy Backup ............................................................................................................................... 28
Simple Configuration Copy ..................................................................................................... 28
Easy Replacement ..................................................................................................................... 29
SD Card Synchronization Failure ........................................................................................... 30

Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Chapter 5 Modbus-TCP Functions................................................................. 31
Chapter 6 Tag Editor ...................................................................................... 32
Tag Editor Overview ................................................................................................................ 32
Menu Choices.................................................................................................................... 33
Tag Editor Basics....................................................................................................................... 34
Tag Arrays....................................................................................................................... 36
Tag Rule Definitions................................................................................................................. 37
Chapter 7 Modbus Configuration Manager.................................................... 38
General Information ................................................................................................................. 38
Overview..................................................................................................................................... 39
Home................................................................................................................................40
Configuration ............................................................................................................................. 41
Authentication .................................................................................................................. 41
Modbus Client .................................................................................................................. 42
Modbus Servers................................................................................................................. 43
EtherNet/IP (Adapter Interface)...................................................................................... 46
Tools........................................................................................................................................... 47
HMS-EN2MB-R Management ...................................................................................... 47
Backup and Restore .......................................................................................................... 47
Mapping Overview ............................................................................................................ 48
Transaction Monitor ......................................................................................................... 49
Chapter 8 CIP Objects .................................................................................... 50
General Information ................................................................................................................. 50
Identity Object (01h)................................................................................................................. 51
Message Router (02h) ............................................................................................................... 53
Assembly Object (04h) ............................................................................................................. 54
Connection Manager (06h) ...................................................................................................... 56
DLR Object (47h) ..................................................................................................................... 59
QoS Object (48h) ...................................................................................................................... 60
ADI Object (A2h) ..................................................................................................................... 61
Port Object (F4h) ...................................................................................................................... 63
TCP/IP Interface Object (F5h) .............................................................................................. 64
Ethernet Link Object (F6h) ..................................................................................................... 67

V
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Appendix A Technical Specification .................................................................. 69
Protective Earth (PE) Requirements...................................................................................... 69
Power Supply ............................................................................................................................. 69
Environmental Specification ................................................................................................... 69
Temperature...................................................................................................................... 69
Relative Humidity............................................................................................................. 69
EMC (CE) Compliance ............................................................................................................ 70
Appendix B Copyright Notices .......................................................................... 71

Doc.Id. SCM-1202-008
Linking Device
Doc.Rev. 1.1
Preface
P. About This Document
For more information, documentation etc., please visit the HMS website, www.anybus.com.
P.1 Related Documents
P.2 Document History
Summary of Recent Changes (1.0... 1.1)
Revision List
P.3 Conventions & Terminology
The following conventions are used throughout this manual:
• Numbered lists provide sequential steps
• Bulleted lists provide information, not procedural steps
• The term ‘linking device’ refers to the EtherNet/IP to Modbus-TCP linking device
• Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value
• A byte always consists of 8 bits
• The terms ‘master’, ‘scanner’, ‘client’ and ‘controller’ will be used interchangeably to describe a
controlling unit on the network
• The terms ‘slave’, ‘adapter’, ‘server’ and ‘device’ will be used interchangeably to describe units
that are controlled by controlling units on the network
Document Author
Modbus Application Protocol Specification V1.1B Modbus Organization
CIP Specification, Vol 1 (CIP Common) & 2 (EtherNet/IP) ODVA
Change Page(s)
Corrected Product Code in Identity Object (01h) to 57h 51
Revision Date Author(s) Chapter(s) Description
1.0 2016-10-27 KaD All First release
1.1 2016-11-15 KaD 8 Minor correction

Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Chapter 1
1. EtherNet/IP to Modbus-TCP Linking Device
1.1 Introduction
The EtherNet/IP to Modbus-TCP Linking Device is used to provide a seamless connection between a
Modbus-TCP network and an EtherNet/IP network. The linking device enables the master of the Eth-
erNet/IP network to control the Modbus-TCP network, and data can be transmitted transparently be-
tween the two networks.
1.1.1 Unique Integration into Studio 5000
The EtherNet/IP to Modbus-TCP linking device features a custom add-on profile (AOP) for easy in-
tegration with Studio 5000. Within this add-on profile (AOP), the HMS configuration tool can be
launched. When the configuration is ready, it can automatically be translated to structured Studio 5000
controller tags.
All network and device level configuration is done within Studio 5000.
IMPORTANT:
The add-on profile is supported by RSLogix 5000, v20 and later.
1.2 Configuring the EtherNet/IP Network
The Linking Device is an EtherNet/IP adapter (slave) on the EtherNet/IP network. The general set-
tings for the adapter interface are configured using the configuration pages. All data transfers must be
configured in Studio 5000. Please note that the size of the I/O data that can be read from and written
to the module is defined when configuring the linking device using the configuration pages.

EtherNet/IP to Modbus-TCP Linking Device 8
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.3 Functional Overview
Internally, the linking device consists of an intelligent gateway platform, a Modbus-TCP interface and
an EtherNet/IP (slave) interface. The Modbus-TCP interface and the EtherNet/IP (slave) interface are
interconnected through the intelligent gateway platform, which basically forwards data from one net-
work to the other and vice versa as shown below.
Industrial network
Modbus-TCP network
Anybus Modbus-TCP
Master Interface
Anybus network
slave interface

EtherNet/IP to Modbus-TCP Linking Device 9
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.4 Data Exchange
Each of the two network interfaces exchanges data on its network through two buffers. The linking de-
vice forwards the data between these buffers as shown below. Note that this process is separated from
the network data exchange. While the linking device ensures data consistency (where applicable), it does
not feature any built-in mechanisms for synchronization between the Modbus-TCP network and the
EtherNet/IP network.
Each buffer holds a maximum of 4096 bytes of data. The first two I/O mapped bytes in either direction
can be dedicated for control/status information, and another eight bytes of data coming from the Mod-
bus-TCP network can feature a live list. Please note that the actual number of bytes that can be ex-
changed is highly network dependent.
Through the dedicated control word, the scanner on the EtherNet/IP network starts/stops the ex-
change of data on the Modbus-TCP network, and also resets the linking device if needed. The scanner
on the EtherNet/IP network can see the status of the Modbus-TCP network in the corresponding status
word. The live list feature gives the scanner on the EtherNet/IP network the opportunity to continu-
ously see and monitor the status of each individual transaction on the Modbus-TCP network.
Two additional lists, transaction status and exception codes, retrievable from the module by the scanner
on the EtherNet/IP network, provides detailed error information about all transactions.
The amount of data that shall be exchanged, and the use of the control/status word and the live list, is
specified separately for each application. This means that even though up to 4096 bytes of data can be
potentially forwarded to an interface, the amount of data that will actually be exchanged on that network
is determined by the Modbus-TCP settings and the limitations of the master side fieldbus.
The available control/status functionality is described below, as well as the live list and the transaction
status and exception code lists. Also note that the terminology and definitions used for different types
of data vary greatly between different networking systems.
Industrial Network InterfaceModbus-TCP Network Interface
Industrial network
Modbus-TCP network
Data To
the Modbus-TCP
Network
Data From
the Modbus-TCP
Network
Data From
the Modbus-TCP
Network
Data to
the Modbus-TCP
Network
Status Word
Control Word

EtherNet/IP to Modbus-TCP Linking Device 10
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.5 I/O Mapped Data
I/O mapped data is cyclic data, exchanged between the networks and/or devices at a high transfer rate.
It is associated with implicit messaging, where data is continuously sent on the network.
1.6 Parameter Data
Parameter data is usually exchanged acyclically to set or change parameters in devices before or during
normal process. Acyclical data is set up as explicit messages using CIP message instructions in Studio
5000.
Typical explicit messages that can be retrieved from the module by the scanner of the EtherNet/IP net-
work includes the transaction status list and the exception code list.
1.7 Control/Status Word
The Control/Status word is always retrievable using acyclical access. Optionally, the Control/Status
word can also be I/O mapped. If so, it is disabled by default. It can be enabled/disabled when config-
uring the EtherNet/IP network via the configuration web pages. See “EtherNet/IP (Adapter Inter-
face)” on page 46.
The Control word is a 16-bit word (uint16) used by the EtherNet/IP network to control the linking de-
vice and subsequently also the Modbus-TCP network.
The Status word is a 16-bit word used by the linking device to report its current actual status to the Eth-
erNet/IP network.
Bit Value Description
0 (Least signifi-
cant bit) 0 Puts the linking device in idle state
1 Puts the linking device in run state
1 - A reboot of the linking device is triggered by a rising edge, i.e. a transition from 0
to 1
2-7 Set to zero Unused
8-15 Set to zero Unused
Bit Value Description
0 (Least signifi-
cant bit) 0 The linking device is in idle state
1 The linking device isin run state
1 - This bit is reflecting the state of bit 1 in the control word
Either 0 or 1
2-7 (reserved) Unused
8-15 (reserved) Unused

EtherNet/IP to Modbus-TCP Linking Device 11
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.8 Live List
The live list features the possibility for the EtherNet/IP network to retrieve a list containing the status
of every transaction on the Modbus-TCP network.
It is accessible using parameter access, and also I/O mapped by default. The I/O mapped live list can
be enabled/disabled when configuring the EtherNet/IP network settings. See “EtherNet/IP (Adapter
Interface)” on page 46. If the I/O mapped live list is enabled, it will occupy either byte 0-7 (control/
status word not enabled) or byte 2-9 (control/status word enabled and mapped to the first two bytes) in
the input data area.
All transactions and their places in the live list are also visible in the Transaction Monitor on the config-
uration web pages.
The live list consists of a bit array with 64 elements, where each bit corresponds to a transaction on the
Modbus-TCP network as in the table below.
• Bit set to 1
Transaction successful.
• Bit set to 0
Transaction not successful.
Note: the reason for the unsuccessful transaction can be found on the corresponding index in
the transaction status list.
The order of the transactions in the live list conforms to the order in which they are stored in the Mod-
bus Server list.
Example
Consider the following configuration:
• Server 1 : a total of 2 transactions
• Server 2 : a total of 3 transactions
• Server 3 : a total of 1 transaction
This scenario will produce a live list as follows (assuming that the transactions are successful):
Byte 7 Byte 6-1 Byte 0
Bit 63 Bit 62-56 Bit 55-8 Bit 7 Bit 6 - 2 Bit 1 Bit 0
Status of trans-
action no 63 Status of trans- action no 62-56 ... Status of trans- action no 7 Status of trans- action no 6 - 2 Status of trans- action no 1 Status of trans- action no 0
Bit 63 Bit 62 - 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
--Server3,
transaction 1 Server 2, transaction 3 Server 2, transaction 2 Server 2, transaction 1 Server 1, transaction 2 Server 1, transaction 1
00111111

EtherNet/IP to Modbus-TCP Linking Device 12
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.9 Transaction Status List
This list holds information about the transactions between the Modbus network and the linking device,
from the perspective of the linking device.
It is a list available from the module, which is possibl3e to be retrieved acyclically (using parameter ac-
cess) by the EtherNet/IP network. It contains a byte array with 64 elements, where each byte contains
a transaction status code as in the table below.
The indexes in the transaction status list correspond completely to the indexes in the transaction live list.
Transaction status codes
Byte 0 Byte 1 Byte 2-6 Byte 7 Byte 8 - 55 Byte 56-62 Byte 63
Status of trans-
action no 0 Status of trans- action no 1 Status of trans- action no 2-6 Status of trans- action no 7 ... Status of trans- action no 56-62 Status of trans- action no 63
TransactionStatus
Code Description
0 Running ok
1 Gateway idle
2 No link
3 Modbus exception
4 Timeout
5 Linking device disconnect
6 Server disconnect
7 Cannot connect
8 Modbus header error
9 Internal device error
10 No valid data
11 Stop sending data to Modbus server
12 Unconfigured transaction

EtherNet/IP to Modbus-TCP Linking Device 13
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
1.10 Exception Code List
If Modbus transactions fail, the slaves can respond with an exception code. These can be found in the
exception code list available from the module, possible to be retrieved acyclically (using parameter ac-
cess) by the EtherNet/IP network. It contains a byte array with 64 elements, where each byte contains
an transaction exception code as in the table below. The indexes in the exception code list correspond
completely to the indexes in the transaction live list.
Standard Modbus exception codes
Note: The exception codes found in the exception code list are only relevant if the corresponding trans-
action status codes equals 3: “Modbus exception”. See “Transaction Status List” on page 12 for more
information.
Note: If the slave responds with an exception code not in the list, refer to the documentation of the
slave for details.
Byte 0 Byte 1 Byte 2-6 Byte 7 Byte 8-55 Byte 56-62 Byte 63
Exception code
for transaction
no 0
Exception code
for transaction
no 1
Exception code
for transaction
no 2 - 6
Exception code
for transaction
no 7
Exception code
for transaction
no 8 - 55
Exception code
for transaction
no 56 - 62
Exception code
for transaction
no 63
Exception Code Description
00 No error
01 Illegal function
02 Illegal data address
03 Illegal data value
04 Slave device failure
05 Acknowledge
06 Slave device busy
08 Memory parity error
0A Gateway path unavailable
0B Gateway target device failed to respond

Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Chapter 2
2. About the HMS-EN2MB-R Linking Device
2.1 External View
•A: Power Connector
This connector is used to apply power to the linking
device. It is also possible to connect protective earth
(PE) to the power connector. See “Power Connec-
tor” on page 19.
• B: SD Card Slot
This slot adds the possibility to store and load con-
figurations from an SD card. See “SD Card Func-
tionality” on page 27.
•C:USBPort
This port adds the possibility to connect a PC to the
linking device to perform firmware upgrades. See
“USB Connector” on page 18.
•D: Status LEDs
See “Status LEDs” on page 17.
•E: DIN-rail Connector
The DIN-rail mechanism fastens the linking device
to a DIN-rail and connects the module to protective
earth (PE). See “Mounting the Linking Device” on
page 15.
• F: EtherNet/IP Connectors
See “EtherNet/IP Connectors” on page 18.
• G: Modbus-TCP Connectors
2-port switch with daisy-chain functionality. See
“Modbus-TCP Connectors” on page 18.
A
C
DE
B
F
G

About the HMS-EN2MB-R Linking Device 15
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
2.2 Mounting the Linking Device
The EtherNet/IP to Modbus-TCP Linking Device can be physically installed either by mounting it onto
a DIN-rail or, if installed in areas exposed to vibration, by mounting it on a wall for more stability.
2.2.1 DIN-rail Mounting
Make sure the DIN-rail fastening mechanism on the back of
the module is in a fixed and closed position, i. e. pushed all the
way up.
To mount the module, first hook it on to the DIN-rail (1),
then push it against the DIN-rail to make it snap on (2).
To unmount the module, a screwdriver is needed. Use the
screwdriver to push the DIN-rail fastening mechanism on the
back of the module down until it locks in a fixed and open po-
sition (1). Then unhook the module from the DIN-rail (2).
Note: Do not leave the module with the DIN-rail fastening
mechanism in a fixed and open position. This may eventually
wear the fastening mechanism out so it cannot be used effi-
ciently. Be sure to push the DIN-rail fastening mechanism
back into the fixed and closed position after demounting the
module.

About the HMS-EN2MB-R Linking Device 16
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
2.2.2 Wall Mounting
Use the wall mounting option if there is a need to place the linking device in an environment exposed
to vibration. This way of mounting the module offers more stability than the traditional DIN-rail mount-
ing.
Note: The device should be fastened in a standing-up position, to ensure a constant air flow.
Note: When mounting the device to a wall using the wall mount option, do not forget to connect the
module to protective earth (PE) via the power connector. See “Power Connector” on page 19.
Mounting Instructions
Step Description Visual description
Open up the package containing the wall
mounting accessories.
- One metal frame
- Industrial velcro
- Four plastic vibration dampers
Remove the plastic protection from one
side of the velcro.
Attach the velcro to the metal frame.
Attach the four plastic vibration dampers
to the linking device, on the side that will
face the wall.
Remove the plastic protection from the
other side of the velcro.
Turn the device around, so that the plastic
vibration dampers face downwards.
Fasten the metal frame to the device by
pressing the frame firmly against the
device, making the two velcro parts attach
to each other.
Attachthe metalframeandthe devicetoa
wall using screws and washers (not
enclosed).
1
2
3
4
5

About the HMS-EN2MB-R Linking Device 17
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
2.3 Status LEDs
Note: A test sequence is performed on all LEDs during startup.
Note: An identification LED sequence can be performed on LEDs 1, 5 and 6 by clicking the “Wink
device” button in the linking device management section in the web configuration interface.
Linking Device and Modbus-TCP Network LEDs
LED no State Status
1 - Module Status
EtherNet/IP Off Power off
Alternating red/green Boot sequence
Flashing green Idle
Green Running
Flashing red Major or minor recoverable error
Red Major or minor unrecoverable error
(Exception state or fatal)
2 - Network Status
EtherNet/IP Off Power off or no IP address
Green Online, one or more connection estab-
lished (CIP Class 1 or 3)
Flashing green Online, no connections established
Red Duplicate IP address, fatal error
Flashing red One or more connections timed out (CIP
Class 1 or 3)
3, 4 - EtherNet/IP
Ethernet Link 1 and 2 Off No link
Flashing green Receiving/transmitting Ethernet packets
at 100 Mbit
Flashing yellow Activity, receiving/transmitting Ethernet
packets at 10 Mbit
5 - SD card
(SD) Green Accessing SD card
Red Failure
6 - Modbus-TCP Status
(MTCP) Off Power off
Green Communicating with Modbus-TCP net-
work
Flashing green Idle
Flashing red Transaction error or timeout
Red Fatal error
7, 8 - Modbus-TCP
Ethernet Link 1 and 2 Off No link
Flashing green Receiving/transmitting Ethernet packets
at 100 Mbit
Flashing yellow Activity, receiving/transmitting Ethernet
packets at 10 Mbit

About the HMS-EN2MB-R Linking Device 18
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
2.4 EtherNet/IP Connectors
Connectors for the EtherNet/IP network are found at the lower front of the module.
2.5 USB Connector
At the upper front of the module there is a USB connector used for firmware upgrades.
2.6 Modbus-TCP Connectors
The Modbus-TCP connectors are found at the bottom of the module.
Pin no Description
1TX+
2TX-
3RX+
6RX-
4, 5, 7, 8 Not connected
Housing Shield
Pin no. Description
1 +5V Input
2 USBDM (USB communication signals)
3 USBDP (USB communication signals)
4 Signal GND
Housing Cable Shield
Pin no. Description
1TX+
2TX-
3RX+
4 Not connected
5 Not connected
6RX-
7 Not connected
8 Not connected
Housing Shield
18
1
2
34
18

About the HMS-EN2MB-R Linking Device 19
Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
2.7 Power Connector
Notes:
• Use 60/75 or 75×C copper (CU) wire only.
• The terminal tightening torque must be between 5... 7 lbs-in (0.5... 0.8 Nm)
See also...
- “Power Supply” on page 69.
Pin no. Description
1 +24V DC
2GND
3 PE (Protective Earth)
123

Doc.Id. SCM-1202-008
EtherNet/IP to Modbus-TCP Linking Device
Doc.Rev. 1.1
Chapter 3
3. Studio 5000 Implementation Example
This section will guide you through all steps necessary to create a basic configuration for the
HMS-EN2MB-R Linking Device.
3.1 Step by Step Guide
1. Start the Studio 5000 software. Expand the “I/O Configuration” folder in the tree view.
Right-click “Ethernet” and select “New Module”.
2. Select the HMS-EN2MB-R Linking Device (catalogue number: HMS-EN2MB-R) and click
“Create”.