Field Device Configuration via Intermediary Data Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The configuration of Foundation Fieldbus field devices is complex and requires substantial skill, and replacing a field device involves recommissioning and reconfiguring it, which is cumbersome and requires a host computer with configuration tool software, making it difficult to manage multiple devices and maintain networks efficiently.

Innovation Solution

A configuration device with a memory domain for storing and uploading/download configuration data for field devices, allowing for simplified configuration and replacement of field devices by uploading or downloading entire device configurations, reducing the need for sequential message configuration and eliminating the requirement for detailed knowledge of the field device or host computer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional configuration methods using host computer software tools are used, then field devices can be configured and replaced, but the process is complex and requires substantial skill and time

Engineering Contradiction:
Improveease of configurationVSAvoidconfiguration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A configuration device is introduced as an intermediary between the field device and the host computer. This configuration device contains a configuration data store with template configurations for different field device types. When a field device needs configuration, the configuration device automatically selects and transfers the appropriate template configuration to the field device, eliminating the need for complex manual configuration procedures and substantial technical expertise.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If manual configuration procedures are used for each field device, then devices can be configured, but the process is time-consuming and reduces productivity

Engineering Contradiction:
Improvedevice configuration speedVSAvoidconfiguration time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Template configurations are prepared in advance and stored in the configuration device's data store. These templates contain pre-configured parameters and settings for different field device types. When a field device is installed or replaced, the configuration device automatically retrieves and transfers the appropriate pre-prepared template configuration, eliminating the need for time-consuming manual configuration procedures and significantly increasing productivity.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If sequential message configuration is used, then field devices can be configured, but the process requires detailed knowledge and is cumbersome

Engineering Contradiction:
Improveease of device replacementVSAvoidtechnical expertise requirement
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The configuration device stores template configurations that are copies of standard field device configurations. When a field device needs to be configured or replaced, the configuration device automatically copies the appropriate template configuration to the field device. This copying process eliminates the need for technicians to have detailed knowledge of sequential message configuration procedures, making device replacement simple and straightforward.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2266023B1Configuration of field devices on a network
Publication Date: 2017.01.11 ROSEMOUNT INC
  • EP2266023B1 patent drawing
  • EP2266023B1 patent drawing
  • EP2266023B1 patent drawing

AI summary

Field devices 18 a communication network 10 can be configured using a configuration device 20 that stores a configuration data for each of the field devices 18 in a network configuration domain in nonvolatile memory 36. Each field device 18 includes a configuration domain associated with configuration data stored in nonvolatile memory 36 of the field device 18. In response to commands from the configuration device 20, the field devices upload configuration data to or download configuration data from the configuration device 20. Field devices 18 receive configuration data from the configuration device 20 and store the received configuration data in the nonvolatile memory 36 to define the configuration of the field device 18.