5/24/2019 Data Consistency Check | PDMS Macro

PDMS Macro

PDMS LEARNING AND MACRO DOWNLOAD

Data Consistency Check

02 FEB
Design errors can be detected by doing consistency check. This is the list of errors for data consistency
check.

ERROR ERROR DESCRIPTION ERROR CAUSE ACTION

CODE BY
A10 HEAD REFERENCE NOT SET The Head reference should only be unset DESIGN
(i.e. null) if the Head Connection Type
HCONN is set to OPEN, VENT, CLOS
or DRAN.
A20 HEAD REFERENCE POINTS This error would result from the deletion DESIGN
TO NONEXISTENT of a component, such as a Nozzle, to
ELEMENT which the Head of the Branch was
originally connected
A30 BAD HEAD RETURN The Head is connected to an element DESIGN
REFERENCE that does not refer back to the Branch.
This can occur when the Head of a
Branch is connected to another Branch,
implying that a Tee should be placed
somewhere along the second Branch.
The error can also occur when two or
more branches are inadvertently
connected to the same terminal.
A100 HEAD TERMINAL Either the Head terminal has an unset ADMIN
PROBLEM WITH SPREF SPREF or the SPREF points to a non-
existent SPCOM.
A110 HEAD TERMINAL Either the Head terminal has an unset ADMIN
PROBLEM WITH CATREF CATREF or the CATREF points to a non-
existent Catalogue component.
A120 HEAD TERMINAL There is a Catalogue problem in ADMIN
PROBLEM IN ACCESSING P- accessing the p-points of the Head
POINTS terminal.
A130 HEAD TERMINAL A required p-point of the Head terminal ADMIN
PROBLEM, P-POINT NO.n does not exist in the set of p-points.
DOES NOT EXIST

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 1/8
5/24/2019 Data Consistency Check | PDMS Macro

A140 HEAD TERMINAL This is testing for flow with Branch to DESIGN
PROBLEM INVALID FLOW Branch connections. Branches have a
ATTRIBUTE ON FLOW a ribute which can be set to
CONNECTED BRANCH FORW or BACK or NUL. If FLOW is not
set correctly this results in an error
A150 HEAD TERMINAL The FORW flow means that the fluid in DESIGN
PROBLEM, TERMINAL the Branch goes from Head to Tail with
INCONSISTENT FLOW the reverse for BACK. The code then
ACROSS BRANCH checks that the fluid flows correctly from
CONNECTION one Branch to the next. To fix the
problem check the network to see that all
the flows are in the correct direction
A200 DIRECTION HDIR NOT If the Head is connected to a terminal, DESIGN
SAME AS TERMINAL such as a Nozzle or Tee, then the
DIRECTION direction HDIR should always be
identical to that of the appropriate p-
point of the terminal.
A210 POSITION HPOS NOT SAME If the Head is connected to a terminal, DESIGN
AS TERMINAL POSITION such as a Nozzle or Tee, then the
position HPOS should always be
identical to that of the appropriate p-
point of the terminal.
A220 HBORE NOT SAME AS If the Head is connected to a terminal, DESIGN
TERMINAL BORE such as a Nozzle or Tee, then the bore
HBORE should always be identical to
that of the appropriate p-point of the
terminal.
A230 CONNECTION TYPE If the Head is connected to a terminal, DESIGN
HCONN NOT SAME AS such as a Nozzle or Tee, then the
TERMINAL CONNECTION connection type HCONN should always
TYPE be identical to that of the appropriate p-
point of the terminal.
A300 REFERENCE HSTUBE There is more than 1mm of tube between ADMIN
UNSET the Head and the p-arrive of the first
Component (or the Tail), but HSTUBE is
unset.
A310 REFERENCE HSTUBE This may occur if part of the ADMIN
REFERS TO A Specification has been deleted.
NONEXISTENT SPCOM
A320 HSTUBE PROBLEM, CATREF This indicates an error in the ADMIN
IN SPCOM IS UNSET Specification.
A330 HSTUBE PROBLEM, CATREF This may occur if part of the Catalogue ADMIN
IN THE SPCOM REFERS TO has been deleted or if the CATREF is
NONEXISTENT Catalogue unset.
COMPONENT

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 2/8
5/24/2019 Data Consistency Check | PDMS Macro

A340 HSTUBE PROBLEM, GTYPE The component pointed to by HSTUBE ADMIN

