Closed markotime closed 11 years ago
Okay, please, help me. Here's a list of information and files you need to provide:
https://github.com/alexrj/Slic3r/wiki/Quick-guide-to-writing-good-bug-reports
Thank you for your help!
Of course, what was I thinking? I'll run it again and get you what you need / thanks for a great program! /mark
Alessandro Ranellucci wrote:
Okay, please, help me. Here's a list of information and files you need to provide:
https://github.com/alexrj/Slic3r/wiki/Quick-guide-to-writing-good-bug-reports
Thank you for your help!
— Reply to this email directly or view it on GitHub https://github.com/alexrj/Slic3r/issues/1225#issuecomment-19128905.
No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2013.0.3343 / Virus Database: 3199/6392 - Release Date: 06/07/13
Using exactly the same gcode file, it mysteriously did NOT misbehave.
My bad, I apologize for both
the false alarm and the badly submitted report.
The code does occasionally stack two layers on one pillar, rather than alternating between them, leaving a small bulge.
In comparison to the garbage left by the H-1's old nozzle, with dribble, it is a small problem. Thanks /mark
@markotime, thank you for your feedback and no need to apologize. :)
Just an off-list question - I may formalize it base on response. My seemecnc H1 with the NEW nozzle still dribbles like an NBA basketball star. It definitely leaves too much detritus behind using G1 position/retract combined moves. It behaves better using G0 retract but toward the end of a move it again drops bombs.
The hollow cube using the latest slic3r (wipe) has 3 sides with lots of beads and threads (G1 / wipe, back and forth move - cooling? - ) while the 4th side seems to use a G0 retract then G0 (or very fast) move to the "first" corner at a new height. That side is almost without a drop.
I guess what I'd like to see is a 1mm G0 retract (or very fast) followed by a "normal" G1 move to the next location which includes further retraction. I suspect that all the back and forth stuff just leaves more time for leakage, so would like to try a more direct approach.
Fan helps cool the "next" location so I can control distortion of pillars that way.
On a "round tuit" with raised letters, the result is an unusable mess.
Have not tried
the "one at a time" option which may do better doing each letter
completely before
doing the next.
Unfortunately I cannot program Mach3 to use relative motion on A and absolute on x y z. This leaves me with a large macro challenge to change the output from slic3r. My attention span is too short.
Otherwise, I'm very please with slic3r on objects without many recesses or gaps. Thank you for a great program and your continuing development!
Noticed that about every 10th layer, as an anomaly in the back and forth dipsy-doodling between the two robot legs, a second extrusion on the same layer of one leg or the other takes place, leaving excess material with predictable results.