W&T connects
Interfaces for TCP/IP, Ethernet, RS-232, RS-485, USB, 20mA, glass and plastic fiber optic cable, http, SNMP, OPC, Modbus TCP, I/O digital, I/O analog, ISA, PCI

Cycle time and event-controlled automation environments

IEC 61131 and IEC 61499 compared

Automation environments with distributed controllers represent the basis for IoT, Smart Grids and Industry 4.0.

The traditional automation model according to IEC 61131, as used for example in PLC programming, is typified by cycle-based processing. The function blocks combined into the overall logic are processed at a fixed interval and the resulting signals and values stored in the internal process image after each cycle . Then depending on the type they are made available on the physical outputs of the controller or as internal variables and together with the signals on the input terminals represent the data-technical basis for the next processing cycle.

But as soon as the overall system consists of more than one controller, the traditional model reaches its limits. Here is where IEC 61499 applies, enabling a modeling of distributed systems. The corresponding cross-manufacturer controllers are for example linked to each other over Ethernet, use this medium to exchange their process data and in this way can be combined into a homogenous overall system. Since the real-time capability is lost due to the latent communication paths between the controllers, an event-based solution replaced the cycle time based approach in IEC 61499. The function blocks familiar from IEC 61131 were expanded with additional in- and outputs for event signaling and contact each other in this way. A function block is then only activated if it receives a trigger signal from another function block.

IEC 61131 and IEC 61499 compared:

  IEC 61131 IEC 61499
Processing Cycle time based Event based
Scalability Only by expanding the processing logic of the individual controller Expanding the processing logic of individual controllers and adding additional controllers
real-time capability Yes, since there are no latent communication paths No, since communication between the controllers has a delay
Interoperability Programming of the individual system according to manufacturer specifications Central programming of the overall system using compatible project planning software

When project planning the system the last step is to export the relevant function scope for each controller in the form of an XML configuration which is then loaded into the respective component. In this way controller sequences can be kept centrally and then distributed to the corresponding controllers and there activated. This approach is also convenient when it comes to later changes, since new rules can be used in a uniform system from task declaration to activation.

In addition to the programmable logic controllers, the use of correspondingly communications capable automation components without their own controller logic is possible. In an Ethernet-based automation environment therefore the Web-IOs from Wiesemann & Theis can also be used as decentralized IO modules in order to acquire analog and digital measurement values or switch corresponding actuators. Integration is carried out for example using the IoT protocols OPC UA or MQTT.

  • #57737

    Web-IO 2x
    Web-IO 4.0 Digital
    2xIn, 2xOut

    Power via PoE also when needed

  • #57730

    Web-IO 12x, 6xRelay
    Web-IO 4.0 Digital
    Digital 12xIn, 12xOut

    12x outputs (6-30V),
    12x inputs (8-30V)

  • #57761

    Web-IO 4.0 Analog 0-20mA
    Web-IO 4.0 Analog
    2x 0..20mA

    Power via PoE also when needed

  • #57762

    Web-IO 4.0 Analog 0-10V
    Web-IO 4.0 Analog
    2x 0..10V

    Power via PoE also when needed