Can nozzle temperature be included in gcode filename?  

RE: Can nozzle temperature be included in gcode filename?

Yes.  Just about all of the settings can be used.  For example if you hover your mouse over the first layer bed temp setting you will see its internal name.  first_layer_bed_temperature, so if you add [first_layer_bed_temperature] to the output string it will add the temp value configured to the name.  

Prusa has this info as part of its knowledge base if you had searched https://help.prusa3d.com/article/list-of-placeholders_205643 .  It states that you can use the settings values plus the ones listed.

RE: Can nozzle temperature be included in gcode filename?

Thanks for the info.  And for the record I did hover, and did see that "first_layer_temperature" was the parameter, but I wrapped it in braces, not brackets.  So close.  And I did search the KB, but did not find that nice reference you included. 

Thanks again. 

RE: Can nozzle temperature be included in gcode filename?

One caveat I jut discovered. When you inert a parameter that includes a percent sign, such as infill percentage, the file name will be rejected by Prusaconnect for the Mk3S as invalid. Of course, Prusalink on the Mini is very happy to accept it… 

RE: Can nozzle temperature be included in gcode filename?

That's because the MK3 firmware has a limited set of allowed characters.  I have a similar problem with my toshiba wfi enabled sd card in my mk3.  As it uses webdav it can be broken by certain characters. 

A % is used as a special character in html for instance.  It is why its always best to self limit yourself to the basic alphanumerics as then there is little to no chance of these different character set issues coming into play.

RE: Can nozzle temperature be included in gcode filename?

Oh, I know very well that % can be a dangerous character 🙂

But it's not a problem with Octoprint, so I'm sure if they made the Prusaconnect code properly escape the % character, the firmware could handle it. But of course, as you suggested, I've changed my output option to not use the infill field. In fact, this made me realize that it was actually never of any use to me anyway as part of the filename, so all is good.