Skeinforge Build Parameters

The extrusion settings, more or less, kinda-sorta, for the latest objects:

  • Layer thickness 0.33 mm
  • Perimeter w/t = 1.75 = 0.58 mm
  • Fill w/t = 1.65 (or as needed)
  • Feed 40 mm/s
  • Flow 2 rev/min with geared stepper
  • Perimeter feed/flow 75% of normal (probably not needed)
  • First layer at 20% of normal feed & flow
  • 210 °C (some at 220 °C) Thermal Core
  • 120 °C build platform (lower at plate surface)
  • Reversal: 20 rev/min, 90 ms reverse & push-back (lower better?)
  • Fill: 2 extra shells, 3 solid surface layers, 0.25 solidity, 0.3 overlap
  • Thread sequence: Loops / perimeter / infill
  • Cool: slow down, minimum 15 sec/layer
  • Bottom / splodge / stretch disabled

Wouldn’t it be great if you could export all that stuff to a text file in a readable format? The CSV files come close, but they’re not really meant for human consumption.

Subject to revision, your mileage may vary, past performance is no indication of future yield, perfectly safe when used exactly as directed, shake before using, don’t touch that dial!

4 thoughts on “Skeinforge Build Parameters

  1. Hi, i’m not sure if this would be useful, but I wrote a small groovy script that parses the csv files from Skeinforge and writes out a rudimentary html page with the values in a table. A slightly modified example is at the bottom of my latest blog post if you want to have a look.

    It would be pretty straight-forward to make the script write out a nice text file instead. I have been planning on doing this when I next get a moment as I think it would be very helpful if there was an easy (standardised?) way to share and compare Skeinforge settings.

    Obviously a module direct in Skeinforge would be optimal – but i’m not a python scripter so it may take a while before I could contribute something there.


    1. Looks good to me, but another language? Ouch!

      I suppose I’m hopelessly retro, but I like plain old text rather than HTML or (ugh) XML…

      Given the number of knobs & buttons in Skeinforge, XML might actually be a better choice for machine parsing. Indeed, having Skeinforge use XML config files rather than CSV would probably be a straightforward, albeit wrenching, change, after which you could export to flat text for annotation & suchlike.

      I am cognizant that nothing is difficult for the guy who doesn’t have to do it…

  2. > Wouldn’t it be great if you could export all that stuff to a text file in a readable format?

    I’ve been thinking for several months now that a “transportable profile” for 3D printers might be better as a set of preferences with values in the 1-100 range (or 1-10 or 1-42 or whatever) and with weights to say which preferences are more important to the user. Things like horizontal and vertical resolution, object strength, print time, etc.

    With that sort of setup, and with another set of values that define the capabilities & properties of your given machine and feed stock (plus a whole bunch of TBD coding), you’d have something that could be used on any sort of machine, regardless of if it prints on the scale of microns or of meters.. It’d also let object designers say things like “this really needs to be printed with strength set to 75” and such.

    Progress is slowly being made in this direction but we’ve still got a ways to go…

    1. a “transportable profile” for 3D printers

      I like it, but wow the number of knobs seems daunting. Even if most parameters change only secondary aspects, I wonder how effectively the capabilities of different printers will distill into a common set of preferences. The knobs seem to interact in mysterious ways, too, and I’m sure different printers have different interactions.

      Takes your mind off all your other problems, that’s for sure…

Comments are closed.