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

MK2.5S upgrade reduces X print size by about 5mm #141

Open
led42 opened this issue Dec 15, 2019 · 1 comment
Open

MK2.5S upgrade reduces X print size by about 5mm #141

led42 opened this issue Dec 15, 2019 · 1 comment

Comments

@led42
Copy link

led42 commented Dec 15, 2019

There's no 2.5S branch so I can only report this bug there.

After the MK2.5 to 2.5S upgrade the print size was reduced by 5mm on the origin size (not possible to go to position x=0).

This is a physical constrain of this design, the endstop-block part enforces this distance on the origin side and reducing the endstop-block will only allow for 2-3mm more until the cables become a problem.

Please see: https://forum.prusaprinters.org/forum/original-prusa-i3-mk2.5s-mk2.5-hardware-firmware-and-software-help/cant-print-below-x5-ish-print-truncated/#post-179382
for more details and information on this issue?

At the moment this issue is made worse by the fact that slicer doesn't account for this problem so any prints that try to use the full size (250mm) will fail.

@floridaservices
Copy link

Old issue yes, but thought this could be useful input from what I have discovered on my own: Even with an Einsy board, without the endstops or endstop block, you will still have trouble on the 2.5S branch with getting the full size due to the cable bundle and unique cable holder of the 2.5 branch. I assume the unique cable holder was needed due to the frame differences between the MK2 and MK3 frames but i've not been able to confirm the frame differences, just assumptions as I don't have a MK3 to compare to. The MK3 cable holder is leaps and bounds ahead of the MK25S holder but it constricts the X axis size even further unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants