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: That One Time Onshape Saved My Deadline—What’s Your Story?
Not so much my deadline, but i was using it with my students when lockdown happened and it made life much much simpler!
That One Time Onshape Saved My Deadline—What’s Your Story?
Onshape’s cloud collaboration tools saved my team’s project last week. We were all working remotely, and the ability to make real-time edits ensured we didn’t miss a critical client deadline. How has Onshape helped you in a pinch? Let’s discuss!
Re: Will PTC ever let the use of OnShape for makers/individuals free from any monetary concessions?
There are no plans.
Re: How to programmatically find faces which define the entry and exits for a hole?
@Caden_Armstrong That was definitely it, thanks!
In case anyone wants more info about how I did this, here's the code snippet:
// Find the faces which connect to the hole
var adjacentFaces = evaluateQuery(context, qAdjacent(cylinder, AdjacencyType.EDGE, EntityType.FACE));
// Loop over each face
for (var face in adjacentFaces) {
// Visualize the face
debug(context, face, DebugColor.MAGENTA);
}
Re: Onshape is not connected. Refresh the browser to continue working on this document? (Now Sorted)
Re: How to create this specific mate ?
Besides this is no good way to design a trigger (make servo and trigger axis parallel and you will avoid a lot of issues!), a tangent condition won't help here, simply because there is no tangency, only two edges being coincident at one point, and these are not necessarily the same two edges all the time. If we had collision detection, that'd be the way to go, but we haven't.
May I propose using a gear mate between the two rotate mates used for servo arm and trigger rotation? Moving one would rotate the other in a given ratio, then. This cannot simulate the free travel of the servo arm before it touches the trigger, of course, but maybe it could get close enough to demonstrate the action intended.
Add fonts
Is there any way to add fonts for the text tool? In particular, I would like to add one of my stenci
Re: How to programmatically find faces which define the entry and exits for a hole?
There are two queries that might help you:
qHoleFaces(seed); → this will filter a query of faces to those that belong to a hole
qAdjacent() → this will take a seed query and find the faces that are adjacent to all of the given entities.
If you take your hole faces and find the adjacent faces, those are the "boundary" faces.
Re: One or more tabs being moved contain workspace references. All referenced tabs will be moved as part
Make a copy of your document, try it, see what happens! :)
It just means that the tab you are moving to another doc has other tabs that depend on it, so for example if you were moving a part to another document and you had a drawing of that part in another tab then, if the part moved and the drawing stayed, the drawing would fail, because the part wasn't there any more. So Onshape will move the part and the drawing into the new doc.
Re: One or more tabs being moved contain workspace references. All referenced tabs will be moved as part
Well, in my experience this note means you can still move the part if you really want to, but be prepared to be left with an even bigger mess than when leaving this part in it's inappopriate location.
I find this situation annoying, even if there is a logical explanation. There are situations where I have designed a part as part of a certain project and only later find out I might need it in another place or even for another project. Then, one would possibly want to move a certain part to it's own document for later use. Now, it dosen't work that easily. It gets even more confusing, if something has been designed in context, with a reference to the part moved. You never know what will be moved along with the part in question.
Since I tried this a few times with limited success, I try to remember always designing supplier parts and such in their own documents from the ground up, but sometimes I forget, or I get such parts in imported files. One example of such are switches and buttons, which will get references to cutouts in some mounting plate rather sooner than later. In my opinion, it is usually easier and more sustainable, to recreate (maybe based on stripped down copy) these parts in their own workspace, and then replace in assemblies where they have been used.
Maybe it would be a good thing, if parts could be copy-moved, stripping their downstream references, keeping the original document intact, just to get around this.