Note: The mapping files use a series of abbreviated names for  supports and piping components, see the PCFIN.MAP file in the PCF translator folder for descriptions of the abbreviations.

Error E33 message as below

E33 No component was found that matches the database search criteria

An error occurred while trying to use the pipeline name keyin value. Either the value is missing, or word 12 is set incorrectly.

Confirm DEFSTR.dat file has word 12 = correct attribute  0 to 3 as below

e.g. 3 = STRESS_SYSTEM_NO

INTERGRAPH OPTIONS BLOCK
!note: refer to PRO_DD_PDSSTRESS:PDSSTRESS.DOC.  Maximum 45 options
   1,   1,  901, 2001,   0,   6,   1,   1,   0,   1,   1,   0,   0,  20,   0,
   0,   0,    0,    0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
   0,   0,    0,    0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   99912

0 Extracts the network by substring of the pipeline name attribute,

LINE_NUMBER_LABEL (Refer to Appendix B, table 12, column 2.)

1 Extracts the network by substring of the stress analysis ID attribute,

STRESS_SYSTEM_NO (Refer to Appendix B, table 12, column 52.)

2 Extracts the network by equality of the pipeline name attribute,

LINE_NUMBER_LABEL (Refer to Appendix B, table 12, column 2.)

3 Extracts the network by equality of the stress analysis ID attribute,

STRESS_SYSTEM_NO (Refer to Appendix B, table 12, column 52.)

Error retrieving Support Type: 81804E9GG

This was caused by following two supports:

NS, 81804E9GG,560-MS-053,CODE1,   8 MPROP,NS, 81804E9GG, 2,560-MS-053,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 DS, 818045DGG,5UG-090,CODE1,   8, 902 MPROP,DS, 818045DGG, 2,5UG-090,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 MPROP,DS, 818045DGG, 4,0.673,0.7396,0.0,0.0,0.0,-1.0

Looking at default Supports.map file, it was obvious that first support did not have any support type mappings i.e. for 560-MS-053. I needed a line in the mapping file for NS support like

560-

Now since this NS support is used in conjunction with another support which has a support type = 5UG-090  - we would need our mapping to reflect the fact that 560- support can come along with the other support:

So by adding only 1 line in Support.Map file will fix this. 

560-+5U(S,G)                      VSTP

Error retrieving Coordinates for Node: 0

Block switch change is ok in Defstr.dat but it appears the STRMAP.TBL and Defstr.dat files were not used by PDSstress module to create the 5000.n file

The path in Defstr.dat is not updated - is this your correct path?

  c:\win32app\ingr\pdstress\dat\strmap.tbl      !PDS TO STRESS MAP

Other clues to not using the provided configuration files, For example, There are components like "RE" and "TW" in the neutral file that we don't support. Another example is that the number of comma-delimited items in the PI card should be 6, but in 5000.n, the number of items is 7.

Error message ** Starting model at node 0 **

No. Index  Type   Comp.Id     P1    P2    P3    P4    P5    P6    P7 --- -----  ----  ----------  ----  ----  ----  ----  ----  ----  ----

Your systemname.n pds file did not convert correctly because

You did not use DEFSTR.DAT to create the PDS neutral file sktest.n.

Typical PI component using DEFSTR.DAT:

PI, 580001GG,6"4001_01_02_07,CODE0,   7,   6MPROP,PI, 580001GG, 1,API-5L-B,0.000000,0.000000,0.000000,001MPROP,PI, 580001GG, 3,6.0,168.300003,BW,S-40, 80001GGMPROP,PI, 580001GG, 4,6.0,168.300003,BW,S-40, 80001GG

Contrasting PI component from sktest.n:

PI, 5CB00FE7,10"STD5356030,,CODE1,   7,   8MPROP,PI, 5CB00FE7, 1,A106-B,0.0000E+00,0.0000E+00,,0,,0.0000E+00MPROP,PI, 5CB00FE7, 3,10.0,273.049996,BW,9.271,, CB01421MPROP,PI, 5CB00FE7, 4,10.0,273.049996,BW,9.271,, CB01421

Try re-creating the *.n file using the DEFSTR.DAT sent by Bentley.

  *** ERROR - E35 ***

