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.
Product Names for Standard Hardware
Nath_McC
Member Posts: 127 PRO
Is there a easy way to update all of the product name and description meta data in the standard content hardware at once?
I mean without having to load each model and update the custom properties one at a time. Im thinking something similar to the layout of the toolbox grid in Solidworks.
I dont want to add or amend any of the standard data just bulk update the hardware product codes to use our internal one.
I mean without having to load each model and update the custom properties one at a time. Im thinking something similar to the layout of the toolbox grid in Solidworks.
I dont want to add or amend any of the standard data just bulk update the hardware product codes to use our internal one.
Tagged:
0
Answers
Yes, kind of.
It is not fully thought out yet, but I am thinking doing something like this.
Assembly tabs represent fastener standard.
Folders in assembly represents the different configurations
But it might be cleaner to have one assembly tab represent an narrower scope, like "ISO 4762, 12.9 class" or "ISO 4762, A4 Stainless Steel".
It depends on how hard it is to maintain this system. I like having as many bolts as possible in the BOM table at the same time. Then I can sort by material or finish when doing edits to the Part Numbers and Decriptions.
There are potentially hundreds of variations to add metadata to, which is another reason to try to standardize types of bolts in our products.
One more thing: I created a custom property called Finish, which has a selection list similar to the one available in the Standard Content Menu. This wasn't available as a default column, strangely enough.
Hope this helps! Would like to know you thoughts on this and possible improvements.
There are way too many options, It's hard to find the "common" stuff we use normally.
People will tend to miss one of the options and then the BOM will have two separate parts, that should have been identical.
Some fasteners are missing. Some are modeled incorrectly, some have way too much detail.
I re-invented it here for us.
Feel free to copy it. (I never got far on the INCH portion, since we hardly use Inch anymore)
AEINC Fasteners | AEInc Fasteners METRIC (onshape.com)
Just update the CSV to add configurations.
Everything is modeled so it will output the same part model.
That way you don't have to "replace instance" if you go from a washer to a bolt or whatever.
It's just one part to fasten them all...
The Part number and Part Description is automatic based off configuration options too.
the downside is, There is no way to filter for valid parts.. example: you can configure a M6 flat washer with a length of 80mm.
Well obviously, washers don't have a bolt length. So the part will just fail until you set length to N/A
So if you want to get a bolt that is some size and length, and it isn't specified on the chart, then it will just fail. So it can be a guess and check to find valid lengths.
But if a length isn't on the list, it can be added very quickly.
The only thing the featurescript is doing in in this case is parsing the CSV.
What do you mean counter sink hole with nothing inside?
If you want to invoke our AI overloards. Then you will need to write something up using the API.
But at that point, you are far off into the weeds of complexity for just a bolt name.
There is a bit of a chicken and egg situation with fasteners, if you start from the assembly and throw fasteners in then it would be nice to have the fastener create the required features in the parts. You can to some extent use assembly contexts for this, by for example using a boolean (with offset) for the clearance holes but if your parts are in multiple part studios you will need to use multiple contexts etc...
However if you define the fastener locations in the part studio, then the "correct" fastener to use in the assembly isn't necessarily straightforward. You might have a bunch of identical threaded holes in a part that are used for fasten different things in the assembly and would use different fasteners.
That said there is a lot of room for improvement: the "insert" dialogue let's you pick the hole feature to match the thread size but it won't update if you change the feature.
I think if/when we get Featurescript in the assembly environment these sort of things will become a lot more feasible.
You gain a bunch of useful information using the hole feature.
Hole tolerance, standard clearances, thread pitch, etc.
You would have none of that using a boolean feature that comes from in context. And you would rely on your user to know all of the standard clearances.