Table ranges.

Holden/Delco Tuning. ALDL, OBD 1.5. Circa 1989 to 2004.
0081(2)
Posts: 149
Joined: Wed Oct 31, 2012 8:59 am
cars: VY commodore supercharged V6
Location: Sydney

Table ranges.

Post by 0081(2) »

I know i have read this before but i cant find it.

When you use data tracing and you see the bubble between cells say rpm to keep it easy it might be showing half in the 2000 rpm mark and half in the 2400 rpm mark which cell is it using or does it range between the two ??
User avatar
VL400
Posts: 4991
Joined: Sun Mar 01, 2009 4:54 am
cars: VL Calais and Toyota Landcruiser. Plus some toys :)
Location: Perth, WA

Re: Table ranges.

Post by VL400 »

It interpolates between the cells. In a 3D table (ie spark advance) it interpolates between both X and Y axis.
User avatar
Holden202T
Posts: 10435
Joined: Sat Feb 28, 2009 11:05 am
Location: Tenambit, NSW

Re: Table ranges.

Post by Holden202T »

the answer is you need to either get the engine to be at one or the other rpm or you need to adjust both cells .....

basically the closer it is to 2400rpm the more percentage of that number is used, if you look at it this way, if you have 2400 = 10 and 2000 = 6 ... at 2200rpm your value delivered might be 8, then at 2300rpm its going to be 9 etc .... but then if you change 2400rpm cell only the values in between will also be offset to be evenly in between the 2000 and 2400 .... so 2000 value stays the same, but then going to 7.5 in the 2400rpm cell, then means your looking at 2200 value of around 6.75 etc ....

the long and the short of it, if you can load it exactly on a cell axis to get the most accurate results.

if you can't then its probably just going to mean more work to get the averages right!
0081(2)
Posts: 149
Joined: Wed Oct 31, 2012 8:59 am
cars: VY commodore supercharged V6
Location: Sydney

Re: Table ranges.

Post by 0081(2) »

Thanks thought that was the case
User avatar
antus
Site Admin
Posts: 10016
Joined: Sat Feb 28, 2009 10:34 am
cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007

Re: Table ranges.

Post by antus »

Yep, and this is why your table needs to be smooth to tune it. If you collect histogram data and apply it wholesale to the table and ends up looking like a porcupine your next round of data is going to be way out. You need to think about an area of the table, look at the collected data and make the changes while keeping the table smooth.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396