vmrevo9

iTrader: (33)

so i'm going to try this when i return home. im trying to set it up now so that all that will be left is to remove the pin from the ECU plug and insert the pin from the LC-1, reflash the ecu and adjust the actual values in EVOscan since i did the ones shown off of memory and hopefully it will be operational.

can you please see the attachments and advise me if i am missing anything. i have Evoscan v2.6 and i have 2 different ECUFlash versions. i use version 1.34.1435 to flas my car due to my old cable and i also have version 1.42 just in case.

thanks in advance!

CRONZ305

iTrader: (1)

the request should be 12 not 3C. Im not sure what 3C is..... Anyone????

correct me if im wrong guys

evo8426

iTrader: (27)

It is 3C on mine, been using this address since installing the wb into the ecu.

CRONZ305

iTrader: (1)

/\ you running tephra v7??

evo8426

iTrader: (27)

Yes, I ran it on V7 MAF and currently run it on V7 SD 2.0

CORZA

iTrader: (3)

Hi Team,

Having some issues with this lately. Story is it was working then I had to rebuild my computer and since then it does not read correctly. Here are some screen shots of what I have tried. I have also tried both 12 and 3C request addresses.

It is an evo 7 ecu running Tephra V7 90550701. Have checked MT addresses etc and all look good in the ROM.

TurboTravis

iTrader: (6)

Please help a tuning dummy..lol.

Basically, a friend helped me set up my FJO wideband to read thru the rear 02 a couple years ago. I reloaded windows, and had to reload ecuscan, therefore I lost the 'function' equation...

The FJO reads from 10.0-20.0, and you can actually program the voltages. It has these defult choices..




And this is the custom table...



I verified with a DVM that it's set up right now to where 20.0=5V. With that said I'm assuming that 10.0 is 0V.

Here in a little while I can download what I have it programmed as...

In the meantime, assuming that I know that 20=5v and assuming 10=0, can someone give me the function exactly as I need to type it into evoscan?

m.al-hassawi

hello everyone
please i need some help, first its an evo 9 USDM ROM ID 88590014 am using the Zt2 the early 2009 i connected the (purple wire) to the rear O2 sensor signal pin in the ECU, i am using tephra mod V7 i copied patch (<table name="Rear O2 (ADC 0A) RAM variable" category="Rear_02" address="3817A" type="1D" level="1" scaling="Hex16"/>) i copied it for Jack_of_Trades to my evo9base.xml file. the 1D table is showing i change MUT 12 to (0x8409) and the 1D table and in evoscan i chaged the request ID to 12 but no data was available on evoscan 2.9. my original request ID was 3C, when i let the same request ID (3C) i can available data but the numbers dont make sense. i try so many formulas was taken from the thread still no sense from the data. when i set my eval=X some nmbers shows on idle between 130-140 and the min and max numbers i got on WOT was 25-255 rich is 25 and lean is 255.

now i dont know whats wrong the address="3817A" , the formula, the MUT table or the request ID ?

please need some help

thank you

EvocentriK

Do you just want to log wideband o2 through pin 73? MUT3C is usually what you want to log.

Patched like you did isn't it MUT08 to log from? https://www.evolutionm.net/forums/5636074-post64.html

m.al-hassawi

yes i only want to log AFR from the external wideband, do you mean this patch isnt the one i need? there is another patch to copy? and which formula and which address do i need?

EvocentriK

You used:

<table name="Rear O2 (ADC 0A) RAM variable" category="Rear_02" address="3817A" type="1D" level="1" scaling="Hex16"/>

So you then need to:

Use this and change the value to 8409 in ECUFlash (don't forget to type in the "0x" first so ECUFlash knows its a hex value...so type in 0x8409 and you'll be all set):

In the link it says if you do that:

This is MUT request 08 so make sure you use that with your Evoscan table.


Thats the way I'm reading it. I don't have a 9 so haven't had to patch the rear o2.

m.al-hassawi

ok after using this patch i have to change MUT08, request ID and the rear O2 1D all to 8409?

EvocentriK

Link says there is only 1 rear o2 1D field to alter to 0x8409, just give it a try see if it works.

m.al-hassawi

I changed the rear o2 1D to 0x8409 but i still have the same data. then i changed the request id on evoscan to 08 and i got 166 fixed. the number wasn't changing even with throttle. thats without a formula. then i changed the MUT08 to 0x8409 the reading became a fixed 255.
so what do u suggest i do now?

EvocentriK

Not sure, never been in this situation with a 9. If you log 3C, you were getting a range of values but none were making sense when you applied the formula?

What made you change from logging 3C unpatched to patching?