FR3132897A1 - Method and device for controlling a man-machine interface for controlling a vehicle driving assistance system - Google Patents

Abstract

The present invention relates to a method and a device for controlling a man-machine interface, called an HMI, for controlling a driving assistance system, called the ADAS system, of a vehicle (10). For this purpose, first data representative of a first activation of the ADAS system are received. Second data representative of the MMI are returned to a user of the ADAS system, the rendering of the second data being obtained from a set of control parameters of the MMI. Third data representative of at least one user action relating to rendering is received. The set of HMI control parameters is modified based on the third data. Figure for abstract: Figure 1

Description

Method and device for controlling a man-machine interface for controlling a vehicle driving assistance system

The present invention relates to methods and devices for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle, for example a motor vehicle. The present invention also relates to a method and a device for determining control parameters of a vehicle HMI. The present invention also relates to a method and a device for customizing an HMI to assist in controlling an ADAS system of a vehicle.

Technology background

Many contemporary vehicles are equipped with functions or system(s) or driving assistance, known as ADAS (from English “Advanced Driver-Assistance System” or in French “Advanced Driving Assistance System”).

To facilitate the control of these ADAS systems and to support the driver of the vehicle in the use of these ADAS systems, it is known to use a man-machine interface, called HMI, which makes it possible to present information to the driver, in the form of graphic, sound, vocal and/or vibration content for example.

The content associated with the HMI rendered to the driver when activating an ADAS system to guide the latter in the execution of operations allowing control of the ADAS system is today the same from one vehicle to another. other, regardless of the user profile of the ADAS system. Thus, a user experienced and comfortable in controlling the ADAS system will receive the same information from the HMI as a less accustomed user and less experienced in controlling the ADAS system.

Beyond the lack of user-friendliness associated with the use of the HMI for controlling the ADAS system, a generic and identical HMI regardless of the user profile, safety problems for the vehicle and its passengers may arise. . Indeed, information deemed essential by an experienced user can find itself buried among the set of information rendered by the HMI for less experienced users. Conversely, content that is too succinct and suitable only for experienced users may prove incomplete for inexperienced users, leading to risks of misuse of the ADAS system.

Summary of the present invention

An object of the present invention is to solve at least one of the problems of the technological background described above.

Another object of the present invention is to improve the control of one or more ADAS systems fitted to a vehicle and/or to improve the safety of the vehicle and its passengers.

According to a first aspect, the present invention relates to a method for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle, the method comprising the following steps :

- reception of first data representative of a first activation of the ADAS system;

- rendering of second data representative of the HMI intended for a user of the ADAS system for controlling the ADAS system, the rendering of the second data being obtained from a set of control parameters of the HMI;

- reception of third data representative of at least one user action relating to the rendering;

- modification of the set of HMI control parameters based on the third data.

Taking into account user actions associated with requests made via the HMI and/or information provided via the HMI makes it possible to adjust the control parameters of the HMI, and ultimately the HMI and the contents. associated messages made to the user, based on a user profile (determined through their actions).

According to one variant, the method further comprises the following steps:

- reception of fourth data representative of a second activation of the ADAS system subsequent to the first activation;

- rendering of fifth data representative of the HMI as a function of the set of modified control parameters, the fifth data being different from the second data.

According to another variation:

- the fifth data correspond to only part of the second data; Or

- the fifth data comprises the second data and a set of data additional to the second data.

According to an additional variant, the third data belongs to a set of data comprising:

- data representative of a number of responses and/or absences of response to a request made via the HMI;

- data representing a duration between the rendering of a request and a response to the request via the HMI;

- data representative of a number of compliances and/or non-compliances with an instruction provided by the HMI.

According to yet another variant, the HMI includes:

- graphic content; and or

- sound or vocal content; and or

- vibrational content.

According to an additional variant, the ADAS system belongs to a set of ADAS systems comprising:

- a semi-automatic lane change system;

