Field Device Access Links for Automatic Communication Path Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Locally installed frame applications in automated plants cannot be easily started for field device access, requiring manual creation of communication topology, which is time-consuming and prone to errors.
Innovation Solution
A method that involves invoking a link composed of a protocol field and a parameter field to initiate a frame application, configure a communication path, and open a device driver, allowing for automated and efficient access to field devices through a client computer connected via a communication network, such as a fieldbus, using a URL-like link to load infrastructure and select appropriate device drivers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual creation of communication topology is used to access field devices, then the frame application can be started, but the process is time-consuming and prone to errors
Solution Approach 1:
The communication topology and device driver information are pre-configured and stored in the automated plant system before the frame application is started. When a user wants to access a field device, the system automatically retrieves the pre-stored communication parameters and device driver information, eliminating the need for manual configuration at the time of access.
Solution Approach 2:
The system automatically configures the communication path and selects the appropriate device driver based on the field device identifier without requiring manual intervention. The automated plant system itself performs the configuration tasks that would otherwise need to be done manually by the operator.
2Reliability
If manual configuration of communication path is performed, then field device access is established, but the process is complex and error-prone
Solution Approach 1:
The automated plant system automatically configures the communication path and selects the appropriate device driver based on the field device identifier, eliminating manual configuration steps that are prone to errors. The system performs self-configuration using pre-stored communication parameters.
Solution Approach 2:
The system uses the field device identifier as feedback to automatically determine the appropriate communication parameters and device driver. The identifier provides information about the field device type and communication requirements, enabling the system to automatically configure the correct communication path without manual intervention.
3Ease of operation
If automated link invocation is implemented, then access to field devices is simplified, but requires standardized communication protocols
Solution Approach 1:
The automated link invocation mechanism uses a universal communication interface that can handle different field device types through standardized protocols. The system maintains adaptability by storing device-specific information (such as device driver identifiers and communication parameters) associated with each field device identifier, allowing the universal interface to adapt to specific device requirements.
Solution Approach 2:
The system changes communication parameters dynamically based on the field device identifier. When a link is invoked with a field device identifier, the system retrieves and applies the appropriate communication parameters and device driver information, enabling automated access while adapting to different device types through parameter adjustment.
Data Source
AI summary
The present disclosure resides in a method for operating, installed in an automated plant, a field device, which is connected for communication with a field access unit by means of a first communication network, especially by means of a fieldbus of automation technology, comprising: invoking a link of the field device in a client computer, wherein the link is composed at least of a protocol field and a parameter field, wherein the invoking of the link initiates steps as follows: starting a first frame application associated with the protocol field of the link; transferring the link to the first frame application and extracting information contained in the parameter field by the first frame application; configuring a communication path between the client computer and the field device via the field access unit with application of the information; opening a device driver or a device description in the first frame application.