11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH997 Nav in 996
Leading reported evidence
Check first and the 997 bose amp would be required
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
997 PCM2.1 (BOSE) into a 996 may be feasible but the amp outputs to speakers would need to be checked first and the 997 BOSE amp would be required.
Leading evidence: 'Check first and the 997 bose amp would be required' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check first and the 997 bose amp would be required' (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
Nick, I understand what you are saying about changing the coding of PCM2.0 and 2.1 units.
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 also think the Bose amplifier is different for 2.0 and 2.1, so that would be an additional change required.
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
Code the cluster in 996 mode test the car in 986 mode but the cluster reports '?' unknown.
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
Actually incorrect, the PCM can be reconfigured in terms of car type, speaker setup (however there is a different head unit for BOSE), the radio frequency spacing USA/ROW etc can also be altered; true this cannot be done without the use of a dealer PIWIS but it can be done ....
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
Actually incorrect, the PCM can be reconfigured in terms of car type, speaker setup (however there is a different head unit for BOSE), the radio frequency spacing USA/ROW etc can also be altered; true this cannot be done without the use of a dealer PIWIS but it can be done ....
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.
Porsche Club GB: 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: 20261026T112012Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Pic is of a PCM 2.0 a MOST based PCM for the 986 not the PCM 2.1 found in the 987. Main issue will be if the 996/986 can system recognises the PCM 2.1 device. If it doesnt then you wont be able to code the unit correctly for a boxster in terms of speakers , BOSE , or radio frequencies (if the unit is sourced from USA). Considering the cost of the map and lack of functionality Id rather fit a Kenwood or Pioneer unit
Well you did ask![
]
MOST bus: [Media Oriented Systems Transport],defines a multimedia fiber-optic (low overhead, low cost) point-to-point network implemented in a ring, star or daisy-chain topology over Plastic optical fibers [POF].
Actually incorrect, the PCM can be reconfigured in terms of car type, speaker setup (however there is a different head unit for BOSE), the radio frequency spacing USA/ROW etc can also be altered; true this cannot be done without the use of a dealer PIWIS but it can be done .... I am speaking from experience here, having imported both our cars from US to UK.
I could be interested in doing this if I could pick up a decent replacement from a newer generation model. What would I need to look for a 987 device or a 997? Or are they the same?
Am I right that if I have BOSE upgrade the replacement would need to be a BOSE unit?
Nick, I understand what you are saying about changing the coding of PCM2.0 and 2.1 units. I think what Berty is getting at is that if the connections are different on the two units, and if you put a PCM2.1 unit in a PCM2.0-equipped car, the PIWIS might not have the correct connections to access the PCM2.1 unit. I also think the Bose amplifier is different for 2.0 and 2.1, so that would be an additional change required.
Also, the diagnostic program on PIWIS is different for the 996 and 997. The 996 program may not be able to access PCM2.1, or certainly wouldn't have the same coding functions. The 997 program may not be able to access a 996 at all.
I'm sure it is technically possible, but I think it might be a huge amount of hassle.
I didn't say it was easy [
] but it is possible. To code a 997 PCM in a 996 you essentially use the PIWIS as if it were connected to a 997. The other non-PCM units report errors but you access the PCM here.
So post the changes and using the PIWIS in 996 mode it reports the PCM with a '?' as it is an unknown ECU.
The same method is employed for a 996 cluster into a 986. Code the cluster in 996 mode test the car in 986 mode but the cluster reports '?' unknown.
Sorry guys to digress [
]
The the other point, for a BOSE car the 997 amp would technically be required. However, the amp outputs may differ. So 997 PCM 2.1 (Non-BOSE) into a non-BOSE 996 (2003+ MOST car) should be simple. 997 PCM2.1 (BOSE) into a 996 may be feasible but the amp outputs to speakers would need to be checked first and the 997 BOSE amp would be required.
I see what you mean. There would be quite a lot of re-wiring though, trying to match up the connections, as it looks like the plugs and sockets are quite different.
I think we both agree that it is possible, but whether or not it is worth the hassle is another thing.
How about using one of these instead? Far more functionality than you'd ever get from PCM.
http://www.kenwood-electronics.co.uk/products/car/navigation/all_in_one/DNX8220BT/
This is a source reference. Confirm exact model applicability in the original material.