- an automatic parking assistance system.

According to another variant, the method further comprises a step of identifying the user, the set of modified control parameters being associated with a user identifier.

According to a second aspect, the present invention relates to a device for controlling a man-machine interface for controlling a vehicle driving assistance system, the device comprising a memory associated with a processor configured for updating implementing the steps of the method according to the first aspect of the present invention.

According to a third aspect, the present invention relates to a vehicle, for example of the automobile type, comprising a device as described above according to the second aspect of the present invention.

According to a fourth aspect, the present invention relates to a computer program which comprises instructions adapted for the execution of the steps of the method according to the first aspect of the present invention, in particular when the computer program is executed by at least one processor.

Such a computer program can use any programming language, and be in the form of a source code, an object code, or an intermediate code between a source code and an object code, such as in partially compiled form, or in any other desirable form.

According to a fifth aspect, the present invention relates to a computer-readable recording medium on which is recorded a computer program comprising instructions for executing the steps of the method according to the first aspect of the present invention.

On the one hand, the recording medium can be any entity or device capable of storing the program. For example, the medium may comprise a storage means, such as a ROM memory, a CD-ROM or a ROM memory of the microelectronic circuit type, or even a magnetic recording means or a hard disk.

On the other hand, this recording medium can also be a transmissible medium such as an electrical or optical signal, such a signal being able to be conveyed via an electrical or optical cable, by conventional or terrestrial radio or by self-directed laser beam or by other ways. The computer program according to the present invention can in particular be downloaded onto an Internet type network.

Alternatively, the recording medium may be an integrated circuit in which the computer program is incorporated, the integrated circuit being adapted to execute or to be used in executing the method in question.

Brief description of the figures

Other characteristics and advantages of the present invention will emerge from the description of the particular and non-limiting examples of embodiment of the present invention below, with reference to the attached Figures 1 to 3, in which:

schematically illustrates a passenger compartment of a vehicle, according to a particular and non-limiting embodiment of the present invention;

schematically illustrates a device configured to control a man-machine interface for controlling a driving assistance system of the vehicle of the , according to a particular and non-limiting embodiment of the present invention;

illustrates a flowchart of the different stages of a method of controlling a man-machine interface for controlling a driving assistance system of the vehicle of the , according to a particular and non-limiting embodiment of the present invention.

Description of the implementation examples

A method and a device for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle will now be described in what follows in reference jointly with Figures 1 to 3. The same elements are identified with the same reference signs throughout the description which follows.

According to a particular and non-limiting example of embodiment of the present invention, a method for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system (for example semi-automatic lane change and/or an automatic parking assistance system), of a vehicle comprises the reception of first data representative of a first activation of the ADAS system. These first data are for example received by the device in charge of controlling the HMI, the activation of the ADAS system being for example obtained via the HMI (for example by pressing a virtual button displayed on a touch screen in the vehicle or by actuation of a physical control unit). Upon receipt of this first data, the HMI control device initiates or triggers the rendering of second data representative of the HMI to a user of the ADAS system for controlling the ADAS system. The second data corresponds for example to graphic and/or sound content data. The rendering of the second data is advantageously obtained from a set of HMI control parameters, for example stored in the memory of the HMI control device. Following or during rendering of the second data, third data representative of at least one user action is received. A user action corresponds for example to a response to a request made via the HMI, to a response time between the request and the response given, to the taking into account or absence of taking into account an instruction given via the HMI. Finally, the set of HMI control parameters is modified based on the third data. The set of modified control parameters is then used for controlling the HMI during a next activation of the ADAS system.

Taking into account user actions associated with requests made via the HMI and/or information provided via the HMI makes it possible to adjust the control parameters of the HMI, and ultimately the HMI and the contents. associated messages made to the user, based on a user profile (determined through their actions).

This makes it possible to adjust the behavior of the HMI to the user profile.

