| View previous topic :: View next topic |
| Author |
Message |
lyckaon
Joined: 28 Jan 2007
Posts: 13
|
 Posted: Mon Jan 07, 2008 3:37 pm Post subject: CA18DET max timing advance |
 |
|
Hi!
What's your max timing advance? And what do you think about my bin?
Here is my setup:
CA18DET
- TR28KAI (hypergear) turbo
- SSA 4-1 manifold
- Free flow exhaust
- RB25 MAF
- Saab intercooler
- 444cc injectors
- 255 lt/min fuel pump
My average TP (with "K" at 242) at 11 psi (~0.8 bar) is between 90 and 100 in boost.
Here is my bin:
http://www.fast-files.com/getfile.aspx?file=5482 |
|
| Back to top |
|
 |
Vetal
Joined: 08 Feb 2006
Posts: 120
|
| Posted: Thu Jan 17, 2008 9:40 am Post subject: |
|
|
| I have 22 at 4000-5200, 26 at 6000 and 30deg at 6800 |
|
| Back to top |
|
|
lyckaon
Joined: 28 Jan 2007
Posts: 13
|
| Posted: Thu Jan 17, 2008 10:14 am Post subject: |
|
|
| This is the real timing advance or the numbers in the table? |
|
| Back to top |
|
|
Vetal
Joined: 08 Feb 2006
Posts: 120
|
| Posted: Thu Jan 17, 2008 10:47 am Post subject: |
|
|
How do I know?  these are degrees in ignition table. Although, I didn't set up base timing, so they could be pretty much useless... |
|
| Back to top |
|
|
lyckaon
Joined: 28 Jan 2007
Posts: 13
|
| Posted: Thu Jan 17, 2008 12:54 pm Post subject: |
|
|
What's your engine management software? I use Nistune, and with the datalog I see that the real timing is about the number in the map minus 22.
That mean that if you have 22 in the map (with romeditor for exemple) your real timing is about at 0° BDTC |
|
| Back to top |
|
|
cb_drift
Joined: 04 May 2004
Posts: 468
Location: New Zealand
|
| Posted: Mon Jan 21, 2008 2:49 am Post subject: |
|
|
it appears that the timing adjustment is actually -16 degrees for the timing maps
*shrug*
just work with a knock monitor and whatever you get to in the end is the limit for your combination of parts....
i use -16 to get correct timing figures - someone on here verified it with a timing light as being -16 to get timing figures and i'll work with that rather than the options of -22 or /2 for the true timing figures....
Use a knock monitor - that is the ONLY way to be sure you are using safe timing values..... |
|
| Back to top |
|
|
darkhalf
Joined: 08 Dec 2003
Posts: 361
Location: Adelaide, Australia
|
| Posted: Mon Jan 21, 2008 10:35 am Post subject: |
|
|
When using NIStune there are three timing map offsets used
| Quote: | CONSULT_TIMING_OFFSET=16
IDLE_TIMING_MAP_OFFSET=16
TIMING_MAP_OFFSET=22
|
The one which cb_drift is talking about is the maps themselves. These are -16 as mentioned
Applies to:
- Timing maps (To view these with offsets applied use the 'filtered view' on the timing map)
- Idle timing map (To view this with offset applied use File-Configuration)
The Consult timing offset is a separate offset with -22 used for display of the timing values in NIStune is interpolated from the timing map routine as the ECU reads it.
We have found that the ECU uses the regualr (knock) map in one variable, but also the (high - regular) in another variable.
NIStune currently reports the regular value in its display, but it might be beneficial to also display (high-regular) + (regular) to get high as a separate variable in the software
Commented code below | Quote: |
B180 LB180: // timing calcs
B180 : B6 10 E8 " " ldaa X10E8 //RPM_MSB/2
B183 : CE B9 B0 " " ldx #IDLE_TIMING
B186 : BD 80 A9 " " jsr L80A9 // Interpolate routine
B189 : 7F 10 C2 " " clr X10C2 // clear DIFF_TIMING
B18C : F6 11 0C " " ldab X110C // check flag
B18F : C5 01 " " bitb #$01
B191 : 26 06 "& " bne LB199
B193 : B0 BE 13 " " suba XBE13
B196 : 24 01 "$ " bcc LB199
B198 : 4F "O" clra
B199 LB199:
B199 : F6 11 0C " " ldab X110C // clear flag
B19C : C4 FE " " andb #$FE
B19E : F7 11 0C " " stab X110C
B1A1 : 7E B2 1E "~ " jmp LB21E // store timing again and RTS
;
B1A4 LB1A4: // base timing calcs
B1A4 : F1 B9 10 " " cmpb XB910
B1A7 : 25 14 "% " bcs LB1BD // main interp routine
B1A9 : 7B 04 53 "{ S" tim #$04DIGITAL_CONTROL_1
B1AC : 27 0F "' " beq LB1BD
B1AE : F6 10 07 " " ldab VEHCILE_SPEED
B1B1 : 26 0A "& " bne LB1BD
B1B3 : F6 11 0C " " ldab X110C
B1B6 : CA 01 " " orab #$01
B1B8 : F7 11 0C " " stab X110C
B1BB : 20 C3 " " bra LB180 // bra timing calcs
;
B1BD LB1BD: // interp routine
B1BD : FE 10 C4 " " ldx X10C4
B1C0 : DF 69 " i" stx X0069
B1C2 : 71 1F 7D "q }" aim #$1FX007D
B1C5 : 72 10 7D "r }" oim #$10X007D
B1C8 : CE BA 00 " " ldx #REG_FIRE
B1CB : DF 74 " t" stx X0074
B1CD : CE BB F0 " " ldx #RPM_SCALE_FIRE
B1D0 : DF 76 " v" stx X0076
B1D2 : CE BB E0 " " ldx #TP_SCALE_FIRE
B1D5 : DF 78 " x" stx X0078
B1D7 : BD 80 D9 " " jsr L80D9 // INTERPOLATE
B1DA : 36 "6" psha // REG_TIMING -> A on STACK
B1DB : 71 1F 7D "q }" aim #$1FX007D
B1DE : 72 10 7D "r }" oim #$10X007D
B1E1 : CE BC 00 " " ldx #HIGH_FIRE
B1E4 : DF 74 " t" stx X0074
B1E6 : CE BB F0 " " ldx #RPM_SCALE_FIRE
B1E9 : DF 76 " v" stx X0076
B1EB : CE BB E0 " " ldx #TP_SCALE_FIRE
B1EE : DF 78 " x" stx X0078
B1F0 : BD 80 D9 " " jsr L80D9 // INTERPOLATE
B1F3 : 33 "3" pulb // REG_TIMING -> from STACK to B
B1F4 : 10 " " sba // A=A-B (HIGH_TIMING -= REG_TIMING)
B1F5 : B7 10 C2 " " staa X10C2 // DIFF_TIMING
// HIGH_TIMING = 10C2 (positive 103D) + REG_TIMING (110D)= HIGH_TIMING
B1F8 : 17 " " tba // REG_TIMING (from B to A)
B1F9 : B7 11 0D " " staa X110D // REG_TIMING
B1FC : D6 58 " X" ldab UNKNOWN_(0058)
B1FE : C5 40 " @" bitb #$40 // 0058#$40 set?
B200 : 27 08 "' " beq LB20A // not set
// 0058#40 set
B202 : B0 B9 2D " -" suba XB92D // REG_TIMING-=B92D(04)
B205 : 24 17 "$ " bcc LB21E // Not negative STORE IGN_TIMING
B207 : 4F "O" clra // Clear difference
B208 : 20 14 " " bra LB21E // Negative STORE IGN_TIMING
;
B20A LB20A: // 0058#$40 not set
B20A : F6 10 55 " U" ldab X1055
B20D : F1 BF D4 " " cmpb XBFD4 // $41
B210 : 24 0C "$ " bcc LB21E //
B212 : B6 10 5F " _" ldaa X105F
B218 : BD 80 9F " " jsr L809F // Interpolate
B21B : BB 11 0D " " adda X110D // add REG_TIMING
B21E LB21E:
B21E : B7 10 3D " =" staa IGN_TIMING (REG_TIMING)
B221 LB221:
B221 : 39 "9" rts |
|
|
| Back to top |
|
|
Vetal
Joined: 08 Feb 2006
Posts: 120
|
| Posted: Mon Jan 21, 2008 3:58 pm Post subject: |
|
|
| lyckaon wrote: | What's your engine management software? I use Nistune, and with the datalog I see that the real timing is about the number in the map minus 22.
That mean that if you have 22 in the map (with romeditor for exemple) your real timing is about at 0° BDTC |
You see numbers relative to whatever your base timing is physically set as. Turn the CAS a millimeter - and your REAL timing will change. |
|
| Back to top |
|
|
Vetal
Joined: 08 Feb 2006
Posts: 120
|
| Posted: Mon Jan 21, 2008 3:58 pm Post subject: |
|
|
| Guys what do you use for knock detection on CA18DET? |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
