Jump to content
SAU Community

Recommended Posts

Hi Folks,

Over the weekend, Dad and I did the 100K service on my R33 GTR. This entailed replacing the water pump (with a N1 pump), the seals on the cams, the idler and tensioner bearings and timing belt.(We didn't do the crank seal as I have an upgraded oil pump to put on before long.) The work went well, with much patience and the engine manual at hand.

The car started up well and sounds just right...for about 2 minutes, then a what I can only describe as a whiring sound starts and continues. We have really only let the car idle until we are completely happy with all our work. Other than this sound, the car is running well. This behaviour is also repeatable. When we stop the car and restart it, it runs well for about another 2 minutes and then the whiring sound starts up again.

We haven't taken the cam and timing belt covers off yet, which is our next step this coming weekend. We had a little peek in the top of the cam cover and at first glance the timing belt looks okay(just a that spot, we didn't spin it round).

We used nissan OEM parts for the idler, tensioner, cam seals and water pump and the timing belt is a gates racing belt.

What I'm wondering is if anyone can offer any advice as to what might be causing this. My personal ideas are either the tension on the timing belt is not right, or that either the tensioner or idler bearing is not good. Can anyone offer any advice as to what this might be, or alternatively what it is not?

Thanks in advance,

murray

The gates racing belts are pretty well known to be louder then the standard/some other timing belts. I have a Dayco timing belt and it hasnt made a noise since I put it in, but i know alot of people with the gates belts experience the whirring noise

I dont think its a serious issue, just a bit of noise, and after the belt wears in a bit it goes away

From what I know about it anyway, its fairly well documented on this site, just search timing belt noise or gates timing belt, something along those lines

Thanks to everybody for their advice - I really appreciate it.

After hearing your responses, Dad and I took the front covers off again and went through the tensioning procedure again and gave the new tensioner and idler an inspection. Everything looked good. With it all in place I gave the crank several rotations, watching the timing belt for lateral travel or anything unusual. Everything looked good so we put it all back together and started the car up. This time the noise was much less. Again it seemed to 'start up' after a minute or two after starting the engine, but the noise was nothing like as loud - it was down to a similar volume as many other regular sounds in the engine area, if it a little less. So considering the advice and experiences of everybody we just kept it idling for a while and then decided to go for a drive as the noise sounded just so much less of problem than after our initial turn on. The volume of the noise when I started this post/topic was really much louder than anything else in the engine area and sounded as something was pretty wrong. Now you would almost just say, that the noise is just how the engine sounds.

Thanks again

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

    • 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. 
    • Holy hell! That is absolutely stunning! Great work!!!
×
×
  • Create New...