Jump to content
SAU Community

Recommended Posts

hey guys

just a question if i replace my rb20 redtop with a rb20 silvertop or even might be thinking of a rb25 (engine, gear box, ecu & loom) will i have to get the engine tuned to suit my hr31 passage if it comes straight out of a running r32? or will it still run fine?

also are there any mods i should know about to do the conversion?

cheers for the help guys

tune on the stock ecu will be fine. tis a bit rich but its fine.

its fairly straight forward. trickiest part is usually the wiring, but theres only a few wires. theres a guide on www.r31skylineclub.com somewhere

I would be using the loom and ecu from which ever motor goes into the car... and at the moment there is an RB25 from an R32 being sold by Phantom32 or something like that for 1500, and a mate paid 1200 for a silvertop recently... which is better value :)

tune on the stock ecu will be fine. tis a bit rich but its fine.

its fairly straight forward. trickiest part is usually the wiring, but theres only a few wires. theres a guide on www.r31skylineclub.com somewhere

can i reuse my original loom thats in the car already? for either a rb20 or rb25??? or are they both different?

cheers

use the loom to match the motor. when you buy an engine package the loom should still be all hooked up, drop it in the car like that and feed the loom through the passenger side guard area into the passenger footwell.

  • 2 weeks later...

Removing the loom is easy. Take the passenger side kick panel off, disconnect the ECU and take out the ECCS/Ignition relays.

Then you can feed the loom back out through the firewall and into the gaurd, then pull it through into the engine bay and remove. Silvertop loom is just the opposite, connect it all up to the engine then feed the ECU connector and relays into the gaurd first, then into the car.

The wiring is straight forward, check out the guide on r31 forums or PM me as I have done a couple before.

Removing the loom is easy. Take the passenger side kick panel off, disconnect the ECU and take out the ECCS/Ignition relays.

Then you can feed the loom back out through the firewall and into the gaurd, then pull it through into the engine bay and remove. Silvertop loom is just the opposite, connect it all up to the engine then feed the ECU connector and relays into the gaurd first, then into the car.

The wiring is straight forward, check out the guide on r31 forums or PM me as I have done a couple before.

ok thanx heaps mate

i take that as the looms are different from the redtop to silvertop?

will pm you if i get stuck thanx heaps

Yes the looms will be different, sensor types/locations vary. The major difference is between NICS and ECCS motors, but there are even differences between redtop ECCS and silvertop ECCS.

Good luck PM me if you get stuck.

  • 4 months later...

Hi everyone. I have just bought a hr31 and wanting to convert to silver top turbo. Just wondering if you have to change all wiring to the dash and a/c or is there just a connector from engine bay to interior wiring so its just the engine bay wiring and ECU that has to be changed? Thanks guys. Sorry this might sound stupid as you have already told how to do it but it just sounds way too easy lol.

Edited by sr_esky

theres a plug down in the passenger footwell where the engine loom joins the body loom. obviously different from 31 to 32 so you need to hardwire a few wires (tacho, temp gauge etc). theres a guide on www.r31skylineclub.com

theres a plug down in the passenger footwell where the engine loom joins the body loom. obviously different from 31 to 32 so you need to hardwire a few wires (tacho, temp gauge etc). theres a guide on www.r31skylineclub.com

or there is a guy named kev in r31skylineclub that mods the loom to suit your cars needs plug & play...

not sure on his user name tho.....

Cool, thanks guys. Have been looking at that site and they have manuals for rb30 r31's. Not to be a pain in the a hole but is the body wiring in the gtsx the same as the body wiring in a standard r31 4 door with rb30? Just different engine wiring from that plug?

Cool, thanks guys. Have been looking at that site and they have manuals for rb30 r31's. Not to be a pain in the a hole but is the body wiring in the gtsx the same as the body wiring in a standard r31 4 door with rb30? Just different engine wiring from that plug?

give kev a call mate tell him what you want done & he will do it pretty cheap to :blink: his number is 0738144674

import is different but still the same procedure. the small brown plug down near the ecu is the body plug on the hr31 side, all the wires you need to wire up are in that plug

Thanks for that. Just wondering where kev is situated? Im in perth so if he is anywhere else then it might be a bit hard or does he supply pre-made looms or diagrams?

he is in brisbane but you could send your loom to him & he can make it you just need to send him a pic of the plug inside the car, just call him & work something out with him mate....

to do that you'd have to figure out which wires are which for him to make a plug, thats the hardest bit of doing it anyway. once you've figured that out you just solder them together and away you go. theres no diagrams or pinouts for the hr31 side of the loom anywhere on the net, you have to figure it out yourself or find someone whos done it before who can be bothered checking for you

to do that you'd have to figure out which wires are which for him to make a plug, thats the hardest bit of doing it anyway. once you've figured that out you just solder them together and away you go. theres no diagrams or pinouts for the hr31 side of the loom anywhere on the net, you have to figure it out yourself or find someone whos done it before who can be bothered checking for you

as i said kev makes the loom so its plug & play

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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • 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. 
×
×
  • Create New...