Depends on what is reported by firmware.
OK its brand new system. will check.
1 Like
@jneilliii
Hi there,
I'm trying to get the bed level visualizer to work but it doesnt seem to store/save and profiles for some reason. the g-code in the settings for the plugin are:
G28
@BEDLEVELVISUALIZER
G29 T
I don't know if it is a configuration problem but even with a 300 second timeout it will still lead to the error saying timeout or config problem.
This is the terminal output after running the BED_MESH_CALIBRATE or G29 T line:
Send: G29 T
Recv: // probe at 57.000,13.000 is z=3.237500
Recv: // probe at 178.500,13.000 is z=3.112500
Recv: // probe at 300.000,13.000 is z=3.245000
Recv: // probe at 300.000,153.000 is z=3.135000
Recv: // probe at 178.500,153.000 is z=2.995000
Recv: // probe at 57.000,153.000 is z=3.080000
Recv: // probe at 57.000,293.000 is z=3.160000
Recv: // probe at 178.500,293.000 is z=3.180000
Recv: // probe at 300.000,293.000 is z=3.415000
Recv: // Mesh Bed Leveling Complete
Recv: // Bed Mesh state has been saved to profile [default]
Recv: // for the current session. The SAVE_CONFIG command will
Recv: // update the printer config file and restart the printer.
Recv: // Mesh Leveling Probed Z positions:
Recv: // 0.242500 0.117500 0.250000
Recv: // 0.085000 0.000000 0.140000
Recv: // 0.165000 0.185000 0.420000
Recv: Mesh X,Y: 7,7
Recv: Search Height: 7
Recv: Mesh Average: 0.12
Recv: Mesh Range: min=0.0000 max=0.4200
Recv: Interpolation Algorithm: lagrange
Recv: Measured points:
Recv: 0.165000 0.147778 0.154444 0.185000 0.239444 0.317778 0.420000
Recv: 0.111944 0.080556 0.073148 0.089722 0.130278 0.194815 0.283333
Recv: 0.085278 0.041852 0.022778 0.028056 0.057685 0.111667 0.190000
Recv: 0.085000 0.031667 0.003333 0.000000 0.021667 0.068333 0.140000
Recv: 0.111111 0.050000 0.014815 0.005556 0.022222 0.064815 0.133333
Recv: 0.163611 0.096852 0.057222 0.044722 0.059352 0.101111 0.170000
Recv: 0.242500 0.172222 0.130556 0.117500 0.133056 0.177222 0.250000
Edit: Running Klipper BTW
Try this...
1 Like
Just for the record literally found the thread where you posted that, after I had posted haha.
It's still not working, this is the output:
Send: BED_MESH_OUTPUT
Recv: // Mesh Leveling Probed Z positions:
Recv: // 0.245000 0.112500 0.242500
Recv: // 0.087500 -0.005000 0.127500
Recv: // 0.160000 0.177500 0.412500
Recv: Mesh X,Y: 7,7
Recv: Search Height: 7
Recv: Mesh Average: 0.11
Recv: Mesh Range: min=-0.0050 max=0.4125
Recv: Interpolation Algorithm: lagrange
Recv: Measured points:
Recv: 0.160000 0.141667 0.147500 0.177500 0.231667 0.310000 0.412500
Recv: 0.110278 0.077222 0.068241 0.083333 0.122500 0.185741 0.273056
Recv: 0.086111 0.040556 0.019352 0.022500 0.050000 0.101852 0.178056
Recv: 0.087500 0.031667 0.000833 -0.005000 0.014167 0.058333 0.127500
Recv: 0.114444 0.050556 0.012685 0.000833 0.015000 0.055185 0.121389
Recv: 0.166944 0.097222 0.054907 0.040000 0.052500 0.092407 0.159722
Recv: 0.245000 0.171667 0.127500 0.112500 0.126667 0.170000 0.242500
Recv:
Recv: ok
For reference, the Gcode is now:
@BEDLEVELVISUALIZER
BED_MESH_OUTPUT
and there is a mesh profile made it just isn't showing up in the stored data for the visualizer.
Also this is my config:
[bed_mesh]
speed: 150
horizontal_move_z: 7
mesh_min: 57, 20
mesh_max: 300, 300
probe_count: 3,3
fade_start: 1.0
#fade_end: 0.0
#fade_target:
#split_delta_z: .025
mesh_pps: 2,2
#algorithm: lagrange
#bicubic_tension: .2
#relative_reference_index: 4
[gcode_macro G29]
gcode:
BED_MESH_CALIBRATE
[safe_z_home]
home_xy_position: 191,157
speed: 150
z_hop: 15.0
z_hop_speed: 10
Edit: Rebooted the Pi and restarted Octoprint. It works!!!! I've been at this for hours and I want to die 
Is it graphing it, just not storing it? Did you enable the option to Save Mesh?
1 Like
Updated to latest version and now its broken. Sad plug-in
Several people have reported that on the repo issue tracker here, but either a change in timeout values, or jsut restarting the pi resolved the issue for them. See additional details here.
Thanks everyone! after many tries finally below worked for my BQ Hephestos 2 with original Marlin 2.0:
M155 S30
@BEDLEVELVISUALIZER
G29 T
M155 S3
Anyway I found another plugin to get the bed mesh:
https://github.com/PrusaOwners/OctoPrint-PrusaMeshMap
Looking really good! That's way more level than mine
Ok, have this set up on my Prusa Mk3S with the following:
G80
@BEDLEVELVISUALIZER
G81
What do I need to add to the GCODE for a Creality CR-10 Max? I understand from this thread that the G80 is peculiar to Prusa?
Check the wiki here for examples. I would make the assumption that it's going to be the Marlin one.
1 Like
Ah perfect, working now! Missed this documentation
hey all, I had my octopi working for a little and found something on the visualizer. I installed it on my pi but it continues to load and say "please wait,retrieving current mesh" it stays on here until it times out. any help is much appreciated! im printing on a tevo tornado
Would be a little helpful to get some details, ie what is your firmware and version you are running on your Tornado, if it supports auto bed leveling and mesh reporting, what you have configured for the gcode script, etc. You can't really just ask to help you fix it without knowing what you have done so far and your personal printer's environment.
Sorry, little backstory: I set up an octopi about a year ago on my RPI 2 with a WiFi dongle and had all of this and more working on it. I’m using a BL touch on my tornado with the marlin firmware(I can’t remember what version exactly I’ll check and get back to you) I recently upgraded to a RPI 3b and a new micro SD claiming faster speeds and decided to get the newest version of Octopi on it. So in short I’ve had the bed visualizer working on this printer but with a different PI. My thinking is that this could be an issue with my settings my g code script is “g28 g29T” all my other settings are the stock ones.
Thanks for the help!
UPDATE: so i woke up this morning and deciding to connect the octopi to my 2.4mhz wifi network rather than my 5mhz network ran the bed visualizer and it worked... dont know what caused this but its working now!
I have the same problem as "Patrick_Friedl", I have a geeetech A30T.
I have nothing displayed, just "Please wait, retrieving current mesh."
Send: G28
Recv: Servo 0: self-checking...
Recv: Servo 0: self-checking is completed
Recv: we last said to move to Z: 15.00
Recv: Hit endstop Z: -1.41
Recv: we last said to move to Z: 15.00
Recv: Hit endstop Z: -1.36
Recv: Llit x: 160.000000 y: 160.000000 z: -1.357500
Recv: ok
Send: M155 S30
Recv: ok
Send: G29 T
Recv: position before G29 x: 198.199997 y: 160.000000 z: 1.750000
Recv: raise extruder Z0: 15.000000
Recv: we last said to move to Z: 15.00
Recv: Hit endstop Z: 1.64
Recv: we last said to move to Z: 15.00
Recv: Hit endstop Z: 1.59
Recv: Llit x: 60.000000 y: 60.000000 z: 1.590000
Recv: raise extruder Z1: 11.590000
Recv: we last said to move to Z: 11.59
Recv: Hit endstop Z: 1.77
Recv: we last said to move to Z: 11.59
Recv: Hit endstop Z: 1.70
Recv: Llit x: 165.000000 y: 60.000000 z: 1.697500
Recv: raise extruder Z2: 11.697500
Recv: we last said to move to Z: 11.70
Recv: Hit endstop Z: 1.68
Recv: we last said to move to Z: 11.70
Recv: Hit endstop Z: 1.68
Recv: Llit x: 270.000000 y: 60.000000 z: 1.677500
Recv: raise extruder Z3: 11.677500
Recv: we last said to move to Z: 11.68
Recv: Hit endstop Z: 1.71
Recv: we last said to move to Z: 11.68
Recv: Hit endstop Z: 1.68
Recv: Llit x: 270.000000 y: 171.000000 z: 1.680000
Recv: raise extruder Z4: 11.680000
Recv: we last said to move to Z: 11.68
Recv: Hit endstop Z: 1.71
Recv: we last said to move to Z: 11.68
Recv: Hit endstop Z: 1.79
Recv: Llit x: 165.000000 y: 171.000000 z: 1.790000
Recv: raise extruder Z5: 11.790000
Recv: we last said to move to Z: 11.79
Recv: Hit endstop Z: 1.71
Recv: we last said to move to Z: 11.79
Recv: Hit endstop Z: 1.65
Recv: Llit x: 60.000000 y: 171.000000 z: 1.650000
Recv: raise extruder Z6: 11.650000
Recv: we last said to move to Z: 11.65
Recv: Hit endstop Z: 1.67
Recv: we last said to move to Z: 11.65
Recv: Hit endstop Z: 1.59
Recv: Llit x: 60.000000 y: 282.000000 z: 1.590000
Recv: raise extruder Z7: 11.590000
Recv: we last said to move to Z: 11.59
Recv: Hit endstop Z: 1.77
Recv: we last said to move to Z: 11.59
Recv: Hit endstop Z: 1.67
Recv: we last said to move to Z: 1.66
Recv: Hit endstop Z: 1.77
Recv: we last said to move to Z: 1.77
Recv: Hit endstop Z: 1.78
Recv: Llit x: 165.000000 y: 282.000000 z: 1.775000
Recv: raise extruder Z8: 11.775000
Recv: we last said to move to Z: 11.77
Recv: Hit endstop Z: 1.61
Recv: we last said to move to Z: 11.77
Recv: Hit endstop Z: 1.73
Recv: we last said to move to Z: 1.72
Recv: Hit endstop Z: 1.72
Recv: Llit x: 270.000000 y: 282.000000 z: 1.712500
Recv: Eqn coefficients: a: 0.000381 b: 0.000169 d: 1.592980
Recv: planeNormal x: -0.000381 y: -0.000169 z: 1.000000
Recv: ok
Send: M155 S3
Recv: ok
This is not a familiar output that my plugin can interpret. Do you know what the firmware is and what its options are for reporting on the interpreted mesh?