Controller Module Cascade Configuration via Data Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cascade control systems in industrial automation face issues such as the 'wind-up effect' and separation of controller cascades due to extreme integral component values and alternative setpoints, requiring complex programming and additional logic to manage, which increases programming effort and specialist knowledge.
Innovation Solution
A universal interface with two transit parameters for exchanging information between master and slave controllers, allowing configuration as master, slave, or both, with a data interface for control value limits, operating modes, and setpoint types, simplifying the programming of controller cascades and reducing the need for multiple connections and additional logic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If additional logic and interconnections are added to the program code to detect and handle wind-up cases, then control reliability is improved, but device complexity increases
Solution Approach 1:
The follower controller automatically detects when it is in a wind-up case through self-diagnosis of its own operating state, and autonomously communicates this information to the master controller via the data interface. This eliminates the need for the master controller to implement complex detection logic, as the follower controller serves itself by providing the necessary status information.
Solution Approach 2:
The data interface establishes a feedback mechanism where the follower controller sends information about its operating mode and setpoint usage to the master controller. This feedback allows the master controller to automatically adjust its integral component behavior without requiring complex detection logic, resolving the contradiction between reliability and complexity.
2Productivity
If multiple connections and additional logic are implemented to manage cascade control issues, then control performance is improved, but programming effort increases
Solution Approach 1:
The data interface is designed as a universal communication channel that handles multiple functions: exchanging information about operating modes, setpoint usage, and wind-up detection. This single multi-functional interface replaces the need for multiple specialized connections and logic blocks, improving control performance while reducing programming effort.
Solution Approach 2:
The patent combines multiple information exchange requirements into a single data interface structure. Instead of implementing separate connections for operating mode detection, setpoint tracking, and wind-up prevention, these functions are merged into one integrated communication protocol between master and follower controllers.
3Measurement precision
If the master controller continuously adjusts the integral component to compensate for control errors, then setpoint accuracy is improved, but system stability deteriorates due to wind-up effect
Solution Approach 1:
The follower controller proactively identifies wind-up conditions before they severely impact system stability by monitoring its own operating state. It communicates this preliminary warning to the master controller, which can then preemptively adjust or pause integral component adjustment, preventing the stability deterioration that would otherwise occur from continuous integral wind-up.
Solution Approach 2:
The system performs preliminary detection of wind-up cases through the data interface communication mechanism. By detecting the follower controller's operating mode and setpoint usage status in advance, the master controller can take preliminary corrective action on the integral component before the wind-up effect fully develops and compromises system stability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a controller module (PID_Temp_1, PID_Temp_2, PID_Temp_3) for use in an industrial automation arrangement, wherein the controller module (PID_Temp_1, PID_Temp_2, PID_Temp_3) is configured for use with a number of similar or essentially functionally identical controller modules (PID_Temp_1, PID_Temp_2, PID_Temp_3) in a cascaded control system, and wherein the controller module (PID_Temp_1, PID_Temp_2, PID_Temp_3) can be configured optionally as a master controller, as a follower controller, or as a master and follower controller in conjunction with other controllers of the cascaded control system. The controller module (PID_Temp_1, PID_Temp_2, PID_Temp_3) has a data interface for communication with other controller modules (PID_Temp_1, PID_Temp_2, PID_Temp_3), whereby the data interface is set up at least for the exchange of information about a control value limit and a current operating mode at runtime of the control.This solution, with a data interface and only one connection for information exchange between the master controller and the follower controller, is simpler for the user than previously existing solutions, where multiple connections and, depending on the product used, additional logic also had to be programmed.