EtherNet/IP gateway
Wieland Electric GmbH | BA000970 | 07/2019 [9855]
100
stance 141 is 41. Byte of the logic data of module SP-COP2-ENI. In samosPLAN
6, it has the designati-
on
input data block 5
.
Write requests are refused if the assembly is already used by an active I/O connection.
Assembly Instances for Logic Input Bytes
80545803
80555787
Assembly Instance 57 = 0x39
Assembly instance 57 belongs to the device profile
discrete universal I/O device.
It contains output
data (T
→
O) with a scope of up to 67 bytes.
The first 50 bytes of assembly instance 57 correspond to the
output data set 1
of the logic data of
the SP-COP2-ENI module. The following table explains the meaning of bytes 50 to 66.
class 1 connection “Logic output (1 to 400) and logic/physical input” [ch. 8.3.1, p. 78]
Illustration 26: Example of the display of assembly instance 57 in the Logix Designer
80571019
Assembly Instances 167 = 0xa7
Assembly instance 167 possesses a different data structure to instance 57. Instance 167 makes the
data available in the samosPRO system in more detail.
Assembly instance 167 in the samosPRO system comprises data (T
→
O) with a scope of up to 112
bytes.
80584715
Byte 0 to 49
Assembly instance 167 corresponds to
output data block 1 to 5
of the logic data of the SP-COP2-ENI
module with a total scope of 50 bytes.
Here, attributes 1 to 50 are represented as with instance 57.
80595723
Byte 50
Bit 7 of byte 50 of assembly instance 167 has the same value as the class 29 instance 1 attribute 5,
which represents the group status of all physical inputs.
Bit 6 of byte 50 of assembly instance 167 has the same value as the class 30 instance 1 attribute 5,
which represents the group status of all physical outputs.
Bit 5 of byte 50 of assembly instance 167, if set, indicates that an error code in class 120 instance 6
attribute 1 is non-zero.
8.5.3
8.5.3.1
8.5.3.2
8.5.3.2.1
8.5.3.2.2