Integrated Parametric RepRap developments

I finally have had time to start working on my IPR project again.  I have a set of prototype parts printed out and have cut plywood sides and rods.

Although I already have several things I want to change I plan to assemble it as much as possible before making any changes. I expect to assemble it a few times before working out all the bugs.  So far I like how it is coming together and think this is a good compromise between a Sell's Mendel and a Prusa Mendel (Although it has much more in common with the Sell's).


I bought some T-Rex 500 R/C helicopter gears that I was thinking of using for a new extruder design but I think the main gear may be larger than I want.  I have some R/C car gears on the way that should be closer to the size of the stock Wade's gears (they may even work on a stock body).

There are more pictures on Flicker
 

First pre-release of Integrated Parametric RepRap

I just uploaded the first pre-release of my Integrated Parametric RepRap OpenSCAD files.  Currently it does not make anything printable but what it does do is "build" a parametric frame based on the settings in the DNA file.

The core files contain the following:
IPR_DNA: All constants and calculations, the constants define all the possible things that make a specific robot unique. (ranging from desired build space to fastener and bearing sizes)
IPR_func: All "standard" modules, such as motor mounts, bearing mounts, hardware models, etc... currently this file "builds" the main frame out of the hardware specified in the IPR_DNA file.
 


The following pictures show the frame with a 100x100, 150x150, & 200x200 build space with normal Mendel sized hardware (including a NEMA17 Z motor on the left).

100x100

150x150

200x200

This picture shows a 300x300 build space with larger hardware (608 guide bearings and 12mm rod).

300x300

This should give you an idea of the flexibility I am building into this design.


I plan to keep ALL constants and calculated values in the DNA file and everything else in a few files that call the DNA and func files.

Here are my current rules:

1. If it is a constant it lives in the DNA file.
2. If it is a calculation that effects parts (not positional calculations but dimensional ones) it lives in the DNA file.
3. If it is a module that anything else needs to call it lives in the func file.

The goal is to eliminate redundancy and simplify the whole process of generating a robots files.


For more information visit the main documentation at:
reprap.org/wiki/Integrated_Parametric_RepRap