Display control software architecture construction method and system, electronic equipment and medium

Abstract

The invention belongs to the technical field of airborne display and control software design, and particularly relates to a display and control software architecture construction method and system, electronic equipment and a medium. On the basis that display and control software is divided into a data receiving and transmitting task and a drawing display task, the data receiving and transmitting task and the drawing display task are set as a periodic task and a non-periodic task respectively; the priority of the data receiving and transmitting tasks is higher than that of the drawing display tasks, the data receiving and transmitting tasks are set to switch the corresponding drawing display tasks into a ready state when a display picture is updated, the drawing display tasks are awakened to participate in scheduling, the display picture is drawn, and the drawing display tasks are suspended to enter a blocking state after drawing is finished; tasks of the display control software are divided and designed more reasonably based on the idea of data driving, a software architecture is constructed, and the real-time performance of the display control software can be improved.

Description

Technical Field

[0001] The present application belongs to the technical field of airborne display and control software design, and specifically relates to a display and control software architecture construction method, system, electronic equipment and medium. Background Art

[0002] Airborne display and control software is an important software of the aircraft avionics system, which provides comprehensive information display and human-computer interaction control functions to pilots through the display and control system hardware and software platform. As a direct interface for aircraft display control, airborne display and control software is required to have real-time characteristics. Therefore, airborne display and control software usually runs in embedded real-time operating systems such as VxWorks and Tianmai.

[0003] Embedded real-time operating systems provide users with efficient real-time multi-task scheduling functions to ensure high operating efficiency of application software. The task scheduling strategy of embedded real-time operating systems uses preemptive scheduling to give priority to high-priority tasks, and then uses a time slice round-robin scheduling algorithm to concurrently execute multiple tasks of the same priority. This scheduling method can give priority to urgent tasks with higher priorities, give priority to ensuring the real-time performance of urgent and important tasks, and tasks of the same priority can be executed concurrently.

[0004] A task in a real-time operating system can have multiple states, among which the most basic states are the following four:

[0005] Ready state: The task has obtained resources other than the CPU and can be executed once the CPU is obtained;

[0006] Blocked state: The task is suspended or is not eligible to compete for the CPU because the required resource conditions are not met;

[0007] Running state: The task has CPU control and is being executed;

[0008] Sleep state: The task has been created or stopped and does not have the right to compete for the CPU.

[0009] During the operation of an embedded real-time operating system, the task state may change due to changes in resources or program instructions. A task in the ready state can be converted to the blocked state through the TaskSuspend() instruction, and a task in the blocked state can be converted to the ready state through the TaskResume() instruction.

[0010] The embedded real-time operating system divides the task priority into 256 levels (0 to 255), with priority 0 being the highest priority and priority 255 being the lowest priority.

[0011] At present, in order to ensure the real-time performance of airborne display and control software, tasks are divided and designed during the design of display and control software architecture. There are two commonly used task division and construction methods. One is to concentrate the data sending and receiving function and the drawing display function in a non-periodic task to simplify the complexity of software parallel design. Since the execution time of the drawing display function will increase with the complexity of the display content, the real-time performance of the control response in the data sending and receiving function cannot be guaranteed; the second is to design the data sending and receiving function and the drawing display function as two different periodic tasks to ensure the real-time performance of the control response, but this will produce a display time delay of a maximum drawing display task cycle, and the real-time performance of the drawing display cannot be guaranteed.

[0012] This application is proposed in view of the above-mentioned technical defects. Summary of the invention

[0013] The purpose of this application is to provide a display and control software architecture construction method, system, electronic device and medium to overcome or alleviate at least one of the known technical defects.

[0014] The technical solution of this application is:

[0015] On the one hand, a method for constructing a display control software architecture is provided, comprising:

[0016] Task type division step: divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks;

[0017] Task periodicity setting steps: set the data sending and receiving task as a periodic task, and set the drawing display task as a non-periodic task;

