AutoPIPE is able to import a variety of file formats. However, CAESAR and Aveva PDMS read/write ability is very restrictive and can only communicate with AutoPIPE through the CII file format. Therefore the ability to read/write information between the 2 applications is well documented in AutoPIPE's online help, including complete information on mapping components.

Attention: Please see the following AutoPIPE help section:
Help > Contents> Search Tab> enter "Caesar CII Mapping" (include the quotes), press List Topics button, double click on the selected topic from the list provided to see more information about:

• Node Number Mapping

• Component Mapping

• Support Mapping

• Load Case Mapping

• Limitations

Frequently Asked Questions

1. Typical problems with importing CII files into AutoPIPE files

2. Imported CII file with segment origin points are reset to 0,0,0.

3. After importing a CESAR file into AutoPIPE, found that after pressing the toolbar button "Show Pipe Properties" does not have an option to view "ALL" Pipe identifiers. Did the import corrupt the program?:

4. The translation of Cii support to AutoPIPE produces arrangements that look messy (using a mixture of Inclines and other supports).

5. Imported CEASER file appears to open, but does not, and program crashes displaying " Bentley AutoPIPE Application is not responding"

6. Load Cases not defined when importing Caesar cii file.--I'm trying to import a .cii Caesar file, and the load cases are not defined. The geometry is there but I can't place any load cases.
   
   Answer: Once the cii file has been opened you must reset the load cases to run the analysis. Instead of selecting the icon to run a static analysis, go to the dropdown menus and select Load> Static Analsysi sets, confirgure the analysis set, press OK button, choose Analyze> Static, and then review combinations with Tools> Combinations command.
   

Error message on Caesar Import:

1. Caesar imported file caused "forrtrl: severe (64) - Input conversion" error

