The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

Please Support Rix Racing
Please Support STM Tuned

ECUflash ECUFlash, Evoscan. A few things I need clarified

This site may earn a commission from merchant
affiliate links, including eBay, Amazon, and others.

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

codydsm1

10+ Year Contributor
53
6
Oct 15, 2011
Loveland, Colorado
A few months back i heard about ECUFlash and you could use it along with EvoScan to tune and log with help from the Tactrix cable/flash plug. I have recently downloaded ECUFlash, paid the 25.00 bucks for EvoScan got the 2.0 cable and flash plug, Donated 5 bucks to ceddy and got Rom 20550011.

Now a few things I'm still not clear on. I've been watching videos and reading threads like crazy but still cant find much on it. When ceddymod is downloaded is there anything else that needs "patched" into ROM before you can use it? I keep seeing videos about the 1byte load. From my understanding it started with 1byte, then went to 2byte and now its to 1byte load, correct?

Now the videos I've seen I see people copying and pasting code into their ROM to go from 1byte to 2byte and then changing an equation in EvoScan I believe or maybe ceddy ROM to something like 1.2*255? Is this something that still needs to be done or has this been updated in newer versions?

Another thing, the MUT table, will the hex values need to change to accommodate the change in code. If it does need done, where would I find those hex values? I find a ton for Evo ROMs. By adding the code it lets you pass the 160 load limit? Is this just for ECU limit or is this the reason my fuel maps and timing maps top out at 160? Or would just getting the big maps take care of that issue?
Thanks in advanced as any info here will help
 
no disrespect taken. you've been very helpful. no local help available that for sure.....ALL dsms around here all run link and tuners have no idea what I'm talking about when I say ecuflash. it's a one way road around here. IF (and that's a big if) I figure this out it's going to be a huge door opening for local dsmers who hate paying someone 500 bucks to hope it's a good tune. again i appreciate your help i just hope I can solve this and solve for others who are having this issue with unresolved threads...just frustrating is all

i have actually modified XML files and added tons of optimizations and to this day i still kill an entire saterday morning and a 6 pack of beer every time i do a new set up of ecuflash and evoscan. just read, follow the steps, cuss a lot, drink some more, then start from scratch and try again. eventually you will catch an AH-HA! moment and it will be smooth sailing.
 
I've ditched all my black box ecu and gone to evo in everything, but I was just logging a customers car the other day on v2.9 and ceddy without issue. I've never had to add XML's to the evoscan folder. I alter the logging formula under dsm/3000gt to match the map sensor I'm using but that's it.

good to know! it seems like I shouldn't be adding the xml file, everytime i do i get the error. this thinking 2.9 puts the file in on its own. as for using dsm/3000gt are you just uusing efi? or do u have a ceddy option?

i have actually modified XML files and added tons of optimizations and to this day i still kill an entire saterday morning and a 6 pack of beer every time i do a new set up of ecuflash and evoscan. just read, follow the steps, cuss a lot, drink some more, then start from scratch and try again. eventually you will catch an AH-HA! moment and it will be smooth sailing.
awesome. ya been waiting for that AH-HA just need a little more guidence
 
something to try that use to work on a older version is to change the name of the ceddy files to exactly match the non ceddy rom and XML, then copy it over the top of the originals. (make backups though, and make sure no app is using any of the files at the time) it has been a while but that was one of the 'tricks' we use too do.
 
So...... I just finished up with uninstalling everything from ecuflash to evoscan and deleting everything ceddy off my comp and once again started over.
First I reinstalled ECUflash, Then I redownloaded Ceddys big maps (20550011-mod-1v9Cb-MAF-BigMaps). Then I was going to reinstall EvoScan v2.9 but i thought id switch it up a little and try different options so i installed EvoScan v2.7, I've also read that v2.7 works better with dsms (actuators, DTC's and such). Before installing v2.7 i read the little memo about deleting driver Op20pt32.dll out of C:Evoscanv2.7\USBdrivers\openport2.0 so Evoscan can connect to the 2.0 cable. When the newest version of ECUflash was installed, all the correct drivers were installed. So after install and before you open Evoscan make sure to delete that file (to my knowledge there is no need to replace that op20pt32.dll driver you deleted out of evoscans file with the driver from ECUFlash, but i could be wrong...someone correct me if i am please)

After, I took the 20550011-mod-1v9Cb-MAF-BigMaps.HEX and the 20550011.xml and placed them both inside C:\programXP\ECUFlash\rommettadata\mitsubishi\eclipse.

Then, i went to the evoscan2.7 folder in the documents tab, selected Datasetting folder, and found a folder named MitsubishiMUTII (~71kb) and deleted it. After that i went back into the folder that i downloaded from ceddy opened Evoscan2.7+ and inside that folder is another file named MitsubishiMUTTII (~8Kb) and placed that into the datasettings folder and BAM!.....NO ERRORS! Evoscan opens just fine and logger works fine. opened up ECUFlash, opened the big map HEX file and everything is there and working.

I was just logging a customers car the other day on v2.9 and ceddy without issue. I've never had to add XML's to the evoscan folder.

Tyeler18 this turned on a lightbulb :aha: So..... when i downloaded EVOScan v2.9 it must have either had the file and been updated for this or it found the file and put it in there on its own cause i never put anything in that file just as tyeler18 stated above, and when i tried to it was already there causing duplicate error.

Now, further back in this thread i was told to replace the MitsubishiMUTII file with the one from ceddy.

You need to replace with what ceddy provided.

This was the case when installing EvoScan 2.7 but not for installing v2.9 due to it already being in the datasetting folder

Thank you all for the help!!! :hellyeah::thumb:
 
This was the case when installing EvoScan 2.7 but not for installing v2.9 due to it already being in the datasetting folder

Thank you all for the help!!! :hellyeah::thumb:

That makes sense since EvoScan has incorporated all of Ceddy's settings in the past. I personally use v2.7 and only use v2.9 for Evo X's. I find v2.7 to be less buggy during datalogging runs for those cars in particular (DSMs and Evo 8/9s).
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Innovation Products Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com RixRacing RockAuto RTM Racing STM Tuned

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Back
Top