Automation System Load State Segmentation for Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automation systems lack effective support for commissioning engineers during testing and loading modifications of control programs, particularly in industrial settings, as they fail to provide transparent load states for individual load objects and restrict debugging capabilities due to inadequate visualization of online and offline program states.
Innovation Solution
Introducing a third state for load objects to indicate deletion, allowing for improved administration and testing of control programs by marking deleted objects as still belonging to the online program, enabling testing at any time and graphical representation of load states for clear differentiation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If only two load states (available and integrated) are used for load objects, then the system structure remains simple, but the ability to track and administer modifications transparently is insufficient
Solution Approach 1:
The patent segments the load state information into three distinct states: first state (available in automation system), second state (integrated into control program), and third state (deleted from control program). This segmentation allows comprehensive tracking of load object status without creating complex management overhead, as each state represents a clear, discrete condition that can be independently managed.
Solution Approach 2:
The patent adds a third dimension to the load state management by introducing the deleted state. This transforms the traditional binary state system into a ternary system, providing additional information about the lifecycle status of load objects. The third state dimension enables differentiation between objects that were never integrated versus those that were previously integrated but have since been deleted.
2Ease of operation
If symbolic or graphical reverse translation information is not available for online testing, then debugging capabilities are restricted, but maintaining system simplicity is preserved
Solution Approach 1:
The patent applies preliminary action by maintaining and storing symbolic and graphical reverse translation information in the automation system even after the original programming elements have been deleted. This allows commissioning engineers to perform online testing and debugging using the preserved translation information, without needing to recreate or reload the original program elements.
Solution Approach 2:
The patent creates a copy of the essential translation information (symbolic and graphical representations) that can be used for online testing independently of the original load objects. This copying mechanism allows debugging operations to proceed using preserved information rather than requiring the original programming elements to be present.
3Ease of operation
If deleted modules are not adequately visualized, then debugging options are lost, but the graphical interface remains simpler
Solution Approach 1:
The patent employs color changes in the graphical representation to indicate different load states of modules. Deleted modules are visually distinguished through specific color coding, allowing commissioning engineers to quickly identify which modules have been deleted while maintaining their visibility in the graphical interface. This visual differentiation preserves debugging capabilities without significantly increasing interface complexity.
Data Source
AI summary
A method for operation of an automation system is specified, with programming elements for integration into a control program provided for the control and/or monitoring of a technical process being transferred or being able to be transferred from a programming device included at least part of the time in the automation system to at least one automation device included in the automation system, with a program element being assigned a first state which identifies this element as available for the control program or a second state which identifies the program element as integrated into the control program, in which there is provision for each program element to be assigned or be able to be assigned at least one further state, so that this state, especially for program modifications, when program elements have been deleted for example, enables the option of testing (debugging) the control program at any time to be maintained.