11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPCCM+ MOST box defective?
Leading reported evidence
Check connection
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
Double check the connection to the PCCM+ (without being too patronising) first.
Leading evidence: 'Check connection' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check connection' (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
Just checking - did you flip the setting from CAN to AMP?
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
So, I was definitely considering using a fully digital path but that requires a working MOST output.
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
This question is only relevant for those with MY03 or later 996s, which are the ones using MOST.
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.
11 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 · 1 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T135432Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
To anyone who installed a PCCM+ in a MOST 996/986, when you initially attached the MOST box, could you see red light inside the socket when the radio powered up? I have no red light shinning at all.
And, for anyone who has currently such a setup, can you check whether the MOST version number shows up in the version info screen? For comparison, here's mine, version empty:
It appears the PCCM+ does not detect the MOST box. I read about a lot of cases where the MOST box was DOA, I'm wondering if I have another such case.
My car is non-MOST and am not going to use it initially at leat but given I have an aftermarket amp with a Toslink input (and only speaker-level inputs, no line-level) I was thinking about getting a MOST to Toslink converter and ensure a fully digital path to the amp. The way it will be now, the PCCM+ converts the iPhone digital stream to analog, amplifies it to speaker level and then it goes down the line to the amp, where it will be digitised again, processed by the DSP stage, converted back to analog and amplified again and finally sent to the speakers. So, I was definitely considering using a fully digital path but that requires a working MOST output.
Bumping... Can anybody give me a hand? Can someone please check their "Version Info" screen and see if their MOST shows a version or is also empty, despite the MOST box working fine, i.e., having sound playing? This question is only relevant for those with MY03 or later 996s, which are the ones using MOST.
Mine was perfect for a couple of years, and then it went through a period of a few months where it would *randomly* re-boot itself, sometimes catching itself in a crash/reboot endless loop. It would be
super
laggy in input response time (like 20+ seconds).
Now it has stabilized and doesn't do the re-boot cycle, but it has no memory. Every time I start up, the radio presets are all erased and it defaults to the bottom of the tuner. And it resets the trip computer, but what else is new?
Overall, I feel like it really just needs a firmware update / re-install, but that does not seem possible in the world.
That's a bummer. Good thing that here in the EU, consumer products have 3 years warranty and I bought direct from the online Porsche Shop. Could have saved 100€ buying it from the likes of Design911 or a couple of others but thought that having an invoice from the mothership would be a better guarantee. And after seeing your photo, I just sent them an email about this. Hopefully they would send me a new MOST box and one of these as compensation:
Got this as a Christmas present (officially licensed Product!) from Rosepassion the other day and ate it today.
Just checking - did you flip the setting from CAN to AMP? It's possible (I guess with the PCCM+ anything is possible) that it doesn't know to look for the MOST box.
Could have swore I posted a reply last night!
Same as tnj100 - I have text in the MOST line.
I don't remember looking at the box when I installed it but my CDC-4 lights up when powered but not connected, as does my Bose amp, the PCM 2.0 used to and the Mr12Volt bluetooth thingy I used to have also lit up. The network functions by passing signal through each component, which replicates it on to the next one in the chain - if it's not lighting up, it isn't working. Double check the connection to the PCCM+ (without being too patronising) first.
Regarding MOST to TOSLINK to maintain your digital line:
Wired carplay is PCM (afaik), S/PDIF supports PCM so that's fine but don't forget you're going from electronic signal from your phone/HU, into the MOST unit, converting to optical, then converting it back to electronic in your MOST-TOSLINK unit, doing some signal processing to extract the PCM feed from the rest of the data, then converting that back to optical to send it down the TOSLINK cable to the amp, which converts it back to electronic signal again. I can't speak for the quality of the components that do this conversion but this might introduce some jitter if the timing slips a bit. It's not as black and white as "digital is immune to interference". How much this matters and whether you'd notice it is also up to you.
The only brand name MOST to TOSLINK unit I found last time I looked was an Audison unit that cost about as much as a decent amplifier, so I figured I'd spend that on speakers instead.
This is a source reference. Confirm exact model applicability in the original material.
