Jump to content
SAU Community

Recommended Posts

Hey guys

So basically i have put a RB25DET NEO into a R32 GTST
Everything mechanical is done.

I have used the RB25det NEO Loom and ECU

I basically need a guide/help on wiring the Rb25det Neo engine loom to the R32 gtst body loom and to basically get this thing started and running.

Now i have searched everywhere for days found little bits and pieces like this :

The internal wiring is the only hard part. You need to place the wires from the 34 loom into the factory 32 internal loom. This is easy if you know what every wire from the 32 and 34 ecu’s is and what thus each wire in each plug in the 32 and 34 kick panel is. It is easiest (in my opinion) to cut the internal loom plugs off the 34 loom and off the 32 loom where it went onto the main ecu loom, and attach the 32 plugs onto the 34 ecu loom. This way, if you crash your 32 or whatever and want to put the neo into a new 32 all your wiring is done basically. If you do it the other way, you will also need all the corresponding 34 internal plugs from the internal loom. I say do it the first way. It’s your choice.
The only point to really note and emphasise here is this:
The r32 is basic. The 34 had TCS and ABS. Each system in the 34 has it’s own computer ie for the
1. Engine
2. TCS
3. ABS
Each computer works both independently, receiving the signals it needs to and consequently processing them, and together. They all talk to each other. If you remove the ABS computer (or in the 32’s case, it was never there to start with) the engine computer does not see a signal from the ABS computer, so it thinks the car has no brakes. And it won’t go. So you need to trick the ECU into thinking that the TCS and ABS computers are their, functioning properly, and sending a signal so the ecu thinks you have never locked up braking or lost traction whilst driving. The information on how to do this, along with spreadsheets of what every wire in the 32 and 34 kick panels is, the plug layouts, ecu pinouts etc is all available via application in writing

Now it says what to do but not how TO DO IT ?!?!

does anyone have a guide or write up for this?

OR know how to do it

Thanks kindly

Ryan

It's pretty easy. I'll see if I have some pics from when I did mine. There is really not much that needs to be done.

Power and earth come from engine bay. Fuel pump, tacho and some other stuff go into the body loom in passenger footwell.

There is a dedicated guide here in the how to section by the way. Search and Ye shall find.

You will need to Nistune the ECU to get rid of the fault codes and CEL. ABS and TCS are the big problem. Nistune fixes all.

The only way to do a neat job of it is to use the complete R34 loom and add the body connections from R32 into it, rather than the sort of horrible hack and tack approach that has been documented elsewhere.

I wish could give you a nice summary on how to do it, but I sensibly left that part in the hands of people who knew exactly what to do and had the bits to do it with before the swap commenced.

Hmmm okay looks like ill get a nistune after i get it started and see how that goes.

but yeah im wanting to cut the plugs off the R32 gtst loom and use them on the NEO loom, if you do find any information on how to do it please lemme know.

and Josh, did you find any photos ????

thanks

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

    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
×
×
  • Create New...