Avionics Software Synchronization via Shadow Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Avionics systems face challenges in synchronizing software versions across distributed power distribution assemblies, leading to potential operational inefficiencies and downtime due to version mismatches or corruption, especially when replacing hardware modules.
Innovation Solution
Implementing a synchronization module that compares and validates operational software instances stored in local and shadow memory, replacing outdated or corrupted versions with a validated instance from the shadow memory during startup, ensuring compatibility and integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of repair
If hardware modules are made removable for maintenance and replacement, then ease of repair is improved, but software version synchronization and configuration consistency deteriorate
Solution Approach 1:
The shadow memory stores a validated copy of the operational software in advance. When a control module is replaced, the new module automatically receives the correct software version from shadow memory without requiring manual intervention or version verification, thus maintaining software consistency while enabling easy hardware replacement.
Solution Approach 2:
The shadow memory acts as an intermediary between the operational memory and the replacement control modules. It provides a validated software copy that ensures configuration consistency when modules are exchanged, resolving the conflict between easy replacement and software synchronization.
2Reliability
If software validation and synchronization checks are performed during startup, then reliability is improved, but productivity deteriorates due to additional verification time
Solution Approach 1:
Software validation is performed in advance during system configuration or maintenance periods, and the validated version is stored in shadow memory. During normal startup, the control module simply copies the pre-validated software from shadow memory to operational memory, significantly reducing startup time while maintaining reliability.
Solution Approach 2:
The system performs full software validation only when necessary (during initial configuration or shadow memory updates), not during every startup. This partial validation approach maintains reliability while minimizing the impact on productivity during normal operations.
3Adaptability or versatility
If software is stored locally in each control module, then adaptability is improved, but loss of information increases due to potential corruption or version mismatches
Solution Approach 1:
Each control module maintains a local copy of the software for adaptability and fast execution. Additionally, a validated copy is maintained in shadow memory, providing a backup that prevents information loss from corruption or version mismatches. The shadow memory serves as a reference for recovering from local software errors.
Solution Approach 2:
The shadow memory provides a pre-prepared backup of validated software before any corruption can occur in the operational memory. This cushioning mechanism ensures that even if local software becomes corrupted, the system can recover by copying from the protected shadow memory, thus preventing information loss.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An assembly for an aircraft according to an example of the present disclosure includes, among other things, a control module (26H,28H) including a processor (32) and a local memory (34) that stores a first instance of operational software executable by the processor and that relates to functionality of the control module to selectively control a vehicle system, and a backplane memory device (42) coupled to the control module by a common backplane. The backplane memory device includes shadow memory (44) that stores a second instance of the operational software. A method of synchronizing an assembly is also disclosed.