OF CATALOGUE is not of type TUBE in the Catalogue.
COMPONENT IS NOT SET
TO TUBE
A350 HSTUBE PROBLEM IN There is a Catalogue problem in ADMIN
ACCESSING P-POINT accessing a p-point of the tube pointed
to by HSTUBE.
A400 HBORE NOT SAME AS BORE The bore of any tube leading from the ADMIN
OF HSTUBE Head, determined from the Catalogue,
should always be identical to HBORE
A410 HCONN NOT COMPATIBLE The connection type of any tube leading ADMIN
WITH CONNECTION TYPE from the Head, determined from the
OF HSTUBE Catalogue, should be compatible with
HCONN.
A420 ISPEC REFERENCE POINTS This error would occur if, for example, ADMIN
TO NONEXISTENT the Insulation Specification pointed to by
ELEMENT ISPEC had been deleted.
A430 INSULATION CANNOT BE There is no suitable insulation in the ADMIN
SELECTED USING HBORE Catalogue for the combination of
temperature TEMP and bore HBORE
B10 TAIL REFERENCE NOT SET The Tail reference should only be unset DESIGN
(i.e. zero) if the Tail connection type
TCONN is set to OPEN, VENT, CLOS or
DRAN.
B20 TAIL REFERENCE POINTS This error would result from the deletion DESIGN
TO NONEXISTENT of a component, such as a Nozzle, to
ELEMENT which the Tail of the Branch was
originally connected.
B30 BAD TAIL RETURN The Tail is connected to an element that DESIGN
REFERENCE does not refer back to the Branch. This
can occur when the Tail of a Branch is
connected to another Branch, implying
that a Tee should be placed somewhere
along the second Branch. The error can
also occur when two or more branches
are inadvertently connected to the same
terminal.
B100 TAIL TERMINAL PROBLEM Either the Tail terminal has an unset ADMIN
WITH SPREF SPREF or the SPREF points to a non-
existent SPCOM.
B110 TAIL TERMINAL PROBLEM Either the Tail terminal has an unset ADMIN
WITH CATREF CATREF or the CATREF points to a non-
existent Catalogue component.
B120 TAIL TERMINAL PROBLEM There is a Catalogue problem in ADMIN
IN ACCESSING P-POINTS accessing the p-points of the Tail
terminal.

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 3/8
5/24/2019 Data Consistency Check | PDMS Macro

B130 TAIL TERMINAL PROBLEM, A required p-point of the Tail terminal ADMIN
P-POINT NO.n DOES NOT does not exist in the set of p-points.
EXIST
B140 TAIL TERMINAL PROBLEM This is testing for flow with Branch to DESIGN
INVALID FLOW ATTRIBUTE Branch connections. Branches have a
ON CONNECTED BRANCH FLOW a ribute which can be set to
FORW or BACK or NUL. If FLOW is not
set correctly this results in an error
B150 TAIL TERMINAL PROBLEM, The FORW flow means that the fluid in DESIGN
TERMINAL INCONSISTENT the Branch goes from Tail to Tail with the
FLOW ACROSS BRANCH reverse for BACK. The code then checks
CONNECTION that the fluid flows correctly from one
Branch to the next. To fix the problem
check the network to see that all the
flows are in the correct direction
B200 DIRECTION TDIR NOT If the Tail is connected to a terminal, DESIGN
SAME AS TERMINAL such as a Nozzle or Tee, then the
DIRECTION direction TDIR should always be
identical to that of the appropriate p-
point of the terminal.
B210 POSITION TPOS NOT SAME If the Tail is connected to a terminal, DESIGN
AS TERMINAL POSITION such as a Nozzle or Tee, then the
position TPOS should always be
identical to that of the appropriate p-
point of the terminal.
B220 TBORE NOT SAME AS If the Tail is connected to a terminal, DESIGN
TERMINAL BORE such as a Nozzle or Tee, then the bore
TBORE should always be identical to
that of the appropriate p-point of the
terminal.
B230 CONNECTION TYPE If the Tail is connected to a terminal, DESIGN
TCONN NOT SAME AS such as a Nozzle or Tee, then the
TERMINAL CONNECTION connection type TCONN should always
TYPE be identical to that of the appropriate p-
point of the terminal.
C500 TUBE BETWEEN HEAD AND The distance between the Head position, DESIGN
TAIL LESS THAN TUBE HPOS, and the Tail position, TPOS, is
MINIMUM greater than zero and less than the
specified minimum tube length (default:
100mm).
C510 BAD HEAD TO TAIL Either the Head position, HPOS, does DESIGN
GEOMETRY not lie at a positive distance along the
line through TPOS in the direction TDIR
or the Tail position, TPOS, does not lie at
a positive distance along the line
through HPOS in the direction HDIR.

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 4/8
5/24/2019 Data Consistency Check | PDMS Macro

