OPERATION MANUAL

NE1S Series Features Section 1-1
Transfer CIP Commands
through Message
Communications
Transparent Message
Communications across
Networks
Specify Paths for Network
Routing without Routing
Tables
Transparent Transfer of
TCP/IP or UDP/IP Packets
across
Ethernet/ControlNet
When necessary, any CIP command can be sent to a device connected
through serial communications or an Ethernet, ControlNet, or DeviceNet network.
Any CIP command, such as a data read/write command, can be sent to
the device and the corresponding response can be received just by executing
a CSND instruction in the NE1S-series CPU Unit's program (without using a
connection).
Ethernet
DeviceNet Unit
Serial
communications
ControlNet Unit
CIP message
communications
NE1S-series CPU Unit
CIP command
sent with CSND
ControlNet network
CIP message
communications
Explicit message
communications
DeviceNet
CIP message communications can be sent and received transparently
through the following networks: Ethernet (built-in Ethernet port), ControlNet
(ControlNet Unit), DeviceNet (DeviceNet Unit), serial communications (built-in
USB and RS-232C ports).
Note For DeviceNet, CIP messages can be sent from other networks to DeviceNet,
but not from DeviceNet to other networks. For serial communications, CIP
messages can be sent from a serial connection to Ethernet, ControlNet, or
DeviceNet, but not from these networks to a serial connection.
When a target device in the network is being specified from an online NE Programmer/Configurator
connection or message communications, the path to
the target can be specified (instead of specifying the network address). With
the source routing method, it is not necessary to create routing tables and
transfer those tables to NE1S-series CPU Units in the network before operation.
TCP/IP or UDP/IP packets can be sent and received transparently between
the Ethernet port and ControlNet network (using the ControlNet Unit's IP over
ControlNet service and Ethernet port's IP routing function).
With these functions, communications based on TCP/IP or UDP/IP (such as
FTP) can be executed between the Ethernet network connected to the Ethernet
port and the ControlNet network connected to the ControlNet Unit.
5