which PID is used by the pcm for the spark maps? dyncylair or cylair? this is for a 2003 silverado 4.3L
ls1b controller.
Printable View
which PID is used by the pcm for the spark maps? dyncylair or cylair? this is for a 2003 silverado 4.3L
ls1b controller.
An easy way to tell is, simply go to the calibration table you want to see. In your case maybe B5913 which is the high octane spark table.
Then look at the AXIS names for column ect.. In this case it tells you exactly what your question was.
DYNCYLAIR_DMA at the top, and SAE.RPM on the side.
+1 what wait4me said.
Also, for some calibrations, the spark table axis mentions more than one airmass (g) pid... you can log which ever of these pids that your PCM supports.
so which pid do i use for the scan log? the pid list shows dyncylair but not dyncylair_dma
Try GM.DYNCYLAIR and see if it logs (i.e. produces reasonable values).
it doesnt have gm.dyncylair. it has dyncylair, cylair, cylair_m
It's been a long time since I looked at the LS1, so hopefully I am remembering this correctly (feel free to correct me if I'm wrong).
For LS1, I would use CYLAIR_M or DYNCYLAIR_M depending on the requirements below. The "_M" (or "_DMA") suffix indicates PIDs that are not normally available from the ECM. EFILive has analyzed which memory locations are used to lookup the data in various table and the _M PIDs report the exact value used by the controller for table look-ups.
Requirements:
- CYLAIR_M is available when a MAF is fitted and fully functional - it is computed based on the MAF values.
- DYNCYLAIR_M is available when the MAF has reported a fault code - i.e. when a MAF is not fitted (or faulty) - it is computed using the MAP, RPM and IAT values.
Note: DYNCYLAIR (without the _M suffix) is a predicted value that the PCM computes from a number of sensor inputs (MAP, RPM, IAT etc). I can't remember (don't know) why it needs to predict the g/cyl ahead of time, I think it is 2 ignitions cycles ahead. It then uses (averages?) the around 5 predicted and past values to arrive at the value used for the lookup (i.e. DYNCYLAIR_M). So you may see very small discrepancies between DYNCYLAIR and DYNCYLAIR_M - I don't think the discrepancies would be significant, except maybe during a high rate of change of airflow, like transitioning from 0% throttle to 100% throttle instantly (or vice-versa).
Regards
Paul
In the V7.5, GM.DYNCYLAIR is the dyncylair you refer to... are you able to log this...?Quote:
Originally Posted by calif0rnia
If GM.DYNCYLAIR does not appear on the axis of the spark tables, there is a file that can be edited to add this pid name to the spark table axes (B5913, B5914).
i dont know, ill have to look. i use v8 for scanning and v7.5 for tuning
Are you able to log DYNCYLAIR using V8...?
yes. however this topic is no longer being pursued, my tuner is gonna use hptuner to do my truck
but thank you for your time and assistance
Either way, your tuner will still have to use the pid DYNCYLAIR to reference the spark tables.
DYNCYLAIR is a pid supported by this ECM.
gotcha thank you