Question: 5 to 1,000 ms (NX701 CPU Unit) 15 − (RPI [ms]/100)

Answer:
1 to 1,000 ms (NX502 and NX102 CPU Units)
2 to 1,000 ms (NX1P2 CPU Unit)
1 to 1,000 ms (NJ-series CPU Unit)*1
1,000 to 10,000 ms 5% of the RPI
*1. Note that the RPI for a NJ-series CPU Unit with unit version 1.00 to 1.02 is between 10 ms to 1,000 ms.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-5
14-1
Communications
System
14
14-1-3
Packet
Interval
(RPI)
Accuracy
16
14
12
10
8
6
4
2
0
RPI [ms]
)%(
)±(
rorre
IPR
14 Communications Performance and Communications Load
0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000
14-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
14-2 Adjusting the Communications Load
In an Ethernet network using an Ethernet switch, the network bandwidth is not shared by all of the no-
des; independent transmission paths are established between individual nodes through the Ethernet
switch.
A dedicated communications buffer is established in the Ethernet switch for communications between
the nodes, and full-duplex communications (simultaneous transmission and reception) are performed
asynchronously with other transmission paths. The communications load in other transmission paths
does not affect communications, so packet collisions do not occur and stable, high-speed communica-
tions can be performed.
The Ethernet switch functions shown in the following table determine the performance of tag data
links.
Item Description
Buffer capacity This is the amount of data that can be buffered when packets ac-
cumulate at the Ethernet switch.
Multicast filtering This function transfers multicast packets to specific nodes only.
QoS function This function performs priority control on packet transfers.
The following table shows the setting ranges of the tag data link settings that can be made for a built-
in EtherNet/IP port.
NX-series CPU Unit NJ-series CPU Unit
Unit ver- Unit ver-
Item Description
NX701 NX502 NX102 NX1P2 sion 1.00 sion 1.03
to 1.02 or later
Network band- Physical 1,000 Mbps 100 Mbps or 10 Mbps
width Ethernet
baud rate
Allowable tag da- Maximum 40,000 20,000 12,000 3,000 pps 1,000 pps 3,000 pps
ta link communi- number of tag pps max. pps max. pps max. max. max. max.
cations band- data link (total of (total of (total of
width packets that 40,000 20,000 12,000
can be proc- pps with pps with pps with
essed in 1 two ports) two ports) two ports)
second (pps:
packets per
second)
Connection re- Number of 256 max. 64 max. 32 max. 32 max.
sources connections (total of (total of (total of 64
that can be 512 with 128 with with two
established two ports) two ports) ports)
Packet interval Refresh peri- 0.5 to 1 to 10,000 ms in 1-ms 2 to 10 to 1 to
(RPI: Requested od for tag da- 10,000 ms increments 10,000 ms 10,000 ms 10,000 ms
Packet Interval) ta in 0.5-ms in 1-ms in- in 1-ms in- in 1-ms in-
incre- crements crements crements
ments
When the tag data link settings exceed the capabilities of the Ethernet switch to be used, increase the
packet interval (RPI) value for adjustment.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-7
14-2
Adjusting
the
Communications
Load
14
14-2-1
Checking
Bandwidth
Usage
for
Tag
Data
Links
14 Communications Performance and Communications Load
Particularly when you configure the settings with an Ethernet switch that does not support multicast
filtering, you need to consider that multicast packets will be sent to all the nodes on the network with-
out setting the connections.
Additional Information
If you select Multi-cast 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.
If required tag data link performance cannot be achieved with the Ethernet switch, re-evaluate the
overall network configuration and take necessary measures such as selecting a different Ethernet
switch or splitting the network.
The following sections show how to check the device bandwidth used by the tag data links in the de-
signed network, and how to set appropriate values.
14-2-1 Checking Bandwidth Usage for Tag Data Links
The Network Configurator can display the bandwidth to be actually used for tag data links at each
built-in EtherNet/IP port, based on the connections set in the network configuration.
The device bandwidth used for tag data links can be checked by clicking the Detail Button in the
Usage of Device Bandwidth Area at the bottom of the Network Configuration Window.
Item Description
# The IP address of the device.
Comment A description of the device. The comment is displayed below the device icon.
The model number of the device is displayed by default.
Usage of Capacity (without The usage rate of allowable tag data link bandwidth for the device is given.
Multicast Filter) Bandwidth used/Allowable tag data link bandwidth
The values outside parentheses are for when multicast filtering is used.
The values inside parentheses are for when multicast filtering is not used.
Mbit/s (without Multicast Fil- The network bandwidth used by the device for tag data link communications is
ter) given.
The values outside parentheses are for when multicast filtering is used.
The values inside parentheses are for when multicast filtering is not used.
14-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
Item Description
Usage of IP multicast ad- The number of multicast IP addresses actually used by the device for commu-
dresses nications is given.
Total usage of IP multicast ad- The number of multicast IP addresses used in the entire network is given. This
dresses value is used to estimate the number of multicast filters required for a switch.
Network Total of Max. Mbit/s The total bandwidth used for tag data link communications in the entire network
is given.
Tag data links will not normally operate if the bandwidth allowed for the network
is exceeded.
 Checking the Usage of Capacity and Network Bandwidth for Tag Data
Links
The usage rate of allowable tag data link bandwidth for each built-in EtherNet/IP port is given in the
Usage of Capacity (without Multicst Filter) column, and the network bandwidth usage for tag da-
ta link communications is given in the Mbit/s (without Multicast Filter) column.
The usage rate and the network bandwidth usage of tag data link communications for which multi-
cast filtering is not supported by the Ethernet switch are given in parentheses in each correspond-
ing column. These values include bandwidth usage for multicast packets since they are sent to all
the nodes without connection settings.
These values can be adjusted as described in 14-2-4 Changing the RPI on page 14-11.
 Checking the Total Number of Multicast IP Addresses in the Network
When using an Ethernet switch that supports multicast filtering, there must be sufficient multicast
filters for the network. Based on the setting of connections, the Network Configurator indicates the
number of multicast IP addresses to be used in the entire network.
Make sure that the number of multicast IP addresses to be used in the entire network does not ex-
ceed the number of multicast filters supported by the Ethernet switch. If necessary, replace the
Ethernet switch with another one with sufficient multicast filters, or adjust the usage rate and net-
work bandwidth usage with the values given for an Ethernet switch without multicast filtering (i.e.,
the values in parentheses). These values can be adjusted as described in 14-2-4 Changing the RPI
on page 14-11.
 Checking the Total Maximum Network Bandwidth
The Network Configurator displays the total maximum bandwidth to be used for the entire network.
This value indicates the maximum possible bandwidth for a transmission path which connects
Ethernet switches in cascade. If this value exceeds the bandwidth for each cascade connection in
the actual network (e.g., 1,000 Mbps for an NX-series CPU Unit, or 100 Mbps for an NJ-series
CPU Unit), the bandwidth for some transmission paths may be exceeded depending on the net-
work wiring, and the tag data links may not operate normally.
If this occurs, calculate the bandwidth usage of each transmission path and make sure that the
bandwidth for any cascade connection is not exceeded, or adjust the bandwidth to ensure that the
value of Network Total of Max. Mbit/s does not exceed the bandwidth for any cascade connec-
tion. These values can be adjusted as described in 14-2-4 Changing the RPI on page 14-11.
14-2-2 Tag Data Link Bandwidth Usage and RPI
The usage rate of allowable tag data link bandwidth as given in the Usage of Capacity (without
Multicast Filter) column can be adjusted by changing the packet interval (RPI) setting.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-9
14-2
Adjusting
the
Communications
Load
14
14-2-2
Tag
Data
Link
Bandwidth
Usage
and
RPI
14 Communications Performance and Communications Load
If the RPI is set shorter, the Usage of Capacity (without Multicast Filter) will increase.
If the RPI is set longer, the Usage of Capacity (without Multicast Filter) will decrease.
The RPI can be set in one of the following ways.
• Setting the same PRI for all the connections
• Setting a PRI for connections of a particular device
• Setting a PRI for a particular connection
When the same RPI is set for all the connections, the Usage of Capacity (without Multicast Filter)
will basically increase proportionally as the RPI is set shorter.
Example: If the Usage of Capacity (without Multicast Filter) is 40% with the PRI set to 50 ms for all
the connections, the Usage of Capacity (without Multicast Filter) may increase to 80% when the
RPI is changed to 25 ms for all the connections.
Precautions for Correct Use
If the Usage of Capacity (without Multicast Filter) is between 80% and 100%, some opera-
tion with the Network Configuator which may cause load on the network, such as monitoring, or
message communications with some user application may temporarily cause excessive load on
the network and result in timeouts. If timeouts occur, increase one or all of the RPI values and
reduce the usage of capacity.
14-2-3 Adjusting Device Bandwidth Usage
This section provides methods for adjusting the device bandwidth usage for tag data links.
Precautions for Correct Use
The Ethernet switch should be able to support the maximum network bandwidth for each CPU
Unit. The maximum network bandwidth for each CPU Unit model is as follows.
• NX701 CPU Unit: 1,000 Mbit/s
• NX502 CPU Unit: 1,000 Mbit/s
• NX102 CPU Unit: 100 Mbit/s
• NX1P2 CPU Unit: 100 Mbit/s
• NJ-series CPU Unit: 100 Mbit/s
Ethernet Switches without Multicast Filtering
• Is the Mbit/s (without Multicast Filter) value for each node below the maximum network band-
width?
If any node exceeds the maximum network bandwidth, change the connection settings, such as the
RPI.
• Is the value of Usage of Capacity (without Multicast Filter) for each node below 100%?
If any node exceeds 100%, change the connections settings, such as the RPI.
• Is the value of Network Total of Max. Mbit/s below the maximum network bandwidth?
If the value exceeds the maximum network bandwidth, the bandwidth for some transmission paths
(e.g., an Ethernet switch or media converter) may be exceeded depending on the network wiring
(e.g., cascade connection of Ethernet switches), and the tag data links may not operate normally.
Check if the bandwidth of the transmission path in each cascade connection is not exceeded. If the
bandwidth is exceeded, rewire the network or increase the bandwidth between Ethernet switches
14-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
(e.g., increase to 1 Gbps). If these countermeasures are not possible, change the connection set-
tings such as the RPI settings, and adjust the bandwidth to ensure that the value of Network Total
of Max. Mbit/s does not exceed the bandwidth for any cascade connection.
Ethernet Switches with Multicast Filtering
• Is the Mbit/s value for each node below the maximum network bandwidth?
If any node exceeds the maximum network bandwidth, change the connection settings, such as the
RPI.
• Is the Usage of Capacity value for each node below 100%?
If any node exceeds 100%, change the connection settings, such as the RPI.
• Is the Network Total of Max. Mbit/s value below the maximum network bandwidth?
If the value exceeds the maximum network bandwidth, the bandwidth for some transmission paths
(e.g., an Ethernet switch or media converter) may be exceeded due to the network wiring (e.g., cas-
cade connection of Ethernet switches), and the tag data links may not operate normally. Check if the
bandwidth of the transmission path in each cascade connection is not exceeded. If the bandwidth is
exceeded, rewire the network or increase the bandwidth between Ethernet switches (e.g., to 1
Gbps). If these countermeasures are not possible, change the connection settings such as the RPI
settings, and adjust the bandwidth to ensure that the value of Network Total of Max. Mbit/s does
not exceed the bandwidth for any cascade connection.
• Is the Mbit/s (without Multicast Filter) value for each node below the maximum network band-
width? Or, is the value of Usage of Capacity (without Multicast Filter) for each node below
100%?
If any node exceeds either of them, check whether the multicast filtering on the relevant Ethernet
switch is functioning correctly. If the number of multicast filters on the Ethernet switch is less than
the number of Total usage of IP multicast addresses, the bandwidth for some transmission paths
may be exceeded depending on the network wiring (e.g., cascade connection of Ethernet switches),
and the tag data links may not operate normally. Calculate the number of multicast filters required
for each Ethernet switch on the network, and check if the resulting number is below the number of
multicast filters provided by the Ethernet switch. If the Ethernet switch does not have a sufficient
number of multicast filters, replace it with another one which has sufficient multicast filters, or
change the connection settings, such as the RPI settings.
14-2-4 Changing the RPI
You can check Usage of Capacity (without Multicast Filter) values offline for the usage rate of al-
lowable tag data link bandwidth if you follow the procedure provided in 14-2-1 Checking Bandwidth
Usage for Tag Data Links on page 14-8.
You can adjust Usage of Capacity (without Multicast Filter) values by changing packet interval
(RPI) values.
If required communications performance cannot be achieved after the adjustment, re-evaluate the net-
work configuration.
1
Make required settings in the Network Configuration Window on the Network Configurator.
2
Click the Detail Button in the Usage of Device Bandwidth Area at the bottom of the Network
Configuration Window.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-11
14-2
Adjusting
the
Communications
Load
14
14-2-4
Changing
the
RPI
14 Communications Performance and Communications Load
The Usage of Device Bandwidth Dialog Box is displayed.
The Usage of Capacity (without Multicast Filter) column shows the usage rate of allowable
tag data link bandwidth, and the Mbit/s (without Multicast Filter) column shows the network
bandwidth usage.
3
You can adjust the Usage of Capacity (without Multicast Filter) value by changing the pack-
et interval (RPI) for the relevant device.
There are three methods for changing the RPI as shown below.
• Method 1: Set the Same RPI for All the Connections
You can adjust the Usage of Capacity (without Multicast Filter) value by changing the
packet interval (RPI) values for all the connections at the same time.
1) Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog
Box.
14-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
2) The Set Packet Interval (RPI) Dialog Box is displayed. Input a new RPI value, and click
the OK Button.
• Method 2: Change the RPI for a Specific Device
You can adjust the Usage of Capacity (without Multicast Filter) value by changing the RPI
for all the connections of a specific device.
Note that the Usage of Capacity (without Multicast Filter) values for the target devices of
the connections are also changed.
1) Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog
Box.
2) The Set Packet Interval (RPI) Dialog Box is displayed. In the Target Device Area, clear
the check boxes for devices to which this RPI setting change is not applied.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-13
14-2
Adjusting
the
Communications
Load
14
14-2-4
Changing
the
RPI
14 Communications Performance and Communications Load
3) Input a new RPI value, and click the OK Button.
• Method 3: Change the RPI for a Specific Connection
You can adjust the Usage of Capacity (without Multicast Filter) value by changing the RPI
for a specific connection.
Note that the Usage of Capacity (without Multicast Filter) value for the target device of the
connection are also changed.
1) Click the Close Button in the Usage of Device Bandwidth Dialog Box.
2) Double-click the device that is set as the originator of the connection. The Edit Device
Parameters Dialog Box is displayed.
14-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
3) In the Register Device List Area, select the connection for which you want to change
the RPI, and click the Edit Button.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-15
14-2
Adjusting
the
Communications
Load
14
14-2-4
Changing
the
RPI
14 Communications Performance and Communications Load
4) The Edit Connection Dialog Box for the device is displayed. Input a new packet interval
(RPI) value, and click the OK Button.
4
If the bandwidth usage rate is not set as desired even after the above operation, re-evaluate
the network configuration,considering the following points. (Refer to 14-2-3 Adjusting Device
Bandwidth Usage on page 14-10.)
• Reduce the number of nodes and connections
• Split the network
5
Check the bandwidth usage rate again.
After you change the connection settings, click the Detail Button in the Usage of Device
Bandwidth Area at the bottom of the Network Configuration Window to check the bandwidth
usage as described in 14-2-1 Checking Bandwidth Usage for Tag Data Links on page 14-8.
It is important to check the bandwidth usage particularly after you change the RPI values for
individual connections, instead of setting the same RPI for all the connections.
6
Run user tests to verify that there are no problems with the new values.
14-2-5 RPI Setting Examples
The following examples explain how to calculate the packet intervals (RPIs) in the following network
configuration.
14-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
Conditions
• Connections:
Example) Seventeen NJ501-1300 Units are connected to the network.
Each device has one 100-word tag for sending and sixteen 100-word tags for receiving, and ex-
changes data with each other.
The packet interval (RPI) for all the connections is set to 120 ms.
The IP addresses of the devices range from 192.168.250.1 to 192.168.250.17.
IP address: 192.168.250.1 192.168.250.2 192.168.250.3 192.168.250.17
NJ501-1300 NJ501-1300 NJ501-1300 NJ501-1300
Send
100CH In_02_a In_03_a In_17_a
Out_01_a
Send
100CH In_01_b In_03_b In_17_b
Out_02_b
Send
100CH In_01_c In_02_c In_17_c 17 network variables,
Out_03_c
100 words ea ch
Send
100CH In_01_t In_02_t In_03_t
Out_17_t
NJ501-1300: 17 Units
Connection RPI: 120 ms
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-17
14-2
Adjusting
the
Communications
Load
14
14-2-5
RPI
Setting
Examples
14 Communications Performance and Communications Load
Checking the Device Bandwidth Usage
When you click the Detail Button in the Usage of Device Bandwidth Area, the window shows that the
usage rate of the tag data link bandwidth for each device is 40.83%, as given in the Usage of Capacity
column in the following window.
Changing Settings
Method 1: Setting the Same RPI for All the Connections
In the previous example, the usage rate of allowable tag data link bandwidth is 40.83% for all the devi-
ces as given in the Usage of Capacity column, and the RPI is set to 120 ms for all the connections. In
the next example, change the RPI to 40 ms so as to increase the usage rate of allowable tag data link
bandwidth up to 80% or less.
Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog Box to display
the Set Packet Interval (RPI) Dialog Box.
Input 40 ms as the new RPI value, and click the OK Button.
14-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
If you set the same packet interval (RPI) for all the connections, the table shows that the usage rate of
allowable tag data link bandwidth is 74.50% for all the device as shown in the Usage of Capacity col-
umn, and this indicates that the shortest packet interval is 40 ms.
Method 2: Changing the Packet Intervals (RPIs) of Specific Devices
In this example, set faster tag data links for specific two devices: 192.168.250.1 and 192.168.250.10.
Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog Box to display
the Set Packet Interval (RPI) Dialog Box.
In the Target Device Area, clear the check boxes for devices to which this RPI change is not applied
(all the devices except 192.168.250.1 and 192.168.250.10). Input 30 ms as the new RPI value, and
click the OK Button.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-19
14-2
Adjusting
the
Communications
Load
14
14-2-5
RPI
Setting
Examples
14 Communications Performance and Communications Load
The usage rate of allowable tag data link bandwidth for each of the two devices, 192.168.250.1 and


