An aircraft brake configuration identification method

Abstract

The embodiment of the application relates to the technical field of aircraft brake control, and discloses an aircraft brake configuration identification method, which comprises the following steps: obtaining a power-on initialization completion result; if the power-on initialization is completed and preset configuration identification conditions are met, configuration identification is performed on a target aircraft, if the configurations identified within a first preset time length are consistent, it is determined that the configuration identification is successful; if the preset configuration identification conditions are not met, or the configurations identified within the first preset time length are inconsistent, configuration identification waiting is performed, and when configuration identification waiting time exceeds a second preset time length, it is determined that the configuration identification fails, and a configuration identification failure alarm is uploaded. The application realizes safe and reliable aircraft brake configuration identification through logical judgment of a power-on initialization completion flag, a brake software bus data packet refreshing flag, a brake software bus data packet hardware monitoring flag and a time sequence, reduces a configuration identification false alarm rate, and significantly improves safety.

Description

Technical Field

[0001] The embodiments of this application relate to the field of aircraft brake control technology, and in particular to an aircraft brake configuration recognition method. Background Technology

[0002] During the development of aircraft, there is a phenomenon of serialization. For example, two aircraft may have similar capabilities but different configurations, such as two-seater and single-seater. Since the two aircraft may be controlled by the same brake control software, configuration recognition technology needs to be designed into the brake control software.

[0003] Conventional braking control methods cannot perform configuration recognition, requiring the development of different braking control software for different aircraft configurations. This is labor-intensive and the software maintenance is not convenient. Meanwhile, braking control methods with configuration recognition technology in the industry have low recognition accuracy and are prone to configuration recognition errors. Summary of the Invention

[0004] The purpose of this application is to provide an aircraft brake configuration recognition method, which aims to improve the accuracy and reliability of the unified brake software for different aircraft in recognizing aircraft configurations.

[0005] To address the aforementioned technical problems, embodiments of this application provide an aircraft brake configuration identification method, comprising the following steps: determining whether the power-on initialization of the target aircraft is complete using a power-on initialization completion flag; if the power-on initialization of the target aircraft is complete, acquiring a brake software bus data packet refresh flag and a brake software bus data packet hardware monitoring flag, and determining whether preset configuration identification conditions are met based on the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag; if the preset configuration identification conditions are met, performing configuration identification on the target aircraft; if the identified configurations are consistent within a first preset time period, determining that the configuration identification is successful, locking the configuration state of the target aircraft until the target aircraft is powered down; if the preset configuration identification conditions are not met, or if the identified configurations are inconsistent within the first preset time period, performing configuration identification waiting; if the configuration identification waiting time exceeds a second preset time period, determining that the configuration identification has failed, and uploading a configuration identification failure alarm.

[0006] An embodiment of this application also provides an aircraft brake configuration recognition system, including: a power-on initialization detection module, a configuration recognition condition judgment module, a configuration recognition success module, and a configuration recognition failure alarm module; the power-on initialization detection module is used to determine whether the power-on initialization of the target aircraft is complete using a power-on initialization completion flag; the configuration recognition condition judgment module is used to, if it determines that the power-on initialization of the target aircraft is complete, obtain a brake software bus data packet refresh flag and a brake software bus data packet hardware monitoring flag, and determine the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag based on the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag. The system determines whether the preset configuration recognition conditions are met. The configuration recognition success module is used to perform configuration recognition on the target aircraft if the preset configuration recognition conditions are met. If the configurations identified within the first preset time period are consistent, the configuration recognition is determined to be successful, and the configuration status of the target aircraft is locked until the target aircraft is powered off. The configuration recognition failure alarm module is used to wait for configuration recognition if the preset configuration recognition conditions are not met, or if the configurations identified within the first preset time period are inconsistent. If the configuration recognition waiting time exceeds the second preset time period, the configuration recognition is determined to be unsuccessful, and a configuration recognition failure alarm is uploaded.

