Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
Is it possible to break the dependency of a mirrored part? I am wanting to mirror parts with geometry dependent initially so any changes are pushed to the mirrored part, to save time, as the majority of changes will apply to both parts. However, sometimes we need to make changes to one of the parts but not it's mirror. Can this be accomplished by undoing the "geometry dependent" setting somehow? Attached are some screenshots of the options/settings I'm seeing when creating the mirror and then when editing definition of the mirrored bodies feature.
I am using Creo 8.
Thanks!
-Matt
Solved! Go to Solution.
If I understand you design intent; I would propose another way to handle it that maintains dependency of the mirrored part geometry. Review this thread and let me know if the method disclosed there would work for you. Read the entire thread, not just the marked solution.
(1) Solved: Mirror component with varying features - PTC Community
If I understand you design intent; I would propose another way to handle it that maintains dependency of the mirrored part geometry. Review this thread and let me know if the method disclosed there would work for you. Read the entire thread, not just the marked solution.
(1) Solved: Mirror component with varying features - PTC Community
I think that might be a good work around, I will do some testing. It's a little more cumbersome than I was hoping for with needing to have that 3rd "master" part, but I think it will be worth it if it does what I want.
I've never really used Merge/Inheritance up to this point... here's what I'm thinking are the correct steps to create the "merge" part:
1. Create the master part
2. Start a new part
3. Get Data group --> Merge/Inheritance
4. Operation type: set to "Merge"
5. Set the source model as the master part
6. Set to Default constraint and hit OK
This seems to give me a merge part that will update whenever the master is changed, but can have its own independent features below the merge in the model tree. Which is great!
Let me know if you see I'm missing a key setting or doing things the long way, etc.
Thanks!
Your list of steps is accurate for the creation of the derivate part using the merge function. Using this method will give you more flexibility while driving both left/right parts from a single master model.