Jump to content
SAU Community

Recommended Posts

I'm also interested in this.

I might even get a copy of the nistune software and have a look at what features the nistune gives the R34 ECU that are tunable.

oh, and I'm a tuner mate - and I only deal with good shit. Sick of tuners only pushing haltech or some crap because that is all they know. I've seen fools cut a Ford XR6T factory ECU out and "wire in" a haltech because they had no idea how to edit a factory ECU, and we all know the XR6T ECU is by far the best ECU for it.

Its what is the most functional for the user \ car owner.

AFAIK you can't NIStune a 33 or 34 GTR ECU.

Type 2 boards cover the following earlier consult vehicles:

M30 Infiniti (VG30DE)

ECR32 Skyline (RB25DE)

ECR33 Skyline (RB25DET)*1

HCR32 Skyline (RB20DET)

BNR32 Skyline (RB26DETT)*2*3

Q45 Infiniti (VH45DE)*4

U12 Bluebird (KA24E)

Y60 Patrol (TB42E)

Z32 Fairlady 300ZX (VG30DETT)

*1 ECR33 RB25DET Skyline can use HCR32DET ECU (no VCT) or Z32 VG30DETT ECU (internal modifications required)

*2 BNCR33 Skyline requires BNR32 RB26DETT ECU and O2 sensors

*3 BNCR34 Skyline requires BNR32 RB26DETT ECU, O2 sensors and CAS wiring modifications

*4 Q45 VH45DE (1990-1992) using removed high gear maps

So everything a 32R NIStune can do.

hhhmm.

I wonder if they are much different software wise, other than the R34 ECU being modified to take to the newer o2 sensors and the CAS wiring.

I definitely wouldn't want to hack up a R34 GTR wiring loom, so I would buy a second hand R32 GTR ecu and internally mod it for the CAS. Its not hard, I made a R32 GTR powerFC work fine in a R32 GTS-T.

You do have to run the r32 GTR ecu but it seems that it plugs straight in and the only mods being the CAS and o2 sensors.

The pins in the 34 cas plug only need swapping around to make it run with the 32 ecu.

As for the o2 sensors, read the attached. Im assuming the 33 o2 sensors would be the same as the 34's.

R32 GTR ECU on R33 GTR.pdf

NIStuning a 33GTR is the same as 34GTR except 34GTR needs the CAS wiring changes.

As for the MFD, I guess it would be a matter of figuring out what signals it needs from the ECU and ensuring it continued to get those signals (pinout for each ECU and one for the MFD and some head/nut scratching) at the correct voltages etc.

  • 2 weeks later...

If plugging in a BNR32 ECU into a BNR34 do we just need to swap over the 1 degree and 60 degree CAS wires to use this particular ECU? Is that all is required in addition to internally modifying the ECU. If so this is good and I just need to update my documentation to suit for people that want to use Nistune on a BNR34

When I meant about Nissan swapping the CAS lines over between models for example S15 ADM and S15 JDM have their CAS wires swapped over on the same two pins. This may be because of having NATS in ADM model

Hmm interesting..

I was just working off your documentation Matt, I haven't done a 34GTR yet.

Pretty much all the NIStune installs I have done are Type-4 boards in either 34GTT's or s2 Stageas.

Type-2 board is in my 32gtst's ECU and I will be kicking that in the guts next week.

  • 2 years later...

So are there any firm instructions on how to get the BNR32 ECU to work in a BNR34? Ie, all wiring mods needed?

I have one here ready to be nistuned but don't know for sure what needs to be done. I have only seen instructions for the BNR33.

  • 6 months later...
okay, all done. I have a nistuned R32GTR ECU running my R34 GTR. I have spoken to Matt from Nistune for some help and regarding what was needed to be done. The car runs absolutely perfect with the R32 GTR ECU.


Compared to the powerfc:


- Starts faster

- comes to idle so much quicker

- idle is heaps more stable

- car just generally runs better


After tuning the rest of the map, it runs really well.


Regarding how I did it, It is a little more than just swapping cas wires -


Differences between wiring:


Pin 8 - Ignition switch (IGN) (R34) / Pin 45 - Not used (R34)

=> Wire pin 8 to Pin 45 (R32 ECU)


Pin 10/20 - Not used (R34)

=> Pin normally for Ignition GND (R32 ECU)

Wire 10/20 to pin 50/60 to provide the R32 ECU with an ignition ground reference. After this R32 ECU will work fine in R34 ECU after speaking to Jono today and getting it working


Pin 31 - Not used (R34)

=> Wire needed to be added for consult CLK signal (R32 ECU)


Pin 41 - Camshaft position 1 deg POS (R34) / Pin 51 not used (R34)

=> Swap to 42/52 on CAS 1 deg POS (R32 ECU)


Pin 42/52 - Camshaft position 120 deg REF (R34)

=> Swap to 41/51 on CAS 120 deg REF (R32 ECU)


Pin 54 - IMMU/NATS (R34) - Don't worry about this

=> Not used (R32 ECU)


Pin 115. Heated O2 sensor control signal

=> This pin not used (R32 ECU) so wire to be connected to pin 50 (control unit ground) on R32 ECU

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • @Haggerty this is your red flag. In MAP based ECU's the Manifold pressure X RPM calculation is how the engine knows it is actually...running/going through ANY load. You are confusing the term 'base map' with your base VE/Fuel table. When most people say 'base map' they mean the stock entire tune shipped with the ECU, hopefully aimed at a specific car/setup to use as a base for beginning to tune your specific car. Haltech has a lot of documentation (or at least they used to, I expect it to be better now). Read it voraciously.
    • I saw you mention this earlier and it raised a red flag, but I couldn't believe it was real. Yes, the vacuum signal should vary. It is the one and only load signal from the engine to the ECU, and it MUST vary. It is either not connected or is badly f**ked up in some way.
    • @Haggerty you still haven't answered my question.  Many things you are saying do not make sense for someone who can tune, yet I would not expect someone who cannot tune to be playing with the things in the ECU that you are.  This process would be a lot quicker to figure out if we can remove user error from the equation. 
    • If as it's stalling, the fuel pressure rises, it's saying there's less vacuum in the intake manifold. This is pretty typical of an engine that is slowing down.   While typically is agree it sounds fuel related, it really sounds fuel/air mixture related. Since the whole system has been refurbished, including injectors, pump, etc, it's likely we've altered how well the system is delivering fuel. If someone before you has messed with the IACV because it needed fiddling with as the fuel system was dieing out, we need to readjust it back. Getting things back to factory spec everywhere, is what's going to help the entire system. So if it idles at 400rpm with no IACV, that needs raising. Getting factory air flow back to normal will help us get everything back in spec, and likely help chase down any other issues. Back on IACV, if the base idle (no IACV plugged in) is too far out, it's a lot harder for the ECU to control idle. The IACV duty cycle causes non linear variations in reality. When I've tuned the idle valves in the past, you need to keep it in a relatively narrow window on aftermarket ecus to stop them doing wild dances. It also means if your base idle is too low, the valve needs to open too much, and then the smallest % change ends up being a huge variation.
    • I guess one thing that might be wrong is the manifold pressure.  It is a constant -5.9 and never moves even under 100% throttle and load.  I would expect it to atleast go to 0 correct?  It's doing this with the OEM MAP as well as the ECU vacuum sensor. When trying to tune the base map under load the crosshairs only climb vertically with RPM, but always in the -5.9 column.
×
×
  • Create New...