Civil aircraft cockpit display system based on IDU mutual transmission data

Abstract

The invention discloses a civil aircraft cockpit display system based on integrated display unit (IDU) mutual data transmission, which comprises an IDU, an external controller, an ARINC825 bus and an ARINC664 bus, and is characterized in that a display management DM application resides in each IDU; the DM application residing in each IDU periodically sends the current IDU health state, the display page format of each IDU, the window where a main / co-driver cursor is located, a press switching controller signal needing to be kept synchronous or data needing to be reconstructed and kept through ARINC664, and receives a page format switching signal and cursor control sent by the controller through ARINC825. The method is more suitable for the IDU integrating display and calculation functions, the dependence on an external additional processor of the IDU is reduced, the cost, the weight and the power consumption are reduced, and the method particularly has obvious competitive advantages in the future market of branch aircrafts.

Description

Technical Field

[0001] The invention belongs to the field of design of integrated avionics systems, and in particular relates to a cockpit display system of a civil aircraft based on IDU mutual data transmission. Background Art

[0002] With the continuous development of cockpit display systems in civil aircraft, integrated display units (IDUs) that integrate display and computing functions have become an inevitable development trend for regional aircraft. In order to meet the high safety level requirements of civil aircraft, IDUs can be interconnected through the highly reliable ARINC664 standard aviation data bus, so each IDU is regarded as a modular IMA.

[0003] The current display management usually relies on a display management processor that is independent of each IDU and interconnected with all IDUs. It uses centralized-distributed data interaction to realize the screen management of the display system. It lacks consideration of the applicability of the IDU with integrated display and computing functions, is not conducive to cost and weight control, and does not meet the flexibility of software development. Xu Yonggang (Xu Yonggang. Design and implementation of multi-display multi-window linkage display reconstruction management. Avionics Technology, March 2019, Vol. 50, No. 1 (Total No. 176)) proposed a design method for linkage display reconstruction management based on multi-display multi-window. This method separates the IDU state management and places it in a display management processor that is interconnected with all IDUs. The integrated display management (Interated Display Manager, DMI) software residing in the processor implements the layout management and scheduling of each IDU screen, and the window management software (Window Manager, WM) residing in each IDU completes the window page management of each IDU according to the DMI layout management instructions. However, this method must rely on an independent external processor device, which is not conducive to the flexibility of software development and is not suitable for IDUs that integrate display and computing functions. Summary of the invention

[0004] The purpose of the present invention is to provide a civil aircraft cockpit display system based on IDU mutual data transmission. The display management (Display Manager, hereinafter referred to as DM) based on IDU mutual data transmission can flexibly define the data transmission content and the master-slave instance source selection method, realize the management of the entire display system screen, and provide a visual human-computer interface interaction for the crew. It is more suitable for an IDU that integrates display and computing functions, reduces dependence on additional processors outside the IDU, and helps to reduce cost, weight, and power consumption, especially in the future market of regional aircraft. It has obvious competitive advantages.

[0005] The object of the present invention is achieved through the following technical solutions:

[0006] A civil aircraft cockpit display system based on data transmission between integrated display units (IDUs), comprising IDUs, external controllers, ARINC825 buses and ARINC664 buses, with a display management (DM) application residing inside each IDU;

[0007] The DM application residing in each IDU periodically sends the current IDU health status, the display page format of each IDU, the window where the main / co-driver cursor is located, the press-to-switch controller signal that needs to be synchronized, or the data that needs to be reconstructed and maintained through ARINC664, and receives the page format switching signal and cursor control sent by the controller through ARINC825.

[0008] Preferably, the DM residing in each IDU selects a DM as the master instance based on the health status of each IDU and the established priority order, and the other unselected DMs are used as slave instances. All slave instance DMs are set according to the press-switch controller signal sent by the master instance DM that needs to be kept synchronized, as well as the signal value of the cursor position and the display page format of each IDU.

[0009] Preferably, when the crew performs a page format switching operation through the controller, the DM resident in each IDU calculates the switched display page format based on the page switching signal received by ARINC825 and the current display format, and broadcasts it to the DM in other IDUs via the ARINC664 bus.

