Hello, i am having an issue with my z offset. My offset is saved in my printer.cfg under [prtouch_v2] z_offset. The issue is that each time i start my printer the first print is fine because it uses that z offset but when i launch a second print the z-offset is way off. What i found out is that after each print there is a line in the console saying z offset = 0. Then i see the z offset on the left the negative value of my desired offset (see image) and it will stay like that for all the remaining prints. I cannot for the life of me figure this one out.
Printer : Rooted Creality K1C using Fluidd
Packages installed : KAMP and improved shapers
Slicer : Orca
It depends on how you start the print. Using the screen will override certain custom macros and settings. It’s very annoying, and different z offset settings in different places also complicate it and can have negative effects. I got it working for a bit but it eventually started resetting again. Gave up and just upgraded to this because the load cells kept giving me bad z offsets to start off with.
Okay, after some playing around, lots of resets and firmware rollbacks, I think I got it.
This all hinges on the fact you trust the bed level check it does automatically before a print via the load cell.
Essentially you need to reset to factory (but make sure to take down all changes you want to keep i.e. run current for the extruder and rotation distance).
This will keep root but wipes everything. Once done, install helper-script and install moonrake+fluidd and improved shapers. Reboot.
Go back to k1c screen and do the input shaper + bed calibration.
Machine is good to use at this point.
Now this is the important part. Do NOT run ‘tune’ or calibration in fluidd UI or the macros. I believe firmware does something funky to these once you reboot. If you need to recalibrate, via the K1C screen.
I haven’t tested this with KAMP so suggest trying what I did first for a few prints, throw in a reboot or to and see if the z-offset sticks. Add KAMP and see how that goes afterwards.
Also use Orca… Creality Print I believe sends something which may interfere with this too.