Redundant Process Controller with Legacy Protocol Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial process control and automation systems face challenges in upgrading controllers while maintaining compatibility with legacy technology, especially in distributed control systems requiring 1:1 redundancy, where upgraded controllers need to seamlessly integrate with legacy controllers without disrupting system availability.
Innovation Solution
The implementation of a modern controller with a microprocessor supporting communication, control execution, and I/O functions, configured for both Ethernet and RTBC protocols, capable of detecting legacy partners and switching protocols accordingly, and designed for integration into legacy systems, ensuring compatibility and seamless operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a modern controller is upgraded in a distributed control system, then system performance and capabilities are improved, but compatibility with legacy controllers becomes problematic
Solution Approach 1:
The controller dynamically adapts its communication protocol based on the operational mode. In legacy mode, it uses RTBC protocols to communicate with legacy controllers, while in modern mode, it uses Ethernet protocols for enhanced performance. This dynamic adaptation resolves the contradiction by allowing the system to switch between compatibility and performance modes as needed.
Solution Approach 2:
The controller changes its communication parameters (protocol type) depending on the operational context. By configurable parameters, the same hardware platform can operate with different communication stacks, enabling both legacy compatibility and modern high-performance operations without physical hardware changes.
2Adaptability or versatility
If protocol switching is implemented for legacy compatibility, then compatibility is improved, but communication complexity increases
Solution Approach 1:
The controller is designed as a universal platform that can perform multiple communication functions through a single integrated architecture. The same communication module handles both RTBC and Ethernet protocols, eliminating the need for separate dedicated hardware for each protocol and reducing overall system complexity despite multi-protocol support.
Solution Approach 2:
The communication module acts as an intermediary that translates between different protocol requirements. It provides a unified interface that mediates between the control logic and the varying communication protocols, simplifying the integration of multiple protocol support without increasing controller complexity.
3Device complexity
If a single microprocessor supports multiple functions, then device complexity is reduced, but functional reliability may be compromised
Solution Approach 1:
The single microprocessor is logically segmented into distinct functional modules through software partitioning. Each module (communication module, control execution module, I/O module) operates independently with dedicated resources and failure isolation mechanisms. This allows the system to maintain reduced hardware complexity while achieving functional reliability through software-based separation of concerns.
Solution Approach 2:
The system implements error detection, correction, and recovery mechanisms beforehand to cushion against potential failures. The communication module includes built-in error handling that can detect and recover from communication errors before they propagate to critical control functions, maintaining reliability despite the use of a single microprocessor.
Data Source
AI summary
A apparatus having a control network and a first controller comprising a microprocessor configured to support communication functions, control execution functions, I/O functions, and control network interface functions, a second controller configured as a redundant partner to the first controller, and an I/O link and I/O modules.