Timing table VS Scan What gives?
Timing table VS Scan What gives?
Here is the scan results:
Here is the advance with PE, minus base timing as found in the "Main Spark" table, the numbers are close but not right on, the numbers in the log almost appear to anticipate the next cell or something?
90kpa Column
Can anybody explain this?
Code:
RPM kpa SA w/o knock retard 3675 94.9 27.4 3750 94.9 26.7 3875 94.54 26.7 3925 94.19 26.4 3975 94.19 26.7 4000 94.19 27.4 4150 94.19 27.4 4225 93.47 28.5 4375 93.47 28.5 4425 93.11 29.5 4400 92.76 29.2 4600 92.4 30.6 4800 92.04 30.9 4875 91.33 31.3 4950 91.33 31.3 4950 90.97 31.6 5075 90.25 31.6 4950 90.25 32
90kpa Column
Can anybody explain this?
Moderator
iTrader: (1)
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
Looks normal. As for the anticipating the next cell. . . the code does a 16 point interpolation between cells (man I wish these port 135 hits would go away, people, clean up and patch your PCs!!).
On a 3d table such as the SA table this is done 3 times: between the two columns, between the two rows, then between those two values. The final value is then fed to the EST.
RBob.
On a 3d table such as the SA table this is done 3 times: between the two columns, between the two rows, then between those two values. The final value is then fed to the EST.
RBob.
Moderator
iTrader: (1)
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
Originally posted by tpi_roc
So seeing 28° commanded at 3200 rpms and 90kpa means Im going to end up with a mix of the previous and adjacent cells?
Where is this routine located?
Thanks for all the help Rbob
So seeing 28° commanded at 3200 rpms and 90kpa means Im going to end up with a mix of the previous and adjacent cells?
Where is this routine located?
Thanks for all the help Rbob
If you had chosen 3000 RPM & 90 Kpa, then yes, the SA would be halfway between the 2800 & 3200 RPM values at 90 KPa. The routine always interpolates, it just depends upon the distance between adjacent cells for the final value.
Here is the header & location of the 3d lookup routine (AXCN, see the ANHT hac for specifics):
Code:
;*====================================================
;
; 3D Look up routine. Returns with the table value,
; (interpolated), based on 2 independent inputs.
;
; INPUTS:
; 1. R min value, (Rows)
; 2. Q min value, (Col's)
; 3. RNUM, number of Q Vals, (col's)
; in each R table
; 4. Thr 1st R table, R num entries in length
;
; 4 + RNUM secont R table
; 4 + (N-1) Nth R table
;
; CALL WITH:
; A Reg = R input, (Row arg)
; B Reg = Q input, (Coll arg)
; X Reg = Table start address
;
; RETURNS WITH:
; A Reg = F(Q,R)
;
; EXEC TIME: 257 - 264 Cycles
; SRACK REG: 9 Bytes
; CODE LENGTH: 114 BYTES
;
;
;*====================================================
LE353: PSHY ;
PSHB ;
PSHX ;
SUBA 0,X ; CALC ROW ARG OFFSET, (LIMITED TO 0)
BCC LE35C ;
; .... else
CLRA ; Gotcha
But this still leaves me with unexplained missing timing then because with this example:
4800 92.04 30.9
The rpm falls right on 4800, which should result in 33.02° timing according to my main spark + PE, or does the 92.04 KPA not being 90kpa even make the difference of 2~ degrees?
But this still leaves me with unexplained missing timing then because with this example:
4800 92.04 30.9
The rpm falls right on 4800, which should result in 33.02° timing according to my main spark + PE, or does the 92.04 KPA not being 90kpa even make the difference of 2~ degrees?
Moderator
iTrader: (1)
Joined: Mar 2002
Posts: 18,432
Likes: 233
From: Chasing Electrons
Car: check
Engine: check
Transmission: check
Originally posted by tpi_roc
Gotcha
But this still leaves me with unexplained missing timing then because with this example:
4800 92.04 30.9
The rpm falls right on 4800, which should result in 33.02° timing according to my main spark + PE, or does the 92.04 KPA not being 90kpa even make the difference of 2~ degrees?
Gotcha
But this still leaves me with unexplained missing timing then because with this example:
4800 92.04 30.9
The rpm falls right on 4800, which should result in 33.02° timing according to my main spark + PE, or does the 92.04 KPA not being 90kpa even make the difference of 2~ degrees?
Another factor that needs to be taken into account is the way the ALDL works. It is not a snap-shot. The ALDL is a running stream of data where each byte is sent individually. Values in the data stream are taken from different points in time.
RBob.
Thread
Thread Starter
Forum
Replies
Last Post
NufNuffZ28
History / Originality
2
Aug 14, 2015 09:12 AM
db057
TBI
10
Aug 11, 2015 10:11 PM




