Unified maintenance management method of fault information based on airborne distributed platform

Abstract

The present invention provides a unified maintenance and management method for fault information based on an airborne distributed platform, comprising: configuring the system management software into an upper level and multiple lower level nodes, the upper level and the lower level respectively perform initialization processes after power-on; the lower level obtains the power-on test results of each resident node, detects and records fault state change information; the lower level sends a joining request to the upper level, the upper level replies to the lower level to allow joining, completes the handshake between the upper level and the lower level, and the lower level reports the recorded power-on detection fault state change information to the upper level; the whole-machine maintenance system sends a command to the upper level, requiring the upper level to send the fault state change information that has occurred in the platform since power-on, and the upper level reports the recorded fault state change information since power-on to the whole-machine maintenance system. The present invention realizes unified fault information collection, maintenance, and management control of multiple nodes and heterogeneous nodes in the airborne distributed platform, and provides reliable maintenance information for ground maintenance personnel.

Description

Technical Field

[0001] The present invention relates to the technical field of airborne distributed system software, and in particular to a unified maintenance and management method for fault information based on an airborne distributed platform. Background Art

[0002] The whole-aircraft maintenance system is responsible for collecting and recording fault information of each aircraft subsystem and equipment. In order to reduce redundant information, only the fault status change information needs to be collected, that is, the state of the fault from non-existence to existence, and the state change information from existence to non-existence. In order to achieve the minimum resource cost to provide the most realistic fault information to maintenance personnel. At present, there are many types of faults in airborne distributed platforms, with large differences, and the locations of faults are scattered. Therefore, there are problems such as complex fault information collection and interactive management mechanisms, possible loss of fault information, and difficulty in continuous maintenance of fault status changes. It cannot meet the requirements of the whole aircraft for unified management of fault information on airborne distributed platforms during initialization, normal operation and maintenance. Summary of the invention

[0003] In view of this, an embodiment of the present application provides a unified maintenance and management method for fault information based on an airborne distributed platform. Based on the hierarchical management mechanism of the airborne distributed platform, the present application can realize the unified collection and management of faults of multiple nodes and heterogeneous nodes in the platform, thereby ensuring the accuracy and continuity of fault information.

[0004] The embodiment of the present application provides the following technical solution: a unified maintenance management method for fault information based on an airborne distributed platform, comprising:

[0005] The system management software is configured as an upper level and a plurality of lower level nodes managed by the upper level in the configuration data of the airborne distributed platform, and the upper level and the lower level respectively perform an initialization process after power-on and then enter a normal operation state;

[0006] The lower level obtains the power-on test results of each resident node, detects and records the fault status change information;

[0007] The subordinate sends a joining request to the superior. After receiving the joining request, the superior records the subordinate's joining status as joined and replies to the subordinate to allow joining.

[0008] After receiving the reply from the superior allowing joining, the subordinate records its joining status as joined, completes the handshake between the superior and the subordinate, and reports the recorded power-on detection fault state change information to the superior, and the superior records the fault state change information sent by the subordinate;

[0009] The superior sends online status information to the whole-machine maintenance system of the airborne distributed platform, and after the whole-machine maintenance system receives the online status information, the superior completes the handshake with the whole-machine maintenance system;

[0010] The whole machine maintenance system sends a command to the superior, requesting the superior to send the fault status change information of the platform since power-on, and the superior reports the recorded fault status change information since power-on to the whole machine maintenance system.

[0011] According to one embodiment, the initialization process includes:

[0012] After the upper level is powered on, the power-on test result of the lower level is obtained. If no power-on reply is received from the lower level, the lower level joining state is set to the non-joining state, the initialization process is completed, and then the normal operation state is entered;

[0013] After the subordinate is powered on, it obtains the power-on test results of the resident node, detects and records the fault state change information; at the same time, it sends a joining request to the superior. If no reply allowing joining is received from the superior, its own joining state is set to the non-joining state, the initialization process is completed, and the detection task is started.

