Question: 64, use an NX-EIP201 EtherNet/IP Unit in addition to the NX-SL5£££ Safety Control Unit.

Answer:
Additional Information
CIP (Common Industrial Protocol)
CIP is a shared industrial protocol for the OSI application layer. The CIP is used in networks
such as EtherNet/IP, CompoNet, and DeviceNet.
Data can be routed easily between networks that are based on the CIP. You can therefore easi-
ly configure a transparent network from the field device level to the host level.
The CIP has the following advantages.
• Destination nodes are specified by a relative path, without fixed routing tables.
• The CIP uses the producer/consumer model. Nodes in the network are arranged on the same
level and it is possible to communicate with required devices whenever it is necessary.
The consumer node will receive data sent from a producer node when the connection ID in
the packet indicates that the node requires the data. Because the producer can send the
same data with the same characteristics in a multicast format, the time required for the trans-
fer is fixed and not dependent on the number of consumer nodes. (Either multicast or unicast
can be selected.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-5
1-1
Introduction
1
1-1-2
Features
of
Built-in
EtherNet/IP
Port
on
NJ/NX-series
CPU
Units
1 Introduction
1-2 System Configuration and Configura-
tion Devices
1-2-1 Devices Required to Construct a Network
The basic configuration for an EtherNet/IP system includes one Ethernet switch to which nodes are
attached in star configuration using twisted-pair cable.
Sysmac Studio (3) Ethernet switch
(Support Software)
(2) Twisted-pair cable
(1) Built-in EtherNet/IP (1) Built-in EtherNet/IP (1) Built-in EtherNet/IP
port on NJ/NX- port on NJ/NX- port on NJ/NX-
Ethernet (LAN) port 100 m series CPU Unit series CPU Unit series CPU Unit
max.
The following products are also required to build a network. Obtain them in advance.
Network device Function
Per Node These Units are used to connect to an EtherNet/IP
• NJ-series CPU Unit (built-in EtherNet/IP port) network.
(NJ501-££££/NJ301-££££/NJ101-££££)
• NX-series CPU Unit (built-in EtherNet/IP port)
(NX701-££££/NX502-££££/NX102-£££££
£/NX1P2-££££££)
• Other OMRON PLCs
CJ2 CPU Units (built-in EtherNet/IP port)
(CJ2H-CPU££-EIP/CJ2M-CPU3£)
CJ-series EtherNet/IP Unit
(CJ1W-EIP21/CJ1W-EIP21S)
CS-series EtherNet/IP Unit
(CS1W-EIP21/CS1W-EIP21S)
(2)Twisted-pair cable The twisted-pair cable has an RJ45 Modular Connec-
tor at each end.
This cable is used to connect the built-in EtherNet/IP
port or EtherNet/IP Unit to an Ethernet switch.
Use an STP (shielded twisted-pair) cable of category
5, 5e, or higher.
(3)Ethernet switch This is a relay device that connects multiple nodes in a
star LAN.
For details on recommended devices to configure a
network, refer to 2-1-1 Recommended Network Devi-
ces on page 2-2.
1-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
1-2-2 Support Software Required to Construct a Network
This section describes the Support Software that is required to construct an EtherNet/IP network.
The built-in EtherNet/IP port has Ethernet Settings and Tag Data Link Settings, which are both stored
in the non-volatile memory of the CPU Unit.
Support Software is provided for each, as described below.
 Built-in EtherNet/IP Port Settings: Sysmac Studio
Use the Sysmac Studio to set the basic settings, such as the local IP address and subnet mask of
the built-in EtherNet/IP port.
The Sysmac Studio can also be used to check if data I/O is being performed correctly for tag data
links.
Windows Computer
Sysmac Studio
Edit Parameters
Built-in EtherNet/IP port Dialog Box
settings (non-volatile memory)
Built-in EtherNet/IP port
NJ/NX-series CPU Unit
Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on the Sysmac
Studio.
 Tag Data Link Settings: Network Configurator
Use the Network Configurator to set the tag data links for the built-in EtherNet/IP port. (The Net-
work Configurator is included in the Sysmac Studio Standard Edition.) The main functions of the
Network Configurator are given below.
• Setting and Monitoring Tag Data Links (Connections)
The network device configuration and tag data links (connections) can be created and edited. Af-
ter connecting to the network, the device configuration and tag data link settings can be upload-
ed and monitored.
• Multi-vendor Device Connections
EDS files can be installed and deleted so that you can construct, set, and manage networks that
contain EtherNet/IP devices from other companies. The IP addresses of EtherNet/IP devices can
also be changed.
Windows computer with
Network Configurator
Tag Data Link Settings Edit Device
(non-volatile memory) Parameters
Dialog Box
Transferred.
Built-in EtherNet/IP port
NJ/NX-series CPU Unit
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-7
Configuration
Devices
1-2
System
Configuration
and
1
1-2-2
Support
Software
Required
to
Construct
a
Network
1 Introduction
For details on the Network Configurator, refer to Section 6 Tag Data Link Functions on page
6-1.
Additional Information
You can also use the Sysmac Studio to set the tag data links.
Refer to A-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP Connections) on
page A-5 for details on setting the tag data links on the Sysmac Studio.
1-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
1-3 Built-in EtherNet/IP Port
1-3-1 Specifications
Specifications
NX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££
££ ££ ££ ££££ NJ301-££££ ££
Item
Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-
sion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10
or later or later or later or later to 1.02 or later or later
Communications protocol TCP/IP or UDP/IP
Sysmac Studio connection, tag data link, CIP message communications, socket services, FTP serv-
Supported services er, FTP client, automatic clock adjustment (NTP client), SNMP agent, DNS client, BOOTP client,
DHCP client*1, Packet Filterr*2, and Packet Filter (Simple)*3
Number of ports 2 (IP routing function supported) 1
100Base-TX, 10Base-T, or 100Base-TX or 10Base-T (100Base-TX is recommended.) *4
1000Base-T (1000Base-T
Physical layer
or 100Base-TX is recom-
mended.) *4
Media access CSMA/CD
method
Modulation Baseband
Transmission Star form
paths
Baud rate 1,000 Mbps (1000Base-T) 100 Mbps (100Base-TX)
Transmission
Transmission Shielded twisted-pair (STP) cable, Category 5, 5e, or higher
specifications
media
Transmission 100 m max. (distance between hub and node)
distance
Number of cas- There is no limitation when an Ethernet switch is used.
cade connec-
tions
256 per port 64 per port 32 per port 32
Number of con- (total of 512 (total of 128 (total of 64
nections with two with two with two
CIP service: ports) ports) ports)
Tag data links 0.5 to 1 to 10,000 ms in 1-ms in- 2 to 10,000 10 to 1 to 10,000 ms in 1-ms in-
(cyclic com- 10,000 ms crements ms in 1-ms 10,000 ms crements
munications) Packet interval in 0.5-ms increments in 1-ms in-
(refresh cycle) increments crements
Packet intervals can be set independently for each connection. (Data is refreshed over the network
at preset intervals and the refresh cycle does not depend on the number of nodes.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-9
1-3
Built-in
EtherNet/IP
Port
1
1-3-1
Specifications
1 Introduction
Specifications
NX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££
££ ££ ££ ££££ NJ301-££££ ££
Item
Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-
sion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10
or later or later or later or later to 1.02 or later or later
40,000 20,000 12,000 3,000 pps*5 1,000 pps*5 3,000 pps*5
pps*5*6 pps*5*6 pps*5*6
Allowed com- Note: The Note: The Note: The Note: The heartbeat is included.
munications heartbeat is heartbeat heartbeat
bandwidth per included. and the CIP and the CIP
Unit Safety rout- Safety rout-
ing are in- ing are in-
cluded.*7 cluded.*8
Number of reg- 256 per port (total of 512 with two ports) 256
istrable tags
Network Network variable Network Network variable
variable CIO, Work, Holding, DM, variable CIO, Work, Holding, DM, or EM Areas
CIO, Work, or EM Areas can be used. CIO, Work, can be used.
Holding, Holding, or
CIP service: Tag types
DM, or EM DM Areas
Tag data links
Areas can- can be
(cyclic com-
not be used.
munications)
used.
8 (7 tags 64 (63 tags 8 (7 tags when the tag set includes the Controller status)
when the when the
Number of tags
tag set in- tag set in-
per connection
cludes the cludes the
(= 1 tag set)
Controller Controller
status) status)
369,664 92,416 19,200 19,200 bytes
bytes per bytes per bytes per
Maximum link
port (total of port (total of port (total of
data size per
739,328 184,832 38,400
node
bytes with bytes with bytes with
two ports) two ports) two ports)
1,444 bytes*9 600 bytes*9
Maximum data
Data concurrency is maintained within each connection.
size per connec-
Refer to 6-1-7 Concurrency of Tag Data Link Data on page 6-14 for methods to maintain concur-
tion
rency.
256 per port 64 per port 32 per port 32 (1 connection = 1 tag set)
(1 connec- (1 connec- (1 connec-
tion = 1 tag tion = 1 tag tion = 1 tag
Number of reg-
set) set) set)
istrable tag sets
(total of 512 (total of 128 (total of 40
with two with two with two
ports) ports) ports)*10
722 words 300 words
(The Controller status (The Controller status uses 1 word when the tag set includes the Con-
Maximum size
uses 1 word when the tag troller status.)
of 1 tag set
set includes the Controller
status.)
Changing tag Supported*11
data link param-
eters when Con-
troller is in RUN
mode
1-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
Specifications
NX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££
££ ££ ££ ££££ NJ301-££££ ££
Item
Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-
sion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10
or later or later or later or later to 1.02 or later or later
Multi-cast pack- Supported
et filter*12
Connections: 128 per port Connec- Connections: 32 (clients plus servers)
(total of 256 with two tions: 32
ports) (clients plus server) per port (to-
Class 3 (number tal of 64
of connections) with two
ports) (cli-
ents plus
CIP message server)
service: UCMM (uncon- Number of clients that can communicate at one time: 32 max.
Explicit nected) Number of servers that can communicate at one time: 32 max.
messages*13 Supported
CIP routing is supported for the following remote Units:
NX701-££££, NX502-££££, NX102-££££, and NX1P2-££££
NJ501-££££, NJ301-££££, NJ101-££££,
CIP routing*14
CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, CJ1W-EIP21S,
CJ2H-CPU££-EIP, and CJ2M-CPU3£.
Using a combination of any Units above, communication can be extended up to a maximum of 8
levels.
Maximum num- --- 128 total 16 total ---
ber of routable
CIP Safety con-
CIP Safety nections
routing*7*8*15 Maximum routa- --- 32 bytes ---
ble safety data
length per con-
nection
Agents SNMPv1 or SNMPv2c
SNMP
MIB MIB-II
Conforms to CT18 Conforms Conforms Conforms to CT18
EtherNet/IP conformance test to CT20 to CT13
*16
10Base-T, Fixed to au- 10Base-T or 100Base-TX
100Base- to negotia- Auto negotiation or fixed settings
TX, or tion
1000Base-
Ethernet interface T
Auto nego-
tiation or
fixed set-
tings
*1. The DHCP client is available only with NX502 CPU Units.
*2. The Packet Filter can be used in CPU Units with the following unit versions.
• NX502 CPU Unit: Version 1.60 or later
• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later
• NX701 CPU Unit: Version 1.29 or later
*3. The Packet Filter (Simple) is available only with NX102 CPU Units.
*4. If tag data links are being used, use 100Base-TX or 1000Base-T.
*5. Here, pps means “packets per second” and indicates the number of packets that can be processed in one second.
*6. If the two built-in EtherNet/IP ports are used simultaneously, the maximum communications data size means the maximum data size of
the total of the two ports.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-11
1-3
Built-in
EtherNet/IP
Port
1
1-3-1
Specifications
1 Introduction
*7. An NX502 CPU Unit with unit version 1.64 or later is required to use the CIP Safety routing.
*8. An NX102 CPU Unit with unit version 1.31 or later is required to use the CIP Safety routing.
*9. To use a data size of 505 bytes or larger, the system must support a large forward open (an optional CIP specification). The CS, CJ,
NJ, and NX-series Units support a large forward open, but before connecting to nodes of other companies, confirm that the devices
also support it.
*10. When tag sets that exceed total of 40 are set, a Number of Tag Sets for Tag Data Links Exceeded (840E0000 hex) event occurs.
*11. If the parameters of the built-in EtherNet/IP port are changed, the port is restarted. When other nodes are in communications with the
affected node, the communications will temporarily time out and automatically recover after the restart.
*12. Because the built-in EtherNet/IP port is equipped with an IGMP client (version 2), unnecessary multicast packets can be filtered out by
an Ethernet switch that supports IGMP snooping.
*13. The built-in EtherNet/IP port uses the TCP/UDP port numbers shown in A-12 TCP/ UDP Port Numbers Used for the Built-in
EtherNet/IP Port on page A-95.
Do not set the same port number for more than one TCP/UDP service.
*14. A CPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher are required to use CIP routing.
*15. When CIP Safety routing is used with the NX502 CPU Unit, it cannot be used if the task period of the primary periodic task is less than
500 µs.
*16. A CPU Unit with the unit version earlier than 1.64 conforms to CT14.
1-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
1-3-2 Part Names and Functions
Parts and Names
 NX701 CPU Unit
RUN
ERROR
BUSY
SHTDWN
SD PWR
SD BUSY
PORT1
EtherNet/IP
NET RUN
Indicators NET ERR
LINK/ACT
PORT1 EtherNet/IP
PORT2 PORT3
EtherNet/IP EtherCAT
NET RUN NET RUN
Built-in EtherNet/IP
NET ERR NET ERR
port 1 LINK/ACT LINK/ACT
PORT2 EtherNet/IP PORT3 EtherCAT
Built-in EtherNet/IP Built-in
port 2 EtherCAT
port
MAC Address Notation
A MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC
address of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in
the place of the Unit as shown below.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-13
1-3
Built-in
EtherNet/IP
Port
1
1-3-2
Part
Names
and
Functions
1 Introduction
LOT No. DDMYY£ xxxx Ver.1.££
PORT1 : ££££££££££££ HW Rev.£
PORT2 : ££££££££££££
MAC addresses
 NX502 CPU Unit
POWER
Built-in EtherNet/IP
port 1
Indicators
PORT2 Built-in EtherNet/IP
port 2
Built-in EtherCAT
port
MAC Address Notation
A MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC
address of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in
the place of the Unit as shown below.
1-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
NX502-1£00 Ver.£.££ HW Rev.£
PORT1 MAC ADDRESS:££££££££££££
PORT2 MAC ADDRESS:££££££££££££
PORT3 MAC ADDRESS:££££££££££££
LOT No. DDMYY£ xxxx
MAC addresses
 NX102 CPU Unit
PORT1 EtherNet/IP
Built-in EtherNet/IP
port 1
Indicators
PORT2 EtherNet/IP
Built-in EtherNet/IP
port 2
PORT3 EtherCAT
Built-in EtherCAT
port
MAC Address Notation
A MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC
address of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in
the place of the Unit as shown below.
Ver.£.££ HW Rev.£ LOT No. DDMYY£ xxxx
PORT1 ££££££££££££
PORT2 ££££££££££££
MAC addresses
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-15
1-3
Built-in
EtherNet/IP
Port
1
1-3-2
Part
Names
and
Functions
1 Introduction
 NX1P2 CPU Unit
IN
SW SETTING
PORT1 EtherNet/IP P RO UNWER
ERROR
Built-in EtherNet/IP port B SU DS PY WR
SD BUSY
PORT1 EtherNet/IP
NET RUN
PORT2 EtherCAT NET ERR
LINK/ACT
PORT2 EtherCAT
NETRUN
NET ERR
LINK/ACT
OUT
Indicators
MAC Address Notation
A MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC
address of the built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in
the place of the Unit as shown below.
PORT1 : ££££££££££££
PORT2 : ££££££££££££
Ver.1.££ HW Rev. £
LOT No. DDMYY£ xxxx
MAC address of built-in EtherNet/IP port
1-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
 NJ-series CPU Unit
USB port
Built-in EtherNet/IP port
Built-in EtherCAT port
Indicators
MAC Address Notation
A MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC
address of the built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in
the two places of the Unit as shown below.
Upper 6 digits of MAC address
PORT 1
XXXXXX
XXXXXX Lower 6 digits of MAC address
MAC address (12 digits)
NJ501-XXXX Ver. XXX
PORT1 : XXXXXXXXXXXX
PORT2 : XXXXXXXXXXXX
XXXXXXX XXXX
Indicators (LEDs)
NX701 CPU Unit NX102 CPU Unit NX1P2 CPU Unit
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-17
1-3
Built-in
EtherNet/IP
Port
1
1-3-2
Part
Names
and
Functions
1 Introduction
PORT1
SD BUSY
EtherNet/IP
NET RUN PORT1 EtherNet/IP
NET RUN
NET ERR NET ERR
LINK/ACT LINK/ACT
PORT2 EtherCAT
PORT2 PORT3
EtherNet/IP EtherCAT
NET RUN NET RUN
NET ERR NET ERR
LINK/ACT LINK/ACT
NJ-series CPU Unit NX502 CPU Unit
 NET RUN, NET ERR, and LINK/ACT
• NET RUN indicator
This shows the status of the CIP connection (tag data links, Class 3 messages).
• NET ERR indicator
This shows the network communications error status. Refer to Section 15 Troubleshooting on
page 15-1 for details.
• LINK/ACT indicator
This shows the Ethernet communications status.
Col
Indicator Status Operating status
or
Ethernet communications are not possible.
• The power supply is OFF or the Controller is reset.
--- Not lit
• A MAC address error or Communications Controller error is occurring.
• The same IP address is assigned to more than one node.
Ethernet communications are in progress.
Flash-
NET RUN • Tag data link connection establishment in progress (originator operation)
ing
Gr • IP address acquisition with BOOTP in progress.
ee Normal
n If only the target is set for the tag data link, this indicator is lit regardless of
Lit
whether the connection from the originator is established. It remains lit even
if the data links are stopped.
There are no Ethernet communications errors.
--- Not lit
• The power supply is OFF or the Controller is reset.
A user-recoverable error is occurring.
• An error is occurring in TCP/IP communications or CIP communications.
Flash-
NET ERR • FTP Server Setting Error, NTP Server Setting Error, etc.
Re ing
• Tag Data Link Setting Error, Tag Data Link Verification Error, etc.
d
• The same IP address is assigned to more than one node.
A user-non-recoverable error is occurring.
Lit
• A MAC address error or Communications Controller error is occurring.
1-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
Col
Indicator Status Operating status
or
The link is not established.
--- Not lit • The cable is not connected.
• The power supply is OFF or the Controller is reset.
LINK/ACT
Flash- Data communications in progress after establishing the link.
Yel
ing
low
Lit Link established.
Additional Information
When the built-in EtherNet/IP port is set to be disabled, all the indicators are turned OFF.
Refer to 4-1 TCP/IP Settings Display on page 4-2 for details on the settings of a built-in
EtherNet/IP port.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-19
1-3
Built-in
EtherNet/IP
Port
1
1-3-2
Part
Names
and
Functions
1 Introduction
1-4 Introduction to Communications
Services
1-4-1 CIP (Common Industrial Protocol) Communications Services
Tag Data Links (Cyclic Communications)
A program is not required to perform cyclic data exchanges with other devices on the EtherNet/IP net-
work.
Normally, a connection is started with the target device for each tag set that was created with the Net-
work Configurator to start communications for tag data links for a built-in EtherNet/IP port. One con-
nection is used per tag set.
The maximum number of connections that can be registered is shown below.
• NX701 CPU Unit: 256 connections (total of 512 connections with two ports)
• NX502 CPU Unit: 64 connections (total of 128 connections with two ports)
• NX102 CPU Unit: 32 connections (total of 64 connections with two ports)
• NX1P2 CPU Unit: 32 connections
• NJ-series CPU Unit: 32 connections
Additional Information
The NX502 CPU Unit can be used with the NX-EIP201 (EherNet/IP Unit) for tag data link com-
munications.
However, check the effect on task execution time because it increases I/O refreshing time.
Refer to 1-3-1 Specifications on page 1-9 for the built-in EtherNet/IP port tag and tag set specifica-
tions.
1-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
Connection Information
• Target IP address
• Target tag set
• Originator tag set
• Packet interval (RPI) Connection
Tag Set (Input) Tag Set (Output)
Tag set name: SP1_IN Tag set name: SP1_OUT
Controller status Controller Status
Tag a Tag i
Tag b Tag ii
Data flow
Tag c
Tag g
Originator device Target device
EtherNet/IP
NoteIn this example, a connection is established with the originator’s tag list with tags a to g (inputs), which are
in a tag set called SP1_IN, and the target’s tag list with tags i and ii (outputs), which are in a tag set called
SP1_OUT.
CIP Message Communications
User-specified CIP commands can be sent to devices on the EtherNet/IP network.
CIP commands, such as those for reading and writing data, can be sent and their responses received
by executing the CIP communications instructions from the user program in the NJ/NX-series CPU
Unit.
NJ/NX-series Controller Built-in EtherNet/IP port
CIP message
CIP_SEND
Ethernet
CIP command
(EtherNet/IP)
CIP response
By specifying a route path, you can send CIP messages (CIP commands and responses) to a device
on another CIP-based network segment via a built-in EtherNet/IP port or the EtherNet/IP Unit (CIP
routing function for message communications).
The maximum number of levels of CIP routing via the ports is eight for any combination of CS, CJ, NJ,
and NX-series CPU Units. Note that the number of levels of IP routing using an L3 Ethernet switch is
not counted in the number of levels of CIP routing via the ports.
• NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-21
tions
Services
1-4
Introduction
to
Communica-
1
1-4-1
CIP
(Common
Industrial
Protocol)
Communications
Services
1 Introduction
Because there are two built-in EtherNet/IP ports, CIP routing is possible by the CPU Unit alone.
Ethernet
(EtherNet/IP)
NX701 CPU Unit, NX502 CPU Unit and NX102 CPU Unit
Built-in EtherNet/IP
port 1
Ethernet
Built-in EtherNet/IP
(EtherNet/IP)
port 2
• NJ-series CPU Unit
By combining the built-in EtherNet/IP port and an EtherNet/IP Unit, CIP routing can be performed.
Ethernet
(EtherNet/IP)
NJ-series CPU Unit EtherNet/IP Unit
Ethernet
(EtherNet/IP)
Built-in EtherNet/IP port
Additional Information
In CIP routing, a node (Unit) that routes information subtracts the equivalent of one hop from
the timeout, deletes its own address from the route information, and relays the information to
the next node (Unit).
When a timeout is specified, the timeout for the actual request service processing is set in the
last hop.
In the case of relay hops, the timeout for the relay route must be added to the timeout for the
request.
OMRON products that support CIP subtract 5 seconds per hop.
Version Information
For an NJ-series CPU Unit, you can use the EtherNet/IP Unit with a CPU Unit with unit version


Question: 01 or later and Sysmac Studio version 1.02 or higher.

Answer:
1-4-2 IP Routing
The EtherNet/IP on the NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units have the IP rout-
ing function. The IP routing function sends IP packets to other network segments based on the routing
information set in the IP router table.
To communicate with devices on other network segments, you must set the IP router table and default
gateway settings for the CPU Unit and each device on the network appropriately for your network con-
figuration.
1-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
Precautions for Correct Use
• You cannot create tag data links between multiple CPU Units using IP routing on the NX701
CPU Units, NX502 CPU Units, and NX102 CPU Units.
• The IP routing function can only be used with the NX701 CPU Units, NX502 CPU Units, and
NX102 CPU Units. IP routing cannot be used with a combination of a built-in EtherNet/IP port
on an NJ-series CPU Unit and an EtherNet/IP Unit.
Computer
HMI
Sysmac Studio
IP address: 10.1.1.1/24 IP address: 10.1.1.2/24
EtherNet/IP Network address: 10.1.1.0/24
NX701, NX502, or
NX102 CPU Unit IP router
table
EtherNet/IP Network address: 10.1.2.0/24
NX701, NX502, or
NX102 CPU Unit IP router
table
EtherNet/IP Network address: 10.1.3.0/24
NJ-series
CPU Unit
IP address: 10.1.3.1/24
 Port Forward - IP Forward
This function divides the network for the built-in EtherNet/IP ports 1 and 2. When you divide the
network, set IP Forward to Do not use. When it is set to Do not use, any other IP packets than
those addressed to the Controller are discarded. Refer to 4-1 TCP/IP Settings Display on page
4-2 for details. You can use this function only for the NX502 CPU Units and NX102 CPU Units.
Additional Information
CIP routing is not be affected by the IP Forward setting.
1-4-3 Packet Filter
This function filters IP packets in the receive processing at the built-in EtherNet/IP ports. While Packet
Filter (Simple) is used to restrict Sysmac Studio connections, Packet Filter performs general-purpose
packet filtering that does not restrict communication partner to Sysmac Studio. Specify packets al-
lowed to be received by IP address or TCP/UDP port number.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-23
tions
Services
1-4
Introduction
to
Communica-
1
1-4-3
Packet
Filter
1 Introduction
Version Information
Packet Filter is available in the following CPU Units of stated versions.
• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later
• NX701 CPU Unit: Version 1.29 or later
• NX502 CPU Unit: Version 1.60 or later
1-4-4 Packet Filter (Simple)
This function filters IP packets in the receive processing at the built-in EtherNet/IP ports. When Packet
Filter (Simple) is enabled, it will allow you to connect the Sysmac Studio only from a computer with the
preregistered IP address, and restrict any other connection from those with unregistered IP addresses.
This function can be used only for NX102 CPU Unit.
Precautions for Correct Use
• Connections to NA-series and NS-series Programmable Terminals are restricted if this func-
tion is enabled. To make connections to these devices, register their IP addresses in the
Packet Filter (Simple) settings. Refer to Packet Filter (Simple) on page 4-10 for details on
the setting.
• If this function is enabled, you cannot connect the Sysmac Studio from a computer whose IP
address is not registered. Before enabling this function, confirm in advance that the IP ad-
dress of the computer is correctly registered.
• If this function is enabled, you cannot connect the Sysmac Studio to the Controller with the
Direct connection via Ethernet Option selected for the connection type. Select Controller -
Communications Setup to confirm that Ethernet connection via a hub is selected for con-
nection type.
• You can disable this function tentatively by starting the Unit in Safe Mode in case you forget
the registered IP address and cannot go online from the Sysmac Studio. Refer to
Troubleshooting When You Cannot Go Online from the Sysmac Studio in the NJ/NX-series
Troubleshooting Manual (Cat. No. W503) for details.
• You can use the Packet Filter (Simple) with Sysmac Studio version 1.49 or lower. Use the
Packet Filter instead of the Packet Filter (Simple) when you use Sysmac Studio version 1.50
or higher.
1-4-5 BOOTP Client
You set the built-in EtherNet/IP port in the BOOTP settings to use the BOOTP client to obtain settings,
such as the built-in EtherNet/IP port IP address, from the BOOTP server.
BOOTP server
BOOTP command Ethernet
Built-in Built-in
IP address EtherNet/IP port EtherNet/IP port
BOOTP client
The built-in EtherNet/IP port IP address is obtained
from the BOOTP server when the power is turned ON.
1-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
1-4-6 DHCP Client
You set the built-in EtherNet/IP port in DHCP setting to use the DHCP client to obtain settings, such as
the built-in EtherNet/IP port IP address, from the DHCP server.
This function can be used only for the NX502 CPU Unit.
DHCP server
DHCP command Ethernet
NJ/NX-series NJ/NX-series
IP address
Controller Controller
DHCP client
1-4-7 FTP Server
An FTP server is built into the built-in EtherNet/IP port so that files can be read from and written to the
SD Memory Card in the CPU Unit of the Controller from computers at other Ethernet nodes.
This makes it possible to exchange data files between a host computer and the Controller with the
host computer as the FTP client and the Controller as the FTP server.
Host computer
(FTP client)
Ethernet
FTP command Built-in EtherNet/IP port
NJ-series Controller
SD Memory
Card
Host computer to Controller Controller to Host computer
File data File data
SD Memory SD Memory
Card Card
1-4-8 FTP Client
The built-in EtherNet/IP port contains an FTP client. With it, you can use FTP client communications
instructions to transfer files between the CPU Unit and host computers on Ethernet.
This makes it possible to exchange data files between a host computer and the Controller with the
Controller as the FTP client and the host computer as the FTP server.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-25
tions
Services
1-4
Introduction
to
Communica-
1
1-4-6
DHCP
Client
1 Introduction
Host computer
(FTP server)
Ethernet
File data Built-in EtherNet/IP Port
NJ/NX-series
Controller
SD Memory
Card
Downloading Data Uploading Data
File data File data
SD Memory SD Memory
Card Card
1-4-9 Automatic Clock Adjustment
With the built-in EtherNet/IP port, clock information is read from the NTP server at the specified time or
at a specified interval after the power supply to the CPU Unit is turned ON. The internal clock time in
the CPU Unit is updated with the read time.
NTP server
NTP command
Ethernet
Clock information
Built-in EtherNet/IP port
NJ/NX-series
Controller
Precautions for Correct Use
An NTP server is required to use automatic clock adjustment.
1-4-10 Socket Service
You can send data to and receive data from any node on Ethernet with the UDP or TCP protocol.
To send/receive data with a socket service, you execute multiple socket communications instructions
in sequence in an ST program to execute the required communications processes.
After a connection with the other communications device is opened with an open instruction, the val-
ues of the variables that are specified for the send instruction are sent and the data that was received
for a receive instruction is stored in the specified variables.
The connection is closed with a close instruction, and communications end.
For TCP, you can also read the socket status and received data.
1-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
You can use a total of 30 TCP ports and UDP ports. (A total of 60 ports for NX502 and NX102 CPU
Units)
Ethernet
Communications processes are
performed with socket commu-
nications instructions (for UDP).
Open processing
Send processing
Receive processing
Close processing
tekcoS
UNIX computer or
other node with socket
service interfaces
Built-in EtherNet/IP port
TCP/UDP
protocol
NJ/NX-series CPU Unit
ST Programming
TCP/UDP
protocol
Built-in EtherNet/IP port
PI
PCT
PDU
1 Introduction
SktUDPCreate(...)
SktUDPSend(...)
SktUDPRcv(...)
SktClose(...)
NJ/NX-series CPU Unit
1-4-11 Secure Socket Services
The secure socket services allow the built-in EtherNet/IP port on the CPU Unit to act as a client, ena-
bling secure socket communications with the on-premises server on the private network or with the
cloud server on the external network.
This function performs encrypted communications using TLS, which use client private keys and certifi-
cates, and enables safe communications.
Cloud
server
Internet
IP router
Firewall
On-premises
server
Ethernet (EtherNet/IP)
Controller
Built-in EtherNet/IP port
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-27
tions
Services
1-4
Introduction
to
Communica-
1
1-4-11
Secure
Socket
Services
1 Introduction
1-4-12 Specifying Host Names
You can directly specify IP addresses, but you can also use the host names instead of the IP address-
es for NTP servers, SNMP managers, or the destinations of socket instructions and CIP
communications instructions (DNS client or hosts settings).
Example: Setting Host Names on the DNS Server
DNS server
IP address Ethernet
Host name
Built-in EtherNet/IP port
NJ/NX-series
Controller
Precautions for Correct Use
• A DNS server is required to use the server host names for the DNS client.
1-4-13 SNMP Agent
The SNMP agent has the following functions.
SNMP Agent
The SNMP agent passes internal status information from the built-in EtherNet/IP port to network man-
agement software that uses an SNMP manager.
Monitors devices on Ethernet/IP
SNMP
manager
Built-in EtherNet/IP port
Ethernet
SNMP message
Management
information Device that supports SNMP
SNMP agent SNMP agent SNMP agent
1-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
SNMP Trap
When specific conditions occur, the built-in EtherNet/IP port that is set as the SNMP agent sends sta-
tus notification reports to the SNMP manager.
The SNMP manager can learn about changes in status even without periodically monitoring the built-
in EtherNet/IP port.
Status notification reports are sent under the following conditions.
• When the Controller is turned ON
• When links are established
• When an SNMP agent fails to be authorized
SNMP manager
Controller power
Trap is turned ON.
Built-in EtherNet/IP port
SNMP agent
1-4-14 TCP/UDP Message Service
This function supports TCP/UDP socket communications, which allow simple access to CIP objects of
the Controller from a system where EtherNet/IP is not supported. This will allow you to change settings
and perform I/O control for NX Units connected to the Controller or the NX bus.
You can use the TCP/UDP message service only for the NX502 CPU Units and NX102 CPU Units.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-29
tions
Services
1-4
Introduction
to
Communica-
1
1-4-14
TCP/UDP
Message
Service
1 Introduction
1-5 EtherNet/IP Communications Proce-
dures
 Basic Operation
1 Wire the Ethernet network with twisted-pair cable. Section 2 Installing Ethernet Net-
works on page 2-1
↓
2 Set the built-in EtherNet/IP port IP address with the Sysmac 5-1 Determining IP Addresses on
Studio. page 5-2


Question: Set the local IP address in one of the following ways:

Answer:
• Defaults:
NX701 CPU Unit
Built-in EtherNet/IP port 1 : 192.168.250.1
(subnet mask = 255.255.255.0)
Built-in EtherNet/IP port 2 : 192.168.251.1
(subnet mask = 255.255.255.0)
NX502 CPU Unit
Built-in EtherNet/IP port 1 : 192.168.250.1
(subnet mask = 255.255.255.0)
Built-in EtherNet/IP port 2 : 192.168.251.1
(subnet mask = 255.255.255.0)
NX102 CPU Unit
Built-in EtherNet/IP port 1 : 192.168.250.1
(subnet mask = 255.255.255.0)
Built-in EtherNet/IP port 2 : 192.168.251.1
(subnet mask = 255.255.255.0)
NX1P2 CPU Unit Built-in EtherNet/IP port : 192.168.250.1
NJ-series CPU Unit Built-in EtherNet/IP port (subnet mask = 255.255.255.0)
• Set any IP address.
• Obtain from the BOOTP server.
• Obtain from the DHCP server (this can be set only for the NX502 CPU Units).
↓
3 Perform a communications test with a PING command from a 5-3 Testing Communications on
computer. page 5-18
↓
4 Use the Sysmac Studio to set the initial settings of the Ether- Section 4 Sysmac Studio Set-
Net/IP Function Module. tings for the Built-in EtherNet/IP
Port on page 4-1
• Set the TCP/IP settings and Ethernet settings as required.
 Using Tag Data Links
1 Import the variable settings for the tags that were created on 6-2-4 Creating Tags and Tag Sets
the Sysmac Studio to the Network Configurator. on page 6-25
↓
2 Use the Network Configurator to create the tag data link table. Section 6 Tag Data Link Func-
tions on page 6-1
1-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
1 Introduction
• Create the network configuration.
• Set the tags, tag sets, and connections.
↓
3 Connect the Network Configurator online.
↓
4 Download the tag data link setting.
↓
5 Start the tag data links (the links starts automatically when
power is turned ON).
↓
6 Check operation. 1-3-2 Part Names and Functions
on page 1-13
Section 15 Troubleshooting on
page 15-1
• Check the built-in EtherNet/IP port indicators.
• Use the Sysmac Studio to check the communications status
with the All Tag Data Link Communications Status system-de-
fined variable.
• Use the monitor function of the Network Configurator to con-
firm that the tag data links are in normal operation.
 Using the Message Communications Service
• CIP Communications Instructions
1 Execute CIP communications instructions in the user program. Section 7 CIP Message Commu-
nications on page 7-1
↓
2 Check operation. 1-3-2 Part Names and Functions
on page 1-13
Section 15 Troubleshooting on
page 15-1
• Use the Sysmac Studio to check the communications status
with the end codes of the instructions (Done, Err, and ErrID).
 Using the Socket Services
1 Execute the socket service instructions in the user program. Section 8 Socket Service on
page 8-1
↓
2 Check operation.
• Use the Sysmac Studio to check the communications status
with the end codes of the instructions (Done, Err, and Error-
ID).
 Using the FTP Server
1 Use the Sysmac Studio to set the initial settings of the Ether- Section 10 FTP Server on page
Net/IP Function Module. 10-1
• Set the FTP settings (enabling FTP, login name, and pass-
word).
↓
2 Connect to the FTP server in the NJ-series CPU Unit from an
FTP client application.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-31
Procedures
1-5
EtherNet/IP
Communications
1
1 Introduction
• Input the FTP login name and password to log onto the built-
in EtherNet/IP port.
• Check the event log to see if the FTP server started.
 Using the Automatic Clock Adjustment
1 Use the Sysmac Studio to set the initial settings of the Ether- Section 12 Automatic Clock Ad-
Net/IP Function Module. justment on page 12-1
• Set the NTP settings (enabling NTP and execution condi-
tions).
↓
2 Execute automatic clock adjustment.
• Execute automatic adjustment at specified times or specified
intervals.
• Use the Sysmac Studio to check the NTP Last Operation
Time and NTP Operation Result system-defined variables.
• Check the event log to see if the NTP client started.
 Using the SNMP Agent
1 Use the Sysmac Studio to set the initial settings of the Ether- Section 13 SNMP Agent on page
Net/IP Function Module. 13-1
• Set the SNMP settings.
• Set the SNMP trap settings.
↓
2 Check operation.
• Check the event log to see if the SNMP agent started.
 Using BOOTP
1 Use the Sysmac Studio to set the initial settings of the Ether- Section 4 Sysmac Studio Set-
Net/IP Function Module. tings for the Built-in EtherNet/IP
Port on page 4-1
• Set the BOOTP settings.
↓
2 Check operation.
• Check the event log to see if BOOTP started.
• Check the Online system-defined variable.
1-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
2
Installing Ethernet Networks
2-1 Selecting the Network Devices.....................................................................2-2
2-1-1 Recommended Network Devices....................................................................2-2
2-1-2 Ethernet Switch Types.....................................................................................2-3
2-1-3 Ethernet Switch Functions...............................................................................2-3
2-1-4 Precautions for Ethernet Switch Selection......................................................2-4
2-2 Network Installation.......................................................................................2-7
2-2-1 Basic Installation Precautions.........................................................................2-7
2-2-2 Recommended Network Devices....................................................................2-7
2-2-3 Precautions When Laying Twisted-pair Cable.................................................2-7
2-2-4 Precautions When Installing and Connecting Ethernet Switches...................2-11
2-3 Connecting to the Network..........................................................................2-13
2-3-1 Ethernet Connectors.....................................................................................2-13
2-3-2 Connecting the Cable....................................................................................2-14
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-1
2
2 Installing Ethernet Networks
2-1 Selecting the Network Devices
2-1-1 Recommended Network Devices
The following table shows the devices recommended for use with the EtherNet/IP.
 Ethernet Switches
Manufacturer Model Description
OMRON W4S1-05D Packet priority control (QoS): EtherNet/IP control data priority
Ethernet standard: IEEE 802.3 10Base-T, 100Base-TX
Auto-negotiation: Supported
Broadcast storm detection function: Supported
Number of ports: 5
Cisco Systems, Consult the manufacturer.
Inc. http://www.cisco.com/
Contec USA, Consult the manufacturer.
Inc. http://www.contec.com/
Phoenix Con- Consult the manufacturer.
tact USA https://www.phoenixcontact.com
 Twisted-pair Cables and Connectors
Applicable EtherNet/IP communications cables and connectors vary depending on the used baud
rate.
For 100Base-TX and 10Base-T, use an STP (shielded twisted-pair) cable of category 5 or higher.
You can use either straight or cross cable.
For 1000Base-T, use an STP (shielded twisted-pair) cable (double shielding with aluminum tape
and braiding) of category 5e or higher. You can use either straight or cross cable.
Cabling materials used for EtherNet/IP communication cables are shown in the table below.
"100Base-TX" in the "Product" column of the table below indicates that either 100Base-TX or
10Base-T can be used.
Product Manufacturer Model
For 1000Base-T Size and con- Cable Hitachi Metals, Ltd. NETSTAR-C5E
and 100Base- ductor pairs: SAB 0.5 × 4P CP
TX AWG24 × 4 Kuramo Electric Co. KETH-SB
pairs
JMACS Japan Co., Ltd. IETP-SB
*1
RJ45 Connec- Panduit Corporation MPS588
tors
For 100Base- Size and con- Cable Kuramo Electric Co., Ltd. KETH-PSB-OMR
TX ductor pairs: JMACS Japan Co., Ltd. PNET/B
AWG22 × 2
RJ45 Assembly OMRON XS6G-T421-1
pairs*1 Connectors
*1. We recommend that you use cables and connectors in above combinations.
2-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
2 Installing Ethernet Networks
2-1-2 Ethernet Switch Types
 Unmanaged Layer 2 (L2) Ethernet Switches
These Ethernet switches use the Ethernet MAC address to switch ports. Ordinary Ethernet
switches have this function. Ethernet switch functions and settings cannot be changed.
 Managed Layer 2 (L2) Ethernet Switches
These Ethernet switches use the Ethernet MAC address to switch ports. Ethernet switch functions
and settings can be changed with special software tools for Ethernet switches running on a network
node. You can also collect analytical data. These Ethernet switches provide more-advanced func-
tions than unmanaged layer 2 Ethernet switches.
2-1-3 Ethernet Switch Functions
This section describes the Ethernet switch functions that are important for an EtherNet/IP network. For
a built-in EtherNet/IP port, consider whether the Ethernet switch supports these functions when you
select the Ethernet switch.
• Multicast filtering
• QoS (Quality of Service) for TCP/UDP port numbers (L4)
 Multicast Filtering
Multicast filtering transfers multicast packets to the specific nodes only. This function is implement-
ed in the Ethernet switch as IGMP snooping or GMRP.
“Specific nodes” are nodes equipped with an IGMP client, and have made transfer requests to the
Ethernet switch. (OMRON built-in EtherNet/IP ports are equipped with an IGMP client.) When the
Ethernet switch does not use multicast filtering, multicast packets are sent to all nodes, just like
broadcast packets, which increases the traffic in the network.
Settings must be made in the Ethernet switch to enable this function. There must be enough multi-
cast filters for the network.
 QoS (Quality of Service) Function for TCP/UDP Port Numbers (L4)
This function controls the priority of packet transmissions so that packets can be sent with higher
priority to a specific IP address or TCP (UDP) port. The TCP and UDP protocols are called trans-
port layer protocols, leading to the name L4 (layer 4) QoS function.
When tag data links and message communications are executed on the same network, tag data
links can be sent at higher priority to prevent problems such as transmission delays due to mes-
sage communications traffic and packet losses due to buffer overflow.
Settings must be made in the Ethernet switch to enable QoS function and give higher priority to tag
data link packets.
These functions are supported by Ethernet switches as described in the table below.
Ethernet switch type Multicast filtering L4 QoS Remarks
Unmanaged L2 Ethernet switch Not supported Not sup- ---
ported
Managed L2 Ethernet switch Supported Supported Both functions must be set
with a special software tool.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-3
2-1
Selecting
the
Network
Devices
2
2-1-2
Ethernet
Switch
Types
2 Installing Ethernet Networks
Ethernet switch type Multicast filtering L4 QoS Remarks
OMRON Ethernet switch Not supported Supported L4 QoS is set with a switch.
(W4S1-series Ethernet switches) No software tool is necessa-
ry. QoS (Quality of Service)
Function for TCP/UDP Port
Numbers (L4) on page 2-3
Additional Information
If you select Multicast Connection for the connection type in the connection settings on the
Network Configurator, multicast packets are used. If the connection type is set to a Point to
Point Connection, multicast packets are not used.
2-1-4 Precautions for Ethernet Switch Selection
The functions supported by the Ethernet switch may affect tag data link transmission delays and the
settings in the Controller configurations and setup.
In addition, if the Ethernet switch supports advanced functions, special settings are required for the
functions.
When you select an Ethernet switch, it is necessary to consider what kind of data transmission and
how much traffic you use over the the network.
Refer to the following precautions when you select an Ethernet switch.
Refer to 14-2 Adjusting the Communications Load on page 14-7 to estimate the communications
load for tag data links.
Selecting the Ethernet Switch Based on the Type of Network Com-
munications
 Executing Tag Data Links Only
We recommend that you use an L2 Ethernet switch without multicast filtering or an L2 Ethernet
switch with multicast filtering.
An L2 Ethernet switch with multicast filtering prevents increased traffic due to unnecessary multi-
cast packets, so the tag data links can operate at higher speed.
If either of the following conditions exists, there is no difference in the traffic condition whether mul-
ticast filtering is supported or not.
• The tag data links are set to share the same data with all nodes in the network. (Multicast pack-
ets are transferred to all nodes in the network, just like broadcast transmission.)
• The tag data link settings are all one-to-one (unicast) and multicast packets are not used.
When multicast filtering is used, settings must be made accordingly on the Ethernet switch. There
must be enough multicast filters for the network.
 Executing Tag Data Links and Message Communications
We recommend an L2 Ethernet switch with multicast filtering and L4 QoS.
If you set tag data links for higher-priority transmission, it is possible to prevent problems such as
transmission delays due to message communications traffic and packet losses due to buffer over-
flow.
When multicast filtering and L4 QoS are used, settings must be made accordingly on the Ethernet
switch.
2-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
2 Installing Ethernet Networks
Selecting the Ethernet Switch Based on the Ethernet Switch's Sup-
ported Functions
 L2 Ethernet Switch without Multicast Filtering
We recommend this kind of Ethernet switch when only tag data links are executed and any of the
following conditions is met.
• The tag data links are set to share the same data with all nodes in the network. (Multicast pack-
ets are transferred to all nodes in the network, just like broadcast transmission.)
• The tag data link settings are all one-to-one (unicast) and multicast packets are not used.
• There is little traffic in the tag data links.
No special settings are required for an L2 Ethernet switch without multicast filtering.
 L2 Ethernet Switch with Multicast Filtering
We recommend this kind of Ethernet switch when only tag data links are executed and the follow-
ing condition is met.
• There are many 1:N links (where N represents some number of nodes in the network) in the tag
data link settings, i.e., there are many multicast packets used, or there is heavy traffic in the tag
data links.
Specific settings are required for an L2 Ethernet switch with multicast filtering. There must be
enough multicast filters for the network.
 L3 Ethernet Switch with Multicast Filtering and L4 QoS Functions
We recommend this kind of Ethernet switch when both tag data links and message communica-
tions are executed.
If you set tag data links for higher-priority transmission, you can prevent problems such as trans-
mission delays due to message communications traffic and packet losses due to buffer overflow.
When multicast filtering and L4 QoS are used, settings must be made accordingly on the Ethernet
switch. There must be enough multicast filters for the network.
Selecting the Ethernet Switch Based on the Network Communica-
tion Speed
 Executing Tag Data Links at a Baud Rate Over 100 Mbps
If you use data tag links with the following conditions, use an Ethernet switch with multicast filtering
or an Ethernet switch that supports a baud rate of 1,000 Mbps.
• Multicast
• Baud rate over 100 Mbps
If there is an Ethernet device on the same network that communicates at a speed of 100 Mbps or
less, the device may affect tag data link communications and cause tag data links to be broken,
even if the device is not related to tag data link communications.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-5
2-1
Selecting
the
Network
Devices
2
2-1-4
Precautions
for
Ethernet
Switch
Selection
2 Installing Ethernet Networks
Precautions for Correct Use
• Ask the Ethernet switch manufacturer for setting procedures for the Ethernet switch.
• Install the Ethernet switch based on its environmental resistance specifications so that the
environmental resistance specifications are fully met. Ask the Ethernet switch manufacturer
for information on the environmental resistance of the Ethernet switch.
2-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
2 Installing Ethernet Networks
2-2 Network Installation
2-2-1 Basic Installation Precautions
• Take the greatest care when you install the Ethernet System. Be sure to follow ISO 8802-3 specifi-
cations. Be sure you understand them before attempting to install an Ethernet System.
• Unless you are already experienced in installation of communications systems, we strongly recom-
mend that you employ a professional to install your system.
• Do not install Ethernet equipment near sources of noise.
If a noisy environment is unavoidable, take adequate measures against noise interference, such as
installation of network components in metal cases or the use of optical cable in the system.
• When using a shielded cable with the shields on both ends of the cable connected to connector
hoods, ground loops induced by improper grounding methods may decrease noise immunity and
cause device damage. To prevent ground loops caused by differences in potential between device
grounding points, the reference potential between the devices must be stabilized. Design grounding
appropriately so that noise current does not flow to ground lines between the devices.
For grounding methods, refer to the NJ-series CPU Unit Hardware User's Manual (Cat. No. W500),
NX-series CPU Unit Hardware User’s Manual (Cat. No. W535), NX-series NX502 CPU Unit
Hardware User’s Manual (Cat. No. W629), NX-series NX102 CPU Unit Hardware User’s Manual
(Cat. No. W593), or NX-series NX1P2 CPU Unit Hardware User’s Manual (Cat. No. W578).
• To obtain information on installing EtherNet/IP cable, contact ODVA.
ODVA web site: http://www.odva.org
• When you install an EtherNet/IP network that combines an information network with the control sys-
tem, and the communications load may be heavy due to tag data links, we recommend that you set
up a network where the load does not affect communications. For example, install the tag data links
in a segment that is separate from the information network.
2-2-2 Recommended Network Devices
Refer to 2-1 Selecting the Network Devices on page 2-2 for the devices recommended for use with the
built-in EtherNet/IP port.
2-2-3 Precautions When Laying Twisted-pair Cable
Connecting the Shield to Connector Hoods
 Between an EtherNet/IP Port and an Ethernet Switch
Connect the shield to connector hoods as described below.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-7
2-2
Network
Installation
2
2-2-1
Basic
Installation
Precautions
2 Installing Ethernet Networks
NJ-series CPU Unit NX-series CPU Unit
1000Base-T
10Base-T 100Base-TX 10Base-T 100Base-TX
*1
• Connect the shield at both ends • Connect the shield at both ends Connect the shield
or or at both ends
• Connect the shield only at the Ethernet • Connect the shield only at the Ethernet
switch side switch side. A clamp core must be at-
tached to the EtherNet/IP port side of
the cable.
*1. For NX701 CPU Units and NX502 CPU Units only.
• 10Base-T or 100Base-TX
Connect the cable shields to the connector hoods as described in either (1) or (2) below.


Question: Connecting the shields at both ends of the cable

Answer:
Connect the shields to the connector hoods at both ends of the cables.
Ethernet switch
Connect shield to connector hood
Connector Connector Connector
GR
terminal
Built-in EtherNet/IP port Power Supply
on NX-series CPU Unit Unit
STP Connector
(Shield) GR
terminal
Built-in EtherNet/IP port Power Supply
on NJ-series CPU Unit Unit
STP Connector
(Shield) GR
terminal


Question: Connecting the shields only at the Ethernet switch side

Answer:
Connect the shields to the connector hoods only at the Ethernet switch side.
• For an NX-series CPU Unit, a clamp core must be attached to the end of the cable at the
EtherNet/IP port side. For a recommended clamp core and attachment methods, refer to
Recommended Clamp Core and Attachment Method on page 2-10.
To comply with EMC standards, it is mandatory that a clamp core be attached when con-
necting the shield to the connector hood only at the Ethernet switch side.
• For an NJ-series CPU Unit, it is not necessary to attach a clamp core.
2-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
2 Installing Ethernet Networks
Ethernet switch
Connect shield to connector hood
Connector Connector Connector Do not connect shield to connector hood
GR
terminal
Built-in EtherNet/IP Power Supply
port on NX-series Unit
CPU Unit
Clamp core
STP Connector
(Shield) GR
terminal
Built-in EtherNet/IP Power Supply
port on NJ-series Unit
CPU Unit
STP Connector
(Shield) GR
terminal
Additional Information
Noise immunity may be reduced and device damage may occur due to ground loops, which
may be caused by improper shield connections and grounding methods.
When using a baud rate of 100 Mbps or less, it may be possible to alleviate this problem by
connecting the shield only at the Ethernet switch side as described in (2), rather than connect-
ing both ends as described in (1).
• 1000Base-T
Connect the shields to respective connector hoods at both ends of the cables.
This connection is required for 1000Base-T to ensure compliance with EMC standards.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-9
2-2
Network
Installation
2
2-2-3
Precautions
When
Laying
Twisted-pair
Cable
2 Installing Ethernet Networks
Ethernet switch
Connect shield to connector hood
GR Connector Connector Connector
terminal
Built-in EtherNet/IP Power Supply
port on NX-series Unit
CPU Unit
STP Connector
(Shield) GR
terminal
Built-in EtherNet/IP Power Supply
port on NX-series Unit
CPU Unit
STP Connector
(Shield) GR
terminal
 Between Two Ethernet Switches
Regardless of which baud rate is used, check with the Ethernet switch manufacturers for informa-
tion about installing the network between Ethernet switches, and in particular whether or not it is
necessary to connect the cable shields to the connector hoods.
Other Precautions When Laying the Twisted-pair Cable
• Firmly insert the connector until it locks into place when you connect the cable to the Ethernet switch
and the built-in EtherNet/IP port.
• Do not install the twisted-pair cable together with high-voltage lines.
• Do not install the twisted-pair cable near devices that generate noise.
• Do not install the twisted-pair cable in locations subject to high temperatures or high humidity.
• Do not install the twisted-pair cable in locations subject to excessive dirt, dust, oil mist or other con-
taminants.
Recommended Clamp Core and Attachment Method
When you use an NX-series CPU Unit and connect the cable shield only with the connector hood of
the Ethernet switch, you need to attach a clamp core to the EtherNet/IP port of the CPU Unit.
The recommended clamp core and attachment method are given below.
 Recommended Clamp Core
Manufacturer Product Model
NEC TOKIN Clamp core ESD-SR-250
ESD-SR-250 dimensions
2-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)