"El Puma"

ProjectPuma

Help Support ProjectPuma:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
JAC said:
He said that he did some creative bypassing (not sure what he did) and the car ran fine, so it confirmed that it is the MAF.
Hmmm........

Well, re-reading this thread, what's done is done.

As to the future, I'd send off for a MAF from IanG. Meantime, spray your existing MAF sensor wire heavily with proper Contact Cleaner, especially of the air filter side of it. Also re-examine your air filter and its position, just in case. Doesn't matter if the spray fixes it and you have a 'new' MAF coming, you can never have too many MAFs around in dusty locations, I reckon.

I would also get really good with a code reader and Forscan (or Torque Pro on Android), especially in live data mode (always a 2 man job, unless you want to go into a tree!) as I'm reckoning you'll need to understand this car and fix it yourself, before taking it to a mechanic or Fords (who seem to be less than useful out your way) ever again.

I would add, you were right not to try to do that cambelt yourself.

JAC said:
(Oh, and now and again, very rarely, it just dies when you come to a stop, but starts again first time no problem).
For the little time it takes, just cover the basics and put it through the 'battery off ECU learning curve' again, as it would have been off during the cambelt stuff. - Disconnect battery for a couple of hours, reconnect, run at idle for 3 minutes. Allow car to warm up and 2 minutes at a steady 1200rpm. Then a 8 -12km drive 'normal' drive, i.e. keep below 5500rpm. The ECU will then have relearned its stuff.

Hope this helps. :)
 
Thanks Frank.

I have already ordered the MAF from Ian G, who has been super helpful (as always it seems).

Basically, between my friend (who is a mechanic) and myself we have always worked on my cars and projects, never been to a garage for anything. The only reason the Puma ended up in the garage is because I read here about the issues and decided to give it to an "expert" (that didn't turn out how I planned it ;) ).

This is actually the first Ford I have owned since a Sierra V6 which was my first car many moons ago. Normally we have worked on VAG engines and some French stuff, but no fords, and definitely no Ford VCTs.

I would.just mount the MAF myself, but seeing that my bill at the garage is already going to be much higher than I thought, I am going to let the mechanic mout it, just in case it doesn't actually fix it.

I will do the reset this weekend that you mention, and take it for a run with the ODB diagnostics on, both Torque and Forscan. I bought a new USB scanner, as the Bluetooth one I had didn't recognize the Puma.

Again, thanks for all your input guys, and lets hope the MAF fixes the issue.
 
If the ECU reset doesn't work in sorting out your tick over, there's an Idle Control Valve reset on Forscan which might help.
Barry
 
UPS inform me that the MAF from Ian G is out for delivery today :thumbs:

Lets hope this fixes the issue as the car is running terrible at the moment. It misses in 1st and 2nd when cold, and dies at high revs. There is also a strong petrol smell now and again. The mechanic is convinced that the MAF will fix this, let's hope he is correct!
 
The MAF arrived, is fitted, and the car works!!!! :thumbs:

It is not 100% smooth in 1st and 2nd, but I will give the ECU a reset this weekend and see what the outcome is.

One thing that I have noticed is that the VCT seems to act at 5000rpm now, I seem to remember that it was around 4000rpm before all this mess, but to be truthful, I am just glad the car seems to be running properly now!

Thanks for all your guys help on this, and thanks Ian for the quick shipment of the MAF.

The only bad part about this is that I just had to pay a 950€ bill at the mechanic :(
 
950 euros... omg... i bought my Pum for 1500 :)

anyway... i'll be seeing this thread... i am going in spring for a cambelt change... i have problems with the idle valve and as i see the TPS...

on short runs, all is fine, at longer runs... when i go to a full stop, my rev is in the sky while the clutch is pressed :)

I will give in a clean on the TPS and ICV see if it help and check for camblet :)

I am happy you got all this thing sorted... got a nice reading... Thank you...

Steve, the other Puma lover, i salute ya'
 
Today I go some time and did (or tried to) an ECU reset.

I disconnected the battery from the car, and to make the most of it, I did a quick parasitic draw test to check the draw from leaving the ODB connector plugged in. The results are exactly the same (48mah) with or without the ODB connector plugged in.

