![]()
| | | |
| Applies To | | |
| | | |
| Product(s): | AutoPIPE, | |
| Version(s): | 2004, XM, & V8i | |
| Environment: | N/A | |
| Area: | import | |
| Subarea: | | |
| Original Author: | Bentley Technical Support Group | |
| | | |
Comments, Questions, and Answers with PCF translator into AutoPIPE:
Note:
Each AutoPIPE translator is installed with a complete manual about the application. See the following file for more details about the translator program:
C:\Bentley\AutoPIPE Translators\PCF Translator \ SmartPlantToAutoPIPETranslator_UserReference.pdf
Issue #1:
PCF conversion worked, but when Import the converted NTL file into AutoPIPE the process aborted: what should I do?
Answer:
See the following link:
http://communities.bentley.com/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/7642.aspx
Issue #2:
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?
Answer: 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 #3
Q. When trying to convert a file from PCF to NTL, the converter freezes at “Parsing complete…” it never creates the NTL file.
Answer: 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 #4
Q. Program does not import a PCF file and hangs with no error message.
Answer: 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.
Another common problem is that the "Description" is too long. Should only be max 60 characters
Example:
DESCRIPTION SUPPORT: Rigid Rod with Double Bolt Clamp, Top Type: WELDED BEAM ATTACH, Rod: Cont. Thread, 3/8 $ *PART:Anvil FIG295 1 1/2 in Double Bolt Pipe Clamp, Finish: Black $ *PART:Anvil FIG290 3/8 in Weldless Eye Nut, Finish: Black $ *PART:Anvil FIG146 3/8 in Continuous Threaded Rod, Length: 77.75 in, Finish: Black $ *PART:Anvil 3/8 in Standard Hex Nut $ *PART:Anvil FIG66 3/8 in Welded Beam Attachment (Connect to Bolt), Finish: Black $ *PART:Anvil FIG290 3/8 in Weldless Eye Nut, Finish: Black $
Avoidance: reduce description to smaller size, i.e.:
DESCRIPTION SUPPORT: Rigid Rod with Double Bolt Clamp,
Issue #5
Q. When trying to convert a file from PCF to NTL, the converter freezes / aborts and it never creates the NTL file, why?
Answer: 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 #6
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".
Answer: 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 #7
Q. After importing a file into AutoPIPE the components were all found to be missing on a computer with dual monitors and intergrated graphics processor.
Answer: See the following WIKI page.
No graphical elements found for the components after importing file into AutoPIPE
Issue #8
Q. Branch piping is not connected to the main header pipe on converted PCF file. As seen in the following screen shot, Group 5 (segments F-G) are not connected to the main header of Group 4 (segment D-E). Otherwise it would be a single group.
![]()
How to fix this problem?
Answer: This issue appears to be a modeling problem in the program that created the PCF file. After reviewing the node point coordinates in the original PCF file to be translated, it was determined that there are no points specified on the header pipe for a tee connection.
Fix the problem by reviewing the original file in the application that created the PCF file to be sure that the piping is correctly connected.
Issue #9
Q. When importing a PCF file, the single line view looks ok, but actually all the pipe sizes are very large, how to resolve?
![]()
Answer: The application ued to create the PCF file did not write the correct units. Example, open the PCF file in any text editor (i.e. Notepad, UltrEdit, ...). See the following component pipe size was found to be 25:
![]()
The units are found at the begining of the PCF file:
![]()
In this example, the units were found to be INCH. This created a pipe size 25.4x larger than the pipe should have been. To fix this issue, change "UNITS-BORE INCH" to "UNITS-BORE MM".
![]()
Issue #10
Q. When I open the .NTL file in AutoPIPE, it truncates my pressure values from 2735 to 735 (it omits the leading number). The values appear correct in the .NTL file if I open in a text editor. If I add a space in front of 2735 in the .NTL file, the number shows correctly when imported into AutoPIPE.
Answer: this is a known issue and was fixed in a new relase of the applicaiton, PCF translator v 01.00.00.36 (CAE-TR-11101
Issue #11
When running the PCF translator the following orccurs:
![]()
Bentley PCF Translator (Not Responding)
What shoudl I do?
Answer.When using the PCF translator, select the file to be converted, make additional changes to all the other settings as needed and press the Convert button.
After pressing the Convert Button, suggest that you remove your hands from the keyboard and mouse. The translator is using a significant amount of system resources to convert the file. Some files that are converted have over 100,000 lines in one file. By pressing a button on the keyboard or mousing over something system resources are taken away from translator. Sometimes when this happens the application will show the Not Responding message and become grayed out, as seen above. However the software is still trying to recover and complete the conversion process. Again, do not touch anything. Most of the time the application will complete the conversion, the PCF translator will no longer show the Not Responding message and you will be able to open the newly converted file in AutoPIPE.
No mater the size of the model, be patient and let the application complete the conversion before moving onto another task. Again, this application is sensitive to system resource allocation. Regardless, if the model is converted and can be opened by AutoPIPE, everything should be ok, continue working on your analysis in AutoPIPE.
IIf this issue occurs alot, you may consider adding more Ram or a beter CPU.
Also, if after an extreme amount of time, the Not repsonding messag is still visible, close the application, file a service request, and send Bentley the PCF file you are having troubles with for review.
Issue #12
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"
Q9 I cannot get the PCF translator to exectue from the command line (Batch Processing) as mentioned in online help info, why?
A9. This passage was not suppose to have been printed in the published documentation because this feature had neever been added to the program. This wae info was removed in the new version of the documentation.
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!