Question: 168.250.10, increases to 87.00% as shown in the Usage of Capacity column, and this indicates

Answer:
that the shorter RPI is set for the connections of these devices.
Note that the usage rate of allowable tag data link bandwidth for all the other devices is also increased
from 40.83% to 44.50% since they are connected with the two devices, 192.168.250.1 and


Answer: In this case, if the Ethernet switch has no multicast filter, the Usage of Capacity value would be


Question: 33% and communications errors might occur due to traffic overload at the built-in EtherNet/IP port.

Answer:
Method 3: Changing the Packet Interval (RPI) of a Specific Connection
In this example, set faster tag data links for a specific connection of a device, 192.168.250.1. Double-
click the device, 192.168.250.1, in the Network Configuration Window.
14-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
Since the Register Device List shows a list of devices connected with 192.168.250.1, double-click a
device, 192.168.250.10, in the list.
Input 10 ms as the new RPI value in the Edit Connection Dialog Box, and click the OK Button. The
usage rate of allowable tag data link bandwidth for the device 192.168.250.1 increases to 50.17% as
shown in the Usage of Capacity column, and this indicates that the RPI for the specific connection is
set shorter.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-21
14-2
Adjusting
the
Communications
Load
14
14-2-5
RPI
Setting
Examples
14 Communications Performance and Communications Load
Note that the usage rate of allowable tag data link bandwidth for the device, 192.168.250.10, is also
increased from 40.83% to 51.00%.
14-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14-3 I/O Response Time in Tag Data Links
Additional Information
This section describes built-in EtherNet/IP ports on the NX and NJ-series CPU Units.
Compared to those built-in EtherNet/IP ports, EtherNet/IP Units, and built-in EtherNet/IP ports
on CJ2H CPU Units (CJ2H-CPU6£-EIP) and CJ2M CPU Units (CJ2M-CPU3£) support differ-
ent data processing performance. Refer to 6-4 Tag Data Links with Other Models on page 6-91
for details.
As explained in 6-1-7 Concurrency of Tag Data Link Data on page 6-14, the tag (network variable) with
a refreshing task is refreshed when the refreshing task is executed in the user program. By setting the
refreshing task, you can calculate the I/O response time that is not affected by the system service.
Precautions for Correct Use
The refreshing task must be set to all tags (network variables). If both tags (network variable)
with a refreshing task and without it exist in a configuration, system service may affect the oper-
ation and I/O response time described in this section may not be maintained.
This section describes the I/O response time when refreshing tasks are set properly.
14-3-1 Timing of Data Transmissions
The following figure shows the timing of transmitting data for tag data link between a built-in
EtherNet/IP port and a CPU Unit.
Data is transmitted at the timing of executing the system common processing 2 of the refreshing task.
I/O refresh Control processing
Refreshing Execution of System common programs processing 1 atad tuptuO gnissecorp atad tupnI gnissecorp nommoc metsyS 1 gnissecorp noitoM lortnoc nommoc metsyS 2 gnissecorp atad tuptuO gnissecorp
14 Communications Performance and Communications Load
Data received.
Primary periodic task
Controller Processing
Variable refresh processing
Controller task period
You can specify either of the following task types for a refreshing task.
• Primary periodic task
The primary periodic task has the highest execution priority. It is executed with high speed and high
precision.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-23
14-3
I/O
Response
Time
in
Tag
Data
Links
14
14-3-1
Timing
of
Data
Transmissions
14 Communications Performance and Communications Load
• Periodic task
A periodic task is executed during the interval between executions of a primary periodic task.
You do not need to specify a refreshing task for tags (variables) with AT specifications; the tag data is
transmitted in a primary periodic task. (This applies to NX502, NX102, NX1P2, and NJ-series CPU
Units.)
Specify a task type for each tag for tag data link processing.
On the Sysmac Studio, set a refreshing task for each variable assigned as a tag.
Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on setting refresh-
ing tasks.
14-3-2 Built-in EtherNet/IP Port Data Processing Time
This section describes the data processing time required to transfer data between the built-in Ether-
Net/IP port and the CPU Unit.
Data Processing Time Overview
The time required for data processing consists of the following three elements.