There schematically illustrates a part of a passenger compartment of a vehicle 10, according to a particular and non-limiting embodiment of the present invention.

There presents a view of the interior of a vehicle 10, in particular of the front part of the passenger compartment of the vehicle 10 including in particular the steering wheel and the dashboard of the vehicle 10.

The vehicle 10 corresponds for example to a vehicle with a thermal engine, with an electric motor(s) or even a hybrid vehicle with a thermal engine and one or more electric motors. The vehicle 1 thus corresponds for example to a land vehicle, for example an automobile, a truck, a coach, a motorcycle. The vehicle 10 corresponds to an autonomous or semi-autonomous vehicle, that is to say under the total or partial supervision of one or more ADAS systems embedded in the vehicle 10.

According to the example of the , a display screen 100 is integrated into the dashboard of the vehicle 10. The display screen 100 corresponds for example to an LCD type screen (from the English “Liquid Crystal Display” or in French “Affichage à liquid crystals"), for example of the TFT type (from the English "Thin-Film Transistor" or in French "Thin Film Transistor"), or OLED (from the English "Organic Light-Emitting Diode" or in French “Organic light-emitting diode”). The display screen 100 is for example arranged in the center of the dashboard, for example above a central facade. Of course, the position of the display screen 100 is not limited to this example, the display screen 100 can be arranged in any position, for example on the central facade.

According to a variant embodiment, the display screen 100 is a touch screen allowing a user to interact with the graphic content displayed on this screen 100 in a tactile manner, for example by clicking via touch on icons to open new pages of the displayed graphical interface, navigate menus by swiping the screen from top to bottom, enlarge or reduce a window by moving two fingers apart or together, etc.

According to a variant, the vehicle 10 further comprises one or more speakers (not illustrated in the ) each configured for rendering sounds and/or voice instructions. The vehicle 10, for example, further comprises one or more microphones configured to pick up voice commands spoken by the driver and/or a passenger in the passenger compartment of the vehicle 10.

According to another variant, the vehicle 10 is equipped with haptic actuators such as vibratory actuators. Such actuators are for example arranged in the steering wheel, in the driver's and/or front passenger's seat. Such actuators are configured to provide haptic feedback to the driver and/or passenger other than the graphic content displayed on the screen 100 and/or the sound or vocal content rendered through the speaker(s).

The screen 100 and/or the speaker(s) and/or the haptic actuator(s) are advantageously configured and used for rendering content(s) of a human-machine interface (HMI) for the restitution of information intended for the driver and/or passengers of the vehicle 10.

An HMI corresponds for example to an interactive system comprising one or more computers/processors on board the vehicle 10 connected in communication via one or more data buses to one or more rendering means such as the screen 100, one or more loudspeakers. speakers and/or one or more haptic actuators.

The computer(s) (or processors) are configured to render content (graphics, sound, voice, vibration or other) according to control parameters which make it possible to determine which content must be rendered, in what order. Such control parameters are for example stored in one or more memories accessible by the processor(s) responsible for generating the content to be rendered.

The contents of the HMI to be rendered depend for example on the ADAS system(s) activated, on the driver's actions (with respect to requests sent via the HMI and/or instructions or instructions provided to the driver via the 'HMI).

An action of the driver of the vehicle 10 or of a user of an ADAS system of the vehicle 10 within the meaning of the present invention includes any operation carried out by the driver via a control member of the vehicle 10, any instruction provided via a control member or a means of interaction (for example a touch command provided via the screen 100 when the latter is touch and/or a voice command spoken by the driver, captured by a microphone then interpreted and understood by the processor(s) in charge of the HMI), any response or lack of response to a request or an instruction issued via the HMI, any consideration or failure to take into account an instruction issued via the HMI.

