Simplify3D User Forum

parallyze wrote: ↑Sat Sep 19, 2020 9:54 pm

JustMKollum wrote: ↑Sat Sep 19, 2020 8:17 pm Remember, this GCODE is only part 1 of 2. I split the model into 2. I should have provided the 2nd part for less confusion. In fact, here you go.

http://www.mediafire.com/file/9m16sybab ... gcode/file

The 2nd part is colored black that you see in the pictures, and it's a 2nd GCODE or 2nd process. That keyhole you see eventually gets sealed at the top, so that's what require's support, so the top doesn't cave in.

I didn't notice you were using seperate processes _AND_ separate gcode files. Most people just do a color change and resume printing using
a single gcode file, as far as I can tell... so you're printing the first (purple) gcode file, then swap filaments and then start the second (black) one? The second one does include homing all axes..?
(And the first one ends at 4.18mm height, the second one does start at 4.5mm using 0.2 layer height, 1st layer @90%...is that gap on purpose?)

Keyhole: With that many solid layers on top I'm pretty sure this should work without supports (and maybe 1 layer of bridging).

Anyways, all the tiny spots all around at layer 18+ (first gcode file) have nothing to adhere to and will get dragged all over the surface (there's 30-40 of them on the in- and outside).

And looking at it... I actually don't understand how you expect this to be a nice print. The black part is much bigger than the purple one:

scars_5.JPG

There's absolutely nothing supporting the black part all around...?! You should definitely check your support generation settings.... ^^

Okay, @parallyze, maybe you can help me with something else, something smaller?

I uploaded the .Factory file for it instead of the GCODE to make things easier:
http://www.mediafire.com/file/waxhsb3op ... ctory/file

It's similar to what I was printing before with the separate processes. This time the first process will be matte yellow and 2nd process will be matte black.

This print shouldn't require supports, at all.

I'm still having surface scratching issues, and I hope the .FACTORY file will help. Please let me know if there's anything I need to change.

Thanks!

JustMKollum wrote: ↑Thu Sep 24, 2020 6:03 pm
Okay, @parallyze, maybe you can help me with something else, something smaller?

I uploaded the .Factory file for it instead of the GCODE to make things easier:
http://www.mediafire.com/file/waxhsb3op ... ctory/file

It's similar to what I was printing before with the separate processes. This time the first process will be matte yellow and 2nd process will be matte black.

This print shouldn't require supports, at all.

I'm still having surface scratching issues, and I hope the .FACTORY file will help. Please let me know if there's anything I need to change.

Yes, that doesn't require any supports. But there's a few other questions coming to my mind when looking at the factory file, maybe it
helps if we keep "scratching issues" seperate from "color changes" later on

As far as I can see you're using two processes which are set up almost identical. The first one is using 0.20mm layer height, 1st layer at 90%
and is set to stop at 3.32mm height. The second one uses the same settings and is set to start at 3.32mm height. That height just won't
be reached exactly (3.18mm or 3.38mm would be valid).

When slicing using both processes the "switch" will take place at layer 17/18 (3.38mm/3.58mm). Because when both processes are selected
for slicing S3D will keep track of the correct layer height.

But you're using two seperate files, which means you're slicing using the 2nd process all alone. Then it will start at 3.42mm... and as the
first process is stopping at 3.38mm this means there's only 0.04mm left for the first layer from the second gcode file. This will result in
massive overextrusion.

If I may suggest something:
Check out if your printer does support a pause/change filament command, like M600. As far as I can tell your Mega X is based on
Marlin firmware, so it should support this command: https://marlinfw.org/docs/gcode/M600.html

For testing you can simply edit the gcode file and put the M600 right at the start of a layer where you want to change colors. If your printer
does support this and you can swap filament/resume the print successfully I don't see the need for two processes on an object like the
one which can be seen in the factory file. You can use some simple objects (box, maybe 30x30x10mm) to test this, no need for a 2h print
(Note: You can also do this using the post processing scripts, but for testing it's probably easier to just edit the gcode file)

Scratches:
The purple/black object had some surface defects because of the short support extrusions. Do you have a picture of this one, I suspect
because of the different start/end positions when using seperate gcode files there was simply just overextrusion/smearing going on right
after the filament change.

On the object inside the factory file it's hard to tell if it's a "scratch" because of material dragging or maybe the retracts aren't set up very
well. Did you test retraction settings by using a simple object, something like this? https://www.thingiverse.com/thing:2563909
(I chose this one because I think I've seen it in a post here recently about retracts)