Skip to main content
lococnc1-Visitor
1-Visitor
February 15, 2011
Question

Transfer Parameter using Pub and Copy Geom?

  • February 15, 2011
  • 4 replies
  • 1977 views
Is it possible to move the value of a parameter using the publish and
copy geometry functions?

I have an assembly that uses a skeleton. A later part has copy geom
from the skeleton.

My problem is that I also have a parameter that gets set in the
Skeleton based on if-then statements.

I am using the execute and input functions in the assembly both belong
to. Problem is that it takes two regenerations for it to get the info
straight. I get a failure and then can regen again and it works. In
tracing it down for some reason it appears to do the "execute" first,
then regens the skeleton (at that point the parameter changes) then
the child part fails.
Very frustrating. I thought the first thing the assembly was supposed
to do was regen the skeleton?

On WF5 M160
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

4 replies

Anonymous
February 16, 2011
Michael,
I haven't looked into Pub & Copy Geoms, but perhaps using Post-Regen relations or assembly level relations would help. The following is from Advanced Part training on relations:

Order of Operations

Relations are not evaluated until the model is regenerated. During a regeneration, relations are evaluated in the following order:
1.

At the beginning of a regeneration, the system solves model relations in the order in which they were entered.
2. In an assembly, the assembly relations are calculated first. Then the system calculates all sub-assembly relations in order of component placement. This means that all sub-assembly relations are calculated before any features or components begin regeneration.
3. The system starts regenerating features in the order of creation. If a feature is attached to feature relations, these relations are solved before regenerating that feature.
4. If you specified any relations as Post Regeneration, the system solves these relations after the regeneration is complete.
Post Regeneration relations are accessed here:

HTH,


Karl Krahmer
Mechanisms and Structural Systems
ASRC Aerospace Corporation
Kennedy Space Center, Florida 32899
Mail code ASRC-5211
TimMcLellan12-Amethyst
12-Amethyst
February 16, 2011
As Karl points out Post Regen may help. It really depends on what your
if-then is driving in your skeleton as well as when/what you are publishing.



If you want or need to really fine tune and control the evaluations of
relations I would first try Karl's recommendation as a direct approach.
However, if you find that you are still getting multiple regenerations I
would look into placing "feature relations" in your skeleton exactly where
you want them evaluated. I have used this approach with some complex BMX
situations and it worked out great.



Keep in mind that you can create a feature such as a point, coordinate
system, or any feature to hold the feature relations you want evaluated at a
specific point in your model tree.



For example:

[FEATURE NAME]

Feature 1

Feature 2

FR-Feature 3 (This may be a place holder for your relation. I typically add
the prefix FR when I have a feature that contains a relation. FR-1's
feature relations are evaluated at the time of the features regeneration.
If input is = YES then Parameter=XX)

FR-Feature 4 (D1=Parameter)



Hope that provides some additional direction and help,

Tim McLellan
Mobius Innovation and Development, Inc.
TimMcLellan12-Amethyst
12-Amethyst
February 16, 2011
UPDATE ** minor edit in example below: FR-1's should read FR-Feature 3's **



As Karl points out Post Regen may help. It really depends on what your
if-then is driving in your skeleton as well as when/what you are publishing.



If you want or need to really fine tune and control the evaluations of
relations I would first try Karl's recommendation as a direct approach.
However, if you find that you are still getting multiple regenerations I
would look into placing "feature relations" in your skeleton exactly where
you want them evaluated. I have used this approach with some complex BMX
situations and it worked out great.



Keep in mind that you can create a feature such as a point, coordinate
system, or any feature to hold the feature relations you want evaluated at a
specific point in your model tree.



For example:

[FEATURE NAME]

Feature 1

Feature 2

FR-Feature 3 (This may be a place holder for your relation. I typically add
the prefix FR when I have a feature that contains a relation. FR-1's
feature relations are evaluated at the time of the features regeneration.
If input is = YES then Parameter=XX)

FR-Feature 4 (D1=Parameter)



Hope that provides some additional direction and help,

Tim McLellan
Mobius Innovation and Development, Inc.
lococnc1-VisitorAuthor
1-Visitor
February 16, 2011
The IF-Then is in the "Program" of the part that is failing. It is as if it
is running the program using the old parameter value. I have tried many of
the suggestions trying to force that relation to happen at the right time
but no matter what I try it seems to use the old value upon running thru the
parts program.

I have submitted a call to PTC.

On Wed, Feb 16, 2011 at 7:18 AM, KRAHMER, KARL ALEXANDER.
(KSC-ASRC-479)[ASRC AEROSPACE CORP] <-> wrote:

> Michael,
> I haven’t looked into Pub & Copy Geoms, but perhaps using
> Post-Regen relations or assembly level relations would help. The following
> is from Advanced Part training on relations:
> *Order of Operations*
> Relations are not evaluated until the model is regenerated. During a
> regeneration, relations are evaluated in the following order:
>
> 1. At the beginning of a regeneration, the system solves model
> relations in the order in which they were entered.
> 2. In an assembly, the assembly relations are calculated first. Then
> the system calculates all sub-assembly relations in order of component
> placement. This means that all sub-assembly relations are calculated before
> any features or components begin regeneration.
> 3. The system starts regenerating features in the order of creation. If
> a feature is attached to feature relations, these relations are solved
> before regenerating that feature.
> 4. If you specified any relations as Post Regeneration, the system
> solves these relations after the regeneration is complete.
>
> Post Regeneration relations are accessed here:
> HTH,
>
>
> *Karl Krahmer*
> Mechanisms and Structural Systems
> ASRC Aerospace Corporation
> Kennedy Space Center, Florida 32899
> Mail code ASRC-5211
> Office: 321-867-5052
> Fax: 321-383-4144
> -* <->
>
> From: Michael Gamber <*>">mailto:-*<->>
>
> Subject: Transfer Parameter using Pub and Copy Geom?
>
> Is it possible to move the value of a parameter using the publish and
> copy geometry functions?
>
> I have an assembly that uses a skeleton. A later part has copy geom
> from the skeleton.
>
> My problem is that I also have a parameter that gets set in the
> Skeleton based on if-then statements.
>
> I am using the execute and input functions in the assembly both belong
> to. Problem is that it takes two regenerations for it to get the info
> straight. I get a failure and then can regen again and it works. In
> tracing it down for some reason it appears to do the "execute" first,
> then regens the skeleton (at that point the parameter changes) then
> the child part fails.
> Very frustrating. I thought the first thing the assembly was supposed
> to do was regen the skeleton?
>
> On WF5 M160
>
>
>
>
Terms & ConditionsAccessibility statement