[0007] Embodiments of this application also provide an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the above-described aircraft brake configuration recognition method.

[0008] Embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described aircraft brake configuration recognition method.

[0009] The embodiments of this application provide an aircraft brake configuration recognition method. Conventional brake control methods cannot perform configuration recognition, requiring the development of different brake control software for different aircraft, which is labor-intensive and inconvenient for software maintenance. At the same time, existing brake control methods with configuration recognition technology are prone to configuration recognition errors. By using power-on initialization completion flags, brake software bus data packet refresh flags, brake software bus data packet hardware monitoring flags, and timing logic judgments, aircraft brake configuration recognition is achieved safely and reliably, reducing the false alarm rate of configuration recognition and significantly improving safety.

[0010] In some optional embodiments, the power-on initialization completion flag is denoted as pbit_power, where pbit_power = 1 indicates power-on initialization is complete, and pbit_power = 0 indicates power-on initialization is not complete. The step of using the power-on initialization completion flag to determine whether the target aircraft's power-on initialization is complete includes:

[0011] If the power-on initialization completion flag is pbit_power=1, then the power-on initialization of the target aircraft is considered complete.

[0012] If the power-on initialization completion flag is pbit_power = 0, then it is determined that the target aircraft's power-on initialization has not been completed.

[0013] In some optional embodiments, the brake software bus data packet refresh flag is denoted as abs_refresh, abs_refresh=1 indicates that the brake software bus data packet has been refreshed, abs_refresh=0 indicates that the brake software bus data packet has not been refreshed, and the brake software bus data packet hardware monitoring flag is denoted as abs_effect, abs_effect=1 indicates that the brake software bus data packet hardware monitoring has been activated, and abs_effect=0 indicates that the brake software bus data packet hardware monitoring has not been activated.

[0014] The preset configuration identification conditions are as follows: the brake software bus data packet refresh flag is abs_refresh=1 and the brake software bus data packet hardware monitoring flag is abs_effect=1.

[0015] In some optional embodiments, the configuration identification of the target aircraft, if the identified configurations are all consistent within a first preset time period, determines that the configuration identification is successful, including:

[0016] The configuration of the target aircraft is identified, and the first configuration identified is recorded as the target configuration. The duration of the target configuration is recorded as the configuration identification duration. If the configuration identification duration is greater than or equal to the first preset duration, the configuration identification is considered successful. The first preset duration ranges from 0.5s to 1.5s.

[0017] In some optional embodiments, the step of waiting for configuration identification if the preset configuration identification conditions are not met, or if the configurations identified within a first preset time period are inconsistent, includes:

[0018] If the preset configuration recognition conditions are not met, or if the configurations identified within the first preset time period are inconsistent, a configuration recognition wait will be initiated, with the time taken from the completion of the power-on initialization of the target aircraft as the configuration recognition wait time.

[0019] In some optional embodiments, determining configuration recognition failure after the configuration recognition waiting time exceeds a second preset time includes:

[0020] If the configuration state of the target aircraft is still not locked after the configuration recognition waiting time reaches the second preset time, the configuration recognition is determined to have failed. The value of the second preset time ranges from 8s to 10s.

[0021] In some optional embodiments, the method further includes, after the upload configuration recognition failure alarm, the method further comprising:

[0022] Update the brake software bus data packet refresh flag and brake software bus data packet hardware monitoring flag. Based on the updated brake software bus data packet refresh flag and updated brake software bus data packet hardware monitoring flag, determine whether the preset configuration recognition conditions are met. Attached Figure Description

[0023] One or more embodiments are illustrated by way of example with reference to the accompanying drawings, and these illustrative descriptions do not constitute a limitation on the embodiments.

[0024] Figure 1 This is a flowchart of an aircraft brake configuration recognition method provided in one embodiment of this application;

[0025] Figure 2 This is a schematic diagram of another embodiment of an aircraft brake configuration recognition system provided in this application;