[0014] According to an embodiment, after the lower level completes the initialization process, it obtains the power-on test result of the resident node, performs periodic detection, records the fault state change information and reports it to the upper level.

[0015] According to one embodiment, it further includes:

[0016] When the subordinate is powered on first and the superior is powered on later, the superior sends an instruction to the subordinate, requiring the subordinate to report all test results since power-on, and the subordinate reports all fault status change information recorded since power-on to the superior.

[0017] According to one embodiment, it further includes:

[0018] The whole-machine maintenance system sends a maintenance test command to the superior, the superior sends the maintenance test command to the subordinate, the subordinate executes the maintenance test command, reports the fault state change information detected during the maintenance test process to the superior, the superior records the fault state change information, and reports the fault state change information to the whole-machine maintenance system.

[0019] According to an embodiment, the method further includes: after waiting for the set maintenance test time, the superior sends a command to obtain maintenance test results to the subordinate, and the subordinate reports the recorded maintenance test results to the superior.

[0020] According to one embodiment, after the superior sends a command to obtain maintenance test results to the subordinate, if the superior does not receive the maintenance test results reported by the subordinate, the subordinate's test results are modified to failure, and all maintenance test results are reported to the whole machine maintenance system.

[0021] According to an embodiment, the whole machine maintenance system records the received fault status change information into a database.

[0022] Compared with the prior art, the at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0023] (1) Based on the hierarchical management and control mechanism of the airborne distributed platform, the present invention can realize unified management and control of the fault information of multiple nodes and heterogeneous nodes in the platform;

[0024] (2) The present invention provides unified management of fault information, reducing the complexity of interaction between each node and the whole machine maintenance system;

[0025] (3) The present invention is based on a two-level recording and two-level handshake mechanism to ensure the accuracy and continuity of fault information recording in various stages such as platform initialization, maintenance and normal operation, and to ensure that all fault status change information can be delivered to the entire aircraft maintenance system without losing fault information, thereby providing ground maintenance personnel with reliable maintenance information. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0027] Figure 1 This is a sequence diagram of unified maintenance management of fault information after the upper level is powered on in an embodiment of the present invention;

[0028] Figure 2 This is a sequence diagram of unified maintenance management of fault information after the lower level is powered on first in an embodiment of the present invention;

[0029] Figure 3 This is a deployment relationship diagram of fault information unified maintenance management software in an embodiment of the present invention. DETAILED DESCRIPTION

[0030] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0031] It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments, and the technical scheme of the present invention will be clearly and completely described. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0032] The embodiment of the present invention provides a method for realizing unified maintenance management of airborne distributed platform fault information, including:

[0033] Step 1: configure the two-level management structure of the system management software in the configuration data, configure the upper level and each lower level node of the airborne distributed platform managed by the upper level, and configure the maximum waiting time for maintenance testing.

[0034] Step 2, the distributed platform is powered on, the lower level starts fault detection, and records fault status change information: After the lower level node starts running, it obtains the power-on test results of the resident module. The lower level node collects and records fault status change information based on the detailed results of the power-on test.

[0035] Step 3: The upper and lower nodes start up respectively, complete the handshake between the upper and lower nodes, and the upper node records the collected fault status change information:

[0036] After the lower-level node is initialized, it sends a request to the upper-level node to join the system; if it receives a message from the upper-level node that allows it to join, it records its own joining status as joined, and sends the fault status change information collected during power-on to the upper-level node, which records the received fault status change information in the distributed platform global fault record table; if it does not receive a response from the upper-level node, it records its own joining status as not joined, completes its own initialization, enters normal operation, starts periodic test operation, and continues to collect faults;

[0037] After the initialization is completed, the superior sends a command to obtain the power-on test results to the subordinate. The subordinate reports the power-on test results of the resident node and the fault status change information since power-on. The superior sets the subordinate joining status of the reply message to the joined status and records the fault status change information reported by the subordinate into the platform global data recording table.

