Interface system between a user and a display device in the cockpit of an aircraft, related aircraft and method

An interface system between a user and a display device in the cockpit of an aircraft, related aircraft and method are provided. The system includes a rotary controller configured to control a target on the display device; a target manager, controlled by the rotary controller for moving the target on the display device during the rotation of the rotary controller and/or for interacting with a field targeted by the target during the rotation of the rotary controller; a haptic feedback generator on the rotary controller during its rotation. The haptic feedback generator is configured to generate at least two distinct haptic profiles on the rotary controller depending on distinct system states and/or distinct man-machine interface states of the aircraft.

This claims the benefit of French Patent Application FR 15 02501, filed Dec. 1, 2015 and hereby incorporated by reference herein.

The present invention relates to an interface system between a user and a display device in the cockpit of an aircraft, comprising:a rotary member able to control a target on the display device;a target management assembly, controlled by the rotary member for displacing the target on the display device during the rotation of the rotary member and/or for interacting with a field targeted by the target during the rotation of the rotary member;a haptic feedback generator on the rotary member during its rotation.

Conducting a flight on an aircraft involves controlling the aircraft, conducting the navigation of the aircraft, managing the communications between the outside world and the systems of the aircraft.

These operations are carried out by the crew, from a cockpit loaded onboard the aircraft, or located in a ground station, in the case of drones.

BACKGROUND

The cockpit generally includes a display device provided with screens, and many physical and/or software interfaces giving the possibility of interacting with the systems of the aircraft.

These interfaces notably include control buttons, keyboards, rotary control members, which are for example positioned on the console located between the members of the crew, on a panel located above the display screens, under the windshield.

Certain interfaces comprising a rotary member are able to control directly or indirectly menus or/and input fields of the display device, in order to navigate between the fields on the screens, to adjust the parameters, to enter instructions, or to actuate avionic systems.

The rotation of the rotary member is carried out with a constant torque which may be felt by the user. The user is therefore unable to easily perceive where he/she is located on the screens of the display device, what type of airplane parameter is being adjusted by him/her, or what are the consequences of the actuation of an airplane system.

The user therefore must carefully track the consequences of the rotation of the rotary member, and determine by means of his/her perception what is the state of the systems of the airplane, in order to appreciate the consequences of his/her action. This consumes time for the user, and requires the attention of the user while it may be used for other purposes.

Further, in certain cases, the actuation of the rotary member on a particular field may act in a totally different way on the aircraft, notably depending on the selective adjustment for actuating the field.

For example, the consequences of a set value applied to a rate of descent, may notably vary depending on the selected type of descent mode, for example a slope in degrees, or a descent rate in feet per second.

This may have significant consequences on the conduction of the flight, notably if the user believes that he/she is in a first descent mode, while a second descent mode has been selected.

U.S. 2015/0081137 discloses an interface system of the aforementioned type, wherein a haptic feedback is provided to the user for improving the interaction with the system.

The interface system described in this document describes a single haptic profile in which the resistance provided to the user increases in the vicinity of a given set value which has to be inputted by the user.

SUMMARY OF THE INVENTION

An object of the invention is to provide an interface system further improving the interaction between the user and the display device, which allows the user to better apprehend the current configuration the aircraft.

For this purpose, a system of the aforementioned type is provided in which the haptic feedback generator is able to generate at least two distinct haptic profiles on the rotary member depending on distinct system states and/or distinct man-machine interface states of the aircraft.