A lack of response and/or a lack of consideration are for example determined by the processor(s) in charge of the HMI by measuring the time elapsed between the time instant associated with the rendering of the request or the instruction and the time instant associated with a response or action of the driver associated with the request or instruction. When the time (duration) elapsed since the time instant associated with the rendering of the request or instruction is greater than a threshold (for example 500 ms, 1 s, 2 s), then the processor(s) interpret this information of duration as corresponding to a lack of response or consideration from the driver.

The computer code of the on-board software(s) comprising the instructions to be loaded and executed as part of the implementation of the HMI is for example executed by one or more computers of the vehicle 10, this set of computers comprising for example the IVI computer (from English “In-Vehicle Infotainment” or in French “Infodivertissement onboard”), which is connected to the other computers of the on-board system of the vehicle 10 via one or more data buses, the IVI computer controlling the infotainment system of the vehicle 10 and the data to be displayed on the display screen 100. These computers advantageously form a multiplexed architecture for the production of different services useful for the proper functioning of the vehicle. The computers communicate and exchange data with each other via one or more computer buses, for example a CAN data bus type communication bus (from the English “Controller Area Network” or in French “Réseau de controllers”). "), CAN FD (from the English "Controller Area Network Flexible Data-Rate" or in French "Réseau de controllers à rate flexible data-Rate"), FlexRay (according to the ISO 17458 standard) or Ethernet (according to the ISO/ IEC 802-3).

An example of architecture of such a calculator is illustrated by the , described in more detail below

A process for controlling a man-machine interface, called HMI, for controlling one or more driving assistance systems, called ADAS system, of a vehicle, for example of vehicle 10, is advantageously implemented by one or more computers (for example by one or more processors of this or these computers in relation to a memory) of the on-board system of the vehicle 10.

The ADAS system(s) correspond for example to:

- a semi-automatic lane change system, called SALC system (from English “Semi-Automatic Lane Change”); and or

- an automatic parking assistance system (or “Park Assist” in English).

In the following description of the process, reference will be made to a single ADAS system for reasons of clarity, without however being limited to this particular example of implementation, the process applying to the implementation of several systems ADAS.

In a first operation, first data representative of a first activation of the ADAS system are received.

The activation of the ADAS system by the driver of the vehicle 10 (or any other user of the vehicle 10) is for example obtained by the actuation of a control member such as a physical button arranged in the dashboard, a lever control (for example near the steering wheel), by tactile pressing on a virtual button of graphic content of the HMI displayed on the screen 100, by uttering a specific voice command, etc.

The first data is received by the computer in charge of the process from the computer in charge of the control unit used by the driver to activate the ADAS system via a data bus connecting these computers.

According to an optional embodiment, activation of the ADAS system is preceded or accompanied by identification of the driver, the personalization of the HMI being, according to this variant, associated with the identified driver. Identification is obtained by any means, for example via the entry of an identification code by the driver, via a biometric fingerprint measured by an ad-hoc sensor, etc.

In a second operation, second data representative of the HMI are rendered, for example generated by the computer(s), these second data being generated for a user of the ADAS system for controlling the ADAS system. The rendering of the second data being obtained from a set of HMI control parameters.

The nature of the second data depends on the type of content represented by this second data. The second data is representative of graphic objects (for example images, graphic objects, icons, graphic virtual buttons) when the content corresponds to graphic content; and/or the second data is representative of voice messages or sounds when the content corresponds to sound or voice content; and/or the second data is representative of haptic effects (e.g. vibrations) when the content corresponds to haptic content (e.g. vibration).

The HMI corresponds to a purely graphic HMI, or according to a variant, to a HMI combining graphic content and vocal/sound content, or according to another variant to a HMI combining graphic content and vocal/sound content and/or additional haptic effects.

The content generated during rendering corresponds to a specific sequence of content, for example a sequence of graphic windows or images (comprising several graphic objects of which at least part is associated with information intended for the user) and/or sound or vocal content.

These contents are then transmitted to the devices responsible for their rendering (for example the display for graphic content on the screen 100 and the sound rendering of the sound/vocal content via the speaker(s)) so that the user can take knowledge of associated information.

