Nistune 0.10.16 Release

[Matt]

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

[louiswun]

Hi Matt,

VQ map display % problems >>
In S13 CA18DET, I see 5120% on the table at value 65535, should it be 100% ?

Thank you

[Matt]

Correct. This should not have been in the fixed list.

Whilst I'm on it checked the code, and appears I've set the maximum value for the Y scale (0-100%) instead of X scale (VQ map values). I've changed the typo tonight and rechecked and scales now appear correct. Checked against S13 CA18DET and Z32 VG30DET for two different types of VQ maps. Fix will be in next version

[louiswun]

Every time I click "Display consult gauges" after connect to USB consult port, Nistune 0.10.16 will crash
Window showing this
http://x18.xanga.com/9d1e065b5853528168 ... 465026.jpg
When I have enable Debug Logging, the crash will not disapper at that moment but only show when I click exit Nistune.

[Matt]

Crash when closing with Debug Logging is a known issue with closing down the file properly whilst its still logging. Should sort that one out

However the crash when opening display whilst connected is a new one. Okay so thats S13 36F00 you have got in the screenshot there, will try it tonight without debug logging and see if I can repeat

[ricardomendes]

hi installed yesterday and I have the same window and crash but is when I connect... Maybe a driver problem?
Same ecu at s13 ca18det..

[ricardomendes]

Changed the driver to an older one and is the same, when I connect it break and send the crash message...

[ricardomendes]

tried today with windows7 and a better laptop and it run fine, the other laptop is a acer aspire one with windows xp, i was running version 10.11 in it and never had any problems, this version 10.16 use more memory than the olders?


regards

[Matt]

Yes it will use slightly more memory. I've modified the software to use more static allocation rather than dynamic. This means memory gets allocated upfront, rather than on the fly for some of the objects. It avoids potential problems with memory leaks and heap corruption, where pointers get overwritten or not deallocated

Will try Windows XP with the CA18DET tomorrow and try and repeat the problem here

[Ligouri Rd.]

Version 0.10.16 Release...Autotune VE map [Note: This has been disabled*]...
*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

Does this mean we should not use auto tune for vehicles with VE maps at all or just not use autotune for the VE table?
Also what are your thoughts as to "zero-ing" the VE map by filling it with 128 (raw) values and using autotune in the primary map (assuming this is possible)?

[Matt]

Dont use it yet for vehicles with a VE map. It worked well with my R31 but did not play nicely with the R34 which uses fuel and VE map

Off boost tuning should be adjusted using the VE map rather than altering the fuel map, then making sure AF alpha (trimming) values stay around 100% during the tuning process

[Adrian]

German language package doesn't work. Ther are an error window when you start nistune and all buttons are unknow...

[Matt]

The language files all need to be updated for the new strings recently added in the last few test versions.

I left out all languages other than English in the interim in versions 0.10.14-0.10.16 to avoid any errors

[Matt]

Rebuild and crash issue no longer occurring. Language packs still need updating. Have more time this week for more software work