Universal Safety I/O Module for Multi-Protocol Automation Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional industrial control systems face limitations in seamlessly integrating and transferring both safety and non-safety data across multiple protocols within a single control architecture, leading to barriers in automation architecture and requiring complex bridging devices.
Innovation Solution
A universal safety block and modular non-safety I/O components facilitate the communication and processing of safety and non-safety data using industrial automation protocols, allowing data to be identified and processed accordingly, ensuring compliance with safety standards and enabling flexible machine control architectures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If safety and non-safety data are kept separate in different networks, then safety signal integrity is maintained, but device complexity and architecture complexity increase
Solution Approach 1:
The patent combines safety and non-safety data transmission into a single control network by integrating a safety I/O module within the control network architecture. The module receives both safety and non-safety data packets, processes them through identical protocol handling, and transmits them over the same network infrastructure, eliminating the need for separate safety networks while maintaining signal integrity through protocol-level separation and processing.
Solution Approach 2:
The control network is designed with universal protocol handling capabilities that can process both safety and non-safety data packets through the same communication infrastructure. The safety I/O module and network interface are configured to handle multiple data types and protocols simultaneously, allowing a single network to serve multiple functions without compromising safety signal integrity.
2Adaptability or versatility
If conventional protocols are used for data transmission, then communication is limited to certain layers, but device complexity is reduced
Solution Approach 1:
The control network implements a universal protocol stack that can handle multiple industrial communication protocols (DeviceNet, ControlNet, EtherNet/IP, Profibus) through a single network interface and processing architecture. The safety I/O module and network interface are configured to translate and process different protocols at the application layer without requiring separate physical networks or complex bridging devices, enabling seamless multi-protocol communication across all automation pyramid layers.
3Speed
If safety data is transmitted through automated intelligence systems, then response time is improved, but risk of signal integrity loss increases
Solution Approach 1:
The safety I/O module implements feedback mechanisms including message redundancy and cross-checking protocols. Safety data packets are transmitted with redundant information and acknowledgment signals, allowing the receiving device to verify signal integrity and request retransmission if errors are detected. This feedback system maintains high-speed automated response while ensuring signal integrity through continuous verification.
Solution Approach 2:
The system incorporates error detection and correction codes in safety data packets before transmission, along with predetermined timeout mechanisms and fallback procedures. These preemptive measures cushion against potential signal integrity loss by preparing correction mechanisms in advance, allowing the system to maintain rapid response times while protecting against data corruption through pre-configured safety margins.
Data Source
AI summary
A safety control block interfaces to one or more devices utilizing one or more communication protocols wherein a network interface receives and/or transmits data directly from a network. A backplane interface receives and/or transmits data from a backplane. A backplane extension receives and/or transmits data from a backplane. A processing component receives data from at least one of the network interface, backplane interface and backplane extension and determines if the received data is related to safety or non-safety. A safety I/O circuitry receives safety data from the processing component; wherein the safety data is utilized to communicate to at least one control device.