Skip to main content
K
kskatun10-Marble
10-Marble
December 12, 2023
Solved

shrinkwrap for welding

  • December 12, 2023
  • 1 reply
  • 10449 views

We use shrinkwrap for welding, because merge does not work for features and a weld with the weld application is a feature in Creo.

 

It works fine, however unlike merge you can not open base model from the model tree, instead you need to go to feature information, copy the number and open that number. Is it possible to make a mapkey to do that instead of manually do it all the time? Below is  mapkey, but how to get rid of the hardcoded filename?

 

 

mapkey foo ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 1 `node2`;\
mapkey(continued) ~ RButtonArm `main_dlg_cur` `PHTLeft.AssyTree` `node2`;\
mapkey(continued) ~ PopupOver `main_dlg_cur` `PM_PHTLeft.AssyTree` 1 `PHTLeft.AssyTree`;\
mapkey(continued) ~ Open `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Close `main_dlg_cur` `PM_PHTLeft.AssyTree`;\
mapkey(continued) ~ Trail `MiniToolbar` `MiniToolbar` `UIT_TRANSLUCENT` `NEED_TO_CLOSE`;\
mapkey(continued) ~ Command `ProCmdInfoFeature@PopupMenuTree` ;~ Command `ProCmdModelOpen` ;\
mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\
mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `PREVIEW_POPUP_TIMER` \
mapkey(continued) `file_open:Ph_list.Filelist:<NULL>`;\
mapkey(continued) ~ Input `file_open` `Inputname` `0265-0413-04 `;\
mapkey(continued) ~ Update `file_open` `Inputname` `0265-0413-04 `;\
mapkey(continued) ~ Command `ProFileSelPushOpen_Standard@context_dlg_open_cmd`;

 

 

Or maybe there are better ways to handle weldassemblies in creo?

Best answer by tbraxton

My above proposal was in the context of using the multibody part as the top-level object for the design of a weldment. My intent was not to use this in conjunction with your current design space but as an alternative. I do not see any issue with the creation of the as welded assembly and drawing in my proposal but as I said I have no real-world experience using weld features in Creo so I may be overlooking something. 

 

I am not proposing to add the multibody part to your current design space so the arguments you make above or not relevant if evaluating my proposal independently. If you consider the sketch I posted above it is effective at maintaining short dependency chains from the top level to the lowest level components and a drawing if you were to add one.

 

If you want to stick with what you have and use shrinkwrap you can call an external script from a mapkey to access the source model name and retrieve it through a mapkey plus an external script or use of one of the Creo APIs.

1 reply

tbraxton
22-Sapphire II
tbraxton22-Sapphire II
22-Sapphire II
December 12, 2023

Can you explain the details about your statement: ...merge does not work for features and a weld with the weld application is a feature in Creo.

 

What exactly needs to be done with the weld feature that you are using shrinkwrap for?

 

Have you considered inheritance features for the weldment assembly?

K
kskatun10-MarbleAuthor
10-Marble
December 12, 2023

We have several parts that we weld together as solid welds with the creo weld module, then we want to machine this. We could of course use assembly cut, but in real life we end up with a welded part. So we create a new part and do shrinkwrap of the weld assembly, this way we have a part that we can machine and that contains the welds. Merge feature requires a help assembly where you add the weld assembly and the part tyou want to merge to, also merge can not be performed on features as far as I know. Shrinkwrap works superb for us, its been stable and are fast to load, the only problem that takes a bit of time is to find the weld assembly since you need to go to feature information copy the assembly name and then copy it in to open file dialog instead of for merge where you can just right click on the feature and chose open bbase model. We were hoping we could achieve this with just selecting the shrinkwrap feature and then run a mapkey. 

 

See post here by Eric for instance: https://community.ptc.com/t5/3D-Part-Assembly-Design/Machining-of-a-weldment-assy/td-p/154438 

tbraxton
22-Sapphire II
tbraxton22-Sapphire II
22-Sapphire II
December 12, 2023

Merge functions only work on parts not assemblies as you have found. The merge function has an external option that does not require a "help assembly" as you call it. Inheritance feature within merge functionality was created to handle multi-stage manufacturing models like as cast and as machined states driven by a common master model. I think this would work for your as welded and as machined versions unless there is something about weld features that prevents this (I have no experience with weld features).

 

As a concept it would seem that you could use multibody in a part model to represent all welded components within a part model which would then enable you to exploit the merge functionality to create a model of the as welded and as machined states of the weldment. 

Terms & ConditionsCookie settingsAccessibility statement