EasyManuals Logo

gefran SIEIDrive ADL300 Functions Description And Parameters List

gefran SIEIDrive ADL300
152 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #136 background imageLoading...
Page #136 background image
136 ADL300 • Appendix
“HeartBeat Time” x “LifeTime Factor”.
Monitoring via NodeGuarding excludes monitoring via HeartBeat and vice versa: only one of the two systems can be ac-
tive. The master must set the objects involved correctly.
The drive also checks the master’s operation via the arrival of the Sync message (only if the “Communication Cycle period”
is di󰀨erent from 0). The threshold (maximum time between two Sync messages received from ADL) is:
“Communication Cycle period” * “LifeTime Factor”
If one of the thresholds is exceeded, the drive changes the Operational status to Pre-Operational status, consequently
generating the BusLoss alarm if it is also enabled.
Index Name Default value
1006h Communication Cycle Period 64ms
100Ch Guard Time 100ms
100D Life time factor 3 (N.B.: this must always be different from 0)
1016h Consumer heartbeat time NodeId = 0 , time = 0
1017h Producer heartbeat time 0
The default settings shown therefore correspond to the use of the NodeGuarding protocol with a threshold of 100ms x 3
and a threshold control even on Sync at 64ms x 3. The HeartBeat is disabled.
1.1.4 Communication objects
This chapter describes the communication objects of the CANopen protocol; they are managed by the interface card.
The managed communication objects are:
1) 1 SDO reception Server.
2) 1 SDO transmission Server.
3) reception PDOs.
4) transmission PDOs.
5) 1 Emergency Object.
6) 1 Node Guarding - Life Guarding.
7) 1 SYNC object.
The following table lists the used communication objects with their priority level and the Message Identier; the “Resulting
COB-ID” is obtained by adding the Node-ID (card address) to the number.
OBJECT PRIORITY MESSAGE ID
1st SDO rx 6 1792 700h+NodeId
1st SDO tx 6 1536 600h+NodeId
1st PDO rx 2 1408 580h+NodeId
1st PDO tx 2 512 200h+NodeId
2nd PDO rx 2 384 180h+NodeId
2nd PDO tx 2 768 300h+NodeId
3st PDO rx 2 640 280h+NodeId
3st PDO tx 2 512 400h+NodeId
4th PDO rx 2 384 380h+NodeId
4th PDO tx 2 768 500h+NodeId
EMERGENCY 1 640 480h+NodeId
NODE GUARDING & HB not used 220 600h+NodeId
SYNC 0 128 80h
Table 1.4.1: Communication Objects
The master NodeGuarding message is a remote type (remote RTR bit set in COB-ID). All other messages used by this
implementation of the CANopen are not RTR.
1.1.5 Object Dictionary Elements
The Object Dictionary is accessible from a master CANopen and represents the set of objects used to congure, send and
monitor size.
The following table shows the communication objects used and accessibility with master CANopen
.
Index (hex) Name
1000 Device Type
1001 Error Register
1002 Manufacturer status register

Table of Contents

Other manuals for gefran SIEIDrive ADL300

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the gefran SIEIDrive ADL300 and is the answer not in the manual?

gefran SIEIDrive ADL300 Specifications

General IconGeneral
Brandgefran
ModelSIEIDrive ADL300
CategoryInverter
LanguageEnglish

Related product manuals