Closed Beagon closed 4 months ago
I have noticed this issue as well, but it seems more general than this case. Any probe command that was not part of the bed mesh procedure will have this effect, I often use the BED_LEVEL_SCREWS_TUNE macro before starting a print and it triggers the same issue.
Should be fixed in dev
Hi, I had something happen and did an emergency stop during the creation of a KAMP mesh and had the following happen the next time I tried to print:
Printer: Neptune 4 Plus
Steps to reproduce:
This seems to only be graphical.