The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

ECMlink MAP sensor problem

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

BerettaDan

15+ Year Contributor
44
7
Jun 19, 2009
Philadelphia, Pennsylvania
I switched to SD and my ECMLink is not seeing the MAP sensor and car is running super rich.

I'm pretty sure I have everything set up right. I have done a lot of searching the last few weeks. Hopefully someone can give me so insight.
I checked the wiring 10 times and from my tests the MAP sensor seems fine. Thanks in advanced

You must be logged in to view this image or video.


You must be logged in to view this image or video.


You must be logged in to view this image or video.


You must be logged in to view this image or video.
 

Attachments

You must be registered for see attachments list
I switched to SD and my ECMLink is not seeing the MAP sensor and car is running super rich.

I'm pretty sure I have everything set up right. I have done a lot of searching the last few weeks. Hopefully someone can give me so insight.
I checked the wiring 10 times and from my tests the MAP sensor seems fine. Thanks in advanced
Stock MAP sensor?
 
If you're using the plug and play harness from ecmlink, bypass the PNP wiring and wire the sensor directly to the car side of the stock harness. My map didn't read correctly either through the adapter cable. If you didn't use the adapter, double check your wiring.

Can you post a log so we can check your ecmlink settings? I'd like to compare to see if something is causing it not to log.
 
Your screen shot is of a missing baro reading in your log, your MAP sensor will be logged under Omni4Bar, add that to your displayed values. The car's probably running rich because you need to tune your SD VE table and injector deadtimes.
 
The map sensor is hard wired not pnp. I checked the wiring a few times its correct. Red 5 volts, black is ground and the blue is putting out 1.1v with key on.
I added baro to the displayed values on the log you can see baro its just faint its under knock. Whenever i click on ve from log screen it says it cant find my map sensor. Its reads can not find log item for map sensor in log file.
 

Attachments

You must be registered for see attachments list
The map sensor is hard wired not pnp. I checked the wiring a few times its correct. Red 5 volts, black is ground and the blue is putting out 1.1v with key on.
I added baro to the displayed values on the log you can see baro its just faint its under knock. Whenever i click on ve from log screen it says it cant find my map sensor. Its reads can not find log item for map sensor in log file.

What Gofer is saying is that it is not going to be called "Baro". It's called "Omni4bar". You need to add that to your captured / displayed values. ECM link is saying that it can not find log item for your map sensor because its not in your captured values.
 
Yes you need to capture omni4bar not baro. Once the ecu sees that info it should run better as well since its seeing a value to know how much fuel it needs to add or subtract as long as your global and deadtimes were already setup from your maf settings
 
Leet is know don't be afraid to ask Easiest way I learned wasd hands on trial and error. Make little tweaks and see how it affects the tune and go from there
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top