Solidoodle announces Highres printing (Page 2 of 4)

Sure wish I could calibrate my machine, hopefully the new ATMega 1284P WITH a BOOTLOADER that I had to buy gets here before the release. Guess I should have spent a lot less time dreaming someone would answer their email and ponied up for one a long time ago.

It's hard to say without flow being right.  You can match your E steps/mm to mine by adding M92 E109 to the beginning of the gcode.  It will last until you reset or power off.

is this going to be a skeinforge or slicer profile?

I've got slic3r profile already worked out at 0.1mm that works fine.
but I've decided that I prefer skeinforge as a slicer as the code that comes out the end is easier for me to understand (and reposition models to avoid my beds deficiencies).

I started testing a 0.1 and a 0.05mm profile for skeinforge, but it's just a pain to use.

I just got my SD last week and have been playing with it ever since. Will I have to update the firmware to do this or will I be able to do this with my " straight out of the box" firmware?

Have you tried changing the settings for support? Altering the angle at which is kicks in is a good start. Use the g-code preview in Repetier-Host to visualise the changes.

Hello,
I am trying to print a "simple" cylindar.

It must be sliced with Skeinforge because it needs support material (due to a rounded bottom and overhanging flange at the top).

BUT, I keep getting the following memory error from Skeinforge.  I think I am somehow overloading my computer (i5/8gb ram), by having it slice a large, yet simple, cylindar.  It may be related to the endless number of polygons needed to represent the curve of the cylindar wall.  The only way I can get it to output a g-code file, is if I drastically reduce the resolution via Autodesk, and then again via meshlab.

This is such a simple part, why do I keep runing into this memory error?  Does anyone know how to fix this?  It processes for hours in skeinforge.  And, even though Slic3r can process and output g-code in just a few minutes.... It Doesn't Appear To Add Support Structures AHHHH!!

Here is my error output via the python window (everything looks fine until the very last second when it needs to save the file):

Exception in Tkinter callback
Traceback (most recent call last):
  File "C:\Python27\lib\lib-tk\Tkinter.py", line 1410, in __call__
    return self.func(*args)
  File "C:\Users\d\Skeinforge\5
0_reprap_python_beanshell\fabmetheus_utilities\settings.py", line 1173, in execu
te
    self.repository.execute()
  File "C:\Users\d\Skeinforge\5
0_reprap_python_beanshell\skeinforge_application\skeinforge.py", line 592, in ex
ecute
    skeinforge_craft.writeOutput(fileName)
  File "C:\Users\d\Skeinforge\5
0_reprap_python_beanshell\skeinforge_application\skeinforge_utilities\skeinforge
_craft.py", line 135, in writeOutput
    return pluginModule.writeOutput(fileName, shouldAnalyze)
  File "C:\Users\d\Skeinforge\5
0_reprap_python_beanshell\skeinforge_application\skeinforge_plugins\craft_plugin
s\export.py", line 294, in writeOutput
    window = skeinforge_analyze.writeOutput(fileName, fileNamePenultimate, fileN
ameSuffix, filePenultimateWritten, gcodeText)
MemoryError

Ian posted a link to that Kisslicer thread on page 1.
Here it is.

I haven't tried it in a few versions, but I kept running into models where it wouldn't generate support where it was clearly needed, despite the option being activated.  That might be the case here, but definitely check that it is activated.  I usually keep it turned off unless I know for certain that I want it.

Although new to 3d printing, I think support material is extremely important. I think I will probably need it for 1/2 of my small plastic engineering projects.  I didn't even see a feature for a raft, but perhaps I need to look further.

Skeinforge makes support material seem simple, when it can process my files.  The frustrating thing is that it gets 99.99% done, and produces the 2 images of the output, but then has this error when it tries to save the output the g-code. 

Is there any way to improve the performance of newest skeinforge on a 64 bit windows system?  I definitly have support turned on in Slic3r, and I varied the min angle between 5 and 80 degrees.  Support is just not showing up on the screen where it should be.  I suppose I could just try to print anyway, to see what it actually is trying to make.

Eventually I may try kissslicer.  I would like to stick with the standard "approved" programs though.

Aron

p.s Which filament provider has the best quality/cost ratio at this point?  I'm getting low....

My first Yoda at 0.1

Sliced with Kisslicer, settings copied to Ian Johnson, with minor modifications (no fan, 1.72 ABS diameter...)

The right side of Yoda is really good.  The left side not so much..., rough and the ear seems burnt.

Maybe I should try at lower temperature, since I can not install a fan...

Aron, if you have been running Skeinforge through Pronterface, then that error doesn't really mean anything.  The gcode should still be getting saved anyway.

For running the current Skeinforge more quickly, look up Cura.  It is a front end for Skeinforge 50 that runs it under PyPy, which is a kind of sped up version of Python.  I think the current download of Repetier (which includes SF50) also automatically sets it up to run under PyPy as well. 

Cura adds a couple of features to Skeinforge, such as fan control and a thing called Joris.  If you are going to print a single walled hollow item like a vase or cup, enabling Joris will have it print in a single spiraling move.    The Z will change constantly rather than in steps that leave a seam up the side.

If you're really stuck, it might be worth designing your own support in the model. I did this for the mk2 extruder and it takes away any grey areas. The final surface was perfect, and the support did its job.