Zone Controller System Global Backbone Network
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conveyor systems face limitations in data communication between zone controllers, leading to restricted data exchange, resource consumption, and lag times, especially as the number of zones increases, and existing zone controllers lack reprogramming capabilities and network connectivity for monitoring or updating.
Innovation Solution
A zone controller system with global communication networks allowing all controllers to share inputs, outputs, and states, enabling intelligent decision-making, and incorporating self-repair functionality through direct one-to-one communications and programmable logic equations, along with off-board configuration tools for easy setup and automatic recognition of new controllers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If daisy-chained serial communication is used between zone controllers, then data can be shared between controllers, but lag times increase and real-time data messaging cannot be achieved as the number of zones increases
Solution Approach 1:
The communication network is segmented into a hierarchical structure with a backbone network connecting all zone controllers directly, rather than using a single daisy-chain path. This allows data to be transmitted through multiple parallel paths simultaneously, reducing lag time and enabling real-time messaging across the entire conveyor system.
Solution Approach 2:
The communication architecture transitions from a one-dimensional daisy-chain topology to a two-dimensional mesh-like network topology. This dimensional change allows data to flow through multiple routes and dimensions, eliminating the sequential bottleneck and enabling simultaneous data exchange between any zone controllers.
2Productivity
If the number of conveyor zones increases, then the conveyor system can handle more payloads and functions, but the number of data messages to pass through each zone controller increases dramatically, consuming zone controller resources
Solution Approach 1:
A backbone communication network acts as an intermediary layer between zone controllers, handling the transmission of data messages between zones. This relieves zone controllers from the burden of routing messages through multiple adjacent controllers, reducing their resource consumption while enabling the system to scale to handle more payloads and functions.
3Reliability
If hardware inputs and outputs are used for signaling between adjacent controllers, then individual wiring provides direct communication, but the data that can be communicated is greatly restricted and assembly is expensive and time-consuming
Solution Approach 1:
The backbone communication network provides a universal communication interface that can transmit multiple types of data (control signals, status information, diagnostic data) through a single network infrastructure. This eliminates the need for separate hardware wiring for each data type while maintaining reliable direct communication between all zone controllers, significantly reducing assembly complexity and cost.
Data Source
AI summary
A zone controller system that includes global communication of inputs, outputs and controller states from all zone controllers allowing each zone controller to operate based on inputs, outputs and controller states from all other zones. The zone controller system may also include direct one-to-one communication connections that allow additional communications. The system may include a user interface to configure operation of the zone controllers utilizing programmable logic equations that may use as variables the inputs, outputs and controller states of any zone controller. The user interface may be implemented in an off board configuration tool that is run on a computer connected to the global network. The system may also utilize one-to-one communications connections to provide self-repair and auto-configuration features. Each zone controller may store its ID(s) and configuration parameters on two other zone controllers, where they can be recovered for self-repair and auto-configuration.