Fault logic configuration system and method based on database

Abstract

The invention provides a fault logic configuration system and method based on a database, and relates to the technical field of airborne maintenance systems, and the system comprises a fault data source module which is used for providing a fault variable required by logic operation; the fault logic module is used for performing logic operation on the fault variables to form a real-time fault diagnosis result; the fault report module is used for receiving the real-time fault diagnosis result and forming a fault diagnosis result record and fault report information according to the real-time fault diagnosis result; and the common component module is used for providing a logic coincidence table and a data type table for the fault data source module and the fault logic module. According to the system, a database relation table design is adopted, and faults can be checked, added, deleted and modified conveniently in the using process; and meanwhile, a fault diagnosis related process is subjected to configurable design from a fault data source to fault logic and then to a fault diagnosis result and a fault report, so that loose coupling of the fault logic and a fault diagnosis program is realized.

Description

Technical Field

[0001] The invention relates to the technical field of airborne maintenance systems, and in particular provides a database-based fault logic configuration system and configuration method. Background Art

[0002] The onboard maintenance system is responsible for the maintenance of the aircraft and is mainly used for the maintenance of the aircraft and its component systems. Fault diagnosis and isolation are the core functions of the onboard maintenance system, which is used for fault analysis and location of aircraft systems. It is related to the improvement of aircraft dispatch rate and has very important economic value for airlines.

[0003] The fault diagnosis function of the onboard maintenance system mainly relies on the input of the member system fault report, so the formation of the member system fault report is related to the success or failure of the fault diagnosis function. Fault logic is the basis of fault diagnosis. In order to improve the fault diagnosis capability of the member system, it is particularly necessary to increase the number of fault logics to cover all fault points as much as possible.

[0004] The existing fault logic design methods mainly adopt programming or text configuration. However, the programming method cannot meet the requirement of fault logic extensibility. The fault logic designed by the text file configuration method is not readable enough. Summary of the invention

[0005] The purpose of this application is to solve the problem that logical failures are not easy to expand.

[0006] In order to achieve the above object, the present invention adopts the following technical solution: a fault logic configuration system based on a database, the system comprising:

[0007] A fault data source module is used to provide fault variables required for logical operations;

[0008] Fault logic module, used to perform logical operations on fault variables to form real-time fault diagnosis results;

[0009] a fault reporting module, configured to receive the real-time fault diagnosis result formed by the fault logic module, and to form a fault diagnosis result record and fault reporting information according to the real-time fault diagnosis result; and

[0010] The common component module is used to provide a logic compliance table and a data type table for the fault data source module and the fault logic module.

[0011] The database-based fault logic configuration system provided by the present invention also has such a technical feature that the fault data source module includes a fault message table, a fault data table and a fault variable table.

[0012] The fault message table includes all fault messages of the onboard system;

[0013] The fault data table includes the fault data contained in the fault message;

[0014] The fault variable table includes system fault variables.

[0015] The database-based fault logic configuration system provided by the present invention also has such a technical feature that the fault logic module includes a fault logic information table and a fault logic table.

[0016] The fault logic table includes the fault logic required for diagnosis of the airborne system;

[0017] The fault logic table includes basic information of fault logic.

[0018] The database-based fault logic configuration system provided by the present invention also has such a technical feature that the fault logic includes a fault logic ID, a fault variable ID and a logical operator.

[0019] The basic fault information includes a fault logic ID and a logic expression.

[0020] The database-based fault logic configuration system provided by the present invention also has such a technical feature that the fault reporting module includes a fault report message table, a fault message variable table and a fault diagnosis result table.

[0021] The fault report message table is associated with the fault message variable table through the fault report message ID;

[0022] The fault message variable table includes a set of fault variables contained in the fault report message;

[0023] The fault diagnosis result table includes a fault logic diagnosis result ID and a fault diagnosis result.

[0024] The database-based fault logic configuration system provided by the present invention also has such a technical feature that the common component module includes a logic symbol table and a data type table,

[0025] The logic symbol table includes logic symbols required for performing logic operations.

[0026] Another object of the present invention is to provide a database-based fault logic configuration method, the method being implemented based on any of the aforementioned fault logic configuration systems, comprising:

[0027] S1: Establish a database table in the fault data source module;

[0028] S2: Establishing the database table in the fault logic module;

[0029] S3: Establishing a database table in the fault reporting module;

[0030] S4: Establish database tables in the common component module.

[0031] The database-based fault logic configuration method provided by the present invention also has the following technical features: S1 comprises:

[0032] S1.1: Add fault message IDs to all fault messages of the airborne system, create a fault message table, add message names and message lengths, and obtain a fault message table;

