A method for encoding faults in communication of a control system

Abstract

The application discloses a fault coding method for communication of a control system, and is applied to a full authority digital electronic controller (FADEC) of an aero-engine, and comprises the following steps: dividing engine faults into a plurality of predetermined safety influence level categories according to the influence degree of the engine faults on flight safety; meanwhile, dividing an engine system into a plurality of subsystems according to the physical or functional composition of the engine system; for each fault, generating a unique fault code according to a predetermined coding rule according to the safety influence level category and the subsystem to which the fault belongs; in the coding rule, at least one part of code bits of the fault code is used for representing the safety influence level category, and another part of code bits is used for representing the subsystem; when the fault occurs for the first time, the generated fault code is stored in association with the first occurrence time of the fault; and the application is favorable for unifying the aero-engine fault coding specification.

Description

Technical Field

[0001] This invention relates to the field of control software data communication technology, and specifically to a fault coding method for control system communication. Background Technology

[0002] Currently, full-authority digital electronic controllers (FADECs) are widely used in aero engines, not only for engine control but also for monitoring the operational status of the entire system. When alarms or malfunctions occur during operation, the FADEC reports and records the abnormal information. However, as a highly complex and sophisticated system, the aero engine requires FADEC to monitor anomalies from multiple subsystems, including sensors, fuel lines, gas lines, actuators, engine bearings, blades, turbines, and the FADEC itself, resulting in an extremely large fault spectrum. Throughout the engine's entire lifecycle, from design and development to product delivery and customer support, there are extremely high requirements for efficient and accurate fault location. In reality, this is often limited by field maintenance personnel's insufficient understanding of the system, non-standard communication, and high similarity in fault names, hindering the analysis and troubleshooting by technical personnel. Summary of the Invention

[0003] Purpose of the invention: The purpose of this invention is to provide a fault coding method for control system communication, which solves the problems of high requirements for maintenance personnel's familiarity with the system, strong requirements for standardized description of fault information, high communication costs, and low efficiency when locating faults in aero-engine systems.

[0004] Technical Solution: The fault coding method for control system communication described in this invention is applied to the full authority digital electronic controller (FADEC) of an aero-engine, and includes the following steps: (1) Engine failures are classified into multiple predetermined safety impact levels according to their impact on flight safety; at the same time, the engine system is classified into multiple subsystems according to its physical or functional composition. (2) For each fault, a unique fault code is generated according to the safety impact level category and the subsystem to which it belongs, and in accordance with a predetermined coding rule; in the coding rule, at least a portion of the code bits of the fault code is used to characterize the safety impact level category, and another portion of the code bits is used to characterize the subsystem. (3) When the fault occurs for the first time, the generated fault code is stored in association with the time of the first occurrence of the fault.

[0005] Furthermore, the safety impact levels are categorized as follows: Category I faults: directly affect engine control and current flight safety, requiring emergency pilot intervention; Category II faults: affect engine control but the controller has the necessary handling logic, requiring no emergency pilot intervention but subsequent investigation; Category III faults: have no direct impact on engine control, require no emergency pilot intervention and can be handled as appropriate.

[0006] Furthermore, in step (1), the subsystem includes at least one or more of the following: bearing system, blade system, turbine system, actuation mechanism system, fuel system, lubricating oil system, air system, full authority digital electronic controller (FADEC) system, and sensor system.

[0007] Furthermore, the predetermined coding rule in step (2) is as follows: the fault code includes, in sequence, the first bit segment representing the safety impact level category, the second bit segment representing the subsystem, and the third bit segment representing the fault sequence number within the subsystem.

[0008] Furthermore, the first code segment uses a single-digit code, the second code segment uses a two-digit code, and the third code segment uses a three-digit code.

[0009] Furthermore, the method also includes a fault management step: in response to the operation instructions of maintenance personnel, performing a clearing operation on the stored fault codes and associated information.

[0010] The fault coding system for control system communication according to the present invention includes the following steps: Fault classification module: classifies engine faults into multiple predetermined safety impact levels according to their degree of impact on flight safety; at the same time, it divides the engine system into multiple subsystems according to its physical or functional composition. Encoding generation module: For each fault, a unique fault code is generated according to its security impact level category and its subsystem, and according to a predetermined encoding rule; in the encoding rule, at least a portion of the code bits of the fault code is used to represent the security impact level category, and another portion of the code bits is used to represent the subsystem; Fault storage module: When a fault occurs for the first time, the generated fault code is stored in association with the time of the first occurrence of the fault.

[0011] An electronic device according to the present invention includes a memory and a processor. The memory stores a computer program, and the processor executes the program to implement the steps of the method.

[0012] The present invention discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method.

[0013] Beneficial effects: Compared with the prior art, the present invention has the following significant advantages: The present invention makes it easier for maintenance personnel to find maintenance manuals and quickly find handling measures based on fault codes; it facilitates rapid fault location for designers; and it helps to unify the fault coding standards for aero engines, reducing the maintenance and support difficulty of different models of the same series of engines. Attached Figure Description

[0014] Figure 1 This is the process of the present invention. Detailed Implementation