C520 HBORE NOT SAME AS When there are no components on the DESIGN
TBORE branch, the Head bore, HBORE, should
be identical to the Tail bore, TBORE
C530 HCONN IS NOT This implies that the Head is connected DESIGN
COMPATIBLE WITH TCONN directly to the Tail with no Tube or
piping components in between; hence
the Head connection type, HCONN,
must be compatible with the Tail
connection type, TCONN.
C540 THIS BRANCH HAS NO This does not necessarily indicate an DESIGN
COMPONENTS error. It is merely output as a warning to
the designer.
D100 REFERENCE SPREF UNSET This probably means that the designer DESIGN
has forgo en to select the piping
component.
D110 REFERENCE SPREF REFERS This may occur if part of the ADMIN
TO A NON-EXISTENT specification has been deleted
SPCOM
D120 SPREF PROBLEM, CATREF This indicates an error in the ADMIN
IN SPCOM IS UNSET Specification.
D130 SPREF PROBLEM, CATREF This may occur if part of the Catalogue ADMIN
IN THE SPCOM REFERS TO has been deleted or if the CATREF in the
NON-EXISTENT SPCOM is unset.
CATALOGUE COMPONENT
D140 SPREF PROBLEM, GTYPE OF The GTYPE of the Catalogue component ADMIN
CATALOGUE COMPONENT must be the same as the type of the
IS NOT SAME AS TYPE OF piping Component in the design data.
DESIGN DATA COMP0NENT
D150 SPREF PROBLEM, GTYPE OF An error has been found in accessing the ADMIN
CATALOGUE COMPONENT p-points of the Catalogue component
IS NOT SAME AS TYPE OF pointed to by CATREF
DESIGN DATA COMP0NENT
D160 REFERENCE CATREF UNSET This applies only to Nozzles, for which ADMIN
the CATREF must be set.
D170 REFERENCE CATREF This may occur if part of the Catalogue ADMIN
REFERS TO A NON- has been deleted. It applies only to
EXISTENT CATALOGUE Nozzles.
COMPONENT
D200 ARRIVE P-POINT NOT IN The arrive p-point number does not exist ADMIN
PTSET OF CATALOGUE in the PTSET of the Catalogue
COMPONENT Component.
D210 LEAVE P-POINT NOT IN The leave p-point number does not exist ADMIN
PTSET OF CATALOGUE in the PTSET of the Catalogue
COMPONENT Component.

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 5/8
5/24/2019 Data Consistency Check | PDMS Macro

D300 REFERENCE CREF NOT SET Multi-way Components may be left DESIGN
unconnected only if the connection type
of the relevant p-point is OPEN, CLOS,
VENT, DRAN or NULL.
D310 REFERENCE CREF POINTS This may occur if the Branch that is DESIGN
TO NON-EXISTENT pointed to by the CREF has been
BRANCH deleted.
D320 BAD CREF RETURN This may occur if the Branch that is DESIGN
REFERENCE pointed to by the CREF has been
reconnected to another terminal.
D330 REFERENCE CRFA n NOT An entry in the connection reference ADMIN
SET array may only remain unset if the
corresponding p- point in the Catalogue
does not exist or if the connection type of
the corresponding point is VENT,
OPEN, CLOS or NULL.
D340 REFERENCE CRFA n POINTS This may occur if the Branch pointed to DESIGN
TO NON-EXISTENT by the nth reference in the connection
BRANCH reference array has been deleted.
D350 BAD CRFA n RETURN This may occur if the element pointed to DESIGN
REFERENCE by the nth reference in the connection
reference array has been reconnected to
a third Branch.
D400 ARRIVE TUBE [ROD] LESS The distance between the arrive p-point DESIGN
THAN TUBE [ROD] of this component and the leave p-point
MINIMUM. ACTUAL TUBE of the previous component (or Head) is
[ROD] LENGTH IS … greater than zero and less than the
specified minimum tube [rod] length
(default: 100mm).
D410 BAD ARRIVE GEOMETRY + The position and direction of the arrive DESIGN
details of geometric errors p-point of this component are not correct
with respect to the leave p-point of the
previous component (or Head). The
error could be caused by incorrect
positioning of this component, the
previous component (or Head) or both.
D420 BAD ARRIVE BORE [ROD The bore of the arrive p-point of this DESIGN
DIAMETER] component is not equal to the bore of the
preceding tube or, if this component is
not preceded by tube, to the bore of the
leave p-point of the previous component
(or HBORE).
D430 BAD ARRIVE CONNECTION The connection type of the arrive p-point DESIGN
TYPE of this component is not compatible with
the preceding tube or, if this component
is not preceded by tube, to the
connection type of the leave p-point of
the previous component (or HCONN).

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 6/8
5/24/2019 Data Consistency Check | PDMS Macro

