Field Bus Device Configuration via Active Protocol Query
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for configuring a new device connected to a field bus are time-consuming and unreliable, as they require network sniffing to determine the used protocols, which increases boot-up time and is complex to implement, especially at OSI layers 2 and 4.
Innovation Solution
A method where a new device sends a broadcast message requesting protocol information, and a first device responds with a configuration message listing the used protocols, allowing the new device to quickly and reliably identify the protocols without needing to sniff the network, using basic Ethernet functionality and UDP protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network sniffing is used to determine the field bus protocol, then the new device can identify the used protocols, but the boot-up time increases and the implementation becomes complex
Solution Approach 1:
Instead of passively sniffing the network to detect protocols (traditional approach), the invention inverts the approach by actively querying other devices for protocol information. The new device sends a broadcast message asking 'What protocol are you using?' rather than listening and analyzing traffic to figure it out. This active inquiry method is both faster and more reliable than passive detection.
Solution Approach 2:
The invention introduces an intermediary mechanism - a standardized query/response message system - that facilitates protocol information exchange. Rather than directly analyzing network traffic or relying on complex sniffing, devices use a mediator message format to request and provide protocol information, simplifying the implementation while maintaining reliability.
2Reliability
If network sniffing at OSI layer 2 is used to determine the field bus protocol, then the new device can identify the used protocols, but the implementation complexity increases
Solution Approach 1:
The invention replaces the mechanical/complex system of packet sniffing and analysis at OSI layer 2 with a simpler information exchange mechanism using standardized messages. Instead of implementing complex network traffic capture and analysis logic, devices simply send and process configuration request/response messages, dramatically reducing implementation complexity while maintaining protocol identification reliability.
Solution Approach 2:
The existing devices on the field bus already possess and maintain knowledge of their protocol configurations. Rather than requiring the new device to figure this out through complex sniffing, the existing devices self-service by directly providing their protocol information through configuration responses, simplifying the overall system complexity.
3Adaptability or versatility
If all field bus protocols are activated simultaneously, then the new device can communicate with any device, but technical constraints prevent this
Solution Approach 1:
The invention applies preliminary action by having devices pre-configure their protocol information and make it available through standardized messages. Rather than attempting to activate all protocols simultaneously (which is technically constrained) or requiring complex runtime protocol detection, the protocol information is prepared in advance and exchanged during the configuration phase, enabling adaptability without excessive complexity.
Data Source
AI summary
The invention relates to a method for configuring a device connected to a field bus, comprising:providing a field bus which is based on an Ethernet network,providing a first device connected to the field bus,transmitting a broadcast message from the new device over the field bus, wherein the broadcast message requests information about a field bus protocol used on the field bus and/or to be used by the new device,sending a configuration response in response to the broadcast message from the first device to the new device, wherein the configuration response comprises information at least about a field bus protocol used on the field bus and/or to be used by the new device.