Could we possibly set up a table of SW/firmware being used

With several diffrent configurations of SW / Firmware and hardware being used on repstraps and repraps.
Could we have some kid of look up table to identify the most popular confiurations.

The table could also be used to provide statistics on the number of reprap and repstraps printers out in the wild. Maybe we include tick boxes to indicate the state of the build. when it has xyz movement its 1st print... etc

---

Bodge It [reprap.org]
=======================================

---

BIQ Sanguinololu SD LCD board	BIQ Stepcon	BIQ Opto Endstop
BIQ Heater Block PCB	BIQ Extruder Peek clamp replacement	BIQ Huxley Seedling
BIQ Sanguinololu mounting	BIQ standalone Sanguinololu or Ramps mounting	Print It Stick It Cut it

My rep strap: [repstrapbertha.blogspot.com]

Buy the bits from B&Q pipestrap [diyrepstrap.blogspot.com]
How to Build a Darwin without any Rep Rap Parts [repstrapdarwin.blogspot.com]
Web Site [www.takeaway3dtech.com]

Manual entry:
DIY design loosely designed on the McWire, but more heavy duty.
Now designing Arm Cortex STM 100 pin controlled all in one PCB with integrated 4Ch Stepper control, with the various additional I/O to complete. 4'th axis on board to be stepper motor control of extruder.
Graham Daniel.

Sounds like a Builder's Wiki page - here's my setup:

Hand cast Bits from Bytes Darwin, with many self built replacement parts now.
Arduino (soon to be Sanguino) running Gen 2 electronics
badly hacked Gcode Interpreter Experimental from Zach's repo running on the Arduino
Replicator G compiled from repository to send the Gcodes to the Arduino, Ubuntu 8.10
Skeinforge to slice the STL's (Ubuntu)
EMC2 on VM (realtime version of Ubuntu) to check the Gcode paths before builds
Blender on Ubuntu to fix and rotate simple STL errors.
Alibre (free version) running on a WinXP VM for major edits or creating new STL's.

The data that needs to be heavily edited (Alibre to Skeinforge to EMC2) ends up passing through 3 different computers before it hits the Darwin; there's probably room for some streamlining there.

Wade

edit - I almost forgot, I use Ubuntu's default text editor to add offsets and cut and paste multiple Gcode files together; thus the need for EMC2 to check for errors. That could also be automated.

Edited 1 time(s). Last edit at 01/21/2009 10:29AM by Wade Bortz.