Lenze EMF2180IB

Lenze · EMF2180IB communication module (EthernetCAN) · Communication Manual · DMS 5.1 EN · 09/2016 · TD17 65
10 CANopen objects implemented
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
10 CANopen objects implemented
Lenze devices can be parameterised with both Lenze codes and manufacturer-independent
"CANopen objects". Fully CANopen-compliant
communication can only be achieved by exclusively
using CANopen objects for the parameterisation. The CANopen objects described in this chapter are
defined in the DS301 V4.02 CAN specification.
This chapter lists the implemented CANopen objects of the communication module in numerically
ascending order.
I-1000 - Device type
The I-1000 CANopen index shows the profile for this device. Furthermore, additional information
defined in the device profile itself can be shown here.
If you are not working according to a specific device profile, the content is "0x0000".
Data frame assignment
I-1001 - Error register
The error register displays the error status in data bytes (U8) in a bit-coded form:
 Note!
Some of the terms used here derive from the CANopen protocol.
Index
I-1000
Name:
Device type
Subindex Lenze
setting
Display range
(min. value | unit | max. value)
Access Data type
0: Device type 0 0 4294967295 ro U32
Byte 8 Byte 7 Byte 6 Byte 5
U32
Device profile number Additional information
Index:
I-1001
Name:
Error register
Subindex Lenze
setting
Display range
(min. value | unit | max. value)
Access Data type
0: Error register - 0 255 ro U8
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Error status
00000000No error
00000001 Error of the communication module
0001 0001 Communication error