[0026] Figure 3 This is a schematic diagram of the structure of an electronic device provided in another embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been provided in the various embodiments of this application to help readers better understand this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments. The division of the various embodiments below is for the convenience of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0028] One embodiment of this application relates to an aircraft brake configuration recognition method applied to an electronic device, wherein the electronic device can be a terminal or a server. In this embodiment and the following embodiments, the electronic device is described using a server as an example. The implementation details of the aircraft brake configuration recognition method of this embodiment are described below. The following implementation details are provided for ease of understanding and are not necessary for implementing this solution.

[0029] The specific process of an aircraft brake configuration recognition method in this embodiment can be described as follows: Figure 1 As shown, it includes:

[0030] Step 101: Use the power-on initialization completion flag to determine whether the power-on initialization of the target aircraft is complete.

[0031] The completion status of power-on initialization is determined based on a power-on initialization completion flag. Specifically, in this embodiment, the power-on initialization completion flag is denoted as pbit_power. If pbit_power = 1, power-on initialization is considered complete; if pbit_power = 0, power-on initialization is considered incomplete, and no further processing is performed. In this embodiment, pbit_power = 1, indicating successful power-on initialization.

[0032] At this point, the power-on initialization check is complete.

[0033] Step 102: Obtain and determine whether the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag meet the preset configuration recognition conditions.

[0034] In this embodiment, the brake software bus data packet refresh flag is denoted as abs_refresh, and the brake software bus data packet hardware monitoring flag is denoted as abs_effect. The preset configuration identification conditions are that the brake software bus data packet refresh flag abs_refresh = 1 and the brake software bus data packet hardware monitoring flag abs_effect = 1.

[0035] Step 103: Perform configuration identification on the target aircraft.

[0036] Flight configuration identification is performed when the brake software bus data packet refresh flag abs_refresh = 1 and the brake software bus data packet hardware monitoring flag abs_effect = 1; flight configuration identification is not performed when the brake software bus data packet refresh flag abs_refresh = 0 or the brake software bus data packet hardware monitoring flag abs_effect = 0.

[0037] In this embodiment, the brake software bus data packet refresh flag abs_refresh = 0, the brake software bus data packet hardware monitoring flag abs_effect = 1, and no aircraft brake configuration brake identification is performed.

[0038] Step 104: Whether the configurations identified within the first preset time period are all consistent.

[0039] It should be noted that clutter data may affect flight configuration identification. Directly locking the identified flight configuration based on the identified configuration will result in errors. Therefore, when an aircraft configuration is identified, it is necessary to detect the duration of the identified configuration, i.e. the time during which no data fluctuations occur and other configurations appear. When the configuration identification continues for a period of time without configuration fluctuations, the aircraft configuration is locked to reduce identification errors.

[0040] In one example, during aircraft configuration recognition, the first identified configuration is designated as the target configuration. The duration of the target configuration is recorded and denoted as the configuration recognition duration t. A first preset duration is denoted as D0, with D0 ranging from 0.5 to 1.5 seconds. When the configuration recognition duration t reaches the first preset duration D0, the aircraft configuration recognition is successful, and the configuration state is locked, meaning the configuration state is no longer updated until the aircraft is powered down. When the configuration recognition duration t does not reach the first preset duration D0 (i.e., t is less than D0), the configuration state is not locked. It should be noted that in this embodiment, D0 is set to 1; implementers can adjust this setting according to actual circumstances.

[0041] Step 105: Configuration recognition successful; the configuration status of the target aircraft is locked.

[0042] If the configurations identified within the first preset time period are all consistent, that is, when the configuration identification time reaches the first preset time period, the aircraft configuration identification is successful and the configuration status is locked.

[0043] It should be noted that when both the brake software bus data packet refresh flag abs_refresh and the brake software bus data packet hardware monitoring flag abs_effect are valid, the bus data has been established. This indicates that both the software and hardware data are valid. The problem of false alarms in configuration recognition is solved by the software and hardware dissimilarity redundancy. When the aircraft brake configuration state is locked, no further processing steps are performed.

