Function errors/warnings/messages
Contents
Degr.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: 14 error conditions, 5 warning conditions, 1 informational message, 1 message
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)
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!]
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!]).
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).
Boundary condition node with double condition.
At a boundary node a condition has been specified both in table ENDPTS and either CONNECT or SISPRC.
If a node is restricted by either a connection or a SIS roller, it's condition is no longer undefined and it may not be mentioned in ENDPTS.
•output table CONDI will become questioned with error indication at that node(s) (STATE = [Error!]).
At a node not being a boundary node an end condition has been specified..
The end condition has been specified in table ENDPTS.
•output table CONDI will become questioned with error indication at that node (ENDCOND = [Error!]).
A not boundary node has been specified a 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!]).
Jount reference 'name' not found in table JOINTS nor in 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!]).
The initial rotation of the joint in element 'number' exceeds the maximum rotation.
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!]).
No soil at infin boundary condition.
At a boundary node an INFIN condition (Infinite in input data table ENDPTS) 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 STATE = [Error!]
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.
Joint reference 'name' in both tables JOINTS and JNTSPRS
A joint reference from table PIPES occurs in both JOINTS and JNTSPRS.
A joint is either displacement related or stiffness related.
Both tables JOINTS and JNTSPRS are empty, but joints are defined in table PIPES.
In table PIPES joints are defined but both tables JOINTS and JNTSPRS are empty.
A joint defined in table PIPES (DF2: Pipeline configuration) should be specified in either table JOINTS or JNTSPRS.
Both tables ELSPRS and TFSPRS are empty, but supports are defined in table SUPPORT.
In table SUPPORT supports are defined but both tables ELSPRS and TFSPRS are empty.
A support defined in table SUPPORT (DF2: Pipeline configuration) should be specified in either table ELSPRS or TFSPRS.
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.)
Rotation direction is 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.)
Pipeline vertical angle at support in node 'number' is 'value' º.
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.)
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).)
SLACK or SLCURVE ignored at infin node.
SLACK space has been specified at INFIN boundary nodes (Infinite in input data table ENDPTS) with SLACK values other than 0.
OR
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.)
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.
Element length > recommended length for elements 'element1' - 'element2', worst case factor is 'value' at element nr. 'element3'.
The length of at least one element exceeds the recommended length for elements, the series runs from 'element1' up to 'element2', with the highest factor observed at 'element3' being 'value'.
Also see "Recommended element length" in table POLYDIF.
Pipeline vertical angle at support in node 'number' is 'value' º.
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.)
H3304 (last modified: Aug 24, 2025)
See also: