Hi All,
I have started to "play" with the versatune software more and more over the last couple of months and need some clarification on the logic utilised for the ignition tables.
For CL and OL ignition tables there are:
Base Timing Normal Extended
Base Timing Normal OverLoad
Max Ignition Timing Extended
I know the Extended and Overload tables are exactly the same on the default High Load map, however what is puzzling me is the Max Ignition Timing Extended Table. I am assuming that +ve values mean the ignition timing is advanced as explained in the tech screen?
If the Base Timing tables are modified to request advanced timing (+ve value compared to standard) then unless the Max Ignition Timing Extended table is changed as well to either the same value or slightly higher (again assuming +ve is more advanced) then the value defined in the Base Timing table will never be achieved. If you refer to the low load values in both CL and OL modes the Base Timing values are higher than the Max Ignition Timing tables.
Is my understanding correct?
Thanks
Lee
Ignition Timing Advance Tables - Logic?
- Steve @ VersaTune
- Lead tuner
- Posts: 1161
- Joined: March 29th, 2010, 12:58 pm
Re: Ignition Timing Advance Tables - Logic?
The "Max" name is a bit misleading. It appears that the ECU starts at the base timing and moves toward the "Max" timing value. In very low load situations, it will actually decrease timing going from base to max.
Re: Ignition Timing Advance Tables - Logic?
Hi Steve,
Thanks for the feedback. OK, so the Max table is actually the target for the ECU to achieve starting at the base value, regardless of +ve or -ve values!
Good to know, thanks!
Lee
Thanks for the feedback. OK, so the Max table is actually the target for the ECU to achieve starting at the base value, regardless of +ve or -ve values!
Good to know, thanks!
Lee
Re: Ignition Timing Advance Tables - Logic?
The timing values used are those from the Base table. The Max table only establishes some limits so that no matter what you command in the Base table those values cannot go above what's in the correspondent cel in the Mac table.
The Max table should not count when the ECU adjust the timing unless the values in the Base tables exceed what's in the Max tables. At first the values from the Base tables are used and then based on various other variables (BAT, ECT, knock values - as can be seen in the Nigh BAT/ECT timing tables) it will decrease (and only decrease) the timing accordingly no matter what we're talking about open loop or closed loop.
The Max table should not count when the ECU adjust the timing unless the values in the Base tables exceed what's in the Max tables. At first the values from the Base tables are used and then based on various other variables (BAT, ECT, knock values - as can be seen in the Nigh BAT/ECT timing tables) it will decrease (and only decrease) the timing accordingly no matter what we're talking about open loop or closed loop.
2008 Cosmic Blue Mazda 3MPS
Built engine + WMI + GTX3071 gen2, ~550BHP @35PSI
2008 Icy Blue Mazda CX7
Built engine and stock exhaust (YES!!), JBR3" + GTX2867 gen2 + Autotech HPFP, self-tuned to 360-ish BHP
Built engine + WMI + GTX3071 gen2, ~550BHP @35PSI
2008 Icy Blue Mazda CX7
Built engine and stock exhaust (YES!!), JBR3" + GTX2867 gen2 + Autotech HPFP, self-tuned to 360-ish BHP
-
- Posts: 4
- Joined: October 7th, 2013, 3:48 pm
Re: Ignition Timing Advance Tables - Logic?
@mituc,
Thanks for the post, most informative
HOBSPONDER TRANSMISSION
Thanks for the post, most informative

HOBSPONDER TRANSMISSION