Field Device Parameter Management via Auxiliary Variable
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Field devices in process automation lack control over the timing and order of parameter changes due to dependencies between parameters, leading to inefficiencies and potential errors, especially in safety-critical applications, where parameters cannot always be changed independently.
Innovation Solution
A method using an auxiliary variable to execute different functions within a fieldbus protocol, allowing parameters to be written or read based on this variable, enabling independent parameter changes and storage management, regardless of the field device's version or protocol commands, by using a fieldbus protocol capable field device with an interface for communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If parameters are written to the field device using device description-based host systems, then parameterization can be performed, but control over the timing and order of parameter changes is lost
Solution Approach 1:
The host system determines dependencies between parameters beforehand and prepares a dependency-resolved parameter set in advance. This preliminary resolution of dependencies allows parameters to be written in the correct order without requiring the field device to perform complex dependency analysis during the writing process.
Solution Approach 2:
A dependency resolution mechanism acts as an intermediary between the host system and the field device. This intermediary resolves parameter dependencies and determines the optimal writing order, freeing the field device from this computational burden while maintaining control over parameter timing and order.
2Adaptability or versatility
If the field device resolves dependencies between parameters itself, then parameter changes can be handled, but performance is significantly reduced
Solution Approach 1:
The dependency resolution function is extracted from the field device and relocated to the host system. The field device no longer needs to perform complex dependency analysis, which significantly improves its performance. The host system assumes responsibility for determining the correct parameter writing order based on predefined dependencies.
3Reliability
If parameters are persisted to non-volatile memory after each parameter receipt, then data safety is improved, but write performance decreases
Solution Approach 1:
The host system determines all parameter dependencies and prepares the complete parameter set for writing before transmission begins. This preliminary preparation allows the field device to receive multiple parameters in quick succession and perform persistence operations in batches or at optimized intervals, rather than after each individual parameter receipt.
4Device complexity
If the same command is used for different field devices, then protocol simplicity is maintained, but different functions may be triggered for different devices
Solution Approach 1:
The field device is designed to handle multiple functions through a single universal command interface. The device interprets the same command differently based on its specific configuration and capabilities, allowing protocol simplicity to be maintained while accommodating diverse field device types. This is achieved through device-specific parameter interpretation rather than command differentiation.
Data Source
Figure 1
AI summary
A method for operating a fieldbus protocol capable field device, wherein the fieldbus protocol includes at least one command, which serves, depending on a value of an auxiliary variable, for performing a first function, respectively for performing a second function, of field device, wherein the first and second functions differ from one another.