Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Weldment Workflow
CLB_48
Member Posts: 6 PRO
Is anyone using Onshape to do weldments with post machined processes? We have created a workflow to accomplish this but is cumbersome and prone to mistakes.
- Create part studio with unique components
-
- Create assembly with any duplicate plates etc.
-
- Part studio in context
- Transform > Copy in Place
-
- Composite Part
- Add machined features to the composite part
-
Although this gets us there it relies on several steps and ensuring you have the right stuff set as not revision managed, etc. Has anyone else tackled this problem or come up with a better solution?
0
Comments
Do you need to do the assembly +incontext step of the process?
Would a derive feature (a custom one that maybe handles the composite/setting not revision managed) into another part studio also work?
You'd have a part studio for as welded, and another for as machined.
Should have the same outcome but makes all the little extra steps more consistent.
Experts in Onshape Automation - Custom Features and Integrated Applications
The ability to have a BOM for weldment was what drove me towards the assembly and in context, I had not considered the derive from PartStudio "branch" instead of the partStudio in Context, will have to do some playing with that but could see that working out! Always great stuff Caden!
Are you using frames at all?
This question relates to something I just realized about the frames feature.
I made a frame using the frames feature. I then created a drawing for the shop to use in saw cutting (Prototype). At this point, I realized that, because it is a composite part, the individual components do not have part numbers. No big deal, I thought, just use item numbers from the cut list. Then I went to the assembly and used the frame component, only to later realize that the long-term plan for this project calls for running the frame members through our supplier's tube laser, at which point we will need an individual part number for each unique part. So I rebuilt the assembly from the individual components. All good until the shop starts asking "so this tube part number#??? Can you tell me where it is on this drawing of the frame member you sent?" At this point, I realized I had drawings with the same info, but absolutely no way to communicate that.
@CLB_48 Sorry if I am hijacking the thread. But I thought this was a related issue that needed to be solved. And the same solution would fix it as well.
We are working around this with a custom feature that pulls in the part number from the item in a customtable, groups them based on geometry, etc. to make a hybrid cutlist/BOM custom table but that is where we are running into the issue with release management. If we have more than one weldment in a part studio, i.e. a couple of subweldments that then get welded together to form an overall, We would run the custom feature multiple times in the PS to create the pseudoboms and it worked great except when you go to add the custom table to a drawing it brings in all of the tables and you remove the non-required ones which was an annoyance but the deal breaker was all of the subweldments went on to the release candidate as well (and werent removable) because they exist in the custom table.
Still working on a solution to that so hopefully we can get there, just wanted to throw it out to the community to see if others had already solved this problem and we were (hopefully) missing something obvious!