The system according to the invention may comprise one or several of the following features, taken individually or according to any technically possible combination:the haptic feedback generator is a torque generator, able to be applied on the rotary member, a torque according to the haptic profile generated during the rotation of the rotary member by the user;the haptic feedback generator is able to generate distinct haptic profiles on the rotary member during the interaction with a same field targeted by the target, depending on the system states and/or on the man-machine interface states of the aircraft;the haptic feedback generator is able to generate distinct haptic profiles on the rotary member during the control of two distinct targeted fields, depending on the system states and/or the man-machine interface states of the aircraft;the distinct man-machine interface states include distinct input interface states which comprise distinct speeds of rotation of the rotary member, the haptic feedback generator being able to generate a first haptic profile to a first speed of rotation of the rotary member and a second distinct haptic profile from the first haptic profile to a second speed of rotation of the rotary member;the distinct man-machine interface states include distinct graphic interface states which comprise positions of the target on successive lists of fields on the display screen, the haptic feedback generator being able to generate a first haptic profile when the target targets a first list of fields and a second distinct haptic profile from the first haptic profile when the target targets a second list of fields;the distinct system states comprise distinct flight phases of the aircraft, the haptic feedback generator being able to generate a first haptic profile during a first flight phase of the aircraft, and of generating a second haptic profile during a second flight phase of the aircraft;the first flight phase is a low altitude transition, notably an ascent or an approach of the aircraft, the second flight phase being cruising of the aircraft;the distinct system states comprise a normal operating state of an airplane system and/or of the aircraft and a degraded operating state of an airplane system and/or of the aircraft, the haptic feedback generator being able to generate a first haptic profile in the normal operating state and being able to generate a second haptic profile in the degraded operating state;the haptic profile comprises at least one wall defining a limit of a preferred domain of use of the rotary member;each haptic profile comprises at least one notch, a first haptic profile comprising at least one first distinct notch from at least one second notch of a second haptic profile;the first haptic profile comprises a first series of successive notches, the second haptic profile comprising a second series of successive notches of profiles and/or intensity distinct from the notches of the first series.

An assembly for controlling an aircraft is also provided, including:a display device, positioned in the cockpit of the aircraft;an interaction system as described above;an avionic unit, able to interact with airplane systems, the interaction system being able to communicate with the avionics unit in order to determine the system states and/or current man-machine interface states of the aircraft.

A method for interaction between a user and a display device of an aircraft is also provided, comprising the following steps:providing an interaction system as described above;in a first system and/or man-machine interface state of the aircraft, driving into rotation the rotary member by a user, the haptic feedback generator generating a first haptic profile on the rotary member;in a second system and/or man-machine interface state of the aircraft, driving into rotation the rotary member by a user, the haptic feedback generator generating a second haptic profile on the rotary member.

The method according to the invention may comprise one or several of the following features, taken individually or according to any technically possible combination:the steps of driving into rotation of the rotary member by a user in the first system and/or man-machine interface state of the aircraft and in the second system and/or man-machine interface state of the aircraft cause interaction of the target with the same field on the display device.

DETAILED DESCRIPTION

A first aircraft control set10is schematically illustrated inFIG. 1.

The set10includes a display device12, a central avionics unit13and an interface system14between a user and the display device12.

The central avionics unit13is notably connected to airplane systems, notably measurement systems24on the aircraft, to outer communication systems26, and to systems28for actuating controls of the aircraft.

The measurement systems24for example include sensors for measuring parameters external to the aircraft, such as temperature, pressure or speed, sensors for measuring internal parameters to the aircraft and to its different functional systems and positioning sensors such as GPS sensors, inertial measurement systems, and/or an altimeter.

The control systems28include specific actuators for actuating controls of the aircraft, such as flaps, rudders, pumps, or further mechanical, electrical and/or hydraulic circuits, and software actuators able to configure the avionic states of the aircraft.

The different systems24to28are connected to the central control unit13, for example digitally, through at least one data bus circulating on a network internal to the aircraft.

The avionic central unit13includes at least one computer and a memory able to receive the pieces of information from the different systems24to28and to process them, and optionally control the systems28for executing flight commands.

The display unit12is preferably placed in the cockpit of the aircraft. It includes at least one display area30.

The display unit12further includes a display management assembly31able to control the display on said or each display area30.

Conventionally, display areas30are generally defined on primary display screens, located facing the seat of each respective crew member, on a multifunctional navigation screen and/or on a control and tracking screen of avionic systems.

The display on each display area30is controlled by the display management assembly31.

The display management assembly31is connected to the avionics central control unit13for receiving data from the different systems24,26,28of the airplane.

It includes a processor, and a memory comprising at least one software application for displaying windows32on the display area30, able to be executed by the processor.

The windows32are for example flight parameter windows, navigation windows, communication windows, and/or airplane system management windows.

The windows32are for example frames in which are displayed graphic elements. They occupy all or part of the display area30in which they are intended to be displayed.

The windows32comprise graphic elements, with which the user is able to interact, notably by means of the interface system14.

With reference toFIGS. 2 and 3, the graphic elements comprise for example menus34which may be actuated by the user, for example by selecting a field of the menu by means of the interface system14, in order to navigate in a tree structure comprising lists of fields.

The navigation notably gives the possibility of showing other windows, and/or of unfolding a procedure.

