
EDS94AYCCA EN 5.0 - 06/2012
L
153
E94AYCCA communication manual (CANopen®)
Implemented CANopen objects
14
Implemented CANopen objects
Lenze devices can be parameterised with Lenze codes and with manufacturer-independent
"CANopen objects". For a completely CANopen-conform communication only the CANopen
objects may be used for parameter setting. The CANopen objects described in this chapter
are defined in the CANopen specification DS301, V4.02.
Many CANopen objects can be mapped to Lenze codes. In the following table, the related
Lenze codes are listed in the column "Relationship to Lenze code".
Overview of the CANopen indexes and their relationship to Lenze codes
Note!
Some of the terms used here derive from the CANopen protocol.
CANopen object
Relationship to Lenze
code
Index
Subindex
Name
0
Device type
-
0
Error register
Pre-defined error field
0
Number of errors
-
1 ... 10
Standard error field
-
0
COB-ID SYNC message
0
Communication cycle period
0
Guard time
0
Life time factor
Store parameters
0
Highest subindex supported
-
1
Save all parameters
-
Restore default parameters
0
Highest subindex supported
-
1
restore all default parameters
-
0
COB-ID EMCY
0
Inhibit time EMCY
Consumer heartbeat time
0
Highest subindex supported
-
1 ... 32
Consumer heartbeat time
0
Producer heartbeat time
Identity object
0
Highest subindex supported
-
1
Vendor ID
-
2
Product code
-
3
Revision number
-
4
Serial number
-