Aviation airborne computer self-detection method
Through the design of configuration tables and state machines, the self-detection method of aviation onboard computers is realized, solving the problem of traditional self-detection functions lacking configurability and automatic response capabilities, realizing low latency and high reliability self-detection effects, improving Self-detection capability and portability.
Patent Information
- Application Number
- CN202411321655.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2025-02-07
AI Technical Summary
The self-detection function of traditional aviation airborne computer equipment lacks convenient configurability, automatic response capability and complete state machine mechanism, making it difficult to meet the needs of low latency, high reliability, and rapid configuration of embedded equipment self-detection.
By designing configuration tables and state machines, the self-detection method of aviation onboard computers is realized. The configuration table contains configuration items such as detection information, power-on detection, and cycle detection. The state machine performs self-detection based on the configuration table, including minimalist power-on detection, comprehensive power-on detection and periodic self-detection, and performs fault confirmation and clearance arbitration.
It realizes low latency, high reliability and rapid configuration of self-detection of aviation airborne computers, reduces the difficulty and labor costs of troubleshooting, and improves self-detection capabilities and portability.
Smart Images
Figure CN119396636A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the field of aviation onboard computers and relates to an aviation onboard computer self-detection method realized by a configuration table and a state machine. Background Art
[0002] In the development process of aviation onboard computer equipment, it is necessary to fully consider the fault detection and response capabilities. The traditional electronic equipment self-detection function does not have convenient configurability, automatic response capabilities, and a complete state machine mechanism. Summary of the invention
[0003] The purpose of the invention is to provide an aviation onboard computer self-detection method, which meets the requirements of low latency, high reliability, and fast configuration of embedded device self-detection through the design of configuration tables and state machines. Compared with traditional self-detection methods, it has the advantages of flexible configuration and system decoupling.
[0004] The object of the present invention is achieved through the following technical solutions:
[0005] A self-test method for an aviation onboard computer includes configuring a configuration table and performing self-testing by a state machine according to the configuration table, wherein:
[0006] The configuration table contains:
[0007] Configuration of the detection information configuration table: used to define the relevant matters of each detection item, including the detection item sequence number, fault confirmation filter parameters, fault clearing filter parameters, detection window times, and detection execution callback function;
[0008] Power-on detection configuration table: used to define the detection items and detection sequence of the simplified power-on detection stage and the comprehensive power-on detection stage;
[0009] Periodic detection configuration table: used to define the detection content and detection cycle of the periodic self-detection stage. Each cycle executes a row of detection items in sequence.
[0010] The state machine consists of the following steps:
[0011] Step 1: Read the detection execution callback function of each detection item configured in the minimalist power-on detection item in the power-on detection configuration table from the detection information configuration table to perform a minimalist power-on self-test. If a fault occurs in the detection item, the fault is confirmed. After completing all minimalist power-on detection items, proceed to step 2;
[0012] Step 2: If a comprehensive power-on self-test is also configured in the power-on test configuration table, the test execution callback function of each test item configured in the comprehensive power-on test item is read from the test information configuration table to perform a comprehensive power-on self-test. If a fault occurs in the test item, the fault is confirmed.
[0013] Step 3: In one cycle, according to the detection items configured in one row of the periodic self-test configuration table, read the detection execution callback function corresponding to the detection item from the detection information configuration table to perform periodic self-test. If the detection item reports a fault, go to step 4. If the detection item does not report a fault, go to step 5. After executing one row, the next cycle executes the next row of detection;
[0014] Step 4: If a periodic detection item reports a fault, arbitration is performed based on the "fault confirmation parameter" and "detection window times" of the detection item in the detection information configuration table to determine whether to confirm the fault;
[0015] Step 5: If the periodic detection item does not report a fault, and the fault is currently in a fault confirmation state, arbitration is performed based on the "fault clearing parameters" and "detection window times" of the detection item in the detection information configuration table to determine whether fault clearing is required.
[0016] Preferably, the fourth step includes the following arbitration steps:
[0017] Step 41: Determine whether the current state of the detection item is fault confirmation, if yes, return to step 3 to perform the next detection, if no, proceed to the next step;
[0018] Step 42: Determine whether the cumulative number of failures of the detection item reaches the fault confirmation filter parameter configured in the detection information configuration table. If yes, the fault is confirmed. Otherwise, the window cycle execution times +1, the cumulative number of failures +1, and proceed to the next step.
[0019] Step 43: Determine whether the window cycle execution times have reached the detection window times configured in the detection information configuration table. If not, execute the next detection. If yes, clear the window cycle execution times and the accumulated fault times before executing the next detection.
[0020] Preferably, the fifth step includes the following arbitration steps:
[0021] Step 51: Determine whether the detection item is currently in a fault confirmation state, if not, return to step 3 to perform the next detection, if yes, proceed to the next step;
[0022] Step 52: Determine whether the number of times that the window period has accumulated without reporting a fault has reached the fault clearing filter parameter configured in the detection information configuration table. If it is a clear fault confirmation state, execute the next test, otherwise proceed to the next step.
[0023] Step 53: The number of window cycle executions +1, the cumulative number of unreported faults +1, determine whether the window execution times have reached the detection window times configured in the detection information configuration table, if not, execute the next detection, if yes, clear the window cycle execution times and the cumulative number of unreported faults, and then execute the next detection.
[0024] The beneficial effects of the present invention are:
[0025] The present invention solves a large number of fault diagnosis and processing problems in actual use, greatly reducing the difficulty and labor cost of troubleshooting. The present invention can conveniently add and delete detection content and set detection behavior attribute parameters based on the configuration table. The present invention is highly decoupled from the operating system and has high portability. The present invention improves the self-detection capability of aviation airborne display control and airborne computer systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 Schematic diagram of the switching process of the state machine shown in the embodiment.
[0027] Figure 2 This is a schematic diagram of fault confirmation arbitration.
[0028] Figure 3 This is a schematic diagram of fault clearing arbitration. DETAILED DESCRIPTION
[0029] The present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.
[0030] The aviation onboard computer self-detection method shown in this embodiment involves two parts: configuration of a configuration table and a state machine that switches states according to the configuration table.
[0031] 1. Configuration table
[0032] In order to make self-detection configurable, three sets of configuration tables are designed, in which detection items, detection stages, fault filtering parameters, execution callback functions, and fault response mechanisms can be easily added and tailored.
[0033] a)Configure the detection information configuration table
[0034] The detection information configuration table is used to define the relevant matters of each detection item, including the detection item sequence number, fault confirmation filter parameters, fault clearing filter parameters, detection window times, detection execution callback function, etc., as shown in Table 1:
[0035] Table 1 Detection information configuration table
[0036]
[0037] Step 1: Fill in the test item sequence number: the number corresponding to each test item, sorted in sequence starting from 1.
[0038] Step 2: Fill in the periodic self-test sequence number: If the test will be used as a periodic test, number it, starting from 1; if it is not used as a periodic test, write the number as -1.
[0039] Step 3: Fill in the fault confirmation filter parameters: For periodic detection, it can be configured to consider the fault confirmed after n cumulative error reports.
[0040] Step 4: Fill in the fault clearing filter parameters: For periodic detection, it can be configured to consider the fault cleared after accumulating n normal reports.
[0041] Step 4: Fill in the detection window times: Periodic self-detection is a judgment based on the cumulative occurrence or elimination of a certain number of times in a time window.
[0042] Step 5: Fill in the fault response method: For each detection, you can configure different fault handling methods; when a fault occurs, the corresponding callback function will be called for processing.
[0043] Step 6. Fill in the fault code: the fault ID corresponding to each detection item. The fault ID number meets the strong data type to prevent misrecording due to jitter during the recording process.
[0044] Item 7: Detection execution callback interface: the actual running function executed by the detection item.
[0045] b) Power-on detection configuration table
[0046] The power-on detection configuration table is used to define the detection items and detection sequence of the simplified power-on detection phase and the comprehensive power-on detection phase, as shown in Table 2:
[0047] Table 2 Power-on detection item configuration table
[0048] Simple power-on detection items Comprehensive power-on detection items Test No. 1 Test No. 3 Test No. 2 Test No. 5 … …
[0049] Step 1: Fill in the "Detection Item Sequence Number" item in the detection information configuration table header into the power-on detection item configuration table.
[0050] Step 2: After the system is powered on, the software will call the corresponding "detection execution callback function" in the detection information configuration table in sequence according to the detection items defined in this table. First execute the minimal power-on detection items, then execute the comprehensive power-on detection items.
[0051] Step 3: If there is a time requirement for the airborne system startup, key tests can be filled in the minimalist power-on test item configuration, and comprehensive power-on test items can be omitted to reduce the startup time.
[0052] Step 4: The detection items are executed in sequence. If a fault occurs, the "fault response method" in the detection information configuration table is called, and the results are stored and reported.
[0053] c) Periodic detection configuration table
[0054] The periodic detection configuration table is used to define the detection content and detection cycle of the periodic self-detection stage. Each cycle executes a row of detection items in sequence. A total of N cycles can be configured, and the detection cycle can be defined according to actual needs, as shown in Table 3:
[0055] Table 3 Periodic detection configuration table
[0056]
[0057] Step 1: Arrange the contents to be tested within a cycle according to the test time and the logical relationship between the test items, and fill in the "Test Item Sequence Number" item in the test information configuration table header into a row in the periodic test configuration table.
[0058] Step 2: Arrange the inspection contents to be performed in subsequent inspection cycles in sequence.
[0059] Step 3: After the system enters the periodic self-test phase, it will execute periodic self-tests in sequence starting from the first cycle, running one line per cycle.
[0060] Step 4: Determine whether the arbitration cycle fault can be confirmed as a fault according to the "fault confirmation filter parameters" and "detection window times".
[0061] Step 5: Determine whether the arbitration cycle fault has been cleared based on the "fault clearing filter parameters" and "detection window times", and determine that the current cycle fault has disappeared.
[0062] 2. State Machine
[0063] The state machine maintains three counts: the cumulative number of faults, the cumulative number of unreported faults, and the number of window cycle executions. It operates according to the above three configuration tables, such as Figure 1 The following steps are shown:
[0064] Step 1: Read the detection execution callback function of each detection item configured in the minimalist power-on detection item in the power-on detection configuration table from the detection information configuration table to perform a minimalist power-on self-test. If a fault occurs in the detection item, the fault is confirmed. After completing all minimalist power-on detection items, proceed to step 2.
[0065] Step 2: If a comprehensive power-on self-test is also configured in the power-on detection configuration table, the detection execution callback function of each detection item configured in the comprehensive power-on detection item is read from the detection information configuration table to perform a comprehensive power-on self-test. If a fault occurs in the detection item, the fault is confirmed.
[0066] Step 3: In one cycle, according to the detection items configured in one row in the periodic self-test configuration table, read the detection execution callback function corresponding to the detection item from the detection information configuration table to perform periodic self-test. If the detection item reports a fault, go to step 4. If the detection item does not report a fault, go to step 5. After executing one row, execute the next row of detection in the next cycle.
[0067] Step 4: If a periodic detection item reports a fault, the fault confirmation is not completed immediately. First, arbitration is performed based on the "fault confirmation parameters" and "detection window times" of the detection item in the detection information configuration table to determine whether to confirm the fault. The arbitration method is as follows: Figure 2 As shown:
[0068] Step 41: Determine whether the current status of the detection item is fault confirmation, if so, return to step 3 to execute the next detection, if not, proceed to the next step.
[0069] Step 42: Determine whether the cumulative number of failures of the detection item reaches the fault confirmation filter parameter configured in the detection information configuration table. If yes, the fault is confirmed. Otherwise, the window cycle execution times are increased by 1, the cumulative number of failures is increased by 1, and the next step is entered.
[0070] Step 43: Determine whether the window cycle execution times have reached the detection window times configured in the detection information configuration table. If not, execute the next detection. If yes, clear the window cycle execution times and the accumulated fault times before executing the next detection.
[0071] Step 5: If the periodic detection item does not report a fault, and the fault is currently in a confirmed state, arbitration must be performed based on the "fault clearing parameters" and "detection window times" to determine whether fault clearing is required. Figure 3 As shown below:
[0072] Step 51: Determine whether the detection item is currently in a fault confirmation state, if not, return to step 3 to execute the next detection, if yes, proceed to the next step.
[0073] Step 52: Determine whether the number of times that no faults are reported in the window period has reached the fault clearing filter parameter configured in the detection information configuration table. If it is a clear fault confirmation state, execute the next test, otherwise proceed to the next step.
[0074] Step 53: The number of window cycle executions +1, the cumulative number of unreported faults +1, determine whether the window execution times have reached the detection window times configured in the detection information configuration table, if not, execute the next detection, if yes, clear the window cycle execution times and the cumulative number of unreported faults, and then execute the next detection.
[0075] It is understandable that those skilled in the art can make equivalent substitutions or changes based on the technical solution and inventive concept of the present invention, and all these changes or substitutions should fall within the protection scope of the claims attached to the present invention.
Claims
1. A method for self-testing an onboard computer of an aircraft, characterized in that Contains a configuration table and a state machine that performs self-tests based on the configuration table, where: The configuration table contains: Configuration of the detection information configuration table: used to define the relevant matters of each detection item, including the detection item sequence number, fault confirmation filter parameters, fault clearing filter parameters, detection window times, and detection execution callback function; Power-on detection configuration table: used to define the detection items and detection sequence of the simplified power-on detection stage and the comprehensive power-on detection stage; Periodic detection configuration table: used to define the detection content and detection cycle of the CBIT stage. Each cycle executes one row of detection items in sequence. The state machine consists of the following steps: Step 1: Read the detection execution callback function of each detection item configured in the minimalist power-on detection item in the power-on detection configuration table from the detection information configuration table to perform a minimalist power-on self-test. If a fault occurs in the detection item, the fault is confirmed. After completing all minimalist power-on detection items, proceed to step 2; Step 2: If a comprehensive power-on self-test is also configured in the power-on test configuration table, the test execution callback function of each test item configured in the comprehensive power-on test item is read from the test information configuration table to perform a comprehensive power-on self-test. If a fault occurs in the test item, the fault is confirmed. Step 3: In one cycle, according to the detection items configured in one row of the periodic self-test configuration table, read the detection execution callback function corresponding to the detection item from the detection information configuration table to perform periodic self-test. If the detection item reports a fault, go to step 4. If the detection item does not report a fault, go to step 5. After executing one row, the next cycle executes the next row of detection; Step 4: If a periodic detection item reports a fault, arbitration is performed based on the "fault confirmation parameter" and "detection window times" of the detection item in the detection information configuration table to determine whether to confirm the fault; Step 5: If the periodic detection item does not report a fault, and the fault is currently in a fault confirmation state, arbitration is performed based on the "fault clearing parameters" and "detection window times" of the detection item in the detection information configuration table to determine whether fault clearing is required.
2. The method for self-testing an onboard computer according to claim 1, characterized in that The fourth step includes the following arbitration steps: Step 41: Determine whether the current state of the detection item is fault confirmation, if yes, return to step 3 to perform the next detection, if no, proceed to the next step; Step 42: Determine whether the cumulative number of failures of the detection item reaches the fault confirmation filter parameter configured in the detection information configuration table. If yes, the fault is confirmed. Otherwise, the window cycle execution times +1, the cumulative number of failures +1, and proceed to the next step. Step 43: Determine whether the window cycle execution times have reached the detection window times configured in the detection information configuration table. If not, execute the next detection. If yes, clear the window cycle execution times and the accumulated fault times before executing the next detection.
3. The method for self-testing an onboard computer according to claim 1, characterized in that The fifth step includes the following arbitration steps: Step 51: Determine whether the detection item is currently in a fault confirmation state, if not, return to step 3 to perform the next detection, if yes, proceed to the next step; Step 52: Determine whether the number of times that the window period has accumulated without reporting a fault has reached the fault clearing filter parameter configured in the detection information configuration table. If it is a clear fault confirmation state, execute the next test, otherwise proceed to the next step. Step 53: The number of window cycle executions +1, the cumulative number of unreported faults +1, determine whether the window execution times have reached the detection window times configured in the detection information configuration table, if not, execute the next detection, if yes, clear the window cycle execution times and the cumulative number of unreported faults, and then execute the next detection.