PATCH: TephraMod V5
Funny, I'm doing this right now too. going from 0008 to 0014. Do you think it is best to copy each table over. I checked all the tables, of course, ones I have modded are different but i noticed a few that I did not touch that were different. Is it best to stay with the settings from my 0008 or go to the 0014. The tables in question were, Open Loop Loads (all 4 RPM were different), desired idle and ISCV (temps were different, step were the same), Air temp compensation (temps were different), and boost limit RPM scale was all messed up. I figured the changes in the 0014 tables to those settings were just updates Mitsu implemented.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
The ROM being used was somehow corrupted/changed after downloaded.
sub7 has now redownloaded the ROM and applied his changes again...
ALL GOOD
Evolving Member
Joined: Jun 2005
Posts: 282
Likes: 5
From: Kuala Lumpur
Evoryder, add this to your 94170014 XML, just above the </rom> at the end of the file.
Enter 0x8425 into MUTE3
Enter 0x8929 into MUT83 (might already be set to that value)
This is the code for evoscan to log them. Not sure what you might need to change for Mitsulogger if thats what you use.
Code:
<table name="MUTE3" address="384e6" type="1D" level="4" scaling="Hex16"/> <table name="MUT83" address="38366" type="1D" level="4" scaling="Hex16"/>
Enter 0x8929 into MUT83 (might already be set to that value)
This is the code for evoscan to log them. Not sure what you might need to change for Mitsulogger if thats what you use.
Code:
<DataListItem DataLog="N" Color="" Display="ALT MAP Activation" LogReference="AltMapActive" RequestID="E3" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="20" ChartMin="0" ChartMax="20" ScalingFactor="1" Notes="Alt Map Activation. 0= Standard Maps 3= Alt Maps" Priority="1" Visible="False" /> <DataListItem DataLog="N" Color="" Display="ALT Map Input Voltage" LogReference="AltMapVoltage" RequestID="83" Eval="(x/256)*5" Unit="Vdc" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="15" ChartMin="0" ChartMax="15" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Evolving Member
Joined: Jun 2005
Posts: 282
Likes: 5
From: Kuala Lumpur
Funny, I'm doing this right now too. going from 0008 to 0014. Do you think it is best to copy each table over. I checked all the tables, of course, ones I have modded are different but i noticed a few that I did not touch that were different. Is it best to stay with the settings from my 0008 or go to the 0014. The tables in question were, Open Loop Loads (all 4 RPM were different), desired idle and ISCV (temps were different, step were the same), Air temp compensation (temps were different), and boost limit RPM scale was all messed up. I figured the changes in the 0014 tables to those settings were just updates Mitsu implemented.
They're different huh? If memory serves me, I didn't notice any difference in those tables when I have done the swap for users in the past. I could be wrong though. Leaving them at the 0014 settings shouldn't do any harm for those particular tables. I would try the 0014 tables first and if there are inconsistencies, go back to the 0008 settings I guess.
TPS=95%
RPM DROP= 800 to 1000 rpm
speed= 20km/h
Load= 50 to 100
Careful getting used to the NLTS. The clutch switch is VERY sensitive! If you accidentally rest your shoe on it while over 95% TPS, you'll think you just hit fuel or boost cut and the car starts dropping rpms instantly (cuz thats what NLTS does
). It gets me once in a while.
RPM DROP= 800 to 1000 rpm
speed= 20km/h
Load= 50 to 100
Careful getting used to the NLTS. The clutch switch is VERY sensitive! If you accidentally rest your shoe on it while over 95% TPS, you'll think you just hit fuel or boost cut and the car starts dropping rpms instantly (cuz thats what NLTS does
). It gets me once in a while.
Last edited by Jack_of_Trades; May 4, 2008 at 08:43 PM.