Printer model not found

[Rickthebig]

I run a Prusa compatible DIY printer and Prusa slicer. Almost everything works fine but the printer model is not found in the gcode file. I could manually add a fake entry, but I don't know the syntax so that it will be recognized by your software.
So what does your software search for in the gcode file to recognize the printer_model?

This is not a bug, by the way...

[garethky]

I actually don't know how you do that from the Prusa Slicer UI. Looks like its something based into the built in profiles. Syntax is:

printer_model: My Printer

[Rickthebig]

Yes but since you check the gcode file, you know what values for printer_model are deemed valid. Would you give me an example of such values that pass the check your program does? Thanks Rick Gareth Farrington ***@***.***> schrieb am So., 15. Feb. 2026, 05:37:

…

*garethky* left a comment (garethky/PrusaSlicerPressureAdvanceCalibration#29) <#29 (comment)> I actually don't know how you do that from the Prusa Slicer UI. Looks like its something based into the built in profiles. Syntax is: printer_model: My Printer — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEBIS7CZ5H36LD5APPFG35L4L7ZZPAVCNFSM6AAAAACUEOX22KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMBTGIZDKNBZGM> . You are receiving this because you authored the thread.Message ID: <garethky/PrusaSlicerPressureAdvanceCalibration/issues/29/3903225493@ github.com>

[garethky]

Oh, you can name it anything you like! The only cases where it matters are for Prusa printers.

[Rickthebig]

Hello again, I still don't know how to change the gcode file to avoid it being rejected, that's the point. I don't want to put whatever I want there but something the postprocessing software will accept. I hope it is clear now. Rick Gareth Farrington ***@***.***> schrieb am Do., 19. Feb. 2026, 01:15:

…

*garethky* left a comment (garethky/PrusaSlicerPressureAdvanceCalibration#29) <#29 (comment)> Oh, you can name it anything you like! The only cases where it matters are for Prusa printers. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEBIS7EXVNCPWDILP2GTRFL4MT6CJAVCNFSM6AAAAACUEOX22KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMRTHE2TEMJVGU> . You are receiving this because you authored the thread.Message ID: <garethky/PrusaSlicerPressureAdvanceCalibration/issues/29/3923952155@ github.com>

[garethky]

What really matters is what firmware you are running:

If its Marlin, Rep Rap Firmware (RRF) or klipper: The model of the printer does not matter.

If its Prusa's actual Prusa Firmware Buddy firmware: Then the name needs to match the model of Prusa printer you are trying to emulate, because that's how Prusa explains which version of pressure advance you have. This is almost certainly not what you have though.

---

To get the value emitted in the right spot in the gcode you need to fill out the printer's model information in the printer profile itself (example). AFAIK there is no way to create a printer in Prusa Slicer's UI without the model filled out. If you make your "Physical Printer" from one of the included profiles then the model will be filled out for you.

So I assume the only way this can have happened is If you created or copied a custom printer profile into Prusa Slicer. If that's the case then you are the author/owner of those files and its up to you to edit them and fix the issue.