Conveyor Controller Data Synchronization via Version Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conveyor systems lack efficient and robust data synchronization between controllers, leading to inefficiencies and the need for human intervention during events like stoppages, which can cause queue buildup and require labor-intensive rebalancing of workstations.
Innovation Solution
A conveyor system controller that uses heartbeat data packets to compare version identifiers and synchronize data entries between controllers, allowing for automatic data synchronization without a central master, enabling efficient communication and reduced human intervention through a standardized serial bus.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a central controller is used to coordinate work stations and synchronize data, then system control and data synchronization can be achieved, but system complexity increases and human intervention is required for rebalancing during stoppages
Solution Approach 1:
Each conveyor system controller autonomously performs data synchronization with neighboring controllers by comparing version identifiers and exchanging data packets without requiring a central controller. The system self-organizes and self-synchronizes, eliminating the need for centralized coordination and reducing overall system complexity.
Solution Approach 2:
The centralized control function is segmented and distributed to individual conveyor system controllers. Each controller independently manages its own data synchronization with adjacent controllers, breaking down the monolithic central controller into multiple autonomous units that collectively achieve system-wide synchronization.
2Productivity
If data synchronization is performed between controllers during stoppages, then queue buildup can be avoided and system rebalancing is improved, but communication overhead and data transmission requirements increase
Solution Approach 1:
Controllers exchange only the necessary data elements for synchronization - specifically version identifiers in heartbeat packets and only updated data entries in synchronizing packets. This partial data exchange approach achieves effective synchronization while minimizing communication overhead and energy consumption compared to transmitting complete data sets.
Solution Approach 2:
Controllers periodically exchange heartbeat data packets containing version identifiers to detect data inconsistencies. This periodic checking mechanism enables timely detection of synchronization needs without continuous data transmission, reducing communication overhead while maintaining system efficiency.
3Extent of automation
If heartbeat data packets with version identifiers are exchanged between controllers, then automatic data synchronization can be achieved, but data packet transmission frequency and communication activity increase
Solution Approach 1:
Controllers pre-exchange version identifiers through periodic heartbeat packets before actual data synchronization is needed. This preliminary action allows controllers to detect data inconsistencies in advance and only initiate full data synchronization when necessary, reducing unnecessary communication time while maintaining automatic synchronization.
4Reliability
If controllers autonomously synchronize data without a central master, then system robustness and efficiency are improved, but data consistency management becomes more complex
Solution Approach 1:
Each controller independently manages its own data consistency by comparing version identifiers received from neighboring controllers. This local quality approach allows each controller to autonomously determine whether its data is current and initiate synchronization only when needed, simplifying data consistency management while maintaining system robustness.
Solution Approach 2:
Controllers use version identifiers as feedback mechanisms to detect data inconsistencies. When a controller receives a heartbeat packet with a newer version identifier, it triggers automatic data synchronization. This feedback-driven approach simplifies autonomous data consistency management while improving system robustness.
Data Source
Figure 1~2
Figure 3~4a
Figure 4b~4c
AI summary
The present disclosure provides a conveyor system controller (11, 12, 13, 14), comprising: a data storage unit (101) configured to store a plurality of data entries, each data entry comprising a data entry ID, a data entry version identifier, and a data payload representing operating information of the controller or another controller; a processing unit (102); a first interface (103) for communicating with another controller. The controller is configured to transmit a first data packet comprising data entry ID and data entry version identifier of a data entry in the data storage unit, to other controllers; and to receive a second data packet transmitted by said another controller, the second data packet comprising data entry ID and data entry version identifier of a data entry of said another controller; and compare the received data entry version identifier of the second data packet, with a data entry version identifier of a corresponding data entry in the data storage unit having a same data entry ID as the second data packet.