Field Device URL Launch for Automatic Driver and Communication Path Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Locally installed frame applications in Plant Asset Management systems cannot be automatically started, requiring manual configuration of communication topology to access field devices, which is error-prone and time-consuming.
Innovation Solution
A method that involves calling a link with a protocol and parameter field to initiate a frame application, configure a communication path, and open a device driver, allowing automatic selection and download of suitable drivers for field device access, thereby simplifying the infrastructure setup on the operating unit.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration of communication topology is performed to access field devices, then access to field devices is achieved, but the process is error-prone and time-consuming
Solution Approach 1:
The communication topology and device driver information are pre-configured and stored in the database associated with the Plant Asset Management application. When a user activates a field device through the application, the pre-stored configuration data is automatically retrieved and used to establish the communication path, eliminating the need for manual configuration and reducing both time and errors.
2Ease of operation
If manual configuration of communication topology is performed, then field device access is established, but manual intervention is required
Solution Approach 1:
The system enables self-service operation where the Plant Asset Management application automatically retrieves communication topology and device driver information from its associated database when a field device is activated. This automated process eliminates manual configuration steps while maintaining ease of operation, as users simply need to activate the device through the application interface.
3Productivity
If infrastructure setup is performed manually on the operating unit, then field device access is configured, but the process is complex and time-consuming
Solution Approach 1:
The complex infrastructure configuration process is extracted and relocated to the database associated with the Plant Asset Management application. The database stores pre-configured communication topology and device driver information, allowing rapid retrieval and automatic configuration when field devices are activated, thereby simplifying the user interface and improving setup speed.
Data Source
Figure 1
Figure 2
AI summary
The invention relates to a method for operating a field device (F1, F2, F3, ..., Fn) used in an automation technology system (A), said field device having a communication link to a field access unit (FE), in particular a processor unit, a gateway, or an edge device, by means of a first wired or wireless communication network (KN1), in particular by means of an automation technology fieldbus, the method comprising: - retrieving a link (URL1, URL2, URL3, ... URLn) of the field device (F1, F2, F3, ..., Fn) on a client computer (CR), the link (URL1, URL2, URL3, ... URLn) consisting at least of a protocol field and a parameter field, the retrieving of the link (URL1, URL2, URL3, ... URLn) triggering the following steps: a) launching a first framework application (FR1) associated with the protocol field of the link (URL1, URL2, URL 3, ... URLn), in particular an FDT framework application, an FDI host, a DD host, or an EDD host; b) transferring the link (URL1, URL2, URL3, ... URLn) to the first framework application (FR1) and, using said first framework application (FR1), extracting at least one item of information obtained in the parameter field; c) configuring a communication path (KP) between the client computer (CR) and the field device (F1, F2, F3, ..., Fn) via the field access unit (FE) using the at least one item of information; d) opening a device driver (GT) associated with the field device (F1, F2, F3, ..., Fn), or a device description associated with the field device (F1, F2, F3, ..., Fn) in the first framework application (FR1).