Sequential prints shown as parrallel

[k2OS]

I'm not sure if I am missing an option somewhere, but I seriously thought slic3r didn't want to make sequential prints as gcode.ws shows all my parts in the same height and being printed in parrallel.. I didn't even test printing anything, as I thought gcode was right and slic3r was wrong.

Is there a setting I am issing? I tried disabling a few things here and there, but couldn't make the site show me the prints as I thought it would happen.

Otherwise great job. It really has saved precious time by analyzing my code before printing it :)

[austjancev-sugarcrm]

Hi, sorry, I did not quite understand you.
Can you give me a link to a file you're trying to view and describe what are you expecting to see?
By default, gcode.ws has two options that are set and might affect the sequence of layers and events: "Sort layers by Z" and "Hide empty layers". Hide empty layers should pretty self-explainatory - if nothing was extruded on a Z height where printer was told to go - that layer would not be shown (that happens a lot in case of z-lifts or, for example, if you are waiting for extruded/bed heat-up on somewhere above platform). "Sort layers by Z" - just makes sure that layers in gcode viewer would be shown in the order according to their Z coordinate, not according to the order printer visited them (once again, help avoid confusion with Z lifts and waits). These are safe to be enabled and changes they introduce are usually not significant.

As for sequntial prints.. it's pretty much impossible to 3d print several parts sequentially on the same same platform, so if you slice several parts on one platform using slic3r - it will generate a gcode that would print one layer for each part and after that move on to the next layer. That's ok.

[k2OS]

Thanks for the very speedy response and explanations, but..

" it's pretty much impossible to 3d print several parts sequentially on the
same same platform" - ehr. no. Small objects fit nicely next to each other.
I've done quite a few sequential prints on my Ultimaker, sliced in Cura.
(it slices them by default for sequential prints when loading several STL's
one at a time, as long as one remembers to set the clearances correctly for
the printer you're using, this works like a charm).

I'm linking to two a dropbox folder with a gcode-file with two parts and
screenshots from Cura and gcode.ws to show what I mean.

Cura Seq a shows curas own gcode preview half way into the first object.
Cura Seq b shows first object done and half way into the 2nd object.
gcodews_layer_0 shows how gcode.ws shows the first layer of the gcode (with
no changes to parameters whatsoever). Scrolling up through the layers, it
looks as if one layer is completed at a time in each object, while out in
reality, one complete part is printed before moving on to the next one
(this is what I thought gcode.ws would show..).

The gcode is attached too.

The files are here:

https://www.dropbox.com/sh/gpedfnl6ey0ckfh/eQeJfXNtNf

Cheers

/rené

On Thu, Sep 26, 2013 at 5:05 AM, austjancev-sugarcrm <
notifications@github.com> wrote:

Hi, sorry, I did not quite understand you.
Can you give me a link to a file you're trying to view and describe what
are you expecting to see?
By default, gcode.ws has two options that are set and might affect the
sequence of layers and events: "Sort layers by Z" and "Hide empty layers".
Hide empty layers should pretty self-explainatory - if nothing was extruded
on a Z height where printer was told to go - that layer would not be shown
(that happens a lot in case of z-lifts or, for example, if you are waiting
for extruded/bed heat-up on somewhere above platform). "Sort layers by Z" -
just makes sure that layers in gcode viewer would be shown in the order
according to their Z coordinate, not according to the order printer visited
them (once again, help avoid confusion with Z lifts and waits). These are
safe to be enabled and changes they introduce are usually not significant.

As for sequntial prints.. it's pretty much impossible to 3d print several
parts sequentially on the same same platform, so if you slice several parts
on one platform using slic3r - it will generate a gcode that would print
one layer for each part and after that move on to the next layer. That's
ok.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-25140945
.

[macouno]

I have the same issue... and switching off "sort by z" doesn't seem to do anything... now... I made this sequential file using a little creative python coding, so I know it isn't neat (the slice numbers aren't quite sequential, neither is the percentage count).... But... it prints out perfectly on my machine.

The gcode was based on a makerware 2.2.2.89 slice of two models that I merged into one file (it says ; Switch where I pasted on the second model): http://misc.macouno.com/index.php?file=Dorus-and-Manus-7cm.gcode

[hudbrog]

Uh, never considered that someone would actually print several models independently in one print. Current implementation depends on Z height a lot to merge layers, since most slicers use z-lift or something similar and without merging layers - it would be almost impossible to read the result. I'm not sure I want to implement that due to limited use case (and current implementation still shows models properly, just at the same time and not sequentially).

[k2OS]

I'd just like to say I accept that this is closed. I was just wondering if I didn't know how to use the site. Keep up the good work :)

[macouno]

Same here... though I wouldn't think it'd be very far fetched to have an option to show the slice in the order that it is in in the gcode file, rather than sorted by Z. Especially for more advanced use cases that could be interesting.

Great work btw... incredibly useful visualisation tool to have!

[dartrax]

Just wanted to say hello and that I started to use sequentially pinting because it has some advantages... If I print 20 objects at once and in the middle of the print one layer has a fault, I lose all 20 half-way-printed parts. With sequential printing, I have 9 objects perfectly finished, 1 object is lost and 10 objects are not yet started to print, so no waste.
It should be noted somewhere that gCodeViewer does not display sequentially printing correct, because currently everybody assumes that the slicer made an error, not gCodeViewer, when the preview shows all objects started at once even with "sort by Z order" option disabled.