How to suppress output during probing?

General Discussion
1

Basic Information:

Printer Model: Monoprice Delta Pro
MCU / Printerboard: Orange Pi LTS / Lerdge X

Describe your issue:

I am still new to Klipper.
I wrote a set of macros and a gcode file to probe the bed to create a 15 x 15 mesh using an alternative method that works better for delta printers. I output the mesh points to the console so that they can be copied and pasted into the printer.cfg. I use filters to suppress the undesired outputs from the probing. It looks right on the console. However, the console filters (Fluidd), only filters the display. The console buffer is still filled with all the extraneous probe result reports. This causes me two problems. The biggest one is that all the extra data filles up the amount of space in the console and it throws away half of the data. The second one is that a Copy and Paste of the console, copies ALL the data, not just the visible data.

My current workaround is a painful and time-consuming amount of screenshots in realtime and image to text conversion and text editing to put it all back together again. I need a better solution.

I am not sure where to look to find a solution. Is it in Klipper to make it suppress the probing output? Is it in the Fluidd console? Or perhaps switching to Mainsail can get double the console field size?
Or is there some other way to send the output to a file to bypass this problem?

I am open to all suggestions, but I am not a Python programmer (or I would have rewritten the built-in probe command to include my algorithms).

2

Have you compared to the output in the klippy.log? This is “unfiltered”, i.e. as Klipper sees it and may be easier to process

3

Thanks for the suggestion. I did another probe “print” and checked the klippy.log. Thousands of lines too long even for my 4K monitor! Anyway, I could not find anything that looked related to my probing data. Other than a copy of the printer.cfg at the top and a few commands sprinkled around, it mostly looked like it was just logging that the printer was still running and its status.

4

I have come up with a reasonable solution. The console buffer can accept 12 out of the 15 lines of probes. I will make two probe files. Each file will probe half the bed. I will copy paste each half into a text file for post processing and then back into the printer.cfg file.

The second issue about copy/paste of the console display was not entirely correct. While the probing is going on, the copy/paste picked up the unfiltered text. However, once the printer was idle, the copy/paste worked as expected. WYSIWYG.