Creating a simplified parametric fastener library
On some other threads we have been discussing the fastener library that comes with some versions of BricsCAD. Personally, I abandoned the provided library and started making my own. But, initially I was unaware that BricsCAD Platinum could do parametric 3D models. I see now that is a viable thing to do with parametrics, and that makes a fastener family a LOT easier to create.
I still have a lot to learn about the Mechanical module of Bricscad, and it will take some time for me to get a better handle on it. But, I thought I would start the discussion about how such a fastener library should be created.
My typical fastener is like the attached file with a 1/4-20 x 1" long Hex Head screw. Note that the head is without the normal curves, and that no thread is modeled. But the issue gets more complicated with other fasteners. For example on a 6" version of that screw, it is only partially threaded. I indicate this to myself by putting a circle where the thread stops. (example also attached. Note that these are all dumb solids)
For a flat head screw I indicate the Philips (cross) by drawing a 2D polyline on the head, and similarly for a socket head, rather than actually modeling the socket.
For a locking screw, I add a polyline on the side to show the nylon patch. Though this information might also simply conveyed in the block name.
As for the file name, since I did not use any fields in the drawing file, I opted to just put that info on the file name. English units don't do well on file name because the "/" is a problem The traditional solution is to use the underscore "_". I also used the - instead of a space between whole inches and the fraction. But, I would prefer the more proper nomenclature on the BOM. So, I imagine I should include some fields. For fasteners the description can do everything except the length, which is the parametric part. You may notice the McMaster part# on the locking fastener. Again, this is probably better handled as a field.
Is there any sort of standard for the fields that I should look towards? or perhaps they should be attributes? Any other comments?
This discussion has been closed.