If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

94-95 $EE xdf (EEXTRA)

!!!DISCLAIMER!!!

I make no guarantee as to the accuracy of this definition or any definition created by or modified by me. Use at your own risk! If you break your vehicle, fail emissions testing, or etc…, the fault is yours and no one else's.

Read the "==!!Read!!==" section using category view for the big thank you for information.

09/14/17 LT1(older diss files from gearhead-efi repo).zip
added diss file that helped me with this xdf.(I have not edited these in anyway, the way you see them is the way i got them)

10/26/17 obd2 on left obd1 on right.jpg
the pic im posting are of my personal obd2 xdf and a 96 corvette auto cal and a 96 roadmaster cal this is the left side of the pic.
The right side of the pic is the obd1 EE xdf and a 95 corvette auto bin and a 95 road master bin.

Lots is the same between the 94-95, 96-97 calibrations.

DO NOT ASK FOR THE OBD2 XDF I WILL NOT GIVE A COPY!!!

11/17/2017 added pic of the same code between $0D and $EE
seems $0D and $EE share alot of the same auto trans routines.

been looking at this XDF with my noob eyes and (in addition to the ton of new parameters) I noticed a difference at address 0x12046 (unknown spark adder vs. EST sytem time lag, 2 digit usec vs 1 digit integer display). Dunno if it means anything but it may be helpful to know, I have it set to 0 in my bin so I don't have to try to account for added spark when working with the main advance tables...

been looking at this XDF with my noob eyes and (in addition to the ton of new parameters) I noticed a difference at address 0x12046 (unknown spark adder vs. EST sytem time lag, 2 digit usec vs 1 digit integer display). Dunno if it means anything but it may be helpful to know, I have it set to 0 in my bin so I don't have to try to account for added spark when working with the main advance tables...

Here's what I have on file.

Hi Jonathon,

This is the EST system time lag and is meant to correct for the latency in the spark system. It is a fixed value in usec:

lag (usec.) = N x 0.08477

Of course since the time lag is a fix time value the correction in terms of degrees will depend on RPM.

Here's what I have on file. Hi Jonathon, This is the EST system time lag and is meant to correct for the latency in the spark system. It is a fixed value in usec: lag (usec.) = N x 0.08477 Of course since the time lag is a fix time value the correction in terms of degrees will depend on RPM. Best regards, TC

Has this exposed any kind of kickdown delay constant? In B-body applications, the 4L60E is significantly more responsive to a kickdown in the 9C1/Impala SS applications, than the Roadmaster or Fleetwood applications. And I have a Roadmaster where the kickdown delay is maddening. I just got this 96 Roadmaster so my head is spinning as I figure out what my best tuning options are (very limited if I stay with the 96 PCM, I know).

EDIT: I loaded the VDF and searched. This is what I see. Not sure what to think. Is there no delay code?

Here in Idaho, it's pretty much all UP from where I'm at at 2700'MSL.
The car used to live in Albany NY running mainly at ~20-400'MSL. Once we moved to BOI, the MIL would come on regularly. That's when I found using a regular Craftsman OBD1 scanner that BLMs were correcting too far lean outside the allowable norm apparently.
Having already some small experience with LSx OBD2 logging and tuning (HPT), and thanks to folks who call this board home I learned how to crack into ye old $EE. I then reacharacterized what I found to be way-wrong MAF tables, which were the source of major closed loop fueling correction to the lean side. I'll bet it was always there, correction within allowable limits, but just got exacerbated by moving to a high-altitude state moving the corrections over that line. Running E10 in NY likely masked it too, but we are now able to get E0 here in all grades, so using that exclusively also drives CL and BLMs to attempt a true 14.7:1, not a fake 14.7:1 stoich' that is actually 14.1:1 or so.
I'll know more when I get my WB hooked up as to the honesty of the CL method of reporting fueling, and actual resulting PE mixture from my tables. Good clean fun, this stuff.

Thanks for the tip on the patch, I'll look forward to learning more about that!

Here in Idaho, it's pretty much all UP from where I'm at at 2700'MSL.
The car used to live in Albany NY running mainly at ~20-400'MSL. Once we moved to BOI, the MIL would come on regularly. That's when I found using a regular Craftsman OBD1 scanner that BLMs were correcting too far lean outside the allowable norm apparently.
Having already some small experience with LSx OBD2 logging and tuning (HPT), and thanks to folks who call this board home I learned how to crack into ye old $EE. I then reacharacterized what I found to be way-wrong MAF tables, which were the source of major closed loop fueling correction to the lean side. I'll bet it was always there, correction within allowable limits, but just got exacerbated by moving to a high-altitude state moving the corrections over that line. Running E10 in NY likely masked it too, but we are now able to get E0 here in all grades, so using that exclusively also drives CL and BLMs to attempt a true 14.7:1, not a fake 14.7:1 stoich' that is actually 14.1:1 or so.
I'll know more when I get my WB hooked up as to the honesty of the CL method of reporting fueling, and actual resulting PE mixture from my tables. Good clean fun, this stuff.

Thanks for the tip on the patch, I'll look forward to learning more about that!

Has this exposed any kind of kickdown delay constant? In B-body applications, the 4L60E is significantly more responsive to a kickdown in the 9C1/Impala SS applications, than the Roadmaster or Fleetwood applications. And I have a Roadmaster where the kickdown delay is maddening. I just got this 96 Roadmaster so my head is spinning as I figure out what my best tuning options are (very limited if I stay with the 96 PCM, I know).

EDIT: I loaded the VDF and searched. This is what I see. Not sure what to think. Is there no delay code?

I have labeled way more in this coming up release, you might just find the answer your looking for.