Knock_Retard_tables

	LT1 Edit Dump of Table --  KNOCK RETARD MAX LIMIT vs MAP
	STOCK
		20	25	30	35	40	45	50	55	60	65	70	75	80	85	90	95	100
	sprk Retard	0	0	0	0	3	3	6	9	12	12	12	12	12	13	13	15	15
	LT1 Edit Dump of Table --  KNOCK RETARD MAX LIMIT vs RPM
	STOCK
		0	400	800	1200	1600	2000	2400	2800	3200	3600	4000	4400	4800	5200	5600	6000	6400
	sprk Retard	9	9	9	9	9	9	9	9	9	9	10	10	11	12	12	12	12
	It seems the "pro - tuners"  tend to zero out the MAP table and manipulate the RPM table. Mine CAME that way
	I have worked the RPM table to something of my "choosing" (not shown)
	LT1 Edit Dump of Table --  KNOCK RETARD MAX LIMIT vs MAP
		20	25	30	35	40	45	50	55	60	65	70	75	80	85	90	95	100
	sprk Retard	0	0	0	0	0	3	6	9	11	11	11	11	11	11	11	11	11
	LT1 Edit Dump of Table --  KNOCK RETARD MAX LIMIT vs RPM
		0	400	800	1200	1600	2000	2400	2800	3200	3600	4000	4400	4800	5200	5600	6000	6400
	sprk Retard	9	9	9	9	9	9	9	9	0	0	0	0	0	0	0	0	0
	The above example might just be the "smartest way" I've seen to set these tables