Real-time vehicle data acquisition and analysis

• US 9,771,880 B2
• Filed: 05/16/2014
• Issued: 09/26/2017
• Est. Priority Date: 05/16/2014
• Status: Active Grant

• Current Assignee: FCA US LLC (Stellantis NV)
• Original Assignee: FCA US LLC (Stellantis NV)
• Inventors: Lee, Yung-Li, Dourra, Hussein, Tjhung, Tana, Theru, Sangeeta
• Primary Examiner(s): Paige, Tyler
• Application Number:
  US14/279,393
• Publication Number:
  US 20150330317A1
• Time in Patent Office: 1,229 Days
• Field of Search: 701 291, 73760
• CPC Class Codes: F02D 2200/1002 Output torque
• CPC Class Codes: F02D 28/00 Programme-control of engines
• CPC Class Codes: F02D 29/02 peculiar to engines driving vehicles; peculiar to engines driving variable pitch propellers
• CPC Class Codes: F02D 41/28 Interface circuits

Abstract

An engine controller, system and method for collecting vehicle data. Drive torque data is determined using the engine controller in the vehicle and is stored in a memory in the vehicle. The drive torque data is stored in a non-time domain format, and may include a histogram of numbers of revolutions at predetermined intervals of drive torque values and/or a matrix of rainflow cycle counts. The drive torque data is temporarily stored in a buffer prior to being stored in the matrix of rainflow cycle counts using back-checking and binning. The drive torque data is downloaded from the vehicle and transmitted to a central data collection center.

Claims

1. A vehicle data collection system, the system comprising:

a vehicle comprising a driveshaft and an engine controller, the engine controller comprising;

a processor configured to;

determine driveshaft torque data by utilizing a simulation model to calculate torque at the driveshaft based on a set of vehicle data including at least one of a vehicle throttle position, a vehicle axle ratio, and a vehicle axle weight, wherein the driveshaft torque data (i) represents torque at the driveshaft for each revolution of the driveshaft over a period in a time-domain and (ii) comprises a plurality of peaks and valleys corresponding to local driveshaft torque maximums and minimums, and

using the driveshaft torque data, generate a revolutions-at-torque output comprising (i) a plurality of distinct ranges of driveshaft torque and (ii) counts for each driveshaft torque range, each count being indicative of a particular driveshaft torque of the driveshaft torque data falling within a particular driveshaft torque range, and

a memory (i) having a limited capacity such that it is incapable of storing the driveshaft torque data and (ii) configured to store information comprising the revolutions-at-torque output; and

a data collection device configured to download the information from the memory.

2. The system of claim 1, wherein the data collection device is configured to download the information when the vehicle is being serviced.

3. The system of claim 2, further comprising a central data collection center configured to receive the downloaded information upon transmission by the data collection device.

4. The system of claim 3, wherein the central data collection center is configured to utilize the information to predict a useful life of at least one of the driveshaft and a component related to the driveshaft.

5. The system of claim 4, wherein the central data collection center is configured to predict the useful life of at least one of the driveshaft and the driveshaft -related component by:

converting the revolutions-at-torque output to a histogram plot; and

utilizing the histogram plot to estimate a fatigue experienced by the at least one of the driveshaft and the driveshaft-related component at each of the plurality of distinct ranges of driveshaft torque.

6. The system of claim 3, wherein the central data collection center is configured to utilize the information to validate or revise designs of a future version of at least one of the driveshaft and a component related to the driveshaft.

7. The system of claim 1, wherein:

the memory comprises a buffer configured for temporary storage;

the processor is further configured to utilize the buffer perform rainflow processing on the driveshaft torque data by;

applying a rainflow cycle counting rule to organize the driveshaft torque data into rainflow cycles, and

generating a rainflow matrix comprising the rainflow cycles; and

the memory is configured to store the rainflow matrix as part of the information.

8. The system of claim 7, wherein:

the rainflow cycle counting rule is a four-point rainflow cycle counting rule; and

applying the rainflow cycle counting rule comprises;

initializing the buffer,

temporarily storing, by the buffer, a plurality of driveshaft torques of the driveshaft torque data,

identifying four consecutive peaks/valleys within the plurality of driveshaft torques,

determining whether two intermediary peaks/valleys within the four consecutive peaks/valleys have magnitudes that are bounded by a remaining two peaks/valleys of the four consecutive peaks valleys, and

