Been using for an age, updated yesterday, BOOM. Results ignored!?!?

[TheGadge]

I've used this just fine since it started out, -until yesterday!

I do an update of bed and it's completely ignored?? -The visualisation shows from ages ago when last used. That's all I can get! Any advice please, many thanks.

[dsiguero]

I'm also having this issue since the last update.

[jneilliii]

More than likely your timeout value is too low and needs to be increased. Increase the value to a number that is past the amount of time it takes for your leveling process to complete and then restart OctoPrint (very important). This has worked for several people in the thread over here.

https://github.com/jneilliii/OctoPrint-BedLevelVisualizer/issues/195

[MasterFuba]

I have the same issue on my Ender3, last update was on 29.3. and i used it excessive then. Now couple of days later Bed Visualizer seems to be in quarantine. After reinstall i see the "you must be logged in" info screen but i can't do anything there. Just wait until new update arrives? Also used commands shown in https://github.com/jneilliii/OctoPrint-BedLevelVisualizer/issues/195 but no success - seems like version is broken to Ender machines or general.

[Skiddz]

I'm in the same boat. Last ABL was 3/19 and since the last update, the mesh won't update.
I use the BLTouch plugin, heat the bed and nozzle, home everything, then use the plugin's buttons to run the probe and save.

Visualizer Gcode is M420 V then M420V1, then M501. Mesh would update in about a minute. Now it tell me I have to be logged in and nothing happens.

I uninstalled the plugin and cleaned the data, then did a power off shut down and restart. Same deal. I tried using just the visualizer to generate the mesh with G28, then G29 T and the printer does probe, but the visualizer never updates.

At this point, I can't even generate a log file because nothing happens. I let it grind all night and still no joy.

CR-10 Mini, TH3D Unified Firmware, (TH3D U1.R2.A3) BLTouch 3.1, Octoprint 1.4.0 on a 4G Raspberry Pi 4B

Using the BLTouch Plugin to generate the mesh data, what would the proper GCode be to update the visualizer?

[edit]

Updated everything on the Pi, uninstalled the 1.1.13 plugin and cleared data, rebooted the Pi, installed 1.1.11. Ran a probe with the BLTouch Plugin, saved it, verified mesh data with M420 V at the terminal, updated the mesh. Literally took 3 seconds to update.

Using this for GCode: @BEDLEVELVISUALIZER M420 V M420 L M420 S1

I guess my setup doesn't 'like' >1.1.11

[jneilliii]

I think the clear data option messes things up to be honest. If you manually remove all the settings for the plugin in config.yaml it could potentially resolve the issue.

[Skiddz]

I'm up and running on 1.1.11 right now and mesh updates are literally taking seconds. I'll look at updating once my next few jobs are printed. Thx!

[electricJP]

This issue has been closed but I don't see any evidence it is solved. I do noticed the same issue this morning after trying to update my mesh (last update was 2020/02/20). Visualizer will just fail with a timeout error, even if I see the G29 completed in terminal.

[jneilliii]

This was a duplicate issue, but your problem to me seems like you need to increase your processing timeout value to something larger. What is it set at now?

[electricJP]

It was working fine at 60s. I increased up to 120s with no luck. I can see in terminal that G29 is completing correctly. It looks like plugin does not catch process end. I use the standard commands: G28 M155 S30
@BEDLEVELVISUALIZER G29 T
M155 S3

[jneilliii]

I upped the default to 1800 for new users this was causing so much pain. Set it to 1800 and restart OctoPrint and I bet it works.

[electricJP]

Yup. it did. Thank you!