Jump to content
SAU Community

Recommended Posts

Hello,

I bought some ARP head studs (202-4207) for my RB26. However I am a bit confused as I am not sure which torquing procedure I shall follow best.

The Nissan torquing procedure for head studs is:

1. Tigthen to 29NM
2. Tigthen to 108NM
3. Loosen to 0 NM
4. Tighten to 25-34 NM
5. Tigthen to 103-113NM

However the ARP manual states:

Following the manufacturers recommended torque sequence tighten the nuts in three equal steps to 105 ft lbs / 142 NM
with ARP ULTRA-TORQUE FASTENER ASSEMBLY LUBRICANT.

So should I use the Nissan torquing procedure but torque to 142NM instead of 103-113NM in step 5 or should I follow the ARP procedure (three equal steps to 142NM)?

Don't tell me to ask ARP regarding this case as I wrote them already two messages (one 10 days ago, another one 5 days ago) and no one bothered to reply to me.

So their customer service doesn't seem to know the solution.

Thanks!

If the engine was built from scratch, as in torque plate bored/honed with the studs at their ideal torque etc etc then I would use the arp tensions as they make the stud and know what torque is required to achieve proper stretch plus the machining was done to suit that tension.

However, if you are just putting some studs in your standard engine to replace the bolts for whatever reason then I would go no more then the standard torque. The problem you might have is the bores will be stressed in a different manner now and they will most likely go out of round (even if only slightly) with more torque pulling the head down harder.

I used ARP specs but I admit, my bore is floating so doesn't suffer from the 'out of round' associated with solid blocks. Clamp the sucker down tight was my motto, 96nm ftw. :)

I followed ARP specs on 2 motors I have used them on, but did tighten then slack off process for OEM gasket. No torque plate hone on either motor, one with MLS HG other with OEM crush type. Both motors since faultless.

I prefer the ARP method as the OEM method is intended for two things: to crush the gasket and then torque, and to allow bolts to stretch. The ARP studs stretch far less and are reusable, so the torque settings are not relevant and 3 steps is better for even torque when not expecting bolts to stretch. If you are using an MLS gasket the tighten then slack off process is also redundant as you don't need to crush the gasket before going for final torque.

In the case of using an OEM gasket go to 30/65/100nm, then loosen off and go 3 increments of 47nm. I wouldn't be afraid to go 3 increments of 50nm (50/100/150) to allow for tool slack.

If using an MLS probably stick to 4 increments of 47nm if you have good tools.

it's not just to crush the gasket the multi stage. It is to also seat the head of the bolt onto the surface below it, in order to get a more accurate torque reading. Can't remember the exact link, but it was from an unbrako catalogue (they make high tensile bolts)

How do you figure the ARP's stretch less?

I would follow the ARP method as closely as possible including lube type etc. The relationship between pre-tension and torque is obviously very sensitive to friction but also things like tightening speed etc.

I will be using a Metal Head Gasket. I removed the head to seat the valves, the block will stay untouched. GtScotT, you mean three and not four increments of 47NM (3*47NM=142NM)?

Still there doesn't seem to be a consensus here regarding this matter...

is the hread pitch on either end of the stud different, if so(i think they are)torquingto nissan specs with lubricant will increase the headgasket crush by about 50%

The final torque recommended by Nissan is lower than the one by ARP. So how come that the head gasket will be crushed more?


What he is getting at (I think) is you need to think of clamping force and torque differently. a finer pitch thread will produce more clamp force at tge same torque setting as a coarser thread. just like if you dont lube up the bolt, it will lose alot to friction and produce far less clamping force.

How do you figure the ARP's stretch less?

I'm just putting things into simple terms. The ARP's are not torque to yield like the stock bolts are, so the easiest way for me to have described WHY they take more torque to the OP was to say that they stretch less. While that may or may not be entirely accurate it is a reasonable way of thinking of it. ARP themselves describe stretch yield to be 5 thou as a rule of thumb, so if considering that as a base the ARPs must stretch less at a given torque, to take more torque than the stock torque to yield bolts and not exceed 5 thou.

Clearly I am not taking the metalurgy of the bolt or its elasticity into consideration as it is hardly important in answering OPs concerns.. The point is that the specs for torquing them are higher than stock and OP should not be concerned.

I will be using a Metal Head Gasket. I removed the head to seat the valves, the block will stay untouched. GtScotT, you mean three and not four increments of 47NM (3*47NM=142NM)?

Still there doesn't seem to be a consensus here regarding this matter...

Yes I do mean 3 increments of 47nm. So in the case of using a MLS HG I would sit the head onto the block and use the factory torque down order, 47, then 94, then 142nm. Double check the last increment and make sure you are pulling the tool towards you, slow. Do not push the tool away when torquing. Steady your body and use the motor and your strong arm to pull towards.

I'm just putting things into simple terms. The ARP's are not torque to yield like the stock bolts are, so the easiest way for me to have described WHY they take more torque to the OP was to say that they stretch less. While that may or may not be entirely accurate it is a reasonable way of thinking of it. ARP themselves describe stretch yield to be 5 thou as a rule of thumb, so if considering that as a base the ARPs must stretch less at a given torque, to take more torque than the stock torque to yield bolts and not exceed 5 thou.

Clearly I am not taking the metalurgy of the bolt or its elasticity into consideration as it is hardly important in answering OPs concerns.. The point is that the specs for torquing them are higher than stock and OP should not be concerned.

Your comments about stretch to yield are very misleading. Broadly speaking the point of using higher grade fasteners is to increase pre-load. ARP are a very high grade fastener (up to 1500MPa UTS) so to hit the higher pre-load the torque is higher. Two bolts of differing grade will stretch the same amount for a given pre-load (assuming equivalent geometry), it's just that the higher grade fastener is capable of a higher pre-tension before you exceed the proof stress. A rule of thumb for stretch ignores the biggest factors driving elongation which are 1) length and 2) pre-load/stress.

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...