2. The following is displayed:
   
   TEE 3710 F 0.0000 0.0000
   *** ERROR: CANNOT PUT TEE AT THIS POINT. TEE IGNORED.
   
   

   Answer:
   This is caused when a tee is configured for a location that AutoPIPE cannot phiysically place a TEE because of an internal componnent connection based on the CII configuration.

   Solution:
   a. Open the CII file in any word processing program.
   b. Search for the location indicated in the error message
   c. See attached file for CII file format details
   d. In the element section, move up a few elements and hand sketch the elements down and past the indicated point.
   e. Review the other section to verify correct settings (i.e. is the tee at the intersection point, is the bend radius correct, pipe diameter, etc..

   In this scenario, the SIF & TEES section had a intersection point that had the wrong name. Modify the tee intersection point with the correct name an file is able to be imported without any errors.
    

3.  

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!

Each AutoPIPE translator is installed with a complete manual about the application. See the following for more details about the tranlator program:

C:\Bentley\AutoPIPE Translators\PCF Translator \ SmartPlantToAutoPIPETranslator_UserReference.pdf

Issue #1:

All the AutoPIPE models that we import from Autodesk Inventor PCF files show flanges and valves as weightless “Zero Weight” components. Is there anything that we can do different on our end to have inventor PCF files carry-out the flanges and the valves weights?

Solution:

Most common cause is your mapping (pcfin.map). Please see the following folder:

C:\Bentley\AutoPIPE Translators\PCF Translator\

Suggest that you review the all files in this location for complete details on this feature. To answer your question directly, your PCF file is not mapping items correctly. Example of a model that imports a flange without error or warnings:

    ITEM-DESCRIPTION    Flange, CL150, RFFE/SWE, ASTM A182-F304, ANSI-B16.5, S-40S

Recommend adjusting PCF file with a valid description, or fix the map file to import your flanges to anything but the default settings.

If there is no mapping between skey item and type, then default will be applied, default is NS (nonstandard).

Issue #2

Q. When trying to convert a file from PCF to NTL, the converter freezes at “Parsing complete…” it never creates the NTL file.

A. Review the PCF file, duplicates of certain components on the same coordinates will cause the connecting logic in translator to hang. Therefor the current PCF file does not  seem like a valid / good PCF file. Open the original model to review duplicate components before exporting a new PCF file to be converted with the AutoPIPE translator.

Issue #3

Q. Program does not import a PCF file and hangs with no error message.

A. Review the original model for a closed loop. AutoPIPE does not support a closed loop (segment connected back to itself) and if detected will hang with no error message.

Issue #4

Q. When trying to convert a file from PCF to NTL, the converter freezes / aborts and it never creates the NTL file, why?

A. After reviewing the file, noticed that there are overlapping components which also freezes the PCF translator. The CAE development team will add some programming logic in the next PCF translator build to display a warning message. PCF translator v.1.0.0.29.

Issue #5

Q. Following is displayed when trying to open converted PCF , NTL file in AutoPIPE:

"E880-1: Error in opening import batch file. File extension must be NTL".

A. There is a known issue if the file name has a blank space before the file extension, the above message is displayed. Confirm that the file name does not have a blank space before the file extension, example: "Test .NTL", remove space "Test.NTL"

Issue #6

Below are general questions and answers about the process  of exporting an existing AutoPIPE model (DAT) to a PCF file, translate the newly created PCF file with the PCF translator back into an AutoPIPE model, and compare AutoPIPE results between before and after translation:

Q1.   The expansion joint are not support in the current PCF translator

A1. Support for Flex/Expansion Joints were implemented in PCF translator 1.0.0.24. Can You please use the latest release of PCF Translator. You can get the newer version of translator from ftp://ftp.bentley.com/pub/tools/fixes/autopipe/PCF_Setup_1.0.0.25.exe (Dec 2012).

Q2. The pipe is oriented 180 deg from original

A2. Before export to PCF from AutoPIPE, In AutoPIPE  Go to Tools> Settings > Isogen Settings

Change North arrow to +X then the coordinates matched exactly

Q3. Pressure and Temp are different from before to after, example: 10 deg & 100 psi converted to 0.0 deg  & 0.0 psi

A3. This is a limitation in AutoPIPE PCF Export, which does not write Pressure and Temperature and hence default values are used.

Q4. Pipe properties changed; wall thickness changed sch 160  changed to STD and Pipe material, from A335-P91 changed to A106-A

 A4. There is a limitation in AutoPIPE PCF Export could not correctly map the material and by default A106-A with STD wall thickness has been used. Adjust the map file as required to correctly map the material and wall thickness.

Q5. Extra support (V-stop)  added to the converted file at origin point with anchor.

A5. During first time Export to PCF. AutoPIPE write Anchors as a Support with SKEY 01AN and then on import this support component converted to an default support V-STOP. Manually delete V-Stop.

Q6. Flanges converted for the expansion joint are in the wrong location.

A6. This has been fixed in a newer version of the translator, upgrade to the latest version of PCF Translator, v1.0.0.32.

Q7. Tee SIF values are different (because of wall thickness issue above, Q4)

A7. Yes, proper schedule has not been exported by AutoPIPE in PCF. update PCF map file accordingly.

Q8 Bend radius is different

A8. Bend length is exactly same but after import from PCF the actual radius has been written instead of "LONG"

Problem:

In addtion to the "StressISO_Troubleshooting.pdf" document found on your hard drive, see the following information: 

TR Number: None
Product: AutoPIPE
Version: n/a
Area: General
Problem ID#: 72015

Answer:

solution 500000088706

Information:

Isogen is a 3rd party software that is bundles with many cad applications such as Bentley AutoPIPE to automatically produce an isometric drawing. Isogen is very particular about the format of the data being converted into an DXF, DWG, or DGN file format. If there is one error in the data Isogen may hang, display a message about warnings with the file, etc...

Use the following steps to trouble shoot an Isogen related issue with AutoPIPE:

1. Known issues

Known issues are documented in the StressISO_Troubleshooting.pdf located in the AutoPIPE folder. Review this document to see if it is a known issue.

2. Isometric based on actual pipe components:

For an example, AutoPIPE can model a tee where the branch axis matches the same direction as the tee's header pipe axis. This is wrong modeling but can be done in AutoPIPE.

However, Isogen will abort because it knows that a tee like that cannot be constructed. In order to export the model, the tee must be fixed so the branch axis does not match the header axis.

The goes for all other pipe components, if the actual component cannot be drawn because of dimensional issues or arrangement, then isogen will abort trying to create a stress iso.

Recommend:

a. Review all valves and flanges closely. Be sure all are modeled correctly
b. Review Tools> Model Consistency Check report to reduce number of warnings.
c. In general, review model looking for obscurities.

Typical issues:
---------------------

a. Flanged valve in middle of pipe run without attached flanges, add flanges to both sides of valve.

b. In middle of pipe run, back to back flange set. Upon closer inspection, there are 3 flanges. Remove the correct flange.

c. Known limitation, reducer cannot be the start or end of segment. Add short pipe run from reducer.

d. Middle of pipe run where 2, 4 inch dia, branches are placed side by side on top of the pipe. However branch center lines are only 3 inches apart causing an overlap. This can be modeled but not exported to Isogen. Fix by reducing branch size or moving center lines apart.

e. Kink in pipe of 179.9 deg, remove pipe kink.

f. W726-170:The tee at point E00 has only two legs, fix by adding a branch run pipe, or change Tee node to a Point node.

3. Where is the warning occurring

If the following is displayed:

---------------------------
ExecISO
---------------------------
There were some warnings and/or errors while executing ISOGEN.
Do you want to review messages:
---------------------------
Yes No
---------------------------

Select the Yes button and

C: \Bentley \AutoPIPE V8i SELECTseries \PISOGEN \PROJECTS \APIPEPROJ \FINAL \OUTPUTFINAL.MES

is automatically displayed. Review the entire document and try to resolve any and all warnings displayed.

4. Disconnected systems:

Before creating a stress iso, review the model segments to be sure they are connected and do not stop at a component (i.e. valve, reducer, bend). Sometimes a run of pipe is broken into multiple segments on the same run of pipe. Remove any additional segments by jointing them at node points.

In addition, with a complicated model use the following feature: Select> Connected segments> choose only one box to highlight a connected series of pipe. AutoPIPE stress iso cannot process 2 disconnected segments at the same time.

With one group of piping selected, create a stress iso as before, and be sure to confirm the "use connected segment" check box is checked ON.

Note: If using "Modeling a "dummy leg" as a structural member or a pipe" modeling technique, stress Iso cannot generate the dummy support. Only 2 workaround suggestions: a. use a different modeling technique allowed by ISOgen or b. manually modify isometric after being created in a cad application.

5. Clean folder

Create a new folder on the Desktop, copy the model's DAT file to the new folder, start AutoPIPE, open the file from the new folder location, run the analysis, try to create a Stress iso DXF file instead of DWG or DGN file.

6. Model Size Limitation:

Isogen has some model size limitations. Try selecting a portion of the model that is completely connected and creating a stress iso based on the select set. See #5 above for technique to select connected segments. Otherwise, need to manually create a selection set of connected segments.

7. Stress iso Template files

AutoPIPE V8i 9.3 and lower:

All Stress iso template files need to be saved into AutoCAD 2000 format only; see the following procedure:

1. Open the isogen title bock in AutoCAD

2. Once open, run an audit by typing A-U-D-I-T in the command line.
AUDIT command evaluates the integrity of a drawing and corrects some errors.

3. When completed, purge the drawing by typing P-U-R-G-E in the command line. The PURGE command removes unused items, such as block definitions and layers, from the drawing.

After the above has been completed, copy the file to the AutoPIPE folder

….C:\Bentley\AutoPIPE V8i SELECTseries3\PISOGEN\BORDERS

In order to use the new border file, under "Isogen Settings" confirm: Drawing Frame File, User Defined, Plot Frame, Drawing Size, AutoCAD units, Dimension/Tex formats settings.

See following link as help

http://communities.bentley.com/other/old_site_member_blogs/bentley_employees/b/joeys_blog/archive/2010/06/03/ddt-audit-generated-on-autoplant-piping-isogen-drawings.aspx

AutoPIPE V8i 9.4 and higher:

Skip the last step for saving to previous version and only A-U-D-I-T, P-U-R-G-E is required before saving the file to 2010 - 2012 format.

8. Switches:

There are 100's of switches that can be adjusted for isogen. Recommend resetting these switches by overwriting the Stressiso.ini and Apipe.opl files with a default copy of each file. Or, use a copy from a person's computer who does not have such issues when creating an iso from the same file that you are having troubles with.

Reset Default Settings
-----------------------------------------------------------------------------
Stress iso stores dialog settings and other information in a variety of files/locations:
___a. Stressiso.ini
___b. Apipe.opl
___c. C:\Bentley \AutoPIPE V8i SELECTseries \PISOGEN \PROJECTS \APIPEPROJ \Final

Depending on configuration, settings enter, or anomalies there could be a conflict when creating a stress iso. Only after completing all the above steps 1-8 should this resolution be considered. The best solution is to reload the default settings again before trying to run stress iso. The easiest method of resetting the default values is over write the current files with a copy of the original files when the application was installed. If you do not have a copy of the original files, suggest uninstall/reinstall the application.

9. Register DLL

The following is displayed in the Final.MES:

***** POD Error(s) *****
Unable to initialise POD : Failed to generate POD - Conversion failure :

Register all DLL
---------------------------------------

a. Close AutoPIPE

b. Log into computer with Admin Rights

c. Locate Register.dll, generally found in "C:\Program Files (x86)\Common Files\Bentley Shared\Plant V8i\Isogen".

d. Right click on the file, select "Run as Administrator" option

e. The screen will display the Dos cmd window and automatically register the following DLL's in the system:
____pipeline.dll
____skey.dll
____importexport.dll
____pod.dll
____pisogen.dll
____materialdata.dll
____smartrad.dll
____catmanager.dll
____idfgen.dll

Note: these DLL should have been registered when the application was installed. Something had prevented them from being registered correctly.

f. Restart AutoPIPE and try to create a new stress Iso drawing.

Register specific DLL
---------------------------------------

a. Close AutoPIPE

b. Locate POD.dll, generally found in "C:\Program Files (x86)\Common Files\Bentley Shared\Plant V8i\Isogen".

c. Open the command-line prompt
____Start Menu> Run
____Type "cmd"
____Press "ENTER" or "Return" keyboard key

d. Using the POD.dll filename and path, call regsvr32, i.e. at the command-line prompt, type:
____ regsvr32 "C:\Program Files (x86)\Common Files\Bentley Shared\Plant V8i\Isogen\pod.dll"
____ Press "ENTER" or "Return" keyboard key

e. You should see a regsvr32 window, confirming success: Close it.
____RegSvr32
____DllRegisterServer in C:\Program Files (x86)\Common Files\Bentley Shared\Plant V8i\Isogen\POD.dll succeeded.

Press "OK" button.

f. Restart AutoPIPE and try to create a new stress Iso drawing.

10. Dimensioning Stress Iso

On the "Stress Isometric Options" dialog, click on the "Isogen Settings" command button, or select Tools > Settings > Isogen…> select the "Dimension / Text tab" displays the current options/settings for adding dimensions and text on a stress Iso drawing.
The Stress Iso utility has a limited number of options available for dimensioning a model and are all listed in the dialog. Any options or type of dimensioning not listed would be considered an enhancement. Please log a service ticket requesting the enhancement in detail.

11. Dimensioning across segments and flanges appear incorrect

A stress Iso was created for a given model. On the stress Iso, it has been observed that the total length of pipe from the pipe end to a flange set (Dim A) and distance from flange set to bend TIP point (Dim B) adds up to be correct total distance. However Dim A and Dim B do not equal the actual values in the model. Additional note, the flange set is at the junction point between 2 connected segments.

As AutoPIPE does not have the length for the flange and it cut the pipe to arrange the space for the flange. As for normal pipeline this scenario works perfect but there is a limitation in AutoPIPE that if the flanges placed on the segment continuation point then the space allocation for flanges can be cut from the one side. By that there was the change in the length which is equal to the flange hub length (ex. 305mm).

The avoidance is to join the segments by selecting the node point between the segments (ex A04) and go to "Edit > Segment > Join" and then export to stress ISO. Then Dim A and B on the model match that in the exported stress Iso drawing. The CAE development team will be adding a 2 point flange in AutoPIPE V8i 9.7project to dismiss such scenarios as seen above.

12. Nothing happens after pressing OK on Isogen settings dialog
(iso not created)

Application was not installed using full administrative rights. Uninstall and re-install AutoPIPE with full admin rights

13. Drawing file is not created, but PCF file is:

___A. Be sure that AutoPIPE was installed on the computer with a person who has has full admin rights. If unknown, completely uninstall the program, delete AutoPIPE folder, reboot the computer logging in with admin rights, reinstall the application.

___B. Check to see if the version of AutoPIPE installed is listed in "add/remove programs" (Win XP) or "Program and Features" (Win 7). If not listed, completely uninstall the program and reinstall with full admin rights.

___C. If the above does not resolve issue send computer information by performing the following:
Computer's system information:
1) Start> Programs> Accessories> System Tools> System Information.
2) After the program has been opened, select File> Save> save file
3) Send me a copy of systemname.NFO file for review.