[0010] Preferably, when the crew performs a cursor movement operation through the controller, the DM resident in each IDU calculates the cursor position after the move based on the cursor control signal received by ARINC825 and the position of the window where the current main / co-pilot cursor is located, and broadcasts it to the DM in other IDUs via the ARINC664 bus.

[0011] Preferably, when an IDU failure occurs, the DM residing in each IDU calculates the page format to be displayed on each available IDU after reconstruction according to the health status of each IDU and broadcasts it through the ARINC664 bus.

[0012] Preferably, after an IDU failure occurs, for parameters that are displayed on other available IDUs after reconstruction and need to be maintained, the DM residing on the available IDU should be set according to the parameter values ​​displayed on the driver's side or the co-driver's side before the reconstruction occurs.

[0013] The beneficial effects of the present invention are:

[0014] The present invention identifies the ARINC825 controller signal operated by the pilot, and realizes the management of the display screen by transmitting ARINC664 data between IDUs, and realizes the synchronization of the press-to-switch controller signal and the consistency of the display screens of each IDU through the unified control of the master DM instance. The display management based on IDU mutual transmission of data adopted by the present invention is simple in design and easy to implement, and has strong practical value for regional aircraft using IDUs with integrated display and computing functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a functional block diagram of the present invention.

[0016] Figure 2 This is a flow chart of the DM master-slave instance switching function of the present invention.

[0017] Figure 3 A functional flow chart is maintained for the reconstruction of the present invention. DETAILED DESCRIPTION

[0018] The present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0019] See also Figure 1 As shown, a civil aircraft cockpit display system based on IDU mutual data transmission shown in this embodiment includes four components: IDU, each IDU has a DM application and a PFD (Primary Flight Display) application resident inside; an external controller for pilot operation to achieve human-computer interaction such as cursor control and display page switching; an ARINC825 bus for data transmission between the controller and the IDU; and an ARINC664 bus for data transmission between IDUs.

[0020] As an example, this embodiment includes 5 IDUs, 2 CCDs (Cursor Control Devices), where CCD1 is on the main driver's side and CCD2 is on the co-driver's side, and 2 DCPs (Display Control Panels), where DCP1 is on the main driver's side and DCP2 is on the co-driver's side. A DM application and a PFD application reside inside each IDU, where the PFD application has parameters that need to be reconstructed and maintained, and the parameters that need to be reconstructed and maintained are transmitted between the DM and PFD through shared memory.

[0021] The 5 IDUs and controllers are interconnected through the ARINC825 bus to receive cursor control signals, cursor inhibition signals, menu display signals, etc. from the CCD, and page format control, true / magnetic heading, navigation source, range signals, etc. from the DCP. The IDUs are interconnected through the ARINC664 bus to transmit IDU health status, the display page format of each IDU, the window where the main / co-pilot cursor is located, the press-to-switch controller signal that needs to be synchronized, and the PFD-related parameters that need to be reconstructed and maintained.

[0022] The DM app does the following:

[0023] (1) The DM application residing in each IDU periodically sends the current IDU health status, the display page format of each IDU, the window where the main / co-driver cursor is located, the press-to-switch controller signal that needs to be synchronized, or the data that needs to be reconstructed and maintained through ARINC664, and receives the page format switching signal, cursor control and other control signals sent by the controller through ARINC825.

[0024] (2) According to the health status of each IDU and the established priority order, a DM is selected from the DMs residing in each IDU as the master instance, and the other unselected DMs are used as slave instances. Figure 2 The DM master-slave instance switching function flow shown in the figure shows that when all five IDUs are in a healthy state, the default priority order is DM5-DM4-DM1-DM3-DM2, then DM5 is the master instance, DM1-DM4 are slave instances, and all slave instance DMs should be set according to the signal values ​​of true / magnetic heading, navigation source, range, cursor suppression, menu display, cursor position, and display page format of each IDU sent by the master instance DM. When the IDU where DM5 resides fails, according to the DM priority order, if the IDU where DM4 resides is healthy, DM4 will be used as the new master instance.

[0025] (3) When the crew performs a page format switching operation through the controller, the DM residing in each IDU calculates the display page format after switching based on the page switching signal received by ARINC825 and the current display format, and broadcasts it through the ARINC664 bus.

