cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

Convert Internal Datum to Standalone / Embedded Datum

akelly
12-Amethyst

Convert Internal Datum to Standalone / Embedded Datum

Currently using Wildfire 4

Using a pre-Wildfire part where features were created with "make datum" during feature creation. These datums don't show up anywhere in the model tree / layer tree / screen, even if I have performed Unhide All, expand all, and set all layers to unhide. If I Edit Definition on the feature then go into Sketch Setup, I can see the plane, but otherwise, I'm unable to pick it.

According to the Wildfire 4 help, these are called "datum features that are internal to a feature". Is there any way to convert these to regular datums? (or, at least make then visible, selectable, etc.?)
Note: I brought up help because it discusses embedded datums and how to convert them to standalone datums. This isn't an embedded datum. I guess pre-Wildfire didn't create explicit features when asynchronous datums were created.

Andrew Kelly, P.E. | Senior Engineer | Crane Aerospace & Electronics | +1 440 326 5555 | F: +1 440 284 1090


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.
3 REPLIES 3
akelly
12-Amethyst
(To:akelly)

In other words, DTM2 exists, but it is not visible in the model tree (or screen), because it is internal to Sketch 3 (see attached).

I want to convert DTM2 to the way it is shown in the attachment.

<<embedded datum.png=">>

mpeterson
12-Amethyst
(To:akelly)

Not the answer to your question, but one reason I very rarely create datums on
the fly. If I realize I need a new datum I will exit the feature creation and
create the datum and then proceed with making my feature. If need be later for
mirroring, patterning orcleaning up the model tree Iwill group it at that
point.

Good Luck withthe resolution to this issue.

Mark A. Peterson
Sr Design Engineer
Igloo Products Corp
-



JOES
1-Visitor
(To:akelly)

Just yesterday I bumped into the same issue. I couldn't make DATUM A
because A was taken. Using Locate found it buried in a pre-WF feature. It
was a revolved cut that cut nothing. I could repress it, move it anywhere
on the model tree but I could not delete it. Finally I was able to rename
the datum to Z & create my new, stand-alone DATUM A.

As I remember, a feature has no delete option if part of that feature, like
a datum, is used in the drawing of the part. Nothing shows whatsoever on
the drawing so it must be something else. No worries, I work-around works
but I dislike leaving that feature at the suppressed at the end of the model
tree.

Regards,
Joe S. 313 410 9034




On Mon, Mar 28, 2011 at 2:08 PM, Kelly, Andrew C <
-> wrote:

> Currently using Wildfire 4
>
> Using a pre-Wildfire part where features were created with "make datum"
> during feature creation. These datums don't show up anywhere in the model
> tree / layer tree / screen, even if I have performed Unhide All, expand all,
> and set all layers to unhide. If I Edit Definition on the feature then go
> into Sketch Setup, I can see the plane, but otherwise, I'm unable to pick
> it.
>
> According to the Wildfire 4 help, these are called "datum features that
> are internal to a feature". Is there any way to convert these to regular
> datums? (or, at least make then visible, selectable, etc.?)
>
> Note: I brought up help because it discusses embedded datums and how to
> convert them to standalone datums. This isn't an embedded datum. I guess
> pre-Wildfire didn't create explicit features when asynchronous datums were
> created.
>
> Andrew Kelly, P.E. | Senior Engineer | Crane Aerospace & Electronics |+1 440 326 5555
> | F: +1 440 284 1090
Announcements
NEW Creo+ Topics: Real-time Collaboration


Top Tags