Question: Variable Access Time

Answer:
Calculate the time required to transfer tag data, which is regarded as the time required to access
the variable.
This calculation is performed for each task. Therefore, if multiple tag sets are set for the same re-
freshing task, use the total for all tag values in the tag sets.
Use the following equation for calculating the variable access time.
Variable access time [μs] = total size of variables [bytes] × a + number of variables × b + number of
accesses × c + d
Number of accesses: equal to the number of tag sets
a to d: Constant values as given below
Constant value (μs)
CPU Unit model
a b c d
NX701-££££ 0.0005 0.033 2.67 7.22
NX502-££££ 0.0012 0.0736 1.34 17.33
NX102-££££ 0.0040 0.240 3.27 25.21
NX1P2-££££ 0.0040 0.240 3.27 25.21
NJ501-££££ 0.0010 0.490*1 1.41 6.68
NJ301-££££ 0.0015*2 0.560*3 2.15 7.52
NJ101-££££ 0.0015 0.560 3.83 7.52
*1. The value is 0.58 for CPU Units with unit version 1.02 or earlier.
*2. The value is 0.0009 for CPU Units with unit version 1.02 or earlier.
*3. The value is 1.03 for CPU Units with unit version 1.02 or earlier.


Question: Number of Data Transfers

Answer:
Tag data transfer is executed as part of the task processing.
14-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
If the time required to process the data transfer is greater than the variable access time (*2), the
entire data cannot be sent in one task period and needs to be split and sent over multiple times
instead.
Number of data transfers = Time required to send the entire data (*1) / Variable access time (*2)
set for the task
*1. This is the variable access time as calculated in step 1 above.
*2. The variable access time is the maximum processing time for accessing the variable. Double-click Task
Settings under Configurations and Setup on the Sysmac Studio to display the Task Settings Tab
Page, and configure the settings for each task.
Precautions for Correct Use
The maximum number of tag data link words that can be transferred through a built-in
EtherNet/IP port is 184,832 words on an NX701 CPU Unit (total of 369,664 words with two
ports), 46,208 words on an NX502 CPU Unit (total of 92,416 words with two ports), 9,600 words
on an NX102 CPU Unit (total of 19,200 words with two ports), and 9,600 words on an NX1P2
CPU Unit or NJ-series CPU Unit.
If the number of tag data link words exceeds the number of words that can be exchanged with
the CPU Unit at one time, the data is divided and transferred over multiple times


Question: Actual Time Required for Data Transfer

