PLC CPU Unit Dynamic Scheduling via Data Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current PLC systems lack the flexibility in scheduling control actions, requiring users to choose from predefined patterns and adjust parameters, which limits customization and increases management burdens, as changing the schedule pattern often necessitates replacing system programs, making it difficult for users to find optimal configurations for specific control purposes.
Innovation Solution
A PLC CPU unit with a microprocessor, storage section, and communication circuit that includes a system program with a procedure library and schedule-building data to execute control programs, allowing users to specify execution order and generate threads, enabling flexible scheduling without replacing system programs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users want to customize scheduling patterns for control actions, then adaptability improves, but system complexity increases because it requires replacing system programs
Solution Approach 1:
The patent divides the scheduling configuration into separate data files (schedule definition files) that are independent from the system program. Users can customize scheduling patterns by modifying these data files rather than replacing the entire system program, thus segmenting the configuration from the core system and reducing complexity.
Solution Approach 2:
The patent uses data files as copies or representations of scheduling configurations that can be easily modified and loaded without changing the system program itself. These data files serve as lightweight copies of the scheduling logic, allowing customization without the overhead of program replacement.
2Ease of operation
If predefined scheduling patterns are used, then ease of operation improves, but adaptability deteriorates due to limited customization options
Solution Approach 1:
The patent implements a dynamic scheduling system where the configuration can be changed by loading different data files at runtime. The system transitions from static predefined patterns to dynamic customizable schedules, allowing users to adapt the scheduling behavior to specific needs while maintaining ease of operation through file-based configuration.
Solution Approach 2:
The patent allows customization of scheduling parameters by modifying data in external files rather than changing the system program structure. Users can adjust timing, sequence, and other scheduling parameters by editing data files, enabling flexible adaptation while keeping the system program intact and easy to operate.
3Adaptability or versatility
If system programs are replaced to change schedule patterns, then adaptability improves, but loss of time increases due to replacement and reconfiguration
Solution Approach 1:
The patent allows scheduling configurations to be prepared in advance as data files without requiring system program replacement. Users can create and store multiple schedule definition files beforehand, and simply load the appropriate file when needed, eliminating the time-consuming process of program replacement and reconfiguration.
Solution Approach 2:
Instead of replacing the system program, the patent uses data files as copies of scheduling configurations that can be quickly swapped and loaded. This approach reduces reconfiguration time significantly compared to full program replacement, as only lightweight data files need to be transferred and loaded rather than entire system programs.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system program includes a procedure library in which at least a procedure for controlling execution of a control program and a procedure for controlling output of output data and input of input data are included. If schedule-building data including execution order specifications for the procedures included in the procedure library is stored in a storage section, the system program causes a microprocessor to execute the procedures included in the procedure library in accordance with the procedure execution order specifications included in schedule-building data.