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.
Creating multiple parts that vary only in input variables?
brooks_talley
Member Posts: 27 ✭
I'm building a cabinet which will have 24 drawers. Of them, 20 have unique dimensions.
My prototype drawer part studio can produce all 20 of them by just varying width & height parameters; everything else is parametric and works out beautifully.
Now... is there some better way to produce my 20 unique parts than just making 20 copies of that part studio, each with those two variables changed? I've heard "configurations" used in this context, but I'm not sure that's what I'm looking for (and it doesn't seem to exist today, anyway).
I don't really mind the "20 copies" approach, but it is a pain, and it means that a minor design change that would otherwise be painless has to be propagated by deleting 19 of those part studios, re-creating them, and re-entering their unique variables. There must be a better way, right?
My prototype drawer part studio can produce all 20 of them by just varying width & height parameters; everything else is parametric and works out beautifully.
Now... is there some better way to produce my 20 unique parts than just making 20 copies of that part studio, each with those two variables changed? I've heard "configurations" used in this context, but I'm not sure that's what I'm looking for (and it doesn't seem to exist today, anyway).
I don't really mind the "20 copies" approach, but it is a pain, and it means that a minor design change that would otherwise be painless has to be propagated by deleting 19 of those part studios, re-creating them, and re-entering their unique variables. There must be a better way, right?
Tagged:
0
Best Answer
-
ilya_baran Onshape Employees, Developers, HDM Posts: 1,210Configurations will be a way to do it, but in the meantime, a feature pattern that includes a variable could work, though it's a bit tricky/obscure.
Basically your feature list would look something like this:
1. Set variable #index = -1
2. Set variable #index = #index + 1
3. Set variable #width = [12 in, 16 in, 14 in, 15 in, 16 in][#index] (you'll need 20 widths in the array for 20 copies)
4. Set variable #height = [6 in, 6 in, 5 in, 5.5 in, 4.5 in][#index] (you'll need 20 heights in the array for 20 copies)
5-30 Model your drawer, using #width and #height
31. Feature pattern features 2-30 20 times.
Hope this helps -- post if you need an example of something like this.Ilya Baran \ VP, Architecture and FeatureScript \ Onshape Inc5
Answers
I hear "Configurations are comming.." or "It's our most requested thing" but until then I'm patiently waiting it's arrival
Basically your feature list would look something like this:
1. Set variable #index = -1
2. Set variable #index = #index + 1
3. Set variable #width = [12 in, 16 in, 14 in, 15 in, 16 in][#index] (you'll need 20 widths in the array for 20 copies)
4. Set variable #height = [6 in, 6 in, 5 in, 5.5 in, 4.5 in][#index] (you'll need 20 heights in the array for 20 copies)
5-30 Model your drawer, using #width and #height
31. Feature pattern features 2-30 20 times.
Hope this helps -- post if you need an example of something like this.
Is this an obsolete workaround or am i just missing something?
Usually if I make things with custom design I use single studio for easier and faster design & check but if there is a possibility that same parts could be reused in other products later then I create drawers into library and create separate assembly.
Difficult to say without seeing the design and not knowing if you are aiming for efficient desing & produce or just learning Onshape functions.
https://cad.onshape.com/documents/bc136e07d5821d81309e85c1/w/fa51e3d19c3b692b77b3b05e/e/2a7f0f54675dc2173a1095ca
Then you will get two different sized box instances...
BUT you'll need to alter Sketch 2 slightly to give the correctly sized bottom part... (and at the moment I can't work out why the inferred/derived/projected/convert size isn't working!)
https://cad.onshape.com/documents/bd61796e2f9631a5c53245ac/w/509dbd33202a9b99b8129a64/e/4f3b443191c7814758e873fe