Nistune Forums

Hi all,
The data that nistune is pulling from the ecu is very delayed, As you can see below it will take a good 0.6seconds to update from the value before.
700RPM Jumps makes tuning very hard, The data nistune is logging from the Wideband is good, its updated every 0.1 seconds but the data coming from the ecu is very delayed when logged.

The Car is a SR20DE Pulsar.

Time______RPM
03:50.8 4362
03:50.9 4950
03:51.0 4950
03:51.1 4950
03:51.2 4950
03:51.3 4950
03:51.4 4950
03:51.5 4950
03:51.6 5600
03:51.7 5600
03:51.9 5600
03:52.0 5600
03:52.1 5600
03:52.2 5600
03:52.3 6175
03:52.4 6175
03:52.5 6175
03:52.6 6175
03:52.7 6175
03:52.8 6175
03:53.0 6675
03:53.1 6675
03:53.2 6675
03:53.3 6675
03:53.4 6675
03:53.5 6675
03:53.6 6675

Ive also attached the smallest log i could find.

There are two modes when using consult - 'tuner' and 'streaming'

With a NIStune board installed, you can perform full maptracing on both modes.

However for faster logging with a log of inputs enabled use 'streaming' mode. You will not be able to make map changes in this mode, but is similar to NissanDataScan and similar programs which stream the data from the consult port at a fast rate and is ideal for data logging

For faster maptracing whilst tuning and using your wideband, reduce the amount of consult inputs to the minimum that you need. This will significantly increase the speed of your maptrace. For example, you may only wish to select RPM, TP and temperature to do your tuning.

In the next version of NIStune that comes out I have also increased the speed of wideband input sampling into the software so it is more in sync with consult data