So is that to say that the ROM still to this day hasn't been completely decoded? That sucks!!
The evo5/6 has been to maybe 75-80%, more than enough to get a car running. The 4g93 is maybe 25%, but enough for what the car is.
So is that to say that the ROM still to this day hasn't been completely decoded? That sucks!!
Correct, it used the same calculations of air temp and flow, and rpm, but no longer attempts to put effort into making it stoich/reading the narrowbandQ: When in open loop, the only thing that changes is that the ECU no longer references the 02 sensor, correct?
So I have bit the bullet and have a Tactrix cable on its way ..... CBF buying a wideband just yet but have access to a dyno so I can just use that one for time being .... I haven't finished turbo setup just need to finish stockpiling metal for pipework and mounts, in the meantime, I figure I will use my time and tidy up Mitsubishi's "fine" tuning work and make it as efficient as I can for the time being as its still a runaround Any Idea how accurate the timing is from factory? as fueling will be an easy fix, by comparison.
another thing to add:
Donki, you should get a GM 3 bar map sensor and wire it in to pin 75, sensor ground and ecu 5V, i took this from the tps and mounted it on the firewall. you can then log boost pressure in evoscan! i used a chinese knockoff sensor and working well. dirt cheap on ebay and makes tuning faster even if sticking with a MAF rom.
So I am failing horribly at finding an XML file for the 4g93 (CE generation) if anyone happens to know where it is hiding on the interwebs please speak up! Google has failed me as has Tactrix and EvoScan sites!
Also, need to know how to find numbers to confirm F or FA chip? is it open the case time or is part number enough?
http://auslancer.com/index.php?threads/ce-lancer-ecu-tuning.9142/page-9#post-238603Thanks for the heads up @donki is the definition built into the 1.44 (or whatever the latest version is) so I can find it automatically? and for others wanting to check it is an easy process once you work out HOW to open it! There are 4 tabs (2 Top 2 Bottom) use some "guitar picks" like those used for opening laptops and phones for repairs and then slide it out (I used one of the loom plugs and gently slid it out so as not to damage the plug)
HAHA I hate those things (worked in security too long)I've done the same, guitar picks or 20c coins will also do the job (plus they go *DING* when it opens and it sounds like you win the pokies lmao
@donki You are a godsend I have a definition file! it works it says ALL the right things mostly I mean lancer is what it was made for so I can't really hate on that! next thing is can I use this for the Evoscan as well instead of trying to use Evo stuff that's not 100% accurate. and also I know it's covered elsewhere but I want to triple check I have the info right that I have found AEM UEGO X-SeriesP/N 30-0300 can be run to the ECU for logging so I don't have to do the serial cable daisy chain of potential doom?
So there is some stuff on the evolution forums so I will have to read as apparently they can with their ECU's but that is a later problem.
Right now I am looking at the logs and from and as far as the from is concerned is 513 injector scaling accurate or is that just a standard thing that Evoscan reports unless it gets told otherwise?
Also on Evoscan is it possible to get the XML I am using in Ecuflash (cerom.XML) to work in Evoscan as I cant tell it to use the .XML file as it will only let me change to a .hex file unless I am doing it wrong but there seems to be very little info anywhere as to how to make this all work (or am I being too fussy?)