The above I presume you are referring to Evo9. Because MUT07, MUT3A, MUT12, MUT3E, MUT4A are all valid for pre 1996 Mitsubishi vehicles.

If Load Calculated is deleted, what would users use instead to get the full range of Load values for say a 1996 Evo4?

 

For those of you having problems getting your UEGO to log, I can verify evoscan v2.9.0017 works
Thanks for the tip evoscan.

Now I still have another issue to fix. I can't get Load 1Byte to log.
Request ID in evoscan is 41 so I opened ecuflash, opened my rom, went to the MUT table and changed the value in MUT41 to 0x840B.
I then flashed my ecu with the modified rom and tried logging but it doesn't work, just says 0 all the time.
Is there anything else I need to do?
I'm on rom 88840016.

 

If those are valid for pre-1996 then perhaps rename the entries or create a separaste xml file? Hasn't anyone figured out a 2-byte load address for these ROMs? Or is there no 2-byte load?

 

I tried checking any DTC's with mine since my CEL light is burned out and I got

CHECK DTC's Complete. In the DTC box it says "No response from vehicle ecu" does that = no codes?

 

Anyone can help me out?

 

No, it will say scan complete and the quantity of DTCs found. Try starting evoscan, connecting the cable to the vehicle then switching the key to the on position, with a 10 sec gap between each step then checking for DTCs. Sometimes it has hard time connecting, I know mine does most times.

 

I play hell reading dtc's through evoscan.

 

evo 9-open port 1.3

I never had any problems logging with evoscan from 2.5 to 2.8 but since switching to 2.9 I have this : "Object reference not set to an instance of an object"

Is it because I re-arranged the lines so I have those I use the most on top ?
It doesn't seem to do this all the time, I'm pretty sure it's one or several values that when logged cause this. I tried logging the bare minimum rpm,tp,adv,airflow,afrmap,afr,knocksum and had no errors.

 

I haven't heard this from anyone else. must be something unique. can you log a support ticket on evoscan website, and write which cable type, baudrate, ecu dropdown you had selected, and which items you had selected.. maybe a screenshot could help .

 

Same thing has happened to me. Evo 9 running Tephra 88590715 and using OP2.0 to connect to the ECM. It happens when I log "External Wideband A/F Ratio" and the signal goes lean - basically when I lift off the throttle, my LC-1 goes really lean and times out in a way. At least that what seems to happen in LogWorks. This was never an issue running EvoScan 2.7 on Windows XP, but now I'm running EvoScan 2.9 on Windows 7. I did not run EvoScan 2.7 on my Win7 machine. Also, I don't think I can blame the serial to usb adapter because it does fine when it's in range. Any other ideas?

Thanks in advance.

- Paul

 

I've been getting a FTDI read timeout error -4 with Evoscan v2.7.0070. Even with anti-virus disabled while logging.

Using an HP mini 210-1018 CL

I'm stumped.

Also I noticed that it's initializing at 5 baud. Shouldn't it be higher than that?

 

thx Ill try to test 1 parameter at a time to hopefully pinpoint the problem and make a screenshot when if/it happens.

Like Zman15, it may be because of my LC-1 WB, I'll try not to log it.

Won't be able to give you an update soon sadly, it's impossible to datalog properly these days, we now have between 15 and -2.2°F outside temp where I live the engine oil temp doesn't go above 158°F and it takes an hour to reach it ><

 

2.7.0070? please use EvoScan v2.9.0017

 

Hamish,

I am running v2.9.0017.

Any ideas or suggestions for my problem?

Thanks,

- Paul

 

i cant log any of my fuel trims, only o2 feed back. Mut table is stock.

Im trying to set latencies and scaling on my 1000cc PTE injectors. I tried the ones on the fuel injector thread with no success.