2 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 Remote fob and memory seats issue - SORTED
Reported or suspected cause
now sorted
Suggestion or failed attempt
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
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 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
Ok, so this issue is now sorted but I thought it may be helpful to future forum users.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
Read full discussion summary
Leading evidence: 'now sorted' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'now sorted' (1 discussions; 0 report identifying it and 1 suggest it). 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.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
Coverage and how to read this overview
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.
2 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 · 1 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T191851Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Ok, so this issue is now sorted but I thought it may be helpful to future forum users.
The issue started when I first purchased my 996 4S. It came with two keys of which one fob worked and the other didn't. The non-working fob lit up when you pressed the unlock button but did not remotely unlock the car. You had to manually unlock the car with the key and get it in to the ignition within 10 seconds before the alarm went off. The key then started the car fine but I wasn't content with this. After trying some of the suggestions on here and the web (several different efforts to wake the key up, re-pair it, clean it etc.) I took it to my local indy who said this was a common fault and it needs a new fob, £140ish.
This was then ordered and paired to the car and worked fine...EXCEPT the seat memory started playing up. I unlock the car and the seat moves all the way forward and the mirrors move down. Once the key is in the ignition, the car knows which seat position and by holding the key symbol or position 1/2, the seat and mirrors return to the memory position. This was becoming annoying as I couldn't get in with the seat forward so it was a case of unlocking, putting the key in to the ignition and then holding the memory button.
Why was the key remembering another position when it was remotely unlocked?? Well a trip back to the indy for them to tell me it is most likely 'operator error', a few hours later to be told it is actually something within the coding which they need to have a further look at, can I bring it back.
A little help from deMort who got it spot on. He soon told me that when the key had been originally set up, the indy had paired the remote to the car but failed to program the transponder to the same position (there are 4 possible positions, 4 keys)
So back to the indy and they solve the problem, after ordering the pairing sheet back from OPC apparently, they managed to 'line' the paired keys and transponders up correctly but claimed that this was more down to the previously faulty key being retained.
Happily, the car is now unlocked and the seat stays where it is or moves to its memory position if for some reason it is not in it. Hopefully this helps people if they have the same issue in the future.
Of course, a big thanks to deMort! :clap:
Basically when you code a key onto these with memory seats then it has to be on the same position ..
we have 1-4 for key codes .. memory seats and they MUST be both coded on the same position .. ie pos 3 for both ... transponder and remote need to be on the same number .
This is an old fault which every garage should know by now but can catch all of us out .
it's a glitch in the software which only affects memory seats .
non memory seats and you can code it where ever you like .
This is a source reference. Confirm exact model applicability in the original material.
