Brent,
Following on from my problems with MAP discussed elsewhere, it would have been very useful to have 2 lines for advance: the 'basic 2D advance' from the set-up table, and 'basic advance + load variation'. This would help both MAP and TPS users as it would indicate the fine adjustments that the load sensor (of whatever type) is making to the basic setting.
Alternatively, the extra line could be just the 'load advance variation', but that would be on quite a small scale.
cheers,
David
Extra line of log data?
Moderators: JeffC, rdoherty, stieg, brentp
-
- Posts: 204
- Joined: Tue Feb 14, 2006 2:14 pm
- Contact:
Maybe it's an extension of the discussion we had several months ago where the final map can be considered as the sum of two maps overlaid on each other:
- a 2D rpm map (every column the same)
- a 2D load map (every row the same)
...and the logging reports the two (interpolated) values that have contributed to the current advance ie the 2D rpm value and the delta load value.
But given that the MJLJ only knows the final map, and not the constituent parts, it wouldn't be possible (unless you "wasted" a row at say 0kPA to define the base 2D rpm map and then did sums to remove the 2D rpm advance from the current total advance)
If you see what I mean
- a 2D rpm map (every column the same)
- a 2D load map (every row the same)
...and the logging reports the two (interpolated) values that have contributed to the current advance ie the 2D rpm value and the delta load value.
But given that the MJLJ only knows the final map, and not the constituent parts, it wouldn't be possible (unless you "wasted" a row at say 0kPA to define the base 2D rpm map and then did sums to remove the 2D rpm advance from the current total advance)
If you see what I mean
-
- Posts: 204
- Joined: Tue Feb 14, 2006 2:14 pm
- Contact: