A display and control software architecture construction method and system, electronic equipment and medium

Abstract

The application 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, an electronic device and a medium. On the basis of dividing the display and 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 aperiodic tasks, the priority of the data transceiving tasks is higher than that of the drawing display tasks, and when the display screen is updated, the corresponding drawing display task is switched to a ready state by the data transceiving task, the drawing display task is woken up to participate in scheduling, the display screen is drawn, and after the drawing is completed, the drawing display task is suspended by itself to enter a blocked state. Based on the idea of data driving, the tasks of the display and control software are more reasonably divided and designed, the software architecture is constructed, and the real-time performance of the display and 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] Aircraft display and control software is a critical component of an aircraft's avionics system. It provides pilots with comprehensive information display and human-machine interactive control capabilities through the system's hardware and software platforms. As the direct interface for aircraft display control, onboard display and control software must possess real-time capabilities. Therefore, it typically runs on embedded real-time operating systems such as VxWorks and Tianmai.

[0003] Embedded real-time operating systems (RTOSs) provide users with efficient real-time multitasking scheduling to ensure high application software efficiency. The task scheduling strategy of an embedded RTOS prioritizes high-priority tasks using preemptive scheduling, supplemented by a round-robin scheduling algorithm to concurrently execute multiple tasks of the same priority. This scheduling method prioritizes urgent tasks with higher priority, ensuring the real-time performance of urgent and important tasks, while allowing tasks of the same priority to execute concurrently.

[0004] A task in a real-time operating system can have multiple states, the most basic of which 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 executing;

[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 will 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 priority of tasks into 256 levels (0 to 255), with priority 0 being the highest priority and priority 255 being the lowest priority.

[0011] Currently, in order to ensure the real-time performance of airborne display and control software, tasks are divided and designed during the design of the display and control software architecture. There are two commonly used task division and construction methods. The first is to concentrate the data transmission and reception function and the drawing display function into a non-periodic task to simplify the complexity of software parallel design. Since the execution time of the drawing display function will be prolonged with the increasing complexity of the display content, the real-time control response in the data transmission and reception function cannot be guaranteed; the second is to design the data transmission and reception function and the drawing display function into two different periodic tasks to ensure the real-time control response, but it will produce a display time delay of a maximum of one 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 method, system, electronic device and medium for constructing a display and control software architecture to overcome or alleviate at least one of the known technical deficiencies.

[0014] The technical solution of this application is:

[0015] On the one hand, a method for constructing a display and 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 state 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 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 method for constructing a display and control software architecture further includes:

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

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

[0023] According to at least one embodiment of the present application, in the above-mentioned display and 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 and 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 has been 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 sending and receiving task is updated, it is judged that the display screen has been updated. 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 has been 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 and 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 set 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 sending and receiving task will switch the corresponding drawing display task to the ready state, wake up the drawing display task to participate in scheduling, and draw the display screen. After the drawing is completed, the drawing display task will suspend itself and enter the blocked state.

[0033] According to at least one embodiment of the present application, the above-mentioned display and 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 and control software architecture construction system, in the task type division module, the task types of the display and control software are divided according to the display and control system configuration, wherein the number of drawing display tasks is determined according to the number of displays driven by the display and 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 has been 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 transmission and reception task is updated, it is judged that the display screen has been updated. The specific settings are:

[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 has been updated.

[0040] According to at least one embodiment of the present application, in the above-mentioned display and control software architecture construction system, 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.

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

[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. 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 and control software architecture. Based on the division of the display and control software into data transceiver tasks and drawing and display tasks, the data transceiver tasks and the drawing and display tasks are respectively set as periodic tasks and non-periodic tasks, and the data transceiver tasks have a higher priority than the drawing and display tasks. Furthermore, when the display screen is updated, the data transceiver task switches the corresponding drawing and display task to a ready state, awakens the drawing and display task to participate in scheduling, and draws the display screen. After the drawing is completed, the drawing and display task suspends itself and enters a blocked state. Based on the data-driven concept, the display and control software tasks are divided and designed more reasonably, and the software architecture is constructed, thereby improving the real-time performance of the display and control software. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0048] Figure 2 This is a schematic diagram of the display screen update judgment logic provided by an 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 this 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 understood as limiting this application. DETAILED DESCRIPTION

[0051] To make the technical solution and its advantages of this application more clear, the technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described here are only some of the embodiments of this application and are only used to explain this application, not to limit this application. It should be noted that for ease of description, only the parts relevant to this application are shown in the accompanying drawings, and other relevant 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 should have the usual meanings understood by those skilled in the art in the field to which this application belongs. The words indicating orientation used in the description of this application 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 means 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 stipulated 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 and control software architecture is provided, such as Figure 1 As shown in the figure, the tasks of the display and control software are divided and designed based on the data-driven idea, which ensures the real-time control response and 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 to be 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 state 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 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 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 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 sending and receiving tasks and drawing display tasks.

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

[0066] The display and control software architecture construction method disclosed in the above embodiment divides the display and control software into data sending and receiving tasks and drawing and display tasks, and sets the data sending and receiving tasks and the drawing and 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 and display tasks. It is also arranged that when the display screen is updated, the data sending and receiving tasks switches the corresponding drawing and display tasks to the ready state, wakes up the drawing and display tasks to participate in the scheduling, and draws the display screen. After the drawing is completed, the drawing and display tasks suspend themselves and enter the blocked state. Based on the data-driven idea, the display and 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 and 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 on the display include flight direction (PFD), navigation (ND), system diagram (SYS), engine (EICAS), flight management (FMS), checklist (CHECK) and central maintenance (CMS) screens. Using the display and control software architecture construction method disclosed in the above embodiment, the display and control software architecture is constructed 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 into one 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. When the display screen is displayed and the corresponding driver data in the data transceiver task DataRecvTask is updated, the data transceiver 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 has been 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, the data receiving and sending task DataRecvTask is set 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 can be bound to the data receiving and sending task DataRecvTask and the drawing display tasks RenderTask1 and RenderTask2 respectively.

[0076] By applying the display and control software architecture construction method disclosed in the above embodiment, on the basis of dividing the airborne display and control software into data transceiver tasks and drawing display tasks, the data transceiver tasks and the drawing display tasks are set as periodic tasks and non-periodic tasks respectively, and the priority of the data transceiver tasks is higher than that of the drawing display tasks. In addition, when the display screen is updated, the data transceiver task switches the corresponding drawing display task to a ready state, wakes up the drawing display task to participate in scheduling, and draws the display screen. After the drawing is completed, the drawing display task suspends itself and enters a blocked state. Based on the data-driven idea, the tasks of the airborne display and 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 and control software, and ensure that the control response of the airborne display and control software and the real-time performance of its drawing display can well meet the system requirements.

[0077] On the other hand, a display and 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 receiving and sending task and the drawing and displaying task, and the priority of the data receiving and sending task is set to be higher than the priority of the drawing and displaying 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 sending and receiving task switches the corresponding drawing display task to the ready state, wakes up the drawing display task to participate in 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 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 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 CPU cores to data sending and receiving tasks and drawing display tasks.

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

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

[0090] In addition, technical personnel 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. Technical personnel 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 random access memory (RAM) and / or cache memory, and the non-volatile memory may be read-only memory (ROM), a hard disk, a flash memory, etc. The memory may store a computer program, and the processor executes the computer program to implement the functions of the embodiments of the present application and / or other desired functions. In addition, the memory may also store various application programs and various data.

[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, etc.

[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 on its memory, its technical effects can refer to the technical effects of the above-mentioned display and control software architecture construction method part, and will not be repeated here.

[0099] On the other hand, a computer-readable storage medium is provided, which stores a computer program. 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, a 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 replacements to the relevant technical features, and the technical solutions after these changes or replacements 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 state 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 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, wherein: Also includes: Task CPU core binding steps: Bind CPU cores to data sending and receiving tasks and drawing display tasks.

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

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

5. The method for constructing a display and control software architecture according to claim 4, wherein: 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, wherein: In the task status switching setting step, the judgment logic for whether the display screen has been 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 sending and receiving task is updated, it is judged that the display screen has been 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 has been updated.

7. The method for constructing a display and control software architecture according to claim 6, wherein: 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 and 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 set higher than that of drawing display tasks; Task state switching setting module: used to set that when the display screen is updated, the data sending and receiving task will switch the corresponding drawing display task to the ready state, wake up the drawing display task to participate in scheduling, and draw the display screen. After the drawing is completed, the drawing display task will suspend itself and enter 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 and control software are divided according to the display and control system configuration. Among them, the number of drawing display tasks is determined according to the number of displays driven by the display and 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 has been 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 sending and receiving task is updated, it is judged that the display screen has been 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 sending and receiving tasks and the drawing 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 according to 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