IP Library Granted Patent US 9,221,465
Granted Patent B2
US 9,221,465 · App. 14/032,807 · Granted Dec 29, 2015

Rough road detection and misfire control

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,221,465
App. No.
14/032,807
Granted
Dec 29, 2015
Kind
B2
Abstract

Computer-implemented techniques include determining, at a controller of a vehicle, a wheel speed for each of two front wheels of the vehicle and two rear wheels of the vehicle. The techniques include calculating, at the controller, a difference between (i) an average of the wheel speeds for the two front wheels of the vehicle and (ii) an average of the wheel speeds for the two rear wheels of the vehicle to obtain an error. The techniques include setting, at the controller, a rough road detection bit when the error is greater than or equal to a threshold indicative of an error corresponding to rough road. The techniques include monitoring, at the controller, the rough road detection bit for a period to obtain a hysteresis band. The techniques also include determining, at the controller, whether the vehicle is traveling on rough road based on the hysteresis band.

Claims (49)

1. A method, comprising:

determining, at a controller of a vehicle, the controller including one or more processors, a wheel speed for each of two front wheels of the vehicle and two rear wheels of the vehicle;

calculating, at the controller, a difference between (i) an average of the wheel speeds for the two front wheels of the vehicle and (ii) an average of the wheel speeds for the two rear wheels of the vehicle to obtain an error;

setting, at the controller, a rough road detection bit when the error is greater than or equal to a threshold indicative of an error corresponding to rough road;

monitoring, at the controller, the rough road detection bit for a period to obtain a hysteresis band; and

based on the hysteresis band, determining, at the controller, whether (i) the vehicle is traveling on rough road or (ii) an engine of the vehicle has misfired.

2. The method of claim 1 , further comprising receiving, at the controller, wheel speed signals from wheel speed sensors associated with the two front wheels and the two rear wheels of the vehicle via a controller area network (CAN), the wheel speed signals being indicative of the wheel speeds for each of the two front wheels and the two rear wheels of the vehicle.

3. The method of claim 2 , further comprising validating, at the controller, the signals as being (i) accurate and (ii) having been generated by the wheel speed sensors within a previous predetermined period.

4. The method of claim 2 , further comprising:

scaling, at the controller, the wheel speed signals to obtain modified wheel speed signals having increased resolutions,

wherein determining the error includes calculating a difference between (i) an average of the modified wheel speed signals for the two front wheels of the vehicle and (ii) an average of the modified wheel speed signals for the two rear wheels of the vehicle.

5. The method of claim 4 , further comprising calculating, at the controller, an absolute value of the error to obtain a modified error.

6. The method of claim 5 , further comprising applying, at the controller, an adjustable gain to the modified error to obtain a first adjusted error.

7. The method of claim 6 , further comprising applying, at the controller, a low-pass filter to the first adjusted error to obtain a filtered error.

8. The method of claim 7 , further comprising adjusting, at the controller, the filtered error to compensate for any offset in the CAN between (i) the wheel speed signals for the two front wheels and (ii) the wheel speed signals for the two rear wheels to obtain a second adjusted error.

9. The method of claim 8 , further comprising applying, at the controller, the cube law to the second adjusted error to obtain a final error.

10. The method of claim 9 , wherein setting the rough road detection bit includes setting, at the controller, the rough road detection bit when the final error is greater than or equal to the threshold.

11. The method of claim 1 , wherein monitoring the rough road detection bit includes counting, at the controller, a number of times the rough road detection bit is set during the period.

12. The method of claim 11 , wherein determining whether the vehicle is traveling on rough road includes:

determining, at the controller, that the vehicle is traveling on rough road when the number of times the rough road detection bit was set during the period is greater than or equal to a count threshold; and

determining, at the controller, that the vehicle is not traveling on rough road when the number of times the rough road detection bit was set during the period is less than the count threshold.

13. The method of claim 12 , further comprising:

detecting, at the controller, a possible misfire of the engine of the vehicle based on a rotational profile of a crankshaft of the engine;

determining, at the controller, that the possible misfire of the engine is not a misfire when the vehicle is determined to be traveling on rough road; and

determining, at the controller, that the possible misfire of the engine is a misfire when the vehicle is determined to not be traveling on rough road.

14. The method of claim 12 , further comprising validating, at the controller, an accelerometer of the vehicle based on the determination of whether the vehicle is traveling on rough road.

