Dynamic Firmware Modules for Self-Adaptive Field Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial automation systems face inflexibility due to rigid firmware in field devices, which hampers quick adaptation to changing demands and regulatory requirements, leading to increased costs and performance burdens from supporting multiple functionalities.
Innovation Solution
A self-adaptive field device with a repository, identity register, and framework that allows dynamic loading and unloading of firmware modules, enabling flexible firmware construction and adaptation, including static and dynamic firmware modules that can be initialized and configured based on machine application requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware is optimized for a specific task within the functional configuration, then field device performance is improved, but flexibility with regard to changes or replacements is reduced
Solution Approach 1:
The firmware is segmented into a framework portion and multiple functional modules. The framework provides the base structure, while individual functional modules can be independently loaded, unloaded, or replaced based on specific machine application requirements. This segmentation allows the field device to maintain optimized performance for specific tasks while enabling flexibility for changes and replacements.
Solution Approach 2:
The field device employs dynamic firmware loading capabilities, allowing functional modules to be loaded or unloaded during operation based on the specific machine application. This dynamic approach enables the firmware configuration to adapt to changing requirements without requiring complete firmware replacement, thus maintaining performance optimization while improving flexibility.
2Adaptability or versatility
If field devices are equipped with multiple functionalities, then versatility is improved, but device complexity and costs increase
Solution Approach 1:
The field device uses a universal framework that can load different functional modules to perform various machine applications. Instead of embedding all possible functionalities directly into the firmware, the framework provides a common foundation that works with different functional modules, reducing overall complexity while maintaining versatility.
Solution Approach 2:
Specific functional modules are extracted from the main firmware and stored separately. This allows the core framework to remain relatively simple while specific functionalities are added only when needed. The functional modules can be selectively loaded based on the specific machine application, reducing the complexity of the always-present firmware while maintaining access to multiple functionalities.
3Reliability
If firmware is loaded permanently on the field device, then task execution reliability is improved, but adaptability to changing demands is reduced
Solution Approach 1:
The framework is pre-configured with the capability to load and execute functional modules, and the identity register is pre-prepared to store information about available modules. This preliminary setup ensures reliable task execution while maintaining the adaptability to load different modules as demands change.
Solution Approach 2:
The identity register provides feedback information about the field device's current configuration and available functional modules. This feedback mechanism allows the system to understand what functionalities are currently loaded and make informed decisions about loading additional modules or replacing existing ones, ensuring both reliable execution and adaptability to changing demands.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A self-adaptive field device is disclosed having a repository, an identity register and a firmware framework having static firmware modules. Further disclosed is an industrial automation system of self-adaptive field devices, and a method for configuring such a system. The method includes booting each field device, evaluating each field device, and initialising each field device. The method may further include resource load balancing.