Human-machine interface for aircraft cockpit
By introducing two specific and normal pointing modes into the robot interface, the problem of cumbersome switching between text input and navigation diagram manipulation is solved, and the function of continuous text input during navigation diagram manipulation is realized, which improves operation efficiency.
Patent Information
- Application Number
- CN202410520723.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-26
- Filing Date
- 2024-04-28
- Publication Date
- 2024-11-26
AI Technical Summary
When performing text input operations, it is difficult to switch between the manipulation of the navigation diagram and the input of the text, resulting in cumbersome and inefficient operations.
Two pointing modes are adopted: specific pointing mode and normal pointing mode. The text input area and navigation map area are active at the same time in the specific mode, allowing text input to continue during navigation map manipulation; the pointing action of other areas in normal mode triggers commands, text input The guidance action in the area abandons text input.
The pilot's text input operation is simplified, allowing text information to continue to be input during the operation of the navigation diagram, avoiding frequent switching operations, and improving operation efficiency.
Smart Images

Figure CN119024993A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a human-machine interface for an aircraft. More specifically, the present invention relates to managing pointing actions with respect to a display interface on a screen of a human-machine interface for an aircraft. Background Art
[0002] Typically, when a pilot wishes to input information through a human-machine interface (HMI) in the cockpit of an aircraft in order to transmit the information to the avionics equipment of the aircraft, the pilot performs a pointing action in a text input area in a display interface provided on the screen of the human-machine interface. In the case of using a pointing device (such as a mouse, a trackball or a touchpad), the pointing action includes moving a cursor to the text input area with the aid of the pointing device and includes clicking on the location to confirm the pointing action. In the case of using a touch screen, the pointing action includes touching the touch screen in the text input area in question (sometimes with more than one finger and possibly with subsequent movement).
[0003] Once a pointing action is performed in the text input area, the cursor is constrained to the text input area. Usually indicated by a flashing vertical bar, the cursor remains constrained until the pilot confirms or abandons the text input. Making an action on another part of the screen causes the text input to be abandoned, and the information that has been entered but not confirmed is lost.
[0004] This can cause problems when the pilot wishes to consult the information she or he needs on the navigation map displayable on the screen to determine the information she or he must enter in the text input area or indeed wishes to make an action on the navigation map (zoom in, pan the navigation map, etc.). This can be, for example, a useful way to search for information related to waypoints of the aircraft path that the pilot must enter in the text input area. Thus, when the pilot must enter a series of pieces of information related to a number of waypoints, she or he must first retrieve this information from the navigation map, then write this information on a piece of paper, perform pointing actions in the text input area, and finally enter this information with the help of the keyboard while referring to the information marked on the piece of paper.
[0005] It is therefore desirable to overcome these drawbacks of the prior art. In particular, it is desirable to provide a solution that allows the text input operations that must be performed by an aircraft pilot via such a human-machine interface to be simplified. Summary of the invention
[0006] A method for managing pointing actions on a display interface on a screen of a human-machine interface in an aircraft cockpit is provided, the display interface comprising a plurality of areas including a text input area, a navigation map area, and at least one other area, each area being associated with a command that can be activated by performing a pointing action in the area. The controller of the human-machine interface implements two pointing modes, one of which is called a specific pointing mode, which is active when text input is performed in the text input area, and the other is called a normal pointing mode, which is active when text input is not performed in the text input area. The controller of the human-machine interface implements the two pointing modes so that: in the normal pointing mode, a pointing action in the area triggers a command (if there is any command associated with the location where the pointing action is performed in the area in question); and in the specific pointing mode, a pointing action in the text input area or the navigation map area triggers a command (if there is any command associated with the location where the pointing action is performed in the area in question), and a pointing action in at least one other area triggers abandonment of text input. Contrary to the commands of the text input area and the navigation map area, the commands of the at least one other area are disabled.
[0007] Thus, the text input operations that must be performed by the aircraft pilot via such a human-machine interface are simplified by means of the implementation of these two pointing modes, thereby allowing the input of texts while tolerating the manipulation of the (aeronautical or airport) navigation chart.
[0008] In one particular embodiment, the controller specifically designates the keyboard of the human-machine interface for text entry in the special pointing mode and designates the keyboard for general use of the human-machine interface in the normal pointing mode.
[0009] In a particular embodiment, when abandoning text input is triggered, any information that has been entered into the text input area but not confirmed is recorded in the input history, and the input history access function is activated in a specific pointing mode but not in a normal pointing mode.
[0010] In one particular embodiment, any information that has been entered into the text entry area and confirmed is also recorded in the input history.
[0011] In one specific embodiment, when the input history access function is activated, the text input area is expanded to display the input history, thereby partially overlapping the area that is inactive in the specific pointing mode.
[0012] A computer program product is also provided herein, the computer program product comprising program code instructions, which, when executed by a processor of a human-machine interface of a cockpit of an aircraft, cause any one of the embodiments of the above method to be implemented. A data storage medium is also provided herein, the data storage medium storing program code instructions, which, when read and executed by a processor of a human-machine interface of a cockpit of an aircraft, cause any one of the embodiments of the above method to be implemented.
[0013] Also provided herein is a human-machine interface for an aircraft cockpit, the human-machine interface comprising a screen and a controller, the controller comprising an electronic circuit system configured to manage pointing actions on a display interface on the screen, the display interface comprising a plurality of areas, the areas comprising a text input area, a navigation map area, and at least one other area, each area being associated with a command that can be activated by performing a pointing action in the area. The electronic circuit system is configured to implement two pointing modes, one is called a specific pointing mode, which is active when text input is performed in the text input area, and the other is called a normal pointing mode, which is active when text input is not performed in the text input area. The electronic circuit system is configured to implement the two pointing modes so that: in the normal pointing mode, a pointing action in the area triggers a command (if there is any command associated with the location where the pointing action is performed in the area in question); and in the specific pointing mode, a pointing action in the text input area or the navigation map area triggers a command (if there is any command associated with the location where the pointing action is performed in the area in question), and a pointing action in at least one other area triggers abandonment of text input, and, contrary to the commands of the text input area and the navigation map area, the commands of the at least one other area are disabled. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The above-mentioned features and other features of the present invention will become more clearly apparent upon reading the following description of at least one exemplary embodiment, which is given with reference to the accompanying drawings, in which:
[0015] [ Figure 1 ] schematically illustrates an aircraft in perspective;
[0016] [ Figure 2 ] schematically illustrates an example of a display interface generated by a human-machine interface of a cockpit of an aircraft;
[0017] [ Figure 3 ] schematically illustrates an algorithm for switching from a normal pointing mode to a specific pointing mode;
[0018] [ Figure 4] schematically illustrates an algorithm for switching from a specific pointing mode to a normal pointing mode;
[0019] [ Figure 5 ] schematically illustrates an algorithm of a method for managing pointing actions depending on whether a human-machine interface is in a specific pointing mode or a normal pointing mode;
[0020] [ Figure 6 ] schematically illustrates the following process after switching to a specific pointing mode. Figure 2 Examples of human-machine interfaces; and
[0021] [ Figure 7 ] schematically illustrates an example of a hardware layout that allows implementation of a human-machine interface. DETAILED DESCRIPTION
[0022] therefore, Figure 1 An aircraft 100 is schematically illustrated in a perspective view. The aircraft 100 is equipped with avionics equipment having at least one human-machine interface. The human-machine interface is installed in the cockpit of the aircraft and is configured to allow the pilot of the aircraft to observe and manipulate information on a screen of the human-machine interface, as well as to input information to be transmitted to the avionics equipment of the aircraft. For example, the input information is information about at least one waypoint of the aircraft according to the flight plan. The at least one waypoint may be identified on a navigation chart (aeronautical or airport) displayed on the screen. Thus, the pilot of the aircraft may input other information. Figure 7 An example of a hardware layout allowing the implementation of a human-machine interface is presented.
[0023] As described in detail below, the human-machine interface is configured to implement two (mutually exclusive) pointing modes, referred to herein as "normal pointing mode" and "special pointing mode".
[0024] Figure 2 An example of a display 200 generated by such a human-machine interface is schematically illustrated.
[0025] The display interface 200 includes a text input area 201. The display interface 200 may include multiple text input areas. Through the text input area 201, the pilot can enter information through the keyboard and transmit the entered information to the avionics. The text input area 201 includes a field 206 for displaying the entered information and may include a virtual action button 207 for confirming the text input. The text input area 201 may also include a virtual action button (not shown) for abandoning the text input.
[0026] When text input is performed in the text input area 201 , the specific pointing mode is active, and when text input is not performed in the text input area 201 , the normal pointing mode is active.
[0027] Therefore, the text input area 201 is active in both the normal pointing mode and the special pointing mode.
[0028] The display interface 200 includes a navigational chart area 203. Through the navigational chart area 203, the pilot can manipulate one or more (airline or airport) navigational charts. The navigational chart area 203 may include various virtual action (command) buttons 204a, 204b, 204c, and the associated actions (commands) are related to the content of the navigational chart area 203.
[0029] The navigation map area 203 is compatible with text input in parallel. Therefore, the navigation map area 203 is active in both normal pointing mode and special pointing mode.
[0030] Thus, in a specific pointing mode, both the text input area 201 and the navigation map area 203 are active at the same time. Therefore, the two areas 201 and 203 have focus at the same time. In particular, the interaction in the navigation map area 203 does not cause the focus to be lost from the text input area 201, and the text input area 201 therefore retains the text information that has been entered and therefore remains ready to receive text input after or even during the interaction. This allows a user (particularly a pilot) to start text input in the text input area 201 by means of a text input device (e.g., a keyboard), then interact with the navigation map in the navigation map area 203 by means of a human-machine interface (e.g., to search for or verify the information necessary for the ongoing text input) without losing the information that has been entered in the text input area 201, and then continue text input in the text input area 201. The user does not need to perform any specific actions before continuing to enter text in the text input area 201 after manipulating the navigation map 203: she or he only needs to continue to enter text by means of a text input device. For example, the user does not need to perform specific actions such as moving the cursor and clicking on the text input area 201 before continuing text input.
[0031] The display interface 200 includes another area 202. This area 202 is not compatible with text input in parallel. Thus, the other area 202 is active in the normal pointing mode, but not in the specific pointing mode. In other words, in the specific pointing mode, a pointing action in the other area 202 does not activate a specific command associated with the location where the pointing action is performed in the other area 202, but on the contrary, the specific command will be executed in the normal pointing mode. For example, the other area 202 is an area intended to enter a new heading for the aircraft, to modify the current speed or altitude of the aircraft, to set the frequency of VHF communication with air traffic control, etc.
[0032] When the human-machine interface includes a pointing device other than a screen (such as a mouse, trackball, or touch pad) to allow the pilot to use the human-machine interface, the display interface 200 includes a cursor 205 (represented by Figure 2 ). The pilot uses the pointing device in question to move the cursor 205 onto the display interface 200 so as to perform a pointing operation in the position where the cursor 205 is placed.
[0033] When the human-machine interface includes a touch screen (and thus no pointing device other than the screen), display interface 200 does not require cursor 205 .
[0034] In the normal pointing mode, the pilot is able to interact with each area of the display interface 200, i.e. commands dedicated to each area can be activated via a pointing action in said area (e.g. a pointing action that activates a virtual button of the area in question). In the specific pointing mode, the pilot is able to interact only with the text input area 201 and the navigation map area 203, i.e. only commands dedicated to the text input area 201 and commands dedicated to the navigation map area 203 can be activated via a pointing action in the area in question. The commands dedicated to each of the other areas 202 are then deactivated.
[0035] Figure 3 An algorithm for switching from a normal pointing mode to a specific pointing mode is schematically illustrated.
[0036] In step 301, the human-machine interface is in a normal pointing mode.
[0037] In step 302 , the human-machine interface detects a pointing action in the text input area 201 .
[0038] In optional step 303, the human-machine interface activates an input history access function. The input history is a record of information previously entered into the text input area 201 that the pilot can subsequently access to repeat or continue information entry.
[0039] In step 304, the human-machine interface preferably causes an input cursor to appear in the field 206 for displaying the entered information.
[0040] In step 305, the human-machine interface assigns the keyboard to be used purely for text input in the text input area 201. On the keyboard, only buttons intended for operations related to text input are affected. Any other buttons not intended for operations related to text input are not affected and can be assigned to commands related to the navigation map area 203 (or commands to abandon text input).
[0041] In step 306, the human-machine interface switches to a specific pointing mode. Next, Figure 3 The algorithm terminates.
[0042] Figure 4 An algorithm for switching from the special pointing mode to the normal pointing mode is schematically illustrated.
[0043] In step 401 , the human-machine interface is in a specific pointing mode. Text input is therefore performed in the text input area 201 .
[0044] In step 402, the human-machine interface detects the detachment of the input cursor, i.e., the abandonment of the text input or the confirmation of the text input. For example, the text input can be confirmed by pressing a dedicated button on the keyboard (e.g., a key marked as "Enter") or by a pointing action on the virtual action button 207 for confirming the text input. For example, the text input is abandoned by pressing a dedicated button on the keyboard (e.g., a key marked as "ESC") or by a pointing action on an area (area 202) that is not active in a specific pointing mode.
[0045] In step 403, the human-machine interface records the information present in the field 206 for displaying the input information in the input history (if the function for accessing such an input history is implemented by the human-machine interface). If the field 206 for displaying the input information is empty, step 403 is omitted. In a specific embodiment, the human-machine interface records the information present in the field 206 for displaying the input information in the input history only if the text input is abandoned. This allows the text input to be interrupted so that the pilot can perform a higher priority operation and then return to the text input.
[0046] In step 404 (if step 303 is performed), the human-machine interface deactivates the input history access function.
[0047] In step 405 , the human-machine interface reassigns the keyboard for general use of the human-machine interface. Thus, buttons used for text input can be used to activate commands in other areas of the display interface 200.
[0048] In step 406, the human-machine interface causes the input cursor to disappear from the field 206 for displaying input information. When the human-machine interface detects confirmation of the text input in step 402, the human-machine interface causes the input information to disappear from the field 206 for displaying the input information. In a specific embodiment, when the human-machine interface detects that the text input is abandoned in step 402, the human-machine interface also causes the input information to disappear from the field 206 for displaying the input information.
[0049] In step 407, the human-machine interface switches to the normal pointing mode. Figure 4 The algorithm terminates.
[0050] Figure 5An algorithm of a method for managing pointing actions depending on whether a human-machine interface is in a specific pointing mode or a normal pointing mode is schematically illustrated.
[0051] In step 501, the human-machine interface detects that a pointing action has been performed.
[0052] In step 502, the human-machine interface determines the pointing mode the human-machine interface is in. When the human-machine interface is in the normal pointing mode, step 503 is executed; otherwise, when the human-machine interface is in the specific pointing mode, step 504 is executed.
[0053] In step 503, the human-machine interface executes the action (command) associated with the pointing action, regardless of any constraints implied by the ongoing text input. If there is a command at the location where the pointing action is performed, the specific command is executed.
[0054] In step 504, the human-machine interface determines the area of the display interface 200 that the pointing action focuses on. When the area of the display interface 200 that the pointing action focuses on is the text input area 201 or the navigation map area 203, step 505 is executed, otherwise step 506 is executed.
[0055] In step 505, the human-machine interface performs an action (command) associated with the pointing action. If there is a command at the location where the pointing action is performed, the specific command is executed. For example, the map displayed in the navigation map area 203 is enlarged or translated, or the input cursor is moved in the text input area 201. Next, Figure 5 The algorithm terminates.
[0056] In step 506, the human-machine interface disengages the input cursor, i.e., the human-machine interface abandons text input. Specifically, the pointing action is performed outside the text input area 201 and outside the navigation map area 203, and the specific pointing mode has been activated (which means that the specific commands of any other area 202 are deactivated). Figure 4 The algorithm is executed and the human-machine interface switches to normal pointing mode. Figure 5 The algorithm terminates.
[0057] In a specific embodiment, when the cursor 205 moves over the other area 202, a symbol is displayed on the screen to warn that a specific pointing mode is activated and making a pointing action (click) on this other area 202 will result in exiting the specific pointing mode and returning to the normal pointing mode.
[0058] Figure 6 Schematic illustration of the switching to a specific pointing mode Figure 2 Example of a human-machine interface.
[0059] exist Figure 6 , an input cursor 601 appears in the field 206 for displaying the entered information. As an illustration, the input cursor 601 has an "I" shape. The input cursor 601 may have another shape, such as a simple vertical bar. For example, the input cursor 601 flashes to increase its visibility in the display interface 200.
[0060] exist Figure 6 In the figure, the area 202 is shaded to schematically show that the area 202 is not active in the specific pointing mode. Thus, the pointing action in the area 202 triggers the exit from the specific pointing mode and abandons the ongoing text input in the text input area 201.
[0061] In the specific pointing mode, a notification bar may be integrated into the display interface 200 to indicate that the specific pointing mode is activated. As a variation, such a notification bar may be temporarily displayed when changing the pointing mode (activating / deactivating the specific pointing mode).
[0062] In a specific embodiment, in a specific pointing mode, the display interface 200 can be relative to Figure 2 This is modified by placing an opaque layer over region 202 to explicitly indicate that a particular pointing mode is enabled.
[0063] exist Figure 6 In the text input area 201, the text input area 201 has been enriched to display an input history 602, in which the pilot can perform a pointing action to select a text input pre-recorded in the input history, and thus reaffirm a previous input or continue an ongoing text input that has been abandoned. This happens when the input history function is accessed (e.g., a pointing action on a virtual button of the text input area 201 allows it to be accessed, or indeed the input history 602 is automatically displayed when text input is activated).
[0064] To enrich the text input area 201 with the input history 602, the text input area can be expanded to partially cover the area 202 that is inactive in a particular pointing mode. Keeping the partial display of the area 202 allows you to continue to see the information that can be displayed therein, and if necessary, you can easily abandon the text input.
[0065] The pointing action in the text input area 201 triggers a command (if there is any command associated with the location of the text input area 201 where the pointing action is performed). For example, a pointing action on the virtual action button 207 for confirming text input confirms the information entered in the field 206 for displaying the entered information.
[0066] The pointing action in the navigation map area 203 triggers a command (if there is any command associated with the location of the navigation map area 203 where the pointing action is performed). For example, a pointing action involving two fingers and then separating the two fingers at the center of the navigation map area 203 triggers zooming in on the navigation map displayed in the navigation map area 203. According to another example, a pointing action on the virtual button 204a triggers an action associated with the virtual button 204a.
[0067] Figure 7 An example of a hardware layout allowing the implementation of a human-machine interface is schematically illustrated.
[0068] The human-machine interface includes a controller CTRL 700, a keyboard KPAD 730, and a screen DISP 740. The screen DISP 740 may be a touch screen, such as a touch screen using resistive or capacitive technology. The human-machine interface may include a pointing device PDEV 720 (such as a mouse, a trackball, or a touch pad) different from the screen DISP 740, more particularly, when the screen DISP 740 is not a touch screen and is only used to project the display interface 200.
[0069] exist Figure 7 In the example of the hardware layout, the controller CTRL 700 includes, connected via a communication bus 710: a central processing unit CPU 701; a random access memory RAM 702; a read-only memory 703, for example an electrically erasable programmable ROM (EEPROM) or a flash ROM; a storage unit, such as a storage medium SM704 like a hard disk drive (HDD) or a reader of a storage medium such as an SD card reader (SD stands for Secure Digital); and an input / output interface manager I / O 705.
[0070] The input / output manager I / O 705 allows the controller CTRL 700 to interact with the keyboard KPAD 730 , the screen DISP 740 and the pointing device PDEV 720 .
[0071] The central processing unit 701 can execute instructions loaded from the read-only memory 702, from an external memory, from a storage medium (such as an SD card) or from a communication network (not shown) into the random access memory 703. When the human-machine interface is turned on, the central processing unit 701 can read instructions from the random access memory 702 and execute them. These instructions form a computer program that enables the central processing unit 701 to implement the steps and algorithms described herein.
[0072] Therefore, all or some of the steps and algorithms described herein may be implemented in software by executing a set of instructions using a programmable machine (e.g., a digital signal processor (DSP) or a microcontroller), or in hardware by a machine or a dedicated chip or chipset (e.g., a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC)). In general, the controller CTRL 700 includes an electronic circuit system designed and configured to implement the steps and algorithms described herein.
Claims
1. A method for managing pointing actions on a display interface (200) on a screen (730) of a human-machine interface of a cockpit of an aircraft (100), the display interface (200) comprising a plurality of areas, the areas comprising: Text input area (201), a navigation map area (203), and at least one other region (202), Each area is associated with a command that can be activated by performing a pointing action in said area, The controller (700) of the human-machine interface implements two pointing modes, one of which is called a specific pointing mode, which is active when text input is performed in the text input area (201), and the other is called a normal pointing mode, which is active when no text input is performed in the text input area (201). The controller (700) of the human-machine interface implements these two pointing modes so that: - in normal pointing mode, said pointing action in said area in question triggers any command, if any, associated with the location in said area where the pointing action is performed, and -In a specific pointing mode, if there is any command associated with the location where a pointing action is performed in the text input area (201) or in the navigation map area (203), the pointing action in the area in question triggers the command, and the pointing action in the at least one other area (202) triggers the abandonment of text input, and the commands of the at least one other area (202) are disabled, in contrast to the commands of the text input area (201) and the navigation map area (203).
2. The method according to claim 1, characterized in that In a specific pointing mode, the controller (700) assigns focus to both the text input area (201) and the navigation map area (203) to allow the user to perform the following sequence of steps: - Input text in the text input area (201); - interacting with the navigation map in the navigation map area (203) by means of the human-machine interface without losing the information already entered in the text input area (201); - Continue text input in said text input area (201) without having to perform any specific action before continuing text input.
3. The method according to claim 1 or 2, characterized in that The controller (700) specifically assigns a keyboard (720) of the human-machine interface for text input in a special pointing mode, and assigns the keyboard (720) for general use of the human-machine interface in a normal pointing mode.
4. The method according to any one of claims 1 to 3, characterized in that When the abandonment of text input is triggered, any information that has been input into the text input area (201) but not confirmed is recorded in the input history, and the input history access function is activated in the special pointing mode but not in the normal pointing mode.
5. The method according to claim 4, characterized in that Any information that has been entered into the text input area (201) and confirmed is also recorded in the input history.
6. The method according to claim 4 or 5, characterized in that When the input history access function is activated, the text input area (201) is expanded to display the input history (602), thereby partially overlapping the area (202) that is inactive in the specific pointing mode.
7. A computer program product comprising program code instructions which, when executed by a processor of a human-machine interface of a cockpit of an aircraft, cause the method according to any one of claims 1 to 6 to be performed.
8. A data storage medium storing a computer program product comprising program code instructions which, when read and executed by a processor of a human-machine interface of a cockpit of an aircraft, cause the method of any one of claims 1 to 6 to be performed.
9. A human-machine interface for a cockpit of an aircraft (100), the human-machine interface comprising a screen (730) and a controller (700), the controller comprising an electronic circuit system, the electronic circuit system being configured to manage pointing actions on a display interface (200) on the screen (730), the display interface (200) comprising various areas, the areas comprising: - a text input area (201), - a navigation map area (203), and - at least one other region (202), Each area is associated with a command that can be activated by performing a pointing action in said area. The electronic circuit system is configured to implement two pointing modes, one called a special pointing mode, which is active when text input is performed in the text input area, and the other called a normal pointing mode, which is active when no text input is performed in the text input area, the electronic circuit system is configured to implement the two pointing modes so that: - in normal pointing mode, a pointing action in the area in question triggers any command, if any, associated with the location in the area where the pointing action is performed, and -In a specific pointing mode, if there is any command associated with the location where the pointing action is performed in the text input area (201) or in the navigation map area (203), the pointing action in the area in question triggers the command, and the pointing action in at least one other area (202) triggers the abandonment of text input, and the commands of the at least one other area are disabled, in contrast to the commands of the text input area (201) and the navigation map area (203).
10. The human-machine interface according to claim 9, characterized in that: In a 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) to allow a user to perform the following sequence of steps: - Input text in the text input area (201); - interacting with the navigation map in the navigation map area (203) by means of the human-machine interface without losing the information already entered in the text input area (201); - Continue text input in said text input area (201) without having to perform any specific action before continuing text input.
