Synchronisaon of PDOs via sync telegram
During cyclic transmission, one or more PDOs are transmied/received in xed me intervals.
An addional specic telegram, the so-called sync telegram, is used for synchronising cyclic
process da
ta.
•
The sync telegram is the trigg
er point for the transmission of process data from the slaves to
the master and for the acceptance of process data from the master in the slaves.
•
For sync-controlled process data processing, the sync telegram must be generated accord-
ingly.
•
The response to a sync telegram is determined by the transmission type selected.
Generang the sync telegram:
•
0x1005 can be used to acvate the generaon of sync t
elegrams and to write the idener
value.
•
Sync telegrams are created when bit 30 (see below) is set to "1".
•
The interval between sync telegrams is to be set in 0x1006.
Wring ideners:
•
To receive PDOs, the value 0x80 mus
t be entered in the 11-bit idener in the Lenze seng
(and in compliance with the CANopen specicaon). This means that all inverters are set to
the same sync telegram by de
fault.
•
If sync telegrams are only to be received by specic nodes, their ideners can be entered
with a value of up to and including 0x07FF.
•
The idener can only be changed if the inverter does not send any sync telegrams (0x1005,
Bit 30 = "0").
Data telegram assignment
8th byte (data 4) 7th byte (data 3) 6th byte (data 2) 5th byte (data 1)
Bit 31 Bit 30 Bit 29 ... bit 11 Bit 10 ... bit 0
x 0/1 Extended idener* 11-bit idener
* The extended idener is not supported. Bit 11 ... bit 29 must be set t
o "0".
Parameter Name / value range / [default seng] Info
0x1005 COB-ID SYNC
0x00000000 ... [0x00000080] ... 0xFFFFFFFF
Idener for sync telegram.
How to change the idener:
1.
Deacvate S
ync: Set bit 30 to "0".
2.
Chang
e idener.
3.
Acvate Sync: Set bit 30 t
o "1".
0x1006 Communicaon cyclic period
0 ... [0] ... 65535000 us
Cycle me for sync telegrams.
•
A seng of "1000" or int
eger mulples of this sengs are possible.
•
With the seng "0", no sync telegrams are generated.
0x1400:000 RPDO1 communicaon parameter: Highest subindex
•
Read only
0x1400:001
(PAR 540/001)
RPDO1 communicaon parameter: COB-ID
(RPDO1 cong.: COB-ID)
0x00000000 ... [0x00000200] ... 0xFFFFFFFF
RPDO1: idener
How to change the idener:
1.
Set PDO to "invalid": Se
t bit 31 to "1".
2.
Change
idener.
3.
Reset PDO to "valid": Se
t bit 31 to "0".
0x1400:002
(PAR 540/002)
RPDO1 communicaon parameter: Transmission type
(RPDO1 cong.: Transm. type)
0 ... [255] ... 255
RPDO1: transmission type in compliance with DS301 V4.02
0x1400:005
(PAR 540/005)
RPDO1 communicaon parameter: Event mer
(RPDO1 cong.: Event mer)
0 ... [100] ... 65535 ms
RPDO1: me-out for the monitoring of data recepon.
0x1401:001
(PAR 541/001)
RPDO2 communicaon parameter: COB-ID
(RPDO2 cong.: COB-ID)
0x00000000 ... [0x80000300] ... 0xFFFFFFFF
RPDO2: idener
How to change the idener:
1.
Set PDO to "invalid": Se
t bit 31 to "1".
2.
Change
idener.
3.
Reset PDO to "valid": Se
t bit 31 to "0".
0x1401:002
(PAR 541/002)
RPDO2 communicaon parameter
: Transmission type
(RPDO2 cong.: Transm. type)
0 ... [255] ... 255
RPDO2: transmission type in compliance with DS301 V4.02
Conguring the network
CANopen
CANopen process data objects
118