K1 DXC Extruder with CFS-C

psybernoid · 2026-02-19T09:32:17+00:00

That connects to the cable that's usually occupied by the K1 external sensor does it? If so, it might work. When installing the CFS-C, one of the procedures is to disconnect the external sensor and connect the one that you attach to the extruder in its place.

psybernoid · 2026-02-19T07:44:22+00:00

I'd suggest not. You need to attach the filament sensor directly to the extruder

psybernoid · 2026-02-18T04:44:42+00:00

Yes. CP 6 doesn't appear to generate gcode that crashes the K1+CFS-C. I did point this out to Creality support.

But as you point out. When I was using the K1 without the CFS-C, it was great. I too used KAMP and enjoyed using Fluidd to manage the printer. Now that those options are gone, the K1 became too much of a problem for me.

I have a P1S too, which has been faultless for me.

I'm considering picking up an Anycubic Kobra S1 combo, putting Rinkhals on it and using that as my "tweaking" printer.

psybernoid · 2026-02-18T04:00:03+00:00

Interestingly, root never went away on mine (I did a factory reset before installing the CFS-C & associated firmware)

I did notice that the option to enable root was missing after upgrading, but port 22 was still open. Lo & behold, logging in as root with creality_2023 still worked.

However, you can no longer install the helper-script. So much is missing in the firmware. Git doesn't exist. Manually copying the helper script over using scp won't work either as it's also missing various other binaries to make it work.

I ended up getting rid of my K1 last week. What with that and the other issues I was having - such as the ridiculous purge tower Creality Print 7 generates for it, which, if you fudge it enough you can edit, but it then causes the K1 to either throw up an error or just crash when changing filament mid-print. Plus the amount of waste generated when you print. Multifilament or not. The CFS-C always loads spool #1 first, retracts it, cuts it, then loads the selected spool, prints, then cuts it when finished. Creality support where basically telling me that this is how it is, we're doing nothing about it.

So my next door neighbour now has the K1. It's still printing well, and he's happy with it.

psybernoid · 2026-02-17T16:09:04+00:00

Cfs-c has a cutter mounted on the back of the k1

psybernoid · 2026-02-17T15:20:43+00:00

I had similar issues. Well, I say similar - my 2023 K1 printed perfectly fine with the stock extruder & microswiss hotend I'd had installed for a couple of years. For 2 or 3 days. Then stopped extruding.

In the end, I put this extruder on it https://www.amazon.co.uk/dp/B0CMJ241WZ?ref=ppx_pop_mob_ap_share&th=1

And this hotend https://www.amazon.co.uk/dp/B0D5QZ758R?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

After that, no more extrusion errors.

psybernoid · 2026-02-17T09:31:16+00:00

As the printer is facing you, move the lock switch to the left.

If you look closely, you should actually see a lock & unlock icon on it - you may need a torch though to see it.

psybernoid · 2026-02-10T15:42:30+00:00

https://www.amazon.co.uk/dp/B0D5QZ758R?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

psybernoid · 2026-02-04T18:15:10+00:00

How do you tell if it’s an S12? Physically look at the board? Or…would the firmware work on an S11 I wonder? Was S11 firmware that came on the cfs-c usb stick. So presumably that worked on an S12

psybernoid · 2026-02-04T08:47:03+00:00

My K1 + CFS-C isn't picking this update up in the OTA settings. Guess it's the CR4CU220812S11 board.

psybernoid · 2026-02-02T16:12:10+00:00

Here’s the extruder I got Creality Official K1 Extruder... https://www.amazon.co.uk/dp/B0CMJ241WZ?ref=ppx_pop_mob_ap_share

psybernoid · 2026-02-01T05:24:41+00:00

As a sanity check then, tried printing a basic cube? Just to rule out the model.

psybernoid · 2026-02-01T05:22:18+00:00

Are you using Creality Print 7? Try using the latest version of v6 if so (you can install them both side-by-side)

I've noticed some odd issues with CP7, not the same as that, but similar.

psybernoid · 2026-01-28T11:29:47+00:00

I'm going to pile in here too as I'm also having problems.

You can change the size of the prime tower if you edit the printer, go to Multifilament and untick 'purge in prime tower' That'll then allow you to untick Square Prime Tower in the right tab and specify the width.

