Connection Setting Parameters
The connection settings in step 4 above have the following setting parameters.
• Setting the Requested Packet Interval (RPI)
The RPI (Requested Packet Interval) is the I/O data refresh cycle on the Ethernet line when tag
data links are established. With EtherNet/IP, data is exchanged on the communications line at
the RPI that is set for each connection, regardless of the number of nodes.
With the built-in EtherNet/IP port, you can set RPI for each connection.
• Setting Multi-cast or Unicast Communications
You can select a multicast connection or unicast (point-to-point) connection as the connection
type in the tag data link connection settings.
With a multicast connection, you can send an output tag set in one packet to multiple nodes and
make allocations to the input tag sets.
A unicast connection separately sends one output tag set to each node, and so it sends the
same number of packets as the number of input tag sets.
Therefore, multicast connections can decrease the communications load if one output tag set is
sent to multiple nodes.
To use a multicast connection and send an output tag set in one packet to multiple nodes, the
following settings for the receiving node must be the same as the settings of the sending node:
the connection type (multicast), the connection I/O type, packet internal (RPI), and timeout value.
Precautions for Correct Use
• The performance of communications devices is limited to some extent by the limitations of
each product's specifications. Consequently, there are limits to the packet interval (RPI) set-
tings.
Refer to
15-2 Adjusting the Communications Load
on page 15-7 and set an appropriate
packet interval (RPI).
• If multicast connections are used, however, use an Ethernet switch that has multicast filtering,
unless packets are received by all nodes in the network.
If an Ethernet switch without multicast filtering is used, multicast packets are broadcast to the
entire network, and so the packets are sent to nodes that do not require them, which will
cause the communications load on those nodes to increase.
• If you use data tag links with multicast traffic at a baud rate over 100 Mbps, use an Ethernet
switch that supports a baud rate of 1000 Mbps.
If there is an Ethernet device on the same network that communicates at 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.
Additional Information
• To calculate the number of connections of each connection type, refer to
• If the maximum number of connections is exceeded, you must review the number of connec-
tions for the built-in EtherNet/IP port, or the number of nodes. When you use an NJ-series
CPU Unit, you can also consider adding EtherNet/IP Units.
7-1-5
Starting and Stopping Tag Data Links
Tag data links are automatically started when the data link parameters are downloaded from the Net-
work Configurator and the power supply to the NJ/NX-series Controller is turned ON.
7 Tag Data Link Functions
7-9
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
7-1 Introduction to T
ag Data Links
7
7-1-5
Starting and Stopping T
ag Data Links
Summary of Contents for Sysmac NX1P2-10 1 Series
Page 8: ...Manual Structure 6 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506...
Page 34: ...Revision History 32 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506...
Page 388: ...9 Socket Service 9 34 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506...
Page 430: ...12 FTP Client 12 14 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506...
Page 569: ...I Index I 1 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506 I...
Page 576: ...Index I 8 NJ NX series CPU Unit Built in EtherNet IP Port User s Manual W506...
Page 577: ......