METHOD AND SYSTEM FOR RECORDING DATA IN A TEST VEHICLE

Abstract

The invention relates to a method for recording, in a data recorder, data relating to a vehicle under test, the method comprising a first recording process (PER1), referred to as basic, of periodic type, with a first periodicity, involving a first set of data, characterized in that the method provides for a second recording process (PER2) of event type, triggered by triggering conditions and involving a second set of data, the second set of data being more extensive than the first set of data, the triggering conditions comprising at least one or more automatic activation conditions, the volume of data of the second set of data being substantially times greater than the volume of data of the first set of data.

Description

Title of the invention: METHOD AND SYSTEM FOR RECORDING DATA IN A TEST VEHICLE

[0001] The invention relates to a method for recording data relating to a motor vehicle subjected to tests, in particular driving tests. The data is recorded in a data recorder on board the vehicle, and this recorder is configured to store the collected data in a memory space and transmit all or part of the collected data to a remote server. The invention also relates to a system configured to implement the proposed method for recording data relating to a motor vehicle subjected to tests.

[0002] The data in question are parameters and variables managed by all or part of the on-board computers of the vehicle, the parameters in question including, among other things, fault counter values.

[0003] We are interested here in test vehicles which are subjected to sustained driving sequences in order to cover fairly substantial mileages, e.g. at least 20,000 km or 30,000 km. These distances can be covered over relatively short periods in order to obtain information fairly quickly about the behavior of the vehicle and the possible occurrence of certain defects, and the monitoring of certain parameters of interest.

[0004] The driving sequences of interest can be carried out in a road configuration with a driver, on test tracks or open roads. However, it is not excluded that certain sequences are carried out on a roller bench with a driver robot at the driving position.

[0005] In order to make the most of the lessons provided by these driving sequences, it is planned to equip each test vehicle with a data recorder.

[0006] The data recorder acquires on a periodic basis parameters and variables captured or calculated by one or more on-board computers of the vehicle.

[0007] These collected data are stored in a memory space of the data recorder. As vehicles include increasingly complex systems, the volume of interesting data to be collected is constantly increasing. The number of data that are interesting to collect is several thousand. In addition, some of these data of interest are not spontaneously emitted by the vehicle's on-board computers.

[0008] However, it is not reasonable to collect all these data on a rapid periodic basis, as this would represent too large volumes of data. In other words, the number of parameters collected by the collection process pe- periodic cannot be increased substantially.

[0009] The inventors therefore sought to increase the coverage of the data collected without increasing the volume of data too much.

[0010] To this end, the present invention proposes a method for recording, in a data recorder, data relating to a vehicle under test, the method comprising a first recording process, called basic, of periodic type, with a first periodicity, involving a first data set, characterized in that the method provides a second recording process called event-driven, triggered by trigger conditions (and incidentally interrupted by stop conditions), involving a second data set, the second data set being larger than the first data set, the trigger conditions comprising at least one or more automatic trigger conditions, the data volume of the second data set being at least five times greater than the data volume of the first data set.

[0011] Thanks to the provisions promoted above, it is possible to obtain, from time to time, thanks to the collection of the second data set, a very wide range of data with a very wide coverage and a high precision and a consequent depth for in-depth analysis. Several thousand data are recorded, which allows an in-depth analysis, for example a posteriori, of the operation and possible malfunctions of the vehicle.

[0012] The second data set is acquired by polling, at least in part. Preferably, a single instance of each data item in the list of the second data set is acquired. When the collection has been carried out for all the data present in the list of the second data set, then the so-called 'stop conditions' are met and the second recording process is completed.

[0013] It is noted that the number of data in the second data set can be between 3000 and 5000.

[0014] Each data item can typically be represented as an integer, encoded in 1, 2 or 4 bytes. Some data items may be real numbers.

[0015] It should be noted that certain data included in the second data set requires the on-board computers to be interrogated by a polling mechanism, i.e. via an interrogation, whereas for the first data set, the data recorder simply reads data present in frames emitted spontaneously in a periodic broadcast mode (in the language of the trade, we say 'broadcasting' or 'Free running').

[0016] The data logger operates by successive measurement sequences.

[0017] It should be understood here that the “measurement sequence” corresponds to a vehicle driving sequence or a driving cycle from the engine start, then the rolling, until stopped by the vehicle driver (or the driving robot).

