ECUFlash / Evoscan / Mitsulogger Questions
Jun 7, 2014, 06:46 PM
#1532
You seem to have a romID of 20030013 
so please rename your hex file to this format: 02_LANCER_EVO7_JDM_98640014.hex
like this. 02_GALANT_VR4_JDM_20030013.hex
also you can put versions on the end like this:
02_GALANT_VR4_JDM_20030013_Original.hex
02_GALANT_VR4_JDM_20030013_ModAddMoreFuel1.hex
02_GALANT_VR4_JDM_20030013_ModAddMoreTiming2.hex
so please rename your hex file to this format: 02_LANCER_EVO7_JDM_98640014.hex
like this. 02_GALANT_VR4_JDM_20030013.hex
also you can put versions on the end like this:
02_GALANT_VR4_JDM_20030013_Original.hex
02_GALANT_VR4_JDM_20030013_ModAddMoreFuel1.hex
02_GALANT_VR4_JDM_20030013_ModAddMoreTiming2.hex
Jun 7, 2014, 10:22 PM
#1533
Completely new to the data logging/ECUflash community...I have a galaxy tablet and was wondering if ECUflash has an app to run on it instead of a laptop? I know EvoScan has the android tablet but not looking to buy another tabled just for data logging. thanks guys!
Jun 8, 2014, 04:51 AM
#1534
Newbie
Join Date: May 2014
Location: Summerholm
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
Thanks Hamish, I see it has worked for you, however nothing has changed for me after changing then address to 1fefa using Notepad++
Is there anything else you did?
I also renamed it in the format you requested.
What is 1fefa?
I still have the same error :-(
Is there anything else you did?
I also renamed it in the format you requested.
What is 1fefa?
I still have the same error :-(
Jun 9, 2014, 03:00 AM
#1537
<rom>
<romid>
<xmlid>EMKS11</xmlid>
<internalidaddress>2fefa</internalidaddress>
<internalidstring>EMKS11</internalidstring>
<make>Mitsubishi</make>
<market>JDM</market>
<model>Galant</model>
<submodel>VR-4</submodel>
<transmission>5MT</transmission>
<year>2002</year>
<flashmethod>mitsukernel</flashmethod>
<memmodel>H8539F</memmodel>
</romid>
<include>VR4Base</include>
<romid>
<xmlid>EMKS11</xmlid>
<internalidaddress>2fefa</internalidaddress>
<internalidstring>EMKS11</internalidstring>
<make>Mitsubishi</make>
<market>JDM</market>
<model>Galant</model>
<submodel>VR-4</submodel>
<transmission>5MT</transmission>
<year>2002</year>
<flashmethod>mitsukernel</flashmethod>
<memmodel>H8539F</memmodel>
</romid>
<include>VR4Base</include>
Jun 9, 2014, 04:47 AM
#1538
Newbie
Join Date: May 2014
Location: Summerholm
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
I'm really only wanting to use the map trace function to speed up tuning. Currently it's really laborious open the xl file, move the logged cells so everything is on the same screen, freeze the top row then start scrolling etc.
I appreciate the time taken to get the above result, it just didn't work?
Jun 9, 2014, 09:45 AM
#1539
Newbie
Join Date: May 2014
Location: Austria
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
Jun 16, 2014, 09:47 AM
#1542
Evolved Member
I am using evoscan 2.9 ,i open my hex file from the evoscan folder the load and rpm scales show correctly in the live map tracer but when ever i try to open a different hex file the load values and rpm show random numbers.
Kindly guide me through.
Thanks
Kindly guide me through.
Thanks
Jun 16, 2014, 11:06 AM
#1544
Newbie
Join Date: May 2014
Location: Austria
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
Jun 17, 2014, 04:26 AM
#1545
thats not strange.. that looks fantastic..
now follow the 2nd instruction I said in a few posts back..
after pressing Ctrl+H in ultraedit, now press CTRL+G and goto the location
0xf52 for evo7/8/9/airtrek
0x1021a for Evo 5/6
0x1fefa (for vr4/galant/legnums/mirage)
0x2fefa (for vr4/galant/legnums/mirage)
and take a screenshot of each for us to look at.
now follow the 2nd instruction I said in a few posts back..
after pressing Ctrl+H in ultraedit, now press CTRL+G and goto the location
0xf52 for evo7/8/9/airtrek
0x1021a for Evo 5/6
0x1fefa (for vr4/galant/legnums/mirage)
0x2fefa (for vr4/galant/legnums/mirage)
and take a screenshot of each for us to look at.
Last edited by evoscan; Jun 17, 2014 at 04:42 AM.
