Creality K1 MAX and gcode filename
Posted: Thu Apr 09, 2026 5:54 am
Hi I'm Antonio and I'm new to this forum but I use S3D from several years.
I've inserted in my 3D printing lab a new Creality K1 Max.
I've rooted it immediately with fluidd w/o any problem and warranty is ok because in Creality cloud give suggestion about rooting.
The issue is this:
when I slice models and I send them directly to the printer via "Begin Printing on Machine" button it's all ok but the gcode filename is unwanted changed but this don't happen using the "Export Build File to Disk" button.
As sample the file LG_wheel_disc.factory is exported as LG_wheel_disc.gcode but directly priting is renamed as print-20260409-112444-516.gcode.
In K1 MAX there isn't any klipper command/feature/macro that change it so I'm thinking the "issue" is in S3D.
Is there a macro or a script sentence to avoid this nosense gcode filename? The reprint must be done immediately otherwise if you add another file is impossible to recognize the right one.
Thank you in advance for your kind reply.
I've inserted in my 3D printing lab a new Creality K1 Max.
I've rooted it immediately with fluidd w/o any problem and warranty is ok because in Creality cloud give suggestion about rooting.
The issue is this:
when I slice models and I send them directly to the printer via "Begin Printing on Machine" button it's all ok but the gcode filename is unwanted changed but this don't happen using the "Export Build File to Disk" button.
As sample the file LG_wheel_disc.factory is exported as LG_wheel_disc.gcode but directly priting is renamed as print-20260409-112444-516.gcode.
In K1 MAX there isn't any klipper command/feature/macro that change it so I'm thinking the "issue" is in S3D.
Is there a macro or a script sentence to avoid this nosense gcode filename? The reprint must be done immediately otherwise if you add another file is impossible to recognize the right one.
Thank you in advance for your kind reply.