Programmable Controller Cycle Synchronization Across Dual Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large-scale programmable controller systems, synchronizing the cycle timings between controller-level and device-level networks is challenging, leading to data synchronization issues and accuracy problems, which affect the accuracy of data collection and preventive maintenance in systems like metal rolling processing.
Innovation Solution
A programmable controller system with a specific controller that generates a first cycle start timing based on a second cycle start timing, and other controllers synchronize their first cycle start timings with this specific controller, while also correcting their second cycle start timings, using a first cycle synchronization unit and a second cycle correction unit to adjust timings and prevent data omission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If controllers operate independently with their own cycle timings, then each controller can function autonomously, but data synchronization accuracy deteriorates and data omission occurs
Solution Approach 1:
A master station is introduced as an intermediary to coordinate timing between controllers. The master station generates master cycle timings and transmits them to slave stations, which then synchronize their operation timings based on these master timings. This intermediary mechanism resolves the timing coordination problem without requiring complex peer-to-peer synchronization between all controllers.
Solution Approach 2:
Slave stations receive master cycle timings from the master station and adjust their operation timings accordingly. The system implements a feedback mechanism where timing information flows from the master station to slave stations, enabling slave stations to correct their timing deviations and maintain synchronized operation across the distributed control system.
2Measurement precision
If the controller-level network operates at a longer cycle than the device-level network, then management functions are simplified, but data collection accuracy deteriorates due to timing mismatches
Solution Approach 1:
The control system is segmented into two distinct timing domains: device-level network timing for high-speed data collection and control, and controller-level network timing for management functions. Each domain operates with its own optimized cycle time, allowing the device-level network to maintain high-speed operations while the controller-level network operates at a slower, more manageable pace for monitoring and coordination.
Solution Approach 2:
The master station acts as a mediator that coordinates between the two different timing domains. It generates master cycle timings that serve as reference points for both device-level and controller-level operations, enabling accurate data collection at device level while maintaining simplified management at controller level through the intermediary timing coordination.
3Adaptability or versatility
If multiple controllers are distributed across different locations, then system scalability is improved, but timing synchronization becomes more difficult and data omission increases
Solution Approach 1:
The master station serves as a central intermediary that distributes timing information to all slave stations regardless of their physical locations. This intermediary approach allows controllers to be distributed across different locations while maintaining timing synchronization through the master station's coordination, enabling system scalability without compromising timing reliability.
Solution Approach 2:
Slave stations continuously receive timing corrections from the master station through the network, implementing feedback-based timing synchronization. This feedback mechanism ensures that even as controllers are added or relocated in the distributed system, all stations can maintain synchronized timing by adjusting based on the master station's timing signals.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A specific controller 150 includes a first cycle generation unit 151 that determines a first cycle start timing of itself on the basis of a second cycle start timing of itself. Different controllers 160 each have a first cycle synchronization unit 161, a second cycle correction unit 162, etc. The first cycle synchronization unit 161 synchronizes the first cycle start timing of itself with a first cycle start timing of the specific controller 150. The second cycle correction unit 162 synchronizes a second cycle start timing of the specific controller 150 with a second cycle start timing of itself by correcting the second cycle start timing of itself.