TephraMod V7
All Evo 8 5-Speeds RPM/MPH:
Calculated by:
Tire Diameter (OEM) = 25.3"
Gear Ratios:
Evo 8 6-Speed RPM/MPH:
Calculated by:
Tire Diameter (OEM) = 25.3"
Gear Ratios:
- 176.2
- 117.3
- 84.7
- 62.0
- 43.3
Calculated by:
Tire Diameter (OEM) = 25.3"
Gear Ratios:
- 2.928
- 1.950
- 1.407
- 1.031
- .720
Evo 8 6-Speed RPM/MPH:
- 177.1
- 118.4
- 87.3
- 67.0
- 52.8
- 42.2
Calculated by:
Tire Diameter (OEM) = 25.3"
Gear Ratios:
- 2.909
- 1.944
- 1.434
- 1.100
- .868
- .693
Last edited by Jack_of_Trades; Oct 16, 2009 at 06:14 AM.
In this moment no, but is possible insert throttle kicker for ALS, but is necessary retarding to -17 or small value for create ALS. Throttle kickers open throttle-body door and insert air and retarding igntion with ecu, create positive Boost 0.3b(5psi) to 0.5b(7psi) when throttle is off and remove Lag when push throttle. Exhaust create sounds (Bang-Bang) with flames. In rallys of europe is more used for remove the lag of turbos. 
See this video in 2.30min or 5:00min
http://www.youtube.com/watch?v=VYbTJOEe_NY
In Spain is rallys in USA is 1/4 mille jeje
Retarding more of -15º to down is one good new option for future tephra's ecu for create real-ALS with Hardware or with kicker part.
See this video in 2.30min or 5:00min
http://www.youtube.com/watch?v=VYbTJOEe_NY
In Spain is rallys in USA is 1/4 mille jeje

Retarding more of -15º to down is one good new option for future tephra's ecu for create real-ALS with Hardware or with kicker part.
Last edited by Oettinger; Oct 16, 2009 at 06:27 AM.
Here is what I got from logging my car:
6 41.8584
5 41.8584
4 61.1504
3 85.3097
2 117.478
1 177.035
0 2899.78
Essentially you just make a new v7 labeled xml (in the two categories on top of the xml) in the evoscan ROMS directory with only pertinent maps (and all of the scalings). IE, just put in bigmaps and if you want boost maps, etc. The includes and the maps that gray out other maps and all of the other junk are what is causing your problem, and its not needed anyway in Evoscan.
If you didn't have map tracer working already you will also need a dead loadcalc in the logs (which just makes a copy of 1 byte load in the column evoscan references.)
When you do what I posted in the link it works fine for me (although it stretches way off screen).
Essentially you just make a new v7 labeled xml (in the two categories on top of the xml) in the evoscan ROMS directory with only pertinent maps (and all of the scalings). IE, just put in bigmaps and if you want boost maps, etc. The includes and the maps that gray out other maps and all of the other junk are what is causing your problem, and its not needed anyway in Evoscan.
If you didn't have map tracer working already you will also need a dead loadcalc in the logs (which just makes a copy of 1 byte load in the column evoscan references.)
Essentially you just make a new v7 labeled xml (in the two categories on top of the xml) in the evoscan ROMS directory with only pertinent maps (and all of the scalings). IE, just put in bigmaps and if you want boost maps, etc. The includes and the maps that gray out other maps and all of the other junk are what is causing your problem, and its not needed anyway in Evoscan.
If you didn't have map tracer working already you will also need a dead loadcalc in the logs (which just makes a copy of 1 byte load in the column evoscan references.)
Here are the Scalings for MPH if anyone wants to convert their XML to MPH:
Code:
<scaling name="VehicleSpeed" units="MPH" toexpr="(x*2)*0.621371192" frexpr="(x/0.621371192)/2" format="%.0f" min="0" max="317" inc="1" storagetype="uint16" endian="big"/> <scaling name="VehicleSpeed8" units="MPH" toexpr="(x*2)*0.621371192" frexpr="(x/0.621371192)/2" format="%.0f" min="0" max="317" inc="1" storagetype="uint8" endian="big"/>
The values I listed are calculated values, not measured with Evoscan.
When you do what I posted in the link it works fine for me (although it stretches way off screen).
Essentially you just make a new v7 labeled xml (in the two categories on top of the xml) in the evoscan ROMS directory with only pertinent maps (and all of the scalings). IE, just put in bigmaps and if you want boost maps, etc. The includes and the maps that gray out other maps and all of the other junk are what is causing your problem, and its not needed anyway in Evoscan.
If you didn't have map tracer working already you will also need a dead loadcalc in the logs (which just makes a copy of 1 byte load in the column evoscan references.)
Essentially you just make a new v7 labeled xml (in the two categories on top of the xml) in the evoscan ROMS directory with only pertinent maps (and all of the scalings). IE, just put in bigmaps and if you want boost maps, etc. The includes and the maps that gray out other maps and all of the other junk are what is causing your problem, and its not needed anyway in Evoscan.
If you didn't have map tracer working already you will also need a dead loadcalc in the logs (which just makes a copy of 1 byte load in the column evoscan references.)
Works perfectly now.
<DataListItem DataLog="Y" Color="" Display="Manifold Air Temp" LogReference="MAT" RequestID="09" Eval="1.8*x-40" Unit="deg F" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-40" GaugeMax="300" ChartMin="-40" ChartMax="300" ScalingFactor="1" Notes=""/>
" wich doesnt work and for some reason it logs as Air temperature using request 3A. Any reason why it logs like this ? (I am using fuel temperature input)
Hi, I was looking through Phenem's USDM 8 ROM and it seems lean spool is disabled though start/stop RPM at 1500?
As I understand it, isn't the best way to disable lean spool through FBA Bit 0? The 1500/1500 method causes tip on knock or something?
Thanks.
As I understand it, isn't the best way to disable lean spool through FBA Bit 0? The 1500/1500 method causes tip on knock or something?
Thanks.
Can someone else confirm this?


