panel wrote:I see ignition tables tweaked into the decimal points sometimes. How are you determining that last increment? Where someone would have 28 but you have 28.4 etc.
It's no great insight, just software interpolation. (IIRC it takes the axis entries % spread into account to keep the slope linear)
That's mostly from manual smoothing in TS, drag select an area and hit the magic wand, it will scale from the 4 corners or ends of the selected area on one row/column.
When you use the up or down keys/buttons while interactively tuning a cell or block it increments in tenths as well, so it's a combination of both.
Also:
Note MS multi table function can cascade the tables automatically either vertically or horizontally, allowing really stupid resolution. (in other words, if i added a turbo, I could create a boosted map for >100 KPA, there is one row or column lost to overlap, it essentially creates one (effective) table from the two or 3 being cascaded. VEAL can tune them all.)
You're saying that you can have your AFR table,Ignition table and your VE table all set at different RPM/MAP values?
That was not the main point I was trying to make... I was lamely trying to explain cascaded tables. (not just for AFR)
Yes, firmware interpolates smoothly within the tables, a certain amount of that is inherent as the VE tables are each 16x16 and the AFR and ignition tables are 12x12.
(VEAL only deals with AFR, I meant to say VEAL can work with the cascaded AFR tables)
If you don't care for that , you can set AFR to 12x12 as well and make all your bins match perfectly, but I haven't heard of or seen any issues with the interpolation.
EDIT---It's still going to interpolate between cells.