5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDoor Auto Locking + Seat Memory Coding
Leading reported evidence
Adjust some of this coding although it is quite confusing
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Very happy to have a tool now to check fault codes and adjust some of this coding although it is quite confusing to navigate....
Leading evidence: 'Adjust some of this coding although it is quite confusing' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'gps rollover event' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Adjust some of this coding although it is quite confusing' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
Now if only I could fix the time on the PCM2 to stop showing year 2000 - I guess this is due to the GPS rollover event that happened a couple of years ago and is not fixable.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Very happy to have a tool now to check fault codes and adjust some of this coding although it is quite confusing to navigate....
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I seem to remember reading somewhere that if you get in this situation then you need to reset the function via PIWIS but again I cant find out where.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I also have an issue with one of my keys where whatever I try I can not get it to forget the old seat memory position using the buttons by the sill it has been programmed for.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I also have an issue with one of my keys where whatever I try I can not get it to forget the old seat memory position using the buttons by the sill it has been programmed for.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
gps rollover event
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
Now if only I could fix the time on the PCM2 to stop showing year 2000 - I guess this is due to the GPS rollover event that happened a couple of years ago and is not fixable.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T174436Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I would like to code out the auto locking function of my 996.2 so the doors do not lock above the 6mph limit, the double pull of the handle is infuriating. I cant find the correct place in PIWIS to do this.
I also have an issue with one of my keys where whatever I try I can not get it to forget the old seat memory position using the buttons by the sill it has been programmed for. I seem to remember reading somewhere that if you get in this situation then you need to reset the function via PIWIS but again I cant find out where. My other key programming works fine, but the above makes the spare key pretty useless as the seat moves every time you unlock the car with it.
I have had a bit of success with coding, in the fact that I have managed to tell my car it does not have a CD Changer and stop the annoying pop up on PCM2 every time I started the car. Interestingly it has never had a CDC so I guess the coding just got messed up at some point, I removed it from the MOST list and its now great, just turns on as expected. Now if only I could fix the time on the PCM2 to stop showing year 2000 - I guess this is due to the GPS rollover event that happened a couple of years ago and is not fixable.
Going to be retrofitting cruise too once I can stomach the ridiculous cost of the stalk.
From memory its the version coding in the alarm system you need to alter .. version 4 is standard with i think version 2 being the lock with ignition on.
Never having tried to code one off before so i don't actually know but try each version and see what happens .
key issues with memory seats are often a case of a new key being coded on but the transponder and the remote have beem coded to different positions ..
Ie you have position 1-4 .. if transponder is coded to 2 and remote to 3 then it causes issues with the memory seats .
To fix you would need to check this then if needed move the transponder to the same position as the remote .
It is not possible to move the remote position.
Be aware when moving it you need to know if the position is that of your other key.
To check you insert 1 key .. check transponder position and the inserted key will be shown at the top .
To do this you WILL need ipas codes which if you don't have then you'll need to go into your local OPC with your driving license and the V5 for the car to obtain .
Transponder can be coded on any time in any position if you mess up .. remote and it cant .. mess with that and it's a new key head .
PCM date .. no chance .. or rather if you want to throw a shed load of money at it its possible .
Thanks ill give it a try, I do have IPAS codes. Previous owner bought 2 brand new keys right before I got the car. I guess the coding isn't quite right.
As for the auto lock thing the issue is it doesn't unlock when you go ignition off.... kids / wife virtually ripping handle off door. Ill play around with it as would rather just have it off.
Currently investigating Cruise Control stalk and viability of fitting on OBC from old stalk. Its much cheaper.
Very happy to have a tool now to check fault codes and adjust some of this coding although it is quite confusing to navigate.... and slow.... Windows XP.
What the car is doing is normal .. you have to double pull the interior handle to unlock then open the door .. same on 997 and onwards.
I think you have an early 996 ? i seem to remember that PCM 2 and in the coding for that you altered V=0 ... that might be 997 though .
It's one of those jobs that id need the car in front of me to sort it i'm afraid .. so many different ways on different models .
Try the version coding anyways .
As with anything when coding .. don't alter too many items at once and always make a note of what you have altered so you can return it to original if needed ..
I talk from experience here
With Piwis the main functions are at the top and you need to scroll right to see them all ..
You can Program things like Dme etc if you want to .. logically it should be fine it its a good copy of a Piwis .. up to you if you want to though
This is a source reference. Confirm exact model applicability in the original material.