Just got my 1.3u and evoscan 2.7....logging Evo 8 and my tps is not reading anything, knock sum is 35 to 55 and timing is 6-22......

What gives.....been searching bit can inly find Evo x stuff

 

ive been reading merlins tunning guide. Its helped.

I recently had no fuel trims being logged. Turned out i had a faulty o2 sensor (on the o2 housing)

Have you checked your TPS sensor? Any check engine lights?

 

Anyone know whether to get the 1.3U or 2.0 for an evo 8 JDM? as i mentioned previously:
http://www.evoscan.com/mitsubishi-su...bd2-can-cables
why cant you live tuning/maping with the OP2.0??? Can you still bleed AYC/ACD with the 1.3U and 2.0??? I really dont know which to buy but im leaning towards the 1.3U atm

 

Trying to add periphery to the XML, but when saving, it's saying "Access Denied"

Any idea what could be preventing me from saving it? Thanks in advance.

 

Ecuflash keeps giving me a unexpected error when trying to open. I've tried various versions with no luck . Can someone help me out? I need to figure out why my stock ecu won't start for inspection.

 

Thx for fixing the disconnect bug related to lift off/high afrs in the 2.9 initial release.


Now there's something else in the latest 2.9.0019 altough less problematic.
evo IX
tephra v7
openport 1.3?
MUTIII EFI

If you try to log "load calculated" a window pops up asking you to place the "injector scaling" parameter above load as if the programm expected it to be another parameter/request line like speed,tps,rpm,timing advance etc...
but scaling is in a separate "cell" and I can't move it around ?!?

I don't need load calculated but I wanted to test if everything was working in 2.9

 

I just purchased a 1.3u cable and downloaded evoscan 2.9 along with the latest ECU flash and I can not for the life of me fifure out how to get it to work. Here is what i have done so far.
1. plug in the 1.3u cable in to my OBD2 port along with my reflash connector.
2. open upp ecuflash and click download rom

after it downloads the ROM I click on fuel or any other table and the computer immediately says ECU flash has stopped working and shuts it off. I've opened several tickets to try and figure out why it will not work. I tried the latest response with no success. I was told to download the XML files from http://www.evoscan.com/roms/mitsubishi click check all and download the xml zip button. I then added this to the rommetadirectory folder. After doing this I had the same issue. I noticed I was suppose to overwrite all the files so I deleted other files in the directory and tried to unlock the zip and my computer says that it is unable to create a specified directory and to make sure the address is valid. That was as far as I was able to get with the tickets I have submitted and I am tired of creating new ones and waiting for responses. I just need some help to get me started. any insight on my issue?

 

Dude you're a legend bug finder.. haha. you a right on, I better fix that and do a v2.9.0020

 

that can happen if you are using old rommetadata xml files. download the latest for your vehicle from www.evoscan.com/roms/mitsubishi

or let me know your romid, and I'll get it off that webpage and attach it here for you.

 

Any help or the issue I posted? I can't go further with anything until this issue is fixed because I can't even see my ROM or view any tables not make adjustments :/

 

Does anyone have any help or advice for the issue I posted a week ago? :/

 

Completely uninstall ECUFlash and reinstall.

If that doesn't work, try using different versions. I believe older versions are available from evoscan.

What are the specs of your computer?

 

sounds like an error in the xml can you post rom here

 

I have tried uninstalling and reinstalling twice with no luck so I'll try an older version. I just bought a computer mainly for this which is a dell. Its running on windows 7 and has 6 gb of ram and 500 gb of hard drive space. I figured it would more then suffice to use for tuning.

And I'm still a little new to this so are you referring to my ROM id? I'm not sure what it is exactly because the program shuts off before I can get any info. Unless there is a way to find out using Evoscan? Thanks for the help guys! I'm going to try and older version after work today and I'll let you know how it goes!

 

yeah the rom id, if you can post the rom here i can tell you what it is and then send you a fixed xml