Extending Embedded Software Components in Field Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating field devices require complete software replacement, leading to increased data loading and memory requirements, which are resource-intensive in automation technology, and do not allow for the expansion of individual functions without replacing the entire firmware.
Innovation Solution
A method for extending embedded software components in field devices by loading an additional software component that interacts with the existing software to provide supplemental functions, allowing for flexible adaptation and expansion of device capabilities without replacing the entire firmware.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If complete software version is transferred to field device, then new functions can be provided, but data loading and memory requirements increase
Solution Approach 1:
The software is divided into a core embedded software component and separate extending software components. The core component remains in the field device while additional functionality is provided through separately loadable extending components that interact with the core component through defined interfaces.
Solution Approach 2:
Additional functionality is extracted from the complete software version and placed into separate extending software components that can be loaded independently. This allows only the necessary additional functions to be transferred rather than the entire software version.
2Adaptability or versatility
If complete firmware is replaced, then new functions can be added, but resource consumption increases
Solution Approach 1:
The firmware is segmented into a stable core embedded software component and modular extending software components. This segmentation allows the core component to remain in memory without replacement, reducing the computational overhead associated with complete firmware replacement while still enabling functional expansion.
Solution Approach 2:
Instead of replacing the complete firmware (excessive action), only the necessary extending software components are loaded to provide additional functionality (partial action). This reduces the processing and memory operations required, thereby lowering resource consumption.
3Adaptability or versatility
If individual functions are to be expanded, then flexibility is improved, but complete firmware replacement is required in conventional approaches
Solution Approach 1:
The software architecture is segmented into a core embedded software component and separate extending software components. Each extending component can be independently developed, loaded, and managed, allowing individual functions to be expanded without affecting the core component or requiring complete firmware replacement.
Solution Approach 2:
The core embedded software component is designed with universal interfaces that can interact with multiple different extending software components. This universality allows the same core component to support various functional extensions, improving flexibility without increasing the complexity of the core software structure.
Data Source
AI summary
Method for extending an embedded software component of a field device (F), wherein an extending software component is loaded into a memory of the field device (F), wherein by means of the extending software component at least one supplemental application function is provided for the field device (F), and wherein the embedded software component and the extending software component interact, in order to execute the supplemental application function.