For example, when the activated ADAS system corresponds to the SALC system, a first image is displayed on the screen 100 to confirm the activation of the SALC system with for example information such as the current speed, the number of traffic lanes. When activating the indicators on one side of the vehicle, an audible warning is issued via the HMI to indicate to the driver that the semi-automatic lane change maneuver is possible and taken into account. A request asking to confirm the implementation of the change via the SALC system is then rendered, for example displayed in the form of graphic content corresponding to a message requesting to validate or acknowledge the lane change by pressing an “OK” button. » (for example a physical button on the steering wheel or a virtual button displayed via the HMI on the screen 100). Finally, a new image is rendered and displayed on screen 100 to indicate that the lane change maneuver is in progress.

According to another example, when the activated ADAS system corresponds to the automatic parking system, a first image is displayed on the screen 100 to confirm the activation of the automatic parking system with for example a maximum speed value not to be exceeded for authorize automatic parking. A series of images are then displayed, for example, to guide the user through the different actions or operations to validate/perform sequentially so that the vehicle parks automatically.

The set of control parameters includes for example one or more of the following parameters, in any possible combination, the list being non-exhaustive:

- parameters representative of the content to be rendered depending on the activated ADAS system; and or

- parameters representative of the sequence of contents to be rendered; and or

- parameters representative of the number of contents to be rendered; and or

- parameters representative of the information to be provided at each stage of the user guidance process in controlling the activated ADAS system; and or

- parameters representative of requests to be rendered; and or

- parameters representative of threshold value of delays for waiting for a response to a request; and or

- parameters representative of instructions.

In a third operation, third data representative of at least one user action relating to rendering are received, for example from the computer(s) detecting this(s) user actions.

The third data corresponds for example to:

- data representative of a number of responses and/or absences of response to a request made via the HMI; and or

- data representing a duration between the rendering of a request and a response to the request via the HMI; and or

- data representing a number of compliances and/or non-compliances with an instruction provided by the HMI

For example, concerning the SALC system, the duration between the request for validation or acknowledgment of lane change activation and pressing the OK button is determined.

According to another example, the duration between the proposal of a lane change by the SALC system and the activation of the indicators by the user is determined.

According to yet another example, the number of presses on the Ok button following a set of audible warnings given by the HMI is recorded.

The actions performed represent the user's performance in controlling the activated ADAS system and thus represent their profile among a set of profiles such as beginner, intermediate or expert for example.

The user profile is for example determined by implementing a machine learning method, for example by a neural network, such a method comprising a learning phase prior to the production phase. Such a method thus includes the classification of data representative of the actions measured or recorded to determine the user profile.

According to one variant, the different metrics associated with the actions measured, recorded or determined are compared to threshold values or charts to determine the user profile.

The set of modified control parameters is for example associated with a user identifier, and stored in a vehicle memory. This is for example interesting when several users use the same vehicle. When a user takes control of the vehicle 10, this user identifies himself and the system retrieves the control parameters from the HMI corresponding to the user thus identified.

In a fourth operation, the set of control parameters of the HMI is modified or adjusted according to the third data, that is to say according to the user profile, to adapt the contents rendered via the HMI to the user profile when the ADAS system is activated again.

The modification of the control parameters corresponds for example to an iterative process according to which the adjustment of the parameters of the fourth operation is carried out progressively as the ADAS system is activated and the control process of the HMI.

According to a variant, the first, second and third operations are executed a determined number of times before implementing the fourth operation, to adjust the control parameters of the HMI with a sufficiently large sample of third data representative of the profile of the user.

In a fifth operation, fourth data (corresponding for example to the first data) representative of a second activation of the ADAS system subsequent to the first activation are received. This second activation corresponds to a new activation of the ADAS system after the set of parameters has been modified.

