Datalogging - 'Knock' vs 'SPKAD_IND' ?

[KrisR]

I've been looking at datalogs on my EBM. Logging with Lund nGauge.

I noticed that the 'Knock' value never triggers above zero on the datalogs (literally never), but the 'SPKAD_IND (1 through 4)' is typically 0 but during a WOT pull when the boost comes on it starts at 1-2 (presumably taking a couple degrees of timing out down low?) then as the revs climb the numbers go negative (I'm guessing adding timing back in as the torque curve drops). Is this true? Are these numbers what I should actually be looking at when trying to observe knock? Or unrelated? I'd like to keep an eye on knock counts that might be concerning.

I sent the logs to Lund and they say the logs look good, but obviously with the LSPI issues in these cars I want to keep and eye on it.

When I was datalogging my Coyote, the 'Knock' values looked / acted more like the SPKAD_IND values on this car. I assume it means Spark Adder, Individual cylinder.

If the 'Knock' count is truly what I would need to see to be converned, it's easier to monitor, I think I can set it up as one of the 'gauges' in the nGauge.

Thanks!

Sponsored

 

[Juben]

I don't recall the name of the ignition corrections PID on the nGauge, but I can tell you that Lund monitors and adjusts ignition timing and corrections globally and not on an individual cylinder basis (like would be from the factory). Look for the PID that's named something like Knock *something* or similar and monitor that. It'll be a global setting (which is what Lund uses) and will be everything you'd need to see. If memory serves me correctly, negative values means it's adding timing and positive means it's pulling timing because of the knock.

 

[KrisR]

Thanks, I'll look again but IIRC the only PID named anything resembling 'knock' was the one I described, simply called 'Knock', which has never been anything but zero, so I don't really believe it. The SPKAD_IND PIDs act just like the old 'knock' PID from my Coyote datalogging. Anyway, thanks.

 

[Tune+]

I believe that PID you are mentioning is Spark Add - Individual cylinder. So it is adding timing down low, then pulling it back out as you go through the RPM.

Every tuner uses spark add differently, I use it different based on every individual car.

 

[KrisR]

Here are the PIDS in the file he sent for logging...

TIME,RPM,ECT,SPARK,ETC_ACT,LOAD,VEH_SPD,TQ_SRC,AFR1,LAMBSE1,STFT11,LTFT11,KNOCK,PEDAL,FRP_ACTUAL,FRP_DESIRED,FUEL_SOURCE,WG_DC,TURBO_TIP,TQ_DD_LIMIT,MCT,MAP,KNK_OCT_ADD,KNK_OCT_MOD,KNK_PI_DETECT_CYL[,KNK_PI_DETECT_CYL[,KNK_PI_DETECT_CYL[,KNK_PI_DETECT_CYL[,KNK_HIGH,KNK_DET_INTEN,KNK_DET_FLG,SPKAD_IND[global],SPKAD_IND[1],SPKAD_IND[2],SPKAD_IND[3],SPKAD_IND[4],VOLTAGE(V)

All the 'KNK..(etc).....' PIDs and 'KNOCK' are always at zero. The only PIDS that seem to be altering timing are the 'SPKAD_IND...' PIDs. The 'SPKAD_IND(GLOBAL)' PID is also always Zero. So I don't see any global spark correction. But what do I know.

Spark generally starts out at between -4 and -3 degrees at low rpm then zeroes out, maybe has +1 to 2 degrees at the top end.

Greg did say in his last email that my car looks octane limited, and to either try and find another source of 93 or whatever. I'm thinking my upcoming IC and DP installations will help as well.

 

[KrisR]

Lund sent me an E30 file to try out. They want to be careful with it so I logged a couple 2500-5000 pulls with it and sent them the files for their perusal.

 

[Juben]

I wish I could remember which PID I used to monitor the corrections, but it's been a while ago. Sorry I'm of no help there, lol. You'll love E30!

 

[KrisR]

I wish I could remember which PID I used to monitor the corrections, but it's been a while ago. Sorry I'm of no help there, lol. You'll love E30!

No problem. Thank you!

It felt pretty sluggish during the pulls I did for logging, but Octane Correction or whatever was still at zero so timing was pretty soft. I'm sure it will like more timing/boost on E30.

Sponsored