[0038] Step 4: Complete the handshake between the superior and the whole machine maintenance system, and report the fault status change to the whole machine maintenance system:

[0039] After the initialization is completed, the superior sends online status information to the whole machine maintenance system;

[0040] After receiving the online status information from the superior, the whole machine maintenance system sends a command to the superior, requesting the superior to report the fault status change information since power-on;

[0041] The superior sends the fault status change information in the local global fault data table to the whole machine maintenance system.

[0042] Step 5: During the maintenance and testing phase, complete the recording and reporting of maintenance and testing failures to maintain the continuity of the failures:

[0043] The whole machine maintenance system sends a maintenance test command to the superior, and after the superior receives the maintenance test command from the whole machine maintenance system, the superior sends a maintenance test command to the subordinate it manages;

[0044] The subordinate starts to perform maintenance testing, records the fault status change information detected during the maintenance testing locally, and sends it to the superior. The superior updates the fault status change information to the distributed platform global fault record table and sends it to the whole machine maintenance system;

[0045] The superior waits for the designated maintenance test time and sends a command to obtain the maintenance test result to the subordinate; the subordinate reports the fault information that occurs during the maintenance test to the superior and reports the maintenance test result to the superior;

[0046] The superior will report the collected maintenance test results of the subordinates to the whole machine maintenance system. The maintenance test results are divided into passed and failed. For subordinates who do not respond to the test results, the superior will set their maintenance test results to failed and report the maintenance test results of all nodes to the whole machine maintenance system.

[0047] The purpose of the embodiment of the present invention is to provide a method for implementing unified maintenance and management of fault information of an airborne distributed platform. Based on the hierarchical management and control mechanism of the airborne distributed platform, the unified collection of faults of multiple nodes and heterogeneous nodes in the platform can be realized. The unified collection and management of faults reduces the complexity of interaction and management between each node and the whole machine maintenance system. The unified collection and management of fault information in each stage of initialization, maintenance and operation of the distributed platform ensures that all fault information can be obtained, and the accuracy and continuity of the fault information, such as the state change from no to no fault state and from yes to no fault state. Through the two-level fault information recording method of the upper and lower levels, it is ensured that when the distributed nodes are not powered on synchronously, the fault information sent by the lower level to the upper level is not lost. Through the handshake between the lower level and the upper level, and the two-level handshake mechanism between the upper level and the whole machine maintenance system, it is ensured that the fault information of the entire platform can be fully delivered to the whole machine maintenance system, and the delivered fault data is complete, accurate and not lost, which can finally meet the collection requirements of the whole machine maintenance system for fault state change information, and can provide maintenance personnel with detailed and accurate fault information records.

[0048] The above-mentioned hierarchical management and control mechanism specifically includes:

[0049] The airborne distributed platform contains a large number of resource nodes. In order to manage the platform nodes in a unified manner and reduce the complexity of interaction with the whole-machine maintenance system, the unified maintenance management software for fault information is divided into two levels. The superior is responsible for receiving the maintenance test commands of the whole-machine maintenance system, issuing maintenance test commands to the subordinates, collecting and recording the fault state change information sent by each subordinate, and sending the fault state change information and maintenance test results detected by the entire platform to the whole-machine maintenance system. The subordinate is responsible for detecting and recording the fault state change information of the resident node, and sending the fault state change information to the superior, which is uniformly sent to the whole-machine maintenance system by the superior, receiving the maintenance test commands from the superior, executing maintenance tests, and reporting faults and maintenance results. In the two-level management structure, there is only interaction between the superior and the whole-machine maintenance system, which reduces the complexity of the interaction.

[0050] Next, combine Figure 1-Figure 3 , the unified maintenance and management execution process of fault information of the present invention is further explained.

[0051] (1) Unified maintenance and management of fault information is responsible for the detection, recording and reporting of faults in the entire process of the airborne distributed platform from initialization, normal operation and maintenance. Since it is a distributed platform, the power-on startup and operation time of each node will be different. When the upper node starts running first, the unified maintenance and management software of fault information executes the following sequence: Figure 1 As shown:

