Comments (9)
In addition to what @evie-lau said, I had to add G29
before G29 T
for the procedure to actually happen (before it would just print the saved values).
M104 S170 ; set extruder temp for bed leveling
M140 S60 ; set bed temp
M109 R170 ; wait for bed leveling temp
M190 S60 ; wait for bed temp
G28 ; home all without mesh bed level
M155 S30
G29
@BEDLEVELVISUALIZER ; instruct plugin to start recording responses from printer.
G29 T ; mesh bed leveling
M155 S3
M104 S0 ; cool down head
M140 S0 ; cooling down the bed
from octoprint-bedlevelvisualizer.
What shows in the terminal tab as the process starts? Usually this means that your firmware just doesn't report the mesh data back followed by an OK with the G29 command.
from octoprint-bedlevelvisualizer.
I am having the same issue too on my Prusa Mini. I am running Firmware version 5.1.2 on my printer. My Octoprint is 1.9.3. Here is the log of what happens when I run the bed visualizer:
Recv: T:138.29/170.00 B:40.02/60.00 A:34.71/0.00 @:103 B@:127 W:?
Recv: T:140.38/170.00 B:40.40/60.00 A:34.71/0.00 @:103 B@:127
Recv: T:140.77/170.00 B:40.33/60.00 A:34.75/0.00 @:103 B@:127 W:?
Recv: echo:busy: processing
Recv: T:170.07/170.00 B:58.93/60.00 A:35.24/0.00 @:30 B@:58
Recv: T:170.05/170.00 B:58.93/60.00 A:35.15/0.00 @:30 B@:59 W:?
Recv: T:170.07/170.00 B:58.95/60.00 A:35.28/0.00 @:30 B@:62 W:?
Recv: echo:busy: processing
Recv: T:170.14/170.00 B:58.95/60.00 A:35.22/0.00 @:30 B@:66
Recv: T:170.21/170.00 B:58.98/60.00 A:35.20/0.00 @:29 B@:63 W:?
Recv: T:170.21/170.00 B:58.98/60.00 A:35.24/0.00 @:29 B@:67 W:?
Recv: echo:busy: processing
Recv: T:170.23/170.00 B:59.02/60.00 A:35.20/0.00 @:29 B@:66
Recv: T:170.19/170.00 B:59.04/60.00 A:35.20/0.00 @:30 B@:65 W:4
Recv: T:170.19/170.00 B:59.05/60.00 A:35.22/0.00 @:30 B@:67 W:3
Recv: echo:busy: processing
Recv: T:170.23/170.00 B:59.08/60.00 A:35.20/0.00 @:29 B@:67
Recv: T:170.12/170.00 B:59.11/60.00 A:35.24/0.00 @:30 B@:64 W:2
Recv: T:170.16/170.00 B:59.18/60.00 A:35.22/0.00 @:30 B@:60 W:1
Recv: echo:busy: processing
Recv: T:170.16/170.00 B:59.19/60.00 A:35.22/0.00 @:30 B@:61
Recv: T:170.19/170.00 B:59.21/60.00 A:35.26/0.00 @:30 B@:60 W:0
Recv: ok
Send: G28
Recv: echo:endstops hit: Z:1.99
Recv: T:170.09/170.00 B:59.35/60.00 A:35.17/0.00 @:30 B@:50
Recv: echo:busy: processing
Recv: T:170.16/170.00 B:59.52/60.00 A:35.22/0.00 @:30 B@:38
Recv: echo:endstops hit: X:147.12
Recv: echo:busy: processing
Recv: echo:endstops hit: Y:-14.72
Recv: T:170.21/170.00 B:59.62/60.00 A:35.13/0.00 @:29 B@:33
Recv: echo:endstops hit: Z:-2.63
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:-2.01
Recv: T:169.93/170.00 B:59.67/60.00 A:35.15/0.00 @:31 B@:34
Recv: X:176.40 Y:24.10 Z:2.00 E:0.00 Count X:17640 Y:2410 Z:800
Recv: ok
Send: G29
Recv: Default storage slot 0 selected.
Recv: Mesh invalidated. Probing mesh.
Recv: T:169.63/170.00 B:59.70/60.00 A:35.13/0.00 @:33 B@:36
Recv: echo:busy: processing
Recv: T:169.65/170.00 B:59.69/60.00 A:35.06/0.00 @:33 B@:42
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.60
Recv: T:169.50/170.00 B:59.70/60.00 A:35.06/0.00 @:34 B@:44
Recv: echo:endstops hit: Z:0.60
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.60
Recv: T:169.54/170.00 B:59.70/60.00 A:35.09/0.00 @:33 B@:46
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.93
Recv: echo:endstops hit: Z:0.91
Recv: T:169.61/170.00 B:59.71/60.00 A:35.07/0.00 @:33 B@:46
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.18
Recv: echo:endstops hit: Z:1.17
Recv: echo:endstops hit: Z:1.15
Recv: T:169.78/170.00 B:59.75/60.00 A:35.04/0.00 @:32 B@:44
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.35
Recv: echo:endstops hit: Z:1.33
Recv: T:169.96/170.00 B:59.75/60.00 A:35.02/0.00 @:31 B@:46
Recv: echo:endstops hit: Z:1.33
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.39
Recv: T:169.96/170.00 B:59.83/60.00 A:35.02/0.00 @:31 B@:38
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.38
Recv: echo:endstops hit: Z:1.38
Recv: T:169.93/170.00 B:59.83/60.00 A:34.96/0.00 @:31 B@:40
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.24
Recv: echo:endstops hit: Z:1.23
Recv: echo:endstops hit: Z:1.22
Recv: T:170.00/170.00 B:59.84/60.00 A:35.02/0.00 @:31 B@:40
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.01
Recv: echo:endstops hit: Z:1.01
Recv: T:170.00/170.00 B:59.86/60.00 A:34.98/0.00 @:31 B@:40
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.00
Recv: echo:endstops hit: Z:0.71
Recv: T:170.09/170.00 B:59.90/60.00 A:34.96/0.00 @:31 B@:37
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.70
Recv: echo:endstops hit: Z:0.70
Recv: T:170.25/170.00 B:59.91/60.00 A:35.00/0.00 @:29 B@:37
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.66
Recv: echo:endstops hit: Z:0.65
Recv: T:170.25/170.00 B:59.95/60.00 A:35.02/0.00 @:30 B@:34
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.98
Recv: echo:endstops hit: Z:0.97
Recv: T:170.28/170.00 B:59.93/60.00 A:35.04/0.00 @:30 B@:36
Recv: echo:endstops hit: Z:0.97
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.12
Recv: T:170.42/170.00 B:59.88/60.00 A:35.00/0.00 @:29 B@:43
Recv: echo:endstops hit: Z:1.12
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.11
Recv: T:170.51/170.00 B:59.90/60.00 A:34.90/0.00 @:28 B@:42
Recv: echo:endstops hit: Z:1.23
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.22
Recv: echo:endstops hit: Z:1.21
Recv: T:170.37/170.00 B:59.91/60.00 A:34.96/0.00 @:29 B@:41
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:1.03
Recv: echo:endstops hit: Z:1.02
Recv: T:169.93/170.00 B:59.93/60.00 A:34.98/0.00 @:32 B@:38
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.92
Recv: T:169.87/170.00 B:59.95/60.00 A:34.98/0.00 @:32 B@:37
Recv: echo:endstops hit: Z:0.92
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.91
Recv: T:169.80/170.00 B:59.95/60.00 A:34.96/0.00 @:32 B@:37
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.79
Recv: echo:endstops hit: Z:0.79
Recv: echo:endstops hit: Z:0.78
Recv: T:169.74/170.00 B:59.99/60.00 A:34.96/0.00 @:32 B@:33
Recv: echo:busy: processing
Recv: echo:endstops hit: Z:0.55
Recv: echo:endstops hit: Z:0.54
Recv: T:169.74/170.00 B:59.95/60.00 A:34.96/0.00 @:32 B@:39
Recv: echo:endstops hit: Z:0.54
Recv: echo:busy: processing
Recv: X:35.20 Y:9.80 Z:2.00 E:0.00 Count X:3520 Y:980 Z:800
Recv: Extrapolating mesh...done
Recv: Unified Bed Leveling System v1.01 active
Recv: ok
Send: M104 S0
Recv: ok
Send: M140 S0
Recv: ok
Recv: T:169.89/0.00 B:59.92/0.00 A:34.83/0.00 @:0 B@:0
Recv: T:169.87/0.00 B:59.91/0.00 A:34.79/0.00 @:0 B@:0
from octoprint-bedlevelvisualizer.
Recv: echo:busy: processing
Recv: X:35.20 Y:9.80 Z:2.00 E:0.00 Count X:3520 Y:980 Z:800
Recv: Extrapolating mesh...done
Recv: Unified Bed Leveling System v1.01 active
Recv: ok
Send: M104 S0
Recv: ok
Send: M140 S0
Recv: ok
Yeah, so no mesh data is actually returned by your firmware. Is there any chance there's a different command for G29 that will report the mesh?
from octoprint-bedlevelvisualizer.
I ran into this too with logs looking the same.
I was able to get the bed topography report by changing G29 to G29 T
as mentioned in the README
I also surrounded the G29 command with M155 S30 and M155 S3 as noted, but not sure if that made any difference.
Logs when using G29 T
:
Send: M155 S30
Recv: ok
Send: G29 T
Recv:
Recv: Bed Topography Report:
Recv:
Recv: ( -41,226) (195,226)
Recv: 0 1 2 3 4 5
Recv: 5 | -2.000 -1.446 -1.050 -0.545 -0.200 +0.140
Recv: |
Recv: 4 | -1.875 -1.400 -0.925 -0.456 -0.114 +0.229
Recv: |
Recv: 3 | -1.908 -1.354 -0.800 -0.368 -0.028 +0.312
Recv: |
Recv: 2 | -1.926 -1.388 -0.849 -0.405 +0.029 +0.462
Recv: |
Recv: 1 | -1.975 -1.490 -1.005 -0.424 [+0.009] +0.441
Recv: |
Recv: 0 | -2.131 -1.592 -1.161 -0.443 -0.011 +0.422
Recv: 0 1 2 3 4 5
Recv: ( -41, -48) (195, -48)
Recv:
Recv: ok
Send: M155 S3
from octoprint-bedlevelvisualizer.
Great, so basically the same as standard Marlin bilinear.
from octoprint-bedlevelvisualizer.
Hi guys, great, tried many ways but this actually works :)
But how are the correction values to be interpreted? Do you use the outer values? At least the in-between screws have to be averaged, right? Which option did you choose that actually works in the end?
![Bildschirmfoto 2023-12-29 um 18 19 14](https://private-user-images.githubusercontent.com/155183363/293401606-21964435-15c4-4cff-a944-778efe7cb3e4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQ3MzY1NTYsIm5iZiI6MTcwNDczNjI1NiwicGF0aCI6Ii8xNTUxODMzNjMvMjkzNDAxNjA2LTIxOTY0NDM1LTE1YzQtNGNmZi1hOTQ0LTc3OGVmZTdjYjNlNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEwOFQxNzUwNTZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03YTNmODZkNDFjYWE3MWI3NDRlZWIxZWI3YzJjY2Q1Mzk3MDM0ZWE0NGJlYzUzYTg5YjBlOGJlNmRhYjgyODZlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.9Miaor1qWzVHOyyAvFTVQEyyKMlZfQmKzdGyjXfQMzU)
from octoprint-bedlevelvisualizer.
personally I've never really liked the screw adjustment UI because of this very reason. It doesn't make sense unless the probe points are directly over the screw locations. I would try to pick the point that is close to the screw location and use that as the adjustment.
from octoprint-bedlevelvisualizer.
Related Issues (20)
- Store Recent Mesh Visuals in Settings HOT 1
- [BUG]: HOT 2
- [FR]: Better PSU Control support HOT 3
- [BUG]: Probing Failed
- [FR]: HOT 5
- [BUG]: OctoDash web page needs authentication HOT 10
- [BUG]: Mesh statistics not readable since rc7 update HOT 11
- [FR]: change the font color in the gui, red and blue are hard on the eyes HOT 1
- [BUG]: No Visualization for Lerdge Z HOT 1
- [FR]: Different colours for data labels HOT 1
- How do I edit coordinate increments in the data and corrections report tabs. HOT 7
- [BUG]: Displayed grid window is too small HOT 2
- [BUG]: Rendering Mesh display error HOT 3
- [BUG]:
- [FR]: Update mesh display through start GCODE HOT 1
- [FR]: Parse/Display Z-offset from ABL process. HOT 3
- [BUG]: HOT 4
- [FR]: Selectable bed temperature without having to rewrite the gcode strings HOT 2
- [FR]: Progress indicator
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from octoprint-bedlevelvisualizer.