The Top DSM Community on the Web

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. Log in to remove most ads.

Please Support Morrison Fabrications
Please Support Rix Racing

EVOscan Idle Position Switch won't log in EVOscan

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

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

jinscho

Proven Member
636
321
Jun 16, 2017
Bangor, Pennsylvania
I'm trying to clean up some bugs on my car so that I can get a tune and get it back out on the road. Last night while @dacowgod was reviewing some data in EVOscan, he noticed that my IPS sat at 0 as if the switch wasn't being triggered. We called it a night at that point as the car wouldn't idle properly on it's own in open loop, and once warmed up it would start and idle, but die every time you came to a stop.

So, this evening I went ahead and readjusted the TPS following the factory service manual:
- .0177 feeler gauge between the stop screw and throttle valve
- turned the TPS until I lost continuity on pins 3 and 4
- verified between .4 and 1v on pins 2 and 4 (.74)
- tightened the screws on the TPS
- verified pins 3 and 4 were still open / 2 and 4 was still in spec (still at .74)
- removed the feeler gauge and verified I had continuity in pins 3 and 4 again

I also took the time to test the ISC while I had the multimeter out following Jafro's video on testing it, and all coils came back with proper resistance.

After putting everything back together, I opened up EVOscan to check and see if the IPS would switch from 0 to 1 now that I had re-adjusted the TPS and... nothing. It just sits at 0.

Next up, I tested continuity between pin 87 on the ECU and pin 3 on the TPS plug. Have perfect continuity, no breaks in the wire.

Since I knew I had continuity on that wire, I decided to try a suggestion that Ricky made and just ground that pin to see if it would trigger a "1" value in EVOscan... nope...

What am I missing here? Is it possible the request ID (4A) and Function (x bit 128) are just wrong in EVOscan? I'm at a loss here and I just want to get this fixed and have the car back up and running.
 
You also should test continuity between ECU pin #92 and TPS's pin #4. If there is continuity, try to connect directly the ECU pin# 87 and pin #92 with a piece of wire. Then see if the IPS gets 1. If it still sits 0, the issue would be on ECU side, the software setting or maybe the ECU itself is bad. If it gets 1, then you probably have some kind of malfunction in TPS since you already checked continuity on #87 and #92.
 
You also should test continuity between ECU pin #92 and TPS's pin #4. If there is continuity, try to connect directly the ECU pin# 87 and pin #92 with a piece of wire. Then see if the IPS gets 1. If it still sits 0, the issue would be on ECU side, the software setting or maybe the ECU itself is bad. If it gets 1, then you probably have some kind of malfunction in TPS since you already checked continuity on #87 and #92.

I've already attempted this (pins 87-92) in a slightly different manner. Since pin 92 is just the sensor ground, by grounding pin 3 on the TPS sensor connector (which I had already verified continuity between pin 3 on the TPS and pin 87 at the ECU), it should have accomplished the same effect as running a wire between 87 and 92 directly. That's why I'm trying to determine if my EVOscan request ID and function codes are wrong before I go looking for a new ECU.
 
I've already attempted this (pins 87-92) in a slightly different manner. Since pin 92 is just the sensor ground, by grounding pin 3 on the TPS sensor connector (which I had already verified continuity between pin 3 on the TPS and pin 87 at the ECU), it should have accomplished the same effect as running a wire between 87 and 92 directly. That's why I'm trying to determine if my EVOscan request ID and function codes are wrong before I go looking for a new ECU.
To me, it sounds pretty much software setting rather than a bad ecu.
I don't use EVOScan, so can't tell something for sure but did you already check this?

You must be logged in to view this image or video.
 
To me, it sounds pretty much software setting rather than a bad ecu.
I don't use EVOScan, so can't tell something for sure but did you already check this?

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

I saw that chart on the EVOscan site while trying to Google IPS settings, but per that post, those are the settings that need to be adjusted in order to log via EVOscan on a 95-96 ECU. From what I could find, the 97+ ECU's have different parameters, but I couldn't find any information on what they should be.

Hopefully someone who uses EVOscan on a black-box can chime in and post their IPS Request ID and Function values..
 
Did you try the parameter in the pic above? As much as I checked, (4A) x (x bit 128) seems to be for EVOs and others.
And the page says as below. The Knocksum is the one different between 95-96 and 97-99. I think the (02) (bit 0x80) is the one for 2G DSM. I am curious about this. Could you please try the parameter (02) (bit 0x80) if works or not, before deciding not working?

You must be logged in to view this image or video.
 
Did you try the parameter in the pic above? As much as I checked, (4A) x (x bit 128) seems to be for EVOs and others.
And the page says as below. The Knocksum is the one different between 95-96 and 97-99. I think the (02) (bit 0x80) is the one for 2G DSM. I am curious about this. Could you please try the parameter (02) (bit 0x80) if works or not, before deciding not working?

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

I'll give it a shot and report back.. really regretting going with a black-box over link, the cost savings is NOT worth the frustration..
 
This is something you have to add yourself right? Like I just added TPS volts for example.
Request 17 Func- x*0.01961 units -V

I can try it on mine if that helps? Just started using this recently
 
Last edited:
This is something you have to add yourself right? Like I just added TPS volts for example.
Request 17 Func- x*0.01961 units -V

I can try it on mine if that helps? Just started using this recently
Yes and no, a lot of the values are already present in EvoScan, and most of them work perfectly.. but there also a few values that need to be adjusted as the request IDs and functions vary between the Evo and DSM ecus.. it just sucks that finding out what those values need to be set at is so difficult..
 
Ok... No idea WTF happened.. but it's now working with a request ID of 02 and function of "bit 0x80". It still gives me the same 'eval is invalid' error, but it cycles between 0 and 1 with 0=on and 1=off.

This whole experience has taught me a VERY valuable lesson... If you have a choice between saving a couple bucks and going with a black box, or spending more and going with ECMLINK... SPEND EVERY LAST DOLLAR YOU HAVE AND AVOID EVOSCAN... Don't get me wrong.. it works.. but the amount of frustration you will deal with is NOT worth the $500 savings..
 
Ok... No idea WTF happened.. but it's now working with a request ID of 02 and function of "bit 0x80".
It's obvious, If it works, it's because that was the number you needed to use. This is why I asked you to try before deciding not to work without actually trying.
 
It's obvious, If it works, it's because that was the number you needed to use. This is why I asked you to try before deciding not to work without actually trying.
Yeah... But I put that same value in earlier and it DIDN'T work... Since I was hitting a wall moved on to a different issue and while running a log i noticed it was showing a 1 for IPS.. I gave it some gas and got a '2', dropping back down to a '1' when the switch reengaged.. fast forward 5 minutes and a fresh log, and it's now showing 0/1.. I changed absolutely nothing for that sensor in EVOscan..

So to recap;
- changed the value, started a log, no change (sat at 0)
- moved on to another issue, started a log, showed a value of 1 = on / 2 = off
- stopped that log and started a fresh one, now showing 0= on / 1= off

:idontknow:
 
Support Vendors who Support the DSM Community
Boosted Fabrication ECM Tuning ExtremePSI Fuel Injector Clinic Innovation Products Jacks Transmissions JNZ Tuning Kiggly Racing Morrison Fabrications MyMitsubishiStore.com RixRacing RockAuto RTM Racing STM Tuned

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds

Back
Top