[0018] Task priority setting steps: set the priority of data sending and receiving tasks and drawing display tasks, and set the priority of data sending and receiving tasks to be higher than the priority of drawing display tasks;

[0019] Task status switching setting steps: When the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

[0020] According to at least one embodiment of the present application, the above-mentioned display control software architecture construction method further includes:

[0021] Task CPU core binding steps: Bind CPU cores to data receiving and sending tasks and drawing and display tasks.

[0022] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction method, in the task type division step, the task types of the display control software are divided according to the display control system configuration, wherein the number of drawing display tasks is determined according to the number of displays driven by the display control module.

[0023] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction method, in the task periodicity setting step, the period of the data sending and receiving task is set to 25 milliseconds.

[0024] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction method, in the task priority setting step, the priority of the data sending and receiving task is set to 100, and the priority of the drawing display task is set to 101.

[0025] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction method, in the task state switching setting step, the judgment logic for whether the display screen is updated is set to: when the display main screen is displayed and the driving data corresponding to the main screen in the data sending and receiving task is updated, it is judged that the display screen is updated, and the specific setting is:

[0026] If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display screen is updated.

[0027] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction method, in the task CPU core binding step, independent CPU cores are respectively bound to the data receiving and sending tasks and the drawing display tasks.

[0028] On the other hand, a display control software architecture construction system is provided, including:

[0029] Task type division module: used to divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks;

[0030] Task periodicity setting module: used to set the data sending and receiving task as a periodic task, and set the drawing display task as a non-periodic task;

[0031] Task priority setting module: used to set the priority of data sending and receiving tasks and drawing display tasks, and the priority of data sending and receiving tasks is higher than that of drawing display tasks;

[0032] Task state switching setting module: used to set that when the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

[0033] According to at least one embodiment of the present application, the above-mentioned display control software architecture construction system further includes:

[0034] Task CPU core binding module: used to bind CPU cores to data sending and receiving tasks and drawing display tasks.

[0035] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction system, in the task type division module, the task types of the display control software are divided according to the display control system configuration, wherein the number of drawing display tasks is determined according to the number of displays driven by the display control module.

[0036] According to at least one embodiment of the present application, in the above-mentioned display and control software architecture construction system, in the task periodicity setting module, the period of the data sending and receiving task is set to 25 milliseconds.

[0037] According to at least one embodiment of the present application, in the above-mentioned display and control software architecture construction system, in the task priority setting module, the priority of the data sending and receiving task is set to 100, and the priority of the drawing display task is set to 101.

[0038] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction system, in the task state switching setting module, the judgment logic for whether the display screen is updated is set to: when the display main screen is displayed and the driving data corresponding to the main screen in the data receiving and sending task is updated, it is judged that the display screen is updated, and the specific setting is:

[0039] If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display screen is updated.

[0040] According to at least one embodiment of the present application, in the above-mentioned display control software architecture construction system, in the task CPU core binding module, independent CPU cores are respectively bound to the data receiving and sending tasks and the drawing display tasks.

[0041] Another aspect provides an electronic device, characterized in that it includes:

[0042] processor;

[0043] A memory stores a computer program, which is configured to implement any of the above-mentioned display and control software architecture construction methods when executed by the processor.

[0044] On the other hand, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, it can implement any of the display and control software architecture construction methods mentioned above.

[0045] This application has at least the following beneficial technical effects:

[0046] Provided are a method, system, electronic device and medium for constructing a display control software architecture. The design divides the display control software into data transceiving tasks and drawing display tasks, sets the data transceiving tasks and drawing display tasks as periodic tasks and non-periodic tasks respectively, and the priority of the data transceiving tasks is higher than that of the drawing display tasks. When the display screen is updated, the data transceiving tasks switch the corresponding drawing display tasks to a ready state, wake up the drawing display tasks to participate in scheduling, and draw the display screen. After the drawing is completed, the drawing display tasks suspend themselves and enter a blocked state. Based on the idea of ​​data-driven, the display control software tasks are divided and designed more reasonably, and the software architecture is constructed, which can improve the real-time performance of the display control software. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 It is a schematic diagram of a method for constructing a display and control software architecture provided in an embodiment of the present application;

