Web-Based Control Unit for Embedded Device Driver Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for connecting embedded devices to control units in industrial control systems are cumbersome and require significant time and logistical effort due to the need for extensive storage of drivers and separate development environments, which complicates the integration and operation of these devices.

Innovation Solution

A method where the control unit provides a web-based programming environment that allows for the creation, modification, and execution of sequence programs, with embedded devices transmitting necessary functional data to the control unit via a data connection, enabling operation without pre-existing knowledge of the device, and allowing for remote access and maintenance through a web server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If all drivers for embedded devices are stored in the development environment, then all embedded devices can be supported, but storage space requirements increase significantly

Engineering Contradiction:
Improvedevice compatibilityVSAvoidstorage space
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts driver information from the control unit's memory and transfers it to the embedded device. The control unit retrieves only the necessary driver data for a specific device when needed, rather than storing all possible drivers permanently. This extraction approach reduces the control unit's storage requirements while maintaining full device compatibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by pre-configuring the embedded device with its own driver information and identification data before connection to the control unit. When the device connects, it automatically provides its driver information to the control unit, eliminating the need for the control unit to have pre-stored drivers for all possible devices. This preliminary preparation enables plug-and-play operation.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If a separate development environment is used for configuration, then comprehensive device support is achieved, but connection time and logistical effort increase

Engineering Contradiction:
Improvedevice support capabilityVSAvoidconnection time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges the configuration functionality directly into the control unit by integrating a programming environment that can be accessed via web server. This eliminates the need for separate external development environments and allows configuration to be performed directly at the control unit, significantly reducing connection and setup time while maintaining comprehensive device support capability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The embedded device performs self-service by automatically transmitting its identification and functional data to the control unit upon connection. This automatic self-identification and self-description eliminates the need for manual configuration steps and reduces logistical effort, allowing the device to be operational within seconds of connection.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If the control unit stores all functional data, then device operation is simplified, but the control unit must be adapted to specific devices

Engineering Contradiction:
Improvedevice operation simplicityVSAvoidcontrol unit adaptation
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent inverts the traditional approach by having the embedded device provide its functional data to the control unit, rather than the control unit having to know about all possible devices in advance. The control unit stores and uses the functional data only after receiving it from the specific connected device, eliminating the need for pre-adaptation while maintaining ease of operation.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentEP3021179B1Method for connecting an embedded device to a control unit
Publication Date: 2019.10.09 SCHNEIDER ELECTRIC AUTOMATION
  • EP3021179B1 patent drawingFigure 1
  • EP3021179B1 patent drawingFigure 2

AI summary

The invention relates to a method for connecting an embedded device to a control unit of an industrial controller, wherein the control unit provides a programming environment by means of which a sequence program of the control unit can be created or modified, wherein access to the programming environment is via a web server of the control unit, wherein the programming environment allows the input of source code and generates executable code from the source code by the control unit, a data connection is established between the embedded device and the control unit, and the embedded device transmits all necessary functional data to the control unit in order to operate the embedded device by means of the control unit, wherein the functional data contains all information necessary for the further operation of the embedded device by the control unit and the functional data comprises functional blocks.which contain functions executable by the embedded device, with the functional blocks being transferred in a source code.