Pajero going into limp mode
Hi Guys,
I have a used Pajero io , H66W, 4G93, 1.8L GDI engine which I imported from Japan. It had 49,000KM on the ODO. Now its at 63,000KM (I do alot of higway travelling as well as offroading). I have done regular basic servive (Oil and Oil filter, spark plugs,, trottle boddy cleaning, did a top engine cleaning using seafoam) and it has never given me any problems. No smoke from tail pipe or anything like that. However, just 2 month back it just went into limp mode and the check engine light stated blinking while on the road. I had to pull off the road and did a ECU resset by removing the negative battery terminal. After that it started fine and never gave me any issues until this month, same thing happened again. I did a ECU reset and all has been fine so far.
However, I am not content with just doing a reset on the ECU so I did a scan using Evoscan (I had a mitsubishi Lancer before the iO) and attached are the results.
What do you guys think might be the issue, or at least somwhere I can use as a starting reference point in diagnosing. Im suspecting either the fuel pump or Trottle body.
It could be just one issue that is throwing out incorrect readings on the other sensors.
My next service will be a big one which will include timing belt change, water pump, transmission fluid flush, transfercase fluid change, rear diff fluid change, cooling system flush, trottle body and EGR valve cleaning, intake valve cleaning using CRC GDI intake valve and turbo cleaner and the low pressure fuel filter (in the tank) replacement.
hey FORDEM, these are the
hey FORDEM,
these are the codes I keep getting everytime I do a scan.
- Oxygen Sensor (11)
- Intake airflow sensor (12)
- ISC motor position sensor (15)
- Engine coolant Temperature sensor (21)
- Barometric pressure Sensor (25)
- Knock Sensor (31)
- Fuel pump relay (42
- Ignition coil.
I'm ASSUMING its limp mode since the car just runs at a very slow pace...doesnt matter if I floor the accelerator pedal.
I just simply pull over, take a reading and clear the codes. After which everything runs fine again. This seems to be happening once every month or so.
I use evo scan to scan for codes. I'm not sure how accurate it is on the Pajero io since it was meant for the lancer Evo. Wouldnt mind if you recomend another one to use.
Even with no check engine lights on...and I do a DTC scan...these codes keep coming up. I'm now working on replacing these sensors (not all at once. too expensive where I'm from).
Codes can be read on the GDI engines using a jumper wire.
There is a downloadable manual in the resource section of the forum that documents a method of reading the codes on a GDI vehicle using a jumper wire and the check engine light - it also explains the various codes and tells you how to test the sensors. It's important to understand that a code does not meak a sensor is defective, the code tells you what the ECU is seeing, and with that many codes, I doubt that all of the sensors called out are defective - it's more likely to be a wiring harness issue, or possibly the ECU itself.
What makes you think it's in limp mode?
First question - what engine does your iO have, and second - what makes you think it's in "limp mode"?
Limp mode is a specific mode of operation that the ECU invokes because it cannot see data from one or more sensors essential to proper operation, a mode intended to allow you to safely get the car back to a safe place rather than just shutting down, essentially it allows you to "limp" home.
Think of a human being out for a brisk walk, stumbling & perhaps spraining an ankle, are you immobilized, no; will it be painful to walk home, definitely; are you going to limp, without a doubt; but you'll get there eventually - it's the same concept, and now you know the origin of the term.
A vehicle in limp mode will typically run rich, with retarded iginition timing, and be limited to a few thousand rpm, all in an attempt to minimise the risk of engine damage.
Now look them up...
What do they mean? Make a note of them, then reset the ECU by disconnecting the battery, after reconnecting the battery, check for codes again to make sure the codes have been cleared, and then allow the engine to idle and switch the a/c on again - if it goes in to limp mode, recheck for codes, and the codes you see this time around will be theones related to the problem.
Hello guys.i didnt get to see
Hello guys.i didnt get to see how the problem of going into limp mode was resolved.I have just had a Pajero io 1.8 gdi engine overhauled.i bought with engine in pieces.If i run the engine in one place it runs over 3500RPM but as soon as i go out on the highway,i dont even drive for 200metres before it goes into limp mode.sometimes i get going again just by removing the battery to reset ecu but sometimes just switching off and starting engine gets vehicle going again.What could be the problem?
Your guess is as good as mine.
What could be the problem?
Can I assume you at least read through the thread?
Do I have to ask the same series of questions another time?
If you read the thread then you know where to find the documentation that will tell you how to read the check engine codes, as well as how to find out what they mean - without that information, we would just be guessing, and I will be upfront with you and tell you - your guess is as good as mine.
Blocked fuel filter? Blocked fuel injector(s)? Blocked fuel line? Blocked catalytic converter? Defective spark plugs? Defective ignition coil? Defective low pressure fuel pump? Defective high pressure fuel pump? Incorrect cam timing?
I could continue making suggestions but in reality, I'm just guessing.
Looking back at MNs post
I see a code listed as ISC motor position sensor (15) - because the GDI engines are "drive by wire" there is no ISC (idle speed controller) and so no ISC motor or position sensors. if Evoscan is reporting a problem with a non-existent sensor, it would suggest an incompatibility with the vehicle.
Syndicate
Maybe I'm missing it
but I'm not seeing any attachment - and - if the CEL is on, there shoud be a code which will at the very least point tell you what or where the ECU thinks the problem lies, no base line required.