15. The method of claim 12 , further comprising controlling, by the controller, torque output of an engine of the vehicle based on the hysteresis band.

16. A method, comprising:

determining, at a controller of a vehicle, the controller including one or more processors, signals indicative of wheel speeds for each of four wheels of the vehicle from respective wheel speed sensors, the four wheels of the vehicle including two front wheels and two rear wheels;

validating, at the controller, the signals as being (i) accurate and (ii) having been generated by the wheel speed sensors within a previous predetermined period;

scaling, at the controller, the signals to increase a resolution of each of the signals in response to the signals being validated;

calculating, at the controller, a difference between (i) an average of the signals for the two front wheels of the vehicle and (ii) an average of the signals for the two rear wheels of the vehicle to obtain an error;

calculating, at the controller, an absolute value of the error to obtain a modified error;

applying, at the controller, an adjustable gain to the modified error to obtain a first adjusted error;

applying, at the controller, a low-pass filter to the first adjusted error to obtain a filtered error;

adjusting, at the controller, the filtered error to compensate for any offset between (i) the signals for the two front wheels and (ii) the signals for the two rear wheels to obtain a second adjusted error;

applying, at the controller, the cube law to the second adjusted error to obtain a final error;

setting, at the controller, a rough road detection bit when the final error is greater than a threshold indicative of an error corresponding to rough road;

monitoring, at the controller, the rough road detection bit for a period to obtain a hysteresis band; and

based on the hysteresis band, determining, at the controller, whether (i) the vehicle is traveling on rough road or (ii) an engine of the vehicle has misfired.

17. The method of claim 16 , wherein monitoring the rough road detection bit includes counting, at the controller, a number of times the rough road detection bit is set during the period.

18. The method of claim 17 , wherein determining whether the vehicle is traveling on rough road includes:

determining, at the controller, that the vehicle is traveling on rough road when the number of times the rough road detection bit was set during the period is greater than or equal to a count threshold; and

determining, at the controller, that the vehicle is not traveling on rough road when the number of times the rough road detection bit was set during the period is less than the count threshold.

19. The method of claim 17 , further comprising:

detecting, at the controller, a possible misfire of the engine of the vehicle based on a rotational profile of a crankshaft of the engine;

determining, at the controller, that the possible misfire of the engine is not a misfire when the vehicle is determined to be traveling on rough road; and

determining, at the controller, that the possible misfire of the engine is a misfire when the vehicle is determined to not be traveling on rough road.

20. The method of claim 17 , further comprising validating, at the controller, an accelerometer of the vehicle based on the determination of whether the vehicle is traveling on rough road.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Jan 24, 2019
From: JPMORGAN CHASE BANK, N.A.
To: FCA US LLC (FORMERLY KNOWN AS CHRYSLER GROUP LLC)
Reel/Frame 048177/0356 →
RELEASE OF SECURITY INTEREST Recorded May 30, 2017
From: CITIBANK, N.A.
To: FCA US LLC (FORMERLY KNOWN AS CHRYSLER GROUP LLC)
Reel/Frame 042885/0255 →
RELEASE OF SECURITY INTEREST RELEASING SECOND-LIEN SECURITY INTEREST PREVIOUSLY RECORDED AT REEL 026426 AND FRAME 0644, REEL 026435 AND FRAME 0652, AND REEL 032384 AND FRAME 0591 Recorded Feb 11, 2016
From: CITIBANK, N.A.
To: FCA US LLC, FORMERLY KNOWN AS CHRYSLER GROUP LLC
Reel/Frame 037784/0001 →
CHANGE OF NAME Recorded Mar 19, 2015
From: CHRYSLER GROUP LLC
To: FCA US LLC
Reel/Frame 035225/0202 →
SECURITY AGREEMENT Recorded Mar 4, 2014
From: CHRYSLER GROUP LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 032384/0640 →
SECURITY AGREEMENT Recorded Mar 4, 2014
From: CHRYSLER GROUP LLC
To: CITIBANK, N.A.
Reel/Frame 032384/0591 →
SECURITY AGREEMENT Recorded Mar 4, 2014
From: CHRYSLER GROUP LLC
To: CITIBANK, N.A.
Reel/Frame 032384/0477 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 20, 2013
From: VARADY, ARTHUR J; KOHLER, PATRICK J; SWANSON, JOHNATHAN M
To: CHRYSLER GROUP LLC
Reel/Frame 031251/0539 →