rb25det tuning in 240sx

[turbotankshane]

Hello all, I'm new to the site but not entirely new to RB's, I've had a customer at my shop who had two r32 GT-R's with rb26dett and a GTS-T with an rb20, we installed a ecumasters EMU on his rb26 with upgraded r34 twins, tuned in on e85 and made me fall in love with the sounds of these engines.

Fast forward to now, I've traded for a 91 240sx with an rb25det swap. I did all the basic maintenance, cleaned up some of the wiring and am now looking to turn it up a bit. My previous customer had left me his original rb26dett ecu, and my s13 had a nistune type 2 board in the glove box when I got it. I also already have an ostrich emulator and burn2 chip programmer from moates.net. I've installed the socket in the ecu, but I would love some input on the best route to proceed. I've got a vci with an adapter for the nissan consult port, but to my knowledge no consult port was added to the vehicle with the swap, while if i am correct I should be able to just plug my ostrich in and load the nistune suite and get to work. 

Advice? 

[Dose Pipe Sutututu]

I would get a new Nistune board and install a consult port direct onto the ECU connector.

No need to burn chips and use emulators, not to mention you could implement full flex support and hook up a launch control switch as well.

[GTSBoy]

I think it's not super easy to use the RB26 ECU on a 20/25.  Whilst the 20 and 26 ECU are super similar, the fact that the 26 expects to see 2x AFMs and 2x O2 sensors and shit like that makes extra challenges that you don't need.  The effort required to use it would be better spent elsewhere.  Definitely worth checking the Nistune forum (or hopefully Dose knows off the top of his head) what the state of play is with that.

I'm assuming the RB25 is running the original 25 ECU? So you can't use the Nistune board in that.  You'd need an RB20 ECU to go forward, and as Dose said, you'd still be better off buying a new Nistune board, with the right program in it.  Using the S13 one would require it to be redone anyway.

You will probably find it easiest and best (although not necessarily the cheapest) to use a Haltech or other similar plug-in ECU rather than having to mess about with all sorts of additional needs to get Nistune working.

[Dose Pipe Sutututu]

I just re-read that after failing at skim reading LOL...

You're better off with a RB20DET ECU as it supports VCT, yes that's right RB20DET can control VCT on your RB25DET motor.

If you're hell bent on using the RB26 ECU on a RB25 that also can be done, however you lose the VCT capability. All you do is wire both AFM signals together so 1x AFM feeds both inputs, however best to check with Matt at Nistune if that's still required for the later/latest firmware for Nistune.

[turbotankshane]

Thanks for the replies. I may have been confusing in my choice of words. The nistune board I have is the correct type 2 board for my application. I know I cant use the rb25 ecu, but in the meantime I tried out my previous customers ancient HKS Pfc f-con piggyback from his rb26 setup, and it plugs into and runs with the rb26 ecu perfectly fine. 

According to what I've found so far,  the rb26 ecu can be used successfully by bridging the maf and o2 inputs. As far as the VTC is concerned, any r32 ecu with part number 23710-04uxx or 11uxx and provisions on the board for the green diagnostic LED output can be used for vtc control, and the ecu I have fits the bill. 

I guess my biggest question is why I shouldn't use the ostrich 2.0 I've already got since its supported by nistune. 

Edited March 7, 2019 by turbotankshane

[GTSBoy]

Having come from an S13, your Type 2 board is currently setup to run a CA18 or SR20 (or, given that you say 240SX, the truck motor that was in that).  It won't run an RB25 without having the correct programming dumped onto it.  Not just the maps, the entire ECU program (from an RB20, ideally, or even the RB26, conceivably).

There is no reason to use emulators &/or burners when you actually have Nistune......

Edited March 7, 2019 by GTSBoy

[turbotankshane]

If a consult cable is $100 and the software is $200 for a license that's enough reason for me to roll with what I've got just to do some basic adjustments, hell I'm sure with a little time making an xdf I could use tunerpro rt and a modified rb26 bin to do what I needed to. It's a stock motor and turbo, I'm just looking to up the boost a little. I have absolutely no reason to put a Haltech in this car at this point in time. 

I'll get in touch with Nistune and see what I can come up with though. 

[turbotankshane]

I think you're still misunderstanding. The type 2 board isn't for a ca/sr/ka ecu at all whatsoever. The board I have came with the car because the previous owner had purchased it specifically for an rb ecu, so it IS the correct board for an rb ecu. I'm looking on their website right now and for this bnr32 rb26dett ecu or even if I were to get any rb20det ecu, the type 2 board is still the correct board. 

There is a single stanza ecu for a ka that takes a type 2 board, but otherwise for a ca/sr/ka you're looking at a type 1 or type 3 board. 

Even if the previous owner had told nistune the wrong vehicle or ecu or something like that when he ordered it, I've got a base image programmer that I could put the correct base rom on the board with. 

Edited March 7, 2019 by turbotankshane

[GTSBoy]

In that case, go your hardest.

[turbotankshane]

After all that research, turns out my 23710-04U01 is indeed an rb20det GTs-T ecu. Guess that makes things just a touch easier.

[GTSBoy]