Operations - AFR AutoTune
1. Set the AFRs that you require in this window
(You can copy/paste AFRs into this table from the Fuel map if you wish)
- Updated: Now there is a copy button to grab target AFRs from your fuel map
2. Open up your fuel map to observe changes as they are made
3. Save your settings for next time
4. Updates - This window specifies how many AFR updates are required on the current selected cell before AFR adjustments are made. Updates for most wideband units are every 30ms, so 5 x 30ms = 150ms by default before it kicks in for the current cell
The reason for this is that I found that whilst adjusting AFRs that there is some delay after the change for it to reach the wideband sensor (when using techedge). You can adjust this to make it work appropriately
5. Range 5% or 2%. This is the range that the current AFR must be in for no more changes to occur. This allows a raw tune then fine tune afterwards
6. Enable autotune then modify your AFR window and fuel map and see how it goes making changes to the fuel map based on feedback. I suggest monitoring filtered values rather than target AFRs to see the effect on changes
Update: Select areas of the map and use space bar to 'grey' out areas of the map that you dont want changed (latest beta versions)
Knock monitoring
Operations - Knock / Warning Panel
1. Select external knock
(Note: ECU knock - only functional on some ECUs and sampling rate needs to be improved for better detection)
2. Below the external field is the sensor which you will use to trigger the knock count.
If you use a wideband unit or DLP A/D converter then you select one of the AUX inputs you have available and connect it to your knock device
Select this AUX input from the drop down list. Next to 'external' are two fields. The LHS field is the AUX input value (eg voltage of sensor detected) and the RHS field is adjustable trigger input value. Eg you can set to 3 volts trigger value
3. When the read AUX value exceeds the trigger AUX value set then the 'knock count' value will increase
4. Once there are a certain amount of knock counts on a single cell, and this exceeds the knock count setting (default vlaue 5) then when the 'Timing Map Adjust' field is ticked, the timing map value will decrement by 1 for each time knock count is reached. The knock count will reset internally (so if knock count is 25 on a particular cell, then it would have decremented 5 times)
5. Alarm sounds are now a short blip each time knock or other limits are exceeded. You can set limits for temperature, rpm etc. Useful also as a speed warning device when you are going too fast
6. To obverse the knock count for the timing map, the knock count register has been made available in the 'Wideband Input Tracer' available under the operations menu
Display knock count 'Current' and this will show you how many knock counts were detected for each cell. I'm sure that is gonig to be useful. You can also look at the Fuel/Timing maps and click the 'Knock' tickbox to view in red cells which have knock count occur at least once on them
Knock is now also recorded in the log file as a small red marker at the top of the log. This can be used for playback which will display knock on the maps and in the warning during playback
WARNING!!!
The factory ECU knock detection may also detect knock in certain parts of the map where the knock flag is set. You may wish to disable knock flags in the timing map or disconnect factory knock sensor if you wish to only retard timing from the map within NIStune
Also - The knock detect/sense facility provided here to retard your timing map is dependent on your triggers and knock count being set correctly in addition to your external knock unit being detected correctly
When tuning, still use knock detection headphones and dont rely just on NIStune to determine your knocking for you - this is beta functionality
Obviously try to avoid knock in the first place, and use this facility as a backup rather than primarily for tuningm avoid any leadup to engine damage. If you start increasing timing and do not notice an increase in torque or can hear audiable pinging then start pulling your timing back
Let me know how your testing goes and what needs to be improved and if it is useful to you. I've tried to get this as bug free (I have no problems listed currently) during simulation testing so it is usable but need to get my car back on the road for other testing
thanks
Matt
i have mainly test it at idle