[0044] Step 106, configuration recognition wait, obtain the configuration recognition wait time.

[0045] When the configuration state is not locked, a configuration recognition waiting time is started. The specific steps of the configuration recognition waiting time are as follows: when the configuration state is not locked, that is, when the brake software bus data packet refresh flag abs_refresh = 0 or the brake software bus data packet hardware monitoring flag abs_effect = 0 or the configuration recognition duration t is less than the first preset duration D0, the timer starts after the power-on initialization is completed and is recorded as the configuration recognition waiting time t1. During the configuration recognition waiting time, the brake software bus data packet refresh flag, the brake software bus data packet hardware monitoring flag and the configuration recognition duration t are still monitored.

[0046] Step 107: Does the configuration recognition waiting time exceed the second preset time?

[0047] The second preset time is denoted as D1, with a value ranging from 8 to 10 seconds. If the configuration recognition waiting time t1 reaches the second preset time D1 and the configuration state is still not locked, the aircraft configuration recognition fails, and a configuration failure alarm status is uploaded. During the recording of the configuration recognition waiting time, the aircraft performs power-on checks and operations according to the specified status. It should be noted that in this embodiment, D1 is set to 10, but the implementer can adjust it according to the actual situation.

[0048] It should be noted that when recording the configuration recognition waiting time, the aircraft normally assigns values ​​to the configuration difference parts according to the specified state to avoid false alarms during the configuration recognition process. In this embodiment, the configuration recognition waiting time is set and a second preset time, i.e., the waiting time threshold, is set to integrate the false alarms caused by the asynchronous operation of the fly-by-wire anti-skid braking system software hardware environment and the power-on initialization of the host computer.

[0049] Step 108: Configuration recognition failed. Upload configuration recognition failure alarm and continuously refresh the brake software bus data packet refresh flag and brake software bus data packet hardware monitoring flag.

[0050] In one example, when aircraft configuration recognition fails, configuration status is not locked. Instead, the aircraft brake configuration failure alarm status is uploaded. The brake software bus data packet refresh flag, brake software bus data packet hardware monitoring flag, and configuration recognition duration are continuously monitored. If the brake software bus data packet refresh flag abs_refresh = 1 and the brake software bus data packet hardware monitoring flag abs_effect = 1, aircraft configuration recognition is performed. If the configuration recognition duration t reaches the first preset duration D0, the configuration status is locked and the configuration failure alarm status is released.

[0051] In this embodiment, the configuration recognition waiting time t1 is greater than the second preset duration D1, i.e., t1 is greater than 10 seconds, and the configuration failure alarm status is uploaded. During the recording of the configuration recognition waiting time, the aircraft performs power-on testing according to the specified two-seat configuration, and the rear cabin brake command is set to the brake release state, without generating any false alarms. After 20 seconds following the upload of the configuration failure alarm status, the brake software bus data packet refresh flag abs_refresh = 1 and the brake software bus data packet hardware monitoring flag abs_effect = 1, and aircraft configuration recognition is performed. When the configuration recognition duration t reaches the first preset duration D0, i.e., t reaches 1 second, the aircraft configuration recognition is successful, the configuration is locked, and the configuration failure alarm status is cleared.

[0052] This completes a method for identifying aircraft brake configurations.

[0053] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this application. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this application.

[0054] Another embodiment of this application relates to an aircraft brake configuration recognition system. The implementation details of this embodiment's aircraft brake configuration recognition system are described below. The following implementation details are provided for ease of understanding and are not essential for implementing this solution. A schematic diagram of this embodiment's aircraft brake configuration recognition system can be seen as follows: Figure 2 As shown, it includes: a power-on initialization detection module, a configuration recognition condition judgment module, a configuration recognition module, a configuration recognition consistency judgment module, a configuration recognition success module, a configuration recognition waiting module, a configuration recognition waiting time judgment module, and a configuration recognition failure alarm module.

