get complete BOM

[AxTheB]

We need complete BOM. There is sparse thingdoc info, Nathan said something about his BOM library for complete-printer.scad

[psytek]

I'm building a Prusa3 and this would be great to have.

[arrfonseca]

Me too!

[psytek]

http://www.kitbom.com/eric.beland/prusa-i3-prerelease

[HereC]

I wrote that bom to try and organize things. Some things in there are probably wrong. I'm in the middle of building this myself, and I'll review it after to see how close I came. Don't view that bom as more than a starting point at this point (I'll take down the warnings in the comment if I correct it)...

[HereC]

Also, I am NOT an i3 dev. So that should probably double your grain-of-salt taking-it-with. :-)

[psytek]

@HereC here is a nice picture if you'd like to update the BOM picture http://www.flickr.com/photos/prusajr/8107645350/in/photostream I'm going to be building about 8 of the i3s so maybe we can share notes through the BOM - thanks for at least getting something started.

[garlandkr]

Has this been completed/worked on? The reprap wiki page and others are very confusing. Especially for the different types of i3 (box, single frame)

[maborg]

yes and is incredible cool. You can see a video of the workshop with Prusa here: http://vimeo.com/maborg/prusa-workshop-arduino-torino-fablab
Somebody known where is the full "blueprint" for the printer ?

[Thav]

@AxTheB, I'm interested in working on this. If I understand thingdoc correctly (and while I've installed it, I've never tried hard enough actually compile an example), comments would go in each of the individual SCAD files listing the parts required for that piece or assembly, then thingdoc would parse out those comments and compile the BOM. I think this is one of the better ways of going about it, so that screws don't have to be counted through every part or at a top level. The limitation I see with that is if someone wants to a do an imperial variant, it's not possible to modify the BOM just through configuration.scad, like you can with the actual parameters of the screw. Anything to make this possible would probably require MORE pre-processing of the SCAD files, and I wouldn't want to take that on day one.

@nophead is very thorough with the Mendel90 BOM (https://github.com/nophead/Mendel90/tree/master/mendel/bom), but with the way the source is managed and the number of contributors to this repository may make it more difficult to maintain here.

Any thoughts on a direction to take?

[AxTheB]

The problem is that by change in configuration.scad can result in chabge in bom - change to bushing*, idler_bearing or i_am_box results in different BOM. I am not sure if thingdoc can cope with it.

[Thav]

Maybe there could be some generic things, like "X axis idler bearing", and whether it gets selected as 624 or 608, it still gets counted, but then its on the user to add their individual line items of 608s up. It's more convenient because it's still in one place, but still a problem.

[nophead]

The BOM generation on Mendel90 is fully automatic, so it doesn't matter how many contributors there are, it would always be correct as long as any new modules that draw vitamins have a vitamin(...) call and any new modules that create STL files have an stl(..) call and are named with an _stl suffix,

[Thav]

Oh! It certainly looks like I didn't read far enough into it. From the text files in the bom directories, they looked meticulously hand generated. Maybe that should have tipped me off that they were so perfect. I guess it will be worth digging in to how you're doing it then.

[nophead]

Its is done with echo statements and a python script that runs the command line version of OpenScad and captures the echos and creates the bom from that.

[AxTheB]

that looks great, i like it.

[Thav]

I've been looking at ThingDoc more. @AxTheB, I remember you saying on G+ that the tdoc stuff for this repo got out of date because there's no documentation on how to use ThingDoc. I 'm working on that part right now, peeling through the code. I like how it parses and uses an off the shelf templating module in python (jinja).

Maybe a solution here is to start echoing ThingDoc control keywords out to a .tdoc file as part of the OpenSCAD compile, then run ThingDoc against it. That way we may be able to make the templates very flexible.

ThingDoc also seems to have hooks for creating assembly steps and including images of parts (which maybe I can ask Miguel Sanchez for his renderings http://www.youtube.com/watch?v=cWUkTEl3bZE), but that's issue #8 isn't it?

[Thav]

Updated the README on ThingDoc so we can see what it does.

https://github.com/Thav/ThingDoc

[Thav]

Got some skeleton ThingDoc definitions going in my fork.

Bill of Materials: Prusa i3 RepRap
++++++++++++++++++++++++++++++++++

Rods and Bars
=============
- 1x Idler

Vitamins
========
- 5x 608 skate bearing
- 2x M4 nut
- 1x M8 Threaded Rod
- 3x M3 10mm screw
- 2x Linear Bearing
- 1x M10 nut
- 2x M3 10mm screw with hex head
- 1x M3 25mm screw

...and so on. I'll try to get quantities right according to manual.txt, then make some assembly "things" where I can start storing the steps from manual.txt.

[ghost]

Has anyone actually managed to produce an actual BOM without skipping anything or assuming single-plate?

I've been looking on and off at building an i3 for at least 3 years now and have still never managed to find anything of a complete bom that isn't without variant specific issues.

[andrewtoler]

I took the i3 parts scad files and adapted them for my needs, one by one.
After printing some of the originals, I realized that they all needed work,
such a moving bolt holes, adding in mount points for end stops and
thickening some surfaces for strength. I also designed a "basket" holder
for an mk extruder because there was no file in existence for that. So all
of it had to be customized. OpenSCAD, FTW.

On Friday, September 18, 2015, Belxjander [email protected] wrote:

Has anyone actually managed to produce an actual BOM without skipping
anything or assuming single-plate?

I've been looking on and off at building an i3 for at least 3 years now
and have still never managed to find anything of a complete bom that isn't
without variant specific issues.

—
Reply to this email directly or view it on GitHub
#6 (comment).

[stormychel]

I think part of the fun is not having a complete BOM :)

[ghost]

makes life hell when writing a reprap build proposal where I have to
account for everything in advance of funding.

3on't get any traction in a Japanese publid school without it.
On 19/09/2015 10:52 PM, "stormychel" [email protected] wrote:

I think part of the fun is not having a complete BOM :)

