Stuck on Please wait, retrieving current mesh. about octoprint-bedlevelvisualizer HOT 7 CLOSED

Try making @bedlevelvisualizer all caps.

from octoprint-bedlevelvisualizer.

I think its lowercase because after adding it I checked the option to save mesh. Because it is all uppercase in the gcode commands window. By unchecking the save mesh option it shows up as all capital letters in the terminal output without making any other changes and it still gets stuck on Please wait, retrieving current mesh.

from octoprint-bedlevelvisualizer.

I'm assuming that the new test results should be stored in config.yaml since thats where I see the last successful plot points that get graphed. If thats the case then it looks like its just not saving the new test data to config.yaml like it should.

from octoprint-bedlevelvisualizer.

The results should only be stored in config.yaml if the option is checked to save mesh. Not sure why the command is getting lowercased when it's being sent to the machine, but I think that is the issue.

from octoprint-bedlevelvisualizer.

It only gets lowercased when the save mesh option is not checked. but the issue of being stuck is present weather it is upper case or not. and weather save mesh is checked or not. I have uninstalled, rebooted, then reinstalled with no change.

from octoprint-bedlevelvisualizer.

This is very similar to another user's issue where it would only be an issue after first powering on his printer that any command sent after a G28 would show as unknown. The problem I'm seeing in the terminal output is that the commands are being sent, but the plugin is receiving an ok prior to the mesh data.

The way the plugin works is it detects sending the command @BEDLEVELVISUALIZER to the printer and then starts watching the commands coming back (Recv: lines). It will collect the lines that match a specific pattern which I can tell yours will work fine. And continues to do that until it receives an ok command back from the printer.

In the terminal output you are showing I'm seeing M105 commands, which means you probably don't have auto temperature reporting and should take out the M155 commands from the script. Try the following in your gcode script after power cycling your printer and pi and let me know if the results are any different.

G28
@BEDLEVELVISUALIZER
G29 T

from octoprint-bedlevelvisualizer.

That did the trick. Thank you!

from octoprint-bedlevelvisualizer.