Dont use gcode you didnt slice yourself  

RE: Dont use gcode you didnt slice yourself

Fully agree: I will NEVER run someone else's gcode, EVER.

Just supply a good STL file 😀

RE: Dont use gcode you didnt slice yourself

You don't have to start a fire per se to create havoc. Park the extruder at [0,0,0] and then run the extruder up to max temperature. You'll melt the PEI sheet pretty quickly. (I did this once unintentionally with the extruder set for PLA and made a mess of my Mk2 print bed.)

RE: Dont use gcode you didnt slice yourself

I am in total agreement that promoting g-code uploads is ill conceived. I can understand the good intention, but the potential risks far outstrips the meager gain.

STL's and 3MF's are a much smarter choice.

Continual harping about not uploading g-codes just adds to a ludicrous stance.

RE: Dont use gcode you didnt slice yourself

Besides the possibility of malicious code, there remains the practical problem of code that's not optimized for your particular printer and filament.  For example, I measure the actual diameter of every filament that I use, and create a "preset" in Slic3r for that particular spool of filament.  In my opinion, this is really necessary to get exactly the right quantity of filament extruded.  Also, it's very possible that I may tweak the temperature settings for the particular brand of filament in use.  So just because someone else created G-code that prints a beautiful Benchy on their printer with their spool of PETG does not mean that their G-code is optimum for my printer with my spool of PETG.

TL;DR:  Start from STL and create your own G-code for optimum results!  And you will be safe from the possibility of malicious G-code.

RE: Dont use gcode you didnt slice yourself

I like the idea of printing from downloaded gcode but Migamix expresses some valid concerns. One way I use to check downloaded gcode for accuracy involves Simplify3d, which I happen to have from a previous printer purchase. It has a gcode previewer capability that will show where the extruder is going to travel in the gcode. Also, gcode can be opened in a text editor and temperatures can be checked by finding all instances of M104's, M109's and the like.

To my knowledge, PrusaSlicer does not have a gcode previewer like Simplify3D's. If that is true, such an addition to PrusaSlicer could improve the safety of printing downloaded gcode.

RE: Dont use gcode you didnt slice yourself

There is a gcode preview in the open source pronterface utility.

RE: Dont use gcode you didnt slice yourself

Repetier-host for Mac will allow opening of gcode files for preview. IdeaMaker (free) and Simplify 3D (paid) slicers will open gcode files for preview as well. It would be nice to be able to do the same in PrusaSlicer, particularly since the gcode preview code is already present.

I am bummed they removed the 2D view from PrusaSlicer a few versions back, as the ability to clearly view the extruder path throughout a print was quite valuable for troubleshooting finish.

RE: Dont use gcode you didnt slice yourself

Posted by: bobstro

[...]

I am bummed they removed the 2D view from PrusaSlicer a few versions back, as the ability to clearly view the extruder path throughout a print was quite valuable for troubleshooting finish.

I vaguely remember that feature, but never really used it before it was removed. But, in the 3D previewer you can lock the top-most layer indicator to the bottom-most layer indicator with the small padlock under the slider. With a top-down view, isn't moving the locked-together layer indicator similar to the old 2D view?

RE: Dont use gcode you didnt slice yourself

Posted by: Sembazuru
I vaguely remember that feature, but never really used it before it was removed. But, in the 3D previewer you can lock the top-most layer indicator to the bottom-most layer indicator with the small padlock under the slider. With a top-down view, isn't moving the locked-together layer indicator similar to the old 2D view?

They're not exactly the same. You can currently lock top & bottom together to see a layer-by-layer "cat scan" view, but you don't see the extruder movements that build that layer. It also shows the approximated filament widths, whereas the 2D view just showed a line. This made things like examining retractions, coasting and z-seams much easier to visualize. Take a look at Michael Hackney's KISSlicer presentation for a good example. Jump ahead to about the 1:50 mark.

RE: Dont use gcode you didnt slice yourself

Is there a way in PRUSA slicer to view the lines of Gcode?

RE: Dont use gcode you didnt slice yourself

I would like to capture the lines that create the nozzle purging print line that PRUSA always produces at the front of the bed at the beginning of every print.  A buddy with a Reprap printer needs to add that as part of set up routine.

RE: Dont use gcode you didnt slice yourself

Posted by: charles.m12

I would like to capture the lines that create the nozzle purging print line that PRUSA always produces at the front of the bed at the beginning of every print.  A buddy with a Reprap printer needs to add that as part of set up routine.

Look in the startup gcode in PrusaSlicer under Printer Settings->Custom G-Code.

RE: Dont use gcode you didnt slice yourself

I included .3mf files for the items I've uploaded. People can see how I printed the parts, and make changes if they want to.

I don't like the "3d models only" flag.

RE: Dont use gcode you didnt slice yourself

3MF is great, and provides the best way of sharing information rather than going "read-only" with gcode. Thanks for doing that.