[MAZOC] Official "Off-Topic" Discussion Thread

[sixpax]

Originally Posted by b1adesofcha0s

Yeah I put steel wool in on Friday, but didn't work. I already ordered the scanner and should have it by the end of this week or early next week. The code it was throwing is PA200.

If you mean P2A00 then try the relearn process:

Here are the instructions:

1. Start engine and warm it up to normal operating temperature.
2. Turn ignition switch OFF.
3. Disconnect mass air flow sensor harness connectors, and restart and run engine for at least 5 seconds at idle speed.
4. Stop engine and reconnect mass air flow sensor harness connector.
5. Make sure DTC P0102 is displayed.
6. Erase the DTC memory.
7. Make sure DTC P0000 is displayed.
8. Run engine for at least 10 minutes at idle speed.

[Z Stig]

Originally Posted by sixpax

If you mean P2A00 then try the relearn process:

Here are the instructions:

1. Start engine and warm it up to normal operating temperature.
2. Turn ignition switch OFF.
3. Disconnect mass air flow sensor harness connectors, and restart and run engine for at least 5 seconds at idle speed.
4. Stop engine and reconnect mass air flow sensor harness connector.
5. Make sure DTC P0102 is displayed.
6. Erase the DTC memory.
7. Make sure DTC P0000 is displayed.
8. Run engine for at least 10 minutes at idle speed.

Good info! Rep for you!

[GM_Traitor3.5]

Originally Posted by sixpax

If you mean P2A00 then try the relearn process:

Here are the instructions:

1. Start engine and warm it up to normal operating temperature.
2. Turn ignition switch OFF.
3. Disconnect mass air flow sensor harness connectors, and restart and run engine for at least 5 seconds at idle speed.
4. Stop engine and reconnect mass air flow sensor harness connector.
5. Make sure DTC P0102 is displayed.
6. Erase the DTC memory.
7. Make sure DTC P0000 is displayed.
8. Run engine for at least 10 minutes at idle speed.

That might work literally right before he goes in for the OBD-II emissions test. Be weary though that this probably won't work in the next few years when MD and VA emissions testing equipment gets an upgrade and they can see when your ECU was re-flashed, how long your last CEL was on for before it was cleared, when the CEL was last cleared, etc.

[m4a1mustang]

Originally Posted by GM_Traitor3.5

That might work literally right before he goes in for the OBD-II emissions test. Be weary though that this probably won't work in the next few years when MD and VA emissions testing equipment gets an upgrade and they can see when your ECU was re-flashed, how long your last CEL was on for before it was cleared, when the CEL was last cleared, etc.

[GM_Traitor3.5]

Originally Posted by m4a1mustang

Yeah, my Dad just told me about the software upgrades to the testing equipment on Sunday (he works for the DEQ emissions control program). They also might start making the inspectors pay closer attention to stuff on the visual inspections and enforce them more often

[m4a1mustang]

Originally Posted by GM_Traitor3.5

Yeah, my Dad just told me about the software upgrades to the testing equipment on Sunday (he works for the DEQ emissions control program). They also might start making the inspectors pay closer attention to stuff on the visual inspections and enforce them more often

That's really annoying.

[Sales@AAMComp]

Originally Posted by GM_Traitor3.5

That might work literally right before he goes in for the OBD-II emissions test. Be weary though that this probably won't work in the next few years when MD and VA emissions testing equipment gets an upgrade and they can see when your ECU was re-flashed, how long your last CEL was on for before it was cleared, when the CEL was last cleared, etc.

I thought they already can do this?

[GM_Traitor3.5]

Originally Posted by Khoi@AAMComp

I thought they already can do this?

Some of the newer analyzers can, but most are running the first gen OBD-II stuff that pull the normal parameters of the ECU to ensure all system checks are there. Some can detect if downstream O2 sensors have been removed from the code for things like headers and what-not so your dash never throws a CEL. Newer software is smart enough to know if the factory flash has been tampered with.

They be getting smarter...