Kossel mesh bed visualizer

I'm trying to get a mesh bed visualizer for my kossel linear plus but I'm not having much luck.
These are the g codes I'm using

G28
M155 S30
@BEDLEVELVISUALIZER
G29 T
M155 S3

It pulls up the graph but doesn't display the bed inside of it.
Any help would be greatly appreciated thank you.

I wonder what @jneilliii would say at a time like this...?

Would have to see the results of the G29 T command from the terminal tab, and screenshots of the stored mesh data in settings.

1 Like

Hi, may I post the data as I also have an Anycubic Kossel linear plus and cannot make the plugin work

Send: G29 T
Recv: G29 Auto Bed Leveling
Recv: X:0.00 Y:0.00 Z:208.27 E:0.00 Count X: 35488 Y:35488 Z:35488
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: dfsaf: 208.272G29 new Z_offset:-15.90
Recv: Bilinear Leveling Grid:
Recv: 0 1 2 3 4 5 6 7 8
Recv: 0 +193.80 +191.74 +192.13 +192.10 +192.08 +192.06 +191.98 +192.88 -442.29
Recv: 1 +192.74 +191.70 +191.78 +191.84 +191.86 +191.89 +191.92 +191.95 -231.21
Recv: 2 +191.68 +191.66 +191.66 +191.62 +191.18 +191.16 +191.09 +191.02 -20.13
Recv: 3 +190.63 +190.66 +190.73 +190.77 +190.81 +190.90 +190.92 +190.94 +190.97
Recv: 4 +190.64 +190.61 +190.59 +190.53 +190.33 +190.31 +190.26 +190.21 +190.18
Recv: 5 +189.83 +189.85 +189.88 +189.92 +189.94 +190.02 +190.05 +190.08 +190.12
Recv: 6 +189.73 +189.69 +189.65 +189.59 +189.40 +189.38 +189.34 +189.32 -21.01
Recv: 7 +189.63 +188.97 +189.00 +189.02 +189.04 +189.11 +189.15 +189.19 -232.14
Recv: 8 +189.53 +188.25 +188.92 +188.86 +188.48 +188.47 +188.44 -21.72 -443.26
Recv:
Recv: X:50.00 Y:89.00 Z:15.90 E:0.00 Count X: 27990 Y:33249 Z:37371
Recv: echo:Settings Stored (669 bytes)
Recv: echo:Hardcoded Default Settings Loaded
Recv: echo:V29 stored settings retrieved (669 bytes)
Recv: echo:Steps per unit:
Recv: echo: M92 X80.00 Y80.00 Z80.00 E96.00
Recv: echo:Maximum feedrates (mm/s):
Recv: echo: M203 X200.00 Y200.00 Z200.00 E200.00
Recv: echo:Maximum Acceleration (mm/s2):
Recv: echo: M201 X3000 Y3000 Z3000 E3000
Recv: echo:Accelerations: P=printing, R=retract and T=travel
Recv: echo: M204 P3000.00 R3000.00 T1500.00
Recv: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv: echo: M205 S0.00 T0.00 B20000 X5.00 Y5.00 Z5.00 E5.00
Recv: echo:Home offset (mm)
Recv: echo: M206 X0.00 Y0.00 Z0.00
Recv: Auto Bed Leveling:
Recv: echo: M420 S0
Recv: echo:Endstop adjustment (mm):
Recv: echo: M666 X0.00 Y0.00 Z0.00
Recv: echo:Delta settings: L=diagonal_rod, R=radius, S=segments_per_second, ABC=diagonal_rod_trim_tower_[123]
Recv: echo: M665 L271.50 R135.40 S80.00 A0.00 B0.00 C0.00
Recv: echo:Material heatup parameters:
Recv: echo: M145 S0 H180 B70 F0
Recv: M145 S1 H240 B110 F0
Recv: echo:PID settings:
Recv: echo: M301 P22.20 I1.08 D114.00
Recv: echo:Filament settings: Disabled
Recv: echo: M200 D3.00
Recv: echo: M200 D0
Recv: echo:Z-Probe Offset (mm):
Recv: echo: M851 Z-15.90
Recv: ok

All of that is what G29 T obtains in stored data only this

I don't see any reason why this would be happening. What's your general settings look like? Any errors in your logs?

Hi. I have upgraded to Marlin 2. It seems to have much more logic data now, but it doesn't work due to my graphics drivers and cannot execute webgl. So i think it is not a plug-in issue anymore, but thank you very much for your prompt reply

Yeah, webgl compatible video drivers are a must for the plotly framework to function.

Yep, it works from my Android phone. Yay!!!