PLC Queue Blocks for Flexible Cross-Platform Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automation engineering programs are inflexible and require significant redesign and validation efforts whenever changes occur in hardware or software, limiting data exchange efficiency between programmable logic controllers (PLCs) and other applications.
Innovation Solution
The introduction of a queue block (QB) in PLC programming, which acts as an interchangeable data type to dynamically exchange data between PLCs and other data consumers, decoupling execution from communication and enabling flexible allocation to various hardware configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If automation engineering programs use traditional PLC-specific Function Blocks and Data Blocks, then data exchange between PLCs requires complex mapping and integration efforts, but the system maintains strict adherence to PLC vendor standards
Solution Approach 1:
The patent introduces a queue block as an intermediary data structure that sits between traditional PLC data blocks and external data consumers. This queue block enables standardized data exchange interfaces while maintaining compatibility with existing PLC-specific Function Blocks, thereby reducing integration complexity without sacrificing adaptability
Solution Approach 2:
The queue block is designed as a universal data structure that can interface with multiple different PLC vendors' standards and protocols simultaneously. It provides a common data exchange mechanism that works across different PLC platforms, eliminating the need for separate mapping efforts for each vendor
2Reliability
If automation programs are tightly coupled with specific hardware configurations, then PLC programs can be executed reliably on designated hardware, but any hardware changes trigger complete redesign and validation
Solution Approach 1:
The patent segments the automation program into distinct functional components: traditional PLC Function Blocks that maintain reliability, queue blocks that provide hardware-agnostic data buffering, and data consumers that handle external communications. This segmentation allows hardware changes in one segment without affecting the core execution logic in other segments
Solution Approach 2:
The queue block introduces dynamic data buffering that can adapt to different hardware configurations at runtime. Instead of static hardware-dependent data structures, the queue block dynamically manages data flow between PLCs and external systems, allowing hardware changes without program redesign
3Productivity
If data exchange between PLCs uses traditional communication protocols, then data can be transmitted between controllers, but the system requires project-specific mapping that is not reusable
Solution Approach 1:
The queue block uses standardized data parameters and data structures that can be configured for different projects without changing the fundamental communication mechanism. This allows the same queue block implementation to be reused across multiple projects with different PLC vendors and protocols, simply by changing configuration parameters rather than rewriting integration code
Data Source
AI summary
A system for exchanging data in an automation environment is provided. The system includes at least one programmable logic controller (PLC A) containing program instructions executable by the at least one programmable logic controller and a queue block (50) configured to dynamically exchange data between the program instructions of the PLC and a data consumer (PLC C, PLC D).