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

    • Shouldn't need a "base map" for anything other than guidance to ignition tuning. You just need the engine capacity right, the injector size right, and something, almost anything, for a VE map. On an NA engine, fuelling is almost completely a function of load signal & rpm. It should run and drive with a completely flat fuel map. It will be too lean under load, but that's easily fixed. We used to tune all ECUs without any base map. There were no such things (until someone had tuned a near stock engine on one, and then they had a "base map".
    • What did you actually buy/how much did it cost? When I got mine in like.. 2017...? 2019? the aim was to run Torque for gauges via ODB2 and things like Track Addict/Laptimers/Dashcam/Reversecam/Spotify etc. Mine never broke, but I wonder if you've got the same needs (it sounds like it). Cause I liked the idea of being able to do anything with it. That said, yours also cost 3x the cost of what I spent so... food for thought.  
    • For me there is a massive difference in manufacturer or big brand crippled android (Sony, Kenwood etc) vs the sort of thing I've installed here, which is basically just a tablet in DIN form factor with open Android, and the other model of course is mirroring - Android Auto/Carplay. I hate the locked down manufacturer and AA options where they decide what apps I'm allowed to install, including the Launcher but also importantly things like Ecutek (for this car) or Real Dash (Stagea) are not supported. Plus those crippled versions tend to be slower due to both overheads and lower spec hardware. On the other hand, when this breaks I'll likely be in trouble for support....but how is that different to owning an Infiniti anyway
    • Yeah, Duncan is helping sell me back to Android devices. I've hated the whole Android head units due to their speed issues. Even in my old Hyundai Kona (2022 model), it behind the scenes was Android, and slow and shitty to start up. Once running wasn't bad, but still a good 15 to 30 seconds.
    • My roof rails are off atm on the E39 until the rust is fixed. I did find another little bit of surface rust under the rails when I took them off. As @soviet_merlin said I'd just leave them alone unless you're planning on ensuring they're properly sealed. I was on the fence about leaving them off as the delete is still a thing in BMW E39's but I feel like the car is missing something (er, it is, der) with them off and I'm looking forward to putting them back on.
×
×
  • Create New...