[0018] The first periodicity of the first recording process may be a few Hertz, for example 5 Hertz, i.e. a recording every 200 milliseconds. Of course, other periodicity values ​​are possible such as a lower frequency of 1 Hz or 2 Hz, without excluding a frequency higher than 5 Hz.

[0019] As will be seen later, the periodicity of the second recording process is much lower than that of the first recording process.

[0020] Advantageously, the data logger operates autonomously. Once programmed, there is no need for human intervention for the process promoted above to take place automatically.

[0021] The data is recorded in a non-volatile memory of the recorder, for example a hard disk, or a Flash EEprom memory area or equivalent.

[0022] According to a particular embodiment, the data volume of the second set is at least 8 times greater than the data volume of the first data set.

[0023] According to one embodiment, during a run of the second recording process, the first recording process is paused, and the first recording process is resumed when the run of the second recording process is completed, and the current mileage of the vehicle is recorded in a memory denoted KMLast at the time when the run of the second recording process ends.

[0024] As a result, the microprocessor of the recorder is fully dedicated to the second recording process, while the first recording process is paused. Thus, the size and power of the microprocessor of the recorder can remain conventional.

[0025] Furthermore, according to one option, the data collected in the second data set encompasses the data collected in the first set, and thus the parameters involved in the first set, or their equivalent, continue to be tracked during the course of the second recording process.

[0026] In addition, the time required to complete the collection of the entire second data set is minimal. However, a few seconds or tens of seconds may be required to scan the few thousand data by polling.

[0027] Note that the KMLast memory contains the mileage corresponding to the end of the second most recent recording process.

[0028] According to one embodiment, the method provides for counting a cumulative mileage noted KMC, traveled since the start of the measurement, the start of the measurement corresponding to the start of the vehicle driving sequence.

[0029] This avoids triggering the second recording process immediately after the start of the measurement sequence.

[0030] According to an optional embodiment, the current mileage of the vehicle, denoted KM, is iteratively recorded and the automatic activation conditions include at least one logical check as follows: KM - KMLast > N1K where N1K is a calibratable kilometer value, for example 500 or 1000.

[0031] We can thus have a very simple logic of kilometer periodicity.

[0032] According to one embodiment, the current mileage of the vehicle, denoted KM, is iteratively recorded and the automatic activation conditions include at least one logical check as follows: KM- KMLast > N1K, and KMC>SK1, where N1K and SKI are calibratable kilometer values.

[0033] As a result, the second recording process is triggered every N1K kilometers traveled. In addition, it is avoided to trigger the second recording process in the first SKI kilometers after the start of the measurement sequence.

[0034] For example, N1K can be chosen at a value of 1000, i.e. the second recording process is triggered every 1000 km. It should be noted that it is possible to choose any value for N1K, for example between 100 km and 2000 km, to have a second data set collected at a desired suitable kilometer frequency.

[0035] For example, SKI can be chosen at a height of 20, i.e. the second recording process is not triggered within the first 20 kilometers after the start of the measurement sequence. In practice, if the recurrence of the N1K kilometers falls at the start of the measurement sequence, the launch of the second recording process is slightly delayed.

[0036] According to one embodiment, the automatic activation conditions further comprise: - a temperature condition, consisting in that a current engine temperature value noted TMC, is such that TMC > STI - a vehicle speed condition, consisting of at least one vehicle speed value having exceeded a threshold noted SV1 since the start of the vehicle driving / measurement sequence, where STI and SV1 are calibratable values, respectively of temperature and speed.

[0037] These additional conditions make it possible to trigger the second recording process only if the rolling is already well established.

[0038] According to one embodiment, the method provides a step of remote transmission of the data collected, by the first process and the second process, to a server remote. This means that there is no need to physically connect the data logger to an Ethernet network or mass storage.

[0039] According to one embodiment, the step of remote transmission of the data is generated on a condition of cutting off the vehicle ignition.

[0040] Advantageously, there is at least daily data upload to the remote server and the data is available for analysis on a daily basis, by engineers or automatic analysis modules.

[0041] Preferably, all of the data collected during the measurement sequence that has just been carried out are unloaded. This then makes it possible to free up the memory space that was occupied by this data in the data recorder s.

[0042] According to one embodiment, the triggering conditions further comprise a manual activation condition, the manual activation condition including activation of the vehicle's headlights for 10 seconds or pressing a specific activation button.

[0043] The driver can thus occasionally add a triggering of the second recording process to obtain a second set of data, additional to the planned collection according to the mileage traveled. The driver can do this when he notices a particular problem or when a malfunction indicator light has come on.

