5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHKey repair (996.1 1 button fob)
Reported or suspected cause
same frequency, bang
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
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 report identifying 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.
Reported cause · Original poster
For the working key it was the same frequency, bang on, every single time.
Leading evidence: 'same frequency, bang' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'same frequency, bang' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Recommend somewhere' (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 performed work without a confirmed outcome
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.
Performed · outcome unconfirmed
the usual issue is they don't get used for a year or more ..
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
Has anyone else had this/can recommend somewhere that can fix it?
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
For my spare key, it was all over the place (I can't remember the exact frequency) but instead of 433.6, it would be 433.2, 434.1, 433.8, changing with each button press.
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.
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
For my spare key, it was all over the place (I can't remember the exact frequency) but instead of 433.6, it would be 433.2, 434.1, 433.8, changing with each button press.
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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
the customer was unaware of this and why his new key fob didn't work .
Hi Folks,
My second key is bust. Sort of.
Starts the car fine, and will unlock the car.... on about the 40th attempt.
I had someone take a look - they were putting our Land Rover keys in new shells - and he showed me that the key isn't sending a signal consistently, and the frequency is inconsistent (my primary key is bang on every time).
Apparently, this is common, and its the transmitter failing. He wasn't sure if he could fix it, and is going to come back to me.
Has anyone else had this/can recommend somewhere that can fix it? Or is this a 'go to Porsche' problem?
I'm not sure if that will help - but thank you.
The chap showed me the frequency the key was transmitting on. For the working key it was the same frequency, bang on, every single time.
For my spare key, it was all over the place (I can't remember the exact frequency) but instead of 433.6, it would be 433.2, 434.1, 433.8, changing with each button press. Eventually you'd 'by fluke' get the right transmit and it would work. That might take 30-40 presses.
Short answer .. you need a new key fob and have it coded to your car .
This can be done at an OPC or an Indy ( porsche specialist ).
The fob is the main cost of the bill so you will only save a bit on the labour rate .. ie 0.5 hrs to replace is standard and my garage is £100 plus vat per hr .. OPC around here are over £200 plus vat per hr .
Long answer .. there are 2 parts to the fob .. a pil which is read by the ignition lock .. as long as its coded and the correct one for the car then the car will start.
The second part is the fob signal to unlock the car .. obviously this is a wireless transmitted signal which the alarm control unit receives , recognises and unlocks the car .
In the UK this is 433 mhz and this alters for various countries so you must be aware of the original market the car was built for .. i have seen a UK car that was a Cyprus one and it uses a different frequency ... the customer was unaware of this and why his new key fob didn't work .
Look at your key fobs and you should see 433 on the back of them .
Ok so 433 mhz .. it's not just going to be .. 433.1 as that would give 9 combinations .. it's more like 433.1368 ..
The system uses a rolling code as well .. hence on a successful operation in that the fob is recognised the frequency will alter which is based on an inbuilt logarithm .... hence after use you will see a different frequency .
The fact your key is altering frequencies with no successful unlocking already proves its faulty or so far out of range its attempting anything .
It's also common as muck for spare keys to stop working .. the usual issue is they don't get used for a year or more .. by then the frequencies have rolled on so far with the main key that the spare is too far out of sync to catch up ..
I've seen brand new and unused spare keys needing replacement due to this .
As such .. if you get a new one .. rotate it with your main key every 3 months .. more so if you use the car many times a day .
I must say .. my short answer is the easiest to follow lol .
