After weeks of importing ALDL cables, Pocket programmers, 2732a chips, Eprom Erasers etc etc etc I am now in a position to burn my first chip.
Being a "canny" Scotsman I have left the car completely stock until i have logged a few stock runs, I have done this for comparison and to evaluate change.
Last night I data logged using WinALDL for the first time and did not get what i was expecting..........

KNOCK COUNT / BLM / O2 / INT TABLES

The Journey logged was a 10 minute drive, I had a minute or two each end in town but the majority was on the Motorway.
I was expecting 128 BLMS across the board but didnt get them, is this the first thing i should be trying to correct ?


Notes - previous owner has disconnected and plugged A.I.R tubes to the exhaust manifolds.
Car averages 250 - 270 miles to a full tank of petrol,even babying it (I consider this fairly ****ty mileage)
TPS low code, scan shows 0 volts until i initially move accel pedal then scan shows TPS in range and OK.

 

What software were you using to generate your knock counts and BLM readings, or did you do those manually just using a table? I'd like to know. Thanks.

 

datalogged into WinALDL

saved the main 4 tables (BLM - INT - KNOCK - O2) at the end of the journey.

imported them into Excel, cleaned them up and made them look nice... made all 4 winALDL tables into one worksheet.
You can use conditional formatting to highlight over 128s as 1 colour and under 128 as another..

cut and paste the 1 master worksheet into Word as a table.

A bit more tidying up in Word to set page sizes etc.

saved as HTML.

phew........

 

Nice formatting.

Rarely is any engine just going to happen to be at 128s. There are way too many variables for that to happen. Experimenting to get 128s is a good way to get your feet wet.

The TPS code is based on voltage and it sounds like your scan tool is using percent. You need to hook a meter up and see what it's doing voltage wise.

A heavy v8 powered car is not going to be an economy winner. If you need more the low-mid 20s, MPG, your in for lots of work, and probably some disappointment.

 

Well this is my newbie line of thinking....
please tell me if I am going to kill my car !

BLMs are all low, this means that the ECU is subtracting fuel.
The inbuilt VE tables + the trim table adjustments that make up the Injector PW are resulting in a rich feedback reading from the O2 sensor.

Option 1. as the readings are all low then reducing the BPW could be used to correct.
However BPW is a figure calculated from engine cylinder size and injector flow and I have not changed either of these, so on this occasion disregard.

Option 2. the VE table values are simply not correct for this particular engine.
Amend the VE tables based on the BLM figure values, as the engine is not able to burn all the fuel being injected then the VE table values should decrease resulting in a shorter PW, resulting in less fuel going in.

Option 3. something "mechanical"
The base timing is incorrect........The knock count is good, all low, so maybe the timing is too retarded
The O2 sensor needs replaced... The O2 values however do look consistent and range from 0.1 to 1.
Fuel pressure too high resulting in more fuel being injected for the same PW....Unlikely as normally fuel pressure would drop due to wear / fuel filter blockage etc.
Possibly blocked air filter....surely not enough air has same result as too much fuel.

Option 4. some combination of all of the above.....

First steps
Double check the base ignition timing, set it to zero to match ecm value.
Check air filter/ slap on that open element.
If no change in BLM after these then adjust VE table based on values in BLM cells.

Note to Grumpy,Rbob etc - If you are LOLing at this point please explain why.........
Note to self - It will be worth it in the end, better to be "green" with Fuel Injection than "yellow" and slap a carb on it.

 

I'd say the data looks normal. The slightly low BLMs may be caused by cannistor purge (CCP). Can play with the VE table is an area or two and see what can be done. With the air removed I'd also disable it in the bin. Can temporarily disable the CCP and see what happens.

The knock stuff looks normal too, but not good. The 9 count block is probably from shutting the engine off. Common to get a lot of counts on crank & shut down. Some of the counts in the high map areas could be the ECM forcing it to test the knock detection system.

The general random knock may be caused by low octane fuel, carbon buildup, advanced timing, a mechanical noise, or random false knock.

Is it possible that the cat is starting to plug up?

RBob.

 

Man that sucks that it takes so much to put the data in that form, because that's exactly what I'm looking for and nothing I've seen does it easily.

 

First, adjust the TPS to .54 volts at idle.

Also, if it's one thing that I learned, don't disable CCP ! You will be stuck in cell 4 and you really should be oscilating cells to better collect date and tune more areas of the .bin

Will VEMaster work on a TBI setup? If so, use that ! You will also need datamaster to use VEMaster.

 

Asking guestions about tuning ain't something I laugh at. I hold a certain reverence for those the ask rather then immediately jump to conclusions.
It's usually always a matter of being #4.
You need to have the base line tune, dead nuts. New plugs, cap, rotor, fuel filter, air filter, wires, etc.. Or you can be chasing mechanical ills. Then all the adjustments set to spec..

From where and tear, and even just variances in how the fuel is blended you can see BL differences.

I would refrain from making universal changes, for just trying to taylor the BLs. You might try it as a, for future info., this is what happens thing, but I wouldn't consider that a way to properly tackle your BL problem.

It looks like you have a good handle on things.

 

JamesBob02 - if you email me your saved winALDL tables i can run them through for you, might be after xmas though.

1bad91z - I have a post on the TBI board asking if anyone has got TTS Datamaster running OK on a 160 baud LO3 F Body, so far no replies...... The Tunerpro guy - magnus - has sent me an email saying 160baud ALDL logging is in his TunerPro 3 month development plan. so for the time being its good old WinALDL.
Can you please expand on your "oscillating cells" theory - sorry to say it but I dont fully understand what you mean.

RBOB & Grumpy - Thanks for all the help. I will be doing more testing/logging over the xmas, new year period and hopefully doing my first "chip burn" soon after.
I have the usual first few performance mods to make - Open element / Headers / Perfrormer RPM intake / LT4 cam etc and i want to get a grip on the tunercat/tunerpro software as well, so plenty more reading to do.

Once again thanks for all the help.