when the two intermediary peaks/valleys have magnitudes that are bounded by the remaining two peaks/valleys, counting the intermediary peaks/valleys as a cycle.

9. A method for obtaining and storing driveshaft torque data for a vehicle comprising a driveshaft and an engine controller, the method comprising:

determining, by a processor of the engine controller, driveshaft torque data by utilizing a simulation model to calculate the torque at the driveshaft based on a set of vehicle data including at least one of a vehicle throttle position, a vehicle axle ratio, and a vehicle axle weight, wherein the driveshaft torque data (i) represents torque at the driveshaft for each revolution of the driveshaft over a period in a time-domain and (ii) comprises a plurality of peaks and valleys corresponding to local driveshaft torque maximums and minimums,

utilizing, by the processor, a buffer of a memory of the engine controller to perform rainflow processing on the driveshaft torque data by;

applying a rainflow cycle counting rule to organize the driveshaft torque data into rainflow cycles, and

generating a rainflow matrix comprising the rainflow cycles;

storing, by the memory, information comprising the rainflow matrix, the memory having a limited capacity such that it is incapable of storing the driveshaft torque data; and

downloading, from the engine controller by a data collection device, the information.

10. The method of claim 9, wherein:

the rainflow cycle counting rule is a four-point rainflow cycle counting rule; and

applying the rainflow cycle counting rule comprises;

initializing the buffer,

temporarily storing, by the buffer, a plurality of driveshaft torques of the driveshaft torque data,

identifying four consecutive peaks/valleys within the plurality of driveshaft torques,

determining whether two intermediary peaks/valleys within the four consecutive peaks/valleys have magnitudes that are bounded by a remaining two peaks/valleys of the four consecutive peaks valleys, and

when the two intermediary peaks/valleys have magnitudes that are bounded by the remaining two peaks/valleys, counting the intermediary peaks/valleys as a cycle.

11. The method of claim 9, wherein the data collection device is configured to download the information when the vehicle is being serviced.

12. The method of claim 11, further comprising receiving, by a central data collection center via transmission from the data collection device, the information.

13. The method of claim 12, further comprising utilizing, by the central data collection center, the information to predict a useful life of at least one of the driveshaft and a component related to the driveshaft.

14. The method of claim 13, further comprising:

using the driveshaft torque data, generating, by the processor, a revolutions-at-torque output comprising (i) a plurality of distinct ranges of driveshaft torque and (ii) counts for each driveshaft torque range, each count being indicative of a particular driveshaft torque of the driveshaft torque data falling within a particular driveshaft torque range; and

storing, by the memory, the revolutions-at-torque output as part of the information.

15. The method of claim 14, further comprising predicting, by the central data collection center, the useful life of at least one of the driveshaft and the driveshaft-related component by:

converting the revolutions-at-torque output to a histogram plot; and

utilizing the histogram plot to estimate a fatigue experienced by the at least one of the driveshaft and the driveshaft-related component at each of the plurality of distinct ranges of driveshaft torque.

16. The method of claim 12, further comprising utilizing, by the central data collection center, the information to validate or revise designs of a future version of at least one of the driveshaft and a component related to the driveshaft.

17. A vehicle data collection system, the system comprising:

a vehicle comprising a driveshaft and an engine controller, the engine controller comprising;

a processor configured to;

obtain driveshaft torque data that represents torque at the driveshaft for each revolution of the driveshaft over a period in a time-domain, the driveshaft torque data comprising a plurality of peaks and valleys corresponding to local driveshaft torque maximums and minimums, and

using the driveshaft torque data, generate a revolutions-at-torque output comprising (i) a plurality of distinct ranges of driveshaft torque and (ii) counts for each driveshaft torque range, each count being indicative of a particular driveshaft torque of the driveshaft torque data falling within a particular driveshaft torque range, and

a memory (i) having a limited capacity such that it is incapable of storing the driveshaft torque data and (ii) configured to store information comprising the revolutions-at-torque output;

a data collection device configured to download the information from the memory when the vehicle is being serviced; and

a central data collection center configured to;

receive the downloaded information upon transmission by the data collection device; and

utilize the information to predict a useful life of at least one of the driveshaft and a component related to the driveshaft by;

converting the revolutions-at-torque output to a histogram plot; and

utilizing the histogram plot to estimate a fatigue experienced by the at least one of the driveshaft and the driveshaft-related component at each of the plurality of distinct ranges of driveshaft torque.