Notices
Series II Technical and Trouble shooting Discuss technical details for the Series II RX-8 and any issues or problems you are facing

Monitoring engine health with OBD datalogging

Thread Tools
 
Search this Thread
 
Rate Thread
 
Old 02-21-2018, 11:43 AM
  #1  
Registered
Thread Starter
iTrader: (1)
 
IamFodi's Avatar
 
Join Date: Mar 2014
Location: Philadelphia, PA
Posts: 862
Received 84 Likes on 68 Posts
Monitoring engine health with OBD datalogging

I want to try to use OBD datalogging to catch problems with aging injectors/sensors/etc. as they develop, before they're bad enough to trigger a CEL. The idea is to randomly datalog my drives to build up a history, and then watch for deviations from the baseline.

Anyone have feedback on good parameters to measure? I’ll be using Torque Pro with a generic OBD Bluetooth dongle.

Fuel trims and cat temp are two fairly obvious examples. Another might be ignition timing. I'd imagine any of those would have to be compared against IATs, throttle, measured load, etc. But that bridge can be crossed later.

I can’t be the first to think of this. Anyone heard of others doing it? What do tuners monitor when they do remote tunes?

Any thoughts welcome.
Old 02-21-2018, 11:44 AM
  #2  
SARX Legend
iTrader: (46)
 
9krpmrx8's Avatar
 
Join Date: Jan 2007
Location: San Antonio, Texas
Posts: 33,784
Received 452 Likes on 366 Posts
It's really too bad we don't have a real oil pressure sensor, that is probably the most important that we cannot monitor. We cannot monitor fuel pressure either which is also a bummer.

Timing doesn't help much because the knock sensor is not reliable. I'd go with g/sec air at idle, and LTFT over time. If idle gets too far off from 5.5 g/sec or fuel trims build, something is up.

Cat temp isn't awful, but the sensor is kind of slow so it won't tell you a ton except for long-term cat failure.

IAT's are so-so since the stock intake is pretty darn good, however, if you go FI, different story.

If you already own the logger then do airflow at idle, and fuel trims, but not a ton of useful information on the rest, unfortunately.

Last edited by Kane; 02-21-2018 at 06:46 PM. Reason: Translating for cranky 9K.
Old 02-21-2018, 06:47 PM
  #3  
Illudium Q-36 Space Moderator
iTrader: (1)
 
Kane's Avatar
 
Join Date: Jan 2007
Location: PCB
Posts: 6,364
Received 41 Likes on 31 Posts
Luckily, I am an excellent translator of disgruntled veterans.
The following users liked this post:
IamFodi (02-21-2018)
Old 02-21-2018, 07:42 PM
  #4  
Registered
Thread Starter
iTrader: (1)
 
IamFodi's Avatar
 
Join Date: Mar 2014
Location: Philadelphia, PA
Posts: 862
Received 84 Likes on 68 Posts
Thanks, Kane.
Old 02-21-2018, 08:54 PM
  #5  
Modulated Moderator
iTrader: (3)
 
dannobre's Avatar
 
Join Date: Feb 2004
Location: Smallville
Posts: 13,718
Received 334 Likes on 289 Posts
Originally Posted by 9krpmrx8
It's really too bad we don't have a real oil pressure sensor, that is probably the most important that we cannot monitor. We cannot monitor fuel pressure either which is also a bummer.

Timing doesn't help much because the knock sensor is not reliable. I'd go with g/sec air at idle, and LTFT over time. If idle gets too far off from 5.5 g/sec or fuel trims build, something is up.

Cat temp isn't awful, but the sensor is kind of slow so it won't tell you a ton except for long-term cat failure.

IAT's are so-so since the stock intake is pretty darn good, however, if you go FI, different story.

If you already own the logger then do airflow at idle, and fuel trims, but not a ton of useful information on the rest, unfortunately.

F**CKING LOL

Kane you are the man
The following users liked this post:
Kane (02-23-2018)
Old 02-24-2018, 01:53 PM
  #6  
Registered
Thread Starter
iTrader: (1)
 
IamFodi's Avatar
 
Join Date: Mar 2014
Location: Philadelphia, PA
Posts: 862
Received 84 Likes on 68 Posts
So, few questions/comments on this.

"g/sec air at idle" refers to the MAF reading at warm idle, correct? And if I see a deviation, that might be a reason to check the MAF sensor? What else would be worth looking at if that happened?

Understood about cat temp. Long-term failure (in this and other parts) is exactly what I'm looking to increase my odds of detecting.

What about O2 sensor readings? I know O2 sensors fail gradually; could I expect the logged values to change over time?

I brought up IATs and those other parameters not to suggest that they'd be interesting on their own, but because I thought they'd be necessary context for things like ignition timing. Correlating everything might be more trouble than it's worth, though. Maybe another day, when I have a ton more time on my hands...

Last edited by IamFodi; 02-24-2018 at 01:56 PM.
Old 02-24-2018, 02:58 PM
  #7  
Registered
iTrader: (1)
 
Loki's Avatar
 
Join Date: Jun 2009
Location: Montreal
Posts: 7,713
Received 952 Likes on 830 Posts
O2 sensor failure manifests as inconsistent readings or slow response. There is an OBD code for slow response, and I *think* there is one for inconsistent readings also. So you don't really need to monitor the raw output yourself.

Cat temp, coolant temp and fuel trims get you 90% of the info necessary to detect a problem. Oil pressure/temp would be the other 10%.
The following users liked this post:
IamFodi (02-24-2018)
Old 02-25-2018, 03:52 PM
  #8  
Illudium Q-36 Space Moderator
iTrader: (1)
 
Kane's Avatar
 
Join Date: Jan 2007
Location: PCB
Posts: 6,364
Received 41 Likes on 31 Posts
Originally Posted by iamfodi
so, few questions/comments on this.

"g/sec air at idle" refers to the maf reading at warm idle, correct? And if i see a deviation, that might be a reason to check the maf sensor? What else would be worth looking at if that happened?
vacuum leak

understood about cat temp. Long-term failure (in this and other parts) is exactly what i'm looking to increase my odds of detecting.

What about o2 sensor readings? I know o2 sensors fail gradually; could i expect the logged values to change over time?
fuel trims will also alert you to this.

i brought up iats and those other parameters not to suggest that they'd be interesting on their own, but because i thought they'd be necessary context for things like ignition timing. Correlating everything might be more trouble than it's worth, though. timing has always been the bane of our engines, too hard to accurately gain insight with odbii only.

maybe another day, when i have a ton more time on my hands...
123
The following users liked this post:
IamFodi (02-25-2018)
Old 02-25-2018, 05:15 PM
  #9  
Boosted Kiwi
iTrader: (2)
 
Brettus's Avatar
 
Join Date: Apr 2006
Location: Y-cat-o NZ
Posts: 20,523
Received 1,490 Likes on 839 Posts
Bit late ...but here are the parameters I monitor when tuning etc :


The following users liked this post:
IamFodi (02-25-2018)
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
no-coast-punk
Series I Interior, Audio, and Electronics
1
05-07-2014 01:37 AM
da67goatman
Series I Interior, Audio, and Electronics
10
03-30-2014 01:29 PM
tiltmode43
Series I Engine Tuning Forum
10
05-26-2011 08:01 PM
Daemos
Canada Forum
20
07-27-2008 03:08 PM
carbonRX8
Series I Do It Yourself Forum
13
05-22-2006 09:37 PM



You have already rated this thread Rating: Thread Rating: 0 votes,  average.

Quick Reply: Monitoring engine health with OBD datalogging



All times are GMT -5. The time now is 10:48 AM.