___D. Also, perform the following:
1) Start DOS command, select Start> Run> type "cmd"
2) Type, cd .. until c:\> is shown
3) Type, c:\> Dir /s /o /ogne>systemname.txt
4) Send me a copy of the systemname.txt for review.

These files may be large and can be shrunk by adding it to a ZIP file. Create a service ticket and send files for review

14. Anchor symbol is not drawn correctly:

Please follow these steps.
1. Close AutoPIPE
2. Open AutoPIPE's installation folder, C:\Bentley\AutoPIPE V8i SELECTseries\
3. Locate the following file "PCFout.map"
4. Open this file in any text editor (i.e. notepad)
5. Go down to line 41, see the following:

ANC SUPPORT 01AN

6. Change "01AN" to "ANCH", should look like:

ANC SUPPORT ANCH

7. Save the file.
8. Open AutoPIPE, run an analysis, process a new stress iso.
The problem should be solved.

15. Cannot be resolved:

If the problem still persists and cannot be resolved by the above suggestions complete the following:
=================================
a. Create a new folder on the Desktop
b. Copy the model's DAT file to the new folder
c. Start AutoPIPE & open the file from the new folder location
d. Run the analysis
e. Create a Stress iso DXF file
f. If the warning in #2 above appears, select OK button
g. Close AutoPIPE
h. Zip all the files in the new folder on the desk top
i. Zip all the files in the following location:

"C:\Bentley \AutoPIPE V8i SELECTseries \PISOGEN \PROJECTS \APIPEPROJ \FINAL"

j. Include the following files from the AutoPIPE application folder. "C:\Bentley \AutoPIPE V8i SELECTseries\:

_____ - i. Stressiso.ini
_____ - ii. Apipe.opl

k. Create a service ticket at:http://appsnet.bentley.com/srmanager/addcall.aspx

Attach both Zip files to the service ticket and submit for review.

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!

Topics under the heading should be based on:

StressISO

1. Review the following file installed with AutoPIPE (search hard drive):
   
   C:\ Bentley \AutoPIPE V8i SELECTseries \StressISO_Troubleshooting.pdf

