Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Using measurement for parameter

sip

New member
Hi all,


I want to use the measurement outcome as a parameter to fill in my BOM. How do I go about doing that? I did it with a point at a length that I made equal to that outcome but when the length changes of course it doesn't update.





WF4 no BMX


Sip
 
Sip,

i played around with this and it works (sort of)

Create an analysis feature measuring the distance.
Then create a relation like:
DST = DISTANCE:FID_ANALYSIS_DISTANCE_1

where DISTANCE:FID_ANALYSIS_DISTANCE_1 was inserted from your analysis feature (INSERT->FROM LIST...->Look in FEATURE-> click on your analysis feature->click on button to insert into relation)

Now in your drawing table repeat region add
&asm.mbr.DST
Update your sheet.
Now it will show that distance.

Note if you change the distance in part, it will not update the relation value in the drawing table unless you regenerate the BOM assembly that it resides in. I don't know a way around this (or understand why this is the case) but maybe someone else does.
Not as clean as I would hope but it does seem to work.
Tobyk
 
My first thought (I don't routinely do it and haven't verified it'll work
as intended) is to use ...
_ A Datum Evaluate* Feature to record the distance and a post-regen relation
to read the value to a parameter. Or ...
_ Create a Datum Sketch that squares up the ends (is it Stock size we want?)
and records the length with a post-regen rel.


Or, maybe, some other variation (planes normal to spine?) with an Eval Feat?


*You have to enable the config option allow_anatomic_features.
Can be done without BMX.
Edited by: jeff4136
 
Thanks guys,


I'm going to try it later on. I'm in the middle of a muddle right now. Fam table.


Sip
 
Thinking thru the problem.

Analysis features create feature parameters. The name of which is tied to the specific feature id. (DISTANCE:FID_12345) That's going to make it difficult to represent in an assy drawing bom as each model's feature parameter will likely have a different FID.

A model parameter's name will be stable and can be referenced in the assy drawing's bom. It would seem, that making the model parameter (LENGTH) equal to the measurement's feature parameter (DISTANCE)is all that is needed.
Model relation: LENGHT=DISTANCE:FID_12345

The problem here is that, while the analysis feature's result (DISTANCE) is calculated during regeneration, the model relation is evaluated only at the start of regeneration. Double regenerations will be needed to make the model parameter update. Not good!

The solution:

To get the model parameter to update in a timely fashion, it is necessary to use a feature relation.

First create the model parameter LENGTH and set it's units to the same as the model's length units.

Choose Tools>Relations, then change the "Look In" drop down to "Feature", and choose the Analysis feature. Next, choose "Insert>From List..." and choose the model parameter LENGTH, pick "Insert Selected" and finish the feature relation to read "LENGTH=DISTANCE".

That's it! Your model parameter will update in a timely fashion, and it can be used in the assembly drawing bom.

P.S. If you want the model parameter LENGTH, to report in units other than the model units. Say, feet instead of inches. When the model parameter LENGTH is created, set it's units to feet instead of inches. Also, when creating the feature relation, make sure that under the utilities menu, the "Units Sensitive" option is checked. Pro/E will take care of the conversion, without you having to add a conversion factor.

I just reread Jeff Howard's post. He mentions Post Regeneration relations. When did PTC slip that into the software?

Edited by: gkbeer
 
Ah post regeneration relations, that's the bit I was missing.

Once I put it the relation in there it worked like a charm. Jeff->
smiley32.gif


Toby
 
Glad to assist. ;^)


> When did PTC slip that into the software?


I'm not sure, not even sure if I discovered it in WF (my intro to Pro/E) or WF2.
Doing a little digging ... the WF2 What's New doc describes the Regeneration
Footer (Annotation Features can be move 'to the Footer'). Post Regen rels may
be associated with it and were introduced at the same time?
 

Sponsor

Back
Top