i have an issue with G29 and bed visualizer, its missing a section of the bed for some reason....this started since I switch to 0.9 steppers and had to tweak the steps per MM settings and stuff....but not sure whats deal here
I'm the author of that plugin. Sounds like when you redid your firmware you may have tweaked something out of whack. The plugin only reads what is reported by the firmware, so if it's not reporting right the plugin will not be able to generate the surface correctly. What are the returned results of running G29 T?
1 Like
That is odd. Again, it's only graphing the results of the firmware report. What does the terminal command G29 T return.
sure here it is....weird thing is if I set steps MM (M92) for X and Y to 300 instead of 312 it works ok, but then the print is not calibrated properly (too short X and Y dimensions).....but if its 300 all is well....
Recv: Bilinear Leveling Grid:
Recv: 0 1 2
Recv: 0 +0.121 +0.039 +0.043
Recv: 1 -0.086 +0.158 +0.021
Recv: 2 -0.065 +0.207 +0.221
Recv:
Recv: Subdivided with CATMULL ROM Leveling Grid:
Recv: 0 1 2 3 4 5 6
Recv: 0 +0.12067 +0.09042 +0.06017 +0.03933 +0.03417 +0.03842 +0.04267
Recv: 1 +0.04333 +0.05947 +0.07560 +0.08146 +0.07018 +0.04864 +0.02709
Recv: 2 -0.03400 +0.02851 +0.09103 +0.12358 +0.10620 +0.05885 +0.01151
Recv: 3 -0.08600 +0.00946 +0.10491 +0.15800 +0.14047 +0.08057 +0.02067
Recv: 4 -0.09578 +0.01023 +0.11623 +0.17958 +0.17184 +0.12145 +0.07106
Recv: 5 -0.08022 +0.02289 +0.12600 +0.19346 +0.20148 +0.17384 +0.14620
Recv: 6 -0.06467 +0.03556 +0.13578 +0.20733 +0.23111 +0.22622 +0.22133
So this is the report with firmware set at 300? What is the report when set at 312?
this was at 312...i can post the 300 in a bit
actually you know what, is never making it to the UI...duh!!! I just realized the date on it is from 2 days ago!!! lol...am so dumb...so its not updating the chart at all since 2 days ago, but that G29T output I posted before is from today
So if you're settings are still correct in the gcode settings of the plugin and still include the @BEDLEVELVISUALIZER flag it should be working fine. Otherwise, check the plugin_tplinksmartplug_debug.log and octoprint.log, as well as the browser's console.