[BUG] Right side of the print too high from the bed when using ABL #269
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bug Description
Test print, 3x3 grid of squares, first two columns of 3 from the left are acceptable, while the last one, on the right, is barely touching the bed.
After manual changes to bed level, Z0 height, results are still the same.
Steps to Reproduce
Installed BLTouch 3.1 following instructions from here, downloaded and flashed MEGA_S_BLT_10_v1.3.1, restored defaults, saved to eeprom. BLTouch passes self test and responds to commands as intended, found my z offset also following instructions from here.
Using start and end gcode provided here (M420 S1 after G28, to enable mesh leveling).
Expected behavior: Consistent first layer of the print
Actual behavior: Right side of the print barely sticks to the bed
Additional Information
Running 1.3.1 on Mega S, with 0.0.2 board.
When checking my bed level in octoprints bed visualizer I can see manual adjustments being reflected accordingly.
I might have solved the issue...
In the meantime change firmware to klipper... and the issue persisted...
It is the bed, bed carriage to be exact, even tho I've tightened the sprints as much as possible, it still has some give on the left side (with one support) and bends a tiny bit from the force of the probe...
This is a common issue with the Mega/S/P Printers. Take a look here:
https://habitoti.de/wordpress/bltouch-frustration/
The more you know... took my tiny bubble level to the carriage and... level visibly changes as it goes from one end of the x axis to the other... time to go back to Marlin and do some math since there is no simple way to edit mesh point in klipper (outside of manually editing them in config file)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.