basics of tuning delco non $12p

[drift-it]

good to hear you got some good results.

with your wideband do you get about .5 more on the tp display? and if so which one is correct? the gauge or TP?

[VL400]

From what I can tell the torque management strategy works by first calculating an estimate of the torque. It uses the airflow and RPM along with a few modifiers, the max torque table is just to limit the airflow for the calculation (it normlly just uses the measured airflow). The ECU retards timing using the excess torque table - which is probably all zero'd out.

Burst knock retard is worth disabling (enabled on S/C and disabled on NA), it pulls timing on sudden throttle movements to help prevent knock - if no knock occurs it pulls a little less (the offset item).

Will be adding more as I can

[sprattzvx]

From what I can tell the torque management strategy works by first calculating an estimate of the torque. It uses the airflow and RPM along with a few modifiers, the max torque table is just to limit the airflow for the calculation (it normlly just uses the measured airflow). The ECU retards timing using the excess torque table - which is probably all zero'd out.

Burst knock retard is worth disabling (enabled on S/C and disabled on NA), it pulls timing on sudden throttle movements to help prevent knock - if no knock occurs it pulls a little less (the offset item).

Will be adding more as I can

mate the stuff you guys do is bloody awesome and fully appreciated. thanks a bunch.
u got some serious brainwaves goin on i bet you could do a rubix cube pretty quick

[antus]

Thanks for that explination. I just copied it to the faq

[Holden202T]

just had a thought after reading VL400's info, is there any timing removed at the same time its going rich in first, or is the timing not following the commanded ?

[sprattzvx]

ill check

just had a thought after reading VL400's info, is there any timing removed at the same time its going rich in first, or is the timing not following the commanded ?

[sprattzvx]

202 theres no timing pulled when its rich. with the updated xdf ive been able to play with all the torque management and burst knock.
with the real time setup working a charm, im planning on booking the dyno (80km trip) for an hour or so in the next month.
been setting up the xdf/adx for full data tracing, but im unsure why the main spark table tracing doesnt seem accurate. it uses the same adx link as the injector constant table etc which works great. title mg/cyl, data type mass a/f, stock units gp/second.
any ideas?
this snap was taken at steady rpm whilst playing with the idle and wotnot.

incorrect.jpg (98.97 KiB) Viewed 5165 times

[VL400]

If you can post up a log, along with your modified XDF and ADX will check it out.

[sprattzvx]

If you can post up a log, along with your modified XDF and ADX will check it out.

idle.xdl

(199.26 KiB) Downloaded 324 times

data trace.adx

(113.27 KiB) Downloaded 396 times

data trace.xdf

(261.86 KiB) Downloaded 376 times

there the gear mate.
thanks.

[krusty]

Ken, there is a setting that retards commanded timing by a negative value under certain conditions. eg if you have commanded 30 degrees timing at a given point and the criteria for this parameter have been met then the parameter value of -10 (eg only here) will give you an actual timing of 20degrees spark advance.

Sorry for all the vagueness but it' caught me out before when setting up idle on a cammed L67