[KwartzLab] 3D Printer: Next Steps
doug at moens.org
Thu Aug 25 12:53:16 EDT 2011
I wasn't slighting your software skills, you are just a more well
rounded maker than me.
If we are going to seriously fork the FiveD firmware, rather than just
fix obvious bugs, it would be good to do this by modding one of the
existing forks, rather than creating a new fork, if we can find an
existing fork close to what we want.
Here's a list of known firmware: http://reprap.org/wiki/Firmware
The Teacup firmware is a fork of FiveD that is apparently compatible
with our hardware (3rd Gen). It's a complete rewrite, actively
maintained. They've redesigned the way acceleration works (they
provide default RepRap acceleration, and a new acceleration mode that,
when enabled, allows faster printing. [*] Support from your gcode
generator is required for the "constant acceleration" mode to work).
Take a look at their wiki and see if it accords with how you would
like acceleration to work:
Teacup is also rewritten to run faster with less cpu, and that may
eliminate some potential sources of printing problems (software
lagging behind the hardware).
[*] Faster printing is also a key feature of the Sprinter firmware.
But Sprinter apparently requires new electronics.
Note to self: I found this information while googling 'skeinforge
teacup': "I also decided on downgrading to Skeinforge 31 as 35 and 39
both add a great deal of extras that 5D is not capable of handling."
Looks like I should start with Skeinforge 31 for my experiments with
our existing 5D firmware.
On 25 August 2011 12:11, Kevin Martin <kpmartin at thinkage.ca> wrote:
> Hey, I'm a software person too!
> I think many of the problems encountered are due to incorrect assignment of responsibilities between the GCode generation and the printer firmware. In particular, management of acceleration and synchronizing extrusion and motion should be entirely in the controller board. But unless we can identify some standard (or at least a convention) that commercial 3D extruder-style printers use (assuming they run from GCode) I don't see any ability to fix this without having to exist our own little bubble world. I'm not convinced that we have the sway to make the rest of the hobby 3d printer world see the error in their ways (or maybe it is just megalomania on my part...). I just know what I would do if I had the time...
> -Kevin Martin
> the Papertrail Handmade Paper & Book Arts
> New Dundee, Ontario, Canada
> -----Original Message-----
> From: discuss-bounces at kwartzlab.ca [mailto:discuss-bounces at kwartzlab.ca] On Behalf Of doug moen
> I'm a software engineer. I don't have Kevin's hardware smarts.
> Discuss mailing list
> Discuss at kwartzlab.ca
More information about the Discuss