Field Instrument Device Description Update Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing process control systems lack an efficient method to update device descriptions of field instruments, leading to inaccessible new features and unresolved bugs in older revisions, as operators are not informed about newer functionalities and compatibility issues.
Innovation Solution
A method and system that compare the host revision of a device description with the instrument revision to generate a character string of update information, which is then displayed to operators, providing details on available features, bugs, and how to obtain newer revisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the host application uses an older revision of the device description, then the system maintains stability with existing functionality, but new features and bug fixes in newer revisions remain inaccessible
Solution Approach 1:
The system implements a feedback mechanism where the host application automatically queries the field instrument to obtain its current device description revision number. This feedback loop enables the application to compare its own revision against the instrument's revision, identifying when updates are available without manual intervention or external documentation review.
Solution Approach 2:
The patent introduces an intermediary update information record that stores revision numbers and update descriptions. This intermediary structure acts as a mediator between the field instrument and the host application, facilitating automatic update detection by comparing stored revision information with current instrument status, thereby bridging the information gap.
2Reliability
If operators manually check for device description updates, then they can access update information, but this process consumes time and is prone to human error
Solution Approach 1:
The host application performs self-service by automatically querying the field instrument for its device description revision number and comparing it against the revision the application was compiled against. This self-service mechanism eliminates the need for operators to manually check update status, reducing time consumption and eliminating human error while maintaining high reliability through automated comparison logic.
3Ease of operation
If the system automatically detects and prompts for updates, then operators are informed about new functionalities, but this requires additional system complexity
Solution Approach 1:
The device description structure serves multiple functions: it not only provides the revision number for compatibility checking but also stores human-readable update information describing new features and improvements. This multi-functionality allows the same data structure to support both automatic update detection and operator information display, avoiding the need for separate complex systems.
Solution Approach 2:
The system creates a local copy of the device description revision information stored in the field instrument and compares it with the revision embedded in the host application. This copying approach simplifies the update detection mechanism by working with replicated data rather than implementing complex real-time communication protocols, reducing system complexity while maintaining ease of operation.
Data Source
Figure 1~2
Figure 3
Figure 4A~4B
AI summary
Methods and systems to update information of a device description of a field instrument are described. In one example, a method involves comparing a host revision of the device description executed via a host application to an instrument revision of the device description of the field instrument, generating a character string of update information based on the comparison, the character string containing the update information, and displaying the character string via the host application.