K1C: How to run MY custom START_PRINT from the touchscreen in firmware 1.3.5.22?

Flagship K Series Creality Flagship K1 & K1C
, ,
1

Hi everyone,

I’m trying to use my own custom START_PRINT macro on my Creality K1C instead of the stock routine created by Creality.

Here is the issue: I created my own script in gcode_macro.cfg and specified it in Orca Slicer. Everything works perfectly as long as I start the print via the Fluidd web interface.

However, if I start a print directly from the printer’s touchscreen, it completely ignores my script. It also ignores the macro in /Helper-Script/KAMP/Start_Print.cfg and just executes some built-in internal routine.

Does anyone know what and where needs to be modified so that starting a print from the touchscreen uses the START_PRINT macro defined in the .cfg files, rather than the hardcoded routine hidden inside the firmware?

Any help or ideas would be appreciated!

2

Now, do not take my word for it but I have seen some macro sections in the Creality Slicer (not Orca).

Let me get some screenshots.

Creality_Print_PPS
Creality_Print_PPS571×646 17.1 KB

G-Code_Types
G-Code_Types1263×902 34.7 KB

That may help you in case you wanted to test some g-code out on the Creality Print. I know what you are asking and I know nothing about Orca for now. I am sorry.

3

Hi @For_Ward,

Thanks for the screenshots and reply!

Just a quick side note: Creality Print (v5.0 and newer) is actually a direct fork of OrcaSlicer. So all those settings are virtually identical in Orca. In fact, that exact window from your screenshot is where I replaced the stock call with my own custom macro name.

The main issue isn’t the slicer itself — it works perfectly when I start the print via the Fluidd web interface.

The issue is strictly with the printer’s touchscreen. When you start a print directly from the screen, Creality’s internal software completely overrides/ignores whatever custom macro is set in the G-code and forces its own hardcoded pre-print routine instead.

And yes, it’s super frustrating! That’s why I’m trying to find a way to bypass or override that hardcoded routine on firmware 1.3.5.22.

1 Like
4

Oh. I was unaware of the custom macro overrides on USB or via WiFi and touchscreen applications. I am sorry to bother you…

5

When I installed KEMP on my K1c this installed a diffeerent Start print macro. Also the installation commented out the original Start print macro in the gcode_macro.cfg file.as shown below .

#[gcode_macro START_PRINT]

#variable_prepare: 0

#gcode:

# WAIT_TEMP_END

# CLEAR_PAUSE

# {% set g28_extruder_temp = printer.custom_macro.g28_ext_temp %}

# {% set bed_temp = printer.custom_macro.default_bed_temp %}

# {% set extruder_temp = printer.custom_macro.default_extruder_temp %}

# {% if ‘BED_TEMP’ in params|upper and (params.BED_TEMP|float) %}

# {% set bed_temp = params.BED_TEMP %}

# {% endif %}

# {% if ‘EXTRUDER_TEMP’ in params|upper and (params.EXTRUDER_TEMP|float) %}

# {% set extruder_temp = params.EXTRUDER_TEMP %}

# {% endif %}

# {% if printer[‘gcode_macro START_PRINT’].prepare|int == 0 %}

# {action_respond_info(“not prepare.\n”)}

# PRINT_PREPARE_CLEAR

# CX_ROUGH_G28 EXTRUDER_TEMP={extruder_temp} BED_TEMP={bed_temp}

# CX_NOZZLE_CLEAR

# ACCURATE_G28

# CX_PRINT_LEVELING_CALIBRATION

# {% else %}

# PRINT_PREPARE_CLEAR

# {% endif %}

# CX_PRINT_DRAW_ONE_LINE

My be you need the disable the original start print maco.

Bill

6

Thanks for the tip, Bill! I’m aware of how KAMP handles START_PRINT.

My issue is a bit different: I’ve customized START_PRINT based on KAMP (even editing /Helper-Script/KAMP/Start_Print.cfg via SSH).

The changes work perfectly when launching a print through Fluidd. However, when I start the exact same G-code file directly from the K1C touchscreen, the printer completely ignores these changes and fails to execute the updated macro.

It seems Creality OS bypasses standard Klipper macros when printing from the display. Has anyone found a workaround to force the touchscreen to use custom start macros?