[0048] Figure 2 It is a schematic diagram of the display screen update judgment logic provided by the embodiment of the present application;

[0049] Figure 3 It is a schematic diagram of the display and control software architecture construction system provided in an embodiment of the present application.

[0050] In order to better illustrate the present embodiment, some parts of the drawings may be omitted, enlarged or reduced, and do not represent the size of the actual product. In addition, the drawings are only used for illustrative purposes and should not be construed as limitations on the present application. DETAILED DESCRIPTION

[0051] In order to make the technical solution and advantages of the present application clearer, the technical solution of the present application will be described in further detail in detail and in detail with reference to the accompanying drawings. It can be understood that the specific embodiments described here are only partial embodiments of the present application, which are only used to explain the present application, not to limit the present application. It should be noted that, for the convenience of description, only the parts related to the present application are shown in the accompanying drawings, and other related parts can refer to the general design.

[0052] In addition, unless otherwise defined, the technical terms or scientific terms used in the description of this application shall have the usual meanings understood by those of ordinary skill in the art to which this application belongs. The words used in the description of this application to indicate orientation are only used to indicate relative directions or positional relationships. When the absolute position of the described object changes, its relative positional relationship may also change accordingly. The word "include" used in the description of this application indicates that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, but does not exclude other elements or objects.

[0053] In addition, it should be noted that, unless otherwise clearly specified and limited, the words "installation", "connection" and similar terms used in the description of this application should be understood in a broad sense. For example, the connection can be a fixed connection or a detachable 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. Technical personnel in the field can understand its specific meaning in this application according to the specific circumstances.

[0054] On the one hand, a method for constructing a display control software architecture is provided, such as Figure 1 As shown, the tasks of the display and control software are divided and designed based on the data-driven idea, ensuring the real-time control response while ensuring the real-time drawing display.

[0055] Task type division steps: divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks.

[0056] Specifically, the task types of the display and control software can be divided according to the configuration of the display and control system. Among them, the number of drawing display tasks is determined according to the number of displays driven by the display and control module.

[0057] Task periodicity setting steps: Set the data sending and receiving task as a periodic task, and set the drawing display task as a non-periodic task.

[0058] Specifically, the period of the data sending and receiving task can be set to 25 milliseconds.

[0059] Task priority setting steps: Set the priority of data sending and receiving tasks and drawing display tasks, and set the priority of data sending and receiving tasks higher than the priority of drawing display tasks.

[0060] Specifically, the priority of the data sending and receiving task can be set to 100, and the priority of the drawing display task can be set to 101.

[0061] Task status switching setting steps: When the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

[0062] The judgment logic for whether the display screen is updated is set as follows: when the main screen of the display is displayed and the drive data corresponding to the main screen in the data receiving and sending task is updated, it is judged that the display screen is updated. The specific setting can be:

[0063] If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display screen is updated, otherwise, it is determined that there is no update, such as Figure 2 shown.

[0064] Task CPU core binding steps: Bind CPU cores to data receiving and sending tasks and drawing and display tasks.

[0065] Specifically, independent CPU cores may be bound to data receiving and sending tasks and multiple drawing display tasks to improve real-time performance.

[0066] The display control software architecture construction method disclosed in the above embodiment, on the basis of dividing the display control software into data sending and receiving tasks and drawing display tasks, sets the data sending and receiving tasks and the drawing display tasks as periodic tasks and non-periodic tasks respectively, and the priority of the data sending and receiving tasks is higher than that of the drawing display tasks, and it is arranged that when the display screen is updated, the data sending and receiving tasks switches the corresponding drawing display tasks to the ready state, wakes up the drawing display tasks to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state. Based on the data-driven idea, the tasks of the display control software are divided and designed more reasonably, and the software architecture is constructed, which can improve the real-time performance of the display control software.

