killerbee
July 25th, 2009, 04:58 AM
In reviewing logs for several weeks now, something needs a change.
The logs make pretty good sense. However, as you go from B1115 to B1102, the cursor for torque is in the wrong place.
The final fuel value in the logs, IS correct.
The GM.ENGTRQREF DMA is not representative of "desired torque". I am not sure of the origin of this pid. :) We need something that translates the (desired torque) value derived from B1115. Is there something else that can be put in place of this torque pid in cal_link to make log readbacks integral for torque?
Here is a WOT example where i have defined 627 as 100% TP desired torque, shown in blue. That value, 82mm is, in fact, the fuel delivered, and the torque pid is highlighting an incorrect value.
Throttle pids are NOT part of the problem. Thanks.
http://forum.efilive.com/attachment.php?attachmentid=5910&d=1248544495
The logs make pretty good sense. However, as you go from B1115 to B1102, the cursor for torque is in the wrong place.
The final fuel value in the logs, IS correct.
The GM.ENGTRQREF DMA is not representative of "desired torque". I am not sure of the origin of this pid. :) We need something that translates the (desired torque) value derived from B1115. Is there something else that can be put in place of this torque pid in cal_link to make log readbacks integral for torque?
Here is a WOT example where i have defined 627 as 100% TP desired torque, shown in blue. That value, 82mm is, in fact, the fuel delivered, and the torque pid is highlighting an incorrect value.
Throttle pids are NOT part of the problem. Thanks.
http://forum.efilive.com/attachment.php?attachmentid=5910&d=1248544495