fullymatted.
Back to search
Planet-9

PIWIS time for coding PCM/NAV

Add to repair workspace
Open repair workspace
Original source
6 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHPIWIS time for coding PCM/NAV

Leading reported evidence

Check on the 1 hour estimate

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 apologize if this topic is not appropriate, but wanted to get a sanity check on the 1 hour estimate.

PIWIS time for coding PCM/NAV
Read full discussion summary

Leading evidence: 'Check on the 1 hour estimate' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check on the 1 hour estimate' (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 · 6 captured posts examined · 1 partial discussions

Frequently discussed actions (1)

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

Check on the 1 hour estimate

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 apologize if this topic is not appropriate, but wanted to get a sanity check on the 1 hour estimate.

PIWIS time for coding PCM/NAV
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.

6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Planet-9: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

1 acknowledgements have no verified action link; they do not establish a repair result.

Outcome without a verified action link

as you can see, I'm still getting the warning triangle /!\ for the Amp section in the main screen (apologize for the quality of these camera phone images)

No unique explicit quoted action; no causal link assigned

Generation: 20261027T051247Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1Original post

Okay. Planning to get the PCM coded tomorrow at the dealership (I did the CDR-24 -> PCM/NAV retrofit), and dealer is quoting me 1hr to code it with the PIWIS . I apologize if this topic is not appropriate, but wanted to get a sanity check on the 1 hour estimate. I would imagize that if I had the tool, it would only take 15 mins. Thanks for any advise.

POST 2Original post

I depends on what the shop rate is at the dealer that's gong to do it, and that usually depends on where you're located geographically, and what the local market will bear. Dealers in big metro areas will charge more because they're expenses are more, and in smaller markets it might be less. The shop rate in Las Vegas is $100. At the dealer in the SF Bay Area I used to go to I think I remember it to be about $125. Call the dealer and ask what their shop rate is per hour, and I'm sure they'll tell you. brad

POST 3Original post

Thanks for the feedback. The San Diego rate is $140/hr, but I was more inquiring whether the actual coding time is going to take 1 hr, not so much the hourly rate. After further thinking it, I think an hour is reasonable so long as everything is coded properly. The have a new coffee machine with various blends and tea, but no Internet connection. The waiting lobby is nice, and since there weren't a lot of cars in, they were able to take me right away. I skipped the complementary wash since my car was already clean. Overall good experience.

POST 4Original post

Not sure the PIWIS coding fixed all my problems. as you can see, I'm still getting the warning triangle /!\ for the Amp section in the main screen (apologize for the quality of these camera phone images) Here is the main screen: Here is the Amp screen. As you can see, it is expecting the 17600/3105, but my exisitng amp is a 17500/3504. I was told that I might need a device swap and that the firmware may not be updatable on the amp. Not sure if this is true: The other potential issue is that the NAV screen doesn't indicate a target device, but is blank: Everything appears to be working and it is now coded for the Boxster, but I don't like the warning triangle and the blank target. Can these be resolved via the PIWIS or via firmware update? Not sure the tech was sufficiently savvy with the PIWIS. Thanks, Jon

POST 5Original post

The triangle is caused by the PCM expecting a different version of the amp software than that is loaded in the amp. There is a function on the PIWIS that can reset this but I wouldn't worry if everything is working ok.

POST 6Original post

Okay, after further parsing older posts here and at another board, it appears that the PCM and DVD drive are at Ver.4 and the amp is at Ver.3. The update disks dated (08.2007) should be able to update the firmware of the amp to Ver.4. Anyone is San Diego care to loan me theirs?

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