[0067] In a specific example, the configuration of the airborne display and control system is that a single display and control module needs to drive two displays with a resolution of 1600*1200. The main screens that need to be displayed in the display include flight instructions (PFD), navigation (ND), system diagram (SYS), engine (EICAS), flight management (FMS), checklist (CHECK) and central maintenance (CMS) screens. The display and control software architecture construction method disclosed in the above embodiment is used to construct the display and control software architecture as follows:

[0068] S1. According to the configuration of the airborne display and control system, the task types of the airborne display and control software are divided, and the airborne display and control software tasks are divided into a data receiving and sending task DataRecvTask and two drawing display tasks RenderTask1 and RenderTask2.

[0069] S2. Set the data receiving and sending task DataRecvTask as a periodic task with a task period of 25 milliseconds, and set the drawing display tasks RenderTask1 and RenderTask2 as non-periodic tasks.

[0070] S3. Set the priority of the data receiving and sending task DataRecvTask to 100, and the priority of the drawing display tasks RenderTask1 and RenderTask2 to 101.

[0071] S4, setting 2: when the display screen is displayed and the corresponding driver data in the data receiving and sending task DataRecvTask is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

[0072] By traversing all main screens, if at least one main screen is being displayed and the screen driver data is updated, it means that the display screen is updated, such as Figure 2 shown.

[0073] If it is determined that the screen of display 1 is updated, set the data receiving and sending task DataRecvTask to call taskResume(RenderTask1) to switch the drawing display task RenderTask1 to the ready state, wake up the drawing display task RenderTask1 to participate in the scheduling, and draw the screen of display 1. After the drawing is completed, the drawing display task RenderTask1 calls taskSuspend(RenderTask1) to suspend itself and enter the blocked state;

[0074] If it is determined that the screen of display 2 has been updated, set the data receiving and sending task DataRecvTask to call taskResume(RenderTask2) to switch the drawing display task RenderTask2 to the ready state, wake up the drawing display task RenderTask2 to participate in the scheduling, and draw the screen of display 2. After the drawing is completed, the drawing display task RenderTask2 calls taskSuspend(RenderTask2) to suspend itself and enter the blocked state.

[0075] S5. Independent CPU cores may be bound to the data receiving and sending task DataRecvTask and the drawing display tasks RenderTask1 and RenderTask2 respectively.

[0076] The display control software architecture construction method disclosed in the above embodiment is applied. On the basis of dividing the airborne display control software into data transceiving tasks and drawing display tasks, the data transceiving tasks and the drawing display tasks are respectively set as periodic tasks and non-periodic tasks, and the priority of the data transceiving tasks is higher than that of the drawing display tasks. It is also arranged that when the display screen is updated, the data transceiving tasks switches the corresponding drawing display tasks to a ready state, wakes up the drawing display tasks to participate in scheduling, and draws the display screen. After the drawing is completed, the drawing display tasks suspend themselves and enter a blocked state. Based on the data-driven idea, the tasks of the airborne display control software are divided and designed more reasonably, and the software architecture is constructed, which can improve the real-time performance of the airborne display control software and ensure that the control response of the airborne display control software and the real-time performance of its drawing display can well meet the system requirements.

[0077] On the other hand, a display control software architecture construction system is provided, such as Figure 3 As shown, it includes a task type classification module, a task periodicity setting module, a task priority setting module, a task state switching setting module, and a task CPU core binding module.

[0078] The task type division module is used to divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks.

[0079] Specifically, the task types of the display and control software can be divided according to the configuration of the display and control system. Among them, the number of drawing display tasks is determined according to the number of displays driven by the display and control module.

[0080] The task periodicity setting module is used to set the data receiving and sending task as a periodic task, and to set the drawing display task as a non-periodic task.

