10 implemented canopen objects, Implemented canopen objects – Lenze E94ARNE Regenerative power supply User Manual
Page 145
EDS94ARNExxxx EN 2.3 - 06/2014
L
145
9400 regenerative power supply module | Parameter setting
"CAN on board" system bus
Implemented CANopen objects
6.10
Implemented CANopen objects
Lenze devices can both be parameterised with Lenze codes and manufacturer-
independent "CANopen objects". A completely CANopen-compliant communication can
only be achieved by using CANopen objects for parameter setting. The CANopen objects
described in this chapter are defined in the CAN specification DS301 V4.02.
Many CANopen objects can be mapped to Lenze codes. The below table lists the related
Lenze codes in the "Relationship to Lenze code" column.
Overview of 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
-