2. Stress Iso Troubleshooting Tips for AutoPIPE ( in addtion to the above)

3. StressISOs (Trunnions)

4. Stress Iso Export: There were some warnings and/or errors while executing ISOGEN.

PDS Stress Analysis Interface

PD_Stress -> PDS model neutral file (*.n) -> STRAIT -> AutoPIPE model neutral file (*.ntl) -> AutoPIPE program -> AutoPIPE model file (*.dat)

Download the following avi to view this process.

STRAIT product brochure

Intergraph PDS configuration files required to export a model to Bentley STRAIT translator.

Import and export of piping models between CAD and AutoPIPE can save man hours in the creation and checking of piping and structural models and prevent errors associated with manual entry of piping models.

AutoPIPE can directly import CAD piping models from AutoPLANT (PXF, with additional PXD & PXH data), AutoPLANT Designer/Isometrics, ProPIPE, Caesar II Neutral (CII), and Aveva PDMS (CII).  In addition, AutoPIPE can import structural steel models from Bentley STAAD and Multi-Steel; if the Multi-Steel model is composed of AISC structural elements in order to consider mass and flexibilities of structural supports as part of the piping analysis. 

In addition, Bentley's CAE development team has produced a number of translators to convert other well known CAD system files to be opened by AutoPIPE. Please see the list of translators that are installed with Bentley AutoPIPE V8i 9.1.1.2 and higher:

1. PCF to AutoPIPE

current version v1.0.0.32, Aug  2013

The PCF translator will translate SmartPlant, Autodesk Inventor, CADWorx, Solidworks, Catia and Medusa PCF file formats. SmartPlant does have a richer data format which supports component stress attributes like: pressure, temperature, pipe weight, insulation etc. The PCF files generated by the other products mentioned only support geometry coordinates and nominal pipe size. We have found several 3rd party applications like Autodesk Inventor may not write a valid PCF files and the PCF translator will do the best conversion it can, but in these cases Autodesk would have to improve the quality of their exported PCF file.

This translator will only work with the PCF file created from one the multiple applications listed above. You may need to contact the application technical support to get a step by step procedure to create a PCF file. Some may even need a software add-on installed (like Solidworks needs an add-on called Routing that allows the user to model piping routes, which can then be transferred to AutoPIPE).

2.  ADLPipe to AutoPIPE

current version v.1.0.0.14, Aug 2013

 ADLPipe Pipe stress program used primarily in the nuclear power industry, converts ADL PIPE models to an *.ntl file format to be opened by AutoPIPE. Originally released in 1967, ADLPipe was the first commercially available piping analysis program and was bought by Bentley in 2008.

3. Intergraph PDS to STRAIT to AutoPIPE 

current version v.6.0.0.13, Aug 2013

PDS is a comprehensive, intelligent computer-aided design/engineering (CAD/CAE) application for plant design, construction, and operations. There is some configuration.

With any PDS setup there is usually an amount of custom configuration of CAD components. The user is also required to  install 2 PDS configuration files on the PDS side to generate a readable PDS stress neutral file. Therefore any out-of-box solution may not work the first time. Since Intergraph PDS has typically a high level of customization we recommend translating a few PDS models for you first to help configure the component mapping. PDS Stress Analysis Interface:

(PD_Stress -> PDS model neutral file (*.n) -> STRAIT -> AutoPIPE model neutral file (*.ntl) -> AutoPIPE program -> AutoPIPE model file (*.dat)

These translators will be installed to the following folder:.

C:\bentley\AutoPIPE Translators

\ADLPipe Translator

\PCF Translator

\STRAIT

Attention: If you had not installed AutoPIPE V8i 9.1.1.2 or higher and would still like to have the translators, please log a service request asking for the respective translator.

All translators have a reference manual included with-in each zip / installation folder for further details information.

If you encounter any problems or have some comments, please report them back to use so we may continue to provide the best possible solutions for our users, such as yourself. Please create a service ticket at http://appsnet.bentley.com/srmanager/addcall.aspx

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!

The following section will cover general questions about AutoPIPE's results based on Loads and Load Sets that are NOT answered by Piping Code calculations

1. Question: noticed that results for all thermal analysis are the same, no mater what temperature setting is entered:
   
   Answer:
   
   Thermal expansion coefficient at ambient temperature is entered in the pipe properties screen or grid ONLY. Units for that coefficient "alpha" is 1.0E-6 in/in/degF or 1.0E-6mm/mm/degC

   The expansion rate for each operating case is entered on the OPerating Pressure & Temperature data screen or Press/Temp/PipID tab of the input grid as shown below:
   
   
   
   
   
   
   The expansion rate is defined as:

           Expansion = MeanAlpha*DeltaT = MeanAlpha*(OperatingTemperature - AmbientTemperature)

   In this equation MeanAlpha is the average alpha between Ambient and Operating temperature

   The units for this is in/100ft or mm/m  (no temperature units since temperature is already multiplied).

   If you enter a standard material like CS or a SPEC material like A106-A on the pipe properties dialog, the expansion data will be filled up automatically based on temperature (note: check box in from of data is enabled, checked ON). Only when you enter NS (Non-Standard) as the material, expansion data will not be computed and needs to be manually entered (note: check box in front of data is disabled, checked OFF). AutoPIPE expansion data is based on code expansion data table (in/100 ft) and not on alpha table. The alpha table might give slightly different results.

   You can override calculated expansion and enter your own values if you wish by disabling (check OFF) the check box in front of the data, then enter your own value (note the value units when entering data).

   In addition, various material libraries are now provided with AutoPIPE where the material library can be edited and  compiled to add or modify expansion data.

   In this case above, the model had T2, T3, and T4 where the expansion values are all the same. Therefore the thermal displacement would be all the same regardless of temperature settings because Auto check box was found disabled (checked OFF). Solution, manually update the data with the correct values, OR enable (check ON) Auto box in front of the expansion values, OR change the pipe properties material to a listed values other than NS.

2.  Question: AutoPIPE: different Results w/same input. 2 separate models with identical input or single model with identical loadcases / analysis sets In both cases the results are different

   TR Number:
   Product: AutoPIPE
   Version: 09.04.00.19
   Area: General
   Problem ID#: 71085
   
   Answer:
   
   Check the model output reports to verify input is identical.

   Steps to repeat:
   ======================================================================
   Comparing 2 AutoPIPE models
   ======================================================================
   1. Start AutoPIPE with a valid license.

   2. Open model DAT

   3. Analyze the system, Analyze> Analyze all.

   4. After the analysis is completed, create a complete output report; Results> Output report> Check all sub reports ON.

   5. Perform steps 2-4 for both models.

   6. Use a program like "Beyond compare" or "Ultra Compare" to compare
   the files. This will quickly highlight and differences between the models.

   Note: take extra care to be sure that all Analysis summary settings are exactly the same (Tools> Model Option> General, Edit, Results, Burried Pipe Options, etc..). In addition for comparsion purpose only, set Tools> Model Options> Results> Sustain Margin (Y/N/E) = N. This setting will affect the allowable calculation.

   7. Expect to find different time stamps and maybe some info that may be out of sync. However, everthing else should be identical.

   8. Fix any differences between models until they are identical
   and then run an anlysis to compare results.

   9. If the models still produce different results, add both model DAT & supporting files to run the analysis in a ZIP file, and send to Tech support for review. Also, include the OUT files used to compare these models.

   ======================================================================
   AutoPIPE Model with similar analysis sets.
   ======================================================================

   1. Start AutoPIPE with a valid license.

   2. Open model DAT file

   3. Analyze the system, Analyze> Analyze all.

   4. After the analysis is completed, create a complete output report; Results> Output report> Check all sub reports ON.

   5. Open the model's input grid, select the Press/Temp/PipeID tab
   copy the entire grid to excell, Use Excell to compare each Temp/Press loadcase to confirm identical settings (could have different Press, Temp, Expansion, Hot Mod,Hot Allow, or Yield values).

   6. Review model listing to confirm no addtional Xtra Data is assigned to a loadcase (i.e. Force, distributed load, concentrated force, cut short, etc..)

   7. If the model still produce different results, create a service ticket using this information  and send for review.

3.  Question: AutoPIPE: Diff GR load in analysis set

   Model has 2 different analysis sets, but the support loads dues to GR(1) and Gr(2) are different, why?

   TR Number: none
   Product: AutoPIPE
   Version: 09.04 and higher
   Area: General
   Problem ID#: 91549
   
   Answer:
   
   The different results from Gravity(1) load case in Analysis set 1 and Gravity(2) in analysis set 2 can be related to Pressure stiffness and Hot Modulus settings in the respective analysis set. Review both analysis sets to be sure same settings exist.

   Pressure Stiffening:
   Select the pressure stiffening case used for the analysis set. Pressure stiffening will change bend flexibility and stress intensification factors for all load cases in the analysis set including the gravity case.

   Hot Modulus:
   Select the hot modulus case used for the analysis set. The hot modulus will affect the element stiffness and calculated displacements and would apply to all load cases including the gravity case.

4.  

5.  

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!

Comments, Questions, and Answers 

1. Question: I am trying to verify pressure extension result in AutoPIPE 09.04.01.05 using hand calculation. Could you please provide the formulas used in AutoPIPE for pressure elongation of a straight pipe (assuming pipe is free to expand). I am using ASME B31.3 and CSA Z662 codes.Model has 2 different analysis sets, but the support loads dues to GR(1) and Gr(2) are different, why?
   
   Answer:
   
   Go through the following link:
   
   http://communities.bentley.com/products/pipe_stress_analysis/f/275801/p/40611/89583.aspx#89583
   
   AutoPIPE uses thick wall formula for calculation of pressure extension. A screen capture below:
   
   

Topics under the heading should be based on:

Load Combinations, Stress Summaries, Results, Floating Results Dialog, etc..

1.  Floating Results Dialog

Comments, Questions and Answers

1. Question:
   
   AutoPipe Results> Code stresses floating dialog shows the Max Expansion Stress to be 4785 psi on the screen however, the report shows 2 stresses (+ /- side) for that node point, one of which has a higher stress of 5004 psi ?
   
   Answer:
   
   The CAE development team has confirmed there is a problem on the floating results dialog for displaying the highest value stress between +/- side (up stream / Down stream) of a node point for bend mid point . This is only repeatable if a beam is connected to a bend mid point. The output report and results grids are correct.
   This has been loged under CAE-TR-11039.
   

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!

Attention: Please see the following AutoPIPE help section:
Help > Contents> Contents Tab> Modeling Approaches> Modeling Approaches>

This help has been provided in order to give users ideas for modeling typical piping arrangements. The steps shown in each example should not be taken as the only method available to create models. In addition, the intent of the examples is to present ways to create adequate models of specific piping components for analytical purposes.

          Anchors        Bends
          Cuts              Flexible Joints
          Frames         Hangers
          Nozzles        Pipes
          Reducers      Rotating Equipment
          Supports       Tees
          Valves           Vessels

Comments, Questions, and Answers:

1.  How to model a 3-way valve?
   
   Answer:

   Inputting three way valves in AutoPIPE is a bit convoluted at this time. AutoPIPE does not allow users to branch from a valve, see the following procedure:

   1. Divide the valve into 3 pieces, length and weight divided, and input them as separate valves,
   2. Put very short dummy runs of rigid pipe (select "rigid" as pipe data identifier) in between the valves and at the branch.
   3. Convert the run points to a Tee using the "convert run to tee" icon/button. See below what it should look like:

2. Valve Pressure rating dropdown list only shows NS (Non-Standrd)
   
   Answer: Per the screen shot below, left Valve dialog is on 8" pipe, right Valve is on a 60 inch pipe. Note the image has only NS for Pipe Rating. the reason is because the pipe size is beyond that found in the current equipment library. Therefore only option available is to select a Pressure Rating = NS, and manually update the valve lengtb.  
   
   

3.  

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!

Click HERE for Bentley STRAIT product Brochure.

The STRAIT Translator program is required to convert a Intergraph PDS 3D piping model to AutoPIPE. This includes geometry, pipe sizes, wall thickness, materials, insulation, supports, valves, flanges, weights etc. The STRAIT Translator is provided, at no charge when AutoPIPE V8i is installed. This application requires a little effort in setting up. This process usually takes about 2-3 iterations to make modifications to the companies PDS Custom configuration and/or STRAIT mapping, since every company has their own unique PDS customization.

To name a few companies that are saving time and money using this application to convert files from PDS to AutoPIPE:

Conversion process:

PDS Stress Analysis Interface

PD_Stress -> PDS model neutral file (*.n) -> STRAIT -> AutoPIPE model neutral file (*.ntl) -> AutoPIPE program -> AutoPIPE model file (*.dat)

Download the following avi to view this process:  click here

We have found in the past if we send the STRAIT software to users to evaluate, very soon they come back and insist it does not work and do not pursue the Bentley software product. This is why we prefer to translate several of your PDS models to AutoPIPE, let you review the translated AutoPIPE model vs. the original PDS model to give confidence in the accuracy and completeness of the stress model, and then send all the completed configuration files..

As mentioned, with any PDS setup there is usually an amount of custom configuration of CAD components. Therefore any out-of-box solution may not work the first time. We would suggest:

Download and install STRAIT:

STRAIT is now bundled with Bentley AutoPIPE download and installation. Please follow the procedure to download and install the current version of Bentley AutoPIPE. AFter installation

Generate a PDS model neutral file:

1. First make sure that the Intergraph PDS pipe stress extraction module is installed. Intergraph calls it PD_STRESS or a similar name. Many PDS users have not even installed this module which comes standard with PDS.

2. Select an example PDS model that you would like to extract. Make sure that it has gone through a consistency check good enough to extract an Isometric.

3. The name of the Intergraph defaults file is DEFAULTS.DAT. Do not use defaults.dat, but instead use the attacheddefstr.dat and strmap.tbl files
   
   NOTE: Ensure the following path in the DEFSTR.DAT file points correctly to the STRMAP.TBL
   c:\win32app\ingr\pdstress\dat\strmap.tbl !PDS TO STRESS MAP [modify path as necessary]

4. Once the .n file has been created, load it into the STRAIT program.
   
   NOTE: Please note that there is a facility within Intergraph PDS which allows users to assign a stress ID to an entire system for extraction of pipe stress neutral files as an alternative to extracting 1 line at a time. The documentation still shows information on the old DOS STRAIT version but the options are all the same.

Typical detailed procedure to Create PDS stress neutral file either by line number or Stress_system_no. AFTER the configuration above hass been completed.

1. Revise segment data
   
   
2. Define Active Group…search criteria…fluid code …
   
   
3. Identify reference point and data any point in the model…and accept it will highlight the piping in the active group defined
   
   
   
4. Toggle brief segment data to see the complete segment data list and revise the stress_system_no 
   
   
5. On PD shell - pick Pipe Stress Analysis
   
   
   
   
6. Fill in model name and stress_system_no under pipeline names
   Note: The pipeline names = line number  if word 12 = 0 or 2  in defstr.dat
   
   
7. .n file will be created in the stress output node path

Convert a PDS file to AutoPIPE file format:

1. Start STRAIT, select Browse button, locate the systemname.N file created from PDS and select the Open button.

2. Press the edit button to modify the configuration settings, press OK button to get back to the main screen.

3. Press the Convert button to start the conversion process. You should see the conversion status screen scrolling and then after a short time, stop scrolling.

4. If all the configuration files and settings were correct, you should see: Neutral File Successfully Processed. (If not, more modifications to the configuration files and / or settings is required).

5. When successfully converted, an AutoPIPE model neutral file (systemname.NTL) is created in the STRAIT folder or designated folder..

6. Copy the systemname.NTL file to a new folder for your AutoPIPE models.

7. Open AutoPIPE, select File> Open> AutoPIPE Batch (.NTL), locate your newly created systemname.NTL file, press Open button.

8. The model should now appear.

9. Select File> Save, this will generate the AutoPIPE model file (systemname.DAT).

 LIMITATIONS:

1. Cannot create PDS stress neutral file for disconnected lines

2. Component limit of 800 which is roughly 800 nodes as well.

3. Unknown components mapped to pipe ID = RIGID

4. Possible disconnects in PDS model = unstable system in AutoPIPE 

5. Mapping a dummy leg to a frame cannot be done.

6. Mapping a hanger to a tie rod is not possible to map to a tie-rod since it must have a connected to point instead of ground.

7. Line numbers - 14 characters can be used mix of alpha-numeric and numeric.

TroubleShooting Bentley STRAIT

Select the following link for TroubleShooting Bentley STRAIT issues

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!

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!

Problem:

How to export a file from Prstructures to AutoPIPE

Answer:

Please see the following web site to export a model from ProStructures to ISM then to STAAD.Pro:

http://communities.bentley.com/products/structural/w/structural__wiki/modeling-and-node-generation-best-practices.aspx

Then see AutoPIPE example folder for details on exporting a file from STAAD Pro to AutoPIPE:

C:\ Bentley\ AutoPIPE V8i SELECTseries \ Examples\ PIPELINK_tutorial.pdf

(above file is installed with each installation of AutoPIPE, or search your hard drive for  "PIPELINK_tutorial.pdf")

Additional Comments:

1. Instructions on flipping the Auto / Open Plant model to match ISM are copied below. Note the transform switch was added to APIPE V9.6.x.x SS5.
   
   

2.  

    

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!

Try to do:

Load ->Dynamic Analysis -> Maximum number of modes (enter mode shapes number you need)

Problem:

Where can I dind information about the different versions of the AutoPIPE PCF translator?

Answer:

The following file is copied to the location when installing the application:

C:\ Bentley\ AutoPIPE Translators\ PCF Translator\ README.txt

Excerpt from the above file:

This enclosure contains a Software Tool for converting SmartPlant, CADWorx,
Autodesk Inventor, SolidWorks PCF Models into an AutoPIPE Batch Neutral File (*.NTL)
which can be automatically saved as *.DAT file and opened in AutoPIPE. Bentley and
Users have performed testing on a number of test models and found good
translation results. Any translation issues found please send to support@bentley.com ,
subject “AutoPIPE” and we will fix and issue a patch for this translator in a timely
manner.

1.0.0.6

   Following Fixes/Changes were made.
   1. Flange rating e.g. CL300 was not being set in the NTL, even though mapping defined in PCFin.map
   2. Flanges were placed separate instead of mating
   3. Vent pipe created in same segment as the header instead of a new segment

1.0.0.7

   1. Point ID for disconnected components was not setup correctly

1.0.0.8

   1. File Opening issue fixed  if the folder name has ".pcf" in it
   2. Olet at branch is always treated as a new segment
   3. Zero Length Pipe are skipped and not written to ntl
   4. Modified Support Mapping "01HG" to "GUID"
   5. Added Component mapping of "UNION" to "PIPE"
   6. Added [UNITS-COORDINATES] mapping of MM-HUNDREDTHS To "30480"

1.0.0.9

   1. Loop between two components detected and hang issue fixed

1.0.0.10

   1. Added command line support (batch processing)
   2. Bend radius clearance issue resolved (round off problem)
   3. Negative OD is handled. Now translator takes an absolute of the OD value.

1.0.0.11

   1. Added Component mapping of "FILTER “to "PIPE"
   2. Piping Code, Material Library and Component Library dropdowns added
   3. Pressure rating is being searched from ITEM-DESCRIPTION; in previous version pressure ratting was
fetched from 2nd position of comma separated ITEM-DESCRIPTION

1.0.0.12

   1. Zero length components are ignored

1.0.0.13

   1. Default material library
   2. A new drop down list to select a version of AutoPIPE installed to open the translated file
   3. Multiple PCF files selection for translation in one go
   4. Bug Fixed: There was problem reading Outside diameter for OLets
   5. Shortcut is created under a new program group Programs> Bentley AutoPIPE Translators > SmartPlant Translator

1.0.0.14

   1. Pipe schedule mapping table added to pcfin.map
   2. Search ITEM DESCRIPTION for a matching schedule with the mapping table. If no match found then use default schedule in the table

1.0.0.15

   1. Added support to ignore tab characters to solve issues with reading pcf files containing tab characters

1.0.0.16

   1. Fixed issue with pressure value in the NTL card which was not exported on correct position. This could result in incorrect value of
pressure imported to AutoPIPE if the value is greater then 99.

1.0.0.17

   1. Fixed wrong pipe and material assignment to run points following bends
   2. Change application name from Smart Pant Translator to PCF Translator.
   3. Search flange rating in ITEM-Code description as well if no rating found in ITEM-DESCRIPTION

1.0.0.18

   1. Fixed supports import problem introduced in ver 1.0.0.12 onwards

1.0.0.19

   1. Introduced some tolerance in coordinates while connecting components in a line

1.0.0.20
   1. Improved bend radius calculation routine to calculate radius using both near, far points of elbow and use the minimum radius of the two

1.0.0.21

   1. Add support to read UCI(Universal Component Identifier ) from each component and write in NTL as UUID tag.

1.0.0.22

   1. Connect disconnected segments if the gap is less than/ equal to tolerance value
   2. Tolerance can be changed from PCFIN.MAP file

1.0.0.23

   1. Add support to import Line Number and Line Class

1.0.0.24

   1. Fixed issues with connection tolerance
   2. Added support to import Flex Joint Component
   3. Retain PXF/PCF flange length
   4. Added support to import cross component

 
1.0.0.25

   1. Fixed unit converion problem in PCF connection tolerance
   2. Fixed an inaccurate distance calculation problem between 2 points

1.0.0.26

   1. Ignore duplicate components while generating NTL file.
   2. Added support to detect overlapping components and notify the user that NTL conversion aborted due to overlapping components.

1.0.0.27

   1. Move PCF Translator business logic into separate Dll

1.0.0.28

   1. #10056 Add feature to batch process multiple PCF files into one DAT file.
       a) Added support to convert multiple PCF files of same unit system into one DAT model.
       b) If multiple PCF files are selected and the unit system of selected PCF files are different then program will show a report which contains file name , units-bore, units cords and units weight.

