^ did you have the wideband ticked in evoscan - that will cause your drop-off problem if its not setup right...

 

Wideband was not ticked.

I have since gotten everything to work on a different laptop using Vista. Wideband is also working with this laptop on Evoscan.

Did a 3rd gear pull and logged it. Scary readings.

Knock in the teens, AFR's in the 13's and 14's throughout the log.

I'm thinking it's a fueling problem: faulty fuel pump, dirty injectors, clogged fuel filter, or even bad spark plugs (incorrectly gapped or incorrect heat range).

Any advice about what to look for would be great.

Car is running stock boost @ around 16/17 psi, TBE, and intake. I don't see why it would run so lean and have such high knock counts unless something was wrong with one of the fueling components.

 

post up the log.

there are a couple of version of evoscan where the LC1 readings (from serial) were delayed or wrong.

but if your knocking as well, then yeh - probably real problem :|

 

http://www.2shared.com/file/5340867/...13_185306.html

http://www.2shared.com/file/5340880/...13_185944.html

Those are the two logs.

What do you suggest?

 

same issue I was having...

 

dude, why are you selecting OBDII? stop tinkering and leave at the defaults, lol. Select EFI like everyone elses screenshots.

 

At the time Evoscan was not working at all. I was merely showing a screenshot with OBDII selected where it at least said "connection successful".

I did a clean install on a Vista laptop and got it to work like normal.

Leads me to believe something was wrong with the .NET framework I downloaded for XP.

 

^^^ ive got my own problems man, im glad yours is working but i still cant logg worth **** lol.

 

As a work around, can't you just log AFR in Logworks, then log timing and knock in Mitsulogger? Not quite ideal, but you can get tuning and I usually adjust one thing per-run.

MB