-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate STL files from SparkFun library for "Standard Library" #17
Comments
From my notes:
Once the plugin is installed you can import a
I also found a reference on how to run a Ruby script within SketchUp from the command line: "Is there a command line in Google Sketchup to export in 3ds or fbx format?" |
ComponentsThe SparkFun Eagle libraries repository is here: https://github.com/sparkfun/SparkFun-Eagle-Libraries AFAICT there is no explicit mapping within the ModelsThe SparkFun 3D model repository is here: https://github.com/sparkfun/3D_Models It seems to have grown somewhat haphazardly (e.g. varied model source formats, export formats and naming conventions) although it looks like there's some attention being paid to tidying it up currently. There are two categories of models, split between the Most individual part models (associated with the SF Eagle libraries) are found in |
In order to determine part/model coverage and how many Summary of
A "valid component" in this sense is one for which both a SketchUp source file and exported "No sketchup file" means that an And the "No STL file" category are the models for which we need to generate STL files. There were also additional cases where neither Further analysis of |
With the information from the model scanner it's possible to determine how much model coverage there is of the SparkFun Eagle libraries (via
(Note that the package total includes duplicates due to the "same" part (in name, at least) appearing in multiple libraries.) For a clearer view of the model coverage it's helpful to look at the individual libraries (this is a count of models found (in either
Note that some packages (e.g. ones in In other cases package names have an suffix (e.g. It doesn't appear at first glance that there is very high model coverage in most cases, although manual mapping of alternate names would presumably help. (If desired I can attach the output with the complete per-package model coverage.) |
The third scanner uses the component model information to determine coverage for specific board designs (via
Additional details show that in most cases the "missing" models for SparkFun boards tend to be for packages that don't actually require a model. SummaryThis initial analysis seems to confirm the value of providing a standard library with mappings because otherwise the amount of effort required to get useful results is non-trivial (especially given there are many additional sources of models (which vary in quality and comprehensiveness)). Although there are potential concerns around comprehensiveness vs load times which may need to be alleviated. With these tools and this analysis we can now track progress as we automate the generation of models and create the mappings. |
Pushed commits with missing batch generated STL files (Note: GitHub will try to render all these files if you click on the commit links):
These were generated by automating SketchUp and then baby-sitting the automation. Baby-sitting was required because the exporting seem to fail non-deterministically with either segfaults or Ruby errors. Eventually re-running the automation enough times generated all the files. (This was using SketchUp 2015.) |
We might want to transfer the branch/fork from my account to Omniblox if we're going to offer to push the generated models back to SparkFun. |
Script used to automate the generation of the STL files: https://github.com/Omniblox/pcb-component-models/blob/master/tools/generate_missing_stl.rb (So we can use it again if we decide we want to use a different model format.) |
With generated STL files in place (via
The 2 "No STL file" items are due to difference in handling of case insensitive file systems. Thus 110 more valid components. Note that due to duplicate names this is fewer than the number of generated component models. |
when you want to work in the main repo - flick me a pull request from your fork. after that then branch the main repo |
These are currently located here: https://github.com/Omniblox/pcb-component-models |
Current status:
|
PR created: sparkfun/3D_Models#238 |
Ideally we'll automate this. Need to investigate how straight-forward automated export is.
The text was updated successfully, but these errors were encountered: