slic3r / Slic3r

Open Source toolpath generator for 3D printers
https://slic3r.org/
GNU Affero General Public License v3.0
3.35k stars 1.29k forks source link

more detailed g-code verbose output #2079

Open luminize opened 10 years ago

luminize commented 10 years ago

Hi,

I'd like to have more detailed verbose output. I'd like to know what type of infill or perimeter is "active". (top) solid layer, inner/outer perimeter I do postprocessing of the Slic3r output with a python scrip. I search for the ; perimeter or ; fill in the lines. That way I can print lines with standard G-code by setting the widths of my extrudate when using "nozzle pressure adjusted velocity extruding" with LinuxCNC. I'm happy to implement this myself. If you could show me which files to search or modify I'd appreciate it. Would save me a lot of time searching for the right places.

Bas

alranel commented 10 years ago

What does "active" mean?

luminize commented 10 years ago

during printing there is the infill being printed, the perimeter, etc, and I can see that in the verbose g-code output like G1 X3.795 Y22.135 A1662.27720 F1200 ; fill. I mean with "active" that this line is part of a series of lines is part of "fill" being printed. So instead of only knowing if it is "fill" i'd like to know if it's "top solid infill" or "solid infill", "first layer" etc, basically all I can manually set with the line widths in the print settings -> advanced tab in Slic3r.

machinekoder commented 10 years ago

I would also be interested in having this implemented. If you show us the place in the code where this comment is generated we might find a way to implement it.

luminize commented 10 years ago

@alexrj I have added more output in the verbose output for my needs, those are the type, the width and the height of the line that is being extruded. where before the commented output was ; fill I have now made it like ;Type=top_solid_infill,line_w=0.5,line_h=0.200000002980232 If you want it to be merged in the main branch let me know how and if the current modifications are good enough. The branch is here: https://github.com/luminize/Slic3r/tree/more-verbose-gcode-comments commits e856247657e5761097dd60faf010f690adffa57a and 8cfae5aee2da0af46480cc10f4830b4792defa85 Regards, Bas

lordofhyphens commented 8 years ago

@luminize open a pull request if you think it belongs in upstream slic3r :)