so how does the JDM sensor benefit us again? what would i gain by running one?

 

You can log boost accurately. So its another tool for tuning. As a bonus, it should also help end all the debates about how much boost taper people are seeing. :-)

 

Don't forget to add me to your group buy list.. I want to get my name on there so people feel more comfortable getting one.

 

Done.

 

im still debating i will know in the next couple days, when is your deadline

 

sign me up, I'll try one.

 

will the map sensor allow the ecu to make finer adjustments to fuel mixture since it's like air desity? i thought the usdm ix already had this sensor incl. i've logged my data with auterra dynoscan and saw intake manifold pressure as a parameter...is this the same map sensor we're talking about?

 

JDM Evo IX map sensor group buy signup
1. MalibuJack x1
2. chrisw x1
3.
4.
5.
6.
7.
8.
9.
10.

 

The original intent of the map sensor on the USDM Evo appears to only be to allow the ecu to monitor the performance of the egr system. The USDM sensor has a limited range of -14.5 psig to 3 psig. The JDM map sensor has a range of -14.5 psig to about 32 psig. The DIY tuning folks would like to use the JDM sensor so that they can accurately log boost which aids in the tuning process. The JDM sensor is identical in appearance to the USDM sensor, so if the JDM sensor works without throwing a code, then adding a JDM pressure sensor will be the easiest way to accurately log boost.

 

How is this different than running MAFTPro? Just need to flash the ecu for a JDM rom? I'm pretty excited if the before mentioned is true.

 

This is in no way like running a MAFTPro, as stated earlier, the stock MDP sensor is used as part of the monitoring of the EGR system (I really didn't even know that until someone posted about it and I researched it)

The purpose of using a JDM Sensor is to allow Evoscan to log boost, as that seems to be something people want the ability to do. Right now, the "early adopters" such as myself, want to hook up the sensor and see if the EGR system throws any codes because of it. Then I'll start looking for a map to adjust it so it won't throw an error..

This currently would have no useful tuning function other than for logging.

In the future, well thats a different story... Stay tuned..

 

Sorry for the noob question, but would it be just as good to use a wideband with boost logging (e.g. ZT2)? For the US models, we have been tuning by logging load (and for some of us that log boost via wideband). Unless there is a table that can be used with specific boost vs. load, I am not sure I understand the real benefit, unless you don't have a wideband that logs boost...

 

There is no real benefit.. But some guys want to be able to log boost in the same logs..

Load is better to work from, if your comfortable logging data simultaneously with two devices, or the device you have is integrated into your logging software and you already have boost logging, then stick with that.

The real benefit is what can possibly be done in the future through the ECU, logging and calibration are just the first steps..

 

AND... of course... the people WITH JDM cars now... like me... would have this functionality added :-)

Actually, is it simple to add this function to Evoscan and other logging tools? If so, and the parameter is already know (regardless if it throws a CEL right now) could it be added first so the JDM guys can see it?

 

Yep, both Evoscan and Mitsulogger can log the "MDP" aka "MAP" sensor.. Look for the correct requestID in the XML definition file, and plug in the correct formula for the 3 bar map sensor (I think it was posted earlier in this thread, if not another one)