9653006v5 WORKS for 05 USDM (9694011)
Mar 24, 2008, 07:50 AM
#1
Evolving Member
Thread Starter
iTrader: (34)
Join Date: Apr 2006
Location: FLORIDA
Posts: 147
Likes: 0
Received 0 Likes
on
0 Posts
9653006v5 WORKS for 05 USDM (9694011)
Hi, I figured I'd start a new thread. Per the instructions from RL and Tephra, I was able to get the 9653006v5 rom to start in my 05 MR. I had to disable the immobilizer using the (0x56D2) code. I will take a trip around the block shortly, but I thought I would share this awesome news.
*update* Its been about a month so far, and I haven't seen any issues. I am using it for dual boost (hi-low settings) with the physical switch, and that works like a charm. Haven't used NLTS much, but what little I use, it works fine. The valet mode works good also. I installed a JDM boost sensor about 2 weeks ago, and that was just plug and play. I can log boost in evoscan now!
The only thing I have seen, which wasn't major, was I had to bump up the idle with AC on setting because I was stalling out, but other than that I'm
Oh and immobilizer is still disabled.
a big thanks to Tephra for making this happen. You rock!
-Jason
*update* Its been about a month so far, and I haven't seen any issues. I am using it for dual boost (hi-low settings) with the physical switch, and that works like a charm. Haven't used NLTS much, but what little I use, it works fine. The valet mode works good also. I installed a JDM boost sensor about 2 weeks ago, and that was just plug and play. I can log boost in evoscan now!
The only thing I have seen, which wasn't major, was I had to bump up the idle with AC on setting because I was stalling out, but other than that I'm
Oh and immobilizer is still disabled.
a big thanks to Tephra for making this happen. You rock!
-Jason
Last edited by rish197; Apr 30, 2008 at 02:14 PM.
Mar 24, 2008, 08:52 AM
#4
rish197, so you donwloaded the 96530006 V5 ROM, disabled the immob, copied over your setting and flashed it to your ECU and the car started?
Just making sure, but you didn't simply copy the XML into your 96940011.xml file and then simply made the immobilzer change to your 96940011 ROM, then flash it, right?
Basically, I'm just trying to make sure that you actually flashed the 96530006 ROM to your ECU and not your 96940011 ROM again.
If you actually did use the 96530006 ROM, then you should have had to disable the Valert rev limit and stuff like that, right?
Eric
Just making sure, but you didn't simply copy the XML into your 96940011.xml file and then simply made the immobilzer change to your 96940011 ROM, then flash it, right?
Basically, I'm just trying to make sure that you actually flashed the 96530006 ROM to your ECU and not your 96940011 ROM again.
If you actually did use the 96530006 ROM, then you should have had to disable the Valert rev limit and stuff like that, right?
Eric
Mar 24, 2008, 09:07 AM
#6
Evolving Member
Thread Starter
iTrader: (34)
Join Date: Apr 2006
Location: FLORIDA
Posts: 147
Likes: 0
Received 0 Likes
on
0 Posts
rish197, so you donwloaded the 96530006 V5 ROM, disabled the immob, copied over your setting and flashed it to your ECU and the car started?
Just making sure, but you didn't simply copy the XML into your 96940011.xml file and then simply made the immobilzer change to your 96940011 ROM, then flash it, right?
Basically, I'm just trying to make sure that you actually flashed the 96530006 ROM to your ECU and not your 96940011 ROM again.
If you actually did use the 96530006 ROM, then you should have had to disable the Valert rev limit and stuff like that, right?
Eric
Just making sure, but you didn't simply copy the XML into your 96940011.xml file and then simply made the immobilzer change to your 96940011 ROM, then flash it, right?
Basically, I'm just trying to make sure that you actually flashed the 96530006 ROM to your ECU and not your 96940011 ROM again.
If you actually did use the 96530006 ROM, then you should have had to disable the Valert rev limit and stuff like that, right?
Eric
I d/l 96530006 rom, made appropriate XML changes to 96530006.xml, disabled all "mods", added the
<table name="(periphery 0)" category="Misc" address="faa" type="1D" level="1" scaling="Hex16"/>, changed value to 56D2 and wrote to ECU.
I am now going one at a time to change fuel/timing maps, and now enabling one mod at a time and making sure it fires up.
Again, I have an 05 MR, so not sure if that would be any different than a regular 05
Also, should I continue to post here or in the other thread. Just figured starting a new thread on this might be easier.
-Jason
Trending Topics
Mar 24, 2008, 01:54 PM
#13
Evolved Member
iTrader: (30)
Join Date: Dec 2003
Location: USA
Posts: 929
Likes: 0
Received 0 Likes
on
0 Posts
MrFred, anyway to check this ROM, 96530006, to determine the proper settings for the JDM Sensor? Not sure if the Euro ROM used a 3 Bar JDM sensor or not. Thoughts?
Mar 24, 2008, 01:56 PM
#14
Evolving Member
Join Date: May 2007
Location: Edinburgh, UK
Posts: 121
Likes: 0
Received 0 Likes
on
0 Posts
Mar 24, 2008, 02:06 PM
#15
No MAP sensor at all on Euro Evos. This is actually even easier to deal with because US cars have all the wiring in place, and the ECU still reads the ADC input. Its just a matter of pointing the ADC MAP sensor RAM address to a free MUT channel and then reading that MUT channel with EvoScan. None of the table editing like for US ECUs.
The more challenging is going to be dealing with the lack of emissions control. I'd bet money that several key emissions routines will not run. What would be lucky is if those emissions routines were simply turned off via the settings in the periphery.
The more challenging is going to be dealing with the lack of emissions control. I'd bet money that several key emissions routines will not run. What would be lucky is if those emissions routines were simply turned off via the settings in the periphery.