In the example ofFIG. 5, the graphic elements advantageously comprise alphanumerical data input fields36by means of the interface system14, notably for inputting a set value applied on a parameter of the aircraft.

The set values are for example control set values given to an automatic pilot or to an automatic lever, for modifying a flight parameter such as a course, a rate of descent, an engine speed.

Alternatively, the set value is a navigation set value, such as a flight plan set value or for controlling the direction of the aircraft towards a given geographical point.

Still alternatively, the set value is an outer communication set value for example a change in radiofrequency.

In the example ofFIG. 8, the graphic elements include controls38which may be actuated by the user, by means of the interface system14, notably for controlling or tracking an airplane system.

In particular, the control is an instruction for opening or closing pumps, actuators, mechanical, electrical and/or hydraulic circuits.

With reference toFIG. 1, the interface system14comprises at least one rotary member50for controlling a target on the display device12, sensors52,54respectively for angular displacement and for torque applied on the rotary member50, and a torque generator56, advantageously formed by the torque sensor54.

By «controlling a target», is notably meant that the rotary member is able to displace a target or «focus» within different fields of a tree structure of a graphic interface, or causing a change in the numerical or logical value of a particular field targeted by the target, in particular when the field is an input field.

The interface system14further includes a target management assembly58on the display device12, controlled by the rotary member50, and a haptic feedback generator60on the rotary member50during its rotation, able to generate distinct haptic profiles on the rotary button depending on distinct system states and/or distinct man-machine interface states of the aircraft, for controlling the torque generator56.

The man-machine interface states notably comprise graphic interface states and input interface states.

In this example, the interface system14further advantageously comprises at least one man-machine interface22distinct from the rotary member50.

The rotary member50is here formed by a rotary button or « rotator switch» around a unique axis A-A′. The angular displacement sensor52is able to determine at each instant the angular position of the rotary member50around the axis A-A′.

The torque sensor54is able to determine, at each instant, the torque applied on the rotary member50during its rotation around the axis A-A′.

The target management assembly58preferably comprises a processor64and a memory66containing software applications able to be executed by the processor.

The memory66notably contains a target management application68, an application70for generating and displacing a target73on a window32of a display area30and a context management application72, able to determine at least one present system and/or man-machine interface state of the aircraft, relevant towards the position of the target on the window32.

The target management application68is able to receive the signals from the angular positioning sensor52for determining the position of a target73on the window32, and the possible blocking of the target73on a field of menus, for inputting set values or for controlling the window32, for the actuation of this field.

The generation and displacement application70for the target is able to receive the data from the target management application68and of generating the display of a target73at the position determined by means of the target management application68depending on the rotation of the rotary member50and on the possible blocking of the target73in a field.

The generation and displacement application70is able to transmit the target display data to the display management assembly31.

The target73is for example materialized by a cursor as inFIG. 1, or by a particular display of a field, notably highlighting, like inFIG. 2 or 3.

The context management application72is able to receive the pieces of information of the position of the target73and of collecting the system state or man-machine interface state which are relevant towards this position, notably by interacting with the avionic unit13.

The context management application72is able to transmit the system state and/or man-machine interface state data to the torque generator60.

For example, when the target73moves in the lists of fields of menus, as illustrated inFIG. 2, the context management application72is able to determine the nature of the list in which moves the target73, the number of fields of this list, and the particular fields of the list of fields giving the possibility of accessing other lists, or to other menus or to obtain man-machine interface state data, here corresponding relevant graphic interface state data.

When the target73is positioned in an input field, as illustrated inFIG. 5, the context management application72is able to determine the type of input field on which the target is positioned, and to obtain relevant system and/or man-machine interface state data relative to this input field.

The relevant data are for example data received from the rotary member50, such as a speed of rotation of the sensor. Alternatively or additionally, the relevant data are the input mode and/or the unit, into which the set value has to be inputted, the flight phase in which is found the aircraft, the targeted set value, and/or the preferential domain of the input values.

When the target is positioned on a control, as illustrated inFIG. 8, the context management application72is able to determine the type of control targeted by the target, and to obtain relevant data of the system and/or man-machine interface state relative to this control.

The relevant data of a system state are for example a normal operating state of the airplane system affected by the control and/or of the aircraft, or on the contrary a degraded operating state of the airplane system affected by the control and/or of the aircraft.

The torque generator60includes a processor80and a memory82containing software applications able to be executed by the processor80.

