Z_offset shenanigans on AD5M

Basic Information:

Printer Model: AD5M
MCU / Printerboard: stm32f103xe @144MHZ
printer.log (71.6 KB)

HOST/SBC: Kunos? (not sure how to find this in fluidd?)

Describe your issue:

Hey, thanks for reading :slight_smile:

I’m totally new to 3d printing, got the FF AD5M and it printed with no issues stock; I flashed klipper via Forge-X found at: GitHub - DrA1ex/ff5m: Forge-X: Flashforge Adventurer 5M (Pro) Firmware mod.

After flashing, I enabled tune_klipper, tune_config, and enabled load_z_offset (and at this point I think I set it to -0.5, don’t completely remember) and when I started a new print I noticed the nozzle was scratching the bed.

with load_z_offset enabled, no matter what I did in fluidd or what I modified in the config, I couldn’t adjust Z_offset to be anything other than -0.5.

With load_z_offset disabled, when the print begins I get a message that says Z_offset setup is being skipped (I may have also enabled this, again don’t completely remember oops).

using probe_calibrate and the paper test gets me a Z_offset of -0.228, however when I try to save this via save_config or new_save_config I get the following error:

!! SAVE_CONFIG section ā€˜probe’ option ā€˜z_offset’ conflicts with included value

and this remains constant independent of load_z_offset’s status.

Checking config elicits a lack of Z_offset in printer.cfg, but it’s defined in both printer111.cfg and printer.base.cfg. there were no other config files, and changing those definitions to -0.228 did not change the error I got on trying to save config.

I read something about creating bed mesh after probe_calibrate so I think it’s worth mentioning that I haven’t got a bed mesh loaded at the moment either.

pls lmk if more info is needed and advise on troubleshooting steps; I want to understand what’s going on and learn how and why this happened and how to prevent it, and I also want to not have my nozzle bedscratch.

the 2 solutions I see here are either:

a) dig through the config and settings until I find the issue and fix it with your help

b) reset the config and any other relevant data/systems so I can move on with my life

(I tried reflashing klipper to see if my problem would disappear but alas, it still haunts me - hence the post)

ty in advance!

It seems that the changes made by these Klipper modifications are quite significant due to the unique requirements of the AD5M. The best option might be to seek support from the aforementioned GitHub project.

1 Like

Welcome stinkystonk.

I don’t know that printer, but it looks pretty good from a price/quality point of view.

Did you see GitHub - FlashForge/AD5M_Series_Klipper?

It looks, like done by Flashforge, but very old. I fear also you have to struggle with

You also may have a look to the forks in the my github link.
Maybe you can start a working group?
You could ā€œcompareā€ these files in case of a problem with your source?