Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
I am going to give two examples of my issue in hopes that someone has a suggestion. The second case is a little confusing.
1. Mirror a part with text
We often create a mirror part but we do not want to mirror the text for obvious reasons. The text on our parts are part of the casting. If you mirror a part with text, the text appears incorrect/mirrored on the other part. If we suppress the text before we mirror, we can add the text to the mirrored part, but if we resume the text of the original, it will show up on the mirror version. (We want them to be dependent)
2. Mirror a part with different feature
If we have a part that has a mirrored version but one specific feature is different. We want to create the mirror part but exclude that one feature. In order to keep the parts dependent, we created an instance of the original part and turned off/suppressed that feature on the instance. We then open the instance and create a mirror part from it. Now we can add the new feature to the mirrored version.
This works but the problem is that when you try to Save a Copy of this part, it all falls apart.
We open the original (Generic) part and Save a Copy to a new name. You must open the table and rename the instance but the mirrored part will continue to reference the original instance name which still exist but it's not in session. I tried opening the mirrored and Save a Copy to it's new name in hopes that when I have it in session and rename the instance on the new part created from the generic, that it would update the link between them but it does not work. The mirrored part and the Save a Copy of the mirrored part still links itself to the original instance name.
Any ideas on how to mirror a part that is dependent while excluding a single feature between them. We can't figure out a way to make this work. If we make the mirror process independent, it works but we loose the ability to make changes to one part and have it automatically update the other.
ΜΟΛΩΝ ΛΑΒΕ
Another solution would be to mirror the partkeeping the model tree. In the mirror part you could supress the original text and recreate it.
There may also be a way to change the driving dimensions of the text to force it to a negative number and thus create the text in the proper orientation. I've never tried this specifically, but it may help if you want to keep more of the common features/dimensions than recreating the text.
Doug,
That worked out perfectly.
Thank you very much for your input.
ΜΟΛΩΝ ΛΑΒΕ
You can simply use the rename in session functionality to avoid the backing up twice.
Just do file rename, check in session so the versions on disk are not changed. Do this for all 3 parts, save all 3 parts.
In Reply to Doug Schaefer:
You're close to what I've done in the past.
1. Create the parent part.
2. Add a family table to the parent and create an instance with the non-mirrored features excluded.
3. Create your mirrored part, referencing the instance
4. Add the text and other revised features to the mirrored part
To make a copy of these parts:
1. Back them all up into an empty, temporary directory.
2. Open the generic, then the instance and finally the mirrored part into an empty session.
3. Rename each, using file -> rename.
4. Save all files.
5. Back them up back into your main working directory.
We don't use any sort of PDM here, so I'm not sure how that would affect the process.
--