A multi-level management method for NVM of flight control computer

Abstract

The present application provides a flight control computer NVM multi-level management method, the method comprising: dividing the NVM memory into multiple NVM areas based on the characteristics of the storage content; configuring a corresponding processing strategy for each NVM area; wherein the processing strategy is generated based on the characteristics of the storage content; after the implementation of the multi-level management strategy provided by the present application, different processing strategies can be formulated for different storage objects, thereby solving the conflict and coupling problems of NVM requirements for different types of data in the flight control system.

Description

Technical Field

[0001] The present application belongs to the technical field of flight control systems, and in particular, relates to a multi-level management method for NVM of a flight control computer. Background Art

[0002] The non-volatile memory (NVM) in the flight control computer is usually used to store important flight parameters and fault information during flight. After the flight, the data in the NVM can be used for fault location, maintenance and repair, and accident analysis in extreme cases.

[0003] The typical use of NVM by the flight control system is to record flight parameters and faults during flight, read data through ground maintenance equipment after the flight is completed, and issue a clear fault command through the ground maintenance equipment after the data is read. The flight control onboard software clears the NVM area after receiving the request. The clearing operation is usually completed by maintenance personnel before the next flight after the data and fault analysis of the previous flight is completed.

[0004] As the flight control system functions are enhanced, the use scenarios of NVM in the flight control onboard software are more diversified. The above-mentioned single use and management strategy of NVM increasingly restricts the expansion of system functions and the convenience of maintenance. Summary of the invention

[0005] In view of the above technical problems, the present application provides a flight control computer NVM multi-level management method, the method comprising:

[0006] Based on the characteristics of the storage content, the NVM memory is divided into multiple NVM areas;

[0007] A corresponding processing strategy is configured for each NVM area; wherein the processing strategy is generated based on the characteristics of the storage content.

[0008] Preferably, the NVM area includes a fault list area, a flight parameter area, a control surface zero offset area and a software anomaly area.

[0009] Preferably, the processing strategy includes:

[0010] A first processing strategy, for the fault list area;

[0011] a second processing strategy for the flight parameter region;

[0012] A third processing strategy is used for the control surface zero offset area;

[0013] The fourth processing strategy is used for the software exception area.

[0014] Preferably, the processing strategy is used to retain the data stored in the NVM area after the flight control system loses power and then recovers.

[0015] Preferably, the first processing strategy is used to clear the data in the fault list area based on the area clearing condition when starting on the ground;

[0016] The area clearing conditions include: a clearing instruction issued by ground maintenance equipment, or an NVM fault recognized by the flight control onboard software.

[0017] Preferably, the second processing strategy is used to clear the data in the flight parameter area based on the area clearing condition when started on the ground;

[0018] The area clearing conditions include: a clearing instruction issued by ground maintenance equipment, or the flight control onboard software identifying an NVM fault;

[0019] The second processing strategy is also used to initialize the parameters to the state required by the flight control system after it is started on the ground.

[0020] Preferably, the third processing strategy is used to rewrite the rudder surface zero position offset when a rudder surface zeroing instruction is received from ground maintenance equipment.

[0021] Preferably, the fourth processing strategy is used to clear the data in the software abnormal area when the flight control onboard software identifies an NVM fault.

[0022] Beneficial technical effects of this application:

[0023] After the multi-level management strategy provided by the present application is implemented, different processing strategies can be formulated for different storage objects, solving the conflict and coupling problems of NVM requirements for different types of data in the flight control system. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 A schematic diagram of a multi-level management method for NVM of a flight control computer provided in an embodiment of the present application;

[0025] Figure 2 A schematic diagram of another flight control computer NVM multi-level management method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0027] In this application, a multi-level management strategy for the flight control computer NVM is proposed. Based on this strategy, the NVM storage area can be partitioned / blocked according to the content and object characteristics recorded in the NVM, and different processing strategies can be implemented for NVMs in different blocks.

[0028] It should be noted that the key points of the technical solution of this application are as follows: Figure 1 ):

[0029] 1) According to different characteristics of the content that the NVM needs to record, the NVM memory is divided into several areas: NVM area 1, NVM area 2, ..., NVM area N.

[0030] 2) Formulate a corresponding processing strategy for each area: NVM processing strategy 1, NVM processing strategy 2, ..., NVM processing strategy N.

[0031] 3) In the implementation of the flight control onboard software, the division of the NVM area needs to be used in conjunction with the corresponding processing strategy (that is, different NVM areas adopt their own processing strategies) to complete the NVM multi-level management strategy.

[0032] Among them, after the multi-level management strategy of the invention is implemented, different processing strategies can be formulated for different storage objects, solving the conflict and coupling problems of NVM requirements for different types of data in the flight control system.

[0033] This method has been applied to the flight control systems of multiple aircraft, helping to expand system functions and enhance maintainability, and reducing system complexity due to the decoupling design.

[0034] In other embodiments of the present application, the specific steps are as follows:

[0035] Step 1: According to the characteristics of the content that the NVM needs to record, the NVM memory is divided into four areas, namely:

[0036] NVM area 1: Fault list area.

[0037] Among them, the NVM area stores detailed information on the occurrence and recovery of faults during flight and detailed results of pre-flight self-tests; after a failure of the flight control system, the detailed content of the fault in the fault list (such as fault type, occurrence time, etc.) can be used to further analyze and locate the fault; when the aircraft is on the ground, the fault list can be obtained through ground maintenance equipment.

