TephraXMOD V2
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
until the LiveTuner gets it own thread I thought I would post this here.
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
No you dont need to be using LiveTuner to use this.. If you set this up in your ROM then from that point on, The #3 map wont ever be used.. and whenever the ECU decides it "would" have used #3, it just pulls data from #1...
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
Code:
<table name="3xMAP -> Use #1 not #3 -> 0xA0CD9058" category="Misc" type="1D" scaling="Hex32" address="17f1c"/>
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
until the LiveTuner gets it own thread I thought I would post this here.
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
No you dont need to be using LiveTuner to use this.. If you set this up in your ROM then from that point on, The #3 map wont ever be used.. and whenever the ECU decides it "would" have used #3, it just pulls data from #1...
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
Code:
<table name="3xMAP -> Use #1 not #3 -> 0xA0CD9058" category="Misc" type="1D" scaling="Hex32" address="17f1c"/>
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
I'll dig for addresses for a few ROM and posted them here.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
<scaling name="Hex32" units="hex" toexpr="x" frexpr="x" format="%04X" min="0" max="4200000000" inc="1" storagetype="uint32" endian="big"/>
You should just to find the location/address, not worry about changing the actual value (ie it should always endup being 0xA0CD9058)
You should just to find the location/address, not worry about changing the actual value (ie it should always endup being 0xA0CD9058)
until the LiveTuner gets it own thread I thought I would post this here.
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
No you dont need to be using LiveTuner to use this.. If you set this up in your ROM then from that point on, The #3 map wont ever be used.. and whenever the ECU decides it "would" have used #3, it just pulls data from #1...
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
V2 only live maps "MAP based Load Calc #1 - Hot/Interpolated", and not the Cold or "other" one (which is used at Idle)..
This bit of code will remap #3 with the same LiveTuner memory table that #1 is set as..
53040010:
Code:
<table name="3xMAP -> Use #1 not #3 -> 0xA0CD9058" category="Misc" type="1D" scaling="Hex32" address="17f1c"/>
Given there is almost difference between 1/2/3 anyways I dont think this will make much difference, but it will make Live Tuning the #1 table work consistently...
I still have to play around with the live tuner.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
nah it will make it Hot+Idle and Cold..
So whenever it would have used #3, it uses #1 instead.. it still uses #1 when it would have used #1...
and #2 (Cold) is unchanged, and not live-tunable
So whenever it would have used #3, it uses #1 instead.. it still uses #1 when it would have used #1...
and #2 (Cold) is unchanged, and not live-tunable
Ok below should be the addresses for the various V2 ROM's. I'm at work and cannot verify so if anyone is feeling adventurous do proceed with caution. I've asked David to verify my findings for the 59580004 ROM I currently run but I'm sure he's sound asleep right now.
I also have the scaling figures for Hex32 that tephra provided earlier and "uint32" which is called by Hex32.
Scaling:
52680222:
55570206:
56890213:
58010205:
59580204:
I also have the scaling figures for Hex32 that tephra provided earlier and "uint32" which is called by Hex32.
Scaling:
Code:
<scaling name="Hex32" units="hex" toexpr="x" frexpr="x" format="%04X" min="0" max="4200000000" inc="1" storagetype="uint32" endian="big"/> <scaling name="uint32" units="uints" toexpr="x" frexpr="x" format="%0.f" min="0" max="4200000000" inc="1" storagetype="uint32" endian="big"/>
Code:
<table name="3xMAP - Use #1 not #3 patch (0xE005FE92 -> 0xA0CD9058)" category="Misc" type="1D" scaling="Hex32" address="18100"/>
Code:
<table name="3xMAP - Use #1 not #3 patch (0xE005FF7C -> 0xA0CD9058)" category="Misc" type="1D" scaling="Hex32" address="187c7"/>
Code:
<table name="3xMAP - Use #1 not #3 patch (0xE00602F4 -> 0xA0CD9058)" category="Misc" type="1D" scaling="Hex32" address="1a6e0"/>
Code:
<table name="3xMAP - Use #1 not #3 patch (0xE006030C -> 0xA0CD9058)" category="Misc" type="1D" scaling="Hex32" address="1a714"/>
Code:
<table name="3xMAP - Use #1 not #3 patch (0xE00602A0 -> 0xA0CD9058)" category="Misc" type="1D" scaling="Hex32" address="1a818"/>
Last edited by itzwolf; Apr 29, 2014 at 12:34 PM.
No rush though. I'm still in the process of stockpiling parts.
From what I understand there were still some minor bugs to be worked out. And not to come off as a jerk but if you read the thread completely you will know who will have it and when it will be available. If you still cant figure it out you might not want to do this yourself. The reason is it could be costly to you and time consuming. You should at the least start by getting an E-tune and listen to what they require first to start learning this. Getting a pro tune is the simplest way to have it done but mod-2 will be some time down the road I think. Tried and true is the best thought I an give you.
From what I understand there were still some minor bugs to be worked out. And not to come off as a jerk but if you read the thread completely you will know who will have it and when it will be available. If you still cant figure it out you might not want to do this yourself. The reason is it could be costly to you and time consuming. You should at the least start by getting an E-tune and listen to what they require first to start learning this. Getting a pro tune is the simplest way to have it done but mod-2 will be some time down the road I think. Tried and true is the best thought I an give you.
As for the tuning, yeah you're totally right. I don't want to mess anything up with my car and I don't have the experience to tune it myself yet. When my car is ready for a tune I will definitely want this flashed onto my ECU though, whether I learn to tune myself or have a tuner do it (most likely going to be the latter until I get the hang of it).
I'm just trying to stay informed on the version I need. Again, no rush though since I don't have any parts installed that are worth tuning for yet.




