3400 w/ Milzy Stage 2 (was Stage 1) tuning

[moonwell]

So tonight was yet another frusterating & unproductive night.

First off, swapped on my spare set of coil packs. The datalog was showing a lot less knock, occuring not nearly as often. The car still felt the same, though. Cutting out, Popping on decel, etc.

So I did some leaning out of the base VE table, since BLM's were still showing rich. Datalogged & all the knock was back! So I reverted the VE table back & then richened it up some to see what affect that had. BLM's changed a tad, but otherwise everything was pretty much the same.

So I reverted back to the programming from right after I changed the coils, and all the knock was back. So I dunno why it showed less knock in that first log

Well, I was still getting those weird jumps to 23000+ spark advance in my logs. I datalogged the '92 to verify it wasn't just a Freescan glitch, and no such advances were being shown. BLM's on the '92 are in the 110-115 range, and it runs pretty decent for 166k.

So I swapped in the entire ECM from the '92, using my custom prom in the 92's memcal via my adapter. Datalog still showed the weird spark advances and spark knock. That rules out the computer & knock sensor circuitry in the Memcal.

So tomorrow night I'm gona try the CPS. Then swap the entire ignition module & coils from the '92. Then procede to push the '94 into the river

[SappySE107]

Do the O2 sensor. That last long shows the O2 not moving very fast and it took forever to hit closed loop.

[moonwell]

Who wants to buy a Red 3400 swapped cammed Z that runs like shit?

New O2 & CPS. No change. Swapped ignition module & coils from the '92. No change

[onefastV6]

You wanna sell the cam :P Don't give up just yet, I am fighting the same battle with KR, it is stressful and discouraging but you will get there eventually.

[burn]

did you ever set the limit of vacuum for the ECM to know to set cell 2 ?

Because under mild acceleration you are sitting in cell 1, but it should be shifting to cell 2. I think the figures are skewed by the lack of vacuum you are experiencing.

[SappySE107]

2 is decel so it shouldn't be hitting cell 2 on acceleration.

[onefastV6]

Have you made any progress lately?

[moonwell]

No new progress. I've taken the week off from messing with it.

Had a meet over the weekend that I managed to drive it to, racking up a couple hundred interstate miles. It would cruise w/o cutting out on the interstate as long as the throttle was kept completely steady. Bump it or let off the slightest bit & it would miss. Previous interstate logs show that it would still randomly start reporting spark retard, even if it couldn't be felt.

I might start messing with it again next week, but I'm really at a loss as to what is going on

[burn]

2 is decel so it shouldn't be hitting cell 2 on acceleration.

depends what program you are logging with. I know in freescan is shows:

idle: cell 0
accel: cell 1
cruise: cell 2

[SappySE107]

It shouldn't. Cruise and accel are the same. Otherwise you don't have a decel cell and there certainly is one. If its not hitting decel, your MAP range is off in the tuning. Possibly more stuff...ive had issues with setups that idle in the 70s leaving no real resolution. Decel would hit high 40s max, mostly 50s.

[burn]

Are you talking about the 8F or the A1?

I know with the 8F the accel & cruise are the same cell, and decel is a different cell, whereas the A1 the accel & decel are the same cell and the cruise is a different cell.

[SappySE107]

Last time im going to say this. 0 is idle, 1 is cruise, accel, wot, 2 is decel. A1, DF, 6D, 88, and probably 8F since GM reuses most of the code between these masks.

[moonwell]

So apparently I was sent a stage 2 cam, not the stage 1 that I ordered

So this is now Stage 2 tuning, rather than Stage 1 tuning. That would explain the excessevly low vacuum.

Milzy claims that I should still be alright clearance wise, so that rules that out as being the problem, which is what I figured it must be when I discovered I'd installed a stage 2.

I hadn't touched the car for a month. Finally messed with it for a little bit this weekend until I relealized the cam issue. Set the max knock retard to 0 (still registering knock counts, but now it can't retard the timing). Seemed to run a little better. Got the BLM's pretty close to 128 at idle & cruise, but that didn't really affect how it was running. Been doing the tuning on the fly with the Ostrich.

[Joseph Upson]

Is the cam regrind being passed up because you can't acquire the specs desired or is it to avoid addressing the pushrod issue, And just how well is the Ostrich working for you and are you using it with a wide band O2 sensor data logging device. I'm planning to purchase the Ostrich soon if not the Romulator.

[burn]

Last time im going to say this. 0 is idle, 1 is cruise, accel, wot, 2 is decel. A1, DF, 6D, 88, and probably 8F since GM reuses most of the code between these masks.

Yes, but freescan displays the information differently that when you are cruising you are in cell 2, and when you are deceling you are in cell 0. but if you actually look at the freescan datalog is shows cell 1 as cruise & cell 2 as decel. I dont know why it does this, and I thought I waws going crazy the other night when I was talking to moonwell on MSN about this issue, so I went and tested it and it actually does display the information inaccuratly like this. Time to switch to TunerPro to do my datalogging. lol.