In a sixth operation, fifth data representative of the HMI are rendered as a function of the set of control parameters modified in the fourth operation, the fifth data being different from the second data.

According to a first example, the fifth data corresponds to only part of the second data, that is to say that the fifth data forms a subset of the second data.

Such an example corresponds for example to the scenario in which the user profile corresponds to the intermediate or experienced profile. For such a profile, it is not useful to render too much content via the HMI to the user to guide them in controlling the ADAS system. According to such an example, only part of the contents of the GUI are rendered. For example, concerning the SALC system, when it is observed that the user activates the indicators each time (or according to a percentage greater than a threshold, for example in 90 or 95% of cases) that an audible warning is given (for example within a time less than a threshold after the audible warning), then the audible warning is suppressed. According to another example concerning the SALC system, when it is observed that the user acknowledges the request to activate the lane change within a time period less than a threshold by pressing the OK button, the rendering and therefore the display of the request are deleted.

According to a second example, the fifth data comprises the second data and a set of data additional to the second data, that is to say that the fifth data comprises the second data and other additional data.

Such an example corresponds for example to the scenario in which the user profile corresponds to the beginner or even novice profile. For such a profile, the user needs more precise guidance, with more intermediate steps, for controlling the activated SALC system. According to this example, additional content of the HMI is rendered in addition to the default content, with for example additional sub-steps, additional information on the action to be executed, additional instructions and/or additional requests that the The user must validate to move on to the next step of controlling the ADAS system.

With such a process, the content of the HMI automatically adapts to the needs of the user, based on their reactions to the rendered content.

Over time, the contents of the HMI adapt to the evolution, for example to improvements, of the user in his mastery of the control of the activated SALC system.

This helps make HMIs more user-friendly and attractive to users, with greater acceptance and less interaction with the HMI when a user has a good grasp of controlling the SALC system, allowing the user to keep your hands on the wheel and stay focused on the road.

There schematically illustrates a device 2 configured for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle, for example of vehicle 10, according to a particular and non-limiting example of embodiment of the present invention. The device 2 corresponds for example to a device on board the vehicle 10, for example a computer.

The device 2 is for example configured for the implementation of the operations described with regard to the and/or steps of the process described with regard to the . Examples of such a device 2 include, without being limited to, on-board electronic equipment such as an on-board computer of a vehicle, an electronic computer such as an ECU (“Electronic Control Unit”), a telephone smart phone, tablet, laptop. The elements of device 2, individually or in combination, can be integrated into a single integrated circuit, into several integrated circuits, and/or into discrete components. Device 2 can be produced in the form of electronic circuits or software (or computer) modules or even a combination of electronic circuits and software modules.

The device 2 comprises one (or more) processor(s) 20 configured to execute instructions for carrying out the steps of the method and/or for executing the instructions of the software(s) embedded in the device 2. The processor 20 may include integrated memory, an input/output interface, and various circuits known to those skilled in the art. The device 2 further comprises at least one memory 21 corresponding for example to a volatile and/or non-volatile memory and/or comprises a memory storage device which may comprise volatile and/or non-volatile memory, such as EEPROM, ROM , PROM, RAM, DRAM, SRAM, flash, magnetic or optical disk.

The computer code of the embedded software(s) comprising the instructions to be loaded and executed by the processor is for example stored on memory 21.

According to different particular and non-limiting examples of embodiment, the device 2 is coupled in communication with other similar devices or systems and/or with communication devices, for example a TCU (from the English “Telematic Control Unit” or in French “Telematic Control Unit”), for example via a communications bus or through dedicated input/output ports.

According to a particular and non-limiting example of embodiment, the device 2 comprises a block 22 of interface elements for communicating with external devices, for example a remote server or the “cloud”, other nodes of the ad hoc network.

