16 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSpoiler programming
Reported or suspected cause
almost certainly
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
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 report identifying 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.
Reported cause
Your issue is almost certainly with that button panel.
Leading evidence: 'almost certainly' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'almost certainly' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check continuity and voltage drop between the plugs' (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 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
and checked programming of the rear body control module to find it's listed as "Fixed".
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
I believe this is just because a previous owner replaced the OEM CDR with an aftermarket
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
Looking at the wiring schematic both run through the gateway controller so I ran diagnostics on it and found an error code that I cannot clear.
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
This is the 2nd panel and was tested before installing.
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
So thinking that this module is most likely the source of my woes as the rear body control module tests OK and everything else it controls is working fine (hatch release, brake, backup, running lights).
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.
16 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 · 4 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T174436Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Picked up a
2006 Cayman S
six months ago and have finally gotten around to addressing the issue of the rear spoiler stuck in the up position. Console mounted spoiler switch doesn't work to lower it either (switch is tested OK so that's not a problem). But I can raise and lower the spoiler using my
Foxwell
.
So fired up the
Foxwell
and checked programming of the rear body control module to find it's listed as "Fixed". Tried to change it to "Retractable" but no joy. Has anyone dealt with this before?
I’m going to assume you know that the button has to be held to be retracted (when under 30kmh), pressing it won’t do anything.
aside from that, does the rear hatch open with the remote and the step trim button? The rear control fuse could have blown while the spoiler was up. The rear hatch and wing are on the same circuit.
After that the only thing I can suggest is checking that the wiring is plugged in, maybe the previous owner unplugged it to keep it in the up position. You can also check continuity of the wires and test the motors externally.
Theo,
Hatch release, which runs from the same power and controller, works with both remote and manual switch. The fact that I can run the spoiler up and down using the
Foxwell
verifies that the wiring from the rear body control module to the spoiler drive is all OK.
I noticed something else the other day. Tried to setup the
HomeLink
and found that, like the spoiler switch, no operation, no
LED
lit. Looking at the wiring schematic both run through the gateway controller so I ran diagnostics on it and found an error code that I cannot clear. So thinking that this module is most likely the source of my woes as the rear body control module tests OK and everything else it controls is working fine (hatch release, brake, backup, running lights). Found a used gateway module from a
987.1
Cayman
up on Ebay for cheap ($30USD) so will give it a try. Cheap enough to be worth the gamble.
If you can retract the spoiler using your
Foxwell
(scan/programming tool I assume) then most likely the gateway is fine and the problem lays between the switch and gateway.
What is the fault code?
You might be right in that the code I found is C144 - No signal - Communication CDR (display)
I believe this is just because a previous owner replaced the OEM CDR with an aftermarket
Sony
.
But I am also seeing about a half dozen modules with the same fault code: C131 - No signal - Communication gateway control unit CAN comfort. Wondering if these are also tied to the OEM CDR delete?
The first fault is definitely unrelated to the spoiler.
The second code is unlikely to be related to the spoiler, but could be something like the communication between the gateway and switch module that is preventing it from working.
Does your PSM off button work? (Also check
PSE
and sport mode if you have it)
Your issue is almost certainly with that button panel.
Make sure everything is plugged in, then check the wires. If it still doesn’t work then you’ve got a faulty panel, which I think last time I checked was about $200 usd from sun coast
This is the 2nd panel and was tested before installing. Plus I'm still left wondering what's up with the
HomeLink
and is it tied to the non-fuctional spoiler & PSM? Frustrating to be sure!
If this is the second panel then maybe check the wiring? Check for continuity and voltage drop between the plugs on the end.
A failing gateway is not something I’ve ever heard about on any other
Cayman
(or
Porsche
for that matter) so I’m skeptical to think that’s the issue.
Kind of random question. Do you have “sport” mode option? If so, does it work?
Foxwell
units have been known to overwrite some of the coding that affects the spoiler and sport mode, rendering them non operational, iirc. Not 100% of the time, but some users doing some functions (can’t quite remember the details now)
Will have to check on the sport mode option. Appreciate the info on the
Foxwell
, that makes more sense to me. My brother has an advanced code reader with the ability to read and program
Porsche
modules. I'll be taking the
Cayman
up to his place for winter storage soon so will take a shot at the rear body control module again.
Appreciate you and Theo for the help and will update once I find the source of this irritation. I was an electronic engineer with more than a touch of OCD so while this should be nothing more than an annoyance it'll drive me nuts until I find the source of the malfunction. Cheers!
I found that the
Homelink
module on my 2007
Boxster S
was just slightly too old to work with my garage door. I picked up a used module from a 2010 Volkswagen off of Ebay for around $20. (Part # 8K0907410C OEM) The part is shared across the entire
Porsche
, VW,
Audi
lineup and was an easy
plug
and play swap.
Update: After reading an earlier post I went in and verified that the limit switch for the spoiler was working properly using
Foxwell
live data. Now I raised the spoiler using the
Foxwell
and then went into the spoiler programming. Now it allowed me to change it from fixed to retractable and everything with the spoiler is now functional in manual mode. Will have to verify dynamic mode operation when I can get it up to speed.
Now just have to address the
Homelink
which is not that crucial to me. If need be I'll keep using the door opener attached to the visor. But if I can figure that puppy out then I'll post another update.
Thanks for the assist everyone!!
If the factory audio is swapped out - you can expect to see quite a few CanBus error codes (Communications) on various modules. The "Can comfort" refers to the "comfort" bus. There is also an "Engine" bus.. IIRC. Sometimes the messages refer to the departed audio component, sometimes not.
