Combining multiple imported parts into a single "Part Studio"

edward_casati

I am using the McMaster catalog for the first time to download pre-made hardware designs, like nuts, bolts, spacers.
When I import a part, Onshape creates a new "Part Studio" tab for each individual part.
Is there a way to combine the imported parts into a single "Part Studio", so I don't end up with a dozen tabs across the bottom of the screen? For example I could have a different "Part Studio" for Nuts and Bolts, another one for Spacers, etc, each one containing several imported parts in one place.

owen_sparks

Hi, although this seems like a simple use case I don't believe there is a simple answer to this.

As it stands OS doesn't have an "Import to this existing part studio" function, nor does it have a "move the contents of this partstudio to another existing partstudio".  If we're talking assemblies then that's easy, but not partstudios.

As you saw the derive has to derive a copy from somewhere so you can't delete the original tab.

I can think of a workaround of building as assembly of each and then doing an in context edit copy in place to get a PS with one of each in there, but that's a sledgehammer to crack a nut, and all the part properties will be lost, you'll just have Part1, Part2, yada-yada.

If your use case is just to tidy the document then I'd say make folders along the bottom of your document for each flavo(u)r of component and put individual partstudios in those with one component in each studio.  When you insert or derive these parts they'll all come in at the origin, which won't happen if they're all spread around in a single studio.

Sorry, that's probably not the answer you're looking for but hopefully good enough for today.

Cheers,

Owen S.

owen_sparks

Have a read of the "Derive" feature help, this will allow you to do as you wish.

Also worth noting that as of the January update onshape has built in hardware options.

Hp that helps Owen S.

edward_casati

Thanks Owen,

I must be missing something... I can derive' an object, but where do I put the original that I am going to reference? When I 'derived' an object, and removed the original that I derived from, the derived seemed to go away also. I saw a couple of projects  that did what I want to do 'by reference'  (there was a 'link symbol involved) but I couldn't figure out where the referenced object was stored..
The hardware feature is nice, but it doesn't have the size nuts and screws that I need.... of course.  (sigh).
-Edward

philip_thomas

Yes, select the 'flatten' option on import

edward_casati

OK, now I feel just plain stupid.....
I can't find a 'flatten' option anywhere.
A) I download the McMaster part.
b) I 'import' the file by pressing the '+' at the bottom left of the screen.
c) A couple of options are presented, neither of which are 'flatten'. I leave the options alone and proceed.
d) The file gets imported into a new tab, plus a file that just seems like a redundant link to the original file.

No 'flatten'. No way to combine the two parts into a single tab that I can figure out.

(BTW... not a useless thread... there's something missing in the user interface that may be obvious to experienced users, but is not intuitive to us plain folk.)

konstantin_shiriazdanov

edward_casati said:

No 'flatten'. No way to combine the two parts into a single tab that I can figure out.

the flatten only is applicable if you improting the whole assembly, then if "flatten" selected all the part are imported in the same part studio. so you need to add your parts in some assembly first in another CAD and then import the assebly to OS

owen_sparks

Hi, although this seems like a simple use case I don't believe there is a simple answer to this.

As it stands OS doesn't have an "Import to this existing part studio" function, nor does it have a "move the contents of this partstudio to another existing partstudio".  If we're talking assemblies then that's easy, but not partstudios.

As you saw the derive has to derive a copy from somewhere so you can't delete the original tab.

I can think of a workaround of building as assembly of each and then doing an in context edit copy in place to get a PS with one of each in there, but that's a sledgehammer to crack a nut, and all the part properties will be lost, you'll just have Part1, Part2, yada-yada.

If your use case is just to tidy the document then I'd say make folders along the bottom of your document for each flavo(u)r of component and put individual partstudios in those with one component in each studio.  When you insert or derive these parts they'll all come in at the origin, which won't happen if they're all spread around in a single studio.

Sorry, that's probably not the answer you're looking for but hopefully good enough for today.

Cheers,

Owen S.

edward_casati

Thanks Owen and everyone else,
The 'create folders' answer is a great temporary solution,until something better can be devised. It still isn't the same as being able to import multiple parts into a single parts studio, but it's a good start!

owen_sparks

Hi Edward.

Sure thing.

One other thing I'd recommend is to add a mate connector to the part in your library part studio.  Then when the time comes to use the part the connector will come in with it too.  Sure they can be inferred from the geometry later but I prefer to have a predefined point that I know is being used each time.

I'm also hoping that in a future version of OS we'll be able to reference mate connectors along the lines of "Derived1.Mateconnector2" to make assembly configurations pretty much build themselves

Cheers,

Owen S.