Mapping Evo 6.5 TME
#1
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Mapping Evo 6.5 TME
Hi Guys,
I have a very low mileage JDM TME that is completely standard apart from a HKS Mushroom filter and hard pipe at the moment. I run the car on either Shell V-Power (98 Ron) or Tesco 99 (Momentum) here in the UK.
Now I have Evoscan and EcuFlash (Beta) and a OP 2.0 cable etc.
I have succesfully downloaded the ROM file and also made a couple of adjustments based on a tuning guide I found on here (I think) and re-flashed the ecu with the file.
I'd like to get a few toys enabled if I can, however as this is my first time using the above software I have yet to be successful enabling anything such as Anti-lag etc, so any help will be great.
Also if I post up my rom file could somebody maybe add the geeky mod or ceddy mods what ever they are please?
I have done a few pulls also in 3rd and find that I still get some counts of knock, all though I have removed some of the timing across the board. Not sure if it maybe phantom knock, so again if anybody cares to have a look I'll also post the logs.
Thanks for any help offered,
Keith
I have a very low mileage JDM TME that is completely standard apart from a HKS Mushroom filter and hard pipe at the moment. I run the car on either Shell V-Power (98 Ron) or Tesco 99 (Momentum) here in the UK.
Now I have Evoscan and EcuFlash (Beta) and a OP 2.0 cable etc.
I have succesfully downloaded the ROM file and also made a couple of adjustments based on a tuning guide I found on here (I think) and re-flashed the ecu with the file.
I'd like to get a few toys enabled if I can, however as this is my first time using the above software I have yet to be successful enabling anything such as Anti-lag etc, so any help will be great.
Also if I post up my rom file could somebody maybe add the geeky mod or ceddy mods what ever they are please?
I have done a few pulls also in 3rd and find that I still get some counts of knock, all though I have removed some of the timing across the board. Not sure if it maybe phantom knock, so again if anybody cares to have a look I'll also post the logs.
Thanks for any help offered,
Keith
#4
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Yes I have had a good read of that thread and others, however I can't download any of the files from that forum as even though I have registered and clicked on the verification email my account has still not been activated by the administrator. I have sent an email quite some days ago, but my account is still not active
Keith
#6
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I would prefer to keep the car as original as possible, so will continue with my quest
#7
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Anybody on here able to help point me in the right direction? I have downloaded the Ceddy stuff and modified the xml file for the TME rom, so now I can see all the different options available. Is it safe for me to flash the ECU with this version? And if so, can I revert back to the original TME map if I wanted to do so in the future?
Thanks,
PS. Anybody on here a member of geekmapped who can help me get my account activated on there too?
Thanks,
PS. Anybody on here a member of geekmapped who can help me get my account activated on there too?
Trending Topics
#8
Evolving Member
Join Date: May 2007
Location: Europe
Posts: 207
Likes: 0
Received 0 Likes
on
0 Posts
Yes you will be able to revert back to the stock any time. It's safe to flash, but it's not always safe to drive, there are several key points that need to be checked after flashing. In the log you have attached in the first post I haven't seen any actual AFR and boost data output.
#10
Evolving Member
This part is very important for flashing The TME Ecu:
"7203 ECUs (Evo6.5 TME)
To log boost you need to install a Map sensor following Ceddy´s instructions and setup, as if you where preparing to go with speed density.
"7203 ECUs (Evo6.5 TME)
Most Evo5/6 ecus use the 7202 cpu. But some late model 6.5s switched to the 7203 cpu. If you are unsure which cpu you have, you should open the case and check the writing on the cpu(large square chip).If the cpu reads MH7202F, you are fine.
If the cpu reads MH7203FA, you need to change the <memmodel> in the 25570100.xml file.
You should try contacting one of Geekmapped moderators here in EvoM so they grant you access to Geekmapped, they are Grayw abd AndyF. There really is a lot more Evo 5/6 tuning info there than here.If the cpu reads MH7203FA, you need to change the <memmodel> in the 25570100.xml file.
Change:
Be sure to switch it back if Flashing another 5/6 ecu. Flashing with the incorrect <memmodel> may brick the ecu, so care should be taken."<memmodel>H8539F</memmodel> to <memmodel>H8539FA</memmodel>
To log boost you need to install a Map sensor following Ceddy´s instructions and setup, as if you where preparing to go with speed density.
#11
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
This part is very important for flashing The TME Ecu:
"7203 ECUs (Evo6.5 TME)
To log boost you need to install a Map sensor following Ceddy´s instructions and setup, as if you where preparing to go with speed density.
"7203 ECUs (Evo6.5 TME)
Most Evo5/6 ecus use the 7202 cpu. But some late model 6.5s switched to the 7203 cpu. If you are unsure which cpu you have, you should open the case and check the writing on the cpu(large square chip).If the cpu reads MH7202F, you are fine.
If the cpu reads MH7203FA, you need to change the <memmodel> in the 25570100.xml file.
You should try contacting one of Geekmapped moderators here in EvoM so they grant you access to Geekmapped, they are Grayw abd AndyF. There really is a lot more Evo 5/6 tuning info there than here.If the cpu reads MH7203FA, you need to change the <memmodel> in the 25570100.xml file.
Change:
Be sure to switch it back if Flashing another 5/6 ecu. Flashing with the incorrect <memmodel> may brick the ecu, so care should be taken."<memmodel>H8539F</memmodel> to <memmodel>H8539FA</memmodel>
To log boost you need to install a Map sensor following Ceddy´s instructions and setup, as if you where preparing to go with speed density.
But EcuFlash Beta reports the chip as H8539FA and says that it uses the 2737001.xml rom file, so do I really need the modify the one you say above?
I will give those guys a message and see if they can help me out on Geekmapped.
I will also install a map sensor as you suggest, thanks for the help so far.
Keith
#12
Evolving Member
No need to remove or open your ECU, just add the "A" to the memmodel in the Ceddy Mods 25570100.xml file and you´ll be able to reflash your TME without trouble; if you ever work with another MH7202F Ecu the you just delete the "A".
#13
Newbie
Thread Starter
Join Date: Sep 2012
Location: United Kingdom
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
See attached file, will this not work? And if not do I need to remove these files altogether so that EcuFlash will revert to 25570100.xml?
Sorry for all the questions, just trying to get this straight in my head.
#14
Evolving Member
Join Date: May 2007
Location: Europe
Posts: 207
Likes: 0
Received 0 Likes
on
0 Posts
Ok thanks. But again why do I need to use the 25570100.xml file as mine is different to that according to Ecuflash. I have renamed the original 2737001.xml to 2737001_old.xml and copied the xml code from the file provided by Ceddy into a new version of 2737001.xml.
See attached file, will this not work? And if not do I need to remove these files altogether so that EcuFlash will revert to 25570100.xml?
Sorry for all the questions, just trying to get this straight in my head.
See attached file, will this not work? And if not do I need to remove these files altogether so that EcuFlash will revert to 25570100.xml?
Sorry for all the questions, just trying to get this straight in my head.
Haven't checked xml files, but ecuflash shoud throw an error if there is an incorrect line, as well you will see if new maps are shown correctly.
In ecuflash folder you can have several modified xml files, there is no need to remove them, just make sure, that there is no duplication.
Last edited by dolphin888; Sep 26, 2012 at 03:15 AM.
#15
Evolving Member
Ok thanks. But again why do I need to use the 25570100.xml file as mine is different to that according to Ecuflash. I have renamed the original 2737001.xml to 2737001_old.xml and copied the xml code from the file provided by Ceddy into a new version of 2737001.xml.
See attached file, will this not work? And if not do I need to remove these files altogether so that EcuFlash will revert to 25570100.xml?
Sorry for all the questions, just trying to get this straight in my head.
See attached file, will this not work? And if not do I need to remove these files altogether so that EcuFlash will revert to 25570100.xml?
Sorry for all the questions, just trying to get this straight in my head.
Also you will have to copy ceddy´s Evoscan xml in evoscan folder (follow instructions) in order to log the new uncapped parameters like 2byte rpm, 2byte airflow Hz, 2byte load, etc.