Not sure if anyone still monitors this. I am running tephra v7/Phenem pre-patched 9417. Everything seems to work great with exception of logging. My EvoScan is default to 15625 and I am able to log but pretty slow. I tried to switch to 62500 but it will not connect to start logging. I was reading somewhere that you have to change the baud rate in the Rom as well but i went through every setting and cant seem to find anywhere to change it.

Ive been trying to figure that out too. I know 9653 has the option but not on 9417.

The xml for 9417 doesn't yet include the MUT baud rate constant. I took a peek at it in IDB but can't find it easily, as it is just a one byte field (0x1F) which is dead common.
Either way I found that changing the MUT baud rate in the ROM and in EvoScan doesn't make much difference to the logging rate. I get the best results by reducing the number of data items to just the bare bones required to tune.

Should I switch back to 9653? Is that the more developed one? I had some cold start issues with that one so I switched. Which is the preferred map? USD car.
2003 Evo 8

9417 is generally preferred because it is easier to tune. I've tried both and been able to get each to work satisfactorily.

To log in data
 

I am sorry if this has been answered here somewhere,
But the main idea from connecting to pin 96 is to collect data to the ECU so the car can run properly without any issues, and bypass the MAF plug "I bought the spoolin up harness"

Goodnight. install tepha v7 on my aspirated lancer (not turbo) and i have problems calibrating my map sensor.
install the roms 96530706 and my roms the factory is 90950001.


the car does not start due to lack of gasoline. but by modifying the SD map VE. raising the load to 50 in the first line from top to bottom manages to turn on but is progressing very poorly

SD map VE left
10
25
45
60
75
90
100
111
SD mao VE right
55
60
65
70
80
95
105
110

This is what I have managed to do to achieve ignition.
my map sensor is the mn143855 it has 4 pins and it incorporates the iat.
the calibration of the ait is perfect, it works the same as the e compared to the evoscan and they are at the same temperature.

You have the 4 plug ECU right? The pinout is different between the evo and the lancer. The fuel pump and A/C circuits are reversed on the circuit board, so you probably need to repin your harness. This is based on the Lancer and Evo ecu's I have, it might not be the case for yours but you should look into it.

hello.
Yes, the ECO has 4 pinnes. The car start and the command A/C is ok.

I made the table MAP SD VE (before showing): The car start, the A/C running but, when i sink the trottle the car does not advance, has gasoline inefficiency.

After i had modification of table MAF COMPENSATION to move maximun values and the car advance, but still has gasoline inefficiency in max trottle (low gasoline in the mix) and minimun trottle has a lot gasoline in the mix.

Question: The table "MAP SENSOR V", anybody can explanar to my? I had some tests with that, but I can't find the desired correlation

Yah that makes a lot of sense actually. Since the change is done in hardware it stands that the lancer pinout would already match the lancer ecu hardware. My issue was when i tried to plug in a lancer ecu into my evo. Thanks for confirming that info.

yes, there are some ecu that the pines do not match and the gasoline pump does not start. but this was not my case.

Normally people use this roms and change the map of evo and place the iat, but I want my car to remain in original conditions since this map has ait built in and it would be a great advance for aspirated engines.

How hard will it be to patch SD to a Non-evo ecu?
m32r based (47110032 romid) :)

Anyone here who did a Speed Density conversion with an AEM 3.5 bar brass map sensor on a JDM EVO VIII that comes with no factory map sensor?

Appreciate any help or direction, TIA