[0055] The power-on initialization detection module 201 is used to determine whether the power-on initialization of the target aircraft has been completed by using the power-on initialization completion flag.

[0056] The configuration recognition condition judgment module 202 is used to acquire and judge whether the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag meet the preset configuration recognition conditions.

[0057] The configuration recognition module 203 is used to perform configuration recognition on the target aircraft.

[0058] The configuration recognition consistency judgment module 204 is used to determine whether the configurations identified within the first preset time period are all consistent.

[0059] The configuration recognition success module 205 is used to lock the configuration status of the target aircraft after successful configuration recognition.

[0060] The configuration recognition waiting module 206 is used for configuration recognition waiting and to obtain the configuration recognition waiting time.

[0061] The configuration recognition waiting time judgment module 207 is used to determine whether the configuration recognition waiting time exceeds the second preset time.

[0062] The configuration recognition failure alarm module 208 is used to upload configuration recognition failure alarms when configuration recognition fails, and to continuously refresh the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag.

[0063] It is not difficult to see that this embodiment is a system embodiment corresponding to the above method embodiments, and this embodiment can be implemented in conjunction with the above method embodiments. The relevant technical details and technical effects mentioned in the above embodiments are still valid in this embodiment, and will not be repeated here to reduce repetition. Accordingly, the relevant technical details mentioned in this embodiment can also be applied to the above embodiments.

[0064] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this application, this embodiment does not introduce units that are not closely related to solving the technical problems proposed in this application; however, this does not mean that other units are absent in this embodiment.

[0065] Another embodiment of this application relates to an electronic device, such as... Figure 3 As shown, it includes: at least one processor 301; and a memory 302 communicatively connected to the at least one processor 301; wherein the memory 302 stores instructions executable by the at least one processor 301, the instructions being executed by the at least one processor 301 to enable the at least one processor 301 to execute an aircraft brake configuration recognition method in the above embodiments.

[0066] The memory and processor are connected via a bus, which can include any number of interconnecting buses and bridges, connecting various circuits of one or more processors and memories. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor is transmitted over the wireless medium via an antenna, which further receives data and transmits it to the processor.

[0067] The processor manages the bus and general processing, and also provides various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory is used to store data used by the processor during operation.

[0068] Another embodiment of this application relates to a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the method embodiments described above.

[0069] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0070] Those skilled in the art will understand that the above embodiments are specific embodiments for implementing this application, and in practical applications, various changes can be made to them in form and detail without departing from the spirit and scope of this application.

Claims

1. A method for identifying aircraft brake configurations, characterized in that, include: The power-on initialization completion flag is used to determine whether the target aircraft's power-on initialization is complete. If the target aircraft's power-on initialization is determined to be complete, the brake software bus data packet refresh flag and brake software bus data packet hardware monitoring flag are obtained. Based on the brake software bus data packet refresh flag and brake software bus data packet hardware monitoring flag, it is determined whether the preset configuration recognition conditions are met. If the preset configuration recognition conditions are met, the target aircraft will be identified in configuration. If the configurations identified within the first preset time period are consistent, the configuration recognition will be confirmed as successful, and the configuration status of the target aircraft will be locked until the target aircraft is powered down. If the preset configuration recognition conditions are not met, or if the configurations identified within the first preset time period are inconsistent, configuration recognition will wait. If the configuration recognition waiting time exceeds the second preset time period, configuration recognition will be determined to have failed, and a configuration recognition failure alarm will be uploaded.

2. The aircraft brake configuration identification method according to claim 1, characterized in that, The power-on initialization completion flag is denoted as pbit_power, where pbit_power = 1 indicates power-on initialization is complete, and pbit_power = 0 indicates power-on initialization is incomplete. The method of using the power-on initialization completion flag to determine whether the target aircraft's power-on initialization is complete includes: If the power-on initialization completion flag is pbit_power=1, then the power-on initialization of the target aircraft is considered complete. If the power-on initialization completion flag is pbit_power = 0, then it is determined that the target aircraft's power-on initialization has not been completed.

