Man-machine interface for aircraft cockpit
The introduction of two pointing modes in the man-machine interface simplifies text entry operations by allowing simultaneous interaction with navigation maps, addressing the issue of data loss and improving efficiency for aircraft pilots.
Patent Information
- Application Number
- EP2024177593
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-26
- Filing Date
- 2024-05-23
- Publication Date
- 2024-11-27
AI Technical Summary
Aircraft pilots face difficulties in entering information via man-machine interfaces due to the need to switch between text entry and navigation map interactions, often resulting in lost data when trying to consult navigation maps while entering waypoints.
Implementing two pointing modes in the man-machine interface: specific pointing mode for text entry and normal pointing mode for navigation, allowing simultaneous interaction with a navigation map without losing entered information, with features like keyboard assignment and entry history recording.
Simplifies text entry operations by enabling pilots to interact with navigation maps without aborting text entry, ensuring data integrity and reducing the need for manual note-taking, while allowing for easy access to previously entered information.
Smart Images

Figure IMGAF001_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present invention relates to a human-machine interface for aircraft. More particularly, the present invention relates to a pointing system for displaying information on a screen of an aircraft human-machine interface. STATE OF PRIOR ART
[0002] Typically, when a pilot wants to input information using an aircraft cockpit human-machine interface (HMI) so that this information can be transmitted to the aircraft's avionics, the pilot selects a text input area displayed on the HMI screen. When using a pointing device (such as a mouse, trackball, or touchpad), selecting involves moving a cursor over the text input area with the device and clicking to confirm the selection. When using a touchscreen, selecting involves touching the touchscreen (sometimes with multiple fingers, possibly followed by a subsequent movement) over the text input area.
[0003] Once the cursor is positioned over the text input area, it is locked within that area. Often represented by a blinking vertical bar, the cursor remains locked until the driver confirms or cancels the text entry. Moving the cursor to another part of the screen cancels the text entry, and any information already entered but not confirmed is lost.
[0004] This can pose a problem when the pilot needs to consult information on an on-screen navigation chart to determine what information to enter in the text input field, or even to interact with the chart (zoom, pan, etc.). This can be useful, for example, when searching for information about a waypoint on the aircraft's flight path that the pilot must enter in the text input field. Therefore, when the pilot needs to enter information for several waypoints, they must first consult the navigation chart, write it down, mark the waypoint in the text input field, and then enter the information using a keyboard, transferring the notes from the paper.
[0005] It is therefore desirable to overcome these drawbacks of the state of the art. In particular, it is desirable to provide a solution that simplifies text entry operations that must be performed by an aircraft pilot using such a human-machine interface. DESCRIPTION OF THE INVENTION
[0006] A pointing management method is proposed here for a display on a screen of an aircraft cockpit human-machine interface, the display comprising areas including a text input area, a navigation map area, and at least one other area, each area being associated with commands that can be performed by pointing on said area.A human-machine interface controller implements two pointing modes: one called the specific pointing mode, which is active when text is being entered in the text input area, and the other called the normal pointing mode, which is active when no text is being entered in the text input area. In normal pointing mode, pointing to a said area triggers the command possibly associated with the location where the pointing is made in that area; and in specific pointing mode, pointing to the text input area or the navigation map area triggers the command possibly associated with the location where the pointing is made in that area, and pointing to said at least one other area triggers an abandonment of text entry, with the commands of said at least one other area being disabled, unlike the commands of the text input area and the navigation map area.
[0007] Thus, the text entry operations to be carried out by an aircraft pilot through this human-machine interface are simplified, thanks to the implementation of these two pointing modes, allowing text entry while accepting to manipulate a navigation map (aerial or airport).
[0008] In a particular embodiment, the controller assigns a human-machine interface keyboard specifically for text input in a specific pointing mode and assigns the keyboard for general human-machine interface use in normal pointing mode.
[0009] In a particular embodiment, when a text entry abandonment is triggered, any information entered in the text input area and not validated is recorded in an input history, and an access functionality to the input history is enabled in a specific pointing mode and not in normal pointing mode.
[0010] In one particular embodiment, any information entered in the text input area and validated is also recorded in the input history.
[0011] In a particular embodiment, when the input history access feature is enabled, the text input area is expanded to display the input history so as to partially cover an inactive area in a specific pointing mode.
[0012] Also proposed herein is a computer program product comprising program code instructions that cause an implementation of the above process in any of its embodiments when said instructions are executed by an aircraft cockpit human-machine interface processor. Also proposed herein is an information storage medium that stores a computer program comprising program code instructions that cause an implementation of the above process in any of its embodiments when said instructions are read and executed by an aircraft cockpit human-machine interface processor.
[0013] Also proposed here is an aircraft cockpit human-machine interface comprising a screen and a controller. The controller includes electronic circuitry configured to perform pointing management for display on the screen. The display includes zones, among them a text input zone, a navigation map zone, and at least one other zone. Each zone is associated with commands that can be executed by pointing at that zone. The electronic circuitry is configured to implement two pointing modes: a specific pointing mode, which is active when text is being entered in the text input zone, and a normal pointing mode, which is active when no text is being entered in the text input zone. In normal pointing mode, pointing at a zone triggers the command possibly associated with the location where the pointing occurs within that zone.and in specific pointing mode, pointing to the text input area or the navigation map area triggers the command possibly associated with the location where the pointing is made on the area in question, and pointing to said at least one other area triggers an abandonment of text input, the commands of said at least one other area being disabled unlike the commands of the text input area and the navigation map area.; BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The features of the invention mentioned above, as well as others, will become clearer upon reading the following description of at least one exemplary embodiment, said description being made in relation to the accompanying drawings, among which: [ Fig. 1 [ ] schematically illustrates, in perspective, an aircraft; [ Fig. 2 ] schematically illustrates an example of a display implemented by an aircraft cockpit human-machine interface; [ Fig. 3 ] schematically illustrates an algorithm for switching from a normal pointing mode to a specific pointing mode; [ Fig. 4 ] schematically illustrates an algorithm for switching from the specific pointing mode to the normal pointing mode; [ Fig. 5 ] schematically illustrates a timekeeping management process algorithm, depending on whether the human-machine interface is in specific timekeeping mode or normal timekeeping mode; Fig. 6 ] schematically illustrates the example of a human-machine interface of the Fig. 2 after switching to a specific pointing mode; and [ Fig. 7 ] schematically illustrates an example of a hardware arrangement enabling the implementation of the human-machine interface. DETAILED DESCRIPTION OF IMPLEMENTATION METHODS
[0015] There Fig. 1 This schematically illustrates, in perspective, an aircraft 100. Aircraft 100 is equipped with avionics that have at least one human-machine interface. The human-machine interface is installed in the aircraft's cockpit and is configured to allow the aircraft pilot to view and manipulate information on a screen of said human-machine interface, and to input information to be transmitted to the aircraft's avionics. For example, the input information is information for at least one waypoint of the aircraft according to a flight plan. This at least one waypoint can be located on a navigation chart (aeronautical or airport) displayed on the screen. Other information can thus be entered by the aircraft pilot. An example of a hardware arrangement for implementing the human-machine interface is presented below in relation to the Fig. 7 .
[0016] As detailed later, the human-machine interface is configured to implement two pointing modes (exclusive of each other), referred to here as "normal pointing mode" and "specific pointing mode".
[0017] There Fig. 2 schematically illustrates an example of a 200 display achieved by such a human-machine interface.
[0018] Display 200 includes a text input area 201. Display 200 may include multiple text input areas. Through this text input area 201, the pilot can enter information using a keyboard and transmit the entered information to the avionics. Text input area 201 includes a display field 206 for the entered information and may include a virtual button 207 for confirming text entry. Text input area 201 may also include a virtual button (not shown) for canceling text entry.
[0019] The specific pointing mode is active when text is being entered in text input area 201, and the normal pointing mode is active when no text is being entered in text input area 201.
[0020] The text input area 201 is thus active in normal pointing mode and in specific pointing mode.
[0021] Display 200 includes a navigation chart area 203. Through this navigation chart area 203, the pilot can manipulate one or more navigation charts (aeronautical or airport). The navigation chart area 203 may offer various virtual buttons 204a, 204b, 204c for actions (commands) related to the content of the navigation chart area 203.
[0022] This navigation map area 203 is compatible with parallel text entry. Therefore, the navigation map area 203 is active in both normal pointing mode and specific pointing mode.
[0023] Thus, in this specific pointing mode, both the text input area 201 and the navigation map area 203 are active simultaneously. These two areas, 201 and 203, therefore have simultaneous focus. Specifically, an interaction in the navigation map area 203 does not cause the text input area 201 to lose focus; it therefore retains previously entered text and remains ready to receive text input after, or even during, the interaction.This allows a user, particularly a pilot, to begin entering text in the text input area 201 using a text input device (e.g., a keyboard), then interact with the navigation map in the navigation map area 203 via the human-machine interface (e.g., to search for or verify information needed for the current text entry) without losing information already entered in the text input area 201, and then continue entering text in the text input area 201. The user does not need to perform any specific action before continuing to enter text in the text input area 201 after manipulating the navigation map 203: they simply need to continue entering text using the text input device.For example, the user does not need to perform a specific action such as bringing a cursor and clicking on the 201 text input area before continuing to enter text.
[0024] Display 200 includes another area, 202. This area 202 is incompatible with parallel text entry. Therefore, this other area 202 is active in normal pointing mode but inactive in specific pointing mode. In other words, in specific pointing mode, pointing to this other area 202 does not execute a specific command associated with the pointing location within that area, a command that would be executed in normal pointing mode. For example, this other area 202 is intended for entering a new aircraft heading, changing the aircraft's current speed or altitude, setting a VHF communication frequency with air traffic control, and so on.
[0025] When the human-machine interface includes a pointing device separate from the screen (such as a mouse, trackball, or touchpad) to allow the pilot to use said human-machine interface, the display 200 includes a cursor 205 (represented by an arrow on the Fig. 2 ). The pilot uses the pointing device in question to move the cursor 205 on the display 200, in order to perform pointing operations at the location where the cursor 205 is positioned.
[0026] When the human-machine interface has a touch screen (i.e., without a pointing device separate from the screen), display 200 does not require cursor 205.
[0027] In normal pointing mode, the pilot can interact with each area of the display (200), meaning that commands specific to each area are possible by pointing within that area (for example, by pointing to a virtual button in that area). In specific pointing mode, the pilot can only interact with the text input area (201) and the navigation map area (203), meaning that only commands specific to the text input area (201) and the navigation map area (203) are possible by pointing within those areas. Commands specific to each other area (202) are then disabled.
[0028] There Fig. 3 schematically illustrates an algorithm for switching from normal pointing mode to specific pointing mode.
[0029] In step 301, the human-machine interface is in normal pointing mode.
[0030] In step 302, the human-machine interface detects a point in the text input area 201.
[0031] In an optional step 303, the human-machine interface activates a feature for accessing an input history. The input history is a record of information previously entered in the text input area 201, which the driver can later access to repeat or continue entering information.
[0032] In step 304, the human-machine interface preferentially displays an input cursor in field 206 for displaying entered information.
[0033] In step 305, the human-machine interface assigns the keyboard solely to text entry in text input area 201. Only the buttons on the keyboard that are intended for a text entry operation are affected. Any other button not intended for a text entry operation is unaffected and can be assigned to a command related to the navigation map area 203 (or to a command to cancel text entry).
[0034] In step 306, the human-machine interface switches to a specific pointing mode. Then, the algorithm is terminated. Fig. 3 .
[0035] There Fig. 4 schematically illustrates an algorithm for switching from the specific pointing mode to the normal pointing mode.
[0036] In step 401, the human-machine interface is in a specific pointing mode. Therefore, text entry is in progress in text input area 201.
[0037] In step 402, the human-machine interface detects either a disengagement of the input cursor (i.e., an abandonment of text entry) or a confirmation of text entry. Text entry confirmation is detected, for example, by pressing a dedicated keyboard button (e.g., a key labeled "ENTER") or by clicking on the virtual button 207, which is used for text entry confirmation actions. Text entry abandonment is detected, for example, by pressing a dedicated keyboard button (e.g., a key labeled "ESC") or by clicking on an inactive area in a specific pointing mode (area 202).
[0038] In step 403, the human-machine interface saves the information in field 206 (the input display) to the input history (if the interface implements the functionality to access such an input history). If field 206 is empty, step 403 is omitted. In a particular embodiment, the human-machine interface saves the information in field 206 only in the input history if text entry is abandoned. This allows the user to resume text entry that was interrupted by the driver to perform a higher-priority operation.
[0039] In a 404 step (if step 303 has been performed), the human-machine interface disables the functionality to access the input history.
[0040] In step 405, the human-machine interface reassigns the keyboard for general human-machine interface use. Thus, the buttons used for text input can be used to execute commands in other areas of display 200.
[0041] In step 406, the human-machine interface (HMI) clears the input cursor from field 206 of the input display. When the HMI detects text input validation in step 402, it clears the entered information from field 206 of the input display. In a particular embodiment, the HMI also clears the entered information from field 206 of the input display when it detects an abandonment of text input in step 402.
[0042] In step 407, the human-machine interface switches to normal pointing mode. Then, the algorithm is terminated. Fig. 4 .
[0043] There Fig. 5 schematically illustrates a timekeeping management process algorithm, depending on whether the human-machine interface is in specific timekeeping mode or in normal timekeeping mode.
[0044] In a 501 step, the human-machine interface detects that a pointing operation is performed.
[0045] In step 502, the human-machine interface determines which pointing mode the human-machine interface is in. When the human-machine interface is in normal pointing mode, step 503 is performed; otherwise, when the human-machine interface is in the specific pointing mode, step 504 is performed.
[0046] In step 503, the human-machine interface performs an action (command) associated with pointing, independently of any restrictions imposed by the ongoing text entry. The specific command, if it exists, for the location where pointing is performed is executed.
[0047] In step 504, the human-machine interface determines which area of display 200 is involved in the pointing. When the area of display 200 involved in the pointing is the text input area 201 or the navigation map area 203, a step 505 is performed; otherwise, a step 506 is performed.
[0048] In step 505, the human-machine interface performs an action (command) associated with the pointing. The specific command, if it exists, for the location where the pointing is performed is executed. For example, zooming or panning a map displayed in the navigation map area 203, or moving the input cursor in the text input area 201. Then, the algorithm is terminated. Fig. 5 .
[0049] In step 506, the human-machine interface disengages the input cursor; that is, the human-machine interface abandons text input. Indeed, the pointing was performed outside the text input area 201 and outside the navigation map area 203, while the specific pointing mode was activated (meaning that the specific commands for any other area 202 are deactivated). The algorithm of the Fig. 4 is therefore executed and the human-machine interface switches to normal pointing mode. Then, the algorithm is terminated. Fig. 5 .
[0050] In a particular embodiment, when the cursor 205 is moved to said other area 202, a symbol is displayed on the screen to warn that the specific pointing mode is activated and that pointing (clicking) on this other area 202 will cause the specific pointing mode to exit and return to the normal pointing mode.
[0051] There Fig. 6 schematically illustrates the example of a human-machine interface of the Fig. 2 after switching to a specific pointing mode.
[0052] On the Fig. 6 In field 206, the entered information display shows the input cursor 601. For example, the input cursor 601 is shaped like an "I". The input cursor 601 can have a different shape, such as a simple vertical bar. For instance, the input cursor 601 blinks to increase its visibility in display 200.
[0053] On the Fig. 6 Area 202 is hatched to schematically show that said area 202 is inactive in the specific pointing mode. Thus, pointing to area 202 triggers an exit from the specific pointing mode, and the text entry in progress in text input area 201 is abandoned.
[0054] In the specific pointing mode, a notification banner can be integrated into the display to indicate that the specific pointing mode is activated. Alternatively, such a notification banner can be displayed temporarily when the pointing mode changes (specific pointing mode activated / deactivated).
[0055] In a particular embodiment, in the specific pointing mode, the display 200 can be modified relative to the Fig. 2 by placing an opaque layer over area 202 to explicitly indicate that the specific pointing mode is engaged.
[0056] On the Fig. 6 The text input area 201 is enhanced to display the input history 602, in which the user can point to select a previously saved text entry in the input history, and thus repeat a previous entry or resume an abandoned text entry. This occurs when the input history functionality is accessed (for example, pointing to a virtual button in the text input area 201 provides access, or the input history 602 is automatically displayed when text input is enabled).
[0057] To enrich the text input area 201 with the input history 602, the text input area can be extended to partially cover an inactive area 202 in a specific pointing mode. Maintaining a partial display of this area 202 allows users to continue viewing information that can be displayed there, and also allows for easy abandonment of text entry when necessary.
[0058] Hovering over text input field 201 triggers the command associated with that location within text input field 201. For example, hovering over the virtual button 207, which validates text entry, validates the information entered in the entered information display field 206.
[0059] Pointing at the navigation map area 203 triggers the command associated with that location on the navigation map area 203. For example, pointing with two fingers and then spreading them apart in the center of the navigation map area 203 will zoom in on a navigation map displayed in that area. Or, as another example, pointing at the virtual button 204a will trigger an action associated with that virtual button.
[0060] There Fig. 7 schematically illustrates an example of a hardware arrangement enabling the implementation of the human-machine interface.
[0061] The human-machine interface includes a CTRL 700 controller, a KPAD 730 keyboard, and a DISP 740 display. The DISP 740 display can be a touchscreen, for example, using resistive or capacitive technology. The human-machine interface may include a separate pointing device PDEV 720 (such as a mouse, trackball, or touchpad), particularly when the DISP 740 display is not a touchscreen and is used solely for projecting the display 200.
[0062] In the example of physical layout of the Fig. 7The CTRL 700 controller comprises, connected by a communication bus 710: a processor or CPU (Central Processing Unit) 701; a RAM (Read-Only Memory) 702; a ROM (Read Only Memory) 703, for example of type ROM (Read Only Memory) or EEPROM (Electrically-Erasable Programmable ROM) or of type Flash; a storage unit, such as a storage medium SM 704 of type HDD (Hard Disk Drive), or a storage medium reader, such as an SD (Secure Digital) card reader; and an I / O interface manager 705.
[0063] The I / O manager 705 allows the CTRL controller 700 to interact with the KPAD keyboard 730, the DISP display 740 and the PDEV pointing device 720.
[0064] The 701 processor is capable of executing instructions loaded into RAM 702 from ROM 703, external memory, storage media (such as an SD card), or a communication network (not shown). When the human-machine interface is powered on, the 701 processor can read instructions from RAM 702 and execute them. These instructions form a computer program, causing the 701 processor to implement the steps and algorithms described herein.
[0065] All or part of the steps and algorithms described here can be implemented in software by executing a set of instructions by a programmable machine, such as a DSP (Digital Signal Processor) or a microcontroller, or implemented in hardware by a dedicated machine or electronic component (chip) or a dedicated set of electronic components (chipset), such as an FPGA (Field Programmable Gate Array) or ASIC (Application-Specific Integrated Circuit). Generally, the CTRL 700 controller includes electronic circuitry adapted and configured to implement the steps and algorithms described here.
Claims
1. Method for managing pointing for a display (200) on a screen (730) of a human-machine interface of an aircraft cockpit (100), the display (200) comprising zones including: - a text entry zone (201), - a navigation map zone (203), and - at least one other zone (202), each zone being associated with commands achievable by pointing on said zone, a controller (700) of the human-machine interface implementing two pointing modes, one called specific pointing mode which is active when text entry is in progress in the text entry zone (201), and the other called normal pointing mode which is active when no text entry is in progress in the text entry zone (201), such that: - in normal pointing mode, pointing on a said zone triggers the command possibly associated with the place where the pointing is carried out on the zone in question, and - in specific pointing mode,a pointing on the text input area (201) or on the navigation map area (203) triggers the command possibly associated with the place where the pointing on the area in question is carried out, and a pointing on said at least one other area (202) triggers an abandonment of the text input, the commands of said at least one other area (202) being deactivated unlike the commands of the text input area (201) and of the navigation map area (203)., 2. The method of claim 1, wherein in a specific pointing mode the controller (700) assigns focus to both the text input area (201) and the navigation map area (203) so as to enable a user to perform the following sequence of steps: - enter text in the text input area (201); - interact by means of the human-machine interface with the navigation map in the navigation map area (203) without losing information already entered in the text input area (201); - continue entering text in the text input area (201) without needing to perform a specific action before continuing entering text.
3. The method of claim 1 or 2, wherein the controller (700) assigns a keyboard (720) of the human-machine interface specifically to text entry in specific pointing mode and assigns the keyboard (720) to general use of the human-machine interface in normal pointing mode.
4. Method according to any one of claims 1 to 3, wherein when an abandonment of the text entry is triggered, any information entered in the text entry area (201) and not validated is recorded in an entry history, and an entry history access functionality being activated in specific pointing mode and not in normal pointing mode.
5. Method according to claim 4, in which any information entered in the text entry area (201) and validated is also recorded in the entry history.
6. The method of claim 4 or 5, wherein when the functionality for accessing the input history is activated, the text input area (201) is expanded to display the input history (602) so as to partially cover an area (202) inactive in a specific pointing mode.
7. A computer program product comprising program code instructions causing an implementation of the method according to any one of claims 1 to 6, when said instructions are executed by an aircraft cockpit human-machine interface processor.
8. An information storage medium storing a computer program comprising program code instructions causing an implementation of the method according to any one of claims 1 to 6, when said instructions are read and executed by an aircraft cockpit human-machine interface processor.
9. Aircraft cockpit human-machine interface (100) comprising a screen (730) and a controller (700), the controller comprising electronic circuitry configured to perform pointing management for a display (200) on the screen (730), the display (200) comprising zones including: - a text entry zone (201), - a navigation map zone (203), and - at least one other zone (202), each zone being associated with commands achievable by pointing on said zone, the electronic circuitry being configured to implement two pointing modes, one called specific pointing mode which is active when text entry is in progress in the text entry zone, and the other called normal pointing mode which is active when no text entry is in progress in the text entry zone, such as: - in normal pointing mode,a pointing on a said zone triggers the command possibly associated with the place where the pointing on the zone in question is carried out, and - in specific pointing mode, a pointing on the text entry zone (201) or on the navigation map zone (203) triggers the command possibly associated with the place where the pointing on the zone in question is carried out, and a pointing on said at least one other zone (202) triggers an abandonment of the text entry, the commands of said at least one other zone being deactivated unlike the commands of the text entry zone (201) and of the navigation map zone (203)., 10. A human-machine interface according to claim 9, wherein in specific pointing mode the electronic circuitry of the controller (700) is configured to assign focus to both the text input area (201) and the navigation map area (203) so as to enable a user to implement the following sequence of steps: - enter text in the text input area (201); - interact by means of the human-machine interface with the navigation map in the navigation map area (203) without losing information already entered in the text input area (201); - continue entering text in the text input area (201) without needing to perform a specific action before continuing entering text.
Citation Information
Patent Citations
ON-BOARD device FOR MANAGING DATA EXCHANGED BY AN AIRCRAFT WITH THE GROUND OR OTHER AIRCRAFT
FR2882439A1
System and method of updating a dynamic input and output device
US20170010846A1
Systems and Methods for Interacting with Multiple Applications that are Simultaneously Displayed on an Electronic Device with a Touch-Sensitive Display
US20180329550A1