According to another particular and non-limiting example of embodiment, the device 2 comprises a communication interface 23 which makes it possible to establish communication with other devices (such as other computers of the on-board system) via a communication channel 230. The communication interface 23 corresponds for example to a transmitter configured to transmit and receive information and/or data via the communication channel 230. The communication interface 23 corresponds for example to a CAN type wired network (from the English “Controller Area Network” or in French “Réseau de controlleres”), CAN FD (from the English “Controller Area Network Flexible Data-Rate” or in French “Réseau de controllers à flow flexible data”), FlexRay ( standardized by the ISO 17458 standard) or Ethernet (standardized by the ISO/IEC 802-3 standard).

According to a particular and non-limiting embodiment, the device 2 can provide output signals to one or more external devices, such as a display screen 240, touch or not, one or more speakers 250 and/or other peripherals 260 (for example a haptic actuator) via output interfaces 24, 25 and 26 respectively. According to a variant, one or the other of the external devices is integrated into the device 2.

There illustrates a flowchart of the different stages of a process for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle, for example vehicle 10 , according to a particular and non-limiting embodiment of the present invention. The method is for example implemented by a device on board the vehicle 10 or by the device 2 of the .

In a first step 31, first data representative of a first activation of the ADAS system are received.

In a second step 32, second data representative of the HMI are rendered to a user of the ADAS system for controlling the ADAS system, the rendering of the second data being obtained from a set of control parameters of the HMI.

In a third step 33, third data representative of at least one user action relating to rendering are received.

In a fourth step 34, the set of HMI control parameters is modified according to the third data.

According to a variant, the variants and examples of the operations described in relation to the apply to the stages of the process of .

Of course, the present invention is not limited to the exemplary embodiments described above but extends to a method of rendering data representative of an HMI in a vehicle which would include secondary steps without thereby departing from the scope of the present invention. The same would apply to a device configured to implement such a process.

The present invention also relates to a vehicle, for example an automobile or more generally an autonomous vehicle with a land engine, comprising the device 2 of the .

Claims (10)

Method for controlling a man-machine interface, called HMI, for controlling a driving assistance system, called ADAS system, of a vehicle (10), said method comprising the following steps:
- reception (31) of first data representative of a first activation of said ADAS system;
- rendering (32) of second data representative of said HMI intended for a user of said ADAS system for controlling said ADAS system, the rendering of said second data being obtained from a set of control parameters of said HMI;
- reception (33) of third data representative of at least one action of said user relating to said rendering (32);
- modification (34) of said set of control parameters of said HMI as a function of said third data. A method according to claim 1, further comprising the following steps:
- reception of fourth data representative of a second activation of said ADAS system subsequent to said first activation;
- rendering of fifth data representative of said HMI as a function of said set of modified control parameters, said fifth data being different from said second data. Method according to claim 2, for which:
- said fifth data corresponds to only part of said second data; Or
- said fifth data comprises said second data and a set of data additional to said second data. Method according to one of claims 1 to 3, for which said third data belongs to a set of data comprising:
- data representative of a number of responses and/or absences of responses to a request made via said HMI;
- data representative of a duration between the rendering of a request and a response to said request via said HMI;
- data representative of a number of compliances and/or non-compliances with an instruction provided by said HMI. Method according to one of claims 1 to 4, for which said HMI comprises:
- graphic content; and or
- sound or vocal content; and or
- vibrational content. Method according to one of claims 1 to 5, for which said ADAS system belongs to a set of ADAS systems comprising:
- a semi-automatic lane change system;
- an automatic parking assistance system. Method according to one of claims 1 to 6, further comprising a step of identifying said user, said set of modified control parameters being associated with an identifier of said user. Computer program comprising instructions for implementing the method according to any one of the preceding claims, when these instructions are executed by a processor. Device (2) for controlling a man-machine interface for controlling a vehicle driving assistance system, said device (2) comprising a memory (21) associated with at least one processor (20) configured for the implementation of the steps of the method according to any one of claims 1 to 7. Vehicle (10) comprising the device (2) according to claim 9.