Sync Task

The PROFINET controller protocol must always be linked with a task. The set cycle time is also used for processing the protocol. In theory, the controller can also be processed via a PLC or NC task. However, if a PLC project, for example, is stopped (e.g. by restart or debugging), this results in the PROFINET part also being stopped. In order to avoid such a side effect is it advisable to always create a free-running SyncTask.

Sync Task 1:


No.

Description

1

This option is enabled by default. In this case the Sync task is triggered via the variable mapping. If several tasks are linked to the PROFINET adapter, the task with the higher priority is always used as the Sync task.

Pay attention to the Sync task. The Sync task must correspond to the value x2, i.e. 1 ms, 2 ms, 4 ms, 8 ms, 16 ms etc. The Sync task of the PROFINET controller must not be set under the Sync task of a PROFINET device.

Example: If the PROFINET device operates with a 4 ms Sync task, the Sync task of the PROFINET controller may be set to 4 ms, 8 ms, 16 ms, etc. In this case cycle times of 1 ms or 2 ms may not be used.

2

If the Sync task is set via the mapping, note that a breakpoint results in interruption of the task, which also affects the PROFINET communication.

You can override this behavior by using the Special Sync Task option. The PROFINET device then uses a Sync task that runs independent of the PLC task.

3

At this point the name, cycle time and priority for the cycle time can be set.