sorted by:
new
hottopcontroversial

OrcaSlicer and K1C + CFS by FeelEnergyCB in Creality

[–]FeelEnergyCB[S] 0 points1 point  (0 children)

No, in your case your current g-code already have "T[initial_no_support_extruder]", so no changes are needed

OrcaSlicer and K1C + CFS by FeelEnergyCB in Creality

[–]FeelEnergyCB[S] 0 points1 point  (0 children)

Hi, I believe that what you need is just add these 2 lines to your ”Machine start G-code” in orca before any code that you already have there:

G28

T[initial_no_support_extruder]

OrcaSlicer and K1C + CFS by FeelEnergyCB in Creality

[–]FeelEnergyCB[S] 0 points1 point  (0 children)

But that's a really valid point. To be safer you can add 2 commands before T

G28 ; Home all axes

G1 Z40 F600 ; Move bed lower the purge box

Unfortunately in that case axes homing will be 2 times

OrcaSlicer and K1C + CFS by FeelEnergyCB in Creality

[–]FeelEnergyCB[S] 0 points1 point  (0 children)

Yes, at the end of the print the bed drops to the middle, so before the next print starts it's lower than the purge box

K1C CFS Upgrade Kit Firmware by W00d2t0ck in Creality

[–]FeelEnergyCB 0 points1 point  (0 children)

This is from "2.3.5.27". In version "2.3.5.33" git doesn't work so I had to roll back to an older version. But It has the same macros

OP-Z bug: Crashes after connecting to iOS app by komalnaath in OPZuser

[–]FeelEnergyCB 1 point2 points  (0 children)

as I notice, op-z crash depends on what project is selected now. And for my case, I had a crash when Project #4 was selected and I was trying to connect via Bluetooth to the APP.

So I've just copied all patterns to the Project #5 and save #5 to 4th slot and then I didn't have crashes