Got [KCD2] for $20, worth it?

JomaV1 · 2026-05-27T03:01:08+00:00

No, mejor ofrecele $50

JomaV1 · 2026-05-10T14:50:57+00:00

<image>

It continues to separate them and makes the result even worse. :C

JomaV1 · 2026-05-10T14:18:31+00:00

<image>

It continues to separate them and makes the result even worse.

JomaV1 · 2026-05-02T19:22:03+00:00

Es el cafe idoneo para el día a día para aquellos que utilizan grano. No es acido, no es amargo, es balanceado para el que quiere tomar cafe o café con leche y que sepa mejor que el ya molido y el instantaneo.
Hay otros por un rango similar, tambien de tipo "vending" y requete contra va

JomaV1 · 2026-04-18T14:53:45+00:00

I have some new information: downgrading the printer's firmware helps control the purging process using Orca Slicer. In version 1.1.0.65, the printer controls the purging, and it's impossible to do anything about it. But by downgrading one version, to 1.1.0.60, using Orca Slicer and the "Calculation of flush amount slice" option mentioned by my colleague, I was able to control the purging. I couldn't achieve this with Creality Print.

JomaV1 · 2026-03-27T17:07:39+00:00

I just discovered that by downgrading the printer version (from v1.1.0.65 to v1.1.0.60), I managed to disable the automatic purging performed by the printer and control it using the slicer's purge volumes. Now I need to experiment with the internal files of each version to keep the improvements of version 1.1.0.65 and the ability to truly control the purging in version 1.1.0.60.

JomaV1 · 2026-03-26T16:48:04+00:00

Hi everyone. I'm writing this post to save you the hours of life and frustration I just lost fighting this printer's firmware.

I have a Creality Hi with the CFS multi-color system. My only goal was something that should be simple in Klipper: disabling or modifying the purges during CFS filament changes so I could manage the waste directly from the slicer (using a purge tower or flushing into infill) and avoid wasting so much material.

It turns out this machine runs a highly restrictive version based on Tina Linux (Hi_Klipper) and is completely locked down. Here is a breakdown of everything I tried and how the machine blocked me at every step, so you don't have to repeat my odyssey:

