Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
Any piping gurus out there?
I have an existing assembly. Need to add a pipeline to it. No matter how I route this new pipeline, a fitting at the end of the previously existing pipeline somehow becomes a child of the new one, and loses it's references, leaving me with no choices other than suppress, delete or freeze. None of these are acceptable. I have never seen this before.
If I use the end of the existing pipeline as my start point,... it loses it's references... but not right away mind you.... later, after I've been working for a while. The same is true if I start the pipeline somewhere else, and route TO that point. This has caused me THREE times, to use the dreaded "Delete All Versions", and attemp to start over from scratch.
Please,... any ideas?If you create an assembly component whose first solid feature is the placement constraint, I found that in the past, Pro/E considers that a circular reference. In other words, if you assemble a newly created part by default coordinate systems, then make the first solid/nonDatum feature as a complete child of existing geometry, that is ok. But if you don't locate it first, and the location AND first solid/nonDatum feature is based off existing geometry, it considers that a foul. Need to locate, then create first feature.
You could also try to eliminate any chain-reactions of parent-child references and make them a single level deep. Instead of referencing the previous pipeline end, create a skeleton coordinate system in space and let the previous pipeline end and new pipeline end both reference that. Having a clear driver-driven relationship that is not concatenated more than one level should also make your models regenerate faster.
Hope that helps!
Akbar Husain
Any piping gurus out there?
I have an existing assembly. Need to add a pipeline to it. No matter how I route this new pipeline, a fitting at the end of the previously existing pipeline somehow becomes a child of the new one, and loses it's references, leaving me with no choices other than suppress, delete or freeze. None of these are acceptable. I have never seen this before.
If I use the end of the existing pipeline as my start point,... it loses it's references... but not right away mind you.... later, after I've been working for a while. The same is true if I start the pipeline somewhere else, and route TO that point. This has caused me THREE times, to use the dreaded "Delete All Versions", and attemp to start over from scratch.
Please,... any ideas?
Chris Benner
Designer II
Powell Fabrication & Manufacturing, Inc.
<u>www.powellfab.com
</u><u>P: 989-681-2158
</u><u>F: 989-681-5013
</u><u></u><u></u><u></u>
<u></u>