What do you do if you have a family table of parts where, for instance, one instance is the cast version, and the other instance is the machined version? Or the geometry is different such that for one instance vs. another, different datum structures are used? What if the same part is used in 2 different dwgs and you want different datum structures for each use? Yes, you can use the casting as an inheritance feature, but tha'ts kind of a pain in an of itself and requires the module some people don't have or don't know how to use.
As much of a pain in the posterior as it is to use GD&T the "normal" way, why not simply use draft datums to populate GTOL's created in the dwg itself rather than the model? I've done a test, by creating draft datums beyond the format, used the "properties" option to turn them into ASME-style datums, and used them as datum references in GTOL reference frames created in the dwg. I have my config.pro setting: "create_drawing_dims_only" set to "yes", and I've create an ASME-style datum symbol that I can attach to or offset from anything, anywhere. So, I have the flexibility of doing anything I want, wherever I want, and am not tied to model datums. Also, on complicated models it cleans up the model tree considerably.
Give it a try with my attached ASME-style datum symbol and let me know what you think.
Grazie!
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.
