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.
Selecting a direction or axis for assembly pattern
brucebartlett
Member, OS Professional, Mentor, User Group Leader Posts: 2,141 PRO
I've found a few times where I want to do a pattern in an assembly and do not have the correct geometry to get the axis or direction. My instinct is to hover over the origin and have the main axis jump up like when doing a mate connection to the origin in the part studio(*edit like when mating to the origin). If there is a way to do this that would be great otherwise this could be moved to an improvement request.,
1
Comments
Twitter: @onshapetricks & @babart1977
I dont enjoy fixing references when they break because of a missing part or lost reference.
I don't see it necessary to add planes into the assemblies if you are able to use the origin as the coordinate system in place of any planes. I see the assembly origin as an end-all solution to assembly planes, axes, etc.
If we could reference all of the axes and planes of this coordinate system (i.e. z-axis, x-axis, y-axis, xy-plane, xz-plane, & yz-plane) then we could have the availability to reference something un-changable.
This concept is powerful and would allow smarter assemblies which are more resistent to changes in the models. I would like to see options in pattern dialogs (and other dialog hoxes) which allow users to reference these entities.
On a similar note, I like tying mates to the origin in assemblieswhen necessary, but I feel it can be difficult to 'wake up' the origin. Especially when a part is in the way. If there was a way to prioritize the origin over parts in most cases then I would be very happy 😁
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977
I really like the way onshape inherits sub-assemblies and want to keep that working. My library is full of working assemblies and the ability to drag them into a higher assembly and they work, well that's pure genius.
Don't want to go back to the flexible state which never worked properly. Onshape is sooooo much better. If you want inheritability in assemblies, which is really cool, don't assemble to the planes in an assembly. If you resist this temptation, I don't care how deep your assembly structure gets, assemblies inherit from sub-assemblies. If you add a constraint along the way up the tree, then your motion becomes more restricted as you add to your project.
In short: don't assemble to these planes please.
Good point. I'm big fan of Onshape's fully functional sub-assemblies and never got this working so smooth (or at all) in Alibre by making loads of sub-stuff 'flexible'
I'm glad you're using it too. It's one of the greatest new features and it's not talked about much. OS is the first to allow you to combine working sub-assemblies into higher assembly and everything works properly. It's recursive and true all the way down to lowest sub-assy. It's very organized.
If you're building any kind of automation, then OS is the only solution. All my linear rails and cylinders have motion that is limited. Then I drag'm into a higher assembly and that 'limit' governs the range of motion for my carriage or what ever I'm designing. It's the closest virtual experience to working on a bench and building something from real parts.
Sometimes I wonder if the fact that there are no planes in an assy, this prevents people from assembling to them. Once you assemble to an assembly, the chain breaks and things stop working. The mates tied to the assembly won't transfer when moving to the next assembly. You can see they're missing if you open it's mate folder in the high assembly. It's hard to write about this without diagrams and graphs.
The library planes I insert or you insert, please don't assemble to them. Keep the chain working.
Twitter: @onshapetricks & @babart1977
Twitter: @onshapetricks & @babart1977