Nistune Formal Release 1.2.21 [update]
Moderator: Matt
Re: Nistune Formal Release 1.0
Nope it will be only a few lines change between those models now the base code is done
Re: Nistune Formal Release 1.0
any ETA on the next release, and what will be included?
Re: Nistune Formal Release 1.0
Will be putting up today. I've been holding off pending a few last minute changes
Re: Nistune Formal Release 1.0
Version put up today to support Feature Pack #1Version 1.2.6
Add code to automatically reset corrupted Moates emulators
Add rev limit hysterysis and counts
Fix update rates causing freeze when wideband connected
Add C35 Laurel RB25DET NEO definitions
Remove N13 CA18DE TPS input gauge
Add K11 VQ maps and update address files
Fix A32 TTP min error
M30 Address file updates
Add S14, S14A, S15, HCR32, BNR32 Feature Pack address definitions
MPH/KMH speed parameter fixes
Add warning messages for power cycle after burn for selected vehicles
Fix bug from 1.2.4 causing TP=0 on Consult2 compatible ECUs
Rename K constant to TP Injection multiplier
Add total injection multiplier parameter
Fix consult timeout freeze
(flex fuel, launch control, fan control firmware)
I have working firmware for S14 SR20DET (74F00), S14A SR20DET (83F00) and S15 SR20DET (93F00). Still putting together documentation (50% complete)
HCR32 and BNR32 has been coded but there is a crash bug in the firmware so I need to sort that out once documentation is completed
Re: Nistune Formal Release 1.0
why not 69F ?Matt wrote: I have working firmware for S14 SR20DET (74F00), S14A SR20DET (83F00) and S15 SR20DET (93F00). Still putting together documentation (50% complete)
Re: Nistune Formal Release 1.0
curious about the launch control...i have a type 3/4 RT (96 G20)Matt wrote:Version put up today to support Feature Pack #1Version 1.2.6
Add code to automatically reset corrupted Moates emulators
Add rev limit hysterysis and counts
Fix update rates causing freeze when wideband connected
Add C35 Laurel RB25DET NEO definitions
Remove N13 CA18DE TPS input gauge
Add K11 VQ maps and update address files
Fix A32 TTP min error
M30 Address file updates
Add S14, S14A, S15, HCR32, BNR32 Feature Pack address definitions
MPH/KMH speed parameter fixes
Add warning messages for power cycle after burn for selected vehicles
Fix bug from 1.2.4 causing TP=0 on Consult2 compatible ECUs
Rename K constant to TP Injection multiplier
Add total injection multiplier parameter
Fix consult timeout freeze
(flex fuel, launch control, fan control firmware)
I have working firmware for S14 SR20DET (74F00), S14A SR20DET (83F00) and S15 SR20DET (93F00). Still putting together documentation (50% complete)
HCR32 and BNR32 has been coded but there is a crash bug in the firmware so I need to sort that out once documentation is completed
when i asked before (years ago) it was said i would need new firmware flashed..
so is this still needed? if so can i flash it myself? i have a few devices capable of flashing Nands & NORs...
is there a process for this i can follow? or do i need to send my ECU back to autovaughn?>
Re: Nistune Formal Release 1.0
69Fxx and other can be done. Just a matter of getting it tested locally first. You can load 74Fxx into a 69Fxx ECU
Full board reflash is required. Base image programmer is required to reflash. Other programmers will not work with our boards. Remember you are programming a board, not a chip.
Full board reflash is required. Base image programmer is required to reflash. Other programmers will not work with our boards. Remember you are programming a board, not a chip.
Re: Nistune Formal Release 1.0
Documentation completed:
http://www.nistune.com/docs/Nistune_Feature_Pack_V1.pdf
http://www.nistune.com/docs/Nistune_Feature_Pack_V1.pdf
Re: Nistune Formal Release 1.0
Any chance the feature pack will be release for the Z31?
Re: Nistune Formal Release 1.0
Does/Will this include the S14 KA24DE (23710-70F00)? I didnt see it in the address file listing.Matt wrote: - Add S14, S14A, S15, HCR32, BNR32 Feature Pack address definitions
Re: Nistune Formal Release 1.0
I knew this would happen... no other vehicles yet!!!
For now we are going to test on the few select models I have physically here. Once these are confirmed all working fine then I will move the code across to the other ECU code bases
Z31 is possible. There may be some slight code changes moving the code from 6303 to 6802 CPU (not as many instructions such bitmask settings opcodes).
I dont see a problem doing the S14 KA24DE but I need to disassemble the code a little further. I would plan on doing ER34 code firstly and testing on my vehicle here and assuming that all goes well then S14 KA24DE next
At this time R32 code is to be finalised (ran out of time last week due to several customer ECUs consuming most of that time) so I'll do that next on Tuesday.
At the moment I'm getting my arduino to do flex conversion from frequency to voltage. Once all confirmed and working I'll get a few of those made up to replace the Zeitronix
For now we are going to test on the few select models I have physically here. Once these are confirmed all working fine then I will move the code across to the other ECU code bases
Z31 is possible. There may be some slight code changes moving the code from 6303 to 6802 CPU (not as many instructions such bitmask settings opcodes).
I dont see a problem doing the S14 KA24DE but I need to disassemble the code a little further. I would plan on doing ER34 code firstly and testing on my vehicle here and assuming that all goes well then S14 KA24DE next
At this time R32 code is to be finalised (ran out of time last week due to several customer ECUs consuming most of that time) so I'll do that next on Tuesday.
At the moment I'm getting my arduino to do flex conversion from frequency to voltage. Once all confirmed and working I'll get a few of those made up to replace the Zeitronix
Re: Nistune Formal Release 1.0
Will the Total Injection Multiplier fix the S14 SR20 refuse to go to open loop at low rev high load (ie : O2 flage switched off but still not following AF target on the map) ?
Re: Nistune Formal Release 1.0
I think it should fix any problems associated with moving K too much and affecting tables depending on it such as this. I have not looked closely at closed loop on my S14 since putting the change in but will check it out
Re: Nistune Formal Release 1.0
In this PDF page 15, should it be RB26 ?Matt wrote:Documentation completed:
http://www.nistune.com/docs/Nistune_Feature_Pack_V1.pdf
Re: Nistune Formal Release 1.0
yeah thats a typo. Fixed for next update
I've done the HCR32 RB20 code so that is ready for testing. Next BNR32 RB26
I've done the HCR32 RB20 code so that is ready for testing. Next BNR32 RB26