Matt, is it a bug ?

louiswun · Post by **louiswun** » Thu May 07, 2009 5:21 am

I have install NIStune Version 0.9.3.6.1 , and then install NIStune Version 0.9.4b, after that, everytime whan I load Nistune, the are some warning message before the main program shows, is it abug or did I did something wrong ?

louiswun · Post by **louiswun** » Thu May 07, 2009 5:23 am

Also when I load S14 SR20DET address, load S14 bin, it will show this.

Mads B (dk) · Post by **Mads B (dk)** » Thu May 07, 2009 9:38 am

you need the newest adresse fil

look in here -> viewtopic.php?t=978

louiswun · Post by **louiswun** » Fri May 08, 2009 12:10 am

Today, I have install april_address_v4.zip , when Nistune load up, no more "Address file invalid instruction ...." warning , but after select address file, load the same rom file from the rom pack, another warning message appear, it is still the same "ECU/Address file mismatch".
Should I uninstall Nistune and go back to NIStune Version 0.9.3.6.1 ?

louiswun · Post by **louiswun** » Fri May 08, 2009 12:16 am

And the fuel map is like this !

Matt · Post by **Matt** » Fri May 08, 2009 2:37 am

what is the ROM file you have loaded, and the address file it is saying you have opened and what you actually have opened

you can always ignore it and continue

newest beta release tonight has v5 address files included in it. let me know how you go with that

older address files will cause those TTP_RECOVERY errors you saw. we included the address files this time to avoid this issue reoccuring!

louiswun · Post by **louiswun** » Fri May 08, 2009 4:04 am

Matt wrote:what is the ROM file you have loaded, and the address file it is saying you have opened and what you actually have opened

you can always ignore it and continue

newest beta release tonight has v5 address files included in it. let me know how you go with that

older address files will cause those TTP_RECOVERY errors you saw. we included the address files this time to avoid this issue reoccuring!

I have just installed NIStune Version 0.9.5b,
Load address file, no problem,
Load rom file from the rom pack NIStune ROM File Pack 2.0
I have load 23710-74F00, but the fuel map seems not correct.

louiswun · Post by **louiswun** » Fri May 08, 2009 4:15 am

Load another rom file, 23710 -69F00, fuel map seems not right too.

louiswun · Post by **louiswun** » Fri May 08, 2009 4:20 am

Load HCR32 23710-11U00 address and rom file, it looks ok !

louiswun · Post by **louiswun** » Fri May 08, 2009 4:41 am

When loading all SR20DET and CA18DET rom files, I also notice that the TTP min ,TTP max and the REV sacle are not correct.

Matt · Post by **Matt** » Fri May 08, 2009 11:38 am

23710-74F00/69F00
See what you are talking about they are doing something odd with the 'filtered view' off the map

Okay what the problem is that we have a VE MAP flag in the base address files which should be in only specific address files with the VE maps

I've made an update the affected address files and put this into another release just then 0.9.5.1b has the fixed address files on the downloads page

Looks fixed now. Thanks for finding that!

Matt · Post by **Matt** » Fri May 08, 2009 11:39 am

Regarding the scales. Those look right

The RPM on the table matches the RPM at the X axis of the graph

The 'ms' pulsewidth on the table matches the ms on the Y axis of the graph

The scalings are correct as I verified the RPM against hardware trace on S13 and HCR32

louiswun · Post by **louiswun** » Fri May 08, 2009 3:57 pm

Hi Matt,
In CA18DET and SR20DET, the TTP min and TTP max seems to be reversed, the TTP min map in Nistune is captured the TTP max HEX data in the rom file, and TTP max map is captured the TTP min HEX data. And I think the RPM scale showing in the TTPmin/TTP max, should be accroding to "Fuel RPM Scale" .
In HCR32 RB20DET, the TTP min and TTP max is correct.
What do you think ?

Matt · Post by **Matt** » Sun May 17, 2009 2:09 am

Please see attached. This is what I think it should look like

TTP min has a smaller higher resolution scale than TTP max

This is verified with hardware maptrace confirming ECU access on particular RPM

S13 CA18 has less points than the other ECUs and the map appears 'backwards' but trace confirms that RPMs are increasing in appropriate direction in the map

S13 CA18 TTPmin/max when adjusted will directly affect injection however and appear to modify current injection when between these points more than just being a pure limiter