2 months ago I replaced a leaking front tube assembly CAT on my 02
Pathfinder (which couldn't be patched w/ the Nissan kit). After
replacement and resetting the emission control unit, the P0430 code did not
return. However now 2 months later the P0430 code has now returned and in
shorter mileage intervals. It remained off after the initial CAT install
for 1200 miles, then after reset it remained off for another 500 miles, but
now it remains off for only about 100 miles. Other forums have suggested
that I need to have the ECU programming updated at a Nissan dealer to make
it more tolerant of O2 deviations from spec. Does anyone have any other
suggestions before I take the machine over to a dealer?

Thanks in advance.
RJ

"e.meyer" <epmeyer50@msn.com> wrote in
news:367c07c3-87ea-4cbf-9c55-77243e5c47ba@f77g2000hsf.googlegroups.com:

> On Oct 26, 4:00*pm, rj <newr...@optonline.net> wrote:
>> 2 months ago I replaced a leaking front tube assembly CAT on my 02
>> Pathfinder (which couldn't be patched w/ the Nissan kit). *After
>> replacement and resetting the emission control unit, the P0430 code
>> did n
> ot
>> return. *However now 2 months later the P0430 code has now returned
>> and
> in
>> shorter mileage intervals. *It remained off after the initial CAT
>> insta
> ll
>> for 1200 miles, then after reset it remained off for another 500
>> miles, b
> ut
>> now it remains off for only about 100 miles. * Other forums have
>> sugges
> ted
>> that I need to have the ECU programming updated at a Nissan dealer to
>> mak
> e
>> it more tolerant of O2 deviations from spec. *Does anyone have any
>> othe
> r
>> suggestions before I take the machine over to a dealer?
>>
>> Thanks in advance.
>> RJ
>
> My '02 periodically gets into a mood where it starts throwing codes
> like that. Before you spend any money on it, reseat all the
> connectors & blow out all the vacuum lines & see if that doesn't make
> it behave.
>
> After years of cursing it, I finally found debris in a vacuum line.
> Once purged, the light came on one more time, went off by itself after
> a couple of days and we haven't seen it again for 4 months and
> counting.
>

Thanks for the advice. Since I made my post it's gone 550 miles w/o
throwing the code so maybe some loose debris is what's setting it off.