Matt, is it a bug ?
Moderator: Matt
Matt, is it a bug ?
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 ?
- Attachments
-
- Image3.jpg
- (16.08 KiB) Downloaded 4688 times
-
- Image2.jpg
- (16.14 KiB) Downloaded 4689 times
-
- Image1.jpg
- (17.61 KiB) Downloaded 4690 times
Also when I load S14 SR20DET address, load S14 bin, it will show this.
- Attachments
-
- Image4.jpg
- (68.39 KiB) Downloaded 4685 times
-
- Posts: 74
- Joined: Sat Mar 22, 2008 7:39 am
- Location: Denmark
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 ?
Should I uninstall Nistune and go back to NIStune Version 0.9.3.6.1 ?
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!
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,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!
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.
- Attachments
-
- Image6.jpg
- (235.47 KiB) Downloaded 4636 times
Load another rom file, 23710 -69F00, fuel map seems not right too.
- Attachments
-
- Image7.jpg
- (233.49 KiB) Downloaded 4633 times
Load HCR32 23710-11U00 address and rom file, it looks ok !
- Attachments
-
- Image8.jpg
- (205.63 KiB) Downloaded 4630 times
When loading all SR20DET and CA18DET rom files, I also notice that the TTP min ,TTP max and the REV sacle are not correct.
- Attachments
-
- Image10.jpg
- (114.53 KiB) Downloaded 4627 times
-
- Image9.jpg
- (117.64 KiB) Downloaded 4628 times
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!
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!
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 ?
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 ?
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
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
- Attachments
-
- rb20_ttpminmax.JPG
- RB20 ttpmin/max
- (136.02 KiB) Downloaded 4520 times
-
- sr20_ttpminmax.JPG
- SR20 ttpmin/max
- (140.02 KiB) Downloaded 4520 times
-
- s13_ca18_ttpmin_max.JPG
- S13 CA18 ttpmin/max
- (126.96 KiB) Downloaded 4520 times