D12.B.6 Tubular Joint Checking

The design of tubular joints for this implementation shall be based on section 6.4 of N-004 and will be applicable to joints formed from a connection of two or more members.

Typical Tubular Joint (Fig 6-1 in N004)

Prior to completing a joint design, the joint should be classified into one of the three categories given by the code. Joint classification is the process whereby a "brace" member connecting into a "chord" member is classified into one of these categories based on the axial force components in the brace. The classification normally considers all the members at a joint that lie in a plane. N-004 defines three joint classification categories: K, X, or Y (or a combination of these).

Joint Classification	Description
K	The axial force in the brace should be balanced by forces in the other braces in the same plane and on the same side of the joint. The code allows a 10% tolerance in the balancing force.
X	The axial force in the brace is reacted as a beam shear in the chord.
Y	The axial force in the brace is carried through the chord to braces in the opposite side.

Note: Typical examples of these joint types are given in Figure 6-3 of the N-004 code. It is worth noting that the joint class for each brace will be different for each load case.

Note: STAAD.Pro does not perform an automatic classification of the joints. This is left up to the engineer. All joints will initially be classified as Y in the generation of the external geometry file. Joints should be re-classified as necessary before performing the final joint capacity checks.

The checks for joint capacity are given in Cl. 6.4.3.2 to 6.4.3.6 and STAAD.Pro performs the checks as per these clauses. However, the program does not deal with conical joint transitions and joints with joint cans. The code also specifies checks and limits for the gaps and eccentricity of joints. This implementation will not perform such geometry checks.

The details of the checks done and the methodology will be discussed in the following sections.

Joint checks are performed as part of the CODE CHECK command and are displayed when either a TRACK 0 or TRACK 3 output design parameter is specified (with the former giving a summary and the latter giving detailed member & joint check results). Refer to D12.B.9 Examples for example input and output including joint checks.

D12.B.6.1 Identification and Classification of CHORD and BRACE Members

This is a two step process where the program automatically identifies the CHORD and BRACE members at a joint and perform a default joint check. The input variables used for the initial joint checks will be generated in an external text file. You can then use this text file to edit or modify the input variables and perform a final check as necessary.

When a member is included in the CHECK CODE list, the program designs the member and also then proceeds to perform the joint checks at either ends of the member. It finds all members that connect to the end nodes of the member being designed and then proceeds to calculate the joint capacities based on each such connected member. The design process follows the section 6.4.3 of the code. This sections specifies certain pre-requisites for its application. If these pre-requisites are not satisfied, then the joint checks will not be performed. The following geometry checks must be satisfied in order for the joint check to be performed:

0.2 ≤ β ≤ 1.0
10 ≤ ɣ ≤ 50
30° ≤ θ ≤ 90°
g / D ≥ -0.6 (for K joints)

where

D / 2T, where D = chord diameter and T = chord thickness.

The program will also produce an output file called filename_Jnt.txt, where "filename" will be the name of the .std input file. This format of this text file is explained in D12.B.8 External Geometry File.

You can then edit this text file to set up the necessary design parameters. Once the program finds of the _JOINTS.txt file, it will read in the necessary parameters from this file and perform the subsequent design checks. This is done by simply performing the design and analysis again for the input file.

Note: This file will be produced only once (i.e., when this file does not exist). If this file exists, it is assumed that you have already done a joint design check and hence the program reads the values from this file and uses these for joint checks.