KAZ MotorSports
June 5th, 2008, 04:03 AM
OK guys,
My nightmare continues with this 1998 Tahoe that I upgraded the PCM to a 411. Way smoother idle, better throttle response, better HP and torque numbers. I am running COS3 on the Express van OS. It has a 2bar MAP in it, Whipple at 5.5-6.0 psi_g of boost at 6000' elevation, 8.8:1 w/forged internals. She is ready to run with plenty of fuel from the Walbro 255 HP pump and FPR.
The problem I am having is DYNCYLAIR is the axis the spark table is looking at to map the spark curve. I do not see anything recorded higher than 0.80 at 108kPa and it looks like from the log it is actually reading the 0.40 area of the map. Commanded spark at 0.80 = 21.5*....actual in the log is showing 30* at the same RPM and that is what is commanded in the 0.40 cell at RPM. All of the spark corrections, multipliers, etc have been zero'd or set to 1.0 to try and track why it is doing this and pin-point which cell it is truely getting the commanded spark value from.
Any insight? I did read Howard's post which was similar to this back in 2006, but there was no real resolution explained or posted from what I read.
Thanks all!
-Kenny
ps...attached is the tune and log file.
My nightmare continues with this 1998 Tahoe that I upgraded the PCM to a 411. Way smoother idle, better throttle response, better HP and torque numbers. I am running COS3 on the Express van OS. It has a 2bar MAP in it, Whipple at 5.5-6.0 psi_g of boost at 6000' elevation, 8.8:1 w/forged internals. She is ready to run with plenty of fuel from the Walbro 255 HP pump and FPR.
The problem I am having is DYNCYLAIR is the axis the spark table is looking at to map the spark curve. I do not see anything recorded higher than 0.80 at 108kPa and it looks like from the log it is actually reading the 0.40 area of the map. Commanded spark at 0.80 = 21.5*....actual in the log is showing 30* at the same RPM and that is what is commanded in the 0.40 cell at RPM. All of the spark corrections, multipliers, etc have been zero'd or set to 1.0 to try and track why it is doing this and pin-point which cell it is truely getting the commanded spark value from.
Any insight? I did read Howard's post which was similar to this back in 2006, but there was no real resolution explained or posted from what I read.
Thanks all!
-Kenny
ps...attached is the tune and log file.