using free software to tune out downstream o2 and evap?
I am getting the following codes with my 5.3 LM7 gen 3 swap in my G Body:
P0036 - HO2S heater control circuit bank 1 sensor 2
P0054 - HO2S heater resistance bank 1 sensor 2
P0056 - HO2S heater control circuit bank 2 sensor 2
P0060 - HO2S heater resistance bank 2 sensor 2
P0443 - EVAP system purge control valve A circuit
P0449 - EVAP system vent valve control circuit / open
P0452 - EVAP system pressure sensor / switch A circuit low
Is your harness a red / blue connector at the PCM or a blue / green connector? The key to using Tuner Pro RT is to make certain that you get the XDF file that exactly matches the operating system (OS). If you edit the OS with an oddball mismatched XDF, your checksums will be wrong resulting in a probably unusable PCM. Maybe even turned into a wheel chock bricked and doorstop device.
Rick
I checked the bin file with universal patcher and the DTC MIL for all the rear o2 sensor codes and evap codes were already turned off, which makes me wonder how is it possible my obdii would read these codes still? I’ll try erasing codes and scanning again.
Also is simply turning off the DTC MIL actually turning off the rear o2 and evap? Or do I need to go elsewhere in the software to turn it off?
Trending Topics
The Best V8 Stories One Small Block at Time
When you "brick" a PCM, does that render it completely ruined, or do you just need to buy a new credit and reprogram it? Because the actual hardware inside the case is still good, right?
This is one of the reasons why I've never tried my own tuning.
I don't think this works for anything newer than a P59 (around the second half of the 2007 model year) but I don't know for sure.
I am not an HP Tuners person so I can't answer that question. However, I think the "credit" is tied to the PCM hardware serial number so perhaps, you would not need a new credit. But again, IDK for sure.
Rick
There is also a way around that problem, but it requires a $75 bit of hardware and either half-dozen solder connections or a printed or CNC'd jig. This page has a few words a few links with more details: https://github.com/LegacyNsfw/PcmHacks/wiki/BDM
Far as I can tell, there are two things that make this interrupted flashes (with cause flash chip corruption) a bigger issue with PCM Hammer than with HP Tuners:
1) PCM Hammer doesn't check the voltage before it starts flashing. I've been meaning to add that feature but we have a couple of big changes in the pipeline and I don't want to rock the boat any more.
2) Bench flashing is a bit risky. And bench flashing the P01 PCMs (and some P59s) requires a pretty stout power supply, because those PCMs have flash chips that will pull about an amp when the erase a section of flash memory, and not many 12v power supplies can handle that. So the flash process starts, PCM Hammer asks the PCM to erase a section of flash memory, the flash chip pulls 10 watts or whatever, and the power supply can't keep up, voltage drops way down, and the PCM reboots... with an erased-but-not-rewritten section of flash memory. That'll be a problem with any flashing software, though.
Of course that raises the question of why bench flashing is more common with PCM Hammer than with HP Tuners or EFI Live. I have a hunch that the commercial tools are better at telling other modules in the vehicle to stay silent, but I don't know what they're doing. But I do know that if another module interrupts the flash process, that's another way to leave a PCM with corrupted flash memory.
Either way, you can usually recover with the pin-grounding trick. Most flash operations don't erase the boot block - that will only happen when changing a PCM from one OS to another.
Rick
I don't know what PCMs were used in '98 but see if you can find out that "P-number" for your PCM and then cross-reference with the ones listed in the first post.
I haven't been involved in adding support for the other PCMs, so that's everything I know.
I am working on a better UI though.














