14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPCCM+ and random odo resetting
Reported or suspected cause
micosd card or perhaps the usb port
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
There is an Upgrade button which takes you to a new screen where you can load a new file by probably a MicoSD card or perhaps the USB port on the breakout box, so this is not something that should require PIWIS.
Leading evidence: 'micosd card or perhaps the usb port' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'micosd card or perhaps the usb port' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check iphone' (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 remember a wierd radio issue in about 2005 where the Radio would just change stations by themselfves randomly...., and it turned out to a problem with the Radio Stations sending out an improper ID Code in thier trasmissions....It was only a problem here in the US...and the Porsche Engineer had to call the offending Radio Station(s) and tell them how not to send out the bad ID Code....lol
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
Imagine having to pay Apple to check your iPhone to verify it has a bug and then install new firmware update...
Replace stations by themselfves randomly...., and it turned out
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
I remember a wierd radio issue in about 2005 where the Radio would just change stations by themselfves randomly...., and it turned out to a problem with the Radio Stations sending out an improper ID Code in thier trasmissions....It was only a problem here in the US...and the Porsche Engineer had to call the offending Radio Station(s) and tell them how not to send out the bad ID Code....lol
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
Sometimes it's just a few miles and I've had 300ish reset free miles before too.
Replace stations by themselfves randomly...., and it turned out
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
I remember a wierd radio issue in about 2005 where the Radio would just change stations by themselfves randomly...., and it turned out to a problem with the Radio Stations sending out an improper ID Code in thier trasmissions....It was only a problem here in the US...and the Porsche Engineer had to call the offending Radio Station(s) and tell them how not to send out the bad ID Code....lol
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
While the 996 doesn't have any steering wheel controls I know that when using the Porsche maps for navigation, it can display turn directions in the cluster display screen.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
micosd card or perhaps the usb port
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
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
There is an Upgrade button which takes you to a new screen where you can load a new file by probably a MicoSD card or perhaps the USB port on the breakout box, so this is not something that should require PIWIS.
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 remember a wierd radio issue in about 2005 where the Radio would just change stations by themselfves randomly...., and it turned out to a problem with the Radio Stations sending out an improper ID Code in thier trasmissions....It was only a problem here in the US...and the Porsche Engineer had to call the offending Radio Station(s) and tell them how not to send out the bad ID Code....lol
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.
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: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi Everyone,
I've seen this issue reported on various sites with the words "There's a fix coming". None of the threads mention what the fix is. Today I saw on FB someone posting about "I've just installed the PCCM+ and I don't get the ODO reset issue" so obviously fixable.
I've rung the local dealership but they're clueless on the issue and want 2 hours dx time and cannot fit me in for 8 weeks.
So... is anyone aware of what the issue is and what the fix is?
thanks
I've been following this for a while as I have the same odometer reset issue as well, which happens at random. Sometimes it's just a few miles and I've had 300ish reset free miles before too. From what I understand it's an issue isolated to the earlier produced models of the PCCM+ while the later produced ones have the fix aka newer firmware installed.
I have reached out to 3 different dealerships, including the one where I purchased the unit and have gotten the runaround and no help outside of also wanting to schedule a diagnostic session for which I'd need to pay for. While I'm not opposed to paying someone for diagnostic time, this is now a decently documented issue (at least via forum posts) and it's a bug that is tied to the product and should be handled by Porsche. All it takes is providing a file download and directions on the site for a self update OR an option to have it done by the dealer. Imagine having to pay Apple to check your iPhone to verify it has a bug and then install new firmware update... This would be all over news and while this is no different it's on a microscopic scale by comparison so it's not really talked about.
The PCCM+ has a "secret" menu that you can access by holding the Version Info button in Settings for several seconds. There is an Upgrade button which takes you to a new screen where you can load a new file by probably a MicoSD card or perhaps the USB port on the breakout box, so this is not something that should require PIWIS. I believe I read on 911uk.com that someone that has access to PIWIS couldn't find anything related to updating the PCCM+.
I am now strongly considering writing to Porsche NA with this and describing my experience. I'll keep on following up until something comes of it (I hope). Because I would be the only voice, which probably wouldn't accomplish much, I'm thinking of creating separate thread here and post on Porsche related pages on Facebook and reaching out to the community on Instagram to gather more examples where this is happening to others so I can either include them in the outreach to Porsche NA or have them send in a pre-written email raising the issue. Basically, amplify this as much as possible. I do have a few lawyer friends so I'd be curious to get their take and see if a manufacturer is at all obligated to support a product with updates like PCCM+ and if they have any suggestions. Not sure if anything will come of it but I think it's worth a try. Other than this bug I really like the unit and would like to keep using it but not having a simple function of trip odometer is annoying and Porsche is just being lazy about sharing a fix that already exists. On the other hand, most dealers don't care enough either as they would most likely need to reach out to Porsche Germany to raise the issue and get the fix. If you can't provide support for a simple radio, it doesn't instill a lot of confidence in the individual and them wanting to do any business with the brand or dealer. As the saying goes: "
Whoever can be
trusted
with
small things
can also be
trusted
with big things. Whoever is dishonest in
little things
will be dishonest in big things too."
Not 996... Porsche sells PCCM+ for first gen Cayennes too. The 955 generation supposedly works well. The 957 generation, well the PCCM+ causes random check engine lights. Porsche's fix was to disable canbus in the Cayenne PCCM+ so no steering wheel controls or insturment cluster integration anymore. They did fix the check engine light though!
So I would not expect a whole lot from Porsche.
That's good to know. Seems like PCCM+ has had it's issues with most/all its applications. Makes me now wonder if there is a way to disable canbus communication in some menu on the PCCM+ for the 996. I can only guess that the radio sends some sort of signal to the gauge cluster via canbus causing the reset. While the 996 doesn't have any steering wheel controls I know that when using the Porsche maps for navigation, it can display turn directions in the cluster display screen. Since I mainly use Android Auto I don't need that feature so disabling the canbus could potentially be a workaround, if it's at all possible. On the other hand, is the Bose amp connected via canbus in any way? If so, that could cause another issue. Who knows...
If there is a fix there should be a Technical Service Bulletin ( with a Number ) on the issue in the Data Base...I would think the TSB # would have been posted if there is one ?
Someone with PPN access would have to search for the TSB...
I remember a wierd radio issue in about 2005 where the Radio would just change stations by themselfves randomly...., and it turned out to a problem with the Radio Stations sending out an improper ID Code in thier trasmissions....It was only a problem here in the US...and the Porsche Engineer had to call the offending Radio Station(s) and tell them how not to send out the bad ID Code....lol
My local dealer said that he couldn’t find a TSB for the PCCM +. The odometer fix over in the UK about 4 years ago was done by the local Porsche OPC with help from Germany. The customer was given a SIM card to insert into the PCM+ with the new firmware. A PIWIS was not required to load the patch.
That's the story I heard as well. I feel like that at this point you need someone you know personally and who also happens to work at a dealership to help with this. They need to reach out to Germany to get that firmware since they haven't bothered to create a TSB for it. Sadly most dealers I talked to are clueless about it and don't give a flying you know what as it takes extra effort on their end and it's something that a customer can do themselves since PIWIS is not needed to load the firmware. I'm hoping that at some point a person that is able to get their hands on the firmware will be able to post it somewhere for download for the rest to use.
I just had my car serviced at Sunset Porsche today and spoke to the service manager and shop foreman. They are not aware of the random odometer reset or a TSB related to said issue. Porsche has screwed the pooch once again!
There are a few threads on this topic floating around. It seems like there certainly IS a fix, despite no TSB being issued. Not sure if it makes a difference that this is out of Porsche's classic catalogue. Based on the screenshot below from the other thread it seems like you need to have family working for the dealer or literally know someone very well. Sadly, that kind of customer support does very little for the brand to convert a 996 owner to customer of another Porsche. Based on the feedback from jaybart, this requires little time to complete and in my mind the service advisor can't really be bothered as it's not really revenue generating for them - not that something like this should be.
I did have someone randomly email me from a local Porsche dealer about booking some service for my car and I brought up this issue with them. The person said they would investigate and get back to me but nothing for 2 week. Looks like it's time for a follow up....
Let everyone know if you get anywhere.... I called the three dealers in Sydney Australia and all three knew zero about patching... Refused to entertain a quick check to see if one exists. they just want diag. time. 3 hours for one, 1 hour for another
This is a source reference. Confirm exact model applicability in the original material.
