log boost with JDM MAP sensor (updated instructions)
Newbie
Joined: Jan 2008
Posts: 20
Likes: 0
From: Somerset, UK
Is it possible to use a GM 3 bar sensor on a VIII 260 ECU with the SD patch?
In other words, use an OEM IX Air Temp Sensor and a GM 3 bar instead of the JDM IX / X MAP Sensor?
If it's any help, here's the scaling table for the GM 3 bar:
In other words, use an OEM IX Air Temp Sensor and a GM 3 bar instead of the JDM IX / X MAP Sensor?
If it's any help, here's the scaling table for the GM 3 bar:
Not yet. I had people reporting a P1400, but I got that one fixed. After finding similar fault check tables in the Evo 9 ROM, I am surprised that Evo 9s are not throwing a P1400. I will be posting more info about these tables in the Evo 9 soon.
If you want to add periphery2, copy my "Periphery4" entry, and change the address to FCA (and change the name to Periphery2).
If you want to add periphery2, copy my "Periphery4" entry, and change the address to FCA (and change the name to Periphery2).
How can I solve P01400 cel code for a IX EDM?
I still have this cell and don`t know how to get rid of it....
Thanks
Did that already after I install the sensor.
Still got this P01400
I suspect that is has something to do with the scaling of the sensor.
I could not find the right addresses for my rom in order to scale the MAP and I think this could be one issue.
The map is reading well the boost except some small differences at the ignition on.
I read -3.3 psi ( even that I live at 200m above see level.(0.19347*x-14.6)
Could be the MAP maybe????
Thanks Evo_Kid
Still got this P01400
I suspect that is has something to do with the scaling of the sensor.
I could not find the right addresses for my rom in order to scale the MAP and I think this could be one issue.
The map is reading well the boost except some small differences at the ignition on.
I read -3.3 psi ( even that I live at 200m above see level.(0.19347*x-14.6)
Could be the MAP maybe????
Thanks Evo_Kid
Newbie
Joined: May 2009
Posts: 7
Likes: 0
From: Rosario SF Argentina
It looks like its possible. ECU pin #73 on your ECU should be a 0-5 V ADC input. You'll also need to splice into 5 V power and signal ground from the wiring harness. I'd need to disassemble your ROM to determine the RAM address that receives the signal. It would probably take me 5 minutes, so PM me to trade email addresses.
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.
Last edited by Guille278; Dec 16, 2009 at 08:53 PM.
What about ROM 96530706 from Tephra v7 ??? Did any one get the JDM 3bar to work on that rom? I would really like to switch to v7 but I'm not sure about logging boost with the 3bar map sensor with that ROM.
Last edited by evodziobak; Dec 21, 2009 at 07:10 AM.
What settings did you apply after the installation of the new map sensor? If they are the proper EVO X map settings, you may want to try a base map to see if the code still shows up.
i did everything that was listed on the first post for my ROM.
it logs perfectly, just get that SES on start up