D500 REFERENCE LSTUBE The user has probably forgo en to select DESIGN
[LSROD] UNSET the piping/hanger Component.
D510 REFERENCE LSTUBE This may occur if part of the ADMIN
[LSROD] REFERS TO A NON- Specification has been deleted.
EXISTENT SPCOM
D520 LSTUBE [LSROD] PROBLEM, This indicates an error in the ADMIN
CATREF IN SPCOM IS Specification.
UNSET
D530 LSTUBE PROBLEM, CATREF This may occur if part of the Catalogue ADMIN
IN THE SPCOM REFERS TO has been deleted or if the CATREF in the
NON-EXISTENT SPCOM is unset
CATALOGUE COMPONENT
D540 LSTUBE PROBLEM, GTYPE The component pointed to by LSTUBE is ADMIN
OF CATALOGUE not of type TUBE in the Catalogue.
COMPONENT IS NOT SET
TO TUBE
D550 LSTUBE [LSROD] PROBLEM There is a Catalogue problem in ADMIN
IN ACCESSING PPOINTS accessing a p-point of the tube/rod
pointed to by LSTUBE [LSROD].
D600 LEAVE BORE [DIAMETER] The bore of the leave p-point of this DESIGN
NOT SAME AS BORE Component is not the same as the bore
[DIAMETER] OF LSTUBE of the tube/rod following the
[LSROD] Component.
D610 LEAVE CONNECTION TYPE The connection type of the leave p-point DESIGN
NOT COMPATIBLE WITH of this Component is not compatible
CONNECTION TYPE OF with the tube/ rod following the
LSTUBE [LSROD] component.
D620 INSULATION CANNOT BE There is no suitable insulation in the ADMIN
SELECTED USING LEAVE Catalogue for the combination of
BORE temperature TEMP and the bore of the
leave p-point.
D630 ATTACHMENT TYPE You have set an incorrect TYPE a ribute DESIGN
INVALID – MUST BE ONE for an ATTA.
OF FLOW, XXXX, SSSS,
CCCC, CCNN, INPP, WELD,
HANG, PENI, NUL OR NULL
D740 ANGLE OF COMPONENT IS The designed angle of a Pulled Bend, DESIGN
GREATER THAN MAXIMUM Elbow or Weld is greater than is allowed
ANGLE SPECIFIED IN SPREF by the SPECs
D740 ANGLE OF COMPONENT IS The designed angle of a Pulled Bend, DESIGN
LESS THAN MINIMUM Elbow or Weld is less than is allowed by
ANGLE SPECIFIED IN SPREF the SPECs.
D740 ANGLE GREATER THAN m The designed angle of a Pulled Bend or DESIGN
DEGREES. ACTUAL ANGLE Elbow is greater than the maximum
IS n. angle specified by the user (see
TOLERANCE MAXANGLE).

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 7/8
5/24/2019 Data Consistency Check | PDMS Macro

D800 Reference DETAIL unset. This refers to the DETA a ribute of the ADMIN
SPREF of the branch component.
Without it no SKEY will be available for
that element within ISODRAFT.
D820 SKEY not set ADMIN
D840 SKEY #N not known. ADMIN
Assumed to be user defined
E700 LEAVE TUBE LESS THAN The distance between the leave p-point DESIGN
TUBE MINIMUM. ACTUAL of the current component and the tail
TUBE LENGTH IS … position, TPOS, is greater than zero and
less than the specified minimum tube
length (default: 100mm).
E710 BAD LEAVE GEOMETRY The position and direction of the leave p- DESIGN
point of this component are not correct
with respect to the position, TPOS, and
direction, TDIR, of the tail. The error
could be caused by incorrect positioning
of this component, the Tail, or both.
E720 LEAVE BORE NOT SAME AS The bore of the leave p-point of this DESIGN
TBORE component is not the same as the tail
bore, TBORE.
E730 LEAVE CONNECTION TYPE The connection type of the leave p-point DESIGN
NOT COMPATIBLE WITH of this component is not compatible with
TCONN the tail connection type TCONN.

Leave a comment
Posted by pdmsmacro on February 2, 2013 in PDMS Piping Training

Tags: AVEVA PDMS macro, ch ce pdms, download pdms macro, isodraft error, pdms data consistency
check, pdms design error, pdms design error messages

Create a free website or blog at WordPress.com.

Entries (RSS) and Comments (RSS)

https://pdmsmacro.wordpress.com/2013/02/02/data-consistency-check/ 8/8