fullymatted.
Back to search
911uk

Setting the clock

Add to repair workspace
Open repair workspace
Original source
3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHSetting the clock

Leading reported evidence

Replace time

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

I noticed my clock was a little slow so went to change the time.

Setting the clock
Read full discussion summary

Leading evidence: 'Replace time' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace time' (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.

Read captured replies

1 matching discussions · 3 captured posts examined · 0 partial discussions

Compare 1 other evidence results

Set there

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

- The clock is also set there.

Setting the clock
Frequently discussed actions (2)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Replace time

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 noticed my clock was a little slow so went to change the time.

Setting the clock

Set there

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

- The clock is also set there.

Setting the clock
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.

3 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: 20261026T200546Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

03 996 C4S. I noticed my clock was a little slow so went to change the time. When I got to the menu in the PCM it stated it was in GMT summertime which was +1 hour 8 mins, strange as should be just one hour. I reset to one hour changed to the correct time and saved the settings. After about 5 mins the clock jumped forwards another 8 minutes. When I checked the date and time again it showed GMT summertime +1hr 8 mins aagain. Any ideas.

POST 2Original post

is it an import ? seems to be set to a different country code. ie a country with a + 1hour and 8 mins time difference , but i'm not sure you can even do this take it to or phone OPC for help Rob

POST 3Original post

Does you have PCM? - The clock is also set there. change it on the PCM and it should reflect on the OBC.

This is a source reference. Confirm exact model applicability in the original material.