Abstract

Cyber-Physical Production Systems (CPPS) are long-living and mechatronic systems, which include mechanics, electrics/electronics and software. The interdisciplinary nature combined with challenges and trends in the context of Industry 4.0 such as a high degree of customization, small lot sizes and evolution cause a high amount of variability. Mastering the variability of functional control software, e.g., different control variants of an actuator type, is itself a challenge in developing and reusing CPPS software. This task becomes even more complex when considering extra-functional software such as operating modes, diagnosis and error handling. These software parts have high interdependencies with functional software, often involving the human-machine interface (HMI) to enable the intervention of operators. This paper illustrates the challenges in documenting the dependencies of these software parts including their variability using family models. A procedural and an object-oriented concept for implementing error handling, which represents an extra-functional task with high dependencies to functional software and the HMI, are proposed. The suitability of both concepts to increase the software's reusability and, thus, its flexibility in the context of Industry 4.0 is discussed. Their comparison confirms the high potential of the object-oriented extension of IEC 61131-3 to handle planned reuse of extra-functional CPPS software successfully.

Highlights

  • AND MOTIVATIONCyber-Physical Production Systems (CPPS) are mecha- diagnosis, error handling and operating modes is an essentronic, variant-rich and long-living systems connected tial part of control software: extra-functional code makes to digital networks to use globally available data and ser- up around 50-75% of industrial control code [4] causing vices

  • The last update of the PLC programming standard IEC 61131-3 enables OO for PLCs, it is not yet established in industry and guidelines for its application are rare [7]. To bridge this gap and illustrate the challenges and potential solutions to deal with extra-functional software parts, this paper gives an introduction to the design decisions required to implement error handling

  • Functional software for implementing the CPPS behavior in automatic mode is only a small part of the control logic compared to the extra-functional software, which is with 50-75% the much larger part [4]

Read more

Summary

INTRODUCTION

Cyber-Physical Production Systems (CPPS) are mecha- diagnosis, error handling and operating modes is an essentronic, variant-rich and long-living systems connected tial part of control software: extra-functional code makes to digital networks to use globally available data and ser- up around 50-75% of industrial control code [4] causing vices. This simple example shows that error handling, operating modes, and HMI are strongly interlinked, but they have fundamentally different implementation and code structures This makes it difficult to manage their variability and systematic reuse. The last update of the PLC programming standard IEC 61131-3 enables OO for PLCs, it is not yet established in industry and guidelines for its application are rare [7] To bridge this gap and illustrate the challenges and potential solutions to deal with extra-functional software parts, this paper gives an introduction to the design decisions required to implement error handling. VOGEL-HEUSER ET AL.: MANAGING VARIABILITY AND REUSE OF EXTRA-FUNCTIONAL CONTROL SOFTWARE IN CPPS planned reuse of variant-rich software systems, where artifacts common to all variants are ideally implemented only once [10].

Reuse of extra-functional CPPS Software
Reuse of HMI Code
Reuse of Operating Modes in Control Code
Steps in Error Handling
PROCEDURAL AND OO CONCEPT TO EASE REUSE OF ERROR HANDLING
Procedural Concept for Error Handling
Procedural Concept to Implement Error Handling
Using OO IEC 61131-3 Concepts
OO IEC to Ease Reuse of Variant-rich or Extrafunctional Control Software
OO Concept with Callback Pattern to Communicate an Error and Its Severity
Method A Method B
Findings
CONCLUSION AND FUTURE WORK

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.