10 implemented canopen objects, Implemented canopen objects – Lenze E94ARNE Regenerative power supply User Manual

Page 145

Advertising
background image

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

I-1000

0

Device type

-

I-1001

0

Error register

C00390

I-1003

Pre-defined 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

0

Guard time

C00382

I-100D

0

Life 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

0

COB-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

-

1

Vendor-ID

-

2

Product code

-

3

Revision number

-

4

Serial number

-

Advertising