Topic: Slic3r 1.1.5 vs 1.2.1

Home Forums Chatter Slic3r 1.1.5 vs 1.2.1

This topic contains 14 replies, has 7 voices, and was last updated by Profile photo of Alain Alain 1 year ago.

Viewing 12 posts - 1 through 12 (of 15 total)
  • Author
    Posts
  • #10124

    René @3dnerd

    Hi,

    On last weekend I did a testprint with slic3r 1.1.5 which comes with AutoMAker 1.00.16. I printed using ABS in normal setting.
    The result was not so good. There were a lot of slicing errors as you can see here:

    Please follow the numbers beneath the red arrows:

    1: A part of a path was not visible in the gcode in all layers so it is missing on the print as well.
    2: The small parts were only printed as outlines, but they were designed full filled.
    3: This wall is 0.3 mm, so just one path of the 0.3 mm nozzle. In some layers a part of the path was not visible in gcode, so the upper parts printed in the air and did not contact the layers underneath. In areas where all layers were printed it was very easy to break upper layers apart. It seems the layers stick not very well.
    4: The start of the vertical wall was fraying

    Since I was not satisfied with the result of slic3r 1.1.5 I tried slic3r 1.2.1 (experimental).
    I renamed the slic3r folder inside Automaker->Common into slic3r115. Then I dowloaded the slic3r 1.2.1 zip and unzipped it into the Automaker->Common folder.
    Then I printed the same model again. The result was much better as you can se here:

    1: The wall was now visible in gcode and was also printed successfully.
    2: The small parts were printed correctly, full filled no more just outlines.
    3: 0.3 mm wall, no missing parts inside some layers anymore, all layers were printed one on top of the other, the problem here was that it was very easy to break upper layers apart. It seems the layers stick not very well
    4. The fraying is reduced, but you can see some gaps, this is similar to the problem 3 that the layers do not stick very well.

    But as you can see the result is much better compared to slic3r 1.1.5, so I recommend to use only slic3r 1.2.1.

    Here some questions:

    1. Overall there is a lot of blobbing, is there any way to reduce it? Is this a problem caused by slic3r or is it a problem of AM and/or printer settings?
    2. How can I avoid the gaps between the layers, it seems they melt not really together

    Thanks!

     

     

    #10142

    pelgrim @pelgrim
    My Robox is a Green Kickstarter Early Bird

    guess me must hope and pray CEL uses the last clic3r version for the next AM release ?

    java (EE), JavaFX, HTML, GIS) programmer, database wizard, framework inventor, looking for a job ! http://roboxing.com/wizards

    #10184
    Profile photo of
    Anonymous

    Well, that’s encouraging to a degree I guess. Though it looks like the blobbing has got worse in 1.2.1 at the price of better accuracy!

    Did you notice if the blobs occur at the start of a nozzle move or the end? It’s just the blobs are present on the external corner of the second piece and not the first, so I wonder if the gcode has altered in some way just there. It might give us a clue on how to fix the blobbing.

    #10229

    René @3dnerd

    Hi,

    for better analysis I added now the zip-files of the printjobs.

    • This reply was modified 1 year ago by  René.
    Attachments:
    You must be logged in to view attached files.
    #10269

    dave @dave

    I tried Slic3r 1.2.1 but it seems it doesn’t position the prints correctly on the bed; Is there a setting that needs to be altered in Slic3r to get this right? If I position something in the center of the bed it just prints in the top left instead.

    #10272
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    I have noticed that too. I was planning to make another topic here explaining debugging of that process (running Slic3r through AM and then manually and trying to figure out why is that so). Didn’t get time/chance to do it, yet.

    #10317

    René @3dnerd

    @Clicky: I found something about print bed position in slic3r 1.2:

    http://kuehlingkuehling.de/2014/08/26/behold-the-new-slic3r-v1-2-0-experimental/

    #10318
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    That makes sense. When I get chance I’ll have a look at it, too. Maybe we need a light ‘pre-processor’ (post slic3r anyway) for it to work - something that will move result gcode back to where it is supposed to be…

    #10333
    Profile photo of Aimdy
    Aimdy @mistsoul
    My Robox is a Blue Commercial Version

    not sure if this affects 1.2.1 but something I have experienced with 1.1.7, is that it would print correctly for half of the print and then shift to a different y axis for the second half of the print, this made the parts completely useless. Hopefully a stable version comes out soon.

    Moh

    #10334
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    I am sure that’s different problem. Can you share gcode of that print?

    #10536
    Profile photo of Aimdy
    Aimdy @mistsoul
    My Robox is a Blue Commercial Version

    @clicky, possible but the problem stopped when I went back to the original AM version of Slicer. I still experience this but is often a slight offset and not as pronounced as when I had 1.1.7. Do you mind going over how to properly switch slicer from 1.1.5 to 1.2.1, perhaps I did it incorrectly.

    Moh

    #10545
    Profile photo of click
    click @click
    My Robox is a Green Kickstarter Limited Edition

    No - I am sure there is nothing wrong they way you did it. It is just as it is - AM hasn’t been made for Slic3e 1.2.x :(…

    You have choice of problem with positioning and good walls or crappy walls wherever you want to position your object to. Hopefully incoming new version of AM will fix it… Until then - have both Slic3rs handy and switch them depending on how wrong you want it!

Viewing 12 posts - 1 through 12 (of 15 total)

You must be logged in to reply to this topic.