Thread: b14 launch control

what's the deal with this tunercode?? never heard of it. You know your stuff though i'll give you that.

He was referring to a bin file that we've been working on for a while now. 520's, n62 maf, sr20det. I had to ask the subaru guys what the latency was on the injectors so that we could even get the tune in the ballpark. I've got one that works pretty good on my car, just need to finish the wideband up to get it tweaked right.

set up is listed below.

The ROM_LABEL is the last 5 characters of the 23710-xxxxx part number on the sticker on the ECU, but the xxxxx is also in the bin itself at address 0x8FF1 (offset 0x0FF1), so that's how I identify a bin. You can run different bins in different ECUs, but it's the bin, not the hardware (ECU) that determines the tune and how the engine runs. All of the ECU ID, part number, etc. info I know about are here: http://www.jimwolftechnology.com/wolfpdf/ECU-ID.PDF

Cheers,
Dave

TunerCode is the trade name I gave the custom ECU firmware development business I'm getting started. The TunerCode firmware is included with a Calum RTV2 board to support the additional I/O capabilities, but will also work with any daughter board. I'm currently working on the TunerCode documentation.

Cheers,
Dave

Do you mean if I use Calum bin for LC it will stay at the initial timing when I launch? What is that 15 degrees locked? As I said, I dont feel anything weird but havent logged a launch control session either.

ROM Label is 31 4D 38 36 31 (Shown as in TunerPro in HEX I think?)



By the way if any tuner here can take a look at that bin above, do you have any suggestion for latency? I have a feeling it should be more around 0.6ms, as 0.77ms is the stock latency of the GTi-R (444cc with SR20 MAF, but I have 444cc with Z32MAF).

The timing will stay at whatever its set to when the speed exceeds 10kph.



Yes, that is hex. Converted to ASCII its 1M861.

Your bin does not have any launch control code, but while looking at it I discovered a timer which renders my previous launch control instructions useless. I'll reiterate that in my next post.

Cheers,
Dave

While looking at gtswrx'x bin, I discovered a timer in the stationary rev limit code which renders this launch control method useless. I apologize for this oversight! There will be a functional and programmable launch control rev limiter in the first release of the TunerCode firmware for B14s.

Regards,
Dave

That's awesome news man! Do we need the Calum R/T2 for this though? and is TunerCode free like TP? And when do you expect to release it?

No, launch control doesn't need any extra I/O.




TunerCode firmware is included with an RTV2 purchase, but will be available separately for around $100. If purchased separately, you will receive a credit towards a Calum RTV2 purchase. There is a non-mandatory $30 registration fee for TunerProRT, and you really should do it. Mark has put in tons of hours and effort for us and TunerProRT is well worth it!




I'm working on the documentation as we speak (err,type) and hope to have it ready by the time TunerPro RT V5 is released. TunerCode uses features only available with TunerPro RT V5.

Cheers,
Dave

Cant fully understand what you are saying, but I dont rely in that Launch Control bin anyway, I use intuition.

However, when you release that code you are talking about, I would very likely try/use it! Especially if the launch control will include timing retard for some exhaust flame time!

Basically what I was saying was that if the timing is 15º when the car reaches 10kph, it will stay at 15º. If it's at 20º, it will stay at 20º. The timing won't be updated again until the speed drops below 10kph. Hope that helps.



I think "timing retard for some exhaust flame time" is called anti-lag, yes?

Dave