Installing ZMOD revealed a problem with my FlashForge Adventurer 5M which was either caused at the factory, during shipment (but the box is clean and shows no signs of mishandling) or my printer was a return that wasn't checked over before it was sent out again. This caused me to be unable to level the bed until I fixed it. The problem revealed itself as a "No Trigger on Probe After Full Movement" error during bed leveling.
I want to pick up where a failed print left off on my Adventurer 5M, but I'm running into the dreaded Timer Too Close (AKA "TTC") error from Klipper, which I know from errors shown on the Fluidd (web) interface instead of just having the system stop printing with no feedback like you get with the stock screen, because I am running the Forge-X mod.
My printer is a FlashForge Adventurer 5M. I got it for about $211 shipped, which is the only reason I bought this unit really. They seem to be hovering around $249 right now. In most ways I am very happy with it, but I ran into an irritating problem today.
I've been looking for a good source on 3d printer calibration, one better than the Orcaslicer page on the subject anyway, and I finally found a great video in straightforward English explaining a useful, working, proven process. Naturally, it was made by a German. Once again, if you'd rather have a video, go watch the video.
I have been 3d printing for a very short time, but I've already learned some stuff I wish I'd known earlier, and I'm going to write about it here now - both to benefit someone else who's just starting, and because I think it will be interesting to look back later and see how much I was or wasn't on the mark.
I printed mostly successfully with a goofy Z-offset for too long (not that long) but finally found the resource which would tell me how to go about fixing it. I prefer a simple written instruction, but ironically the answer was a video by Ricky Impey. If you would rather watch a video, just stop now and go watch it. If you would like the entire process explained to you in text from start to stop [by a human] instead, read on.
Subject tells the short story. Longer story, I wanted to start pipewire, pipewire-pulse, and wireplumber at KDE login. In troubleshooting I found that KDE is overwrought here. Instead of just starting the scripts named here with run-parts or similar, it creates .desktop files for them in .config/autostart. I didn't put a shebang (e.g. #!/bin/bash) at the top of the script. As it turns out, this breaks this whole facility because the .desktop files will just try to run the script as an executable and fail with an execve format error.
I've just installed Devuan Excalibur using mostly the OpenZFS instructions for Debian Trixie, as I did before except with Chimaera (which I then upgraded to Daedalus.) I had a grand old time getting it to boot and started over a couple of times, which is not a big deal because it does not take very long to get to the point where it doesn't boot. I had been using legacy booting and chose to try UEFI, which is working okay now.
I've wanted a 3D printer for a long, long time, but recently they have come down so much in price that I couldn't resist any more and picked up a FlashForge Adventurer AD5M. Out of the box it can really only handle PLA and PETG, but I've upgraded it with an enclosure kit and additional nozzle that make it capable of printing most filaments.