wp/Marlin-2-0-x-Anycubic-i3-MEGA-S
1
0
Fork 0
Code Issues 28 Pull Requests 2 Actions Packages Projects Releases 30 Wiki Activity

Updated FAQ (english) (markdown)

Oliver Köster
2023-01-19 08:55:50 +01:00
parent 5e81a0c877
commit e63634b26d
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ-(english).md

@@ -116,4 +116,10 @@
>1. Prohibit all movement until homing has been performed. >1. Prohibit all movement until homing has been performed.
>2. Allow any movement outside of the end stops. >2. Allow any movement outside of the end stops.
> >
>I opted for the second option, because manual driving often means you know exactly what you are doing and can keep an eye on the nozzle. The prerequisite for homing would cause more problems if there is still a component on the print bed. >I opted for the second option, because manual driving often means you know exactly what you are doing and can keep an eye on the nozzle. The prerequisite for homing would cause more problems if there is still a component on the print bed.
## I installed a BLTouch sensor in my i3 MEGA/MEGA S/MEGA PRO, but one side of the print bed has a higher distance to the nozzle than the other. But that only affects the difference between the left and right side.
> This is neither a problem with the firmware nor with your installation. Rather, there is a design-related hardware issue. The two superimposed rods of the X-guide are not 100% on top of each other, but slightly twisted. Because one of the two rods is further forward or further back, the rotation of the entire X axis changes and the nozzle raises or lowers accordingly. The problem was described very well by [Hansi in his blog](https://habitoti.de/wordpress/bltouch-frustration/). As a solution, you can either try to align both rods/axles absolutely the same, or you can compensate for this by calculating the deviation and telling the slicer when printing. There is also a [tool that solves this problem](https://habitoti.de/wordpress/mesh-adjustment-tool/).
Many thanks and a big compliment to Hansi, who identified, solved and documented this problem!