3. The aircraft brake configuration identification method according to claim 1, characterized in that, The brake software bus data packet refresh flag is denoted as abs_refresh. abs_refresh=1 indicates that the brake software bus data packet has been refreshed, and abs_refresh=0 indicates that the brake software bus data packet has not been refreshed. The brake software bus data packet hardware monitoring flag is denoted as abs_effect. abs_effect=1 indicates that the brake software bus data packet hardware monitoring is effective, and abs_effect=0 indicates that the brake software bus data packet hardware monitoring is not effective. The preset configuration identification conditions are as follows: the brake software bus data packet refresh flag is abs_refresh=1 and the brake software bus data packet hardware monitoring flag is abs_effect=1.

4. The aircraft brake configuration identification method according to claim 1, characterized in that, The configuration identification of the target aircraft, if the identified configurations are all consistent within a first preset time period, is determined to be successful, including: The configuration of the target aircraft is identified, and the first configuration identified is recorded as the target configuration. The duration of the target configuration is recorded as the configuration identification duration. If the configuration identification duration is greater than or equal to the first preset duration, the configuration identification is considered successful. The first preset duration ranges from 0.5s to 1.5s.

5. The aircraft brake configuration identification method according to claim 1, characterized in that, If the preset configuration recognition conditions are not met, or if the configurations identified within the first preset time period are inconsistent, then configuration recognition waiting is performed, including: If the preset configuration recognition conditions are not met, or if the configurations identified within the first preset time period are inconsistent, a configuration recognition wait will be initiated, with the time taken from the completion of the power-on initialization of the target aircraft as the configuration recognition wait time.

6. The aircraft brake configuration identification method according to claim 1, characterized in that, The step of determining configuration recognition failure when the waiting time exceeds a second preset duration includes: If the configuration state of the target aircraft is still not locked after the configuration recognition waiting time reaches the second preset time, the configuration recognition is determined to have failed. The value of the second preset time ranges from 8s to 10s.

7. The aircraft brake configuration identification method according to claim 1, characterized in that, Following the alarm indicating upload configuration recognition failure, the method further includes: Update the brake software bus data packet refresh flag and brake software bus data packet hardware monitoring flag. Based on the updated brake software bus data packet refresh flag and updated brake software bus data packet hardware monitoring flag, determine whether the preset configuration recognition conditions are met.

8. An aircraft brake configuration recognition system, characterized in that, The system includes a power-on initialization detection module, a configuration recognition condition judgment module, a configuration recognition success module, and a configuration recognition failure alarm module; The power-on initialization detection module is used to determine whether the power-on initialization of the target aircraft has been completed by using the power-on initialization completion flag; The configuration recognition condition judgment module is used to obtain the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag if it is determined that the power-on initialization of the target aircraft is completed, and to determine whether the preset configuration recognition conditions are met based on the brake software bus data packet refresh flag and the brake software bus data packet hardware monitoring flag. The configuration recognition success module is used to perform configuration recognition on the target aircraft if the preset configuration recognition conditions are met. If the configurations identified within the first preset time period are all consistent, the configuration recognition is determined to be successful, and the configuration status of the target aircraft is locked until the target aircraft is powered off. The configuration recognition failure alarm module is used to wait for configuration recognition if the preset configuration recognition conditions are not met or if the configurations identified within the first preset time period are inconsistent. When the configuration recognition waiting time exceeds the second preset time period, the configuration recognition is determined to have failed and a configuration recognition failure alarm is uploaded.

9. An electronic device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform an aircraft brake configuration recognition method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements an aircraft brake configuration recognition method as described in any one of claims 1 to 7.

Images