Function errors/warnings/messages

Compose model boundary conditions

 

Function ready condition: All '(R)equired' input data tables tested. In case input data table SUPPORT contains data it shall be tested and a tested input data table ELSPRS or TFSPRS shall be present as well, and vice versa.

 

Function error condition: 11 error conditions, 4 warning conditions, 2 messages

Errors:

E330/1:

Support name 'name' not found

The spring support reference name SUPREF specified in input data table SUPPORT has not been specified in table ELSPRS or TFSPRS.

table CONDI will become questioned with error indication at that support (STATE = [Error!], COSYS = UNDEFND)

E330/2:

Fixed boundary condition with support

At a boundary node a FIXED condition has been specified and to that node a spring support has been assigned as well.

output table CONDI will become QUESTIONED with at the related boundary node an error indication ENDCOND = [Error!]

E330/3:

More than one support per node

Spring support(s) (groups) have been specified in table SUPPORT such that overlap occurs.

output table CONDI will become questioned with error indication at that node(s) (STATE = [Error!]).

E330/4:

Name both in tables ELSPRS and TFSPRS

A support reference from table SUPPORT occurs in both ELSPRS and TFSPRS.

output table CONDI will become questioned with error indication at that node (STATE = [Error!], COSYS = DOUBLE).

E330/5:

Cond node with double condition

At a boundary node a condition has been specified both in table ENDPTS and CONNECT.

output table CONDI will become questioned with error indication at that node(s) (STATE = [Error!]).

E330/6:

Cond node with no condition

At a boundary node no end condition has been specified in table ENDPTS.

output table CONDI will become questioned with error indication at that node (ENDCOND = [Error!]).

E330/7:

No-cond node with condition

At a node NOT being a boundary node an end condition has been specified in table ENDPTS.

output table CONDI will become questioned with error indication at that node (STATE = [Error!]).

E330/8:

JOINTREF 'name' not in JOINTS/JNTSPRS

A joint reference from table PIPES does not occur in table JOINTS or table JNTSPRS.

output table CONDI has not been produced
output table J-SDATA will become questioned with error indication at the joint elements in question (JOINTREF = [Error!]).

E330/9:

MAXROT joint elem 'number' < inirot

The calculated initial rotation difference over a joint exceeds the maximum possible rotation MAXROT specified in table JOINTS.

output table J-SDATA will become questioned with error indication at the joint elements in question (ROTDIR = [Error!]).

 

E300/1:

No soil at infin boundary condition

At a boundary node an INFIN condition has been specified and at that node all soil parameters have a value = 0.

output table CONDI will become QUESTIONED with at the related boundary node an error indication ENDCOND = [Error!]

E300/2:

Unstable pipeline data model

At all boundary nodes a FREE end condition has been specified, and no external supports and no soil are present.

output table CONDI will become questioned.

Warnings:

W330/1:

Support without stiffness

In input table ELSPRS a spring has been specified with zero values for all stiffness components.

(In special cases this may result in an unstable pipeline model.)

W330/2:

Rotdir not parallel to kink plane

A pin hinge has been specified in a kink in the pipeline and the plane of rotation specified in table JOINTS is not the kink plane.

(The angle between the planes is over 5 degrees.)

W330/3:

SUPPORT 'number', max. angle 'value' deg

The vertical angle of the pipeline at the position of the support, defined in the local coordinate system, is greater than 20 degrees.

('Number' is the node number of the support, 'value' is the actual angle.)

W330/4:

Initial rotation in bellows joint > 1°.

Without any load applied, at least one bellows-type pipeline joint already has a kink angle of larger than 1 degree.

(Bellows connections are defined in table "Joint stiffnesses" [JNTSPRS]
Use column “Initial joint rotation” [IniRot] of table “Joint characteristics” [J-SDATA] to find the affected joint(s).)

W300/1:

Slack ignored at infin node

SLACK space has been specified at INFIN boundary nodes with SLACK values other than 0.

W300/2:

Slcurve ignored at infin node

SLCURVE has been specified at INFIN boundary node other than BILIN.

(All conditions at INFIN nodes must be linear, so the linear branche of the BILIN curve is applied at these nodes.)

Messages:

M330/1:

SUPPORT 'number', max. angle 'value' deg

The vertical angle of the pipeline at the position of the support, defined in the local coordinate system, is  between 5 and 20 degrees.

('Number' is the node number of the support, 'value' is the actual angle.)

M330/2:

Maximum rotation in joint(s) changed

The maximal rotation in a joint has a physical limitation defined by tan-1(('x-C' + 'x-T') / Diameter). When the user defined MaxRot in table JOINTS exceeds this limitation this message is reported. In result table J-SDATA the maximal allowable rotation is reported.

M300/1:

ELEM-L/ADV-L 'value', 'number' (number1 - number2)

An element length exceeds the recommended length.

(Value = maximal occurring element length quotient (>1). Number = element number with reported length quotient. Number1 - number2 = start, end of elem. series with quotient >1 The calculation accuracy at the recommended length is 3%.)

 


H3304, last changed: 14/09/2016

See also:

Design function description

Input data table overview

Output data table overview