
Lenze · Servo-Inverter 9400 HighLine · Reference manual · DMS 10.0 EN · 11/2013 · TD05/06 339
9 "CAN on board" system bus
9.10 Implemented CANopen objects
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.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 on Lenze codes. The following table lists the related Lenze
codes 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 Designation
I-1000
0 Device type -
I-1001
0 Error register C00390
I-1003 Predefined error field
0 Number of errors -
1 ... 10 Standard error field -
I-1005
0 COB-ID SYNC message C00367
C00368
I-1006 0 Communication cycle period C00369
I-100C 0Guard time C00382
I-100D 0Life time factor C00383
I-1010 Store parameters
0 Highest subindex supported -
1 Save all parameters -
I-1011
Restore default parameters
0 Highest subindex supported -
1 restore all default parameters -
I-1014
0COB-ID EMCY C00391
I-1015 0 Inhibit time EMCY C00392
I-1016 Consumer heartbeat time
0 Highest subindex supported -
1 ... 32 Consumer heartbeat time C00385/1...32
I-1017 0 Producer heartbeat time C00381
I-1018 Identity object
0 Highest subindex supported -
1Vendor ID -
2 Product code -
3 Revision number -
4 Serial number -
Comentarios a estos manuales