fluidd VS print_area_bed_mesh

check out Fluidd

Perfect timing to thank to the team behind project Fluidd as well. After some time of inactivity, project has recovered and releasing regular updates, giving us awesome alternative the Mainsail UI.

That’s the fluidd logo in the top left

My recommendation if your just setting up: do yourself a huge favor and do not use OctoPrint. Instead I recommend using Mainsail of Fluidd. They’re both great web interfaces designed specifically for Klipper. Very fast, lightweight and take advantage of all available Klipper functions. Octoprint is very resource hungry.

In the past I used OctoPrint, but now I moved to Mainsail, because it has a better ui and some plugins are directly build in. You can install Kiauh and use it to install Mainsail or Fluidd next to OctoPrint.

You will need a raspberry pi, or an old laptop/pc that is x64. If raspberry pi, you can use either the mailsail or fluidd install image that will configure the entire ui and set up the basics for installing klipper. I’ll link to some videos that can help you if using a pi. Otherwise if using a desktop you will need to install Debian Linux and set up a user named pi and then use a project called kiauh which will allow you to configure mainsail or fluidd.

Personally I prefer Mainsail. But Fluidd is also popular.

Good catch! I've created an issue in GitHub and, once I get consensus on an approach, I'll look at fixing this

A macro that only probes the bed area that you are printing in aka dynamic bed mesh probing! https://github.com/Turge08/print_area_bed_mesh

Well i just wanted to use this bed mesh plugin https://github.com/Turge08/print_area_bed_mesh

print_area_bed_mesh GitHUB

Unparsed config option 'origin: https://github.com/Turge08/print_area_bed_mesh.git' detected in section [update_manager print_area_bed_mesh]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Gives this a try, it wont fix your problem but auto adjust your probed area to your print area. https://github.com/Turge08/print_area_bed_mesh

If you want to get fancy with it, check out this little gem: print_area_bed_mesh

By print_size_mesh, do you mean this macro? https://github.com/Turge08/print_area_bed_mesh

My main reason to start using it was because of a macro (not this one, but it's a better one) that only generates a mesh for the area you will be printing in. It can also reuse meshes if the new mesh is the same size or smaller than the last. Of course you can just generate one mesh and run with it for awhile, but I like having as fresh a mesh as I can and this saves time.