[0033] S1.2: select a fault message from the fault message table formed in S1.1, split all fault data bits of the selected fault message and create a fault data table;

[0034] S1.3: Select any fault variable corresponding to the fault message selected in S1.2, select the fault data bit and logical relationship according to the fault variable definition, generate a fault variable table, and add the fault variable ID, fault data ID and logical operator;

[0035] S1.4: Repeat S1.3 until all fault variables corresponding to the fault message have been created in the fault variable table;

[0036] S1.5: Repeat S1.2 to S1.4 until the fault data table and fault variable table corresponding to the fault messages in all fault message tables have been established.

[0037] The database-based fault logic configuration method provided by the present invention also has the following technical features: S2 includes:

[0038] S2.1: Create a fault logic information table based on all fault logics recorded in the system;

[0039] S2.2: Select any fault logic from the fault logic information table created in S2.1, and add the corresponding fault logic expression of the fault logic;

[0040] S2.3: According to the fault logic expression supplemented in S2.2, create the fault variable ID and logic operator corresponding to the fault logic in the fault logic table;

[0041] S2.3: Repeat S2.2 to S2.3 until all fault logics have been established in the fault logic table.

[0042] The database-based fault logic configuration method provided by the present invention also has the following technical features: S3 includes:

[0043] S3.1: Establish a corresponding fault diagnosis result table according to the fault logic table established by the fault logic module;

[0044] S3.2: Select any logical fault in the fault diagnosis result table established in S3.1 and add the fault diagnosis result;

[0045] S3.3: Map the fault diagnosis results added in S3.2 to fault variables and create a fault variable table;

[0046] S3.4: According to the system interface definition, the fault variable is assigned to the fault report message, and the offset of the corresponding fault variable in the fault message and the fault message ID in the fault variable message table are supplemented;

[0047] S3.5: Repeat S3.2 to S3.4 until all attributes of the fault diagnosis result table have been added and the fault message variables corresponding to the fault diagnosis result table have been defined in the fault message variable table;

[0048] S3.6: Create a fault report message table based on all fault report messages.

[0049] Beneficial Effects

[0050] The database-based fault logic configuration system provided by the present invention adopts a database relational table design, which is convenient for viewing, adding, deleting and modifying faults during use; at the same time, the fault diagnosis-related processes from the fault data source to the fault logic, and then to the fault diagnosis results and fault report are configurable, realizing loose coupling between the fault logic and the fault diagnosis program.

[0051] The database-based fault logic configuration method provided by the present invention can realize the diagnosis of different faults only by adding corresponding fault logics while keeping the airborne system fault diagnosis method architecture or program unchanged, and at the same time report the diagnosis results to the airborne maintenance system, thereby effectively solving the fault diagnosis problem of the airborne system. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, 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 disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0053] Figure 1 The following is an architecture diagram of the system provided by the embodiment of the present invention. DETAILED DESCRIPTION

[0054] The present application is further described in detail below in conjunction with the accompanying drawings and examples, but it should be noted that these implementation methods are not limitations of the present application, and equivalent changes or substitutions in functions, methods, or structures made by ordinary technicians in the field based on these implementation methods are all within the scope of protection of the present application.

[0055] In the description of the embodiments of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing the creation of the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the creation of the present application.

[0056] In addition, the terms "first", "second", "third", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", etc. may explicitly or implicitly include one or more of the features. In the description of the invention of this application, unless otherwise specified, the meaning of "plurality" is two or more.

[0057] The terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the invention of this application can be understood by specific circumstances.

[0058] like Figure 1 As shown, an embodiment of the present application provides a database-based fault logic configuration system, the system comprising:

[0059] A fault data source module 101 is used to provide fault variables required for logic operations;

[0060] The fault logic module 102 is used to perform logic operations on the fault variables to form real-time fault diagnosis results;

[0061] A fault reporting module 103, configured to receive the real-time fault diagnosis result formed by the fault logic module, and to form a fault diagnosis result record and fault report information according to the real-time fault diagnosis result; and

[0062] The common component module 104 is used to provide a logic matching table and a data type table for the fault data source module 101 and the fault logic module 102 .

[0063] In the above embodiment, the fault data source module 101 provides the fault logic module 102 with the fault variables required for logical operations, and the fault variables are obtained by using the logic compliance table and data type table provided by the common component module 104 and the fault data logical operation. The fault logic module 102 performs a logical operation on the fault variables of the fault data source module 101 by using the function of the common component module 104 to form a real-time fault diagnosis result. The diagnosis result is used as the input of the fault reporting module 103 to form a fault diagnosis result record and a fault report message. The present invention splits the fault message into fault variables, and then forms a fault report through fault logical operations, and finally realizes the fault reporting and fault recording to the airborne maintenance system.