—
Reply to this email directly or view it on GitHub
#6 (comment).

[andrewtoler]

-bags of M5 screws, nuts and washers of a few sizes.
-threaded rod, 2 types
-nuts and washers
-smooth rod
-linear bearings x12
-stepper motors x4
-couplings x2
-belt, about 5 feet or so
-pulleys
-extruder assembly
-heated bed
-power supply
-end stops x3
-wires
-RAMPS/Arduino (cheap Chinese knockoff from ebay is ok)
-wood or metal for the frame and bed carriage
-some tie wraps and wire wraps

Besides tools and printing all the plastic parts, that's it. It snaps
itself together effortlessly in about 3 months.

On Sat, Sep 19, 2015 at 7:00 PM, Belxjander [email protected]
wrote:

makes life hell when writing a reprap build proposal where I have to
account for everything in advance of funding.

3on't get any traction in a Japanese publid school without it.
On 19/09/2015 10:52 PM, "stormychel" [email protected] wrote:

I think part of the fun is not having a complete BOM :)

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

[ghost]

Too bad everyone gives off the impression that they assume I am doing this
for myself.

and that qnd bom appears wrong at least to me... oh well.
On 20/09/2015 11:42 AM, "Andrew WJ Toler" [email protected] wrote:

-bags of M5 screws, nuts and washers of a few sizes.
-threaded rod, 2 types
-nuts and washers
-smooth rod
-linear bearings x12
-stepper motors x4
-couplings x2
-belt, about 5 feet or so
-pulleys
-extruder assembly
-heated bed
-power supply
-end stops x3
-wires
-RAMPS/Arduino (cheap Chinese knockoff from ebay is ok)
-wood or metal for the frame and bed carriage
-some tie wraps and wire wraps

Besides tools and printing all the plastic parts, that's it. It snaps
itself together effortlessly in about 3 months.

On Sat, Sep 19, 2015 at 7:00 PM, Belxjander [email protected]
wrote:

makes life hell when writing a reprap build proposal where I have to
account for everything in advance of funding.

3on't get any traction in a Japanese publid school without it.
On 19/09/2015 10:52 PM, "stormychel" [email protected] wrote:

I think part of the fun is not having a complete BOM :)

—
Reply to this email directly or view it on GitHub
<#6 (comment)
.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

[gw2]

The BOM for an I 3 is awful, and there are many issues you need to fix
yourself. Build a different printer if it's a problem for you. Or make your
own BOM.
On Sep 20, 2015 12:49 AM, "Belxjander" [email protected] wrote:

Too bad everyone gives off the impression that they assume I am doing this
for myself.

and that qnd bom appears wrong at least to me... oh well.
On 20/09/2015 11:42 AM, "Andrew WJ Toler" [email protected]
wrote:

-bags of M5 screws, nuts and washers of a few sizes.
-threaded rod, 2 types
-nuts and washers
-smooth rod
-linear bearings x12
-stepper motors x4
-couplings x2
-belt, about 5 feet or so
-pulleys
-extruder assembly
-heated bed
-power supply
-end stops x3
-wires
-RAMPS/Arduino (cheap Chinese knockoff from ebay is ok)
-wood or metal for the frame and bed carriage
-some tie wraps and wire wraps

Besides tools and printing all the plastic parts, that's it. It snaps
itself together effortlessly in about 3 months.

On Sat, Sep 19, 2015 at 7:00 PM, Belxjander [email protected]
wrote:

makes life hell when writing a reprap build proposal where I have to
account for everything in advance of funding.

3on't get any traction in a Japanese publid school without it.
On 19/09/2015 10:52 PM, "stormychel" [email protected] wrote:

I think part of the fun is not having a complete BOM :)

—
Reply to this email directly or view it on GitHub
<
#6 (comment)
.

—
Reply to this email directly or view it on GitHub
<#6 (comment)
.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

[andrewtoler]

That bom I rattled off was composed while I was looking directly at my i3
that I built. At some point you have to take the bull by the horns and do
your own work on this...

On Sat, Sep 19, 2015 at 11:48 PM, Belxjander [email protected]
wrote:

Too bad everyone gives off the impression that they assume I am doing this
for myself.

and that qnd bom appears wrong at least to me... oh well.

On 20/09/2015 11:42 AM, "Andrew WJ Toler" [email protected]
wrote:

-bags of M5 screws, nuts and washers of a few sizes.
-threaded rod, 2 types
-nuts and washers
-smooth rod
-linear bearings x12
-stepper motors x4
-couplings x2
-belt, about 5 feet or so
-pulleys
-extruder assembly
-heated bed
-power supply
-end stops x3
-wires
-RAMPS/Arduino (cheap Chinese knockoff from ebay is ok)
-wood or metal for the frame and bed carriage
-some tie wraps and wire wraps

Besides tools and printing all the plastic parts, that's it. It snaps
itself together effortlessly in about 3 months.

On Sat, Sep 19, 2015 at 7:00 PM, Belxjander [email protected]
wrote:

makes life hell when writing a reprap build proposal where I have to
account for everything in advance of funding.

3on't get any traction in a Japanese publid school without it.
On 19/09/2015 10:52 PM, "stormychel" [email protected] wrote:

I think part of the fun is not having a complete BOM :)

—
Reply to this email directly or view it on GitHub
<
#6 (comment)
.

—
Reply to this email directly or view it on GitHub
<#6 (comment)
.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).