Any plans to support the script on CFS upgraded K1's?

[FusionOpz]

Any plans to support the script on CFS-upgraded K1's? I know the upgrade kit comes with new firmware, I've just ordered mine

[jmwhelan]

After rooting, I installed the helper script on my k1-max with CFS installed.

No issues installing moonraker, mainsail, entware and Mobileraker companion.

Running firmware 2.3.5.27

[ddemeterco]

Managed to follow the official guide to install Mainsail or Fluidd just to lower extruder current and it fixed the errors now it prints flawlessly. Check this link: https://github.com/CrealityOfficial/K1_Series_Annex/tree/main

[ddemeterco]

I’ll be using no the same logic to install the helper script soon. Preload the script .sh on a SD card and using command to install it.

[sixtysecondstosmash]

Managed to follow the official guide to install Mainsail or Fluidd just to lower extruder current and it fixed the errors now it prints flawlessly. Check this link: https://github.com/CrealityOfficial/K1_Series_Annex/tree/main

Thanks, this will do for now. Lots of advanced features are still missing, but even basic ones like camera and timelapse access aren't available too.

I’ll be using no the same logic to install the helper script soon. Preload the script .sh on a SD card and using command to install it.

This is an interesting solution, but makes sense considering it works to install fluidd and mainsail. Please do post an update if you have any luck with it

[ddemeterco]

OK, I tried. So far no luck, I get an error on line 7.

/usr/data/helper.sh: .: line 7: can't open '/usr/data/scripts/*.sh': No such file or directory

[sixtysecondstosmash]

That's too bad. Hopefully someone figures it out soon, or Creality posts something to get it working again. As people start getting their kits this will probably get more attention

[NexGen-3D-Printing]

Watching this thread, as I'm considering one of these as well, but if I have to use Creality's software, app and cloud rubbish, then I may as well just go buy a Bambulab machine, the fact that we can jailbreak the K1 range is the only reason I purchased them.

[tropho23]

I had the same thought! If I can't tune my K1 printers that very badly need to be tuned using root tools, then I won't bother adding CFS units to any of my twelve K1-series printers. I already have one Bambu X1C with AMS for multicolor needs and it really does 'just work' as everyone says, without all the hassle I experience with every K1 printer I've purchased.

[A-Void-Me]

I just installed the new "cfs" firmware and i can "start" the helper-script.

I did it this way:

git config --global http.sslVerify false

git clone --depth 1 https://github.com/Guilouz/Creality-Helper-Script.git /usr/data/helper-script

sh /usr/data/helper-script/helper.sh

[sixtysecondstosmash]

I noticed that the instructions mentioned to try the git config if the script didn't work initially, but it still doesn't work. The script won't install even after trying it

[A-Void-Me]

i just updated today to the version 2.3.5.33 and i got the same problem.

Downgraded to 2.3.5.27 and i can use git etc. again.

[marcribe]

Please, anyone with root... can you share the config files, please? I want to take a look in the macros

[FusionOpz]

Where did you find 2.3.5.27?Sent from my iPhoneOn Apr 5, 2025, at 2:53 PM, A-Void-Me ***@***.***> wrote: i just updated today to the version 2.3.5.33 and i got the same problem. Downgraded to 2.3.5.27 and i can use git etc. again. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[A-Void-Me]

someone on reddit uploaded it to dropbox - CR4CU220812S11_ota_img_V2.3.5.27.img

https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0

[ityshchenko]

CR4CU220812S11_ota_img_V2.3.5.33

[quentin013101]

Hello, do any of you have an error with the tc2841 cutter?

[Play13thStreet]

Yes! At mine K1C the Sensor for cutting Flamen is broken. I Write to Creality, that I need a new, they will send. I will report if the problem is gone

[Play13thStreet]

Check if the sensor plug is in the correct socket. It is located on the back, bottom left!

[FusionOpz]

So I noticed something while ssh’ing into my printer lastnight, the git binaries are broken, 0bytes

[fenix8k]

Hi, I just made a mini guide on how to install the helper script on the last firmware

https://github.com/Guilouz/Creality-Helper-Script-Wiki/discussions/797

[Zionmatrix2025]

NO - Use the one down farther

[pgallent]

JFYI, finally I found how to get the screen working as in a K1C, and getting the CFS functional to use the K1C Filamants.

You have to go to
/usr/data/creality/userdata/config/system_config.json

And update the values for "model" and "model_str" as follows:

  "device_info":{
    "device_sn":"XXXXXXXXXXXXXX",
    "device_mac":"XXXXXXXXXXXX",
    "model":1007,
    "model_str":"K1C",
    "bed_length":220,
    "bed_width":220,
    "bed_hight":270,
    "ui_direction":3,
    "z_direction":1
  },

Thx to @becast that gave me the values in this topic:

#793

[fenix8k]

I don't understand your comment, I just check my printer and my file is like your modified one is, I havent modified my file so I think this is the default with the last firmware.

[pgallent]

On a K1 SE?

I had "1011" as "model" and "K1 SE" as "model_str".

On the printer screen I only had access to 1 fan, and CFS didn't allow me to select filaments as ABS or ASA.

[Papalexi]

Did you solved the problem with tc2841? i have the same problem and can´t solve it.

[A-Void-Me]

I maybe found a way to install the Creality Helper Script on 2.3.5.33. Can someone try it? It worked for me after a factory reset.

SSH into the machine.

Install Entware:
wget http://bin.entware.net/mipselsf-k3.4/installer/generic.sh -O - | sh

Add Entware to your path
export PATH=/opt/bin:/opt/sbin:$PATH

Start entware on boot (not sure here)
echo '/opt/etc/init.d/rc.unslung start' >> /etc/rc.local; echo 'exit 0' >> /etc/rc.local

Update and install Git:

opkg update
opkg install git-http
opkg install git  # (Optional, if git is missing)

Clone the script:
git clone --depth 1 https://github.com/Guilouz/Creality-Helper-Script.git /usr/data/helper-script

"fix" the invalid repo error:

mv /usr/bin/git /usr/bin/git.bak
ln -s /opt/bin/git /usr/bin/git
git config --global --add safe.directory /usr/data/moonraker/moonraker

Run the script:
sh /usr/data/helper-script/helper.sh

[3rdnfnlbst]

I had my k1 max rooted with the USB method but couldnt get moonraker to work. it would always show it as invalid and would give me an error when I tried to recover it. I reset my machine and rerooted it. Seems moonraker is working now, the helper script shows an old version "v0.0.0-1-gb46787a6-inferred". More importantly I cannot install Octoeverywhere and OctoApp as I keep getting errors during the install that state: Collected errors:

• verify_pkg_installable: Only have 0kb available on filesystem /opt, pkg python3-pip needs 7900
• opkg_install_cmd: Cannot install package python3-pip.
• verify_pkg_installable: Only have 0kb available on filesystem /opt, pkg python3-pillow needs 1910
• opkg_install_cmd: Cannot install package python3-pillow.

I dont know what to do. Please any help is appreciated.
I had to restore back to factory and reused the USB method to install everything. I got the Octos to install, with a bit of extra steps, But I still get moonraker as invalid so I guess Timelapses won't work for me.
If anyone decided to maybe make an update for the USB method so the stuff is maybe more up to date I will try that again.

Revert to the .27 firmware as it's A LOT more flexible.

Somehow I got moonraker to finally show and update. Just have the helper script showing as invalid. But is working at this point so I’m happy. Hopefully I will start to get my Timelapse videos again.

[MarksToys]

Thanks Very much... worked perfectly for me..

[Trails5v]

thank you this helped me alot

[justicestorm]

You are the goat! It worked! I have .33 installed on k1se and k1c.

Fantastic! Thank you so much!

[justicestorm]

You are the goat! It worked! I have .33 installed on k1se and k1c.

Fantastic! Thank you so much!

[jrabkid]

Has there been any update on this since? I'm about to do the upgrade myself but worried I will lose the klipper interface who which I have come accustomed to.

[Jdbye]

You could install this: https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0

I have it installed and it works with the script. However, be aware that the adaptive purge line reportedly doesn’t work well with it, while adaptive mesh does. I'm using Obico, but since the 2.3.5.33 update lacks proper Git support, the helper script is significantly limited—“gimped,” for lack of a better word.

Another issue I’ve noticed with both versions is that after a print finishes, tapping the screen brings up the “print complete” menu. However, if you click either of the buttons (print again / okay), the screen dims and becomes unresponsive to touch. The only way to recover is by rebooting the machine or restarting Klipper.

P.S. From what I’ve read and heard, the reason the developer has remained silent on this topic is because he (allegedly!) doesn’t have the upgrade kit or a K2 unit. His focus currently seems to be on the H2D by Bambu. So, it may be a while before we see further development—unless someone else decides to pick up the mantle.

How do you disable adaptive purge in KAMP?

[3rdnfnlbst]

You could install this: https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0
I have it installed and it works with the script. However, be aware that the adaptive purge line reportedly doesn’t work well with it, while adaptive mesh does. I'm using Obico, but since the 2.3.5.33 update lacks proper Git support, the helper script is significantly limited—“gimped,” for lack of a better word.
Another issue I’ve noticed with both versions is that after a print finishes, tapping the screen brings up the “print complete” menu. However, if you click either of the buttons (print again / okay), the screen dims and becomes unresponsive to touch. The only way to recover is by rebooting the machine or restarting Klipper.
P.S. From what I’ve read and heard, the reason the developer has remained silent on this topic is because he (allegedly!) doesn’t have the upgrade kit or a K2 unit. His focus currently seems to be on the H2D by Bambu. So, it may be a while before we see further development—unless someone else decides to pick up the mantle.

How do you disable adaptive purge in KAMP?

You can edit the file on the machine. In Start_Print.cfg change adaptive mesh from 1 to 0

[Jdbye]

You could install this: https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0
I have it installed and it works with the script. However, be aware that the adaptive purge line reportedly doesn’t work well with it, while adaptive mesh does. I'm using Obico, but since the 2.3.5.33 update lacks proper Git support, the helper script is significantly limited—“gimped,” for lack of a better word.
Another issue I’ve noticed with both versions is that after a print finishes, tapping the screen brings up the “print complete” menu. However, if you click either of the buttons (print again / okay), the screen dims and becomes unresponsive to touch. The only way to recover is by rebooting the machine or restarting Klipper.
P.S. From what I’ve read and heard, the reason the developer has remained silent on this topic is because he (allegedly!) doesn’t have the upgrade kit or a K2 unit. His focus currently seems to be on the H2D by Bambu. So, it may be a while before we see further development—unless someone else decides to pick up the mantle.

How do you disable adaptive purge in KAMP?

You can edit the file on the machine. In Start_Print.cfg change adaptive mesh from 1 to 0

Near the top, in the output_pin thing, right? The macro doesn't need to be changed?

[3rdnfnlbst]

You could install this: https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0
I have it installed and it works with the script. However, be aware that the adaptive purge line reportedly doesn’t work well with it, while adaptive mesh does. I'm using Obico, but since the 2.3.5.33 update lacks proper Git support, the helper script is significantly limited—“gimped,” for lack of a better word.
Another issue I’ve noticed with both versions is that after a print finishes, tapping the screen brings up the “print complete” menu. However, if you click either of the buttons (print again / okay), the screen dims and becomes unresponsive to touch. The only way to recover is by rebooting the machine or restarting Klipper.
P.S. From what I’ve read and heard, the reason the developer has remained silent on this topic is because he (allegedly!) doesn’t have the upgrade kit or a K2 unit. His focus currently seems to be on the H2D by Bambu. So, it may be a while before we see further development—unless someone else decides to pick up the mantle.

How do you disable adaptive purge in KAMP?

You can edit the file on the machine. In Start_Print.cfg change adaptive mesh from 1 to 0

Near the top, in the output_pin thing, right? The macro doesn't need to be changed?

No you have to either edit the file through fluidd or download the file to your computer from the printer and edit it. Then delete the stock file and upload the new one to the same folder.

[Jdbye]

You could install this: https://www.dropbox.com/scl/fi/kheowq2kpkmws2t0nizgk/CR4CU220812S11_ota_img_V2.3.5.27.img?rlkey=1tnhw5qcrmddn3c83z4u22cbi&e=2&dl=0
I have it installed and it works with the script. However, be aware that the adaptive purge line reportedly doesn’t work well with it, while adaptive mesh does. I'm using Obico, but since the 2.3.5.33 update lacks proper Git support, the helper script is significantly limited—“gimped,” for lack of a better word.
Another issue I’ve noticed with both versions is that after a print finishes, tapping the screen brings up the “print complete” menu. However, if you click either of the buttons (print again / okay), the screen dims and becomes unresponsive to touch. The only way to recover is by rebooting the machine or restarting Klipper.
P.S. From what I’ve read and heard, the reason the developer has remained silent on this topic is because he (allegedly!) doesn’t have the upgrade kit or a K2 unit. His focus currently seems to be on the H2D by Bambu. So, it may be a while before we see further development—unless someone else decides to pick up the mantle.

How do you disable adaptive purge in KAMP?

You can edit the file on the machine. In Start_Print.cfg change adaptive mesh from 1 to 0

Near the top, in the output_pin thing, right? The macro doesn't need to be changed?

No you have to either edit the file through fluidd or download the file to your computer from the printer and edit it. Then delete the stock file and upload the new one to the same folder.

It seems to be working by editing [output_pin ADAPTIVE_PURGE_LINE]
I also saw the macro KAMP_PURGE_LINE_SETTINGS for turning on/off the purge line, but I wasn't sure if it would save between restarts.

[jrabkid]

I got all installed however I cant really do much, when trying to home the printer all I get is

"{"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}"

[VashBaldeus]

I got all installed however I cant really do much, when trying to home the printer all I get is

"{"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}"

what firmware version? tried 2.3.5.27?

[Jdbye]

I got all installed however I cant really do much, when trying to home the printer all I get is

"{"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}"

I've got the same issue.....

Did either of you fix it? Having this issue right now...

[Jdbye]

DO NOT install option 3 in the tools menu. "Fix printing Gcode files from folder"
There is no uninstall option for this, the old gcode.py is deleted irrecoverably and the only solution is a factory reset.

[justicestorm]

What what do you mean? My k1se with the cfs upgrade firmware is rooted and now its majorly tweaking out. Is this a possible cause?

DO NOT install option 3 in the tools menu. "Fix printing Gcode files from folder"
There is no uninstall option for this, the old gcode.py is deleted irrecoverably and the only solution is a factory reset.

[Jdbye]

What what do you mean? My k1se with the cfs upgrade firmware is rooted and now its majorly tweaking out. Is this a possible cause?

DO NOT install option 3 in the tools menu. "Fix printing Gcode files from folder"
There is no uninstall option for this, the old gcode.py is deleted irrecoverably and the only solution is a factory reset.

If you're getting the error message mentioned, this is the cause.

[cometsegler]

I had the same problem for 3 weeks when I installed CF's upgrade on my K1Max:
Fluidd installation was terminated. I was able to reinstall Fluidd via helper script, but got error codes during operation
Because I multiplied my problems by changing the stepper motors from 42-60 to 42-48 (board CR4CU220812S12 but entry "hw_version" CR4CU220812S11 in system_version.json)
After factory reset the helper script disappears ... and git clone does not work.
After adjusting factory_printer.cfg and printer.cfg my printer works again, although without Fluidd.
I would copy the files manually, but unfortunately I'm not deep enough in the matter yet

[jrabkid]

What firmware version are you on? .33 doesn't gave the git command any more. There is work around to get it kind of going but version .27 seems to be the best all rounder firmware

[sevagjb]

What firmware version are you on? .33 doesn't gave the git command any more. There is work around to get it kind of going but version .27 seems to be the best all rounder firmware

i upgrade my printer two weeks ago, and after i update the firmware i lost the access to Fluidd but i reinstalled from the script and worked until today when i discovered error from the UI, so i start as usual from the script clean reset then i discovered the problem for the .33 ,
I can't install the script so i reinstalled the .27 and everything worked again,
I am wondering why ceality not making firmware included the fluid, then a lot of people have less problem.

[jrabkid]

What firmware version are you on? .33 doesn't gave the git command any more. There is work around to get it kind of going but version .27 seems to be the best all rounder firmware

i upgrade my printer two weeks ago, and after i update the firmware i lost the access to Fluidd but i reinstalled from the script and worked until today when i discovered error from the UI, so i start as usual from the script clean reset then i discovered the problem for the .33 , I can't install the script so i reinstalled the .27 and everything worked again, I am wondering why ceality not making firmware included the fluid, then a lot of people have less problem.

They do but it's much more cut down. Releasing the full interface opens up a can of worms to damage the printer if you use the software wrong. You have to think that most of their customers are new to printing so it needs to be as simple as possible. While I love fluidd like yourself it can be a minefield to somehow new.

[sevagjb]

They do but it's much more cut down. Releasing the full interface opens up a can of worms to damage the printer if you use the software wrong. You have to think that most of their customers are new to printing so it needs to be as simple as possible. While I love fluidd like yourself it can be a minefield to somehow new.

Yes, absolutely correct, but it already happened in the E3 V3 and Hi and K2, so why not for the K1C?
For example, I have the E3 V3 and use the Fluidd sensors with my home assistant. I've never rooted the printer before, but I need to do that for the K1C and get rid of the hassle of rooting the printer.

[cometsegler]

it is 33, if the git clone command is permanently disabled, i will go back to .27.

[Zionmatrix2025]

Either that or follow the instructions further up...
#787 (comment)

[bud4ever]

i got the script running but facing a lot of issues, as the system got really cut down.
Can't install Obico or Octoeverywhere:

                 =========-=-=-=-------
                     -==-==-=------

OctoEverywhere For Klipper, Creality, Elegoo, And Bambu Lab Printers
The 3D Printing Communities #1 Remote Access And AI Cloud Service

OctoEverywhere empowers the worldwide maker community with...

• Free & Unlimited Mainsail, Fluidd, Elegoo, Creality, And Bambu Lab Printers Remote Access
• Free & Unlimited Next-Gen AI Print Failure Detection
• Free Full Frame Rate & Full Resolution Webcam Streaming
• 5 Star Rated iOS & Android Apps
• Real-Time Print Notifications
• And So Much More

Running in K1 and K1 Max OS mode
Checking required system packages are installed...
Downloading http://bin.entware.net/mipselsf-k3.4/Packages.gz
Updated list of available packages in /opt/var/opkg-lists/entware
Package python3 (3.11.10-1) installed in root is up to date.
Package python3-pip (23.3.1-1) installed in root is up to date.
Package python3-pillow (10.1.0-1) installed in root is up to date.
Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/opt/bin/python3'
isolated = 0
environment = 1
user site = 1
safe_path = 0
import site = 1
is in build tree = 0
stdlib dir = '/opt/lib/python3.11'
sys._base_executable = '/opt/bin/python3'
sys.base_prefix = '/opt'
sys.base_exec_prefix = '/opt'
sys.platlibdir = 'lib'
sys.executable = '/opt/bin/python3'
sys.prefix = '/opt'
sys.exec_prefix = '/opt'
sys.path = [
'/opt/lib/python311.zip',
'/opt/lib/python3.11',
'/opt/lib/python3.11/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x77a74050 (most recent call first):

Checking Python Virtual Environment For OctoEverywhere...
No virtual environment found, creating one now.
Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/opt/bin/python3'
isolated = 0
environment = 1
user site = 1
safe_path = 0
import site = 1
is in build tree = 0
stdlib dir = '/opt/lib/python3.11'
sys._base_executable = '/opt/bin/python3'
sys.base_prefix = '/opt'
sys.base_exec_prefix = '/opt'
sys.platlibdir = 'lib'
sys.executable = '/opt/bin/python3'
sys.prefix = '/opt'
sys.exec_prefix = '/opt'
sys.path = [
'/opt/lib/python311.zip',
'/opt/lib/python3.11',
'/opt/lib/python3.11/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x774eb050 (most recent call first):

Updating PIP if needed... (this can take a few seconds or so)
./install.sh: line 341: /usr/data/octoeverywhere-env/bin/python: not found
Installing or updating required python libs...
./install.sh: line 351: /usr/data/octoeverywhere-env/bin/pip3: not found
./install.sh: line 493: /usr/data/octoeverywhere-env/bin/python3: not found

[Play13thStreet]

Where do you put these Makros?

[bud4ever]

gcode_macro.cfg

[gfrcr]

How is your start print?

[jrabkid]

Sure if it helps. CHECK_FILAMENT_AT_START: prevents printing if filament is not loaded in extruder. Add to machine start gcode in Slicer: CHECK_FILAMENT_AT_START

BOX_LOAD_FROM_CFS: loads from CFS

LOAD_FROM_SPOOL automatically sets correct ID for spoolman. Add to each filament start gcode in Slicer: SET_ACTIVE_SPOOL ID=

LOAD_TPU_MANUAL: slowly loads TPU, could not load TPU via normal extrude

UNLOAD_TPU_MANUAL: slowly unloads TPU

LOAD_FROM_EXTERNAL_SPOOL: loads from external spool ;)

UNLOAD_FROM_CFS: unloads

END_PRINT and END_PRINT_NO_M84: modified to skip unloading after printing via CFS (if you want to print with the same color again). Add SET_GCODE_VARIABLE MACRO=custom_macro VARIABLE=unload_on_end VALUE=0 to machine end gcode

[gcode_macro CHECK_FILAMENT_AT_START]
gcode:
  {% if printer['filament_switch_sensor filament_sensor_2'].filament_detected == False %}
    { action_respond_info("Kein Filament erkannt! Druck wird pausiert.") }
    PAUSE
  {% endif %}

[gcode_macro BOX_LOAD_FROM_CFS]
gcode:
  {% if params.SLOT is defined %}
    T{params.SLOT|int}
    G90
    M117 Lade Filament aus Slot {params.SLOT} ...
    BOX_LOAD_MATERIAL_WITH_MATERIAL
  {% else %}
    {action_respond_info("⚠️ Bitte Parameter SLOT=0–3 angeben")}
  {% endif %}

[gcode_macro LOAD_CFS_1]
gcode:
  BOX_LOAD_FROM_CFS SLOT=0

[gcode_macro LOAD_CFS_2]
gcode:
  BOX_LOAD_FROM_CFS SLOT=1

[gcode_macro LOAD_CFS_3]
gcode:
  BOX_LOAD_FROM_CFS SLOT=2

[gcode_macro LOAD_CFS_4]
gcode:
  BOX_LOAD_FROM_CFS SLOT=3

[gcode_macro LOAD_FROM_SPOOL]
description: Lade Filament vom Spoolman-Eintrag mit ID und CFS-Slot
variable_temp: 0
gcode:
  {% if params.ID is defined and params.SLOT is defined %}
    {% set id = params.ID|int %}
    {% set slot = params.SLOT|int %}
    SET_ACTIVE_SPOOL ID={id}
    {action_respond_info("🎯 Lade Spool ID %d aus Slot %d ..." % (id, slot))}

    {action_call_remote_method(
       "spoolman_get_spool_info",
       spool_id=id
    )}

    {% set material = spoolman.spool.material|lower %}
    {% set hotend_temp = spoolman.spool.print_temp|default(0)|int %}

    {% if hotend_temp == 0 %}
      {action_respond_info("⚠️ Keine gültige Temperatur in Spoolman-Eintrag")}
      ABORT
    {% endif %}

    SET_GCODE_VARIABLE MACRO=custom_macro VARIABLE=default_extruder_temp VALUE={hotend_temp}
    T{slot}
    LOAD_MATERIAL
  {% else %}
    {action_respond_info("⚠️ Syntax: LOAD_FROM_SPOOL ID=<spool_id> SLOT=<0-3>")}
  {% endif %}

[gcode_macro LOAD_TPU_MANUAL]
description: "Lade TPU manuell in die Box – ohne CFS-Zuführung"
gcode:
    M117 Lade TPU manuell...
    M109 S220 ; TPU-typische Temperatur
    M83 ; relative Extrusion
    G91 ; relative Positionierung

    ; Optional: etwas rückziehen, falls Düse voll ist
    G1 E-2 F60

    ; Langsames Einziehen in die Box
    G1 E30 F90
    G1 E30 F60
    G1 E20 F30

    G90 ; zurück zu absoluten Koordinaten
    M117 TPU geladen

[gcode_macro UNLOAD_TPU_MANUAL]
description: "Ziehe TPU manuell aus dem Extruder – ohne CFS"
gcode:
    M117 Entlade TPU manuell...
    M109 S220
    M83
    G91

    ; Langsamer Rückzug
    G1 E-20 F30
    G1 E-30 F60
    G1 E-10 F90

    G90
    M117 TPU entladen

[gcode_macro LOAD_FROM_EXTERNAL_SPOOL]
description: Lade Filament von externer Spule (ohne CFS)
gcode:
  {% if params.ID is defined %}
    {% set id = params.ID|int %}
    SET_ACTIVE_SPOOL ID={id}
    {action_respond_info("🎯 Lade externe Spule ID %d ..." % id)}

    {action_call_remote_method(
       "spoolman_get_spool_info",
       spool_id=id
    )}

    {% set hotend_temp = spoolman.spool.print_temp|default(0)|int %}

    {% if hotend_temp == 0 %}
      {action_respond_info("⚠️ Keine gültige Temperatur in Spoolman-Eintrag")}
      ABORT
    {% endif %}

    SET_GCODE_VARIABLE MACRO=custom_macro VARIABLE=default_extruder_temp VALUE={hotend_temp}
    LOAD_MATERIAL
  {% else %}
    {action_respond_info("⚠️ Syntax: LOAD_FROM_EXTERNAL_SPOOL ID=<spool_id>")}
  {% endif %}

[gcode_macro UNLOAD_FROM_CFS]
description: Entlade Filament korrekt über das CFS-System
gcode:
  M117 Entlade Filament über CFS...
  BOX_QUIT_MATERIAL
  
  

[gcode_macro QUIT_MATERIAL]
variable_enabled: 0
gcode:
  SAVE_GCODE_STATE NAME=myMoveState
  RESTORE_E_CURRENT
  M109 S{printer.custom_macro.default_extruder_temp}
  M83
  {action_respond_info("[QUIT_MATERIAL] ➤ Entladevorgang gestartet")}
  G1 E100 F300
  G1 E-15 F3000
  G1 E-22.4700 F2400
  G1 E-6.4200 F1200
  G1 E-3.2100 F720
  G1 E5.0000 F356
  G1 E-5.0000 F384
  G1 E5.0000 F412
  G1 E-5.0000 F440
  G1 E5.0000 F467
  G1 E-5.0000 F495
  G1 E5.0000 F523
  G1 E-5.0000 F3000
  G1 E-15 F3000
  SET_E_MIN_CURRENT
  RESTORE_GCODE_STATE NAME=myMoveState


[gcode_macro END_PRINT]
gcode:
  {% if printer['gcode_macro custom_macro'].unload_on_end|default(1)|int == 1 %}
    {action_respond_info("[END_PRINT] ➤ QUIT_MATERIAL wird aufgerufen")}
    QUIT_MATERIAL
  {% else %}
    {action_respond_info("[END_PRINT] ➤ QUIT_MATERIAL deaktiviert – Filament bleibt geladen")}
  {% endif %}
  END_PRINT_NO_M84
  M84

[gcode_macro END_PRINT_NO_M84]
gcode:
  {% if printer['gcode_macro custom_macro'].unload_on_end|default(1)|int == 1 %}
    {action_respond_info("🔁 BOX_END_PRINT wird ausgeführt")}
    BOX_END
    BOX_END_PRINT
  {% else %}
    {action_respond_info("⏭️ BOX_END_PRINT übersprungen – Filament bleibt geladen")}
  {% endif %}

  Qmode_exit
  EXCLUDE_OBJECT_RESET
  PRINT_PREPARE_CLEAR
  M220 S100
  SET_VELOCITY_LIMIT ACCEL=5000 ACCEL_TO_DECEL=2500
  TURN_OFF_HEATERS
  M107 P1
  M107 P2
  END_PRINT_POINT
  WAIT_TEMP_START
  BOX_GET_FIVE_WAY_STATE

Hi is it possible to upload the gcode file? the emojis are throwing me off and cant seem to figure them out. Sorry to be stupid.

[jrabkid]

Pretty please? I'm getting nowhere and I cant seem to figure out the emojis to text properly

[gfrcr]

Can someone help me make Kamp work on my K1 MAX? I’ve tried everything and I can’t make the adaptive bed mesh occur

[3rdnfnlbst]

What issue are you having? Your machine is rooted? And you installed kamp correct?

I’ve always used my K1 rooted, with fluidd and KAMP, but since I upgraded with CFS and the .33 firmware, there have been so many problems that I’m even discouraged, well the problem I’m having now is not being able to do the Adaptive Bed Mesh, I select the file directly from the K1 screen as they already said and put the option to calibrate, but it only measures the 4 corners and starts printing, I really don’t know what’s wrong.

so yeah .33 hasn't been the easiest to root but I do have it working. at this moment I have everything working properly. I have been told by another person online that they have .34 and that the rooting process is just like it was before the cfs upgrade with .34 firmware. I have the firmware I just haven't tried it yet. I am willing to send your way if you want to give it a try.

[gfrcr]

If you can send it to me, thank you, I’ve been with CFS for 1 month and I haven’t gotten 1 color print until now, or it crashes the cutter, or because of the mesh bed that takes the entire table and breaks the first layer, I’ve already broken the hot end because of this firmware ... I really can’t do anything

[Zionmatrix2025]

https://file-cdn.creality.com/file/b7988cbf341c24d5d0773adeb35dbb9f/CR4CU220812S11_ota_img_V2.3.5.34.img
from the reddit click below, or use the .27 above

[Zionmatrix2025]

does the custom fan ducts hit the back of the case? Mine is broke free and is held by a rubber band because of the purge wiper.

[gfrcr]

does the custom fan ducts hit the back of the case? Mine is broke free and is held by a rubber band because of the purge wiper.

I’m now with a Ben2c Nautilus, very good alias, but I had to make another part for the purge, but the only thing that’s not working for me is the damn bed mesh

[Killer-boss6814]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

[3rdnfnlbst]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

So in my opinion I don’t think you want to get rid of that empty purge line. The reason I Think it’s still there is for times when you want to print with the side spool. The next command would be to start printing if filament is already loaded. Once it sees no filament is loaded it will begin the CFS loading procedure.

I don’t know which machine you have so I’m linking you to both of the profiles I made for the k1 series for Orca Slicer.

https://www.printables.com/model/1309579-k1-max-cfs-w-orca-config-test-print-7925-update

https://www.printables.com/model/1316504-k1k1ck1se-cfs-upgrade-orca-slicer-config-test-v8

[jrabkid]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

So in my opinion I don’t think you want to get rid of that empty purge line. The reason I Think it’s still there is for times when you want to print with the side spool. The next command would be to start printing if filament is already loaded. Once it sees no filament is loaded it will begin the CFS loading procedure.

I don’t know which machine you have so I’m linking you to both of the profiles I made for the k1 series for Orca Slicer.

https://www.printables.com/model/1309579-k1-max-cfs-w-orca-config-test-print-7925-update

https://www.printables.com/model/1316504-k1k1ck1se-cfs-upgrade-orca-slicer-config-test-v8

These profiles work for the k1 and CFS properly? I think when I tried before I came into gcode issues. It's been a while of course but still.

[3rdnfnlbst]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

So in my opinion I don’t think you want to get rid of that empty purge line. The reason I Think it’s still there is for times when you want to print with the side spool. The next command would be to start printing if filament is already loaded. Once it sees no filament is loaded it will begin the CFS loading procedure.
I don’t know which machine you have so I’m linking you to both of the profiles I made for the k1 series for Orca Slicer.
https://www.printables.com/model/1309579-k1-max-cfs-w-orca-config-test-print-7925-update
https://www.printables.com/model/1316504-k1k1ck1se-cfs-upgrade-orca-slicer-config-test-v8

These profiles work for the k1 and CFS properly? I think when I tried before I came into gcode issues. It's been a while of course but still.

It’s been working for me on the k1 max. I don’t have one of the smaller machines to test with but it should be the same gcode. The only difference is the build size which has been edited

[jrabkid]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

So in my opinion I don’t think you want to get rid of that empty purge line. The reason I Think it’s still there is for times when you want to print with the side spool. The next command would be to start printing if filament is already loaded. Once it sees no filament is loaded it will begin the CFS loading procedure.
I don’t know which machine you have so I’m linking you to both of the profiles I made for the k1 series for Orca Slicer.
https://www.printables.com/model/1309579-k1-max-cfs-w-orca-config-test-print-7925-update
https://www.printables.com/model/1316504-k1k1ck1se-cfs-upgrade-orca-slicer-config-test-v8

These profiles work for the k1 and CFS properly? I think when I tried before I came into gcode issues. It's been a while of course but still.

It’s been working for me on the k1 max. I don’t have one of the smaller machines to test with but it should be the same gcode. The only difference is the build size which has been edited

Excellent, I will have to give that a try as that was one of my biggest gripes is that I had to use creality slicer. While not the worst I certainly love orca better when you have multiple printers.
Thank you for your efforts.

[3rdnfnlbst]

does anyone know how to make the cfs load material via command I can put in a START_PRINT macro? Here is what mine currently looks like.

[gcode_macro START_PRINT]
variable_prepare: `0`
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
   --- Set up temps ---
  {% set bed_temp = params.BED_TEMP|default(printer.custom_macro.default_bed_temp)|float %}
  {% set extruder_temp = params.EXTRUDER_TEMP|default(printer.custom_macro.default_extruder_temp)|float %}
  {% set safe_temp = 130 %}
   --- Step 1: Safe warm-up for leveling ---
  M104 S{safe_temp}          ; start warming nozzle to 130°C (no wait)
  M190 S{bed_temp}           ; wait for bed to reach target
  M109 S{safe_temp}          ; wait for nozzle to reach 130°C
   --- Step 2: Homing & basic prep ---
  PRINT_PREPARE_CLEAR
  CX_ROUGH_G28 EXTRUDER_TEMP={safe_temp} BED_TEMP={bed_temp}
  CX_NOZZLE_CLEAR
  ACCURATE_G28
   --- Step 3: Adaptive Bed Mesh ---
  BED_MESH_CLEAR
  BED_MESH_CALIBRATE
  BED_MESH_PROFILE SAVE=adaptive
  BED_MESH_PROFILE LOAD=adaptive
   --- Step 4: Load filament via BOX/CFS system ---
  {% if 'WITH_MATERIAL' in params|upper %}
      BOX_LOAD_MATERIAL_WITH_MATERIAL
    {% else %}
      BOX_LOAD_MATERIAL_WITHOUT_MATERIAL
    {% endif %}
   --- Step 5: Full heat for printing ---
  M104 S{extruder_temp}
  M109 S{extruder_temp}
   --- Step 6: Final prep & purge ---
  _SMART_PARK
  _LINE_PURGE

Everything except Step 4 works, where it is supposed to load the material. It just skips past it. It does a bed mesh and the goes straight to the line purge and then does the filament change after which doesn't make sense. Has anyone cracked this because I am stumped.

So in my opinion I don’t think you want to get rid of that empty purge line. The reason I Think it’s still there is for times when you want to print with the side spool. The next command would be to start printing if filament is already loaded. Once it sees no filament is loaded it will begin the CFS loading procedure.
I don’t know which machine you have so I’m linking you to both of the profiles I made for the k1 series for Orca Slicer.
https://www.printables.com/model/1309579-k1-max-cfs-w-orca-config-test-print-7925-update
https://www.printables.com/model/1316504-k1k1ck1se-cfs-upgrade-orca-slicer-config-test-v8

These profiles work for the k1 and CFS properly? I think when I tried before I came into gcode issues. It's been a while of course but still.

It’s been working for me on the k1 max. I don’t have one of the smaller machines to test with but it should be the same gcode. The only difference is the build size which has been edited

Excellent, I will have to give that a try as that was one of my biggest gripes is that I had to use creality slicer. While not the worst I certainly love orca better when you have multiple printers. Thank you for your efforts.

Of course. If you can please rate the profile after you use it for a bit and leave a comment.

[Jdbye]

Having some trouble after the upgrade. It went through the self check fine right after installing the CFS firmware, but when I try to start a print it gives me "System error, try restarting" and in the fluidd interface I can see this error: {"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}

That's the homing gcode. No idea why it's failing. Trying to home from the UI does the same thing too.

Additionally, I can no longer do the self check. Something the helper script did must have broken things, unless plugging in the CFS is what broke it. I installed pretty much everything except the remote access stuff, screws tilt adjust and git backup. On .33 firmware since that was on the USB drive.

[justicestorm]

Same on my k1se.

[Jdbye]

I unplugged the CFS, that wasn't it. I removed KAMP just in case, didn't help. I'm going to remove everything I installed with the script and see if it works. If not, factory reset time.

Here is the full log fluidd shows when I try to home:

$ G28 Z
00:11:59  // x_axes is NULL
00:11:59  // move xy
00:11:59  // Klipper state: Shutdown
00:11:59  !! {"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}
00:11:59  !! {"code":"key60", "msg":"Internal error on command:_HOME_Y", "values": ["_HOME_Y"]}
00:11:59  // {"code": "key94", "msg":"MCU 'nozzle_mcu' shutdown: Command request
// This generally occurs in response to an M112 G-Code command
// or in response to an internal error in the host software.", "values": []}
00:11:59  !! {"code": "key94", "msg":"MCU 'nozzle_mcu' shutdown: Command request
00:11:59  // {"code": "key94", "msg":"MCU 'leveling_mcu' shutdown: Command request
// This generally occurs in response to an M112 G-Code command
// or in response to an internal error in the host software.", "values": []}
00:11:59  // {"code": "key94", "msg":"MCU 'leveling_mcu' shutdown: Command request
// This generally occurs in response to an M112 G-Code command
// or in response to an internal error in the host software.", "values": []}
00:11:59  // {"code": "key94", "msg":"MCU 'rpi' shutdown: Command request
// This generally occurs in response to an M112 G-Code command
// or in response to an internal error in the host software.", "values": []}
00:11:59  // {"code": "key94", "msg":"MCU 'mcu' shutdown: Command request
// This generally occurs in response to an M112 G-Code command
// or in response to an internal error in the host software.", "values": []}
00:11:59  !! {"code": "key94", "msg":"MCU 'mcu' shutdown: Command request
00:11:59  !! {"code":"key60", "msg":"Internal error on command:G28", "values": ["G28"]}
00:11:59  !! {"code": "key94", "msg":"MCU 'rpi' shutdown: Command request
00:11:59  !! {"code": "key94", "msg":"MCU 'leveling_mcu' shutdown: Command request
00:12:04  !! {"code": "key294", "msg": "Timeout on wait for oid:4 name:'tmcuart_response' response", "values":[]}
00:12:09  !! {"code": "key294", "msg": "Timeout on wait for oid:4 name:'tmcuart_response' response", "values":[]}

[justicestorm]

Exact same thing im experiencing

[Jdbye]

Had to do a factory reset, self check is working again. I'm going to hope this was just a fluke and try the root helper script again. Otherwise I might have to go without a proper web UI and all the fancy stuff for a while. At least my printer isn't broken.

[Jdbye]

It seems fine now, installed just the essentials (nginx/mainsail/fluidd) so I guess it was a fluke.

I might've accidentally pressed something I shouldn't because after the purge chute calibration it took me to the expert settings menu, I didn't notice and was trying to scroll down and it was pressing things instead, it went into the nozzle PID calibration but I backed out of it immediately. No idea how that works so I definitely don't want to mess with it. So not sure if that could be why but I can't rule it out.

[Jdbye]

The issue reappeared. I am about 90% sure I figured it out. DO NOT install option 3 in the tools menu. "Fix printing Gcode files from folder"
There is no uninstall option for this, the old gcode.py is deleted irrecoverably and the only solution is a factory reset. The error is coming from this file. Have a look here and you can see the error message: https://github.com/Guilouz/Creality-Helper-Script/blob/main/files/fixes/gcode.py#L209C1-L210C114
The script should probably be patching this file rather than replacing it outright. If used on any firmware version the script hasn't been tested on, it's not guaranteed to work. I personally am quite annoyed, after troubleshooting this for hours, to find out that the script simply deletes the old file without making a backup. That's just bad practice.

Edit: Confirmed, that was the issue.

[jrabkid]

Yes I confirmed your theory over the last day or 2 also after countless restores and setups again.

[justicestorm]

Thank you I will do what you tried. Hope it works. Kinda annoyed

[jrabkid]

On a slightly separate note, does ANYONE know how to use the side scrubber on the hopper after it changes filament or purges as it just goes straight from the purge to the print plate. I saw 1 video online that someone done it but cant find info on it anywhere.

[Moonman0922]

I made a macro to use it!
It's not perfect, but you can tune the exact positions. It is made for a K1C and I cant guarantee that it'll work for any other model.
I'm using KAMP so I commented out CX_NOZZLE_CLEAR and added a call to NOZZLE_WIPE_STEP instead in the START_PRINT macro inside of start_print.cfg. However, it should work with the stock START_PRINT macro inside gcode_macro.cfg as long as you do the same!
Let me know if that works for you or if you run into trouble!

[gcode_macro NOZZLE_WIPE_STEP]
gcode:
G90
G1 Z26 F600
BOX_MOVE_TO_SAFE_POS
G1 X168.8 Y215 F4800
G1 X167.8 Y225.8 F4800
G1 X169.8 Y215.8 F4800
G1 X167.8 Y225.8 F4800
G1 X169.8 Y215.8 F4800
G1 X167.8 Y225.8 F4800
G1 X168.8 Y215 F4800
BOX_MOVE_TO_SAFE_POS

[jrabkid]

You stick it on where the instruction tells you to stick it on when fitting the cfs upgrade however most people print out a nozzle wiper and use that gcode. But the nozzle is expected to be cleaned every time and if it doesn't then there is something wrong. If you don't have one on it still looks for it at the back of the printer before the start. If it can't find one it goes ahead.

It actually uses it? I wondered since there isn't any calibration routine to set the position of it and there's already one on the hopper (which does have a calibration routine) that this one was just extra for your own use.

You will find that on all the K1 variants that the one on the hopper is not used at all sadly.

[jrabkid]

I made a macro to use it! It's not perfect, but you can tune the exact positions. It is made for a K1C and I cant guarantee that it'll work for any other model. I'm using KAMP so I commented out CX_NOZZLE_CLEAR and added a call to NOZZLE_WIPE_STEP instead in the START_PRINT macro inside of start_print.cfg. However, it should work with the stock START_PRINT macro inside gcode_macro.cfg as long as you do the same! Let me know if that works for you or if you run into trouble!

[gcode_macro NOZZLE_WIPE_STEP] gcode: G90 G1 Z26 F600 BOX_MOVE_TO_SAFE_POS G1 X168.8 Y215 F4800 G1 X167.8 Y225.8 F4800 G1 X169.8 Y215.8 F4800 G1 X167.8 Y225.8 F4800 G1 X169.8 Y215.8 F4800 G1 X167.8 Y225.8 F4800 G1 X168.8 Y215 F4800 BOX_MOVE_TO_SAFE_POS

You are what they call a legend.... Thank you.

[Moonman0922]

Happy to help!
I'm no expert, but I'm slowly working on adding the functionality I want without messing up my configuration with a firmware update. I plan to add a macro for the cutter soon! I'll update here when I do!

[Jdbye]

I made a macro to use it! It's not perfect, but you can tune the exact positions. It is made for a K1C and I cant guarantee that it'll work for any other model. I'm using KAMP so I commented out CX_NOZZLE_CLEAR and added a call to NOZZLE_WIPE_STEP instead in the START_PRINT macro inside of start_print.cfg. However, it should work with the stock START_PRINT macro inside gcode_macro.cfg as long as you do the same! Let me know if that works for you or if you run into trouble!

[gcode_macro NOZZLE_WIPE_STEP] gcode: G90 G1 Z26 F600 BOX_MOVE_TO_SAFE_POS G1 X168.8 Y215 F4800 G1 X167.8 Y225.8 F4800 G1 X169.8 Y215.8 F4800 G1 X167.8 Y225.8 F4800 G1 X169.8 Y215.8 F4800 G1 X167.8 Y225.8 F4800 G1 X168.8 Y215 F4800 BOX_MOVE_TO_SAFE_POS

Nice! It seems like this firmware does not do a purge line the way previous firmwares did, so I am guessing that CX_NOZZLE_CLEAR is where the adhesive nozzle brush is being used. So changing it in START_PRINT should make it use the hopper brush instead of the adhesive brush. Very clean solution. I am worried that the adhesive brush will come off in cleaning, I am not sure how water (and alcohol) resistant that adhesive is, so this will surely come in handy.

[Jdbye]

My printer pauses every time after the first filament change. I hit resume and then it doesn't happen again for the rest of the print. Anybody know why? Is it something in OrcaSlicer? I have manual filament change turned off and the filament change g-code copied from Creality Print. All the other G-code is pretty standard too (I think I copied all of it from Creality Print and changed nothing but that was a while ago)

[jrabkid]

It will not work with settings directly copied from creality print and is well stated already in this chat. You need to use the print profile on printables to use orca and even that's hot and miss. Use creality print to see if it does it with that first. If not then you know your problem.

[Jdbye]

It will not work with settings directly copied from creality print and is well stated already in this chat. You need to use the print profile on printables to use orca and even that's hot and miss. Use creality print to see if it does it with that first. If not then you know your problem.

It works though. That's the only issue I'm having. Seems like it should be an easy fix, it's probably just a setting I overlooked. I already have a profile I tuned and that one seems to do a lot of unnecessary things, like using a prime tower, doing manual toolchanges in start print (OrcaSlicer is already inserting a toolchange after the start print command), making a purge line (unnecessary when the printer can poop it out), and changing a ton of settings which I'm unsure of the effect they have. I'm not sure this profile is an overall improvement over what I already have. I am not even sure that the prime tower would work as intended because the printer would still do its own poops on every toolchange anyway so you'd just get double the waste? Anyways, there is just too much changed there for me to incorporate all this into my existing profile. But the one thing that isn't different is the gcode. Besides the unneccessary extra fluff in the start print gcode it's identical to mine.

[jrabkid]

It will not work with settings directly copied from creality print and is well stated already in this chat. You need to use the print profile on printables to use orca and even that's hot and miss. Use creality print to see if it does it with that first. If not then you know your problem.

It works though. That's the only issue I'm having. Seems like it should be an easy fix, it's probably just a setting I overlooked. I already have a profile I tuned and that one seems to do a lot of unnecessary things, like using a prime tower, doing manual toolchanges in start print (OrcaSlicer is already inserting a toolchange after the start print command), making a purge line (unnecessary when the printer can poop it out), and changing a ton of settings which I'm unsure of the effect they have. I'm not sure this profile is an overall improvement over what I already have. I am not even sure that the prime tower would work as intended because the printer would still do its own poops on every toolchange anyway so you'd just get double the waste? Anyways, there is just too much changed there for me to incorporate all this into my existing profile. But the one thing that isn't different is the gcode. Besides the unneccessary extra fluff in the start print gcode it's identical to mine.

Hmm... that is weird and you may be one of the few lucky ones, for me and many others there seems to be an error with the Start gcode that stops it from even starting and I cant figure it out myself however when using the profile from printables it works great. I hold my hand up on this part then as I dont know what to tell you mate lol

[Jdbye]

It will not work with settings directly copied from creality print and is well stated already in this chat. You need to use the print profile on printables to use orca and even that's hot and miss. Use creality print to see if it does it with that first. If not then you know your problem.

It works though. That's the only issue I'm having. Seems like it should be an easy fix, it's probably just a setting I overlooked. I already have a profile I tuned and that one seems to do a lot of unnecessary things, like using a prime tower, doing manual toolchanges in start print (OrcaSlicer is already inserting a toolchange after the start print command), making a purge line (unnecessary when the printer can poop it out), and changing a ton of settings which I'm unsure of the effect they have. I'm not sure this profile is an overall improvement over what I already have. I am not even sure that the prime tower would work as intended because the printer would still do its own poops on every toolchange anyway so you'd just get double the waste? Anyways, there is just too much changed there for me to incorporate all this into my existing profile. But the one thing that isn't different is the gcode. Besides the unneccessary extra fluff in the start print gcode it's identical to mine.

Hmm... that is weird and you may be one of the few lucky ones, for me and many others there seems to be an error with the Start gcode that stops it from even starting and I cant figure it out myself however when using the profile from printables it works great. I hold my hand up on this part then as I dont know what to tell you mate lol

Here is mine, you can compare:

M140 S0
M104 S0 
START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer] BED_TEMP=[bed_temperature_initial_layer_single]

I am guessing that your error might be in the settings and not the gcode, my printer settings are from an older profile that was recommended when I bought this printer (sorry I don't remember which site I got it from), which I tweaked by tuning all of the speed settings as they were not optimized for speed (copying a lot from Creality Print) and went through every setting in Creality Print and compared the two to make sure nothing important was missing, and has been working well for me for a long time before the CFS upgrade. I only had to turn off the "manual filament change" setting and add the filament change gcode to make the CFS work on it.

I can share my profile if you like.

As for my issue with the printer pausing after first filament change. There is no pause or M600 inserted into the gcode file. So this pause must be happening on the printer side somehow, perhaps in one of the macros. It's not a huge problem as I can resume it from the web UI but I would like to solve it if possible. This doesn't happen on the tool change called at the start of every print but only on the first filament change in prints that use multi color. I have only printed 2 multi color prints so far but it happened with both.

Edit: I have also just tweaked the gcode following the OrcaSlicer section on this wiki to add SET_PRINT_STATS_INFO into machine start and layer change gcode for layer stats as mine was missing it.

[Jdbye]

3rd multi color print, the printer didn't pause this time. So maybe that was a coincidence or related to some error, though I didn't see one on the screen when it happened and I was standing by the printer last time.

[Jdbye]

M600 macro doesn't unload filament with the CFS, does anybody know how to make it work so the CFS unloads the filament making it easy to swap filament? I have to do it through the touchscreen UI and it's more complicated to do now as it makes you set the filament type for the active slot in the CFS before it will let you do anything. It's not as simple as check temperature and hit retract anymore.
Is there a specific macro to unload filament with the CFS? Then one could simply replace the _UNLOAD_FILAMENT macro in the m600 gcode. This information seems impossible to find on Google so I am afraid nobody knows but this is probably the best place to ask.
The entire M600 macro can probably be reduced down to a simple unload CFS and pause. On resume the CFS will just load the last slot used automatically so the custom resume is not needed.
I wish that Creality would document their custom gcode/macros as they do not seem to be visible in the .cfg files so they must be baked into the firmware.

Edit: It seems that simply doing a tool change with T17 (or perhaps with any non existent tool) unloads the CFS on the K2, will have to test this. It might be necessary to save the current tool before unload, and do a tool change on resume to load the previous filament.

[jrabkid]

M600 macro doesn't unload filament with the CFS, does anybody know how to make it work so the CFS unloads the filament making it easy to swap filament? I have to do it through the touchscreen UI and it's more complicated to do now as it makes you set the filament type for the active slot in the CFS before it will let you do anything. It's not as simple as check temperature and hit retract anymore. Is there a specific macro to unload filament with the CFS? Then one could simply replace the _UNLOAD_FILAMENT macro in the m600 gcode. This information seems impossible to find on Google so I am afraid nobody knows but this is probably the best place to ask. The entire M600 macro can probably be reduced down to a simple unload CFS and pause. On resume the CFS will just load the last slot used automatically so the custom resume is not needed. I wish that Creality would document their custom gcode/macros as they do not seem to be visible in the .cfg files so they must be baked into the firmware.

Edit: It seems that simply doing a tool change with T17 (or perhaps with any non existent tool) unloads the CFS on the K2, will have to test this. It might be necessary to save the current tool before unload, and do a tool change on resume to load the previous filament.

On the helper script there is an option to add the M600 command is there not from memory? Dont quote me on that but I thought there was.

Edit: There is:
https://guilouz.github.io/Creality-Helper-Script-Wiki/helper-script/helper-script-installation/#install-menu

[Jdbye]

M600 macro doesn't unload filament with the CFS, does anybody know how to make it work so the CFS unloads the filament making it easy to swap filament? I have to do it through the touchscreen UI and it's more complicated to do now as it makes you set the filament type for the active slot in the CFS before it will let you do anything. It's not as simple as check temperature and hit retract anymore. Is there a specific macro to unload filament with the CFS? Then one could simply replace the _UNLOAD_FILAMENT macro in the m600 gcode. This information seems impossible to find on Google so I am afraid nobody knows but this is probably the best place to ask. The entire M600 macro can probably be reduced down to a simple unload CFS and pause. On resume the CFS will just load the last slot used automatically so the custom resume is not needed. I wish that Creality would document their custom gcode/macros as they do not seem to be visible in the .cfg files so they must be baked into the firmware.
Edit: It seems that simply doing a tool change with T17 (or perhaps with any non existent tool) unloads the CFS on the K2, will have to test this. It might be necessary to save the current tool before unload, and do a tool change on resume to load the previous filament.

On the helper script there is an option to add the M600 command is there not from memory? Dont quote me on that but I thought there was.

Edit: There is: https://guilouz.github.io/Creality-Helper-Script-Wiki/helper-script/helper-script-installation/#install-menu

I think you missed the point. The M600 command isn't designed for the CFS so it can't unload the active filament in the CFS, I am asking if there is a way to modify it to unload the filament from the CFS. I think the T17 command is probably it. But it will take rewriting the M600 gcode. So I'm going to look into that.
You can't load new filament into the CFS while there is a filament loaded into the printer because of the silly routine it goes through whenever you insert a filament so the active filament has to be unloaded before new filament can be loaded in any of the slots.

[jrabkid]

Apologies, I was half sleeping when reading and just noticed the m600 part and didn't take the time to read it all properly.

[Jdbye]

I have figured that the M600 macro is not being properly installed. The RESUME macro in gcode_macro.cfg is not being fully commented out and I just ran into an infinite pause/resume loop where I was not able to continue the print. So don't install M600 support.

[justicestorm]

Wait can you explain what you had to change?

My k1se is now saying its a k1c and on other .conf it is saying k1max

I had the same problem for 3 weeks when I installed CF's upgrade on my K1Max:
Fluidd installation was terminated. I was able to reinstall Fluidd via helper script, but got error codes during operation
Because I multiplied my problems by changing the stepper motors from 42-60 to 42-48 (board CR4CU220812S12 but entry "hw_version" CR4CU220812S11 in system_version.json)
After factory reset the helper script disappears ... and git clone does not work.
After adjusting factory_printer.cfg and printer.cfg my printer works again, although without Fluidd.
I would copy the files manually, but unfortunately I'm not deep enough in the matter yet

[Mixerdude]

Any plans to support the script on CFS-upgraded K1's? I know the upgrade kit comes with new firmware, I've just ordered mine

I keep getting TC2841 code formatted 2 times 3 extruders filament is cutting fine. The CFS will not return filament until i taker it out of the extruder then it works.

[Jdbye]

Any plans to support the script on CFS-upgraded K1's? I know the upgrade kit comes with new firmware, I've just ordered mine

I keep getting TC2841 code formatted 2 times 3 extruders filament is cutting fine. The CFS will not return filament until i taker it out of the extruder then it works.

I started getting this error so I took the extruder apart, put it back together, ran the cutter calibration again then everything was fine. I think there may have been a piece of filament jammed that was preventing the cutter from working correctly.

[eugenz3rr]

Context: K1 w. CFS upgrade.

K1 Firmware version: 2.3.5.34
CFS Firmware version: 1.1.3
Creality-Helper-Script: v0.0.0-1-gb46787a6-inferred
mainsail: v2.17.0
moonraker: v0.10.0-3-g343bba4c

Specific Problems I have figured out so far.

1. If KAMP is enabled the neither of two settings (Adaptive Bed Mesh/Full Bed Mesh) will work. Why?
   The Purge Line is done without loaded Filament. So it'll just push the remaining filament and drag it around.
2. The CFS-Upgrade came with a brush that wasn't used (it's installed to the right of the poop shoot).

Current solution that works for me so far.

1. When installing KAMP the original START_PRINT macro is commented out and replaced with a KAMP START_MACRO that worked for the K1 non CFS Firmware Version 1.x.
   Due to me not having much time I used Gemini to merge the newer Version of the START_PRINT with the older KAMP START_PRINT. This came out and the purge line worked again!
2. Additionally to the above changes I added the custom macro from @Moonman0922
   I placed this gcode into /usr/data/printer_data/config/Helper-Script/KAMP/Start_Print.cfg

[gcode_macro NOZZLE_WIPE_STEP]
gcode:
    G90
    G1 Z26 F600
    BOX_MOVE_TO_SAFE_POS
    G1 X168.8 Y215 F4800
    G1 X167.8 Y225.8 F4800
    G1 X169.8 Y215.8 F4800
    G1 X167.8 Y225.8 F4800
    G1 X169.8 Y215.8 F4800
    G1 X167.8 Y225.8 F4800
    G1 X168.8 Y215 F4800
    BOX_MOVE_TO_SAFE_POS

[gcode_macro START_PRINT]
variable_prepare: 0
gcode:
  # --- CFS / BOX INITIALIZATION ---
  BOX_START_PRINT                       ; Initialize CFS logic
  G90
  WAIT_TEMP_END
  CLEAR_PAUSE

  # --- TEMPERATURE SETTINGS ---
  {% 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 %}

  # --- PRE-PRINT PREP & MESHING ---
  {% if printer['gcode_macro START_PRINT'].prepare|int == 0 %}
    PRINT_PREPARE_CLEAR
    CX_ROUGH_G28 EXTRUDER_TEMP={extruder_temp} BED_TEMP={bed_temp}

    #    # --- MODIFICATION START ---
    # CX_NOZZLE_CLEAR   <-- Commented out stock macro
    NOZZLE_WIPE_STEP  ; <-- Replaced with custom macro
    # --- MODIFICATION END ---

    ACCURATE_G28
    
    {% if printer['output_pin ADAPTIVE_BED_MESH'].value == 1 %}
      RESPOND TYPE=command MSG="Starting Adaptive Bed Mesh..."
      BED_MESH_CLEAR
      BED_MESH_CALIBRATE
      BED_MESH_PROFILE SAVE=adaptive
      BED_MESH_PROFILE LOAD=adaptive
    {% else %}
      {% if printer['output_pin FULL_BED_MESH'].value == 0 and (not printer['bed_mesh'].profile_name) %}
        RESPOND TYPE=command MSG="No bed mesh found. Starting Full Bed Mesh..."
        CX_PRINT_LEVELING_CALIBRATION
      {% endif %}
      {% if printer['output_pin FULL_BED_MESH'].value == 1 %}
        RESPOND TYPE=command MSG="Starting Full Bed Mesh..."
        CX_PRINT_LEVELING_CALIBRATION
      {% endif %}
      BED_MESH_PROFILE LOAD=default
    {% endif %}
  {% else %}
    PRINT_PREPARE_CLEAR
  {% endif %}

  # --- CFS FILAMENT LOADING ---
  M140 S{bed_temp}
  M104 S{extruder_temp}
  # This command tells the CFS to feed the material to the nozzle
  BOX_START_PRINT_EXTRUDE_MATERIAL START_PRINT=8 

  # Wait for final temps
  M190 S{bed_temp}
  M109 S{extruder_temp}

  # --- PURGE LINE LOGIC ---
  {% if printer['output_pin ADAPTIVE_PURGE_LINE'].value == 1 %}
    _SMART_PARK
    RESPOND TYPE=command MSG="Starting Adaptive Purge Line..."
    _LINE_PURGE
  {% else %}  
    RESPOND TYPE=command MSG="Starting Classic Purge Line..."
    CX_PRINT_DRAW_ONE_LINE EXTRUDER_TEMP={extruder_temp} BED_TEMP={bed_temp} NEED_G28=0
  {% endif %}

  SET_VELOCITY_LIMIT ACCEL={printer.configfile.settings.printer.max_accel}

Maybe this helps someone in need as much it helped me. Maybe we can build on that and create a cfs fork?

[koen01]

if you have issues with creality print 7 and KAMP where the printer first does a full mesh (because of the no object detected message) and then the adaptive mesh, change the print_prepared macro in start_print.cfg to this:

[gcode_macro PRINT_PREPARED]
gcode:
{action_respond_info("print prepared
(prepare flag suppressed for KAMP)")}

[Peeecha]

The above macro didn't work for me. Took me a while to figure out why my printer still does the full mesh.

If you are like me and have the printer linked to creality cloud, then there is this magical toggle in Workbench - Device settings - Print detection with AI - Print calibration. In my case it was turned on and surprisingly it can't be toggled off (there is some JS bug). If I remember correctly, similar pre-print calibration setting was on the older firmware directly on the printer. But its gone now.

This does the full mesh calibration. If you have more luck than me, try turning that off first.

If not, then you need to replace the CX_PRINT_LEVELING_CALIBRATION.
Add this to your gcode_macro.cfg:

[gcode_macro CX_PRINT_LEVELING_CALIBRATION]
rename_existing: CX_PRINT_LEVELING_CALIBRATION_ORIG
gcode:
  {action_respond_info("CX_PRINT_LEVELING_CALIBRATION called - skipped, KAMP will handle mesh")}

Then update the full mesh fallback branch inside the START_PRINT macro from @eugenz3rr to this:

{% if printer['output_pin FULL_BED_MESH'].value == 0 and (not printer['bed_mesh'].profile_name) %}
  RESPOND TYPE=command MSG="No bed mesh found. Starting Full Bed Mesh..."
  CX_PRINT_LEVELING_CALIBRATION_ORIG
{% endif %}
{% if printer['output_pin FULL_BED_MESH'].value == 1 %}
  RESPOND TYPE=command MSG="Starting Full Bed Mesh..."
  CX_PRINT_LEVELING_CALIBRATION_ORIG
{% endif %}

This way the Creality prepare phase calls CX_PRINT_LEVELING_CALIBRATION and gets silently skipped, but your macro can still trigger a real full mesh when genuinely needed by calling _ORIG directly.

And to get rid off the empty wipe on the bed, if you don't have the bristles glued, and are using the macro for side brush on the hopper, you need to replace the CX_NOZZLE_CLEAR.
Add this to your gcode_macro.cfg:

[gcode_macro CX_NOZZLE_CLEAR]
rename_existing: CX_NOZZLE_CLEAR_ORIG
gcode:
  {action_respond_info("CX_NOZZLE_CLEAR skipped - using custom NOZZLE_WIPE_STEP instead")}

[KaraokeAmerica]

Is this conversation about ONLY the regular CFS or also the CFS-C?

[Jdbye]

I have the regular CFS, of course I can't speak for anybody else, but I'd guess a majority have the regular CFS since the CFS-C only released recently.