[0081] Specifically, the period of the data sending and receiving task can be set to 25 milliseconds.

[0082] The task priority setting module is used to set the priority of the data sending and receiving task and the drawing display task, and the priority of the data sending and receiving task is set higher than the priority of the drawing display task.

[0083] Specifically, the priority of the data sending and receiving task can be set to 100, and the priority of the drawing display task can be set to 101.

[0084] The task state switching setting module is used to set that when the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

[0085] The judgment logic for whether the display screen is updated is set as follows: when the main screen of the display is displayed and the drive data corresponding to the main screen in the data receiving and sending task is updated, it is judged that the display screen is updated. The specific setting can be:

[0086] If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display screen is updated, otherwise, it is determined that there is no update, such as Figure 2 shown.

[0087] The task CPU core binding module is used to bind the CPU core to the data receiving and sending tasks and the drawing and display tasks.

[0088] Specifically, independent CPU cores may be bound to data receiving and sending tasks and multiple drawing display tasks to improve real-time performance.

[0089] Regarding the display and control software architecture construction system disclosed in the above-mentioned embodiment, since it corresponds to the display and control software architecture construction method disclosed in the above-mentioned embodiment, the description is relatively simple. For specific related matters, please refer to the relevant instructions in the part of the display and control software architecture construction method. Its technical effects can also refer to the technical effects of the relevant parts of the display and control software architecture construction method, which will not be repeated here.

[0090] In addition, technicians in the field should also be able to realize that the various modules and units of the display and control software architecture construction system disclosed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, this application generally describes them according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Technicians in the field can choose to adopt different methods to implement the described functions for each specific application and its actual constraints, but such implementation should not be considered to be beyond the scope of this application.

[0091] Another aspect provides an electronic device, comprising:

[0092] processor;

[0093] A memory stores a computer program, which is configured to implement any of the above-mentioned display and control software architecture construction methods when executed by the processor.

[0094] In some optional embodiments, the processor can be a central processing unit CPU or other form of processing unit with data processing capability and / or instruction execution capability, can be a general-purpose processor or a special-purpose processor, and can control other components in the compensation electronic device to perform the desired functions.

[0095] In some optional embodiments, the memory may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory, the volatile memory may be a random access memory RAM and / or a cache memory cache, and the non-volatile memory may be a read-only memory ROM, a hard disk, a flash memory, etc. The memory may store a computer program, and the processor runs the computer program to implement the functions in the embodiments of the present application and / or other desired functions. In addition, various application programs and various data may also be stored.

[0096] In some optional embodiments, the processor and the memory may be connected via a bus system, which may be a serial or parallel communication bus or the like.

[0097] It should be noted that, for the sake of clarity and brevity, not all components of the electronic device are shown in the above embodiments. To implement the necessary functions of the electronic device, technicians in the field can provide and set other components not shown according to specific needs.

[0098] For the electronic device disclosed in the above embodiments, since its processor can implement any of the above-mentioned display and control software architecture construction methods when executing the computer program stored in its memory, its technical effects can be correspondingly referred to the technical effects of the above-mentioned display and control software architecture construction methods, and will not be repeated here.

[0099] On the other hand, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, it can implement any of the above-mentioned display and control software architecture construction methods.

[0100] In some optional embodiments, the computer-readable storage medium may include a memory card of a smartphone, a storage component of a tablet computer, a hard disk of a personal computer, a random access memory RAM, a read-only memory ROM, an erasable programmable read-only memory EPROM, a portable compact disk read-only memory CD-ROM, flash memory, or any combination of the above storage media, or other applicable storage media.

[0101] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. Those skilled in the art should understand that the scope of protection of the present application is obviously not limited to these specific embodiments. Without departing from the principles of the present application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the scope of protection of the present application.

Claims

