I enabled the "Use Relative Z Offsets" which I think is what you said, though the setting is named differently and managed to do two successful back to back mesh updates. I Googled and found previous comments of yours helping others and def want to add that the Octoprint restart is important, which I wouldn't have known without your comments helping others. I am gonna shut this off for now and mess with it more later, but I am feeling pretty confident it should be fine. Thank you
Hello. I have encountered an issue. I have recently had a bltouch sensor die on me, so i made a servo probe for bed levelling. Everything works just fine, except one thing. For some reason when I add the "@BEDLEVELVISUALIZER" to the Gcode Commands for Mesh Update Process, my servo arm will deploy, then stow, and then execute G28 and G29. This is bad, as my head will crash. When i remove the command, the G28 and G29 execute properly. I cnan recreate these results through the terminal as well by executing "@BEDLEVELVISUALIZER" then G28. My arm will deploy then stow and try and auto home. Just wondering if anyone else has encountered this issue and has any advice on it. Thank you in advance.
Your firmware shouldn't react that way to the @ command. But that @ command should also not be before G28, it should be after G28 and before G29.
Yeah, I had an issue with the firmware, and stored eeprom settings on my sd card. The problem i was experiencing here is all fixed now. Now, there is something strange in the firmware itself. For some reason, M190 S60 command makes my printer want to change filament, but thats not because of this octoprint plugin, bed level visualizer. kinda weird, just use G4 to wait instead of M190.
you sure you didn't transpose those commands? M160 M600 is filament change I think.
No, i didn't transpose them i don't think. Manually entering the M190 or M600 command seems to initiate a filament change. It's weird.
I got it sorted. Silly me had Low instead of HIGH for my filament runout sensor. Typical of when your modifying firmware at 3am.
1 Like
Hello.
I just want to ask why Bed Visualizer worked me before on Python 2.7, but now when I updated Python to 3.1 I can not install this Plugin anymore. All other Plugins work well, just Bed Visualizer not.
Why? What is the solution?
Thank you for support
Could you please share some logs?
There is a known issues section on the readme specific to updating the environment to python 3. You probably just need to run that command that's listed for the fix...
I can not upload logs, because is my octoprint logs 4.552KB big.
This message I get when I install the Bed Visualizer:
You can zip them...
How do you try to install the plugin?
Have you done this:
- Install will fail silently in Python 3 due to missing system dependencies. You may have to SSH to your pi and run the command
sudo apt install libatlas3-baseto get the plugin to load.
as @jneilliii recommended?
No i did't run this command yet. I will try this tomorow. Thank you
Hello,
I run this command and is now ok. Working 
Thank you for your help
I have problems with the plugin and a Creality Ender 3Pro with the original firmware version of Creality (1.3.1 2020-04-25 for BLTouch).
When I send the commands G28 and G29 T, I only get this output on the console:
"Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly"
Can i change that?
Yes, you can make the command whatever is necessary to get a mesh report out of the firmware. Some people have reported taking the T off of the G29 command helps.