[0044] The execution of this additional second data set recording may be further subject to an engine running condition and a zero vehicle speed condition.

[0045] The invention further relates to a recording system comprising a data logger, a user interface with a specific activation button and a light or text indication, characterized in that the data logger is configured to implement the method as described above.

[0046] According to one embodiment, the data recorder comprises remote transmission means, the system being characterized in that the data recorder is configured to implement the remote transmission of the data as described previously.

[0047] The invention will be further detailed by the description of non-limiting embodiments, and on the basis of the appended figures illustrating variants of the invention, in which: [Fig.l] is a schematic representation of the profile of a motor vehicle; [Fig.2] shows an example of a functional diagram of the system involved in the method implemented according to the present invention; [Fig.3] shows a timing diagram illustrating a sequence of operation of the data logger; [Fig.4] schematically illustrates data collected and stored in the data logger's memory.

[0048] In the various figures, the same references designate identical or similar elements.

[0049] In [Fig. 1], a vehicle 9 is shown schematically.

[0050] The vehicle in question 9 may be a passenger vehicle, a utility vehicle, a van, a recreational vehicle, etc.

[0051] The vehicle in question 9 comprises a powertrain 3. The powertrain may comprise an electric traction motor, and / or an internal combustion engine and / or a fuel cell powered by a hydrogen tank. Indeed, the vehicle 9 may be a 100% electric vehicle or a hybrid vehicle or even a conventional vehicle with a thermal engine. In the case where there is an electric powertrain, the vehicle 9 comprises a traction battery 2.

[0052] In the context of the present invention, the vehicle 9 is equipped with an ERLOG data recorder marked 1. The data recorder 1 can be installed in the rear trunk of the vehicle, however another location is not excluded.

[0053] As illustrated in [Fig.2], after its installation (known per se), the data recorder 1 is connected to one or more multiplexed buses 91,92 of the vehicle 9. The data recorder 1 is configured to read the messages circulating on these multiplexed buses 91,92 and generally to record a copy of the relevant data in a memory area 8. Generally, each vehicle is equipped with one or more CAN buses of the 500 kB or 1 MB type, without excluding other CAN buses at lower transmission speeds. The multiplexed buses can also include one or more LIN buses, one or more FlexRay buses, one or more Ethernet buses, without excluding other types of buses, proprietary or not.

[0054] The memory area 8 or memory space may be internal or external to the main board of the data logger.

[0055] The data collected are parameters and variables managed by all or part of the on-board computers 5 of the vehicle. The parameters in question are in particular, among others, fault counter values.

[0056] Some data of interest to be collected are present in messages / frames spontaneously emitted by one or more of the on-board computers 5 (in so-called 'free running' mode). Other data of interest to be collected require the use of an interrogation to be addressed to the computer which holds the information in question, this interrogation is also called 'polling' in the jargon of the trade. This involves a question-answer mechanism.

[0057] The data recorder 1 can use wired connections 11 to capture certain data or parameters prevailing in the vehicle, without being able to recover them. on a multiplexed bus.

[0058] It may further be provided that one of the controls 95 present in the vehicle is used to trigger a specific action relating to the 2nd recording process as will be seen later.

[0059] The data recorder 1 comprises a processing unit, otherwise called microprocessor 10. The data recorder may comprise a motherboard and one or more daughter cards as known per se and therefore not detailed here.

[0060] The system comprises an interface box, more precisely a user interface with a specific activation button 12 and a light or text indication 13. The light indication is for example a multi-colored light diode.

[0061] The data logger 1 comprises transmission means, for example means comprising a WiFi coupler 16 and an antenna 17. Alternatively or additionally, the transmission means may comprise a cellular network coupler.

[0062] The method promoted here comprises a first PERI recording process, called basic, of periodic type, with a first periodicity first The first recording process is configured to iteratively collect a first set of data generically identified by ER1, the successive captures being noted ERl(i), i being an index, each capture being identified by a timestamp and incidentally by the current mileage at the time of the capture. The first data set may comprise for example approximately 500 data.

[0063] The first periodicity of the first recording process may be a few Hertz, for example 5 Hertz, i.e. one recording every 200 milliseconds. Of course, other periodicity values ​​are possible.

[0064] Just to give an idea of ​​the order of magnitude, in the simple hypothesis where each data is a number on a byte, one minute of recording implies 5x500x60 = 150 kilobytes. That is 9 megabytes over one hour of driving.

