
Lenze · 8400 HighLine · Reference manual · DMS 12.0 EN · 06/2017 · TD23
753
11
System bus "CAN on board"
11.11
CANopen objects implemented
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
11.11
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.
Many CANopen objects can be mapped on Lenze codes. In the following table, the corresponding
Lenze codes are listed in the column "Relationship to Lenze codes".
Overview of CANopen indices 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
-
Predefined error field
0
Number of errors
-
1 ... 10
Standard error field
-
0
COB-ID SYNC message
0
Communication cycle period
0
COB-ID EMCY
-
Consumer heartbeat time
0
Highest subindex supported
-
1 ... n
Consumer heartbeat time
• "BaseLine C" version: n = 1
• "StateLine C" version: n = 7
• "HighLine C" version: n = 15
• "TopLine C" version: n = 15
0
Producer heartbeat time
Identity object
0
Highest subindex supported
-
1
Vendor ID
-
2
Product code
-
3
Revision number
-
4
Serial number
-
SDO1 server parameter
0
Highest subindex supported
-
1
COB-ID client
−>
server (rx)
-
2
COB-ID server
−>
client (tx)
-
SDO2 server parameter
0
Highest subindex supported
-
1
COB-ID client
−>
server (rx)
-
2
COB-ID server
−>
client (tx)
-