Quantcast
Channel: AutoPIPE
Viewing all articles
Browse latest Browse all 16073

Wiki Page: PCF Translator FAQ & troubleshooting - AutoPIPE

$
0
0
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? Issue #2: PCF Translator Freezes / Not Responding, now what should I do ? - AutoPIPE Issue #3: Import from Autodesk Inventor PCF files show flanges and valves as weightless “Zero Weight” components, why and how to avoid when using PCF translator in AutoPIPE? Issue #4: "E880-1: Error in opening import batch file. File extension must be NTL" message appear when importing a PCF fiule in AutoPIPE, why and how to avoid? Issue #5: No graphical elements found for the components after importing file into AutoPIPE with the PCF translator Issue #6: Branch piping is not connected to the main header pipe in converted AutoPIPE PCF file, why? Issue #7: When importing a PCF file, all the pipe sizes are very large in AutoPIPE, why and how to resolve? Issue #8: When I open the .NTL file in AutoPIPE, it truncates my pressure values, why and how to avoid? Issue #9: Isn't my piping code, material, and components supported in the AutoPIPE PCF translator? Issue #10: Imported PCF file containing branch connection O-let / olet (weldolet, elbolet, threadolet, etc..) are not connected correctly in AutoPIPE model, why and how to avoid? Issue #11: When importing a PCf file into AutoPIPE, Status = "Incorrect Component Connection Tolerance Value", why and how to avoid? 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 the 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!

Viewing all articles
Browse latest Browse all 16073

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>