2018 silverado 5.3 afm deleted and disabled

[baychef]

2018 chevy silverado mechanically deleted afm and disabled in i3 , new cam , lifters and trays , it was running excellent in lieu of a custom lew tune after the break in period but its now throwing codes p0430 and p0

[mikel]

you remove the cats?

[baychef]

no it was an intake leak and the map sensor we changed map and installed new manifold gaskets, and a pcv wasnt fully locked in , its night and day , looking forward to data logging and lews custom tune

[baychef]

im still getting p0430 and p0420 and they pop up in a weird way they will simultaneously pop up with the tire pressure monitor sensor im not a tech but my dude is super sharp and hes baffled it runs strong with the canned tuned but i need to figure this out before logging for lew , ANY feedback would be great

[mikel]

put it back to stock and drive it for a while to confirm the tune is not the issue?

[baychef]

thanks for the reply, how do i remove tune while still maintaining afm disable, its fully deleted mechanically

[baychef]

what happens if the cat codes go away

[mikel]

thanks for the reply, how do i remove tune while still maintaining afm disable, its fully deleted mechanically

use the modify stock option and just select the AFM disable.

[baychef]

we figured it out we did an full scan on a snap on scanner and cats and o2 up and down stream and all were within specs with tune removed , so far after about 75 miles in stock theres been no trouble codez but we will run it for a few days first

[baychef]

thank you for the quick reply i appreciate it

[baychef]

well im incredibly frustrated over this!
ive put about 100 miles on truck in stock and no codes other than the tpsm which apparently isnt related to anything.so whats my next move ?

[mikel]

what is the specific tpsm code?

[baychef]

the tpsm code is resolved i had a tire pressure sensor go out i got a new one had it installed and its resolved . the cat codes p0420 and p0430 was perplexing they were pretty consistent in canned tune but after running 100 octane 11.999 $ a gal lol and running the diablo octane tune it ran great no codes i ran a full tank no codes and i data logged , the only way i could run with no codes other than a diablo tune was stock with afm enabled with 100 octane in manual so afm wasnt trying to adjust injectors , im going to email lew the log and see what yall say. my tech ran multiple scans with a professional snap on scanner the cats were all within spec as were the upstream and downstream o2 sensors , but i had new downstream o2 sensors and a map sensor so we replaced them all with no visible change in the scan #s .my tech isnt just some shady tree mechanic he was the main tech at nor cal mopar and ASE. master in chevy, mopar, and 10 other makers hes very sharp and hes at a loss

thank you mike for the response i do appreciate your time this is VERY. frustrating and time consuming
mike shimonek

[mikel]

If you load the tune that seems to cause the codes and get them to come back, Id love to look at the 'last tune written' from the device at that point.

[baychef]

lew has the data