External Server for Field Device Operation via Dynamic Web Pages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing solutions for operating field devices in automation technology, such as those requiring device drivers and device descriptions, are cumbersome due to direct dependencies and the need for frequent updates, and integrated web servers in field devices face compatibility issues and resource limitations, limiting their applicability.

Innovation Solution

A server outside the field device dynamically generates field device-specific websites, and an operating program with a web browser provides access to these websites on a display unit, establishing a communication connection via a communication driver, allowing offline or online operation without the need for direct device connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If device drivers and device descriptions are used to operate field devices, then field devices can be operated with comprehensive functionality, but the system becomes complex and requires frequent updates

Engineering Contradiction:
Improvefield device operationVSAvoiddevice driver library
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the device driver functionality from the operating unit and relocates it to a server. The server generates device-specific websites that encapsulate all necessary driver information and communication protocols, allowing the operating unit to operate field devices without maintaining a local device driver library.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The server implements a universal solution that can operate any field device by dynamically generating appropriate device-specific websites. Instead of requiring different drivers for different devices, the server provides a multi-functional platform that adapts to various field device types through web-based interfaces.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If device drivers are updated to keep the host up to date, then field device compatibility is improved, but time is lost due to installation and update processes

Engineering Contradiction:
Improvefield device compatibilityVSAvoidupdate installation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The server performs preliminary actions by pre-generating device-specific websites with all necessary driver information and communication protocols embedded. This allows the operating unit to have immediate access to up-to-date device drivers without requiring installation or update processes at the host level.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the server receives information about field devices and automatically generates or updates device-specific websites. This ensures that the latest driver versions and compatibility information are continuously maintained and made available without manual intervention.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If integrated web servers are placed in field devices, then device driver updates are simplified, but resource limitations and compatibility issues arise

Engineering Contradiction:
Improvedriver update processVSAvoiddevice compatibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

Instead of placing web servers in field devices (embedded approach), the patent inverts the architecture by placing the web server functionality in a separate external server. This allows field devices to remain simple while the server handles all complex web-based operations and driver management.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The server acts as an intermediary between the operating unit and field devices. It provides web-based interfaces that simplify driver updates and device management, while also ensuring compatibility across different field device types through standardized web communication protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If multiple device descriptions are created for different fieldbus systems, then field devices can be integrated into various systems, but the number of descriptions becomes very large

Engineering Contradiction:
Improvefieldbus system integrationVSAvoidnumber of device descriptions
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The server provides a universal web-based interface that can communicate with field devices across different fieldbus systems (Profibus, Foundation Fieldbus, HART, etc.). Instead of requiring separate device descriptions for each system, the server adapts to various protocols through a single multi-functional platform.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent extracts protocol-specific device description logic from the operating unit and relocates it to the server. The server generates device-specific websites that encapsulate protocol adaptation rules, allowing the operating unit to interact with diverse fieldbus systems through a unified web interface without maintaining multiple device descriptions.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP2789145B1Device for operating at least one automation technology field device
Publication Date: 2018.08.29 ENDRESS HAUSER PROCESS SOLUTIONS AG
  • EP2789145B1 patent drawingFigure 1

AI summary

The invention relates to a device for operating at least one automation technology field device (F) by means of an operating unit (BE) that is connected to or connectible to said field device (F), a server (S), which is arranged outside the field device (F), being associated with the operating unit (BE), and the server (S) making web pages (WS) available to the respective field devices (F), depending on the type of field device. The operating unit (BE) is associated with an operating program (BP) which makes a browser (B) available such that the field device type-specific web pages (WS) can be made available on a display unit and that a communications connection (KA) can be established between the server (S) and the field device (F) for the purpose of operating the field device (F).