Mesh bed compensation results
-
The other thread on mesh bed compensation reminded me of a question. Would it be possible to add that every probe point can be moused over to get its z height reading in the mesh map?
It would be much quicker and more accurate dialing everything in. just knowing the readings of one side makes it slower and more difficult due to bed warpage.
-
This is already implemented. Perhaps you are using an older version of DWC.
-
Does it need to be enabled somewhere? as you can see by both the screenshots from myself and the other person in the mesh bed leveling thread they only show on the front row.
I have everything updated to the latest as of a week ago.
-
Chrome is the browser, I do not know if that makes a difference.
-
Please confirm which version of Duet Web Control you are using. It's reported in the General tab of the Settings page.
-
1.15b
-
Please confirm which version of Duet Web Control you are using. It's reported in the General tab of the Settings page.
1.15b
-
1.15b generally shows all the points as dots that can be moused over, however in 1.16 chrishmm fixed a bug that sometimes caused only a few of the points to be shown.
-
Is there a 1.16 DWC binary that can be downloaded that is compatible with 1.18.1? or any hint as to what needs to be done to fix this bug.
I have tried multiple browsers with all the same result.
-
I figured this out, if anyone else is having an issue with the dots not showing up then your mesh bed gcode is not correct even though it completes and seems normal. For me it was as simple as changing the Mesh bed starting points to match the offsets configured for the probe instead of X0:180 Y0:180 I changed it to X0:180 Y12.5:180
-
I'm glad you figured it out. My guess is that your bed.g file had a row of zeros at the start because y=0 was not accessible to the probe, and that row of zeros was confusing DWC.
Christian hasn't built a .bin version of DWC 1.16 because that release is targeted ad the forthcoming 1.19 firmware release.
