-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ender 3 S1 #28
Comments
Hi, thank you very much. You sure these coordinates are correct? Marlin should factor in probe-to-nozzle offset when doing a |
Ouch, seems like I got it wrong in the README: should be But be VERY CAREFUL when doing that! There are 2 settings in Marlin, bed size and max coordinate. My Ender 3 Pro has a bed size of 235, but can easily move to X=245 without colliding with anything. If the same is true for the S1, using I'd be happy to implement support for it if you think that would be benificial. |
Hmm, weird, see the results.. M211 S0; Disable End Stop M211 S1; Enable End Stop so I guess they should work, but the same behavior, only moves until Y179 not passed that. Send: G30 X30 Y190 Here are the results of 503 just in case. Send: M503 |
Hey Juri, quick question on something I am noticing. Say I use AutoBim to set the Ender 3V2, it goes through the cycles and finally done. If I immediately do another one, the system things is out of calibration.
I just did for instance, and all was ok. I did the process again and the first corner was -0.11 out, that is a lot.
I have the regular 3nder 3V2 with the second stepper motor and the Y cable connecting both Z motors and for what I get the unit is pretty balanced and prints are pretty good, but this seems to be an issue with my unit.
Any ideas or suggestions or opinion on something like? https://www.youtube.com/watch?v=oUdoJUs8Zcg
Regards,
Paul Aviles
From: Juri Berlanda ***@***.***>
Sent: Tuesday, January 4, 2022 5:24 AM
To: j-be/AutoBim ***@***.***>
Cc: Paul Aviles ***@***.***>; Author ***@***.***>
Subject: Re: [j-be/AutoBim] Ender 3 S1 (Issue #28)
Ouch, seems like I got it wrong in the README: should be M211 S0 to disable and M211 S1 to reenable (see https://marlinfw.org/docs/gcode/M211.html). M121 seem to be the physical endstops, not the virtual ones.
But be VERY CAREFUL when doing that!
There are 2 settings in Marlin, bed size and max coordinate. My Ender 3 Pro has a bed size of 235, but can easily move to X=245 without colliding with anything. If the same is true for the S1, using M211 may help.
I'd be happy to implement support for it if you think that would be benificial.
—
Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB7VU2AZYMBHJI3IPXSX6X3UULDFZANCNFSM5LEUE4TQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
If I had to guess I'd go for "bent bed" (see #10), but 0.11 is indeed a lot. Apart from using "First corner as reference" as propsed there too I'd recommend counterchecking with the Bed Level Visualizer. As for the belt driven Z axis: I am most definitely going to do that next time I'm heavily bored. I'm just not sure if I'll go with the design you linked, or if I'll mod the Ender 3 to a Voron Switchwire (see here or here or Google - there are a couple more). I think though it is not necessary to get good prints, but it might help. Also, Z axis with screw is unbelievably difficult to troubleshoot imho. And it sure looks amazing. |
Worked fine on an Ender 3 S1 stock firmware 1.0.3C but the bed measurements need to be adjusted to:
x 10 - y 25
x 20 - y 179
x 179 - y 179
x 179 - y 25
I think the probe points (hence the x10 - y25) should sit on top of the screws for better measurement/alignment but that is my personal feeling.
Juri, this is an amazing plugin so thank you!
The text was updated successfully, but these errors were encountered: