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

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"