Nistune 0.10.16 Release
Posted: Tue Apr 17, 2012 1:12 am
Version 0.10.16 Release
Fixed bugs:
VQ Map offset correction issue in 0.10.15 for S13 CA18
S13 CA18DET VQ map display. Actually 1040mv first cell, then increments
VQ map display % problems
Update Help F1 quick keys
Wideband crash on reconnect. Make wideband main classes polymorphic
Log file name wraps around if too long
Check map marking functionality still works
When opening synced image as comparison and main is blanked, unsynced error msg
Auto tune grey out 'don’t tune' areas are wiped out with maptrace cursor
Remove AFR lookup tables where not needed for interpolation in wideband folder
Having programmer and DLP plugged in, Nistune thinks one is an emulator
Enhancements:
Autotune VE map [Note: This has been disabled*]
VQ Map autotuner
Right click VQ map to allow offset for R31/Z31/VLT
Above changes fix the VQ map issue introduced in 0.10.15 (release has been pulled because of that problem). Accuracy of the map trace cursor vs actual changes have been confirmed on several ECUs.
Main areas of focus these two weeks were the AFR autotune fixing and testing.
AFR autotuning using the VQ map option works as expected. VQ map adjustments are made until target AFRs are reached. Note that once you modify the standard VQ map, Nistune will not be able to determine what VQ map this was. Altering the VQ map removes the address file defined voltage offset for consult gauge display for the AFM voltage for older ECUs (R31/Z31/VLT). I've added a right click offset tickbox to force using the offset when the VQ map has been altered. This has been tested tonight on my R31
*VE map auto tune has completed implementation but in vehicle testing tonight showed it does not behave as expected. Adjusting the VE map where the maptrace cursor sits do not adjust injection time/AFRs as expected with O2 disabled, so I will review the map trace cursor location vs hardware tracing. Also the fuel map ranges for VE map enabled ECUs are different and need to be altered where a VE map exists. I would not suggest using auto tune on vehicles with VE map (only a few but these include ER34, S14KA, B14 SR, K11 etc) until the min/max ranges for checking are updated
Fixed bugs:
VQ Map offset correction issue in 0.10.15 for S13 CA18
S13 CA18DET VQ map display. Actually 1040mv first cell, then increments
VQ map display % problems
Update Help F1 quick keys
Wideband crash on reconnect. Make wideband main classes polymorphic
Log file name wraps around if too long
Check map marking functionality still works
When opening synced image as comparison and main is blanked, unsynced error msg
Auto tune grey out 'don’t tune' areas are wiped out with maptrace cursor
Remove AFR lookup tables where not needed for interpolation in wideband folder
Having programmer and DLP plugged in, Nistune thinks one is an emulator
Enhancements:
Autotune VE map [Note: This has been disabled*]
VQ Map autotuner
Right click VQ map to allow offset for R31/Z31/VLT
Above changes fix the VQ map issue introduced in 0.10.15 (release has been pulled because of that problem). Accuracy of the map trace cursor vs actual changes have been confirmed on several ECUs.
Main areas of focus these two weeks were the AFR autotune fixing and testing.
AFR autotuning using the VQ map option works as expected. VQ map adjustments are made until target AFRs are reached. Note that once you modify the standard VQ map, Nistune will not be able to determine what VQ map this was. Altering the VQ map removes the address file defined voltage offset for consult gauge display for the AFM voltage for older ECUs (R31/Z31/VLT). I've added a right click offset tickbox to force using the offset when the VQ map has been altered. This has been tested tonight on my R31
*VE map auto tune has completed implementation but in vehicle testing tonight showed it does not behave as expected. Adjusting the VE map where the maptrace cursor sits do not adjust injection time/AFRs as expected with O2 disabled, so I will review the map trace cursor location vs hardware tracing. Also the fuel map ranges for VE map enabled ECUs are different and need to be altered where a VE map exists. I would not suggest using auto tune on vehicles with VE map (only a few but these include ER34, S14KA, B14 SR, K11 etc) until the min/max ranges for checking are updated