BigEvo908

....

BigEvo908

All of a sudden after my car started registering 36 counts of knock. The tune on the car was a break-tune for 2.3l stoker, and was fine. But now when I go past 140 load I get very high knock. I've also noticed that when I log timing advance is at 30* across the board. regardles of what in my timing map it's showing 30* in evo scan and on my op2.0 ad card. I checked for boost and exhaust leaks and fixed the exhaust leaks, I tried to pull timing and it has no effect. It weird because everything was working fine then one day my CEL for knock started going crazy. Any advice? I don't believe its phantom I believe the high knock is cause of the timing advance. What would cause timing to act that way. I'm tired of an evo driving in vacuum. It's like dating a hot pornstar and only be allowed to go over the blouse.. please help!!

evo9gtx

Ok so here's the issue and hoping someone may help me figure this out because it's really depressing me just put new head gasket new head studs new fp black turbo new cams new timing on an 05 Evo 8 gsr and was going to get car update on the tune because of the new cams and turbo and what not but the idle is staying lean on the AEM wideband guage and the sensor is good we tested to see if the sensor was bad but it's not. Tscomp is the one helping me retune it but we can't get the idle afr's to run 14.7-15.3 like normal does anyone had this issue and figured it out please help me out this is so depressing the car runs great and sounds great but leans out on idle and cruising speeds all the way lean.

jayjay2892

here is my download from my car ecu it wont open in ecuflash mi ecu id is 23520009 and all I get is this:
[02:59:03.458] Kernel Type winnt
[02:59:03.458] Kernel Version 6.3.9600


[02:59:03.458] CPU x86_64


[02:59:03.458] Product Name Windows 8.1


[02:59:03.458] Product Type windows


[02:59:03.458] Product Version 8.1


[02:59:03.458] Qt Version 5.6.0


[02:59:03.458] Qwt Version 6.1.2


[02:59:03.458] QwtPlot3D Version 0.2.6


[02:59:03.458] Boost Version 1.60


[02:59:03.458] FTDI Library Version 3.02.11


[02:59:03.458] Openport J2534 Library Version 1.02.4798


[02:59:03.489] 67 memory models read.


[02:59:03.489] scanning for metadata models in C:/Users/stephanie/Documents/Jay/EcuFlash/rommetadata/mitsubishi/evo


[02:59:03.645] 148 ROM metadata models scanned.


[02:59:03.645] checksum module "subarudbw" loaded.


[02:59:03.645] checksum module "subarudiesel" loaded.


[02:59:03.645] checksum module "subaruhitachi" loaded.


[02:59:03.645] checksum module "mitsucan" loaded.


[02:59:03.645] checksum module "mitsuh8" loaded.


[02:59:03.645] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.


[02:59:03.645] patch module "Mitsu CAN RAM Parameter Logging" loaded.


[02:59:03.661] flashing tool "wrx02" loaded.


[02:59:03.661] flashing tool "wrx04" loaded.


[02:59:03.677] flashing tool "sti04" loaded.


[02:59:03.692] flashing tool "sti05" loaded.


[02:59:03.692] flashing tool "mitsucan" loaded.


[02:59:03.692] flashing tool "mitsukernel" loaded.


[02:59:03.692] flashing tool "mitsukernelocp" loaded.


[02:59:03.692] flashing tool "mitsubootloader" loaded.


[02:59:03.692] flashing tool "shbootmode" loaded.


[02:59:03.692] flashing tool "shaudmode" loaded.


[02:59:03.708] flashing tool "subarucan" loaded.


[02:59:03.723] flashing tool "subarucand" loaded.


[02:59:03.739] flashing tool "subarubrz" loaded.


[02:59:03.739] flashing tool "subaruhitachi" loaded.


[02:59:12.195] opening rom file C:/Users/stephanie/Documents/Jay/Jay lancer/read_image.srf


[02:59:12.226] using metadata XML ID 23520009 from file C:/Users/stephanie/Documents/Jay/EcuFlash/rommetadata/mitsubishi/evo/23520009.xml


[02:59:12.226] using metadata XML ID 23520009 from file C:/Users/stephanie/Documents/Jay/EcuFlash/rommetadata/mitsubishi/evo/23520009.xml


[02:59:31.794] opening rom file C:/Users/stephanie/Documents/Jay/Jay lancer/jay basemep.bin


[02:59:31.810] 131072 byte image read.


[02:59:31.810] using metadata XML ID 23520009 from file C:/Users/stephanie/Documents/Jay/EcuFlash/rommetadata/mitsubishi/evo/23520009.xml

BigEvo908

what year evo?


has it been flashed before?


try loading this xml file in "C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo" and then open.

BigEvo908

jay
ok I see what's going on here you have an eclipse 98 gst with a ceddy modded rom flashed to it. 23520009 is an older version. go here and check out the newer versions. let me know how this works out for you. good luck


http://ceddy.us/h8-ecu-wiki/roms-ecuflash-defs/


P.S. you could probably flash back to a stock 98 eclipse rom but it wont have the mods. if you decided to do that you would have to copy over you maps. fuel,timing,boost,etc.

JArnold

Hey guys, I am trying to figure out how to log Mivec timing (06 mr). I've tried evoscan but only get 72.. I added the new log item but not sure what I did wrong.. all of the suggestions that I have found were for previous versions of evoscan.. seems like a lot has changed.. I can log the ace Ecu but not at the same time as logging efi? If that makes any sense..

Rerolling

Is it possible to have the fuel map in lambda, i found a reply to this question, but i can't get it to save
is it possible to log the aem uego in lambda it logs in afr and it will log lambda with the decimal point in the wrong place

rosuegk7

iTrader: (2)

I cannot get EvoScan to work for the life of me. I can read my rom just fine with EcuFlash but when I go to datalog, it connects to the ECU but the values are either all 0 or jumping all over the place. I have tried EvoScan 2.9, 2.8 and 2.7 with two different laptops (windows 7 on MBP and Windows 10 on a dell). I have also tried setting the baud rate to what appears in the MUT2 from my rom (25000).

I have tried reinstalling the software and drivers multiple times each to no avail.

In EvoScan I can make the actuators work but I can't view the DTC or read the ECU.

I am using a tactrix 1.3U cable.

Anyone have any ideas on what to try?

Should I try finding an old school laptop?

Thanks!!!

Update - This thread fixed the issue!

mr.k

What did you do from that thread? I tried to reinstall the drivers and do the zip file, yet I am still getting the same results that you were having before.

Se7ve

Has anyone gotten Evoscan to work with an OBDII bluetooth module?

Bmurray

iTrader: (5)

So I am trying to adjust my idle using Evoscan. I can log the car, check DTCs, etc etc. But everytime I try to go into Speed Adj. Screw Mode, the lights on the dash flash like it's connecting then just says "No Response form Vehicle ECU". I have tried uninstalling and reinstalling evoscan, didn't work. I am using a Tactrix 2.0 cable that I purchased brand new. This is for my Evo 9.

Ryan4dc

iTrader: (4)

Sorry if this was asked before but is there a way to get the tables resized so I see more then a single number instead what the actual value is? I cannot see the immobilizer code to transfer to the new rom.

Silva 77

Hy Guys! I bought an EVO5 from England with evo8 ECU. It's tuned by somebody, but I don't know who. I really loves my program, but I think the difference between Our and UK fuel is makes some knock in my mid range. ( I want to change the ignition timing at these points) But for some reason I can't modify and watch my tables with the EcuFlash. I just can saved it.
Somebody can help me about this? I don't want to reprogramming all my car with a different tuner (I cant trust anyone near my city).

My ROM: https://drive.google.com/open?id=0B-...G94Qk1JZGEtcGM

Thank U Guys!

Arlo

Hi All

I posted request for a working "58010005 2012 Mitsubishi EvoX Mode23 Golden.xml" in the ecuflash section. I believe I added the ROM number to reference it.


It's for EvoScan 2.8. The ones I've found will not open and EvoScan does not see it.
I'm getting Line and position errors in an xml editor. Where other xml's open in Windows xml editor, it shows blank. In Notepad it will open.

My tuner is secretive about his xml's and I'm trying to work with him to get accurate logs.

Two tuners and I get surging still. Boost tuning info I see references mostly for an Evo IX (mine's an X) and terminology is explained a bit confusing. And yes! I'm reading until my eyes hurt.

So why won't this xml open? And why won't EvoScan see it when I place it in the correct directory with the others? Do I really need it?

Help!!