[0052] a. The upper node starts initialization and obtains the power-on test results of the lower node. Since the lower node is not online at this time, the upper node cannot receive the lower node's reply. The upper node sets the lower node's joining status that has not replied to the message to the unjoined status. The upper node completes initialization and enters normal operation;

[0053] b. The lower-level node starts initialization, obtains the power-on test results of the resident node, analyzes the test results, and records the fault status change information;

[0054] c. Send a joining request to the superior. After receiving the request, the superior records the subordinate's joining status as joined and replies to the subordinate to allow joining;

[0055] d. The subordinate receives the reply from the superior allowing joining, records its own joining status as joined, completes the handshake between the superior and the subordinate, reports the power-on detection fault status change information of the node to the superior, and the superior records the fault status change information sent by the subordinate;

[0056] e. The subordinate starts the periodic test task, performs periodic fault detection on the resident nodes, records the fault status change information found and reports it to the superior, and the superior updates the recorded fault status change information;

[0057] f. The superior sends online status information to the whole machine maintenance system. After receiving the online status information, the whole machine maintenance system completes the handshake between the superior and the whole machine maintenance system, and sends a command to the superior, requesting the superior to send the fault status change information of the platform since power-on;

[0058] g. The superior reports all the fault status change information of the distributed platform in the global fault record table since the platform was powered on to the whole machine maintenance system, and the whole machine maintenance system records the fault information in the database;

[0059] h. The whole machine maintenance system sends maintenance test commands to the superior;

[0060] i. The superior sends a maintenance test command to the subordinate node it manages;

[0061] j. The subordinate executes the maintenance test command and reports the fault status change information found during the maintenance test to the superior, who records the fault information and reports the fault status change information to the whole machine maintenance system, which records the fault status change information in the database;

[0062] k. After waiting for the maintenance test time, the superior sends a command to obtain the maintenance test results to the subordinates, collects the maintenance test results reported by the subordinates, and modifies the test results of the subordinates that have not responded to the results to failure, and reports the maintenance test results of all nodes to the whole machine maintenance system.

[0063] (2) The lower-level node starts the runtime execution sequence first. Figure 2 As shown:

[0064] a. The lower-level node starts initialization, obtains the power-on test results of the resident node, analyzes the test results, and records fault information;

[0065] b. Send a joining request to the superior. Since the superior is not online, the subordinate cannot receive the superior's permission to join request, and sets its own joining status to the unjoined status. After completing the initialization, start the periodic detection task;

[0066] c. After the subordinate detects a fault in a periodic manner, it records the fault status change information and reports it to the superior;

[0067] d. After startup, the superior sends a message to the subordinate to obtain the power-on test result;

[0068] e. The subordinate receives the power-on test result acquisition message from the superior, sets its own joining status to the joining status, sends the test result message and the fault status change information detected since power-on to the superior, sets its own status to joined, and completes the handshake between the superior and the subordinate;

[0069] f. After the superior receives the reply message of the power-on test result from the subordinate, it sets the subordinate's joining status to the joined status, and after receiving the fault status change information from the subordinate, it records the fault status change information in the distributed platform global fault record table;

[0070] g. The superior sends online status information to the whole machine maintenance system. After receiving the online status information, the whole machine maintenance system completes the handshake between the superior and the whole machine maintenance system, and sends a command to the superior, requesting the superior to send the fault status change information of the platform since power-on;

[0071] h. The superior reports all the fault status change information of the distributed platform in the global fault record table since the platform was powered on to the whole machine maintenance system, and the whole machine maintenance system records the fault information in the database;

[0072] i. The whole machine maintenance system sends maintenance test commands to the superior;

[0073] j. The superior sends maintenance test commands to the subordinate nodes it manages;