[0015] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0016] like Figure 1 As shown, this embodiment of the invention provides a fault coding method for control system communication, applied to the full authority digital electronic controller (FADEC) of an aero-engine, comprising the following steps: Step 1: Classify engine faults: First, engine malfunctions are classified into three categories based on their safety impact: Category I, Category II, and Category III. Category I malfunctions directly affect engine control, have a direct impact on the stable operation of the current engine, affect flight safety, and require emergency handling by the pilot. Examples include FDAEC core circuit malfunctions, critical sensor malfunctions, critical actuator malfunctions, and abnormal malfunctions of engine bearings and blades. Once a malfunction occurs, short-term deployment or deployment is prohibited.

[0017] Category II faults affect normal engine control, but the FADEC has its own handling logic. They do not require emergency pilot intervention and will not affect the current flight, but require investigation after landing. This includes faults in critical sensors with protective design features. Prolonged deployment is prohibited after a fault occurs.

[0018] Category III indicates no impact on normal engine control, requiring no pilot intervention; the pilot can continue flight operations after landing, and further action can be taken as needed. This applies to single-channel sensor malfunctions with redundant design.

[0019] Then, the engine subsystems are divided as shown in Table 1: the faults in each subsystem are sorted by serial number.

[0020] Table 1 is a schematic diagram of numbering based on the engine subsystem. bearings 01 Lubricating oil circuit 06 paddle blades 02 airway 07 turbine 03 FADEC 08 Actuating mechanism 04 sensor 09 fuel road 05 Reserved … Step 2: Number engine faults according to the following rules, leaving sufficient space for future digits: fault level uses a one-digit code, subsystem uses a two-digit code, and fault sequence number uses a three-digit code. For example, turbine debris fault number 1 in the turbine category has no impact on flight but requires maintenance after the aircraft lands, and its corresponding number is 203001.

[0021] Step 3: Store the fault number and the time of occurrence: Only when the fault occurs for the first time will the fault number and the time of occurrence be stored in the allocated space.

[0022] Step 4: Each fault can be recorded and cleared: When maintenance personnel complete maintenance operations and resolve faults, they can set a clear command to clear the corresponding fault.

Claims

1. A fault coding method for control system communication, characterized in that, The Full Authority Digital Electronic Controller (FADEC) used in aero engines includes the following steps: (1) Engine failures are classified into multiple predetermined safety impact levels according to their impact on flight safety; at the same time, the engine system is classified into multiple subsystems according to its physical or functional composition. (2) For each fault, a unique fault code is generated according to the safety impact level category and the subsystem to which it belongs, and in accordance with a predetermined coding rule; in the coding rule, at least a portion of the code bits of the fault code is used to characterize the safety impact level category, and another portion of the code bits is used to characterize the subsystem. (3) When the fault occurs for the first time, the generated fault code is stored in association with the time of the first occurrence of the fault.

2. The fault coding method for control system communication according to claim 1, characterized in that, In step (1), the safety impact level categories include: Class I faults: directly affect engine control and current flight safety, requiring emergency handling by the pilot; Class II faults: affect engine control but the controller has handling logic, do not require emergency handling by the pilot but require subsequent investigation; Class III faults: have no direct impact on engine control, do not require emergency handling by the pilot and can be handled at an opportune time.

3. The fault coding method for control system communication according to claim 1, characterized in that, In step (1), the subsystem includes at least one or more of the following: bearing system, blade system, turbine system, actuation mechanism system, fuel system, lubricating oil system, air system, full authority digital electronic controller (FADEC) system, and sensor system.

4. The fault coding method for control system communication according to claim 1, characterized in that, In step (1), the predetermined coding rule in step (2) is: the fault code includes the first code segment representing the safety impact level category, the second code segment representing the subsystem, and the third code segment representing the fault sequence number within the subsystem.

5. The fault coding method for control system communication according to claim 1, characterized in that, In step (1), the first code segment is encoded with one digit, the second code segment is encoded with two digits, and the third code segment is encoded with three digits.

6. The fault coding method for control system communication according to claim 1, characterized in that, The method also includes a fault management step: in response to the operation instructions of maintenance personnel, a clearing operation is performed on the stored fault codes and associated information.

7. A fault coding system for control system communication, characterized in that, Includes the following steps: Fault classification module: classifies engine faults into multiple predetermined safety impact levels according to their degree of impact on flight safety; at the same time, it divides the engine system into multiple subsystems according to its physical or functional composition. Encoding generation module: For each fault, a unique fault code is generated according to its security impact level category and the subsystem to which it belongs, and in accordance with predetermined encoding rules; In the coding rule, at least a portion of the code bits of the fault code are used to characterize the safety impact level category, and another portion of the code bits are used to characterize the subsystem; Fault storage module: When a fault occurs for the first time, the generated fault code is stored in association with the time of the first occurrence of the fault.

8. An electronic device, characterized in that, It includes a memory and a processor, the memory storing a computer program, and the processor executing the program to implement the steps of the method according to claims 1-7.

9. A computer-readable storage medium, characterized in that, The device contains a computer program that, when executed by a processor, implements the steps of the method described in claims 1-7.

Images