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.
Instantiating a library
How to create a library for a company using Onshape. It also works for individuals.
Features of this instantiated library:
- no maintenance
- no admin
- easy to find & reuse parts, part studios or assemblies
- creates a repository for assemblies that have inheritable motion
- it's free, professional licenses are easier to setup
- wish I had done this along time ago
When inserting into an assembly, just use a filter:
- "lib" is a custom property I created; you can call it "anything"
- lib is a boolean with only a true/false state
- lib was created for only parts, part studios & assemblies
- click it true and only library components show up when inserting
Highlighting parts shows only parts in the library:
- currently there's only 1 part & 1 assembly in my library
Highlighting assemblies shows only assemblies in the library:
- Here's the only assembly in the library
Adding vendor to search filter:
- shows library components from this vendor
- if the vendor field is empty it's ignored
- the vendor field is case insensitive ie.. rusty shed equals Rusty Shed
This seems like a good pattern to reuse geometry and it's fast. Having a library of moving slides, cylinders, clamps.... will help develop automated equipment more quickly. There's not much to setting it up except to say, "I'm going to do it". If you work with multiple people, everyone should agree to a standard of some kind. Remember garbage in your library means garbage out of your library.