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)

Richard Hamilton

Contributing Members
  • Posts

    1,830
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Richard Hamilton

  1. Try removing the USB and OBD2 cables from the VCI. Spray the connectors with some contact cleaner, wipe off the excess, and reconnect. A poor connection will cause the error you are getting.
  2. I'll echo what Loren is saying. No problems connecting to a 996T. It may also be a problem with your VCI. FWIW, v18.150.500 is a fake. 18.100 was the last official release of the software. Try running Regedit. It will likely take you straight to the registry value which has been manipulated.
  3. Well, a quick Google took me to Suncoast Porsche at $255: https://www.suncoastparts.com/product/PCM21UPDATE.html I'll PM you a couple of other options.
  4. Take a look at item 6) on this thread: Of course, you can't tell which side is the problem without a diagnostic check.........
  5. 04035 means your system is at what Porsche call Standard Production Status. You need to update it to Level A, then Level B, and finally Level C. After doing that, you will need the latest map disk, because your old map disk won't run. I can't advise where else to get the US map DVD, other than going to a dealer. The disk might not be as expensive as you think, so it is worth asking. As I said before, when I have bought map disks from Porsche, via my Porsche specialist, they have come complete with the update CDs. I have heard that people (in the UK) buying them over the counter at a Porsche dealer come with the update disks removed.
  6. AT is an abbreviation of Austausch - German for Exchange.
  7. The Fuchs ATF seems to be readily available here in the UK.
  8. I know a fellow in France who has converted Middle East units to EU maps. I think you can have more than one region on the system, but either way you have to have an Activation Code for the EU maps, which is entered using a PIWIS, before loading the maps.
  9. The 996 Turbo box is a derivative of the Mercedes 722.6 transmission. SHELL Spirax S4ATF3403 is quoted as a replacement for 3403-M115 by a supplier I use over here (lubricantsupplies.co.uk). It has MB approval, but no specific Porsche approval that I can find. Porsche release approved oil lists on a regular basis. Engine oil lists seem to be released at least once a year, but the last one for Approved transmission fluids for the 996 I have seen is dated 2008, and shows the 3403-M115. The lists are published as Technical Service Bulletins. Google that and you will find sites that you can download them from. Edit: Are you sure you can't get Fuchs Titan 3353 over there? A quick Google took me to this site: https://lubricants-ils.com.au/product/fuchs-titan-atf-3353/
  10. Can you get Shell ATF 3403-M115 over there? That is the other approved ATF for the 996.2 and Turbo.
  11. You'll need a PST2 or PIWIS tester, and the Porsche IPAS security codes for your car. I once updated the fuel map in the DME of my 996T and it was fairly straightforward. Just a note of warning. Yours is DME5.2.2 and a lot of clone PST2s don't have good OBD2 cables. When programming 5.2.2 the software applies a voltage to one of the OBD2 pins during the programming routine. A lot of clone cables don't have this connection. Therefore I would go to a reputable specialist, or someone who has done it before. It is also likely you will have to go to a specialist for the IPAS codes, as Porsche are reluctant to give them to individuals. There may be other methods of flashing the fuel maps without the codes (as tuners do) but I don't know if they can change it from US to RoW.
  12. I have coded several clusters for Cruse Control, including 2003 & 2004 models with a PIWIS tester, and never had any problems with the green cruise light. However, I do tend to use a PIWIS1 or PST2 when working on 986's. Both systems were based on the Bosch software (for Bosch control units), whereas PIWIS2 was made when they started switching over to Siemens (for the 9x1). I know there were several cases of the early versions of the PIWIS2 software bricking instruments clusters when activating OBC and Cruise, so perhaps there are still anomalies.
  13. I've never heard of anything like that before. The only thing I can think of is that the program is corrupted, or the DME is faulty. I guess you could try getting it re-flashed. Sorry - not much help. I assume that the car runs fine, and you don't have a CEL. As the RoW 2.5's aren't OBD2 compliant, many of the fault codes don't throw a CEL.
  14. Is this a 2.5 Boxster? Have you had the car for long? Could it have been re-programmed with the US fuel map by mistake, or have a US DME fitted?
  15. Locking the module sets the vehicle type (986/996), but I am not sure if it sets the other parameters. The section of the manual which describes changing the module says that after the new module is fitted it has to be locked, but nothing else. The diagnostic manual says what I showed in my last post, so I presume it could be done after locking. I have only locked an airbag module once, about 10 years ago, and can't remember what options the locking routine presented me with. The only conclusive way to tell would be to plug in a Porsche Tester and try. Running my PIWIS2 in simulation mode it looks possible though. That option not being easily available to you, I would be tempted to see if the wiring exists to the X-16 and X-17 plugs under the seats. If it is there, you could just fit US buckles, and you should be able to clear the faults.
  16. The diagram shows that the US buckles contain switches and resistors. RoW cars only have a simple switch on the driver's buckle which is grounded when the buckle it inserted. So to rewire it to simulate the US buckles is not as easy as I first thought. If the wiring is in place under the seats, it might be possible to fit US buckles though. This is what the WSM shows as the coding options: The following equipment features can be changed: – Driver’s/passenger’s airbag – Buckle – Child seat occupancy (passenger) – USA (vehicles) So I think your easiest option would be to get it re-coded, or just ignore the fault codes if you don't get the airbag light.
  17. Bear in mind that the seat belt buckles on RoW cars are not connected to the airbag module, as they are with US cars. I suspect that is your problem, as the car is a Japanese model and you have fitted a US module. The airbag unit is looking for a contact which doesn't exist. The seat belt buckles on RoW cars are only connected to the instrument cluster, for the warning light and buzzer. You may be able to work round this by re coding the airbag module to use RoW settings. Alternatively, it would be easy enough to rewire the connector to match US spec. I will look at the wiring diagrams when I get to my PC in the morning and post again.
  18. I wonder if it might be the microswitch inside the door lock, which senses that the door is locked, has stuck, and the system thinks that the door is locked (when it isn't). That would cause the handle microswitches not to function. If you can get it on a Porsche tester, you can view the switch contacts, which should help in the diagnosis.
  19. I don't know about US cars, but over here the Stop/Start is set to default "On". This can be changed with a PIWIS tester to Default "Off" or "Remember Last".
  20. I had B6's on my 996T. I had a full suspension refurb at the time. Check the ride heights. The rear sometimes sags, giving a nose-up attitude. The overall improvement was dramatic, the car felt so 'planted' afterwards, and the ride was much more compliant.
  21. Bilstein. A re-valved version of their B4 model.
  22. It probably isn't the sort of thing dealers normally do. You need to get the coding in the "MOST Installed" section of the PCM to match the hardware attached to the system. Then run the Handover Routine to reset everything.
  23. I just remembered this, which I posted a while ago. There is a pdf of the Individual Memory setting section of the manual.
×
×
  • 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.