Jump to content

Welcome to RennTech.org Community, Guest

There are many great features available to you once you register at RennTech.org
You are free to view posts here, but you must log in to reply to existing posts, or to start your own new topic. Like most online communities, there are costs involved to maintain a site like this - so we encourage our members to donate. All donations go to the costs operating and maintaining this site. We prefer that guests take part in our community and we offer a lot in return to those willing to join our corner of the Porsche world. This site is 99 percent member supported (less than 1 percent comes from advertising) - so please consider an annual donation to keep this site running.

Here are some of the features available - once you register at RennTech.org

  • View Classified Ads
  • DIY Tutorials
  • Porsche TSB Listings (limited)
  • VIN Decoder
  • Special Offers
  • OBD II P-Codes
  • Paint Codes
  • Registry
  • Videos System
  • View Reviews
  • and get rid of this welcome message

It takes just a few minutes to register, and it's FREE

Contributing Members also get these additional benefits:
(you become a Contributing Member by donating money to the operation of this site)

  • No ads - advertisements are removed
  • Access the Contributors Only Forum
  • Contributing Members Only Downloads
  • Send attachments with PMs
  • All image/file storage limits are substantially increased for all Contributing Members
  • Option Codes Lookup
  • VIN Option Lookups (limited)

Recommended Posts

Posted (edited)

Hi!

I have been reading lots of old threads but still haven't really found someone in a similar situation as me, hence this additional thread on the subject.

My car is a 986 S 2002 with 125k miles and I think my MAF is bad because of CEL P1128/P1130 (also P0410/P1411) and a bit of a rough idle. Tried cleaning it two times with no difference.Pulled the MAF and to my surprise I found a 996.606.124.00, which I thought only existed on the 2000 models. Since it is a 2002 model I expected to find a 996.606.125.00. I don't know the history of the car so maybe an earlier owner installed the wrong model.

- My question is should I fit a 996.606.124.00 or a 996.606.125.01?And in case the answer is: Depends on your DME flash version, can I determine this using my Durametric?

Additional info:Chassis # 9802U661342Engine #M96/216720XXXX

Any advice is appreciated

Best

Andy

Edited by Andy_C
  • Moderators
Posted

Hi!

I have been reading lots of old threads but still haven't really found someone in a similar situation as me, hence this additional thread on the subject.

My car is a 986 S 2002 with 125k miles and I think my MAF is bad because of CEL P1128/P1130 (also P0410/P1411) and a bit of a rough idle. Tried cleaning it two times with no difference.Pulled the MAF and to my surprise I found a 996.606.124.00, which I thought only existed on the 2000 models. Since it is a 2002 model I expected to find a 996.606.125.00. I don't know the history of the car so maybe an earlier owner installed the wrong model.

- My question is should I fit a 996.606.124.00 or a 996.606.125.01?And in case the answer is: Depends on your DME flash version, can I determine this using my Durametric?

Additional info:Chassis # 9802U661342Engine #M96/216720XXXX

Any advice is appreciated

Best

Andy

The 124.00 MAF is an early (2000 model year) e-gas unit; if you went from the 124.00 to the 125.00 (now discontinued) or 125.01 your DME will need to be reflashed (PIWIS or PST II only) to accept it.

That said, the P0410 and P1411 are secondary air injection system failure codes, not the MAF, but are often mistaken as MAF related codes.

Posted

Do some reading here .... it will give you an idea of the complexity of the systems you are dealing with, some pictures, flow charts, etc.

My similar problem was never really resolved but I do know the mechanic inspected and tightened all fittings and the problem was gone for 5 years. Even he wasn't sure he had found the problem and I left his shop with the admonition to come back if it happens again. But as JFP has said, my problem cause could be totally different than yours yet for the same codes.

Posted

Thanks both of you for your responses. I will research and troubleshoot some more before I throw more money on the problem without really knowing the root of it (already replaced a perfectly fine AOS due to a theory I had... :-) )

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.