Lenze PLC Designer PLC Designer (R3-1) - Manual (Page 909)

L-force | PLC Designer
Device Editors

DMS 4.1 EN 03/2011 TD29 907
Access on EtherCAT Configuration via Application
Implicit Instance of the Master
For each EtherCAT Master implicitly an instance of type "IoDrvEtherCAT" will be
created as soon as a master device has been inserted in the devices tree. The name of
the instance is identical with the device name used in the tree. Information on the
availability of this instance is displayed in the lower part of the I/O Mapping dialog.
The master instance can be used in the application for accessing the EtherCAT bus
during runtime; for example for a restart of the master or for watching the state of
particular slaves. For the latter see: Concatenated List for Checking all Slaves.
The following parameters can be used for this purpose according to syntax
"<instancename>.<parameter>":
Input parameters:
xRestart On a rising edge the complete master will be restarted. All configuration
parameters will be re-loaded.
xStopBus When this parameter is TRUE, the communication is stopped. No further
EtherCAT telegrams will be sent. On most of the devices afterwards a restart is
necessary, because they have gotten into error state.
Output parameter:
xConfigFinished If this parameter is TRUE, the transfer of all configuration parameters has been
finished successfully. The communication is running.
xDistributedClockInSync If distributed clocks are used, the PLC will be synchronized with the first
EtherCAT Slave for which the DC setting is activated. The output gets TRUE as
soon as this synchronization has been finished successfully. This signal for
example can be used to start SoftMotion function blocks not before the PLC is
running in synchronized mode, because otherwise position jumps could occur.
At the start of the PLC the output is FALSE and will change to TRUE after a few
seconds. If the synchronicity gets lost due to any faults, the output will be
reset to FALSE.
xError This output will get TRUE if an error is detected during the start of the
EtherCAT stack or if during operation the communication with the slaves gets
interrupted because no more messages can be received (for example due to a
cable break).
The error cause can be made out with the help of the logging list resp. via the
error string. Thereby "Ethercat_Master.LastMessage.Ethercat_Master" is the
instance of the master.