1.0.0.29

   1. #10791 PCF Translator: Temperature is incorrectly imported
   2. #10792 PCF Translator: Corrosion allowance is not imported from PCF file.
   3. #10793 PCF Translator: Wrong values of insul. density & specific gravity are imported.
   4. #10794 PCF Translator: Pipe schedule is not imported from PCF file.
   5. #10835 PCF Translator: Program does not import support whose SKEY is ANCH.
   6. #10854 PCF Translator: Fetch material from Item Code > Description.
   7. #10856 PCF Import: segment connectivity issues with >1 incoming pipes.
   8. PCF Translator: Add an option to ignore continuation components.

1.0.0.30

   1. #10862 PCF Translator: Add an option to ignore continuation components.
   2. #10866 PCF Translator:Overlapping comp. report should be displayed at the end on dialog.

1.0.0.31

   1. #10882 PCF Translator: Add an option to ignore overlapping components.
   2. Add support to define PCF to AutoPIPE coordinates mapping.
   3. #10887 PCF Translator: Move Toler., flange length, Ignore options to Tools>Setting dlg

1.0.0.32

   1. #10056 Add feature to batch process multiple PCF files into one DAT file.
   2. #10938 PCF Translator: Add support to fetch pipe size (OD) if specified in fraction

1.0.0.33

   1. #11014 PCF Translator: Point names of 4 characters may cause import to fail

