mesh bed error detection
As I mentioned in some posts before, I´m trying to get a mesh bed error detection running. Is there something like gcode for that? I cant find anything like this using the search engine, but I cant imagine, that no one was having the same problem?
When Mesh Bed Compensation is running, and something (whyever) is going wrong (inconsestent Z probe readings, z probe not triggered, z probe already triggered, etc.) I want a script that can be added to my bed.g, where I can ask for an error like this. The problem is, after the error the printer is going to print, with the nozzle at lower or higher heights than needed...
Looking for your answers
I´m trying to get a mesh bed error detection running.
With conditionals and some variables at hand, it’s no problem to write a bit of code that checks for inconsistencies. Simply wait for RRF 3.x which will give you all that.
However, I don’t really like this approach. I prefer to use a mechanical end stop to set Z at a known hight above the bed, which makes sure that the Z probe is not triggered at this stage. And, speaking of Z probes: in my opinion, the BLTouch is too fragile, I use a more robust design, so that I can be sure it works. Finally, I have carefully chosen the values for M558, there are no misreadings at all. If anything should be wrong with my height map, It is safe to say that any deviations are physically present on my bed’s surface.
@infiniteloop Hey, thanks for your answer. So you mean 3.1? I´m using 3.01 at the moment.
Why you think I´m using a BlTouch? I´m using Pinda´s, since BlTouch got me very bad results, at much lower levelling speed.
So you mean 3.1?
No, I can’t predict the future. Variables have been announced, now we wait for their arrival.
Why you think I´m using a BlTouch?
I didn’t imply that, I just mentioned BLTouch as an example of a probe with an impressive amount of mentions in this forum.
@infiniteloop So you hope that error messages are going to save in variables?
So you hope that error messages are going to save in variables?
No. You need variables for a script which monitors uncommon behaviour of your probe, especially in case of inconsistent readings. But don’t expect the firmware to deliver errors in all the circumstances you’ve mentioned in your initial post. Instead, you might try to avoid some of them completely: a „Z probe already triggered“ event should not happen if your config and homez files are properly designed.
AndreS last edited by