[0065] Advantageously, the method promoted here comprises a second recording process identified by PER2.

[0066] The periodicity of this second recording process is much lower than that of the first recording process.

[0067] The second recording process is configured to collect, upon event, a second set of data generically identified by ER2, the successive captures being noted ER2(k), k being an index. Each capture is identified by the current mileage at the time of capture and incidentally a corresponding timestamp. The second set of data may comprise for example in a typical example 4000 data.

[0068] We can choose a very simple kilometer periodicity logic, for example a capture every 100 km.

[0069] Still to establish the orders of magnitude, if the vehicle travels at an average speed of 100 km / hour, we would have one capture per hour, which means in terms of data volume, still for the simplistic hypothesis of data on one byte each, 4 kilobytes per hour.

[0070] We can thus see that although the extent of the data in the second data set is much greater than that of the first data set (8 times more in the illustrated example), its weight in the memory is much less important (2000 times less). We will see later that the kilometer periodicity for the second recording process will even be several hundred kilometers, with an average occurrence of less than once a day.

[0071] The data recorder 1 operates by successive measurement sequences, each “measurement sequence” corresponding to a vehicle driving sequence or a driving cycle from the engine starting, then driving, until it is stopped by the vehicle driver (or the driving robot).

[0072] Once programmed, the data recorder 1 operates autonomously, without human intervention, automatically.

[0073] According to one embodiment, during a run of the second recording process ER2, the first recording process is paused, and the first recording process is resumed when the run of the second recording process is completed.

[0074] Under these conditions, all the computing power of the recorder's processor is dedicated to the polling mechanism, in order to make the time required to record the second data set as short as possible.

[0075] The current mileage of the vehicle is recorded in a memory denoted KMLast each time the second recording process ends. At the end of each second recording process, the new KMLast mileage value replaces the previous one.

[0076] The second PER2 recording process is triggered by trigger conditions. Automatic trigger conditions are provided which will be detailed below. There is also the option of triggering the second recording process on a voluntary action carried out by the driver of the vehicle ('manual' mode).

[0077] We count a cumulative mileage noted KMC, traveled since the start of the measurement which corresponds in practice to the start of the vehicle's driving sequence.

[0078] The current mileage of the vehicle, noted KM, is repeatedly recorded.

[0079] Automatic triggering

[0080] According to a particular embodiment, a logic of kilo periodicity can be adopted very simple metric, for example we trigger the second recording process every N1K kilometers.

[0081] According to an advantageous embodiment, the automatic activation conditions comprise at least one logical check as follows: KM - KMLast > N1K, and KMC > SKI.

[0082] The N1K and SKI parameters are calibratable kilometer values.

[0083] We can choose N1K = 1000.

[0084] We can choose SKI = 20.

[0085] The automatic activation conditions may further include a temperature condition and a vehicle speed condition.

[0086] The temperature condition consists in that a current engine temperature value noted TMC, is such that TMC > STI.

[0087] The vehicle speed condition consists of at least one vehicle speed value having exceeded a threshold noted SV 1 since the start of the vehicle driving / measurement sequence.

[0088] The parameters STI and SV1 are calibratable values. We can choose STI = 70 °C. We can choose SV 1 = 40 km / h.

[0089] The method provides a step of remote transmission 14 of the data collected by the first process and the second process, to a remote server 4.

[0090] The step of remote transmission of the data is generated on a condition of cutting off the ignition 36 of the vehicle.

[0091] Other remote transmission logics can nevertheless be retained.

[0092] Manual trigger

[0093] The manual trigger conditions are added to the automatic trigger conditions; they allow the recording of a second set of additional data to be added to a voluntary event.

[0094] The manual activation condition may be an activation of the vehicle headlights for 10 seconds. The push button 95 illustrated in [Fig.2] represents the contact of the headlight control lever.

[0095] The manual activation condition may be pressing a specific activation button 12.

[0096] The driver can thus occasionally add a triggering of the second recording process when he notices a particular problem or when a malfunction indicator light has come on.

[0097] The execution of this additional recording of second data set, manually triggered, can be further subject to an engine running condition and a zero vehicle speed condition.

[0098] Example of a timeline

[0099] The measurement sequence by the data recorder 1 starts at the instant tl when the driver switches on the ignition ('IGN') 31 and starts the vehicle.

[0100] From this moment, the first PERI basic registration process is executed in the background.

