OK I found a hack for my E6, looking through it I realized there is a LOT of stuff I can play with. Just to see if I could, I tried to add a table for near idle spark advance vs rpm vs map. This is what I got from my hack

;---------------------------------------------
; NEAR IDLE SPK ADV Vs. RPM Vs. Load
; BDKJ, TYPE E6 ECM
;
; 1 MPH L.T. 40
; 2 TPS E.Q. or G.T 1.6% & L.T. or E.Q 2.3% TPS
; 3 COOL G.T. 35 DEG c
; 4 RUN TIME G.T. 30 SEC'S
; SEE L4154
;
;; 03-23-2000 Dissassemby of BDKJ
; 17 COL x 17 BLOCKS = 289 BYTES
;
; TBL = 2.844 * (SPK ADV + 10 Bias)
;---------------------------------------------
ORG $4284 ;
;
L4284 FCB 0 ; MIN MAP Val
L4285 FCB 0 ; Min RPM Val
L4286 FCB 17 ; LINES/BLOCK
;---------------------------------------------
; 400 RPM
; SPK ADV MAP
;---------------------------------------------
L4287 FCB 85 ; 19.9 20
L4288 FCB 85 ; 19.9 25
L4289 FCB 85 ; 19.9 30
L428A FCB 85 ; 19.9 35
L428B FCB 85 ; 19.9 40
L428C FCB 80 ; 18.1 45
L428D FCB 77 ; 17.1 50
L428E FCB 63 ; 12.2 55
L428F FCB 60 ; 11.1 60
L4290 FCB 54 ; 9.0 65
L4291 FCB 46 ; 6.2 70
L4292 FCB 40 ; 4.1 75
L4293 FCB 37 ; 3.0 80
L4294 FCB 34 ; 2.0 85
L4295 FCB 31 ; 0.9 90
L4296 FCB 28 ; -0.2 95
L4297 FCB 26 ; -0.9 100

So what I put into tuner pro under the conversion is ".35161*((x-y)-10)" by working backwards like Mark says in his tutorial. x being the entrys at that hex address, and y being the main spark bias (located at 0x4137). I end up with the same pattern as the chart exampled in the hack, but not the same numbers. my main spark bias is .84 degrees higher than his, but the calculations in my chart are about 3-4 degrees lower. My guess is that the extra load my truck initially has (more weight) means less timing to keep knock away. Am I right? How do I verify my results?

 

It is probably safe to say you can do more customizing in TP than I but... I think to verify your results all you need to do is burn a chip and do a datalog? It should show up right away since you are working with low rpm stuff.

 

The best way to verify your results is to test your .xfd with against .bin the hack was done from. For example, the $E6 hack is from the BDKJ.bin so load that .bin into TunerPro and see if you get the same results as the hack when you add items to the .xdf file. If you don't get the same results then you know something is wrong and you need to correct it. HTH

 

Good idea haulin, thanks again!

 

brain fart. I totally missed what the question was.

Good luck