Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hot end carriage colliding with rear bed retainer during levelling #19

Closed
bakedpanda opened this issue Jun 4, 2020 · 2 comments
Closed
Labels
duplicate This issue or pull request already exists

Comments

@bakedpanda
Copy link

I'm having some trouble with this firmware (mpmd_marlin_1.1.x-119r11-SM1110-PCfan-10Alimit) where the carriage is colliding with the rear bed clip during levelling. Would you be able to compile a release with a smaller probing grid?

My printer is using the the stock parts.

Thanks

@PurpleHullPeas
Copy link

This is a repeat of #11 .
There are fixes and workaround options in the thread, above. The collision is due to false advertising. Monoprice/Malyan advertises a 110 mm build plate diameter, but designed the stock printer in such a way that it is impossible without modifications (such as a glass bed or alternate bed clip design).

@aegean-odyssey
Copy link
Owner

aegean-odyssey commented Jun 5, 2020

Yes, it does seem that some printers do not meet the manufacturer's own spec. Here, we've seen the issue on one of four printers (so far). Probably the easiest and quickest solution for you is to change the AUTO_CALIBRATE.gcode file in the setup_gcode directory of the micro SD card contents. It's a simple change that will direct the G29 command to shrink the grid that it uses to generate a bed level mesh.

With a text editor, change the line
G29 V3
to
G29 L-50 R50 F-50 B50 V3

I'll close this issue as it is a duplicate of issue #11. Please don't hesitate to re-open it if I've misunderstood your issue.

Thank you for giving the firmware a try.

@aegean-odyssey aegean-odyssey added the duplicate This issue or pull request already exists label Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants