I/O Module Synchronization; Case 1: The Codesys Task Interval Is Set As Less Than The I/O Module Cycle; Figure 54: I/O Module Synchronization 01 - WAGO -I/O-IPC-C6 Manual

WAGO-I/O-SYSTEM 750
758-874/000-131 WAGO-I/O-IPC-C6
11.9

I/O Module Synchronization

The I/O module cycle and the CoDeSys task cycle are optimally automatically
synchronized: This depends on the number of I/O modules connected and the
fastest CoDeSys task cycle set in the I/O-IPC. The synchronization cases
described below can therefore take place.
In this chapter, CoDeSys task means only tasks within CoDeSys that contain an
access to the I/O module. Tasks that do not access the I/O module are not
synchronized in the same way as the following. Compare the chapter "Creating a
Task Configuration".
11.9.1 Case 1: The CoDeSys task interval is set as less than the
I/O module cycle
The implementation of the CoDeSys task is synchronized with the cycle time of
the I/O module.
The CoDeSys task is processed parallel to the I/O module. The CoDeSys task
interval is lengthened to the I/O module cycle time. This is necessary so that each
CoDeSys task is started with new input data from the I/O module and the output
values are also set at the module after each CoDeSys task.
CTI
CT
KBZ KBZ

Figure 54: I/O module synchronization 01

CTI:
CT:
KBZ:
Example:
CoDeSys Task Interval (CTI): 100 µs
I/O Module Cycle (KBZ): 350 µs
Result: Adaptation of the CoDeSys Task Intervals to the I/O module cycle:
350 µs.
Manual
Version 1.0.0
CT
CoDeSys Task Interval
CoDeSys Task that accesses the I/O module of the internal data bus
I/O Module Cycle
CoDeSys 2.3 Runtime Environment
CTI
KBZ
t
123