Error searching for PDS item name in PDS to STRESS map

  Item name : STTS  PDS to STRESS map :\\DESCLTPDS02\ddrive\173101\pds\stress\data\strmap.tbl

This means the path to the TBL file is incorrect the DEFSTR.dat file

 PDS Interface Error Report

PDSSTR version 06.04.01.10

 o21091.n & pw16034.n

! Date                 : 13-MAR-2002 11:12:06  *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : -1   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** WARNING - W4 ***  Unable to locate end prep, default end prep used  End prep : 300   *** ERROR - E35 ***  Error searching for PDS item name in PDS to STRESS map  Item name : 5SLE  PDS to STRESS map : c:\win32app\ingr\pdstress\dat\strmap.tbl   *** ERROR - E35 ***  Error searching for PDS item name in PDS to STRESS map  Item name : 5LP  PDS to STRESS map : c:\win32app\ingr\pdstress\dat\strmap.tbl

In both your PDS model neutral files (pw16034.n & o21091.n), the files appear to have terminated prematurely because of an error during the PDS neutral file creation process.  Hence, the information in the files is not complete.  In one model (pw16034.n), it appears that the mapping data for the component item name “5SLE” is missing from the PDS to STRESS map file as reported in the first pdsstr.err file.  In the other model (o21091.n.n), it appears that the mapping data for the component item name “5LP” is missing from the PDS to STRESS map file (strmap.tbl) as reported in the second pdsstr.err file.  To fix this problem, you will need to provide the missing component items in the PDS to STRESS map file (c:\win32app\ingr\pdstress\dat\strmap.tbl) and re-generate the PDS neutral files.  Please let me know if you need further assistance.

Partial completion of NTL file

Reviewing the processing steps in the DBG file for 020524b.n, there appears to be several anomalies in the PDS neutral file that I have never seen before. These anomalies are causing processing problems in STRAIT.  It does not appear that this file was generated from the PDS stress interface module. .Do you know how it was generated?   Here are some of the anomalies that I observed:

1. The same component identifier "31B000CBG" is defined twice in the PDS neutral file but with different node numbers:

RB, 31B000CBG,6"WCAAAAWAAA,CODE0, 914,  36RB, 31B000CBG,6"WCAAAAWAAA,CODE0, 902,  36

2. Some components are defined twice in the PDS neutral file.  For example, component 51B0010BG is defined on line 167 and again on line 447.  Similarly, component 31B000B9G is also defined twice on line 162 and again on line 442.

3. Not all the end nodes (node > 900) are referenced by the components in the PDS neutral file.  In other words, I do not understand how it is possible that only 2 of 24 end nodes are referenced by the model (nodes 902 and 914).  STRAIT relies on an end node or nozzle (LNOD) to start an AutoPIPE segment.  Consequently, after starting segments at nodes 902 and 914, there were no other end nodes left in the model for STRAIT to start from.  It would be possible for me to modify STRAIT to start from a free end, but this would require a lot of processing time to identify all the free ends in a large model.

4. The processing history of 020524b.n is given in 020524b.dbg.  Notice that after processing the olet component 31B000B9G, STRAIT does not search for a connecting component at node 37 of the olet.  STRAIT is designed to stop at the olet in order to avoid 90 degree kinks in the segment.  The assumption is that STRAIT will process the header later and connect it to the olet at that time.  In the model you sent me, the corresponding header for the olet had no end nodes and consequently, STRAIT could not start a new segment from the beginning of the header (see comment 3 above).  It might be possible for me to modify STRAIT to start a new segment from an olet node in the special case where there are no other nodes to start from as in 020524b.n.

Support Delimiter string

The Strait.cnf file contains a Support Delimiter string as shown below which the default is "-" which signifies the end of the callout.

SETTINGS0.25 ! Minimum Pipe SizeSSTD ! Default Schedule/ThicknessCS ! Default Materials- ! Support Delimeter string

This can be changed to any other character e.g "&", "$" etc especially if "-" character exists in the PDS support numbering e.g 5ASW-10

In PDS 2 support types are available NS = non-directional supports e.g typically v-stops and

DS = directional supports e.g. anchors where the direction cosine is defined by a pipe point (<900) and end point (>900).

