boltsparts / bolts_archive Goto Github PK

Right now a table for every name of the part is generated. This could be avoided by generating a table only for every class.id.

http://reprap.org/wiki/Stepper#Size
http://www.pololu.com

The table data needs specified units

Currently the drawings used on the webpage to illustrate the general geometry and the dimensions of a base are pretty ugly and generated by a ugly, slow, homegrown OpenSCAD machinery.

1. Try how to do this in FreeCAD
2. Have a proper mechanism in the blt files to specify drawings
3. Write a contribution guide about it

check for possible errors
fetch Boltification issues?
Drawings
missing base geometries
missing optional fields

Have a field in the blt file indicating the source of the data.

General

How to fix an error in a blt file
How to add a new class to a collection
How to add a collection
Using git on your local computer
Using githubs webbased interface

FreeCAD

How to install BOLTS for FreeCAD
How to use BOLTS for FreeCAD
How to write a FreeCAD base file
How to write a Base Function
How to create a Base FCstd file

OpenSCAD

How to install BOLTS for OpenSCAD
How to use BOLTS for OpenSCAD
How to write a OpenSCAD base file
How to write a Base Module
How to create a STL base file

http://www.numberfactory.com/

Stuff about nuts and bolts and NEMA motors, check what can be used

Thread for permissions

http://sourceforge.net/apps/phpbb/free-cad/viewtopic.php?f=21&t=2268&start=0

The question is, what to put there and what to keep on BOLTS page

Either generate the init.py or research dynamic module loading.

I think it is a good idea to separate the scripts used to manage a number of collections and the collection data itself into two repositories.

generate a function for each part to get the values for all parameters to allow to write more general code.

this can be also used to simplify the generated stub

http://en.wikipedia.org/wiki/Pipe_%28fluid_conveyance%29#Sizes
http://de.wikipedia.org/wiki/Rohr_%28Technik%29#Abmessungen
http://de.wikipedia.org/wiki/Nennweite
http://en.wikipedia.org/wiki/Nominal_Pipe_Size

Have nice navigation menu similar to docs

http://www.artofillusion.org

written in java, scriptable and extendable via plugins. Not sure how many people use it for CAD though and whether it is a worthwile target.

http://www.wd-bearing.com/en/Linear-bearings/LM-UULM-UUAJLM-UUOP.htm#.UmZbznhb_0o

So that the GUI widgets can be chosen appropriately.

For start I think
String, Enumerated Type and Numbers
are sufficient

There is something similar to BOLTS already:

http://brlcad.org/w/index.php?title=Hex&oldid=4605

The workflow looks a bit awkward.

Like Nopheads BOM mechanism from https://github.com/nophead/Mendel90?source=cc

or better yet a mailing list.

I think it is a good thing to keep track of authorship and licenses as precisely as possible from the beginning.

However there can be many different licenses and copyright stakeholders:

The base modules/geometries/functions have one or more copyright holders and a license.

The blt files have copyright and license

The core tools have a copyright and a license

Generated code is afaik under the same license as the blt and/or base modules.

What are appropriate licenses for the data? http://opendatacommons.org/licenses/odbl/1.0/ ?

What licenses fit together how?

Make BOLTS a nice macro, as suggested by yorik here:

https://sourceforge.net/apps/phpbb/free-cad/viewtopic.php?f=8&t=4549#p35626

How does this interfere with my development workflow?

Here
https://github.com/yorikvanhavre/FreeCAD-library
and here
https://sourceforge.net/apps/phpbb/free-cad/viewtopic.php?f=19&t=4205&start=0

there are a lot of parts that might be useful to have in BOLTS.

Requires #3 to be fixed first

I require a url for every license, but if the license terms are unclear, there is no canonical page for that.

Therefore a page explaining the implications of unclear licensing should be created on the BOLTS Webpresence

But I think there is not very much that BOLTS does not have. Maybe checkout forks on Github.

https://github.com/SolidCode/MCAD

maybe a few special functions whose verbosity can be set conveniently

Tasks fall in different categories.

Smells

Should go to Task list. Requires a mechanism to mark false positives, probably a extra file to specify ignorances.

• Table checks, can reuse some code I have written in the past (https://github.com/jreinhardt/bolttools/blob/3c924e1a702dd77be99b1418095cd781149d54b9/checker.py)
• missing standard from Standardisation Organisation. One would expect that all standardisation organisations have standards for a kind of part. (Not doing it, not robust enough)
• missing optional fields, short descriptions (not doing it, not robust)
• missed connections. If the set of classids for base geometries for two different backends have a non empty intersection, then it should be possible for each of the base geometries to take care of the union of the sets of classids.
• parameter names should conform to [a-zA-z][a-z0-9_]*
• notes (not doing it, not robust)

Errors

Semantically clearly wrong and have an obvious fix. Check for during blt parsing?

• Non-unique class ids
• wrong spelling for bool values (uppercase required)
• License from set of allowed licenses.

contains some points from #17

There are quite a few parts readily modeled.

https://github.com/nophead/Mendel90/tree/master/scad/vitamins

• Blog more
• get it into planet.arcol.hu

How should the syntax be to position and orient a part? How to indicate that I want to subtract a part to create e.g. a nut trap?

(similar to #20)

Ask on the mailing list

What do I need for infrastructure?

The BOLTS part selector should have a widget that shows more detailed informations about the Standard, Collection, Part that is currently selected

Could also provide a button to open the corresponding BOLTS specification page

This would allow to also provide downloadable html documentation and avoid many "updated from master" commits.

see e.g.
http://www.astbearings.com/http://www.astbearings.com/

Generate a list of contributors, maybe ranked by contributions

http://www.reyher.de/download/REYHER_Technische_Informationen.pdf
http://www.reyher.de/download/REYHER_Genormte_Verbindungselemente.pdf

Also has a table with corresponding DIN/ISO/EN standards.

The screwmaker macro
http://freecadweb.org/wiki/index.php?title=Macro_screw_maker1_2
contains some screwtypes that are not yet supported, and has in general nicer geometries.

It is licensed und lgpl, so no problem here.

http://www.thingiverse.com/thing:30136

1. Understanding and writing blt files
2. Building base module for OpenSCAD
3. Building base functions for FreeCAD

It would be nice to have a BOLTS distribution in STEP format. This would allow users of most CAD applications to profit from BOLTS.

1. The export should be automatic
2. How does STEP treat parametric dimensions?

Possibility 1:
Disable the add button when no document is active. This requires signals when documents are loaded.

Possibility 2:
Just give a message with FreeCAD.Console with the problem

single row radial and sealed ball bearings have same standard name. Need to unify them. Maybe problem with

It would be nice to have a mechanism to boltify parts in fcstd format. This requires several steps:

1. A appropriate mechanism to specify this kind of base in the blt file
2. A suitable directory structure to store the fcstd files
3. A loader that can load the parts and adjust parameters according to the blt file
4. Check that licenses are compatible

Sometimes one wants additional parameters that are not specific to the part, but to the base. For example to choose between a very detailed representation that looks great (with a real thread for bolts or all the balls for bearings) and one that is more schematic.

Would need to add that to the spec and implement it.

to work around a performance issue with tori.

author, license, notes

source for basefile element