EtherNet/IP gateway
Wieland Electric GmbH | BA000970 | 07/2019 [9855]
103
NOTICE
The functions of the UCMM Message Client (unconnected), which can also be configured in samos-
PLAN
6, are not available in the module version D-01.01.
Adjust Performance
80697611
A configuration of the number of process data bytes exactly matching the application helps to re-
duce the volume of periodically exchanged data bytes.
The PLC specifies the number of output bytes in the form of specific Forward_Open Service data as
Connection Size
for O
→
T. The PLC should set the
Fixed/Variable
bit to 1, meaning
variable
.
The PLC also specifies the number of input bytes. The controller module cyclically transfers data in
the scope of the
connection size
for T
→
O through RPI in the value specified in Forward_Service. If
the
fixed/variable
bit is set by the PLC, meaning
variable
, then not all the assembly bytes must be
transmitted.
Connection with more than one PLC
80711307
The EtherNet/IP function of the SP-COP2-ENI module allows access by more than one PLC. Up to five
encapsulation sessions with input and output data can be set up simultaneously.
If only reading of the process data of the SP-COP2-ENI module is required, “Input only” or “Listen
only” connections can also be used. Note that a “Listen only” connection is closed automatically by
the SP-COP2-ENI module when the owner, who has set up the “Exclusive” or “Input Only” connec-
tion, terminates the connection.
If process data from multiple PLCs are to be transmitted to the SP-COP2-ENI module, the other PLCs
can access the assembly instances 138 to 141 for Class 1 connections. Class 3 connections can be set
up in parallel, provided that there is no conflict with regard to the owner. Please see the following
for more information:
List of Assembly data [ch. 8.5.1, p. 97]
Diagnostics and troubleshooting
80725003
Notifications via network
80735243
80745483
Explicit Message Connection
Device Status is available by reading Class 1, instance 1, attribute 5. Vendor specific interface for
alarms and diagnostic for Explicit Message Connections is defined as follows:
Presence of process alarm can be detected by reading class 29, instance 1, attribute 5 and class 30,
instance 1, attribute 5. The module mode (
Run
or another state) has to be checked, because the
alarm bit is set to 0 = OK every time the module is not in
Run
mode.
The module mode can be detected by reading class 120 Instance 5 Attribute 1.
The presence of module diagnostic events can be detected by reading class 120 Instance 6 Attribute
1.
Detailed reasons for process alarms and system diagnostic events can be found out by reading all 60
attributes of Class 120 Instance 3 which contains the dedicated system status bytes.
80754827
Implicit Message Connection
If assembly instance 57 is used, Bit 6 and 7 of Byte 66 signal a process alarm when set.
If assembly instance 167 is used, Bit 6 and 7 of Byte 66 signal a process alarm when set. Bit 5 signals
diagnostic events or process alarms when set.
Event details can be queried by Explicit Message requests as described here:
8.7
8.8
8.9
8.9.1
8.9.1.1
8.9.1.2
