Multi-Master Operation - Leroy-Somer digitax st User Manual

An EVENT task is triggered when the trigger parameter is actually written to and the
value written (1 to 4) determines which task is actually triggered. The task trigger
parameter can be written to using cyclic or non-cyclic data.
Table 12.23 EVENT task trigger parameters
Trigger
parameter
Pr 61.40*
Pr 61.41
Pr 61.42
Pr 61.43
* The specified EVENT task will be triggered in the SM-Applications module fitted in the
lowest slot number on the drive.
When an EVENT task runs in the SM-Applications module the reason code parameter
(Pr 90.12 to Pr 90.15 for EVENT to EVENT3 respectively) will indicate why the event
task was triggered. The reason codes are given in Table 12.24. More information can be
found in the SM-Applications module user guide.
Table 12.24 EVENT task reason codes
Solution Module
SM-DeviceNet
SM-PROFIBUS DP-V1
SM-CANopen
SM-INTERBUS
SM-CAN
If cyclic data is used to trigger an EVENT task in an SM-Applications module it is best to
NOTE
map the last OUT cyclic data word to the EVENT task trigger parameter; as cyclic data
is written to destination parameters in the order in which it is received, this guarantees
that all received cyclic data will have been written to the target parameters BEFORE the
EVENT task runs in the SM-Applications module.
This feature can only be used on drives with multiple option slots and that support the
NOTE
SM-Applications module.
12.15

Multi-master operation

The SM-PROFIBUS DP-V1 can be used on PROFIBUS-DP networks containing one or
more master controllers. Consult your master controller documentation for information
on how to configure a multi-master PROFIBUS-DP network.
Users must ensure that in networks with multiple master devices that only one master
NOTE
controller is configured to access the SM-PROFIBUS DP-V1.
SM-Profibus DP-V1 supports the simultaneous connection of one class 1 master and
NOTE
one class 2 master.
84
Value written to trigger parameter
0 1
No action EVENT*
EVENT task
No action
in slot 1
EVENT task
No action
in slot 2
EVENT task
No action
in slot 3
Reason code
1
2
3
4
5
www.leroy-somer.com
2 3
EVENT1* EVENT2*
EVENT1 task EVENT2 task
in slot 1 in slot 1
EVENT1 task EVENT2 task
in slot 2 in slot 2
EVENT1 task EVENT2 task
in slot 3 in slot 3
SM-PROFIBUS-DP User Guide
4
EVENT3*
EVENT3 task
in slot 1
EVENT3 task
in slot 2
EVENT3 task
in slot 3
Issue : a