| Applies To | |||
| Product(s): | AutoPIPE | ||
| Version(s): | All | ||
| Area: | Import | ||
| Original Author: | Bentley Technical Support Group | ||
| Date Logged & Current Version | April. 2015 09.06.01.11 |
Problem:
When importing a model created with branch connection O-let / olet (weldolet, elbolet, threadolet, etc..) component into AutoPIPE, the AutoPIPE model is not created correctly or not at all. Why and how to avoid?
Solution:
Add Olet and disconnected branches handling
PCF translator 1.0.0.40 and higher now supports OLET components that are connected to PIPE components. With three limitation:
1. OLET component must be located within the radius of the header pipe size. Otherwise it will not be automatically connected. In addition,
2. Because the PCF format does not explicitly describe an OLET component, All OLET components are mapped to tee type = WELDED and must be manually updated as needed with in AutoPIPE after being imported (check fr updates).
3. AutoPIPE (Dec 2018) cannot model OLET components connected directly to a BEND component, see AutoPIPE help Modeling Approaches to model pipe connections to elbows.
PCF translator 1.0.0.39 and lower:
AutoPIPE does not support OLETs, there is only TEEs to represent OLETs.
We are working on a version of PCF Translator that supports OLETs. First part of this update is complete and we are testing it with more models to see if we find any issue. One issue we found is the inconsistency among different systems writing PCF files. Some systems have OLET connecting at the centerline of the pipe - where as some systems have OLETs connecting at surface of the pipeline. We have dealt with the first case and looking at the second one now.
Please file a Support request and attach your files so we have more example models to test with.
See Also
06. Branch piping is not connected to the main header pipe in converted AutoPIPE PCF file, why?
PCF Translator FAQ & troubleshooting