Nice idea! I just happened to be modifying my end g-code last night and I noticed that slic3r has a gcode for layer change. You could put a pause or an orbit in there as well, or whatever you'd like to delay the printby KickMe0869 - Slic3r
That's a good idea to use a sacrificial column! Prior to building my enclosure I had luck with making a really tall wall around the part, but sometimes it would pop loose and mess everything up. The nice part was that it was something I could do in Slic3r though. I wish I had thought of just having a basic column part like that! The last few prints I've done have come out well. I turned offby KickMe0869 - Slic3r
QuoteJean-Baptiste "One more thing" to my previous post : I check the "Use Ping-Pong Communication (send only after ok)" parameter (set XON/XOFF) in the "Connection" tab of the "Printer setting" DialogBox, to avoid the faintest USB problem (Thank's Pierre from Gi-Nova Grenoble). I know this is an old thread, but I just wanted to say THANK YOU! My printer randomly started having this issue, andby KickMe0869 - Sanguino(lolu)
Thanks for the reply! I did run a print with a couple of small parts and as far as I could tell you are absolutely correct. The larger of the two parts received the same amount of cooling (fan speed was set the same) as the very tiny part. I'm very aware of that particular issue, as I've had it happen to me on a few occasions. I'm thinking that the way Slic3r currently works is sub-optimal.by KickMe0869 - Slic3r
I am curious - the Slic3r settings of "slow down" and "enable cooling" if "layer time is below X seconds" are pretty nice features. However I'm wondering how it calculates layer time if I am doing multiple parts, or if I am printing a part with both large and small features. I can see two scenarios: A: By "layer time" it means the area currently being processed and infilled. For example, wheby KickMe0869 - Slic3r