Spark table bug?

[spittybug]

Unless I'm doing something wrong....which is always on the table!!!

I'm running alpha n for fuel but speed density for ignition load (works well for me, that's not the issue). There seems to be a disconnect between the graphical reading of spark 2 advance and what it shows on the table on the right side of screen. I think it has something to do with axis units? I've attached a short log. I've tried with my tune file open and closed both, no difference. VE is fine. There's also data for adv table 3, yet I don't have one.......... Bug or am I doing something wrong?

Don't mind some of the weird fueling numbers; they are good in the driving area and I need to clean the rest up.

Thanks guys.

[slow_hemi6]

I had a look and it does seem to apply the same y axis field to both tables. Might have something to do with the tuning feature as opposed to just being a viewer. If you go into Options tab and select Default Y Axis you can change the axis field, I was hoping selecting Load would use the applicable load for each table but it just seems to use the fuel table load for both tables. Have to wait for an answer from Phil I guess.

[LT401Vette]

You can set the Y axis load specific to a table by right clicking on the tables Y axis and select "Set Y-Axis Over-ride"

[spittybug]

I changed the axis using the override.... closed and reloaded. Changing it to TPS makes the blue ball trace disappear.

The advance table hardly ever gets more Y than the first or second row at most. That's 25 to 35 if in kPa or 0 to 1 in TPS. The real kPa is much greater than that load, shows correctly on graph, yet not on this table. The RPM change is tracking properly.

In TS my advance table uses load/RPM (speed density). The VE uses TPS/RPM (alpha n)

Something isn't changing in terms of units....

[slow_hemi6]

Try using MAP for the y axis as opposed to Load.