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.
I am using Creality Ender 3Pro with the original firmware version of Creality (1.4.1 2020-04-25 for BLTouch)
I update mesh using .
M140 S60 ; starting by heating the bed for nominal mesh accuracy
M117 Homing all axes ; send message to printer display
G28 ; home all axes
M117 Heating the bed ; send message to printer display
M190 S60 ; waiting until the bed is fully warmed up
M300 S1000 P500 ; chirp to indicate bed mesh levels is initializing
M117 Creating the bed mesh levels ; send message to printer display
M155 S30 ; reduce temperature reporting rate to reduce output pollution
@BEDLEVELVISUALIZER ; tell the plugin to watch for reported mesh
G29 T ; run bilinear probing
M155 S3 ; reset temperature reporting
M140 S0 ; cooling down the bed
M300 S440 P200 ; make calibration completed tones
M300 S660 P250
M300 S880 P300
M117 Bed mesh levels completed ; send message to printer display
I just keep getting the same date
Using saved mesh data from 5/1/2021, 10:22:15 PM.
It does not show the current mesh...
How Can I get it to show the updated date and info?
enable debug logging, restart octoprint, and provide the log plugin_bedlevelvisualizer_debug.log as an attachment here. Also check octoprint.log for errors.