Leuze electronic MSI 400 Series Manual page 92

Fig. 8.26: Example of the display of assembly instance 57 in the Logix Designer
8.5.3.2 Assembly Instances 167 = 0xa7
Assembly instance 167 possesses a different data structure to instance 57. Instance 167 makes the data
available in the MSI 400 system in more detail.
Assembly instance 167 in the MSI 400 system comprises data (T→O) with a scope of up to 112 bytes.
8.5.3.2.1 Byte 0 to 49
Assembly instance 167 corresponds to output data block 1 to 5 of the logic data of the MSI 430 module
with a total scope of 50 bytes.
Here, attributes 1 to 50 are represented as with instance 57.
8.5.3.2.2 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 attrib-
ute 1 is non-zero.
Bits 0 to 4 of byte 50 of assembly instance 167 byte are reserved for future use.
8.5.3.2.3 Byte 51
Byte 51 of assembly instance 167 supplies the system mode of the controller modules. It shows the same
value as attribute 1 of instance 5 in class 120.
8.5.3.2.4 Byte 52 to 111
Bytes 52 to 111 of assembly instance 167 make the corresponding state bytes of the controller mode avail-
able. They show the same value as attributes 1 to 60 of instance 3 in class 120.
Leuze electronic MSI 400
EtherNet/IP gateway
92