Here is my current model with my failed attempt to do this:

https://cad.onshape.com/documents/2c723e3e98b11c5789768dc4/w/98990b8a08bc3ba7b4cb7d14/e/6b02c8a2f24e869c42c1aac8?renderMode=0&tangentEdgeStyle=2&uiState=6a982e4047df4d50aba6d446

Link: https://cad.onshape.com/documents/7391e5a0490b42447ce0ff5b/w/53872c7c5b423e4986a5c184/e/04adc8ae18645be2e5e6e869?renderMode=0&uiState=6a978080c791f3c69a051e4f

(apologies for my bad MSpaint drawings)

So I'm trying to make some plant pots that I can 3d print at home on my bambu, and I can't pin down why this loft isn't happy. the two sketches are the same, excpet that the top one is a little larger. Both are fully parameterized, created by usind a pattern that repeats 2 semicircles about the central point. Even if I make the curves very tame, the loft fails. Any help or advice would be appreciated.

They have gone to the Learning Center and began taking the lessons and the tutorials.

How can they log into OnShape and obtain a drawing surface (screen) where they would be able to create a new sketch and manipulate it on the screen using the various tools and commands?

I would like for them to practice as they follow the lessons.

Thanks!

• 1/4PT Flexible Oil Coolant Pipe Hose
• Silicone Tubing

Now, I can design the adaptive part as needed, example my first will be a design to implement the straw by designing/printing a 'cola' cap usage. Below you'll find my Onshape CAD link where I created the custom bottle threads, which are functional with the bottle, but it printed only a hole, not NPT hole.

When using the hole function on Onshape, setting it to 1/4-18 NPT does printer (BambuLab A1 Mini) not print threads?

Thanks for all input

e14f96724ba55a1f3232efe2

thanks

I am ultimately wanting to estimate the stresses in the connecting bolts. As a start, I have used fixed mates at each bolt point, and supported the ends in a way that permits rotation and translation. I have set the Connectivity Method to be only via Mates. The overall deflection is broadly what I would predict from a simple uniform beam analysis, but where I would expect to see stress points at each of the connecting mates, I see just overall uniformly low-stress regions across almost the entirety of the composite structure.

It's my very first attempt (I have watched a number of the introductory videos) so I am guessing that I am making some sort of rookie mistake. I would greatly appreciate any pointers to what that might be.

This is the link to the model:

https://cad.onshape.com/documents/2edb0b04dbc05f310e8e0e1a/w/1ad29dcbefda8860e378858d/e/2232a517725c2700ac63f4c3?renderMode=0&uiState=6a8e7a11f776b43fc09e153a

This is a long one, but I feel like the background of my thought process will be helpful communicating my question and I'm hoping that someone here can help me wrap my head around how in-context works.

Inciting Problem:

My goal was to make a featurescript that evaluates using a query that automatically includes all bodies in the part studio, including the ones from an in-context assembly, but the query could not include the in-context geometry without manual selection in the UI.

TL;DR of the post:

As far as I can tell, this isn't possible because the parts from the assembly that you see as "ghosted" entities aren't actually in the part studio until they're manually selected to be referenced, but that raises another question for me that I haven't been able to figure out:

If the assembly parts don't exist within the Part Studio yet, how come features that use manually selected entities with EntityType filters are able to identify and control what is clickable on the assembly before the reference is made?

The Long version of the post:

My understanding was that any select-able/highlighted entity, like an edge or vertex, is a UI shortcut that's mapped to a pre-compiled list of all entities within the instance. Then, when a filter is applied, it activates/deactivates the UI shortcuts based upon what entity type it points to in the list it's already able to read. This total list is what I figured the input of "context is Context" is when defining a feature.

If true, it would stand to reason then that features can't automatically query from an in-context assembly because the entities within it aren't on the list that was used in the input of the feature. This explication also justifies why the assembly entities need to be referenced or derived before they can be used, since the act of referencing it is actually just reading from the assembly context, then writing a copy as a new entry to the part studio context, making it available to be accessed by features.

On the surface, these pieces seem to fit so nicely together; When you open a feature, the context up until that point is evaluated including any copied references from other contexts. Then, when a selection field is activated, the list of entities in the context is filtered to match the definition of the field and what's leftover is the list of entities that can be selected in the UI to be added to the query.

However, the rub is that in-context references don't have to be defined prior to using a feature in order to be filtered. If the "Offset Curve" tool is used, the selection UI still only allows for curves and edges to be clicked on at which point the reference is made and the copied edge/curve is added to the query. This seems to imply that the feature can still read the other context, at least enough to filter the UI based up what's being hovered over and trigger the steps to create and query the reference.

So if the in-context geometry is available to the feature to be filtered through for one by one selection via the user in the UI, how come there's no ability for it to simply apply the filer the same way, but automatically grab all remaining entities to be referenced in the same way as it would be if it was manually clicked on?

Epilogue:

I presume that I have at least one, if not many, critical flaws in how I understand this process to work. As such, I invite anybody with more accurate knowledge on the subject than I to impart their wisdom upon this thread. In the exceedingly unlikely event that I nailed it, I'd like to request some new functions to read and make references from in-context assemblies to the primary part studio context automatically.

Thanks in advance for any insight!

I have encountered a problem, where I have the inner part of the bearing connected to a rod via cylindrical mate and the outer part of the bearing, to be more specific the plane area with the bore holes, must be parallel to the marked side of the servomotor, no planar mate. In theory this connection must work, but for some reason it fails here.

The blue arrows indicate the parallel mate and the red arrows the cylindrical mate. The inner part of the bearing is rotationally independent from the outer part of the bearing. The bores of the linkage rod only have cylindrical mates.

Additionally, I was able to create the aforementioned cylindrical and parallel mate, but the linkage rod was suddenly constrained to a horizontal position. I want the linkage rod only constrained with the two cylindrical mates and nothing else, so actually it should move freely in a 2D-plane.

I’m currently working on creating various jigs for parts that we manufacture. This works well for solid parts using Boolean operations, but I would like to achieve the same result with hollow parts, as shown in the picture.

Is there a way to create only the imprint of the outer or inner surface of a hollow part, rather than simply subtracting the entire part from another object? Ideally, I would like to use the surface geometry to create a matching fixture or jig.

Also, the offset function doesn't seem to work for a lot of parts with more advanced geometry.

Thanks in advance.