XDF question

bezerk

New member
i have a Q about this, for code 59 there are for example 2 XDF files, 1.1 and 1.5. now let's sat my bin in the truck has been put on by 1.1, if i now grab the bin with 1.5..does that do bad stuff?
 

JSM

Active member
Re: XDF question

Nope... the bin info itself is the same, the XDF is just how WE HUMANS look at the info on it, 1.5 had a few fixes and correction in how WE look at things, the truck ecm knew all along how to read it.
 

bezerk

New member
Re: XDF question

i thought the same thing. but was wondering since tables were changed,.
thanks!
 

MRKING

New Parts for Old Trucks
Re: XDF question

Are you referring to tuner pro rt v5 or the older one ?

I tried using TP RT v5 , but with the def files i have i cant get it to work properly and am just using the older version for now .You have any luck with it bezerk ?
 

bezerk

New member
Re: XDF question

referring to the xdf file you need to open up in tunerpro as well as the bin.
 

JSM

Active member
Re: XDF question

Was the BARO calculation a part of this fix?

Paul would know more, but the baro issue is more of a GM code issue. The code tells the ecm to grab the map sensor reading RIGHT before you crank the key, before the engine calls for any air. The problem is that doesn't always work and it can grab the reading after the engine starts grabbing air, messing up the reading.
 

TYTILIDIE

METH HEAD
Re: XDF question

Paul would know more, but the baro issue is more of a GM code issue. The code tells the ecm to grab the map sensor reading RIGHT before you crank the key, before the engine calls for any air. The problem is that doesn't always work and it can grab the reading after the engine starts grabbing air, messing up the reading.

You know I never knew THAT was the problem, just knew there was one. That explains A LOT of things. Would turning the key and letting it sit for a few seconds do any justice to that issue?
 

turbodig

Active member
Re: XDF question

You know I never knew THAT was the problem, just knew there was one. That explains A LOT of things. Would turning the key and letting it sit for a few seconds do any justice to that issue?

It's actually kind of funky how it does it....

The ECM is fast enough to see the voltage rise as you turn the key on to apply ignition power.
When it sees this, it considers it a "key-on" event, and reads baro.

The problem with this, is that during cranking, if your battery is a bit weak or your connections dirty, voltage can drop down into that "key on" range. This causes another BARO read, this time while the engine is cranking and there's a bit of vacuum there. Voila, funky BARO reading.

I've been working on fixes to try to insure that BARO read happens only when the key is on, but the engine isn't turning. It sounds simple enough, but due to the timing at which the BARO routine runs, it's tough to tell sometimes.

Turning the key and holding it will get you a good read, but it may get "re-read" by another voltage event.
That's the Wheaties-Whizzer, right there.
 

TYTILIDIE

METH HEAD
Re: XDF question

It's actually kind of funky how it does it....

The ECM is fast enough to see the voltage rise as you turn the key on to apply ignition power.
When it sees this, it considers it a "key-on" event, and reads baro.

The problem with this, is that during cranking, if your battery is a bit weak or your connections dirty, voltage can drop down into that "key on" range. This causes another BARO read, this time while the engine is cranking and there's a bit of vacuum there. Voila, funky BARO reading.

I've been working on fixes to try to insure that BARO read happens only when the key is on, but the engine isn't turning. It sounds simple enough, but due to the timing at which the BARO routine runs, it's tough to tell sometimes.

Turning the key and holding it will get you a good read, but it may get "re-read" by another voltage event.
That's the Wheaties-Whizzer, right there.

Interesting. Hopefully this gets resolved some day. I am assuming this to be a good reason why every now and then the wideband will seem like its a dirty dirty liar?
 
Top