pcmhacking.net

My understanding is it is still tuned by the VE table except it uses default map parameters to assume the map value based on the TPS and RPM and those parameters.

That looks a lot better!

I finished rewiring the reluctor using shielded wire, shoeld grounded to the chassis. Ran a few test cranks with the plugs out, it didn't look too bad, only a could of spikes when the coil was connected. (I forgot to put the protective cover over the reluctor in the distributor).
Used toming light to check that I had the polarity correct.
Wiped the NVRAM and loaded a known good BIN onto it.
Brake cleaner and paper towel on the spark plugs.

Started first kick and then died.
Then it started just like it always had.

No RPM spikes noticed in a few minutes of running.

I did previously do a test start with a reprogrammed Memcal with the good cal on it, with no luck.

Corrupted NVRAM may have been the problem, so may the reluctor.
It did not behave as previous corrupted NVRAM jas in the past as it was gradual and the fan didn't turn on with ignition on.
Thanks for all of the assistance. That kind of support os why I chose the Delco system in the first place and stuck with the PCM hacking hardware.
Awesome support guys, I'm learning a lot!

Cheers.

Good to hear! That talk of the nvram gives me another thought - how old is the nvram? Could its battery be nearing end of life? I know you tested a memcal and still saw problems, but it might be a second factor.

There was a couple of weird map sensor settings but I don't think it would stop it starting. But it only takes a missing decimal point in a setting for there to be issues. Good to hear its running again

Thanks for looking into it.

What were the weird MAP settings?

Think default map for engine not running was one of them would have to go back through it

I'm trying to tune it in using BLMs but am having some issues.
1. The BLMs appear not to do anything above 3200RPM.
2. BLM seems happy to pull out fuel but not add it when required.

Is there something in my scalers or tables that would prevent this function from working correctly?

I'm not the best when it comes to block learn but my method of tuning is to turn it off and adjust the VE to get the wideband data where I want it the the spark table of knock sensor (and common sense) data. I think if you are looking at block learn remember it's adapting to out of spec and if you disconnect the battery you'll have to start all over again. Just my thoughts.

Has your map sensor error problem been fixed yet cause with the code active it won't be using the map sensor

How do I fix the map sensor error.
I am not sure what I should see when I look at the parameters.

On a different note. My WBO2 now has an error. It's registering 14.7 at all times. I'm guessing it's new sensor time. (Maybe 3000 k's old).

I have been able to get much better results tuning by narrowband O2volts than i ever got with the WB histogram spreadsheet. It drives quite nicely now.

I did notice that BLMs were trying to pull fuel out even when the O2 sensor was below 500mV.
I don't think that should happen.