[0074] k. The subordinate executes the maintenance test command and reports the fault status change information found during the maintenance test to the superior, who records the fault information and reports the fault status change information to the whole machine maintenance system, which records the fault status change information in the database;

[0075] l. After waiting for the maintenance test time, the superior sends a command to obtain the maintenance test results to the subordinates, collects the maintenance test results reported by the subordinates, and modifies the test results of the subordinates that have not responded to the results to failure, and reports the maintenance test results of all nodes to the whole machine maintenance system.

[0076] Example

[0077] This embodiment includes three parts: introduction to a typical operating environment, information configured in system configuration data, and description of application effects.

[0078] (1) Typical operating environment: There are 5 nodes in the airborne distributed platform. The nodes are divided into two categories: 1 IOM (input and output node), 3 DPMs (data processing nodes), and 1 CMM (central storage node). The upper level is deployed on the IOM node, the lower level is deployed on all nodes, and the whole machine maintenance system is deployed on the CMM node. The upper and lower level deployment relationship of the fault information unified maintenance management control software is as follows: Figure 3 shown.

[0079] In the configuration data, configure the identification number of each lower-level resident node as follows:

[0080] ——IOM node identification number is 1;

[0081] ——DPM1 node identification number is 2;

[0082] ——DPM2 node identification number is 3;

[0083] ——DPM3 node identification number is 4;

[0084] ——The CMM node identification number is 5;

[0085] The fault information that can be detected on each node is:

[0086] ——BIT_CPU_TEST_ITEM, processor test;

[0087] ——BIT_FPU_TEST_ITEM, floating point coprocessor test;

[0088] ——BIT_RAM_TEST_ITEM, random memory test;

[0089] ——BIT_FLASH_TEST_ITEM, FLASH memory test;

[0090] ——BIT_NVRAM_TEST_ITEM, non-volatile memory test;

[0091] ——BIT_INT_TEST_ITEM, interrupt controller test;

[0092] ——BIT_TIMER_TEST_ITEM, timer counter test;

[0093] ——BIT_WATCHDOG_TEST_ITEM, watchdog timer test;

[0094] ——BIT_MMST_TEST_ITEM, electronic disk storage function failure.

[0095] (2) The contents configured in the system configuration data include:

[0096] The management structure is configured in the system-level configuration data, and the superior directly manages the subordinates 1, 2, 3, 4, and 5;

[0097] In the upper-level attribute configuration, configure the upper-level deployment on the IOM module;

[0098] In the upper-level property configuration, configure the maintenance test waiting time to 30 seconds;

[0099] (3) The specific application effects are:

[0100] After the distributed platform is powered on, follow the steps below to perform unified maintenance and management of fault information:

[0101] a. Each module starts running, and the upper, lower and whole machine maintenance systems are initialized respectively;

[0102] b. The lower level on the three DPM modules starts up first and obtains the power-on test results. The power-on test on DPM1 fails. The failed item is the BIT_NVRAM_TEST_ITEM test item. The lower level on DPM1 records the NVRAM fault status change information, which includes:

[0103] ——Fault code NVRAM_FAULT, value is 32;

[0104] ——The number of faults from no fault to fault is 1;

[0105] ——the fault state is present;

[0106] ——The fault type is a hard fault;

[0107] ——The fault occurred at 11:12:34.

[0108] c. The subordinates on the three DPM modules that have been started first send a joining request to the superior. If no reply is received from the superior allowing joining, the record status is not joined. The three subordinates start the periodic test tasks and enter the normal operation stage;

[0109] d. During the periodic detection of the DPM1 module, the BIT_NVRAM_TEST_ITEM test item does not detect any faults, and the fault status change information is recorded at this level, including the following contents:

[0110] ——Fault code NVRAM_FAULT, value is 32;

[0111] ——The number of faults from no fault to fault is 1;

[0112] ——The fault status is non-existent;

[0113] ——The fault type is intermittent fault;

[0114] ——The fault disappeared at 11:12:36;

