what logging on HPtuners?
I just log using the default imperial config. It's got most everything you'd want. Depends on what you're trying to tune thought. When I was doing MAF calibration I added dynamic airflow and dropped something else like spark advance to stay under 25 bytes. At 25+ bytes the sample rate gets cut in half. If you were trying to get a cammed out car to idle right you'd ad LTIT and STIT and running airflow (RAF). On a WOT log you'd want to make sure you're logging KR.
It really depends on what you're looking for, where you
should look. For instance I have configs which are all
about transmission and I have ones that are for tuning
performance. Depending on what you're chasing you may
prefer to limit yourself to 12 PIDs (for 20/sec capture rate)
or you may be wanting to just drag a big net and get 48
at 5/sec, rather than the default 24, /10.
In general you want to log things that are either directly
of interest (O2s, fuel trims, RPM, MAP, dynamic airflow,
TPS, MPH, spark advance, knock retard, etc.) or are used
as indices for important tables and modifiers (ECT, IAT,
dynamic cylinder air, delivered torque - trans) so you can
tell why you got, what you got.
Work backwards from the goal to the data needed and the
tables involved, and then cover the bases.
should look. For instance I have configs which are all
about transmission and I have ones that are for tuning
performance. Depending on what you're chasing you may
prefer to limit yourself to 12 PIDs (for 20/sec capture rate)
or you may be wanting to just drag a big net and get 48
at 5/sec, rather than the default 24, /10.
In general you want to log things that are either directly
of interest (O2s, fuel trims, RPM, MAP, dynamic airflow,
TPS, MPH, spark advance, knock retard, etc.) or are used
as indices for important tables and modifiers (ECT, IAT,
dynamic cylinder air, delivered torque - trans) so you can
tell why you got, what you got.
Work backwards from the goal to the data needed and the
tables involved, and then cover the bases.
