Profiles vs gcode  

RE: Profiles vs gcode

I don't think you can see which profile that was used, like Print Settings Profile, Filament Profile

However, the last 240 something lines in the gcode-file lists all the settings that was used in the slicer. 
Look at them and compare with your Print, Filament, and Printer Settings
Also, you can import the settings from gcode, "File" - "Import" - "Import Config", choose the gcode-file and settings are imported

RE: Profiles vs gcode

Maybe there are tools figureing that out. But you can also use Notepad++ and at the end of the GCODE you can find lots of informations that could help. I found filament type and temperatures, nozzle diameter and lot more. So I would give it a try.

Generate GCodes and then try to find the settings in it you used in the Slicer.

Best regards, Clemens

RE: Profiles vs gcode

The data is in the .gcode... here's one of mine.

; physical_printer_settings_id = 
; post_process = 
; print_settings_id = 0.30mm DRAFT @MK3
; printer_model = MK3
; printer_notes = Don't remove the following keywords! These keywords are used in the "compatible printer" condition of the print and filament profiles to link the particular print and filament profiles to this printer profile.\nPRINTER_VENDOR_PRUSA3D\nPRINTER_MODEL_MK3\n
; printer_settings_id = MK3 - Anti-Ooze
; printer_technology = FFF

RE: Profiles vs gcode

@tim-2

THANKS!

RE: Profiles vs gcode

You can also import the settings back into PS from any gcode created in PS.  You can use File>Import>Import Config and select your gcode file.  So no need to use a text editor.

Once loaded back in you can save the settings as you normally would save a profile.

RE: Profiles vs gcode

@neophyl

Thank you for that information - completely new to me, that is ingenious!!!

Up to now I only stored the STL-Files. Knowing that it also makes sense to keep the GCode-Files of successful prints.

Best regards, Clemens

RE: Profiles vs gcode

The 'best' way (imo) is to actually save the project file.  The .3mf file stores everything.  Models, part placement, profile settings used, modifiers, variable layer heights, painted on support areas.  Everything.

Once you get into the habit of saving them you have snapshots of everything used to generate the gcode.  Also as the gcode name can be based on the saved project name so matching them up is easy.  

I still like the gcode settings as a backup though as if Prusa update one of their profiles and you load a project in that uses it then any changes they made to a profile since you last sliced will be taken into account.  I don't like the idea of settings being updated in the background which is also why I almost never use Prusa profiles for my own stuff but copies I've made and tweaked to suit my setup.

RE: Profiles vs gcode

@neophyl

True for new projects - but for older projects (where you don't have saved a 3MF-Projekt) the GCODE-Import for receiving the settings is a good thing.

Best regards, Clemens