Looks like there is already a new release candidate that takes the change into account.
That was fast (haven’t tested it yet)
1 Like
Tested and … it works great!
Thanks for your “going into the deep” it solves the problem at least!
Just to prove the calibration lines up with the Mesh by raising one corner of the bed with some plastic between the platform and the plate to confirming the change is registered in the Mesh in the expected location.
Great debugging guys, @brvdboss That edit fixed my loading issue,
i had to edit it in the installed files on my Octoprint
~/oprint/lib/python2.7/site-packages/octoprint_bedlevelvisualizer/__init__.py (for anyone whos looking for it) Then added the “+” after the first “\d” as provided above
(\s*[\s+)|([?\s?+?-?\d+?.\d+]?\s*,?)
and then rebooted and ran the M420V (also had to up the Z limit to 5,20)
WORKED!@
You don’t have to do the edit manually anymore. The last release candidates already include the fix. You can go to the update settings for octoprint and allow it to use release candidates:
And this is my very basic configuration of the plugin:
I originally misunderstood the z-limit. If you use relative z-offset you can specify “-1,1” (or larger numbers if needed, default is -2,2). That defines how far up/down it shows from the origin height.
Hi nfmaas, did you figure out your z axes issues, I just go my Snapmaker the ending of last year and z axes linear modules would appear to lag each other sometimes on the first 15 layers. I took apart the unit several times only enough to try to level the unit and make sure the linear modules was not binding each other. The last attempt I took the unit completely apart and as I got to the cable attached to the z converter I found one of the cables came off with out pushing the lock. The loose cable on the converter seem to add enough of a lag on the signal to the linear module. After securing the cables and putting the unit back together I have not seen a lag between the z linear modules.
1 Like
I mailed snapmaker with the issue i had and they sended me two new rail modules. After that the calibration was a lot better.
I know this post has been quiet for a while but I’ve read the whole thing and don’t see what I"m looking for. Can anyone tell me how much they are adjusting by when doing the “Tight/Loose/Ok?” check? I was going to start with 0.05 either or up or down as needed. Does this seem right or should I do .01?
.05 is about all that’s really going to matter in my opinion.
You could do .01, but I’m almost certain that there’s more backlash in the machine than that. I’d also be impressed if you could feel the difference between .01 too tight and just perfect, so your probably end up just missing exactly right through simple human error.
Thank you so much for sharing this with the community. I’ve been dabbling with two different 3D printers for two years (including an A350) and have constantly struggled with keeping the bed level after 2 or 3 prints with fresh nozzles. I have read through your posts after completely rebuilding my A350 and it wasn’t until I found this one and used your 7x7 gcode that my system finally appears to be working across the entire bed surface for the first layer. Fingers crossed that it continues.
I had tried warming the print bed for an hour before starting the leveling process without success. I feel as if I’ve wasted several entire reels of filament trying to find the right settings to ensure adhesion when moving to certain corners of the print bed. I actually feel like up until now, my hand-adjusted Creality 10s was easier to configure than the A350. Thanks to your knowledge you’ve shared here, I might be finally turning a corner.
Please Help, I have followed all these steps, everything seems perfect with the Hot Level gcode. But when i go to print everything is then way to tight and not filiment comes out.
Use live z offset on the touchscreen?