Redundant Process Controller with Legacy Protocol Synchronization
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 where upgraded controllers need to work in harmony with legacy controllers for redundancy and continuous system availability.
Innovation Solution
The implementation of a modern controller with a single microprocessor supporting communication, control execution, and I/O functions, configured to operate with both Ethernet and RTBC protocols, and capable of detecting and synchronizing with legacy controllers, allowing seamless integration and operation within existing legacy systems.
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 switching resolves the contradiction by allowing the system to optimize performance when possible while maintaining backward compatibility when needed.
Solution Approach 2:
The modern controller is designed with multi-functionality to support both legacy RTBC protocols and modern Ethernet protocols simultaneously. This universal capability allows it to interface with both legacy and modern controllers, resolving the compatibility issue while maintaining improved performance capabilities when operating in modern mode with other modern controllers.
2Speed
If Ethernet protocols are used for communication between controllers, then communication speed and modern capabilities are improved, but compatibility with legacy RTBC protocol controllers is lost
Solution Approach 1:
The controller dynamically selects the communication protocol based on the operational mode and the type of controller it needs to communicate with. When operating in legacy mode with RTBC controllers, it uses RTBC protocols. When operating in modern mode with other Ethernet-capable controllers, it uses Ethernet protocols for faster communication. This dynamic adaptation resolves the speed- compatibility contradiction.
Solution Approach 2:
The controller acts as an intermediary that can translate between RTBC and Ethernet protocols. When a modern controller needs to communicate with a legacy RTBC controller, the protocol translation capability enables compatibility without sacrificing the modern Ethernet capabilities when communicating with other modern controllers.
3Reliability
If legacy controllers are replaced with modern controllers, then system reliability and support are improved, but integration with existing legacy systems becomes complex
Solution Approach 1:
The modern controller is designed with universal compatibility to support both legacy RTBC protocols and modern Ethernet protocols. This multi-functionality allows seamless integration into existing legacy systems without requiring complete system replacement, thereby improving reliability while maintaining simple integration through a single controller type that handles both protocol modes.
Solution Approach 2:
The controller can dynamically switch between operational modes (legacy and modern) depending on the system configuration and communication requirements. This dynamic capability simplifies integration by allowing the modern controller to adapt to the existing system environment, reducing the complexity of integration while maintaining improved reliability through modern hardware and support.
4Device complexity
If a single microprocessor is used in the modern controller, then device complexity is reduced, but the ability to handle multiple protocols and functions simultaneously becomes challenging
Solution Approach 1:
The controller merges multiple functions (RTBC protocol handling, Ethernet protocol handling, control execution, and I/O processing) into a single microprocessor. This consolidation reduces device complexity by eliminating the need for separate microprocessors for each function while maintaining full multi-protocol support through software-based protocol stacks and intelligent task management within the single processor.
Data Source
Figure 1
Figure 2
Figure 3
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.