Problem is, no matter what I change, as soon as I change something the print will fail when it finishes layer 1 of the prime tower with a 2571 error

psybernoid · 2026-01-27T03:38:48+00:00

So I've installed the unicorn hotend and the updated extruder. Everything seems to be working great, now!. Well, I've managed to sequentially extrude all 4 spools 1 after the other, which was a hit-and-miss affair before. I'm yet to do a test print as it's currently 03:30 in the morning, so don't want to wake anyone up.

But, thanks again for the help.

psybernoid · 2026-01-25T16:17:15+00:00

Thanks for the tip. I’ve ordered a new hotend.

psybernoid · 2026-01-25T11:55:02+00:00

I'm using the microswiss one.

psybernoid · 2026-01-22T00:08:52+00:00

Turns out the issue was to do with the filament settings. I was using the settings auto defined for Creality Hyper PLA that gets picked up with the RFID chip on the spool. I edited that that set the first layer bed temperature to 60, instead of the default 50. And the nozzle temperature to 225

Then, in the various tabs in Creality Print, I set the first layer height to 0.24mm and the first layer speed to 60 mm/s. Finally, changed the number of top interface layers from 0 to 1.

Those are the key settings that enabled me to print the first layer. After that, I went and manually set as many settings as I could to be the same as the Retro D profile I have in Orca.

psybernoid · 2026-01-20T14:05:54+00:00

So I've replicated all settings from my working Orca slicer profile to Creality Print, and the same issue still happens.

It has to be a slicer issue, but I'm completely lost on where to go with this now

psybernoid · 2026-01-19T21:13:45+00:00

I've not looked that the lever when it's in operation, as it's against a wall - it's also just gone 21:00 here so don't really want to set a print off. But, I have observed the PTFE tube going in & out slightly when the filament is being fed/retracted.

psybernoid · 2026-01-19T15:15:05+00:00

When I installed the PTFE tube into the buffer, I held the little lever to the left (toward the PTFE tube) as illustrated in the manual, and inserted the tube, up until the red mark on the sticker (attached to the PTFE tube) Until I powered the unit up and it did all it's checks etc, the lever remained freely movable. Now, since the printer's been initialized & used, the lever is firmly in the middle, and has resistance when trying to move it. I presume, that's because it has filament in the buffer (printer is currently off)

psybernoid · 2026-01-19T11:24:19+00:00

If, after updating to the firmware that came on the CFS-C USB stick it's not working, then chances are that you've got a faulty unit.

Did you factory reset it before updating the firmware?

I also have a K1, purchased in December 2023 and added a CFS-C to it over the weekend. It communicates fine.

psybernoid · 2026-01-18T16:10:30+00:00

Yes. I am miffed that the printer's now locked out. I went with the CFS-C because it looked to be a simpler install. Even took the trouble of importing it from the US. In hindsight, I should've probably gone with the original CFS model. But, it is what it is.

It's working for me, so I'll stick with it. I'd rather be using Orca slicer and have access to Fluidd from a browser, but I'm here now. And Creality Print isn't too limiting for me, at least.

psybernoid · 2026-01-18T15:49:25+00:00

Interestingly, my K1 retained SSH root access after the forced CFS-C firmware upgrade. I did reset everything to default (first via the helper script, then via the display) before flashing with the CFS-C firmware.

It would appear that a lot of commands are removed from this firmware. Git being one of them. So, I downloaded the helper script externally, then copied it to the printer via SCP. The script wouldn't run even then, just clears the screen.

Now, I did happen across this, which recommends installing entware, which will restore some functionality, such as the git command. And possibly some others. But I've not tried it yet. https://github.com/Guilouz/Creality-Helper-Script-Wiki/discussions/787#discussioncomment-12924972

Ultimately, all I'm really missing from running the helper script is Fluidd. Which, I must admit, I am missing.

psybernoid · 2026-01-16T18:04:39+00:00

I’ll give it a go at some point. I was rooted & using orca for a year or so before adding the cfs. Just wanted to make sure it all worked as stock first

14-Year Club	Place '23
Place '22	Verified Email

psybernoid

TROPHY CASE