1.0.0.34

  1. #11048 PCF Translator: Program should remove overlapping part of a component. 

 We have added a new option to remove the overlapping part of a component. This option is by default on. The option to ignore overlapping component and remove part of component are naturally exclusive of each other so if one is enabled, other becomes disabled.

User is also warned of the affect in the log as shown below.

Note: Please make sure that you uninstall your previous PCF Translator before installing this - as this installer detects if PCFIn.map file is modified on your machine and then it does not replace/update it.

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!

CAE Development team logged issues about PCF translator

____1. CAE-TR- 4814:

Incorrect default keywords for STRAIT & PCF options in autopipe.ini file:

Description:  The keywords for the STRAIT and PCF options are incorrectly listed as 'UserStrait' and 'UserPCF'. They should be 'UseStrait' and 'UsePCF'. The problem was caused by a typographical error in the case where the autopipe.ini file does not exists initially and the program creates the autopipe.ini file. The file should be updated with corrected information.
Corrected Version:  8.5.1.9

____2. CAE-TR-8989:

pcfout.map file needs update to include additional valve end connections:

Description:  The pcfout.map file needs to be updated to include additional valve end connections.
Corrected Version:  9.3.0.5

____3. CAE-TR-10304:

All Import PCF menu options should open individual help page.:

Description:  “F1” key is invoking the same help page for the Import-> SmartPlant, CADWorx, SolidWorks, Autodesk Inventor, CATIA, and the new Autodesk Plant 3D menu commands. It should open separate help page for each menu option
Corrected Version:  9.5.0.15

____4. CAE-TR-10358:

PCF Translator: Program crashes when import PCF file:

Description:  When import PCF file translator crashes. PCF file is attached for testing.
Corrected Version:  1.0.0.25

____5. CAE-TR-10611:

PCF Translator: Program should ignore sign of Thickness:

Description:  PCF file is not imported if “COMPONENT-ATTRIBUTE4” (Thickness) is negative in PCF file. So program should ignore sign of thickness.
Corrected Version:  9.6.0.1

____6. CAE-TR-10616:

PCF Translator imports API code as flange rating instead of actual flange class