Answer:
You can use the task period of the refreshing task and the number of data transfers as calculated
in (2) above to calculate the actual time required to transfer the data.
Task period × Number of data transfers
Data Processing Time Calculation Example
The following shows an example to explain how to calculate the time required for tag data transfer.
• CPU Unit model
NJ501-££££
• Refreshing task
Primary periodic task
Task period: 500μs (variable access time: 3%)
• Settings of tag sets
Tag set Refreshing task Number of variables Total size of variables
Tag set A Primary periodic task 8 600 bytes
Tag set B Primary periodic task 4 200 bytes
Tag set C Primary periodic task 10 1,000 bytes
1
Calculate the variable access time as shown below.
[(600 + 200 + 1,000) bytes × 0.001 μs] + [(8 + 4 + 10) variables × 0.49 μs] + 3 × 1.41 μs + 6.68
μs = 23.49 μs
2
Calculate the number of data transfers.
Time required for data transfer: Variable access time in step1 = 23.49 μs
Variable access time set for the task: 500 μs × 0.03 = 15 μs
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-25
14-3
I/O
Response
Time
in
Tag
Data
Links
14
14-3-2
Built-in
EtherNet/IP
Port
Data
Processing
Time
14 Communications Performance and Communications Load
Number of data transfers 23.49 μs ÷ 15 μs = 1.6 times
Thus, approximately two data transfers are required.
3
Calculate the actual time required for the entire data transfer.
500 μs × 2 times = 1,000 μs
14-3-3 Relationship between Task Periods and Packet Intervals (RPIs)
Effect of Tag Data Links on Task Periods
Tag data transfer is executed as part of the task processing.
Therefore, the tag data transfer process is added to the task processing for tasks set as a tag’s re-
freshing task. This requires you to make adjustments to the variable access time and task period in
the Task Settings Tab Page so that these processes are completed within a single task period.
1
Calculate the time required for the data transfer and set the result as the variable access
time(*).
For the formula for calculating the time required for data transfer, refer to Data Processing
Time Overview on page 14-24.
* If the same refreshing task is set for multiple tag sets, calculate the total time required for all tags in tag
sets.
2
Set the variable access time in the Task Setup to a value equal to or greater than the value
calculated in step 1 above.
Adjust the task period time after adding in the time calculated in step 1. Use the Sysmac Studio
to set the variable access time and task period settings.
Refer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details.
Adjusting Packet Intervals (RPIs) According to the Task Period
Tag data is transferred based on the actual time required for the transfer (task period × number of data
transfers), regardless of the packet interval (RPI) setting.
Set the packet interval (RPI) as below.
Actual time required for data transfer (Task period × Number of data transfers) < RPI
For details on the actual time required for data transfer, refer to 14-3-2 Built-in EtherNet/IP Port Data
Processing Time on page 14-24.
Example: Relationship between the RPI Setting and the Time Required for Data Transfer
• Task period: 10 ms
• Number of data transfers: 2 times
• Actual time required for data transfer: 10 ms × 2 times = 20 ms
Regardless of the RPI value, the time required for the data transfer is 20 ms.
14-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
I/O refreshing
User program execution
Motion control
RPI of 10 ms RPI of 20 ms
Example: Primary periodic task Example: Primary periodic task
(1) (2) (1) (2)
Task period: 10 ms Task period: 10 ms
Send data Send data
processing Task period × 2 processing Task period × 2
Refreshing period Refreshing period
during RPI during RPI:
10 ms 20 ms
To Controller #2 To Controller #2
Time required to transfer data from Controller #1: 20 ms
noissimsnarT
1#rellortnoC
htap
noissimsnarT
1#rellortnoC
htap
14 Communications Performance and Communications Load
OI
UPG
MC
Data link processing
(system common processing 3)
OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC
Tag data link service Tag data link service
14-3-4 Maximum Tag Data Link I/O Response Time
You can calculate the maximum I/O response time by adding up the time of (1) to (6) in the following
figure.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-27
14-3
I/O
Response
Time
in
Tag
Data
Links
14
14-3-4
Maximum
Tag
Data
Link
I/O
Response
Time
(1) (2) (3)
Example of data transfer processing over 3 task periods
noissimsnarT
tuptuO
ecived
tupnI
htap
ecived
I/O refreshing
User program execution
Motion control
Data link processing (system
Tag data link I/O response time common processing 2)
(4) Network transmission delay time
(5) Receive data
processing time
(1) Input ON
response time (2) pS re on ced s d sa inta g time (3) RPI (6) rO esu ptp ou nt s O e N tim e
Input
Task period
Tag data link
refresh period
Controller #2
processing
Task period
rellortnoC
rellortnoC
1#
2#
14 Communications Performance and Communications Load
OI
UPG
MC
Example: Primary periodic task
OIUP MC OIUP MC OIUP MC OIUP MC OIUP MC Controller #1 processing
G G G G G
Tag data link service
Tag data link service
OIUP MC OIUP MC OIUP MC OIUP MC OIUP MC
G G G G G
Output
Additional Information
• In CPU Units with unit version 1.03 or later, tag data link is processed in the tag data link
service.
• In CPU Units with unit version 1.00 to 1.02, tag data link is processed in the system service. If
a tag data link timeout occurs, reconsider the execution time of the system service.
• The tag data link service is not executed during execution of the communications bridge serv-
ice. Therefore, the I/O response time for the tag data links may be longer when CIP Safety
communications are performed.


Question: Input ON Response Time

Answer:
The input ON response time contains the delay time for the external input device from when the
input occurs until the switch actually changes to ON and the time until the input data is stored in
the memory area of the CPU Unit. Refer to the input delay information of the device for input
switch delay time.
One task period is required until the input data is stored in the memory area of the CPU Unit. Ac-
cordingly, the input ON response time is calculated as below.
Input ON response time = Input device delay time + Task period


Question: Send Data Processing Time

Answer:
This is the time required to transfer a variable from a CPU Unit to the built-in EtherNet/IP port.
14-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
Since data transfer is executed as part of task processing, the send data processing time is as
long as the task period.
If the data is larger than the allowable data size to send in a single task process (which can be set
with Variable Access Time of the task), the data will be transferred over more than one task peri-
od, requiring additional time equivalent to the task period multiplied by the number of transfers.
For details on the send data processing time, refer to 14-3-2 Built-in EtherNet/IP Port Data Proc-
essing Time on page 14-24.


Question: Packet Interval (RPI)

Answer: This is the communications refresh period which can be specified on the Network Configurator.


Question: Network Transmission Delay Time

Answer: The transmission delay on an Ethernet line is 50 μs or less. This delay time can be ignored.


Question: Receive Data Processing Time

Answer:
This is the time required to transfer data that is received on the built-in EtherNet/IP port to a varia-
ble in the CPU Unit.
Since data receive is executed as part of task processing, the receive data processing time is as
long as the task period.
If the data is larger than the allowable data size to receive in a single task process (which can be
set with Variable Access Time of the task), the data will be transferred over more than one task
period, requiring additional time equivalent to the task period multiplied by the number of transfers.
For details on the receive data processing time, refer to 14-3-2 Built-in EtherNet/IP Port Data Proc-
essing Time on page 14-24.
Data transfer is executed once every task period. If another input data is received just after the da-
ta transfer in the current task period, the transfer of the received data will be delayed by one Con-
troller task period.
Additional Information
If the Unit has connections with multiple nodes, the total amount of data to be exchanged will
increase, and the Unit may send or receive data larger than the data size allowed per transfer.
In this case, the number of data transfers increases.


Question: Output ON Response Time

Answer:
This is the delay time from when an output command is issued by the Controller until the output is
executed on the external output device.
Output ON response time = Output device delay time + CPU task period
Additional Information
The I/O response time may be longer due to noise, or other causes.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-29
14-3
I/O
Response
Time
in
Tag
Data
Links
14
14-3-4
Maximum
Tag
Data
Link
I/O
Response
Time
14 Communications Performance and Communications Load
14-4 Message Service Transmission Delay
This section describes delay time in the service processing of a CIP communications instruction (CIP-
Write).
Instruction (CIPWrite) executed. Instruction completed.
OI UPG MC IO UPG MC OI UPG MC OI UPG MC
Controller#1
Command generated. Received response interpreted.
System System
service × service
Line Line
Transmission path
Controller#2
×
IO UPG MC IO UPG MC Variable written.
Received command interpreted. Response generated.
System System
service service
Transmission System Transmission Receive System Variable System Transmission Receive System
delay service delay delay service written. service delay delay service
Task period Line Task period Task period Line Task period
(local node) (remote node) (remote node) (local node)
Maximum transmission delay time = Send delay + System service execution time + Transmission delay
(Local node task period)
+ Receive delay + System service execution time
(Remote node task period)
+ Variable write time + System service execution time + Transmission delay
(Remote node task period)
+ Receive delay + System service execution time
(Local node task period)
Processes with delay time are processed within the task period of each node as shown in the above
diagram.
Delay time related to transmission lines is as below.
14-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
14 Communications Performance and Communications Load
 Transmission Delay
The transmission delay on an Ethernet line is 50 μs or less. This delay time can be ignored.
Additional Information
Depending on the actual operating environment, the transmission time may be longer
than the one calculated with the equations given above.
The following factors can cause longer transmission time: the load rate of the network (the de-
gree of network congestion), the window size of each network node, traffic load on the built-in
EtherNet/IP port (e.g., simultaneous tag data link communications), and the system configura-
tion.
CIP communications instructions are executed in the system service process.
If a timeout occurs for a CIP communications instruction, reconsider the execution time for the
system service.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-31
14-4
Message
Service
Transmission
Delay
14
14 Communications Performance and Communications Load
14-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15
Troubleshooting
This section explains how to detect errors, how to check the communication status of
the EtherNet/IP network with the Network Configurator, and how to identify and trou-
bleshoot errors which may occur due to the tag data link connection status.
15-1 Overview of Troubleshooting......................................................................15-2
15-2 Checking Status with the Network Configurator.......................................15-3
15-2-1 The Network Configurator's Device Monitor Function...................................15-3
15-2-2 Connection Status Codes and Troubleshooting...........................................15-11
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-1
15
15 Troubleshooting
15-1 Overview of Troubleshooting
You manage all of the errors that occur on the NJ/NX-series Controller as events.
This allows you to see what errors have occurred and find corrections for them with the same methods
for the entire range of errors that is managed (i.e., CPU Unit, NX Units, NX-series Slave Terminals,
EtherCAT slaves,*1 and CJ-series Units).
*1. Only Sysmac devices are supported.
Host computer HMI
Checking Network Status
EtherNet/IP
Troubleshooter
Network Configurator
Built-in
NJ/NX-series EtherNet/IP CJ-series Units and
Port
CPU Unit NX Units
Troubleshooting
Sysmac Studio
Built-in EtherCAT port
EtherCAT
EtherCAT
slaves
Error management range for NJ/NX-series Controller
You can use the troubleshooting functions of the Sysmac Studio or the Troubleshooter on an HMI to
quickly check for errors that have occurred and find corrections for them.
Refer to the NJ/NX-series Troubleshooting Manual (Cat. No. W503) for error types and details, specific
corrections when errors occur, and troubleshooting information on the entire NJ/NX-series Controllers.
15-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
15-2 Checking Status with the Network
Configurator
15-2-1 The Network Configurator's Device Monitor Function
Connect the Network Configurator online, select the device to be checked, right-click to display the
pop-up menu, and select Monitor.
The Monitor Device Dialog Box will be displayed.
Precautions for Correct Use
Monitoring may not be performed if the following settings are configured on the NJ/NX-series
Controller on the connection route or on the destination NJ/NX-series Controller. If monitoring is
not performed, check the following settings. Refer to CIP Message Server on page 4-21,
andPacket Filter on page 4-8 for details on the settings.
• The Do not use Option is selected for the CIP message server.
• The Use Option is selected for Packet Filter.
Additional Information
If a communications error occurs during monitoring, the dialog box will continue to show the last
information that was collected.
To start monitoring again, close the Monitor Device Dialog Box, and then open the Monitor
Device Dialog Box again.
You cannot monitor the CIP Safety communications status with Network Configurator. Refer to the NX-
series Safety Control Unit User’s Manual (Cat. No. Z930) for details on confirming CIP Safety commu-
nications status.
 Status 1 Tab Page