1. A method for constructing a display and control software architecture, characterized in that: include: Task type division step: divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks; Task periodicity setting steps: set the data sending and receiving task as a periodic task, and set the drawing display task as a non-periodic task; Task priority setting steps: set the priority of data sending and receiving tasks and drawing display tasks, and set the priority of data sending and receiving tasks to be higher than the priority of drawing display tasks; Task status switching setting steps: When the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

2. The method for constructing a display and control software architecture according to claim 1, characterized in that: Also includes: Task CPU core binding steps: Bind CPU cores to data receiving and sending tasks and drawing and display tasks.

3. The method for constructing a display and control software architecture according to claim 2, characterized in that: In the task type division step, the task types of the display control software are divided according to the display control system configuration, wherein the number of drawing display tasks is determined according to the number of displays driven by the display control module.

4. The method for constructing a display and control software architecture according to claim 3, characterized in that: In the task periodicity setting step, the period of the data sending and receiving task is set to 25 milliseconds.

5. The method for constructing a display and control software architecture according to claim 4, characterized in that: In the task priority setting step, set the priority of the data sending and receiving task to 100 and the priority of the drawing display task to 101.

6. The method for constructing a display and control software architecture according to claim 5, characterized in that: In the task status switching setting step, the judgment logic for whether the display screen is updated is set to: when the main screen of the display is displayed and the drive data corresponding to the main screen in the data receiving and sending task is updated, it is judged that the display screen is updated. The specific settings are: If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display screen is updated.

7. The method for constructing a display and control software architecture according to claim 6, characterized in that: In the task CPU core binding step, independent CPU cores are bound to the data receiving and sending tasks and the drawing and display tasks respectively.

8. A display control software architecture construction system, characterized in that: include: Task type division module: used to divide the task types of the display and control software into data sending and receiving tasks and drawing display tasks; Task periodicity setting module: used to set the data sending and receiving task as a periodic task, and set the drawing display task as a non-periodic task; Task priority setting module: used to set the priority of data sending and receiving tasks and drawing display tasks, and the priority of data sending and receiving tasks is higher than that of drawing display tasks; Task state switching setting module: used to set that when the display screen is updated, the data receiving and sending task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters the blocked state.

9. The display and control software architecture construction system according to claim 8, characterized in that: Also includes: Task CPU core binding module: used to bind CPU cores to data sending and receiving tasks and drawing display tasks.

10. The display and control software architecture construction system according to claim 9, characterized in that: In the task type division module, the task types of the display control software are divided according to the display control system configuration, wherein the number of drawing display tasks is determined according to the number of displays driven by the display control module.

11. The display and control software architecture construction system according to claim 10, characterized in that: In the task periodicity setting module, the period of the data sending and receiving task is set to 25 milliseconds.

12. The display and control software architecture construction system according to claim 11, characterized in that: In the task priority setting module, set the priority of the data sending and receiving task to 100 and the priority of the drawing display task to 101.

13. The display and control software architecture construction system according to claim 12, characterized in that: In the task status switching setting module, the judgment logic for whether the display screen is updated is set to: when the main screen of the display is displayed and the driving data corresponding to the main screen in the data receiving and sending task is updated, it is judged that the display screen is updated. The specific settings are: If the PFD screen is displayed and the PFD drive data is updated, or the ND screen is displayed and the ND drive data is updated, or the SYS screen is displayed and the SYS drive data is updated, or the EICAS screen is displayed and the EICAS drive data is updated, or the FMS screen is displayed and the FMS drive data is updated, or the CHECK screen is displayed and the CHECK drive data is updated, or the CMS screen is displayed and the CMS drive data is updated, it is determined that the display main screen is updated.

14. The display and control software architecture construction system according to claim 13, characterized in that: In the task CPU core binding module, independent CPU cores are bound to the data receiving and sending tasks and the drawing and display tasks respectively.

15. An electronic device, characterized in that: include: processor; A memory stores a computer program, which is configured to implement the display and control software architecture construction method of claim 1 when executed by the processor.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, can implement the display and control software architecture construction method described in claim 1.

Images