PE enabled, but not activating (0411 8322)

[woody80z28]

Gotcha. Thanks. Looks like I was editing my post when you added yours. That's the exact kind of thing I was envisioning to get around a PE issue.

[woody80z28]

Great success!

I modified the LRT bin to also disable the MAF and mistakenly flashed the non-modified one. AFR was low 14s. So I looked at it and realized what happened, flashed a MAFless copy and AFRs were in the low 12s. My ~19-20sec "dyno" pull only took 16sec! That's a definite improvement.

So I know I need to do some MAF scaling. Very excited though...cause now I know I can make changes and see results.

Thanks to everyone who helped out. I would not have figured this out on my own.

[LRT]

....

[woody80z28]

Thank you. All input is appreciated.

We're "essential" so even though NY is mostly closed, I gotta go to work. But we're on 4 days right now cause orders are slow. And today is beautiful! So I just got back from a drive.

Tires: yes, I went from stock 245s to 265s. What's the TOS? EDit: nvm. Trans output shaft speed.

Fans: That old bin is from when I was setting up my fans. My operating temp was only hitting mid 160s, so I set them there just to be sure the harness worked. It's set to 192 now. I actually replaced the tstat with a 180, thinking the previous owner may have put a 160 in, but it didn't change the operating temp. Warmer days now have put my operating temp in the mid 170s, but my gauge is always about 185...even when the datalog and my handheld read 160. Strange. I don't see an added bypass anywhere.

Spark: I made those the same to simplify tuning like my obd1 Beretta. Maybe that's not ideal.

I just logged another bin where I reactivated the MAF after adding 10%to the g/sec chart. That put my wideband in the mid 14s at WOT. I'll make the fan changes, etc and try yours, too. Edit: Looks like you added more than 10%. Which is needed.

I'm working with Kur4o to get a decent solution to datalog with TunerPro and the obdlink. We're adding KR logging, but that showing 1.5deg the whole time, so something needs adjusting. That whole deal has been a challenge, too.

Going to flash and test it now.

[woody80z28]

Hmmm. I tried that bin out and it gave an MIL (P1336 Crankshaft Position System Variation). It was noticeably less responsive. But it had to have entered PE (13.4 at WOT) with the open loop table set at stoich up top.

I put the last tune in just to be sure it wasn't a sensor problem and the MIL went away and the throttle response came back.

[LRT]

....

[kur4o]

I am almost sure that the case relearn data is stored at the eeprom region of the bin 4000-8000 area, which can be overwritten only in clone mode. Under normal programming it shouldn`t be updated. Maybe the error is caused by some other settings that affect this DTC.

LRT you have lots experience with the ls1 code. It is completely off topic but have you managed to figure out the routine that sends data via the ALDL bus on the ls1 pcm. I am trying to find it and make a hack that will enable the pcm to stream custom data via aldl for logging essential data. I looked at a lot of dissasemblies but I am not even close to figuring this out.

Confirming the PE mode can be done by looking at the stoich target the pcm use. If it is stuck at 14.7 all the time, than there is indeed no PE enabled.