EvoX support for EcuFlash and EvoScan
#1
EvoX support for EcuFlash and EvoScan
Hey guys, I have done a whole lot of mods to my car already. such has removing the cat, pod and headers. I want to keep my original ecu rom, but I want to update the fuel and timing maps to the EvoX FQ400 does anyone have any EvoX JDM ralliart roms for download? I could only find the Evo8 and Evo9 Ralliart ones on the limitless website. where can I find ALL the latest evoX developent xmls?
From what I have read I see that EcuFlash and EvoScan is the best tools for tuning my EvoX. I have downloaded ecuflash and evoscan v2.6 beta8 and ordered a OpenPort2.0 cable and evoscan combo from limitless.co.nz they were the cheapest I could find.
I see that EvoScan EvoX datalogging support is going to be released in the next week. I downloaded mitsulogger, and mutmonitor, but they didn't work using my friends op2 cable. Looks like EvoScan is my only hope. Also is the EvoScan gps touchscreen going to support EvoX too? I think it would be too much stuffing around trying to build a carpc when the evoscan gps looks like it will do everything i need especially if it has wideband support too, and I can locate it on my windscreen where I can easily see it. Is there any other touchscreen devices available for EvoX?
From what I have read I see that EcuFlash and EvoScan is the best tools for tuning my EvoX. I have downloaded ecuflash and evoscan v2.6 beta8 and ordered a OpenPort2.0 cable and evoscan combo from limitless.co.nz they were the cheapest I could find.
I see that EvoScan EvoX datalogging support is going to be released in the next week. I downloaded mitsulogger, and mutmonitor, but they didn't work using my friends op2 cable. Looks like EvoScan is my only hope. Also is the EvoScan gps touchscreen going to support EvoX too? I think it would be too much stuffing around trying to build a carpc when the evoscan gps looks like it will do everything i need especially if it has wideband support too, and I can locate it on my windscreen where I can easily see it. Is there any other touchscreen devices available for EvoX?
#2
EvoScan GPS Navigator will support EvoX datalogging soon, I am currently working on it.
EvoScan v2.6 beta9 will support OpenPort2.0 Datalogging and DTC for 1994-2008 Mitsubishi. I have it running at 190+ samples per second!
EvoScan v2.6 beta9 will support OpenPort2.0 Datalogging and DTC for 1994-2008 Mitsubishi. I have it running at 190+ samples per second!
#3
its too bad NOTHING works with the 2.0 cable thanks for taking my money colby.....
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
#4
its too bad NOTHING works with the 2.0 cable thanks for taking my money colby.....
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
Lack of skill is no reason to abuse colby
#5
Ban
its too bad NOTHING works with the 2.0 cable thanks for taking my money colby.....
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
You couldve posted a simple question but NO. Now you're gonna get what's coming to you.
#6
Monsta, what he meant to say was: "This OpenPort 2.0 is the best thing to happen to Mitsubishi owners this century, unfortunately I got an error message that I need to fix, can anyone make a suggestion"
So assuming he said that, I would reply with:
1. Try using the device manager (from run command enter devmgmt.msc)
2. uninstall the comport assigned to the openport2.0 (cause it looks like your comport froze up)
3. restart the computer, then reinstall the latest ecuflash, plug the op2.0 back in, run ecuflash.
4. let the firmware get updated by ecuflash.
5. try again.
6. if it still doesn't work, then post on the developers Openport2.0 forum at forums.openecu.org
So assuming he said that, I would reply with:
1. Try using the device manager (from run command enter devmgmt.msc)
2. uninstall the comport assigned to the openport2.0 (cause it looks like your comport froze up)
3. restart the computer, then reinstall the latest ecuflash, plug the op2.0 back in, run ecuflash.
4. let the firmware get updated by ecuflash.
5. try again.
6. if it still doesn't work, then post on the developers Openport2.0 forum at forums.openecu.org
#7
I bought the touch screen but have yet to use it at it's potential. I hope the logger for the X gets release soon.
I haven't figured out how to view the rom on the touch screen. Didn't try hard enough but I will soon
I haven't figured out how to view the rom on the touch screen. Didn't try hard enough but I will soon
Trending Topics
#9
Any leak as to when v2.6 beta9 might be released?
Thread
Thread Starter
Forum
Replies
Last Post
evoscan
ECU Flash
1338
Aug 16, 2020 05:22 AM
evo4mad
ECU Flash
1880
May 5, 2015 07:22 PM
evo4mad
Evo X Engine Management / Tuning Forums
115
Feb 3, 2010 07:52 PM
evo4mad
ECU Flash
180
Jun 7, 2007 06:06 PM