Maximum Unsupported Span Table
- Last UpdatedFeb 11, 2025
- 2 minute read
Some users base maximum unsupported spans for pipes on ‘Span Tables’. The Hangers & Supports application provides a method whereby these tables can be entered into a data table and the maximum spans can be graphically indicated in the 3D model by partially highlighting the supported branches.
The Purpose (PURP) attribute of the Span Table Specification (SPEC) should be set to HSPT, the :VISI set to false, and the DESC attribute may have an optional description text.
The hierarchy for this data table is variable, depending on the number of parameters which you wish to cross-reference, but the format is as follows:
|
At Selection (SELE)/ Specification (SPCO) Owner |
||
|
TDEF |
<expression> |
|
|
This expression can be anything which yields a single numeric or text value based on the current HANGER. It is recommended that the supplied user function SELEATT be used, as this will return the value of any attribute or any pseudo-attribute of any part of the hanger or related support or pipe. For example: USRFUNC (SELEATT ATTA LBOR) returns the leave bore of the ATTA. USRFUNC (SELEATT ATTA lt;part (RTEX of DETREF of LSTU , 2)gt;) returns the schedule of the attached pipe (for the standard AVEVA pipe specs).USRFUNC (SELEATT BRAN TEMP) returns the temperature rating of the attached branch. |
||
|
Refer to the internal macro documentation of SELEATT for further information. |
||
|
At SELE/SPCO |
||
|
TANS |
<test> |
|
|
This test is used for the data returned by the owner's TDEF expression to yield a logical true or false. |
||
|
Suitable tests might be (for the above examples): eq 20 eq 'SCH80' (notice the use of quotes '...' and not vertical bars |...| ) lt 177 |
||
|
Tests are performed in list order, so if multiple matches are possible, the first is assumed. In this way, ranges can be defined (as with the temperature example above) by using lt or gt and putting the test values in increasing or decreasing order as applicable. |
||
The actual span is stored in the Comment (COMM) attribute of the Specification (SPCO). The application will return an error value if matches cannot be made from the Span Table.