[0064] In some embodiments, the fault data source module 101 includes a fault message table, a fault data table, and a fault variable table.

[0065] The fault message table includes all fault messages of the airborne system, which is a collection of system fault messages, including basic information such as fault message ID and length;

[0066] The fault data table includes fault data included in the fault message, wherein each fault data has information such as a fault data ID, a corresponding fault message, and an offset;

[0067] The fault variable table includes system fault variables, which are logical expressions of fault data. Fault variables include information such as fault variable ID, fault data ID, and logical operators. The fault variable table can realize the configuration of variables required for system fault diagnosis.

[0068] In some embodiments, the fault logic module 102 includes a fault logic information table and a fault logic table.

[0069] The fault logic table includes the fault logic required for diagnosis of the airborne system. The fault logic is the core of fault diagnosis. Different faults can be diagnosed by configuring different fault logics.

[0070] The fault logic table includes basic information of fault logic.

[0071] In some embodiments, the fault logic includes a fault logic ID, a fault variable ID, and a logical operator.

[0072] The basic fault information includes a fault logic ID and a logic expression.

[0073] In some embodiments, the fault reporting module 103 includes a fault report message table, a fault message variable table, and a fault diagnosis result table.

[0074] The fault report message table is a set of fault report messages that need to be reported to the airborne maintenance system, and the fault report message table is associated with the fault message variable table through the fault report message ID;

[0075] The fault message variable table includes a set of fault variables contained in the fault report message, and the fault variables include information such as fault variable ID, fault diagnosis result and offset;

[0076] The fault diagnosis result table includes a fault logic diagnosis result ID and a fault diagnosis result.

[0077] In some embodiments, the common component module 104 includes a logic symbol table and a data type table.

[0078] The logic symbol table includes logic symbols required for logic operations. The logic symbol table is the logic symbols required for logic operations, typically "and", "or", "not", etc. The data type table represents different types of data, typically "enumeration", "integer", "floating point", etc.

[0079] In some embodiments, a database-based fault logic configuration method is provided, the method being implemented based on any of the above-mentioned fault logic configuration systems, including:

[0080] S1: Establish a database table in the fault data source module;

[0081] S2: Establishing the database table in the fault logic module;

[0082] S3: Establishing a database table in the fault reporting module;

[0083] S4: Establish database tables in the common component module.

[0084] In some embodiments, the S1 includes:

[0085] S1.1: Add fault message IDs to all fault messages of the airborne system, create a fault message table, add message names and message lengths, and obtain a fault message table;

[0086] S1.2: select a fault message from the fault message table formed in S1.1, split all fault data bits of the selected fault message and create a fault data table;

[0087] S1.3: Select any fault variable corresponding to the fault message selected in S1.2, select the fault data bit and logical relationship according to the fault variable definition, generate a fault variable table, and add the fault variable ID, fault data ID and logical operator;

[0088] S1.4: Repeat S1.3 until all fault variables corresponding to the fault message have been created in the fault variable table;

[0089] S1.5: Repeat S1.2 to S1.4 until the fault data table and fault variable table corresponding to the fault messages in all fault message tables have been established.

[0090] In some embodiments, the S2 includes:

[0091] S2.1: Create a fault logic information table based on all fault logics recorded in the system;

[0092] S2.2: Select any fault logic from the fault logic information table created in S2.1, and add the corresponding fault logic expression of the fault logic;

[0093] S2.3: According to the fault logic expression supplemented in S2.2, create the fault variable ID and logic operator corresponding to the fault logic in the fault logic table;

[0094] S2.3: Repeat S2.2 to S2.3 until all fault logics have been established in the fault logic table.

[0095] In some embodiments, S3 includes:

[0096] S3.1: Establish a corresponding fault diagnosis result table according to the fault logic table established by the fault logic module;

[0097] S3.2: Select any logical fault in the fault diagnosis result table established in S3.1 and add the fault diagnosis result;

[0098] S3.3: Map the fault diagnosis results added in S3.2 to fault variables and create a fault variable table;

[0099] S3.4: According to the system interface definition, the fault variable is assigned to the fault report message, and the offset of the corresponding fault variable in the fault message and the fault message ID in the fault variable message table are supplemented;

[0100] S3.5: Repeat S3.2 to S3.4 until all attributes of the fault diagnosis result table have been added and the fault message variables corresponding to the fault diagnosis result table have been defined in the fault message variable table;

[0101] S3.6: Create a fault report message table based on all fault report messages.

