Remote Field Device Servicing via Web Server Protocol Emulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing solutions for servicing field devices from remote terminals face challenges such as inconsistent device drivers, compatibility issues, and high installation efforts due to the large number of device descriptions and DTMs, leading to difficulties in integrating field devices into control systems and maintaining compatibility across different versions.
Innovation Solution
The integration of a web server in field devices that communicates with remote terminals using defined transmission protocols, allowing for dynamic content delivery of device information, including firmware, and using a generic communication driver to emulate onsite servicing protocols, eliminating the need for consistent device drivers on remote terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If device drivers and device descriptions are installed on remote terminals to service field devices, then field devices can be integrated and serviced, but installation effort and complexity increase significantly
Solution Approach 1:
The patent introduces a protocol converter as an intermediary device that translates between different fieldbus protocols and a standardized internal protocol. This converter handles protocol-specific device descriptions and drivers centrally, eliminating the need to install multiple protocol-specific drivers on each remote terminal. The converter mediates between the diverse fieldbus systems (Profibus, Foundation Fieldbus, HART) and the servicing tools, reducing terminal complexity while maintaining integration capability.
Solution Approach 2:
The protocol converter implements a universal interface that can service multiple fieldbus protocols through a single standardized connection to remote terminals. By creating a unified protocol layer that translates various fieldbus protocols into a common internal format, the system enables single-driver-based servicing of diverse field devices, eliminating the need for multiple protocol-specific drivers on each terminal.
2Adaptability or versatility
If multiple device descriptions are maintained for different fieldbus protocols, then compatibility with various field devices is achieved, but consistency and reliability decrease due to version mismatches
Solution Approach 1:
The protocol converter acts as a centralized intermediary that maintains a single source of truth for device descriptions. Instead of distributing multiple protocol-specific driver versions across terminals, the converter stores and manages device descriptions centrally, translating them into the standardized internal protocol. This ensures all terminals receive consistent device information from a single authoritative source, eliminating version mismatch issues.
Solution Approach 2:
The system creates a standardized copy of device descriptions in the protocol converter's internal representation. Rather than using the original protocol-specific device descriptions directly on terminals, the converter creates a unified internal copy that abstracts away protocol differences. This standardized copying process ensures consistency across all terminals while maintaining the ability to service different fieldbus protocols.
3Adaptability or versatility
If protocol-specific drivers are used for different fieldbuses, then specific field devices can be serviced, but the number of required drivers and device descriptions increases
Solution Approach 1:
The protocol converter serves as a mediator that consolidates multiple protocol-specific drivers into a single device. Instead of requiring each remote terminal to install separate drivers for Profibus, Foundation Fieldbus, HART, and other protocols, the converter handles all protocol translations centrally through a single standardized interface to the terminals, dramatically reducing the number of drivers needed.
Solution Approach 2:
The protocol converter implements a universal driver architecture that can handle multiple fieldbus protocols through a single standardized connection. By creating a multi-functional translation layer that converts various protocols into a common internal format, the system enables one driver to service multiple protocol types, eliminating the need for numerous protocol-specific drivers on each terminal.
Data Source
AI summary
An apparatus for servicing a field device from a remote terminal, wherein the field device has an onsite display/servicing capability and is connected to a fieldbus of process automation technology. The remote terminal and the field device communicate with one another via at least one defined transmission protocol. A web server is integrated in the field device, in a Plant Access Point or in the remote terminal; the web server provides all requested device information, which is the so called firmware, of the field device in the form of dynamically produced contents to the remote terminal. A communication driver specific to the applied transmission protocol and a browser are integrated in the remote terminal. The communication driver emulates the protocol of the onsite display/servicing capability of the field device on the remote terminal and the dynamically produced contents are displayed on a display of the remote terminal via the web browser, so that the onsite display/servicing capability at the field device and the display/servicing capability at the remote terminal are identical.