ECUFlash / Evoscan / Mitsulogger Questions
#1036
Stupid question. I am running EcuFlash v2.8 and it seems that I already have a MUT table. Did the newer versions come setup already?
Also, does anyone have the address to put in my MUT table for 2byte load for 96940011?
Also, does anyone have the address to put in my MUT table for 2byte load for 96940011?
Last edited by PrimerSdime; Aug 11, 2011 at 03:50 AM.
#1037
Where do i input the 4 digit immobilizer code? Do i have to be connected to the car in order to see this option?
I cant find it when i go to edit map for "Init Code" or "Immobilizer"...
I cant find it when i go to edit map for "Init Code" or "Immobilizer"...
Last edited by 403VO; Aug 11, 2011 at 05:19 PM.
#1038
First, you have to have a rom saved on your computer. Open said rom, and go down to "misc". Then, check the open box next to "Immobilizer" and input your 4 digit code into the box that appears. If these options are light grey in appearance, go to options and change your user level to something with higher privileges. Lastly, flash the rom to your ecu.
#1043
Kool, finally i think i'm making progress.
So now i have another problem,
All the latest versions of ECUflash kept crashing on me. The only one that doesn't crash is version 1402178, but i can't get a vehicle interface through Tactrix openport 2.0 even with the drivers installed. Are those even compatible with one another?
So now i have another problem,
All the latest versions of ECUflash kept crashing on me. The only one that doesn't crash is version 1402178, but i can't get a vehicle interface through Tactrix openport 2.0 even with the drivers installed. Are those even compatible with one another?
#1044
I have interface with the Beta version but when i start to scroll down the list it just crashes... &*%*(&$&^$& This is frustrating!!
& version 1.42.2595 doesn't even start.. Failed to initialize prompt.
EDIT: I think the scaling is messed up so the beta version is being picky...Here is the xml file i changed to an .txt (Attached) so you could look it over if you have time an figure out where it's screwed up. Thanks for your time if you could.
& version 1.42.2595 doesn't even start.. Failed to initialize prompt.
EDIT: I think the scaling is messed up so the beta version is being picky...Here is the xml file i changed to an .txt (Attached) so you could look it over if you have time an figure out where it's screwed up. Thanks for your time if you could.
Last edited by 403VO; Aug 11, 2011 at 07:06 PM.
#1048
This 2.0 cable came with the car so i just assumed it's the right one... How was i able to connect an reflash the first time where i messed up the immobilizer though if it wasn't the right cable? hmmm.....I'm sooo lost now.
#1049
Have you reinstalled something since it originally worked? The FTDI drivers are *very* picky, and I've had to do uninstall and reinstall a few times to get it to work properly.
If you uninstall, make sure you remove the ecuflash directory and everything it contains, then go to "Add/Remove Software" in the windows control panel, and remove the FTDI drivers from there. It's also Then make sure your cable is unplugged and reboot.
Follow the guide at https://www.evolutionm.net/forums/ec...i-drivers.html
After you've done that, you can reinstall your chosen version of ecuflash (with drivers), reboot and then plug in your cable for the first time.
If you uninstall, make sure you remove the ecuflash directory and everything it contains, then go to "Add/Remove Software" in the windows control panel, and remove the FTDI drivers from there. It's also Then make sure your cable is unplugged and reboot.
Follow the guide at https://www.evolutionm.net/forums/ec...i-drivers.html
After you've done that, you can reinstall your chosen version of ecuflash (with drivers), reboot and then plug in your cable for the first time.