The memory thus contains an application84for generating distinct haptic profiles92,94, according to the system and/or man-machine interface state received, and an application86for transmitting the haptic profile generated by the application84to the torque generator56of the rotary member50.

Each haptic profile92,94generated by the application84includes at least one notch90, preferably a plurality of successive notches90visible inFIGS. 4, 6, 7, and 9 to 12. Each haptic profile92,94advantageously comprises walls91of an intensity greater than that of the notches90for materializing the limits of an adequate rotation range of the rotary member50.

The distinct haptic profiles92,94for example have a number of different notches90, and/or at least two notches90with different lengths, intensity and shape for materializing different system and/or graphic interface states.

For example, as illustrated byFIG. 4, a first profile92has a number of notches90distinct from a second profile94, for example three notches of small intensity and a notch of stronger intensity for the first profile92and two notches of small intensity and a wall91for the second profile94.

This materializes the number of fields of menus available in a list of fields110,112, the notch90with the strongest intensity materializing a field for passing to another list of fields.

In the example illustrated byFIG. 6, a first profile92has notches with a greater length and a smaller maximum intensity than the notches of a second profile94, for materializing a different speed of rotation of the rotary member50.

In the example illustrated byFIG. 7, the notches90of a first haptic profile92have a notch shape, different from the notches90of a second haptic profile94which have a triangular shape, for materializing a different input mode of parameters, or a different input scale.

In the example illustrated inFIGS. 9 and 10, a first haptic profile92has a notch90with an intensity greater than that of the notch90of a second haptic profile94, for materializing a difference in the operating state of an airplane system onto which a control has to be applied.

In the example illustrated inFIGS. 11 and 12, a first profile92has a first series of notches90and a second series of notches90surrounding a single recess98, for materializing a specific target value intended to be inputted. A second haptic profile94includes two series of notches with greater intensity than an intermediate series materializing a range of preferred target values.

The distinct haptic profiles92,94are generated by the generation application84depending on the system and/or graphic interface state data transmitted by the context management application72.

The distinct haptic profiles92,94are for example generated according to the display present on the display area30, for example menus or fields available on the display area30. They may be generated according to the type of action on the rotary member, for example on the speed of rotation of this rotary member50.

Alternatively, the different haptic profiles are able to be generated according to the type of input, for example on the input mode and on the unit selected for the input.

Still alternatively, the different haptic profiles are generated according to the relevant flight phase, for example a rolling, take-off, cruising, or landing phase or further depending on operating states of the airplane systems, or on the aircraft, for example a normal operating state or a degraded operating state during a failure.

The transmission application86is able to express the haptic profile generated by the generation application84as an electric control signal of the torque generator56for applying the haptic profile to the rotary member50during its rotation, depending on the system and/or graphic interface state data.

The torque generator is able to generate a torque corresponding to the given haptic profile, during the rotation of the rotary member50by the user. This profile is expressed by variable travel and force to be produced by the user for overcoming the generated torque.

Examples of interaction methods between a user and a display device of an aircraft, applied by means of the system14will now be described.

In a first example, illustrated byFIGS. 2 to 4, the user actuates the rotary member50for navigating in the successive lists110,112of fields.

Certain particular fields114of the list, here the last field of the list materialize an end of a list, a bottom of a page, a change of list and of windows.

During the actuation of the rotary member50, the target management application68determines the position of the target73on the window32, and transmits it to the application for generating and displacing the target70in order to generate the display of the target73on the window32. In this example, the display of the target73is materialized by highlighting of the field selected by the user.

The context management application72determines in which list110,112of fields is found the target73and provides graphic interface state data comprising the number of fields in the list, and the position of the particular fields114of the list to the application84for generating haptic profiles.

The application84for generating haptic profiles then generates a first haptic profile92comprising a number of notches90corresponding to the number of fields of the list110, the intensity of the notch corresponding to a particular field114being greater than the intensity of the other notches.

The generated haptic profile92is transmitted to the torque generator56by the application for transmitting a profile86.

At each passage between two fields, the torque generator56generates a torque corresponding to the defined notch90in the haptic profile92.

When the user switches onto the second list112, the context management application72detects the change in the graphic interface state and transmits the graphic interface state data comprising the number of fields in the second list112and the position of the particular fields114of the list to the application84for generating a haptic profile.

The application84for generating a haptic profile then generates a second haptic profile94distinct from the first haptic profile92, by the number of small intensity notches.