I left the battery disconnected for 2 hours as suggested.

During this time, I remove the back seats to see how much weight I would save by removing them. I must say that it is ridiculous how little the base of the backseats weights, I think my phone weighs more than the seats :D Anyways, as I would need to declare the removal of the seats on the cars paperwork (which involves an engineering project and professional certificates etc.) I will be leaving them installed :)

After 2 hours, I reconnected the battery, started the car, and let it idle for approximately 3 mins. Barry (I think it was Barry) mentioned leaving it for 2 mins at a constant 1200rpm, but as the idle rpm is set at 850rpm, it sat at 850rpm for 3 mins.

I then took the car for a calm drive of 20km without pushing it over 4000rpm.

I must say, this has only made the stalling issue worse :(

Before, it would stall now and again, now it is doing it a lot more often (but not all the time).

As Barry mentioned doing an "idle valve reset" with Forscan, I hooked up Forscan and ran some tests.

The results of the "Key On Engine Off" were:

(OK) [13:29:14.116] Key On Engine Running On Demand Self-Test has been started
(WARN) [13:30:26.716] Test completed, found DTCs: P1000, P1650
(OK) [13:31:26.203] Key On Engine Off On Demand Self-Test has been started
(WARN) [13:31:37.587] Test completed, found DTCs: P1000
===DTC P1000===
Code: P1000 - On-Board Diagnostic (OBD) Systems Readiness Test Not Complete

Module: Powertrain Control Module

Diagnostic Trouble Code details

Check of all systems is not complete since last memory clear.

--Possible Causes--
- The vehicle is new from the factory and has not yet been through a complete OBD Drive Cycle.
- The battery or PCM has been disconnected.
- An OBD monitor failure had occurred prior to completion of an OBD Drive Cycle.
- The PCM DTCs have been cleared as part of a service process.

Note: The only way P1000 can be cleared (removed) from memory is when all of the OBD monitors have been successfully completed during normal vehicle operation.

P1000 cannot be cleared from the PCM when: 1. The thermostat is stuck open and a DTC is not generated. 2. There is an open VSS circuit and a DTC is not generated. 3. If the vehicle has a Power Take Off (PTO), the circuit is shorted to VPWR or B+, or the PTO is ON during Self-test.

The purpose of the Diagnostic Trouble Code DTC P1000 is to indicate that not all of the On Board Diagnostics OBD monitors have yet been successfully completed. You may also refer to the OBD Drive Cycle defined under the Powertrain Control/Emission Diagnosis Manual-Diagnostic Methods or the Owner's Manual.

Remember: It is not necessary to remove P1000 from the Powertrain Control Module PCM by driving the vehicle.

===END DTC P1000===


The results of the "Key On Engine Running" test were:

(OK) [13:29:14.116] Key On Engine Running On Demand Self-Test has been started
(WARN) [13:30:26.716] Test completed, found DTCs: P1000, P1650
===DTC P1000===
Code: P1000 - On-Board Diagnostic (OBD) Systems Readiness Test Not Complete

Module: Powertrain Control Module

Diagnostic Trouble Code details

Check of all systems is not complete since last memory clear.

--Possible Causes--
- The vehicle is new from the factory and has not yet been through a complete OBD Drive Cycle.
- The battery or PCM has been disconnected.
- An OBD monitor failure had occurred prior to completion of an OBD Drive Cycle.
- The PCM DTCs have been cleared as part of a service process.

Note: The only way P1000 can be cleared (removed) from memory is when all of the OBD monitors have been successfully completed during normal vehicle operation.

P1000 cannot be cleared from the PCM when: 1. The thermostat is stuck open and a DTC is not generated. 2. There is an open VSS circuit and a DTC is not generated. 3. If the vehicle has a Power Take Off (PTO), the circuit is shorted to VPWR or B+, or the PTO is ON during Self-test.

The purpose of the Diagnostic Trouble Code DTC P1000 is to indicate that not all of the On Board Diagnostics OBD monitors have yet been successfully completed. You may also refer to the OBD Drive Cycle defined under the Powertrain Control/Emission Diagnosis Manual-Diagnostic Methods or the Owner's Manual.

Remember: It is not necessary to remove P1000 from the Powertrain Control Module PCM by driving the vehicle.

===END DTC P1000===

===DTC P1650===
Code: P1650 - PSP Switch Out of Self-test Range

Module: Powertrain Control Module

Diagnostic Trouble Code details

PSP switch circuit fault

Steering wheel not turned during self test.  Note some vehicles require the steering wheel to be rotated to full lock and released.

Open or Shorted PSP Switch circuit..

This DTC may be caused by :

Suspect PSP switch.

Suspect power steering hydraulic system.

Suspect PCM.


I then checked the Engine Idle RPM setting, and it is set to 848rpm.

I looked for a function to reset the "Idle Valve" that Barry mentioned, but I could not find it. The only thing I could find related that it would let me control was the "Idle Air Intake", but as soon as this was set to anything over 0% the car stalled.

I looked into the programming features, but it tells me that I need an "extended liscense key" to use them. The option to reset the ECU to default parameters did not complete (I tried this 3 times, but it failed every time).


So...

I am still having the stalling issue (even more than before, but not all the time). What happens is that when I come to a junction, if I come to a stop with the clutch pressed down, usually in 2nd, the reves of the car drop to below 500rpm and the car stalls. The car starts again no problem, and this does not happen every time.

Any ideas or tips as to what to try next?

(BTW, my last Ford, the V6 Sierra didn't have this issue 'cos it was a good old carburettor with an idle screw ;) )
 
