Now that the holidays are over I have more free time for myself again. So I upgraded my evoscan to the Maptracer Edition and the installation was successful. The problem I am encountering is with the maptracer feature. I load my log file in which was captured with Evoscan 2.0 Maptracer Edition, load the xml file from the ROM install directory and then load hex file. When I select any items to trace it's just blank. So I then load the sample log files from the installation and it traces it out fine. So i'm lost here Has anyone else experienced this issue with the maptrace? If so, what did you do to resolve it? TIA

 

reinstalled Windows XP, ecuflash 1.30, and evoscan 2.0 maptracer edition... I still can't get this to trace out the log file.

 

Ok, I got it working with Kreionic’s help. He sent me one of his logs and I was able to trace the log okay. Now we just verified the installation of my Evoscan (ES) is fine. So I sent him my ES log and to my surprise he was not able to trace anything. Our next step we to use the 88590015 xml rom file that was included the the ES installation directory and copy it over to EcuFlash ROM directory (C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo) . Make sure you make a copy of the original 88590015.xml file. Open EcuFlash in developer mode and modify your 2 byte settings for load and air flow. While you’re in EcuFlash, set the following values: 2-byte Air Flow high bit = 27177 , 2-byte Air Flow low bit = 27176 , 2-byte load mod #1 = 27169, and 2-byte load mod #2 = 27168 . I then saved the hex file and flashed it into the ECU. We now need to make change with the 2-byte air flow in ES. While you’re in ES, right-click Air Flow 2-Byte Mod in the display plane and click edit. Change the RequestID 04 to RequestID 02 and RequestID 05 to RequestID 03, and then click OK. Since I am still at work I drove around the parking lot while logging. Opened up the log with maptrace and NOW IT WORKS! Thanks Kreionic!

 

Wow this was the same problem I had.

 

Does anyone know why the "vs RPM" graph has strange readings. I cant figure out why. It screwed me up at first. I couldnt figure out why my timing + 2byte load was so messed up. lol

Does this happen to anyone else?

 

I am not that smart with ecuflash code or evoscan, but (correct me if I am wrong) wouldn't this deactivate the 2byte load and airflow, by giving them their default values in ecuflash?

what I mean is, during the 2byte airflow instructions, it says to replace the default values:

MUT02: 6A29
MUT03: 6A28

with these values:

MUT02: 6B9E (type 0x6B9E)
MUT03: 6B9F (type 0x6B9F)

Putting in the values that you have supplied:

27177
27176

puts the values back to default:

MUT02: 6A29
MUT03: 6A28

The same is true for what you have for 2byte load. Won't this deactivate those 2byte logging options?

 

The above solution is not working for me (03 evo8 94170008). In playing around with this a bit I have found that:

1. You cannot load any xml from ecuflash that contains anything beyond the table name and address.

2. If I get past the above problem I cannot view anything other than the sample logs.

I do not like having to use the rom xml supplied with evoscan. I have too many mods to it. And yes I made a copy stripping out everything except table name and address.....

I think there is a problem in the parsing of the excel files. Hopefully Hamish will address this problem. It has been a while...

 

disregard