12.26 is not a data glitch, it's a MAF glitch. If you use the monitors and watch the entire log you will find data glitches, I did not note them.
Unless your pumping the gas when you accelerate? Your TPS is faulty...
Printable View
12.26 is not a data glitch, it's a MAF glitch. If you use the monitors and watch the entire log you will find data glitches, I did not note them.
Unless your pumping the gas when you accelerate? Your TPS is faulty...
I'll have to look at that MAF glitch. MAF has 6(?) tables, if they don't start/stop with the same number it can cause issues. The definition had a limit set (which you guys helped me figure out before) on each of the tables, and I'd make the change, save it, and not notice that it reverted back to a lower number until after some time. I may have been dealing with that at that time.
On the TPS, if it was in the 35-45MPH range, I may have been manipulating the throttle trying to find a spot that I could keep the truck accelerating. The problem is so consistent, if I can find my spare, it will be much faster to simply swap the TPS to verify or eliminate the TPS as the problem. In these cases, I always hope it is the hard part. New/good part, no problem. :)
I was looking at those MAF tables, and each one has a differant scaler? So it changes from one table to next and scaler changes?
scalar has to change, or else resolution is crap. the newer masks use a scalar and offset to make a 0-512 gram/sec range with excellent resolution while only using 8-bit values.
Old MAF sucks. lol
But yes...when you change the engine components you may hit the scaler limit, so you have to adjust the scaler to be able to adjust the table upwards. It took a fair bit on mine to get the tables to be able to get close in fueling, at least on the low end. I don't get real high on the airflow numbers, highest I saw on that log I believe was about 118 gms/sec, but I'm pretty certain I wasn't beating on it.
I'm thinking those TPS spikes correspond with how bad it ran trying to take off from a stop. I had to modulate the throttle to get it to accelerate. I'm going to have to pull a new log and see what it looks like. Those MAF dips are right where the tables split, so I suspect that was another issue. Funny thing is, I never felt them.
That's a cool tool, I'm going to have to use it more. I'm also going to have to get a datalog that is based on the current bin, see if anything has changed for the better. When it's pulling through 35MPH TPS is not acting goofy from the monitor reading. I still don't see anything that would represent that problem in the 35MPH range?
I'd work on enabling it if I knew how to!
I was thinking it was disabled due to the code 21, but it's disabled before the code set. I compared the old bin with a stock bin, I don't see anything with difference tool, nothing under learn, control, or BLM that seems like it would be used to disable. Is there something like that in $42?
Yup!
Luckily I've never had to work on $6E...
Like I said, I've got a PARTIAL log with the "new" bin/XDF, when I can get back to it, I'll see if learn control is still showing disabled. The other XDF had a ton more detail, hopefully as basic as this XDF is, the difference will be apparent quickly.
Got the log. Code 21 is gone. So something in the other bin going on there.
Decel enlean still disabled. No AIR turnoff in this XDF and it's causing engine to go lean. Either I learn to add things to the XDF, or I get off my rear and just swap the '727 to be done with this. Learn control disabled. Can't find anything on learn control online, so not sure what is going on there...something to do with being in ALDL mode?
Attached is what little data I got before the ECM froze again.
If you open 2 instances of TunerPro you can copy one paremeter from a XDF and go to other and copy it in...
Apparently learn control showing disabled is normal. BLM's are moving, so things are ok.
DFCO is going to take more time. Should be working, going to have to check parameters again, everything I saw looked like it should be working.
I saw the button to open two instances of TP, so I will try that when I get the chance. I can't believe AIR is causing this large of a problem (I understand the O2 offsets it uses), but looks like it correlates to the areas I am having problems in.
As opposed to opening two instances of tunerpro, how hard is it to simply strip the AIR routine out of the bin? Or at least enough of it so it never worked?
I don't see myself ever running AIR, if it's not overly complex to do (vs adding the parameter in the XDF which is apparently easy), it would probably be beneficial for me to learn how.
Anyone willing to walk me through it, or point me to a post basic enough for me to grasp?
So the air parameter is in one xdf and you want it in another xdf? I help you add them all together to make a better xdf, way easy compared to stripping code from a bin...
Open TP, load one xdf and make TP a half window. Go to Tools, Custom Tools and New TunerPro Instance, when it opens load the other xdf. Click on the parameter you want to copy and move to other xdf, while it's highlighted right click and Copy XDF parameter to Clipbaord. Move to other instance of TunerPro and right click on a parameter where you want to add the new one and choose Paste XDF parameter From Clipboard.
Seriously it's to easy...