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.
Options
Measured Variable in a Variable Studio
jacob_kelley486
Member Posts: 9 ✭
I have just started using the Variable Studio feature in order to have variables across multiple Part Studios. It is a great tool! However I can't seem to figure out if it is possible to have a driven variable (Measured) like you can do with a variable in a Part Studio. I am hoping to grab a measurement from one of the Part Studios and use it across other Part Studios. Also I would be calculating other variables in the Variable Studio based on that measured variable. Is this feature possible yet? If it is, it isn't intuitive to find and I can't seem to find anything searching online.
0
Best Answer
-
Options
_anton
Member, Onshape Employees Posts: 296 
Not possible at the moment; you can help us prioritize this by submitting an improvement request.
The conceptual difficulty with such a workflow is that the Part Studio and the Variable Studio would form a circular reference, so we'd need to construct something that avoids that, such as our Assembly in-context mechanism. Even if we did implement this, though, you'd have to deal with manually updating "contexts", which could be laborious and error-prone.
The two recourses now are 1. just do all the math in your Variable Studio, computing the measured quantity there. This is often possible and tends to be the simplest solution. Or 2. keep the measured variable in the Part Studio, use the SuperDerive feature to import it into other Part Studios. But then you can't import it into a Variable Studio.
And I should mention that you can copy the measured value into the Variable Studio, but that's obviously non-parametric.4
Answers
The conceptual difficulty with such a workflow is that the Part Studio and the Variable Studio would form a circular reference, so we'd need to construct something that avoids that, such as our Assembly in-context mechanism. Even if we did implement this, though, you'd have to deal with manually updating "contexts", which could be laborious and error-prone.
The two recourses now are 1. just do all the math in your Variable Studio, computing the measured quantity there. This is often possible and tends to be the simplest solution. Or 2. keep the measured variable in the Part Studio, use the SuperDerive feature to import it into other Part Studios. But then you can't import it into a Variable Studio.
And I should mention that you can copy the measured value into the Variable Studio, but that's obviously non-parametric.