[0026] (4) When the crew member performs a cursor movement operation through the controller, the DM residing in each IDU calculates the cursor position after the move based on the cursor control signal received from ARINC825 and the position of the window where the current main / co-pilot cursor is located, and broadcasts it through the ARINC664 bus.

[0027] (5) When an IDU fails, the DM residing in each IDU calculates the page format to be displayed on each available IDU after reconstruction based on the health status of each IDU and broadcasts it via the ARINC664 bus. Figure 3 In the reconstruction and holding function flow shown in the figure, the DM and PFD residing in the IDU transmit the reconstruction and holding data through the shared memory. For the IDU whose current display format contains PFD, the DM residing therein broadcasts the PFD related parameters that need to be reconstructed and held through the ARINC664 bus. Each DM determines whether the PFD has been reconstructed from nothing to something in the IDU according to the current display format and the display format of the previous cycle. If it has occurred, it is set according to the PFD related parameter values ​​displayed on the side (driver side or co-driver side) before the reconstruction occurs.

[0028] (6) For the push-to-switch controller signals that need to be synchronized between IDUs, such as true / magnetic heading, navigation source, range, cursor suppression, menu display, etc., as well as key display signals such as the cursor position and the display page format of each IDU, they should be uniformly controlled by the master control instance DM. That is, all slave instance DMs should be set according to the above signal values ​​sent by the master control instance DM to avoid inconsistent calculation results of each DM due to asynchronous power-on of each IDU or loss of controller signals, thereby ensuring the correctness and consistency of the display screens of each IDU.

[0029] (7) After an IDU failure occurs, for parameters that need to be maintained after reconstruction and are displayed on other available IDUs, the DM residing on the available IDU should be set according to the parameter values ​​displayed on that side (driver side or passenger side) before the reconstruction occurs.

[0030] It is understandable that those skilled in the art can make equivalent substitutions or changes based on the technical solution and inventive concept of the present invention, and all these changes or substitutions should fall within the protection scope of the claims attached to the present invention.

Claims

1. A civil aircraft cockpit display system based on data transmission between integrated display units (IDU), comprising IDU, external controller, ARINC825 bus and ARINC664 bus, characterized in that: A display management DM application resides inside each IDU; The DM application residing in each IDU periodically sends the current IDU health status, the display page format of each IDU, the window where the main / co-driver cursor is located, the press-to-switch controller signal that needs to be synchronized, or the data that needs to be reconstructed and maintained through ARINC664, and receives the page format switching signal and cursor control sent by the controller through ARINC825.

2. A civil aircraft cockpit display system based on data transmission between integrated display units IDU according to claim 1, characterized in that The DM residing in each IDU selects a DM as the master instance according to the health status and established priority order of each IDU, and the other unselected DMs are set as slave instances. All slave instance DMs are set according to the press-switching controller signals sent by the master instance DM that need to be synchronized, as well as the signal values ​​of the cursor position and the display page format of each IDU.

3. A civil aircraft cockpit display system based on data transmission between integrated display units IDU according to claim 1, characterized in that When the crew switches the page format through the controller, the DM residing in each IDU calculates the switched display page format based on the page switching signal received by ARINC825 and the current display format, and broadcasts it to the DM in other IDUs through the ARINC664 bus.

4. A civil aircraft cockpit display system based on data transmission between integrated display units IDU according to claim 1, characterized in that When the crew performs cursor movement operations through the controller, the DM residing in each IDU calculates the cursor position after the move based on the cursor control signal received from ARINC825 and the position of the window where the current main / co-pilot cursor is located, and broadcasts it to the DM in other IDUs through the ARINC664 bus.

5. A civil aircraft cockpit display system based on data transmission between integrated display units IDU according to claim 1, characterized in that When an IDU failure occurs, the DM residing in each IDU calculates the page format to be displayed on each available IDU after reconstruction according to the health status of each IDU and broadcasts it through the ARINC664 bus.

6. A civil aircraft cockpit display system based on data transmission between integrated display units IDU according to claim 5, characterized in that After an IDU failure occurs, for parameters that are displayed on other available IDUs after reconstruction and need to be maintained, the DM residing on the available IDU should be set according to the parameter values ​​displayed on the driver's side or the co-driver's side before the reconstruction occurs.

Images