FEC920: USER GUIDE
Page 41
A
September 18
Figure 32 Explicit messaging example
USING TAGS
When acting as servers, many PLCs present their data in a tag format instead of implicit data format. For this
reason, when the client is configured as ‘Client (Tags)’, (see Section 6.7) 30 input and 30 output tags become
available to the user via iTools (Figure 33).
Virtual Channel.1.Main.Input1
Virtual Channel.2.Main.Input1
EtherNet/IP Client
Loop.1.Setpoint.SP1
Loop.1.Setpoint.SP2
Loop.2.Setpoint.SP1
Loop.1.Setpoint.SP2
11.1
-19.1
1
23.0
132.0
246.2
111.11
9
123.123.123.223 : Point2Point : 1000ms
Implicit I/O
EtherNet/IP Client
123.123.123.222
Client (IO)
Explicit 1
No Connection
Explicit 2
No Connection
Explicit Messaging
Destination Address
Service Code
Class Id
Instance Id
Attribute Id
Data Type
Data
Send
123.123.123.223
Get Attribute
162
4150
1
INT
3
No
Input Tags
Connection Failed
Output Tags
Connection Failed
123.123.123.223 : 1000ms
Tag I/O
EtherNet/IP Client
123.123.123.222
Client (Tags)
Tags page appears if ‘Mode’ is set to ‘Client
(Tags)’ in EtherNet/IP configuration (Section
6.7).
Explicit messaging is not possible in tag IO
mode as tag mode needs to consume both
connections for communications with the PLC.
When wired to parameters which have
descriptors, the descriptor names appear
instead of the ‘opc’ names (e.g.
Loop.1.Setpoint.SP1) shown here.
A5E45696052A Rev-AA
