bed mesh running at START_PRINT has significant offset applied

I recently started having some very poor quality prints. I noticed the skirt loops on the print were very compressed down into the bed. I figured it was bad filament, maybe needed drying or something, so I stuck it in for a drying cycle. WHen it came out it was still happening and then started occuring when using the sceond toolhead. In looking at the bedmesh that is created from the START_PRINTmacro I see that there is a significant offset that appears to be applied. In order to fix I heated the bed/chamber/hotend to printing temperatures, performed a z-tilt and then a bed mesh. This appeared totally normal and looked perfect. So I kicked off another print and same thing happened. Next I disabled the bed mesh from START_PRINT, set the default mesh to use as the one I just created (in the properly heated environment) and every print has been perfect since. Just to see where things stood, I went back to letting ratos create the mesh from START_PRINT and very similar failure as before. Though instead of the offset being applied to squish into the bed it was far too high. Just to be sure I once again preheated the entire printer and created a bed mesh. It looked perfect, but in comparing it to the one ratos just created during START_PRINT, (it's named ratos so it's easy to find) I can see clearly this offset being applied. Attaching screenshots of my good mesh and this bad mesh. For now I'm just going to go back to a static, default bed mesh and disable the one that gets created in START_PRINT but ideally I would not have to do this. Anyone have any ideas on how to address this? Im not sure what could be going on and what could be causing this.
No description
No description
3 Replies
rms497
rms497OP2mo ago
In investigating the issue, I have found that I am able to get this problem to go away and come back with a single setting, variable_beacon_contact_start_print_true_zero. When it's True, the issue will be there and this offset appears wherever the bed mesh scan occurs, but when it's False it works correctly, as expected. Anyone have insight into why that may be happening with this setting? For the record that is the only beacon specific variable I am setting right now. I am not changing the default values for anything beacon specific in my printer.cfg.
alex3thy
alex3thy2w ago
Hello, did you manage to fully work it out? One question, what probe are you using?
s1krrvoodoomagic
I'm going to follow this, I have been trying to get prints to stick to the bed and have failed miserably. I've noticed that I had to redo my z-offset after getting it dialed in. Somewhat confidence inspiring that your bed looks similar to mine.

Did you find this page helpful?