Lenze PLC Designer PLC Designer (R2-x) - Manual (Page 31)

L-force | PLC Designer
Lenze specifications

DMS 3.2 EN 02/2011 TD29 29
2.3 CANopen / PROFIBUS / EtherCAT
The "CANopen control technology", "PROFIBUS control technology", and "EtherCAT
control technology" communication manuals provide some detailed information on
the commissioning and diagnostics of "Logic" and "Motion" field devices.
Note
• Control technology release 2.5 does not support EtherCAT.
• In the Lenze control technology, PROFIBUS can only be used as "Logic bus".
• The mapping required for cross communication has to be created in the »PLC
Designer«. When the PLC is started, the entire configuration/PDO mapping is
written to the Servo Drives 9400. During this process, the entries from the
»Engineer« are overwritten.
2.4 PLC program for the documentation of a cycle time violation
A cycle time violation can be documented in the IPC logbook by a code as described in
the following.
For the determination of the required cycle time of a PLC project, please observe the
procedures described in the "CANopen control technology" and "EtherCAT control
technology" communication manuals (section "Determining the minimum cycle time
of the PLC project").
The library "SysTaskInfo.lib" is used for evaluating the task runtimes. Via the
Taskinfo() function block that is included, the following information can be retrieved:
Max./last jitter:
They are updated during a positive edge at the input bBeginCycle.
Min./max./last task runtime:
They are updated during a negative edge at the input bBeginCycle.
Function:
• Using the "taskinfo" function block from the "SysTaskInfo.lib" library information
can be queried via a task.
• Using the "LLS_AddLog" function a logbook entry can be generated from the PLC in
the logbook of the IPC.
• If the measured jitter is greater than the cycle time, a task cycle has been omitted
and a corresponding logbook entry will be generated in the logbook of the IPC.