**Need Help setting up V7???** Here is your answer
Evolving Member
Joined: Aug 2009
Posts: 128
Likes: 0
From: Herndon, VA
First you download it from the v7 thread here.
Scroll to the 2nd post, under the big red heading ROMS.
The 3 options for 94170715 are the first ROM packages listed. The 1st one is just a basic ROM. The 2nd one has some "teaks" done which are listed in the thread, the 3rd one is for running Speed Density.
Download the one you want, it will be zipped. When you unzip it, you will have the ROM, and one or two XML definitions.
The XML definition(s) need to be moved to your evo subdirectory under the rommetadata folder for ecuflash. What does that mean? It probably means "c:/program files/openecu/ecuflash/rommetadata/mitsubihi/evo". YMMV depending on if you have a 64 bit computer, or if you installed it to a different directory.
After that, you open ecuflash, and you flash the 94170715 ROM that you downloaded.
Joined: Mar 2003
Posts: 394
Likes: 7
From: Used to be in Nor Cal, now working in Seoul
Update
I tried the new XML from Appauldd, and fresh rom posted by phenem if it solves my problem with Gear based boost control, but still not working.
I didn't modify the MUT table, and this time I also logged RPM_SPEED_RATIO_AVERAGE item.
Most of the time it is stuck to the highest value: 747.2092 rpm/kph, and the maximum value is 704.8941 rpm/kph during about 30 minutes of driving including 5th gear cruise.
I wish I had the disassembly skill to check if the variables/scalings regarding this function, but I just hope someone (Tephra himself would be the best, but I know he is busy.
) can check the 94170715 rom.
It may be specific to my 03 EVO (Purchased June 03, Have been using 94170008, not sure what rom came from factory), does anyone else with 03 EVO has the same symptom?
I guess other functions related to boost control seems working.
Although Boost Error and WGDC correction variable logging gives the same mininum values (-3.7825, and 0), and WGDC is stuck 100 even at idle (as long as the log shows) after once it is activated. 100% under this load value is set to 160 kPa and BCS Reactivation/deactivation rpm is set to 2250/2156 & 7812/7719.
Even I am describing the symptoms in detail, but overall it drives great, and I love the added functions!
Thanks again to Tephra and other many contributors!
EDIT: GM 3 port solenoid + Omni 4-bar are used.
I didn't modify the MUT table, and this time I also logged RPM_SPEED_RATIO_AVERAGE item.
Most of the time it is stuck to the highest value: 747.2092 rpm/kph, and the maximum value is 704.8941 rpm/kph during about 30 minutes of driving including 5th gear cruise.
I wish I had the disassembly skill to check if the variables/scalings regarding this function, but I just hope someone (Tephra himself would be the best, but I know he is busy.
) can check the 94170715 rom.It may be specific to my 03 EVO (Purchased June 03, Have been using 94170008, not sure what rom came from factory), does anyone else with 03 EVO has the same symptom?
I guess other functions related to boost control seems working.
Although Boost Error and WGDC correction variable logging gives the same mininum values (-3.7825, and 0), and WGDC is stuck 100 even at idle (as long as the log shows) after once it is activated. 100% under this load value is set to 160 kPa and BCS Reactivation/deactivation rpm is set to 2250/2156 & 7812/7719.
Even I am describing the symptoms in detail, but overall it drives great, and I love the added functions!
Thanks again to Tephra and other many contributors!
EDIT: GM 3 port solenoid + Omni 4-bar are used.
Thanks to many members here, Tephra MOD7 94170715 works wonderfully on my 03 EVO VIII! I do appreciate many contributers' efforts!
The only problem I have is gear based boost control is not working right.
I added these items to Evoscan, and they return only single value:
<DataListItem DataLog="N" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.029551*x-3.78251" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Gear_Tephra" LogReference="GearTephra" RequestID="40" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="Tephra Mod's Gear" Priority="5" Visible="False" />
Boost Error is fixed at -3.78251 (Omi 4 bar sensor min value), and WGDC correction is fixed at "0", and Gear_Tephra is fixed at "1".
I have been using mrfred's direct ECU based boost control without problem when I was using 94170008.
But it seems current ECU is indeed using 1st gear WGDC for all gears, but it does make some corrections according to the boost.
RPM Boost WGDC BoostError/WGDC Correction/Gear
3250 21.4 70.5 -3.78 0 1
3344 22.5 70 -3.78 0 1
3438 23.0 69.5 -3.78 0 1
3531 22.8 69.5 -3.78 0 1
3625 22.8 69.5 -3.78 0 1
3688 22.5 69.5 -3.78 0 1
3813 23.0 69 -3.78 0 1
3906 22.5 68.5 -3.78 0 1
4000 22.8 68.5 -3.78 0 1
4094 23.0 68.5 -3.78 0 1
4188 22.8 68.5 -3.78 0 1
4250 22.8 68.5 -3.78 0 1
4344 22.5 68.5 -3.78 0 1
4406 22.3 68.5 -3.78 0 1
4469 22.3 68.5 -3.78 0 1
4594 22.5 68.5 -3.78 0 1
4656 22.5 68.5 -3.78 0 1
4750 22.3 68.5 -3.78 0 1
4844 22.8 68.5 -3.78 0 1
4938 22.3 68.5 -3.78 0 1
5031 22.3 68.5 -3.78 0 1
5094 21.8 68.5 -3.78 0 1
5188 21.8 68.5 -3.78 0 1
5250 21.8 68.5 -3.78 0 1
5344 21.6 68.5 -3.78 0 1
5438 21.1 68.5 -3.78 0 1
5531 21.4 68.5 -3.78 0 1
5594 21.4 68.5 -3.78 0 1
5719 20.9 69 -3.78 0 1
5781 20.9 69.5 -3.78 0 1
5844 21.1 69.5 -3.78 0 1
5938 20.7 70 -3.78 0 1
6000 20.4 70 -3.78 0 1
My first gear baseline WGDC is:
3250 72
3500 71
3750 71
4000 70
4500 70
5000 70
5500 70
6000 72
And Max WGDC upward correction was zeroed out.
This is my RPM/MPH based gear selection table:
10 6
43.3186 5
61.9912 4
84.6903 3
117.301 2
176.195 1
2899.78 0
MUT table was modified to log 2byte Load value (00 and 01), and didn't touch 40 (preset for gear) and others.
I am pretty confident that I set up correctly other scalings and values for direct-boost control using Omni 4-bar sensor option.
I hope some one can help me fully enjoying Tephra V7 rom!
The only problem I have is gear based boost control is not working right.
I added these items to Evoscan, and they return only single value:
<DataListItem DataLog="N" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.029551*x-3.78251" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Gear_Tephra" LogReference="GearTephra" RequestID="40" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="Tephra Mod's Gear" Priority="5" Visible="False" />
Boost Error is fixed at -3.78251 (Omi 4 bar sensor min value), and WGDC correction is fixed at "0", and Gear_Tephra is fixed at "1".
I have been using mrfred's direct ECU based boost control without problem when I was using 94170008.
But it seems current ECU is indeed using 1st gear WGDC for all gears, but it does make some corrections according to the boost.
RPM Boost WGDC BoostError/WGDC Correction/Gear
3250 21.4 70.5 -3.78 0 1
3344 22.5 70 -3.78 0 1
3438 23.0 69.5 -3.78 0 1
3531 22.8 69.5 -3.78 0 1
3625 22.8 69.5 -3.78 0 1
3688 22.5 69.5 -3.78 0 1
3813 23.0 69 -3.78 0 1
3906 22.5 68.5 -3.78 0 1
4000 22.8 68.5 -3.78 0 1
4094 23.0 68.5 -3.78 0 1
4188 22.8 68.5 -3.78 0 1
4250 22.8 68.5 -3.78 0 1
4344 22.5 68.5 -3.78 0 1
4406 22.3 68.5 -3.78 0 1
4469 22.3 68.5 -3.78 0 1
4594 22.5 68.5 -3.78 0 1
4656 22.5 68.5 -3.78 0 1
4750 22.3 68.5 -3.78 0 1
4844 22.8 68.5 -3.78 0 1
4938 22.3 68.5 -3.78 0 1
5031 22.3 68.5 -3.78 0 1
5094 21.8 68.5 -3.78 0 1
5188 21.8 68.5 -3.78 0 1
5250 21.8 68.5 -3.78 0 1
5344 21.6 68.5 -3.78 0 1
5438 21.1 68.5 -3.78 0 1
5531 21.4 68.5 -3.78 0 1
5594 21.4 68.5 -3.78 0 1
5719 20.9 69 -3.78 0 1
5781 20.9 69.5 -3.78 0 1
5844 21.1 69.5 -3.78 0 1
5938 20.7 70 -3.78 0 1
6000 20.4 70 -3.78 0 1
My first gear baseline WGDC is:
3250 72
3500 71
3750 71
4000 70
4500 70
5000 70
5500 70
6000 72
And Max WGDC upward correction was zeroed out.
This is my RPM/MPH based gear selection table:
10 6
43.3186 5
61.9912 4
84.6903 3
117.301 2
176.195 1
2899.78 0
MUT table was modified to log 2byte Load value (00 and 01), and didn't touch 40 (preset for gear) and others.
I am pretty confident that I set up correctly other scalings and values for direct-boost control using Omni 4-bar sensor option.
I hope some one can help me fully enjoying Tephra V7 rom!
Last edited by ace33joe; Mar 27, 2010 at 09:59 PM.
Running into a problem trying to set up V7 on a friends 03. His car has a replacement ECU from another car. The immoblizer code was never obtained so he's using 65535 (FFFF). When switching over to the V7 the car will not start.
His rom id from the ECU was, 94170008 from a 2004, downloaded the 94170715 V7. Converted everything over. Copied the Immoblizer, and Init code. For the Immoblizer year, we tried them all, none of them worked 03 or 04.
Any ideas?
His rom id from the ECU was, 94170008 from a 2004, downloaded the 94170715 V7. Converted everything over. Copied the Immoblizer, and Init code. For the Immoblizer year, we tried them all, none of them worked 03 or 04.
Any ideas?
I'm using the 96530706-TephraMod-phenem ROM, together with EvoScan 2.6. Two questions for the smart guys out there:
1) Which load value (Load Calculated, Load MUT2Byte, etc.) in EvoScan is the most accurate?
2) Is there a way to log the target boost value the ECU is using to calc the boost error?
Thanks!
1) Which load value (Load Calculated, Load MUT2Byte, etc.) in EvoScan is the most accurate?
2) Is there a way to log the target boost value the ECU is using to calc the boost error?
Thanks!
I'm using the 96530706-TephraMod-phenem ROM, together with EvoScan 2.6. Two questions for the smart guys out there:
1) Which load value (Load Calculated, Load MUT2Byte, etc.) in EvoScan is the most accurate?
2) Is there a way to log the target boost value the ECU is using to calc the boost error?
Thanks!
1) Which load value (Load Calculated, Load MUT2Byte, etc.) in EvoScan is the most accurate?
2) Is there a way to log the target boost value the ECU is using to calc the boost error?
Thanks!
You should be able to log boost error directly as seen in this thread.
https://www.evolutionm.net/forums/ec...t-control.html
2Byte is the most accurate
You should be able to log boost error directly as seen in this thread.
https://www.evolutionm.net/forums/ec...t-control.html
You should be able to log boost error directly as seen in this thread.
https://www.evolutionm.net/forums/ec...t-control.html
I understand it should be possible to get this from JDMMAP and "Boost Error", but the formulas for these are non-intuitive, so I'm not sure how to calculate the target value from those two readings.
Thanks RoadSpike. I can log boost error fine, but I want to log the boost target ("Boost Desired Engine 'PSI'" in EcuFlash) too if possible. Since the value is now gear dependent, it would give me a way to verify what value the ECU is trying to hit
I understand it should be possible to get this from JDMMAP and "Boost Error", but the formulas for these are non-intuitive, so I'm not sure how to calculate the target value from those two readings.
I understand it should be possible to get this from JDMMAP and "Boost Error", but the formulas for these are non-intuitive, so I'm not sure how to calculate the target value from those two readings.
Joined: Mar 2003
Posts: 394
Likes: 7
From: Used to be in Nor Cal, now working in Seoul
Another update
Sorry for keep quoting myself, but here is another update.
I switched to 96530706, the universal VIII rom, and thanks to various tips from members with 03/04 USDM EVOs, it seems it is working ok.
Gear based boost control and boost error logging now work fine!
Only thing I noticed was that it idles at higher rpm (like ~1000 rather than near 850) even after warm-up, so it felt like BISS is more open.
I will adjust BISS using SAS mode from Evoscan, and see if it solves the high rpm problem.
If someone with 03/04 USDM EVO VIII has the same problem with gear base boost control, please try 96530706 rom.
I switched to 96530706, the universal VIII rom, and thanks to various tips from members with 03/04 USDM EVOs, it seems it is working ok.
Gear based boost control and boost error logging now work fine!
Only thing I noticed was that it idles at higher rpm (like ~1000 rather than near 850) even after warm-up, so it felt like BISS is more open.
I will adjust BISS using SAS mode from Evoscan, and see if it solves the high rpm problem.
If someone with 03/04 USDM EVO VIII has the same problem with gear base boost control, please try 96530706 rom.
I tried the new XML from Appauldd, and fresh rom posted by phenem if it solves my problem with Gear based boost control, but still not working.
I didn't modify the MUT table, and this time I also logged RPM_SPEED_RATIO_AVERAGE item.
Most of the time it is stuck to the highest value: 747.2092 rpm/kph, and the maximum value is 704.8941 rpm/kph during about 30 minutes of driving including 5th gear cruise.
I wish I had the disassembly skill to check if the variables/scalings regarding this function, but I just hope someone (Tephra himself would be the best, but I know he is busy.) can check the 94170715 rom.
It may be specific to my 03 EVO (Purchased June 03, Have been using 94170008, not sure what rom came from factory), does anyone else with 03 EVO has the same symptom?
I guess other functions related to boost control seems working.
Although Boost Error and WGDC correction variable logging gives the same mininum values (-3.7825, and 0), and WGDC is stuck 100 even at idle (as long as the log shows) after once it is activated. 100% under this load value is set to 160 kPa and BCS Reactivation/deactivation rpm is set to 2250/2156 & 7812/7719.
Even I am describing the symptoms in detail, but overall it drives great, and I love the added functions!
Thanks again to Tephra and other many contributors!
EDIT: GM 3 port solenoid + Omni 4-bar are used.
I didn't modify the MUT table, and this time I also logged RPM_SPEED_RATIO_AVERAGE item.
Most of the time it is stuck to the highest value: 747.2092 rpm/kph, and the maximum value is 704.8941 rpm/kph during about 30 minutes of driving including 5th gear cruise.
I wish I had the disassembly skill to check if the variables/scalings regarding this function, but I just hope someone (Tephra himself would be the best, but I know he is busy.
) can check the 94170715 rom.It may be specific to my 03 EVO (Purchased June 03, Have been using 94170008, not sure what rom came from factory), does anyone else with 03 EVO has the same symptom?
I guess other functions related to boost control seems working.
Although Boost Error and WGDC correction variable logging gives the same mininum values (-3.7825, and 0), and WGDC is stuck 100 even at idle (as long as the log shows) after once it is activated. 100% under this load value is set to 160 kPa and BCS Reactivation/deactivation rpm is set to 2250/2156 & 7812/7719.
Even I am describing the symptoms in detail, but overall it drives great, and I love the added functions!
Thanks again to Tephra and other many contributors!
EDIT: GM 3 port solenoid + Omni 4-bar are used.