21 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHBosch 5.7 PSM/ABS Module rebuild services
Leading reported evidence
Repair dme
Performed · outcome unconfirmed
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 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
The DME was repaired and the O2 fault is now gone, but the ABS/PSM issue remained exactly the same before and after the DME repair.
Leading evidence: 'Repair dme' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust switch' (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 · Original poster
- Ran through troubleshooting steps for code 4460 as outlined in the FSM - everything checks out
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'm using a VAS6154 V1.6.6 Full Chip with PIWIS III v41.500 (Engineering Mode).
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.
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.
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
The only other work done around that time was sending the DME (ECU) to ECU Doctors to repair an O2 sensor fault that was causing the check engine light.
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.
21 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.
2 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I had this happening and unplugging and replugging the pressure sensor a few times fixed it.
Dealing with a 4460 ABS code in my 2001 C2S.
The ABS and PSM lights come on when the ABS system does the self test(?) at around 30mph and the ABS unit is showing code 4460. When the car is cycled off and then back on, the lights will go through the same sequence (off until ~30mph when I can hear the ABS pump run)
So far I've done the following troubleshooting:
- Replaced brake switch and confirmed functionality by following troubleshooting steps outlined in the FSM for fault code 4340 (Brake light switch Fault)
- Ran through troubleshooting steps for code 4460 as outlined in the FSM - everything checks out
- Live data from wheel speed sensors are accurate
At this point, the FSM indicates the ABS/PSM module is bad. I've seen a few online services that offer rebuild services for ~$300. Has anyone used any of these services? Did it fix your problem?
Ive been driving without ABS/PSM for several thousand miles now because my ABS module is bad. But Its a C4, and I figure 911s didnt have ABS before the early 90s, so what the hell, do I really need it anyway? Plus, I enjoy a little wheel spin every now and then. I do hate the lights though. Im going to get a rebuilt replacement one of these days and have my shop swap it, bleed it, etc...
you can try putting a proportioning valve on the circuit going into the PSM pump. The 30 miles an hour is a check for pressure. Getting this fault is common with people who switch over to the GT three master cylinder, I know it was happening to me.
if you unplug the PSM pump does it still give you the ABS fault?
I was saying to try the porportioning valve to see if that makes a difference even with your car being stock.
I had this happening and unplugging and replugging the pressure sensor a few times fixed it.
If you want to get into the module a company called Module Masters can fix it, or buy one on ebay with same bosch part# and swap it.
I have said this many times on this Forum... The ABS code 4460 for "pressure sensor" is 99 times out of 100 due to an intermittent functioning or misadjusted brake light switch...
The brake lights MUST come on BEFORE the pressure sensor value starts to rise, otherwise it will set the fault and turn on the warning lights...
The Factory Work Shop Manual does NOT mention this !!!! Ask me how I know .........
I just installed a brand new brake light switch and I'm still getting the ABS/PSM lights. It only happens when driving and not when I press the brakes. I tried adjusting the switch but same thing. Did I buy a bad switch maybe?
If you have a PWIS you can watch the brake light signal and also the Pressure Sensor Values at the same time to see the "timing " of the two....... If the pressure sensor rises before the brake light signal it will set the code...
Of course you could also have a problem with the Mater Cylinder adjustment not letting OFF the pressure and the pressure builds with heat/driving....Should be a very slight pressure on the Sensor at all times
Hi everyone,
I'm hoping someone has run into this before.
I have a 2004 Porsche 996 C4S 6-speed manual with the ABS and PSM lights on permanently. The cruise control is also disabled.
Using PIWIS III, the only fault code I'm getting is:
5281 – Variant coding error (Version coding error)
Here's what I've tried so far:
New battery installed
Steering angle sensor calibrated
Cleared faults multiple times
Verified the PSM module is the original unit
VIN and transmission (manual) are correctly identified in the PSM
Attempted to recode the module using PIWIS (Complex Coding), but it fails with "29000 – Negative control unit response" and the 5281 fault immediately returns.
Has anyone experienced this before?
Could this be:
a corrupted PSM EEPROM,
a failed PSM module,
or is there another coding procedure I'm missing?
Any advice or similar experiences would be greatly appreciated.
Do your brake lights work? Common for the brake light switch at the brake pedal to fail. That disables the cruise control and also effects the ABS/PSM. I would start there.
When did this problem start ? Did you buy the car with this problem ? Any recent work on the car prior to this problem occurring ?
First off I would get another PIWIS Tester ( known good one ) and try to do a manual coding of the PSM module since that is the fault code you have....
With that fault either the codeing is wrong for the car ( and your PIWIS is not working well ) or the Module is faulty..
I would also try your PIWIS on another car of the same model just to see how it works......Nothing worse than a piece of Test Equipment that is unproven/can't trust ...
PS :: also you need to start your own technical thread and not hy-jack someone else's that probably has a different problem from you ...
Sorry for hijacking the thread but thanks for the reply.I bought the car about a year ago and it did
not
have this problem.
Toward the end of last season, the ABS/PSM lights would occasionally come on if the car had been sitting for a week or so, but they would usually go away after 1–2 minutes of driving or after restarting the car.
After taking it out of winter storage this spring, the lights have stayed on permanently, and the cruise control stopped working at the same time.
The only other work done around that time was sending the DME (ECU) to ECU Doctors to repair an O2 sensor fault that was causing the check engine light. The DME was repaired and the O2 fault is now gone, but the ABS/PSM issue remained exactly the same before and after the DME repair.
I'm using a VAS6154 V1.6.6 Full Chip with PIWIS III v41.500 (Engineering Mode). I also verified that the VIN and manual transmission are correctly identified in the PSM module.
I agree that I'd like to try another known-good PIWIS installation before concluding the module itself is faulty. I'm also trying to find another 996 locally so I can verify that my PIWIS setup is working correctly.
Quick update on my 2004 C4S with fault
5281 – Version Coding Error
.
I sent the original ABS/PSM module to XeMODeX for testing. They found no fault with the module and returned it without repair.
The module has never been replaced, and the problem developed gradually: the ABS/PSM lights were initially intermittent after the car sat for several days, then became permanent after winter storage. Cruise control stopped working at the same time.
The battery and brake-light switch are new, the steering-angle sensor has been calibrated, wheel-speed signals appear normal, and the VIN/manual transmission are correctly identified. Manual coding with my PIWIS still fails with
29000 – Negative control unit response
, and code 5281 returns immediately.
Since the module tested good, what would you check next: another known-good PIWIS installation, PSM power/grounds, CAN communication, or something else?
Any guidance on specific PIWIS actual values or electrical tests would be appreciated.
Final Update
When ECU Doctor repaired the DME, the wrong VIN was entered and the coding was incorrect. The car was being identified as Tiptronic, and several coding values were set to zero.
A Porsche dealer reprogrammed the DME with the correct VIN and manually entered the proper coding. Once that was done, the other modules accepted the programming.
Fault 5281 is now gone, and the ABS, PSM, and cruise control are all working normally. The original ABS module was never faulty.
Unfortunately, I am now back to the original issue I paid ECU Doctor to repair: the Bank 2 post-catalyst O2 sensor heater fault.
Wow! What did ECU Dr. Have to say about their error? That�s some pretty lame work if you ask me� sounds like they mixed up your module with someone else�s�
Porsche Dealer to the rescue!!
So this problem started right after the DME reprogramming/repair ? ..........Had you told us that bit of info we could have gotten you there faster ...
But glad you got it sorted annyway.....