[0038] NVM area 2: flight parameters area.

[0039] Among them, the NVM area stores important aircraft status information (such as sensor voting values, intermediate states of control law calculations, etc.); after the flight control system loses power in the air and recovers quickly, the flight parameters stored in the NVM area can help the flight control system restore the state before the power failure and continue to effectively control the aircraft.

[0040] NVM area 3: rudder zero offset area.

[0041] Among them, due to reasons such as manufacturing process accuracy and installation errors on the aircraft, there may be errors in the mechanical zero position of the rudder after installation, and the zero position errors of the rudders of the same model and different aircraft may be different. In order to achieve a more accurate control effect, the zero position error of the rudder is measured after installation, and the measurement results are recorded.

[0042] Among them, the NVM area is used to store the zero-position error of the rudder surface, and introduce the zero-position error of the rudder surface installation into the control command to "eat up" the error and achieve a more precise control effect.

[0043] NVM area 4: software exception area.

[0044] Among them, the flight control onboard software is safety-critical software and has undergone rigorous testing and verification. However, the technical characteristics of the software itself determine that it can never be proved that the software is absolutely correct. In order to prevent software anomalies from occurring during the operation of the onboard software, the flight control onboard software has been specially designed. That is, after an abnormality occurs in the software operation, the flight control onboard software will record the abnormal scene for subsequent analysis and improvement.

[0045] The NVM area is used to store software abnormality site information, which is the main basis for further troubleshooting and analysis. For some extremely rare occasional failures, the site information is even more valuable.

[0046] Step 2: formulate corresponding processing strategies according to the characteristics of the storage content and objects in each NVM area. The division of NVM areas / blocks needs to be used in conjunction with the corresponding processing strategies. Specifically:

[0047] Processing strategy 1 (applicable to the fault list area)

[0048] Among them, the content of this area is retained when started in the air; the clearing conditions are judged when started on the ground. The area clearing conditions applicable to this strategy include: Condition 1, which can be cleared by a clearing command issued by ground maintenance equipment; Condition 2, which is cleared when the flight control onboard software recognizes an NVM fault.

[0049] Processing strategy 2 (applicable to flight parameter area)

[0050] Among them, the content of this area is retained when started in the air; the clearing conditions are judged when started on the ground. The area clearing conditions applicable to this strategy include: Condition 1, which can be cleared by a clearing command issued by ground maintenance equipment; Condition 2, which is cleared when the flight control onboard software recognizes an NVM fault.

[0051] Among them, if the conditions for clearing the area are met during ground startup, the flight control system parameters will be initialized to the state required after ground startup after clearing (for example, the wheel load voting value needs to be initialized to "ground", the landing gear voting value needs to be initialized to "down", etc.).

[0052] Processing strategy 3 (applicable to the zero offset area of ​​the rudder surface)

[0053] The content of the area to which this strategy applies is only rewritten when a control surface zeroing command is received from ground maintenance equipment; otherwise, the content of the area is permanently retained. This ensures that the content of the control surface offset area of ​​each aircraft is not accidentally modified.

[0054] Processing strategy 4 (applicable to software abnormal area)

[0055] The content of the area to which this strategy applies is only cleared when the flight control onboard software identifies an NVM fault; otherwise, it is never cleared. This way, valuable abnormal field data can be retained to prevent accidental clearing. After such a fault occurs, the flight control computer should be returned for inspection immediately.

[0056] It should be noted that 1) the purpose is to partition / block the NVM storage area, and the specific partitioning method can be (but not limited to) one or a combination of the following methods: multiple chips, FPGA logic partitioning, link configuration partitioning, static array partitioning in source code, etc. 2) From the perspective of design flexibility, the above-mentioned multiple processing strategies do not require to be completely different.

[0057] The above is only a specific embodiment of the present invention, and the present invention is described in detail. The unexplained part is a conventional technology. However, the protection scope of the present invention is not limited to this. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. The protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A flight control computer NVM multi-level management method, characterized in that: The method comprises: Based on the characteristics of the stored content, the NVM memory is divided into a plurality of NVM areas; wherein the NVM areas include a fault list area, a flight parameter area, a control surface zero offset area, and a software anomaly area; A corresponding processing strategy is configured for each NVM area; wherein the processing strategy is generated based on the characteristics of the storage content, and the processing strategy includes: A first processing strategy, for the fault list area; a second processing strategy for the flight parameter region; A third processing strategy is used for the control surface zero offset area; A fourth processing strategy is used for the software exception area; The first processing strategy is used to clear the data in the fault list area based on the area clearing condition when starting on the ground; wherein the area clearing condition includes: a clearing instruction issued by ground maintenance equipment, or the flight control onboard software identifies an NVM fault; The second processing strategy is used to clear the data in the flight parameter area based on the area clearing condition when started on the ground; wherein the area clearing condition includes: a clearing instruction issued by the ground maintenance equipment, or the flight control onboard software identifies an NVM fault; The second processing strategy is also used to initialize the parameters to the state required by the flight control system after starting on the ground; The third processing strategy is used to rewrite the rudder surface zero position offset when receiving a rudder surface zeroing instruction issued by ground maintenance equipment; The fourth processing strategy is used to clear the data in the software abnormal area when the flight control onboard software identifies an NVM fault.

2. The method according to claim 1, characterized in that The processing strategy is used to retain the data stored in the NVM area after the flight control system loses power and then recovers.

Images