Sorry, I’m trying to respond more quickly but the forum is limiting the number of posts I can make.
Hmm, I have actually run both the scripts you suggest. When I ran the one with the G28 commands it probed the bed and displayed the visualisation I posted but I thought this was from the probing it did just then rather than the “saved” calibration.
In any event, seeing that visualisation actually made me more likely to think that the prints were running without using the mesh as the visualisation almost perfectly depicted what I suspected the problem was.
Yes, I agree. I’m just using Bed Visualiser because that was the only way I knew how to get something that I knew what to expect. As I say, I’ve been trying BED_MESH_OUTPUT but have just been getting the “Bed has not been probed” message and haven’t known why.
Thank you this @Sineos. This is almost certainly the step I have been missing!
(I know this is probably obvious to you guys but I didn’t actually realise it required two steps)
As it is my printer’s on the other side of town but I’ll drive out there tomorrow and give this a go.
That’s a very interesting idea.
I’ll see if the regular mesh leveling will work first but will consider this if I still have problems.
From the screen shot I posted above I take it I have a variation of 0.2845 mm. That kind of seems like a lot, yeah? Given I typically print with a layer height of 0.2 mm for quick practical prints and 0.1 mm for aesthetic works 0.28 mm is almost 3 layers worth of variance. Is that normal?
Okay, took me a little while to get back to my printer but I think that might have fixed it.
Typing BED_MESH_PROFILE LOAD="default" before typing BED_MESH_OUTPUT does indeed output the matrix of values.
So I updated the Bed Visuliser code to be:
@BEDLEVELVISUALIZER ; instruct plugin to start recording responses from printer.
BED_MESH_PROFILE LOAD="default"
BED_MESH_OUTPUT ; report the bed leveling mesh points.
And it does indeed show the commented values saved in printer.cfg file.
(I checked this my modifying the decimal point of one of the values and sure enough Bed Visualizer showed a spike at that location)
I also added the BED_MESH_PROFILE LOAD="default" command to my start GCODE and it seems all is now working as it should:
