Threw a couple DTC's after going to APR v5.0 (m)
#1
AudiWorld Super User
Thread Starter
Join Date: Apr 2000
Posts: 3,849
Likes: 0
Received 0 Likes
on
0 Posts
Threw a couple DTC's after going to APR v5.0 (m)
Has anyone else thrown the Cat inefficency codes 16805 & 16815 with aftermarket DP's & APR's new code?
I've got the AWE DP's (w/o test pipes). Been running APR's stage 2+ software two years without any problems but went with the Stage 1/2 when they updated to v5.0 figuring the Stage 2+ was for the early release APR DP's only.
Right now I'm thinking maybe I still need Stage 2+, though I thought the prevailing opinion on this was that I wouldn't.
Anybody else running into this situation?
I've got the AWE DP's (w/o test pipes). Been running APR's stage 2+ software two years without any problems but went with the Stage 1/2 when they updated to v5.0 figuring the Stage 2+ was for the early release APR DP's only.
Right now I'm thinking maybe I still need Stage 2+, though I thought the prevailing opinion on this was that I wouldn't.
Anybody else running into this situation?
#3
AudiWorld Super User
Thread Starter
Join Date: Apr 2000
Posts: 3,849
Likes: 0
Received 0 Likes
on
0 Posts
Perhaps, but I think it is unlikely since (m)
I was running the stock chip for almost two weeks before updating to v5.0
I wrote a note to APR and will be anxious to see what they say. I might have to put the stock chip back in to confirm it is a software issue, good suggestion.
I wrote a note to APR and will be anxious to see what they say. I might have to put the stock chip back in to confirm it is a software issue, good suggestion.
#4
Using the stock ECU is a good idea.
Do you have a home programmer by any chance? If so, then you could try v3.3 Stage II software and see if those same faults shows up. Reason I say try that is because you'll be running high boost for comparison sake. Chipped programming will definitely make any problems come to light quicker than the stock programming anyway.
#6
Had the same problem with v3.3. When I was running cats (m)
and using Stage 2 programming, it would trigger a CEL every 3-4 days or so. Once I switched over to Stage 2+ programming, no CEL and no codes would show up. Must have been reading too much flow even with the cats in place. Only other possibility could be an exhaust leak maybe or fried 02 sensors.
#7
AudiWorld Expert
IF YOU HAVE NO CATS, YOU'RE GONNA GET THE CODES
Sorry for the CAPS, just felt in the mood.
APR's original downpipe design did not relocate the O2 sensors such that they were around the remaining cat, therefore when running APR's downpipes with cats, there was no cat inbetween the primary and secondary O2 sensors, and APR's stg2+ code addressed this by not giving the cat efficiency DTC.
Other downpipe manufacturers that relocted the O2 sensors around the cat did not need any special code SO LONG AS YOU RUN THE DOWNPIPES WITH THE CATS.
AS SOON AS YOU REMOVE ALL CATS (from anyone's downpipes), now every set-up becomes the same in that there is no cat between the primary and secondary O2 sensors. Therefore, unless the software is designed to not give that DTC (like APR's stg2+ is), you will get this code.
Make sense?
APR's original downpipe design did not relocate the O2 sensors such that they were around the remaining cat, therefore when running APR's downpipes with cats, there was no cat inbetween the primary and secondary O2 sensors, and APR's stg2+ code addressed this by not giving the cat efficiency DTC.
Other downpipe manufacturers that relocted the O2 sensors around the cat did not need any special code SO LONG AS YOU RUN THE DOWNPIPES WITH THE CATS.
AS SOON AS YOU REMOVE ALL CATS (from anyone's downpipes), now every set-up becomes the same in that there is no cat between the primary and secondary O2 sensors. Therefore, unless the software is designed to not give that DTC (like APR's stg2+ is), you will get this code.
Make sense?