Implemented CANopen objects
Reference between CANopen object and Lenze code
13
l
91
EDSMF2178IB EN 3.0
13
Implemented CANopen objects
Lenze controllers can be parameterised with Lenze codes and manufacturer−independent
"CANopen objects". A completely CANopen−conform communication can only be achieved
by using CANopen objects for parameter setting.
All CANopen objects described in these instructions are defined according to the "CiA Draft
Standard 301/version 4.02".
)
Note!
Some of the terms used here derive from the CANopen protocol.
13.1
Reference between CANopen object and Lenze code
CANopen objects and Lenze codes do not have the same functionalities.
Some CANopen objects have a direct influence on the corresponding codes:
ƒ
If a new value is written within an object, the value is also adopted in the
corresponding code C18xx or C23xx.
ƒ
When reading an object, the values stored under the corresponding code are
displayed.
Example
The CANopen object I−1017 (producer heartbeat time) is mapped on the codes C1870/2
and C2370/2:
ƒ
Reading the object I−1017:
– Response: Value under code C1870/C2370, subcode 2.
ƒ
Writing a new value into the object I−1017:
– The new producer heartbeat time is also entered under C1870/2 and C2370/2.