The following check boxes are displayed for the status. If a check box is checked with , the sta-
tus is TRUE.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-3
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-1
The
Network
Configurator's
Device
Monitor
Function
15 Troubleshooting
Classification Item TRUE status description
Ethernet Status Com. Controller Error An error occurred in the Communications Controller.
IP Address Duplicated The same IP address is assigned to more than one
node.
On-Line The Unit is online. (The EtherNet/IP Unit can perform
communications processing.)
Multiple Switch ON More than one data link start/stop switch changed to
TRUE at the same time.
Data Link Status Comparison Error The remote node information in the tag data link param-
eters was different from the actual node information.
Main causes:
• The specified target does not exist.
• The variable name does not match.
• The connection size is different.
• Connection resources are not sufficient.
Data Link Status Tag Data Link Error There were two or more errors in a connection as an
originator.
Invalid Parameter An error was found in the parameters for tag data links
that are saved in non-volatile memory.
All Tag Data Link Tag data links are communicating in all connections as
the originator.
Tag Data Link Tag data links are communicating in one or more con-
nections as the originator.
Configuration Er- Ethernet Link Status A link is established with the Ethernet switch.
ror Status Ethernet Basic Settings Log- The following settings are incorrect:
ic Error • TCP/IP settings (IP address, subnet mask, or link set-
tings)
IP Router Table Error There is a mistake in the IP router table information.
Ethernet Ext Config Logical Always FALSE.
Error
BOOTP Server Error One of the following errors occurred when using the
BOOTP server:
• The IP address received from the BOOTP server is
incorrect.
• A communications timeout occurred with the server.
In the Target Node Status, information about the target node that acts as the originator is dis-
played.
If all tag data link connections to the node are established and normal, this information is displayed
in blue. However, if any connection is broken it is displayed in red.
15-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-5
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-1
The
Network
Configurator's
Device
Monitor
Function
15 Troubleshooting
 Status 2 Tab Page
This tab page displays information on nodes with tag data link originator settings. This information
is in blue if the connection is normal, or red if an error occurred.
Additional Information
The target Controller status can be used when the Controller status is set to Included for all the
target sets for both originator and target connections.
If it is set to Not included, it is grayed out on the display.
15-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
 Connection Tab Page
• Target Node Status
Information about the target node that acts as the originator is displayed.
If all tag data link connections to the node are established and normal, this information is dis-
played in blue. However, if any connection is broken it is displayed in red.
However, this information is displayed in gray if the connection to the node is stopped.
• Connection Status
The Status Column of the connection status shows the status of each connection that is set as
the originator. The connection status can be used to identify the cause of tag data link errors.
Refer to 15-2-2 Connection Status Codes and Troubleshooting on page 15-11 for details on the
connection status.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-7
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-1
The
Network
Configurator's
Device
Monitor
Function
15 Troubleshooting
 Controller Log Tab Page
This tab page displays the Controller event log that is stored in the CPU Unit.
The error history shows errors that have occurred. It can be saved in a file in the computer.
Refer to the operation manual of the CPU Unit for details on error information.
15-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
 Tag Status Tab Page
This tab page displays if the tag settings for each tag for tag data links are set so that data can be
exchanged with the CPU Unit.
The following status is displayed depending on the status that is set.
Normally resolved: Normal data exchange is possible.
Resolving: The variables with tags are being resolved.
When the resolution is completed normally, a connection will be established and the data ex-
change will start.
Different sizes: Different sizes are set for the network variables and the tag settings.
A connection will not be established for a tag for which this error occurs.
No tag: A network variable is not set in the variable table in the CPU Unit for the specified tag setting. Or,
instead of a member of union variable, unions are specified.
A connection will not be established for a tag for which this error occurs.
Attribute error: 1. Writing is not possible for Read Only and Constant attributes.


Question: The I/O direction that is set in the tag data link settings does not agree with the I/O direction

Answer:
of the variable in the CPU Unit. There is an error in the setting of a Network Publish attribute
for a CPU Unit variable.
A connection will not be established for a tag for which this error occurs.
If the status is not “Normal resolution completed,” check the tag data link settings or the network
variable settings in the variable table in the NJ/NX-series CPU Unit.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-9
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-1
The
Network
Configurator's
Device
Monitor
Function
15 Troubleshooting
 Ethernet Information Tab Page
