Page 7 of 21
Re: Launch control
Posted: Thu Apr 08, 2010 8:58 am
by BlueRB240
I think it's a Type 3 board thing. I'll give it a try and see if it works on my Type 3.
Re: Launch control
Posted: Thu Apr 08, 2010 11:38 am
by Preston
Downloaded update and don't see where it's at either. I have a 93 s13 KADE. Will this work for me?
Re: Launch control
Posted: Thu Apr 08, 2010 5:26 pm
by skyline_stu
I think some of you guys have the wrong idea The version uploaded is the NISTUNE Software with the launch control flags/tables added in (via Nistune board or daughter board)
IT IS NOT THE LAUNCH LIMITER FIRMWARE CODE FOR YOUR NISTUNE BOARD
**** S13 SR20DET available NOW ****
RNN14 Coming soon
RB30 Testing in progress
Check out my Youtube Video done this afternoon to demonstrate its operation.
http://www.youtube.com/watch?v=WfuGsJmXQfo
I also need test vehicles for the development of other ECU/Engines - Let me know if your interested, I'd need your vehicle for 24hrs at my shop to write, test and verify correct operation
Please contact me for further information. S13 SR20DET costs $15 plus P&H - YOU MUST SEND YOUR ECU HERE AS I NEED TO REPROGRAM THE BOARD USING A BASE IMAGE PROGRAMMER.
Skyline_Stu
Re: Launch control
Posted: Thu Apr 08, 2010 5:49 pm
by BlueRB240
Fidel sticks lol I live too faraway.
Re: Launch control
Posted: Thu Apr 08, 2010 7:11 pm
by TM_S13
hum... seems to be working quite nicely.
congrats on the achievement
Re: Launch control
Posted: Thu Apr 08, 2010 10:10 pm
by src
Thanks Matt. I just broke my clutch box so I will test it as soon as I get a new one.
Re: Launch control
Posted: Fri Apr 09, 2010 5:05 pm
by Mads B (dk)
looks very nice.... now we just need something for the ca18det engine
Re: Launch control
Posted: Sun Apr 11, 2010 11:13 am
by Matt
^ As stu said this was for src and skyline_stu to get the launch control working for existing (B13 SR20DE, S13 KA24DE and S13 SR20DET) launch control firmware changes out there at the moment
These should be able to be easily ported to other platforms (given time). I'm working on getting our newer USB Base image programmer in the meantime
Re: Launch control
Posted: Sun Apr 11, 2010 11:22 am
by Preston
Who do we need to send boards to to get them flashed for this? I have a 93 KA24DE so from what you said I'm able to get it currently? Thanks, this will be a useful feature if I can get it.
Re: Launch control
Posted: Sun Apr 11, 2010 6:33 pm
by skyline_stu
Preston,
What's your base image file ID? There are posts about the KA version somewhere in the forums - I think 91LC.BIN will be the file to search for.
Stu
Re: Launch control
Posted: Sun Apr 11, 2010 8:55 pm
by Matt
Myself or some of the distributors can do the reflash of the Type 3 board
Re: Launch control
Posted: Sun Apr 11, 2010 9:59 pm
by BlueRB240
Any in Southern California? I wouldn't mind launch control on my NX.
Re: Launch control
Posted: Tue Apr 13, 2010 6:47 pm
by all shal perrish
Matt wrote:Myself or some of the distributors can do the reflash of the Type 3 board
can andy from autovaughn ?
/ is it now workgin on ka ecus?
Re: Launch control
Posted: Wed Apr 14, 2010 5:37 am
by xylemer
Hi, this is Andy with AutoVaughn Performance. I will offer free re-flashes on any board Type, but we will not be responsible for shipping or any other problems that may result from this re-flash.
I currently do not have any ENT to program your board for the launch control. The user will have to supply this file.
I suggest giving me a call or email, to further discuss the details.
Andy
AutoVaughn Performance
(615) 796-6234
sales@autovaughnperformance.com
http://www.autovaughnperformance.com
Authorized NIStune Distributor and Installer
Re: Launch control
Posted: Wed Apr 14, 2010 9:44 am
by skyline_stu
Thanks for offering the service, but as I want to retain the software rights and keep control of where it ends up, so the ECU or Board needs to come here for updating. It's easier that way too, I can test it out on my test bench.
It's a little more involved than simply reprogramming the board, I've got to remove the users' mapping before reprogramming and then put it all back after the firmware change.
Sorry if this is an inconvienience to the users but that's how I've decided to ensure that it remains my interlectual property. There's been considerable time spent writing, testing, debuging the routines employed.
Stu