Fieldbus Interface Module With Virtual Address Configuration Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fieldbus systems lack a simple, flexible, and efficient method for configuring and parameterizing peripheral systems without a Profinet controller, as configuration information is not inherently stored during connection establishment in non-Profinet environments like EtherNet/IP or Modbus TCP/IP.
Innovation Solution
An interface module with a connection for a fieldbus, module slots for sensors/actuators, a configuration memory for logical addresses, and a firmware infrastructure for establishing Profinet connections, including detection and transformation means to handle virtual addresses, allowing for persistent storage and conversion of configuration files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fieldbus system uses non-Profinet protocols (EtherNet/IP or Modbus TCP/IP) for connection establishment, then the system can operate without a Profinet controller, but the configuration information is not inherently stored during connection establishment
Solution Approach 1:
The patent applies preliminary action by pre-configuring virtual addresses in the configuration memory before actual physical connections are established. The system prepares virtual address assignments in advance, which are then mapped to physical addresses during runtime, ensuring configuration information is preserved even when using non-Profinet protocols that don't inherently store such data during connection establishment.
2Ease of manufacture
If virtual addresses are used in configuration files for fieldbus participants, then the configuration can be stored and transformed, but additional detection and transformation means are required to handle virtual addresses
Solution Approach 1:
The patent introduces virtual addresses as an intermediary layer between the configuration storage and physical device addresses. The detection means identifies virtual addresses in received configuration files, and the inverse transformation means converts them to physical addresses. This intermediary mechanism simplifies configuration storage while managing the added complexity through a systematic address translation process.
3Reliability
If the interface module stores configuration files with virtual addresses in configuration memory, then the configuration persists after power failure, but the module requires initialization means to transform virtual addresses to real logical addresses after restart
Solution Approach 1:
The system performs preliminary action by storing configuration files with virtual addresses in configuration memory before power failure occurs. After restart, the initialization means automatically detects these virtual addresses and transforms them to real logical addresses, minimizing initialization time by having the transformation logic pre-prepared and automatically executed upon system restart.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
To facilitate the configuration and parameterization of a fieldbus participant (Dev), it is proposed to transform logical addresses (lAdr) on the side of an engineering system (ES) to virtual addresses (vAdr) using a transformation means (Tr). In an interface module (20), a detection means (EM) recognizes that virtual addresses (vAdr) are present in a received virtual configuration file (vKonfig). This recognition triggers a signal (Si) which causes the interface module (20) to accept the virtual configuration file (vKonfig) and store it permanently in a configuration memory (KS). Furthermore, in the interface module (20), a reverse transformation means (RTr) transforms the virtual addresses (vAdr) back to physically existing addresses, namely the logical addresses (lAdr).which, for data exchange of the process data (IO) of the module slot (11) when requested by other fieldbus participants, the process data (IO) in the module slot (11) are addressed.