This tab page displays the communications status at the communications driver level of the built-in
Ethernet/IP port.
The error counter information can be used to confirm whether communications problems have oc-
curred.
The tag data link information can be used to confirm characteristics such as the Bandwidth (pps).
15-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
15-2-2 Connection Status Codes and Troubleshooting
This section explains how to identify and correct errors based on the tag data link's connection status.
The connection status can be read using the Connection Tab Page of Monitor Device Window with
the Network Configurator. Refer to 15-2-1 The Network Configurator's Device Monitor Function on
page 15-3 for details.
Additional Information
The connection status has the same meaning as the Connection Manager's General and Addi-
tional error response codes, as defined in the CIP specifications.
The following table shows the likely causes of the errors causes for each configuration and connection
status (code).
Originator Target
Configuration 1 CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21,
CJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M- CJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-
CPU3£, NJ501-££££, NJ301-££££, NJ101- CPU3£, NJ501-££££, NJ301-££££, NJ101-
££££, NX701-££££, NX502-££££, NX- ££££, NX701-££££, NX502-££££, NX-
EIP201, NX102-££££, NX1P2-££££££ EIP201, NX102-££££, NX1P2-££££££
Configuration 2 CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, Products from other manufacturers
CJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-
CPU3£, NJ501-££££, NJ301-££££, NJ101-
££££, NX701-££££, NX502-££££, NX-
EIP201, NX102-££££, NX1P2-££££££
Configuration 3 Products from other manufacturers CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21,
CJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-
CPU3£, NJ501-££££, NJ301-££££, NJ101-
££££, NX701-££££, NX502-££££, NX-
EIP201, NX102-££££, NX1P2-££££££
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
00 0000 Normal status code: --- --- ---
The connection has been opened and
the tag data link is communicating nor-
mally.
01 0100 Error code returned from target: This error does Depends on Depends on
Attempted to open multiple connections not occur. the target's the originator's
for the same connection. specifications. specifications.
(This error (This error
should not oc- should not oc-
cur. If it does, cur. If it does,
contact the tar- contact the
get device's originator devi-
manufacturer.) ce's manufac-
turer.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-11
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-2
Connection
Status
Codes
and
Troubleshooting
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0103 Error code returned from target: This error does Confirm that Confirm that
Attempted to open a connection with an not occur. the target sup- the originator
unsupported transport class. ports Class 1. supports Class


Question: 01 0106 Duplicate consumers: If the tag data Depends on If the tag data

Answer:
Attempted to open multiple connections link is stopped the target's link is stopped
for single-consumer data. or started, this specifications. or started, this
error may oc- (Contact the error may oc-
cur according target device's cur according
to the timing, manufacturer.) to the timing,
but the system but the system
will recover au- will recover au-
tomatically. tomatically.
01 0107 Error code returned from target: This error does This error does This is not an
Attempted to close a connection, but that not occur. not occur. error because
connection was already closed. the connection
is already
closed.
01 0108 Error code returned from target: This error does Check which Check which
Attempted to open a connection with an not occur. connection connection
unsupported connection type. types can be types can be
used by the used by the
target. originator. (An
(Contact the error will occur
manufacturer.) if a connection
Only multicast other than a
and point-to- multicast or
point connec- point-to-point
tions can be connection is
set. set.)
01 0109 Error code returned from target: Check the connection (sizes) set in the originator
The connection size settings are differ- and target.
ent in the originator and target.
01 0110 Error code returned from target: Check whether Depends on Check whether
The target was unable to open the con- the tag data the target's the tag data
nection, because of its operating status, link is stopped specifications. link is stopped
such as downloading settings. at the target. (Contact the at the target.
(Restart the tag target device's (Restart the tag
data link com- manufacturer.) data link com-
munications munications
with the soft- with the soft-
ware switch.) ware switch.)
01 0111 Error code returned from target: This error does Check the tar- Set the origina-
The RPI was set to a value that exceeds not occur. get's RPI set- tor's RPI set-
the specifications. ting specifica- ting to 10 sec-
tions. onds or less.
15-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0113 Error code generated by originator or re- Check the con- Check the con- Check the con-
turned from target: nection set- nection set- nection settings
Attempted to open more connections tings (number tings (number (number of
than allowed by the specifications. of connections) of connections) connections) at
at the origina- at the origina- the originator
tor and target. tor and target. and target.
Check the con- Check the con-
nection specifi- nection specifi-
cations for de- cations for de-
vices from oth- vices from oth-
er manufactur- er manufactur-
ers. ers.
The NX502 CPU Unit is set to disable Make sure that the NX502 CPU Unit on the CIP
CIP Safety communications. Safety communications path is set to enable CIP
Safety communications.
01 0114 Error code returned from target: This error does Depends on Check the orig-
The Vendor ID and Product Code did not not occur. the target's inator's con-
match when opening connection. specifications. nection set-
(Contact the tings.
target device's
manufacturer.)
Check that the
target device's
EDS file is cor-
rect.
01 0115 Error code returned from target: This error does Depends on Check the orig-
The Product Type did not match when not occur. the target's inator's con-
opening connection. specifications. nection set-
(Contact the tings.
target device's
manufacturer.)
Check that the
target device's
EDS file is cor-
rect.
01 0116 Error code returned from target: Check the ma- Depends on Check the orig-
The Major/Minor Revisions did not jor and minor the target's inator's con-
match when opening connection. revisions set specifications. nection set-
for the target (Contact the tings.
device and target device's
connection. If manufacturer.)
necessary, ob- Check that the
tain the most target device's
recent EDS file EDS file is cor-
and set it rect.
again.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-13
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-2
Connection
Status
Codes
and
Troubleshooting
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0117 Error code returned from target: Check whether Depends on Check the orig-
The tag set specified in the connection's the originator the target's inator's con-
target variables does not exist. and target tag specifications. nection set-
sets and tags (Contact the tings. Check
are set correct- target device's whether the
ly. manufacturer.) target tag sets
and tags are
set correctly.
01 011A Error code generated by originator: Unexpected Unexpected Depends on
Connection could not be established be- network traffic network traffic the target's
cause the buffer was full due to high traf- may have been may have been specifications.
fic. received. received. (Contact the
Use the Ether- Use the Ether- target device's
net Information net Information manufacturer.)
Tab Page of Tab Page of
the Network the Network
Configurator's Configurator's
device monitor device monitor
to check the to check the
bandwidth us- bandwidth us-
age, and cor- age, and cor-
rect the load. rect the load.
If there are pla- If there are pla-
ces where ces where
broadcast broadcast
storms occur, storms occur,
such as loop such as loop
connections in connections in
the network the network
connection for- connection for-
mat, then cor- mat, then cor-
rect them. rect them.
01 011B Error code returned from target: This error does Depends on Set the origina-
The RPI was set to a value that is below not occur. the target's tor's RPI set-
the specifications. specifications. ting to 1 ms or
(Contact the greater.
target device's
manufacturer.)
15-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0127 Error code returned from target: This error does Check the con- This error does
The connection data size settings are not occur. nection (sizes) not occur.
different in the originator and target. set in the origi-
(data from originator to target) nator and tar-
get.
(data from orig-
inator to target)
Depends on
the target's
specifications.
(Contact the
manufacturer.)
Check that the
target device's
EDS file is cor-
rect.
01 0128 The connection data size settings are Check the connection (sizes) set in the originator
different in the originator and target. and target.
(data from target to originator) (data from target to originator)
01 0203 Error code generated by originator: Tag data link communications from the target timed
The connection timed out. out. Check the power supply and cable wiring of
the devices in the communications path, including
the target and switches. If performance has drop-
ped due to heavy traffic, change the performance
settings. For example, increase the timeout time or
RPI setting.
Also, check whether the CIP message communica-
tions of the target are stopped and whether the CIP
communications are permitted by Packet Filter
function of the originator or the device on the route.
01 0204 Error code generated by originator: There was no response from the target. Check the
The connection open process timed out. power supply and cable wiring of the devices in the
communications path, including the target and
switches.
Also, check whether the CIP message communica-
tions of the target or originator are stopped and
whether the CIP communications are permitted by
Packet Filter function of the target device or the de-
vice on the route.
01 0205 Error code returned from target: This error does Depends on Depends on
There was a parameter error in the not occur. the target's the originator's
frame used to open the connection. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-15
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-2
Connection
Status
Codes
and
Troubleshooting
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0301 Error code generated by originator or re- Check the total Check the total Check the total
turned from target: number of the number of the number of the
Total number of tag sets that are set to tag sets that tag sets that tag sets that
the product was exceeded. are set to the are set to the are set to the
product and set product and set product and set
the tag sets so the tag sets so the tag sets so
that the total that the total that the total
number does number does number does
not exceed the not exceed the not exceed the
maximum of maximum of maximum of
the allowable the allowable the allowable
number. number. number.
01 0302 Error code generated by originator or re- Check the con- Check the tar- Check the con-
turned from target: nection set- get's connec- nection settings
The tag data link's allowable bandwidth tings (number tion settings (number of
(pps) was exceeded. of connections (number of connections
and RPI) at the connections and RPI) at the
originator and and RPI). originator and
target. Check the con- target.
nection set-
tings (number
of connections
and RPI) at the
originator and
target.
01 0311 Error code returned from target: This error does Depends on Depends on
There was a parameter error in the not occur. the target's the originator's
frame used to open the connection. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
01 0312 Error code returned from target: This error does Depends on Depends on
There was a parameter error in the not occur. the target's the originator's
frame used to open the connection. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
01 0315 Error code returned from target: This error does Depends on Depends on
There was a parameter error in the not occur. the target's the originator's
frame used to open the connection. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
15-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
01 0316 Error code returned from target: This error does Depends on Depends on
There was a parameter error in the not occur. the target's the originator's
frame used to close the connection. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
01 031C Error code generated by originator: This error does The originator Depends on
Some other error occurred. not occur. generates this the originator's
code when an specifications.
unsupported (Contact the
response code originator devi-
is returned ce's manufac-
from the target turer.)
in reply to an
open request.
08 --- Error code returned from target: This error does Depends on Depends on
There is no Forward Open or Large For- not occur. the target's the originator's
ward Open service in the target device. specifications. specifications.
(Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-17
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-2
Connection
Status
Codes
and
Troubleshooting
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
D0 0001 Error code generated by originator: The connection The meaning Depends on
The connection operation is stopped. was stopped of this error the originator's
because the code is defined specifications.
Tag Data Link by each ven- (Contact the
Stop Bit was dor, so it de- originator devi-
turned ON, or pends on the ce's manufac-
the settings da- target's specifi- turer.)
ta is being cations.
downloaded. (Contact the
Either turn ON target device's
the Tag Data manufacturer.)
Link Start
Switch, or wait
until the set-
tings data has
been down-
loaded.
This code in-
cludes fatal
Controller er-
rors and Unit
failure. To han-
dle these er-
rors, refer to
the NJ/NX-
series
Troubleshootin
g Manual (Cat.
No. W503).
D0 0002 Error code generated by originator: Wait until the The meaning Depends on
The connection is being opened (open- opening proc- of this error the originator's
ing processing in progress). essing is com- code is defined specifications.
pleted. by each ven- (Contact the
dor, so it de- originator devi-
pends on the ce's manufac-
target's specifi- turer.)
cations.
(Contact the
target device's
manufacturer.)
15-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15 Troubleshooting
Connection status Handling
General Additional
Source of error Configuration Configuration Configuration
Status Status
1 2 3
(hex) (hex)
OMRON error code
01 0810 Error code returned from target: It occurs when The meaning The meaning of
The latest data cannot be retrieved from the CPU Unit of this error this error code
the CPU Unit after a connection was task period is code is defined is defined by
opened. (Automatic recovery by connec- too long after a by each ven- each vendor,
tion open retry) connection was dor, so it de- so it depends
opened or pends on the on the origina-
when the Con- target's specifi- tor's specifica-
troller system cations. tions.
stopped due to (Contact the (Contact the
an error on the target device's originator devi-
Controller. manufacturer.) ce's manufac-
If it occurred turer.)
due to a long
task period, the
error will be re-
covered auto-
matically. If it
was caused by
stoppage of the
Controller sys-
tem, the cause
of the error will
be identified
from the error
information of
the CPU Unit.
01 0811 Error code generated by originator: It occurs when The meaning The meaning of
The latest data cannot be retrieved from the CPU Unit of this error this error code
the CPU Unit after a connection was task period is code is defined is defined by
opened. (Automatic recovery by connec- too long after a by each ven- each vendor,
tion open retry) connection was dor, so it de- so it depends
opened. pends on the on the origina-
The error will target's specifi- tor's specifica-
be recovered cations. tions.
automatically. (Contact the (Contact the
target device's originator devi-
manufacturer.) ce's manufac-
turer.)
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-19
15-2
Checking
Status
with
the
Network
Configurator
15
15-2-2
Connection
Status
Codes
and
Troubleshooting
15 Troubleshooting
15-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
A
Appendices
A-1 Functional Comparison of EtherNet/IP Ports on NJ/NX-series
CPU Units and Other Series..........................................................................A-3
A-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP
Connections)..................................................................................................A-5
A-2-1 Overview of the Tag Data Links (EtherNet/IP Connections) Settings
with the Sysmac Studio...................................................................................A-5
A-2-2 Procedure to Make the EtherNet/IP Connection Settings with the
Sysmac Studio................................................................................................A-6
A-2-3 EtherNet/IP Connection Settings.....................................................................A-7
A-2-4 Making the EtherNet/IP Connection Settings with the Sysmac Studio..........A-11
A-2-5 Checking Communications Status with the Sysmac Studio and Trou-
bleshooting....................................................................................................A-32
A-2-6 Troubleshooting.............................................................................................A-36
A-3 EDS File Management.................................................................................A-42
A-3-1 Installing EDS Files.......................................................................................A-42
A-3-2 Creating EDS Files........................................................................................A-43
A-3-3 Deleting EDS Files........................................................................................A-43
A-3-4 Saving EDS Files..........................................................................................A-44
A-3-5 Searching EDS Files.....................................................................................A-44
A-3-6 Displaying EDS File Properties.....................................................................A-45
A-3-7 Creating EDS Index Files..............................................................................A-45
A-4 Precautions for Using the Network Configurator on Windows XP,
Windows Vista, or Windows 7 or Higher....................................................A-46
A-4-1 Changing Windows Firewall Settings............................................................A-46
A-5 Variable Memory Allocation Methods.......................................................A-49
A-5-1 Variable Memory Allocation Rules.................................................................A-49
A-5-2 Important Case Examples.............................................................................A-58
A-6 Precautions When Accessing External Outputs in CPU Units...............A-62
A-7 TCP State Transitions.................................................................................A-63
A-8 Example of NX Unit Setting Using NX Configuration Object Service....A-65
A-8-1 Changing the Unit Operation Settings for Singe NX Unit..............................A-65
A-8-2 Changing the Unit Operation Settings for Multiple NX Units.........................A-66
A-8-3 Initializing the Unit Operation Settings for Singe NX Unit..............................A-66
A-9 Tag Data Link Settings with Generic Devices...........................................A-67
A-9-1 Creating Generic Devices.............................................................................A-67
A-9-2 Creating a Tag or Tag Set for Generic Device...............................................A-68
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-1
A
Appendices
A-10 Procedure to Use Secure Socket Service with Secure Socket
Configuration Commands...........................................................................A-72
A-10-1 Settings for Starting Secure Socket Services................................................A-72
A-10-2 Procedure for Replacing the CPU Unit..........................................................A-74
A-11 Secure Socket Configuration Commands................................................A-79
A-11-1 Operating Environment for Secure Socket Configuration Commands..........A-79
A-11-2 Location and Starting Procedure of Secure Socket Configuration
Commands....................................................................................................A-80
A-11-3 Command and Option Formats.....................................................................A-80
A-11-4 Common Specifications to All Commands....................................................A-81
A-11-5 Command Specifications...............................................................................A-83
A-12 TCP/ UDP Port Numbers Used for the Built-in EtherNet/IP Port.............A-95
A-13 Version Information..................................................................................A-100
A-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
A-1 Functional Comparison of EtherNet/IP
Ports on NJ/NX-series CPU Units and
Other Series
¡: Supported, ---: Not supported
Built-in Built-in Built-in Built-in Built-in
EtherNet/IP EtherNet/IP EtherNet/IP EtherNet/IP EtherNet/IP NX-series
Item port on port on port on port on port on NJ- EtherNet/IP
NX701 CPU NX502 CPU NX102 CPU NX1P2 CPU series CPU Unit
Unit Unit Unit Unit Unit
Tag data link communica- OK OK OK OK OK OK
tions service
CIP message communica- OK OK OK OK OK OK
tions service
IP routing OK OK OK --- --- OK
Socket services OK OK OK OK OK ---
FTP server OK OK OK OK OK ---
FTP client OK OK OK OK OK ---
Mail send/receive --- --- --- --- --- ---
Web functions --- --- --- --- --- ---
Automatic adjustment of OK OK OK OK OK ---
PLC/Controller’s internal
clock
Error history OK*1 OK*1 OK*1 OK*1 OK*1 OK*1
Response to PING com- OK OK OK OK OK OK
mand
SNMP/SNMP trap OK OK OK OK OK OK
CIDR function for IP ad- OK OK OK OK OK OK
dresses
DHCP client --- OK --- --- --- ---
LLDP --- OK ¡*2 --- --- OK
Online connection via Ether- --- --- --- --- --- ---
Net/IP using CX-One
Online connection via Ether- OK OK OK OK OK OK
Net/IP using Network Con-
figurator
Mounting in an NJ-series --- --- --- --- --- ---
CPU Unit
Connection settings using OK OK OK OK OK OK
the Sysmac Studio
*1. This is equivalent to the event log in the EtherNet/IP of an NJ-series Controller.
*2. A CPU Unit with unit version 1.64 or later is required to use LLDP.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-3
A-1
Functional
Comparison
of
EtherNet/IP
Ports
on
NJ/NX-series
CPU
Units
and
Other
Series
A
Appendices
OK: Supported, ---: Not supported
CJ2H-CPU6£-EIP CS1W-EIP21 CS1W-
CJ-series
CJ2M-CPU3£ CJ1W-EIP21 EIP21S
Item Ethernet
Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- CJ1W-
Unit
sion 1.0 sion 2.0 sion 2.1 sion 1.0 sion 2.0 sion 2.1 EIP21S
Tag data link commu- --- OK OK OK OK OK OK OK
nications service
CIP message commu- --- OK OK OK OK OK OK OK
nications service
IP routing --- --- --- --- --- --- --- ---
Socket services OK --- --- --- --- --- --- OK
FTP server OK --- OK OK --- OK OK OK
FTP client --- --- --- --- --- --- --- ---
Mail send/receive OK --- --- --- --- --- --- ---
Web functions OK --- --- --- --- --- --- ---
Automatic adjustment OK --- OK OK --- OK OK OK
of PLC/Controller’s in-
ternal clock
Error history OK OK OK OK OK OK OK OK
Response to PING OK OK OK OK OK OK OK OK
command
SNMP/SNMP trap --- --- OK OK --- OK OK OK
CIDR function for IP --- --- OK OK --- OK OK OK
addresses
DHCP client --- --- --- --- --- --- --- ---
LLDP --- --- --- --- --- --- --- ---
Online connection via OK --- OK OK --- OK OK OK
EtherNet/IP using CX-
One
Online connection via --- OK OK OK OK OK OK OK
EtherNet/IP using Net-
work Configurator
Mounting in an NJ- --- --- --- --- --- --- OK*1*2 OK*1*3
series CPU Unit
Connection settings --- --- --- OK --- --- OK OK
using the Sysmac Stu-
dio
*1. You cannot use the following functions if you connect to the CPU Unit through an EtherNet/IP Unit.
• Placing the Sysmac Studio online with the CPU Unit (However, you can place the Network Configurator online)
• Using the Troubleshooter of an NS-series PT
*2. The CJ1W-EIP21 can be mounted on the NJ-series CPU Unit in the following combinations.
• CJ1W-EIP21: Unit version 2.1 or later
• NJ-series CPU Unit: Unit version 1.01 or later
• Sysmac Studio: Version 1.02 or higher
The CS1W-EIP21 cannot be mounted to the NJ-series CPU Unit.
*3. The CJ1W-EIP21S can be mounted on the NJ-series CPU Unit in the following combinations.
• CJ1W-EIP21S: Lot number: 241001£ or later
• NJ-series CPU Unit: Unit version 1.67 or later
• Sysmac Studio: Version 1.60 or higher
The CS1W-EIP21S cannot be mounted to the NJ-series CPU Unit.
A-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
A-2 Use the Sysmac Studio to Set the Tag
Data Links (EtherNet/IP Connections)
A-2-1 Overview of the Tag Data Links (EtherNet/IP Connections) Set-
tings with the Sysmac Studio
You can use the Sysmac Studio to set the settings required for creating tag data links (EtherNet/IP
connections)*1 between NJ/NX-series Controllers.
*1. The tag data links and EtherNet/IP connections enable cyclic tag data exchanges on an EtherNet/IP network
between Controllers or between Controllers and other devices. Here, "EtherNet/IP connection" refers to both
the tag data links and the EtherNet/IP connections.
Version Information
Sysmac Studio version 1.10 or higher is required to use the Tag Data Link (EtherNet/IP Con-
nection) Settings.
Acceptable System Configuration Conditions for Setting the Ether-
Net/IP Connection Settings on the Sysmac Studio
If an NJ/NX-series Controller operates as the originator device, you can use the Sysmac Studio to set
the originator device settings for the EtherNet/IP connections.
Similarly, if an NJ/NX-series Controller operates as the target device, you can use the Sysmac Studio
to set the tags and tag sets of the target device.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-5
A-2
Use
the
Sysmac
Studio
to
Set
the
Tag
Data
Links
(EtherNet/IP
Connections)
A
Sysmac
Studio
A-2-1
Overview
of
the
Tag
Data
Links
(EtherNet/IP
Connections)
Settings
with
the
Appendices
Settings for the originator device Settings for the target device
NX-series Controller NX-series Controller
(Two built-in (Two built-in
EtherNet/IP ports) EtherNet/IP ports)
NJ-series Controller NJ-series Controller
Tag and tag set settings
Setting with the Sysmac
Studio is possible.
(A built-in (A built-in EtherNet/IP port on the
EtherNet/IP port on CPU Unit or EtherNet/IP Unit)
the CPU Unit or Tag and tag set settings
CS-/CJ-series PLC
EtherNet/IP Unit)
Setting is possible only with
the Network Configurator.
FH/FZ/FQ/ZW-series Sensor
or another similar Unit Tag and tag set settings
Settings not required.
Tag and tag set settings Connection settings
Setting with the Sysmac Setting with the Sysmac
Studio is possible. Studio is possible.
Use the Network Configurator if a CS/CJ-series PLC operates as the originator device.
Settings for the originator device Settings for the target device
CS-/CJ-series PLC NJ/NX-series Controller
Setting is possible only with
the Network Configurator.
A-2-2 Procedure to Make the EtherNet/IP Connection Settings with the
Sysmac Studio
1 Registering devices • Main Window
↓ Register devices with which the EtherNet/IP connections
are established to the project.
Setup Window
2 Creating network variables*1 --- Refer to Registering the Net- Global Variable Table on the
work Variable for the Origina- Sysmac Studio
tor Device on page A-12.
↓
3 Registering tags and tag sets --- Refer to Registering the Tag EtherNet/IP Connection Set-
and Tag Set on page A-13. tings (Tag Set Display)
A-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
↓ Register the network variables that are set in step 2 as
tags and tag sets.
4 Setting connections --- Refer to Setting Connections EtherNet/IP Connection Set-
for the Originator Device on tings (Connection Display)
page A-16.
↓ Specify devices (i.e., target devices and originator devi-
ces) and tag sets to communicate with using the Ether-
Net/IP connections.
5 Going online from the Sysmac Studio --- Refer to Transferring the • Main Window
Connection Settings Data on
page A-28.
↓
6 Downloading EtherNet/IP connection --- Refer to Transferring the • Synchronization Window/
settings Connection Settings Data on Transfer to Controller Dia-
Note Connections automatically start after page A-28. log Box
the download. • EtherNet/IP Connection
Settings
↓
7 Checking operation --- Refer to A-2-5 Checking EtherNet/IP Connection Moni-
Stopping and starting connections Communications Status with tor Tab Page
the Sysmac Studio and Trou-
bleshooting on page A-32.
*1. Variables with its Network Publish attribute set to Output or Input in the Global Variable Table are called
network variables.
A-2-3 EtherNet/IP Connection Settings
This section describes the screen configuration for EtherNet/IP connection settings.
Screen Transitions in the EtherNet/IP Connection Settings
• Connection Settings
Select EtherNet/IP Connection Settings from the Tools Menu.
EtherNet/IP Device List Tab Page
Double-click or right-click the
device to set and select Edit EtherNet/IP Connection Settings (Tag Set Display)
from the menu.
Use the tab icons to switch
between displays.
EtherNet/IP Connection Settings
(Connection Display)
Right-click the device to set
and select Monitor from the EtherNet/IP Connection Monitor Tab Page
menu.
• Transferring connection settings to the Controller from the computer
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-7
A-2
Use
the
Sysmac
Studio
to
Set
the
Tag
Data
Links
(EtherNet/IP
Connections)
A
A-2-3
EtherNet/IP
Connection
Settings
Appendices
Select EtherNet/IP Connection
Settings from the Tools Menu to
display the device list.
Select Synchronization Select Transfer - To Controller Right-click the device and select
from the Controller Menu. from the Controller Menu. Edit from the menu.
Transfer to Controller Dialog EtherNet/IP Connection
Synchronization Window
Box Settings Tab Page
Precautions for Correct Use
To transfer only the connection settings, execute Transfer from the EtherNet/IP Connection Set-
ting Tab Page.
Even if you clear the Do not transfer the connection setting Check Box, the connection set-
tings are not transferred from the Synchronization Window, the Transfer to the Controller Dia-
log Box, or the Transfer from the Controller Dialog Box as long as the data in the computer is
synchronized with the data in the Controller.
EtherNet/IP Device List Tab Page
The list indicates the devices to which EtherNet/IP connections can be set.
For information on how to access this tab page, refer to Registering the Tag and Tag Set on page
A-13.
EtherNet/IP Connection Settings (Tag Set Display)
Register tag sets required to create connections.
Each tag set represents the data that is sent and received through a connection. You can register up
to eight tags in one tag set.
A-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
The name and size of the tag must be the same as those of the network variable *1. Set whether to
include the Controller status information in tags for the tag sets. You can also set the data output oper-
ation at a fatal error occurrence for output tags.
Refer to Registering the Tag and Tag Set on page A-13 for information on how to register tags and
tag sets.
*1. A variable with its Network Publish attribute set to Output or Input in the Global Variable Table is called a
network variable.
EtherNet/IP Connection Settings (Connection Display)
Specify the target devices and set their connections.
For each connection, set the following information: Connection Name, Connection I/O Type, I/O, target
device tag set (target variable), originator device tag set (originator variable), Packet Interval (RPI),
and Timeout Value.
Refer to Setting Connections for the Originator Device on page A-16 for information on how to make
connection settings.
Precautions for Correct Use
If you changed the IP address, model, or revision of the target device after making the connec-
tion settings, perform the following.
With the Sysmac Studio version 1.11 or higher, change the connection settings entirely.
With the Sysmac Studio version 1.10 or lower, create the connections again.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-9
A-2
Use
the
Sysmac
Studio
to
Set
the
Tag
Data
Links
(EtherNet/IP
Connections)
A
A-2-3
EtherNet/IP
Connection
Settings
Appendices
EtherNet/IP Connection Monitor Tab Page
You can check the EtherNet/IP connection setting status offline and communications status online.
When online, you can start and stop connections.
Refer to A-2-5 Checking Communications Status with the Sysmac Studio and Troubleshooting on
page A-32 for information on how to check the EtherNet/IP connection setting status and communi-
cations status.
A-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
A-2-4 Making the EtherNet/IP Connection Settings with the Sysmac
Studio
This section describes the procedure to make the EtherNet/IP connection settings with the Sysmac
Studio.
Here, we take the following system configuration as an example to describe how to set the
EtherNet/IP connection settings.
Example: System that connects the built-in EtherNet/IP port on Controller 1 and the built-in
EtherNet/IP port on Controller 2 via Ethernet
• Set the settings so that values in the network variable Net_Out1 allocated for Controller 2 are sent to
the network variable Net_In1 allocated for Controller 1 at the set RPI of 50 ms cycle.
• This example assumes the programs for both Controllers 1 and 2 are registered in the same project.
Sysmac Studio
Project on the Sysmac Studio
Controllers 1 and 2 are respectively named as follows and registered in the same project.
· Controller_1 (Controller 1: NJ501-1500 (Built-in EtherNet/IP Port))
· Controller_2 (Controller 2: NJ501-1500)
Ethernet
Originator device Target device
Controller 1 Controller 2 CJ1W-EIP21
(NJ501-1500: (NJ501-1500) (NJ)
Built-in EtherNet/IP
port)
Originator device tag set Target device tag set
Net_In1 (Tag set) Net_Out1 (Tag set)
(Tag) (Tag)
Net_In1 Net_Out1
Convert the network variable to the tag.
Network variable Network variable
(Network Publish attribute: Input) (Network Publish attribute: Output)
Net_In1 Net_Out1
(Data type: WORD) (Data type: WORD)
Follow the flow below to set the settings to Controllers 1 and 2 for which to establish EtherNet/IP con-
nections.
The required settings for the originator device and the target device are shown below.
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-11
A-2
Use
the
Sysmac
Studio
to
Set
the
Tag
Data
Links
(EtherNet/IP
Connections)
A
A-2-4
Making
the
EtherNet/IP
Connection
Settings
with
the
Sysmac
Studio
Appendices
Settings for the originator device (Controller 1) Settings for the target device (Controller 2)
Registering the network variable Registering the network variable
Registering the tag and tag set Registering the tag and tag set
Setting connections
Transferring settings for the connection, Transferring settings for the tag and
the tag, and the tag set the tag set
Registering the Network Variable for the Originator Device
Register the network variable that is sent and received using the EtherNet/IP connections.
Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for the operations for regis-
tering variables.
1
Assign the network variable to the tag used for the EtherNet/IP connection for Controller 1
(originator device).
This network variable receives data from Controller 2 (target device).
Select Input or Output for Network Publish of a variable in the Global Variable Table so that
the variable can serve as a network variable, i.e. the variable can be used for the EtherNet/IP
connections.
In this example, set the network variable for Controller 1 as shown below.
• Variable name: Net_In1
• Data type: WORD
• Network Publish attribute: Input
 Network Variables Used for EtherNet/IP Connections
• Network variable name
A-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
Appendices
You cannot specify an I/O memory address for a tag name in the EtherNet/IP connection set-
tings. Thus, do not specify an I/O memory address for the network variable name that is to be
assigned to a tag.
The following text strings are recognized as the I/O memory address names.