Microcontroller Fault Isolation via Dual-Controller Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microcontroller-based computers, a primary microcontroller may erroneously diagnose server hardware as faulty when it itself has a fault, leading to working hardware being replaced and a faulty microcontroller continuing to generate errors, resulting in downtime, resource waste, and incorrect identification of faulty components.
Innovation Solution
A method where the primary microcontroller sets fault records for itself and the component as pending faults and fails over to a backup microcontroller, which then confirms the fault status, clearing or setting permanent fault records accordingly to distinguish between hardware and microcontroller faults.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a primary microcontroller is used to detect faults in server hardware, then fault detection capability is improved, but the reliability of the system deteriorates because the microcontroller itself may be faulty and generate erroneous diagnoses
Solution Approach 1:
The system divides the microcontroller functionality into separate primary and backup microcontrollers. The primary microcontroller handles fault detection while the backup microcontroller verifies fault diagnoses. This segmentation allows the system to maintain fault detection capability while adding verification to eliminate erroneous diagnoses from potentially faulty microcontrollers.
Solution Approach 2:
The backup microcontroller acts as an intermediary that verifies fault diagnoses made by the primary microcontroller. When the primary microcontroller detects a fault, the backup microcontroller independently checks the same hardware component to confirm whether the fault is real or erroneous. This intermediary verification process resolves the contradiction by filtering out false positives while maintaining detection capability.
2Reliability
If redundant microcontrollers are used to avoid single point of failure, then system reliability is improved, but the complexity of the system increases due to need for fault record management and failover mechanisms
Solution Approach 1:
The system pre-establishes fault records for both the primary microcontroller and the hardware components before faults occur. These fault records are prepared in advance with clear states (pending fault, permanent fault, clear) and management rules. When faults are detected, the pre-established record structure allows for systematic management without ad-hoc complexity, reducing the operational burden despite having redundant microcontrollers.
3Measurement precision
If the primary microcontroller sets fault records and fails over to backup microcontroller, then fault isolation accuracy is improved, but the time required for fault identification increases due to failover process
Solution Approach 1:
The system performs preliminary actions by having both primary and backup microcontrollers ready with pre-configured fault records and verification capabilities. When the primary microcontroller detects a fault, the backup microcontroller is already prepared to independently verify the fault condition. This preliminary preparation allows for rapid failover and verification without significant time loss, as the verification process can begin immediately upon failover.
Solution Approach 2:
The system rushes through the verification process by having the backup microcontroller independently check the same hardware component that triggered the fault diagnosis. Rather than performing extensive additional testing, the backup microcontroller quickly verifies the specific fault condition and compares results. This rapid verification approach maintains high fault isolation accuracy while minimizing the time added by the failover and verification process.
Data Source
AI summary
A method and data processing system for isolating a faulty component in a computer. A first microcontroller detects a fault in a component of a computer. Responsive to detecting the fault, the first microcontroller sets a first fault record for the component to pending fault, sets a second fault record for the first microcontroller to pending fault, and fails over to a second microcontroller. If the second microcontroller detects the fault in the component of the computer, then the first fault record for the component is set to permanent fault, and the second fault record for the first microcontroller is cleared. If the second microcontroller determines the component of the computer does not have the fault, then the first fault record for the component is cleared, and the second fault record for the first microcontroller is set to permanent fault.