Lenze E94AYCEO - Manual (Page 124)

Lenze · E94AYCEO communication module (EtherNet/IP™) · Communication Manual · DMS 3.0 EN · 12/2013 · TD17
124
14 Implemented CIP™ objects
14.1 General CIP objects
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
14.1.3 Assembly Object (4 / 0x04)
For the data exchange, the communication module supports the assembly object instances 110
(0x6E, Custom Output) and 111 (0x6F, Custom Input).
The contents of the input and output data depends on the I/O data arrangement in the drive (
I/O
configuration in the »Engineer« ( 55) ).
Class attributes
Instance attributes for output data of the scanner
Assembly output objects (scanner to adapter) are assumed to have a 4-byte header (32-bit "Run/Idle
header"). When mapping the assemblies, this header will automatically be added to the data
stream by most Allen-Bradley PLC/SLC equipment.
If your PLC does not support this header (like the Rockwell PLCs do), add a preceding 32-bit header
to the output image.
You can then define the bit 0 of this header in the process image of your PLC:
• State ’0’: idle mode
• State ’1’: run mode
For the operation with Rockwell PLCs, adaptations are not required.
The
Lenze Class (104 / 0x68) ( 142) provides the image of the scanner output data.
Attribute
ID
Service Name Data type Value
1 Get Revision UINT 2 (0x02)
2 Get Max. Instance UINT 111 (0x6F)
Attribute
ID
Service Name Data type Value
3 Get / Set Data Array of BYTE Max. 64 bytes from the scanner
4 Get Size UINT Number of bytes in attribute 3 (Data)