The user easily perceives, depending on the haptic profile felt during the rotation, what is the number of fields available in the list110,112, and what are the particular fields114, since the latter has to overcome a greater force in order to pass the notch generated by the haptic profile.

This improves the target displacements in the graphic interface, and facilitates the task of the crew.

In a second example illustrated byFIG. 5and byFIG. 6, the user places the target on an input field36of a flight parameter, and modifies the set value associated with this flight parameter by rotating the rotary member50.

Depending on the speed of rotation of the rotary member50, rapid increments or slow increments of the set value are applied. For example, in the case of the adjustment of a set altitude, the slow increments are 100 feet, and the rapid increments are 1,000 feet.

The context management application72receives speed of rotation data of the rotary member50and provides man-machine interface state data, here input interface state data to the application for generating a haptic profile84, depending on the speed of rotation of the rotary member50.

In a first range of speeds of rotation of the rotary member50, greater than a predetermined speed of rotation, the speed of rotation is considered as high, while in a second range of speeds of rotation, less than a predetermined speed of rotation, the speed of rotation is considered as slow.

When the speed of rotation is high, the context management application72transmits a man-machine interface state datum formed by an indication of a high speed of rotation to the application for generating a haptic profile84.

A first haptic profile92, consisting of small intensity notches90and with relatively large extents is then generated and is transmitted to the torque generator56by the application86.

When the speed of rotation is low, the context management application72transmits a man-machine interface state datum formed by an indication of a low speed of rotation to the application for generating a haptic profile84.

A second haptic profile92comprising notches with a stronger maximum intensity, but with smaller lengths, are then generated.

Moreover, the context management application72defines recommended minimum and maximum limits of the flight parameter and transmits these limits to the generation application84for materializing the limits by walls91in the haptic profile92,94.

Thus, the user may very simply determine at which speed the set value of the flight parameter is modified, and with which increment. This limits the risk of error and facilitates input.

A third example of application of the method is illustrated byFIG. 7. In this example, the user adjusts the same flight parameter, i.e. the speed. The user has two input modes for proceeding with the adjustment, for example a real speed (IAS) indicated in knots or as a Mach number.

The context management application72transmits to the application for generating a haptic profile84a man-machine interface state datum including an indication of the type of input mode and/or of scale selected for the parameter.

When the indication corresponds to a first type of scale, for example a real speed indicated in knots, the generation application84generates a first haptic profile90for example consisting of notch-shaped notches90.

When the indication of the type of scale corresponds to a second type of scale, for example to a Mach number, the generation application84generates a second haptic profile92, for example consisting of saw-tooth notches90.

The transmission application86then transmits the haptic profile to the torque generator56.

Then the user very easily perceives which is the type of selected scale, which limits the risk of an input error.

Alternatively, the flight parameter is an altitude, and the scales are given in feet or in flight levels. Still alternatively, the fight parameter is a speed of descent, and the scales are given as a slope or as a vertical speed.

Still alternatively, the type of scale for the input depends on the flight phase in which the aircraft is found. In this case, the context management application72transmits to the application for generating a haptic profile84system state data thus including data for identifying the flight phase, and the haptic profile92,94is selected according to the flight phase.

In the fourth example, illustrated inFIG. 10, the user actuates a control38of an airplane system. In a normal state of the airplane system, or more generally of the aircraft, the control should not generally be activated, while in a failure procedure, corresponding to a degraded state of the airplane system or of the aircraft, the control may be executed or should be executed.

The context management application72is able to identify the operational state of the airplane system or of the aircraft, and to produce a system state datum corresponding to an indicator of the need for securing the interaction.

When the airplane system or the aircraft is in a normal operational state, the generation application84generates a first haptic profile92having a notch90with strong intensity, in order to dissuade the user from executing the command.

On the contrary, when the airplane system or the aircraft is in a degraded operating operational state, the generation application84generates a second haptic profile94having a notch90of small intensity suggesting to the user that he/she may carry out the command, or even that he/she should carry out the command.

FIGS. 11 and 12illustrate two distinct haptic profiles92,94which may be generated according to the type of inputted fight parameter type on two distinct input fields.

In the profile ofFIG. 11, the fight parameter should be adjusted accurately to a set value. The first haptic profile92includes two series of notches90surrounding a recess98materializing the set value.

On the contrary, in the profile ofFIG. 12, the fight parameter should be adjusted within a preferential range. The second haptic profile94thus includes a series of notches90with strong intensity surrounding a series of notches90of small intensity, materializing the preferential range.