Decoupling Field Device Drivers for Low-Resource Automation Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for remote control of field devices in automation systems require high computing power and memory, limiting their use to larger computing units and making it difficult to access spatially distributed automation systems, as both logic and user interface device driver components run in the same framework application, necessitating direct access to computer units and high hardware resources.
Innovation Solution
Central installation of device driver packages on a server outside the field devices, with only web-based user interface components running on the server and logic device driver components in the server frame application, allowing user interfaces to be loaded and displayed in a web browser, decoupling the field device management module from user interfaces and peripherals, enabling operation on low-resource devices like one-chip computers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If both logic device driver components and user interface device driver components run in the same framework application, then complete field device functionality is achieved, but high computing power and memory are required
Solution Approach 1:
The framework application is segmented into two separate components: a server-side framework application that runs logic device driver components, and a client-side framework application that runs user interface device driver components. This segmentation allows each component to run independently with reduced resource requirements, resolving the contradiction between complete functionality and high power consumption.
Solution Approach 2:
A communication interface acts as an intermediary between the server-side and client-side framework applications, enabling data exchange and coordination without requiring both components to run on the same high-power device. This mediator allows the system to maintain full functionality while distributing computational load across lower-power devices.
2Ease of operation
If the framework application runs locally on the operating device, then direct access to field devices is enabled, but remote access to spatially distributed automation systems becomes difficult
Solution Approach 1:
The server acts as an intermediary between the operating device and field devices, enabling remote access to spatially distributed automation systems. The server-side framework application maintains direct access to field devices while the client-side application provides remote interface, resolving the contradiction between direct access and remote capability.
Solution Approach 2:
The system transitions from a single-location local access model to a distributed remote access model by separating the framework application into server and client components that can communicate across different spatial locations through network infrastructure.
3Ease of operation
If device driver packages are installed locally on the operating device, then field device operation is enabled, but hardware requirements increase
Solution Approach 1:
The user interface device driver components are extracted from the server and relocated to the client device, allowing the server to run with minimal hardware requirements while the client handles the resource-intensive user interface operations. This extraction resolves the contradiction between operational capability and hardware complexity.
Solution Approach 2:
The framework application is copied into two versions: a streamlined server version that runs logic device drivers with minimal resources, and a full-featured client version that runs user interface device drivers. This copying strategy enables field device operation while reducing the hardware burden on the server.
4Device complexity
If a web browser is used to display user interfaces, then peripheral display units are no longer needed, but only web-based user interface components can run
Solution Approach 1:
The physical display unit is replaced with a software-based web browser interface, eliminating the need for peripheral display hardware. The user interface is rendered through web technologies accessible via browser, substituting mechanical/display dependencies with software-based presentation.
Solution Approach 2:
The web browser serves as a universal interface platform that can display various user interface types (web-based, HTML, XML) without requiring device-specific peripherals. This universality allows the system to maintain adaptability while eliminating peripheral dependencies.
Data Source
Figure 1
Figure 2
Figure 3a~3c
AI summary
The invention relates to a method and an arrangement for remotely controlling at least one field device (D1... Dn) in at least one automation system (P1... Pk) with an operator panel (BG), wherein an operator program (BP) runs in the operator panel, which communicates with a server framework application (SFDT-FA) that runs on one of the field device management modules (FMM1... FMMk) assigned to the at least one automation system (P1... Pk), wherein device driver packages (DTM-P1... DTM-Pk) and at least one communication device driver package (CDTM-P) for operating the field devices (D1... Dn) are installed in the server framework application (SFDT-FA), each of which includes a logic device driver component (DTM-BL1... DTM-BLn; CDTM-BL1... CDTM-BLn) and a user interface device driver component (DTM-UI1... DTM-UIn; CDTM-UI1... CDTM-UIn). exhibit.To simplify the configuration and operation of field devices in spatially distributed automation systems, it is planned that the device driver packages (DTM-P1 ... DTM-Pn) of all field devices (D1 ... Dn) of the automation systems (P1 ... Pk) are installed centrally in a client framework application (CFDT-FA), which runs on a server (S) assigned to the operator panel (BG) and located outside the field devices (D1 ... Dn). The client framework application (CFDT-FA) of the server (S) should only run web-based user interface device driver components (DTM-UI1 ... DTM-UIn; CDTM-UI1 ... CDTM-UIn). The server framework application (SFDT-FA) of the field device management modules (FMM1 ... FMMk) should only run logic device driver components (DTM-BL1 ... DTM-BLn; CDTM-BL1 ... CDTM-BLn). and that field device type-specific user interface of at least one device driver orThe communication device driver is provided as a web page by a web server (WSER) coupled with the client frame application (CA) and is loaded and displayed in a web browser (WB) provided by the operator device (BG).