Hi JAC
It was Frank not me that suggested the ECU reset but if you didn't follow his instructions it may not have worked. I would suggest you re-do the reset again and then drive the car around for a while to make sure it's ok.
As for the ICV reset the car has to be in a certain state before you do it as it will tell you on the computer screen ie at normal operating temp with the engine running and all the switches in the off position. When you start the test the computer will ask you to do things like turn the steering 180 deg, press the brake pedal and press the clutch pedal which you should do when prompted. Once you have done all this the car will rev itself up for a split second and then the test is over as indicated on your computer screen. Then it should run ok unless there is something else wrong with it.
I hope that helps.
Barry
 
Sorry Barry, I had already started typing before I realised that I couldn't remember if it was you or Frank.

The test did ask me to press the brake and release (which I did) and turn the steering wheel 180º and release (which I guessed was turn it back to center), the test did reach 100% but as you can see from the results, it didn't detect the turning of the wheel. The only thing I can think of that was on was the interior light, as I did the test with the door open as it was so hot today here (26ºC). I will give it another go tomorrow if I get time.

To be honest, I am not much of a mechanic, as my mechanical partner always odes the dirty work, I usually deal with the electrical side and the research, but as I decided to keep the Puma for myself, he is letting me get on with it (which is a good learning curve I guess). As I was getting (or trying to) the Puma running properly today, he was at the side of me working on a Renault that is 25 years old and hasn't been started since 2003. In the time it took me to do the ECU testing, he removed half the engine, the fuel pump, the whole air intake system, put it all back together, got the car started and still had time to laugh at me :D (I must admit, he does offer to help, but my pride keeps telling him "no, I'm fine" and then I come running to you guys ;) )
 
Hi JAC
Yes you will have to do it again as the steering wheel needs to go slightly over 180 deg and it also gives another instruction which I can't remember but I think it means depress the clutch pedal. It's much easier to do the Forscan stuff with a passenger sat in giving you instructions what to do when the requests/commands come on screen.
Barry
 
JAC said:
After 2 hours, I reconnected the battery, started the car, and let it idle for approximately 3 mins. Barry (I think it was Barry) mentioned leaving it for 2 mins at a constant 1200rpm, but as the idle rpm is set at 850rpm, it sat at 850rpm for 3 mins.

I then took the car for a calm drive of 20km without pushing it over 4000rpm.

I must say, this has only made the stalling issue worse :(
Yeah, it would be. 3 minutes at idle, then let it warm up, then 2 minutes at 1200rpm using your foot on the accelerator to keep it at a constant 1200 rpm.
 
Edit - Note to self - when editing an existing post, try actually selecting the word 'Edit' and not 'Quote' or you will end up with a double post that cannot be deleted. :)