Description:  PCF Translator: Importing API code as flange rating vs actual flange class

ITEM-DESCRIPTION Gate Valve B16.34/API 600 A851 Gr CF8M Flange CL 150 RF B16.47/A bolted bonn

Imports flange with rating 600 instead of actual i.e. 150.
Corrected Version:  <<None>>

____7. CAE-TR-10730:

PCF Translator crashes when first component length is less than Tolerance

Description:  During PCF Import, translator crashes if first component length in PCF file is less than tolerance.
Corrected Version:  1.0.0.28

____8. CAE-TR-10781:

PCF Translator: Extract useful information from the component-attribute data

Description:  PCF component data has “COMPONENT-ATTRIBUTE” used for describing the information like temperature, pressure, material etc.
Previously translator read the whole value and assigns it. Now translator has to extract the useful value from the complete string like “A106-B” from “BOMCOLUMN_Material_A106-B” string
Corrected Version:  <<None>>

____9. CAE-TR-10791:

PCF Translator: Temperature is incorrectly imported if specified in deg C

Description:  In PCF file if temperature is specified in Celsius (degree C) then it is not imported correctly in both English and Metric units.
Corrected Version:  1.0.0.28

____10. CAE-TR-10792:

PCF Translator: Corrosion allowance is not imported from PCF file.

Description:  During PCF import corrosion allowance is not imported from PCF file if wall thickness (Component-Attribute4) is not defined in PCF file.
Corrected Version:  1.0.0.28

____11. CAE-TR-10793:

PCF Translator: Wrong values of insul. density & specific gravity are imported.

Description:  Wrong density “kg/m^3” factor for metric unit system is defined in pcfin.map file due to which wrong values of insulation density and specific gravity are imported.
Avoidance: Manually update PCFin.map file, Unit Distance Section; change kg/m^3  1, to kg/m^3   16.018464.
Corrected Version:  1.0.0.28

____12. CAE-TR-10794:

PCF Translator: Pipe schedule is not imported from PCF file.

Description:  During PCF import if pipe schedule is defined in PCF file then then the defined pipe schedule is not imported, only STD pipe schedule is imported.
Avoidance: Manually update PCFin.map file, Schedule section, example add new line SCH 40 (1st col.) and S40S (2nd col).
Corrected Version:  1.0.0.28

___13. CAE-CR-10862

PCF Translator: Add an option to ignore continuation components.

Description:  PCF Translator should ignore all those components which are continuation to other pipeline.
User has an option to turn it OFF/ON from PCFIN.MAP file.
The continuation component has been identified by the CONTINUTION keyword.

Corrected Version:  9.6.0.7
Product Version:  1.0.0.29

__14. CAE-CR-10886

PCF Translator: Add support to define axis mapping between PCF and program

Description:  Implement feature in PCF Translator to select different axis orientation for incoming PCF files and also select on which application axis to map i.e. (+ X  Y vertical) or (+Y Z vertical).

Different options to select for incoming PCF files are
1.    +Y_NORTH
2.    -Y_SOUTH
3.    +X_EAST
4.    -X_WEST

Corrected Version:  <<None>>

__15. CAE-CR-10854

PCF Translator: Fetch material from Item Code > Description.

Description:  PCF Translator should be able to fetch material from Item code > description in case material is not specified in Attribute3 in PCF file.

Corrected Version:  9.6.0.7
Product Version:  1.0.0.28

__16. CAE-CR-10855

PCF Translator: Add new piping codes, Material and Component libraries.

Description:  Add new Piping codes, Materials and Component libraries in PCF Translator to make it consistent with AutoPIPE

Corrected Version:  9.6.0.7
Product Version:  1.0.0.29

__17. CAE-CR-10882

PCF Translator: Add an option to ignore overlapping components.

Description:  PCF Translator should ignore the second overlapping component. User has an option to turn it OFF/ON from PCFIN.MAP file.

Corrected Version:  <<None>>

__18. CAE-CR-10887

PCF Translator: Move Toler., flange length, Ignore options to Tools>Setting dlg

Description:  Move the following options to Tools > Settings dialog, so the that user can easily change these settings from GUI instead of changing these settings manually in map file.
1. Tolerance
2. Retain Flange Length
3. Ignore Continuation Components
4. Ignore Overlapping Components

Corrected Version:  <<None>>

Update: July 18, 2013:

This is directly related to the issue when the following is displayed on the translator dialog during cthe conversion process.

*** Import process aborted due to overlapping components ***
Conversion Aborted..

The CAE development team implemented detection and blocking of overlapping components as they may cause issues during import. Some models do import in AutoPIPE where as some hang. Even for the ones that import ok - the issue is that there will still be overlapping pipes which may not be correct. PCF Translator generates a log of all overlapping components to help identify to the user their location and number of occurrence. These log files are located in the same folder as the PCF file. This log file is named .log3.

The default behavior is to block the import and let the user review and correct the model in the original software that was used to create the file. However, if the user wishes to still import the model without making changes, we now have an option to ignore overlapping components during import. What this option does is that it ignores any new component that overlaps an existing component. This is still in BETA phase and is scheduled to be included with AutoPIPE 9.6 (release Q3 2013). If you are interested in the BETA version please log a service request mentioning this CAE number, requesting a BETA PCF translator.

If you do use the PCF translator, it is at your own risk. In addition to a complete model review, minimize the number of Model Consistency Check, and Design Checks before running the analysis.

__19. CAE-CR-10936

PCF Translator: ability to import beam / frame

Description:  PCF Translator, add ability to import beam / frame into model.

True nature of the problem is that most software applications do not support exporting beam information when creating a PCF file. AutoPIPE is only able to import information that is actually in the PCF file. When the information is made available in the file, the CAE development team will incorporate this enhancement.

Corrected Version:  <<None>>

Topics under the heading should be based on:

PCF SmartPlant Translator Issues

Note: PCF file does not store Pressure or Temperature settings, to be sure library data is retrieved for pipe properties, thermal expansion, hot modulus, hot allowable, etc, after importing a model suggest the following steps: select Tools> Model Options> General change Ambient temperature to a different setting, press OK button, after the model data has been refreshed, reset Ambient temperature back to the original setting.

1. AutoPipe No graphical elements found for the components after Importing sample DGN file [TN]

2. AutoPIPE: PCF Translator FAQ & Troubleshooting

3. Imported NTL Errors from PCF Translated File

4. PCF Translator Logged Issues

5. PCF Translator Version and Features