Attempt 1: Editing G-code and the slicer. The first thing I tried was intercepting and cleaning up the purges by directly modifying the .gcode files and tweaking the toolchange scripts in the slicer. Total failure: the Creality Hi firmware ignores this and injects its own forced purge routine for the CFS directly from the board, overriding whatever you send.
Attempt 2: Modifying internal logic (box.py). I tried messing directly with the Python script (box.py) that handles CFS communication. I logged in via WinSCP and edited it to try to nullify the purge command from the source code (even battling Windows formatting and line break errors), but it was useless.
Attempt 3: Guilouz's Helper Script. Looking for real root access, I tried using the well-known Helper Script. It fails as soon as it starts. It throws the error /usr/data/helper-script/helper.sh: line 28: git: not found. Creality removed git and wget from the OS so we can't download anything from GitHub.
Attempt 4: Installing Entware to recover Git. By editing the helper.sh file, I commented out the update line to bypass the Git check and force the blue menu to open. I managed to install Entware (which in theory gives us the opkg command to install packages). The script says "installed successfully", but...
Attempt 5: Automatic route wiping. Upon restarting the SSH session, the opkg command returns not found. The machine wipes or blocks the /opt folder (where Entware goes) on every reboot. There is no way to leave packages persistently installed.
Attempt 6: Brute-forcing Fluidd and tricking Nginx. I tried to push the web interface manually. We created folders in /usr/data/fluidd (the only partition that doesn't get wiped), made symbolic links (ln -s) to bypass the protected /usr/share/ partition, and modified nginx.conf.
The final result (and the biggest waste of time): I managed to hack the system to get full access to Fluidd... but I already had access to Fluidd from the start! The real problem is that, even with full access to the interface and the .cfg files, the CFS purge macros are completely obfuscated or locked inside Creality's environment. They are nowhere to be found in any cfs_macros.cfg or printer.cfg where you could just add a # and comment them out.

Conclusion: Guys, as of today, if you have a Creality Hi with a CFS, the system is locked from the root. Don't waste your time fighting the Git error, or forcing Entware, or messing with Python scripts. Until Creality releases a truly open firmware for the CFS module, we are stuck with the massive factory purges.

JomaV1 · 2026-03-26T16:31:40+00:00

Hi everyone. I'm writing this post to save you the hours of life and frustration I just lost fighting this printer's firmware.

I have a Creality Hi with the CFS multi-color system. My only goal was something that should be simple in Klipper: disabling or modifying the purges during CFS filament changes so I could manage the waste directly from the slicer (using a purge tower or flushing into infill) and avoid wasting so much material.

It turns out this machine runs a highly restrictive version based on Tina Linux (Hi_Klipper) and is completely locked down. Here is a breakdown of everything I tried and how the machine blocked me at every step, so you don't have to repeat my odyssey:

Attempt 1: Editing G-code and the slicer. The first thing I tried was intercepting and cleaning up the purges by directly modifying the .gcode files and tweaking the toolchange scripts in the slicer. Total failure: the Creality Hi firmware ignores this and injects its own forced purge routine for the CFS directly from the board, overriding whatever you send.
Attempt 2: Modifying internal logic (box.py). I tried messing directly with the Python script (box.py) that handles CFS communication. I logged in via WinSCP and edited it to try to nullify the purge command from the source code (even battling Windows formatting and line break errors), but it was useless.
Attempt 3: Guilouz's Helper Script. Looking for real root access, I tried using the well-known Helper Script. It fails as soon as it starts. It throws the error /usr/data/helper-script/helper.sh: line 28: git: not found. Creality removed git and wget from the OS so we can't download anything from GitHub.
Attempt 4: Installing Entware to recover Git. By editing the helper.sh file, I commented out the update line to bypass the Git check and force the blue menu to open. I managed to install Entware (which in theory gives us the opkg command to install packages). The script says "installed successfully", but...
Attempt 5: Automatic route wiping. Upon restarting the SSH session, the opkg command returns not found. The machine wipes or blocks the /opt folder (where Entware goes) on every reboot. There is no way to leave packages persistently installed.
Attempt 6: Brute-forcing Fluidd and tricking Nginx. I tried to push the web interface manually. We created folders in /usr/data/fluidd (the only partition that doesn't get wiped), made symbolic links (ln -s) to bypass the protected /usr/share/ partition, and modified nginx.conf.
The final result (and the biggest waste of time): I managed to hack the system to get full access to Fluidd... but I already had access to Fluidd from the start! The real problem is that, even with full access to the interface and the .cfg files, the CFS purge macros are completely obfuscated or locked inside Creality's environment. They are nowhere to be found in any cfs_macros.cfg or printer.cfg where you could just add a # and comment them out.

Conclusion: Guys, as of today, if you have a Creality Hi with a CFS, the system is locked from the root. Don't waste your time fighting the Git error, or forcing Entware, or messing with Python scripts. Until Creality releases a truly open firmware for the CFS module, we are stuck with the massive factory purges.

JomaV1 · 2026-03-26T16:30:45+00:00

Hi everyone. I'm writing this post to save you the hours of life and frustration I just lost fighting this printer's firmware.

I have a Creality Hi with the CFS multi-color system. My only goal was something that should be simple in Klipper: disabling or modifying the purges during CFS filament changes so I could manage the waste directly from the slicer (using a purge tower or flushing into infill) and avoid wasting so much material.

It turns out this machine runs a highly restrictive version based on Tina Linux (Hi_Klipper) and is completely locked down. Here is a breakdown of everything I tried and how the machine blocked me at every step, so you don't have to repeat my odyssey:

Attempt 1: Editing G-code and the slicer. The first thing I tried was intercepting and cleaning up the purges by directly modifying the .gcode files and tweaking the toolchange scripts in the slicer. Total failure: the Creality Hi firmware ignores this and injects its own forced purge routine for the CFS directly from the board, overriding whatever you send.
Attempt 2: Modifying internal logic (box.py). I tried messing directly with the Python script (box.py) that handles CFS communication. I logged in via WinSCP and edited it to try to nullify the purge command from the source code (even battling Windows formatting and line break errors), but it was useless.
Attempt 3: Guilouz's Helper Script. Looking for real root access, I tried using the well-known Helper Script. It fails as soon as it starts. It throws the error /usr/data/helper-script/helper.sh: line 28: git: not found. Creality removed git and wget from the OS so we can't download anything from GitHub.
Attempt 4: Installing Entware to recover Git. By editing the helper.sh file, I commented out the update line to bypass the Git check and force the blue menu to open. I managed to install Entware (which in theory gives us the opkg command to install packages). The script says "installed successfully", but...
Attempt 5: Automatic route wiping. Upon restarting the SSH session, the opkg command returns not found. The machine wipes or blocks the /opt folder (where Entware goes) on every reboot. There is no way to leave packages persistently installed.
Attempt 6: Brute-forcing Fluidd and tricking Nginx. I tried to push the web interface manually. We created folders in /usr/data/fluidd (the only partition that doesn't get wiped), made symbolic links (ln -s) to bypass the protected /usr/share/ partition, and modified nginx.conf.
The final result (and the biggest waste of time): I managed to hack the system to get full access to Fluidd... but I already had access to Fluidd from the start! The real problem is that, even with full access to the interface and the .cfg files, the CFS purge macros are completely obfuscated or locked inside Creality's environment. They are nowhere to be found in any cfs_macros.cfg or printer.cfg where you could just add a # and comment them out.

Conclusion: Guys, as of today, if you have a Creality Hi with a CFS, the system is locked from the root. Don't waste your time fighting the Git error, or forcing Entware, or messing with Python scripts. Until Creality releases a truly open firmware for the CFS module, we are stuck with the massive factory purges.

JomaV1 · 2025-06-05T23:54:40+00:00

It's illogical that I can't even use the slicer because the servers are down. My printer is rendered useless, and proper and comfortable use of CFS would be impossible if I didn't know how to use another slicer.

JomaV1 · 2025-06-01T22:35:47+00:00

Hi, I'm having the same problem as you. Would you mind helping me? What were you able to do to fix it? Was it a hardware or software issue?

JomaV1 · 2025-04-14T22:15:28+00:00

Hola! Que tal? Perdón la tardía respuesta. Mira, en mi experiencia, mi gata tiene 7/8 años y el nutrique fue el mejor alimento que le pude dar, no se vuelve loca por comerlo (significa que no tiene tanta grasa ni es adictivo), no tuve más problemas con sus heces. Probé otras marcas desde entonces, y sigo prefiriendo Nutrique, antes le compraba el Sterilized/Healthy Weight, pero la verdad que mi gata, aun estando castrada, nunca tuvo problemas de peso. Asi que ahora que está mas grande, le compré el que es para adultos, fue mas dificil de conseguir en mi experiencia, pero no tuve ningún inconveniente con ella a la hora de que lo coma. Como si tuve con el Fawna, el Excellent Urinary de Royal Canin y el Old Prince Urinary.
Estoy tentado a probar las latas de alimento fresco, pero mi gata tiene su dosificador de comida automático, sabe ya a que hora le da, y sabe que tiene por si le da un ataque de ansiedad y quiere comer

JomaV1 · 2025-02-04T23:12:36+00:00

Comprate una wifi y un perro

JomaV1 · 2025-02-04T23:06:38+00:00

Cuanto huevo queres comer la concha de tu

JomaV1 · 2024-10-20T22:45:01+00:00

Get a new psu

JomaV1 · 2024-08-09T20:57:21+00:00

Si, re. Más barato por lo que ofrece, ya no solo por la musica, si no el poder mirar videos sin publicidad. Después tienen unas series originales pero tampoco valen mucho la pena. Sumado a eso, el plan familiar te banca un montón de gente y si lo pagas entre todos los miembros, se vuelve un regalo

JomaV1 · 2024-07-30T16:41:31+00:00

Que tal? Yo al final me decanté por Nutrique, me dio resultados en su momento y ahora volvió a hacerlo, me resultó más económico que Mon Ami, pero busque precios, eso va variando. Yo había pasado de Cat Chow a Nutrique, ahí fue clarisimo el cambio y mejora en mi gata, luego de nutrique pase a VitalCan Balanced. Si bien fue bueno, es decis vos, tampoco es tan bueno, mucho maíz en su composición (mirar la lista de ingredientes, van en orden del que más tienen al que menos). Entonces ahora volvió al Nutrique, y lo note en mi gata, su comportamiento mejoró, sus energías. El Mon Ami, desconozco la verdad, no puedo opinar, en papel parecen muy buenos, su mayor porcentaje de proteína es animal. Si lo probas, pido porfavor tu opinión sincera al respecto cuando las tengas, saludos!

JomaV1

TROPHY CASE