The result of not doing a 'battery off ECU learning curve' reset on a Puma can range from almost no discernible difference to normal or to violently kangarooing up the road for half a mile with the brakes full on feeling, which then improves but the car then runs like some old granny car...or anywhere inbetween those two extremes.

I encountered the latter extreme and very quickly learned how to become the 'World Expert of ECU Resets on Pumas' :p

Please also note this from an earlier post here -

Frank said:
I would also get really good with a code reader and Forscan (or Torque Pro on Android), especially in live data mode ( always a 2 man job, unless you want to go into a tree!)
 
Code P1650 will pop up unless you turn the steering wheel all THE WAY to it's endpoint. Only then the switch opens up and PCM adds throttle to compensate the extra strain that the pump is putting on the engine. Having said that, I discovered it only afyer I have replaced it and noticed how it works; it was faulty and I had the same error as well :|
 
Frank said:
I would also get really good with a code reader and Forscan (or Torque Pro on Android), especially in live data mode ( always a 2 man job, unless you want to go into a tree!)

Actually no need for another person: you record it. You can select over 20 different parameters to be recorded and then study it later at your desk.

If needed, ask me what you would like to monitor and I can do the same thing on my car which is OK and then you can make a comparison. My guess is that VCT is troubling you. If you want, I can go on a drive, record it and then send you the data and after examining it you try to replicate the driving conditions from me?

Just a thought, but I am willing to give it a try if you want?
 
JAC said:
I looked into the programming features, but it tells me that I need an "extended liscense key" to use them.


Getting the extended license is straightforward automated task which is rather well documented on Forscan page. That shouldn't stop you

This is how to get the extended licence
http://forscan.org/forum/viewtopic.php?f=5&t=836" onclick="window.open(this.href);return false;


This is the generator link: http://forscan.org/forum/extlic.php" onclick="window.open(this.href);return false;
 
Wild E. Coyote said:
Frank said:
I would also get really good with a code reader and Forscan (or Torque Pro on Android), especially in live data mode ( always a 2 man job, unless you want to go into a tree!)
Actually no need for another person: you record it.
True, but I did specifically refer to 'live data mode' above and not 'record data mode'.
 
Thanks for all the input guys.

I currently have the battery disconnected (1 hour to go) and will repeat the reset process.

I will then repeat the KOEO and KOER tests in Forscan to see what the outcome is. I can't get the extended liscense yet as I need to wait for the administrators group on Forscan to activate my account, so if any programming is needed it will have to wait until next weekend (I am very busy at work at the moment with end of year stuff).

For recording data in Forscan, is there anything you recommend me to record? I am on my own today so I don't have anyone to help me in Live data mode.

In fact, is it possible to load a profile from someone else and automatically record the same stuff?

I will be using the car to go to work and back this week (it's too cold for the motorbike at the moment!) so I can record the trips to and from work if that would be of any use, but they are only about 4km each way.

Thanks again.
 
Well, I repeated the process...

I removed the battery for 2 hours, reconnected, let the car idle for approx 3 minutes, kept the car a 1200 rpm for approx 3 minutes and then drove for 22km.

I repeated both the KOEO and KOER tests and the DTC P1000 fault is still present.

This time, when doing the KOER test, I turned the steering wheel to full lock and back, this has solved the DTC P1650 fault.

This time, on the 22km run, the car only stalled on me once, when slowing down with the clutched pressed in 3rd.
 
So, after a a few days of driving the car normally, it still stalls now and again, but it seems to have gone back to it's old self which means it only does it occasionally and at random times (normally at the most inconvenient times :) )

I do have a question regarding the normal behaviour of the engine that maybe you can help me on.

When I got the car, you could really feel the VCT changing the engine at around 4000rpm. However, now the engine power is just one long smooth acceleration. There is no lack of power at any rpm, but accelerating from low revs all the way up to the red line there is no notice in change in the engine, just like any normal engine. I'm guessing that this is a good thing, but could you confirm that this is the normal behaviour of the Puma 1.7 when running properly?

Thanks, as always.
 
I just throttled the hell out of mine...

I got the woosh sound at shifting... like the damn BOV... didn't felt any hard kick in after 4k... reved till 5k...
 

Latest posts

Back
Top