PDS 1-way support

STRAIT can process 1-way PDS supports if they are mapped to either INCL, ROTA, or DAMP in the supports.map file. It works for both “DS” and “NS” component types. For “DS”, STRAIT calculates the direction cosing using the “from” and “to” nodes in the “DS” card. For NS, STRAIT defaults the direction cosines to 0,1,0.

Support not translated

There are 3 issues with the .N file that are causing the error messages.

A support cannot be defined at a tee or olet point – node 26 in an olet point as defined on the line “   5    21    OU   32B0023EG     26“ in the .N file. You can confirm by moving the support to node 27, i.e. change 26 to 27 for the support in the .N file and the problem does not occur.

23    NS   82B000DBG    26

Disconnected segment – Node 21 do not connect back to any other components in the main part of the model.

57    32    PI  52B07531G    20   914                              58     3    PI  52B000D3G    21    20

Disconnected supports – the two supports below do not connect to any piping node, e.g. nodes 19 and 29 are not defined in any of the piping components.

4    NS   82B000D9G    190    NS   82B000DCG    29

Error and Warnings #1

Several of warning messages we get are related to supports because we do not have your updated supports.map file.

Note: The filename.err file contains list of all the warning and error messages.

Several of following components appear to not have all fields written to PDS neutral file:

Warning: mismatched fields; Component ignored: 6180032GGWarning: mismatched fields; Component ignored: 6180033GG

e.g. only 5 instead of 6 fields plus properties for this Olet, We believe this is mapping issue in your strmap.tbl for these 2 components.

OL, 6180033GG,, 927, 109

Several warning messages related to line numbers not found in the project.lst file but also there is a column missing for corrosion, see updated project.lst attached.

Error reading Line List File: 1001Error reading Line List File: 1029Error reading Line List File: 1010Error reading Line List File: 1341

Warning: invalid spec code; pipe name ignored: 100.0000

Using option 6 = 3 in strait.cnf  is causing this warning message we  recommend changing this option to 0

2 unprocessed components - check connectivity of the PDS model because these PDS components do not have any other nodes connected to.

These appear to be part of the orifice plate e.g instrument piping and may be best to ignored this message.

Warning: unprocessed Component found: 6200022GGWarning: unprocessed Component found: 6180031GG

Component Mapping #1

Appears orifice plate needs to be mapped to flange, FL (or RB ,rigid body) in the Strmap.tbl

STRAIT component not mapped

The component type discrepancy between E24 and E25 is a mapping issue when generating the PDS neutral file. In the PDS neutral file (HPS.N), the component type "RB" is specified for the PDS component ID "6388004EG". The "RB" was assigned based on a component mapping file, "strmap.tbl", when generating the PDS neutral file (*.n). AutoPIPE then converts any "RB" components in the PDS neutral file to a rigid pipes which are shown in magenta color in the AutoPIPE model.

RB, 6388004EG,Inst-**PV-007,CODE0,  82, 107PROP,RB, 6388004EG, 1,,3.000000,0.000000,0.000000,18004001PROP,RB, 6388004EG, 2,CL150,CL150,0.000000PROP,RB, 6388004EG, 3,6.0,6.625000,WN,NREQD, 3881100GPROP,RB, 6388004EG, 4,6.0,6.625000,WN,NREQD, 3881100G

If the component defined between E24 and E25 is actually a valve, then the component map file (strmap.tbl) need be updated to assign "VA" instead of "RB" to the PDS component type defined between E24 and E25. Additionally, if there is no component mapping information for the PDS component type in strmap.tbl, it will be mapped to "RB" by default.

Material Default

Material defaults to CS instead of A106-B

You have setup to use the materials.map file in the strait.cnf file i.e option 8 = 1, hence Strait will try to map materials found in

the PDS neutral file to Autopipe materials - if not found then defaults to material in strait.cnf file.

There are no material names (i.e blank) defined in the PDS neutral file - appears no materials defined in the PDS model.

You can set the default material A106-B in the strait.cnf  for all materials for all pipes to be set to A106-B.

Error and Warnings #2

The following warning messages in the S01.err file

