What did you do to your X today?

[Demon X]

Originally Posted by momostallion

ah sounds like you just lost your definition files.

and that file goes by definition files or Evo?? I found the "evo" file that has some definitions..

Originally Posted by evox79

PM me If you can't get it figured out.This literally just happened to me..Took me a few hours deticated to finally move foward with my flash.. You'll need to do clean reinstall of ecuflash.. Hamish from tactrix sent me these instructions.. I had to go into deep computer geek mode.. After doing the reinstall.. Also make sure you have all the correct definitions in C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo



-------------------EcuFlash Installation-------------------
; for Windows XP users we recommend to install the EcuFlash 1.42
; for Vista/Windows 7 users we recommend to install the 1.43 beta version
; accept all defaults when prompted, do not install to a different directory
; best practice is to install EcuFlash first, after drivers are loaded, then plug in the Openport 2.0 (it will install it's drivers)
-------------------Uninstall/Reinstall-------------------
; EcuFlash recommended steps to de-install/re-install to the beta version (1.43)
; steps must be performed in the exact sequence for optimal results
; use the DEEP SCRUB procedure to completely eliminate previous files
1. Make sure the OpenPort cable is NOT connected to your computer
2. In Add/Remove Programs, uninstall all versions of EcuFlash and all drivers with OpenPort, Tactrix, or FTDI in the name. (SEE DEEP SCRUB)
3. In program files, delete the OpenECU folder.
4. Delete any EcuFlash shortcuts that you have on the desktop or elsewhere.
5. Reboot.
6. Download and install the latest version of EcuFlash 1.43 (beta). http://www.tactrix.com/index.php?opt...d=44&Itemid=65. For Vista/Win7 users, right click the EcuFlash installer and select “run as admin”.
7. Plug the OpenPort cable into a USB port on your computer.
8. When Windows asks to connect to windows update, select NO, then select “install the software automatically”. This may occur twice before the driver install is finished.

DEEP SCRUB:
Sometimes the driver just won't work no matter how much you install/uninstall EcuFlash. This happens 1% of the time, and to fix this, you need to go into the c:\windows\inf\ folder and do a windows search "in file contents" for the word FTDI and delete just those specific inf files. (On my PC I found oem10.inf oem11.inf oem12.inf oem14.inf.) Then reinstall from the EcuFlash installer, then it will work.
(Remember x86 means 32bit windows, and x64 means 64bit version of windows.)
On some strange situations, when plugging in the "FTDI USB to Serial COM" cable it pops up a message informing you that the driver was not digitally signed correctly and will be disabled. This can be fixed by going to the c:\windows\system32\drivers folder and deleting ftser2k.sys and then UN-installing the driver, plug the cable back in, and reinstalling if requested, using the FTDI driver that comes with ECUFlash in the drivers folder.
BTW, if you are looking for the drivers, EcuFlash has a spare copy of the drivers in their installation folders in case you need them again.
Here are those folder locations:
32-vit version of Windows ->
C:\Program Files (x86)\OpenEcu\EcuFlash\drivers\openport 1.3\
C:\Program Files (x86)\OpenEcu\EcuFlash\drivers\openport 2.0\
64-bit version of Windows ->
C:\Program Files\OpenEcu\EcuFlash\drivers\openport 1.3\
C:\Program Files\OpenEcu\EcuFlash\drivers\openport 2.0\
double click DPInst.exe to run this driver installation program.
Also if windows asks for a driver folder, you can point it at the right folder above.
Also, make sure that everytime you run Ecuflash, you run it as administrator - you can set it up to do this every time by modifying the EcuFlash Icon shortcut (right-click -> properties -> advanced -> check box "run as administrator").

thats a lot of searching lol

[chetrickerman]

David, I emailed you back your rom. Flash it to your car and let me know how it goes

[Demon X]

Alright, thanx boss Tm im going to check if it pases state inspection

[Turbo_love]

Autocrossed it for the first time at an SCCA Practice Event.

[momostallion]

Originally Posted by Demon X

and that file goes by definition files or Evo?? I found the "evo" file that has some definitions..

thats a lot of searching lol

the rom on your ECU has an id, it's 8 digits. ie: 52680015.bin
in order to ecuflash to be able to read that rom file, it needs a definition file for 52680015.

when you open the rom, ecuflash looks in it's folder
\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\
for the matching .xml, typically named to match: 52680015 .xml

all you have to do is know what your rom id is then download the definition xml file for that rom and put it in that folder.

[chetrickerman]

His rom ID is 52680018

[Demon X]

Got the issues fix on my comp/ECUFlash guys, THANK YOU ROB FROM KAIZEN TUNING

[oftheheavens]

Originally Posted by evodad424

I think thats a good price, 1099 was the lowest i ever found for a new Tomei.

i think i paid 1k for just the cbe. and like 400 for the test pipe or something like that.

[oftheheavens]

front and rear pwjdm tow hooks. was a PITA installing the front. had to cut it, and drill the crash beam and bla bla bla, but finally got it in and looking good

[da Loc]

finally realigned my wheels