14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPCM2 showing wrong date
Leading reported evidence
Use piwis and pst 2
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
I am now on 26/02/2000 and I used the PIWIS and PST 2 to try to code the date in the MMI module but it didn't even change.
Leading evidence: 'Use piwis and pst 2' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'being experienced here' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace date' (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
I suspect a similar issue is being experienced here.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
similar issue is being experienced here
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
I suspect a similar issue is being experienced here.
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 can change the date on the PIWIS and the car momentarily accepts it then revers to 02.02.2000.
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
The problem started about a year ago when the date would sometimes not show when the unit was on and would either appear later or if I pushed the 1, 4 and 8 buttons together to soft reset the system.
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
The problem started about a year ago when the date would sometimes not show when the unit was on and would either appear later or if I pushed the 1, 4 and 8 buttons together to soft reset the system.
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.
14 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Porsche Club GB: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 1 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Tried this on my driveway, with car blocked in for security, but did not work.
The date on my 2004 996 turbo PCM2 is wrong and i cannot correct it even with a PIWIS or PST 2. The problem started about a year ago when the date would sometimes not show when the unit was on and would either appear later or if I pushed the 1, 4 and 8 buttons together to soft reset the system. The problem then recurred when I re-started the car later.
However, over the last 2 months, this is no longer an issue in that the date is showing all the time as it should except it started on 01/01/2000. I am now on 26/02/2000 and I used the PIWIS and PST 2 to try to code the date in the MMI module but it didn't even change. When I did it in the Navigation module, it corrects on the screen for 10 seconds then reverts to the pre-corrected date.
Any advice would really be appreciated if anyone else has had the same problem and how to correct it.
Lots of reports of this on PCM2.1 (9x7 cars). One possibility is the GPS "Millennium Bug" desribed here:
https://thenextweb.com/te...-problem-of-their-own/
Thank you. On other forums, there are reports that trying to recode the PCM by parking the car in a garage then leaving unlocked overnight may work as the car cannot receive a GPS signal and somehow the new date sticks. I may try it at some point when I get round to it.
I have exactly the same problem. I was told to leave the car unlocked, engine off but ignition on for a couple of hours in an open space. Was told that PCM2 will reset to current date once it has received new data from the GPS satellites. Tried this on my driveway, with car blocked in for security, but did not work.
I will try the suggestion to leave it in my garage unlocked overnight and see if that works.
From what I can glean from others' success, it seems to work if you have coded the PCM with the PIWIS or PST2 while the car is hidden from the GPS signal e.g in a garage and leaving the car unlocked for a day or two. I don't think just leaving it unlocked in the garage would work.
This sounds like a firmware issue or a standby battery fault on the PCM (common fault on old computer devices). Most units that have a memory will require a standby battery (e.g. LR44) to keep it active in the event main power is lost, such as a car battery in this case. If either loses power then the memory will erase and default to factory settings. A remote key fob would be another example.
I suspect a similar issue is being experienced here. Without taking PCM apart it is difficult to diagnose without seeing the circuit, but pretty sure one of our US cousins on rennlist will have done it. The millennium bug is firmware and would require memory to be flashed to the latest version - I would have thought this would have been a routine fix during a service? Being proprietary units this may prove to be difficult to fix without cooperation from the manufacturer or those in the know.
Weirdly, I was coming on here asking how to set the date, as mine has been incorrect for a while now, and thought I'd done something. It's not a big issue, but it is bloody annoying, as now all I see is the year 2000, and how I wish I was 19 years younger
I tried coding the car in the garage so that it wouldn't pick up a GPS signal but have been unsuccessful. I can change the date on the PIWIS and the car momentarily accepts it then revers to 02.02.2000. Guess I'll just have to live with it. Annoying but its a first world problem really.
A quick follow up with this thread as mine has been doing the 'old date thing' for a few months now and I've just lived with it, but now the clock is showing slow when the car is left and then as soon as you put the ignition on it shows the correct time. Must be a back-up battery failing or failed thing, but I would have thought it would stop altogether and re-set to 0:00 or 12:00. Anyhow just thought I'd put it out there. When I have time I'll pull out the PCM and look for a battery.
No joy so far. It is basically a software issue as described in the link that Richard attached above. Unfortunately our cars are too old for Porsche to issue a fix. Mine now says 02/07/2000.
My date has been blank on the main screen for months and on the programming page it is stuck on 01/01/2000. I went to the dealership for a Nav update and a problem with my radio having no sound. I also asked the tech if he could set set the date so it shows on the main screen. He did the Nav update as well as set the correct date however he said he didn’t have much faith the date would stay. Not much luck with the radio issue either but at least for three days I enjoyed the correct date showing on the main screen however I pulled and re connected the PCM fuse to see if I could get sound out of my radio (which I successfully did temporarily) however the date disappeared again. Both issues are driving me nuts!
This is a source reference. Confirm exact model applicability in the original material.
