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.
Best Of
Re: Cutting dimensions for tubes, parallel to the tube.
Here is one way to accomplish this. A separate sketch in the part studio can give some lines for dimensioning. When you get to the drawing show/hide sketches.
Tipps for oragnization of documents
Hi guys,
just wanted to ask how you organize your big projects.
For example, you have a big machine with 20 different assemblies that are all dependent on each other.
Every assembly consists of 10 Part Studios and 10 sub-assemblies and few other tabs (drawing, imported parts, etc.) - so big enough for its own document.
But, for me the problem with different documents is that I must make a version of the document to see the changes in another document. This applies to every single change in the document (also for just adding a thread, hole, chamfer, ..). This function is good in a later status of the design process. But at the start you have a lot of small changes in the different assemblies and sub-assemblies you want to see live without making a version.
So therefore, I am curious how you organize your documents or am I the only one with these problems?
Re: Create a freewheel mate condition?
I too am trying to model a design that has a one-way clutch. I'd be happy with either an abstract "one way revolute" mate, or a "pawl and ratchet" relation, or just some way to be able to model this with individual parts interacting somehow.
Like OP I don't want just a static design, I want to be able to move one part and see the effect that it has on the rest of the system (through the one-way clutch).
I've only just started using OnShape and this seems to suggest that it won't be suitable for this task. If this is a planned feature, someone please let me know!
Re: Auto-populating Part Numbers and/or Names
Since the previous post we have turned off release management as the part number generator (a positive feature) did not outweigh the learning curve that appeared. In that case the part numbers which were being generated were great, however they did not carry through when we attempted to export assemblies or part studios wholly. Therefore for the time being release management has been taken away.
Currently I am attempting to make export rules work for our use-case and the following nomenclature appears useful:
This, once again, works great for singular parts and for the top level of assemblies and/or part studios. The parts within the assemblies do not seem to translate over however once the files are exported from Onshape for further use, reverting to their Part 1, Part 2 etc. common naming convention.
This appears to be a common issue when using a different step translator between import and exporting operations. Looking into the causes of this I reference the following sources for information:
https://forum.freecad.org/viewtopic.php?style=4&t=39438
https://forums.autodesk.com/t5/fusion-support/when-exporting-to-step-file-all-body-names-and-folders-are-lost/td-p/10758938
https://www.alibre.com/forum/index.php?threads/loss-of-part-names-in-exported-assemblies.7123/post-37687
Per these sources I went to look at an exported Step (AP242) from Onshape and imported it back into Onshape to see what happens.
That test yields positive results:
Looking at the step file from that export we can see that the part name is provided under the identity "PRODUCT". And when imported all the names match with the imported parts.
Ref. https://www.steptools.com/docs/stp_aim/html/t_product.html
So we know that the exporter is taking the part names. We also know the part names cannot be auto-generated or directly link to a part number. Therefore, what does export rule do for me when I am trying to get parts to export with a provided file name from within an assembly or a part studio?
Even if I include Parts as a category within the scope of Part Studios and assemblies, I yield the same results. Have I misunderstood how the export rules are meant to function?
Under these settings Part Studios import using the names created by the export rules as shown:
Are we unable to utilize this on contained parts in the part studio?
Any feedback or thoughts would be appreciated.
Re: Why can I not see +Render Studio?
Hi Jason. Unfortunately, Render Studio is currently only available to Professional users.
Re: Circular pattern change the assembly type
I think I found out the problem : The axis I'm using is the origin, and when the assembly is inserted in another assembly, it keeps using the origin as reference !
Re: Show Dimensions in Assembly