Warning: invalid spec code; pipe name ignored: 60.00000Error retrieving Support Type: 82800003GError retrieving Support Type: 82800013GWarning: invalid spec code; pipe name ignored: 20.00000Error retrieving Support Type: 82800016G

Adding the following assemblies in supports.map fixes the support type errors above.

Assemblies do provide mapping many supports at one location to 1 or many different Autopipe support types.

Note: supports at node 12 are 5FSX1-W and 5G2 which are both mapped to VSTP

5G(1,2,3);+5S(1,2,3)(C,G,M)(3,4,5,6)(L,#);            GUID,VSTP5FSX1-W;+5S(1,2,3)(C,G,M)(3,4,5,6)(L,#);                   VSTP

Note: Amended supports.map to the following.

!5S(1,2,3)(C,G,M)(3,4,5,6);                                VSTP5S(1,2,3)(C,G,M)(3,4,5,6)(L,#);                            VSTP

Note: In some cases guides and vstops are mapped at the same point which makes the vstop redundant.

"Warning: invalid spec code...."

Option 6 for pipe identifiers is limited to 6 characters

Using option 6 = 3 in strait.cnf  is causing this warning message we  recommend changing this option to 0

Disconnected segments and DBG file

Besides tees and olets, supports cannot be added to bend centers. This is a just a logical condition programmed in the translator. I think we could remove this limitation, if needed.

The disconnected components and supports are reported in the DBG file. In the example below, nodes 19 and 29 are not defined on any other piping components in the PDS neutral file.

 Warning: Unprocessed Components: Index  Type   Comp.Id     P1    P2    P3    P4    P5    P6    P7 -----  ----  ----------  ----  ----  ----  ----  ----  ----  ---     4    NS   82B000D9G    19    23    NS   82B000DBG    26    30    NS   82B000DCG    29

For the disconnected segments, you need to check the error message file and look for any warnings like the one below.

Warning: possible unconnected segment found: I1

Then, you need to look in the DBG file for the block of components that belong to the disconnected segment as shown below. In the example below, node 914 is an end point and node 21 is not defined on any other piping components in the PDS neutral file. So, the entire segment is “disconnected”

** Starting new segment from I1 **  51    32    PI  52B07531G    20   914                                52     3    PI  52B000D3G    21    20

The DBG file has all the information one needs to troubleshoot modeling problems created by PDS

Scenario 1

The two supports below defined in the “plantsteam.n” model neutral file could not be processed because the “P1” nodes are not defined on any piping component in the model neutral file. The “P1” node appears to be the center node of a component but the component itself is not included in the model neutral file. This problem could be caused by improper modeling in the PDS model or invalid mapping of some of the PDS components in the “strmap.tbl file” or improper mapping of the two supports in the “supports.map” file.

Type   Comp.Id     P1    P2    P3    P4    P5    P6    P7----  ----------  ----  ----  ----  ----  ----  ----  ---  DS   86080001D  2032   936  DS   860800020  2047   940

Scenario 2

There are two set of pipe segments below in which both ends of the segments are not connected to any other component in the main model.

Segment 1:  node 913 is a free end node. By definition, a free end node are not connected to any other component. Node 423 is not defined on any other piping components in the model neutral file.

RB  36080000F   913   430NP  36080000E   428   430VA  36080000D   426   428  2009NP  36080000C   423   426

Segment 2:  nodes 966 and 970 are both free end nodes. By definition, a free end node is not connected to any other component.

RB  3608001EA   966     6NP  3608001F3     6     5VA  3608001F4     5     4  2069NP  3608001F5     4     3RB  3608001F6   970     3

If there are actually components defined in the PDS model at nodes 913, 423, 966, or 970, then the problem could be caused by improper modeling in the PDS model or invalid mapping of some of the PDS components in the “strmap.tbl file”.

Disconnected segments and DBG file

AutoPIPE program crashes when import the STRAIT converted file.

Answer: Confirm that there is not a close loop in the original PDS model. At this time AutoPIPE V8i 9.6 and lower does not suport a close loop, segment connected back onto it self.

Enhancement has been looged: CAE-CR-9416: Add ability to import closed loop segments from PDS

See Also

Bentley AutoPIPE

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please submit any comments you have on this Wiki article to
the "Comments" area below. THANK YOU!