Accesstuner question

[ryst]

So, I'm just starting out using Accesstuner, and the first thing I ran into that I can't figure out is editing the axises. I don't have a *need* to edit them right now, but I could see it being useful at some point. One thing I noticed is the Cobb Stock Stage0 tune and the Cobb Stage1-3 have different axis labels on the Boarderline timing table. Here's an example:
Cobb Stage0

Cobb Stage3


Along the (x) RPM axis, the Stage0 tune, goes 750,1000,4000,5000,6250,6250,6250,6250,6250,6250 and the Stage3 (also true for Stage1 and 2) goes 750,1000,1500,2000,2500,3000,3500,4000,5000,5500,6250 ... The ones on the staged tunes make more sense, and seem like you'd get more consistent spark timing.

Is there something that has to be enabled to be able to edit the axises?

 

[COBB Tuning1]

Is there something that has to be enabled to be able to edit the axises?

On Stage0 you will see exactly how the some of the OEM table axis look (de-normalized). You'll find the axes segregated by folder when they are de-normalized by default. In this case, look for the "Axis BL Timing" to edit the normalizers. We do this in our OTS maps to any table that is changed in our calibration if needed. There's also mention of these in the "5-D table" mention in the beginning of the tuning tips document. The ECU will interpolate between the points when doing lookups and works properly with OEM values. If you decide to normalize the OEM axes, proceed with caution as scaling higher or non-linear will change the timing lookups based on your input.

Cheers,
-Braden @ COBB

 

[ryst]

On Stage0 you will see exactly how the some of the OEM table axis look (de-normalized). You'll find the axes segregated by folder when they are de-normalized by default. In this case, look for the "Axis BL Timing" to edit the normalizers. We do this in our OTS maps to any table that is changed in our calibration if needed. There's also mention of these in the "5-D table" mention in the beginning of the tuning tips document. The ECU will interpolate between the points when doing lookups and works properly with OEM values. If you decide to normalize the OEM axes, proceed with caution as scaling higher or non-linear will change the timing lookups based on your input.

Cheers,
-Braden @ COBB

This makes a lot more sense now, thanks for the response, and I see the X and Y axis tables now. I was't looking in the axis folder

 

[ryst]

If you decide to normalize the OEM axes, proceed with caution as scaling higher or non-linear will change the timing lookups based on your input.

Cheers,
-Braden @ COBB

One quick question though, do you normalize the values just so it's easier to read and interpolate the data for us tuners?

 

[COBB Tuning1]

One quick question though, do you normalize the values just so it's easier to read and interpolate the data for us tuners?

It's done as needed depending on the way the car is responding. If I need to add resolution to a specific range of the table I'll re-scale and adjust the values accordingly so blending is accurate. There are cases where I simply want a better visual representation however, and in those cases it's doing exactly the same thing as the OEM table but is represented better visually in our software.

Cheers,
-Braden @ COBB