Implemented cip™ objects – Lenze E84DGFCG User Manual
Page 118

Lenze · Decentralised frequency inverter 8400 motec (EtherNet/IP™ option) · EDS84DMOTEIP EN 2.0 - 10/2013
118
Implemented CIP™ objects
General CIP objects
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Data mapping of the output assemblies
Note!
In order to be able to use the torque control for the assembly object instances 22 (0x16),
23 (0x17), 72 (0x48), 73 (0x49), the "DriveMode" attribute has to be written by means of
explicit message transfer.
Data component
[Bits 0 ... 7]
Class
Instance
Number
Attribute
Name
Number
Name
Number
RunFwd [Bit 0]
Control
Supervisor
0x29
1
Run1
3
RunRev [Bit 1]
Control
Supervisor
0x29
1
Run2
4
FaultReset [Bit 2]
Control
Supervisor
0x29
1
FaultRst
12
NetCtrl [Bit 5]
Control
Supervisor
0x29
1
NetCtrl
5
NetRef [Bit 6]
AC Drive
0x2A
1
NetRef
4
Drive Mode [Bits 0 ... 7]
AC Drive
0x2A
1
DriveMode
6
Speed Reference [Bits 0 ... 7]
AC Drive
0x2A
1
SpeedRef
8
Torque Reference [Bits 0 ... 7]
AC Drive
0x2A
1
TorqueRef
12
Custom Output [Bits 0 ... 7]
Note!
In case of the assembly object instances 21 (0x15) and 23 (0x17), NetCtrl (Bit 5) and
NetRef (Bit 6) have to be set in order that the drive can receive start/stop commands and
speed/torque commands via the network.