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.
Using group and sub assemblies
guy_rogel
Member, User Group Leader Posts: 88 PRO
After a very expensive mistake in a project , I have realized there is a major logic problem with sub assemblies in on shape.
When inserting a sub assembly to a top level assembly it is possible to "Group" it. But this will only lock the position of the sub assembly parts. A change in the location of one or more parts in the sub assembly tab will not reflect at the top level assembly tab. this means there is no option to have a sub assembly linked to it's tab in the same document. I find this to be very very trubbling. what is the point in having sub assemblies if they do not reflect correctly.
I think there must be an option (I think it should be by defult) to make sure sub assembly in the top level will be the same as it's TAB
It cost me more then 5000 USD to find this logic issue.
UPDATE
please see my comments how this can be solved
When inserting a sub assembly to a top level assembly it is possible to "Group" it. But this will only lock the position of the sub assembly parts. A change in the location of one or more parts in the sub assembly tab will not reflect at the top level assembly tab. this means there is no option to have a sub assembly linked to it's tab in the same document. I find this to be very very trubbling. what is the point in having sub assemblies if they do not reflect correctly.
I think there must be an option (I think it should be by defult) to make sure sub assembly in the top level will be the same as it's TAB
It cost me more then 5000 USD to find this logic issue.
UPDATE
please see my comments how this can be solved
Tagged:
3
Comments
This sometimes seems to happen with linear patterns of assemblies as well.
IR for AS/NZS 1100
I now use a very simple (not nice but simple) solution to my problem
If I need to move a sub assembly which is not fully defined (for example an imported PCB ) in a top level assembly I :
- Group it first
- use mating to move it wherever needed
- Delete or supress the group mate to make sure any changes in the sub assembly will reflect in the top level assembly
not the nicest solution but worksuse the group mate with care
Guy
Making a composite part (good for imported stuff or things you model, "closed" makes it a single "thing" with one color for everything, not "closed" preserves colors)
Adding the parts to a subassembly, then grouping. Be sure to fix so that they aren't moved from the default position! That will let you add stuff later by directly clicking the green checkmark to insert in a consistent location, then grouping, rather than having to mate everything individually
@alnis is my personal account. @alnis_ptc is my official PTC account.
I will defiantly check this soon
IR for AS/NZS 1100
This is not intuitive for subassemblies and is always a confusing issue. I think group should throw a warning when someone selects a sub assembly. Or just prevent the ability to select sub assemblies when creating a group mate.
Hi,
I just moved to OS from other cad and the solution with "composite parts" is not really well suited for working with imported parts.
Imagine you purchase your PCB as an single product and you need to assign an Part Number for the whole PCB (then also Vendor and Supplier PN for the BOM purposes)
When you try to release such "composite part" in OS you're asked to apply Part Numbers to ALL items in the composite parts.
I.E. you must assign part numbers to all bodies in composite part - an complete waste of resources.
When I buy an complete PCB assembly from a supplier it has an SPN assigned to it and just ONE part number.
Now - in OS - when you'll export a BOM it will turn out to be excessive complex.
Hello, I am new with onshape. But i do not understand the Assembly and Sub-Assembly logic. When I do have an Assembly with Sub-Assembly and i move a Sub-Assambly - why is it just moving the part of that Sub-Assembly i grap, and not the whole subassembly? (not the same logic like SolidWorks?) br Mark
The difference is that "Fix" is not a constraint, it is only used to stop the current assembly from floating around and does not transfer up to the next assembly. In the subassembly, fix one part (to stop it floating) then use Group.
You can also use the "lock" function so that the sub-assembly behaves more like SolidWorks.
It's designed like real life. Let's say you have a door knob subasm inside of a door asm. In ProE/Creo, the knob subasm would be static in the door asm. In OS, you could turn the door knob and it would move the latch, and you could do this regardless of how far the door is rotated on its hinges in the top level asm. Its super easy to do real-life motion, but it does require changing the thought process of how assemblies are built.