Hardware Module Fieldbus Communication via Network Module Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for connecting hardware modules to fieldbus systems require significant adaptation and verification for each different fieldbus system, leading to increased development, production, and storage costs, especially in safety-relevant applications where multiple communication protocols and fieldbus systems are involved.
Innovation Solution
A method where the hardware module reads and stores communication software from a network module, allowing it to communicate via various fieldbus systems, enabling flexible use and reducing the need for specific fieldbus-dependent hardware designs, and allowing existing hardware modules to be adapted to future fieldbus systems by swapping network modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hardware modules are specially adapted to each fieldbus system, then communication compatibility is improved, but device complexity and production costs increase
Solution Approach 1:
The system is divided into two independent parts: a fieldbus-independent hardware module and a fieldbus-specific network module. The hardware module contains only the fieldbus-independent communication hardware, while the network module contains the fieldbus-specific communication software and protocols. This segmentation allows the hardware module to remain simple and universal, while the network module handles the complexity of different fieldbus systems.
Solution Approach 2:
The hardware module is designed to be universal and fieldbus-independent, capable of working with multiple fieldbus systems through different network modules. The network module acts as an adapter that provides fieldbus-specific functionality, allowing the same hardware module to communicate with various fieldbus systems (PROFIBUS, PROFIsafe, EtherCAT, etc.) without modification.
2Reliability
If verification and qualification are performed for each fieldbus system, then safety compliance is improved, but time and cost increase
Solution Approach 1:
The verification and qualification process is segmented into two parts: the hardware module requires verification only once for its fieldbus-independent communication function, while the network module requires verification for each specific fieldbus system. This allows the hardware module to be verified a single time, avoiding repeated verification for different fieldbus systems.
Solution Approach 2:
The hardware module is pre-verified and qualified for its fieldbus-independent communication functionality before being paired with specific network modules. This preliminary verification eliminates the need to repeat the entire verification process when connecting to different fieldbus systems, as only the network module needs to be verified for its fieldbus-specific protocols.
3Ease of operation
If communication software is stored in the hardware module, then communication capability is improved, but adaptability to different fieldbuses decreases
Solution Approach 1:
The fieldbus-specific communication software is extracted from the hardware module and placed in the network module. The hardware module retains only the fieldbus-independent communication hardware and basic processing capabilities, while the network module contains the fieldbus-specific protocols and communication software. This extraction allows the hardware module to remain flexible and adaptable to different fieldbus systems.
Solution Approach 2:
The network module acts as an intermediary between the fieldbus-independent hardware module and the fieldbus-specific communication protocols. It translates and adapts the generic communication requests from the hardware module into fieldbus-specific protocols, enabling the hardware module to communicate with different fieldbus systems without containing fieldbus-specific software.
4Reliability
If network modules are specially adapted to hardware modules, then communication performance is improved, but production efficiency decreases
Solution Approach 1:
The system is manufactured in two independent parts: standardized hardware modules and fieldbus-specific network modules. The hardware modules are produced in large quantities using standardized processes, while the network modules are produced separately for specific fieldbus systems. This segmentation allows both components to be manufactured independently and efficiently, then assembled together.
Solution Approach 2:
The hardware module is designed as a universal platform that can work with multiple types of network modules for different fieldbus systems. This universality allows the hardware module to be produced once and used with various network modules, improving production efficiency while maintaining communication performance through specialized network modules.
Data Source
Figure 1
Figure 2
AI summary
The method involves establishing data connection between a hardware module (14) and a field-bus (26) by a network module (12) connected to a field-bus. The hardware module is coupled to the network module. The communication software is read out from the memory (18) of the network module by the hardware module and communication software is provided for the communication of the hardware module with the field-bus. The communication software is stored in the hardware module to communicate over the field-bus. Independent claims are included for the following: (1) network module; and (2) modular system.