2009 Lancer Ralliart - GST Basemap
Jul 20, 2012, 08:06 PM
#3346
Newbie
iTrader: (1)
Join Date: Apr 2009
Location: Melbourne, Australia
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
Hi Richardjh,
Can I ask if there will be a AUS Boost Pill + TBE version released for my 2009?
I've had a look through the ZIP file but that combination only starts at 2010.
Big fan of your efforts,
Craig
Can I ask if there will be a AUS Boost Pill + TBE version released for my 2009?
I've had a look through the ZIP file but that combination only starts at 2010.
Big fan of your efforts,
Craig
Jul 20, 2012, 09:52 PM
#3347
Evolved Member
For AUS/EDM 2009, just use the 2010-named tunes. 
They are all the same ROM base... 5361... therefore interchangeable. There's honestly no point in supporting a load more combinations of "2009" when a later version of the same base ROM ID is available.
So: If you're on 53610009, 53610010 or 53610012, use "2010 AUS/EDM". That's 53610013.
My own RA came with 53610010. This year, I finally bit the bullet and "upgraded" to 53610013. Was lots of work, as I had custom patches for all sorts of crazy stuff, lol. Reeeewrite.
If you've got logging set up for an older ROM version, you will probably need to revise your logging addresses. See this post for those!
Gimme a shout if you need any assistance.
Rich
They are all the same ROM base... 5361... therefore interchangeable. There's honestly no point in supporting a load more combinations of "2009" when a later version of the same base ROM ID is available.
So: If you're on 53610009, 53610010 or 53610012, use "2010 AUS/EDM". That's 53610013.
My own RA came with 53610010. This year, I finally bit the bullet and "upgraded" to 53610013. Was lots of work, as I had custom patches for all sorts of crazy stuff, lol. Reeeewrite.
If you've got logging set up for an older ROM version, you will probably need to revise your logging addresses. See this post for those!
Gimme a shout if you need any assistance.
Rich
Jul 20, 2012, 11:05 PM
#3348
Newbie
iTrader: (1)
Join Date: Apr 2009
Location: Melbourne, Australia
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
For AUS/EDM 2009, just use the 2010-named tunes.
They are all the same ROM base... 5361... therefore interchangeable. There's honestly no point in supporting a load more combinations of "2009" when a later version of the same base ROM ID is available.
So: If you're on 53610009, 53610010 or 53610012, use "2010 AUS/EDM". That's 53610013.
My own RA came with 53610010. This year, I finally bit the bullet and "upgraded" to 53610013. Was lots of work, as I had custom patches for all sorts of crazy stuff, lol. Reeeewrite.
If you've got logging set up for an older ROM version, you will probably need to revise your logging addresses. See this post for those!
Gimme a shout if you need any assistance.
Rich
They are all the same ROM base... 5361... therefore interchangeable. There's honestly no point in supporting a load more combinations of "2009" when a later version of the same base ROM ID is available.
So: If you're on 53610009, 53610010 or 53610012, use "2010 AUS/EDM". That's 53610013.
My own RA came with 53610010. This year, I finally bit the bullet and "upgraded" to 53610013. Was lots of work, as I had custom patches for all sorts of crazy stuff, lol. Reeeewrite.
If you've got logging set up for an older ROM version, you will probably need to revise your logging addresses. See this post for those!
Gimme a shout if you need any assistance.
Rich
When I try to open that the 2010 file in EcuFlash it comes up with unknow rom. I'm using rom 53610010, you mentioned you upgraded yours to 53610013. Is that the only way I can get this to work or is there any easier way?
Cheers for the help
Craig
Jul 21, 2012, 04:22 AM
#3350
Newbie
iTrader: (1)
Join Date: Apr 2009
Location: Melbourne, Australia
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
Hey Rich,
I downloaded the XML for 53610013 then dropped it i to OpenECU in the evo section of Rommetadata. Below is a picture of what happens when I try and open it
Any ideas why I can't see this tune like the others?
Craig
I downloaded the XML for 53610013 then dropped it i to OpenECU in the evo section of Rommetadata. Below is a picture of what happens when I try and open it
Any ideas why I can't see this tune like the others?
Craig
Jul 21, 2012, 05:08 AM
#3351
Evolved Member
In the "evo" section? Mine lives in the "lancer" section.
Now, be aware... as soon as EcuFlash opens its first ROM, it goes tearing into its "rommetadata" directory and loads EVERYTHING ending in ".xml". If you have two "53610013.xml" files, it's in the lap of the Gods as to which one it loads first.
If you have "old_xxxxx.xml", it'll happily load that. The main part of the filename doesn't tell it what ROM it's for... neither does the folder it lives in. The ROM ID is inside the XML.
So... don't have two files for the same ROM, don't store backup .xml files anywhere under "rommetadata", etc. etc.
Oh, and under Windows 7, it does some more otherer crazy stuff - but I can't give specifics, as I'm still on XP. Something about where it stores or looks for .xml files!
Rich
Now, be aware... as soon as EcuFlash opens its first ROM, it goes tearing into its "rommetadata" directory and loads EVERYTHING ending in ".xml". If you have two "53610013.xml" files, it's in the lap of the Gods as to which one it loads first.
If you have "old_xxxxx.xml", it'll happily load that. The main part of the filename doesn't tell it what ROM it's for... neither does the folder it lives in. The ROM ID is inside the XML.
So... don't have two files for the same ROM, don't store backup .xml files anywhere under "rommetadata", etc. etc.
Oh, and under Windows 7, it does some more otherer crazy stuff - but I can't give specifics, as I'm still on XP. Something about where it stores or looks for .xml files!
Rich
Jul 21, 2012, 07:58 AM
#3352
hey so maybe im a little, slow... although i normally have no issues with computer related tasks... but where in the hell IS the rommetadata folder? with mitsubishi/lancer?? all i can find is a top folder called ecuflash with no sub folders and in the program under options i can change the metadata directory location but i dont think thats what i want to do here. do i need to make the folders myself or am i missing something?
Jul 21, 2012, 08:27 AM
#3353
hey so maybe im a little, slow... although i normally have no issues with computer related tasks... but where in the hell IS the rommetadata folder? with mitsubishi/lancer?? all i can find is a top folder called ecuflash with no sub folders and in the program under options i can change the metadata directory location but i dont think thats what i want to do here. do i need to make the folders myself or am i missing something?
Jul 21, 2012, 08:49 AM
#3354
Evolved Member
You can have loads and loads of XMLs... just don't have more than one for any given ROM ID!
You should only have one "53610013.xml" file... anywhere under "rommetadata".
edit: That screenshot shows that you've already got a "stub" style 53610013 definition somewhere. It's got nowt but the very basics. But - you can flash perfectly well with that stub definition. You just want to see all the shiny tables, don't ya?
Rich
You should only have one "53610013.xml" file... anywhere under "rommetadata".
edit: That screenshot shows that you've already got a "stub" style 53610013 definition somewhere. It's got nowt but the very basics. But - you can flash perfectly well with that stub definition. You just want to see all the shiny tables, don't ya?
Rich
Last edited by richardjh; Jul 21, 2012 at 08:52 AM.
Jul 21, 2012, 11:14 AM
#3355
You can have loads and loads of XMLs... just don't have more than one for any given ROM ID!
You should only have one "53610013.xml" file... anywhere under "rommetadata".
edit: That screenshot shows that you've already got a "stub" style 53610013 definition somewhere. It's got nowt but the very basics. But - you can flash perfectly well with that stub definition. You just want to see all the shiny tables, don't ya?
Rich
You should only have one "53610013.xml" file... anywhere under "rommetadata".
edit: That screenshot shows that you've already got a "stub" style 53610013 definition somewhere. It's got nowt but the very basics. But - you can flash perfectly well with that stub definition. You just want to see all the shiny tables, don't ya?
Rich
Jul 22, 2012, 03:31 PM
#3357
Jul 23, 2012, 03:10 AM
#3359
Newbie
Join Date: Jul 2011
Location: Ukraine
Posts: 29
Likes: 0
Received 0 Likes
on
0 Posts
- DTC P0139 Disable 0x1 -> 0x0
- ECU Options Set #2 bit 1
?
Thank you.
Last edited by dandan2000; Jul 23, 2012 at 03:13 AM.
Jul 23, 2012, 04:34 AM
#3360
Evolved Member
As far as I can gather...
DTC P0139 Disable 0x1 -> 0x0 is just a tweak to stop P0139 coming up.
In contrast, setting ECU Options Set #2 bit 1 to 0 will disable the entire rear o2 sensor, including its heater circuit. Apparently, having an unheated o2 sensor stuck in hot exhaust gases can permanently damage the sensor.
No original Base Map should have the ECU Options Set #2 bit 1 set to 0. If someone with a TBE wants to tweak it to eliminate a pesky CEL, it's easy enough for them to do via EcuFlash.
Rich
DTC P0139 Disable 0x1 -> 0x0 is just a tweak to stop P0139 coming up.
In contrast, setting ECU Options Set #2 bit 1 to 0 will disable the entire rear o2 sensor, including its heater circuit. Apparently, having an unheated o2 sensor stuck in hot exhaust gases can permanently damage the sensor.
No original Base Map should have the ECU Options Set #2 bit 1 set to 0. If someone with a TBE wants to tweak it to eliminate a pesky CEL, it's easy enough for them to do via EcuFlash.
Rich
Last edited by richardjh; Jul 23, 2012 at 04:36 AM. Reason: Added the word "original".