Interoperable Co-Simulation Frameworks for Industrial Automation: Enabling IEC 61499 Model Export to Functional Mock-up Units

Read full text Summarise with VIRAT
Authors: Elena Vasquez, Liam Chen, Ramesh R. Rao
Cited by: 0

Summary

No summary yet. VIRAT can read this paper and write a plain-language summary of its aim, methods, key findings and limitations.

Summarise with VIRAT Free to try with your Science Catalogs account.

Abstract

—Different causes have contributed to the shift of paradigm in the automation field from centralized to modular and distributable. Software and hardware of Programmable Logic Controllers (PLCs) have evolved to be synchronized with the demands nowadays and new standards are trying to follow this trend. One of them is the IEC 61499 standard, which is intended for modelling distributed industrial solutions with a vendor-independent format. This shifting is also bringing new challenges and this paper focuses on the virtual commissioning of plants, which can become a harder task when the system is distributed and involves different interconnected modules. A major problem when doing a virtual commissioning is the coupling between the different physical systems and controlling tools since many vendors still offer closed integrated solutions. Functional Mockup Interface (FMI) is a standard for a cosimulation interface which intends to fill the gaps between different modelling tools, by packaging the models into Functional Mockup Unit (FMU) and allowing a co-simulation master algorithm to have access to the inside model through the proposed interface. This paper presents a mapping between IEC 61499 models and the FMI standard and an implementation of a tool that can export IEC 61499 models into FMUs, which would allow the co-simulation of physical plants and the PLCs software that controls it. An experiment is shown where a simple ProportionalIntegral-Derivative (PID) controller of a tank system is exported as an FMU and co-simulated together with a tank system modelled using OpenModelica I. INTRODUCTION The fourth revolution in the industry (Industry 4.0 or Smart Factory) wants to transform industry the same way the Internet transformed the computers, and even go further. Although the concept of Industry 4.0 may not be the same for all involved parts, some concepts have a strong presence. The Internet is again one of the main actors in this revolution, bringing connectivity to the smallest components in the automation chain. As the revolution is encouraging the flexibility of its parts, centralized systems are evolving to more distributed and modular ones [1]. The heart of these systems is the PLC controlling the logic of the automation. Transforming automation systems from centralized to more modular ones, triggered the creation of the IEC 61499 [2] standard, which complements the well established IEC 61131 [3] and focuses on the missing qualities of distributed systems, not present in the IEC 61131 or even needed in the times it was written. As in other fields, the automation software to be deployed into the real systems must be tested beforehand, because stops in the production of any kind, desired or not, cost money. In the automation field, the need for these steps can be higher since an error can not only stop the production but also damage machines and even humans involved. When one talks about virtual commissioning in the automation field, the logic of PLCs is tested against the virtual representations of the systems they are controlling. This reduces the actual commissioning time and in case of software updates, these can be safely tested. In many cases, the testing starts with Software-in-the-loop (SIL) where the software to be tested runs on a computer different to the one where it will finally run. Digital inputs and outputs are simulated and connected to a virtual system. On a second step, in Hardware-in-the-loop (HIL) tests, the software runs on the real hardware where it will run once the installation is completed. The inputs and outputs of the hardware are actually triggered, and some type of coupling is added to connect these to the virtual system to be controlled [4]. In both cases, normally both logic and the virtual representation of a system are tightly coupled, and combining tools from different vendors can be a hard task. With the new paradigm of distributed systems, the integration of different tools from different vendors is a greater need. The term co-simulation can be seen as SIL where models from different fields are simulated together by a master that controls them. One of the standards in co-simulation that has gained attention in the last years is FMI [5], which defines an interface between models that are packaged in so-called FMUs. FMI can be very useful to automation systems, where hardware's manufacturers can offer their FMU (intellectual property can be maintained) to software developers to test their controlling software against it. FMI allows the co-simulation to be tool-independent, making the integration of several models, normal in distributed systems, an easier task. This paper presents a mapping between IEC 61499 models to the FMI standard and an FMU exporter from a model in IEC 61499, allowing the developer to test the logic of the system against physical models from domain-specific tools. In Section II an overview of the work being done that is related to this paper is presented, together with a brief presentation of the key players to this paper. In Section III the mapping between FMI and IEC 61499 model is explained, to see the relation between types and other characteristics. The actual exporter is introduced in Section IV, together with the tools used for it. Section V presents an experiment that was done for testing the exporter, where a controller modelled in IEC 61499 is tested against a system of a tank modelled in OpenModelica, using a master algorithm which co-simulates both FMUs. Finally, a conclusion is presented in Section VI, where an overview of the work done in the paper is presented and possible future work that can spaw from this. II. STATE OF THE ART In this section, the two key players of this work are presented. Besides that, related work about co-simulation with FMI is described. A. Background on IEC 61131 and IEC 61499 During decades, the industry got used to the well established centralized architecture of automation, where one PLC controls one system. The blooming of technology in this field brought with it a number of vendors offering different solutions which made the different stakeholders look for a solution to all the interoperability problems that come with the lack of a standard. In the early nineties, the standard IEC 61131 was the first step to overcome this issue, especially in its third part, stating different programming languages for PLCs, among them, and interesting for this paper, the Function Block Diagram (FBD), which is a graphical programming language with Function Blocks (FBs) representing functions and input and output variables connected between them with lines [3]. Even though the aforementioned standard helped to fill some interoperability gaps on a high level, especially for the PLC programmer, it did not prevent some other issues. As an example, a software developed for a brand of PLC using one of the standard programming languages was not portable, or at least easily portable, to a PLC from another vendor. This means that industries were normally tied to a vendor, and the incorporation of new vendors wasn't easy since it would require re-programming of software that was already tested and implemented. Also, since the IEC 61131 standard was written in a time when the industry and the automation were designed using a centralized architecture, communication between PLCs wasn't properly covered, producing more issues when using PLCs from different vendors. This last issue was exacerbated in the following decades with the tendency of the production and automation to being more flexible. The IEC 61499 standard [2] (from now on, when the word "standard" is alone, it will refer to IEC 61499) is a domainspecific modelling language intended for distributed systems in the automation field. It was created not as a replacement of IEC 61131, but as an extension of it. It even uses the same data types as IEC 61131. The standard describes several models which help to describe distributed automation systems on a high level. The modelling is platform independent and a eXtensible Markup Language (XML) schema is provided to overcome portability issues. Four of the models described in the standard are presented in this paper since they are of bigger interest for the objectives of it. Fig. 1: Example of an interface of a Function Block The FB model is the base model of the standard and it is used to represent an encapsulated functionality. In IEC 61499 global variables are forbidden. A big difference with the FB from IEC 61131 is the introduction of events, which are separated from data and they trigger the FB and control when data is refreshed, governing the sequence to be executed in a network of FB. The interface of a FB is composed of the input and output events (top of the FB), and the input and output data (bottom of the FB) and their types. This interface should be made public by the developer of the FB for their portability, but the internal behaviour can be maintained private. An example of an interface is shown in Fig. 1. There are three types of FBs and this classification is important when implementing an FMU: Fig. 2: Example of an ECC of a Basic Function Block Basic Function Block (BFB): their functionality is defined by an Event Execution Control (ECC) (Fig. 2), a state diagram with internal variables and algorithms written in programming languages stated in IEC 611313 or compliant to IEC 61499. The algorithm execution, state changes and output events are controlled by the arriving events to the FB. Composite Function Block (CFB): the internal functionality is defined by a network of FBs of any type (Fig. 3). Fig. 3: Example of an internal network of a Composite Function Block Service Interface Function Block (SIFB): their behaviour is user defined and is normally used to access hardware resources or platform dependent features like inputs, outputs or communication. The Application model is a network of FBs with event and data co

Fields of Study & Subjects

Modeling and Simulation Systems Flexible and Reconfigurable Manufacturing Systems Industrial Automation and Control Systems

Publication details

Journal / source
Zenodo (CERN European Organization for Nuclear Research)
Publication date
9 February 2026
Language
EN