[0101] During the first few kilometers of SKI between time t1 and t8, the automatic trigger conditions prohibit the second recording process from being launched.

[0102] At time t2, the current mileage KM becomes such that KM = KMLast + N1K. We have therefore reached the recurrence based on the kilometer periodicity and the second recording process PER2 is triggered.

[0103] The top line ('Cond Auto') in [Fig.3] illustrates the logic output of the automatic conditions for launching the second recording process. At time t2, logic state 32 changes to 1.

[0104] At the end of the execution of the second recording process, the current mileage KM overwrites the old value of KMLast.

[0105] At time t3, the current mileage KM becomes such that KM = KMLast + N1K. The recurrence based on the kilometer periodicity has therefore been reached again and the second recording process PER2 is triggered. At time t3, the logic state 33 changes to 1.

[0106] At time t4, there is an occurrence of manual triggering. On the line marked 'Act Manu' in [Fig.3], logic signal 34 goes to 1.

[0107] Depending on the options selected, the current mileage KM can be reassigned to the KMLast memory or not.

[0108] At time t5, the current mileage KM becomes such that KM = KMLast + N1K. The recurrence based on the kilometer periodicity has therefore been reached again (from t3 or t4 depending on the configuration) and the second recording process PER2 is triggered. At time t5, the logic state 35 changes to 1.

[0109] At time t6, the rolling sequence is finished and the contact is cut, this falling edge is noted 36.

[0110] Between time t6 and t7, the data recorder 1 performs a remote transmission step 14 of the collected data (ER1 and ER2), by the first process PERlet the second process PER2, to a remote server 4, for subsequent exploitation. This is represented by block 37 on line 'WiTX'.

[0111] When the remote transmission has been carried out correctly, the storage area corresponding to this data in the memory 8 of the data recorder can be used again to store new data there.

[0112] Whereby, a storage capacity of 32 gigabits or 64 gigabits may be sufficient for the memory 8 in the data logger.

[0113] The data logger 1 may be based on the IPElog2™ product line of the IPETRONIK™ company.

Claims

Claims

1. Method for recording, in a data recorder (1), data relating to a vehicle under test (9), the method comprising a first recording process (PERI), called basic, of periodic type, with a first periodicity, involving a first data set, characterized in that the method provides a second recording process (PER2) of event type, triggered by trigger conditions and involving a second data set, the second data set being larger than the first data set, the trigger conditions comprising at least one or more automatic trigger conditions, the data volume of the second data set being at least five times greater than the data volume of the first data set.

2. Method according to claim 1, characterized in that during a run of the second recording process, the first recording process is paused, and the first recording process is resumed when the run of the second recording process is completed, and the current mileage of the vehicle is recorded in a memory denoted KMLast at the time when the run of the second recording process ends.

3. Method according to any one of claims 1 to 2, characterized in that the procedure provides for counting a cumulative mileage noted KMC, traveled since the start of the measurement, the start of the measurement corresponding to the start of the vehicle driving sequence.

4. Method according to claim 2 and claim 3, characterized in that the current mileage of the vehicle, denoted KM, is iteratively recorded and the automatic activation conditions comprise at least one logical check as follows: KM - KMLast > N1K, and KMC > SKI, where N1K and SKI are calibratable mileage values.

5. Method according to claim 4, characterized in that the automatic activation conditions further comprise: - a temperature condition, consisting in that a current engine temperature value noted TMC, is such that TMC > STI - a vehicle speed condition, consisting in that at least one vehicle speed value has exceeded a threshold noted SV 1 since the start of the vehicle driving / measurement sequence, where STI and SV1 are calibratable values, respectively of temperature and speed.

6. Method according to any one of claims 1 to 5, characterized in that the method provides a step of remote transmission (14) of the data collected by the first process and the second process, to a remote server (4).

7. Method according to claim 6, characterized in that the step of remote transmission of the data is generated on a condition of cutting off the ignition (36) of the vehicle.

8. A method according to any one of claims 1 to 7, characterized in that the triggering conditions further comprise a manual activation condition, the manual activation condition including activation of the vehicle's headlights for 10 seconds or pressing a specific activation button (12).

9. Recording system comprising a data logger (1), a user interface with a specific activation button (12) and a light or text indication (13), characterized in that the data logger is configured to implement the method according to one of claims 1 to 8.

10. Recording system according to claim 9, wherein the data recorder comprises remote transmission means (16,17) characterized in that the data recorder is configured to implement the method according to one of claims 6 to 7.

Images