Originally Posted by 03lances

One question, so is the only reason to use the 3 bar is because obviously for you guys the 1 bar is worthless? What I am getting at is I am driving a car only hitting 10psi, can I use the 1 bar map to log my boost then using this?

Originally Posted by Guille278

I worked in my evo. Conecting the signal of MAP sensor on #73 ECU pin, see nothing on EvoScan 2.5
Then, remove the ECU and open it, the terminal # 73 is not connected to any circuit.

Thinking and observing, the # 75 pin is locatd next to the # 76 (Lambda Signal) and the internal circuits, filters, resistors and transistors are very similar locatd. Next step, injected into the # 75 Pin 2.5Volts limited power to observe a variation of reading in Lambda # 2 on EVOSCAN. Finally I corrected The Request and Formula for MAP read .

Works well as datalog, but can cause changes in behavior of the ECU to change the input value of the 2nd Lambda signal? Even taking into account that does not own or EVO 6 wiring for the 2nd lambda sensor?


Easier, the value of the # 75 pin is taken into account in the programming of the ECU?

Thanks and cheers.

Originally Posted by mrfred

Updates
Where to get the MAP sensor

MAP Sensor Swap

Here is a picture of the MAP sensor location (right on top of the intake manifold):



<Request LogReference="JDMMAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" Logged="y" Response="2"/>