Computer-implemented method for developing PLC-based automation solutions
A model-based development process for PLCs automates artifact generation and visualizes state diagrams, addressing the complexity and flexibility issues in PLC programming, enhancing efficiency and reducing errors.
Patent Information
- Application Number
- PCT/EP2026/063240
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Developing industrial control programs for programmable logic controllers (PLCs) based on predefined state machines is laborious, especially as automation systems become more complex, and existing methods lack flexibility and effective visualization tools.
A model-based development process that generates PLC artifacts and user interface artifacts from a system model, allowing for automated generation of PLC programs and intuitive visualization of state diagrams, using standard PLC development setups without additional functionality.
Enhances the flexibility and efficiency of PLC development and operation by providing automated generation of PLC artifacts and intuitive state diagram visualization, reducing manual programming errors and improving development workflows.
Smart Images

Figure EP2026063240_12112026_PF_FP_ABST
Abstract
Description
[0001] 20260502WG - MetaCre8
[0002] 1
[0003] Computer-implemented method for developing PLC-based automation solutions
[0004] The invention relates to a computer-implemented method, a computer program with program code, a computer-readable storage medium with program code, a data processing device, and a development system for a programmable logic controller.
[0005] Industrial controllers and their associated I / O devices are essential for the operation of modern automation systems. These controllers interact with field devices, for example, in a production hall, to control automated processes related to objectives such as product manufacturing, material handling, batch processing, higher-level control, and similar applications. Industrial controllers store and execute user-defined control programs to make decisions related to the controlled process. Such programs can include, among others, ladder logic (LAD), sequential function chart (SFC), function block diagram (FBD), instruction list (IL), structured text (ST), or other similar programming structures. The controller receives any combination of digital, analog, or networked data signals from the field devices, indicating the current state of the process (e.g., temperature, temperature, temperature, etc.).
[0006] The controller receives signals (temperature, position, presence or absence of parts, fill level, etc.) and executes the control program to automate process decision-making based on the received signals. The controller then outputs appropriate digital, analog, or networked control signals to the field devices according to the decisions made by the control program. These outputs can include device control signals, temperature or position control signals, motion control commands, commands to machining or material handling robots, and the like.
[0007] System developers often use a state machine approach to design the behavior of automation systems. The state machine approach assumes that at any given time, the system is in one of a predetermined number of states, and the events that cause the system to transition from one state to another are predefined. Developing industrial control programs based on a predefined state machine design can be a laborious task, especially as automation systems become more complex.
[0008] The abbreviation PLC is to be understood as "programmable logic controller" in the following.
[0009] US Patent 12,005,924 B2 describes a state machine management component that runs on an edge device within an industrial plant. This component can discover state machines defined on industrial controllers and translate their definitions into information models. These information models enable remote client applications to discover and utilize the state machines. The edge-level information models allow client applications to display or consume state machine data generated by the controller, graphically represent the state machines, and transmit commands or values as state machine commands to the controller via the edge device.The system at the edge level thus enables client applications without prior knowledge of the state machines at the control level to discover, retrieve and interact with the state machines defined on the industrial controllers.
[0010] US patent application US 2014 / 0280528 A1 describes a state machine configurator for creating state machines executable on controllers. The state machine configurator provides a development environment that allows a user to define a customized state machine to control a specific industrial process. Once the states and state transitions are defined, the configurator compiles the state machine's configuration information to generate a state machine instruction that can be imported into an industrial control program to facilitate control of the industrial process according to the defined state machine. The state machine configurator supports the creation of role-specific state machines and embedded state machines.
[0011] Against this background, the object of the present invention is to improve the development and operation of a programmable logic controller.
[0012] In particular, the present invention may aim to increase the flexibility in the development of automation solutions for programmable logic controllers (PLCs). The features of the invention are defined in the independent claims, with advantageous embodiments described in the dependent claims. The features of the claims can be combined in any technically meaningful way, taking into account the explanations in the following description and features from the figures, which represent supplementary embodiments of the invention.
[0013] The invention relates to a computer-implemented method comprising:
[0014] Providing a system model following a model-based development process that represents the behavior of at least one programmable logic controller (PLC),
[0015] Generating at least one PLC artifact for the programmable logic controller (PLC) based on the system model using a generation device; generating at least one user interface artifact for a user interface based on the system model using the generation device; generating a PLC program, which is executed using a PLC runtime environment of the PLC, based on the PLC artifact using a PLC development device; generating a state diagram based on the user interface artifact using a user interface generation device.
[0016] Reading at least one state value from the PLC runtime environment during execution of the PLC program using a reading device and
[0017] Display of the state diagram, wherein the state diagram is graphically animated based on at least one state value. The invention is based on the understanding that today's machines and systems for process manufacturing or discrete manufacturing can be considered mechatronic or cyber-physical systems. Their development requires the collaboration of specialists from the disciplines of mechanical design, electrical design, and software development. Today's development workflow for machines and systems is characterized by numerous information and media breaks. Mechanical engineering often takes the lead and is responsible for the initial design of a machine function. After the creation of a conceptual 3D model, coordination takes place with representatives from the disciplines of electrical engineering and control software. Furthermore, the invention is based on the understanding that today's PLC programming uses a significant portion of its capacity for testing and debugging.One reason is the increased error rate due to manual programming. Another is the lack of effective means for visualizing the running program.
[0018] A key advantage of the solution according to the invention is that the development and operation of a programmable logic controller (PLC) or a corresponding automation solution become particularly efficient and flexible. Due to the automated generation of the PLC artifact based on the system model, a standard PLC development setup can be used. This setup does not need to be adapted or extended for the use of the solution according to the invention. Furthermore, the animation of the state diagram provides the viewer with an intuitive overview of information that is particularly relevant for development and operation.
[0019] The system model preferably represents the desired behavior of the programmable logic controller (PLC). The system model preferably comprises a graphical model in the form of diagrams with standardized data structures. Those skilled in the art understand the term "model-based development process" to preferably refer to so-called Model-based Systems Engineering (MBSE).
[0020] Preferably, the system model consists of a block diagram and a state diagram. The block diagram preferably contains elementary functions representing actuators, sensors, and a control function in the sense of a mechatronic system. The behavior of the control function is further preferably described by a state machine. The variables connected to the ports of the control function are available in a state diagram to, for example, trigger a state change depending on sensor signals. Boolean expressions are used, for example, in the software implementation for these state changes (transitions).
[0021] The programmable logic controller (PLC) is preferably designed according to the IEC 61131-3 standard. Preferably, part of its behavior is set by the PLC manufacturer. More preferably, another part is set via a user program. While the PLC's behavior is determined by the operating system, the configuration, and the user program, for the present solution according to the invention, the behavior determined by the user program is of particular importance.
[0022] A person skilled in the art understands the term PLC artifact preferably as a tangible or interpretable result of generation by the generating device. PLC artifacts preferably comply with the requirements of standard IEC 61131-3. The PLC artifact preferably contains textual program code. Furthermore, interface specifications from the block diagram are preferably used for generating the PLC artifact.
[0023] The term "user interface artifact" is understood by those skilled in the art preferably as a tangible or interpretable result of generation by the generation unit. The user interface artifact preferably contains a diagram instance specification. The diagram instance specification is, for example, a list that specifies which diagram component types are required for a given system model. The diagram instance specification also specifies which dimension (size), coordinate, rotation, and / or textual elements each diagram component type should have. The generation of the PLC computer program code is preferably carried out using a PLC builder unit of the PLC development unit. The PLC artifact is preferably transferred from the generation unit to an end device, for example, a developer PC, with an attached source code management unit and can then be made available to the PLC development unit.Preferably, the PLC artifact is integrated into a project structure automatically or through user interaction with the PLC development facility.
[0024] The user interface generation unit is preferably part of a user interface development unit. The state diagram is preferably generated using a user interface builder unit within the user interface development unit. The user interface artifact is preferably transferred from the generation unit to an end device, such as a developer PC, with an attached source code management unit, and can then be made available to the user interface development unit.
[0025] The artifacts are preferably further integrated into a project structure automatically or through interaction of a user with the user interface generation device or the PLC generation device.
[0026] The reading device is preferably part of a graphical user interface. The status values are preferably provided directly to the reading device. Alternatively or additionally, the status values are mirrored and provided to the reading device via another device. Methods such as OPC UA (Open Platform Communications Unified Architecture) and MQTT (Message Queuing Telemetry Transport) can be used for this purpose.
[0027] The display is preferably done using a display device of a graphical user interface (GUI).
[0028] The programmable logic controller (PLC) is preferably part of a complete system (e.g., a production plant) that has and / or performs a multitude of functions, one function being implemented by the PLC. In other words, the complete system comprises a multitude of PLC-based functions. The method according to the invention is further preferably carried out for each PLC-based function of the complete system.
[0029] Accordingly, the entire system is created and developed incrementally.
[0030] In a further advantageous embodiment of the method, it is proposed that the reading of the at least one state value is performed using address information. This address information specifies the read address for reading the state value from the PLC runtime environment. The address information is provided by the generation unit during the generation of the user interface artifact, depending on the generation of the PLC artifact.
[0031] This provides a particularly advantageous solution for reading the current state values and consequently animating the state diagram. This eliminates the need for any additional PLC-side features beyond the standard functionality of commercial PLC / HMI (Human Machine Interface) combinations to visualize the current state diagram. In other words, the programmable logic controller (PLC) complies with the IEC 61131-3 standard, which does not include any additional functions for implementing the method according to the invention.
[0032] The address information is embedded, for example, in the diagram instance specification.
[0033] In a further advantageous embodiment of the method, it is proposed that the state diagram be graphically animated based on at least one state value by visually highlighting a sub-area of the state diagram which represents a current execution section during the execution of the PLC program.
[0034] This results in a particularly intuitive animation of the state diagram, which also provides the viewer with important information: the current execution phase. The sub-area is preferably a diagram component defined by a specific diagram component type. This allows for a particularly effective implementation of the animation by highlighting the graphical elements defined by the diagram component type during the animation.
[0035] In a further advantageous embodiment of the method, it is proposed that the system model includes a state machine and the state diagram graphically represents the state machine.
[0036] In this way, a particularly suitable variant is created to support a user in the development and / or operation of the automation solution.
[0037] In a further advantageous embodiment of the method, it is proposed that the generation unit is logically and / or physically separated from the PLC development unit and / or the user interface generation unit.
[0038] This embodiment is particularly advantageous for implementing a PLC development device that complies with IEC 61131-3 and does not have any additional functions beyond those specified in the standard. In this way, standard PLC development devices can be used with the solution according to the invention. These devices do not need to be equipped with or implemented with additional functions to achieve the effects of the solution according to the invention.
[0039] A person skilled in the art understands logical separation preferably to mean that the generation unit and the PLC development unit can be distributed on the same physical device, but do not interact with each other. This is achieved, for example, through so-called containers or independent applications. Existing interfaces of the PLC development unit can be used, for instance, to enable automated data exchange between the applications. In the case of physical separation, the generation unit and the PLC development unit are preferably installed on different physical devices. This consideration applies analogously to the separation of the generation unit and a user interface generation unit.
[0040] In a further advantageous embodiment of the method, it is proposed that the user interface be implemented by means of a frontend application.
[0041] This represents a particularly suitable alternative to the user interface described above, which comprises a graphical user interface with a display device. This is because the frontend application allows for increased flexibility in user interface development.
[0042] In this embodiment, it is proposed that the user interface includes a frontend application, which therefore enables intuitive and user-friendly interaction with the system model.
[0043] For example, a diagram instance specification is read from an information model, and the user interface is initialized with the state diagram based on this specification. The information model is implemented, for example, using OPC UA, data structures in the sense of an Asset Administration Shell, or other data models. Preferably, the diagram instance specification contains the address information for reading the data sources to update the state values. This enables automated diagram configuration. According to a specific embodiment, the diagram instance specification (as user interface artifacts) is retrieved from the generation unit and transferred to the front-end application as a structured data set. There, the data set is used in the user interface generation unit together with the type library and the data acquisition service to initialize the dynamically animated user interface.The data acquisition service uses the address information contained in the user interface artifact to supply the diagram components with the corresponding data from the controller, for example via OPC UA or MQTT, in order to animate them dynamically. This enables automatic diagram configuration.
[0044] The frontend application is preferably part of the user interface generation facility. The frontend application can further preferably be part of the modeling facility.
[0045] In a further advantageous embodiment of the method, it is proposed that the PLC artifact comprises a PLC function block and that the generation of the PLC program is carried out using the PLC function block, a user-defined data type and / or a symbol table.
[0046] The term PLC function block (FB) is preferably understood as a reusable program block for a programmable logic controller (PLC). It encapsulates a specific function or part of a control process and has defined inputs and outputs as well as internal memory for data that is retained even after the block has been executed (static variables). It is also preferably a self-contained, small program that performs a specific task and communicates with other program parts via its interfaces (inputs and outputs). For example, it is implemented as a modular code section that executes a specific function within the controller. This enables structured and modular programming of PLC applications. Furthermore, the function block preferably encapsulates logic and data to create a reusable component.
[0047] User-defined data types are often referred to in technical terms as User Defined Types (UDTs). These can be part of the PLC artifact.
[0048] In programmable logic controllers (PLCs), the symbol table preferably defines the assignment of symbolic names to the physical or logical addresses of inputs and outputs, flags, counters, timers, data blocks, and other variables in the PLC program. The symbol table can be part of the PLC artifact. Furthermore, in an advantageous embodiment of the method, it is proposed that the user interface artifact includes a diagram instance specification. The state diagram is generated based on the diagram instance specification and a diagram component type specified in the diagram instance specification, which is provided by the user interface generation device.
[0049] This represents a particularly simple method for generating the state diagram according to its representation in the system model. Furthermore, predefined diagram component types are used to generate the state diagram, thus making efficient use of available resources.
[0050] The diagram instance specification preferably indicates which diagram component types are required. The advantage of this embodiment is that the diagram component types are available in the user interface generation facility as user-defined templates or a library and can be conveniently used for generating the user interface.
[0051] In a further advantageous embodiment of the method, it is proposed that when generating the user interface artifact based on the system model, a diagram component type is taken into account, which is provided by a modeling device. The diagram component type provided by the modeling device corresponds to the diagram component type provided by the user interface generation device.
[0052] This has the advantage that the diagram component type (in the sense of a complete data set) does not need to be transferred from the modeling device to the user interface generation device. It also takes advantage of the fact that diagram component types are frequently provided in user interface generation devices. Furthermore, in an advantageous embodiment of the method, it is proposed that when PLC program code, which can be displayed using the PLC development device, is changed, the system model is adapted by determining a system model partial piece of information that at least partially represents the system model, and the adaptation of the system model is then performed depending on the change in the PLC program code and based on this system model partial piece of information.
[0053] This creates a way to (semi-)automatically convert changes to the PLC program code, displayed via the PLC development environment, into changes to the system model. In other words, the system model is synchronized based on the change in the PLC program code. This eliminates the need for model references in the source code on the PLC side, for example, in the form of embedded identifications in comments or annotations. In ambiguous cases, comments intended to guide the user in understanding the generated program code can be reused to map the code change to the model.
[0054] The PLC program code is modified, for example, using the PLC development environment. For instance, the modification is initiated by a user of the PLC development environment or entered through interaction with the PLC development environment.
[0055] The system model partial information preferably provides the information relating to the system model that allows the system model to be automatically adapted depending on changes to the PLC program code.
[0056] In a first preferred embodiment, the system model partial information is more preferably an ID (identifier) that is part of the user interface artifact and, in particular, part of the diagram instance specification. More preferably, the system model partial information includes the ID that establishes a link to the original model component (and the one to be modified) in the modeling setup. The original model component is more preferably a textual component of the system model (and not a graphical one). This solution is based on the understanding that program code generated from the system model can be divided into two groups. The first group comprises automatically generated code for the state machine structure. This code is derived from the information in the graphically created model. The second group comprises code derived from textual models.For example, structured text or similar languages are used as so-called Action Languages.
[0057] Alternatively or additionally, according to a second preferred embodiment, the system model sub-information specifies the name of a state of the state machine associated with the change in the PLC program code. Based on this state, it can be determined which model components in the modeling setup should be adjusted.
[0058] Preferably, according to the first and / or second preferred embodiment, state variables are used as partial information in the system model. In hierarchical state structures, the state variable structure represents the hierarchical structure in the form of a namespace. The namespace provides a name for each state variable, where the name consists of several sections, each indicating a hierarchical level of the hierarchical state structure. For example, the penultimate section of a state variable's name indicates the respective parent element (container) of a state. Orthogonal (parallel) states have different names at a common hierarchical level.
[0059] In a further advantageous embodiment of the method, it is proposed that the state diagram be adapted, preferably updated, based on the adapted system model.
[0060] This embodiment makes it possible to achieve a corresponding (partially) automated update of the visualization of the state diagram, based on the textual model elements, when the PLC program code is adapted.
[0061] The adaptation of the state diagram based on the adapted system model preferably means that the system model is adapted according to the embodiment described above, preferably (partially) automatically. User interface artifacts are then regenerated based on this adaptation. Alternatively or additionally, existing (already generated) user interface artifacts can be updated using the name of the associated state without first adapting the system model. This name can be implemented using the namespace described above.
[0062] In a further advantageous embodiment of the method, it is proposed that the state diagram is changed when a PLC program code, which can be displayed by means of the PLC development device, is modified, wherein the state diagram is adapted depending on the change in the PLC program code.
[0063] This has the advantage that the display of the state diagram, which includes parts of the program code as a purely visual representation, is adjusted to the changes in the program code.
[0064] Preferably, the state diagram is adapted without modifying the system model. This allows the user to maintain consistency between the adapted code and the corresponding state diagram without necessarily having to modify the system model. Synchronization of the system model can then be performed at a later time.
[0065] According to a further aspect, a computer program with program code is proposed which, when executed on a computing device, causes it to execute the computer-implemented method according to an embodiment as described above. The computer program is preferably a computer program product. The computing device is preferably a computing device of the generation device, PLC development device, user interface generation device, and / or the modeling tool described above. Alternatively or additionally, the computer program is executed distributed by means of the computing device of the generation device, the computing device of the PLC development device, the computing device of the user interface generation device, and / or the computing device of the modeling tool.
[0066] According to another aspect, a computer-readable storage medium containing program code is proposed which, when executed on a computing device, causes it to execute the computer-implemented method according to an embodiment as described above.
[0067] The storage medium is, for example, part of a physical storage device. Storage media include magnetic storage media (such as hard disk drives (HDDs), floppy disks, magnetic tapes), optical storage media (such as CDs, DVDs, Blu-ray discs), and semiconductor storage media (such as USB flash drives, memory cards, solid-state drives (SSDs), ROM (read-only memory), RAM (random access memory), flash memory, EPROM, and EEPROM).
[0068] According to another aspect, a data processing device is proposed, comprising:
[0069] a system model according to a model-based development process, which represents the behavior of at least one programmable logic controller, a generation device which is set up,
[0070] at least one PLC artifact for the programmable logic controller and
[0071] at least one user interface artifact for a user interface
[0072] to generate using the system model,
[0073] a PLC development facility which is set up to generate a PLC program which is executed using a PLC runtime environment of the programmable logic controller, based on the PLC artifact,
[0074] a user interface generation device configured to generate a state diagram based on the user interface artifact, and a reading device configured to read at least one state value from the PLC runtime environment when executing the PLC program, wherein the user interface is configured to display the state diagram and to graphically animate the state diagram based on the at least one state value.
[0075] The data processing device is preferably configured to carry out the inventive method described above.
[0076] According to another aspect, a development system for a programmable logic controller is proposed, comprising:
[0077] at least one data processing device according to an embodiment as described above.
[0078] The development system comprises the components required for the development of the programmable logic controller (PLC). These include computer programs, computing devices, storage devices, input devices, output devices, network devices, etc.
[0079] For advantages, embodiments and design details of the computer program and computer-readable storage medium according to the invention, the data processing device according to the invention and the development system according to the invention, reference can be made to the preceding description of the corresponding features of the computer-implemented method according to the invention.
[0080] The invention described above is explained in detail below against the relevant technical background with reference to the accompanying drawings, which show preferred embodiments. The invention is in no way limited by the purely schematic drawings, although it should be noted that the drawings are not dimensionally accurate and are not suitable for defining size relationships. It is illustrated in
[0081] Fig. 1 : a first embodiment of a data processing device according to the invention;
[0082] Fig. 2: a first embodiment of a method according to the invention as a schematic flowchart;
[0083] Fig. 3: a second embodiment of a data processing device according to the invention;
[0084] Fig. 4: a second embodiment of a method according to the invention; Fig. 5: an embodiment of an extension of the method according to the invention as a schematic flowchart;
[0085] Fig. 6: an embodiment of a display for a technical device; Fig. 7: an embodiment of a state diagram; and
[0086] Fig. 8: another embodiment of a display for a technical device; and
[0087] Fig. 9 shows a third embodiment of a data processing device according to the invention.
[0088] Fig. 1 shows a first embodiment of a data processing device 2 according to the invention.
[0089] Figure 2 shows a first embodiment of a method 1 according to the invention as a schematic flowchart representing the steps of method 1. The method 1 shown in Figure 2 will now be described with reference to the process steps performed by the data processing device 2 shown in Figure 1.
[0090] The data processing device 2 is part of a development system 27. The data processing device 2 includes a modeling device 25. The modeling device 25 is, for example, a computer system that a user can operate to define a system model 3 within the framework of a model-based development process. The system model 3 models, for example, a technical device 46 (see Fig. 6 and Fig. 8). The model-based development process is, for example, Model-based Systems Engineering (MBSE), in which graphical models in the form of diagrams with standardized data structures are used. The system model 3 comprises a state machine. The system model 3 represents the behavior of a programmable logic controller 4. The diagrams are formed from predefined diagram component types 24, which are provided by the modeling device 25.In one process step, the modeling unit 25 performs a provision 28 of the system model 3 according to the model-based development process. In other words, the system model 3 is defined and provided by means of the modeling unit 25. Based on this, the system model 3 can be retrieved.
[0091] The data processing device 2 further comprises a generation unit 6. The generation unit 6 performs a process step 29 generating PLC artifacts 5 for the programmable logic controller 4 based on the system model 3. In other words, the PLC artifacts 5 are generated by means of the generation unit 6. The PLC artifacts 5 comprise PLC function blocks 19, user-defined data types 20, and symbol tables 21. The term PLC function block 19 (FB) is preferably understood as a reusable program block within a programmable logic controller 4. It encapsulates a specific function or part of a control process and has defined inputs and outputs as well as internal memory for data that is retained even after the block has been executed (static variables).It is preferably a self-contained small program that performs a specific task and communicates with other program parts via its interfaces (inputs and outputs). For example, it is implemented as a modular code section that executes a specific function within the controller 4. This enables structured and modular programming of PLC applications. The PLC function block 19 preferably encapsulates logic and data to create a reusable component. The data types 20 are, for example, so-called User Defined Types (UDTs). The PLC artifacts 5 are transferred to an end device, such as a developer PC, and connected to a source code management system. The PLC artifacts 5 are supplied to the PLC development system 11 via interfaces or in the form of files. The PLC artifacts 5 are integrated into a project structure.
[0092] The generation unit 6 further executes a process step 30 generating user interface artifacts 7 for a user interface 8 based on the system model 3. In other words, the user interface artifacts 7 are generated by the generation unit 6. During generation 30, diagram component types 24, provided by the modeling unit 25, are taken into account. The user interface artifacts 7 comprise a diagram instance specification 22 and are transferred to an end device, for example, a developer PC, where they can be provided to a user interface generation unit 13. A file bundle consisting of PLC artifacts and user interface artifacts can be created. The diagram instance specification 22 is, for example, a list that specifies which diagram component types 24 are required for a given system model 3.The diagram instance specification 22 also specifies the dimension (size) and coordinate of each diagram component type 24. Furthermore, the diagram instance specification 22 contains, for example, textual elements and address information for state variables. The user interface generation unit 13 provides diagram component types 23 that correspond to the diagram component types 24 provided by the modeling unit 25. The diagram component types 23 are provided as libraries for user-defined, parameterizable, and reusable components. Based on the diagram instance specification 22, the user interface generation unit 13 is thus able to use the desired diagram component types 23 for visualizing the state machine.
[0093] The PLC development unit 11 includes a PLC builder unit 33, which executes a process step 31 of generating a PLC program 9. In other words, the PLC program 9 is generated using the PLC builder unit 33. The generation step 31 is performed using the PLC artifact 5 and type libraries 38. The PLC program 9 is executed using a PLC runtime environment 10 of the programmable logic controller 4 (according to a process step 35). During the execution step 35 of the PLC program 9, the programmable logic controller 4 uses state values 15 to control the sequence.
[0094] The user interface generation device 13 includes a user interface builder device 34, which performs a process step 32 generating a state diagram 12 based on the user interface artifact 7. In other words, the user interface builder device 34 generates the state diagram 12 based on the user interface artifact 7. The state diagram 12 is then transferred to a user interface 8 and integrated into it.
[0095] A reading device 16 performs a process step 36 of reading state values 15 from the PLC runtime environment 10 when executing 35 of the PLC program 9. In other words, the reading device 16 reads state values 15 from the PLC runtime environment 10. The reading 36 of the state values 15 is performed using address information, which specifies the read address for reading 36 the state values 15 from the PLC runtime environment 10. The address information is provided when generating 30 the user interface artifact 7, depending on the generation 29 of the PLC artifact 5.
[0096] The status values 15 are, for example, provided directly to the reading device 16. Alternatively or additionally, the status values 15 are mirrored and provided to the reading device 16 via another device. Solutions such as OPC UA (Open Platform Communications Unified Architecture) and MQTT (Message Queuing Telemetry Transport) can be used for this purpose.
[0097] The user interface 8 executes a process step 37 of the state diagram 12. Displaying 37 is done using a display device of a graphical user interface 8 (GUI). The state diagram 12 graphically represents the state machine. The state diagram 12 is animated graphically based on at least one state value 15. For this purpose, a sub-area 17 of the state diagram 12, which represents a current execution phase during the execution 35 of the PLC program 9, is visually highlighted.
[0098] The generation unit 6 is logically and physically separated from the PLC development unit 11. The generation unit 6 is further logically and / or physically separated from the user interface generation unit 13. The PLC development unit 11 can thus be configured according to standard IEC 61131-3, wherein the functionalities according to the invention are part of the generation unit 6 and the user interface generation unit 13.
[0099] In the method 1 described above, a person skilled in the art understands that the concept underlying method 1 incrementally creates and develops a complete system (for example, a production plant). Accordingly, several functions of the complete system are successively modeled, generated, and developed using method 1 according to the invention. In this way, the generated artifacts for each function can be successively integrated into the respective project structure.
[0100] Figure 3 shows a second embodiment of a data processing device 2 according to the invention. The data processing device 2 shown in Figure 3 is constructed similarly to the data processing device 2 shown in Figure 1. Identical or functionally equivalent elements are provided with the same reference numbers. Figure 4 shows a second embodiment of a method 1 according to the invention as a schematic flowchart representing the steps of the method 1. The method 1 shown in Figure 4 will now be described with reference to the process steps performed by the data processing device 2 shown in Figure 3. This second embodiment of the data processing device and the method according to the invention can be understood as an alternative or supplement to the functionalities of the first embodiment.The user interface generation device 14 comprises a front-end application 18. The front-end application provides, among other things, the diagram component types. The diagram instance specification 22 (as user interface artifacts 7) generated by the generation device 6 is read from an information model 41, and the user interface 8 is initialized with the state diagram 12. The information model 41 is implemented, for example, using OPC UA, data structures in the sense of an Asset Administration Shell, or other data models. Preferably, the diagram instance specification 22 contains the address information 36 for reading the data sources to update the state values 15. In this way, automated diagram configuration is enabled.
[0101] The sequence of procedure 1 according to Fig. 4 is similar to the sequence of procedure 1 shown in Fig. 2. Identical and functionally equivalent process steps are provided with the same reference numbers.
[0102] The generation unit 6 executes a process step 30, generating user interface artifacts 7 for a user interface 8 based on the system model 3. In other words, the user interface artifacts 7 are generated by the generation unit 6. During generation 30, diagram component types 23, provided by the modeling unit 25, are taken into account. For a frontend application 18, static data is supplied, for example, via REST (REST: Representational State Transfer), while dynamic data is collected via a data acquisition service and stored in the respective user interface component, for example, using OPC UA. The user interface artifact is, for example, in JSON format (JSON: JavaScript Object Notation).
[0103] The frontend application 18 generates the state diagram 12 in a process step 32. In contrast to the first embodiment of method 1, the display 37 of the state diagram 12 is achieved by executing the frontend application 18. In a process step 36, the state values 15 are read from the PLC runtime environment 10 when executing 35 the PLC program 9. Figure 5 shows an extension of the first embodiment of method 1 according to the invention shown in Figure 2. Identical or functionally equivalent components are provided with the same reference numerals.
[0104] In the extension shown in Fig. 5, an ID (identification) is embedded as system model sub-information during the generation 30 of the user interface artifact 7. The ID establishes a link to the original model component in the modeling device 25. The ID is part of the diagram instance specification 22. Furthermore, the original model component is preferably a textual component of the system model 3 (and not a graphical component). This solution is based on the understanding that program code generated from the system model 3 can be divided into two groups. The first group comprises automatically generated code for the structure of the state machine. This code is derived from the information of the graphically created model (graphical component). The second group comprises code derived from textual models.For example, structured text or similar languages are used as so-called Action Languages.
[0105] The system model partial information is stored, for example, by means of a higher-level source code management system and outside of the PLC development system 11. Alternatively or additionally, the system model partial information is stored in a synchronized workspace on an end device (e.g., a developer PC) as well as in the source code management system. In process step 39, PLC program code 26, which is displayed by means of the PLC development system 11, is modified. This occurs, for example, through user interaction with the PLC development system 11.
[0106] During change 39, system model 3 is (partially) automatically or system-guidedly adapted (according to a process step, adaptation 40). The adaptation 40 of system model 3 is performed depending on change 39 of the PLC program code 26 and based on the system model partial information. Based on the adapted system model 3, the state diagram 12 is adjusted.
[0107] The basis for adapting the system model 3 based on code changes is the aggregated data sets (in particular, program code or difference, user interface artifact), which are transmitted, for example, from a continuous integration pipeline or an interface application installed on the end device to the generating unit in order to perform reverse engineering and initiate the model change process. For the adaptation of the state diagram 12, an adapted user interface artifact 7 with an adapted diagram instance specification 22 is generated. In this way, a change 39 of the PLC program code 26 is (partially) automatically transferred into an adapted state diagram 12.
[0108] Alternatively, the state diagram can be adapted depending on the change in the PLC program code without adapting the system model.
[0109] Figure 6 shows an embodiment of a display 37 of a technical device 46. The display 37 shows a view perceived by a user of the user interface 8. In the illustrated embodiment, the device 46 is a slide 47 that can be moved automatically between position 49 (A) and position 50 (B) by means of a pneumatic drive 48. In the view shown in Figure 6, the slide 47 is in position 50 (B).
[0110] Figure 7 schematically shows a state diagram 12, which represents the states of the slide 47 shown in Figure 6. The state diagram 12 is based on a state machine, which is used to model the device 46 shown in Figure 6. The state diagram 12 shows a state 42, in which the slide 47 is in position A. The state diagram 12 also shows a state 43, in which the slide 47 is in position B. Furthermore, the state diagram 12 shows a state 44, in which the slide 47 moves to position B, and a state 45, in which the slide 47 moves to position A. Since the slide 47 shown in Figure 6 is in position B, the corresponding state 43 is visually highlighted. This highlighting is an example of the graphical animation of the state diagram 12. For this purpose, a sub-area 17 of the state diagram 12 is visually highlighted.The highlighted section 17 represents a current execution section of the PLC program 9, which is executed by the programmable logic controller 4, which is used to control the carriage 47.
[0111] Figure 8 shows another embodiment of the display 37 shown in Figure 6. The display 37 is constructed similarly to the display 37 shown in Figure 6. Identical or functionally equivalent elements are provided with the same reference numerals. In contrast to Figure 6, the carriage 47 in the display 37 of Figure 8 is shown moving to position B. Accordingly, the operating and display element 51 "move to B" is shown hatched (and, in one implementation, for example, represented as an illuminated push button). This corresponds to state 44 of the state diagram 12 shown in Figure 7. In other words, the state shown in Figure 8 would result in state 44 being highlighted in the state diagram 12.
[0112] Figure 9 shows a third embodiment of a data processing device 2 according to the invention. The data processing device 2 shown in Figure 9 is constructed similarly to the data processing device 2 shown in Figure 3. Identical or functionally equivalent elements are provided with the same reference numbers.
[0113] The diagram instance specification 22 (as user interface artifacts 7) is retrieved from the generation unit 6 and transferred as a structured data set to the front-end application 18. There, the data set is used in the user interface generation unit 14, together with the diagram component types 23 and the data acquisition service 52, to initialize the dynamically animated user interface 8. The data acquisition service 52 uses the address information contained in the user interface artifact 7 to supply the diagram components with the corresponding data from the controller 4, for example via OPC UA or MQTT, in order to animate them dynamically. This enables automatic diagram configuration.Although the invention has been further illustrated and described in detail by the preferred embodiments, the invention is not limited by the disclosed examples and other variations can be derived from them by a person skilled in the art without departing from the scope of protection of the invention. List of reference numerals.
[0114] 1. Procedure 31. Generate data processing device 32. Generate system model 33. PLC builder setup control 34. User interface 5. PLC artifact builder setup generation setup 35. Execute
[0115] 7 User Interface Artifact 36 Read
[0116] 8 User interface 37 Displays
[0117] 9 PLC program 38 Type libraries 10 PLC runtime environment 39 Change
[0118] 11 PLC development facility 40 Adapt
[0119] 12 State diagram 41 Information model 13 User interface 42 State Generation device 43 State
[0120] 14 User interfaces - 44 Status of generation unit 45 Status
[0121] 15 State value 46 Device
[0122] 16 Reading device 47 Sled
[0123] 17 Sub-area 48 Pneumatic drive 18 Front-end application 49 Position
[0124] 19 PLC function block 50 positions
[0125] 20 Data type 51 Display element 21 Symbol table 52 Data acquisition service 22 Chart instance specification
[0126] 23 Chart Component Type
[0127] 24 Chart Component Type
[0128] 25 Modeling device
[0129] 26 PLC program code
[0130] 27 Development system
[0131] 28 Provide
[0132] 29 Produce
[0133] 30 Produce
Claims
Patent claims 1. Computer-implemented method (1), comprising: Providing (28) a system model (3) according to a model-based development process which represents the behavior of at least one programmable logic controller (4), Generating (29) at least one PLC artifact (5) for the programmable logic controller (4) based on the system model (3) using a generation device (6), Generating (30) at least one user interface artifact (7) for a user interface (8) based on the system model (3) using the generation device (6), Generating (31) a PLC program (9) which is executed using a PLC runtime environment (10) of the programmable logic controller (4), based on the PLC artifact (5) using a PLC development device (11 ), Generating (32) a state diagram (12) from the user interface artifact (7) using a user interface generation device (13,14), Reading (36) at least one state value (15) from the PLC runtime environment (10) during execution (35) of the PLC program (9) using a reading device (16) and 1. Display (37) of the state diagram (12), wherein the state diagram (12) is graphically animated based on the at least one state value (15).
2. Method (1) according to claim 1, wherein the reading (36) of at least one state value (15) is carried out using address information, the address information specifies the read address for reading (36) the state value (15) from the PLC runtime environment (10) and the address information is provided by means of the generation device (6) during the generation (30) of the user interface artifact (7) depending on the generation (29) of the PLC artifact (5).
3. Method (1) according to claim 1 or claim 2, wherein the state diagram (12) is graphically animated based on at least one state value (15) by visually highlighting a sub-area (17) of the state diagram (12) which represents a current execution section during the execution (35) of the PLC program (9).
4. Method (1) according to one of the preceding claims, wherein the system model (3) comprises a state machine and The state diagram (12) graphically represents the state machine.
5. Method (1) according to one of the preceding claims, wherein the generation unit (6) is logically and / or physically separated from the PLC development unit (11) and / or the user interface generation unit.
6. Method (1) according to any one of the preceding claims, wherein the user interface (8) is implemented by means of a front-end application (18).
7. Method (1) according to any one of the preceding claims, wherein the PLC artifact (5) comprises a PLC function block (19) and the generation (31) of the PLC program (9) is carried out using of the PLC function block (19), a user-defined data type (20) and / or a symbol table (21) This has been done.
8. Method (1) according to any of the preceding claims, wherein the user interface artifact (7) comprises a diagram instance specification (22) and The generation (32) of the state diagram (12) is carried out according to the diagram instance specification (22) and according to a diagram component type (23) specified in the diagram instance specification (22), which is provided by means of the user interface generation device.
9. Method (1) according to one of the preceding claims, wherein, when generating (30) the user interface artifact (7) based on the system model (3), a diagram component type (24) is taken into account which is provided by means of a modeling device (25), and The diagram component type (24) provided by the modeling device (25) corresponds to the diagram component type (23) provided by the user interface generation device (13, 14).
10. Method (1) according to any one of the preceding claims, comprising: Adapting (40) the system model (3) when changing (39) a PLC program code (26), which can be displayed using the PLC development device (11), by a system model partial information which at least partially represents the system model (3) is determined and the adaptation (40) of the system model (3) depending on the change (39) of the PLC program code (26) and on the basis of the system model partial information is carried out.
11. Method (1) according to claim 10, wherein the state diagram (12) is adapted based on the adapted system model (3).
12. Computer program with program code which When executed (35) on a computing device, this causes the computer-implemented method (1) according to at least one of claims 1 to 11 to be executed.
13. Computer-readable storage medium containing program code, which When executed (35) on a computing device, the computing device is caused to execute the computer-implemented method (1) according to at least one of claims 1 to 11.
14. Data processing device (2), comprising: a system model (3) according to a model-based development process, which represents the behavior of at least one programmable logic controller (4), a generating facility (6) which is set up, at least one PLC artifact (5) for the programmable logic controller (4) and at least one user interface artifact (7) for a user interface (8) to generate using the system model (3), a PLC development facility (11) which is set up to generate a PLC program (9) which is executed by means of a PLC runtime environment (10) of the programmable logic controller (4) using the PLC artifact (5), a user interface generation device (13, 14) which is configured to generate a state diagram (12) based on the user interface artifact (7), and a reading device (16) which is configured to read at least one state value (15) from the PLC runtime environment (10) when executing (35) the PLC program (9), wherein the user interface (8) is set up to display the state diagram (12) and to graphically animate the state diagram (12) based on at least one state value (15).
15. Development system (27) for a programmable logic controller (4), comprising: at least one data processing device (2) according to claim 14.
