19 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSelf healing AOS?
Reported or suspected cause
aos/regulator, period
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
A high reading of the crankcase vacuum is caused by a failing AOS/regulator, period.
Leading evidence: 'aos/regulator, period' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'aos/regulator, period' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace battery and retest' (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 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
As far as AOS failure causing intermittent readings, the #1 cause is a leak in the regulator diaphragm, and depending on the size of the leak will determine the effect on the Diaphragm Regulator Control.
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 · Original poster
Someone suggested I change the battery and retest.
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 · Original poster
Maybe I need to test the old fashioned way with a slack tube.
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.
Reported cause
As far as AOS failure causing intermittent readings, the #1 cause is a leak in the regulator diaphragm, and depending on the size of the leak will determine the effect on the Diaphragm Regulator Control.
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.
19 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: 20261026T113718Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
So I have an electronic manometer and have been monitoring my AOS every few months.
The first few times I tested it was well under 5”H2O.
Then the next time it read a little under 7”.
Someone suggested I change the battery and retest.
Last time, after a new battery was installed, was back in November of last year and it reached nearly 9”.
I’ve been putting replacement off, and then decided I’d wait for
@Porschetech3
’s UAOS.
When I tested it on Friday after a 35 mile commute, it read 4.94”.
I’m going to retest after my commute tomorrow.
What could cause an AOS to fail, and then un-fail?
Maybe I need to test the old fashioned way with a slack tube.
Cars don't heal themselves. If you AOS showed signs of failing, it will not magically fix itself. I fit happened ones, it will happen again. Your car is trying to tell you something, make sure you listen.
I agree that an intermittent issue would be more likely than self healing. Hopefully
@Porschetech3
could chime in, or you could bring it up in his AOS Solution thread.
A high reading of the crankcase vacuum is caused by a failing AOS/regulator, period.
An air leak of the crankcase( oil cap or fill tube bellows ect) will cause a "low" reading of crankcase vacuum, and also a lean air/fuel condition due to fresh air/oxygen ingestion.
A vaccum/air leak on the intake manifold/lines will not effect crankcase vacuum (manometer reading), but will effect intake vacuum reading and cause lean air/fuel condition..
As far as the manometer being inaccurate, that is highly unlikely unless it's some dirt cheap China junk.
As far as AOS failure causing intermittent readings, the #1 cause is a leak in the regulator diaphragm, and depending on the size of the leak will determine the effect on the Diaphragm Regulator Control. The Atmosphere port is very small on the factory design AOS and it only takes a very small leak in the diaphragm to effect the pressure on that side of the diaphragm. The diaphragm is rubber so the leak can and will vary in size, causing the pressure control to be unstable. A complete failure (big rip) in the rubber diaphragm will cause full manifold vacuum (400 inh2o) 29 inhg to be applied to the crankcase as is #1 cause of engine hydrolock.
Bruce , I am building you UAOS as we speak, and will be shipping it out tomorrow, with a "new reworked AOS", since your is failing it is high priority.
Since these are Custom built, production is a little slow, but mostly due to backorder from Porsche Factory parts ( Auto Atlanta) like the hose I use and rework it to fit.
Just waiting on the backordered hoses from Auto Atlanta, and rest of my Accumlator order to be printed by Schmit Proto to complete the other orders, then I will be ready to order another batch.
