I love less cables

Would anything else need to be done? That is, how would I get it to read properly in EvoScan?

Regardless, I'm not ready to do this since I still can't get my Rear O2 Sensor disabled properly

 

I think you will find hooking up the wb will actually fix your P0140 problem...

I will integrate MrFreds rear02 sim eventually - but for now that will fix it..

You will need todo the ECU_2 bit change obviously..

 

Ok, so assuming that I hook it up:

What am I logging in EvoScan to get the AFR?
Do I have to "calibrate" EvoScan so that it knows it is a UEGO, not an LC-1?

I know, newbie questions, but I don't want to go fiddling around if I don't know the end goal.

 

yes you need to come up with a formula so that evoscan knows what voltage represents what AFR.

whats your ROMID and what voltage matches what AFR? (ie 0v = 10AFR, 5v = 16AFR)

I will give you the Eval to put into evoscan...

 

once wired the P0140 goes away
and the P0139 shows up (slow response)

 

Thanks so much, you're a miracle worker!

ROM ID:
52680018

AEM UEGO Values:

Volts Gasoline
0.000 10.00
0.125 10.25
0.250 10.50
0.375 10.75
0.500 11.00
0.625 11.25
0.750 11.50
0.875 11.75
1.000 12.00
1.125 12.25
1.250 12.50
1.375 12.75
1.500 13.00
1.625 13.25
1.750 13.50
1.875 13.75
2.000 14.00
2.125 14.25
2.250 14.50
2.375 14.75
2.500 15.00
2.625 15.25
2.750 15.50
2.875 15.75
3.000 16.00
3.125 16.25
3.250 16.50
3.375 16.75
3.500 17.00
3.625 17.25
3.750 17.50
3.875 17.75
4.000 18.00
4.125 18.25
4.250 18.50

 

ok ill do the patch then... *annoying*

 

So now logger know Real AFR from WB and AFRMap, so it can calculate compensation automatically?
Idea to put in fuel map our destination values and evoscan can automatically calculate values for afr compensation table! This will save a lot of time!

We just need to log current value from "AFR Compensation" map. After this we can write excel script that can fill our fuel compensation automatically.

 

alright you lot - all of you shoo out of my thread hehe

Bob - last page - someone wrote an excel sheet to calculate the difference between map and Actual AFR and then told you what to change where.

personally I would NOT be changing the AFR Calibration map just yet, we dont know enough about how that works! Just tune like you would for CT9A...ie tune the fuel map knowing its not a "target AFR"...

 

Dave. Let me know when I can trest that rear o2 sim patch cel is killin me

I tuned my evo using the cal map, and MAF, its very stable and afr doesn't vary day to day. Now all I need is my E85 and 30-35psi map next week!!!

 

Motec PLM 0v = 7.35 , 5v = 25.725.Is it possible to have a formula for this one?

 

assuming its Linear:

logging the 10bit ADC for rear02:

Eval="7.35+ 18.375*x/1023"

 

OT crap removed.

Naji, unless you want a vacation, stop trashing threads with your anti Zeitronix propaganda.

 

do you need to change the injector scaling in evoscan to the same scaling as your ecu?

i noticed that when you open evoscan it has scaling at 513... where as the evo x is 532. does that make a difference for anything?

 

On Sunday I logged mode23 boost and the ZT2 boost with the medical grade Kavlico 3.5 bar MAP sensor I could not log the rpm with the ZT2 since the wire is not connected. I ran Evoscan and the ZT2 logger at the same time and logged the boost for the same 4th gear run. I compared the peaks and valleys of both boost curves and can confirm an almost exact overlap between the two.

I have compared the JDM MAP sensor to the GM 3-bar MAP sensor on my Evo 9 and they were very close.

Good to know that mode 23 boost is accurate