23 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHStrange PSM/ABS issue - need help
Reported or suspected cause
now
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 · Original poster
ok, so to follow up on that: problem is now solved.
Leading evidence: 'now' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'now' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check brake light switch usually the culprit' (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
- during this time I also installed 3mm wheel spacers at the front wheels
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
- during this time I also replaced a broken tail light and used an LED tail light
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
- during this time I also replaced a broken tail light and used an LED tail light
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 suspect 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.
Suspected cause · Original poster
Would be completely random that MAF issue is coming now when I have tinkered with all those other things that could be related, but I guess I should keep that in mind.
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.
Suspected cause · Original poster
Would be completely random that MAF issue is coming now when I have tinkered with all those other things that could be related, but I guess I should keep that in mind.
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.
23 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T000231Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all,
I have a strange issue that has just started and I need some help to figure out what's going on. Been doing a lot of searches and I have some idea but things don't add together well.
Here is the back story:
- car has been parked for about 1 month waiting for some parts
- during this time I fixed 1 brake line and did a brake bleed for that corner
- during this time I also replaced a broken tail light and used an LED tail light
- during this time I also installed 3mm wheel spacers at the front wheels
- my tire sizes are not matching very well but this has been the case for the last 5k+ miles (235/35/19 fronts and 295/30/19 rears)
The issue:
- I get a PSM/ABS error message on dash
- warning lights disappear after I re-start the car
- DME code read by Durametric is P0571 (brake switch: signal implausible)
- warning light appear at 75mph (without touching the brake) at the same time that the spoiler raises
- no issue at all as long as I stay under 75mph
Note that my cheap cable running durametric 3.0.15 SW version cannot read the actual ABS/PSM module
yes it seems to be the most common root cause and it could be that my wife pressed the pedal too hard as we were bleeding the brakes, but then the question is why would it show up only at 75mph and without me braking?
I've also read that a MAF issue can cause this condition.
I have the issue intermittently, but I've been too lazy to troubleshoot it. Now that the car is back together (I finally got the GT3 console delete finished), I'll move on to this issue.
Interestingly, I see this most often when I'm at idle for a while - for example, waiting for my wife at the Nissan dealership a while back. This was the same pattern I saw when my MAF was going bad last time around...
yes I read MAF several time and I thought this was it as it's supposed to come under hard acceleration first, but then I tried accelerating slowly to 75mph and still get the issue.
Would be completely random that MAF issue is coming now when I have tinkered with all those other things that could be related, but I guess I should keep that in mind.
ok, just had an idea and went for a test drive. at 40mph, if I push the manual spoiler button (down by my foot), I get the same error.
so definitely something to do with the spoiler, I think that means it's not the MAF nor an alignment issue.
I don't get the spoiler warning light which I would expect... wonder what to do next now
How old is your battery? I vaguely also remember something about a failing battery being at fault for someone's PSM/ABS fault, and since deploying the spoiler draws a decent amount...
was thinking the same... especially since another mod I have is a BigCrank ETX14L that's about a year old.
It got pretty low while the car was parked, maybe that's the issue.
Will try swapping the battery tonight see if that helps
I'm thinking all of the above....
The one that sticks in my head though is the one you didn't mention in the poll. You removed a brake line than bled. Did you purge the entire system or just that corner?
I would suggest you bleed all corners. RR, LR, RF and LF in that order. If you don't have a Motive Power Bleeder you should get one. Its a one person diy.
Also you have a Durametric right? I would activate the brake booster and bleed it at the RF.
Just some thoughts...
If MAF, then you'd get P0115 and P5525.
I'd say either brake light switch or -most likely- led brake lights. Did you install aux resistors with led bulbs? If not, please do so. I have not got any warnings with leds and resistors. When installing I made a test without resistors...and installed them right away...
thanks all for your input.
alpine -> it's a full LED assembly, with no resistors integrated.
every where I read that on a 996.2 they would need a resistor so that may be it - weird thing is I can brake or put the lights on and get no message
did another test this morning:
- engine on, car parked, lights off, manual wing switch --> no warning
- engine on, car parked, lights on, manual wing switch --> warning
I am thinking 2 options now:
a) battery is dying, HIDs + wing is too much current draw and this is why I am getting a message
b) LED tail lights are the culprit, and somehow it shows up only when the wing goes up (why??)
FWIW, my car was down for about two weeks and was not on the battery charger. My first day driving it was Monday, the battery was definitely low, and the dash popped up the PSM/ABS combo three times.
After a night on the battery tender, I drove the same route yesterday - same stops, same traffic, zero dash lights.
I have aftermarket LED tails. Each side has integrated resistor packs.
Just a pure guess but the taillight wiring is on the same sub assembly as the spoiler so they may share common ground circuits and such which might trigger the lights. Do you have the stock ones that you can swap back in to do a quick test?
gonna try that tonight - pretty sure that's the LED lights now.
I did another test during lunch to see if that's a current draw issue:
- lights off, ventilation fan on, radio on - no warning
- lights on (parking lights only, no HID), ventilation off, radio off - warning
so I do not think the draw is the issue - must be the LED tail lights
alpine wins.
if I put back just 1 normal bulb on the parking lights, then no issue
Resistors ordered.
before I install them I will have to figure out if I need to put them on the brake light circuit or on the parking light circuit.
Facts seems to indicate parking light circuit but that's bad - that would mean the resistors will be super hot after a while with the lights on.
For those who had to put resistors with your LED tail lights - did you put the resistor on the brake light circuit or the parking light circuit?
Nice. Congrats on getting it tracked down.
The lights I purchased have an individual resistor for each bulb.
One of the techniques I have seen for increasing resistance includes adding a bulb to the circuit rather than a resistor - so instead of just generating heat, the light shines away, tucked away behind the light assembly.
ok, so to follow up on that: problem is now solved.
I put 1 3 Ohm resistor on one side between the brake wire and the ground.
Just one side, all seems good now
This is a source reference. Confirm exact model applicability in the original material.