[0115] e. When the upper level residing on the IOM completes initialization, it sends a message to the five lower levels to obtain the power-on test result. After receiving the message, the lower levels residing on the IOM node and the three DPM nodes update the joining status to the joined status and reply to the upper level with the power-on test result. The lower level residing on the DPM1 node sends the NVRAM fault status change information since power-on. The upper level records the fault information in the distributed platform global fault record table, which includes the following information:

[0116] ——The ID of the failed node DPM1, the value is 2;

[0117] ——Fault code NVRAM_FAULT, value is 32;

[0118] ——The number of faults from no fault to fault is 1;

[0119] ——The fault status is non-existent;

[0120] ——The fault type is intermittent fault;

[0121] ——The fault disappeared at 11:12:36;

[0122] f. The initialization of the whole machine maintenance system residing on the CMM module is completed, and the initialization of the lower level residing on the CMM module is completed. The power-on result is checked and it is found that the BIT_FLASH_TEST_ITEM test fails. The FLASH fault status change information is recorded locally, including the following information:

[0123] ——Fault code FLASH_FAULT, value is 16;

[0124] ——The number of faults from no fault to fault is 1;

[0125] ——the fault state is present;

[0126] ——The fault type is a hard fault;

[0127] ——The fault occurred at 11:12:37.

[0128] g. The subordinate residing on the CMM node sends a joining request to the superior. After receiving the superior's reply of allowing joining, it records its own joining status as joined and sends the FLASH fault status change information to the superior. The superior records the fault status change information into the local global fault data, which includes the following information:

[0129] ——The ID of the CMM of the node where the failure occurred, the value is 5;

[0130] ——Fault code FLASH_FAULT, value is 16;

[0131] ——The number of faults from no fault to fault is 1;

[0132] ——the fault state is present;

[0133] ——The fault type is a hard fault;

[0134] ——The fault occurred at 11:12:37.

[0135] h. The superior sends online status information to the whole machine maintenance system residing on the CMM module, and the whole machine maintenance system sends a command to the superior, requiring the superior to report the fault status change information that has occurred on the platform since power-on;

[0136] i. The superior sends the fault status change information that has occurred since power-on, including the NVRAM fault status change information on the DPM1 module and the FLASH fault status change information on the CMM module, to the whole machine maintenance system, and the whole machine maintenance system records the fault status change information in the database;

[0137] j. The whole machine maintenance system sends a maintenance test command to the superior residing on the IOM, and the superior sends a maintenance test command to all five subordinates;

[0138] k. The subordinate node starts to perform maintenance testing. When performing maintenance testing, the subordinate residing on DPM1 finds a RAM_FAULT fault in addition to NVRAM_FAULT. The subordinate residing on DPM1 updates the local fault status change record, which contains the following information:

[0139] ——Fault code RAM_FAULT, value is 8;

[0140] ——The number of faults from no fault to fault is 1;

[0141] ——the fault state is present;

[0142] ——The fault type is a hard fault;

[0143] ——The fault occurred at 11:14:50;

[0144] 1. The subordinate residing on DPM1 sends the fault information to the superior, and the superior records the fault in the distributed platform global fault record table and sends it to the whole machine maintenance system at the same time, including the following information:

[0145] ——The ID of the failed node DPM1, the value is 2;

[0146] ——Fault code RAM_FAULT, value is 8;

[0147] ——The number of faults from no fault to fault is 2;

[0148] ——the fault state is present;

[0149] ——The fault type is a hard fault;

[0150] ——The fault occurred at 11:14:50;

[0151] m. The CMM module found no fault during maintenance testing, and updated the previously discovered FLASH fault information and reported it to the superior. The updated content is:

[0152] ——Fault code FLASH_FAULT, value is 16;

[0153] ——The number of faults from no fault to fault is 1;

[0154] ——The fault status is non-existent;

[0155] ——The fault type is intermittent fault;

[0156] ——The fault disappeared at 11:14:45;

