7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996.2 40AE drive cycle reset
Leading reported evidence
Check code reader and viola
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.
Leading evidence: 'Check code reader and viola' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check code reader and viola' (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 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
The smog guy said "drive it, do different stuff, keep checking the monitor status, bring it back when they are "ready" but before the CEL comes on again.
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
Keep checking the monitors (like every time you turn on the engine), and get it to the test asap after they are ready (there is one that can be "not ready , in Calif, can't remember which) not sure about Tx.
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
Add it to your tank when it�s maybe 1/4 empty, then drive normally for at least 15mins and then refuel and check your readiness monitors.
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 smog guy said "drive it, do different stuff, keep checking the monitor status, bring it back when they are "ready" but before the CEL comes on again.
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
Keep checking the monitors (like every time you turn on the engine), and get it to the test asap after they are ready (there is one that can be "not ready , in Calif, can't remember which) not sure about Tx.
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
Keep checking the monitors (like every time you turn on the engine), and get it to the test asap after they are ready (there is one that can be "not ready , in Calif, can't remember which) not sure about Tx.
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.
7 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: 20261027T154520Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
First of all, many thanks in advance for the guidance on this topic and many prior to this from my lurker days.
First post, long time lurker. Currently have a 99 996 c4 and recently got a 996 40AE #1277.
Context: my 40AE has fabspeed 200 cell cats, Supercup exhausts and competition intake. The car was in trickle charge for a while until the dealer I bought from did all the needed maintenance including o2 sensors. Now I need to get it registered in Texas and it�s not passing inspection given it needs to complete the drive cycle.
currently no CEL is on.
I have tried, despite being a PITA, the instructions below, but no dice
Gas at 3/4 to 1/4 full, no more no less -
Start (cold start required) and idle 2.5 minutes.
Begin driving, accelerate to 20-30 mph and maintain speed for 3.5 minutes.
Then increase speed to 40-55 mph, again maintaining steady speed for 15 minutes.
Then decelerate and come to a complete stop and idle in neutral for 3 minutes.
My guess is I need to do the 40 to 55 mph for 15 mins again. Based on the live data I gathered from my blue driver obdII reader, there seems to be drops is speed. I thought it was cumulative but I guess not.
because I still keep getting this message from the Blue Driver this morning.
Do you all recommend I try again? Or are there anything else I need to try like a softronics tune? Idk how that will help as I don�t have a cel.
really appreciate the guidance folks!!
current stable pics for fun
I�d suggest trying it again, maybe late at night when you can get on a long stretch of road and just cruise at 50-55mph.
If that doesn�t work, and because it�s a cat readiness thing, there�s a product called cataclean that you can try. Add it to your tank when it�s maybe 1/4 empty, then drive normally for at least 15mins and then refuel and check your readiness monitors. After
going through 3 drive cycles throughout 3 separate days at 2am, this was the only thing that got the cat monitors on my e46 ready.
Your best shot is to keep trying. The recommendation to drive late at night is ideal; there�s much less traffic to impede (and be impeded by).
I�ve never used Cataclean, and I�m a bit wary of adding stuff like that. The most glaring issue I see is that you�re running 200-cell cats; even in brand new condition, they�re probably borderline - in terms of emissions - which causes the DME to be hesitant about passing the readiness test.
I�d like to see you try multiple attempts at completing the drive cycle before you add the Cataclean. It�s very easy to add it in, but it�s damn near difficult to remove. Try to exhaust all non-invasive methods first.
Solid advice! Tried again and probably annoyed at least 9 drivers going 55 on a 75 with hazards on parts of the way. Coasted off to zero into a safe area, held the clutch for 3 mins and idled. Checked the code reader and viola! All green.
Thanks for the advice folks. Now time to get registration, plates and enjoy the car!
P.S. the 26 mile drive back was the first time I opened her up a bit. The x51 combined with the fabspeed bolt ons �.. phew! She moves. The supercups are for sure gonna get the axe in favor of the fisters.
I don't believe the "drive cycle" requirements.
I have seen the same info posted for different manufacturers.
My Mom has an 2001 XC-70 Volvo, it failed the Ca smog test for the "monitor not ready" issue (I had cleared an intermittent downstream O2 sensor fault recently).
The smog guy said "drive it, do different stuff, keep checking the monitor status, bring it back when they are "ready" but before the CEL comes on again.
I did that, and the monitors were all ready after about 50 miles, it passed smog, and the CEL (and O2 DTC) hasn't come back.
(an unscrupulous shop would have recommended changing the cat)
My advice, DRIVE IT! Do different stuff. Keep checking the monitors (like every time you turn on the engine), and get it to the test asap after they are ready (there is one that can be "not ready , in Calif, can't remember which) not sure about Tx.
Good luck,
Paul
That would typically be the �EVAP� monitor.
Unless, if your car�s model year is between 96-99, then you can have any single monitor remain incomplete and still pass the OBD portion of the test.
https://www.bar.ca.gov/obd-test-reference#readiness
As far as your comment about the drive cycle requirements, you�re generally correct. However, following the prescribed methods vastly improve your chances of completing the readiness tests in a short amount of time.
I�ve also driven a few vehicles that would never set the monitors unless you follow the instructions exactly.