[0102] In some embodiments, the S4 includes:

[0103] S4.1: Create a logic symbol table based on the fault variable table of the fault data source module and all the category logic operators used in the fault logic table of the fault logic module.

[0104] S4.2: Create a data type table for all data types in the fault data table of the fault data source module.

[0105] The above is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the protection scope of the present application. The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and variations can be made without departing from the technical principles of the present application, and these improvements and variations should also be regarded as the protection scope of the present application.

Claims

1. A database-based fault logic configuration system, characterized in that: The system comprises: A fault data source module is used to provide fault variables required for logical operations; Fault logic module, used to perform logical operations on fault variables to form real-time fault diagnosis results; a fault reporting module, configured to receive the real-time fault diagnosis result formed by the fault logic module, and to form a fault diagnosis result record and fault reporting information according to the real-time fault diagnosis result; and The common component module is used to provide a logic compliance table and a data type table for the fault data source module and the fault logic module.

2. The database-based fault logic configuration system according to claim 1, characterized in that: The fault data source module includes a fault message table, a fault data table and a fault variable table. The fault message table includes all fault messages of the onboard system; The fault data table includes fault data contained in the fault message; The fault variable table includes system fault variables.

3. The database-based fault logic configuration system according to claim 1, characterized in that: The fault logic module includes a fault logic information table and a fault logic table. The fault logic table includes the fault logic required for diagnosis of the airborne system; The fault logic table includes basic information of fault logic.

4. The database-based fault logic configuration system according to claim 3, characterized in that: The fault logic includes a fault logic ID, a fault variable ID and a logical operator. The basic fault information includes a fault logic ID and a logic expression.

5. The database-based fault logic configuration system according to claim 1, characterized in that: The fault reporting module includes a fault reporting message table, a fault message variable table and a fault diagnosis result table. The fault report message table is associated with the fault message variable table through the fault report message ID; The fault message variable table includes a set of fault variables contained in the fault report message; The fault diagnosis result table includes a fault logic diagnosis result ID and a fault diagnosis result.

6. The database-based fault logic configuration system according to claim 1, characterized in that: The common component module includes a logic symbol table and a data type table, The logic symbol table includes logic symbols required for performing logic operations.

7. A fault logic configuration method based on a database, characterized in that: The method is implemented based on the fault logic configuration system according to any one of claims 1 to 6, and includes: S1: Establish a database table in the fault data source module; S2: Establishing the database table in the fault logic module; S3: Establishing a database table in the fault reporting module; S4: Establish database tables in the common component module.

8. The database-based fault logic configuration method according to claim 7, characterized in that: The S1 includes: S1.1: Add fault message IDs to all fault messages of the airborne system, create a fault message table, add message names and message lengths, and obtain a fault message table; S1.2: select a fault message from the fault message table formed in S1.1, split all fault data bits of the selected fault message and create a fault data table; S1.3: Select any fault variable corresponding to the fault message selected in S1.2, select the fault data bit and logical relationship according to the fault variable definition, generate a fault variable table, and add the fault variable ID, fault data ID and logical operator; S1.4: Repeat S1.3 until all fault variables corresponding to the fault message have been created in the fault variable table; S1.5: Repeat S1.2 to S1.4 until the fault data table and fault variable table corresponding to the fault messages in all fault message tables have been established.

9. The method for configuring fault logic based on a database according to claim 7, characterized in that: The S2 includes: S2.1: Create a fault logic information table based on all fault logics recorded in the system; S2.2: Select any fault logic from the fault logic information table created in S2.1, and add the corresponding fault logic expression of the fault logic; S2.3: According to the fault logic expression supplemented in S2.2, create the fault variable ID and logic operator corresponding to the fault logic in the fault logic table; S2.3: Repeat S2.2 to S2.3 until all fault logics have been established in the fault logic table.

10. The method for configuring fault logic based on a database according to claim 7, characterized in that: The S3 includes: S3.1: Establish a corresponding fault diagnosis result table according to the fault logic table established by the fault logic module; S3.2: Select any logical fault in the fault diagnosis result table established in S3.1 and add the fault diagnosis result; S3.3: Map the fault diagnosis results added in S3.2 to fault variables and create a fault variable table; S3.4: According to the system interface definition, the fault variable is assigned to the fault report message, and the offset of the corresponding fault variable in the fault message and the fault message ID in the fault variable message table are supplemented; S3.5: Repeat S3.2 to S3.4 until all attributes of the fault diagnosis result table have been added and the fault message variables corresponding to the fault diagnosis result table have been defined in the fault message variable table; S3.6: Create a fault report message table based on all fault report messages.

Images