'89 probs-typical scan data
Thread Starter
Burning Brakes
Joined: Dec 2003
Posts: 1,183
Likes: 1
From: MidOhio
'89 probs-typical scan data
OK, so now I'm playing with my brand new AutoXray 3000 scanner and graphing software and I've come up with a general question, sort of!
One of the probs I'm trying to solve is the fact that when I drop the throttle on my automatic in D or OD, for instance at 63 mph, the scan data shows the injector pulse doesn't go to zero for 4.5 sec after the TPS is at .52 V (closed throttle). That's an awful long time when there's a cop comming at ya in a 50 zone and you don't want to light up the brakes.
It drops from 4 mS to 1.4 mS in the 0.5 S it takes for theTPS to hit zero and then dribbles to 0.9 mS, 4 sec after TPS hit zero, then drops to zero in the last 0.5 sec. Anyone out there know if this kind of time delay is a normal thing with these TPI systems?
One of the probs I'm trying to solve is the fact that when I drop the throttle on my automatic in D or OD, for instance at 63 mph, the scan data shows the injector pulse doesn't go to zero for 4.5 sec after the TPS is at .52 V (closed throttle). That's an awful long time when there's a cop comming at ya in a 50 zone and you don't want to light up the brakes.
It drops from 4 mS to 1.4 mS in the 0.5 S it takes for theTPS to hit zero and then dribbles to 0.9 mS, 4 sec after TPS hit zero, then drops to zero in the last 0.5 sec. Anyone out there know if this kind of time delay is a normal thing with these TPI systems?
Le Mans Master
Joined: Dec 2000
Posts: 7,839
Likes: 22
From: San Diego, Ca
If it immediately dropped to zero it would quit.
The IAC acts like a dashpot to prevent stalling; that extra air needs fuel.
Most AutoXrays are slow (realitively speaking); so you're not seeing real time data when you log. If you have a driveability issue, post what it is. Otherwise, capturing and saving info when it's good, is good for when it's bad.
The IAC acts like a dashpot to prevent stalling; that extra air needs fuel.
Most AutoXrays are slow (realitively speaking); so you're not seeing real time data when you log. If you have a driveability issue, post what it is. Otherwise, capturing and saving info when it's good, is good for when it's bad.
Thread Starter
Burning Brakes
Joined: Dec 2003
Posts: 1,183
Likes: 1
From: MidOhio
If it immediately dropped to zero it would quit.
The IAC acts like a dashpot to prevent stalling; that extra air needs fuel.
Most AutoXrays are slow (realitively speaking); so you're not seeing real time data when you log. If you have a driveability issue, post what it is. Otherwise, capturing and saving info when it's good, is good for when it's bad.
The IAC acts like a dashpot to prevent stalling; that extra air needs fuel.
Most AutoXrays are slow (realitively speaking); so you're not seeing real time data when you log. If you have a driveability issue, post what it is. Otherwise, capturing and saving info when it's good, is good for when it's bad.
Le Mans Master
Joined: Aug 2000
Posts: 8,838
Likes: 31
From: Australia
The X ray is not being updated as fast as the data is being produced which you can see in more detail with a laptop , ALDL cable and datalogging software. Consider what you are seeing a snapshot
Exp
The '85 ECM transmitted diagnostic data at 160 BAUD ; about a 1.25 second interval between the 25 Bytes of data
The 85 - 89 ECM transmits diagnostic data at 8192 BAUD. The data stream of 64 Bytes cycles through every 62.5 milliseconds (16 per second) at this rate.
Melting Slicks
Joined: Aug 2003
Posts: 3,389
Likes: 391
From: Lakeville MI
The injector BPW going to zero is DFCO, or Deceleration Fuel Cut Off.
There is a delay timer and disable/enable LV8 thresholds for DFCO along with throttle, rpm and velocity conditons.
With factory tuning, the LV8 to disable/enable DFCO is rather low (40/33 or 40/30) and the delay time is 1.75 seconds (manual) or 0.25 seconds (auto).
So it takes time for the IAC to reduce the airflow to bring the LV8 down into the DFCO enable range, and another 0.25-1.75 seconds delay time with conditions fulfilled before fuel cut occurs. 4.5 seconds sounds reasonable.
I've gone as low as 300 ms for the delay and raised the LV8 disable/enable thresholds to roughly 80/70, for nearly instantaneous DFCO on throttle release. Tuned in this manner the powertrain wind up/wind down and subsequent engine braking and DFCO fuel cut occur almost simultaneously for a smooth transition from accel to decel.
Feels good for long periods of coast down, but can be annoying in traffic, if I lift the throttle a hair. For increased comfort, I've added some delay back in (approx 1 second), so I get a sort-of bimodal engine braking response.
There is a delay timer and disable/enable LV8 thresholds for DFCO along with throttle, rpm and velocity conditons.
With factory tuning, the LV8 to disable/enable DFCO is rather low (40/33 or 40/30) and the delay time is 1.75 seconds (manual) or 0.25 seconds (auto).
So it takes time for the IAC to reduce the airflow to bring the LV8 down into the DFCO enable range, and another 0.25-1.75 seconds delay time with conditions fulfilled before fuel cut occurs. 4.5 seconds sounds reasonable.
I've gone as low as 300 ms for the delay and raised the LV8 disable/enable thresholds to roughly 80/70, for nearly instantaneous DFCO on throttle release. Tuned in this manner the powertrain wind up/wind down and subsequent engine braking and DFCO fuel cut occur almost simultaneously for a smooth transition from accel to decel.
Feels good for long periods of coast down, but can be annoying in traffic, if I lift the throttle a hair. For increased comfort, I've added some delay back in (approx 1 second), so I get a sort-of bimodal engine braking response.
Last edited by tequilaboy; Nov 4, 2009 at 12:44 PM.
Thread Starter
Burning Brakes
Joined: Dec 2003
Posts: 1,183
Likes: 1
From: MidOhio
The injector BPW going to zero is DFCO, or Deceleration Fuel Cut Off.
There is a delay timer and disable/enable LV8 thresholds for DFCO along with throttle, rpm and velocity conditons.
With factory tuning, the LV8 to disable/enable DFCO is rather low (40/33 or 40/30) and the delay time is 1.75 seconds (manual) or 0.25 seconds (auto).
So it takes time for the IAC to reduce the airflow to bring the LV8 down into the DFCO enable range, and another 0.25-1.75 seconds delay time with conditions fulfilled before fuel cut occurs. 4.5 seconds sounds reasonable.
I've gone as low as 300 ms for the delay and raised the LV8 disable/enable thresholds to roughly 80/70, for nearly instantaneous DFCO on throttle release. Tuned in this manner the powertrain wind up/wind down and subsequent engine braking and DFCO fuel cut occur almost simultaneously for a smooth transition from accel to decel.
Feels good for long periods of coast down, but can be annoying in traffic, if I lift the throttle a hair. For increased comfort, I've added some delay back in (approx 1 second), so I get a sort-of bimodal engine braking response.
There is a delay timer and disable/enable LV8 thresholds for DFCO along with throttle, rpm and velocity conditons.
With factory tuning, the LV8 to disable/enable DFCO is rather low (40/33 or 40/30) and the delay time is 1.75 seconds (manual) or 0.25 seconds (auto).
So it takes time for the IAC to reduce the airflow to bring the LV8 down into the DFCO enable range, and another 0.25-1.75 seconds delay time with conditions fulfilled before fuel cut occurs. 4.5 seconds sounds reasonable.
I've gone as low as 300 ms for the delay and raised the LV8 disable/enable thresholds to roughly 80/70, for nearly instantaneous DFCO on throttle release. Tuned in this manner the powertrain wind up/wind down and subsequent engine braking and DFCO fuel cut occur almost simultaneously for a smooth transition from accel to decel.
Feels good for long periods of coast down, but can be annoying in traffic, if I lift the throttle a hair. For increased comfort, I've added some delay back in (approx 1 second), so I get a sort-of bimodal engine braking response.
