6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHWierd ! Digital speedo started displaying km/h!
Leading reported evidence
Replace clock back an hour
Performed · outcome unconfirmed
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 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 · Original poster
On the way to work today I changed the clock back an hour..
Leading evidence: 'Replace clock back an hour' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust with the stalk' (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 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
If not, the dealer has to fix, otherwise you can adjust with the stalk.
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 will check for on-board computer - but I don't think so.
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
BTW, dont depress the reset button first, cause that changes the function to "clock".
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
turning the clock reset to the left changes the travel computer readouts to metric.
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.
6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 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: 20261027T053112Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
On the way to work today I changed the clock back an hour.. immediately afterwards I noticed that the speed readout converted to km/h and the odometer as well... The analogue readout continued as mph.
The outside temp stayed at Farenheit.
As I cursed my way to work - the bl%&#$ airbag light came on !
I have searched the archives and the Rennlist FAQ and found a long set of fixes for the airbag light but no mentions of the wierd speedo readout...
Using all my technical knowledge I thought of a few causes:
1) maybe the car worked out that I have spent most of my life driving in Australia;
2) maybe the car was originally Canadian?
3) had some kind of slow moving y2k bug?
4) was upset that we went off daylight saving time!
Any more substantive ideas would be appreciated - its really off-putting!
Thanks
Turn the clock button to the left and hold it for 5 to 10 seconds. I think that should reset your digital readout to mph.
My 996 in Canada is in kph but I can change it to kph by turning the clok **** to the left and holding it for 5-10 seconds. I would think that yours works the same way.
Wilam is correct. turning the clock reset to the left changes the travel computer readouts to metric. BTW, dont depress the reset button first, cause that changes the function to "clock". Just turn the button to the left anf hold for a few seconds.
Wilam and Gretch you were spot on! I turned the clock **** and held it there and hey presto back to MPH. Very cool. Thanks.
All I need to do now is get that airbag light to go off and I will be smiling again - was thinking of a good piece of black tape over the light! Only kidding will get it done properly...
This is a source reference. Confirm exact model applicability in the original material.
