Native Project Documentation Storage in Industrial Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial controllers lack the ability to natively store project documentation, leading to inconsistencies and difficulties in diagnostics, as documentation is typically separated from executable code, making it challenging for multiple users to access and update project files simultaneously.
Innovation Solution
The industrial controller is configured to store project documentation natively within its memory, allowing individual components to be accessed directly, and notifications of changes can be sent to connected devices, ensuring that project files remain current across multiple computers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If project documentation is stored separately from executable code in conventional controllers, then code execution efficiency is maintained, but documentation accessibility and consistency deteriorate
Solution Approach 1:
The patent merges project documentation and executable code into a single native project file stored within the controller. This integration ensures that documentation and code remain synchronized, eliminating consistency issues while maintaining straightforward access through the unified file structure.
Solution Approach 2:
The native project file serves multiple functions simultaneously: it stores executable code, contains project documentation, and acts as a single source of truth for both programmers and the controller. This multi-functionality eliminates the need for separate documentation files and complex synchronization mechanisms.
2Adaptability or versatility
If project files are updated on multiple computers, then collaboration is enabled, but consistency and synchronization become problematic
Solution Approach 1:
The system implements a feedback mechanism where the controller reads the native project file and executes code while maintaining an up-to-date understanding of the current project state. This feedback loop ensures that when multiple users work on the project, changes are properly reflected in the controller's execution environment.
Solution Approach 2:
The native project file acts as an intermediary between multiple programmers and the controller. All users work with the same file format, and the controller serves as the central authority that executes the code and maintains the authoritative version, preventing synchronization conflicts.
3Ease of operation
If documentation is uploaded from controller to personal computer, then external access is enabled, but descriptive information is lost
Solution Approach 1:
The system creates accurate copies of the native project file containing both executable code and documentation. When programmers need to work with documentation externally, they can copy the entire native project file to their computers, ensuring all descriptive information is preserved without loss.
Solution Approach 2:
The native project file is structured to allow selective extraction of documentation components while maintaining the integrity of the whole. Programmers can access specific documentation sections as needed while the complete file remains available for full project reference.
4Ease of manufacture
If descriptive text is retained only in project files on personal computers, then documentation is easily edited, but controller diagnostics become difficult
Solution Approach 1:
The controller is equipped with the capability to read and interpret the native project file format directly. This self-service capability allows the controller to access its own documentation and code without external assistance, enabling effective diagnostics and troubleshooting directly at the controller level.
Solution Approach 2:
The system changes the parameter of documentation storage from external-only (personal computers) to internal-capable (controller native storage). This parameter change enables the controller to directly access and process documentation, facilitating diagnostics while programmers retain full editing capabilities through the same native file format.
Data Source
AI summary
An industrial controller comprises a processing component and a memory that comprises logic code that is executable by the processing component. The memory further comprises documentation associated with the logic code and other control components, wherein the documentation is stored in a native form to enable individualized access to a portion of the documentation to an accessing entity. For example, the documentation can comprise one or more of descriptive text relating to a rung of ladder logic, a text box associated with a portion of the sequential function chart, a text box associated with a function block diagram, and embedded descriptive text within structured text.