2001 Camaro on the dyno, can't get spark to do what I need. while logging RUN_DMA is at 34* , SPARKADV is at 18.5* only way I seem to be able to add timing is by putting a value in the eq ratio table.
2001 Camaro on the dyno, can't get spark to do what I need. while logging RUN_DMA is at 34* , SPARKADV is at 18.5* only way I seem to be able to add timing is by putting a value in the eq ratio table.
Phil, welcome to the forum:
First off, you have way too many Pids/Channels being logged. That will cause a major lag in logging data. You need to keep the channel count to 24 or less for valid data.
Second, I am not sure what you are referring to when you are referencing the EQ Ratio table. What are you saying here?
Lastly, if you could post your Tune it will be a lot easier to deduce where your Spark values are coming from. Again, it could just be the 50 channels being logged that is causing the problem.
trying to figure out where my spark was going, don't usually log that many channels. tune might be a little hack in the spark and knock areas, try anything at this point.
eq ratio table for spark, 'Fuel Mixture Spark Correction' under 'Spark' and 'General'
Well, the channel count may be throwing off the data somewhat. If I look at frame 12..your Spark Advance is 19.0 degrees..you are getting 6.0 degrees of retard from your Trans Torque Reduction Spark. You are commanding 27.0 degrees in your High-Octane Spark table. 27.0 - 6.0 = 21. On Frame 11 2.2 degrees was being deducted from the ECT Spark Table.
So everything adds up..it is just a case of your Frame #'s are not lining up perfectly (50 channel count). Same issue with your Base DMA Spark. It is off by a couple of frames.
As an F.Y.I., there are some cases where putting Spark into the Fuel Mixture Spark Correction is warranted, but I would try reducing your channel count first. You don't seem to be encountering any mechanical KR..I think your Scan & frames are lagging..
Edit..Look at your Cylinder Air at Frame 12..it reads .98..so that correlates to 19 degrees of Spark on your High-octane Table. That data is correct, your Spark values are lagging..
Last edited by WeathermanShawn; November 23rd, 2010 at 08:27 AM. Reason: Additional Information..
Ill give that a shot, why would tranny be pulling spark when I have torque reduction off?
Your transmission torque reduction is still active in D0801 and D0802. If you were referring to D0301 being set to "Disabled" - that does not disable upshift / downshift torque reduction.
Regards,
Taz
that doesn't just apply to upshifts? or rather it will pull timing during a WOT run?
New run, less channels (i see what you mean by lagging) I zeroed torque reduction for upshifts. Still getting -6.0 deg pulled from tranny?
Phil:
I am not an expert when it comes to the Tranny Torque Reduction. Experts like TAZ have far more experience in knowing if and when it is disabled.
However, sometimes the Scan Tool is utilizing a Look-Up Spark Table Value and will display it as a reduction (unless it is zeroed). I assume this PID may also be utilizing a Traction Control feature?
Regardless, here is what may be happening. Even though Table B5913 says it is linked via DYNAIR, you are still MAF-Enabled. Therefore it is pulling your Spark via CYLAIR.DMA not DYNAIR.DMA. If you look at your first log when you logged CYLAIR you were hitting a max of .98 g/cyl. When you switched to DYNAIR you were hitting only a max of .80, but no doubt your Spark Value when properly matched to CYLAIR would have matched up to your WOT Spark Value of 19 degrees.
So, I really don't think it is pulling 6 degrees of Spark via Torque reduction. If you have the time and energy re-log using CYLAIR.DMA. That should match up perfectly to your High-Octane Spark Table.
Good luck..
trying that now.
p.s. Can I raise the airflow limits or change normalizers?