Modular Embedded Controller Architecture for Obsolescence Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional embedded controllers are customized for specific applications, leading to lack of common architecture, complicating maintenance and obsolescence management due to individual redesign requirements when common components become obsolete.
Innovation Solution
A modular embedded controller with a generic motherboard and interchangeable daughterboards, including power, PHM, and communication modules, allowing customization while maintaining a common architecture across different applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If point design approach is used to customize controllers for specific applications, then the controller can provide required functionality and accommodate application constraints, but control systems for different devices lack common architecture and maintenance becomes complicated
Solution Approach 1:
The controller is divided into a common platform portion and application-specific portions. The common platform includes shared hardware resources and operating system, while application-specific functionality is implemented through separate software modules or daughterboards that can be selectively added to the common platform.
Solution Approach 2:
A universal common platform is designed that can support multiple different applications through configuration rather than hardware redesign. The platform provides standardized interfaces and resources that can be adapted to various application requirements through software or modular add-on components.
2Adaptability or versatility
If point design controllers are used with common components, then the controllers can be developed for specific applications, but when common components become obsolete each controller must be individually redesigned and requalified
Solution Approach 1:
The system is segmented into a stable common platform and replaceable application-specific modules. When components become obsolete, only the affected modules need to be updated while the common platform remains unchanged, eliminating the need to redesign entire controllers.
Solution Approach 2:
Multiple application-specific controllers share a merged common platform infrastructure. This consolidation allows obsolescence management to be handled at the module level rather than requiring individual controller redesigns, as the common platform provides a stable base for all applications.
3Adaptability or versatility
If customized layout and components are used for various controllers, then each controller can accommodate specific application constraints, but maintenance and re-design become more challenging
Solution Approach 1:
The controller architecture is segmented into a standardized common platform and application-specific modules. This segmentation allows maintenance personnel to work on standardized components across different applications, reducing the need for application-specific maintenance expertise while still accommodating diverse application requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A modular embedded controller includes an enclosure (120) with an external interface (104), a generic motherboard (106), and an external device-specific input/output daughterboard (112). The generic motherboard has a supervisory processor (108) and a plurality of daughterboard seats and is supported in the enclosure. The external device-specific input/output daughterboard is supported in one of the daughterboard seats, connects the external interface to the motherboard supervisory processor, and has an input/output processor translate data communicated between the motherboard supervisory processor and a device connected to the external interface. Embedded engine controllers and gas turbine engines with embedded controllers are also described.