[0157] n. After receiving the fault status change information from the CMM, the superior updates the content in the local global fault record and reports the fault status change information to the whole machine maintenance system, including:

[0158] ——The ID of the CMM of the node where the failure occurred, the value is 5;

[0159] ——Fault code FLASH_FAULT, value is 16;

[0160] ——The number of faults from no fault to fault is 1;

[0161] ——The fault status is non-existent;

[0162] ——The fault type is intermittent fault;

[0163] ——The fault disappeared at 11:14:45;

[0164] o. No faults were found during the maintenance test of other lower-level nodes. After waiting for 30 seconds, the upper level sent a maintenance test result reporting command to the lower-level nodes, received the lower-level maintenance test results, and except for the DPM1 module test result which failed, the test results of other modules passed. All module test results were sent to the whole machine maintenance system to complete this maintenance test.

[0165] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A unified maintenance management method for fault information based on an airborne distributed platform, characterized in that: include: The system management software is configured as an upper level and a plurality of lower level nodes managed by the upper level in the configuration data of the airborne distributed platform, and the upper level and the lower level respectively perform an initialization process after power-on and then enter a normal operation state; The lower level obtains the power-on test results of each resident node, detects and records the fault status change information; The subordinate sends a joining request to the superior. After receiving the joining request, the superior records the subordinate's joining status as joined and replies to the subordinate to allow joining. After receiving the reply from the superior allowing joining, the subordinate records its joining status as joined, completes the handshake between the superior and the subordinate, and reports the recorded power-on detection fault state change information to the superior, and the superior records the fault state change information sent by the subordinate; The superior sends online status information to the whole-machine maintenance system of the airborne distributed platform, and after the whole-machine maintenance system receives the online status information, the superior completes the handshake with the whole-machine maintenance system; The whole machine maintenance system sends a command to the superior, requesting the superior to send the fault status change information of the platform after power-on, and the superior reports the recorded fault status change information after power-on to the whole machine maintenance system; The initialization process includes: After the upper level is powered on, the power-on test result of the lower level is obtained. If no power-on reply is received from the lower level, the lower level joining state is set to the non-joining state, the initialization process is completed, and then the normal operation state is entered; After the subordinate is powered on, it obtains the power-on test results of the resident node, detects and records the fault state change information; at the same time, it sends a joining request to the superior. If it does not receive a reply from the superior allowing joining, it sets its own joining state to the non-joining state, completes the initialization process, and starts the detection task; After the lower level completes the initialization process, it obtains the power-on test result of the resident node, performs periodic detection, records the fault status change information and reports it to the upper level; It also includes: when the subordinate is powered on first and the superior is powered on later, the superior sends an instruction to the subordinate, requiring the subordinate to report all test results since power-on, and the subordinate reports all fault status change information recorded since power-on to the superior.

2. The method for unified maintenance and management of fault information based on an airborne distributed platform according to claim 1, characterized in that: Also includes, The whole-machine maintenance system sends a maintenance test command to the superior, the superior sends the maintenance test command to the subordinate, the subordinate executes the maintenance test command, reports the fault state change information detected during the maintenance test process to the superior, the superior records the fault state change information, and reports the fault state change information to the whole-machine maintenance system.

3. The method for unified maintenance and management of fault information based on an airborne distributed platform according to claim 2, characterized in that: Also includes, After waiting for the set maintenance test time, the superior sends a command to obtain maintenance test results to the subordinate, and the subordinate reports the recorded maintenance test results to the superior.

4. The method for unified maintenance and management of fault information based on an airborne distributed platform according to claim 3, characterized in that: After the superior sends a command to obtain maintenance test results to the subordinate, if the superior does not receive the maintenance test results reported by the subordinate, the subordinate's test results are modified to failure, and all maintenance test results are reported to the whole machine maintenance system.

5. The method for unified maintenance and management of fault information based on an airborne distributed platform according to claim 2, characterized in that: The whole machine maintenance system records the received fault status change information into a database.

Images